1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T M.3120TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 1(05/2002) SERIES M: TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Telecommunications management network CORBA
2、 generic network and network element level information model Amendment 1: Protection switching ITU-T Recommendation M.3120 (2001) Amendment 1 ITU-T M-SERIES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS
3、Introduction and general principles of maintenance and maintenance organization M.10M.299 International transmission systems M.300M.559 International telephone circuits M.560M.759 Common channel signalling systems M.760M.799 International telegraph systems and phototelegraph transmission M.800M.899
4、International leased group and supergroup links M.900M.999 International leased circuits M.1000M.1099 Mobile telecommunication systems and services M.1100M.1199 International public telephone network M.1200M.1299 International data transmission systems M.1300M.1399 Designations and information excha
5、nge M.1400M.1999 International transport network M.2000M.2999 Telecommunications management network M.3000M.3599 Integrated services digital networks M.3600M.3999 Common channel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. M.3120
6、(2001)/Amd.1 (05/2002) i ITU-T Recommendation M.3120 CORBA generic network and network element level information model Amendment 1 Protection switching Summary This amendment provides protection switching enhancements to the generic network information model. The model describes protection switching
7、 managed object classes and their properties that are generic and useful to describe information exchanged across all interfaces defined in M.3010 TMN architecture. These generic managed object classes are intended to be applicable across different technologies, architectures and services. The prote
8、ction switching managed object classes in this amendment may be specialized to support the management of various telecommunications networks. Source Amendment 1 to ITU-T Recommendation M.3120 (2001) was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on
9、 29 May 2002. ii ITU-T Rec. M.3120 (2001)/Amd.1 (05/2002) FOREWORD The International Telecommunication 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 f
10、or 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, establishes the topics for study by the ITU-T stu
11、dy 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 standards are prepared on a collaborative basis
12、 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. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of th
13、is 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, whether asserted by ITU members or others outside of the Recommendation development process. As of the dat
14、e 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 cautioned that this may not represent the latest information and are therefore strongly urged to consult
15、 the TSB patent database. ITU 2002 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. M.3120 (2001)/Amd.1 (05/2002) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Overview of the protection switching inf
16、ormation model 1 4 Information Model IDL 3 4.1 Imports 4 4.2 Forward Declarations . 4 4.3 Structures and Typedefs . 5 4.4 Exceptions 11 4.4.1 Exceptions and Constants for Conditional Package. 11 4.5 Interfaces Fine-grained 12 4.5.1 ProtectionGroup . 12 4.5.2 ProtectionUnit. 16 4.6 Interfaces Faade.
17、19 4.6.1 ProtectionGroup_F . 19 4.6.2 ProtectionUnit_F 21 4.7 Notifications . 21 4.8 Name Binding. 22 4.8.1 ProtectionGroup . 22 4.8.2 ProtectionUnit. 23 4.9 ProbableCauseConst. 23 ITU-T Rec. M.3120 (2001)/Amd.1 (05/2002) 1 ITU-T Recommendation M.3120 CORBA generic network and network element level
18、information model Amendment 1 Protection switching 1 Scope This amendment provides protection switching model enhancements to the CORBA generic network and NE level information model. The IDL model describers protection switching managed object classes and their properties that are generic and usefu
19、l to describe information exchanged across all interfaces defined in M.3010 TMN architecture. These generic protection switching object classes are intended to be applicable across different technologies, architectures and services. They can be extended by various telecommunication industries for ma
20、naging specific network technologies, such as ATM, SONET/SDH and Ethernet. 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
21、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 most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recomme
22、ndations is regularly published. 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.780 (2001), TMN Guidelines for defining CORBA managed objects. 4
23、ITU-T Recommendation X.780.1 (2001), TMN Guidelines for defining coarse-grained CORBA managed objects interfaces. 5 ITU-T Recommendation M.3120 (2001), CORBA generic network and network element level information model. 6 ITU-T Recommendation M.3100 (1995), Generic network information model, plus Ame
24、ndment 2 (2000). 7 ITU-T Recommendation G.774 (2001), Synchronous digital hierarchy (SDH) management information model for the network element view. 8 ITU-T Recommendation G.774.3 (2001), Synchronous digital hierarchy (SDH) management of multiplex-section protection for the network element view. 3 O
25、verview of the protection switching information model Clause 4 defines a set of CORBA IDL interfaces for the protecting switching information model. These interfaces are translated manually from a set of ITU-T Recs. M.3100 Amendment 2 and G.774.3 GDMO managed object classes following the TMN CORBA f
26、ramework and guidelines given in ITU-T Recs. Q.816 and X.780 for fine-grained CORBA interface. 2 ITU-T Rec. M.3120 (2001)/Amd.1 (05/2002) In addition to the fine-grained interfaces in 4.5, a companion set of Faade interfaces are defined in 5.6. These faade interfaces are defined according to the coa
27、rse-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 are the names of the corresponding fine-grained interfaces appended with “_F“ (an underscore followed by a capital “F“). This amendment IDL
28、is an integral part of ITU-T Rec. M.3120. This implies that all definitions (object classes, type, structure, etc.) defined in ITU-T Rec. M.3120 are in the same IDL module and can be referenced without the module identifier. The IDL in this amendment has been compiled successfully without syntax err
29、or. 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 relationship of the CORBA interfaces defined in this Recommendation. Note that faade interfaces follow the same inheritance hiera
30、rchy relationship as the corresponding fine-grained interfaces. It should also be noted that additional interfaces, although required, are not shown in the figures. Examples are the factory classes. T0417290-02itut_x780:ManagedObject nameGet()objectClassGet()packagesGet()creationSourceGet()deletePol
31、icyGet()attributesGet()destroy() attributesBulkGet()itut_m3120:ProtectionGroupitut_m3120:ProtectionUnitoperationStateGet()availabilityStatusGet()supportedByObjectListGet()groupTypeGet/Set()revertiveGet/Set()waitToRestoreTimeGet/Set()lockedInConditionGet/Set()currentProblemListGet()invokeProtection()
32、releaseProtection()protectingGet()reliableResourceListGet()unreliableResourceListGet()protectionStatusGet()priorityGet/Set()Figure 1/M.3120 Inheritance relationship ITU-T Rec. M.3120 (2001)/Amd.1 (05/2002) 3 T0417300-02unreliableResourceListreliableResourceListitut_m3120:ManagedElementsuperiorSubcla
33、sssubordinateSubclassmanagerCreatableitut_m3120:ProtectionGroupsuperiorSubclasssubordinateSubclassmanagerCreatableitut_m3120:ProtectionUnititut_x780:ManagedObjectFigure 2/M.3120 Containment and association relationship 4 Information Model IDL #ifndef _itut_m3120_amd1_idl_ #define _itut_m3120_amd1_id
34、l_ #include #pragma prefix “itu.int“ /* This IDL code is intended to be stored in a file named “itut_m3120_amd1.idl“ located in the search path used by IDL compilers on your system. The M.3120 main module (defined in M.3120) is contained in a separate file named “itut_m3120.idl“ */ /* 4 ITU-T Rec. M
35、.3120 (2001)/Amd.1 (05/2002) This fragment is added to the module, itut_m3120, which contains IDL definition based on objects defined in M.3100 and G.855.1. */ module itut_m3120 /* 4.1 Imports */ /* Types imported from itut_x780 */ typedef itut_x780:AdditionalTextType AdditionalTextType; typedef itu
36、t_x780:AdditionalInformationSetType AdditionalInformationSetType; typedef itut_x780:CorrelatedNotificationSetType CorrelatedNotificationSetType; typedef itut_x780:NotifIDType NotifIDType; typedef itut_x780:NullType NullType; /* 4.2 Forward Declarations */ /* Interface forward declarations */ interfa
37、ce ProtectionGroup; interface ProtectionUnit; /* Valuetype forward declarations */ valuetype ProtectionGroupValueType; valuetype ProtectionUnitValueType; /* Typedefs forward declarations */ typedef MONameType ProtectionGroupNameType; typedef MONameType ProtectionUnitNameType; /* ITU-T Rec. M.3120 (2
38、001)/Amd.1 (05/2002) 5 4.3 Structures and Typedefs Structures and typedefs defined in the following are arranged in alphanumeric order. */ typedef sequence ProtectionGroupNameSetType; typedef sequence ProtectionGroupNameSeqType; typedef sequence ProtectionUnitNameSetType; typedef sequence Protection
39、UnitNameSeqType; /* This attribute specifies the criteria of the locked-in condition. The criteria includes the automatic protection switching (APS) rate and the associated setting and releasing time windows. If the number of APS of a Protection Unit reaches the value specified in the hitsCount fiel
40、d within a moving time window of specified length, the Protection Unit will enter the locked-in condition. Each switch to protection and its subsequent release is considered as one hit. The length of the time window for entering the locked-in condition is specified in the settingWindowTime field. On
41、ce a Protection Unit is in the locked-in condition, future request of APS will be denied until the locked-in condition is released. The release criterion is no APS request within another moving time window. The length of this time window is specified in the releasingWindowTime field. */ struct Locke
42、dInConditionType unsigned short settingWindowTime; unsigned short releaseingWindowTime; unsigned short hitsCount; ; enum ProtectionDirectionType protectionDirectionTransmit, protectionDirectionReceive, protectionDirectionBidirectional ; enum ProtectionGroupType protectionGroupPlus, / 1+1 or hot-stan
43、dby protectionGroupColon / M:N ; /* The Protection Status attribute indicates the status of the protection switch in an Protection Unit object. The following behaviour applies to this attribute: This attribute must be capable of indicating pending as well as active switching requests relative to the
44、 protection unit. However, only one of the values lockout, forced switch, or manual switch can be present at the same time. A protection system may support only a subset of the allowable values of this attribute. The subset of values to be supported by a system is implementation-specific. The syntax
45、 of this attribute includes a sub-field “relatedUnit“ which is of union of “fromProtectionUnitNumber“ and “toProtectionUnitNumber“. This sub-field is used to indicate on which unit the service is carried. 6 ITU-T Rec. M.3120 (2001)/Amd.1 (05/2002) For a protected PU, both the fromProtectionUnit and
46、the toProtectionUnit hold the ID of the related protecting PU. When switching to the protecting PU (i.e. service will be carried by the protecting PU), the toProtectionUnit choice is used. When switching back to the protected PU (service will be carried by the protected PU), the fromProtectionUnit c
47、hoice is used. For a protecting PU, both the fromProtectionUnit and the toProtectionUnit hold the ID of the related protected PU. When switching to the protected PU (i.e. service will be carried by the protected PU), the toProtectionUnit choice is used. When switching to the protecting PU (service w
48、ill be carried by the protecting PU), the fromProtectionUnit choice is used. If a system can support protection switching due to Resource Degrade (RD) besides Resource Fail (RF), protection switching of RD is similar to that in the subsequent description for RF. The following allowable Protection St
49、atus values are associated with each protected Protection Unit (PU). No Request: No switch request is present on the unit. In this case, service is on the protected PU, status syntax is noRequest. For non-revertive system, the status syntax of the related protecting PU is also noRequest. Manual Switch to Protecting Unit Complete: The unit has completed a Manual Switch. In this case, service is on the related protectingPU, status syntax of the protected PU is manualSwitch (switchStatus: completed;
