A1353-RA Functional and Graphical Evolutions ed30.pdf

Alcatel BSS

Telecom Parameters Dictionary

OMC Document

Reference Guide

Release B9 from MR2

3BK 20924 AAAA PCZZA Ed.30P02

Status IN PREPARATION

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 / 1041 IN PREPARATION 3BK 20924 AAAA PCZZA Ed.30P02

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Parameter Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Parameter Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 LCS Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 Network (CDE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3 GSM Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.1 Network (CDE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.2 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323.3 System (CST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

4 GPRS Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673

4.1 Network (CDE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6744.2 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

5 E-GPRS Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10175.1 Network (CDE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10185.2 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021

6 2G-3G Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10316.1 Site (CAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032

3BK 20924 AAAA PCZZA Ed.30P02 IN PREPARATION 3 / 1041

Contents


Preface

Preface

Purpose The BSS Parameter Dictionary lists all of the Telecom Parameters for GSMand GPRS.

What’s New In Edition 30First official release of document.This document was generated from the database 15 of the BSS TelecomParameters.

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

Assumed Knowledge Not applicable.


Preface


1 Introduction

1 Introduction


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 the

next. 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 because

not 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 Alcatel

documentation.

Definition: definition/purpose of the parameter.

Coding rules:, Rules of coding, when necessary.

Mandatory rules: Mandatory relationships or inter-dependence of some

data.

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.

Value

Min/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.


2 LCS Telecom Parameters




2.1 Network (CDE)

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

Unit Minimum Maximum DefaultValue

% 0 100 50.7

Modifiable OMC Changes: – RNO Changes: –

Parameter Access –

External Comment –

Cell Type Dependent No

Nb of TRX Dependent No

Type NoneMigration

Rule Not applicable



2.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 –



Type Number

SubSystem MFS

Instance MFS


% 0 100 25






Type NoneMigration

Rule Not applicable



2.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 –



Type Number

SubSystem MFS

Instance MFS


% 0 100 15.28






Type NoneMigration

Rule Not applicable



2.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 –



Type Reference

SubSystem MFS

Instance MFS


None 0 63 0

Modifiable OMC Changes: None RNO Changes: No

Parameter Access —




Type NoneMigration

Rule Not applicable



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






Type NoneMigration

Rule Not applicable






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






Type NoneMigration

Rule Not applicable






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






Type NoneMigration

Rule Not applicable



2.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 –



Type Timer

SubSystem MFS

Instance MFS


sec 4 10 5






Type NoneMigration

Rule Not applicable



2.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 –



Type Timer

SubSystem MFS

Instance MFS


sec 4 10 5






Type NoneMigration

Rule Not applicable



2.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 –



Type Number

SubSystem MFS

Instance MFS


None 4 10 5






Type NoneMigration

Rule Not applicable



2.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 –



Type Timer

SubSystem MFS

Instance MFS


sec 1 300 60



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



Type NoneMigration

Rule Not applicable



2.2 Site (CAE)

2.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 –


Category Site (CAE)

Type Number

SubSystem MFS

Instance BSS


None 1 1.5 1.2






Type Migration of common B8/B9 MFS parameters bythe OMC (B)

Migration

Rule Value of previous release



2.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 –


Category Site (CAE)

Type Number

SubSystem MFS

Instance cell


None 0 360 0

Modifiable OMC Changes: PRC & SC RNO Changes: No

Parameter Access Edit cell / LCS

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




Migration




2.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 –


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.




Migration




2.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)


Category Site (CAE)

Type Flag

SubSystem BSC

Instance BSS


None 0 1 0

Modifiable OMC Changes: PRC & SC RNO Changes: BSS

Parameter Access Edit BSC / LCS




Type OEF migration for BSC parametersMigration




2.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)


Category Site (CAE)

Type Flag

SubSystem MFS

Instance BSS


None 0 1 0







Migration




2.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 –


Category Site (CAE)

Type Flag

SubSystem MFS

Instance cell


None 0 1 0







Migration




2.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 –


Category Site (CAE)

Type Flag

SubSystem MFS

Instance cell


None 0 1 0


Parameter Access Edit Cell / LCS





Migration




2.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 –


Category Site (CAE)

Type Flag

SubSystem MFS

Instance BSS


None 0 1 0

Modifiable OMC Changes: PRC & SC RNO Changes: ?






Migration




2.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 –


Category Site (CAE)

Type Flag

SubSystem MFS

Instance cell


None 0 1 0







Migration




2.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 –


Category Site (CAE)

Type Number

SubSystem MFS

Instance cell


None 0 360 0







Migration




2.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 –


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




Migration




2.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 –


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




Migration




2.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 –


Category Site (CAE)

Type Number

SubSystem MFS

Instance BSS


None 0.5 1 0.6







Migration




2.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 –


Category Site (CAE)

Type Number

SubSystem MFS

Instance BSS


None 0.5 1 0.85







Migration




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


Category Site (CAE)

Type Timer

SubSystem MFS

Instance BSS


sec 1 300 10


Parameter Access Edit BSS / LCS

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




Migration




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



Category Site (CAE)

Type Timer

SubSystem MFS

Instance BSS


sec 0.1 180 3







Migration




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







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







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







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


Category Site (CAE)

Type Timer

SubSystem MFS

Instance BSS


sec 1 300 9







Migration




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


Category Site (CAE)

Type Timer

SubSystem MFS

Instance BSS


sec 0.1 120 2







Migration



3 GSM Telecom Parameters




3.1 Network (CDE)

3.1.1 (ADDR_MON) - (ADDR_MON)

HMI Name ADDR_MONParameter Name

Logical Name ADDR_MON

Definition Time it takes to ADDR_TR to be reached to report an alarm. Ontimeout, the address error counter is reset.

Coding rules step size = 0.1sec

Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 6553.5 15






TypeMigration

Rule –



3.1.2 (ADDR_TR) - (ADDR_TR)

HMI Name ADDR_TRParameter Name

Logical Name ADDR_TR

Definition Address error threshold for alarm detection.

Coding rules –

Mandatory rules –



Type Threshold

SubSystem BSC

Instance BSC


None 1 255 60






TypeMigration

Rule –



3.1.3 (Autocleaning_Timer) - (T_AUTOCLEANING_MEAS_REP)

HMI Name Autocleaning_TimerParameter Name

Logical Name T_AUTOCLEANING_MEAS_REP

Definition Guard time for detection of SDCCH/TCH autocleaning procedure.


Mandatory rules –

Recommended rules In micro cells, it is recommended to set N_BAD_SACCH so thatT_AUTOCLEANING_MEAS_REP > N_BAD_SACCH * 480ms + 30seconds if T_AUTOCLEANING_MEAS_REP <> 0.


Type Timer

SubSystem BSC

Instance BSS


sec 0 255 40


Parameter Access Edit BSC / Procedures / General timers and procedures

External Comment T_AUTOCLEANING_MEAS_REP = 0 inhibits the autocleaningprocedure.



TypeMigration

Rule –



3.1.4 (BF_HI_RX) - (BF_HI_RX)

HMI Name BF_HI_RXParameter Name

Logical Name BF_HI_RX

Definition Threshold on LAPD RX buffers occupancy for transition from normalto busy condition.

Coding rules –

Mandatory rules –

Recommended rules BF_HI_RX > BF_LO_RX


Type Threshold

SubSystem BSC

Instance BSC


% 0 100 80






TypeMigration

Rule –



3.1.5 (BF_HI_TX) - (BF_HI_TX)

HMI Name BF_HI_TXParameter Name

Logical Name BF_HI_TX

Definition Threshold on LAPD TX buffers occupancy for transition from normalto busy condition.

Coding rules –

Mandatory rules –

Recommended rules BF_HI_TX > BF_LO_TX


Type Threshold

SubSystem BSC

Instance BSC


None 0 30 16






TypeMigration

Rule –



3.1.6 (BF_LO_RX) - (BF_LO_RX)

HMI Name BF_LO_RXParameter Name

Logical Name BF_LO_RX

Definition Threshold on LAPD RX buffers occupancy for transition from busyto normal condition.

Coding rules –

Mandatory rules –

Recommended rules BF_LO_RX < BF_HI_RX


Type Threshold

SubSystem BSC

Instance BSC


% 0 100 70






TypeMigration

Rule –



3.1.7 (BF_LO_TX) - (BF_LO_TX)

HMI Name BF_LO_TXParameter Name

Logical Name BF_LO_TX

Definition Threshold on LAPD TX buffers occupancy for transition from busyto normal condition.

Coding rules –

Mandatory rules –

Recommended rules BF_LO_TX < BF_HI_TX


Type Threshold

SubSystem BSC

Instance BSC


None 0 30 8






TypeMigration

Rule –



3.1.8 (CGI_REQUIRED) - (CGI_REQD)

HMI Name CGI_REQUIREDParameter Name

Logical Name CGI_REQD

Definition Controls format of cell identifications sent to the MSC.

Coding rules 0: CGI not used, 1: CGI used

Mandatory rules –

Recommended rules Alcatel recommend to set the CGI_REQD parameter to 1 providedthat the MSC supports the CGI format. The CGI_REQD parametershall be set to 1 if the operator wants to allow inter-PLMN 2Gto 2G handovers. If this parameter needs to be changed, it isrecommended to change it during a migration phase to avoid anyadditional Telecom outage.


Type Flag

SubSystem BSC

Instance BSC


None 0 1 1


Parameter Access Edit BSC / Interworking / MSC interworking

External Comment Depends on MSC Type. The value indicated here is forimplementation purposes.



TypeMigration

Rule –



3.1.9 (COUNT_DECR) - (COUNT_DECR)

HMI Name COUNT_DECRParameter Name

Logical Name COUNT_DECR

Definition Stepsize by which the leaky bucket counter used during the reactionto TCU overload is decremented upon T_COUNT_I expiry.

Coding rules –

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


None 1 10 1






TypeMigration

Rule –



3.1.10 (COUNT_I_THRESHOLD) - (COUNT_I_THRESHOLD)

HMI Name COUNT_I_THRESHOLDParameter Name

Logical Name COUNT_I_THRESHOLD

Definition Leaky bucket counter threshold used to trigger defense actions uponTCU overload.

Coding rules –

Mandatory rules –



Type Threshold

SubSystem BSC

Instance BSC


None 0 50 10






TypeMigration

Rule –



3.1.11 (COUNT_INCR_1) - (COUNT_INCR_1)

HMI Name COUNT_INCR_1Parameter Name

Logical Name COUNT_INCR_1

Definition Stepsize by which the leaky bucket counter used during the reactionto TCU overload is incremented upon TCU overload level 1.

Coding rules –

Mandatory rules –

Recommended rules COUNT_INCR_1 <= COUNT_INCR_2


Type Number

SubSystem BSC

Instance BSC


None 0 10 2






TypeMigration

Rule –



3.1.12 (COUNT_INCR_2) - (COUNT_INCR_2)

HMI Name COUNT_INCR_2Parameter Name

Logical Name COUNT_INCR_2

Definition Stepsize by which the leaky bucket counter used during the reactionto TCU overload is incremented upon TCU overload level 2.

Coding rules –

Mandatory rules –

Recommended rules COUNT_INCR_2 >= COUNT_INCR_1


Type Number

SubSystem BSC

Instance BSC


None 1 10 4






TypeMigration

Rule –



3.1.13 (CRC_MON) - (CRC_MON)

HMI Name CRC_MONParameter Name

Logical Name CRC_MON

Definition Time in which CRC_TR is to be reached to report an alarm. Ontimeout, the CRC error counter is reset.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 25.5 10






TypeMigration

Rule –



3.1.14 (CRC_TR) - (CRC_TR)

HMI Name CRC_TRParameter Name

Logical Name CRC_TR

Definition CRC error threshold for alarm detection.

Coding rules –

Mandatory rules –



Type Threshold

SubSystem BSC

Instance BSC


None 1 255 50






TypeMigration

Rule –



3.1.15 (EGSM_RR_ALLOC_STRATEGY) -(EGSM_RR_ALLOC_STRATEGY)

HMI Name EGSM_RR_ALLOC_STRATEGYParameter Name

Logical Name EGSM_RR_ALLOC_STRATEGY

Definition Defines the radio resource allocation strategy used in EGSM cells.

Coding rules 0: Different behaviour for EGSM capable MS: The BSS handlesdifferently EGSM capable MS from PGSM only capable MS in EGSMcells.1: Same behaviour for EGSM capable MS: The BSS handles in thesame way only PGSM capable MS as EGSM capable MS in EGSMcells, i.e. the BSS assumes that all GSM900 MS are EGSM capable.

Mandatory rules 1) When EGSM_RR_ALLOC_STRATEGY is set to "Differentbehaviour for EGSM capable MS", the OMC-R does not allow theoperator to define the BCCH, CCCH, SDCCH and CBCH on a G1TRX.2) For a hopping G1 TRX, if EGSM_RR_ALLOC_STRATEGY = 0then TRX_PREF_MARK <> 0



Type Number

SubSystem BSC

Instance BSS


None 0 1 0






Type NoneMigration

Rule Not applicable



3.1.16 (EN_FR_IF_HR_PREF) - (EN_FR_IF_HR_PREF)

HMI Name EN_FR_IF_HR_PREFParameter Name

Logical Name EN_FR_IF_HR_PREF

Definition When set, this flag allows, when bugged MS asking for a "dual rate,half-rate preferred", to allocate a full rate channel.

Coding rules 0 : function disabled, 1 : function enabled

Mandatory rules –



Type Flag

SubSystem BSC

Instance BSC


None 0 1 0






TypeMigration

Rule –



3.1.17 (I_TX_LAPD) - (I_TX_LAPD)

HMI Name I_TX_LAPDParameter Name

Logical Name I_TX_LAPD

Definition Maximum LAPD transmission queue length.

Coding rules –

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


None 5 204 105






TypeMigration

Rule –



3.1.18 (LB_DECR) - (LB_DECR)

HMI Name LB_DECRParameter Name

Logical Name LB_DECR

Definition Stepsize by which a leaky bucket overload counter in the BSC isdecremented on T_LB_OV expiry.

Coding rules –

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


None 1 10 3






TypeMigration

Rule –



3.1.19 (LB_INCR) - (LB_INCR)

HMI Name LB_INCRParameter Name

Logical Name LB_INCR

Definition Stepsize by which a leaky bucket overload counter in the BSC isincremented each time an OVERLOAD is received from the FU.

Coding rules –

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


None 1 10 2






TypeMigration

Rule –



3.1.20 (MEAS_RES_DISCARDED_i [1]) - (MEAS_RES_DISCARDED_i [1])

HMI Name MEAS_RES_DISCARDED_i [1]Parameter Name

Logical Name MEAS_RES_DISCARDED_i [1]

Definition Percentage of MEASUREMENT RESULT messages discarded bythe TCU at step I.

Coding rules –

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


% 0 100 10






TypeMigration

Rule –



3.1.21 (MEAS_RES_DISCARDED_i [10]) - (MEAS_RES_DISCARDED_i[10])




Coding rules –

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


% 0 100 0






TypeMigration

Rule –







Coding rules –

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


% 0 100 20






TypeMigration

Rule –







Coding rules –

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


% 0 100 30






TypeMigration

Rule –







Coding rules –

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


% 0 100 40






TypeMigration

Rule –







Coding rules –

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


% 0 100 0






TypeMigration

Rule –



3.1.30 (MIN_RLF_TIME_DL) - (MIN_RLF_TIME_DL)

HMI Name MIN_RLF_TIME_DLParameter Name

Logical Name MIN_RLF_TIME_DL

Definition Minimum time before detecting a radio link failure of a DL TBF,triggered by N3105 or NstagnatingWindowDL.

Coding rules step size = 100 ms

Mandatory rules –

Recommended rules It is recommended to set a value close to the time of temporary verybad radio conditions that the operator would like to support during aDL TBF. Typically, a few seconds.


Type Timer

SubSystem MFS

Instance MFS


ms 0 25000 4000






Type NoneMigration

Rule Not applicable



3.1.31 (NBLK) - (NBLK)

HMI Name NBLKParameter Name

Logical Name NBLK

Definition Maximum number of BLOCK messages that can be sent if the ACKfrom the MSC is not received.

Coding rules 255: infinite transmission

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


None 1 255 2






TypeMigration

Rule –



3.1.32 (NBR_STEPS_OVRL_1) - (NBR_STEPS_OVRL_1)

HMI Name NBR_STEPS_OVRL_1Parameter Name

Logical Name NBR_STEPS_OVRL_1

Definition Number of steps needed to reduce the load upon TCU overloadlevel 1.

Coding rules –

Mandatory rules –

Recommended rules NBR_STEPS_OVRL_1 <= NBR_STEPS_OVRL_2


Type Number

SubSystem BSC

Instance BSC


None 1 10 1






TypeMigration

Rule –



3.1.33 (NBR_STEPS_OVRL_2) - (NBR_STEPS_OVRL_2)

HMI Name NBR_STEPS_OVRL_2Parameter Name

Logical Name NBR_STEPS_OVRL_2

Definition Number of steps to reduce the load upon TCU overload level 2.

Coding rules –

Mandatory rules –

Recommended rules NBR_STEPS_OVRL_2 >= NBR_STEPS_OVRL_1


Type Number

SubSystem BSC

Instance BSC


None 1 10 2






TypeMigration

Rule –



3.1.34 (NUBLK) - (NUBLK)

HMI Name NUBLKParameter Name

Logical Name NUBLK

Definition Maximum number of UNBLOCK messages that are sent if the ACKfrom the MSC is not received.

Coding rules 255: infinite transmission

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


None 1 255 2






TypeMigration

Rule –



3.1.35 (PROT_MON) - (PROT_MON)

HMI Name PROT_MONParameter Name

Logical Name PROT_MON

Definition Time in which PROT_TH is to be reached to report an alarm. Ontimeout, the protocol error counter is reset.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 6553.5 10






TypeMigration

Rule –



3.1.36 (PROT_TH) - (PROT_TH)

HMI Name PROT_THParameter Name

Logical Name PROT_TH

Definition Protocol error threshold for alarm detection.

Coding rules –

Mandatory rules –



Type Threshold

SubSystem BSC

Instance BSC


None 1 255 10






TypeMigration

Rule –



3.1.37 (SDCCH_AVG_PERIOD) - (SDCCH_AVG_PERIOD)

HMI Name SDCCH_AVG_PERIODParameter Name

Logical Name SDCCH_AVG_PERIOD

Definition Period used to average the processor occupancy measurements.

Coding rules 8 bits, step size=1sec

Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 16 10






TypeMigration

Rule –



3.1.38 (SDCCH_HIGH_DELAY) - (SDCCH_HIGH_DELAY)

HMI Name SDCCH_HIGH_DELAYParameter Name

Logical Name SDCCH_HIGH_DELAY

Definition Delay added to SDCCH internal release when TCU processor loadis high.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 10 2






TypeMigration

Rule –



3.1.39 (SDCCH_LOW_DELAY) - (SDCCH_LOW_DELAY)

HMI Name SDCCH_LOW_DELAYParameter Name

Logical Name SDCCH_LOW_DELAY

Definition Delay added to SDCCH internal release when TCU processor load islow.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 10 0






TypeMigration

Rule –



3.1.40 (SMS_INHIBIT) - (SMS_INHIBIT)

HMI Name SMS_INHIBITParameter Name

Logical Name SMS_INHIBIT

Definition This flag enables/disables SMS support.

Coding rules 0: SMS permitted, 1: SMS inhibited

Mandatory rules –



Type Flag

SubSystem BSC

Instance BSC


None 0 1 0






TypeMigration

Rule –



3.1.41 (SSF) - (SSF)

HMI Name SSFParameter Name

Logical Name SSF

Definition This parameter inditifies the numbering plan of the Signalling PointCode.

Coding rules coded over 4 bits.only values 0, 4, 8 and 12 are defined : Value =0, international network; Value = 4, Spare, reserved for internationaluse; Value = 8, National network; Value = 12 , Reserved for nationaluse

Mandatory rules –



Type Number

SubSystem BSC

Instance BSC


None 0 12 12



External Comment SSF (Sub-Service Field) is composed of 4 bits: 2bits for NetworkIndicator and 2 spare bits.



TypeMigration

Rule –



3.1.42 (T_BTS_EST_CNF) - (T_BTS_EST_CNF)

HMI Name T_BTS_EST_CNFParameter Name

Logical Name T_BTS_EST_CNF

Definition Supervision of the SAPI 3 Establishment procedure.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 6553.5 4






TypeMigration

Rule –



3.1.43 (T_BTS_RLS_CNF) - (T_BTS_RLS_CNF)

HMI Name T_BTS_RLS_CNFParameter Name

Logical Name T_BTS_RLS_CNF

Definition Supervision of the SAPI 3 Release procedure.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 6553.5 4






TypeMigration

Rule –



3.1.44 (T_CBC_READY) - (T_CBC_READY)

HMI Name T_CBC_READYParameter Name

Logical Name T_CBC_READY

Definition Defines the maximum period during which the BSC tries to connectto the CBC before issueing an alarm or returning CMD-MODE Resp.

Coding rules step size: 1 sec

Mandatory rules –

Recommended rules T_CBC_READY > 8 * T_CONNECT


Type Number

SubSystem BSC

Instance BSC


sec 10 600 300






TypeMigration

Rule –



3.1.45 (T_COUNT_I) - (T_COUNT_I)

HMI Name T_COUNT_IParameter Name

Logical Name T_COUNT_I

Definition Supervision of the leaky bucket counter used during the reaction toTCU overload.

Coding rules –

Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 50 12






TypeMigration

Rule –



3.1.46 (T_i) - (T_i)

HMI Name T_iParameter Name

Logical Name T_i

Definition Duration of SSP or SPI condition that triggers an Internal Resetprocedure.


Mandatory rules –

Recommended rules For BSC Evolution, the default value must be increased to 10 sec.


Type Timer

SubSystem BSC

Instance BSC


sec 0 10 3






TypeMigration

Rule –



3.1.47 (T_LB_OV) - (T_LB_OV)

HMI Name T_LB_OVParameter Name

Logical Name T_LB_OV

Definition Supervision of the leaky bucket counter used during the reactionto FU overload.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0.1 25.5 10






TypeMigration

Rule –



3.1.48 (T_OVL_MSC) - (T_OVL_MSC)

HMI Name T_OVL_MSCParameter Name

Logical Name T_OVL_MSC

Definition Minimum delay between two consecutive OVERLOAD messagessent to the MSC.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0.1 6553.5 20






TypeMigration

Rule –



3.1.49 (T_RCR_ACK) - (T_RCR_ACK)

HMI Name T_RCR_ACKParameter Name

Logical Name T_RCR_ACK

Definition Supervision of the RF Channel Release procedure.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 6553.5 5






TypeMigration

Rule –



3.1.50 (T_SMSCB_RESP) - (T_SMSCB_RESP)

HMI Name T_SMSCB_RESPParameter Name

Logical Name T_SMSCB_RESP

Definition Maximum waiting time to get a response from the BTS to a primitive.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 1 10 2






TypeMigration

Rule –



3.1.51 (T1_0858) - (T1_0858)

HMI Name T1_0858Parameter Name

Logical Name T1_0858

Definition Delay during which, after reception of an OVERLOAD from the BTS,a new OVERLOAD is ignored.


Mandatory rules T1_0858 < T2_0858



Type Timer

SubSystem BSC

Instance BSC


sec 3 6553.5 30






TypeMigration

Rule –



3.1.52 (T2_0858) - (T2_0858)

HMI Name T2_0858Parameter Name

Logical Name T2_0858

Definition Minimum delay between debarring of an access class, in the casewhere the BTS stops sending OVERLOAD.


Mandatory rules T2_0858 > T1_0858



Type Timer

SubSystem BSC

Instance BSC


sec 3 6553.5 50






TypeMigration

Rule –



3.1.53 (T9101) - (T9101)

HMI Name T9101Parameter Name

Logical Name T9101

Definition Supervision of the SCCP connection release procedure.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 6553.5 10






TypeMigration

Rule –



3.1.54 (T9103) - (T9103)


Logical Name T9103

Definition Supervision of the Channel Activation procedure.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 6553.5 3






TypeMigration

Rule –



3.1.55 (T9108) - (T9108)


Logical Name T9108

Definition Supervision of the Physical Context procedure.


Mandatory rules –



Type Timer

SubSystem BSC

Instance BSC


sec 0 6553.5 3






TypeMigration

Rule –



3.1.56 (T9110) - (T9110)


Logical Name T9110

Definition Guards the response of the MSC when no resources areallocated to the SCCP connection (started on the receptionof CONN_IND(SCCP_CON_REQ) not carrying a HANDOVERREQUEST message and stopped when a HANDOVER REQUESTmessage is received on the same SCCP connection as theSCCP_CON_REQ message). Guards also the response of the MSCwhen a HANDOVER FAILURE or ASSIGNMENT FAILURE messagehas been sent (stopped when a HANDOVER REQUEST or CLEARCOMMAND message is received).


Mandatory rules –

Recommended rules T9110 << max [T(ias), T(iar)].


Type Timer

SubSystem BSC

Instance BSC


sec 0 6553.5 20


Parameter Access Edit BSC / Procedures / General Timers and procedure




TypeMigration

Rule –



3.1.57 (TCH_INFO_PERIOD) - (TCH_INFO_PERIOD)

HMI Name TCH_INFO_PERIODParameter Name

Logical Name TCH_INFO_PERIOD

Definition Periodicity of TCH usage information update in the BSC.

Coding rules stepsize = 0.1

Mandatory rules –



Type Timer

SubSystem BSC

Instance BSS


sec 2 25.5 5

Modifiable OMC Changes: Displayed RNO Changes: No

Parameter Access Edit BSC / HO/Reselection / HO Control




TypeMigration

Rule –



3.1.58 (THR_LB_OV) - (THR_LB_OV)

HMI Name THR_LB_OVParameter Name

Logical Name THR_LB_OV

Definition Counter threshold for triggering global defence actions in the BSCupon FU overload.

Coding rules –

Mandatory rules –



Type Threshold

SubSystem BSC

Instance BSC


None 0 50 10






TypeMigration

Rule –



3.1.59 (THRESHOLD_1_0) - (THRESHOLD_1_0)

HMI Name THRESHOLD_1_0Parameter Name

Logical Name THRESHOLD_1_0

Definition Free buffer thresholds separating "no overload" condition and"overload level 1" condition when pointer P points at position 0.

Coding rules –

Mandatory rules THRESHOLD_1_0 >= THRESHOLD_2_0



Type Threshold

SubSystem BSC

Instance BSC


% 0 100 25






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 28






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 55






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 31






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 34






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 37






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 40






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 43






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 46






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 49






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 52






TypeMigration

Rule –






Definition Free buffer thresholds separating "overload level 1" condition and"overload level 2" condition when pointer P points at position 0.

Coding rules –

Mandatory rules THRESHOLD_2_0 <= THRESHOLD_1_0



Type Threshold

SubSystem BSC

Instance BSC


% 0 100 22






TypeMigration

Rule –







Coding rules –




Type Threshold

SubSystem BSC

Instance BSC


% 0 100 25






TypeMigration

Rule –
