Network Design Scheme For XX Telecom Pilot Office (LLD & DD)

21/12/7 Security Level:
Network Design
Scheme for XX
Telecom Pilot Office
(LLD & DD)
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Contents
• Requirement Analysis
• Network Planning
• Network Design
 Network Topology
 DCN Design
 Parameter Design for NNI Packet Ports
 MPLS Design
 Service and PW Design
 Tunnel Design
 MPLS OAM Design
 Tunnel APS Design
 Label Design
 QoS Design
1. Requirement Analysis
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

Service Requirement Overview
 Service carrier
 The design should focus on current requirements and the foreseeable service requirements in the future.
 For example, the network of the pilot office and future commercial networks primarily carry Ethernet
services that are transmitted back by CDMA BTSs, and other services (such as services of VIP customers
from the government and business sectors).
 Expandability
 The design should consider possible network expansions and changes in the future.
 For example, the network of the pilot office should be capable of smoothly expanding to a large commercial
network.
 High reliability
 The target of high reliability is to protect the network against possible risks that usually include fiber link
failures, single point failures of NEs, board failures, and shared risk link group (SRLG) failures.
 Design approaches: The design should integrate the tunnel layer (tunnels), the network layer (links), the
equipment layer (CircuitPack), and routing policies.
 Easy management and maintenance

 The design should make a packet transmission easy-to-manage and easy-to-maintain as an SDH network.
 Design approaches: (1) private line services; (2) MPLS/Ethernet service OAM, (3) network management
and maintenance based on design documentation

Example: Service Carrier Requirements
 Access capabilities of CDMA BTSs
 Long term: Totally 600 BTSs are planned, all of which are to be connected to the
backbone layer through five backbone transmission nodes at Jiebei, Yinzhong, Shiqi,
Panhuo, and Qiuai respectively. On average, 120 BTSs are connected to a transmission
subnet, where a backbone transmission node is located.
 Trial operation term: Ten BTSs are connected for test.
 Service models of CDMA BTSs

 Services of the BTSs in Yinzhong region are converged to the BSCs at Jiebei and
Yinzhong.
 Service distribution:
 Long term: The ratio of BTS quantity at Jiebei to those at Yinzhon is 4/1, that is, at least 480 BTSs
are connected to the Jiebei BSC and at least 120 BTSs to the Yinzhong BSC.
 Trial operation term: All the 10 BTSs are connected to the Jiebei BSC.
 Bandwidth: The bandwidth of 10 Mbit/s is planned for each BTS.
 Other services
 The office direction and bandwidth of services are to be determined.

Example: Network Expansion Requirements
 Backbone layer expansion

 The design focuses on the future connection between nodes in the
Jiebei region and those on the backbone layer of other regions.
 Convergence and access layer expansion

 The design focuses on the connection between the nodes on the
backbone layer in the Yinzhong region and the subnets on the
convergence/access layers.

2. Network Planning

Network Planning Contents of LLD & DD
 This design scheme does not focus on network planning itself, but the basis and
principles of network design, including low-level design (LLD) and detailed design (DD).
This information is usually provided by the customer in their network
plan/requirements or by the M&S Dept. in the high-level design (HLD).
 When network planning itself does not provide design basis or principles, we can make
reasonable assumptions and use them upon approval.
 Network planning (HLD) usually includes the following items:

 Characteristics and trend of services and networking
 Network topology/structure
 Carrier mode
 Network protection mode
 Service routing policy
 OAM mode
 Synchronization mode
 DCN and NMS architecture
 Most of these items are described briefly with a focus on scale and rule.

Example: Overall Network Structure
The backbone layer is
composed of 10GE rings.
Backbone layer
The backbone layer and the convergence
layer are connected through shared NEs.
The convergence layer is
composed of GE rings.
Convergence layer
The backbone layer and the access layer are connected through shared NEs.
Access layer The convergence layer and the access layer are intersectant or tangent.
The access layer is composed of GE rings or links.
 Subnets on the backbone layer, convergence layer, and access layer

are pure OSN/PTN networks or hybrid networks.

Example: Network Carrier Mode – PWE3
ETH Service
NE NE NE NE
Ingress PW Egress
Ingress Transit Tunnel Transit Egress

Ingress Egress
Tunnel Tunnel Tunnel
Connection Connection Connection
Ingress Egress Ingress Egress Ingress Egress
ETH Link ETH Link ETH Link
 All the network-to-network interface (NNI) links on the network of the pilot office are carried by MPLS
PWs, and all tunnels are carried by static signaling. Ethernet private line (EPL) services constitute the
majority of network services.
 Comparison of MPLS PWE3 and SDH network objects:

 The ETH service corresponds to E1 circuits, PWs correspond to VC-12 channels, and tunnels correspond to VC-4 channels.
 VC-12 and VC-4 channels have fixed bandwidth, while PWs and tunnels have changeable bandwidth.
 VC-12 and VC-4 channels are identified by timeslot, while PWs and tunnels are identified by label.

Example: Network Protection Mode
 Tunnel/LSP APS based network protection mode is adopted to implement
service protection switching within 50 ms.
Shiqi Jieb Qiua
ei i
Tunnel/LSP
APS protection Working tunnel
group
Protection tunnel
Yinzhong Panhuo
 For subnets with chain topology (such as ring links), a working tunnel and
a protection tunnel are configured for a single chain. When the single
chains form a ring, you can change the routes of the protection tunnels to
Shiqi Jieb Qiuai
protect the ring. Working and protection ei
tunnels with the same
route on the chain Working tunnel
Chaoyang
Yinzhong Protection tunnel Panhuo

NMS Through In-Band DCN
 The network of the pilot office is composed of OSN and PTN NEs.
 OSN NEs support in-band DCN communication over IP or HWECC.

PTN NEs support in-band DCN communication over IP.
 All the OSN 3500 NEs can function as IP or HWECC gateways.
 Pure OSN subnets run HWECC, pure PTN subnets run IP, and
OSN/PTN hybrid subnets run IP.

3. Network Design

General Requirements for Network Design
 LLD & DD orient toward network delivery, management, and maintenance.
 Different from HLD, network design (LLD & DD) comes to details.
 Output parameters of LLD & DD should be suitable to be input parameters of

network debugging tools and the NMS.
 LLD & DD in the following two modes should be made before and during the
delivery of network software debugging:
 Advance design: Network design is completed before software debugging.
 Synchronous design: Network design is performed during the software debugging
process, providing design parameters for each software debugging link before the start of
the link.

Contents of Network Design
 Network topology  Tunnel design
 DCN design  MPLS OAM design
 Parameter design for NNI packet  Tunnel APS design

ports/user network interface (UNI)
ports  Label design
 MPLS design  QoS design
 Network synchronization design  Ethernet OAM (services and links)

(optional)
 Service and PW design

3.1 Network Topology

Network Topology Design
 In HLD and DD phases, the task of network topology design

is to break down the HLD topology to physical ports, that is,
define cable connections.
 Key points of topology (cable connection) design:

 DCN and synchronization support by device models: Use ports that do
not support DCN or synchronization as UNIs instead of NNIs.
 Tunnel ASP cross-ring protection: Try to keep routes of cross-ring
tunnels with identical protection properties passing through ports on
associated boards. This is also a solution to SRLG problems.

Structure of the Network of the Pilot Office
Shiqi Jiebei Qiuai
Backbone layer
Ring#1
Yinzhong Panhuo
Wuxiang Zhanqi
Convergence layer Qiuai

Ring#2
Mozhi Tangxi
Yinzhou
Shundeli plant Hongsen Wood Wuxiang Zhanqi
Access layer
Ring#3 L#1
Jishigang Shiqi Mozhi Dongwu
Telecom
Jinlong
Yunlong L#2 Yinzhou
Telecom Dongwu II L#3
Ring#4 Yinzhou
Yinzhong Gaoqian
Yinzhou Hengxi Qianhurenjia Yinzhou Binhai
Mozhi
Telecom Community

Example: Network Topological View
Yinzhou Binhai
Wuxiang Zhanqi
Community
s3p2 s1p1
s3p1 s4p1 s3p1
Yinzhou Shundeli
Hongsen Wood Ring#2 s3p2 s4p1 L#3
plant s3p1
s13p2 s13p1
Jiebei Jiebei
Dongwu Jinlong
s13p1 s13p2 BSC#2 BSC#3 s4p1
L#1 s1p1
Ring#3 Yinzhou Dongwu II
s2p1
s13p2 s13p1 Shiqi s33p1 s33p2 s3p1
s13p1 s13p9 s32p1
s5p1 s11p1 s13p1 s11p1 Yinzhou Gaoqian
Jishigang Telecom Qiuai s4p1
s3p1 s13p1 s3p2 s3p1
Jieb s31p1
s4p1 s3p1 s4p1
s13p2
Yunlong ei
Ring#1 Mozhi Tangxi
Telecom s13p1 s13p1 s5p1 s3p1 L#2
Ring#4 s3p1 s5p1
s13p2
s13p1 s13p9
Qianhurenjia
ETH Yinzhong Panhuo
Yinzhou Hengxi Legend:
Telecom
LAN2
PTN 3900 OSN 3500
Legend: PTN 1900
5pts YinzhongT2000 OSN 1500
10GE
2pts PTN
T2000
GE 950/910
1pt
FE BSC BTS

3.2 DCN Design

DCN Design
 DCN design should include the following items:

 DCN subnet division (LLD)
 DCN communication protocol design (LLD)
 DCN port design (DD)
 Management IDs and IP addresses of NEs (DD)
 Key points of design:

 DCN subnet division for large networks
 Communication protocol design and gateway selection for OSN/PTN hybrid
networks
 Mapping between the management IDs and the IP addresses of NEs
 Effect of the DCN status of UNI ports on network security

DCN Communication Protocol Design
Zhanqi Yinzhou Binhai
Wuxiang Community
Yinzhou
Shundeli plant Hongsen Wood
Dongwu
Jiebei BSC Jinlong
Yinzhou
Dongwu II
Jishigang Qiuai Yinzhou
Telecom Gaoqian
Shiqi Jiebei
Yunlong
Telecom Mozhi Tangxi
Yinzhong Panhuo Qianhurenjia

Yinzhou Hengxi
Telecom
By default, the reserved VLAN ID (4094) is used for in-band DCN communication.
YinzhongT2000 Description:
Legend: 1. All IP links form an OSPF domain with the domain
To: NMS number as 0.0.0.0.
HWECC link network in the 2. The OSN 3500 NEs at Yinzhong and Shiqi act as
office
IP-HWECC gateways.
IP link
3. In-band DCN packets on the link layer have the
VLAN ID as 4094 and bandwidth as 512 kbit/s.
Management IDs and IP Addresses of NEs
ID: 2009/88 ID: 2008/88
IP: 129.88.7.217/16 IP: 129.88.7.216/16 Yinzhou Binhai
Wuxiang Zhanqi Community
ID: 2011/88 ID: 2010/88
IP: 129.88.7.219/16 IP: 129.88.7.218/16
Yinzhou Shundeli plant Hongsen Wood ID: 2017/88

Dongwu ID: 2013/88
IP: 129.88.7.225/16
Jiebei BSC Jinlong IP: 129.88.7.221/16
Yinzhou ID: 2014/88

ID: 2003/88
IP: 129.88.7.211/16 Dongwu II IP: 129.88.7.222/16
Jishigang
Qiuai Yinzhou
Telecom ID: 2015/88
Gaoqian IP: 129.88.7.223/16
ID: 2012/88
IP: 129.88.7.220/16 Shiqi Jiebei
Yunlong ID: 2005/88 ID: 2004/88
IP: 129.88.7.213/16 IP: 129.88.7.212/16
Telecom
ID: 2018/88 Mozhi Tangxi
IP: 129.88.7.226/16 ID: 2006/88 ID: 2007/88
IP: 129.88.7.214/16 IP: 129.88.7.215/16
Yinzhou Hengxi
Telecom Yinzhong Panhuo
Qianhurenjia ID: 2016/88
IP: ID: 2001/88
ID: 2019/88 ID: 2002/88 IP: 129.88.7.224/16
129.88.0.1/16 IP: 129.88.7.209/16
IP: 129.88.7.227/16 IP: 129.88.7.210/16
YinzhongT2000
Description:
To: NMS
IP: 1. NEs of the pilot office network use 88 as the extended ID to be
network in the
129.9.1.151/24
distinguished from the NEs on the existing network. The basic IDs
office
of the NEs of the pilot office network range from 2001 to 2019.
This design scheme does not include a DCN 2. The network segment IP address129.88.0.0/16 is used as the
subnet division plan, but designs management IDs NE management IP address, and the host IP address for NE
and IP addresses of NEs management is calculated base on the basic IDs of NEs. For
for easy integration with the existing network. example, the basic ID 2001 corresponds to host IP address
129.88.7.209.
DCN Design Summary
 The OSN access equipment supports complete remote debugging after the
completion of local installation, power-on, and cable connection.
 If VLAN ID conflicts occur between service packets and in-band DCN packets,
reset a VLAN ID for in-band DCN packets.
 The network of the pilot office is a small network, so the DCN subnet division
scheme is not provided. It is recommended that DCN subnet division and
protection schemes are designed at the link layer according to the network
topology when the network is expanded to 50 NEs. Thus, a DCN subnet
includes 50 or less NEs.
 For designed DCN parameters, see the attachment:

3.3 Parameter Design for NNI Packet Ports

NNI Packet Port Parameters
 To implement MPLS PWE3, all NNI packet ports on the

network of the pilot office work in Layer-3 port mode, with the
tunnel status enabled.
 All NNI 10GE ports work in 10GE full-duplex WAN mode.
 All NNI GE ports work in 1000M full-duplex mode.
 All NNI packet ports have their maximum transmission unit

(MTU) value larger than that required by a radio carrier.

Working Mode of NNI Ports
 Auto-negotiation, full-duplex, and half-duplex
 Full-duplex: The port works in two directions at the same time.
Half-duplex: The port works in two directions consecutively.
Auto-negotiation: The port works in full-duplex or half-duplex mode according to protocol settings.
 Full-duplex mode is recommended for NNI ports.
 LAN and WAN modes of 10GE ports

 Interface type:
 10G Base-SR, LR, ER, and ZR ports work in LAN mode.
 10G Base-SW, LW, EW, and ZW ports work in WAN mode.
 Network model:
 WAN ports are defined as equipment ports that are connected to WAN (such as the Internet)
access equipment (such as WAN routers and switches). WAN ports usually support DHCP client.
 LAN ports are defined as ports that are connected to local user equipment (such as hosts). LAN
ports usually support DCHP server for quick configuration of local user equipment for Internet
access.
 The working mode of 10GE ports varies with interface type, and network model when necessary.

3.4 MPLS Design

Basic MPLS Properties
 LSR ID/Node ID
 A globally unique LSR ID is allocated to each NE that is connected to an MPLS link as the node ID on
the control plane.
 The LSR ID of an NE must be different and in a different network segment from the management IP
address of the NE.
 The LSR ID of an NE must be in a different network segment from the NNI port IP addresses of the NE.
 NNI IP address/Port IP address

 Each port of an MPLS link must have an independent IP address that is globally unique.
 Each port IP address of an NE must be different and in a different network segment from the
management IP address of the NE.
 Each port IP address of an NE must be in a different network segment from the LSR ID of the NE.
 Each port IP address of an NE must belong to a different network segment.
 The end IP addresses of an MPLS link must belong to a network segment.
 Ranges of LSR IDs and NNI IP addresses

 A 32-bit IP address ranges from 1.0.0.1 to 223.255.255.254, except for broadcast addresses, network
addresses, and addresses in 127.x.x.x, 192.168.x.x, and 192.169.x.x.

MPLS Design: LSR ID/Node ID
LSR ID: 130.0.0.9 LSR ID: 130.0.0.8 LSR ID: 130.0.0.17
Wuxiang Zhanqi
LSR ID: 130.0.0.11 LSR ID: 130.0.0.10
Yinzhou Shundeli Hongsen Wood Yinzhou Binhai
plant Jiebei BSC Dongwu LSR ID: 130.0.0.13 Community
Jinlong
Yinzhou LSR ID: 130.0.0.14
Dongwu II
Jishigang LSR ID: 130.0.0.3
Telecom Qiua Yinzhou
LSR ID: 130.0.0.15
i Gaoqian
LSR ID: 130.0.0.12
Shiqi Jiebei
Yunlong LSR ID: 130.0.0.5 LSR ID: 130.0.0.4
Telecom
LSR ID: 130.0.0.18
Mozhi Tangxi
LSR ID: 130.0.0.6 LSR ID: 130.0.0.7
Qianhurenjia
Yinzhou Hengxi Yinzhong Panhuo LSR ID: 130.0.0.16
Telecom LSR ID: 130.0.0.1 LSR ID: 130.0.0.2
LSR ID: 130.0.0.19
YinzhongT2000
 An LSR ID is an IP address with a 32-bit mask. For the network of the pilot office, network segment
130.0.0.X is used, where IP addresses from 130.0.0.1 to 130.0.0.19 have been allocated.

MPLS Design: NNI IP Address Wuxiang Zhanqi
18.0.0.37 18.0.0.34 18.0.0.33 18.0.0.77
Yinzhou Shundeli 18.0.0.57 18.0.0.30
plant Hongsen Wood
18.0.0.46 18.0.0.45 18.0.0.78
Jiebei BSC 18.0.0.58
18.0.0.49 18.0.0.42
Dongwu Jinlong
18.0.0.61 Yinzhou Binhai
Community
18.0.0.62
Jiebei Yinzhou Dongwu II
18.0.0.13 18.0.0.10 18.0.0.65
18.0.0.50 18.0.0.41 18.0.0.14 18.0.0.9 18.0.0.38
18.0.0.53 18.0.0.54
18.0.0.66
Shiqi Qiuai Yinzhou
Jishigang
Telecom
18.0.0.17
18.0.0.6 Gaoqian
18.0.0.21 18.0.0.69
Yunlong 18.0.0.70
18.0.0.29
18.0.0.8 18.0.0.22 18.0.0.26
Telecom 2
18.0.0.2
5
18.0.0.85 Mozhi
18.0.0.18 18.0.0.5 Tangxi
18.0.0.81 18.0.0.73
18.0.0.1 18.0.0.2
18.0.0.86 18.0.0.74
18.0.0.90 Yinzhong Panhuo
Qianhure
18.0.0.89
Yinzhou Hengxi njia
Description:
Telecom The allocated NNI IP
addresses of the pilot office Each MPLS NNI IP address on the
network range from 18.0.0.1 to network of the pilot office has a 30-bit
18.0.0.90. mask, that is, 255.255.255.252. Each link
uses an average of four IP addresses.
3.5 Service and PW Design

Service and PW Design
 NE-level service type and network-level service model
 NE-level service type: It refers to the single-site service type configured for an NE,
including private line, private network, and convergence.
 Network-level service model: It refers to the topology of end-to-end services on the whole
network, including point-to-point, single-point convergence, multi-point convergence, and
mesh.
 Tasks of PW design
 Break down the network-level service model to NE-level service types. For example,
break down the convergence service model to NE-level private line services and NE-level
convergence services, calculate PW requirements based on the NE-level service types,
and determine PW objects.
 Key points:
 Private line services are preferred for each management and maintenance.
 The supported service volume of each type varies with device model.
 The QoS scheme may vary with the service and PW design.

Example: Service Carrier Requirements for
the Network of the Pilot Office Yinzhou Binhai
Community
Yinzhou Hongsen Wood

Shundeli plant
Jiebei Jiebei Dongwu Jinlong
BSC#2 BSC#3
Yinzhou Dongwu II
Yinzhou Gaoqian
Jishigang
Telecom
Yunlong
Telecom
Yinzhong
BSC#5 Qianhurenjia
Yinzhou Hengxi Telecom  The network of the pilot office carries the EPL services between the 10 base
stations on one side and Jiebei BSC#2, Jiebei BSC #3, and Yinzhong BSC#5 on
the other. The bandwidth of each private line is as follows: CIR = PIR = 10 Mbit/s.
 Private line services are identified by the VLAN ID, which is identical with the
NodeB services BTS number.

Example: PW Objects on the Network of the
Pilot Office Wuxiang Zhanqi
Yinzhou Binhai
Community
Yinzhou
Jiebei BSC Dongwu Jinlong
Yinzhou Dongwu II
Shiqi
Yinzhou Gaoqian
Jishigang Qiuai
Telecom Jiebei
Yunlong Mozhi Tangxi

Telecom
Qianhurenjia
Yinzhong
Panhuo
Yinzhou Hengxi
Telecom  Ten PW objects are available for carrying NodeB services,
and correspond to the ten base station Ethernet services.
Bidirectional PW object  Each PW object is a bidirectional PW.
carrying NodeB
services
 The PW ID is identical with the PW label.

PW Object Naming Rule
 PW naming rule applies to bidirectional PW objects.
 PW naming rule
Ethernet service ID:PW office direction:tunnel APS ID
 Example: EPL#0002:Jiebei-Yinzhou Shundeli plant:TAPS#0002
 Ethernet service ID
 It is the ID of the Ethernet service that is carried by a PW. For example, EPL#1
stands for the first EPL service carried by a PW.
 PW office direction
 It indicates the start and end NEs of a PW, in the format of NE1 name-NE2 name.
 Tunnel APS ID
 It is the ID of the tunnel APS object that carries a PW.

3.6 Tunnel Design

Tunnel Design
 Tasks of tunnel design:

 Determine tunnels/tunnel APS objects (quantity and office direction)
 Determine the mapping between tunnel and PW
 Name tunnel objects
 Extended discussion:
 Generally, PWs and tunnels are considered as service classification
approaches.
 PW corresponds to VLAN ID, and tunnel corresponds to office
direction and customer.

Principles of Determining Tunnel Objects
 Principles of determining tunnel objects:
 A tunnel carries various kinds of services for a
single customer in an office direction of an NE .

 A tunnel APS group includes two tunnels, a working
tunnel and a protection tunnel.

 A bidirectional tunnel includes two unidirectional Shiqi Jiebei Qiuai
tunnels, a forward tunnel and a backward tunnel.
 Example 1: NodeB customers require two kinds of Tunnel#3

services, OAM service and user & signaling service, Tunnel#1 Tunnel#2
to be transmitted between Jiebei and Yinzhong. Both
kinds of services are carried by Tunnel#1.
Yinzhong Panhuo
 Example 2: NodeB customers and VIP customers
from the government and enterprise sectors require
services to be transmitted between Jiebei and
Panhuo. The two kinds of services are carried by
Tunnel#2 and Tunnel#3 respectively.
Description:
In this design scheme, all NodeB services
are considered services for the same
customer.

Tunnel Objects on the Network of the Pilot Office
Yinzhou Binhai
Wuxiang Zhanqi Community
Yinzhou Shundeli
plant Hongsen Wood
Jiebei BSC Dongwu Jinlong
Yinzhou Dongwu II
Shiqi
Yinzhou Gaoqian
Jishigang Qiuai
Telecom Jiebei
Yunlong
Mozhi Tangxi
Telecom
Yinzhong Qianhurenjia
Panhuo
 Ten tunnel APS groups are available for carrying NodeB service PWs. Each
Yinzhou Hengxi
Telecom group includes two bidirectional tunnels, a working tunnel and a protection
tunnel. Each bidirectional tunnel includes two unidirectional tunnels, a
Tunnel APS protection forward tunnel and a backward tunnel. All together, 20 bidirectional tunnel
groups carrying NodeB objects, or 40 unidirectional tunnel objects, exist on the network.
service PWs  The automatic allocation scheme of the T2000 is adopted for tunnel ID
allocation.

Tunnel Object Naming Rule
 Tunnel naming rule applies to unidirectional tunnel objects.
 Tunnel naming rule

Purpose of tunnel:office direction of tunnel:direction of tunnel: APS property
 Example: EVDO:Jiebei-Yinzhou Shundeli plant:forward:working
 Purpose of tunnel
 It is the customer or type of the service carried by a tunnel. In this project, EVDO stands for data services of
CDMA BTSs. More values are to be defined.
 Office direction/Direction of tunnel

 It indicates the start and end NEs of a tunnel, in the format of NE 1 name-NE 2 name.
 The meaning of the office direction field varies with the direction field. If the direction of tunnel is Forward, NE 1
is the start NE and NE 2 is the end NE. If the direction of tunnel is Backward, NE 2 is the start NE and NE 1 is
the end NE.
 APS property
 Value: working or protection
Description: It defines whether a tunnel is a working tunnel or a protection tunnel in an APS group.

3.7 MPLS/Tunnel OAM Design

MPLS/Tunnel OAM Design
 Tasks of MPLS OAM design

 Determine the scope of MPLS OAM configuration, that is, determine
the NEs and the tunnels on which OAM configuration is made.
 Determine OAM configuration parameters such as OAM status,
backward tunnel, test mode, type of test packet, sending interval of
test packet, with a focus on backward tunnel.

Concept of MPLS/Tunnel OAM
 The MPLS OAM mechanism effectively detects,
determines, and locates network defects on the MPLS
layer, to monitor the network performance.
 The OAM status can trigger protection switching,

implementing fast fault detection and service
protection. This mechanism ensures carrier-class
services on PSNs.
 MPLS OAM implements the following features:

 Query on demand and continuous detection,
finding defects of monitored LSPs in real time
EVDO:Jiebei-Yinzhou Shundeli  Network defects detection, analysis, location, and
plant:forward:working
reporting to the NMS
EVDO:Jiebei-Yinzhou Shundeli
 Protection switching triggering upon detection of a
plant:backward:working link defect or failure
Jiebei Yinzhou
plant:forward:protection  Real-time monitoring of performance indexes such
Shundeli
EVDO:Jiebei-Yinzhou Shundeli plant as packet loss ratio, delay, and jitter, and reporting
plant:backwrd:protection to the NMS

Relations Between MPLS OAM Design and
Alarming & Protection
EVDO:Jiebei-Yinzhou Shundeli  Forward working matches backward working.
plant:forward:working  When a fiber is cut, the back transmission route of
BDI packets becomes unavailable. The start NE of
plant:backward:working the tunnel does not send a BDI alarm while the end
EVDO:Jiebei-Yinzhou Shundeli Yinzhou Shundeli NE sends an FDI alarm (when the FDI sending
Jiebei plant:forward:protection plant option is enabled).
EVDO:Jiebei-Yinzhou Shundeli  It is recommended that 1+1 single-ended switching
plant:backward:protection
instead of dual-ended switching be adopted for this
Forward working matches backward working. design scheme.
plant:forwarding:working  Forwarding working matches backward
protection.
plant:backward:working  When a fiber is cut, a BDI and an FDI alarms (when
EVDO:Jiebei-Yinzhou Shundeli Yinzhou the FDI sending option is enabled) are sent.
Jiebei plant:forward:protection Shundeli plant  It is recommended that either single-ended switching
EVDO:Jiebei-Yinzhou Shundeli or dual-ended switching be adopted for this design
plant:backward:protection
scheme.
Forward working matches backward protection.

Design for 50 ms LSP Protection Switching
 For a tunnel APS group, configure MPLS OAM parameters

four times on the NEs at both ends.
 MPLS OAM parameters except for backward tunnel:

 OAM status: enabled
 Test mode: manual
 Type of test packet: FFD
 Sending interval of test packet: 3.3 ms

3.8 Tunnel APS Design

Tunnel APS Design
 Tasks of tunnel APS design
 Determine the routes of the working tunnel and backward tunnel in a
tunnel APS group.
 Key points:
 Protection loop: Routes of the working tunnel and protection tunnel form a
protection loop. Half of the loop is used as the working route and the other
half is used as the protection route.
 Routing policy: (1) uniform routing; (2) shortest path routing; (3) routing for
load sharing
 Relations between routing policy and protection mode
– 1+1 protection: All routing policies achieve the same result.
– 1:1 protection: Shortest path routing and routing for load sharing are
recommended, and uniform routing is not recommended.

Tunnel APS Routing Wuxiang Zhanqi
Yinzhou
Jiebei BSC
Dongwu Jinlong
Yinzhou Binhai
Community
Jiebei
Yinzhou Dongwu II
Shiqi Qiuai Yinzhou

Jishigang Gaoqian
Telecom
Yunlong
Telecom Mozhi
Tangxi
Yinzhong Panhuo
Qianhurenjia
Yinzhou Hengxi
Telecom
 On a tunnel APS loop, the working tunnel takes the shorter path and the protection tunnel takes the longer path.
 For example, in tunnel APS Jiebei-Yinzhou Shundeli plant, the route is the working tunnel is Jiebei-Shiqi-
Hongsen Wood-Yinzhou Shundeli plant, and the protection route is Jiebei-Qiuai-Panhuo-Yinzhong-Shiqi-
Jishigang Telecom-Yinzhou Shundeli plant.

Naming Rule of Tunnel APS Groups
 Description:
 The name of tunnel APS group is not a necessary parameter for network debugging, but is defined in this
design for easy description and understanding.
 Naming rule of tunnel APS groups

Purpose of tunnel:office direction of tunnel
 The meaning of fields here is identical with that in tunnel object names.
 This naming rule shows that a bidirectional tunnel APS group object includes four
unidirectional tunnel objects.
 For example, tunnel APS group EVDO:Jiebei-Yinzhou Shundeli plant includes four unidirectional tunnel
objects, EVDO:Jiebei-Yinzhou Shundeli plant:forward:working, EVDO:Jiebei-Yinzhou Shundeli
plant:backward:working, EVDO:Jiebei-Yinzhou Shundeli plant:forward:protection, and EVDO:Jiebei-
Yinzhou Shundeli plant:backward:protection. The first two tunnel objects form a bidirectional working
object, and the last two tunnel objects form a bidirectional protection tunnel object.
Bidirectional tunnel
Tunnel APS object: EVDO:Jiebei-Yinzhong:forward:working object:
EVDO:Jiebei-Yinzhou EVDO:Jiebei-Yinzhou
Shundeli plant EVDO:Jiebei-Yinzhong:backward:working Shundeli plant:working
EVDO:Jiebei-Yinzhong:forward:protection Bidirectional tunnel
EVDO:Jiebei-Yinzhong:backward:working object:
Yinzhong Jiebei
EVDO:Jiebei-Yinzhou
Shundeli plant:protection
Tunnel APS Group Parameters
 Protection type  Working tunnel type
 1+1/1: 1  MPLS tunnel
 Switching mode  Working ingress tunnel ID
 Single-ended/Dual-ended  Forward working/Backward working
 Revertive mode  Working egress tunnel ID
 Revertive  Backward working/Forward working
 WTR (m)  Protection tunnel type
 5m  MPLS Tunnel
 Hold-off time (100 ms)  Protection ingress tunnel ID
 0 ms  Forward protection/Backward protection
 Protection egress tunnel ID
 Backward protection/Forward protection

3.9 Label Design

Label Design Procedure
 From PW label design to tunnel label design
 PW label design: from convergence to access, from coarse-

granularity access nodes from fine-granularity access nodes
 Tunnel label design: from the top down

PW Label Design:
from Convergence to Access and from Coarse-
Granularity Access Nodes to Fine-Granularity
Access Nodes Service
 Allocate PW labels to service convergence convergence
nodes and then access nodes. PW label nodes
200 -350
 Allocate PW labels to access nodes at the Coarse-

regional level, subnet level, and NE level in PW label PW label granularity
200 -299 300 -350 service
turn.
access nodes
 Allocate PW labels to service convergence
nodes from coarse-granularity nodes to fine-
granularity nodes. PW label PW label PW label PW label
200 -249 250 -299 300 -324 325 -350
 Principles of node division:
 Fine-granularity node division saves label Fine-granularity service
resources but at the cost of worse flexibility. access nodes
 Coarse-granularity node division uses more  Node division in PW label allocation is independent of
label resources but provides better flexibility. network topology. This means that fine-granularity
nodes under a coarse-granularity node are
 Generally, nodes are divided to the access-
unnecessarily to have correlated topologies.
layer subnet level.

Tunnel Label Design: from the Top down
 Tunnel label design: from the top down

 Tunnel labels should be allocated from the top down. For a three-layer
network, the tunnel label design should be made in the sequence of
backbone layer, convergence layer, and access layer.
 Description:
 Tunnel label design is optional. By default, the T2000 supports
automatic label allocation during tunnel creation.

About Label Planning and Design
 Label resource planning outputs a
label resource use rule. The rule is not
Idle
compulsory and is maintained
manually.
Define Clear purpose of label
purpose of
 Label resource planning and design is
label
to specify a few label ranges for PW/Tunnel objects
specific purposes so that labels in a release labels
Reserve Use
range can be allocated to objects
serving the corresponding purpose. Redefine purpose of label Allocate labels to
PW/tunnel objects
 Label resource planning is based on an
assumed service requirement. If the Label planning and design
assumption goes beyond actual
conditions, the planning should be
adjusted.

Contents of Label Design
 PW label design
 Tunnel label design

 PW label design

PW Label Resource Planning
 The ingress label and egress label of a PW object must be equal.
 To support services in uncertain office directions (such as VIP customer services),

label range 0/16-199 is reserved on all NEs throughout the network as PWs carrying
these services. This ensures that enough PWs are available for 184 EPL services in any
office directions throughout the network even in the worst conditions.
 PW label resource planning for CDMA BTS services:

 Totally 500 labels are reserved at Jiebei to support 500 PWs, more than the required 480 PWs.
 Totally 200 labels are reserved at Yinzhong to support 200 PWs, more than the required 120 PWs.
 It is evaluated that each backbone node requires 140 PWs to connect to the subnets, 100 PWs to Jiebei
and 40 PWs to Yinzhong.

PW Label Planning
PW labels:
200-699 500 and 200 PWs are
designed for Jiebei and
Shiqi Jiebei Qiuai
PW labels: Yinzhong respectively to
700 -899
Backbone layer support at least 500 and 200
Ring#1 EPL services from the access
layer.
Yinzhong Panhuo
Shiqi
Panhuo
Attached subnet Qiuai
Yinzhong Jiebei Attached subnet
PW labels:
Attached subnet Attached subnet PW labels: Attached subnet
300-399
740-779 500-599 PW labels:
PW labels: PW labels:
820-859 600-699
400-499 200-299
780-819 700-739 860-899
 Totally 140 PWs, 100 PWs to Jiebei and 40 PWs to Yinzhong, are designed for each regional
subnet attached to a backbone node.
 Idle labels in the range of 2048 to 28671are allocated for inter-node communication on the
backbone layer.

PW Label Preservation Scheme
Label range 16-199 on all NEs throughout
the network is reserved for services in
PW labels: PW labels: uncertain office directions.
200-699 700 -899
Ring#1 Jieb Shiqi Yinzhong Panhuo Qiuai Ring#1
ei
To: Qiuai To:
Idle labels: Idle labels: Idle labels: Idle labels: Idle labels:
700-28671 200-28671 200-699 200-28671 200-28671 Jiebei
900-28671
Ring#2
Ring#3 N/A L#1
N/A Ring#4
L#2
L#3
Yinzhong Access
Jiebei Region Shiqi Region Panhuo Region Qiuai Region
Region PW
Jiebei 200-299 300-399 400-499 500-599 600-699 500
Yinzhong 700-739 740-779 780-819 820-859 860-899 200
Access PW 140 140 140 140 140 700
Free label 200-299 200-399 200-499 200-599

300-699
space in 400-739 500-779 600-819 700-859 -
740-1535
the region 780-1535 820-1535 860-1535 900-1535

Summary: PW Label Use Rules
 Label range 16-199 on all NEs throughout the network is reserved for services in uncertain office
directions.
 Label ranges 200-699 and 700-899 are reserved on the service convergence NEs at Jiebei and Yinzhong
for PWs on the NEs in the subnets attached to the five backbone nodes at Jiebei, Shiqi, Yinzhong,
Panhuo, and Qiuai.
 Label ranges 200-299, 300-399, 400-499, 500-599, and 600-699 are reserved on the NEs at Jiebei for PWs
on the NEs in the subnets attached to the five backbone nodes at Jiebei, Shiqi, Yinzhong, Panhuo, and
Qiuai.
 Label ranges 700-739, 740-779, 780-819, 820-859, and 860-899 are reserved on the NEs at Yinzhong for
PWs on the NEs in the subnets attached to the five backbone nodes at Jiebei, Shiqi, Yinzhong, Panhuo,
and Qiuai.
 Totally 140 labels are reserved on each NE in the subnets attached to the five backbone nodes at Jiebei,
Shiqi, Yinzhong, Panhuo, and Qiuai for CDMA service PWs.
 The PW label ranges reserved on NEs are identical among the subnets in the same region, and are
different among the subnets in different regions (intersection as null).
 Label range 5000-28671 is reserved for PWs between the five backbone NEs.

 PW label design

 About tunnel label design
 Tunnel label design for the backbone layer
 Tunnel label design for the convergence layer
 Tunnel label design for the access layer

 PW label design


About Tunnel Label Design
 Tunnel label space is limited virtual network resources.
Reasonable and effective use of the resources is important
for network operation. Tunnel label area design is a solution
to effective label resource utilization.
Tunnel label Tunnel label

 Example: 16 17
Approach 1:
Hop-based label
Jiebei Shiqi Yinzhong
Tunnel label
Approach 2: 16
Unified label
Jiebei Shiqi Yinzhong

Structure Design for Tunnel Label Subnets
Tunnel label
6666
Label 16 is being used by Tunnel label
another tunnel. 106
Same NE Tunnel label subnet#0

Higher-layer Connection of different NEs
Space: 16-32,768
subnets
Tunnel label
16
Label 16 is being used by
another tunnel.
Tunnel label subnet#1

Lower-layer
Space: 16-2,048 Lower-layer Tunnel label subnet#2
subnets subnets Space: 16-2,048
 About tunnel label subnet

 The structure of tunnel label subnets is a label resource utilization rule defined for easy network management.
 A tunnel label subnet corresponds to a tunnel label range.
 The tunnel labels in a tunnel label subnet are assigned values in the corresponding label space, and the label
values remain the same in the routes of the subnet.
 When a higher-layer subnet is connected to several lower-layer subnets, the tunnel label range of the higher-layer
subnet includes that of each lower-layer subnets to make it possible for label value conversion.
 When a tunnel route enters a different area, the tunnel label value changes into the value in the corresponding
label space of the new area.

 PW label design


Tunnel Label Allocation on the
Backbone Layer: Ring#1
Idle labels: Idle labels:
Idle labels: Idle labels: Idle labels:
200-699 200-1999 200-1999
700-1999 200-1999 900-1999 5000-28671 5000 -28671
5000-28671 5000-28671 5000-28671
Ring#1 Jiebei Shiqi Yinzhong Panhuo Qiuai Ring#1
To: Tunnel Tunnel Tunnel Tunnel Tunnel

Tunnel
labels:
To:
labels: labels: labels: labels: labels:
Qiuai 2000 - 4999 2000 - 4999 2000 - 4999 2000 - 4999 2000 - 4999 2000 - 4999 Jiebei
Ring#2
N/A Ring#4 N/A L#1
Ring#3
L#2
L#3
Tunnel
Yinzhong Panhuo
Jiebei Region Shiqi Region Qiuai Region APS
Region Region
Capacity
Reserved
2000-2599 2600-3199 3200-3799 3800-4399 4400-4999 750
label
Tunnel
APS 150 150 150 150 150 750
capacity
Summary: Tunnel Label Allocation on
the Backbone Layer
 Label ranges 2000-2599, 2600-3199, 3200-3799, 3800-4399, and 4400-4999 are
reserved on the NEs of the five backbone nodes at Jiebei, Shiqi, Yinzhong,
Panhuo, and Qiuai on Ring#1 for tunnels between the NEs on the backbone
nodes and the attached subnets.
 These 3000 labels support 750 LSP APS PWs even in the worst conditions, more
than the required 700 PWs.
 The label values of unidirectional tunnels remain the same in Ring#1 route.
 The tunnel labeled N, where N is an even number in the range of 2000 to 4998,
and the tunnel labeled N + 1 form a bidirectional tunnel pair.
 For tunnels between the NEs on the backbone nodes of Ring#1 and the attached
subnets, labels in the reserved range are allocated in an ascending order.

 PW label design


Tunnel Label Resource Allocation on
the Convergence Layer: Ring#2
200-4399 200-4399 200-4399 200-4399 200-4399
5000 -28671 5000 -28671 5000 -28671 5000 -28671 5000 -28671
Ring#2 Qiuai Wuxiang Zhanqi Tangxi Mozhi Ring#2
To: Tunnel Tunnel Tunnel Tunnel Tunnel Tunnel To:

labels: labels: labels: labels: labels: labels:
Mozhi 4400-4999 4400-4999 4400-4999 4400-4999 4400-4999 4400-4999 Qiuai
Idle labels: Idle labels: Idle labels:

200-599 200-599 200-599
L#1 L#3 L#2
700-859 700-859 700-859
900-1535 900-1535 900-1535
 The tunnel label range reserved on the convergence layer is consistent with that on the backbone
layer. Ring#2 is a subnet attached to the backbone node at Qiuai on Ring#1. Therefore, the tunnel label
range of Ring#2 inherits that of Ring#1, which is 4400-4999.
 Tunnel label allocation rule on Ring#2: in ascending order
 When a new convergence-layer subnet is connected to the Qiuai node, the purpose of reserved tunnel
labels on the convergence layer can be changed, for example, 4400-4699 be allocated to Ring#2 and
4700-4999 to the new convergence ring.

Summary: Tunnel Label Allocation on
the Convergence Layer
 Usually, the PTN 1900 is used on the convergence layer because it provides 32 k label
space to converge large-volume services (about 6,000 protected private line services).
 The OSN 1500 is not recommended on the convergence layer (particularly when the
convergence-layer subnet is large) because it provides only 2 k label space to converge
small-volume services (about 400 protected private line services).
 When the PTN 1900 is used on a convergence-layer subnet, it can inherit the tunnel
label scheme on the backbone layer to keep label consistency in the tunnel route
crossing the backbone layer and convergence layer.
 When a new convergence-layer subnet is connected to a backbone node, the tunnel

label range reserved for the original convergence-layer subnet can be divided, for
example, in half.

 PW label design


Tunnel Label Evaluation for Access-
Layer Subnets
 An access layer subnet is a simple ring or chain on the access layer.
 Tunnel label evaluation for an access-layer subnet should consider the following items:
number of PWs connected to the access-layer subnet (P), neighboring relationship
among access-layer subnets (N), and idle label intersection between access-layer
subnets and the connected backbone-/convergence-layer NE (L). N stands for the
number of neighboring access-layer subnets. For example, a backbone/convergence
node is connected to N access-layer rings or chains.
 Tunnel label evaluation model for access-layer subnets

 L ≥P + L * N, or L≥ P + 4 * P * N, where L = 4 * P (in the worst conditions)
 This model shows the relationship among topology, service volume (PW), tunnel quantity, and label
resource. For example, an OSN 3500 is connected to 10 OSN 1500 rings through private lines with
tunnel APS protection. In this case, L approximates 1,500, N is 10, the average service volume (PW) of
each OSN 1500 ring is up to 36, and the maximum number of tunnel labels for each OSN 1500 ring is
144. Thus, the tunnel label ranges of the 10 OSN 1500 rings do not cross and all the OSN 1500 rings
can be connected to an OSN 3500.
 This model can be used to evaluate either access-layer subnets or the convergence layer and backbone
layer.

Quick Reference for Tunnel Label Evaluation
PW Tunne l N La be l
20 80 13 1100
40 160 6 1100
60 240 4 1100
80 320 3 1100
100 400 2 1100
120 480 2 1100
 Description:
 The label quantity 1,100 has the PW and reserved quantities deducted.

Reference Device Specifications
NE Tunnel PW Label Default Start Multicast

Type (Unidirectional (Bidirectio Space Label Label
) Quantity nal) Size Space
Quantity
OSN 3500 4k 16 k 32 k 16-32,767 -
OSN 1500 512 512 2k 16-2,047 -
PTN 3900 4k 8k 32 k 16-32,767 28,672
PTN 1900 1k 2k 32 k 16-32,767 28,672
PTN 950 512 1,024 1.5 k 16-1,535 1,536
PTN 910 512 1,024 1.5 k 16-1,535 1,536

Tunnel Label Resource Allocation to Access
Subnets Attached to Ring#1
200-28671 200-699
900-28671
Ring#1 Jiebei Shiqi Yinzhong Panhuo Qiuai Ring#1
To: Tunnel Tunnel Tunnel Tunnel Tunnel

Tunnel
labels:
To:
Qiuai 2000 - 4999 2000 - 4999 2000 - 4999 2000 - 4999 2000 - 4999 2000 - 4999 Jiebei
Tunnel Tunnel
labels: labels:
1376- 1535 1376- 1535
200-299 Ring#3 Ring#4 200-399
400-739 500-779
780-1535 820-1535
 For each access-layer subnet attached to a backbone node,

the designed PW quantity is 40, 160 tunnel labels or 40 tunnel
APS groups are required, and the tunnel label space is 1,376-
1,535.

Tunnel Label Resource Allocation to Access
Subnets Attached to Ring#2
200-4399 200-4399 200-4399 200-4399 200-4399
5000 -28671 5000 -28671 5000 -28671 5000 -28671 5000 -28671
Ring#2 Qiuai Wuxiang Zhanqi Tangxi Mozhi Ring#2
To: Tunnel Tunnel Tunnel Tunnel Tunnel To:

Mozhi 4400-4999 4400-4999 4400-4999 4400-4999 4400-4999 Qiuai
Idle labels: Tunnel Tunnel Idle labels: Tunnel Idle labels:

labels: labels: labels:
200-599 200-599 200-599
1216-1375 1376-1535 1376-1535
700-859 L#1 L#3 700-859 L#2 700-859
900-1535 900-1535 900-1535
 For each access-layer subnet attached to Ring#2, the designed PW quantity is 40, and
160 tunnel labels are required.
 The idle label intersection among Wuxiang node, Mozhi node, L#1, and L#2 is 200-599,
600-859, and 900-1,535. The idle label intersection between L#1 and L#2 is null.
 The tunnel label space of L#1 is 1,216-1,375, and the tunnel label space of L#2 and L#3
is 1,376-1,535.

Summary: Tunnel Label Resource
Allocation on the Access Layer
1. Evaluate the service volume of access subnets (PW quantity).
2. Identify the neighboring relationship among access layer subnets.
3. Calculate neighboring access-layer subnets and the intersection of

idle label space of all backbone/convergent NEs.
4. Allocate tunnel label space in the intersection for each access

subnet with the volume of the space four times of the service
volume of each access subnet. Make sure that the tunnel label
space of neighboring access-layer subnets does not overlap.

3.10 QoS Design

QoS Design
 Tasks of QoS design

 Determine the QoS control point
 Determine the QoS policy (CAR and forwarding priority)
 Design principles: easy management and maintenance

 Ingress control preferred
 Simple traffic classification preferred

Example: QoS Requirement Analysis
 The network of the pilot office carries the DO service of

CDMA BTSs, which requires the CIR and PIR to be 10 Mbit/s
for each BTS, but does not require flow classification.
Therefore, the QoS scheme of the pilot office network
focuses on the CIR and PIR of private line services.
 The CIR and PIR for tunnels are unlimited.
 The forwarding priority of all services is EF.

Example: QoS Control Point Wuxiang Zhanqi
Yinzhou Binhai
Community
Yinzhou Shundeli
plant Hongsen Wood Ring#2 L#3
Jiebei Jiebei Dongwu Jinlong
Uplink BSC#2 BSC#3
L#1
V-UNI ingress Ring#3 Yinzhou Dongwu II
Downlink
Shiqi s33p1 s33p2 V-UNI ingress
Yinzhou Gaoqian
Jishigang Qiua
Telecom Jiebei i
Yunlong
Ring#1 Mozhi Tangxi
Telecom L#2
Ring#4
Qianhurenjia
ETH
Yinzhong Panhuo
Yinzhou Hengxi
Telecom
 Using the ingress as a QoS control point is called ingress policy.
 Configure uplink CIR and PIR on the port between the transmission device and the BTS and the service
UNI/ingress corresponding to the BTS VLAN ID, and set the forwarding priority of the service UNI ingress to EF.
 Configure downlink CIR and PIR on the port between the transmission device and the BSC and the service
UNI/ingress corresponding to the BTS VLAN ID, and set the forwarding priority of the service UNI ingress to EF.
 Do not configure CIR, PIR, or priority for tunnels.
BTS

Example: QoS Design for Service UNI
Ingress
 Both uplink and downlink forwarding  For the OSN 1500, the V-UNI ingress policy
priorities are configured on the service UNI can be deployed on the service UNI ingress
ingress through parameter EF. for uplink bandwidth restriction. This QoS
policy includes the following parameters:
 For the PTN 3900 (OSN 3500), CIR and PIR  Name: CAR 10 Mbit/s
are configured directly on the service UNI  Flow classification condition: cVLAN ID =
ingress. Therefore, CIR and PIR of the 1, wildcard as 4095
service UNI ingress can be changed for  Association between classified flow and
downlink bandwidth restriction. CAR: CIR = PIR = 10 Mbit/s
 Queue sharing disabled
 For the PTN 910/950, CIR and PIR are
configured directly on the service UNI  Create this QoS policy for the OSN 1500 at
ingress. Therefore, CIR and PIR of the both ends and deploy the policy on the
service UNI ingress can be changed for service UNI ingress.
uplink or downlink bandwidth restriction.

Exception: Uplink Ingress Policy of the OSN
1500

Thank you
www.huawei.com

Network Design Scheme For XX Telecom Pilot Office (LLD & DD)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Network Design Scheme For XX Telecom Pilot Office (LLD & DD)

Uploaded by

Copyright:

Available Formats

21/12/7 Security Level:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

 Easy management and maintenance

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

 Service models of CDMA BTSs

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5

 Backbone layer expansion

 Convergence and access layer expansion

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

 Network planning (HLD) usually includes the following items:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

The access layer is composed of GE rings or links.

 Subnets on the backbone layer, convergence layer, and access layer

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

Ingress Transit Tunnel Transit Egress

ETH Link ETH Link ETH Link

 Comparison of MPLS PWE3 and SDH network objects:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

Yinzhong Protection tunnel Panhuo

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

 OSN NEs support in-band DCN communication over IP or HWECC.

 All the OSN 3500 NEs can function as IP or HWECC gateways.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

 LLD & DD orient toward network delivery, management, and maintenance.

 Output parameters of LLD & DD should be suitable to be input parameters of

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

 DCN design  MPLS OAM design

 Parameter design for NNI packet  Tunnel APS design

 MPLS design  QoS design

 Network synchronization design  Ethernet OAM (services and links)

 Service and PW design

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

 In HLD and DD phases, the task of network topology design

 Key points of topology (cable connection) design:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

Shiqi Jiebei Qiuai

Convergence layer Qiuai

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

 DCN design should include the following items:

 Key points of design:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

Yinzhong Panhuo Qianhurenjia

Yinzhou Shundeli plant Hongsen Wood ID: 2017/88

Jiebei BSC Jinlong IP: 129.88.7.221/16

Yinzhou ID: 2014/88

 For designed DCN parameters, see the attachment:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 24

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 25

 To implement MPLS PWE3, all NNI packet ports on the

 All NNI 10GE ports work in 10GE full-duplex WAN mode.

 All NNI GE ports work in 1000M full-duplex mode.

 All NNI packet ports have their maximum transmission unit

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 26

 LAN and WAN modes of 10GE ports

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 27

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 28