1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T M.3120TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 2(03/2003) 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 2 ITU-T Recommendation M.3120 (2001) Amendment 2 ITU-T M-SERIES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Introduction and gener
3、al 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 International leased g
4、roup 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 exchange M.1400M.1999 Inter
5、national 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 (2001)/Amd.2 (03/2003)
6、 i ITU-T Recommendation M.3120 CORBA generic network and network element level information model Amendment 2 Summary This amendment provides several enhancements to the CORBA generic network and network element level information model. First, it details a mechanism that supports reporting attribute
7、value ranges across the CORBA interface. Second, it defines a new Generic Transport TTP object class which is intended to represent a physical port or endpoints of transport connections. Third, it defines a new object class, ManagedElementR2, a subclass of ManagedElement with three additional attrib
8、utes added. These attributes include one to hold the “model code“ of a piece of equipment. Another new attribute is used to represent network element aliases, or names used by the EMS to refer to Network Elements. Also defined is an attribute to hold the generic “type“ of a network element. Another
9、enhancement included in this amendment relates to expanding the CharacteristicInfo constants module so that it can adequately represent as much of the currently available signal rates as possible. Source Amendment 2 to ITU-T Recommendation M.3120 (2001) was prepared by ITU-T Study Group 4 (2001-2004
10、) and approved under the WTSA Resolution 1 procedure on 29 March 2003. ii ITU-T Rec. M.3120 (2001)/Amd.2 (03/2003) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (I
11、TU-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 Standardization Assembly (WTSA), which meets every four
12、 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 technology which fall within ITU-Ts purview, the
13、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. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to
14、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, whether asserted by ITU members or others outside
15、 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 cautioned that this may not represent the lates
16、t 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. M.3120 (2001)/Amd.2 (03/2003) iii CONTENTS Page 1 Scope 1 2
17、 References. 1 3 Definitions 2 4 Abbreviations 2 5 Conventions 2 6 Overview of attribute value ranges. 2 7 Overview of the generic transport TTP 5 8 Enhancements to ManagedElement object class 6 8.1 Model code . 7 8.2 Network element aliases. 7 8.3 Network element type. 7 9 Expansion of characterist
18、ic information. 7 10 Information model 8 10.1 Structures and TypeDefs 8 10.2 Interfaces Fine-grained 10 10.3 Interfaces Faade. 16 10.4 Name binding . 19 ITU-T Rec. M.3120 (2001)/Amd.2 (03/2003) 1 ITU-T Recommendation M.3120 CORBA generic network and network element level information model Amendment
19、2 1 Scope This amendment provides several enhancements to the CORBA generic network and network element level information model. First, it details a mechanism that supports reporting attribute value ranges across the CORBA interface. Second, it defines a new Generic Transport TTP object class which
20、is intended to represent a physical port or endpoints of transport connections. Third, it defines a new object class, ManagedElementR2, a subclass of ManagedElement with three additional attributes added. These attributes include one to hold the “model code“ of a piece of equipment. Another new attr
21、ibute is used to represent network element aliases, or names used by the EMS to refer to Network Elements. Also defined is an attribute to hold the generic “type“ of a network element. Another enhancement included in this amendment relates to expanding the CharacteristicInfo constants module so that
22、 it can adequately represent as much of the currently available signal rates as possible. 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 edit
23、ions 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 most recent edition of the Recommendations and other references listed below. A list of the currently vali
24、d 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. 1 ITU-T Recommendation Q.816 (2001), CORBA-Based TMN Services. 2 ITU-T Recommendation Q.816.1 (2001), CORBA-Based TMN Se
25、rvices Extensions to Support Coarse-Grained Interfaces. 3 ITU-T Recommendation X.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 Objects. 5 ITU-T Recommendation M.3120 (2001), CORBA Generic
26、 Network and NE Level Information Model. 6 ITU-T Recommendation M.3100 (1995), Generic Network Information Model plus Amendment 1 (1999). 7 ITU-T Recommendation Q.822.1 (2001), Coarse-Grained CORBA Generic Network and NE Level Information Model. 8 ANSI Standard T1.231.1997 (1997), Digital Hierarchy
27、Layer 1 In-Service Digital Transmission Performance Monitoring. 2 ITU-T Rec. M.3120 (2001)/Amd.2 (03/2003) 3 Definitions This amendment has no new definitions in addition to those found in the main Recommendation. 4 Abbreviations This amendment has no new abbreviations in addition to those found in
28、the main Recommendation. 5 Conventions This amendment has no new conventions in addition to those found in the main Recommendation. 6 Overview of attribute value ranges This clause provides a mechanism that allows managed systems using the M.3120 paradigm, to automatically report acceptable value ra
29、nges for attributes associated with a network element in the model. Such mechanism would be a valuable asset for equipment discovery and configuration, since a managing system would automatically be aware of the acceptable value ranges for each configurable parameter in the network before attempting
30、 to set these values. For this mechanism to be implemented, we define a new AttributeRanges object class. The AttributeRanges class allows the managed system to report the minimum and maximum values a certain attribute accepts, as well as the granularity, or step increments, of the range. Each Attri
31、buteRanges instance contains ranges for attributes belonging to one object class. The “kind“ attribute in AttributeRanges denotes the object class for which ranges are being defined. “attributeName“ specifies the name of the attribute for which a range is being defined. The range is then defined usi
32、ng the “minimum“, “maximum“, and “granularity“ attributes. “granularity“ is not needed for attributes containing floating numbers. For each ManagedElement instance representing a network element, one or more AttributeRanges instances may be created. AttributeRanges instances are bound to the Managed
33、Element instance via a containment relationship. Ranges are defined per ManagedElement instance. This allows for an attribute to have different ranges when it belongs to different network elements. In other words, the scope of each AttributeRanges instance is the relevant objects associated with the
34、 ManagedElement which contains the AttributeRanges instance. Figure 1 illustrates the scoping concept more clearly. In the figure, we see two different instances of ManagedElement (A and B). Contained under ManagedElement A are two AttributeRanges instances named A and B. Similarly, contained under
35、ManagedElement B are two other AttributeRanges instances named C and D. AttributeRanges A defines ranges for all AalProfileTypeOne instances associated with ManagedElementA, while AttributeRanges C defines ranges for AalProfileTypeOne instances associated with ManagedElement B. Similarly, AttributeR
36、anges B defines ranges for all CesServiceProfile instances associated with ManagedElementA, and AttributeRanges D defines ranges for CesServiceProfile instances associated with ManagedElement B. In other words, the managed system instantiates one AttributeRanges instance (portrayed as a table in the
37、 figure) per class per Managed Element instance. Hence, if the managing system needs to modify the parameters of an AalProfileTypeOne instance associated with ManagedElement A (such as the instance ProfileA in the figure), it can query AttributeRanges A before modifying the values. In order to set r
38、anges for attributes defined inside data structures, the dot notation is used. For instance, consider the following data structure: ITU-T Rec. M.3120 (2001)/Amd.2 (03/2003) 3 struct SampleStructureType long xyx, long abc, float def ; In order to set an attribute range on attribute xyz, we may refer
39、to attribute xyz by setting the attributeName attribute in AttributeRangeType to “SampleStructureType.xyz“. Clause 10.2.1 defines a set of CORBA IDL interfaces for the attribute value ranges information model. These interfaces are translated manually from a set of Amendment 7/M.3100 GDMO managed obj
40、ect classes 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 interface in clause 10.2.1, a companion Facade interface is defined in clause 10.3.1. This facade interface is defined according to the c
41、oarse-grained framework and guidelines given in Q.816.1 and X.780.1 for supporting coarse-grained CORBA interfaces. The name of this facade interface is the name of the corresponding fine-grained interface appended with “_F“ (an underscore followed by a capital “F“). Figure 2 and Figure 3 show the i
42、nheritance and containment relationship of the CORBA interfaces defined in this clause. Note that facade interfaces follow the same inheritance hierarchy relationship as the corresponding fine-grained interfaces. 4 ITU-T Rec. M.3120 (2001)/Amd.2 (03/2003) M.3120AMD.2_F01ManagedElement AAttributeRang
43、es Akind: atmf_m4nw_v2:AalProfileTypeOne150001086553516cbrRate11001attributeName:cellLossIntegrationPeriodPartiallyFilledCellsgranularity:maximum:minimum:kind:ManagedElement BAttributeRanges Catmf_m4nw_v2:AalProfileTypeOnegranularity:maximum:minimum:attributeName:44000100163276764cbrRate1601cellLoss
44、IntegrationPeriodPartiallyFilledCells416383256CesBufferedCDVTolerancekind:granularity:maximum:minimum:attributeName:AttributeRanges Datmf_m4nw_v2:CesServiceProfileAalProfileTypeOne ProfileCCesServiceProfile ProfileDContainmentAssociationCbrRate: 128CellLossIntegration Period: 2000PartiallyFilledCell
45、s: 20CesBufferedCDVTolerance: 8192CesServiceProfile ProfileBCesBufferedCDVTolerance: 16384AalProfileTypeOne ProfileAPartiallyFilledCells: 40CellLossIntegration Period: 1000CbrRate: 3286553516CesBufferedCDVTolerancekind:granularity:maximum:minimum:attributeNameAttributeRanges Batmf_m4nw_v2:CesService
46、ProfileFigure 1/M.3120/Amd.2 Instance diagram portraying the use of AttributeRanges ITU-T Rec. M.3120 (2001)/Amd.2 (03/2003) 5 M.3120AMD.2_F02itut_x780:ManagedObject nameGet()objectClassGet()packagesGet()creationSourceGet()deletePolicyGet()attributesGet()destroy() attributesBulkGet()itut_m3120:Attri
47、buteRangeskindGet()rangesGet()Figure 2/M.3120/Amd.2 Attribute value ranges inheritance relationship M.3120AMD.2_F03itut_m3120:ManagedElementsuperiorSubclasssubordinateSubclassmanagerCreatableitut_m3120:AttributeRangesFigure 3/M.3120/Amd.2 Attribute value ranges containment relationship 7 Overview of
48、 the generic transport TTP This clause defines a new Generic Transport TTP object class. This new object is used to represent a physical port or endpoints of transport connections. It may be used by technology-specific models as an abstraction of an underlying transport layer. A new GenericTransport
49、TTP interface is defined. This object is a subclass of NetworkTP. It is related to ManagedElement using a containment relationship. It is associated with CircuitPack using the PortAssociationList attribute, and with LinkEnd using the ClientLinkEndPointerList attribute. Clause 10.2.2 defines a set of CORBA IDL interfaces for the GenericTransportTTP and GenericTransportPmCD object classes. These interfaces are translated manually from a set of Amendment 8/M.3100 GDMO managed object classes following the TMN CORBA framework and guideli
