Ipran Lld Solution

www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Copyright © Huawei Technologies Technologies Co., Ltd. 2013. 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 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 all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

About This Document Change History Changes between document issues are cumulative. The latest document iss ue contains all the changes made in previous issues.

Issue 01 (2013-01-30) This is the first release.

Issue 02 (2013-08-30) Optimized the format of characters, figures, and tables is optimized and the information presentation mode.

Contents Objective of the IPRAN Solution Key Technical Solutions of IPRAN Networks Key Delivery Process of the IPRAN Technical Solution

Positioning of IPRAN Packet Transport Networks Packet transport networks should be constructed based on the requirements of mobile backhaul services. Recently, packet transport networks are mainly used to bear FE services for 3G mobile backhaul networks, VIP leased line services, and a few TDM services f or 2G/3G mobile backhaul networks. For sites where packet transport devices and existing MSTP devices coexist, packet transport devices do not need to bear TDM services such as E1s from BTSs and NodeBs. For new sites or sites on which MSTP devices are replaced by packet transport devices, packet transport devices should rece ive and transmit all types of services. MSC Server PSTN/ISDN MISUP/MTUP GSM/GPRS BSS BTS

BSC

C/D E

A

SMSC

CAP

Abis MGW Iu-CS

IPRAN network

Lc

Gs

Gd

Gr/Gf

CAP

GMLC DNS Firewall

Gb Lg Iub UTRAN

Iu - ps

SGSN

Lh

SCP

Lg

RNC

Node B

HLR/AuC/EIR

GGSN

Gn

Gi

WAP Gateway

Intranet/Internet

Ga Gp

IPRAN network CG

BG

Inter PLMN

RADIUS

IPRAN Network Construction Design Roadmap The hierarchical architecture design between cell site gateways (CSGs), aggregation site gatew ays (ASGs) and radio service gateways (RSGs) is applicable to large-scale bearer networks. ATN and CX routers form an IPRAN packet transport network, featuring simple and flexible networking. ATNs function as CSGs to form an access network, CX600s ASGs to form an aggregation network, and CX600s function as RSGs at the core layer. These devices can be flexibly deployed according to service bearing requirements.

Core/Aggregation layer Access layer

ATN950/950B CX600-X16 32U 16 Slots

CX600-X8

CX600-X3

14U 8 Slots

4U 3 Slots

2U 8Slots

ATN910 1U 4 Slots

IPRAN Network Architecture BSC/RNC

New or reused RAN-CE equipment co-site with RNCs and function as the gateways of wireless equipment. Nodes at all layers co-build the bearer paths from BTSs/NodeBs to the BSC/RNC, which are mainly used to carry wireless voice services and data services. At the same time, to bear various service types, the services of some group users are migrated to the IPRAN network, to improve the efficiency.

S-GW/MME U2000

With the hierarchical architecture ensured:  Core layer: mesh networking  Aggregation layer: ring or square networking  Access layer: ring or chain networking Network characteristics:  All devices on the network are managed by the NMS in a unified manner.  A large-scale route network is constructed and route reflectors (RRs) are required.  Dual clock sources are introduced at the core layer for network-wide synchronization.  CX600s connect two layers.  RAN-CEs can be newly added or reused.

RAN-CE PRC/BITS BGP-RR

PRC/BITS Core layer

NE40E-X16

10GE aggregation ring

CX600-X8 CX600-X3 GE GE ATN910 FE TDM GE ETH BTS/Node B eNode B

TDM ETH BTS/Node B

FE GE eNode B

IPRAN Network Architecture Last Mile

Aggregation

Access

Core

BSC/RNC/MME RSG

STM-1

ASG BTS/Node B

CSG

Core

SPE

S-GW NPE

GE

E1/FE UPE eNode B PWE3

2G TDM PWE3 3G ATM PWE3

PWE3 Aggregation Tunnel

Access Tunnel

3G ETH VRF LTE VRF S1 LTE VRF X2

X2 L3VPN

L3VPN

Ethernet Service

2G TDM PWE3 3G ATM PWE3 3G ETH VRF LTE VRF S1

Hierarchy L3VPN

Device role Access device

MS-PW

Definition Access devices on a packet transport network refer to IPRAN devices that are used for service access and are

Role in the Solution UPE/CSG

located at the network edge. Aggregation device

RNC MME

RANCE

TDM/ATM Services

BSC

Aggregation devices on a packet transport network refer to IPRAN devices that aggregate traffic from access devices.

SPE/ASG

Contents Objective of the IPRAN Solution Key Technical Solutions of IPRAN Networks Solution Overview Physical Topology and Hardware Planning Resource Planning Route Protocol Planning Service Planning Reliability Planning QoS Planning Clock/Time Synchronization Planning NMS Planning

Key Delivery Process of the IPRAN Technical Solution

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Solution Overview Home user

Internet FTTX

Government/e nterprise user

Enterpris e CE

WLAN

Mobile phone user

Softswi tch

AP

Base station

RNC

Device role

CSG

ASG

Device type

ATN950B/ATN950 /ATN910

CX600-X

Encapsulation mode

P NE40E&CX600

Ethernet

L3VPN

L3VPN

TDM/ATM

PW

PW

LSP protocol

RSVP-TE/LDP

IGP protocol

ISIS/OSPF

RSG

RSVP-TE/LDP ISIS/OSPF

This document uses RSVP-TE and ISIS as an example to describe the solution.

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Solution Overview BSC Service core control layer

cSTM-1/n*E1

T D M P W E 3

RNC cSTM-1

T D M P W E 3

GE

MME 10GE

L 3 V P N

Governme nt/Enterpri se leased E1 FE line

L 3 V P N

L 2 V P N

L 3 V P N

L 3 V P N

L 2 V P N

L 3 V P N

Internet FE

BRAS

TG

GE

L 2 V P N

L 2 V P N

L 3 V P N

L 2 V P N

L 3 V P N

IGP routing T D M P W E 3 E1

Service access

2G BTS

T D M P W E 3 E1

L 3 IGP V routing P N

L 2 V P N

OLT FE

3G NodeB

GE

LTE eNodeB

E1

FE

FE

Government/Ent Internet erprise leased leased line line

FE

Broadband

FE

VOIP

Contents

1

Objective of the IPRAN Solution

2

Key Technical Solutions of IPRAN Networks Solution Overview Physical Topology and Hardware Planning Resource Planning Route Protocol Planning Service Planning Reliability Planning QoS Planning Clock/Time Synchronization Planning NMS Planning

3


Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Physical Topology Currently, a packet transport network consists of the edge layer, aggregation layer, and core layer, and is deployed based on two layers: aggregation/ core layer, and edge layer.

Base station

BSC/RNC Base station Base station BSC/RNC

Base station Bearer network

Base station

BSC/RNC

Base station Core Base station RAN-CE Base station

CSG

A ring topology is preferred for the access layer. Chains can be used if optical cables are insufficient. A maximum of three chains are allowed to be connected to a node on the aggregation edge. GE or 10 GE links can be used based on service requirements. GE or 10 GE links are recommended for sites in areas that require high bandwidth (for example, most sites on a ring are HSPA+ sites or carry VIP leased line. Nodes on the edge access rings are dualhomed to aggregation nodes preferably.

ASG

Core/Aggregation

Aggregation nodes should form a ring network or be directly corrected to core nodes. W ith (X2) traffic increase between access nodes, the aggregation layer gradually form a mesh network. The aggregation layer should adopt 10 GE links based on service requirements and technology maturity.

Core The mesh topology is configured for core nodes. Multiple routes are set up between nodes to improve network reliability. The core aggregation layer network adopts the rate of 10GE for networking based on the service requirements and technology maturity.

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Physical Topology Dual core equipment rooms, each of w hich houses one core device: District-level core devices and core devices in the core equipment room form a square-shaped topology. Each core device can be mounted with aggregation rings independently. It is recommended that core devices and the RNC share the same site. Scenario 1 is preferred. Scenario 1: Devices that connect RNCs/BSCs and the IPRAN network are newly added and share an equipment room with t he RNCs/BSCs to save optical fibers. The devices belong to the same domain as the IPRAN network and are planned to function as RSGs. Core devices do not receive/transmit services. This scenario provides good protection switching performance and facilitates end-to-end maintenance.

Scenario 1

Scenario 2

BSC/RNC GE/CPOS

BSC/RNC

GE/CPOS

GE

GE

RNC equipment room

Core equipment room 1 N×10GE

Core equipment room 2

Scenario 2: Devices that connected to RNCs/BSCs are reused and function as CEs of the IPRAN network. Core devices and the reused CEs are connected in back-to-back mode. The reused CEs receive/transmit only Ethernet services. Compared with scenario 1, this scenario provides poorer protection switching performance.

It is recommended that RNCs/BSCs be deployed in pairs for backup.

Aggregation ring 1 Aggregation ring 2

Physical Topology

Hardware Planning

Aggregation ring 3District core District core

ASG

Aggregation ring 4

District core

District core

Aggregation ring 7

Aggregation ring 9

6 ring 8 Aggregation ring 5 Aggregation ring Aggregation

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Physical Topology Scenario 1

Scenario 2

BSC/RNC

BSC/RNC

GE/CPOS

GE/CPOS

GE

Dual core equipment rooms, each of which houses two core devices: District-level core devices and core devices in the core equipment room form a square-shaped topology. Aggregation devices can be connected to core devices. It is recommended that core devices and the RNC share the same site. Scenario 1 is preferred.

GE

RNC equipment room If optical cables are sufficient, fibers indicated by dotted lines can be connected.


10GE


Based on the wireless service model, an RNC and base stations managed by the RNC belong to the same area, to improve handover performance. Therefore, the aggregation/core layer plan should be consistent with the wireless area plan, avoiding crossarea aggregation rings. If a few base stations and their RNC do not belong to the same area, traffic from these base stations can be transmitted over the 10 GE links between core devices.

Aggregation ring 13 Aggregation ring 14 District core 1

District core 8 District core 2

District core 3

Aggregation ring 1

Aggregation ring 2 Aggregation ring 3

Physical Topology

District core sites can be built independently or in pairs.

District core 7

District core 4

District core 5

District core 6 Aggregation ring 10

Aggregation ring 9 Aggregation ring 6 Aggregation ring 4 Aggregation ring 7 Aggregation ring 5 Aggregation ring 8

Hardware Planning

Aggregation ring 2

Aggregation ring 11

For a district that requires remote disaster recovery for aggregation rings, a pair of links indicated by the solid line and dotted line can be deployed.

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Physical Topology Currently, it is recommended that CX600s function as ASGs. The network structures shown in the following figures are not recommended: BSC/RNC It is not recommended that an access ring be directly connected to a core RSG. The topologies do not meet the requirements of standard hierarchical design and are difficult to deploy and maintain.

An access ring is not allowed to connect an ASG and an RSG. The topology does not meet the requirements of standard hierarchical design and are difficult to deploy and maintain

Core RSG

Access ring 2 10GE

Access ring 1 CSG

ASG Access ring 1 10GE

CSG Access ring 2

Access ring 3 ASG

Physical Topology

Hardware Planning

S-GW/MME

CSG

It is not recommended that an access ring be connected to two or more aggregation rings. The topologies do not meet the requirements of standard hierarchical design and are difficult to deploy and maintain

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Hardware Planning NE&CX devices are recommended to be deployed on the aggregation/core layer. Configure 800-mm-deep standard cabinets for small equipment rooms that house

aggregation devices. Configure the west and east ports on an aggregation ring to be on different boards. Deploy the west and east optical paths over different optical cables. Use GE boards to transmit Ethernet services and CPOS boards to transmit TDM services to the RNS/BSC. Deploy multiple links between a pair of RSGs and configure these links to be connected to different boards, ensuring link redundancy between RSGs. Configure optical modules that support proper wavelengths and distances based on requirements of interconnected devices. Configure active and standby clock sources, and introduce them at the core layer to the IPRAN network from different devices. In addition, ensure that clock cables are delivered. Ensure that all devices on the IPRAN network support clocks. Configure a mapping NMS and licenses.

Core/Aggregation layer

CX600-X16 32U 16 Slots

CX600-X8

CX600-X3

14U 8 Slots

4U 3 Slots

Access layer Deploy ATN 950B/950/910 at the access layer. Configure the east and west ports on a ring to be on different boards. Configure E1 boards to carry TDM services bases on service requirements.  ATN950/910 provides a GE capacity and ATN950B provides a 10GE capacity. Special ETSI mounting ears are required if ATN devices need to be installed in ETSI

2U 8Slots

cabinets. Physical Topology

ATN950/950B

Hardware Planning

VRP inside

VRP inside ATN910 1U 4 Slots

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Hardware Planning

Reuse of RAN-CE Devices  If devices on the new packet transport network are provided by the same vendor as that of the existing RAN CEs, the RAN CEs can be reused to function as the core-layer devices for the packet transport network.  The packet transport network is capable of carrying L3VPN services. The function of dynamically adjusting

eNodeB homing should be implemented on the packet transport network. In principle, Iub interfaces carried by the packet transport network are not interconnected with the RNC through RAN CEs. Base station homing adjustment is separately performed on MSTP and packet transport networks. The scenario where the MSTP and packet transport networks communicate with each other about base station homing adjustment is not considered currently. Iub interfaces, however, can be interconnected with the RNC through RAN CEs if existing RNC interfaces are insufficient and cannot be expanded.  If being provided by a vendor different from that provides the devices on the new packet transport network,

the existing RAN CEs cannot be reused. The existing RAN CEs can be reserved to provide Layer 3 functions for an MSTP backhaul network and will not be expanded in principle.

Physical Topology

Hardware Planning



Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks – Resource Planning Name Planning

IP Address Planning

 Name devices or ports based on

 Planning principles

naming rules.

 Plan LSR-ID/management IP addresses.  Plan interface IP addresses.  Use a planning tool to automatically allocate IP

addresses.  Specify an IP address range.  Specify the mask length.

VLAN Planning

AS Number Planning

 Plan VLANs for base stations.

 Allocate AS numbers by group customers in a unified

 Plan VLANs for subinterfaces.

manner.

 Plan VRRP VLANs.

You may use the U2000 to automatically allocate tunnel numbers, BFD IDs, and PW IDs.

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Name Planning Device naming Adhere to the following rules when you n ame a device: 1. The name of a network device is unique on the entire network. 2. The name of a network device indicates the type of the network device. 3. The name of a device name indicates the physical location of the device or physical location of the equipment room where the device is located. 4. Devices at the same physical location are differentiated by sequence numbers. An example of a device name: [City] [Area] [Aggregation ring ID] [Equipment room] [Device model] [Sequence number in the equipment room] Example: SZ.BT.BR01.HW.CX600X8-1 [Shenzhen] [Bantian] [Aggregation 1] [Huawei equipment room] [CX600-X8] [1] Interface description Configure description for each interface so that it can be easily identified and maintained. Format: connect to [Name of the peer device] [Interface type] [Interface ID of the peer device] Example: Connect to [SZ.HWM.NE40EX16-1] GigabitEthernet0/2/16 Service Interface Description Configure description for each service interface so that it can be easily identified and maintained. Configure the service interface description based on customers' requirements. Format: TO_Service office_Service name Example: TO_HW_NodeB-3GPS//Indicates that the service interface carries 3G PS services of NodeBs in a Huawei equipment room. Name Planning

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - IP Address Planning BSC/RNC

S-GW/MME

Planning principles for device management IP addresses IP addresses of local packet transport network RAN-CE RAN-CE devices (loopback addresses) are private IPv4 Lo:10.1.1.1/32 Lo:10.1.1.2/32 addresses. To ensure the interoperability and manageability of the network, IP addresses are allocated in three levels: group, national subnet, and local subnet. Ensure that each IP address is unique on a Lo:10.1.1.4/32 Lo:10.1.1.3/32 network, allocate consecutive IP addresses if possible in consideration of network scalability, and reserve some IP addresses. When allocating device IP addresses on local Lo:10.1.2.1/32 networks, it is recommended that you adhere to Aggregation ring 1 Aggregation ring 2 the following rules: Lo:10.1.2.4/32 1. Allocate IP addresses by network layer. For example, allocate different IP address Lo:10.1.2.3/32 segments to the core layer, aggregation layer, Lo:10.1.2.2/32 and edge layer in ascending order. 2. Use a 32-bit mask for device IP addresses. Access ring 11 3. Allocate consecutive IP addresses to Lo:10.1.3.4/32 Lo:10.1.3.1/32 neighboring devices if possible. 4. Reserve some IP addresses. Lo:10.1.3.3/32 It is recommended that you use the public DCN Lo:10.1.3.2/32 solution and use IP addresses of interface FE TDM loopback0 as the management IP addresses and GE ETH device IP addresses.

BTS/Node B

eNode B

Internet

BRAS

Access ring 21

TDM ETH BTS/Node B

FE GE eNode B

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - IP Address Planning BSC/RNC

S-GW/MME

Planning principles for device interconnection IP addresses RAN-CE Interface IP addresses (interconnection IP addresses) are used for communication between 10.2.1.1/30 NEs on a network. Therefore, the IP address of a local interface and that of the peer interface must be in the same network segment. 10.2.1.2/30 Interface IP addresses of packet transport NEs 10.2.1.21/30 must be unique in an AS. Therefore, private IPv4 10.2.1.17/30 addresses are used as interface IP addresses and are allocated by each local network. It is recommended that an AS use one or more class-B 10.2.1.18/30 address segments (such as 172.16.0.0/16). Aggregation ring1 10.2.1.22/30 When allocating device IP addresses on local 10.3.1.1/30 networks, it is recommended that you adhere to the following rules: 10.3.1.2/30 1. Allocate IP addresses by ring. Specifically, 10.4.1.25/30 10.4.1.1/30 allocate addresses as follows: Rings before chains, closest node on a chain and then 10.4.1.2/30 10.4.1.26/30 farther nodes in ascending order. Odd Access ring 11 numbered addresses to upper or left interfaces 10.4.1.5/30 of links and even numbered addresses to lower 10.4.1.6/30 or right interfaces of links on a ring 2. Use a 30-bit mask for device IP addresses. TDM FE 3. Reserve some IP addresses.

ETH

IP Address Planning

BTS/Node B

GE

eNode B

Internet

BRAS

Aggregation ring 2

Access ring 21 TDM ETH BTS/Node B

FE GE eNode B

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

Key Technical Solutions of IPRAN Networks - VLAN Planning VLAN Type

VLAN Planning Principle

VLANs for base stations

1. Packets from base stations carry VLAN tags. 2. Packets from base stations does not carry VLAN tags. Negotiate with the wireless network department about how to allocate service VLAN IDs and service gateway IP addresses.

VLANs for interfaces

1. Main interfaces are used for interconnection between aggregation devices. 2. Main interfaces are used for interconnection between access devices. 3. When an ASG is interconnected with access rings, allocate subinterfaces for interconnection based on IGP process IDs of the access rings. Plan subinterface IDs, VLAN numbers, and IGP process IDs consistently. 4. Plan the subinterface IDs for interconnection between ASGs in an access ring process to be consistent with those for interconnection between the ASG and the access ring. 5. Use ETH-Trunk subinterfaces for interconnection between RSGs in the aggregation ring process and plan VLANs for these subinterfaces.

VRRP VLAN

Plan a VLAN ID range for interfaces between RSGs.

Other service VLANs

Plan other service VLANs based on service requirements.

VLAN Planning

NMS Deployment



Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Route Deployment 

Make simple and easy-to-deploy IGP plans. The cost values of links need to show the link bandwidth relationship.  Import route into processes of access rings through the IGP on ASGs because LSR IDs of the ASGs that connect tangent rings are added to processes of aggregation rings.  Import the management addresses and interface addresses of the access ring into the aggregation ring for the U2000 and the plug-in-play function.  Import the IP address segment of the U2000 into the access ring so that they can communicate with each other.  To avoid route loops, set metric to a value larger than that may exist on actual networking when introducing a route, for example, 200000.  Ensure that traffic on an aggregation ring is transmitted to an access ring. To achieve this, configure a lower cost value on the aggregation side.  Ensure that the cost plan can be used as a basis for the creation of TE tunnels.  Ensure that E2E traffic from the access ring to the aggregation ring is not transmitted over the intermediate links between aggregation ring nodes.

Deploy routing protocols in hierarchical mode and use IS-IS multi-processes.

RSG BTS/Node B

E1/FE

BGP Planning

STM-1

ISIS ZZ (process) ISIS XX (process)

BSC RNC

GE

eNode B

ASG

COST planning

BTS/Node B

CSG

100

100

RSG 100 2000

E1/FE eNode B

IGP Planning

CSG

100

100

10

STM-1

BSC

45

10

100 ASG

10

10

10

GE

RNC

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Solution Overview BSC/RNC

S-GW/MME

RAN-CE Deploy the same IGP process for the core and aggregation layers. Number IGP processes of rings or chains singlehomed to a node on the aggregation ring separately.

RAN-CE ISIS 1000

ISIS 1000

ISIS 1000

ISIS 101 ISIS 102 ISIS 103

ISIS11 Number IGP processes of level-2 access rings and main access rings consistently. IGP Planning

BGP Planning Last Mile

ISIS 11 TDM ETH BTS/Node B

FE GE

Number IGP processes of access rings chains dualhomed to a node on the aggregation ring separately. eNode B

ISIS 21 ISIS 21 TDM ETH BTS/Node B

FE GE eNode B

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Route Deployment  Set the cost of links between RSGs to a value greater than the total c ost of the longest link at the aggregation layer to ensure that the active

LSP from an ASG to the master RSG does not pass along the link between the ASG and the slave RSG.  Set the cost of links between ASGs to a value greater than the total cost of the longest link at the access layer to ensure t hat the active LSP from a CSG to an ASG does not pass along the link between the other ASGs.  Retain the default cost 10 for IS-IS links except those between RSGs and between ASGs.  By default, TE tunnels are not allowed to cross IGP areas. Planning cost values can simplify configuration of TE explicit paths in an IGP area.  The cost plan must ensure that primary and secondary TE LSPs share a minimum of nodes. IGP cost planning: Paths can be selected in "TE explicit path + simplified cost value" mode. 100 100

100

CSG BTS/Node B E1/FE eNode B

IGP Planning

BGP Planning

ASG (active) 10

ISIS ZZ (process) 2000 ISIS Level 2 100

100 100 RSVP TE

10

10

ISIS XX (process) ISIS Level 2

10 ASG (standby) RSVP TE

10

RSG (active) STM-1

BS C

45 RNC GE

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Route Deployment TE Tunnel Design Principles TE-HSB is the preferred path protection scheme. To ensure that the TE plan facilitates reliability and node addition/deletion, adhere to the following principles when planning TE paths: It is recommended that you select automatic calculation of HSB paths. Therefore, plan primary and secondary LSPs to share a minimum of nodes. A loose explicit path and a strict explicit path may be used during TE path planning. When specifying an explicit path, you can specify nodes that an LSP must go through or nodes that an LSP cannot go through on an explicit path. In the IPRAN solution, loose explicit paths are often used to facilitate node addition or deletion. Specifically, include the IP address of the ingress or egress interface of the source o r end if possible and exclude undesired paths on the intermediate network to ensure that a path is unique. That is, specify the egress interface on the source node and the ingress interface on the sink node and exclude undesired intermediate nodes. In this manner, the active LSP is specified (loose interface), re-optimization, overlap, and best-effort path can be implemented. It is recommended that you configure BFD for TE-LSP for the TE path from a CSG to the master ASG, HSB for TE paths from a CSG to the master and slave ASGs, and HSB and BFD for the entire aggregation layer.

IGP Planning

BGP Planning

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Route Deployment As shown in the figure, if the access network topology is relatively simple, planning TE explicit paths is simple or is even unnecessary. Subsequent node addition or deletion for network expansion does not require adjustment of explicit paths. On the aggregation ring, specify the egress interface on a CX to control the traffic direction. At the core layer, specify paths hop by hop to control the traffic direction.

C1

FTTX Enterpr ise CE

A1

4 5 6

3 N3

N5 Bearer network N6

N4

A2 C4

Home user

Bearer network

A3

Mobile user IGP Planning

BGP Planning

C5

BSC/RNC

S-GW/MME

C3

Government/e nterprise user WLAN

1 N1

C2

AP

Base station

Design of Explicit Path Selection

2

N2

Internet Softswitch

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

Key Technical Solutions of IPRAN Networks - Route Deployment Based on the IGP cost plan: The LSP plan for access rings is as follows: The active LSP from A1 to C1 can be created along the clockwise direction with no need for specifying an explicit path. The active LSP from C1 to A1 can be created along the clockwise direction with no need for specifying an explicit path. HSB paths can be created along the counter-clockwise direction using the automatic calculation function. Paths from A1 to C2 are created similarly. • •

The LSP plan for the aggregation/core layer: It is recommended that you specify paths for devices at the core layer and above hop by hop for the active LSP on the aggregation side. Tunnel from C1 to N1: include 3,N5,N3,1 Tunnel from N1 to C1: include 1,N3,N5,3 Tunnel from C2 to N1: include 5,N5,N3,1 Tunnel from N1 to C2: include 1,N3,N5,5 Tunnel from C1 to N2: include 4,N6,N4,2 Tunnel from N2 to C1: include 2,N4,N6,4 Tunnel from C2 to N2: include 6,N6,N4,2 Tunnel from N2 to C2: include 2,N4,N6,6 HSB-protected paths can be automatically calculated (when the overlap function is enabled, the active and standby paths must share a minimum of nodes). Numbers indicate interface IP addresses and device names Nx indicate loopback IP addresses. • • • • • • • •

IGP Planning

BGP Planning

NMS Deployment

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Route Solution General Planning Principles  Use a hierarchical BGP model complying with the HVPN architecture.  Configure the priority of routes that the master RSG/ASG advertises to be higher than that of routes that the slave R SG/ASG advertises so that traffic is always transmitted to the m aster RSG/ASG in a normal situation.  Configure the priority of routes that the master ASG advertises to an access ring to be higher than that of routes that the slave ASG advertises to an access ring so that traffic is always transmitted to the master ASG in a normal situation.  Consider the effectiveness of VPN FRR and the complexity of route priority configuration when planning routes.  Plan priorities of routes that an ASG advertises to the master RSG in ascending order along the counter-clockwise direction, and priorities of routers that an ASG advertises to the slave RSG in ascending order along the clockwise direction.  It is recommended that you plan a same RD for a VPN service on the entire work. The ASG transmits default routes to the CSG with the next-hop address destined for the ASG (the ASG does not transmit RSG routes to the CSG).

The RSG transmits specific routes to the ASG.

RSG

Specify the CSG to the UPE mode.

STM-1

BSC

ASG CSG

BTS/Node B

Core

E1/FE eNode B

IGP Planning

NPE

UPE The CSG transmits specific routes to the ASG.

BGP Planning

SPE

RANCE The ASG transmits the specific routes of the CSG to RSGs and changes the next-hop address to be destined for the ASG.

S-GW GE

RNC MME

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Route Solution Configuring priorities of routes that ASGs advertise to a CSG Configure proper priorities for routes that ASGs advertise to the CSG so that the active and standby routers can be distinguished on a ring network. For example, set local-preference of the route that the master ASG advertises to the CSG to 150 and that of the route that the slave ASG advertises t o the CSG to 100. In t his manner, the route that the master ASG advertises to the CSG is preferred. Advantages compared to the model of load-sharing of traffic in two directions: 1. In the load sharing solution, maintenance personnel may easily ignore traffic monitoring. As service traffic increases, network redundancy is insufficient. As a result, when one path fails, the other path cannot meet bandwidth requirements. 2. In the load sharing solution, the service model and traffic planning are complex. A large number of routing polices are required to ensure even upstream and downstream traffic.

STM-1 BTS/Node B E1/FE CSG eNode B IGP Planning

BSC

Bearer network

BGP Planning

ISIS XX (process)

ISIS ZZ (process)

GE ASG

RSG

RNC

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Route Solution Configuring priorities of routes advertised by RSGs and ASGs when RSGs also function as RRs 1. Ensure that priorities of routes that an ASG advertises to RSG-1 are higher than those of routes that the ASG advertises to RSG-2. Configure the priorities of routes that an ASG advertises to RSG-1 to decrease along the counter-clockwise direction in a s pecific step, and the priorities of routes that the ASG advertises to RSG-2 to decrease along the clockwise direction in a specific step (to ensure VPN FRR f or X2/FMC services). In this manner, two routes are available from the ASG side t o the RSG side, and VPN FRR can be im plemented. 2. Ensure that the priorities of routes that RSG-1 advertise to an ASG are higher those of routes that RSG-2 advertise to the ASG so that two routes are available from the RSG side to the ASG side and VPN FRR c an be implemented. 3. Configure RRs in pairs so that VPN FRR can be implemented.

ASG-1

RSG-1 (RR) STM-1

ASG-2 BTS/Node B ISIS ZZ (process) E1/FE

CSG

eNode B IGP Planning

BGP Planning

BSC

Bearer network ISIS XX (process) GE ASG-3

ASG-4

RSG-2 (RR)

RNC

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Route Solution Configuring priorities of routes advertised by RSGs and ASGs when independent RRs are deployed 1. Ensure that priorities of routes that the ASG side advertises to RR-1 are higher than those of routes that the ASG side advertises to RR-2. Configure the priorities of routes that the ASG side advertises to RR-1 t o decrease along the counter-clockwise direction in a specific step, and the priorities of routes that the ASG side advertises to RR-2 t o decrease along the clockwise direction in a specific step (t o ensure VPN FRR for X2/FMC services). In this manner, two routes are reflected to the RSG, and VPN FRR can be implemented. 2. Ensure that priorities of routes that the RSG side advertises to RR-1 are higher than priorities of routes that the RSG side advertises to RR-2. Configure the priorities of routes that the RSG side advertises to RR-1 to decrease along the counter-clockwise direction, and the priorities of routes that the ASG side advertises to RR-2 to decrease along the clockwise direction (t o ensure VPN FRR for X2/FMC services). In this manner, two routes are reflected to the ASG side and VPN FRR can be im plemented. 3. Configure RRs in pairs so that VPN FRR can be implemented. 1. Cluster-IDs of two RRs must be the same. 2. A VPN service has only one RD on an entire network.

ASG-1

RR-1

ASG-2

RSG-1 STM-1

BTS/Node B E1/FE CSG eNode B IGP Planning

Bearer network ISIS ZZ (process)

ISIS XX (process) GE RSG-2

ASG-3 BGP Planning

BSC

ASG-4

RR-2

RNC



Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Service Deployment Both E1 and ATM services are carried

MS-PW/CW enabled

by TDM channels. E1 interfaces on base stations transmit IMA services. When a base station transmits multiple channels of E1/IMA services, multiple TDM channels are required to map E1 interfaces. These TDM channels are not bound.

PW1

PW2

RSG

ASG BTS/Node B

STM-1

CSG ISIS ZZ (process)

ISIS XX (process)

Bearer network

E1/FE GE eNode B TDM

TDM

TDM

PW1 TE1 ETH1

E1/ATM service

ETH service

PW1 Swap

TE1 ETH2

TDM Swap

TDM

PW2 TE2 ETH3

PW2 Swap

TE2 ETH4

TDM

BS C RNC

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Service Deployment MS-PW/CW enabled

Extended device deployment

PW2

PW1

RSG

PW2

ASG BTS/Node B CSG ISIS ZZ (process)

PW3

ISIS XX (process)

TDM

TDM

PW1 TE1 ETH1 E1/ATM service

ETH service

TDM

PW1 Swap

TE1 ETH2

TDM

PW2 Swap

TE2 ETH3

PW2 Swap

TE2 ETH4

N×E1 Green line: standby PW

PW5

eNode B

BS C

GE ISIS YY (process)

Bearer network

E1/FE

TDM

Red line: active PW

TDM Swap

TDM

PW2 TE2 ETH3

PW2 Swap

TE2 ETH4

TDM

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Service Deployment L3VPN used to carry end-to-end Ethernet services between CSGs and RSGs Iub interface from the BSC/RNC to base stations

HVPN (Hierarchy VPN)

L3VPN

L3VPN

RSG

ASG

BS STM-1 C

CSG BTS/Node B E1/FE

ISIS ZZ (process)

ISIS XX (process)

Bearer network GE

eNode B PDU

PDU

PDU

PDU

PDU

PDU

IP

IP

IP

IP

IP

IP

ETH0

VRF1

VRF2

ETH5

TE1

E1/ATM service

ETH service

ETH1

Swap

VRF1 TE1 ETH2

Swap

VRF2 TE2 ETH3

Swap

TE2 ETH4

RN C



Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Reliability  Deploy 1:1 or 1+1 E-APS based on BSCs/RNCs from different vendors.  Deploy detection time of BFD for TE-LSP and BFD for PW in hierarchical mode to protect links and end-to-end PWs , respectively.

PW1

PW2

RSG

ASG BTS/Node B

STM-1

CSG Primary PW

Bearer network

ICB PW

E1/FE GE

BS C RNC

eNode B PW

TE Tunnel

PW PW

TE Tunnel

PW

Protection scheme TE LSP 1:1 & PW Redundancy BFD for TE-LSP & BFD for PW Detection technology

MS-PW

HVPN

E-APS (standalone mode) E-APS

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Reliability 6

2

A

CSG BTS/Node B

C

4 ASG B Primary PW

1

8 RSG D

Bearer network

STM-1 E

10

ICB PW

RNC

E1/FE eNode B

3 PW

TE Tunnel

Protection scheme Detection technology Fault Point

Protection Mode

BSC

Protection Scheme

GE

5

9

7 PW PW

TE Tunnel

TE LSP 1:1 & PW Redundancy BFD for TE-LSP & BFD for PW

PW E-APS (standalone mode) E-APS

Traffic Path (Using TE Tunnels/E-APS

A

TE-HSB protection

BFD for TE-LSP

Path in the case of a fault: ①③⑤④⑥⑧⑩－》Path after the fault is cleared: ①②④⑥⑧⑩

B

PW protection

BFD for PW+PW Redundancy

Path in the case of a fault: ①③⑤⑦⑨⑧⑩－》Path after the fault is cleared: ①②④⑥⑧⑩

C

TE-HSB protection

BFD for TE-LSP

Path in the case of a fault: ①②④⑤⑦⑨⑧⑩－》Path after the fault is cleared: ①②④⑥⑧⑩

D

PW protection/gateway protection

BFD for PW+PW Redundancy/E-APS

Path in the case of a fault: ①③⑤⑦⑨⑩－》Path after the fault is cleared: ①③⑤⑦⑨⑩ (APS does not switch back.) －》Path after the fault is cleared: temporarily ①③⑤⑦⑨⑧⑩ Finally: ①②④⑥⑧⑩ (APS switches back.)

E

Gateway protection/PW protection

E-APS/PW Redundancy

Path in the case of a fault: temporarily ①②④⑥⑧⑨⑩ finally: ①③⑤⑦⑨⑩ －》Path after the fault is cleared: ①③⑤⑦⑨⑩ (APS does not switch back.) －》Path after the fault is cleared: temporarily ①③⑤⑦⑨⑧⑩ Finally: ①②④⑥⑧⑩ (APS switches back.)

MS-PW

HVPN

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Reliability RSG-1 MASTER PW SLAVE PW

CSG

W P B C I

ASG

RSG-2

CSG single-homed to an ASG: Deploy a primary and a secondary PW to from a CSG to an ASG and then to two RSGs.

RSG-1 B W C P I

MASTER PW SLAVE PW

CSG

ASG

RSG-2

ASG

CSG

MS-PW

RSG

HVPN

RSG single-homed to an RNC: TA master PW and a slave PW can be deployed. The deployment method for CSGs is the same as that for RSGs.

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Reliability Master E-APS technology introduction  APS is used on SDH interfaces (such as CPOS interfaces) to provide redundancy protection. Similar to LMSP, the APS mechanism uses K1/K2 bytes in multiplex section overheads in SDH frames to exchange switching protocol information. Alarms at the SDH layer trigger APS switching. E-APS is a crossequipment protection switching mechanism.  E-APS is available in two modes: 1:1 and 1+1. In 1:1 mode, the transmit end transmits packets to a single link, and the receive end receives the packets from this link. In 1+1 mode, the transmit end s ends identical packets to the active and standby links, and the receive end selectively receives packets from the active link.  E-APS is available in two modes: single-ended or dual-ended. In single ended switching mode, if one optical fiber in a pair of optical fibers is interrupted, the packets on the optical fiber are switched and packets on the normal optical fiber rem ain unchanged.  It is recommended that you use 1+1 E-APS in single-ended and non-revertive mode. Configure the independent mode for PW redundancy.

Single-fiber failure Master BSC/aGW

Core and aggregation layers

Slave E-APS Slave Master

Master BSC/aGW Single-fiber failure Slave

Core and aggregation layers

E-APS Slave

MS-PW

HVPN

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

Key Technical Solutions of IPRAN Networks - Reliability If VRRP needs to be deployed for interconnection between RSGs and RNCs, RNCs must support configuration of the same IP address for two different interfaces. If RNCs do not support the configuration, the RSGs can be directly connected to the RNCs. Different interconnection modes are used for RNCs from different vendors.  Use TE-HSB to protect links.  Use VPN FRR to protect PEs.  Deploy multiple aggregated links between RSGs to provide redundancy.  Deploy detection time of BFD for TE-LSP and BFD for PW in hierarchical mode to protect links and PEs respectively.

L3VPN

L3VPN RSG

ASG

STM-1

CSG BTS/Node B

Bearer network

E-VRRP

E1/FE GE eNode B

Hierarchy VPN

Protection scheme

Detection technology

MS-PW

HVPN

TE Tunnel

TE Tunnel

TE LSP 1:1(TE-HSB)

TE LSP 1:1(TE-HSB)

TE TUNNEL (VPN FRR)

TE TUNNEL (VPN FRR)

BFD for TE-LSP

BFD for TE-LSP

BFD for TE-Tunnel

BFD for TE-Tunnel

BSC

E-VRRP BFD FOR VRRP

RNC

NMS Deployment

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Reliability VALNIF + VRRP (mode 1)  Deploy VRRP on RSGs (deploy VLANIF interfaces), configure the RNC to be dual-homed to two RSGs, and specify the virtual IP address of

VRRP as the default gateway IP address for wireless devices.  Configure GE interfaces that connect the RNC and RSGs to work in auto-negotiation mode so that a s ingle-fiber failure can be detected.  If the RNC works in master/slave mode, the master RSG forwards received traffic to the master interface on the RNC.  Configure static routes from RSG1/RSG2 to the logical interface address of the RNC with the next-hop address being the RNC interface address

(192.1.1.4). Configure private static routes to be advertised into BGP.

Determine the interconnection mode based on the wire devices.

RSG-1 VRF1:192.1.1.1/29 192.1.1.4/29 IPRAN

VRRP Virtual-IP: 192.1.1.3/29

Node B

VRF1:192.1.1.2/29 RSG-2

MS-PW

HVPN

RNC GW:192.1.1.3

Do not bind static routes with any interfaces. W hen the link between RSG-1 and the RNC is interrupted, traffic is forwarded from RSG-1 to RSG-2 and then to the RNC so that the upstream traff ic is consistent with the downstream traffic.

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

Key Technical Solutions of IPRAN Networks - Reliability IGP + static routes (mode 2)  Use IP addresses with 30-bit masks f or interconnection between the master/slave RSGs and different interfaces on the RNC.  Configure IS-IS multi-instances between the master RGS and the slave RGS. Configure static routes from RSG1/RSG2 to the logical

interface address of the RNC. Import private static routes into IS-IS and BGP for advertisement. Advertise private static routes and private IGP routes into BGP.  Configure GE interfaces that connect the RNC and RSGs to work in auto-negotiation mode so that a single-fiber failure can be detected.  Configure BFD for IS-IS to quickly detect the IS-IS status.  If the RNC works in master/slave mode, the master RSG forwards received traffic to the master interface on the RNC.

Determine the interconnection mode based on the wire devices.

RSG-1 VRF1:192.1.1.1/30 IPRAN

Node B

192.1.1.2/30 VRF1:ISIS multi-instance BFD for ISIS 192.1.1.6/30 VRF1:192.1.1.5/30 RSG-2

RNC

Bind static routes with interfaces.

MS-PW

HVPN

NMS Deployment

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

Key Technical Solutions of IPRAN Networks - Reliability IGP (mode 3) Use IP addresses with 30-bit masks f or interconnection between the master/slave RSGs and different interfaces on the CE. Configure OSPF multi-area between the master/slave RSGs and the CE. In reuse scenarios, configure the RSGs to import OSPF

routes into BGP in a VPN. Configure GE interfaces that connect the CE and RSGs to work in auto-negotiation mode so that a single-fiber failure can be

detected. Configure BFD for OSPF to quickly detect the OSPF status.  After receiving traffic, the RSGs forward the traffic according to priorities of routes learnt from the OSFP area at the CE side.

RSG-1

192.1.1.2/30 VRF1:192.1.1.1/30

RANCE-1 RNC

VRF1:OSPF multi-area

IPRAN

BFD for OSPF Node B RSG-2

VRF1:192.1.1.5/30 192.1.1.6/30

RANCE-2

RAN CE reused

MS-PW

HVPN

NMS Deployment

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Reliability L3VPN 2 BTS/Node B

L3VPN 4 ASG B

A

CSG 1

6

C

8 RSG D

Bearer network

E1/FE eNode B

5 Hierarchy VPN

3 TE Tunnel

Protection scheme Detection technology Fault Point

Protection Mode

7 TE Tunnel

TE LSP 1:1 (TE-HSB)

TE LSP 1:1 (TE-HSB)

TE TUNNEL (VPN FRR)

TE TUNNEL (VPN FRR)

BFD for TE-LSP

BFD for TE-LSP

BFD for TE-Tunnel

BFD for TE-Tunnel

Protection Scheme

9

STM-1 E GE

BSC 10 RNC

E-VRRP BFD For VRRP

Traffic Path (Using TE Tunnels/E-APS)

A

TE-HSB protection

BFD for TE-LSP

Path in the case of a fault: ①③⑤④⑥⑧⑩－》Path after the fault is cleared: ①②④⑥⑧⑩

B

VPN FRR protection

BFD for TE-Tunnel

Path in the case of a fault: ①③⑤⑦⑨⑧⑩－》Path after the fault is cleared: ①②④⑥⑧⑩

C

TE-HSB protection

BFD for TE-LSP

Path in the case of a fault: ①②④⑤⑦⑨⑧⑩－》Path after the fault is cleared: ①②④⑥⑧⑩

D

VPN FRR protection/gateway protection

BFD for TE-Tunnel BFD for VRRP

Path in the case of a fault: ①②④⑤⑦⑨⑩－》Path after the fault is cleared: ①②④⑥⑧⑨⑩ (RNC does not switch back.) －》Path after the fault is cleared: ①②④⑥⑧⑩ (RNC switches back.)

E

Gateway protection

BFD for VRRP

Path in the case of a fault: ①②④⑥⑧⑨⑩ －》Path after the fault is cleared: ①②④⑥⑧⑨⑩ (RNC does not switch back.) －》Path after the fault is cleared: ①②④⑥⑧⑩ (RNC switches back.)

MS-PW

HVPN



Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - QoS Deployment ASG BTS/Node B

RSG

STM-1

CSG

BSC Bearer network

Access ring

E1/FE

RNC GE

eNode B Access-layer CSG  Traffic shaping/policing  Traffic classification  Priority mapping  Queue scheduling Equipment CSG

ASG RSG

Core-layer RSG  Traffic shaping/policing  Traffic classification  Priority mapping  Queue scheduling

Aggregation-layer ASG  Priority mapping  Queue scheduling

QoS Deployment Based on the DSCP values added by base stations, configure CSGs to remark priorities of packets from the base stations differently in different solutions (if the DSCP values added by base stations map EXP values, CSGs do not remark priorities but mark that the priorities are trusted). Normally, priorities for VPN services are mapped to the EXP values of external LSPs. A CSG directly identifies and maps priorities if packets from base stations carry priorities (802.1P or DSCP); otherwise, performs traffic classification. When an ASG is swapping outer tags, EXP values are also mapped. An ASG maps packet priorities and schedules packets based on priorities. An egress RSG pops outer LSP tags, remarks EXP values into DSCP fields of IP packets and forwards the packets to the wireless devices. If the PHP function is configured, the penultimate device pops outer LSP tags, maps EXP values into inner LSP lags, and forwards the packets to wireless devices. An RSG performs operations similar to those on the CSG.



Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Clock Deployment Frequency synchronization Synchronous Ethernet: Synchronous Ethernet is a preferred frequency synchronization solution. The standard SSM is enabled. If W DM devices are involved, ensure that all W DM devices support transparent transmission of synchronous Ethernet packets. Time synchronization  1588v2: 1588v2 is the only solution that implements time synchronization. This solution has high requirements on intermediate networks and is not recommended currently.  Base stations on the live network are connected to GPS for time synchronization.

Overview

Wireless Standard

Precision Requirement for Clock Frequency

Precision Requirement for Clock Phase

GSM

0.05ppm

NA

WCDMA

0.05ppm

NA

TD-SCDMA

0.05ppm

+/-1.5us

CDMA2000

0.05ppm

+/-3us

Synchronous Ethernet

Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

QoS Deployment

Reliability

Clock Deployment

NMS Deployment

Key Technical Solutions of IPRAN Networks - Clock Deployment  Planning principle: top to bottom, separated layers, break up the same layer, upper left and lower right, links connected to an upper

layer ring function as BITS. If a link between two BITSs is interrupted, pseudo-synchronous state is generated (which does not affect the tracing quality in theory).  Enable the standard SSM (clock levels can be carried).  Select clocks by comparing clock levels and then clock priorities.  It is recommended that the first node connect to BITSs through 2 Mbit/s external interfaces for frequency synchronization.  Ensure that a clock chain has a maximum of 20 hops along either the primary or second direction. Priorities of synchronization sources:  A smaller value indicates a higher

1

1

BITS-1

2 2

BTS/Node B

2

1 1

2

1

1

1 STM-1

2

2 1 2 Aggregation layer

1 2

eNode B

2 2

Overview

1

1

2

BSC 1

1

2

1

Core layer

1

RNC 2

2

GE

2

Synchronous Ethernet

priority. Source selection does not involve the sources that are not configured with priorities. With the same priority, source preference is BITS > INTERFACE > PTP. With the same source type, a source with a smaller port/slot ID is preferred.

BITS-2



Solution Overview

Physical Topology

Resource Planning

Route Deployment

Service Deployment

Reliability

QoS Deployment

Clock Deployment

Key Technical Solutions of IPRAN Networks - NMS Deployment Requirements on NMS:  The U2000 manages ATNs, CXs, and NE40Es in a unified m anner and performs end-to-end topology management, service provisioning, fault diagnosis, and performance monitoring.  According to the live network conditions, configure the NMS to be single-homed or dual-homed to devices in core equipment rooms.  The plug-and-play function enables ATNs on the acc ess ring to go online automatically. Network deployment:  Deploy the NMS in the public network management mode. That is, NMS information shares IGP with services.  Import the management addresses and interface addresses of the access ring into the aggregation ring for the U2000 to manage and the plug-in-play function to use.  Import the IP address segment of the U2000 into the access ring so that t hey can communicate with each other.  To avoid route loops, set metric to a value greater than the m aximum possible value in actual networking when introducing a route, for example, 20000.

RSG

ASG BTS/Node B

BSC

CSG Access ring

Bearer network U2000

eNode B ISIS YY (process)

ISIS ZZ (process)

RNC

NMS Deployment

Contents Objective of the IPRAN Solution Key Technical Solutions of IPRAN Networks Key Delivery Process of the IPRAN Technical Solution

Key Process of IPRAN Delivery Marketing solution

HLD LLD

Project TD

Customer requirements/Networking diagram from the design institution

HLD design/customer's regulations/diagram for physical installation/slot layout

DD Hardware installation

Interface interconnection table/slot layout/fiber patch cord

Engineering team

Plug-and-play Software commissioning engineer

Service provisioning

U2000 plug-and-play

U2000

Key Process of IPRAN Delivery-Network Design and Deployment Procedure for SingleOSS Office/Design institution

Topology information (information collection and updating)

Command template

Designer

Engineering files/link planning data

Idle equipment

Deployment personnel

Command template

Basic configuration script

Service template

Equipment carrying services

Key Process of IPRAN Delivery Network Resource Planning

Service Resource Planning

CSG/ASG/RSG Data Preparation Equipment carrying services

Idle equipment Management address planning Interface address planning Subinterface, VLAN, and VRRP VLAN planning IGP area planning AS planning

Base station-RNC homing relationship Base station address allocation Base station VLAN allocation VPN resource planning (RT/RD) Base station QoS/bandwidth planning Physical interface and CPOS timeslot planning

ETH service

ETH service

Tunnel deployment

Port deployment

VPN deployment BFD deployment Port deployment

TDM service Tunnel deployment

Device and port naming planning

Base station QoS planning

LDP deployment

Clock planning

Planning on the number of E1/ETH interfaces on base stations

PW deployment

Tunnel number

BFD deployment

PW label

Synchronous clock deployment

BFD flag

Port deployment

TDM service PW deployment BFD deployment Synchronous clock deployment Port deployment

Topology design Device panel and interface interconnection design Clock topology design

Ipran Lld Solution

Recommend Documents