IP RAN 2G, 3G & LTE

Muhamad YopanCCIE#38903

Ericsson Indonesia

100NGN Workshop

June 17-19, 2013

Traditional telecommunication network

A dedicated infrastructure is required to support different services

IP convergence refers to the capability of the Internet to act as a single foundation for various functions that traditionally had their own platforms.

IP Convergence

2G & 3G Architecture

RAN

What is IP RAN

IP RAN is a reference solution

2G

3G

LTE

BSC

RNC

cell site

– Physical and logical connectivity– HW recommendations– Redundancy– 2G/3G/LTE/Wifi co-location– Quality of Service– Synchronization– Security– IP Addressing– Management

A reference for how to connect cell site and switch site:

switch siteMBH MPBN

SIU/TCU

MPBN

CPG / MME

IP RAN IP RAN

Switch siterouter

OSS-RC

Synchsrv

IPSecMBH

cell sitecell site

IP RAN Design Goals

The IP RAN solution abstracts away the diverse transport networks -Multiple technologies and providers but one network view for the RAN applications

Provides a unified set of services to the RAN applications-Synch, QoS handling, SLA monitoring, security, ...

Utilizes simple, cost efficient transport services

Enables multiple transports to cell site- Different transports for different traffic types with different requirements (QoS vs. Availability)

Dual transport redundancy

IP RAN solution is aligned with mbh and Mpbn

2G

3G

LTE

BSC

RNC

CGWMSS

MME

CGW

IP RAN MBH

LRAN, Access

MPBN

HRAN, METRO

IP RAN MPBNFor Mobile Core

IP site Infrastructure

Multivendor

MBH

Multivendor

• The IP RAN solution is fully aligned with the Mobile Backhaul and the MPBN solutionsTogether they form “Mobile Transport”, and provides end-to-end transport services.

Mobile Transport

IP RAN Engineering Aspect

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

Competencies required

IPBasic

- 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

IuPs

IuPs

MPLS

MPLS

IuB/IPMub/IP

IuB/IPMub/IP

3G

CBU

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

3G

CBU

3G

Metro E

Synchronization in IP RAN

IP RAN recommends the SoIP solution• SoIP is independent on what transport network is

used as long as it provides IP connectivity and the right characteristics

• Based on standard NTP and/or 1588v2– Same transport network requirements, same sync

algorithm

• SoIP server integrated in the RNC boards– SoIP over NTP only supported

• Standalone SoIP server required for 1588v2• SoIP client in SIU, TCU 02 and RBSes

– 1588v2 currently only supported by the SIU/TCU 02

• Proven in live customer networks

FREQUENCY SYNCRONIZATION USING SIU/TCU

FREQUENCY SYNCRONIZATION WITHOUT SIU/TCU

SECURITY

RAN security challenges

• User plane traffic:– GSM: Abis is not encrypted from BSC to RBS– WCDMA: Iub frames are encrypted (3GPP standard) from RNC to UE– LTE: Can be natively protected using IPSec

• Control plane traffic:Is un-encrypted for GSM, WCDMA and LTE.– Can be protected using IPSec for GSM and LTE– Can be protected using external IPSec equipment for WCDMA

• O&M traffic:– Is protected on application level using SSL for both GSM, WCDMA and LTE

(Ericsson solution)– IPsec is supported for LTE O&M and can be activated if needed, to get an extra

level of security

• Highest priority is to protect BSC/RNC site and OSS from external intrusion.

IPSec in LTE• eNodeB supports IPSec (currently for IPv4 only) to protect traffic

– Tunnel mode– Encryption and integrity (ESP) according to 3GPP

• Anti-replay protection• 3DES and AES encryption• MD5 and SHA-1 integrity

– Certificates based IKEv2 key handling

• Separate tunnels for UP/CP/Synch and O&M. – One IPsec tunnel for UP/CP and Synch, and one for O&M. (O&M is also

SSL-protected inside the IPsec tunnel).– Redundant tunnels monitored using Dead Peer Detection

• Auto integration also supports IPSec– Using IKEv2 Configuration Payload

QUALITY OF SERVICE

BEHAVIOR OF FLOWS

QOS PRIORITY HANDLING• IP RAN solution provides

recommendations for:

– Traffic classification

– Prioritization

– Scheduling

– Link dimensioning (including for adaptive modulation)

•The solution resolves RAN congestion in a controlled and predictable way• Common QoS recommendations apply for GSM/CDMA/WCDMA/LTE

24

PCRF

GbIu

S1-MME

Iu

S11

Gy

Rx+

SGi

HLR/HSS

S5

User planeControl plane

Gn

S13

3G

LTE

2G

PDN

Serving

DM USD

GxGateway

MME

SGSN

Gn

S1-U

GrEIR

S10

S16

X2 S6a

CSFB/IWF

SGs

OFCS

MME

GMLC SMLC

SLgSLs

IMS

E-CSCFP-CSCF

Mw

M1MGCF PSAP

Positioning

Emergency

E/// OSS -SQWOSS

Mul

Lte architecture

The transformation

Backhaul (IP/Ethernet)

NodeBBTS

Radio intelligent moving to eNodeB

Backhaul transition to IP/Ethernet

RNC bearer mobility

evolves to SGW

MSC voice and packet

data switching

evolve into SGW

CS and PS evolve into

a unified all-IP, IMS domain

Best effort to e2e QoS IP anchor moves to PDH GW

Internet browsing to Web 2.0+

Backhaul PS CoreRNC

SGSN GGSN

CS Core

eNodeB SGW

MMEPCRF

PDN GW

Today

LTE