scope:

An information model describes the things in a domain in terms of objects, their properties (represented as attributes) and their relationships. This Recommendation¹ describes a core information model of transport resources. 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 model 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 management 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 management, [ITU-T G.8052] for carrier Ethernet management and [ITU-T G.7718.1] for ASON control management. An example of an information model

A uniform protocol-neutral core information model for traditional management, 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 domains 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 include:

- 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 subnetworks.

- Distributed NEs (e.g., a PON) with a mediation function to allow management visibility of each of the "encapsulated" NEs.

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.

¹ This Recommendation includes an electronic attachment containing the information model files and the companion profile file specified in clause 8.1.