6-240280Issue 1.1CTXX 4727Issue 2.

0en Nokia Networks Oy NOKIA Switching Core Network RNC integration in Nokia 3GRelease 4 Training Documen

Contents 6-240280Issue 1.1 Nokia Networks Oy 3 (22) Contents 1 Objectives.............................................................................................4 2introduction to RNC integration in 3G Release 4 corenetwork......................................................................................5 2.1 Iu-CS control plane................................................................................6 3Integration 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...........................................2

The main steps of integrating the Iu-CS interface are described in the figuresabove. (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 IuCS 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

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 (AALType 2 signalling protocol) and SCCP (in RNC) besides the network management and testing.

The AAL type 2 (ATM adaptation layer type 2) signalling protocol provides signaling services for establishing, maintaining, and releasing AAL type 2point-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 signaling 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 signaling link sets and signalling route sets, and change of the states of signalling links and routes

his procedure describes how to create routing objects and digit analysis for theIu-CS and Iur interfaces. The associated signalling used is broadband MTP3signalling. The routing objects must be created at both ends of the Iu-CSinterface between two network elements before any user plane connections canbe built between the

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 theendpoints have been created.Furthermore, the route, under which the endpoints are to be created, must allowthe type of the endpoints.When we create the route for the Iu-CS interface, we need to specify thefollowing: Route number Route type (which is ATM) Signalling network and signalling point code of MGW (where the route isheading 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 theservice 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 becreated by using the VPIs having the same service category given in theprevious step and also having free VCs under them

ATM route

VCC endpoint

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 planetraffic, voice or data, is intended to be directed.For Iu-CS interface, digit analysis is required only in RNC. The digit analysesused in RNC side have to be created within the same tree (IuDATree) as the onegiven 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 havecreated an analysis with an MML, you must not change the value of the treefrom the GUI.In Iu-CS E.164 AESA (ATM End System Address) is used, so add number 45before 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, digitanalysis is required if the AAL2 nodal functionality is used for theimplementation of Iur interface through a MGW. Nb interface on ATMbackbone, needs digit analysis definitions in MGW

Digit analysis in RNC

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. Thesame address is used in AESA format (i.e. after adding digits 45 before thenumber) in digit analysis at RNC (Created in NEMU

4.1 Integration procedure in MSS Before integrating the RNC to MSS, take care that following things are readyand available. MGW is integrated and registered successfully to the MSS Iu-CS interface between MGW and RNC is created and available for bothcontrol plane and user plane.In MSS, following definitions are to be created to integrate RNC

4.1.1 Signalling definitions Signalling route is to be created in MSS towards RNC. This signalling routewill use MGW as STP. As mentioned before, role of MGW is of signallinggateway.Once the signalling route is created, allow activation of route and then manuallyactivate the route.If SCCP and RANAP (SCCP subsystem) are not created in MSS for its ownpoint code then they are to be created now. After that create SCCP and RANAPfor RNC point code. Activate necessary SCCP and SCCP subsystemdefinitions. 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 iscreated in Cellular Radio network database of MSS, this UPD is

attached toRNC.UPD is used in user plane analysis to find the MGW, which can take care of theuser plane traffic for the call in question.Give unique name to the UPD while creating it. Backbone network connectioncharacteristics (BNCC) for this UPD are always AAL2 because user plane of RNC is always ATM based using AAL2 adaptation. After execution of theMML command, the system will automatically allocate UPD number. Notedown this number as in few MML commands, UPD is identified only bynumber.User plane towards RNC can be controlled by more than one MGW. Attach allthe MGWs, which can control user plane towards given RNC. Selection of MGW from multiple MGWs can be defined by load sharing index

UTRAN datain MSS