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

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

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

2、ts and analysis Recommendation ITU-T M.3704 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 telepho

3、ne circuits 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.1

4、199 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

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

6、-T M.3704 provides the requirements and analysis for one of the common management services performance management. The functional requirements for the performance management interface include the management functions for performance measurement jobs, performance threshold monitor and performance dat

7、a files. In the analysis part, the detail information model supporting the above function across the management interface is provided. History Edition Recommendation Approval Study Group 1.0 ITU-T M.3704 2010-01-13 2 Keywords Common management service, measurement job, performance management, PMIRP,

8、 threshold monitor. ii Rec. ITU-T M.3704 (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 Sector (ITU-T) is a pe

9、rmanent 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 four years, estab

10、lishes 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, the necessary sta

11、ndards 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. However, the Re

12、commendation 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 negative equivalents

13、 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 use of a claimed

14、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 Recommendation, ITU had not r

15、eceived 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:/www.itu.int/ITU-T

16、/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.3704 (01/2010) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Re

17、commendation . 2 4 Abbreviations 2 5 Conventions 2 6 Requirements 3 6.1 Concepts and background . 3 6.2 Business-level requirements . 3 6.3 Specification-level requirements 6 7 Analysis 18 7.1 Concepts and background . 18 7.2 Information object classes 18 7.3 Interface definition . 30 7.4 Scenarios

18、. 52 Bibliography. 55 Rec. ITU-T M.3704 (01/2010) 1 Recommendation ITU-T M.3704 Common management service Performance management Protocol neutral requirements and analysis 1 Scope This Recommendation specifies the overall requirements and the analysis for performance management and defines the seman

19、tics of operations (and their parameters) visible across the management interface in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters. The transferring of performance data file is outside the scope of this Recommendation. 2 Refer

20、ences 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 revision; user

21、s 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 this Recommend

22、ation 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.3160 Recommendation ITU-T M.3160 (2008), Generic, protocol-neutral management information model. ITU-T M.3400 Re

23、commendation ITU-T M.3400 (2000), TMN management functions. ITU-T M.3700 Recommendation ITU-T M.3700 (2010), Common management services Object management Protocol neutral requirements and analysis. ITU-T M.3701 Recommendation ITU-T M.3701 (2010), Common management services State management Protocol

24、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 Q.822 Recommendation ITU-T Q.822 (1994), Stage 1, Stage 2 and Stage 3 description for the Q3 Interface Performance

25、management. 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.721 Recommendation ITU-T X.721 (1992) | ISO/IEC 10165-2:1992, Information technology Open systems Interconnection Str

26、ucture of management information: Definition of management information. ITU-T X.739 Recommendation ITU-T X.739 (1993) | ISO/IEC 10164-11:1994, Information technology Open Systems Interconnection Systems Management: Metric objects and attributes. 2 Rec. ITU-T M.3704 (01/2010) 3 Definitions 3.1 Terms

27、defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 agent ITU-T M.3020: Encapsulates a well-defined subset of management functionality. It interacts with managers using a management interface. From the managers perspective, the agent behaviour is only visible via

28、the management interface. 3.1.2 information object class ITU-T M.3020: Describes the information that can be passed/used in management interfaces and is modelled using the stereotype “Class“ in the UML meta-model. For a formal definition of information object class and its structure of specification

29、, see Annex B of ITU-T M.3020. 3.1.3 manager ITU-T M.3020: Models a user of agent(s) and it interacts directly with the agent(s) using management interfaces. Since the manager represents an agent user, it gives a clear picture of what the agent is supposed to do. From the agent perspective, the mana

30、ger behaviour is only visible via the management interface. NOTE Considered equivalent to IRPManager b-3GPP TS 32.150. 3.2 Terms defined in this Recommendation This Recommendation has no new definitions. 4 Abbreviations This Recommendation uses the following abbreviations: DN Distinguished Name EM E

31、lement Manager FS Function Set FTP File Transfer Protocol IOC Information Object Class IRP Integration Reference Point NE Network Element NM Network Manager PM Performance Management PMIRP Performance Management Integration Reference Point UML Unified Modelling Language (OMG) 5 Conventions This Reco

32、mmendation follows the conventions defined in ITU-T M.3020. Usage of ProxyClass: a ProxyClass is a stereotype in UML repertoire described in ITU-T M.3020, which can be used to represent other IOCs listed in the Note under the corresponding UML diagram. Rec. ITU-T M.3704 (01/2010) 3 6 Requirements 6.

33、1 Concepts and background The purpose for performance measurement is for the agent to provide functions to the manager to collect performance measurement data, and to monitor these collected measurement data by setting pre-defined thresholds, so that notifications can be generated and sent from the

34、EMs or NEs to the NM in time. In this Recommendation, the function for collecting performance measurement against network elements is achieved through creating measurement jobs, which can be used to specify the network entities to be measured, the corresponding performance parameters to be collected

35、 against them, and to control the generation of performance measurement data. The detailed performance measurement data will be generated into data files and transferred to the manager periodically. The monitoring of performance data is achieved from setting up threshold monitors, which can scan the

36、 collected measurement data against pre-defined thresholds on certain performance parameters, and threshold-crossing alarms can be generated and sent to the manager for processing. 6.2 Business-level requirements 6.2.1 Requirements Performance measurement is one of the key functions of the network m

37、anagement interface. The manager should be able to request an agent to take measurements on the performance of certain network resources. The performance management requirements can be grouped into one of the following categories: Management of network performance measurements, e.g., create measurem

38、ent job, suspend measurement job, resume measurement job, query measurement job, stop measurement job, delete measurement job, etc. Management of PM threshold-cross monitoring, e.g., create threshold monitor, delete threshold monitor, query threshold monitor, modify threshold monitor, suspend notifi

39、cation monitor, resume notification monitor, threshold-crossing alarm report, etc. Management of measurement files, e.g., performance data file preparation report, performance data file transfer, etc. 6.2.1.1 Management of network performance measurements The manager shall be able to request the age

40、nt to: REQ-PM-FUN-01 Collect specific performance measurements on specific network resources. The network resources, whose performance measurements are to be managed or collected, must have been modelled and must be visible via the management interface. REQ-PM-FUN-02 Collect the performance measurem

41、ents in a file. The data format of this file will depend on the network technology being measured. REQ-PM-FUN-03 Emit a notification announcing the availability of file(s) in REQ-PM-FUN-02. REQ-PM-FUN-04 Create a measurement job. REQ-PM-FUN-05 Suspend a running or scheduled measurement job. REQ-PM-F

42、UN-06 Resume a running or scheduled measurement job. REQ-PM-FUN-07 Stop a running or scheduled measurement job. 4 Rec. ITU-T M.3704 (01/2010) REQ-PM-FUN-08 Query the information and running status of one or more measurement jobs. REQ-PM-FUN-09 Remove a measurement job. This means the complete set of

43、 the PM data files related to this measurement file can be removed from the IRP agent. REQ-PM-FUN-10 Define a measurement job schedule, including the definition of the recording interval(s), job start time and job stop time. It is noted that the agent can only derive or determine the value of a perf

44、ormance measurement at the end of a granularity period. The agent may also have to reset the value of a performance measurement at the beginning of a granularity period. The above agent behaviours are dependent on the nature of the performance measurement types (cumulative counter, gauge). 6.2.1.2 M

45、anagement of PM threshold monitoring The manager shall be able to request the agent to: REQ-PM-FUN-11 Set threshold values to specific performance measurements of specific network resources. REQ-PM-FUN-12 Query the threshold values that are set to specific performance measurements of specific networ

46、k resources. REQ-PM-FUN-13 Modify the threshold values that are set to specific performance measurements of specific network resources. REQ-PM-FUN-14 Suspend a threshold monitor on specific network resources. REQ-PM-FUN-15 Resume a threshold monitor on specific network resources. REQ-PM-FUN-16 Remov

47、e a threshold monitor on specific network resources. REQ-PM-FUN-17 Emit an alarm notification (including clearing) when the threshold value(s) have been crossed and not just reached, as defined in ITU-T Q.822. The manager shall be able to: REQ-PM-FUN-18 Subscribe to notifications that carry threshol

48、d-cross alarms and information on the availability of performance measurement data files. 6.2.1.3 Management of measurement files The agent shall be able to allow the manager to: REQ-PM-FUN-19 Manage the transfer of data files containing performance measurement data. REQ-PM-FUN-20 Request a list of

49、available files, including the specification of filter. 6.2.2 Actor roles The capabilities described in this Recommendation are available and relevant to all agents and managers. 6.2.3 Telecommunication resources The performance management functionality is applicable to all types of telecommunication resources. 6.2.4 High-level use case diagrams The performance management function set contains: Performance measurement management function set, performance threshold management function