ITU-T M 3706-2013 Common management services C Test management C Protocol neutral requirements and analysis (Study Group 2)《(预发布)共同管理业务 测试管理 协议中立要求与分析》.pdf

《ITU-T M 3706-2013 Common management services C Test management C Protocol neutral requirements and analysis (Study Group 2)《(预发布)共同管理业务 测试管理 协议中立要求与分析》.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3706-2013 Common management services C Test management C Protocol neutral requirements and analysis (Study Group 2)《(预发布)共同管理业务 测试管理 协议中立要求与分析》.pdf（38页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T M.3706TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2013) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Integrated services digital networks Common management services Test management Protocol neutral requirements and

2、 analysis Recommendation ITU-T M.3706 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 cir

3、cuits 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 In

4、ternational 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.3999C

5、ommon channel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T M.3706 (11/2013) i Recommendation ITU-T M.3706 Common management services Test management Protocol neutral requirements and analysis Summary Recommendation ITU-T M.3706 pr

6、ovides the requirements and analysis for test management which is one of the common management services. Test management functions are used to assist in various high level management function sets such as fault management or performance management. The purpose of testing is to obtain information abo

7、ut the functionality and performance of the managed network subjected to the test. The functional requirements for the test management interface include the management functions for test object controlling, test category, test object state monitoring, test result reporting, etc. In the analysis part

8、, the detailed information model supporting the above functions across the management interface is provided. History Edition Recommendation Approval Study Group Unique ID*1.0 ITU-T M.3706 2013-11-13 2 11.1002/1000/12045 Keywords Common management service, test management, test management IRP. _ *To

9、access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T M.3706 (11/2013) FOREWORD The International Telecommunication Union (ITU) is the U

10、nited Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recomm

11、endations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The a

12、pproval 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, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administ

13、ration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compl

14、iance 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 negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation i

15、s required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed In

16、tellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendati

17、on. 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:/www.itu.int/ITU-T/ipr/. ITU 2014 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, withou

18、t the prior written permission of ITU. Rec. ITU-T M.3706 (11/2013) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Requirements 2 6.1 Concepts and backgrou

19、nd . 2 6.2 Business level requirements . 3 6.3 Specification-level requirements 6 7 Analysis 12 7.1 Concepts and background . 12 7.2 Information object classes 13 7.3 Interface definition . 19 Bibliography. 30 Rec. ITU-T M.3706 (11/2013) 1 Recommendation ITU-T M.3706 Common management services Test

20、management Protocol neutral requirements and analysis 1 Scope The purpose of this Recommendation is to define an interface through which a manager can perform test functions on an agent. This document specifies the overall requirements and the analysis for test management and defines the semantics o

21、f operations (and their parameters) visible via the management interface. This Recommendation provides the protocol neutral model definition for notification. It defines, for the purpose of performing test functions on an agent, the information is observable and controlled by the management systems

22、client and it also specifies the semantics of the interactions used to carry this information. This Recommendation does not define the syntax or encoding of the operations and their parameters. 2 References The following ITU-T Recommendations and other references contain provisions which, through re

23、ference 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 revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the mo

24、st 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 this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T M.3020 Rec

25、ommendation ITU-T M.3020 (2009), Management interface specification methodology. ITU-T M.3160 Recommendation ITU-T M.3160 (2008), Generic, protocol-neutral management information model. ITU-T M.3702 Recommendation ITU-T M.3702 (2010), Common management services notification management Protocol neutr

26、al requirement 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.737 Recommendation ITU-T X.737 (1995) | ISO/IEC 10040:1998, Information technology Open Systems Inte

27、rconnection Systems Management: Confidence and diagnostic test categories. ITU-T X.745 Recommendation ITU-T X.745 (1993) | ISO/IEC 10164-12:1994, Information technology Open Systems Interconnection Systems Management: Test management function. 2 Rec. ITU-T M.3706 (11/2013) 3 Definitions 3.1 Terms de

28、fined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 agent ITU-T M.3020 3.1.2 information object class ITU-T M.3020 3.1.3 manager ITU-T M.3020 3.1.4 test category ITU-T X.745 3.1.5 test conductor ITU-T X.745 3.1.6 test object ITU-T X.745 3.1.7 managed object referrin

29、g to test ITU-T X.745 3.2 Terms defined in this Recommendation This Recommendation has no new terms or definitions. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: EMS Element Management System FS Function Set ID Identifier IOC Information Object Class

30、 IRP Integration Reference Point MORT Managed Object Referring to Test NE Network Element NMS Network Management System OS Operating System TO Test Object 5 Conventions This Recommendation follows the conventions defined in ITU-T M.3020. In this Recommendation, Test management IRP is an interface in

31、 an agent providing test management functions. 6 Requirements 6.1 Concepts and background The test management function is used to assist in various high level management function sets such as fault management or performance management. The purpose of testing is to obtain information about the functi

32、onality and performance of the managed network subjected to the test. Testing is an activity that involves the operator, the managing system (operating system (OS) and the managed system (network element (NE). Generally the operator requests the execution of tests from the OS and the managed NE auto

33、nomously executes the tests without any further support from the operator. Rec. ITU-T M.3706 (11/2013) 3 Based on the descriptions in ITU-T X.737, there are eight test categories: Connection test, Connectivity test, Data integrity test, Loopback test, Protocol integrity test, Resource boundary test,

34、 Resource self-test and Test infrastructure test. This Recommendation reuses the above test categories and provides a test category extension mechanism. In the case of intrusive tests it is required that the network resources to be tested are locked prior to test execution. During the test execution

35、 the telecommunication service provided by the network resources is interrupted. After completion of the test, depending on the test result, the network resources shall be set to the most appropriate state. Test management capabilities should be provided over the NMS-EMS in order to allow the NMS op

36、erator to perform tests on network resources. This capability is especially important at times when only the NMS but not the EMS is attended, which might be the case at night or during weekends. In the context of fault management the NMS operator may use the testing capabilities over the NMS-EMS int

37、erface for numerous purposes: When a fault has been detected and if the information provided in the alarm report is not sufficient to localise the faulty resource, tests can be executed in order to localise the fault. When a fault has been detected and if the information provided in the alarm report

38、 specifies the faulty resource, tests can be executed on that resource in order to determine the required repair action. During normal operation of the NE, tests can be executed for the purpose of discovering undetected faults. After a faulty resource has been repaired or replaced and before it is r

39、estored to service, tests can be executed on that resource in order to make sure that it is fault free. However, regardless of the context where the testing is used, its target is always the same: verify if a systems physical or functional resource performs properly and, in case it happens to be fau

40、lty, provide all the information to help the operator to localise and correct the fault. The test management IRP bases its design on work referenced in ITU-T X.745. 6.2 Business level requirements 6.2.1 Requirements The test management requirements can be grouped into one of the following categories

41、: General, i.e., the test management requirements for general purposes, e.g., test identification, test result header format, etc. Test object management, e.g., initiate test object, terminate test object, subscribe test object, resume test object, query test object information. Test category, e.g.,

42、 query or specify test types. Test result reporting, e.g., report test results. 6.2.1.1 General The following requirements apply for general purposes. REQ-TM-FUN-01 An agent shall provide a mechanism for managers to perform test functions on managed networks. REQ-TM-FUN-02 An agent shall provide a m

43、echanism to identify each test object initiated by a manager. 4 Rec. ITU-T M.3706 (11/2013) REQ-TM-FUN-03 It is required that all test results generated by agents support the same header format that contains enough information to identify the test category, the managed entities that are tested and t

44、he time stamp at which the test result is generated. 6.2.1.2 Test object management The following requirements apply to the test management interface. REQ-TM-FUN-04 A manager shall be able to initiate a test object to be performed in an agent. REQ-TM-FUN-05 A manager shall be able to query the detai

45、led information of a specified test object in an agent. REQ-TM-FUN-06 A manager shall be able to suspend the execution of a specified test object in an agent. REQ-TM-FUN-07 A manager shall be able to resume the execution of a suspended test object in agent. REQ-TM-FUN-08 A manager shall be able to t

46、erminate a specified test object in an agent. REQ-TM-FUN-09 The agent shall provide managers with the capability to monitor the states of a test object. The test state may assume one of the following values: not initialised, idle, initialising, testing, terminating or disabled. The actual test state

47、 value shall be derived from the actual operational state and procedural status according to the mapping table specified in ITU-T X.745. Any state change shall be reported to the manager using notifications. 6.2.1.3 Test category discovery The following requirements apply for test category discovery

48、. REQ-TM-FUN-10 An agent shall provide managers with the capability to discover the test categories (types) supported by the agent. The possible test categories include but are not limited to: Connection test, Connectivity test, Data integrity test, Loopback test, Protocol integrity test, Resource b

49、oundary test, Resource self-test and Test infrastructure test. These test categories are defined in ITU-T X.737. When there are new test categories to be used in the test management interface, an agent should provide means for a manager to discover the new test categories. 6.2.1.4 Test result management The following requirements apply for test result management. REQ-TM-FUN-11 When predefined trigger events occur, the test result of the test object should be gener