1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T G.7711/Y.1702 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2015) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Data over Transport Generic aspects Transport network control aspects SERIES Y:
2、GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Internet protocol aspects Operation, administration and maintenance Generic protocol-neutral information model for transport resources Recommendation ITU-T G.7711/Y.1702 ITU-T G-SERIES RECOMMENDATIONS TRANSMISS
3、ION 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 INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES G.300G.399 GE
4、NERAL 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 TELEPHONY G.450G.499 TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS G.600G.699 DIGITAL TERMINAL EQUIPM
5、ENTS G.700G.799 DIGITAL NETWORKS G.800G.899 DIGITAL SECTIONS AND DIGITAL LINE SYSTEM G.900G.999 MULTIMEDIA 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
6、.7099 Transport network control aspects G.7700G.7799 PACKET OVER TRANSPORT ASPECTS G.8000G.8999 ACCESS NETWORKS G.9000G.9999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T G.7711/Y.1702 (08/2015) i Recommendation ITU-T G.7711/Y.1702 Generic protocol-neutral inform
7、ation model for transport resources Summary Recommendation ITU-T G.7711/Y.1702 specifies a core information model of transport resources. The information model is applicable for the management and control of transport networks regardless of whether the transport networks utilize a traditional operat
8、ion support system (OSS) management, an automatically switched optical network (ASON) control plane, or a software defined networking (SDN) controller to configure transport connectivity. The model is also applicable to the management and control of the transport network regardless of the technology
9、 of the underlying transport network. Furthermore, the applicability of the information model is independent of the ultimate protocols that will be used in the management and control interfaces. This Recommendation includes an electronic attachment containing the information model files and the comp
10、anion profile file specified in clause 8.1. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T G.7711/Y.1702 2015-08-13 15 11.1002/1000/12567 _ * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommend
11、ations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T G.7711/Y.1702 (08/2015) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). Th
12、e 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 standardizing telecommunications on a worldwide basis. The World Telecommunication Standa
13、rdization 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
14、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 indicate both a telecommunication administration and a recognized operating agency. Com
15、pliance 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 achieved when all of these mandatory provisions are met. The words “shall“ or some other
16、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 PROPERTY RIGHTSITU draws attention to the possibility that the practice or implement
17、ation 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 of the Recommendation development process. As
18、 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 that this may not represent the latest information and are therefore strongly urged
19、 to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2015 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T G.7711/Y.1702 (08/2015) iii Table of Contents Page 1 Scope . 1 1.1 Develo
20、pment and use of the ITU-T G.7711 generic information model . 2 2 References . 5 3 Definitions 6 3.1 Terms defined elsewhere 6 3.2 Terms defined in this Recommendation . 6 4 Abbreviations and acronyms 6 5 Conventions 8 5.1 UML modelling conventions 8 5.2 Model artefact lifecycle stereotypes conventi
21、ons . 8 5.3 Forwarding entity terminology conventions 8 5.5 Pictorial diagram conventions 8 6 Overview of the Generic Information Model (GIM) 10 6.1 Overview of the Core Network Module (CNM) 11 6.2 Core Foundation Module (CFM) 17 6.3 Termination subset of CNM . 21 6.4 Forwarding subset of CNM 24 6.5
22、 Topology subset of CNM . 27 7 Future area of the GIM . 39 7.1 Synchronization (frequency and time/phase) module 40 7.2 Scheduling module . 40 7.3 Logging module 40 7.4 Notification module 40 7.5 Performance management module . 40 7.6 Fault management module . 40 7.7 ECC management module 40 7.8 Pol
23、icy management module . 40 7.9 Physical equipment management module 40 7.10 Generalized OAM/MEP functions . 40 8 UML model files . 40 8.1 Papyrus file . 40 8.2 Data dictionary file . 40 Annex A UML modelling guidelines 41 A.1 Introduction 41 A.2 Source references 41 A.3 Overview 41 A.4 UML artefact
24、descriptions 42 iv Rec. ITU-T G.7711/Y.1702 (08/2015) Page A.5 UML profile definitions . 59 A.6 Recommended modelling patterns . 62 Bibliography. 67 Information model files and the companion profile file specified in clause 8.1 Rec. ITU-T G.7711/Y.1702 (08/2015) 1 Recommendation ITU-T G.7711/Y.1702
25、Generic protocol-neutral information model for transport resources 1 Scope An information model describes the things in a domain in terms of objects, their properties (represented as attributes) and their relationships. This Recommendation1 describes a core information model of transport resources.
26、This information model is intended to be applicable to the management and control of the transport network regardless of whether the transport networks utilize traditional OSS management ITU-T G.7710, an ASON control plane ITU-T G.8080 or an SDN controller to configure transport connectivity. The mo
27、del is also intended to be applicable to the management and control of the transport network regardless of the transport technology of the underlying transport network. Furthermore, the applicability of the information model is independent of the ultimate protocols that will be used in the managemen
28、t and control interfaces. The core information model defined in this Recommendation can be used as the base for the extension of transport/control-technology-specific information models. Such extensions will be specified in the technology-specific Recommendations, such as ITU-T G.874.1 for OTN manag
29、ement, ITU-T G.8052 for carrier Ethernet management and ITU-T G.7718.1 for ASON control management. An example of an information model extension is shown in Figure 1-1. Figure 1-1 Example of an information model extension A uniform protocol-neutral core information model for traditional management,
30、ASON control and SDN control will ensure consistent operation, administration, maintenance and provisioning (OAMP) of the transport network. This will benefit the network operators and system/equipment vendors for enabling interoperability between SDN-controlled and traditionally-managed network dom
31、ains and future migration from traditional management to SDN control. Furthermore, it is essential that the information model be applicable to complex network elements (NEs) that may be deployed in current networks, which requires support of more than a simple nodal view. Examples of such NEs includ
32、e: Multi-layer NEs with subnetworks at each layer with transitional links between the subnetworks. NEs that have their matrix partitioned (e.g., to model multiple multiplex section share protection ring (MSPRING) terminations or to model connectivity restrictions) with “internal“ links between the s
33、ubnetworks. Distributed NEs (e.g., a PON) with a mediation function to allow management visibility of each of the “encapsulated“ NEs. _ 1 This Recommendation includes an electronic attachment containing the information model files and the companion profile file specified in clause 8.1. 2 Rec. ITU-T
34、G.7711/Y.1702 (08/2015) The complexity of these NEs makes it difficult to distinguish between the NE view and what is traditionally called the network view. The core information model thus encompasses both a nodal view and a network view of the transport resources. 1.1 Development and use of the ITU
35、-T G.7711 generic information model Figure 1-2 provides an overview of the common information model (IM) and shows how the purpose specific IM views and data schema2 are related to it. The term data schema (DS) in this document is used in the context of either (1) a specific protocol that is used to
36、 implement a purpose specific interface or (2) a programming language that is used to invoke a purpose specific application programming interface (API). Guidelines for the use of unified modelling language (UML) in the common IM as well as pruning and refactoring the common IM to provide a purpose s
37、pecific view and ultimately mapping to a data schema will also be provided. Figure 1-2 Methodology of IM and DS development 1.1.1 Common IM An information model describes the things in a domain in terms of objects, their properties (represented as attributes) and their relationships. The common IM s
38、hould be expressed in UML and include all of the artefacts (object classes, attributes, relationships, etc.) that are necessary to describe the generic model and domains for the technologies/applications being developed. It will be necessary to continually expand and refine the common IM over time a
39、s new forwarding technologies, capabilities and applications are encompassed and new insights are gained. To allow these extensions to be made in a seamless manner, the common IM will be structured into a generic model, see ITU-T G.7711. In addition the common IM will be structured into a number of
40、models which are specific to the forwarding technologies (such as OTN in ITU-T G.874.1, Ethernet in ITU-T G.8052, etc.) and applications such as ASON control plane management in _ 2 The term data schema is used instead of data model since the term data model is also used in a wider context. Rec. ITU
41、-T G.7711/Y.1702 (08/2015) 3 ITU-T G.7718.1. This modelling process is intended to allow these extensions to be developed with as much independence as possible. Generic model The artefacts in the generic model ITU-T G.7711 will be used by the technology/application specific models either directly or
42、 with extensions. The generic model will be constructed as a set of modules each addressing a specific topic to allow for easier navigation. This Recommendation is responsible for specifying and maintaining the generic model. As a result of advancements in the industry it may be recognised that some
43、 parts of the generic model may need to be augmented or changed. This Recommendation will ensure that any such areas are clearly identified using lifecycle stereotypes. The older model forms will be maintained to ensure ongoing compatibility and to ease migration. Specific models It is expected that
44、 the transport forwarding technology or application specific domains will develop the appropriate models which contain objects, attributes and associations that relate solely to their respective domains. In some cases an application or forwarding technology addition will also require enhancement of
45、the generic model. In some cases an artefact in a specific model initially considered to be purely for a single forwarding technology or application may be subsequently recognised as common across several specific models and hence there will be a need to migrate this artefact to the generic model. T
46、o assure coherency, any artefacts, attributes or associations that might be identified during the development of forwarding technology or application specific views should be included in the appropriate fragment of the common information model. Only those properties that relate to the specific encod
47、ing or style of interaction of an interface may be added outside the common information model. 1.1.2 Purpose specific IM view A purpose specific information model view is a subset of the common IM and should be expressed in UML. A purpose specific information model view will typically be much smalle
48、r than the entire common IM. If additional artefacts (objects, packages, attributes or associations) are identified while establishing a specific view, these should be added to the appropriate fragment of the common IM so that they are available for future use. To provide maximum reusability, a purp
49、ose specific view should be developed in two steps: Prune and refactor the artefacts of the common IM to provide a model of the network to be managed. Only those artefacts that represent the capabilities that are both in scope and supported are include in the purpose specific IM. Define the access rights for the various groups of users that will manage that network. Pruning and refactoring provides a purpose specific IM that represents the capa
