Configuring the Iu Interface

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 Week 2 6. RBS Site Specific Configuration 7. Radio Network Configuration
03/02/10 Alcatel Lucent Sinad OReilly

Week 1

Stage 4 RNC Site-Specific

Configuration of the Iu and Iur interfaces
Core Network
Iu Iu

Iub RANAG

Iur Mur RNC RNC OSS-RC Iub Mub

Iub

RBS

RBS

03/02/10

Alcatel Lucent

Sinad OReilly

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!

03/02/10

Alcatel Lucent

Sinad OReilly

Iu Interface(s)
We focus on configuring from RNC side

IuCS CP IuCS UP IuPS UP/CP

MSC-S

RNC

MGW SGSN

All must be configured!

03/02/10 Alcatel Lucent Sinad OReilly

IuCS Control Plane

03/02/10

Alcatel Lucent

Sinad OReilly

IuCS CP Protocol Stacks (ATM/IP)

ATM:
RANAP SCCP MTP3b NNI-SAAL AAL 5 ATM Physical layer
03/02/10 Alcatel Lucent

IP:

RANAP SCCP M3UA SCTP IP Ethernet Physical layer

Sinad OReilly

ATM/IP Lower Layers

03/02/10

Alcatel Lucent

Sinad OReilly

Physical Layer (ATM), what are We Modelling?

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

Physical ports

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

03/02/10

Alcatel Lucent

Sinad OReilly

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
4

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

Os155SpiTtp
1

Vc4Ttp
03/02/10

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

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)

03/02/10

Alcatel Lucent

Sinad OReilly

ATM Layer - What are We Modelling?

The logical ATM end-to-end connection
Virtual channel - VclTp Virtual path - VplTp

Core Network

RNC ATM Port which maps to physical port - AtmPort

03/02/10

Virtual Path connection termination point - VpcTp

Alcatel Lucent

Sinad OReilly

ATM Layer Managed Objects

The ATM layer requires ATM Ports, VCs, VPs and traffic descriptors for each. We need the following classes:
Note: The traffic descriptor MO class is not a child of the VplTp or VclTp classes, rather there is an association between them

Transport Network

The TransportNetwork MO will be in place already

AtmPort

VplTp

AtmTraffic Descriptor

VpcTp

VclTp

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)

03/02/10

Alcatel Lucent

Sinad OReilly

Management of ATM MOs

The 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)

03/02/10

Alcatel Lucent

Sinad OReilly

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!
Signalling SS7 IuPS User Data

SP SP

G P B

MP

SP

S SP SP P B BP

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

03/02/10

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

Alcatel Lucent Sinad OReilly

AAL5 Layer Managed Objects

The AAL5 Layer requires an AAL5 Termination point. It is modelled using the following MO class:
PlugInUnit from the GPB in slot 8 or 9 used with IuCS/PS/r control plane traffic Transport Network PlugInUnit Aal5TpVccTp Spm Spm should be the PDR special processor in the SPB used with IuPS user plane traffic

The TransportNetwork MO will be in place already This MO represents an AAL5 TP and must be created

03/02/10

Alcatel Lucent

Sinad OReilly

Management of AAL2/5 MOs

AAL 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)

03/02/10

Alcatel Lucent

Sinad OReilly

Physical Layer (IP), what are We Modelling?

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

Physical Ethernet ports, one active one standby.

ET-MFG

03/02/10

Alcatel Lucent

Sinad OReilly

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

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

PlugInUnit
1

EtMfg

GigaBitEthernet

These two new classes represent ET-MFG functionality, and an Ethernet termination point on the board.

03/02/10

Alcatel Lucent

Sinad OReilly

Management of Ethernet MOs

Ethernet 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)

03/02/10

Alcatel Lucent

Sinad OReilly

IP Layer - What are We Modelling?

GPB ET-MFG IP Interface IP @ 1 IP Access Host GPB IP @ 2 ET-MFG IP Interface

Up to 8 IP interfaces, support traffic seperation at each port

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

03/02/10

Alcatel Lucent

Sinad OReilly

IP interface Managed Object

The IP interface MO is added to the Gigabit Ethernet port

Equipment

GigaBitEthernet
8

Equipment, down to GigaBitEthernet MOs should be in place already

IpInterface

Up to 8 of these for VLAN seperation

03/02/10

Alcatel Lucent

Sinad OReilly

IP Host Managed Objects

Different MO Classes for Signalling, NTP and user data hosts
Managed Element IP hosts terminate the IP protocol: GPB: Signalling SPB: IuPS user data ETB: Iub/IuCS user data, NTP

IpSystem

IpAccessHostGpb

IpAccessHostEt

IpAccessHostSpb

GeneralProcessor Unit

IpInterface

Spm

03/02/10

Alcatel Lucent

Sinad OReilly

Management of IP MOs
Ethernet 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)

03/02/10

Alcatel Lucent

Sinad OReilly

SCTP Layer - What are We Modelling?

Here we model the SCTP End point

GPB active

SCTP end point

IP Access Host GPB

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

Alcatel Lucent

Sinad OReilly

Higher Layer Protocols

03/02/10

Alcatel Lucent

Sinad OReilly

NNI-SAAL Layer Managed Objects

For 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

The TransportNetwork MO will be in place already

NniSaalProfile

NniSaalTp

Aal5VccTp

Under it we can create NNI-SAAL TPs, link them to an NNI-SAAL profile and map them to AAL5 TPs
03/02/10 Alcatel Lucent Sinad OReilly

Mtp3b Layer - What are We Modelling?

With Mtp3b we must ask three main questions:
1. Who am I? (what is my signalling point code?)

2. What are the destinations?

3. What are the available routes to the destinations?

03/02/10

Alcatel Lucent

Sinad OReilly

Mtp3b Layer
Viewing these parameters in a bit more detail:

542

SRS to SR1 542 SR1 473 SR1 342 SR1 545 SR2

use M3UA SLS A SLS B SLS A SLS B

Signalling Link 1

347
My Signalling Point Code is 347

SLS A
Signalling Link 2

473

545

342

03/02/10

Alcatel Lucent

Sinad OReilly

Mtp3b Layer Managed Objects

TransportNetwork Set the node signalling point code (SPC) here

Mtp3bSpItu

M3UAssociation

Mtp3bSls

Mtp3bSrs

Mtp3bAp

Sctp

Mtp3bSlItu

Mtp3bSr

NniSaalTp

03/02/10

Alcatel Lucent

Sinad OReilly

Management of Mtp3b Layer MOs

Mtp3b 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)

03/02/10

Alcatel Lucent

Sinad OReilly

SCCP Layer Managed Objects

TransportNetwork

SccpSp

SccpScrc

SccpApLocal

SccpApRemote

Mtp3bAp
03/02/10 Alcatel Lucent Sinad OReilly

Management of SCCP Layer MOs

SCCP 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)

03/02/10

Alcatel Lucent

Sinad OReilly

Top Level Configuration of IuCS CP

03/02/10

Alcatel Lucent

Sinad OReilly

RANAP Layer Managed Objects

RncFunction
4

CnOperator
32

IuLink

Ranap

SccpApLocal
03/02/10 Alcatel Lucent

SccpApRemote
Sinad OReilly

Management of RANAP MOs

RANAP 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)

03/02/10

Alcatel Lucent

Sinad OReilly

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

03/02/10

Alcatel Lucent

Sinad OReilly

MOCN Example
Here two operators are connected to the same RNC
MSC Server (NRI=5)

CN1 Operator 1 PLMN 272-32-2

IuFlex

MSC Server (NRI=2)

CN2 Operator 2 PLMN 272-34-2

03/02/10

Alcatel Lucent

Sinad OReilly

MOCN Example MiB Extract

RncFunction=1

CnOperator = operator1
MCC=272 MNC=32

Ranap=CS IuLink=CS
networkResource Identifier=5

SccpApRemote = Cn_Op1

SccpApLocal = Ranap_sig

CnOperator = operator2
MCC=272 MNC=34

IuLink=CS

Ranap=CS
networkResource Identifier=2

SccpApRemote = Cn_Op2

03/02/10

Alcatel Lucent

Sinad OReilly

IuCS User Plane

03/02/10

Alcatel Lucent

Sinad OReilly

IuCS User Plane

User plane over IP/ATM (AAL2)

Q-AAL2 signalling (if ATM used)

RNC

MGW

For ATM transport we use AAL 2 Adaption Layer, and need to use Q-AAL2 signalling to set up the AAL2 paths
03/02/10 Alcatel Lucent Sinad OReilly

IuCS UP Protocol Stacks (ATM/IP)

Using ATM Q-AAL2 MTP3b AAL 2 ATM SDH NNI-SAAL AAL 5 ATM SDH Using IP RTP UDP IP Ethernet

03/02/10

Alcatel Lucent

Sinad OReilly

Possible Scenario for Lower Layers

GPB slot 8 AAL5 Termination Point cqa ETB Slot 6 VCI=36 AAL2 Path ca1 AAL2 Path ca2 VCI=40 VCI=41

GPB slot 9 AAL5 Termination Point cqb VCI=36 AAL2 Path ca3 AAL2 Path ca4 VCI=40 VCI=41

VCs for Q-AAL2 signalling

RNC
03/02/10 Alcatel Lucent

MGW
Sinad OReilly

Example MiB Extract for ATM

AtmPort= MS-6-1 VplTp=vp1 AtmTrafficDescriptor = C1P33000 AtmPort= MS-6-2 VplTp=vp1

VpcTp=1 VclTp =vc36 VclTp =vc40 VclTp =vc41

AtmTrafficDescriptor = U3P4500M3000

VpcTp=1 VclTp =vc36

AtmTrafficDescriptor = C2P12000

VclTp =vc40 VclTp =vc41

03/02/10

Alcatel Lucent

Sinad OReilly

Example MiB Extract for AAL Layer

Slot=8 TransportNetwork=1 PlugInUnit=1 PlugInUnit=1 Slot=9

VclTp=vc36

Aal5TpVccTp=cqa

Aal5TpVccTp=cqb

VclTp=vc36

Aal2PathVccTp=ca1 VclTp=vc40
supportedQosClasses= CLASS_A_B

Aal2PathVccTp=ca3
supportedQosClasses= CLASS_A_B

VclTp=vc40

Aal2PathVccTp=ca2 VclTp=vc41
supportedQosClasses= CLASS_A_B

Aal2PathVccTp=ca4
supportedQosClasses = CLASS_A_B

VclTp=vc41

Aal2QosProfile=1
03/02/10 Alcatel Lucent Sinad OReilly

Possible Scenario for Higher Layers

Mtp3bAp cq service indicator =12 Mtp3bSrs cq Destination Point Code = MGW Signaling Point Code Mtp3bSr cq Mtp3bSls cq Mtp3bSl cqa NniSaalTp cqa AAL5Tp cqa GPB slot 8 Mtp3bSl cqb NniSaalTp cqb AAL5Tp cqb GPB slot 9 M3UA cq

Service indicator for Q-AAL2

SCTP sigtran IP Host GPB GPB slot 8 GPB slot 9

ATM-based System
03/02/10 Alcatel Lucent

IP-based System
Sinad OReilly

Q-AAL2
Setting up the AAL2 paths between nodes

Number direction 10 12 Path A Path B Path C

1000...

13

1345
My AESA is 1345

Path B

1200...

1210...

1300...

03/02/10

Alcatel Lucent

Sinad OReilly

Q-AAL2 Managed Objects

Transport Network

Aal2Sp

Aal2QosCode PointProfile

Aal2Ap

Aal2RoutingCase

Mtp3bAp

Aal2Path DistributionUnit

Aal2PathVccTp

03/02/10

Alcatel Lucent

Sinad OReilly

Management of Q-AAL2 MOs

Q-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)

03/02/10

Alcatel Lucent

Sinad OReilly

IuPS Interface

03/02/10

Alcatel Lucent

Sinad OReilly

IuPS Protocol Stacks (ATM)

CP:
RANAP SCCP MTP3b NNI-SAAL AAL 5 ATM Physical layer
03/02/10 Alcatel Lucent

UP:

User Plane GTP-U UDP IP AAL 5 ATM Physical layer

Sinad OReilly

IuPS Protocol Stacks (IP)

CP:
RANAP SCCP M3UA SCTP IP Ethernet Physical layer
03/02/10 Alcatel Lucent

UP:

User Data

GTP-U UDP IP Ethernet Physical layer

Sinad OReilly

SGSN in Pool Example

Here the RNC is connected to two pooled SGSNs

SGSN 1 (NRI=2)

IuFlex

SGSN 2 (NRI=6)

03/02/10

Alcatel Lucent

Sinad OReilly

SGSN in Pool MiB Extract

RncFunction=1

CnOperator = operator1
MCC=272 MNC=32

Ranap=PS IuLink=PS1
networkResource Identifier=2

SccpApRemote = Cn_Op1

SccpApLocal = Ranap_sig

IuLink=PS2

Ranap=PS
networkResource Identifier=6

SccpApRemote = Cn_Op2

03/02/10

Alcatel Lucent

Sinad OReilly

PDR Managed Objects

Equipment

SpDevicePool

PdrDevice

Spm

IuLink

PacketDataRouter

Aal5TpVccTp

03/02/10

Alcatel Lucent

Sinad OReilly

Management of PDR MOs

PDR 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)

03/02/10

Alcatel Lucent

Sinad OReilly

Scenario for PS User Plane

MGW 2
SPM Slot 19 PDR pg1a PDR Device PDR pg1b AAL5 TP pg1b AAL5 Tp pg1a ETB Slot 6 VCI=64

VCI=68

SPM Slot 23 PDR pg5a PDR Device PDR pg5b AAL5 Tp pg5b AAL5 TP pg5a VCI=64

VCI=68

RNC
03/02/10 Alcatel Lucent

MGW 1
Sinad OReilly

Chapter Concludes
03/02/10 Alcatel Lucent Sinad OReilly