ITU-T M 3701-2010 Common management services C State management C Protocol neutral requirements and analysis (Study Group 2)《通用管理业务 状态管理 与协议无关的要求和分析 2号研究组》.pdf

《ITU-T M 3701-2010 Common management services C State management C Protocol neutral requirements and analysis (Study Group 2)《通用管理业务 状态管理 与协议无关的要求和分析 2号研究组》.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3701-2010 Common management services C State management C Protocol neutral requirements and analysis (Study Group 2)《通用管理业务 状态管理 与协议无关的要求和分析 2号研究组》.pdf（26页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T M.3701TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2010) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Integrated services digital networks Common management services State management Protocol neutral requirements an

2、d analysis Recommendation ITU-T M.3701 ITU-T M-SERIES RECOMMENDATIONS TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Introduction and general principles of maintenance and maintenance organization M.10M.299 International transmission systems M.300M.559 International telephone ci

3、rcuits M.560M.759 Common channel signalling systems M.760M.799 International telegraph systems and phototelegraph transmission M.800M.899 International leased group and supergroup links M.900M.999 International leased circuits M.1000M.1099 Mobile telecommunication systems and services M.1100M.1199 I

4、nternational public telephone network M.1200M.1299 International data transmission systems M.1300M.1399 Designations and information exchange M.1400M.1999 International transport network M.2000M.2999 Telecommunications management network M.3000M.3599 Integrated services digital networks M.3600M.3999

5、Common channel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T M.3701 (01/2010) i Recommendation ITU-T M.3701 Common management services State management Protocol neutral requirements and analysis Summary Recommendation ITU-T M.3701

6、provides the requirements and analysis for one of the common management services state management. The state management capabilities are intended for use by specific information object classes (IOCs). History Edition Recommendation Approval Study Group 1.0 ITU-T M.3701 2010-01-13 2 Keywords Common m

7、anagement service, state management. ii Rec. ITU-T M.3701 (01/2010) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Secto

8、r (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every

9、four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview,

10、the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary

11、. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the neg

12、ative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the

13、use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendati

14、on, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/

15、www.itu.int/ITU-T/ipr/. ITU 2010 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T M.3701 (01/2010) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 1 4 Abbreviations 2 5 Conventions 2 6 Requi

16、rements 2 6.1 Business level requirements . 2 7 Analysis overview 8 7.1 Concepts and background . 8 7.2 Information object classes 8 7.3 Interface definition . 16 7.4 IOC properties, inheritance and import 16 Bibliography. 17 Rec. ITU-T M.3701 (01/2010) 1 Recommendation ITU-T M.3701 Common managemen

17、t services State management Protocol neutral requirements and analysis 1 Scope This Recommendation defines the requirements and specifies the semantics of the state and status information visible across the management interface. It also specifies the interaction required for the management of the st

18、ate and status information. The state and status attributes specified in this document shall be used, where applicable, as attributes in information object class (IOC) definitions of other management interface specifications. When used by the IOC definition, the semantics of the state and status att

19、ributes can be qualified and enhanced if deemed necessary. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All

20、Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regu

21、larly published. The reference of a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T M.3020 Recommendation ITU-T M.3020 (2009), Management interface specification methodology. ITU-T M.3060 Recommendation ITU-T M.3060/Y.2401 (2006)

22、, Principles for the Management of the Next Generation Networks. ITU-T M.3700 Recommendation ITU-T M.3700 (2010), Common management services Object management Protocol neutral requirements and analysis. ITU-T M.3702 Recommendation ITU-T M.3702 (2010), Common management services Notification manageme

23、nt Protocol neutral requirements and analysis. ITU-T X.680 Recommendation ITU-T X.680 (2008) | ISO/IEC 8824-1:2008, Information technology Abstract Syntax Notation One (ASN.1): Specification of basic notation. ITU-T X.731 Recommendation ITU-T X.731 (1992), Information technology Open Systems Interco

24、nnection Systems management: State management function. 3 Definitions For the purposes of this Recommendation, the following terms and definitions apply. This Recommendation uses the following terms from ITU-T M.3020: association; agent; data; information object class (IOC); Information Object; 2 Re

25、c. ITU-T M.3701 (01/2010) Information Object Instance; manager; UML. This Recommendation uses the following terms from ITU-T X.731: capacity increase (CI) capacity decrease (CD) 4 Abbreviations None. 5 Conventions This Recommendation uses the conventions defined in ITU-T M.3020 for requirements capt

26、ure and analysis. UML state diagrams are used for state attribute transition diagrams. 6 Requirements The management state of a managed object represents the instantaneous condition of availability and operability of the associated resource from the point of view of management. Different classes of

27、managed object have a variety of state attributes that express and control aspects of the operation of their associated resource that are peculiar to each class. However, the management state is expected to be common to a large number of resources and for this reason is to be standardized; it expres

28、ses key aspects of their usability at any given time. Its purpose is to control the general availability of a resource and to make visible information about that general availability. 6.1 Business level requirements State management is defined to specify and to standardize the generic state and stat

29、us attributes of managed resources. There are a variety of managed objects and the related network resources. Different managed objects and the network resources they model may require different subsets of the attributes defined in state management. State management shall specify status attributes,

30、modelling more detailed information about other aspects of the state of the corresponding network resources that may affect their operability and usage. The status attributes also contain more detailed information about the administrative constraints on its operation that are controlled by a manager

31、. Identifier Definition REQ-SM-FUN-01 State management shall specify an operability state which defines whether or not the resource is physically installed and working. The operational state gives the information about the real capability of a resource to provide or not provide service. The operatio

32、nal state is “enabled“ when the resource is able to provide service, “disabled“ when the resource cannot provide service. A resource can lose the capability to provide service because of a fault or because another resource on which it depends is out of service (e.g., disabled or locked). Rec. ITU-T

33、M.3701 (01/2010) 3 In case a resource does not lose completely its capability to provide service, the operational state shall be “enabled“ and the availability status shall be “degraded“. REQ-SM-FUN-02 State management shall specify a usage state which defines whether or not the resource is actively

34、 in use at a specific instant, and if so, whether or not it has spare capacity for additional users at that instant. A resource is said to be “in use“ when it has received one or more requests for service that it has not yet completed or otherwise discharged, or when some part of its capacity has be

35、en allocated, and not yet reclaimed, as a result of a previous service request. Otherwise it is “not in use“. REQ-SM-FUN-03 State management shall specify an administration state which defines permission to use (“unlocked“) or prohibition against using (“locked“) the resource imposed through the man

36、agement services. The administrative state is used by the operator to make a resource available for service, or to remove a resource from service. For example: for fault correction, the administrative state can be used to isolate a faulty resource; in case of redundancy, the administrative state can

37、 be used to lock the active resource and let the standby resource become active (preventive maintenance); for test management, the administrative state can be used to put a resource out of service to run an intrusive test on it. REQ-SM-FUN-04 State management shall specify a lifecycle state which re

38、presents the planned and tracked state of a physical or logical resource. The lifecycle state tracks the plan for the managed object representing a resource. Inventoried resources may have a life cycle attribute so that their deployment can be planned, tracked, and managed. Logical resources, e.g.,

39、connection, are not inventoried; however, their deployment can be planned, tracked, and managed using a lifecycle state attribute. REQ-SM-FUN-06 State management shall specify an alarm status which can have zero or more of the following values, not all of which are applicable to every class of manag

40、ed object. When the value of this attribute is empty, this implies that none of the status conditions described below are present. Under repair: The resource is currently being repaired. When under repair value is present, the operational state is either disabled or enabled. Critical: One or more cr

41、itical alarms indicating a fault have been detected in the resource, and have not been cleared. The operational state of the managed object can be disabled or enabled. Major: One or more major alarms indicating a fault have been detected in the resource, and have not yet been cleared. The operationa

42、l state of the managed object can be disabled or enabled. 4 Rec. ITU-T M.3701 (01/2010) Minor: One or more minor alarms indicating a fault have been detected in the resource, and have not yet been cleared. The operational state of the managed object can be disabled or enabled. Alarm outstanding: One

43、 or more alarms have been detected in the resource. The condition may or may not be disabling. If the operational state is enabled, additional attributes, particular to the managed object class, may indicate the nature and cause of the condition and the services that are affected. REQ-SM-FUN-07 Stat

44、e management shall specify a procedural status which is supported only by those classes of managed objects that represent some procedure (e.g., a test process) which progresses through a sequence of phases. Depending upon the managed object class definition, the procedure may be required to reach ce

45、rtain phase for the resource to be operational and available for use (i.e., for the managed object to be enabled). Not all phases may be applicable to every class of managed object. If the value of this attribute is an empty set, the managed object is ready; for example, the initialization is comple

46、te. When the value of this attribute is empty, this implies that none of the status conditions described below are present. Initialization required: The resource requires initialization to be invoked by the manager before it can perform its normal functions, and this procedure has not been initiated

47、. The manager may be able to invoke such initialization through an action. The terminating condition may also be present. The operational state is disabled. Not initialized: The resource requires initialization before it can perform its normal functions, and this procedure has not been initiated. Th

48、e resource initializes itself autonomously, but the operational state may be either disabled or enabled, depending upon the managed object class definition. Initializing: The resource requires initialization before it can perform its normal functions, and this procedure has been initiated but is not

49、 yet complete. When this condition is present, the initialization required condition is absent, since initialization has already begun. The operational state may be disabled or enabled, depending upon the managed object class definition. Reporting: The resource has completed some processing operation and is notifying the results of the operation, e.g., a test process is sending its results. the operational state is enabled. Terminating: The resource is in a termin