ADAPTATION DIRECTION 1/155 42-CNT 293 0429 Uen B

Telefonaktiebolaget LM Ericsson 2008. All rights reserved.

MRNCA

Mobile Telephony Data: Radio Network Controller

Contents
1 Introduction
1.1 Scope
1.2 Handling Instructions

2 Commands
2.1 EXRBC
2.2 EXROE
2.3 EXROI
2.4 MGLAE
2.5 MGLAI
2.6 MGMAE
2.7 MGMAI
2.8 MGRIC
2.9 MGRIE
2.10 MGRII
2.11 SETIR
2.12 SETRE

3 Examples
3.1 Connection of New RNC
3.2 Changing of RNC Data
3.3 Disconnection of RNC

4 Glossary

5 References
5.1 Operational Instructions
5.2 Command Descriptions
5.3 Application Information

1 Introduction

1.1 Scope
This Adaptation Direction describes the administration of Radio Network Controller
(RNC) and Universal Mobile Telecommunication System (UMTS) paging areas which
consists of the following:

Connection of new RNC

Changing of RNC identity or Global Core Network Identity Capability (GLCNID)
for RNC or both of them
Adding the supported codecs of the RNC
Removing the supported codecs of the RNC
Changing data for outgoing and incoming traffic routes
Changing of Transport Bearer (TB)
Definition of location area
Definition of UMTS paging area
Deletion of UMTS paging area
Deletion of location area
Disconnection of RNC

1.2 Handling Instructions

Complete handling of RNC administration is described in the following Operational
Instructions:

Operational Instruction Mobile Telephony, Location Area, Define

Operational Instruction Mobile Telephony, Location Area, Delete
Operational Instruction Mobile Telephony, RNC, Connect
Operational Instruction Mobile Telephony, RNC, Change
Operational Instruction Mobile Telephony, RNC, Disconnect
Operational Instruction Mobile Telephony, UMTS Paging Area, Define
Operational Instruction Mobile Telephony, UMTS Paging Area, Delete
Operational Instruction Data Record Route, Connect
Operational Instruction Route Data, Change
Operational Instruction Data Record Route, Disconnect
Operational Instruction Seizure Supervision of Trunks and IWU, Change

2 Commands

2.1 EXRBC
Command EXRBC changes or specifies route data in the Mobile Services Switching
Centre (MSC) / Visitor Location Register (VLR) Server. The data can be changed
regardless of the route state.

For information about the command syntax and parameters, see Command
Description EXRBC.
2.2 EXROE
Command EXROE deletes all data which concerns a route or routes in the MSC/VLR
Server.

For information about the command syntax and parameters, see Command
Description EXROE.

2.3 EXROI
Command EXROI initiates and defines data for a route or routes in the MSC/VLR
Server.

For information about the command syntax and parameters, see Command
Description EXROI.

2.4 MGLAE
Command MGLAE deletes the definition of a Location Area Identity (LAI) from the
MSC/VLR Server.

For information about the command syntax and parameters, see Command
Description MGLAE.

2.5 MGLAI
Command MGLAI defines a LAI in the MSC/VLR Server.

For information about the command syntax and parameters, see Command
Description MGLAI.

2.6 MGMAE
Command MGMAE deletes a connection between a LAI and an RNC.

For information about the command syntax and parameters, see Command
Description MGMAE.

2.7 MGMAI
Command MGMAI defines a connection between a LAI and an RNC.

For information about the command syntax and parameters, see Command
Description MGMAI.
2.8 MGRIC
This command either changes the RNC identity, the GLCNID capability or both of
them, or it sets or removes specific or all of the supported codecs for an RNC in the
MSC/VLR Server, or it changes the TB supported by an RNC.

For information about the command syntax and parameters, see Command
Description MGRIC.

2.9 MGRIE
Command MGRIE deletes the definition of an RNC data in the MSC/VLR Server.

For information about the command syntax and parameters, see Command
Description MGRIE.

2.10 MGRII
Command MGRII defines a new RNC in the MSC/VLR Server. The GLCNID capability
is initiated to the value "Not Supported" for the connected RNC. The TB is set to
default value "Asynchronous Transfer Mode" (ATM) when an RNC is defined.

For information about the command syntax and parameters, see Command
Description MGRII.

2.11 SETIR
Command SETIR connects or reconnects the seizure supervision on routes.

For information about the command syntax and parameters, see Command
Description SETIR.

2.12 SETRE
Command SETRE disconnects the seizure supervision on routes.

For information about the command syntax and parameters, see Command
Description SETRE.

3 Examples

3.1 Connection of New RNC

3.1.1 Scenario

This example connects a new RNC HKI1 with RNC identity 228-12-206 to the
MSC/VLR Server. It defines the following new LAIs:

New LAI 228-12-1200.

New LAI 228-12-1201.
New LAI 228-12-1202.

and connects them to the RNC called HKI1. It defines new outgoing traffic route
OCIT4 and incoming traffic route ICIT4 with the following specifications:
Device type MUIUCM
Signalling Connection Control Part (SCCP) protocol, SI=SCCP
Signalling point 2-12345, indicating a national network with destination point
code 12345, SP=2-12345

The example also connects seizure supervision for outgoing traffic route OCIT4 and
incoming traffic route ICIT4.

3.1.2 Initiation and Definition of Data for Outgoing and Incoming Traffic
Routes

Initiate outgoing traffic route OCIT4 and incoming traffic route ICIT4.

EXROI:R=OCIT4&ICIT4,DETY=MUIUCM,SI=SCCP,SP=2-12345;

See the Application Information for block MUIUCM.

3.1.3 Connection of Seizure Supervision

Connect seizure supervision to outgoing traffic route OCIT4 and incoming traffic route
ICIT4.

SETIR:R=OCIT4&ICIT4;

For more information, see Operational Instruction Seizure Supervision of Trunks and
IWU, Change.

3.1.4 Definition of New RNC

Define new RNC HKI1 with RNC identity 228-12-206 and connect outgoing traffic
route OCIT4 and incoming traffic route ICIT4 to it. GLNCIND capability is initialized
to value 0 (Not supported). TB is initialized to value 0 (ATM).

The parameter RNCID consists of three parts. The first field is the mobile country
code, the second one is the mobile network code, and the last one is the RNC
number.

MGRII:RNC=HKI1,RNCID=228-12-206,R1=OCIT4,R2=ICIT4;
3.1.5 Definition of Location Areas

Define the LAIs 228-12-1200, 228-12-1201 and 228-12-1202.

The parameter LAI consists of three parts. The first field is the mobile country code,
the second one is the mobile network code, and the last one is the location area
code.

MGLAI:LAI=228-12-1200;
MGLAI:LAI=228-12-1201;
MGLAI:LAI=228-12-1202;

3.1.6 Definition of UMTS Paging Areas

This example connects RNC called HKI1 to LAI1,LAI2 and LAI3. Figure 1 shows this
connection.

Figure 1 UMTS Paging Area

Connect the RNCs and the LAIs

MGMAI:LAI=228-12-1200,RNC=HKI1;
MGMAI:LAI=228-12-1201,RNC=HKI1;
MGMAI:LAI=228-12-1202,RNC=HKI1;

Note: A maximum of 32 RNCs can be connected to one LAI.

3.2 Changing of RNC Data

3.2.1 Scenario

The first example changes the RNCID for RNC HKI1 from 228-12-206 to 228-12-260.
Note that the new RNCID must be unused.

The second example changes the RNCID for RNC HKI1 from 228-12-206 to 228-12-
260 and changes GLCNID to 1 (supported). Note that the new RNCID must be
unused.

The third example changes GLCNID to 1 (supported).

The fourth example sets the UMTS_AMR2_GC as supported codec of the RNC HKI1.

The fifth example sets the UMTS_AMR2_GC and UMTS_AMR_WB_SET0 as supported

codecs of the RNC HKI1.

The sixth example removes the UMTS_AMR2_GC from the list of codecs supported by
the RNC HKI1.

The seventh example removes all the codecs from the list of supported codecs by the
RNC HKI1.

The eighth example changes the TB supported by RNC HKI1.

The ninth example changes the PBSD parameter for incoming route ICIT4 and
changes the MGG parameter for incoming route ICIT4 and also for outgoing route
OCIT4.

3.2.2 Changing of RNC Identity

Change RNC identity for RNC HKI1 to 228-12-260.

MGRIC:RNC=HKI1,RNCID=228-12-260;

3.2.3 Changing of the RNC Identity and the Capability GLCNID

Change RNC identity for RNC HKI1 to 228-12-260 and changing GLCNID to 1
(supported).

MGRIC:RNC=HKI1,RNCID=228-12-260,GLCNID=1;

3.2.4 Changing the GLCNID Capability

Change GLCNID to 1 (supported).

MGRIC:RNC=HKI1,GLCNID=1;
3.2.5 Adding an RNCCODEC

Set the UMTS_AMR2_GC as supported codec of the RNC HKI1.

MGRIC:RNC=HKI1,RNCCODEC=UMTS_AMR2_GC;

3.2.6 Adding two RNCCODECs

Set the UMTS_AMR2_GC and UMTS_AMR_WB_SET0 as supported codecs of the RNC

HKI1.

MGRIC:RNC=HKI1,RNCCODEC=UMTS_AMR2_GC&UMTS_AMR_WB_SET0;

3.2.7 Removing an RNCCODEC

Remove the codec UMTS_AMR2_GC from the list of codecs supported by the RNC
HKI1.

MGRIC:RNC=HKI1,RRNCCODEC=UMTS_AMR2_GC;

3.2.8 Removing all the RNCCODECs

Remove all the codecs from the list of codecs supported by RNC HKI1.

MGRIC:RNC=HKI1,RRNCCODEC=ALL;

3.2.9 Changing the TB Supported by the RNC

All calls established on RNC-HKI1 will use TB Internet Protocol (IP).

MGRIC:RNC=HKI1,TB=1;

3.2.10 Changing Data for Outgoing and Incoming Traffic Routes

If Media Gateway Selection is supported, the PBSD parameter for incoming routes
and the MGG parameter for incoming and outgoing routes can be specified.

EXRBC:R=ICIT4,RGSPAR=PBSD-FORWD;
EXRBC:R=ICIT4,RGSPAR=MGG-MGG1;
EXRBC:R=OCIT4,RGSPAR=MGG-MGG1;

See the Application Information for block MUIUCM.

Note: The MGG parameter is required for both incoming and outgoing routes. The
MGGs can be of different values. PBSD is applicable for incoming routes only.

3.3 Disconnection of RNC

3.3.1 Scenario

This example disconnects RNC HKI1 from the MSC/VLR Server.

Before the deletion of the RNC can take place, the LAIs connected to the RNC should
be disconnected. This example disconnects the LAIs 228-12-1200, 228-12-1201, and
228-12-1202 from RNC with identity HKI1. If the LAIs and the traffic routes are no
longer required, they can be deleted.

The example deletes the affiliated traffic routes OCIT4 and ICIT4. The example also
disconnects the seizure supervision for outgoing traffic route OCIT4 and incoming
traffic route ICIT4.

3.3.2 Deletion of UMTS Paging Areas

Delete connection between the RNC and the LAIs.

MGMAE:LAI=228-12-1200,RNC=HKI1;
MGMAE:LAI=228-12-1201,RNC=HKI1;
MGMAE:LAI=228-12-1202,RNC=HKI1;

3.3.3 Deletion of Location Areas

Delete the definition of LAIs 228-12-1200, 228-12-1201, and 228-12-1202.

MGLAE:LAI=228-12-1200;
MGLAE:LAI=228-12-1201;
MGLAE:LAI=228-12-1202;

3.3.4 Deletion of RNC

Delete RNC with identity HKI1.

MGRIE:RNC=HKI1;

3.3.5 Disconnection of Seizure Supervision

Disconnect seizure supervision from outgoing traffic route OCIT4 and incoming traffic
route ICIT4.

SETRE:R=OCIT4&ICIT4;

3.3.6 Removing of Outgoing and Incoming Traffic Routes

Remove the affiliated traffic routes OCIT4 and ICIT4.

EXROE:R=OCIT4&ICIT4;
4 Glossary
ATM Asynchronous Transfer Mode
GLCNID Global Core Network Identity Capability
IP Internet Protocol
LAI Location Area Identity
MSC Mobile Services Switching Centre
RNC Radio Network Controller
SCCP Signalling Connection Control Part
TB Transport Bearer
UMTS Universal Mobile Telecommunication System
VLR Visitor Location Register

5 References

5.1 Operational Instructions

Data Record Route, Connect

Data Record Route, Disconnect
Mobile Telephony, Location Area, Define
Mobile Telephony, Location Area, Delete
Mobile Telephony, RNC, Change
Mobile Telephony, RNC, Connect
Mobile Telephony, RNC, Disconnect
Mobile Telephony, UMTS Paging Area, Define
Mobile Telephony, UMTS Paging Area, Delete
Route Data, Change
Seizure Supervision of Trunks and IWU, Change

5.2 Command Descriptions

EXRBC Exchange Data, Specification of Route Data, Change
EXROE Exchange Data, Connection of Route, End
EXROI Exchange Data, Connection of Route, Initiate
MGLAE Mobile Telephony, Location Area, End
MGLAI Mobile Telephony, Location Area, Initiate
MGMAE Mobile Telephony, UMTS Paging Area, End
MGMAI Mobile Telephony, UMTS Paging Area, Initiate
MGRIC Mobile Telephony, Radio Network Controller, Change
MGRIE Mobile Telephony, Radio Network Controller, End
MGRII Mobile Telephony, Radio Network Controller, Initiate
SETIR Seizure Supervision on Devices, Inhibition, Reset
SETRE Seizure Supervision on Devices, End

5.3 Application Information

MUIUCM