Ip ran v1.1

IP RAN Network Design 2G & 3G

Muhamad YopanCCIE#38903

Ericsson Indonesia

CCIETalk session, May 12, 2013

Meet Challenges in Mobile Backhaul

2G/3G Network Architecture

IP RAN Solution

What it means• IP RAN is a full IP connectivity solution to enable smooth

and future-proof introduction and deployment of IP transport in RAN.

• IP RAN covers IP feature in GSM and IP in WCDMA.• IP RAN is a tested and verified solution and is aligned

with M-PBN.

Scope• Designs maintaining RAN performance

– Capacity & Synchronization– QoS & Traffic Separation– Network Security

• Future proof designs based on verified IP-RAN solution

• Automated Design and Integration configuration transfer

• Competence to handle the complexity of Multi-vendor networks

Competencies requiredIPBasic

- IP Addressing- VLAN- Static routing- Dynamic routing (OSPF, IS-IS)- STP (MSTP, PVST, RSTP)- VRRP, HSRP- QOS- BFD

Optional:- IP MPLS - VPN L2/L3- MPLS TP- Tunneling- Metro E- IP SLA

Mobile broadband- 2G Architecture- 3G Architecture- Product Knowledge

Functionality

• Transport Connectivity• Network Synchronization• Quality of Service• Security

Transport Connectivity

Synchronization in IP RAN• In traditional GSM/WCDMA access networks, the distribution of a

reference clock signal to the RBS is supported by the SDH and PDH technology

• In Packet Transport Network the RBS cannot be synchronized by traditional PDH/SDH layer 1 interface

Network Synchronization over IP • Transport transparent and independent (L2, L3, access, backhaul)

• Client/Server solution, integrated in the certain boards

• Proven in real networks

• No need for GPS, ITU1588, Sync Over Ethernet solutions

• Use protocols available today (NTP/PTP)

QoS requirements on IP RAN

• Telecom Grade requirements on Transport NW• Different requirements on voice and data • Service Performance seen by users is degraded with increased

delay or frame loss

QoS Priority Handling

• Handletraffic according to Network, Userand Servicedimensions• Common QoS rules for GSM/WCDMA/LTE• A framework for resolving RAN congestion in a controlled and

predictable way, when demand for resources exceeds supply.

Quality of Service

• QoS traffic handling

– Traffic classification for both GSM & WCDMA

– Marking: DSCP and/or p-bit

– Queuing

Queuing capabilities are hardware dependent. It is recommended to use three or four queues in the Transport Network.

QoS Supported in IP RAN

• The use of DSCP– Application mapping to DiffServ is recommended to be the same within

a network domain (dedicated RAN, Dedicated Core or Common multi-service).

• The use of p-bits– Mapping to Ethernet-QoS can be used differently due to queue-

principles and congestion behavior.

– Remarking/Remapping– If the transport network could handle QoS on both, L3 and L2, the Per

hop-behavior (DiffServ value) is the one to act upon.

Network planning & design key for success

Adaptation of Class-of-Service to network conditions

Security• RAN Security:

– Iub user plane frames are encrypted (3GPP standard) from RNC to UE

– Abis user plane is not encrypted from BSC to RBS– Control plane is sent open for bothGSM & WCDMA– O&M traffic is protected on application level for both GSM &

WCDMA– Highest priority is to protect BSC/RNC and OSS from external

intrusion.

Consideration Aspect

• New network architecture between Access and Core networks• Network topology logical and physical• Choice of backhaul network (L2 or L3 IP network)• Network Security, Quality of Service and Synchronization• O&M network• Existing backhaul network and backhaul providers• Core network IP infrastructure• Traffic model and Node & Interface dimensioning• Migration and Future expansion

Related Services

• The IP-RAN Network Design has relationships with the following services:

• Network Strategy Consulting• Microwave Network Design• Optical Network Design• Core Network Design• Product Configuration & Integration• Site Engineering & Installation• Customer Training

IP RAN Network Design Approach

Build

RequirementSpecification

Detailed DesignSpecification

NetworkAcceptance

Addressing

Traffic Modeling

Topology

Security

L3 RoutingL2 Switching

Node & InterfaceDimensioning

Protection & Redundancy

Traffic Separation

Quality of Servicesetting

Solution DesignSpecification

Tunneling &Firewalling

Start-up &Info Gathering

Solution Design

Detailed Design

Conclusion

Integration

Build

Cases

2G Physical Topology

MPLS

BSC

OSS

NTP/PTP Server

Metro Ethernet

Microwave

Microwave

PE 2

PE 1

ME

ME

Microwave

2G

MPLSPE 1

PE 2

SR_AbisVLAN (765)

SR_Abis VLAN (765)

BSC

A side

B Side

Switch Side-A

Switch Side-B

SR_Abis VLAN (765)

SR_Abis VLAN (765)

BSC_Inner VLAN (777)


Interconn VLAN

Interconn VLAN

SR_AbisVRRP IP:

SR_AbisVRRP IP:

OM VLAN (3405)

SR_AbisVLAN (765)

Abis VLANVRRP IP:

OM VLANVRRP IP:

Abis VLAN (3305)

Abis VLAN (3305)

OM VLAN (3405)

Board

Floating IP : x.x.x.67/26Board #0 : x.x.x.68/26Board #1 : x.x.x.69/26Board #2 : x.x.x.70/26Board #3 : x.x.x.71/26

MetroE

OM VRF

OM VRF

OM Vlan forward to OM vrf

BSC_Inn

er (I

nter

nal_A

)

X.x.x.6

5/26

BSC_Inner (Internal_A)

X.x.x.66/26

Static route (Low priority)Administrative Distance: 2


192.168.2.1/30

192.168.2.2/30

Static route (High priority)Administrative Distance: 1

SR_Abis VLAN (765)

Hub Site

Abis Vlan forward to IuB vrf

IuB VRF

IuB VRF

OSS

Static route

Static route


ME

ME

NTP/PTP Server

2G

2G Logical Topology (Southbound)

2G Logical Topology (Northbound)

MPLSPE 1

PE 2

SS7 (100)

SS7 (200)

BSC

A side

B Side

Switch Side-A

Switch Side-B

SS7 (100)

SS7 (200)



Interconn VLAN

Interconn VLAN

OM VLAN (3405)

SS7 (200)

Board

Floating IP : x.x.x.67/26Board #0 : x.x.x.68/26Board #1 : x.x.x.69/26Board #2 : x.x.x.70/26Board #3 : x.x.x.71/26

BSC_Inn

er (I

nter

nal_A

)

X.x.x.6

5/26

BSC_Inner (Internal_A)

X.x.x.66/26



192.168.2.1/30

192.168.2.2/30


SS7 (100

Signaling vrf

Signaling vrf

Static route

Static route


ME

ME



IuPs

IuPs

MPLS

MPLS

IuB/IPMub/IP

IuB/IPMub/IP

3GCBU

3G

Router border Operator 2

IuCs

SGSN in pool

IuCS, IuPS, IuB, IuR

IuCS, IuPS, IuB, IuR

RNCIuCs

Operator BOperator A RAN SHARING TOPOLOGY

Metro E

Router border Operator 1

IuPS vrf

Nb vrf

Static routeIuCS, IuR

IuPS

IuB

PE 1

IuCS, IuR

IuPS

IuB

PE 2

RNC

MSC

SGSN

SGSN 1

SGSN 2

SGSN 3

MSC

PE

PE

PE PE

IuB/IPMub/IP

IuB/IPMub/IP

3GCBU

3G

Metro E

Destination Name Destination Namex.x.x.244/32x.x.x.245/32x.x.x.246/32x.x.x.247/32x.x.x.244/32x.x.x.245/32x.x.x.246/32x.x.x.247/32x.x.x.244/32x.x.x.245/32x.x.x.246/32x.x.x.247/32

y.y.y.49/32y.y.y.50/32y.y.y.53/32y.y.y.54/32

x.x.x.248 /29 SGSN B1x.x.x.248 /29 SGSN B2x.x.x.248 /29 SGSN B3x.x.x.0/26 RNC B1 y.y.y.81 /32 SGSN A2x.x.x.0/28 y.y.y.160/28x.x.x.16/28 y.y.y.176/28x.x.x.64/29x.x.x.72/29x.x.x.96/27 MGW B1 y.y.y.128/26 RNC A1x.x.x.192/27 RNC B1 y.y.y.0/25 MGW A1

y.y.y.160/28y.y.y.176/28y.y.y.0/28y.y.y.16/28y.y.y.0/28y.y.y.16/28y.y.y.0/28y.y.y.16/28

x.x.x.64/29 y.y.y.160/28x.x.x.72/29 y.y.y.176/28

y.y.y.128/26 RNC A1y.y.y.192/26 RNC A2y.y.y.0/26 RNC A3y.y.y.64/26 RNC A4

User Plane x.x.x.96/27 RNC B2 y.y.y.128/26 RNC A1

InterfaceRouter border operator A Router border operator B

IuPS

Control Plane

SGSN B1y.y.y.160/28

RNC A1SGSN B2

y.y.y.176/28SGSN B3

x.x.x.64/29RNC B1 SGSN A1

x.x.x.72/29

User Planey.y.y.128/26 RNC A1

IuCSControl Plane

MSC B1 RNC A1

RNC B1 y.y.y.0/27 MSC A1

User Plane

IuR

Control Plane

x.x.x.64/29

Control Plane

RNC B1

RNC A1

RNC A2

x.x.x.72/29RNC A3

RNC A4

RNC B2 RNC A1

User Plane x.x.x.96/27 RNC B1

Ip ran v1.1

Technology