3. 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
6. 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 site
MBH MPBN
SIU/TCU
MPBN
CPG / MME
IP RAN IP RAN
Switch site
router
OSS-RC
Synch
srv
IPSecMBH
cell sitecell site
7. 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
8. IP RAN solution is aligned with
mbh and Mpbn
2G
3G
LTE
BSC
RNC
CGW
MSS
MME
CGW
IP RAN MBH
LRAN, Access
MPBN
HRAN, METRO
IP RAN MPBN
For Mobile Core
IP site
Infrastructure
Multivendor
MBH
Multivendor
9. • 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.
Mobile Transport
15. 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
19. 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.
20. 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
23. 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
25. The transformation
Backhaul (IP/Ethernet)
NodeB
BTS
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 Core
RNC
SGSN GGSN
CS Core
eNodeB SGW
MME
PCRF
PDN GW
Today
LTE
