Bss18 Parm Dic

Kapsch CarrierCom France SAS

411-9001-124

Kapsch GSM BSS Parameter ReferenceUser Documentation

411-9001-124 Version 18.08 November 15, 2010 1.0


Global System for Mobile Communications (GSM)Release: V18.0 PC3Document number: 411-9001-124Document release date: November 15, 2010

Copyright © 2000-2010 Kapsch. All Rights Reserved.

The information contained in this document is the property of Kapsch CarrierCom France S.A.S. (in the following referred to as “Kapsch”). Except as specifically authorized in writing by Kapsch, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation and maintenance purposes only.

The content of this document is provided for information purposes only and is subject to modification. It does not constitute any representation or warranty from Kapsch as to the content or accuracy of the information contained herein, including but not limited to the suitability and performance of the product or its intended application.

Kapsch and the Kapsch logo are trademarks of Kapsch and/ or its licensors. All other trademarks are the property of their owners.



411-9001-124 18.08 1.0 Page 3 of 446

Contents

New in this release ............................................................................................................. 5

Introduction......................................................................................................................... 8

1. Overview............................................................................................................................... 9

1.1. Network configuration objects and their parameters............................................................................ 9

1.2. Different types of configuration parameters ....................................................................................... 12

1.3. Description of dictionary entries ......................................................................................................... 13

1.3.1. Header line......................................................................................................................................... 13

1.3.2. Main body of entries........................................................................................................................... 14

2. Parameters listed in alphabetical order........................................................................... 16

2.1. 3 ......................................................................................................................................................... 16

2.2. A......................................................................................................................................................... 19

2.3. B......................................................................................................................................................... 61

2.4. C ........................................................................................................................................................ 96

2.5. D ...................................................................................................................................................... 128

2.6. E....................................................................................................................................................... 143

2.7. F ....................................................................................................................................................... 161

2.8. G ...................................................................................................................................................... 171

2.9. H ...................................................................................................................................................... 179

2.10. I ...................................................................................................................................................... 192

2.11. J ..................................................................................................................................................... 210

2.12. L ..................................................................................................................................................... 211

2.13. M .................................................................................................................................................... 221

2.14. N ................................................................................................................................................... 252

2.15. O .................................................................................................................................................... 267

2.16. P .................................................................................................................................................... 291

Page 4 of 446 411-9001-124 18.08 1.0


2.17. Q ................................................................................................................................................... 319

2.18. R ................................................................................................................................................... 319

2.19. S .................................................................................................................................................... 338

2.20. T ..................................................................................................................................................... 370

2.21. U .................................................................................................................................................... 395

2.22. V..................................................................................................................................................... 405

2.23. W.................................................................................................................................................... 406

2.24. X..................................................................................................................................................... 407

2.25. Z ..................................................................................................................................................... 407

A. Objects and parameters evolution ................................................................................ 411

B. Objects and parameters evolution ................................................................................ 425

C. Parameters per feature ................................................................................................... 428

D. PCUSN components ....................................................................................................... 444

411-9001-124 18.08 1.0 Page 5 of 446


New in this release

The following section details what is new in Kapsch GSM BSS Parameter Reference(411-9001-124) for the V18 P&C 3 release.

FeaturesSee the following sections for information about feature changes:

• “V18.0 BTS software for Rail” on page 5

• “TMU3 introduction & TMU1 TMU2 TMU3 mixity” on page 5

• “preferredNonAdaptativeAMRcodec Class 3” on page 314 (2.16. “P” on page 291 and C.1. “AMR for group calls (VGCS or VBS)” on page 428)

• “Abis over IP on Optical BSC 3000 (34965)” on page 5

V18.0 BTS software for RailThe sections impacted by this feature are as follows:

• “AllocPriorityTimerT14Railways” on page 46

• “extendedTimingAdvanceWindow” on page 159

TMU3 introduction & TMU1 TMU2 TMU3 mixityThe sections impacted by this feature are as follows:

• “estimatedSiteLoad Class 3” on page 156

Specific TDMA Allocation for CS Data (27395)The sections impacted by this feature are as follows:

• “dataOnNoHoppingTS” on page 130

Abis over IP on Optical BSC 3000 (34965)This feature modifies the GSM BSC 3000 (optical configuration) to connect to its depen-dent BTS with an Abis interface that runs over an packetized IP network instead of a tra-ditional time-division multiplex carrier (E1 or T1).

The sections impacted by this feature are as follows:

• added the bsc30000electrical_ip value and a new check for the section “bscArchitec-ture Class 0” on page 73.

• added the bsc30000electrical_ip value in the section “ipgPcmList Class 3” on page 199.

• added the bsc30000electrical_ip value in the section “positionInShelf Class 0” on page 311.

• added the bsc30000electrical_ip value in the section “positionInShelf Class 0” on

Page 6 of 446 411-9001-124 18.08 1.0


page 311.

• added the bsc30000electrical_ip value in the section “shelfNumber Class 0” on page 344.

• added the bsc30000electrical_ip value in the section “shelfNumber Class 0” on page 344.

Other changesSee the following sections for changes that are not feature-related:

• Updated parameter description in “ipRoutingTable Class 3” on page 205.

• Renamed parameter ipIBOSEthernetPortUsed and its values in “ipIBOSEthernet-PortMonitored Class 3” on page 199.

• Changed value name in section “ipRedundancyProtocolOnAbisPort Class 3” on page 204.

• Changed value name in section “ipRedundancyProtocolOnIBOSPort Class 3” on page 205.

• Changed value name in section “ipRedundancyProtocolOnAggregatePort Class 3” on page 204.

• Updated description of parameter in section “ipCRPnChannel_userPriority Class 3” on page 197.

• Updated description of parameter in section “ipRTPnChannel_TosDscp Class 3” on page 206.

• Updated description of parameter in section “ipCRPnChannel_TosDscp Class 3” on page 196.

• Updated description of parameter in section “ipIBOSTraffic_TosDscp Class 3” on page 200.

• Updated description of parameter in section “ipPdvSelfTuningRange Class 2” on page 202.

• Changed recommended value in section “ipDefaultGateway Class 3” on page 197.

• Added section “ipServiceChannel_TosDscp” on page 208.

• Added section “ipSynchroType Class 2” on page 209.

• Added section “ipSelfTuning Class 2” on page 207.

• Added section “connectedHsaOnPort0 Class 3” on page 124.

411-9001-124 18.08 1.0 Page 7 of 446


• Added section “connectedHsaOnPort1 Class 3” on page 124.

• Modified description in section “ipPortAddress Class 3” on page 203.

• Added section “ipAggregateEthernetPortMonitored” on page 195.

Page 8 of 446 411-9001-124 18.08 1.0


Introduction

The Kapsch GSM BSS Parameter Reference is a guide that describes all GSM BSS net-work element parameters that the user can access using the OMC-R.

PrerequisitesUsers must be familiar with networking principles.

They must also be familiar with the following manuals:

Kapsch GSM BSS Documentation roadmap (411-9001-000)

Navigation• “Introduction” on page 8 contains general information on BSS operating parameters.

• Chapter 2. “Parameters listed in alphabetical order” on page 16 describes all the op-erating parameters listed in alphabetical order, and explains their use.

• A. “Objects and parameters evolution” on page 411 lists new configuration parame-ters and objects by release.

• B. “Objects and parameters evolution” on page 425 lists new configuration parame-ters and objects by release.

• C. “Parameters per feature” on page 428 presents BSS parameters per feature.

ATTENTIONFor a BSC 3000, there are no more class 1 parameters; all these parameters arenow class 0.

411-9001-124 18.08 1.0 Page 9 of 446


Chapter 1. Overview

1.1. Network configuration objects and their parametersThis dictionary summarizes all the GSM BSS parameters used to define all the objectsmanaged on the OMC-R. An object model is used to describe each managed networkelement. Each object is defined in terms of its parameters (also called attributes), andits relationships with other objects. A containment tree is used to depict the relationshipsamong these objects (see Figure 1., “Object main tree structure,” on page 9) toFigure 4., “Network subtree objects,” on page 10). For more information on objects andparameters, refer to Kapsch GSM BSS Fundamentals — Operating Principles (411-9001-007), for parameters listed per object, refer to Kapsch GSM OMC-R CommandsReference - Objects and Fault menus (411-9001-128).

FIGURE 1. Object main tree structure

FIGURE 2. omc subtree objects

ATTENTIONFor a BSC 3000, there are no more class 1 parameters; all these parameters arenow class 0.

Page 10 of 446 411-9001-124 18.08 1.0


FIGURE 3. md subtree objects

FIGURE 4. Network subtree objects

411-9001-124 18.08 1.0 Page 11 of 446


FIGURE 5. bsc 3000 subtree objects

FIGURE 6. btsSiteManager subtree objects

Users can create, modify, and delete objects using commands and actions displayed inthe menus of the OMC-R Browser window (see Figure 7., “Menus in the OMC-R brows-er window,” on page 12). Parameters are widely used in all commands and actions.

For more information on commands, refer to Kapsch GSM OMC-R Commands Refer-ence - Objects and Fault menus (411-9001-128) to Kapsch GSM OMC-R CommandsReference - Security, Administration, SMS-CB, and Help menus (411-9001-130).

Page 12 of 446 411-9001-124 18.08 1.0


FIGURE 7. Menus in the OMC-R browser window

For CT2000 and datafill purposes, the following remarks must be taken into consider-ation:

• If not indicated, the parameters are considered mandatory in all cases. For example, if a parameter is marked as Not Mandatory at the OMC-R level, the user does not need to employ it in CT2000, there will not be any value in the command files to cre-ate the associated object.

• A parameter is dependant of an OMC feature only when indicated. For any parameter associated with an OMC feature, if the feature is active at OMC-R then the parameter is mandatory at object creation otherwise it is not. Example: a parameter marked as "cell Tiering" dependant will only be used when the cellTiering feature is active at the OMC-R level.

• A parameter is considered product-dependant only when indicated and to be used only when the product is used in the network. For example, a parameter marked "BSC 3000" dependant is mandatory when the object to create/modify belongs to the "BSC 3000" architecture.

• CT2000 is an offline, multi-release CM OAM tool. The CT2000 . Throughout this doc-ument, the user will be able to distinguish whether a parameter present in CT2000 DRF interface needs to be filled or not, depending upon the actual network configu-ration.

1.2. Different types of configuration parametersThere are two types of configuration parameters: customer and manufacturer parame-ters.

411-9001-124 18.08 1.0 Page 13 of 446


• Customer parameters:

– addressing parameters, which are relative to objects (for example: bsc number)

– design parameters, which are relative to contract characteristics (for example:configRef, SiteName)

– optimization parameters, which are relative to network tuning (for example: cell-ReselectHysteresis)

– operating parameters, which are relative to network operation (for example: cell-Barred)

• Manufacturer parameters:

– system parameters, which can seriously affect system operation, and whichmust be under the control of the manufacturer (for example: runPwrControl)

– product parameters, which are incompatible with the current system release (forexample: sWVersionbackup)

New configuration parameters are summarized in A. “Objects and parameters evolution”on page 411.

1.3. Description of dictionary entriesEach parameter is described separately and arranged in alphabetical order.

Dictionary entries fall into two parts:

• the header line

• the main body, composed of several fields

1.3.1. Header lineThe header line contains some or all of the following information (see following figure):

• the name of the OMC-R parameter

• the class of the parameter (if any)

• the BSS version from which it applies

Page 14 of 446 411-9001-124 18.08 1.0


FIGURE 8. Header line

1.3.2. Main body of entriesThe main body contains up to nine fields:

• Description: parameter definition

• Value range: displayed in square brackets and the unit if any Example: [2 to 300] seconds

• Object: object name(s) in which the parameter is defined

• Default value: value which allows to deactivate the function

• Type: parameter type. The five accepted values are the following:

1. Dynamic parameters (DD) are not stored in databases. They are managed by theBSC applications, and they can be consulted on operator request.

2. Internal parameters (DI) are stored in the OMC-R operation database (BDE) and are not sent to Network Elements. They supply additional information on how an object

type meaning

is handled by the Configuration Management application

is handled by any other applications (4)

DD Dynamic data (1) X X(5)

DI Internal data (2) X

DP Permanent data (3) X X(6)

DS Static data X

Id Identifier X X(7)

411-9001-124 18.08 1.0 Page 15 of 446


is configured at a given time. They can be consulted on operator request and some of them can also be modified.

3. Permanent parameters (DP) are stored in the application database (BDA) and in the operation database (BDE). Most of them are mandatory and they are defined with the object that uses them. They are managed by the operator.

4. Fault Management, Performance Management, Command Functions.

5. parameter displayed in command output

6. parameter entered by users

7. parameter which is either entered by users, or displayed in command output

– Condition: It indicates the necessary conditions in which the parameter can beused.

– Checks: Semantic checks performed by the OMC-R are indicated with the Cre-ate [C], Set [M], Delete [D], or specific action [A] commands.

– Feature: Field introduced from V12. It indicates the reference of the Featurethat impacts the parameter description.

– Restrictions: Applicable restrictions are indicated with the Create [C], Set [M],Delete [D], or specific action [A] commands.

– Remark: optional field containing comments.

Page 16 of 446 411-9001-124 18.08 1.0


Chapter 2. Parameters listed in alphabetical order

For a BSC 3000, there are no more class 1 parameters; all these parameters are nowclass 0.

2.1. 3

3GAccessMinLevel

3GAccessMinLevelOffse

3GReselection ARFCN

Description:

Sub-parameter of the “gsmTo3GReselection Class 3” on page 178 parameter: gives the minimum threshold for Ec/No for the UTRAN FDD cell reselection (FDD only).

Object:bts

Value range:[-20 / -18 / -16 / -14 / -12 / -10 / -8 / -6]

Unit:dBm

Type:DP

Default value:-12

Release:V18.0.0

Description:

Sub-parameter of the “gsmTo3GReselection Class 3” on page 178 parameter: gives the minimum threshold offset for Ec/No for the UTRAN FDD cell reselection (FDD only).

Object:bts

Value range:[0]

Unit:dBm

Type:DP

Default value:0

Release:V18.0.0 P&C1

Description:

Sub-parameter of the “gsmTo3GReselection Class 3” on page 178 parameter: lists the ARFCN in the reselection mode for:

• FDD: neighboring UMTS cell ARFCN

• TDD: neighboring TD-SDCMA cell ARFCN

Object:bts

Value range:Maximum of 8 values are available for BSC V18.0.0 PC1 or higher, and only 4 four others]

411-9001-124 18.08 1.0 Page 17 of 446


3GReselectionOffsetl

3GReselectionThreshold

Note: For bsc V16.0 and v17.0, only value -102 is available.

Unit:dBm

Type:DP

Default value:Empty

Checks:

• [C/M]: It is forbidden to change the value of this parameter if the value

of the interferenceMatrixRunningOnBSC parameter of the bsc object is yes (which means the Interference Matrix feature is activated).

• [C/M]: Different TDD or FDD ARFCN must be configured.

• [C/M]: For BSS V18.0.0, if FDD technology is selected, the maximum

ARFCN list size is limited to 4.

• [C/M]: For BSS V18.0.0 or v17.0, if TDD technology is selected, the

maximum ARFCN list size is limited to 4.

Release:V18.0.0 P&C1

Description:

Sub-parameter of the “gsmTo3GReselection Class 3” on page 178 parameter: applies an offset to RLA_C for cell reselection to access the technology/mode FDD and TDD.

Object:bts

Value range:[-infinity / -28 / -24 / -20 / -16 / -12 / -8 / -4 / 0 / 4 / 8 / 12 / 16 / 20 / 24 / 28]

Unit:dBm

Type:DP

Default value:-infinity

Release:V18.0.0

Description:

Sub-parameter of the “gsmTo3GReselection Class 3” on page 178 parameter: gives the minimum threshold for RSCP for UTRAN FDD cell reselection (FDD only).

Object:bts

Value range:[-114 / -112 / -110 / -108 / -106 / -104 / -102 / -100 / -98 / -96 / -94 / -92 / -90 / -88 / -86 / -84]

Unit:dBm

Type:DP

Default value:-102

Release:V18.0 P&C1

Page 18 of 446 411-9001-124 18.08 1.0


3GSearchLevel

3GTechnology

Description:

Sub-parameter of the “gsmTo3GReselection Class 3” on page 178 parameter: search for 3G cells (FDD or TDD) if the signal level is below -98 dBm or above -54 dBm.

Object:bts

Value range:

[less than -98 dBm / less than -94 dBm / less than -90 dBm / less than -86 dBm / less than -82 dBm / less than -78 dBm / less than -74 dBm / Always / more than -78 dBm / more than -74 dBm / more than -70 dBm / more than -66 dBm / more than -62 dBm / more than -58 dBm / more than -54 dBm / Never]

Unit:dBm

Type:DP

Default value:Never

Release:V18.0

Description:Sub-parameter of the “gsmTo3GReselection Class 3” on page 178 parameter: specifies the FDD or TDD 3G technology selection.

Object:bts

Value range:[FDD (0) /TDD (1)]

Unit:dBm

Type:DP

Default value:FDD

Checks:

[C/M]: If the 3GTechnology parameter is set to the FDD value, there is a control thatUARFCNs are allowed by 3GPP TS 25.101.UARFCNs must be part of the DL ARFCN range defined in 3GPP TS 25.101 Rel 7:for UMTS 2000: 10562 to 10838for UMTS 1900: 9662 to 9938, 412, 437, 462, 487, 512, 537, 562, 587, 612, 637, 662, 687for UMTS 1800: 1162 to 1513for UMTS 1700/2100: 1537 to 1738,1887, 1912, 1937, 1962, 1987, 2012, 2037, 2062, 2087 for UMTS 850: 4357 to 4458, 1007, 1012, 1032, 1037, 1062, 1087for UMTS 800: 4387 to 4413, 1037, 1062for UMTS 2600: 2237 to 2563, 2587, 2612, 2637, 2662, 2687, 2712, 2737, 2762, 2787, 2812, 2837, 2862, 2887, 2912

for UMTS 900: 2937 to 3088for UMTS 1700: 9237 to 9387

411-9001-124 18.08 1.0 Page 19 of 446


2.2. A

abisSpy Class 3

absoluteRFChannelNo Class 2

[C/M]: If the 3GTechnology parameter is set to the TDD value, there is a control that UARFCNs are allowed by 3GPP TS 25.102. UARFCNs must be part of the DL ARFCN range defined in 3GPP TS 25.102 Rel 7:for frequencies between 1900 and 1920 MHz, the UARFCN uplink and downlink transmission is included in the range from 9504 to 9596.for frequencies between 2010 and 2025 MHz, the UARFCN uplink and downlink transmission is included in the range from 10054 to 10121.for frequencies between 1850 and 1910 MHz, the UARFCN uplink and downlink transmission is included in the range from 9254 to 9546.

for frequencies between 1930 and 1990 MHz, the UARFCN uplink and downlink transmission is included in the range from 9654 to 9946.for frequencies between 1910 and 1930 MHz, the UARFCN uplink and downlink transmission is included in the range from 9554 to 9646.for frequencies between 2570 and 2620 MHz, the UARFCN uplink and downlink transmission is included in the range from 12854 to 13096.

Release:V18.0

Description:Whether measurement reports from the BTS and the mobiles are forwarded to the BSC in order to spy on the Abis Interface.

Value range:[in progress / not in progress]

Object:bts

Default value:not in progress

Type:DP

Description:

Radio frequency used in the network frequency band by a radio time slot that does not obey frequency hopping laws. Setting this attribute forbids the radio time slot to obey frequency hopping laws.The frequency of the radio time slot that carries a cell BCCH in a TDMA frame (channelType = "mainBCCH", "mainBCCHCombined", or "bcchSdcch4CBCH") is not managed by users. When the parent bts object is unlocked, the system automatically assigns the cell bCCHFrequency to the concerned channel object and updates it whenever it is changed.

Value range:

[1 to 124] (GSM 900 network), [955 to 1023] / [0 to 124] (GSM-R), [975 to 1023] / [0 to 124] (E-GSM), [512 to 885] (GSM 1800 network), [512 to 810] (GSM 1900 network), [128 to 251] (GSM 850 network), [955 / 1023] / [0 / 55] (GSM-R).

Object:channel

Condition:To define if the TDMA does not hop

Page 20 of 446 411-9001-124 18.08 1.0


access time end

access time start

accessClassCongestion Class 3

Type: DP

Checks:

[C/M]: The attribute is undefined when the radio time slot is authorized to hop or its channelType is "mainBCCH", "mainBCCHC ombined", or "bcchSdcch4CBCH".[C/M]: The attribute is defined when the radio time slot is not authorized to hop and its channelType is "tCHFull", "sDCCH", "sdcch8CBCH", or "cCH".[C/M]: When defined, the frequency is one of those allotted to the parent bts object (cellAllocation list).[M]: Concentric cell: When defined, the frequency is not used by the channel objects related to the transceiver objects allotted to the other cell zone.[C/M]: If the frequency hopping is not used, the absoluteRFChannelNo attribute indicates a radio frequency number which is located between [0 to 124] or [955 to 1023] when the standardIndicator attribute is equal to ’Rgsm.’

Description:Time of the day after which the user is not allowed to log in.It is after access time start.

Value range:[<time> (18:00)]

Object:user profile

Type:DP

Checks:[C/M]: access time end is after access time start.

Description:Time of the day after which the user is allowed to log in.

Value range:[<time> (09:00)]

Type:DP

Checks:[C/M]: access time start is before access time end.

Description:List of access classes that are not authorized in a cell during TCH congestion phase (class 10 not included).

Value range:[0 to 9] User classes[11 to 15] Operator classes

Object:bts

Type:DP

ReleaseV9

411-9001-124 18.08 1.0 Page 21 of 446


accessibilityState

acknowledged by

acknowledgment time

activationObject

Description:MSC accessibility state

Value range:

[reachable / congested / unReachable]reachable................. The remote signaling point is within reach.congested................. 80% of the BSC pool of buffers handling outgoing MSC messages is full. unReachable...... The remote signaling point is out of reach.

Object:signallingLinkSet

Type:DD

Description:

To select alarms acknowledged by a given user. Enter the user’s name as defined in the user’s profile.Do not fill in if this criterion is not to be selected.

Value range:[case sensitive]

Object:Alarm logs - Filter

Type:DP

Description:To select messages acknowledged at that time.

Value range:

Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in if this criterion is not to be selected.

Object:Alarm logs - Filter

Type:DP

Description:Identifier or name of the traced bsc object on the OMC-R.

Value range:[bscId range]

Object:callPathTrace

Type:DP

Checks:

[C]: The bsc object is created.[C]: The callPathTrace object is not created for the bsc object. The Call path tracing function isunique in a given BSS.

Restrictions:[M]: This attribute cannot be modified.

Page 22 of 446 411-9001-124 18.08 1.0


activationObject

adaptiveReceiver Class

Note: This parameter is only available for BSC 3000. It is visible only in GPRS.

additional supervised PCM 0 Class 2

Description:Identifier or name of the traced bsc object on the OMC-R.

Value range:[bscId range]

Object:traceControl

Type:DP

Checks:

[C]: The bsc object is created.[C]: The traceControl object is not created for the bsc object. The Call path tracing function isunique in a given BSS.

Restrictions:[M]: This attribute cannot be modified.

Description:

Allows a return to the initial receiver processing for either peculiar cell configurations or both of them.In a first step, the parameter is a simple switch, but more than one bit should be allocated to handle later extensions (automatic recognition of configurations requiring the initial receiver processing).

Value range:0/1 (0: disabled, 1: enabled)

Object:transceiver

Default value:disabled

Type:DP

Release:V17

Description:

Configuration of a new alarm controlled by a BTS in Drop and Insert configuration. The alarm is sent when a level 1 transmission network link failure is detected by the BTS, and is caused by an odd PCM port connected with a physical PCM link on the Abis interface between the BSC and one of the following BTSs:BTS 18000S12000S8000 BTS with BCFS8000 BTS with CBCFS8002 BTS with CBCFS2000 H/L BTSe-cell

Value range:

[yes (the odd PCM link is supervised by the BTS) / no (the odd PCM link is not supervised by the BTS)] If PCM 0 belongs to the bscSitePCMList parameter the values YES or NO are equivalent (recommendation: NO)

Object:btsSiteManager

411-9001-124 18.08 1.0 Page 23 of 446




Feature:GSM-R V12

Type: DP

Release:V12

Description:


Value range:



Feature:GSM-R V12

Type: DP

Release:V12

Description:


Value range:



Feature:GSM-R V12

Page 24 of 446 411-9001-124 18.08 1.0




Type: DP

Release:V12

Description:


Value range:



Feature:GSM-R V12

Type: DP

Release:V12

Description:


Value range:



Feature:GSM-R V12

Type: DP

Release:V12

411-9001-124 18.08 1.0 Page 25 of 446



Description:


Value range:



Feature:GSM-R V12

Type: DP

Release:V12

Page 26 of 446 411-9001-124 18.08 1.0


additional unmasked users alarms Class 2

Description:

Configuration of the new user (unprotected) external alarm loops controlled by the BTS (added to the already existing unprotected external alarms, see parameter "unmasked users alarms"). These additional alarms are detected by the RECAL board of the main cabinet. When an alarm is unmasked, it means the relevant equipment is monitored by the BTS. There are 24 additional user (unprotected) alarms on the S8002 BTS, 14 alarms on the S8000 Outdoor BTS, and 20 alarms on the S8000 Indoor BTS. A user alarm is used when an external item of equipment is inserted in the BTS (a microwave terminal for instance) and does not require a new DLU.

Value range:

[All alarms maskedAlarm 1 unmaskedAlarms 1 to 2 unmaskedAlarms 1 to 3 unmaskedAlarms 1 to 4 unmaskedAlarms 1 to 5 unmaskedAlarms 1 to 6 unmaskedAlarms 1 to 7 unmaskedAlarms 1 to 8 unmaskedAlarms 1 to 9 unmaskedAlarms 1 to 10 unmaskedAlarms 1 to 11 unmaskedAlarms 1 to 12 unmaskedAlarms 1 to 13 unmaskedAlarms 1 to 14 unmaskedAlarms 1 to 15 unmaskedAlarms 1 to 16 unmaskedAlarms 1 to 17 unmaskedAlarms 1 to 18 unmaskedAlarms 1 to 19 unmaskedAlarms 1 to 20 unmaskedAlarms 1 to 21 unmaskedAlarms 1 to 22 unmaskedAlarms 1 to 23 unmaskedAlarms 1 to 24 unmasked]


Feature:GSM-R V12

Type: DP

Release:V12

411-9001-124 18.08 1.0 Page 27 of 446


addresses

adjacent cell umbrella ref Class 3

adjacentCellHandOver

Description:

Definition of the OMC-R user(s) to whom the message is addressed.Select the all option to send the message to all OMC-R users.Select the users option to send the message to selected OMC-R users. Enter their names as defined in their profiles [case sensitive], separated by the "&" character.

Object:user message - Answer / New message

Type:DP

Description:Identifier of the adjacentCelHandOver object that describes the neighbor cell towards which a directed retry will be triggered in BSC mode.

Value range:[0 to 31]

Object:bts

Type:DP

Checks:

[C/M]: The preferential umbrella cell must refer to an existing adjacentCellHandOver object instance.[C/M]: When the function "directed retry" is made by interrogation of the BTS, the preferential umbrella cell must not be indicated.

ReleaseV9

Description:

Identifier of an adjacentCellHandOver object that defines a neighbor cell of a serving cell for handover management purposes. A bts object may reference up to thirty-two objects of this type.


Object:adjacentCellHandOver

Type:Id

Checks:

[C]: The associated bts object is created and theadjacentCellHandOver object is not created for that object.[C]: The number of adjacentCellHandOver objects created for a bts object is limited to maxAdjCHOARMPerBts (static configuration data).[C/M]: The (baseColourCode, bCCHFrequency, networkColourCode) combination is unique in the set including a serving cell and its neighbor cells.[C/D]: If the related BSC application database is built, the parent bsc object is unlocked. [M]: The parent bsc object is unlocked.[M/D]: The adjacentCellHandOver object is created.[D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.

Page 28 of 446 411-9001-124 18.08 1.0


adjacentCellHandOverId

adjacentCellReselection

adjacentCellReselectionId

[D]: No mdScanner object refers to the adjacentCellHandOver object (no observation is running on that object).[D]: At least one adjacentCellHandOver object should be created for the bts object.

ReleaseV8

Description:

Identifier of an adjacentCellHandOver object that defines re-selection management parameters for a serving cell.A bts object may reference up to sixty-four objects of this type.


Object:adjacentCellHandOver

Type:DP

ReleaseV14

Description:

Identifier of an adjacentCellReselection object that defines re-selection management parameters for a serving cell. A bts object may reference up to thirty-two objects of this type.


Object:adjacentCellReselection

Type:Id

Checks:

[C]: The bts object is created and the adjacentCellReselection object is not created for that object.[C]: The number of adjacentCellReselection objects created for a bts object is limited to maxAdjCHOARMPerBts (static configuration data).[M]: The parent bsc object is unlocked. [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked.[M/D]: The adjacentCellReselection object is created.[D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.

ReleaseV8

Description:

Identifier of an adjacentCellReselection object that defines re-selection management parameters for a serving cell.A bts object may reference up to sixty-four objects of this type.


Object:adjacentCellReselection

411-9001-124 18.08 1.0 Page 29 of 446


administrativeState

administrativeState

administrativeState

Type:DP

ReleaseV14

Description:

Activation state of an alarm criteria.An alarm criteria is created in unlocked state.The OMC-R Fault Management function ignores the inactive criteria when processing notifications.

Value range:[locked / unlocked]

Object:alarm criteria

Type:DP

Description:ISO state

Value range:[locked (inactive) / unlocked (active)]

Object:atmRm

Feature:BSC/TCU e3: AR 1209

Type:DP

Release:V13


Value range:[locked (inactive) / unlocked (active)]A bsc object is created in locked state.

Object:bsc

Type:DP

Checks:

[M]: If mobileCountryCode and mobileNetworkCode are defined for the bsc object, they match those of all dependent bts objects.[M]:The following check is only performed when the bsc object is unlocked:The dependent software object is created and its sWVersionRunning attribute defines a software version downloaded to the BSC disk.

Page 30 of 446 411-9001-124 18.08 1.0


administrativeState

administrativeState


Value range:

[locked / unlocked]A bscMdInterface object is created in unlocked state.When the object is locked, the BSC involved in the BSS/OMC-R link described by this object cannot communicate with the OMC-R.

Object:bscMdInterface

Type:DP

Checks:[M]: The concerned bsc object is unlocked.

Description:

ISO stateA bts object is created in locked state. When the object is unlocked, the described cell will be working if the carrier TDMA frame (or BCCH frame) is successfully configured in the BTS and at least <minNbOfTDMA> TDMA frames (including the carrier frame) are operating.The dataOnNoHoppingTS attribute enables/disables to establish a data call on non-hopping TDMA on a FR channel for the 2.4, 4.8, 9.6 data rates. When this parameter is changed to unlock state, the RTU semantic control is performed.The attempt to activate the Specific TDMA Allocation for CS Data functionality succeeds only when a valid license is available. When there is at least one built BSC with "dataOnNoHoppingTS" activated, then, no TRX, bts, btsSiteManager, unlocking, no reset BDA build and no build BDA is possible without a valid license.

The preferredNonAdaptativeAMRcodec attribute enables/disables to establish an AMR call on a FR channel with the AMR codec modes 4.75, 5.9, 6.7 & 10.2 as configured.The attempt to activate the Non-Adaptative AMR Codec For Group Calls functionality succeeds only when a valid license is available. When there is at least one built BSC with “preferredNonAdaptativeAMRcodec” activated, then, no TRX, bts, btsSiteManager, unlocking, no reset BDA build and no build BDA is possible without a valid license.

Value range:[locked / unlocked / shuttingDown (soft release)]

Object:bts

Type:DP

411-9001-124 18.08 1.0 Page 31 of 446


Checks:

[M]: The parent bsc object is unlocked.[M]: It is not possible to change from "shuttingD own" to "unlocked" or from "locked" to "shuttingDown".M]: It is not possible to change to "shuttingDown" if the application database of the related BSC is not built.The following checks are only performed when the bts object is unlocked:The associated handOverControl and powerControl objects are created for the bts object.The mobileCountryCode and mobileNetworkCode attributes match those of the parent bsc object when they are defined for that object.The frequencies in the cellAllocation list comply with the standardIndicator attribute value.The minNbOfTDMA attribute value is less than or equal to the number of transceiver objects created for the bts object.

Cavity cell: The number of dependent transceiver objects equals the number of frequencies in the cellAllocation list.Eight channel objects are created for each dependent transceiver object if the cell works in normal mode, four channel objects are created for each dependent transceiver object if the cell works in extended mode.The following apply:Only one of them has a channelType equal to "mainBCCH", "mainBCCHCombined", or "bcchSdcch4CBCH".If the smsCB attribute of the bts object is "used", one of them has a channelType equal to "sdcc8CBCH" or "bcchSdcch4CBCH".Concentric cell:Two transceiverZone objects are created for the bts object.

Each dependent transceiver object refers to a transceiverZone object (transceiver zone Ref is defined).All channel objects describing the cell BCCH or common channels (channelType = "cCH") depend on transceiver objects allotted to the outer zone.If frequency hopping is allowed in a zone (zone frequency hopping), it is allowed in the cell (btsIshopping).The frequencies used by the transceiver objects in a zone are separate from the frequencies used by the transceiver objects in the other zone.

Releasing a bts object by shutting down sustains the callssupported by the described cell. The system actions are as follows:Radio resources remain allocated until the calls end.Once a TDMA frame is released, a CLEAR CONFIG REQUEST message is sent to the partnered TRX/DRX.When all calls are terminated, the cell is released (administrativeState = "locked" and operationalState = "disabled") and the concerned TRX/DRXs and TDMA frames are unreachable (availabilityStatus = "{dependency}".

Page 32 of 446 411-9001-124 18.08 1.0


administrativeState

Notes:

It is recommended to bar direct access to the cell before initiating a soft release (cellBarred = "barred"), to prevent off-call mobiles from listening to the cell during the soft release phase, so they can immediately re-select another cell for receiving or sending calls. It is recommended also to forbid incoming handovers in the cell (incomingHandOver = "disabled"), to remove the cell from the list of eligible cells and, thus, avoid its selection if the BTS receives such a request.In order to speed up the soft release process, the Force HandOvers command can be used first to redirect the traffic currently handled by the serving cell towards its neighbor cells.If a hard lock request is sent during the soft release phase, all the calls supported by the cell are immediately released by the BSC.

If the administrativeState of the object is unlocked and the availabilityStatus is unknown, the object status is undetermined. You must request the status of the bsc object on the OMC-R, to update the network view.

Description:

ISO state. The dataOnNoHoppingTS attribute enables/disables to establish a data call on non-hopping TDMA on a FR channel for the 2.4, 4.8, 9.6 data rates. When this parameter is changed to unlock state, the RTU semantic control is performed.The attempt to activate the Specific TDMA Allocation for CS Data functionality succeeds only when a valid license is available. When there is at least one built BSC with "dataOnNoHoppingTS" activated, then, no TRX, bts, btsSiteManager, unlocking, no reset BDA build and no build BDA is possible without a valid license.


Value range:[locked / unlocked]A btsSiteManager object is created in locked state..


Type:DP

411-9001-124 18.08 1.0 Page 33 of 446


administrativeState

administrativeState

Checks:

[M]: The parent bsc object is unlocked.The following checks are only performed when the btsSiteManager object is unlocked:The scheduled time slot (pcmTimeSlotNumber) is masked in the btsSiteManager object radioSiteMask.The radioSiteMask of all btsSiteManager objects sharing a same PCM link in the BSS are dissociated and their scheduled time slots are different and masked in their radioSiteMask.The bscSitePcmList list includes at least two items if the btsSiteManager object redundantPcmPresence attribute is "true".All pcmCircuit objects referenced in the list (pcmCircuitBsc components) are created for the parent bsc object and assigned to the Abis interface.One of them identifies a PCM link with a pcmCircuitBtsSiteManager reference in the range [0 to 3] for clock synchronization.

The greatest bts object identifier must be lower than the maxNbOfCells value of the parent btsSiteManager object.The configRef attribute defines a DLU file downloaded to the BSC disk.The dependent software object is created and its sWVersionRunning attribute defines a software version downloaded to the BSC disk.If the administrativeState of the object is unlocked and the availabilityStatus is unknown, the object status is undetermined. You must request the status of the bsc object on the OMC-R, to update the network view.

Description:ISO state. Locking the object blocks the collection of data and the generation of the associated messages.

Value range:

[locked / unlocked]A callPathTrace object is created in locked state. Unlock the object to start collecting data in the related BSC.In that case, data collecting is stopped in the related BSC.However, current messages are stored by the BSC and notified to the OMC-R agent.

Object:callPathTrace

Type:DP

Notes:

If trace data collecting is stopped by locking the object, the BSC continues to send the current trace messages to the OMC-R agent, but no notifications are issued.If trace data collecting is stopped by locking the object or on reaching the end-of-session criterion, it is automatically restarted whenever the callPathTrace object is unlocked. For instance, if the end-of-session criterion defines a period of time that elapsed, data collecting will restart for the entire period.

Description:ISO state.


Object:cc

Page 34 of 446 411-9001-124 18.08 1.0


administrativeState

administrativeState

administrativeState

administrativeState


Type:DP

Release:V13



Object:cem


Type:DP

Release:V13



Object:controlNode


Type:DP

Release:V13

Description: ISO state. Locking the object blocks the transmission of the associated messages to the OMC-R manager. The administrativeState of an efd object is set by the user at object creation time and can be changed with the Modify command.

Value range: [locked / unlocked]

Object: efd

Type: DP

Description: ISO state.


Object: g3BscEqp

Feature: BSC/TCU e3: AR 1209

411-9001-124 18.08 1.0 Page 35 of 446


administrativeState

administrativeState

administrativeState

administrativeState

administrativeState

Type: DP

Release: V13



Object: hardware transcoder 3G


Type: DP

Release: V13



Object: hsaRc

Feature: BSC 3000 optical

Type: DP

Release: V17



Object: hsaRcTcu

Feature: TCU 3000 optical

Type: DP

Release: V17



Object: iem


Type: DP

Release: V13


Value range: [unlocked]The igm object is always unlocked.

Object: igm

Page 36 of 446 411-9001-124 18.08 1.0


administrativeState

administrativeState

administrativeState

administrativeState

Feature: Abis Over IP

Type: DP

Release: V18.0



Object: iom

Feature: BSC 3000 optical / TCU 3000 optical

Type: DP

Release: V17



Object: interfaceNode


Type: DP

Release: V13



Object: ipgRc


Type: DP

Release: V18.0


Value range: [locked / unlocked]Locked administrativeState means no communication between the IPM and the IPG, so all the data flow are stopped between the IPM and the IPG.Unlocked administrativeState means messages have been sent to the IPM and the IPG to establish the communication between the IPM and the IPG.

Object: ipm


Type: DP

411-9001-124 18.08 1.0 Page 37 of 446


administrativeState

administrativeState

administrativeState

administrativeState

Release: V18.0

Checks: [C/M]: It is forbidden to unlock the ipm object if it does not refer to any btsSiteManager object.[C/M]: Only one IPM among IPMs with the same MAC address can be unlocked.

Description: Activation state of a repeated jobA job object is created in unlocked state.When a job is set inactive, it is not run.

Value range: [locked (inactive) / unlocked (active)]

Object: job

Type: DP

Checks: [M]: The job is not running.

Description: ISO state. It is set by the OMC-R agent.

Value range: [locked (= restored log) / unlocked (= current log)]An unlocked log object describes a current log on the OMC-R agent disks. A locked log object describes a log restored on the disks.

Object: log - Display

Type: DP

Notes: The attributes of the log objects are not managed by users.



Object: lsaRc


Type: DP

Release: V13

Description: ISO state. Locking the object blocks the generation of processed alarms when out-of-range conditions are met. The administrativeState of an mdWarning object is set by the user at object creation time and can be changed with the Modify command. A change of state is effective when the OMC-R is restarted.Whatever the state of the object, the related notifications are always forwarded to the OMC-R manager.


Object: mdWarning

Type: DP

Page 38 of 446 411-9001-124 18.08 1.0


administrativeState

administrativeState

administrativeState

administrativeState

administrativeState



Object: mms


Type: DP

Release: V13



Object: omu


Type: DP

Release: V13


Value range: [locked / unlocked]A pcmCircuit object is created in locked state.

Object: pcmcircuit

Type: DP

Checks: [M]: The parent bsc object is unlocked.


Value range: [locked / unlocked]A pcu object is created in locked state.

Object: pcu

Feature: GPRS (SV407 - V12)

Type: DP


Release: V12


Value range: [locked / unlocked]A signallingLink object is created in locked state.

Object: signallingLink

411-9001-124 18.08 1.0 Page 39 of 446


administrativeState

administrativeState

administrativeState

Type: DP




Object: sw8kRm

Type: DP


Release: V13



Object: tmu

Type: DP


Release: V13

Description: ISO state. Locking the object blocks the collection of data and the generation of the associated messages.

Value range: [locked / unlocked]A traceControl object is created in locked state. Unlock the object to start collecting trace data in the related BSC.

Object: traceControl

Type: DP


Notes: If trace data collecting is stopped by locking the object, the BSC continues to send the current trace messages to the OMC-R agent, but no notifications are issued.If traced calls are not terminated when the object is locked, all trace information related to those calls will be lost, unless partial record generation was requested. In that case, only data that are not yet recorded will be lost.Trace data collecting is automatically restarted in the BSC whenever the traceControl object is unlocked.

Page 40 of 446 411-9001-124 18.08 1.0


administrativeState

Description: ISO state. ISO state. The dataOnNoHoppingTS attribute enables/disables to establish a data call on non-hopping TDMA on a FR channel for the 2.4, 4.8, 9.6 data rates. When this parameter is changed to unlock state, the RTU semantic control is performed.The attempt to activate the Specific TDMA Allocation for CS Data functionality succeeds only when a valid license is available. When there is at least one built BSC with "dataOnNoHoppingTS" activated, then, no TRX, bts, btsSiteManager, unlocking, no reset BDA build and no build BDA is possible without a valid license.


Value range: [locked / unlocked / shuttingDown (soft release)]A transceiverEquipment object is created in locked state.

Object: transceiverEquipment

Type: DP

Checks: [M]: The parent bsc object is unlocked.[M]: It is not possible to change from "shuttingDown" to "unlocked" or from "locked" to "shuttingDown".[M]: It is not possible to change to "shuttingDow n" if the application database of the related BSC is not built.The following checks are only performed when the transceiverEquipment object is unlocked:The lapdLinkOMLRef and lapdLink RSLRef attributes of the transceiverEquipment object refer to lapdLink objects using the same lapdTerminalNumber in the parent BSC.The related software object is created and its sWVersionRunning attribute defines a software version downloaded to the BSC disk.Releasing a transceiverEquipment object by shutting down sustains the calls supported by the described TRX/DRX and the partnered TDMA frame. The system actions which may be carried out are the following:

411-9001-124 18.08 1.0 Page 41 of 446


administrativeState

administrativeState

administrativeState

To carry out a soft release. This action does not automatically cause a handover. By carrying out this action, the operator must wait for the end of the coms before the TRX/DRX changes to "blocked".To carry out a forced handover. A forced handover on the bts object will cause the DRX/TRX to change to "blocked" more quickly.If the TDMA frame affected by this operation has priority over other frames in the BSS, the BSC re-configures that frame on a different TRX/DRX and immediately transfers the current calls handled by the TRX/DRX being released.When all calls are transferred or terminated, the TRX/DRX is released (administrativeState = "locked" and operationalState = "disabled"), and the partnered TDMA frame is unreachable if it has not been reconfigured (availabilityStatus = "{dependency}".

Notes: If a hard lock request is sent during the soft release phase, all the calls handled by the TRX/DRX are immediately released by the BSC. If the administrativeState of the object is unlocked and the availabilityStatus is unknown, the object status is undetermined. You must request the status of the bsc object on the OMC-R, to update the network view.


Value range: [locked / unlocked]A transcoder object is created in locked state.

Object: transcoder

Type: DP

Checks: [M]: The parent bsc object is unlocked. The following checks are only performed when the transcoder object is unlocked:All transcoder objects created for the same parent bsc object refer to lapdLink objects that use the same lapdTerminalNumber in the BSC.



Object: trm


Type: DP

Release: V13


Value range: [locked / unlocked / shuttingDown (soft release)] An xtp object is created in locked state.

Object: xtp

Type: DP

Page 42 of 446 411-9001-124 18.08 1.0


agprsFilterCoefficient Class 3

agpsTimer Class 3

alarm criteria

Checks: [M]: The parent bsc object is unlocked.[M]: It is not possible to change from "shuttingDown" to "unlocked" or from "locked" to "shuttingDown".[M]: It is not possible to change to "shuttingDown" if the application database of the related BSC is not built.The BSC will refuse to unlock a terrestrial traffic circuit that could break the OMC channel connection down. Releasing an xtp object by shutting down sustains the call supported by the described terrestrial traffic circuit. The system actions are as follows:Any further attempt of the MSC to allocate the terrestrial circuit is refused.When the call is completed, the terrestrial circuit is released (administrativeState = "locked" and operationalState = "disabled").

Notes: All terrestrial circuits supported by a given PCM link can be softly released at the same time. If the PCM link supports a signaling link, it remains operating.If a hard lock request is sent during the soft release phase, the call supported by the terrestrial circuit is immediately released by the BSC.

Description: The load of each cell considered in dynamic AGPRS algorithm is filtered with a forgetting factor given by agprsFilterCoefficient.

Value range: [0 to 100] %

Object: bts

Deafult value: 0 (deactivates the feature in the cell at the PCU level).

Type: DP

Release: V14

Description: Duration of an A-GPS location.

Value range: [0 to 255] seconds

Object: bsc

Deafult value: 0 second

Type: DP

Release: V15

Note: This parameter is optional.

Description: Active alarm configuration.

Value range: [day configuration / night configuration / specific configuration / reference configuration]The active configuration is the alarm criteria configuration currently used by the OMC-R Fault Management function for fault processing. The names given to the alarm operating configurations (day / night / specific) only serve to identify them. Any configuration may be activated at any time by users, but only one can be active at a time.

Object: omc

411-9001-124 18.08 1.0 Page 43 of 446


alarm criteria

alarm number

alarm severity

alarm state

Type: DP

Note: When the OMC-R is started up or the active server is switched over, the OMC-R activates the configuration the name of which corresponds to the time of the day that start-up or switchover occurs. The following apply:The daytime configuration is activated when the event occurs between 9:00 a.m. and 6:00 p.m. (static configuration data).The nighttime configuration is activated when the event occurs between 6:00 p.m. and 9:00 a.m. (static configuration data).The active configuration can be forced by users at any other time. If a problem occurs while loading the selected configuration, the OMC-R uses the reference configuration and sends a warning message to the user.

Description: Identifier of an alarm criterion on the OMC-R.

Value range: [0 to 99 999] (manufacturer configuration) Users can lock / unlock alarmcriteria which IDs are lower than 100 000.Users can create / modify / delete criteria, which IDs are greater than or equal to 100 000.

Object: alarm criteria

Type: Id

Checks: [C]: The alarm criteria identifier is in the range [100 001 to 2 147 483 646].[C]: The alarm criteria does not exist in the operator configurations.[M/D]: The alarm criteria exists in the operator configurations.

Description: To select alarms with a given number.Do not fill in if this criterion is not to be selected.

Value range: [0 to 2147483646]

Object: Alarm logs - Filter

Type: DP

Description: To select alarms according to the severity.Do not fill in if this criterion is not to be selected.

Value range: [critical / major / minor]


Type: DP

Description: To select alarms according to the acknowledgement state. Do not fill in if this criterion is not to be selected.

Value range: [acknowledged / unacknowledged]

Page 44 of 446 411-9001-124 18.08 1.0


alarmDuration

alarmDuration

alarmPriority


Type: DP

Description: Alarm hold duration when a counter is involved.

Value range: [0 to 345600] second


Condition: To define if a counter is associated with the criterion.

Type: DP

Description: Alarm hold duration when a counter is involved.

Value range: [0 to 345600] second



Type: DP

Description: Alarm processing priority.

Value range: [CLEARED / critical / indeterminate / major / minor / warning]There are six defined priority levels which provide an indication of how it is perceived that the capability of the managed object has been affected. The following definitions are used:CLEARED: ...... The cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this managed object that have the same type, probable cause, and specific problems.critical: ......... The critical severity level indicates that a service affecting condition has occurred and an immediate corrective action is required.indeterminate: .... The indeterminate severity level indicates that the severity level of the service affecting condition cannot be determined. major: .......... The major severity level indicates that a service affecting condition has developed and a deferred corrective action is required.

minor: .......... The minor severity level indicates the existence of a non-service affecting fault condition and that a corrective action should be taken in order to prevent a more serious fault. warning: ......... The warning severity level indicates the detection of a potential or impending service affecting fault, before any significant effects have been felt. An action should be taken to further diagnose and correct the problem in order to prevent it from becoming a more serious service affecting fault.

Object: mdWarning

Type: DP

411-9001-124 18.08 1.0 Page 45 of 446


allocationState

allocPriorityTable Class 3

allocPriorityThreshold Class 3

Description: TDMA frame allocation state

Value range: [available / not available / not significant] available ................. The SACCH FILLING messages containing the SYS INFO 5 and 6 have been acknowledged by the BTS.not available .... The SACCH FILLING messages containing the SYS INFO 5 and 6 have not been acknowledged by the BTS.not significant .... The SACCH FILLING messages containing the SYS INFO 5 and 6 have not been sent to the BTS by the BSC.

Object: transceiver

Type: DD

Description: Table of conversion of the 18 external priorities (14 are GSM external priorities) to 13 internal priorities. (See Default value below.)

Value range: [0 to 12] "0" defines the highest priority.

Object: bts

Feature: WPS queuing management (22463)

Default value: 0 8 9 10 11 12 0 0 0 0 0 0 0 0 0 0 0 0

Type: DP

Description: Number of free TCHs needed for processing a TCH allocation request with an internal priority higher than 1.These channels are reserved to allocation requests with a maximum internal priority (priority 0).The TCH allocation is performed according to algorithm in the following table:


Object: bts

Default value: 0

Type: DP

Number of freeTCH = 0

1 <= Number of free TCH <= allocPriorityThreshold

Number of free TCH> allocPriorityThreshold

TCH request of priority 0

- queueing if defined or - reject

TCH allocated TCH allocated

TCH request of priority >0



TCH allocated

Page 46 of 446 411-9001-124 18.08 1.0


allocPriorityTimers Class 3

AllocPriorityTimerT14Railways

allocWaitThreshold Class 3

allOtherCasesPriority Class 3

Description: Table of timers defining the maximum queuing time of TCH allocation requests (public and WPS requests), according to the internal priority.

Value range: [List of 13 elements]: [0-255] seconds

Object: bts


Default value: 0 0 0 0 0 0 0 0 28 28 28 28 28

Type: DP

Description: Table of T14 timers, specifying the max queuing duration that can be allowed for a VGCS/VBS request, according to the internal priority.

Value range: List of 13 elements in the range [0 to 65535].

Object: bts

Feature: Timer T14 introduction for group call queueing (35098)

Default value: 0 0 0 0 0 0 0 0 28 28 28 28 28

Type: new

Release V18.0

Description: Table of thresholds defining the maximum number of TCH allocation requests queued (public and WPS), according to their internal priority.

Value range: [List of 13 elements]: [0-63]

Object: bts


Default value: 0 0 0 0 0 0 0 0 5 5 5 5 5

Type: DP

Description: Index in the allocPriorityTable that defines the processing priority of TCH allocation requests with cause "other cases". This priority is used in primo-allocations or when an SDDCH cannot be allocated for overload reasons.


Object: bts

Default value: 17

Type: DP

411-9001-124 18.08 1.0 Page 47 of 446


amrAdaptationSet Class 3

amrDirectAllocIntRxLevDL Class 3

amrDirectAllocIntRxLevUL Class 3

Description: This attribute defines the lines of parameter used for theadaptation mechanism. This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’bts’ object instance in unlocked.

Value range: Int [0 to 3]

Object: bts

Default value: 0

Type: DP

Release: V14

Note: This parameter is available for all BSCs 3000 and applicable to versions earlier than V16.

Description: Downlink RxLev threshold for direct AMR TCH allocation in the inner zone.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’handOverControl’ object instance in unlocked.

Value range: Int [-110 to -47]

Object: handOverControl

Default value: -80 to -79 dB

Type: DP

Checks: 057CO01 - amrDirectAllocIntRxLevDL >= concentAlgoIntRxLev where concentAlgoIntRxLev is intRxLev in the ConcentAlgoData sequence of concentAlgoData attribute.

Release: V14

Note: This parameter is only available for BSC 3000.

Description: Uplink RxLev threshold for direct AMR TCH allocation in the inner zone.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’handOverControl’ object instance in unlocked.




Type: DP

Release: V14


Page 48 of 446 411-9001-124 18.08 1.0


amrDirectAllocRxLevDL Class 3

amrDirectAllocRxLevDL Class 3

amrDlFrAdaptationSet class 3

amrDlHrAdaptationSet class 3

Description: Downlink RxLev threshold for direct AMR TCH allocation.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’handOverControl’ object instance in unlocked.




Type: DP

Release: V14


Description: This attribute defines the downlink RxLev threshold for direct AMR TCH allocation.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’handOverControl’ object instance in unlocked.




Type: DP

Release: V14


Description: This attribute defines the lines of parameter used for the downlink AMR full rate adaptation mechanism.


Object: bts

Default value: 0

Type: DP

Feature: AMR Optimizations

Release: V15


Description: This attribute defines the lines of parameter used for the downlink AMR half rate adaptation mechanism.


Object: bts

411-9001-124 18.08 1.0 Page 49 of 446


amrFRIntercellCodecMode Class 3

amrFRIntracellCodecMode Class 3

amrHRIntercellCodecMode Class 3

Default value: 0

Type: DP


Release: V15


Description: Target codec mode to trigger an intercell quality handover from a RR channel.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’handOverControl’ object instance in unlocked.

Value range: [12.2 / 10.2 / 6.7 / 5.9 / 4.75]


Default value: 4.75

Type: DP

Release: V14


Description: Target codec mode to trigger an intracell quality handover FR to FR.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’handOverControl’ object instance in unlocked.

Value range: [12.2 / 10.2 / 6.7 / 5.9 / 4.75]


Default value: 4.75

Type: DP

Release: V14


Description: Target codec mode to trigger an intercell quality handover from an HR channel.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’handOverControl’ object instance in unlocked.

Value range: [7.4 / 6.7 / 5.9 / 4.75]


Default value: 4.75

Type: DP

Page 50 of 446 411-9001-124 18.08 1.0


amrHRToFRIntraCodecMode Class 3

amriRxLevDLH Class 3

amriRxLevULH Class 3

Release: V14


Description: Target codec mode to trigger an intracell quality handover from AMR HR to FR.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’handOverControl’ object instance in unlocked.

Value range: [7.4 / 6.7 / 5.9 / 4.75]


Default value: 6.7

Type: DP

Release: V14


Description: This attribute is the downlink RxLev threshold in case of AMR FR intracell handover.This attribute can only be modified if the ’handOverControl’ object instance in unlocked.

Value range: [-110 to -47]



Type: DP

Release: V14


Description: This attribute is the uplink RxLev threshold in case of AMR FR intracell handover.This attribute can only be modified if the ’handOverControl’ object instance in unlocked.

Value range: [-110 to -47]



Type: DP

Release: V14


411-9001-124 18.08 1.0 Page 51 of 446


amrReserved1

amrReserved2 Class 3

amrUlFrAdaptationSet class 3

Description: See information contained in the Attention paragraph below.



Default value: 0

Type: DP

Release: V16

Note1: This parameter is only available for BSC 3000.

Parameter range evolution for amrReserved 1 is as follows:• 0: RATSCCH procedure enabled (default value)• 1: RATSCCH procedure disabled - initial Full Rate ACS is optimistic• 2: RATSCCH procedure disabled - initial Full Rate ACS is pessimistic

Description: AMR L1m deactivation for:AMR FR intracell handover and AMR quality inter-cell handover and AMR power control mechanism.This parameter is available at the OMC-R level, managed by all NRPs, except the AMR activation NRP and this parameter is not managed by the CT2000 and the SDO.

Value range: [0 to 3]Deactivations for this parameter are:Value 0 (default): AMR L1m algorithms are used.Value 1: AMR FR intracell handover and AMR quality inter cell handover are deactivated, but the AMR power control is activated.Value 2: AMR FR intracell handover and AMR quality inter cell handover are activated, and the AMR power control is deactivated.Value 3: AMR FR intracell handover, AMr quality inter cell handover and the AMR power control are deactivated.


Type: DP

Release: V14

Note1: This parameter is only available for BSC 3000.

Description: This attribute defines the lines of parameter used for the uplink AMR full rate adaptation mechanism.


Object: bts

Type: DP

Default: 0


Release: V15

Note1: This parameter is optional.

Page 52 of 446 411-9001-124 18.08 1.0


amrUlHrAdaptationSet class 3

amrWbDlAdaptationSet class 3

amrWBPowerControlCIThresholdUl class 3

amrWbNbMaxPdtchPreemption class 2

Description: This attribute defines the lines of parameter used for the uplink AMR half rate adaptation mechanism.


Object: bts

Type: DP

Default: 0


Release: V15

Note1: This parameter is optional.

Description: This attribute defines the set of parameters used for the downlink Wide Band AMR adaptation mechanism.

Value range: [nominal, optimistic, pessimistic, operator]

Object: bts

Type: DP

Default: corresponding to nominal

Feature: Wide-band AMR support

Release: V18.0

Description: This attribute defines the set of parameters used for the downlink Wide Band AMR adaptation mechanism.

Value range: [corresponding to nominal, optimistic, pessimistic, operator]

Object: powerControl

Type: DP



Release: V18.0

Description: This parameter defines the maximum number of PDTCH AMR-WB capable allocated or not to the PCU and pre-emptable before using TCH non-AMR Wide Band capable..

Value range: [0...127]

Object: bts

Type:

Default: 0


Release: V18.0

411-9001-124 18.08 1.0 Page 53 of 446


amrWbSacchPowerOffsetSelection class 2

amrWbUlAdaptationSet class 3

amrWBIntercellCodecMThresh Class 3

amrWBIntracellCodecMThresh Class 3

Description: This parameter enables/disables the repeated FACCH feature on the AMR-WB channel and also specifies the threshold to reach before using the repeated downlink FACCH procedure.

Value range: [disable, AMR-WB FR 6.60 kbps, AMR-WB FR 8.85 and lower]

Object: bts

Type:

Default: disable


Release: V18.0

Description: This attribute defines the set of parameters used for the uplink Wide Band AMR adaptation mechanism.

Value range: [nominal, optimistic, pessimistic, operator]

Object: bts

Type: DP



Release: V18.0

Description: This parameter specifies the target codec mode to trigger an inter-cell AMR-WB quality handover.

Value range: [6K60, 8K85, 12K65]


Type:

Default: 8K85


Release: V18.0

Description: This parameter specifies the target codec mode to trigger an inter-cell AMR-WB quality handover.

Value range: [6K60, 8K85, 12K65]


Type:

Default: 8K85


Release: V18.0

Page 54 of 446 411-9001-124 18.08 1.0


amrWBiRxLevDLH Class 3

amrWBiRxLevULH Class 3

answerPagingPriority Class 3

architecture

Description: This parameter specifies the minimum downlink Rx level to trigger an intra-cell handover AMR-WB FR to FR.

Value range: [less than -110, -110 to -109, ..., -49 to -48, more than -48] dBm


Type: DP

Default: [-75....-74] dBm


Release: V18.0

Description: This parameter specifies the minimum uplink Rx level to trigger an intra-cell handover AMR-WB FR to FR.

Value range: [less than -110, -110 to -109, ..., -49 to -48, more than -48] dBm


Type: DP

Default: [-75....-74] dBm


Release: V18.0

Description: Index in the allocPriorityTable that defines the processing priority of TCH allocation requests with cause "reply to paging".This priority is used in signaling mode on TCH only.


Object: bts

Type: DP

Default: 17

Description: Architecture of the OMC-R agent in terms of servers. It is provided by the OMC-R agent.The standard configuration is "one active with one passive" and the basic configuration is "one active without passive".

Value range: [dual servers but passive not running dual servers running single server running]

Object: md - Display

Type: DP

Checks: • [M]: This attribute is not managed by users.

411-9001-124 18.08 1.0 Page 55 of 446


assignRequestPriority Class 3

associatedLog

associatedTMUPosition

aterLapd

Description: Index in the allocPriorityTable that defines the processing priority of TCH allocation requests with cause "immediate assignment".This priority is used when radio resource allocation queueing is not requested by the MSC or not authorized in the BSS (refer to the bscQueueingOption entry in the Dictionary).


Object: bts

Type: DP

Default value: 17

Description: Identifier of the log object that describes the associated records on the OMC-R agent disks.For an mdScanner object, this attribute is displayed provided mdLog = "logged".


Object: callPathTrace, mdScanner, traceControl - Display

Type: DI

Restrictions: • [C/M]: This attribute is not managed by users.

Description: Gives the number of the TMU hosting the active associated core process (hardware slot position).

Value range: [Shelf Number (0 or 1) and Slot Number (from 1 to 15) of the TMU]

Object: btsSiteManager, signallingLinkSet, transcoder and pcu

Feature: BSC 3000 cell group management/load balancing - stage 1(139111).

Type: DD

Default: None


Description: ATER LAPD repartition and status.

Value range: List of ATER LAPD descriptions [pcmAterId, tsAterId, lapdIsPresent, lapdIsOpened], with:pcmAterId: 0 to 65535tsAterId: 0 to 65535lapdIsPresent: yes / nolapdIsOpened: yes / no

Object: cemRc

Feature: Optical TCU High Capacity 4K

Page 56 of 446 411-9001-124 18.08 1.0


aterLapd

atmRm

atmRmId

attenuation Class 2

Type: DD

Release: V18.0

Description: ATER LAPD distribution and status.

Value range: List of ATER LAPD descriptions [pcmAterId, tsAterId, lapdIsPresent, lapdIsOpened], with:pcmAterId: 0 to 65535tsAterId: 0 to 65535lapdIsPresent: yes / nolapdIsOpened: yes / no

Object: lsaRc

Feature: BSC/TCU e3 GET DATA enhancement

Type: DD

Release: V16

Description: The ATM RM (ATM Resource Module), which provides a SONET OC-3c (Optical Carrier level 3c) interface to allow direct connection between the Interface Node and the Control Node.


Object: atmRm

Type: DP

Release: V13

Description: Identifier of the ’atmRm’ object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000.


Object: atmRm

Type: DP

Release: V13

Description: Attenuation due to coupling system losses. This value depends on the BTS configuration.

Value range: [0 to 14] dB

Object: btsSiteManager

Default value: Depends on the equipment.

411-9001-124 18.08 1.0 Page 57 of 446


auditBdaStatus

auditState

availabilityStatus

availabilityStatus

Type: DP

Release: V9

Note: If the attenuation parameter is set [0 to 14], then the DLU attenuation is replaced by the OMC attenuation parameter.

Description: Synthetic result of a BDA audit

Value range: [no difference / some differences (see list below) / many differences (see partial list below)]The information is stored in sessions logs.no difference ...... Object instances in BDA and BDE are identical. some differences ... Less than ten object instances are different in BDA and BDE (they are listed in the session logs). many differences .. More than ten object instances are different in BDA and BDE (the first ten are listed in the session logs).

Object: bsc

Type: DI

Description: Whether an audit is in-progress in the BSC. Access to a BSC are blocked whenever an audit of its application database is in-progress (Audit BDA command).This attribute is unknown to the BSC and cannot be directly modified by users.When an audit is in-progress in a BSC, all configuration commands involving the BSS are forbidden.

Value range: [inProgress / notInProgress]

Object: bsc

Type: DI

Description: List of the users authorized to copy, display and run the command file. Enter their names as defined in their profiles and use the "&" character to separate them.

Object: commandFile

Type: DP

Description: ISO stateRefer to the operationalState entries in the Dictionary for a description of possible state parameter combinations for these objects: administrativeState, availabilityStatus, operationalState.

Value range: [{} / {disabled} / {failed} ]

Page 58 of 446 411-9001-124 18.08 1.0


availabilityStatus

availabilityStatus

availabilityStatus

availabilityStatus

Object: bsc, bscMdInterface, pcmCircuit, signallingLink, transcoder

Type: DD

Description: ISO stateRefer to the operationalState entries in the Dictionary for a description of possible state parameter combinations for these objects: administrativeState, availabilityStatus, operationalState.

Value range: [{} / {disabled} / {failed} / {unknown}]

Object: btsSiteManager, transceiver, transceiverEquipment,

Type: DD

Note: If the administrativeState of the object is unlocked and the availabilityStatus is unknown, the object status is undetermined. You must request the status of the bsc object on the OMC-R, to update the network view.

Description: ISO stateThe "enabled" state for a bts object is a transitory state that follows a soft release request. Refer to the administrativeState entry related to the bts object in the Dictionary.

Value range: [{} / {dependency} / {failed} /{unknown}]

Object: bts

Type: DD

Note: If the administrativeState of the object is unlocked and the availabilityStatus is unknown, the object status is undetermined. You must request the status of the bsc object on the OMC-R, to update the network view.

Description: ISO state

Value range: [{notInstalled} / {} / {failed} / {dependency}]

Object: atmRM, cc, cem, controlNode, iem, interfaceNode, lsaRc, mms, omu, sw8kRm, tmu, trm, hsaRc, hsaRcTcu, iom

Type: DD


Value range: [notInstalled / Failed / onLine / degraded]

Object: igm


411-9001-124 18.08 1.0 Page 59 of 446


availabilityStatus

availabilityStatus

availabilityStatus

availabilityStatus

Type: DD

Release: V18.0

operationalState availabilityStatus Meaning

disabled notInstalled IGM not plugged

disabled failed software / hardware fault on IGM

enabled onLine IGM fully operational

enabled degraded IGM operational, but with fault on one or several following interfaces: Ethernet port (Abis, IBOS, Aggregation), optical fiber 0, optical fiber 1


Value range: [{degraded} / {} ]

Object: ipgRc


Type: DD

Release: V18.0


Value range: [{degraded} / {} ]

Object: ipgRc


Type: DD

Release: V18.0

Description: ISO stateThe "logFull" state applies to a log object that describes an observation or trace log, and indicates that the saving message directory on the OMC-R agent disks is full. Refer to the capacityAlarmThreshold entry in the Dictionary.

Value range: [{} / {logFull}]

Object: log

Type: DD


Value range: [{} (the associated observation is running) / {offDuty} (the associated observation has ended)]

Page 60 of 446 411-9001-124 18.08 1.0


availabilityStatus

availabilityStatus

availabilityStatus

available synchronization sources

Object: mdScanner

Type: DD

Description: ISO stateRefer to the operationalState entry in the Dictionary for a description of possible state parameter combinations: administrativeState, availabilityStatus, operationalState.

Value range: [{} / {dependency} / {failed}]

Object: pcu


Type: DD

Release: V12

Description: ISO stateRefer to the operationalState entry in the Dictionary for a description of possible state parameter combinations: administrativeState, availabilityStatus, operationalState.


Object: pcusn


Type: DD

Release: V12

Description: ISO stateRefer to the operationalState entry in the Dictionary for a description of possible state parameter combinations:administrativeState, availabilityStatus, operationalState, and usageState. A state change notification is issued after the soft release.


Object: xtp

Type: DD

Description: Available synchronization sources gives all the synchronization signals detected by the BTS, regardless of the BTS current synchronization mode and of the synchronization mode selected at the OMC.This parameter is used in response of the "Display Data Information" (normal) action.

Value range: [Abis synchronization only / Abis + external synchronization source coming from a master BTS / Abis + GPS connection detected]

411-9001-124 18.08 1.0 Page 61 of 446


averagingPeriod Class 2

2.3. B

backup manager addresses

backupServer

baseColourCode Class 3

Object: bts

Type: BTS synchronization

Description: Number of SACCH multi-frames over which the interference levels are averaged. This averaging will be performed immediately before the transmission of the RESOURCE INDICATION message.This attribute, together with the "thresholdInterference" attribute, allows users to manage interferences in radio cells. Refer to this entry in the Dictionary.

Value range:[0 to 255] SACCH frame (1 unit = 480 ms on TCH, 470 ms on SDCCH)


Default value: 20

Type: DP

Description: Backup addresses of the OMC-R manager that receives the messages. They are provided by the manager.

Object: efd - Display

Type: DI


Description: Name of the backup OMC-R agent server if any. It is provided by the OMC-R agent.In a mono-server configuration with redundancy, this attribute is not filled in.


Type: DP

Description: Base station Color Code assigned to a neighbor cell. The (BCC, NCC) pair forms the cell BSIC.


Object: adjacentCellHandOver

Type: DP

Checks: • [M]: Each defined (baseColourCode, bCCHFrequency, networkCo-lourCode) combination is unique in the set including aserving cell and its neighbor cells.

Page 62 of 446 411-9001-124 18.08 1.0


baseColourCode Class 2

batteryRemoteControllerPresence Class 2

bCCHFrequency Class 3

Description: Base station Color Code assigned to a serving cell. It is broadcast on the cell SCH and is used to distinguish cells that share the same BCCH fre-quency.The (BCC, NCC) pair forms the cell BSIC. The information is broadcasted on the cell SCH. Several BCCs may be assigned to a same BTS. Hence, different codes can be allotted to cells that may have overlapping areas (adjacent cells).The Base Station Identity Code (BSIC) is a 6-bit code: bits 6-5-4 = NCC (PLMN color code), bits 3-2-1 = BCC (Base station color code). At cell level, the NCC bits can be used to increase BCC col-or possibilities when the NCC is not needed.


Object: bts

Type: DP

Checks: • [M]: Each defined (baseColourCode, bCCHFrequency, networkCo-lourCode) combination is unique in the set including a serving cell and its neighbor cells.

• [M]: Modification of bCCHFrequency, baseColourCode and networkColourCode is forbidden while interfer-ence matrix is running.

Description: Whether BRC (Battery Remote Controller) board is present or not.

Value range: [0, 1]• 0: Not present• 1: present


Default value: 0

Type: DP

Release: V15

Description: Radio frequency allocated to a neighbor cell BCCH in the network fre-quency band. The information is broadcast on the serving cell SACCH.

Value range: [1 to 124] (GSM 900 network),[955 to 1023] / [0 to 124] (GSM-R),[975 to 1023] / [0 to 124] (E-GSM),[512 to 885] (GSM 1800 network),[512 to 810] (GSM 1900 network),[128 to 251] (GSM 850 network),[955 / 974] for GSM-R,[975 / 1023] / [0] for GSM-R (EGSM BCCH),[1 / 55] for GSM-R (PGSM BCCH).

Note: The standardIndicator for GSM-R values is Rgsm.


Type: DP

411-9001-124 18.08 1.0 Page 63 of 446



Checks: • [M]: Each defined (baseColourCode, bCCHFrequency, networkCo-lourCode) combination is unique in the set including a serving cell and its neighbor cells.

• [M]: The bCCHFrequency value must be set according to the stan-dardIndicator attribute.

• [C/M]: For an adjacentCellHandOverKapsch object instance, the bCCHFrequency can take one of the following values:[1 to 124] (GSM 900 network), [512 to 885] (GSM 1800 network), [512 to 810] (GSM 1900 network), [0 to 124] or [975 to 1023] (E-GSM), [128 to 251] (GSM 850 network),[0 to 124] or [955 to 1023] (GSM-R).

• [C]: Cannot create a new instance of adjacentCellUTRAN if the number of different bCCHFre-quency parameters in adjacentCellHandOver object is equal to 32. The purpose of this check is to forbid UTRAN neighbour cell creation if 32 different BCCH frequencies are already declared for GSM neigh-bour cells.

• [C]: Cannot set the bCCHFrequency parameter on an adjacentCell-HandOver object to a 32nd different value in the subset of adjacent-CellHandOver instances belonging to the same upper bts if at least one instance of adjacentCellUTRAN is created. The purpose of this check is to forbid existence 32 different BCCH frequencies on the GSM neighbour cells under the same GSM cell if at least one UTRAN neighbour cell is declared.

• [M]: Modification of bCCHFrequency, baseColourCode and net-workColourCode is forbidden while interference matrix is running.

• [C]: Customer should not validate IM activation on a cell with 32 in-stances of adjacentCell (existing IM control) or with 31 instances of adjacentCell with 31 different values of bCCFFrequeny parameter if at least one instance of adjacentCellUTRAN is created. The purpose of this check is to warn customer on IM activation if at least one UTRAN neighbour cell is declared and the cell already has real neighboring cells with 31 different BCCH.

Description: Radio frequency used for selection and re-selection management.The information is broadcast on the serving cell BCCH.

Value range: [1 to 124] (GSM 900 network),[955 to 1023] / [0 to 124] (GSM-R),[975 to 1023] / [0 to 124] (E-GSM network),[512 to 885] (GSM 1800 network),[512 to 810] (GSM 1900 network),[128 to 251] (GSM 850 network),[955 / 974] for GSM-R,[975 / 1023] / [0] for GSM-R (EGSM BCCH),[1 / 55] for GSM-R (PGSM BCCH).


Object: adjacentCellReselection

Type: DP

Page 64 of 446 411-9001-124 18.08 1.0



bckgDLLayer3WindowSize Class 3

Checks: • [M]: The bCCHFrequency value must be set according to the stan-dardIndicator attribute.

Checks: • [C/M]: For an adjacentCellReselection object instance, the bCCHFre-quency can take one of the following values:

[1 to 124] (GSM 900 network),[512 to 885] (GSM 1800 network),[512 to 810] (GSM 1900 network),[0 to 124] or [975 to 1023] (E-GSM),[128 to 251] (GSM 850 network),[0 to 124] or [955 to 1023] for GSM-R.

Note: An adjacentCellReselection object can use the same BCCH as the serv-ing cell to which it is associated. This allows a mobile to immediately re-cover the cell on which it was "camping" after being switched off, then switched back on, and is especially useful in the selection process.

Description: Radio frequency allocated to a cell BCCH (Broadcast Control CHannel) in the network frequency band.The information is broadcast on the cell SACCH.The BCCH frequency is automatically assigned to the radio time slot carrying the cell BCCH when the cell is brought into service (absoluteR-FChannelNo attribute of the channel object describing the carrier TDMA frame TS0). It is broadcast to the radio time slot whenever modified.The BCCH is used by the BTS for broadcasting cell related system in-formation to MS, such as frequency band and list of frequency channels used, authorized services and access conditions, list of neighbor cells, and radio parameters (such as maximum transmission strength, mini-mum reception strength).

Value range: [1 to 124] (GSM 900 network),[955 to 1023] / [0 to 124] (GSM-R),[975 to 1023] / [0 to 124] (E-GSM network),[512 to 885] (GSM 1800 network),[512 to 810] (GSM 1900 network),[128 to 251] (GSM 850 network),[955 / 974] for GSM-R, if at least one of the cell allocation ERFCN is in the [955 / 974] range, the BCCH must be also included within this range.[975 / 1023] / [0] (GSM-R (EGSM BCCH)), [1 / 55] (GSM-R (PGSM BCCH)).


Object: bts

Type: DP

Checks: • [M]: The BCCH frequency is included in the cellAllocation list.

• [M]: Each defined (baseColourCode, bCCHFrequency, net-workColourCode) combination is unique in the set including a serving cell and its neighbor cells.

• [M]: For a dualband cell, the bCCHFrequency attribute must be in the primary band of sfrequencies.

Description: Anticipation window size to be used in the context of BTS background downloading. It is used by SPR for BTS Abis downloading.

Value range: [1..8]

Object: bsc

411-9001-124 18.08 1.0 Page 65 of 446


bdaNewBscState

Default value: 1

Feature: BSC 3000 support of BTS background downloading

Type: DP

Release: V16

Note: This parameter is mandatory. It is applicable to BSC 3000 only.

Description: Current bsc state related to the new BDA

Value range: [ready for on-line reset/running on-line reset / waiting for on-line build/waiting for software change/waiting for Bda change/running software change/running Bda chang/waiting for end of probative phase / { }]

Object: bsc

Type: DI

Remark: This attribute is modified by the OMC-R agent when processing "end of probative phase", "Activate New BDA", "On line reset BDA", or "On-line reset cancel" actions or receiving an unsolicited message sent by the BSC.This attribute is NULL { } as long as the BSC has not been connected to the OMC-R agent.

Note: For a V10 BSC, this attribute is always NULL { }.The different states are obtained according to the following:• "ready for on-line reset": This state is reached after the following oc-

currences:

– BSC complete restart

– "end of probative phase" or BDA "new" activation or reset on-linecancel succeeded

– partial or complete spontaneous BSC restart

– BSC operating command aborted

• "running on-line reset": BSC reset on-line is being executed

• "waiting for on-line build": BSC reset on-line has succeeded

• "waiting for software change": "BDA version" reset on-line has suc-ceeded

• "waiting for Bda change": "BDA edition" reset on line has succeeded

• "running software change": BSC Type 5 EFT activation is being ex-ecuted

• "running Bda change": BSC BDA "new" activation is being executed

• “waiting for end of probative phase": BSC Type 5 EFT activation has succeeded

Release: V11

Page 66 of 446 411-9001-124 18.08 1.0


bdaSelected

bdaState

bdaVersionBuild

Description: Current BSC Application Database (BDA)

Value range: [running / new]

Object: bsc

Type: DI

Remark: This attribute is modified by the MD-R when processing "On line reset BDA" actions or receiving a BSC spontaneous event.This attribute is set "running" at the bsc object instance creation. For a V10 BSC, this attribute is never modified and its value is "running".

Note: The different states are obtained according to the following:• "new": BSC upgrades with prototype BDA change

• "running": BSC upgrades without prototype BDA change

Release: V11

Description: Whether the BSC application database (BDA) is built. No transactions with a BSC can be implemented prior to building its application data-base.When a bsc object is created or following a user Off line reset BDA com-mand, the value of this attribute is "not built".This attribute is unknown to the BSC and cannot be directly modified by users. It is updated by the system after a user Build BDA command.

Value range: [built / not built / inconsistency]

Object: bsc

Type: DI

Release: V11

Description: Version number of the BSC application database for rebuilding purpos-es.When the BSC is initialized or following a user Off line reset BDA com-mand, the value of this attribute is "0" (BDA not built). The BSC then sends a "build database request" message, indicating that its database is defective and needs rebuilding.By issuing a Build BDA command, the user informs the OMC-R that the BSC database must be regenerated.


Object: bsc - Build BDA

Type: DP

Checks: • [A]: If the command follows a BSC architecture change, the new ar-chitecture complies with the information in the last "build database re-quest" message received from the BSC.

Release: V11

411-9001-124 18.08 1.0 Page 67 of 446


bdaVersionNumber

beacBatteryRemoteControllerPresence Class 2

beginning date

beginSearchTime

Description: Current version number of the BSC application database. "0" means that the BDA is not built.Once the user has built or rebuilt the BDA, this attribute is assigned the bdaVersionBuild value sent with the user build command.If the BDA is being regenerated following an On line reset BDA com-mand, this attribute gives the user the version number of the BDA cur-rently used by the BSC.


Object: bsc

Type: DD

Description: Whether the optional equipment Battery Remote Controller (BRC) is present or absent in S8000 outdoor or S8002.

Value range: [Present, Absent]


Type: DP

Release: V15

Description: To select call monitoring data recorded on that date and thereafter.Do not fill in if information produced from the start is displayed.

Value range: [mm/dd/yyyy hh:mm:ss]

Object: Call monitoring - Display SDO

Type: DP

Checks: • [A]: beginning date is on or before end date.

Description: Absolute time to start searching for the observation reportsto cumulate.Observation data accumulating starts with the information contained in the last observation message collected in the requested period of time. Refer to the partnered endSearchTime entry in the Dictionary.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).

Value range: [<date> , <time>]

Object: Display custom report

Type: DP

Checks: • [A]: beginSearchTime is after endSearchTime.

• [A]: The defined period is less than or equal to six hours.

Page 68 of 446 411-9001-124 18.08 1.0


beginSearchTime

beginSearchTime

beginSearchTime

Description: Absolute time to start searching for the observation report to edit default is the current date and time).The report displays the information contained in the last observation message generated in the requested period of time. Refer to the part-nered endSearchTime entry in the Dictionary.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Object: Display raw report

Type: DP


Note: If no permanent observation has been received within the specified pe-riod, a message is displayed.

Description: Absolute time to start searching for the available permanent observa-tions to list (default is the current date and time).The first listed report is the last observation report generated in the re-quested period of time. Refer to the partnered endSearchTime entry in the Dictionary.


Object: List available permanent observations

Type: DP


Description: Absolute time to start searching for the available permanent observa-tions to list (default is the current date and time).The first listed report is the last observation report generated in the re-quested period of time. Refer to the partnered endSearchTime entry in the Dictionary.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Object: List available temporary observations

Type: DP


411-9001-124 18.08 1.0 Page 69 of 446


beginSearchTime

bEPPeriod Class 3

biZonePowerOffset Class 3

Description: Absolute time to end searching for the observation messages to list (de-fault is twelve days before beginSearchTime).The last listed message is the first observation message generated in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Object: List observation messages

Type: DP


Description: When EDGE is activated in the cell, the field is present and indicates the BEP filter averaging period to the MS.

Value range: 0 to 15

Object: bts

Feature: EDGE traffic management (20231)

Default value: 0

Type: DP

Release: V15

Note: Values 11 to 15 are reserved in tge 3GPP specification and shall not be used. 10 is the recommended value.

Description: Power offset between the inner TRXs and the outer TRXs of the adja-centCellHandOver object of a dualband, dualcoupling, or concentric cell.Offset added in calculation formula to draw up the list of eligible cells for handover towards a dualband, dualcoupling, or concentric cell inner zone to take into account the difference of propagation models between the two bands of the cells and the difference of transmission power be-tween TRXs of the two zones due to either BTS configuration or cou-pling.

Value range: [-63 to 63] dB


Default value: If main band = 850MHz 3dBIf main band = 1900MHz -3 dB

Feature: Dualband cell management (TF875 - V12)

Type: DP

Release: V12

Note: This parameter is only available for S8000 or e-cell BTS DRX transceiv-er architecture.

Page 70 of 446 411-9001-124 18.08 1.0


biZonePowerOffset Class 3

bsc3GEqpt

bsc3GEqptId

bsc

Description: Power offset between inner and outer TRXs of the handOverControl ob-ject of a dualband, dualcoupling, or concentric cell.




Default value: If main band = 850MHz 3dBIf main band = 1900MHz -3 dB

Type: DP

Release: V12

Note: This parameter is only available for S8000 or e-cell BTS DRX transceiv-er architecture.• zoneTxPwrMaxReduction (inner zone)

Description: Identification and dynamic data describing the hardware configuration of a BSC 3000 (global point of view).


Object: bsc3GEqpt

Type: DP

Release: V13

Description: Identifier of the ’bsc3GEqpt’ object class. This identifier is allocated by the MD-R at object creation. The only value allocated by the MD-R is 0. This attribute cannot be modified. This attribute is relevant for BSC 3000.


Object: bsc3GEqpt

Type: DP

Release: V13

Description: Identifier of a bsc object on the OMC-R.The bsc reference is part of all BSS configuration object identifiers. In all MMI commands, a bsc object can be referenced by name (bsc-Name).When a bsc object is created and the referenced bscMdInterface object is unlocked, the system attempts to establish the BSS/OMC-R link con-nection.


Object: bsc

411-9001-124 18.08 1.0 Page 71 of 446


bsc

bsc equipment name

Type: Id

Checks: • [C]: The number of BSCs managed by an OMC-R is limited to max-BscPerNetwork (static configuration data).

• [C]: The referenced bscMdInterface object (bscMdInterfaceRef) is created.

• [D]: The BSC application database has been reset by an Off line reset BDA command (bdaState = "not built").

• [D]: No mdScanner, traceControl, or callPathTrace object refers to the bsc object (no observation or trace function is active in the BSC).

Description: Identifier or name of a bsc object on the OMC-R.It defines the parent bsc object.


Object: adjacentCellHandover, adjacentCellReselection, bts, btsSiteManager, channel, frequencyHoppingSystem, handOverControl, lapdLink, multi-ple site, pcmCircuit, powerControl, signallingLink, signallingLinkSet, sig-nallingPoint, software, transceiver, transceiverEquipment, transceiverZone, transcoder, xtp

Type: Id

Checks: • [C]: The bsc object is created.

Description: To select messages issued by a given type of BSC or TCU processor.Do not fill in if this criterion is not to be selected.

Value range: [ / slti / pcu element]

Object: Alarm and notification logs - Filter


Type: DP

Checks: "css7" identifies the BSC CCS7 boards; "signaling link" identifies the SS7 signaling links defined in the BSS and controlled by the CCS7 boards.

Page 72 of 446 411-9001-124 18.08 1.0


bscList

bsc model

Description: List of the BSCs simultaneously monitored for further data processing by the SDO machine. Fill in the list with BSC reference numbers or names, up to maxBscPerNetwork.Do the following to create the list:• To add a BSC, fill in the bscNumber field with the reference num-

ber of the BSC on the OMC-R and click Add.

• To remove one or more BSCs, select the lines that display their ref-erence numbers and click Remove.

When the list is complete, click the option matching the desired com-mand, as follows:• Start: ........... starts collecting call monitoring data in the selected

BSCs.

• Stop: ............ stops collecting call monitoring data in the selected BSCs.

• Transfer: ......... transfers the BSC selected data files to the OMC-R.

• Processing: ....... copies and processes the selected data files in the SDO machine. A set of resultant ASCII data files is produced, it is identified as the Level 1 set.

Value range: [ 1 to 255]

Object: Call monitoring - Commands (SDO)

Type: DP

Checks: • [A]: The number of BSCs in the list is limited to maxBscPerNetwork (static configuration data).

• [A]: Each BSC occurs once in the list.

Notes: • The user must make sure that the BSCs in the list are created on the OMC-R since no checks are performed by the system.

• Processing: The call monitoring data files are meant to exist in the "/MD/ftam/bsc" directory on the OMC-R agent disks. For each BSC in the list, all files saved in that directory whose name begins with "SDO_CM_BSCnnn" will be processed: "nnn" is the BSC reference number on the OMC-R (if bsc = 5, then nnn is read "005"). See Kapsch GSM BSS Fundamentals — Operating Principles (411-9001-007).

• The bscList needs not be defined when selecting the Query com-mand which displays the activity state of the Call monitoring function in all the BSCs connected to the OMC-R.

Description: To select messages issued by a given model of BSC.

Value range: bsc 3000Do not fill in if this criterion is not to be selected.


411-9001-124 18.08 1.0 Page 73 of 446


bscNumber

bscArchitecture Class 0

Type: DP

Checks: bsc30000 is the value that must be used for this parameter in case of a BSC 3000.

Description: Identifier [1 to 255] or name of a BSC to add to the bscList.Fill in this field and click Add to add the BSC to the list. Refer to the bscList entry in the Dictionary.

Object: Call monitoring - Commands (SDO)

Type: DP

Description: Architecture of the BSC

Value range: [bsc30000 / bsc30000 optical/bsc30000electrical_ip bsc30000OpticalHC/bsc3000optical_ip]

Object: bsc

Type: DP

Checks: • [C/M]: The maximum PCM number is set to 231 (E1) /308 (T1) at the OMC-R when the bscArchitecture parameter is set to bsc30000Optical.

• [C/M]: When bscArchitecture equals bsc30000optical, valid pcmCir-cuitIds are:

– [0, 104] for LsaRC E1

– [147, 272] for HsaRC E1

– [0, 139] for LsaRC T1

– [196, 363] for HsaRC T1

This semantic check checks the validity of the pcmCircuitId when bs-cArchitecture equals bsc30000 Optical.

• [C/M]: The maximum PCM number is set to 126 (E1) / 168 (T1) at the OMC-R when the bscArchitecture parameter is set to bsc30000electrical_ip.

[C/M]: When the bscArchitecture parameter equals bsc30000electrical_ip, valid pcmCircuitIds are:

– [0, 104] for LsaRC E1

– [273, 335] for IPG RC E1

– [0, 139] for LsaRC T1

– [364, 447] for IPG RC T1

This semantic check checks the validity of the pcmCircuitId when thebscArchitecture parameter equals bsc30000electrical_ip.

Page 74 of 446 411-9001-124 18.08 1.0


bscCapacityReduction Class 3

bscCounterList Class 3

• [C/M]: The maximum PCM number is set to 231 (E1) / 308 (T1) at the OMC-R when the bscArchitecture parameter is set to bsc30000optical_ip.

• [C/M]: When the bscArchitecture parameter equals bsc30000optical_ip, valid pcmCircuitIds are:

– [0, 41], [63,104] for LsaRC E1

– [147, 272] for HsaRC E1

– [273, 293] for IPG RC E1

– [0, 55], [84,139] for LsaRC T1

– [196, 363] for HsaRC T1

– [364, 391] for IPG RC T1

Description: This attribute allows to reduce the traffic on the BSC in order to protect the MSC against high traffic load.This attribute can only be modified if the ’bsc’ object instance is unlocked


Object: bsc, signallingPoint

Type: DP

Release: V14

Description: Gives the list of counters associated to an observation type.


Object: bscCounterList

Type: Id

Release: V18.0

Note: Every time the bscCounterList object is modified, it is necessary to up-date the form files in order to include added counters, to delete removed ones.

411-9001-124 18.08 1.0 Page 75 of 446


bscDateTime

bscGprsActivation Class 3

bscHighSwitchingCapacity Class 3

bscHighSwitchingCapacity Class 3

Description: Current BSC reference date and time.This attribute is set by a user Synchronize bsc clock command, which broadcasts the current OMC-R agent date and time to the concerned BSC.It is also updated by the OMC-R agent in the following conditions:• A user Set command on the md object is run, which changes its ex-

ternalTime attribute.

• The BSS/OMC-R link is established.

• The BSS/OMC-R link is reestablished after a breakdown.

• The statutory time is modified.

The OMC-R agent sends an alarm notification to the OMC-R manager when the time difference with a BSC drifts too much.

Value range: [<date>,<time>]

Object: bsc

Type: DD

Description: Flag used to activate the GPRS at BSC level.

Value range: [disabled / enabled]

Object: bsc


Default value: disabled

Type: DP

Release: V12

Description: This parameter on the BSC enables the DS512 feature.


Object: bsc

Feature: BSC 3000 switching increase capacity (24436)


Type: DP

Release: V15

Description: Whether frequency hopping reconfiguration is authorized in BTSs that use cavity coupling.When frequency reconfiguration is authorized, it allows to automatically reconfigure the hopping sequence whenever a frequency is lost or re-covered in the BTS.

Value range: [true / false]

Page 76 of 446 411-9001-124 18.08 1.0


bscIPFirstAdr Class 2

bscIPSecondAdr Class 2

bscList

Object: bsc

Feature: BSC 3000 switching increase capacity (24436)

Default value: true

Type: DP

Checks: • [M]: It can be "true" provided the btsHopReconfR estart of one of the related bts objects is also "true".

Release: V8

Description: Indicates the first BSC IP address used for a ’bscMdInterface’ object in-stance. IP address corresponds to the subscriber number on the network used.This attribute is modified by the Manager.Value changes are notified to the Manager.

Value range: [7 to 15] String

Object: bscMdInterface

Type: DP

Checks: • [C/M]: The IP address must not already be used in a first address for another bscMDInterface object instance.

• [C/M]: The IP address must not already be used in a second address for another bscMDInterface object instance.

Release: V13

Description: Indicates the second BSC IP address used for a ’bscMdInterface’ object instance. IP address corresponds to the subscriber number on the network used.This attribute is modified by the Manager.Value changes are notified to the Manager.



Type: DP

Checks: • [C/M]: The IP address must not already be used in a first address for another bscMDInterface object instance.

• [C/M]: The IP address must not already be used in a second address for another bscMDInterface object instance.

Release: V13

Description: This attribute indicates for which BSC(s) the units of software has been downloaded. This attribute is allocated by the MD-R at object creation. This attribute cannot be modified by the Manager. This attribute is up-dated by the MD-R when a "sWDownload" command is performed suc-cessfully.Value changes are notified to the Manager.


411-9001-124 18.08 1.0 Page 77 of 446


bscLog

bscLogId

bscMdInterface

bscMdInterfaceRef

Object: executableSoftware

Type: DP

Release: V13

Description: bscLog modelizes the management of the BSC internal log files.

Value range: [bscVers13 +Inf]

Object: bscLog

Type: DP

Release: V13

Description: Identifier of the ’bscLog’ object class.This identifier is allocated by the MD-R at object creation.This attribute cannot be modified. This attribute is relevant for BSC 3000.

Value range: [bscVers13 +Inf]

Object: bscLog

Type: DP

Release: V13

Description: Identifier of a bscMdInterface object defined with regard to the md ob-ject.



Type: Id

Checks: • [D]: No bsc object refers to the bscMdInterface object.

Description: Identifier of the bscMdInterface object that describes the BSS/OMC-R link involving the BSC.


Object: bsc

Type: DP

Checks: • [D]: No bsc object refers to the bscMdInterface object.

Restrictions: • [M]: This attribute cannot be modified.

Page 78 of 446 411-9001-124 18.08 1.0


bscMdInterfaceVersionNumber

bscLogId

bscName

Description: Release number of the BSC/OMC-R interface. It is provided bythe BSC when the BSS/OMC-R link is physically established.If the release number does not match the software version running in the BSC (sWVersionRunning attribute of the related software object), the BSC issues a start-of-fault message.


Object: bsc - Display

Type: DI

Restrictions: • [[C/M]: This attribute is not managed by users.

Description: Enables or disables dynamic barring of access class at the bsc level.

Value range: [enabled / disabled]

Object: bsc


Type: DP

Release: V9

Description: Reference name of a bsc object on the OMC-R.It begins with a letter and is case sensitive.

Value range: [30 characters max.]

Object: bsc

Type: DP

Checks: • [C/M]: The name of a BSC is unique to the OMC-R.

Release: V13

Note: Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (such as TRX, BSC, BTS, BTSSM). All other symbols/characters are prohibited.The valid symbols are:• letter characters: A, B, C..., Z, a, b, c..., z

• digit symbols: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

• minus sign: -

• undescore: _

• space

411-9001-124 18.08 1.0 Page 79 of 446


bscPcuPcmRefList Class 2

bscQueueingOption Class 1

bscRefList

Description: List of BSC-PCU PcmCircuit.

Value range: BSC 3000 V16, E1 PCM: [1 to 32] values in the range [0..167]BSC 3000 V16, T1 PCM: [1 to 36] values in the range [0..167]BSC 3000 V17: [1 to 54] values in the range [0..167]BSC 3000 optical V17: T1 [1..54] values in range [0..363]; E1[1..54] values in range [0..272]

Object: pcu

Feature: 18749 (PCUSN - more than 12 Agprs PCMs per BSC), (step 1: up to one full PCUSN shelf per BSC).


Type: DP

Checks: • [C/M]: All the referred pcmCircuit object instances of this attribute must exist.

• [C/M]: The referred pcmCircuit object instances must be of pcmAgprs type (pcmType attribute).

• [C/M]: The referred pcmCircuit object instances must not be already referred to another pcu object instance on the same BSC.

Release: V12

Description: Whether radio resource allocation requests are queued in the BSC when no resources are available.If no resource is available when an allocation request is received and queueing is not allowed, the allocation request is refused immediately.

Value range: [allowed (MSC driven) / forced (O&M driven) / not allowed]• allowed .......... Resource allocation request queueing depends on

the type of operation and indicative items provided with the messages received from the MSC.

• forced ........... Resource allocation request queueing depends on the type of operation only.

• not allowed ....... Resource allocation request queueing is forbidden.

Object: signallingPoint

Default value: forced

Type: DP

Note: Allocation requests for immediate assignments and inter-bss, intra-bss, and inter-bts handovers are never queued. Only TCH resource re-quests (assignments request and intraCell handover) are queued de-pending on the priority of the demand and the number of request present in the queue.

Description: List of the bsc objects managed by a pcuSN object.

Value range: V16, E1/T1 PCM: [0 to 18] values in the range [1 to 255] The BSS sys-tem does not take into account the value range [17 to 18] for an E1 con-figuration. V17: [0 to 27] values in the range [1 to 255]

Page 80 of 446 411-9001-124 18.08 1.0


bscReset

bscSitePcmList Class 2

Object: pcusn


Type: DP

Release: V12

Description: Requests a control node reset.


Object: bsc3GEqpt

Type: DP

Release: V13

Description: List of the PCM links allotted to a site on the Abis interface, up to max-PcmCPerBtsSM. Each link is identified by a (pcmCircuitBsc, pcmCir-cuitBtsSiteManager) pair that defines it on BSC end and BTS end.The following rule is applied:• A PCM link connected to DDTI board no.i in the BSC has a pcmCir-

cuitBsc reference equal to "2i" or "2i+1" with regard to the BSC (each board manages two links at a time). Refer to Kapsch GSM BSC Ref-erence Manual.

• The same PCM link connected to DTI board no.j in the BTS has a pcmCircuitBtsSiteManager reference equal to "j" with regard to the BTS (each board manages one single link). Refer to Kapsch GSM BTS Reference Manuals.

The number of pairs in the list sets the number of links allotted to the ra-dio site.

Value range: list (1..6) of (pcmCircuitBsc, pcmCircuitBtsSiteManager) pairs.Refer to pcmCircuitBsc and pcmCircuitBtsSiteManager entries for more information on their value ranges.


Type: DP

Checks: • [C]: The number of PCM links allotted to a site is limited to maxPc-mCPerBtsSM (static configuration data).

• [C/M]: The list contains at least one pair, two if the btsSiteManager object redundantPcmPresence attribute is "true".

• [C/M]: Each pair is unique in the list.

• [C/M]: Each pcmCircuitBsc reference matches a pcmCircuit object created for the parent bsc object and assigned to the Abis interface (pcmType = "pcmAbis").

• [M]: If a pcmCircuitBsc reference is changed, the current link is not used by any dependent transceiverEquipment object.

411-9001-124 18.08 1.0 Page 81 of 446


bscTimeSlot

bscUsedAdr

bsCvMax Class 3

bsPowerControl Class 3

Description: PCM link (pcmCircuitId) and timeslot (timeSlotNumber) used by the ra-dio timeslot on the Abis interface. The PCM link is identified on BSC end [0 to 47].The information is displayed provided that the parent transceiver object is working. Refer to the operationalState entry for this object in the Dic-tionary.

Value range: pcmCircuitId [0 to 47] timeSlotNumber [1 to 31 (E1 PCM) or 24 (T1 PCM)]

Object: channel

Type: DD

Description: BSC address actually used. This attribute is managed by the MD-R. Val-ue changes are not notified to the Manager.

Value range: [comNotEstablished / ipFirstUsed / ipSecondUsed]


Type: DP

Release: V13

Description: Number of packets left to transmit divided by the number of UL TS allo-cated to the MS.


Object: bts


Default value: 1

Type: DP

Remark: bsCvMax is broadcasted in the system information.

Release: V13

Description: Whether BTS transmission power control is allowed at cell level.




Type: DP

Page 82 of 446 411-9001-124 18.08 1.0


bssMapT1 Class 1

bssMapT4 Class 1

bssMapT7 Class 1

bssMapT8 Class 1

Description: A interface timer triggered by the BSC in the BSSMAP management procedure.It is started on transmission of BLOCK or UNBLOCK by the,BSC and canceled on receipt of BLOCK ACKNOWLEDGE or UNBLOCK AC-KNOWLEDGE sent by the MSC.


Object: bsc

Default value: 5

Type: DP

Description: A interface timer triggered by the BSC in the BSSMAP management procedure.It is started on transmission of RESET and canceled on receipt of RE-SET ACKNOWLEDGE sent by the MSC. On elapse, the BSC sends RESET.


Object: bsc

Default value: 60

Type: DP

Description: A interface timer triggered by the BSC in the BSSMAP management procedure.It is started on transmission of HANDOVER REQUIRED and canceled on receipt of HANDOVER COMMAND, RESET, RESET CIRCUIT, CLEAR COMMAND or HANDOVER REQUIRED REJECT.


Object: bsc

Default value: 7

Type: DP

Description: A interface timer triggered by the BSC in the BSSMAP management pro-cedure. It is greater than t3103 for all BTS object instances attached to the BSC.It is started on transmission of HANDOVER COMMAND andcanceled on receipt of CLEAR COMMAND sent by the MSC or HANDO-VER FAILURE sent by MS.


Object: bsc

Default value: 15

Checks: • [C/M]: bssMapT8 > t3103 for all BTS objects dependent on the BSC object.

411-9001-124 18.08 1.0 Page 83 of 446


bssMapT7 Class 1

bssMapT12 Class 1

bssMapT13 Class 1

bssMapT19 Class 1

Description: A interface timer triggered by the BSC in the BSSMAP management pro-cedure.It is started on transmission of HANDOVER REQUIRED and canceled on receipt of HANDOVER COMMAND, RESET, RESET CIRCUIT, CLEAR COMMAND or HANDOVER REQUIRED REJECT.


Object: bsc

Default value: 7

Type: DP

Description: A interface timer triggered by the BSC in the BSSMAP management procedure. This timer is used with a Phase I MSC only.It is started on transmission of RESET CIRCUIT by the BSC and can-celed on receipt of RESET CIRCUIT ACKNOWLEDGE sent by the MSC.


Object: bsc

Default value: 5

Type: DP

Description: A interface timer triggered by the BSC in the BSSMAP management procedure.It is started on receipt of RESET sent by the MSC. On elapse, the BSC sends RESET ACKNOWLEDGE to the MSC.


Object: bsc

Default value: 32

Type: DP

Description: A interface timer triggered by the BSC in the BSSMAP management pro-cedure. This timer is used with a Phase II MSC only.It is started on transmission of RESET CIRCUIT by the BSC and can-celed on receipt of RESET CIRCUIT ACKNOWLEDGE sent by the MSC.


Object: bsc

Default value: 32

Type: DP

Release: V8

Page 84 of 446 411-9001-124 18.08 1.0


bssMapT20 Class 1

bssMapTchoke Class 1

bssPagingCoordination

bssSccpConnEst Class 1

Description: A interface timer triggered by the BSC in the BSSMAP management procedure.It is started on transmission of CIRCUIT GROUP BLOCK or CIRCUIT GROUP UNBLOCK by the BSC and canceled on receipt of CIRCUIT GROUP BLOCK ACKNOWLEDGE or CIRCUIT GROUP UNBLOCK ACKNOWLEDGE sent by the MSC.


Object: bsc

Default value: 32

Type: DP

Release: V8

Description: A interface timer triggered by the BSC in the handover management procedure.It is started by the BSC when the last neighbor cell in the list is rejected. On timer elapse, the BSC asks the MSC to provide a new list of eligible cells.

Value range: [1 to255] seconds

Object: bsc

Default value: 4

Type: DP

Description: Enable BSS Cs paging coordination

Value range: disabled/enabled

Object: bts

Default value: 0 (recommended)

Type: DP

Description: A interface timer triggered by the BSC in the handover management procedure.It is set on transmission of CONNECTION REQUEST and canceled on receipt of CONNECTION CONFIRM or CONNECTION REFUSED.

Value range: [5 to 360, by steps of 5] seconds

Object: signallingLinkSet

Default value: 5

Type: DP

Checks: • [C/M]: bssSccpConnEst parameters must have the same values for both A and Lb signallingLinkSet instances.

411-9001-124 18.08 1.0 Page 85 of 446


bssSccpInactRx Class 1

bssSccpInactTx Class 1

bssSccpRelease Class 1

bssSccpSubSysTest Class 1

Description: A interface timer T(iar) triggered by the BSC in the SCCP inactivity de-tection procedure.It is set either on transmission or receipt of CONNECTION CONFIRM or on receipt of any other message during the connection and canceled on receipt of any message.

Value range: [2 to 30] minutes


Default value: 11

Type: DP

Checks: • [C/M]: bssSccpInactRx parameters must have the same values for both A and Lb signallingLinkSet instances.

Description: A interface timer T(ias) triggered by the BSC in the SCCP inactivity de-tection procedure.It is set either on transmission or receipt of CONNECTION CONFIRM or on transmission of any other message during the connection and canceled on transmission of any message.



Default value: 11

Type: DP

Checks: • [C/M]: bssSccpInactTx parameters must have the same values for both A and Lb signallingLinkSet instances.

Description: A interface timer T(rel) triggered by the BSC in the SCCP management procedure.It is set on transmission of RELEASE and canceled on receipt of RE-LEASED COMPLETE or RELEASED.



Default value: 10

Type: DP

Checks: • [C/M]: bssSccpRelease parameters must have the same values for both A and Lb signallingLinkSet instances.

Description: A interface timer T(state info) triggered by the BSC in the SCCP man-agement procedure.It is set on transmission of SST and canceled on receipt of SSA.

Value range: [5 to 60, by steps of 5] seconds


Default value: 30

Page 86 of 446 411-9001-124 18.08 1.0


bsTxPwrMax Class 3

Type: DP

Checks: • [C/M]: bssSccpSubSysTest parameters must have the same values for both A and Lb signallingLinkSet instances.

Description: Maximum theoretical level of BTS transmission power in a cell.The BSC relays the information to the mobiles in the Abis CELL MODI-FY REQUEST message.• For concentric cells, dualband cells and dualcoupling cells:

The value of PwrReqSentToPowerAmplifier is equal to the value ofbsTxPwrMax added to the value of DLU attenuation (depending onthe coupling equipment type, that is for instance D, H2D, H4D) or At-tenuation on the btsSiteManager (if Attenuation has a value), and re-duced of the value of “Zone Tx power max reduction” of thetransceiverZone.

For PA: the value of PwrReqSentToPowerAmplifier must be between31dB and 44dBm. This value range is valid for Radio Module (RM).

For HePA: the value of PwrReqSentToPowerAmplifier must be be-tween 34dB and 47dBm. This value range is valid for High Power Ra-dio Module (HPRM).

For MePA: the value of PwrReqSentToPowerAmplifier between33dB and 46dB. This value range is valid for Medium Power RadioModule (MPRM).

• For mono zone cells:

The value of PwrReqSentToPowerAmplifier is equal to the value ofbsTxPwrMax added to the value of DLU attenuation (depending onthe coupling equipment type, that is for instance D, H2D, H4D) or At-tenuation on the btsSiteManager (if Attenuation has a value).


Object: The recommended value is 43 dB.

Default value: powerControl

Type: DP

Checks: • [M]: For a normal cell, the use of the block edge channels must induce a cell power limitation to 40 dB for PCS networks, and 42 dB for GSM 850 networks.

• [M]: For a concentric cell, the use of the block edge channels in the large zone and in the small zone must induce a cell power limitation to 40 dB for PCS networks and 42 dB for GSM 850 networks (’bsTx-PwrMax - zoneTxPwrMaxReduc’)

• [M]: For a dualband cell and, the use of the block edge channels in the large zone and in the small zone must induce a cell power limita-tion to 40 dB for PCS - GSM850 networks and 42 dB for GSM850 - PCS networks (’bsTxPwrMax - zoneTxPwrMaxReduc’)

411-9001-124 18.08 1.0 Page 87 of 446


bssSccpSubSysTest Class 1

• [M]: For a dualcoupling cell, the use of the block edge channels in the large zone and in the small zone must induce a cell power limitation to 40 dBm for PCS networks and 42 dBm for GSM850 networks (’bsTxPwrMax - zoneTxPwrMaxReduc - bizonePowerOffset’)

Note: Some bsTxPowerMax values are not compatible with the effective pow-er output by the BTS.bsTxPwrMax < 32 (dB)when an edge frequency is defined for the cell (i.e. if the value is includ-ed in the cellAllocation attribute values).The use of edge frequencies leads to a cell power reduction. The list of edge frequencies is described in the MD-R configuration file, MD/base/config/boundEdge.cfg.This file is can be configured off-line. To update the database according to the list of edge frequencies, use the shell /MD/install/shell/cm_configBde.sh.

Description: Identifier of a bts object defined with regard to a btsSiteManager object.All channel, transceiver, and transceiverEquipment objects in a BSS are identified with regard to a bts object that defines the covering cell.In all MMI commands, a bts object can be referred to by the sequence "siteName.cellName" where siteName and cellName identify the cover-ing site and the cell respectively by name.


Object: bts

Type: Id

Checks: • [C]: The number of cells managed by an OMC-R is limited to maxBt-sPerNetwork (static configuration data).

• [C]: The number of cells attached to a radio site is limited to maxN-bOfCells (attribute of the parent btsSiteManager object).

• [C]: The software object related to the parent btsSiteManager object is created.

• [C]: The mobileCountryCode and mobileNetwork Code attributes match those of the parent bsc object if they are defined for that object (cell CGIs must comply).

• [C/M]: The adjacent cell umbrella Ref attribute is defined if the cell is a microcell (cellType) and directed retry handovers are processed in BSC mode (directedRetryModeUsed).

• [C]: If the application database of the related BSC is built, the parent bsc object is unlocked and the parent btsSiteManager object is locked.

Page 88 of 446 411-9001-124 18.08 1.0


bts

bts equipment name

• [D]: If the application database of the related BSC is built, the parent bsc object is unlocked, the parent btsSiteManager object is locked, and the bts object is locked.

• [D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.

• [D]: No adjacentCellHandOver object refers to the bts object (the de-scribed cell is not used as a neighbor cell of another serving cell).

• [D]: No mdScanner object describing a temporary observation refers to the bts object (no observation is running on the described cell).

• [D]: No traceControl or callPathTrace object refers to the bts object (no tracing is running on the described cell).

Note: All cells covered by a given radio site must be created in numerical as-cending order and deleted in the reverse order.

Description: Identifier or name of a bts object.It defines the associated bts object.


Object: adjacentCellHandOver, adjacentCellReselection, channel, frequency-HoppingSystem, handOverControl, powerControl, software, transceiv-er, transceiverEquipment, transceiverZone.

Type: Id

Checks: • [C]: The bts object is created.

Description: To select messages issued by a given type of BTS equipment. Do not fill in if this criterion is not to be selected.

Value range: [[BTS main power / converterB/ converter C/ converterA/CSW1 / CSW2 / CSW1M/ TX / SYN / SYNO /ALAT / ALATO / DCC / DTI / RX splitter / TX splitter / antenna / column system RX / converter D / column system TX / door contact / fan system / RX fan / TX fan / cabinet fan / fans rack / MWT system / exchanger system / rectifiers groups / distribution sys-tem / fuses system / breakers / battery system / temperature system / smoke detector / CSWM/SYNC/ALCO/DSC/PCMI / GTW / PCM0 / PCM1 / rectifier 48V / converter F / converter BCF / battery disconnected switch /cooler system /LNA / VSWR / user system / distribution box / bat-tery cabinet / main breaker / diu / external alarm / VGA/ DLNA/MNU/DCU/RX/ DBF / AMNU / DCU4 / DRX / FPRX / Lightning Protection / BCF Cabinet door / BCF Cabinet fan / SBCF / PA / AC power supply / DC power supply / transmit antenna / cabinet high temperature alarm/ cabinet low temperature alarm

411-9001-124 18.08 1.0 Page 89 of 446


bts list

btsSMSynchroMode Class 2

/ EXTERNAL CONTACT ACCESS / drxmain reception chain / drx diver-sity reception chain / splitter output / high power module / splitter / low power RF module / rf supply module / CMCF / PCM / CPCMI / RECAL / rx splitterM / rx splitter D / combiner h4 lna / combiner h4 vswr / txFilter / combiner rx filter lna / combiner d vswr / rxMainConnector / rxDivCon-nector / dacsCooler / compact dacs cooler / compact distribution / PMNU / RDRX / PMOD / BTS synchronization / PSU / Heatsink / Preventive lightning protection / Battery / External Environment / SLTI / SALCO / not protected alarm / internal temperature / external temperature / Remote Tunable Cavity Combiner / Cavity /battery monitored / blower tray / S12000 rectifier / S12000 smoke detector / S12000 lightning protection / S12000 battery disconnected / S12000 cooler / Edge High PA / Edge DRX / Edge PA / CMCF phase 1 /CMCFphase2 /CMCFphase 3 /DRXND3/ ICM/ IFM/ABM / RM/ RM_PA / RM_TRX / HPRM / HPRM PA / HPRM TRX / MPRM/ MPRM_TRX / MPRM_PA / TRX MAIN RECEPTION CHAIN / TRX DIV RECEPTION CHAIN / DDM / DDM MAIN LNA / DDM DIV LNA / DDM 1 VSWR / DDM 2 VSWR /

DDM_H2 / DDM_H2 MAIN LNA / DDM_H2 DIV LNA / DDM_H2 1 VSWR / DDM_H2 2 VSWR / TX FILTER / TX FILTER VSWR / TX FILTER H2 / TX FILTER H2 VSWR / SICS / ECU / TRX / H4]


Type: DP

Description: List of the cells involved in broadcasting the short message. Enter the (bsc, btsSiteManager, bts ) reference of each bts object.

Object: short message - Start broadcast

Type: DP

Checks: • [A]: Each bts object in the list is created.

• [A]: Each bts object in the list is assigned a CBCH, that is there is one channel object in the set of transceiver objects dependent on the bts object whose channelType is "bcchSdcch4CBCH" or "sdcch8CBCH".

• [A]: No more than five short messages are being broadcast in the cells at that time.

Description: Type of site synchronization.


Value range: [normal / master / slave / gpsBurstSync, gpsTimeSync / masterGps-BurstSync / masterGpsTimeSync]

Type: DP

Feature: Network Synchronization

Default value: normal (synchronized on Abis link)

Checks: • [C/M]: slave, gpsBurstSync or gpsTime Sync values are allowed only if btsModel is S8000 CBCF, S12000, or BTS 18000.

Checks: • [C/M]: slave, gpsBurstSync or gpsTime Sync values are allowed only if btsModel is S8000 CBCF, S12000, BTS 6000 or BTS 18000.

• C/M]: master, masterGpsBurstSync or masterGpsTi meSync values are allowed only if btsModel is S8000 CBCF or S12000.

Page 90 of 446 411-9001-124 18.08 1.0


bts time between HO configuration Class 3

btsDescription

btsHopReconfRestart Class 2

btsIsHopping Class 2

Release: V15


Description: Whether the HOPingpongTimeRejection timer can be used at bts level when processing handovers.Refer to bts object btstimeBetweenHOConfiguration and adjacentCell-HandOver object hoPingpongTimeRejection attributes in this Dictionary of Parameters.

Value range: [0 / 1]

Object: bts

Feature: General protection against ping-pong handovers (TF821 - V12)

Default value: 0

Type: DP

Release: V9

Description: BTS configuration description (such as BTS type, configuration, cou-pling system) corresponding to the transcription of configRef attribute.

Value range: [chain of characters]


Type: DI

Release: V10

Note: It designates the maximum configuration of the configRef file loaded on one of the BTSs. But it does not necessarily corresponds to the config-uration of the btsSiteManager object concerned.

Description: Whether hopping frequency reconfiguration is authorized on TX restart in a cell.


Object: bts


Default value: true

Type: DP

Checks: • [C/M]: If the attribute value is "true", the bscHopReconfUse attribute of the parent bsc object is also "true".

Release: V8

Description: Whether frequency hopping is allowed in a cell.

Value range: [hopping / noHopping / hoppingWithCarrierFilling (V8) / noHopping-WithCarrierFilling (V8)]

Object: bts

411-9001-124 18.08 1.0 Page 91 of 446


btsMSAccessClassBarringFunction Class 3

btsReserved3 Class 3

Default value: Hopping

Type: DP

Checks: • [M]: If frequency hopping is allowed, the GSM "fhMgt" function is de-fined in the siteGsmFctList attribute of the parent btsSiteManager ob-ject.

• [M]: If it is disabled, no channel object dependent on the bts object is authorized to obey frequency hopping laws.

Note: The "xxxWithCarrierFilling" configuration means that the BTS covering the cell must use a TX for BCCH filling purposes. The following apply:• The BSC sends the information to the BTS in the Abis CELL CON-

FIGURATION REQUEST message.

• If the BTS does not have a redundant TRX/DRX, one of the operat-ing TRX/DRXs is assigned to that purpose and the partnered TDMA frame is unreachable (refer to the operationalState entry for the trans-ceiver object in the Dictionary).

• When this TRX/DRX is malfunctioning, the BTS re-configures the other TRX/DRXs. Users are then warned by the system, by means of a notification.

The "noHoppingWithCarrierFilling" configuration can be usedin all BTSs, regardless of the coupling mode. The following apply:• Hybrid coupling: All cell TX configurations provide BCCH filling.

• Cavity coupling: Only the TX that transmits the cell BCCH frequency is configured to provide BCCH filling.

The "hoppingWithCarrierFilling" configuration can only be used in BTSs that use cavity coupling. The following apply:• Hybrid coupling: The BTS refuses the configuration.

• Cavity coupling: All cell TX configurations provide self-frequency fill-ing.

Description: Enable or disable dynamic barring of access class at the bts level.


Object: bts


Type: DP

Release: V9

Description: Mean number of logical channels belonging to the large frequency reuse pattern and used at the same time for data communications.

Value range: [-16 to +16]

Object: bts

Feature: Automatic Cell Tiering (TF995 V12)

Default value: 0

Page 92 of 446 411-9001-124 18.08 1.0


btsReserved4 Class 3

btsSensitivity Class 3

btsSensitivityInnerZone Class 3

btsSiteManager

Type: DP

Release: V12

Description: Attribute reserved for future use.

Value range: [-32768 to 32767]

Object: bts

Type: DP

Release: V12

Description: Target power needed for BTS decoding. This parameter has an influ-ence on the power control efficiency.


Object: bts

Default value: 0


Type: DP

Release: V12

Note: The power control function used is the Open Loop Control.

Description: Minimum power needed for BTS decoding in the inner zone of a dual-band cell.


Object: bts


Default value: 0

Type: DP

Release: V12

Description: Identifier of a btsSiteManager object defined with regard to a bsc ob-ject.All bts, channel, transceiver, and transceiverEquipment objects in a BSS are identified with regard to a btsSiteManager object that defines the covering radio site.In all MMI commands, a btsSiteManager object can be referred to by name (siteName).



Type: DP

411-9001-124 18.08 1.0 Page 93 of 446


btsSiteManager

btsSiteManager model

Checks: • [C]:

• [C]: The software object related to the parent bsc object is created.

• [C]: The referenced lapdLink object (lapdLinkOMLRef) is created for the parent bsc object and assigned to the Abis interface.

• [C]: If the application database of the related BSC is built, the refer-enced pcmCircuit objects (bscSitePcmList) are created for the parent bsc object and assigned to the Abis interface (pcmType = "pc-mAbis").

• [C/M]: The bscSitePcmList list contains at least two pairs if the btsSiteManager object redundantPcmPresence attribute is "true".

• [C]: If one of the pcmCircuit objects in the list describes a PCM link that is shared with another site in the BSS, the radioSiteMask of the two btsSiteManager objects are dissociated.

• [C]: If the application database of the related BSC is built, the parent bsc object is unlocked.

• [D]: If the application database of the related BSC is built, the parent bsc object is unlocked and the btsSiteManager object is locked.


Description: Identifier or name of a btsSiteManager object. It defines the parent btsSiteManager object.It defines the parent btsSiteManager object. By definition, a radio site (btsSiteManager object) is related to a BSC, a radio cell (bts object) is related to a radio site, a TRX/DRX (transceiv-erEquipment object), a TDMA frame (transceiver object) and its radio time slots (channel objects) are related to a radio cell.In all MMI commands, the objects dependent on a btsSiteManager ob-ject can be identified at BSC or site level, whichever is the most conve-nient to users.


Object: adjacentCellHandOver, adjacentCellReselection, bts, channel, frequen-cyHoppingSystem, handOverControl, powerControl, software, trans-ceiver, transceiverEquipment, transceiverZone.

Type: Id

Release: The maximum number of sites supported by a BSC 3000 is 500. The system accepts values between 0 and 499 (inclusive).

Description: To select messages issued by a given model of BTS.Do not fill in if this criterion is not to be selected.

Value range: / s8000 inDoor / s8000 outDoor / s8000 inDoor CBCF / s8000 outDoor CBCF / e-CELL / s8002 outdoor CBCF O2 / s12000 inDoor / s12000 out-Door / BTS18000 inDoor / BTS18000 outDoor]

Page 94 of 446 411-9001-124 18.08 1.0


btsSiteManagerList Class 2

btsThresholdHopReconf Class 2

btsType Class 2


Type: DP

Description: List of btsSiteManager objects attached to a multiple site object


Object: multiple site

Type: DP

Checks: • [C/M]: Each btsSiteManager object is unique in the list and created for the parent bsc object.

• [M]: The parent bsc object is unlocked and the referenced btsSiteM-anager objects are locked.

Note: The order in which the btsSiteManager objects are entered in the list must match the BTS chaining order, beginning with the BTS closest to the BSC.

Description: Minimum number of frequencies working in a cell to allow frequency hopping reconfiguration.If this attribute defines the nominal number of cell frequencies, the re-configuration process is deactivated. Refer to the btsHopReconfRestart entry in the Dictionary.


Object: bts

Dedfault value: 1

Type: DP

Checks: • [M]: This number is less than or equal to the number of transceiver objects created for the bts object.

Release: V8

Description: Defines the type of the Abis interface used by the site: IP or TDM.

Value range: [TDM / IP]



Dedfault value: TDM

Type: DP

411-9001-124 18.08 1.0 Page 95 of 446


btsWithCavity Class 2

Checks: • [C/M]: When the btsType parameter equals IP, the btsSiteManager parameter can be unlocked only if the BTS is referenced by an IPM.

• [C/M]: When the btsType parameter equals TDM, the btsSiteMan-ager parameter can be unlocked only if the BTS is not referenced by an IPM.

• [C/M]: When the btsType parameter equals IP, the PCMs defined on the btsSiteManager object cannot be defined in the following ranges:

– [0, 104] for E1

– [0, 139] for T1

• [C/M]: When the btsType parameter equals TDM, the PCMs defined on the btsSiteManager object cannot be defined in the following rang-es:

– [273, 335] for E1

– [364, 447] for T1

• [C/M]: When the btsType parameter is set to IP or when a btsSiteM-anager object is created with he btsType parameter set to IP, the teiBtsSiteManager parameter must be equal to 0.

• [C/M]: When the btsType parameter is set to IP or when a btsSiteM-anager object is created with he btsType parameter set to IP, the ra-dioSiteMaskOffset parameter must be equal to 0.

• [C/M]: If a BTS is referenced to PCMs already used by another BTS, the OMC-R checks that the btsType parameter of both BTSs is the same.

If several PCMs are defined on the new BTS, a consistency with allthe BTSs using these PCMs must be done.

• [C/M]: A maximum of two IP BTSs (btsType parameter equal to IP) can be defined on the same IP PCM.

Description: Whether the bts object instance uses a transceiver equipment with cav-ity.


Object: bts

Dedfault value: false

Feature: Mixed hybrid and cavity combiner BTSs (PR1179 - V12)

Type: DP

Release: V12

Page 96 of 446 411-9001-124 18.08 1.0


buildState

2.4. C

callClearing Class 3

callDropActivation class 3

Description: Whether BSC application database building is in-progress. Commands on all objects related to the bsc concerned object are refused while the BDA is being built.When the bsc object is created, the value of this attribute is enforced to "notInProgress". It is unknown to the BSC and cannot be directly modi-fied by users.It is changed to "inProgress" by the system after a user Build BDA com-mand on the bsc object as long as database building is in-progress. It is then changed back to "notInProgress" when the operation is complete.

Value range: [inProgress / notInProgress]

Object: bsc

Type: DI

Description: Maximum distance between MS and BTS before a call is cleared.It is greater than msRangeMax.This distance defines the cell maximum coverage area.

Value range: [2 to 35] km (non-extended mode),[2 to 120] km (extended mode).

Object: bts

Default value: 35 in non-extended mode, 90 in extended mode

Type: DP

Checks: • [C/M]: callClearing > msRangeMax (attribute of the handOverCon-trol object associated with the bts object).

• [C/M]: The maximum distance is 35 km if the extended cell attribute of the bts object is "false".

• [C/M]: The maximum distance is 120 km if the extended cell attribute of the bts object is "true".

• 7 km for urban

• 35 km for rural

Description: Activation of cell call drop data retrieval of cell call drops at OMC-R.

Object: bts

Value range: [Disabled (0) / traffic drops (1) / signaling drops (2) / traffic + signaling drops (3)]

Type: DP

Feature: Call drop analysis

Default value: 0

411-9001-124 18.08 1.0 Page 97 of 446


callPathObservationArea Class 2

callPathTrace

Checks: • [C/M]: callDropActivation parameter cannot be set to a value different from 0 in more than 80 cells per BSC. Call drop analysis feature can-not be activated on more than 80 cells at a time

• [C/M]: Call drop analysis feature cannot be activated on the cell if interference matrix is still running on this cell. This semantic checks forbids activation of interference matrix and call drop analysis fea-tures at the same time on a cell.

Release: V15

Note: This parameter is mandatory.

Description: List of up to thirty-one same-type objects observed.Enter each object reference according to the type (bts, transceiverEquipment, xtp).

Value range: [list of objects belonging to the same class]

Object: callPathTrace

Type: DP

Checks: • [C/M]: All observed objects belong to the same class.• [M]: The callPathTrace object is locked.

Description: Identifier of a callPathTrace object defined with regard to the md object.This object describes the Call path tracing function of a BSS (follow-up of calls using one or more common resources in the BSS).A callPathTrace object is created in locked state. Unlock the object to start collecting trace data.



Type: Id

Checks: DP

Default value: • [C]: The callPathTrace object is not created for the md object.

• [C/M/D]: The application database of the related BSC is not being built.

• [C/M/D]: If the application database of the related BSC is built, the BSS/OMC-R link is established and no audit is running in the BSC.

• [D]: The callPathTrace object is created.

Release: V18.0

Page 98 of 446 411-9001-124 18.08 1.0


callPathTraceType Class 2

callReestablishment Class 3

callReestablishmentPriority Class 3

capacityAlarmThreshold

Description: Type of information stored by the BSC.The information stored with respect to the type is detailed in Kapsch GSM BSS Fundamentals — Operating Principles (411-9001-007).If the request cannot be fulfilled, the BSC attempts to store another type of information, using the following rule: radio >>> hand over >>> radio.

Value range: [basic / hand over / radio]


Type: DP

Checks: • [M]: The callPathTrace object is locked.

Description: Whether call re-establishment in a cell is allowed when the radio link is broken off for propagation reasons.The information is broadcast to the mobiles at regular intervals on the cell BCCH.On receipt of a CHANNEL REQUIRED message with cause "call re-establishment", the BSC attempts to allocate a TCH in one of the cells where call re-establishment is allowed. Then, if no TCH is available the BSC attempts to allocate a SDCCH.

Value range: [allowed / not allowed]

Object: bts

Default value: not allowed

Type: DP

Description: Index in the allocPriorityTable that defines the processing priority of TCH allocation requests with cause "call reestablishment".This priority is used in primo-allocations or when an SDDCH cannot be allocated for overload reasons.


Object: bts

Default value: 17

Type: DP

Description: Filling threshold of the message saving partition on the OMC-R agent disks, beyond which a notification is triggered.The size of the saving partitions is indicated in the system commissioning files.

This attribute is significant when the object describes a current log; it has no meaning when the object describes a restored log.

When the threshold is reached, the OMC-R agent initiates the following actions:

411-9001-124 18.08 1.0 Page 99 of 446


capacityTimeRejection Class 3

cause

cCCHGprsAtBtsLevel Class 3

• A notification is sent to the OMC-R manager.

• For a current alarm log, old messages are deleted to make room in the partition. If all saved messages are of today’s date, further notifi-cations are not saved and the operationalState of the log object is forced to "disabled".

• For a current observation or trace log, the operationalState of the log object is forced to "disabled" and its availabilityStatus is forced to "logFull".

Value range: [0 to 2147483646]. "2147483646" defines a 100% threshold (the parti-tion is full).


Type: DP

Note: The attributes of the log objects are not managed by users.

Description: Minimum time between one intracell HO and the next capacity intracell HO.This attribute can only be modified if the ’handOverControl’ object in-stance is unlocked.

Value range: Int [0 to 120] seconds


Default Value: 0

Type: DP

Release: V14


Description: To select messages according to one or more causes associated with a fault number. Refer to Kapsch GSM BSS and OMC Maintenance Manuals.This parameter is a component of the specific problems filter. Refer to this entry in the Dictionary.



Type: DP

Description: Used to activate the CCCH management at BTS level.


Object: bts


Type: DP

Release: V14

Page 100 of 446 411-9001-124 18.08 1.0


cc

ccId

cellAllocation Class 2

Description: The Communication application module Controller, which is the ATM switch implementing the ATM network used as the Control Node backplane. This board also provides ATM on OC-3 (Optical Carrier level 3) connectivity towards the Interface Node.


Object: cc

Type: DP

Release V13

Description: Identifier of the ’cc’ object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000.


Object: cc

Type: DP

Release V13

Description: List of no more than 64 frequencies allotted to a cell in the network frequency band. By definition, all cells covered by a given radio site use the same frequency band defined by the type of the network (standardIndicator). All cells declared as neighbor cells of a serving cell use the same frequency band as the serving cell.

Value range: [1 to 124] (GSM 900 network),[512 to 885] (GSM 1800 network),[512 to 810] (PCS 1900 network),[0 to 124 / 955 to 1023] (GSM-R network),[0 to 124 / 975 to 1023] (extended GSM network),[128 to 251] (GSM 850 network),[99 / 1023] / [0 / 55] (GSM-R network).


Object: bts

Type: DP

Checks: • [C/M]: Each frequency occurs once in the list and complies with the type of the network (refer to the standardIndicator entry in the Dic-tionary).

• [C/M]: GSM 900 / GSM-R / Extended GSM networks: The number of frequencies in the list is limited to 64.

• [C/M]: GSM 1800/1900/850 network: The number of frequencies in the list depends on the gap between the lowest and the greatest de-fined frequencies.

411-9001-124 18.08 1.0 Page 101 of 446


cellBarQualify Class 3

cellBarred Class 3

Maximum gap between frequencies Number of frequencies

between 257 and 512 [2 to 18]




• [C/M]: The cell BCCH frequency (bCCHFrequency) is part of the list.

• [C/M]: For dualband networks, the number of frequencies must be inferior or equal to 64 by frequency band.

• [M]: The frequencies allotted to the radio time slots (channel objects) of the set of TDMA frames related to the cell are part of the list.

• [C/M]: An element of the list of cellAllocation parameter can take one of the following values:

[1 to 124] (GSM 900 network),[512 to 885] (GSM 1800 network)[512 to 810] (GSM 1900),[0 to 124] or [955 to 1023] (GSM-R network),[0 to 124 or [975 to 1023] (E-GSM network)[128 to 251] (GSM 850 network).

Description: Cell selection priority used in the C2 algorithm in Phase II.The information is broadcast to the mobiles at regular intervals on the cell BCCH.

Value range: [true (low priority) / false (normal priority)]

Object: bts

Default Value: False

Type: DP

Release: V8

Description: IWhether direct cell access are barred to mobiles. The information is broadcast to the mobiles at regular intervals on the cell BCCH.During a call, it is transmitted on a signaling link. If the attribute value is changed to "barred", all in-progress calls can continue but the BSC will direct further mobile calls to another cell.

Value range: [barred / not barred]

Object: bts

Default Value: not barred

Type: DP

Remark: Even when cell access are barred to MSs, the cell may be indirectly accessible if incoming handovers are allowed (incomingHandOver attribute of the associated handOverControl object).

Page 102 of 446 411-9001-124 18.08 1.0


cellDeletionCount Class 3

cellDtxDownLink Class 3

cellIdentity Class 3


Description: Number of consecutive "Measurement Result" messages which, if not received from a given neighbor cell, will cause all previously stored information related to that cell to be deleted.From V12, this number corresponds to the number of missing measurement reports after which this neighbor cell is no more eligible. The measurements related to this neighbor cell are not deleted as far as less than 10 consecutive measurements are missing.


Object: bts

Default value: 5 in rural environment, 2 in microcell environment

Type: DP

Note: Any entered value superior than 10 is taken into account as 10 value.

Description: Whether the use of discontinuous transmission in BTS-to-MS direction is allowed in a cell.


Object: bts

Default value: enabled

Type: DP

Remark: The dtxMode attribute allows users to control the use of discontinuous transmission on the uplink. Refer to this entry in the Dictionary.

Description: Cell Identity code (CI) that identifying in a location area, a neighbor cell of the current cell.



Type: DP

Checks: • [C/M]: A CGI is unique in the set including a serving cell and its neigh-bor cells.

Description: Cell Identity code (CI) identifying in a location area, aneighbor cell of the current cell.



Type: DP


411-9001-124 18.08 1.0 Page 103 of 446



cellName

cellPagingState

Description: Cell Identity code (CI) identifying a serving cell in a location area.A CGI (Cell Global Identifier) is unique in a location area.It identifies a cell in the PLMN and includes four fields: cellIdentity (CI), locationAreaCode (LAC),mobileCountryCode (MCC), and mobileNetworkCode (MNC).


Object: bts

Type: DP

Checks: • [C/M]: A CGI is unique in the set including a serving cell and its neighbor cells.

Description: Reference name of a bts object on the coverage site. It is case sensitive.


Object: bts

Type: DP

Checks: • [C/M]: The name of a cell is unique to the covering radio site.

Note: Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (such as TRX, BSC, BTS, BTSSM). All other symbols/characters are prohibited.The valid symbols are:

– letter characters: A, B, C..., Z, a, b, c..., z

– digit symbols: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

– minus sign: -

– undescore: _

– space

Description: Processing mode of the paging requests in the cell.

Value range: [allowed / not allowed / not significant]This attribute is dynamically managed by the BSC.• allowed .......... The operationalState of the transceiver object de-

scribing the TDMA frame no.0 carrying the BCCH is "working" and SYS INFO 1, 2, 3, 4 have been acknowledged by the BTS.

• not allowed ....... The operationalState of thetransceiver object de-scribing the TDMA frame no.0 carrying the BCCH is "working" and SYS INFO 1, 2, 3, 4 have not been acknowledged by the BTS.If no message has been acknowledged by the BTS, the notification 1256 "Non response to SYS INFO 1, 2, 3, 4 or 2bis" is issued.

• not significant .... The operationalState of the transceiver object de-scribing the TDMA frame no.0 carrying the BCCH is not "working".

Page 104 of 446 411-9001-124 18.08 1.0


cellReselectHysteresis Class 3

cellReselectOffset Class 3

Object: bts

Type: DD

Description: Hysteresis to re-select towards a cell:when the MS is in GSM - IDLE mode and re-selects a cell with a different LA (Location Area) when the MS is in GMM stand by state and re-selects a cell with a different LA (Location Area) or a different RA (Routing Area)when the MS is in GMM ready state and re-selects a different cell A mobile can select a cell in another location area provided the re-selection parameter value of that cell oversteps the re-selection parameter values of all the cells in the same location area as the current camping cell by at least cellReselectHysteresis dB. The information is broadcast on the cell BCCH. The re-selection criterion (C1) formula is: C1 = (A - Max(B,0)) where A and B are as follows: A = average level of the received signal - rxLevAccessMinB = msTxPwrMaxCCH - Maximum RF output power of the MS. The re-selection criterion (C2) formula is given with thecellReselectOffset entry.

Value range: [[0 to 14, by steps of 2] dB

Object: bts

Default Value 6 dB

Type: DP

Note: The greater the value of cellReselectHysteresis, the later a new cell in another location area is selected. This prevents from switching back and forth two location areas.

Description: Encouragement to re-select a cell (C2 criterion) for phase2 MS.The re-selection criterion (C2) formula is:C2 = C1 + cellReselectOffset - temporaryOffset x H (penaltyTime - T)C1 is defined with the cellReselectHysteresis entry.T is a timer that is started when the cell is placed by the MS on the list of most suitable cells to receive the calls, and is stopped when the cell is no longer on the list.H(penaltyTime - T) equals 0 when penaltyTime < T and

penaltyTime T.In the case when penaltyTime = 640, re-selection criterion formula becomes:C2 = C1 - cellReselectOffset

Value range: [0 to 126, by steps of 2] dB

Object: bts

Feature: AR 264

Default value: 4

Type: DP

411-9001-124 18.08 1.0 Page 105 of 446


cellReselInd Class 3

cellThreshold Class 2

cellType Class 3

cellType Class 3

Release: V8

Note: The value given to this attribute allows to more or less encourage the mobiles to re-select the cell.

Description: Whether cell re-selection criterion (C2) use is authorized.

Value Range: [true / false]

Object: bts

Default Value: True

Type: DP

Release: V8

Description: Needed number of transceiver object instances that must be in enabled state so that the cell is working.The value of this attribute must be less than or equal to the number of TDMA frames created for this cell

This attribute can be modified only if the bts object instance is locked. This attribute can be modified only if the bsc object instance is unlocked.

Value range: [f1 to 16]

Object: bts

Default Value: 1

Type: DP

Description: Type of the adjacent cell.

Value range: [normalType / umbrellaType / microType]


Default Value normalType

Type: DP

Description: Type of the serving cell

Value range: [normalType / umbrellaType / microType]

Object: bts

Default Value normalType

Type: DP

Checks: • [C/M]: The adjacent cell umbrella Ref attribute is defined if the cell is a microcell (cellType) and directed retry handovers are processed in BSCmode (directedRetryModeUsed).

Page 106 of 446 411-9001-124 18.08 1.0


cemId

cemPcmList class 3

channel

Description: Identifier of the ’cem’ object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000.


Object: cem

Type: DP

Release V13

Description: List of the PCM links for the cemRc provided with the sub-parameters:• pcmInstance

• virtualPortNumber

Value range: [0 ... 335

Object: cemRc

Type: DP

Release: V18.0 P&C1

Note:

Description: Identifier of a channel object (radio time slot).In all MMI commands, a channel object can be referred to by the se-quence "siteName.cellName.transceiver.channel", where siteName and cellName respectively identify the covering site and cell by name.


Object: Channel

Type: Id

Checks: • [C]: The number of channel objects dependent on a transceiver object is limited to eight.

• [C/M]: If the channel object does not obey frequency hopping laws, the absoluteRFChannelNo is defined unless it carries the parent cell BCCH, and fhsRef and maio are undefined.

• [C/M]: If the channel object obeys frequency hopping laws, the abso-luteRFChannelNo is undefined, and fhsRef and maio are defined.

• [C/D]: If the application database of the related BSC is built, the par-ent bsc object is unlocked and the parent bts object is locked.


411-9001-124 18.08 1.0 Page 107 of 446


channel state

channelReleaseOnAbisFailure

Description: Type and resource state of the logical channels multiplexed on the radio time slot.

Value range: Type: [BCCH / RACH / PCH AGCH / SDCCH/4 / SDCCH/8 / TCH (full rate) / CCH],Resource state: [not created / disabled / working / free / busy / blocking / working, blocked / blocking, removing / disabled, blocked / free, blocked / removing / available / working not CBCH / disabled not CBCH / working CBCH / disabled CBCH]• available ........ The channel is allocated, not blocked, and free.

• busy ............ The channel is allocated, not blocked, and busy.

• disabled ......... The channel is not configured.

• working, blocked .. The channel is allocated and blocked.

• disabled, blocked.. The channel is not allocated and blocked.

Object: channel - Display channel state

Type: DD

Notes: • The types of logical channels that can be multiplexed on a radio time slot depend on its channelType. Refer to this entry in the Dictionary.

• The resource state of SDCCH no.2 is "disabled" if a CBCH is defined.

• A radio channel is blocked or released by means of a user Modify channel state command.

• A radio channel is allocated when the TDMA frame is configured (in the Abis way) and its radio time slots are mapped onto an Abis inter-face PCM link.

Description: Channel Release on Abis Failure feature is enabled or disabled.The Channel release policy feature is allowed on the BTS S8000 CBCF and BTS S12000.The feature is allowed for BTS model which contains the string:• “8000”

• ”12000”

except for BTS model: • ”BSS_btsModelS8000inDoor (CBCF)

• ”BSS_btsModelS8000outDoor (CBCF)


Object: bts

Feature: Channel release policy on BTS after Abis failure


Page 108 of 446 411-9001-124 18.08 1.0


channelType Class 2

Type: DP

Note: • The recommended value is disabled.

• This parameter is mandatory.

• [C/M]: A spare of the “TRX container” (IEITDMATranspAttr2 = 0x52) is used on bts object to activate the feature.

Spare 5 attribute ofTDMACONFIGCONTAINERofTDMA CONFIG message

8 7 6 5 4 3 1

IEI = TD_S PARE 5_IEI0 1 0 0 1 1 0

High part of spare 50 0 0 0 0 0 0

Low part of spare50 0 0 0 0 0/1 n/a

Default value = 0x0000

Bit 2 (from1 to 8) of the lowpart of spare 5 parameter can take the values:

0: Channel release policy after the ABIS failure is not activate d

1: Channel release policy after the ABIS failure is activated.

Description: Type of logical channel supported by a radio TS.

Value range: [tCHFull / sDCCH / mainBCCH / mainBCCHCombined / bcchsdcch4CBCH / sdcch8CBCH / cCH (V12) / pDTCH (V12)].An SDCCH is only allocated to a mobile during call setup. Once the call is established, the SDCCH is released and a TCH supports the call, serving traffic and signaling needs.A CBCH (Cell Broadcast CHannel) configuration enables use of the Short Message Service -Cell Broadcast (SMS-CB) in a cell when a radio time slot of a TDMA frame related to the cell supports that type of channel. The CBCH can be combined with an SDCCH/8 or a BCCH+SDCCH/4. It takes the place of SDCCH no.2 in all cases.If the time slot carries a cell BCCH, its type sets the cell BCCH configuration (combined or not combined).

Object: channel

Feature: Extended CCCH (TF184 - V12) GPRS (SV407 - V12)

Default value: None

Type: DP

411-9001-124 18.08 1.0 Page 109 of 446


Note: • [C/M]: If the type is "mainBCCH", "mainBCCHCombin ed", or "bcchSdcch4CBCH", the channel object identifier is [0] and the object is not authorized to hop.

• [C/M]: The type "cCH" can only be used if TS 0 carries a BCCH log-ical channel ("main BCCH", "main BCCH combined").

• [C/M]: The only allowed association of (BCCH + CCCH) timeslots are (0), (0, 2), (0, 2, 4), (0, 2, 4, 6).

• [C/M]: If the type is "sdcch8CBCH", the channel object identifier is in the range [0 to 3] if the covering cell works in normal mode, and it equals 0 or 2 if the cell works in extended mode (extended cell attri-bute of the parent bts object).

• [C/M]: If the type is "sdcch8CBCH", the noOfBlksForA ccessGrant attribute of the parent bts object has a value greater than 0.

• [C/M]: If the type is "bcchSdcch4CBCH" or "sdcch8CBCH", use of the SMS-CB service is authorized in the parent bts object (smsCB = "used").

• [C/M]: Concentric cell: If the parent transceiver object belongs to the cell inner zone, the only authorized types are "bcchSdcch4CBCH" and "sdcch8CBCH".

• [M]: The "pDTCH" channelType is only allowed from V12 BSCs for GPRS.

A radio channel is identified by an 8-bit code built up by the OMC-R from the channel type and the number of the time slot that supports it:

8 7 6 5 4 3 2 1

C5 C4 C3 C2 C1 < TN >

TN bits (bits 3 to 1) indicate the radio time slot number [0-7].C bits (bits 8 to 4) describe the type of the channel:

00001 ACCH with a TCH/FR (SACCH/FACCH)

0001T ACCH with a TCH/HR

001TT ACCH in an SDCCH/4 configuration

01TTT ACCH in an SDCCH/8 configuration

BCCH

10001 RACH (Uplink CCCH)

10010 PCH + AGCH (Downlink CCCH)

The T bits indicate the subchannel number [0 to 7]:

There are four subchannels [0 to 3] in an SDCCH/4 configuration:

00100 SDCCH/4 + ACCH subchannel no.0

00101 SDCCH/4 + ACCH subchannel no.1 (combined CBCH)



• There are four subchannels [0 to 3] in an SDCCH/4 configuration:


Page 110 of 446 411-9001-124 18.08 1.0


01001 SDCCH/8 + ACCH subchannel no.1 (CBCH)







The logical channels that can be multiplexed on a radio time slot depend on its channelType.They are described in the following table.

channelType Bits C5-C1

tCHFull BM + ACCH (SACCH/FACCH)

sDCCH SDCCH/8 + ACCH subchannels [0 to 7](SACCH/FACCH)

mainBCCH BCCHRACH (Uplink)PCH + AGCH (Downlink)

mainBCCHCom-bined

BCCHRACH (Uplink)PCH + AGCH (Downlink)SDCCH/4 + ACCH subchannels [0 to 3]

bcchSdcch4CBCH

BCCHCBCH (= SDCCH No2)RACH (Uplink)PCH + AGCH (Downlink)SDCCH/4 + ACCH subchannels [0 to 3]

sdcch8CBCH CBCH (= SDCCH No2)SDCCH/4 + ACCH subchannels [0 to 3](SACCH/FACCH)

cCH BCCHRACH (Uplink)PCH + AGCH (Downlink)

Remark:

Configuration of logical channels and broadcast of short messages are managed by two independent OMC-R functions.When a short message broadcast is started in a cell, the presence of a channel object with a CBCH dependent on the concerned bts object is checked. On the contrary, the SMS-CB function is not aware of changes made to that attribute.Consequently, withdrawing a CBCH from a cell configuration will implicitly stop any short message broadcast in the cell without the SMS-CB function knowing.

Note:

The following counters have been multiplexed on TSs 0, 2, 4, and 6 for the Extended CCCH feature: C1026, C1027, C1028, C1029, C1030, C1031, C1033, C1604, C1605.

Comments:No recommended value is specified since this parameter depends on the strategy of the operator.

411-9001-124 18.08 1.0 Page 111 of 446


chanState

chosenChannelAsscomp Class 1

chosenChannelCompL3Info Class 1

Description: Whether or not, the radio channel is blocked.


Object: channel - Set channel state

Type: DP

Checks: • [A]: A BCCH or a CBCH, whether combined or not, cannot be blocked.

• [A]: The parent btsSiteManager and bts objects are unlocked.

Notes: • When a CBCH is defined for a cell, it always uses SDCCH no.2.

• Run a Display channel state command to check that the channel has switched to the specified state. Refer to the channel state entry in the Dictionary.

Release: V11

Description: Whether the "Chosen channel" element is used in the ASSIGN COMPLETE messages (Phase II compliance).



Default value: False

Type: DP

Release: V8

Note: If the MSC parameter MULTIPLE_VOCODER_SUPPORT (Table OFCVAR) is set to ON (see 411-2231-455 for more details), then the BSC parameter chosenChannelAsscomp needs to be set to TRUE.

Description: Whether the "Chosen channel" element is used in the COMPLETE LAYER 3 INFORMATION messages (Phase II compliance).




Type: DP

Release: V8

Note: If the MSC parameter MULTIPLE_VOCODER_SUPPORT (Table OFCVAR) is set to ON (see 411-2231-455 for more details), then the BSC parameter chosenChannelCompL3Info needs to be set to TRUE.

Page 112 of 446 411-9001-124 18.08 1.0


chosenChannelHoPerf Class 1

chosenChannelHoReq Class 1

cic Class 0

Description: Whether the "Chosen channel" element is used in the HANDOVER PERFORMED messages (Phase II compliance).




Type: DP

Release: V8


Description: Whether the "Chosen channel" element is used in the HANDOVER REQUEST ACKNOWLEDGE messages(Phase II compliance).




Type: DP

Release: V8


Description: Circuit Identity Code = numbers of the PCM link and time slot used by a terrestrial circuit on the A interface, defined with regard to the MSC (cic = 32xmscPcmNumber + mscPcmTsNumber).The cic is coded into 16 bits, as follows:xxxxxxxxxxxnnnnn = (32xmscPcmNumber) + mscPcmTsNumber Bits x identify the PCM link involved in the BSC/MSC link with regard to the MSC (mscPcmNumber), bits n identify the time slot used on that PCM link with regard to the MSC (mscPcmTsNumber).


Object: xtp

Type: DP

411-9001-124 18.08 1.0 Page 113 of 446


cId Class 3

circuitGroupBlock Class 1

circuitGroupBlock Class 1

Checks: • [C]: A cic is unique to the parent bsc object.

• [C]: The PCM TS used by the terrestrial circuit on the A interface is identical on MSC end (mscPcmTsNumber component) and BSC end (timeSlotNumber), and is not allotted to another xtp or signallingLink object dependent on the parent bsc object.

• [C]: If PCM link no.3 is used on the A interface (pcmCircuitId), the TS number is in the range [1 to 27] if the PCM link is an E1 link and in the range [1 to 20] if the PCM link is a T1 link. Since the last four TSs on that link are not mapped on the Ater interface, they cannot be used. Refer to the transcoderMatrix entry in the Dictionary.


Description: cell identity of the UMTS neighbouring cell for HO


Object: adjacentCellUTRAN

Default value: 0

Type: DP

Release: V17

Checks: • [C] The set of attributes cId, rNCId, mobileCountryCodeUTRAN’ and mobileNetworkCodeUTRAN must be unique among all the instances of the objects adjacentCellUTRAN attached to the same bts.

Note: This parameter isonly available for BSC 3000.

Description: Whether the CIRCUIT GROUP BLOCK and CIRCUIT GROUP UNBLOCK messages are used (Phase II compliance).If these messages are unused, the BLOCK and UNBLOCK messages are used.

Feature: Unequipped circuit and circuit group block (UF1169.1 - V12)



Object: report template

Type: DP

Release: V8

Description: Whether the CIRCUIT GROUP BLOCK and CIRCUIT GROUP UNBLOCK messages are used (Phase II compliance).If these messages are unused, the BLOCK and UNBLOCK messages are used.



Page 114 of 446 411-9001-124 18.08 1.0


circularFileId

circularFileState

clear time

cleared by

Type: DP

Release: V8

Description: Identifier of a BSC circular file.BSC circular files are automatically created by the system: the FAULT files are created with the BSC, the PERF(observations) and TRACE (trace data) files are created when the BSC application database is built.

Value range: [majorFault / minorFault /observation (permanent andtemporary) / instrumentPanel]


Object: bscMdInterface - Circular file

Type: Id

Checks: [A]: The circular file is created.

Description: State of a circular file. When a circular file is closed, the spontaneous messages stored are not forwarded to the OMC-R agent.This attribute is set by the system following a user Close circular file or Open circular file command.When a circular file is closed, the messages are stored until the file is reopened. Some messages may be lost if the capacity of the file is reached.

Value range: [closed / opened]

Object: bscMdInterface - Display circular file state

Type: DP

Description: To select alarms cleared at that time.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in if this criterion is not to be selected.

Value range: [<date>,<time>]Object: Cleared alarm log - Filter

Type: DP

Description: To select alarms ceased by a given user. Enter the user’sname as defined in the user’s profile.Do not fill in if this criterion is not to be selected.

Object: Cleared alarm log - Filter

Type: DP

411-9001-124 18.08 1.0 Page 115 of 446


clearing cause

cn

control Node Id

coderPoolConfiguration Class 2

Description: To select alarms according to the cause of ceasing.Do not fill in if this criterion is not to be selected.

Value range: [user command / object enabled / object deleted / clear event received / automatic purge / cleared on low threshold crossing / circular file saturation]


Type: DP

Description: The Control Node, which provides the GSM protocol processing (CallProcessing, SS7 and LAPD), as well as BSS OA&M. A logical point of view and a sub-track(hardware) point of view are managed. The SIM modulesare also managed.


Object: controlNode

Type: DP

Description: Identifier of a ’controlNode’ object class. This identifier is allocated by the MD-R at object creation. The only value allocated by the MD-R is 0. This attribute cannot be modified. This attribute is relevant for BSC 3000.


Object: controlNode

Type: DP

Release: V13

Description: This attribute indicates enumerated speech coding algorithms supported by the TCU.

Value range: List of [coderAlgo, minimumCall, powerULI, powerDLI], with:coderAlgo: fullRatecoder / enhancedFullRateCoder / ctmEnhancedFullRateCoder / amrFullHalfRateCoder minimumCall: 1 to 65535 until V16 / 0 to 65535 for V17 and higher powerUL: -15 to +15powerDL: -15 to +15

Object: transcoder

Type: DP

Release: V13

Page 116 of 446 411-9001-124 18.08 1.0


coderPoolConfiguration Class 2

coderPoolList

Description: This attribute indicates enumerated speech coding algorithms supported by the TCU.

Value range: List of [coderAlgo, minimumCall, powerULI, powerDLI], with:coderAlgo: fullRatecoder / enhancedFullRateCoder / ctmEnhancedFullRateCoder / amrFullHalfRateCoder / amrWideBandFullRateCoder minimumCall: 1 to 65535 until V16 / 0 to 65535 for V17 and higherpowerUL: -15 to +15powerDL: -15 to +15

Object: transcoder

Type: DP

Release: V13

Checks: [C/M]: Checks are performed to determine the presence of a valid license for AMR-WB on the following operations:

• unlocking a transcoder

• building the BDA of a BSC

• resetting a BDA of a BSC

When there is a transcoder object with the coderPoolConfiguration parameter value set to "amrWideBandFullRateCoder", then no transcoder unlocking, no BDA build and no BDA reset is possible on the related BSC without a valid license.If the check fails, then the corresponding action is rejected and a clear error message displayed

Description: Current partitioning of the coder pool. This attribute is dynamically managed by the BSS. It is set to NULL at object creation. Value changes are not notified to the Manager. This attribute is relevant for TCU 3000.

Value range: list of [coderAlgo, archipelagoes, emptyArchipelago, maximumCall, currentCall, minimumCallsRespected] with:coderAlgo: fullRatecoder / enhancedFullRateCoder / ctmEnhancedFullRateCode / amrFullHalfRateCoder / amrWideBandFullRateCoder archipelagoes: 0 to 65535 emptyArchipelago: 0 to 65535maximumCall: 0 to 65535currentCall: 0 to 65535minimumCallsRespected: yes / no


Type: DD

Release: V13

411-9001-124 18.08 1.0 Page 117 of 446


codingScheme Class 2

command classes

command line

command number

Description: Channel coding scheme (CS) used for data in GPRS mode (UL and DL).

Value range: [cs1, cs2]

Object: transceiver


Default value: cs1

Type: DP

Release: V12

Note: cs1 is used for control blocks. Depending on the codingScheme parameter, cs1 or cs2 is used for data blocks in UL and DL.

Description: List of no more than twenty-five authorized command classes that define a user’s command domain. MMI commands grant access to OMC-R functions.Each class defines a subset of commands (one of them provides access to all MMI commands). The comprehensive list of MMI commands, together with their class(es), can be displayed using the Display command classes command.


Object: user profile

Type: DP

Description: Command associated with the job. Follow the Line mode syntax. If the job is meant to run a simple command, enter the sequence describing the command and its parameters.If the job is meant to run a command file, enter the following:Run-commandFile: object=(commandFile=/<directory>/<filename>);The command file must be created in the specified directory.The Line mode syntax is detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).

Value range: [case sensitive]

Object: job

Type: DP

Description: Serial number of the command to abort. It is assigned by the system and is registered in session logs.Every MMI command launched by the user is identified by a serial number assigned by the system. Open the user session log consultation window and search for that number.

Value range: [1 to infinity]

Page 118 of 446 411-9001-124 18.08 1.0


commandFile

comment

comment

comment

comment

Object: commandFile - Abort

Type: DP

Description: Identifier (name) of a command file in the saving directory. Enter the file name only.If the file exists in the selected directory, the user can either overwrite its contents with the commands newly recorded or append the new commands to the existing file (see Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130)).

Value range: [case sensitive, 14 characters max.]

Object: commandFile - Create file

Type: Id

Description: User-defined text

Value range: LString (0-510 symbols)


Default value: Empty string

Release: V18.0.0 P&C2

Description: User-defined text

Value range: LString (0-510 symbols)


Default value: Empty string

Type: P&C1

Description: Text comment.



Type: DP

Release V11

Description: Additional information coming with the short message. It is not broadcast.


411-9001-124 18.08 1.0 Page 119 of 446


comments

compressedModeUTRAN Class 3

computeSyntheticCounters

concentAlgoExtMsRange Class 3

Object: short message

Type: DP

Description: Additional information (such as creation date).

Object: software - Display markers

Type: DD

Description: Flag to indicate whether compressed mode UTRAN is supported

Value range: 0: disabled / 1: enabled

Object: bts

Default value: 0

Type: DP

Checks:

Release: V17


Description: Whether synthetic counters are included in the observation report.This parameter is significant only for permanent bsc and instrument panel observation report display requests.


Object: Display xxx report

Type: DP

Description: MS to BTS distance below which a handover is requested from the large zone to the small zone if the level criteria is verified.



Default value: 1 km

Condition: To define if the associated bts object describes a concentric, dualband or dualcoupling cell

Type: DP

Page 120 of 446 411-9001-124 18.08 1.0


concentAlgoExtRxLev Class 3

concentAlgoExtRxLevUL Class 3

Checks: • [C/M]: concentAlgoExtMsRange concentAlgoIntMsRange

• [C/M]: The maximum distance is 34 km if the extended cell attribute of the associated bts object is "false".

• [C/M]: The maximum distance is 120 km if the extended cell attri-bute of the bts object is "true".

Release: V9

Description: The level of the MS signal strength from below which a handover is requested from the large zone to the small zone.

Value range: [less than -110, -110 to -109,..., -49 to -48, more than -48] dB


Default value: - 95 to - 94


Type: DP

Checks: • [C/M]: concentAlgoExtRxLev > concentAlgoIntRxLev

Release: V9

Description: Uplink RxLev threshold above which an intra-cell handover from the large zone to the small zone is triggered.





Type: DP

Feature: Multi-zone cell enhancement

Release: V18.0

411-9001-124 18.08 1.0 Page 121 of 446


concentric cell Class 2

condition

Description: Whether the cell is monozone, concentric, dualband or dualcoupling:A concentric, dualband, or dualcoupling cell describes a combination of two transmission zones, the outer (or large) zone and the inner (or small) zone. The inner zone is entirely included in the outer zone.A dualband cell is a particular type of concentric cell for which GSM 900 and GSM1800 or GSM850 and GSM1900 TRXs/DRXs coexist and share the same BCCH.A dualcoupling cell is a particular type of concentric cell for which the TRXs/DRXs are combined with two types of combiners.For concentric configurations (concentric, dualband or dualcoupling), a TDMA frame belongs to one zone or the other, but never to both, and the frequencies used in each zone are separated.

Value range: [monozone / concentric / dualband / dualcoupling]

• monozone....... normal cell

• concentric....... two concentric transmission zones

• dualband......... two concentric transmissions zones with GSM 900 and GSM 1800 TRXs/DRXs for the one or GSM 850 GSM 1900 TRXs/DRXs for the other dualcoupling.. two concentric transmission zones with TRXs/DRXs combined with a one type of combiner for the one and with another type of combiner for the other

Object: bts


Default value: dualband

Type: DP

Note: Dualband cells are only available for S8000 DRX transceiver architecture.Dualcoupling cells are only available for BTSs equippedwith non mixed DCU4 or DRX transceiver architecture.

Release: V9

Description: Condition for calling the counting mechanism when a counter is involved.The following fields can be combined in the logical expression:

Parameter Notification type Operators

administrativeState state change

availabilityStatus state change =

bsc equipment name alarm =

bsc model alarm =

cause alarm =

btsSiteManager model alarm < = >

bts equipment name alarm =

Page 122 of 446 411-9001-124 18.08 1.0


configRef Class 3

equipment processor number alarm =

faultNumber alarm < = >

operationalState state change < = >

perceived severity alarm =

postMortem alarm =

usageState state change =

The "postMortem" field can take two values, either "before BSC restart" or "after bsc restart". They have the following meaning:before BSC restart means that the notification issued by the BSC was received by the OMC-R agent without the BSC having restarted (nominal conditions). after BSC restart means that the notification was issued by the BSC and the BSC was restarted before the OMC-R agent received the notification. These notifications do not trigger alarms.The following logical operators can be used in the logical expression:• & stands for the logical AND.

• | stands for the logical OR.

• ! stands for the logical NOT.

Value range: [logical expression]


Condition: To define if a Counter is associated with the criterion.

Type: DP

Description: Dual TDMA DLU references (QBx, KBx, MIx and NIx) shall not be selected without the corresponding RTUThe presence of valid license for Dual TDMA is checked on the following operations :• Unlock a TRX (Q3 object: transceiverEquipment)• Unlock a cell (Q3 object: bts)• Unlock a site (Q3 object btsSiteManager)• Unlock an entire site (Q3 objects: those in the btsSiteManager sub-tree) as this command is run via commands on the objects in the sub-tree• Build a BDA• Reset (on-line and off-line) a BDAThe attempt to activate the dual TDMA functionality is possible only when a valid license is available. When there is at least one btsSiteManager with a dual TDMA specific configRef, then no TRX, bts & btsSiteManager unlocking, no reset BDA build and no build BDA is possible without a valid license.

Value range: [1 to VVV]


Type: DP


411-9001-124 18.08 1.0 Page 123 of 446


configRefList

configurationType

counter list

Checks: There is a feature lock for dual TDMA configurations in V18.0, attention must be paid to get these licenses before upgrading to V18.0.

Note: If the attribute is nonzero, the user must check that the DLU configuration file exists on the concerned BSC disk, since no check is performed by the OMC-R.The configRef is an ASCII-coded integer in base 32 that allows to code the version of the DLU configuration file as seven characters (xxaYYYz).The btsDescription parameter gives the transcription of the configRef parameter.

Description: This attribute identifies the list of available configRef for a btsSiteManager delivery. For another object class instance, this attribute is empty. This attribute is allocated by the MD-R at object creation. This attribute cannot be modified by the Manager.



Type: DP

Release: V13

Description: Type of configuration the alarm criterion belongs to:The manufacturer configuration is known as the reference configuration. The operator configurations are known as the daytime configuration, the nighttime configuration, and the specific (or particular) configuration. Refer to the alarm criteria entry in the Dictionary.

Value range: [manufacturer / operator]


Type: DP

Checks: [M]: This attribute cannot be modified.

Description: Type of the counter list displayed.

Value range: [default / all]• "default": the default counter list

• "all": the whole counter list


Type: DP

Release: V12

Page 124 of 446 411-9001-124 18.08 1.0


connectedHsaOnPort0 Class 3

connectedHsaOnPort1 Class 3

counter list filename

counterId

counters

Description: defines if HSA 0 is connected or not connected to IPGRC.This parameter is used to synchronize BSC defence mechanisms (HSA 0, IPG) and to manage IPGRC optical link supervision on port 0.

Value range: 0, 255

Object: ipgRc

Default value 255

Recommended value:

Not applicable

Type: DP

Release: V18.0

Description: defines if HSA 1 is connected or not connected to IPGRC.This parameter is used to synchronize BSC defence mechanisms (HSA 1, IPG) and to manage IPGRC optical link supervision on port 1.

Value range: step 1, 255

Object: ipgRc

Default value 255

Recommended value:

Not applicable

Type: DP

Release: V18.0

Description: Full pathname of the counter list file.


Type: DP

Release: V11

Description: Q3 name of a permanent BSS observation counter. See Kapsch GSM BSS Fundamentals — Operating Principles (411-9001-007).

Value range: [50 characters max., case sensitive]

Object: mdWarning - detection function = "outOfRangeCounter"

Type: DP

Description: List of the Q3 names of the counters eligible for observation, which are in the counter list filename.


411-9001-124 18.08 1.0 Page 125 of 446


counters

cpueNumber Class 0 or Class 1 (see note)

cpueOccurrence

Type: DP

Release: V11

Description: List of counters (Q3 names) chosen for observation.


Value range: [list of Q3 counter names]

Type: DP

Release: V11

Description: Gives the number of the cell group to which the object will be mapped. Allows to by-pass the BSC algorithm which distributes the sites into Cell Groups.

Value range: [0 to 53 or empty]


Feature: CPU/BIFP load sharing (AR874 - V12)

Default value: 0

Type: DP

Checks: • [C]: The btsSiteManager object is limited according to the cpueNum-ber attribute value.

• [C]: The transceiverEquipment object instance number is limited ac-cording to the cpueNumber attribute value.

Notes: • Depending on the BSC type, cpueNumber class is:

• for a BSC 3000, to modify this parameter the bdaState must be "not built"

• This parameter only applies to type 3 to type 5 BSCs.

Release: V12

Description: Gives the number of the cell-group to which the site has been mapped at site creation. This mapping is not modifiable, except by deleting the site.



Type: DD

Default value: None

Page 126 of 446 411-9001-124 18.08 1.0


cRC Class 0

creator

criteriaEventType

cSS7LocalSubSystemNumber Class 0

cSS7RemoteSubSystemNumber Class 0

Description: Whether the CRC (Cyclic Redundancy Check) test on PCM links is used by the CTMx board controlling the PCM link, whether it is a pcmCircuit object dependent on a bsc object (Abis or Ater interface) for a BSC 3000 or dependent on a transcoder object (A interface) for a TCU 3000.

Value range: [used / not used]

Object: pcmCircuit

Default value: not used

Type: DP

Description: Report template creator name.



Type: DP

Release: V11

Description: Type of the notifications handled by the alarm criterion.Selecting "alarmNotification" includes all Q3 alarm notifications such as communicationAlarm, equipmentAlarm, environmentalAlarm, process-ingError-Alarm, and qualityOfServiceAlarm.Selecting "stateChangeNotification" includes all Q3 state change notifi-cations.

Value range: [alarmNotification / stateChangeNotification]


Type: DP

Description: SS7 local subsystem number for the BSSMAP application.



Type: DP

Release: V15

Note: • The recommended value is 254 (0x00FE).

• This parameter is only available for BSC 3000.

Description: SS7 remote subsystem number for the BSSMAP application.



411-9001-124 18.08 1.0 Page 127 of 446


CTU cable

current log size

current synchronization mode

currentChannelHorqd Class 1

Type: DP

Release: V15

Note: The recommended value is 254 (0x00FE).


Description: The CTU (cable transition unit) provides the physical interface to the customer’s spans in the BSC 3000 and the TCU 3000.

Value range: [true / false]True value: No break in the copper connection from the CTU to the IEM module of the LSA.False value: The cable is improperly installed from the CTU to the IEM module of the LSA or some break in the copper connection from the CTU and the IEM module of the LSA.

Object: lsaRc

Feature: AR 1209 - V13.1

Type: DD

Release: V13

Description: Current log size expressed in bytes.



Type: DP

Remark: The attributes of the log objects are not managed by users.

Description: Current synchronized mode gives the currentsynchronization mode of the BTS according to the synchronization mode received in the set ex-ternal contact message (if received) but regardless of the synchroniza-tion signals available.This parameter is used in response of the "Display Data Information" (normal) action.

Value range: [normal Abis synchronization / slave BTS correctly synchronized on master signal 1/ Abis synchronization due to master synchronization not available / slave BTS synchronized on master SY but master GSM time has been lost / Abis synchronization due to loss of master SY / hold over mode / Abis synchronization due to GPS synchronization unavailable or lack of accuracy / hold over mode due to a loss of GPS synchronization / hold over mode due to a GPS synchronization lack of accuracy / Net-work GPS Synchronized]

Object: bts

Feature: BTS synchronization

Description: Whether the "Current channel" element is used or not in the HANDO-VER REQUIRED messages (Phase II compliance).

Value range: [false / true]

Page 128 of 446 411-9001-124 18.08 1.0


cypherModeReject Class 1

2.5. D

dARPPh1Priority class 2

data non transparent mode Class 3


Default value: true

Type: DP

Release: V12





Type: DP


Release: V18.0

Description: Whether the CYPHER MODE REJECT messages are used (Phase II compliance).




Type: DP

Release: V8


Description: Specifies the priority of SAIC (Single Antenna Interference Cancellation) mobiles on the TDMA.

Object: transceiver

Value range: [high priority, low priority]

Unit: DP

Type: Network Synchronization

Default value: high priority

Release: V15


Description: Set of transmission rates used for data non transparent mode transmis-sion on the Radio interface (MS ↔ BTS) and Abis interface (BTS ↔ BSC).

Value range: [9.6 / 14.4] (kbit/s)

Object: bts

411-9001-124 18.08 1.0 Page 129 of 446


data non transparent mode Class 3

data transparent mode Class 3

data transparent mode Class 3

Unit: 9.6

Type: DP

Checks: • [C/M]: The only allowed configurations are the following:

• "9.6"

• "9.6" and "14.4"

Release: V11

Description: Set of transmission rates used for data non transparent mode transmis-sion on the Radio interface (MS ↔ BTS) and Abis interface (BTS ↔ BSC).

Value range: [9.6 / 14.4] (kbit/s)


Default value: 9.6 kbit/s

Type: DP


• "9.6"

• "9.6" and "14.4"

Release: V9

Description: Set of transmission rates used for data transparent mode transmission on the Radio interface (MS ↔ BTS) and Abis interface (BTS ↔ BSC).

Value range: ["1.2/0.075" / 0.6 / 1.2 / 2.4 / 4.8 / 9.6 / 14.4] (kbit/s)

Object: bts

Type: DP


• 1.2/0.075, 0.6, 1.2, 2.4, 4.8, and 9.6 (6 values)

• 1.2/0.075, 0.6, 1.2, 2.4, 4.8, 9.6, and 14.4 (7 values)

Release: V11

Description: Set of transmission rates used for data transparent mode transmission on the Radio interface (MS ↔ BTS) and Abis interface (BTS ↔ BSC).

Value range: ["1.2/0.075" / 0.6 / 1.2 / 2.4 / 4.8 / 9.6 / 14.4] (kbit/s)


Default value:

Type: DP

Page 130 of 446 411-9001-124 18.08 1.0


data14-4OnNoHoppingTs Class 3

dataOnNoHoppingTS

date


• 1.2/0.075, 0.6, 1.2, 2.4, 4.8, and 9.6 (6 values)

• 1.2/0.075, 0.6, 1.2, 2.4, 4.8, 9.6, and 14.4 (7 values)

Release: V9

Description: Whether data 14.4 kbit/s transmission rate is allowed at bts level on the non hopping TSs.


Object: bts


Type: DP

Release: V12

Description: This attribute enables/disables to establish a data call on non-hopping TDMA on a FR channel for the 2.4, 4.8, 9.6 data rates.


Object: bts

Class: 3


Type: DP

Release: V18 P&C 3

Note: The parameter “dataOnNoHoppingTS” has RTU semantic control on SET ([M]).

Description: Date on which data to archive were recorded.Date format entry forms are detailed in Kapsch GSM OMC-R Com-mands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).

Value range: [<date>]

Object: Display daily report

Type: DP

delivery

Description: Name of executable software package to download to the BSC disk.The name of the delivery identifies the type and version of the BSS soft-ware for which it is designed as follows:• BSC 3000 software format = "BSxabcdefghi"

411-9001-124 18.08 1.0 Page 131 of 446


Field Meaning Value

BSx Name x = [1.. 4]

ab Version [09..32]

cd Subversion Number [01..99]

ef Edition [01..99]

gh Patch Level [01..99]

i Revision Factor ‘C’

delivery

Description: • BSC 3000 software format = "B3Gabcdefghi"

• TCU 3000 software format = "TC3abcdefgh"

Field Meaning Value

ab Version [13..32]

cd Subversion Number [01..99]

ef Edition [01..99]

gh Patch Level [01..99]

i Debug Delivery ’D’

delivery

Description: • TCB/BTS/TRX software format = "XXXabcdef"

BTS TRX

xxx BCF/ BC1/BC2/SBC/ CBC/PIC/IBC/ ICM

TRX/TR1/DRX/ CDR/EDG/ERM

ab [00.. 32] [00.. 32]

c ’A’.. ’H’ ’A’.. ’H’

d [01..08] [01..08]

ef [01.. 32] [01.. 32]

delivery

Value range: XXXabcdefghi (g, h and i are optional)

Object: software - Download

Page 132 of 446 411-9001-124 18.08 1.0


date

date

date

Type: DP

Checks: [A]: Corresponding executableSoftware object must exist. That means that the software delivery must be previously installed from CD-ROM or gigatape on MD disk.• [A]: The software being downloaded must be present on MD disk and

accessible.

• [A]: There should be no downloading in progress of the same type of software.

• [A]: The software must match the architecture of BSC to which it is being downloaded.

• [A]: The parent bsc object is unlocked.



Object: md - Archive

Type: DP

Note: Archiving fault, observation, or trace data is not possible for the current day.

Description: Date on which data to restore were recorded.Date format entry forms are detailed in Kapsch GSM OMC-R Com-mands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Object: md - Restore

Type: DP



Object: omc - Restore

Type: DP

delivery

411-9001-124 18.08 1.0 Page 133 of 446


day intervention

day to be purged

degradedCause

degradedCause

delayBetweenRetrans Class 2

Description: Type of action associated with an alarm criterion in the daytime configuration.

Value range: [noAlarm / critical / major / minor]


Type: DP

Description: Date on which the data to purge were recorded.Date format entry forms are detailed in Kapsch GSM OMC-R Com-mands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Object: omc - Data purge

Type: DP

Release: V10

Description: Gives the reasons of the degraded or enabled state.

Value range: [Not significant, GPRS]

Object: bts

Type: DD

Release: V15

Description: Gives the reasons of the degraded or enabled state.

Value range: [Lack of Abis resources / Site not supporting Edge / Site insufficient number of DS0 / TRX insufficient Edge capability / Site not supporting CS3 CS4 / TRX insufficient Packet capability / Site not supporting nei-ther CS3 CS4, neither Edge / Site not supporting CS3 CS4, with insuffi-cient number of DS0 / TRX insufficient Edge capability in a site not supporting CS3 CS4 / TRX insufficient Edge and packet capability / TRX not mapped to GsmUmtsCombBcchTeiVal / Not significant]

Object: transceiver

Feature: GPRS

Type: DD

Release: V15

Description: Number of occurrences of a paging sub-group that separates two trans-missions of the same paging message.The following inequality, that is not checked by the system, must be true (refer to these entries in the Dictionary):retransDuration ≥ (delayBetweenRetrans + 1) x nbOfRepeat


Page 134 of 446 411-9001-124 18.08 1.0


deltaUtc

detectionFunction

directAllocIntFrRxLevDL Class 3

directAllocIntFrRxLevUL Class 3

Object: bts

Default value: 0

Type: DP

Release: V8

Description: Gap between the current OMC-R agent time and the GMT reference. Enter a positive value [+m] when the OMC-R agent is located east of the Greenwich meridian and a negative value [-m] when it is located west.

Value range: [-1440 to +1440] minute The range of possible values allows to update the OMC-R reference time within ± 24 hours.

Object: md

Type: DP

Remark: Setting this attribute does not change the time displayed in the system "Session informations" window which refers tothe workstation internal clock.

Note: This parameter cannot be modifield.

Description: Associated function.

Value range: [excessiveAnomalyRate / outOfRangeCounter]

Object: mdWarning

Type: DP

Description: Downlink RxLev threshold above which a TCH-FR could be allocated in the small zone of a multi-zone cell (in conjunction with directAllocIntFr-RxLevUL).




Type: DP


Remark: V18.0

Description: Uplink RxLev threshold above which a TCH-FR could be allocated in the small zone of a multi-zone cell (in conjunction with directAllocIntFrRx-LevDL).




Type: DP

411-9001-124 18.08 1.0 Page 135 of 446


directedRetry Class 3

directedRetryModeUsed Class 3

directedRetryPrio Class 3


Remark: V18.0

Description: Minimum signal strength level received by the mobiles to be granted ac-cess to the neighbor cell, used in processing directed retry handovers in BTS mode.

Value range: [less than -110, -110 to -109,... , -49 to -48, more than -48] dB


Default value: >-48 dB

Type: DP

Remark: V9

Description: Specify how directed retry handovers are processed in a cell either di-rectly by the BSC (microcells only) or by querying the BTS first.

Value range: [bsc / bts]

Object: bts

Default value: bts

Type: DP

Checks: • [C/M]: The BSC mode is authorized if the cell is a microcell (cell-Type) and the adjacent cell umbrella Ref attribute is defined.

Note: The micro cell should be entirely covered by the macro cell in order to use efficiently the bsc mode.The use of the bts mode is recommended in a hot spot when these are several micro cells under the umbrella.The bts mode allows the use of micro cells to rescue the umbrella cell and also avoids a saturation of the umbrella cell.The bts mode is also recommended for all other cases.

Remark: V9

Description: Defines the number priority for directed retry handovers.


Object: bts


Type: DP

Remark: V12

Page 136 of 446 411-9001-124 18.08 1.0


directory

display Data Configuration

display Data Information

distHreqt Class 3

distributionActivation Class 3

Description: Name of the directory created on the OMC-R agent disks for storing a delivery containing a BSS software version.The directory name identifies the type and version of the BSS software stored. Refer to the executableSoftware entry in the Dictionary.If the directory exists on the OMC-R agent disks, the user is warned.

Value range: [BSxabvcdefgh (BSC software) / XXXabcdef (others)]

Object: md - Create delivery dir

Type: DP

Description: A command applied on btsSiteManager to configure the data display.

Value range: normal EDGE

Object: Select the object instance and choose the command.

Description: A command applied on btssiteManager to state required data display.

Value range: normal EDGE

Object: Select the object instance and choose the command.

Description: Number of distance measurements, used to compute the weighted av-erage MS-to-BTS distance in handover algorithms.



Default value: 4

Type: DP

Checks: • [C/M]: distHreqt is equal to the number of weights in distWtsList (refer to the next entry).

Description: Activation of distributions for observation purpose.

Object: bts

Value range: [0/1: disabled / enabled]

Type: DP

Feature: Distribution on Radio measurements

Default value: 0

Checks: • [C/M]: Measurement distribution cannot be activated if interference matrix is running on this cell. The purpose of this semantic check is to forbid activation of interference matrix and distribution features at the same time on a cell.

411-9001-124 18.08 1.0 Page 137 of 446


distributionDuration Class 3

distHreqt Class 3

Release: V15


Description: Duration of the observation.

Object: bts

Value range: [0..92] (1 unit = 15 minutes)

Note: 0 is interpreted as 1

Type: DP

Checks: • [C/M] Measurement distribution cannot be activated if interference matrix is running on this cell. The purpose of this semantic check is to forbid activation of interference matrix and distribution features at the same time on a cell.


Default value: 0

Release: V15


Description: Starting time of the observation period for distributions (OMC-R server current timer).

Object: bts

Value range: [00:00 to 23:59]

Type: DP


Default value: 00:00

Checks: • [C/M] Measurement distribution cannot be activated if interference matrix is running on this cell. The purpose of this semantic check is to forbid activation of interference matrix and distribution features at the same time on a cell.


Note: The distributionTime parameter set by the operator is relative to the OMC-R server current timer, and not to the local BTS hour.In case of feature activation on all cells of a BSC, the time to compute all the corresponding TGEs can take up to 20 minutes. To ensure that the feature is not to be activated the day after, the operator must leave a margin of 30 minutes between activation time and distributionTime parameter.

Release: V15

Page 138 of 446 411-9001-124 18.08 1.0


distributionQualityThreshold Class 3

distWtsList Class 3

diversity Class 2

Description: RxQual threshold for RxLev distribution.This parameter is used according to the following principles:• Uplink case: measurements are those given by the BTS. A measure-

ment is taken into account in the uplink RxLev distribution if the RxQual_UP is equal to or greater than distributionQualityThreshold.

• Downlink case: measurements are those given by the MS. A mea-surement is taken into account in the downlink RxLev distribution if the RxQual_Dw is equal to or greater than distributionQualityThreshold.

• For RxQual distributions, all measurements are kept whatever their RxQual values are.

Object: bts


Type: DP


Default value: 0

Release: V15


Description: List of no more than sixteen weights, used to compute the average MS-to-BTS distance from distHreqt measurements.The L1M function balances distHreqt raw measurements with the weights defined in the distWtsList list. Each measurement is partnered with one weight in the list.Weight/measurement associations are set in the order which the weights are recorded. The latest received measurement is always partnered with the first weight in the list.Super-average = [(measurement i x weighti)] / 100, i = 1 to distHreqt



Default value: 40 30 20 10

Type: DP

Checks: • [C/M]: The number of weights in the list is equal to distHreqt and their sum equals 100.

Description: Whether reception diversity is allowed in a cell. This parameter is used to control the diversity activation and the choice of the algorithm


Value range: disabled (0) / enabled (1) / enhancedDiversity (3)

Object: bts


411-9001-124 18.08 1.0 Page 139 of 446


dlGMSKMCS2UpperThreshold Class 3

dlGMSKMCS3UpperThreshold Class 3

dlMCS2UpperThreshold Class 3


Type: DP

Note: The Joint Diversity feature is applicable only on e-DRX and RM hard-ware. If the value enhancedDiversity is used for others types of TRX with diversity, then the V17 BTS shall apply the classic value (diversity enabled = 1).

Description: The parameter sets the threshold between MCS2 and the next code in the two DL GMSK Only Link Adaptation tables and the DL GMSK table.


Object: bts

Default value: 0 (disabled MCS2 in the Link Adaptation tables)

Feature: EDGE link adaptation (20219)

Type: DP

Note: V15

Description: The parameter sets the threshold between MCS3 and the next code in the two DL GMSK Only Link Adaptation tables and the DL GMSK table.


Object: bts


Default value: 0 (disabled MCS3 in the Link Adaption tables)

Type: DP

Release: V15

Description: The parameter sets the threshold between MCS2 and the next code in the DL 8PSK Link Adaptation table.


Object: bts



Type: DP

Release: V15



Object: bts


Page 140 of 446 411-9001-124 18.08 1.0







Type: DP

Release: V15



Object: bts



Type: DP

Release: V15



Object: bts



Type: DP

Release: V15



Object: bts



Type: DP

Release: V15



Object: bts



411-9001-124 18.08 1.0 Page 141 of 446


diversityUTRAN Class 3

drxTimerMax Class 3

dtxMode Class 3

Type: DP

Release: V15

Description: Indicates if there is diversity in the cell or not

Value range: 0: no diversity / 1: diversity


Default value: 0

Type: DP

Release: V17

Notes: This parameter is only available for BSC 3000.

Description: Maximum value allowed for mobile stations to request non-DRX mode after packet transfer mode.

Value range: [0 (0s), 1 (1s), 2 (2s), 3 (4s), 4 (8s), 5 (16s), 6 (32s), 7 (64s)] The deac-tivation value for the sub-feature TF1220.3 transfer non DRX mode is 0.

Object: bts

Feature: GPRS (SV407 - V12, and TF1220 V12.4c)

Default value: 0 s

Type: DP

Release: V12

Description: MS control of the discontinuous transmission mechanism in a cell.Discontinuous transmission is designed to lessen MS battery consump-tion and diminish interference by breaking off the transmission when no data or speech are being transmitted.

Value range: For BSC 3000:[frmsMayUseDtx_hrmsShallNotUseDtx, frmsShallUseDtx_hrmsShallNotUseDtx, frmsShallNotUseDtx_hrmsShallNotUseDtx, frmsMayUseDtx_hrmsMayUseDtx, frmsShallUseDtx_hrShallUseDt, frmsShallNotUseDtx_hrShallUseDtx].

Object: bts

Default value: For BSC 3000:frmsMayUseDtx_hrmsMayUseDtx

Type: DP

Release: The cellDtxDownlink attribute allows users to control the use of dis-continuous transmission on the downlink. Refer to this entry in the Dic-tionary.

Page 142 of 446 411-9001-124 18.08 1.0


duration

dwAckTime Class 3 (packetAckTime)

dynamicAbis class 2

Description: Time delay before running the next command.The Sleep command can be inserted in a command file as many times as necessary.


Object: commandFile - Sleep command

Type: DP

Description: Defines the DL TBF Keep-Alive timer.

Value range: [1 to 64] steps 500 ms for downlink transfer

Object: transceiver

Feature: GPRS (SV407 - V12 and TF1220 - V12.4c)

Default value: 1

Type: DP

Release: V12

Description: Enables and disables the dynamic abis feature

Value range: Disabled/Enabled


Default value: Disabled

Checks: • 702CO01 "The dynamicAbis feature can not be activated on a btsSiteManager supporting more than 16 EDGE transceivers".

• 702CO02 "It is not allowed to set dynamicAbis parameter to "en-abled" on a BTS e-cell and S8000 BCF or BTS version less V17".

• 11CO01 "The EDGE capability of a transceiver cannot be modified if the btsSiteManager is unlocked, and the dynamicAbis feature is en-abled on it. The EDGE capability of a transceiver is set using the edgeDataServiceType parameter. ".

• It is forbidden to modify the numberOfJokerDS0 parameter on a transceiver object if the parent btsSiteManager instance is unlocked and the dynamic abis feature is activated.

• It is forbidden to add or remove an EDGE transceiver if the parent btsSiteManager instance is unlocked and the dynamic abis feature is activated. An EDGE transceiver is a transceiver where edgeDataSer-viceType = fullCapabilityRequested.

• The egprsServices parameter on a bts object cannot be modified, if the parent btsSiteManager is unlocked, and the dynamicAbis feature is enabled on it.

Release: V17


411-9001-124 18.08 1.0 Page 143 of 446


dynamicAgprsAllowed Class 2

2.6. E

early classmark sending Class 3

earlyClassmarkSendingUTRAN Class 3

EATrafficLoadEnd Class 3

Description: Enables or disables the Dynamic Agprs feature on the whole PCU.

Value range: [yes / no]

Object: pcu

Default value: disabled or no (according to BSC architecture and release)

Release: V14

Note: If EDGE is activated, enabling the dynamic Agprs feature is strongly rec-ommended.

Description: Whether Early classmark sending procedure initiated by a multiband MS is allowed.The information is broadcasted to the mobiles at regular intervals on the cell BCCH (SYS INFO 3).

Value range: [Not Allowed/Allowed]

Object: bts

Default value: Not Allowed

Type: DP

Note: The recommended value is “Allowed”.

Release: V10

Description: Indicates whether UTRAN classmark change message will be sent with the Early classmark sending


Object: bts


Type: DP

Release: V17


Description: Used to trigger the activation/deactivation of the VEA allocation accord-ing to Filtered_TCH_ratio.The EVEA feature is activated as soon as the EATrafficLoadStart and EATrafficLoadEnd parameters are both different from 100.If the EATrafficLoadStart parameter is equal to 100 and the EATraffi-cLoadEnd parameter is different to 100, the EVEA feature is activated.

Value range: [0...100], step = 1

Object: bts

Feature: Enhanced very early assignment

Default value: 100

Page 144 of 446 411-9001-124 18.08 1.0


EATrafficLoadStart Class 3

edgeDataServiceType Class 2

edgeFavor Class 3

eDGEMixity Class 3

Type: DP

Release: V18.0

Description: Used to trigger the activation/deactivation of the VEA allocation accord-ing to Filtered_TCH_ratio.The EVEA feature is activated as soon as the EATrafficLoadStart and EATrafficLoadEnd parameters are both different from 100.If the EATrafficLoadStart parameter is equal to 100 and the EATraffi-cLoadEnd parameter is different to 100, the EVEA feature is activated.


Object: bts

Default value: 100

Type: DP

Release: V18.0

Description: Type of EDGE packet data service which can be managed by one TD-MA.

Value range: capability not requested / full capability requested

Object: transceiver

Default value: capability not requested

Type: DP

Release: V15

Description: The parameter is used by PCU to configure the relative offer of an EDGE TDMA.

Value range: 1 to 5 (by step of 0,04)

Object: transceiversc


Default value: 1

Type: DP

Release: V15

Description: Limitation of GPRS mobiles allocation on EDGE TDMA.


Object: bts

Feature: EDGE dynamic allocation (20230)

Default value: 100

411-9001-124 18.08 1.0 Page 145 of 446


efd

efdType

Type: DP

Release: V15

Description: • Identifier of an efd object defined with regard to the md object.

• Seven efd objects are automatically created for the md object, an "efdAlarm" type object, an "efdConfiguration" type object, an "ef-dObs" type object, an "efdSpecificNotif" type object, an "efdStat-eChange" type object, an "efdTrace" type object, and an "efdClass" type object. Refer to the efdType entry.

• The administrativeState attribute of an efd object sets the conditions for forwarding the associated messages to the OMC-R manager.


Object: efd

Type: Id

Note: An efd object should be created in unlocked state.

Description: Type of the messages processed by the efd object.

Value range: • [efdAlarm / efdConfiguration / efdObs / efdSpecificNotif / efdStat-eChange / efdTrace / efdClass]

• An "efdAlarm" type object tallies alarm notifications issued by the OMC-R agent.

• An "efdConfiguration" type object tallies object create and set mes-sages issued by the users and attribute value change messages is-sued by the BSC.

• An "efdObs" type object tallies observation messages collected by the OMC-R agent.

• An "efdStateChange" type object tallies object state change notifica-tions.

• An "efdSpecificNotif" type object allows users to define sets of spe-cific notification messages to process such as endOfArchival, endO-fRestore, beginningOfBdeArchival, downloadEnd, endOfBdeArchival, endOfBdaBuiding, endOfMarkingConsultation, or endOfSoftwareChange.

• An "efdTrace" type object tallies trace messages collected by the OMC-R agent.

• An "efdClass" type object tallies efd class objects creation and dele-tion messages. Thus these notifications enable to identify the external managers which are being connected to the MD-R.

Object: efd

Page 146 of 446 411-9001-124 18.08 1.0


egprsIrULActivation Class 3

egprsServices Class 3

Type: DP


Description: Whether the uplink incremental redundancy feature is enabled or dis-abled.


Object: bts


Type: DP

Checks: • [M]: Uplink incremental redundancy can not be activated if EDGE feature is not activated on the cell. Refer to the egprsServices entry in this dictionary.

Release: V16


Description: Activates EDGE in the cell. If ’1’, sets to ’1’ the EDGE presence bit in the GPRS CELL Options including BEP-PERIOD, EGPRS_PACKET_CHANNEL _REQUEST. If ’0’, sets to ’0’ the EDGE presence bit in the GPRS Cell Options omitting BEP-PERIOD and EGPRS_PACKET_CHANNEL_REQUEST.

Value range: Disabled (value 0); Enabled (value 1)

Object: bts


Default value: 0

Type: DP

Checks: • [M]: Checks are performed to determine the presence of a valid li-cense for EDGE on the following operations:

• setting the egprsSer vice parameter on the bts object

• unlocking a TRX

• building a BSC

• resetting a BDA of a BSC

If the check fails, then the corresponding action is rejected and a clear error message displayed.

Release: V15

411-9001-124 18.08 1.0 Page 147 of 446


emergencyCallPriority Class 3

emergencyCallRestricted Class 3

emergencyThreshold Class 3

eMLPPThreshold Class 3

Description: Index in the table allocPriorityTable for a TCH allocation request whose cause is "emergency call".This priority is used in primo-allocations or when an SDDCH cannot be allocated for overload reasons.


Object: bts

Default value: 17

Type: DP

Description: Whether emergency calls from mobiles are authorized in a cell.

Value range: [not restricted / restricted]• not restricted..... All emergency calls are accepted whichever is the

mobile access class

• restricted

– Emergency calls are forbidden for mobiles with access classes 0to 9

– For mobiles with access classes 11 to 15, emergency calls areforbidden for those whose classes are listed in the entries of thenotAllowedAccessClasses attribute

Object: bts

Default value: restricted

Type: DP

Description: If the priority of a group call is equal or higher than emergencyThresh-old, a notification is periodically sent. A mobile station entering a cell where such a high priority group call is ongoing is then notified.

Value range: [none, priority 4, priority 3, priority 2, priority 1, priority 0, priority B, pri-ority A] none is the lowest priority priority 0 is recommended


Feature: ASCI

Default value: priority 0

Type: DP

Release: GSM-R V15

Description: Defines the minimum value that the eMLPP Precedence of an incoming call must have to be taken into account by the BSS with inband signaling (paging and vbs/vgcs assignment request).

Value range: [none / priority 4 / priority 3 / priority 2 / priority 1 / priority 0 / priority B / priority A]

Page 148 of 446 411-9001-124 18.08 1.0


enableRepeatedFacchFr Class 2

enableRepeatedFacchHr Class 2

enableRepeatedFacchWBFr class 2


Feature: ASCI (GSM-R V12)

Default value: none

Type: DP

Release: V12

Description: Enables or disables the Repeated FACCH feature on AMR FR.

Value range: [disabled / FR 4.75 kbps / FR 5.9 and lower / FR 6.7 and lower]

Object: bts

Feature: Repeated Downlink FACCH

Default value: disabled (0)

Type: DP

Note: • The recommended value is FR 6.7 and lower.

• This parameter applies to BSC 3000 V16 and higher.

Release: V16

Description: Enables or disables the Repeated FACCH feature on AMR HR.

Value range: [disabled / HR 4.75 kbps / HR 5.9 and lower / HR 6.7 and lower]

Object: bts

Feature: Repeated Downlink FACCH for TCH/H


Type: DP

Note: The recommended value is HR 6.7 and lower.

Release: V18.0

Description: This parameter enables/disables the repeated FACCH feature on the AMR-WB channel and also specifies the threshold to reach before using the repeated downlink FACCH procedure.

Value range: [disable, AMR-WB FR 6.60 kbps, AMR-WB FR 8.85 and lower]

Object: bts


Default value: disable

Release: V18.0

411-9001-124 18.08 1.0 Page 149 of 446


encrypAlgoAsscomp Class 1

encrypAlgoHoperf Class 1

encrypAlgoHoreq Class 1

encryptionAlgorSupported Class 0

Description: Whether the "Chosen encryption algorithm" element is used in the AS-SIGN COMPLETE messages (Phase II compliance).




Type: DP

Release: V8

Description: Whether the "Chosen encryption algorithm" element is used in the HAN-DOVER PERFORMED messages (Phase II compliance).




Type: DP

Release: V8

Description: Whether the "Chosen encryption algorithm" element is used in the HAN-DOVER REQUEST ACKNOWLEDGE messages (Phase II compli-ance).




Type: DP

Release: V8

Description: For BSC 3000. Type of ciphering capability supported by the BTSs of a BSS. When no ciphering capability is supported, users’ calls are not crypted.

Value range: • [none / gsmEncryptionV1]

Object: bsc

Default value: none

Type: DP

Checks: • [C/M]: Only one type of ciphering capability is defined.

Version: V15-V16

Page 150 of 446 411-9001-124 18.08 1.0


encryptionAlgorSupported Class 3

end date

end date

end of probative Phase Type

Description: Type of ciphering capability supported by the BTSs of a BSS. When no ciphering capability is supported, users’ calls are not crypted.

Value range: • [none / gsmEncryptionV1]

• gsmEncryptionV3FallbackNoEncryption

• gsmEncryptionV3FallbackV1

Object: bsc

Default value: none

Type: DP

Checks: • [C/M]: Only one type of ciphering capability is defined.

Version: V17

Description: To select call monitoring data recorded on that date and before. It is on or after beginning date.Do not fill in if information produced to the end should be displayed.

Value range: [mm/dd/yyyy hh:mm:ss]

Object: Call monitoring - Display (SDO)

Type: DP

Checks: [A]: end date is on or after beginning date.

Description: Date on which data were last recorded in the log (default is the current date). It is on or after start date.Date format entry forms are detailed in Kapsch GSM OMC-R Com-mands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in if this criterion is not to be selected.


Object: System session log - Filter

Type: DP

Checks: • [A]: end date is on or after start date.

Description: Whether the user validate or cancel the software change after new de-livery activation.

Value range: [validate software change / cancel software change]

Object: bsc - End of probative phase

Type: DP

Release: V11

Note: This parameter only applies to BSC Upgrades with prototype BDA change (BSC Version Upgrade and BSC Edition Upgrade).

411-9001-124 18.08 1.0 Page 151 of 446


end time

end time

endAlarmFilter

endAlarmThreshold

Description: Absolute time of final job run if the job is to be periodically run over a lim-ited period of time.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).If date matches the date in start time, fill in time with a value after start time.


Object: job

Condition: To define when a job periodicity is defined and only if the job life is lim-ited (user’s choice).

Type: DP

Checks: • [A]: end time is after start time.

Description: End of system log reading on the requested end date (default is 24:00).Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in if this criterion is not to be selected.

Value range: [<time>]


Type: DP

Checks: • [A]: If end date and start date are identical, end time is after start time.

Description: Condition for ceasing the alarm when no counter is involved.The fields that can be combined in the logical expression are described under the startAlarmFilter entry in the Dictionary.



Condition: To define if no counter is associated with the criterion.

Type: DP

Description: Minimum counting value in the reference period, below which an end-of-alarm message is sent if the corresponding start-of-alarm message was sent first. The value must be checked by users.This attribute defines a minimum value read at the end of the defined refPeriod. It must be lower than startAlarmThreshold.Threshold changes are effective when the OMC-R is restarted.

Value range: [0.00 to 2147483646]

Object: mdWarning if detectionFunction = "excessiveAnomalyRate"

Type: DP

Page 152 of 446 411-9001-124 18.08 1.0


endAlarmThreshold

endCounterThreshold

endSearchTime

Description: • Minimum (thresholdLow) / maximum (thresh oldHigh)

• counting value in the reference period, above/below which an end of "lower threshold/upper threshold" alarm message is sent if the corre-sponding start-of-alarm message was sent first. The value must be checked by users.

• If thesholdType is "thresholdLow", it defines a minimum value for a one minute reference period (or the counter collecting period for PCM unavailability counters), above which the end of "lower threshold" alarm message is sent. It must be greater than startAlarmThreshold "low".

Description: • If thesholdType is "thresholdHigh", it defines a maximum value for a one minute reference period (or the counter collecting period for PCM unavailability counters), below which the end of "upper thresh-old" alarm message is sent. It must be lower than startAlarmThresh-old "high".

• Threshold changes are effective when the OMC-R is restarted.

Value range: [0.00 to 2147483646]

Object: mdWarning if detectionFunction = "outOfRangeCounter"

Type: DP

Remark: • The threshold limits depend on the associated counter.

• The BSS counter threshold crossing detection mechanism is de-scribed in Kapsch GSM BSS Fundamentals — Operating Principles (411-9001-007).

Description: Maximum counting threshold when a counter is involved.




Type: DP

Description: Absolute time to end searching for the observation reports to cumulate. It is six hours before beginSearchTime at the most.Observation data accumulating ends with the information contained in the first observation message collected in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary.


Object: Display custom report

Type: DP

Checks: • [A]: endSearchTime is before beginSearchTime.

• [A]: The defined period is less than or equal to six hours.

411-9001-124 18.08 1.0 Page 153 of 446


endSearchTime

endSearchTime

endSearchTime

Description: Absolute time to end searching for the observation report to edit (default is one hour before beginSearchTime).The report displays the information contained in the last observation message generated in the requested period of time. Refer to the part-nered beginSearchTime entry in the Dictionary.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Object: Display raw report

Type: DP

Checks: [A]: endSearchTime is before beginSearchTime.

Note: If no permanent observation has been received within the specified pe-riod, a message is displayed.

Description: Absolute time to end searching for the available permanent observations to list (default is twelve days before beginSearchTime).The last listed report is the first observation report generated in the re-quested period of time. Refer to the partnered beginSearchTime entry in the Dictionary.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Object: List available permanent observations

Type: DP


Description: • Absolute time to end searching for the available permanent observa-tions to list (default is twelve days before beginSearchTime).

• The last listed report is the first observation report generated in the requested period of time. Refer to the partnered beginSearchTime en-try in the Dictionary.

• Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Object: List available temporary observations

Type: DP


Page 154 of 446 411-9001-124 18.08 1.0


endSearchTime

endSessionCriteriaDuration

endSessionCriteriaType

enhancedTRAUFrameIndication

Description: • Absolute time to end searching for the available permanent observa-tions to list (default is twelve days before beginSearchTime).

• The last listed report is the first observation report generated in the requested period of time. Refer to the partnered beginSearchTime en-try in the Dictionary.

• Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Type: DP


Description: Definition of the criterion end a call path tracing session.

Value range: [5 to 1080] mins

Type: DP

Release: V11

Description: Definition of the criterion that will end a call path tracing session.

Value range: [duration / number (of calls) / oam (locking the • callPathTrace object)] duration......... endSessionCriteriaDuration

• = [5 to 1080] minutes number.......... endSessionCriteriaNbCall = [1 to 2500]

• oam............ administrativeState = "locked"

Only one criterion is defined. When it is true, the call follow-up session is stopped in the BSS. Refer to the usageState entry related to this ob-ject in the Dictionary.


Type: DP

Checks: • [M]: The callPathTrace object is locked.

Note: The session is automatically restarted by unlocking the object, regard-less of the end-of-session criterion.

Description: Whether the BTS uses the Enhanced TRAU Frame (EFT = executable Software) for TCU.

Value range: [notAvailable / available / active]

Object: bsc

Type: DI

411-9001-124 18.08 1.0 Page 155 of 446


enhCellTieringConfiguration

equipment identity

Feature: PCM error correction (FM660 - V12) and PCM error correction removal (34533)

Notes: Due to feature "PCM error correction removal", the only value allowed for this parameter is notAvailable

Release: V12

Description: This attribute allows to configure the cell tiering algorithm at BTS level instead of the cellTieringConfiguration attribute from V14 release BSC.This parameter is composed of the following five parameters:pcwiHreqave: Averaging window size for PwCI Value range: Int [0 to 16]numberOfPcwiSamples: Minimum number of PwCI samples required to reach a reliable distribution (representative of the real distribution in the whole cell) x 1000Value range: Int [0 to 60]hoMarginTiering: Hysteresis between the uCirDLH and lCirDLH tiering thresholds to avoid ping-pong handovers, expressed in dBValue range: Int [0 to 63] dB

Description: selfTuningObs: Indicating that the bts is in charge of sending PwCI dis-tribution onto Abis interfaceValue range: [notSentByBts / sentEveryTime / sentEveryHour]nbLargeReuseDataChannels: Mean number of logical channels be-longing to the large frequency reuse pattern and used at the same time for data communications Value range: Int [-16 to 16]


Type: DP

Notes: Available bits are the following:Bit N: 7 6 5 4 3 2 1 0Value X X 0 0 0 0 0 0Note:First bits (upper bits) indicate:- All bits set to 0 = PwCI distribution is gathered if tiering is activated (in-tracell attribute) but not sent onto Abis interface.

Checks: • [C/M] 522DI01: Only ten cells at OMC-R level can be observed with this mode

• [C/M] 522DI02: Only 40 cells at OMC-R level can be observed with this mode

• [C/M] 522CO01: Bit six and seven can not be set at the same time

• [C/M] 522CO02: All the handOverControl object instances of the OMC-R must have the same value for the selfTuningObs field when a bit is different from 0

Note: The bit numbers 0 to 5 (six lower bits) are reserved for future use. This attribute is modified by the Manager. Value changes are notified to the Manager.

Release: V14

Description: This parameter is composed of the bts equipment name and the equipment processor number parameters. Refer to these entries in the Dictionary.

Object: mdWarning (create)

Page 156 of 446 411-9001-124 18.08 1.0


equipment processor number

error concealment unit Class 2

estimatedSiteLoad Class 3

Type: DP

Notes: During the command "create mdWarning", the operator can define ei-ther "equipment identity" or "processor identity", but not both.

Release: V11

Description: To select a processor or an equipment in the preselected type Consult the corresponding notification messages ("Equipment number" field).Do not fill in if neither bsc equipment name nor bts equipment name is defined or if this criterion is not to be selected.

Value range [0 to 200]


Type: DP

Description: Whether the Error Concealment Unit (ECU) is used. The ECU provides a voice quality improvement on the uplink in bad radio propagation con-ditions.

Value range: [not used, used]

Object: bts


Type: DP

Release: V11

Description: This parameter is used• at site creation, in order to preset the Erlang consumption of the new

Cell Group

• otherwise, in order to set the Erlang consumption of a site to a value either less or greater than the one calculated using the ERLANG_PER_N_TRX_CELL table



Default value: 0 (the consumption is then calculated using the ERLANG_PER_N_TRX_CELL table)

Type: DP

411-9001-124 18.08 1.0 Page 157 of 446


exclusive interval of codano

exclusive list of codano

executableSoftware

executableSoftwareId

Notes: The internal erlang capacity of a TMU3 is 1600. A BSC filters the value of the estimatedSiteLoad parameter for a homogeneous TMU configu-ration (for example, either only TMU1, or only TMU3) that has been de-clared as a homogenous TMU configuration through the BSC Data Config,This filtering does not apply to homogeneous BSC configurations that are not declared as this type of configuration through the BSC Data Config.For a homogeneous TMU1 configuration, the BSC uses the value min(550,estimatedSiteLoad). For a homogenous TMU2 configuration, the BSC uses the value min(1100,estimatedSiteLoad). For a homoge-nous TMU3 configuration, the BSC uses the value min(1600,estimated-SiteLoad).For a homogenous TMU3 configuration, the BSC uses the value min(1600, estimatedSite-Load).

Release: V18.0 P&C3

Description: To select messages according to their fault number.The filter can contain one (or several) intervals defining the fault num-bers not to be retrieved. For example, interval 5~8 enables to retrieve ALL the fault numbers except fault numbers 5, 6, 7, and 8.

Value range: [0 to 65535 - 0 to 65535]


Type: DP

Release: V12

Description: To select messages that do not contain one (or several) given fault number(s).



Type: DP

Release: V12

Description: An instance of this managed object class is used to represent a unit of software that is separately identifiable and is ready to be used by the system.



Type: DP

Description: Identifier of a ’executableSoftware’ object class. This identifier is allocat-ed by the MD-R at object creation, if not given by the Manager. This at-tribute cannot be modified.



Page 158 of 446 411-9001-124 18.08 1.0


executableSoftwareName

extended cell Class 2

Type: Id

Release: V13

Description: Name of a software version. This attribute is allocated by the MD-R at object creation, if not given by the Manager. This attribute cannot be modified.



Type: DP

Release: V13

Description: Whether the cell is extended (up to 120 km large) or not. The cell work-ing mode governs the upper limit of the following attribute values (refer to theses entries in the Dictionary):• callClearing, msRangeMax, and rndAccTimAdvThres hold attri-

butes of the bts object

• concentAlgoExtMsRange and concentAlgoIntMsRange attri-butes of the associated handOverControl object if the bts object de-scribes a concentric cell

Value range: [true (extended) / false (normal)]

Object: bts

Default value: false

Type: DP

Checks: • [M]: If the attribute is changed to "true" and a CBCH is defined for the cell, this channel is carried by a radio time slot with an even iden-tifier number. Refer to the channelType entry in the Dictionary.

• [M]: It is not possible to unlock a BTS that has its extendedCell pa-rameter set to true if the site is running software from one of Dual TDMA DLUs.

Release: V9

Note: In that mode, the radio time slots with odd identifier numbers are un-known to the BSC and the diversity functionality is not available in the cells.

411-9001-124 18.08 1.0 Page 159 of 446


extendedTimingAdvanceWindow

external alarm configuration Class 2

Description: This parameter is used to control the Extended Timing Advance Window feature. The presence of valid license for Extended Timing Advance Window is checked on the following operations:• Unlock a TRX (Q3 object: transceiverEquipment)• Unlock a cell (Q3 object: bts)• Unlock a site (Q3 object btsSiteManager)• Unlock an entire site (Q3 objects: those in the btsSiteManager sub-tree)• Build a BDA• Reset (on-line and off-line) a BDAThe attempt to activate the Extended Timing Advance Window function-ality is possible only when a valid license is available. When there is at least one bts with extendedTimingAdvanceWindow activated, then no TRX, bts & btsSiteManager unlocking, no reset BDA build and no build BDA is possible without a valid license.


Object: bts

Deafult value: disabled

Type: DP

Checks: • [M]: There is a feature lock in V18 which requires specific licenses for Extended Timing Advance Window.

Release: V18.0 P&C3

Note: The recommended value is enabled.The feature will be enabled/disabled for all the TRXs of a given cell.

Description: Configuration of the external alarm loops controlled by a BTS. Alarm loop "n" is monitored (not monitored) when the nth bit is set to 1 (0) in the binary field. The alarm mask is immediately displayed in the hexadecimal field just below. The alarm mask can be set using the hexadecimal field as well as the binary field.The number of connectors per alarm board depends on the type of the alarm boards installed in the BTS.

BTS Type of board

Number of protected external alarms per cabinet

S8000 ALCO RECAL (CBCF) 16

S12000 ALCO RECAL (CBCF) 16

BTS 18000 ABM 16

BTS 6000 (See note below.) ABM/RICAM 8

Description The correspondence between those 48 bits and the external alarms of each site directly depends on three factors: the type of BTS, the number of cabinets, and the convention for numbering those cabinets.

Page 160 of 446 411-9001-124 18.08 1.0


external battery cabinet Class 2

externalTime

Description: • S8000/S12000/BTS 18000: 48 external alarms max., up to 3 cabi-nets in the future - 16 alarms per cabinet (16 bits per cabinet).

• BTS 6000: 24 external alarms max., up to 3 cabinets - 8 alarms per cabinet (8 bits per cabinet).

Value range: [48-bit register]


Default value: 48 bits equal to "0"

Type: DP

Note: If RICAM/ICAM is used instead in the BCF, the reduced connectivity leads to limitations in terms of ABMs. Then in term of total alarms:• BTS18000 with RICAM/ICAM max. configuration includes one full main cab + one half ext cab, that is 1 RICAM + 2 ABMs, so 24 DALE max.• BT6000 with RICAM/ICAM max. configuration includes one main cab + one ext cab, that is 1 RICAM+ 1 ABM, so 16 DALE max.

Release: V17

Description: Presence or absence of the optional equipment "ancillary battery cabi-net" in S8000 Outdoor.

Value range: [Present / Absent]


Type: DP

Release: V9

Description: Current OMC-R agent date and time.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Object: md

Type: DP

Remark: Setting this attribute does not change the time displayed in the system "Session informations" window which refers to the workstation internal clock.

Note: This parameter cannot be modified.

411-9001-124 18.08 1.0 Page 161 of 446


extUtbfNoData Class 3

2.7. F

facchPowerOffset Class 2

Family

Observed object: bts

Description: When this Extended UL TBF sub-feature is enabled, it makes possible that MSs do not send Packet Uplink Dummy Control Block during peri-ods of inactivity.


Object: bts


Type: DP

Feature: Extended UL TBF

Release: V15

Description: Power offset that applies to FACCH signaling

Value range: [0..10]; step = 2

Object: bts

Type: DP

Feature: Tx power offset for signaling channels

Default value: 0 (no power offset)

Note: This parameter applies to BSC 3000 V16 and higher.

Release: V16

Description: Family of counters in which are chosen the counters to be observed.The list of the available families depends on the Observed object class and the observation type selected in the report template definition of the observation. See Tables hereafter.

Value range: [See tables below]


Type: DP

Checks: [M]: Family is used to include counters in observation report. Family is not saved with the report template as it is reset every time the template editor is open. Counters from different families can be included in the same report template.Observed object: bsc

Observation real time (ORT)

A interface, synthetic

Observation fast statistic (OFS)

A interface, OMC interface Releases of communications in signaling phase, Channel mode, ASCI, NONE, BSC 3G, synthetic

Page 162 of 446 411-9001-124 18.08 1.0


Observed object: bts

Observed object: transceiverZone

Observed object: transceiverEquipment

Observed object: btsSiteManager

Observed object: pcmCircuit

Observed object: adjacentCellHandOver


SDCCH allocations, Intra-bss handovers, Inter-bss handovers, TCH allocations, Establishment, Global handovers


SDCCH allocations, TCH allocations, Channel mode, Inter-bss handovers, Intra-bss handovers, Intra-cell handovers, Dedicated channel assignment, Global handovers, Establishment, Releases of communications in signaling phase, Releases of communications in traffic phase, Layer One Management, Interferences, Directed retry, SMS, Abis Level 2, ASCI, NONE, GPRS, AMR, EDGE, WPS, synthetic


SDCCH allocations on TrZone TCH allocations on TrZone


SDCCH allocations on TrZone, TCH allocations on TrZone, Layer One Management on TrZone, GPRS on TrZone, AMR on TrZone, EDGE, WPS


----------------------


----------------------


----------------------


BSC 3G - Abis Level 1


----------------------


PCM/synthetic


----------------------


Neighbor cells, AMR

411-9001-124 18.08 1.0 Page 163 of 446


Observed object: omu

Observed object: tmu

Observed object: cc

Observed object: cem

Observed object: pcmPort

Observed object: signalingLink

Observed object: channel


----------------------


BSC 3G


----------------------


BSC 3G


----------------------


BSC 3G


----------------------


BSC 3G


----------------------


BSC 3G - PcmPort


----------------------


----------------------


----------------------


----------------------

Page 164 of 446 411-9001-124 18.08 1.0


faultNumber

fDDARFCN Class 3

fDDMultiratReporting Class 3

fDDReportingThreshold Class 3

Description: To select messages with a given fault number.This parameter is a component of the specific problems filter. Refer to this entry in the Dictionary.



Type: DP

Description: UTRAN FDD frequency

Value range: 0... 16383


Type: DP

Checks: • [M]: AdjacentCellUtran objects belonging to the same bts cannot have more than 3 different fDD_ARFCN values.

• [C/M]: The set of attributes fDDARFCN and scramblingCode must be unique among all the instances of the objects adjacentCellUTRAN at-tached to the same bts The purpose of this check is to Check unicity of UTRAN radio neighbouring cells identifiers for one GSM cell.

• [C/M]: fDDARFCN or scramblingCode cannot be changed if Interfer-ence Matrix feature is activated on the bts.

• [C/M: Check that there is no more than three different FDD_ARFCN values in all the adjacentCellUTRAN objects of one cell.


Description: Number of FDD cells to be reported in the list of strongest cells in the EMR message

Value range: 0...3, 0 = No UTRAN cell is favored, 1 = strongest UTRAN cell is fa-vored. 2 = strongest UTRAN cells are favored. 3 = strongest UTRAN cells are favored.

Object: bts

Default value: 0 - No UTRAN cell is favored.

Type: DP

Checks:

Release: V17


Description: Apply priority reporting if the reported value is above threshold for FDD frequency band

Value range: 0...6 on MOD (corresponds to -115, -109, -79 dBm RSCP values on MMI; + 7 on MOD corresponds to “never” on MMI)

411-9001-124 18.08 1.0 Page 165 of 446


fDDReportingThreshold2 Class 3

fERThreshold1 Class 3



Default value: Never

Type: DP

Checks:

Release: V17


Description: Indicates the CPICH Ec/N0 level above which UTRAN cells will be reported by the MS

Value range: 0... 63 (0 means always reported) The Ec/No step is in half dB:• “0” means always reported.

• In range 1 to 49, “1” means “CPICH Ec/No -24 dB” and “49” means “CPICH Ec/No 0 dB”.

• Values from 50 to 63 should not be used for Ec/No.


Default value: 0

Type: DP

Checks:

Release: V17

Note: This parameter is available only for BSC 3000.

Description: Lowest threshold taken into account for Frame Erasure Rate (FER) evaluation.

Value range: [0 to 100], steps of 0.1 %

Object: bts

Default value: 0

Type: DP


Checks: [C/M]: Following rule applies: fERThreshold1 <= fERThreshold2 <= fERThreshold3 <= fERThreshold4 The purpose of this semantic check is to check coherency between FER thresholds.


Release: V15

Description: Second threshold taken into account for FER evaluation.


Object: bts

Default value: 0

Page 166 of 446 411-9001-124 18.08 1.0




fhsRef Class 2

Type: DP


Checks: [C/M]: Following rule applies: fERThreshold1 <= fERThreshold2 <= fERThreshold3 <= fERThreshold4The purpose of this semantic check is to check coherency between FER thresholds.

Release: V15

Description: Third threshold taken into account for FER evaluation.


Object: bts

Default value: 0

Type: DP


Checks: [C/M]: Following rule applies: fERThreshold1 <= fERThreshold2 <= fERThreshold3 <= fERThreshold4 The purpose of this semantic check is to check coherency between FER thresholds.


Release: V15

Description: Highest threshold taken into account for FER evaluation.


Object: bts

Default value: 0

Type: DP


Checks: • [C/M]: Following rule applies: fERThreshold1 <= fERThreshold2 <= fERThreshold3 <= fERThreshold4

The purpose of this semantic check is to check coherency between FER thresholds.


Release: V15

Description: Identifier of the frequencyHoppingSystem object that defines the fre-quency hopping management parameters for the radio time slot. Setting this attribute and the maio attattribute allows the time slot to obey fre-quency hopping laws.


Object: channel

Condition: To define if the time slot hops in frequencies.

411-9001-124 18.08 1.0 Page 167 of 446


filteredTrafficCoefficient Class 3

floor

flowControlMaxDelay

Type: DP

Checks: • [C/M]: This attribute is undefined if frequency hopping is not allowed for the parent bts object (btsIsHopping = "no hopping") or the chan-nelType of the channel object is "mainBCCH", "mainBCCHComb-ined", or "bcchSdcch4CBCH".

• [C/M]: If the attribute is defined, the following is checked:

• The maio attribute is also defined.

• The referenced frequencyHoppingSystem object is created for the parent bts object.

• Each frequency occurs once in the mobileAllocatio n list and is al-lotted in the cellAllocation list of the parent bts object.

Checks: • The number of frequencies in the mobileAllocation list is greater than the maio attribute value.

• Concentric cell: The frequencies in the mobileAllocation list are not used in the zone to which the parent transceiver object does not be-long.

Description: Filter coefficient which is taken into account in the cell load evaluation.

Value range: [0 to 1, by step of 0.001]

Object: bts

Default value: 0

Type: DP

Feature: AMR based on traffic

Release: V15

Description: Floor number which identifies the localization in a building.

Value range: [1 to 2 characters]

Object: transcoder, controlNode, interfaceNode, hardware transcoder 3G.

Type: DD

Description: This attribute specifies the maximum time interval between two consec-utive FLOW-CONTROL-MS messages sent to the SGSN.


Default value: 300

Object: pcusn

Type: DP

Release: V14

Page 168 of 446 411-9001-124 18.08 1.0


flowControlMaxRate

fnOffset class 2

forced handover algo Class 3

frAmrPriority Class 2

Description: This attribute specifies the minimum interval between sending consecu-tive Flow-Control PDU for a given BVC or for a MS. It represents the C timer in the ETSI GPRS specifications.

Value range: [1001 to 9999] ms

Default value: 2000

Object: pcusn

Type: DP

Release: V14

Description: Allows to specify and control Frame Number (FN) difference between BTSs in case of network synchronization by GPS.Refer also to the tnOffset entry in this dictionary.

Value range: [0..84863]


Default value: 0


Type: DP

Release: V15


Description: Minimum signal strength level received by the mobiles to be granted ac-cess to a neighbor cell in case of forced handover.


Default value: less than -110


Type: DP

Release: V9

Description: This attribute defines the AMR FR priority of a TDMA. This attribute is modified only if the corresponding ’bts’ object instance is locked (object-MustBeLockedError).

Value range: Int [0 to 2] Priority 0 is given to a high priority TDMA Priority 1 is given to a low priority TDMA Priority 2 disables this service on the TDMA

Default value: 0

Object: transceiver

Type: DP

Release: V14


411-9001-124 18.08 1.0 Page 169 of 446


frequencyHoppingSystem

frPowerControlTargetMode Class 3

frPowerControlTargetModeDl Class 3

Description: Identifier of a frequencyHoppingSystem object that defines frequency hopping management parameters for radio time slots that obey frequen-cy hopping laws. A bts object may reference up to sixty-four objects of this type.Refer to the hoppingSequenceNumber and mobileAllocation entries in the Dictionary.


Object: frequencyHoppingSystem

Type: Id

Checks: • [C]: The associated bts object is created and the frequencyHopping-System object is not created for that object.

• [C]: The number of frequencyHoppingSystem objects created for a bts object is limited to sixty-four.

• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked.

• [M]: The parent bsc object is unlocked and the associated bts object is locked.

• [M/D]: The frequencyHoppingSystem object is created.


Checks: • [D]: No channel object dependent on the bts object refers to the fre-quencyHoppingSystem object (fhsRef attribute).

Description: This attribute defines the target codec mode for AMR FR power control.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute is modified if the ’powerControl’ object instance is un-locked.

Value range: [FR 12.2 / FR 10.2 / FR 6.7 / FR 5.9 / FR 4.75]

Default value: FR 12.2


Type: DP

Release: V14


Description: Downlink AMR codec target used to define the downlink power control threshold for FR AMR calls.

Value range: [FR 12.2 / FR 10.2 / FR 6.7 / FR 5.9 / FR 4.75]

Default value: FR 12.2



Page 170 of 446 411-9001-124 18.08 1.0


fullDlKa Class 3

fullHRCellLoadEnd Class 3

Type: DP

Release: V16


Description: Whether the Full DL Keep Active feature is enabled or not.This feature allows MSs that operate in a non-extended UL TBF mode to increase their uplink throughput.



Object: bts


Type: DP

Note: [C/M]: The following flag combination is prohibited:nwExtUtbf = enabled and fullDlKa = disabled

Release: V15

Description: This parameter defines the threshold that triggers the end of the conges-tion period of the AMR maximization. The AMR maximization is activat-ed as soon as the fullHRCellLoadStart and fullHRCellLoadEnd parameters are both different from 100.


Default value: 100

Object: bts

Feature: AMR maximization

Type: DP

Check: • [C/M]: If the values of both hrCellLoadStart and fullHRCellLoad-Start parameters are different from 100, it means both AMR Based On Traffic (ABOT) and AMR maximization are activated.

• Then a semantic control checks the following:

• fullHRCellLoadStart > fullHRCellLoadEnd > hrCellLoadEnd

• fullHRCellLoadStart > hrCellLoadStart

• [C/M]: If the value of the hrCellLoadStart parameter is equal to 100 and the value of the fullHRCellLoadStart parameter is different from 100, it means that ABOT is not activated and AMR maximization is ac-tivated. Then a semantic control checks the following:

411-9001-124 18.08 1.0 Page 171 of 446


fullHRCellLoadStart Class 3

2.8. G

Check: • fullHRCellLoadStart > fullHRCellLoadEnd.

• [C/M]: If the value of the hrCellLoadStart parameter is different from 100 and the value of the fullHRCellLoadStart parameter is equal to 100, it means that ABOT is activated and AMR maximization is not ac-tivated. Then a semantic control checks the following:

• hrCellLoadStart >= hrCellLoadEnd.

• [C/M]: If the values of both hrCellLoadStart and fullHRCellLoad-Start parameters are equal to 100, it means both AMR Based On Traf-fic (ABOT) and AMR maximization are not activated. No semantic control occurs.

Release: V18.0

Description: This parameter defines the threshold that triggers the beginning of the congestion period of the AMR maximization.The AMR maximization is activated as soon as the fullHRCellLoadStart and fullHRCellLoadEnd parameters are both different from 100.


Default value: 100

Object: bts

Type: DP

Checks: • [C/M]: If the values of both hrCellLoadStart and fullHRCellLoad-Start parameters are different from 100, it means both AMR Based On Traffic (ABOT) and AMR maximization are activated. Then a semantic control checks the following:

• fullHRCellLoadStart > fullHRCellLoadEnd > hrCellLoadEnd

• fullHRCellLoadStart > hrCellLoadStart

Check: • [C/M]: If the value of the hrCellLoadStart parameter is equal to 100 and the value of the fullHRCellLoadStart parameter is different from 100, it means that ABOT is not activated and AMR maximization is ac-tivated. Then a semantic control checks the following:

• fullHRCellLoadStart > fullHRCellLoadEnd.

• [C/M]: If the value of the hrCellLoadStart parameter is different from 100 and the value of the fullHRCellLoadStart parameter is equal to 100, it means that ABOT is activated and AMR maximization is not ac-tivated. Then a semantic control checks the following:

• hrCellLoadStart >= hrCellLoadEnd.

Check: • [C/M]: If the values of both hrCellLoadStart and fullHRCellLoad-Start parameters are equal to 100, it means both AMR Based On Traf-fic (ABOT) and AMR maximization are not activated. No semantic control occurs.

Release: V18.0

Page 172 of 446 411-9001-124 18.08 1.0


geographical coordinates

Description: Definition of the geographical coordinates of the equipment in the net-work.These coordinates are defined by a latitude and a longitude, each ex-pressed by four fields.

Value range: Latitude is expressed by the four following fields:• Deg Lat.......... [0 to 90] degrees

• Min Lat.......... [0 to 59] minutes

• Hundreth of sec Lat........ 0 to 5999] hundredth second

• Direction Lat.... [North / South]

Longitude is expressed by the four following fields:• Deg Lon.......... [0 to 180] degrees

• Min Lon.......... [0 to 59] minutes

• Hundreth of sec Lon........ [0 to 5999] hundredth second

• Direction Lon.... [East / West]

Object: • bsc

• btsSiteManager

• md

• transcoder

Type: DI

Release: V11

411-9001-124 18.08 1.0 Page 173 of 446




Description: Definition of the geographical coordinates of the pcuSN equipment in the network.These coordinates are defined by a latitude and a longitude, each ex-pressed by four fields.



• Hundreth of sec Lat

• ........... 0 to 5999] hundredth second




• Hundreth of sec Lon

• ........... 0 to 5999] hundredth second


Object: pcu, pcusn


Type: DI

Release: V12

Description: Definition of the geographical coordinates of the equipment in the net-work. These coordinates are defined by a latitude and a longitude, each expressed by four fields.



• Hundreth of sec Lat........ 0 to 5999] hundredth second




• Hundreth of sec Lon........ [0 to 5999] hundredth second


Page 174 of 446 411-9001-124 18.08 1.0


gprsAvgParam Class 3

gprsCellActivation Class 3

gprsNetworkModeOperation Class 3

Object: • bsc

• btsSiteManager

• md

• transcoder

Type: DI

Release: V11

Description: This parameter is composed of the following attributes:• nAvgI

• nAvgT

• nAvgW

Refer to these entries in this dictionary.

Release: V12

Description: This is a Flag used to activate the GPRS at cell level.


Object: bts



Type: DP

Release: V12

Description: Indicates the network mode of operation.

Value range: [0..2] with:• 0 = NMO II

• 1 = NMO I (recommended value, activates the feature

• from the MSs point of view)

• 2 = NMO III (forbidden in this release)

Object: bts

Feature: GPRS (TF1134 - NMO I)

Default value: 0 (NMO II)

Type: DP

Release: V15

411-9001-124 18.08 1.0 Page 175 of 446


gprsPcuCrossConnectList Class 2

gprsCellActivation Class 3

gprsNetworkModeOperation Class 3

Description: This parameter is a list of pairs of the following attributes:• pcmNbr

• nbrTch


Value range: BSC 3000 V16, E1 PCM: [0 to 32] pairs of [pcmNbr, nbrTch]BSC 3000 V16, T1 PCM: [0 to 36] pairs of [pcmNbr, nbrTch]BSC 3000 V17: [0 to 54] pairs of pcmNbr, nbrTch]

Feature: PCUSN - more than 12 Agprs PCMs per BSC (18749)

Release: V12

Description: This is a Flag used to activate the GPRS at cell level.


Object: bts



Type: DP

Release: V12

Description: Indicates the network mode of operation.

Value range: [0..2] with:• 0 = NMO II

• 1 = NMO I (recommended value, activates the feature

• from the MSs point of view)

• 2 = NMO III (forbidden in this release)

Object: bts

Feature: GPRS (TF1134 - NMO I)

Default value: 0 (NMO II)

Type: DP

Release: V15

Page 176 of 446 411-9001-124 18.08 1.0


gprsPcuCrossConnectList Class 2

gprsPcuLockExtendedConf Class 2

gprsPermittedAccess Class 3

gprsPreemption Class 3

Description: This parameter is a list of pairs of the following attributes:• pcmNbr

• nbrTch


Value range: BSC 3000 V16, E1 PCM: [0 to 32] pairs of [pcmNbr, nbrTch]BSC 3000 V16, T1 PCM: [0 to 36] pairs of [pcmNbr, nbrTch]BSC 3000 V17: [0 to 54] pairs of pcmNbr, nbrTch]

Feature: PCUSN - more than 12 Agprs PCMs per BSC (18749)

Release: V12

Description: This parameter is composed of the following attributes:• dynamicAgprsAllowed

• agprsTSharingProtection

Refer to these entries in this Dictionary.

Default value: [disabled / 0]

Release: V12

Description: It defines the Routing Area Color (3-bit length) of the cell.If the MS receives different values of the Routing Area Color field in two different cells, it shall interpret the cell re-selection information as if the two cells belonged to different RA.


Object: bts

Default value: 0


Type: DP

Release: V12

Description: Set to yes, it allows the PCU to refuse GSM preemption over shared GSM/GPRS TS if GPRS resources are not sufficient to ensure the min-imum bandwidth for each MS.In the case of lack of GSM radio TS, the BSC has to allocate one shared GSM/GPRS radio TS to GSM and a preemption procedure is started. When one shared radio TS temporarily allocated to GSM is released (end of GSM allocation due to end of call or handover), then a realloca-tion procedure is started to increase the GPRS capacity.


Object: bts

Default value: yes

411-9001-124 18.08 1.0 Page 177 of 446


gprsPreemptionForHR Class 3

gprsPreemptionProtection Class 3

gprsPriority Class 2 (gprsTranscvLockExtendedConf)

gprsState

Feature: GPRS (TF1121 - V12)

Type: DP

Release: V12

Description: Activation of PDTCH pre-emption for HR channel


Object: bsc

Default value: 0 (disabled)

Recommended value:

1 (enabled)

Type: DP

Release: V17

Description: Protection timer used by the BSC in order to reduce the load in case of PCU TDMA TS Status Nack message reception during a preemption procedure. This message is sent by the PCU.

Value range: [1 to 60] second(s)

Object: bts

Default value: 10


Type: DP

Release: V12

Description: Priorities affected to the TDMA.Priority affected to the TDMA when allocating packet resources.

Value range: [p1 or p2 (high GPRS priority)]

Object: transceiver

Default value: p1


Type: DP

Release: V12

Description: Reserved for future use.

Object: bts (cell)

Type: DD

Release: V15

Page 178 of 446 411-9001-124 18.08 1.0


gprsState

gsmTo3GReselection Class 3

Description: Reserved for future use.

Object: transceiver

Type: DD

Release: V15

Description: "gsmtoUMTSReselection" parameter renamed to "gsmto3GReselection". gsmTo3GRe selection is composed of 5 sub-parameters:• 3GTechnology

• 3GSearchLevel

• 3GReselectionOffset

• 3GAccessMinLevel

• 3GAccessMinLevelOffset

• 3GReselectionThreshold

• 3GReselection ARFCN

Object: bts

Type: DP

Checks: • [C/M]: 3GReselection ARFCN’ of the attribute ’gsmTo3GReselection’ accepts empty list (feature not activated) or frequencies must be in bands:

• 1900-1920 MHz 9504 to 9596

• 2010-2025 MHz 10054 to 10121

• 1850-1910 MHz 9254 to 9546

• 1930-1990 MHz 9654 to 9946

• 1910-1930 MHz 9554 to 9646

• 2570-2620 MHz 12854 to 13096

• [C/M]: If the 3GTechnology parameter is set to the TDD value, there is a control that UARFCNs are allowed by 3GPP TS 25.102. UARF-CNs must be part of the DL ARFCN range defined in 3GPP TS 25.102 Rel 7.

Release: V14

411-9001-124 18.08 1.0 Page 179 of 446


gsmToUMTSServiceHo Class 3

GsmUmtsCombBcchTeiVal Class 2

2.9. H

handOver from signalling channel Class 3

handOverControl

Description: Allows the customer to set a value that the BSC uses when the MSC does not provide optional service handover information in ASSIGN_REQUEST or HANDOVER_REQUEST messages

Value range: 0: should;1: should not; 2: shall not;3:gsmToUMTSHoDisabled (always takesprecedence over the MSC value)

Object: bsc

Default value: 3

Type: DP

Release: V17

Note: This parameter is available only for BSC 3000.This parameter is optional.

Description: The TEI value of the GSM TRX which is combined with an UMTS TRX.

Value range: 0 to 254, empty

Object: bts

Default value: empty

Type: DP

Release: V18.0.0 P&C2

Description: Authorization to perform intercell handovers on signaling channels (SDCCH or TCH in signaling mode).




Type: DP

Remark: The attribute was named TCH and sDCCHHandOver on the V8 OMC-R MMI.

Description: Identifier of a handOverControl object that defines handover manage-ment parameters in a cell. A bts object may reference one and only one object of this type.



Page 180 of 446 411-9001-124 18.08 1.0


hardware configuration Class 2

Type: Id

Checks: • [C]: The associated bts object is created and the handOverControl ob-ject is not created for that object.• [M]: The parent bsc object is unlocked. If class 2 attributes are modi-fied, the associated bts object is locked.• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked and the associated bts object is locked.• [M/D]: The handOverControl object is created.• [D]: The associated bts object is not referenced, except by a power-Control object.• [D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.

Description: Type of architecture used in the transceiverEquipment. This parameter flags the TRX in HPRM, RM, MPRM or HPRM3T in the BTS 18000.

Value range: • [Dcu2 / Dcu4 / Drx / Rm / Hprm / Mprm / HPRM3T /Other] for BSC V16 and subsequent releases• [RM1/2 1800 30/30, RM2 1800 30/30, RM1/2 1800 50/30, RM2 1800 50/30, DCU2, DCU4, DRX, RM1/2900 40/40, RM1 900 40/40, RM2 900 40/40, RM1 900 60/45, RM2 900 60/45, RM1/2 1900 30/30, RM1 1900 30/30, RM2 1900 30/30, RM2 1900 50/30, RM1 1800 30/30, RM1 1800 50/30, RM1 850 60/45/Other] for BSC V17 and subsequent releases


Feature: BTS 18000 introduction, BTS 18000 HPRM, differentiation of the BTS 18000 RMs with power transmit level of 40 Watts, and BTS 18000 HPRM3T differentiation at the OMC-R

Default value: 0

Type: DP

411-9001-124 18.08 1.0 Page 181 of 446


hardwareRef Class 2

hardwareRef Class 2

Checks: • [M]: Checks that the default value is not left on BTS 18000. In case of BTS 18000(btsModel = 910, 911, 900, 901), checks at unlock transceiverEquipment that its HardwareConfiguration is different from “DRX”, “DCU2”, “DCU4”.• [M]: Checks that the default value is not left on BTS 6000 or BTS 18000. In case of BTS 6000 or BTS 18000 (btsModel = 910, 911, 900, 901), checks at unlock transceiverEquipment that its HardwareConfigu-ration is one of the following “DCU2”, “DCU4”. or "DRX"• [M]: Checks that default value is set on other BTS than BTS 18000. In case of BTS different from BTS 18000 (btsModel = 910, 911, 900, 901), this checks at unlocktransceiverEquipment that its Hardware Configuration is different from Rm, Hprm, Mprm, Hprm3t or Other.• [M]: Checks that default value is set on other BTS than BTS 6000 or BTS 18000. In caseof BTS different from BTS 6000 or BTS 18000 (btsModel = 910, 911, 900, 901), thischecks at unlock transceiverEquipment thatits Hardware Configuration is different fromRm, Hprm, Mprm, Hprm3t or Other.• [M]: Consistency inside an RM definition. In case of BTS 18000 (bts-Model = 910, 911, 900, 901), this checks at unlock transceiverEquip-ment that its hardware configuration is the same as the other unlocked transceiver equipment of the sameRM.• [M]: Consistency inside an RM definition. In case of BTS 6000 or BTS 18000 (btsModel = 910, 911, 900, 901), this checks at unlock transceiv-erEquipment that its hardware configuration is the same as the otherunlocked transceiver equipment of the same RM.• [M]: Software Reference coherency inside an RM. Existing check that must be run after previous checks.• [M]: • If the sWVersionRunning parameter of the software-transceiv-erEquipment object is ERMxxxxxx, it is not possible to configure the RM3 hardware configurations.• If the sWVersionRunning parameter of the software-transceiv-erEquipment object is NRMxxxxxx, it is not possible to configure the hardware configurations other than RM3.

Release: V11

Description: Hardware reference of a site BCF. Check BSS upgrade file.



Type: DP

Description: Hardware reference of a TRX/DRX. Check BSS upgrade file. When a TRX is a DCU4 or a DRX ( S8000, S12000, E-cell), the hardware refer-ence field of the transceiver equipment object must be equal to 0.



Type: DP

Page 182 of 446 411-9001-124 18.08 1.0


hexa text

highSpeedUplinkDistortionRemoval

hoMargin Class 3

Description: Transcription in hexadecimal of the contents of a short message.The content of the hexa text parameter is displayed when using the com-mand Display hexa. It cannot be modified by the user. Only the content of the text parameter is modifiedby the user.Refer to the text (short message) entry in the Dictionary.

Value range: [chain of characters]

Object: short message - Display hexa

Type: DI

Release: V12

Description: This parameter is used to control the high speed uplink distortion remov-al feature; when enabled, some uplink distortion caused by high speed mobiles will be removed by the BTSThe presence of valid license for High Speed Uplink Distortion Removal is checked on the following operations:• Unlock a TRX (Q3 object: transceiverEquipment)• Unlock a cell (Q3 object: bts)• Unlock a site (Q3 object btsSiteManager)• Unlock an entire site (Q3 objects: those in the btsSiteManager sub-tree)• Build a BDA• Reset (on-line and off-line) a BDAThe attempt to activate the High Speed Uplink Distortion Removal func-tionality is possible only when a valid license is available. When there is at least one bts with highSpeedUplinkDistortionRemoval activated, then no TRX, bts & btsSiteManager unlocking, no reset BDA build and no build BDA is possible without a valid license.


Object: bts


Feature: GSM-R V18.0. Customer specific

Type: DP

Release: V18.0 P&C3

Description: A margin to use for PBGT handovers to avoid subsequenthandover, in PBGT formula.



Default value: 4

Type: DP

411-9001-124 18.08 1.0 Page 183 of 446


hoMarginAMR Class 3

hoMarginAMRUTRAN Class 3

hoMarginBeg Class 3

hoMarginDist Class 3

Description: This attribute defines the handover margin linked to AMR quality hando-ver.This attribute is modified if the ’adjacentCellHandOver’ object instance is unlocked.



Default value: -2

Type: DP

Release: V14

Description: Margin to be used for intercell quality handover to UMTS for AMR calls

Value range: -63...63


Default value: 63

Type: DP

Checks:

Release: V17


Description: Margin to be added to hoMargin until rxLevHreqave for early handover mechanism in order to compensate the lack of measurements.This parameter is coupled with hoMargin and rxLevHreqaveBeg.

Value range: [0..63] dB

Object: bts

Default value: 4

Type: DP

Checks: • [M]: This parameter is inhibited when set to 63 dB.

Note: This parameter shall be set such as hoMarginhoMargin+hoMarginBeg or hoMarginBeg0This parameter is not available for DCU2.

Release V11

Description: Margin to be used for Distance Handovers.



Default value: -24 dB

Type: DP

Release: V8

Page 184 of 446 411-9001-124 18.08 1.0


hoMarginDistUTRAN Class 3

hoMarginRxLev Class 3

hoMarginRxQual Class 3

hoMarginTiering Class 3

Description: Margin to be used for distance handover to UMTS

Value range: -63...63 dB


Default value: 63

Type: DP

Checks:

Release: V17


Description: Margin to be used for signal strength Handovers.




Type: DP

Release: V8

Description: The margin is used for Signal Quality Handovers.




Type: DP

Release: V8

Description: Hysteresis between the uPwCIDLH and lPwCIDLH tiering thresholds to avoid ping-pong handovers (expressed in dB). This attribute allows to configure the CellTieringConfiguration at bts level.

Note: CellTiering mode must be activated.



Default value: 4 dB

Feature: Automatic Cell Tiering (TF995-V12)

Type: DP

Release: V12

411-9001-124 18.08 1.0 Page 185 of 446


hoMarginRxLevUTRAN Class 3

hoMarginRxQualUTRAN Class 3

hoMarginTrafficOffset Class 3

hoMarginTrafficOffsetUTRAN Class 3

Description: Margin to be used for signal strength handover to UMTS



Default value: 63

Type: DP

Checks:

Release: V17


Description: Margin to be used for signal quality handover to UMTS



Default value: 63

Type: DP

Checks:

Release: V17


Description: Minimum signal strength margin with the serving cell allowing the best neighbor cell selection when a handover is triggered for overload rea-sons.



Feature: Handover for traffic reasons (TF132 - V12)

Default value: 0 dB

Type: DP

Checks: • [C/M]: This attribute must be in the range [0 63].• [C/M]: When set to "0", the handovers for traffic reasons are not al-lowed in the adjacent cell.

Release: V12

Note: This attribute only applies to BTSs equipped with non mixed DCU4 or DRX boards.

Description: Offset to be subtracted to the hoMarginUTRAN to allow handover for traffic reason when the current cell is in overload

Value range: 0...63 dB


Default value: 63

Type: DP

Page 186 of 446 411-9001-124 18.08 1.0


hoMarginUTRAN Class 3

hoPingpongCombination Class 3

Checks:

Release: V17


Description: Margin to be used for PBGT handover to UMTS



Default value: 63

Type: DP

Checks:

Release: V17


Description: Two causes (HOInitialCause and HONonEssentialCause), indicating the causes of ping-pong handovers in overlapping areas.The following causes are defined with regard to the neighboring cell:• HOInitialCause indicates the essential handover cause which leads to enter the neighbor cell (cause of incoming handover).• HONonEssentialCause indicates the non-essential handover cause which leads to leave the cell (cause of outgoing handover).This parameter defines the combination for which the hoPingpongTi-meRejection attribute is used.

Value range: [rxQual, rxLev, distance, powerBudget, capture, directedRetry, OaM, traffic, all, allCapture, allPowerBudget, AMRquality]


Feature: General protection against ping-pong handovers (TF821-V12)

Type: DP

Checks: • [M]: The parent bsc object is unlocked.[M]: Check that all the values of ’HOPingpong Combination’ attribute must be different.This element checks for non duplications of HOPingpongCombination values

Notes: • allCapture cause (only applying to HONonEssentialCause)matches the capture cause for all the micro-cells belonging to the current macro-cell. This cause has to be used in order to prevent ping-pong handovers between micro- and macro-layers.• allPowerBudget cause (only applying to HONonEssentialCause) matches the powerBudget cause for all the neighboring cells of the cur-rent cell. This cause is used in order to restore the "Minimum time be-tween handovers" (feature TF218).

Release V12

411-9001-124 18.08 1.0 Page 187 of 446


hoPingpongCombinationUTRAN Class 3

hoPingpongTimeRejection Class 3

hoPingpongTimeRejectionUTRAN Class 3

hoRejectionTimeOverloadUTRAN Class 3

Description: List of couple of causes indicating the causes of ping-pong handovers in the overlapping areas (cause of incoming ho, cause of outgoing ho). It is possible for up to four elements to appear in the list.

Value range: List of cause GSM to UMTS and cause UMTS to GSM (traffic, power-Budget, directedRetry, rxLev, rxQual, distance, OaM (forced ho), all, all-PowerBudGeT)


Default value: ("rxQual", "powerBudget")

Type: DP

Checks:

Release: V17


Description: Time before a new handover attempt is triggered.Refer to bsc object timeBetweenHOConfiguration and btsobject bts time between HO configuration attributes in this Dictionary of Param-eters for this timer activation.Refer to adjacentCellHandOver object hoPingpongCombination attri-bute in this Dictionary of Parameters for the combinations for which this timer applies.To avoid ping-pong handovers this new timer is started after a successful handover. Up to the expiration of this timer, the receipt of HANDOVER INDICATION messageis ignored.

Value range: [0 to 60] s


Feature: General protection against ping-pong handovers (TF821-V12).

Default value: [30 sec]

Release: V12

Description: Time before a new handover attempt to UMTS can be triggered

Value range: 0...60 seconds (0 means immediately)


Default value: 30s

Type: DP

Checks:

Release: V17


Description: Time before trying a new handover attempt toward an overloaded UMTS cell

Value range: 0 ... 60 seconds (0 means immediately)

Page 188 of 446 411-9001-124 18.08 1.0


hoppingSequenceNumber Class 2

hoSecondBestCellConfiguration Class 3

hoTraffic Class 3

Object: bsc

Default value: 30s

Type: DP

Checks:

Release: V17

Note: This parameters is only available for BSC 3000.

Description: Hopping sequence number used by a radio time slot which obeys fre-quency hopping laws.Select different HSNs for nearby cells that use the same set of frequen-cies.



Type: DP

Checks: • [M]: If the frequencyHoppingSystem object isreferenced by a channel object (fhsRefattribute defined), the parent bsc object isunlocked and the associated bts object islocked.

Description: Number of neighbor cells in which the BSC immediatelyattempts to perform a new handover when the previous handover at-tempt failed with return to the old channel.Giving the attribute a value greater than 2 allows the BSC to renew the handover request without waiting for a new set of radio measurements (the first attempt is included in this count). The same list of neighbor el-igible cells is used to process the request (no new list is provided by the BTS).


Object: bsc

Default value: 3

Type: DP

Release: V9

Description: Whether handovers for traffic reasons at bsc level are allowed.


Object: bsc



Type: DP

Release: V12

Note: Enabling this parameter allows the related BTSs with DCU4 or DRX transceiver architecture handle handovers for traffic reasons.

411-9001-124 18.08 1.0 Page 189 of 446


hoTraffic Class 3

hrAmrPriority Class 2

hrCellLoadEnd Class 3

Description: Whether handovers for traffic reasons at bts level are allowed.


Object: bts



Type: DP

Release: V12

Note: This attribute is only available for DCU4 or DRX transceiver architecture.

Description: This attribute defines the AMR HR priority of a TDMA.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can be modified only if the corresponding ’bts’ object in-stance is locked (objectMustBeLockedError).

Value range: [0 to 2]Priority 0 is given to a high priority TDMAPriority 1 is given to a low priority TDMAPriority 2 disables this service on the TDMA

Object: transceiver

Default value: 0

Type: DP

Release: V14


Description: This attribute defines the cell load threshold used for AMR FR/HR deci-sion. This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’bts’ object instance is unlocked.


Object: bts

Default value: 0

Type: DP

Checks: • [C/M]: If the values of both hrCellLoadStart and fullHRCellLoadStart parameters are different from 100, it means both AMR Based On Traffic (ABOT) and AMR maximization are activated. Then a semantic control checks the following:• fullHRCellLoadStart > fullHRCellLoadEnd > hrCellLoadEnd • fullHRCellLoadStart > hrCellLoadStart• [C/M]: If the value of the hrCellLoadStart parameter is equal to 100 and the value of the fullHRCellLoadStart parameter is different from 100, it means that ABOT is not acti-vated and AMR maximization is activated. Then a semantic control checks the following:fullHRCellLoadStart > fullHRCellLoadEnd.

Page 190 of 446 411-9001-124 18.08 1.0


hrCellLoadEnd Class 3

hrCellLoadStart Class 3

hrCellLoadStart Class 3

Checks: • [C/M]: If the value of the hrCellLoadStart parameter is different from 100 and the value of the fullHRCellLoadStart parameter is equal to 100, it means that ABOT is activated and AMR maximization is not acti-vated. Then a semantic control checks the following: hrCellLoadStart >= hrCellLoadEnd.• [C/M]: If the values of both hrCellLoadStart and fullHRCellLoadStart parameters are equal to 100, it means both AMR Based On Traffic (ABOT) and AMR maximization are not activated. No semantic control occurs.

Release: V14


Description: This attribute is used to trigger the beginning of AMR HR allocation in the cell. This attribute is modified by the Manager. Value changes are noti-fied to the Manager. This attribute can only be modified if the ’bts’ object instance is unlocked. In this version, this parameter has the following meaning:• if HRCellLoadStart is equal to 0, then a FR radio channel is always al-located to the MS,• if HRCellLoadStart is greater than 0, then a HR radio channel is allo-cated to the MS, according to its radio conditions.


Object: bts

Default value: 100

Type: DP

Checks: • [C/M]: If the values of both hrCellLoadStart and fullHRCellLoadStart parameters are different from 100, it means both AMR Based On Traffic (ABOT) and AMR maximization are activated. Then a semantic control checks the following:• fullHRCellLoadStart > fullHRCellLoadEnd >hrCellLoadEnd• fullHRCellLoadStart > hrCellLoadStart• [C/M]: If the value of the hrCellLoadStart parameter is equalto 100 and the value of the fullHRCellLoadStartparameter is different from 100, it means that ABOT is not activated and AMR maximization is activated. Then a semantic control checks the fol-lowing: fullHRCellLoadStart > fullHRCellLoadEnd.

Checks: • [C/M]: If the value of the hrCellLoadStart parameter is different from 100 and the value of the fullHRCellLoadStart parameter is equal to 100, it means that ABOT is activated and AMR maximization is not acti-vated. Then a semantic control checks the following:hrCellLoadStart >= hrCellLoadEnd.• [C/M]: If the values of both hrCellLoadStart and fullHRCellLoadStart parameters are equal to 100, it means both AMR Based On Traffic (ABOT) and AMR maximization are not activated. No semantic control occurs.

Release: V14


411-9001-124 18.08 1.0 Page 191 of 446


hrPowerControlTargetMode Class 3

hrPowerControlTargetModeDl Class 3

hsaPcmList Class 3

Description: This attribute defines the target codec mode for AMR HRpower control.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’powerControl’ object instance is unlocked.

Value range: [HR 7.4 / HR 6.7 / HR 5.9 / HR4.75]


Default value: HR 7.4

Type: DP

Release: V14


Description: Downlink AMR codec target used to define the downlink power control threshold for HR AMR calls.

Value range: [HR 7.4 / HR 6.7 / HR 5.9 / HR 4.75]

Object: PowerControl

Type: DP


Default value: HR 7.4

Notes: This parameter applies to BSC 3000 V16 and higher.

Release: V16

Description: List of pcmCircuit object instances connected to a HSA.

Note: The class is 3 since some new pcmCircuits may be connected without stopping the HSA. Moreover, for a given port, the pcmCircuit may be re-placed provided that the old and new pcmCircuits are in the ’locked’ ad-ministrative State. The complete pcmCircuit list is always given. This attribute is monitored by the Manager. Value changes are notified to the Manager. This attribute can be modified only if the ’bsc’ object instance is unlocked. This attribute is relevant for BSC 3000 optical and TCU 3000 optical.This attribute has the following characteristics:pcmInstance, virtualPortNumber (not a physical port since it is multi-plexed in the optical fiber but it has the same idea as the portNumber in lsaRc) This parameter can also refer to new pcmSmlc.

Value range: [0 .. 83]

Object: iom, hsaRc, hsaRcTcu


Page 192 of 446 411-9001-124 18.08 1.0


hsaPcmList Class 3

hsaRc

2.10. I

identifier

Type: DP

Checks: • [C/M]: HsaRc under Bsc not possible for a non existing referenced Pc-mCircuit.• [C/M]: HsaRc under Transcoder not possible for a non existing refer-enced PcmCircuit.• [C/M]: HsaRc under Bsc not possible if a referenced pcmCircuit is al-ready referenced by another HsaRc.• [C/M]: HsaRc under Transcoder not possible if a referenced pcmCir-cuit is already referenced by another HsaRc.• [C/M]: Creation/Modification HsaRc under Transcoder is not possible for referenced PcmCircuit different than Ate r, A, A_Lb or Lb types.• [C/M]: A HSA under Transcoder module of E1 type handles 21 PCMs. The Ater referenced PcmCircuit are connected to port 0 through port 4 and the A, A _Lb and Lb referenced PcmCircuits are connected to port 5 through port 20.• [C/M]: A HSA under Transcoder module of T1 type handles 28 PCMs. The Ater referenced PcmCircuit are connected to port 0 through port 5 and the A, A _Lb and Lb’ referenced PcmCircuits are connected to port 6 through port 27.

Checks: • [D]: Not possible to delete a PcmCircuit under bsc, still referenced to a HsaRc.• [D]: Not possible to delete a PcmCircuit under transcoder, still refer-enced to a HsaRc.• [C/M]: LsaRc under Bsc not possible with two referenced PcmCircuits on the same port number.• [C/M]: HsaRc under Transcoder not possible with two referenced Pc-mCircuits on the same port number.• [C/M]: HsaRc not possible for shelf position and slot position already used.• [C/M]: L=HsaRc under Transcoder not possible for an A referenced Pc-mCircuit which is not defined under the same transcoder.• [C/M]: HsaRc under Transcoder not possible for an A referenced Pc-mCircuit with a port number equal to 0, 1, 2 or 3.• [C/M]: HsaRc under Transcoder is not possible for referenced PcmCir-cuit different than ’Ater’ or ’A’ type.[C/M]: The association between Pcm and port of LsaRc is incorrect.

Release: V17

Description: The High Speed Access Resource Complex module, which provides the optical interface for the OC3/STM1 interfaces.


Object: hsaRc

Type: DP

Description: Name of a BSS software application followed by its version number.Refer to the executableSoftware entry related to the software object in the Dictionary where the name formats are explained.

Value range: [XXXabcdef]


Type: DD

411-9001-124 18.08 1.0 Page 193 of 446


identifier

identifier

identifier

iem

iemId

Description: Name of a BSC database configuration file followed by its version num-ber.Refer to the executableSoftware entry related to the software object in the Dictionary where the name formats are explained.

Value range: [BSxabvcdefgh]

Object: software-bsc - Display markers

Type: DD

Description: Name of a BSC database configuration file followed by its version num-ber.Refer to the eft entry related to the software object in theDictionary where the name formats are explained.

Value range: [BSxabvcdefgh]

Object: software-bsc - Display markers

Type: DD

Description: Identifier of a short message. It allows MSs to identify the short message and discard it if already received.



Type: DD

Description: The Interface Electronic Module, is part of the LSA RC (Low Speed Ac-cess Resource Complex) module.


Object: iem

Type: DP

Note: V13

Description: Identifier of the ’iem’ object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000.


Object: iem

Type: DP

Release: V13

Page 194 of 446 411-9001-124 18.08 1.0


iMSIAttachDetach Class 2

in

inactivity timeout

inclusive interval of codano

inclusive interval of codano

Description: Whether MS attachment/detachment is allowed. Allowing enables the system to take into account temporary MS absence to prevent unsuc-cessful call attempts.

Value range: [allowed / not allowed]

Object: bts

Default value: allowed

Type: DP

Description: The Interface Node, which provides the network connectivity through PCM trunk or higher speed interfaces (OC-3 - Optical Carrier level 3 - or STM-1 - Synchronous Transport level 1) as well as the time switching capability.



Type: DP

Description: Maximum time between two user commands, over which the system in-duces an automatic logout procedure.

Value range: [2 to 2147483646] (5) minute


Type: DP

Remark: Moving the mouse inside an MMI window on the terminal screen resets the counter.

Description: To select messages according to their fault number. The filtering list can contain one (or several) interval(s). For example, interval 5~8 enables to retrieve fault numbers 15, 6, 7, and 8. Do not fill in if this criterion is not to be selected.

Value range: [0 to 65535 - 0 to 65535]


Type: DP

Release: V12

Description: To select messages according to their fault number. The filter can con-tain one (or several) fault number(s).Do not fill in if this criterion is not to be selected.



411-9001-124 18.08 1.0 Page 195 of 446


incomingHandOver Class 3

inhibitRequest

inId

ipAggregateEthernetPortMonitored

Type: DP

Release: V12

Description: Whether incoming handovers are allowed in a cell.




Type: DP

Description: Whether the SS7 channel is inhibited.


Object: signallingLink - Set inhibit

Type: DP

Checks: • [M]: The parent bsc object and the signallingLink object are unlocked.

Remark: An inhibit request may have no immediate effect and can even be re-fused. Run a Display all command on the signallingLink object to display the resource state of the SS7 channel and check that the system has applied the request (signallingLinkResState).

Description: Identifier of an ’ in’ object class. This identifier is allocated by the MD-R at object creation. The only value allocated by the MD-R is 0. This attri-bute cannot be modified.



Type: DP

Release: V13

Description: This parameter defines if some equipments are connected (directly or through gateways) on the aggregate Ethernet ports. It informs the BSC if it has to monitor or not the link on these 2 ports (on IGM0 and IGM1). It is used by Ethernet links supervision function inside BSC.

Value range: 0..65535

Object: ipgRc

Type: DP

Default value: 0

Release: V18.0

Page 196 of 446 411-9001-124 18.08 1.0


ipCompressionActivation Class 3

ipCompressionDepth Class 2

ipCRPnChannel_TosDscp Class 3

Description: Defines if the compression is used over the IP network.

Value range: [Not Used / Used]



Type: DP

Default value: Not Used

Release: V18.0

Description: Defines the compression depth which must be used. Has a direct impact on the RTD between the BSC and the IPM.

Value range: [20, 40, 60, 80, 100]

Unit: ms



Default value: 40

Recommended value:

40

Type: DP

Release: V18.0

Note: To modify this parameter, the ipm object must be locked.

Checks: • [C/M]: Before changing the ipCompressionDepth parameter, the OMC-R checks that the ipm object is locked.

Description: Defines the DSCP value that the BSC must set at the Layer 3 level for CRPn Channel. Corresponds to the 6 higher bits in the "Type Of Ser-vice" or “Differentiated Services” field in the IP header.The chosen value must be compliant with the type of domain (DS or TOS) which is available at provider network side.For example, if the type of domain is DS, 3 groups of values are defined in RFC 2474, 2475 and 3260 :• best effort PHB (DSCP 0):this value is not recommended.

• expedited forwarding (DSCP 46): value recommended for real-time packets (voice)

• assured forwarding (DSCP 10, 12, 14, 18, 20, 22, 26, 28, 30, 34, 36, 38): value recommended for packets which need to have a high level of delivery reliability

(if the type of domain is TOS, see RFC 791)


Object: ipgRc


411-9001-124 18.08 1.0 Page 197 of 446


ipCRPnChannel_userPriority Class 3

ipDefaultGateway Class 3

Default value: 46 (DSCP 46)

Recommended value:

46 (Expedited Forwarding PHB)

Type: DP

Release: V18.0



Description: Defines the priority that the BSC must set at the Layer 2 level for CRPn Channel. Meaningful only if VLAN tags (IEEE802.1Q) are used on the Abis backhaul. General recommendations are:• 0: best effort (not recommended)

• 1-4: business critical data

• 5-6: delay sensitive data

• 7: network control information (not to use)

The chosen value must be compliant with what is available at the pro-vider network side.


Object: ipgRc


Default value: 6

Recommended value:

5, 6

Type: DP

Release: V18.0



Description: Defines the IP address of the default Gateway. It is used by router func-tion inside the BSC.

Value range: Compliant with semantic check "IP addresses allowed values".

Object: ipgRc


Default value: Empty list

Recommended value:

Not applicable

Type: DP

Page 198 of 446 411-9001-124 18.08 1.0


ipDHCPServerList Class 3

Release: V18.0

Checks: [C/M]: A consistency check is done to verify if the IP address of the de-fault Gateway can be empty: in this case, the 0 value is sent to the BSC; otherwise the following checks are done:• address format: xx.yy.zz.tt, each value xx, yy, zz, tt is an integer in-

cluced in the range [0...255]

• address different from:

—0.0.0.0

—127.0.0.0 to 127.0.0.255 (local addresses)

—255.255.255.255 (broadcast address)

—224.0.0.0 to 239.255.255.255 (multicast addresses)

Description: Defines the list of IP addresses of the DHCP servers used on the system for IPM IP addresses definition. It is used by DHCP relay function inside the BSC.

Value range: List of up to 10 IP addresses, compliant with semantic check "IP ad-dresses allowed va ues"

Object: ipgRc



Type: DP

Release: V18.0

Checks: • [C/M]: Each IP address set inside the ipDHCPServerList parameter must be unique.

• [C/M]: A consistency check is done to verify if the IP address can be empty: in this case, the 0 value is sent to the BSC; otherwise the fol-lowing checks are done:

• address format: xx.yy.zz.tt, each value xx, yy, zz, tt is an integer in-cluced in the range [0...255]


—0.0.0.0

—127.0.0.0 to 127.0.0.255 (local addresses)

—255.255.255.255 (broadcast address)

—224.0.0.0 to 239.255.255.255 (multicast addresses)

411-9001-124 18.08 1.0 Page 199 of 446


ipgPcmList Class 3

ipgRc Reference

ipIBOSEthernetPortMonitored Class 3

Description: Defines the list of PCMs handled by the ipgRc (coming from S-links). Up to 84 PCMs can be created on T1 configurations and 63 PCMs in E1 configurations.

Value range: • bsc30000electrical_ip

– E1: 273 to 335

– T1: 364 to 447

• bsc 3000optical_ip

– E1: 273 to 293

– T1: 364 to 391

Object: ipgRc



Type: DP

Release: V18.0

Checks: • [C/M]: When a PCM is created on an IPG, the PCM type must be Abis. The pcmCircuitId range on the IPG is:

• [273, 293] for IPG RC E1

• [364, 391] for IPG RC T1

Description: Identifier of the ipgRc object.


Object: igm


Type: DP

Release: V18.0

Description: Defines if some equipments are connected (directly orthrough gateways) on the aggregate Ethernet ports. Informs the BSC if it must supervise or not the link on the IGM0 and IGM1 ports.It is used by the Ethernet links supervision function inside the BSC.

Value range: “Not Monitored” (0), “Monitored” (1)

Object: ipgRc


Type: DP

Release: V18.0

Page 200 of 446 411-9001-124 18.08 1.0


ipIBOSTraffic_TosDscp Class 3

ipIBOSTraffic_userPriority Class 3

Description: Defines the DSCP value that the BSC must set at the Layer 3 level for the traffic on the IBOS port. Corresponds to the 6 higher bits in the "Type Of Service" or “Differentiated Services” field in the IP header.The chosen value must be compliant with the type of domain (DS or TOS)which is available at provider network side.Three groups of values are defined in the RFC 2474, 2475 and 3260:• best effort PHB (DSCP 0) this value is not recommended.

• expedited forwarding (DSCP 46): value recommended for real-time packets (voice)

• assured forwarding (DSCP 10, 12, 14, 18, 20, 22, 26, 28, 30, 34, 36, 38): value recommended for packets which need to have a high level of delivery reliability

(if the type of domain is TOS, please see RFC 791).


Object: ipgRc


Default value: 10 (Assured Forwarding PHB)

Recommended value:

10, 12, 14, 18, 20, 22, 26, 28, 30, 34, 36, 38

Type: DP

Release: V18.0

Description: Defines the priority that the BSC must set at the Layer 2 level for the IPtraffic on the IBOS interface. Meaningful only if VLAN tags are used on the IBOS. General recommendations are:• 0: best effort (not recommended)

• 1-4: business critical data

• 5-6: delay sensitive data

• 7: network control information

The chosen value must be compliant with what is available at the provider network side.


Object: ipgRc


Default value: 4

Recommended value:

1, 2, 3, 4

Type: DP

Release: V18.0

411-9001-124 18.08 1.0 Page 201 of 446


ipLmuMatrix Class 3 (BSC 3000)

ipIpgRcCounterPeriod Class 3

bts

ipm MAC address Core A Class 3

Description: This parameter defines the matrix connection used for LMU feature. It provides the list of (Abis PCM,TS) (SMLC PCM,TS) (BTSSM id) interconnection which must be configured inside BSC in order to interconnect Timeslots on LMU PCM side with virtual IP timeslots on Abis IP interface. BTSSM id is present in order to resolve “PCM sharing issue”

Value range: [0 to 65535] for Abis PCM Number[0 to 255] for Abis TimeSlot Number[0 to 65535] for SMLC PCM Number[0 to 255] for SMLC TimeSlot Number[0 to 65535] for BTSSM id

Object: bsc



Type: DP

Release: P&C2

Description: Defines the periodicity for the counters collection inside the IGM.• 0 means no counter is collected inside the IPG

• other values means the IPG cyclically collects counters with the spec-ified period

Value range: [0 / 5 / 10 / 15 / 20 / 30 / 60]

Unit: min

Object: ipgRc


Default value: 15

Type: DP

Release: V18.0

Description: Identifier of an ipm object.

Value range: [1]

Object: ipm


Type: Id

Release: V18.0

Description: Defines the primary MAC address of the IPM / IPM-USER for the au-thentication

Value range: [0x000000000000...0xFFFFFFFFFFFF]

Page 202 of 446 411-9001-124 18.08 1.0


ipm MAC address Core B Class 3

ipPdvManualSet Class 2

ipPdvSelfTuningRange Class 2

Object: ipm


Type: DP

Release: V18.0

Checks: • [C/M]: No more than two IPMs with the same MAC address are al-lowed.

Description: Defines the secondary MAC address of the RIPM /RIPM-USER for the authentication.

Value range: [0x000000000000...0xFFFFFFFFFFFF]

Object: ipm


Type: DP

Release: V18.0

Checks: • [C/M]: No more than two IPMs with the same MAC address are al-lowed.

Description: If the automatic adjustment is not activated, this parameter defines the set which must be used.

Value range: [1...4] with:• 1: #1 must be used• 2: #2 must be used• 3: #3 must be used• 4: #4 must be used



Default value: 2

Type: DP

Release: V18.0


Checks: • [C/M]: Before changing the ipPdvManualSet parameter, the OMC-R checks that the ipm object is locked.

Description: If the automatic adjustment is activated, this parameter defines the list of allowed sets.Possible values : 1 to 15, with :Bit0 = #1Bit1 = #2Bit2 = #3Bit3 = #4Example : 7 means #1, #2 and #3 are allowed.



411-9001-124 18.08 1.0 Page 203 of 446


ipPortAddress Class 3


Default value: 7

Type: DP

Release: V18.0


Checks: • [C/M]: Before changing the ipPdvSelfTuningRange parameter, the OMC-R checks that the ipm object is locked.

Description: Defines the list of IP addresses used on each Ethernet interface (IBOS, Aggregate port, Abis):• only one entry can be defined on the IBOS port• only one entry can be defined on the Aggregate port• several entries can be defined on the Abis port

Value range: Up to 394 entries can be defined.The values are presented in a table with six columns:• PortIPAddressOnIGM0 column: compliant with semantic check "IP addresses allowed values"• PortIPAddressOnIGM1 : empty (not used in V18.0) – not visible at OMC-R• Mask column: compliant with semantic check "IP addresses allowed values" and compliant with syntaxic check "IP Mask allowed values"• VLAN column: 0 to 4092 (0 means no VLAN tag is inserted in the Ether-net frame• VRId column: 1 to 255• Interface 0, 1, 2 which corresponds to Abis (0), IBOS (1), Aggregate (2)

Object: ipgRc



Type: DP

Release: V18.0

Checks: • [C/M]: The maximum number of Abis entries with the same VRId in-side the table of the ipPortIPaddress_VRId_List parameter is 255.

• [C/M]: Only one entry can be defined with the IBOS interface inside the table of the ipPortIPaddress_VRId_List parameter.

• [C/M]: Only one entry can be defined with the Aggregate interface inside the table of the ipPortIPaddress_VRId_List parameter.

• [C/M]: The IP address defined in the PortIPAddressOnIGM0 column must not belong to a subnet already defined in the table (all the sub-nets are known by applying, for each line, the mask and the IGM0 IP address).

• [C/M]: The IP address defined in the PortIPAddressOnIGM0 column must not belong to a subnet already defined inside the ipRoutingTable parameter of the ipgRc object.

Page 204 of 446 411-9001-124 18.08 1.0


ipRedundancyProtocolOnAbisPort Class 3

ipRedundancyProtocolOnAggregatePort Class 3

• [C/M]: A consistency check is done to verify if the IP address set in the PortIPAddressOnIGM0 column and in the Mask column can be empty: in this case, the 0 value is sent to the BSC; otherwise the fol-lowing checks are done:

• address format: xx.yy.zz.tt, each value xx, yy, zz, tt is an integer in-cluded in the range [0...255]


– 0.0.0.0

– 127.0.0.0 to 127.0.0.255 (local addresses)

– 255.255.255.255 (broadcast address)

– 224.0.0.0 to 239.255.255.255 (multicast addresses)

• [C/M]: The following syntaxic checks are performed on the Mask col-umn of the ipPortIPaddress_VRId_List parameter:

• all the bits set to 1 in the mask must be contiguous

• all the bits set to 1 must be aligned on the left part of the mask

Example:The following value is allowed: 255.255.240.0(11111111.11111111.11110000.00000000).Example:The following values are not allowed:• 63.255.255.240 (00111111.1111.....)• 255.240.255.0 (11111111.11110000.111 11111.0)

Description: Defines the protocol used on the Abis ports to aggregate the IP and MAC addresses. It is used by the Ethernet redundancy function inside the BSC.


Object: ipgRc


Default value: 0

Type: DP

Release: V18.0

Description: Defines the protocol used on the aggregate ports to aggregate the IP and MAC addresses. It is used by the Ethernet redundancy function in-side the BSC.


Object: ipgRc


Default value: 0

411-9001-124 18.08 1.0 Page 205 of 446


ipRedundancyProtocolOnIBOSPort Class 3

ipRoutingProtocolOnAggregatePort Class 3

ipRoutingProtocolOnIBOSPort Class 3

ipRoutingTable Class 3

Type: DP

Release: V18.0

Description: Defines the protocol used on the IBOS ports to aggregate the IP and MAC addresses. It is used by the Ethernet redundancy function inside the BSC.


Object: ipgRc


Default value: 0

Type: DP

Release: V18.0

Description: Defines the protocol used to provide external gateways on the aggregate port with the routing tables known by the ipgRc. It is used by the router function inside the BSC.

Value range: static

Object: ipgRc


Default value: static

Type: DP

Release: V18.0

Description: Defines the protocol used to provide external gateways on the IBOS port with the routing tables known by the ipgRc. It is used by the router func-tion inside the BSC.

Value range: static

Object: ipgRc


Default value: static

Type: DP

Release: V18.0

Description: Defines the IP routing table. Up to 410 entries can be defined. It is used by router function inside the BSC.

Value range: Each entry is made of 3 attributes:• subnet: compliant with semantic check "IP addresses allowed values"• Mask: compliant with semantic check "IP addresses allowed values" and compliant with semantic check "IP Mask allowed values"• nextHopRouter: compliant with semantic check "IP addresses al-lowed values"

Page 206 of 446 411-9001-124 18.08 1.0


ipRTPnChannel_TosDscp Class 3

Object: ipgRc



Type: DP

Release: V18.0

Checks: • [C/M]: A subnet in the ipRoutingTable parameter must be unique.• [C/M]: The subnet set in the ipRoutingTable parameter must not have already been set in the list of subnets declared in the ipPortIPaddress_VRId_List para eter (all the subnets are known by applying, for each line, the mask and the IGM0 IP address).• [C/M]: The IP address in the nextHopRouter column of the ipRouting-Table parameter mustbelong to one of the subnets declared in the ipPortIPaddress_VRId_List parameter (all the subnets are known by applying, for eachline, the mask and the IGM0 IP address).• [C/M]: A consistency check is done to verify if the IP address set in the subnet, Mask and nextHopRouter columns can be empty: in this case, the 0 value is sent to the BSC; otherwise the following checks are done:• address format: xx.yy.zz.tt, each value xx, yy, zz, tt is an integer inclu-ced in the range [0...255]• address different from: — 0.0.0.0 — 127.0.0.0 to 127.0.0.255 (local addresses) — 255.255.255.255 (broadcast address) — 224.0.0.0 to 239.255.255.255 (multicast addresses)

• [C/M]: The following syntaxic checks are performed on the Mask col-umn of the ipRoutingTable:• all the bits set to 1 in the mask must be contiguous• all the bits set to 1 must be aligned on the left part of the maskThe following value is allowed:255.255.240.0(11111111.11111111.11110000.00000000).The following values are not allowed:• 63.255.255.240(00111111.1111.....)• 255.240.255.0(11111111.11110000.11111111.0)

Description: Defines the DSCP value that the BSC must set at the Layer 3 level for RTPn Channel. Corresponds to the 6 higher bits in the "Type Of Service" or“Differentiated Services” field in the IP header and must be compliant with the values defined in RFC2474, RFC2475, and RFC3260.Three groups of values are defined in these RFCs:• best effort PHB (DSCP 0)• expedited forwarding (DSCP 46): value recommended for real-time packets• assured forwarding (DSCP 10, 12, 14, 18, 20, 22, 26, 28, 30, 34, 36, 38): value recommended for packets which need to have a high level of delivery reliabilityThe chosen value must be compliant with what is available at the pro-vider network side.(if the type of domain is TOS, see RFC 791)


Object: ipgRc


Default value: 46

Recommended value:

46

411-9001-124 18.08 1.0 Page 207 of 446


ipRTPnChannel_userPriority Class 3

IPSEC Payload Class 3

ipSelfTuning Class 2

Type: DP

Release: V18.0

Description: Defines the priority that the BSC must set at the Layer 2 level for RTPn Channel. Meaningful only if VLAN tags are used on the Abis backhaul. General recommendations are:• 0: best effort (not recommended)• 1-4: business critical data• 5-6: delay sensitive data• 7: network control informationThe chosen value must be compliant with what is available at the pro-vider network side.


Object: ipgRc


Default value: 6

Recommended value:

5, 6

Type: DP

Release: V18.0

Description: Set through the SET command with the warning about the reset being mandatory.

Value range: [Not Ciphered / Ciphered with AES-CBC 128bits]

Object: ipm


Default value: Ciphered with AES-CBC 128bits

Type: DP

Release: V18.0

Description: defines if automatic adjustment is used for PDV and compression peri-od.IPM must be locked to modify this parameter.

Value range: 0, 1


Feature: Abis over IP

Default value: 0

Recommended value:

0

Type: DP

Release: V18.0

Page 208 of 446 411-9001-124 18.08 1.0


ipServiceChannel_TosDscp

ipServiceChannel_userPriority Class 3

Description: This parameter defines the 6 higher bits in the “Type Of Service” or “Dif-ferentiated Services” Field in the IP header, which must be set by BSC atLayer 3 level for Service Channel on Abis port. When IBOS is connected onAbis port, it also applies to IGM/IBOS service channel The chosen value must be compliant with the type of domain (DS or TOS)which is available at provider network side.For example, if the type of domain is DS, 3 groups of values are defined in RFC 2474, 2475 and 3260 :• Best Effort PHB (DSCP 0): this value is not recommended.

• Expedited Forwarding (DSCP 46): this value is recommended for real time packets (voice)

• Assured Forwarding (DSCP 10,12,14,18,20,22,26,28,30,34,36,38): this value is recommended for packets which need to have a high lev-el of delivery reliability.

(if the type of domain is TOS, see RFC 791)

Value range: 0..63

Object: ipgRc


Default value: 10 (Assured Forwarding PHB)

Recommended value:

10, 12, 14, 18, 20, 22, 26, 28, 30, 34, 36, 38

Type: DP

Release: V18.0

Description: Defines the priority that the BSC must set at the Layer 2 level for Service Channel. Meaningful only if VLAN tags are used on the Abis backhaul.• 0: best effort (not recommended)• 1-4: business critical data• 5-6: delay sensitive data• 7: network control informationThe chosen value must be compliant with what is available at the pro-vider network side.


Object: ipgRc


Default value: 4

Recommended value:

1, 2, 3, 4

Type: DP

Release: V18.0

411-9001-124 18.08 1.0 Page 209 of 446


ipSynchroPacketPeriod Class 2

ipSynchroType Class 2

ipSynchroUplinkActivation Class 2

ipTrafficPacketPeriod Class 2

Description: Defines the period between two clock synchronization packets sent to the IPM (DL mode) or to the IPG (UL mode).

Value range: 21

Object: ms


Default value: 21

Recommended value:

21

Type: DP

Release: V18.0

Checks: • [C/M]: Before changing the ipSy chroPacketPeriod parameter, the OMC-R checks that the ipm object is locked.

Description: defines the clock synchronization source used at IPM level.IPM must be locked to modify this parameter.

Value range: 0..2



Default value: 0

Recommended value:

Not applicable

Type: DP

Release: V18.0

Description: Defines if the uplink traffic for the IPM clock synchronization is activated or not activated..

Value range: [Not activated]



Default value: Not activated

Recommended value:

Not activated

Type: DP

Release: V18.0

Checks: • [C/M]: Before changing the ipSynchroUplinkActivation parameter, the OMC-R checks that the ipm object is locked.

Description: Defines the period between two RTPn IP packets.

Value range: [4]

Page 210 of 446 411-9001-124 18.08 1.0


2.11. J

job

jobResult

jokerPerMainTarget Class 3

Unit: ms



Default value: 4

Type: DP

Release: V18.0


Checks: • [C/M]: Before changing the ipTrafficPacketPeriod parameter, the OMC-R checks that the ipm object is locked.

Description: Identifier (name) of a job on the OMC-R.

Value range: [case sensitive, unlimited number of characters]. The . and / characters are forbidden.

Object: job

Type: Id

Checks: • [M/D]: The job is created on the OMC-R.

Description: Identifier (name) of the associated job on the OMC-R. A results file stores the commands executed and the system responses to those commands during the associated job successive runs, beginning with the first run.


Object: jobResult

Type: Id

Description: Target number of joker AGPRS 16 kbit/s TSs to be assigned by both BSC and PCU to every main AGPRS 16 kbit/s TS (that is to every PDTCH linked with AGPRS).

Value range: 0 to 4

Object: transceiver


Default value: 0

Type: DP

411-9001-124 18.08 1.0 Page 211 of 446


2.12. L

label

language

lapdLink

Notes: • The recommended values are 2, 3 or 4, depending on operator Abis configuration (numberOfJokerDS0) and estimated EDGE TDMA throughput.• Even if jokerPerMainTarget is a class 3 parameter, new values will not be immediately taken into account. The parameter will be used by BSC or PCU at the next AGPRS reconfiguration (when a TDMA_TS_STATUS message is sent from BSC to PCU) or when the PCU protection timer expires (agprsTsSharingProtection, internal timer set to 10s).

Release: V15

Description: Label of an archive cartridge.When a label is set, all information already stored on thecartridge is lost.


Object: md, omc - Display labelmd, omc - Set labelmd, omc - Archivemd, omc - Restoremd, omc - Display archive list.

Type: DP

Description: Language in which a short message is broadcasted. The information is used in the data coding scheme when the short message is broadcast-ed.

Value range: [German / English / Italian / French / Spanish / Dutch / Swedish / Danish / Portuguese / Finnish / Norwegian / Greek / Turkish / Hungarian / Polish / unspecified / Multi Byte Character Set]


Type: DP

Description: Identifier of a lapdLink object defined with regard to a bsc object.In all MMI commands, a LAPD link can be referenced by "bscName.lap-dLink" where bscName is a permanent attribute of the parent bsc object that identifies it by name.


Object: lapdLink

Type: Id

Page 212 of 446 411-9001-124 18.08 1.0


lapdLinkOMLRef Class 2

lapdLinkOMLRef Class 2

Checks: • [C]: The number of LAPD links per BSC is limited to 841. Fourteen links can be assigned to the TCUs on the Ater interface or to the PCU on the Agprs interface, 147 links can be assigned to the radio sites on the Abis interface, and the remaining links can be assigned to the TRX/DRXs on the Abis interface, with two links per TRX/DRX.• [C]: The software object related to the parent bsc object is created.• [C]: The number of lapdLlink objects dependent on the same bsc ob-ject that use the same lapdTerminalNumber is limited to maxTeiPer-LapdCh (static configuration data).• [C]:• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked.

• [D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.• [D]: No btsSiteManager, transceiverEquipment, or transcoder objects refer to the lapdLink object.

Remark: A lapdLink object has no administrativeState of its own; its operational-State depends on the administrativeState of the parent bsc object.

Description: Identifier of the lapdLink object with sapi = OML referenced by the btsSiteManager object.



Type: DP

Checks: • [C/M]:• [C/M]: The number of objects dependent on a bsc object that refer to lapdLink objects using the same lapdTerminalNumber is limited to maxTeiPerLapdCh (static configuration data).• [C]: The number of LAPD channels used by a site and the related TRX/DRXs is limited to maxLapdChPerBtsSM (static configurationdata).• [C/M]: If the lapdLink object lapdConcent ration attribute value is "en-abled", the defined lapdTerminalNumber is used by no more than four btsSiteManager objects dependent on the same bsc object.• [C/M]: If the lapdLink object ladConcent rationattribute value is "disabled", the definedlapdTerminalNumber is not used.

Description: Identifier of the lapdLink object with sapi = OML referenced by the trans-ceiverEquipment object.



Type: DP

Checks: • [C]: The number of LAPD channels used by a site and its related TRX/DRXs is limited to maxLapdChPerBtsSM (static configuration data).• [C/M]:• [C/M]: The number of btsSiteManager and transceiverEquipment ob-jects dependent on a bsc object that refer to lapdLink objects using the same lapdTerminalNumber is limited to maxTeiPerLapdCh (static configuration data).• [M]: The parent bsc object is unlocked, the parent btsSiteManager ob-ject and the transceiverEquipment object are locked.

411-9001-124 18.08 1.0 Page 213 of 446


lapdLinkRSLRef Class 2

lapdTerminalNumber Class 0

Description: Identifier of the lapdLink object with sapi = RSL referenced by the trans-ceiverEquipment object.



Type: DP

Checks: • [C]: The number of LAPD channels used by a site and its related TRX/DRXs is limited to maxLapdChPerBtsSM (static configurationdata).• [C/M]:• [C/M]: The number of btsSiteManager and transceiverEquipment ob-jects dependent on a bsc object that refer to lapdLink objects using the same lapdTerminalNumber is limited to maxTeiPerLapdCh (static configuration data).• [M]: The parent bsc object is unlocked, the parent btsSiteManager ob-ject and the transceiverEquipment object are locked.

Description: BSC SICD port assigned to the LAPD link. For more information on the use of this parameter, refer to GSM BSS Engineering Rules, 411-9001-138.

lapdTerninalNumber = 4 x number of the mother SICD4 board [0 to 9] + port number [0 to 3]lapdTerninalNumber = 8 x number of the mother SICD8board [0 to 4] + port number [0 to 7]

Value range: [0 to 7] (BSC type 1)[0 to 15] (BSC type 2)[0 to 23] (BSC type 3)[0 to 31] (BSC type 4)[0 to 39] (BSC type 5)[0 to 254] (BSC 3000)

Object: lapdLink

Default value:


Type: DP

Checks: • [C/M]: The number of SICD ports in a BSC depends on its type, know-ing that a SICD board manages four ports and a SICD8V board manag-es eight ports.

BSC type T1 T2 T3 T4 T5

SICD ports 8 16 24 32 40

Page 214 of 446 411-9001-124 18.08 1.0


layer3MsgCyphModComp Class 1

lcsType Class 0

level to process

• [M]: If the port is used by an Abis interface LAPD link, it cannot be used for TCU and PCU signaling.• [M]: If the port is used by an Ater interface LAPD link, it cannot be used for BTS and PCU signaling.• [M]: If the port is used by an Agprs interface LAPD link, it cannot be used for BTS and TCU signaling.• [M]: The number of btsSiteManager and transceiverEquipment ob-jects dependent on a bsc object that refer to lapdLink objects using the same lapdTerminalNumber is limited to maxTeiPerLapdCh (static configuration data).

Description: Whether the "Layer 3 message" element is used in the CYPHER MODE COMPLETE messages (Phase II compliance).




Type: DP

Release: V8

Description: MS Location technical solution to use.

Value range: [nss based / bss based] According to the BSC version:

Object: bsc

Type: DP

Note: This parameter is mandatory. It is only available for BSC 3000.

Checks: • [M]: If the value of lcsType is bss based then two signallingLinkSet instances must be created and at least one signallingLink must be cre-ated for the Lb interface - signallingLinkSet(1).• [M]: If the value of lcsType is nss based then only one signallingLink-Set instance must exist and be equal to 0.• [M]: If the value of lcsType is tandem hybrid then only one signallin-gLinkSet instance must exist and be equal to 0.

Release: V14

Description: Identifier of a set of SDO resultant data files. Level 1 identifies the latest set produced by the SDO machine.As many as three sets of resultant data files created from the same work-station can exist in the SDO machine. Any one can be selected for report display or purge purposes.

Value range: [1, 2, 3]

Object: Call monitoring - Display/Management) (SDO)

Type: DP

Checks: • [A]: The set of files exists in the SDO machine.

411-9001-124 18.08 1.0 Page 215 of 446


Licenses needed to put object in service

Licenses used by this object

lightning protection Class 2

line

Description: Number of licenses required to Build BDA on the bsc object or to unlock the btsSiteManager object.The parameter is equal to 0 if the BDA is already built or if the btsSiteM-anager object is already unlocked.

Value range: [0..NNNN] (The range depends on the number of licenses configured, used in total and on certain objects)

Object: md - Display RM capacitybsc - Display RM capacitybtsSiteManager - Display RM capacity

Feature: AMR Feature Activation ControlEDGE Feature Activation Control

Release: V17

Description: Number of licenses (RM Capacity) used by the object (bsc or btsSiteM-anager).The parameter is equal to 0 if the bsc object is not build or if the btsSiteManager object is locked.


Object: md - Display RM capacitybsc - Display RM capacitybtsSiteManager - Display RM capacity


Release: V17

Description: Presence or absence of the optional equipment "lightning arrester" in S8000 Outdoor.



Type: DP

Release: V9

Description: Line number of the first command to run (default is 1).Every command in a command file is assigned a line number. Line no.1 corresponds to the first recordedcommand, line no.n corresponds to the last recorded command.


Object: commandFile - Run

Type: DP

Page 216 of 446 411-9001-124 18.08 1.0


locationAreaCode Class 3



locationAreaCodeUTRAN Class 3

Description: Code of a location area of the neighbor cell in the PLMN.



Type: DP


Description: Code of a location area of the neighbor cell in the PLMN.



Type: DP


Description: Code of a location area in the PLMN.A CGI (Cell Global Identifier) is unique in a location area. It identifies a cell in the PLMN and includes four fields: cellIdentity (CI), locationAr-eaCode (LAC), mobileCountryCode (MCC), and mobileNetwork-Code (MNC).


Object: bts

Type: DP


Description: Location area code (LAC) of the UMTS neighbouring cell for HO

Value range: 0...65535


Default value: N.A.

Type: DP

Release: V17


411-9001-124 18.08 1.0 Page 217 of 446


log

logFullAction

logicalFiberInfo

Description: Identifier of a log object defined with regard to the md object. It is as-signed by the OMC-R agent.The current alarm log is no.1. Current observations logs are created in ascending numerical order each time a new mdScanner object is creat-ed. Current trace logs are created in ascending numerical order each time a new callPathTrace or traceControl object is created.A restored log is created each time a Restore command on the md ob-ject related to faults, observations, or trace data is run.


Object: log

Type: Id

Checks: • (on observation and trace logs)• [D]: The observation or the associated trace function is stopped.

Restrictions: • [D]: The log object describing the current alarm log can-not be deleted.

Notes: • The log objects are created by the OMC-R agent and can be deleted by users under certain conditions (see above).• The attributes of the log objects are not managed by users.

Description: Action taken by the OMC-R agent in case of storage directory capacity threshold overflow.The value "wrap" means that messages may be purged; the value "halt" means that further messages are not saved. Refer to the capacityAlar-mThreshold entry in the Dictionary.

Value range: [wrap (alarm log) / halt (observation or trace log)]


Type: DP

Note: The attributes of the log objects are not managed by users.

Description: Logical fiber and crossover info. List of four values:• fiberRxState: either the state of the RX fiber on the active CEM or the state of the crossover RX used by the active CEM• fiberTxState: either the state of the TX fiber on the active CEM or both the state of the crossover TX and TX fiber on the passive CEM• crossoverRx indicates if the crossover is used for the reception• crossoverTx indicates if the crossover is used for the transmission The Undefined value means that the TCU or the Interface Node is not reachable.

Value range: List of logicalFiberInfo descriptions [[fiberRxState, fiberTxState, cross-overRx, crossoverTx], with:• fiberRxState: NotUsed / OK / KO / Unde-fined• fiberTxState: NotUsed / OK / KO / Undefined• crossoverRx: NotUsed / OK / KO / Undefined• crossoverTx: NotUsed / OK / KO / Undefined

Object: cemRc

Type: DD

Feature: Optical BSC/TCU High Capacity 4K

Release: V18.0

Page 218 of 446 411-9001-124 18.08 1.0


login command type

longTbfLossThroughput Class 3

longTbfSizeThreshold Class 3

lRxLevDLH Class 3

lRxLevDLP Class 3

Description: Select login and user profile

Value range: [login request, server update]


Description: Loss of throughput for long TBF in percentage of allocated bandwidth. Prioritize normal transfer over long data transfer.

Value range: [0 to 100] in %

Object: bts


Default value: 0

Type: DP

Release: V12

Description: Threshold for long TBF size, in Kbytes. This parameter is used in the functionality which penalizes long TBF.


Object: bts


Default value: 100

Type: DP

Release: V12

Description: Signal strength threshold in BTS-to-MS direction, below which a hando-ver may be triggered.

Value range: [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB


Default value: -101 to -100 dB (GSM 900 and GSM 850)-99 to -98 dB (GSM1800/1900)

Type: DP

Description: Signal strength threshold in BTS-to-MS direction, below which the pow-er control function increases power. .




Type: DP

411-9001-124 18.08 1.0 Page 219 of 446


lRxLevULH Class 3

lRxLevULP Class 3

lRxQualDLH Class 3

lRxQualDLP Class 3

lRxQualULH Class 3

Description: Signal strength threshold in MS-to-BTS direction, below which a hando-ver may be triggered.



Default value: -101 to -100 dB (GSM 900 and GSM 850) -99 to -98 dB (GSM 1800/1900)

Type: DP

Description: Signal strength threshold in MS-to-BTS direction, below which the power control function increases power. It is lower than uRxLevULP.




Type: DP

Description: Bit error rate threshold in BTS-to-MS direction, above which an inter cell handover may be triggered.

Value range: [less than 0.2, 0.2 to 0.4, 0.4 to 0.8, ... , 6.4 to 12.8, more than 12.8] %


Feature: Intracell handover enhancements (TF819 - V12)

Default value: 1.6 to 3.2 %

Type: DP

Description: Bit error rate threshold in BTS-to-MS direction, above which the power control function increases power. It is greater than or equal to uRxQual-DLP.



Default value: 0.4 to 0.8

Type: DP

Checks: • [C/M]: lRxQualDLP uRxQualDLP

Note: The uRxQualDLP parameter is ignored when the BTS uses the ad-vanced "one shot" power control algorithm.

Description: Bit error rate threshold in MS-to-BTS direction, above which an inter cell handover may be triggered.


Page 220 of 446 411-9001-124 18.08 1.0


lRxQualULP Class 3

lsaPcmList Class 3



Feature: Intracell handover enhancements (TF819 - V12)

Type: DP

Description: Bit error rate threshold in MS-to-BTS direction, above which the power control function increases power. It is greater than or equal to uRxQua-lULP.




Type: DP

Checks: • [C/M]: lRxQualULP uRxQualULP

Note: The uRxQualULP parameter is ignored when the BTS uses the advanced "one shot" power control algorithm.

Description: List of pcmCircuit object instances connected to a LSA.

Note: The class is 3 since some new pcmCircuits may be connected without stopping the LSA. Moreover, for a given port, the pcmCircuit may be re-placed provided that the old and new pcmCircuits are in the ’locked’ ad-ministrative State.The complete pcmCircuit list is always given. This attribute is monitored by the Manager. Value changes are notified to the Manager. This attri-bute can be modified only if the ’bsc’ object instance is unlocked.This attribute is relevant for 3G BSC and 3G TCU. This parameter can also refer to new pcmSmlc.


Object: iem, lsaRc


Type: DP

Checks: • [C/M]: LsaRc under Bsc not possible for a non existing referenced Pc-mCircuit.• [C/M]: LsaRc under Transcoder not possible for a non existing refer-enced PcmCircuit.• [C/M]: LsaRc under Bsc not possible if a referenced pcmCircuit is al-ready referenced by another LsaRc.• [C/M]: LsaRc under Transcoder not possible if a referenced pcmCir-cuit is already referenced by another LsaRc.• [C/M]: Creation/Modification LsaRc under Transcoder is not possible for referenced PcmCircuit different than Ate r, A, A_Lb or Lb types.• [C/M]: A LSA under Transcoder module of E1 type handles 21 PCMs. The Ater referenced PcmCircuit are connected to port 0 through port 4 and the A, A _Lb and Lb referenced PcmCircuits are connected to port 5 through port 20.

411-9001-124 18.08 1.0 Page 221 of 446


lsaRc

lsaRcId

lsaRc Reference

2.13. M

• [C/M]: A LSA under Transcoder module of T1 type handles 28 PCMs. The Ater referenced PcmCircuit are connected to port 0 through port 5 and the A, A _Lb and Lb’ referenced PcmCircuits are connected to port 6 through port 27.• [D]: Not possible to delete a PcmCircuit under bsc, still referenced to a LsaRc.• [D]: Not possible to delete a PcmCircuit under transcoder, still refer-enced to a LsaRc.• [C/M]: LsaRc under Bsc not possible with two referenced PcmCircuits on the same port number.• [C/M]: LsaRc under Transcoder not possible with two referenced Pc-mCircuits on the same port number.• [C/M]: LsaRc not possible for shelf position and slot position already used.

• [C/M]: LsaRc under Transcoder not possible for an A referenced Pc-mCircuit which is not defined under the same transcoder.• [C/M]: LsaRc under Transcoder not possible for an A referenced Pc-mCircuit with a port number equal to 0, 1, 2 or 3.• [C/M]: LsaRc under Transcoder is not possible for referenced PcmCir-cuit different than ’Ater’ or ’A’ type. [C/M]: The association between Pcm and port of LsaRc is incorrect.

Release: V13

Description: The Low Speed Access Resource Complex module, which provides the electrical interface for the DS1 (Digital Signal level 1) or PCM30 interfac-es.


Object: lsaRc

Type: DP

Description: Identifier of the ’lsaRc’ object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000.


Object: lsaRc

Type: DP

Release: V13

Description: Pointer to the associated ’lsaRc’ object instance. This attribute cannot be modified. It is set at ’iem’ creation as indicated by the BSS.


Object: iem


Release: V13

Page 222 of 446 411-9001-124 18.08 1.0


machine name

machine name

mainNetworkBand Class 0

mainNetworkBand Class 0

Description: Name of the machine (terminal or server), as defined in its profile for a terminal, in which the job is run (default is the logged-in user’s terminal). Enter "server" for the OMC-R server console.


Object: job

Type: DP

Checks: • [C/M]: The machine is authrized to run jobs.

Note: Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (such as TRX, BSC, BTS, BTSSM). All other symbols/characters are prohibited.

Description: Name of the machine, as defined in its profile for a terminal, in which the associated job was run ("server" identifies the OMC-R server).

Object: jobResult

Type: DD

Note: Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (such as TRX, BSC, BTS, BTSSM). All other symbols/characters are prohibied.

Description: Indicates the main network band.

Object: jobResult

Type: DD


Description: Indicates the main network band.

Value range: [900/1800/850/1900] network band

Object: bsc

Type: DP

Release: V15

411-9001-124 18.08 1.0 Page 223 of 446


maio Class 2

managedObjectClass

managedObjectInstance

manager address type

Description: Index in the list of frequencies allotted to a radio time slot which obeys frequency hopping laws.Setting this attribute, together with the fhsRef attribute, allows the time slot to obey frequency hopping laws.This offset allows to differentiate channel objects that reference frequen-cyHoppingSystem objects with identical attributes (orthogonality princi-ple).

Value range: [0 to N-1] N is the number of frequencies (64) allotted to the time slot.

Object: channel

Type: DP

Checks: • [C/M]: The attribute is in the range [0 to 63].• [C/M]: It is undefined if frequency hopping is not allowed for the parent bts object (btsIsHopping = "no hopping") or the channelType of the channel object is "mainBCCH", "mainBCCHCombined", or "bcchSdcch4CBCH".• [C/M]: If the attribute is defined, the fhsRef attribute is also defined.• [C/M]: If the attribute is defined, its value is lower than the number of frequencies defined in the mobile Allocation list (attribute of the refer-enced frequencyHoppingSystem object).

Description: Object class referenced.

Value range: [adjacentCellHandOver / adjacentCellReselection / bsc / bscMdInter-face / bts / btsSiteManager /callPathTrace / channel / efd / frequency-HoppingSystem / handOverControl / lapdLink / log / md / mdScanner / mdWarning / pcmCircuit / powerControl / signallingLink / signallingLink-Set / signallingPoint / software / traceControl / transceiver / transceiv-erEquipment / transceiverZone / transcoder / xtp]

Object: alarmRecord, mdScanReportRecord, observationFileReady Record, stateChangeRecord, traceFileReadyRecord, traceLogRecord.

Type: DP

Description: Identification of an object in the class.

Object: alarmRecord, mdScanReportRecord, observationFileReadyRecord, stateChangeRecord, traceFileReadyRecord, traceLogRecord.

Type: DP

Description: OMC-R manager address type

Value range: [internal / external]


Type: DP

Checks: • [C/M]: This attribute is not managed by users.

Page 224 of 446 411-9001-124 18.08 1.0


manager addresses

managerServer

manufacturerIntervention

marking type

masterBtsSMId class 2

Description: Addresses of the OMC-R manager that receives the messages. They are provided by the manager.


Type: DP


Description: Name of the active OMC-R agent server. It is provided by the OMC-R agent.This server is referred to as the "NMC" server in the Q3 names of the permanent md observation counters related to the OMC-R agent active server.


Type: DP

Description: Type of action associated with an alarm criterion in the manufacturer configuration.



Type: DP

Description: Type of software to consult.Selecting "prom" allows to display the software applications loaded in PROMs in the selected BSS entity. Selecting "soft" allows to display the software applications loaded in the processors of the selected BSS en-tity.

Value range: [prom / soft]


Type: DP

Description: When its value is not empty, this parameter identifies the master BTS (for synchronization purpose).


Value range: [0 to 499 or empty]

Type: DP

Feature: BTS Synchronization

Default value: empty

Release: V15


411-9001-124 18.08 1.0 Page 225 of 446


max log size

maxAdjCHOARMPerBts

maxBscPerNetwork

maxBsTransmitPowerInnerZone Class 3

maxBtsPerBtsSM

Description: Maximum log size expressed in bytes.


Type: DP

Remark: The attributes of the log objects are not managed by the users.

Description: Maximum number of neighbor cells associated with a serving cell for handover and re-selection management (static OMC-R configuration data).

Value range: [32]

Object: OMC-R

Type: DS

Description: Maximum number of BSCs handled by an OMC-R (static OMC-R con-figuration data).

Value range: [20]

Object: OMC-R

Type: DS

Description: Maximum level of BTS transmission power in the inner zone of a dual-band cell.


Object: bts


Default value: 2

Type: DP

Release: V12

Description: Maximum number of radio cells controlled by a site (static OMC-R con-figuration data).

Value range: [6 (BTS "conventional") / 4 (others)]

Object: OMC-R

Type: DS

Page 226 of 446 411-9001-124 18.08 1.0


maxBtsPerNetwork

maxDnTbfP1P2Threshold Class 3

maxDnTbfPerTs Class 3

maxDwAssign Class 3

maxFileSize Class 2

Description: Maximum number of radio cells controlled by an OMC-R (static OMC-R configuration data).

Value range: [3200]

Object: OMC-R

Type: DS

Description: Maximum number of downlink TBF on a P1 TDMA before selection of P2 TDMA.


Object: bts


Default value: 16

Release: V12

Description: Maximum number of downlink TBF per TDMA on a timeslot basis.


Object: bts


Default value: 8

Type: DP

Release: V12

Description: Maximum number of Immediate Assignment messages per second.

Value range: [1 to 32] blocks

Object: bts


Default value: 8

Type: DP

Release: V12

Note: Because no TS partitioning is implemented in GPRS V12.4 b release, the number of maximum TBF establishment cannot exceed the number of TS configured in the cell. Recommended value has to be set to the number of PDTCH configured in the cell.

Description: Maximum size of the call path tracing data file in the BSC.

Value range: [30 to 500] kbit/s

411-9001-124 18.08 1.0 Page 227 of 446


maximum acknowledgment time

maximum alarm number

maximum clear time

maximum event time


Type: DP

Checks: • [M]: The callPathTrace object islocked.

Notes: • If trace data collecting is stopped by locking the object, the BSC con-tinues to send the current trace messages to the OMC-R agent, but no notifications are issued.• If trace data collecting is stopped by locking the object or on reaching the end-of-session criterion, it is automatically restarted whenever the callPathTrace object is unlocked. For instance, if the end-of-session cri-terion defines a period of time that elapsed, data collecting will restart for the entire period.

Description: To select messages acknowledged at that time or before. Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Ref-erence - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in if this criterion is not to be selected.



Type: DP

Checks: • [A]: It is after minimum acknowledgment time when filled in.

Description: To select alarms with a number lower than or equal to that one.Do not fill in if this criterion is not to be selected.



Type: DP

Checks: • [A]: It is greater than or equal to minimum alarm number when filled in.

Description: To select alarms cleared at that time or before. Absolute time format en-try forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in if this criterion is not to be selected.



Type: DP

Checks: • [A]: It is after minimum clear time when filled in.

Description: To select messages issued at that time or before. Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in if this criterion is not to be selected.


Page 228 of 446 411-9001-124 18.08 1.0


maximum MD notification number

maximum OMC notification number

maximum reception time

maxLapdChPerBtsSM


Type: DP

Checks: • [A]: It is after minimum event time when filled in.

Description: To select OMC-R agent notifications with a number lower than or equal to that one.Do not fill in if this criterion is not to be selected.



Type: DP

Checks: • [A]: It is greater than or equal to minimum MD notification number when filled in.

Description: To select OMC-R manager notifications with a number lower than or equal to that one.Do not fill in if this criteria is not to be selected.



Type: DP

Checks: • [A]: It is greater than or equal to minimum OMC notification number when filled in.

Description: To select messages received at that time or before.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in if this criterion is not to be selected.



Type: DP

Checks: • [A]: It is after minimum reception time when filled in.

Description: Maximum number of LAPD channels used by a radio site (static OMC-R configuration data).

Value range: [6]

Object: OMC-R

Type: DS

411-9001-124 18.08 1.0 Page 229 of 446


maxNbrConsMess

maxNbOfCells Class 2

maxNbrPDAAssig Class 2 (gprsTranscvLockExtendedConf)

maxNbrPUDWithoutVchange Class 2 (NN0002Max) gprsTranscvLockExtended-Conf

Description: Maximum number of messages stored in the BSC log files. This number is allocated by the MD-R at object creation. This attribute can be modi-fied only if the ’bsc’ object instance is locked.


Object: bscLog

Type: DP

Release: V13

Description: Maximum number of radio cells controlled by a site.

Value range: [1 to maxBtsPerBtsSM]


Type: DP

Checks: • [C/M]: The number of cells controlled by a site is limited to maxBt-sPerBtsSM (refer to this entry in the Dictionary).• [M]: This number must be greater than the bts object greatest identifier created for the btsSiteManager object.

Description: Maximum number of:• Polling request messages sent on PDCH after immediate assignment message has been sent on CCCH.• PDAS messages on old TS when changing TS allocation before going into failure.


Object: transceiver


Default value: 5

Type: DP

Release: V12

Description: Maximum number of PUAN (Packet Uplink Ack/Nack) consecutively sent without V(A) has changed (respectively, maximum number of PDAN (Packet Downlink Ack/Nack) consecutively sent without V(Q) has changed).


Object: transceiver


Default value: 10

Type DP

Release: V12

Page 230 of 446 411-9001-124 18.08 1.0


maxNbrRLCEmptyBlock Class 2 (n3101Max) (gprsTranscvLockExtendedConf)

maxNumberRetransmission Class 3

maxPcmCPerBtsSM

maxPcmCPerTranscd

maxRACH Class 3

Description: Maximum number of USF where no data is received in the UL direction.


Object: transceiver


Default value: 10

Type: DP

Release: V12

Description: Maximum number of RACH burst retransmissions allowed in a call in case of non-system response.The information is broadcast to the mobiles at regular intervals on the cell BCCH. It defines the maximum number of times a mobile can renew access requests to the BTS on RACH.

Value range: [one / two / four / seven]

Object: bts

Default value: two

Type: DP

Description: Maximum number of PCM links used by a radio site on the Abis interface (static OMC-R configuration data).

Value range: [6]

Object: OMC-R

Type: DS

Description: Maximum number of PCM links used by a remote transcoder on the Abis interface (static OMC-R configuration data).

Value range: [4]

Object: OMC-R

Type: DS

Description: Broadcast of the PSI 13 message on PACCH during uplink or downlink TBF.The parameter has an MMI constraint (visibility) of GPRS only for usage.

Value range: [0 to 15]• 0: disabled• 1..15: enabled

Object: bts

Feature: Broadcast of PSI 13 (Feature 27358)

411-9001-124 18.08 1.0 Page 231 of 446


maxRowCount

maxSigLPerSigLS

maxTeiPerLapdCh

maxTranscdBPerTranscd

maxTranscdPerBsc

Default value: 0

Type: DP

Notes: • The recommended value is 1.• Only applicable for BSC 3000.

Release: V12

Description: Maximum number of information lines per table to access. "0" means ac-cessing all data. The default value is "1000".


Object: Trace data display

Type: DP

Description: Maximum number of SS7 channels linked to a BSC (static OMC-R con-figuration data).

Value range: 16 (BSC 3000)

Object: OMC-R

Type: DS

Description: Maximum number of TEI addresses allotted to a LAPD terminal (static OMC-R configuration data).It defines the maximum number of LAPD links that can use the same SICD port in the BSC (lapdTerminalNumber attribute of the lapdLink objects).

Value range: [15]

Object: OMC-R

Type: DS

Description: Maximum number of transcoding boards housed in a remote transcoder (static OMC-R configuration data).

Value range: [10 in a GSM 900, E-GSM, GSM-R or 1800 network 8 in a GSM 1900 network]

Object: OMC-R

Type DS

Description: Maximum number of remote transcoders linked to a BSC (static OMC-R configuration data).

Value range: [34 (BSC 3000)2 (TCU3G)]

Page 232 of 446 411-9001-124 18.08 1.0


maxUpTbfP1P2Threshold Class 3

maxUpTbfPerTs Class 3

md

md notification number

Object: OMC-R

Type: DS

Description: Maximum number of uplink TBF on a P1 TDMA before selection of P2 TDMA.


Object: bts


Type: DP

Default value: 16

Release: V12

Description: Maximum number of uplink TBF per TDMA on a timeslot basis.


Object: bts


Type: DP

Default value: 8

Release: V12

Description: Identifier of the md object that describes the OMC-R agent. It is enforced by the system.The md object is unique to the OMC-R. It is created when the system is started.

Value range: [1]

Object: md

Type: Id

Description: To select OMC-R agent notifications with a given number.



Type: DP

411-9001-124 18.08 1.0 Page 233 of 446


mdArchive

mdConfirm

mdFileName

mdGranularityPeriod

Description: Whether archiving the observation messages processed is allowed.The value of this attribute is "not archived" when mdScannerType = "performance monitor" (instrument panel observation) and "archived" otherwise.

Value range: [archived / not archived]

Object: mdScanner

Type DP

Checks: • [M]: This attribute cannot be modified.

Description: Whether the observation messages processed should be acknowl-edged.The value of this attribute is "not confirmed" when mdScannerType = "performance monitor" (instrument panel observation) and "confirmed" otherwise.

Value range: [confirmed (yes) / not confirmed (no)]

Object: mdScanner - Display

Type: DP

Checks: • [C/M]: This attribute is not managed by users.

Description: Name of an observation file containing an elementary report. Refer to the naming rules to Kapsch GSM BSS Fundamentals — Operating Prin-ciples (411-9001-007).

Object: mdScanReportRecord

Type: DP


Description: Recovery period of the observation messages by the OMC-R agent.

Value range: • [5, 10, 15] minutes....... permanent general md• [15, 30, 60] minutes...... Fast Statistic Observation (OFS)• [1440] minutes... General Statistic Observation (OGS)• [5, 10, 15] minutes....... Diagnostic Observation (ODIAG)• [1, 2, 3, 4, 5] minutes... performance monitor (Real Time Observation (ORT))• [5, 10, 15, 30, 60]minutes........ Temporary Observation(TO)

Object: mdScanner

Type: DP

Checks: • [C/M]: The number of temporary observations running at the same time with a 5-minute recovery period in the BSSs managed on the OMC-R is limited to 50.

Page 234 of 446 411-9001-124 18.08 1.0


mdGranularityPeriod

mdGranularityPeriod

mdId

Restrictions: • [M]: This attribute cannot be modified if mdScannerType = "tempo-rary xxx". Stop the observation if necessary by deleting the concerned mdScanner object and create it back with a new observation period.

Note: For a BSC 3000 the mdGranularityPeriod can be reduced:• 5 minutes if the mdObjectList contains 1 bts max.• 10 minutes if the mdObjectList contains 2 bts max.• 15 minutes in all other casesThis note only applies to ODIAG observation.


Value range: • [5, 10, 15] minutes....... permanent general md• [15, 30, 60] minutes...... permanent general bsc (GPO-BSC)• [15, 30, 60] minutes...... Fast Statistic Observation (OFS)• [1440] minutes... General StatisticObservation (OGS)• [15] minutes..... Diagnostic Observation (ODIAG)• [1, 2, 3, 4, 5] minutes... performance monitor (Instrument Panel (IPO) or Real Time Observation (ORT))• [5, 10, 15, 30, 60]minutes........Temporary Observation (TO)

Object: mdScanReportRecord

Type: DP


Value range: • [5, 10, 15] minutes....... permanent general md• [15, 30, 60] minutes...... permanent general bsc (GPO-BSC)• [15, 30, 60] minutes...... Fast Statistic Observation (OFS)• [1440] minutes... General Statistic Observation (OGS)• [15] minutes..... Diagnostic Observation (ODIAG)• [1, 2, 3, 4, 5] minutes... performance monitor (Instrument Panel (IPO) or Real Time Observation (ORT))• [5, 10, 15, 30, 60] minutes........ Temporary Observation (TO)

Object: observationFileReadyRecord

Type: DP

Description: Identifier of the md object describing the OMC-R agent. It is enforced by the system. This attribute allows users to identify the md object on the OMC-R.

Value range: [1]


Type: DP

Checks: • [M]: This attribute is not managed by users.

411-9001-124 18.08 1.0 Page 235 of 446


mdLog

mdObjectList

mdObjectList

Description: Whether the observation messages processed are saved on the OMC-R agent disks.The value of this attribute is "not logged" when mdScannerType = "per-formance monitor" (instrumentpanel observation) and "logged" otherwise.

Value range: [logged / not logged]

Object: mdScanner

Type DP

Checks: • [M]: This attribute cannot be modified.

Description: Identification of the observed object. It depends on the type of the de-fined observation.

mdScannerType mdObjectList

permanent gen-eral md

md

permanent gen-eral bsc

bsc

general statistic (OGS)

bsc

fast statistic (OFS)

bsc

performance monitor

bsc

real time (ORT) bsc

temporary sig-nallingLink*

bsc & signallingLink

temporary Abis Interface bts*

bsc & btsSiteManager & bts

diagnostic (ODIAG)

bsc, bts, signallingLink, hardware transcoder 3G, transcoderEqpt,pcmPort, transceiverEqpt & btsSiteManager, pcmCircuit, adjacentCell

* This type only applies to V12 BSCs.

Description: Identification of the observed object. It depends on the type of the de-fined observation.


Object: display xxx report

Type DP

Page 236 of 446 411-9001-124 18.08 1.0


mdObjectList

mdScanner

mdScannerType

mdScannerType

Description: Identification of the observed object. It depends on the type of observa-tion defined.



Type: DP

Description: Identifier of an mdScanner object defined with regard to the md object.The mdScanner object class describes the OMC-R agent and BSS observations. These objects are managed by the OMC-R "Performance Management" function.


Object: mdScanner

Type: Id

Checks: • (performed only when the object describes a BSS observation)• [C/M/D] : The application database of the BSC is not being built.• [C/M/D] : If the application database of the BSC is not built, temporary observations cannot be managed.• [C/M/D] : If the application database of the BSC is built, the BSS/OMC-R link is established and no audit is in-progress in the BSC.

Remark: Deleting an mdScanner object that describes a temporary observation is always possible if the observation duration has elapsed (stopTime 1= 0) and the stop TGE has been sent to the BSC.

Description: The type of observation.

Value range: [fast Statistic / general statistic / real Time / diagnostic / temporary inter-ference / temporary signallingLink /temporary Abis Interface bts / permanent general md / permanent gen-eral manager]


Type: DP


Value range: [fast Statistic / general statistic / real Time / diagnostic / temporary inter-ference / temporary signallingLink /temporary Abis Interface bts / permanent general md / permanent gen-eral manager


Type: DP

411-9001-124 18.08 1.0 Page 237 of 446


mdScannerType

mdScannerType

mdScannerType

mdStorageDuration


Value range: [fast Statistic / general statistic / real Time / diagnostic / temporary inter-ference / temporary signallingLink / temporary Abis Interface bts / per-manent general md / permanent general manager]

Object: Load formulae

Type: DP


Value range: [fast Statistic / general statistic / real Time / diagnostic / temporary inter-ference / temporary signallingLink /temporary Abis Interface bts / permanent general md / permanent gen-eral manager / pcuSN]

Object: mdScanner

Type: DP

Checks: • [C]: The defined observation is not running.


Notes: • The permanent general md observation is unique to the OMC-R.• The permanent general bsc and Instrument Panel observations are unique to a BSS (V10).• The OGS is unique to a BSS (V11+).• The OFS is unique to a BSS (V11+).• The ORT is unique to a BSS (V11+).• A temporary observation of a given type or ODIAG (V11+) is unique to a BSS.


Value range: [fast Statistic / general statistic / real Time / diagnostic / temporary inter-ference / temporary signallingLink / temporary Abis Interface bts / per-manent general md / permanent general manager / pcuSN]r]


Type: DP

Description: Storage duration of the observation messages processed on the OMC-R agent disks.Observation messages are kept on the OMC-R agent disks for a limited period of time, provided the mdLog attribute of the associated log object is "logged". They are automatically purged at regular intervals. The user must archive the observation data, for data analysis occurring after the purge time set by the static configuration.

Value range: [N] hour. N is a static configuration data. Since instrument panel obser-vation messages are not kept, N equals zero for the log objects that de-scribe these observations.

Object: mdScanner

Type: DP


Page 238 of 446 411-9001-124 18.08 1.0


mdTransferMode

mdWarning

MIB version

microCellCaptureTimer Class 3

Description: Service used by the OMC-R agent to transmit the observation messages processed to the OMC-R manager.

Value range: [FTAM (permanent general md and bsc observations) / CMIS (others)]


Type: DP


Description: Identifier of a mdWarning object defined with regard to the md object.The mdWarning object class describes the processing conditions of BSS alarms of "outOfRangeCounter" and "excessiveAnomalyRate" type. These objects are managed by the OMC-R "Fault Management" function.


Object: mdWarning

Type: Id

Description: Appears during creation of executableSoftware object and is an internal representation of MIB version.


Feature: Flexible OMC-R

Type: DP

Release: V18.0

Description: Time used to confirm a capture (signal strength stability) when using mi-cro-cell Algorithm type A.

Value range: Time = N multiplied by <runHandOver>. According to microCellCapture-Timer value, N values are the following:• [0 to 249] N = [0 to 249]• 250 N = 512• 251 N = 1024• 252 N = 2048• 253 N = 4096• 254 N = 8192• 255 N = 16384


Default value: 0

Condition: To define if A handover algorithm is activated

Type: DP

Checks: • [C]: This attribute is defined if the described neighbor cell is a micro-cell (cellType = "microType").

411-9001-124 18.08 1.0 Page 239 of 446


microCellStability Class 3

minimum acknowledgment time

minimum alarm number

Release: V8

Note: To activate the MicroCellAlgo feature for this parameter,1. Set the MicroCellAlgo (in the omc_services.cfg of the OMC) to A. Stop the OMC-R application and perform the "omc_configure.sh -A" com-mand.2. For the BSCs to take effect of the new feature activation, perform a Build-BDA on all the BSCs on this OMC-R during the next maintenance window.

Description: Strength Level Stability Criterion for Capture Algorithm A.



Default value: 10

Condition: To define if A handover algorithm is activated

Type: DP

Checks: • [C]: This attribute is defined if the described neighbor cell is a micro-cell (cellType = "microType").

Note: To activate the MicroCellAlgo feature for this parameter,1. Set the MicroCellAlgo (in the omc_services.cfg of the OMC) to A. Stop the OMC-R application and perform the "omc_configure.sh -A" com-mand.2. For the BSCs to take effect of the new feature activation, perform a Build-BDA on all the BSCs on this OMC-R during the next maintenance window.

Description: Selecting messages acknowledged at that time or after.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in criterion if not to be selected.



Type: DP

Checks: • [A]: It is before maximum acknowledgment time when filled in.

Description: To select alarms with a number greater than or equal to that one.Do not fill in criterion if not to be selected.



Type: DP

Checks: • [A]: It is lower than or equal to maximum alarm number when filled in.

Page 240 of 446 411-9001-124 18.08 1.0


minimum clear time

minimum event time

minimum MD notification number

minimum OMC notification number

Description: To select alarms cleared at that time or after.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in criterion if not to be selected.



Type: DP

Checks: • [A]: It is before maximum clear time when filled in.

Description: To select messages issued at that time or after.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in criterion if not to be selected.



Type DP

Checks: • [A]: It is before maximum event time when filled in.

Description: To select OMC-R agent notifications with a number greater than or equal to that one.Do not fill in criterion if not to be selected.



Type: DP

Checks: • [A]: It is lower than or equal to maximum MD notification number when filled in.

Description: To select OMC-R manager notifications with a number greater than or equal to that one.Do not fill in criterion if not to be selected.



Type: DP

Checks: • [A]: It is lower than or equal to maximum OMC notification number when filled in.

411-9001-124 18.08 1.0 Page 241 of 446


minimum reception time

minNbOfJokersPerConnectedMain Class 3

minNbOfTDMA Class 2

minNbrGprsTs Class 3

Description: To select messages received at that time or after.Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in criterion if not to be selected.



Type: DP

Checks: • [A]: It is before maximum reception time when filled in.

Description: Minimum number of joker AGPRS 16 kbit/s TSs per main AGPRS 16 kbit/s TS, that cannot be preempted by the Dynamic Agprs feature.

Value range: [0..4] step 0.125

Object: transceiver

Default value: 0

Type: DP

Feature EDGE Dynamic Agprs minimum of joker TS

Checks: • [C/M]: minNbOfJokersPerCon nectedMain must be lower than or equal to the target number of jokers per TDMA (parameter jokerPer-MainTarget)• [C/M]: minNbOfJokersPerConnectedMain must be equal to 0 when EDGE is not activated on TDMA (that is when edgeDataServiceType is equal to capability is not requested)

Release: V16Note: This parameter is mandatory. It is only available for BSC

3000.

Description: Minimum number of TDMA frames working for the cell itself.The frame carrying the cell BCCH must be among them and success-fully configured.


Object: bts

Default value: 1

Type: DP

Checks: • [M]: This number is less than or equal to the number of transceiver objects (TDMA frames) created for the bts object.

Description: Minimum number of TS dedicated to GPRS in the cell.


Object: bts


Page 242 of 446 411-9001-124 18.08 1.0


minTimeQualityIntraCellHO Class 3

minTimeQualityIntraCellHO Class 3

missDistWt Class 3

Default value: 0

Type: DP

Release: V12

Description: This attribute defines the minimum time between one intracell HO and the next quality intracell HO.This attribute can only be modified if the ’handOverControl’ object in-stance is unlocked



Default value: 0

Type: DP

Release: V12

Description: This attribute defines the minimum time between one intracell HO and the next quality intracell HO.This attribute can only be modified if the ’handOverControl’ object in-stance is unlocked



Default value: 0

Type: DP

Release: V14

Note: Applies to a BSC 3000 architecture only.

Description: Weight applied to missing Distance measurement.The missing measurement is replaced by the latest received raw mea-surement weighed by this corrective factor when calculating the average MS-BTS distance.The range of permitted values makes missing distance measurements not favored.



Default value: 110

Type: DP

411-9001-124 18.08 1.0 Page 243 of 446


missRxLevWt Class 3

missRxQualWt Class 3

mms

mmsId

Description: Weight applied in case of missing signal strength measurement report.The missing measurement is replaced by the latest computed arithmetic average, or by the latest received raw measurement if no average value is available, weighed bythis corrective factor when calculating the average signal strength in the cell. Selecting the greatest value makes missing strength measure-ments not favored.



Default value: 90

Type: DP

Description: Weight applied to missing Quality measurement. The missing measurement is replaced by the latest computed arithmetic average, or by the latest received raw measurement if no average value is available, weighed by this corrective factor when calculating the aver-age bit error rate in the radio link. The range of permitted values makes missing quality measurements not favored.



Default value: 110

Type: DP

Description: The Memory Mass Storage module, which holds all the private data (for OMU) and those that must be secured and still accessible in the event of an OMU failure or disk failure (for Control Node).


Object: mms

Type: Id

Description: Identifier of the ’mms’ object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000.


Object: mms

Type: DP

Release: V 13

Page 244 of 446 411-9001-124 18.08 1.0


mmsUsage

mobileAllocation Class 2

mobileCountryCode Class 3


Description: Indicates whether the MMS is private (i.e. associated to an OMU) ; or shared-mirrored (associated to the Control Node).This attribute cannot be modified. It is set by the MD-R at MMS creation.

Value range: [0 (Shared) to 1 (Private)]

Object: mms


Type: DP

Checks: • [M]: The MMS disc scan can be launched only for MMS objects that have the mmsUsage parameter set to mmsUsageShared.

Release: V13

Description: List of sixty-four frequencies allotted in the network frequency band to a radio time slot obeying frequency hopping laws.

Value range: [1 to 124] (GSM 900 network),[955 to 1023] / [0 to 124] (GSM-R),[975 to 1023] / [0 to 124] (E-GSM),[512 to 885] (GSM 1800 network),[512 to 810] (GSM 1900 network),[128 to 251] (GSM 850 network),[955 / 1023] / [0 /55] (GSM-R).


Type: DP

Checks: • [C/M]: Each frequency occurs once in the list and is allotted to the par-ent bts object (cellAllocation).• [M]: If the frequencyHoppingSystem object is referenced by a channel object dependent on the associated bts object, the parent bsc object is unlocked and the associated bts object is locked.

Description: Code of the PLMN home country.Refer to the next entry.



Type: DP

Checks: • [C]: This code is identical to the mobileCountryCode attribute of the parent bsc object when it is defined for that object.• [C/M]: A CGI is unique in the set including a serving cell and its neigh-bor cells.

Description: Code of the PLMN home country.Refer to the next entry.



411-9001-124 18.08 1.0 Page 245 of 446




mobileCountryCodeUTRAN Class 3

Type: DP


Description: Code of the PLMN home country. It is defined when theMSC does not manage cell global identifiers (CGI). The MSC does not manage cell global identifiers (CGI) for a GSM-R network (Group call). Refer to the next entry.


Object: bsc

Condition: For a GSM network: to define when the MSC does not manage cell glob-al identifiers (CGI).

Condition: For a GSM-R network: mandatory as the MSC does not manage cell global identifiers (CGI) for Group Call.

Type: DP

Description: Code of the PLMN home country.A CGI (Cell Global Identifier) is unique within a location area. It identifies a cell unambiguously in the PLMN and includes four fields: cellIdentity-Code (CI), locationAreaCode (LAC), mobileCountryCode (MCC), and mobileNetworkCode (MNC).


Object: bts

Type: DP


Description: Mobile country code (MCC) of the UMTS neighbouring cell for HO

Value range: 000..999 (string)


Default value: NA

Type: DP

Checks: • [C]: The set of attributes cId, rNCId,mobileCountryCodeUTRAN andmobileNetworkCodeUTRAN mustbe unique among all the instancesof the objects adjacentCellUTRANattached to the same bts.

Release: V17


Page 246 of 446 411-9001-124 18.08 1.0


mobileNetworkCode Class 3



mobileNetworkCodeUTRAN Class 3

Description: Code of the PLMN in the country.Refer to the next entry.



Type: DP

Checks: • [C]: This code is identical to the mobileNetworkCode attribute of the parent bsc object when it is defined for that object.• [C/M]: A CGI is unique in the set including a serving cell and its neigh-bor cells.

Description: Code of the PLMN in the country. It must be defined when the MSC does not manage cell global identifiers (CGI). Refer to the next entry.


Object: bsc

Type: DP

Description: Code of the PLMN in the country.A CGI (Cell Global Identifier) is unique within a location area. It identifies a cell unambiguously in the PLMN and includes four fields: cellIdentity-Code (CI),locationAreaCode (LAC), mobileCountryCode (MCC),and mobileNetworkCode (MNC).


Object: bts

Type: DP

Checks: • [C]: This code is identical to the mobileNetworkCode attribute of the parent bsc object when it is defined for that object.• [C/M]: A CGI is unique in the set including a serving cell and its neigh-bor cells.

Description: Mobile network code (MNC) of the UMTS neighbouring cell for HO

Value range: 00..999 (string)


Default value: N.A.

Type: DP

Checks: • [C]: The set of attributes cId, rCId, mobileCountryCodeUTRAN and mobileNetworkCodeUTRAN must beunique among all the instances of the objects adjacentCellUTRAN attached to the same bts.

Release: V17


411-9001-124 18.08 1.0 Page 247 of 446


modeModifyMandatory Class 3

monitoredObjectClass

monitoredObjectInstance

monitoredSpecificProblemsList

Description: Whether a CHANNEL MODE MODIFY message is sent to the mobile af-ter a directed retry handover in the BSS.

Value range: [used (yes) / not used (no)]

Object: bsc


Type: DP

Checks: • [C/M]: The attribute value can only be "used" if directed retry hando-vers are allowed at BSC level. Refer to the interBscDirectedRetry and intraBs cDirectedRetry entries in the Dictionary.

Release: V9

Description: Class of the serving object for the notifications processed.Lists the possible object classes to be monitored.

Value range: [adjacentCellHandOver / adjacentCellUTRAN / atmRm / bscLog / bts / btsSiteManager / cc / cem / cem3 / cemRc / Bsc / cemRc Tcu / channel / transceiverZone / control node / handOverControl / hardware transcod-er 3G / hsaRc /hsaRc Tcu / iem / igm / interface node / iom / ipgRc / ipm /lapdLink / lsaRc Bsc / lsaRc Tcu / mms / omu / / pcmCircuit / pcu / pow-erControl / signallingLink / signallingLinkSet /signallingPoint / software / sw8kRm / tmu / transceiver /transceiverEquipment / transcoder / trm / xtp]

Object: mdWarning

Feature: PM1270 - TDMA based counters

Type: DP


Description: Identification of a serving object in the class. They identify the object that issued the processed notifications. Enter the concerned object identifi-cation sequence.

Value range: [adjacentCellHandOver / adjacentCellUTRAN / atmRm / bsc / bscLog / bts / btsSiteManager / cc / cem / cem3/ cemRc Bsc / cemRc Tcu / chan-nel / control / node /handOverControl / hardware transcoder 3G / hsaRc /hsaRc Tcu / iem / igm / interface node / iom / ipgRc / ipm / lapdLink / lsaRc Bsc / lsaRc Tcu / mms / omu / pcmCircuit/ pcu / powerControl / signallingLink / signallingLinkSet /signallingPoint / software / sw8kRm / tmu / transceiver /transceiverEquipment / transceiverZone / transcoder / trm /xtp]

Object: mdWarning

Type: DP

Description: List of the specific problems taken into account in the process.This parameter filters the processed notifications according to the fol-lowing criteria: cause number, fault number, and processor number.

Value range: [(cause, faultNumber) pair]

Page 248 of 446 411-9001-124 18.08 1.0


month

msBtsDistanceInterCell Class 3

msCapWeightActive Class 2

msLeakRate


Type: DP

Description: Identifies the month the observation report was created. Date format en-try forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB,and Help menus (411-9001-130).


Object: Display busiest day of the month report

Type: DP

Description: To determine whether inter-bts handovers are allowed in a cell for dis-tance reasons.




Type: DP

Description: To specify whether the Weight Fair Allocation algorithm is used or not.


Object: bts


Default value: yes

Type: DP

Release: V12

Description: This attribute specifies the leak rate parameter for one GPRS MS with 1 TS. This value is used only once at the MS Bucket creation time on SGSN side. For GPRS, (that is, if EDGE is not activated in the cell or there is no TDMA that is EDGE capable in the cell), this value is sent to the SGSN in the FLOW-CONTROL-BVC message as the default MS Leak Rate. (60kbps is considered as soon as one EDGE TDMA is acti-vated in the cell).

Value range: [2W, 8 W, 2W + 8 W]

Default value: 2W + 8W

Release: V12

411-9001-124 18.08 1.0 Page 249 of 446


msPowerClassToggle Class 3

msRangeMax Class 3

msTxPwrMax Class 3

Description: MS power class which needs dedicated statistics.

Value range: [2W / 8W / 2W + 8W]

Object: bts

Feature: Advanced Speech Call Items

Default value: 2W + 8W

Type: DP

Release: V15

Description: Maximum MS-to-BTS distance beyond which a handover may be trig-gered. It can be set to 1 for a microcell and is less than callClearing in all cases. The attributes ’msRangeMax’ and ’concentAlgoIntMsRange= ’ must verify ’msRangeMax’ >= ’concentAlgoIntMsRange’.



Default value: 34 in non-extended mode, 89 in extended mode

Type: DP

Checks: • [C/M]: msRangeMax < callClearing (associated bts object attribute)• [C/M]: The maximum distance is limited to 34 km if the extended cell attribute of the associated bts object is "false".• [C/M]: The maximum distance is 120 km if the extended cell attribute of the bts object is "true".

Description: Maximum MS transmission power in a serving cell. It is equal to msTx-PwrMaxCCH in a GSM 900 network.

Value range: [5 to 43, by steps of 2] dB (GSM 900, GSM-R, E-GSM, GSM 850, GSM 850 - GSM 1900 and GSM 900 - GSM 1800 networks)[0 to 36, by steps of 2] dB (GSM 1800, and GSM 1800 -GSM 900 networks) [0 to 33] dB (GSM 1900, E-GSM and 1900-850, GSM 850)

Object: bts

Default value: Typical value of 33 dB for GSM 900 handhelds

Default value: lds and 30 dB for GSM 1800 and 1900 handhelds

Type: DP

Checks: • [C/M]: GSM 900 networks: msTxPwrMax = msTxPwrMaxCCH

Note: The msTxPwrMax values [displayed by the OMC-R] /[typed by the OMC-R operator] are encoded values. Thecorresponding maximum MS transmission powers in a serving cell are compliant to GSM Rec 05.05, that is to say:• [5 to 39] dB (GSM 900 network)

Page 250 of 446 411-9001-124 18.08 1.0


msTxPwrMax2ndBand Class 2

msTxPwrMaxCCH Class 3

Description: Maximum MS transmission power in the band 1 of the dualband cell de-pending on the network type (BCCH is only defined in band 0).

Value range: [0 to 36] for GSM 900 - GSM 1800 (gsmdcs), [5 to 43] for GSM 1800 - GSM 900 (dcsgsm),[0 to 33] for GSM 850 - GSM 1900 (gsm850pcs),[5 to 43] for GSM 1900 - GSM 850 (pcsgsm850),for all in the steps of 2 + value = 33 for GSM 850 - GSM 1900 0..43 for other standardIndicator types.

Object: bts

Default value: Typical value of 33 dB for GSM 900 and GSM 850 handhelds, 30 dB for GSM 1800 and 1900


Type: DP

Checks: • [C/M]: 464C001 The attribute value must be even and located be-tween [0 to 36] dB when the standardIndicator attribute is equal to"gsmdcs".• [C/M]: 464C002 The attribute value must be odd and located between [5 to 43] dB when the standardIndicator attribute is equal to "dcsgsm".• [C/M]: 464C003 The attribute value must be even and located be-tween [0 to 33] dB when the standardIndicato r attribute is equal to"gsm850pcs".• [C/M]: 464C004 The attribute value must be odd and located between [5 to 43] dB when the standardIndicator attribute is equal to "pcsgsm850".

Note: The msTxPwrMax values [displayed by the OMC-R] / [typed by the OMC-R operator] are encoded values. The corresponding maximum MS transmission powers in a serving cell are compliant to GSM Rec 05.05, it means:• [5 to 39] dB (GSM 900 network)• [0 to 36] dB (GSM 1800 network)

Release: V12

Description: Maximum MS transmission power in a cell CCCH.The BSC relays the information to the mobiles in the Abis CELL MODI-FY REQUEST message.

Value range: [[5 to 43, by steps of 2] dB (GSM 900, GSM 850, GSM-R, and GSM 900 - GSM 1800 networks) [0 to 36, by steps of 2] dB (GSM 1800, and GSM 1800 - GSM 900 networks) [0 to 33] dB (GSM 1900, 1900-850, and GSM-R networks)

Object: bts

Default value: Typical value of 33 dB for GSM 900 and GSM 850 handhelds, 30 dB for GSM 1800 and 1900

Type DP

Remark: If the cell is used as a neighbor cell of another serving cell in the network, msTxPwrMaxCCH must be identical to the msTxPwrMaxCell power defined for the corresponding adjacentCellHandOver object (the values must be checked by users).

Note: The msTxPwrMax values [displayed by the OMC-R] / [typed by the OMC-R operator] are encoded values. The corresponding maximum MS transmission powers in a serving cell are compliant to GSM Rec 05.05, that is to say:• [5 to 39] dB (GSM 900 network)

411-9001-124 18.08 1.0 Page 251 of 446


msTxPwrMaxCell Class 3

multi band reporting Class 3

multiple site

Description: Maximum MS transmission power in a neighbor cell. It is equal to msTx-PwrMaxCCH when the cell is declared as a serving cell on the network (the value must be checked by users).

Value range: [5 to 43, by steps of 2] dB (GSM 900, GSM-R, E-GSM, GSM 850, GSM 850 - GSM 1900 and GSM 900 - GSM 1800 networks) [0 to 36, by steps of 2] dB (GSM 1800 network and GSM 1800 - GSM 900) [0 to 33, by steps of 2 + value 33] dB (GSM 1900-850 networks)


Default value: Typical value of 33 dB for GSM 900 or 850 handhelds and 30 dB for GSM 1800 and 1900 handhelds

Type: DP

Remark: If the cell is used as a neighbor cell of another serving cell in the network, msTxPwrMaxCell should be identical to the msTxPwrMaxCCH power defined for the corresponding adjacentCellHandOver object (the values must be checked by users).

Notes: • The msTxPwrMax values [displayed by the OMC-R] / [typed by the OMC-R operator] are encoded values.The corresponding maximum MS transmission powers in a serving cell are compliant to GSM Rec 05.05, that is to say:• [5 to 39] dB (GSM 900 network)• [0 to 36] dB (GSM 1800 network)

Description: Minimum number of cells multibanding MSs, report their radio measure-ments in each frequency band.

Value range: [the six strongest cells / the strongest cell out band / the two strongest cells out band / the three strongest cells out band]• six strongest allowed cells irrespective of their frequency band• the strongest allowed cell outside the current frequency band• the two strongest allowed cells outside the current frequency band• the three strongest allowed cells outside the current frequency band

Object: bts

Default value: the six strongest cells

Type: DP

Release: V10

Description: Identifier of a multiple site object defined with regard to a bsc object.



Type: Id

Checks: • [C]: The multiple site object is not created for the parent bsc object.• [C/M]: The btsSiteManager objects in the btsSiteManagerList list are created for the parent bsc object and are not referenced by another mul-tiple site object.• [M/D]: The multiple site object is created and the current btsSiteMan-ager objects referenced in the btsSiteMan agerList list are locked.

Release: V8

Page 252 of 446 411-9001-124 18.08 1.0


multipleVocoders Class 1

muxNumber Class 3

2.14. N

Description: Whether the BSC is linked to one or more MSCs using different speech coding protocols.An MSC uses either the GSM protocol or the JTC protocol. "False" means that only the GSM protocol is compatible.


Object: bsc


Type: DP

Notes: • If MSC parameter MULTIPLE_VOCODER_SUP PORT, (Table OF-CVAR) is set to ON (as detailed in NTP < 455 >), then the following BSC parameters must be set to TRUE:• chosenChannelAsscomp• chosenChannelHoReq• chosenChannelHoPerf• chosenChannelCompL3Info

Release: V8

Description: pcuSN mux identification

Value range: [noMux / oneMux / twoMux]

Object: pcusn


Type: DP

Release: V12

n3103 Class 3

Description: Maximum number of repetition of a PUAN (Packet Uplink Ack/Nack) message.


Object: bts

Default value: 5


Type: DP

Release: V12

n3105max Class 2 (gprsTranscvLockBtsExtendedConf)

Description: Maximum number of consecutive RLC data blocks sent by the PCU with a valid RRBP and not having been acknowledged by the MS.


Object: transceiver

Default value: 4


411-9001-124 18.08 1.0 Page 253 of 446


Type: DP

Release: V12

nACCActivation Class 3

Description: Activation of the Network Assisted Cell Change feature.


Object: bts


Feature: Network Assisted Cell Change for release 4 MS

Type: DP

Release: V16


nAMRWBRequestedCodec Class 3

Description: This parameter specifies a minimum number of codecModeRequest out of pRequestedCodec in the (n,p) voting mechanism to trigger an alarm AMR-WB HO.

Value range: 0 to 196


Default value: 44


Release: V18.0

nAvgl Class 3 (gprsAvgParam)

Description: Signal strength filter used for MS output power control. It specifies the "Interference signal strength filter" constant for power control. NAVG -I = 2 (k/2) with k = nAvgI.


Object: bts

Default value: 0


Type: DP

Release: V12

nAvgT Class 3 (gprsAvgParam)

Description: Signal strength filter used for MS output power control, which specifies the "Signal strength filter period" for power control in packet transfer mode. TAVG -T = 2 (k/2) /6 with k =nAvgT.


Object: bts

n3105max Class 2 (gprsTranscvLockBtsExtendedConf)

Page 254 of 446 411-9001-124 18.08 1.0


Default value: 0


Type: DP

Checks: • [M]: The parent bsc object is unlocked.

Release: V12

nAvgW Class 3 (gprsAvgParam)

Description: Signal strength filter used for MS output power control, which specifies the "Signal strength filter period" for power control in packet idle mode. TAVG -W = 2 (k/2) /6 with k =nAvgW.


Object: bts


Type: DP

Checks: • [M]: The parent bsc object is unlocked.

Release: V12

Note: Tavg_w has no impact on frequency measurements and computations done by the MS, which is always equal to the frequency of paging blocks decoding.

nbOfFramesForFER Class 3

Description: Number of frames taken into account for FER (Frame Erasure Rate) evaluation.


Object: bts

Type: DP

Checks: • [C/M] The value for nbOfFramesForFER must not be equal to [1..249]. The purpose of this semantic check is Forbid values 1 to 249 for nbOf-FramesForFER.


Default value: 0

Release: V14


nbOfRepeat Class 2

Description: Maximum number of times that paging messages are repeated to mo-biles that belong to the same paging sub-group.It is set to "3" in former BSS versions (static configuration parameter).The following inequality, that is not checked by the system, must be true (refer to these entries in the Dictionary):retransDuration (delayBetweenRetrans + 1) x nbOfRepeat


nAvgT Class 3 (gprsAvgParam)

411-9001-124 18.08 1.0 Page 255 of 446


Object: bts

Default value: 3

Type: DP

Release: V8

nbrFreeTchBeforeAnticipation Class 3


Value range: [0]

Object: bts


Default value: 0

Type: DP

Release: V12

nbrFreeTchToEndAnticipation Class 3


Value range: [0]

Object: bts

Default value: 0


Type: DP

Release: V12

nCapacityFRRequestedCodec Class 3

Description: Number of 12.2 codec mode requested to trigger a capacity handover (FR to HR).This attribute can only be modified if the ’handover’ control object in-stance is unlocked.



Default value: 44

Type: DP

Release: V14


nbOfRepeat Class 2

Page 256 of 446 411-9001-124 18.08 1.0


nCHPosition Class2

Description: Defines the number of blocks and position of the first block for NCH.

Value range: [0 block1 block, first block 01 block, first block 11 block, first block 21 block, first block 31 block, first block 41 block, first block 51 block, first block 62 blocks, first block 02 blocks, first block 12 blocks, first block 22 blocks, first block 32 blocks, first block 42 blocks, first block 53 blocks, first block 03 blocks, first block 13 blocks, first block 23 blocks, first block 33 blocks, first block 44 blocks, first block 04 blocks, first block 14 blocks, first block 24 blocks, first block 35 blocks, first block 05 blocks, first block 15 blocks, first block 26 blocks, first block 06 blocks, first block 17 blocks, first block 0]

Object: bts

Feature: (GSM-R V12)

Default value: 0 block

Type: DP

Release: V12

Note: nCHPosition - noOfBlocksForAccessGrant relation according to chan-nelType attribute

channelType nCHPosition noOfBlocksFor AccessGrant

mainBCCH 1 block, first block 0 to 62 blocks, first block 0 to 53 blocks, first block 0 to 44 blocks, first block 0 to 35 blocks, first block 0 to 26 blocks, first block 0 to 17 blocks, first block 0

>= 1>= 2>= 3>= 4>= 5>= 6= 7

mainBCCHCombined

1 block, first block 01 block, first block 12 blocks, first block 0

1 or 2= 12= 12

411-9001-124 18.08 1.0 Page 257 of 446


networkColourCode Class 3

Description: Color code of the mobile network. The (BCC,NCC) pair forms the cell BSIC.



Type: DP

Checks: • [M]: Each defined (baseColourCode, bCCHFrequency, networkC-olourCode)combination is unique in the set including a serving cell and its neighbor cells.• [M]: Modification of bCCHFrequency, baseColourCode and networkC-olourCode is forbidden while interference matrix is running.

networkColourCode Class 2

Description: Color code of the mobile network. It allows countries with common bor-ders to allocate BCCs and BCCH frequencies at their own convenience in international border areas. The (BCC,NCC) pair forms the cell BSIC.The information is broadcasted on the cell SCH.The Base Station Identity Code (BSIC) is a six-bit code: bits 6-5-4 = NCC (PLMN color code), bits 3-2-1 = BCC (Base station color code). Outside border areas, the NCC bits can be used to increase the number of BCC possibilities.


Object: bts

Type: DP

Checks: • [M]: Each defined (baseCo lourCode,bCCHFrequency, networkColourCode) combination is unique in the set including a serving cell and its neighbor cells.

Remark: The NCC should not be confused with the MCC (Mobile Country Code) nor the MNC (Mobile Network Code), which are part of the CGI (Cell Global Identifier).


networkIndicator Class 1

Description: Identifier of the SS7 network.

Value range: [nationalReserved / national / internationalReserved / international]


Type: DP

Checks: • [C/M]: For 3G, any value in the value range can be used.

new name

Description: New name to give to the short message. It is different from the current short message identifier.


Page 258 of 446 411-9001-124 18.08 1.0


Object: short message - Rename

Type: DP

Checks: • [A]: It is different from the current short message identifier.• [A]: It does not exist on the OMC R.

new password 1st try

Description: User’s new password to use in the next login request. It begins with a letter, contains at least one non-alphabetical character among the first eight characters, and is case sensitive. It is not displayed.

Value range: [6 characters min]

Object: user profile - Change password

Type: DP

Checks: • [A]: It begins with a letter and contains one non-alphanumerical char-acter among the first eight characters.• [A]: It is at least six-character long.• [A]: It is different from the N previous occurrences (N is set in static configuration data).

new password 2nd try

Description: Second definition of the user’s new password that will not be validated unless it is exactly the same as new password 1st try. It is not displayed. Refer to the new password 1st try entry in the dictionary. The new password is validated when opening a new session.



Type: DP

Checks: • [A]: It begins with a letter and contains one non-alphanumerical char-acter among the first eight characters.• [A]: It is at least six-character long.• [A]: It is different from the N previous occurrences(N is set in static configuration data).

new power control algorithm Class 3

Description: Algorithm used by the BTS to control power in a cell. The "step by step" value refers to the standard power control algorithm.The "one shot" value refers to the advanced power control algorithm.The "enhanced one shot" value refers to the advanced power algorithm used in connection with the handOverControl object rxLevHreqaveBeg attribute used in the early handover mechanism.

Value range: [step by step / one shot / enhanced one shot]

Object: bts

Feature: Fast power control at TCH assignment (TF975 - V12)

Default value: one shot

Type: DP

new name

411-9001-124 18.08 1.0 Page 259 of 446


Notes: • The "enhanced one shot" attribute value can only apply to non mixed DCU4 or DRX transceiver architecture.• Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (such as TRX, BSC, BTS, BTSSM). All other symbols/characters are prohibited.

Release: V9

next execution time

Description: Date and time of next job run.

Value range: [<date> <time>]

Object: job - Display

Condition: This parameter is significant and displayed only when a job run period-icity is defined.

Type: DD

nFRRequestedCodec Class 3

Description: This attribute modifies the "n" parameter in the AMR full rate "(n,p) vot-ing" mechanism used for FR->HR handovers.This parameter is used by all AMR FR HO not only FR=>HR.This attribute can only be modified if the ’handOverControl’ object in-stance is unlocked.



Default value: 24

Type: DP

Release: V14


nHRRequestedCodec Class 3

Description: This attribute modifies the "n" parameter in the AMR half rate "(n,p) vot-ing" mechanism used for FR->HR handovers.This parameter is used by all AMR HR HO not only FR=>HR.This attribute can only be modified if the ’handOverControl’ object in-stance is unlocked.



Default value: 34

Type: DP

Release: V14


new power control algorithm Class 3

Page 260 of 446 411-9001-124 18.08 1.0


night intervention

Description: This attribute modifies the "n" parameter in the AMR half rate "(n,p) vot-ing" mechanism used for FR->HR handovers.This parameter is used by all AMR HR HO not only FR=>HR.This attribute can only be modified if the ’handOverControl’ object in-stance is unlocked.



Default value: 34

Type: DP

Release: V14


night intervention

Description: Type of action associated with an alarm criterion in the nighttime config-uration.



Type: DP

noOfBlocksForAccessGrant Class 2

Description: Number of CCCH blocks not used for paging.A BCCH is combined when it shares the same radio time slot with four SDCCHs which can include a CBCH (refer to the channelType entry in the Dictionary). In that case, the attribute value is no greater than to 2 (the value must be checked by users).Refer also to the nCHPosition entry in this dictionary.

Value range: [0 to 2] if the cell uses a combined BCCH, [1 to 7] otherwise."0" means that PCH blocks are used for sending immediate assignment messages as and when needed.

Object: bts

Default value: 2

Type: DP

Checks: • [M]: This number is greater than zero if the channelType of one of the channel objects dependent on the bts object is "sdcch8CBCH" (refer to this entry in the Dictionary).• [M]: This number is strictly greater than zero if the SysInfo 2Q and/or SysInfo 13 on extended BCCH features are activated.Checks:• [M]: If Bit 9 (SI13) or Bit 10 (SI2Quater) in value of label 64 in bscData-Config table is set, the value of NoOfBlocksForAccessGrant in the bts object cannot be set to 0.

411-9001-124 18.08 1.0 Page 261 of 446


noOfMultiframesBetweenPaging Class 2

Description: Number of occurrences of a paging sub-group.The greater this number, the greater the number of paging sub-groups.

Value range: [2 to 9] multi-frame of fifty-one frames

Object: bts

Default value: 6

Type: DP

notAllowedAccessClasses Class 3

Description: List of mobile access classes that are forbidden in the cell, except case of congestion.This attribute, together with the emergencyCallRestricted attribute, al-lows to control access to a cell according to the service classes autho-rized.

Value range: List of mobile access class:• [0 to 9]: user classes• [11 to 15]: operator classes

Object: bts

Default value: Leave the field empty

Type: DP

Remark: General conditions mobiles are granted access to a cell are allotted at subscription time.

notification number

Description: Reference number of the associated notification


Object: alarmRecord, mdScanReportRecord, observationFileReadyRecord, stateChangeRecord, traceFileReadyRecord, traceLogRecord.

Type: DP

notification type

Description: This is to select messages specific to the type of notifications. Do not fill in if this criterion is not to be selected.

Value range: [attributeValueChange / communicationsAlarm / environmentalAlarm / equipmentAlarm / objectCreation / objectDeletion /processing Er-rorAlarm / qualityOfServiceAla rm / stateChange / specific]


Type: DP

Page 262 of 446 411-9001-124 18.08 1.0


numberOfJokerDS0 Class 2

Description: Number of jokers DS0 associated to one TDMA. The description applies to the Abis interface.


Object: transceiver

Feature: Data Backhaul Evolution (19174)

Default value: 0

Type: DP

Checks: • [C/M]: The numberOfJokerDS0 allowed values are:• [0..4] for S8000 BCF BTS model• [0..6] for S8000 CBCF, S12000 and e-cell BTS models• [0..8] for BTS 18000 BTS models

Checks: [C/M]: The numberOFJokerDS0 allowed values are:[0..4] for S8000 BCF BTS model[0..6] for S8000 CBCF, S12000 and e-cell BTS models[0..8] for BTS 6000 and BTS 18000 BTS models

Release: V15

Note: The recommended value is linked to target QoS and radio conditions. The value may be set to a non-zero value even if EDGE is not activated in corresponding TDMA.Resources will be reserved and unused in that case. However, it may help to properly configure a TDMA before activating EDGE.

number of records

Description: Number of records.


Type: DP

Remark: The attributes of the log objects are not managed by the users.

number of large reuse data channels Class 3

Description: Mean number of logical channels belonging to the larger frequency re-use pattern and used at the same time for data communications which is used for cell tiering.

Value range: [-16 to +16]


Type: DP

Release: V15

411-9001-124 18.08 1.0 Page 263 of 446


numberOfEnabledHDLCPorts

Description: Number of ’enabled’ HDLC ports in the TMU or IEM module. Operation-al State of the HDLC channels in the TMU/IEM modules. Operational State of the HDLC channels in the TMU/LSA modules. The global Op-erational State of the HDLC feature is given by the number of ports/channels with an individual operational state set to ’enabled’.This attribute is dynamically managed by the BSS. It is set to NULL at ’iem’ or ’tmu’ object instance creation. Value changes are not notified to the Manager. This attribute is relevant for BSC 3000.


Object: iem, tmu


Type: DD

Release: V13

Note: BSC 3000 V16: this parameter no more exists.

numberOfPwciSamples Class 3

Description: Minimum number of PwCI samples required to reach a reliable distribu-tion. This attribute allows the configuration of CellTieringConfiguration at bts level.




Default value: 20

Type: DP

Release: V12

Note: CellTiering mode must be activaed.

Page 264 of 446 411-9001-124 18.08 1.0


numberOfSlotsSpreadTrans Class 3

Description: Number of radio time slots RACH transmission accesses are spread in a random manner to avoid collisions.The information is broadcast to the mobiles at regular intervals on the cell BCCH.In the event of non-system response, the mobile renews the RACH bursts after a randomly defined period varying with numberOfS-lotsSpreadTrans.

MS Phase 1

The time T between two transmissions of the same RACH burst is the following:T= [D + (N+1) x 4.615]ms where• D is the maximum system response pending time:• N is the randomly number generated by the mobile in the range [0 to numberOfSlotsSpreadTrans-1]• 4.615 ms is the time occupied by a time slot.

MS Phase 2

The time T between two transmissions of the same RACH burst is the following (whichever is the BCCH, combined or not):T= 4.615 x [S+(N + 1)] ms where• S is a parameter depending on the BCCH configuration and on the value of numberOfSlotsSpreadTrans (see table hereafter)• N is the randomly number generated by the mobile in the range [0 to numberOfSlotsSpreadTrans-1]• 4.615 ms is the time occupied by a time slot.

NumberOfSlotsSpreadTrans S on not combined BCCH S on combined BCCH

3, 8, 14, 50 55 41

411-9001-124 18.08 1.0 Page 265 of 446


4, 9, 16 76 52

5, 10, 20 109 58

6, 11, 25 163 86

7, 12, 32 217 11

Value range: [3 to 12 / 14 / 16 / 20 / 25 / 32 / 50] time slots

Object: bts

Default value: 32

Type: DP

Note: The choice will depend on the quantities of GSM phase 1 and GSM phase 2 mobiles. For Mobile phase 1, numberOfSlotsSpreadTrans = 50leads to the lower double allocation rate. For Mobile phase 2, numberOfSlotsSpreadTrans = 6, 7, 11, 12, 25, 32 (respectively 5, 10, 20) for BCCH combined(respectively BCCH not combined) leads to the lower double allocation rate.Therefore, for a network that handles a combination of both types of mo-biles, numberOflotsSpreadTrans should be set to 32 (default value).

numberOfTCHFreeBeforeCongestion Class 3

Description: Minimum number of free TCHs triggering the beginning of the TCH con-gestion phase and the beginning of the traffic overload condition.


Object: bts

Default value: 0

Type: DP

Checks: • [C/M]: numberOfTCHFree BeforeCongestion numberOfTCHFree-ToEndCongestion

Release: V9

numberOfTCHFreeToEndCongestion Class 3

Description: A threshold giving the number of free TCHs, which triggers the end of TCH congestion phase and the end of the traffic overload condition (ad-ditionally, this parameter takes into account the preempted PDTCH).


Object: bts

Default value: 0

Type: DP

Checks: • [C/M]: numberOfTCHFreeToEndCongestion numberOfTCHFree-BeforeCongestion

Release: V9

Page 266 of 446 411-9001-124 18.08 1.0


numberOfTCHQueuedBeforeCongestion Class 3

Description: Maximum number of TCH allocation requests queued which triggers the beginning of the TCH congestion phase and the beginning of the traffic overload condition.


Object: bts

Default value: 0

Type: DP

Checks: • [C/M]: numberOfTCHQueuedBeforeCongestion numberOfTCH-QueuedToEndCongestion

Release: V9

numberOfTCHQueuedToEndCongestion Class 3

Description: Maximum number of TCH allocation requests queued triggering the end of the TCH congestion phase and the end of the traffic overload condi-tion.


Object: bts

Default value: 0

Type: DP

Checks: • [C/M]: numberOfTCHQueuedToEndCongestion numberOfTCH-QueuedBeforeCongestion

Release: V9

Number of XTP under this BSS

Description: Real number of XTP created under the BSC.

Value range: [0..NNNN]

Object: md - Display 4K Erlangs Informationbsc - Display 4K Erlangs Information


Release: V17

nUsfExt Class 3

Description: USF frequency during the second phase of the extended UL period

Value range: [0..100] (1 unit = 20 ms)

Note: Even if the nUsfExt parameter value is set to 0 or 1, the period remains equal to 40ms (nUsfExt=2); 2 being the minimum parameter value for PCU.

Object: bts


Default value: 0

411-9001-124 18.08 1.0 Page 267 of 446


2.15. O

Type: DP

Release: V15

nwExtUtbf Class 3

Description: Whether the Extended UpLink TBF feature is enabled or not.


Object: bts



Type: DP

Checks: • [M]: The following flag combination is prohibited: nwExtUtbf = en-abled and fullDlKa = sdisabled

Release: V15

objectClass

Description: Q3 object class

Value range: [adjacentCellHandOver / adjacentCellReselection /alarmRecord / bsc / bscCounterList / bscMdInterface / bts / btsSiteManager / callPathTrace / channel / efd /frequencyHoppingSystem / handOverControl / lapdLink /log / md / mdScanner / mdScanReportRecord / mdWarning/ network / observationFileReadyRecord / pcmCircuit/ powerControl / signallin-gLink / signallingLinkSet signallingPoint / software / stateChangeRecord /traceControl / traceFileReadyRecord / traceLogRecord/ transceiver / transceiverEquipment / transceiverZone /transcoder / xtp]

Object: alarmRecord, mdScanReportRecord, observationFileReadyRecord, stateChangeRecord, tracFileReadyRecord,traceLogRecord.

Type: DP

objectInstance

Description: Scope of an alarm criteria. It covers all network objects when undefined.


Type: DP

nUsfExt Class 3

Page 268 of 446 411-9001-124 18.08 1.0


object Filter List

Description: To select messages issued by one or several objects, and their subtree (optional).The object Filter List parameter includes the following components: ob-jects and scope.Click the Modify button to enter the names of the objects to be selected.The scope enables to select the subtree of an object.

Value range: objects [adjacentCellHandOver / adjacentCellReselection /adjacentCel-lUTRAN / atmRm / bsc /bscMdInterface / bts / btsSiteManager / cc / cem / cem3 / cemRc Bsc / cemRcTcu / channel / control node / frequency-HoppingSystem /handOverControl / hardware bsc 3G / hardware trans-coder 3G / hsaRc / hsaRc Tcu / ibos / iem / igm / interface node /iom / ipgRc / ipm / lapdLink / log / lsaRc Bsc / lsaRc Tcu /md / mdScanner / mdWarning / mms / network / omc / omu/ pcmCircuit / pcu / pcusn / pow-erControl / signallingLink/ signallingLinkSet / signallingPoint / software / sw8kRm /tmu / transceiver / transceiverEquipment / transceiverZone / transcoder / trm / xtp]


Type: DP

Release: V12

objects

Description: To select messages issued by one or several objects (50 objects max.), enter the concerned object class(es). This field must be empty to select all object classes.Do not fill in if this criterion is not to be selected. If a class is selected, the user may select one or more objects created in that class. If no object is selected, all messages issued by all objects created in the class are displayed.

Value range: [adjacentCellHandOver / adjacentCellReselection / alarmRecord / bsc / bscCounterList / bscMdInterface / bts / btsSiteManager / callPathTrace / channel /efd / frequencyHoppingSystem / handOverControl / lapdLink / log / md / mdScanner / mdScanReportRecord /mdWarning / network / observationFileReadyRecord / omc/ pcmCircuit / pcu / pcusn / power-Control / signallingLink/ signallingLinkSet / signallingPoint / software /stateChangeRecord / traceControl / traceFileReadyRecord/ traceLo-gRecord / transceiver / transceiverEquipment /transceiverZone / trans-coder / transcoderBoard / xtp]


Type: DP

objects assigned

Description: List of the BSSs assigned to the relay. Fill in the list with bsc object iden-tifiers or names.


Object: relay

Type: DP

Remark: A BSS can be assigned to several relays at the same time.

411-9001-124 18.08 1.0 Page 269 of 446


observation type

Description: Type of the observation.

Value range: [general Statistic / fast Statistic / real Time / diagnostic]


Type: DP

Release: V11

observation type

Description: Type of the observation.

Value range: [Observation real time / Observation fast statistic /Performance monitor]


Type: DP

Release: V11

observed counters

Description: List of counters (Q3 names) chosen for observation.


Value range: [list of Q3 counter names]

Type: DP

Release: V11

observed object class

Description: Class of object the user observes.

Value range: [bsc / btsSiteManager / bts / pcmCircuit / adjacentCellHandOver / trans-ceiverZone / transceiverEquipment / omu / tmu/ cc / cem / pcmPort / sig-nallingLink / channel / omc / md / machine]


Type: DP

Release: V11

occupationState

Description: Determines whether the PCM TS used by the terrestrial circuit is occu-pied by an SS7 channel. This attribute is significant provided the xtp ob-ject is unlocked.

Value range: [preempted / notPreempted]• preempted........ The terrestrial circuit is mapped on a time slot occu-pied by an SS7 channel on the Ater interface.• notPreempted..... The PCM time slot is available for the traffic.

Page 270 of 446 411-9001-124 18.08 1.0


Object: xtp

Type: DD

offsetLoad Class 3

Description: Load offset applied by the bsc to the cell selection process.



Feature: Handover decision according to adjacent cell priority and load (TF716 - V12)

Default value: 0

Type: DP

Checks: • [C/M]: This attribute must be in the range [0 to 63].

Notes: • When set to "0", no offset is effective.• This parameter is set to "0" for the cells that do not belong to the relat-ed bsc object.

Release: V12

offsetPriority Class 3

Description: Priority offset applied by the bsc to the cell selection process.



Feature: Handover decision according to adjacent cell priority and load (TF716 - V12)

Default value: 1

Type: DP

Checks: • [C/M]: This attribute must be in the range [1 to 5].

Release: V12

Note: "1" is the highest priority.

offsetPriorityUTRAN Class 3

Description: Priority offset applied by the bsc to the cell selection process

Value range: 1...5


Default value: 1

Type: DP

Checks:

Release: V17


occupationState

411-9001-124 18.08 1.0 Page 271 of 446


oMC notification number

Description: To select OMC-R manager notifications identified by a given number.Do not fill in this criterion if not to be selected.



Type: DP

omuId

Description: Identifier of the ’omu’ object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified and is relevant for BSC 3000 and TCU 3000.


Object: omu

Type: DP

Release: V13

on error

Description: Whether to stop running commands when an applicative error is detect-ed by the system (stop).

Value range: [stop / continue]


Type: DP

onlyExtUtbf Class 3

Description: Whether only Extended UpLink TBF mode is supported.


Object: bts



Type: DP

Release: V15

Note: The recommended value is ’enable’.

onePhaseAccess Class 2

Description: One phase access activation parameter.

Value range: [disabled / enabled / edgeEnabled / gprsEdgeEnabled]

Object: bts

Feature: GPRS TBF establishment improvement: one phase access (15015)

Page 272 of 446 411-9001-124 18.08 1.0



Type: DP

Checks: • [C/M]: Edge must be activated at cell level (egprsServices must be equal to enabled ) if onePhaseAccess is equal to edgeEnabled orgprsEdgeEnabled. Checks:• [C/M]: Edge must be activated (edgeDataService Type must be equal to full capabilities are requested) on BCCH TDMA (TDMA having lowest priority) if onePhaseAccess is equal to edgeEnabled or gprsEdgeEnabled

Notes: • "0" stands for disabled "One phase access".• "1" stands for enabled "One phase access".

Release: V15

onePhaseDnMsCapability Class 3

Description: Default number of DL TS to be considered for MS attempting a 1 phase access.


Object: bts

Feature: GPRS TBF establishment improvement: one phase access (15015)

Default value: 1

Type: DP

Release: V15

Note: Values 0 and 9 to 255 are interpreted as default value by the PCU.

operationalState



The state parameter combinations for the atmRm object are as follows:

administrative State operationalState availability Status

{} disabled notInstalled

{} disabled {}

{} disabled failed

{} disabled dependency

{} enabled {}

Object: atmRm


onePhaseAccess Class 2

411-9001-124 18.08 1.0 Page 273 of 446


Type: DD

Release: V13

operationalState



The state parameter combinations for the bsc object are as follows:

administrative State

operational State

availability Status Meaning

locked disabled {} The BSC has just been created or locked.

unlocked disabled {} The BSC is in restart or BDA build phase.

unlocked disabled dependency The BSS/OMC-R link is not created or the BSC database is not built.

unlocked disabled failed The BSC refuses every command, including resetting.

unlocked enabled {} The BSS/OMC-R link and the associations with the BSC are established, and the BSC database is built.

Object: bsc

Type: DD

operationalState



The state parameter combinations for the bscMdInterface object are as follows:


operational State


locked disabled {} The BSS/OMC-R link has been locked by a user.

unlocked disabled {} The link has just been created and the connection is not established yet (initial state).

unlocked disabled dependency The link is down.

Page 274 of 446 411-9001-124 18.08 1.0


unlocked disabled failed The connection cannot be reestablished.

unlocked enabled {} The connection is established.


Type: DD

operationalState



The state parameter combinations for the bts object are as follows:


operational State


locked disabled {} The cell has just been created or locked.

unlocked disabled dependency The radio site is not working or the TDMA frames are not correctly configured.

unlocked enabled {} The radio site is working and the number of TDMA frames correctly configured for the cell is reached.

shutting Down enabled busy The radio cell is being released following a soft release command.

Object: bts

Type: DD

operationalState



The state parameter combinations for the btsSiteManager object are as follows:


operational State


locked disabled {} The site has just been created or locked.

unlocked disabled {} Downloading in the site BCF is in-progress.

411-9001-124 18.08 1.0 Page 275 of 446


unlocked disabled dependency The PCM link used for the site LAPD signaling is faulty.

unlocked disabled failed Loss of Level 3 dialogue or configuration Abis message not correctly acknowledged or downloading problem

unlocked enabled {} The PCM is available for LAPD signaling, the Level 3 dialogue is established, and the configuration and Abis connection with the site BCF are OK.


Type: DD

operationalState

Description: ISO state. "disabled" means the BSC cannot send the messages to the OMC-R agent.


The state parameter combinations for the callPathTrace object are as follows:


operational State

usage State Meaning

locked enabled idle Call path tracing has just started in the BSC or has been stopped by the operator.

unlocked enabled busy Call path tracing is in-progress and messages are forwarded to the OMC-R agent.

unlocked enabled idle Call path tracing is stopped (end-of-session criterion is true).

unlocked enabled Call path tracing is in-progress but messages are not forwarded to the OMC-R agent.


Type: DD

operationalState



The state parameter combinations for the cc object are as follows:

Page 276 of 446 411-9001-124 18.08 1.0


operationalState availabilityStatus

disabled notInstalled

disabled {}

disabled failed

disabled dependency

enabled online

Object: cc


Type: DD

Release: V13

operationalState



The state parameter combinations for the cem object are as follows:


operational State availability Status

{} disabled notInstalled

{} disabled {}

{} disabled failed


{} enabled {}

Object: cem


Type: DD

Release: V13

operationalState



The state parameter combinations for the controlNode object are as follows:

411-9001-124 18.08 1.0 Page 277 of 446




{} disabled {}

{} disabled failed

{} disabled degraded

{} enabled online

Object: controlNode


Type: DD

Release: V13

operationalState



Object: efd

Type: DD

operationalState



The state parameter combinations for the g3BscEqp object are as follows:



{} disabled {}

{} enabled {}


Object: g3BscEqp


Type: DD

Release: V13

Page 278 of 446 411-9001-124 18.08 1.0


operationalState



The state parameter combinations for the g3Transcoder object are as follows:



{} disabled {}

{} disabled failed


{} enabled degraded

{} enabled {}



Type: DD

Release: V13

operationalState



The state parameter combinations for the hsaRc object are as follows:

operational State

availability Status

disabled dependency

disabled {}

degraded

disabled {}

Object: hsaRc

Feature: BSC 3000 optical

Type: DD

Release: V17

411-9001-124 18.08 1.0 Page 279 of 446


operationalState



The state parameter combinations for the iem object are as follows:



{} disabled not installed

{} disabled {}

{} disabled failed


{} enabled {}

Object: iem


Type: DD

Release: V13

operationalState



The state parameter combinations for the igm object are as follows:


Meaning

disabled notInstalled IGM not plugged

disabled failed software / hardware fault on IGM

enabled onLine IGM fully operational

enabled degraded IGM operational, but with fault on one or several fol-lowing interfaces: Ethernet port (Abis, IBOS, Aggrega-tion), optical fiber 0, optical fiber 1

Object: igm


Type: DD

Release: V18.0

Page 280 of 446 411-9001-124 18.08 1.0


operationalState



The state parameter combinations for the iom object are as follows:




{} disabled {}

{} disabled failed


{} enabled {}

Object: iom

Feature: BSC 3000 optical / TCU 3000 optical

Type: DD

Release: V17

operationalState



The state parameter combinations for the interfaceNode object are as follows:


disabled dependency

disabled {}

degraded

disabled {}



Type: DD

Release: V13

411-9001-124 18.08 1.0 Page 281 of 446


operationalState



The state parameter combinations for the ipgRc object are as follows:

operationalState availabilityStatus

disabled notInstalled

disabled {}

enabled degraded

enabled {}

Object: igm


Type: DD

Release: V18.0

operationalState



The state parameter combinations for the ipm object are as follows:


operational State


locked disabled {} IPM locked

locked disabled {}

unlocked enabled {} if IPM connected to IBOS

unlocked disabled {} if IPM is disconnected from IBOS

unlocked disabled failed if the IPM is disabled for more than 30 minutes

Object: ipm


Type: DD

Release: V18.0

Page 282 of 446 411-9001-124 18.08 1.0


operationalState



The state parameter combinations for the log object are as follows:

operational Stateavailability Status Meaning

disabled {} The disk message saving partition is full (current alarm log).

disabled logFull The disk message saving partition is full (current observation or trace log).

enabled {} The messages are actually saved in the partition.

Object: log

Type: DD

operationalState



The state parameter combinations for the lsaRc object are as follows:

operational State

availability Status

disabled dependency

disabled {}

enabled degraded

disabled {}

Object: lsaRc


Type: DD

Release: V13

411-9001-124 18.08 1.0 Page 283 of 446


operationalState

Description: ISO state. "disabled" means the BSC cannot send the messages to the OMC-R agent.


The state parameter combinations for the mdScanner object are as follows:


disabled {} The observation is running but the messages cannot be forwarded to the OMC-R agent.

disabled {offDuty} The observation is stopped and the messages cannot be forwarded to the OMC-R agent.

enabled {} The observation is running and the messages are forwarded to the OMC-R agent.

enabled {offDuty} The observation is stopped and the messages are forwarded to the OMC-R agent.

Object: mdScanner

Type: DD

operationalState



The state parameter combinations for the mms object are as follows:


operational State

availability Status

locked {} {}

Object: mms


Type: DD

Release: V13

operationalState


Page 284 of 446 411-9001-124 18.08 1.0



The state parameter combinations for the omu object are as follows:


operational State

availability Status

locked {} {}

Object: omu


Type: DD

Release: V13

operationalState



The state parameter combinations for the pcmCircuit object are as follows:


operational State


locked disabled {} The PCM has just been created or locked.

unlocked disabled dependency The TCU is faulty (A interface PCMs).

unlocked disabled failed The DDTI board or the internal PCM partner is faulty, or the connection is down.

unlocked enabled {} The DDTI board and the internal PCM partner are working and the connection is established.

Object: pcmCircuit

Type: DD

operationalState



The state parameter combinations for the pcu object are as follows:

operationalState

411-9001-124 18.08 1.0 Page 285 of 446



operational State


locked disabled {} The PCU has just been created or locked.

unlocked disabled dependency The Level 2 is not established or the connection with the BSC is down (external PCM).

unlocked enabled {} The PCU is working.

Object: pcu


Type: DD

Release: V12

operationalState



The state parameter combinations for the pcu object are as follows:


disabled {} The pcusn has just been created.

disabled dependency The pcusn object does not work, or the PCMlink does not work.

enabled {} The pcusn object is working.

Object: pcusn


Type: DD

Release: V12


operationalState



The state parameter combinations for the signallingLink object are as follows:

Page 286 of 446 411-9001-124 18.08 1.0



operational State


locked disabled {} The SS7 link has just been created or locked.

unlocked disabled dependency The PCM carrying the SS7 link is faulty or there is no MTP2 message between the BSC and the MSC.

unlocked disabled failed The CCS7 board is faulty.

unlocked enabled {} The PCM and CCS7 board are working and MTP2 messages are exchanged between the BSC and the MSC.


Type: DD

operationalState



The state parameter combinations for the sw8kRm object are as follows:


operational State

availability Status


{} disabled {}

{} disabled failed


{} enabled {}

Object: sw8kRm


Type: DD

Release: V13

operationalState


411-9001-124 18.08 1.0 Page 287 of 446



The state parameter combinations for the tmu object are as follows:


operational State

availability Status

locked disabled not installed

unlocked disabled {}

{} disabled failed


{} enabled degraded

{} enabled {}

Object: tmu


Type: DD

Release: V13

operationalState

Description: ISO state. "disabled" means the BSC cannot send themessages to the OMC-R agent.


The state parameter combinations for the traceControl object are as follows:


locked enabled Call tracing has not started or has been stopped, and the messages are forwarded to the OMC-R agent.

locked disabled Call tracing has been stopped and the messages cannot be forwarded to the OMC-R agent.

unlocked enabled Call tracing is in-progress in the BSC and the messages are forwarded to the OMC-R agent.

unlocked disabled Call tracing is in-progress but the messages cannot be forwarded to the OMC-R agent.


Type: DD

operationalState

Page 288 of 446 411-9001-124 18.08 1.0


operationalState



The state parameter combinations for the transceiver object are as follows:


disabled dependency The parent cell is not working or no TRX/DRX is available for the TDMA frame.

disabled failed The BTS has refused the TDMA frame configuration or is using the partnered TRX/DRX for BCCH filling purposes.

enabled {} The parent cell is working, a TRX/DRX is available for the TDMA frame, and the BTS has accepted the TDMA frame configuration.

Object: transceiver

Type: DD

operationalState



The state parameter combinations for the transceiverEquipment object are as follows:


operational State


locked disabled {} The TRX/DRX has just been created or locked.

unlocked disabled {} Downloading in the TRX/DRX is in-progress.

unlocked disabled dependency The parent radio site or the parent cell or the PCM link partner is not woring.

unlocked disabled failed The TRX/DRX is assigned to BCCH filling by the BTS or loss of Level 3 dialogue or Abis configuration message not correctly acknowledged or downloading problem or status regression.

411-9001-124 18.08 1.0 Page 289 of 446


unlocked enabled {} The parent cell is working, a PCM is available to the TRX/DRX, and the Level 3 dialogue is established.

shutting Down enabled {} The TRX/DRX is being released following a soft release command.


Type: DD

operationalState



The state parameter combinations for the transcoder object are as follows:


operational State


locked disabled {} The TCU has just been created or locked.

unlocked disabled dependency The internal PCM partner is faulty or the Level 2 is not established or the connection with the BSC is down (external PCM).

unlocked enabled {} The TCU is working.

Object: transcoder

Type: DD

operationalState



The state parameter combinations for the trm object are as follows:


operational State

availability Status

locked disabled not installed

unlocked disabled {}

{} disabled failed


{} enabled {}

Page 290 of 446 411-9001-124 18.08 1.0


Object: trm


Type: DD

Release: V13

operationalState



The state parameter combinations for the xtp object are as follows:


operational State

usage State


locked disabled idle {} The CIC has just been created or locked.

unlocked disabled idle dependency The PCM link partner is faulty.

unlocked disabled idle failed The CIC is preempted.

unlocked enabled idle {} The CIC is working and traffic-free.

unlocked enabled busy {} The CIC is working and traffic-busy.

shutting Down enabled busy {} The CIC is being released following a soft release command.

Object: xtp

Type: DD

otherServicesPriority Class 3

Description: An index in the table allocPriorityTable for a TCH allocation request (in signaling mode) whose cause is "other services".This priority is used in primo-allocations or when an SDDCH cannot be allocated for overload reasons.


Object: bts

Default value: 17

Type: DP

411-9001-124 18.08 1.0 Page 291 of 446


2.16. P

output classes

Description: List of authorized output classes defining a terminal output domain. Out-put classes grant access to various types of data.

Value range: [login window / OMC-R browser / alarm window / performance monitor] When the "login window" class is authorized, the "Login" window is au-tomatically displayed on the terminal screen outside work sessions.

Object: terminal profile

Type: DP

output classes

Description: List of authorized output classes defining a user’s output domain. Output classes grant access to various types of data.

Value range: [OMC-R browser / alarm window / performance monitor / command file manager / security manager / SMS-CB manager / description window / job scheduler window / alarm log window / system session log window / call traces window / Unix window / notification log window / notification window / relay manager / alarm criteria] The "notification log window" class gives access to the system notifica-tion log, while the "notification window" class gives access to the user notification log.


Type: DP

owner

Description: Name of the user creating the command file on the OMC-R.


Object: commandFile

Type: DP

packetAckTime Class 3Description: This parameter is composed of the following attributes:

• dwAckTime• upAckTimeThe deactivation value is 64 for both of them.Refer to these entries in this Dictionary.

Release: V12

Page 292 of 446 411-9001-124 18.08 1.0


packetFlowContext Class 3Description: This parameter is composed of the following attributes:

• pfcArp1ConversationalCSCallProtection

• pfcArp1StreamingCSCallProtectin





• pfcNrtRequestedDnMbrCounterThreshold

• pfcNrtRequestedUpMbrCounterThreshold

• pfcPreemptionRatioGold

• pfcPreemptionRatioSilver

• pfcRtDowngradeAllowed

• pfcRtRequestedDnGbrCounterThreshold

• pfcRtRequestedUpGbrCounterThreshold

• pfcT6

• pfcT8

• pfcTsGuaranteedBitRateDl

• pfcTsGuaranteedBitRateUl

Refer to these entries in this Dictionary.These attributes have no effect on the BSS if the pfcActivation param-eter is diabled.


Feature: BSS Packet Flow Context

Type: DP

Release: V16

Notes: • This parameter is mandatory. It is applicable to BSC 3000 only.• This parameter is part of the complex packetFlowConte xt attribute.

packetSiStatus Class 3Description: Activation of the System Information Status feature in the cell.


Object: bts

411-9001-124 18.08 1.0 Page 293 of 446



Feature: Network Assisted Cell Change for release 4 MS

Type: DP

Release: V16


pagingOnCell Class 3Description: Enables or disables paging requests in a cell.


Object: bts


Type: DP

Release: V9

pan Class 3Description: This parameter is composed of the following attributes:

• panInc

• panDec

• panMax

Refer to these entries in this Dictionary.

Release: V12

panDec Class 3 (pan)Description: The MS counter N3102 is decremented by panDec each time PUAN

timer expires

Value range: [0 (4s), 1 (8s), 2 (12s), 3 (16s), 4 (20s), 5 (24s), 6 (28s), 7 (32s)]

Object: bts


Default value: 0

Type: DP

Release: V12

Note: If the MS counter equals "0", an abnormal release is performed.

packetSiStatus Class 3

Page 294 of 446 411-9001-124 18.08 1.0


panInc Class 3 (pan)

Description: The MS counter N3102 is incremented by panInc each time a PUAN message which allows the transmit window to go forward is received.

Value range: [0 (4s), 1 (8s), 2 (12s), 3 (16s), 4 (20s), 5 (24s), 6 (28s), 7(32s)]

Object: bts


Default value: 0

Type: DP

Release: V12


panMax Class 3 (pan)

Description: Maximum value of the counter N3102 (used in case of block acknowl-edgment time out), set by the MS at each cell reselection.

Value range: [0 (4s), 1 (8s), 2 (12s), 3 (16s), 4 (20s), 5 (24s), 6 (28s), 7 (32s)]

Object: bts


Default value: 0

Type: DP

Release: V12


parameter(s)

Description: List of parameters to define when running the command file.Their generic format is $XXX, where $ identifies such a parameter and XXX is a string of uppercase, alphanumerical characters that does not contain spaces.

Object: commandFile

Type: DP

partialRecordCriteriaType Class 2Description: Criterion that defines the type of partial records to generate in the BSC.

Value range: [event type / numbered / timed / no partial]• event type ........ The BSC generates partial records each time a han-dover is successful (partialRecordCriteriaEvent-Type = "handover").• numbered ........ The BSC generates partial records every <N> suc-cessful handovers (partialRecordCriteriaNb-Event = [1 to 64]).• timed ............ The BSC generates partial records every <N> seconds (partialRecord-Criteria-Timer= [1 to 60]).• no partial ........ The BSC does not generate partial records.If "no partial" is selected, trace data are only recorded at the end of each traced call. If the traceControl object is locked before the end of a call, all related data are lost.

411-9001-124 18.08 1.0 Page 295 of 446



Type: DP

Checks: • [M]: The traceControl object is locked.

A traceControl object is created in locked state. Unlock the object to start collecting trace data in the related BSC.

partialRecordCriteriaEventTypeDescription: Create traceControl. Select this criterion when partialRecordCriteri-

aType is equal to "Event type".

Value range: handover

Type: DP

partialRecordCriteriaNbEventDescription: Create traceControl. Enter the number of events when partialrecordCri-

teriaType is equal to "Numbered".


Type: DP

partialrecordCriteriaTimerDescription: This parameter should be set to "Hand over" when

partialRecordCriteriaType is equal to "Event type".


Type: DP

particular interventionDescription: Type of action associated with an alarm criteria in the specific configura-

tion.



Type: DP

passwordDescription: User’s current password as defined in the user’s profile. It is not dis-

played.



Type: DP

partialRecordCriteriaType Class 2

Page 296 of 446 411-9001-124 18.08 1.0


passwordDescription: User’s password. It begins with a letter, contains at least one non-alpha-

betical character among the first eight characters, and is case sensitive.

Value range: [6 characters min]

Object: user profile - Create/Set

Type: DP

Checks: • [C/M]: The password begins with a letter and contains one non-alpha-numerical character among the first eight characters.• [C/M]: The password is at least six-character long.

password durationDescription: Maximum time during which the user’s current password is valid.

Value range: [2 to 2147483646] days When a password validity duration runs out, the password must be changed on opening the next work session.The user’s access to MMI commands is barred until the password is changed. Refer to the password status entry.


Type: DP

Note: It is possible for this parameter to take on an infinite value.If so, the password will not expire.

pcmCircuitDescription: Identifier of a pcmCircuit object defined with regard to a bsc object (Abis,

Ater, Lb, A_Lb, or Agprs interface). It is related to the number of the DDTI board to which the PCM described link is physically connected in the BSC. PCM links are identified by the DDTI boards to which they are connected in the BSC. A PCM link connected to DDTI board no.i has a reference equal to "2i" or "2i+1" (each board manages two links at a time). See NTP < 22 >, which gives the relationship between the number of a board and its physical location in the BSC equipment cabinet.When the PCM link is allotted to a site on the Abis interface, it is also identified by a reference number defined with regard to the site (pcmCir-cuitBtsSiteManager). Refer to the bscSitePcmList entry in the Dic-tionary.

Value range: [0..363]Max number of pcmCircuit T1: 0..168 (BSC 3000); 0..364 (BSC 3000 Optical); 0..88 (TCU 3G) Max number of pcmCircuit E1: 0..126 (BSC 3000); 0..252 (BSC 3000 Optical); 0..66 (TCU 3G)

Object: pcmCircuit (Abis, Ater, Lb, A_Lb and Agprs interfaces)


411-9001-124 18.08 1.0 Page 297 of 446


Type: Id

Checks: • [C]: The number of external PCM links allotted to a BSC on the Ater interface depends on the number of TCUs linked to the BSC (one TCU uses one link).• [C]: The software object related to the parent bsc object is created.• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked.• [D]: If the application database of the related BSC is built, the pcmCir-cuit object is locked.• [D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.• [D]: No btsSiteManager object (Abis PCM) or transcoder object (Ater PCM) or pcu object (Agprs PCM) refers to the pcmCircuit object.• [D]: No mdScanner object describing a temporary observation refers to the pcmCircuit object (no observation is running on the concerned PCM).

pcmCircuitDescription: Identifier of a pcmCircuit object defined with regard to a transcoder ob-

ject (A interface).


Type: Id

Checks: • [C]: The number of PCM links connected to a remote transcoder on the A interface is limited to maxPcmCTPerTranscd (static configuration data).• [C]: The parent transcoder object is created.• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked.• [D]: If the application database of the related BSC is built, the pcmCir-cuit object is locked.• [D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.• [D]: No signallingLink or xtp object refers to the pcmCircuit object.

pcmCircuitBscDescription: Identifier of a PCM link (pcmCircuit object) used by a radio site defined

with regard to the BSC. It is related to the number of the DDTI board to which the link is physically connected in the BSC.Refer to the bscSitePcmList entry in the Dictionary, which defines the relationship between these two attributes.

Value range: Depending on the BSC type, the value range is:• [0 to 167] for a BSC 3000


Type: DP

pcmCircuit

Page 298 of 446 411-9001-124 18.08 1.0


pcmCircuitBtsSiteManagerDescription: Identifier of the PCM link defined with regard to the BTS. It is related to

the number of the DTI or PCMI board to which the link is physically con-nected in the BTS.Refer to the bscSitePcmList entry in the Dictionary, which defines the relationship between these two attributes.



Type: DP

pcmCircuitIdDescription: Identifier of the PCM link used by a LAPD link.

Since all radio sites have a switching facility, the BSC can directly allo-cate the PCM link that supports a LAPD link.

Value range: [0 to 167] for BSC 3000

Object: lapdLink

Note: This parameter is only available for the lapdLink OML object on BSC 3000.

Type: DD

pcmCircuitId Class 2Description: Identifier of the PCM link used by an SS7 channel on the A interface, de-

fined with regard to the TCU.



Type: DP

Checks: • [C/M]: The pcmCircuit object is created for the transcoder object ref-erenced by thesignallingLink object (transcoderId).• [C/M]: If the described link is PCMA no.3, the time slot used by the SS7 channel (timeSlotNumber) is in the range [1 to 27] if the PCM link is an E1 link and in the range [1 to 20] if the PCM link is a T1 link.Since the last four time slots of that link are not mapped on the Ater in-terface, they are unusable (refer to the transcoderMatrix entry in the Dictionary).

pcmCircuitId Class 2Description: Description: Identifier of the PCM link used by a terrestrial circuit on the

A interface, defined with regard to the TCU.


Object: xtp

411-9001-124 18.08 1.0 Page 299 of 446


Type: DP

Checks: • [C/M]: The pcmCircuit object is created for the transcoder object ref-erenced by the xtp object (transcoderId).• [C/M]: If the described link is PCMA no.3, the time slot used by the ter-restrial circuit (timeSlotNumber ) is in the range [1 to 27] if the PCM link is an E1 link and in the range [1 to 20] if the PCM link is a T1 link. Since the last four time slots of that link are not mapped on the Ater interface, they are unusable (refer to the transcoderMatrix entry in theDictionary).

pcmErrorCorrection Class 2Description: Whether the bts uses the new ETF (Enhanced TRAU Frame) frame (set

to "1") or the ETSI "Rec 08.60" frame (set to "0").


Object: bts

Feature: PCM error correction (FM660 - V12)

Default value: 1

Type: DP

Checks: • [C/M] The "PCM error correction" feature is not supported anymore. This attribute cannot be set to 1 to forbid switching on the PCM errorcorrection feature.

Release: V12

Note: This parameter is only available for BTSs equipped with non mixed DCU4 or DRX transceiver architecture.

pcmNbr Class 2 (gprsPcuCrossConnectList)Description: Number of PCM links used for Agprs interface.

Value range: BSC 3000: [6 to 167]

Object: pcu


Default value: None

Type: DP

Release: V12

pcmTimeSlotNumber Class 2Description: For a TDM BTS, this parameter indicates the rendezvous time slot of the

site.For an IP BTS, this parameter indicates the time slot used for the main lapd on the BSC side. The time slot used for the main lapd, on the BTS side, is always DS0#1.

Value range: [1 to 31] if the PCM link is an E1 link[1 to 24] if the PCM link is a T1 link


Type: DP

pcmCircuitId Class 2

Page 300 of 446 411-9001-124 18.08 1.0


Checks: • [C/M]: The scheduled time slot is masked in the bstSiteManager object radioSiteMask, so it cannot be allotted by the BSC.

Notes: • The relation "scheduled time slot = teiBtsSiteManager + 1" is always true at BTS level.• It can be false at BSC level provided a PCM switching matrix is used between the BSC and the BTS; otherwise, it is true.

Release: V8

pcmType Class 0 (BSC 3000)Description: Interface on which the PCM link is used.

Value range: [pcmA / pcmAbis / pcmAter / pcmAgprs / pcmA_Lb / pcm_Lb]

Object: pcmCircuit


Type: DP

Checks: • [M]: If the current attribute value is pcmA, no signallingLink or xtpobject refers to that object (pcmTimeSlotNumber).• [M]: If the current attribute value is pcmAbis, no btsSiteManager object refers to that object (bscSitePcmList).

• [M]: If the current attribute value is pcmAter, no transcoder object re-fers to that object (pcmCircuitId ).

• [M]: If the current attribute value is pcmAgprs, no pcu object refers to that object (bscPcuPcmRefList ).

• [M]: pcmAbis is forbidden for pcmCircuitId equals 0, 2, 4, or 6.• [C/M]: signallingLink of Lb interface must be referenced to pcmCir-cuit of pcmLb or pcmA_Lb type.• [C/M]: signallingLink of A interface must be referenced to pcmCir-cuit of pcmA or pcmA_Lb type.

pcuDescription: Identifier of a pcu object defined with regard to a bsc object.


Object: pcu


Type: Id

Release: V12

pcmTimeSlotNumber Class 2

411-9001-124 18.08 1.0 Page 301 of 446


pcuCellStateDescription: From the BSC point of view, this parameter corresponds to the GPRS

configuration of the cell in the PCU. This is made possible through the messages exchanged between the BSC and the PCU.

Value range: [0, Not Significant;1, GPRS: no PDTCH channels created;2, GPRS: out of service;3, GPRS: service OML configuring;4, GPRS: service RSL configuring;5, GPRS: in service;6, GPRS: service unavailable -OML;7, GPRS: service unavailable - Gbdown;8, GPRS: service unavailable - BVC KO]

Object: pcu

Type: DD

Release: V16

pcusnDescription: Identifier of a pcusn object.


Object: pcusn


Type: Id

Release: V12

pcuSNNameDescription: Reference name of a PCUSN object on the OMC-R.

It begins with a letter and is case sensitive.


Object: pcusn

Type: DP

Checks: • [C/M]: The name of a pcuSN is unique to the OMC-R.

Release: V12

Note: Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (such as TRX, BSC, BTS, BTSSM). All other symbols/characters are prohibited.The valid symbols are: letter characters: A, B, C..., Z, a, b, c..., z- digit symbols: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 - minus sign: -- undescore: _

Page 302 of 446 411-9001-124 18.08 1.0


penaltyTime Class 3Description: Timer used by an idle mobile before re-selecting a cell (C2 criterion).

When a mobile places the cell on the list of strongest carriers, it starts a timer that stops after penaltyTimeseconds. This timer is reset when the mobile removes the cell from the list.For the entire timer duration, the re-selection criterion (C2) is assigned a negative temporaryOffset value.Refer to the cellReselectOffset entry in the Dictionary.

Value range: [20 to 640, by steps of 20] seconds. The value "640" is reserved and in-dicates that the temporary offset is ignored in the re-selection criterion (C2) calculation. It also changes the sign in the C2 formula.

Object: bts

Feature: AR 264

Default value: 20

Type: DP

Release: V8

perceived severityDescription: To select messages according to the priority.

The alarm processing priority provides an indication of how it is per-ceived that the capability of the managed object has been affected. Re-fer to the alarmPriority entry in the Dictionary where the priority levels are explained.

Value range: [cleared / critical / indeterminate / major / minor / warning] Do not fill in if this criterion is not to be selected.


Type: DP

periodicityDescription: Time between two runs if the job is to be periodically run.

Value range: [1 to 2147483646] minute(s)

Object: job

Condition: To define if it is a periodic job.

Type: DP

pfcActivation Class 2Description: Activates the Packet Flow Context feature in the cell.


Object: bts



Type: DP

411-9001-124 18.08 1.0 Page 303 of 446


Release: V16


pfcArp1ConversationalCSCallProtection Class 3Description: Indicates if the real time PFCs Conversational of ARP 1 (allocation / re-

tention priorities 1) are protected against voice preemption. This param-eter is not used.





Type: DP

Note: This parameter is part of the complex packetFlowContext attribute.

Release: V16

pfcArp1StreamingCSCallProtection Class 3Description: Indicates if the real time PFCs Streaming of ARP 1 (allocation / retention

priorities 1) are protected against voice preemption.





Type: DP



Release: V16







Type: DP


Release: V16

pfcActivation Class 2

Page 304 of 446 411-9001-124 18.08 1.0



priorities 2) are protected against voice preemption.





Type: DP


Release: V16







Type: DP


Release: V16


priorities 3) are protected against voice preemption. This parameter is not used.





Type: DP


Release: V16

pfcFlowControlActivation Class 2Description: Activates the flow control of the Packet Flow Context in the cell.


Object: bts

411-9001-124 18.08 1.0 Page 305 of 446




Type: DP

Checks: • [M]: If pfcActivation is disabled, it is not allowed to enable pfcFlow-ControlActivation.

Release: V16

Note: This parameter is optional. It is applicable to BSC 3000 only.

pfcMinNrtBandwidthPerTs Class 3Description: Specifies the percentage of each TS of the TDMA which is reserved for

non real time PFC (including MSs with no PFC). This parameter is used for the admission control ofa real time PFC.


Object: transceiver

Default value: 0


Type: DP

Release: V16


Note: The value ‘0’ or a very low value may result in a TBF with only NRT PFC not being allocated enough bandwidth. This results in TBF drops. The value ‘0’ is internally converted to 1 inside the PCU.

Note: The value ‘100’ or a very high value may result in all RT PFC being downgraded or deleted. This value is internally converted to 99 inside PCU.

pfcMinNumberOfJokersforTsGuaranteedBitRate Class 3Description: Number of jokers that are needed to guarantee both uplink and downlink

throughputs in any location of the cell. Refer to the pfcTsGuranteedBi-tRateUl and the pfcTsGuranteedBitRateDl entries in this dictionary.

Value range: [0 to 4] 16 kbit/s PCM TS

Object: transceiver

Default value: 0


Type: DP

Checks: • [C/M]: pfcMinNumberOfJoker sforTsGuaranteedBitRate’ must be lower than or equal to minNbOfJokersPerConnectedMain so that real timePFC can be accepted when dynamic Agprs is activated.


Release: V16

pfcFlowControlActivation Class 2

Page 306 of 446 411-9001-124 18.08 1.0


pfcNrtRequestedDnMbrCounterThreshold Class 3Description: Threshold used by the pcuPfcNrtRequestedDnMbrGTThres counter

(C15267). For more information, refer to Kapsch GSM BSS Perfor-mance Management — Observation Counters Dictionary (411-9001125).

Value range: [0..568] kbit/s

[0..568] kbit/s powerControl

Default value: 0 (all requests are taken into account)


Type: DP


Release: V16

pfcNrtRequestedUpMbrCounterThreshold Class 3Description: Threshold used by the pcuPfcNrtRequestedUpMbrGTThres counter

(C15268). For more information, refer to Kapsch GSM BSS Perfor-mance Management — Observation Counters Dictionary (411-9001-125).





Type: DP


Release: V16

pfcPreemptionRatioGold Class 3Description: Defines the percentage of raw radio bandwidth a gold NRT PFC (THP1)

may preempt from silver and bronze NRT PFC (THP2 or THP3 or back-ground or MS without PFC support)

Value range: [0.00 to 93.750] by step of 0.5%


Default value: 0 (no preemption)

Type: DP

Release: V14 (renamed in V16)

Note: The value may be decreased to lower the impact on Silver and Bronze subscribers when the traffic is high.

411-9001-124 18.08 1.0 Page 307 of 446


pfcPreemptionRatioSilver Class 3Description: Defines the percentage of raw radio bandwidth a silver NRT PFC (THP2)

may preempt from bronze NRT PFC (THP3 or background or MS with-out PFC support)

Value range: [0.00 to 93.750] by step of 0.5%


Default value: 0 (no preemption)

Type: DP

Release: V14 (renamed in V16)

Note: The value may be decreased to lower the impact on Bronze subscribers when the traffic is high.

pfcRtDowngradeAllowed Class 3Description: In case the guaranteed bit rate of a real time PFC cannot be granted, this

parameter indicates whether the PFC is deleted or downgraded into a non real time PFC. If it is downgraded into a non real time PFC, the pa-rameter specifies which traffic class and PFC are used for the down-grade.

Value range: [downgrade not allowed / downgrade to interactive THP1 / downgrade to interactive THP2 / downgrade to interactive THP3 / downgrade to back-ground]


Default value: downgrade not allowed


Type: DP


Release: V16

pfcRtRequestedDnGbrCounterThreshold Class 3Description: Threshold used by the pcuPfcRtRequestedDnGbrGTThres counter

(C15265). For more information, refer to Kapsch GSM BSS Perfor-mance Management — Observation Counters Dictionary (411-9001-125).





Type: DP


Release: V16

Page 308 of 446 411-9001-124 18.08 1.0


pfcRtRequestedUpGbrCounterThreshold Class 3Description: Threshold used by the pcuPfcRtRequestedUpGbrGTThres counter

(C15266). For more information, refer to Kapsch GSM BSS Performance Management — Observation Counters Dictionary (411-9001-125).





Type: DP


Release: V16

pfcT6 Class 3Description: pfcT6 is the guard timer for the Download Packet Flow Context proce-

dure.

Value range: [0.1 to 10] seconds by step of 0.1 second


Default value: 0


Type: DP


Release: V16

pfcT8 Class 3Description: pfcT8 is the guard timer for the Modify Packet Flow Context

procedure.

Value range: [0.1 to 10] seconds by step of 0.1 second


Default value: 0


Type: DP

DP This parameter is part of the complex packetFlowContext attribute.

Release: V16

pfcTsGuaranteedBitRateDl Class 3Description: For an EDGE MS, specifies the downlink throughput which is guaran-

teed in any location of the cell.


Default value: 0

411-9001-124 18.08 1.0 Page 309 of 446



Type: DP


Release: V16

pfcTsGuaranteedBitRateUl Class 3Description: For an EDGE MS, specifies the uplink throughput which is guaranteed

in any location of the cell.

Value range: [1 to 60] kbit/s


Default value: 0


Type: DP


Release: V16

plmnPermitted Class 3Description: List of NCC of the PLMNs on which MSs are allowed to take measure-

ments for handovers. Listening to the PLMN to which the cell belongs must be authorized.


Object: bts

Default value:

Type: DP

pODTypeDescription: Type of the BSC or BTS involved, as defined in the Physical Objects Dic-

tionary.

Value range: [ BTSoutdoor / BTSindoor / BTSmicro / BTSsmart ]


Type: DP

pointCode Class 1Description: MSC identifier in the SS7 network (Destination Point Code).

Value range: • in ETSI SS7 protocol [0 to 16383]• in ANSI SS7 protocol [0 to 16777215]


Type: DP

pfcTsGuaranteedBitRateDl Class 3

Page 310 of 446 411-9001-124 18.08 1.0


pointCode Class 1Description: BSC identifier in the SS7 network (Origin Point Code).

Value range: • in ETSI SS7 protocol [0 to 16383]• in ANSI SS7 protocol [0 to 16777215]


Type: DP

port Ethernet operationalDescription: Operational state of the OMU external Ethernet port.

ISO operational state (enabled/disabled).This attribute is dynamically managed by the BSS. Value changes are not notified to the Manager.This attribute is relevant for BSC 3000.

Value range: [enabled/disabled]

Object: omu


Type: DD

Release: V13

port Ethernet statusDescription: Availability status of the OMU module external Ethernet port.

ISO availability status ({}, {dependency}, {failed}).This attribute is dynamically managed by the BSS. Value changes are not notified to the Manager.This attribute is relevant for BSC 3000.


Object: omu


Type: DD

Release: V13

positionInShelfDescription: Indicates the position of a module in a shelf.


Object: atmRm, cc, cem, iem, lsaRc, mms, omu, sw8kRm, tmu, trm, hsaRc, hsaRcTcu, iom


Type: DD

Release: V13

411-9001-124 18.08 1.0 Page 311 of 446


positionInShelf Class 0Description: Defines the slot position for the IGM.

Value range: • for bsc30000electrical_ip: 1, 2

• for bsc3000optical_ip: 9,10

Object: igm


Type: DP

Release: V18.0

positionInShelf Class 0Description: Defines the slot position for the ipgRc. IGM0 is the reference used for

the ipgRc position in the shelf.

Value range: • for bsc30000electrical_ip: 1

• for bsc3000optical_ip: 9

Object: ipgRc


Type: DP

Release: V18.0

powerBudgetInterCell Class 3Description: Authorization to perform intercell handovers for power budget.




Type: DP

powerClassDescription: Transmission power class of a TDMA frame.

Value range: [powerClass5 (GSM 900 network, GSM-R network, E-GSM, GSM 850 - GSM 1900 and GSM 900 - GSM 1800 network) powerClass1 (GSM 1800 network, GSM 1900 network, GSM 1800 - GSM 900 network and GSM 1900 - GSM 850)]

Object: transceiver

Default value: powerClass1

Type: DP

Page 312 of 446 411-9001-124 18.08 1.0


Checks: • [C]: The attribute value complies with the type of network in which the TDMA frame is used. Refer to the standardIndicator entry in the Dictionary (attribute of the parent bts object).


powerControlDescription: Identifier of a powerControl object that defines the power control man-

agement parameters in a cell. A bts object may reference one and only one object of this type.



Type: Id

Checks: • [C]: The associated bts object is created and the powerControl object is not created for that object.• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked and the associated bts object is locked.

• [M]: The parent bsc object is unlocked.• [M/D]: The powerControl object is created.

• [D]: The associated bts object is not referenced, except by an handO-verControl object.


powerControlIndicator Class 3Description: Whether MS signal strength measurements include measurements on

BCCH. BCCH measurements must not be included when the following two conditions are met:• The radio channel hops at least on two different frequencies, including the BCCH frequency.• Power control on the downlink is used.

Value range: [include BCCH measurements / do not include BCCH measurements] This parameter should only be used with cavity coupling.

Object: bts

Default value: include BCCH measurements

Type: DP

powerIncrStepSizeUpLink Class 3Description: Increment step size for uplink power control. This is applicable to BSC

3000 only.This attribute is modified by the Manager. Value changes are notified to the Manager.This attribute can only be modified if the ’bsc’ object instance is un-locked.This attribute can only be modified if the ’bts’ objectinstance is unlocked.


powerClass

411-9001-124 18.08 1.0 Page 313 of 446



Default value: 4

Type: DP

Checks: • 0566CO01: The attribute ’powerIncrStepSizeUL’ must verify: ’1RxLevULP’ + ’powerIncrStepSizeUL’ <= ’uRxLevULP’

Release: V14


powerIncrStepSizeDownLink Class 3Description: Increment step size for downlink power control. This is applicable to

BSC 3000 only.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’bsc’ object instance is un-locked.This attribute can only be modified if the ’bts’ object instance is unlocked.



Default value: 4

Type: DP

Checks: • 0565CO01 - The attribute ’powerIncrStepSizeDL’ must verify:’1RxLevDLP’ + ’powerIncrStepSizeDL’ <= ’uRxLevDLP’

Release: V14

powerRedStepSizeDownLink Class 3Description: Decrement step size for downlink power control. This is applicable to

BSC 3000 only.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’bsc’ object instance is un-locked.This attribute can only be modified if the ’bts’ object instance is unlocked.



Default value: 2

Type: DP

Checks: • 0567CO01 - The attribute ’powerRedStepSizeDL’ must verify: ’uRx-LevDLP’ - ’powerRedStepSizeDL’ >= ’1RxLevDLP’

Release: V14


powerIncrStepSizeUpLink Class 3

Page 314 of 446 411-9001-124 18.08 1.0


powerRedStepSizeUpLink Class 3Description: Decrement step size for uplink power control. This is applicable to BSC

3000 only.This attribute is modified by the Manager.Value changes are notified to the Manager.This attribute can only be modified if the ’bsc’ object instance is un-locked.This attribute can only be modified if the ’bts’ object instance is unlocked.



Default value: 2

Type: DP

Checks: • 0568CO01-The attribute ’powerRedStepSizeUL’ must verify: ’uRxLev-ULP’ - ’powerRedStepSizeUL’ >= ’1RxLevULP’

Release: V14


preemptionAuthor Class 3Description: Defines the preemption management

Value range: [forbidden, authorizedWithRelease, authorizedForcedHO]


Default value: forbidden

Feature: ASCI (GSM-R V12)

Type: DP

Release: V12

Note: authorizedForcedHO option is not available.

preemptionConfiguration Class 3Description: This parameter is composed of preemptionAuthor and eMLPPThresh-

old. Refer to these entries in the Dictionary.


Type: DP

Release: V14

preferredNonAdaptativeAMRcodec Class 3Description: This parameter is used to activate/deactivate AMR NB codec for group

(VGCS or VBS) calls. This attribute establishes an AMR call on a FR channel with the specified AMR codec modes.

Object: bsc

Value range: 0, 4.75, 5.9, 6.7, 10.2

Default value: 0

411-9001-124 18.08 1.0 Page 315 of 446


Type: DP

Release: V18 P&C3

Note: This new parameter “preferredNonAdaptativeAMRcodec” is applicable only for the AMR Group calls. This parameter has RTU semantic control on SET ([M]).

pRequestedCodec Class 3Description: This attribute defines the "p" parameter in the AMR "(n,p) voting" mech-

anism.This attribute can only be modified if the ’handOverControl’ object in-stance is unlocked.

Value range: Int [12 to 192] in steps of 12


Default value: 48

Type: DP

Release: V14


preemptionConfiguration Class 3Description: This parameter is composed of preemptionAuthor and eMLPPThresh-

old. Refer to these entries in the Dictionary.


Type: DP

Release: V14

preSynchroTimingAdvance Class 3Description: Pre-defined timing advance used in a pre-synchronized handover pro-

cedure between the serving cell and this neighbor cell.This value of timing advance is used when the parameter "synchro-nized" is set to "pre sync HO with timing advance".The operator defines a predefined timing advance when a phase 2 MS goes from the serving cell to this neighbor cell approximately at the same place (railway, highway).

Value range: [0 to 35] (km)


Default value: Refer to parameter synchronized

Type: DP

Release: V10

preferredNonAdaptativeAMRcodec Class 3

Page 316 of 446 411-9001-124 18.08 1.0


priority Class 2Description: Priority level of a TDMA frame.

Among the set of TDMA frames attached to the cell, only the one carry-ing the cell BCCH must be allotted the highest priority [0].At least <minNbOfTDMA> TDMA frames related to a cell (refer to this entry in the Dictionary) must be successfully configured for the cell to be working. They include the TDMA frame carrying the cell BCCH and those with the highest priority(ies). If this is true when the cell is brought into service, then, the cell will be working. Otherwise, its operational-State will be "disabled" and its availabilityStatus will be "{dependen-cy}".


Object: transceiver

Type: DP

Checks: • [M]: The parent bsc object is unlocked and the associated bts object is locked.

privateMmsOmuRefDescription: Pointer to the associated ’omu’ object instance for private MMS, NULL

for shared-mirrored MMS.This attribute cannot be modified.It is set by the MD-R at MMS creation.


Object: mms


Type: DP

Release: V13

privilegedCell Class 3Description: Allows to segregate cells according to their mapping on Agprs PCM.

Value range: [no, yes]

Object: bts

Default value: no

Feature: Optimized Agprs cell allocation

Type: DP

Release: V16

Notes: • This parameter is mandatory. It is applicable to BSC 3000 only.• This parameter is of class 3. No modification of its value is taken into account by the BSC immediately and it does not trigger any re-configu-ration of Agprs.

411-9001-124 18.08 1.0 Page 317 of 446


probable causeDescription: To select messages according to the numerical value of the ISO proba-

bleCause field.Do not fill in if this criterion is not to be selected.The following table indicates the messages displayed according to the probable cause.

Alarm type Probable cause Value

Communications Execution failure of a MD request by the BSCCall establishment errorCommunication protocol errorCommunication subsystem failureCorrupt dataDegraded signalDTE-DCE interface errorLAN errorLocal node transmission errorLoss of frameLoss of signalReceive failureRemote node transmission errorTransmit failure

624569121325272829404254

Environmental External alarm loopEnclosure door openFire detectedHeating, ventilation, or cooling systemMaterial supply exhausted

5814182130

Equipment Equipment absentEquipment malfunctionHeating, ventilation, or cooling system problemInput/output device errorInput device errorMaterial supply exhaustedPower problemProcessor problemReceive failureReceiver failureStorage capacity problemTemperature unacceptableTiming problemTransmit failureTransmitter failure

601521232430353740414950525455

Page 318 of 446 411-9001-124 18.08 1.0


ProcessingError Cause of restart or switchoverNo responseApplication subsystem failureConfiguration or customization errorCorrupt dataFile errorOut of memoryQueue size exceededSoftware errorSoftware program abnormally terminatedSoftware program errorStorage capacity problemUnderlying resource unavailableVersion mismatch

5961279173239464748495657

QualityOfService ShutdownCongestionPerformance degradedQueue size exceededResource at or nearing capacityResponse time excessiveRetransmission rate excessiveThreshold crossed

638343943444551



Type: DP

processor identityDescription: This parameter is composed of the bsc equipment name and the

equipment processor number parameters. Refer to these entries in the Dictionary.

Object: mdWarning (create)

Type: DP

Release: V11

Note: During the command "create mdWarning", the operator can define ei-ther "equipment identity" or "processor identity", but not both.

pwciHrequave Class 3Description: Cell Tiering Mode parameter.

This is the averaging window size for powerControl.This attribute allows to configure the cellTieringConfiguration parameter at bts level.

Note: Cell Tiering mode must be activated.



Default value: 8

Type: DP

411-9001-124 18.08 1.0 Page 319 of 446


2.17. Q

2.18. R

qsearchC Class 3Description: The MS searches for UMTS

cells if level is above orbelow the threshold when theserving BCCH frequency ispart of the BA_List

Value range: 0:"<-98 dBm"1: “< -94 dBm”2: “< -90 dBm”3: “< -86 dBm”4: “< -82 dBm”5: “< -78 dBm”6: “< -74 dBm”7: “always”8: “> -78 dBm”9: “> -74 dBm”10: “> -70 dBm”11: “> -66 dBm”12: “> -62 dBm”13: “> -58 dBm”14: “> -54 dBm”15: “never”

QsearchC < -XX dBm: the HO towards theUMTS can be done only if the RxLev from the serving cell is below -XX.QsearchC > -XX dBm: the HO towards theUMTS canbe done only if the RxLevfromthe serving cell is above -XX. "values different from"always" and "never" areuseful only if serving BCCH ispart of BA_List in SI5"


Default value: 15

Type: DP

Checks:

Release: V17

Notes: This parameter is available only for BSC 3000.

radChanSelIntThreshold Class 3Description: Maximum interference level on free radio channels, below which are ar-

ranged in groups of priority allocation.The information is used to allocate free channels with the lowest inter-ference level. The levels depend on the thresholdInterference attribute value defined for the cell. Refer to this entry in the Dictionary.The BSC distributes free radio channels among two groups:• The first group contains the list of channels with a measured averaged interference level equal to or lower than the defined level.• The second group contains the list of channels with a measured aver-aged interference level higher than the defined level, and recently re-leased channels for which no measurement is available.Four resource pools are defined for each SDCCH or TCH type of chan-nel:• low interference level radio channels that are authorized to hop• low interference level radio channels not authorized to hop• high interference level radio channels authorized to hop• high interference level radio channels not authorized to hop

Page 320 of 446 411-9001-124 18.08 1.0


FIGURE 9. Channels are allocated cyclically inside each pool



Default value: 1

Type: DP

Release: V8

radioLinkTimeOut Class 3Description: Maximum value of the counter (S) associated with the downlink SACCH

messages, beyond which the radio link is cut off. It is lower than or equal to t3109.Mobiles comply with system operating conditions when the counter (S) is assigned a value lower than or equal to t3109.If the receiver is unable to decode a downlink SACCH message (BTS-to-MS direction), the counter is decreased by 1. If the message is re-ceived, the counter is increased by 2. When the counter goes down to zero, the radio link is declared "faulty".

411-9001-124 18.08 1.0 Page 321 of 446


Value range: [4 to 64, by steps of 4] SACCH frames (1 unit = 480 ms on TCHs, 470 ms on SDCCHs)

Object: bts

Default value: 20 SACCH

Type: DP

Checks: • [C/M]: radioLinkTimeOut t3109.

Notes: • The rlf1 attribute serves the same goal on the uplink.• The system

radioSiteMask Class 2Description: Definition of the PCM time slots used by a site. TS n is masked when bit

n is set to 0, it is used when bit n is set to 1 in the binary field.The radio site mask is immediately displayed in the hexadecimal field just below. The radio site mask is setusing the hexadecimal field as well as the binary field.The mask defines the time slots used in each PCM link allotted to a giv-en radio site. Time slot allocation is managed by the BSC; a time slot available on a site is used either by a radio time slot for traffic purposes or by a LAPD link which does not carry the link with the site BCF for sig-naling.A PCM E1 link carries thirty-two time slots. TS 0 (least significant bit) is always masked since it cannot be used. The radioSiteMask of a site us-ing E1 links is as follows:

radioSiteMask = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx0 | | | | |TS31 23 15 7 TS0

A PCM T1 link carries twenty-four time slots. The radioSiteMask of a site using T1 links is as follows:

radioSiteMask = XXXXXXXXXXXXXXXXXXXXXXXX | |TS24 TS1

Sites that do not share PCM links are assigned the full set.

In a BTS chain, the scheduled time slots of each radio site must be al-lotted in ascending order (such as TS1, TS2, TS3), beginning with the site closest to the BSC. Refer to the pcmTimeSlotNumber entry.

Value range: [32-bit mask]

Page 322 of 446 411-9001-124 18.08 1.0



Type: DP

Checks: • [C/M]: TS 0 cannot be assigned.• [C/M]: If PCM T1 links are used, TSs 25 to 31 cannot be assigned.• [C/M]: The radioSiteMask of all sites sharing a same PCM link (drop and insert connections) are dissociated.• [M]: The scheduled time slot of the radio site (pcmTimeSlotNumber) is masked [0] since it cannot be used.

radioSiteMaskOffset Class 2Description: The radioSiteMaskOffset parameter provides the de-correlation of the

radio site mask used on BTS site with the radio site mask used on BSC side (refer to the radioSiteMask entry).

On BTS side, the mask is the result of a calculation using the ra-dioSiteMask value and the radioSiteMaskOffset parameter.

According to the radioSiteMaskOffset value (named s below), the radio site mask on BTS side (RSMbts) is:

• s = 0: RSMbts and RSMbsc are identical• s > 0: If RSMbsc is [TSm..TSn] then RSMbts is [TSm-s..TSn-s]• s < 0: If RSMbsc is [TSm..TSn] then RSMbts is [TSm+|s|..TSn+|s|]

Example 1: if RSMbsc is [TS31..TS28] and s = +26, then RSMbts is [TS05..TS02].

Example 2: if RSMbsc is [TS05..TS02] and s = -19, then RSMbts is [TS24..TS21].

Value range: Int [-28 to 28]


Type: DP

Checks: • [C/M]: If the radioSiteMaskOffset is positive, the lowest TS number of the resultant BTS radio site mask must be greater than or equal to 1.• [C/M]: If the radioSiteMaskOffset is negative, the greatest TS number of the resultant BTS radio site mask must be lower than or equal to 31 (case of an E1 PCM) or to 24 (case of a T1 PCM). • [C/M]: the radioSiteMaskOffset is in the range [-28, +28] (case of an E1 PCM) or in the range [-21,+21] (case of a T1 PCM).• [C/M]: When the btsType parameter is set to IP or when a btsSiteM-anager object is created with he btsType parameter set to IP, the ra-dioSiteMaskOffset parameter must be equal to 0.

Release: V14

radioSiteNameDescription: Reference name of a multiple site object on the OMC-R. It begins with a

letter and is case sensitive.The name of a multiple site can be used in all MMI commands to refer-ence the multiple site on the OMC-R.



Type: DP

radioSiteMask Class 2

411-9001-124 18.08 1.0 Page 323 of 446


Checks: • [C/M]: The name of a multiple site is unique to the OMC-R.

Note: Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (such as TRX, BSC, BTS, BTSSM). All other symbols/characters are prohibited.The valid symbols are:- letter characters: A, B, C..., Z, a, b, c..., z- digit symbols: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9- minus sign: -- undescore: _- space

radResSupBusyTimer Class 3Description: Maximum time that SDCCH or TCH can be continuously occupied with-

out generating an alarm.

Value range: [1 to 18] hours

Object: bsc

Default value: 3

Type: DP

Release: V8

radResSupervision Class 3Description: Indicates whether radio resources are controlled at the cell level (both

busy resources and free resources).When no control is performed, no alarm related to the use or non use of an SDCCH or TCH is generated. Refer to the radResSupBusyTimer and radResSupFreeTimer entries in the Dictionary.


Object: bts

Default value: true

Type: DP

Notes: • radResSupBusyTimer and radResSupFreeTimer can be set automat-ically by the OMC-R calendar function.• The activation of this feature does not induce any signaling or CPU overload. Only the BSS-OMC-R link is overloaded at a rate of radResSupBusyTimer or radResSupFreeTimer.

Release: V8

radResSupFreeTimer Class 3Description: Maximum time an SDCCH or TCH can be continuously free without gen-

erating an alarm.

Value range: [1 to 18] hours

Object: bsc

Default value: 18

radioSiteName

Page 324 of 446 411-9001-124 18.08 1.0


Type: DP

Release: V8

rangeDescription: Time period chosen over which the counter values are read.

Value range: [5 min / 15 min / 30 min / 60 min / 2 hours]


Notes: • The authorized values for OFS observation type are 60 min, 2 hours, 6 hours, 12 hours, and 24 hours.• The authorized values for ORT and Performance Monitor observation types are 5 min, 15 min, 30 min, 60 min, and 2 hours.

Type: DP

reception timeDescription: To select messages received at that time.

Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in if this criterion is not to be selected.



Type: DP

record referenceDescription: Identifier of a user call as recorded in a call monitoring data file.


Object: Call monitoring - Display (SDO)

Type: DP

Checks: • [A]: It is in the range [0 to 63].• [A]: This parameter is mandatory when a user call report (Events op-tion) or a radio measurements report (Measurements option) is request-ed.• [A]: It can be undefined when a synthesis report (Synthesis option) is requested. In that case, a summary of all user recorded calls is dis-played.

radResSupFreeTimer Class 3

411-9001-124 18.08 1.0 Page 325 of 446


redundantPcmNumberDescription: Number of the redundant PCM link defined on BSC end.

This dynamic attribute is displayed provided the btsSiteManager object redundantPcmPresence attributevalue is "true".



Type: DD

Remark: A redundant link is not normally used for traffic or signaling connections.

redundantPcmPresence Class 2Description: Presence of a redundant PCM link on a radio site



Type: DP

Checks: • [M]: If the attribute value is "true", the object bscSitePcmList attribute includes two items, one identifies the PCM active link, and the other identifies the PCM redundant link.

refPeriodDescription: Reference counting period when a counter is involved.



Condition: To define if a counter is associated with the criteria.

Type: DP

refPeriodDescription: Reference counting period used by the "excessiveAnomal yRate" func-

tion.This attribute is not used by the detection "outOfRangeCo unter" func-tion. In that case, the reference period is set as follows:• For cumulative counters, the thresholds define total values not to be reached during a one minute reference period.• For load or value counters, the thresholds define maximum or mini-mum average values not to be reached during a 1 minute reference pe-riod, except for the PCM unavailability counters for which they define total values not to be reached during the reference observation period.The BSS observation counter threshold crossing detection mechanism is described in Kapsch GSM BSS Fundamentals — Operating Principles (411-9001-007).


Page 326 of 446 411-9001-124 18.08 1.0



Type: DP

related bts site manager listDescription: Lists the btsSiteManager Ids connected to the IPM / RIPM / IPM-USER

/ RIPM-USER (up to 1 btsSiteManagers per IPM only).

Object: ipm

Value range: list of up to 1btsSiteManager Id only



Type: DP

Release: V18.0

relatedSoftwaresDescription: This attribute identifies the list of software identified separately. This list

represents the units of software ready for equipment use. This attribute is allocated by the MD-R at object creation. This attribute is not modified by the Manager.



Type: DP

Release: V13

relayDescription: Identifier of a BSS alarm relay which activates an external alarm loop

when the counter of immediate unacknowledged alarms shows a non-zero value for one of the BSSs assigned to the relay. BSS relays transfer the state of the associated BSS immediate action alarm counters to re-mote sites.A BSS relay is associated with several BSCs. Conversely, a BSC is si-multaneously assigned to several relays.


Object: relay

Type: Id

Reminder: OMC-R relays are used to transfer the state of system alarm counters to remote sites and are not managed by users.

refPeriod

411-9001-124 18.08 1.0 Page 327 of 446


remoteSsuStateDescription: State of the remote subsystem (BSSAP)

Value range: [inService / outOfService]• inService ................. The MSC BSSAP service is working for the BSC.• outOfService ..... The MSC BSSAP service is not working.


Type: DD

repetition rateDescription: Periodicity of short message broadcasting.

Each concerned BSC repeatedly sends the selected short message to the BTSs covering the selected cells at the repetition rate defined by the user.Each BTS repeatedly broadcasts the short message to all mobiles un-der its control, using the same repetition rate.

Value range: [2 sec. / 30 sec. / 1 min. / 2 min. / 4 min. / 8 min. / 16 min./ 32 min.]

Object: short message - Start broadcast

Type: DP

report rangeDescription: Time period over which the counter values are read.

Value range: [5 min. / 15 min. / 30 min. / 60 min. / 2 hours / 6 hours / 12 hours / 24 hours]


Type: DP

Notes: • The authorized values for OFS observation type are 60 min., 2 hours, 6 hours, 12 hours, and 24 hours.• The authorized values for ORT and Performance Monitor observation types are 5 min., 15 min., 30 min., 60 min., and 2 hours.

Release: V11

report templateDescription: Identifier of the report template object defined with regard to the bsc ob-

ject.



Type: DP

Release: V11

Page 328 of 446 411-9001-124 18.08 1.0


report typeDescription: A type of observation report.

Value range: [single observed instance / several observed instance]• single observed instance ........several observedcounters on a single object• several observed instance ....... single counter observed on severalobjects


Type: DP

Release: V11

reportObjLevelDescription: Level of the report to edit.

Fill in only when editing a permanent bsc report. Examples: "bsc = all" or "bsc = 1 & bsc = 2".

Value range: [adjacentCellHandOver / bsc / bts / transceiverZone / hardwareTcu3G]


Type: DP

Checks: • [A]: If specific objects are entered, they all belong to the same class.

reportTypeMeasurement Class 3Description: Type of measurement: normal or enhanced

Value range: Measurement report (0) / Enhanced Measurement Report (1)

Object: bts

Default value: 0

Type: DP

Checks: • M: Parameter reportTypeMeasurement shall not be changed if inter-ferenceMatrixRunningOnBts is equal to yes. This purpose of this check is to forbid activation and deactivation of EMR if interference matrix fea-ture is already activated on the cell.

Release: V17

retransDuration Class 2Description: Maximum number of occurrences of a same paging sub-group separat-

ing the first and last transmissions of the same paging message.


Object: bts

Default value: 10

Type: DP

411-9001-124 18.08 1.0 Page 329 of 446


Checks: • [C/M]: retransDuration (delayBetweenRetrans + 1) x nbOfRepeat

Release: V8

retry on errorDescription: Whether commands are rerun when the system detects an application

error.This parameter has priority over the on error parameter. When its value is "True", the error command is rerun; when it is "False", the on error parameter is analyzed.The errors involved, the time between reruns, and the maximum number of reruns are defined in static configuration data.

Value range: [true / false] (default is False)


Type: DP

rlf1 Class 2Description: Value to compute the initial and maximum value of the (CT)

counter used in the BTS radio link control algorithm.The FP (FrameProcessor) in the BTS runs the following algorithm to monitor the uplink SACCHs (MS-to-BTS direction):• The FP sets the CT counter to 0 at channel activation.• On each correct SACCH, the following occurs: — if (CT=0) then CT=4*rlf1 + 4 else CT=min (4*rlf1 +4, CT+rlf2)• On each incorrect SACCH, the following occurs: — CT = max(0, CT-rlf3) — When CT reaches 0, a CONNECTION FAILURE INDICATION mes-sage is sent to the BSC every T3115 until a Deactivate SACCH or RF CHANNEL RELEASE message is received.


Object: bts

Default value: 4

Type: DP

Notes: • The radioLinkTimeOut attribute serves the same goal on the down-link.• The system does not check that the values of the two attributes are consistent.

Release: V8

rlf2 Class 2Description: Step value by which the (CT) counter is increased by the radio link con-

trol algorithm when an uplink SACCH is decoded.Refer to the rlf1 entry.

Value range: [1 to 4] SACCH frames

Object: bts

Default value: 2

retransDuration Class 2

Page 330 of 446 411-9001-124 18.08 1.0


Type: DP

Release: V8

rlf3 Class 2Description: Step value by which the (CT) counter is decreased by the radio link con-

trol algorithm when an uplink SACCH is not decoded.Refer to the rlf1 entry.

Value range: [1 to 4] SACCH frames

Object: bts

Default value: 1

Type: DP

Release: V8

rLCPolling Class 3Description: Configuring the polling frequency for DL TBF.

Value range: [0 to 2]• 0 selects the original polling frequency of 240 ms and deactivates this feature• 1 selects a polling frequency which doubles the original to every 120 ms (during the first 240 ms, then adding one opportunity to setup a UL TBF)• 2 selects a polling frequency which quadruples the original to every 60 ms (during the first 240 ms, then adding three opportunities to setup a UL TBF)

Object: bts

Default value: 0

Type: DP

Release: V15

rmpConfStateDescription: State of radio measurement processing in the TDMA frame.

Value range: [configured / not configured / not significant]• configured: The CURRENT CELL PARAMETER, NEIGHBOUR CELL PARAMETER (and EXTENDED NEIGHBOUR CELL PARAMETER when more than sixteen defined neighbor cells) messages have been acknowledged by the BTS.• not configured: The messages have not been acknowledged by the BTS. If a CURRENT CELL PARAMETER message is not acknowl-edged, thenotification 1258 "Non response during the configuration of the remote L1M" is issued. If a NEIGHBOUR CELL PARAMETER or EX-TENDED NEIGHBOUR CELL PARAMETER message is not acknowl-edged, the notification 1259 "Negative acknowledgement of a distant L1M command" is issued.• not significant: The BTS has not sent the messages to the BSC (either the TDMA frame is not working or SYS INFO was not acknowledged).

Object: transceiver

Type: DD

rlf2 Class 2

411-9001-124 18.08 1.0 Page 331 of 446


rNCId Class 3Description: RNC identity of the UMTS neighbouring cell for HO


Object: adjacentCellUTRA N

Default value: N.A.

Type: DP

Checks: • [C]: The set of attributes cId, rNCId, mobileCountryCodeUTRAN and mobileNetworkCodeUTRANmust be unique among all the instances of the objects adjacentCellUTRAN attached to the same bts.

Release: V17


rndAccTimAdvThreshold Class 3Description: MS-to-BTS distance beyond which mobile access requests to a cell are

refused.It defines the maximum timing advance value accepted.The effective timing advance value is broadcast in the CHANNEL RE-QUIRED message sent by the BTS to the BSC. If it is above the user defined threshold, the BSC ignores the request.

Value range: [2 to 135] km (non-extended mode)[2 to 120] km (extended mode)

Object: bts

Default value: 35

Type: DP

Checks: • [C/M]: The maximum distance is 35 km if the bts object extended cell attribute is "false".• [C/M]: The maximum distance is 120 km if the extended cell attribute of the bts object is "true".

Release: V8

The number of access requests that are refused for that reason is ac-counted by the BSC (permanent bsc observation counter 1161/6) and fed back to the OMC-R.

routingArea Class 2Description: GPRS Cell Global Identifier (locationAreaCode + cellIdentity + routin-

gArea).


Object: bts


Default value: 0

Release: V12

Note: A Routing Area is necessarily included in a Location Area.

Page 332 of 446 411-9001-124 18.08 1.0


rowPositionDescription: Position number which identifies the position within a row.

Value range: String from 1 to 4 characters

Object: transcoder, controlNode, interfaceNode, hardware transcoder 3G

Type: DP

runCallClear Class 3Description: Number of "Measurement Results" messages received before the call

clearing algorithm in a cell is triggered.

Value range: [1 to 31] SACCH frames (1 unit = 480 ms on TCHs, 470 ms on SDCCHs)

Object: bts

Default value: 16

runHandOver Class 3Description: Number of "Measurement Results" messages received before the han-

dover algorithm in a cell is triggered.


Object: bts

Default value: 1

Type: DP

runPwrControl Class 3Description: Number of "Measurement Results" messages received before the pow-

er control algorithm in a cell is triggered.


Object: bts

Default value: 4

Type: DP

rxLevAccessMin Class 3Description: Minimum signal strength level received by the mobiles for being granted

access to a cell. The information is sent to MS prior to registering.As an example, a threshold level of -104 dB corresponds to an accept-able BER of approximately 10-2 (minimum recommended value).

Value range: [less than -110, -110 to -109, ... , -49 to -48, more than -48]dB

411-9001-124 18.08 1.0 Page 333 of 446


Object: bts

Default value: less than -110 dB

Type: DP

rxLevDLIH Class 3Description: Maximum interference level in BTS-to-MS direction, beyond which an in-

tra-cell handover may be triggered.




Type: DP

rxLevDLPBGT Class 3Description: Downlink signal strength threshold above which handovers for power

budget are inhibited.In certain issues, the operator may prevent handover for power budget in case of the received level in the serving cell is good enough that a handover does not improve thesituation.This parameter shall be set such as rxLevDLPBGT lRxLevDLH.



Default value: more than -48

Type: DP

Notes: • This parameter is disabled by setting it to the default value: more than -48 (dB).• This parameter is only available for DCU4 or DRX transceiver archi-tecture. It is disabled for DCU2 architecture.

Release: V11

rxLevDLPbgtUTRAN Class 3Description: Downlink signal strength threshold above which handovers to UTRAN

for power budget are inhibited

Value range: <-110 ... >-48 dBm


Default value: 63 (on MOD), “>-48” (on MMI)?

Type: DP

Checks:

Release: V17


rxLevAccessMin Class 3

Page 334 of 446 411-9001-124 18.08 1.0


rxLevHreqave Class 3Description: Number of signal strength measurements performed on a serving cell,

used to compute arithmetic strength averages in handover and power control algorithms.

Value range: [1 to 10] number of measurement results


Default value: 8

Type: DP

rxLevHreqaveBeg Class3Description: Number of measurement reports on current cell for signal strength arith-

metic average for early handover mechanism.Refer to the rxLevHreqave entry in the Dictionary. This parameter is coupled with hoMarginBeg and rxNCellHreqaveBeg use.



Default value: 2

Type: DP

Notes: • This parameter is set such as rxLevHreqaveBeg rxLevHreqave.• This parameter is only available for DCU4 or DRX transceiver archi-tecture.

Release: V11

rxLevHreqt Class 3Description: Number of arithmetic averages taken into account to compute the

weighted average signal strength in handover and power control algo-rithms. Each is calculated fromrxLevHreqave signal strength measurements on a serving cell.



Default value: 1

Type: DP

Checks: • [C/M]: It is equal to the number of weights inrxLevWtsList (refer to this entry in theDictionary).

rxLevMinCell Class 3Description: Minimum signal strength level received by MS for being granted access

to a neighbor cell.



411-9001-124 18.08 1.0 Page 335 of 446


Default value: -95 to -94 dB (GSM 900 or 850), -93 to -92 (GSM 1800 or 1900)

Type: DP

rxLevMinCellUTRAN Class 3Description: Minimum signal strength level received by MS for being granted access

to an UMTS neighbour cell

Value range: <-110...>-48


Default value: 63 (on MOD), “>-48” (on MMI)

Type: DP

Checks:

Release: V17


rxLevNCellHreqaveBeg Class 3Description: Number of measurement results used in early handover algorithm to

compute the average neighboring signal strength.Refer to the rxNCellHreqave entry in this dictionary.This parameter is coupled with hoMarginBeg and rxLevHreqaveBeg use.



Default value: 2

Type: DP

rxLevRxQualDistributionActivation Class 3Description: Defines the frequency of RxLev and RxQual distribution.

This is not used in this version.Only values 0, 1 and 2 are valid.This attribute is modified by the Manager.Value changes are notified to the Manager.


Object: bts

Type: DP

Release: V14

rxLevMinCell Class 3

Page 336 of 446 411-9001-124 18.08 1.0


rxLevULIH Class 3Description: The maximum interference level in MS-to-BTS direction, beyond which

an intra-cell handover is triggered.

Value range: [less than -110, -110 to -109, ..., -49 to -48, more than -48] dB, without Uplink Mapping Feature activated. [less than -117, ... , more than -42] dB, when the Uplink MappingFeature is used.


Feature: Uplink Mapping (TF 876)


Type: DP

rxLevWtsList Class 3Description: Values of weights used for signal strength weighed average.

The L1M function first calculates rxLevHreqave arithmetic averages from raw measurements, and balances rxLevHreqt averages among those with the weights defined in rxLevWtsList.Each arithmetic average is partnered with one weight in the list. Weight/average associations are set in the order the weights are recorded. The latest computed arithmetic average is always partnered with the first weight in the list.Super-average = [ (averagei x weighti)] / 100, i = 1 to rxLevHreqt



Default value: 100

Type: DP

Checks: • [M]: The number of weights in the list is equal to rxLevHreqt and their sum equals 100.

rxNCellHreqave Class 3Description: Number of measurement results used in the Power Budget algorithm to

compute the average neighboring signal strength.No weighted average is computed for this category of measurement.



Default value: 8

Type: DP

411-9001-124 18.08 1.0 Page 337 of 446


rxQualAveBeg Class 3Description: This attribute defines the number of quality measures used by the power

control mechanism, in case of hopping TS or fast MS.This attribute is modified if the ’handOverControl’ object instance is un-locked.



Default value: 2

Type: DP

Release: V14


rxQualDLIH Class 3Description: Bit error rate threshold in BTS-to-MS direction for intracell handover,

above which a handover may be triggered.




Type: DP

Release: V12

rxQualHreqave Class 3Description: Number of arithmetic averages taken into account to compute the

weighted average bit error rate in handover and power control algo-rithms. Each is calculated from rxQualHreqave bit error rate (BER) mea-surements on a radio link.



Default value: 1

Type: DP

rxQualHreqt Class 3Description: Number of bit error rate measurements performed on a radio link, used

to compute arithmetic bit error rate averages in handover and power control algorithms.



Default value: 8

Type: DP

Page 338 of 446 411-9001-124 18.08 1.0


2.19. S

rxQualULIH Class 3Description: Bit error rate threshold in MS-to-BTS direction for intracell handover,

above which a handover may be triggered.




Type: DP

Release: V14

rxQualThresholdDistribution Class 3Description: RxQual threshold for taking into account measurements in

RxLev and Interf matrix distributions.This attribute is modified by the Manager.Value changes are notified to the Manager.

Value range: [inferiorTo02 / between02and04 / between04and08 / between08and16 / between16and32 / between32and64 / between64and128 / superiorTo128]

Object: bts

Type: DP

Release: V14

rxQualWtsList Class 3Description: List of up to sixteen weights used to compute the average bit error rate

on a radio link.The L1M function calculates rxQualHreqave arithmetic averages from raw measurements, and balances rxQualHreqt averages among those with the weights defined in rxQualWtsList.Each arithmetic average is partnered with one weight in the list. Weight/average associations are set in the order the weights are recorded. The latest computed arithmetic average is always partnered with the first weight in the list.



Default value: 100

Type: DP

sIkAssociatedTmuPortPositionDescription: Gives the TMU and port number bearing the SS7 signaling.

Value range: [tmuPos / hardwareSlotPositionNMC / portNumber]


411-9001-124 18.08 1.0 Page 339 of 446


Type: DD

Release: V14

sIkATerResourceDescription: Gives the Ater PCM and TS bearing SS7 signaling..

Value range: pcmRef [0 to 167] ts [1 to 31]


Type: DD

Release: V14

sacchPowerOffset Class 2Description: Describes the power offset that applies to SACCH frames

Value range: [0..6] dB; step = 2

Object: bts

Type: DP

Feature:: Tx power offset for signaling channels

Default value: 0 (no power offset)

Notes: This parameter applies to BSC 3000 V16 and higher.

Release: V16

sacchPowerOffsetSelection Class 2Description: Describes the CODEC selection for applying a power offset on SACCH

messages.

Value range: [NULL / FR 4.75 kbps / FR 5.9 and lower / FR 6.7 and lower]

Object: bts

Type: DP


Default value: NULL (no power offset for SACCH)


Release: V16

sapiDescription: The Service Access Point Indicator defining the type of LAPD link use.

Value range: [RSL / OML]

Object: lapdLink

Type: DP


sIkAssociatedTmuPortPosition

Page 340 of 446 411-9001-124 18.08 1.0


scannerIdDescription: The identifier of the mdScanner object describing the observation.

Value range: [0 to 2147483646] "0" identifies the OMC-R permanent manager obser-vation. For a BSS observation or the OMC-R agent permanent observa-tion, this parameter must match the reference number of an mdScanner object.


Type: DP

Checks: • [A]: If the request concerns a BSS observation or the OMC-R agent permanent observation, the related mdScanner object is created.

scannerIdDescription: The identifier of the mdScanner object describing the observation.

Value range: 0 to 2147483646] "0" identifies the OMC-R permanent manager observation.For a BSS observation or the OMC-R agent permanent observation, this parameter must match the reference number of an mdScanner object.


Type: DP

Checks: • [A]: If the request concerns a BSS observation or the OMC-R agent permanent observation, the related mdScanner object is created.

sCCPRoutingIndicatorDescription: Indicated which route the SCCP takes.

Value range: [international/national]


Type: DP


scramblingCode Class 3Description: Scrambling code of the UMTS cell



Default value: 0

Type: DP

Release: V17

411-9001-124 18.08 1.0 Page 341 of 446


Checks: [C/M]: The set of attributes fDDARFCN and scramblingCode mustbe unique among all the instances of the objects adjacentCellUTRAN at-tached to the same bts• [C/M/D]: fDDARFCN or scramblingCode can’t be changed if Interfer-

ence Matrix feature is activated on the bts

Note: This parameter is only available for the BSC 3000.

unequippedCircuit Class 1Description: This attribute specifies if the automatic handover adaptation mechanism

is enabled/disabled.This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute is modified only if the ’bts’ object instance isunlocked.

Value range: [Enabled/Disabled]

Object: bts


Type: DP

Release: V14


selfTuningObs Class 3Description: BTS mode sending the PwCI distribution on the Abis interface. This at-

tribute allows the configuration of CellTieringConfiguration at BTS level.

Note: CellTiering mode must be activated.

Value range: [pwCi distribution not sent, pwCi distribution sent after gathering, one pwCi distribution sent per hour]



Type: DP

Release: V12

Note: PWCI distribution may be gathered and sent onto the Abis interface in-dependently of tiering activation.

sequenceNumberDescription: Tracing the record identification number.

Object: traceFileReady

Type: DP

scramblingCode Class 3

Page 342 of 446 411-9001-124 18.08 1.0


serial numberDescription: Three fields (geographical scope, message code, update number) iden-

tify a particular message from the source and type indicated by the Mes-sage Identifier are altered every time a given Message Identifier is changed.

Value range: [geographical scope, message code, update number]• geographical scope .. [immediate cell wide normal PLMN wide normal location area wide normal cell wide]• message code ..... [0 to 1023] differentiate messages from same source and type (same Message Identifier)• update number .... [0 to 15]differentiate older and newer versions of the same message

Object: short message - Display broadcast characteristics

Type: DP

serial numberDescription: Three fields (geographical scope, message code, update number) iden-

tify a particular message from the source and type indicated by the Mes-sage Identifier are altered every time a given Message Identifier is changed.

Value range: [geographical scope, message code, update number]• geographical scope .. [immediate cell wide normal PLMN wide normal location area wide normal cell wide]• message code ..... [0 to 1023] differentiate messages from same source and type (same Message Identifier)• update number .... [0 to 15 differentiate older and newer versions of the same message

Object: short message - Display broadcast characteristics

Type: DP

servingBandReporting Class 3Description: Number of GSM cells in the serving band to be reported in the list of

strongest cells in the EMR message

Value range: 0: “No inband cell is favoured”1: “1 strongest inband cell is favoured”2: “2 strongest inband cells are favoured”3: “3 strongest inband cells are favoured”

Object: bts

Default value: 3

Type DP


411-9001-124 18.08 1.0 Page 343 of 446


servingBandReportingOffset Class 3Description: Offset to apply to the reported value when prioritizing the cells for

reporting for GSM serving frequency band

Value range: 0..7 on MOD (corresponding to 0, 6, , 42 dB. on MMI), + 0xFF on MOD corresponding to ”not significant” on MMI


Default value: not significant

Type: DP

Release: V17


servingFactorOffset Class 3Description: This attribute defines the offset linked to the serving cell, used to de-

crease the HO margin, in some specific cases.This attribute is only modified if the ’handOverControl’ object instance is unlocked.



Default value: -2

Type: DP

Release V14


session context saving modeDescription: Session context saving mode.

Value range: [automatic when logout / on user request]


Type: DP

Release: V10

sGSNRelease Class 3Description: The parameter is set to ’0’ when the SGSN supports rel’98

or older and set to ’1’ when the SGSN supports rel’99.

Value range: ["SGSN is rel’98 or older" (SGSNR = ’0’)"SGSN is rel’99 onwards" (SGSNR = ’1’)

Object: bts

Default value: 0

Feature: EDGE Traffic Management (20231)

Page 344 of 446 411-9001-124 18.08 1.0


Type: DP

Release: V15

sharedPDTCHratioDescription: This parameter defines the percentage of shared PDTCH TS (config-

ured and available) taken into account in the filtered_erlang.


Object: bts

Feature: AMR maximization

Default value: 100

Type: DP

Release: V18.0

shelfNumberDescription: Indicates the position of a module in a shelf.


Object: atmRm, cc, cem, iem, lsaRc, mms, omu, sw8kRm, tmu, trm, hsaRc, hsaRcTcu, iom

Feature: AR 1209 - V13.1 - V13.1

Type: DD

Release: V13

shelfNumber Class 0Description: Defines the shelf number for the IGM.


• for bscoptical_ip: 1

Object: igm


Type: DP

Release: V18.0

shelfNumber Class 0Description: Defines the shelf number for the ipgRc.


• for bscoptical_ip: 1

Object: ipgRc

sGSNRelease Class 3

411-9001-124 18.08 1.0 Page 345 of 446



Type: DP

Release: V18.0

short messageDescription: An identifier (name) of a short message on the OMC-R.

A message name identifies the short message on the OMC-R; it is not relayed to the BSC during broadcasting. It can be changed by the Re-name command (see the new name entry in the Dictionary).Setting a short message characteristics does not affect the current broadcast of the message. The change will be effective when a new broadcast command is launched.A short message broadcasting is identified on the OMC-R by a unique serial number assigned by the system when broadcasting is initiated (refer to this entry in the Dictionary).



Type: Id

Checks: • C]: The name of a short message is unique to the OMC-R.• [M]: The short message is created.• [D]: The short message is not being broadcast.

signallin-gLink

Description: This field provides the Signaling Link (SLK) identifier. It is a sub-param-eter field of SignallingLinkResourcesStates

Value range: See signallingLinkObjectInstance; signallingLinkId range.


Default value: Not applicable

Type: DD

Release: V17

Note: This parameter is only for BSC 3000.Only the signallingLinkId part of this field is displayed at the MMI.

signallingLinkIdDescription: Identifier of a signallingLink object defined with regard to a

signallingLinkSet object.



Type: Id

shelfNumber Class 0

Page 346 of 446 411-9001-124 18.08 1.0


Checks: • [C]: The number of signaling links controlled by a BSC is limited to maxSigLPerSigLS (static configuration data).• [C]: The maximum number of signallingLink objects for Lb interface is 2.• [C/M]: The referenced pcmCircuit object (pcmCircuitId) is assigned to the A interface and depends on the same transcoder object (trans-coderId) as the signallingLink object.• [C/M]: The referenced PCM,TS pair (pcmCircuitId and timeSlot-Number) is not already assigned to a signallingLink or xtp object depen-dent onthe same transcoder object, and the time slotis not mapped on the TS used by the OMC channel on the Ater interface.• [C/M]: If the SS7 link uses PCMA link no.3 (pcmCircuitId), the timeS-lotNumber is in the range [1 to 27] if the PCM link is an E1 link or in the range [1 to 20] if the PCM link is a T1 link. Since the last four time slots of that link are not mapped on the Ater interface, they are unusable (refer to the transcoderMatrix entry in the Dictionary).• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked.

Checks: • [D]: If the application database of the related BSC is built, the signal-lingLink object is locked.[D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.• [D]: No mdScanner object refers to the signallingLink object (no obser-vation is running on that object).

signallingLinkResourcesStatesDescription: Gives Dynamic Datas (DDs) on all SLKs below the signallingLinkSet ob-

ject. This parameter is composed of the following sub-parameter fields: signallingLInk, slkAssociatedTmuPortPosition, slkATerResource, slkAResource, signallingLinkResState

Value range: Contains up to 16 elements



Type: DD

Notes: • This parameter is available only for BSC 3000.• This parameter is an array with a variable amount of elements. Each element carries information about the path of one SLK of the beam.

Release: V17

signallingLinkResStateDescription: SS7 channel resource state. It is a sub-parameter field of signallin-

gLinkResourcesStates.

Value range: [blocked / inhibited / inhibitedLocal / inhibitedDistant / inhibitedL ocalD-istant / inhibitedBlocked / notInhibitedNotBlocked]• inhibited ............. state enforced by a user SetInhibit command• inhibitedLocal ......... state enforced by a user• inhibitedDistant ........ state enforced by the MSC• inhibitedLocalDistant .. state enforced by a user and the MSC• blocked .............. state enforced by the MSC following a loss of dia-logue between MTP2 and MTP3


Type: DD

signallingLinkId

411-9001-124 18.08 1.0 Page 347 of 446


signallingLinkResState fieldDescription: This field provides Signaling Link (SLK) resource state.

Value range: See the SignallingLinkResStateN MCType type. [inhibited/blocked, localInhibited/ distantInhibited/ distantLocalInhibited]



Type: DD

Release: V17

Note: This field is only for BSC 3000.Note that the state available will be displayed when this variable length array will contain no item.

signallingLinkSetDescription: Identifier of a signallingLinkSet object describing the route (not the link-

set) between the BSC and MSC, or the BSC and SMLC.

Value range: [0 to 1] where signallingLinkSet[0] represents A interface and signallin-gLinkSet[1] represents Lb interface.


Type: Id

Checks: • [C]: The signallingLinkSet object is not created for the parent signal-lingPoint object.• [C]: If the application database of the related BSC is built, the parent bsc object is unlocked.• [D]: The application database of the related BSC has been reset by an Off line reset BDA command.

signallingPointDescription: Identifier of a signallingPoint object describing a BSC-MSC link on the

BSC.



Type: Id

Checks: • [C]: The signallingPoint object is not created for the parent bsc object.• [C]: The software object related to the parent bsc object is created.• [C]: If the application database of the related BSC is built, the parent bsc object is unlocked.• [D]: The application database of the related BSC has been reset by an Off line reset BDA command.

Page 348 of 446 411-9001-124 18.08 1.0


sigPowerOverboost Class 3Description: Reserved for future use.

Value range: [0dB to 1.6dB]

Object: bts

Default value: 0dB

Type: DP

Checks: • [C/M]: sigPowerOverboost cannot be set to 1.6 because bsPower-Control is not enabled or bts is not a BTS18000 or is not operating in 1900 MHz frequency band• [C/M]: sigPowerOverboost cannot be set to 1.6 because bsPower-Control is not enabled or bts is not a BTS 6000 or BTS18000 or is not operating in 1900 MHz frequency band

Release: V16

siteDescription: Name that identifies the site.

Value range: String [1 to 16 characters]


Type: DD

siteGsmFctList Class 2Description: List of up to 14 elements identifying the GSM functions configured in a

site BCF.

Value range: [entityMgt / download / siteMgt / abisSig / abisTraf / rfTrans / rfRecep / cellMgt / fhMgt / tdmaMgt / tsMgt / gsmTime / car0Fil / freqMgt] Routing mode The routing mode of the messages handled by the GSM functions, en-abling the Abis interface to identify the GSM entity to which the messag-es are sent, and the maximum response time of each GSM function summarized in the following table.

GSM function Routing modeResponsetime

Without centralized O&M

With centralized O&M

GSM entity Management

relative tei bcf 10 seconds

downloading relative tei relative tei 32 seconds

site Management relative tei bcf 120 seconds

abis SignallingManagement

bcf bcf 120 seconds

411-9001-124 18.08 1.0 Page 349 of 446


abis Traffic Management

bcf bcf 120 seconds

radio frequencyTransmission

bcf bcf 120 seconds

radio frequency Reception

not implemented

none 0 second

cell Management bcf bcf 120 seconds

frequency hoppingManagement


tdma Management


time slot Management


gsmTime not implemented

none 0 second

carrier 0 Filling not implemented

none 0 second

frequency Management

bcf bcf 120 seconds

siteGsmFctList Class 2Object: btsSiteManager

Default value: site Mgt/abisSig

Type: DP

Checks: • [C/M]: Each function occurs once in the list.• [C/M]: The "entityMgt", "download", "tdmaMgt", and "tsMgt" functions are included in the list.• [C/M]: The "freqMgt" function is only allowed for a BTS using cavity coupling.• [M]: The "fhMgt" function is included in the list if bts objects dependent on the btsSiteManager object are authorized to hop (btsIsHopping).

Notes: • The GSM functions whose routing mode is "not implemented" must not be included in the list. See the preceding table.• The GSM entities managing these GSM functions are BCF and TRX.

siteNameDescription: Reference name of a radio site on the OMC-R. It begins with a letter and

is case sensitive.The name of a site can be used in all MMI commands to reference the site on the OMC-R.



Type: DP

Page 350 of 446 411-9001-124 18.08 1.0


Checks: • [C/M]: The name of a site is unique to the OMC-R.

Note: Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (such as TRX, BSC, BTS, BTSSM). All othersymbols/characters are prohibited.The valid symbols are:• letter characters: A, B, C..., Z, a, b, c..., z.• digit symbols: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9.• minus sign: -• undescore: _• space:

slkAResource fieldDescription: This field provides SLK A section related data. It is a sub-parameter field

of signallingLinkResourcesStates.

Value range: MMI displayed fields:• pcmInstance: 0-167• ts: Integer 1-13


Type: Not applicable

Release: V17

Notes: This field is only for BSC 3000.This optional field is meaningful if anA resource has been assigned to thisSignaling Link (SLK) path.

slkAssociatedTmuPortPosition fieldDescription: SLK CN termination identifier. It is a sub-parame ter field of signallin-

gLinkResourcesStates

Value range: • shelf number: Integer 0-1• positionInShelf: Integer 1-15• portNumber: Integer

Object: Not applicable


Type: DD

Release: V17

Notes: • This parameter is only available for BSC 3000.• This optional field is meaningful if a CN termination has been assigned to this SLKpath.

slkAssociatedTmuPortPositionDescription: SLK CN termination identifier

Value range: Displayed fields:• shelfNumber: Integer 0-1• positionInShelf: Integer 1-15• portNumber: Integer

siteName

411-9001-124 18.08 1.0 Page 351 of 446




Type: DD

Release: V17

Notes: This parameter is available only forBSC 3000. This optional parameter is meaningful if a CN termination has been assigned to Signaling Link path.

slkATerResource fieldDescription: SLK Ater section identifiers. It is a sub-parameter field of

signallingLinkResourcesStates.

Value range: • pcmInstance: Integer 0-363

• ts: Integer 1-31



Type: DD

Release: V17

Notes: • This field is only available for BSC 3000.• This optional field is meaningful if an Ater resource has been assigned to a Signaling Link (SLK) path.

slkATerResourceDescription: SLK Ater section identifiers

Value range: Displayed fields:• pcmInstance: Integer 0-363• ts: Integer 1-31



Type: DD

Release: v17

Notes: • This field is available only for BSC 3000.

• This optional parameter is meaningful if an Ater resource has been assigned to this Signaling Link (SLK) path.

slc Class 2Description: Code of an SS7 channel. It is identical on BSC and MSC

ends.



slkAssociatedTmuPortPosition

Page 352 of 446 411-9001-124 18.08 1.0


Type: DP

Checks: • [C/M]: The code of an SS7 link is one-of-a-kind to theBSC.

small to large zone HO priority Class 3Description: External priority of inter-zone handovers from the inner zone to the outer

zone in a concentric cell.This attribute is defined if the associated bts object describes a concen-tric cell.



Default value: 17

Condition: To define if the associated bts object describes a concentric cell.

Type: DP

Release: V9

smartPowerManagementConfig Class 3Description: Enables/disables the smart power management feature

Value range: [disabled/enabled/enhanced]


Type: DP

Release: V17

Notes: • on BTS 18000 family, if the RM is equipped with PA Andrew, both smart power management and enhanced smart power management are supported• on BTS 18000 family, if the RM is equipped with PA Powerwave, only smart powermanagement is supported (not enhanced smart power management)• on S8000 and S12000 BTSs, only smart power management is sup-ported (not enhanced smart power management)

Checks: [C/M]: Checks are performed to determine the presence of a valid li-cense for Smart Power Management on the following operations:• setting the value of the smartPowerMana gementConfig parameter to "enabled" or "enhanced"• unlocking a cell (bts object) even if the Smart Power Management is not activated on it• unlocking a site (btsSiteManager object)• unlocking a TRX (transceiverEquipment object)• building the BDA of a BSC• resetting a BDA of a BSCThe attempt to set the "enabled" or "enhanced" value of the smartPow-erManagementConfig parameter on the powerControl object is possi-ble only when a valid license is available. When there is at least one powerControl object with the smartPowerManagementConfig pa-rameter value set to "enabled" or "enhanced", then no TRX unlocking, no bts unlocking, no btsSiteManager unlocking, no BDA build and no BDA reset is possible on the related BSCwithout a valid license.If the check fails, then the corresponding action is rejected and a clear error message displayed

slc Class 2

411-9001-124 18.08 1.0 Page 353 of 446


smartPowerSwitchOffTimer Class 3Description: Set the timer before switching the PA OFF

Value range: 5-255 (minutes)


Type: DP

Release: V17

Notes: BSC 3000 only

smoke detector Class 2Description: Presence or absence of the optional equipment "smoke

detector" in S8000 Outdoor.



Type: DP

Release: V9

smsCB Class 3Description: Whether broadcasting of short messages in unacknowl-

edged mode is authorized in a cell.Value range: [used / unused]

Object: bts

Default value: used

Type: DP

Checks: • [M]: The attribute value is "used" if the channelType of one of the channel objects dependent on the bts object is "bcchSdcch4CBCH" or "sdcch8CBCH" .

Remark: Configuration of logical channels and broadcast of short messages are managed by two separate OMC-R functions. When a short message broadcast is started, the presence of a CBCH in the channelType of a channel object dependent on a concerned bts object is checked. How-ever, the SMS-CB function is not aware of changes made to that attri-bute.Consequently, withdrawing a CBCH from the configuration will stop any short message broadcast in the concerned cell without the SMS-CB function knowing.

Page 354 of 446 411-9001-124 18.08 1.0


softwareDescription: Identifier of a software object.

The software object class allows users to manage the software releases of bsc objects (BSC), btsSiteManager objects (BCF), transceiverEquip-ment objects (TRX).Software objects are managed by the OMC-R "Software Management" function. The software objects have four attributes: sWVersionBackUp, sWVersionFallback, sWVersionNew, and sWVersionRun-ning. They are managed by the system according to the following user commands: Download, Activate new version, and Return to previous version.


Object: software

Type: Id

Checks: Checks common to all software objects:• [C]: The software object is not created for the parent managed object.• [D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command. Additional checks per-formed on the software-bsc object:• [C]:• [C/D]: If the application database of the related BSC is built, the bsc object is locked.• [D]: All objects dependent on the bsc object are deleted. Additional checks performed on the software-btsSiteMan ager object:• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked and the btsSiteManager object is locked.• [D]: All objects dependent on the btsSiteManager object are deleted. Additional check performed on the software-transceiverE quipment ob-ject:• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked, the parent bts object is locked, and the transceiv-erEquipment object is locked.

softwareLabelDescription: This attribute is a comment about the related software.

This attribute is modified by the Manager. Value changesare notified to the Manager.



Type: DP

Release: V13

source indicator Description: Select messages according to the source of the operation.

Do not fill in if this criterion is not to be selected.

Value range: [resource operation / management operation / unknown]


Type: DP

411-9001-124 18.08 1.0 Page 355 of 446


specific problemsDescription: Selecting messages according to a (cause, fault number) pair. This pa-

rameter allows selection of a fault number with one or more associated causes. Refer to these entries in the Dictionary. Do not fill in if this crite-rion is not selected.


Type: DP

speechMode Class 3Description: List of the speech algorithms associated with channel use modes in the

cell.The "full rate" value refers to the standard algorithm.

Value range: list of [algoid]where:[algoid] = full rate, enhanced full rate, AMR full rate, AMR half rate, AMR Wide Band full rate

Object: bts

Default value: [full rate, enhanced full rate]

Type: DP

Checks: • [C/M]: The "full rate" value is mandatory; it must be defined in the list.• [C/M]: Checks are performed to determine the presence of a valid li-cense for AMR-WB on the following operations:• setting the value of the speechMode parameter to "AMR Wide Band full rate"• unlocking a TRX• unlocking a bts• unlocking a btsSiteManager• building the BDA of a BSC• resetting a BDA of a BSCThe attempt to set the "AMR Wide Band full rate" value of the speech-Mode parameter on the bts object is possible only when a valid license is available. When there is a bts object with the speechMode parameter value set to "AMR Wide Band full rate", then no TRX unlocking, no BDA build and no BDA reset is possible on the related BSC without a valid license. If the check fails, then the corresponding action is rejected and a clear error message displayed

Release: V8

speechMode Class 3Description: List of the speech algorithms associated with channel use modes on the

A interface. The "full rate" value refers to the standard algorithm.

Value range: list of [algoid]where:[algoid] = full rate, enhanced full rate, AMR full rate, AMR half rate, AMR Wide Band full rate


Default value: [full rate, enhanced full rate]

Type: DP

Page 356 of 446 411-9001-124 18.08 1.0


Checks: • [C/M]: The "full rate" value is mandatory; it must be defined in the list.• [C/M]: Checks are performed to determine the presence of a valid li-cense for AMR on the following operations:• setting the value of the speechModeparameter to "AMR half rate" or "AMR full rate"• unlocking a TRX• building a BSC• resetting a BDA of a BSCThe attempt to set an "AMR half rate" or "AMR full rate" value of the speechMode parameter on the signallingPoint object is possible only when a valid license is available. When there is a signallingPoint object with the speechMode parameter value set to "AMR half rate" or "AMR full rate", then no TRX unlocking, no BDA build and no BDA reset is pos-sible on the related BSC without a valid license.If the check fails, then the corresponding action is rejected and a clear error message displayed• [C/M]: Checks are performed to determine the presence of a valid li-cense for AMR-WB on the following operations:• setting the value of the speechMode parameter to "AMR Wide Band full rate"• unlocking a TRX • building the BDA of a BSC • resetting a BDA of a BSC

The attempt to set the "AMR Wide Band full rate" value of the speech-Mode parameter on the signallingPoint object is possible only when a valid license is available. When there is a signallingPoint object with the speechMode parameter value set to "AMR Wide Band full rate", then no TRX unlocking, no BDA build and no BDA reset is possible on the relat-ed BSC without a valid license. If the check fails, then the corresponding action is rejected and a clear error message displayed

Release: V8

speechOnHoppingTs Class 3Description: This attribute is reserved for future use.

Value range: [true, false]

Object: bts



Type: DP

Release: V12

speechVersionAsscomp Class 1Description: Whether the "Speech version" element is used or not in the ASSIGN

COMPLETE messages (Phase II compliance).



Default value: true

Type: DP

Release: V12

speechMode Class 3

411-9001-124 18.08 1.0 Page 357 of 446


speechVersionHoperf Class 1Description: Whether the "Speech version" element is used or not in the HANDOVER

PERFORMED messages (Phase II compliance).



Default value:

Type: DP

Release: V12

speechVersionHoreq Class 1Description: Whether the "Speech version" element is used in the HANDOVER RE-

QUEST ACKNOWLEDGE messages (Phase II compliance).



Default value: true

Type: DP

Release: V12

speechVersionHorqd Class 1Description: Whether the "Speech version" element is used or not in the

HANDOVER REQUIRED messages (Phase II compliance).



Default value: true

Type: DP

Release: V12

standard indicator AdjC Class 3Description: Type of network in which this neighbor cell is working.

Value range: [gsm / extended gsm / dcs 1800 / pcs 1900 / R gsm / gsm850 / gsmdcs / dcsgsm / pcsgsm850 / gsm850pcs]

Object: adjacentCellHandover


Default value: gsm

Type: DP

Release: V10

Note: "gsmdcs" and "dcsgsm" are only available for S8000 DRX transceiver architecture.

Page 358 of 446 411-9001-124 18.08 1.0


standard indicator AdjC Class 3Description: Type of network in which this neighbor cell is working.

Value range: [gsm / extended gsm / dcs 1800 / pcs 1900 / R gsm / gsm850 / gsmdcs / dcsgsm / pcsgsm850 / gsm850pcs]


Default value: gsm


Type: DP

Release: V10

Note: "gsmdcs" and "dcsgsm" are only available for S8000 DRX transceiver architecture.

standardIndicator Class 2Description: Type of network in which the cell is working. From the value given to this

attribute, the OMC-R determines the network frequency band and the frequencies used by all radio entities (cells and radio time slots) in the related site.

Value range: [gsm / extended gsm / dcs1800 / pcs1900 / R gsm / gsmdcs / dcsgsm / gsm 850 / gsm850pcs / pcsgsm850 / gsm450 / gsm480 / gsm750 / egsmdcs / dcsegsm]

Object: bts


Type: DP

Note: GSM 900 network (gsm) The GSM 900 frequency band is 2*25 MHz wide and includes 124 pairs of carrier frequencies, numbered [1 to 124], which are 200 kHz apart:• Uplink direction (MS-to-BTS) = 890 to 915 MHz• Downlink direction (BTS-to-MS) = 935 to 960 MHz A frequency N cor-responds to the following Uplink frequency:• f1 = 890 + 0.2xN MHz where N = [1 to 124] For the Downlink frequency there is the following shift: • f2 = f1 + 45 MHzEXTENDED GSM network (extended gsm) The extended GSM fre-quency band is 2*35 MHz wide and includes 174 pairs of carrier fre-quencies, numbered [0 to 124] and [975 to 1023], which are 200 kHz apart:• Uplink direction (MS-to-BTS) = 880 to 915 MHz • Downlink direction (BTS-to-MS) = 925 to 960 MHz A frequency N cor-responds to the following Uplink frequency:• f1 = 880.2 + 0.2x(N - 975) MHz where N = [975 to 1023]• f1 = 890 + 0.2xN MHz where N = [0 to 124] For the Downlink frequency there is the following shift:• f2 = f1 + 45 MHz

411-9001-124 18.08 1.0 Page 359 of 446


Note: The extended GSM frequency band defined above is the definition of the ETSI. GSM-R network (R gsm)The GSM-R frequency band is 2*39 MHz wide and includes 194 pairs of carrier frequencies, numbered [0 to124] and [955 to 1023], which are 200 kHz apart: • Uplink direction (MS-to-BTS) = 876 to 915 MHz• Downlink direction (BTS-to-MS) = 921 to 960 MHzA frequency N corresponds to the following Uplink frequency:• f1 = 876.2 + 0.2x(N - 955) MHz where N = [955 to 1023]• f1 = 890 + 0.2xN MHz where N = [0 to 124] For the Downlink frequency there is the following shift:• f2 = f1 + 45 MHz

Note: The GSM-R frequency band defined hereabove is the definition of the ETSI. GSM 1800 network (dcs1800)The GSM 1800 frequency band is 2*75 MHz wide and includes 374 pairs of carrier frequencies, numbered [512 to 885], which are 200 kHz apart: • Uplink direction (MS-to-BTS) = 1710 to 1785 MHz• Downlink direction (BTS-to-MS) = 1805 to 1880 MHz A frequency N corresponds to the following Uplink frequency:• f1 = 1710.2 + 0.2x(N - 512) MHz where N = [512 to 885]For the Downlink frequency there is the following shift:• f2 = f1 + 95 MHzGSM 1900 network (pcs1900)The GSM 1900 frequency band is 2*60 MHz wide and includes 299 pairs of carrier frequencies, numbered [512 to 810], which are 200 kHz apart:• Uplink direction (MS-to-BTS) = 1850 to 1910 MHz• Downlink direction (BTS-to-MS) = 1930 to 1990 MHz A frequency N corresponds to the following Uplinkfrequency:• f1 = 1850.2 + 0.2x(N - 512) MHz where N = [512 to 810]For the Downlink frequency there is the following shift:• f2 = f1 + 80 MHzGSM 900 - GSM 1800 network (gsmdcs)

Note: The primary band is GSM 900 (see above GSM 900 Network para-graph). The secondary band is GSM 1800 (see above GSM 1800Network paragraph). GSM 1800 - GSM 900 network (dcsgsm)The primary band is GSM 1800 (see above GSM 1800 Network para-graph). The secondary band is GSM 900 (see above GSM 900 Network paragraph).

Note: "gsmdcs" and "dcsgsm" are only available for S8000 DRX transceiver architecture. GSM 850The GSM 850 frequency band is 2*25 MHz wide and includes 124 pairs of carrier frequencies, numbered [128 to 251],• Uplink direction = 824 to 849 MHz• Downlink direction = 869 to 894 MHzA frequency N corresponds to the following Uplink frequency:• f1 = 824.2 + 0.2x(N - 128) MHz where N = [128 to 251]For the Downlink frequency there is the following shift:• f2 = f1 + 45 MHz

Release: V9

standbyStatusDescription: ISO State

Value range: [hotStandby / coldStandby / providingService]

Object: atmRm, cem, iem, lsaRc, omu, sw8kRm, trm, hsaRc, hsaRcTcu, iom


standardIndicator Class 2

Page 360 of 446 411-9001-124 18.08 1.0


Type: DD

Release: V13

standbyStatusDescription: ISO State

Value range: [hotStandby / coldStandby / providingService / nonSignificant]

operationalState standbyStatus Meaning

disabled coldStandby IGM not flushed (end of start-up, beginning of the passive update by the active update

enabled hotStandby IGM enabled and passive

enabled providingService IGM enabled and active

Object: igm


Type DD

Release: V18.0

standbyStatus TMUDescription: This data provides the duplex operational status of the TMU board. It

can be either (for a TMU) providingService when TMU is distributed or coldStandby when TMU is started but not (yet) distributed.

Value range: INTEGER with:• hotStandby (0)• coldStandby (1)• providingService (2)• notSignificant (15)

Object: TMU

Type: DD

Release: V17

Note: This parameter is available in BSC 3000 only.

start dateDescription: The date the first data is recorded in the log (default is the current date).

Date format entry forms are detailed in Kapsch GSM OMC-R Com-mands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


standbyStatus

411-9001-124 18.08 1.0 Page 361 of 446



Type: DP

start timeDescription: Absolute time of first job run (default is the current date and time). Abso-

lute time format entry forms are detailed in Kapsch GSM OMC-R Com-mands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130). If date matches the current date, set time to a value at least one minute after the current time.


Object: job

Type: DP

start timeDescription: Start of system log reading on the requested start date (default is 00:00).

Time format entry forms are detailed in Kapsch GSM OMC-R Com-mands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Do not fill in if this criterion is not selected.

Value range: [<time>]


Type: DP

startAlarmFilterDescription: Condition for triggering an alarm when no counter is involved.

The following fields can be combined in the logical expression:


administrativeState

state change =

availabilityStatus state change =

bsc equipment name

alarm =

bsc model alarm =

cause alarm < = >

btsSiteManager model

alarm =

bts equipment name

alarm =

equipment processor number

alarm < = >

start date

Page 362 of 446 411-9001-124 18.08 1.0


faultNumber alarm < = >

operationalState state change =

perceived severity alarm =

postMortem alarm =

usageState state change =

The following logical operators can be used in the logical expression:• & stands for the logical AND.• | stands for the logical OR.• ! stands for the logical NOT.The "postMortem" field can take two values, either "before BSC restart" or "after BSC restart". They have the following meaning:• before BSC restart means that the notification issued by the BSC was received by the OMC-R agent without the BSC having restarted (nomi-nal conditions).• after BSC restart means that the notification was issued by the BSC, then, the BSC was restarted before the OMC-R agent received the noti-fication. These notifications do not trigger alarms.



Condition: To define if no counter is associated to the criterion.

Type: DP

startAlarmThresholdDescription: The maximum counting value in the reference period when a start-of-

alarm message is sent. The value must be checked by users.This attribute defines a maximum value read at the end of the defined refPeriod. It must be greater than endAlarmThreshold. Threshold changes are effective when the OMC-R is restarted.

Value range: [0.00 to 2147483646]


Type: DP

startAlarmThresholdDescription: Minimum (thresholdLow) / maximum (thresholdHigh) counting value in

the reference period, below/above which a start of "lower threshold/up-per threshold" alarm messageis sent. The value must be checked by users. If thesholdType = "thresh-oldLow", this attribute defines aminimum value for a one minute reference period (or the counter collect-ing period for PCM unavailability counters), below which a start of "lower threshold" alarm message issent. It must be lower than startAlarmThreshold "low". If thesholdType = "thresholdHigh", this attribute defines a maximum value for a one minute reference period (or thecounter collecting period for PCM unavailability counters), above which a start of "upper threshold" alarm message is sent. It must be greater than startAlarmThreshold "high". Threshold changes are effective when the OMC-R is restarted.

Value range: [0.00 to 2147483646]


411-9001-124 18.08 1.0 Page 363 of 446


Type: DP

Remark: • The threshold limits depend on the associated counter.• The BSS counter threshold crossing detection mechanism is described in Kapsch GSM BSS Fundamentals — Operating Principles (411-9001-007).

startCounterThresholdDescription: Minimum counting threshold when a counter is involved.



Condition: To define when a counter is associated with the criterion.

Type: DP

startTimeDescription: Date and time the files were restored on the OMC-R agent

disks.



Condition: This attribute is significant and displayed only when the log object de-scribes a log restored on the OMC-R agent disks.

Type: DP

startTimeDescription: Date and time the temporary observation started.

This information is provided by the system and indicates the exact time when the observation counters are collected for the first time.



Type: DI

stopTimeDescription: Date and time the OMC-R agent will purge the restored

files.

Value range: [<date>, <time>]



Type: DP

startAlarmThreshold

Page 364 of 446 411-9001-124 18.08 1.0


stopTimeDescription: Date and time the temporary observation will stop.

Absolute time format entry forms are detailed in Kapsch GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).


Object: mdScanner - Create temporary observation


Type: DP

Checks: • [C]: stopTime - startTime > mdGranularityPeriodminutes• [C]: stopTime - startTime < 1440 minutes (24 hours)

Restrictions: • [M]: This attribute cannot be modified. Stop the observation if neces-sary by deleting the mdScanner object and restart it by creating a new mdScanner object with the appropriate attributes.

subChanIdDescription: AGCH subchannel number: Do not fill in when the channelType of the

radio time slot is "tchFull" or "mainBCCH".

Value range: [0 to 7] when channelType = "sDCCH" or "sdch8CBCH", [0 to 3] otherwise

Object: channel - Set channel state

Type: DP

Checks: • [A]: The parent btsSiteManager and bts objects are unlocked.

Reminder: A BCCH or a CBCH cannot be blocked.

subjectDescription: Identifier (name) of a user message in the OMC-R.

It is displayed in the "Inter-user message manager" window of the mes-sage addressees and allows them to identify the message before read-ing.


Object: user message

Type: Id

411-9001-124 18.08 1.0 Page 365 of 446


suffixDescription: Optional string of characters to add to the name of the call monitoring

data files when saved in the OMC-R. When a suffix is defined, a call monitoring data file transferred to the OMC-R by running the Transfer command is saved under the name "SDO_CM_BSCnnn_<suf-fix>.yyyymmdd ", where "nnn" identifies the BSC hosting the data file (if bsc = 5,then nnn is read "005") and "yyyymmdd" is the file saving date. See Kapsch GSM BSS Fundamentals — Operating Principles (411-9001-007).


Object: Call monitoring - Transfer (SDO)

Type: DP

summaryDescription: Text explaining the goal of the command file.

Object: commandFile

Type: DP

suspendResumeActivation Class 3Description: Enables or disables the Suspend/Resume feature.

Value range: [disabled / enabled]. The recommended value is "enabled".


Object: bsc

Feature: GPRS / EDGE Suspend and Resume

Type: DP

Notes: • When disabled:• The Suspend is still performed.• The Resume is performed through the Routing AreaUpdate message.• The new value does not apply to ongoing calls. Itapplies to new calls only.

Release: V15

Page 366 of 446 411-9001-124 18.08 1.0


supportingTransceiverEquipmentDescription: Identifier of the TRX associated with the TDMA frame by the BSC.

This dynamic attribute allows the user to know the TDMA-TRX/DRX as-sociation established by the BSC. It is displayed provided the transceiv-er object operationalState is "enabled". Refer to this entry in the Dictionary. If the TRX/DRX is declared faulty because of a frequency loss, the system takes the following actions:• attempt to reconfigure the associated TDMA frame on the redundant TRX/DRX• if there is no redundant TRX/DRX, reconfiguration of the TDMA frame on another TRX/DRX if its priority is higher than the priority of the TDMA frame currently configured If the associated TDMA frame cannot be re-configured for some reason, all frames that were using the frequency lost by the TRX/DRX will be disturbed.


Object: transceiver

Type: DP

Remark: Only BTSs using cavity coupling manage dynamic reconfiguration of hopping frequencies.

sw8kRmDescription: The 8k Subrate Timeswitch Ressource Module, which adds sub-track

switching capability to the Interface Node.


Object: sw8kRm

Type: Id

sw8kRmIdDescription: Identifier of the ’sw8kRm’ object class. This identifier is allocated by the

MD-R at object creation, depending on the shelf and slot numbers indi-cated by the BSC. This attribute cannot be modified. This attribute is rel-evant for BSC 3000 and TCU 3000.


Object: sw8kRm

Type: DP

Release: V13

swVersionActive Class 3Description: Defines the current version running.

Value range: String containing the IPM software name.

Object: ipm


Type: DP

411-9001-124 18.08 1.0 Page 367 of 446


Release: V18.0

Notes: This parameter is mandatory for the ipm object creation.This parameter can be modified through the Activate new version action in the Configuration --> Software menu or during an automatic upgrade.

sWVersionBackUpDescription: Reference number of the backup software release. It is identical to

sWVersionRunning.Refer to the sWVersionRunning entry in the Dictionary.

Value range: [Bsxabvcdefgh (BSC software) / XXXabcdef (others)]

Object: software

Type: DP

sWVersionFallBackDescription: Reference number of the previous software release. It is updated follow-

ing a version change command.Refer to the sWVersionRunning entry in the Dictionary.This attribute is undefined when the object is created.As a result of an Activate new version command, the system updates the sWVersionFallBack attribute with the reference of the software re-lease previously running in the related BSS entity.As a result of a Return to previous version command, the system sets the sWVersionFallBack attribute undefined.

Value range: [Bsxabvcdefgh (BSC software) / XXXabcdef (others)]

Object: software

Type: DP

sWVersionNewDescription: Reference number of the new software release. It is updated following a

download or version change command. Refer to the sWVersionRunning entry in the Dictionary.This attribute is undefined when the object is created. As a result of an Activate new version command, the system sets the sWVersionNew at-tribute undefined. As a result of a Download or Return to previous ver-sion command, the system updates the sWVersionNew attribute with the reference of the software release downloaded or that was presently run-ning in the related BSS entity.


Object: software

Type: DP

sWVersionPassive Class 3Description: Defines the software version in the IPM NON ACTIVE flash.

Value range: String containing the IPM software name.

Object: ipm

swVersionActive Class 3

Page 368 of 446 411-9001-124 18.08 1.0




Release: V18.0

Notes: This parameter can be modified through the Download action in the Con-figuration --> Bsc menu or during an automatic upgrade.This parameter is automatically updated when reception of the SwSta-tusRsp during the IPM authentication.

sWVersionRunning Class 2Description: Reference number of the software release currently running. It is defined

by the user at object creation time and is updated following version change commands.This parameter identifies the type and version of the software currently running in the related BSS entity. Check the BSS delivery descriptor file to fill it in when creating the software object.As a result of an Activate new version or Return to previous version com-mand, the system updates the sWVersionRunning attribute with the ref-erence of the software release newly activated in the related BSS entity.For more information on the reference number formats for each type of BSS entity driven by software, refer to the "delivery" entry in this Diction-ary.

Value range: String from 9 to 12 characters

Object: software

Type: DP

Checks: • [C]: The attribute is defined (nonzero value).• [C]: The first three letters of the reference number match the type of the managed object related to the software object.

synchronized Class 3Description: Whether the neighbor cell and the associated serving cell are synchro-

nous, and is attached to the same BTS.

Value range: [not synchronized cells / synchronized cells / pre sync HO with timing ad-vance / pre sync HO, default timing advance] • "not synchronized cells": the neighbor cell and theserving cell are not attached to the same BTS• "synchronized cells": the neighbor cell and the serving cell are attached to the same BTS• "pre sync HO with timing advance": the handover procedure between the neighbor cell and the serving cell is pre-synchronized with the GSM Real Time Difference between the neighbor cell and the serving cell in the "HANDOVER COMMAND" message• "pre sync HO, default timing advance": a pre-defined timing advance is used in the pre-synchronized handover procedure between the serving cell and theneighbor cell. Refer to "preSynchroTimingAdvance" param-eter.


Default value: not synchronized cells

Type: DP

sWVersionPassive Class 3

411-9001-124 18.08 1.0 Page 369 of 446


synchronizingCemRcFiberDescription: Source port of the CEM3 of the synchronization clock

Value range: [0: Port 0 of active CEM3, 1: Port 1 of active CEM3, 2: Port 0 of passive CEM3, NotSignificant: none

Object: bsc

Type: DD

Feature: Optical BSC High Capacity 4K

Release: V18.0

synchronizingCemRcFiberDescription: Source port of the CEM3 of the synchronization clock

Value range: [0: Port 0 of active CEM3, 1: Port 1 of active CEM3, 2: Port 0 of passive CEM3, NotSignificant: none]

Object: transcoder

Type: DD

Feature: Optical BSC High Capacity 4K

Release: V18.0

synchronizingHsaRcDescription: Source HsaRC of the clock synchronization

Value range: • 0: HsaRC 0 is the source of the clock synchronization• 1: HsaRC 1 is the source of the clock synchronization• Not significant: none of the HsaRC is the source of the clock synchro-nization

Object: bsc


Type: DD

Release: V17

synchronizing PCMDescription: Synchronizing PCM choice (on Ater interface).

Value range: [synchro mic 0, synchro mic 2, synchro mic 4, synchro mic 6, synchro internal clock]

Object: bsc

Type: DD

Release: V10

Page 370 of 446 411-9001-124 18.08 1.0


2.20. T

syntheticFaultNumberDescription: A synthetic fault number assigned to the alarm when a counter is

involved.



Condition: To define when a counter is associated to the criterion.

Type: DP

Checks: • [C/M]: The number is in the range [39500 to 39549].

systemInfoType2 Class 2Description: Reserved for future use.


Object: bts

Type: DP

Release: V15

t3101 Class 3Description: BSC timer triggered during the immediate assignment procedure. Use

the suggested system value.It is set on transmission of CHANNEL ACTIVATION by the BSC and can-celed on receipt of ESTABLISH INDICATION sent by the BTS.


Object: bts

Default value: 3

Type: DP

t3103 Class 3Description: BSC timer triggered during the handover procedure. Use the suggested

system value.It is set on transmission of HANDOVER COMMAND by the BSC and canceled on receipt of either HANDOVER COMPLETE or HANDOVER FAILURE sent by the MS (intra-bss handover), or CLEAR COMMAND sent by the MSC (inter-bss handover). At expiry of T3103, the channel is released.

Value range: [2 to 255] seconds (t3103 < bssMapT8)

Object: bts

Default value: 5 seconds

Type: DP

Checks: • [C/M]: t3103 < bssMapT8 (attribute of the parent bsc object)

411-9001-124 18.08 1.0 Page 371 of 446


t3107 Class 3Description: BSC timer triggered during the assignment command procedure. Use

the suggested system value.It is set on transmission of ASSIGN COMMAND by the BSC and canceled on receipt of either ASSIGN COMPLETE or ASSIGN FAILURE sent by MS.


Object: bts


Type: DP

t3109 Class 3Description: BSC timer triggered during the SACCH deactivation procedure. Use the

suggested system value.It is set on receipt of DEACTIVATE SACCH ACKNOWLEDGE sent by the BTS and canceled on receipt of RELEASE INDICATION sent by the BTS. If the timer expires, an RF CHANNEL RELEASE message issent to the BTS and an RF CHANNEL RELEASE ACK is expected.Mobiles comply with system operating conditions when the counter (S) associated with SACCH messages is assigned a value below or equal to t3109.

Value range: [2 to 255] seconds (t3109 radioLinkTimeout)

Object: bts


Type: DP

Checks: • [C/M]: t3109 radioLinkTimeout

t3111 Class 3Description: BSC timer triggered during the radio resource clearing procedure. Use

the suggested system value.It is set on receipt of RELEASE INDICATION sent by the BTS. On elapse, the BSC sends RF CHANNEL RELEASE.


Object: bts

Default value: 2 seconds (1 second in a GSM-R context)

Type: DP

t3121 Class 3Description: Timer to wait for handover to UTRAN complete message

Value range: 2...255 seconds

Object: bts

Default value: 12

Page 372 of 446 411-9001-124 18.08 1.0


Type: DP

Checks:

Release: V17


t3122 Class 3Description: Minimum time that mobiles must wait before issuing a channel

allocation request when an immediate assignment has failed.


Object: bts


Type: DP

t3168 Class 3Description: This timer is used at the MS side to define when to stop waiting for the

PUAS message after sending either a PRR message or a Channel Re-quest in a PDAN.

Value range: [[0 (500 ms)1 (1000 ms)2 (1500 ms)3 (2000 ms)4 (2500 ms)5 (3000 ms)6 (3500 ms)7 (4000 ms)]

Object: bts

Default value: 0

Type: DP

Release: V14

t3172 Class 3Description: Value of the timer started by the mobile on reception of a Packet

Access Reject message (in seconds).


Object: bts


Default value: DP

Release: V12

t3121 Class 3

411-9001-124 18.08 1.0 Page 373 of 446


t3192 Class 3Description: Wait for DL TBF release after reception of the final block.

This timer is used on the MS side to define when the MS received all the RLC data blocks. When the timer expires, the MS releases the resourc-es associated with the TBF and begins to monitor its paging group (DRX mode).

Value range: [0 (500 ms)1 (1000 ms)2 (1500 ms)3 (0 ms)4 (80 ms)5 (120 ms)6 (160 ms)7 (200 ms)]

Object: bts

Type: DP

Default value: 0

Release: V14

taDetectionDataExtCell class 2Description: Activate/deactivates the advanced TA detection in eGPRS above 35 ki-

lometers.


Object: bts


Type: DP

Release: V18.0

Checks: • [C/M]: Checks are performed to determine the presence of a valid li-cense for GPRS/Edge on Extended Cell on the following operations:• setting the value of the taDetectionDataExt Cell parameter to "enabled"• unlocking a TRX• unlocking a cell• unlocking an entire site• building a BSC• resetting a BDA of a BSCThe attempt to set the "enabled" value of the taDetectionDataExtCell parameter on the bts object is possible only when a valid license is avail-able. When there is a bts object with the taDetectionDataExtCell param-eter value set to "enabled", then no TRX unlocking, no bts unlocking, no btsSiteManager unlocking, no BDA build and no BDA reset is possible on the related BSC without a valid license. If the check fails, then the cor-responding action is rejected and a clear error message displayed

Page 374 of 446 411-9001-124 18.08 1.0


target BdaDescription: Target BDA for the On-line reset command See Kapsch GSM OMC-R

Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).

Value range: [running / new / old]• "running" for "BDA Edition" reset on-line (i.e. basic BDA change without prototype BDA change)• "new" or "old" for "BDA Version" reset on line (i.e. BSC upgrades with prototype BDA change)

Object: bsc - On-line reset

Type: DP

Release: V11

teiBtsSiteManager Class 2Description: TEI address of the site BCF in the LAPD protocol. In a BTS chain, the

TEI addresses must be allocated in ascending order (such as TEI0, TEI1, TEI2), beginning with the BTS closest to the BSC. In a BTS loop configuration, the TEI addresses must be allocated in ascending order (such as TEI0, TEI1, TEI2), beginning with the BTS directly linked to the BSC that uses DTI board no.0 for the Abis link input. The following TEI values 3, 7, 11, 15, and 19 are forbidden when T1 PCMs on Abis inter-face are used.The relationship between internal E1 PCM TSs (DTI, PCMI or CPCMI) or BSC (DDTI) and external PCM TSs is thefollowing:

E1 0 1 2 3 4 5 6 7 8 9 10

11 12

13 14

15

T1 1 2 3 4 5 6 7 8 9 10 11

12

E1 16

17 18

19 20 21

22

23 24 25

26

27 28

29 30

31

T1 13 14

15 16

17

18 19 20

21 22 23

24

E1 PCM TSs 4, 8, 12, 16, 20, 24, and 28 are not mapped onto T1 PCM TSs. The scheduled or "rendez-vous" TSs (=teiBtsSiteManager +1) can-not be defined on these internal E1 PCM TSs

Value range: Depending on the BTS type, the value range is:• [0 to 9] for a BTS 18000• [0 to 13] for an S12000• [0 to 15] for all other BTSs


411-9001-124 18.08 1.0 Page 375 of 446


Type: DP

Checks: • [C/M]: The number of TEI addresses allotted to a LAPD channel is lim-ited to maxTeiPerLapdCh (static configuration data).• [C/M]: Values 3, 7, 11 and 15 are forbidden in T1 mode.• [C/M]: When the btsType parameter is set to IP or when a btsSiteMan-ager object is created with he btsType parameter set to IP, theteiBtsSiteManager parameter must be equal to 0.

teiLapdLinkDescription: TEI address of the LAPD link in the LAPD protocol. It is updated by the

OMC-R agent according to the TEI address allotted by the user to the entity (BCF, TRX/DRX, TCU) using the LAPD link.


Object: lapdLink - Display

Type: DP


teiTransceiverEqpt Class 2Description: TEI address of the TRX/DRX in the LAPD protocol.

Value range: The value range is:

Object: • [14 to 55], case of an S12000• [14 to 79], case of a BTS 18000 and a BSC 3000• [16 to 63], in other cases

Type: DP

Checks: • [C/M]: The number of TEI addresses allotted to a LAPD channel is lim-ited to maxTeiPerLapdCh (static configuration data).• [C/M]: The TEI address is not assigned to another transceiverEquip-ment object dependent on the same bts object. • [C/M]: HPRM does not support following TEIs: 14, 17, 18, 21, 22, 25, 34, 37, 42, 45, 50, 53, 64, 67, 70, 73, 76, 79• [M]: No mdScanner object refers to the transceiverEquipment object (no observation is running on the TRX/DRX or the parent cell). Checks:• [M]: The parent bsc object is unlocked, the parent bts object and the transceiverEquipment object are locked.

teiTranscoder Class 2Description: TEI address of the TCU in the LAPD protocol.


Object: transcoder

Type: DP

Checks: . [C/M]:Bsc 3000: No check. The TEI address is not used by BSC 3000.. [C/M]: 0 . teiTranscoder . 126

Page 376 of 446 411-9001-124 18.08 1.0


temporaryOffset Class 3Description: Negative offset applied during Penalty Time for re-selecting a cell (C2

criterion).This negative offset is applied during the entire penaltyTime duration and allows to prevent speeding mobiles from selecting the cell. Refer tothe cellReselectOffset entry in the Dictionary.

Value range: [0 to 70, by steps of 10] dB

Object: bts

Feature: AR 264

Default value: 70

Type: DP

Release: V8

terminal nameDescription: Name of a terminal as defined in its profile (default is the

logged-in user’s terminal). Do not fill in if this criterion is not to be selected.

Value range: case sensitive]


Type: DP

Checks: • [A]: The terminal is known to the OMC-R.

Note: Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL object names (such as TRX, BSC, BTS, BTSSM). All othe symbols/characters are prohibited.

terminal profileDescription: Identifier (name) of an OMC-R terminal.

Value range: [case sensitive, 1 character min.]


Type: Id

Checks: • [C]: The name of a terminal is unique to the OMC-R.• [M/D]: The terminal profile object is created.

text

Description: Comment to display before running the next command The Echo: text = blah blah blah command can be inserted anywhere in a command file, and as many times as necessary. The text is displayed as it is in session logs when the command file is run.

Value range: [unlimited number of characters]

Object: commandFile - Echo command

Type: DP

411-9001-124 18.08 1.0 Page 377 of 446


textDescription: Contents of a short message. It is broadcast as it is.

Value range: [93 characters max]


Type: DP

textDescription: Contents of a user message. It is sent as it is.

Value range: [unlimited number of characters]

Object: user message

Type: DP

tFH or RWM Class 2Description: Presence or absence of the optional equipment "microwave terminal" in

4000 Outdoor.



Type: DP

Release: V9

tfoActivation class 3Description: Indicates if TFO is activated or not.

Value range: [activated / deactivated]

Object: bsc

Feature: TFO support

Default value: deactivated

Type: DP

Release: V18.0

tGMMKeepAlive Class 3Description: Configures the GMM Keep Alive mechanism.

Value range: [[0..64]• 0: the feature is disabled (the same Keep Alive timer is used for data and GMM procedures)• [1..63] (1 unit = 100 ms): enables the feature and sets the GMM Keep Alive timer duration. The recommended value is 5• 64: the Keep Alive mechanism is disabled for GMM procedures

Object: bts

Page 378 of 446 411-9001-124 18.08 1.0


Feature: 23038 - Disabling ’TBF Keep Alive’

Type: DP

Release: V15

This BSS is using licenseDescription: Indicates whether the BSC is using a 4K Erlangs license.

Value range: [yes/no]

Object: md - Display 4K Erlangs Informationbsc - Display 4K Erlangs Information


Release: V17

thresholdInterference Class 2Description: List of four thresholds defined in ascending order, used to sort idle chan-

nels on the basis of measured interference levels.This attribute, together with the averagingPeriod attribute, allows to manage interferences in a radio cell. The classification is used by the ra-dio resource allocator.The interference processing algorithm for a cell is as follows:• For each idle radio channel, the BTS permanently measures the signal strength level RXLEV.• When averagingPeriod "Measurement results" messages have been received, the L1M function in the BTS calculates interference level aver-ages, sorts the idle channels according to the five defined interference levels (Level 0 corresponds to the lowest interference level), and sends the information to the BSC.

tGMMKeepAlive Class 3

411-9001-124 18.08 1.0 Page 379 of 446


Description: • The BSC tallies the interference levels and, if the temporary "interfer-ence" observation is running for the bsc object, sends the channelIdle-LevelMax and channelIdleLevelEch counters every <mdGranularityPeriod> minutes to the OMC-R agent. Refer also to C1619 permanent observation counters.



Defaultvalue: -100 -90 -80 -70

value:

Type: DP

Checks: • [C/M]: The thresholds are defined in ascending order.• [M]: The parent bsc object is unlocked and the associated bts object is locked

thresholdTypeDescription: Type of thresholds managed.

The startAlarmThreshold and endAlarmThreshold attribute values, which trigger permanent BSS observation counter threshold overflow messages, depend on the type of thresholds managed by the mdWarning object. Refer to these entries in the Dictionary.

Value range: [thresholdLow / thresholdHigh]


Type: DP

timeBetweenHOConfiguration Class 3Description: Whether the hoPingpongTimeRejection timer can be used in a BSS

when processing handovers.Refer to bts object bts time between HO configuration and adjacentCell-HandOver object hoPingpongTimeReject ion attributes in this Dictionary of Parameters.

Value range: [used / not used]

Object: bsc


Default value: used

Type: DP

Release: V9

timerGcchNotif Class 3Description: Time between two FACCH notifications.



Default value: 2 (recommended)

Page 380 of 446 411-9001-124 18.08 1.0


Feature: ASCI

Type: DP

Release: GSM-R V15

timerPeriodicUpdateMS Class 3Description: Time between two location update requests.

Value range: [0 to 255] 1/10th of hour. "0" means that no periodiclocation update is requested.

Object: bts

Default value: 60

Feature: ASCI

Type: DP

Remark: The operator must be aware that the input of low values for this attribute causes an important traffic load during the location update procedures. For instance, entering the value "1" for this attribute leads to that all Mo-biles will execute an update of their LAC every 6 minutes.

timeSlotNumberDescription: PCM time slot used by a LAPD link Since all radio sites house a

switching facility, the BSC can directly map the LAPD link onto a PCM time slot.

Value range: [1 to 24] (GSM 1900/850 networks), [1 to 31] (other networks).

Object: lapdLink

Note: This parameter is only available for the lapdLink OML object on BSC 3000.

Type: DP

Remark: The LAPD link with a radio site BCF always uses TSn = pcmTimeSlotNumber (radio site scheduled time slot). Refer to this entry in the Dictionary.

timeSlotNumber Class 2Description: PCM time slot used by an SS7 channel on the A interface.



timerGcchNotif Class 3

411-9001-124 18.08 1.0 Page 381 of 446


Type: DP

Checks:: • [C/M]: The time slot is not already assigned on the A interface to a sig-nallingLink or xtp object dependent on the same bsc object and is not mapped on the TS used by the OMC channel on the Ater interface. Checks:• [C/M]: If the SS7 link uses PCMA link no.3 (pcmCircuitId), the timeslot is in the range [1 to 27] if the PCM link is an E1 link or in the range [1 to 20] if the PCM link is a T1 link.Since the last four time slots of that link are not mapped on the Ater in-terface, they are unusable (refer to the transcoderMatrix entry in the Dic-tionary).

timeSlotNumberDescription: PCM time slot used by a terrestrial circuit on the A interface.

Value range: [1 to 24] (GSM 1900/850 networks), [1 to 31] (other networks).

Object: xtp

Type: DP

Checks:: • [C]: The time slot is identical to the mscPcmTsNu mber component of the xtp object cic attribute (refer to this entry in the Dictionary).• [C]: The time slot is not already assigned on the A interface to an xtp or signallingLink object dependent on the same bsc object, and is not mapped on the TS used by the OMC channel on the Ater interface.Checks:• [C]: If the terrestrial circuit uses PCMA link no.3 (pcmCircuitId), the timeslot is in the range [1 to 27] if the PCM link is an E1 link or in the range [1 to 20] if the PCM link is a T1 link. Since the last four time slots of that link are not mapped on the Ater interface, they are unusable (refer to the transcoderMatrix entry in the Dictionary).

Restrictions: • • [M]: This attribute cannot be modified due to its relationship with the mscPcmTsNumber component of the cic attribute.

tmuDescription: The Traffic Management Unit, which is responsible for managing the

GSM protocol: it provides processing power for Call Processing, termi-nates GSM protocol (A, Abis and Ater interfaces), terminates low level GSM protocol (LAPD and SS7).


Object: tmu

Type: Id

Release: V13

tmuIdDescription: Identifier of the ’tmu’ object class. This identifier is allocated by the MD-

R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000.


Object: tmu

timeSlotNumber Class 2

Page 382 of 446 411-9001-124 18.08 1.0


Type: DP

Release: V13

tnOffset class 2Description: Allows to specify and control Timeslot Number (TN) difference between

BTSs in case of network synchronization by GPS.Refer also to the fnOffset entry in this dictionary.


Value range: [0..7]

Type: DP


Default value: 0

Release: V15


tNwExtUtbf Class 3Description: Inactive period timer.

Maximum time of inactivity during which the UL radio resources are not released.


Object: bts

Default value: 0

Type: DP


Checks: • [M]: tNwExtUtbf value must be greater than or equal to tUsfExt value.

Release: V15

Total licenses for this OMC-RDescription: Number of licenses (RM Capacity or 4K Erlangs Information) configured

on the OMC-R.


Object: md - Display RM capacitybsc - Display RM capacitybtsSiteManager - Display RM capacitymd - Display 4K Erlangs Informationbsc - Display 4K Erlangs Information

Feature: AMR Feature Activation Control EDGE Feature Activation Control

Release: V17

tmuId

411-9001-124 18.08 1.0 Page 383 of 446


Total unused licensesDescription: Number of licenses free to be used or exported to another OMC-R.

Value range: [0..NNNN] (The value can be negative when licenses have been export-ed from the OMC-R while all of them are used by objects)

Object: md - Display RM capacitybsc - Display RM capacitybtsSiteManager - Display RM capacitymd - Display 4K Erlangs Informationbsc - Display 4K Erlangs Information


Release: V17

traceConstraintListDescription: List of logical expressions that allow to filter the information to display.

The following filter criteria are used: [bsPower / bssTraceType / bssTraceTypeUsed / establishmentCause / hoCauseClass / ho-ClauseValue / hoRrResult / mobileId / msPower / pcm / recordingEntity / rrCause / timeSlot / timingAdvance / tracedBts / traceRecId / traceRef-erenceC rit / trStartTime / trStopTime. / trxIdrxId].See Kapsch GSM OMC-R Commands Reference - Security, Administra-tion, SMS-CB, and Help menus (411-9001-130) .


Type: DP

traceControlDescription: Identifier of a traceControl object defined with regard to the md object.

It describes the Call tracing function of a BSC.A traceControl object is created in locked state. Unlock the object to start collecting data in the related BSC.



Type: Id

Checks: • [C]: The traceControl object is not created for the md object.• [C/M/D]: The application database of the related BSC is not being built.• [C/M/D]: If the application dat base of the related BSC is built, the BSS/OMC-R link is established and no audit is in-progress in the BSC.• [M/D]: The traceControl object is created.

Release: V8

Page 384 of 446 411-9001-124 18.08 1.0


traceDayAccessedDescription: Date of data recording

Date format entry forms are detailed in Kapsch GSM OMC-R Com-mands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130).Setting this parameter limits the display to trace data recorded on the specified day.



Type: DP

traceFileNameDescription: Name of a call tracing or call path tracing data file on the OMC-R agent

disks. The naming rules are described in Kapsch GSM BSS Fundamen-tals — Operating Principles (411-9001-007).

Object: traceFileReadyRecord

Type: DP

Note: Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL object names (such as TRX, BSC, BTS, BTSSM). All other symbols/characters are prohibited.

traceInfoRequestedDescription: List of information to display with respect to the type. See Kapsch GSM

OMC-R Commands Reference - Configuration, Performance, and Main-tenance menus (411-9001-129).

Value range: [abisInfo / bsicInfo / bssMapInfo / btsInfo / ChannelInfo / cicInfo / dtapInfo / handoverInfo / manufacturerExtInfo A and Ater / manufacturerExtInfo Abis / measurementInfo / msClassmarkInfo / powerControlIn fo / rrInfo / timingAdvanceInfo / trxInfo / txPowerInfo]


Type: DP

traceReferenceDescription: Reference of a trace message received from the MSC.

Value range: [0 to 63] (Phase I)[0 to 65535] (Phase II)

Object: traceFileReadyRecord

Type: DP

411-9001-124 18.08 1.0 Page 385 of 446


traffic PCM allocation priority Class 2Description: Allocation priority of a TDMA frame on the covering site PCMs.

This attribute is used in case of Abis PCM reconfiguration.


Object: transceiver

Type: DP

Checks: • [M]: The parent bsc object is unlocked and the parent bts object is locked.

Release: V9

Note: "0" should be assigned to the highest priority frame(s).

transceiverDescription: Identifier of a transceiver object defined with regard to a bts object.

It defines the parent transceiver object.


Object: channel

Type: Id

Checks: • [C]: The transceiver object is created.

transceiverDescription: Identifier of a transceiver object defined with regard to a bts object.

By definition, a TDMA frame is related to a cell, a cell is related to a site, and a site is related to a BSC.In all MMI commands, a transceiver object can be referred to by the se-quence "siteName.cellName.transceiver", where siteName and cell-Name respectively identify the covering site and cell by name.A TDMA frame is brought in service on the network at creation time. It is working when the parent bts object is unlocked.


Object: transceiver

Type: Id

Checks: • [C]: The number of TDMA frames per cell is limited to 16, regardless of the type of the BSC that controls the cell.• [C]: The handOverControl and powerControl objects are created for the parent bts object.• [C]: If the parent bts object describes a concentric cell, two transceiv-erZone objects are created for that object.• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked and the parent bts object is locked.• [D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.

Page 386 of 446 411-9001-124 18.08 1.0


transceiver equipment class Class 2Description: The class of a TRX/DRX.

The class of a TRX/DRX sets, among others, its maximum transmission power. The attribute possible values have the following meaning:

• Class 1 corresponds to GSM 900 class 5 or GSM 1800/1900 class 1 (20W to 40W transmitters).• Class 2 corresponds to GSM 900 class 6 which is not supported or GSM 1800/1900 class 2 (10W to 20W transmitters).

When dual band (concentric cell) is used, the class of a TRX/DRX en-ables to distinguish which DRX and which TDMA are used in the outer zone or inner zone.

Class 1 corresponds to a TDMA in the frequency band carrying BCCH so belonging to transceiverZone = 0 (large/outer zone). Class 2 corre-sponds to a TDMA in the frequency band not carrying BCCH so belong-ing to transceiverZone = 1 (small/inner zone).

When cell is dualband, transceiver equipment class values differentiate TRX of the main band (for which the class value is 1) and TRX of the ex-tended band (for which the class value is 2).

Value range: [0 (reserved) / 1 / 2]


Type: DP

Checks: • [M]: Concentric cell: If the TRX/DRX is partnered with a TDMA frame, its class matches the TRX/DRX class allotted to the zone to which the TDMA frame belongs (refer to the next entry).

Release: V9

transceiver zone Ref Class 2Description: Identifier of the transceiverZone object that defines the zone to which a

TDMA frame belongs in a concentric cell.

Value range: [0 (large or outer zone) / 1 (small or inner zone)]

Object: transceiver

Condition: To define if the covering cell is concentric

Type: DP

Checks: • [C]: The referenced transceiverZone object is created for the parent bts object.• [M]: The parent bsc object is unlocked and the parent bts object is locked.

Release: V9

transceiverEquipmentDescription: Identifier of a transceiverEquipment object defined with regard to a bts

object. It defines the related transceiverEquipment object.


Object: software

411-9001-124 18.08 1.0 Page 387 of 446


Type: Id

Checks: • [C]: The transceiverEquipment object is created.

transceiverEquipmentDescription: Identifier of a transceiverEquipment object defined with regard to a bts

object.By definition, a TRX/DRX is related to a cell, a cell is related to a site, and a site is related to a BSC.In all MMI commands, a transceiverEquipment object can be referred to by the sequence "siteName.cellName.tr ansceiverEquipment", where siteName and cellName respectively identify the covering site and cell by name.



Type: Id

Checks: • [C]: The number of TRX/DRXs per site is limited to 24, regardless of the type of the BSC that controls the site.• [C]: The number of TRX/DRXs per cell is limited to 16, regardless of the type of the BSC that controls the cell

• [C]: The handOverControl and powerControl objects are created for the parent bts object.• [C]: The referenced lapdLink objects (lapdLinkO MLRef and lap-dLinkRSLRef) are created for the parent bsc object.• [C]: If the application database of the related BSC is built, the parent bsc object is unlocked and the parent bts object is locked.• [D]: If the application database of the related BSC is built, the parent bsc object is unlocked, the parent btsSiteManager and bts objects are locked, and the transceiverEquipment object is locked.

• [D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.• [D]: No traceControl or callPathTrace object refers to the transceiv-erEquipment object (the BSC Call tracing or Call path tracing function does not monitor that object).

transceiver equipment classDescription: Class of the TRX/DRXs partnered with the TDMA frames of the zone.

The class of a TRX/DRX sets, among others, its maximum transmission power. Refer to the previous entry. When dual band (concentric cell) is used, the class of a TRX/DRX en-ables to distinguish which DRX and which TDMA are used in the outer zone or inner zone.Class 1 corresponds to a TDMA in the frequency band carrying BCCH so belonging to transceiverZone = 0 (large/outer zone).Class 2 corre-sponds to a TDMA in the frequency band not carrying BCCH so belong-ing to transceiverZone = 1 (small/inner zone).


Object: transceiverZone

Type: DP


transceiverEquipment

Page 388 of 446 411-9001-124 18.08 1.0


Release: V9

Note: The transceiverZone objects are only created for bts objects that de-scribe concentric cells.

transceiverZoneDescription: Identifier of a transceiverZone object that describes the large zone or the

small zone of a concentric cell.The transceiverZone objects are only significant for the bts objects that describe concentric cells. Two transceiverZone objects are created for each created concentric bts object; one describes the large or outer transmission zone, and the other describes the small or inner transmis-sion zone.

Value range: [0 (large or outer zone) / 1 (small or inner zone)]


Type: Id

Checks: • [C]: The associated bts object is created and the transceiverZone ob-ject is not created for that object.• [C]: The number of transmission zones in a concentric cell equals 2. Each transceiverZone object is one-of-a -kind to the associated bts ob-ject.• [C/D]: If the application database of the related BSC is built, the parent bsc object is unlocked and the associated bts object is locked.• [M]: The parent bsc object is unlocked.• [D]: If the application data-base of the related BSC is not built, it has been reset by an Off line reset BDA command.• [D]: No transceiver object refers to the transceiverZone object.

Release: V9

transcoder3GEqptIdDescription: Identifier of the ’hardware transcoder 3G’ object class. This identifier is

allocated by the MD-R at object creation. The only value allocated by the MD-R is 0. This attribute cannot be modified. This attribute is relevant for TCU 3000.



Type: DP

Release: V13

transcoderDescription: Identifier of a transcoder object defined with regard to a bsc object.

It defines the parent transcoder object.

Value range: [0 to 33] (BSC 3000, E1 PCM network), [0 to 33] (BSC 3000, T1 PCM network)

Object: pcmCircuit (A interface)

Type: Id

Checks: • [C]: The transcoder object is created.

transceiver equipment class

411-9001-124 18.08 1.0 Page 389 of 446


transcoderDescription: Identifier of a transcoder object defined with regard to a bsc object.

Value range: [0 to 33] (BSC 3000, E1 PCM network), [0 to 33] (BSC 3000, T1 PCM network)

Object: transcoder

Type: Id

Checks: • [C]: The number of remote transcoders linked to a BSC is limited to maxTranscdPerBsc (staticconfiguration data).• [C]: The software object related to the parent bsc object is created.• [C]: The referenced lapdLink object (lapd LinkOMLRef) is created for the parent bsc object.• [C]: If the application database of the related BSC is built, the parent bsc object is unlocked.• [D]: If the application database of the related BSC is built, the parent bsc object is unlocked and the transcoder object is locked.• [D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.

transcoderArchitectureDescription: Indicates the TCU hardware configuration. This attribute is modified by

the Manager. Value changes are notified to the Manager. This attribute can only be modified if the BDA is not built.

Value range: [tcu3G / tcu3GOptical / tcu3GOpticalHC]

Object: transcoder

Default value:

Type: DP

Release: V13

Checks: • [C/M]: The maximum PCMs (A and Ater) number is set to 252 (E1) / 336 (T1) at the OMC-R when the transcoderArchitecture parameter is set to the tcu3GOpticalHC value.• [C/M]: At the OMC-R, the maximum CICs number is set to:

• 1984 when the transcoderArchitecture parameter is set to the tcu3G value and is attached to a bsc which has its bscArchitecture pa-rameter set to the bsc30000 value• 2112 when the transcoderArchitecture parameter is set to the tcu3G value and is attached to a bsc which has its bscArchitecture parameter set to the bsc30000Optical value• 3168 when the transcoderArchitecture parameter is set to the tcu3GOptical value• 4150 when the transcoderArchitecture parameter is set to the tcu3GOpticalHC value

transcoderId Class 2Description: Identifier of the remote transcoder linked to the PCM link that carries the

SS7 channel on the A interface.



Page 390 of 446 411-9001-124 18.08 1.0


Type: DP

Checks: • [C/M]: The referenced transcoder object is created and the pcmCircuit object used by the signallingLink object (pcmCircuitId) is related to that object.

transcoderId Class 2Description: Identifier of the remote transcoder linked to the PCM link that carries the

terrestrial circuit on the A interface.


Object: xtp

Type: DP

Checks: • [C/M]: The referenced transcoder object is created and the pcmCircuit object used by the xtp object (pcmCircuitId) is related to that object.

transparentSiteAttrib2 Class 2Description: BSC 2nd class transparent attribute on bstSiteManager MO.

This attribute is modified by the Manager. Value changes are notified to the Manager.

Value range: String [0 to 129]


Type: DP

Release: V14

transparentTeiAttrib2 Class 2Description: BSC transparent attribute on bts MO. Transmitted to SUP-TEI AO and

then to the bts in LOAD_READY message.This attribute is modified by the Manager. Value changes are notified to the Manager.

Value range: String [0 to 27]

Object: bts

Type: DP

Release: V14

tResumeAck Class 3Description: Timer used by the bsc waiting for an MS Resume Ack from a pcu. On

timer expiry, the procedure is canceled. A TCH Release is sent to the MS, requesting this MS to send a Routing Area Update.

Value range: [0..10] (1 unit = 100 ms). The recommended value is 1.

Default value: 0

transcoderId Class 2

411-9001-124 18.08 1.0 Page 391 of 446


Object: bsc


Type: DP

Release: V15

Note: Value 0 is considered as 1 by the BSC.

trmDescription: The Transcoding Resource Module, which is responsible for GSM voc-

oding of the voice channels.


Object: trm

Type: Id

trmArchipelagoCallsDescription: Number of calls per archipelago and per TRM.

Value range: List of 3 archipelagoes. Each of them is a list [coderAlgo, maximumNum-berOfCalls, currentNumberOfCalls] with: coderAlgo: fullRatecoder / en-hancedFullRateCoder / ctmEnhancedFullRateCode / amrFullHalfRateCoder maxi mumNumberOfCalls: 0 to 65535 current-NumberOfCalls: 0 to 65535

Object: trm

Feature: BSC/TCU e3 GET DATA enhancement

Type: DD

Release: V16

trmIdDescription: Identifier of the ’trm’ object class. This identifier is allocated by the MD-

R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000.


Object: trm

Type: DP

Release: V13

trmIncreaseCapacity Class 3Description: Allows the TRM3 increase capacity activation.


tResumeAck Class 3

Page 392 of 446 411-9001-124 18.08 1.0


Object: transcoder

Feature: TRM3 capacity increase


Type: DP

Note: The recommended value is "disabled".

Release: V18.0

Checks: • [C/M]: Checks are performed to determine the presence of a valid li-cense for TRM3 capacity increase on the following operations:• setting the value of the trmIncreaseCapacit y parameter to "enabled"• unlocking a TRX• building the BDA of a BSC• resetting a BDA of a BSCThe attempt to set the "enabled" value of the trmIncreaseCapacity pa-rameter on the transcoder object is possible only when the number of working TCU 3000s allowed to use the TRM3 capacity increase does not exceed the licensed volume.If the check fails, then the corresponding action is rejected and a clear error message displayed.

tsConfigurationDescription: Configuration of the radio TDMA frame time slots.

This dynamic attribute indicates, for each time slot, the reconfiguration state, the type of logical channel supported, the frequency channel used (absoluteRFChannelNo) if the time slot does not hop, the list of fre-quency channels used (mobileAllocation), the maio, and the hopping-SequenceNumber if the time slot hops.When frequency hopping is used if "reconfiguration state" is "true", it means that BSC has recalculated the frequency hopping law following the loss of one or several TRX (defense of TDMA carrying the BCCH. If "reconfiguration state" is "false", it means that the TDMA configuration is the original one.When frequency hopping is not used, this boolean has no meaning and would be set to "false".


Object: transceiver

Type: DD

Remark: Since the time slots are reconfigured after each dynamic reconfiguration of the hopping frequencies, the data can be different from those defined by the user when creating the channel objects.

Release: V8

tSuspendAck Class 3Description: Timer used by the bsc waiting for an MS Suspend Ack message from a

pcu. On timer expiry, the Suspend message is repeated. After three un-successful attempts, the procedure is canceled.

Value range: [1..10] seconds. The recommended value is 1.

Default value: 1

Object: bsc


trmIncreaseCapacity Class 3

411-9001-124 18.08 1.0 Page 393 of 446


Type: DP

Release: V15

Note: Value 0 is considered as 1 by the BSC.

tUsfExt Class 3Description: Throughput optimization timer.

On timer expiry, the USF allocation is optimized in order to give priority to active MSs that share the TS with the inactive MS.


Object: bts

Default value: 0


Type: DP

Checks: • [C/M]: tUsfExt value must be lower than or equal to tNwExtUtbf val-ue.

Release: V15

txPowerMaxReduction Class 2Description: Maximum transmission power level allowed in a TDMA frame (attenua-

tion versus bsTxPowerMax) per transceiver.

Value range: [0 to 30 by step of 2] dB. "0" is the only value accepted.

Object: transceiver

Default value: 0

Type: DP

Checks: • [C/M]: The only value accepted by the system is 0 dB.

Remark: Since the system accepts only one value for this attribute, changing it has no meaning.

type

Description: Type of data to archive or restore.

Value range: [faults / observations / trace data / backup / other data]• Fault data are stored in the "/MD/notif" partition on the OMC-R agent disks.• Observation data are stored in the "/MD/obs" partition on the OMC-R agent disks.• Trace data are stored in the "/MD/trace_function" partition on the OMC-R agent disks.• Backup data are stored on the OMC-R agent disks.• Other data files are defined in the "/MD/config" partition on the OMC-R agent disks.

Object: md - Archive

Type: DP

tSuspendAck Class 3

Page 394 of 446 411-9001-124 18.08 1.0


typeDescription: Type of data to archive or restore.

Value range: [faults / observations / trace data / backup / other data]• Fault data are restored to the "/MD/restored/notif" partition on the OMC-R agent disks.• Observation data are restored to the "/MD/restored/obs" partition on the OMC-R agent disks.• Trace data are restored in the "/MD/restored/trace_function" partition on the OMC-R agent disks.• Other data files are restored to their source directory on the OMC-R agent disks.

Object: md - Restore

Type: DP


Value range: [faults / observations / trace data / backup / backup without eft / PCUO-AM / other data]• Fault data are stored in the "/CMN/base/save_rest" partition on the OMC-R manager disks.• Observation data are stored in the "/OMC/obs" partition on the OMC-R manager disks.• Trace data are stored in the "/CMN/base/save_rest" partition on the OMC-R manager.• Backup data are stored on the OMC-R manager disks.• Other data files are defined in the "/OMC/data" partition on the OMC-R manager disks.

Object: omc - Archive

Type: DP


Value range: [faults / observations / trace data / backup / other data]• Fault data are restored to the "/CMN/base/save_rest" partition on the OMC-R manager disks.• Observation data are restored to the "/OMC/obs" partition on the OMC-R manager disks.• Trace data are restored to the "/CMN/base/save_rest" partition on the OMC-R manager disks.• Other data files are restored to their source directory "/OMC/data" on the manager disks.

Object: omc - Restore

Type: DP

411-9001-124 18.08 1.0 Page 395 of 446


2.21. U

typeDescription: Type of observation report.

Value range: [single observed instance / several observed instance]• single observed instance ....... several observed counters on a single object• several observed instance ....... single counter observed on severalobjects


Type: DP

Release: V11

type of data to be purgedDescription: Type of the OMC data to be purged.

Value range: [traceData]

Object: omc - Data purge

Type: DP

Release: V10

type of displayDescription: Choice of the observation counter display mode.

Value range: [Chart / Table / Text]


Type: DP

Release: V11

Restrictions: • [M]: The cic and timeSlotNumber attributes of an xtp object cannot be modified.

ulBepPeriod Class 2Description: The parameter is used by BTS to derive the forgetting factor used in the

UL to compute averaged MEAN-BEP and CV-BEP.


Object: transceiver


Default value: 0

Page 396 of 446 411-9001-124 18.08 1.0


Type: DP

Release: V15

ulGMSKMCS2UpperThreshold Class 3Description: The parameter allows the operator to set the threshold between MCS2

and the next code in the UL GMSK Only Link Adaptation table.


Object: bts


Default value: 0 (disabled MCS2 in the Link Adaptation Tables)

Type: DP

Release: V15

ulGMSKMCS3UpperThreshold Class 3Description: The parameter allows to set the threshold between MCS3 and the next

code in the UL GMSK Only Link Adaptation table.


Object: bts



Type: DP

Release: V15

ulMCS2UpperThreshold Class 3Description: The parameter is used to set the threshold between MCS2 and the next

code in the UL Link Adaptation table.


Object: bts



Type: DP

Release: V15




Object: bts

ulBepPeriod Class 2

411-9001-124 18.08 1.0 Page 397 of 446




Type: DP

Release: V15




Object: bts



Type: DP

Release: V15




Object: bts



Type: DP

Release: V15




Object: bts



Type: DP

Release: V15

ulMCS3UpperThreshold Class 3

Page 398 of 446 411-9001-124 18.08 1.0





Object: bts



Type: DP

Release: V15

unequippedCircuit Class 1Description: Whether the UNEQUIPPED CIRCUIT messages are used (Phase II

compliance).





Type: DP

Checks: [C/M]: The only accepted value is "false" in V10 and V11.

Remark: Since the system accepts only one value for this attribute in V10 and V11, changing it has no meaning.

Release: V8

unitDescription: The name that identifies the unit.

Value range: String [1 to 2 characters]


Type: DD

Note: This parameter is applicable for TCU3G only.

unknownNCellWarning Class 3Description: Whether feedback of measurements performed by mobiles on neighbor

cells that are unknown to the BSC is allowed.When feedback of measurements is enabled, notifications with codano 1260 are generated. These notifications indicate that measurements are performed on cells which use the same BCCH as a neighbor cell of the serving cell but have different BSICs.


Object: bts

411-9001-124 18.08 1.0 Page 399 of 446



Type: DP

upgradeStatusDescription: Stands whether an upgrade is complete, or is whether or not it is still in

progress.This attribute is dynamically managed by the BSS.Value changes are notified to the manager.

Value range: [notInProgress / inProgress / performed / toBeUpgraded / aborted; du-plicateInProgress; frozen; failed; flashUpdated; Unknown]

Object: transcoder, atmRm, cc, cem, controlNode, iem, iom, interfaceNode, omu, tmu, trm, hardware transcoder 3G, sw8kRm, btsSiteManager, transceiverEquipment


Type: DD

Release: V13



Value range: [notInProgress / inProgress / performed / toBeUpgraded / aborted; duplicateInProgress; frozen; failed; flashUpdated;Unknown]

Object: igm


Type DD

Release: V18.0

unknownNCellWarning Class 3

Page 400 of 446 411-9001-124 18.08 1.0




Value range: [notInProgress / downloadInProgress / activateInProgress / download-Failed / activateFailed / performed]• notInProgress: initial condition at the IPM connection, manual up-

grade

• downloadInProgress: transient state during the software download

• activateInProgress: transient state during the software activation

• downloadFailed: final condition in case of a software download fail-ure (kept until the next IPM connection or manual upgrade)

• activateFailed: final condition in case of a software activation (kept until the next IPM connection or manual upgrade)

• performed: final condition in case of a successful upgrade (kept until the next IPM connection or manual upgrade), so the IPM is up to date

Object: ipm


Type DD

Release: V18.0

uplinkPowerControl Class 3Description: Whether power control in the MS-to-BTS direction is authorized at cell

level.




Type: DP

Release: V8

uplinkPwrCtrlDuringUTDOA Class 3Description: Reserved for future use.


Object: bsc


411-9001-124 18.08 1.0 Page 401 of 446


Type: DP

Release V16

uplinkReply Class 3Description: Defines the use of the uplink-reply procedure, which applies to VBS and

VGCS calls for radio resources optimization.

Value range: [0 to 2] with:• 0: Disabled (recommended value for non-GSM-R customers)• 1: Enabled on all group calls (recommended value for GSM-R custom-ers)• 2: Enabled on all group calls except on emergency group calls (option-al value for GSM-R customers)

Object: bsc

Feature: ASCI

Default value: 0

Type: DP

Release: GSM-R V15

uplinkReplyTimer Class 3Description: Timer value of the uplink-reply procedure.

Value range: [0 to 65535] seconds, with:• 0: the feature is not allowed• 6: recommended minimum value• 120: recommended value

Object: bts

Feature: ASCI

Default value: 120

Type: DP

Release: GSM-R V15

uRxLevDLP Class 3Description: Upper strength threshold for BTS txpwr decrease for step by step algo-

rithm.




Type: DP

uplinkPwrCtrlDuringUTDOA Class 3

Page 402 of 446 411-9001-124 18.08 1.0


uRxLevULP Class 3Description: Upper strength threshold for MS txpwr decrease for step by step algo-

rithm.It is greater than lRxLevULP.




Type: DP

Note: This parameter is significant only when the BTS uses the standard "step by step" power control algorithm.

uRxQualDLP Class 3Description: Upper quality threshold to reduce BTS txpwr for step by step algorithm.

It is lower than or equal to lRxQualDLP.




Type: DP

Checks: • [M]: uRxQualDLP lRxQualDLP


uRxQualULP Class 3Description: Upper quality threshold to reduce MS txpwr for step by step algorithm.

It is lower than or equal to lRxQualULP.




Type: DP

Checks: • [M]: uRxQualULP lRxQualULP


411-9001-124 18.08 1.0 Page 403 of 446


usageStateDescription: Activity state of the Call path tracing function in the BSC.

Refer to the endSessionCriteriaType entry in the Dictionary and the operationalState entry related to the callPathTrace object which de-scribes the possible state parameter combinations for this type of object.

Value range: [idle / busy ]• idle ............. The PCM time slot that conveys the terrestrial circuit is traffic-free.• busy ............. The PCM time slot conveys the terrestrial circuit is work-ing and carrying traffic.


Type: DP

usageState Description: ISO state

Refer to the operationalState entry related to the xtp object which de-scribes the possible state parameter combinations for this type of object.

Value range: [idle / busy / active]• idle ............. The PCM time slot that conveys the terrestrial circuit is traffic-free.• busy ............. The PCM time slot conveys the terrestrial circuit is work-ing and carrying traffic.• active ........... The PCM time slot that conveys the terrestrial circuit is active.

Object: xtp

Type: DD

use default listDescription: Whether the default counter list has to be used.

Value range: [yes]


Type: DP

Release: V11

user nameDescription: Name of an OMC-R user as defined in the user’s profile

(default is the logged-in user’s name).Do not fill in if this criterion is not to be selected.



Type: DP

Page 404 of 446 411-9001-124 18.08 1.0


Checks: • [A]: The related user profile object is created onthe OMC-R.


user profileDescription: Identifier (name) of an OMC-R user.

Value range: [case sensitive, 2 characters min]


Type: DP

Checks: • [C]: The name of a user is one-of-a-kind to the OMC-R.• [M/D]: The user profile object is created.

usernameDescription: Name of the OMC-R user, as defined in the user’s profile, who created

the job.


Type: DD

Object: job


usernameDescription: Name of the OMC-R user, as defined in the user’s profile, who created

the associated job.


Object: obResult

Type: DD


usfGranularity Class 3Description: The type of granularity supported by PCU when dynamic allocation is

available.

Value range: [0]

Object: bts

user name

411-9001-124 18.08 1.0 Page 405 of 446


2.22. V

VEASDCCHOverflowAllowed Class 3

voiceBroadcastService Class 3

voiceGroupCallService Class 3

Feature: EDGE dynamic allocation (20230)

Default value: 0 (granularity 1)

Type: DP

Release: V15

Description: Used to allow (or not) the SDCCH overflowing when EVEA is activated.

Value range: [disabled / allowed]

Object: bts

Feature: Enhanced very early assignment


Type: DP

Release: V18.0

Description: Authorize Voice Broadcast Service.





Type: DP

Release: V12

Description: Authorize Voice Group Call Service.





Type: DP

Release: V12

usfGranularity Class 3

Page 406 of 446 411-9001-124 18.08 1.0


VSWR meter Class 2

2.23. W

workstation name

wPSManagement Class 3

wPSQueueStepRotation Class 3

Description: Presence or absence of the optional equipment "voltage stationary wave rate meter" in:• BTS e-cell• BTS S2000H/S2000L• BTS S8000 Indoor or Outdoor, S8002, S8003, S8006• BTS 6000• BTS 9000• BTS 18000



Type: DP

Release: V9

Description: Name of a workstation as defined in its profile (default is the logged-in user’s workstation).


Object: omc - Display workstation markers

Type: DP

Checks: • [A]: The terminal profile object describing the workstation is created on the OMC-R.


Description: WPS feature is enabled or disabled.

Value range: [disabled 0 ; enabled 1]

Object: bsc

Feature: WPS queuing managment (22463)


Type: DP

Checks: • [A]: The terminal profile object describing the workstation is created on the OMC-R.

Release: V15

Description: One out of the WPSQueueStepRotation value to first have an evaluation of the WPS queues in the radio resource allocator.


Object: bts

Feature: WPS public access bandwidth protection (2246

Default value: 4

411-9001-124 18.08 1.0 Page 407 of 446


2.24. X

xtp

2.25. Z

zI bss

Type: DP

Checks: [A]: The terminal profile object describing the workstation is created on the OMC-R.

Release: V15

Description: Identifier of an xtp object (eXchange Termination Point) defined with re-gard to a bsc object.


Object: xtp

Type: Id

Checks: • [C]: The software object related to the bsc object is created.• [C/M]: The referenced pcmCircuit object (pcmCircuitId) is assigned to the A interface and depends on the same transcoder object (trans-coderId) as the xtp object.• [C]: The time slot used by the xtp object (timeSlotNumber) is identical to the mscPcmTsNumber component of the cic attribute.• [C/M]: The referenced PCM,TS pair (pcmCircuitId and timeSlot-Number) is not already assigned to an xtp or signallingLink object de-pendent on the same transcoder object, and the time slot is not mapped on the TS used by the OMC channel on the Ater interface.• [C/M]: If the terrestrial circuit uses PCMA link no.3 (pcmCircuitId), the timeSlotNumber is in the range [1 to 27] if the PCM link is an E1 link or in the range [1 to 20] if the PCM link is a T1 link. Since the last four time slots of that link are not mapped on the Ater interface, they are unusable (refer to the transcoderMatrix entry in the Dictionary).• [C]: If the application database of the related BSC is built, the parent bsc object is unlocked.• [D]: If the application database of the related BSC is built, the parent bsc object is unlocked and the xtp object is locked.• [D]: If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.• [D]: No traceControl or callPathTrace object refers to the xtp object (the Call tracing and Call path tracing functions do not monitor that ob-ject).

Restrictions: • [M]: The cic and timeSlotNumber attributes of an xtp object cannot be modified.

Description: List of selected BSCs that defines a BSS zone of interest.Enter "all" to include all the BSCs created on the OMC-R.If the ZI bss list should include only a subset of BSCs, fill in the list as follows:• The Add button allows to add a BSC to the list.• The Delete button allows to remove selected BSCs from the list. A BSS terminal zone of interest allows users to filter the unsolicited mes-sages (output domain) that can be output on the terminal outside users’ work sessions according to the BSS entities that send them.


Type: DP

Note: The user can enter a BSC in the list that is not created yet.When it is created, this BSC will be handle as the other BSCs already created.

Page 408 of 446 411-9001-124 18.08 1.0


zI bss

zone frequency hopping Class 2

zone frequency threshold Class 2

Description: List of selected BSCs that defines a BSS zone of interest.Enter "all" to include all the BSCs created on the OMC-R.If the ZI bss list should include only a subset of BSCs, fill in the list as follows:• The Add button allows to add a BSC to the list.• The Delete button allows to remove selected BSCs from the list.A BSS user’s zone of interest defines the BSS entities the user is entitled to work on. It allows to filter both the MMI commands they can enter (command domain) according to the objects managed by these com-mands and the unsolicited messages (output domain) they have access to according to the BSS entities that send them.


Type: DP

Note: The user can enter a BSC in the list that is not created yet.When it is created, this BSC will be handle as the otherBSCs already created.

Description: Whether frequency hopping is authorized in the zone.If frequency hopping is not allowed in a zone, the channel objects that describe the radio time slots of the TDMA frames used in the zone can-not be allowed to hop.

Value range: [hopping / not hopping]


Default value: not hopping

Type: DP


Release: V9


Description: Minimum number of frequencies needed to allow frequency reconfigu-ration in the zone.



Default value: 1

Type: DP


Release: V9


411-9001-124 18.08 1.0 Page 409 of 446


zone Tx power max reduction Class 2

Description: Attenuation vs bsTxPowerMax that defines the maximum TRX/DRX transmission power in the zone.



Default value: 0

Type: DP

Checks: • [C/M]: zone Tx power max reduction equals zero if the transceiver-Zone object describes the cell outer zone. It is greater than zero if the transceiverZone object describes the cell inner zone.• [M]: The parent bsc object is unlocked and the associated bts object is locked.

Release: V9


Page 410 of 446 411-9001-124 18.08 1.0


411-9001-124 18.08 1.0 Page 411 of 446


A. Objects and parameters evolution

This appendix categorizes new configuration parameters and objects by release

A.1. V18.0 Pick and Choose 2 parameters

A.2. V18.0 Pick and Choose 1 parameters

Parameter Object

AllocPriorityTimerT14Railways bts

Comment btsSiteManager

Comment bts

GsmUmtsCombBcchTeiVal bts

Parameter Object

3GAccessMinLevelOffset bts

3GReselectionThreshold bts

administrativeState igm

administrativeState ipgRc

administrativeState ipm

amrWbDlAdaptationSet bts

amrWbNbMaxPdtchPreemption bts

amrWbSacchPowerOffsetSelection bts

amrWbUlAdaptationSet bts

amrWBIntercellCodecMThresh handOverControl

amrWBIntracellCodecMThresh handOverControl

amrWBiRxLevDLH handOverControl

amrWBiRxLevULH handOverControl

amrWBPowerControlCIThresholdUl powerControl

availabilityStatus igm

availabilityStatus ipgRc

availabilityStatus ipm

btsType btsSiteManager

Page 412 of 446 411-9001-124 18.08 1.0


concentAlgoExtRxLevUL handOverControl

concentAlgoIntRxLevUL handOverControl

directAllocIntFrRxLevDL handOverControl

directAllocIntFrRxLevUL handOverControl

EATrafficLoadEnd bts

EATrafficLoadStart bts

enableRepeatedFacchHr bts

enableRepeatedFacchWBFr bts

IP@ of IBOS connected to IPM ipm

ipAggregateEthernetPortUsed ipgRc

ipCompressionActivation btsSiteManager

ipCompressionDepth btsSiteManager

ipCRPnChannel_TosDscp ipgRc

ipCRPnChannel_userPriority ipgRc

ipDefaultGateway ipgRc

ipDHCPServerList ipgRc

ipgPcmList ipgRc

ipgRc Reference igm

ipIpgRcCounterPeriod ipgRc

ipIBOSEthernetPortUsed ipgRc

ipIBOSTraffic_TosDscp ipgRc

ipIBOSTraffic_userPriority ipgRc

ipm MAC address Core A ipm

ipm MAC address Core B ipm

ipPortIPAddress_VRId_List ipgRc

ipRoutingProtocolOnAbisPort ipgRc

ipRoutingProtocolOnAggregatePort ipgRc

ipRoutingProtocolOnIBOSPort ipgRc

ipRoutingTable ipgRc

Parameter Object

411-9001-124 18.08 1.0 Page 413 of 446


ipPdvManualSet btsSiteManager

ipPdvSelfTuningRange btsSiteManager

ipRTPnChannel_TosDscp ipgRc

ipRTPnChannel_userPriority ipgRc

IPSEC Payload ipm

ipServiceChannel_TosDscp ipgRc

ipServiceChannel_userPriority ipgRc

ipSynchroPacketPeriod btsSiteManager

ipSynchroUplinkActivation btsSiteManager

ipTrafficPacketPeriod btsSiteManager

MIB version executableSoftware

fullHRCellLoadEnd bts

fullHRCellLoadStart bts

nAMRWBRequestedCodec handOverControl

operationalState igm

operationalState ipgRc

operationalState ipm

positionInShelf igm

positionInShelf ipgRc

related bts site manager list ipm

sharedPDTCHratio bts

shelfNumber igm

shelfNumber ipgRc

standbyStatus igm

sWVersionActive ipm

sWVersionPassive ipm

taDetectionDataExtCell bts

tfoActivation bsc

trmIncreaseCapacity transcoder

Parameter Object

Page 414 of 446 411-9001-124 18.08 1.0


A.3. New V17 parameters

upgradeStatus igm

upgradeStatus ipm

VEASDCCHOverflowAllowed bts

Parameter Object

adaptiveReceiver transceiver

administrativeState hsaRc

administrativeState hsaRcTcu

availabilityStatus hsaRc

availabilityStatus hsaRcTcu

bssPagingCoordination bts

cId adjacentCellUTRAN

compressedModeUTRAN bts

diversityUTRAN adjacentCellUTRAN

dynamicAbis btsSiteManager

earlyClassmarkSendingUTRAN bts

fDDARFCN adjacentCellUTRAN

fDDMultiratReporting bts

fDDReportingThreshold handOverControl

fDDReportingThreshold2 handOverControl

gsmToUMTSServiceHo bsc

gprsPreemptionForHR bsc

hoMarginUTRAN adjacentCellUTRAN

hoMarginAMRUTRAN adjacentCellUTRAN

hoMarginDistUTRAN adjacentCellUTRAN

hoMarginRxLevUTRAN adjacentCellUTRAN

hoMarginRxQualUTRAN adjacentCellUTRAN

Parameter Object

411-9001-124 18.08 1.0 Page 415 of 446


hoMarginTrafficOffsetUTRAN adjacentCellUTRAN

hoPingpongCombinationUTRAN adjacentCellUTRAN

hoPingpongTimeRejectionUTRAN adjacentCellUTRAN

hoRejectionTimeOverloadUTRAN bsc

hsaPcmList hsaRc

hsaPcmList hsaRcTcu

Licenses needed to put object in service Display RM Capacity - md

Licenses needed to put object in service Display RM Capacity - bsc

Licenses needed to put object in service Display RM Capacity - btsSiteManager

Licenses used by this object Display RM Capacity - md

Licenses used by this object Display RM Capacity - bsc

Licenses used by this object Display RM Capacity - btsSiteManager

locationAreaCodeUTRAN adjacentCellUTRAN

mobileCountryCodeUTRAN adjacentCellUTRAN

mobileNetworkCodeUTRAN adjacentCellUTRAN

Number of xtp under this BSS Display 4K Erlangs - md

Number of xtp under this BSS Display 4K Erlangs - bsc

offsetPriorityUTRAN adjacentCellUTRAN

operationalState hsaRc

operationalState hsaRcTcu

positionInShelf hsaRc

positionInShelf hsaRcTcu

qsearchC handOverControl

reportTypeMeasurement bts

rNCId adjacentCellUTRAN

scramblingCode adjacentCellUTRAN

rxLevDLPbgtUTRAN adjacentCellUTRAN

rxLevMinCellUTRAN adjacentCellUTRAN

servingBandReporting bts

Parameter Object

Page 416 of 446 411-9001-124 18.08 1.0


ServingBandReportingOffset handOverControl

shelfNumber hsaRc

shelfNumber hsaRcTcu

signallingLink field signallingLinkSet

signallingLinkResourcesStates signallingLinkSet

signallingLinkResState signallingLinkSet

slkAResource field signallingLinkSet

slkAssociatedTmuPortPosition signallingLink

slkAssociatedTmuPortPosition field signallingLinkSet

slkATerResource signallingLink

slkATerResource field signallingLinkSet

smartPowerManagementConfig powerControl

smartPowerSwitchOffTimer powerControl

standbyStatus hsaRc

standbyStatus hsaRcTcu

standbyStatus TMU

synchronizingHsaRc bsc

t3121 bts

This BSS is using license Display 4K Erlangs - mds

This BSS is using license Display 4K Erlangs - bsc

Total licenses for this OMC-R Display RM Capacity - mdDisplay 4K Erlangs - md

Total licenses for this OMC-R Display RM Capacity - bscDisplay 4K Erlangs - bsc

Total licenses for this OMC-R Display RM Capacity - btsSiteManager

Total unused licenses Display RM Capacity - mdDisplay 4K Erlangs - md

Total unused licenses Display RM Capacity - bscDisplay 4K Erlangs - bsc

Total unused licenses Display RM Capacity - btsSiteManager

Parameter Object

411-9001-124 18.08 1.0 Page 417 of 446



Parameter Object

aterLapd lsaRc

bckgDLLayer3WindowSize bsc

channelReleaseonAbisFailure bts

eGPRSlrUlActivation bts

enableRepeatedFacchFr bts

facchPowerOffset bts

frPowerControlTargetModeDl PowerControl

hrPowerControlTargetModeDl PowerControl

interferenceMatrixRunningOnBts bts

interferenceMatrixRunningOnBsc bsc

minNbOfJokersPerConnectedMain transceiver

monitoredObjectClass mdWarning

nACCActivation bts

packetFlowContext powerControl

packetSiStatus bts

pcuCellState pcu

pfcActivation bts

pfcArp1ConversationalCSCallProtection powerControl

pfcArp1StreamingCSCallProtection powerControl





pfcFlowControlActivation bts

pfcMinNrtBandwidthPerTs transceiver

pfcMinNumberOfJokersforTsGuaranteedBitRate transceiver

pfcNrtRequestedDnMbrCounterThreshold powerControl

Page 418 of 446 411-9001-124 18.08 1.0



pfcNrtRequestedUpMbrCounterThreshold powerControl

pfcPreemptionRatioGold powerControl

pfcPreemptionRatioSilver powerControl

pfcRtDowngradeAllowed powerControl

pfcRtRequestedDnGbrCounterThreshold powerControl

pfcRtRequestedUpGbrCounterThreshold powerControl

pfcT6 powerControl

pfcT8 powerControl

pfcTsGuaranteedBitRateDl powerControl

pfcTsGuaranteedBitRateUl powerControl

privilegedCell bts

sacchPowerOffset bts

sacchPowerOffsetSelection bts

sigPowerOverboost bts

trmArchipelagoCalls trm

uplinkPwrCtrlDuringUTDOA bsc

Parameter Object

allocPriorityTable bts

allocPriorityTimers bts

amrUlHrAdaptationSet bts

amrDlHrAdaptationSet bts

amrUlFrAdaptationSet bts

amrDlFrAdaptationSet bts

available synchronization sources bts

beacBatteryRemoteControllerPresence btsSiteManager

batteryRemoteControllerPresence btsSiteManager

Parameter Object

411-9001-124 18.08 1.0 Page 419 of 446


bEPPeriod bts

bscHighSwitchingCapacity bsc

bssSccpConnEst signallingPoint or signallingLinkSet

bssSccpInactRx signallingPoint or signallingLinkSet

bssSccpInactTx signallingPoint or signallingLinkSet

bssSccpRelease signallingPoint or signallingLinkSet

bssSccpSubSysTest signallingPoint or signallingLinkSet

btsSMSynchroMode btsSiteManager

callDropActivation bts

concentricCell bts

cpueNumber btsSiteManager

css7LocalSubSystemNumber signallingLinkSet

css7RemoteSubSystemNumber signallingLinkSet

current synchronization mode bts

dARPPh1Priority transceiver

degradedCause bts

degradedCause transceiver

delivery bts

distributionActivation bts

distributionDuration bts

distributionQualityThreshold bts

distributionTime bts

diversity bts

dlGMSKMCS2UpperThreshold bts

dlGMSKMCS3UpperThreshold bts

dlMCS2UpperThreshold bts




Parameter Object

Page 420 of 446 411-9001-124 18.08 1.0




edgeDataServiceType transceiver

edgeFavor transceiver

eDGEMixity bts

egprsServices bts

emergencyThreshold signallingPoint

agpsTimer bsc

estimatedSiteLoad btsSiteManager

extUtbfNoData bts

fERThreshold1 bts

fERThreshold2 bts

fERThreshold3 bts

fERThreshold4 bts

filteredTrafficCoefficient bts

floor bts

fnOffset btsSiteManager

fullDlKa bts

gprsNetworkModeOperation bts

gprsState bts

gprsState transceiver

initialMCSDL transceiver

initialMCSUL transceiver

jokerPerMainTarget transceiver

mainNetworkBand bsc

masterBtsSMId btsSiteManager

msPowerClassToggle bts

nbLargeReuseDataChannels bts

numberOfJokerDS0 transceiver

Parameter Object

411-9001-124 18.08 1.0 Page 421 of 446


nUsfExt bts

nwExtUtbf bts

onePhaseAccess bts

onePhaseDnMsCapability bts

onlyExtUtbf bts

reportTypeMeas bts

rLCPolling bts

sGSNRelease bts

standardIndicator bts

suspendResumeActivation bsc

systemInfoType2 bts

tGMMKeepAlive bts

timerGcchNotif signallingPoint

tnOffset btsSiteManager

tNwExtUtbf bts

tResumeAck bsc

tSuspendAck bsc

tUsfExt bts

ulBepPeriod transceiver

ulGMSKMCS2UpperThreshold bts

ulGMSKMCS3UpperThreshold bts

ulMCS2UpperThreshold bts






uplinkReply bsc

uplinkReplyTimer bts

Parameter Object

Page 422 of 446 411-9001-124 18.08 1.0



usfGranularity bts

wPSManagement bsc

wPSQueueStepRotation bts

Parameter Object

peakThroughputLimitation powerControl

upQoSCriterion powerControl

dwQoSCriterion powerControl

minThroughputGold powerControl

minThroughputSilver powerControl

minThroughputBronze powerControl

preemptionRatioGold powerControl

preemptionRatioSilver powerControl

voicePreemptionGold powerControl

voicePreemptionSilver powerControl

voicePreemptionBronze powerControl

admissionCtrlGold powerControl

admissionCtrlSilver powerControl

admissionCtrlBronze powerControl

frPowerControlTargetMode powerControl

hrPowerControlTargetMode powerControl

powerIncrStepSizeDL powerControl

powerIncrStepSizeUL powerControl

powerRedStepSizeDL powerControl

powerRedStepSizeUL powerControl

gsmToUmtsReselection bts

gsmToUmtsReselection bts

Parameter Object

411-9001-124 18.08 1.0 Page 423 of 446


uMTSSearchLevel bts

uMTSReselectionOffset bts

uMTSAccessMinLevel bts

uMTSReselectionARFCN bts

amrAdaptationSet bts

hrCellLoadEnd bts

hrCellLoadStart bts

selfAdaptActivation bts

hrAmrPriority transceiver

nbOfFramesForFER bts

rxLevRxQualDistributionActivation bts

rxQualThresholdDistribution bts

transparentTeiAttrib2 bts

amrDirectAllocIntRxLevDL handOverControl

amrDirectAllocIntRxLevUL handOverControl

amrDirectAllocRxLevDL handOverControl

amrDirectAllocRxLevUL handOverControl

amrFRIntracellCodec handOverControl

amrHRIntercellCodec handOverControl

amrHRToFRIntraCodec handOverControl

amrReserved1 handOverControl

amrReserved2 handOverControl

amriRxLevDLH handOverControl

amriRxLevULH handOverControl

capacityTimeRejection handOverControl

enhCellTieringConfiguration handOverControl

nCapacityFRRequestedCodec handOverControl

offsetNeighbouringCell handOverControl

nFRRequestedCodec handOverControl

Parameter Object

Page 424 of 446 411-9001-124 18.08 1.0


nHRRequestedCodec handOverControl

pRequestedCodec handOverControl

minTimeQualityIntraCellHO handOverControl

rxQualAveBeg handOverControl

servingFactorOffset handOverControl

adjacentCellReselectionId adjacentCellReselection

adjacentCellHandOverId adjacentCellHandOver

hoMarginAMR adjacentCellHandOver

bscCapacityReduction bsc, signallingPoint

frAmrPriority transceiver

lcsType bsc

sIkAssociatedTmuPortPosition signallingLink

sIkATerResource signallingLink

transparentSiteAttrib2 btsSiteManager

dynamicAgprsAllowed pcu

cCCHGprsAtBtsLevel bts

agprsFilterCoefficient bts

t3168 bts

t3192 bts

flowControlMaxDelay pcusn

Parameter Object

411-9001-124 18.08 1.0 Page 425 of 446


B. Objects and parameters evolution

This appendix categorizes new configuration parameters and objects by release.

B.1. V18.0 Pick and Choose 3 parameters

B.2. V18.0 Pick and Choose 2 parameters

B.3. V18.0 Pick and Choose 1 parameter

Parameter Object

dataOnNoHoppingTS bts

bsc3000optical_ip bsc

Parameter Object

AllocPriorityTimerT14Railways bts

Comment btsSiteManager

Comment bts

GsmUmtsCombBcchTeiVal bts

Parameter Object

3GAccessMinLevelOffset bts

3GReselectionThreshold bts

administrativeState igm

administrativeState ipgRc

administrativeState ipm

amrWbDlAdaptationSet bts

amrWbNbMaxPdtchPreemption bts

amrWbSacchPowerOffsetSelection bts

amrWbUlAdaptationSet bts




Page 426 of 446 411-9001-124 18.08 1.0



amrWBPowerControlCIThresholdUl powerControl

availabilityStatus igm

availabilityStatus ipgRc

availabilityStatus ipm

btsType btsSiteManager

concentAlgoExtRxLevUL handOverControl

concentAlgoIntRxLevUL handOverControl



EATrafficLoadEnd bts

EATrafficLoadStart bts

enableRepeatedFacchHr bts

enableRepeatedFacchWBFr bts

IP@ of IBOS connected to IPM ipm

ipAggregateEthernetPortUsed ipgRc

ipCompressionActivation btsSiteManager

ipCompressionDepth btsSiteManager

ipCRPnChannel_TosDscp ipgRc

ipCRPnChannel_userPriority ipgRc

ipDefaultGateway ipgRc

ipDHCPServerList ipgRc

ipgPcmList ipgRc

ipgRc Reference igm

ipIpgRcCounterPeriod ipgRc

ipAggregateEthernetPortMonitored ipgRc

ipIBOSTraffic_TosDscp ipgRc

ipIBOSTraffic_userPriority ipgRc

ipm MAC address Core A ipm

Parameter Object

411-9001-124 18.08 1.0 Page 427 of 446


ipm MAC address Core B ipm

ipPortIPAddress_VRId_List ipgRc

Parameter Object

Page 428 of 446 411-9001-124 18.08 1.0


C. Parameters per feature

This appendix presents BSS parameters per feature.

C.1. AMR for group calls (VGCS or VBS)• preferredNonAdaptativeAMRcodec

C.2. AMR based on traffic• filteredTrafficCoefficient (bts)

C.3. AMR Optimizations• amrDlFrAdaptationSet (bts)

• amrDlHrAdaptationSet (bts)

• amrUlFrAdaptationSet (bts)

• amrUlHrAdaptationSet (bts)

C.4. BSC/TCU 3000• administrativeState (atmRm, cc, cem, controlNode, hardware bsc 3G, hardware

transcoder 3G, iem, interfaceNode, lsaRc, mms, omu, sw8kRm, tmu, trm, hsaRc, hsaRcTcu, iom)

• availabilityStatus (hsaRcTcu)

• operationalState (atmRm, cc, cem, controlNode, hardware bsc 3G, hardware trans-coder 3G, iem, interfaceNode, lsaRc, mms, omu, sw8kRm, tmu, trm, hsaRc, has-RcTcu, iom)

• cTU cable (iem)

• hsaPcmList (hsaRcTcu, iom)

• hsaRc Reference (iom)

• interOmuEtherlinkOper (controlNode)

• lsaPcmList (iem, lsaRc)

• lsaRc Reference (iem)

• mmsUsage (mms)

• numberOfEnabledHDLCPorts (iem, tmu)

• port Ethernet operational (omu)

• port Ethernet status (omu)

• port 0 X25 status (omu)

411-9001-124 18.08 1.0 Page 429 of 446


• port 1 X25 status (omu)

• positionInShelf (atmRm, cc, cem, iem, hsaRc, hsaRcTcu, lsaRc, mms, omu, sw8kRm, tmu, trm, iom, hsaRc)

• shelfNumber (hsaRc, hsaRcTcu, iem, iom, lsaRc)

• standbyStatus (hsaRc, hsaRcTcu, iem, iom, lsaRc)

C.5. BSC 3000 cell group management/load balancing• associatedTMUPosition (btsSiteManager, signallingLinkSet, transcoder, pcu)

C.6. BSC 3000 switching increase capacity• bscHighSwitchingCapacity (bsc)

C.7. BSC overload management• processorLoadSupConf (bsc)

C.8. Dualband cell management• biZonePowerOffset (adjacentCellHandOver)

• biZonePowerOffset (handOverControl)

• concentric cell (bts)

• msTxPwrMax2ndBand (bts)

• standard indicator AdjC (adjacentCellHandover)

• standard indicator AdjC (adjacentCellReselection)

• standardIndicator (bts)

C.9. EDGE dynamic allocation• eDGEMixity (bts)

• usfGranularity (bts)

C.10. EDGE traffic management• bEPPeriod (bts)

• edgeFavor (transceiver)

• egprsServices (bts)

• initialMCSDL (transceiver)

• initialMCSUL (transceiver)

• jokerPerMainTarget (transceiver)

• sGSNRelease (bts)

Page 430 of 446 411-9001-124 18.08 1.0


C.11. EDGE link adaptation• dlGMSKMCS2UpperThreshold (bts)

• dlGMSKMCS3UpperThreshold (bts)

• dlMCS2UpperThreshold (bts)






• ulBepPeriod (transceiver)

• ulGMSKMCS2UpperThreshold (bts)

• ulGMSKMCS3UpperThreshold (bts)

• ulMCS2UpperThreshold (bts)






C.12. GSM-R V12• additional supervised PCM 0 (btsSiteManager)

• additional supervised PCM 1 (btsSiteManager)





• additional unmasked users alarms (btsSiteManager)

• eMLPPThreshold (signallingPoint)

• nCHPosition (bts)

411-9001-124 18.08 1.0 Page 431 of 446


• preemptionAuthor (signallingPoint)

• preemptionConfiguration (signallingPoint)

• voiceBroadcastService (signallingPoint)

• voiceGroupCallService (signallingPoint)

C.13. GSM-R V15• emergencyThreshold (signallingPoint)

• msPowerClassToggle (bts)

• timerGcchNotif (signallingPoint)

• uplinkReply (bsc)

• uplinkReplyTimer (bts)

C.14. GPRS (SV407 - V12)• administrativeState (pcu)

• associatedInterface (lapdLink)

• availabilityStatus (pcu)

• availabilityStatus (pcusn)

• bscGprsActivation (bsc)

• bscRefList (pcusn)

• bsCvMax (bts)

• btsSensitivity (bts)

• btsSensitivityInnerZone (bts)

• channelType (channel)

• codingScheme (transceiver)

• drxTimerMax (bts)

• dwAckTime (transceiver)

• geographical coordinates (pcusn)

• gprsCellActivation (bts)

• gprsPermittedAccess (bts)

• lapdConcentration (lapdLink)

Page 432 of 446 411-9001-124 18.08 1.0


• lapdTerminalNumber (lapdLink)

• longTbfLossThroughput (bts)

• longTbfSizeThreshold (bts)

• maxBsTransmitPowerInnerZone (bts)

• maxDnTbfP1P2Threshold (bts)

• maxDnTbfPerTs (bts)

• maxDwAssign (bts)

• maxNbrPDAAssig (transceiver)

• maxNbrPUDWithoutVchange (transceiver)

• maxNbrRLCEmptyBlock (transceiver)

• maxUpTbfP1P2Threshold (bts)

• maxUpTbfPerTs (bts)

• msCapWeightActive (bts)

• muxNumber (pcusn)

• n3103 (bts)

• n3105max (transceiver)

• nAvgl (bts)

• nAvgT (bts)

• nAvgW (bts)

• nbrFreeTchBeforeAnticipation (bts)

• nbrFreeTchToEndAnticipation (bts)

• nbrTch (pcu)

• operationalState (pcu)

• operationalState (pcusn)

• panDec (bts)

• panInc (bts)

• panMax (bts)

411-9001-124 18.08 1.0 Page 433 of 446


• pcmCircuit (pcmCircuit)

• pcmNbr (pcu)

• pcmType (pcmCircuit)

• pcu (pcu)

• pcuLapdEqptRefList (pcu)

• pcusn (pcusn)

• routingArea (bts)

• speechOnHoppingTs (bts)

• t3172 (bts)

• upAckTime (transceiver)

C.15. GPRS (TF1134 - NMO I)• gprsNetworkModeOperation (bts)

C.16. GPRS (TF1121 - V12)• gprsPreemption (bts)

• gprsPreemptionProtection (bts)

• gprsPriority (transceiver)

• minNbrGprsTs (bts)

C.17. GPRS TBF establishment improvement: one phase access• onePhaseAccess (bts)

• onePhaseDnMsCapability (bts)

C.18. GPRS / EDGE Suspend and Resume• suspendResumeActivation (bsc)

• tResumeAck (bsc)

• tSuspendAck (bsc)

C.19. PCUSN - more than 12 Agprs PCMs per BSC• bscPcuPcmRefList (pcu)

• gprsPcuCrossConnectList (pcu)

C.20. Network Synchronization• btsSMSynchroMode (btsSiteManager)

• dARPPh1Priority (transceiver)

Page 434 of 446 411-9001-124 18.08 1.0


• fnOffset (btsSiteManager)

• tnOffset (btsSiteManager)

C.21. BTS Synchronization• available synchronization sources (bts)

• current synchronization mode (bts)

• masterBtsSMId (btsSiteManager)

C.22. Automatic Cell Tiering• btsReserved3 (bts)

• hoMarginTiering (handOverControl)

• interferenceType (adjacentCellHandOver)

• intraCell (handOverControl)

• numberOfPwciSamples (handOverControl)

• selfTuningObs (handOverControl)

C.23. Handover for traffic reasons• hoMarginTrafficOffset (adjacentCellHandOver)

• hoTraffic (bsc)

• hoTraffic (bts)

C.24. Handover decision (adjacent cell priority and load)• offsetLoad (adjacentCellHandOver)

• offsetPriority (adjacentCellHandOver)

C.25. General protection against pingpong handover• bts time between HO configuration (bts)

• directedRetryPrio (bts)

• hoPingpongCombination (adjacentCellHandOver)

• hoPingpongTimeRejection (adjacentCellHandOver)

• timeBetweenHOConfiguration (bsc)

C.26. Intracell handover enhancements• lRxQualDLH (handOverControl)

• lRxQualULH (handOverControl)

C.27. AR 264

411-9001-124 18.08 1.0 Page 435 of 446


• cellReselectOffset (bts)

• penaltyTime (bts)

• temporaryOffset (bts)

C.28. Mixed hybrid and cavity combiner BTSs• btsWithCavity (bts)

C.29. Call drop analysis• callDropActivation (bts)

C.30. Extended CCCH• channelType (channel)

C.31. CPU/BIFP load sharing• cpueNumber (btsSiteManager)

C.32. Distribution on Radio measurements• distributionActivation (bts)

• distributionDuration (bts)

• distributionTime (bts)

• distributionQualityThreshold (bts)

• fERThreshold1 (bts)




• nbOfFramesForFER (bts)

C.33. Extended UL TBF• extUtbfNoData (bts)

• fullDlKa (bts)

• nUsfExt (bts)

• nwExtUtbf (bts)

• onlyExtUtbf (bts)

• tNwExtUtbf (bts)

• tUsfExt (bts)

C.34. Broadcast of PSI 13

Page 436 of 446 411-9001-124 18.08 1.0


• maxRACH (bts)

C.35. L1M evolutions for advanced features support• measurementProcAlgorithm (bts)

C.36. Fast power control at TCH assignment• new power control algorithm (bts)

C.37. Data Backhaul Evolution• numberOfJokerDS0 (transceiver)

C.38. Disabling TBF Keep Alive• tGMMKeepAlive (bts)

C.39. PCM error correction• enhancedTRAUFrameIndication (bsc)

• pcmErrorCorrection (bts)

C.40. Unequipped circuit and circuit group block• circuitGroupBlock (signallingPoint)

• unequippedCircuit (signallingPoint)

C.41. WPS public access bandwidth protection• wPSQueueStepRotation (bts)

C.42. PS queuing management• allocPriorityTable (bts)

• allocPriorityTimers (bts)

• allocWaitThreshold (bts)

C.43. BSC/TCU e3 GET DATA enhancement• aterLapd (lsaRc)

• trmArchipelagoCalls (trm)

C.44. Network Assisted Cell Change for release 4 MS• nAccActivation (bts)

• packetSiStatus (bts)

C.45. BSS Packet Flow Context• packetFlowContext (powerControl)

• pfcActivation (bts)

• pfcArp1ConversationalCSCallProtection (powerControl)

• pfcArp1StreamingCSCallProtection (powerControl)

411-9001-124 18.08 1.0 Page 437 of 446






• pfcFlowControlActivation (bts)

• pfcMinNrtBandwidthPerTs (transceiver)

• pfcMinNumberOfJokersforTsGuaranteedBitRate (transceiver)

• pfcNrtRequestedDnMbrCounterThreshold (powerControl)

• pfcNrtRequestedUpMbrCounterThreshold (powerControl)

• pfcPreemptionRatioGold (powerControl)

• pfcPreemptionRatioSilver (powerControl)

• pfcRtDowngradeAllowed (powerControl)

• pfcRtRequestedDnGbrCounterThreshold (powerControl)

• pfcRtRequestedUpGbrCounterThreshold (powerControl)

• pfcT6 (powerControl)

• pfcT8 (powerControl)

• pfcTsGuaranteedBitRateDl (powerControl)

• pfcTsGuaranteedBitRateUl (powerControl)

C.46. BSC 3000 support of BTS background downloading• bckgDLLayer3WindowSize (bsc)

C.47. Optimized Agprs cell allocation• privilegedCell (bsc)

C.48. EDGE Dynamic Agprs• dynamicAgprsAllowed (pcu)

• minNbOfJokersPerConnectedMain (transceiver)

C.49. Switch Interference Matrix• interferenceMatrixRunningOnBts (bts)

• interferenceMatrixRunningOnBsc (bts)

C.50. Channel release policy on BTS after Abis failure

Page 438 of 446 411-9001-124 18.08 1.0


• channelReleaseOnAbisFailure (bts)

C.51. PM1270 - TDMA based counters• monitoredObjectClass (mdWarning)

C.52. Tx power offset for signalling channels• facchPowerOffset (bts)

• sacchPowerOffsetSelection (bts)

• sacchPowerOffset (bts)

• hrPowerControlTargetModeDl (PowerControl)

• frPowerControlTargetModeDl (PowerControl)

• sigPowerOverboost(bts)

C.53. Tx power overboost for signaling channels• enableRepeatedFacchFr (bts)

C.54. U-TDOA support on the BSS• uplinkPwrCtrlDuringUTDOA (bsc)

C.55. Enhanced Measurement Report (EMR) support• servingBandReporting (bts)

• ServingBandReportingOffset (handOverControl)

C.56. GSM to UMTS handover• cId (adjacentCellUTRAN)

• compressedModeUTRAN (bts)

• diversityUTRAN (adjacentCellUTRAN)

• earlyClassmarkSendingUTRAN (bts)

• fDDARFCN (adjacentCellUTRAN)

• fDDMultiratReporting (bts)

• fDDReportingThreshold (handOverControl)

• fDDReportingThreshold2 (handOverControl)

• gsmToUMTSServiceHo (bsc)

• hoMarginAMRUTRAN (adjacentCellUTRAN)

• hoMarginDistUTRAN (adjacentCellUTRAN)

• hoMarginRxLevUTRAN (adjacentCellUTRAN)

411-9001-124 18.08 1.0 Page 439 of 446


• hoMarginRxQualUTRAN (adjacentCellUTRAN)

• hoMarginTrafficOffsetUTRAN (adjacentCellUTRAN)

• hoMarginUTRAN (adjacentCellUTRAN)

• hoPingpongCombinationUTRAN (adjacentCellUTRAN)

• hoPingpongTimeRejectionUTRAN (adjacentCellUTRAN)

• hoRejectionTimeOverloadUTRAN (bsc)

• locationAreaCodeUTRAN (adjacentCellUTRAN)

• mobileCountryCodeUTRAN (adjacentCellUTRAN)

• mobileNetworkCodeUTRAN (adjacentCellUTRAN)

• offsetPriorityUTRAN (adjacentCellUTRAN)

• qsearchC (handOverControl)

• rNCId (adjacentCellUTRAN)

• rxLevDLPbgtUTRAN (adjacentCellUTRAN)

• rxLevMinCellUTRAN (adjacentCellUTRAN)

• scramblingCode (adjacentCellUTRAN)

• t3121 (bts)

C.57. Novel Adaptive Receiver• adaptiveReceiver (transceiver)

C.58. Signaling Link GET Dynamic Data enhancements• slkATerResource (signallingLink)

• slkAssociatedTmuPortPosition (signallingLink)

• signallingLinkResourcesStates (signallingLinkSet)

• signallingLink field (signallingLinkSet)

• slkATerResource field (signallingLinkSet)

• slkAssociatedTmuPortPosition field (signallingLinkSet)

• slkAResource field (signallingLinkSet)

• signallingLinkResState field (signallingLinkSet)

C.59. Smart Power Management

Page 440 of 446 411-9001-124 18.08 1.0


• smartPowerManagementConfig (powerControl)

• smartPowerSwitchOffTimer (powerControl)

C.60. Software Preparation for BSC 3000 Optical Carriers Introduction• synchronizingHsaRc (bsc)

C.61. AMR-HR on pre-empted PDTCH• gprsPreemptionForHR (bsc)

C.62. Dynamic Abis interface readiness in V17• dynamicAbis (btsSiteManager)

C.63. BSS paging coordination• bssPagingCoordination (bts)

C.64. Permanent AAL-1 self-testing• standbyStatus (TMU)

C.65. AMR feature lock at OMC-R• Licenses used by this object (Display RM Capacity - md)

• Licenses needed to put object in service (Display RM Capacity - md)

• Number of XTP under this BSS (Display 4K Erlangs - md)

• This BSS is using license (Display 4K Erlangs - md; Display 4K Erlangs - bsc)

• Total licenses for this OMC-R (Display RM Capacity - md; Display 4K Erlangs - md; Display RM Capacity - bsc; Display 4K Erlangs - bsc; Display RM Capacity - btsSiteManager)

• Total unused licenses (Display RM Capacity - md; Display 4K Erlangs - md; Display RM Capacity - bsc; Display 4K Erlangs - bsc; Display RM Capacity - btsSiteManager)

C.66. EDGE feature lock at OMC-RSee C.65. “AMR feature lock at OMC-R” on page 440

C.67. Abis over IP• administrativeState (igm)

• administrativeState (ipgRc)

• administrativeState (ipm)

• availabilityStatus (igm)

• availabilityStatus (ipgRc)

• availabilityStatus (ipm)

• btsType (btsSiteManager)

411-9001-124 18.08 1.0 Page 441 of 446


• IP@ of IBOS connected to IPM (ipm)

• ipAggregateEthernetPortUsed (ipgRc)

• ipCompressionActivation (btsSiteManager)

• ipCompressionDepth (btsSiteManager)

• ipCRPnChannel_TosDscp (ipgRc)

• ipCRPnChannel_userPriority (ipgRc)

• ipDefaultGateway (ipgRc)

• ipDHCPServerList (ipgRc)

• ipgPcmList (ipgRc)

• ipgRc Reference (igm)

• ipIpgRcCounterPeriod (ipgRc)

• ipAggregateEthernetPortMonitored (ipgRc)

• ipIBOSTraffic_TosDscp (ipgRc)

• ipIBOSTraffic_userPriority (ipgRc)

• ipm MAC address Core A (ipm)

• ipm MAC address Core B (ipm)

• ipPortIPAddress_VRId_List (ipgRc)

• ipRoutingProtocolOnAbisPort (ipgRc)

• ipRoutingProtocolOnAggregatePort (ipgRc)

• ipRoutingProtocolOnIBOSPort (ipgRc)

• ipRoutingTable (ipgRc)

• ipPdvManualSet (btsSiteManager)

• ipPdvSelfTuningRange (btsSiteManager)

• ipRTPnChannel_TosDscp (ipgRc)

• ipRTPnChannel_userPriority (ipgRc)

• ipServiceChannel_TosDscp (ipgRc)

• ipServiceChannel_userPriority (ipgRc)

Page 442 of 446 411-9001-124 18.08 1.0


• ipSynchroUplinkActivation (btsSiteManager)

• ipTrafficPacketPeriod (btsSiteManager)

• operationalState (igm)

• operationalState (ipgRc)

• operationalState (ipm)

• positionInShelf (igm)

• positionInShelf (ipgRc)

• related bts site manager list (ipm)

• shelfNumber (igm)

• shelfNumber (ipgRc)

• standbyStatus (igm)

• sWVersionActive (ipm)

• sWVersionPassive (ipm)

• upgradeStatus (igm)

• upgradeStatus (ipm)

C.68. AMR maximization• fullHRCellLoadEnd (bts)

• fullHRCellLoadStart (bts)

• shared PDTCHratio (bts)

C.69. Enhanced very early assignment• EATrafficLoadEnd (bts)

• EATrafficLoadStart (bts)

• VEASDCCHOverflowAllowed (bts)

C.70. FACCH repetition for TCH/HR• enableRepeatedFacchHr(bts)

C.71. Fast Ack/Nack reporting• evolvedEdgeLatRedActivation (bts)

C.72. Flexible OMC-R• MIB version (executableSoftware)

411-9001-124 18.08 1.0 Page 443 of 446


C.73. GPRS/EDGE services on extended cell• taDetectionDataExtCell(bts)

C.74. Multi-zone cell enhancement• concentAlgoExtRxLevUL (handOverControl)

• concentAlgoIntRxLevUL (handOverControl)

• directAllocIntFrRxLevDL (handOverControl)

• directAllocIntFrRxLevUL (handOverControl)

C.75. TFO support• tfoActivation (bsc)

C.76. TRM3 capacity increase• trmIncreaseCapacity (transcoder)

C.77. AMR-WB support• amrWbDlAdaptationSet (bts)

• amrWbNbMaxPdtchPreemption (bts)

• amrWbSacchPowerOffsetSelection (bts)

• amrWbUlAdaptationSet (bts)

• amrWBIntercellCodecMThresh (handOverControl)

• amrWBIntracellCodecMThresh (handOverControl)

• amrWBiRxLevDLH (handOverControl)

• amrWBiRxLevULH (handOverControl)

• amrWBPowerControlCIThresholdUl (powerControl)

• enableRepeatedFacchWBFr (bts)

• nAMRWBRequestedCodec (handOverControl)

C.78. Multiple ARFCN• 3GAccessMinLevelOffset (bts)

• 3GReselectionThreshold (bts)

C.79. Additional comment field in site and sector parameters list• Comment (btsSiteManager)

• Comment (bts)

Page 444 of 446 411-9001-124 18.08 1.0


D. PCUSN components

The PCUSN components are described in the following NTPs:

• Kapsch Multiservice switch 7400, 15000, 20000 Component - PcGtl (NN10600-060_PcGtl)

• Kapsch Multiservice switch 7400, 15000, 20000 Component - Psusa (NN10600-060_Pcusa)

• Kapsch Multiservice switch 7400, 15000, 20000 Component - Psusn (NN10600-060_Pcusn)

For more information on the PCUSN components, refer to:

• Kapsch Multiservice switch 7400, 15000, 20000 Component Overview (NN10600-060)



Kapsch CarrierCom France SAS446


Documents

Bss18 Parm Dic