Anda di halaman 1dari 25

IP RAN Network

Design 2G & 3G

CCIETalk session, May 12, 2013

Muhamad Yopan
CCIE#38903
Ericsson Indonesia
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 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
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
Adaptation of Class-of-Service to network conditions

• 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


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
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
Cases
2G Physical Topology

PE 1

ME

Microwave
OSS

Metro Ethernet MPLS

NTP/PTP Server

BSC Microwave ME PE 2

Microwave

2G
2G Logical Topology (Southbound)
BSC
Switch Side-A Static route

BSC_Inner

A)
OM VLAN
OM Vlan forward to OM vrf

6 l_
VLAN (777) (3405)

/2 rna
Static route (High priority)

65 te
Administrative Distance: 1 Abis Vlan forward to IuB vrf

x. n
x. (I
X . ner
n
IuB VRF

_I
C
BS ME Abis VLAN
(3305) OM VRF
SR_Abis
VLAN (765)
SR_Abis
VLAN (765)
OSS
A side Interconn Static route (Low priority)
Administrative Distance: 2 SR_Abis
VLAN PE 1
VLAN (765) OM VLAN
Board

Floating IP : x.x.x.67/26
192.168.2.1/30
VRRP IP:
MPLS
Board #0 : x.x.x.68/26 SR_Abis SR_Abis
Board #1 : x.x.x.69/26 VRRP IP:
Board #2 : x.x.x.70/26
VRRP IP:
Board #3 : x.x.x.71/26
192.168.2.2/30 Abis VLAN
VRRP IP:
PE 2
Static route (Low priority)
Administrative Distance: 2 NTP/PTP Server
SR_Abis IuB VRF
B Side VLAN (765)
Interconn
BS VLAN
SR_Abis
C VLAN (765)
_I Abis VLAN
n OM VRF
X. ne ME (3305)
x. r (
x. In SR_Abis
66 te
/2 rna VLAN (765)
6 l_
A)
Static route (High priority) OM VLAN
Administrative Distance: 1 (3405)

BSC_Inner Static route


VLAN (777) Switch Side-B

MetroE

Hub Site

2G
2G Logical Topology (Northbound)

BSC
Switch Side-A Static route

BSC_Inner
A)

OM VLAN
6 l_

VLAN (777) (3405)


/2 rna

Static route (High priority) ME


65 te

Administrative Distance: 1
x. n
x. (I
X. ner

Signaling
n

SS7 (100)
_I

vrf
C
BS

SS7 (100 Static route (Low priority)


SS7 (100) Administrative Distance: 2

A side Interconn Static route (Low priority)


Administrative Distance: 2
VLAN PE 1
Board

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

PE 2
Static route (Low priority)
Administrative Distance: 2 Signaling
Static route (Low priority)
B Side Administrative Distance: 2 vrf
Interconn
BS VLAN
C
_I
n
X. ne
x. r (
x. In
66 te SS7 (200)
/2 rna
6 l_ SS7 (200)
A) SS7 (200)
Static route (High priority)
Administrative Distance: 1

ME

BSC_Inner Static route


VLAN (777) Switch Side-B
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
Router border operator A Router border operator B
Interface
Destination Name Destination Name
x.x.x.244/32
x.x.x.245/32
SGSN B1
x.x.x.246/32
y.y.y.160/28
x.x.x.247/32
x.x.x.244/32
x.x.x.245/32
SGSN B2 RNC A1
x.x.x.246/32
x.x.x.247/32
Control Plane
x.x.x.244/32
y.y.y.176/28
x.x.x.245/32
IuPS SGSN B3
x.x.x.246/32
x.x.x.247/32
y.y.y.49/32
x.x.x.64/29
y.y.y.50/32
RNC B1 SGSN A1
y.y.y.53/32
x.x.x.72/29
y.y.y.54/32
x.x.x.248 /29 SGSN B1
x.x.x.248 /29 SGSN B2 y.y.y.128/26 RNC A1
User Plane
x.x.x.248 /29 SGSN B3
x.x.x.0/26 RNC B1 y.y.y.81 /32 SGSN A2
x.x.x.0/28 y.y.y.160/28
MSC B1 RNC A1
x.x.x.16/28 y.y.y.176/28
Control Plane
x.x.x.64/29
IuCS RNC B1 y.y.y.0/27 MSC A1
x.x.x.72/29
x.x.x.96/27 MGW B1 y.y.y.128/26 RNC A1
User Plane
x.x.x.192/27 RNC B1 y.y.y.0/25 MGW A1
y.y.y.160/28
RNC A1
y.y.y.176/28
x.x.x.64/29
y.y.y.0/28
RNC A2
y.y.y.16/28
Control Plane RNC B1
y.y.y.0/28
RNC A3
y.y.y.16/28
x.x.x.72/29
y.y.y.0/28
RNC A4
IuR y.y.y.16/28
x.x.x.64/29 y.y.y.160/28
Control Plane RNC B2 RNC A1
x.x.x.72/29 y.y.y.176/28
y.y.y.128/26 RNC A1
y.y.y.192/26 RNC A2
User Plane x.x.x.96/27 RNC B1
y.y.y.0/26 RNC A3
y.y.y.64/26 RNC A4
User Plane x.x.x.96/27 RNC B2 y.y.y.128/26 RNC A1