S01M01ed1_Introduction.pptx

UTRAN · LR15.W IP RAN DescriptionIP RAN Description · Introduction

1 · 1 · 1COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Module 1Introduction

Section 1IP RAN Description

UTRANLR15.W IP RAN DescriptionTMO18277_V5.0-SG Edition 1

TMO18277_V5.0-SG-LR15.W-Ed1 Module 1.1 Edition 1

Learning experience powered byAlcatel-Lucent University



Module objectives

Upon completion of this module, you should be able to:

Describe what is the scope of IP in UTRAN Explain the principle of IuboIP, IuCSoIP, IuPSoIP, and IuRoIP features Describe the hardware impacts



Table of Contents

1 Feature presentation 72 Hardware impact 20



Table of Contents [cont.]



1 Feature presentation




1.1 Introduction

In UA05, all the interfaces are carried over ATM: ATM backbone is used for the control plane and the user plane IP is used only for OAM




1.1 Introduction [cont.]

In UA06, the IP Evolution

Nodes B

Node B

Iub

Iub Iu-PS

Iu-CS

Iur

RNC

RNCCSCN

PSCN



SGSN

IP Network



The evolution is meant to completely replace the ATM transport network by an IP transport network:

It was the scope of the UA07.1 release

The UA07.1 release provides the possibility to use only the IP transport network on all the interfaces with the following features:

Native IP Iub Support RNC Support for IuCS over IP RNC Support for IuPS over IP RNC Support for IuR over IP Node B

RNC

MSC

SR





Since UA07, all the interfaces are carried over IP.

Nodes B

Node B

Iub

IubIu-PS

Iu-CS

Iur

RNC

RNC

CSCN

PSCN





In UA08, following features are added: Link Aggregation Group (LAG) Bidirectional Forwarding Detection SCTP Multi-homing in RNC Path Diversity Hybrid + Split Iub IP subnet reduction for PMC-RAB




1.2 Native IP Iub overview

FEATURE DESCRIPTION: Full IP transport on Iub: No ATM at all, no

pseudowire 3GPP Compliant Protocols: SCTP/IP in Cplane,

UDP/IP in Uplane Co-existence of ATM, Hybrid and IP Node Bs on

a given RNC IP and Ethernet QoS supported Node B synchronization: IEEE1588v2 (PTP)

FEATURE VALUE: OPEX reduction by using lower cost IP transport Seamless migration to IP IP Carrier Grade

DEPENDENCIES: 4ptGigE card in RNC xCCM in BTS optionally with GE MDA External IEEE1588v2 server (or alternative

synch method) Ethernet switch/IP router for layer 2 transport

architectures

IP/Ethernet

RNC

IEEE1588 server

SR

Node B



MSC MSCMSC


1.3 IuCS over IP overview

FEATURE DESCRIPTION:

3GPP Compliant Protocols Simultaneous support for ATM and IP stacks on Iu-CS

Homogeneous transport for UP and CP only (full IP or full ATM)

Iu-CS Flex (ATM and IP Iu-CS instances)

IP and Ethernet QoS support

FEATURE VALUE:

OPEX savings through use of cheaper IP transport

Seamless migration

IP Carrier Grade

DEPENDENCIES:

4ptGigE card in RNC

Ethernet Switch/IP Router for layer 2 transport architectures

IuCS Pool

SR

RNC

ATM transportIP transport

MGW

MGW

MGW

MGW

MGW

MGW



SGSN

GGSN

GGSN

GGSN

GGSN

GGSN

GGSN


1.4 IuPS over IP overview

FEATURE DESCRIPTION:

3GPP Compliant Protocols Simultaneous support for ATM and IP stacks on Iu-PS

Homogeneous transport for UP and CP only (full IP or full ATM)

Iu-PS Flex (ATM and IP Iu-CS instances)

IP and Ethernet QoS support

FEATURE VALUE:

OPEX savings through use of cheaper IP transport

Seamless migration

IP Carrier Grade

DEPENDENCIES:

4ptGigE card in RNC

Ethernet Switch/IP Router for layer 2 transport architectures

SGSN

IuCS Pool

SR

RNC

ATM transportIP transport

SGSN




1.5 Iur over IP overview

FEATURE DESCRIPTION: Full IP transport on Iur: no ATM at

all, no pseudowires 3GPP Compliant Protocols Simultaneous support for ATM and

IP Drift RNCs (that is Iur instances) Homogeneous transport for UP and

CP only (full IP or full ATM) IP and Ethernet QoS supported

FEATURE VALUE: OPEX reduction by using lower cost

IP transport Seamless migration to IP Carrier Grade IP

DEPENDENCIES: 4ptGigE card in RNC IP Drift RNCs Ethernet switch/IP router for layer 2

transport architectures

RNC

SR

SR

SRSR

IP / Ethernet

RNC RNC RNC




1.6 IP backbone

The IP backbone has to fulfill the following requirements: It is not necessarily fully dedicated to the UTRAN Ipv4 backbone DiffServ capable for the QoS management

AggregationNetwork

Backhauling

Note: The IP backbone is beyond the scope of this training.

RNC

Node B



RNC


1.7 RNC connection to the IP backbone

The RNC is connected to an IP backbone through a 7750 SR:

It is a layer 3 access router providing IP routing, DiffServ forwarding, and L3 Carrier Grade.

For redundancy purposes, this Service Router may be duplicated.

7750 SR

ATM Network

IP Network




1.8 Node B connection to the IP backbone

There are 3 ways to connect the Node B to the IP backbone:

An Ethernet Access Module (EAM) can be added in front of the Node B and an Ethernet Access Termination (EAT) in front of the RNC, to access an Ethernet backbone only (using ATM pseudowires for ATM transport). In the

Alcatel-Lucent global solution, EAM is a SAR7705 and EAT is a SR7750.

The xDSL access can also be used for IP/Ethernet.

An Ethernet access can be used in addition to the existing connection to the ATM backbone.



2 Hardware impact



2 Hardware impact

2.1 RNC hardware overview

New cards must be added to support the IP transport features.

The RNC must be equipped with 2 GigE 4 ports cards.

This card provides 4 GigaEthernet ports supporting the following interfaces:

1000BaseLX 1000BaseSX interfaces

The 4pGe card has an operating capability of full data line rate (1 Gbit/s) for each port. However, the aggregated backplane interface throughput for the four ports is 2.5 Gbit/s.



The 4pGigE cards route IP packets from the RNC cards to the Network Elements (Node B and SGSN). They provide:

Traffic management: QoS Mapping, Buffer Management, Queuing and Congestion Control, Scheduling, and DiffServ Capable

VLAN Support: To separate the traffic Defense Mechanisms with Protected Default Route (PDR) to spare

the Layer 3 routing

2 Hardware impact

2.2 RNC hardware structure

DCPS

IN

RNC

.

.

.

IP Network

SGSN

CP

RAB

4pGE

4pGENode B



2 Hardware impact

2.3 RNC hardware 4pGigE

The 4pGigE cards must go into slots 14 and 15: If not present in the RNC, any PSFP/DCPS cards in slots 14 and 15

must be replaced by the two 4pGigE cards.

This is illustrated in the following figure.

CARD CAGE 2

PS

07

PS

06

PS

05

PS

04

PS

03

PS

02

CP 0

1C

P 0

0

PS

13

PS

12

PS

11

PS

10

OC

3 0

9O

C3

08

CARD CAGE 1

PS

14

PS

15



2 Hardware impact

2.4 BTS GE MDA introduction in xCCM/xCCM-U

The xCCM board is in Node B

xCCM-U front panel

RJ-45 Fast Ethernet Port 2 will be used for Hybrid Iub IP connectivity:

Embedded 4 E1/T1 ports

Embedded 4 E1/T1 ports

MDA 4 E1/T1 ports orGigabit Ethernet

xCCM front panel

The xCCM-U board is included in the d2U unit with 2 xCEM-U

New MDA can be plugged on the xCCM mother board to have a Gigabit Ethernet interface for Iub

MDA 4 E1/T1 ports orGigabit Ethernet



IP Network

2 Hardware impact

2.5 IP backbone

The UTRAN IP backbone and the CN IP backbone are supposed to be a level 3 or level 2 network with IPv4 addressing, IP (or IP/MPLS) routing, and DiffServ forwarding.

It is supposed to be secure and transparent: IP packets shall be conveyed without any modification of the UDP/IP headers because IP addresses and UDP ports are used as bearer identifiers:

No NAT

Node B ATM Network

RNC



Module summary

In this module, we:

Described what is the scope of IP in UTRAN Explained the principle of IuboIP, IuCSoIP, IuPSoIP, and IuRoIP features Described the hardware impacts



IntroductionEnd of module

S01M01ed1_Introduction.pptx

Documents

w ip ran descriptionip

wed1 module

w ip ran descriptiontmo18277

copyright alcatellucent

ip ran description utranlr15

ip overview151

ip backbone181

ip overview141