scope:

This Recommendation defines the architecture requirements for a data communication network (DCN) which may support distributed management communications related to the telecommunication management network (TMN), distributed control communications (e.g., signalling and routing) related to the automatically switched optical network (ASON), distributed control communications (e.g., signalling and routing) related to multiprotocol label switching - transport profile (MPLS-TP), control communications related to software defined networking (SDN), and other distributed communications (e.g., orderwire or voice communications, software download). The DCN architecture considers networks that are IP-only, open system interface (OSI)-only, and mixed (i.e., support both IP and OSI). The interworking between parts of the DCN supporting IP-only, parts supporting OSI-only, and parts supporting both IP and OSI are also specified - other protocols (other than IP or OSI) are outside the current scope of this Recommendation.

The DCN provides Layer 1 (physical), Layer 2 (data-link) and Layer 3 (network) functionality and consists of routing/switching functionality interconnected via links. These links can be implemented over various interfaces, including wide area network (WAN) interfaces, local area network (LAN) interfaces, and embedded communication channels (ECCs).

Various applications (e.g., TMN, ASON) require a packet-based communication network to transport information between various components. For example, the TMN requires a communication network, which is referred to as the management communication network (MCN) to transport management messages between TMN components (e.g., network element function (NEF) component and operations support function (OSF) component). ASON requires a communication network, which is referred to as the control communication network (CCN), and MPLS-TP requires a communication network, which is referred to as signalling communication network (SCN) to transport signalling and routing messages between functional management and control (MC) components (e.g., connection controller (CC) components and routing controller (RC) components). This Recommendation specifies data communication functions (DCFs) that can be used to support one or more application's communication network.

The DCFs provided in this Recommendation support connectionless network services. Additional functions may be added in future versions of this Recommendation to support connection-oriented network services.

Version 4 of this Recommendation provided the requirements for the MPLS transport profile (MPLS-TP) signalling communication channel (SCC) and management communication channel (MCC) DCFs. The part of this Recommendation that addresses MPLS for transport networks complies with the transport profile of MPLS architecture as defined by Internet Engineering Task Force (IETF). In the event of a difference between this Recommendation and any of the normatively referenced request for comments (RFCs) for MPLS-TP, the RFCs will take precedence.

The 2020 version (version 5) provides updates that cover control communications related to software defined networking (SDN). A new Appendix V is also added to this version to provide a mapping between clauses here and prior versions due to restructuring.

The 2022 version (version 5.1) provides updates of the definition of CCN and DCN, replacing SCN with CCN, replacing the control component with the MC component, and some editorial changes. A new subclause of 8.2.5 is also added to this version for MTN ECC.

This Recommendation forms part of a family of Recommendations covering transport networks.