Ipran Lld Solution

HUAWEI TECHNOLOGIES CO., LTD.

www.huawei.com

IPRAN ATN+CX (HVPN) Solution Design

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

Copyright Huawei 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 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 issue

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


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 for 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 receive and

transmit all types of services.

Positioning of IPRAN Packet Transport Networks

Intranet/Internet

Inter PLMN

A

Iu-CS

Gp

Gb

Gi

PSTN/ISDN

Node B

RNC

UTRAN

Iub Iu - ps

BTS

BSC

GSM/GPRS

BSS

Abis

SGSN Ga

CG

GGSN

BG

GMLC

SMSC

SCP

HLR/AuC/EIR

DNS

WAP

Gateway

RADIUS

Firewall

C/D

MISUP/MTUP

E

CAP

Lg

Gr/Gf

Gd

CAP

Lg

Gn

Gs Lc

Lh

MSC Server

MGW

IPRAN network

IPRAN network


IPRAN Network Construction Design Roadmap

The hierarchical architecture design between cell site gateways (CSGs), aggregation site gateways

(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.

Access layer

ATN950/950B ATN910

2U 8Slots

1U 4 Slots

Core/Aggregation layer

4U 3 Slots

14U 8 Slots

CX600-X8 CX600-X16 CX600-X3

32U 16 Slots


GE

Core layer

GE

10GE

aggregation ring

BSC/RNC S-GW/MME

eNode B BTS/Node B

FE

GE

CX600-X3

PRC/BITS

U2000

RAN-CE

NE40E-X16

BGP-RR

eNode B BTS/Node B

TDM

ETH

FE

GE

ATN910

CX600-X8

PRC/BITS

TDM

ETH

IPRAN Network Architecture

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.

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.


IPRAN Network Architecture Last Mile Access Aggregation Core BSC/RNC/MME

eNode B

BTS/Node B

MS-PW

2G TDM PWE3

3G ATM PWE3

3G ETH VRF

LTE VRF S1

LTE VRF X2

Hierarchy L3VPN

2G TDM PWE3

3G ATM PWE3

TDM/ATM Services

Ethernet Service

Access Tunnel

L3VPN

PWE3

CSG

ASG

S-GW

RNC

MME

BSC RSG

Core

Aggregation Tunnel

L3VPN

PWE3

X2

UPE SPE

NPE

RANCE

STM-1

GE

E1/FE

3G ETH VRF

LTE VRF S1

Device role Definition Role in the Solution

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

located at the network edge.

UPE/CSG

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

devices.

SPE/ASG

RAN CE RAN-CEs refer to CEs that aggregate traffic from BSCs/RNCs. RSGs can function as CEs if no CEs are

available. It is recommended that independent.

NPE/RSG



Contents



Resource Planning

Solution Overview

Route Protocol Planning Service Planning

Reliability Planning QoS Planning Clock/Time Synchronization Planning

NMS Planning

Physical Topology and Hardware Planning


FTTX

Base

station

Enterpris

e CE

AP

RNC

Internet

Softswi

tch

Key Technical Solutions of IPRAN Networks - Solution Overview

CSG ASG P RSG

ATN950B/ATN950

/ATN910

CX600-X

PW PW

L3VPN L3VPN Ethernet

TDM/ATM

RSVP-TE/LDP RSVP-TE/LDP

ISIS/OSPF ISIS/OSPF

NE40E&CX600

This document uses

RSVP-TE and ISIS as an

example to describe the

solution.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability

Home user

Government/e

nterprise user

WLAN

Mobile phone

user

Device type

Encapsulation

mode

LSP protocol

IGP protocol

Device role

Network Structure Service Model



Service

access

Service core

control layer

2G BTS

E1

cSTM-1/n*E1

BSC

3G NodeB

cSTM-1

RNC

E1

GE

L3V

PN

Broadband

BRAS

L2V

PN

GE

10GE GE

E1 FE

E1 FE

IGP

routing

FE FE

L3V

PN

TD

M P

WE

3

TD

M P

WE

3

TD

M P

WE

3

TD

M P

WE

3

LTE eNodeB

MME

L3V

PN

Government/Ent

erprise leased

line

Governme

nt/Enterpri

se leased

line

FE

FE

Internet

leased line

Internet

L2V

PN

L

2V

PN

L2V

PN

L3

VP

N

VOIP

FE

TG L

3V

PN

L

3V

PN

L2V

PN

L

2V

PN

IGP

routing

L3V

PN

L

3V

PN

OLT

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability

Network Structure Service Model


Key Delivery Process of the IPRAN Technical Solution 3

Contents

Objective of the IPRAN Solution 1 Key Technical Solutions of IPRAN Networks 2

Resource Planning

Solution Overview



NMS Planning



Key Technical Solutions of IPRAN Networks - Physical Topology

CSG ASG Core

BSC/RNC

RAN-CE

Core/Aggregation

Core

Bearer

network

Base station

BSC/RNC

BSC/RNC

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.

Aggregation nodes should form a ring network or be

directly corrected to core nodes. With (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.

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 dual-

homed to aggregation nodes preferably.

Base station

Base station

Base station

Base station

Base station

Base station

Base station

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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability

Physical Topology Hardware Planning


ASG

Dual core equipment rooms, each of which 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.


Core equipment room 2 Core equipment room 1

Aggregation ring 1

Aggregation ring 2 Aggregation ring 3

N10GE

BSC/RNC BSC/RNC

GE/CPOS GE GE/CPOS GE


Aggregation ring 4

Aggregation ring 8


Scenario 1 Scenario 2

District core District core District core District core

Scenario 1: Devices that connect

RNCs/BSCs and the IPRAN network

are newly added and share an

equipment room with the 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 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.

RNC equipment room

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



RNC equipment room

Core equipment room 2 Core equipment room 1 N10GE 10GE

District core 3 District core 4


Aggregation ring 4

Aggregation ring 2

Aggregation ring 11

District core 8

District core 7

Aggregation ring 10

District core 2

District core 1

Aggregation ring 2

Aggregation ring 1

Aggregation ring 3

District core 5 District core 6

Aggregation ring 9



N10GE

Scenario 1 Scenario 2

BSC/RNC BSC/RNC

GE/CPOS GE GE/CPOS GE


If optical cables are

sufficient, fibers indicated

by dotted lines can be

connected.

District core sites can be

built independently or in

pairs.

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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability


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.

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 cross-

area 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.



Access ring 2

10GE

RSG

ASG

CSG Access ring 1

10GE Access ring 3

Access ring 1

Access ring 2

ASG

CSG

CSG

BSC/RNC S-GW/MME

Core

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

Currently, it is recommended that CX600s function as ASGs. The network structures shown in the following figures

are not recommended:

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability


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/Aggregation layer

4U 3 Slots

14U 8 Slots

CX600-X8 CX600-X16 CX600-X3

32U 16 Slots

Access layer

ATN950/950B ATN910

2U 8Slots

1U 4 Slots

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.

VRP inside

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 cabinets.

VRP inside

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability




Contents



Resource Planning

Solution Overview


Reliability Planning QoS Planning

Clock/Time Synchronization Planning NMS Planning



Key Technical Solutions of IPRAN Networks Resource Planning

Name Planning IP Address Planning

Name devices or ports based on

naming rules.

Planning principles

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.

Plan VLANs for subinterfaces.

Plan VRRP VLANs.

Allocate AS numbers by group customers in a unified

manner.

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

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability


Key Technical Solutions of IPRAN Networks - Name Planning

Device naming

Adhere to the following rules when you name 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]

Name Planning

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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability


Planning principles for device management IP

addresses

IP addresses of local packet transport network

devices (loopback addresses) are private IPv4

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

network, allocate consecutive IP addresses if

possible in consideration of network scalability,

and reserve some IP addresses.

When allocating device IP addresses on local

networks, it is recommended that you adhere to

the following rules:

1. Allocate IP addresses by network layer. For

example, allocate different IP address

segments to the core layer, aggregation layer,

and edge layer in ascending order.

2. Use a 32-bit mask for device IP addresses.

3. Allocate consecutive IP addresses to

neighboring devices if possible.

4. Reserve some IP addresses.

It is recommended that you use the public DCN

solution and use IP addresses of interface

loopback0 as the management IP addresses and

device IP addresses.

Key Technical Solutions of IPRAN Networks - IP Address Planning

Access ring 21

Aggregation ring 1

BSC/RNC S-GW/MME

eNode B BTS/Node B

TDM

ETH

FE

GE

RAN-CE

Internet

BRAS

Access ring 11

eNode B BTS/Node B

TDM

ETH

FE

GE

Aggregation ring 2 Lo:10.1.2.1/32

Lo:10.1.1.1/32

Lo:10.1.3.1/32

Lo:10.1.2.2/32

Lo:10.1.1.2/32

Lo:10.1.2.3/32

Lo:10.1.2.4/32

Lo:10.1.3.4/32

Lo:10.1.3.3/32 Lo:10.1.3.2/32

Lo:10.1.1.3/32 Lo:10.1.1.4/32

RAN-CE

IP Address Planning

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability


Key Technical Solutions of IPRAN Networks - IP Address Planning

Planning principles for device interconnection

IP addresses

Interface IP addresses (interconnection IP

addresses) are used for communication between

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.

Interface IP addresses of packet transport NEs

must be unique in an AS. Therefore, private IPv4

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

address segments (such as 172.16.0.0/16).

When allocating device IP addresses on local

networks, it is recommended that you adhere to the

following rules:

1. Allocate IP addresses by ring. Specifically,

allocate addresses as follows: Rings before

chains, closest node on a chain and then

farther nodes in ascending order. Odd

numbered addresses to upper or left interfaces

of links and even numbered addresses to lower

or right interfaces of links on a ring

2. Use a 30-bit mask for device IP addresses.

3. Reserve some IP addresses.

Access ring 21

Aggregation ring1

BSC/RNC S-GW/MME

eNode B BTS/Node B

TDM

ETH

FE

GE

RAN-CE

Internet

BRAS

Access ring 11

eNode B BTS/Node B

TDM

ETH

FE

GE

Aggregation ring 2

10.2.1.2/30

10.2.1.1/30

10.4.1.2/30

10.4.1.1/30

10.3.1.2/30

10.3.1.1/30

10.4.1.26/30

10.4.1.25/30

10.2.1.18/30

10.2.1.17/30

10.2.1.22/30

10.2.1.21/30

10.4.1.5/30

10.4.1.6/30

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability

IP Address 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.

Key Technical Solutions of IPRAN Networks - VLAN Planning

VLAN Planning

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



Contents



Resource Planning

Solution Overview



NMS Planning



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.

Key Technical Solutions of IPRAN Networks - Route Deployment

eNode B

BTS/Node B CSG

ASG

RNC

BSC RSG

STM-1

GE E1/FE

ISIS XX (process) ISIS ZZ (process)

eNode B

BTS/Node B CSG

ASG

RNC

BSC RSG

STM-1

GE E1/FE

100 100

100

100

100

10

10 100

10

10

2000

10 45

Deploy routing

protocols in hierarchical

mode and use IS-IS

multi-processes.

COST

planning

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability

IGP Planning BGP Planning


Last Mile

ISIS 21

ISIS 1000

BSC/RNC S-GW/MME

eNode B BTS/Node B

TDM

ETH

FE

GE

RAN-CE

ISIS 1000

ISIS11

eNode B BTS/Node B

TDM

ETH

FE

GE

ISIS 1000

ISIS 102

ISIS 11 ISIS 21

RAN-CE

ISIS 103


Deploy the same IGP

process for the core

and aggregation layers.

Number IGP processes

of level-2 access rings

and main access rings

consistently.

ISIS 101

Number IGP

processes of rings

or chains single-

homed to a node

on the

aggregation ring

separately. Number IGP

processes of

access rings

chains dual-

homed to a node

on the

aggregation ring

separately.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability




RSVP TE RSVP TE

eNode B

BTS/Node B

CSG

RNC

BS

C

RSG (active)

STM-1

GE E1/FE

ISIS XX (process)

ISIS Level 2

ISIS ZZ (process)

ISIS Level 2

100 100 100

100 100

100 10 10

10 10

10 2000 45

ASG (active)

ASG (standby)

Set the cost of links between RSGs to a value greater than the total cost 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 that 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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability




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 or 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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



BSC/RNC

S-GW/MME

Home user

Government/e

nterprise user

WLAN

Mobile user

FTTX

Base station

Enterpr

ise CE

AP Bearer

network

Bearer

network

Internet

Softswitch


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.

A1

C1

1

A2

C4

A3

C2

C3

C5

N5 N3 N1

N6 N4 N2 2

3

4 5

6

Design of

Explicit Path

Selection

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability




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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



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 RSG/ASG advertises so that traffic is always transmitted to the master 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.

eNode B

BTS/Node B CSG

ASG

S-GW

RNC

MME

BSC

RSG

Core

UPE

SPE

NPE

RANCE

STM-1

GE

E1/FE

Specify the CSG to the UPE mode.

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 CSG transmits

specific routes to

the ASG.

The RSG transmits

specific routes to

the ASG.

The ASG transmits the specific routes of the CSG

to RSGs and changes the next-hop address to be

destined for the ASG.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability




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 to the CSG to 100. In this 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.

Bearer network

eNode B

BTS/Node B

CSG

ASG

RNC

BSC

RSG

STM-1

GE

E1/FE ISIS XX (process) ISIS ZZ (process)

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



Bearer network

eNode B

BTS/Node B

CSG RNC

BSC STM-1

GE E1/FE


ASG-1 ASG-2

ASG-3 ASG-4

RSG-1 (RR)

RSG-2 (RR)


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 specific 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 for X2/FMC

services). In this manner, two routes are available from the ASG side to the RSG side, and VPN FRR can be implemented.

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 can be implemented.

3. Configure RRs in pairs so that VPN FRR can be implemented.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



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 to decrease along the counter-clockwise direction in a specific step,

and the priorities of routes that the ASG side advertises to RR-2 to decrease along the clockwise direction in a specific step (to 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 (to ensure VPN FRR for X2/FMC services). In this

manner, two routes are reflected to the ASG side and VPN FRR can be implemented.

3. Configure RRs in pairs so that VPN FRR can be implemented.

Bearer network

ASG-3

RNC

BSC

RSG-2

STM-1

GE

ISIS XX (process)

eNode B

BTS/Node B

CSG E1/FE ISIS ZZ (process)

RR-1

RR-2

RSG-1

ASG-1

ASG-2

ASG-4


1. Cluster-IDs of two RRs must be the same.

2. A VPN service has only one RD on an entire network.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability




Contents



Resource Planning

Solution Overview



Clock/Time Synchronization Planning

NMS Planning



Key Technical Solutions of IPRAN Networks - Service Deployment

Bearer network

eNode B

BTS/Node B CSG

ASG

RNC

BS

C

RSG

STM-1

GE

E1/FE


TDM TDM

PW1

TE1

ETH1

TDM

PW1

TE1

ETH2

Swap

TDM

PW2

TE2

ETH3

Swap

TDM

PW2

TE2

ETH4

Swap

TDM

PW1 PW2

MS-PW/CW enabled Both E1 and ATM services are carried 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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability

E1/ATM service ETH service



Bearer network

eNode B

BTS/Node B CSG

ASG RSG

GE

E1/FE

ISIS XX (process) ISIS ZZ (process) NE1

PW1 PW2

MS-PW/CW enabled

PW3

ISIS YY (process)

TDM TDM

PW1

TE1

ETH1

TDM

PW1

TE1

ETH2

Swap

TDM

PW2

TE2

ETH3

Swap

TDM

PW2

TE2

ETH4

Swap

TDM TDM

PW2

TE2

ETH3

TDM

PW2

TE2

ETH4

Swap Swap

PW2

PW5

Red line: active PW

Green line: standby PW

BS

C

Extended

device

deployment

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability




Bearer network

eNode B

BTS/Node B CSG

ASG

RN

C

BS

C

RSG

STM-1

GE E1/FE ISIS XX (process) ISIS ZZ (process)

L3VPN L3VPN

HVPN (Hierarchy VPN)

Swap Swap

PDU

ETH0

IP

PDU

VRF1

TE1

ETH1

IP

PDU

VRF1

TE1

ETH2

IP

VRF2

TE2

ETH3

PDU

IP

VRF2

TE2

ETH4

PDU

IP

PDU

ETH5

IP

Swap

L3VPN used to carry end-to-end

Ethernet services between

CSGs and RSGs

Iub interface from the BSC/RNC

to base stations

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability




Contents



Resource Planning

Solution Overview




NMS Planning



Key Technical Solutions of IPRAN Networks - Reliability

MS-PW HVPN

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.

Bearer network

eNode B

BTS/Node B CSG

ASG

RNC

BS

C

RSG

STM-1

GE

E1/FE

Primary PW

TE LSP 1:1 & PW Redundancy

BFD for TE-LSP & BFD for PW

E-APS (standalone mode)

E-APS

ICB PW

PW TE Tunnel PW PW TE Tunnel PW

PW1 PW2

Protection scheme

Detection technology

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability


Bearer network

eNode B

BTS/Node B CSG

ASG

RNC

BSC

RSG

STM-1

GE E1/FE

10 Primary PW

PW TE Tunnel PW

TE LSP 1:1 & PW Redundancy

BFD for TE-LSP & BFD for PW

E-APS (standalone mode)

E-APS

ICB PW

A

1

B D

E

2 4

5

7

6

3 9

8 C

PW TE Tunnel PW

Protection scheme



MS-PW HVPN

Fault

Point

Protection Mode Protection Scheme 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.)

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



MS-PW HVPN

ASG

CSG RSG

PW redundancy

MASTER PW CSG SLAVE PW

RSG-1

RSG-2

PW redundancy

ASG

ICB

PW

MASTER PW CSG SLAVE PW

RSG-1

RSG-2

PW redundancy

ASG

ICB

PW

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 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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



MS-PW HVPN

BSC/aGW Core and

aggregation

layers

E-APS

Single-fiber failure

BSC/aGW Core and

aggregation

layers

E-APS

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 cross-

equipment 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 sends

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 remain 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.

Master

Slave

Master

Slave

Master

Slave

Master

Slave

Single-fiber failure

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



MS-PW HVPN

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.

Bearer network

eNode B

BTS/Node B CSG

ASG

RNC

BSC

RSG

STM-1

GE E1/FE

TE Tunnel

TE LSP 1:1(TE-HSB)

TE TUNNEL (VPN FRR)

BFD for TE-LSP

BFD for TE-Tunnel

E-VRRP

BFD FOR VRRP

TE Tunnel

L3VPN L3VPN

Hierarchy VPN

BFD for TE-LSP

BFD for TE-Tunnel

TE LSP 1:1(TE-HSB)

TE TUNNEL (VPN FRR)

E-VRRP

Protection scheme


QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



MS-PW HVPN

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 single-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.

IPRAN

RNC

Node B

VRRP Virtual-IP:

192.1.1.3/29

VRF1:192.1.1.1/29

VRF1:192.1.1.2/29

GW:192.1.1.3

RSG-1

RSG-2

192.1.1.4/29

Determine the

interconnection mode based

on the wire devices.

Do not bind static routes with any interfaces. When

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 traffic is

consistent with the downstream traffic.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



MS-PW HVPN

IGP + static routes (mode 2)

Use IP addresses with 30-bit masks for 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.

IPRAN

RNC

Node B 192.1.1.6/30

VRF1:192.1.1.1/30

VRF1:192.1.1.5/30

192.1.1.2/30

RSG-1

RSG-2

VRF1:ISIS multi-instance BFD for ISIS

Determine the

interconnection mode

based on the wire devices.

Bind static routes

with interfaces.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



MS-PW HVPN

IGP (mode 3)

Use IP addresses with 30-bit masks for 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.

IPRAN

RNC

Node B

192.1.1.6/30

VRF1:192.1.1.1/30

VRF1:192.1.1.5/30

192.1.1.2/30 RSG-1

RSG-2

VRF1:OSPF multi-area

BFD for OSPF

RANCE-1

RANCE-2

RAN CE reused

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability


Bearer network

eNode B

BTS/Node B CSG

ASG

RNC

BSC

RSG STM-1

GE E1/FE

TE Tunnel

TE LSP 1:1 (TE-HSB)

TE TUNNEL (VPN FRR)

BFD for TE-LSP

BFD for TE-Tunnel

E-VRRP

BFD For VRRP

TE Tunnel

L3VPN L3VPN

Hierarchy VPN

BFD for TE-LSP

BFD for TE-Tunnel

TE LSP 1:1 (TE-HSB)

TE TUNNEL (VPN FRR)

A

1 B

D

E

4

5 7 3

9

8 C 6 2

10

Protection

scheme

Detection

technology


MS-PW HVPN

Fault Point Protection Mode Protection Scheme 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.)

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



Contents



Resource Planning

Solution Overview




NMS Planning



Key Technical Solutions of IPRAN Networks - QoS Deployment

Bearer network

eNode B

BTS/Node B CSG

ASG

RNC

BSC

RSG STM-1

GE E1/FE

Access ring

Access-layer CSG

Traffic shaping/policing Traffic classification Priority mapping Queue scheduling

Aggregation-layer ASG

Priority mapping Queue scheduling

Core-layer RSG

Traffic shaping/policing Traffic classification Priority mapping Queue scheduling

Equipment QoS Deployment

CSG 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.

ASG When an ASG is swapping outer tags, EXP values are also mapped.

An ASG maps packet priorities and schedules packets based on priorities.

RSG 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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability



Contents



Resource Planning

Solution Overview






Key Technical Solutions of IPRAN Networks - Clock Deployment

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

Frequency synchronization

Synchronous Ethernet: Synchronous Ethernet is a preferred frequency synchronization solution. The standard SSM

is enabled. If WDM devices are involved, ensure that all WDM 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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability

Overview Synchronous Ethernet


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.

eNode B

BTS/Node B

RNC

BSC

STM-1

GE

BITS-1

BITS-2

1 2

1

2

1

2

1

2

1 2 1

2

1

2

2

1

2

1

2 2

Core layer Aggregation layer 2

2 1

1

2

1

1

1

2

1

Priorities of synchronization sources:

A smaller value indicates a higher 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.

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability

Overview Synchronous Ethernet



Contents



Resource Planning

Solution Overview






Key Technical Solutions of IPRAN Networks - NMS Deployment

Requirements on NMS:

The U2000 manages ATNs, CXs, and NE40Es in a unified manner 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 access 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 they can communicate with each other. To avoid route loops, set metric to a value greater than the maximum possible value in actual networking when introducing a route, for example, 20000.

ISIS YY (process) ISIS ZZ (process)

Bearer network

eNode B

BTS/Node B CSG

ASG

RNC

BSC RSG

Access ring

U2000

QoS Deployment

Clock Deployment

NMS Deployment

Resource Planning

Solution Overview

Route Deployment

Service Deployment

Physical Topology

Reliability


Contents





Key Process of IPRAN Delivery

HLD

LLD

Hardware installation

Plug-and-play

Service provisioning

DD

Marketing solution

Project TD

Engineering team

Software commissioning

engineer

Customer requirements/Networking

diagram from the design institution

HLD design/customer's

regulations/diagram for physical

installation/slot layout

Interface interconnection table/slot

layout/fiber patch cord

U2000 plug-and-play

U2000


Office/Design institution

Designer

Deployment

personnel

Key Process of IPRAN Delivery-Network Design and Deployment

Procedure for SingleOSS

Topology information (information collection

and updating)

Engineering

files/link

planning data

Command

template

Command

template

Basic configuration

script

Service

template

Idle equipment

Equipment

carrying services


CSG/ASG/RSG Data Preparation Service Resource

Planning

Network Resource

Planning

Key Process of IPRAN Delivery

Management address

planning

Interface address planning

Subinterface, VLAN, and

VRRP VLAN planning

IGP area planning

AS planning

Device and port naming

planning

Clock 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

Base station QoS planning

Planning on the number of E1/ETH

interfaces on base stations

Tunnel number

PW label

BFD flag

Topology design

Device panel and

interface

interconnection

design

Clock topology

design

ETH service

Tunnel deployment

VPN deployment

BFD deployment

Port deployment

TDM service

Tunnel deployment

LDP deployment

PW deployment

BFD deployment

Synchronous clock

deployment

Port deployment

ETH service

Port deployment

TDM service

PW deployment

BFD deployment

Synchronous clock

deployment

Port deployment

Idle equipment Equipment

carrying services

Thank you www.huawei.com

Copyright 2013 Huawei Technologies Co., Ltd. All Rights Reserved. The information in this document may contain predictive statements including, without limitation, statements regarding the future financial and operating results, future product portfolio, new technology, etc. There are a number of factors that could cause actual results and developments to differ materially from those expressed or implied in the predictive statements. Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the information at any time without notice.

Documents

Ipran Lld Solution