Configuring the Iu Interfaces.pdf

(1)

Configuring the Iu Interface

(2)

Configuring the Ericsson UTRAN

1.

1. InInititiaial l CoConfnfigigururatatioionn

2.

2. SiSite te BaBasisic Cc Cononfifiguguraratitionon

3.

3. SiSite te ExExteternarnal l CoConfnfiguiguratratioionn

4.

4. RNRNC SC Site ite SpSpeciecifific Cc Confonfigigurauratitionon

5.

5. RXRXI SiI Site Ste Specpecifific ic CoConfinfiguguratratioionn

6.

6. RBRBS SS Site ite SpSpececifiific c CoConfinfigurguratationion

7.

7. RaRadidio Neo Netwtworork k CoConfnfigigururatatioionn

Week 1

Week 2

(3)

Configuring the Ericsson UTRAN

1.

1. InInititiaial l CoConfnfigigururatatioionn

2.

2. SiSite te BaBasisic Cc Cononfifiguguraratitionon

3.

3. SiSite te ExExteternarnal l CoConfnfiguiguratratioionn

4.

4. RNRNC SC Site ite SpSpeciecifific Cc Confonfigigurauratitionon

5.

5. RXRXI SiI Site Ste Specpecifific ic CoConfinfiguguratratioionn

6.

6. RBRBS SS Site ite SpSpececifiific c CoConfinfigurguratationion

7.

7. RaRadidio Neo Netwtworork k CoConfnfigigururatatioionn

Week 1

Week 2

(4)

St

ag

e 4 –

RN

C Si

te

-S

pe

ci

fi

c

RNC RNC RNCRNC RANAG RANAG Iur Iur I Iuubb IIuubb Iub Iub RBS RBS RBS RBS OSS-RC OSS-RC Mub Mub Mur Mur Core Network Core Network Iu Iu Iu Iu Configuration of the Iu Configuration of the Iu

and Iur interfaces

(5)

Transport History for the Iu/Iur interface

Up to P5 –

Up to P5 – all traffic all traffic transtransmitted omitted over ver AATMTM

P5 release –

P5 release – Iu/Iur CP anIu/Iur CP and IuPS UP od IuPS UP over ver AATM or IPTM or IP

P6/6.1

P6/6.1 relearelease –se – Iur UP ovIur UP over er AATM or IPTM or IP

P7 rele

P7 release –ase – IuCS UIuCS UP ovP over er AATM or IPTM or IP

From P7 onwards

possible to have all

interfaces over IP!

(6)

Iu Interface(s)

RNC RNC SGSN SGSN MSC-S MSC-S MGW MGW IuCS UP IuCS UP IuCS CP IuCS CP IuPS UP/CP IuPS UP/CP

All must be configured!

We focus on configuring from RNC side

(7)

(8)

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

(9)

(10)

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

(11)

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

(12)

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)

(13)

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

(14)

ATM Layer Managed Objects

The 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

(15)

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)

(16)

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!

MP G 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”

(17)

AAL5 Layer Managed Objects

The 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 already PlugInUnit

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 –

(18)

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)

(19)

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

(20)

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.

(21)

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)

(22)

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

(23)

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

IpInterface Up to 8 of these for VLAN seperation

(24)

IP Host Managed Objects

Different MO Classes for Signalling, NTP and user data hosts

Managed Element

IpSystem

IpAccessHostGpb

IP hosts terminate the IP protocol: GPB: Signalling

SPB: IuPS user data

ETB: Iub/IuCS user data, NTP

IpAccessHostSpb

GeneralProcessor

Unit IpInterface Spm

(25)

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

(26)

SCTP Layer - What are We Modelling?

Here we model the SCTP End point

GPB active

IP Access Host GPB

SCTP 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

(27)

(28)

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

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

(29)

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?

(30)

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 1 SLS A 542 M3UA SRS to… use SR1 473 SLS A SR1 342 SLS B SR1 545 SR1 SLS A SLS B SR2

(31)

Mtp3b Layer Managed Objects

TransportNetwork Mtp3bSpItu Mtp3bAp Mtp3bSrs Mtp3bSls M3UAssociation Sctp

Set the node signalling point code (SPC) here

Mtp3bSlItu

NniSaalTp

(32)

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)

(33)

SCCP Layer Managed Objects

TransportNetwork SccpSp SccpScrc SccpApRemote SccpApLocal Mtp3bAp

(34)

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)

(35)

(36)

RANAP Layer Managed Objects

RncFunction CnOperator IuLink SccpApRemote Ranap SccpApLocal 4 32

(37)

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)

(38)

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

(39)

MOCN Example

CN1 Operator 1 PLMN 272-32-2 MSC Server (NRI=5) CN2 Operator 2 PLMN 272-34-2 MSC Server (NRI=2) IuFlex

(40)

MOCN Example – MiB Extract

RncFunction=1 CnOperator = operator1 MCC=272 MNC=32 CnOperator = operator2 IuLink=CS IuLink=CS Ranap=CS Ranap=CS networkResource Identifier=5 SccpApRemote = Cn_Op1 SccpApRemote = Cn_Op2 SccpApLocal = Ranap_sig MCC=272 MNC=34 networkResource Identifier=2

(41)

(42)

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

(43)

IuCS UP Protocol Stacks (ATM/IP)

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

(44)

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

(45)

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

(46)

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=ca1 supportedQosClasses= CLASS_A_B Aal2PathVccTp=ca3 supportedQosClasses= CLASS_A_B VclTp=vc40 VclTp=vc41 VclTp=vc40 VclTp=vc41 Aal2PathVccTp=ca2 supportedQosClasses= CLASS_A_B Aal2PathVccTp=ca4 supportedQosClasses = CLASS_A_B Aal2QosProfile=1

(47)

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 9 GPB slot 8 SCTP sigtran IP Host GPB

ATM-based System IP-based System

Service indicator for

(48)

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

(49)

Q-AAL2 Managed Objects

Transport Network Aal2Sp Aal2Ap Aal2QosCode PointProfile Aal2RoutingCase Mtp3bAp Aal2Path DistributionUnit Aal2PathVccTp

(50)

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

(51)

(52)

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

(53)

IuPS Protocol Stacks (IP)

UP: CP: GTP-U UDP User Data IP Ethernet Physical layer M3UA SCTP RANAP SCCP IP Ethernet Physical layer

(54)

SGSN in Pool Example

SGSN 1 (NRI=2) SGSN 2 (NRI=6) IuFlex

(55)

SGSN in Pool – MiB Extract

RncFunction=1 CnOperator = operator1 MCC=272 MNC=32 IuLink=PS1 IuLink=PS2 Ranap=PS Ranap=PS networkResource Identifier=2 SccpApRemote = Cn_Op1 SccpApRemote = Cn_Op2 SccpApLocal = Ranap_sig networkResource Identifier=6

(56)

PDR Managed Objects

Equipment

SpDevicePool

PdrDevice Spm

(57)

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)

(58)

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 RNC MGW 1

…

MGW 2 PDR pg1a PDR pg1b PDR pg5a PDR pg5b