
R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255



Jos Manuel Tapia / 9.12.2008

Agenda

Use case introduction

Virtual LANs

Site solution and addressing

Protection

QoS

Q&A


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Network topology

RNC

DCN Router

DCN

NetAct

Site Equipment

VRRP/ HSRP

Multi-Layer Routers

Operator L2 Network

ToP Master


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Virtual LANs


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Shared network

Operators that own the Ethernet network will typically use it to support a variety of services:

Own mobile backhaul

Other backhaul networks

Enterprise VPN

Home access

Etc

To guarantee that the mobile network traffic is not mixed with traffic for the other services, a typical mechanism to separate the traffic in a layer 2 network is the use of VLANs

Additionally it is good practice to divide the L2 network broadcast domain, to increase security and resilience


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Operator L2 Network

Virtual LANs configuration (I)

Enterprise VLAN

One VLAN per Node B

RNC site

RNC

ToP Master clock

CIR

VLAN Trunk

Mobile backhaul VLANS CIR

CIR


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Virtual LANs configuration (II)

There is one VLAN defined between each Node B and the RNC site routers (for actual customer cases, some Node Bs can share the VLAN)

There are no VLANs between the site routers and the RNC

There are no VLANs between the site routers and ToP master

RNC site router is responsible for the tagging, as well as the Node Bs

Both VLAN id and priority is marked in each packet RNC site router derives the VLAN id from the Node B IP address

VLAN priority is derived from the DSCP


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Site solution and addressing


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




RNC Site Solution RNC2600

ICSU 0

ICSU 2 (SP)

OMS

OMU (WO)

RNC2600

NPGE0 (WO)

NPGE1 (SP)

OMU (SP)

ESA24-0

-2 NPGEs (2N)

-Only one GbE port is used

-In real customer cases additional NPGEs to be added as needed

- 3 ICSUs (N+1)

-In real customer cases additional NPGEs to be added as needed

-1 OMS (no redundancy)

-2 OMU (1+1)

-2 ESA24

Units not relevant for the use case are excluded for clarity

GE0

GE1

GE0

GE1

ESA24-1

ICSU 1


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




RNC Site Solution Dual Cisco 7609 routers

Site solution tailored for fast Ethernet protection Leverage Layer 2 switching functionality of the routers

No additional Ethernet protection required in routers Working and spare NPGE ports are connected via layer 2 Using trunk links between the routers Upper router (#1) has higher priority than the lower router (#2)

Operator Network

(IP based)

RNC

NPGE-0 (WO)

GE0

GE1

Multi-layer Router #1

VLAN 10

Multi-layer Router #2

NPGE-3 (SP)

GE0

GE1

VLAN 20

VLANs 10 & 20

VLAN 10

VLAN 20

VLANs 10 & 20

WAN

WAN

Etherchannel


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




RNC Site Solution Symmetricom T5000

RAN synchronization is based Timing over Packet, with the ToP Master clock located in the RNC site

The ToP Master clock is responsible for the synchronization of the RNC and the Node Bs

RNC synchronization is recommended for proper internal behaviour during switchover. Synchronization is done via either 2.048 MHz or 2.048 sync signal

Node Bs are synchronized via IEEE1588. One master can synchronize up to 600 Node Bs (release 1.1, 1Q2009)

Redundancy is provided by equipping dual IOC cards


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




BTS site solution

Flexi

FTIB

Units not relevant for the use case are excluded for

clarity

ToP

Other Flexi units

UltraSite

IFUH

ToP (piggyback)

WAM1

System Module

AXC

WAM2

WAM3

WAM4

WAM5

WAM6

Only one port is used in RU10 (2 more are available)

-Flexi

-1 FTIB (includes ToP server)

-Ultra

-AXC with 1 IFUH

-ToP module

-6 WAMs

FE0

FE0


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




IP subnets

Iub One external subnet for each VLAN, between the RNC site routers and

the Node B

One external subnet in the RNC site, including ToP master and RNC site routers

RNC One internal signalling subnet

One internal/external subnet in the RNC site for DCN

Node B One internal subnet for DCN


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Network configuration Iub user plane and control plane

Subnet

Subnet

Subnet

Subnet

RNC2600

O&M 1.1.4.41/29 1.1.4.42/29

O&M 1.1.4.9/29 1.1.4.10/29

O&M 1.1.4.25/29 1.1.4.26/29

BTS 3

BTS 1

BTS 2

NPGEP 0 (WO)

GE0 1.1.1.1/29

ICSU 00

1.1.2.1/26

C/U-Plane 1.1.4.36/29

C/U-Plane 1.1.4.20/29

1.1.1.4/29

UNI

UN

I

UN

I

UN

I

C/U-Plane 1.1.4.4/29

VL

AN

Tru

nk

VL

AN

11

VL

AN

12 VLAN11

1.1.4.2/28 VLAN12 1.1.4.18/28 VLAN13 1.1.4.34/28

VLAN11 1.1.4.3/28 VLAN12 1.1.4.19/28 VLAN13 1.1.4.35/28

1.1.1.5/29

1 2

3 4

1.1.1.6/29

1.1.4.1/28

1.1.4.17/28

1.1.4.33/28

NPGEP 1 (SP)

GE0 1.1.1.1/29

Site Routers VRRP groups

ICSU 01

1.1.2.2/26

ICSU 2 (SP)

1.1.2.3/26

Subnet

Subnet


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Network configuration DCN

Subnet

RNC2600

O&M 1.1.4.41/29 1.1.4.42/29

O&M 1.1.4.9/29 1.1.4.10/29

O&M 1.1.4.25/29 1.1.4.26/29

BTS 3

BTS 1

BTS 2

OMS

1.1.3.2/28

OMU-0 (WO)

1.1.3.5/28

C/U-Plane 1.1.4.36/29

C/U-Plane 1.1.4.20/29

UNI

UN

I

UN

I

UN

I

C/U-Plane 1.1.4.4/29

VL

AN

Tru

nk

VL

AN

11

VL

AN

12 VLAN11

1.1.4.2/28 VLAN12 1.1.4.18/28 VLAN13 1.1.4.34/28

VLAN11 1.1.4.3/28 VLAN12 1.1.4.19/28 VLAN13 1.1.4.35/28

DCN

ESA24-1

ESA24-0 1.1.3.5/28

OMU-1 (SP)

1.1.3.5/28

1.1.3.5/28

1.1.3.2/28

1.1.3.1/28

1.1.3.2/28

1 2

3 4

1.1.1.6/29

1.1.4.1/28

1.1.4.17/28

1.1.4.33/28



R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Subnet

Subnet

Subnet

Subnet

Network configuration Iub synchronization

O&M 1.1.4.41/29 1.1.4.42/29

O&M 1.1.4.9/29 1.1.4.10/29

O&M 1.1.4.25/29 1.1.4.26/29

BTS 3

BTS 1

BTS 2

C/U-Plane 1.1.4.36/29

C/U-Plane 1.1.4.20/29

UNI

UN

I

UN

I

UN

I

C/U-Plane 1.1.4.4/29

VL

AN

Tru

nk

ToP

VL

AN

11

VL

AN

12 VLAN11

1.1.4.2/28 VLAN12 1.1.4.18/28 VLAN13 1.1.4.34/28

VLAN11 1.1.4.3/28 VLAN12 1.1.4.19/28 VLAN13 1.1.4.35/28

1.1.5.17/29

1.1.5.20/29

1.1.5.21/29

1 2

3 4 5

1.1.1.6/29

1.1.4.1/28

1.1.4.17/28

1.1.4.33/28

1.1.5.22/29



R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Protection


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




HSRP virtual router

NPGE failure

RNC2600

NPGEP 0 (WO)

GE0 1.1.1.1/29

1.1.1.5/29

NPGEP 1 (WO)

GE0 1.1.1.1/29

O&M 1.1.4.25/29 1.1.4.26/29

BTS 2

C/U-Plane 1.1.4.20/29

UN

I

1.1.1.4/29

The site routers will forward the traffic between the new RNC port and the working UNI

The default gateway is protected by VRRP/HSRP in this scenario

Under normal operational conditions the upper router has higher HSRP priority, thus this router will reply to the ARP request and NPGE0 will use it as its gateway to route all the traffic

Packets are now delivered from NPGE1 to the upper router via the lower router and from there to the Node B as usual

1.1.1.6/29 (active)

1.1.1.6/29 (standby)

Legend:

Physical IP address

Virtual IP address (act.)

Virtual IP address (stby)


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




UNI failure

HSRP virtual router

RNC2600

NPGEP 0 (WO)

GE0 1.1.1.1/29

1.1.1.5/29

NPGEP 1 (WO)

GE0 1.1.1.1/29

O&M 1.1.4.25/29 1.1.4.26/29

BTS 2

C/U-Plane 1.1.4.20/29

UN

I

1.1.1.4/29 VLAN12 1.1.4.18/28

VLAN12 1.1.4.19/28

1.1.1.6/29 (active)

Legend:

Physical IP address



When the active UNI fails, the transport network will activate the spare UNI It will also send MSTP/STP BPDUs to enable the site routers to learn the new network topology, and after topology is learnt, frame forwarding will continue via

the other router


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Router failure

RNC2600

NPGEP 0 (WO)

GE0 1.1.1.1/29

1.1.1.5/29

NPGEP 1 (SP)

GE0 1.1.1.1/29

O&M 1.1.4.25/29 1.1.4.26/29

BTS 2

C/U-Plane 1.1.4.20/29

UN

I

1.1.1.4/29

HSRP virtual router

HSRP responsibility

switchover

RNCs NPGE unit performs switchover in order to utilize physical links towards second router while UNI switchover does the same on the network side

A layer 3 based switchover of the routers gateway functionality is also performed so that NPGEs need only one gateway IP address

NPGE switchover requires the failing router to switch off their ports


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




HSRP virtual router

ToP interface failure

O&M 1.1.4.25/29 1.1.4.26/29

BTS 2

C/U-Plane 1.1.4.20/29

UN

I

1.1.5.17/29

1.1.5.20/29

1.1.5.21/29

Only one ToP port is active at a time. The system is monitoring both ports (later unit redundancy will be available.

After detecting an failure in the Ethernet link, there is a switchover to the other port (in 1.5 ~ 3 seconds)

The ToP master will send a gratuitous ARP through the working port so that the HSRP virtual router will properly switch traffic to the other port

1.1.1.6/29 (active)

1.1.1.6/29 (standby)

Legend:

Physical IP address




R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Quality of Service


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Quality of Service introduction

Traffic classification All other traffic types are classified to some QoS class (PHB) Packets are marked according to the allocated QoS class (DSCP and VLAN p-

bits)

Admission control DCH RT, DCH nRT and HSPA RT traffic is subject to admission control

In this case all NRT HSPA traffic is treated as best effort (i.e. NBR=0 for all HSPA SPIs)

Scheduling Different traffic classes are scheduled according to the traffic class and the

weight assigned to that class

Shaping In this case there is not shaping in RNC and in Node B. Traffic is limited to the

interface rate

Traffic limitation relies on the CAC, on dimensioning and on air interface limitation.

If there is congestion, lower priority traffic will be dropped


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Mean user traffic per BTS

Service Type (RAB) Service bit rate on Iub

[kbps] Mean traffic per BTS (BH)

CS AMR 12.2 Voice 12.2 19.2 Erl

VoIP (Streaming HSPA) GBR: 29.6 4.8 Erl

CS 64 UDI Video 64 3 Erl

DCH PS I/B 64 DL 64 82 kbps



HSPA I/B Max. 14 Mbps 1500 kbps

Three BTSs are used in this case

For UL traffic, the following ratio is applied:

Release 99 (UL/DL): 1/5

HSxPA Rel. 6 (HSUPA / HSDPA): 1/4.3


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Iub Service Level Agreement

Maximum delays

(based on measurements)

Iub+Iur: R99 voice: 50 ms R99 data: 50 ms HSDPA: 200 ms HSUPA: 160 ms

Packet loss: better than 0.1% (10-3)

Recommended network conditions

(based on end-to-end performance targets)

Iub+Iur: Delay: 20 ms or lower Delay variation: below +/- 5 ms

Packet loss: better than 0.01% (10-4) For video streaming applications e.g. lower frame loss of 10 -6 is recommended

Availability: 99.99%

RNC

NB

Eth

SGSN

MGW

NB

Eth

RNC

Eth

Eth

Eth

Iub Iu-PS

Iur

Iu-CS Iub


R 255 G 211

B 8

R 255 G 175

B 0

R 127 G 16

B 162

R 163 G 166

B 173

R 137 G 146

B 155

R 175 G 0

B 51

R 52 G 195

B 51

R 0 G 0

B 0

R 255 G 255

B 255




Q&A

Documents

3G L2 Backhaul Network