PTN3900 Product Description

00534442
OptiX PTN 3900 Packet Transport Platform of PTN Series

V100R002C00
Product Description
Issue 01
Date 2009-06-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided “AS IS” without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2009-06-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Product Description About This Document
About This Document
Purpose
This document describes the networking application, functions, structure, features of the
equipment.
This document provides guides to get the general information about the OptiX PTN 3900.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX PTN 3900 V100R002C00
OptiX iManager T2000 V200R007C03
Intended Audience
This document is intended for:
l Network Planning Engineers
Organization
This document is organized as follows.
Chapter Description
1 Overview Describes the equipment features and the position of the

equipment in the network.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential iii

About This Document Product Description
Chapter Description
2 Functions and Features Describes the service types, processing capability, service
interfaces, protection capability, QoS, OAM feature, NSF
function and DCN mode that are supported by the
equipment.
3 System Architecture Describes the functional modules, hardware structure and

software structure of the equipment.
4 Services Describes the services of the equipment.
5 Key Features Describes the main features of the equipment.
6 Protection Describes the equipment-level protection and network-level

protection of the equipment.
7 Operation, Administration Describes the operation, maintenance and management

and Maintenance capabilities of the equipment and the T2000 network
management system used for the equipment.
8 Security Management Describes the main technical characteristics of the

equipment in terms of safe operation.
9 Networking Application Describes the application of the equipment on mobile

services , L2VPN services and offload solutions.
10 Technical Specifications Describes the technical specifications of the equipment.
A Compliant Standards and Describes the compliant standards and protocols of the
Protocols equipment.
B Glossary Lists the glossary used in this document.
C Acronyms and Lists the acronyms and abbreviations used in this document.
Abbreviations
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
WARNING
iv Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Symbol Description
Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,
CAUTION
performance degradation, or unexpected results.
NOTE Indicates a tip that may help you solve a problem or save
time.
TIP Provides additional information to emphasize or supplement
important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential v

GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Update History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Update in 01 (2009-06-30) Based on Product Version V100R002C00

This document is the first release of the V100R002C00 version.
vi Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Update in Issue 07 (2009-06-01) Based on Product Version V100R001

The update of the document are as follow:
l Chapter 10 Technical Specifications:
The power consumption is updated.

The technical specifications of the optical interfaces on the boards are updated.

l Chapter 2 Functions and Features, Chapter 3 System Architecture and Chapter 10
Technical Specifications:
TN82XCS, TN82EG16 and TN81EFF8 boards are added.
l Chapter 2 Functions:
External time interface is added.
l Chapter 5 Key Features:
IEEE 1588 V2 clock is added.
The maximum number of virtual ports supported for each VSI is modified from 64 to 256.
The number of supported APS protection groups is added.
The number of supported ML-PPP groups is added.
l Chapter 4 Services and Chapter 10 Technical Specifications:
The number of supported ATM connections supported by the OptiX PTN 3900 is modified
from 4k to 8k (remote service) and from 2k to 4k (local service).

DCN packets can be transparently transported over the IP tunnel or GRE tunnel is added.
Synchronous Ethernet Clock is added.

l Chapter 2 Functions and Features, Chapter 3 System Architecture and Chapter 10
Technical Specifications:
EX2 board is added.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential vii

l Chapter 2 Functions and Features and Chapter 6 Protection:

TPS protection is added.
The number of supported ATM services supported by the OptiX PTN 3900 is modified
from 512 to 2k (remote service) and from 512 to 1k (local service).
The number of supported ATM connections supported by the OptiX PTN 3900 is modified
from 1k to 4k (remote service) and from 1k to 2k (local service).

l Chapter 2 Functions and Features and Chapter 10 Technical Specifications:
Information about the Ve-1.2 interface is deleted.
The supported number of MAC addresses is described separately for the static and dynamic
scenarios.
The lower limit of the wavelength range of the CMR2 is changed from 1291 to 1271.

This document is the first release of the V100R001 version.
viii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Product Description Contents
Contents
About This Document...................................................................................................................iii

1 Overview......................................................................................................................................1-1
1.1 Equipment Introduction...................................................................................................................................1-2
1.2 Network Application.......................................................................................................................................1-3
2 Functions and Features..............................................................................................................2-1

2.1 Service Types..................................................................................................................................................2-3
2.2 Service Processing Capability.........................................................................................................................2-3
2.2.1 Switching Capability..............................................................................................................................2-3
2.2.2 Maximum Access Capability.................................................................................................................2-3
2.3 Interface Types................................................................................................................................................2-4
2.3.1 Service Interfaces...................................................................................................................................2-5
2.3.2 Administration and Auxiliary Interfaces................................................................................................2-5
2.4 Networking Capability....................................................................................................................................2-6
2.5 Protection Capability.....................................................................................................................................2-11
2.6 QoS................................................................................................................................................................2-12
2.7 OAM Features...............................................................................................................................................2-13
2.8 NSF................................................................................................................................................................2-14
2.9 Clock.............................................................................................................................................................2-14
2.10 DCN Scheme...............................................................................................................................................2-15
3 System Architecture...................................................................................................................3-1
3.1 Functional Modules.........................................................................................................................................3-2
3.2 Hardware Structure......................................................................................................................................... 3-3
3.2.1 Overview................................................................................................................................................3-4
3.2.2 Cabinet................................................................................................................................................... 3-4
3.2.3 Subrack...................................................................................................................................................3-6
3.2.4 Boards.....................................................................................................................................................3-9
3.2.5 Valid Slots for Boards..........................................................................................................................3-10
3.3 Software Architecture...................................................................................................................................3-12
3.3.1 Overview..............................................................................................................................................3-12
3.3.2 NE Software.........................................................................................................................................3-14
3.3.3 Board Software.....................................................................................................................................3-15
4 Services.........................................................................................................................................4-1
Issue 01 (2009-06-30) Huawei Proprietary and Confidential ix

Contents Product Description
4.1 Overview.........................................................................................................................................................4-2
4.1.1 Service Model........................................................................................................................................4-2
4.1.2 Service Processing..................................................................................................................................4-7
4.2 Ethernet Service..............................................................................................................................................4-9
4.3 ATM Service.................................................................................................................................................4-13
4.4 Circuit Emulation Service.............................................................................................................................4-14
4.5 L3VPN Services............................................................................................................................................4-16
5 Key Features................................................................................................................................5-1
5.1 MPLS..............................................................................................................................................................5-3
5.1.1 MPLS Background.................................................................................................................................5-3
5.1.2 Basic MPLS Concepts............................................................................................................................5-3
5.1.3 MPLS System Structure.........................................................................................................................5-5
5.1.4 MPLS Features of the Equipment..........................................................................................................5-5
5.2 IS-IS Routing Protocol....................................................................................................................................5-6
5.3 BGP.................................................................................................................................................................5-8
5.4 OSPF Protocol...............................................................................................................................................5-10
5.5 RIP.................................................................................................................................................................5-12
5.6 MPLS Signaling............................................................................................................................................5-14
5.7 PWE3............................................................................................................................................................5-14
5.8 IP Tunnel and GRE Tunnel...........................................................................................................................5-15
5.9 QoS................................................................................................................................................................5-17
5.10 IGMP Snooping...........................................................................................................................................5-20
5.11 MSTP/RSTP/STP........................................................................................................................................5-21
5.12 ACL ............................................................................................................................................................5-22
5.13 BFD.............................................................................................................................................................5-23
5.14 Synchronous Ethernet Clock.......................................................................................................................5-23
5.15 IEEE 1588 V2 Clock...................................................................................................................................5-25
6 Protection.....................................................................................................................................6-1
6.1 Equipment Level Protection............................................................................................................................6-2
6.1.1 TPS Protection........................................................................................................................................6-2
6.1.2 1+1 Protection for the SCA Board.........................................................................................................6-3
6.1.3 1+1 Protection for the Cross-Connect and Timing Board......................................................................6-4
6.1.4 1+1 Protection for the PIU.....................................................................................................................6-5
6.2 Network Level Protection...............................................................................................................................6-5
6.2.1 MPLS 1+1 and 1:1 Protection................................................................................................................6-6
6.2.2 FRR Protection.......................................................................................................................................6-8
6.2.3 Ethernet LAG Protection......................................................................................................................6-10
6.2.4 Ethernet Spanning Tree Protection......................................................................................................6-11
6.2.5 LMSP Protection..................................................................................................................................6-13
6.2.6 Packet E1 ML-PPP Protection.............................................................................................................6-16
6.2.7 IMA Protection.....................................................................................................................................6-17
x Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Product Description Contents
7 Operation, Administration and Maintenance......................................................................7-1

7.1 OAM Capability..............................................................................................................................................7-2
7.1.1 Operation and Configuration Tools........................................................................................................7-2
7.1.2 Monitoring and Maintenance.................................................................................................................7-2
7.1.3 Diagnosis and Debugging...................................................................................................................... 7-3
7.1.4 Expansion and Upgrade......................................................................................................................... 7-3
7.2 T2000 Network Management System.............................................................................................................7-3
8 Security Management................................................................................................................8-1
8.1 Authentication Management...........................................................................................................................8-2
8.2 Authorization Management.............................................................................................................................8-2
8.3 Network Security Management.......................................................................................................................8-2
8.4 System Security Management.........................................................................................................................8-3
8.5 NE Security Log Management........................................................................................................................8-3
8.6 Syslog Management........................................................................................................................................8-3
9 Networking Application...........................................................................................................9-1
9.1 Application of the Equipment for Mobile Services........................................................................................ 9-2
9.2 Application of the OptiX PTN 3900 for the L2VPN Service.........................................................................9-6
9.2.1 Transport of the E-Line Service.............................................................................................................9-6
9.2.2 Transport of the E-LAN Service............................................................................................................9-7
9.3 Offload Solution..............................................................................................................................................9-9
10 Technical Specifications.......................................................................................................10-1
10.1 System Specifications.................................................................................................................................10-2
10.2 System Performance....................................................................................................................................10-3
10.3 Technical Specifications of Boards.............................................................................................................10-6
10.3.1 Technical Specification of the TN81EG16........................................................................................10-7
10.3.2 Technical Specification of the TN82EG16........................................................................................10-8
10.3.3 Technical Specification of the EX2....................................................................................................10-9
10.3.4 Technical Specification of the ETFC...............................................................................................10-10
10.3.5 Technical Specifications of the EFF8..............................................................................................10-11
10.3.6 Technical Specification of the EFG2...............................................................................................10-11
10.3.7 Technical Specification of the MP1.................................................................................................10-12
10.3.8 Technical Specification of the MD1................................................................................................10-13
10.3.9 Technical Specification of the MQ1................................................................................................10-13
10.3.10 Technical Specification of the CD1...............................................................................................10-13
10.3.11 Technical Specification of the AD1...............................................................................................10-13
10.3.12 Technical Specification of the ASD1.............................................................................................10-14
10.3.13 Technical Specifications of the AFO1...........................................................................................10-15
10.3.14 Technical Specification of the POD41...........................................................................................10-16
10.3.15 Technical Specification of the D12................................................................................................10-17
10.3.16 Technical Specification of the D75................................................................................................10-17
10.3.17 Technical Specification of the CMR4............................................................................................10-18
Issue 01 (2009-06-30) Huawei Proprietary and Confidential xi

Contents Product Description
10.3.18 Technical Specification of the CMR2............................................................................................10-19

10.3.19 Technical Specification of the TN81SCA......................................................................................10-20
10.3.20 Technical Specification of the TN82SCA......................................................................................10-20
10.3.21 Technical Specification of the TN81XCS......................................................................................10-21
10.3.22 Technical Specification of the TN82XCS......................................................................................10-21
10.3.23 Technical Specification of the PIU................................................................................................10-21
10.3.24 Technical Specification of the FAN...............................................................................................10-21
10.4 Laser Class................................................................................................................................................10-21
10.5 Specifications of Clock Interfaces.............................................................................................................10-22
10.6 Reliability Specifications..........................................................................................................................10-23
10.7 EMC Performance Specifications.............................................................................................................10-23
10.8 Safety Certification...................................................................................................................................10-24
10.9 Environment Requirements.......................................................................................................................10-25
10.9.1 Environment for Storage..................................................................................................................10-25
10.9.2 Environment for Transportation.......................................................................................................10-27
10.9.3 Environment for Operation..............................................................................................................10-29
A Compliant Standards and Protocols.....................................................................................A-1

B Glossary......................................................................................................................................B-1
C Acronyms and Abbreviations................................................................................................C-1
Index.................................................................................................................................................i-1
xii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Product Description Figures
Figures
Figure 1-1 Appearance of the OptiX PTN 3900..................................................................................................1-2

Figure 1-2 Network application of the OptiX PTN 3900.....................................................................................1-3
Figure 2-1 Networking mode I for mobile communication.................................................................................2-7
Figure 2-2 Networking mode II for mobile communication................................................................................2-8
Figure 2-3 Networking mode for offload solution...............................................................................................2-8
Figure 2-4 Networking Mode for E-Line Services...............................................................................................2-9
Figure 2-5 Networking Mode for E-LAN Services..............................................................................................2-9
Figure 2-6 Networking Mode for E-Aggr Services............................................................................................2-10
Figure 2-7 Networking Mode for L3VPN..........................................................................................................2-11
Figure 2-8 OAM mechanism of the OptiX PTN 3900.......................................................................................2-13
Figure 3-1 Functional modules of the OptiX PTN 3900......................................................................................3-2
Figure 3-2 Hardware structure of the OptiX PTN 3900.......................................................................................3-4
Figure 3-3 Appearance of the cabinets used to house the OptiX PTN 3900........................................................3-5
Figure 3-4 Structure of the OptiX PTN 3900 subrack.........................................................................................3-6
Figure 3-5 Slot layout of the OptiX PTN 3900....................................................................................................3-7
Figure 3-6 Slot processing capacity of the OptiX PTN 3900...............................................................................3-9
Figure 3-7 Logical block diagram for the software architecture of the OptiX PTN 3900.................................3-13
Figure 3-8 Architecture of the NE software for the OptiX PTN 3900...............................................................3-14
Figure 3-9 Architecture of the board software for the OptiX PTN 3900...........................................................3-15
Figure 4-1 MPLS-Based PWE3 Service model of the OptiX PTN 3900............................................................4-3
Figure 4-2 BGP/MPLS service model of the OptiX PTN 3900...........................................................................4-5
Figure 4-3 OptiX PTN 3900 service model.........................................................................................................4-6
Figure 4-4 E-Line service illustration................................................................................................................4-11
Figure 4-5 E-LAN service illustration................................................................................................................4-12
Figure 4-6 E-Aggr service illustration................................................................................................................4-13
Figure 4-7 CES service application model.........................................................................................................4-15
Figure 4-8 Retiming synchronization mode of the CES service clock..............................................................4-16
Figure 4-9 Networking Application of the BGP/MPLS L3VPN.......................................................................4-17
Figure 4-10 Service packet forwarding of the BGP/MPLS L3VPN..................................................................4-18
Figure 5-1 Label encapsulation structure.............................................................................................................5-4
Figure 5-2 Encapsulation location of labels in Ethernet frames...........................................................................5-4
Figure 5-3 Typical application of the PWE3......................................................................................................5-15
Figure 5-4 ATM PWE3 over MPLS tunnel.......................................................................................................5-16
Issue 01 (2009-06-30) Huawei Proprietary and Confidential xiii

Figures Product Description
Figure 5-5 ATM PWE3 over IP tunnel..............................................................................................................5-16

Figure 5-6 ATM PWE3 over GRE tunnel .........................................................................................................5-17
Figure 5-7 ACL based on flow classification.....................................................................................................5-23
Figure 5-8 Typical networking for synchronous Ethernet................................................................................. 5-24
Figure 5-9 Architecture of the IEEE 1588 V2 clock..........................................................................................5-25
Figure 5-10 Typical networking for IEEE 1588 V2 clock synchronization...................................................... 5-27
Figure 6-1 MPLS 1+1 protection.........................................................................................................................6-6
Figure 6-2 MPLS 1:1 protection..........................................................................................................................6-7
Figure 6-3 FRR protection...................................................................................................................................6-9
Figure 6-4 Ethernet LAG protection..................................................................................................................6-10
Figure 6-5 Switching network with multiple VLANs........................................................................................6-12
Figure 6-6 Network topology after the MSTP begins running.......................................................................... 6-13
Figure 6-7 LMSP 1+1 protection....................................................................................................................... 6-14
Figure 6-8 LMSP 1:1/1:N protection................................................................................................................. 6-15
Figure 6-9 Packet E1 ML-PPP protection..........................................................................................................6-17
Figure 6-10 IMA transmission...........................................................................................................................6-17
Figure 8-1 Schematic diagram of Syslog protocol transmitting...........................................................................8-4
Figure 9-1 Networking application of the OptiX PTN 3900 for transport of mobile services (E1 service between
the base station and equipment)............................................................................................................................9-4
Figure 9-2 Networking application of the OptiX PTN 3900 for transport of mobile services (IMA E1 service
between the base station and equipment)..............................................................................................................9-5
Figure 9-3 Networking application of the OptiX PTN 3900 for transport of mobile services (FE service between
the base station and equipment)............................................................................................................................9-6
Figure 9-4 Networking Application of the E-Line Service..................................................................................9-7
Figure 9-5 Networking Application of the E-LAN Service.................................................................................9-8
Figure 9-6 Offload solution................................................................................................................................9-10
Figure 9-7 Application in an ATM-forwarding-based ADSL network (MPLS Tunnel used)...........................9-10
Figure 9-8 Application in an ATM-forwarding-based ADSL network (IP Tunnel used)..................................9-11
Figure 9-9 Application in an ATM-forwarding-based ADSL network (GRE Tunnel used).............................9-11
Figure 9-10 Application in an ETH-forwarding-based ADSL network.............................................................9-12
Figure 9-11 Application in an IP-forwarding-based ADSL network (IP tunnel used)...................................... 9-12
Figure 9-12 Application in an IP-forwarding-based ADSL network (GRE tunnel used)..................................9-12
xiv Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Product Description Tables
Tables
Table 2-1 Switching capability of the OptiX PTN 3900......................................................................................2-3

Table 2-2 OptiX PTN 3900 interface quantity.....................................................................................................2-4
Table 2-3 Service interfaces of the OptiX PTN 3900..........................................................................................2-5
Table 2-4 Administration and auxiliary interfaces of the OptiX PTN 3900........................................................2-6
Table 2-5 Equipment level protection................................................................................................................2-11
Table 2-6 Network level protection....................................................................................................................2-12
Table 3-1 Mapping relation between slots for processing boards and interface boards of the OptiX PTN 3900
...............................................................................................................................................................................3-8
Table 3-2 Mapping relation between processing boards and interface boards of the OptiX PTN 3900..............3-8
Table 3-3 Boards and their key functions...........................................................................................................3-10
Table 3-4 Valid slots for boards in the OptiX PTN 3900 subrack.....................................................................3-11
Table 4-1 Comparison among L2 Ethernet services stipulation.........................................................................4-10
Table 4-2 Instances for service packet forwarding of the BGP/MPLS L3VPN.................................................4-18
Table 5-1 MPLS features of OptiX PTN 3900.....................................................................................................5-6
Table 5-2 MPLS specification of OptiX PTN 3900.............................................................................................5-6
Table 5-3 HQoS action points at the access side and the network side of the equipment..................................5-20
Table 5-4 Comparison among the MSTP, STP and RSTP.................................................................................5-21
Table 6-1 E1 TPS protection schemes and supported boards .............................................................................6-2
Table 6-2 Mapping relations between working and protection slots in TPS protection......................................6-3
Table 6-3 TPS protection parameters...................................................................................................................6-3
Table 6-4 1+1 protection parameters of the SCA board.......................................................................................6-4
Table 6-5 1+1 protection parameters of the cross-connect and timing board......................................................6-4
Table 6-6 MPLS 1+1 and 1:1 protection parameters...........................................................................................6-7
Table 6-7 LMSP protection parameters..............................................................................................................6-16
Table 9-1 Application of the OptiX PTN 3900 for the mobile service................................................................9-2
Table 9-2 Application of the OptiX PTN 3900 for the E-Line service................................................................9-7
Table 9-3 Application of the OptiX PTN 3900 for the E-LAN service...............................................................9-8
Table 10-1 Specifications of the ETSI cabinet for the OptiX PTN 3900 subrack.............................................10-2
Table 10-2 Specifications of the OptiX PTN 3900 subrack...............................................................................10-3
Table 10-3 System performance specifications..................................................................................................10-3
Table 10-4 Specifications of the interfaces on the TN81EG16..........................................................................10-7
Table 10-5 Wavelengths of 1000BASE-CWDM interfaces on the TN81EG16................................................10-8
Table 10-6 Specifications of the interfaces on the TN82EG16..........................................................................10-8
Table 10-7 Wavelengths of 1000BASE-CWDM interfaces on the TN82EG16................................................10-9
Issue 01 (2009-06-30) Huawei Proprietary and Confidential xv

Tables Product Description
Table 10-8 Specifications of interfaces on the EX2.........................................................................................10-10

Table 10-9 Interface specifications of the ETFC..............................................................................................10-10
Table 10-10 Specifications of the interfaces on the EFF8................................................................................10-11
Table 10-11 Specifications of the interfaces on the EFG2...............................................................................10-12
Table 10-12 Wavelengths of 1000BASE-CWDM interfaces on the EFG2.....................................................10-12
Table 10-13 Specifications of interfaces on the CD1.......................................................................................10-13
Table 10-14 Specifications of interfaces on the AD1.......................................................................................10-14
Table 10-15 Specifications of interfaces on the ASD1....................................................................................10-14
Table 10-16 Specifications of interfaces on the AFO1....................................................................................10-15
Table 10-17 Specifications of interfaces on the POD41..................................................................................10-16
Table 10-18 Specifications of interfaces on the POD41..................................................................................10-16
Table 10-19 Interface specifications of the D12...............................................................................................10-17
Table 10-20 Interface specifications of the D75...............................................................................................10-17
Table 10-21 Specifications of optical interfaces on the CMR4........................................................................10-18
Table 10-22 Rules of adding/dropping wavelength of the CMR4...................................................................10-19
Table 10-23 Specifications of optical interfaces on the CMR2........................................................................10-19
Table 10-24 Rules of adding/dropping wavelength of the CMR2...................................................................10-20
Table 10-25 Laser Class...................................................................................................................................10-22
Table 10-26 Specifications of clock interfaces of the OptiX PTN 3900..........................................................10-22
Table 10-27 Timing and synchronization performance....................................................................................10-23
Table 10-28 Reliability specifications..............................................................................................................10-23
Table 10-29 Safety certifications that the OptiX PTN 3900 has passed..........................................................10-24
Table 10-30 Climatic requirements of the OptiX PTN 3900 for storage.........................................................10-25
Table 10-31 Density requirements for mechanically active substances during storage...................................10-26
Table 10-32 Density requirements for chemically active substances during storage.......................................10-26
Table 10-33 Requirements of mechanical stress for storage............................................................................10-27
Table 10-34 Climatic requirements for transportation.....................................................................................10-27
Table 10-35 Density requirements for mechanically active substances during transportation........................10-28
Table 10-36 Density requirements for chemically active substances during transportation............................10-28
Table 10-37 Requirements of mechanical stress for transportation.................................................................10-29
Table 10-38 Temperature and humidity required by the OptiX PTN 3900 for operation................................10-29
Table 10-39 Other climatic requirements of the OptiX PTN 3900 for operation............................................10-30
Table 10-40 Density requirements for mechanically active substances during operation...............................10-30
Table 10-41 Density requirements for chemically active substances during operation...................................10-30
Table 10-42 Requirement of mechanical stress for operation..........................................................................10-31
xvi Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Product Description 1 Overview
1 Overview
About This Chapter
This chapter describes the features and network application of the OptiX PTN 3900.
1.1 Equipment Introduction
The OptiX PTN 3900 is new generation metropolitan optical transport platform, which is
developed by Huawei for packet transport.
1.2 Network Application
The OptiX PTN 3900 is applied at the convergence layer and the backbone layer of a
metropolitan transport network.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential 1-1

1 Overview Product Description
1.1 Equipment Introduction

The OptiX PTN 3900 is new generation metropolitan optical transport platform, which is
developed by Huawei for packet transport.
As emerging data services are widely applied, operators require increasing bandwidth of the
transport network and demand more flexibility of scheduling bandwidth. As a circuit-switching
network, the traditional SDH-based multiservice transport network is inapplicable to the data
services that feature burst and flexibility. In addition, the traditional connectionless IP network
should not be used as a telecommunication carrier network because it cannot strictly ensure the
quality and performance of important services.
With the pseudo wire emulation edge-to-edge (PWE3) technology, the multi-protocol label
switch (MPLS) technology, as well as ideal operation, administration and maintenance (OAM)
and protection switching mechanism, the OptiX PTN 3900 is able to provide services of carrier-
class quality in a packet transport network and SDH transport network.
Figure 1-1 shows the OptiX PTN 3900 equipment.
Figure 1-1 Appearance of the OptiX PTN 3900
1-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Product Description 1 Overview
1.2 Network Application

The OptiX PTN 3900 is applied at the convergence layer and the backbone layer of a
metropolitan transport network.
The OptiX PTN 3900 is mainly used in the convergence layer and the backbone layer of a
metropolitan transport network. It transports packet services in the network, and converges the
services to an IP/MPLS backbone network.
The OptiX PTN 3900 also supports the coarse wavelength division multiplexing (CWDM)
networking and realizes the local wavelength grooming.
In later versions, the OptiX PTN 3900 supports the SDH boards of the OptiX OSN
1500/2500/3500/7500 product series and supports the dense wavelength division multiplexing
(DWDM) boards of the OptiX OSN 3800/6800 product series, to realize the networking with a
WDM/SDH backbone network. This facilitates the smooth evolution of the metropolitan
transport network from a time division multiplex (TDM) switching network to a packet switching
network.
Figure 1-2 shows the network application of the OptiX PTN 3900.
Figure 1-2 Network application of the OptiX PTN 3900

Backbone
layer WDM/SDH backbone IP/MPLS backbone
STM-N GE/10GE
Metro WDM
SDH convergence PTN convergence

Convergence
layer
P
T
N
Access
layer
Packet access L2 access
SDH access
DSLAM Enterprise
BTS NodeB
private line
OptiX PTN 3900

Switch
OptiX PTN 1900 SDH network element

1 Overview Product Description

Product Description 2 Functions and Features
2 Functions and Features
About This Chapter
The OptiX PTN 3900 supports various types of services, and provides abundant functions and
features to ensure service transport quality and efficiency.
2.1 Service Types

The OptiX PTN 3900 supports L3VPN service, Ethernet services, asynchronous transfer mode
(ATM) services, and circuit emulation services (CES).
2.2 Service Processing Capability
The service processing capability of the OptiX PTN 3900 is categorized into the switching
capability and the service access capability.
2.3 Interface Types
The external interfaces of the OptiX PTN 3900 are categorized into service interfaces, and
administration and auxiliary interfaces.
2.4 Networking Capability
The OptiX PTN 3900 supports various networking modes to apply to different scenarios.
2.5 Protection Capability
The OptiX PTN 3900 provides equipment level protection and network level protection.
2.6 QoS
The OptiX PTN 3900 provides hierarchical end-to-end quality of service (QoS) management,
and thus provides high quality transports that are differentiated by service.
2.7 OAM Features
The OptiX PTN 3900 supports Ethernet operations, administration and maintenance (OAM) and
MPLS OAM, to realize fast defect detection and to trigger protection switching. In this way, the
carrier-class quality of service is guaranteed in the packet switching network.
2.8 NSF
With the non-stop forwarding (NSF) function, data forwarding can be properly performed even
when the control plane of the equipment is faulty (for example, the CPU is restarted). In this
case, key services on the network are protected.
2.9 Clock

2 Functions and Features Product Description
The OptiX PTN 3900 supports the physical layer clock synchronization mechanism, the external
clock input/output, and the equipment internal clock. In addition, the OptiX PTN 3900 also
supports the IEEE 1588 V2 clock synchronization
2.10 DCN Scheme
The data communication network (DCN) is an integral part of network management, and is used
to transmit the network management information. The OptiX PTN 3900 supports the inband
DCN to ensure the intercommunication of network management information.

2.1 Service Types

The OptiX PTN 3900 supports L3VPN service, Ethernet services, asynchronous transfer mode
(ATM) services, and circuit emulation services (CES).
The OptiX PTN 3900 processes the following Ethernet services:
l E-Line services
l E-LAN services
l E-Aggr services
The OptiX PTN 3900 processes the following ATM services:

l ATM emulation service
l IMA emulation service
The OptiX PTN 3900 processes the E1 CES service.

The OptiX PTN 3900 processes the L3VPN service.
2.2 Service Processing Capability

The service processing capability of the OptiX PTN 3900 is categorized into the switching
capability and the service access capability.
2.2.1 Switching Capability
The OptiX PTN 3900 supports the packet-based service switching.
2.2.2 Maximum Access Capability
The OptiX PTN 3900 is capable of accessing services through various interfaces.
2.2.1 Switching Capability

The OptiX PTN 3900 supports the packet-based service switching.
Table 2-1 lists the switching capability of the OptiX PTN 3900.
Table 2-1 Switching capability of the OptiX PTN 3900

Product Switching Capability Line Rate I/O Capability
OptiX PTN 3900 320 G 160 G
Note: The OptiX PTN 3900 provides unidirectional switching capability of 320 Gbit/s in the
ingress and egress directions. That is, the OptiX PTN 3900 provides bidirectional switching
capability of 640 Gbit/s.
2.2.2 Maximum Access Capability

The OptiX PTN 3900 is capable of accessing services through various interfaces.
Table 2-2 lists the access capabilities of different interfaces of the OptiX PTN 3900.

Table 2-2 OptiX PTN 3900 interface quantity

Interface Access Processing Entire Accessed by Interface
Type Capability Capability Equipment Board or Processing
(Board (Board Access Board
Name) Name) Capability
E1 (including 32 (D75/D12) 32 (MD1 and 504 Accessed by interface

IMA E1, ML- MP1) board
PPP E1, and 63 (MQ1 and
TDM E1) MP1)
Packet over 2 (POD41) 8 (EG16) 32 Accessed by interface

SDH/SONET board
(POS) STM-1/4
FE electrical 12 (ETFC) 47 (EG16) 188 Accessed by interface

interface board
FE optical 8 (EFF8) 32 (EG16) 128 Accessed by interface

interface board
GE 16 (EG16) 16 (EFG2) + 8 160 The GE signals can be

2 (EFG2) (EG16) accessed by processing
board (EG16) as well as
interface board (EFG2)
10GE 2 (EX2) 2 (EX2) 16 Accessed by processing

board
Channelized 2 (CD1) 2 (CD1 and 32 Accessed by processing

STM-1 MP1) board
ATM STM-1 2 (AD1) 2 (AD1 and 32 (AD1, The ATM STM-1 signals
2 (ASD1) MP1) ASD1) can be accessed by
2 (ASD1 and 128 (AFO1) processing board (AD1,
8 (AFO1) ASD1) as well as
MP1)
interface board (AFO1)
32 (EG16)
2.3 Interface Types

The external interfaces of the OptiX PTN 3900 are categorized into service interfaces, and
administration and auxiliary interfaces.
2.3.1 Service Interfaces

The OptiX PTN 3900 provides multiple types of interfaces.
2.3.2 Administration and Auxiliary Interfaces
The administration and auxiliary interfaces include the administration interfaces, external clock
interfaces, and alarm interfaces.

2.3.1 Service Interfaces

The OptiX PTN 3900 provides multiple types of interfaces.
Table 2-3 lists the service interfaces supported by the OptiX PTN 3900.
Table 2-3 Service interfaces of the OptiX PTN 3900

Interface Type Description Remark
FE interface Electrical interfaces: 10/100BASE-TX Applicable to UNI

Optical interfaces: 100BASE-FX and NNI
GE interface 1000BASE-SX, 1000BASE-LX, 1000BASE- Applicable to UNI

VX, 1000BASE-ZX, 1000BASE-CWDM and NNI
10GE interface 10GBASE-SR, 10GBASE-LR, 10GBASE- Applicable to UNI

LW, 10GBASE-ER, 10GBASE-EW, and NNI
10GBASE-ZR, 10GBASE-ZW
POS interface STM-1 optical interfaces: S-1.1, L-1.1, L-1.2 Applicable to UNI
STM-4 optical interfaces: S-4.1, L-4.1, L-4.2, and NNI
Ve-4.2
ATM STM-1 interface S-1.1, L-1.1, L-1.2 Applicable to UNI

and NNI
Channelized STM-1 S-1.1, L-1.1, L-1.2 Applicable to UNI

interface and NNI
E1 interface 75-ohm/120-ohm E1 electrical interfaces: Applicable to UNI

DB44 connectors and NNI
CWDM interface CMR2: 1271nm - 1611nm -

CMR4: 1291nm - 1611nm
NOTE
UNI Connects with BTS or NodeB.

NNI Connects with PSN network.
2.3.2 Administration and Auxiliary Interfaces

The administration and auxiliary interfaces include the administration interfaces, external clock
interfaces, and alarm interfaces.
Table 2-4 lists the administration and auxiliary interfaces of the OptiX PTN 3900.

Table 2-4 Administration and auxiliary interfaces of the OptiX PTN 3900
Interface Type Description Quantity
Administration Ethernet NM interface (ETH) 1 (RJ-45)

interface
Cascading network interface (EXT) 1 (RJ-45)
Administration serial interface (F&f) 1 (RJ-45)
Auxiliary interface Cabinet indicator interface (four-channel) 1 (RJ-45)
Cabinet indicator cascading interface (four- 1 (RJ-45)

channel)
Alarm input interface (eight-channel) 2 (RJ-45)
Common interface for alarm output and 1 (RJ-45)

cascading (two-channel output and two-
channel cascading)
External clock interface Common interface for 120-ohm clock input 2 x RJ-45
and output (2048 kbit/s or 2048 kHz), or 2 x SMB
Common interface for 75-ohm clock input
and output (2048 kbit/s or 2048 kHz)
External time interface DCLS time input interface

DCLS time output interface
1PPS + time information input interface, or
1PPS + time information output interface
NOTE
The external clock and external time share one interface, which can be used as either clock or time, but
not both, at the same time.
When the TN81XCS board is applied, the equipment provides only the external clock interface. That is,
the external time interface is not available.
2.4 Networking Capability

The OptiX PTN 3900 supports various networking modes to apply to different scenarios.
Networking Interface
The OptiX PTN 3900 supports the following interfaces for networking.
l 10GE
l GE
l FE
l POS STM-4
l POS STM-1
l ML-PPP

NOTE
l It is recommended that the ML-PPP should be used to form the chain network.
l The FE electrical interface is not recommended to be used as networking interface.
Typical Networking for Mobile Communication

Figure 2-1 and Figure 2-2 show the typical networking modes of the OptiX PTN equipment
for mobile communication. Figure 2-3 shows the networking application of the OptiX PTN
equipment in the offload solution.
Figure 2-1 Networking mode I for mobile communication
ML-PPP
POS
POS
POS
ML-PPP
OptiX PTN 3900 BTS NodeB
OptiX PTN 1900 BSC RNC

Figure 2-2 Networking mode II for mobile communication
GE
GE
GE
GE
GE
OptiX PTN 3900 BTS NodeB
OptiX PTN 1900 BSC RNC
Figure 2-3 Networking mode for offload solution
HSDPA Wholesale ADSL network

flow
R99 flow
Leased line
NodeB OptiX PTN 1900 RNC
ADSL modem OptiX PTN 3900

For details on the networking application of the OptiX PTN equipment for mobile
communication, see 9.1 Application of the Equipment for Mobile Services. For details on the
networking application of the OptiX PTN equipment in the offload solution, see9.3 Offload
Solution.
Typical Networking for Ethernet Services

Figure 2-4 shows the typical networking mode of the PTN equipment for E-Line services.
Figure 2-4 Networking Mode for E-Line Services
FE
GE
E-Line
Protection Path
OptiX PTN 3900
OptiX PTN 1900
CE
Figure 2-5 shows the typical networking mode of the PTN equipment for E-LAN services.
Figure 2-5 Networking Mode for E-LAN Services
FE
GE
E-LAN
OptiX PTN 3900
OptiX PTN 1900
CE
Figure 2-6 shows the typical networking mode of the PTN equipment for E-Aggr services.

Figure 2-6 Networking Mode for E-Aggr Services
FE
OptiX PTN 3900 NodeB
GE
OptiX PTN 1900 RNC Convergence link
For details on the networking application of the OptiX PTN equipment for Ethernet services,
see 9.2 Application of the OptiX PTN 3900 for the L2VPN Service.
Typical Networking for L3VPN

Figure 2-7 shows the typical networking mode of the L3VPN.

Figure 2-7 Networking Mode for L3VPN
CE-A CE-C VPN 2

VPN 1
Backbone network
P P
PE
PE
PE
VPN 2 P P
VPN 1
CE-D
CE-B
OptiX PTN 3900/OptiX PTN 1900
CE
For details on the networking application of the OptiX PTN equipment for L3VPN, see 4.5
L3VPN Services.
2.5 Protection Capability

The OptiX PTN 3900 provides various equipment level protection schemes, as listed in Table
2-5.
Table 2-5 Equipment level protection
Protection Object Protection Scheme Revertive Mode
Cross-connect and timing board 1+1 hot backup Non-revertive
System control, communication and 1+1 hot backup Non-revertive

auxiliary processing board
Sub-board and MP1 board 1:N (1 - 4) TPS Revertive
Power interface unit 1+1 hot backup -

The OptiX PTN 3900 provides various network level protection schemes, as listed in Table
2-6.
Table 2-6 Network level protection
Protected Object Protection Scheme
MPLS Tunnel 1+1 protection
1:1 protection
Reroute protection
Fast reroute (FRR) protection
Ethernet link Link aggregation group (LAG) protection
Multiple spanning tree protocol (MSTP) protection
POS STM-1/ 1+1 linear MSP

POS STM-4
1:1 linear MSP
Channelized STM-1 1+1 linear MSP
1:1 linear MSP
ATM STM-1 1+1 linear MSP
1:1 linear MSP
1:N (2≤N≤7) linear MSP (AFO1)
IMA group IMA member protection
ML-PPP group ML-PPP member protection
2.6 QoS
The OptiX PTN 3900 provides hierarchical end-to-end quality of service (QoS) management,
and thus provides high quality transports that are differentiated by service.
The OptiX PTN 3900 provides complete QoS grooming mechanisms, which include the
following:
l DiffServ mode based on flow classification. With the DiffServ mode, the OptiX PTN 3900
helps operators provide services of different quality classes for users. Hence, operators can
provide an integrated network that can carry data, voice and video services.
l QoS for end-to-end services
– Hierarchical QoS (HQoS) mechanism at the access side. The HQoS mechanism helps
control the overall bandwidth for a single service type, a single service access point,
multiple service access points, a single service or multiple services. See Table 5-3 for
the action points of the HQoS.
– Traffic Engineering (TE) mechanism at the network side. The TE mechanism helps
balance the network traffic to ensure the service quality.

With the complete QoS mechanisms, the OptiX PTN 3900 ensures that the specifications of
delay, delay variation, and bandwidth are satisfied for different services, and thus guarantees
the provision of carrier-class services.
2.7 OAM Features

The OptiX PTN 3900 supports Ethernet operations, administration and maintenance (OAM) and
MPLS OAM, to realize fast defect detection and to trigger protection switching. In this way, the
carrier-class quality of service is guaranteed in the packet switching network.
Figure 2-8 shows the OAM mechanism of the OptiX PTN 3900.
Figure 2-8 OAM mechanism of the OptiX PTN 3900
CE CE
FE FE
PTN PTN
Router Router
IEEE 802.1ag Service Layer (UNI to UNI)
ITU Y.1731 Connectivity Layer

Access Link Access Link
IEEE 802.3ah PW
ITU Y.1711 LSP
At the network level, the OptiX PTN 3900 supports MPLS OAM and Ethernet OAM.
l The OptiX PTN 3900 supports the following MPLS OAM functions.
– The equipment provides hardware support, to transmit and receive connectivity
verification (CV) messages, fast failure detection (FFD) messages, backward defect
indicator (BDI) messages, and forward defect indicator (FDI) messages, and to perform
timeout judgment for these messages. In compliance with ITU-T Y.1710 and ITU-T Y.
1711, the fast continuity check and failure indication are realized. As supported by the
equipment, the minimum period for transmitting the FFD packets is 3.3 ms.
– The equipment supports the MPLS Tunnel Ping and TraceRoute commands, and also
the virtual circuit connectivity verification (VCCV) command for the PW. These
commands can be used to detect and locate the faults.
– The equipment supports performance monitoring for MPLS Tunnel. In compliance with
ITU-T Y.1710, the equipment provides hardware support for the monitoring of packet
loss ratio, packet delay and packet delay variation.
l The OptiX PTN 3900 supports the following Ethernet OAM functions that are compliant
with IEEE 802.1ag and ITU-T Y.1731.
– The equipment provides hardware support for the Ethernet continuity check (ETH-CC)
and the performance monitoring. As supported by the equipment, the minimum period
for transmitting the OAM frames is 3.3 ms.

– The control plane of the equipment supports the Ethernet loopback (ETH-LB) and
Ethernet link trace (ETH-LT) operations.
– The equipment supports performance monitoring for the E-Line service. In compliance
with ITU-T Y.1731, the equipment provides hardware support for the monitoring of
packet loss ratio, packet delay, and packet delay variation.
At the link layer, the OptiX PTN 3900 supports the following OAM mechanisms.
l The equipment supports Ethernet OAM that is compliant with IEEE 802.3ah. Each Ethernet
port supports link discovery, link state monitoring, remote fault indication, and remote
loopback.
l The equipment supports ATM OAM, including the fault management in the F4 OAM and
F5 OAM.
2.8 NSF
With the non-stop forwarding (NSF) function, data forwarding can be properly performed even
when the control plane of the equipment is faulty (for example, the CPU is restarted). In this
case, key services on the network are protected.
The OptiX PTN 3900 supports the protocol level graceful restart (GR) technology (for example,
the LDP GR). In the case of a fault, the neighbor nodes do not delete the route information. In
this way, services are still forwarded and the network route oscillation is avoided.
The OptiX PTN 3900 supports the NSF function in the following cases:
l The warm reset of the processing board and the XCS board.
l The cold reset of the XCS board (the XCS board should be configured with 1+1 protection).
l The reset of the SCA board (the SCA board should be configured with 1+1 protection).
2.9 Clock
The OptiX PTN 3900 supports the physical layer clock synchronization mechanism, the external
clock input/output, and the equipment internal clock. In addition, the OptiX PTN 3900 also
supports the IEEE 1588 V2 clock synchronization
Physical Layer Clock Synchronization

The clock system of the OptiX PTN 3900 supports extracting the clock information from the
following transmission links:
l Extraction of clock signals from POS STM-1/STM-4 interfaces

l Extraction of clock signals from channelized STM-1 interfaces
l Extraction of clock signals from ATM STM-1 interfaces
l Extraction of clock signals from synchronous Ethernet interfaces
l Extraction of clock signals from E1 interfaces
The OptiX PTN 3900 supports input/output of two 75-ohm or two 120-ohm external clock
sources, which are of 1+1 protection.

The OptiX PTN 3900 supports three clock working modes, that is, the locked, hold-over, and
free-run modes. The OptiX PTN 3900 also supports the processing and transfer of
synchronization status messages (SSM).
The synchronous Ethernet is a technology used to synchronize the clock at the Ethernet physical
layer. Clock signals are extracted directly from the serial bit flow on the Ethernet link. These
clock signals are then used for data transmission. In this way, the clock signals are transferred.
IEEE 1588 V2
IEEE 1588 V2 is a time synchronization protocol that provides the nanosecond accuracy to meet
the requirements of 3G base stations. OptiX PTN 3900 supports the following features of IEEE
1588 V2:
l The equipment can use the IEEE 1588 V2 protocol to achieve the clock synchronization
and time synchronization.
l The equipment supports the boundary clock (BC) mode, ordinary clock (OC) mode, and
transparent clock (TC)/(TC+OC) mode. The TC mode includes the end-to-end (E2E) TC
mode and (P2P) TC mode.
l The equipment supports the BMC algorithm to select clock source.
2.10 DCN Scheme

The data communication network (DCN) is an integral part of network management, and is used
to transmit the network management information. The OptiX PTN 3900 supports the inband
DCN to ensure the intercommunication of network management information.
The OptiX PTN 3900 adopts the inband DCN scheme. In this scheme, the setup of dedicated
DCN channels is not required, and hence the network construction cost is greatly lowered.
The OptiX PTN 3900 supports a maximum of 128 DCN channels. The OptiX PTN 3900 supports
the inband DCN through the following interfaces.
l 10GE
l GE
l FE
l POS STM-4/STM-1
l E1
NOTE
l The FE electrical interfaces are not recommended to be used as networking interfaces.

Product Description 3 System Architecture
3 System Architecture
About This Chapter
This chapter describes the system architecture of the OptiX PTN 3900 in terms of functional
module, hardware structure and software architecture.
3.1 Functional Modules

The functional modules of the OptiX PTN 3900 include the service processing module,
management and control module, heat dissipation module and power supply module.
3.2 Hardware Structure
This section describes the cabinet that can house the OptiX PTN 3900 subrack, subrack structure,
and boards in the subrack.
3.3 Software Architecture
This section describes the architecture of the NE software and board software.

3 System Architecture Product Description
3.1 Functional Modules

The functional modules of the OptiX PTN 3900 include the service processing module,
management and control module, heat dissipation module and power supply module.
Figure 3-1 shows the functional modules of the OptiX PTN 3900.
Figure 3-1 Functional modules of the OptiX PTN 3900

External Clock/Time
FE/GE/10GE POS
Clock module
ATM STM-1
GE/10GE
客户接口
E1
UNI NNI
Switching plane
interface interface ML-PPP
Channelized
STM-1 Service Service
sub-board sub-board
Service processing module
Bus
NM interface
Alarm I/O interface
Heat
Power supply Management and
dissipation Alarm cascade interface
module control module
module CF card
F&f
Service Processing Module

The service processing module includes the UNI interfaces, NNI interfaces, clock module and
switching module.
The equipment supports several types of services from the UNI interfaces and NNI interfaces.
l UNI interfaces: E1, ATM STM-1, FE/GE/10GE and channelized STM-1
l NNI interfaces: POS STM-1/STM-4, GE/10GE, ML-PPP
The service sub-board and corresponding interface board are jointly used to access channelized
STM-1, ATM STM-1 and E1 services. The switching plane processes the service signals
accessed into the equipment.
The clock module can receive either the network clock from the NNI interfaces or the external
input clock from the external clock interfaces. The clock module selects the clock source of

better quality and locks phase of the clock source for synchronization. Finally, the clock module
provides the system clock for each module and supports the output of clock signals through the
external clock interfaces.
The clock module processes and transfers the synchronization status messages (SSMs).
Management and Control Module

The management and control module uses the bus inside the system for inter-board
communication and communication between the system control board and other boards. This
module can also transfer the manufacturing information of the management board.
This module also supports functions such as inband DCN management and non-stop forwarding.
In addition, this module provides complete management interfaces and auxiliary interfaces,
including the network management interface, alarm input/output interface, alarm concatenation
interface, F&f interface and CF card interface.
Heat Dissipation Module

The heat dissipation module dissipates the heat generated by the equipment with flowing air.
The heat dissipation module consists of the fan board, fan frame and fans. The fans support the
intelligent adjustment of the rotating speed according to the system temperature.
Power Supply Module

The power supply module supplies power to the boards and fans of the equipment and monitors
the power supply.
3.2 Hardware Structure

This section describes the cabinet that can house the OptiX PTN 3900 subrack, subrack structure,
and boards in the subrack.
3.2.1 Overview
The OptiX PTN 3900 equipment consists of the subrack and boards.
3.2.2 Cabinet
The OptiX PTN 3900 can be installed in a 300 mm deep ETSI cabinet (N63E cabinet or T63
cabinet).
3.2.3 Subrack
The OptiX PTN 3900 subrack is of a dual-layer structure. The subrack consists of processing
board area, interface board area, switching fabric area, system control board area, power supply
board area, fan area and fiber routing trough.
3.2.4 Boards
Boards of the OptiX PTN 3900 include the processing board, WDM board, service sub-board,
interface board, cross-connect and timing board, system control, communication and auxiliary
processing board, fan board and power supply board.
3.2.5 Valid Slots for Boards
On the OptiX PTN 3900 subrack, 40 slots are available, covering the 16 slots for processing
boards, 16 slots for interface boards, two slots for switching boards, two slots for system control
boards, two slots for PIU boards, and two slots for FAN boards.

3.2.1 Overview
The OptiX PTN 3900 equipment consists of the subrack and boards.
Figure 3-2 shows the subrack installed in the cabinet.
Figure 3-2 Hardware structure of the OptiX PTN 3900
Cabinet
Power distribution
unit
Cable distribution
plate
Subrack
3.2.2 Cabinet
The OptiX PTN 3900 can be installed in a 300 mm deep ETSI cabinet (N63E cabinet or T63
cabinet).
Figure 3-3 shows the cabinets used to house the OptiX PTN 3900 subrack.

Figure 3-3 Appearance of the cabinets used to house the OptiX PTN 3900
T63 cabinet N63E cabinet

3.2.3 Subrack
The OptiX PTN 3900 subrack is of a dual-layer structure. The subrack consists of processing
board area, interface board area, switching fabric area, system control board area, power supply
board area, fan area and fiber routing trough.
Subrack Structure
Figure 3-4 shows the structure of the OptiX PTN 3900 subrack.
Figure 3-4 Structure of the OptiX PTN 3900 subrack
Interface board area
Interface board
area System control
board area
Power supply
board area
Fan area
(without air filter)
Processing board
area
Processing
board area Switching fabric
area
Fiber routing trough
Fan area
Air filter
Functions of these areas of the subrack are as follows.
l Processing board area, which is used to house the processing boards and service sub-
boards.
l Interface board area, which is used to house the interface boards.
l System control board area, which is used to house the system control, communication and
auxiliary processing board (SCA).
l Switching fabric area, which is used to house the cross-connect and timing board (XCS).
l Power supply board area, which is used to house the power supply boards.

l Fan area, which is used to house the fan tray assembly and air filter.
l Fiber routing trough, which is used to route fibers and external clock cables.
Slot Allocation
The OptiX PTN 3900 subrack consists of the upper layer and lower layers. The upper layer
contains 20 slots and the lower layer contains 18 slots. In addition, there are two slots for FAN
boards. In total, 40 slots are available on the OptiX PTN 3900 subrack.
Figure 3-5 shows the position of each slot in the OptiX PTN 3900 subrack.
Figure 3-5 Slot layout of the OptiX PTN 3900
S S S S S S S S P P S S S S S S S S S S
L L L L L L L L I I C C L L L L L L L L
O O O O O O O O U U A A O O O O O O O O
T T T T T T T T T T T T T T T T
1 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3
9 0 1 2 3 4 5 6 27 28 29 30 1 2 3 4 5 6 7 8
Fan SLOT 39
S S S S S S S S X X S S S S S S S S
L L L L L L L L C C L L L L L L L L
O O O O O O O O S S O O O O O O O O
1 2 3 4 5 6 7 8 9 10 1 1 1 1 1 1 1 1
1 2 3 4 5 6 7 8
Fiber routing trough Fiber routing trough
Fan SLOT 40
Air filter
Mapping Relation Between Processing Boards and Interface Boards

Table 3-1 lists the mapping relation between slots for processing boards and interface boards.

Table 3-1 Mapping relation between slots for processing boards and interface boards of the
OptiX PTN 3900
Slots for Processing Boards Slots for Interface Boards
Slot 1 Slots 19-20
Slot 2 Slots 21-22
Slot 3 Slots 23-24
Slot 4 Slots 25-26
Slots 5-8 -
Slots 11-14 -
Slot 15 Slots 31-32
Slot 16 Slots 33-34
Slot 17 Slots 35-36
Slot 18 Slots 37-38
Table 3-2 lists the mapping relation between processing boards and interface boards.
Table 3-2 Mapping relation between processing boards and interface boards of the OptiX PTN
3900
Processing Board Service Sub-Board Interface Board
MP1 MD1, MQ1 D75, D12
AD1, ASD1, CD1 -
EG16 - ETFC, EFG2, POD41,

EFF8, AFO1
EX2 - -
Slot Processing Capacity

Figure 3-6 lists the processing capacity of each slot in the OptiX PTN 3900 subrack.

Figure 3-6 Slot processing capacity of the OptiX PTN 3900
S S S S S S S S P P S S S S S S S S S S
L L L L L L L L I I C C L L L L L L L L
O O O O O O O O U U A A O O O O O O O O
1 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3
9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8
Fan SLOT 39
S S S S S S S S S S S S S S S S
L L L L L L L L X X L L L L L L L L
O O O O O O O O C C O O O O O O O O
T T T T T T T T S S T T T T T T T T
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7 8
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
G G G G G G G G G G G G G G G G
b b b b b b b b b b b b b b b b
i i i i i i i i i i i i i i i i
t t t t t t t t t t t t t t t t
/ / / / / / / / / / / / / / / /
s s s s s s s s s s s s s s s s
Fiber routing trough Fiber routing trough

Fan SLOT 40
Air filter
3.2.4 Boards
Boards of the OptiX PTN 3900 include the processing board, WDM board, service sub-board,
interface board, cross-connect and timing board, system control, communication and auxiliary
processing board, fan board and power supply board.
Table 3-3 lists the boards of the OptiX PTN 3900 and their functions.

Table 3-3 Boards and their key functions

Board Type Board Name Key Function
Processing board EX2, EG16, MP1 l Accesses and processes

10GE, GE, channelized
Service sub-board MD1, MQ1, CD1, AD1, STM-1 and ATM STM-1
ASD1 signals.
l Processes E1 signals.
WDM board CMR2, CMR4 Adds or drops coarse

wavelength division
multiplexing (CWDM)
signals.
Interface board ETFC, EFG2, POD41, D12, Accesses ATM STM-1, FE,
D75, EFF8, AFO1 GE, POS STM-1/STM-4 and
E1 signals.
Cross-connect and timing XCS l Grooms services .

board l Provides the clock and
time .
System control, SCA Provides an interface to

communication and auxiliary connect the system to the
processing board T2000.
Performs the system control
function.
Fan board FAN Dissipates heat for boards.
Power supply board PIU Accesses the external power

supply.
NOTE
The SCA has two versions, that is, TN81SCA and TN82SCA.
The XCS has two versions, that is, TN81XCS and TN82XCS.
The EG16 has two versions, that is, TN81EG16 and TN82EG16.
3.2.5 Valid Slots for Boards

On the OptiX PTN 3900 subrack, 40 slots are available, covering the 16 slots for processing
boards, 16 slots for interface boards, two slots for switching boards, two slots for system control
boards, two slots for PIU boards, and two slots for FAN boards.
Table 3-4 lists the valid slots for boards in the OptiX PTN 3900 subrack.

Table 3-4 Valid slots for boards in the OptiX PTN 3900 subrack
Board Full Name Valid Slot Remarks
SCA System control, Slots 29 - 30 -

communication and
auxiliary processing unit
XCS Cross-connect and Slots 9 - 10 -

synchronous timing unit
PIU Power interface unit Slots 27 - 28 -
FAN Fan board Slots 39 - 40 -
EX2 2-port 10 Gigabit Ethernet Slots 1, 3, 5, 7, 11, One EX2 occupies two
Switching Processing Board 13, 15, and 17 slots.
EG16 16-port GE Ethernet Slots 1, 3, 5, 7, 11, One EG16 occupies two

processing board 13, 15, and 17 slots.
MP1 Multi-protocol (TDM/IMA/ Slots 1 - 8 and 11 - -

ATM/ML-PPP) multi- 18
interface (E1/STM-1)
mother processing board
MD1 32 x E1 service sub-board Slots 1 - 5 and 14 - The MD1 should be jointly

18 used with the MP1 and
interface board.
MQ1 63 x E1 service sub-board Slots 1 - 5 and 14 - The MQ1 should be jointly

18 used with the MP1 and
interface board.
CD1 2-port channelized STM-1 Slots 1 - 8 and 11 - The CD1 should be jointly
sub-board 18 used with the MP1.
AD1 2-port ATM STM-1 sub- Slots 1 - 8 and 11-18 The AD1 should be jointly
board used with the MP1.
ASD1 2-port ATM STM-1 sub- Slots 1 - 8 and 11 - The ASD1 should be jointly
board with SAR function 18 used with the MP1.
AFO1 8 x ATM STM-1 interface Slots 19 - 26 and 31 The AFO1 should be jointly
board - 38 used with the EG16.
ETFC 12 x FE electrical interface Slots 19 - 26 and 31 The ETFC should be jointly

EFF8 8 x FE optical interface board Slots 19 - 26 and 31 The EFF8 should be jointly
- 38 used with the EG16.
EFG2 2 x GE optical interface Slots 19 - 26 and 31 The EFG2 should be jointly

POD41 2 x 622/155 Mbit/s POS Slots 19 - 26 and 31 The POD41 should be

interface board - 38 jointly used with the EG16.

Board Full Name Valid Slot Remarks
D12 32 x E1 120-ohm electrical Slots 19 - 26 and 31 The D12 should be jointly

interface board - 38 used with the MD1 and
MP1, or MQ1 and MP1.
D75 32 x E1 75-ohm electrical Slots 19 - 26 and 31 The D75 should be jointly

interface board - 38 used with the MD1 and
MP1, or MQ1 and MP1.
CMR2 2-channel optical add/drop Slots 1 - 8 and 11 - -

multiplexing board 18
CMR4 4-channel optical add/drop Slots 1 - 8 and 11 - -

multiplexing board 18
3.3 Software Architecture

This section describes the architecture of the NE software and board software.
3.3.1 Overview
The software for the OptiX PTN 3900 consists of the management plane, control plane and data/
forwarding plane.
3.3.2 NE Software
The NE software manages, monitors and controls the running status of boards in the NE. The
NE software also functions as the service unit for the communication between the T2000 and
boards. In this way, the T2000 can control and manage the NE. In addition, the NE software
manages the software loading, software package loading and fix of the system control board.
3.3.3 Board Software
The board software is responsible for Layer 2 switching, the MPLS packet processing and the
QoS. The board software monitors and reports the alarms and performance events of each board
to the NE software.
3.3.1 Overview
The software for the OptiX PTN 3900 consists of the management plane, control plane and data/
forwarding plane.
Figure 3-7 shows the logical block diagram for the software architecture of the OptiX PTN
3900.

Figure 3-7 Logical block diagram for the software architecture of the OptiX PTN 3900
System control, communication and

auxiliary processing board
Management
plane System
management unit
Control
plane System control
unit
Processing Processing
board board
Forwarding Forwarding
unit unit
Data
Switching
plane unit
Forwarding 交换网板 Forwarding
unit unit
General cross-
Processing connect and timing Processing
board board board
Management Plane
The management plane performs functions such as performance management, fault
management, configuration management, software management, Layer 2 protocol control and
security management. The NE software and board software both belong to the management
plane. The board software is used to manage the data/forwarding plane.
Control Plane
The control plane consists of a group of communication entities and controls the calling and
connection. The control plane uses signaling to set up, release, monitor and maintain
connections, and to recover connections in the case of a fault. Both the NE software and board
software are involved in the functions of the control plane.
Data Plane
The data plane receives and forwards service data according to the forwarding message generated
by the control plane. This plane also monitors the control packets of services and reports these
packets to the control plane and the management plane.The processing boards and XCS are
responsible for the provision of the data plane.

3.3.2 NE Software
The NE software manages, monitors and controls the running status of boards in the NE. The
NE software also functions as the service unit for the communication between the T2000 and
boards. In this way, the T2000 can control and manage the NE. In addition, the NE software
manages the software loading, software package loading and fix of the system control board.
On the element management layer of the telecommunications management network, the NE

software has NE functions, partial coordination functions and operating system functions on the
network element layer. The NE software uses the data communication function for the
communication between the NE and other parts, including equipment, the T2000 and other NEs.
Figure 3-8 shows the architecture of the NE software for the OptiX PTN 3900.
Figure 3-8 Architecture of the NE software for the OptiX PTN 3900
Software GCP Protocol
Platform
Interface Configuration Module IGMP
management
snooping
QoS Layer 2
Alarm and
performance MSTP
management MPLS
DCN Equipment management LACP
Basic frame
Hardware driver
Software Platform
The software platform consists of the interface management module, alarm and performance
management module, and DCN module.
Interface management module: This module divides and converts different forms of commands
from different types of terminals to the internal commands of the same form.
Alarm and performance management module: This module supports the reporting and query of
current alarms, storage and query of history alarms, reporting of performance events and
management of the system logs.
DCN module: This module processes the DCN packets, and provides the communication
between the local NE and other parts, including the T2000 and other NEs.
GCP
The GCP provides a uniform static or dynamic distribution mechanism for MPLS labels. The
GCP also provides routing protocols and trail computation algorithm related to the creation of
dynamic service. In addition, the GCP provides the LMP protocol related to the neighbor auto-
discovery function of the transport plane.

Configuration Module
The configuration module consists of the equipment management sub-module and QoS sub-
module. The functions of the configuration module as follows.
l Responsible for the management configuration of the entire NE, including service
management, equipment management, resource management and protocol configuration
agent.
l Responsible for the setting and querying of the attributes of alarms and performance of the
managed objects.
l Responsible for querying and reporting of the performance data.
l Responsible for inter-board alarm suppression and query of alarms of specified objects.
l Responsible for storing configuration data.
l Responsible for providing Layer 2 switching, processing MPLS and IP packets and the
QoS function.
Protocol
IGMP Snooping protocol, which is a Layer 2 multicast protocol and provides the Layer 2
multicast function.
MSTP protocol, which is a spanning tree protocol used for loop release, link backup and VLAN-
based link load balance.
Link aggregation control protocol (LACP) protocol, which is used for linear bandwidth
increasing, link backup and load balance.
Basic Frame
The basic frame provides the basic platform kernel and system support. For example, the basic
frame realizes the board management, distributed message management and log management.
3.3.3 Board Software

The board software is responsible for Layer 2 switching, the MPLS packet processing and the
QoS. The board software monitors and reports the alarms and performance events of each board
to the NE software.
Figure 3-9 shows the architecture of the board software for the OptiX PTN 3900.
Figure 3-9 Architecture of the board software for the OptiX PTN 3900
Forwarding plane Alarm/log Performance Software
management
LIB Software
Alarm report/ 15-m/24-h
indication performance package
Alarm detection loading
computation
Alarm anti-jitter/
Statistics of inter-board Patch
RMON
performance units suppression management
Basic frame
Hardware driver

l The forwarding plane monitors alarms and makes performance statistics.

l The alarm/log module reports and suppresses alarms.
l The performance module makes performance statistics and provides RMON functions.

Product Description 4 Services
4 Services
About This Chapter
This chapter describes the services of the equipment.
4.1 Overview
The OptiX PTN 3900 supports the L2VPN and L3VPN service, Ethernet service, ATM service
and CES service. Based on the service model of the OptiX PTN 3900, this section describes the
processing of various services in the OptiX PTN 3900.
4.2 Ethernet Service
The OptiX PTN 3900 supports various Ethernet services and provides ideal L2VPN solutions.
4.3 ATM Service
In the transport network with the packet switching as the core, the OptiX PTN 3900 provides
the ATM emulation service.
4.4 Circuit Emulation Service
In a packet switching network (PSN), the circuit emulation services are used to transparently
transmit the TDM circuit. The OptiX PTN 3900 supports TDM CES accessed by the E1 electrical
interfaces and the channelized STM-1 optical interfaces.
4.5 L3VPN Services
The OptiX PTN 3900 supports border gateway protocol (BGP)-based or MPLS-based layer3
virtual private network (L3VPN) services. The equipment provides a complete L3VPN solution.

4 Services Product Description
4.1 Overview
The OptiX PTN 3900 supports the L2VPN and L3VPN service, Ethernet service, ATM service
and CES service. Based on the service model of the OptiX PTN 3900, this section describes the
processing of various services in the OptiX PTN 3900.
4.1.1 Service Model

According to different equipment interconnected, the services of the PTN equipment have
different layer models on the user-network interface (UNI) side and the network-network
interface (NNI) side.
4.1.2 Service Processing
Based on the PTN service model, this section describes the processing of the Ethernet service,
ATM service and CES service in the OptiX PTN 3900.
4.1.1 Service Model

According to different equipment interconnected, the services of the PTN equipment have
different layer models on the user-network interface (UNI) side and the network-network
interface (NNI) side.
OptiX PTN 3900 adopts the MPLS-based PWE3 model to process Ethernet services, ATM
services, and CES services.
OptiX PTN 3900 adopts the BGP/MPLS model to process L3VPN services.
Basic concepts
Basic concepts include customer edge (CE), provider edge (PE), provider (P), and site.
l CE is the edge equipment in the user network and has interfaces to directly connect the
network of the service provider. A CE can be a router, a switch, or a host. Normally, a CE
need not support the MPLS.
l PE is the edge router of the service provider. It is the edge equipment in the network of the
service provider and is directly connected to the CE.
l P is the backbone router in the network of the service provider. It is not directly connected
to the CE. The P equipment needs to have only the basic MPLS forwarding capability.
l Site is the IP system group where IP systems are interconnected and the connectivity is
independent of the network of the service provider. The site is connected to the network of
the service provider through the CE. One site can include multiple CEs, but one CE belongs
to only one site.
MPLS-Based PWE3 Model

The MPLS-Based PWE3 service model of the OptiX PTN 3900 which is used as PE is as shown
in Figure 4-1.

Figure 4-1 MPLS-Based PWE3 Service model of the OptiX PTN 3900
UNI NNI
Forwarder
Emulated
Native service Ethernet TDM TDM ATM Ethernet
ATM switch service
processing switch processing
PWE3 (Encapsulation) Psudo wire
PW Demultiplexer (PW label)

Service Ethernet ATM TDM PSN (MPLS)
interface tunneling
IMA Tunnel (Tunnel label)
PPP PPP 802.2

(MP) HDLC 802.3
Data-Link
E1/ E1/ E1/ STM-1/ GE/ and
Physical FE GE 10GE STM-1
cSTM-1 cSTM-1 cSTM-1 STM-4 10GE Physical
ML-PPP POS Ethernet
To CE To PSN
The UNI side is interconnected to the customer-side equipment (CE), responsible for accessing
the customer-side services to the PSN network. In the service model, the functions of layers on
the UNI side are described as follows.
l Physical layer
The physical layer provides interfaces between the PTN equipment and the transmission
media, such as cables and fibers.
– In the direction from the CE to the PE, the physical layer processes the physical signals
(electrical signals or optical signals) transmitted from the customer-side equipment,
extracts information from the signals, and transmits the information to the service
interface layer.
– In the direction from the PE to the CE, the physical layer receives the information
transmitted from the service interface layer, converts the information into signals
suitable for the transmission through the transmission medium, and then transmits the
signals to the customer-side equipment through the physical channel.
l Service interface layer
– In the direction from the CE to the PE, the service interface layer receives the
information transmitted from the physical layer, distinguishes service types, and
transmits the services to the corresponding native service processing (NSP) layer for
processing.
– In the direction from the PE to the CE, the service interface layer receives the service
signals transmitted from the NSP layer, selects the proper physical channel type and
transmits the signals to the physical layer.

l NSP layer
According to the customer requirements, the NSP layer performs relevant processing for
different services.
The NNI side is interconnected to the PSN equipment, to achieve the transmission of customer
services in the PSN network. In the service model, the functions of layers on the NNI side are
described as follows.
l Emulation service layer
The emulation service layer corresponds to the payload that is to be encapsulated into the
PW. An emulation service corresponds to a PW. The emulation service layer is an abstract
logical layer. The PTN equipment does not perform any specific operation at this layer.
l PWE3 encapsulation layer
The PWE3 encapsulation layer adopts different encapsulation modes for different
emulation services. It can encapsulate different emulation services into PWE3 protocol data
units or decapsulate different emulation services from PWE3 protocol data units.
l MPLS layer
The MPLS layer contains the following two MPLS labels:
– Outer label, that is, the tunnel label. It is used to create and maintain a tunnel that crosses
the MPLS network between the PE stations at two ends of a service, for the purpose of
carrying the PW.
– Inner label, that is, the PW label. It is used to distinguish different PWs in the same
tunnel.
l Data link layer and physical layer
As the carrier layers of the MPLS, the data link layer and the physical layer provide links
for the MPLS layer to transmit data. The OptiX PTN 3900 supports the following network-
side link types.
– Ethernet link (GE/10GE interface)
– POS link (STM-1 or STM-4 interface)
– ML-PPP link (E1 interface or channelized STM-1 interface)
The forwarder located between the UNI and the NNI mutually forwards services processed at
the NSP layer on the UNI side and the emulation services on the NNI side.
NOTE
The Ethernet link of the FE electrical interface is not recommended to be used as the network-side link for
the OptiX PTN 3900.
BGP/MPLS Model
Figure 4-2 shows the BGP/MPLS service model of the OptiX PTN 3900 which is used as PE.

Figure 4-2 BGP/MPLS service model of the OptiX PTN 3900

UNI NNI
VPN label
Native service VRF
processing layer MPLS layer
Tunnel label
Service interface IP
layer IPoE1
PPP PPP 802.2
(MP) HDLC 802.3 Data link layer
E1/ STM-1/ GE/ and
E1/ physical layer
Physical layer FE GE 10GE STM-1 cSTM-1 STM-4 10GE
cSTM-1
ML-PPP POS Ethernet
To PSN
To CE
On the UNI side, the equipment is connected to the customer edge (CE) to access the L3VPN
services to the PSN. In the case of the BGP/MPLS model, layers on the UNI side have the
following functions.
l Physical layer
The physical layer provides interfaces to connect transmission media, such as cables or
fibers, to the PTN equipment.
– In the CE-to-PE direction, the physical layer processes the physical signals (electrical
or optical signals) transmitted from the user-side equipment, extracts information from
the signals, and then sends the signals to the service interface layer.
– In the PE-to-CE direction, the physical layer receives information transmitted from the
service interface layer, converts the information into signals that can be transmitted over
the transmission medium, and then sends the signals to the user-side equipment through
the physical channel.
l Service interface layer
– In the CE-to-PE direction, the service interface layer receives information transmitted
from the physical layer, extracts and sends IP packets to corresponding VPN routing
and forwarding tables (VRFs) for processing.
– In the PE-to-CE direction, the service interface layer receives service signals transmitted
from VRFs, selects proper types of physical channels, and sends the service signals onto
the physical layer.
l Native service processing module
On the native service processing layer, respective VRF processes each L3VPN service. The
VRF has the following functions:
– Forwards IP packets of each service port (UNI ports and NNI ports) in the native VPN
according to the routing table of the VPN.
– Updates routes connected to the CE by running the same routing protocol as CE.
– Updates routes of the VPN by using the multi-protocol extensions for border gateway
protocol (MP-BGP) on all equipment in the VPN.

On the NNI side, the native service processing layer is connected to the PSN equipment to
transmit the L3VPN services in the PSN network. In the case of the BGP/MPLS service model,
layers on the NNI side have the following functions.
l MPLS layer
The MPLS layer includes two MPLS labels:
– The external MPLS label is a tunnel label, which is used to create and maintain a tunnel
between PEs at two ends of a service. The tunnel crosses an MPLS network to carry
PWs.
– The internal MPLS label is a PW label, which identifies a PW in a tunnel.
l Data link layer and physical layer
The data link layer and the physical layer work as the MPLS carrier layer and provide links
for the MPLS layer to transmit data. The OptiX PTN 3900 supports the following types of
network-side links.
– Ethernet link (FE interface or GE interface)
– cSTM-1 link
– ML-PPP link (E1 interface)
Service Model of P Equipment

Figure 4-3 shows the service model of OptiX PTN 3900 which is used as P equipment.
Figure 4-3 OptiX PTN 3900 service model

NNI NNI
Forwarder
MPLS layer Tunnel label Tunnel label MPLS layer
PPP PPP 802.2 PPP PPP 802.2

(MP) HDLC 802.3 (MP) HDLC 802.3
Data-Link STM- STM- Data-Link
and E1/ 1/STM- GE/1 E1/ 1/STM- GE/1 and
Physical cSTM-1 4 0GE cSTM-1 4 0GE Physical
ML-PPP POS Ethernet ML-PPP POS Ethernet
To PSN To PSN
The NNI side, interconnected with the PSN equipment, transmits the services in the public PSN.
The OptiX PTN 3900 has only the MPLS forwarding capability. That is, the OptiX PTN 3900
forwards the MPLS packets according to the forwarding table of tunnel labels.

4.1.2 Service Processing

Based on the PTN service model, this section describes the processing of the Ethernet service,
ATM service and CES service in the OptiX PTN 3900.
Ethernet Service Processing
At the physical layer on the UNI side, the OptiX PTN 3900 supports the interconnection to the
customer-side equipment through the following physical interfaces to access the Ethernet
service.
l FE
l GE
l 10GE
The service interface layer on the UNI side:
l In the direction from the CE to the PE, receives the signals transmitted from the physical
layer, extracts the Ethernet frames, and sends the Ethernet frames to the Ethernet switch
module at the native service processing (NSP) layer for processing.
l In the direction from the PE to the CE, receives the Ethernet frames transmitted from the
Ethernet switch module that is at the NSP layer, and sends the Ethernet frames to the
corresponding Ethernet physical channel.
According to the customer requirements, the NSP layer on the UNI side performs the following
processing.
l Processes a VLAN tag for the Ethernet frames (adds, strips or exchanges a VLAN tag).
l Performs the QoS processing, such as flow classification and congestion management.
l Controls the access authority by using the access control list (ACL).
l Performs the Ethernet OAM processing according to IEEE 802.1ag or IEEE 802.3ah.
The forwarder located between the UNI and the NNI mutually forwards the Ethernet service at
the NSP layer on the UNI side and the relevant PW on the NNI side. The forwarder can adopt
the following two modes to determine the relevant PW of the Ethernet service.
l Port that accesses the Ethernet service

l Port that accesses the Ethernet service + VLAN ID of the Ethernet frame
The emulation service layer on the NNI side corresponds to the payload that is to be encapsulated
into the PW. The emulation service layer is an abstract logical layer. The PTN equipment does
not perform any specific operation at this layer.
The PWE3 encapsulation layer on the NNI side adds the PW header to an Ethernet frame to
form a PW protocol data unit (PDU).
At the MPLS layer on the NNI side, by using two tags, the OptiX PTN 3900 distinguishes the
PW that carries the service from the tunnel that carries the PW.
At the data link layer and the physical layer on the NNI side, the OptiX PTN 3900 carries and
transmits the MPLS packet through different links.

NOTE
On the NNI side, the Ethernet service can be carried by a QinQ Tunnel instead of an MPLS Tunnel. In this
case, the C-VLAN and S-VLAN tags are used instead of MPLS labels.
On the NNI side, the Ethernet service can be directly carried by a physical Ethernet port without using the
PWE3 encapsulation and MPLS label technology. In this case, the Ethernet port is fully occupied by the
Ethernet service.
ATM Service Processing

customer-side equipment through the following physical interfaces to access the ATM service.
l STM-1
l Channelized STM-1 (IMA adaptation is adopted.)
l E1 (IMA adaptation is adopted.)

layer, extracts the ATM cells, and sends the ATM cells to the ATM switch module at the
NSP layer for processing.
l In the direction from the PE to the CE, receives the ATM cells transmitted from the ATM
switch module that is at the NSP layer, and sends the ATM cells to the corresponding
physical channel.
processing.
l Performs the VP switching.
l Performs the VC switching.
l Performs the ATM OAM processing.
The forwarder located between the UNI and the NNI mutually forwards the ATM service at the
NSP layer on the UNI side and the relevant PW on the NNI side. The forwarder can adopt the
following modes to determine the relevant PW of the ATM service.
l VCC
l VPC
into the PW. The emulation service layer is an abstract logical layer. The PTN equipment does
not perform any specific operation at this layer.
The PWE3 encapsulation layer on the NNI side can adopt the following two modes to encapsulate
the ATM cells into a PW PDU.
l Encapsulating one ATM cell into a PW PDU.
l Encapsulating N (N<=31) ATM cells into a PW PDU. This is also referred to as ATM cell
concatenation.

CES Service Processing
customer-side equipment through the following physical interfaces to access the CES service.
l Channelized STM-1
l E1
layer, extracts the TDM services, and sends the TDM services to the TDM processing
module at the NSP layer for processing.
l In the direction from the PE to the CE, receives the TDM services transmitted from the
TDM processing module that is at the NSP layer, and sends the TDM services to the
corresponding physical channel.
processing
l Performs the multiplexing and demultiplexing for channelized STM-1 signals and E1
signals.
l Performs the E1 (VC-12) granularity scheduling for the channelized STM-1 signals.
The forwarder located between the UNI and the NNI mutually forwards the TDM service at the
NSP layer on the UNI side and the relevant PW on the NNI side. The forwarder can adopt the
following two modes to determine the relevant PW of the TDM service.
l E1 port that accesses the TDM service

l Channelized STM-1 port and VC-12 timeslot that access the TDM service
into the PW. The emulation service layer is an abstract logical layer. No specific operation is
performed at this layer.
The PWE3 encapsulation layer on the NNI side can adopt the following two modes to encapsulate
the TDM service into a PW PDU.
l Structure-agnostic encapsulation. In this case, the emulated E1 signals are considered as a

bit stream. No matter whether the emulated E1 signals have the timeslot structure, the PTN
equipment does not recognize the timeslot structure.
l Structure-aware encapsulation. In this case, the emulated E1 signals are considered as a
structure-aware bit stream consisting of 64 kbit/s timeslots. The 64 kbit/s timeslots are
visible to the PTN equipment.
4.2 Ethernet Service

The OptiX PTN 3900 supports various Ethernet services and provides ideal L2VPN solutions.

A virtual private network (VPN) is a private network constructed on the basis of the public
network. The L2VPN is the VPN based on technologies of the link layer. The VPN constructed
on the public network can provide the same security, reliability and manageability as the existing
private networks.
Service providers can provide the VPN value-added service for enterprises to fully use the
existing network resources and to increase the service volume. In addition, service providers
can consolidate long-term partnership with enterprises.
For VPN users, the cost to lease the network is saved. The flexibility of the VPN networking
makes the network management easier for enterprises. As the network security and encryption
technology develops, the private data can be transmitted over the public network with security.
Service Form
For the OptiX PTN 3900, the Ethernet service has the following forms.
l Point-to-point service: E-Line service

l Multipoint-to-multipoint service: E-LAN service
l Multipoint-to-point converging service: E-Aggr service
The QoS processing, such as flow classification and bandwidth control, can be performed for
the Ethernet service.
Standardization organizations such as ITU-T, IETF and MEF stipulate the model frames for L2
Ethernet services. Table 4-1 lists these model frames. In this document, the L2 Ethernet services
are of the model frame stipulated by MEF.
Table 4-1 Comparison among L2 Ethernet services stipulation
Service Type Service Transport IETF ITU-T MEF

Multiplexing Tunnel Model Model Model
Point-to- Line Physically Physically - EPL E-Line

point isolated isolated
service
Virtual Physically VLAN - EVPL
Line isolated
MPLS VPWS
VLAN Physically -
isolated
VLAN -
MPLS VPWS
Multipoint- LAN Physically Physically - EPLAN E-LAN

to- isolated isolated
multipoint
service Virtual VLAN Physically - EVPLAN
LAN isolated
S-VLAN -
MPLS VPLS

Service Type Service Transport IETF ITU-T MEF

Multiplexing Tunnel Model Model Model
S-VLAN B-MAC -
B-VLAN
E-Line Service Illustration

Figure 4-4 illustrates the E-Line service provided by the PTN products.
Company A has two branches in City 1 and City 3. Company B has two branches in City 2 and
City 3. Company C has two branches in City 1 and City 2. The branches of Company A, Company
B, and Company C require data communication among themselves. Private line services are
then provided to Company A, Company B, and Company C separately for the communication
requirement. In addition, the data are isolated.
Figure 4-4 E-Line service illustration
Metro Nationwide/Global Metro

carrier Ethernet carrier Ethernet carrier Ethernet
Company A Company A
Company C Metro Company B

carrier Ethernet
City 1 City 3
E-Line1
E-Line2 City 2
E-Line3
Company C Company B
E-LAN Service Illustration

Figure 4-5 illustrates the E-LAN service provided by the PTN products.
The headquarters of Company Z is in City 3. Branch A of Company Z is located at City 1, City
2 and City 3. Branch B of Company Z is located at City 1 and City 2. Branch A and Branch B
have no service connection. Data from the two branchs should be isolated. The headquarters
needs to communicate with the branchs and to access to the Internet.
The PTN products can be used to provide the E-LAN service. Different VLAN tags are used to
identify service data from different branchs. In this way, the headquarters can communicate with

the branchs and the data from different branchs are isolated. In addition, the VLAN is used to
isolate the Internet data accessed by the headquarters from the internal service data.
Figure 4-5 E-LAN service illustration
ISP
Metro Nationwide/Global
carrier Ethernet carrier Ethernet
Branch B Headquarter
Metro
carrier Ethernet
Branch A Metro Branch B

carrier Ethernet
City 1 City 3
VLAN1 City 2
VLAN2
VLAN3 Branch A Branch B Branch A
E-Aggr Service Illustration

The E-Aggr service is a point-to-point bidirectional convergence service. Figure 4-6 illustrates
the E-Aggr service provided by the PTN products.
To construct a 3G network, an operator needs to converge services from each NodeB and transmit
the converged services to the RNC. The data flow between NodeB and the RNC is taken as a
service. At the convergence node, overall bandwidth is specified for the services to ensure the
QoS.

Figure 4-6 E-Aggr service illustration
FE
FE
GE
FE
OptiX PTN 3900 Node B
OptiX PTN 1900 RNC
4.3 ATM Service

In the transport network with the packet switching as the core, the OptiX PTN 3900 provides
the ATM emulation service.
The OptiX PTN 3900 accesses ATM services at the source node and encapsulates the ATM cells
in the PW and then transports them to the destination node. At the destination node, ATM cells
are recovered. In this way, ATM services are emulated. The OptiX PTN 3900 supports the
following encapsulation schemes.
l 1:1 virtual channel connection (VCC) mapping scheme: one VCC is mapped into one PW.
l N:1 VCC mapping scheme: N (N≤32) VCCs are mapped into one PW.
l 1:1 virtual path connection (VPC) mapping scheme: one VPC is mapped into one PW.
l N:1 VPC mapping scheme: N (N≤32) VPCs are mapped into one PW.
The OptiX PTN 3900 can access the IMA service and supports the following operations.
l Query of the IMA link status.
l Add the channelized STM-1 VC-12 link (CD1) or E1 link to the IMA group.
l Delete the channelized STM-1 VC-12 link (CD1) or E1 link from the IMA group.
The OptiX PTN 3900 supports the following ATM specifications.

l The OptiX PTN 3900 supports a maximum of 4k ATM services (remote service) and a
maximum of 2k ATM services (local service), each optical interface supports 512 ATM
services.
l The OptiX PTN 3900 supports a maximum of 8k ATM connections (remote service) and
a maximum of 4k ATM connections (local service), each optical interface supports 1k ATM
connections.
The OptiX PTN 3900 supports the following IMA specifications.
l The CD1 board supports a maximum of 64 IMA groups.
l The MD1 board and MQ1 board support a maximum of 32 IMA groups.
l Each IMA group contains a maximum of 32 E1 links or 32 channelized STM-1 VC-12
channels.
For the ATM service, the QoS policies can be configured in relation to the service type and
bandwidth.
4.4 Circuit Emulation Service

In a packet switching network (PSN), the circuit emulation services are used to transparently
transmit the TDM circuit. The OptiX PTN 3900 supports TDM CES accessed by the E1 electrical
interfaces and the channelized STM-1 optical interfaces.
Application Model
The OptiX PTN 3900 uses the PWE3 technology to provide the CES.
The CES mainly applies to the wireless service and enterprise private line service. For 2G/3G
stations or enterprise private lines, the PTN equipment accesses E1 signals from E1 lines or
channelized STM-1 lines. The PTN equipment then encapsulates the E1 signals into packets,
which are then transported to the opposite end through the PW. Figure 4-7 shows the process.

Figure 4-7 CES service application model
Backbone
layer
IP/MPLS backbone
Convergence
RNC BSC
layer
Access
layer
NodeB BTS BTS NodeB
OptiX OptiX
CES
PTN 3900 PTN 1900
Emulation Mode
The OptiX PTN 3900 supports the CES services in both the structured emulation mode and
unstructured emulation mode.
The structured emulation mode is also the structure-aware TDM circuit emulation service over
packet switched network (CESoPSN) mode.
l In this mode, the equipment detects the frame structure, framing scheme and timeslot
information in the TDM circuit.
l In this mode, the equipment processes the overhead in the TDM frames and extracts the
payload. The equipment then places each channel of timeslots into the packet payload in a
certain sequence. In this way, each channel of services are fixed and known.
The unstructured emulation mode is also the structure-agnostic TDM over packet (SAToP)
mode.
l In this mode, the equipment does not detect the structure of any TDM signals, but takes
signals as bit flow of the fixed rate. In this way, the overall TDM signals is emulated.
l In this mode, the overhead and payload in the TDM signals are transparently transmitted.
In the structured emulation mode, the OptiX PTN 3900 senses the E1 structure of the TDM
signal and provides the idle 64 kbit/s timeslot suppression function to save the transmission
bandwidth.

Service Clocks
TDM services have high requirements for clock synchronization. The OptiX PTN 3900 supports
the retiming synchronization mode.
In the retiming synchronization mode, the system clock of the PEs are synchronized and the
system clock is used as the service clock (retiming). Thus, all the PEs and CEs are synchronized
and the service clocks of the TDM services on all the CEs and PEs are synchronized. See Figure
4-8.
Figure 4-8 Retiming synchronization mode of the CES service clock
CES
BTS TDM PE PE TDM BSC
4.5 L3VPN Services

The OptiX PTN 3900 supports border gateway protocol (BGP)-based or MPLS-based layer3
virtual private network (L3VPN) services. The equipment provides a complete L3VPN solution.
Basic Concepts
The BGP/MPLS L3VPN, based on the PE, is an L3VPN technology of the provider provisioned
VPN (PPVPN). It uses the BGP to issue VPN routes in the backbone network of the service
provider and uses the MPLS to forward VPN packets in the backbone network of the service
provider.
The BGP/MPLS L3VPN enables flexible networking and can be easily extended. In addition,
the BGP/MPLS L3VPN supports the MPLS QoS and MPLS TE.
Figure 4-9 shows the schematic diagram of BGP/MPLS L3VPN application.

Figure 4-9 Networking Application of the BGP/MPLS L3VPN
CE-A CE-C VPN 2

VPN 1
Backbone network
P P
PE
PE
PE
VPN 2 P P
VPN 1
CE-D
CE-B
OptiX PTN 3900/OptiX PTN 1900
CE
Route Diffusion
The route is the basis of the Layer 3 IP forwarding. The diffusion and differentiation of routers
is a core problem to be solved by the L3VPN solution
The BGP/MPLS L3VPN solution of the OptiX PTN equipment supports the following routing
mechanisms:
l Runs the open shortest path first (OSPF), routing information protocol (RIP), and E-BGP
routing protocols together with the CE to complete the VPN route diffusion between the
local equipment and the CE.
l Uses the MP-BGP protocol to complete the VPN route diffusion between PEs in the same
VPN.
l Uses the IS-IS routing protocol for networking between the OptiX PTN equipment.
Service Forwarding
The BGP/MPLS L3VPN adopts the MPLS technology to forward service packets by using two
MPLS labels. On the PE connected to the CE, the VPN, to which a service packet belongs, is
distinguished by using the inner MPLS label. When traveling the public PSN, the service packets
are forwarded in the public PSN by using the outer MPLS label.
As shown in Figure 4-10, IP packets of the CE-C in VPN 2 need be transmitted to the subnet
connected to CE-B. For the packet forwarding process, see Table 4-2.

Figure 4-10 Service packet forwarding of the BGP/MPLS L3VPN

IP IP
VPN 2 VPN 2
CE-A Label 2 Label 1 IP VPN 2
IP Link Link ETH
VPN 1 VPN 2
Label 3
P1 P2 CE-C
Link
PE-Y
PE-X
IP
ETH
PE-Z
VPN 2 P3 P4
VPN 1
CE-D
CE-B
Table 4-2 Instances for service packet forwarding of the BGP/MPLS L3VPN
NE Action Description Label Stack
CE-C Forwards a IP The destination IP address is the host IP

packet. that is connected to CE-B and is ETH
located in VPN 2. The IP packet is
transmitted to PE-Y through an
Ethernet link.
PE-Y Extracts the IP PE-Y extracts the IP packet from the IP

packet. Ethernet link that is connected to CE-
C.
PE-Y Determines the PE-Y determines that the packet IP

VPN that the IP belongs to VPN 2 based on the VPN 2
packet belongs Ethernet port and then adds a MPLS
to. private label, which corresponds to
VPN 2, to the IP packet.
PE-Y Routes and PE-Y checks for the virtual routing IP

forwards the and forwarding (VRF) table VPN 2
packet. corresponding to VPN 2. Based on Label 1
the VRF table, it learns that the Link
packet should be forwarded to the
tunnel between PE-Y and PE-X.
Then, PE-Y adds MPLS label 1,
which corresponds to the tunnel, to
the IP packet.

NE Action Description Label Stack
P2 MPLS P2 extracts the outer MPLS label IP

forwarding from the packet and checks for the VPN 2
MPLS forwarding table. Then, P2 Label 2
forwards the MPLS forwarding table Link
to the link connected to P1 and
exchanges the outer label with label
2.
P1 MPLS P1 extracts the outer MPLS label IP

forwarding from the packet and checks for the VPN 2
MPLS forwarding table. Then, P2 Label 3
forwards the MPLS forwarding table Link
to the link connected to PE-X and
exchanges the outer label with label
3.
PE-X Determines the PE-X extracts the forwarded MPLS IP

VPN that the packet, strips the two MPLS labels,
packet belongs and determines that the packet
to. belongs to VPN 2 based on the inner
label.
PE-X Routes and PE-X checks for the VRF table IP

forwards the corresponding to VPN 2. Based on ETH
packet. the VRF table, it learns that the
packet should be forwarded to the
Ethernet link connected to CE-B.
Then, PE-X adds Ethernet
encapsulation to the IP packet and
sends it to CE-B.

Product Description 5 Key Features
5 Key Features
About This Chapter
This chapter describes key features of the equipment.

5.1 MPLS
The OptiX PTN 3900 uses the multiprotocol label switching (MPLS) technology to transport
multiple types of services. This section describes the basic concepts related to the MPLS and
application of the MPLS supported by the OptiX PTN 3900.
5.2 IS-IS Routing Protocol
The intermediate system to intermediate system (IS-IS) routing protocol, a link state protocol,
belongs to the internal gateway protocol and is applicable to the internal of the autonomous
system. The OptiX PTN 3900 uses the IS-IS routing protocol, which is used with the label
distribution protocols RSVP-TE and LDP to realize the dynamic creation of the MPLS LSP.
5.3 BGP
In the case of the L3VPN service application, the OptiX PTN 3900 uses the BGP to control route
advertisement and selection of the best route. On the client side, the OptiX PTN 3900 discovers
routes by running the external BGP (E-BGP). On the network side, the OptiX PTN 3900
discovers routes by running the multiprotocol extensions for BGP-4 (MP-BGP).
5.4 OSPF Protocol
The OptiX PTN 3900 supports the open shortest path first (OSPF) protocol. On the client side,
the OptiX PTN 3900 discovers routes by running the OSPF protocol. On the network side, the
OptiX PTN 3900 discovers routes by running the OSPF protocol and provides the conditions
for tunnel creation, that is, enables OSPF traffic engineering (TE).
5.5 RIP
The OptiX PTN 3900 supports the routing information protocol (RIP). On the client side, the
OptiX PTN 3900 obtains the routing information and discovers routes by running the RIP.
5.6 MPLS Signaling
The MPLS signaling used by the OptiX PTN 3900 includes LSP signaling and PW signaling.
The LSP signaling is responsible for distributing LSP labels and the PW signaling is responsible
for distributing PW labels to establish PW.
5.7 PWE3
The pseudo wire emulation edge-to-edge (PWE3) technology is used to provide tunnels on the
packet switching network (IP/MPLS) to emulate the Layer 2 VPN protocol for some services,

5 Key Features Product Description
such as the TDM, ATM and Ethernet services. The emulated VPN protocol is used to connect
the traditional network and packet switching network. In this way, networks are extended and
resources can be shared.
5.8 IP Tunnel and GRE Tunnel
The OptiX PTN 3900 can use the IP tunnel or GRE tunnel to carry the ATM PWE3 service,
CES PWE3 service and ETH PWE3 service. In this way, ATM emulation services and ETH
emulation services can be transparently transmitted in an IP network.
5.9 QoS
The equipment supports DiffServ based on the standard, including flow classification, flow
policing, traffic shaping, congestion management and queue scheduling.
5.10 IGMP Snooping
The Internet group management protocol (IGMP) Snooping function is used to realize multicast
distribution.
5.11 MSTP/RSTP/STP
The multiple spanning tree protocol (MSTP) is compatible with the spanning tree protocol (STP)
and rapid spanning tree protocol (RSTP). In addition, the MSTP rectifies the defects of the STP
and RSTP. The MSTP supports fast reconfiguration and provides multiple paths for forwarding
data. During the data forwarding process, the VLAN data is of load balance. The MSTP complies
with IEEE 802.1s.
5.12 ACL
To filter data packets, the access control list (ACL) can be used to stipulate a series rules in order.
The equipment classifies the received data packets according to the ACL rules and then forwards
or discards these packets.
5.13 BFD
The OptiX PTN 3900 supports the bidirectional forwarding detection (BFD) function. The Hello
mechanism is used to detect states of Ethernet links.
5.14 Synchronous Ethernet Clock
The OptiX PTN 3900 realizes the synchronous Ethernet clock on the Physical layer.
5.15 IEEE 1588 V2 Clock
The OptiX PTN 3900 supports the function of adopting the IEEE 1588 V2 protocol to realize
clock synchronization and time synchronization.

5.1 MPLS
The OptiX PTN 3900 uses the multiprotocol label switching (MPLS) technology to transport
multiple types of services. This section describes the basic concepts related to the MPLS and
application of the MPLS supported by the OptiX PTN 3900.
5.1.1 MPLS Background

The multiprotocol label switching (MPLS) was originally used to increase the forwarding speed
of a router. Currently, the MPLS are evolving to the backbone routing and the VPN solution.
5.1.2 Basic MPLS Concepts
Several basic MPLS concepts facilitate the understanding of the MPLS technology. These basic
MPLS concepts include forwarding equivalence class (FEC), label, label distribution protocol
(LDP) and label switched path (LSP).
5.1.3 MPLS System Structure
The MPLS system consists of the control plane and forwarding plane.
5.1.4 MPLS Features of the Equipment
Using the MPLS technology, the OptiX PTN 3900 not only greatly increases the packet
forwarding speed but also provides the capability of seamlessly connecting to Layer 2 networks
such as the ATM and Ethernet networks. In addition, the OptiX PTN 3900 provides better
solutions for application of the TE, VPN and QoS.
5.1.1 MPLS Background

The multiprotocol label switching (MPLS) was originally used to increase the forwarding speed
of a router. Currently, the MPLS are evolving to the backbone routing and the VPN solution.
The MPLS is integrated with the Layer 3 routing function of the IP network and the highly
effective forwarding mechanism of the traditional Layer 2 network. Similar to the forwarding
scheme of the existing Layer 2 network, the forwarding plane is connection-oriented. Hence,
the MPLS can be seamlessly connected to Layer 2 networks such the ATM and Ethernet
networks. In addition, the MPLS provides better solutions for the application of the traffic
engineering (TE), virtual private network (VPN) and quality of service (QoS). Hence, the MPLS
becomes a criterion for expanding the data network and increasing the network operability.
To better meet the requirements of the transport network for service quality, the connectionless
feature of the standard MPLS should be simplified, and the OAM and protection capabilities
should be enhanced. In compliance with the latest international standards, the OptiX PTN
3900 supports a series of MPLS features for the transport network.
5.1.2 Basic MPLS Concepts

Several basic MPLS concepts facilitate the understanding of the MPLS technology. These basic
MPLS concepts include forwarding equivalence class (FEC), label, label distribution protocol
(LDP) and label switched path (LSP).
Forwarding Equivalence Class

As a classification forwarding technology, the MPLS considers the packets of the same
forwarding scheme as a class, which is called an FEC. In the MPLS network, the packets in the
same FEC are processed in the same way.

Label
A label is a short identifier of fixed length and is locally valid (only valid in the MPLS domain).
The label is used to identify the FEC that one packet belongs to. On certain conditions, for
example, when load sharing is required, several labels may correspond to one FEC, but one label
just indicates one FEC.
The packet headers carry labels and the labels do not contain any topology information. Labels
are locally valid. A label has four bytes, which are encapsulated in the way illustrated in Figure
5-1.
Figure 5-1 Label encapsulation structure

0 19 22 23 31
Label Exp S TTL
A label has the following four sections.
l Label: 20 bits. The label section indicates the label value and is used as the forwarding
pointer.
l Exp: 3 bits. The Exp section is reserved for test and currently used for CoS.
l S: 1 bit. The S section is an identifier at the bottom of a stack. The MPLS supports the
layered labels, or multiple labels. If S is 1, it indicates that the label is at the bottom.
l TTL: 8 bits. The TTL section has the same indication as the time to live (TTL) of IP packets.
As a connection identifier, the label is similar to the VPI/VCI for ATM. The labels are
encapsulated between the link layer and the network layer in a Ethernet frame. Figure 5-2 shows
the encapsulation location of labels.
Figure 5-2 Encapsulation location of labels in Ethernet frames
Ethernet/PPP header Label Layer 3 data
Ethernet/SONET/SDH packet
LDP
The LDP is the control protocol for the MPLS. Similar to the signaling protocol of the traditional
network, the LDP is responsible for creation and maintenance of LSP and PW, FEC
classification, and label distribution.
The MPLS can use several types of label distribution protocols.
l Some protocols are exclusively stipulated for label distribution, such as LDP and constraint-
routing label distribution protocol (CR-LDP). The OptiX PTN 3900 uses the LDP to create
and maintain PWs.
l Some exiting protocols can be extended to support the label distribution, such as border
gateway protocol (BGP) and resource reservation protocol (RSVP). The OptiX PTN

3900 uses the resource reservation protocol-traffic engineering (RSVP-TE) protocol to

create and maintain LSPs.
LSP
In an MPLS network, the path involved in an FEC is called an LSP.
The LSP is a unidirectional path from the ingress to egress. Each node on an LSP is a label
switched router (LSR). According to the data transport direction, adjacent LSRs are upstream
LSR and downstream LSR.
The LSPs are classified into static LSPs and dynamic LSPs. The static LSPs are manually
configured by the administrator. The dynamic LSPs are created dynamically by the RSVP-TE
protocol.
5.1.3 MPLS System Structure

The MPLS system consists of the control plane and forwarding plane.
The control plane of the MPLS system is connectionless. The control plane of the MPLS system
uses the powerful and flexible routing function of a Layer 3 network, which meets the network
requirements of new application.
The forwarding plane is also called a data plane, which is connection-oriented and can use Layer
2 networks such as Ethernet. The MPLS uses short labels of fixed length to encapsulate packets.
The forwarding plane then quickly forwards the encapsulated packets.
5.1.4 MPLS Features of the Equipment

Using the MPLS technology, the OptiX PTN 3900 not only greatly increases the packet
forwarding speed but also provides the capability of seamlessly connecting to Layer 2 networks
such as the ATM and Ethernet networks. In addition, the OptiX PTN 3900 provides better
solutions for application of the TE, VPN and QoS.
To ensure the service quality required in a transport network, the OptiX PTN 3900 simplifies
the non-connection-oriented feature of the MPLS.
l The OptiX PTN 3900 does not use the penultimate hop popping (PHP).
l The OptiX PTN 3900 does not support LSP Merge, for the LSP Merge makes the source
of a data flow unknown. If the source is unknown, the OAM and performance monitoring
become difficult or unusable.
l The OptiX PTN 3900 does not support the equal cost multiple path (ECMP), for the ECMP
makes the CC of the OAM and performance monitoring complex.
In addition, the OptiX PTN 3900 provides complete OAM support and powerful protection
capabilities.
l The OptiX PTN 3900 uses the MPLS OAM mechanism compliant with ITU-T Y.1711 to
fast check the LSP.
l The OptiX PTN 3900 uses the protection switching mechanism that complies with ITU-T
Y.1720 and ITU-T G.8131. The OptiX PTN 3900 not only provides FRR protection for
LSPs, but also provides end-to-end transport protection for LSPs.
The OptiX PTN 3900 supports the MPLS technology and has the following MPLS features.

Table 5-1 MPLS features of OptiX PTN 3900

Feature Description
MPLS basic The equipment supports basic MPLS functions and service forwarding.
function The equipment uses the RSVP-TE protocol to create and maintain the
MPLS Tunnels, and uses the LDP to create and maintain the PWs.
The equipment uses the MPLS tunnel technology and the pseudo wire
emulation edge-to-edge (PWE3) technology to form an MPLS network,
where multiple services can be accessed.
The equipment supports the static MPLS Tunnel and dynamic MPLS
Tunnel.
The equipment supports the static PW and dynamic PW.
MPLS OAM The equipment supports the MPLS OAM in compliance with ITU-T Y.
1711.
The equipment supports Ping and TraceRoute commands for the MPLS
Tunnel.
MPLS protection The equipment supports the MPLS Tunnel re-route (RR).
The equipment supports the MPLS Tunnel fast re-route (FRR).
The equipment supports the 1+1 protection and 1:1 protection for the
MPLS Tunnel.
Others The equipment supports the TE based on the MPLS Tunnel.
The equipment supports the MPLS QoS.
Table 5-2 MPLS specification of OptiX PTN 3900

Feature Specifications
Maximum 8k
number of MPLS
tunnel
Maximum 16k
number of PWs
5.2 IS-IS Routing Protocol

The intermediate system to intermediate system (IS-IS) routing protocol, a link state protocol,
belongs to the internal gateway protocol and is applicable to the internal of the autonomous
system. The OptiX PTN 3900 uses the IS-IS routing protocol, which is used with the label
distribution protocols RSVP-TE and LDP to realize the dynamic creation of the MPLS LSP.
The IS-IS routing protocol used by the OptiX PTN 3900 creates and synchronizes the link state
database (LSD) through routing protocol packets, such as link state PDUs. Based on the LSDB

and path cost, the OptiX PTN 3900 uses the optimized shortest path first (SPF) algorithm to
generate the routing table, and uses the IS-IS TE of the IS-IS routing protocol to generate the
traffic engineering database (TEDB). The TEDB and routing table are the bases of creating the
MPLS LSP. The TEDB computes the route that the MPLS LSP travels through. The routing
table forwards the RSVP-TE and LDP protocol packets to realize label distribution. In this way,
the MPLS LSP is dynamically created.
Three features of the IS-IS routing protocol are supported by the OptiX PTN 3900, that is, three
types of IS-IS routing protocol packets, optimized SPF algorithm, path cost, and IS-IS traffic
engineering (IS-IS TE).
Three Types of IS-IS Routing Protocol Packets

The IS-IS routing protocol belongs to the network player of the OSI protocol model. The IS-IS
routing protocol runs directly at the data link layer. When the IS-IS routing protocol is processed,
the decapsulation of the network layer is absent. With the preceding feature, the IS-IS routing
protocol is more applicable to the PTN transport network using the MPLS packet switching
technology.
The IS-IS routing protocol packets use the uniform encapsulation format. The length of the
packets is changeable and the extensibility is strong. The complexity of the protocol is decreased,
because the types of the protocol packets are few. Thus, the running is more reliable and efficient.
The OptiX PTN 3900 realizes the following three types of IS-IS routing protocol packets:
l Hello packets
Hello packets are used to construct and maintain neighbor relation between network nodes.
Hence, Hello packets are also called IS-to-IS hello (IIH) PDUs.
l Link state PDUs
Link state PDUs are used to exchange the link state information. In a network running the
IS-IS routing protocol, each network node generates a link state PDU, which contains all
the link state information of this network node. To generate its own LSDB, each network
node collects all the link state PDUs within the local domain and between domains.
l SNP packets
Sequence number PDUs (SNP) describe the link state PDUs in all or part of the LSDB.
The SNP is used to synchronize and maintain the LSDB of each network node in the PTN
network.
Optimized SPF Algorithm

The IS-IS routing protocol realized by the OptiX PTN 3900 uses the optimized SPF algorithm
for route computation and update. When the topology is changed, the resources (network
bandwidth, processing capability of network nodes, and memory) for updating the new route
are few, and thus the convergence rate of the entire network is improved.
path cost
The OptiX PTN 3900 supports the manual setting of path cost, and controls the route that the
MPLS LSP travels through when it is dynamically created.
IS-IS TE
When the MPLS constructs the LSP, the traffic engineering information of all the links in the
local domain should be known. The IS-IS TE realized by the OptiX PTN 3900 supports the

construction of the MPLS LSP. The OptiX PTN 3900 obtains the traffic engineering information
(link utilization and path cost) of all the links in the network through the IS-IS routing protocol.
It constructs and synchronizes the TEDB, and uses the constrained shortest path first (CSPF)
algorithm used by the TEDB to compute the route that the MPLS LSP travels through.
5.3 BGP
In the case of the L3VPN service application, the OptiX PTN 3900 uses the BGP to control route
advertisement and selection of the best route. On the client side, the OptiX PTN 3900 discovers
routes by running the external BGP (E-BGP). On the network side, the OptiX PTN 3900
discovers routes by running the multiprotocol extensions for BGP-4 (MP-BGP).
As an exterior gateway protocol (EGP), the border gateway protocol (BGP) runs between
autonomous systems (ASs) to control route advertisement and selection of the best route.
NOTE
An AS is a collection of routers that are under the control of one entity and have the same internal routing
policy.
The BGP supported by the OptiX PTN 3900 complies with RFC 3107 (Carrying Label
Information in BGP-4), RFC 1997 (BGP Communities Attribute), RFC 4271 (A Border Gateway
Protocol 4) and RFC 4760 (Multiprotocol Extensions for BGP-4).
Basic Concepts
The basic concepts with regard to the BGP are as follows:
l Speaker: The OptiX PTN equipment that transmits the BGP messages is referred to as a
speaker, which receives or generates new routing information and advertises the routing
information to its peers. When a BGP speaker receives routing information from another
AS, the BGP speaker advertises the routes to its peers in the AS, if the route is better than
the known routes or the BGP speaker does not contain the routes.
l Peer: The BGP speakers that exchange the routing information are peers to each other.
l Internal BGP (I-BGP): When the BGP runs in the same AS, the BGP is referred to as I-
BGP.
l External BGP (E-BGP): When the BGP runs in different ASs, the BGP is referred to as E-
BGP.
l MP-BGP: MP-BGP is the multiprotocol extensions for the BGP-4. The MP-BGP supports
multiple network protocols. MP-BGP runs in the same AS.
BGP Messages
In the PSN, the BGP notifies the routing information, maintains and interrupts connections by
transporting the BGP messages. The OptiX PTN 3900 supports the following messages:
l Open messages: When a TCP connection is established, the Open messages are sent to
establish connections between BGP peers.
l Update messages: The Update messages are transported for peers to exchange the routing
information. The Update messages can advertise the information about multiple reachable
routes with the same attributes and delete the information about multiple unreachable
routes.

l Keepalive messages: The Keepalive messages are sent periodically to the peers to maintain
the validity of connections. When receiving the Open messages, the peers send the
Keepalive messages to maintain the validity of connections. After the acknowledgment,
the peers can exchange the Update, Notification, and Keepalive messages.
l Notification messages: When detecting a status error, the Notification messages are sent
to peers. Then, the BGP connection is interrupted immediately.
NOTE
The routing information is transported according to the incremental updates. That is, only route changes
are notified.
BGP Attributes
BGP routing attributes are a series of parameters that further define certain routes and thus help
the BGP to filter and select routes.
The OptiX PTN 3900 supports the following BGP attributes:
l Origin: The Origin attribute defines the origin of the path information.
l AS_Path: The AS_Path attribute records the numbers of the ASs that one route traverses
from the local to the destination, in a vector sequence. The AS_Path attribute avoids route
loops. Generally, the BGP does not receive the information about the route whose AS_Path
attribute contains the local AS number. In this manner, the route loop is avoided.
l Next_Hop: The Next_Hop attribute indicates the address of the next hop along the message
transmission path to the destination.
l Multi-exit-descriminator (MED): The MED attribute is transmitted only between two
adjacent ASs to determine the best route along which the traffic enters the AS. The route
whose MED value is the smallest is selected as the best route with priority.
l Community: The Community attribute simplifies the routing policy and facilitates the
maintenance and management of routes.
BGP Route Selection Policy

When there are multiple routes with the same destination, the BGP selects the routes by using
the following polices:
1. Discards the route whose next hop is unreachable.
2. Prefers the route of the highest Local_Pref value.
3. Prefers the route that starts from the OptiX PTN equipment.
4. Prefers the route with the least AS_Path.
5. Prefers the route whose Origin is the lowest.
6. Prefers the route whose MED is the lowest.
7. Prefers the routes learned from the E-BGP.
8. Prefers the route of the shortest path in the AS.
BGP Route Notification Principle

The OptiX PTN 3900 notifies the routing information by adhering to the following principles:
l When there are multiple valid routes, the BGP speaker advertises only the best route to its
peers.

l The BGP speaker advertises only the routing information that it uses to its peers.
l The BGP speaker advertises all the routes that it learns from the E-BGP to its peers
(including E-BGP peers and I-BGP peers).
l The BGP speaker does not advertises the routes that it learns from the I-BGP to its I-BGP
peers.
l The BGP speaker advertises the routes that it learns from the I-BGP to its E-BGP peers,
when the synchronization of the BPG and IGP is not enabled.
l The BGP speaker advertises all the BGP routes to the new peers once the connections are
established.
NOTE
The synchronization between the BGP and IGP refers to the process where the BGP adds a new route to
the routing table only after the IGP adds the new route to the routing table. If the BGP is not synchronous
with the IGP, the BGP straightly adds new routes to the routing table.
5.4 OSPF Protocol

The OptiX PTN 3900 supports the open shortest path first (OSPF) protocol. On the client side,
the OptiX PTN 3900 discovers routes by running the OSPF protocol. On the network side, the
OptiX PTN 3900 discovers routes by running the OSPF protocol and provides the conditions
for tunnel creation, that is, enables OSPF traffic engineering (TE).
The OSPF protocol is a dynamic interior gateway protocol (IGP) that is compiled based on link
status by IETF.
On the network, the OSPF protocol transfers the link state information and computes routes to
obtain the routing information according to the link state information.
The OSPF protocol supported by the OptiX PTN 3900 complies with RFC 3623 (Graceful OSPF
Restart), RFC 2328 (OSPF Version 2), RFC 3630 (TE Extensions to OSPF Version 2), and RFC
2370 (The OSPF Opaque LSA Option).
Basic Concepts
The basic concepts with regard to the OSPF protocol include the OSPF protocol packet, link
state advertisement (LSA), neighbor, adjacency, router ID, and OSPF TE.
l There are the following categories of OSPF protocol packets:
– Hello packets: The Hello packets are used to discover and maintain the OSPF
neighborhood and are sent periodically.
– Database description (DD) packets: Exchanging the DD packets are used to maintain
synchronization of the databases. The DD packets describe the summary of the local
link state database (LSDB).
– Link state request (LSR) packet: The LSR packets are used to request for the required
LSA from each other. The LSR packets are sent to each other only after they successfully
start to exchange the DD packets.
– Link state update (LSU) packet: The LSU packets are used to send the required LSA to
each other.
– Link state acknowledgment (LSAck) packet: The LSAck packets are used to
acknowledge the received LSA.
l The OSPF advertises the routing information by encapsulating the route description into
LSAs. The common LSA categories are as follows:

– Router LSA (type 1): The router LSA describes the link status and cost of the OptiX
PTN equipment and is flooded only in the OSPF area.
– Network LSA (type 2): The network LSA describes the status of the links in the local
network segment and is flooded in the OSPF area.
– Network summary LSA (type 3): The network summary LSA describes the routes in a
certain network segment in the OSPF area and advertises the routing information to
other related OSPF areas.
– AS boundary router (ASBR) summary LSA (Type 4): The ASBR summary LSA
describes the routes to the ASBRs and advertises the routing information to all other
related OSPF areas except the areas where the ASBRs are located.
– AS external LSA (type 5): The AS external LSA describes the routers to the outside of
the AS and advertises the routing information to all the OSPF areas (Stub area and NSSA
excluded).
– Not so totally stub area (NSSA) LSA (type 7): The NSSA LSA describes the routers to
the outside of the AS and is flooded only in the NSSA.
– Opaque LSA (type 10): The opaque LSA carries the TE information.
l Neighbor: When running the OSPF protocol, the OptiX PTN equipment sends the Hello
packets through the OSPF interface. When receiving the Hello packets, the OptiX PTN
equipment checks the related parameters defined in the packets for consistency. If the
related parameters are consistent, the neighborhood is established.
l Adjacency: The neighborhood does not necessarily ensure the adjacency. The network type
determines when the adjacency can be established. Two OptiX PTN systems can establish
the adjacency only after they successfully exchange the DD packets and LSA.
l Router ID: A router ID is a 32-bit value that uniquely identifies an OptiX PTN equipment
in an AS. A router ID is important for the OptiX PTN equipment to run the OSPF protocol.
l OSPF TE: The OSPF TE supports the creation of the label switching paths (LSPs) for TE.
Before building LSPs, the MPLS protocol has to know the traffic information of all links
in the area. The MPLS protocol obtains the TE information of the links through the OSPF
protocol.
OSPF Route Computation

The OSPF protocol computes routes in the following way:
1. Each OptiX PTN equipment generates the LSA based on the surrounding network topology
and sends the LSA to other systems on the network through the DD packets, LSR packets,
or LSU packets.
2. Each OptiX PTN equipment collects the LSAs sent by the adjacent systems. The collection
of LSAs is referred to an LSDB. The OptiX PTN equipment can obtain the topology of the
entire network from the LSDB. The LSDB is the same for the OptiX PTN equipment of
the PTN network.
NOTE
The LSA describes the surrounding topology of the OptiX PTN equipment and the LSDB describes
the network topology of the entire AS.
3. According to the LSDB, each OptiX PTN equipment computes a shortest path tree that is
rooted at itself by using the shortest path first (SPF) algorithm. The tree defines the routes
to each node in the AS.

OSPF Area
The OSPF protocol logically divides the OptiX PTN systems into areas, which are identified by
area IDs. Each interface where the OSPF protocol runs must belong to an area.
The OptiX PTN equipment supports the OSPF backbone area, which is responsible for inter-
area routing information. Backbone areas should be interconnected.
OSPF Router Classification

According to the positions in the AS, the OptiX PTN systems can be classified as follows:
l Internal router, IR: All interfaces on an internal router belong to one OSPF area.
l Backbone router: A backbone router must have one interface or more that belong to a
backbone area. Hence, all the routers in the backbone areas are backbone routers.
l Autonomous System Border Routers, ASBR: The OptiX PTN equipment that exchanges
the routing information with other ASs is referred to as ASBR. An ASBR may not be located
at the border of an AS. The OptiX PTN equipment that introduces the external routing
information is an ASBR.
OSPF Network Classification

According to the link-layer protocol types, the OSPF classifies networks as follows:
l Broadcast network: When Ethernet is used as the link-layer protocol, the OSPF considers
the network as a broadcast network by default.
l Point-to-point network: When PPP is used as the link-layer protocol, the OSPF considers
the network as a point-to-point network by default.
5.5 RIP
The OptiX PTN 3900 supports the routing information protocol (RIP). On the client side, the
OptiX PTN 3900 obtains the routing information and discovers routes by running the RIP.
The RIP is an internal gateway protocol (IGP). Based on the distance-vector algorithm, the RIP
uses the hop count to indicate the distance to the destination. The RIP is applicable to small-
scale networks.
The RIP supported by the OptiX PTN 3900 complies with the RFC 2453 (RIP Version 2).
Basic Concepts
The basic concepts related to the RIP supported by the OptiX PTN 3900 include the hop count,
RIP message, RIP routing database, and RIP timer.
l Hop count: The RIP uses the hop count to measure the distance to the destination. The hop
count is also referred to as metric. As defined in the RIP, if the OptiX PTN equipment is
directly connected to a network, the hop count is 0; if the OptiX PTN equipment is
connected to a network through one set of equipment, the hop count is 1. The hop count
can be determined by analog. To limit the convergence time, the RIP defines that the metric
should be an integer in the range of 0 to 15. If the hop count is 16 or more, the RIP defines
the metric as infinite. That is, the RIP considers the destination as unreachable.
l RIP messages: The RIP switches the routing information on the basis of user datagram
protocol (UDP) messages by using the RIP packets. The RIP protocol defines two types of

messages, that is, request messages and response messages. The request messages are sent
to request the neighbors to send all or part of the routing information and the response
messages send all or part of the local routing information.
l RIP routing database: One set of the OptiX PTN equipment that runs the RIP manages one
RIP routing database, which contains the route entries to all the reachable destinations on
the network. The key route entries are as follows:
– Destination address, which is the IP address of the host or network.
– Next-hop address, which is the IP address of the interface on the adjacent equipment
that the RIP packets have to traverse to reach the destination.
– Interface, which forwards packets.
– Metric, which indicates the distance from the OptiX PTN equipment to the destination
and is an integer in the range of 0 to 15.
– Routing time, which indicates the period from the last time when the route entries are
modified to the present time. When the route entries are modified, the routing time is
reset to 0.
– Route flag, which distinguishes the routes of the internal routing protocol from the routes
of the external routing protocol.
l RIP timer, which controls the RIP. There are three types of RIP timers, that is, Update,
Age, and Garbage-Collect.
– Update time: During the update time, the OptiX PTN equipment periodically transmits
the update packets.
– Age time: If the OptiX PTN equipment fails to receive the update packets from one of
its neighbors when the age time expires, the OptiX PTN equipment considers the route
to the neighbor as unreachable.
– Garbage-Collect time: If the OptiX PTN equipment fails to receive the update packets
from one of its neighbors during the garbage-collect time, the OptiX PTN equipment
deletes the route to the neighbor from the route table.
Working Process of the RIP

The RIP receives the routing information from other equipment on the network and thus
maintains the local IP-layer route table. In this manner, the IP-layer packets can be transmitted
along the correct routes. In addition, the RIP broadcasts the routing information of the local
OptiX PTN equipment to inform the neighbor equipment of route changes.
When processing the RIP, the OptiX PTN equipment mainly processes the RIP packets and RIP
routes.
l The OptiX PTN equipment processes the RIP packets as follows:

1. When the RIP starts running, the initial route table contains the routing information
of only the directly-connected interfaces on the local OptiX PTN equipment.
2. When running the RIP, the OptiX PTN equipment sends the request messages to its
neighbors.
3. When receiving the request messages, the neighbor equipment responds to the request
and returns the response messages, which contain the information about the local route
table. The neighbor equipment also computes routes.
4. When receiving the response messages from its neighbors, the OptiX PTN equipment
modifies the local route table.

l The OptiX PTN equipment processes the RIP routes as follows:

– When receiving the response messages, the OptiX PTN equipment modifies the route
table, sends the messages to trigger updates on its neighbors that send the response
messages, and broadcasts the route updates. When receiving the route updates, the
neighbor equipment sends the messages to trigger updates to its neighbors. When the
broadcast is complete, each set of equipment triggers updates and maintains the latest
routing information.
– The RIP adopts the aging mechanism to process the timeout routes and to ensure the
validity of routes. Hence, the RIP periodically sends the local route table to its neighbors.
When receiving the routing information, the neighbor equipment updates the local
routing information. The equipment that runs the RIP repeats this process without
exception.
5.6 MPLS Signaling

The MPLS signaling used by the OptiX PTN 3900 includes LSP signaling and PW signaling.
The LSP signaling is responsible for distributing LSP labels and the PW signaling is responsible
for distributing PW labels to establish PW.
LSP Signaling
The OptiX PTN 3900 uses the RSVP-TE protocol as the LSP signaling.
At first, the RSVP protocol is used to reserve resources for certain services. In this way, the QoS
can be guaranteed. As TE comes up lately, the RSVP protocol is extended to create LSP. In this
way, TE is more easily realized.
The RSVP-TE protocol used by the OptiX PTN 3900 has the following functions.
l Supports various messages and objects of standard RSVP-TE protocol.
l Supports shared-explicit (SE) style to reserve resources. For the SE style, resources are
reserved for a group of transmitters, which share the reserved resources.
l Supports refreshing, fast re-transmission and confirmation of the software status.
PW Signaling
The OptiX PTN 3900 uses the label distribution protocol (LDP) as the PW signaling.
The LDP is a control and signaling protocol for the MPLS.
The LDP protocol used by the OptiX PTN 3900 has the following functions.
l Supports extension of the LDP protocol by the PWE3.
l Supports the extended neighbor discovery mechanism.
l Supports the label distributing scheme of the downstream on demand.
l Supports the ordered label control scheme.
l Supports the liberal retention mode.
5.7 PWE3
The pseudo wire emulation edge-to-edge (PWE3) technology is used to provide tunnels on the
packet switching network (IP/MPLS) to emulate the Layer 2 VPN protocol for some services,

such as the TDM, ATM and Ethernet services. The emulated VPN protocol is used to connect
the traditional network and packet switching network. In this way, networks are extended and
resources can be shared.
Basic Concept
The PWE3 is an end-to-end Layer 2 service carrying technology, and belongs to point-to-point
L2VPN. In the two provider edges (PEs) of a network, the LDP is used as the signaling and
tunnels are used to emulate various Layer 2 services at the customer edge (CE), such as the Layer
2 data packets and bit flow. In this way, the Layer 2 data at the CE end are transparently
transmitted in the network.
The PWE3 is used to create point-to-point channels, which are isolated from each other. The
Layer 2 packets from users are transparently transmitted among PWs. For PE equipment, the
mapping relation between user access interfaces and PWs is determined after the PW connection
is set up. For P equipment, MPLS packets are forwarded according to the MPLS labels. The
Layer 2 user packets encapsulated in the MPLS packets are not processed.
Typical Application
The PWE3 is used to integrate the original access schemes with the existing IP backbone
networks. In this way, repeated network construction is reduced and the OpEx is saved.
Figure 5-3 Typical application of the PWE3
BSC
E1, STM-1 interface

FE RNC
EMS
ATM, GE interface
PWE3
PWE3
PWE3
IMA E1, FE interface
E1 interface
BTS
NodeB
5.8 IP Tunnel and GRE Tunnel

The OptiX PTN 3900 can use the IP tunnel or GRE tunnel to carry the ATM PWE3 service,
CES PWE3 service and ETH PWE3 service. In this way, ATM emulation services and ETH
emulation services can be transparently transmitted in an IP network.
Take ATM emulation services as an example.

In an MPLS network that consists of the PTN equipment, the PWE3 technology is used to provide
the ATM emulation services. Figure 5-4 shows how the ATM emulation services are
encapsulated.
Figure 5-4 ATM PWE3 over MPLS tunnel
ATM ATM
PTN PTN
switch switch
MPLS
network
ATM ATM ATM

E1/STM-1 PWE3 E1/STM-1
PW Label
MPLS Label
Ethernet
If an ATM emulation service that travels through an IP network is required, the OptiX PTN
3900 can use the IP tunnel or GRE tunnel to carry the ATM PWE3. This complies with RFC
4023. As shown in Figure 5-5 and Figure 5-6, an ATM emulation service can be provided
between NE A and NE B, even though the IP network between NE A and NE B does not support
the MPLS.
Figure 5-5 ATM PWE3 over IP tunnel
ATM ATM
PTN Router Router PTN
switch switch
IP
ne two rk
ATM ATM ATM ATM

E1/STM-1 PWE3 PWE3 E1/STM-1
PW Label PW Label
IP IP
Ethernet Ethernet

Figure 5-6 ATM PWE3 over GRE tunnel
ATM ATM
PTN Router Router PTN
switch switch
IP
ne two rk
ATM ATM ATM ATM

E1/STM-1 PWE3 PWE3 E1/STM-1
PW Label PW Label
GRE GRE
IP IP
Ethernet Ethernet
NOTE
DCN packets can be transparently transported over the IP tunnel or GRE tunnel. When the DCN packets
pass through a third-party network, the DCN packets are transported in an end-to-end manner.
5.9 QoS
The equipment supports DiffServ based on the standard, including flow classification, flow
policing, traffic shaping, congestion management and queue scheduling.
The equipment realizes the eight groups of pre-hop behavior (PHB) stipulated in the standard.
The eight PHB groups are BE, AF1, AF2, AF3, AF4, EF, CS6 and CS7. With the equipment,
the vendors can provide services of different quality classes for users. In this way, an integrated
network emerges to carry data, voice and video services at the same time.
QoS in the DiffServ Mode

One DiffServ region may contain several types of packets, including VLAN packets and MPLS
packets. To provide a good class of service (CoS) for various packets, at the edge of the DiffServ
region, the ingress equipment maps the DSCP/EXP/VLAN Pri/S-VLAN dei+pcp into the CoS
and the egress equipment maps the CoS into the EXP/VLAN Pri/S-VLAN dei+pcp.
One DiffServ region may contain several types of packets, including VLAN packets, MPLS
packets and IP packets. Hence, in actual application, the priority of which layer to be mapped
into the forwarding class should be specified.
The Layer 2 packets include customer VLAN (C-VLAN) packets and service VLAN (S-VLAN)
packets. The Layer 3 packets include MPLS packets and IP packets. By default, the equipment
maps the forwarding class according to the priorities of Layer 2 packets.
Flow Classification
The flow classification indicates that data packets are classified into several priorities or service
classes. For example, if the first six bits of the DSCP type of service (ToS) field are used for the
flow classification, the flow can be classified into a maximum of 64 classes. After the flow is
classified, other QoS features then can be used for different classes. In this way, the class-based
congestion management and traffic shaping are realized.
The equipment supports the simple flow classification and the complex flow classification.

Simple flow classification:
In the simple flow classification, the priorities of external packets and the priorities of internal
packets are mapped to each other, according to the DSCP values of IP packets, the EXP values
of MPLS packets, and the Pri values of VLAN packets.
Equipment support for the simple flow classification:
The equipment supports the simple flow classification for S-VLAN packets, C-VLAN packets,
IP packets, and MPLS packets. The simple flow classification is performed at an Ethernet port
or at a POS port.
Purpose of the simple flow classification:
The simple flow classification is effective for an internal node in a DS region. In a DS region,
the simple flow classification rules are the same for all nodes. The simple flow classification
maps the original priorities of packets in the network to the internal priorities of the equipment,
so that the packets can be transmitted inside the equipment according to the preset priorities.
Compared with the complex flow classification, the simple flow classification features a simplex
classification form and easy configuration. In this case, the QoS configuration for each node in
a DS region is simplified.
Complex flow classification:
In the complex flow classification, packets are classified according to relatively complex rules.
The processing actions include the ACL, the CAR, and the setting of CoS.
Equipment support for the complex flow classification:
The equipment supports the complex flow classification for S-VLAN packets, C-VLAN packets,
and IP packets. The complex flow classification is performed at an Ethernet port.
Purpose of the complex flow classification:
In the complex flow classification, packets are classified according to complex rules. Further
processing, including the ACL, the CAR, and the setting of grooming class, is also conducted
for the flow bandwidth and for the flow forwarding. The complex flow classification features
flexible and diversified classification forms. In this case, the user can classify accessed services
based on the QoS in a more specific manner.
CAR
The committed access rate (CAR) is a method used to limit the rate of accessed packets according
to the four preset parameters of the token bucket. The purpose of CAR is to mark accessed
packets with colors (or label the packets), and to limit the rate of accessed packets.
The CAR provides the following two key functions.
l Labeling: Realized by color marking and re-labeling.

l Traffic rate limiting: Realized by the specific action taken on the packets after they are
marked with colors.
There are two color marking modes: color-blind and color-aware. In both modes, the current
rate of packets is compared with the committed information rate (CIR) and peak information
rate (PIR) of the token bucket. The packets that exceed the PIR are marked in red. The packets
that exceed the CIR but are within the PIR are marked in yellow. The packets that are within the
CIR are marked in green. The difference is that, in the color-aware mode, if the packets

themselves have a color, their own color is compared with the color that should be marked and
then the deeper color is used.
Traffic rate limiting determines whether to discard some colored packets, and thus limits the
access rate of the traffic.
The default rule is that the red packets are discarded and the yellow and green packets are allowed
to pass. The actions can also be manually set for the three-color packets.
NOTE
The token bucket is a technology used to realize the CAR functions. In IETF Recommendations, the single
rate three color marker (srTCM) or two rate three color marker (trTCM) algorithm is used to assess packets.
According to the assessment result, the packets are marked with colors and labeled with different discarding
priorities. The PTN equipment adopts the trTCM algorithm.
Queue Scheduling
Packets are sent to queues of different grooming priorities by using different flow classification
methods. After the flow classification, the equipment adopts a PQ + WFQ + SPL (that is, priority
queuing + weighted fair queuing + Strict Priority-low) method to groom the queues. The PQ
method is adopted to groom the CS7, CS6, and EF packets. The WFQ method is adopted to
groom the AF packets. The lowest priority is adopted to groom the BE packets.
Congestion Management
In the case of a congestion, the equipment discards packets by using the tail-drop method and
the weighted random early detect (WRED) method. The network congestion can be alleviated
by using these discarding methods.
In the tail-drop method, a buffer queue is used to buffer the packets, and the packet discarding
priorities are not distinguished during the buffering. When the buffer queue is full, packets that
come thereafter are discarded.
In the WRED method, the discarding priorities (that is, colors) of packets can be detected.
According to the discarding priorities, the upper threshold, lower threshold, and probability are
set for the purposes of packet discarding. In this case, different discarding characteristics are
provided.
Traffic Shaping
The purpose of traffic shaping is to limit the traffic burst of outgoing packets of a network, and
thus to transmit the packets out at a relatively even rate. In this way, congestion is prevented on
the downstream equipment, and fewer packets are discarded. The equipment adopts the generic
traffic shaping (GTS) algorithm.
HQoS
The hierarchical QoS (HQoS) is a QoS technology that can both control the service traffic and
groom services according to their priorities. With the complete traffic statistics functions
provided by the HQoS, the network administrator can supervise the bandwidth occupied by each
type of service, and reasonably allocate the bandwidth for services by analyzing the traffic.
The traditional QoS grooms traffic on a port basis, but cannot groom traffic on a multiple-user
and multiple-service basis. The HQoS, however, provides the multilevel grooming mode. In this
mode, the HQoS provides differentiated QoSs for multiple services of multiple users.

Compared with the traditional QoS, the HQoS has the following advantages:
l The multilevel grooming mechanism provides rich service capabilities.
l Parameters such as the maximum queue length and the WRED can be configured for a flow
queue.
l The CIR and PIR can be configured for each user.
The HQoS can be reflected as the hierarchical service grooming. Based on the HQoS, a network
carrier can provide further classified service guarantees.
The HQoS function is implemented on the equipment at the network edge. The purpose of such
an implementation is to maintain a simple core network. In this case, not every piece of
equipment in the network is required to conduct the complex QoS processing. At the network
edge, the HQoS is implemented as seven levels of grooming: V-UNI+CoS, V-UNI, V-UNI
group, PW+CoS, PW, Tunnel, and port+CoS. Table 5-3 lists the action points of the HQoS.
Table 5-3 HQoS action points at the access side and the network side of the equipment
Action In the Ingress Direction In the Egress Direction
Point
At the V-UNI+CoS, V-UNI, and V-UNI V-UNI+CoS, V-UNI, V-UNI group,

access side group and port+CoS
At the PW+CoS, Tunnel, and PW Tunnel, and port+CoS

network
side
The HQoS support for accessed services is described as follows.

l The one-level CAR is supported for each service. The color marking is supported for
packets.
l The three-level (V-UNI+CoS, PW+CoS, and Port+CoS) grooming is supported for each
service. Eight queues are supported for each level of grooming. The shaping and WRED
functions are supported for the queues. Three of the eight queues are low-delay queues,
and the other five are non-low-delay queues.
l For each service, the ingress NE supports up to four levels of bandwidth limitation, and the
egress NE also supports up to four levels of bandwidth limitation.
5.10 IGMP Snooping

The Internet group management protocol (IGMP) Snooping function is used to realize multicast
distribution.
The IGMP Snooping function is helpful in the following aspects.
l The network bandwidth is saved.
l Each VLAN is independently forwarded. Hence, the information security is increased.
The OptiX PTN 3900 supports the following L2 IGMP Snooping functions.
l The L2 IGMP Snooping function complies with RFC4541. The L2 IGMP Snooping can
analyze and process the IGMPv1 and IGMPv2 protocol packets. When the IGMP Snooping

protocol is enabled and IGMPv3 protocol packets are received, the equipment forwards the
packets to all other ports in the VLAN of the packets, except the port receiving the packets.
l The L2 IGMP Snooping only applies to the E-LAN service rather than other types of
services.
l The equipment supports the setting of the aging time of the router port.
l The equipment supports the setting of maximum non-response times.
l The equipment supports the setting of the allowed multicast groups for use and the
maximum number of their members.
l The equipment supports addition of static router ports and member ports.
l The equipment supports the setting of the quick deletion function on the member port.
NOTE
For the static member, the quick deletion function cannot be set.
5.11 MSTP/RSTP/STP
The multiple spanning tree protocol (MSTP) is compatible with the spanning tree protocol (STP)
and rapid spanning tree protocol (RSTP). In addition, the MSTP rectifies the defects of the STP
and RSTP. The MSTP supports fast reconfiguration and provides multiple paths for forwarding
data. During the data forwarding process, the VLAN data is of load balance. The MSTP complies
with IEEE 802.1s.
The MSTP divides a switching network into several domains. In each domain, several spanning
trees are formed and are independent from each other. Each spanning tree is called a multiple
spanning tree instance (MSTI) and each domain is called a multiple spanning tree (MST) domain.
The MSTP sets the VLAN mapping table, which specifies the mapping relation between VLAN
and MSTI, to connect the VLAN and MSTI.
Table 5-4 lists the comparison among the MSTP, STP and RSTP.
Table 5-4 Comparison among the MSTP, STP and RSTP
Spanning Feature Remarks

Tree
Protocol
STP A spanning tree not of a loop is l The MSTP and RSTP are
formed to prevent multicast storm and compatible, and they can recognize
provide redundant backup. protocol packets of each other.
l The STP does not recognize the
RSTP l A spanning tree not of a loop is
MSTP packets. To be compatible
formed to prevent multicast storm
with the STP, the MSTP sets two
and provide redundant backup.
working modes, which are STP-
l Fast reconfiguration. compatible mode and MSTP mode.
In the STP-compatible mode, each
port of the equipment transmits
STP packets. In the MSTP mode,
each port of the equipment
transmits MSTP packets and has
the MST functions.

Spanning Feature Remarks

Tree
Protocol
MSTP l A spanning tree not of a loop is l Generally, if a switch running the

formed to prevent multicast storm STP is present in a switching
and provide redundant backup. network, the port of the equipment
l Fast reconfiguration. connected to the STP switch
automatically migrates from the
l Multiple spanning trees realize MSTP mode to the STP-
load balance among VLANs. compatible mode.
VLANs of different traffic volume
l If the switch running the STP is
are forwarded to different paths.
removed from the network, the port
cannot automatically migrate from
the STP-compatible mode back to
the MSTP mode.
The OptiX PTN 3900 supports the following key MSTP specifications.
l MSTP topology aggregation time: In the case of a link failure, the aggregation time is less
than 1s if the conditions are present for P/A mechanism and is equal to 2 x (Forward Delay
Time) if the conditions do not exist for P/A mechanism.
l Each MST domain supports a maximum of 16 MSTIs.
l Each port group supports a maximum of 16 Ethernet ports.
l On the equipment that supports the MSTP, load balance is realized by setting the path cost
and port priority for different VLANs.
– Ports in different spanning tree instances have different path cost. Proper path cost
makes the traffic of different VLANs forwarded along different physical links. In this
way, load balance is realized.
– In different spanning tree instances, one ports is of different priorities. In this way, one
port plays different roles in different MSTIs. As a result, the traffic of different VLANs
are transmitted along different physical links. Hence, load balance is realized.
5.12 ACL
To filter data packets, the access control list (ACL) can be used to stipulate a series rules in order.
The equipment classifies the received data packets according to the ACL rules and then forwards
or discards these packets.
The ACL is just a group of rules and cannot filter data packets. Instead, the ACL marks a class
of data packets. How to process these packets, however, depends on the specific functions that
introduce the ACL. For the OptiX PTN 3900, the ACL should be used with the flow classification
function to filter data packets. Figure 5-7 shows the details. The flow classification should be
created before the creation of ACL. The equipment supports self-defined ACL. The maximum
number of ACLs supported by the OptiX PTN 3900 is 8k.

Figure 5-7 ACL based on flow classification
Network A
Flow ID=2
Disable
GE
Internet
GE
Enable
Flow ID=1
Network B
5.13 BFD
The OptiX PTN 3900 supports the bidirectional forwarding detection (BFD) function. The Hello
mechanism is used to detect states of Ethernet links.
The BFD is a simple Hello protocol, which is similar to the neighbor detection mechanism of
the routing protocol in many aspects. A pair of systems periodically transmit the detection
packets in the channels where inter-system talk is established. If a system does not receive any
detection packets in a certain time from the opposite end, it is determined that some part of the
bidirectional channel connected to adjacent nodes is faulty.
The OptiX PTN 3900 adopts the asynchronous mode to perform BFD detection for Ethernet
links. In the asynchronous mode, the equipment at both ends of a link periodically transmits the
BFD control packets to each other. If the equipment does not receive any BFD control packets
in a long time from the opposite end, it is determined that the Ethernet link is faulty.
The OptiX PTN 3900 performs BFD at intervals of 1 second.
5.14 Synchronous Ethernet Clock

The OptiX PTN 3900 realizes the synchronous Ethernet clock on the Physical layer.
Synchronous Ethernet Clock

The synchronous Ethernet clock refers to a technology that achieves clock synchronization on
the physical layer of Ethernet and thus is similar to the SDH clock. The synchronization process
of the synchronous Ethernet clock is as follows:
l The devices such as the primary reference clock (PRC) transfer clock signals to the NE
through the external clock interface.
l NEs transfer the clock signals through the synchronous Ethernet among them.

l The clock processing module of each NE extracts the clock signals from the serial bit stream
on the Ethernet line and selects a clock source.
l The clock phase-locked loop traces one of the Ethernet line clocks and generates the system
clock.
l The system clock is used as the transmit clock on the physical layer of Ethernet to transport
data. In this way, the clock is transferred to the downstream.
NOTE
To achieve the synchronous Ethernet clock, each NE that the synchronization information traverses should
support the synchronous Ethernet technology.
The synchronous Ethernet clock has the following features:

l The synchronous Ethernet clock is easy to realize and is highly reliable.
l The synchronous Ethernet clock adopts the synchronization status information (SSM) to
indicate clock quality and exclusive OAM packets to transfer the SSM.
Typical Networking
The OptiX PTN equipment constitutes a synchronous Ethernet, supports the synchronous
Ethernet interfaces and realizes synchronization on the physical layer of Ethernet. Figure 5-8
shows the typical networking for synchronous Ethernet.
Figure 5-8 Typical networking for synchronous Ethernet
RNC
NodeB clock PRC

signal
BTS
BSC
OptiX PTN 3900

GE
FE
OptiX PTN 1900
In a synchronous Ethernet, the clock information from devices such as PRC is distributed to the
OptiX PTN equipment that is connected to the base transceiver station (BTS) or WCDMA base
station (NodeB). Then, the OptiX PTN equipment extracts and transfers the clock signals to the

BTS or NodeB, base station controller (BSC), and radio network controller (RNC) through
synchronous Ethernet interfaces. In this way, the synchronous Ethernet clock is realized.
5.15 IEEE 1588 V2 Clock

The OptiX PTN 3900 supports the function of adopting the IEEE 1588 V2 protocol to realize
clock synchronization and time synchronization.
As a precision time protocol (PTP), the IEEE 1588 V2 protocol achieves the nanosecond-class
precision, which meets the requirement of 3G base stations.
NOTE
To achieve IEEE 1588 V2 clock synchronization, all NEs on the clock link should support the IEEE 1588
V2 protocol.
In the application of networking, the IEEE 1588 V2 clock can achieve the 1 microsecond precision.
BMC Algorithm
The best master clock (BMC) algorithm compares data describing two clocks to determine which
data describes the better clock, and selects the better clock as the clock source. The BMC
algorithm includes the following algorithms:
l Data set comparison algorithm: The NE determines which of the clocks is better, and selects
the better clock as the clock source. If an NE receives two or more channels of clock signals
from the same grandmaster clock (GMC), the NE selects one channel of the clock signals
that traverses the least number of nodes as the clock source.
l State decision algorithm: The state decision algorithm determines the next state of the port
based on the results of the data set comparison algorithm.
Clock Architecture
Figure 5-9 shows the architecture of the IEEE 1588 V2 clock.
Figure 5-9 Architecture of the IEEE 1588 V2 clock
OC1
GMC
TC1
1
BC1 BC1
2 3 1 2 3
TC2+OC2 TC3
OC3 OC4 OC5

The OptiX PTN 3900 supports four models for the IEEE 1588 V2 clock architecture.
l Ordinary clock (OC): A clock that has a single IEEE 1588 V2 port and the clock needs to
be recovered. It may serve as a source of time, i.e. be a master clock, or may synchronize
to another clock, i.e. be a slave clock.
l Boundary clock (BC): A clock that has multiple IEEE 1588 V2 ports and the clock needs
to be recovered. It may serve as the source of time, i.e. be a master clock, and may
synchronize to another clock, i.e. be a slave clock.
l Transparent clock (TC): A device that measures the time taken for a PTP event message
to transit the device and provides this information to clocks receiving this PTP event
message. That is, the clock device functions as an intermediate clock device to transparently
transmit the clock and process the delay, but does not recover the clock.
– End-to-end TC: A transparent clock that supports the use of the end-to-end delay
measurement mechanism between slave clocks and the master clock.
– Peer-to-peer TC: A transparent clock that supports the use of the peer-to-peer delay
measurement mechanism.
l TC+OC: A clock device corrects and transparently transmits the time stamps for the IEEE
1588 V2 packets, and realizes clock synchronization.
NOTE
l The end-to-end TC and peer-to-peer TC adopt different mechanisms to realize delay transmission, and
do not interwork on the same communication path. That is, the adjacent TC devices on the same time
path can adopt either the end-to-end TC or peer-to-peer TC, but they cannot adopt both at the same
time.
l Time Stamp (TS) is used to convey time information.
l PTP event messages are timed messages in that an accurate TS is generated both at transmission and
receipt.
Typical Networking
By using the IEEE 1588 V2 protocol, the OptiX PTN equipment can transfer the precise time
information to achieve clock synchronization and time synchronization for equipment in the
network. This meets the requirement of the telecommunications network for precise time. Figure
5-10 shows the typical networking for IEEE 1588 V2 clock synchronization.

Figure 5-10 Typical networking for IEEE 1588 V2 clock synchronization

GMC
PRC
BC RNC
BC/TC/TC+OC
NE1
BC/TC/TC+OC
BC/TC/TC+OC
BC/TC/TC+OC
BC/TC/TC+OC/OC
NodeB
Master clock transfer trail

OptiX PTN 3900
Slave clock transfer trail
OptiX PTN 1900

GE/10GE/STM-N
FE
Clock signals
In Figure 5-10, the PRC transfers clock signals to NE1 and RNC, which selects the PRC as the
GMC according to the BMC algorithm. In this case, the PRC is of the OC model and only works
as the clock source. NE1 is of the BC model, in the case of the connected PRC, NE1 is the clock
sink, in the case of the other connected OptiX PTN equipment, NE1 is a clock source. NE1
transmits IEEE 1588 V2 packets to the other OptiX PTN equipment, which transfers the packets
downstream. In this case, the other OptiX PTN equipment works in the BC, TC, TC+OC or OC
mode.
If only one clock source is available for the network, the OptiX PTN equipment can work in
BC, TC, or TC+OC mode to realize the following functions:
l In the BC mode, the OptiX PTN equipment selects the time source, recovers the system
time of the local NE, and adopts the system time as the new time source to transmit the
time information downstream. When the intermediate NEs require time synchronization,
this mode is applicable.

l In the TC mode, the OptiX PTN equipment updates and transparently transmits the time
stamps of the IEEE 1588 V2 packets, and transfers the time information downstream. When
the intermediate NEs do not require clock or time synchronization, this mode is applicable.
l In the TC+OC mode, the OptiX PTN equipment realizes the following functions:
– Updates and transparently transmits the time stamps of the IEEE 1588 V2 packets, and
transfers the time information downstream.
– Synchronizes the clock (not the time) for the local NE.
When the intermediate NEs require clock synchronization, this mode is applicable.
l In the OC mode, the OptiX PTN equipment selects the time source and recovers the system
time of the local NE. In addition, the OptiX PTN equipment adopts the system time as the
new time source, and transmits the time information downstream through the external time
interface. When the intermediate NEs are connected to the NodeB, this mode is applicable.
If multiple clock domains are in the network, the OptiX PTN equipment can work in the TC or
TC+OC mode.
l In the case of different GMCs, the IEEE 1588 V2 packets must be transferred through
different ports.
NOTE
The BC mode is not applicable to this case, because the NE in the BC mode synchronizes itself with one
channel of clock signals, which is selected as a clock source from the clock signals and is transferred
downstream. One of the clock sources is transferred downstream and the other clock signals are terminated.
NodeB receives time information from the external time interface of the OptiX PTN equipment,
and synchronizes the time with RNC.

Product Description 6 Protection
6 Protection
About This Chapter
6.1 Equipment Level Protection

The equipment level protection includes the 1+1 protection for the system control, TPS
protection, communication and auxiliary processing board (SCA), the 1+1 protection for the
cross-connect and timing board (XCS), the 1+1 protection for the power supply, and the
protection for fans.
6.2 Network Level Protection
The network level protection includes the MPLS Tunnel 1+1 and 1:1 protection, the LMSP
protection, the FRR protection, the Ethernet LAG protection, the spanning tree protection, the
packet E1 ML-PPP protection and the IMA protection.

6 Protection Product Description
6.1 Equipment Level Protection

The equipment level protection includes the 1+1 protection for the system control, TPS
protection, communication and auxiliary processing board (SCA), the 1+1 protection for the
cross-connect and timing board (XCS), the 1+1 protection for the power supply, and the
protection for fans.
6.1.1 TPS Protection

The TPS protection scheme protects the MP1 board and the E1 service sub-board on it. When
an MP1 board or the service sub-board on it has a hardware failure, the signal flow from the
interface board is switched, by software and hardware operations, to a normal MP1 board that
is specially used for protection. In this way, the faulty service sub-board is protected. The TPS
protection scheme is able to protect E1 physical links. The OptiX PTN 3900 supports a maximum
of two groups of 1: N (N≤4) TPS protection.
6.1.2 1+1 Protection for the SCA Board
The 1+1 protection for the SCA board is provided when two SCA boards are installed on the
equipment. When the software or hardware of the working SCA is faulty, or when the working
and protection SCAs receive a switching command, the SCA working/protection switching
occurs. In this way, the protection for the SCA is realized.
6.1.3 1+1 Protection for the Cross-Connect and Timing Board
The 1+1 protection for the cross-connect and timing board is provided when the equipment is
installed with two cross-connect and timing boards. When the software or hardware of the
working board is faulty, or when the working and protection boards receive a switching
command, the working/protection switching occurs. In this way, the protection for the cross-
connect and timing board is realized.
6.1.4 1+1 Protection for the PIU
Two power interface units (PIU) that provide hot backup for each other are installed on the
equipment. When one PIU fails, the equipment can still function properly.
6.1.1 TPS Protection

The TPS protection scheme protects the MP1 board and the E1 service sub-board on it. When
an MP1 board or the service sub-board on it has a hardware failure, the signal flow from the
interface board is switched, by software and hardware operations, to a normal MP1 board that
is specially used for protection. In this way, the faulty service sub-board is protected. The TPS
protection scheme is able to protect E1 physical links. The OptiX PTN 3900 supports a maximum
of two groups of 1: N (N≤4) TPS protection.
Protection Schemes and Supported Boards

The equipment supports TPS protection for E1 physical links. Table 6-1 lists the TPS protection
schemes and supported boards.
Table 6-1 E1 TPS protection schemes and supported boards

Protection Scheme Supported Boards
Two 1:N (N≤4) protection groups MD1+MP1, MQ1+MP1

Table 6-2 lists the mapping relations between working and protection slots in TPS protection.
Table 6-2 Mapping relations between working and protection slots in TPS protection
Working Slot Protection Slot Interface Board Slot
Slots 1, 2, 3, and 4 Slot 5 Slots 19-26
Slots 15, 16, 17, and 18 Slot 14 Slots 31-38
TPS Protection Parameters

Table 6-3 lists the TPS protection parameters.
Table 6-3 TPS protection parameters

Parameter Description
Priority 0-3, among which 0 is the highest priority.
Switching type Lock/unlock, forced switching, manual switching,

automatic switching.
Switching condition Any of the following conditions triggers the switching:

l The clock of the working board is lost.
l The working board is offline.
l The working board is in a cold reset.
l The working board has a hardware failure.
l A switching command is issued.
Switching time In the case of TPS switching, the restoration time for the E1
physical link is less than 50 ms.
Revertive mode Revertive.
WTR time 300s to 720s. A WTR time of 600s is recommended.
6.1.2 1+1 Protection for the SCA Board

The 1+1 protection for the SCA board is provided when two SCA boards are installed on the
equipment. When the software or hardware of the working SCA is faulty, or when the working
and protection SCAs receive a switching command, the SCA working/protection switching
occurs. In this way, the protection for the SCA is realized.
On the OptiX PTN 3900, the valid slots for the SCA are slots 29 and 30.
Table 6-4 lists the SCA 1+1 protection parameters of the OptiX PTN 3900.

Table 6-4 1+1 protection parameters of the SCA board

Slots for boards Slots 29 and 30.

l The working board has a failure.
l A switching command is manually issued.
l The working board is removed.
l Both ejector levers on the front panel of the working board
are rotated to the open position
l The working board is in a warm reset.
Revertive mode Non-revertive
6.1.3 1+1 Protection for the Cross-Connect and Timing Board

The 1+1 protection for the cross-connect and timing board is provided when the equipment is
installed with two cross-connect and timing boards. When the software or hardware of the
working board is faulty, or when the working and protection boards receive a switching
command, the working/protection switching occurs. In this way, the protection for the cross-
connect and timing board is realized.
The cross-connect and timing board for the OptiX PTN 3900 is the XCS, valid slots of which
are slots 9 and 10.
Table 6-5 lists the 1+1 protection parameters of the cross-connect and timing board.
Table 6-5 1+1 protection parameters of the cross-connect and timing board
Slots for boards Slot 9 and slot 10

l The working board has a failure.
l The working board is removed.
l Both ejector levers on the front panel of the working board
are rotated to the open position
Revertive mode Non-revertive

6.1.4 1+1 Protection for the PIU

Two power interface units (PIU) that provide hot backup for each other are installed on the
equipment. When one PIU fails, the equipment can still function properly.
The PIU accesses -48 V or -60 V power supply for the OptiX PTN 3900. The PIU boards are
installed in slot 27 and slot 28. The two PIU boards provide hot backup for each other.
6.2 Network Level Protection

The network level protection includes the MPLS Tunnel 1+1 and 1:1 protection, the LMSP
protection, the FRR protection, the Ethernet LAG protection, the spanning tree protection, the
packet E1 ML-PPP protection and the IMA protection.
6.2.1 MPLS 1+1 and 1:1 Protection

In the MPLS 1+1 and 1:1 protection, the protection path protects the service that is transported
in the working path. When the working path is faulty, the service is switched to the protection
path. The 1+1 protection adopts the dual fed and selective receiving mechanism, and the 1:1
protection adopts the single fed and single receiving mechanism.
6.2.2 FRR Protection
Fast reroute (FRR) is a feature of MPLS, and provides fast local protection. FRR is usually
deployed in a network that requires high reliability. When a local failure occurs in the network,
FRR is able to quickly switch the services to a bypass tunnel. In this case, the impact on data
services is very small.
6.2.3 Ethernet LAG Protection
Link aggregation means that a group of physical Ethernet ports with the same bit rate are bundled
together to form a logical port (LAG). In this way, link aggregation increases the bandwidth and
provides link protection. OptiX PTN 3900 supports LAG protection for the Ethernet UNI ports.
6.2.4 Ethernet Spanning Tree Protection
The multiple spanning tree protocol (MSTP) can be used to prevent a loop. Using an algorithm,
the MSTP blocks redundant paths so that the loop network can be trimmed as a tree network. In
this case, the proliferation and endless cycling of packets, which can cause a broadcast storm,
is prevented in the loop network. The major difference between the MSTP and STP/RSTP
protocols is that the MSTP protocol can forward data based on VLAN ID and thus realizes the
load balancing.
6.2.5 LMSP Protection
In the LMSP protection, the protection path protects the service that is transported in the working
path. When the working path is faulty, the service is switched to the protection path. The LMSP
protection includes the 1+1 LMSP, 1:1 LMSP and 1:N (2≤N≤7) LMSP. The 1+1 protection
adopts the dual fed and selective receiving mechanism, and the 1:1/1:N protection adopts the
single fed and single receiving mechanism. These protection schemes are mainly used for the
channelized STM-1 port, the ATM STM-1 port and the POS port. The 1:N LMSP is supported
by the AFO1 board.
6.2.6 Packet E1 ML-PPP Protection
Multilink PPP (ML-PPP) indicates that several PPP channels are bundled to increase the
bandwidth, to share the loading and to provide backup. ML-PPP protection indicates that the
services at the network side can be transmitted in bundled PPP channels. In this way, the load
of the board ports at the network side can be shared and protected.
6.2.7 IMA Protection

Inverse multiplexing for ATM (IMA) demultiplexes a concentrated flow of ATM cells into
multiple lower-rate links, and at the remote end multiplexes these lower-rate links to recover as
the same sequence as the original concentrated flow of ATM cells. In this way, multiple lower-
rate links are flexibly and conveniently multiplexed.
6.2.1 MPLS 1+1 and 1:1 Protection

In the MPLS 1+1 and 1:1 protection, the protection path protects the service that is transported
in the working path. When the working path is faulty, the service is switched to the protection
path. The 1+1 protection adopts the dual fed and selective receiving mechanism, and the 1:1
protection adopts the single fed and single receiving mechanism.
In the MPLS protection, the extended APS protocol information is transported through the
protection path. The equipment at the two ends exchanges the protocol state information and the
switching state information. According to the protocol state and switching state, the equipment
at the two ends performs the service switching.
The MPLS protection complies with ITU-T G.8131.
MPLS 1+1 Protection

Figure 6-1 shows the MPLS 1+1 protection supported by the equipment.
Figure 6-1 MPLS 1+1 protection

Service detection point
Service detection point
Working path
Subnetwork
Processing board Processing board
Access Cross-connect Cross-connect Access

Protection path/
protocol path
Subnetwork
The MPLS 1+1 protection adopts the dual fed and selective receiving mechanism for services.
When the working path is faulty, the receive end selects the service from the protection path. In
this way, the service switching is realized.
l Detection method:
– Physical layer check: At the physical layer, the loss of signal is detected in
microseconds.
– Link layer check: The link layer check is performed through the MPLS OAM. If the
MPLS OAM check time is 3.3 ms, it ensures that the MPLS automatic switching time
is less than 50 ms.
l Switching process: The receive end selects the service channel according to the link status.

MPLS 1:1 Protection
Figure 6-2 shows the MPLS 1:1 protection supported by the equipment.
Figure 6-2 MPLS 1:1 protection

Service detection point Service detection point
Working path
Subnetwork
Subnetwork
Protection path
Protocol path
In the MPLS 1:1 protection, the accessed service is transported in the working path. When the
working path is faulty, the service is switched to the protection path. The single fed and single
receiving mechanism is used for the service. The extended APS protocol information is
transported through the protection path. The equipment at the two ends exchanges the protocol
state information and the switching state information. According to the protocol state and
switching state, the equipment at the two ends performs the service switching.
l Detection method:
– Physical layer check: At the physical layer, the loss of signal is detected in
microseconds.
– Link layer check: The link layer check is performed through the MPLS OAM. If the
MPLS OAM check time is 3.3 ms, it ensures that the MPLS automatic switching time
is less than 50 ms.
l Switching process: After a negotiation using the extended APS protocol, the transmit end
switches the service to the protection path, and the receive end selects the service from the
protection path.
Protection Parameters
Table 6-6 lists the parameters of the MPLS 1+1 and 1:1 protection.
Table 6-6 MPLS 1+1 and 1:1 protection parameters
Switching Revertive Switching Switching Switching Default WTR

Type Mode Protocol Time Delay Time Time
1+1 single- Non- Extended ≤ 50 ms 0s to 10s (0s by -

ended revertive APS default)
switching


1+1 dual- Non- Extended ≤ 50 ms 0s to 10s (0 by -

switching
1+1 single- Revertive Extended ≤ 50 ms 0s to 10s (0 by 300s

ended APS default)
switching
1+1 dual- Revertive Extended ≤ 50 ms 0s to 10s (0 by 300s

ended APS default)
switching
1:1 dual- Non- Extended ≤ 50 ms 0s to 10s (0 by -

switching
1:1 dual- Revertive Extended ≤ 50 ms 0s to 10s (0 by 300s

ended APS default)
switching
Any of the following conditions triggers the switching:

l The board has a failure.
l The board is in a cold reset.
l The physical link is faulty.
l LSP fault is detected by MPLS OAM.
6.2.2 FRR Protection

Fast reroute (FRR) is a feature of MPLS, and provides fast local protection. FRR is usually
deployed in a network that requires high reliability. When a local failure occurs in the network,
FRR is able to quickly switch the services to a bypass tunnel. In this case, the impact on data
services is very small.
Basic Concepts of FRR

The basic concepts of FRR are described as follows.
l Detour mode: Refers to one-to-one backup. In the detour mode, LSPs are protected
separately, that is, one protection LSP is specially created for each protected LSP. This
protection LSP is called a detour LSP.
l Bypass mode: Refers to facility backup. In the bypass mode, one protection LSP is used to
protect multiple LSPs. This protection LSP is called a bypass LSP.
l PLR: Refers to point of local repair. The PLR is the ingress node of a detour LSP or bypass
LSP. The PLR must be on the route of the working LSP, and cannot be the egress node of
the working LSP.

l MP: Refers to merge point. The MP is the egress node of a detour LSP or bypass LSP. The
MP must be on the working LSP, and cannot be the ingress node.
l Link protection: In link protection, a direct link connection exists between the PLR and the
MP, and the working LSP passes through this link. When this link fails, the services can
be switched to a detour LSP or bypass LSP.
l Node protection: In node protection, the PLR and the MP are connected through an
intermediate node, and the working tunnel passes through this node. When this node fails,
the services can be switched to a detour LSP or bypass LSP.
FRR protection complies with RFC 4090.
FRR Protection Principle

FRR provides protection for links or nodes that are between the PLR and the MP, and connected
to the PLR. The basic principle of FRR protection is to use a preconfigured tunnel to protect one
or multiple tunnels. The equipment supports the bypass mode.
A bypass tunnel refers to a non-FRR-protected tunnel that is designated to protect other tunnels
which pass through a certain physical interface. A bypass tunnel is triggered by manual
configuration at the PLR. The configuration of a bypass tunnel is similar to that of a common
tunnel. The only difference is that the bypass tunnel cannot be configured with the FRR attribute.
That is, embedded protection is not allowed for a tunnel.
Service restoration time: Less than 50 ms
Figure 6-3 shows the FRR protection.
Figure 6-3 FRR protection

C
D E
B
A
MP
PLR
In Figure 6-3, the working tunnel is marked in blue, and the bypass tunnel is marked in red.
FRR protects the B-C link and node C, which are connected to the PLR. When link B-C or node
C fails, the data on the working tunnel is switched to the bypass tunnel. After the switching, the
original path information between the PLR and the MP is deleted.

6.2.3 Ethernet LAG Protection

Link aggregation means that a group of physical Ethernet ports with the same bit rate are bundled
together to form a logical port (LAG). In this way, link aggregation increases the bandwidth and
provides link protection. OptiX PTN 3900 supports LAG protection for the Ethernet UNI ports.
The Ethernet LAG protection can realize the load sharing and the non load sharing among ports.
In this case, the bundled links are not distinguished by the working and protection attributes.
The system provides inter-board and intra-board LAG protection. When any link is faulty, the
service packets are transported to other links.
Figure 6-4 shows the Ethernet LAG protection supported by the equipment.
Figure 6-4 Ethernet LAG protection

Intra-board LAG Inter-board LAG
protection protection
Ethernet board ... Ethernet board
Ethernet board Ethernet board

...
Link aggregation has the following advantages:

l The link bandwidth is increased.
l The link reliability is improved. When a link is invalid, other links share the services.
l Load sharing is provided. The links in a link aggregation group (LAG) share the load.
The equipment supports the following two link aggregation modes:

l Manual aggregation
l Static aggregation
For failed links, the equipment supports the following revertive modes:
l Revertive
l Non-revertive
The equipment supports the following sharing modes:

l Load sharing
l Non load sharing
The equipment supports the priority setting for the ports in an LAG.

The equipment supports the inter-board and intra-board LAG protection.
Manual Aggregation
The manual bundling of ports does not require the link aggregation control protocol (LACP),
and does not require the exchange of protocol packets. In manual aggregation, the aggregation
of ports is manually specified by the administrator.
On the OptiX PTN 3900, multiple physical Ethernet ports can be bundled as one logical port.
With the port bundling technology, the transmission bandwidth between two equipment can be
increased without a hardware expansion, and the link reliability is also improved.
After the setting of an LAG, the equipment automatically enables the load sharing among the
physical ports that are bundled as a logical port. When one physical port fails, and if the load
sharing is enabled, the traffic on the faulty port is automatically shared by other physical ports.
When the faulty port recovers, the traffic is reallocated to ensure that the load is shared among
all ports.
After the setting of an LAG, if the non loading sharing mode is adopted, only one member link
has traffic and the other member links are in the standby state. In fact, this provides a hot standby
scheme. When the active member link fails, the system activates one of the standby member
links to shield the link failure.
Static Aggregation
The static aggregation of links requires the LACP protocol. In static aggregation, the automatic
maintenance of aggregated ports is realized through the exchange of protocol packets. The
administrator, however, is still responsible for creating an LAG and adding member links into
the LAG. Furthermore, the LACP protocol cannot change the configuration information of the
administrator.
The OptiX PTN 3900 supports the LACP protocol that complies with IEEE 802.3ad. By
exchanging LACP packets, two interconnected equipment negotiate which ports can be used to
forward data, and thus determine whether an egress port is in the selected or standby state.
The LACP protocol maintains the link state according to the port state. When aggregation
conditions change, the link aggregation is automatically adjusted or dismantled. Among the
member links of an LAG, the load sharing or non load sharing modes can function based on
ports, MAC addresses, IP addresses, or MPLS labels.
6.2.4 Ethernet Spanning Tree Protection

The multiple spanning tree protocol (MSTP) can be used to prevent a loop. Using an algorithm,
the MSTP blocks redundant paths so that the loop network can be trimmed as a tree network. In
this case, the proliferation and endless cycling of packets, which can cause a broadcast storm,
is prevented in the loop network. The major difference between the MSTP and STP/RSTP
protocols is that the MSTP protocol can forward data based on VLAN ID and thus realizes the
load balancing.
The MSTP supported by the equipment is compliant with IEEE 802.1s, and is compatible with
the STP and RSTP. For the difference between the MSTP and the STP/RSTP, see Table 5-4.
The MSTP adopts the concepts of region and instance. The MSTP divides a switching network
into different regions as required. Multiple independent spanning trees are generated in each
region. Each spanning tree is referred to as a multiple spanning tree instance (MSTI), and each
region is referred to as an MST region. The MSTP determines the mapping relations between

VLANs and MSTIs by setting a VLAN mapping table (that is, a VLAN and MSTI mapping
relation table). Each instance is mapped to one VLAN or a group of VLANs.
NOTE
l Instance: Equipment that runs the MSTP may have multiple spanning trees at the same time. Each
spanning tree is referred to as a multiple spanning tree instance. In this way, these spanning trees can
be distinguished.
l Region: A region refers to a group of interconnected switching equipment that have the same VLAN-
to-instance mapping relations.
Bridge protocol data units (BPDUs) that carry region and instance information are transmitted
among equipment. According to the BPDU information, the equipment determines whether it
belongs to a specific region. Several spanning tree instances can be run within a region, and only
one spanning tree can be run among regions.
Figure 6-5 shows a switching network that has multiple VLANs.
Figure 6-5 Switching network with multiple VLANs

NE1 ROOT
10, 20, 30 10, 20
NE2 ROOT 20, 30 NE5
10, 30 10, 30
30 20
NE3 NE4
10
ROOT
After the MSTP begins running, each VLAN has an independent MST. See Figure 6-6.

Figure 6-6 Network topology after the MSTP begins running

NE1 ROOT NE1
ROOT
NE2 NE5 NE2 NE5
NE3 NE4 NE3 NE4
VLAN 10 NE1 VLAN 20
NE2 NE5
NE3 ROOT NE4
VLAN 30
As each instance is mapped to one VLAN or a group of VLANs, the MSTP can forward data
based on VLAN packets and thus realizes the load balancing for VLAN data. In this case, a
perfect integration of the RSTP and VLAN is achieved.
6.2.5 LMSP Protection

In the LMSP protection, the protection path protects the service that is transported in the working
path. When the working path is faulty, the service is switched to the protection path. The LMSP
protection includes the 1+1 LMSP, 1:1 LMSP and 1:N (2≤N≤7) LMSP. The 1+1 protection
adopts the dual fed and selective receiving mechanism, and the 1:1/1:N protection adopts the
single fed and single receiving mechanism. These protection schemes are mainly used for the
channelized STM-1 port, the ATM STM-1 port and the POS port. The 1:N LMSP is supported
by the AFO1 board.
LMSP 1+1 Protection

Figure 6-7 shows the LMSP 1+1 protection supported by the equipment.

Figure 6-7 LMSP 1+1 protection

Working path
Cross-connect Cross-connect
Protection path
The LMSP 1+1 protection adopts the dual fed and selective receiving mechanism for services.
When the working path is faulty, the receive end selects the service from the protection path. In
this way, the service switching is realized.
l Detection method: The LOS alarm, LOF alarm, MS_AIS alarm, or B2_SD, B2_EXC are
detected at the physical layer.
l Switching process: The receive end selects the service according to the line state.
LMSP 1:1/1:N Protection

Figure 6-8 shows the LMSP 1:1/1:N protection supported by the equipment.

Figure 6-8 LMSP 1:1/1:N protection

Working path
Cross-connect Cross-connect
Protection path
In the LMSP 1:1/1:N protection, the service is transported in the working path. When the working
path is faulty, the service is switched to the protection path. The single fed and single receiving
mechanism is used for the service. The APS protocol information is transported through the
protection path. The equipment at the two ends exchanges the protocol state information and the
switching state information. According to the protocol state and switching state, the equipment
at the two ends performs the service switching.
l Detection method: The LOS alarm, LOF alarm, MS_AIS alarm, or B2_SD, B2_EXC are
detected at the physical layer.
l Switching process: After a negotiation using the APS protocol, the transmit end switches
the service to the protection path, and the receive end selects the service from the protection
path.
Protection Parameters
Table 6-7 lists the parameters of the LMSP protection.

Table 6-7 LMSP protection parameters

1+1 single- Non- Not ≤ 50 ms 0s to 10s (0s by -

ended revertive required default)
switching
1+1 dual- Non- APS ≤ 50 ms 0s to 10s (0s by -

ended revertive default)
switching
1+1 single- Revertive Not ≤ 50 ms 0s to 10s (0s by 300s

ended required default)
switching
1+1 dual- Revertive APS ≤ 50 ms 0s to 10s (0s by 300s

ended default)
switching
1:1 dual- Revertive APS ≤ 50 ms 0s to 10s (0s by 300s

ended default)
switching
1:N dual- Revertive APS ≤ 50 ms 0s to 10s (0s by 300s

ended default)
switching
Any of the following conditions triggers the switching:

l The board has a failure.
l The board is in a cold reset.
l The physical link is faulty.
6.2.6 Packet E1 ML-PPP Protection

Multilink PPP (ML-PPP) indicates that several PPP channels are bundled to increase the
bandwidth, to share the loading and to provide backup. ML-PPP protection indicates that the
services at the network side can be transmitted in bundled PPP channels. In this way, the load
of the board ports at the network side can be shared and protected.
Figure 6-9 shows the packet E1 ML-PPP protection.

Figure 6-9 Packet E1 ML-PPP protection

Link
..
Processing board . Processing board
Link
After the service signals are accessed, the cross-connect board cross-connects the signals to the
processing board, which uses the allocated bundled links to transmit the signals. In this way, the
load of board ports at the network side is shared and protected. The links all share the service
load and no one is standby.
ML-PPP is a intra-board protection scheme. If any link fails, the service load is shared by other
links for transmission.
l Detection method:
– At the physical layer, the loss of signal and the AIS, RDI state are detected in
microseconds.
– At the link layer, the detection is performed by the ML-PPP protocol in milliseconds.
l Switching process: The receive end selects the service according to the link state.
6.2.7 IMA Protection

Inverse multiplexing for ATM (IMA) demultiplexes a concentrated flow of ATM cells into
multiple lower-rate links, and at the remote end multiplexes these lower-rate links to recover as
the same sequence as the original concentrated flow of ATM cells. In this way, multiple lower-
rate links are flexibly and conveniently multiplexed.
IMA is applicable for transmitting ATM cells through E1 ports and channelized VC12 links.
IMA provides a path for ATM cells, but does not process the service types or ATM cells. Hence,
IMA transparently transmit signals of the ATM layer and a higher layer. Figure 6-10 shows the
IMA transmission.
Figure 6-10 IMA transmission
Link 1
Link 2
ATM cell flow Link 3 ATM cell flow
IMA group

In the case of the IMA protection, cells are distributed to other normal links for transport if one
link in the IMA group fails. In this case, services are protected.

Product Description 7 Operation, Administration and Maintenance
7 Operation, Administration and Maintenance
About This Chapter
The OptiX PTN 3900 provides powerful functions of operation, administration and maintenance.
7.1 OAM Capability

The boards and functions of the OptiX PTN 3900 are designed according to customer
requirements for operation and maintenance. Hence, the equipment provides powerful
maintenance capabilities.
7.2 T2000 Network Management System
The T2000 is used to manage the OptiX PTN 3900.

7 Operation, Administration and Maintenance Product Description
7.1 OAM Capability

The boards and functions of the OptiX PTN 3900 are designed according to customer
requirements for operation and maintenance. Hence, the equipment provides powerful
maintenance capabilities.
7.1.1 Operation and Configuration Tools

Users can use the OptiX iManager T2000 to operate and configure the OptiX PTN 3900.
7.1.2 Monitoring and Maintenance
The OptiX PTN 3900 supports several monitoring and maintenance functions.
7.1.3 Diagnosis and Debugging
The OptiX PTN 3900 provides the function of diagnosis and debugging of the system hardware
and software faults.
7.1.4 Expansion and Upgrade
The OptiX PTN 3900 supports capacity expansion by adding new boards or replacing boards,
and provides several upgrade schemes.
7.1.1 Operation and Configuration Tools

Users can use the OptiX iManager T2000 to operate and configure the OptiX PTN 3900.
T2000: Users can use the OptiX iManager T2000 transport network management system (T2000
for short) to perform network level configuration, especially service configuration. The T2000
supports software package loading and collection of information on faults. For details on the
T2000, refer to 7.2 T2000 Network Management System.
7.1.2 Monitoring and Maintenance

The OptiX PTN 3900 supports several monitoring and maintenance functions.
The OptiX PTN 3900 supports the following monitoring and maintenance functions.
l Each board has running status and alarm indicators, which are used for the network
administrator to locate and handle faults in time.
l The equipment provides functions such as alarm management and alarm filtering.
l The equipment supports automatic laser shutdown. (The Ethernet interface does not support
this function.)
l The equipment supports software upgrade without affecting services.
l The equipment supports in-service backup and loading of the database.
l The equipment supports restoration of the system configuration from the database.
l The equipment supports MPLS OAM and Ethernet OAM.
l The equipment supports the non-stop forwarding (NSF) function.
l The equipment supports inband management DCN.
l The T2000 can be used to dynamically monitor the running status, alarms and performance
of each NE in the network.

l The equipment supports package loading and remote loading of the board software and NE
software, and provides functions of anti-mistake loading and resuming interrupted file
transfer.
7.1.3 Diagnosis and Debugging

The OptiX PTN 3900 provides the function of diagnosis and debugging of the system hardware
and software faults.
The OptiX PTN 3900 uses the following network connectivity test schemes to provide the
diagnosis and debugging functions.
l MPLS layer connectivity test scheme:
– LSP Ping
– PW CVVC Ping
– TraceRoute
– MPLS OAM
l ETH layer connectivity test scheme:
– Loopback (LB) test
– Link trace (LT) test
– Continuity check (CC)
7.1.4 Expansion and Upgrade

The OptiX PTN 3900 supports capacity expansion by adding new boards or replacing boards,
and provides several upgrade schemes.
The OptiX PTN 3900 supports insertion of new boards and replacement of boards for expansion.
For the upgrade of the OptiX PTN 3900, working and protection SCA boards should be used.
The working/protection backup ensures that no services are interrupted during the upgrade.
If the XCS boards are of working/protection backup when the board software is upgraded,
services are generally not interrupted or only interrupted for less than 50 ms. After one service
board is replaced, as required, with another service board of the same type, the new board
automatically copies the service configuration of the replaced board. Hence, service
reconfiguration is not necessary.
The OptiX PTN 3900 supports anti-mistake software loading and version rollback in the case
of upgrade failure. The upgrade process is reversible.
NOTE
Rollback indicates that the original software version and service configuration can be recovered in the case
of upgrade failure. The new software covers the original software only after the upgrade succeeds.
7.2 T2000 Network Management System

The T2000 is used to manage the OptiX PTN 3900.
In compliance with ITU-T Recommendations, the T2000 applies the standard management
information model and object-oriented management technology. The T2000 exchanges
information with the NE software through the communication module, to implement monitoring
and management over the network equipment.

7 Operation, Administration and Maintenance Product Description
The T2000 software runs on a workstation or a PC. The T2000 enables the user not only to
operate and maintain transmission equipment, but also to manage the transmission network. The
T2000 software has the following management functions.
Alarm and Performance Management

The T2000 realizes the following alarm management functions: real-time collection, prompting,
filtering, browsing, acknowledgement, check, clearing, counting, alarm insertion, alarm
correlation analysis, and fault diagnosis.
l Automatically reports alarms and performs alarm consistency check.
l Checks and deletes alarms.
l Clears and filters current or history alarms of an NE, and filters abnormal performance
events.
l Stores the alarm data.
Configuration Management
The configuration management function enables users to configure and manage interfaces,
clock, services, tunnels, protection and NE time.
l Creates or deletes network entities.
l Creates or changes fibers.
l Sets or modifies NE attributes, and delivers configuration.
l Configures interface attributes.
l Configures tunnels and protection.
l Configures OAM.
l Configures services.
l Configures clock sources.
l Uploads configuration data or checks data consistency.
l Checks NE information.
Maintenance Management
For the maintenance management, several schemes are provided to help maintenance personnel
to locate and clear equipment faults.
l Sets loopback.
l Sets the NE timing synchronization scheme.
l Resets boards or NE software.
l Sets automatic laser shutdown. (The Ethernet interface does not support this function.)
l Starts performance monitoring.
l Backs up the NE database.
Security Management
The T2000 can use several schemes to manage the NE security.

l NE user management.
l NE login management.
l NE login lockout.
l NE setting lockout.
l NE user group management.
l NE security parameters.
l NE security log.

Product Description 8 Security Management
8 Security Management
About This Chapter
The T2000 uses many schemes to manage the security of the OptiX PTN 3900 NE. The NE
security management takes effect on the basis of the reasonable planning.
8.1 Authentication Management
Considering the security, only the legal user can log in to the NE after authentication.
8.2 Authorization Management
Proper authority assignment to different NE users can ensure the successful operations
performed by each user and the security of the NE system.
8.3 Network Security Management
Safe data transmission between the T2000 and NEs is the prerequisite for the T2000 to effectively
manage the NEs.
8.4 System Security Management
Considering the security, the system provides some security policies, which must be executed
forcibly.
8.5 NE Security Log Management
The NE security logs record the operations performed by all the NE users and the operation
results. By querying these logs, the administrator can trace and review the operations.
8.6 Syslog Management
The system log service (Syslog service) is used for the security management on an NE. For
unified control by maintenance engineers, all types of information are transmitted to the log
server in the format complying with the system log (Syslog) protocol.

8 Security Management Product Description
8.1 Authentication Management

Considering the security, only the legal user can log in to the NE after authentication.
l NE login management: You can successfully log in to the NE only by entering a valid user
name and a valid password.
l NE user switching: On a client, only one user is allowed to operate the NE each time. For
this reason, if multiple users intend to operate the same NE simultaneously, they need to
be switched to ensure that the data is unique.
l Forcibly making other users exit from the NE: To avoid errors caused by simultaneous
configuration by multiple users, or to prevent other users from illegally logging in to the
NE, one user can forcibly make other users who are at lower level exit from the NE.
l NE login locking: After the locking function is enabled, a user whose level is lower than
that of the current user is not allowed to log in to the NE.
l NE setting locking: You can lock the settings of functional modules of the NE to prevent
other users from operating the locked modules.
l Query the online NE users.
8.2 Authorization Management

Proper authority assignment to different NE users can ensure the successful operations
performed by each user and the security of the NE system.
l NE user management:
– According to the operation authorities, NE users are divided into five levels, which
involve monitoring level, operation level, maintenance level, system level, and
debugging level in an ascending order.
– According to the T2000, NE users are classified into LCT NE users, EMS NE users,
CMD NE users, and general NE users.
– Create NE users, assign authorities, or specify a user flag.
– Modify the user name, change the password, modify the operation authority, or change
the user flag.
– Delete NE users.
l NE user group management:
– According to the operation authority, by default, NE user groups are divided into
administrator group, super administrator group, operator group, monitoring personnel
group, and maintenance personnel group.
– Modify the group of a user.
8.3 Network Security Management

Safe data transmission between the T2000 and NEs is the prerequisite for the T2000 to effectively
manage the NEs.
l Set the ACL rule to filter the received IP packets, control the data traffic in the network,
and to avoid malicious attack. According to the system security level, the ACL rule is
divided into basic ACL and advanced ACL.

Product Description 8 Security Management
– For an NE that requires lower security level, you can set the basic ACL rule only to
check the source address of the IP packets.
– For an NE that requires higher security level, you can set the advanced ACL rule. In
this case, the NE checks the source address, sink address, source port, sink port, and
protocol type of the received IP packets.
– If both the advanced and the basic ACL rules are available, the NE adopts the advanced
ACL rule to check the packets.
– Query the ACL rule.
– Modify the ACL rule.
– Delete the ACL rule.
l An NE can access the T2000 by using any of the following methods:
– Access over the Ethernet port (ETH port and EXT port). By default, an NE connects to
the T2000 over the Ethernet port.
– Access through the serial interface.
l Control the access to NEs by using LCT: If the T2000-LCT needs to be used to manage
NEs, you can enable the LCT access authority allowed by the NE on the T2000.
l When the T2000 communicates with an NE, confidential data (such as user name and
password) is encrypted.
8.4 System Security Management

Considering the security, the system provides some security policies, which must be executed
forcibly.
l Query or set the Warning Screen information of the NE.
l Query and set the Warning Screen switch of the NE to decide whether to report an alarm
after a user logs in to the NE.
l Query or set the earliest expiry time and the latest expiry time of the password.
l Query or set the maximum number of illegal login attempts.
l Query or set the maximum number of overdue password attempts.
l Query or set the password uniqueness.
8.5 NE Security Log Management

The NE security logs record the operations performed by all the NE users and the operation
results. By querying these logs, the administrator can trace and review the operations.
l Query the security logs of the NE.
l Set forwarding NE logs to the Syslog Server.
8.6 Syslog Management

The system log service (Syslog service) is used for the security management on an NE. For
unified control by maintenance engineers, all types of information are transmitted to the log
server in the format complying with the system log (Syslog) protocol.
The OptiX PTN 3900 supports:

8 Security Management Product Description
l Enabling and disabling of Syslog protocol

l Setting of Syslog protocol transmit modes: UDP (by default) and TCP
l Adding and deletion of Syslog servers
l Coexisting of multiple Syslog servers and the sending of logs to multiple servers at the
same time
l Reporting of alarms upon the communication disconnection between the Syslog server and
the NE
Figure 8-1 shows how the Syslog protocol is transmitted in a network. To ensure the security
of system logs, make sure that at least two system log servers are available in a network.
Normally, IP protocol is used for the communication between the NE and the system log servers.
The communication between NEs can be realized through several methods, for example, ECC
mode or IP over DCC mode.
Figure 8-1 Schematic diagram of Syslog protocol transmitting

NE B
NE A
(client) NE C
NMS (client)
TCP/IP DCN
Syslog server B
Real time
security log
NE D
Syslog server A
NOTE
Normally, a system log server is a workstation or server that is dedicated to storing the system logs of all
NEs in a network.
A forwarding gateway NE receives the system logs of other NEs and forwards the logs to the system log
server. In Figure 8-1, NE A and NE C are forwarding gateway NEs.
When IP protocol is adopted on each NE for communication, every NE can directly communicate
with the two system log servers through the IP protocol. Hence, configure the IP addresses and
port numbers on the NE, and the system is able to transmit the NE logs to the two Syslog servers
through the auto addressing function of IP protocol. No forwarding gateway NE is required.
When DCN mode is adopted on each NE for communication, the NE that does not directly
connect to the Syslog servers cannot communicate with the servers. The logs of the NE must be
transmitted to a gateway NE that directly communicates with the Syslog servers through DCN.
Then, the logs are forwarded to the Syslog servers by the gateway NE. Hence, the forwarding
gateway NE must be configured, for example, configure NE A as the forwarding gateway NE
for NE D.

Product Description 9 Networking Application
9 Networking Application
About This Chapter
The OptiX PTN 3900 is used at the convergence and backbone layers of the MAN. The
equipment can transport various services and carry WDM services at the convergence and
backbone layers of the MAN. The equipment can be used to transport mobile services, private
line services and broadband services.
9.1 Application of the Equipment for Mobile Services

The OptiX PTN 3900 is used at the radio access network (RAN) layer of the mobile network.
In other words, the OptiX PTN 3900 is used in the transport network between base stations and
base station controllers.
9.2 Application of the OptiX PTN 3900 for the L2VPN Service
The OptiX PTN 3900 can transport E-Line services and E-LAN services. The L2VPN supports
fast service delivery, end-to-end OAM, and reliable protection.
9.3 Offload Solution
During service transmission between the NodeB and RNC for 3G mobile communication, the
PTN equipment can divert the high speed downlink packet access (HSDPA) service from the
services. The HSDPA service then can be carried by a low-cost network that accesses and
forwards packets, such as an ADSL network. In this way, the transmission cost is reduced and
the competitiveness of operators is enhanced.

9 Networking Application Product Description
9.1 Application of the Equipment for Mobile Services

The OptiX PTN 3900 is used at the radio access network (RAN) layer of the mobile network.
In other words, the OptiX PTN 3900 is used in the transport network between base stations and
base station controllers.
The OptiX PTN 3900 provides several types of interfaces (Ethernet, POS, ATM, channelized
STM-1, and E1) to access and carry packet services. Besides, the equipment uses the native
TDM scheme to carry TDM E1 and ATM E1 services at the base station side. Table 9-1 shows
the application of the OptiX PTN 3900 for the mobile service.
Table 9-1 Application of the OptiX PTN 3900 for the mobile service
Item Description
Service Figure 9-1 shows how Figure 9-2 shows Figure 9-3 shows how
accessing to access the E1 services how to access the to access the FE
from base transceiver IMA E1 services services from base
stations (BTS). from base stations. stations.
Application Packet mode

mode
Networking Tree, ring, mesh Tree, ring, mesh Tree, ring, mesh
scheme
Service type Channelized E1, IMA E1, ATM FE, GE

Fractional E1, STM-1 STM-1
Networking GE, 10GE, ML-PPP E1, GE, 10GE, ML-PPP GE, 10GE
interface POS E1, POS
Protection MPLS Tunnel 1+1/1:1, FRR, LMSP

Item Description
Service scenario l Transport of CES l At the access l The Ethernet

(PWE3) E1 point, the IMA E1 services from FE
emulation service group is interfaces are
l Emulation of E1 terminated and converged to GE/
services, which are PWE3 emulation 10GE interfaces on
placed into the is performed to the the basis of Layer 2
channelized STM-1 ATM services in switching or
at the convergence the group. VLAN.
point and then l At the l When Layer 2
transported to the convergence switching is used
base station point, the for convergence of
controller (BSC). equipment services from FE
encapsulates the interfaces to GE/
ATM services 10GE interfaces,
emulated in the services between
PWE3 scheme base stations are
into non- isolated.
channelized
STM-1, and then
transmits them to
the radio network
controller (RNC).
NOTE
Channelized E1: The same service is configured for the 32 timeslots of an E1 signal.
Fractional E1: Different services are configured for the 32 timeslots of an E1 signal.

Figure 9-1 Networking application of the OptiX PTN 3900 for transport of mobile services (E1
service between the base station and equipment)
E1 GE/POS/
GE/POS/ ML-PPP
ML-PPP
STM-1
E1
GE/POS/ GE/POS/
ML-PPP ML-PPP
GE/POS/
ML-PPP
GE/POS/ STM-1
ML-PPP
E1
OptiX PTN 3900 BTS
OptiX PTN 1900 BSC

Figure 9-2 Networking application of the OptiX PTN 3900 for transport of mobile services
(IMA E1 service between the base station and equipment)
IMA E1 GE/POS/
GE/POS/ ML-PPP
ML-PPP
IMA E1
IMA E1
GE/POS/ GE/POS/
ML-PPP ML-PPP
GE/POS/
ML-PPP
GE/POS/ ATM STM-1
ML-PPP
IMA E1
OptiX PTN 3900

NodeB
OptiX PTN 1900 RNC

Figure 9-3 Networking application of the OptiX PTN 3900 for transport of mobile services (FE
service between the base station and equipment)
FE GE/POS/ GE/POS/
ML-PPP ML-PPP
GE
FE
GE/POS/ GE/POS/
ML-PPP ML-PPP
GE/POS/
ML-PPP
GE/POS/ FE
ML-PPP
FE
OptiX PTN 3900 NodeB
OptiX PTN 1900 RNC
9.2 Application of the OptiX PTN 3900 for the L2VPN

Service
The OptiX PTN 3900 can transport E-Line services and E-LAN services. The L2VPN supports
fast service delivery, end-to-end OAM, and reliable protection.
9.2.1 Transport of the E-Line Service

The OptiX PTN 3900 provides the L2 E-Line service.
9.2.2 Transport of the E-LAN Service
The OptiX PTN 3900 provides the L2 E-LAN service.
9.2.1 Transport of the E-Line Service

The OptiX PTN 3900 provides the L2 E-Line service.
As shown in Figure 9-4, the OptiX PTN 3900 provides the E-Line service.

Figure 9-4 Networking Application of the E-Line Service
FE
GE
E-Line
Protection Path
OptiX PTN 3900
OptiX PTN 1900
CE
Table 9-2 Application of the OptiX PTN 3900 for the E-Line service
Item Description
Application mode Packet service
Networking Chain, mesh

scheme
Service type 10GE, GE, FE
Networking 10GE, GE
interface
Protection l MPLS Tunnel 1+1/1:1 protection

l MPLS FRR/RR protection
l LAG protection for UNI ports
l TE function supported by interconnecting MPLS tunnels at the
network side
Service scenario l The PTN equipment provides the E-Line service. The equipment
accesses user services from GE or FE interfaces and then
transparently transmits these services. In addition, the equipment
provides DiffServ/HQoS service.
l The equipment supports the traffic statistics counting based on port
or service (PW, Tunnel).
l The equipment provides the Ethernet OAM function (IEEE 802.1ag,
IEEE 802.3ah) and MPLS OAM function (ITU-T Y.1711).
9.2.2 Transport of the E-LAN Service

The OptiX PTN 3900 provides the L2 E-LAN service.
As shown in Figure 9-5, the OptiX PTN 3900 provides the E-LAN service.

Figure 9-5 Networking Application of the E-LAN Service
FE
GE
E-LAN
OptiX PTN 3900
OptiX PTN 1900
CE
Table 9-3 Application of the OptiX PTN 3900 for the E-LAN service
Item Description
Application Packet service

mode
Networking Mesh
scheme
Service type 10GE, GE, FE
Networking 10GE, GE
interface
Protection l MPLS Tunnel 1+1/1:1 protection

l MPLS FRR/RR protection
l LAG protection for UNI ports
l TE function provided by interconnecting MPLS tunnels at the network
side

Item Description
Service l The equipment provides E-LAN services, services stipulated in L2VPN/

scenario IEEE 802.1ad/IEEE 802.1ah, and DiffServ/HQoS service.
l The equipment supports the traffic statistics counting based on port or
service (PW, Tunnel).
l The equipment provides the Ethernet OAM function (IEEE 802.1ag,
IEEE 802.3ah) and MPLS-OAM function (ITU-T Y.1711).
l The equipment supports interconnection to the user STP/RSTP/MSTP.
l The equipment supports L2 multicast, and L2 broadcast suppression.
l The equipment supports isolation of user data.
l The equipment supports ACL, DOS-attack prevention and access
authentication.
9.3 Offload Solution

During service transmission between the NodeB and RNC for 3G mobile communication, the
PTN equipment can divert the high speed downlink packet access (HSDPA) service from the
services. The HSDPA service then can be carried by a low-cost network that accesses and
forwards packets, such as an ADSL network. In this way, the transmission cost is reduced and
the competitiveness of operators is enhanced.
Overview of the Offload Solution

The HSDPA technology greatly increases the data service rate for 3G mobile communication.
In addition, Iub interfaces (the interfaces between the NodeB and the RNC) require more and
more transmission bandwidth. To reduce the transmission cost and ensure the QoS of important
services, the PTN equipment provides a complete offload solution.
As shown in Figure 9-6, the services sent by the NodeB are accessed to the OptiX PTN 1900
at the access node, through the IMA E1. The OptiX PTN 3900 at the convergence node, is
connected to the RNC through the ATM STM-1 interface. The service flow at Iub interfaces can
be classified into the signaling flow, R99 flow and HSDPA flow by VPI/VCI.
l The OptiX PTN 1900 at the access node uses the IMA E1 to transport the signaling flow
and R99 flow to the OptiX PTN 3900 at the convergence node.
l The OptiX PTN 1900 at the access node encapsulates the HSDPA flow and sends the
encapsulated flow to the ADSL modem through an FE interface. The flow then travels
through the ADSL network and finally arrives at the OptiX PTN 3900 at the convergence
node.
According to the forwarding schemes used by the ADSL network, the offload solution can be
used on the following three scenarios.
l ATM-forwarding-based ADSL network
l ETH-forwarding-based ADSL network
l IP-forwarding-based ADSL network

Figure 9-6 Offload solution
HSDPA Wholesale ADSL network

flow
R99 flow
Leased line
NodeB OptiX PTN 1900 RNC
ADSL modem OptiX PTN 3900
Application in an ATM-Forwarding-Based ADSL Network

For the accessed HSDPA service, the OptiX PTN 1900 at the access node supports three
encapsulation schemes.
l MPLS Tunnel used: ATM/PWE3/PW label/MPLS label/ETH, as shown in Figure 9-7.
l IP Tunnel used: ATM/PWE3/PW label/IP/ETH, as shown in Figure 9-8.
l GRE Tunnel used: ATM/PWE3/PW label/GRE/IP/ETH, as shown in Figure 9-9.
Figure 9-7 Application in an ATM-forwarding-based ADSL network (MPLS Tunnel used)

ATM ATM
PWE3 PWE3
PW Label PW Label
ATM MPLS Label MPLS Label
PWE3 Ethernet Ethernet
ATM
PW Label AAL5 Network AAL5
MPLS Label ATM ATM
Ethernet ADSL ADSL STM-1
modem DSLAM
ATM
STM-1
NodeB OptiX PTN

ATM OptiX PTN RNC
1900
E1/STM-1 ATM 3900
E1

Figure 9-8 Application in an ATM-forwarding-based ADSL network (IP Tunnel used)

ATM ATM
PWE3 PWE3
PW Label PW Label
ATM IP IP
PWE3 Ethernet Ethernet
ATM
PW Label AAL5 Network AAL5
IP ATM ATM
Ethernet ADSL ADSL STM-1
modem DSLAM
ATM
STM-1
NodeB OptiX PTN OptiX PTN

ATM RNC
1900 3900
E1/STM-1 ATM
E1
Figure 9-9 Application in an ATM-forwarding-based ADSL network (GRE Tunnel used)

ATM
PWE3
PW Label
ATM GRE ATM
PWE3 IP PWE3
PW Label Ethernet PW Label
ATM
GRE AAL5 GRE
Network
IP ATM IP
Ethernet ADSL ADSL Ethernet
modem DSLAM
ATM
STM-1
NodeB OptiX PTN OptiX PTN RNC

ATM 1900 3900
E1/STM-1 ATM
E1
The ADSL modem can work in either the bridge or the router mode.
l When working in the bridge mode, the ADSL modem performs EoA encapsulation to the
accessed FE services. The OptiX PTN 1900 at the access node can use either the MPLS
Tunnel or the IP Tunnel and GRE Tunnel.
l When working in the router mode, the ADSL modem performs IPoA encapsulation to the
accessed FE services. the OptiX PTN 1900 at the access node can use the IP Tunnel and
GRE Tunnel.
Services forwarded through the ADSL network are finally converged to the OptiX PTN 3900
at the convergence node through the STM-1 interface. The OptiX PTN 3900 at the convergence
node then rearranges the data packets that carry the HSDPA services, and forwards the data
packets along with the signaling and R99 services to the RNC. The RNC forwards the services
to different service networks according to service types. In this way, the HSDPA service can be
forwarded in the wireless access and transport network in an end-to-end manner.
Application in an ETH-Forwarding-Based ADSL Network

For such application, the ADSL network realizes Layer 2 forwarding of Ethernet packets
according to frame headers. In this way, the MPLS tunnel can be used to transport the HSDPA
service, as shown in Figure 9-10.

Figure 9-10 Application in an ETH-forwarding-based ADSL network

ATM
PWE3
PW Label
MPLS Label ATM
ATM
PWE3
PWE3 Ethernet
ETH PW Label
PW Label AAL5 Network MPLS Label
MPLS Label ATM
ADSL Ethernet
Ethernet ADSL DSLAM
modem
ATM
STM-1

ATM RNC
1900 3900
E1/STM-1 ATM
E1
Application in an IP-Forwarding-Based ADSL Network

For such application, the ADSL network forwards the IP packets according to the IP headers.
Hence, the IP tunnel or GRE tunnel is required to carry packets, as shown in Figure 9-11 and
Figure 9-12.
Figure 9-11 Application in an IP-forwarding-based ADSL network (IP tunnel used)

ATM
PWE3
PW Label
ATM IP ATM
PWE3 Ethernet PWE3
PW Label AAL5 IP Network PW Label
IP ATM IP
modem DSLAM
ATM
STM-1

ATM RNC
1900 3900
E1/STM-1 ATM
E1
Figure 9-12 Application in an IP-forwarding-based ADSL network (GRE tunnel used)

ATM
PWE3
PW Label
ATM GRE ATM
PWE3 IP PWE3
PW Label Ethernet PW Label
GRE AAL5 IP Network GRE
IP ATM IP
modem DSLAM
ATM
STM-1
NodeB OptiX PTN OptiX PTN RNC

ATM 1900 3900
E1/STM-1 ATM
E1

Product Description 10 Technical Specifications
10 Technical Specifications
About This Chapter
The technical specifications of the OptiX PTN 3900 are related to several items.
10.1 System Specifications

The system specifications of the OptiX PTN 3900 cover the specifications of the cabinets and
the subrack.
10.2 System Performance
The OptiX PTN 3900 have different performance specifications for different performance items.
10.3 Technical Specifications of Boards
Technical specifications of boards cover specifications of interfaces, dimensions, weight and
power consumption of boards.
10.4 Laser Class
Lasers are of two classes according to the value of the output optical power.
10.5 Specifications of Clock Interfaces
Clock interfaces of the OptiX PTN 3900 and synchronization performance of the equipment
comply with related ITU-T standards.
10.6 Reliability Specifications
Reliability specifications of the OptiX PTN 3900 cover system usability, system mean annual
failure rate, MTTR system mean repair time and MTBF system mean fault interval.
10.7 EMC Performance Specifications
EMC performance specifications of the OptiX PTN 3900 comply with ETSI EN 300 386 V1.3.3.
10.8 Safety Certification
The OptiX PTN 3900 is awarded with several safety certificates.
10.9 Environment Requirements
The OptiX PTN 3900 requires proper environment for storage, transportation and operation.
This section describes the environment specifications for storage, transportation and operation
separately.

10 Technical Specifications Product Description
10.1 System Specifications

The system specifications of the OptiX PTN 3900 cover the specifications of the cabinets and
the subrack.
The OptiX PTN 3900 can be installed in an ETSI cabinet. lists the specifications of the ETSI
cabinets.
Table 10-1 Specifications of the ETSI cabinet for the OptiX PTN 3900 subrack
Number of
Allowed
Number of Number of
Dimensi OptiX PTN
Cabinet Weight Allowed OptiX Allowed
ons 3900 and
Type (kg) PTN 3900 OptiX PTN
(mm) OptiX PTN
Subracks 1900 Subracks
1900
Subracks
300 mm 600 60 2 4 1 x OptiX PTN

deep (width) x 3900 Subrack
ETSI 300 and 2 x OptiX
cabinet (depth) x PTN 1900
(T63) 2200 Subrack
(height)
300 mm 600 42 1 4 1 x OptiX PTN

deep (width) x 3900 Subrack
ETSI 300 and 2 x OptiX
cabinet (depth) x PTN 1900
(N63E) 2000 Subrack
(height)
600 45 2 4 1 x OptiX PTN

(width) x 3900 Subrack
300 and 2 x OptiX
(depth) x PTN 1900
2200 Subrack
(height)
NOTE
H
D
Table 10-2 lists the specifications of the OptiX PTN 3900 subrack.

Table 10-2 Specifications of the OptiX PTN 3900 subrack

Item Specification
Dimensions (mm) 496 (width) x 295 (depth) x 800 (height)
Weight (kg) Empty subrack: 35 (no boards or air filter housed)
Fully configured subrack: 60
Power consumption l Typical configuration I:

(W, with typical Power consumption: 1091
configuration) Configuration: 2 x FAN + 2 x PIU + 2 x XCS + 2 x SCA + 1 x
TN81EG16 + 7 x MP1 + 4 x AD1 + 1 x CD1 + 2 x MQ1 + 2 x
D75 + 1 x EX2
l Typical configuration II:
Power consumption: 855
Configuration: 2 x FAN + 2 x PIU + 2 x XCS + 2 x SCA + 1 x
TN81EG16 + 3 x MP1 + 1 x CD1 + 2 x MQ1 + 2 x D75 + 1 x
EX2
l Typical configuration III:
TN81EG16 + 4 x MP1 + 4 x CD1 + 2 x EX2
l Typical configuration IV:
TN81EG16 + 1 x EFF8 + 1 x EX2
Power consumption 2000(without microwave feature)

(W, with maximum 2650 (with microwave feature)
configuration)
Voltage range (V, DC) -38.4 to -57.6 (-48 V power supply)

-48.0 to -72.0 (-60 V power supply)
10.2 System Performance

The OptiX PTN 3900 have different performance specifications for different performance items.
Table 10-3 lists the system performance specifications of the OptiX PTN 3900.
Table 10-3 System performance specifications

Item Performance Specifications
FRR protection When less than 256 tunnels are switched at the same time, the FRR
time for TE tunnel protection time is less than 50 ms.

MPLS Tunnel 1 The protection switching time is less than 50 ms.

+1/1:1 protection
switching time
LAG protection l When links fail bidirectionally, the LAG protection switching time is
switching time less than 500 ms.
l When links fail unidirectional, the LAG protection switching time is
less than 3.5s.
Switching When the board is removed or manually switched, the service is not
performance of affected.
the SCA and XCS
Maximum l Typical configuration (static configuration): ≤ 8 minutes

interval for
l Typical configuration (dynamic signaling enabled): ≤ 15 minutes
consecutive
switching of the l Maximum configuration (static configuration): ≤ 10 minutes
active and standby l Maximum configuration (dynamic signaling enabled): ≤ 20 minutes
SCA
MSTP topology In the case of a link failure, the switching time is less than 1s when
converging time conditions are available for fast reconfiguration, and less than 30s when
conditions are unavailable for fast reconfiguration.
Maximum 256
number of routing
neighbors
Maximum 20k
number of routes
supported by the
equipment
Number of 4k (TN81SCA)
supported MPLS 8k (TN82SCA)
Tunnels
Total number of 256 (TN81SCA)

supported IP 1k (TN82SCA)
Tunnels and GRE
Tunnels
Number of 2k
supported Tunnel
OAM
Number of 8k (TN81SCA)
supported PWs 16k (TN82SCA)
Number of 1512
supported CES
services

Number of 4k (remote service) and 2k (local service)

supported ATM
services
Number of 8k (remote service) and 4k (local service)

supported ATM
connections
(including VCCs
and VPCs)
Number of 4k
supported E-Line
services
Number of VSI 1k
supported for E-
LAN
Maximum 256
number of virtual
ports supported
for each VSI
Number of The entire equipment supports 128k dynamic MAC addresses.

supported
dynamic MAC
addresses
Number of The entire equipment supports 2k static MAC addresses.

supported static
MAC addresses
Number of 64k
supported VLAN/
VLAN list
Granularity of CAR and Shaping support the minimum granularity of 64 kbit/s

CAR/Shaping
Number of CAR Single-bucket CAR: 8k (dual-bucket CAR: 4k)

supported by the
equipment
ARP table 512 static ARP entries for the entire equipment
capacity 256 dynamic ARP entries for each port
Number of The equipment supports a maximum of 4k multicast groups. The

multicast groups equipment supports a maximum of 24k multicast members.
supported by the
equipment
Number of 1k
supported APS
protection groups

Number of 256
supported ML-
PPP groups
Number of 64 (TN81SCA)
supported L3VPN 255 (TN82SCA)
10.3 Technical Specifications of Boards

Technical specifications of boards cover specifications of interfaces, dimensions, weight and
power consumption of boards.
10.3.1 Technical Specification of the TN81EG16

Specifications of the TN81EG16 cover specifications of interfaces, board dimensions, and
weight.
weight.
10.3.3 Technical Specification of the EX2
The technical specifications of the EX2 cover the interface specifications, board dimensions,
and weight.
10.3.4 Technical Specification of the ETFC
Specifications of the ETFC board cover the interface specifications, board dimensions, and
weight.
10.3.5 Technical Specifications of the EFF8
The technical specifications of the EFF8 include the interface specifications, board dimensions,
and weight.
10.3.6 Technical Specification of the EFG2
Specifications of the EFG2 cover specifications of interfaces, board dimensions, and weight.
10.3.7 Technical Specification of the MP1
Specifications of the MP1 board cover board dimensions, and weight.
10.3.8 Technical Specification of the MD1
Specifications of the MD1 board cover board dimensions, and weight.
10.3.9 Technical Specification of the MQ1
Specifications of the MQ1 board cover board dimensions, and weight.
10.3.10 Technical Specification of the CD1
Specifications of the CD1 board cover specifications of interfaces, board dimensions, and
weight.
10.3.11 Technical Specification of the AD1
Specifications of the AD1 cover specifications of interfaces, board dimensions, and weight.
10.3.12 Technical Specification of the ASD1
Specifications of the ASD1 cover specifications of interfaces, board dimensions, and weight.

10.3.13 Technical Specifications of the AFO1

The technical specifications of the AFO1 cover the interface specifications, board dimensions,
and weight.
10.3.14 Technical Specification of the POD41
Specifications of the POD41 board cover specifications of interfaces, board dimensions, and
weight.
10.3.15 Technical Specification of the D12
Specifications of the D12 board cover interface specifications, board dimensions, and weight.
10.3.17 Technical Specification of the CMR4
Specifications of the CMR4 board cover specifications of interfaces, board dimensions, weight
and power consumption.
10.3.19 Technical Specification of the TN81SCA
Specifications of the TN81SCA board cover board dimensions, and weight.
10.3.21 Technical Specification of the TN81XCS
Specifications of the TN81XCS board cover board dimensions, and weight.
10.3.23 Technical Specification of the PIU
Specifications of the PIU board cover board dimensions, weight, and input voltage.
10.3.24 Technical Specification of the FAN
Specifications of the FAN board cover board dimensions, weight, and working voltage.

weight.
Table 10-4 lists the specifications of interfaces on the TN81EG16.
Table 10-4 Specifications of the interfaces on the TN81EG16
Item Specification
Optical 1000BASE- 1000BASE- 1000BASE- 1000BASE- 1000BASE-

interface type SX LX VX ZX CWDM
(0.5km) (10 km) (40 km) (80 km) (40 km)
Fiber type Multi-mode Single- Single- Single- Single-mode

mode mode mode

Item Specification
Working 770 to 860 1270 to 1270 to 1500 to For details on

wavelength 1355 1355 1580 wavelength
range (nm) allocation, see
Table 10-5.
Mean -9.5 to 0 -11 to -3 - 5 to 0 -2 to 5 0 to 5

launched
optical power
(dBm)
Receiver -17 -19 -22 -22 -19

sensitivity
(dBm)
Min. overhead 0 -3 -3 -3 -3
point (dBm)
Extinction 9 9 9 9 9
ratio (dB)
Table 10-5 Wavelengths of 1000BASE-CWDM interfaces on the TN81EG16

No. Wavelength (nm) No. Wavelength (nm)
1 1464.5 to 1477.5 5 1544.5 to 1557.5
2 1484.5 to 1497.5 6 1564.5 to 1577.5
3 1504.5 to 1517.5 7 1584.5 to 1597.5
4 1524.5 to 1537.5 8 1604.5 to 1617.5
Board dimensions (mm): 261.4 (height) x 266.8 (depth) x 50.8 (width)

Weight (kg): 2.40

weight.
Table 10-6 lists the specifications of interfaces on the TN82EG16.
Table 10-6 Specifications of the interfaces on the TN82EG16

Item Specification

(0.5km) (10 km) (40 km) (80 km) (40 km)

Item Specification

mode mode mode
Working 770 to 860 1270 to 1355 1270 to 1355 1500 to 1580 For details on
wavelength wavelength
range (nm) allocation,
see Table
10-7.
Mean -9.5 to 0 -11 to -3 - 5 to 0 -2 to 5 0 to 5

launched
optical power
(dBm)
Receiver -17 -19 -22 -22 -19

sensitivity
(dBm)
point (dBm)
ratio (dB)
Table 10-7 Wavelengths of 1000BASE-CWDM interfaces on the TN82EG16

1 1464.5 to 1477.5 5 1544.5 to 1557.5
2 1484.5 to 1497.5 6 1564.5 to 1577.5
3 1504.5 to 1517.5 7 1584.5 to 1597.5
4 1524.5 to 1537.5 8 1604.5 to 1617.5

Weight (kg): 2.40
10.3.3 Technical Specification of the EX2

The technical specifications of the EX2 cover the interface specifications, board dimensions,
and weight.
Table 10-8 lists the specifications of interfaces on the EX2.

Table 10-8 Specifications of interfaces on the EX2
Item Specification
Optical 10GBASE- 10GBASE- 10GBASE- 10GBASE- 10GBASE-

interface SR LR LR ER ZR
type (0.3 km) 10GBASE- 10GBASE- 10GBASE- 10GBASE-
LW LW EW ZW
(2 km) (10 km) (40 km) (80 km)
Fiber type Multi-mode Single-mode Single- Single- Single-mode

mode mode
Working 840 to 860 1260 to 1355 1260 to 1530 to 1530 to 1565

wavelength 1355 1565
range (nm)
Mean -7.3 to -1 -8.2 to 0.5 -8.2 to 0.5 -4.7 to 4 0 to 4

launched
optical
power
(dBm)
Receiver -11.1 -11 -11 -14.1 -21

sensitivity
(dBm)
Min. -1 -1 0.5 -1 -7
overhead
point (dBm)
Extinction 3 3.5 3.5 3 3

ratio (dB)
Board weight (kg): 2.08
10.3.4 Technical Specification of the ETFC

Specifications of the ETFC board cover the interface specifications, board dimensions, and
weight.
Table 10-9 lists the interface specifications of the ETFC.
Table 10-9 Interface specifications of the ETFC
Item Specification
Electrical interface rate 10 Mbit/s, 100 Mbit/s
RJ-45 electrical interface specification Compliant with the IEEE 802.3
Transmit jitter 1.4 ns (peak to peak)

Weight (kg): 0.55
10.3.5 Technical Specifications of the EFF8

The technical specifications of the EFF8 include the interface specifications, board dimensions,
and weight.
Interface Specifications
Table 10-10 lists the specifications of the optical interfaces of the EFF8.
Table 10-10 Specifications of the interfaces on the EFF8
Item Specification
Optical interface 100BASE-FX 100BASE-FX 100BASE-FX

type (15 km) (40 km) (80 km)
Fiber type Single-mode Single-mode Single-mode
Working 1261 to 1360 1263 to 1360 1480 to 1580

wavelength range
(nm)
Mean launched -15 to -8 -5 to 0 -5 to 0

optical power
(dBm)
Receiver sensitivity -28 -34 -34

(dBm)
Min. overhead point -8 -10 -10

(dBm)
Extinction ratio 8.2 10 10

(dB)
Other Specifications
Weight (kg): 0.64
10.3.6 Technical Specification of the EFG2

Specifications of the EFG2 cover specifications of interfaces, board dimensions, and weight.
Table 10-11 lists the specifications of interfaces on the EFG2. Table 10-12 lists the wavelengths
of colored optical interfaces on the EFG2.

Table 10-11 Specifications of the interfaces on the EFG2

Item Specification

(0.5km) (10 km) (40 km) (80 km) (40 km)

mode mode mode
Working 770 to 860 1270 to 1355 1270 to 1355 1500 to 1580 For details on
wavelength wavelength
range (nm) allocation, see
Table 10-12.
Mean -9.5 to 0 -11 to -3 - 5 to 0 -2 to 5 0 to 5

launched
optical power
(dBm)
Receiver -17 -19 -22 -22 -19

sensitivity
(dBm)
point (dBm)
ratio (dB)
Table 10-12 Wavelengths of 1000BASE-CWDM interfaces on the EFG2

1 1464.5 to 1477.5 5 1544.5 to 1557.5
2 1484.5 to 1497.5 6 1564.5 to 1577.5
3 1504.5 to 1517.5 7 1584.5 to 1597.5
4 1524.5 to 1537.5 8 1604.5 to 1617.5

Weight (kg): 0.52
10.3.7 Technical Specification of the MP1

Specifications of the MP1 board cover board dimensions, and weight.
Weight (kg): 1.15

10.3.8 Technical Specification of the MD1

Specifications of the MD1 board cover board dimensions, and weight.
Weight (kg): 0.34
10.3.9 Technical Specification of the MQ1

Specifications of the MQ1 board cover board dimensions, and weight.
Weight (kg): 0.34
10.3.10 Technical Specification of the CD1

Specifications of the CD1 board cover specifications of interfaces, board dimensions, and
weight.
Table 10-13 lists the specifications of interfaces on the CD1.
Table 10-13 Specifications of interfaces on the CD1
Item Specification
Nominal bit rate (Mbit/s) 155.52
Optical interface type S-1.1 L-1.1 L-1.2

(15 km) (40 km) (80 km)
Working wavelength 1261 to 1360 1263 to 1360 1480 to 1580

range (nm)
Launched optical power -15 to -8 -5 to 0 -5 to 0

(dBm)
Optical receiver -28 -34 -34

sensitivity (dBm)
Minimum overload -8 -10 -10

(dBm)
Extinction ratio (dB) 8.2 10 10

Weight (kg): 0.34
10.3.11 Technical Specification of the AD1

Specifications of the AD1 cover specifications of interfaces, board dimensions, and weight.

Table 10-14 lists the specifications of interfaces on the AD1.
Table 10-14 Specifications of interfaces on the AD1
Item Specification
Nominal bit rate (Mbit/s) 155.52

(15 km) (40 km) (80 km)

range (nm)

(dBm)

sensitivity (dBm)

(dBm)
Weight (kg): 0.35
10.3.12 Technical Specification of the ASD1

Specifications of the ASD1 cover specifications of interfaces, board dimensions, and weight.
Table 10-15 lists the specifications of interfaces on the AD1.
Table 10-15 Specifications of interfaces on the ASD1
Item Specification
Nominal bit rate 155.52

(Mbit/s)

(15 km) (40 km) (80 km)

range (nm)
Launched optical -15 to -8 -5 to 0 -5 to 0

power (dBm)

Item Specification

sensitivity (dBm)

(dBm)

Weight (kg): 0.35
10.3.13 Technical Specifications of the AFO1

The technical specifications of the AFO1 cover the interface specifications, board dimensions,
and weight.
Interface Specifications
Table 10-16 lists the specifications of interfaces on the AFO1.
Table 10-16 Specifications of interfaces on the AFO1

Item Specification
Nominal bit rate 155.52

(Mbit/s)
Optical interface S-1.1 L-1.1 L-1.2

type (15 km) (40 km) (80 km)

range (nm)
Mean launched - 15 to - 8 - 5 to 0 - 5 to 0
optical power (dBm)
Receiver sensitivity - 28 - 34 - 34
(dBm)
Minimum overhead -8 - 10 - 10
point (dBm)
Other Specifications

Weight (kg): 0.78
10.3.14 Technical Specification of the POD41

Specifications of the POD41 board cover specifications of interfaces, board dimensions, and
weight.
Table 10-17 and Table 10-18 list the specifications of interfaces on the POD41.
Table 10-17 Specifications of interfaces on the POD41

Item Specification
Nominal bit rate (kbit/s) 155520

(15 km) (40 km) (80 km)

range (nm)

(dBm)

sensitivity (dBm)

(dBm)
Table 10-18 Specifications of interfaces on the POD41

Item Specification
Nominal bit rate (kbit/s) 622080
Optical interface type S-4.1 L-4.1 L-4.2 V-4.2

(15 km) (40 km) (80 km) (100 km)
Fiber type Single-mode Single-mode Single-mode Single-mode
Working wavelength 1261 to 1360 1280 to 1355 1480 to 1580 1480 to 1580
range (nm)
Launched optical power -15 to -8 -3 to 2 -3 to 2 -3 to 2

(dBm)
Optical receiver -28 -28 -28 -32

sensitivity (dBm)

Item Specification
Minimum overload -8 -8 -8 -13

(dBm)
Extinction ratio (dB) 8.2 10 10 10

Weight (kg): 0.55

Table 10-19 lists the interface specifications of the D12.
Table 10-19 Interface specifications of the D12

Item Specification
Nominal bit rate: (kbit/s) 2048
Code HDB3
Pulse shape at output port Compliant with ITU-T G.703
Attenuation of input interface at 1024 kHz 0 to 6

frequency point (dB)
Anti-interference capability of input port Compliant with ITU-T G.703
Input jitter tolerance Compliant with ITU-T G.823
Output jitter Compliant with ITU-T G.823

Weight (kg): 0.56

Table 10-20 lists the interface specifications of the D75.
Table 10-20 Interface specifications of the D75

Item Specification
Nominal bit rate: (kbit/s) 2048
Code HDB3

Item Specification
Pulse shape at output port Compliant with ITU-T G.703
Attenuation of input interface at 1024 kHz 0 to 6

frequency point (dB)
Anti-interference capability of input port Compliant with ITU-T G.703
Input jitter tolerance Compliant with ITU-T G.823
Output jitter Compliant with ITU-T G.823
Weight (kg): 0.57

Table 10-21 lists the specifications of optical interfaces on the CMR4.
Table 10-21 Specifications of optical interfaces on the CMR4
Item Specification Optical Interface
Working wavelength range 1291 to 1611 -

(nm)
Channel spacing (nm) 20 -
0.5 dB passband bandwidth ≥ ±6.5 IN-D1

(nm) IN-D2
Insertion loss in the ≤ 1.5 IN-D3
wavelength-dropping IN-D4
channel (dB)
Adjacent channel isolation > 25

(dB)
Non-adjacent channel > 35

isolation (dB)
0.5 dB passband bandwidth ≥±6.5 A1-OUT

(nm) A2-OUT
Insertion loss in the ≤ 1.5 A3-OUT
wavelength-adding channel A4-OUT
(dB)
Insertion loss (dB) ≤ 1.5 IN-MO

MI-OUT

Isolation (dB) > 13
Return loss (dB) > 40 -
The CMR4 adds/drops and multiplexes four signals to/from the multiplexed signals. Table
10-22 lists the rules of adding/dropping wavelength of the CMR4.
Table 10-22 Rules of adding/dropping wavelength of the CMR4
Group Wavelength (nm)
A1/D1 A2/D2 A3/D3 A4/D4
1 1291 1311 1331 1351
2 1391 1411 1431 1451
3 1471 1491 1591 1611
4 1511 1531 1551 1571
Weight (kg): 0.9

Table 10-23 lists the specifications of optical interfaces on the CMR2.
Table 10-23 Specifications of optical interfaces on the CMR2
Working wavelength range 1271 to 1611 -

(nm)
Channel spacing (nm) 20 -
0.5 dB passband bandwidth ≥ ±6.5 IN-D1

(nm) IN-D2
Insertion loss in the ≤ 1.5
wavelength-dropping
channel (dB)
Adjacent channel isolation > 25

(dB)

Non-adjacent channel > 35

isolation (dB)
0.5 dB passband bandwidth ≥±6.5 A1-OUT

(nm) A2-OUT
Insertion loss in the ≤ 1.5
wavelength-adding channel
(dB)
Insertion loss (dB) ≤ 1.0 IN-MO

MI-OUT
Isolation (dB) > 13
Return loss (dB) > 40 -
The CMR2 adds/drops and multiplexes two signals to/from the multiplexed signals. Table
10-24 lists the rules of adding/dropping wavelength of the CMR2.
Table 10-24 Rules of adding/dropping wavelength of the CMR2

Group Wavelength (nm)
A1/D1 A2/D2
1 1271 1371
2 1471 1491
3 1511 1531
4 1551 1571
5 1591 1611

Weight (kg): 0.8

Weight (kg): 0.93


Weight (kg): 0.96

Board dimensions (mm): 294.1 (height) x 271.5(depth) x 40.0 (width)
Weight (kg): about 2.45

Weight (kg): about 2.48
10.3.23 Technical Specification of the PIU

Specifications of the PIU board cover board dimensions, weight, and input voltage.
Weight (kg): 1.5
Input voltage range (V DC):
10.3.24 Technical Specification of the FAN

Specifications of the FAN board cover board dimensions, weight, and working voltage.
Weight (kg): 4.5
Working voltage (V):
10.4 Laser Class

Lasers are of two classes according to the value of the output optical power.
WARNING
Avoid direct eye exposure to the laser beams launched from the optical interface during the
installation and maintenance of the fiber. Otherwise, your eyes may be hurt.
Table 10-25 shows the laser classes of the boards.

Table 10-25 Laser Class

Laser Class Label Board
Class 1 CD1, AD1, ASD1, EFG2, POD41, EG16, EX2,

CLASS 1 EFF8, AFO1
LASER
PRODUCT
Class 1M LASER
CMR2, CMR4
RADIATION
DO NOT VIEW DIRECTLY

WITH OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT
10.5 Specifications of Clock Interfaces

Clock interfaces of the OptiX PTN 3900 and synchronization performance of the equipment
comply with related ITU-T standards.
Clock Interface Types

The OptiX PTN 3900 provides external clock input interfaces and clock output interfaces. Table
10-26 lists the details.
Table 10-26 Specifications of clock interfaces of the OptiX PTN 3900

Clock Type Interface Specification
External clock Two-channel 75-ohm 2048 kbit/s (G.703) or 2048 kHz (G.703) inputs
synchronization Two-channel 120-ohm 2048 kbit/s (G.703) or 2048 kHz (G.703)
source inputs
Synchronization Two-channel 75-ohm 2048 kbit/s (G.703) or 2048 kHz (G.703)

output clock outputs
Two-channel 120-ohm 2048 kbit/s (G.703) or 2048 kHz (G.703)
outputs
External time Two-channel DCLS time inputs

synchronization Two-channel 1PPS + time information inputs
source
Synchronization Two-channel DCLS time outputs

output time Two-channel 1PPS + time information outputs

Timing and Synchronization Performance

The timing and synchronization performance of the OptiX PTN 3900 complies with ITU-T G.
813 and G.823.
Table 10-27 lists details on the timing and synchronization performance.
Table 10-27 Timing and synchronization performance
Output Jitter Output Frequency of the Long-Term Phase

Internal Oscillator in Free- Variation (Locked
Run Mode Mode)
Complies with ITU-T G.813 Complies with ITU-T G.813 Complies with ITU-T G.
and G.823. and G.823. 813 and G.823.
10.6 Reliability Specifications

Reliability specifications of the OptiX PTN 3900 cover system usability, system mean annual
failure rate, MTTR system mean repair time and MTBF system mean fault interval.
Table 10-28 lists the reliability specifications of the OptiX PTN 3900.
Table 10-28 Reliability specifications
Item Required Specification
System usability 0.9999992: The equipment should not be out

of service for more than 0.42 minutes in one
year.
System mean annual failure rate Less than 1.2%
MTTR system mean repair time Two hours
MTBF system mean fault interval 284.99 years
10.7 EMC Performance Specifications

EMC performance specifications of the OptiX PTN 3900 comply with ETSI EN 300 386 V1.3.3.
The OptiX PTN 3900 complies with the following EMC standards:
l ETSI EN 300 386 1.3.3 (2005-04)
l ETSI EN 300 132-2 (2003-09)
l CISPR22 (2003-04)
l GR-1089 (2006)
l IEC 61000-4-2 (2001-04)
l IEC 61000-4-3 (2002-09)

l IEC 61000-4-4 (1995+A1:2000.11+A2:2001.07)

l IEC 61000-4-5 (2001-04)
l IEC 61000-4-6 (2003-05)
l IEC 61000-4-29 (2000-08)
10.8 Safety Certification

The OptiX PTN 3900 is awarded with several safety certificates.
Table 10-29 lists the safety certifications that the OptiX PTN 3900 has passed.
Table 10-29 Safety certifications that the OptiX PTN 3900 has passed
Certification Item Criteria
Electromagnetic compatibility (EMC) CISPR22 Class A

CISPR24
EN55022 Class A
EN50024
ETSI EN 300 386 Class A
ETSI ES 201 468
CFR 47 FCC Part 15 Class A
ICES 003 Class A
AS/NZS CISPR22 Class A
GB9254 Class A
VCCI Class A
Safety IEC 60950-1

IEC/EN41003
EN 60950-1
UL 60950-1
CSA C22.2 No 60950-1
AS/NZS 60950-1
BS EN 60950-1
IS 13252
GB4943
Laser safety FDA rules

21 CFR 1040.10 and 1040.11
IEC60825-1
IEC60825-2
EN60825-1
EN60825-2
GB7247

Certification Item Criteria
Health ICNIRP Guideline

1999-519-EC
EN 50385
OET Bulletin 65
IEEE Std C95.1
Environment protection RoHS
10.9 Environment Requirements

The OptiX PTN 3900 requires proper environment for storage, transportation and operation.
This section describes the environment specifications for storage, transportation and operation
separately.
10.9.1 Environment for Storage

The OptiX PTN 3900 requires proper environment for storage.
10.9.2 Environment for Transportation
The OptiX PTN 3900 requires proper environment for transportation.
10.9.3 Environment for Operation
The OptiX PTN 3900 requires proper environment for operation.
10.9.1 Environment for Storage

The OptiX PTN 3900 requires proper environment for storage.
Climate
Table 10-30 lists the climatic requirements of the OptiX PTN 3900 for storage.
Table 10-30 Climatic requirements of the OptiX PTN 3900 for storage
Item Specification
Temperature -40℃ to +70℃
Relative humidity 10% to 100%
Temperature change 0.5℃/min

rate
Air flowing speed ≤ 30 m/s
Air pressure 70 kPa to 106 kPa
Solar radiation ≤ 1120 W/m2
Heat radiation ≤ 600 W/m2

Waterproof Requirement
Requirement for storing equipment on the customer site: Generally, the equipment must be
stored indoors.
No water should remain on the floor or leak to the equipment carton. The equipment should be
placed away from places where water leakage is possible, such as near the automatic fire-fighting
facilities and heating facilities.
If the equipment is stored outdoors, the following four conditions are required.
l The carton must be intact.

l Required rainproof measures must be taken to prevent water from entering the carton.
l No water is on the ground where the carton is placed.
l The carton must be free from direct exposure to sunshine.
Biological Environment
l Avoid multiplication of microbe, such as eumycete and mycete.
l Keep rodents such as mice away.
Air Cleanness
l The air must be free from explosive, electric-conductive, magnetic-conductive or corrosive
dust.
l Table 10-31 lists the density requirements for mechanically active substances during
storage.
l Table 10-32 lists the density requirements for chemically active substances during storage.
Table 10-31 Density requirements for mechanically active substances during storage
Mechanically Active Substance Content
Suspending dust ≤ 5.00 mg/m3
Precipitable dust ≤ 20.0 mg/m2·h
Gravel ≤ 300 mg/m3
Table 10-32 Density requirements for chemically active substances during storage
Chemically Active Substance Content
SO2 0.30 mg/m3 to 1.0 mg/m3
H2S 0.1 mg/m3 to 0.5 mg/m3
NOx 0.5 mg/m3 to 1.0 mg/m3
NH3 1.0 mg/m3 to 3.0 mg/m3

Cl2 0.1 mg/m3 to 0.3 mg/m3
HCl 0.1 mg/m3 to 0.5 mg/m3
HF 0.01 mg/m3 to 0.03 mg/m3
O3 0.05 mg/m3 to 0.1 mg/m3
Mechanical Stress
Table 10-33 lists the requirements of mechanical stress for storage.
Table 10-33 Requirements of mechanical stress for storage
Item Sub-Item Specification
Random vibration ASD - 0.02m2/s3 -
Frequency range 5 Hz to 10 10 Hz to 50 Hz 50 Hz to 100

Hz Hz
dB/oct 12 - -12
Axes of vibration 3
10.9.2 Environment for Transportation

The OptiX PTN 3900 requires proper environment for transportation.
Climate
Table 10-34 lists climatic requirements for transportation.
Table 10-34 Climatic requirements for transportation
Item Specification
Temperature -40℃ to +70℃
Relative humidity 5% RH to 95% RH

rate
Air following speed ≤ 20 m/s

Item Specification
Rain ≤ 6 mm/min
Waterproof Requirement
The following conditions should be present for transportation.
l The carton must be intact.

l Required rainproof measures must be taken to the transportation tools to prevent water from
entering the carton.
l No water is on the transportation tools.
Air Cleanness
dust.
transportation.
l Table 10-36 lists the density requirements for chemically active substances during
transportation.
Table 10-35 Density requirements for mechanically active substances during transportation
Mechanically Active Substances Content
Precipitable dust ≤ 3.0 mg/m2·h
Table 10-36 Density requirements for chemically active substances during transportation
SO2 ≤ 1.0 mg/m3
H2S ≤ 0.5 mg/m3
NOx ≤ 1.0 mg/m3
HCl ≤ 0.5 mg/m3

NH3 ≤ 3.0 mg/m3
HF ≤ 0.03 mg/m3
O3 ≤ 0.1 mg/m3
Mechanical Stress
Table 10-37 lists the requirements of mechanical stress for transportation.
Table 10-37 Requirements of mechanical stress for transportation
Random vibration ASD 1 m2/s3 -3 dB
Frequency range 5 Hz to 20 Hz 20 Hz to 200Hz
Bump Shock spectrum type 100 m/s2, 11ms, 100 in each direction
I (mass>50kg)
Shock spectrum type 180 m/s2, 6ms, 100 in each direction

II (mass≤50kg)
Direction of bump 6
10.9.3 Environment for Operation

The OptiX PTN 3900 requires proper environment for operation.
Climate
Table 10-38 and Table 10-39 list the climatic requirements of the OptiX PTN 3900 for operation.
Table 10-38 Temperature and humidity required by the OptiX PTN 3900 for operation
Temperature Relative humidity
Long-term operation Short-term operation Long-term Short-term

operation operation
0℃ to 50℃ -5℃ to 55℃ 5% to 95%

NOTE
When the OptiX PTN 3900 is installed in an ETSI cabinet, ignore the radiation.

Table 10-39 Other climatic requirements of the OptiX PTN 3900 for operation
Item Specification
Altitude ≤ 4000 m

rate
Air following speed ≤ 5 m/s
Air Cleanness
dust.
operation.
l Table 10-41 lists the density requirements for chemically active substances during
operation.
Table 10-40 Density requirements for mechanically active substances during operation
Mechanically Active Substance Content
Suspending dust ≤ 0.4 mg/m3
Precipitable dust ≤ 15 mg/m2·h
Table 10-41 Density requirements for chemically active substances during operation
SO2 0.30 mg/m3 to 1.0 mg/m3
H2S 0.1 mg/m3 to 0.5 mg/m3
NOx 0.5 mg/m3 to 5.0 mg/m3

NH3 1.0 mg/m3 to 3.0 mg/m3
Cl2 0.1 mg/m3 to 0.3 mg/m3
HCl 0.1 mg/m3 to 0.5 mg/m3
HF 0.01 mg/m3 to 0.03 mg/m3
O3 0.05 mg/m3 to 0.1 mg/m3
Mechanical Stress
Table 10-42 lists the requirements of mechanical stress for operation.
Table 10-42 Requirement of mechanical stress for operation

Sinusoidal vibration Velocity 5 mm/s -
Acceleration - 2 m/s2
Frequency range 5 Hz to 62 Hz 62 Hz to 200 Hz
Shock Shock spectrum type II 30 m/s2, 11ms, 3 in each direction
Direction of bump 6

Product Description A Compliant Standards and Protocols
A Compliant Standards and Protocols
Environment Standard
Standard or Protocol Title
ETSI EN 300 019-1 Environmental Engineering (EE)

Environmental conditions and environmental
tests for telecommunications equipment
Classification of environmental conditions
ETSI EN 300 019-2 Environmental Engineering (EE)

Environmental conditions and environmental
tests for telecommunications equipment
Specification of environmental tests
ETSI EN 300 753 Equipment Engineering (EE)

Acoustic noise emitted by
telecommunications equipment
IEC 60068-1 Environmental testing

Part 1: General and guidance
IEC 60068-2 Basic environmental testing procedures

Part 2: Tests
IEC 600721-1 Classification of environmental conditions-

Part 1: Environmental parameters and their
severities
IEC 600721-2 Classification of environmental conditions-

Part 2: Environmental conditions appearing
in nature
IEC 600529 Degrees of protection provided by enclosures

(IP Code)
Issue 01 (2009-06-30) Huawei Proprietary and Confidential A-1

A Compliant Standards and Protocols Product Description
QM333 Specification for environmental testing of

electronic equipments for transmission and
switching use
GR-63 NEBS Requirements: Physical Protection
GR-63-CORE NEBS™ Requirements: Physical Protection
EMC Standard
EN 55022 Information technology equipment-Radio

disturbance characteristics-Limits and
methods of measurement
ETSI EN 300 132-2 Equipment Engineering (EE): Power supply

interface at the input to telecommunications
equipment
Part 2: Operated by direct current (dc)
ETSI EN 300 386 Electromagnetic compatibility and Radio

spectrum Matters (ERM)
Telecommunication network equipment;
ElectroMagnetic Compatibility (EMC)
requirements
ETSI ES 201 468 Electromagnetic compatibility and Radio

spectrum Matters (ERM)
Additional ElectroMagnetic Compatibility
(EMC) telecommunications equipment for
enhanced availability of service in specific
applications
ETSI EN 300 253 Environmental Engineering (EE)

Earthing and bonding configuration inside
telecommunications centres
EN 61000-4-29 Electromagnetic compatibility (EMC)-

Part4-29: Testing and measurement
techniques-Voltage dips, shot interruptions
and voltage variations on d.c. input power
port immunity tests
CISPR22 Information technology equipment-Radio

disturbance characteristics-Limits and
methods of measurement
A-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

IEC 61000-4-29 Electromagnetic compatibility (EMC)-

Part4-29: Testing and measurement
techniques-Voltage dips, shot interruptions
and voltage variations on d.c. input power
port immunity tests
ITU-T K.27 Bonding Configurations and Earthing Inside

a Telecommunication Building
GR-1089-CORE Electromagnetic Compatibility and Electrical

Safety - Generic Criteria for Network
Telecommunications Equipment
IEC 61000-4-5 Electromagnetic compatibility (EMC)- Part

4: Testing and measurement techniques -
Section 5: Surge immunity test
Safety Compliance Standard

IEC/EN/UL 60950-1 Information technology equipment - Safety -

Part 1: General requirements
IEC/EN 60825-1 Safety of laser products - Part 1: Equipment

classification, requirements and user's guide
IEC/EN 60825-2 Safety of laser products - Part 2: Safety of

optical fibre communication systems (OFCS)
73/23/EEC Low voltage directive
21 CFR 1040.10/1040.11 Performance standards for light-emitting-

products
Ethernet Service Standard

IEEE802.1D Media access control (MAC) bridges
IEEE802.1Q Virtual bridged local area networks
IEEE802.1ad Provider bridges
IEEE802.1ag Connectivity fault management
IEEE802.1ah Provider backbone bridges

IEEE802.3 Carrier sense multiple access with collision

detection (CSMA/CD) access method and
physical layer specifications
ITU-T G.8012 Ethernet UNI and Ethernet over transport

NNI
ITU-T G.1730 Requirements for OAM functions in Ethernet

based networks and Ethernet services
ITU-T G.1731 OAM functions and mechanisms for Ethernet

based networks
ITU-T G.8031 Ethernet protection switching
ITU-T G.8010 Architecture of Ethernet layer networks
ITU-T G.8021 Characteristics of Ethernet transport network

equipment functional blocks
MEF MEF2 Requirements and framework for Ethernet

service protection in metro Ethernet networks
MEF MEF4 Metro Ethernet network architecture

framework - Part 1: generic framework
L2VPN Standard
draft-ietf-l2vpn-oam-req-frmk-05 L2VPN OAM requirements and framework
draft-ietf-l2vpn-signaling-08 Provisioning, autodiscovery, and signaling in

L2VPNs
RFC 4664 Framework for layer 2 virtual private

networks (L2VPNs)
MPLS Standard
ITU-T G.8112 Interfaces for the transport MPLS (T-MPLS)

hierarchy
ITU-T G.8131 Protection switching for transport MPLS (T-

MPLS) networks
ITU-T Y.1711 Operation & Maintenance mechanism for

MPLS networks

ITU-T Y.1720 Protection switching for MPLS networks
ITU-T Y.1561 Performance and availability parameters for

MPLS networks
ITU-T G.8110 MPLS layer network architecture
ITU-T G.8110.1 Application of MPLS in the transport

network
ITU-T G.8121 Characteristics of transport MPLS equipment

functional blocks
ITU-T Y.1710 Requirements for OAM functionality for

MPLS networks
RFC 2702 Requirements for traffic engineering over

MPLS
RFC 2205 Resource Reservation protocol (RSVP)-

version 1 functional specification
RFC 3031 MPLS architecture
RFC 3469 Framework for multi-protocol label

switching (MPLS)-based recovery
RFC 3811 Definitions of textual conventions for

multiprotocol label switching (MPLS)
management
RFC 3812 Multiprotocol label switching (MPLS) traffic

engineering management information base
RFC 3813 Multiprotocol label switching (MPLS) label

switching router (LSR) management
information base
RFC 3814 Multiprotocol label switching (MPLS)

forwarding equivalence class to next hop
label forwarding entry (FEC-To-NHLFE)
management information base
RFC 4220 Traffic engineering link management

information base
RFC 4221 Multiprotocol label switching (MPLS)

management overview
RFC 4377 Operations and management (OAM)

requirements for multi-protocol label
switched (MPLS) networks
RFC 4378 A framework for multi-protocol label

switching (MPLS) operations and
management (OAM)

RFC 3032 MPLS label stack encoding
RFC 3036 LDP specification
RFC 3037 LDP applicability
RFC 3209 Extensions to RSVP for LSP tunnels
RFC 3210 Applicability statement for extensions to

RSVP for LSP tunnels
RFC 3215 LDP state machine
RFC 3443 Time to live (TTL) processing in multi-

protocol label switching (MPLS) networks
RFC 3477 Signalling unnumbered links in resource

Reservation protocol - traffic engineering
(RSVP-TE)
RFC 3478 Graceful restart mechanism for label

distribution protocol
RFC 3612 Applicability statement for restart

mechanisms for the label distribution
protocol (LDP)
RFC 3815 Definitions of managed objects for the

multiprotocol label switching(MPLS), label
distribution protocol(LDP)
RFC 3936 Procedures for modifying the resource

reservation protocol(RSVP)
RFC 4090 Fast reroute extensions to RSVP-TE for LSP

tunnels
RFC 4182 Removing a restriction on the use of MPLS

explicit NULL
RFC 4201 Link bundling in MPLS traffic engineering

(TE)
draft-ietf-mpls-soft-preemption-08 MPLS traffic engineering soft preemption
RFC 3609 Tracing requirements for generic tunnels
RFC 4204 Link management protocol (LMP)
RFC 4327 Link management protocol (LMP)

management information base (MIB)

PWE3 Standard
RFC 3916 Requirements for pseudo-wire emulation

edge-to-edge (PWE3)
RFC 3985 Pseudo wire emulation edge-to-edge (PWE3)

architecture
RFC 4197 Requirements for edge-to-edge emulation of

time division multiplexed (TDM) circuits
over packet switching networks
RFC 4385 Pseudowire emulation edge-to-edge (PWE3)

control word for use over an MPLS PSN
RFC 4446 IANA allocations for pseudowire edge to

edge emulation (PWE3)
RFC 4447 Pseudowire setup and maintenance using the

label distribution Protocol (LDP)
RFC 4448 Encapsulation methods for transport of

Ethernet over MPLS networks
RFC 4720 Pseudowire emulation edge-to-edge (PWE3)

frame check sequence retention
RFC 4553 Structure-agnostic time division

multiplexing (TDM) over packet (SAToP)
draft-ietf-pwe3-cesopsn-07 Structure-aware TDM circuit emulation

service over packet switched network
(CESoPSN)
draft-ietf-pwe3-vccv-11 Pseudo wire virtual circuit connectivity

verification (VCCV)
draft-ietf-pwe3-segmented-pw-03 Segmented pseudo wire
draft-ietf-pwe3-ms-pw-requirements-03 Requirements for inter domain pseudo-wires
draft-ietf-pwe3-ms-pw-arch-02 An architecture for multi-segment pseudo

wire emulation edge-to-edge
Layer 2 Protocol Standard

RFC 4541 Considerations for internet group

management protocol (IGMP) and multicast
listener discovery (MLD) snooping switches
IEEE 802.3 (Clause43) Link aggregation

IEEE 802.1Q (Clause13) The multiple spanning tree protocol (MSTP)
RFC 0826 Ethernet address resolution protocol
RFC 3046 DHCP relay agent information option
QoS Standard
ITU-T Y.1291 An architectural framework for support of

quality of service (QoS) in packet networks
MEF MEF10 Ethernet services attributes phase 1
RFC 3289 Management information base for the

differentiated services architecture
RFC 3644 Policy quality of service (QoS) Information

model
RFC 3670 Information model for describing network

device QoS datapath mechanisms
RFC 2212 Specification of guaranteed quality of service
RFC 2474 Definition of the differentiated services field

(DS Field) in the IPv4 and IPv6 headers
RFC 2475 An architecture for differentiated services
RFC 2597 Assured forwarding PHB group
RFC 2697 A single rate three color marker
RFC 2698 A two rate three color marker
RFC 3140 Per hop behavior identification codes
RFC 3246 An expedited forwarding PHB (Per-hop

behavior)
RFC 3270 Multi-protocol label switching (MPLS)

support of differentiated services
RFC 3564 Requirements for support of differentiated

services-aware MPLS traffic engineering
RFC 4124 Protocol extensions for support of diffserv-

aware MPLS traffic engineering
RFC 4125 Maximum allocation bandwidth constraints

model for diffserv-aware MPLS traffic
engineering

RFC 4127 Russian dolls bandwidth constraints model

for diffserv-aware MPLS traffic engineering
RFC 4128 Bandwidth constraints models for

differentiated services (Diffserv)-aware
MPLS traffic engineering
ATM Standard
RFC4717 Encapsulation Methods for Transport of

Asynchronous Transfer Mode (ATM) over
MPLS Networks
RFC4816 Pseudowire Emulation Edge-to-Edge

(PWE3) Asynchronous Transfer Mode
(ATM) Transparent Cell Transport Service
RFC2684 Multiprotocol Encapsulation over ATM

Adaptation Layer 5
ITU-T I.610 B-ISDN operation and maintenance

principles and functions
AF-PHY-0086.001 AF-PHY-0086.001 Inverse Multiplexing for

ATM Specification Version 1.1
AF-TM-0121.000 Traffic Management Specification
SDH Standard
ITU-T G.703 Physical/electrical characteristics of

hierarchical digital interfaces
ITU-T G.707 Network node interface for the synchronous

digital hierarchy (SDH)
ITU-T G.773 Protocol suites for Q-interfaces for

management of transmission systems
ITU-T G.841 Types and characteristics of SDH network

protection architectures
ITU-T G.957 Optical interfaces for equipments and

systems relating to the synchronous digital
hierarchy

Product Description B Glossary
B Glossary
ACL Access control list. A list of sequential instructions that are composed
of permit|deny statements. In firewall, the ACL is used on router
interfaces so that the router can determine which data packets to receive
and which to refuse. In QoS, the ACL is also used for flow
classification.
ATM The asynchronous transfer mode (ATM) is designed to transfer voice,

video, and other multimedia data that requires short bursts of large
quantities of data that can survive small losses but must be broadcast
in real time. ATM uses uniform 53-byte cells. (Each cell has a 5-byte
address header and 48 bytes of data.) These short, standardized cells
can be processed through a digital ATM switch very quickly, allowing
for data transmission speeds surpassing 600 Mbit/s.
aggregation A collection of objects that makes a whole. An aggregation can be a

concrete or conceptual set of whole-part relationships among objects.
BDI When detecting a defect, the sink node of a LSP uses backward defect
indication (BDI) to inform the upstream end of the LSP of a
downstream defect along the return path.
BTS Base transceiver station. A station used to transport services and

signaling through air interfaces. A BTS includes the baseband
processing unit, wireless equipment, and antenna.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential B-1

B Glossary Product Description
CES Circuit emulation service. A service defined by the ATM Forum to

provide a virtual connection that emulates a constant bit rate (CBR)
connection with dedicated bandwidth. This specification supports the
emulation of existing TDM connections across ATM networks in
particular.
colored packet A packet whose priority is determined by defined colors.
concatenation A process that combines multiple virtual containers. The combined

capacities can be used a single capacity. The concatenation also keeps
the integrity of bit sequence.
control plane A set of communicating entities that are responsible for the
establishment of connections including set-up, release, supervision and
maintenance. A control plane is supported by a signaling network.
CoS Class of service (CoS) is a queuing discipline. An algorithm compares

fields of packets or CoS tags to classify packets and to assign to queues
of differing priority. CoS does not ensure network performance or
guarantee priority in delivering packets.
dual-homing A network topology in which a device is connected to the network at

two independent access points. One point is the primary connection
and the other a standby connection that is activated in the event of a
failure of the primary connection.
E-LAN The Ethernet LAN that provides services through a non-traditional

network. The media of an E-LAN is different from the traditional media
of a LAN.
E-Line The Ethernet line that provides the Ethernet private line service, the
Ethernet-based Internet access service, and the point-to-point Ethernet
VPN service.
E-Tree The Ethernet multicast service, that is, the point-to-multipoint E-LAN
service.
FDI Forward defect indication (FDI) is generated and traced forward to the
sink node of the LSP by the node that first detects defects. It includes
fields to indicate the nature of the defect and its location. Its primary
purpose is to suppress alarms being raised at affected higher level client
LSPs and (in turn) their client layers.
B-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

FEC Forwarding equivalence class. A term used in multiprotocol label

switching (MPLS) to describe a set of packets with similar or identical
characteristics which may be forwarded the same way; that is, they may
be bound to the same MPLS label.
forwarding plane Also referred to as the data plane. The forwarding plane is connection-
oriented, and can be used in Layer 2 networks such as an ATM network.
frame A repetitive set of consecutive timeslots constituting a complete cycle

of a signal or of another process in which the relative position of each
timeslot in the cycle can be identified.
hop A network connection between two distant nodes. For Internet

operation a hop represents a small step on the route from one main
computer to another.
IGMP snooping Internet group management protocol snooping. A mechanism used for
signaling from the host to the router, in the end network of IP multicast.
Through IGMP, the host joins or quits a multicast group, and the router
determines whether multicast group members exist in the downstream
network segment.
IGP Interior gateway protocol. A routing protocol that is used within an

autonomous system. The IGP runs in small-sized and medium-sized
networks. The commonly used IGPs are the routing information
protocol (RIP), the interior gateway routing protocol (IGRP), the
enhanced IGRP (EIGRP), and the open shortest path first (OSPF).
IMA Inverse multiplexing for ATM (IMA) demultiplexes a concentrated

flow of ATM cells into multiple lower-rate links, and at the remote end
multiplexes these lower-rate links to recover the original concentrated
flow of ATM cells.
IS-IS Intermediate system to intermediate system. A protocol used by

network devices (routers) to determine the best way to forward
datagrams or packets through a packet-based network. It is a dynamic
routing protocol designed by ISO.
L2VPN Layer 2 virtual private network. A virtual private network realized in

the packet switched (IP/MPLS) network by Layer 2 switching
technologies.
LAG Link aggregation group. A group in which multiple links connected to

the same equipment are bundled together to increase the bandwidth and
improve the link reliability. An LAG can be regarded as one link.

LDP Label distribution protocol. A protocol using which two label switch
routers (LSR) exchange label mapping information. The two LSRs are
called LDP peers and the exchange of information is bidirectional. LDP
is used to build and maintain LSR databases that are used to forward
traffic through MPLS networks.
link A "topological component" that provides transport capacity between

two endpoints in different subnetworks via a fixed (that is, inflexible
routing) relationship.
LSP Label switch path. An ingress and egress switched path built through
a series of LSRs to forward the packets of a particular FEC using a label
swapping forwarding mechanism.
LSR Label switch router. A device located in the core of the network that
switches labeled packets according to precomputed switching rules.
This device can be a switch or a router.
MPLS L2VPN The MPLS L2VPN provides the Layer 2 VPN service based on an
MPLS network. In this case, on a uniform MPLS network, the carrier
is able to provide Layer 2 VPNs of different media types, such as ATM,
FR, VLAN, Ethernet, and PPP.
MPLS OAM The MPLS OAM provides continuity check for a single LSP, and
provides a set of fault detection tools and fault correct mechanisms for
MPLS networks. The MPLS OAM and relevant protection switching
components implement the detection function for the CR-LSP
forwarding plane, and perform the protection switching in 50 ms after
a fault occurs. In this way, the impact of a fault can be lowered to the
minimum.
MPLS TE tunnel In the case of reroute deployment, or when traffic needs to be

transported through multiple trails, multiple LSP tunnels might be used.
In traffic engineering, such a group of LSP tunnels are referred to as
TE tunnels. An LSP tunnel of this kind has two identifiers. One is the
Tunnel ID carried by the SENDER object, and is used to uniquely
define the TE tunnel. The other is the LSP ID carried by the
SENDER_TEMPLATE or FILTER_SPEC object.
MSTP The multiple spanning tree protocol (MSTP) can be used in a loop
network. Using an algorithm, the MSTP blocks redundant paths so that
the loop network can be trimmed as a tree network. In this case, the
proliferation and endless cycling of packets is avoided in the loop
network.
multicast To transmit data to multiple recipients on the network at the same time
using one transmission stream to the switches, at which point data are
distributed out to the end users on separate lines.

NSAP Network service access point. The point at which the OSI Network
Service is made available to a Transport entity. The NSAPs are
identified by OSI Network Addresses. The NSAP is a generic standard
for a network address consisting of 20 octets. ATM has specified E.164
for public network addressing and the NSAP address structure for
private network addresses.
packet The information unit at the network layer.
PDU Packet data unit. The unit that is transported in a local interconnect
network (LIN) diagnostic frame. A PDU used for node configuration
is a complete message.
POS Packet over SDH/SONET. A MAN and WAN technology that provides
point-to-point data connections. The POS interface uses SDH/SONET
as the physical layer protocol, and supports the transport of packet data
(such as IP packets) in MAN and WAN.
PW A pseudo wire is an emulated point-to-point connection over a packet

switched network that allows the interconnection of two nodes with
any L2 technology.
PWE3 Pseudo wire emulation edge to edge. In a packet switched network

(PSN), a Layer 2 service bearing technology that emulates as truly as
possible the basic behaviors and characteristics of ATM services, frame
relay services, Ethernet services, low speed TDM services, SONET/
SDH services, and other services.
QoS Quality of service. The capability of equipment to provide different

levels of quality for different services.
route A path for traffic between two designated points.
switching The process of interconnecting functional units, transmission channels

or telecommunication circuits for as long as is required to convey
signals.

synchronous status A message that is used to transmit the quality levels of timing signals
message on a synchronous timing link. By reading the SSM, a node clock in the
SDH network and the synchronization network obtains the upstream
clock information. The SSM performs relevant operations (such as
tracing, switching, and hold-over) on the clock of the local node, and
then transmits the synchronization information of the local node to the
downstream.
traffic engineering Traffic engineering (TE) encompasses traffic management, capacity

management, traffic measurement and modelling, network modelling,
and performance analysis.
tunnel A information transmission channel that is set up between two entities

in the application of VPN. A tunnel provides sufficient security to
prevent intrusion to the VPN internal information.
V-NNI A virtual network-network interface (V-NNI) is a network-side

interface.
VPLS Virtual private LAN service. A service that, with the assistance of an
IP public network, realizes the interconnection of LANs through a
VPN. The VPLS is the extension of a LAN in the IP public network.
VPWS Virtual Private Wire Service. A virtual private wire service is a point-
to-point circuit (link) connecting two customer edge devices. The link
is established as a logical through a packet switched network. The CE
in the customer network is connected to a PE in the provider network
via an attachment circuit. The attachment circuit is either a physical or
a logical circuit.
V-UNI A virtual user-network interface is a client-side interface.

Product Description C Acronyms and Abbreviations
C Acronyms and Abbreviations
ACL Access Control List
AF Assured Forwarding
APS Automatic Protection Switching
ARP Address Resolution Protocol
ATM Asynchronous Transfer Mode
ATM PVC ATM Permanent Virtual Circuit
BDI Backward Defect Indicator
BSC Base Station Controller
BTS Base Transceiver Station
CES Circuit Emulation Service
CSPF Constraint-based Shortest Path First
CV Connectivity Verification
CWDM Coarse Wavelength Division Multiplx
DCC Data Communication Channel
Issue 01 (2009-06-30) Huawei Proprietary and Confidential C-1

C Acronyms and Abbreviations Product Description
DCN Data Communication Network
DWDM Dense Wavelength Division Multiplexing
E-Aggr Ethernet Aggregation
E-LAN Ethernet LAN
E-Line Ethernet Line
ECC Embedded Control Channel
EMC Electromagnetic Compatibility
EPL Ethernet Private Line
EPLAN Ethernet Private LAN
ETH-CC Ethernet Continuity Check
ETH-LB Ethernet Loopback
ETH-LT Ethernet Link Trace
ETS European Telecommunication Standards
ETSI European Telecommunications Standards

Institute
EVPL Ethernet Virtual Private Line
EVPLAN Ethernet Virtual Private LAN
FDI Forward Defect Indicator
FEC Forwarding Equivalence Class
FFD Fast Failure Detection
FRR Fast Reroute
GCP GMPLS Control Plane
GE Gigabit Ethernet
GFP Generic Framing Procedure
GR Graceful Restart
C-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

HA High Availability
H-QoS Hierarchical Quality of Service
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics

Engineers
IGP Interior Gateway Protocol
IGMP Internet Group Management Protocol
IGMP Snooping Internet Group Management Protocol

Snooping
IMA Inverse Multiplexing for ATM
IP Internet Protocol
IS-IS Intermediate System to Intermediate System
ITU-T International Telecommunication Union -

Telecommunication Standardization Sector
L2VPN Layer 2 Virtual Private Network
L3VPN Layer3 Virtual Private Network
LACP Link Aggregation Control Protocol
LAG Link Aggregation Group
LAN Local Area Network
LDP Label Distribution Protocol
LMSP Linear Multiplex Section Protection
LPT Link State Path Through
LSA Link State Advertisement
LSP Label Switch Path
LSR Label Switch Router

C Acronyms and Abbreviations Product Description
MAC Media Access Control
MEP Maintenance End Point
MIP Maintenance Intermediate Point
ML-PPP Multilink Point-to-Point Protocol
MP Merge Point
MPLS Multiprotocol Label Switching
MPLS TE Multiprotocol Label Switching Traffic

Engineering
MSP Multiplex Section Protection
MSTP Multiple Spanning Tree Protocol
NSAP Network Service Access Point
NSF Non-Stop Forwarding
OAM Operation, Administration and Maintenance
PDH Plesiochronous Digital Hierarchy
PE Provider Edge
PLR Point of Local Repair
POS Packet over SDH/SONET
PPP Point-to-Point Protocol
PTN Packet Transport Network
PW Pseudo Wire
QoS Quality of Service
C-4 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

RSTP Rapid Spanning Tree Protocol
RSVP Resource Reservation Protocol
SDH Synchronous Digital Hierarchy
SLA Service Level Agreement
STP Spanning Tree Protocol
TE Traffic Engineering
TDM Time Division Multiplexing
V-NNI Virtual Network-Network Interface
V-UNI Virtual User-Network Interface
VC Virtual Channel
VCC Virtual Channel Connection
VCCV Virtual Circuit Connectivity Verification
VLAN Virtual Local Area Network
VP Virtual Path
VPC Virtual Path Connection
VPLS Virtual Private LAN Service
VPN Virtual Private Network
VPWS Virtual Private Wire Service
WTR Wait to Restore

Product Description Index
Index
A
I
access capability, 2-3
ACL, 5-22 IGMP Snooping, 5-20
application inband DCN, 2-15
E-LAN service, 9-7 interface type
E-Line service, 9-6 service interface, 2-5
mobile service, 9-2 IP tunnel, 5-15
IS-IS routing protocol, 5-6
B
L
BFD, 5-23
l3vpn service
C introduction, 4-16
laser class, 10-21
clock, 2-14 log
compliant standard list, A-1 security log, 8-3
Syslog, 8-3
D
DCN, 2-15
M
diagnosis and debugging, 7-3 monitoring and maintenance, 7-2
MPLS
E basic concept, 5-3
equipment feature, 5-5
E-Aggr service, 4-12 generation background, 5-3
E-LAN service, 4-11 signaling, 5-14
E-Line service, 4-11 system structure, 5-5
environment requirement MPLS OAM, 2-13
storage, 10-25 MSTP, 5-21
Transportation, 10-27
Ethernet OAM, 2-13
expansion and upgrade, 7-3
N
network application, 1-3
G network management system, 7-3
NSF, 2-14
GRE tunnel, 5-15
O
H
OAM
hardware Ethernet OAM, 2-13
board, 3-9 MPLS OAM, 2-13
slots for boards, 3-10 security management, 8-1
structure, 3-4 offload solution, 9-9
subrack, 3-6
Issue 01 (2009-06-30) Huawei Proprietary and Confidential i-1

Index Product Description
operation and configuration tool service model, 4-2

T2000, 7-2 service type, 2-3
service interface type, 2-5
P service processing
ATM service processing, 4-8
protection CES service processing, 4-9
1+1 protection for PIU, 6-5 Ethernet service processing, 4-7
1+1 protection for SCA, 6-3 software
1+1 protection for XCS, 6-4 architecture, 3-12
capability, 2-11 board software, 3-15
FRR protection, 6-8 NE software, 3-14
IMA, 6-17 switching capability, 2-3
LAG protection, 6-10 system
linear MSP protection, 6-13 functional modules, 3-2
ML-PPP protection, 6-16
MPLS Tunnel 1+1 protection, 6-6 T
MPLS Tunnel 1:1 protection, 6-7
MSTP protection, 6-11 technical specification
TPS protection, 6-2 AD1, 10-13
protocol ASD1, 10-14
IS-IS, 5-6 cabinet, 10-2
MSTP, 5-21 CD1, 10-13
PWE3, 5-15 clock interface, 10-22
CMR2, 10-19
Q CMR4, 10-18
D75, 10-17
QoS EFG2, 10-11
CAR, 5-18 EG16, 10-7, 10-8
congestion management, 5-19 EMC, 10-23
DiffServ, 5-17 FAN, 10-21
flow classification, 5-17 MD1, 10-13
HQoS, 5-19 MP1, 10-12
overview, 2-12 MQ1, 10-13
queue scheduling, 5-19 PIU, 10-21
shaping, 5-19 POD41, 10-16
reliability, 10-23
S SCA, 10-20, 10-20
subrack, 10-2
safety certification, 10-24 system performance, 10-3
security XCS, 10-21, 10-21
access control, 8-2
ACL, 8-2
authentication, 8-2
authorization, 8-2
network, 8-2
password, 8-3
security log, 8-3
Syslog, 8-3
system, 8-3
user name, 8-3
service
ATM service, 4-13
CES service, 4-14
Ethernet service, 4-9
E-Aggr service, 4-12
E-LAN service, 4-11
E-Line service, 4-11
IMA service, 4-13
i-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)


PTN3900 Product Description

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

PTN3900 Product Description

Transféré par

Droits d'auteur :

Formats disponibles

00534442

OptiX PTN 3900 Packet Transport Platform of PTN Series

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX PTN 3900 V100R002C00

OptiX iManager T2000 V200R007C03

l Network Planning Engineers

1 Overview Describes the equipment features and the position of the

Issue 01 (2009-06-30) Huawei Proprietary and Confidential iii

3 System Architecture Describes the functional modules, hardware structure and

4 Services Describes the services of the equipment.

5 Key Features Describes the main features of the equipment.

6 Protection Describes the equipment-level protection and network-level

7 Operation, Administration Describes the operation, maintenance and management

8 Security Management Describes the main technical characteristics of the

9 Networking Application Describes the application of the equipment on mobile

10 Technical Specifications Describes the technical specifications of the equipment.

B Glossary Lists the glossary used in this document.

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

iv Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Indicates a potentially hazardous situation, which if not

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Issue 01 (2009-06-30) Huawei Proprietary and Confidential v

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Double-click Press the primary mouse button twice continuously and

Update in 01 (2009-06-30) Based on Product Version V100R002C00

vi Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Update in Issue 07 (2009-06-01) Based on Product Version V100R001

Update in Issue 06 (2009-04-20) Based on Product Version V100R001

Update in Issue 05 (2009-02-20) Based on Product Version V100R001

Update in Issue 04 (2009-01-10) Based on Product Version V100R001

Update in Issue 03 (2008-10-20) Based on Product Version V100R001

Issue 01 (2009-06-30) Huawei Proprietary and Confidential vii

l Chapter 2 Functions and Features and Chapter 6 Protection:

Update in Issue 02 (2008-08-20) Based on Product Version V100R001

Update in Issue 01 (2008-05-10) Based on Product Version V100R001

viii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

About This Document...................................................................................................................iii

2 Functions and Features..............................................................................................................2-1

Issue 01 (2009-06-30) Huawei Proprietary and Confidential ix

x Huawei Proprietary and Confidential Issue 01 (2009-06-30)

7 Operation, Administration and Maintenance......................................................................7-1

Issue 01 (2009-06-30) Huawei Proprietary and Confidential xi

10.3.18 Technical Specification of the CMR2............................................................................................10-19

A Compliant Standards and Protocols.....................................................................................A-1

xii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Figure 1-1 Appearance of the OptiX PTN 3900..................................................................................................1-2

Issue 01 (2009-06-30) Huawei Proprietary and Confidential xiii