00 rn20080en12gln1 introduction to parameter planning

Introduction to Parameter Planning

Training DocumentBSSPAR: CTXX 010

RN20080EN12GLN1v 3.0

© Nokia Siemens Networks 1 (21)

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

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

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

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

NOKIA logo is a registered trademark of Nokia Oyj.

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

Copyright © Nokia Oyj 2008. All rights reserved.




Contents

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

2 Managed Object Classes and Parameter Sets...........5

3 BSC Level Parameters..................................................8

4 BCF Level Parameters..................................................9

5 BTS, SEG, TRX, & RTSL Level Parameters..............10

6 ADJC, UADJC, HOC, & POC Parameters..................11

7 Parameter Dictionaries...............................................127.1 Parameter Properties....................................................12

8 New Objects and Parameters....................................15

9 Parameters & Timer Handling In PRFILE & PAFILE 169.1 PRFILE.........................................................................169.2 PAFILE..........................................................................17

10 Influence of Parameters During Call Phases...........18

11 Optional Features.......................................................20

12 Parameter Planning Impacts......................................21

13 The BSS Parameter Planning Course..........................22



1 Module Objectives

At the end of the module, the participant will be able to:

Sketch a BSS Managed Object Hierarchy

Look up the parameters at each level, in a parameter dictionary

Identify parameter value ranges and default settings




2 Managed Object Classes and Parameter Sets

Radio Network Management of a cellular network is an important function to ensure that the network is performing all its tasks (e.g. call set-ups and handovers). RNW configuration is a continuous process where parameters may be changed often due to maintenance work, optimisation or site re-structuring.

The BSC radio network configuration management provides the operator with the means of controlling the radio network configuration data stored in the BSS Radio Network Configuration Database (BSDATA).

At the top-level user interface of the Nokia NMS, the management of various network elements and managed objects is structured in the hierarchical manner as shown below.

The Nokia NMS keeps a record of the parameters, states, configuration, and other relevant details of each cell in the database. In doing so, the operator can see via the NMS the current parameters. It is possible that different sets of parameters can be stored building up a history of parameters.

Figure 1. Managed Object Hierarchy

The BSC is the parent object and has a number of child objects below it, some of which in turn have other children below them. The objects may represent real network elements (e.g. BCF, BTS) or functional objects



ADJC FHS

RTSL

TRX HOC POC

BTS

HW-DB

BTS-SW

BCFMABA

BSC

UPDATE

that represent a function of a unit (e.g. Handover Control, Power Control).

The Managed Objects shown in Figure 1 are:

Base Station Controller (BSC)

Base Control Function (BCF)

Base Station (BTS) and, not shown (SEG)

Transceiver (TRX)

Radio Timeslot (RTSL)

Handover Control Parameters per cell (HOC)

Power Control Parameters per cell (POC)

Adjacent Cell definitions (ADJC)

Frequency Hopping per cell (FHS)

BCCH Allocation Frequency List (BA)

Mobile Allocation Frequency List (MA)

The following operations on managed objects are supported:

1. Creating and removing objects (BCF, BTS, SEG, TRX, ADJC, BA, MA) in the database.

2. Changing of parameter values. The change is distributed and activated immediately.

3. Changes in the following objects are possible on-line, i.e., they do not cause any break in the service: BSC level parameters, handover and power control parameters, adjacent cell definitions, BA frequency lists, most of the cell parameters.

4. Managing frequency hopping (both baseband hopping and radio frequency hopping).

5. Interrogating parameter values.

6. Changing the administrative state (LOCKED/UNLOCKED) of the object (BCF, BTS, TRX, and RTSL).

7. Displaying the operational states of the functional entities (BCF, BTS, TRX, and RTSL).

In an enhancement 'Radio Network MML Improvement' there are improvements for Output Radio Network Configuration and Check Adjacent Cell Data MML commands. There is also a command for checking that the amount of IUO interfering cell definitions does not exceed the allowed maximum.




The enhancement 'Guard Channel Management' enables the use of guarded channels by controlling the maximum TRX transmit power. The FCC, the local regulator in the USA, has set certain emission limits for GSM1900 equipment to ensure that an operator on a band does not interfere with another operator on the adjacent bands.



3 BSC Level Parameters

The BSC level parameters available in software are given in Section 2 of the BSS Radio Network Parameter Dictionary. There are at least 82 BSC level parameters dealing with alarms and features. The following is an example of a BSC level parameter definition as it can be found in that dictionary.

Figure 2. Example of a BSC Level Parameter

The meanings of the attributes of the above-mentioned parameter such as range, MML default will be discussed later in this module.

The setting of a BSC parameter is valid for all cells served by this BSC.




4 BCF Level Parameters

A BCF is the logical supervision entity of a Base Station cabinet or site. It may contain a number of sectors (BTS's), but it is controlled by a single supervision link (BCFSIG LAPD). The BCF object contains BSC-specific radio network data. The BCF level parameters available in software are given in Section 3 of the BSS Radio Network Parameter Dictionary. There are at least 21 BCF level parameters. The following is an example of a BCF level parameter definition, found in that dictionary.

Figure 3. Example of a BCF Level Parameter



5 BTS, SEG, TRX, & RTSL Level Parameters

The BTS, SEG, TRX, and RTSL level parameters available in software are given in Sections 5, 6, 17, and 18 of the BSS Radio Network Parameter Dictionary. There are at least 59 BTS level parameters, 126 SEG level parameters, 43 TRX level parameters, and 3 RTSL level parameters.

Many of the parameters that were previously at BTS level, have now been transferred to SEG level. The following is an example of a BTS level parameter definition (PMIN), found in that dictionary.

Figure 4. Example of a BTS Level Parameter




6 ADJC, UADJC, HOC, & POC Parameters

Each adjacent cell (ADJC and UADJC) object contains a description of one of the adjacent cells of a BTS. The handover control object (HOC) contains parameters controlling the handover procedure to and from a BTS. The power control object (POC) contains parameters controlling the power control procedure within a BTS.

The ADJC, UADJC, HOC, and POC level parameters used in software are given in Section 7, 8, 9, and 10 of the BSS Radio Network Parameter Dictionary. There are at least 45 ADJC level parameters, 11 UADJC level parameters, 85 HOC level parameters, and 39 POC level parameters.



7 Parameter Dictionaries

The aim of a parameter dictionary is to assist radio network planning and optimisation engineers and other BSC users to find certain BSS parameters, their meanings, properties and relation to the GSM specifications. Parameters that are in other databases or files are not listed here.

There are two parameter dictionaries that we can use during this course:

1. BSS Radio Network Parameter Dictionary that contains BSS parameters. The values can be modified using MML commands.

2. BSS and NSS RNW Parameter Dictionary that contains BSS and NSS parameters. The values can be modified using NMS (NetAct) GUI or MML commands.

There may be new parameters with newer software releases, as well default or range of existing parameters may change. So always use the current relevant or latest versions of the parameter dictionaries available from NOKIA.

7.1 Parameter Properties

The parameter dictionary gives the following properties for each parameter:

• GSM reference: the name of standard in which the parameter is defined

• Q3 name: the name of the parameters that is used on the GUI

• Modification: states how the parameters can be modified, e.g. Online, Offline.

• Range: the range of values that the parameter can take

• MML default value: the default value of the parameter

• Description of what the parameter is used for in the BSS

• Related command(s) that perform a function relevant to this parameter

Note: Optional parameters are marked as OPTIONAL. The name of the optional feature that needs to be activated before the parameter is taken into use is given in brackets. For example: OPTIONAL (Intelligent Shutdown with Timer Control) means that the parameter is optional and is in use when the feature Intelligent Shutdown with Timer Control is activated.




The activation of an OPTIONAL feature requires a SW licence and appropriate payment.

A typical parameter description given in the BSS and NSS Radio Network Dictionary is shown in Figure 5. The parameter definitions in this dictionary show additional properties such as NMS (NetAct) GUI Range.

Figure 5. Example from the BSS and NSS RNW Parameter Dictionary

For most parameters, the default value is also the recommended value. An exception to this rule occurs when the default value has turned off a function or feature, which the operator wants to use. Another exception that applies to a small number of parameters is when experience has shown that the recommended value should be somewhat different to the default value.

The recommended parameter values are dependent on the network configuration, local conditions, and the operator. They may change with time.



8 New Objects and Parameters

For every BSS software release, the parameter dictionary is updated. Objects and parameters may be added, modified, or removed.

All these changes, including new parameters, are listed in the Section 'Summary of changes' at the beginning of the BSS Radio Network Dictionary. The new parameters are listed in order, according to the RNW Managed Objects such as BSC, BTS, Adjacent Cell, etc.

Figure 6. Example of a Previous Summary of changes

Changes to MML's are not covered in detail in the dictionary. However there is, at the end of the dictionary, a section called ‘Related command list’.




9 Parameters & Timer Handling In PRFILE & PAFILE

Parameters are handled in the BSC with the aid of two parameter files:

PRFILE (General Parameter File) and

PAFILE (BSC Control Parameter File)

All the information about controlling the standard and optional features of the BSC is stored in the PRFILE. The file is administered (output the status, or make a modification) with the parameter handling MML program, command group WO (ZWOx commands).

The PAFILE is used for storing modified values of GSM-BSC parameters.

When an application is started, it first reads its parameters and timers from the PAFILE system file. If the PAFILE system file is empty, the application uses the general default values. The application arranges its internal parameters and timers according to the parameters and timers it has read from the PAFILE system file. If the system file contains values for a timer or a parameter used by the application, the application updates its values.

9.1 PRFILE

The BSC has a group of features that are not included in the basic software, but the customer can choose them to be included in the software (OPTIONAL features). There is also a group of features that are typical in all BSCs, but the extent of their use depends on the delivery (standard features).

All the information about controlling the above features is assembled in the BSC in the PRFILE (General Parameter File). One can modify and interrogate the contents of the file with the Parameter Handling MML (PRHAND) WO command group, ZWOx commands.

The WO command group menu is:

PARAMETER HANDLING COMMANDS

? ….. DISPLAY MENUC: ….. CHANGE PARAMETER VALUEI: ….. INTERROGATE PARAMETER VALUEP: ….. CREATE NEW PARAMETERL: ….. CREATE NEW PARAMETER CLASS



O: ….. LIST AND OUTPUT OPTIONAL FEATURESF: ….. ACTIVATE/DEACTIVATE OPTIONAL FEATUREZ: ….. RETURN TO MAIN LEVEL

The commands ZWOP CREATE NEW PARAMETER, and ZWOL CREATE NEW PARAMETER CLASS, are not available to the customer, and will probably be removed.

9.2 PAFILE

Parameter Administration provides the operator with the means of outputting and modifying the parameters and timers stored in the BSC Control Parameter File (PAFILE) in the BSC. Timers refer to GSM timers specified in the GSM specifications. It also provides and checks the restrictions and ranges of the parameters and timers, and stores the data in a system file. This file is supplied to all computer units. It is possible to output and modify these parameters and timers by means of the local MML.

PAFILE is used for storing modified values of GSM/BSC parameters. The record number and default value of each parameter are defined to the data types in the system environment. The GSM Timer and BSC Parameter Handling (GPAHAN) EG group commands, (ZEGx commands), are used to display and modify the values of GSM timers and BSC parameters.

If parameters or timers are modified with the MMI, the values will be stored in the system file. All applications are supposed to read the system file at regular intervals, as they have to update their relevant parameters. Thus, the modification of parameters is updated in all applications within 5 minutes.

The EG command group menu is:

GSM TIMER AND BSC PARAMETERS HANDLING COMMANDS

? ….. DISPLAY MENUO: ….. OUTPUT TIMERS/PARAMETERST: ….. MODIFY TIMERP: ….. MODIFY PARAMETERSZ: ….. RETURN TO MAIN LEVEL




10 Influence of Parameters During Call Phases

Parameter settings have a major influence on the quality of each call or other transaction made via the air interface. They therefore directly affect the extent to which network KPI’s (Key Performance Indicators) are achieved.

The various call phases during a mobile originated call (MOC) are shown below. The parameters set by an operator have a major influence on the signalling that takes place during the call phases.

Figure 7. MOC Call Phases



MS BTS BSC

AUTHENTICATION (SDCCH)Phase 2 : MM signalling

CIPHERING MODE (SDCCH)Phase 8 : Ciphering

TMSI REALLOCATION (SDCCH)

SETUP (SDCCH)

Phase 2 : MM signalling

CH. REQUEST (RACH)

IMMEDIATE ASSIGN(AGCH)

SERVICE REQUEST (SDCCH)

Phase 1 : Paging, initial MS

CH.RELEASEPhase 4 : Release

ALERTING & CONNECT (FACCH)Phase 2 : MM signalling

CONN. ACK. and MEASUREMENTPhase 15 : Conversation

DISCONNECT & RELEASE (FACCH) Phase 4 : Release

ASSIGNMENT (SDCCH-FACCH)Phase 3 : Basic assignment

There are 11 signalling procedures used, during the 15 possible phases of a basic call or other transaction, to provide CS speech or CS data services to a subscriber:

1. The paging procedure used to page a mobile to start the establishment of a mobile terminating call (MTC) with a mobile station (MS).

2. The channel required procedure starts the establishment of a mobile originating call (MOC) or to answer the PAGING REQUEST message.

3. Channel reservation procedure: used to request a dedicated signalling channel.

4. Channel activation procedure: After a successful reservation of a new channel, the BSC activates it by sending this message to the BTS.

5. The IMMEDIATE ASSIGN message facilitates assignment of the MS onto an SDCCH channel; the IMMEDIATE ASSIGN REJECT message facilitates refusal of the access sent by the MS.

6. The BSC starts the SCCP connection establishment procedure for the MS after receiving the ESTABLISH INDICATION message for the SDCCH establishment from the BTS.

7. Transmission of Transparent L3 messages is used in communication between the MS and the MSC. The BTS and the BSC forward the transparent messages.

8. Ciphering procedure is one of the security procedures designed to protect the subscriber identity and data.

9. Assignment procedure is used in assigning the MS to the correct TCH channel.

10. Channel release procedure is used for releasing a dedicated radio channel.

11. System information broadcasting procedure: The network periodically broadcasts messages on the BCCH. Some of this information influences the cell reselection made by the mobiles.

Cell reselection criterion C1 enables the MS to select a cell. The C2 reselection criterion may be defined by the operator for example in an environment where there is coverage by both a micro cell and a macrocell.

The parameters affecting C1 and C2 are covered in BSSPAR Module 2 “Idle Mode Operation”.




11 Optional Features

Application features With the Feature Management MML, the operator is able to list the feature options in the BSC and turn the operator-specific options in the BSC package on or off.

Feature management MML commands perform these functions:

list OPTIONAL features in the software package of the BSC, and show if they are on or off

turn on an OPTIONAL feature

turn off an OPTIONAL feature

Each feature may be controlled by a number of additional feature-specific parameters. These parameters are handled separately by using corresponding management commands.

The LIST command will show all OPTIONAL features that are included in that particular SW package. The MML commands related to each feature are shown regardless of the state of the feature, so the operator will be able to see and modify a detailed feature parameter, even when the feature has been turned off by the operator at the BSC level.

The TURN ON command will activate the feature to work, according to the BSC level, or cell level, parameter settings related to this feature. The TURN OFF command will deactivate the feature in the BSC.

For example: Activate the E-OTD Position Based Services (WOA)

Activate the Position Based Services feature in the BSC with control parameter PBS_USAGE. The parameter is in the off state after the software update and must be set on:

ZWOA: 2, 654, A;

Where:

Parameter class 2 is SYSTEM_FUNCT_CONFIGUR

Parameter number 654 is PBS_USAGE

Activate Feature A



12 Parameter Planning Impacts

The parameter planning process is a vital step after the network rollout. Parameters available in the Nokia BSS may be classified as follows:

BSC, BCF, BTS, and SEG parameters

BTS parameters for Adjacent Cells, ADJC and UADJC

BTS parameters for Handover Control (HOC)

BTS parameters for Power Control (POC)

BA and MA parameters

TRX & RTSL parameters

LCSE related parameters, and SMLC, LMUA, Repeater, RITTT

Other special-purpose parameters: IO_TEXT; RA; NSE; NS_VC; TRK_TBL; DAP




13 The BSS Parameter Planning Course

The material presented in the modules of this BSSPAR course contains explanations and examples of Base Station Subsystem (BSS) Parameters, including parameters related to Radio Network Planning. The material refers to parameters that are currently available in a Nokia BSS. There are GSM Phase 2 parameters implemented and identified.

All the parameters, which can be found in the BSC and the NMS (NetAct), are written in bold format, for example cellReselectHysteresis (HYS)(SEG)(0, 2, 4, ..14dB)(4dB).

After the long name of each parameter (e.g. cellReselectHysteresis), there is a short name (e.g. HYS), the object level (e.g. SEG), the range of values (e.g. 0..14dB), and the MML default value (e.g. 4dB).



00 rn20080en12gln1 introduction to parameter planning

Documents