IP RAN

2G, 3G & LTE

Muhamad Yopan
CCIE#38903
Ericsson Indonesia

100NGN Workshop
June 17-19, 2013
Traditional telecommunication network

A dedicated infrastructure is required to

support different services
IP Convergence
IP convergence refers to the capability of the Internet to act as a
single foundation for various functions that traditionally had their
own platforms.
2G & 3G Architecture
RAN
What is IP RAN
IP RAN is a reference solution

IP RAN Synch
srv
IP RAN
2G OSS-RC
BSC

3G

SIU/TCU
MBH IPSec
CPG / MME

MPBN
MPBN
LTE Switch site
router RNC
MBH

cell site switch site

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

– Physical and logical connectivity
– HW recommendations
– Redundancy
– 2G/3G/LTE/Wifi co-location
– Quality of Service
– Synchronization
– Security
– IP Addressing
– Management
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

BSC CGW
MSS
2G

IP site
3G Infrastructure

CGW
RNC MME
LTE
LRAN, Access HRAN, METRO

IP RAN MBH MPBN

IP RAN MBH
MPBN
For Mobile Core

Multivendor
Mobile Transport
• The IP RAN solution is fully aligned with the
Mobile Backhaul and the MPBN solutions
Together they form “Mobile Transport”, and provides end-to-end
transport services.
IP RAN Engineering Aspect
IP RAN Network Design Approach
Requirement Solution Design Detailed Design Network
Specification Specification Specification Acceptance

L3 Routing
L2 Switching

Node & Interface

Addressing Dimensioning

Protection & Build

Traffic Modeling
Redundancy Build

Traffic Separation
Topology
Quality of Service
setting Integration
Security
Tunneling &
Firewalling

Start-up & Solution Detailed

Conclusion
Info Gathering Design Design
Competencies required
IP Mobile broadband
Basic - 2G Architecture
- IP Addressing - 3G Architecture
- VLAN - Product Knowledge
- 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
 Operator A RAN SHARING Operator B
TOPOLOGY SGSN
in pool

SGSN 2

SGSN 1
SGSN 3
SGSN

MSC

MSC IuPs

IuPs
IuCs

RNC
IuCs
PE
RNC
PE
IuCS, IuPS,
PE
IuCS, IuR
IuPS
Static route IuB, IuR
PE Nb
IuB vrf
MPLS
IuPS
PE 1
vrf
MPLS IuCS, IuPS,
IuB, IuR
Router border Operator 1 Router border Operator 2

IuB/IP
IuCS, IuR Mub/IP
IuPS
IuB

PE 2

IuB/IP
Mub/IP

Metro E IuB/IP
Mub/IP

Metro E IuB/IP
Mub/IP

3G
CBU

3G
CBU 3G

3G
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
•The solution resolves RAN
recommendations for:
congestion in a controlled and
– Traffic classification predictable way
– Prioritization • Common QoS recommendations
– Scheduling apply for
– Link dimensioning (including for GSM/CDMA/WCDMA/LTE
adaptive modulation)
Lte architecture
HLR/HSS

CSFB/IWF
EIR
Gr
DM USD
2G OFCS
Gb SGSN
Iu
Gy PCRF
Iu Gn Gateway
Gx
3G S16 Rx+

Gn
Serving SGi
PDN
S1-U S5 S13
X2 LTE S1-MME S11
S6a
MME
MME SGs
Control plane S10
User plane Mul SLs
SLg
IMS
E/// OSS -SQWOSS Mw
P-CSCF E-CSCF MGCF PSAP
M1 GMLC SMLC
Positioning Emergency

24
The transformation
Today

NodeB
CS Core
BTS
Backhaul PS Core
RNC
SGSN GGSN

MSC voice
CS and PS Best effort
Radio RNC bearer and packet
Backhaul evolve into to e2e QoS Internet
intelligent mobility data
transition to a unified all- IP anchor browsing to
moving to evolves to switching
IP/Ethernet IP, IMS moves to Web 2.0+
eNodeB SGW evolve into
domain PDH GW
SGW

PCRF
MME
LTE Backhaul (IP/Ethernet)

eNodeB SGW
PDN GW