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

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

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

2、nd analysis Recommendation ITU-T M.3700 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 c

3、ircuits 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

4、International 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.399

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

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

7、ommon management service, object management. ii Rec. ITU-T M.3700 (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 Standardizati

8、on Sector (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 meet

9、s every 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 p

10、urview, 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 v

11、oluntary. 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

12、 the negative 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 invo

13、lve the 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 Reco

14、mmendation, 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 a

15、t http:/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.3700 (01/2010) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 1 4 Abbreviations and acronyms 2 5

16、Conventions 2 6 Requirements 2 6.1 Business level requirements . 2 7 Analysis 8 7.1 System context 8 7.2 Information object classes 9 7.3 Interface definition . 9 Bibliography. 25 Rec. ITU-T M.3700 (01/2010) 1 Recommendation ITU-T M.3700 Common management services Object management Protocol neutral

17、requirements and analysis 1 Scope This Recommendation defines the requirements for basic object management, including retrieve object information, create object, delete object, modify object attribute, cancel operation, subscribe notification, receive notification, generate attribute value change no

18、tification, generate state change notification, generate object create notification, generate object delete notification. The operations and notifications specified in this document shall be used, where applicable, in information object class (IOC) definitions of other management interface specifica

19、tions. 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 Recommendations and other references are subject to

20、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 regularly published. The reference to a document within

21、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), Principles for the Management of the Next Generati

22、on Networks. ITU-T M.3701 Recommendation ITU-T M.3701 (2010), Common management services State management Protocol neutral requirements and analysis. ITU-T M.3702 Recommendation ITU-T M.3702 (2010), Common management services Notification management Protocol neutral requirements and analysis. ITU-T

23、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. 3 Definitions For the purposes of this Recommendation, the following terms and definitions apply. This Recommendation uses the following terms

24、from ITU-T M.3020: agent; association; data; manager; information object class (IOC). 2 Rec. ITU-T M.3700 (01/2010) 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: EM Element Manager IOC Information Object Class IRP Integration Reference Point NE Netwo

25、rk Element NM Network Manager OS Operations System UML Unified Modelling Language 5 Conventions This Recommendation uses the conventions defined in ITU-T M.3020 for requirements capture and analysis. 6 Requirements 6.1 Business level requirements 6.1.1 Requirements 6.1.1.1 General requirements This

26、service uses the following services and thus implicitly imports all the requirements defined therein: notification management ITU-T M.3702; state management ITU-T M.3701. In addition, the following specific requirements apply for object management as specified in this and subsequent clauses. Identif

27、ier Definition REQ-OM-FUN-01 The object management functions shall be able to operate on any information object. REQ-OM-NON-01 The definitions of new object types may specify which object management functions are applicable. REQ-OM-FUN-02 The object management capabilities shall be independent of an

28、y specific definitions of information objects, attributes, etc. 6.1.1.2 Information retrieval Identifier Definition REQ-OM-FUN-03 The agent will provide an operation to retrieve the value of attributes from one or more IOC instances. REQ-OM-FUN-04 An operation to retrieve the containment relationshi

29、ps between the IOC instances of a containment tree of information objects shall be provided. REQ-OM-FUN-05 An operation to retrieve the interface versions that are supported by the agent may be provided. Rec. ITU-T M.3700 (01/2010) 3 REQ-OM-FUN-06 An operation to cancel a previously initiated operat

30、ion if it has not completed may be provided. This operation shall, as a minimum, be able to cancel the operation that retrieves attributes. It may be specified to cancel any operation. 6.1.1.3 Life cycle operations Life cycle operations are not intended to be implemented without implementation of th

31、e information retrieval requirements. Identifier Definition REQ-OM-FUN-07 An operation to create an instance of a information object shall be provided. REQ-OM-FUN-08 An operation to delete one or more instances of information objects shall be provided. REQ-OM-FUN-09 An operation to modify one or mor

32、e attributes of one or more instances of information objects shall be provided. REQ-OM-FUN-10 A manager may subscribe to notifications about a set of object management operations: object creation, object deletion, object modification and when part or the whole configuration information should be syn

33、chronized. 6.1.2 Actor roles The capabilities described in this Recommendation are available and relevant to all agents and managers. 6.1.3 Telecommunication resources The object management functionality is applicable to all types of telecommunication resources. 6.1.4 High-level use cases The first

34、overview use-case diagram in Figure 1 shows the overall interaction of the object management function. M.3700(10)_F01ObjectmanagementStatemanagementManagerInformationretrievalLife cycleoperationsNotificationmanagementFigure 1 High level use case for object management 4 Rec. ITU-T M.3700 (01/2010) 6.

35、1.4.1 Retrieve object information Use-case stage Evolution/Specification Related use Goal The agent returns to the manager attribute values from one or more information object class instances. Actor and roles The manager invokes operations on the agent. Telecom resources The object management functi

36、onality is applicable to all types of telecommunication resources. Assumptions The use case is applicable to any information object class. One or several information objects may be retrieved based on the containment hierarchy. There is an open communication channel between the manager and the agent.

37、 This general service is used to get attributes unless a specific service has been defined by one of the common management services. Pre conditions None. Begins when The manager sends a request to retrieve information on one or more IOC instances. Step 1 The manager invokes the information retrieval

38、 operation on the agent. Ends when Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. Cancel pending operation Exceptions operationFailed duplicateInvocation resourceLimitation operationCancelled complexityLimitation Post conditions None.

39、Traceability REQ-OM-FUN-01, REQ-OM-FUN-03, REQ-OM-FUN-04, REQ-OM-FUN-05 6.1.4.2 Cancel pending operation Use-case stage Evolution/Specification Related use Goal The manager invokes this operation to cancel an on-going operation it issued before. Actor and roles The manager invokes the cancel operati

40、on on the agent. Telecom resources The object management functionality is applicable to all types of telecommunication resources. Rec. ITU-T M.3700 (01/2010) 5 Use-case stage Evolution/Specification Related use Assumptions The use case is applicable when specified by the relevant information object,

41、 Ref. REQ-OM-FUN-01. The previous operation is either already being processed or waiting for processing by the agent. There is an open communication channel between the manager and the agent. Pre conditions The previous operation invoked by this manager has not been completed. Begins when The manage

42、r sends a request to cancel a previously issued operation. Step 1 The manager invokes the cancel operation on the agent. Ends when The requested operation is cancelled or an exception is returned to the manager. Exceptions operationFailed Post conditions The operation identified by the operation is

43、cancelled. Traceability REQ-OM-FUN-06 6.1.4.3 Create object Use-case stage Evolution/Specification Related use Goal This operation is invoked by the manager to request the agent to create a Information object class instance in the MIB maintained by the agent. Actor and roles The manager invokes the

44、operation on the agent. Telecom resources The object management functionality is applicable to all types of telecommunication resources. Assumptions The use case is applicable when specified by the relevant information object, Ref. REQ-OM-FUN-01. This operation will create only one IOC instance. The

45、re is an open communication channel between the manager and the agent. Pre conditions A IOC instance with the same distinguished name as the object specified for creation does not exist. Begins when The manager sends a request to create a IOC instance in the MIB maintained by the agent. Step 1 The m

46、anager invokes the create information object operation on the agent. Ends when The requested IOC instance is created or an exception is returned to the manager. 6 Rec. ITU-T M.3700 (01/2010) Use-case stage Evolution/Specification Related use Exceptions operationFailed objectClassSpecificationMismatc

47、h invalidObjectInstance createNotAllowed noSuchObjectClass classInstanceConflict noSuchAttribute invalidAttributeValue missingAttributeValue parentObjectDoesNotExist objectExists Post conditions a) The IOC instance of the specified object class has been created with the specified distinguished name.

48、 b) An object creation notification is emitted for the created object, if notifiable. Notifiable means here that the notification is supported and not suppressed. Traceability REQ-OM-FUN-07 6.1.4.4 Delete object Use-case stage Evolution/Specification Related use Goal This operation is invoked by the

49、 manager to request the deletion of one or more information object class instances from the MIB maintained by the agent. Actor and roles The manager invokes the operation on the agent. Telecom resources The object management functionality is applicable to all types of telecommunication resources. Assumptions The use case is applicable when specified by the relevant information object, Ref. REQ-OM-FUN-01. This operation will delete one or more IOC instances. There is an open