ITU-T Q 822 1-2001 COBRA-Based TMN Performance Management Service Series Q Switching and Signalling Q3 Interface (Study Group 4)《基于CORBA的TMN性能管理业务-系列Q 交换和信令-Q3接口(第4研究组)》.pdf

《ITU-T Q 822 1-2001 COBRA-Based TMN Performance Management Service Series Q Switching and Signalling Q3 Interface (Study Group 4)《基于CORBA的TMN性能管理业务-系列Q 交换和信令-Q3接口(第4研究组)》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 822 1-2001 COBRA-Based TMN Performance Management Service Series Q Switching and Signalling Q3 Interface (Study Group 4)《基于CORBA的TMN性能管理业务-系列Q 交换和信令-Q3接口(第4研究组)》.pdf（51页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU SERIES Q: SWITCHING AND SIGNALLING Q3 interace Q.822.1 (10/2001) CORBA-based TMN performance management service TU-T Recommendation Q.822.1 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING I

2、N THE INTERNATIONAL MANUAL SERVICE FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF S

3、IGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS General Message transfer part (MTP) Signalling connection control part (SCCP) Telephone user part (TUP) ISDN supplementary services Data user pa

4、rt Signalling System No. 7 management ISDN user part Transaction capabilities application part Test specification 43 INTERFACE DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 General Data link layer Network layer User-network management Stage 3 description for supplementary services using DSSI PUBLIC LAN

5、D MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) BROADBAND ISDN SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q. 1-Q.3 Q.60-Q.99 Q. IOO-Q. 1 19 Q.4-Q.59 Q. 120-Q.249 Q.250-Q.309 Q.3 10-

6、4.399 Q.400-Q.499 Q.500-Q.599 Q.600-Q.699 Q.700-Q.799 Q.700 Q.701-Q.709 4.71 1-Q.719 Q. 720-Q.729 Q.730-Q.739 Q.740-Q.749 Q.750-Q.759 Q.760-Q.769 Q.770-Q.779 Q.800-Q.849 Q.780-4.799 Q .8 5 0-Q .999 Q.850-Q.9 19 Q.920-Q.929 Q.930-Q.939 Q.940-Q.949 Q.1000-Q.1099 Q.1 lOO-Q.1199 Q. 1200-Q. 1699 Q.950-Q.

7、999 Q. 1700-4.1799 Q.1900-Q. 1999 Q.2000-Q.2999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Recommendation Q.822.1 CORBA-based TMN performance management service Summary This Recommendation defines an information model to be used in telecommunications performance ma

8、nagement (PM) based on COMA. It defines in Interface Definition Language (IDL) a set of interfaces, notifications, and constants. The intent of this Recommendation is to define a CORBAIDL model similar to that defined in ITU-T Recs. X.739 and Q.822 using CMISE. This Recommendation is compliant with

9、COMA modelling standards in ITU-T X.780, X.780.1, Q.816, Q.816.1 and M.3120. Source ITU-T Recommendation 4.822.1 was prepared by ITU-T Study Group 4 (200 1-2004) and approved under the WTSA Resolution 1 procedure on 7 October 2001. ITU-T Rec. Q.822.1 (10/2001) 1 FOREWORD The International Telecommun

10、ication Union (ITU) is the United Nations specialized agency in the field of telecommunications. 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 Recommendations on them with

11、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 approval of ITU-T Recomm

12、endations 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 IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for con

13、ciseness to indicate both a telecommunication administration and a recognized operating agency. 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 po

14、sition 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 received notice of intellectual property, pro

15、tected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 2002 All rights reserved. No part of this publication may be re

16、produced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. 11 ITU-T Rec. Q.822.1 (10/2001) CONTENTS Page 1 2 3 4 4.1 4.2 4.3 Scope . References . Abbreviations Overview of the Performance Management Servic

17、e Requirements 4.1.1 Functional Requirements . 4.1.2 Design Requirements . Service Modelling . 4.2.1 Scope . 4.2.2 UML Model . 4.2.3 Containment Relationship . Service Interface Description 4.3.1 Scanner 4.3.2 CurrentData . 4.3.3 ThresholdData . 4.3.4 HistoryDataFile . 4.3.5 AbstractHistoryDataScann

18、er . 4.3.6 ListHistoryDataScanner . 4.3.7 ClassHistoryDataScanner 4.3.8 ScopedFilteredHistoryDataScanner . 5 Performance Management Service IDL . 5.1 Imports 5.2 Forward Declarations 5.3 Structures and Typedefs 5.4 Exceptions . 5.5 Interfaces - Fine-grained 5.5.1 Scanner 5.5.2 CurrentData . 5.5.3 Th

19、resholdData . 5.5.4 HDFile (HistoryDataFile) 5.5.5 AbstractHDScanner (AbstractHistoryDataScanner) . 5.5.6 ListHDScanner 5.5.7 ClassHDScanner 5.5.8 ScopedFilteredHDScanner 5.6 Interfaces - Facade . 5.6.1 Scanner F - 1 1 2 2 2 2 4 4 4 4 8 8 8 9 11 12 13 13 14 15 15 15 16 17 18 18 19 20 23 24 25 26 27

20、28 29 29 . ITU-T Rec . Q.822.1 (10/2001) 111 5.6.2 5.6.3 5.6.4 5.6.5 5.6.6 5.6.7 5.6.8 CurrentData F . . ThresholdData-F . HDFileF (HistoryDataFile) AbstractHDScanner-F (AbstractHistoryDataScanner) . ListHDScanner F . ClassHDScanner-F ScopedFilteredHDScannerF 5.7 Notifications 5.8 Name Binding . 5.8

21、.1 ThresholdData . 5.8.2 HDFile . 5.8.3 AbstractHDScanner . 5.9 HDFileFormatConst Annex A - File Format A . 1 Text File Format BNF . A.2 Text File Format Description Annex B - COMA File Format Convention Appendix I - Example of CurrentDataValueType and HistoryDataValueType inheritance usage . Page 3

22、0 32 33 34 35 35 36 37 37 37 37 38 38 39 39 41 43 43 iv ITU-T Rec . Q.822.1(10/2001) ITU-T Recommendation Q.822.1 CORBA-based TMN performance management service 1 Scope This Recommendation defines a support service to be used in telecommunications performance management (PM) based on CORBA. It defin

23、es in Interface Definition Language (IDL) a set of interfaces in both fine-grained and facade version, data types, and constants. The intent of this Recommendation is to define a CORBNIDL specification similar to that defined in ITU-T Recs. X.739 and Q.822 using CMISE. This Recommendation is complia

24、nt with proposed COBA modelling standards in ITU-T Recs. X.780, X.780.1,Q.816, Q.816.1 and M.3120. 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,

25、 the editions indicated were valid. All Recommendations and other references are subject to revision; all 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 c

26、urrently valid ITU-T Recommendations is regularly published. OMG Document fomal/99- 10-07, The Common Object Request Broker: Architecture and Speczjkation, Revision 2.3.1. OMG Document fonna1/2000-06-20, Notzjkation Service Speczjkation, Version 1 .O. ITU-T Recommendation 4.816 (2001), CORBA-based T

27、MNsewices. ITU-T Recommendation Q.8 16.1 (2001), CORBA-based TkNservices extensions to support coarse-grained interfaces. ITU-T Recommendation X.780 (2001), TMN guidelines for defining CORBA managed objects . ITU-T Recommendation X.780.1 (2001), TMN guidelines for defining coarse-grained CORBA manag

28、ed objects interfaces. ITU-T Recommendation M.3 120 (2001), CORBA Generic Network and NE Level Information Model. ITU-T Recommendation X.72 1 (1 992), Information technology - Open systems interconnection - Structure of management information: Definition of management information. ITU-T Recommendati

29、on X.738 (1 993), Information technology - Open Systems Interconnection - Systems management: Summarization function. ITU-T Recommendation X.739 (1 993), Information technology - Open Systems Interconnection - Systems management: Metric objects and attributes. ITU-T Recommendation 4.822 (1994), Stag

30、e 1, stage 2 and stage 3 description for the Q3 interface - Performance management. ITU-T Recommendation 4.823 (1996), Stage 2 and stage 3 functional speciJications for traffic management. ITU-T Rec Q.822.1 (102001) 1 3 Abbreviations This Recommendation uses the following abbreviations: CMIP Common

31、Management Information Protocol CORBA DN Distinguished Name FDN Fully Distinguished Name GDMO NE Network Element PM Performance Management QOS Quality of Service RDN Relative Distinguished Name SNMP Simple Network Management Protocol TL 1 Transaction Language 1 TMN Telecommunications Management Netw

32、ork UML Unified Modelling Language Common Object Request Broker Architecture Guidelines for the Definition of Managed Objects 4 Overview of the Performance Management Service 4.1 Requirements 4.1.1 Functional Requirements Performance Measurement is used in two ways in TMN. One way is in the measurem

33、ent of the performance of transport and protocol entities. In this use the measurements are subjected to thresholding and are collected for engineering and service. history on a time scale that is not real time critical. This is the use supported by ITU-T Rec. 4.822 and technology-specific standards

34、 directly based on it. The other use of performance measurement is in support of network traffic management. In this application the measurements are not subjected to thresholding, but are collected periodically on a time scale that is needed to support the application of network management controls

35、. The typical time scale for this collection has historically been 5 minutes. This is the use supported by ITU-T Rec. Q.823. ITU-T Rec. 4.823 reuses the mechanisms of ITU-T Rec. 4.822 together with the generic simple scanner of ITU-T Rec. X.738 to produce a single scan report that summarized the pre

36、vious granularity period and is reported to a network management OS. These two uses of performance measurement are summarized in the Use Cases shown in Figure 1. 2 ITU-T Rec 4.822.1 (10/2001) Administer Trafic Report Administer PM Report PM Data / Y Y / Performance Manager / QOS threshold crossed QO

37、S threshold crossed trafic report Report trafic Periodic Report Trafic Monitor Performance TO415900-O2 Figure UQ.822.1- Use cases for performance measurement In summary, the TMN Management functions for performance management include data collection, data storage, thresholding, and data reporting. P

38、erformance data collection refers to the ability for a NE to collect the various PM data relating to a single monitored entity in that NE. This function allows a TMN manager to assign PM data collection interval, to suspendresume PM data collection process, and to reset the performance monitoring co

39、unters. PM data storage refers to the capability for a NE to store historical PM data on each monitored entity for prescribed time duration. This function allows a TMN manager to establish a duration during which to maintain a specific record of PM historical data, to optionally screen historical da

40、ta based on some criteria (e.g. suppress “all-zero“ data), and to remove historical PM data at the end of time interval. PM thresholding refers to the ability for a NE to inform a TMN manager of any threshold crossing. It also provides the TMN manager with the means for establishing thresholding cri

41、teria. PM data reporting refers to the capability for a NE to report PM data on a scheduled basis, or as a result of a spontaneous request from the TMN manager. A report may contain data fi-om a given monitored entity, or it can contain summarized data from a set of monitored entities. This function

42、 allows a TMN manager to request PM data, to allowshnhibits the emission of scheduled reports in the NE, and to screen the PM data reports on some criteria (e.g. suppress “all-zero“ data). 3 ITU-T Rec 4.822.1 (10/2001) 4.1.2 Design Requirements This Recommendation follows the information modelling g

43、uidelines defined in ITU-T Rec. X.780. In addition, this Recommendation tries to keep the model practical, simple and to make sense to users and manufacturers. 4.2 Service Modelling 4.2.1 Scope To support the functional requirements the performance management service needs currentData to collect per

44、formance measurements, historyData to store the collected measurements, thresholdData to specify the thresholds, and some specific scanner to report history data. Since currentData is inherited from Scanner, the model also needs Scanner. However, based on the modelling guidelines and the needs from

45、existing and current PM applications, not all the capabilities defined for these managed objects in ITU-T Recs. X.739 and 4.822 are necessary at this point in time. As a result, some of the optional packages are not included in this model. In the future, if the need for a capability arises, the rele

46、vant package(s) will be reconsidered for inclusion. For most managed objects identified above, their IDL model can be derived from a translation of the X.739 and 4.822 GDMO. For historyData, however, direct translation may result in a potentially large number of managed objects. These entities are r

47、ead only as historical data stores of current data and do not need to be CORBA interfaces. Instead, it is proposed that they be defined as CORBA valuetypes. The Q.822 translation will define a base valuetype for historyData, called HistoryDataValueType. This valuetype HistoryDataValueType will be ac

48、cessible through methods on the CurrentData interface. When a current data is subclassed it is intended that the corresponding HistoryDataValueType be subclassed along with it. Since the data that needs to be stored is not in CORBA interfaces but HistoryDataValueTypes, to report history data, simply

49、 translating the GDMO homogeneous and simple scanners will not work. Instead, a new kind of scanner is needed - one that collects data from the HistoryDataValueTypes. This model attempts to keep the interfaces strongly typed whenever possible. This is because the collection of traffic data is computationally intensive since large amount of data must be collected and processed by the network manager in a short period of time. For this purpose, HistoryDataScanner is designed to retrieve history data saved under the relevant CurrentData objects. A file transfer mechanism is used in Hi