Configuring the Iu Interfaces.pdf

Configuring the Iu Interface

Configuring the Ericsson UTRAN 1. Init Initia iall Co Conf nfig igur urat atio ion n 2. Site Site Ba Basi sic c Con Confi figu gura rati tion on

Week 1

3. Site Site Exte Externa rnall Co Conf nfigu igurat ratio ion n 4. RN RNC C Site Site Sp Speci ecifi fic c Conf Config igura urati tion on 5. RX RXII Site Site S Spec pecif ific ic Co Confi nfigu gurat ratio ion n Week 2 6. RB RBS S Site Site Sp Spec ecifi ific c Co Confi nfigur gurat ation ion 7. Ra Radi dio o Netw Networ ork k Co Conf nfig igur urat atio ion n 03/02/10

Alcatel Lucent

© Sinéad O’Reill

Configuring the Ericsson UTRAN 1. Init Initia iall Co Conf nfig igur urat atio ion n 2. Site Site Ba Basi sic c Con Confi figu gura rati tion on

Week 1

3. Site Site Exte Externa rnall Co Conf nfigu igurat ratio ion n 4. RN RNC C Site Site Sp Speci ecifi fic c Conf Config igura urati tion on 5. RX RXII Site Site S Spec pecif ific ic Co Confi nfigu gurat ratio ion n Week 2 6. RB RBS S Site Site Sp Spec ecifi ific c Co Confi nfigur gurat ation ion 7. Ra Radi dio o Netw Networ ork k Co Conf nfig igur urat atio ion n 03/02/10

Alcatel Lucent

© Sinéad O’Reill

Stag St age e 4 – RN RNC C Site Site-S -Spe peci cifi fic c Configuration of the Iu and Iur interfaces

Core Network Iu Iu

Iub

Iur

RANAG Mur RNC

RNC OSS-RC

Iub

Iub

RBS

03/02/10

Mub

RBS

Alcatel Lucent

© Sinéad O’Reill

Transport History for the Iu/Iur interface Up to P5 – all traffic trans transmitted mitted over over ATM P5 release – Iu/Iur CP and and IuPS UP over over ATM or IP P6/6.1 relea release se – Iur UP over over ATM or IP P7 release release – IuCS UP UP over over ATM or IP From P7 onwards possible to have all interfaces over IP!

03/02/10

Alcatel Lucent

© Sinéad O’Reill

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

IuCS CP

MSC-S

IuCS UP IuPS UP/CP

RNC

MGW SGSN

All must be configured! 03/02/10

Alcatel Lucent

© Sinéad O’Reill

IuCS Control Plane

03/02/10

Alcatel Lucent

© Sinéad O’Reill

IuCS CP Protocol Stacks (ATM/IP) ATM:

RANAP

IP:

SCCP

SCCP

MTP3b

M3UA

NNI-SAAL

SCTP

AAL 5

IP

ATM

Ethernet

Physical layer 03/02/10

RANAP

Physical layer Alcatel Lucent

© Sinéad O’Reill

ATM/IP Lower Layers

03/02/10

Alcatel Lucent

© Sinéad O’Reill

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

© Sinéad O’Reill

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

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

4

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

© Sinéad O’Reill

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

© Sinéad O’Reill

ATM Layer - What are We Modelling? The logical ATM end-to-end connection Virtual channel - VclTp

Virtual path - VplTp

Core Network

RNC

Virtual Path connection termination point - VpcTp

ATM Port which maps to physical port - AtmPort 03/02/10

Alcatel Lucent

© Sinéad O’Reill

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

AtmTraffic Descriptor

Transport Network

The “TransportNetwork” MO will be in place already

AtmPort

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)

VplTp

VpcTp

VclTp

03/02/10

Alcatel Lucent

© Sinéad O’Reill

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

© Sinéad O’Reill

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

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

SP

MP

S SP SP P B BP

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

© Sinéad O’Reill

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

The “TransportNetwork” MO will be in place already 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

03/02/10

Alcatel Lucent

© Sinéad O’Reill

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

© Sinéad O’Reill

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

© Sinéad O’Reill

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

03/02/10

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

Alcatel Lucent

© Sinéad O’Reill

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

© Sinéad O’Reill

IP Layer - What are We Modelling? GPB

ET-MFG IP Interface

IP @ 1 IP Access Host GPB ET-MFG

IP @ 2

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

IP Interface

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

03/02/10

Alcatel Lucent

© Sinéad O’Reill

IP interface Managed Object The IP interface MO is added to the Gigabit Ethernet port

Equipment

GigaBitEthernet

“Equipment”, down to “GigaBitEthernet” MOs should be in place already

8

IpInterface

03/02/10

Up to 8 of these for VLAN seperation

Alcatel Lucent

© Sinéad O’Reill

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

GeneralProcessor Unit

03/02/10

IpAccessHostEt

IpInterface

Alcatel Lucent

IpAccessHostSpb

Spm

© Sinéad O’Reill

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

© Sinéad O’Reill

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

© Sinéad O’Reill

Higher Layer Protocols

03/02/10

Alcatel Lucent

© Sinéad O’Reill

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

NniSaalProfile

NniSaalTp

The “TransportNetwork” MO will be in place already

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

© Sinéad O’Reill

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

© Sinéad O’Reill

Mtp3b Layer

SRS to…

Viewing these parameters in a bit more detail:

542

use

SR1

M3UA

SR1 473

SLS A SR1

342

542

545

SLS B SR1 SR2

Signalling Link 1

347

SLS A

SLS B

545

Signalling Link 2

My Signalling Point Code is 347

03/02/10

473

SLS A

342

Alcatel Lucent

© Sinéad O’Reill

Mtp3b Layer Managed Objects TransportNetwork

Set the node signalling point code (SPC) here

Mtp3bSpItu

M3UAssociation

Sctp

Mtp3bSls

Mtp3bSrs

Mtp3bSlItu

Mtp3bSr

Mtp3bAp

NniSaalTp

03/02/10

Alcatel Lucent

© Sinéad O’Reill

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

© Sinéad O’Reill

SCCP Layer Managed Objects TransportNetwork

SccpSp

SccpScrc

SccpApLocal

SccpApRemote

Mtp3bAp 03/02/10

Alcatel Lucent

© Sinéad O’Reill

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

© Sinéad O’Reill

Top Level Configuration of IuCS CP

03/02/10

Alcatel Lucent

© Sinéad O’Reill

RANAP Layer Managed Objects RncFunction 4

CnOperator 32

IuLink

Ranap

SccpApLocal 03/02/10

SccpApRemote Alcatel Lucent

© Sinéad O’Reill

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

© Sinéad O’Reill

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

© Sinéad O’Reill

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

IuFlex

03/02/10

MSC Server (NRI=2)

Alcatel Lucent

CN1 Operator 1 PLMN 272-32-2

CN2 Operator 2 PLMN 272-34-2

© Sinéad O’Reill

MOCN Example – MiB Extract RncFunction=1

CnOperator = operator1

Ranap=CS IuLink=CS

networkResource Identifier=5

MCC=272 MNC=32

CnOperator = operator2

SccpApRemote = Cn_Op1

SccpApLocal = Ranap_sig

IuLink=CS

Ranap=CS networkResource Identifier=2

SccpApRemote = Cn_Op2

MCC=272 MNC=34

03/02/10

Alcatel Lucent

© Sinéad O’Reill

IuCS User Plane

03/02/10

Alcatel Lucent

© Sinéad O’Reill

IuCS User Plane

User plane over IP/ATM (AAL2)

Q-AAL2 signalling (if ATM used)

MGW

RNC

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

© Sinéad O’Reill

IuCS UP Protocol Stacks (ATM/IP) Using ATM

AAL 2 ATM SDH

Q-AAL2

Using IP

MTP3b

RTP

NNI-SAAL

UDP

AAL 5 ATM

IP Ethernet

SDH

03/02/10

Alcatel Lucent

© Sinéad O’Reill

Possible Scenario for Lower Layers GPB slot 8

ETB Slot 6 VCI=36

AAL5 Termination Point cqa

AAL2 Path ca1

VCI=40

AAL2 Path ca2

VCI=41

VCs for Q-AAL2 signalling

GPB slot 9 VCI=36

AAL5 Termination Point cqb

AAL2 Path ca3

VCI=40

AAL2 Path ca4

VCI=41

RNC 03/02/10

MGW Alcatel Lucent

© Sinéad O’Reill

Example – MiB Extract for ATM AtmPort= MS-6-1

AtmTrafficDescriptor = C1P33000

VplTp=vp1

VpcTp=1

AtmPort= MS-6-2 VplTp=vp1

AtmTrafficDescriptor = U3P4500M3000

VpcTp=1

VclTp =vc36 VclTp =vc40

VclTp =vc36 AtmTrafficDescriptor = C2P12000

VclTp =vc41

03/02/10

VclTp =vc40 VclTp =vc41

Alcatel Lucent

© Sinéad O’Reill

Example – MiB Extract for AAL Layer Slot=9

Slot=8 TransportNetwork=1 PlugInUnit=1

VclTp=vc36

VclTp=vc40

VclTp=vc41

Aal5TpVccTp=cqa

Aal5TpVccTp=cqb

Aal2PathVccTp=ca1

Aal2PathVccTp=ca3

supportedQosClasses= CLASS_A_B

supportedQosClasses= CLASS_A_B

Aal2PathVccTp=ca2

Aal2PathVccTp=ca4

supportedQosClasses= CLASS_A_B

supportedQosClasses = CLASS_A_B

PlugInUnit=1

VclTp=vc36

VclTp=vc40

VclTp=vc41

Aal2QosProfile=1 03/02/10

Alcatel Lucent

© Sinéad O’Reill

Possible Scenario for Higher Layers Mtp3bAp cq service indicator =12

Service indicator for Q-AAL2

Mtp3bSrs cq Destination Point Code = MGW Signaling Point Code Mtp3bSr cq Mtp3bSls cq Mtp3bSl cqa

M3UA cq

Mtp3bSl cqb

NniSaalTp cqa

NniSaalTp cqb

AAL5Tp cqa

AAL5Tp cqb

IP Host GPB

GPB slot 8

GPB slot 9

GPB slot 8

ATM-based System 03/02/10

SCTP sigtran

GPB slot 9

IP-based System Alcatel Lucent

© Sinéad O’Reill

Q-AAL2

Number direction

Setting up the AAL2 paths between nodes

1000...

1345…

Path B

1200...

10

Path A

12

Path B

13

Path C

1210...

My AESA is 1345…

1300...

03/02/10

Alcatel Lucent

© Sinéad O’Reill

Q-AAL2 Managed Objects Transport Network

Aal2Sp

Aal2QosCode PointProfile

Mtp3bAp

Aal2Ap

Aal2RoutingCase

Aal2Path DistributionUnit

Aal2PathVccTp

03/02/10

Alcatel Lucent

© Sinéad O’Reill

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

© Sinéad O’Reill

IuPS Interface

03/02/10

Alcatel Lucent

© Sinéad O’Reill

IuPS Protocol Stacks (ATM) CP:

RANAP

UP:

SCCP

GTP-U

MTP3b

UDP

NNI-SAAL

IP

AAL 5

AAL 5

ATM

ATM

Physical layer 03/02/10

User Plane

Physical layer Alcatel Lucent

© Sinéad O’Reill

IuPS Protocol Stacks (IP) CP:

RANAP

UP:

User Data

SCCP

03/02/10

M3UA

GTP-U

SCTP

UDP

IP

IP

Ethernet

Ethernet

Physical layer

Physical layer Alcatel Lucent

© Sinéad O’Reill

SGSN in Pool Example Here the RNC is connected to two pooled SGSNs

SGSN 1 (NRI=2)

SGSN 2 (NRI=6)

IuFlex

03/02/10

Alcatel Lucent

© Sinéad O’Reill

SGSN in Pool – MiB Extract RncFunction=1

CnOperator = operator1

Ranap=PS networkResource Identifier=2

IuLink=PS1

MCC=272 MNC=32

SccpApLocal = Ranap_sig

IuLink=PS2

03/02/10

SccpApRemote = Cn_Op1

Ranap=PS networkResource Identifier=6

Alcatel Lucent

SccpApRemote = Cn_Op2

© Sinéad O’Reill

PDR Managed Objects Equipment

SpDevicePool

PdrDevice

IuLink

03/02/10

PacketDataRouter

Alcatel Lucent

Spm

Aal5TpVccTp

© Sinéad O’Reill

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

© Sinéad O’Reill

Scenario for PS User Plane MGW 2 SPM Slot 19 PDR pg1a

AAL5 Tp pg1a

VCI=64

…

PDR Device PDR pg1b

ETB Slot 6

AAL5 TP pg1b

VCI=68

… SPM Slot 23 PDR pg5a

AAL5 TP pg5a

…

PDR Device PDR pg5b

AAL5 Tp pg5b

VCI=68

MGW 1

RNC 03/02/10

VCI=64

Alcatel Lucent

© Sinéad O’Reill