Security Level:
Network Design Scheme for XX Telecom Pilot Office (LLD & DD)
www.huawei.com
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 Confidential
Page 3
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.
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
Huawei Confidential
Page 4
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.
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.
Other services
Huawei Confidential
Page 5
Huawei Confidential
Page 6
2. Network Planning
Huawei Confidential
Page 7
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.
Huawei Confidential
Page 8
Backbone layer
The backbone layer and the convergence layer are connected through shared NEs.
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.
Subnets on the backbone layer, convergence layer, and access layer are pure OSN/PTN networks or hybrid networks.
Huawei Confidential Page 9
PW
Transit
Tunnel Connection
Egress
Ingress
Ingress
Tunnel
Tunnel Connection
Ingress Egress
Transit
Tunnel Connection
Ingress
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.
Huawei Confidential
Page 10
Tunnel/LSP APS based network protection mode is adopted to implement service protection switching within 50 ms.
Shiqi Jieb ei Working tunnel
Qiua i
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 protect the ring.
Working and protection tunnels with the same route on the chain
Chaoyang Shiqi Jieb ei Qiuai
Working tunnel
Yinzhong
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential
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.
Huawei Confidential
Page 12
3. Network Design
Huawei Confidential
Page 13
LLD & DD orient toward network delivery, management, and maintenance. Different from HLD, network design (LLD & DD) comes to details.
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.
Huawei Confidential
Page 14
Network topology
Tunnel design
DCN design
Parameter design for NNI packet ports/user network interface (UNI) ports MPLS design Network synchronization design (optional) Service and PW design
Huawei Confidential
Page 15
Huawei Confidential
Page 16
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.
Huawei Confidential
Page 17
Backbone layer
Yinzhong
Ring#1
Panhuo Wuxiang Zhanqi
Convergence layer
Qiuai
Ring#2
Mozhi Tangxi
Access layer
Wuxiang
Zhanqi
Ring#3 L#2
L#1
Ring#4
Yinzhou Hengxi Telecom
Yinzhong Qianhurenjia Mozhi Page 18
Dongwu Jinlong Yinzhou Dongwu II L#3 Yinzhou Gaoqian Yinzhou Binhai Community
Huawei Confidential
Zhanqi
s3p1 s4p1
s3p2
Hongsen Wood
s13p1 s13p2
Ring#2
Jiebei BSC#2 Jiebei BSC#3
s3p1
L#3
s13p1
Ring#3
s13p2 s13p1 s13p1 s13p9
L#1
s32p1 s11p1
s4p1 s1p1
s2p1
Shiqi
s5p1 s3p1
s33p1 s11p1
s33p2 s13p1
s3p1 s4p1
Yinzhou Gaoqian
s3p1 s4p1
Qiuai
Ring#1 Ring#4
s3p1 s5p1 s13p9
Jieb ei
s13p1
s31p1
s4p1
s3p2 s3p1
L#2
Mozhi Qianhurenjia
Tangxi
Yinzhong
Panhuo
Legend:
PTN 3900 PTN 1900 PTN 950/910 BSC OSN 3500 OSN 1500 T2000 BTS
Legend:
5pts
10GE GE FE
YinzhongT2000
2pts
1pt
Huawei Confidential
Page 19
Huawei Confidential
Page 20
DCN Design
DCN subnet division (LLD) DCN communication protocol design (LLD) DCN port design (DD) Management IDs and IP addresses of NEs (DD)
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
Huawei Confidential
Page 21
Qiuai
Yinzhou Gaoqian
Mozhi
Tangxi
Panhuo
Qianhurenjia
By default, the reserved VLAN ID (4094) is used for in-band DCN communication. Description:
To: NMS network in the office
1. All IP links form an OSPF domain with the domain number as 0.0.0.0. 2. The OSN 3500 NEs at Yinzhong and Shiqi act as IP-HWECC gateways. 3. In-band DCN packets on the link layer have the VLAN ID as 4094 and bandwidth as 512 kbit/s.
Page 22
Huawei Confidential
Wuxiang
ID: 2011/88 IP: 129.88.7.219/16 ID: 2010/88 IP: 129.88.7.218/16
Zhanqi
Jishigang Telecom
ID: 2012/88 IP: 129.88.7.220/16
Qiuai Shiqi
ID: 2005/88 IP: 129.88.7.213/16
Jiebei
ID: 2004/88 IP: 129.88.7.212/16
Mozhi
ID: 2006/88 IP: 129.88.7.214/16
Tangxi
ID: 2007/88 IP: 129.88.7.215/16
Yinzhong
ID: 2001/88 IP: 129.88.7.209/16
Panhuo
ID: 2002/88 IP: 129.88.7.210/16
Qianhurenjia
YinzhongT2000
IP: 129.9.1.151/24
1. NEs of the pilot office network use 88 as the extended ID to be distinguished from the NEs on the existing network. The basic IDs 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 NE subnet division plan, but designs management IDs 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 example, the basic ID 2001 corresponds to host IP address for easy integration with the existing network. 129.88.7.209. Page 23 HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential
Description:
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:
Huawei Confidential
Page 24
Huawei Confidential
Page 25
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.
Huawei Confidential
Page 26
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.
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.
Huawei Confidential
Page 27
Huawei Confidential
Page 28
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.
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.
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.
Huawei Confidential
Page 29
Wuxiang
LSR ID: 130.0.0.11 LSR ID: 130.0.0.10
Zhanqi
Jishigang Telecom
LSR ID: 130.0.0.12
Qiua i Shiqi
LSR ID: 130.0.0.5
Jiebei
LSR ID: 130.0.0.4
Mozhi
LSR ID: 130.0.0.6
Tangxi
LSR ID: 130.0.0.7
Qianhurenjia Yinzhong
LSR ID: 130.0.0.1
Panhuo
LSR ID: 130.0.0.2
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.
Huawei Confidential
Page 30
Zhanqi
18.0.0.77
Hongsen Wood
18.0.0.45 18.0.0.42
18.0.0.46
Jiebei BSC
18.0.0.58
18.0.0.78
Dongwu Jinlong
18.0.0.61
Jiebei
18.0.0.13 18.0.0.50 18.0.0.53 18.0.0.41 18.0.0.54 18.0.0.14 18.0.0.10 18.0.0.9 18.0.0.38
18.0.0.62
Yinzhou Dongwu II
18.0.0.65
Shiqi
18.0.0.17
Qiuai
18.0.0.6
Mozhi
18.0.0.18 18.0.0.1 18.0.0.5 18.0.0.2 18.0.0.73 18.0.0.74
18.0.0.70 18.0.0.2 5
Tangxi
Yinzhong
Panhuo
The allocated NNI IP addresses of the pilot office network range from 18.0.0.1 to 18.0.0.90.
Huawei Confidential
Description:
Qianhure njia
Each MPLS NNI IP address on the network of the pilot office has a 30-bit mask, that is, 255.255.255.252. Each link uses an average of four IP addresses.
Page 31
Huawei Confidential
Page 32
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.
Huawei Confidential
Page 33
Example: Service Carrier Requirements for the Network of the Pilot Office Yinzhou Binhai
Community
Hongsen Wood Jiebei BSC#2 Jiebei BSC#3 Dongwu Jinlong Yinzhou Dongwu II Yinzhou Gaoqian
Qianhurenjia
NodeB services
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 BTS number.
Huawei Confidential
Page 34
Ten PW objects are available for carrying NodeB services, and correspond to the ten base station Ethernet services. Each PW object is a bidirectional PW. The PW ID is identical with the PW label.
Huawei Confidential
Page 35
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
Huawei Confidential
Page 36
Huawei Confidential
Page 37
Tunnel Design
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.
Huawei Confidential
Page 38
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 tunnels, a forward tunnel and a backward tunnel. Example 1: NodeB customers require two kinds of services, OAM service and user & signaling service, to be transmitted between Jiebei and Yinzhong. Both kinds of services are carried by Tunnel#1.
Shiqi
Jiebei
Qiuai
Tunnel#3
Tunnel#1 Tunnel#2
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.
Huawei Confidential
Page 39
Zhanqi
Panhuo
Ten tunnel APS groups are available for carrying NodeB service PWs. Each group includes two bidirectional tunnels, a working tunnel and a protection tunnel. Each bidirectional tunnel includes two unidirectional tunnels, a forward tunnel and a backward tunnel. All together, 20 bidirectional tunnel objects, or 40 unidirectional tunnel objects, exist on the network. The automatic allocation scheme of the T2000 is adopted for tunnel ID allocation.
Huawei Confidential
Page 40
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.
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.
Huawei Confidential
Page 41
Huawei Confidential
Page 42
Huawei Confidential
Page 43
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.
EVDO:Jiebei-Yinzhou Shundeli plant:forward:working EVDO:Jiebei-Yinzhou Shundeli plant:backward:working EVDO:Jiebei-Yinzhou Shundeli plant:forward:protection EVDO:Jiebei-Yinzhou Shundeli plant:backwrd:protection
Jiebei
MPLS OAM implements the following features: Query on demand and continuous detection, finding defects of monitored LSPs in real time Network defects detection, analysis, location, and reporting to the NMS Protection switching triggering upon detection of a link defect or failure Yinzhou Real-time monitoring of performance indexes such Shundeli plant as packet loss ratio, delay, and jitter, and reporting to the NMS
Huawei Confidential
Page 44
Jiebei
When a fiber is cut, the back transmission route of BDI packets becomes unavailable. The start NE of the tunnel does not send a BDI alarm while the end NE sends an FDI alarm (when the FDI sending option is enabled). It is recommended that 1+1 single-ended switching instead of dual-ended switching be adopted for this design scheme.
Jiebei
When a fiber is cut, a BDI and an FDI alarms (when the FDI sending option is enabled) are sent. It is recommended that either single-ended switching or dual-ended switching be adopted for this design scheme.
Huawei Confidential
Page 45
OAM status: enabled Test mode: manual Type of test packet: FFD Sending interval of test packet: 3.3 ms
Huawei Confidential
Page 46
Huawei Confidential
Page 47
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.
Huawei Confidential
Page 48
Wuxiang
Zhanqi
Jiebei
Yinzhou Dongwu II
Shiqi
Jishigang Telecom
Yunlong Telecom
Qiuai
Yinzhou Gaoqian
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 JiebeiShiqi-Hongsen Wood-Yinzhou Shundeli plant, and the protection route is Jiebei-Qiuai-PanhuoYinzhong-Shiqi-Jishigang Telecom-Yinzhou Shundeli plant. HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 49
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.
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:JiebeiYinzhou 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 object: EVDO:Jiebei-Yinzhou Shundeli plant:working Bidirectional tunnel object: EVDO:Jiebei-Yinzhou Jiebei Shundeli plant:protection
Page 50
Yinzhong
HUAWEI TECHNOLOGIES CO., LTD.
EVDO:Jiebei-Yinzhong:backward:working
Huawei Confidential
Protection type
1+1/1: 1
MPLS tunnel Forward working/Backward working Backward working/Forward working MPLS Tunnel Forward protection/Backward protection Backward protection/Forward protection
Switching mode
Single-ended/Dual-ended
Revertive mode
Revertive
WTR (m)
5m
0 ms
Huawei Confidential
Page 51
Huawei Confidential
Page 52
From PW label design to tunnel label design PW label design: from convergence to access, from coarsegranularity access nodes from fine-granularity access nodes Tunnel label design: from the top down
Huawei Confidential
Page 53
PW Label Design: from Convergence to Access and from CoarseGranularity Access Nodes to Fine-Granularity Access Nodes Service
Allocate PW labels to service convergence nodes and then access nodes. Allocate PW labels to access nodes at the regional level, subnet level, and NE level in turn. Allocate PW labels to service convergence nodes from coarse-granularity nodes to finegranularity nodes. Principles of node division:
convergence nodes
Fine-granularity node division saves label resources but at the cost of worse flexibility. Coarse-granularity node division uses more label resources but provides better flexibility. Generally, nodes are divided to the accesslayer subnet level.
Node division in PW label allocation is independent of network topology. This means that fine-granularity nodes under a coarse-granularity node are unnecessarily to have correlated topologies.
Huawei Confidential
Page 54
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.
Huawei Confidential
Page 55
Label resource planning outputs a label resource use rule. The rule is not compulsory and is maintained manually. Idle
Label resource planning and design is to specify a few label ranges for specific purposes so that labels in a range can be allocated to objects serving the corresponding purpose.
Reserve
Redefine purpose of label
Use
Label resource planning is based on an assumed service requirement. If the assumption goes beyond actual conditions, the planning should be adjusted.
Huawei Confidential
Page 56
Huawei Confidential
Page 57
Huawei Confidential
Page 58
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.
Huawei Confidential
Page 59
PW Label Planning
PW labels: 200-699 PW labels: 700 -899
Shiqi
Jiebei
Qiuai
Backbone layer
Ring#1
Yinzhong Panhuo
500 and 200 PWs are designed for Jiebei and Yinzhong respectively to support at least 500 and 200 EPL services from the access layer.
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.
Huawei Confidential
Page 60
Label range 16-199 on all NEs throughout the network is reserved for services in uncertain office directions.
Panhuo Idle labels: 200-28671 Qiuai Idle labels: 200-28671
Jieb ei
Idle labels: 700-28671
Shiqi
Yinzhong
N/A
Ring#3
Ring#4
N/A
Jiebei Region Jiebei Yinzhong Access PW Free label space in the region 200-299 700-739 140 300-699 740-1535
Yinzhong
Region 400-499 780-819 140 200-399 500-779 820-1535
Access
PW 500 200 700
Huawei Confidential
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. Page 62
Huawei Confidential
About tunnel label design Tunnel label design for the backbone layer
Huawei Confidential
Page 63
About tunnel label design Tunnel label design for the backbone layer
Huawei Confidential
Page 64
Tunnel label space is limited virtual network resources. Reasonable and effective use of the resources is important
Jiebei
Tunnel label 16
Shiqi
Yinzhong
Jiebei
Shiqi
Yinzhong
Huawei Confidential
Page 65
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.
Huawei Confidential
Page 66
About tunnel label design Tunnel label design for the backbone layer
Huawei Confidential
Page 67
Jiebei
Panhuo
Tunnel labels: 2000 - 4999
Ring#1
Tunnel labels: 2000 - 4999
To: Jiebei
N/A
Ring#3
Ring#4
N/A
Jiebei Region
Shiqi Region
Yinzhong Region
Panhuo Region
Reserved
label Tunnel APS capacity
2000-2599
2600-3199
3200-3799
3800-4399
150
150
150
Huawei Confidential
150
Page 68
150
750
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.
Huawei Confidential
Page 69
About tunnel label design Tunnel label design for the backbone layer
Huawei Confidential
Page 70
To: Mozhi
L#1
L#3
L#2
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.
Huawei Confidential
Page 71
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.
Huawei Confidential
Page 72
About tunnel label design Tunnel label design for the backbone layer
Huawei Confidential
Page 73
Tunnel Label Evaluation for AccessLayer 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.
Huawei Confidential
Page 74
PW 20 40 60 80 100 120
N 13 6 4 3 2 2
Description:
The label quantity 1,100 has the PW and reserved quantities deducted.
Huawei Confidential
Page 75
PTN 3900
PTN 1900 PTN 950 PTN 910
4k
1k 512 512
8k
2k 1,024 1,024
32 k
32 k 1.5 k 1.5 k
16-32,767
16-32,767 16-1,535 16-1,535
28,672
28,672 1,536 1,536
Huawei Confidential
Page 76
Jiebei
Tunnel labels: 2000 - 4999
Shiqi
Panhuo
Tunnel labels: 2000 - 4999
Qiuai
Ring#1
Tunnel labels: 2000 - 4999
To: Jiebei
Ring#3
Ring#4
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,3761,535.
Huawei Confidential
Page 77
To: Mozhi
L#1
L#3
L#2
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.
Huawei Confidential
Page 78
Huawei Confidential
Page 79
Huawei Confidential
Page 80
QoS Design
Huawei Confidential
Page 81
Huawei Confidential
Page 82
Wuxiang
Zhanqi
Ring#2
Dongwu Jinlong
L#3 L#1
Yinzhou Dongwu II Yinzhou Gaoqian
Ring#3
Shiqi
s33p1
Ring#1 Ring#4
ETH
L#2
Panhuo
Mozhi
Tangxi
Qianhurenjia
Yinzhou Hengxi Telecom
Yinzhong
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. BTS Do not configure CIR, PIR, or priority for tunnels. Huawei Confidential Page 83
Both uplink and downlink forwarding priorities are configured on the service UNI
For the OSN 1500, the V-UNI ingress policy can be deployed on the service UNI ingress
For the PTN 3900 (OSN 3500), CIR and PIR are configured directly on the service UNI ingress. Therefore, CIR and PIR of the service UNI ingress can be changed for downlink bandwidth restriction.
Name: CAR 10 Mbit/s Flow classification condition: cVLAN ID = 1, wildcard as 4095 Association between classified flow and CAR: CIR = PIR = 10 Mbit/s Queue sharing disabled
For the PTN 910/950, CIR and PIR are configured directly on the service UNI ingress. Therefore, CIR and PIR of the service UNI ingress can be changed for uplink or downlink bandwidth restriction.
Create this QoS policy for the OSN 1500 at both ends and deploy the policy on the service UNI ingress.
Huawei Confidential
Page 84
Huawei Confidential
Page 85
Thank you
www.huawei.com