cellular radio network management

91
Cellular Radio Network Management DN9797631 Issue 8-1 en # Nokia Siemens Networks 1 (91) Nokia Siemens Networks DX MSC / MSS / DX HLR, Rel. M14.3, Product Documentation, v. 3

Upload: le-tuan-linh

Post on 10-Mar-2015

1.027 views

Category:

Documents


9 download

TRANSCRIPT

Page 1: Cellular Radio Network Management

Cellular Radio NetworkManagement

DN9797631Issue 8-1 en

# Nokia Siemens Networks 1 (91)

Nokia Siemens Networks DX MSC / MSS / DXHLR, Rel. M14.3, Product Documentation, v. 3

Page 2: Cellular Radio Network Management

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia 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 DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 3: Cellular Radio Network Management

Contents

Contents 3

List of tables 6

List of figures 7

Summary of changes 9

1 Cellular radio network management 111.1 Cellular radio network concepts 121.2 GSM/UMTS radio networks 171.3 MSC/MSS cellular radio network configuration 23

2 Location area handling 272.1 Logical grouping of own/auxiliary location area parameters 282.2 Logical grouping of network location area parameters 31

3 BSC handling 333.1 Logical grouping of BSC parameters 33

4 RNC handling in MSS 374.1 Logical grouping of RNC parameters in MSS concept 38

5 BTS and service area handling 415.1 Logical grouping of BTS/service area parameters 41

6 NRI and pool area configuration handling 456.1 Logical grouping of NRI and pool area parameters 46

7 General RNW Parameter Handling in MSS 497.1 Logical grouping of general RNW parameters 49

8 Creating a cellular radio network 518.1 Creating location areas 518.1.1 Creating own location area 518.1.2 Creating auxiliary location area 528.1.3 Adding network location area 528.2 Creating BSC 538.3 Defining routes for BSC 548.4 Defining signalling system information for BSC 558.5 Defining supported mode sets of BSCs 568.6 Creating RNCs 568.6.1 Creating own RNC 568.6.2 Creating auxiliary RNC 588.7 Creating BTS/service area and defining LA - BTS - BSC and LA - service

area - MGW relations 608.8 Sequence for creating a cellular radio network 638.9 Creating SGSN connections 64

DN9797631Issue 8-1 en

# Nokia Siemens Networks 3 (91)

Contents

Page 4: Cellular Radio Network Management

8.10 Creating zone codes 658.11 Creating NRI and pool area 66

9 Optimizing a cellular radio network 679.1 Modifying location area parameters 679.1.1 Modifying own location area parameters 679.1.2 Modifying auxiliary location area parameters 689.1.3 Modifying network location area parameters 689.2 Deleting location areas 699.2.1 Deleting own location area 699.2.2 Deleting auxiliary location area 699.2.3 Deleting network location area 709.3 Modifying BSC parameters 709.3.1 Changing cell identification method 719.3.2 Changing paging method 729.3.3 Changing channel priority assignment function mode 729.3.4 Changing reverse circuit allocation function mode 739.3.5 Modifying BSSAP version, version name, version information, and output

BSSAP version data 739.4 Deleting BSC/MGW R99 749.5 Modifying RNCs 759.5.1 Modifying own RNC 759.5.2 Modifying auxiliary RNC 769.5.3 Modifying RNC version data 779.6 Deleting RNCs 779.6.1 Deleting own RNC 779.6.2 Deleting auxiliary RNC 789.7 Handling AMR mode sets 789.7.1 Modifying mode sets for AMR codecs 789.8 Modifying BTS/service area 799.8.1 Modifying BTS/service area parameters 799.8.2 Modifying traffic reason handover 809.8.3 Modifying resource indication 809.8.4 Modifying BTS neighborhood 809.9 Deleting BTS/service area 819.10 Modifying NRI and pool area configuration 819.10.1 Modify pool area 829.10.2 Delete pool area 829.10.3 Add MSS in pool area 829.10.4 Modify MSS in pool area 829.10.5 Remove MSS from pool area 839.10.6 Modify neighbor pool area 839.10.7 Delete neighbor pool area 839.10.8 Modify MSS in neighbor pool area 839.10.9 Remove MSS from neighbor pool area 849.11 Sequence in deleting a radio network 849.12 Transferring BSCs between MSCs/MSSs 859.13 Creating LA, network LA, and BSC 869.14 Creating BTS and LA-BTS-BSC relation 879.15 Changing old MSC/MSS configuration 879.16 Changing BSC configuration 889.17 Making BSC and BTS operational 88

4 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 5: Cellular Radio Network Management

9.18 Removing duplicate configurations from old MSC/MSS 889.19 Handling SGSN connections 899.19.1 Modifying SGSN parameters 899.19.2 Deleting SGSN connections 909.20 Handling zone codes 909.20.1 Modifying zone code 909.20.2 Deleting zone code 90

DN9797631Issue 8-1 en

# Nokia Siemens Networks 5 (91)

Contents

Page 6: Cellular Radio Network Management

List of tables

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

Table 2. Administrative numbering for radio network objects 25

6 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 7: Cellular Radio Network Management

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

DN9797631Issue 8-1 en

# Nokia Siemens Networks 7 (91)

List of figures

Page 8: Cellular Radio Network Management

8 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 9: Cellular Radio Network Management

Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument 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 approvedfeature names.

Changes made between issues 8–0 and 7–1

. The E9, General RNW Parameter Handling in MSS MML commandgroup has been introduced.

. The E2P and E2O commands have been removed.

. Multi-Operator Core Network (MOCN) overview has been added tothe Section GSM/UMTS radio networks.

. New Multipoint A/Iu related parameters for configuring enhancedredistribution functionality of UEs have been introduced.

. The E3P command for deleting pool area configuration has beenintroduced.

. The maximum number of BSCs in maximum radio networkconfiguration 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

DN9797631Issue 8-1 en

# Nokia Siemens Networks 9 (91)

Summary of changes

Page 10: Cellular Radio Network Management

. 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

Changes made between issues 7–1 and 7–0

Information on Unlicensed Mobile Access (UMA) has been removed as itis no longer supported.

10 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 11: Cellular Radio Network Management

1 Cellular radio network management

Cellular radio network management allows you to manage the networkconfiguration 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 configurationelements: location area (LA), Base Station Controller (BSC), BaseTransceiver Station (BTS), Radio Network Controller (RNC), and theservice area,

. Modify the parameters of the radio network configuration elements,

. Handle the administrative states for the BSC, BTS, RNC, and theservice area,

. Define the relationships between the radio network configurationelements,

. Output the data of radio network configuration elements and therelationships 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 UniversalMobile Telecommunications System (UMTS)) with the EL CommandGroup,

. Handling network location areas (GSM and UMTS) with the EICommand Group,

. Handling BSCs with the ED Command Group,

. Handling the BTS cells (GSM), the service area (UMTS) and theauxiliary 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,

DN9797631Issue 8-1 en

# Nokia Siemens Networks 11 (91)

Cellular radio network management

Page 12: Cellular Radio Network Management

. NRI and pool area configuration handling with the E3 CommandGroup,

. Handling roaming areas (zone codes) (GSM and UMTS) with the EKCommand Group,

. Handling the Gs-interface (an interface between the MSC and theServing GPRS Support Node (SGSN)) definitions (GSM) with the EJCommand Group.

1.1 Cellular radio network concepts

The following are descriptions of some of the basic concepts related to thecellular radio networks.

Cellular radio network

A cellular radio network of an MSC/MSS is a geographical area where theMSC/MSS provides GSM or UMTS radio access.

Cell

Cells are the basic units in a GSM cellular radio network. A cell is ageographical area that is covered by a transceiver. A base transceiverstation (BTS) network element generally controls several cells. In cellularradio network configuration management in the MSS, the term "BTS" isconsidered one cell.

Figure 1. Cells

12 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 13: Cellular Radio Network Management

Service area

Service areas are the basic units of a UMTS cellular radio network. Aservice area is a geographical area covering one or more UMTS cells.UMTS cells are not defined in the cellular radio network configuration ofthe MSS. Service areas connected to an MSS through MGW Rel-4 havean LA-service area relation.

Figure 2. Location area–service area relation

Location area

A location area (LA) consists of one or more adjacent cells in a GSMnetwork, or one or more service areas in a UMTS network. Userequipment/mobile stations can roam inside an LA without having toperform location updates. LAs in GSM and UMTS networks have the sameparameters.

LA 2

SA 1

SA 2

SA 3

SA 4

SA 6

SA 5

SA 7SA 7

LA 1

SA 7

LA 3

DN9797631Issue 8-1 en

# Nokia Siemens Networks 13 (91)

Cellular radio network management

Page 14: Cellular Radio Network Management

Note

If either one of Features 1449 or 1564 is activated, then the LocationAreas for UMTS/GSM must be defined separately. If both Features1449 and 1564 are activated, this is not needed. You can check theLA's UMTS/GSM access with the ELL command.

Figure 3. Location areas

A network can include its own LAs, network LAs (addresses of LAscontrolled by other MSC/MSSs), and auxiliary LAs (in UMTS networksonly).

UMTS/GSM access

In the multipoint Iu/A concept, you need to be able to determine whetheryour system has UMTS/GSM access.

Even though a Location Area can include both GSM cells and UMTSservice areas, it is recommended that Location Areas would be definedand used separately for the UMTS and the GSM, so that a single LA wouldonly 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/VLRarea. An MSC/VLR area can consist of one or more LAs, the size of whichis decided in network planning. The trade-off in the LA size is that smallLAs require more location updates from user equipment/mobile stations,which means an increased signalling load. Large LAs require more pagingprocedures, which means an increased load on the BSS/RNS airinterface.

LA1

LA4

LA6

LA9

LA2

LA7

LA5

LA8

LA3

14 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 15: Cellular Radio Network Management

Figure 4. MSC/VLR area

Pool area

A pool area corresponds closely to an MSC/MSS service area. The maindifference is that a pool area is served by multiple MSCs/MSSssimultaneously. The radio network configuration concerning the pool areamust be identical in every MSS controlling the pool area. The traffic isshared between the MSSs within the pool area and a mobile station canroam within the pool area without having to change the serving MSS.

Another difference between a pool area and a service area is that poolareas may overlap, whereas service areas cannot.

LA9

LA3

LA1

LA5

LA7

LA4

LA2

LA8

LA6

MSC/VLR

DN9797631Issue 8-1 en

# Nokia Siemens Networks 15 (91)

Cellular radio network management

Page 16: Cellular Radio Network Management

Figure 5. Pool area 1

Figure 6. Pool area 2

LA12

LA6

LA8

LA10

LA2

LA5

LA9

LA3

LA1

LA4

LA11

LA7

MSC/VLR 1 MSC/VLR 2 MSC/VLR 3

LAnLAn

LAn

LAn

LAn

LAn

LA1

LAn

LAn

LA1

LAn

Pool area 1

Pool area 2

Pool area 3

Overlap

OverlapLAn

LAn LAn

LAn

LAn

LAn

LAn

LAn

LAn

Overlap

LA1

LAn

16 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 17: Cellular Radio Network Management

PLMN

The MSC/VLR areas in the GSM/UMTS networks form a Public LandMobile Network (PLMN). One PLMN can be defined for each LA. An LAcan belong to only one PLMN.

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 earlierradio network concepts a BSS/RAN (Radio Access Network) is connectedto one MSS, but with multipoint Iu/A concept, a RAN/BSS node can beconnected to several MSSs. For more information on this concept, seeSections Pool area and Multipoint network.

GSM/UMTS 3G radio network elements

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

PLMN2

LA3

LA1

LA2

PLMN1

PLMN3

LA4

DN9797631Issue 8-1 en

# Nokia Siemens Networks 17 (91)

Cellular radio network management

Page 18: Cellular Radio Network Management

Figure 8. GSM/3G radio network elements

Network Subsystem

The NSS contains the MSS, which serves the BSS and the RNS underthem.

According to the 3GPP standardized Bearer Independent Circuit SwitchedCore Network concept (Rel-4), the control plane (CP) and the user plane(UP) were separated with the introduction of MGW Rel-4 at system levelM12. At this stage, the MSC functionality was split into two distinct logicalentities. The MSS handles the CP (call control, mobility control, and MGWcontrol) and the MGW Rel-4 handles the UP connections.

The Home Location Register (HLR) supports 2G, 3G and dual-modesubscribers.

The Visitor Location Register (VLR) stores the mobile subscriberinformation 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.

Navigator

GSM BS BSCHLR

GSM mobile

Navigator

GSM BS BSCGSM mobile

UMTS BS RNCUMTS mobile

IN ServiceControl Point

PSTN/ISDN/IP

lu

A

A

A lu

BSS and RNS NSS

MSC/MSS

MGWR4

18 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 19: Cellular Radio Network Management

The Base Station Controllers (BSCs) are defined to the radio networkconfiguration of the MSC/MSS. Normally one BSC controls several BaseTransceiver Stations (BTSs). A BTS realises the radio interface towardsthe mobile stations. One BTS network element can have several cells. Inthe MSC/MSS radio network configuration management, the term "BTS" isconsidered one cell. Therefore, all the cells of a BTS network elementhave to be defined in the MSC/MSS, but not in the physical BTS networkelement.

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 ofWCDMA base stations.

In the MSS concept, the RNCs are defined in the radio networkconfiguration (with an RNC-specific MML) as network elements.

The MSS concept can have two kinds of RNCs in the radio networkconfiguration: RNCs that belong to the MSS's own radio network; andRNCs that belong to an auxiliary radio network of the MSS.

The base stations, or cells, of the RNS are not defined in the radio networkconfiguration of the MSC/MSS.

Multipoint network

In the earlier radio network concept, a RAN/BSS is normally connected toone MSS, but the introduction of the multipoint concept now enables aRAN/BSS node to be connected to several MSSs simultaneously. Theserving area of MSSs is called a pool area and the group of MSSs is calledan MSS pool.

At the beginning of the transaction, the RAN/BSS node selects the MSS towhich the signalling messages are routed. The selection is based on theNetwork Resource Identifier (NRI), which is allocated in an MSS/VLR. If noMSSs are configured for the NRI indicated by the mobile, the RAN/BSSmode selects one of the MSSs in the MSS pool, while at the same timetaking into account the load balancing between the MSSs in the pool. TheMSSs within one pool area and in the overlapping neighboring pool areasmust have unique NRIs.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 19 (91)

Cellular radio network management

Page 20: Cellular Radio Network Management

Using multiple MSSs/MSCs within a pool area increases serviceavailability as other MSSs/MSCs are still able to provide services even ifone MSS/MSC within a pool area fails. It also enlarges the served areacompared to the service area of a single MSS/MSC. This results inreduced inter-MSC/MSS location updates and handovers while alsoreducing the HLR update traffic.

Furthermore, overlapping pool areas allow the separation of the overalltraffic into different mobile station moving patterns. For example, each poolarea can cover a separate residential area while all overlapping pool areascan cover the city centre.

Another significant advantage of the multiple MSS/MSCs in a pool area isthe possibility of capacity upgrades by additional MSSs/MSCs in the poolarea. A multipoint network can consist of up to 10 parallel MSSs/MSCsand 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 aneighboring MSC/MSS. The auxiliary radio network definitions containauxiliary location areas, auxiliary service areas and auxiliary RNCs.Auxiliary radio network definitions may be needed for the "Flexible Iuinterface for handover/relocation" concept or for the "Iur- interface betweenRNCs of different MSC" concept. The use of auxiliary network requiresFeature 1260: Inter-System Handover and UMTS Changes and/or Feature1325: 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 thisconcept is to avoid inter-MSS relocations and thereby to reduce the inter-MSS signalling load. The MSS controls relocations from its own radionetwork to an auxiliary radio network and also inside an auxiliary network.In the "Flexible Iu interface for handover/relocation" concept, the RNC isdefined in two MSSs: as its own RNC in one MSS, and as an auxiliaryRNC in the other MSS, in which also the location areas are definedcorrespondingly. An RNC can be connected to both MSSs through an Iu-interface. If a user equipment starts a transaction from an area controlledby an RNC connected to two MSSs, the transaction is always directedtowards the own MSS. From the MSS point of view, a transaction can notbe started from an auxiliary network, nor paging performed towards anauxiliary network either.

20 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 21: Cellular Radio Network Management

The auxiliary location area and the auxiliary service area definitions arerequired for the "Iur- interface between RNCs of different MSC" concept aswell. It is possible that the mobile station starts the transaction from theradio network of the neighboring MSC/MSS and the signalling is routed tothe MSC/MSS because of the Iur- interface between the RNCs. Thelocation area and the service area are defined to the MSC/MSS, otherwisetransaction is rejected. Normally, when serving an RNC relocationprocedure is supported, it is enough to define the border areas of theneighboring MSC/MSS as auxiliary network. It is possible to reduce theamount of auxiliary networks by defining the auxiliary location area relatedto "default service area", which can be used instead of the real servicearea received from Iu/A'- interface. Using an auxiliary location area relatedto the default service area requires that the auxiliary location area isdefined 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 touse the MSC/MSS-related default location area and service area pair. Thelocation area code (LAC) value 65533 and the service area code (SAC)value 65534 are reserved for this special use. If the MSC/MSS receives anunknown service area identification (SAI), and the MSC/MSS-relateddefault location area and service area are defined in the own radio networkdefinitions, then they are used (instead of the SAI received from Iu/A'-interface) in further call processing. The MSC/MSS-related default LACand default SAC values are not recommended to be used in normal radionetwork configuration.

When the auxiliary location area or the MSC-related default definitions areused, the accuracy of the mobile station's real location (in service arealevel) is lost.

Multi-Operator Core Networks (MOCN)

Network sharing architectures allow different core network operators toconnect to a shared radio access network. The operators do not onlyshare the radio network elements, but may also share the radio resourcesthemselves. In addition to this shared radio access network, the operatorsmay have additional dedicated radio access networks, for example, 2Gradio access networks. The MOCN architecture for network sharing isdefined in 3GPP TS 23.251 Network sharing; Architecture and functionaldescription.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 21 (91)

Cellular radio network management

Page 22: Cellular Radio Network Management

In the figure below, a MOCN reference architecture is illustrated. In thefigure, CN operators A, B and C together share the radio access networkfor 3G. Each operator may also have their dedicated radio accessnetworks, for example, for 2G. This does not obsolete the fact that eachoperator may have the Multipoint Iu feature activated in their own networkssimultaneously.

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 includeinformation concerning the available core network operators into thebroadcast system information. The available core network operators haveto 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, itis possible that the UE supports the core network operator selectionprocess. The functionality for the MOCN is specified separately fornetwork sharing supporting UEs and non-supporting UEs. The majority ofUEs, that is, the pre Rel-6 UEs do not support the network sharingcurrently, thus the network support for non-supporting UEs is necessary.The Nokia Siemens Networks MOCN implementation targets to supportboth supporting and non-supporting UEs for network sharing.

The MOCN configuration requires Feature 1325: RANAP and BSSAP inMSC Server with the optional Multiple PLMN Support for RNC Node inMSS functionality and Feature 1847: Multi-Operator Core Network Supportin MSS to be activated in the MSS.

RNC

Radio Access NetvorkOperator x

CNOperator A

CNOperator B

CNOperator C.......... ..........

Iu

22 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 23: Cellular Radio Network Management

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/mobilestation 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 theuser equipment/mobile station through the correct BSC and RNC,the MSC/MSS has to know the location area relation of thesenetwork elements.

. Handle Control Network Resource Identifier (NRI) and pool areaconfiguration. The NRI and the Pool Area Configuration Handlingare 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 networkconfiguration 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).

DN9797631Issue 8-1 en

# Nokia Siemens Networks 23 (91)

Cellular radio network management

Page 24: Cellular Radio Network Management

The following lists what needs to be defined in the radio networkconfiguration for multipoint concept (optional):

. If you are using the multipoint concept (optional), these definitionsare 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 MSSin a controlled way, the MSS can be put into maintenance mode. Forthis you have to define following:. Maintenance NRI (Null NRI). Non-broadcast location area identity (LAI)

. For enhanced redistribution functionality of UEs the followingoptional 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 haveplanned the work carefully beforehand. Using the IMPORT/EXPORT/ACTIVATE commands below is worth considering especially if you aredealing with a large configuration in your network. The issues toconsider beforehand include, for example, planning on how toimplement the following in the whole configuration:

. Marking the LA's to be copied (with the ELT command for the ownLA'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).

24 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 25: Cellular Radio Network Management

You need to remember that the information must be absolutely identicalin your pool area configuration within a multipoint concept.

You should be aware that using these commands will not make theprocedure completely automatic (manual work is still needed), but it willnonetheless decrease the amount of the manual work needed, as wellas make the manual work more easy to perform.

Any combination of the above radio access types are simultaneouslypossible in an MSC/MSS.

Maximum radio network configuration in the MSC/MSS

The following table shows the maximum configuration in the MSC/MSS foreach 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 radionetwork object.

Table 2. Administrative numbering for radio network objects

Object Number range

BSC 1 – 4095

DN9797631Issue 8-1 en

# Nokia Siemens Networks 25 (91)

Cellular radio network management

Page 26: Cellular Radio Network Management

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 areacode 65534 should not be used as normally in own radio networkconfiguration, because they have special role in the auxiliary radionetwork concept.

For further details see Section Cellular Radio Network ManagementOverview.

26 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 27: Cellular Radio Network Management

2 Location area handling

Managing location areas involves creating and deleting location areas,and modifying location area parameters in the MSC/MSS cellular radionetwork configuration files.

You can create and update own and auxiliary location area-specific data ofthe MSC/MSS with the EL Command Group. For more information on theEL commands, see Location Area Handling, EL Command Group.

Own location areas are used in GSM and UMTS. You can handle ownlocation 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 areoptional and are only used in the MSS concept (UMTS). For moreinformation, see the Auxiliary networks in GSM/UMTS radio networks.

You can handle the auxiliary location area-specific data with the followingcommands:

. ELS – create auxiliary location area <option>

. ELM – modify auxiliary location area data <option>

DN9797631Issue 8-1 en

# Nokia Siemens Networks 27 (91)

Location area handling

Page 28: Cellular Radio Network Management

. 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 thenetwork 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 areaparameters

Parameters relating to own/auxiliary location areas can be divided into thefollowing 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, theprimary MCC and MNC values of the MSC/MSS are used. Theprimary 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

28 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 29: Cellular Radio Network Management

. (RE) re-establishment channel assignment priority

. (EM) emergency channel assignment priority

If the A-interface Priority Information Control is used, then theELH command and the radio channel assignment priorityparameters are not available. See related channel priorityassignment parameter in Logical grouping of BSC/MGW R99parameters.

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 beforeyou 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 Serverconcept.

You need to define the auxiliary service area with the EPCcommand before you can give SAC. See the BTS objectnumber parameter in Logical grouping of BTS/service areaparameters.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 29 (91)

Location area handling

Page 30: Cellular Radio Network Management

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 theparameter name TYPE. The "LA" is the default value and the"AUXLA" is the optional one.

. With the INC parameter you can identify whether the locationarea is set in the pool concept or not. The values for thisparameter 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 WVcommand group.

For more information about this command group, see GSMNetwork and Network Element Specific Number Handling, WVCommand 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 WVcommand group.

For more information about this command group, see GSMNetwork and Network Element Specific Number Handling, WVCommand Group.

. (EQPLMN) equivalent PLMN index for LA <option>

The equivalent PLMNs are handled with the MX commandgroup.

For more information about the commands of this commandgroup, see VLR and PLMN Parameter Handling, MXCommand Group.

. (ISP) intelligent selective paging <option>

7. Output. (RT) relation type

With this parameter you can define how detailed the outputrelational information will be.

. (INCSEL) include in pool concept selector <option>

With this parameter you can limit the output to LAs that areincluded in Multipoint pool concept only.

30 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 31: Cellular Radio Network Management

Note

The default for RT has changed from ALL to NONE. This change is dueto the fact that depending on the maximum configuration, the printoutcan become a very large one.

You can use the ELO and the ELJ commands to arrange the informationyou wish to print out.

2.2 Logical grouping of network location areaparameters

The parameters relating to network location areas can be divided into thefollowing logical groups:

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/VLRaddress group parameters because their values are copied.

3. MSC/VLR address

Note

If you are using the NPAI parameter to define the relation of yournetwork location area and the neighbor pool area, the MSC/VLRaddresses 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

DN9797631Issue 8-1 en

# Nokia Siemens Networks 31 (91)

Location area handling

Page 32: Cellular Radio Network Management

. (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 modifiedwith the ED command group.

. (NPAI) Neighbor pool area index <option>

5. Change PLMN

This parameter group requires the Feature 1168: Multiple PLMN andInter-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>. (MNC) mobile network code <option>. (INCSEL) include in pool concept selector <option>

With this parameter you can limit the output to LAs that areincluded in Multipoint pool concept only.

For further information, see Logical grouping of own/auxiliary location areaparameters.

32 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 33: Cellular Radio Network Management

3 BSC handling

You can handle the BSC parameters with the ED Command Group. Formore information, see Cellular Network Controller Handling, ED CommandGroup.

With this command group you can create and delete a BSC, modify BSCparameters, and output BSC related data.

You can also use it to output and remove MGW R99 from the MSS. Nonew MGW R99 configuration can be created, because the MGW R99network is no longer supported.

3.1 Logical grouping of BSC parameters

Parameters relating to BSC can be divided into the following logicalgroups:

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 objectparameter 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>

DN9797631Issue 8-1 en

# Nokia Siemens Networks 33 (91)

BSC handling

Page 34: Cellular Radio Network Management

If you do not give a reference object, the default values for the aboveparameters 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 RNWParameter Handling, E9 Command Group.

9. Output BSC data. pool view mode

10. Output BSSAP data

34 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 35: Cellular Radio Network Management

. (TYPE) object type

. (NAME) object name

. (NO) object number

. information group

This parameters allows you to choose the type of informationyou will view.

(FUN, TIM, PAR, BSC, NLA or ALL)

For further information, see Cellular radio network management overview.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 35 (91)

BSC handling

Page 36: Cellular Radio Network Management

36 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 37: Cellular Radio Network Management

4 RNC handling in MSS

You can use the commands of the E2 command group in MSS to managethe RNCs under your MSS. For more information, see Radio NetworkController Parameter Handling, E2 Command Group.

From the point of view of Radio Network Controller Parameter HandlingMML, an auxiliary radio network is controlled by a neighbor MSS and usedby an own MSS for relocations. Therefore, an own MSS needs to know theauxiliary network's configuration.

With the auxiliary radio network commands of this command group youcan handle an auxiliary RNC in an own MSS.

State changes of RNCs in an auxiliary radio network only apply to an ownMSS.

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

DN9797631Issue 8-1 en

# Nokia Siemens Networks 37 (91)

RNC handling in MSS

Page 38: Cellular Radio Network Management

. 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 MSSconcept

Parameters for handling RNCs in the MSS concept can be divided into thefollowing logical groups:

1. RNC identification. (RNCID) radio network controller identification. (MCC) mobile country code <option>. (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

38 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 39: Cellular Radio Network Management

. (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 changedby the system. You can only change the administrative state.The operational state is valid only if the administrative state isUNLOCKED.

To see other functions of cellular radio network management, see CellularRadio Network Management Overview.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 39 (91)

RNC handling in MSS

Page 40: Cellular Radio Network Management

40 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 41: Cellular Radio Network Management

5 BTS and service area handling

You can handle base transceiver station (BTS) and service areaconfiguration files with the EP Command Group. For more information, seeBase 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 thefollowing logical groups:

1. BTS/SA identification. (TYPE) object type. (NAME) object name. (NO) object number

2. Reference BTS/SA identification

DN9797631Issue 8-1 en

# Nokia Siemens Networks 41 (91)

BTS and service area handling

Page 42: Cellular Radio Network Management

. (RNAME) reference object name

. (RNO) reference object number

The reference BTS parameter values are copied to the followinggroup 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 notgive a reference object.

The reference BTS parameter values are also present in the "trafficreason handover" and in "resource indication" logical parametergroups below. You can modify traffic reason handover parameterswith the EPH command and resource indication parameters with theEPI command.

Note

A reference BTS's neighbor BTS list is not copied to the BTS you arecreating. 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. (MCC) mobile country code <option>. (MNC) mobile network code <option>

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>

42 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 43: Cellular Radio Network Management

. (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” SACmust 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

DN9797631Issue 8-1 en

# Nokia Siemens Networks 43 (91)

BTS and service area handling

Page 44: Cellular Radio Network Management

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 Cellularradio network management overview.

44 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 45: Cellular Radio Network Management

6 NRI and pool area configuration handling

You can handle the NRI and the pool area configuration with the E3command group. For more information, see NRI and Pool AreaConfiguration 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

DN9797631Issue 8-1 en

# Nokia Siemens Networks 45 (91)

NRI and pool area configuration handling

Page 46: Cellular Radio Network Management

6.1 Logical grouping of NRI and pool area parameters

The parameters for handling the NRI and the pool area can be divided intothe 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

46 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 47: Cellular Radio Network Management

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.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 47 (91)

NRI and pool area configuration handling

Page 48: Cellular Radio Network Management

48 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 49: Cellular Radio Network Management

7 General RNW Parameter Handling inMSS

You can use the commands of the E9 command group in MSS to managethe general radio network parameters. For more information, see GeneralRNW Parameter Handling, E9 Command Group.

This command group includes the commands to create, modify, delete andinterrogate the mode sets of the AMR codecs. Created mode sets can beattached to BSCs and RNCs. For more information, see Cellular NetworkController Handling, ED Command Group and Radio Network ControllerParameter 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 thefollowing logical groups:

. 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

DN9797631Issue 8-1 en

# Nokia Siemens Networks 49 (91)

General RNW Parameter Handling in MSS

Page 50: Cellular Radio Network Management

50 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 51: Cellular Radio Network Management

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, OperatingInstructions)

. creating and activating signalling connections (see SignallingTransport over IP, Operating Instructions)

. creating and activating routing connections for each BSC using theRCC (for more information, see Creating circuit groups and routes),and for RNCs behind each MGW Rel–4 (for more information, seeUser 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 givingparameters in the following parameter groups:

DN9797631Issue 8-1 en

# Nokia Siemens Networks 51 (91)

Creating a cellular radio network

Page 52: Cellular Radio Network Management

. Location area identification

. Reference location area identification

If you give a reference location area to create an own locationarea, parameter values for the following parameter groups arecopied from the reference location area:

. Radio channel assignment priority

. Paging

. Roaming

. Miscellaneous

See Logical grouping of own/auxiliary location area parameters forthe 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 givingparameters in the following parameter groups:. Location area identification. Reference location area identification

If you give a reference location area to create an auxiliarylocation area, parameter values for the following parametergroups are copied from the reference location area:

. Radio channel assignment priority

. Roaming

(RNGP, AMNC, and RMNC)

See Logical grouping of own/auxiliary location area parameters forthe 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 anetwork location area in the other MSC/MSSs of your network, so that theMSCs/MSSs will know the network location areas under their control.

You do not need to define all location areas as network location areas. Justdefine the neighboring location areas that belong to different MSC/MSSsas network location areas.

52 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 53: Cellular Radio Network Management

Note

If the network location area contains an UMTS access the BSSAPversion connected to the location area has RANAP EXTENSIONSSUPPORTED set as YES.

Note

Before you add a network location area, check with the EIO commandthat 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 theparameters in the following parameter groups:. Location area identification. Reference location area identification

See Logical grouping of network location area parameters forparameters 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. Tobring the BSC into operational use, change the state into UNLOCKED withthe EDS command.

Steps

1. Create BSC (EDC)

Create a BSC with the EDC command, by giving parameters in thefollowing parameter groups:. BSC identification. Reference BSC identification

See Logical grouping of BSC parameters for parameters in theabove parameter groups.

See the EDC command reference for examples.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 53 (91)

Creating a cellular radio network

Page 54: Cellular Radio Network Management

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 leastone route with the EDR command, or enable one circuit allocation byBSS with the EDH command. Also, define a signalling point code withthe 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 Logical grouping of BSC parameters for parameters in theabove parameter groups.

See the EDS command for examples.

8.3 Defining routes for BSC

The EDR command is related to the RC command group, used for Creatingcircuit groups and routes. If you have defined the route(s) of the BSC withMML for creating TDM circuit groups (with the RCC command), you canadd the corresponding route to the cellular radio network file with the EDRcommand. You can also define the SPC and SNC in the cellular radionetwork file before creating the corresponding SPC with SS7 networkadministration MML. For instructions, see Signalling Transport over IP,Operating Instructions.

You need to define at least one route with this command before you canchange the BSC administrative state to UNLOCKED with the EDScommand. The EDR command is therefore linked to the EDS command andEDH <option>.

54 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 55: Cellular Radio Network Management

Note

Before you connect routes to BSC, they have to be defined in routingmanagement.

Steps

1. Define routes for BSC (EDR)

Define the routes of circuit pools between a BSC and an MSC withthe EDR command, by giving parameters in the following parametergroups:. BSC identification. UP resources

See Logical grouping of BSC parameters for parameters in theabove parameter groups.

See the EDR command for examples.

8.4 Defining signalling system information for BSC

The EDL command is related to the SS7 network administration commandclass. So, if you have defined the SPC for a BSC with SS7 networkadministration MML, you can add the corresponding SPC to the cellularradio network file with the EDL command. Additionally, you can define theSPC and SNC in the cellular radio network file before creating thecorresponding SPC with SS7 network administration MML. Forinstructions see Signalling Transport over IP, Operating Instructions.

Steps

1. Define signalling system information for BSC (EDL)

Define signalling system information with the EDL command, bygiving parameters in the following parameter groups:. BSC identification. CP resources

See Logical grouping of BSC parameters for parameters in theabove parameter groups.

See the EDL command for examples.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 55 (91)

Creating a cellular radio network

Page 56: Cellular Radio Network Management

8.5 Defining supported mode sets of BSCs <optional>

With the EDG command, you can modify the supported mode sets fornarrowband 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 givingparameters in the following parameter groups:. BSC identification. AMR modes

Note

Before mode sets can be defined per BSC, the mode sets must becreated with the commands of the General RNW Parameter Handling,E9 command group.

See Logical grouping of BSC parameters for parameters in the aboveparameter 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 ownRNC with SS7 network administration MML. For further information seeSignalling Transport over IP, Operating Instructions. Once you have doneso, add the corresponding RNC address to the cellular radio network filewith the E2C command. You can also define the RNC address in thecellular radio network file before creating it with SS7 networkadministration MML.

The system creates an RNC in the LOCKED state. Change the state toUNLOCKED with the E2S command to make the RNC operational.

56 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 57: Cellular Radio Network Management

Note

Before creating an RNC to an own radio network, make sure that thelocation area to which you will connect the RNC is defined in the MSSand user plane destinations. If not, create a location area with the ELCcommand.

Steps

1. Create own RNC (E2C)

Create an own RNC with the E2C command, by giving parameters inthe 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 JFCcommand of the User Plane Topology Data Handling commandgroup.

List user plane destinations and select the ones you want to see(available (AVAIL) or used (USED)) with the E2L command, bygiving parameters in the following parameter group:. UPD usage

See Logical grouping of RNC parameters in MSS concept forparameters in the above parameter groups.

See the E2L command for examples.

You can change user plane destinations in an own radio networkwith the E2M command.

3. Define mode sets for AMR codecs (E9P)

You can create, modify and delete mode set for AMR codecconfiguration with the commands of the General RNW ParameterHandling, E9 command group. The following parameters can begiven:. TYPE (mode set type). OM (optimization mode). SCS modes (Supported Codec Set modes). ACS modes (Active Codec Set modes)

DN9797631Issue 8-1 en

# Nokia Siemens Networks 57 (91)

Creating a cellular radio network

Page 58: Cellular Radio Network Management

You can output created mode sets with the E9O command. See theE9P and E9O commands for examples.

You can change used mode sets in an own radio network with theE2M 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 Resetprocedure to initiate the Iu-interface between the MSS and RNC.

Change the administrative state of an own RNC with the E2Scommand, by giving parameters of the following parameter groups:. RNC identification. State handling

See Logical grouping of RNC parameters in MSS concept forparameters in the above parameter groups.

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 followingparameter group:. RNC identification

See Logical grouping of RNC parameters in MSS concept forparameters 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 anauxiliary RNC with SS7 network administration MML.

For further information see Signalling Transport over IP, OperatingInstructions.

After you have performed this action, add the corresponding RNC addressto the cellular radio network file with the E2E command. You can alsodefine the RNC address in the cellular radio network file before creating itwith SS7 network administration MML.

58 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 59: Cellular Radio Network Management

The system creates an RNC in the LOCKED state. Change the state toUNLOCKED 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 thefollowing parameter groups:. RNC identification. Miscellaneous. RNC address

See Logical grouping of RNC parameters in MSS concept forparameters in the above parameter groups.

See the E2E command for examples.

2. List user plane destinations (E2L)

User Plane Destinations (UPD) can be created with the JFC UserPlane 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, bygiving parameters in the following parameter group:. UPD usage

See Logical grouping of RNC parameters in MSS concept forparameters in the above parameter groups.

See the E2L command for examples.

You can change user plane destinations in an auxiliary radio networkwith the E2F command.

3. Define mode sets for AMR codecs (E9P)

You can create, modify and delete mode set the AMR codecconfiguration with the commands of the General RNW ParameterHandling, E9 command group. The following parameters can begiven:. TYPE (mode set type). OM (optimization mode). SCS modes (Supported Codec Set modes). ACS modes (Active Codec Set modes)

You can output created mode sets with the E9O command. See theE9P and E9O commands for examples.

You can change used mode sets in an auxiliary radio network withthe E2F command.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 59 (91)

Creating a cellular radio network

Page 60: Cellular Radio Network Management

4. Change administrative state of auxiliary RNC (E2K)

Change the administrative state of an auxiliary RNC with the E2Kcommand, by giving the following parameter groups:. RNC identification. State handling

See Logical grouping of RNC parameters in MSS concept forparameters in the above parameter groups.

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 thefollowing parameter group:. RNC identification

See Logical grouping of RNC parameters in MSS concept forparameters in the above 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 sameas a cell in GSM. A service area in UMTS is handled the same way as aBTS.

The system creates a BTS/service area in LOCKED administrative state.To make the BTS/service area operational, change the administrative stateto UNLOCKED with the EPS command.

Note

Before you create a BTS or a service area, make sure that location areahas been defined in the MSC/MSS, in order to be able to connect theBTS/service area to it. If necessary, create a location area with the ELCcommand.

Before you can create the auxiliary service area, you have to create theauxiliary LA for that service area with the ELS command.

60 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 61: Cellular Radio Network Management

Steps

1. Create BTS/service area (EPC)

Create a BTS or service area with the EPC command, by giving thefollowing parameter groups:. 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 forparameters in the above parameter groups.

See the EPC command for examples.

2. Define LA-BTS-BSC relation (EPB)

When you create a BTS with the EPC command, you automaticallyconnect it to a location area.

You must define the BTS-BSC relation before you can UNLOCK theBTS with the EPS command.

Note

A BTS has to be in LOCKED state when you modify the LA-BTS-BSCrelation. If necessary, change the state to LOCKED with the EPScommand.

Define the LA-BTS-BSC relation with the EPB command, by givingparameters in the following parameter groups:. BTS/SA identification. LA–BTS–BSC relation

See Logical grouping of BTS/service area parameters forparameters in the above parameter groups.

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 theMSS-MGW Rel-4 concept.

The only possible value is MGWNBR=MSS, which indicates thatservice area is in the MSS concept.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 61 (91)

Creating a cellular radio network

Page 62: Cellular Radio Network Management

You will need to change the service area's administrative state toUNLOCKED with the EPS command after having defined the servicearea 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, bygiving the following parameter groups:. BTS/SA identification. MGWNBR=MSS

See Logical grouping of BTS/service area parameters forparameters in the above parameter groups.

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 EPScommand, by giving parameters in the following parameter groups:. BTS/SA identification. State handling

See Logical grouping of BTS/service area parameters forparameters in the above parameter groups.

See the EPS command for examples.

62 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 63: Cellular Radio Network Management

8.8 Sequence for creating a cellular radio network

Note

If either one of the Iu/A multipoint concepts are being used, you need toperform 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/MSSaccording to the instructions in Creating location areas, CreatingBSC, and Creating RNCs.

2. Create BTS/service area

Create each necessary BTS/service area according to theinstructions 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. Forfurther information, see User plane routing, Operating Instructions.

4. Create signalling connections

Create and activate the necessary signalling connections. For moreinformation, see Signalling Transport over IP, Operating Instructions.

5. Create routing connections

Create and activate the necessary routing connections for each BSCwith the RCC command (see Creating circuit groups and routes) andfor 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 toinstructions in Creating BSC, Creating RNCs, and Creating BTS/service area.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 63 (91)

Creating a cellular radio network

Page 64: Cellular Radio Network Management

Note

When creating a pool area concept, it is recommended to plan theactivation carefully and base the plans on the capacity need. Beforeyou start you should be aware of whether you want to implement thepool area concept at some point, and if so, keep the UMTS/GSMaccesses separate. For more information on creating the sequences forthe UMTS/GSM, refer to the Feature 1564: Multiple A Interface, FeatureActivation 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 ServingGPRS Support Node (SGSN), the main element in the General PacketRadio Service (GPRS) network.

The Gs interface, one of several G interfaces in the GPRS, is an optionalinterface between the MSC and the SGSN that allows the SGSN to sendlocation data to the MSC and receive paging requests from the MSC.

Figure 10. Gs interface between MSC and SGSN

Gs

ASGSN

BSS

MSC/VLR

Gb

GPRS MS (Class A and B)

64 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 65: Cellular Radio Network Management

The feature fully supports Class B GPRS mobiles, which allows them touse GPRS and circuit switched (CS) services simultaneously. It also saveson radio resources in PLMNs that support both CS and GPRS because:

. GPRS/IMSI attaches, routing, and location updates of class A and Bmobiles are combined

. CS paging is to a smaller area when done via SGSN

When you create a new SGSN connection, the program sets the SGSNdelay of the SGSN to the default value (zero). If necessary, you can modifythe 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 enablesyou to arrange location areas into roaming areas identified with a zonecode. The roaming areas associated with a zone code may includeanything from one location area up to a whole PLMN. Location areas in azone code do not need to be adjacent, hence you can create roamingareas 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 zonecodes for each subscriber.

When the subscriber does a location update to an LA, the system checksthe zone code data, and depending on the settings, allows or preventsroaming. 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.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 65 (91)

Creating a cellular radio network

Page 66: Cellular Radio Network Management

Steps

1. Create zone code (EKC)

Create a zone code with the EKC command. Give each zone code aunique hexadecimal identifier and name. You can then define theroaming and IN-MM triggering parameters. If you do not, the systemuses the default values which are: Roaming allowed in the zonecode 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 EKAcommand. 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 PoolArea.

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. Butalso in solely MOCN related environment, the NRI configuration needsto be defined by Feature 1847: Multi-Operator Core Network Support inMSS.

66 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 67: Cellular Radio Network Management

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 andcorresponding parameter groups:. Location area identification

(ELP). Radio channel assignment priority

(ELH). Roaming

(ELE, ELR). Miscellaneous

(ELE)

See Logical grouping of own/auxiliary location area parameters forparameters in the above parameter groups.

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 givingparameters in the following parameter groups:. Location area identification

(NAME or LAC or MCC and MNC). Output

See Logical grouping of own/auxiliary location area parameters forparameters in the above parameter groups.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 67 (91)

Optimizing a cellular radio network

Page 68: Cellular Radio Network Management

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 givingparameters in the following parameter groups:. Location area identification. Radio channel assignment priority. Roaming

See Logical grouping of own/auxiliary location area parameters forparameters in the above parameter groups.

See the ELM command reference for examples.

2. Output auxiliary location area data (ELJ)

Output auxiliary location area with the ELJ command, by givingparameters in the following parameter groups:. Location area identification

(NAME or LAC or MCC and MNC). Output

See Logical grouping of own/auxiliary location area parameters forparameters in the above parameter groups.

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 givingparameters in the following parameter groups:. Location area identification. Miscellaneous. New PLMN

See Logical grouping of network location area parameters forparameters in the above parameter groups.

See the EIM command reference for examples.

68 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 69: Cellular Radio Network Management

2. Output network location area parameters (EIO)

Output network location area with the EIO command, by givingparameters in the following parameter groups:. Location area identification

(NAME or LAC or MCC and MNC). Output

See Logical grouping of network location area parameters forparameters in the above parameter groups.

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 givingparameters in the following parameter group:. Location area identification

See Logical grouping of own/auxiliary location area parameters forparameters in the above 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 withthe EPF command.

Delete an auxiliary location area with the ELG command, by givingparameters in the following parameter group:

DN9797631Issue 8-1 en

# Nokia Siemens Networks 69 (91)

Optimizing a cellular radio network

Page 70: Cellular Radio Network Management

. Location area identification

See Logical grouping of own/auxiliary location area parametersforparameters in the above parameter group.

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 givingparameters in the following parameter group:. Location area identification

See Logical grouping of network location area parameters forparameters in the above parameter group.

9.3 Modifying BSC parameters

The EDR command for creating UP resources is related to the RCcommand group, used for Creating circuit groups and routes. If you havedefined the route(s) of the BSC with MML for creating TDM circuit groups(with the RCC command), you can add the corresponding route to thecellular radio network file with the EDR command. Or, you can define theSPC and SNC in the cellular radio network file before creating thecorresponding SPC with SS7 network administration MML. For moreinstructions, see Signalling Transport over IP, Operating Instructions.

Note

The BSC needs to be in LOCKED state with all of the followingcommands, except EDV, EDN, EDT. If necessary, change the state toLOCKED with the EDS command.

Steps

1. Modify BSC parameters

Modify a BSC with the following commands and correspondingparameter groups:

70 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 71: Cellular Radio Network Management

. BSC identification

. State handling

(EDS). UP resources

(EDR). CP resources

(EDL). Miscellaneous

(EDH, EDM, EDI, EDP). BSSAP version

(EDV, EDN, EDT). AMR modes (EDG)

See Logical grouping of BSC parameters for parameters in theabove parameter groups.

2. Output BSC data (EDO)

Output BSC data with the EDO command, by giving parameters inthe following parameter groups:. BSC identification. Output BSC data

See Logical grouping of BSC related parameters for parameters inthe 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, bygiving parameters in the following parameter groups:. BSC identification. Miscellaneous:

Cell identification method

See Logical grouping of BSC related parameters for parameters inthe above parameter groups.

See the EDM command for examples.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 71 (91)

Optimizing a cellular radio network

Page 72: Cellular Radio Network Management

9.3.2 Changing paging method

Steps

1. Change paging method (EDP)

Change the paging method with the EDP command, by givingparameters in the following parameter groups:. BSC identification. Miscellaneous:

paging method

See Logical grouping of BSC related parameters for parameters inthe above parameter groups.

See the EDP command for examples.

Note

The LAC or LAI paging method is recommended because it producesless signalling load between the MSC and the BSC than other pagingmethods. 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 EDIcommand, by giving parameters in the following parameter groups:. BSC identification. Miscellaneous:

Channel priority assignment function mode

See Logical grouping of BSC related parameters for parameters inthe above parameter groups.

See the EDI command for examples.

72 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 73: Cellular Radio Network Management

9.3.4 Changing reverse circuit allocation function mode

Note

Make sure the administrative state is LOCKED before you change thereversed circuit allocation function mode. If necessary, change it toLOCKED with the EDS command.

Feature 901: 2G FR AMR - HR AMR Speech Codec Support.

Steps

1. Change the reverse circuit allocation function mode <option> withthe EDH command, by giving parameters in the following parametergroups:. BSC identification. Miscellaneous:

Circuit allocation by BSS

See Logical grouping of BSC related parameters for parameters inthe above parameter groups.

See the EDH command for examples.

9.3.5 Modifying BSSAP version, version name, version information, andoutput 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 areidentified with a unique number called the BSSAP version.

You will need to modify the BSSAP version after creating a BSC becausethe system automatically attaches BSSAP version 15. You will also needto modify the BSSAP version if you give a reference object because theparameter values of the reference object are copied.

Steps

1. Modify BSSAP version, version name, version information, andoutput BSSAP version data

DN9797631Issue 8-1 en

# Nokia Siemens Networks 73 (91)

Optimizing a cellular radio network

Page 74: Cellular Radio Network Management

Modify BSSAP version with the EDV command, name of BSSAPversion with command EDN, BSSAP version information with theEDT command , and output BSSAP version data with the EDBcommand, by giving the following parameter groups:. BSC identification. BSSAP version. Output BSSAP data

See Logical grouping of BSC related parameters for parameters inthe above parameter groups.

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 thatthere is no BTS/SAC connected to it. If necessary, you can remove theBTS, by deleting the BTS–BSC relation with the EPB command, and theSAC, by changing the service area to MSS concept with the EPFcommand.

Ensure that the BSC/MGW is in LOCKED administrative state beforeyou delete it. If necessary, change the administrative state to LOCKEDwith the EDS command.

Steps

1. Delete BSC/MGW R99 (EDD)

Delete a BSC/MGW R99 with the EDD command, by givingparameters in the following parameter groups:. BSC/MGW R99 identification

Feature 1260: Inter-System Handover and UMTS Changes isrequired for you to be able to give TYPE=MGW.

. Reference BSC/MGW R99 identification

See Logical grouping of BSC related parameters for parameters inthe above parameter groups.

See the EDD command reference for examples.

74 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 75: Cellular Radio Network Management

9.5 Modifying RNCs

9.5.1 Modifying own RNC

You can define signalling system information (RNC address) for an ownRNC with SS7 network administration MML. For further information, seeSignalling Transport over IP, Operating Instructions. Once you have doneso, add the corresponding RNC address to the cellular radio network filewith the E2M command. You can also define the RNC address in thecellular radio network file before creating it with SS7 networkadministration 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 UNLOCKEDstate are VER, AMR, AMRCODEC, ADDMSET, REMMSET, LACLA andLACLR. If necessary, change the state to LOCKED with the E2Kcommand.

Steps

1. Modify own RNC (E2M)

Modify an RNC in an own radio network with the E2M command, bygiving the following parameter groups:. RNC identification. Miscellaneous. RNC address. LA-RNC relation

See Logical grouping of RNC parameters in MSS concept forparameters 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 getall RNCs for all PLMNs by default if you give only the RNCIDparameter. To interrogate data of RNCs in a particular PLMN, givethe PLMN parameters (MCC <option> and MNC <option>).

If you want to interrogate all RNCs that are attached to a specificuser plane destination, give the UPD or NUPD parameters.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 75 (91)

Optimizing a cellular radio network

Page 76: Cellular Radio Network Management

Interrogate own RNC with the E2I command, by giving the followingparameter group:. RNC identification

See Logical grouping of RNC parameters in MSS concept forparameters in the above parameter group.

See the E2I command for examples.

9.5.2 Modifying auxiliary RNC

You can define signalling system information (RNC address) for anauxiliary RNC with SS7 network administration MML. For furtherinformation, see Signalling Transport over IP, Operating Instructions. Onceyou have done so, add the corresponding RNC address to the cellularradio network file with the E2F command. You can also define the RNCaddress in the cellular radio network file before creating it with SS7network 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 UNLOCKEDstate 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 thefollowing parameter groups:. RNC identification. Miscellaneous. RNC address

See Logical grouping of RNC parameters in MSS concept forparameters in the above parameter groups.

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 theRNCID parameter. To interrogate data of RNCs in a particularPLMN, give the PLMN parameters (MCC <option> and MNC<option>).

76 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 77: Cellular Radio Network Management

If you want to interrogate all RNCs that are attached to a specificuser plane destination, give the UPD or NUPD parameters.

Interrogate an RNC in an auxiliary radio network with the E2Hcommand, by giving the following parameter group:. RNC identification

See Logical grouping of RNC parameters in MSS concept forparameters in the above 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 givingthe following parameter group:. RANAP version

See Logical grouping of RNC parameters in MSS concept forparameters in the above parameter group.

See the E2N command for examples.

2. Interrogate RNC version data (E2J)

Interrogate RNC version information with the E2J command, bygiving the following parameter group:. RANAP version identification

See Logical grouping of RNC parameters in MSS concept forparameters in the above parameter group.

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 theadministrative state to LOCKED with the E2S command.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 77 (91)

Optimizing a cellular radio network

Page 78: Cellular Radio Network Management

Steps

1. Delete own RNC (E2D)

Delete an RNC from an own radio network with the E2D command,by giving the following parameter group:. RNC identification

See Logical grouping of RNC parameters in MSS concept forparameters 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. Ifnecessary, change the administrative state to LOCKED with the E2Kcommand.

Steps

1. Delete auxiliary RNC (E2G)

Delete an RNC from an auxiliary radio network with the E2Gcommand, by giving the following parameter group:. RNC identification

See Logical grouping of RNC parameters in MSS concept forparameters in the above parameter group.

See the E2G command for examples.

9.7 Handling AMR mode sets

9.7.1 Modifying mode sets for AMR codecs

Steps

1. Define mode sets for AMR codecs (E9P)

Modify mode set information with the E9P command, by giving thefollowing data:

78 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 79: Cellular Radio Network Management

. TYPE (mode set type)

. ID (mode set ID)

. OM (optimization mode)

. 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 givingthe 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 EPRcommand, by giving parameters in the following parameter groups:. BTS/SA identification. Miscellaneous

See Logical grouping of BTS/service area parameters forparameters in the above parameter groups.

See the EPR command for examples.

2. Outputting BTS/service area (EPO)

Output BTS/service area data with the EPO command, by givingparameters in the following parameter groups:. BTS/SA identification. Output data group

See Logical grouping of BTS/service area parameters forparameters in the above parameter groups.

See the EPO command for examples.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 79 (91)

Optimizing a cellular radio network

Page 80: Cellular Radio Network Management

9.8.2 Modifying traffic reason handover

Steps

1. Modify traffic reason handover (EPH)

Modify traffic reason handover with the EPH command <option>, bygiving parameters in the following parameter groups:. BTS identification. Traffic reason handover

See Logical grouping of BTS/service area parameters forparameters in the above parameter groups.

See the EPH command for examples.

9.8.3 Modifying resource indication

The resource indication function provides the MSC with information aboutthe number of free traffic channels in a cell.

Steps

1. Modify resource indication (EPI)

Modify resource indication with the EPI command, by givingparameters in the following parameter groups:. BTS identification. Resource indication

See Logical grouping of BTS/service area parameters forparameters in the above parameter groups.

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 neighborhoodwith the EPN command, by giving parameters in the followingparameter groups:. BTS identification. Neighborhood

80 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 81: Cellular Radio Network Management

See Logical grouping of BTS/service area parameters forparameters in the above parameter groups.

See the EPN command for examples.

9.9 Deleting BTS/service area

Note

By deleting a BTS/service area, you are also removing it fromneighboring cell lists.

Note

The BTS and service area have to be in LOCKED state when youdelete them. If necessary, change the administrative state with the EPScommand.

Steps

1. Delete BTS/service area (EPD)

Delete a BTS/service area with the EPD command, by givingparameters in the following parameter group:. BTS/SA identification

See Logical grouping of BTS/service area parameters forparameters in the above parameter group.

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 andalso for exporting/importing network pool area configuration in MSS.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 81 (91)

Optimizing a cellular radio network

Page 82: Cellular Radio Network Management

9.10.1 Modify pool area

Steps

1. Modify pool area

Modify pool area with the E3M command. If command is given for thefirst time own pool area is created and the POOLNAME and NRILENparameters 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 thepool area, all MSSs under it must be removed with the E3Dcommand.

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 E3Acommand.

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 ismodified, then you can only give the following parameters with thecommand: NNAME, CONFSEL, NRIADD, NRIREM, MAINT, MNRI, PNRI<option>, NRIVALC <option>, STOPLEV <option>, TIMER<option>, NBLAC, NBMCC <option> and NBMNC <option>.

82 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 83: Cellular Radio Network Management

9.10.5 Remove MSS from pool area

Steps

1. Remove MSS from pool area

Remove MSS from pool area with the E3D command. Beforeremoving an own or parallel MSS from own pool area, you mustremove the NRI's from the particular MSS with the E3E commandfirst.

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 aneighbor pool area all MSSs under it must be removed first with theE3G command.

Note

Before removing an MSS, you must first remove the NRI's from thatparticular 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 theneighbor pool area.

Steps

1. Modify MSS in neighbor pool area

DN9797631Issue 8-1 en

# Nokia Siemens Networks 83 (91)

Optimizing a cellular radio network

Page 84: Cellular Radio Network Management

You can modify the parameters of MSSs in the neighbor pool areawith 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 E3Gcommand. Remember that before removing an MSS, you must firstthe 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 radionetwork 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 EDScommand , RNC with the E2S command, and BTS/service area withthe EPS command.

2. Delete BTS-BSC and service area-MGW R99 relations

Delete BTS-BSC relation (EPB command) and service area-MGWR99 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 ELDcommand.

84 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 85: Cellular Radio Network Management

9.12 Transferring BSCs between MSCs/MSSs

Transferring of BSCs between MSCs/MSSs may be required for capacityreasons. 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 untilyou have tested the BSC in the new MSC/MSS. Lock the BSC in the oldMSC/MSS to prevent usage.

In radio network configuration you can have duplicate location areas underan MSC/MSS by means of the identical LAC switch (ILS) parameter. Thisprocedure 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 includethe whole LA, and the LA remains in the old MSC/MSS. The transferredBSC cells are defined for the LA in the target MSC/MSS. Again, the BSCand cells are locked in the old MSC/MSS, and removed only after thetransfer has been successfully completed. The LA in the target MSC/MSSis 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 createand activate signalling connections between the two elements. For moreinformation on signalling configuration see Signalling Transport over IP,Operating Instructions.

The following figure illustrates a BSC named SORIBSC being transferredto another MSC/MSS.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 85 (91)

Optimizing a cellular radio network

Page 86: Cellular Radio Network Management

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 toinstructions in Section Creating own location area.

If the location area has already been defined in the MSC/MSS as anetwork location area, use the ILS parameter.

When using the ILS parameter, make sure that all the cells in alocation area are connected to one BSC. A location area that issimultaneously active in an old and new MSC/MSS will cause inter-MSC handover problems. The ILS parameter is to be usedtemporarily only.

2. Add network LA

Add network location area according to instructions in Addingnetwork location area.

LAC3030

TSL 16MSC2

SPC=234567

MSC1SPC=16382 SORI

BSCSPC=B30

Signalling link number 30Signalling link set REBSCExternal route number 500

PCM 105

BTS311

86 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 87: Cellular Radio Network Management

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 systeminformation 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/servicearea.

2. Define LA-BTS-BSC relation

Define the LA-BTS-BSC relation according to instructions inCreating 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 inModifying 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

DN9797631Issue 8-1 en

# Nokia Siemens Networks 87 (91)

Optimizing a cellular radio network

Page 88: Cellular Radio Network Management

Change administrative state of BSC with the EDS command andBTS 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 forfurther 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 EPScommand.

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 theconfiguration from the old MSC.

88 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 89: Cellular Radio Network Management

Steps

1. Delete BTSs of transferred BSC

Delete BTSs of the transferred BSC according to instructions inDeleting 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 Deletingown location area.

4. Delete duplicate network LA definition of BSC in new MSC/MSS

Delete BSC's duplicate network location area definition from the newMSC/MSS according to instructions in Deleting network locationarea.

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 incomparison with paging across an A-interface. The system uses the delayvalue 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 parameterwith 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.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 89 (91)

Optimizing a cellular radio network

Page 90: Cellular Radio Network Management

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 codewith the EKM command. Identify the zone code by its hexadecimalidentifier 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 canoutput all location areas (default value) or only location areasincluded 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 roamingor IN-MM triggering, or the ones that do not allow roaming or IN-MMtriggering. The default value is all zone codes that include thelocation 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)

90 (91) # Nokia Siemens Networks DN9797631Issue 8-1 en

Cellular Radio Network Management

Page 91: Cellular Radio Network Management

Delete zone codes, one at a time, with the EKD command.

See the EKD command for examples.

DN9797631Issue 8-1 en

# Nokia Siemens Networks 91 (91)

Optimizing a cellular radio network