1、 International Telecommunication Union ITU-T G.7718.1/Y.1709.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2006) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Data over Transport Generic aspects Transport network control aspects SERIES Y: GLOBAL INFORMATION INFRASTRUC
2、TURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Internet protocol aspects Operation, administration and maintenance Protocol-neutral management information model for the control plane view ITU-T Recommendation G.7718.1/Y.1709.1 ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MED
3、IA, DIGITAL SYSTEMS AND NETWORKS INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS G.100G.199 GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS G.200G.299 INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES G.300G.399 GENERAL CHARACTERISTI
4、CS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES G.400G.449 COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY G.450G.499 TRANSMISSION MEDIA CHARACTERISTICS G.600G.699 DIGITAL TERMINAL EQUIPMENTS G.700G.799 DIGITAL NETWORKS G.800G
5、.899 DIGITAL SECTIONS AND DIGITAL LINE SYSTEM G.900G.999 QUALITY OF SERVICE AND PERFORMANCE GENERIC AND USER-RELATED ASPECTS G.1000G.1999 TRANSMISSION MEDIA CHARACTERISTICS G.6000G.6999 DATA OVER TRANSPORT GENERIC ASPECTS G.7000G.7999 General G.7000G.7099 Transport network control aspects G.7700G.77
6、99 PACKET OVER TRANSPORT ASPECTS G.8000G.8999ACCESS NETWORKS G.9000G.9999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. G.7718.1/Y.1709.1 (12/2006) i ITU-T Recommendation G.7718.1/Y.1709.1 Protocol-neutral management information model for the control plane view S
7、ummary ITU-T Recommendation G.7718.1/Y.1709.1 provides a protocol-neutral management information model for managing the ASON control plane. It includes an electronic attachment containing the UML description in navigable html format and in the original Rational Rose format. Source ITU-T Recommendati
8、on G.7718.1/Y.1709.1 was approved on 14 December 2006 by ITU-T Study Group 15 (2005-2008) under the ITU-T Recommendation A.8 procedure. Keywords ASON, control plane, protocol-neutral information model, UML. ii ITU-T Rec. G.7718.1/Y.1709.1 (12/2006) FOREWORD The International Telecommunication Union
9、(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 stan
10、dardizing 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 is c
11、overed 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 to in
12、dicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achiev
13、ed when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL P
14、ROPERTY 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, whether ass
15、erted 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, implementers are cautioned
16、 that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2007 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
17、ITU-T Rec. G.7718.1/Y.1709.1 (12/2006) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation. 2 4 Abbreviations 2 5 Conventions 4 5.1 Object creation and deletion. 4 5.2 Textual conventions 4 6 Control plane management requ
18、irements . 8 7 Analysis 8 8 Design of the protocol-neutral information model . 9 8.1 Class diagram Call/connection class diagram . 9 8.2 Class diagram Common attributes diagram (InheritanceTree) . 10 8.3 Class diagram Discovery service class diagram 11 8.4 Class diagram Notification class diagram .
19、11 8.5 Class diagram Routing service class diagram . 12 8.6 Class diagram Signalling service class diagram 13 9 Class definitions 13 9.1 AlarmSeverityAssignmentProfile. 13 9.2 CR-LDPProtocol 13 9.3 Call . 14 9.4 CallCreateData . 19 9.5 CallDetailRecord 21 9.6 CallService . 22 9.7 CommonResourceInfor
20、mation . 26 9.8 Connection 27 9.9 ConnectionCreateData 29 9.10 ConnectionService 31 9.11 ConnectionTerminationPoint . 32 9.12 ControlPlane. 32 9.13 ControlPlaneService. 34 9.14 DiscoveryService 35 9.15 ISISArea . 36 9.16 ISISNeighbour 38 9.17 ISISProtocol . 39 9.18 LayerAdjacencyDiscovery . 40 9.19
21、ManagedElement 42 iv ITU-T Rec. G.7718.1/Y.1709.1 (12/2006) Page 9.20 OSPFArea. 42 9.21 OSPFNeighbour . 44 9.22 OSPFProtocol. 45 9.23 PNNIArea. 46 9.24 PNNINeighbour 48 9.25 PNNIRoutingProtocol 49 9.26 PNNISignallingProtocol. 50 9.27 RSVPProtocol. 51 9.28 RoutingArea . 51 9.29 RoutingTable 55 9.30 S
22、NP. 55 9.31 SNPLinkConnection. 56 9.32 SNPP. 57 9.33 SNPPLink. 58 9.34 SignallingProtocol 62 9.35 TerminationPoint 63 9.36 TrailTerminationPoint 63 9.37 TransportEntityCapabilityExchange 63 10 Notification definitions. 65 10.1 Alarm 65 10.2 AttributeValueChangeNotification. 66 10.3 Notification. 66
23、10.4 ObjectCreationNotification 68 10.5 ObjectDeletionNotification 68 10.6 StateChangeNotification. 68 11 Data Types 68 11.1 Enumerations 68 11.2 Structures 75 11.3 TypeDefinitions 76 Appendix I G.7718.1 and TMF 608v3.0. 79 Appendix II Alternate representations 80 Electronic attachment: Layer rate s
24、upporting document. UML description in navigable html format. UML description in original Rational Rose format. ITU-T Rec. G.7718.1/Y.1709.1 (12/2006) 1 ITU-T Recommendation G.7718.1/Y.1709.1 Protocol-neutral management information model for the control plane view11 Scope This Recommendation provide
25、s a protocol-neutral management information model for managing the ASON control plane. It identifies the telecommunication management network (TMN) managed entities required. These entities are relevant to information exchanged across standardized interfaces defined in ITU-T M.3010 TMN architecture.
26、 The protocol-neutral management information model should be used as the base for defining protocol-specific management information models, for example, CMISE information model and CORBA IDL interfaces. The specific mapping of the protocol-neutral entities into protocol-specific managed object class
27、es is the decision of the protocol-specific modelling design. Protocol-specific information models and their mapping from the protocol-neutral model will be described in other documents. This Recommendation applies to network elements performing ASON control plane functions, and those systems in the
28、 TMN that manage them. The architecture or ASON control plane and its components are given in ITU-T G.8080 and the management framework and requirements are given in ITU-T G.7718. The object entities defined in this model apply to configuration and fault management. There are several different persp
29、ectives from which management information may be defined for management purposes. The control plane fragment contains those object entities and information having to do with managing the control plane functions, irrespective of the platform performing those functions. That platform may be a traditio
30、nal network element or a stand-alone element with no transport functionality. 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 indicat
31、ed 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 Reco
32、mmendations 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. ITU-T G.7710 ITU-T Recommendation G.7710/Y.1701 (2001), Common equipment management function requirements. ITU-T G.7713 ITU-T Recomm
33、endation G.7713/Y.1704 (2006), Distributed call and connection management (DCM). ITU-T G.7714 ITU-T Recommendation G.7714/Y.1705 (2005), Generalized automatic discovery for transport entities. ITU-T G.7718 ITU-T Recommendation G.7718/Y.1709 (2005), Framework for ASON management. ITU-T G.8080 ITU-T R
34、ecommendation G.8080/Y.1304 (2006), Architecture for the automatically switched optical network (ASON). _ 1This Recommendation includes an electronic attachment containing the layer rate supporting document, the UML description in navigable html format and in the original Rational Rose format. 2 ITU
35、-T Rec. G.7718.1/Y.1709.1 (12/2006) ITU-T M.3010 ITU-T Recommendation M.3010 (2005), Principles for a telecommunications management network. ITU-T M.3100 ITU-T Recommendation M.3100 (2005), Generic network information model. ITU-T X.733 ITU-T Recommendation X.733 (1992), Information technology Open
36、Systems Interconnection Systems management: Alarm reporting function. AF-PNNI-0055 MFA Forum AF-PNNI-0055.002, Private Network-Network Interface Specification Version 1.1 (PNNI 1.1), April 2002. IETF RFC 2328 IETF RFC 2328 (1998), OSPF Version 2. IETF RFC 3473 IETF RFC 3473 (2003), Generalized Multi
37、-Protocol Label Switching (GMPLS) Signalling Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions. ISO/IEC 10589 ISO/IEC 10589:2002, Information technology Telecommunications and information exchange between systems Intermediate system to intermediate system intra-domain routeing i
38、nformation exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473). TMF MTNM Tele Management Forum MTNM SD1-17_LayerRates. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1
39、.1 alarm severity assignment profile (ASAP): ITU-T M.3100. 3.1.2 connection termination point (CTP): ITU-T M.3100. 3.1.3 termination point (TP): ITU-T M.3100. 3.1.4 trail termination point (TTP): ITU-T M.3100. 3.1.5 alarm reporting control (ARC): ITU-T G.7710. 3.1.6 subnetwork point (SNP): ITU-T G.8
40、080. 3.1.7 subnetwork point pool (SNPP): ITU-T G.8080. 3.1.8 subnetwork point pool link (SNPP link): ITU-T G.8080. 3.2 Terms defined in this Recommendation None. 4 Abbreviations This Recommendation uses the following abbreviations: ASON Automatically Switched Optical Network AVC Attribute Value Chan
41、ge Notification AVP Attribute name Value Pair CMISE Common Management Information Service Element CORBA Common Object Request Broker Architecture ITU-T Rec. G.7718.1/Y.1709.1 (12/2006) 3 CP Control Plane CR-LDP Constraint-based Label Distribution Protocol DCM Distributed Call and Connection Manageme
42、nt EMS Element Management System ENNI External Network-Network Interface GDMO Guidelines for Definition of Managed Objects HTML HyperText Markup Language Id, ID Identifier IDL Interface Definition Language I-NNI Internal Network-Network Interface IP Internet Protocol ISIS Intermediate System Interme
43、diate System routing protocol LCAS Link Capacity Adjustment Scheme LRM Link Resource Manager LSA Link State Advertisement MIB Management Information Base MTNM Multi-Technology Network Management MTU Maximum Transmission Unit NA Not Applicable NE Network Element NMS Network Management System OSPF Ope
44、n Shortest Path First PNNI Private Network-to-Network Interface RSVP Resource Reservation Protocol RSVP-TE Resource Reservation Protocol Traffic Engineering SCN Signalling Communication Network SRG Shared Risk Group TCE Transport Capability Exchange TMF TeleManagement Forum TMN Telecommunication Man
45、agement Network TRI Transport Resource Identifier TTP Trail Termination Point UML Unified Modelling Language UNI User-to-Network Interface UNI-C User-to-Network Interface Customer side UNI-N User-to-Network Interface Network side 4 ITU-T Rec. G.7718.1/Y.1709.1 (12/2006) 5 Conventions This Recommenda
46、tion uses the UML notation to specify a protocol-neutral information model. UML itself does not specify an execution environment, so there are no pre-existing object methods provided. This is in contrast to the X.721 (GDMO/CMISE) notation which provides many methods in its assumed environment. This
47、Recommendation has therefore specified some general methods, and has specified them as operations against the ControlPlane object. 5.1 Object creation and deletion An object can be Created or Deleted by using the relevant operation on the ControlPlane object. However, some objects are created as the
48、 result of very significant activity in the control plane, and the generic create operation cannot have any knowledge of the very special behaviour of (for example) creating a call object. Some objects are also expected to be automatically created when the platform supporting those objects is initia
49、lized. It is not expected to create such objects by independent management action. This specification takes care of these significant differences by providing special operations to create these special objects, and it is a convention that these special operations are used in place of the generic ones. 5.2 Textual conventions Several important properties of network management applications need to be specified, and UML does not provide any formal support. This Re
