Technical requirements for automatically switched optical network management
- Part 2: NMS system function
1 Scope
This part of the standard specifies the management scope, technical requirements and system function requirements for the network management system (NMS) of automatically switched optical network (ASON).
This part is applicable to the ASON NMS.
2 Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of this part. For dated references, subsequent amendments (excluding corrections) to, or revisions of, any of these publications do not apply. However, parties to agreements based on this part are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. For undated references, the latest edition of the normative document applies.
GB/T 21645.1-2008 Technical requirements for automatically switched optical network - Part 1: Architecture and general requirements
YD/T 1289.3-2003 Synchronous digital hierarchy (SDH) transport network management system technical specification part 3: Network management system (NMS) function
YD/T 1767.1-2008 Technical requirements for automatically switched optical network management - Part 1: Basic principle
3 Terms and abbreviations
3.1 Terms
For the purposes of this document, the terms and definitions established in GB/T 21645.1 and YD/T 1289.3-2003 and the following apply.
3.1.1
network management system (NMS)
ASON NMS, namely, a software and hardware system used to manage ASON, which provides an end-to-end network view of the whole network, and is able to manage ASON elements or subnetworks in multi-device vendors and multi-control domain environments in the network
3.1.2
element management system (EMS)
ASON EMS, namely, a software and hardware system used to manage one or more ASON elements, which manages ASON elements or subnetworks provided by a single equipment vendor
Note: The EMS given in this part refers to the element management system and subnetwork management system collectively in the traditional sense.
3.1.3
name
unique and immutable identifier of a managed object in the EMS or NMS management domain
3.1.4
user label
user-friendly name that can be configured for a managed object, an attribute which can, in an EMS, be initially set as the local name of the EMS, and which can be managed and assigned by the NMS
3.1.5
layered SNPP
group of SNPPs with the same layer rate
3.1.6
layered SNPP link
SNPP link at a specific layer rate
3.1.7
multilayer routing area (MLRA)
multilayer routing area (MLRA) which is composed of one or more routing areas in a control plane. Each routing area corresponds to a supported layer rate. An MLRA contains a plurality of subordinate MLRAs interconnected by SNPP links. Each MLRA can in turn contain corresponding subordinate MLRAs, the subordinate RAs are completely contained in their superior RAs, and the smallest MLRA contains one routing node. The MLRA forms a hierarchical structure through this inclusion relationship. The division of MLRAs is determined by EMS
In this part, three levels of MLRA are supported: top-level MLRAs (corresponding to the entire ASON managed by a control plane), intermediate-level MLRAs and routing nodes [corresponding to management elements (MEs)]. In a network without control planes, an MLRA contains 0 or more multilayer subnetworks (MLSN) and supports the provision of connections across multiple MLSNs.
3.1.8
multilayer SNPP (MLSNPP)
set of layered SNPPs, with each layer rate corresponding to a layered SNPP
3.1.9
multilayer SNPP link (MLSNPP link)
collection of SNPP links of control planes in different layer networks, wherein multilayers do not represent client-server relationships, but rather multiple layer rates that are flexibly mapped to the same switching hierarchy
3.1.10
diversity
network resources (links and nodes) with multiple parallel connections for different usage between a pair of input and output ports, which may be classified into different types depending on factors such as links, nodes or management policies: node-unrelated diversities (with separated nodes) if two connections do not share any nodes other than the ingress and egress nodes; link-unrelated diversities (with separated links) if the routes of two connections do not share any links
Foreword II
1 Scope
2 Normative references
3 Terms and abbreviations
3.1 Terms
3.2 Abbreviations
4 ASON NMS management scope
5 Technical requirements
5.1 General requirements for the system
6 Requirements for system management functions
6.1 Use case
6.2 Transport plane management functions
6.3 Control plane management functions
6.4 Signaling communications network (SCN) management
Annex A (Informative) Schematic diagram for hierarchical relationship of MLRA
Technical requirements for automatically switched optical network management
- Part 2: NMS system function
1 Scope
This part of the standard specifies the management scope, technical requirements and system function requirements for the network management system (NMS) of automatically switched optical network (ASON).
This part is applicable to the ASON NMS.
2 Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of this part. For dated references, subsequent amendments (excluding corrections) to, or revisions of, any of these publications do not apply. However, parties to agreements based on this part are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. For undated references, the latest edition of the normative document applies.
GB/T 21645.1-2008 Technical requirements for automatically switched optical network - Part 1: Architecture and general requirements
YD/T 1289.3-2003 Synchronous digital hierarchy (SDH) transport network management system technical specification part 3: Network management system (NMS) function
YD/T 1767.1-2008 Technical requirements for automatically switched optical network management - Part 1: Basic principle
3 Terms and abbreviations
3.1 Terms
For the purposes of this document, the terms and definitions established in GB/T 21645.1 and YD/T 1289.3-2003 and the following apply.
3.1.1
network management system (NMS)
ASON NMS, namely, a software and hardware system used to manage ASON, which provides an end-to-end network view of the whole network, and is able to manage ASON elements or subnetworks in multi-device vendors and multi-control domain environments in the network
3.1.2
element management system (EMS)
ASON EMS, namely, a software and hardware system used to manage one or more ASON elements, which manages ASON elements or subnetworks provided by a single equipment vendor
Note: The EMS given in this part refers to the element management system and subnetwork management system collectively in the traditional sense.
3.1.3
name
unique and immutable identifier of a managed object in the EMS or NMS management domain
3.1.4
user label
user-friendly name that can be configured for a managed object, an attribute which can, in an EMS, be initially set as the local name of the EMS, and which can be managed and assigned by the NMS
3.1.5
layered SNPP
group of SNPPs with the same layer rate
3.1.6
layered SNPP link
SNPP link at a specific layer rate
3.1.7
multilayer routing area (MLRA)
multilayer routing area (MLRA) which is composed of one or more routing areas in a control plane. Each routing area corresponds to a supported layer rate. An MLRA contains a plurality of subordinate MLRAs interconnected by SNPP links. Each MLRA can in turn contain corresponding subordinate MLRAs, the subordinate RAs are completely contained in their superior RAs, and the smallest MLRA contains one routing node. The MLRA forms a hierarchical structure through this inclusion relationship. The division of MLRAs is determined by EMS
In this part, three levels of MLRA are supported: top-level MLRAs (corresponding to the entire ASON managed by a control plane), intermediate-level MLRAs and routing nodes [corresponding to management elements (MEs)]. In a network without control planes, an MLRA contains 0 or more multilayer subnetworks (MLSN) and supports the provision of connections across multiple MLSNs.
3.1.8
multilayer SNPP (MLSNPP)
set of layered SNPPs, with each layer rate corresponding to a layered SNPP
3.1.9
multilayer SNPP link (MLSNPP link)
collection of SNPP links of control planes in different layer networks, wherein multilayers do not represent client-server relationships, but rather multiple layer rates that are flexibly mapped to the same switching hierarchy
3.1.10
diversity
network resources (links and nodes) with multiple parallel connections for different usage between a pair of input and output ports, which may be classified into different types depending on factors such as links, nodes or management policies: node-unrelated diversities (with separated nodes) if two connections do not share any nodes other than the ingress and egress nodes; link-unrelated diversities (with separated links) if the routes of two connections do not share any links
Contents of YD/T 1767.2-2011
Foreword II
1 Scope
2 Normative references
3 Terms and abbreviations
3.1 Terms
3.2 Abbreviations
4 ASON NMS management scope
5 Technical requirements
5.1 General requirements for the system
6 Requirements for system management functions
6.1 Use case
6.2 Transport plane management functions
6.3 Control plane management functions
6.4 Signaling communications network (SCN) management
Annex A (Informative) Schematic diagram for hierarchical relationship of MLRA
