ZXONE 5800: Multi-Service Core Optical Switch Equipment

ZXONE 5800
Multi-service Core Optical Switch Equipment

System Descriptions
Version: V1.20
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.1 2012–02–20 Updated
R1.0 2011–12–30 ZXONE 5800(V1.20) Issued
Serial Number: SJ-20111121090706-001
Publishing Date: 2012-02-20(R1.1)

Table of Contents
About This Manual ......................................................................................... I
Chapter 1 System Overview ...................................................................... 1-1
1.1 Introduction to ZXONE 5800 ............................................................................... 1-1
1.2 Application of ZXONE 5800 ................................................................................ 1-3
Chapter 2 Hardware Architecture ............................................................. 2-1

2.1 Cabinet.............................................................................................................. 2-1
2.2 Subrack ............................................................................................................. 2-3
2.3 Boards............................................................................................................... 2-4
2.3.1 Board List ................................................................................................ 2-4
2.3.2 Classification of Boards ............................................................................ 2-5
2.4 Functional Units ................................................................................................. 2-5
2.4.1 Relationship Between Functional Units ...................................................... 2-5
2.4.2 Introduction to Functional Units ................................................................. 2-5
2.5 Functional Planes............................................................................................... 2-7
Chapter 3 Software Architecture............................................................... 3-1

3.1 Overview of Software Architecture....................................................................... 3-1
3.2 Intelligent Software............................................................................................. 3-1
3.3 Board Software .................................................................................................. 3-2
3.4 Agent Software .................................................................................................. 3-2
3.5 EMS Software.................................................................................................... 3-3
3.6 Communication Protocols and Interfaces ............................................................. 3-4
Chapter 4 System Functions ..................................................................... 4-1

4.1 Service Function ................................................................................................ 4-1
4.1.1 Service Types .......................................................................................... 4-1
4.1.2 Service Access Capability......................................................................... 4-1
4.2 Cross-Connection Function................................................................................. 4-2
4.3 System Control and Communication Functions .................................................... 4-3
4.4 Overhead Processing Functions.......................................................................... 4-3
4.5 Clock Functions ................................................................................................. 4-4
4.6 Alarm Function................................................................................................... 4-5
4.6.1 Alarm Input/Output Functions.................................................................... 4-5
4.6.2 Alarm Detection Function.......................................................................... 4-5
4.7 Performance Detection Function ......................................................................... 4-5
I
4.8 Optical Amplification Function ............................................................................. 4-6
4.9 Protection Function ............................................................................................ 4-7
4.9.1 Equipment-Level Protection ..................................................................... 4-7
4.9.2 Network-Level Protection .......................................................................... 4-8
4.10 Online Upgrade of Board Software .................................................................... 4-8
4.11 ASON Functions............................................................................................... 4-8
4.11.1 End-to-End Service Configuration ........................................................... 4-8
4.11.2 Restoration of Mesh Network................................................................... 4-9
4.11.3 ASON Service Levels ........................................................................... 4-10
4.11.4 Conversion Between Service Levels ...................................................... 4-14
4.11.5 Service Optimization Function ............................................................... 4-15
4.11.6 Tunnel Services.................................................................................... 4-15
4.11.7 Service Association .............................................................................. 4-16
4.11.8 Transfer Between PC Service and SPC Service ..................................... 4-19
4.11.9 Service Preemption .............................................................................. 4-21
4.11.10 Resource Sharing ............................................................................... 4-22
4.11.11 Interconnection Between Traditional Service and ASON Service ........... 4-24
4.11.12 Receiving/Sending on One Route ........................................................ 4-26
Chapter 5 Configuration and Network Architecture................................ 5-1

5.1 Equipment Configuration .................................................................................... 5-1
5.1.1 Board Description..................................................................................... 5-1
5.1.2 Board Slots in the Subrack........................................................................ 5-1
5.1.3 Board Configuration Principle.................................................................... 5-4
5.2 Typical Configuration .......................................................................................... 5-5
5.2.1 Terminal Multiplexer (TM).......................................................................... 5-5
5.2.2 Add/Drop Multiplexer (ADM) ..................................................................... 5-7
5.2.3 SDXC Equipment ..................................................................................... 5-9
5.3 Networking Modes.............................................................................................5-11
5.3.1 Point-to-Point Network.............................................................................5-11
5.3.2 Chain Network ....................................................................................... 5-12
5.3.3 Ring Network ......................................................................................... 5-14
5.3.4 Star Network .......................................................................................... 5-16
5.3.5 Mesh Network........................................................................................ 5-16
5.3.6 Hybrid Network ...................................................................................... 5-17
5.4 Networking Application ..................................................................................... 5-18
5.4.1 Traditional SDH Networking Application .................................................. 5-18
5.4.2 ASON Networking Application ................................................................. 5-19
II
5.4.3 GE Service Networking Application ......................................................... 5-20
5.5 Networking Application for Ethernet Services ..................................................... 5-21
5.6 Configuration Example ..................................................................................... 5-22
Appendix A Fundamentals of ASON ....................................................... A-1

A.1 Generation Background of ASON ....................................................................... A-1
A.1.1 Definition of ASON................................................................................... A-1
A.1.2 Problems in Traditional Optical Networks................................................... A-1
A.1.3 Generation of ASON ................................................................................ A-2
A.1.4 Advantages of ASON ............................................................................... A-2
A.2 ASON Architecture............................................................................................. A-3
A.2.1 Connection Types in ASON ...................................................................... A-6
A.2.2 Control Plane Functions ........................................................................... A-6
A.2.3 Control Plane Interfaces ........................................................................... A-7
A.2.4 Control Protocols ..................................................................................... A-9
A.3 ASON Networking............................................................................................ A-11
A.4 Protection and Restoration ............................................................................... A-13
A.4.1 ASON Protection ................................................................................... A-13
A.4.2 ASON Restoration ................................................................................. A-14
A.5 ASON Services................................................................................................ A-15
A.5.1 Introduction to ASON Services................................................................ A-15
A.5.2 Cases of ASON Service Model ............................................................... A-17
A.5.3 Management of ASON Services.............................................................. A-20
List of Figures................................................................................................. I
List of Tables................................................................................................. III
Glossary .........................................................................................................V
III
IV
About This Manual
Purpose
At first, thank you for choosing the Unitrans ZXONE 5800 Multi-Service Core Optical Switch
Equipment of ZTE Corporation!
Based on Synchronous Digital Hierarchy (SDH), ZXONE 5800 is a high–capacity
cross-connect equipment providing a maximum rate of 10 Gbit/s. This equipment is
applied in the metropolitan-area core layer and the toll backbone layer.
Intended Audience
This manual is intended for:
l Planning engineer
l Installation supervision engineer
l Installation engineer
l Operation and maintenance engineer
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
Chapter 1, System Describes features and applications of ZXONE 5800.

Overview
Chapter 2, Hardware Describes the cabinet, subrack, boards, functional units, and functional
Architecture planes of ZXONE 5800.
Chapter 3, Software Describes the software structure, intelligent software, board software,
Architecture agent software, EMS software, communication protocol, and interfaces
of ZXONE 5800.
Chapter 4, System Describes system functions of ZXONE 5800.

Functions
Chapter 5, Configuration Describes the equipment configuration, typical NE configuration,

and Network Architecture networking modes, networking applications, and configuration
examples of ZXONE 5800.
Related Documentation
The following documentation is related to this manual:
I
Manual Summary
Unitrans ZXONE 5800 (V1.20) Multi-Service Core Describes technical features, upgrade/main-
Optical Switch Equipment Product Descriptions tenance features, interfaces, and technical
specifications of ZXONE 5800.
Unitrans ZXONE 5800 (V1.20) Multi-Service Core Describes equipment hardware, including the
Optical Switch Equipment Hardware Descriptions cabinet, power distribution box, subrack, boards,
interfaces, and indicators.
Unitrans ZXONE 5800 (V1.20) Multi-Service Describes on-site installation procedures,

Core Optical Switch Equipment Installation including installation preparations, hardware
Descriptions installation, cable installation, installation check,
and power-on/power-off.
Unitrans ZXONE 5800 (V1.20) Multi-Service Core Describes major items and common operations
Optical Switch Equipment Maintenance Manual for routine maintenance.
(Volume I) Routine Maintenance
Unitrans ZXONE 5800 (V1.20) Multi-Service Core Describes handling methods for the equipment
Optical Switch Equipment Maintenance Manual alarms and performance events.
(Volume II) Alarm and Performance
Conventions
ZTE documents employ the following typographical conventions.
Typeface Meaning
Italics References to other manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input fields, radio button names, check boxes,
drop-down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens and company name.
Note: Provides additional information about a certain topic.
Checkpoint: Indicates that a particular step needs to be checked before proceeding

further.
Tip: Indicates a suggestion or hint to make things easier or more productive for the
reader.
II
Chapter 1
System Overview
Table of Contents
Introduction to ZXONE 5800.......................................................................................1-1
Application of ZXONE 5800........................................................................................1-3
1.1 Introduction to ZXONE 5800

ZXONE 5800 is a multi-service core optical cross-connect equipment, which
effectively meets the grooming and scheduling requirements of the high-capacity and
large-granularity traffic.
l Compliant Standards
Based on the SDH system, ZXONE 5800 complies with the ITU-T G.707 mapping
structure.
l Service Functions
A single subrack of ZXONE 5800 provides 40 board slots. The equipment provides
STM-1, STM-4, STM-16, STM-64, GE, and 10 GE optical interfaces. It supports the
transparent transmission of GE services and convergence of GE and 10 GE services.
l Intelligent Characteristic
ZXONE 5800 also supports ASON functions by providing an independently-running
intelligent software system. With this software system, ZXONE 5800 can implement
the functions of dynamic bandwidth allocation, intelligent service routing and
configuration, etc., which effectively improve the bandwidth utilization ratio in network.
l Cross-Connection Capacity and Granularity
ZXONE 5800 provides a maximum access capacity of 1.28 T. The cross-connection
granularity is VC4.
ZXONE 5800 also provides the lower-order cross-connection capability of 160 G with
the granularity of TU3/TU12.
l EMS Software
The Element Management System (EMS) NetNumen T31 is used to manage ZXONE
5800. As a distributed, multi-process and modularized system, NetNumen T31
provides the functions of configuration management, fault management, performance
management, maintenance management, end-to-end circuit management, security
management, system management, and report management.
l Protection Function
1-1
SJ-20111121090706-001|2012-02-20(R1.1) ZTE Proprietary and Confidential

ZXONE 5800 System Descriptions
Featuring high system reliability and stability, ZXONE 5800 has perfect equipment
and network protection capability. The equipment protection modes include 1+1 hot
backup for the important boards, 2:4 protection for the higher-order cross-connect
boards, 1:4 protection for the lower order cross-connect boards, etc. The network
protection modes include 1+1 or 1:N linear multiplex section (MS) protection, two
fiber bidirectional MS shared protection ring (with extra traffic), four fiber bidirectional
MS shared protection ring (with extra traffic), Sub-Network Connection Protection
(SNCP), SDH logical sub-network protection, mesh networking protection, and
rerouting protection.
l Application Scope
ZXONE 5800 can be widely deployed on the backbone layer in long haul networks and
the core layer in metropolitan area networks with its high cross-connection capacity,
multiple cross-connection granularity and perfect protection mechanisms.
l Equipment Structure
As a core component, the subrack of ZXONE 5800 is installed in a cabinet meeting the
ETS standard, whose height can be 2000 mm, 2200 mm or 2600 mm. The subrack
has a three-layer structure. A cabinet can only accommodate one subrack. Figure
1-1 shows the outline of ZXONE 5800 subrack in a cabinet.
1-2

Chapter 1 System Overview
Figure 1-1 Outline of ZXONE 5800 Subrack in Cabinet
1.2 Application of ZXONE 5800

As a junction center for high-capacity scheduling, ZXONE 5800 is mainly used at the
metro-area core layer and long haul backbone layer, supporting the adding/dropping and
scheduling of high-capacity large-granularity traffic.
ZXONE 5800 can integrate the whole transmission network into one system, which
significantly increases the utilization ratio of the network resource. If configured with the
ASON functions, ZXONE 5800 can transport different types of services over the network,
and provide protection and restoration of different levels.
1-3

This page intentionally left blank.
1-4

Chapter 2
Hardware Architecture
Table of Contents
Cabinet ......................................................................................................................2-1
Subrack......................................................................................................................2-3
Boards .......................................................................................................................2-4
Functional Units .........................................................................................................2-5
Functional Planes.......................................................................................................2-7
2.1 Cabinet
This section describes the ZXONE 5800 cabinet and its technical specifications.
Cabinet Outline and Configuration

ZTE unified transmission equipment cabinet is used for ZXONE 5800. It complies with the
ETS standard.
The cabinet has front and rear columns and a front door which can be opened. Figure 2-1
shows the outline of the cabinet.
2-1

Figure 2-1 ZXONE 5800 Cabinet
Technical Specifications
The technical specifications of the ZXONE 5800 cabinet are listed in Table 2-1.
Table 2-1 Dimensions and Weight of Cabinet
Cabinet Type (Height × Width × Depth, mm) Weight (kg)
2000×600×300 59
2200×600×300 65
2-2

Chapter 2 Hardware Architecture
2.2 Subrack
Subrack Structure
The subrack of ZXONE 5800 has a three-layer structure. It can be mounted in an ETS
cabinet with 600 mm width and 300 mm depth. Figure 2-2 shows the structure of ZXONE
5800.
Figure 2-2 Subrack Structure
1. Top cover board 4. Board area 7. Fiber tray

2. Lintel 5. Cabling area 8. Mounting flange
3. Fan plug-in box 6. Dust-proof unit 9. Fiber holder
Technical Specifications
Table 2-2 lists the technical parameters of the ZXONE 5800 subrack.
Table 2-2 Technical Parameters of the ZXONE 5800 Subrack
Dimension (Height × Width × Depth, mm) Weight (kg)
1349 × 497 × 270 38.5
• The dimension of the subrack does not include that of the mounting flanges of the subrack. The
weight of the subrack is that of an empty subrack with backplane, but without boards, fan plug-in box
and dust-proof unit.
2-3

2.3 Boards
2.3.1 Board List
Boards of ZXONE 5800 are listed in Table 2-3.
Table 2-3 Board List
Board Code Board Name
MB Mother board
NCPA Net control processor, type A
NCPB Net control processor, type B
SAIA System application interface, type A
HOXA Higher-order cross-connect, type A
HOXB Higher-order cross-connect, type B
LOXA Lower-order cross-connect, type A
S64Ax4 4–port STM-64 optical line, type A
S64A Single-port STM-64 optical line, type A
S64AFECx4 4–port STM-64 FEC optical line, type A
S64AFECx2 2–port STM-64 FEC optical line, type A
16Ax8 Single-port STM-64 FEC optical line, type A
S4Ax16 16–port STM-4/1 optical line, type A
S4Ax8 8–port STM-4/1 optical line, type A
SGEAx8 8–port transparent gigabit Ethernet, SDH, type A
SGEAx4 4–port transparent gigabit Ethernet, SDH, type A
SGESx8 8–port GE Ethernet processor, SDH, type S
SGESx4 4–port GE Ethernet processor, SDH, type S
STGSx2 2–port 10GE Ethernet processor, SDH, type S
OAx2 2–port optical amplifier
OA Single-port optical amplifier
PWRA Power board
FAN Fan unit board
• The fan unit board consists of a Fan Mother Board (FMB), a Fan Control Processor (FCP) board, and a Fan LED
(FLED) board.
2-4

2.3.2 Classification of Boards

In terms of function, the boards of ZXONE 5800 can be divided into the following two
classes.
l Functional boards: NCPA, SAIA, HOXA, HOXB, LOXA, OAx2, OA, and PWRA board
l Service boards: optical line boards (including S64Ax4, S64Ax2, S64A, S16Ax8,
S16Ax4, S4Ax16 and S4Ax8), GE transparent transmission boards (including
SGEAx8 and SGEAx4), and convergence board (STGSx2)
2.4 Functional Units

2.4.1 Relationship Between Functional Units
In terms of function, the hardware system of ZXONE 5800 can be partitioned into power
supply unit, clock unit, cross-connect unit, service management unit, electromechanical
management unit, SDH service interface unit, and ASON control unit. Among them, the
SDH service interface unit contains two parts, SDH line unit and data access unit.
Figure 2-3 illustrates the logical relationship between the functional units of ZXONE 5800.
Figure 2-3 Relationship Between the Functional Units of ZXONE 5800
2.4.2 Introduction to Functional Units

Each functional unit of ZXONE 5800 is briefly described as follows.
l Power Supply Unit
Dual -48 V power supplies are respectively connected to two power supply boards
installed in the equipment subrack. In this way, 1+1 hot backup of power supply is
2-5

available. The power supply boards implement the functions of power distribution,
input filtering, lightning and surge protection, overcurrent protection, input overvoltage
and undervoltage detection and report, and undervoltage turn-off.
Each service board implements the power-related functions of hot backup of power
supply, reverse connection prevention of DC power supply, soft start and power supply
management.
l Clock Unit
The clock unit provides a unified system clock to all the other boards in the equipment.
The clock unit also supports 1+1 backup. Both the active and the standby clock
units output a group of clock signals to each slot in the subrack. Service boards
and cross-connect boards select one group of clock signals from these two available
groups as their active clock signals.
In addition, the clock unit can select an external clock or extracted clock as the
reference clock source according to actual configuration, to get a synchronous
running status of network. Two external clocks can be input from the equipment
subrack. And each service board slot supports the extracting of two clocks from lines.
l Cross-Connect Unit
The cross-connect unit can be a higher-order cross-connect unit or a lower-order one.
A higher-order cross-connect unit implements the flexible allocation of payloads
and overheads as well as non-blocking higher-order cross-connection at VC4 level.
Higher-order cross-connect boards installed in the equipment subrack complete the
high-order cross-connect function.
Each higher-order cross-connect board HOXA in ZXONE 5800 provides the maximum
higher-order cross-connect capacity of 160 G. Each higher-order cross-connect board
HOXB provides the maximum higher-order cross-connect capacity of 320 G. ZXONE
5800 can be configured with six cross-connect boards at most. Two of them are
used as standby boards to provide 2:4 backup protection. When configured with the
HOXA boards, the system provides a maximum higher-order cross-connect capacity
of 640 G; when configured with the HOXB boards, the system provides a maximum
higher-order cross-connect capacity of 1.28 T.
A lower-order cross-connect unit provides the cross-connect capacity of 160 G based
on the granularity of VC3/VC12. Lower-order cross-connect is implemented by the
lower-order cross-connect board, which is installed in the 40 G service board slot. Five
lower-order cross-connect boards can be configured at the same time to implement
1:4 backup protection.
l Service Management Unit
The service management unit receives commands from an EMS and reports
information to it so as to implement the configuration, management and maintenance
of each board in the equipment.
l Electromechanical Management Unit
2-6

The electromechanical management unit supports the functions of board power-on

control, reset control, temperature detection, board information querying, board
operation log processing and power distribution control.
l ASON Control Unit
The ASON control unit, as an intelligent management unit, allows automatic
connection establishment and automatic resource discovery in optical transport
network under the control of ASON signaling protocols. The ASON control units of the
NEs in an optical transport network cooperate with each other via an ASON signaling
system to implement the intelligent management and connection automatization.
Moreover, they start rerouting in case of network failure to protect and recover SDH
traffic in the network.
l SDH Service Interface Unit

The SDH service interface unit comprises two units: SDH line unit and data access
unit.
The SDH line unit supports the access of STM-1, STM-4, STM-16 and STM-64
service signals. It converts these signals into required formats and forwards them to
corresponding cross-connect units for convergence and allocation.
l Data Access Unit
The data access unit supports the access of GE transparent transmission service and
10 GE convergence service. It maps the service signals into cascaded VC4s and then
forwards them into corresponding cross-connect unit for convergence and allocation.
2.5 Functional Planes

In terms of functional plane, the hardware system of ZXONE 5800 can be divided into
Transport Plane (TP), Management Plane (MP) and Control Plane (CP). Figure 2-4
illustrates the relationship between these three functional planes.
Figure 2-4 Relationship Between the Functional Planes
2-7

Each functional plane is described as follows.

l Transport Plane
The transport plane is composed of the cross-connect unit, clock unit and the SDH
service interface unit. It receives management commands from both the management
plane and the control plane. The transport plane, having the cross-connect unit as the
core, supports the cross-connection, scheduling and transmission of various service
signals accessed from the SDH service interface unit. At the same time, it provides
hardware channels for the management of the other two planes.
l Management Plane
The management plane is composed of the service management unit. It supports the
management and configuration of NEs by means of EMS GUI or command lines.
l Control Plane
The control plane supports automatic establishment of connections and automatic

discovery of resources in an optical network under the control of signaling protocols
to implement the intelligent management. The control plane is composed of control
NEs in an optical network. These control NEs, cooperates with each other through
an ASON signaling system. In addition, it starts rerouting in case of network failure to
perform the protection and recovery of the accessed services.
2-8

Chapter 3
Software Architecture
Table of Contents
Overview of Software Architecture..............................................................................3-1
Intelligent Software.....................................................................................................3-1
Board Software ..........................................................................................................3-2
Agent Software...........................................................................................................3-2
EMS Software ............................................................................................................3-3
Communication Protocols and Interfaces ...................................................................3-4
3.1 Overview of Software Architecture

The system software of ZXONE 5800 comprises board software, Agent and NetNumen
T31 EMS, which run on each board, NE control processor board and EMS computer
respectively. It implements the management and control of boards, NEs and the whole
network.
The ZXONE 5800 software adopts layered structure design with each layer implementing
specific function and providing service to the upper layer. The software structure is shown
in Figure 3-1.
Figure 3-1 Software Structure of ZXONE 5800
3.2 Intelligent Software

ZXONE 5800 can be loaded with the ASON intelligent software to implement intelligent
control of the equipment. The intelligent software is independent of the system software.
It is loaded to the NE control processor board as a software module.
The loaded intelligent software provides an independent control plane, with which
the capabilities of maintaining dynamic connection, routing and signaling processing,
3-1

automatic discovery, connection control and protection/recovery are available in the

whole optical network.
In addition, the optical network supports real-time bandwidth allocation on actual demands
for the traffic engineering of optical channels, which makes it easy to introduce various new
value-added services to the network.
3.3 Board Software

The board software runs in each board to manage, supervise, and control the board
operation.
Each board receives EMS commands forwarded by the Agent in the NE control processor
board, and then performs corresponding processing, gives responses and reports alarm,
performance and event information to the EMS.
The board software has the following functions: alarm, performance and event processing,
configuration management, communication management, automatic protection switching,
online software downloading, and functional circuit driving.
3.4 Agent Software

Agent, located on the NE control processor board of an NE, acts as a service unit that
supports the communication between an EMS and the boards in an NE. It allows the EMS
to monitor, control and manage the NE. In summary, an Agent has the following functions:
l Configure each board during initialization after the NE is powered on.
l Monitor alarms and performances of the normally-running NE, receive monitoring and
configuration commands issued by the EMS from the gateway NE in its network and
report processing results, alarms and performances via the ECC interface.
The gateway NE is connected to the EMS through the Qx interface on the system
interface board. The LCT interface of the NE control processor board can also be
used to connect the Agent to an EMS. NEs can be managed by means of command
lines.
In terms of function, Agent is composed of the following modules.
l Embedded Operating System Platform
This platform is responsible for the management of public resources. It provides a

hardware-independent execution environment for applications.
l Communication and Control Module
This module acts as an interface module supporting the information exchange

between the Agent and the other board software in an NE. It issues maintenance or
operation commands to corresponding boards from the Agent.
At the same time, this module collects status, alarm, performance and event
information of each board and reports it to the Agent.
3-2

Chapter 3 Software Architecture
l Equipment Management Module

This module is a critical part of Agent to implement the management of corresponding
NE, through which the Agent issues network management commands.
l Communications Module
This module supports the exchange of management information between an EMS
and an NE, and that between two NEs.
l Database Management Module
This module manages and accesses alarm, performance, event, equipment and
network information collected by Agent.
3.5 EMS Software

The EMS software NetNumen T31 is used to manage and monitor the ZXONE 5800 NEs.
It provides the functions of configuration management, fault management, performance
management, maintenance management, end-to-end circuit management, security
management, system management, and report management.
Figure 3-2 illustrates the architecture of the EMS software.
Figure 3-2 Architecture of the EMS Software
l Manager
It is also called "Server". Manager acts as the server of GUI. It exchanges information
with Agent via the Qx interface. Manager provides the following functions.
à Receive requests from GUI, analyze the requests and forward related information
to Agent or send the information to Database.
à Receive processed information from the database, analyze the information and
forward it to GUI
3-3

à Receive the information from Agent, analyze the information and then forward it
to Database or GUI
l GUI
It is also called "Client". GUI has the following functions.
à Provide graphical user interface for users.
à Provide service interfaces for configuration management, fault management,
performance management, security management, maintenance management,
system management and online help.
à Support user security control.
l Database
Database provides the following functions.
à Support the query of information of interfaces and management functional
modules.
à Store the configuration information, alarm information, etc.
à Keep data consistency between Database and Agent.
3.6 Communication Protocols and Interfaces

The communication interfaces in the software system of ZXONE 5800 and the
corresponding communication protocols used by them are introduced in Table 3-1.
Table 3-1 Communication Interfaces in ZXONE 5800 Software System
Interface Description
S interface is the communication interface between the Agent on the NE control pro-
S interface
cessor board and the other boards in an NE. It complies with a private protocol.
Intelligent Platform Management Interface (IPMI) is an interface used for the commu-
IPMI inter- nication of intelligent platform management information between the Agent on the NE
face control processor board and the other boards in an NE. It complies with a private pro-
tocol.
Qx interface is the communication interface between Agent and Manager, that is, the
interface between the NE control processor board and the computer where the EMS
Qx interface
software is running. As to ZXONE 5800 equipment, it is located on the SAIA board. It
complies with the TCP/IP protocols, ITU-T Q.811 and ITU-T Q.812 recommendations.
f interface is the communication interface between Agent and a Local Craft Terminal
f interface
(LCT). It is an Ethernet interface complying with TCP/IP.
ECC inter- Embedded Control Channel (ECC) interface is the communication interface between
face NEs. It complies with TCP/IP.
3-4

Chapter 4
System Functions
Table of Contents
Service Function ........................................................................................................4-1
Cross-Connection Function ........................................................................................4-2
System Control and Communication Functions ..........................................................4-3
Overhead Processing Functions.................................................................................4-3
Clock Functions..........................................................................................................4-4
Alarm Function ...........................................................................................................4-5
Performance Detection Function ................................................................................4-5
Optical Amplification Function ....................................................................................4-6
Protection Function ....................................................................................................4-7
Online Upgrade of Board Software .............................................................................4-8
ASON Functions ........................................................................................................4-8
4.1 Service Function

4.1.1 Service Types
ZXONE 5800 supports the access of SDH services and Ethernet services. Refer to Table
4-1 for details.
Table 4-1 Types of Services Supported By ZXONE 5800
Service Type Compliant Standard Rate
STM-1 ITU-T G.707 155.52 Mbit/s
STM-4 ITU-T G.707 622.08 Mbit/s
SDH service STM-16 ITU-T G.707 2.488 Gbit/s
STM-64 ITU-T G.707 9.953 Gbit/s
STM-64 FEC ITU-T G.709 10.709 Gbit/s
GE IEEE 802.3 1.25 Gbit/s

Ethernet service
10GE IEEE 802.3ae 9.953 Gbit/s or 10.313 Gbit/s
4.1.2 Service Access Capability

Refer to Table 4-2 for the service access capacity of ZXONE 5800.
4-1

Table 4-2 Service Access Capacity of ZXONE 5800
Service Type Corresponding Board Access Capacity of Access Capacity of Subrack

Board (Channel/Subrack)
(Channel/Board)
Higher-order cross-connect board HOXA
STM-64 FEC S64AFEC 4 64
S64Ax4, S64Ax2 and

STM-64 4 64
S64A
STM-16 S16Ax8 and S16Ax4 8 160
GE
transparent SGEAx8 and SGEAx4 8 320
transmission
GE
SGESx8 8 320
convergence
10 GE
STGSx2 2 80
convergence
Higher-order cross-connect board HOXB
STM-64 FEC S64AFEC 4 96
S64Ax4, S64Ax2 and

STM-64 4 96
S64A
GE
transparent SGEAx8 and SGEAx4 8 320
transmission
GE
SGESx8 8 320
convergence
10 GE
STGSx2 2 80
convergence
4.2 Cross-Connection Function

ZXONE 5800 provides two kinds of cross-connect boards: lower-order cross-connect
board and higher-order cross-connect board.
4-2

Chapter 4 System Functions
l The lower-order cross-connect board provides the function of cross-connection on

VC12 or VC3 level with the capacity of 40 G. It supports 1:4 board protection at most.
l The higher-order cross-connect board HOXA provides the function of non-blocking
cross-connection on VC4 level with the maximum capacity of 160 G. The higher-order
cross-connect board HOXB provides the function of non-blocking cross-connection on
VC4 level with the maximum capacity of 320 G. At least four higher-order cross-con-
nect boards should be configured in a ZXONE 5800 system and six can be configured
at most to support 2:4 board protection.
Table 4-3 lists the cross-connection capacity of the ZXONE 5800 system.
Table 4-3 Cross-Connection Capacity of ZXONE 5800
Cross-Connect Level Cross-Connect Capacity in Single Subrack
VC4 (configured with HOXA) 4096×4096 VC4 (640 G)
VC4 (configured with HOXB) 8192×8192 VC4 (1.28 T)
VC3 3072×3072 VC3 (160 G)
VC12 64512×64512 VC12 (160 G)
4.3 System Control and Communication Functions

The system control and communication functions of ZXONE 5800 are implemented by the
NE control processor board, including
l Issue configuration commands to the boards and collects their performances, alarms,
and events.
l Select route between NEs and implement the communication of management
information between NEs via ECC.
l Report the alarm and performance information of the subnetwork where the local NE
is located to corresponding Subnetwork Management Control Center (SMCC) via the
Qx interface, and receive management and configuration commands sent from the
SMCC. Qx interface is the communication interface between an NE and an SMCC.
l Implement the management and configuration of NEs by means of command lines
via the f interface (that is, the LCT interface).
l Provide a hardware platform for loading the ASON control plane, through which the
intelligent management function of NEs is available.
l Implement the integrated control and management of the electromechanical platform
in ZXONE 5800 subrack.
4.4 Overhead Processing Functions

The overhead processing functions of ZXONE 5800 is performed by optical line boards,
cross-connect boards and NE control process board cooperatively.
ZXONE 5800 provides the following overhead processing functions.
4-3

l Separate Section Overheads (SOHs) and payloads from SDH frames.

l Transfer the ECC and ASON control information via the Data Communication Channel
(DCC).
l Support overhead transparent transmission.
4.5 Clock Functions

The clock function of ZXONE 5800 is integrated in the NE control processor board, which
supports 1+1 backup protection of clock. The NE control processor board provides a group
of active clock signals and a group of standby clock signals to each slot in ZXONE 5800
subrack. Service boards and cross-connect boards select one group of clock signals as
the active one according to the active/standby control signal. The clock functions provided
by ZXONE 5800 are described as follows.
1. Clock Source Selection
External clocks, extracted clocks from STM-N (N=1, 4, 16, 64) interfaces and internal
clocks can be selected as the timing reference of the ZXONE 5800 equipment. ZXONE
5800 supports four clock modes: fast pull-in mode, tracking mode, holdover mode
and free running mode. A ZXONE 5800 subrack can provide two channels of external
reference clock signals (2 MHz or 2 Mbit/s). Each service board slot supports two
channels of extracted clock signals.
2. Clock Source Switching
The switching of clock source occurs when the current clock source is lost, a
clock source with higher quality recovers or the current clock source degrades to a
lower quality level. ZXONE 5800 supports both system clock switching based on
synchronization priority and automatic clock switching based on SSM algorithm. In
a complex network, the automatic clock switching based on the SSM algorithm can
optimize the timing distribution in the network, simplify the synchronization planning
and avoid timing loop so as to guarantee the optimal synchronization of the whole
network.
3. Clock Input and Output
The ZXONE 5800 subrack provides two channels of output external reference clock
signals and two channels of input external reference clock signals via corresponding
physical interfaces on the SAIA board. Each SAIA board provides a 75Ω clock
interface and a 120Ω clock interface, which can be configured as a 2 Mbit/s interface
or 2 MHz interface. Two SAIA boards can be configured in a subrack at the same
time to implement the protection and backup of clock interfaces.
4-4

4.6 Alarm Function

4.6.1 Alarm Input/Output Functions
The NE control processor board of ZXONE 5800 collects the alarm signals from
corresponding NE and forwards them to an alarm box or column-head cabinet through
SAIA board in the same NE. At the same time, it receives the external alarm signals.
ZXONE 5800 provides the following alarm input/output functions.
l Support the input of eight channels of external on-off alarm signals via the alarm input
interfaces (S_ALMIN1 and S_ALMIN2) on the front panel of SAIA board.
l Support the output of three channels of on-off alarm signals and one channel of on-off
ring trip signal via the alarm output interface (S_ALMOUT) on the front panel of SAIA
board.
l Support the output of five channels of subrack alarm signals via the subrack alarm
output interface (E_ALMOUT) on the front panel of SAIA board, including ring alarm
signal, minor alarm signal, major alarm signal, critical alarm signal and normal power
supply indication signal.
l Support the input and management of four channels of tandem on-off alarm signals
via the alarm tandem input interface (ALMTandemIN) on the front panel of SAIA board.
4.6.2 Alarm Detection Function

ZXONE 5800 supports not only the detection of common SDH alarms (such as
regenerator/multiplex section alarms and higher/lower-order channel alarms) but also the
detection of ASON alarms. The detection of ASON alarms include the query and report
of alarms on the control plane, alarm mask setting, and alarm notification of the transport
resources.
4.7 Performance Detection Function

ZXONE 5800 supports the detection of SDH digital performance, analog performance,
Ethernet performance and ASON performance.
l SDH Digital Performance Detection
Refer to Table 4-4 for the SDH digital performance items that can be detected by
ZXONE 5800.
Table 4-4 SDH Digital Performance Items Detected by ZXONE 5800
Detection Point Detected Performance
Regenerator section SD, EXC, BBE, ES, SES, UAS, CSES, and OFS
SD, EXC, BBE, ES, SES, UAS, CSES, FEBBE, FEES, FESES,
Multiplex section
FEUAS, and FECSES
4-5

SD, EXC, BBE, ES, SES, UAS, CSES, FEBBE, FEES, FESES,
VC4/VC3/VC4-nc/VC3-nc
FEUAS, and FECSES
AU4/AU4-nc PJE+ and PJE-
l Analog Performance Detection

Refer to Table 4-5 for the SDH analog performance items that can be detected by
ZXONE 5800.
Table 4-5 Analog Performance Items Detected by ZXONE 5800
STM-1 to STM-64 physical inter- Received optical power, transmitted optical power, laser
faces (optical) working current (bias current), and laser temperature
Received optical power, transmitted optical power, module

EDFA temperature, laser TEC current, laser working current, and
laser temperature
Temperature Temperature at detection points
Board voltage Voltage
l Ethernet Performance Detection

Refer to Table 4-6 for the Ethernet performance items that can be detected by ZXONE
5800.
Table 4-6 Ethernet Performance Items Detected by ZXONE 5800
Number of received/sent frames, number of re-

Ethernet user port ceived/sent bytes, and the number of received/sent
broadcast/multicast/unicast frames
Number of received/sent GFP frame bytes, number of

VCG (EOS) port received/sent GFP customer data frames, and the num-
ber of received/sent GFP free frames
l ASON Performance Detection

Refer to the Unitrans ZXUCP A100 (V1.20) Unified Control Plane User Manual for the
ASON performance items that can be detected by ZXONE 5800.
4.8 Optical Amplification Function

ZXONE 5800 can support non-regenerator long-haul transmission with the application of
optical line boards and optical amplifier (OA) boards. The rate of optical line boards can
be STM-1, STM-4, STM-16 or STM-64. The wavelength of light source must be 1550 nm.
4-6

The OA boards of ZXONE 5800 can integrate the functions of OPA and OBA, which can
be realized by replacing EDFA modules in the boards.
4.9 Protection Function

4.9.1 Equipment-Level Protection
Power Supply Protection
l Out-of-cabinet power protection
Two groups of -48 V power supplies in the equipment room are introduced into the
ZXONE 5800 cabinet, which are connected to two power supply boards in a subrack
respectively. The 1+1 protection mode is adopted for the external power supply. The
ZXONE 5800 equipment can keep running normally when either group of external
power supply fails, or when one of the two power supply board fails or is unplugged
from slot.
l Board power supply protection
The service boards adopt the distributed power supply mode to reduce the power
influence between boards to zero. All boards support overcurrent and overvoltage
protection.
The design of the boards in ZXONE 5800 follows the principle that electromechanical
management functions and service management functions are separated. With the
electromechanical management functions, the power-on sequence of boards can
be controlled, which can effectively avoid system abnormity caused by centralized
power-on of all boards.
NCP (ASON) and Clock Protection

The NE control processor board of ZXONE 5800 comprises NCP (ASON) unit and clock
unit. Two NE control processor boards can be configured at the same time to implement
1+1 protection.
The active NCP (ASON) unit backs up the information in its database to the standby NCP
(ASON) unit during normal running. The service board communicates with the active NCP
(ASON) unit.
Both the active and the standby clock units provide a group of clock signals to service
boards. Each service board selects one from these two groups according to the working
status of the active and the standby clock units.
Cross-Connect Protection
ZXONE 5800 provides the higher-order cross-connect and lower-order cross-connect
functions.
4-7

Higher-order cross-connect boards support 2:4 protection. With this protection mode
configured in a ZXONE 5800 system, the cross-connection function can keep normal
when any two higher-order cross-connect boards fail.
Lower-order cross-connect boards support 1:N (N≤4) protection.
1+1 Protection of SAIA Board

ZXONE 5800 can be configured with two SAIA boards to provide 1+1 protection of clock
input/output interfaces.
4.9.2 Network-Level Protection

ZXONE 5800 with strong network self-healing capability supports traditional SDH
network-level protection modes, logical sub-network protection and Mesh protection as
follows.
l 1+1 or 1: N linear multiplex section (MS) protection
l Two-fiber bidirectional MS shared protection ring (with extra traffic or without extra
traffic), and four-fiber bidirectional MS shared protection ring (with extra traffic or
without extra traffic)
l Sub-Network Connection Protection (SNCP)
The SNCP supports SNC (I), SNC (N), and SNC (I) + SD.
l Logical Sub-Network Protection
The logical sub-network protection is a new protection mode presented by ZTE
Corporation, which is based on ITU-T recommendations. ZXONE 5800 supports the
protection of more complex networks with higher security and improved bandwidth
utilization ratio.
l Mesh Protection
ZXONE 5800 with loaded ASON control plane supports the protection of mesh
networks. This protection mode can effectively improve network reliability and
bandwidth utilization ratio.
4.10 Online Upgrade of Board Software

ZXONE 5800 supports the remote online upgrade of board software for convenient
equipment maintenance.
4.11 ASON Functions

4.11.1 End-to-End Service Configuration
End-to-end service configuration is supported in the ASON.
4-8

For an SPC service, users only need to specify the first node, last node,
protection/restoration properties of the service. Then the control plane uses the routing
protocol to select a service route automatically. Meanwhile, the control plane uses the
signaling protocol to configure cross-connection for the service node by node.
When establishing an SPC service, you need to set the following service properties:
l First node
l Last node
l Bandwidth information
l Protection property
l Restoration property
l Retry times after failure of service setup
l Routing Policy
à Included nodes and included links
à Excluded nodes, excluded nodes and excluded SRLG
à Detached connection
As shown in Figure 4-1, the EMS issues a command to establish a VC4 service from NE
1 to NE 3, then according to the routing policy, the control plane selects the best route:
NE1→NE5→NE3. According to the procedure described in the "Creating LSP" section, the
control plane establishes cross-connection on each node to complete the service setup.
Figure 4-1 End-to-End Service Configuration
4.11.2 Restoration of Mesh Network

The ASON control plane supports the restoration of mesh network. Compared with the
traditional network, the restoration of mesh network does not need to reserve 50% of the
4-9

network resource, and as long as the network resource allows, the restoration path can still
be found after many times of faults. The utilization ratio of network resource is increased.
As shown in Figure 4-2, when the fiber between NE 1 and NE 5 fails, the first
node NE 1 initiates rerouting, and finds a restoration path indicated with a blue line
(NE1→NE2→NE6→NE3), then the service is switched to the new path for transport.
If the new service path fails, the first node can use the existing network resource to find
another new service path.
Figure 4-2 Restoration of Mesh Network
4.11.3 ASON Service Levels

ASON can conveniently divide services by priority according to user requirements, to
provide services complying with Service Level Agreement (SLA).
In ASON, service levels are implemented by configuring services as different protection
types and restoration types.
The service levels supported by ZXONE 5800 are listed in Table 4-7.
Table 4-7 ZXONE 5800 Service Levels
Ser- Optimiza- Protection

Protection Restoration
vice Rerouting Reversion tion of Switching
Type Time
Level Rerouting Time
Permanent
1 1+1 path Supported Supported Supported <50 ms <2 s
protection
4-10

Ser- Optimiza- Protection

Protection Restoration
vice Rerouting Reversion tion of Switching
Type Time
Level Rerouting Time
Total MS
2 Supported Supported Supported <50 ms <2 s
protection
1+1 path
protection
1:N path
protection
5 No protection Supported Supported Supported — <2 s
6 Extra service — — Supported — —
• "-" indicates no such a property.
Level 1 Service
Level 1 service is a permanent 1+1 path protection service, which includes two
connections: working connection and protection connection. The two connections form
1+1 protection relation.
According to the setting of routing policy, the trails of two connections should be completely
independent. When any one of the connections fails, the first node will reroute immediately,
establishing a new connection to replace the faulty one, and generate a new 1+1 protection
relation.
Therefore, for a level 1 service, two connections are available at any time as the network
resource allows, as shown in Figure 4-3.
When the working connection fails, the service is switched to the protection connection.
The switching time is less than 50 ms.
4-11

Figure 4-3 Level 1 Service
Other service properties supported by level 1 service:

l Supports rerouting lockup.
l Supports optimization of working connection and protection connection.
l Supports modification for initial connection.
Level 2 Service
Level 2 service is a total MSP service, which only contains one working connection.
All the trails by which the working connection of the level 2 service passes enable the
Multiplex Section Protection (MSP). When the working connection fails, the MS protection
of transport plane will be used first to restore the working connection. The switching time
of MSP is less than 50 ms.
When the MSP fails, the control plane will enable rerouting to search for a new restoration
connection for the service. After the restoration connection is set up, the service is switched
to the restoration connection. The service restoration time is generally less than 2 s.
After the fault of working connection disappears, the service will revert to the original
working connection, and the restoration connection is deleted.
Figure 4-4 shows the level 2 service.
4-12

Figure 4-4 Level 2 Service

l Supports optimization of working connection.
l Supports the setup of level 2 services on the working links of all MS shared protection
rings and linear MS links.
l Supports automatic reversion or manual reversion.
l After the service is switched to the restoration connection, if the restoration connec-
tion is still on the trail of MSP, the original trail of the service can be modified to the
restoration connection.
Level 3 Service
Level 3 service is a 1+1 path protection service, which includes two connections: working
connection and protection connection. The two connections form 1+1 protection relation.
When the working connection fails, the service is switched to the protection connection.
The switching time is less than 50 ms.
When both the working connection and the protection connection fail, the service is
interrupted.

l Supports optimization of working connection and protection connection.
l Supports modification for initial connection.
4-13

Level 4 Service
Level 4 service is a 1:N (1≤N≤15) protection group set up by the control plane. N working
connections share one protection connection. When any one of the working connections
fails, the protection switching is implemented by the control plane. The switching time is
generally less than 200 ms. If the protection connection also fails after that, the working
connection will either start restoration (with restoration property) or fail.
The working connections in the 1:N (1≤N≤15) protection group must be configured with
different priorities (ranging from 1 to 15, and smaller value with higher priority). When
multiple working connections in a protection group fail at the same time, the working
connection with the highest priority will implement protection switching, while other
working connections with lower priorities will either enable restoration (with restoration
property) or fail.
Level 5 Service
Level 5 service is an unprotected service, which only contains one working connection.
When the working connection fails, the first node initiates rerouting to establish a new
restoration connection, and the service is switched to the restoration connection. The
service restoration time is generally less than 2 s.
l Supports optimization of working connection.
l The revertible level 5 service supports modifying the restoration connection to the
initial trail of the service after restoration occurs.
Level 6 Service
Level 6 service is an extra service, which only contains one working connection.
The connection of an extra service prefers to use the resource of protection links in the MSP
protection group, and then uses the resource of unprotected links. When service protection
switching occurs in the MSP protection group, the extra service will fail. When the network
resource is inadequate, establishing or restoring the connection of other non-extra service
will preempt the resource occupied by the working connection of the extra service.
Other service property supported by level 6 service: Supports optimization of working
connection.
4.11.4 Conversion Between Service Levels
Caution!
The conversion between service levels may cause transient interruption of services.
4-14

ZXONE 5800 supports the following conversion between intelligent services:

l Conversion between level 1 and level 3 services
Note:
In ZXONE 5800, the conversion between service levels is implemented by modifying the
properties of service protection, restoration, and reversion.
4.11.5 Service Optimization Function

Under the following situations in the ASON network, the trails of service connections may
not be the best, and service optimization is recommended.
l Faults occur for many times, and the trails of service connections also change for
many times accordingly.
l The network topology is changed.
Principles of service optimization: based on the latest network resource, a best connection
(LSP) is created, and the service is switched to the new connection; then the original
connection is deleted.
In service optimization, the route strategy of the service can also be reset.
Except for service level 4, all other service levels support the optimization function.
Note:
When a service is busy or it has a restoration connection, optimization is not allowed.
4.11.6 Tunnel Services

Generally, ASON only carries services with a rate of VC4 or higher. When carrying services
with lower rates, the tunnel technology is adopted for transport.
When establishing a tunnel service, a tunnel LSP is established first, and then the service
with lower rate is cross connected to the tunnel at the first node and last node. The service
with lower rate is transported through the tunnel, as shown in Figure 4-5.
4-15

Figure 4-5 Tunnel Services
A tunnel LSP can carry multiple lower-rate services. For example, a tunnel LSP can carry
63 VC12 services.
Note:
At present, ZXONE 5800 can carry VC12 and VC3 lower-rate services.
4.11.7 Service Association

ZXONE 5800 can associate two unprotected services with the same property, to form a
cross-domain 1+1 SNCP protection relation.
The associated services are not a complete 1+1 SNCP in the local domain, or they are only
two services with separate trails. They are used to form a 1+1 SNCP protection relation
with two cross-domain end-to-end services.
When a service is being restored, the route of its associated service cannot be chosen,
even it is the best restoration route.
At present, ZXONE 5800 supports two types of associated services: 1+1 associated
service and non 1+1 associated service.
1+1 Associated Service

An end-to-end service passes through the ASON network and the traditional SDH
network. From the end-to-end perspective, a 1+1 path protection is formed, supported by
1+1 associated service in the ASON domain, as shown in Figure 4-6.
4-16

Only the two services with the same first node but different last node are associated. These
two services has a 1+1 protection relation at the first node.
Figure 4-6 1+1 Associated Service Diagram 1
In Figure 4-6, the transmit/receive timeslots of the first node service in the ASON domain
form a protection relation of "concurrent transmitting and preferred receiving"; generally,
there are two last nodes in the ASON domain (or only one node, but with two service exit
timeslots, as shown in Figure 4-7), which are connected to the SDH network respectively.
4-17

Figure 4-7 1+1 Associated Service Diagram 2
Caution!
The two services for 1+1 association must be unprotected services, and they must have
the same property.
Non 1+1 Associated Service

An end-to-end service goes through the ASON network and then to the traditional SDH
network. From the end-to-end perspective, a 1+1 path protection is formed. From the
ASON domain perspective, the two connections have neither the same first node nor the
same last node (or they have the same first node but different service adding timeslots),
supported by non 1+1 associated service in the ASON domain, as shown in Figure 4-8.
4-18

Figure 4-8 Non 1+1 Associated Service Diagram
If the two services that form a non 1+1 protection association have the restoration property,
when one of the service connections fails, the connection route of the other service will be
excluded.
Caution!
There is no requirement on the property of the two services for non 1+1 protection
association.
4.11.8 Transfer Between PC Service and SPC Service

ZXONE 5800 supports the transfer between the traditional PC service and the SPC
service.
Transfer from the PC service to the SPC service refers to converting the service connection
managed/maintained by the management plane to the service connection maintained by
the control plane. The allocated resources are uniformly managed by the control plane,
and the connection status is maintained by the signaling.
Transfer from the SPC service to the traditional PC service refers to converting the service
connection maintained by the control plane to the service connection managed/maintained
by the management plane. The allocated resources are uniformly managed by the
management plane, and the connection status is maintained by the EMS.
4-19

Note:
When the permanent 1+1 SNCP and 1+1 SNCP service are transferred to the PC service,
the SNCP control parameters of the first node and the last node should be consistent; if
there are shared middle nodes, the SNCP control parameters should be the same as the
default values on the EMS. Otherwise, the transfer is not allowed.
Table 4-8 lists the PC services and SPC services supported by ZXONE 5800.
Table 4-8 List of Transfers Between PC Services and SPC Services
No. SPC Service Type PC Service Type SPC→PC Service PC→SPC Service
Transfer Transfer
1 Permanent 1+1 1+1 SNCP Supported Supported

SNCP protection, protection
with restoration and
reversion

with restoration but
without reversion

without restoration
4 1+1 SNCP 1+1 SNCP Supported Supported

protection, with protection
restoration and
reversion
5 1+1 SNCP 1+1 SNCP Supported Supported

protection, without protection
restoration
6 MS protection, with Total MS protection Supported Supported

restoration and
reversion
7 MS protection, Total MS protection Supported Supported

without restoration
8 Working service in None Not supported Not supported

1:N protection group
9 Protection service in None Not supported Not supported

1:N protection group
4-20

No. SPC Service Type PC Service Type SPC→PC Service PC→SPC Service
Transfer Transfer
10 No protection, with No protection Supported Supported

restoration and
reversion
11 No protection, with No protection Supported Supported

restoration but
without reversion
12 No protection, No protection Supported Supported

without restoration
13 Extra service Extra service Supported Supported
4.11.9 Service Preemption

ZXONE 5800 supports connection preemption between services. Preemption includes:
l Preemption of extra services
l Preemption of restoration connections of normal revertive services
Service preemption should follow the rules below.
l The initial connection of a normal service (the initial connection of a revertive
service/the current connection of a non-revertive service) cannot be preempted at
any time.
l When the network resource is not adequate, the initial connection of a normal service
can preempt the unprotected link resource of an extra service.
l When the network resource is not adequate, the restoration connection of a normal
service can preempt the unprotected link resource of an extra service first. If the
resource is still inadequate, it will preempt the resource on the restoration connections
of other normal services (revertive) based on the restoration priorities.
l When resource competition but not preemption occurs, the establishment of a
restoration connection is ensured first, but not the establishment of a normal service.
l After the MSP that the extra service passes is switched, the extra service is
preempted; after the MSP switching is reverted, the extra service is restored.
When the unprotected link resource used by the extra service is preempted by
other services with a higher priority, the extra service will be preempted; when the
higher-priority services release their resources, the extra service is restored.
l When an extra service is first preempted by the restoration connection (revertive) of
other services with a lower priority, and then preempted by the restoration connection
with a higher priority, the original restoration connection with a lower priority should
be deleted.
l When an extra service is preempted by the restoration connection (revertive) of other
services, if the fault of the corresponding initial connection persists, the preemption
4-21

state will keep until the fault of the initial connection is removed or the restoration
connection fails, even if free resources are available again in the network.
4.11.10 Resource Sharing

Resource sharing means different connections in the same service can share the same
timeslot resource on the transport plane.
When querying the routes of a connection, also take the route information of other
connections in the service as the shared resource in addition to the existing route
constraints. Figure 4-9 shows an example.
Figure 4-9 Example of Resource Sharing
In Figure 4-9, (a) shows the normal case of the working path, while (b) shows the case
when section B-D of the working path fails.
When section B-D fails, the work restoration path is: A-B-C-D, which shares section A-B
with the original working path.
Several resource sharing scenarios are as follows:
l Two connections of the same service share the resource, as shown in Figure 4-10.
à When establishing permanent 1+1 SNCP and 1+1 SNCP services, if the route
strategy is set to maximum detaching, the working connection and protection
connection can share the resource.
à When restoration occurs on the working connection or protection connection of
the permanent 1+1 SNCP service, the restoration connection can share resource
with the working connection and the protection connection.
à When optimization occurs on the working or protection connection of the

permanent 1+1 SNCP and 1+1 SNCP services, and the route strategy is set to
maximum detaching of working and protection, the optimization connection can
share resource with the working connection and the protection connection.
4-22

Figure 4-10 Resource Sharing Between Two Connections of the Same Service
l Three connections of the same service share the resource, as shown in Figure 4-11.
à When the 1+1 SNCP service is being restored, the restoration connection can
à When restoration occurs on the working connection or protection connection of
the permanent 1+1 SNCP service, the restoration connection can share resource
with the working connection and the protection connection.
à When optimization occurs on the working or protection connection of the
permanent 1+1 SNCP and 1+1 SNCP services, and the route strategy is set to
maximum detaching of working and protection, the optimization connection can
Figure 4-11 Resource Sharing Among Three Connections of the Same Service
l Four connections of the same service share the resource.
When restoration occurs on both the working connection and the protection
connection of the permanent 1+1 SNCP service, the working restoration connection,
protection restoration connection, working connection, and protection connection
can share resource.
4-23

Note:
The 1+1 associated service and the non 1+1 associated service do not support resource
sharing.
4.11.11 Interconnection Between Traditional Service and ASON

Service
The traditional service is a non-path-protection service
This is the simplest scenarios among the interconnections between traditional services and
ASON services. In such a case, ASON only needs to select the timeslots for connecting
the traditional service into the ASON node as the service adding timeslots to create a
service.
As shown in Figure 4-12, at access node A', select timeslot 1 for connecting the traditional
service as the service adding timeslot for creating service in the ASON domain.
Figure 4-12 Interconnection Between Traditional Service and ASON Service 1
The traditional service is a 1+1 path-protection service

When the traditional service is a 1+1 path protection service, two different cases should
be considered:
l The service enters the ASON domain via the same node.
l The service enters the ASON domain via different nodes.
ASON processes these two cases in different ways.
l The 1+1 path protection service enters the ASON domain via the same node
If the service is a 1+1 path protection service in the SDH domain, it is an unprotected
service in the ASON domain, as shown in Figure 4-13.
4-24

This is the ring-with-chain scenario. At access node A', there are two access timeslots:
1 and 2. One of them is the access timeslot, while the other is the access protection
timeslot. The last node Z can have either one or two timeslots for service dropping.
If the service is a 1+1 path protection service in the SDH domain, it is a 1+1 SNCP
service in the ASON domain, as shown in Figure 4-14.
This is the tangent rings scenario. At access node A', there are two access timeslots:
1 and 2. One of them is the access timeslot, while the other is the access protection
timeslot. The last node Z can have either one or two timeslots for service dropping.
4-25

Caution!
à In the ring-with-chain and tangent rings scenarios, at least one of the first and last
nodes should have two timeslots, which can be timeslots of different ports.
à In the ring-with-chain scenario, the unprotected service in the ASON domain does
not support TX/RX common channel.
à In the ring-with-chain and tangent rings scenarios, the tunnel type for creating
service must be non-tunnel.
l The 1+1 path protection service enters the ASON domain via different nodes
If the service enters the ASON domain via different nodes, and then exits the ASON
domain via the same node, ASON can configure 1+1 associated service to support
this scenario.
If the service enters the ASON domain via different nodes, and then exits the ASON
domain via different nodes, ASON can configure non 1+1 associated service to
support this scenario.
For 1+1 associated service and non 1+1 associated service, refer to the "Service
Association" section.
4.11.12 Receiving/Sending on One Route

Receiving/sending on one route ensures that the service is sent and received on the same
route.
If receiving/sending on one route is chosen, the service will be received/sent on the same
route in the subsequent restoration or optimization.
Caution!
Only the unprotected service supports receiving/sending on one route.
4-26

Chapter 5
Configuration and Network
Architecture
Table of Contents
Equipment Configuration ............................................................................................5-1
Typical Configuration..................................................................................................5-5
Networking Modes....................................................................................................5-11
Networking Application .............................................................................................5-18
Networking Application for Ethernet Services ...........................................................5-21
Configuration Example .............................................................................................5-22
5.1 Equipment Configuration

5.1.1 Board Description
In terms of functions, the ZXONE 5800 boards are divided into two types.
l Functional boards: include the NCP board, SAIA board, higher-order cross-connect
board, lower-order cross-connect board, optical amplification board, and power board.
l Service boards: include the optical board, GE transparent transmission board, and
10 GE convergence board.
5.1.2 Board Slots in the Subrack

When ZXONE 5800 is configured with boards, the functional boards (except lower-order
cross-connect boards) have dedicated slots but the service boards do not.
Figure 5-1 shows layout of board slots in the subrack. Each board slot is identified with a
number.
5-1

Figure 5-1 Layout of Board Slots
Configured With the HOXA Board

When the system is configured with the HOXA board, the cross-connect capacity of the
system is 640 G. Now, users should install boards into proper slots according to Table 5-1.
5-2

Chapter 5 Configuration and Network Architecture
Table 5-1 Boards and Slots
Slot No. Access Board That Can Be Installed In

Capacity
S64Ax2, S64A, S64AFECx2, S64AFEC,

1 to 7, 12 to 19, and 21 to 23 20 G S16Ax8, S16Ax4, S4Ax16, S4Ax8, SGEAx8,
SGEAx4, SGESx8, and STGSx2
S64Ax4, S64Ax2, S64A, S64AFECx4,

S64AFECx2, S64AFEC, S16Ax8, S16Ax4,
8, 11 40 G
S4Ax16, S4Ax8, SGEAx8, SGEAx4, SGESx8,
STGSx2, and LOXA
9, 10 - NCPA, NCPB
20, 36 - PWRA
S64A, S64AFEC, S16Ax4, S4Ax16, S4Ax8,

24, 32 to 34, and 39 to 54 10 G
SGEAx8, SGEAx4, SGESx8, and STGSx2
25 to 28, 30, 31 - HOXA
29 - Reserved
35, 38 - OAx2, OA
37, 55 - SAIA
Configured With the HOXB Board

When the system is configured with the HOXB board, the cross-connect capacity of the
system is 1.28 T. Now, users should install boards into proper slots according to Table 5-2.
Table 5-2 Boards and Slots
Slot No. Access Board That Can Be Installed In

Capacity
S64Ax4, S64Ax2, S64A, S64AFECx4,

1 to 8, 11 to 19, 21 to 24, and S64AFECx2, S64AFEC, S16Ax8, S16Ax4,
40 G
32 to 34 S4Ax16, S4Ax8, SGEAx8, SGEAx4, SGESx8,
LOXA, and STGSx2
9, 10 - NCPA, NCPB
20, 36 - PWRA
S64Ax2, S64A, S64AFECx2, S64AFEC,

39 to 54 20 G S16Ax8, S16Ax4, S4Ax16, S4Ax8, SGEAx8,
SGEAx4, SGESx8, and STGSx2
25 to 28, 30, 31 - HOXB
29 - Reserved
35, 38 - OAx2, OA
37, 55 - SAIA
5-3

5.1.3 Board Configuration Principle

A ZXONE 5800 system contains the following mandatory boards/components and some
optional boards/components.
l Mandatory Boards/Components
à Backplane: It supports the connection among boards in the system.
à NE control processor board: As the nerve center of the whole system, it is
responsible for controlling and managing NE and provides clock functions. At
least one NE control processor board must be configured in a system. Two NE
control processor boards can be installed at the same time for 1+1 protection.
à Higher-order cross-connect board: It acts as the core for service processing. At
least four higher-order cross-connect boards must be configured in a system.
Additional two can be installed as the standard configuration for 2:4 protection.
à SAIA board: It provides alarm input/output interfaces, external clock interfaces
and EMS interfaces. At least one SAIA board must be configured in a system.
Two SAIA boards can be installed at the same time for 1+1 protection.
à PWR board: It supplies power to the other boards in the system. Two PWR
boards must be installed.
Note:
In combination with the necessary boards introduced above, the following two subrack
components must be configured in a ZXONE 5800 system as well.
à Fan plug-in box: It is responsible for the heat dissipation of subrack. Two fan
plug-in boxes must be configured in a subrack.
à Dust-proof unit: It is used to keep the inside of a subrack clean, avoiding dust
accumulation which influences the heat dissipation of equipment. One dust-proof
unit must be configured in a subrack.
l Optional Boards/Components
à Lower-order cross-connect board: It is configured when the time division

lower-order cross-connection is needed in a system. Configure one board to
provide 40 G cross-connect capacity. Configure five boards to provide 160 G
cross-connect capacity and forms 1:4 protection.
à Service boards: Various service boards are optional for the access of
transmission services. Select corresponding service boards according to the
types of services to be transported. The number of service boards configured in
a system depends on the quantity of available slots and their access capacity
in the system.
5-4

à Optical amplifier board: It provides the optical amplification function. Configure

proper optical amplifier board according to actual attenuation compensation
amount and engineering requirements. If the rate of service signals to be
amplified is STM-64, an additional Dispersion Compensation Module (DCM)
should be configured according to actual dispersion. DCM is a passive module,
which can be just placed outside of a subrack.
5.2 Typical Configuration

With a modularized design, ZXONE 5800 can be configured as a Terminal Multiplexer
(TM), Add-Drop Multiplexer (ADM) or a Synchronous Digital Cross-Connect (SDXC)
equipment in the same hardware system. Different types of boards can be installed in
a ZXONE 5800 subrack to implement the functions of TM, ADM or SDXC after certain
configurations or modifications in the EMS.
5.2.1 Terminal Multiplexer (TM)

Equipment Principle
TM equipment is composed of optical line boards and corresponding functional boards.
In TM equipment, SDH overheads are terminated in optical line boards and are no longer
transferred.
When acting as TM equipment, ZXONE 5800 combines some STM-N signals into a single
STM-M signal (M>N), or separates STM-N signals from an STM-M signal. Figure 5-2
shows the block diagram of TM equipment.
Figure 5-2 Principle of TM Equipment
Configuration Instructions
l Determine the rate level of TM equipment according to the signal rate in the aggregate
direction.
l For TM equipment at the STM-64 level, if the equipment supports the FEC function,
configure an S64AFECx4, S64AFECx2, or S64AFEC board. If the equipment does
not support the FEC function, configure an S64Ax4, S64Ax2, or S64A board. Then
5-5

configure optical line boards of STM-16, STM-4 and STM-1 and other service boards
as required.
l For TM equipment at the STM-16 level, configure an S16Ax8 or S16Ax4 board. Then
configure optical line boards of STM-4 and STM-1 and other service boards as re-
quired.
l For TM equipment at the STM-4 level, configure an S4Ax16 or S4Ax8 board. Then
configure optical line boards of STM-1 and other service boards as required.
l Configure mandatory functional boards: NCPA/NCPB, PWRA, SAIA, and
HOXA/HOXB.
l Configure LOXA board(s) if lower-order cross-connection of service signals is
required.
l Configure ASON software if the intelligent bandwidth allocation function is required.
Configuration Example
Figure 5-3 shows the board layout of TM equipment at the STM-64 level. With this
configuration, the ZXONE 5800 TM equipment can combine eight STM-16 signals into
two STM-64 signals and separate STM-16 signals from STM-64 signals in the opposite
direction.
5-6

Figure 5-3 Configuration Example of TM Equipment
5.2.2 Add/Drop Multiplexer (ADM)

Equipment Principle
ADM equipment is composed of optical line boards and corresponding functional boards.
In ADM equipment, SDH section overheads are terminated at the receiving side in an
optical direction and are reinserted at the transmitting side in the same optical direction.
When acting as ADM equipment, ZXONE 5800 can directly drop low-rate optical tributary
signals from a high-rate signal stream at a time or add tributary signals into a high-rate
signal stream. Figure 5-4 shows the block diagram of ADM equipment.
5-7

Figure 5-4 Principle of ADM Equipment
l Determine the rate level of ADM equipment according to the signal rate in the
aggregate direction.
l For ADM equipment at the STM-64 level, if the equipment supports the FEC function,
configure an S64AFECx4 or S64AFECx2 board or two S64AFEC boards at least. If
the equipment does not support the FEC function, configure an S64Ax4 or S64Ax2
board or two S64A boards at least. Then configure optical line boards of STM-16,
STM-4 and STM-1 and other service boards as required.
l For ADM equipment at the STM-16 level, configure an S16Ax8 or S16Ax4 board at
least. Then configure optical line boards of STM-4 and STM-1 and other service
boards as required.
l For ADM equipment at the STM-4 level, configure an S4Ax16 or S4Ax8 board at least.
Then configure optical line boards of STM-1 and other service boards as required.
l For ADM equipment at the STM-1 level, configure an S4Ax16 or S4Ax8 board at least.
Then configure other service boards as required.
l Configure mandatory functional boards: NCPA/NCPB, PWRA, SAIA, and
HOXA/HOXB.
l Configure LOXA board(s) if lower-order cross-connection of service signals is
required.
Figure 5-5 shows the board layout of ADM equipment at the STM-64 level. With this
configuration, the ZXONE 5800 ADM equipment can drop STM-16 signals from STM-64
signals at a time or add STM-16 signals into STM-64 signals directly.
5-8

Figure 5-5 Configuration Example of ADM Equipment
5.2.3 SDXC Equipment

Equipment Principle
An SDXC equipment is composed of optical line boards and corresponding functional
boards.
SDXC equipment cross-connects M channels of input STM-N signals into N channels of

output STM-N signals. The greater the highest rate level of signals that are accessible
to the SDXC equipment is, the higher carrying capacity the SDXC equipment has. The
smaller the lowest rate level of signals that can be cross-connected in the cross-connect
matrix in the SDXC equipment is, the more flexible cross-connection capability the SDXC
equipment has.
When ZXONE 5800 is configured as an SDXC equipment, the highest rate level that are
accessible to the equipment is 10 Gbit/s. The space division cross-connect capacity of
the equipment is 1.28 T, and the granularity of the space division cross-connect is VC4;
5-9

the time division cross-connect capacity is 160 G, and the granularities of the time division
cross-connect are TU3 and TU12.
Figure 5-6 shows the block diagram of SDXC equipment.
Figure 5-6 Principle of SDXC Equipment
l When ZXONE 5800 is configured as a space division cross-connect SDXC, configure
multiple interface boards, and the corresponding functional boards: NCPA/NCPB,
PWRA, SAIA, and HOXA/HOXB.
l When ZXONE 5800 is configured as a time division cross-connect SDXC, config-
ure multiple interface boards, and the corresponding functional boards: NCPA/NCPB,
PWRA, SAIA, HOXA/HOXB, and LOXA.
Figure 5-7 shows the board layout of an SDXC4/4 equipment. With this configuration, the
ZXONE 5800 SDXC equipment can cross-connect 64 channels of input STM-1 signals
into 64 channels of output STM-1 signals. The cross-connect granularity is VC4.
5-10

Figure 5-7 Configuration Example of SDXC Equipment
5.3 Networking Modes

With high transmission and cross-connection capacity, ZXONE 5800 can be widely used
in long haul networks and metro area networks. It supports multiple networking modes:
point-to-point, chain, star, ring and mesh.
5.3.1 Point-to-Point Network

The aggregate rate in the point-to-point network can be STM-1, STM-4, STM-16 and
STM-64.
Dual TM configuration can be in the 1+1 protection or non-protection mode. The single
TM configuration is in the non-protection mode.
l When the 1+1 protection mode is configured, two aggregation boards form mutual
protection. This mode enhances the reliability of service transmission, but it lowers
the service access capability.
5-11

l In the case of non protection mode, the service access capability is improved at the
price of deterioration of service transmission reliability.
The point-to-point networking is suitable for large capacity inter-office trunk and inter-office
expansion. Figure 5-8 shows the point-to-point networking mode. The equipment used at
the two ends of the point-to-point network can be both ZXONE 5800, or ZXONE 5800 and
other SDH equipment.
Figure 5-8 Point-to-Point Networking
5.3.2 Chain Network

When ZXONE 5800 is used in a chain network, the aggregate rate can be STM-1, STM-4,
STM-16 and STM-64.
The chain network is composed of the TM equipment and the ADM equipment. Figure 5-9
shows three types of chain networks consisting of ZXONE 5800.
5-12

Figure 5-9 Chain Networking
A chain network may contain only ZXONE 5800 equipment or comprise some ZXONE
5800 equipment and some other kinds of SDH equipment of ZTE Corporation.
A chain network can be configured with 1+1 protection or 1:N linear MS protection.
l When the 1+1 protection mode is configured, two aggregation boards form mutual
protection. This mode enhances the reliability of service transmission, but it lowers
the service access capability.
l Under the 1:N protection mode, N working channels and one protection channel are
available. When any one of the N channels fails, the protection channel is used to
protect the failed working channel. If two working channels have problems at the
same time, only the one with higher priority will be protected. 1:1 protection can be
regarded as a particular case of 1:N protection.
l When the non-protection mode is configured, the networking of ADM equipment and
dual TM equipment can improve the service access capabilities. However, it reduces
the reliability of service transmission.
The chain networking mode is applicable to long haul trunk networks, communication
networks with traffic distributed in chain or chain branches of ring networks.
5-13

5.3.3 Ring Network

The line interface of the ring network features self-closing. The tributary services between
NEs can be transmitted in point-to-point mode in both directions (east and west). Such a
network topology has very strong viability and self-healing capability and is applicable to
large-capacity optical networks.
Ring networks can be divided into two types according to their self-healing ring structures:
path shared ring and Multiplex Section (MS) shared ring. In terms of abstract functional
structure, the path shared ring supports Sub-Network Connection (SNC) protection while
the MS shared ring supports path protection.
ZXONE 5800 can be used to construct two-fiber/four-fiber bidirectional MS shared ring at
STM-64, STM-16 or STM-4 level.
Figure 5-10 shows a ring network consisting of ZXONE 5800.
Figure 5-10 Ring Networking
A ring network may contain only ZXONE 5800 equipment or comprise some ZXONE
5800 equipment and some other kinds of SDH equipment of ZTE Corporation. In such
case, different service boards on the ring must be configured with the same protection
mechanism. A logical sub-ring protection mode can also be used in a ring network. Under
this mode, multiple logical sub-rings are built in the ring network according to actual
situations. Each logical sub-ring is independent. The protection action on a single logical
sub-ring does not influence the other sub-rings.
The following describes how the protection in a ring network is implemented with the
example of a four-fiber bidirectional MS shared ring. As shown in Figure 5-11, the services
between node A and node D pass node B and node C in normal situation. Once some
fault occurs between node B and node C, the ring performs protection switching and then
the routes of services change accordingly, as shown in Figure 5-12.
5-14

Figure 5-11 Normal Service Routes in Four-Fiber Bidirectional MS Shared Ring
Figure 5-12 Service Routes After Protection Switching in Four-Fiber Bidirectional MS

Shared Ring
Two types of two-fiber/four-fiber bidirectional MS shared rings composed of ZXONE 5800

can be configured with extra traffic or without extra traffic.
two-fiber/four-fiber bidirectional MS shared rings have the capability of heavy traffic
transmission. The capacity of a two-fiber bidirectional MS shared ring (without extra
traffic) is up to K/2×STM-N; while the capacity of a four-fiber bidirectional MS shared ring
5-15

(without extra traffic) is up to K×STM-N, where “K” is the number of nodes on the ring,
and “STM-N” is the highest rate of the ring.
The MS shared ring has the merits of large service transmission capacity and flexible
switching.
Its disadvantage is that it is required to process the APS protocol at the time of switching,
which results in long fault response/recovery time.
The two-fiber/four-fiber bidirectional MS shared rings are commonly used for high-capacity
transmission at STM-16/STM-64 rate level in traffic-distributed trunk networks and long
haul networks.
5.3.4 Star Network

ZXONE 5800 with high cross-connection capacity can be used with other SDH equipment
of ZTE Corporation together to form a star network. In such network, ZXONE 5800 acts
as a core scheduling equipment to implement the traffic grooming in the network. Figure
5-13 shows a star network consisting of ZXONE 5800 and other SDH equipment.
Figure 5-13 Star Networking
5.3.5 Mesh Network

ZXONE 5800 with intelligent characteristic supports the mesh networking mode, as shown
in Figure 5-14.
5-16

Figure 5-14 Mesh Networking
The mesh networking mode is flexible and scalable with strong self-healing capability.
Compared with traditional SDH networking modes, the mesh networking mode does not
need to reserve bandwidth, resulting in the saving of bandwidth. It is very favorable in
the current situation that the demands for bandwidth keep increasing. In addition, the
intelligent control function of ASON can be integrated into mesh networks to carry out
rerouting calculation, provide recovery algorithm on network level and offer various service
protection modes at different levels.
5.3.6 Hybrid Network

ZXONE 5800 can be used with other SDH-based multi-service node equipment (such as
ZXMP S385) of ZTE Corporation to form a hybrid network, as shown in Figure 5-15.
5-17

Figure 5-15 Hybrid Network
ZXONE 5800 acts as a cord node to provide large-capacity and intelligent service
scheduling. In addition, such a core network can be easily changed to a mesh network to
enhance the network security.
5.4 Networking Application

5.4.1 Traditional SDH Networking Application
ZXONE 5800 is an SDH-based large-capacity cross-connect equipment, which can be
upgraded to an OTN equipment in future.
As shown in Figure 5-16, ZXONE 5800 is located at the long haul backbone network and
metro area core layer in the traditional SDH networking application.
5-18

Figure 5-16 Traditional SDH Networking Application
5.4.2 ASON Networking Application

In ASON networking application as shown in Figure 5-17, ZXONE 5800 acts as an
intelligent core node to schedule cross-ring services at the core layer and convergence
layer. The core layer is a 10 Gbit/s whole mesh network, which carries the 2G and 3G
services. The core layer adopts SDH protection + ASON dynamic recovery mode, which
can provide 50 ms carrier-class protection in the case of multiple broken fiber. The
convergence layer is a 2.5 Gbit/s ring consisting of the ZXMP S385 equipment.
5-19

Figure 5-17 ASON Networking Application
5.4.3 GE Service Networking Application

In the IP network, ISP and ASP needs higher and more flexible bandwidth, in order
to establish effective connections. ZXONE 5800 can directly provide the GE service
interface, which implements the long distance point-to-point transmission of the Ethernet
service over SDH.
As shown in Figure 5-18, the networking modes of the ZXONE 5800 equipment are very
flexible, such as chain network, ring network, mesh network, or hybrid network with the
above modes.
5-20

Figure 5-18 GE Service Networking Application
• The dotted lines in the

figure are point-to-point
connection paths.
5.5 Networking Application for Ethernet Services

ZXONE 5800, when configured with SGEA boards, can not only provide all the functions
of a traditional SDH equipment, but also support the processing of Ethernet data as
a multi-service node equipment. It is capable of carrying Ethernet Private Line (EPL)
services providing the functions of traffic policing, CoS and QoS as required.
An EPL has two service access points. User Ethernet MAC frames are transmitted on it
transparently from point to point. The traffic of each EPL subscriber is carried by a private
SDH channel. Different subscribers do not share SDH bandwidth, which leads to the same
bandwidth guarantee and security performance as SDH. L2 switching and MAC address
learning is unnecessary during the point-to-point transmission of EPL services.
Figure 5-19 shows a typical application of ZXONE 5800 for the transmission of EPL
services. The Ethernet service between subscriber X and Y is transparently transmitted
through ZXONE 5800 equipment A and J, which are configured with SGEA boards, and
the other intermediate equipment B, C, D, E, F, G and H.
5-21

Figure 5-19 Application of ZXONE 5800 for EPL
5.6 Configuration Example

Service Requirements
Four 10 Gbit/s SDH optical transmission devices are used at site A, B, C and D in an optical
transmission project. Figure 5-20 shows the physical locations of these four sites.
5-22

Figure 5-20 Locations of Site A, B, C, and D
There are eight STM-1 optical signals on each of the spans between site A and site B,
site A and site C, site A and site D. There are three STM-4 service signals between site B
and D. There are Ethernet service signals with the rate less than 1 Gbit/s for transparent
transmission between site A and C. All the STM-1 and STM-4 services are short haul
services.
Networking Analysis
1. Determine the kind of equipment to be used and the rate of the network
ZXONE 5800 at STM-64 level is recommended at site A, B, C and D. The aggregate
rate of the network is 10 Gbit/s.
2. Determine the network topology
The site distribution and service allocation should be considered for choosing a
network topology. Generally, a ring networking mode with excellent self-healing
capability is preferable once the available routes allow. The ring networking mode
is recommended even when the sites are distributed as a chain in case of enough
cables and fibers. For complex site distribution, a hybrid networking mode with
multiple network topological structures can be used.
In this example, it is recommended to construct a ring network consisting of four sites
(A, B, C and D) according to the actual situation of each site’s location and service
requirements.
3. Choose a protection mode
To enhance the system reliability, the STM-64 multiplex section protection ring is
configured for the ring network.
4. Choose an access NE and an EMS used to manage all the NEs in the network
Choose an EMS according to the equipment type in the network. The EMS used in
a network had better have the capability of managing all types of equipment in the
whole network. The EMS computer is connected to an access NE, through which the
5-23

EMS can manage the other NEs in the network. Generally, a main office or station
with heavy traffic is selected as the access NE.
Decide whether the connection between the NM and access NE is local or remote,
and in the case of a remote NM, determine the type of the communication network.
In this example, NetNumen T31 provided by ZTE Corporation is used to manage
ZXONE 5800 NEs.Site A (NE A) is selected as the access NE, to which the EMS
is connected locally with a network cable.
5. Determine the clock source and a gateway NE
The clock source of each NE can be selected from external clocks, line clocks or
internal clocks according to actual requirements. The gateway NE refers to the NE
configured as the clock source. The synchronization clock of the network is obtained
from that NE. Generally, the access NE in a network also acts as the gateway NE for
the purpose of convenient routine maintenance.
In this example, site A (NE A) is selected as the gateway NE providing the timing
source, and an internal clock is selected as the clock source.
The networking diagram derived from the above analysis is shown in Figure 5-21.
Figure 5-21 Network Topology
Configuration Implementation
This part briefly introduces the board configurations, structural component configurations
and networking configurations for each site.
l Board Configurations
à Functional boards: NCPB, SAIA, HOXA, LOXA and PWRA. It is recommended
to configure two NCPB, SAIA, LOXA and PWRA boards and six HOXA boards in
each site to improve the system stability.
à Optical line boards: Select the types of optical interfaces according to the
transmission distance and service rate. Then select optical line boards according
5-24

to the rate of optical interfaces. In this example, S64A, S16A and S4A boards
are used to meet the service requirements.
à Ethernet board: Configure SGEA boards in site A and site C for the transparent
transmission of Ethernet services between these two sites, and configure the
SGEA board and the related optical line board in the EMS according to the traffic
capacity.
Table 5-3 describes the board configurations in each site.
Table 5-3 Board Configurations of Each Site
Quantity
Board
Site A Site B Site C Site D
NCPB 2 2 2 2
SAIA 2 2 2 2
PWRA 2 2 2 2
LOXA 2 2 2 2
HOXA 6 6 6 6
S64A (S-64.2b) - - 1 1
S64A (L-64.2b) - - 1 1
S64A×2
1 1 - -
(L-64.2b)
S4A×4 (S-4.1) - 1 - 1
S4A×8 (S-1.1) 3 1 1 1
SGEA×8 1 - 1 -
• The above table only gives one type of optional optical modules for each kind of optical line
board. In actual application, proper optical module types should be used according to actual
situations.
l Structural Component Configurations

à Configuration of cabinet
ZXONE 5800 is mounted in a cabinet of 2200 mm height. In this example, a

cabinet with the height of 2200 mm is deployed at each site.
à Configuration of components
Configure other necessary components in each cabinet, including power

distribution box, subrack, fan plug-in box and dust-proof unit. For different
models of cabinets, the needed quantities of these components are different.
In a 2200 mm cabinet, one power distribution box, one subrack, one dust-proof
unit and two fan plug-in boxes should be installed.
l Networking Configurations
5-25

Configure all the ZXONE 5800 NEs in the EMS NetNumen U31 R22. Based on the
status of an NE (equipment), online or offline, two typical configuration procedures
are available as follows.
à Create online NEs
Create online NEs → Select the access NE → Install boards → Establish
connections between NEs → Configure MS protection → Configure service →
Configure overheads → Configure clock sources → Query NCP time
à Create offline NEs
Create offline NEs → Select the access NE → Install boards → Establish
connections between NEs → Configure MS protection → Configure service →
Configure overheads → Configure clock sources
After configuration, change the status of NEs from offline to online, download the
database of NEs, and then query NCP time.
Note:
Refer to related operation manuals of NetNumen U31 R22 for detailed instructions of
network configuration and service configuration.
Application Features
In this example, the ring networking mode is adopted with a two-fiber bidirectional MS
protection mode.
When any site on the ring fails or some fiber between two sites breaks, the services can
still be transmitted successfully in a protected way without being influenced due to the
self-healing capability of the network and hot backup of important boards. On the other
hand, the MS protection ring supports the repeated use of timeslots on the ring. The
capacity of the ring network is up to K/2×STM-N, where “K” is the number of nodes on the
ring and “STM-N” is the highest rate. Therefore, the maximum capacity of the ring network
in this example is 2×STM-64.
This networking mode is applicable to the transmission trunk networks with scattered
nodes and high service reliability requirement.
5-26

Appendix A
Fundamentals of ASON
Table of Contents
Ÿ Generation Background of ASON ........................................................................... A-1
Ÿ ASON Architecture ................................................................................................. A-3
Ÿ ASON Networking ................................................................................................ A-11
Ÿ Protection and Restoration ................................................................................... A-13
Ÿ ASON Services .................................................................................................... A-15
A.1 Generation Background of ASON

A.1.1 Definition of ASON
Automatically Switched Optical Network (ASON) is also called intelligent optical network.
In an ASON, service requests are initiated dynamically by user ends or a management
system. ASON selects routes automatically for these requests and implements the
functions of connection setup, modification, release, automatic protection and restoration,
and automatic discovery etc. ASON is a new-generation optical network integrated with
switch and transport functions.
A.1.2 Problems in Traditional Optical Networks

Traditional optical networks have the following problems, which hinder the development of
services and improvement of service quality.
l End-to-end services can only be configured segment by segment via a network
management system, which results in long time for commissioning. Fast automatic
setup and protection of end-to-end services is unavailable in traditional optical
networks.
l Network load can not be balanced and optimized automatically.
l Differentiated service is unavailable without diverse QoS.
l Any change of network topology can not be embodied in real time in a network
management system, which makes real-time management difficult.
l Traditional optical networks commonly use network management systems with
multiple hierarchies, which manage a great diversity of equipment. And accordingly,
it is different to use a unified network management system to manage all kinds of
equipment, such as DXC, ADM and WDM etc. .
l Different models of equipment are used on backbone layer with lots of connections
among optical interfaces, which makes the network structure complex.
A-1

l Traditional optical networks generally use ring networking mode. It results in the
existence of many cross-ring nodes, which become bottlenecks for traffic scheduling.
l The bandwidth utilization ratio of SDH ring is low because 50% bandwidth needs to
be reserved for the protection purpose.
l Traditional optical transport networks, originally designed for voice transmission,
can no longer satisfy the service demands better with the fast development of data
services.
A.1.3 Generation of ASON

ASON emerges to meet the new demands for optical transport networks as listed below
since traditional optical networks can not effectively satisfy these demands.
l High expansibility is required for transmission networks with the rapid growth of data
services.
l Semi-static traditional transmission networks are challenged by the bursting
characteristic of data services.
l High bandwidth and quick commissioning of network is needed.
l A diversity of application and service is required.
l Client equipment (routers and switches) can be easily managed and plug-and-play.
The rapid development of data services requires more bandwidth and higher service quality
for optical transport networks, which drives the evolution from traditional optical networks,
which only provides fixed bandwidth, to more flexible and intelligent networks, which are
easy to manage and control. ASON is such network meeting the demands. It supports
the classification of services and intelligent configuration according to resources and traffic
in network. In addition, ASON features powerful survivability with protection capability in
case of faults in network. It acts as an optical transport network that supports real-time
bandwidth configuration and dynamic end-to-end connection management.
A.1.4 Advantages of ASON

The new generation optical network ASON can not only satisfy the new demands of
modern telecommunication services but also solve the problems in traditional optical
networks. It has the following advantages.
l An ASON equipment can replace multiple traditional transport equipment, which leads
a network with clear structure.
l Flexible traffic scheduling is available due to the high-capacity and multiple-granularity
switching function provided by ASON equipment.
l ASON supports flexible mesh networking mode with strong self-healing capability,
high scalability and bandwidth utilization ratio.
l ASON supports automatic discovery of network topology.
l Automatic balancing and optimizing of link load can be implemented in ASON. In
addition, the dynamic bandwidth allocation in ASON improves bandwidth utilization
ratio.
l ASON supports fast and flexible service commissioning based on signaling request.
A-2

Appendix A Fundamentals of ASON
l End-to-end (cross-ring) traffic protection is supported.

l The network management is simplified and finally a unified network management
system can be realized to support the interconnection and intercommunication of
different networks.
l ASON allows service setup completed in shorter time, as well as dynamic request and
release of bandwidth.
l ASON supports new value-added services, including bandwidth allocation on
demand, bandwidth lease and wholesale, Optical Virtual Private Network (OVPN)
and Service Level Agreement (SLA) etc.
ASON changes optical networks from bandwidth transport networks with low profit
earnings into service networks providing direct profitable services and applications.
A.2 ASON Architecture

The functional architecture of ASON has three planes: management plane, control plane
and transport plane (also called service plane), as shown in Figure A-1. This figure
also includes the DCN, which provides the communication paths to carry signalling and
management information among the management plane, control plane and the transport
plane, and the internal communication of each of them. It carries distributed signaling
messages related to the control plane and management messages related to the transport
plane.
A-3

Figure A-1 Architecture of ASON
The following describes the three planes in ASON respectively.

1. Control Plane
The ASON control plane is composed of a group of communication entities that provide
the functions of call control, connection control and restoration of connection in case
of failure. It collects and distributes network topology information on the control plane
in ASON, and provides routes by means of Shortest Path First (SPF) algorithm.
The purpose of the control plane is to

l Facilitate fast and efficient configuration of connections within a transport layer
network to support both switched and soft permanent connections.
l Reconfigure or modify connections that support calls that have previously been
set up.
l Perform a restoration function.
The control plane mainly involves the following parts:
l Signaling channels allowing the exchange of control information among nodes

l End-to-end connection allowing to be fast set up and released by nodes and
signaling protocols
A-4

l Topology database that can be modified and maintained in a distributed way

l Fast and flexible restoration mechanism
The control plane can be divided into different domains according to the division
of network management domains. The control plane can base its domain division
on different regions, equipment vendors, protocols, signaling systems or security
and reliability requirements. The control plane in a single management domain can
be subdivided to improve the scalability of network and avoid inter-domain control
information storm.
The control plane architecture should have the following characteristics:
l Support various transport infrastructures, such as the SDH transport network, as
defined in ITU-T G.803, and the Optical Transport Network (OTN), as defined in
ITU-T G.872.
l Support various protection and restoration mechanisms.
l Support various control protocols.
l Support traffic control engineering.
l Be applicable regardless of how the control plane has been subdivided into
domains and routing areas, and how the transport resources have been
partitioned into subnetworks.
l Be applicable regardless of the implementation of connection control that may
range from a fully distributed to a centralized control architecture.
l Be mainly applicable to client-layer services with the focus on real-time service
switching.
2. Management Plane
The management plane provides the function of managing the transport plane,
control plane and DCN. The transport plane, control plane and DCN report their
management information (event, alarm and performance etc.) to the management
plane. According to the received management information, the management plane
coordinates the works on all planes.
In terms of logical function, the management plane can be divided into three layers:
NE layer, element management layer and network management layer.
Based on the domain division of the control plane, each control domain can use its
own ASON network management system, or multiple control domains share a unified
network management system. ASON network management systems can also be
deployed for different network operators respectively. A network management system
can be used to manage the network of a single operator. The network of an operator
can also be divided into multiple control domains.
3. Transport Plane
The transport plane provides explicit routes and circuit service stream, and transfers
fault management and performance detection information.
The transport plane, layered as defined in ITU-T G.805, supports existing and
future transmission technologies. It provides the functions of optical signal
transmission, multiplexing, protection switching configuration and multiple-granularity
A-5

cross-connection etc., and guarantees the reliability of optical signals transmitted

over it by checking the signal quality.
A.2.1 Connection Types in ASON

ASON supports three types of connections: permanent connection, switched connection
and soft permanent connection. They are used under different application conditions.
l Permanent Connection (PC)
A PC is a connection type that is provisioned by the management system
(management plane).
The management plane configures resources on the transport plane to set up a PC.
It not only initiates but also configures the PC. Once being set up, a PC will always
exist until the management plane commands to release it
l Switched Connection (SC)
SC is also called signaling connection, which is established on request of the control
plane. The control plane completes the configuration of transport plane resources.
Actually, an SC is established as a result of a request from an end user. Once the
end user presents a release request, this SC will be released under the control of the
control plane.
The introduction of SC is the kernel of ASON, which makes intelligent functions
available in optical networks. Due to SC, ASON can automatically provide needed
optical channels according to user requirements.
l Soft Permanent Connection (SPC)
SPC is also called hybrid connection, which is a combination of PC and SC.
An SPC is a user-to-user connection whereby the user-to-network portion of
the end-to-end connection is established by the network management system
(management plane) as a PC. The network portion of the end-to-end connection is
established as a switched connection using the control plane. In the network portion
of the connection, requests for establishment of the connection are initiated by the
management plane and setup by the control plane.
A.2.2 Control Plane Functions

The intelligent functions of ASON are mainly implemented by the control plane, which
provides basic functions and core functions as follows:
l Basic Functions
The basic functions of the ASON control plane include routing, signaling, link
management and unit interface technology, which form the base of the control plane.
à Routing functions: route calculation (service route and signaling route),
implementation of routing protocols, maintenance of route tables, distribution
and management of network topology and local resource information.
A-6

à Signaling functions: set up, release and maintain Label Switched Path (LSP),
process LSP-related requests (including setup request of SPC) coming from the
management plane or UNI-C and maintain signalling sessions.
à Link management functions: discovery function (including neighbor discovery
and service discovery), data channel connectivity verification, control channel
maintenance, Traffic Engineering (TE) link management and fault information
processing etc.
à Unit interface technology: definition of interface standards among units in ASON
l Core Functions
The core functions of the ASON control plane include connection control,
protection/restoration, service processing and policy management.
à Connection control functions: control and management of three kinds of
connections (PC, SC and SPC) specified in ASON.
à Protection/restoration functions: used to guarantee the survivability of ASON,
including local span protection, ring protection, end—to—end protection and
distributed restoration mechanism.
à Service processing functions: used to support the transport of new intelligent
value-added services, such as Bandwidth On Demand (BOD), and Optical Virtual
Private Network (OVPN) etc.
à Policy management functions: used for the processing of calls to ensure

intelligent use of network resources.
A.2.3 Control Plane Interfaces

The ASON control plane has three kinds of signaling control interfaces: UNI, E-NNI and
I-NNI, as shown in Figure A-2.
A-7

Figure A-2 Signaling Control Interfaces in ASON
The following briefly introduces these signaling control interfaces:

l UNI
UNI is an interface between client end and ASON equipment. It is a bidirectional
signaling interface between two control plane entities, one of which requests service
and the other provides service.
Client layer network can automatically request to set up a new connection, query or
release existing connections via UNI. UNI, located between client end and optical
network, supports call security and authorization and number service. It also provides
the functions of call control, resource discovery, connection control and connection
selection.
The functions of UNI are supported by relevant signaling protocols. Two mature
signaling protocols used by it are: CR-LDP and RSVP-TE. The later one is widely
used these days.
l E-NNI
E-NNI is a bidirectional signaling interface between two control plane entities in
different control domains. The purpose of E-NNI is to exchange accessibility
information between different domains regardless of the topology information inside
networks.
E-NNI supports the functions of call control, resource discovery, connection control,
connection selection and connection route selection.
l I-NNI
I-NNI is a bidirectional signaling interface between two control plane entities in the
same control domain. The purpose of I-NNI is to deliver the topology information to
A-8

each connection unit inside a network. As a kind of intra-domain interface, I-NNI can
use private protocols defined by vendors without the requirement for standardization.
I-NNI supports the functions of resource discovery, connection control, connection
selection and connection route.
A.2.4 Control Protocols

Control protocols are important components of the ASON control plane. They form the
base for the implementation of control plane functions. A suite of Generalized MPLS
(GMPLS) protocol is extended to support the capabilities and functionality of an ASON.
Compared with the original GMPLS protocol, the protocol suite used by ASON has the
following additional features:
l Support IPv4, IPv6 and Network Service Access Point (NSAP).
l Support user—defined service specifications and service diversity with UNI and E-NNI
interfaces.
l Support domains and hierarchical architecture.
l Support call/connection separation.
l Support soft permanent connection.
l Support service signals of various formats and rate levels
l Support different intra-domain and inter-domain protocols.
Figure A-3 shows the composition of the suite of GMPLS protocols used for ASON, which
involves Link Management Protocol (LMP), routing protocols and signaling protocols.
Figure A-3 GMPLS Protocol
The following briefly introduces each part of the GMPLS protocol suite.
l LMP
LMP runs on the transport plane between adjacent nodes to provide links and
manage bidirectional control channels between them. LMP currently consists of
four primary procedures, of which the first two are mandatory and the last two are
optional: control channel management, link property correlation, link verification and
link fault management, as described below:
à Control channel management
Control channel management is used to establish and maintain control channel
connectivity between adjacent nodes. It completes parameter negotiation and
signaling information transfer. At least one bidirectional control channel should
A-9

be available between adjacent nodes. Multiple control channels are allowed as

backups.
The connectivity and interface identifiers of local and remote nodes on transport
plane should be known, which can be got through the management plane or
by means of automatic discovery mechanism. The remote node supports the
association between transport plane interface identifier and trace object. For SDH
transport plane, LMP control channel management uses Trail Trace Identifier
(TTI).
à Link property correlation
Link property correlation is used to aggregate multiple data links into a single
TE link and to synchronize the link properties. This function greatly reduces the
delivery of Link State Advertisement (LSA) messages in networks.
Link property correlation allows the bundling, modification and correlation of links
as well as the exchange of their traffic engineering parameters, to ensure the
consistency of the properties and capacity of TE links between adjacent nodes.
à Link verification
Link verification is used to verify the physical connectivity of the data links and
verify the mapping of the Interface-ID to Link-ID. The local-to-remote associations
can be obtained using a prior knowledge or using the link verification procedure.
The link verification procedure is initiated by the “begin verify” message on the
control channel. It is implemented with the coordination between control channel
and data channels. Link verification procedure is optional depending on the
configuration of “verification flag” during parameter negotiation.
After link verification, a local-to-remote identifier mapping table with definite link
states can be achieved.
à Link fault management
Link fault management is initiated by a downstream node that detects data link
fault. It is used to exchange channel fault messages and response messages so
as to detect link state hop by hop along Label Switched Path (LSP) towards the
upstream until localize the faulty link. This procedure enables quick response to
link faults and precise location of faulty links.
l Routing Protocols
At present, ITU-T has not specify routing protocols for ASON. The commonly used
intra-domain routing protocols include OSPF and IS-IS, while inter-domain routing
protocols include BGP, OSPF, PNNI and DDRP. Among them, OSPF is most
widely-used by different vendors. Here, we give a brief introduction of OSPF.
OSPF is a dynamic routing protocol based on link state and SPF algorithm. OSPF
learns network topology (in the same area) by exchanging link state between
neighbors and calculates the routes to all destinations in the area with SPF algorithm.
A-10

OSPF collects not only the topology information of network, including topology
information on control layer and traffic topology information used for constrained route
calculation, but also network protection information. It calculates routes according
to the topology information on control layer to establish routing tables on the control
layer.
After the collection of transport plane topology in the whole area, OSPF calls CSPF
algorithm to search traffic path. The following constraints are involved when using
CSPF algorithm: maximum link bandwidth, available link bandwidth, shared link risk
group, nodes to be involved (or nodes to be avoided), SLA and optical distance etc.
CSPF calculates not only end-to-end working paths but also corresponding protection
paths.
l Signaling Protocols
ITU-T G.7713 specifies three signaling protocols for ASON: PNNI, RSVP-TE and
CR-LDP.
à PNNI originates from traditional telecommunication signaling protocols (Q.2931,
Q.931 and SS7). It is highly reliable without enough flexibility. PNNI can not
communicate with GMPLS. It is only applicable to soft permanent connections.
à RSVP originates from IPCoS technology. Compared with PNNI, RSVP can better
implement resource synchronization, error and fault processing such as power
failure. Moreover, it makes multicast easier. RSVP can fully separate the control
plane and the data plane with better flexibility. It is used between I-NNI and E-NNI,
supporting soft permanent connections and intra-domain switched connections
from local domains to exterior domains or all paths between service providers.
à CR-LDP originates from IP MPLS technology. It, being difficult to realize
multicast, needs great extension and improvement. CR-LDP is applicable to
UNI, E-NNI and I-NNI, supporting some ASON-related automatic calling and
connection operations.
From the comparison of these three signaling protocols, RSVP is more mature and
most vendors adopt it as their signaling protocol.
A.3 ASON Networking

ASON supports multiple networking modes, including independent mesh networking and
hybrid networking with traditional optical network via UNI or NNI interfaces.
Independent Networking
When only ASON equipment are used to form a network, the mesh networking mode is
commonly used, as shown in Figure A-4.
A-11

Figure A-4 Mesh Networking
Hybrid Networking via UNI

ASON can be deployed with other traditional optical networks to form a hybrid network via
UNI interfaces, as shown in Figure A-5.
Figure A-5 Hybrid Networking via UNI
In such hybrid network, traditional optical networks are accessed to ASON as clients. This
networking mode is applicable for hybrid networking of existing metro area networks and
newly-constructed ASON backbone network. It has the following features.
l Existing network resources can be fully utilized.
l UNI agents send connection requests from the network management system to
ASON, which completes the setup of connections.
l UNI interfaces are used between ASON and traditional optical networks but not
directly used for end users. Therefore, the hybrid network does not directly support
switched connection services of clients.
A-12

l The functions of UNI interfaces are actually provided by data equipment but not
transmission equipment in optical networks such as SDH equipment.
Hybrid Networking via NNI

An out-of-band ASON can be deployed with other traditional optical networks to form a
hybrid network via UNI interfaces, as shown in Figure A-6. NNI agents are configured for
the traditional optical networks, which enables the interconnection between these optical
networks with ASON.
Figure A-6 Hybrid Networking via NNI
The hybrid network using NNI interfaces is more like an ASON with more functions.
Each NNI agent can represent one or more node equipment. NNI acts for a node or a
network. It can provide switched connection services. And NNI interfaces between ASON
and traditional optical networks can provide more network information, such as routing
information and protection/restoration information.
Those existing optical networks that can not be upgraded or reconstructed can be directly
interconnected to an ASON, they are management and configured separately. This
interconnection mode is similar to that of networks provided by different vendors. It is
unable to realize unified management and scheduling in the whole network.
A.4 Protection and Restoration

A.4.1 ASON Protection
Protection is a procedure to replace a failure resource with a reserved standby resource,
which is generally completed in dozens of seconds. The following introduces the protection
mechanisms and types in an ASON.
A-13

l Protection Mechanisms
ASON supports two protection mechanisms, one is based on the transport plane and
the other is based on the control plane.
à Protection based on transport plane: The management plane implements the
protection configuration. The control plane is not involved in such protection.
à Protection based on control plane: The control plane implements the protection
configuration, including setting up one or multiple protection connections and
providing connection configuration information for the purpose of protection etc.
The protection based on control plane is carried out between the source node and
sink node of a protected link. Only the connection controllers of the source node
and sink node are involved in the protection regardless of those of intermediate
nodes.
l Protection Types
ASON supports the following protection types.
à 1+1 protection: Services are transported on both the working link and protection
link. Those with better quality are received at receive end.
à 1:1 protection: Services are only transported on the working link. The protection
link does not carry services or only carries services with lower priority. When the
working link fails, the services carried by it are switched to the protection link;
while the original services with lower priority carried by the protection link are
discarded.
à M:N protection (M N): N working links share M protection links. M and N can
be preset. The protection links can carry low-priority services. No one-to-one
relationship is set between working links and protection links. When a working
link fails, its services are switched to an available protection link, which discards
its original low-priority services. If more than M working links fail at the same time,
only M working links with higher priority are protected.
à MS protection ring and MS protection link
A.4.2 ASON Restoration

Restoration is a procedure to reroute for a new connection to replace a failed connection
with idle capacity in network, which is generally completed in hundreds of milliseconds to
several seconds.
Restoration can be controlled in a centralized way or a distributed way. The distributed
control is commonly used of restoration in ASON.
l Centralized control: Restoration is completed under the control of a network control
center.
l Distributed control: Restoration is completed by distributed intelligent NEs in a
network.
Restoration can be divided into rerouting restoration and pre-planned LSP restoration.
A-14

l Rerouting restoration
à Pre-planned rerouting: Pre-planned rerouting calculates restoration routes for
working connections before any failure. When a working connection fails, the
pre-planned connection is activated to replace the failed one. The restoration
may not be guaranteed if resources have not been reserved or chosen before
the occurrence of failure.
à Dynamic rerouting: Dynamic rerouting calculates restoration route for working
connection in real time when a failure occurs, selects standby resources, sets up
new connections to replace the failed one.
The dynamic rerouting is mostly used in ASON.

l Pre-planned LSP restoration (or pre-planned LSP rerouting)
Pre-planned LSP restoration is carried out after signaling exchange. The restoration
resources on the restoration path are pre-planned. LSP restoration can complete the
signal exchange on demand or complete it in advance. If the signaling exchange
is completed on demand, the control plane delivers restoration-related signalings to
each relevant node before restoration. If the signaling exchange is completed in
advance, pre-planned LSP restoration will start directly.
A.5 ASON Services

A.5.1 Introduction to ASON Services
Service Types
The following lists the types of services that can be transported over an ASON.
l SDH service: SDH connections with granularity of VC-n and VC-n-Xv as specified in
ITU-T G.707
l OTN service: OTN connections with granularity of ODUk and ODUk-n-Xv as specified
in ITU-T G.709
l Transparent or non-transparent optical wavelength services
l Ethernet services of 10 Mbit/s, 100 Mbit/s, 1 Gbit/s and 10 Gbit/s
l FICON, ESCON, FC and SAN services
Service Connection Types

ASON supports three types of connections: Permanent Connection (PC), Switched
Connection (SC) and Soft Permanent Connection (SPC).
l PC: It is a connection type that is provisioned by the management system
(management plane).
l SC: Also called signaling connection, it is established on request of the control plane.
l SPC: Also called hybrid connection, it is a combination of PC and SC.
A-15

Service Connection Topology Types

ASON supports the following topology types of service connections.
l Bidirectional point-to-point connection
l Unidirectional point-to-point connection
l Unidirectional point-to-multipoint connection
ASON supports the separation of call and connection control for the enhanced functions
such as bandwidth on demand, diversity of circuit assignment and connection bundling
etc. The separation of call and connection control reduces call control messages of
intermediate control nodes and thus lessen the workload of decoding and message
translation. And because of the separation, a call can correspond to multiple connections.
At present, the bidirectional point-to-point connection is the most widely used connection
mode.
Classes of Service
ASON supports the convenient division of services based on priority to provide
transmission traffic complying with SLA.
Clients have different requirements for connection availability. These requirements can be
expressed in terms of the "service level", which describes restoration/protection options
and priority related connection characteristics, such as holding priority (e.g. pre-emptable
or not), setup priority, or restoration priority.
l Setup priority: It refers to connection setup time, which may be on day, hour or minute
level.
l Holding priority (pre-emptable or not): It determines whether a connection link without
protection can be preempted to carry more important service when some fault occurs
in system.
l Restoration priority: It refers to restoration time in case of system failure and
restoration level such as percentage of restored services.
The control plane supports the priority setting of each connection, bandwidth reservation
as the purpose of restoration, as well as route unification after failure recovery. Generally,
ASON supports the following connection levels.
l Private connection (1+1 and 1:1)
l Shared protection (1:N and M:N)
l Non-protection (transport on active link)
l Non-protection (transport on protection link)
Service Access Methods

In order to access services to an ASON, physical connections should be established
between clients and carrier networks on the transport plane. The following access
methods are optional, according to the locations of carrier networks and clients.
l Intra-office access (when NEs in optical networks and client NEs are located at the
same place)
A-16

l Direct remote access (for client devices with private link connections)
l Remote access via access subnet
l Dual homing access: It is a special case of the access network. A client device may
be dual homed to a carrier network through two different paths. The purpose of dual
homing is to enhance the network survivability. When one of the access path fails,
the client traffic will not be interrupted due to the existence of the other access path.
Service Access Control

From a security perspective, network resources should be protected from unauthorized
accesses and should not be used by unauthorized entities. Service Access Control is the
mechanism that limits and controls entities trying to access network resources, especially
via UNI and E-NNI. The service access control function should be implemented and
support the following features:
l An authentication function of an entity should be included in order to prevent
masquerade (spoofing). Masquerade is fraudulent use of network resources by
pretending to be a different entity. An authenticated entity should be given a service
access level in a configurable policy basis.
l Each entity should be authorized to use network resources according to its service
level.
l A corresponding mechanism should be set up at UNI and NNI to ensure the integrity
of client authentication and link information, such as link setup, release and signaling
information, in order to manage connections and guard against service intrusions.
Usage based billing should be realized at UNI and E-NNI. It should be stringent
enough to avoid any repudiation. Repudiation means that an entity involved in a
communication exchange subsequently denies the fact.
A.5.2 Cases of ASON Service Model

This topic introduces the following three cases of ASON service model:
l Enhanced private line service
l Bandwidth On Demand (BOD) service
l Optical Virtual Private Network (OVPN) service
Enhanced Private Line Service

Enhanced private lines provide enhanced leased or private services, which are assigned
in real time or approximately real time by service Management Interfaces (MIs) of PC or
SPC. They share the following features:
l A connection should be requested via service management interface.
l A client device and optical network has a relationship of client/server.
l The optical network is invisible to clients. And the setup of optical connections
depends on the intelligence of the network.
The management plane and control plane in ASON cooperates to realize an SPC, which
can provide services quickly. Clients just need to tell the carrier where and what kind of
A-17

service is needed. The carrier can set up satisfactory service connections almost in real
time through the management plane and control plane. In addition, the carrier can change
the service attributes fast in condition that lines between clients and carrier network can
meet the requirements.
BOD Service
BOD services are automatic connection services whose bandwidth is allocated on demand
via UNI signaling interfaces. Such connections, being switched connections, are set up in
real time. BOD services share the following features:
l Optical network can be invisible or visible in a limited degree for clients according to
actual interconnection modes or network management policies.
l A BOD service connection is based on the intelligence of either optical network or
client according to different interconnection models on the control plane.
l A client device or its agent can initiate a connection request directly via UNI.
When a connection is requested via UNI, optical transport network can set up
corresponding service connection as required. A client device must have the capability of
service discovery to get service information in the transport network via its UNI-N. During
setting up the connection, the service attributes must be found, including framing mode,
signal type, transparency, and cascading mode etc.
Two request modes are optional when a client device requests a service connection via
UNI: direct request and indirect request, as illustrated in Figure A-7.
A-18

Figure A-7 Direct and Indirect Request via UNI
l Direct request: UNI-C functions are implemented in a client device, which can directly
request for services in a transport network.
l Indirect request: UNI-C is independent of a client device. It performs UNI functions
on behalf of one or multiple client devices.
OVPN Service
OVPN service is a kind of virtual private network service provided for a specific client group.
OVPN services share the following features:
l Clients sign to use certain network resources, such as optical connection ports and
wavelengths etc.
l OVPN services support Closed User Group (CUG). Any site in an OVPN can request
to dynamically configure connections with other sites in the same CUG.
l Optical connections for OVPN services can be PC, SPC or SC, depending on different
assignment modes.
l A client has the visibility and control capability of network resources as its service
contract allows.
l OVPN supports basic functions of an ASON platform, such as protection/restoration
and end-to-end service connection setup etc.
An optical transport network can be divided into multiple OVPNs. The network resources
of each part can only belong to one OVPN. Authorized clients of an OVPN can manage
corresponding resources of the network.
A-19

A.5.3 Management of ASON Services

The ASON management plane focuses on the management of connections and dynamic
services, not like traditional networks focusing on equipment management and control.
The management plane can assign the attributes of all kinds of connection services.
Normal connection management operations (such as connection release) will not lead
protection and restoration. ASON supports the protection and restoration initiated by the
management plane in maintenance, which forces traffic to be switched to a protection
circuit.
The ASON management plane provides the following service management functions:
l End-to-end service assignment
l Service setup and release
l Service protection/restoration mechanism
l Service attribute and service level agreement
l OVPN management
ASON service management systems, supporting traditional service management
functions, are compatible with previous service management systems.
A-20

List of Figures
Figure 1-1 Outline of ZXONE 5800 Subrack in Cabinet............................................. 1-3
Figure 2-1 ZXONE 5800 Cabinet .............................................................................. 2-2
Figure 2-2 Subrack Structure .................................................................................... 2-3
Figure 2-3 Relationship Between the Functional Units of ZXONE 5800..................... 2-5
Figure 2-4 Relationship Between the Functional Planes............................................ 2-7
Figure 3-1 Software Structure of ZXONE 5800 ......................................................... 3-1
Figure 3-2 Architecture of the EMS Software ............................................................ 3-3
Figure 4-1 End-to-End Service Configuration ........................................................... 4-9
Figure 4-2 Restoration of Mesh Network ................................................................. 4-10
Figure 4-3 Level 1 Service ...................................................................................... 4-12
Figure 4-4 Level 2 Service ...................................................................................... 4-13
Figure 4-5 Tunnel Services ..................................................................................... 4-16
Figure 4-6 1+1 Associated Service Diagram 1 ........................................................ 4-17
Figure 4-7 1+1 Associated Service Diagram 2 ........................................................ 4-18
Figure 4-8 Non 1+1 Associated Service Diagram.................................................... 4-19
Figure 4-9 Example of Resource Sharing................................................................ 4-22
Figure 4-10 Resource Sharing Between Two Connections of the Same
Service ................................................................................................. 4-23
Figure 4-11 Resource Sharing Among Three Connections of the Same
Service ................................................................................................. 4-23
Figure 4-12 Interconnection Between Traditional Service and ASON Service
1 ........................................................................................................... 4-24
2 ........................................................................................................... 4-25
3 ........................................................................................................... 4-25
Figure 5-1 Layout of Board Slots............................................................................... 5-2
Figure 5-2 Principle of TM Equipment ....................................................................... 5-5
Figure 5-3 Configuration Example of TM Equipment ................................................. 5-7
Figure 5-4 Principle of ADM Equipment .................................................................... 5-8
Figure 5-5 Configuration Example of ADM Equipment .............................................. 5-9
Figure 5-6 Principle of SDXC Equipment ................................................................ 5-10
Figure 5-7 Configuration Example of SDXC Equipment .......................................... 5-11
I
Figure 5-8 Point-to-Point Networking ..................................................................... 5-12

Figure 5-9 Chain Networking .................................................................................. 5-13
Figure 5-10 Ring Networking .................................................................................. 5-14
Figure 5-11 Normal Service Routes in Four-Fiber Bidirectional MS Shared
Ring...................................................................................................... 5-15
Figure 5-12 Service Routes After Protection Switching in Four-Fiber Bidirectional
MS Shared Ring ................................................................................... 5-15
Figure 5-13 Star Networking ................................................................................... 5-16
Figure 5-14 Mesh Networking ................................................................................. 5-17
Figure 5-15 Hybrid Network .................................................................................... 5-18
Figure 5-16 Traditional SDH Networking Application ............................................... 5-19
Figure 5-17 ASON Networking Application.............................................................. 5-20
Figure 5-18 GE Service Networking Application...................................................... 5-21
Figure 5-19 Application of ZXONE 5800 for EPL..................................................... 5-22
Figure 5-20 Locations of Site A, B, C, and D ........................................................... 5-23
Figure 5-21 Network Topology ................................................................................ 5-24
Figure A-1 Architecture of ASON ..............................................................................A-4
Figure A-2 Signaling Control Interfaces in ASON ......................................................A-8
Figure A-3 GMPLS Protocol......................................................................................A-9
Figure A-4 Mesh Networking...................................................................................A-12
Figure A-5 Hybrid Networking via UNI.....................................................................A-12
Figure A-6 Hybrid Networking via NNI.....................................................................A-13
Figure A-7 Direct and Indirect Request via UNI.......................................................A-19
II
List of Tables
Table 2-1 Dimensions and Weight of Cabinet............................................................ 2-2
Table 2-2 Technical Parameters of the ZXONE 5800 Subrack................................... 2-3
Table 2-3 Board List.................................................................................................. 2-4
Table 3-1 Communication Interfaces in ZXONE 5800 Software System .................... 3-4
Table 4-1 Types of Services Supported By ZXONE 5800 .......................................... 4-1
Table 4-2 Service Access Capacity of ZXONE 5800 ................................................. 4-2
Table 4-3 Cross-Connection Capacity of ZXONE 5800 ............................................. 4-3
Table 4-4 SDH Digital Performance Items Detected by ZXONE 5800........................ 4-5
Table 4-5 Analog Performance Items Detected by ZXONE 5800............................... 4-6
Table 4-6 Ethernet Performance Items Detected by ZXONE 5800 ............................ 4-6
Table 4-7 ZXONE 5800 Service Levels ................................................................... 4-10
Table 4-8 List of Transfers Between PC Services and SPC Services ...................... 4-20
Table 5-1 Boards and Slots ....................................................................................... 5-3
Table 5-2 Boards and Slots ....................................................................................... 5-3
Table 5-3 Board Configurations of Each Site ........................................................... 5-25
III
List of Tables
This page intentionally left blank.

Glossary
ADM
- Add/Drop Multiplexer
APS
- Automatic Protection Switching
ASON
- Automatically Switched Optical Network
ASP
- Application Service Provider
BBE
- Background Block Error
BGP
- Border Gateway Protocol
BOD
- Bandwidth On Demand
CP
- Control Plane
CR-LDP
- Constrained Route - Label Distribution Protocol
CSPF
- Constrained Shortest Path First
CUG
- Closed User Group
CoS
- Class of Service
DCC
- Data Communications Channel
DCM
- Dispersion Compensation Module
DDRP
- Domain to Domain Routing Protocol
DXC
- Digital Cross Connect
E-NNI
- External Network-Network Interface
V
ECC
- Embedded Control Channel
EDFA
- Erbium Doped Fiber Amplifier
EMS
- Network Element Management System
EPL
- Ethernet Private Line
ES
- Errored Second
ESCON
- Enterprise System Connection
ETS
- European Telecommunication Standard
EXC
- Excessive Bit Error Ratio
FC
- Fiber Channel
FEBBE
- Far End Background Block Error
FEES
- Far End Errored Second
FESES
- Far End Severely Errored Second
FEUAS
- Far End Unavailable Second
FICON
- Fiber Connection
GE
- Gigabit Ethernet
GFP
- Generic Framing Procedure
GMPLS
- Generalized Multi-Protocol Label Switching
GUI
- Graphical User Interface
I-NNI
- Internal Network-Network Interface
VI
Glossary
IP
- Internet Protocol
IPCoS
- IP Class of Service
IPMI
- Intelligent Platform Management Interface
IS-IS
- Intermediate System-to-Intermediate System
ISP
- Internet Service Provider
ITU-T
- International Telecommunication Union - Telecommunication Standardization
Sector
L2
- Layer 2
LCT
- Local Craft Terminal
LMP
- Link Management Protocol
LSA
- Link State Advertisement
LSP
- Label Switched Path
MAC
- Medium Access Control
MI
- Management Interface
MP
- Management Plane
MPLS
- Multi Protocol Label Switching
MS
- Media Server
NNI
- Network Node Interface
NSAP
- Network Service Access Point
OBA
- Optical Booster Amplifier
VII
OFS
- Out of Frame Second
OPA
- Optical Pre-Amplifier
OSPF
- Open Shortest Path First
OTN
- Optical Transport Network
OVPN
- Optical Virtual Private Network
PC
- Permanent Connection
PJE+
- Positive Pointer Justification Event
PJE-
- Negative Pointer Justification Event
PNNI
- Private or Public Network-to-Network Interface
QoS
- Quality of Service
RSVP-TE
- Resource ReSerVation Protocol - Traffic Engineering
SAN
- Storage Area Network
SC
- Switched Connection
SD
- Signal Degrade
SDH
- Synchronous Digital Hierarchy
SES
- Severely Errored Second
SLA
- Service Level Agreement
SMCC
- Sub-network Management Control Center
SNC
- Sub-Network Connection
VIII
Glossary
SNCP
- Sub-Network Connection Protection
SPC
- Soft Permanent Connection
SPF
- Shortest Path First
SRLG
- Shared Risk Link Group
SSM
- Synchronization Status Message
STM-N
- Synchronous Transport Module, level NN=1, 4, 16, 64
TCP
- Transfer Control Protocol
TE
- Traffic Engineering
TM
- Terminal Multiplexer
TP
- Transport Plane
TTI
- Trail Trace Identifier
UAS
- Unavailable Seconds
UNI
- User Network Interface
UNI-C
- UNI Signaling Agent - Client
UNI-N
- UNI Signaling Agent - Network
VC-n
- Virtual Container, level n
WDM
- Wavelength Division Multiplexing
IX

ZXONE 5800: Multi-Service Core Optical Switch Equipment

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZXONE 5800: Multi-Service Core Optical Switch Equipment

Uploaded by

Copyright:

Available Formats

ZXONE 5800

Multi-service Core Optical Switch Equipment

Revision No. Revision Date Revision Reason

R1.1 2012–02–20 Updated

R1.0 2011–12–30 ZXONE 5800(V1.20) Issued

Serial Number: SJ-20111121090706-001

Publishing Date: 2012-02-20(R1.1)

Chapter 2 Hardware Architecture ............................................................. 2-1

Chapter 3 Software Architecture............................................................... 3-1

Chapter 4 System Functions ..................................................................... 4-1

Chapter 5 Configuration and Network Architecture................................ 5-1

Appendix A Fundamentals of ASON ....................................................... A-1

What Is in This Manual

Chapter 1, System Describes features and applications of ZXONE 5800.

Chapter 4, System Describes system functions of ZXONE 5800.

Chapter 5, Configuration Describes the equipment configuration, typical NE configuration,

Unitrans ZXONE 5800 (V1.20) Multi-Service Describes on-site installation procedures,

Italics References to other manuals and documents.

“Quotes” Links on screens.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before proceeding

1.1 Introduction to ZXONE 5800

SJ-20111121090706-001|2012-02-20(R1.1) ZTE Proprietary and Confidential

SJ-20111121090706-001|2012-02-20(R1.1) ZTE Proprietary and Confidential

Figure 1-1 Outline of ZXONE 5800 Subrack in Cabinet

1.2 Application of ZXONE 5800

SJ-20111121090706-001|2012-02-20(R1.1) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20111121090706-001|2012-02-20(R1.1) ZTE Proprietary and Confidential

Cabinet Outline and Configuration

SJ-20111121090706-001|2012-02-20(R1.1) ZTE Proprietary and Confidential

Figure 2-1 ZXONE 5800 Cabinet

Table 2-1 Dimensions and Weight of Cabinet

Cabinet Type (Height × Width × Depth, mm) Weight (kg)

SJ-20111121090706-001|2012-02-20(R1.1) ZTE Proprietary and Confidential

Figure 2-2 Subrack Structure

1. Top cover board 4. Board area 7. Fiber tray

Table 2-2 Technical Parameters of the ZXONE 5800 Subrack

Dimension (Height × Width × Depth, mm) Weight (kg)

1349 × 497 × 270 38.5

SJ-20111121090706-001|2012-02-20(R1.1) ZTE Proprietary and Confidential

Table 2-3 Board List

Board Code Board Name

NCPA Net control processor, type A

NCPB Net control processor, type B

SAIA System application interface, type A

HOXA Higher-order cross-connect, type A

HOXB Higher-order cross-connect, type B

LOXA Lower-order cross-connect, type A

S64Ax4 4–port STM-64 optical line, type A

S64Ax2 2–port STM-64 optical line, type A

S64A Single-port STM-64 optical line, type A

S64AFECx4 4–port STM-64 FEC optical line, type A

S64AFECx2 2–port STM-64 FEC optical line, type A

16Ax8 Single-port STM-64 FEC optical line, type A

S16Ax8 8–port STM-16 optical line, type A

S16Ax4 4–port STM-16 optical line, type A

S4Ax16 16–port STM-4/1 optical line, type A

S4Ax8 8–port STM-4/1 optical line, type A

SGEAx8 8–port transparent gigabit Ethernet, SDH, type A

SGEAx4 4–port transparent gigabit Ethernet, SDH, type A

SGESx8 8–port GE Ethernet processor, SDH, type S

SGESx4 4–port GE Ethernet processor, SDH, type S