1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Q.822.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 1(03/2003) SERIES Q: SWITCHING AND SIGNALLING Q3 interface CORBA-based TMN performance management service Amendment 1: Generic transport performance management ITU-T Recommendation Q.822.1 (
2、2001) Amendment 1ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.1
3、00Q.119 SPECIFICATIONS OF SIGNALLING SYSTEM No. 4 Q.120Q.139 SPECIFICATIONS OF SIGNALLING SYSTEM No. 5 Q.140Q.199 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 Q.250Q.309 SPECIFICATIONS OF SIGNALLING SYSTEM R1 Q.310Q.399 SPECIFICATIONS OF SIGNALLING SYSTEM R2 Q.400Q.499 DIGITAL EXCHANGES Q.500Q.599 INTE
4、RWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.169
5、9 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. Q.822.1 (2001)/Amd.1 (03/2003)
6、i ITU-T Recommendation Q.822.1 CORBA-based TMN performance management service Amendment 1 Generic transport performance management Summary This amendment provides a new object class that can be used to represent Performance Management data for a physical port or endpoints of transport connections. T
7、his new Generic Transport PM object class is intended to be applicable across different technologies, architectures and services. The IDL model describes the new GenericTransportPmCD object class and all the interfaces associated with it. Source Amendment 1 to ITU-T Recommendation Q.822.1 (2001) was
8、 prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 March 2003. ii ITU-T Rec. Q.822.1 (2001)/Amd.1 (03/2003) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU
9、 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 a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardiza
10、tion 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 Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information techn
11、ology 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 “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLEC
12、TUAL 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 Intellectual Property Rights, wheth
13、er 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 Recommendation. However, implementors are cau
14、tioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2003 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Q.822.1 (2001)/
15、Amd.1 (03/2003) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Overview of the Generic Transport PM Data information model 1 4 Information model IDL. 3 4.1 Forward declarations 4 4.2 Structures and typedefs. 4 4.3 Exceptions for conditional packages 4 4.4 Interfaces Fine-grained 4 4.5 Interfaces Faad
16、e. 12 4.6 Name binding . 15 ITU-T Rec. Q.822.1 (2001)/Amd.1 (03/2003) 1 ITU-T Recommendation Q.822.1 CORBA-based TMN performance management service Amendment 1 Generic transport performance management 1 Scope This amendment provides a new object class that can be used to represent Performance Manage
17、ment data for a physical port or endpoints of transport connections. This new Generic Transport PM object class is intended to be applicable across different technologies, architectures and services. The IDL model describes the new GenericTransportPmCD object class and all the interfaces associated
18、with it. 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 t
19、o 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 withi
20、n this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. 1 ITU-T Recommendation Q.816 (2001), CORBA-based TMN services. 2 ITU-T Recommendation Q.816.1 (2001), CORBA-based TMN services: Extensions to support coarse-grained interfaces. 3 ITU-T Recommendation X
21、.780 (2001), TMN guidelines for defining CORBA managed objects. 4 ITU-T Recommendation X.780.1 (2001), TMN guidelines for defining coarse-grained CORBA managed object interfaces. 5 ITU-T Recommendation M.3100 (1995), Generic network information model, plus Amendment 2 (2000). 6 ITU-T Recommendation
22、Q.822.1 (2001), CORBA-based TMN performance management service. 7 ANSI Standard T1.231-1997, Digital Hierarchy Layer 1 in-Service Digital Transmission Performance Monitoring. 3 Overview of the Generic Transport PM Data information model This amendment provides the definition of a new Generic Transpo
23、rt PM Data object class. This new object class is used for collection of performance data related to the GenericTransportTTP (the termination of a generic transport connection). GenericTransportPmCDValueType and GenericTransportPmHDValueType contain placeholders for current and history data values f
24、or counters within the physical transport protocol monitoring grouping. 2 ITU-T Rec. Q.822.1 (2001)/Amd.1 (03/2003) The GenericTransportPmCD object class is subclassed from the CurrentData object class defined in ITU-T Recs Q.822 and Q.822.1. Inherited methods from CurrentData provide for retrieval
25、of the SuspectFlag, retrieval of the ElapsedTime, activating or deactivating HistoryRetention, associating threshold data with a current data instance, and activating or deactivating the suppression of counters having all-zero counts. Additional inherited methods from Scanner provide for the setting
26、 of AdministrativeState, retrieval of OperationalState, and setting of Granularity Period. Similarly, GenericTransportPmHD is subclassed from the HistoryData. For some digital signals, performance primitives in the incoming direction are reported to the far-end via special messages embedded within t
27、he signal format. Examples include: the Performance Report Message (PRM) in DS1 ESF, Far-End Block Error (FEBE) indicators in DS3 CC-bit applications, and Remote Error Indicators (REI) in SDH. With such a capability built into a transmission signal, reporting of transmission performance parameters o
28、bserved at the far-end can be provided at the near-end. For this reason, the managed entity used to hold Generic Transport TTP performance management data contains placeholders for both near-end and far-end data. The GenericTransportPmCD object attributes are arranged into six packages: near-end pat
29、h, near-end line, near-end section, far-end path, far-end line, and far-end section. Only the near-end path package attributes are mandatory. Other packages may be used whenever they are deemed relevant to the underlying transport technology being modelled. Clause 4 defines a set of CORBA IDL interf
30、aces for the GenericTransportPmCD and GenericTransportPmHD objects. These interfaces are specified following the TMN CORBA framework and guidelines given in ITU-T Recs Q.816 and X.780 for fine-grained CORBA interface. In addition to the fine-grained interfaces in 4.4, a companion set of Faade interf
31、aces are defined in 4.5. These faade interfaces are defined according to the coarse-grained framework and guidelines given in ITU-T Recs Q.816.1 and X.780.1 for supporting coarse-grained CORBA interface. The name of these faade interfaces is the name of the corresponding fine-grained interface appen
32、ded with “_F“ (an underscore followed by a capital “F“). This amendment IDL is an integral part of ITU-T Rec. Q.822.1. This implies that all definitions (object classes, type, structure, .) defined in ITU-T Rec. Q.822.1 are in the same IDL module and can be referenced without the module identifier.
33、The IDL in this amendment has been compiled successfully without syntax error. The compiler used claims CORBA 2.3 compliance, which includes value type and M4 macro capabilities. Figures 1 and 2 show the inheritance, containment, and association relationships of the CORBA interfaces defined in this
34、amendment. Note that faade interfaces follow the same inheritance hierarchy relationship as the corresponding fine-grained interfaces. Q.822.1AMD.1_F01itut_q822d1:CurrentDataitut_q822d1:GenericTransportPmCDFigure 1/Q.822.1/Amd.1 Inheritance relationship ITU-T Rec. Q.822.1 (2001)/Amd.1 (03/2003) 3 Q.
35、822.1AMD.1_F02portAssociationListportAssociationListclientLinkEndPointerListserverTTPitut_m3120:CircuitPackitut_m3120:ManagedElementsuperiorSubclasssubordinateSubclassmanagerCreatableitut_m3120:GenericTransportTTPsuperiorSubclasssubordinateSubclassmanagerCreatableitut_m3120:LinkEnditut_q822d1:Generi
36、cTransportPmCDFigure 2/Q.822.1/Amd.1 Containment and association relationships 4 Information model IDL #ifndef _itut_q822d1_amd1_idl_ #define _itut_q822d1_amd1_idl_ #include #pragma prefix “itu.int“ /* This IDL code is intended to be stored in a file named “itut_q822d1_amd1.idl“ located in the searc
37、h path used by IDL compilers on your system. The Q.822.1 main module (defined in ITU-T Rec. Q.822.1) is contained in a separate file named “itut_q822d1.idl“ */ /* This fragment is added to the module, itut_q822d1, which contains IDL definition based on objects defined in ITU-T Rec. Q.822. */ module
38、itut_q822d1 /* 4 ITU-T Rec. Q.822.1 (2001)/Amd.1 (03/2003) 4.1 Forward declarations */ /* Interface forward declarations */ interface GenericTransportPmCD; /* Valuetype forward declarations */ valuetype GenericTransportPmCDValueType; valuetype GenericTransportTTPHDValueType; /* Typedefs forward decl
39、arations */ typedef MONameType GenericTransportPmCDNameType; /* 4.2 Structures and typedefs No new structures are defined in this amendment. */ /* 4.3 Exceptions for conditional packages */ exception NOfarEndLinePMDataPackage ; exception NOfarEndPathPMDataPackage ; exception NOfarEndSectionPMDataPac
40、kage ; exception NOnearEndLinePMDataPackage ; exception NOnearEndSectionPMDataPackage ; /* 4.4 Interfaces Fine-grained */ /* 4.4.1 GenericTransportPmCD (Physical Transport Performance Monitoring Current Data) This object retrieves attributes or current and history data counter values for counters wi
41、thin the Physical Transport Protocol Monitoring grouping. Additional inherited methods from Scanner provide for the setting of AdministrativeState, retrieval of OperationalState, and setting of Granularity Period. Inherited methods from CurrentData provide for retrieval of the SuspectFlag, retrieval
42、 of the ElapsedTime, activating or deactivating HistoryRetention, associating threshold data with a current data instance, and activating or deactivating the suppression of counters having all-zero counts. Applicable methods from Scanner include: administrativeStateGet, administrativeStateSet, opera
43、tionalStateGet, granularityPeriodGet, and granularityPeriodSet. ITU-T Rec. Q.822.1 (2001)/Amd.1 (03/2003) 5 Applicable methods from CurrentData include: suspectIntervalFlagGet, suspectIntervalFlagDefaultSet, elapsedTimeGet, historyRetentionGet, historyRetentionSet, thresholdDataInstanceListGet, thre
44、sholdDataInstanceListSet, getMostRecent, getBetween, numSuppressedIntervalsGet, maxSuppressedIntervalsGet, maxSuppressedIntervalsSet. This object should support the following notifications: objectCreation, objectDeletion, attributeValueChange, and stateChange. A Threshold Crossing Alert (qualityOfSe
45、rviceAlarm) is used to notify the management system when any of the performance parameters exceeds a pre-set threshold described in the associated ThresholdData object. A containment relationship exists between a GenericTransportTTP and its associated GenericTransportPmCD object. */ valuetype Generi
46、cTransportPmCDValueType: truncatable itut_q822d1:CurrentDataValueType /* The codingViolationsPath parameter is used as a count of certain error events occurring in the accumulation period. Sample error events include Frame Synchronization and CRC errors for DS1 links, or P-bit and CP-bit parity erro
47、rs for DS3 links. */ public unsigned long codingViolationsPath; / GET /* The erroredSecondsPath parameter is a count of 1-second intervals containing path errors. Sample path errors include CRC-6 errors (DS1), Severely-Errored Frame defects (DS1/DS3), and P-bit Parity errors (DS3). */ public unsigne
48、d long erroredSecondsPath; / GET /* The severelyErroredSecondspath parameter is a count of 1-second intervals with X or more path error events, or one or more Loss of Signal defect. */ public unsigned long severelyErroredSecondsPath; / GET /* The unavailableSecondsPath parameter is a count of 1-seco
49、nd intervals during which the path is unavailable. */ public unsigned long unavailableSecondsPath; / GET public unsigned long failureCounterPath; / GET public unsigned long farEndCodingViolationsPath; / GET / farEndPathPMDataPackage / Conditional, present if the instance supports it public unsigned long farEndErroredSecondsPath; / GET / farEndPathPMDataPackage / Conditional, present if the instance supports it public unsigned long farEndSeverelyErroredSecondsPath; / GET / farEndPathPMDa
