Iub Over IP - RevA

1Kista 10-11 Jun 2008 TIM A.Guerrieri - Iub over IP

Iub over IPIub over IP

TIM -

Telecom ItaliaAlessandro Guerrieri

RAN Transport WorkshopEricsson CME2G3G User Group

Kista, June 10-11 2008


AgendaAgenda

••

Iub in TIM Utran todayIub in TIM Utran today

••

Iub over IP in P6 GA: Iub over IP in P6 GA: Functional highlightsFunctional highlights

••

Architecture and Architecture and implementationimplementation

••

Lab tests (ongoing)Lab tests (ongoing)

••

ConclusionsConclusions


IubIub

in TIM Utranin TIM Utran

todaytoday


Reference architecture in Ericsson Area -

today

BTS

BTS

MGW

MSC

SGSN

RXIBTS

BTS

Iub, Mub

Iub, Mub

UTRAN Core Network

RNCIu

Iub

RXI

RNCIu

IurGbE

GTW-A

GTW-A

BTS

GTW-B

MGW

MSC

SGSN

BTS

BTSIub, Mub

GTW-A

GbE GTW-B

BTS

Iub

RXI

RNC

Iur

BTS

Iub

Iub

E1 Links

STM1 links (local)

Iu


Common ITU-T specifications used

Specified by 3GPP

ATM Adaptation

Layer

AAL2

AAL0

AAL5

Physical Layer

Physical Connection (E1/E3/STM1)

VP (Virtual Path)

ATM LayerVC (Virtual Channel)

Radio Network Layer

Transport Network Layer

ATM Transport according to 3GPP R99

UTRAN Protocol layers -

Iub over ATM

(concess. Ericsson)

Radio Application

Layer

WCDMA Radio

Application Channels



Specified by 3GPP

ATM Adaptation

Layer

AAL2

AAL0

AAL5

Physical Layer Physical Connection (Ethernet / Optical)

VP (Virtual Path)ATM Layer

VC (Virtual Channel)

Radio Network Layer



Radio Application

Layer

WCDMA Radio


IP Layer IP

UTRAN Protocol layers -

ATM over IP


Iub over a GbE backbone

GbE TI

RNCE1

E1

GTW-A

E1

E1

GTW-A

GTW-B

RNC

Link E1

Link STM-1 VC 12

Link STM-1 VC 4Ethernet

OSS

IPATM

ATMATM


Iub over GbE

•

Upgrade

of existing

UMTS sites

to

HSDPA and new Node

Bs

will

be

activated on the TI Gigabit

Ethernet

(GbE)

•

GbE

will

be

also

used

in inner

network segments

between

Media Gateways

and SGSN/MSC Servers

•

GbE

will

lead

to

gradual

phase

out of standalone

dedicated

ATM switches•

Convergent IP based infrastructure for the mobile and fixed networks

•

Multiplexing at IP-DSLAMs

with other Telecom Italia services: IPTV, ADSL, connectivity for business customers

•

Negligible additional delay (MPLS Tunnels of the UMTS VLAN within GbE require few packet processing)

•

Shorter E1 local loops and bandwidth saving for ATM virtual connections within the Gigabit Ethernet.

Migration of Iub onto GbE has started in Q1 2006.


Iub over GBE

RNC

GbE access Gateway(GTW A)

N* x E1

IMA or ATM

GbE backbone Gateway(GTW B)

ATM over IP (GbE)

Node B

ATM VPI=kVCI#1VCI#2

…VCI#n

STM-1 VC4 Link(Unchannelized)

* N typically equals 4 for HSDPA Node Bs


Iub (ATM) over GbE

NodeB

SOL SDH

nxE1 GBE

DWDM Infr. GBE

nxSTM1

SDH

3G

SDH

RNCfeeder

metro

8630 8840

ADM

ADM

Rete otticametropolitana OPM

Circuito ATM

VLAN per UMTS

PWE3 (Martini circuits)

GTW_AGTW_B

ModemSHDSL

ModemSHDSL

Centrale di attestazion

e

SOL rame

metro

STM1CWDM CWDM


Iub over IPIub over IPin P6 GA:in P6 GA:

FunctionalFunctionalhighlightshighlights



Specified by 3GPP

ATM Adaptation

Layer

AAL2

AAL0

AAL5

Physical Layer

Physical Connection (E1/E3/STM1)

VP (Virtual Path)

ATM LayerVC (Virtual Channel)

Radio Network Layer



UTRAN Iub over ATM

Radio Application

Layer

WCDMA Radio


(by. Ericsson)



Specified by 3GPP

Physical Layer

Physical Connection (Ethernet / Optical)

Radio Network Layer



Radio Application

Layer

WCDMA Radio


IPTransport Layer

UTRAN Iub over IP


Iub new Protocol Stack (with IP)

Node B Application Part

(NBAP)

AAL2

TransportLayer

Physical Layer

Radio NetworkLayer

Radio NetworkControl Plane

Transport Network

Control Plane

DC

H FP

RA

CH

FP

ATM

AAL5

User Plane

SSCF-UNI

SSCOP

AAL 5

SSCF-UNI

SSCOP

Q.2630.2

Q.2150.2

FAC

H FP

PCH

FP

Data Link Layer

IP

SCTP

ATM ATM Data Link Layer

IP

UDP

ALCAP

HS-D

SCH

FP

TDD

DSC

H FP

USC

H FP

TFCI2 FP

E-DC

H FP


Iub over IP Protocol Stack

DCH, HS-DSCH, E-DCH FACH, PCH, RACH FPsNBAP

TransportNetworkLayer

RadioNetworkLayer

Radio Network Control Plane

Network Synch Radio Network User Plane

NW SoIP

Ethernet

and Node Sync (over FACH)

IPUDPSCTP (*)

NTP

(*) SCTP (Stream Control Transmission Protocol)(by. Ericsson)


P6 Iub over IP/Ethernet

(by. Ericsson)


Node B side: ET-MFX11 board• Ethernet Board: Auto negotiation for 10/100/1000 Mbps selection• Connectors:

-

1 SFP 1000 Base-X (SMF, MMF) optical port-

6 RJ45 10/100/1000Base-T electrical ports• Integrated Ethernet Switch -

8 IP Interfaces• VLAN 802.1Q, • L2 Ethernet priority 802.1p,• L3 IP Diffserv

priority (DSCP)• Network Synch Client for IP Transport, Iub and O&M• Capacity: 100 Mbps (Iub+Mub

IP overheads included)•

In P6 GA only RBS in HW R3. In P6 FP RBS in HW R2/R1 (TUB2 and

GPB51 needed)•

In RBS the ET-MFX11 board replace the ET-MC1 board (no Dual Stack in

RBS)

•

Layer 2 Link Redundancy: RSTP (Rapid Spanning Tree Protocol, 802.1D-

2004).•

Layer 3 Redundancy: for supervision of the default routers, the

ET-MFX12 board use of Router Path Supervision (RPS). An alternative to the built-in support for router redundancy it is to use other external mechanisms for router redundancy such as VRRP (or HSRP).

ETHERNET1/SFP

Ethernet D

Ethernet C

Ethernet B

Ethernet A

F

O

I

Ethernet E

Ethernet F


RNC side: ET-MFX12 board

• Ethernet Board: Auto negotiation for 10/100/1000 Mbps selection• Connectors:

-

1 SFP 1000 Base-X (SMF, MMF) optical port-

6 RJ45 10/100/1000Base-T electrical ports• Integrated Ethernet Switch –

8 IP Interfaces• VLAN 802.1Q, • L2 Ethernet priority 802.1p, • L3 IP Diffserv

priority (DSCP)• Network Synch Server for IP• Capacity: 500 Mbps (Iub IP overheads included)•

ET-MFX 12 can be placed in any subrack (MS and/or ES) and RXI in any

ETB slot (in addition or replacing existing ET Boards –

Dual Stack in RNC).

•

Layer 2 Link Redundancy: RSTP (Rapid Spanning Tree Protocol, 802.1D-

2004).•

Layer 3 Redundancy: for supervision of the default routers, the

ET-

MFX12 board use of Router Path Supervision (RPS). An alternative

to the built-in support for router redundancy it is to use other external mechanisms for router redundancy such as VRRP (or HSRP).

ETHERNET1/SFP

Ethernet D

Ethernet C

Ethernet B

Ethernet A

F

O

I

Ethernet E

Ethernet F


Definitions: IP Host and MultiHoming

GPB Host = Ip

Host in the GPB board -

Used for Control PlaneSPB Host = Ip

Host in the SPB board -

Used for User PlaneET Host = Ip

Host in the ET-MFX board

IP Host = "any terminal equipment connected to an IP nework (hosting an application)".3 IP Host types available in Ericsson Utran:

MultiHomingAn IP Host is characterized by one (Single-

Homed Host) or more IP addresses (Multi-

Homed Host). Multihoming

is supported on GPB and SPB hosts, allowing two IP addresses to be defined per IP Host: these IP addresses can be generally used simultaneously or one at a time, and are controlled by the application software

ApplicationHost

Board

IP address 1

IP path 1

IP path 2

IP address 2

by Ericsson


Definitions: Movable Host and IP Interface

IP Interface = One IP Physical Port + One VLAN (subnet)

• It is not possible to have an IP Interface associated to:-

more than one physical IP Port (and more than one ET-Board)-

more than one VLAN

• It is possible to have: -

an IP Interface associated to more than one IP Host-

more than one IP interface associated to the same IP port-

more than one IP interface associated to the same VLAN

•

Max 8 IP Interfaces are available in the ET-MFX board. (= max 8 VLAN in a ET-

MFX board)

ApplicationHost

Board

ApplicationHost

BoardET-IP

ET-IP GPB 1

GPB 2by Ericsson

Movable Host (only supported by GPB Hosts)Movable host makes it possible to move the IP host between boards. If the application software is moved from one board to another, the application determines which board the host executes on and the host is automatically reconfigured on the new board.


ET-MFX Architecture

ETHERNET1/SFP

Ethernet D

Ethernet C

Ethernet B

Ethernet A

F

O

I

Ethernet E

Ethernet F

InternalEthernetSwitchExternal

Eth ports InternalEth port

SystemPort

TransportNetwork

Each ET-MFX board is configured with one IP-Interface:-

One Vlan, One Physical Port

ET-MFX

IPInterface


ET-MFX, Typical RNC Architecture

GPBHost

Appli-cation

ETMFX12

ETMFX12

GPBHost

Appli-cation

SPB Host (pool)

Mul

tiHom

edM

ovea

ble

SC

TP H

ost

Router Path

Supervision

RNC

Mul

tiHom

edH

ost


ET-MFX, Typical RNC Architecture

MS

ES1

ES2

(by. Ericsson)


RNC IP Addressing

Control PlaneOne address for each Module GPB / ET-MFX12 association. One RNC Module "sees" two ET-MFX12.

User PlaneOne address for each ET-MFX12 (SPB Host is a Pool)

RPS – Def GTWRPS: one address for each ET-MFX12Default Gateways: two addresses (one address for each Router)

Example for an RNC Type C-

15 GPB Modules in P6, 6 ET-MFX12 boards, ONE Vlan

/ Subnet

-

Control Plane: 30 IP addresses needed for Control Plane-

User Plane: 6 IP addresses needed for UP

-

RPS: 6 IP addresses needed for RPS, 2 IP for 2 Default Gateways

All IP addresses above share the same subnet


ET-MFX, Typical RBS Architecture

InternalEthernetSwitchExternal

Eth ports InternalEth port

SystemPort

TransportNetwork ET-MFX

CBUFEPort

O&MTraffic

SiteLAN

2 VLANs:Vlan "A": IubVlan "B": Mub

JumperCable


RBS IP Addressing

SUBNET / VLAN "A" for Iub (User and Control Plane)-

1 IP address reserved for Control Plane

-

1 IP address reserved for User Plane / Synch Host-

1 IP address optionally reserved for RPS (currently not used)

SUBNET / VLAN "B" for Mub-

1 IP address needed for O&M

-

Additional IP addresses may be needed for Site LAN devices


Layer 2 restriction

"E/// recommendations for Layer 2 Networks�To reduce the risk of performance reduction in a WCDMA RAN node due to flooding of traffic, any layer 2 network aggregated in an

RNC or

RBS node shall be limited.�Due to this Ericsson recommend:–

That a layer 3 node shall be placed between the RNC and any layer 2

access network–

That the IP RBS is a leaf RBS and only aggregate SiteLAN

connected

equipment."

February 2008


Network Synchronization over IP

•

Client -

Server synchronization architecture. A Network Synch Server is in RNC and a client in RBS. Two optional features: FAJ 121 1154 "Network Synch server for IP transport" for RNC or RXI, FAJ 121 1155 "Network Synch client for IP transport" for RBS.

•

Synch -

Server connection is based on SNTP Protocol (Simpliflied Network Time Protocol).

•

No other synchronization functionalities required (external devices, Synch nodes, GPS etc.)

•

Requirement for network synchronization: delay variation < 0.1 ms for 1% SNTP Packets.

(by Ericsson)


Transport Requirements for Iub over IP

•

Service requirements: no additional requirement for the backhauling IP network compared to the "ATM over GbE" solution.

• Network Synchronization requirement:delay variation < 0.1 ms for 1% SNTP Packets.


QoS for Iub over IP

•

QoS

separation is supported at IP level, using DSCP (Differentiated Services Code Points). [0...63].

•

QoS

separation is supported at Ethernet level by using the Priority

Bits (L2 Ethernet priority 802.1p). P-bit [0..7]

• The selection of QoS

class of the bearers is operator configurable.

Bearer X

Bearer Y

Bearer Z

DSCPX

DSCPY

DSCPZ

P-BitX

P-BitY

P-BitZ


(by Ericsson)

Configurable transport bearer QoS

class –

Iub default values


(by Ericsson)

QoS

classes: mapping of DSCP over P-Bit -

default values

Default mapping of Layer 3 DSCPOver Layer 2 Ethernet P-bits

This mapping table is configurable by operator at Internal Ethernet Port level. The settings are visible in the dscpPbitMap attribute on InternalEthernetPort

MO.

This means all the IP interfaces associated to the relevant Internal Ethernet Port will use the same DSCP to P-bit mapping


Architecture,Architecture,

implementationimplementation

andand

first testsfirst tests


OPM

RNCEth

Eth

Eth

Eth

RNC

Link E1

Link STM-1 VC 12

Link STM-1 VC 4Ethernet

OSS

IP IPIP

Eth

Eth

Iub over IP


RNC

GE

GE

10GE

10GEGE

METRO

NodeBFEEDER

10GE 10GE

Sede SGU

RemoteFeeder

RETE OTTICA DWDM o

fibra nuda10GE

10GE

10GE

10GE

METROdi raccoltaGE

Sede SL

Sede SGURemote

Feeder

GE

10GE

Anello fibra ottica in primaria

NodeB

GE 1:2

1:2ONT OLT

NodeB

GE

VDSL2+

Modem

ONU

2:16

Fibra nuda

Sede SL


Iub over IP –

Architecture 1 (FTTB)


Iub over IP –

Architecture 2 (FTTCab)

RNC

GE

GE

10GE

10GEGE

METROFEEDER

10GE10GE

Sede SGU

RemoteFeeder

RETE OTTICA

DWDM o fibra nuda

10GE

10GE

10GE

10GE

METROdi raccolta

Sede SLSede SGU

RemoteFeeder

GE


NodeB

NT VDSL2

copperVDSL2

NodeB

NT VDSL2

Eth

Eth

copper

VDSL2

Cabinet con ONU VDSL2


OPMOpticalPackedMetro

MS

Eth

Eth

Eth

Iub over IP (2)

ES1

ES2

DCN(OSS)

RdG

MdR

MdR

RemoteFeeder

RemoteFeeder

RPS HSRP

HSRP

RSTP


QoS

Mapping

3 QoS Priority Levels• Maximum: Network Synchronization and Conversational/Streaming traffic• Medium: PS R99 DCHs and NBAP signaling• Best effort: HSDPA/HSUPA

Layer 3:DSCP

Layer 2:P-bit

High Priority46

Sync

18

CS & Stream5

Sync, CS, Stream

Medium Priority 22PS R99, NBAP

3PS R99, NBAP

Best Effort 0HSxPA

0HSxPA

Our Optical Packed Metro is a Layer 2 network working with 3 P-bit values (5, 3, 0), so we had to adapt the mapping of DSCP to P-bit to the existing situation.


QoS

Mapping (2)

Layer 3:DSCP

Layer 2:P-bit

46

Sync18

CS & Stream

5Sync, CS,

Stream

22PS R99, NBAP

3PS R99, NBAP

0HSxPA

0HSxPA

(by Ericsson)


Iub –

RNC IPs

and Subnet

In order to reserve the right amount of IP adresses, the worst case ("future proof" approach) is adopted i.e. RNC type F:-

up to 6 Subracks

-

up to 3+6+6+6+6+6 = 33 RNC Modules-

up to 16 ET-MFX12 boards (maximum value for the RNC)

• User Plane: 16 IP addresses (16 ET-MFX boards)• Control Plane: 66 IP addresses (2 * 33 RNC Modules)• Routing Path Supervision: 16 IP addresses (12 ET-MFX boards)• Default Gateways: 2 IP addresses (2 Default Gateways)• Subnet and Broadcast: 2 IP addresses• OPM: 4 IP addresses

Total: 102 IP addressesClosest Subnet Size: 128 (subnet /25)


Iub –

RBS IPs

and SubnetIub Subnet/Vlan:• User Plane: 1 IP address • Control Plane: 1 IP address• Default Gateways: 2 IP addresses (2 Default Gateways)• Subnet and Broadcast: 2 IP addresses

Total: 2*N + 4 IP addresses (N = n. of RBSs)Maximum value (768 Node Bs) = 1540 IP Adresses (more than /22 subnet, not advisable)Subnet Size adopted: /22 (1024 Ips) = up to 500 Node BsA second /22 subnet will be adopted in case of more than 500 Node Bs.

Mub Subnet/Vlan:• Mub: 1 IP address • Default Gateway: 1 IP addresses (only 1 Default Gateway + HSRP)• Subnet and Broadcast: 2 IP addresses.• Site Lan (at RNC level): 16 IP addresses.• RdG configuration: 8 IP addresses

Subnet Size adopted: /22 (1024 Ips) = up to 500 Node BsA second /22 Subnet will be adopted in case of more than 500 Node Bs.


Overall data definition –

RNC Level

RNC Level

• VlanID_RNC_side• Subnet_RNC_side

• Def_GTW1 (1 IP)• Def_GTW2 (1 IP)• IP_Iub_CP (66 IP) = X.Y.W.1-66• IP_Iub_UP (16 IP) = X.Y.(W+1).1-16• 16 IP per RPS = X.Y.(W+2).1-16 • 4 IP per OPM = X.Y.(W+3).251-254

• Mub_OeM_on_Site

(16 IP)

• TD (pointer to the 2 Optical Fiber delivery contract)


Overall data definition –

RBS Level

Node B Level

• RBS_nr• TD (pointer to the OF delivery contract)• IP_Iub_UP

(1 IP)

• IP_Iub_CP

(1 IP) • Def_GTW1 (1 IP)• Def_GTW2 (1 IP)• VlanID_lato_NB• Subnet_lato_NB• Optional VlanID_NB_side_over500• Optional Subnet_NB_side_over500

• Mub

(1 IP)• Mub_Def_GTW

(1 IP)

• Mub_VlanID• Mub_Subnet• Optional_Mub_VlanID_over500• Optional_Mub_Subnet_over500


Configuration Tool Development

Project DataTransport Radio O&M CN

ToolASCOT

Scripts(via EMAS)

RXIRNC BTS

ToolIRMA

xml(RANOS)

Router configuration

and connection with RANOS

Data load(pseudo manual)

MSC

SGSN

BTS

Installationactivities

Minimumpreconfig.

on site

UTR


Lab testsLab tests(ongoing)(ongoing)


Tests and Field Trial

Jan-Mar Apr May Jun Jul Aug-Dec

Project definition

On site activities (HW, Swap)

Lab Test

Field Test ph1

Field Test ph2

today

-

Fiber to the RNC-

HW Swap in RNC-

Fiber to the Node B (FTTB)-

Node B Swap HW R2-> R3-

HW Swap R2->R3Final part of P6 Lab test

First 2 RBS in Milan:

Field Test ph3

9 RBS in Milan (in HW R3)

More RBSs in HW R2 (P6 FP needed)

Iub over IP over ADSL2+ could be testedin the 2H 2008


First Lab Test Results

Throughput test: HSDPA 16-QAM 10 codes: 5.8 -

6.0 Mbps reached

ok

Only 1 week of test activities today

Configuration issues: -

2 days for parameter reconfiguration after P6.0.0 EU6 load ok

-

HSRP problems in the backhauling network (OPM) ok-

NTP configuration (2 server configurable in Node B) ok

-

NTP link in the uplink path (RBS -> RNC) ongoing

Very good interwork and coordination between Utran and backhauling experts are needed in order to deal with configuration problems


ConclusionsConclusions


Evolutions

Iub over IP over ADSL2+ / VDSL (FTTCab)

Iub over IP and ATM (Dual Stack in RBS, P6 FP)

(by Ericsson)

(by Ericsson)


Conclusions

• Iub over IP is THE solution for:─

the transport bottlenecks removal

─

the evolution of the network towards new services (HSPA Evolution, in Utran P7, and LTE)

•

Iub over IP is not an immediate solution for the whole network due to the slow availability of the optical fiber (FTTB solution).Iub over IP over VDSL can be adopted in case of FTTCab.

•

Under evaluation the P6 FP RBS Dual Stack option, to be used with ADSL2+ / VDSL


Acknowledgements:

Michele Marone, Paolo Parodi, Patrizio Pasqualetti, Barbara Pippi

(Ericsson Italy, Utran IP experts)

Elena Spreafico (TIM, Utran Transport expert)

Topazzi Simone & C. (TIM, Test Plant)


Thanks for Your Attention

Alessandro Guerrieri

TIM Telecom Italia Wireless Access Engineering [email protected]

Iub Over IP - RevA

Documents

Transcript of Iub Over IP - RevA