parameters b11

Alcatel-Lucent GSM

Telecom Parameters Dictionary

OMC Document

Reference Guide

Release B11

3BK 21624 AAAA PCZZA Ed.09

Status RELEASED

Short title

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel.

BLANK PAGE BREAK

2 / 1278 3BK 21624 AAAA PCZZA Ed.09

Contents

ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 Parameter Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Parameter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 VGCS Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 LCS Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.1 Network (CDE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.2 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4 IP Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.1 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5 GSM Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155.1 Network (CDE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165.2 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2055.3 System (CST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787

6 GPRS Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7896.1 Network (CDE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7906.2 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836

7 E-GPRS Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11797.1 Network (CDE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11807.2 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183

8 DTM Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12038.1 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204

9 2G-LTE Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12079.1 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208

10 2G-3G Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123510.1 Network (CDE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123610.2 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237

3BK 21624 AAAA PCZZA Ed.09 3 / 1278

Contents

4 / 1278 3BK 21624 AAAA PCZZA Ed.09

Preface

PrefacePurpose The BSS Parameter Dictionary lists all of the Telecom Parameters for GSM

and GPRS.

Whats New In Edition 09This document was generated from the edition 18rl of the BSS TelecomParameters database.

In Edition 08This document was generated from the edition 17rl of the BSS TelecomParameters database.







3BK 21624 AAAA PCZZA Ed.09 5 / 1278

Preface

In Edition 01First official release of document.

Audience This manual is designed for OMC-R users, O&M technicians and systemdesigners.

Assumed Knowledge Not applicable.

6 / 1278 3BK 21624 AAAA PCZZA Ed.09

1 Introduction

1 Introduction

3BK 21624 AAAA PCZZA Ed.09 7 / 1278

1 Introduction

1.1 Parameter ClassificationThe GSM and GPRS parameters are classified into three categories:

Network: customer dependent parameters, related to the network topology,defined by the customer and valid for the complete network (e.g. BTS name,Cell ID, LAC number ...). They can be adjusted by CDE scripts.Site: adjustable parameters from one cell to the next or from one BSC to thenext. They are set to a default value. They can be adjusted from the OMC-R.System: fixed parameters, i.e. BSS system mandatory rules orautomatically populated in the DLS skeleton and let unchanged becausenot customer dependent. Some of them are coded in BTS Software andconfiguration files.

1.2 Parameter DescriptionTo each parameter are associated the following characteristics:

Logical Parameter Name: Mnemonic conventionally used in Alcateldocumentation.

Definition: definition/purpose of the parameter.

Coding rules:, Rules of coding, when necessary.

Mandatory rules: Mandatory relationships or inter-dependence of somedata.

Recommended rules: Recommended relationships or inter-dependenceof some data.

Feature: Indicates to which feature the parameter is linked.

Category: Category into which the parameter is classified.

Instance: Possible instance of the parameter.

ValueMin/Max values: Possible range of the parameter values.Default value: Parameter value in release B9 for a generic configuration.

Modifiable: Indicates if the parameter is modifiable at the OMC-R.

Parameter Access: Indicates where the parameter is accessible at theOMC-R.

External Comments: Specific information, when necessary, relatedto the parameter.

8 / 1278 3BK 21624 AAAA PCZZA Ed.09

2 VGCS Telecom Parameters


3BK 21624 AAAA PCZZA Ed.09 9 / 1278


2.1 Site (CAE)2.1.1 (CELL_RESELECT_HYSTERESIS(n)) -

(CELL_RESELECT_HYSTERESIS(n))HMI Name CELL_RESELECT_HYSTERESIS(n)Parameter Name

Logical Name CELL_RESELECT_HYSTERESIS(n)Definition Level hysteresis for cell reselection applied when the new cell is in

a different location area.

Coding rules step size = 2dB; coded on 3 bits (000 : 0 dB, 111 : 14 dB)

Mandatory rules

Recommended rules

Category Site (CAE)Type Number

SubSystem BSC

Instance cell

Unit Minimum Maximum DefaultValue

dB 0 14 6

External Comment

Cell Type Dependent No

Nb of TRX Dependent No

10 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.2 (CELL_RESELECT_OFFSET) -(CELL_RESELECT_OFFSET(n)(BSC))

HMI Name CELL_RESELECT_OFFSETParameter Name

Logical Name CELL_RESELECT_OFFSET(n)(BSC)Definition Permanent offset to C2 criterion.

Coding rules step size = 2dB; coded on 6 bits (000000:0 dB, 111111 : 126 dB)

Mandatory rules CELL_RESELECT_OFFSET(n)(MFS) =CELL_RESELECT_OFFSET (n)(BSC)

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance cell


dB 0 126 0

External Comment



3BK 21624 AAAA PCZZA Ed.09 11 / 1278


2.1.3 (EN_INBAND_NOTIF) - (EN_INBAND_NOTIF)HMI Name EN_INBAND_NOTIFParameter Name

Logical Name EN_INBAND_NOTIF

Definition Flag to disable/enable the in-band notification

Coding rules 0: disabled, 1:enabled

Mandatory rules

Recommended rules

Category Site (CAE)

Type Flag

SubSystem BSC

Instance BSC


None 0 1 0

External Comment



12 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.4 (EN_INBAND_PAGING) - (EN_INBAND_PAGING)HMI Name EN_INBAND_PAGINGParameter Name

Logical Name EN_INBAND_PAGING

Definition Flag to disable/enable the in-band paging

Coding rules 0: disabled, 1: enabled

Mandatory rules

Recommended rules

Category Site (CAE)

Type Flag

SubSystem BSC

Instance BSC


None 0 1 0

External Comment



3BK 21624 AAAA PCZZA Ed.09 13 / 1278


2.1.5 (EN_UPLINK_REPLY) - (EN_UPLINK_REPLY)HMI Name EN_UPLINK_REPLYParameter Name

Logical Name EN_UPLINK_REPLY

Definition Flag to disable/enable the uplink reply procedure


Mandatory rules

Recommended rules

Category Site (CAE)Type Flag

SubSystem BSC

Instance BSC


None 0 1 0

External Comment



14 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.6 (EN_VGCS) - (EN_VGCS)HMI Name EN_VGCSParameter Name

Logical Name EN_VGCS

Definition Flag to disable/enable the VGCS in the cell


Mandatory rules

Recommended rules When the VGCS feature (EN_VGCS) is activated, it is recommendedto- include the Response Request in the HANDOVER REQUIREDmessage (RESP_REQ).- to configure, at least, one TRX with TRX_PREF_MARK 0 in thecell.- to set EN_TCH_PREEMPT to enabled, otherwise to set the valueof MIN_VGCS_TS to a value greater or equal to 2


SubSystem BSC

Instance cell


None 0 1 0

External Comment



3BK 21624 AAAA PCZZA Ed.09 15 / 1278


2.1.7 (INBAND_PAGING_THR) - (INBAND_PAGING_THR)HMI Name INBAND_PAGING_THRParameter Name

Logical Name INBAND_PAGING_THR

Definition If the eMLPP priority included in the Paging message from the MSCis higher than or equal to this parameter, then the BSS shall triggerin-band paging within cells, that are identified to be paged from thePAGING message, and that have existing VGC active.

Coding rules Coded over 3 bits000 : deactivation of inband paging001 : call priority level 4 (lowest priority)010 : call priority level 3011 : call priority level 2100 : call priority level 1101 : call priority level 0110 : call priority level B111 : call priority level A (highest priority)

Mandatory rules

Recommended rules

Category Site (CAE)

Type Threshold

SubSystem BSC

Instance cell


None 0 7 4

External Comment



16 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.8 (MAX_VGCS_TS) - (MAX_VGCS_TS)HMI Name MAX_VGCS_TSParameter Name

Logical Name MAX_VGCS_TS

Definition Maximum number of radio timeslots that can be used by the VGCScalls in the cell.

Coding rules

Mandatory rules MIN_VGCS_TS 0



3BK 21624 AAAA PCZZA Ed.09 17 / 1278


2.1.9 (MIN_VGCS_TS) - (MIN_VGCS_TS)HMI Name MIN_VGCS_TSParameter Name

Logical Name MIN_VGCS_TS

Definition Minimum number of radio timeslots that are reserved for the VGCScalls in the cell in normal situation (point-to-point CS call can NOTuse these timeslots).

Coding rules

Mandatory rules MIN_VGCS_TS


2.1.10 (MS_TXPWR_MAX_CCH) - (MS_TXPWR_MAX_CCH(n)(BSC))HMI Name MS_TXPWR_MAX_CCHParameter Name

Logical Name MS_TXPWR_MAX_CCH(n)(BSC)Definition Maximum transmission power an MS is allowed to use when

accessing the cell until otherwise commanded, broadcast on PBCCHfor CS service establishment.

Coding rules P-GSM/G1 coding: step size = 2 dBm; 0: 43 dBm, ..., 19: 5 dBm.GSM 850 coding: step size = 2 dBm; 0: 39 dBm, 1: 39 dBm, 2: 39dBm, 3: 37 dBm, 4: 35 dBm,..., 19: 5 dBm.DCS 1800 coding:step size = 2 dBm; 0: 30 dBm, ..., 15: 0 dBm.DCS 1900 coding: range 0 to 15, 30, 31; 30: 33 dBm, 31: 32 dBm,0: 30 dBm, 1: 28 dBm, ..., 15: 0 dBm.

Mandatory rules

Recommended rules


SubSystem BSC

Instance cell


dBm 5 43 43

External Comment According to the 3GPP TS 05.05, if the BCCH frequency band isP-GSM/G1, depending on the version of MS (Phase 1 MS or Phase2/onwards MS), the coded value "0", "1" and "2" are interpreteddifferently:- Coded value "0": (interpreted as 43 dBm by the Phase 1 MS;interpreted as 39 dBm by the Phase 2/onwards MS);- Coded value "1": (interpreted as 41 dBm by the Phase 1 MS;interpreted as 39 dBm by the Phase 2/onwards MS);- Coded value "2": (interpreted as 39 dBm by both the Phase 1 MSand the Phase 2/onwards MS).



3BK 21624 AAAA PCZZA Ed.09 19 / 1278


2.1.11 (NOTIF_FACCH_OTHER_VGCS_CALL_THR) -(NOTIF_FACCH_OTHER_VGCS_CALL_THR)

HMI Name NOTIF_FACCH_OTHER_VGCS_CALL_THRParameter Name

Logical Name NOTIF_FACCH_OTHER_VGCS_CALL_THR

Definition If the eMLPP priority is higher than or equal to this parameter, theNotifications message shall be sent on FACCH of all other on-goingVGCS call.

Coding rules Coded over 3 bits000 : deactivation of notification on FACCH of other on-going VGCScalls001 : call priority level 4 (lowest priority)010 : call priority level 3011 : call priority level 2100 : call priority level 1101 : call priority level 0110 : call priority level B111 : call priority level A (highest priority)

Mandatory rules

Recommended rules

Category Site (CAE)Type Threshold

SubSystem BSC

Instance cell


None 0 7 0

External Comment



20 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.12 (NOTIF_FACCH_PTP_CALL_THR) -(NOTIF_FACCH_PTP_CALL_THR)

HMI Name NOTIF_FACCH_PTP_CALL_THRParameter Name

Logical Name NOTIF_FACCH_PTP_CALL_THR

Definition If the eMLPP priority is higher than or equal to this parameter, theNotifications message shall be sent on FACCH of all on-going pointto point call whose MS is VGCS capable.

Coding rules Coded over 3 bits000 : deactivation of notification on FACCH of all on going point topoint calls in the cell001 : call priority level 4 (lowest priority)010 : call priority level 3011 : call priority level 2100 : call priority level 1101 : call priority level 0110 : call priority level B111 : call priority level A (highest priority)

Mandatory rules

Recommended rules

Category Site (CAE)Type Threshold

SubSystem BSC

Instance cell


None 0 7 0

External Comment



3BK 21624 AAAA PCZZA Ed.09 21 / 1278


2.1.13 (NOTIF_PCH_THR) - (NOTIF_PCH_THR)HMI Name NOTIF_PCH_THRParameter Name

Logical Name NOTIF_PCH_THR

Definition The priority threshold for notification over PCH.The BSS shall consider, for Notification/PCH, only VGCS-Calls whichhave a priority (eMLPP priority) not below this parameter. If morethan one is selected, all these voice group calls shall be notified onPCH and all with the same frequency of occurrence.

Coding rules Coded over 3 bits000 : deactivation of notification on PCH in the cell001 : call priority level 4 (lowest priority)010 : call priority level 3011 : call priority level 2100 : call priority level 1101 : call priority level 0110 : call priority level B111 : call priority level A (highest priority)

Mandatory rules

Recommended rules

Category Site (CAE)

Type Threshold

SubSystem BSC

Instance cell


None 0 7 0

External Comment



22 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.14 (NUMBER_NCH_BLOCKS) - (NUMBER_NCH_BLOCKS)HMI Name NUMBER_NCH_BLOCKSParameter Name

Logical Name NUMBER_NCH_BLOCKS

Definition This parameter defines the maximum number of blocks usable forNCH.

Coding rules

Mandatory rules if EN_VGCS is enabled :- BS_AG_BLKS_RES >= NUMBER_NCH_BLOCKS- if BCCH_EXT = true, then BS_AG_BLKS_RES >NUMBER_NCH_BLOCKS

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance cell


None 1 7 2

External Comment The parameter is significant when EN_VGCS is enabled



3BK 21624 AAAA PCZZA Ed.09 23 / 1278


2.1.15 (NY2) - (NY2)HMI Name NY2Parameter Name

Logical Name NY2

Definition Maximum number of repetitions for the VGCS UPLINK GRANTmessage during an uplink access procedure

Coding rules

Mandatory rules

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance cell


None 1 7 3

External Comment



24 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.16 (PENALTY_TIME) - (PENALTY_TIME(n)(BSC))HMI Name PENALTY_TIMEParameter Name

Logical Name PENALTY_TIME(n)(BSC)Definition Time during which MS shall apply TEMPORARY_OFFSET to C2

criterion.

Coding rules step size = 20s. 0: 20s, 1: 40s, ..., 30: 620s, 31: TEMPORARYOFFSET ignored and cell_RESELECT_OFFSET has a negativevalue

Mandatory rules

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance cell


sec 20 620 20

External Comment

Single inhibited (31)

Umbrella inhibited (31)Concentric inhibited (31)Concentric Umbrella inhibited (31)

Microcell 20 s (0)Minicell 20 s (0)

Extended inner cell inhibited (31)

Cell Type Dependent

Extended outer cell inhibited (31)Nb of TRX Dependent No

3BK 21624 AAAA PCZZA Ed.09 25 / 1278


2.1.17 (RXLEV_ACCESS_MIN) - (RXLEV_ACCESS_MIN(n)(BSC))HMI Name RXLEV_ACCESS_MINParameter Name

Logical Name RXLEV_ACCESS_MIN(n)(BSC)Definition Minimum received level at the MS required for initial access to the

cell.

Coding rules Coded on 6 bits, 0=-110 dBm, 63=-47 dBm, step size=1dBm.

Mandatory rules RXLEV_ACCESS_MIN(n)(MFS) = RXLEV_ACCESS_MIN(n)(BSC)Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance cell


dBm -110 -47 -100

External Comment



26 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.18 (START_UPLINK_REPLY) - (START_UPLINK_REPLY)HMI Name START_UPLINK_REPLYParameter Name

Logical Name START_UPLINK_REPLY

Definition Maximum number of repetitions for the UPLINK FREE message (withthe Uplink Access Request bit set to L) during the initial part of theuplink access procedure (i.e. before sending the first UPLINK FREEmessage with the Uplink Access Request bit set to H)

Coding rules

Mandatory rules

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance cell


None 1 1024 256

External Comment The parameter is significant only if EN_UPLINK_REPLY is set to true.



3BK 21624 AAAA PCZZA Ed.09 27 / 1278


2.1.19 (T_NOTIF_RESPONSE_DELAY) - (T_NOTIF_RESPONSE_DELAY)HMI Name T_NOTIF_RESPONSE_DELAYParameter Name

Logical Name T_NOTIF_RESPONSE_DELAY

Definition This Timer is used to delay the Multiple SACCH Info Modify andthe VGCS_ADD_INFO in order to give the MS a chance to receivethe immediately transmitted VGCS_ADD_INFO/FACCH and SI6messages

Coding rules step size = 100 ms

Mandatory rules

Recommended rules

Category Site (CAE)

Type Timer

SubSystem BSC

Instance BSC


ms 100 1000 200

External Comment



28 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.20 (T_REPETITION_CHANNEL_RELEASE) -(T_REPETITION_CHANNEL_RELEASE)

HMI Name T_REPETITION_CHANNEL_RELEASEParameter Name

Logical Name T_REPETITION_CHANNEL_RELEASE

Definition This parameter defines the repetition period of CHANNEL RELEASEmessage sent on FACCH


Mandatory rules

Recommended rules

Category Site (CAE)Type Timer

SubSystem BSC

Instance cell


ms 200 1000 200

External Comment



3BK 21624 AAAA PCZZA Ed.09 29 / 1278


2.1.21 (T_REPETITION_UPLINK_FREE) - (T_REPETITION_UPLINK_FREE)HMI Name T_REPETITION_UPLINK_FREEParameter Name

Logical Name T_REPETITION_UPLINK_FREE

Definition Delay between consecutive repetitions of the UPLINK FREEmessage, sent to the mobile station. The UPLINK FREE messagesshall be repeated as long as no uplink is granted to a mobile station.


Mandatory rules

Recommended rules


SubSystem BSC

Instance cell


ms 20 480 200

External Comment



30 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.22 (T_WAIT_UPLINK_ACCESS) - (T_WAIT_UPLINK_ACCESS)HMI Name T_WAIT_UPLINK_ACCESSParameter Name

Logical Name T_WAIT_UPLINK_ACCESS

Definition Guard timer to wait for an Uplink Access. If no such bursts arereceived at this timer expiry, the BSC releases the voice group callchannel in that cell and provide notifications containing no channeldescription.

Coding rules step size = 1sec

Mandatory rules

Recommended rules T_Wait_Uplink_Access >= [START_UPLINK_REPLY + (10 *WAIT_UPLINK_ACCESS)] * T_REPETITION_UPLINK_FREE

Category Site (CAE)

Type Timer

SubSystem BSC

Instance BSC


sec 3 300 60

External Comment The parameter is significant only if EN_UPLINK_REPLY is set to true



3BK 21624 AAAA PCZZA Ed.09 31 / 1278


2.1.23 (T_WAIT_UPLINK_REQUEST_ACK) -(T_WAIT_UPLINK_REQUEST_ACK)

HMI Name T_WAIT_UPLINK_REQUEST_ACKParameter Name

Logical Name T_WAIT_UPLINK_REQUEST_ACK

Definition Guard timer to wait for UPLINK REQUEST ACK or UPLINKREQUEST REJECT message from the MSC.


Mandatory rules

Recommended rules


SubSystem BSC

Instance BSC


ms 500 5000 500

External Comment



32 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.24 (T14) - (T14)HMI Name T14Parameter Name

Logical Name T14

Definition Maximum queuing time for the VGCS Assignment Requests

Coding rules step size = 1sec

Mandatory rules

Recommended rules


SubSystem BSC

Instance BSC


sec 1 19 6

External Comment



3BK 21624 AAAA PCZZA Ed.09 33 / 1278


2.1.25 (T3115) - (T3115)HMI Name T3115Parameter Name

Logical Name T3115

Definition This timer is used for the repetition of the VGCS UPLINK GRANTmessage during the uplink access procedure. If the timer expiresbefore the reception of a correctly decoded frame from MS, the BTSrepeats the VGCS UPLINK GRANT message to the requesting MS

Coding rules step size = 20ms

Mandatory rules

Recommended rules

Category Site (CAE)

Type Timer

SubSystem BSC

Instance cell


ms 100 480 200

External Comment



34 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.26 (TEMPORARY_OFFSET) - (TEMPORARY_OFFSET(n))HMI Name TEMPORARY_OFFSETParameter Name

Logical Name TEMPORARY_OFFSET(n)Definition Offset applied to C2 criterion for the duration of PENALTY_TIME.

Coding rules step size = 10dB. 0: 0dB, 1:10dB, 6: 60dB, 7: infinity

Mandatory rules

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance cell


dB 0 infinity 0

External Comment

Single 0 dB (0)Umbrella 0 dB (0)

Concentric 0 dB (0)Concentric Umbrella 0 dB (0)Microcell infinity (7)

Minicell infinity (7)Extended inner cell 0 dB (0)

Cell Type Dependent

Extended outer cell 0 dB (0)Nb of TRX Dependent No

3BK 21624 AAAA PCZZA Ed.09 35 / 1278


2.1.27 (VGCS_FIX_AMR_FR_CODEC) - (VGCS_FIX_AMR_FR_CODEC)HMI Name VGCS_FIX_AMR_FR_CODECParameter Name

Logical Name VGCS_FIX_AMR_FR_CODEC

Definition This parameter defines the type of FR AMR codec used in thenetwork.

Coding rules 0 : AMR Full Rate Codec 12,2 kbit/s;1 : AMR Full Rate Codec 10,2 kbit/s;2 : AMR Full Rate Codec 7,95 kbit/s;3 : AMR Full Rate Codec 7,40 kbit/s;4 : AMR Full Rate Codec 6,70 kbit/s;5 : AMR Full Rate Codec 5,90 kbit/s;6 : AMR Full Rate Codec 5,15 kbit/s;7 : AMR Full Rate Codec 4,75 kbit/st;

Mandatory rules

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance BSC


None 0 7 1

External Comment



36 / 1278 3BK 21624 AAAA PCZZA Ed.09


2.1.28 (VGCS_FIX_AMR_HR_CODEC) - (VGCS_FIX_AMR_HR_CODEC)HMI Name VGCS_FIX_AMR_HR_CODECParameter Name

Logical Name VGCS_FIX_AMR_HR_CODEC

Definition This parameter defines the type of HR AMR codec used in thenetwork.

Coding rules 0 : AMR Half Rate Codec 7,95 kbit/s;1 : AMR Half Rate Codec 7,40 kbit/s;2 : AMR Half Rate Codec 6,70 kbit/s;3 : AMR Half Rate Codec 5,90 kbit/s;4 : AMR Half Rate Codec 5,15 kbit/s;5 : AMR Half Rate Codec 4,75 kbit/s;

Mandatory rules

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance BSC


None 2 5 4

External Comment AMR Half Rate codec mode 7,95 kb/s is not supported by AlcatelBSS.AMR Half Rate codec mode 7,4kb/s is not supported as a"stand-alone" codec



3BK 21624 AAAA PCZZA Ed.09 37 / 1278


2.1.29 (WAIT_UPLINK_ACCESS) - (WAIT_UPLINK_ACCESS)HMI Name WAIT_UPLINK_ACCESSParameter Name

Logical Name WAIT_UPLINK_ACCESS

Definition Maximum number of repetitions for the UPLINK FREE message(with the Uplink Access Request bit set to L) per cycle, during thenon-initial part of the uplink access procedure (i.e. after sending thefirst UPLINK FREE message with the Uplink Access Request bit setto H).Each time the value of this counter becomes zero, the BTS send oneUPLINK FREE message with the Uplink Access Request bit set to H.

Coding rules

Mandatory rules

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance cell


None 1 32 3

External Comment The parameter is significant only if EN_UPLINK_REPLY is set to true.



38 / 1278 3BK 21624 AAAA PCZZA Ed.09

3 LCS Telecom Parameters


3BK 21624 AAAA PCZZA Ed.09 39 / 1278


3.1 Network (CDE)3.1.1 (CONFIDENCE_ORIGIN) - (CONFIDENCE_ORIGIN)

HMI Name CONFIDENCE_ORIGINParameter Name

Logical Name CONFIDENCE_ORIGIN

Definition Confidence origin used in the 3D linear regression of the confidenceof the ellipsoid arc returned by the MFS when providing the referencelocation to the A-GPS server.

Coding rules step size = 0.1

Mandatory rules

Recommended rules

Category Network (CDE)Type Number

SubSystem MFS

Instance MFS


% 0 100 50.7

External Comment



40 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.1.2 (CONFIDENCE_VS_ARC_FACTOR_SLOPE) -(CONFIDENCE_VS_ARC_FACTOR_SLOPE)

HMI Name CONFIDENCE_VS_ARC_FACTOR_SLOPEParameter Name

Logical Name CONFIDENCE_VS_ARC_FACTOR_SLOPE

Definition Slope ratio between the confidence and the arc factor used in the 3Dlinear regression of the confidence of the ellipsoid arc returned bythe MFS when providing the reference location to the A-GPS server.


Mandatory rules

Recommended rules

Category Network (CDE)

Type Number

SubSystem MFS

Instance MFS


% 0 100 25

External Comment



3BK 21624 AAAA PCZZA Ed.09 41 / 1278


3.1.3 (CONFIDENCE_VS_RADIUS_SLOPE) -(CONFIDENCE_VS_RADIUS_SLOPE)

HMI Name CONFIDENCE_VS_RADIUS_SLOPEParameter Name

Logical Name CONFIDENCE_VS_RADIUS_SLOPE

Definition Slope ratio between the confidence and the sum of minimum radiusfactor and maximum radius factor used in the 3D linear regressionof the confidence of the ellipsoid arc returned by the MFS whenproviding the reference location to the A-GPS server.


Mandatory rules

Recommended rules


Type Number

SubSystem MFS

Instance MFS


% 0 100 15.28

External Comment



42 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.1.4 (MS_BASED_AGPS_ASSIST_DATA_LIST) -(MS_BASED_AGPS_ASSIST_DATA_LIST)

HMI Name MS_BASED_AGPS_ASSIST_DATA_LISTParameter Name

Logical Name MS_BASED_AGPS_ASSIST_DATA_LIST

Definition Bitmap (8 bits) defining the types of optional assistance data to beretrieved from the A-GPS server when using the MS based A-GPSpositioning method. The following optional assistance data type areconsidered: Almanac, UTC model, DGPS corrections, referencetime, acquisition assistance, real-time integrity.

Coding rules bit 8 (most significant) and bit 7 are not used (i.e. always set to 0); bit6=1: real-time integrity is retrieived; bit 5=1: acquisition assistanceis retrieived; bit 4=1: reference time is retrieived; bit 3=1: DGPScorrections is retrieived; bit 2=1: UTC model is retrieived; bit 1 (leastsignificant)=1: Almanac is retrieived.

Mandatory rules

Recommended rules

Category Network (CDE)Type Reference

SubSystem MFS

Instance MFS


None 0 63 0

External Comment



3BK 21624 AAAA PCZZA Ed.09 43 / 1278


3.1.5 (PREF_GPS_LIST_Priority_1) - (PREF_GPS_LIST_Priority_1)HMI Name PREF_GPS_LIST_Priority_1Parameter Name

Logical Name PREF_GPS_LIST_Priority_1

Definition The most preferred GPS positioning method.

Coding rules It contains a reference to a GPS method: 1 for MS Assisted A-GPS,2 for MS Based A-GPS, 3 for Conventional GPS.

Mandatory rules

Recommended rules The same GPS methods reference should not be used for differentpriorities


Type Number

SubSystem MFS

Instance MFS


None 1 3 1

External Comment



44 / 1278 3BK 21624 AAAA PCZZA Ed.09




Definition The second preferred GPS positioning method.


Mandatory rules

Recommended rules The same GPS methods reference should not be used for differentpriorities.


Type Number

SubSystem MFS

Instance MFS


None 1 3 2

External Comment



3BK 21624 AAAA PCZZA Ed.09 45 / 1278




Definition The third preferred GPS positioning method.


Mandatory rules

Recommended rules The same GPS methods reference should not be used for differentpriorities.


Type Number

SubSystem MFS

Instance MFS


None 1 3 3

External Comment



46 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.1.8 (SAGI_TCP_DATA_TIMEOUT) - (SAGI_TCP_DATA_TIMEOUT)HMI Name SAGI_TCP_DATA_TIMEOUTParameter Name

Logical Name SAGI_TCP_DATA_TIMEOUT

Definition Parameter used in the context of supervision of SAGI based onTCP keep alive mechanism. This timer controls the retransmissiontimeout for the sending of the individual data segments.

Coding rules step size = 1 second

Mandatory rules

Recommended rules

Category Network (CDE)Type Timer

SubSystem MFS

Instance MFS


sec 4 10 5

External Comment



3BK 21624 AAAA PCZZA Ed.09 47 / 1278


3.1.9 (SAGI_TCP_KEEP_ALIVE_INTERVAL) -(SAGI_TCP_KEEP_ALIVE_INTERVAL)

HMI Name SAGI_TCP_KEEP_ALIVE_INTERVALParameter Name

Logical Name SAGI_TCP_KEEP_ALIVE_INTERVAL

Definition Parameter used in the context of supervision of SAGI based on TCPkeep alive mechanism. This timer determines the interval separatingkeep alive retransmissions until a response is received. Once aresponse is received, the delay until the next keep alive transmissionis again controlled by the value of this timer. The connectionwill be aborted after the number of retransmissions specified bySAGI_TCP_MAX_DATA_RETRANS have gone unanswered.

Coding rules step size = 1 second

Mandatory rules

Recommended rules

Category Network (CDE)Type Timer

SubSystem MFS

Instance MFS


sec 4 10 5

External Comment



48 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.1.10 (SAGI_TCP_MAX_DATA_RETRANS) -(SAGI_TCP_MAX_DATA_RETRANS)

HMI Name SAGI_TCP_MAX_DATA_RETRANSParameter Name

Logical Name SAGI_TCP_MAX_DATA_RETRANS

Definition Parameter used in the context of supervision of SAGI based on TCPkeep alive mechanism. This parameter controls the number of timesTCP will retransmit an individual data segment before aborting theconnection. The retransmission timeout is given by the parameterSAGI_TCP_DATA_TIMEOUT.

Coding rules

Mandatory rules

Recommended rules


Type Number

SubSystem MFS

Instance MFS


None 4 10 5

External Comment



3BK 21624 AAAA PCZZA Ed.09 49 / 1278


3.1.11 (T_SAGI_GUARD) - (T_SAGI_GUARD)HMI Name T_SAGI_GUARDParameter Name

Logical Name T_SAGI_GUARD

Definition Timer to guard the response from the A-GPS server (on SAGI:interface with A-GPS server).

Coding rules step size = 1 sec

Mandatory rules

Recommended rules


Type Timer

SubSystem MFS

Instance MFS


sec 1 300 60

External Comment The timer is meaningful in the MFS when EN_SAGI=1.



50 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2 Site (CAE)3.2.1 (ARC_SIZE_FACTOR) - (ARC_SIZE_FACTOR)

HMI Name ARC_SIZE_FACTORParameter Name

Logical Name ARC_SIZE_FACTOR

Definition Factor used in the computation of the width in degree of the ellipsoidarc returned by the MFS when computing location estimate based onTA positionning method.


Mandatory rules

Recommended rules


SubSystem MFS

Instance BSS


None 1 1.5 1.2

External Comment



3BK 21624 AAAA PCZZA Ed.09 51 / 1278


3.2.2 (AZIMUTH) - (LCS_AZIMUTH)HMI Name AZIMUTHParameter Name

Logical Name LCS_AZIMUTH

Definition Antenna direction orientation for the sector supporting the cell (usedby the MFS to compute location estimate based on TA positionningmethod).

Coding rules 0: 0 degree,..., 359: 359 degree, 360: omnidirectional cell

Mandatory rules

Recommended rules


SubSystem MFS

Instance cell


None 0 360 0

External Comment 0 corresponds to the North orientation and is counted clockwise.



52 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2.3 (EN_CONV_GPS) - (EN_CONV_GPS)HMI Name EN_CONV_GPSParameter Name

Logical Name EN_CONV_GPS

Definition Flag to enable or disable the positioning method Conventional GPS.

Coding rules 0 = disabled; 1 = enabled

Mandatory rules EN_CONV_GPS = 0 (from B11 MR3)Recommended rules

Category Site (CAE)

Type Flag

SubSystem MFS

Instance cell


None 0 1 0

External Comment - The activation of this positioning method is meaningful whenEN_LCS=1.- Only the value 0 is supported (from B11 MR3)



3BK 21624 AAAA PCZZA Ed.09 53 / 1278


3.2.4 (EN_LCS) - (EN_LCS (BSC))HMI Name EN_LCSParameter Name

Logical Name EN_LCS (BSC)Definition Enables/Disables the Location Services (LCS) in the BSS.


Mandatory rules - Equal to EN_LCS (MFS)- EN_LCS = "disabled" on BSC G2 (from B11 MR3)- EN_LB and EN_LCS shall not be both enabled at the same time

Recommended rules


SubSystem BSC

Instance BSS


None 0 1 0

External Comment - Parameter available on BSC Evolution only (from B11 MR3).- Only the value 0 is supported on G2 BSC (from B11 MR3)



54 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2.5 (EN_LCS) - (EN_LCS (MFS))HMI Name EN_LCSParameter Name

Logical Name EN_LCS (MFS)Definition Enables/Disables the Location Services (LCS) in the BSS.


Mandatory rules - Equal to EN_LCS (BSC)- EN_LCS = "disabled" on BSC G2 (from B11 MR3)- EN_LB and EN_LCS shall not be both enabled at the same time

Recommended rules


SubSystem MFS

Instance BSS


None 0 1 0

External Comment - Parameter available on BSC Evolution only (from B11 MR3).- Only the value 0 is supported on G2 BSC (from B11 MR3)



3BK 21624 AAAA PCZZA Ed.09 55 / 1278


3.2.6 (EN_MS_ASSISTED_AGPS) - (EN_MS_ASSISTED_AGPS)HMI Name EN_MS_ASSISTED_AGPSParameter Name

Logical Name EN_MS_ASSISTED_AGPS

Definition Flag to enable or disable the positioning method MS AssistedA-GPS.


Mandatory rules - EN_MS_ASSISTED_AGPS = 0 (from B11 MR3)Recommended rules

Category Site (CAE)

Type Flag

SubSystem MFS

Instance cell


None 0 1 0




56 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2.7 (EN_MS_BASED_AGPS) - (EN_MS_BASED_AGPS)HMI Name EN_MS_BASED_AGPSParameter Name

Logical Name EN_MS_BASED_AGPS

Definition Flag to enable or disable the positioning method MS Based A-GPS.


Mandatory rules - EN_MS_BASED_AGPS = 0 (from B11 MR3)Recommended rules

Category Site (CAE)

Type Flag

SubSystem MFS

Instance cell


None 0 1 0




3BK 21624 AAAA PCZZA Ed.09 57 / 1278


3.2.8 (EN_SAGI) - (EN_SAGI)HMI Name EN_SAGIParameter Name

Logical Name EN_SAGI

Definition Flag indicating whether SAGI (interface with the A-GPS server) isconfigured or not for this BSS.

Coding rules 0: disabled; 1: enabled

Mandatory rules - EN_SAGI = 0 (from B11 MR3)Recommended rules

Category Site (CAE)

Type Flag

SubSystem MFS

Instance BSS


None 0 1 0

External Comment - Only the value 0 is supported (from B11 MR3)



58 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2.9 (Geographical Coordinates) -(GEOGRAPHICAL_COORDINATES_FLAG)

HMI Name Geographical CoordinatesParameter Name

Logical Name GEOGRAPHICAL_COORDINATES_FLAG

Definition Indicates whether latitude and longitude are significant or not.

Coding rules 0: not significant, 1: significant

Mandatory rules

Recommended rules

Category Site (CAE)

Type Flag

SubSystem MFS

Instance cell


None 0 1 0

External Comment



3BK 21624 AAAA PCZZA Ed.09 59 / 1278


3.2.10 (HALFPWR_BEAM_WIDTH) - (HALFPWR_BEAM_WIDTH)HMI Name HALFPWR_BEAM_WIDTHParameter Name

Logical Name HALFPWR_BEAM_WIDTH

Definition Antenna half power beam for the sector supporting the cell (used bythe MFS to compute location estimate based on TA positionningmethod).

Coding rules 0: half power beam width unknown, 1: 1 degree,..., 360: 360 degree(omnidirectional cell)

Mandatory rules

Recommended rules

Category Site (CAE)

Type Number

SubSystem MFS

Instance cell


None 0 360 0

External Comment



60 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2.11 (LATITUDE) - (LCS_LATITUDE)HMI Name LATITUDEParameter Name

Logical Name LCS_LATITUDE

Definition Latitude of the BTS supporting the cell (used by the MFS to computelocation estimate based on TA positionning method).

Coding rules Sequence of:- number of degrees (from 0 to 90)- number of minutes (from 0 to 59)- number of fractional minutes (from 0 to 9999)- direction (boolean, true for South and false for North)

Mandatory rules

Recommended rules

Category Site (CAE)

Type List of numbers

SubSystem MFS

Instance cell


None 0,0,0,false 90,59,9999,true #

External Comment 1) 0 latitude corresponds to the Equator;2) The coding for OMC-R HMI is described in the "BSS O&MParameters" document, parameter "LCS-Latitude".



3BK 21624 AAAA PCZZA Ed.09 61 / 1278


3.2.12 (LONGITUDE) - (LCS_LONGITUDE)HMI Name LONGITUDEParameter Name

Logical Name LCS_LONGITUDE

Definition Longitude of the BTS supporting the cell (used by the MFS tocompute location estimate based on TA positionning method).

Coding rules Sequence of:- number of degrees (from 0 to 180)- number of minutes (from 0 to 59)- number of fractional minutes (from 0 to 9999)- direction (boolean, true for West and false for East)

Mandatory rules

Recommended rules

Category Site (CAE)


SubSystem MFS

Instance cell


None 0,0,0,false 180,59,9999,true #

External Comment 1) 0 longitude corresponds to the Greenwich Meridian;2) The coding for OMC-R HMI is described in the "BSS O&MParameters" document, parameter "LCS-Longitude".



62 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2.13 (MAX_RADIUS_FACTOR) - (MAX_RADIUS_FACTOR)HMI Name MAX_RADIUS_FACTORParameter Name

Logical Name MAX_RADIUS_FACTOR

Definition Factor used in the computation of the maximum radius of the ellipsoidarc returned by the MFS when computing location estimate based onTA positionning method.


Mandatory rules

Recommended rules


SubSystem MFS

Instance BSS


None 0.5 1 0.6

External Comment



3BK 21624 AAAA PCZZA Ed.09 63 / 1278


3.2.14 (MIN_RADIUS_FACTOR) - (MIN_RADIUS_FACTOR)HMI Name MIN_RADIUS_FACTORParameter Name

Logical Name MIN_RADIUS_FACTOR

Definition Factor used in the computation of the minimum radius of the ellipsoidarc returned by the MFS when computing location estimate based onTA positionning method.


Mandatory rules

Recommended rules


SubSystem MFS

Instance BSS


None 0.5 1 0.85

External Comment



64 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2.15 (T_LCS_Delay_Tolerant) - (T_LCS_Delay_Tolerant)HMI Name T_LCS_Delay_TolerantParameter Name

Logical Name T_LCS_Delay_Tolerant

Definition SMLC timer to guard the calculation of the MS position (including theRRLP message exchange with the target MS) in case of a DelayTolerant Location Request.


Mandatory rules T_Location + T_Location_Longer > T_LCS_Delay_Tolerant >=T_LCS_Low_Delay

Recommended rules

Category Site (CAE)

Type Timer

SubSystem MFS

Instance BSS


sec 1 300 10

External Comment The timer is meaningful in the MFS when EN_LCS=1.



3BK 21624 AAAA PCZZA Ed.09 65 / 1278


3.2.16 (T_LCS_Low_Delay) - (T_LCS_Low_Delay)HMI Name T_LCS_Low_DelayParameter Name

Logical Name T_LCS_Low_Delay

Definition SMLC timer to guard the calculation of the MS position (includingthe RRLP message exchange with the target MS) in case of a LowDelay Location Request.

Coding rules step size = 0.1 sec


Recommended rules

Category Site (CAE)

Type Timer

SubSystem MFS

Instance BSS


sec 0.1 180 3




66 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2.17 (T_Loc_abort) - (T_Loc_abort)HMI Name T_Loc_abortParameter Name

Logical Name T_Loc_abort

Definition BSC timer supervising the response from the SMLC in case ofLocation Abort.


Mandatory rules

Recommended rules T_Loc_abort < T_Location

Category Site (CAE)

Type Timer

SubSystem BSC

Instance BSS


sec 1 30 2

External Comment The timer is meaningful in the BSC when EN_LCS=1.



3BK 21624 AAAA PCZZA Ed.09 67 / 1278


3.2.18 (T_Location) - (T_Location)HMI Name T_LocationParameter Name

Logical Name T_Location

Definition BSC timer, on a per call basis, supervising the response from theSMLC in case of Location request, when no RRLP exchange istriggered with the MS.



Recommended rules -

Category Site (CAE)

Type Timer

SubSystem BSC

Instance BSS


sec 1 300 15

External Comment The timer is meaningful in the BSC when EN_LCS=1.



68 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2.19 (T_Location_Longer) - (T_Location_Longer)HMI Name T_Location_LongerParameter Name

Logical Name T_Location_Longer

Definition BSC timer, on a per call basis, supervising the response from theSMLC in case of Location request, when a RRLP exchange istriggered with the MS.



Recommended rules T_Location_Longer > T_Location

Category Site (CAE)

Type Timer

SubSystem BSC

Instance BSS


sec 1 300 30

External Comment The timer is meaningful in the BSC when EN_LCS=1, and replacesT_Location timer in case of Conventional GPS, MS Assisted A-GPSand MS Based A-GPS positioning methods.



3BK 21624 AAAA PCZZA Ed.09 69 / 1278


3.2.20 (T_RRLP_Delay_Tolerant) - (T_RRLP_Delay_Tolerant)HMI Name T_RRLP_Delay_TolerantParameter Name

Logical Name T_RRLP_Delay_Tolerant

Definition SMLC timer to guard the RRLP message exchange between theSMLC and the target MS, in case of a Delay Tolerant LocationRequest.


Mandatory rules T_LCS_Delay_Tolerant > T_RRLP_Delay_TolerantT_RRLP_Delay_Tolerant >= T_RRLP_Low_Delay

Recommended rules

Category Site (CAE)

Type Timer

SubSystem MFS

Instance BSS


sec 1 300 9




70 / 1278 3BK 21624 AAAA PCZZA Ed.09


3.2.21 (T_RRLP_Low_Delay) - (T_RRLP_Low_Delay)HMI Name T_RRLP_Low_DelayParameter Name

Logical Name T_RRLP_Low_Delay

Definition SMLC timer to guard the RRLP message exchange between theSMLC and the target MS, in case of a Low Delay Location Request.


Mandatory rules T_Low_Delay > T_RRLP_Low_DelayT_RRLP_Delay_Tolerant >= T_RRLP_Low_Delay

Recommended rules


SubSystem MFS

Instance BSS


sec 0.1 120 2




3BK 21624 AAAA PCZZA Ed.09 71 / 1278


72 / 1278 3BK 21624 AAAA PCZZA Ed.09

4 IP Telecom Parameters


3BK 21624 AAAA PCZZA Ed.09 73 / 1278


4.1 Site (CAE)4.1.1 () - (MSC_OFFLOAD_STATE)

HMI Name Parameter Name

Logical Name MSC_OFFLOAD_STATE

Definition State assigned to a given MSC, connected to the BSC (Aflex feature),for the load redistribution function. That function removes the "offloaded" MSC from the list of candidate MSCs on BSS side.

Coding rules 0: off loaded1: on loaded

Mandatory rules

Recommended rules

Category Site (CAE)

Type Flag

SubSystem BSC

Instance MSC


None 0 1 1

External Comment - Significant only if EN_A_FLEX is enabled.- Aflex function is available on BSC Evolution only.- If a MSC server is in high load situation, the operator can avoidthe MSC to enter the overload situation through the update of thatparameter to "off loaded" for the concerned MSC.

Parameter change: on going traffic is not disrupted. Change appliedimmediately after modification. The complete redistribution of the MSrequires the same change done on Core Network side too.



74 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.2 () - (SGSN_OFFLOAD_STATE)HMI Name Parameter Name

Logical Name SGSN_OFFLOAD_STATE

Definition State assigned to a given SGSN, connected to the MFS (Gbflexfeature), for the load redistribution function. That function removesthe "off loaded" SGSN from the list of candidate SGSNs on BSS side.

Coding rules 0: off loaded1: on loaded

Mandatory rules

Recommended rules In a BSS in multi-GP/GPU configuration, for a consistent behaviourof the Gbflex feature, all the NSEs, connected to the same SGSN,must have the same SGSN_OFFLOAD_STATE.

Category Site (CAE)

Type Flag

SubSystem MFS

Instance NSE


None 0 1 1

External Comment - Significant only if EN_GB_FLEX is enabled.- If a SGSN server is in high load situation, the operator can avoidthe SGSN to enter the overload situation through the update of thatparameter to "off loaded" for all the NSEs of all the BSSs connectedto the concerned SGSN.

Parameter change: on going traffic is not disrupted. Change appliedimmediately after modification. The complete redistribution of the MSrequires the same change done on Core Network side too.



3BK 21624 AAAA PCZZA Ed.09 75 / 1278


4.1.3 (ASIG_SCTP_ENDPOINT_IP_Address_1) -(ASIG_SCTP_ENDPOINT_IP_Address_1)

HMI Name ASIG_SCTP_ENDPOINT_IP_Address_1Parameter Name

Logical Name ASIG_SCTP_ENDPOINT_IP_Address_1

Definition Primary IP adress of a SCTP endpoint (used by M3UA protocol) onthe MSC side.

Coding rules coded on 15 characters string

Mandatory rules - ASIG_SCTP_ENDPOINT_IP_Address_1 andASIG_SCTP_ENDPOINT_PORT shall together uniquelyidentify a SCTP endpoint inside one MSC- 255.255.255.255 and 0.0.0.0 are both forbidden

Recommended rules

Category Site (CAE)

Type IP address

SubSystem BSC

Instance SCTP EndPoint


None None None None

External Comment Parameter change: before any modification, the operator must lockthe associated A Signalling Link (ASL).



76 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.4 (ASIG_SCTP_ENDPOINT_IP_Address_2) -(ASIG_SCTP_ENDPOINT_IP_Address_2)

HMI Name ASIG_SCTP_ENDPOINT_IP_Address_2Parameter Name

Logical Name ASIG_SCTP_ENDPOINT_IP_Address_2

Definition Secondary IP adress of a SCTP endpoint (used by M3UA protocol)on the MSC side.It is an optional address used in case of SCTP multihoming in MSCside.


Mandatory rules - 255.255.255.255 and 0.0.0.0 are both forbidden

Recommended rules

Category Site (CAE)Type IP address

SubSystem BSC



None None None None




3BK 21624 AAAA PCZZA Ed.09 77 / 1278


4.1.5 (ASIG_SCTP_ENDPOINT_LIST) - (ASIG_SCTP_ENDPOINT_LIST)HMI Name ASIG_SCTP_ENDPOINT_LISTParameter Name

Logical Name ASIG_SCTP_ENDPOINT_LIST

Definition List of the SCTP endpoints (used by M3UA protocol) on the MSCside.Up to 4 endpoints can be defined in that list.

Coding rules coded as an array of 4 entriesEach entry is an SCTP endpoint, composedof ASIG_SCTP_ENDPOINT_IP_Address_1,ASIG_SCTP_ENDPOINT_PORT andASIG_SCTP_ENDPOINT_IP_Address_2

Mandatory rules When the MSC TRAFFIC_MODE is in load sharing, the number ofSCTP endpoints configured in the ASIG_SCTP_ENDPOINT_LISTmust be equal or greater than MIN_NB_ACTIVE_

Recommended rules

Category Site (CAE)


SubSystem BSC

Instance MSC


None None None None

External Comment Parameter change: before any modification, the operator must lockthe associated A Signalling Link(s) (ASL).



78 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.6 (ASIG_SCTP_ENDPOINT_PORT) - (ASIG_SCTP_ENDPOINT_PORT)HMI Name ASIG_SCTP_ENDPOINT_PORTParameter Name

Logical Name ASIG_SCTP_ENDPOINT_PORT

Definition Port of a SCTP endpoint (used by M3UA protocol) on the MSC side.

Coding rules Step size = 1

Mandatory rules ASIG_SCTP_ENDPOINT_IP_Address_1 andASIG_SCTP_ENDPOINT_PORT shall together uniquely identify aSCTP endpoint inside one MSC

Recommended rules


SubSystem BSC



None 1 65535 None




3BK 21624 AAAA PCZZA Ed.09 79 / 1278


4.1.7 (EN_A_FLEX) - (EN_A_FLEX)HMI Name EN_A_FLEXParameter Name

Logical Name EN_A_FLEX

Definition Enables/disables the support of the "Aflex" feature (for signalingtraffic). The Aflex feature allows a BSS to be connected to morethan one MSC.


Mandatory rules EN_A_FLEX is enabled only if EN_ASIG_OVER_IP is enabledWhen EN_A_FLEX is enabled, up to 16 MSCs can be connected toone BSC.When EN_A_FLEX is disabled, only one MSC can be connectedto one BSC.

Recommended rules

Category Site (CAE)

Type Flag

SubSystem BSC

Instance BSC


None 0 1 0

External Comment - Aflex function is available on BSC Evolution only.- Support of A-Flex by the MSC server is mandatory.- Support of Virtual MGW feature by the Media Gateway is mandatory.

Parameter change: Before disabling the feature from the BSC side,the operator must delete all the excessive MSCs (except one, ie nomore than one MSC connected to the BSC).Before enabling the feature, the operator must have configured theNULL_NRI and NRI_LENGTH parameters. Then the Aflex featuredeals with the unlocked MSC(s).



80 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.8 (EN_ASIG_OVER_IP) - (EN_ASIG_OVER_IP)HMI Name EN_ASIG_OVER_IPParameter Name

Logical Name EN_ASIG_OVER_IP

Definition Enables/disables the support of "A signalling over IP"


Mandatory rules - EN_A_FLEX is enabled only if EN_ASIG_OVER_IP is enabled.- EN_ASIG_OVER_IP can be enabled if, at least, one MSC SCTPendpoint has been configured.

Recommended rules


SubSystem BSC

Instance BSC


None 0 1 0

External Comment - Function available on BSC Evolution only.

- Parameter change: A BSC reset procedure is needed, aftermodification, to resynchronize all the channels of the A interface.This BSC reset leads to a total outage of several minutes. Notelecom service is provided during this procedure.



3BK 21624 AAAA PCZZA Ed.09 81 / 1278


4.1.9 (EN_GB_FLEX) - (EN_GB_FLEX)HMI Name EN_GB_FLEXParameter Name

Logical Name EN_GB_FLEX

Definition Enables/disables the support of the "Gbflex" feature (for data andsignaling traffic). The GbFlex feature allows a BSS to be connectedto more than one SGSN.


Mandatory rules - EN_GB_FLEX is enabled only if Gb_Transport_Mode is IP- If Gb_Transport_Mode is FR then EN_GB_FLEX must be disabled- EN_GB_FLEX is enabled only if SGSNR = 1- When EN_GB_FLEX is enabled, up to 8 SGSNs can be connectedto one BSS.- When EN_GB_FLEX is disabled, only one SGSN can be connectedto one BSS.

Recommended rules

Category Site (CAE)

Type Flag

SubSystem MFS

Instance BSS


None 0 1 0

External Comment Support of Gb-Flex by the SGSN is mandatory.

Parameter change: no impact on the on going telecom service.Before disabling the feature from the MFS side, the operator shalldelete all the excessive NSEs (no more than one NSE per GPU, ieno more than one SGSN connected to the BSS).



82 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.10 (Gb_Configuration_Type) - (Gb_Configuration_Type)HMI Name Gb_Configuration_TypeParameter Name

Logical Name Gb_Configuration_Type

Definition Configuration type used with Gb over IP.In case of static configuration, the SGSN IP endpoint(s) are given byO&M.In case of dynamic configuration, the SGSN IP endpoint(s) aresent dynamically by the SGSN. For that exchange, at least onepre-configured SGSN IP endpoint is previously given by O&M.

Coding rules 0 : Static configuration1: Dynamic configuration

Mandatory rules In a BSS in multi-GP/GPU configuration where Gb_Transport_Modeis IP, all the NSEs connected to the same SGSN, having childrenSGSN IPendpoint(s), must have the same Gb_Configuration_Type.

Recommended rules

Category Site (CAE)

Type Enumerated

SubSystem MFS

Instance NSE


None 0 1 0

External Comment Gb_Configuration type is significant only when Gb_Transport modeis IP.Parameter change: before any parameter modification, the operatorhas to delete the children SGSN IP endpoint(s).



3BK 21624 AAAA PCZZA Ed.09 83 / 1278


4.1.11 (GPU_Gb_Base_IP) - (GPU_Gb_Base_IP)HMI Name GPU_Gb_Base_IPParameter Name

Logical Name GPU_Gb_Base_IP

Definition Base address of the IP address of the local Gb IP endpoint, used todefine the GPU_Gb_IP_Address of each GPU board (for Gb over IPinterface).

Coding rules coded on 32 bitsThe last group is set to 000 (base address)

Mandatory rules

Recommended rules

Category Site (CAE)

Type IP address

SubSystem MFS

Instance MFS


None 0 4294967295 None

External Comment Parameter change: if Gb_transport_Mode is already in IP mode, achange of this parameter must be followed by a manual reset of theassociated GP/GPU (during the IP settings preparation phase, nomanual reset is needed since the reset is automatically performed bythe MFS at the feature activation time).



84 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.12 (GPU_Gb_Base_UDP) - (GPU_Gb_Base_UDP)HMI Name GPU_Gb_Base_UDPParameter Name

Logical Name GPU_Gb_Base_UDP

Definition Base port number of the UDP port number of the local Gb IPendpoint, used to define the GPU_Gb_UDP_port of each GPU board(for Gb over IP interface).

Coding rules

Mandatory rules

Recommended rules


SubSystem MFS

Instance MFS


None 63488 64512 64512




3BK 21624 AAAA PCZZA Ed.09 85 / 1278


4.1.13 (GPU_Gb_IP_Address) - (GPU_Gb_IP_Address)HMI Name GPU_Gb_IP_AddressParameter Name

Logical Name GPU_Gb_IP_Address

Definition Allows to display the IP address of the local Gb IP endpoint, used bya GPU board in a NSE instance (for Gb over IP interface)

Coding rules coded on 32 bitscoded default value is for implementation purposes only

Mandatory rules

Recommended rules

Category Site (CAE)

Type IP address

SubSystem MFS

Instance GPU


None 0 4294967295 None

External Comment Calculated by the MFS from the GPU_Gb_Base_IP value.



86 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.14 (GPU_Gb_UDP_Port) - (GPU_Gb_UDP_Port)HMI Name GPU_Gb_UDP_PortParameter Name

Logical Name GPU_Gb_UDP_Port

Definition Allows to display the UDP port number of the local Gb IP endpoint,used by a GPU board in a NSE instance (for Gb over IP interface).

Coding rules

Mandatory rules

Recommended rules

Category Site (CAE)

Type Number

SubSystem MFS

Instance GPU


None 63488 64512 64512

External Comment equal to GPU_Gb_base_UDP.



3BK 21624 AAAA PCZZA Ed.09 87 / 1278


4.1.15 (IP_Address) - (SGSN_IP_Address)HMI Name IP_AddressParameter Name

Logical Name SGSN_IP_Address

Definition IP address of a SGSN Ipendpoint, used in case of static configurationof Gb over IP interface.IP address of a pre-configured SGSN IP endpoint, used in case ofdynamic configuration of Gb over IP interface.


Mandatory rules - Each SGSN IP EndPoint (SGSN_IP_Address, SGSN_UDP_Port)must be unique per NSE.- in case of static configuration, up to 16 SGSN IP endpoints can bedefined per NSE.- In case of dynamic configuration, only a single pre-configuredSGSN IP endpoint can be defined per NSE.

Recommended rules

Category Site (CAE)Type IP address

SubSystem MFS

Instance SGSN-IPEndPoint


None 0 4294967295 None

External Comment



88 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.16 (IPGB_SUBNET_MASK_MFS) - (IPGB_SUBNET_MASK_MFS)HMI Name IPGB_SUBNET_MASK_MFSParameter Name

Logical Name IPGB_SUBNET_MASK_MFS

Definition Mask of the subnet where is allocated the range of MFS addressesused forGb telecom protocols


Mandatory rules

Recommended rules

Category Site (CAE)

Type IP address

SubSystem MFS

Instance MFS


None 0 4294967295 None




3BK 21624 AAAA PCZZA Ed.09 89 / 1278


4.1.17 (LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1) -(LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1)

HMI Name LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1Parameter Name

Logical Name LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1

Definition Local primary IP adress of a SCTP endpoint (used by M3UAprotocol) on the BSC side.


Mandatory rules - LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1 andLOCAL_ASIG_SCTP_ENDPOINT_PORT shall together uniquelyidentify a SCTP endpoint inside the BSC

Recommended rules 255.255.255.255 and 0.0.0.0 are both forbidden

Category Site (CAE)

Type IP address

SubSystem BSC



None None None None

External Comment



90 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.18 (LOCAL_ASIG_SCTP_ENDPOINT_PORT) -(LOCAL_ASIG_SCTP_ENDPOINT_PORT)

HMI Name LOCAL_ASIG_SCTP_ENDPOINT_PORTParameter Name

Logical Name LOCAL_ASIG_SCTP_ENDPOINT_PORT

Definition Local port of a SCTP endpoint (used by M3UA protocol) on theBSC side.

Coding rules Step size = 1

Mandatory rules LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1 andLOCAL_ASIG_SCTP_ENDPOINT_PORT shall together uniquelyidentify a SCTP endpoint inside the BSC

Recommended rules By default, the LOCAL_ASIG_SCTP_ENDPOINT_PORT values aretaken in the range 61953-61999.

It is recommended to change these values only in case of IOT issuewith the MSC. In this case it is recommended:- to not use values in the range 0..49151 ("well known" and "ianaregistered" ports)-to avoid the values already used by other BSS protocols using IP,-and especially to not use the ports used by the IP_BSSAsig protocol(to avoid conflicts during the transition from Asig over TDM to Asigover IP).

Category Site (CAE)

Type Number

SubSystem BSC



None 1 65535 None

External Comment Parameter change: Before any modification of theLocal_Asig_SCTP_Endpoint_Port, If the Aflex feature is enabled,Alcatel-Lucent recommends to firstly set the concerned MSC into the"off loaded" state in order to redirect the new traffic towards otherMSCs. Then, the operator must lock all the A Signalling Links (ASL)of the modified MSC. Under some circumstances (e.g. that MSC isthe only MSC still operational, ie in IT or FIT, state among all theMSCs connected to a BSC), the BSS-TEL is to be previously lockedtoo. This procedure leads the BSC to reject any new calls and wait forsome minutes (Wait Traffic Clear) before shutting down the on goingcalls. After modification of the Local_Asig_SCTP_Endpoint_Port, thelocked objects must be unlocked and be "on loaded" again to reopenthe telecom service.

3BK 21624 AAAA PCZZA Ed.09 91 / 1278




92 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.19 (MIN_NB_ACTIVE_IPSP) - (MIN_NB_ACTIVE_IPSP)HMI Name MIN_NB_ACTIVE_IPSPParameter Name

Logical Name MIN_NB_ACTIVE_IPSP

Definition The minimum number of active IP server processes (IPSP) in theMSC server required to handle the traffic with that MSC.

Coding rules

Mandatory rules When the MSC TRAFFIC_MODE is in load sharing, the number ofSCTP endpoints configured in the ASIG_SCTP_ENDPOINT_LISTmust be equal or greater than MIN_NB_ACTIVE_IPSP

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance MSC


None 1 4 1

External Comment - This parameter is significant when the TRAFFIC_MODE of theMSC is load sharing mode.- Parameter change: before any modification of theMIN_NB_ACTIVE_IPSP, If the Aflex feature isenabled, Alcatel-Lucent recommends to firstly set the concernedMSC into the "off loaded" state in order to redirect the new traffictowards other MSCs. Then, the operator must lock all the A SignallingLinks (ASL) of the modified MSC. Under some circumstances (e.g.that MSC is the only MSC still operational, ie in IT or FIT, state amongall the MSCs connected to a BSC), the BSS-TEL is to be previouslylocked too. This procedure leads the BSC to reject any new calls andwait for some minutes (Wait Traffic Clear) before shutting down theon going calls. After modification of the MIN_NB_ACTIVE_IPSP, thelocked objects must be unlocked and be "on loaded" again to reopenthe telecom service.



3BK 21624 AAAA PCZZA Ed.09 93 / 1278


4.1.20 (MSC_CN_ID) - (MSC_CN_ID)HMI Name MSC_CN_IDParameter Name

Logical Name MSC_CN_ID

Definition This parameter indicates, within a given PLMN, the Core NetworkIdentifier.It is part of the Global Core Network Identifier, defined in 3GPP TS23.003 as (PLMN-id + CN-id), which uniquely identifies a MSC forthe Aflex feature.

Coding rules coded on 2 bytesThe coded default value is for implementation purposes only; thisdummy value indicates that the operator does not provide any MSCidentifier yet.

Mandatory rules - All the MSCs, connected to one BSC, must have differentMSC_CN_ID.

Recommended rules - The operator must control that, in a PLMN, 2 MSCs must have2 different MSC_CN_ID.


SubSystem BSC

Instance MSC


None 0 4095 None

External Comment - Significant only if EN_A_FLEX is enabled- Aflex function is available on BSC Evolution only.- The operator must control that the BSC and all the MSCs connectedto that BSC via Aflex feature must belong to the same PLMN.- Parameter change: No impact on the telecom service, on goingcalls are not disrupted (still established with the same MSC). Changeapplied immediately on the new calls established after modification.



94 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.21 (MSC_MCC) - (MSC_MCC)HMI Name MSC_MCCParameter Name

Logical Name MSC_MCC

Definition Mobile Country Code of the MSC, connected to the BSC. It is part ofthe Global Core Network Identifier, defined in 3GPP TS 23.003 as(PLMN-id + CN-id), which uniquely identifies a MSC for the Aflexfeature.

Coding rules 3 digits BCDThe coded default value is for implementation purposes only; thisdummy value indicates that the operator does not provide any MCCyet.

Mandatory rules The OMC-R initializes the parameter with the MCC field of theBSC-OwnPLMN. It is not changeable on the HMI.

Recommended rules

Category Site (CAE)

Type Reference

SubSystem BSC

Instance MSC


None 0 999 None

External Comment - Significant only if EN_A_FLEX is enabled- Aflex function is available on BSC Evolution only.- The operator must control that the BSC and all the MSCs connectedto that BSC via Aflex feature must belong to the same PLMN.



3BK 21624 AAAA PCZZA Ed.09 95 / 1278


4.1.22 (MSC_MNC) - (MSC_MNC)HMI Name MSC_MNCParameter Name

Logical Name MSC_MNC

Definition Mobile Network Code of the MSC, connected to the BSC. It is part ofthe Global Core Network Identifier, defined in 3GPP TS 23.003 as(PLMN-id + CN-id), which uniquely identifies a MSC for the Aflexfeature.

Coding rules 3 digits BCDThe coded default value is for implementation purposes only; thisdummy value indicates that the operator does not provide any MNCyet.

Mandatory rules The OMC-R initializes the parameter with the MNC field of theBSC-OwnPLMN. It is not changeable on the HMI.

Recommended rules

Category Site (CAE)

Type Reference

SubSystem BSC

Instance MSC


None 0 999 None

External Comment - Significant only if EN_A_FLEX is enabled- Aflex function is available on BSC Evolution only.- The operator must control that the BSC and all the MSCs connectedto that BSC via Aflex feature must belong to the same PLMN.



96 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.23 (MSC_SPC) - (MSC_SPC)HMI Name MSC_SPCParameter Name

Logical Name MSC_SPC

Definition Signalling Point Code of a given MSC, connected to the BSC.

Coding rules coded over 14 bits

Mandatory rules All the MSCs connected to one BSC must have different MSC_SPC.

Recommended rules

Category Site (CAE)

Type Number

SubSystem BSC

Instance MSC


None 0 16383 None

External Comment - Significant only if EN_ASIG_OVER_IP is set to TRUE- "A signalling over IP" function is available on BSC Evolution only.- Parameter change: Before any modification of the MSC_SPC, If theAflex feature is enabled, Alcatel-Lucent recommends to firstly setthe concerned MSC into the "off loaded" state in order to redirectthe new traffic towards other MSCs. Then, the operator must lockall the A Signalling Links (ASL) of the modified MSC. Under somecircumstances (e.g. that MSC is the only MSC still operational, iein IT or FIT, state among all the MSCs connected to a BSC), theBSS-TEL is to be previously locked too. This procedure leads theBSC to reject any new calls and wait for some minutes (Wait TrafficClear) before shutting down the on going calls. After modificationof the MSC_SPC, the locked objects must be unlocked and be "onloaded" again to reopen the telecom service.



3BK 21624 AAAA PCZZA Ed.09 97 / 1278


4.1.24 (MSC_WEIGHT) - (MSC_WEIGHT)HMI Name MSC_WEIGHTParameter Name

Logical Name MSC_WEIGHT

Definition Weight assigned to a MSC, connected to the BSC (Aflex feature), forthe load balancing function. A high value is to be associated to ahigh capacity MSC.

Coding rules

Mandatory rules

Recommended rules It is recommended to set a weight value consistent with the numberof A-trunks connected to that MSC.

Category Site (CAE)

Type Number

SubSystem BSC

Instance MSC


None 1 255 1

External Comment - Significant only if EN_A_FLEX is enabled- Aflex function is available on BSC Evolution only.- Parameter change: No impact on the telecom service, on goingcalls are not disrupted (still established with the same MSC). Changeapplied immediately on the new calls established after modification.



98 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.25 (NRI_LENGTH) - (NRI_LENGTH)HMI Name NRI_LENGTHParameter Name

Logical Name NRI_LENGTH

Definition This parameter defined the configurable length of a NRI (NetworkResource Identification), expressed as a number of bits It is usedby the BSC to derive the NRI value from the received temporaryidentity TMSI, and to identify the serving MSC, connected to the BSC(Aflex feature). The NRI is coded starting from the bit 23 (the mostsignificant bit of the NRI) of the TMSI, regardless of the NRI length.

Coding rules The coded default value is for implementation purposes only; thisdummy value indicates that the operator does not provide any lengthvalue yet.

Mandatory rules - Each NRI of the list


4.1.26 (NRI_LENGTH_PS) - (NRI_LENGTH_PS)HMI Name NRI_LENGTH_PSParameter Name

Logical Name NRI_LENGTH_PS

Definition This parameter defined the configurable length of a NRI (NetworkResource Identification), expressed as a number of bits It is usedby the MFS to derive the NRI value from the received TLLI, and toidentify the serving SGSN, connected to the MFS (Gbflex feature).The NRI is coded starting from the bit 23 (the most significant bit ofthe NRI) of the TLLI, regardless of the NRI length.

Coding rules

Mandatory rules - Each NRI of the list


4.1.27 (NRI_LIST) - (NRI_LIST)HMI Name NRI_LISTParameter Name

Logical Name NRI_LIST

Definition List of the Network Resource Identifiers, associated to a given MSC,connected to the BSC (Aflex feature). Up to 8 NRIs can be definedper MSC.The NRI is part of the temporary identity TMSI, which is assigned bythe serving MSC to the MS. The BSC derives the NRI from any Initiallayer 3 message, in order to identify the serving MSC.

Coding rules Coded on 2 bytesThe empty list (length = 0) value 1024 is for implementation purposeonly; this dummy list indicates that the operator does not provideany NRI yet.

Mandatory rules - 2 different MSCs, connected to the BSC, must have 2 differentNRI_LIST.- A NRI shall be unique among all the NRI_LIST of all the MSCsconnected to the BSC (and especially when the BSC is in theoverlapping zone of 2 CS pool areas).- Each NRI of the list




102 / 1278 3BK 21624 AAAA PCZZA Ed.09


4.1.28 (NRI_LIST_PS) - (NRI_LIST_PS)HMI Name NRI_LIST_PSParameter Name

Logical Name NRI_LIST_PS

Definition List of the Network Resource Identifiers, associated to a givenSGSN, connected to the MFS (Gbflex feature). Up to 8 NRIs can bedefined per SGSN (and at least one).The NRI is part of the temporary identity P-TMSI, which is assignedby the serving SGSN to the MS. The MFS derives the NRI from theTLLI received from the MS, in order to identify the serving SGSN.

Coding rules coded on 2 bytesThe value 1024 is only defined for implementation purpose (it is nota valid value).

Mandatory rules - In a BSS, 2 different SGSNs must have 2 different NRI_LIST_PS.- A NRI shall be unique among all the NRI_LIST_PS of all the NSEsof one GP /GPU.- Each NRI of the list


4.1.29 (NULL_NRI) - (NULL_NRI)HMI Name NULL_NRIParameter Name

Logical Name NULL_NRI

Definition Upon reception of a message with that dummy/reserved NRIincluded, the BSC uses the load balancing algorithm for selectingone MSC, among the "on loaded" MSC connected to the BSC (Aflexfeature), and for re-routing the received message to that MSC.

Coding rules coded on 2 bytesThe coded default value is for implementation purposes only; thisdummy value indicates that the operator does not provide any nullNRI yet.

Mandatory rules - NULL_NRI


4.1.30 (NULL_NRI_PS) - (NULL_NRI_PS)HMI Name NULL_NRI_PSParameter Name

Logical Name NULL_NRI_PS

Definition In UL cases, upon TLLI reception with that dummy/reserved NRIincluded, while a SGSN is not already selected for a mobile, the MFSuses the load balancing algorithm for selecting one SGSN amongthe "on loaded" SGSN connected to the MFS (Gbflex feature).

Coding rules coded on 2 bytes

Mandatory rules - NULL_NRI_PS


4.1.31 (Peer_NSE_Data_Weight) - (Peer_NSE_Data_Weight)HMI Name Peer_NSE_Data_WeightParameter Name

Logical Name Peer_NSE_Data_Weight

Definition Indicates the da

parameters b11

Documents