Cellular Radio Network Management PDF

Nokia Siemens Networks DX MSC / MSS / DX
HLR, Rel. M14.3, Product Documentation, v. 3
Cellular Radio Network

Management
DN9797631 # Nokia Siemens Networks 1 (91)

Issue 8-1 en
Cellular Radio Network Management
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted in
any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given “as is” and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT
NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners,
and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2009. All rights reserved.
2 (91) # Nokia Siemens Networks DN9797631

Issue 8-1 en
Contents
Contents
Contents 3
List of tables 6
List of figures 7
Summary of changes 9
1 Cellular radio network management 11

1.1 Cellular radio network concepts 12
1.2 GSM/UMTS radio networks 17
1.3 MSC/MSS cellular radio network configuration 23
2 Location area handling 27

2.1 Logical grouping of own/auxiliary location area parameters 28
2.2 Logical grouping of network location area parameters 31
3 BSC handling 33
3.1 Logical grouping of BSC parameters 33
4 RNC handling in MSS 37

4.1 Logical grouping of RNC parameters in MSS concept 38
5 BTS and service area handling 41

5.1 Logical grouping of BTS/service area parameters 41
6 NRI and pool area configuration handling 45

6.1 Logical grouping of NRI and pool area parameters 46
7 General RNW Parameter Handling in MSS 49

7.1 Logical grouping of general RNW parameters 49
8 Creating a cellular radio network 51

8.1 Creating location areas 51
8.1.1 Creating own location area 51
8.1.2 Creating auxiliary location area 52
8.1.3 Adding network location area 52
8.2 Creating BSC 53
8.3 Defining routes for BSC 54
8.4 Defining signalling system information for BSC 55
8.5 Defining supported mode sets of BSCs 56
8.6 Creating RNCs 56
8.6.1 Creating own RNC 56
8.6.2 Creating auxiliary RNC 58
8.7 Creating BTS/service area and defining LA - BTS - BSC and LA - service
area - MGW relations 60
8.8 Sequence for creating a cellular radio network 63
8.9 Creating SGSN connections 64

Issue 8-1 en
8.10 Creating zone codes 65

8.11 Creating NRI and pool area 66
9 Optimizing a cellular radio network 67

9.1 Modifying location area parameters 67
9.1.1 Modifying own location area parameters 67
9.1.2 Modifying auxiliary location area parameters 68
9.1.3 Modifying network location area parameters 68
9.2 Deleting location areas 69
9.2.1 Deleting own location area 69
9.2.2 Deleting auxiliary location area 69
9.2.3 Deleting network location area 70
9.3 Modifying BSC parameters 70
9.3.1 Changing cell identification method 71
9.3.2 Changing paging method 72
9.3.3 Changing channel priority assignment function mode 72
9.3.4 Changing reverse circuit allocation function mode 73
9.3.5 Modifying BSSAP version, version name, version information, and output
BSSAP version data 73
9.4 Deleting BSC/MGW R99 74
9.5 Modifying RNCs 75
9.5.1 Modifying own RNC 75
9.5.2 Modifying auxiliary RNC 76
9.5.3 Modifying RNC version data 77
9.6 Deleting RNCs 77
9.6.1 Deleting own RNC 77
9.6.2 Deleting auxiliary RNC 78
9.7 Handling AMR mode sets 78
9.7.1 Modifying mode sets for AMR codecs 78
9.8 Modifying BTS/service area 79
9.8.1 Modifying BTS/service area parameters 79
9.8.2 Modifying traffic reason handover 80
9.8.3 Modifying resource indication 80
9.8.4 Modifying BTS neighborhood 80
9.9 Deleting BTS/service area 81
9.10 Modifying NRI and pool area configuration 81
9.10.1 Modify pool area 82
9.10.2 Delete pool area 82
9.10.3 Add MSS in pool area 82
9.10.4 Modify MSS in pool area 82
9.10.5 Remove MSS from pool area 83
9.10.6 Modify neighbor pool area 83
9.10.7 Delete neighbor pool area 83
9.10.8 Modify MSS in neighbor pool area 83
9.10.9 Remove MSS from neighbor pool area 84
9.11 Sequence in deleting a radio network 84
9.12 Transferring BSCs between MSCs/MSSs 85
9.13 Creating LA, network LA, and BSC 86
9.14 Creating BTS and LA-BTS-BSC relation 87
9.15 Changing old MSC/MSS configuration 87
9.16 Changing BSC configuration 88
9.17 Making BSC and BTS operational 88

Issue 8-1 en
Contents
9.18 Removing duplicate configurations from old MSC/MSS 88

9.19 Handling SGSN connections 89
9.19.1 Modifying SGSN parameters 89
9.19.2 Deleting SGSN connections 90
9.20 Handling zone codes 90
9.20.1 Modifying zone code 90
9.20.2 Deleting zone code 90

Issue 8-1 en
List of tables
Table 1. Maximum radio network configuration in the MSC/MSS 25

Table 2. Administrative numbering for radio network objects 25

Issue 8-1 en
List of figures
List of figures
Figure 1. Cells 12
Figure 2. Location area–service area relation 13
Figure 3. Location areas 14
Figure 4. MSC/VLR area 15
Figure 5. Pool area 1 16
Figure 6. Pool area 2 16
Figure 7. PLMNs 17
Figure 8. GSM/3G radio network elements 18
Figure 9. MOCN reference architecture 22
Figure 10. Gs interface between MSC and SGSN 64
Figure 11. Transferring BSCs between MSCs/MSSs 86

Issue 8-1 en

Issue 8-1 en
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest

document issue contains all changes made to previous issues.
Changes made between issues 8–1 and 8–0
Feature references have been corrected according to the approved

feature names.
. The E9, General RNW Parameter Handling in MSS MML command

group has been introduced.
. The E2P and E2O commands have been removed.
.
Multi-Operator Core Network (MOCN) overview has been added to
the Section GSM/UMTS radio networks.
.
New Multipoint A/Iu related parameters for configuring enhanced
redistribution functionality of UEs have been introduced.
.
The E3P command for deleting pool area configuration has been
introduced.
. The maximum number of BSCs in maximum radio network
configuration has been increased.
. The following sections have been added to the document:
.
General RNW parameter handling in MSS
. Handling AMR mode sets
.
The following subsections have been added to the document:
. Defining supported mode sets of BSCs
.
Delete pool area

Issue 8-1 en
. The following subsection has been removed:

. Modifying mode sets for AMR codecs
. New parameters have been added to the following subsection:
.
Logical grouping of own/auxiliary location area parameters
. Logical grouping of network location area parameters
.
Logical grouping of BSC parameters
. Logical grouping of RNC parameters in MSS concept
.
Logical grouping of NRI and pool area parameters
Information on Unlicensed Mobile Access (UMA) has been removed as it

is no longer supported.

Issue 8-1 en
Cellular radio network management
1 Cellular radio network management

Cellular radio network management allows you to manage the network
configuration in the Mobile Services Switching Centre/MSC Server (MSC/
MSS) using an MML interface. You can do the following:
.
Create and delete the following radio network configuration
elements: location area (LA), Base Station Controller (BSC), Base
Transceiver Station (BTS), Radio Network Controller (RNC), and the
service area,
. Modify the parameters of the radio network configuration elements,
.
Handle the administrative states for the BSC, BTS, RNC, and the
service area,
.
Define the relationships between the radio network configuration
elements,
.
Output the data of radio network configuration elements and the
relationships of the radio network configuration elements,
. Initialize the interfaces between the MSC–BSC, and the MSC–RNC
(Global Restart procedure).
The main functions of the cellular radio network management are:
. Handling location areas under the MSC/MSS (GSM and Universal

Mobile Telecommunications System (UMTS)) with the EL Command
Group,
. Handling network location areas (GSM and UMTS) with the EI
Command Group,
. Handling BSCs with the ED Command Group,
.
Handling the BTS cells (GSM), the service area (UMTS) and the
auxiliary service area (UMTS) with the EP Command Group,
. Handling RNCs (UMTS) with the E2 Command Group,
. Handling general RNW parameters with the E9 Command Group,

Issue 8-1 en
. NRI and pool area configuration handling with the E3 Command

Group,
. Handling roaming areas (zone codes) (GSM and UMTS) with the EK
Command Group,
. Handling the Gs-interface (an interface between the MSC and the
Serving GPRS Support Node (SGSN)) definitions (GSM) with the EJ
Command Group.
1.1 Cellular radio network concepts

The following are descriptions of some of the basic concepts related to the
cellular radio networks.
Cellular radio network
A cellular radio network of an MSC/MSS is a geographical area where the

MSC/MSS provides GSM or UMTS radio access.
Cell
Cells are the basic units in a GSM cellular radio network. A cell is a
geographical area that is covered by a transceiver. A base transceiver
station (BTS) network element generally controls several cells. In cellular
radio network configuration management in the MSS, the term "BTS" is
considered one cell.
Figure 1. Cells

Issue 8-1 en
Service area
Service areas are the basic units of a UMTS cellular radio network. A
service area is a geographical area covering one or more UMTS cells.
UMTS cells are not defined in the cellular radio network configuration of
the MSS. Service areas connected to an MSS through MGW Rel-4 have
an LA-service area relation.
LA 2
SA
SA77
LA 1
SA 2
SA 1
LA 3
SA 3
SA 5
SA 4
SA 6
Figure 2. Location area–service area relation
Location area
A location area (LA) consists of one or more adjacent cells in a GSM

network, or one or more service areas in a UMTS network. User
equipment/mobile stations can roam inside an LA without having to
perform location updates. LAs in GSM and UMTS networks have the same
parameters.

Issue 8-1 en
Note
If either one of Features 1449 or 1564 is activated, then the Location

Areas for UMTS/GSM must be defined separately. If both Features
1449 and 1564 are activated, this is not needed. You can check the
LA's UMTS/GSM access with the ELL command.
LA9
LA6 LA5
LA1 LA2
LA4 LA8
LA7
LA3
Figure 3. Location areas
A network can include its own LAs, network LAs (addresses of LAs
controlled by other MSC/MSSs), and auxiliary LAs (in UMTS networks
only).
UMTS/GSM access
In the multipoint Iu/A concept, you need to be able to determine whether

your system has UMTS/GSM access.
Even though a Location Area can include both GSM cells and UMTS
service areas, it is recommended that Location Areas would be defined
and used separately for the UMTS and the GSM, so that a single LA would
only have either UMTS service areas or GSM cells connected to it.
MSC/VLR area
The network's own LAs, belonging to the same MSC, form an MSC/VLR
area. An MSC/VLR area can consist of one or more LAs, the size of which
is decided in network planning. The trade-off in the LA size is that small
LAs require more location updates from user equipment/mobile stations,
which means an increased signalling load. Large LAs require more paging
procedures, which means an increased load on the BSS/RNS air
interface.

Issue 8-1 en
LA9
LA7 LA3
LA4 LA5
LA2 MSC/VLR LA1
LA8
LA6
Figure 4. MSC/VLR area
Pool area
A pool area corresponds closely to an MSC/MSS service area. The main

difference is that a pool area is served by multiple MSCs/MSSs
simultaneously. The radio network configuration concerning the pool area
must be identical in every MSS controlling the pool area. The traffic is
shared between the MSSs within the pool area and a mobile station can
roam within the pool area without having to change the serving MSS.
Another difference between a pool area and a service area is that pool
areas may overlap, whereas service areas cannot.

Issue 8-1 en
LA12
LA3 LA6
LA1 LA9 LA8
MSC/VLR 1
LA4 MSC/VLR
LA52 MSC/VLR 3 LA10
LA11 LA2
LA7
Figure 5. Pool area 1
Pool area 2
LAn
LAn LAn
Overlap
LA1
LAn LAn LAn
LAn LAn LAn
Pool area 1 LA1 LAn Overlap
LAn LAn LAn
LAn LAn LAn
LA1
Overlap
LAn LAn
LAn
Pool area 3
Figure 6. Pool area 2

Issue 8-1 en
PLMN
The MSC/VLR areas in the GSM/UMTS networks form a Public Land

Mobile Network (PLMN). One PLMN can be defined for each LA. An LA
can belong to only one PLMN.
PLMN1
LA1
PLMN2 LA2
LA3
PLMN3
LA4
Figure 7. PLMNs
For further details, see Cellular radio network management overview.
1.2 GSM/UMTS radio networks

The MSS concept supports separate handling of the control plane (CP)
and the user plane (UP) traffic with the MGW Rel-4. (For more information,
see User plane routing, Operating Instructions.)
With system level M13, the multipoint Iu/A concept is introduced. In earlier
radio network concepts a BSS/RAN (Radio Access Network) is connected
to one MSS, but with multipoint Iu/A concept, a RAN/BSS node can be
connected to several MSSs. For more information on this concept, see
Sections Pool area and Multipoint network.
GSM/UMTS 3G radio network elements
A GSM radio network consists of a Network Subsystem (NSS) and a Base

Station Subsystem (BSS), while a 3G radio network consists of an NSS
and a Radio Network Subsystem (RNS).

Issue 8-1 en
BSS and RNS NSS

GSM BS BSC MSC/MSS
HLR
A
Navigator
GSM mobile
A lu
PSTN/
ISDN/
Navigator
A
IP
GSM mobile IN Service
GSM BS BSC MGW
Control Point
R4
lu
UMTS mobile
UMTS BS RNC
Figure 8. GSM/3G radio network elements
Network Subsystem
The NSS contains the MSS, which serves the BSS and the RNS under
them.
According to the 3GPP standardized Bearer Independent Circuit Switched

Core Network concept (Rel-4), the control plane (CP) and the user plane
(UP) were separated with the introduction of MGW Rel-4 at system level
M12. At this stage, the MSC functionality was split into two distinct logical
entities. The MSS handles the CP (call control, mobility control, and MGW
control) and the MGW Rel-4 handles the UP connections.
The Home Location Register (HLR) supports 2G, 3G and dual-mode

subscribers.
The Visitor Location Register (VLR) stores the mobile subscriber

information of those currently using the network controlled by the MSS.
Base Station Subsystem (GSM)
The BSS consists of a BSC, a transcoder (TC), and BTSs.

Issue 8-1 en
The Base Station Controllers (BSCs) are defined to the radio network
configuration of the MSC/MSS. Normally one BSC controls several Base
Transceiver Stations (BTSs). A BTS realises the radio interface towards
the mobile stations. One BTS network element can have several cells. In
the MSC/MSS radio network configuration management, the term "BTS" is
considered one cell. Therefore, all the cells of a BTS network element
have to be defined in the MSC/MSS, but not in the physical BTS network
element.
The TC converts coded speech to 64 kbit/s PCM format and vice versa.
The TC is a logical part of the BSC.
Radio Network Subsystem (UMTS)
The Radio Network Substystem (RNS) consists of an RNC and of

WCDMA base stations.
In the MSS concept, the RNCs are defined in the radio network
configuration (with an RNC-specific MML) as network elements.
The MSS concept can have two kinds of RNCs in the radio network
configuration: RNCs that belong to the MSS's own radio network; and
RNCs that belong to an auxiliary radio network of the MSS.
The base stations, or cells, of the RNS are not defined in the radio network
configuration of the MSC/MSS.
Multipoint network
In the earlier radio network concept, a RAN/BSS is normally connected to

one MSS, but the introduction of the multipoint concept now enables a
RAN/BSS node to be connected to several MSSs simultaneously. The
serving area of MSSs is called a pool area and the group of MSSs is called
an MSS pool.
At the beginning of the transaction, the RAN/BSS node selects the MSS to
which the signalling messages are routed. The selection is based on the
Network Resource Identifier (NRI), which is allocated in an MSS/VLR. If no
MSSs are configured for the NRI indicated by the mobile, the RAN/BSS
mode selects one of the MSSs in the MSS pool, while at the same time
taking into account the load balancing between the MSSs in the pool. The
MSSs within one pool area and in the overlapping neighboring pool areas
must have unique NRIs.

Issue 8-1 en
Using multiple MSSs/MSCs within a pool area increases service

availability as other MSSs/MSCs are still able to provide services even if
one MSS/MSC within a pool area fails. It also enlarges the served area
compared to the service area of a single MSS/MSC. This results in
reduced inter-MSC/MSS location updates and handovers while also
reducing the HLR update traffic.
Furthermore, overlapping pool areas allow the separation of the overall

traffic into different mobile station moving patterns. For example, each pool
area can cover a separate residential area while all overlapping pool areas
can cover the city centre.
Another significant advantage of the multiple MSS/MSCs in a pool area is

the possibility of capacity upgrades by additional MSSs/MSCs in the pool
area. A multipoint network can consist of up to 10 parallel MSSs/MSCs
and of up to 20 neighboring pool areas.
For more information, see CS Core Multipoint Configuration Guidelines,

CS Core System Documentation.
Auxiliary networks
An auxiliary network is part of a UMTS radio network that belongs to a

neighboring MSC/MSS. The auxiliary radio network definitions contain
auxiliary location areas, auxiliary service areas and auxiliary RNCs.
Auxiliary radio network definitions may be needed for the "Flexible Iu
interface for handover/relocation" concept or for the "Iur- interface between
RNCs of different MSC" concept. The use of auxiliary network requires
Feature 1260: Inter-System Handover and UMTS Changes and/or Feature
1325: RANAP and BSSAP in MSC Server.
An auxiliary location area and auxiliary RNC definitions are required for the
"Flexible Iu interface for handover/relocation" concept. The purpose of this
concept is to avoid inter-MSS relocations and thereby to reduce the inter-
MSS signalling load. The MSS controls relocations from its own radio
network to an auxiliary radio network and also inside an auxiliary network.
In the "Flexible Iu interface for handover/relocation" concept, the RNC is
defined in two MSSs: as its own RNC in one MSS, and as an auxiliary
RNC in the other MSS, in which also the location areas are defined
correspondingly. An RNC can be connected to both MSSs through an Iu-
interface. If a user equipment starts a transaction from an area controlled
by an RNC connected to two MSSs, the transaction is always directed
towards the own MSS. From the MSS point of view, a transaction can not
be started from an auxiliary network, nor paging performed towards an
auxiliary network either.

Issue 8-1 en
The auxiliary location area and the auxiliary service area definitions are
required for the "Iur- interface between RNCs of different MSC" concept as
well. It is possible that the mobile station starts the transaction from the
radio network of the neighboring MSC/MSS and the signalling is routed to
the MSC/MSS because of the Iur- interface between the RNCs. The
location area and the service area are defined to the MSC/MSS, otherwise
transaction is rejected. Normally, when serving an RNC relocation
procedure is supported, it is enough to define the border areas of the
neighboring MSC/MSS as auxiliary network. It is possible to reduce the
amount of auxiliary networks by defining the auxiliary location area related
to "default service area", which can be used instead of the real service
area received from Iu/A'- interface. Using an auxiliary location area related
to the default service area requires that the auxiliary location area is
defined in the MSC/MSS.
Note that in this concept, auxiliary RNCs do not need to be configured.
Another possibility to reduce the amount of auxiliary radio networks is to

use the MSC/MSS-related default location area and service area pair. The
location area code (LAC) value 65533 and the service area code (SAC)
value 65534 are reserved for this special use. If the MSC/MSS receives an
unknown service area identification (SAI), and the MSC/MSS-related
default location area and service area are defined in the own radio network
definitions, then they are used (instead of the SAI received from Iu/A'-
interface) in further call processing. The MSC/MSS-related default LAC
and default SAC values are not recommended to be used in normal radio
network configuration.
When the auxiliary location area or the MSC-related default definitions are
used, the accuracy of the mobile station's real location (in service area
level) is lost.
Multi-Operator Core Networks (MOCN)
Network sharing architectures allow different core network operators to

connect to a shared radio access network. The operators do not only
share the radio network elements, but may also share the radio resources
themselves. In addition to this shared radio access network, the operators
may have additional dedicated radio access networks, for example, 2G
radio access networks. The MOCN architecture for network sharing is
defined in 3GPP TS 23.251 Network sharing; Architecture and functional
description.

Issue 8-1 en
In the figure below, a MOCN reference architecture is illustrated. In the

figure, CN operators A, B and C together share the radio access network
for 3G. Each operator may also have their dedicated radio access
networks, for example, for 2G. This does not obsolete the fact that each
operator may have the Multipoint Iu feature activated in their own networks
simultaneously.
CN CN CN
.......... Operator A Operator B Operator C ..........
Iu
RNC
Radio Access Netvork

Operator x
Figure 9. MOCN reference architecture
In a shared network, a core network operator is identified by a PLMN-id

(MCC+MNC). Each cell in the shared radio access network shall include
information concerning the available core network operators into the
broadcast system information. The available core network operators have
to be the same for all the cells of a Location Area in the shared network.
The MOCN as such does not require any support from the UE, however, it
is possible that the UE supports the core network operator selection
process. The functionality for the MOCN is specified separately for
network sharing supporting UEs and non-supporting UEs. The majority of
UEs, that is, the pre Rel-6 UEs do not support the network sharing
currently, thus the network support for non-supporting UEs is necessary.
The Nokia Siemens Networks MOCN implementation targets to support
both supporting and non-supporting UEs for network sharing.
The MOCN configuration requires Feature 1325: RANAP and BSSAP in

MSC Server with the optional Multiple PLMN Support for RNC Node in
MSS functionality and Feature 1847: Multi-Operator Core Network Support
in MSS to be activated in the MSS.

Issue 8-1 en
1.3 MSC/MSS cellular radio network configuration

The radio network configuration in the MSC/MSS allows you to:
. Control (block and unblock) traffic from/to BSCs, RNCs, BTSs

(cells), and service areas.
. Handle location updating. The location of a user equipment/mobile
station is given in the LAI stored in the MSC/VLR.
. Handle paging. In a mobile terminated call, the user equipment/
mobile station is paged from a particular location area. To page the
user equipment/mobile station through the correct BSC and RNC,
the MSC/MSS has to know the location area relation of these
network elements.
. Handle Control Network Resource Identifier (NRI) and pool area
configuration. The NRI and the Pool Area Configuration Handling
are used for managing NRI information in MSS or for exporting/
importing network pool area configuration in MSS.
. Create pool areas in your switching centre.
. Control various types of handovers/relocations:
. In an inter-BSC handover, the target BSC is derived from cell
information in the target cell list.
. In an inter-MSC handover, the relocation target MSC is
derived from location area information in the target cell list.
.
In an inter-system handover (GSM to UMTS), the target RNC
identification is derived from the source BSC.
.
In an UMTS to UMTS handover, the target RNC identification
is derived from the source RNC.
The following lists what needs to be defined in the radio network

configuration of the MSC/MSS for GSM access:
. Location areas under its own control (own location areas),

. BSCs under its own control,
. BTSs (cells) under its own control,
.
LA–BTS–BSC relation,
. BTS (cell) relation between the location area and the BSC, and
.
Location areas controlled by other MSC/MSSs in the network
(network location areas).

Issue 8-1 en
The following lists what needs to be defined in the radio network

configuration for multipoint concept (optional):
. If you are using the multipoint concept (optional), these definitions

are mandatory:
. NRIs and pool areas to be used
.
Parameters needed within the pool area
. All neighboring MSSs outside the pool area
.
The location areas which will be included in the pool concept
. The network location areas which will be included in the pool
concept
. For redistribution of UEs in A/Iu-multipoint configuration from a MSS
in a controlled way, the MSS can be put into maintenance mode. For
this you have to define following:
. Maintenance NRI (Null NRI)
.
Non-broadcast location area identity (LAI)
. For enhanced redistribution functionality of UEs the following
optional parameters can be defined:
. Parallel MSS maintenance NRI list (PNRI).
.
NRI validity check (NRIVALC).
. VLR stop level for redistribution (STOPLEV).
. Redistribution of active call timer (TIMER).
. Parallel MSS maintenance NRI list (PNRI).
. NRI weight factor (WF).
Note
Before you start creating your multipoint solution, make sure you have
planned the work carefully beforehand. Using the IMPORT/EXPORT/
ACTIVATE commands below is worth considering especially if you are
dealing with a large configuration in your network. The issues to
consider beforehand include, for example, planning on how to
implement the following in the whole configuration:
.
Marking the LA's to be copied (with the ELT command for the own
LA's and the EIT command for the network LA's).
.
Exporting of LA's (with the E3X command) from a Radio Network,
. Importing of LA's (with the E3Y command) to a Radio Network,
.
Activating of LA's in the Radio Network (with the E3V command).

Issue 8-1 en
You need to remember that the information must be absolutely identical

in your pool area configuration within a multipoint concept.
You should be aware that using these commands will not make the
procedure completely automatic (manual work is still needed), but it will
nonetheless decrease the amount of the manual work needed, as well
as make the manual work more easy to perform.
Any combination of the above radio access types are simultaneously

possible in an MSC/MSS.
Maximum radio network configuration in the MSC/MSS
The following table shows the maximum configuration in the MSC/MSS for
each radio network object.
Table 1. Maximum radio network configuration in the MSC/MSS
Object Limit
Own LA 1000/5000*
Network LA 2000/20000*
BSC 150/500*
BTS (cell)/service area/auxiliary service areas 5000/ 8000/ 10000/ 50000*
Own RNC 150/1500*
Auxiliary RNC 150
Auxiliary LA 2000
MSCs/MSSs in a pool 10
neighboring pools in a network 20
* = depending on switch type and optionalities
Administrative numbering of network objects
The following table shows the permissible number range for each radio
network object.
Table 2. Administrative numbering for radio network objects
Object Number range

BSC 1 – 4095

Issue 8-1 en
Table 2. Administrative numbering for radio network objects (cont.)
Object Number range

RNC ID 1 – 4095
LA 1 – 65533
BTS (cell)/ service area 1 – 65535
Note
Please note, that the location area code 65533 and the service area
code 65534 should not be used as normally in own radio network
configuration, because they have special role in the auxiliary radio
network concept.
For further details see Section Cellular Radio Network Management

Overview.

Issue 8-1 en
Location area handling
2 Location area handling

Managing location areas involves creating and deleting location areas,
and modifying location area parameters in the MSC/MSS cellular radio
network configuration files.
You can create and update own and auxiliary location area-specific data of
the MSC/MSS with the EL Command Group. For more information on the
EL commands, see Location Area Handling, EL Command Group.
Own location areas are used in GSM and UMTS. You can handle own
location area-specific data with the following commands:
.
ELC – create location area
. ELP – modify re-paging parameters
.
ELH – modify channel assignment priorities <option>
. ELR – modify national roaming parameters <option>
.
ELE – modify location area parameters <option>
. ELL – analyze location area <option>
. ELT – set location area for pool concept <option>
. ELD – delete location area
. ELO – output location area data <option>
The commands for handling the auxiliary location area-specific data are
optional and are only used in the MSS concept (UMTS). For more
information, see the Auxiliary networks in GSM/UMTS radio networks.
You can handle the auxiliary location area-specific data with the following
commands:
. ELS – create auxiliary location area <option>

.
ELM – modify auxiliary location area data <option>

Issue 8-1 en
. ELG – delete auxiliary location area <option>

. ELJ – output auxiliary location area data <option>
Network location areas are used in GSM and UMTS. You can handle the
network location area-specific data with the EI Command Group.
The commands are:
.
EIA – add location area to network
. EIR – remove location area from network
.
EIM – modify location area parameters
. EIO – output network location area data
.
EIT – set network location area for pool concept <option>.
2.1 Logical grouping of own/auxiliary location area

parameters
Parameters relating to own/auxiliary location areas can be divided into the
following logical groups:
1. Location area identification

. (NAME) location area name
. (LAC) location area code
. (MCC) mobile country code <option>
.
(MNC) mobile network code <option>
MCC and MNC are optional and require the Feature 1168:
Multiple PLMN and Inter-PLMN Handover Support.
If the MCC and MNC are not given in the MML command, the
primary MCC and MNC values of the MSC/MSS are used. The
primary values are defined with the WV Command Group.
2. Reference location area identification
. (RNAME) reference location area name
. (RLAC) reference location area code
. (ILS) identical location area code switch
3. Radio channel assignment priority
.
(OR) ordinary channel assignment priority
. (HO) handover channel assignment priority

Issue 8-1 en
. (RE) re-establishment channel assignment priority

. (EM) emergency channel assignment priority
If the A-interface Priority Information Control is used, then the
ELH command and the radio channel assignment priority
parameters are not available. See related channel priority
assignment parameter in Logical grouping of BSC/MGW R99
parameters.
4. Paging
. (AT) repaging attempts
.
(INT) repaging interval timer 1
. (INT2) repaging interval timer 2 <option>
. (INT3) repaging interval timer 3 <option>
. (FAT) FSM repaging attempts (Forward SM repaiging)
<option>
.
(FINT) FSM repaging interval timer 1 <option>
. (FINT2) FSM repaging interval timer 2 <option>
.
(FINT3) FSM repaging interval timer 3 <option>
. (PAT) PSI repaging attempts (Provide Subscriber Information
repaiging) <option>
. (PINT) PSI repaging interval timer 1 <option>
. (PINT2) PSI repaging interval timer 2 <option>
. (PINT3) PSI repaging interval timer 3 <option>
5. Roaming
.
(RNGP) mobile station roaming number group <option>
You need to define the group with the WVC command before
you can give RNGP <option>.
. (MNC) allowed MNC in national roaming
(Used for own location areas.)
. (AMNC) add allowed MNC in national roaming <option>
(Used for auxiliary location areas.)
. (RMNC) remove allowed MNC in national roaming <option>
(Used for auxiliary location areas.)
6. Miscellaneous
. (DASAC) default auxiliary service area code <option>
This parameter is related to UMTS and the MSC Server
concept.
You need to define the auxiliary service area with the EPC
command before you can give SAC. See the BTS object
number parameter in Logical grouping of BTS/service area
parameters.

Issue 8-1 en
This parameter is only usable for auxiliary LAs.

. When using the ELT command, you can determine whether
you are using the LA or the auxiliary LA by giving the
parameter name TYPE. The "LA" is the default value and the
"AUXLA" is the optional one.
.
With the INC parameter you can identify whether the location
area is set in the pool concept or not. The values for this
parameter are "Y” for “yes, include in the pool concept” and “N”
for “no, do not include in the pool concept”.
.
(DSAV) daylight saving <option> and (TZ) time zone
. (VMSC) virtual MSC address index <option> and (VVLR)
virtual VLR address index.
The VMSC and VVLR addresses are handled with the WV
command group.
For more information about this command group, see GSM
Network and Network Element Specific Number Handling, WV
Command Group.
. (HYPO) hypo-lac paging <option>
.
(PPREV) paging prevention <option>
. (HONLA) handover number range index for LA <option>
The handover number ranges are handled with the WV
command group.
For more information about this command group, see GSM
Network and Network Element Specific Number Handling, WV
Command Group.
.
(EQPLMN) equivalent PLMN index for LA <option>
The equivalent PLMNs are handled with the MX command
group.
For more information about the commands of this command
group, see VLR and PLMN Parameter Handling, MX
Command Group.
. (ISP) intelligent selective paging <option>
7. Output
. (RT) relation type
With this parameter you can define how detailed the output
relational information will be.
.
(INCSEL) include in pool concept selector <option>
With this parameter you can limit the output to LAs that are
included in Multipoint pool concept only.

Issue 8-1 en
Note
The default for RT has changed from ALL to NONE. This change is due
to the fact that depending on the maximum configuration, the printout
can become a very large one.
You can use the ELO and the ELJ commands to arrange the information
you wish to print out.
2.2 Logical grouping of network location area

parameters
The parameters relating to network location areas can be divided into the
1. Location area identification

. (LAC) location area code
.
(MCC) mobile country code <option>
. (MNC) mobile network code <option>
2. Reference location area identification
. (RNAME) reference location area name
. (RLAC) reference location area code
.
(ILS) identical location area code switch
If you give a reference location area, you cannot give the MSC/VLR
address group parameters because their values are copied.
3. MSC/VLR address
Note
If you are using the NPAI parameter to define the relation of your
network location area and the neighbor pool area, the MSC/VLR
addresses must be defined with the E3L MML command.
. (MISDN) MSC ISDN number

. (MNA) nature of MSC address
.
(MSNC) MSC signalling network code
. (MSPC) MSC signalling point code
.
(VISDN) VLR ISDN number
. (VNA) nature of VLR address

Issue 8-1 en
. (VSNC) VLR signalling network code

. (VSPC) VLR signalling point code
4. Miscellaneous
.
(VLRS) VLR inquiry allowed
. (TRA) call tracing allowed
.
(IMSC) inter-MSC handover allowed
. (CID) cell identification method
.
(VER) BSSAP version
This is a GSM parameter. Version information can be modified
with the ED command group.
. (NPAI) Neighbor pool area index <option>
5. Change PLMN
This parameter group requires the Feature 1168: Multiple PLMN and
Inter-PLMN Handover Support.
.
(NMCC) new mobile country code <option>
. (NMNC) new mobile network code <option>
6. Output
. location area code
.
(MCC) mobile country code <option>
. (INCSEL) include in pool concept selector <option>
With this parameter you can limit the output to LAs that are
included in Multipoint pool concept only.
For further information, see Logical grouping of own/auxiliary location area

parameters.

Issue 8-1 en
BSC handling
3 BSC handling
You can handle the BSC parameters with the ED Command Group. For
more information, see Cellular Network Controller Handling, ED Command
Group.
With this command group you can create and delete a BSC, modify BSC
parameters, and output BSC related data.
You can also use it to output and remove MGW R99 from the MSS. No
new MGW R99 configuration can be created, because the MGW R99
network is no longer supported.
3.1 Logical grouping of BSC parameters

Parameters relating to BSC can be divided into the following logical
groups:
1. BSC identification
. (TYPE) object type
. (NAME) object name
. (NO) object number
2. Reference BSC identification
.
(RNAME) reference object name
. (RNO) reference object number
If you give a reference object, the following reference object
parameter values are copied:
.
BSSAP subsystem number <option>
. cell identification method
. paging method
. BSSAP version
. channel priority assignment function mode
.
reversed circuit allocation function mode <option>

Issue 8-1 en
If you do not give a reference object, the default values for the above
parameters are used.
3. State handling
.
administrative state
4. UP resources
.
pool number
. route number
.
pool TFO capability <option>
5. CP resources
.
(SNC) signalling network code
. (SPC) signalling point code
. (SSN) BSSAP subsystem number <option>
6. Miscellaneous
. cell identification method
CGI, CLI or CI for BSC
. paging method
CGI, CLI, LAI, LAC or ALL for BSC
. channel priority assignment function mode
.
circuit allocation by BSS
7. BSSAP version
a. Version identification
. (VER) BSSAP version
. (VERNAME) name of BSSAP version
b. Version related functionality
. parameter type
.
parameter index
. parameter value
8. AMR modes
. Full Rate AMR narrowband mode set id <option>
.
Half Rate AMR narrowband mode set id <option>
. Full Rate AMR wideband mode set id <option>
The mode sets are handled with the commands of the General RNW
Parameter Handling, E9 Command Group.
9. Output BSC data
.
pool view mode
10. Output BSSAP data

Issue 8-1 en
BSC handling
. (TYPE) object type

. (NO) object number
.
information group
This parameters allows you to choose the type of information
you will view.
(FUN, TIM, PAR, BSC, NLA or ALL)
For further information, see Cellular radio network management overview.

Issue 8-1 en

Issue 8-1 en
RNC handling in MSS
4 RNC handling in MSS

You can use the commands of the E2 command group in MSS to manage
the RNCs under your MSS. For more information, see Radio Network
Controller Parameter Handling, E2 Command Group.
From the point of view of Radio Network Controller Parameter Handling

MML, an auxiliary radio network is controlled by a neighbor MSS and used
by an own MSS for relocations. Therefore, an own MSS needs to know the
auxiliary network's configuration.
With the auxiliary radio network commands of this command group you
can handle an auxiliary RNC in an own MSS.
State changes of RNCs in an auxiliary radio network only apply to an own

MSS.
The following commands are for handling own RNCs:
.
E2C – create RNC to own radio network
. E2M – modify RNC in own radio network
. E2D – delete RNC from own radio network
. E2S – change RNC state in own radio network
. E2I – interrogate RNC in own radio network
. E2R – restart RNC in own radio network
The following commands are for handling auxiliary RNCs:
.
E2E– create RNC in auxiliary radio network
. E2F – modify RNC in auxiliary radio network
.
E2G – delete RNC from auxiliary radio network
. E2K – change RNC state in auxiliary radio network

Issue 8-1 en
. E2H – interrogate RNC in auxiliary radio network

. E2T – restart RNC in auxiliary radio network
The following commands are for handling RANAP parameters:
.
E2N – modify RNC version specific information
. E2J – interrogate RNC version specific information
The following command is for listing user plane destinations:
. E2L – list user plane destinations
Note
All commands that are not mandatory require the Feature 1325:
RANAP and BSSAP in MSC Server.
4.1 Logical grouping of RNC parameters in MSS

concept
Parameters for handling RNCs in the MSS concept can be divided into the
1. RNC identification
. (RNCID) radio network controller identification
.
(MNC) mobile network code <option>
. (RNCNAME) radio network controller name
.
(NNAME) new radio network controller name
. (UPD) index of a user plane destination (for interrogation only)
.
(NUPD) name of a user plane destination (for interrogation
only)
2. Miscellaneous
. (TOA) type of address
. (UPD) user plane destination index
.
(NUPD) user plane destination name
. (VER) RANAP version
.
(AMR) adaptive multi-rate speech codec mode count

Issue 8-1 en
RNC handling in MSS
. (AMRCODEC) AMR codec capability

. (MSET) mode set for AMR codec
3. RNC address
.
(DIG) global title address
. (NI) network indicator
.
(SPC) signalling point code
4. RANAP version
a. Version identification
. (VER) radio network controller parameter set
b. Version information
. (TYPE) information type
. index
. value
5. UPD usage
.
(LTYPE) user plane destination list
Selects output type: available (connectable) or used
(connected).
6. LA–RNC relation
.
(LACL) location area code list
. (LACLA) location area code list add
. (LACLR) location area code list remove
. (MCC, MNC) list of supported multiple PLMNs in RNC
<option>
7. State handling
. (STATE) radio network controller state
The operational state of own and auxiliary RNCs is changed
by the system. You can only change the administrative state.
The operational state is valid only if the administrative state is
UNLOCKED.
To see other functions of cellular radio network management, see Cellular

Radio Network Management Overview.

Issue 8-1 en

Issue 8-1 en
BTS and service area handling
5 BTS and service area handling

You can handle base transceiver station (BTS) and service area
configuration files with the EP Command Group. For more information, see
Base Transceiver Station Handling, EP Command Group.
With the following commands you can:
. EPC – create BTS or service area

. EPR – modify BTS or service area parameters
. EPH – modify traffic reason handover parameters
. EPI – modify resource indication parameters
.
EPN – modify BTS neighborhood
. EPS – change BTS or service area administrative state
.
EPB – define location area-BTS-BSC/UNC relation
. EPF – define location area-service area-MGW relation
.
EPD – delete BTS or service area
. EPO – output BTS or service area data
5.1 Logical grouping of BTS/service area parameters

The parameters for handling BTS/service areas can be divided into the
1. BTS/SA identification
.
(TYPE) object type
.
(NO) object number
2. Reference BTS/SA identification

Issue 8-1 en
. (RNAME) reference object name

. (RNO) reference object number
The reference BTS parameter values are copied to the following
group 5 (miscellaneous) parameters:
. local area dialling code <option>
.
charging area code <option>
. supplementary charging area codes <option>
.
cell band <option>
. routing zone
.
tariff area
. DTX function
. cell dependent routing <option>
. cell test state
Default values for the above parameters are used if you do not
give a reference object.
The reference BTS parameter values are also present in the "traffic
reason handover" and in "resource indication" logical parameter
groups below. You can modify traffic reason handover parameters
with the EPH command and resource indication parameters with the
EPI command.
Note
A reference BTS's neighbor BTS list is not copied to the BTS you are
creating. You can modify the list with the EPN command.
3. Output data group

.
data group
4. LA identification
.
(LAC) location area code
. (LANAME) location area name
5. Locating services
. (PSET) parameter set <option>
. (ERGMLC) ESRK requested from GMLC <option>
.
(NOPOS) no positioning procedure initiated <option>
. (NONCAS) no NCAS support <option>
.
(POST) position determination timer <option>

Issue 8-1 en
BTS and service area handling
. (EU) ESRK usage <option>

. (ESRK) ESRK range index <option>
. (CQOS) Cell based QOS for LCS <option>
.
(ESGMLC) GMLC index for emergency services <option>
6. Miscellaneous
.
(LAD) local area dialling code
. (CI) cell identity (this parameter is an alternative to the SAC
parameter; if TYPE has the value “BTS”, CI must be used.)
. (SAC) service area code (this parameter is an alternative to
the CI parameter; if TYPE has the value “Service Area” SAC
must be used.)
. (BAND) cell band <option>
. (CA) charging area code <option>
. (SCA) supplementary charging area codes <option>
.
(CLN) location number <option>
. (TON) type of location number <option>
.
(NPI) numbering plan identification <option>
. (PRES) number presentation status <option>
.
(INN) internal network number indicator <option>
. (RZ) routing zone
. (TA) tariff area
. (DTX) downlink DTX disabled by MSC
. (CDR) cell dependent routing <option>
.
(TE) cell test state
7. State handling
.
administrative state
8. LA relations
a. LA-BTS-BSC relation
. (BSCNAME) BSC name
.
(BSCNO) BSC number
b. LA-SA-MGW relation
. (SANAME) service area name
. (SA) service area number
. (MGWNBR) MGW number

Issue 8-1 en
9. Traffic reason handover (BTS only)

a. Neighborhood
. (NNO) neighborhood BTS number
.
(NNAME) neighborhood BTS name
. neighborhood modification mode
b. Modify traffic reason handover
. (TRHI) traffic reason handover function to cell
.
(TRHO) traffic reason handover function from cell
. (INC) in-criterion (per cent)
.
(OUTC) out-criterion (per cent)
. (HOJ) handover candidate enquiry jitter
. (COEF) coefficient
. (HYST) hysteresis value
. (TCH) triggering channel type
.
(INTI) interference levels for in-criterion
. (INTO) interference levels for out-criterion
10. Resource indication (BTS only)
. (RI) resource indication function
.
(RIM) resource indication method
. (RIP) resource indication period
. (LIV) load information validity time
. (ERI) extended resource indicator function
. (TAR) total accessible resource indication
.
(SM) subsequent mode
. (TCHP) full rate traffic channel max count
.
(TCHH) half rate traffic channel max count
To see other functions of cellular radio network management see Cellular

radio network management overview.

Issue 8-1 en
NRI and pool area configuration handling
6 NRI and pool area configuration handling

You can handle the NRI and the pool area configuration with the E3
command group. For more information, see NRI and Pool Area
Configuration Handling, E3 Command Group.
With the commands you can:
. E3M — modify pool area

. E3P — delete pool area
. E3O — interrogate pool area
. E3A — add MSS to pool area
.
E3E — modify MSS in pool area
. E3D — remove MSS from pool area
.
E3I — interrogate MSS in pool area
. E3C — create neighbor pool area
.
E3H — modify neighbor pool area
. E3F — delete neighbor pool area
. E3S — interrogate neighbor pool area
. E3L — add MSS to neighbor pool area
. E3N — modify MSS in neighbor pool area
. E3G — remove MSS from neighbor pool area
. E3J — interrogate MSS in neighbor pool area
.
E3X — export RN configuration of pool area
. E3Y — import RN configuration to pool area
.
E3V — activate RN configuration of pool area

Issue 8-1 en
6.1 Logical grouping of NRI and pool area parameters

The parameters for handling the NRI and the pool area can be divided into
the following logical groups:
1. Identification
. (POOLNAME) neighbor pool area name
.
(NNAME) new pool area name / new MSS name (depends on
the given command)
. (MSSNAME) MSS name
. (NNAME) new MSS name / new pool area name (depends on
the given command)
2. NRI Handling
. (NRILEN) the length of NRI value in bits
.
(NLEN) the new length of NRI in bits
. (NRI) network resource identifier
.
(NPAI) neighbor pool area index (this parameter is related to
linking the E3 command group to the EI command group)
. (NRIADD) add NRI value
. (NRIREM) remove NRI value
3. Maintenance mode
. (MAINT) maintenance mode of own MSS
. (MNRI) maintenance NRI
.
(PNRI) parallel NRI list <option>
. (NRIVALC) NRI validity check <option>
.
(STOPLEV) VLR stop level for redistribution <option>
. (TIMER) redistribution of active call timer <option>
.
(WF) NRI weight factor <option>
. (NBLAC) non broadcast LAC
. (NBMCC) non broadcast MCC
. (NBMNC) non broadcast MNC
4. MSC/VLR Address
.
(MDIG) the global title address of an MSS
. (MNI) MSS network indicator
.
(MSPC) MSS signalling point code
. (VDIG) global title address of a VLR
.
(VNI) VLR network indicator
. (VSPC) VLR signalling point code

Issue 8-1 en
NRI and pool area configuration handling
5. Configuration transfer
. (CONFSEL) configuration selection of own MSS.
. (DNAME) the name of the directory where radio network
configuration is imported/exported.
. (INC) included in pool concept (this parameter belongs to the
EL and the EI command groups).
6. Miscellaneous
.
(TYPE) object identification.
. (TRA) call tracing allowed.
.
(VER) BSSAP version (this parameter belongs to the EI
command group).
. <view mode> indicates whether the network location area
relation list is shown in the execution printout or not.

Issue 8-1 en

Issue 8-1 en
General RNW Parameter Handling in MSS
7 General RNW Parameter Handling in

MSS
You can use the commands of the E9 command group in MSS to manage
the general radio network parameters. For more information, see General
RNW Parameter Handling, E9 Command Group.
This command group includes the commands to create, modify, delete and
interrogate the mode sets of the AMR codecs. Created mode sets can be
attached to BSCs and RNCs. For more information, see Cellular Network
Controller Handling, ED Command Group and Radio Network Controller
Parameter Handling in MSS, E2 Command Group.
The following commands are for handling mode sets for AMR codecs:
. E9P – define mode sets for AMR codecs

. E9O – output mode sets of AMR codecs
7.1 Logical grouping of general RNW parameters

Parameters for handling RNCs in the MSS concept can be divided into the
.
Mode set identification
. TYPE – mode set type
. ID – mode set id
. Mode set information
. SCS – modes in the supported codec set
. ACS – modes in the active codec set
. OM – optimization mode

Issue 8-1 en

Issue 8-1 en
Creating a cellular radio network
8 Creating a cellular radio network

Setting up a cellular radio network involves:
.
creating own/auxiliary and network location areas, BSC, RNC, BTS/
service area
.
defining relations between network elements
. creating user plane destinations (see User plane routing, Operating
Instructions)
. creating and activating signalling connections (see Signalling
Transport over IP, Operating Instructions)
.
creating and activating routing connections for each BSC using the
RCC (for more information, see Creating circuit groups and routes),
and for RNCs behind each MGW Rel–4 (for more information, see
User plane routing, Operating Instructions)
.
creating SGSN connections
. arranging LAs into zone codes
. changing administrative state of BSC, RNC, and BTS/service area
8.1 Creating location areas
8.1.1 Creating own location area
Steps
1. Create own location area (ELC)
Create own location area with the ELC command , by giving

parameters in the following parameter groups:

Issue 8-1 en
. Location area identification

. Reference location area identification
If you give a reference location area to create an own location
area, parameter values for the following parameter groups are
copied from the reference location area:
.
Radio channel assignment priority
. Paging
.
Roaming
. Miscellaneous
See Logical grouping of own/auxiliary location area parameters for
the parameters in the above parameter groups.
See the ELC command references for examples.
8.1.2 Creating auxiliary location area
Steps
1. Create auxiliary location area (ELS)
Create an auxiliary location area with the ELS command, by giving

.
Reference location area identification
If you give a reference location area to create an auxiliary
location area, parameter values for the following parameter
groups are copied from the reference location area:
. Radio channel assignment priority
.
Roaming
(RNGP, AMNC, and RMNC)
the parameters in the above parameter groups.
See the ELS command reference for examples.
8.1.3 Adding network location area
Once you have created a new location area, you need to add it as a
network location area in the other MSC/MSSs of your network, so that the
MSCs/MSSs will know the network location areas under their control.
You do not need to define all location areas as network location areas. Just
define the neighboring location areas that belong to different MSC/MSSs
as network location areas.

Issue 8-1 en
Note
If the network location area contains an UMTS access the BSSAP

version connected to the location area has RANAP EXTENSIONS
SUPPORTED set as YES.
Note
Before you add a network location area, check with the EIO command
that the network location area does not already exist.
Steps
1. Add network location area (EIA)
Add a network location area with the EIA command, by giving the
.
Location area identification
. Reference location area identification
See Logical grouping of network location area parameters for
parameters in the above parameter groups.
See the EIA command reference for examples.
8.2 Creating BSC

The system creates the BSC object in a LOCKED administrative state. To
bring the BSC into operational use, change the state into UNLOCKED with
the EDS command.
Steps
1. Create BSC (EDC)
Create a BSC with the EDC command, by giving parameters in the

following parameter groups:
.
BSC identification
. Reference BSC identification
See Logical grouping of BSC parameters for parameters in the
above parameter groups.
See the EDC command reference for examples.

Issue 8-1 en
2. Change administrative state of BSC (EDS)

You need to change the BSC administrative state to:
. UNLOCKED after creating a BSC with EDC, to make it
operational;
. UNLOCKED before you restart a BSC with EDE;
.
LOCKED before deleting a BSC with EDD.
Note
Before changing the administrative state to UNLOCKED, define at least

one route with the EDR command, or enable one circuit allocation by
BSS with the EDH command. Also, define a signalling point code with
the EDL command.
Change the BSC administrative state (L/U) with the EDS command,
by giving the parameters in the following parameter groups:
.
BSC identification
. State handling
See the EDS command for examples.
8.3 Defining routes for BSC

The EDR command is related to the RC command group, used for Creating
circuit groups and routes. If you have defined the route(s) of the BSC with
MML for creating TDM circuit groups (with the RCC command), you can
add the corresponding route to the cellular radio network file with the EDR
command. You can also define the SPC and SNC in the cellular radio
network file before creating the corresponding SPC with SS7 network
administration MML. For instructions, see Signalling Transport over IP,
Operating Instructions.
You need to define at least one route with this command before you can
change the BSC administrative state to UNLOCKED with the EDS
command. The EDR command is therefore linked to the EDS command and
EDH <option>.

Issue 8-1 en
Note
Before you connect routes to BSC, they have to be defined in routing

management.
Steps
1. Define routes for BSC (EDR)
Define the routes of circuit pools between a BSC and an MSC with
the EDR command, by giving parameters in the following parameter
groups:
.
BSC identification
. UP resources
See the EDR command for examples.
8.4 Defining signalling system information for BSC

The EDL command is related to the SS7 network administration command
class. So, if you have defined the SPC for a BSC with SS7 network
administration MML, you can add the corresponding SPC to the cellular
radio network file with the EDL command. Additionally, you can define the
SPC and SNC in the cellular radio network file before creating the
corresponding SPC with SS7 network administration MML. For
instructions see Signalling Transport over IP, Operating Instructions.
Steps
1. Define signalling system information for BSC (EDL)
Define signalling system information with the EDL command, by

giving parameters in the following parameter groups:
.
BSC identification
. CP resources
See the EDL command for examples.

Issue 8-1 en
8.5 Defining supported mode sets of BSCs <optional>

With the EDG command, you can modify the supported mode sets for
narrowband and wideband AMR codecs of one or more BSCs.
Steps
1. Define supported mode sets for BSC (EDG)
Define supported mode sets with the EDG command, by giving

. BSC identification
.
AMR modes
Note
Before mode sets can be defined per BSC, the mode sets must be
created with the commands of the General RNW Parameter Handling,
E9 command group.
See Logical grouping of BSC parameters for parameters in the above

parameter groups. See the EDG command for examples.
8.6 Creating RNCs
8.6.1 Creating own RNC
You can define signalling system information (RNC address) for an own
RNC with SS7 network administration MML. For further information see
Signalling Transport over IP, Operating Instructions. Once you have done
so, add the corresponding RNC address to the cellular radio network file
with the E2C command. You can also define the RNC address in the
cellular radio network file before creating it with SS7 network
administration MML.
The system creates an RNC in the LOCKED state. Change the state to
UNLOCKED with the E2S command to make the RNC operational.

Issue 8-1 en
Note
Before creating an RNC to an own radio network, make sure that the
location area to which you will connect the RNC is defined in the MSS
and user plane destinations. If not, create a location area with the ELC
command.
Steps
1. Create own RNC (E2C)
Create an own RNC with the E2C command, by giving parameters in

the following parameter groups:
. RNC identification
.
Miscellaneous
. RNC address
.
LA-RNC relation
See the E2C command for examples.
2. List user plane destinations (E2L)
User Plane Destinations (UPD) can be created with the JFC
command of the User Plane Topology Data Handling command
group.
List user plane destinations and select the ones you want to see
(available (AVAIL) or used (USED)) with the E2L command, by
giving parameters in the following parameter group:
.
UPD usage
See Logical grouping of RNC parameters in MSS concept for
See the E2L command for examples.
You can change user plane destinations in an own radio network
with the E2M command.
3. Define mode sets for AMR codecs (E9P)
You can create, modify and delete mode set for AMR codec
configuration with the commands of the General RNW Parameter
Handling, E9 command group. The following parameters can be
given:
.
TYPE (mode set type)
. OM (optimization mode)
.
SCS modes (Supported Codec Set modes)
. ACS modes (Active Codec Set modes)

Issue 8-1 en
You can output created mode sets with the E9O command. See the
E9P and E9O commands for examples.
You can change used mode sets in an own radio network with the
E2M command.
4. Change administrative state of own RNC (E2S)
Change an own RNC's administrative state to:
. UNLOCKED when you want to make it operational after
having created it
. LOCKED when you want to delete an RNC that is in
UNLOCKED state.
Changing an own RNC to UNLOCKED generates a Global Reset
procedure to initiate the Iu-interface between the MSS and RNC.
Change the administrative state of an own RNC with the E2S
command, by giving parameters of the following parameter groups:
.
RNC identification
. State handling
See the E2S command for examples.
5. Restart own RNC (E2R)
This procedure initiates the Iu-interface between the RNC and MSS.
Restart own RNC with the E2R command, by giving the following
parameter group:
.
RNC identification
parameters in the above parameter group.
See the E2R command for examples.
8.6.2 Creating auxiliary RNC
You can define signalling system information (RNC address) for an

auxiliary RNC with SS7 network administration MML.
For further information see Signalling Transport over IP, Operating

Instructions.
After you have performed this action, add the corresponding RNC address
to the cellular radio network file with the E2E command. You can also
define the RNC address in the cellular radio network file before creating it
with SS7 network administration MML.

Issue 8-1 en
The system creates an RNC in the LOCKED state. Change the state to
UNLOCKED with the E2K command to make the RNC operational.
Steps
1. Create auxiliary RNC (E2E)
Create an auxiliary RNC with the E2E command by giving the

.
Miscellaneous
. RNC address
See the E2E command for examples.
2. List user plane destinations (E2L)
User Plane Destinations (UPD) can be created with the JFC User
Plane Topology Data Handling command.
List user plane destinations and select the ones you want to see
(available (AVAIL) or used (USED)) with the E2L command, by
giving parameters in the following parameter group:
. UPD usage
See the E2L command for examples.
You can change user plane destinations in an auxiliary radio network
with the E2F command.
You can create, modify and delete mode set the AMR codec
configuration with the commands of the General RNW Parameter
Handling, E9 command group. The following parameters can be
given:
. TYPE (mode set type)
. SCS modes (Supported Codec Set modes)
.
ACS modes (Active Codec Set modes)
You can output created mode sets with the E9O command. See the
E9P and E9O commands for examples.
You can change used mode sets in an auxiliary radio network with
the E2F command.

Issue 8-1 en
4. Change administrative state of auxiliary RNC (E2K)

Change the administrative state of an auxiliary RNC with the E2K
command, by giving the following parameter groups:
.
RNC identification
. State handling
See the E2K command for examples.
5. Restart auxiliary RNC (E2T)
This procedure initiates the Iu-interface between the RNC and MSS.
Restart an auxiliary RNC with the E2T command , by giving the
following parameter group:
See the E2T command for examples.
8.7 Creating BTS/service area and defining LA - BTS -

BSC and LA - service area - MGW relations
A BTS in MSC cellular radio network configuration files means the same
as a cell in GSM. A service area in UMTS is handled the same way as a
BTS.
The system creates a BTS/service area in LOCKED administrative state.

To make the BTS/service area operational, change the administrative state
to UNLOCKED with the EPS command.
Note
Before you create a BTS or a service area, make sure that location area
has been defined in the MSC/MSS, in order to be able to connect the
BTS/service area to it. If necessary, create a location area with the ELC
command.
Before you can create the auxiliary service area, you have to create the
auxiliary LA for that service area with the ELS command.

Issue 8-1 en
Steps
1. Create BTS/service area (EPC)
Create a BTS or service area with the EPC command, by giving the
. BTS/SA identification OR Reference BTS/SA identification
(If you use a reference BTS, group 5 (miscellaneous)
parameter values are copied.)
.
LA identification
. Miscellaneous
See Logical grouping of BTS/service area parameters for
See the EPC command for examples.
2. Define LA-BTS-BSC relation (EPB)
When you create a BTS with the EPC command, you automatically
connect it to a location area.
You must define the BTS-BSC relation before you can UNLOCK the
BTS with the EPS command.
Note
A BTS has to be in LOCKED state when you modify the LA-BTS-BSC

relation. If necessary, change the state to LOCKED with the EPS
command.
Define the LA-BTS-BSC relation with the EPB command, by giving

. BTS/SA identification
.
LA–BTS–BSC relation
See the EPB command for examples.
3. Define LA-service area-MGW relation (EPF)
You do not need to define the service area–MGW relation in the
MSS-MGW Rel-4 concept.
The only possible value is MGWNBR=MSS, which indicates that
service area is in the MSS concept.

Issue 8-1 en
You will need to change the service area's administrative state to

UNLOCKED with the EPS command after having defined the service
area to be in MSS concept.
Note
A service area must be in LOCKED state when you modify its relations.
If necessary, change the administrative state with the EPS command.
Define LA–service area–MGW relation with the EPF command, by

giving the following parameter groups:
. MGWNBR=MSS
See the EPF command for examples.
4. Change administrative state of BTS/service area (EPS)
You need to change the BTS/service area administrative state to:
.
LOCKED before deleting a BTS/service area with the EPD
command.
.
LOCKED before defining BTS/service area relations with the
EPB and EPF commands.
. UNLOCKED after having created a BTS/service area with the
EPC command, to make it operational;
. UNLOCKED after having defined BTS/service area relations
with the EPB and EPF commands.
Change the administrative state of a BTS/service area with the EPS
command, by giving parameters in the following parameter groups:
.
State handling
See the EPS command for examples.

Issue 8-1 en
8.8 Sequence for creating a cellular radio network
Note
If either one of the Iu/A multipoint concepts are being used, you need to
perform the following sequence individually for both UMTS/GSM.
Steps
1. Create LA, BSC, and RNC
Create each necessary LA, BSC, and RNC in the MSC/MSS

according to the instructions in Creating location areas, Creating
BSC, and Creating RNCs.
2. Create BTS/service area
Create each necessary BTS/service area according to the
instructions in Creating BTS/service area.
3. Create user plane destinations
User plane destinations must be created before creating RNCs.
Create user plane destinations for RNCs behind MGWs Rel-4. For
further information, see User plane routing, Operating Instructions.
4. Create signalling connections
Create and activate the necessary signalling connections. For more
information, see Signalling Transport over IP, Operating Instructions.
5. Create routing connections
Create and activate the necessary routing connections for each BSC
with the RCC command (see Creating circuit groups and routes) and
for RNCs behind each MGW Rel-4 (see User plane routing,
Operating Instructions).
6. Change administrative states
Unlock each BSC, RNC, and BTS/service area according to
instructions in Creating BSC, Creating RNCs, and Creating BTS/
service area.

Issue 8-1 en
Note
When creating a pool area concept, it is recommended to plan the

activation carefully and base the plans on the capacity need. Before
you start you should be aware of whether you want to implement the
pool area concept at some point, and if so, keep the UMTS/GSM
accesses separate. For more information on creating the sequences for
the UMTS/GSM, refer to the Feature 1564: Multiple A Interface, Feature
Activation Manual and to the Feature 1449: Multipoint Iu in MSC Server,
Feature Activation Manual.
8.9 Creating SGSN connections

An MSC/VLR equipped with the Support of Interaction with SGSN in MSC/
VLR feature supports a standard Gs signalling interface to the Serving
GPRS Support Node (SGSN), the main element in the General Packet
Radio Service (GPRS) network.
The Gs interface, one of several G interfaces in the GPRS, is an optional

interface between the MSC and the SGSN that allows the SGSN to send
location data to the MSC and receive paging requests from the MSC.
MSC/VLR
Gs
SGSN
A
Gb
BSS
GPRS MS (Class A and B)
Figure 10. Gs interface between MSC and SGSN

Issue 8-1 en
The feature fully supports Class B GPRS mobiles, which allows them to
use GPRS and circuit switched (CS) services simultaneously. It also saves
on radio resources in PLMNs that support both CS and GPRS because:
.
GPRS/IMSI attaches, routing, and location updates of class A and B
mobiles are combined
.
CS paging is to a smaller area when done via SGSN
When you create a new SGSN connection, the program sets the SGSN
delay of the SGSN to the default value (zero). If necessary, you can modify
the value using the EJM command.
Steps
1. Create SGSN connection (EJC)
Create an SGSN connection with the EJC command.
8.10 Creating zone codes

Creating a zone code requires feature Regional Roaming, which enables
you to arrange location areas into roaming areas identified with a zone
code. The roaming areas associated with a zone code may include
anything from one location area up to a whole PLMN. Location areas in a
zone code do not need to be adjacent, hence you can create roaming
areas that include large cities but not the surrounding areas.
You can create up to 500 zone codes to an MSC, and define up to 10 zone
codes for each subscriber.
When the subscriber does a location update to an LA, the system checks
the zone code data, and depending on the settings, allows or prevents
roaming. IN-MM triggering is handled similarly.
Zone codes are used to:
. control network traffic load

. restrict national roaming in a hired network
. set up location areas based on cell type
. set up location areas with different tariffs
.
create location areas specific to a customer, such as, an office.

Issue 8-1 en
Steps
1. Create zone code (EKC)
Create a zone code with the EKC command. Give each zone code a
unique hexadecimal identifier and name. You can then define the
roaming and IN-MM triggering parameters. If you do not, the system
uses the default values which are: Roaming allowed in the zone
code area; IN-MM triggering not allowed.
See command reference for examples.

2. Add/remove LA to/from zone code (EKA)
Add/remove a location area to/from a zone code with the EKA
command. Identify the zone by its hexadecimal identifier or name,
and identify the location area by its code (LAC) or name (LANAME).
See command reference for examples.
8.11 Creating NRI and pool area

For reference on how this procedure is performed, see Add MSS in Pool
Area.
Steps
1. See above in Procedure information.
Note
Defining Multipoint related NRI configuration requires Feature 1564:

Multiple A Interface or Feature 1449: Multipoint Iu in MSC Server. But
also in solely MOCN related environment, the NRI configuration needs
to be defined by Feature 1847: Multi-Operator Core Network Support in
MSS.

Issue 8-1 en
Optimizing a cellular radio network
9 Optimizing a cellular radio network
9.1 Modifying location area parameters
9.1.1 Modifying own location area parameters
Steps
1. Modify own location area parameters
Modify own location area with the following commands and

corresponding parameter groups:
(ELP)
. Radio channel assignment priority
(ELH)
. Roaming
(ELE, ELR)
. Miscellaneous
(ELE)
See the ELP, ELH, ELR, and ELE command references for examples.
2. Output own location area data (ELO)
Output own location area data with the ELO command, by giving
.
(NAME or LAC or MCC and MNC)
. Output

Issue 8-1 en
See the ELO command reference for examples.
9.1.2 Modifying auxiliary location area parameters
Steps
1. Modify auxiliary location area parameters (ELM)
Modify auxiliary location area with the ELM command, by giving

.
Radio channel assignment priority
. Roaming
See the ELM command reference for examples.
2. Output auxiliary location area data (ELJ)
Output auxiliary location area with the ELJ command, by giving
. Output
See the ELJ command reference for examples.
9.1.3 Modifying network location area parameters
Steps
1. Modify network location area parameters (EIM)
Modify network location area with the EIM command, by giving

.
Miscellaneous
. New PLMN
See the EIM command reference for examples.

Issue 8-1 en
2. Output network location area parameters (EIO)

Output network location area with the EIO command, by giving
.
.
Output
See the EIO command reference for examples.
9.2 Deleting location areas
9.2.1 Deleting own location area
Steps
1. Delete own location area (ELD)
Delete own location area with the ELD command, by giving

parameters in the following parameter group:
.
See the ELD command reference for examples.
9.2.2 Deleting auxiliary location area
Steps
1. Delete auxiliary location area (ELG)
Note
You cannot delete an auxiliary location area with a service area under it.
Before deleting a location area, delete the LA-service area relation with
the EPF command.
Delete an auxiliary location area with the ELG command, by giving


Issue 8-1 en

See Logical grouping of own/auxiliary location area parametersfor
See the ELG command reference for examples.
9.2.3 Deleting network location area
Steps
1. Delete network location area (EIR)
Delete network location area with the EIR command, by giving

9.3 Modifying BSC parameters

The EDR command for creating UP resources is related to the RC
command group, used for Creating circuit groups and routes. If you have
defined the route(s) of the BSC with MML for creating TDM circuit groups
(with the RCC command), you can add the corresponding route to the
cellular radio network file with the EDR command. Or, you can define the
SPC and SNC in the cellular radio network file before creating the
corresponding SPC with SS7 network administration MML. For more
instructions, see Signalling Transport over IP, Operating Instructions.
Note
The BSC needs to be in LOCKED state with all of the following

commands, except EDV, EDN, EDT. If necessary, change the state to
LOCKED with the EDS command.
Steps
1. Modify BSC parameters
Modify a BSC with the following commands and corresponding

parameter groups:

Issue 8-1 en
. State handling
(EDS)
.
UP resources
(EDR)
.
CP resources
(EDL)
.
Miscellaneous
(EDH, EDM, EDI, EDP)
.
BSSAP version
(EDV, EDN, EDT)
. AMR modes (EDG)
2. Output BSC data (EDO)
Output BSC data with the EDO command, by giving parameters in
the following parameter groups:
.
Output BSC data
See Logical grouping of BSC related parameters for parameters in
the above parameter groups.
See the EDO command reference for examples.
9.3.1 Changing cell identification method
Steps
1. Change cell indentification method (EDM)
Change the cell identification method with the EDM command, by

.
BSC identification
. Miscellaneous:
Cell identification method
See the EDM command for examples.

Issue 8-1 en
9.3.2 Changing paging method
Steps
1. Change paging method (EDP)
Change the paging method with the EDP command, by giving

.
BSC identification
. Miscellaneous:
paging method
See the EDP command for examples.
Note
The LAC or LAI paging method is recommended because it produces

less signalling load between the MSC and the BSC than other paging
methods. LAI method is used if radio network configuration of the MSC/
MSS contains several PLMNs.
9.3.3 Changing channel priority assignment function mode
Steps
1. Change channel priority assignment function mode (EDI)
Change the channel priority assignment function mode with the EDI
.
Miscellaneous:
Channel priority assignment function mode
See the EDI command for examples.

Issue 8-1 en
9.3.4 Changing reverse circuit allocation function mode
Note
Make sure the administrative state is LOCKED before you change the
reversed circuit allocation function mode. If necessary, change it to
LOCKED with the EDS command.
Feature 901: 2G FR AMR - HR AMR Speech Codec Support.
Steps
1. Change the reverse circuit allocation function mode <option> with

the EDH command, by giving parameters in the following parameter
groups:
.
BSC identification
. Miscellaneous:
Circuit allocation by BSS
See the EDH command for examples.
9.3.5 Modifying BSSAP version, version name, version information, and

output BSSAP version data
An MSC contains 50 pre-packaged BSSAP service profile descriptions,

which define the data combinations of BSS functions and values of A-
interface timers and parameters. BSSAP service profile descriptions are
identified with a unique number called the BSSAP version.
You will need to modify the BSSAP version after creating a BSC because
the system automatically attaches BSSAP version 15. You will also need
to modify the BSSAP version if you give a reference object because the
parameter values of the reference object are copied.
Steps
1. Modify BSSAP version, version name, version information, and

output BSSAP version data

Issue 8-1 en
Modify BSSAP version with the EDV command, name of BSSAP

version with command EDN, BSSAP version information with the
EDT command , and output BSSAP version data with the EDB
command, by giving the following parameter groups:
.
BSSAP version
. Output BSSAP data
See the EDV, EDN, EDT, and EDB command references for examples.
9.4 Deleting BSC/MGW R99
Note
Before you delete a BSC/MGW R99, check with the EDO command that
there is no BTS/SAC connected to it. If necessary, you can remove the
BTS, by deleting the BTS–BSC relation with the EPB command, and the
SAC, by changing the service area to MSS concept with the EPF
command.
Ensure that the BSC/MGW is in LOCKED administrative state before

you delete it. If necessary, change the administrative state to LOCKED
with the EDS command.
Steps
1. Delete BSC/MGW R99 (EDD)
Delete a BSC/MGW R99 with the EDD command, by giving

.
BSC/MGW R99 identification
Feature 1260: Inter-System Handover and UMTS Changes is
required for you to be able to give TYPE=MGW.
. Reference BSC/MGW R99 identification
See the EDD command reference for examples.

Issue 8-1 en
9.5 Modifying RNCs
9.5.1 Modifying own RNC
You can define signalling system information (RNC address) for an own
RNC with SS7 network administration MML. For further information, see
Signalling Transport over IP, Operating Instructions. Once you have done
so, add the corresponding RNC address to the cellular radio network file
with the E2M command. You can also define the RNC address in the
cellular radio network file before creating it with SS7 network
administration MML.
Note
The RNC must be in LOCKED state for you to modify RNC parameters.
The parameters that you can modify when the RNC is in UNLOCKED
state are VER, AMR, AMRCODEC, ADDMSET, REMMSET, LACLA and
LACLR. If necessary, change the state to LOCKED with the E2K
command.
Steps
1. Modify own RNC (E2M)
Modify an RNC in an own radio network with the E2M command, by

giving the following parameter groups:
.
Miscellaneous
. RNC address
.
LA-RNC relation
parameters in above parameter groups.
See the E2M command for examples.
2. Interrogate own RNC (E2I)
When you interrogate an RNC in an own radio network, you will get
all RNCs for all PLMNs by default if you give only the RNCID
parameter. To interrogate data of RNCs in a particular PLMN, give
the PLMN parameters (MCC <option> and MNC <option>).
If you want to interrogate all RNCs that are attached to a specific
user plane destination, give the UPD or NUPD parameters.

Issue 8-1 en
Interrogate own RNC with the E2I command, by giving the following
parameter group:
See the E2I command for examples.
9.5.2 Modifying auxiliary RNC
You can define signalling system information (RNC address) for an

auxiliary RNC with SS7 network administration MML. For further
information, see Signalling Transport over IP, Operating Instructions. Once
you have done so, add the corresponding RNC address to the cellular
radio network file with the E2F command. You can also define the RNC
address in the cellular radio network file before creating it with SS7
network administration MML.
Note
The RNC must be in LOCKED state for you to modify RNC parameters.
The only parameters you can modify when the RNC is in UNLOCKED
state are VER, AMR, AMRCODEC, ADDMSET, and REMMSET.
If necessary, change the state to LOCKED with the E2K command.
Steps
1. Modify auxiliary RNC (E2F)
Modify an auxiliary RNC with the E2F command, by giving the

. Miscellaneous
. RNC address
See the E2F command for examples.
2. Interrogate auxiliary RNC (E2H)
By default you will get all RNCs for all PLMNs if you give only the
RNCID parameter. To interrogate data of RNCs in a particular
PLMN, give the PLMN parameters (MCC <option> and MNC
<option>).

Issue 8-1 en
If you want to interrogate all RNCs that are attached to a specific

user plane destination, give the UPD or NUPD parameters.
Interrogate an RNC in an auxiliary radio network with the E2H
command, by giving the following parameter group:
See the E2H command for examples.
9.5.3 Modifying RNC version data
Steps
1. Modify RNC version data (E2N)
Modify RNC version information with the E2N command, by giving

the following parameter group:
. RANAP version
See the E2N command for examples.
2. Interrogate RNC version data (E2J)
Interrogate RNC version information with the E2J command, by
giving the following parameter group:
. RANAP version identification
See the E2J command for examples.
9.6 Deleting RNCs
9.6.1 Deleting own RNC
Note
Make sure that the RNC is in LOCKED state. If necessary, change the
administrative state to LOCKED with the E2S command.

Issue 8-1 en
Steps
1. Delete own RNC (E2D)
Delete an RNC from an own radio network with the E2D command,
by giving the following parameter group:
parameters in above parameter group.
See the E2D command for examples.
9.6.2 Deleting auxiliary RNC
Note
Before you start, make sure that the RNC is in LOCKED state. If
necessary, change the administrative state to LOCKED with the E2K
command.
Steps
1. Delete auxiliary RNC (E2G)
Delete an RNC from an auxiliary radio network with the E2G

command, by giving the following parameter group:
.
RNC identification
See the E2G command for examples.
9.7 Handling AMR mode sets
9.7.1 Modifying mode sets for AMR codecs
Steps
Modify mode set information with the E9P command, by giving the
following data:

Issue 8-1 en
. TYPE (mode set type)

. ID (mode set ID)
.
SCS modes (Supported Codec Set modes)
. ACS modes (Active Codec Set modes)
See the E9P command for examples.
2. Output mode sets of AMR codecs (E9O)
Interrogate mode set information with the E9O command, by giving
the following parameters:
.
TYPE (mode set type)
. ID (mode set ID)
See the E9O command for examples.
9.8 Modifying BTS/service area
9.8.1 Modifying BTS/service area parameters
Steps
1. Modify BTS/service area parameters (EPR)
Modify BTS/service area <option> parameters with the EPR

. Miscellaneous
See the EPR command for examples.
2. Outputting BTS/service area (EPO)
Output BTS/service area data with the EPO command, by giving
.
BTS/SA identification
. Output data group
See the EPO command for examples.

Issue 8-1 en
9.8.2 Modifying traffic reason handover
Steps
1. Modify traffic reason handover (EPH)
Modify traffic reason handover with the EPH command <option>, by

.
BTS identification
. Traffic reason handover
See the EPH command for examples.
9.8.3 Modifying resource indication
The resource indication function provides the MSC with information about
the number of free traffic channels in a cell.
Steps
1. Modify resource indication (EPI)
Modify resource indication with the EPI command, by giving

. BTS identification
. Resource indication
See the EPI command for examples.
9.8.4 Modifying BTS neighborhood
Steps
1. Modify BTS neighborhood (EPN)
Add/remove a neighboring BTS to/from an object BTS neighborhood

with the EPN command, by giving parameters in the following
parameter groups:
. BTS identification
. Neighborhood

Issue 8-1 en

See the EPN command for examples.
9.9 Deleting BTS/service area
Note
By deleting a BTS/service area, you are also removing it from

neighboring cell lists.
Note
The BTS and service area have to be in LOCKED state when you
delete them. If necessary, change the administrative state with the EPS
command.
Steps
1. Delete BTS/service area (EPD)
Delete a BTS/service area with the EPD command, by giving

See the EPD command for examples.
9.10 Modifying NRI and pool area configuration

You can modify parameters of own pool area with the E3 command group.
This command group is used for managing NRI information in MSS and
also for exporting/importing network pool area configuration in MSS.

Issue 8-1 en
9.10.1 Modify pool area
Steps
1. Modify pool area
Modify pool area with the E3M command. If command is given for the
first time own pool area is created and the POOLNAME and NRILEN
parameters must both be given.
9.10.2 Delete pool area
Steps
1. Delete pool area
Delete the pool area with the E3P command. Before deleting the
pool area, all MSSs under it must be removed with the E3D
command.
9.10.3 Add MSS in pool area
Steps
1. Add MSS in pool area
You can add own or parallel MSS in own pool area with the E3A
command.
9.10.4 Modify MSS in pool area
Steps
1. Modify MSS in pool area
Modify own or parallel MSS with the E3E command. If own MSS is
modified, then you can only give the following parameters with the
command: NNAME, CONFSEL, NRIADD, NRIREM, MAINT, MNRI, PNRI
<option>, NRIVALC <option>, STOPLEV <option>, TIMER
<option>, NBLAC, NBMCC <option> and NBMNC <option>.

Issue 8-1 en
9.10.5 Remove MSS from pool area
Steps
1. Remove MSS from pool area
Remove MSS from pool area with the E3D command. Before
removing an own or parallel MSS from own pool area, you must
remove the NRI's from the particular MSS with the E3E command
first.
9.10.6 Modify neighbor pool area
Steps
1. Modify neighbor pool area
Modify neighbor pool area with the E3H command.
9.10.7 Delete neighbor pool area
Steps
1. Delete neighbor pool area
Delete neighbor pool area with the E3F command. Before deleting a
neighbor pool area all MSSs under it must be removed first with the
E3G command.
Note
Before removing an MSS, you must first remove the NRI's from that
particular MSS with the command E3N.
9.10.8 Modify MSS in neighbor pool area
With this command you can modify the parameters of MSSs in the
neighbor pool area.
Steps
1. Modify MSS in neighbor pool area

Issue 8-1 en
You can modify the parameters of MSSs in the neighbor pool area
with the E3N command.
9.10.9 Remove MSS from neighbor pool area
Steps
1. Remove MSS from neighbor pool area
You can remove MSS from neighbor pool area with the E3G
command. Remember that before removing an MSS, you must first
the NRI's from the MSS with the command E3N command.
9.11 Sequence in deleting a radio network

This procedure describes how to delete a radio network from MSC radio
network configuration files.
Steps
1. Lock state of BSC/MGW R99, RNC, and BTS/service area
Lock the administrative state of BSC/MGW R99 with the EDS

command , RNC with the E2S command, and BTS/service area with
the EPS command.
2. Delete BTS-BSC and service area-MGW R99 relations
Delete BTS-BSC relation (EPB command) and service area-MGW
R99 relation (EPF command).
3. Delete BTS/service area
Delete BTS/service area with the EPD command.
4. Delete BSC/MGW R99
Delete BSC/MGW R99, with the EDD command.
5. Delete LA
Delete LA from MSC radio network configuration, with the ELD
command.

Issue 8-1 en
9.12 Transferring BSCs between MSCs/MSSs

Transferring of BSCs between MSCs/MSSs may be required for capacity
reasons. The maximum number of BSCs under an MSS is 500 (optional).
When transferring a BSC, you will need to define the BSC in the new MSC/
MSS.
Do not, however, remove the configuration from the old MSC/MSS until
you have tested the BSC in the new MSC/MSS. Lock the BSC in the old
MSC/MSS to prevent usage.
In radio network configuration you can have duplicate location areas under
an MSC/MSS by means of the identical LAC switch (ILS) parameter. This
procedure describes how to move an entire LA under another MSC/MSS,
enabling use of the ILS parameter.
Another scenario is that the transferred BSC cells (BTSs) do not include
the whole LA, and the LA remains in the old MSC/MSS. The transferred
BSC cells are defined for the LA in the target MSC/MSS. Again, the BSC
and cells are locked in the old MSC/MSS, and removed only after the
transfer has been successfully completed. The LA in the target MSC/MSS
is defined as a network LA in the old MSC/MSS and in the BSC.
When you transfer a BSC to another MSC/MSS, you will need to create
and activate signalling connections between the two elements. For more
information on signalling configuration see Signalling Transport over IP,
Operating Instructions.
The following figure illustrates a BSC named SORIBSC being transferred

to another MSC/MSS.

Issue 8-1 en
MSC1 MSC2
SPC=16382 SORI TSL 16 SPC=234567
PCM 105
BSC
SPC=B30
Signalling link number 30
Signalling link set REBSC
External route number 500
LAC
3030
BTS311
Figure 11. Transferring BSCs between MSCs/MSSs
9.13 Creating LA, network LA, and BSC

Steps
1. Create LA
Create BSC's location area in the new MSC/MSS according to

instructions in Section Creating own location area.
If the location area has already been defined in the MSC/MSS as a

network location area, use the ILS parameter.
When using the ILS parameter, make sure that all the cells in a
location area are connected to one BSC. A location area that is
simultaneously active in an old and new MSC/MSS will cause inter-
MSC handover problems. The ILS parameter is to be used
temporarily only.
2. Add network LA
Add network location area according to instructions in Adding
network location area.

Issue 8-1 en
3. Create BSC
Create BSC according to instructions in Creating a BSC.
4. Define SPC and SNC
Define signalling point code (SPC) and signalling network code
(SNC) according to instructions in Defining signalling system
information for BSC.
5. Set full rate pool
Set full rate pool according to instructions in Defining routes for BSC.
9.14 Creating BTS and LA-BTS-BSC relation

Steps
1. Create BTS
Create BTS according to instructions in Creating a BTS/service

area.
2. Define LA-BTS-BSC relation
Define the LA-BTS-BSC relation according to instructions in
Creating BTS/service area and defining LA-BTS-BSC and LA-
service area - MGW relations.
3. Modify BTS parameters
Modify BTS parameters, if needed, according to instructions in
Modifying BTS or service area parameters.
9.15 Changing old MSC/MSS configuration

Steps
1. Define network location area in old MSC/MSS
After having created a BSC's location area in a new MSC/MSS,

define the location area as a network location area in the old MSC/
MSS.
See Adding network location area for instructions.

2. Change BSC and BTS administrative state

Issue 8-1 en
Change administrative state of BSC with the EDS command and

BTS with the EPS command.
9.16 Changing BSC configuration

You need to change the BSC configuration before you transfer it.
Steps
1. Delete A-interface
Delete A-interface in the old MSC/MSS. See BSS integration for

further information.
2. Create A-interface
Create an A-interface in the new MSC/MSS. See BSS integration.
9.17 Making BSC and BTS operational

Unlock the elements to make them operational.
Steps
1. Unlock BSC and BTS
Unlock the BSC with the EDS command and BTS with the EPS
command.
See the EDS and EPS commands for examples.
9.18 Removing duplicate configurations from old MSC/

MSS
If the BSC in the new MSC/MSS works, it is safe for you to remove the
configuration from the old MSC.

Issue 8-1 en
Steps
1. Delete BTSs of transferred BSC
Delete BTSs of the transferred BSC according to instructions in

Deleting a BTS or service area.
2. Delete BSC
Delete BSC according to instructions in Deleting a BSC.
3. Delete duplicate location area
Delete duplicate location area according to instructions in Deleting
own location area.
4. Delete duplicate network LA definition of BSC in new MSC/MSS
Delete BSC's duplicate network location area definition from the new
MSC/MSS according to instructions in Deleting network location
area.
9.19 Handling SGSN connections
9.19.1 Modifying SGSN parameters
Using the Gs interface, CS paging requests make a detour via the SGSN.
The SGSN delay parameter defines the delay resulting from this detour in
comparison with paging across an A-interface. The system uses the delay
value to adjust the repaging interval. The default value of the delay is zero.
Steps
1. Modify SGSN address or delay parameter (EJM)
Modify SGSN address or the value of the SGSN delay parameter

with the EJM command.
See the EJM command for examples.

2. Interrogate SGSN connections (EJO)
Interrogate SGSN connections with the EJO command.
See the EJO command for examples.

Issue 8-1 en
9.19.2 Deleting SGSN connections
Steps
1. Delete SGSN connections (EJD)
Delete SGSN connections with the EJD command.
See the EJD command for examples.
9.20 Handling zone codes
9.20.1 Modifying zone code
Steps
1. Modify zone code (EKM)
Modify the use of a zone code or change the name of a zone code
with the EKM command. Identify the zone code by its hexadecimal
identifier or name.
See the EKM command for examples.

2. Output zone code data (EKO)
You can output zone code data by giving the code or name. You can
output all location areas (default value) or only location areas
included in the zone code.
You can also output data by giving the location area code or name.
You can define what zones to output – the ones that allow roaming
or IN-MM triggering, or the ones that do not allow roaming or IN-MM
triggering. The default value is all zone codes that include the
location area.
Output zone code data with the EKO command.
See the EKO command for examples.
9.20.2 Deleting zone code
Steps
1. Delete zone code (EKD)

Issue 8-1 en
Delete zone codes, one at a time, with the EKD command.
See the EKD command for examples.

Issue 8-1 en

Cellular Radio Network Management PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cellular Radio Network Management PDF

Uploaded by

Copyright:

Available Formats

Nokia Siemens Networks DX MSC / MSS / DX

HLR, Rel. M14.3, Product Documentation, v. 3

Cellular Radio Network

DN9797631 # Nokia Siemens Networks 1 (91)

2 (91) # Nokia Siemens Networks DN9797631

1 Cellular radio network management 11

2 Location area handling 27

4 RNC handling in MSS 37

5 BTS and service area handling 41

6 NRI and pool area configuration handling 45

7 General RNW Parameter Handling in MSS 49

8 Creating a cellular radio network 51

DN9797631 # Nokia Siemens Networks 3 (91)

8.10 Creating zone codes 65

9 Optimizing a cellular radio network 67

4 (91) # Nokia Siemens Networks DN9797631

9.18 Removing duplicate configurations from old MSC/MSS 88

DN9797631 # Nokia Siemens Networks 5 (91)

Table 1. Maximum radio network configuration in the MSC/MSS 25

6 (91) # Nokia Siemens Networks DN9797631

DN9797631 # Nokia Siemens Networks 7 (91)

8 (91) # Nokia Siemens Networks DN9797631

Changes between document issues are cumulative. Therefore, the latest

Changes made between issues 8–1 and 8–0

Feature references have been corrected according to the approved

Changes made between issues 8–0 and 7–1

. The E9, General RNW Parameter Handling in MSS MML command

DN9797631 # Nokia Siemens Networks 9 (91)

. The following subsection has been removed:

Changes made between issues 7–1 and 7–0

Information on Unlicensed Mobile Access (UMA) has been removed as it

10 (91) # Nokia Siemens Networks DN9797631

1 Cellular radio network management

The main functions of the cellular radio network management are:

. Handling location areas under the MSC/MSS (GSM and Universal

DN9797631 # Nokia Siemens Networks 11 (91)

. NRI and pool area configuration handling with the E3 Command

1.1 Cellular radio network concepts

Cellular radio network

A cellular radio network of an MSC/MSS is a geographical area where the

12 (91) # Nokia Siemens Networks DN9797631

Figure 2. Location area–service area relation

A location area (LA) consists of one or more adjacent cells in a GSM

DN9797631 # Nokia Siemens Networks 13 (91)

If either one of Features 1449 or 1564 is activated, then the Location

Figure 3. Location areas

In the multipoint Iu/A concept, you need to be able to determine whether

14 (91) # Nokia Siemens Networks DN9797631

LA2 MSC/VLR LA1

Figure 4. MSC/VLR area

A pool area corresponds closely to an MSC/MSS service area. The main

DN9797631 # Nokia Siemens Networks 15 (91)

Figure 5. Pool area 1

Figure 6. Pool area 2

16 (91) # Nokia Siemens Networks DN9797631

The MSC/VLR areas in the GSM/UMTS networks form a Public Land

For further details, see Cellular radio network management overview.

1.2 GSM/UMTS radio networks

GSM/UMTS 3G radio network elements

A GSM radio network consists of a Network Subsystem (NSS) and a Base

DN9797631 # Nokia Siemens Networks 17 (91)

BSS and RNS NSS

Figure 8. GSM/3G radio network elements