ITU-T G 874 1-2002 Optical transport network (OTN) Protocol-neutral management information model for the network element view Series G Transmission Systems and Media Digital Systemns.pdf

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T G.874.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2002) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital networks Optical transport networks Optical transport network (OTN): Protocol-neutral management information mo

2、del for the network element view ITU-T Recommendation G.874.1 ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS G.100G.199 GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS G.200G.299

3、 INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES G.300G.399 GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES G.400G.449 COORDINATION OF RADIOTELEPHONY AND LINE TELEPHON

4、Y G.450G.499 TESTING EQUIPMENTS G.500G.599 TRANSMISSION MEDIA CHARACTERISTICS G.600G.699 DIGITAL TERMINAL EQUIPMENTS G.700G.799 DIGITAL NETWORKS G.800G.899 General aspects G.800G.809 Design objectives for digital networks G.810G.819 Quality and availability targets G.820G.829 Network capabilities an

5、d functions G.830G.839 SDH network characteristics G.840G.849 Management of transport network G.850G.859 SDH radio and satellite systems integration G.860G.869 Optical transport networks G.870G.879 DIGITAL SECTIONS AND DIGITAL LINE SYSTEM G.900G.999 QUALITY OF SERVICE AND PERFORMANCE G.1000G.1999 TR

6、ANSMISSION MEDIA CHARACTERISTICS G.6000G.6999 DIGITAL TERMINAL EQUIPMENTS G.7000G.7999 DIGITAL NETWORKS G.8000G.8999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. G.874.1 (01/2002) i ITU-T Recommendation G.874.1 Optical transport network (OTN): Protocol-neutral m

7、anagement information model for the network element view Summary This Recommendation provides a protocol-neutral management information model for managing network elements in the optical transport network (OTN). The model contains the managed entities and their properties that are useful to describe

8、 the information exchanged across interfaces defined in the M.3010 telecommunications management network (TMN) architecture. The protocol-neutral management information model shall be used as the base for defining protocol-specific management information models, for example, CMISE, CORBA, and SNMP i

9、nformation models. Mapping from the protocol-neutral entities into protocol-specific objects is a decision of the specific protocol modelling design and should be described in the protocol-specific information model Recommendations. Source ITU-T Recommendation G.874.1 was prepared by ITU-T Study Gro

10、up 15 (2001-2004) and approved under the WTSA Resolution 1 procedure on 6 January 2002. History Version Date Notes 1 6 Jan 2002 Initial version Keywords Optical transport network, Protocol-neutral information model, UML. ii ITU-T Rec. G.874.1 (01/2002) FOREWORD The International Telecommunication Un

11、ion (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 a view to

12、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 Recommendations

13、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 ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness t

14、o 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 position con

15、cerning 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, protected by

16、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. ITU 2002 All rights reserved. No part of this publication may be reproduced, by

17、 any means whatsoever, without the prior written permission of ITU. ITU-T Rec. G.874.1 (01/2002) iii CONTENTS Page 1 Scope 1 2 References 1 3 Terms and Definitions 2 3.1 Definitions from ITU-T Rec. M.3100 2 3.2 Definitions from ITU-T Rec. G.872. 2 3.3 Definitions from ITU-T Rec. G.709/Y.1331 2 3.4 D

18、efinitions from ITU-T Rec. G.798. 2 3.5 Definitions from ITU-T Rec. G.7710/Y.1701 2 4 Abbreviations and Acronyms. 3 5 OTN NE Management Requirements 3 6 Analysis 4 7 Design of the Protocol-neutral Information Model 4 7.1 UML Class Diagram 4 7.1.1 Class Diagram for OTN-Specific Entity 5 7.1.2 Class D

19、iagram for Fault Management Support Entity. 7 7.2 UML Data Dictionary 7 7.2.1 Data Dictionary for OTN Specific Entity 7 7.2.2 Data Dictionary for Fault Management Support Entity. 38 Appendix I Usage of the Model for TCM and GCC 41 I.1 TCM locations 42 I.1.1 TC_Trail between ODUk_CTP Source and ODUk_

20、CTP Sink (Points C and D). 42 I.1.2 TC_Trail between ODUk_CTP Sink and ODUk_CTP Source (Points E and F) 44 I.1.3 TC_Trail between ODUk_TTP Source and ODUk_CTP Source (Points G and H). 45 I.1.4 Two TC_Trail terminations within one ODUk_CTP. 46 I.2 GCC access locations. 48 I.2.1 COMMS channel between

21、two ODUk_TTPs (Points A and B, TT atomic functions are included). 48 I.2.2 COMMS channel between ODUk_CTP and ODUk_TTP (Points C and B(bis) TT atomic function at B(bis) is not included). 50 I.2.3 Several COMMS channels. 52 I.3 GCC access and TCM locations together 54 I.3.1 TC_Trail and COMMS channel

22、 between ODUk_CTP Source and ODUk_CTP Sink (Points C and D) 54 iv ITU-T Rec. G.874.1 (01/2002) Page I.3.2 Terminating TC_Trail and inserting GCC within one ODUk_CTP 56 I.3.3 Bidirectional example with TCM and GCC access . 58 ITU-T Rec. G.874.1 (01/2002) 1 ITU-T Recommendation G.874.1 Optical transpo

23、rt network (OTN): Protocol-neutral management information model for the network element view 1 Scope This Recommendation provides a protocol-neutral management information model for managing network elements in the optical transport network (OTN) 1-3. It identifies the telecommunications management

24、network (TMN) managed entities required for the management of OTN network elements. These entities are relevant to information exchanged across standardized interfaces defined in the M.3010 TMN architecture 6. The protocol-neutral management information model should be used as the base for defining

25、protocol-specific management information models, for examples, CMISE information model and CORBA IDL interfaces. The specific mapping of the protocol-neutral entities into protocol-specific managed object classes is the decision of the protocol-specific modelling design. For example, a TTP entity de

26、fined in this Recommendation may be mapped into multiple managed object classes, for instance into TTP Sink and TTP Source in CMISE. On the other hand, all the monitoring entities may be mapped into a single class in a protocol-specific model. Protocol-specific information models and their mapping f

27、rom the protocol-neutral model will be described in other Recommendations. This Recommendation applies to OTN network elements and those systems in the TMN that manage OTN network elements. Functional capabilities of OTN equipment are given in ITU-T Rec. G.798 3, and aspects of the management of OTN

28、 equipment are provided in ITU-T Recs. G.7710/Y.1701 4 and G.874 5. The object entities defined in this Recommendation can apply to fault management and configuration management. There are several different perspectives from which management information may be defined for management purposes. The ne

29、twork element viewpoint is concerned with the information that is required to manage a network element. This refers to information required to manage the network element function and the physical aspects of the network element. This Recommendation addresses only the network element view of OTN manag

30、ement. 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 to

31、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. 1 ITU-T Recommendation G.872 (2001)

32、, Architecture of optical transport networks. 2 ITU-T Recommendation G.709/Y.1331 (2001), Network node interface for the optical transport network. 3 ITU-T Recommendation G.798 (2002), Characteristics of optical transport network hierarchy equipment functional blocks. 4 ITU-T Recommendation G.7710/Y

33、.1701 (2001), Common equipment management function requirements. 2 ITU-T Rec. G.874.1 (01/2002) 5 ITU-T Recommendation G.874 (2001), Management aspects of the optical transport network element. 6 ITU-T Recommendation M.3010 (2000), Principles for a telecommunications management network. 3 Terms and

34、Definitions 3.1 Definitions from ITU-T Rec. M.3100 The following terms are defined in ITU-T Rec. M.3100 and used in this Recommendation. ASAP Alarm Severity Assignment Profile CTP Connection Termination Point TP Termination Point TTP Trail Termination Point 3.2 Definitions from ITU-T Rec. G.872 The

35、following terms are defined in ITU-T Rec. G.872 and used in this Recommendation. OCh Optical Channel OMS Optical Multiplex Section OTM Optical Transport Module OTN Optical Transport Network OTS Optical Transmission Section OTU Optical Channel Transport Unit 3.3 Definitions from ITU-T Rec. G.709/Y.13

36、31 The following terms are defined in ITU-T Rec. G.709/Y.1331 and used in this Recommendation. ODUk Optical Channel Data Unit-k ODUkP Optical Channel Data Unit-k, Path ODUkT Optical Channel Data Unit-k, Tandem connection sublayer OPS Optical Physical Section OTUk Optical Transport Unit-k 3.4 Definit

37、ions from ITU-T Rec. G.798 The following terms are defined in ITU-T Rec. G.798 and used in this Recommendation. A Adaptation function GCC General Communication Channel MP Management Point TT Trail Termination function 3.5 Definitions from ITU-T Rec. G.7710/Y.1701 The following term is defined in ITU

38、-T Rec.G.7710/Y.1701 and used in this Recommendation. ARC Alarm Reporting Control ITU-T Rec. G.874.1 (01/2002) 3 4 Abbreviations and Acronyms This Recommendation uses the following abbreviations: ARC Alarm Reporting Control ASAP Alarm Severity Assignment Profile CMISE Common Management Information S

39、ervice Element CORBA Common Object Request Broker Architecture CTP Connection Termination Point GCC General Communication Channel IDL Interface Definition Language MP Management Point NE Network Element OCh Optical Channel ODUk Optical Channel Data Unit-k ODUkP Optical Channel Data Unit-k, Path ODUk

40、T Optical Channel Data Unit-k, Tandem connection sublayer OMS Optical Multiplex Section OPS Optical Physical Section OTM Optical Transport Module OTN Optical Transport Network OTS Optical Transmission Section OTU Optical Channel Transport Unit SNC Subnetwork Connection TMN Telecommunication Manageme

41、nt Network TP Termination Point TT Trail Termination function TTP Trail Termination Point UML Unified Modelling Language 5 OTN NE Management Requirements This Recommendation models the OTN transport functions that are relevant to OTN NE management. These functions are defined in ITU-T Rec. G.798 for

42、 the termination, adaptation, and connection functions of the OTN layers, including OTS, OMS, OPS, OCh, OTUk, ODUkP, and ODUkT. In particular, the input and output information exchanged at the Management Point (MP) shall be modelled. The termination, adaptation, and connections functions and input/o

43、utput information cover the areas of configuration and fault management as described in ITU-T Recs. G.7710/Y.1701 and G.874. Details of the management functions that need to be modelled are provided in ITU-T Recs. G.7710/Y.1701 and G.874. 4 ITU-T Rec. G.874.1 (01/2002) 6 Analysis In this Recommendat

44、ion, managed resources and management support resources are modelled as objects in the information model. The management view of a resource is a managed object. This Recommendation specifies the properties of the resources visible for management. Objects with similar properties are be grouped into o

45、bject classes. An object instance is an instantiation of an object class. The properties of an object include the behaviour, attributes, and operations that can be applied on the object. An object instance is characterized by its object class and may possess multiple attribute types and associated v

46、alues. In the protocol-neutral model, object classes are represented as Unified Modelling Language (UML) classes. Object classes, attribute types, and operations are defined for the purpose of communicating network management messages between systems, and need not be related to the structure of data

47、 within those systems. An object class may be a subclass of another class. A subclass inherits properties of its superclass, in addition to possessing its own specific attributes and properties. In this Recommendation, the OTN-specific transport object classes are defined. These object classes are n

48、ot inherited from any generic transport superclasses. In the future, when defining protocol-specific OTN object classes, the protocol-specific OTN object classes could be mapped from the protocol-neutral OTN object classes and also inherited from the protocol-specific generic transport object classe

49、s for additional properties. In addition to the OTN resource, the model also includes object classes for management support functions such as alarm reporting control and alarm severity assignment. 7 Design of the Protocol-neutral Information Model 7.1 UML Class Diagram Figure 7-1 provides a generic view of the UML classes of a particular transport layer network and its associated server and client layer networks. In this layer network, the CTP, TTP, SNC, and Subnetwork classes are shown. If connection function is not supported in