10 RNC Integration in Nokia 3G Release 4

6-240280 Issue 1.1

CTXX 4727

Issue 2.0en

© Nokia Networks Oy

NOKIA Switching Core Network

RNC integration in Nokia 3G Release 4

Training Document

M13

M13

2 (22) © Nokia Networks Oy

6-240280 Issue 1.1

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia's customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according to the applicable laws.

NOKIA logo is a registered trademark of Nokia Oyj.

Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only.

Copyright © Nokia Oyj 2005. All rights reserved.

Contents

6-240280 Issue 1.1


3 (22)

Contents

1 Objectives............................................................................................. 4

2 Introduction to RNC integration in 3G Release 4 core network...................................................................................... 5

2.1 Iu-CS control plane ................................................................................ 6

3 Integration of RNC to 3G Release 4 MGW (Iu-CS).............................. 7 3.1 Creation of ATM resources for control plane and user plane.................. 7 3.2 Creation of SS7 configuration for control plane ...................................... 9 3.2.1 Creation of MTP and MTP services........................................................ 9 3.3 Creation of routing objects and digit analysis for user plane................. 12 3.3.1 Creation of routing objects ................................................................... 14 3.3.2 Creation of digit analysis in RNC & MGW ............................................ 17 3.4 Configure other Iu-CS parameters ....................................................... 18

4 Integration RNC to MSC server......................................................... 19 4.1 Integration procedure in MSS............................................................... 19 4.1.1 Signalling definitions ............................................................................ 20 4.1.2 User plane routing definitions............................................................... 20 4.1.3 Cellular Radio Network definitions in MSS ........................................... 21

M13


6-240280 Issue 1.1

1 Objectives

After this module the student should be able to:

• Identify the key components of integration of RNC to 3G Release 4 core

network.

• Explain each step of the RNC integration to the 3G PP Release 4 core

network with the use of the Integration Manual for MSS and MGW

(available in NED).

• With the use of the Integration Manual, list and explain the necessary

integration parameters.

M13

6-240280 Issue 1.1


5 (22)

2 Introduction to RNC integration in 3G Release 4 core network

This chapter describes the integration procedure of 3G Release 4 Core network

to 3G UTRAN. Iu-CS interface is the interface between Multimedia Gateway

(MGW) and Radio Network Controller (RNC). In 3G Release 4 it is extended to

MSC Server (MSS) also. MGW takes both control plane and user plane data

from RNC. Control plane is transferred to MSS while user plane is switched by

MGW under the control of MSS. In MSS, we also need to define signalling

definitions, user plane related routing definitions and cellular radio network

related configuration for RAN.

Role of MGW can be summarised as

• Signalling gateway for control plane

• Switching of user plane under control of MSS

Figure 1. Interfaces in 3G Release 4 core network

M13


6-240280 Issue 1.1

2.1 Iu-CS control plane

Iu-CS interface is ATM based and carries user plane using AAL2 adaptation

layer and control plane using AAL5 adaptation layer. The control plane consists

of RANAP signalling protocol.

Figure 2. RANAP signalling between RNC and MSS

M13

6-240280 Issue 1.1


7 (22)

3 Integration of RNC to 3G Release 4 MGW (Iu-CS)

Figure 3. Integration procedure in RNC & MGW Figure 4. Integration procedure in MSS

The main steps of integrating the Iu-CS interface are described in the figures

above. (Figure 3: Integration procedure in RNC and MGW, Figure 4:

Integration procedure in MSS)

NOTE:

Before starting the integration process please ensure that all necessary

parameters for create Iu-CS interface are available.

RNC, MGW and MSS are fully commissioned.

MGW is integrated to MSS.

3.1 Creation of ATM resources for control plane and user plane.

ATM Resources are to create for both control plane and user plane before

creating any signalling and routing definitions.

Set upIu-CS Interface

1. Configure of the physical interfaces

2. Creation of ATM resourcefor control and user plane

3. Creation of signalling configurationfor control plane

4. Creation of routing and digit analysisfor user plane

End

5. Configure RNC and MGW parameters

Set upIu-CS Interface





End






End


Create signalling route to RNC throughMGW. Create SCCP & subsystem RANAP

Activate signalling definitions created earlier.

Create UPD for RNC. Add MGW to UPD

Create Cellular radio networkConfiguration for RAN.

End

Unlock Cellular radio network definitions





End


Create signalling route to RNC throughMGW. Create SCCP & subsystem RANAP

Activate signalling definitions created earlier.

Create UPD for RNC. Add MGW to UPD

Create Cellular radio networkConfiguration for RAN.

End

Unlock Cellular radio network definitions

M13


6-240280 Issue 1.1

ATM resource creation is described in the chapter “ATM Resource

Management and Digit Analysis”.

Figure 5. Creation of ATM resources

ATM interface

Access profiles of ATM interfaces

VPL termination point (VPLtp)

VCL termination point (VCLtp)

VC connection

phyTTP

ATM interface

Access profiles of ATM interfaces

VPL termination point (VPLtp)

VCL termination point (VCLtp)

VC connection

phyTTP

M13

6-240280 Issue 1.1


9 (22)

3.2 Creation of SS7 configuration for control plane

Iu-CS interface consist of the user plane and control plane. On the control plane

at application level we have the RANAP protocol running over MTP3B and

SCCP for Iu-CS interface. AAL type 2 signalling is used for ATM bearer

establishment between RNC and MGW.

Figure 6. Creating control plane

3.2.1 Creation of MTP and MTP services

We start the creation of the SS7 signalling configuration on Iu-CS by building

the MTP first. In MTP level the first step to start is the creation of services. As

far as Iu-CS is concerned, the needed services of MTP are the AAL2 (AAL

Type 2 signalling protocol) and SCCP (in RNC) besides the network

management and testing.

ATM based signalling link

Signalling link set

Signalling route set

Allow activation and activate link

Allow activation and activate route set

Create AAL2 service if not created

ATM based signalling link

Signalling link set


Allow activation and activate link

Allow activation and activate route set

Create AAL2 service if not created

M13


6-240280 Issue 1.1

Figure 7. MTP3 and its services in RNC

The AAL type 2 (ATM adaptation layer type 2) signalling protocol provides

signalling services for establishing, maintaining, and releasing AAL type 2

point-to-point data connections between two AAL-type-2 end users.

Once the services are created, we need to create an own signalling point code of

the RNC and MGW. After this step we are able to start creating the signalling

link, on which we are able to deliver the signalling messages.

When we create the signalling links over the Iu-CS interface, they will based on

ATM VCs, which were reserved in the earlier steps of integration process (that

is, when we created the ATM resources for signalling, user traffic, and O&M

data purposes).

Subsequent steps of the signalling link creation are the creation of the signalling

link sets and signalling route sets, and change of the states of signalling links

and routes.

Service Information Octet

SCCP SNM SNT

Message Routing

MTP - 3

Message forown SPC

AAL2 SIG

Service Information Octet

SCCP SNM SNT

Message Routing

MTP - 3

Message forown SPC

AAL2 SIG

M13

6-240280 Issue 1.1


11 (22)

Signalling link

Signalling link set


Figure 8. Creation of MTP

Signalling ATM adaptation layer, Network-Node Interface (NNI), consists of

protocol stacks SSCF-NNI (service-specific co-ordination function - NNI),

SSCOP (service-specific connection-oriented protocol), and AAL5 (ATM

adaptation layer 5). This protocol stack provides reliable transport of messages

over the ATM layer. From the integration point of view, we do not need to

configure the SAAL NNI manually. This part of the protocol stack is

automatically configured after the MTP3 is built and after the signalling links

are built over ATM PVCs.

Figure 9. Signalling protocol stack in MGW towards RNC

ATM

AAL5

SCCOP

SSCF –NNI

MTP3b

STC

AAL2

ATM

AAL5

SCCOP

SSCF –NNI

MTP3b

STC

AAL2

M13


6-240280 Issue 1.1

3.3 Creation of routing objects and digit analysis for user plane

The flowchart below shows the procedure for creating user plane

Figure 10. Creating user plane procedure

This procedure describes how to create routing objects and digit analysis for the

Iu-CS and Iur interfaces. The associated signalling used is broadband MTP3

signalling. The routing objects must be created at both ends of the Iu-CS

interface between two network elements before any user plane connections can

be built between them.

AAL type 2 connection

Digit analysis

Destination

Subdestination

ATM route

VCC endpoint group

VCCep

1

2

3

5

Create an ATM route

Create VCC endpoint group(s)

Create VCC endpoint(s)

Create digit analysis

4 Unblock AAL2 path


Digit analysis

Destination

Subdestination

ATM route

VCC endpoint group

VCCep

1

2

3

5

Create an ATM route



Create digit analysis

4 Unblock AAL2 path

M13

6-240280 Issue 1.1


13 (22)

DX200 IPA2800

Digit analysis in put

parameters

Dial number, CF No,

MSRN, HON

ATM End System

Address (AESA)

Digit analysis is used

when

Involve with call, i.e. call

set-up

AAL2 connection is

needed

Destination Call destination AAL2 destination

Subdestination Map to CS-route Map to ATM route

Table 1 Digit analysis concept in DX200 MSC and IPA2800

RNC/MGW

Route(common concept)

Circuit Group

Circuit

VCCE group

VCCE

Figure 11. Route concept in DX200 and IPA2800

Questions

1. When does an RNC need to set up AAL2 connection?

____________________________________________

2. The RNC sets up AAL2 connection to which NEs?

NodeB MGW 3G SGSN RNC MSC

In ATM, routing has a close relationship to Connection Admission Control

(CAC). It is different from the TDM world. In TDM, when a free circuit is

hunted, the resource is found for the connection. In ATM, CAC is needed after

selection of VPC/VCC. CAC decides finally if the connection can be accepted

so that the guaranteed QoS of a new connection and existing connections is not

M13


6-240280 Issue 1.1

violated. Examples of input parameter for CAC are QoS class, Service Category

and egress traffic parameters. The concept of CAC algorithm in ATM compare

to traditional TDM is shown in figure below.

Figure 12. TDM route and ATM route

3.3.1 Creation of routing objects

Before starting, we have to make sure that the appropriate (broadband MTP3)

signalling and the associated VC link termination points (VCLtp) for the

endpoints have been created.

Furthermore, the route, under which the endpoints are to be created, must allow

the type of the endpoints.

When we create the route for the Iu-CS interface, we need to specify the

following:

• Route number

• Route type (which is ATM)

• Signalling network and signalling point code of MGW (where the route is

heading to)

• The AAL2 node identifier (Name of AAL2 node where route heading to)

In the following step, when we create the endpoint group, we can specify the

service category to be placed under this route for ingress and egress directions.

The service category options are CBR, VBR, and UBR.

After the endpoint groups are created, the endpoints themselves could be

created by using the VPIs having the same service category given in the

previous step and also having free VCs under them.

Free Circuit

Available VP/VC that can support

QoS

ConnectionAccepted

ConnectionAccepted

ConnectionRejected

ConnectionRejected

ATM routeTDM route

NoNo

YesYes

CAC

Free Circuit

Available VP/VC that can support

QoS

ConnectionAccepted

ConnectionAccepted

ConnectionRejected

ConnectionRejected

ATM routeTDM route

NoNo

YesYes

CAC

M13

6-240280 Issue 1.1


15 (22)

The final step to execute is the unblocking of AAL type 2 path (VCCep).

Figure 13. Steps to create routing and digit analysis

RRI:;

ROUTES

ROU TYPE INT/EXT USER_ST SIGP ANI NET SPC (H/D)

1 ATM EXT WO-EX AAL2 A00002001 - 0000/00000

2 ATM EXT WO-EX AAL2 A00002002 - 0000/00000

3 ATM EXT WO-EX AAL2 A00002003 - 0000/00000

4 ATM EXT WO-EX AAL2 A00004001 - 0000/00000 5 ATM EXT WO-EX AAL2 A00004002 - 0000/00000

6 ATM EXT WO-EX AAL2 A00004003 - 0000/00000

100 ATM EXT WO-EX AAL2 MGW01 NA0 0888/02184

Figure 14. ATM route


Digit analysis

Destination

Subdestination

ATM route

VCC endpoint group

VCCep

IN RNC & MGW

IN RNC & MGW 1

2

3

4

Create an ATM route




Digit analysis

Destination

Subdestination

ATM route

VCC endpoint group

VCCep

IN RNC & MGW

IN RNC & MGW 1

2

3

4

Create an ATM route



M13


6-240280 Issue 1.1

LII:100,;

INTERROGATE ENDPOINT GROUP

ROUTE EP IN SERV EG SERV

NUMBER GROUP CATEGORY CATEGORY ------ ----- ---------- ----------

100 1 C C

Figure 15. VCC Endpoint group

LJI:ROU=100,;

LOADING PROGRAM VERSION 2.1-0

INTERROGATE ENDPOINT

ROUTE EP PATH TERMINATION POINT

NUMBER GROUP ID IF ID VPI VCI ------ ----- ---------- ----- ----- ------

100 1 1 1 1 36

AAL2 CPS-SDU

OWNER LOSS R MUX DEL

----- ------- -------

LOCAL 1*10E-5 10.0 MS

EFF ADMIN EFF OPER LOCAL REMOTE

STATE STATE END AGREED END --------- -------- --------- ------ ---------

UNLOCKED ENABLED UNBLOCKED NO UNBLOCKED

OVERALL

STATE

-------

WO - EX

COMMAND EXECUTED

Figure 16. VCC endpoint

M13

6-240280 Issue 1.1


17 (22)

Digits

TREE Destination/

Subdestination

Endpoint

Group

Endpoint

Tree Digit ATM Route

1 45xxx 100

2 49xxx

Route ANI SPC

100 MGW01 888

Route Number E-Group Ingress Egress

100 1 C C

ATM Route E-Group IF VPI VCI

100 1 1 1 36

ZRIIZRRI

ZLII

ZLJI

Digits

TREETREE Destination/

Subdestination

Destination/

Subdestination

Endpoint

Group

EndpointEndpoint

Tree Digit ATM Route

1 45xxx 100

2 49xxx

Route ANI SPC

100 MGW01 888

Route Number E-Group Ingress Egress

100 1 C C

ATM Route E-Group IF VPI VCI

100 1 1 1 36

ZRIIZRRI

ZLII

ZLJI

Figure 17. Example of routing and digit analysis with interrogation commands

3.3.2 Creation of digit analysis in RNC & MGW

The digit analysis is used to find a route to the destination that the user plane

traffic, voice or data, is intended to be directed.

For Iu-CS interface, digit analysis is required only in RNC. The digit analyses

used in RNC side have to be created within the same tree (IuDATree) as the one

given in the RNC dialog of the RNC RNW Object Browser.

The analyses related to the Iu-CS interface are created with MML commands.

All the digit analyses in Iu are related to one digit analysis tree. Once you have

created an analysis with an MML, you must not change the value of the tree

from the GUI.

In Iu-CS E.164 AESA (ATM End System Address) is used, so add number 45

before digit sequence in order to avoid conflicts with different number formats.

For more information see “ATM Resource and Digit Analysis” module.

Digit analysis is not required in MGW for Iu-CS interface. But in MGW, digit

analysis is required if the AAL2 nodal functionality is used for the

implementation of Iur interface through a MGW. Nb interface on ATM

backbone, needs digit analysis definitions in MGW.

M13


6-240280 Issue 1.1

E.164 AESA

An E.164 AESA allows an E.164 number to be encapsulated within an AESA

structure.

The IDI of an E.164 AESA contains an E.164 address and is always 8 octets in

length. In order to encode the E.164 within the AESA, a single semi-octet (1111

= F) is added to the end of the E.164 number to obtain an integral number of

octets. The E.164 is padded with leading zeros.

AFI = 45 0 0 0 0 0 0 0 0 0 0 6 6 1 0 0 F HO-DSP ESI SEL

E.164 number +66 100 encoded in an AESA structure.

Figure 18. E.164 AESA Encoding

Figure 19. Digit analysis in RNC (created by NEMU)

3.4 Configure other Iu-CS parameters

MGW AAL2 services endpoint address is to be defined in MGW

(ZWEC:AAL2:SEA=XXXX). This address is defined in E.164 format. The

same address is used in AESA format (i.e. after adding digits ‘45’ before the

number) in digit analysis at RNC (Created in NEMU).

M13

6-240280 Issue 1.1


19 (22)

4 Integration RNC to MSC server

Nokia MSS can simultaneously behave as 3G MSC for R99 MGW and as MSC

server for R4 MGW. This section describes integration of RNC to MSC server.

Figure 20. RNC example configuration for 3G Release 4 core network

4.1 Integration procedure in MSS

Before integrating the RNC to MSS, take care that following things are ready

and available.

• MGW is integrated and registered successfully to the MSS

• Iu-CS interface between MGW and RNC is created and available for both

control plane and user plane.

In MSS, following definitions are to be created to integrate RNC.

M13


6-240280 Issue 1.1

4.1.1 Signalling definitions

Signalling route is to be created in MSS towards RNC. This signalling route

will use MGW as STP. As mentioned before, role of MGW is of signalling

gateway.

Once the signalling route is created, allow activation of route and then manually

activate the route.

If SCCP and RANAP (SCCP subsystem) are not created in MSS for its own

point code then they are to be created now. After that create SCCP and RANAP

for RNC point code. Activate necessary SCCP and SCCP subsystem

definitions.

4.1.2 User plane routing definitions

RNC data in MSS is defined differently for 3G Release 4.

User plane destination (UPD) has to be created first. Later on when RNC is

created in Cellular Radio network database of MSS, this UPD is attached to

RNC.

UPD is used in user plane analysis to find the MGW, which can take care of the

user plane traffic for the call in question.

Give unique name to the UPD while creating it. Backbone network connection

characteristics (BNCC) for this UPD are always AAL2 because user plane of

RNC is always ATM based using AAL2 adaptation. After execution of the

MML command, the system will automatically allocate UPD number. Note

down this number as in few MML commands, UPD is identified only by

number.

User plane towards RNC can be controlled by more than one MGW. Attach all

the MGWs, which can control user plane towards given RNC. Selection of

MGW from multiple MGWs can be defined by load sharing index.

M13

6-240280 Issue 1.1


21 (22)

Figure 21. Example of UPD for RNC

Cellular radio network definitions

4.1.3 Cellular Radio Network definitions in MSS

Procedure of creating cellular radio network definitions for RNC in 3G Release

4 is as described in figure below.

Figure 22. UTRAN data in MSS

JFI:UPD=0:;

MSCi DX220-LAB 2004-06-14

11:33:00

NAME: UPD0 ID: 000

RESELECTION PROVISION:

NORMAL CALLS: PREPARE BNC

EMERGENCY CALLS: PREPARE BNC

BNC CHARACTERISTICS: AAL2

DEFAULT CODEC: G711

MGWS:

NAME ID REG LDSH

---- -- --- ----

MGW01 0 Y 1

Create RNC to MSS radio network

Create Service area

Define LA-SA-MGW relation(put MGWNBR=MSS for Rel. 4)

Unlock service area

Unlock RNC

Create Location Area

Create RNC to MSS radio network

Create Service area

Define LA-SA-MGW relation(put MGWNBR=MSS for Rel. 4)

Unlock service area

Unlock RNC

Create Location Area

M13


6-240280 Issue 1.1

Figure 23. Example of RNC data in MSS

E2I:RNCID=1,:;

MSCi DX220-LAB 2004-06-14

11:40:30

RNC IN OWN RADIO NETWORK

===========================================

RNC IDENTIFICATION:

RNC IDENTIFICATION............. RNCID ... : 0001

MOBILE COUNTRY CODE............ MCC ..... : 244

MOBILE NETWORK CODE............ MNC ..... : 06

RNC NAME....................... RNCNAME . : RNC01

RNC PARAMETERS:

RNC STATE...................... STATE ... : UNLOCKED

RNC OPERATIONAL STATE.......... OPSTATE . : AVAILABLE

USER PLANE DESTINATION INDEX... UPD ..... : 000

USER PLANE DESTINATION NAME.... NUPD .... : UPD0

RNC VERSION.................... VER ..... : R99

AMR SPEECH CODEC MODE COUNT.... AMR ..... : 4

RNC GLOBAL TITLE ADDRESS....... DIG ..... : -

NUMBERING PLAN................. NP ...... : -

TYPE OF NUMBER................. TON ..... : -

NETWORK INDICATOR.............. NI ...... : NA0

SIGNALLING POINT CODE.......... SPC ..... : 2710

LOCATION AREA CODE LIST:

LAC MCC MNC

===============

01727 244 06

Documents

10 RNC Integration in Nokia 3G Release 4