configuring the iu interfaces.pdf

Configuring the Iu Interface

03/02/10 Alcatel Lucent © Sinéad O’Reilly

Configuring the Ericsson UTRAN

1. Initial Configuration

2. Site Basic Configuration

3. Site External Configuration

4. RNC Site Specific Configuration

5. RXI Site Specific Configuration

6. RBS Site Specific Configuration

7. Radio Network Configuration

Week 1

Week 2


Stage 4 – RNC Site-Specific

RNC RNC

RANAG

Iur

Iub Iub

Iub

RBSRBS

OSS-RC

Mub

Mur

Core Network

Iu

Iu

Configuration of the Iu

and Iur interfaces


Transport History for the Iu/Iur interface

Up to P5 – all traffic transmitted over ATM

P5 release – Iu/Iur CP and IuPS UP over ATM or IP

P6/6.1 release – Iur UP over ATM or IP

P7 release – IuCS UP over ATM or IP

From P7 onwards possible to have all interfaces over IP!


Iu Interface(s)

RNC

SGSN

MSC-S

MGW

IuCS UP

IuCS CP

IuPS UP/CP

All must be configured!

We focus on configuring from RNC side


IuCS Control Plane


IuCS CP Protocol Stacks (ATM/IP)

IP:ATM:

MTP3b

NNI-SAAL

RANAP

SCCP

AAL 5

ATM

Physical layer

M3UA

SCTP

RANAP

SCCP

IP

Ethernet

Physical layer


ATM/IP Lower Layers


Physical Layer (ATM), what are We Modelling?

We have to model the four physical STM-1 ports on the ET-MF4 SDH interface board

ET-MF4

Physical ports

The ET-MF4 has an MSP port, which will also be modelled


Physical layer Managed Objects The IuCS PHY layer is realised using SDH (STM-1) links. We model these links using the following MO Classes:

Equipment

Exchange Terminal

Os155SpiTtp

Vc4Ttp

“Equipment”, “Subrack”, “Slot”, “PlugInUnit” and “ExchangeTerminal” MOs should be in place already

These two new classes represent an STM-1 termination point on the board, and we must create one of each for each TP

4

1


How to alter/create/delete these MOs?The two MO classes can be found under the Equipment view in Element Manager. They are also found under the Equipment stack in the EM containment view (Object Explorer tool for old EMAS)


ATM Layer - What are We Modelling?

The logical ATM end-to-end connection

RNC

Core Network

Virtual Path connection termination point - VpcTp

Virtual channel - VclTp Virtual path - VplTp

ATM Port which maps to physical port - AtmPort


ATM Layer Managed ObjectsThe ATM layer requires ATM Ports, VCs, VPs and traffic descriptors for each. We need the following classes:

Transport Network

AtmPort

VplTp

The “TransportNetwork” MO will be in place already

Under it we must create these new MOs to represent the ATM layer. A VC or VP may use a Traffic descriptor MO that is already in place (as TDs can be used many times)

VpcTp

VclTp

AtmTraffic Descriptor

Note: The traffic

descriptor MO

class is not a

child of the VplTp

or VclTp classes,

rather there is an

association

between them


Management of ATM MOsThe two MO classes can be found under the ATM view in Element Manager. They are also found under the TransportNetwork stack in the EM containment view (Object Explorer tool for old EMAS)


AAL5 Layer - What are We Modelling?

We are modelling the mapping of the user data to the ATM cells. Remember AAL5 must terminate on a processor, the type of processor depends on the type of traffic!

MPG

P

B

S

P

B

SP

SP

SP

SP

SP

BP

Signalling – SS7 IuPS User Data

Slot 8/9 of the Main Subrack. MO Class is “PlugInUnit”

Slot 19-23 of the Main Subrack. MO Class is “spm”


AAL5 Layer Managed ObjectsThe AAL5 Layer requires an AAL5 Termination point. It is modelled using the following MO class:

Transport Network

Aal5TpVccTp

The “TransportNetwork” MO will be in place alreadyPlugInUnit

This MO represents an AAL5 TP and must be created

Spm

Spm should be the PDR special processor in the SPB – used with IuPS user plane traffic

PlugInUnit from the GPB in slot 8 or 9 –used with IuCS/PS/r control plane traffic


Management of AAL2/5 MOsAAL MOs can be found under the ATM view in Element Manager. They are also found under the TransportNetwork stack in the EM containment view (OE tool for old EMAS)


Physical Layer (IP), what are We Modelling?

ET-MFG

Physical Ethernet ports, one active one standby.

We have to model the gigabit Ethernet interfaces on the ET-MFG interface board


Physical layer Managed Objects

The IP-based IuCS PHY layer is realised using Ethernet links. We model these links using the following MO Classes:

Equipment

PlugInUnit

EtMfg

GigaBitEthernet

“Equipment”, “Subrack”, “Slot”, and “PlugInUnit” MOs

should be in place already

These two new classes represent ET-MFG functionality,

and an Ethernet termination point on the board.

1


Management of Ethernet MOsEthernet MOs can be found under the Equipment view in Element Manager. They are also found under the Equipment stack in the EM containment view (OE tool for older nodes)


IP Layer - What are We Modelling?

Up to 8 IP interfaces,

support traffic seperation at

each port

ET-MFG

IP Interface

ET-MFG

GPB

IP Interface

IP Access

Host GPB

IP @ 1

IP @ 2

For SS7 signalling IP host is located in slot 8/9 of the Main Subrack


IP interface Managed ObjectThe IP interface MO is added to the Gigabit Ethernet port

Equipment

GigaBitEthernet

“Equipment”, down to “GigaBitEthernet” MOs

should be in place already

IpInterfaceUp to 8 of these for VLAN

seperation

8


IP Host Managed ObjectsDifferent MO Classes for Signalling, NTP and user data hosts

ManagedElement

IpSystem

IpAccessHostGpb

IP hosts terminate the IP protocol: GPB: Signalling SPB: IuPS user data ETB: Iub/IuCS user data, NTP

IpAccessHostSpb

GeneralProcessorUnit

SpmIpInterface

IpAccessHostEt


Management of IP MOsEthernet MOs can be found under the IP view in Element Manager. They are also found under the IpSystem stack in the EM containment view (OE tool for old EMAS)


SCTP Layer - What are We Modelling?

Here we model the SCTP End point

GPB active

IP Access Host GPBSCTP

end point

Reliable Program Uniter allows for switching between end points in active and redundant GPBs, in slot 8 and 9 of the Main Subrack


Higher Layer Protocols


NNI-SAAL Layer Managed ObjectsFor the NNI-SAAL layer we need to create the NNI-SAAL termination points. These can be created from the signalling view in EM, or from the TransportNetwork Stack

Transport Network

NniSaalTp

The “TransportNetwork” MO will be in place already

Under it we can create NNI-SAAL TPs, link them to an NNI-SAAL

profile and map them to AAL5 TPs

NniSaalProfile Aal5VccTp


Mtp3b Layer - What are We Modelling?

1. Who am I? (what is my signalling point code?)

With Mtp3b we must ask three main questions:

2. What are the destinations?

3. What are the available routes to the destinations?


Mtp3b Layer

Viewing these parameters in a bit more detail:

347

My Signalling Point Code is

347

473

542

545

342

Signalling Link 2

Signalling Link 1SLS A

542 M3UA

SRS to… use

SR1

473 SLS A SR1

342 SLS B SR1

545 SLS A SR1

SLS B SR2


Mtp3b Layer Managed Objects

TransportNetwork

Mtp3bSpItu

Mtp3bApMtp3bSrsMtp3bSlsM3UAssociation

Sctp

Set the node signalling point code (SPC) here

Mtp3bSlItu

NniSaalTp

Mtp3bSr


Management of Mtp3b Layer MOsMtp3b Layer MOs can be found under the signalling view in Element Manager. They are also found under the TransportNetwork stack in the EM containment view (OE tool for old EMAS)


SCCP Layer Managed Objects

TransportNetwork

SccpSp

SccpScrc

SccpApRemoteSccpApLocal

Mtp3bAp


Management of SCCP Layer MOsSCCP Layer MOs can be found under the signalling view in Element Manager. They are also found under the TransportNetwork stack in the EM containment view (OE tool for old EMAS)


Top Level Configuration of IuCS CP


RANAP Layer Managed Objects

RncFunction

CnOperator

IuLink

SccpApRemote

Ranap

SccpApLocal

4

32


Management of RANAP MOsRANAP MOs can be found under the radio network view in Element Manager. They are also found under the RncFunction stack in the EM containment view (OE tool for old EMAS)


IuFlex

IuFlex allowed for the use of multiple Iu links to the Core Network. This introduced two potential functionalities:

1. Multi-Operator Core Network – allows for mulitple operators to connect from the core network to the node

2. MSC-in-pool – allows for the pooling of MSC-Servers with the (logical) connection of the Iu inteface to each. Should an MSC-S fail, other MSC-Servers may take over their load

Both of these services must be configured correctly in the RNC managed object model. We focus on MOCN here and view its effect


MOCN Example

CN1 Operator 1PLMN 272-32-2

MSCServer(NRI=5)

CN2 Operator 2PLMN 272-34-2

MSCServer(NRI=2)

IuFlex

Here two operators are connected to the same RNC


MOCN Example – MiB Extract

RncFunction=1

CnOperator = operator1

MCC=272

MNC=32


IuLink=CS

IuLink=CS

Ranap=CS

Ranap=CS

networkResource Identifier=5

SccpApRemote = Cn_Op1


SccpApLocal = Ranap_sig

MCC=272

MNC=34



IuCS User Plane


IuCS User Plane

RNC MGW

User plane over IP/ATM (AAL2)

Q-AAL2 signalling (if ATM used)

For ATM transport we use AAL 2 Adaption Layer, and need to use Q-AAL2 signalling to set up the AAL2 paths


IuCS UP Protocol Stacks (ATM/IP)

Using IP

UDP

IP

Ethernet

RTP

Using ATM

AAL 2

ATM

SDHATM

SDH

NNI-SAAL

Q-AAL2

MTP3b

AAL 5


Possible Scenario for Lower Layers

ETB Slot 6

VCI=36

VCI=36

GPB slot 9

AAL5

Termination

Point

cqb

GPB slot 8

AAL5

Termination

Point

cqa

VCI=40

VCI=40

VCI=41

VCI=41

AAL2 Path ca1

AAL2 Path ca2

AAL2 Path ca3

AAL2 Path ca4

RNC MGW

VCs for Q-AAL2

signalling


Example – MiB Extract for ATM

AtmPort= MS-6-1

VplTp=vp1

VpcTp=1

VclTp =vc36

AtmTrafficDescriptor = U3P4500M3000

AtmTrafficDescriptor = C1P33000

AtmTrafficDescriptor = C2P12000

VclTp =vc40

VclTp =vc41

AtmPort= MS-6-2

VplTp=vp1

VpcTp=1

VclTp =vc36

VclTp =vc40

VclTp =vc41


Example – MiB Extract for AAL Layer

Aal5TpVccTp=cqa

TransportNetwork=1

VclTp=vc36

PlugInUnit=1

Slot=8

Aal5TpVccTp=cqb

PlugInUnit=1

Slot=9

VclTp=vc36

Aal2PathVccTp=ca1supportedQosClasses=

CLASS_A_B

Aal2PathVccTp=ca3supportedQosClasses=

CLASS_A_B

VclTp=vc40

VclTp=vc41

VclTp=vc40

VclTp=vc41Aal2PathVccTp=ca2supportedQosClasses=

CLASS_A_B

Aal2PathVccTp=ca4supportedQosClasses

= CLASS_A_B

Aal2QosProfile=1


Possible Scenario for Higher Layers

GPB slot 9

AAL5Tp cqb

GPB slot 8

AAL5Tp cqa

NniSaalTp cqa

Mtp3bSl cqa

Mtp3bSls cq

Mtp3bSr cq

Mtp3bSrs cq

Destination Point Code = MGW Signaling Point Code

Mtp3bAp cq

service indicator =12

M3UA cq

NniSaalTp cqb

Mtp3bSl cqb

GPB slot 9GPB slot 8

SCTP sigtran

IP Host GPB

ATM-based System IP-based System

Service indicator for

Q-AAL2


Q-AAL2

Setting up the AAL2 paths between nodes

1345…

My AESA is 1345…

1200...

1000...

1210...

1300...

Path B

10 Path A

Number direction

12 Path B

13 Path C


Q-AAL2 Managed Objects

Transport Network

Aal2Sp

Aal2ApAal2QosCode PointProfile

Aal2RoutingCase

Mtp3bAp Aal2Path DistributionUnit

Aal2PathVccTp


Management of Q-AAL2 MOsQ-AAL2 MOs can be found under the ATM view in Element Manager. They are also found under the TransportNetwork stack in the EM containment view (OE tool for older nodes)


IuPS Interface


IuPS Protocol Stacks (ATM)

UP:CP:

MTP3b

NNI-SAAL

RANAP

SCCP

AAL 5

ATM

Physical layer

UDP

IP

User Plane

GTP-U

AAL 5

ATM

Physical layer


IuPS Protocol Stacks (IP)

UP:CP:

GTP-U

UDP

User Data

IP

Ethernet

Physical layer

M3UA

SCTP

RANAP

SCCP

IP

Ethernet

Physical layer


SGSN in Pool Example

SGSN 1(NRI=2)

SGSN 2(NRI=6)

IuFlex

Here the RNC is connected to two pooled SGSNs


SGSN in Pool – MiB Extract

RncFunction=1


MCC=272

MNC=32

IuLink=PS1

IuLink=PS2

Ranap=PS

Ranap=PS




SccpApLocal = Ranap_sig

networkResourceIdentifier=6


PDR Managed Objects

Equipment

SpDevicePool

PdrDevice Spm

IuLink PacketDataRouter Aal5TpVccTp


Management of PDR MOsPDR MOs can be found under the Equipment view in Element Manager. They are also found under the Eqipment stack in the EM containment view (OE tool for older nodes)


Scenario for PS User Plane

ETB Slot

6

SPM Slot 23

PDR Device

SPM Slot 19

PDR Device

VCI=64

VCI=64

VCI=68

VCI=68

AAL5 Tp pg1a

AAL5 TP pg1b

AAL5 TP pg5a

AAL5 Tp pg5b

RNCMGW 1

…

…

…

MGW 2

PDR pg1a

PDR pg1b

PDR pg5a

PDR pg5b


Chapter

Concludes

configuring the iu interfaces.pdf

Documents

em containment view

object explorer tool

iucs user plane

sctp end point

iups protocol stacks

rnc03 02 10 alcatel lucent

vcltp vc36

user data