December 2009

IP RAN Concept - Evolution

Transport Network Engineer

Fadi Deek

09/12/20092

Agenda

•What is Ericsson IP RAN solution•Why and When we need IP RAN;•Requirements of an e2e solution;•Advantages & Benefits •Evolving of the current network;•Strategy to Evolve to IP RAN •Different components needed for the evolution:- HW, Physical and Logical connectivity

•Requirements on the TN (SLA) & IP RAN design considerations

3 09/12/2009

What is Ericsson IPRAN solution

IP RAN is a full IP connectivity solution aimed to enable a smooth and future-proofintroduction and deployment of Ericsson’s IP transport in RAN

•It’s used to address the needs of operators that are moving to the next generation IP-based RAN for GSM and/or WCDMA networks

•It covers Ericsson’s Abis over IP feature in BSS07A/B and Iub over IP in WCDMA P6/7

•It gives detailed equipment recommendations for the BSC/RNC and RBS sites for use in the IP RAN environment

•It’s a tested and verified solution and is aligned with the M-PBN

•It highlights the importance of quality-of-service, how to classify and give priority to traffic in IP RAN

•It describes the types of IP transport security and perimeter protection measures that should be taken in IP RAN

Why and When IP RAN

Clear Trend Towards IP

Mobile data traffic growth

More bandwidth is needed

Operators are looking at the migration to All IP

4 09/12/2009

The Way Forward is to ……..

Increase Mobile Backhaul capacity as traffic increase

Reduce costs per bit of transporting data traffic

IP/Ethernet promises low cost CAPEX & OPEX

….. Solve The Next Bottleneck Optimize the network for new subscriber growth

5 09/12/2009

This will require the IP RAN Solution

Residential

Business

Access Aggregation and Metro IP Edge IP Core

IP RANMobile

PBN

Metro Solution

DFA

IPTV

Mobile

LRAN

Mobile BackhaulHRANIP RAN

Mobile

PBNLRAN

MBH TransportHRAN IP

RAN

Metro Solution

Residential

Business

Access Aggregation and Metro IP Edge IP Core

IP RANMobile

PBN

Metro Solution

DFA

IPTV

Mobile

LRAN

Mobile BackhaulHRANIP RAN

Mobile

PBNLRAN

MBH TransportHRAN IP

RAN

IP

RAN

IP

RAN

Metro Solution

6 09/12/2009

Ericsson IP RAN Comprehensive Solution

7 09/12/2009

09/12/20098

GSM/WCDMA IP Co-transport- Leverage on 3G Ethernet backhaul

• Example HSPA 14.4 with 17 Mbps in backhaul

• Migrate GSM to Native Abis over IP

• Introduce Bandwidth sharing

• Saving depend on traffic mix

• 0 extra € to transport GSM traffic

3G

2G/3G Co-site

17 MbpsGE

2E1/T1

Voic

e

Packet over E1/T12G

IP Co transport design rules by thumb

HSPA

(Mbps)

Deployed WCDMA IP

Backhaul cap.

Absorbed

GSM traffic

7.2 10 Mbps ~ 1 E1

14.4 17 Mbps ~ 2 E

21 23 Mbps ~ 3 E1

HSPA/LTE

R99

GSMVoice

Streaming

HSPA+

Edge

HSPA/LTE

R99

GSMVoice

Streaming

HSPA

SIU

Dynamic Bandwidth utilization

Saving depend on traffic mix & Efficiency is achieved with QoSand packet transport sharing. This will lead to a decrease in the backhaul cost.

9 09/12/2009

•About 70 % E1 efficiency gain with Local Connectivity Function (LCF)

•No change to existing RAN design

•Statistical multiplexing

•E1 “bundling” with Multilink Point-to-Point Protocol (ML-PPP)

•Single converged IP backhaul serving 2G/3G/4G Technologies;

•Unifying traffic management and simplifying network operation

•Quality of service (QoS) by traffic type

•Dynamic bandwidth sharing

•Enhanced reliability / ML-PPP

•3GPP-compliant transport

•Investment protection Substantial OpEx reduction

•Growth in GSM revenue without increasing costs

•Expanded call-carrying capacity of existing E1 RAN

•Utilization of existing E1 capacity from GSM to also handle UMTS

•Faster rollout, Cost Transmission reduction which will Lower the TCO and we will

Higher ARPU

•Loss of E1 span does not result in loss of service

•Reduce ATM spending, investment in IP- The future

Advantages & Benefits

10 09/12/2009

Evolving the current Network

RBS Site

• Upgrade the RBSs interfaces to Native IP- Gives minimum overhead- Enable dynamic bandwidth sharing- Provides flexibility and simplicity- provide high scalability

• Introducing the SIU

• Upgrade the microwave links to native Ethernet

Switch Site

• Preparation of the RNC/BSC sitesfor the IP connectivity

• Introduction of an overlay packet metro layer to prepare for capacitygrowth

Cores sites

• IP/MPLS

11 09/12/2009

Strategy To Evolve To IPRAN

• Single Interface to carry both GSM and WCDMA Traffic using the SIU• IP Over E1/ML-PPP supported by the same SIU for both the GSM and WCDMA Traffic• IP Over Ethernet supported by the same SIU for both the GSM and WCDMA Traffic

12 09/12/2009

Based on the existing TDM network & the new Ethernet Transport network

• In this Solution we will use the existing transport network, previously used for TDM, to transfer IP packets between RBS and BSC /RNC sites

•At the RBS site, The SIU will provide support of IP over E1, using ML-PPP. The use of IP over E1 will make all the E1 defined for the SIU a “ common resource” for the RBS-to-BSC/RNC path, which means that if some E1 go down, the remaining ones will carry the traffic with reduced bandwidth.

•At the BSC/RNC site a SmartEdge node has been included as a dedicated ML-PPP router that bridges from ML-PPP to Ethernet

13 09/12/2009

Using IP Over E1/ML-PPP with the Legacy TDM Network

•This solution will be used whenever Unitel will have an IP/Ethernet based transport equipment available such as ML-TN equipped with ETU or Ethernet capabilities (ex. AMM20P, NPU1C with MMU2D/H)

• In this case the GSM/WCDMA traffic transport can be done between the RBS and BSC/RNC using L2 or L3 backhaul •All the Iub traffic from a group of RBSs will be concentrated in a Gigabit Ethernet interface that will be delivered to the SE Router.

14 09/12/2009

Using IP Over Ethernet

The migration to All IP will be as follow

• BTS- Upgrade to BSS 07A or later (SW upgrade)

• SIU- Elect/Optical FE/GE WAN interface - Time distribution through E1 to BTSs- SEGw functionality

• BSC- Upgrade to BSS 07A or later (SW upgarde)- PGW board required for Abis over IP/ Optimization- Ethernet/IP functionality via BSC LAN Switch

For The 2G sitesFor The 2G sites

15 09/12/2009

• Redback RAN routers flexibility- Support L2/L3 VPN- Support ML-PPP - Support QoS for traffic prioritization - Scalable security filtering capabilities

• BSC Link redundancy (via BSC LAN SW)- VRRP- RSTP (SEOS 6.1.5)- BVI (RB/combined L2/L3_SEOS 6.1.4.3)

• Site interconnect- Core traffic - O&M traffic

• Increase scalability- Smaller broadcast domain by segregating traffic at layer 3- Standard security can be provided by implement ACL

16 09/12/2009

• Migrate to all IP site by site- Native IP in RBS - All sites not IP at the same time

• Hybrid Transport Node – Key MW technology- Native Ethernet and TDM Transport - Easy capacity upgrade

• Coexistence ATM/IP transport on RNC - Smooth introduction to IP

• Introduce an Ethernet carrier grade• Build high capacity packet overlay- Significant capacity boost- WDM for higher capacity and/or network separation

17 09/12/2009

For The 2G/ 3G Co-located sites

• BTS- Upgrade to BSS 08A or later (SW upgrade)

• Node-B- ET-MFX 11

• SIU- Elect/Optical FE/GE WAN interface - Transport Co-sharing for 2G & 3G traffic

• BSC- Upgrade to BSS 08A or later (SW upgarde)- PGW board required for Abis over IP/ Optimization- Ethernet/IP functionality via BSC LAN Switch

• RNC- ET- MFX 12

18 09/12/2009

Different Components Needed for the Migration

Hardware Equipments

19 09/12/2009

BSC/RNC site Physical Connectivity

• This physical connectivity is valid for both for L2 and L3 transport networks.

•Each ET-MFX board in the RNC is connected to one RAN switch with GE link (traffic is carried over these links)

•RNC O&M traffic is delivered directly from GPB boards to the site switch (MPBN towards the OSS)

•Each BSC LAN is connected to one site switch with one GE link

20 09/12/2009

Logical Connectivity

Logical connectivity

•Different VLANs are depicted in different colors

•Abis_BSC VLAN carries Abis over IP user/control traffic. One VLAN is defined for all BSCs in the site.

•Abis_Synch VLAN carries synchronization traffic between the STN and the Time Servers.

• Iub_Traffic_n VLAN carries Iub over IP user/control traffic and synchronization traffic to the ET-MFX boards.

One VLAN is defined for each RNC in the site

• Interconn VLAN is used for redundancy purposes

VLAN = Subnet

RSTP

X

21 09/12/2009

GSM/WCDMA Co-location using SIU with a Mini-Link TN

BSC/RNC Site

The first figure represent a co-location sites using the SIU for an IP over Ethernet solution

The second picture represent a co-location sites using the SIU for an IP over E1/ML-PPP

BSC/RNC SiteBSC/RNC Site

22 09/12/2009

Requirements on TN and IP RAN Design ConsiderationsGSM TDM to IP migration WCDMA IP-RAN

* RAN site Connectivity: (PGW, ET-MFX allocations…)

* Synchronization: When transport has asynchronous (Ethernet) media, a new synchronization methodologies needed to be implemented

* IP addressing with different VLANs: for both the GSM & WCDMA

* Quality of Services: Traffic classification, Diff Services (L3), P-bits_CoS (L2) mapping

* Security if needed

*** Note: When using a shared infrastructure for MPBN and IPRAN it’s essential to reach to an agreement in the packet classifications, marking and queuing applied on those common interfaces, so that the selected Qos solution fulfils the requirements for both solutions.

IP RAN Design Considerations

23 09/12/2009

Q&A

24 3/12/2009

Thank you