9001 124 PDF

Kapsch CarrierCom France SAS
411-9001-124
GSM BSS Parameter Reference

User Documentation
411-9001-124 Version 18.16 December 23, 2013 1.0

Global System for Mobile Communications (GSM)

Release: V18 P&C5
Document number: 411-9001-124
Document release date: December 23, 2013
Copyright © 2010-2013 Kapsch CarrierCom France S.A.S. 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.16 1.0 Page 3 of 524
Publication History
Following changes are incorporated in NTP: 411-9001-124 on the specified dates.
December 23, 2013

Version 18.16
Following feature is modified for P&C5 release:
• Trans-European Transport Network Executive Agency (TEN-T EA) features:
– “50034 - NACC inter BSC/inter PCUSN with RIM” on page 12
– “22915 - Extended Uplink TBF” on page 12
• “50037, 50042 - Linux x86 platform installation and Converged OAM” on page 13
March 18, 2013

Version 18.14
Following are the new features introduced for P&C5 release:
• “33296 - A Flex - GSM Access” on page 7
• “33296 - Quasi Associated Mode (QAM) - GSM Access” on page 8
– “50032 - PFC restriction removal” on page 9
– “50031 - EDGE Family C MCS-1 & 4 implementation” on page 10
– “50033 - NACC inter BSC/intra PCUSN feature” on page 11
• “50035 - OMC-R installation on any SPARC platform” on page 13
• “50025 - Distinguish TX versus Rx fault at IOM” on page 13
May 21, 2012

Version 18.13
PRM12/0000561 Deleted X.25 related information under section “BSC/TCU 3000” on

page 504
411-9001-124 18.16 1.0 Page 4 of 524
Publication History
Following changes are incorporated in NTP: 411-9001-124 on the specified dates.
May 09, 2012

Version 18.12
PRM12/0000479 Included the following missing parameters under appropriate alpha-

betical listing:
bscHopReconfUse Class 1, bscMSAccessClassBarringFunction Class 3, bts, concen-

tAlgoIntMsRange Class 3, concentAlgoIntRxLev Class 3, concentAlgoIntRxLevUL
Class 3, date, distributionTime Class 3, encrypAlgoCiphModComp Class 1, initialMCS-
DL Class 3, initialMCSUL Class 3, interBscDirectedRetry Class 3, interBscDirectedRe-
tryFromCell Class 3, interCellHOExtPriority Class 3, interCellHOIntPriority Class 3,
interferenceType Class 3, interferenceMatrixRunningOnBsc, interferenceMatrixRun-
ningOnBts, interferer cancel algo usage Class 2, interOmuEtherlinkOper, intraBscDi-
rectedRetry Class 3, intraBscDirectedRetryFromCell Class 3, intraCell Class 3,
intraCellHOIntPriority Class 3, intraCellQueueing Class 3, intraCellSDCCH Class 3,
iom, IP@ of IBOS connected to IPM, IPM IP@, IPM IP subnet mask, ipAggregateEther-
netPortUsed Class 3, ipAggregateTraffic_TosDscp Class 3,
ipAggregateTraffic_userPriority Class 3, ipIBOSEthernetPortUsed Class 3,
ipOtherAbisTraffic_TosDscp Class 3, ipOtherAbisTraffic_userPriority Class 3, ipRout-
ingProtocolOnAbisPort Class 3, upAckTime Class 3 (packetAckTime), selfAdaptActiva-
tion Class 3, unmasked users alarms Class 2, physicalFiberInfo.
February 14, 2012

Version 18.11
PRM12/0000204 Updated "new password 1st try" on Page 287.
November 30, 2011

Version 18.10
P&C4 delivery.
411-9001-124 18.16 1.0 Page 5 of 524
Contents
New in this release ............................................................................................................. 7
Introduction....................................................................................................................... 18
1. Overview ............................................................................................................................. 19
1.1. Network configuration objects and their parameters............................................................... 19
1.2. Different types of configuration parameters ............................................................................ 22
1.3. Description of dictionary entries.............................................................................................. 23
1.3.1. Header line ................................................................................................................... 23

1.3.2. Main body of entries ..................................................................................................... 24
2. Parameters listed in alphabetical order........................................................................... 26
2.1. 3 .............................................................................................................................................. 26
2.2. A ............................................................................................................................................. 31
2.3. B ............................................................................................................................................. 76
2.4. C ........................................................................................................................................... 117
2.5. D ........................................................................................................................................... 156
2.6. E ........................................................................................................................................... 176
2.7. F............................................................................................................................................ 196
2.8. G ........................................................................................................................................... 208
2.9. H ........................................................................................................................................... 217
2.10. I ........................................................................................................................................... 231
2.11. J .......................................................................................................................................... 265
2.12. L .......................................................................................................................................... 266
2.13. M ......................................................................................................................................... 278
2.14. N ........................................................................................................................................ 313
2.15. O ......................................................................................................................................... 331
2.16. P ........................................................................................................................................ 353
2.17. Q ........................................................................................................................................ 382
2.18. R ........................................................................................................................................ 383
2.19. S ........................................................................................................................................ 403
2.20. T.......................................................................................................................................... 437
2.21. U ......................................................................................................................................... 464

Page 6 of 524 411-9001-124 18.16 1.0
2.22. V ......................................................................................................................................... 476
2.23. W ........................................................................................................................................ 477
2.24. X ......................................................................................................................................... 478
2.25. Z.......................................................................................................................................... 480
A. Objects and parameters evolution ................................................................................ 483
B. Parameters per feature ................................................................................................... 499
C. PCUSN components ....................................................................................................... 522

411-9001-124 18.16 1.0 Page 7 of 524
New in this release

The following sections detail what are new in the GSM BSS Parameter Reference (411-
9001-124) for release V18.0 P&C5.
P&C5 Features
See the following sections for information about feature changes:
• “33296 - A Flex - GSM Access” on page 7
• “33296 - Quasi Associated Mode (QAM) - GSM Access” on page 8
– “50032 - PFC restriction removal” on page 9
– “50031 - EDGE Family C MCS-1 & 4 implementation” on page 10
– “50033 - NACC inter BSC/intra PCUSN feature” on page 11
– “22915 - Extended Uplink TBF” on page 12
• “50035 - OMC-R installation on any SPARC platform” on page 13
• “50025 - Distinguish TX versus Rx fault at IOM” on page 13
• “50037, 50042 - Linux x86 platform installation and Converged OAM” on page 13
33296 - A Flex - GSM Access

A-Flex allows a BSC to connect to multiple MSCs through pool area. In Radio Access
Network (RAN), a pool area includes all LA(s) of one or more MSCs that are served by
the same group of Core Network (CN) nodes in parallel. So a Mobile Station (MS) can
move between MSCs in the pool area and it is served by the same MSC as long as it is
in radio coverage of the pool area. Following sections are impacted by this feature.
• Modified the following parameters with Object: (if A Flex or QAM activated) row and
included a NOTE.
– “bssSccpConnEst Class 1” on page 102
– “bssSccpRelease Class 1” on page 103
– “bssSccpInactTx Class 1” on page 103
– “bssSccpInactRx Class 1” on page 103
– “bssSccpSubSysTest Class 1” on page 104

Page 8 of 524 411-9001-124 18.16 1.0
– “cSS7LocalSubSystemNumber Class 0” on page 152
– “cSS7RemoteSubSystemNumber Class 0” on page 152
– “pointCode Class 1” on page 373
• Added parameter “networkResourceIdentifierLength” on page 319
• Added parameter “nullNRI” on page 325
• Added parameter “remoteNodeType” on page 391
• Added parameter “networkResourceIdentifierList” on page 320
• Added parameter “signallingLinkSetInstances List” on page 414
• Added parameter “status” on page 431
• Added parameter “adjacentPointCode” on page 41
• Added parameter “remoteSignallingPointInstance” on page 391
• Added subsection “V 18.0 P&C5 parameters” on page 483 within the section “Objects
and parameters evolution” on page 483.
• Added subsection “A Flex - GSM Access” on page 499 within the section “Parame-
ters per feature” on page 499.
33296 - Quasi Associated Mode (QAM) - GSM Access

In the Quasi Associated Mode, a BSC addresses one MSC through one or several Me-
dia Gateways (MGW), which act as a STP (Signalling Transfer Point). In combined
mode, Quasi Associated Mode and A Flex - GSM Access features enable a BSC to con-
nect to one or more MSC through one or more MGWs, and pool areas.
For more information about A Flex - GSM Access feature, refer section “33296 - A Flex
- GSM Access” on page 7.
• Following is the list of new parameters included for Quasi Associated Mode.
– networkResourceIdentifierLength. For more information about this parameter,

refer “networkResourceIdentifierLength” on page 319.
– nullNRI. For more information about this parameter, refer “nullNRI” on page 325.
– remoteNodeType. For more information about this parameter, refer “remoteNo-

deType” on page 391.
– networkResourceIdentifierList. For more information about this parameter “net-

workResourceIdentifierList” on page 320.
411-9001-124 18.16 1.0 Page 9 of 524
– signallingLinkSetInstanceList. For more information about this parameter, refer

“signallingLinkSetInstances List” on page 414.
– status. For more information about this parameter, refer “status” on page 431.
– adjacentPointCode. For more information about this parameter, refer “adjacent-

PointCode” on page 41.
– remoteSignallingPointInstance. For more information, refer “remoteSignalling-

PointInstance” on page 391.
• Modified the following parameters with Object: (if A Flex or QAM activated) row and
included a NOTE.
– “bssSccpConnEst Class 1” on page 102
– “bssSccpRelease Class 1” on page 103
– “bssSccpInactTx Class 1” on page 103
– “bssSccpInactRx Class 1” on page 103
– “bssSccpSubSysTest Class 1” on page 104
– “cSS7LocalSubSystemNumber Class 0” on page 152
– “cSS7RemoteSubSystemNumber Class 0” on page 152
– “pointCode Class 1” on page 373
• Following sections are impacted by this feature:
– Added subsection “V 18.0 P&C5 parameters” on page 483 within the section
“Objects and parameters evolution” on page 483.
– Added subsection “Quasi Associated Mode (QAM) - GSM Access” on page 501
within the section “Parameters per feature” on page 499.
50032 - PFC restriction removal
ATTENTION:
This feature is applicable only to PCUSN equipped with PcuspE2 sub-system.
In P&C5 release with the implementation of PFC restriction removal feature, the following
restrictions which existed in previous releases are removed to avail full benefits of Packet
Flow Context (PFC) feature.
• A GPRS mobile or EDGE mobile was Real Time (RT) accepted only on GPRS TDMA
or EDGE TDMA, respectively.
Page 10 of 524 411-9001-124 18.16 1.0
• Also, GPRS mobiles on EDGE TDMA or EDGE mobiles on GPRS TDMA were allowed
only in Non Real Time (NRT) mode.
With the implementation of this feature, fixed values as given below are allotted for
GPRS MS or EDGE MS, which are allocated a GPRS TBF. Included a NOTE about the
fixed values allotted for GPRS MS and EDGE MS, which are allocated a GPRS TBF in
the following parameters:
– “pfcTsGuaranteedBitRateDl Class 3” on page 371
– “pfcTsGuaranteedBitRateUl Class 3” on page 371
50031 - EDGE Family C MCS-1 & 4 implementation

EDGE Family C MCS-1 and MCS-4 implementation feature implements Family C EG-
PRS Coding schemes: MCS-1 and MCS-4.
3GPP Specifications define 9 coding schemes for EGPRS coding, which are grouped
into 3 families A, B & C.
• Family A: MCS-3, MCS-6, MCS-8, MCS-9
• Family B: MCS-2, MCS-5, MCS-7
• Family C: MCS-1, MCS-4
ATTENTION:
The support for EDGE family C is introduced with this feature in P&C5.
Following are the list of new parameters included for this feature:
– dlMCS1UpperThreshold. For more information about this parameter, refer

“dlMCS1UpperThreshold Class 3” on page 171.
– dlMCS4UpperThreshold. For more information about this parameter, refer

“dlMCS4UpperThreshold Class 3” on page 172
– ulMCS1UpperThreshold. For more information about this parameter, refer

“ulMCS1UpperThreshold Class 3” on page 465
– ulMCS4UpperThreshold. For more information about this parameter, refer

“ulMCS4UpperThreshold Class 3” on page 466
– dlGMSKMCS1UpperThreshold. For more information about this parameter, re-

fer “dlGMSKMCS1UpperThreshold Class 3” on page 170
– dlGMSKMCS4UpperThreshold. For more information about this parameter, re-

fer “dlMCS4UpperThreshold Class 3” on page 172
– ulGMSKMCS1UpperThreshold. For more information about this parameter, re-

fer “ulGMSKMCS1UpperThreshold Class 3” on page 465
411-9001-124 18.16 1.0 Page 11 of 524
• Added subsection “EDGE Family C MCS-1 & 4 implementation” on page 502 within
the section “Parameters per feature” on page 499.
Following are the parameters enhanced in P&C5 release to accept MCS1 and MCS4 as
input:
– initialMCSUL. For more information about this parameter, refer “initialMCSUL

Class 3” on page 235.
– initialMCSDL. For more information about this parameter, refer “initialMCSDL

50033 - NACC inter BSC/intra PCUSN feature

Network Assisted Cell Change (NACC) inter BSC/intra PCUSN feature is enhancement
of the current NACC feature, which allows the NACC procedure between cells managed
by different BSC linked to the same PCUSN.
• Following is the list of new parameters included for this feature:
– naccInterBscIntraPcusnActivation. For more information about this parameter,

refer “naccInterBscIntraPcusnActivation Class 3” on page 313.
– routingArea. For more information about this parameter, refer “routingArea

– baseColourCode. For more information about this parameter, refer “baseCo-

lourCode Class 3” on page 77.
– networkColourCode. For more information about this parameter, refer “net-

workColourCode Class 3” on page 318
• Included a note in the following parameters as the adjacentCellReseletion object is

enhanced in V18 P&C5 release:
– mobileCountryCode. For more information about this parameter, refer “mobile-

CountryCode Class 3” on page 304.
– mobileNetworkCode. For more information about this parameter, refer “mobile-

NetworkCode Class 3” on page 306.
– locationAreaCode. For more information about this parameter, refer “location-

AreaCode Class 3” on page 271.
– cellIdentity. For more information about this parameter, refer “cellIdentity Class
3” on page 124.
Page 12 of 524 411-9001-124 18.16 1.0
• Added subsection “NACC Inter BSC/Intra PCUSN” on page 502 within the section
“Parameters per feature” on page 499.
50034 - NACC inter BSC/inter PCUSN with RIM

Network Assisted Cell Change (NACC) Inter BSC/Inter PCUSN feature enables an Mo-
bile Station (MS) to avail System Information (SI) 1/3/13 of a target cell, even if the target
cell is managed by a different BSC linked to a different PCUSN through RAN Information
Management (RIM) procedure.
RAN Information Management (RIM) procedure
The NACC inter BSC between two PCUSNs is achieved through the implementation of
RAN Information Management (RIM) procedure, which allows the SI1/3/13 transfer be-
tween PCUSNs through Packet Core (SGSN). All the RIM protocol messages are trans-
ferred between the PCU and the SGSN using the signaling BVC.
The existing NACC features are enhanced to allow the NACC procedure between cells
managed by different BSCs linked to another PCUSN. NACC Inter BSC/Inter PCUSN
feature is an enhancement of the following features:
• NACC for release 4 MS.
• NACC Inter BSC/Intra PCUSN feature. For more information about this feature, refer
“50033 - NACC inter BSC/intra PCUSN feature” on page 11
For more information about this feature and feature activation, refer GSM BSS Funda-
mentals-Operating-Principles (411-9001-007).
Following sections are impacted by this feature:
• Added a new parameter, “globalInterBscNaccActivation” on page 209.
• Added the new parameter, gloabalInterBscNaccActivation in “V 18.0 P&C5 parame-

ters” on page 483 within the section “Objects and parameters evolution” on
page 483.
• Added subsection “NACC Inter BSC/Inter PCUSN with RIM” on page 502 within the
section “Parameters per feature” on page 499.
22915 - Extended Uplink TBF

Extended UL TBF feature enables the system to keep the uplink resources to the mobile
station during temporary inactive periods where the mobile station has no RLC data
blocks to send. The maximum of The Extented UL TBF period (tNwExtUtbft) is 5 sec.
An extended Uplink TBF allows the mobile station to use the same uplink TBF for sub-
sequent data transfer. It does not require re-establishment for another UL TBF hence
saving the TBF establishment time, and as a result increasing the throughput. The TBF
will be released at a point determined by the PCU.
411-9001-124 18.16 1.0 Page 13 of 524
In the specific context of “ETCS2 over GPRS”, the feature Extended UL TBF has been
identified as essential to fulfill the requested performances, in terms of “time to deliver”.
Extended UL TBF is used to maintain the TBF alive and the inactivity timer must be set
to a value bigger than the maximum duration between 2 ETCS2 uplink messages. This
duration can be bigger than the recommended 3GPP maximum value, i.e 5 seconds.
For more information about this feature, refer GSM BSS Fundamentals— Operating
Principles (411-9001-007).
The enhancement is to extend this period (tNwExtUtbft) up to 20s.
• Modified the parameter “tNwExtUtbf Class 3” on page 451.
50035 - OMC-R installation on any SPARC platform

In combined OMC-R server configuration (Oracle T3-2 server), the OMC-R application and
all third party softwares can be installed in a virtual machine on any SPARC platform, which
supports virtualization. Installing the OMC-R application in a virtual machine makes the ap-
plication to be independent of server’s hardware type and also allows to use the virtual ma-
chines as a platform for OMC-R.
ATTENTION:
The new installation procedure of OMC-R application is applicable only to Combined
OMC-R server configuration (virtual environment).
For more information about Combined OMC-R server configuration, refer GSM OMC-R
Fundamentals (411-9001-006).
This document is not impacted by this feature.
50025 - Distinguish TX versus Rx fault at IOM

From P&C5 in simplex optical fiber connection to IOM, it is possible to identify the faulty
optical fiber cable (Tx/Rx). For more information about identifying the faulty optical fiber ca-
ble, refer Fault number: 2047 for BSC 3000 and TCU 3000 in GSM BSC 3000/TCU 3000
Fault Clearing (411-9001-131).
This document is not impacted by this feature.
50037, 50042 - Linux x86 platform installation and Converged OAM

With the implementation of 50037 'x86 platform installation' and 50042 'Converged
OAM' features, it is possible to run OMC-R application in a virtual environment on an x86
64-bit architecture, independently of server type.
Running the OMC-R application in a virtual environment makes the application indepen-
dent of the underlying hardware and to co-allocate different OAM applications (Carri-
erNMS, RPM, CBM, and DS) on the same server.
ATTENTION: The new installation procedures of OMC-R application are applicable

only to Converged OAM virtual environment. For more information about the instal-
lation procedure of OMC-R in Converged OAM Virtual Environments, refer GSM
OMC-R Fundamentals (411-9001-006).
• Added a new parameter, “ftpUserPassword” on page 206.

Page 14 of 524 411-9001-124 18.16 1.0
• Added a new parameter “ftpUserPassword” in A.1. “V 18.0 P&C5 parameters” on

page 483
411-9001-124 18.16 1.0 Page 15 of 524
P&C4 Features
See the following sections for information about feature changes:
• “BTS 9000 Outdoor system introduction” on page 15
• “High Speed Uplink Distortion Removal on Packet Data” on page 15
• “BTS Secured Loop on BSCe3” on page 15
• “BTS 9000 for Outdoor Battery Remote Monitoring” on page 15
• “2G- 4G Cell reselection” on page 16
BTS 9000 Outdoor system introduction

The BTS9000 outdoor is a new BTS in the BTS18000 family, and it is dedicated to rail-
ways customers in the R-GSM frequency band.
• Updated parameter “additional unmasked users alarms Class 2” on page 38
• “unmasked users alarms” on page 470
BTS 9000 for Outdoor Battery Remote Monitoring

Battery Remote Monitoring is introduced on BTS 9000 Outdoor BTS. BTS9000 OUT-
DOOR can operate on emergency batteries in case of main power supply failure.
Updated parameter “batteryRemoteControllerPresence” on page 78
High Speed Uplink Distortion Removal on Packet Data

The High Speed Uplink Distortion Removal (HSUDR) on packet data is a signal process-
ing feature beneficial for GSM-R users who need to convey critical packet data from
trains going at very high speeds. This allows better and faster radio transmissions.
• Added parameter “highSpeedUplinkDistortionRemovalOnPacketData” on page 220
• Added A.2. “V18.0 Pick and choose 4 parameters” on page 484
• Added B.85. “High Speed Uplink Distortion Removal on Packet Data” on page 519
BTS Secured Loop on BSCe3

This feature ensures that the communication and signaling links are maintained and au-
tomatically switched over the redundant path during network transmission failure in BTS
loop.
• Added parameter “securedLoopActivation” on page 406
• Updated parameter “bscSitePcmList” on page 97
• Updated parameter “configRef” on page 147
• Updated parameter “radioSiteMask” on page 385

Page 16 of 524 411-9001-124 18.16 1.0
• Added A.2. “V18.0 Pick and choose 4 parameters” on page 484
• Added B.86. “BTS Secured Loop on BSCe3” on page 520
2G- 4G Cell reselection

The 2G-4G reselection feature consists of the cell reselection based on priority from
GSM to LTE and GSM to UTRAN for idle and Packet data mode. GSM to LTE cell rese-
lection feature allows multimode mobiles supporting GSM and LTE radio access tech-
nology to reselect to LTE coverage in idle and packet transfer mode.
The GSM to UTRAN reselection based on priority feature allows mobile, supporting pri-
ority based inter-RAT cell reselection, to select a suitable cell from another radio access
technology. This reselection is done according to algorithm for inter-RAT cell reselection
based on priority information, provided by the network in System Information 2quater
message.
See the following sections for the changes related to this feature:
• “3GPriority” on page 27
• “3GReselection ARFCN” on page 27
• “3GReselectionOnPriority” on page 28
• “3GQRxLevMin” on page 26
• “gsmPriority” on page 214
• “gsmToLteReselection” on page 214
• “default3Gpriority” on page 162
• “default3GQRxLevMin” on page 162
• “defaultThreshold3G” on page 163
• “Default not allowed LTE cells” on page 162
• “Default Not Allowed PCIDs” on page 163
• “Default PCID Bitmap Group” on page 163
• “hysteresisPrio” on page 231
• “lteARFCN” on page 264
• “lteRxLevMin” on page 277
• “ItePriority” on page 278

411-9001-124 18.16 1.0 Page 17 of 524
• “measurementBandwidth” on page 290
• “not allowed cells” on page 324
• “not Allowed PCIDs” on page 324
• “PCID Bitmap Group” on page 358
• “PCID to TA mapping” on page 359
• “threshold3Ghigh” on page 445
• “threshold3Glow” on page 447
• “thresholdPrioritySearch” on page 448
• “timerReselection” on page 449
• “thresholdLteHigh” on page 447
• “thresholdLteLow” on page 447
• Updated Figure 6., “btsSiteManager subtree objects,” on page 21

Page 18 of 524 411-9001-124 18.16 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.
ATTENTION
For a BSC 3000, there are no more class 1 parameters; all these parameters are
now class 0.
Prerequisites
Users must be familiar with networking principles.
They must also be familiar with the following manuals:
GSM BSS Documentation roadmap (411-9001-000)
Navigation
• “Introduction” on page 18 contains general information on BSS operating parame-
ters.
• Chapter 2. “Parameters listed in alphabetical order” on page 26 describes all the op-
erating parameters listed in alphabetical order, and explains their use.
• A. “Objects and parameters evolution” on page 483 lists new configuration parame-
ters and objects by release.
• B. “Parameters per feature” on page 499 lists new configuration parameters and ob-
jects by release.
• B. “Parameters per feature” on page 499 presents BSS parameters per feature.
411-9001-124 18.16 1.0 Page 19 of 524
Chapter 1. Overview
1.1. Network configuration objects and their parameters

This dictionary summarizes all the GSM BSS parameters used to define all the objects
managed on the OMC-R. An object model is used to describe each managed network
element. Each object is defined in terms of its parameters (also called attributes), and
its relationships with other objects. A containment tree is used to depict the relationships
among these objects (see Figure 1., “Object main tree structure,” on page 19) to
Figure 4., “Network subtree objects,” on page 20). For more information on objects and
parameters, refer to GSM BSS Fundamentals — Operating Principles (411-9001-007),
for parameters listed per object, refer to GSM OMC-R Commands Reference - Objects
and Fault menus (411-9001-128).
ATTENTION
For a BSC 3000, there are no more class 1 parameters; all these parameters are
now class 0.
FIGURE 1. Object main tree structure
FIGURE 2. omc subtree objects

Page 20 of 524 411-9001-124 18.16 1.0
FIGURE 3. md subtree objects
FIGURE 4. Network subtree objects

411-9001-124 18.16 1.0 Page 21 of 524
FIGURE 5. bsc 3000 subtree objects
FIGURE 6. btsSiteManager subtree objects
Users can create, modify, and delete objects using commands and actions displayed in
the menus of the OMC-R Browser window (see Figure 7., “Menus in the OMC-R brows-
er window,” on page 22). Parameters are widely used in all commands and actions.
For more information on commands, refer to GSM OMC-R Commands Reference - Ob-
jects and Fault menus (411-9001-128) to GSM OMC-R Commands Reference - Secu-
rity, Administration, SMS-CB, and Help menus (411-9001-130).
Page 22 of 524 411-9001-124 18.16 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 parameters

There are two types of configuration parameters: customer and manufacturer parame-
ters.
411-9001-124 18.16 1.0 Page 23 of 524
• 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 which
must be under the control of the manufacturer (for example: runPwrControl)
– product parameters, which are incompatible with the current system release (for
example: sWVersionbackup)
New configuration parameters are summarized in A. “Objects and parameters evolution”

on page 483.
1.3. Description of dictionary entries

Each 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 line

The 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 24 of 524 411-9001-124 18.16 1.0
FIGURE 8. Header line
1.3.2. Main body of entries

The 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:
is handled by the
Configuration is handled by any
Management other applications
type meaning application (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)
1. Dynamic parameters (DD) are not stored in databases. They are managed by the
BSC 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
411-9001-124 18.16 1.0 Page 25 of 524
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 be

used.
– 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 Feature
that 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 26 of 524 411-9001-124 18.16 1.0
Chapter 2. Parameters listed in alphabetical order
For a BSC 3000, there are no more class 1 parameters; all these parameters are now
class 0.
2.1. 3
3GAccessMinLevel
Description: Sub-parameter of the “gsmTo3GReselection” on page 215
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: dB
Type: DP
Default value: -12
Release: V18.0.0
3GAccessMinLevelOffset
parameter: gives the minimum threshold offset for Ec/No for the
UTRAN FDD cell reselection (FDD only).
Object: bts
Value range: [0]
Unit: dB
Type: DP
Default value: 0
Release: V18.0.0 P&C1
3GQRxLevMin
Description: Minimum RX level required for cells on the target UTRAN frequency
(dBm). It is as sub-parameter of “gsmTo3GReselection” on
page 215.
Object: bts
Unit: dBm
Value range: (non significant, -119 , -117 , -115 , …, -59 , -57 )
Type: DP
Default value: non significant
411-9001-124 18.16 1.0 Page 27 of 524
Class: 3
Release: V18.0 P&C4
3GPriority
Description: Priority of a UTRAN frequency layer. It is as sub-parameter of
“gsmTo3GReselection” on page 215.
Object: bts
Value range: (non significant , 0, 1, 2, 3, 4, 5, 6, 7)
Type: DP
Checks: The value for Default3Gpriority parameter and each 3Gpriority value
from 3GReselection ARFCN parameter must be different from
ltePriority parameter value for each lteAdjacentCellReselection in bts
object.
Default value: non significant
Class: 3
Release: V18.0 P&C4
3GReselection ARFCN
parameter: lists the ARFCN in the reselection mode for:
• FDD: neighboring UMTS cell ARFCN
• TDD: neighboring TD-SDCMA cell ARFCN
From P&C4 this is a structure composed of the following parameters:
– ARFCN
– 3Gpriority
– threshold3Ghigh
– threshold3Glow
– 3GQRxLevMin
Object: bts
Value range: From V18.0.0 P&C3, maximum of 8 values are available for BSC
Previous releases, maximum of 4 values are available for BSC
Type: DP
Default value: Empty
Page 28 of 524 411-9001-124 18.16 1.0
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.
From V18.0 P&C4 , this is modified to a structure composed of
“3GPriority” on page 27, “3GQRxLevMin” on page 26,
“threshold3Ghigh” on page 445, “threshold3Glow” on page 447.
[1-16383] for ARFCN.
Note: all sub-parametres are displayed on MMI for all BSC versions.
Only default values must be available for BSC versions older than P&C4
release.
3GReselectionOffset
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: dB
Type: DP
Default value: -infinity
Release V18.0.0
3GReselectionOnPriority
Description: Used to activate or deactivate the GSM to UTRAN reselection based on
priority.
Object: bts
Value range: disabled (0)/enabled (1)]
Class: 3
Type: DP
Checks: The ARFCN parameter from 3GReselection ARFCN structure should
not be present if the gsmToLteReselection is enabled and
3GReselectionOnPriority is disabled.
If the 3GReselectionOnPriority parameter is set to enabled and if at
least one ARFCN parameter from 3GReselection ARFCN structure has
its associated parameters (3Gpriority, threshold3Glow, threshold3Ghigh
and 3GQRxLevMin) set to "non significant", the 3 parameters
"default3Gpriority", "defaultThreshold3G" and "default3GQRxLevMin"
must be different from "non significant".
411-9001-124 18.16 1.0 Page 29 of 524
Default value: Disabled

Checks: • Activation of GSM to UTRAN reselection based on priotiry requires
the corresponding RTU. For more information, see GSM BSS Funda-
mentals Operating Principles (411-9001-007).
• If the 3GReselectionOnPriority parameter is set to enabled and if at

least one ARFCN parameter from 3GReselection ARFCN structure
has its associated parameters (3Gpriority, threshold3Glow,
threshold3Ghigh and 3GQRxLevMin) set to "non significant", the 3 pa-
rameters "default3Gpriority", "defaultThreshold3G" and
"default3GQRxLevMin" must be different from "non significant".
• 3GReselectionOnPriority being active is forbidden when no 3G neigh-

bor cells are defined.
– Set 3GReselectionOnPriority=enabled is forbidden if

3GReselection ARFCN list is
– Set 3GReselection ARFCN=empty is forbidden if

3GReselectionOnPriority=enabled
– Create bts with 3GReselectionOnPriority=enabled and

3GReselection ARFCN=empty is forbidden
Release: V18.0 P&C4
3GReselectionThreshold
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
Note: For bsc V16.0 and v17.0, only value -102 is available.
3GSearchLevel
parameter: search for 3G cells (FDD or TDD) if the signal level is below
-98 dBm or above -54 dBm.
Object: bts
Page 30 of 524 411-9001-124 18.16 1.0
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
3GTechnology
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 that
UARFCNs 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 10838
for UMTS 1900: 9662 to 9938, 412, 437, 462, 487, 512, 537, 562, 587,
612, 637, 662, 687
for UMTS 1800: 1162 to 1513
for 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, 1087
for UMTS 800: 4387 to 4413, 1037, 1062
for UMTS 2600: 2237 to 2563, 2587, 2612, 2637, 2662, 2687, 2712,
2737, 2762, 2787, 2812, 2837, 2862, 2887, 2912
for UMTS 900: 2937 to 3088
for UMTS 1700: 9237 to 9387
[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.
411-9001-124 18.16 1.0 Page 31 of 524
Release: V18.0
2.2. A
abisSpy Class 3
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
absoluteRFChannelNo Class 2
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
Type: To define if the TDMA does not hop
Page 32 of 524 411-9001-124 18.16 1.0
Checks: DP
Description: [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.’
access time end

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.
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.
411-9001-124 18.16 1.0 Page 33 of 524
accessClassCongestion Class 3
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
Release: V9
accessibilityState
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
acknowledged by
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
acknowledgment time
Description: To select messages acknowledged at that time.
Value range: Absolute time format entry forms are detailed in GSM OMC-R
Commands Reference - Security, Administration, SMS-CB, and Help
menus (411-9001-130).
Type: DP
Page 34 of 524 411-9001-124 18.16 1.0
activationObject
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 is unique in a given BSS.
Restrictions: [M]: This attribute cannot be modified.
activationObject
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 tracing function is unique in a given BSS.
Restrictions: [M]: This attribute cannot be modified.
adaptiveReceiver Class
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
Feature: disabled
Type: DP
Release: V17
Note: This parameter is only available for BSC 3000. It is visible
only in GPRS.
411-9001-124 18.16 1.0 Page 35 of 524
additional supervised PCM 0 Class 2

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 18000
S12000
S8000 BTS with BCF
S8000 BTS with CBCF
S8002 BTS with CBCF
S2000 H/L BTS
e-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
Feature: GSM-R V12
Type: DP
Release: V12

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 18000
S12000
S8000 BTS with BCF
S8000 BTS with CBCF
S8002 BTS with CBCF
S2000 H/L BTS
e-cell
Feature: GSM-R V12
Type: DP
Release: V12
Page 36 of 524 411-9001-124 18.16 1.0

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 18000
S12000
S8000 BTS with BCF
S8000 BTS with CBCF
S8002 BTS with CBCF
S2000 H/L BTS
e-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 2 belongs to the bscSitePCMList
parameter the values YES or NO are equivalent (recommendation: NO)
Feature: GSM-R V12
Type: DP
Release: V12

BTS 18000
S12000
S8000 BTS with BCF
S8000 BTS with CBCF
S8002 BTS with CBCF
S2000 H/L BTS
e-cell
Feature: GSM-R V12
Type: DP
Release: V12
411-9001-124 18.16 1.0 Page 37 of 524

BTS 18000
S12000
S8000 BTS with BCF
S8000 BTS with CBCF
S8002 BTS with CBCF
S2000 H/L BTS
e-cell
Feature: GSM-R V12
Type: DP
Release: V12

BTS 18000
S12000
S8000 BTS with BCF
S8000 BTS with CBCF
S8002 BTS with CBCF
S2000 H/L BTS
e-cell
Feature: GSM-R V12
Type: DP
Release: V12
Page 38 of 524 411-9001-124 18.16 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/9000 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 masked
Alarm 1 unmasked
Alarms 1 to 2 unmasked
Alarms 1 to 24 unmasked]
Feature: GSM-R V18
Type: DP
Release: V18
addresses
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.
411-9001-124 18.16 1.0 Page 39 of 524
Object: user message - Answer / New message

Type: DP
adjacent cell umbrella ref Class 3

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.
Release: V9
adjacentCellHandOver
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.
[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.
Release: V8
Page 40 of 524 411-9001-124 18.16 1.0
adjacentCellHandOverId
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.
Type: DP
Release: V14
adjacentCellReselection
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.
Release: V8
adjacentCellReselectionId
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.
Type: DP
Release: V14
411-9001-124 18.16 1.0 Page 41 of 524
adjacentPointCode
Description: This parameter indicates the point code used by the BSC to reach the
adjacent node to which the signallingLinkSet is created. It can be the
point code of a MGW (acting as a STP) or a MSC/SMLC acting as a
SP.
Class: 0
Value range: 0 to 16777215
Default Value: • Empty (MMI)
• 0xFFFFFFFF (MOD)
Object: SignallingLinkSet
Type: DP
Release: V18 P&C5
Feature: A Flex - GSM Access or Quasi Associated Mode
Note: • This parameter is available only for BSC 3000. Also, this parameter
will be available for configuration only if A Flex - GSM Access or Qua-
si Associated Mode feature is activated.
• Existing pointCode (MMI) parameter and new adjacentPointCode

(MMI) parameter are mapped to the same MOD adjacentSignallingIn-
fo attribute under the signallingLinkSet object. Provisioning the values
among these two parameters is taken care through the NRP plug-in.
administrativeState
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
administrativeState
Description: ISO state
Value range: [locked (inactive) / unlocked (active)]
Object: atmRm
Type: BSC/TCU e3: AR 1209
Checks: DP
Release: V13
Page 42 of 524 411-9001-124 18.16 1.0
administrativeState
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.
administrativeState
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.
411-9001-124 18.16 1.0 Page 43 of 524
administrativeState
A 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 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 and no
build BDA is possible without a valid license.
Value range: [locked / unlocked / shuttingDown (soft release)]
Object: bts
Type: DP
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.
Page 44 of 524 411-9001-124 18.16 1.0
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 calls
supported 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}".
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.
411-9001-124 18.16 1.0 Page 45 of 524
administrativeState
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.
is at least one built BSC with "dataOnNoHoppingTS" activated, then, no

is at least one built BSC with “preferredNonAdaptativeAMRcodec”
activated, then, no TRX, bts, btsSiteManager, unlocking, no reset BDA
and no build BDA is possible without a valid license.
A btsSiteManager object is created in locked state..
Type: DP
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.
Page 46 of 524 411-9001-124 18.16 1.0
administrativeState
Description: ISO state. Locking the object blocks the collection of data and the
generation of the associated messages.
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.
Type: DP
Note: 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.
administrativeState
Description: ISO state.
Object: cc
Feature: BSC/TCU e3: AR 1209
Type: DP
Release: V13
administrativeState
Object: cem
Type: DP
Release: V13
411-9001-124 18.16 1.0 Page 47 of 524
administrativeState
Object: controlNode
Type: DP
Release: V13
administrativeState
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.
Object: efd
Type: DP
administrativeState
Object: g3BscEqp
Type: DP
Release: V13
administrativeState
Object: hardware transcoder 3G
Type: DP
Release: V13
administrativeState
Page 48 of 524 411-9001-124 18.16 1.0
Object: hsaRc
Feature: BSC 3000 optical
Type: DP
Release: V17
administrativeState
Object: hsaRcTcu
Feature: TCU 3000 optical
Type: DP
Release: V17
administrativeState
Object: iem
Type: DP
Release: V13
administrativeState
Value range: [unlocked]
The igm object is always unlocked.
Object: igm
Feature: Abis Over IP
Type: DP
Release: V18.0
administrativeState
Object: iom
Feature: BSC 3000 optical / TCU 3000 optical
411-9001-124 18.16 1.0 Page 49 of 524
Type: DP
Release: V17
administrativeState
Object: interfaceNode
Type: DP
Release: V13
administrativeState
Object: ipgRc
Type: DP
Release: V18.0
administrativeState
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
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.
Page 50 of 524 411-9001-124 18.16 1.0
administrativeState
Description: Activation state of a repeated job
A job object is created in unlocked state.
When a job is set inactive, it is not run.
Object: job
Type: DP
Checks: [M]: The job is not running.
administrativeState
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.
administrativeState
Object: lsaRc
Type: DP
Release: V13
administrativeState
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
411-9001-124 18.16 1.0 Page 51 of 524
administrativeState
Object: mms
Type: DP
Release: V13
administrativeState
Object: omu
Type: DP
Release: V13
administrativeState
A pcmCircuit object is created in locked state.
Object: pcmcircuit
Type: DP
administrativeState
A pcu object is created in locked state.
Object: pcu
Feature: GPRS (SV407 - V12)
Type: DP
Release: V12
Page 52 of 524 411-9001-124 18.16 1.0
administrativeState
A signallingLink object is created in locked state.
Object: signallingLink
Type: DP
administrativeState
Object: sw8kRm
Type: DP
Release: V13
administrativeState
Object: tmu
Type: DP
Release: V13
administrativeState
Description: ISO state. Locking the object blocks the collection of data and the
generation of the associated messages.
A traceControl object is created in locked state. Unlock the object to start
collecting trace data in the related BSC.
Type: DP
411-9001-124 18.16 1.0 Page 53 of 524

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.
administrativeState
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.
functionality succeeds only when a valid license is available. When there is
at least one built BSC with "dataOnNoHoppingTS" activated, then, no

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 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
[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
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:
Page 54 of 524 411-9001-124 18.16 1.0
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.
administrativeState
A transcoder object is created in locked state.
Object: transcoder
Type: DP
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.
administrativeState
Object: trm
Type: DP
Release: V13
administrativeState
Value range: [locked / unlocked / shuttingDown (soft release)] An xtp object is created
in locked state.
411-9001-124 18.16 1.0 Page 55 of 524
Object: xtp
Type: DP
[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
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.
agprsFilterCoefficient Class 3
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
Default value: 0 (deactivates the feature in the cell at the PCU level).
Type: DP
Release: V14
agpsTimer Class 3
Description: Duration of an A-GPS location.
Value range: [0 to 255] seconds
Object: bsc
Default value: 0 second
Type: DP
Release: V15
Note: This parameter is optional.
Page 56 of 524 411-9001-124 18.16 1.0
alarm criteria
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
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.
alarm criteria
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.
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.
alarm number
Description: To select alarms with a given number.
Type: DP
411-9001-124 18.16 1.0 Page 57 of 524
alarm severity
Description: To select alarms according to the severity.
Value range: [critical / major / minor]
Type: DP
alarm state
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]
Type: DP
alarmDuration
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
alarmPriority
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.
Page 58 of 524 411-9001-124 18.16 1.0
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
allocationState
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
allocPriorityTable Class 3
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
allocPriorityThreshold Class 3
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
411-9001-124 18.16 1.0 Page 59 of 524
Default value: 0
Type: DP
Number of 1 <= Number of free Number of free TCH

free TCH <= >
TCH = 0 allocPriorityThreshold allocPriorityThreshold
TCH request of - queueing if TCH allocated TCH allocated
priority 0 defined or -
reject
TCH request of - queueing if - queueing if defined or - TCH allocated
priority >0 defined or - reject
reject
allocPriorityTimers 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
AllocPriorityTimerT14Railways
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
allocWaitThreshold Class 3
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
Page 60 of 524 411-9001-124 18.16 1.0
Default value: 0000000055555

Type: DP
allOtherCasesPriority Class 3
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
amrAdaptationSet Class 3
Description: This attribute defines the lines of parameter used for the
adaptation 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.
amrDirectAllocIntRxLevDL Class 3
Description: Downlink RxLev threshold for direct AMR TCH allocation in the inner
zone.
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
411-9001-124 18.16 1.0 Page 61 of 524
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.
amrDirectAllocIntRxLevUL Class 3
Description: Uplink RxLev threshold for direct AMR TCH allocation in the inner zone.
Type: DP
Release: V14
amrDirectAllocRxLevDL Class 3
Description: Downlink RxLev threshold for direct AMR TCH allocation.
Type: DP
Release: V14
amrDirectAllocRxLevUL Class 3
Description: This attribute defines the downlink RxLev threshold for direct AMR TCH
allocation.
Page 62 of 524 411-9001-124 18.16 1.0

Type: DP
Release: V14
amrDlFrAdaptationSet class 3
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
amrDlHrAdaptationSet class 3
Description: This attribute defines the lines of parameter used for the downlink AMR
half rate adaptation mechanism.
Object: bts
Default value: 0
Type: DP
Release: V15
amrFRIntercellCodecMode Class 3
Description: Target codec mode to trigger an intercell quality handover from a RR
channel.
Value range: [12.2 / 10.2 / 6.7 / 5.9 / 4.75]
Default value: 4.75
Type: DP
411-9001-124 18.16 1.0 Page 63 of 524
Release: V14
amrFRIntracellCodecMode Class 3
Description: Target codec mode to trigger an intracell quality handover FR to FR.
Value range: [12.2 / 10.2 / 6.7 / 5.9 / 4.75]
Default value: 4.75
Type: DP
Release: V14
amrHRIntercellCodecMode Class 3
Description: Target codec mode to trigger an intercell quality handover from an HR
channel.
Value range: [7.4 / 6.7 / 5.9 / 4.75]
Default value: 4.75
Type: DP
Release: V14
amrHRToFRIntraCodecMode Class 3
Description: Target codec mode to trigger an intracell quality handover from AMR
HR to FR.
Value range: [7.4 / 6.7 / 5.9 / 4.75]
Default value: 6.7
Type: DP
Page 64 of 524 411-9001-124 18.16 1.0
Release: V14
amriRxLevDLH Class 3
Description: This attribute is the downlink RxLev threshold in case of AMR FR
intracell handover.
Value range: [-110 to -47]
Type: DP
Release: V14
amriRxLevULH Class 3
Description: This attribute is the uplink RxLev threshold in case of AMR FR intracell
handover.
Value range: [-110 to -47]
Type: DP
Release: V14
amrReserved1
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.
411-9001-124 18.16 1.0 Page 65 of 524
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
amrReserved2 Class 3
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.
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.
amrUlFrAdaptationSet class 3
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.
amrUlHrAdaptationSet class 3
Description: This attribute defines the lines of parameter used for the uplink AMR
half rate adaptation mechanism.
Object: bts
Page 66 of 524 411-9001-124 18.16 1.0
Type: DP
Default: 0
Release: V15
Note1: This parameter is optional.
amrWbDlAdaptationSet class 3
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
amrWBPowerControlCIThresholdUl class 3
Description: This attribute defines the set of parameters used for the downlink Wide
Value range: [corresponding to nominal, optimistic, pessimistic, operator]
Object: powerControl
Type: DP
Release: V18.0
amrWbNbMaxPdtchPreemption class 2
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.16 1.0 Page 67 of 524
amrWbSacchPowerOffsetSelection class 2
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
amrWbUlAdaptationSet class 3
Description: This attribute defines the set of parameters used for the uplink Wide
Value range: [nominal, optimistic, pessimistic, operator]
Object: bts
Type: DP
Release: V18.0
amrWBIntercellCodecMThresh Class 3
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
amrWBIntracellCodecMThresh Class 3
Description: This parameter specifies the target codec mode to trigger an inter-cell
AMR-WB quality handover.
Value range: [6K60, 8K85, 12K65]
Page 68 of 524 411-9001-124 18.16 1.0
Type:
Default: 8K85
Release: V18.0
amrWBiRxLevDLH Class 3
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
amrWBiRxLevULH Class 3
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
answerPagingPriority Class 3
TCH allocation requests with cause "reply to paging".
This priority is used in signaling mode on TCH only.
Object: bts
Type: DP
Default: 17
411-9001-124 18.16 1.0 Page 69 of 524
architecture
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.
assignRequestPriority Class 3
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
associatedLog
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.
associatedTMUPosition
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
Page 70 of 524 411-9001-124 18.16 1.0
Feature: BSC 3000 cell group

management/load balancing - stage 1(139111).
Type: DD
Default: None
aterLapd
Description: ATER LAPD repartition and status.
Value range: List of ATER LAPD descriptions [pcmAterId, tsAterId, lapdIsPresent,
lapdIsOpened], with:
pcmAterId: 0 to 65535
tsAterId: 0 to 65535
lapdIsPresent: yes / no
lapdIsOpened: yes / no
Object: cemRc
Feature: Optical TCU High Capacity 4K
Type: DD
Release: V18.0
aterLapd
Description: ATER LAPD distribution and status.
Value range: List of ATER LAPD descriptions [pcmAterId, tsAterId, lapdIsPresent,
lapdIsOpened], with:
pcmAterId: 0 to 65535
tsAterId: 0 to 65535
lapdIsPresent: yes / no
lapdIsOpened: yes / no
Object: lsaRc
Feature: BSC/TCU e3 GET DATA enhancement
Type: DD
Release: V16
atmRm
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
411-9001-124 18.16 1.0 Page 71 of 524
atmRmId
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
attenuation Class 2
Description: Attenuation due to coupling system losses. This value depends on the
BTS configuration.
Value range: [0 to 14] dB
Default value: Depends on the equipment.
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.
auditBdaStatus
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
Page 72 of 524 411-9001-124 18.16 1.0
auditState
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
availabilityStatus
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
availabilityStatus
Refer 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} ]
Object: bsc, bscMdInterface, pcmCircuit, signallingLink, transcoder
Type: DD
availabilityStatus
Refer 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.
411-9001-124 18.16 1.0 Page 73 of 524
availabilityStatus
The "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.
availabilityStatus
Value range: [{notInstalled} / {} / {failed} / {dependency}]
Object: atmRM, cc, cem, controlNode, iem, interfaceNode, lsaRc, mms, omu,
sw8kRm, tmu, trm, hsaRc, hsaRcTcu, iom
Type: DD
availabilityStatus
Value range: [notInstalled / Failed / onLine /
degraded]
Object: igm
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
Page 74 of 524 411-9001-124 18.16 1.0
availabilityStatus
Value range: [{degraded} / {} ]
Object: ipgRc
Type: DD
Release: V18.0
availabilityStatus
Value range: [{degraded} / {} ]
Object: ipgRc
Type: DD
Release: V18.0
availabilityStatus
The "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
availabilityStatus
Value range: [{} (the associated observation is running) / {offDuty} (the associated
observation has ended)]
Object: mdScanner
Type: DD
411-9001-124 18.16 1.0 Page 75 of 524
availabilityStatus
Refer 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
availabilityStatus
possible state parameter combinations: administrativeState,
availabilityStatus, operationalState.
Object: pcusn
Type: DD
Release: V12
availabilityStatus
possible state parameter combinations:
administrativeState, availabilityStatus, operationalState, and
usageState.
A state change notification is issued after the soft release.
Object: xtp
Type: DD
available synchronization sources

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.
Page 76 of 524 411-9001-124 18.16 1.0
Value range: [Abis synchronization only / Abis + external synchronization source

coming from a master BTS / Abis + GPS connection detected]
Object: bts
Type: BTS synchronization
averagingPeriod Class 2
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.
[0 to 255] SACCH frame (1 unit = 480 ms on TCH, 470 ms on SDCCH)
Value range:
Default value: 20
Type: DP
2.3. B
backup manager addresses

Description: Backup addresses of the OMC-R manager that receives the
messages. They are provided by the manager.
Object: efd - Display
Type: DI
backupServer
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
411-9001-124 18.16 1.0 Page 77 of 524
baseColourCode Class 3
Description: Base colour code value of the AdjacentCellReselection object..
Class: 3
Value range: [-1 to 7]
Default value: -1
Type: DP
Feature: NACC inter BSC/intra PCUSN feature
Release: V18 P&C5
Note: This parameter is available for BSC3000 only.
Checks: The routingArea, baseColourCode and networkColourCode parame-
ters of the adjacentCellReselection object should be either all valid or
all invalid. That means that for an AdjacentCellReselection object, if
one of the routingArea, baseColourCode and networkcolourCode pa-
rameters has a valid value, then the 2 other parameters should also
have a valid value.
The valid values for the baseColourCode parameter are [0 to 7].
Invalid value for this parameter is -1.
Description: Base station Color Code assigned to a neighbor cell. The (BCC, NCC)
pair forms the cell BSIC.
Type: DP
Checks: • [M]: Each defined (baseColourCode, bCCHFrequency, networkCo-
lourCode) combination is unique in the set including a
serving cell and its neighbor cells.
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
Page 78 of 524 411-9001-124 18.16 1.0
Type: DP
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.
batteryRemoteControllerPresence
Description: Whether BRC (Battery Remote Controller) board is present or not in
BTS 9000 Outdoor.
Value range: [0, 1]
• 0: Not present
• 1: present
Class 2
Default value: Absent
Type: DP
Release: V18
bCCHFrequency Class 3
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.16 1.0 Page 79 of 524

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 bCCHF
requency 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.
[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).
Page 80 of 524 411-9001-124 18.16 1.0
Type: DP
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).
[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.
411-9001-124 18.16 1.0 Page 81 of 524
bckgDLLayer3WindowSize Class 3
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
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.
bdaNewBscState
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-line

cancel 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
Page 82 of 524 411-9001-124 18.16 1.0
• "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
bdaSelected
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
bdaState
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
411-9001-124 18.16 1.0 Page 83 of 524
bdaVersionBuild
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
bdaVersionNumber
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
beacBatteryRemoteControllerPresence Class 2
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
beginning date
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
Page 84 of 524 411-9001-124 18.16 1.0
Type: DP
Checks: • [A]: beginning date is on or before end date.
beginSearchTime
Description: Absolute time to start searching for the observation reports
to 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 GSM OMC-R Com-
mands 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.
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.
(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.
beginSearchTime
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
411-9001-124 18.16 1.0 Page 85 of 524
beginSearchTime
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.
(411-9001-130).
Object: List available temporary observations
Type: DP
beginSearchTime
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.
(411-9001-130).
Object: List observation messages
Type: DP
bEPPeriod Class 3
Description: When EDGE is activated in the cell, the field is present and indicates the
BEP filter averaging period to the MS.
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.
Page 86 of 524 411-9001-124 18.16 1.0
biZonePowerOffset Class 3
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 3dB
If 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.
biZonePowerOffset Class 3
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 3dB
If 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)
bsc3GEqpt
Description: Identification and dynamic data describing the hardware configuration
of a BSC 3000 (global point of view).
Object: bsc3GEqpt
Type: DP
Release: V13
411-9001-124 18.16 1.0 Page 87 of 524
bsc3GEqptId
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
bsc
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
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).
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.
Page 88 of 524 411-9001-124 18.16 1.0
bsc equipment name

Description: To select messages issued by a given type of BSC or TCU processor.
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.
bscList
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
411-9001-124 18.16 1.0 Page 89 of 524
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 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.
bsc model
Description: To select messages issued by a given model of BSC.
Value range: bsc 3000
Type: DP
Checks: bsc30000 is the value that must be used for this parameter in case of a
BSC 3000.
bscNumber
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
bscArchitecture Class 0
Page 90 of 524 411-9001-124 18.16 1.0
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
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 the
bscArchitecture parameter equals bsc30000electrical_ip.
• [C/M]: The maximum PCM number is set to 231 (E1) / 308 (T1) at the
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

411-9001-124 18.16 1.0 Page 91 of 524
bscCapacityReduction Class 3
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
bscCounterList Class 3
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.
bscDateTime
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
Page 92 of 524 411-9001-124 18.16 1.0
bscGprsActivation Class 3
Description: Flag used to activate the GPRS at BSC level.
Value range: [disabled / enabled]
Object: bsc
Default value: disabled
Type: DP
Release: V12
bscHighSwitchingCapacity Class 3
Description: This parameter on the BSC enables the DS512 feature.
Object: bsc
Feature: BSC 3000 switching increase capacity (24436)
Type: DP
Release: V15
bscHopReconfUse Class 1
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]
Object: bsc
Default Value True
Type: DP
Checks: • [M]: It can be "true" provided the btsHopReconfRestart of one of
the related bts objects is also "true".
Release: V8
bscIPFirstAdr Class 2
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.
Value range: [7 to 15] String
411-9001-124 18.16 1.0 Page 93 of 524
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
bscIPSecondAdr Class 2
Description: Indicates the second BSC IP address used for a ’bscMdInterface’ object
instance.
IP address corresponds to the subscriber number on the network used.
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
bscList
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.
Object: executableSoftware
Type: DP
Release: V13
bscLog
Description: bscLog modelizes the management of the BSC internal log files.
Value range: [bscVers13 +Inf]
Object: bscLog
Page 94 of 524 411-9001-124 18.16 1.0
Type: DP
Release: V13
bscLogId
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
bscMdInterface
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.
bscMdInterfaceRef
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.
bscMdInterfaceVersionNumber
Description: Release number of the BSC/OMC-R interface. It is provided by
the 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
411-9001-124 18.16 1.0 Page 95 of 524
Type: DI
Restrictions: • [[C/M]: This attribute is not managed by users.
bscMSAccessClassBarringFunction Class 3
Description: Enables or disables dynamic barring of access class at the bsc
level.
Value range: [enabled / disabled]
Object: bsc
Type: DP
Release V9
bscName
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
bscPcuPcmRefList Class 2
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).
Page 96 of 524 411-9001-124 18.16 1.0
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
bscQueueingOption Class 1
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.
bscRefList
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]
Object: pcusn
Type: DP
Release: V12
411-9001-124 18.16 1.0 Page 97 of 524
bscReset
Description: Requests a control node reset.
Object: bsc3GEqpt
Type: DP
Release: V13
bscSitePcmList
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 GSM BSC Reference
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 GSM BTS Ref-
erence 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
Page 98 of 524 411-9001-124 18.16 1.0
Class 2
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.
• On unlocking the btsSiteManager object, pcm1 and pcm2 on bsc-

SitePcmList are not provisioned if the securedLoopActivation is en-
abled. This is available only for S8000 BTS family and not for
BTS18000 family
• On unlocking the btsSiteManager object, if the securedLoopActiva-

tion parameter is set to "enabled", the OMC-R checks no more than 2
PCMs are referenced.

tion parameter is set to "enabled", the OMC-R checks whether the
BSC PCM identities belong to the same board:
• S8000 BTS :
• bscSitePcmList = (n ~ 0) & (n+1 ~ 3) with the PCM identity "n" even

and different of PCM 0,1,2,3,4 and 5 of LsaRC 0 (synchronizing
ATER PCM)
• BTS9000 BTS :
• bscSitePcmList = (n ~ 0) & (n+1 ~ 1) with the PCM identity "n" even

and different of PCM 0,1,2,3,4 and 5 of LsaRC 0 (synchronizing
ATER PCM)
bscTimeSlot
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
411-9001-124 18.16 1.0 Page 99 of 524
bscUsedAdr
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
bsCvMax Class 3
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
bsPowerControl Class 3
Description: Whether BTS transmission power control is allowed at cell level.
Type: DP
bssMapT1 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
Page 100 of 524 411-9001-124 18.16 1.0
bssMapT4 Class 1
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
bssMapT7 Class 1
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
bssMapT8 Class 1
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 and
canceled 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.
bssMapT12 Class 1
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.
411-9001-124 18.16 1.0 Page 101 of 524
Object: bsc
Default value: 5
Type: DP
bssMapT13 Class 1
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
bssMapT19 Class 1
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
bssMapT20 Class 1
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
Page 102 of 524 411-9001-124 18.16 1.0
bssMapTchoke Class 1
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
bssPagingCoordination
Description: Enable BSS Cs paging coordination
Value range: disabled (0) /enabled (1)
Object: bts
Default value: 0 (recommended)
Type: DP
bssSccpConnEst Class 1
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: (if A Flex signallingLinkSet and remoteSignallingPoint
or QAM activated)
Default value: 5
Type: DP
Checks: • [C/M]: bssSccpConnEst parameters must have the same values for
both A and Lb signallingLinkSet instances.
Note: If A Flex - GSM Access or Quasi Associated Mode feature is activated,
this parameter will be available under SignallingLinkSet and RemoteS-
ignallingPoint objects. However; bssSccpConnEst parameter under
SignallingLinkSet object is not used and the default value will be
“Empty”.
411-9001-124 18.16 1.0 Page 103 of 524
bssSccpInactRx Class 1
Description: A interface timer T(iar) triggered by the BSC in the SCCP inactivity
detection procedure.
It is set either on transmission or receipt of CONNECTION CON-
FIRM or on receipt of any other message during the connection and
canceled on receipt of any message.
Value range: [2 to 30] minutes
Object: (if A Flex or signallingLinkSet and remoteSignallingPoint
QAM activated)
Default value: 11
Type: DP
Checks: • [C/M]: bssSccpInactRx parameters must have the same values
for both A and Lb signallingLinkSet instances.
Note: If A Flex - GSM Access or Quasi Associated Mode feature is acti-
vated, this parameter will be available under SignallingLinkSet and
RemoteSignallingPoint objects. However; bssSccpInactRx parame-
ter under SignallingLinkSet object is not used and the default value
will be “Empty”.
bssSccpInactTx Class 1
Description: A interface timer T(ias) triggered by the BSC in the SCCP inactivity
detection procedure.
It is set either on transmission or receipt of CONNECTION CON-
FIRM or on transmission of any other message during the connection
and canceled on transmission of any message.
QAM activated)
Default value: 11
Type: DP
Checks: • [C/M]: bssSccpInactTx parameters must have the same values
for both A and Lb signallingLinkSet instances.
RemoteSignallingPoint objects. However; bssSccpInactTx parame-
ter under SignallingLinkSet object is not used and the default value
will be “Empty”.
bssSccpRelease Class 1
Description: A interface timer T(rel) triggered by the BSC in the SCCP man-
agement procedure.
It is set on transmission of RELEASE and canceled on receipt of
RELEASED COMPLETE or RELEASED.
Page 104 of 524 411-9001-124 18.16 1.0
QAM activated)
Default value: 10
Type: DP
Checks: • [C/M]: bssSccpRelease parameters must have the same val-
ues for both A and Lb signallingLinkSet instances.
vated, this parameter will be available under SignallingLinkSet
and RemoteSignallingPoint objects. However; bssSccpRelease
parameter under SignallingLinkSet object is not used and the
default value will be “Empty”.
bssSccpSubSysTest Class 1
Description: A interface timer T(state info) triggered by the BSC in the SCCP
management procedure.
It is set on transmission of SST and canceled on receipt of SSA.
Value range: [5 to 60, by steps of 5] seconds
QAM activated)
Default value: 30
Type: DP
Checks: • [C/M]: bssSccpSubSysTest parameters must have the same
values for both A and Lb signallingLinkSet instances.
vated, this parameter will be available under SignallingLinkSet
and RemoteSignallingPoint objects. However; bssSccpSubSysT-
est parameter under SignallingLinkSet object is not used and the
default value will be “Empty”.
bsTxPwrMax Class 3
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 of

bsTxPwrMax added to the value of DLU attenuation (depending on
the 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 the
transceiverZone.
For PA: the value of PwrReqSentToPowerAmplifier must be between

31dB and 44dBm. This value range is valid for Radio Module (RM).
411-9001-124 18.16 1.0 Page 105 of 524
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 between

33dB and 46dB. This value range is valid for Medium Power Radio
Module (MPRM).
• For mono zone cells:
The value of PwrReqSentToPowerAmplifier is equal to the value of

bsTxPwrMax added to the value of DLU attenuation (depending on
the coupling equipment type, that is for instance D, H2D, H4D) or At-
tenuation on the btsSiteManager (if Attenuation has a value).
Note: The recommended value is 43 dB.
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’)
• [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
power output by the BTS.
Remark: For a GSM 1900 network (standardIndicator of bts object set to
’pcs1900’), the MD-R checks the following:
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 up-
date the database according to the list of edge frequencies, use the shell
/MD/install/shell/cm_configBde.sh.
Page 106 of 524 411-9001-124 18.16 1.0
bssSccpSubSysTest Class 1
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.
• [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.
411-9001-124 18.16 1.0 Page 107 of 524
bts
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
covering 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 max-
BtsPerNetwork (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 mobileNetworkCode attri-

butes 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 pro-
cessed in BSC mode (directedRetryModeUsed).
bsc object is unlocked and the parent btsSiteManager object is
locked.
bsc object is unlocked, the parent btsSiteManager object is locked,
and the bts object is locked.
• [D]: No adjacentCellHandOver object refers to the bts object (the de-

scribed cell is not used as a neighbor cell of another serving cell).

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.
Page 108 of 524 411-9001-124 18.16 1.0
bts
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.
bts
Description: Identifier of an ipm object.
Value range: [1]
Object: ipm
Type: Id
Release V18
bts equipment name

Description: To select messages issued by a given type of BTS equipment.
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.16 1.0 Page 109 of 524
/ 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
bts list
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.
btsSMSynchroMode Class 2
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)
Page 110 of 524 411-9001-124 18.16 1.0
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.
Release: V15
bts time between HO configuration Class 3

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
btsDescription
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.
btsHopReconfRestart Class 2
Description: Whether hopping frequency reconfiguration is authorized on TX restart
in a cell.
Object: bts
Default value: true
Type: DP
411-9001-124 18.16 1.0 Page 111 of 524
Checks: • [C/M]: If the attribute value is "true", the bscHopReconfUse attribute

of the parent bsc object is also "true".
Release: V8
btsIsHopping Class 2
Description: Whether frequency hopping is allowed in a cell.
Value range: [hopping / noHopping / hoppingWithCarrierFilling (V8) / noHopping-
WithCarrierFilling (V8)]
Object: bts
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 used

in 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.
btsMSAccessClassBarringFunction Class 3
Description: Enable or disable dynamic barring of access class at the bts level.
Object: bts
Page 112 of 524 411-9001-124 18.16 1.0

Type: DP
Release: V9
btsReserved3 Class 3
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
Type: DP
Release: V12
btsReserved4 Class 3
Description: Attribute reserved for future use.
Object: bts
Type: DP
Release: V12
btsSensitivity Class 3
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.
btsSensitivityInnerZone Class 3
Description: Minimum power needed for BTS decoding in the inner zone of a dual-
band cell.
411-9001-124 18.16 1.0 Page 113 of 524
Object: bts
Default value: 0
Type: DP
Release: V12
btsSiteManager
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
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.
bsc object is unlocked and the btsSiteManager object is locked.
Page 114 of 524 411-9001-124 18.16 1.0
btsSiteManager
Description: Identifier or name of a btsSiteManager object. It defines the parent
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).
btsSiteManager model
Description: To select messages issued by a given model of BTS.
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]
Type: DP
btsSiteManagerList Class 2
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.
411-9001-124 18.16 1.0 Page 115 of 524
btsThresholdHopReconf Class 2
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
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
btsType Class 2
Description: Defines the type of the Abis interface used by the site: IP or TDM.
Value range: [TDM / IP]
Dedfault value: TDM
Type: DP
Page 116 of 524 411-9001-124 18.16 1.0
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.

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 all
the 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.
btsWithCavity Class 2
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
411-9001-124 18.16 1.0 Page 117 of 524
buildState
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
2.4. C
callClearing Class 3
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".

of the bts object is "true".
• 7 km for urban
• 35 km for rural
callDropActivation class 3
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
Page 118 of 524 411-9001-124 18.16 1.0
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.
callPathObservationArea Class 2
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]
Type: DP
Checks: • [C/M]: All observed objects belong to the same class.
• [M]: The callPathTrace object is locked.
callPathTrace
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: • [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: V8.0
411-9001-124 18.16 1.0 Page 119 of 524
callPathTraceType Class 2
Description: Type of information stored by the BSC.
The information stored with respect to the type is detailed in 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.
callReestablishment Class 3
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
callReestablishmentPriority Class 3
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
Page 120 of 524 411-9001-124 18.16 1.0
capacityAlarmThreshold
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:
• 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.
capacityTimeRejection Class 3
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
cause
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.
411-9001-124 18.16 1.0 Page 121 of 524

Type: DP
cCCHGprsAtBtsLevel Class 3
Description: Used to activate the CCCH management at BTS level.
Object: bts
Type: DP
Release: V14
cc
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
ccId
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
Page 122 of 524 411-9001-124 18.16 1.0
cellAllocation Class 2
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.
[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.
Maximum gap
between frequencies Number of frequencies
between 257 and 512 [2 to 18]
411-9001-124 18.16 1.0 Page 123 of 524
• [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).
cellBarQualify Class 3
Description: Cell selection priority used in the C2 algorithm in Phase II.
cell BCCH.
Value range: [true (low priority) / false (normal priority)]
Object: bts
Default Value: False
Type: DP
Release: V8
cellBarred Class 3
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 124 of 524 411-9001-124 18.16 1.0
cellDeletionCount 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.
cellDtxDownLink Class 3
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.
cellIdentity Class 3
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, a neighbor cell of
the current cell.
Class: 3
411-9001-124 18.16 1.0 Page 125 of 524
Type: DP
Note: This parameter is available for BSC 3000 only. The adjacentCellRese-
lection object is enhanced for V18 P&C5 to include the cell indentity in-
formation through this parameter and the this information of every BTS
is communicated to PCU as a part of adjacentcellreseletion list.
bor cells.
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.
cellName
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.
– 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
Page 126 of 524 411-9001-124 18.16 1.0
cellPagingState
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".
Object: bts
Type: DD
cellReselectHysteresis Class 3
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 - rxLevAccessMin
B = msTxPwrMaxCCH - Maximum RF output power of the MS. The re-
selection criterion (C2) formula is given with the
cellReselectOffset 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.
411-9001-124 18.16 1.0 Page 127 of 524
cellReselectOffset Class 3
Description: Encouragement to re-select a cell (C2 criterion) for phase
2 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
Release: V8
Note: The value given to this attribute allows to more or less encourage the
mobiles to re-select the cell.
cellReselInd Class 3
Description: Whether cell re-selection criterion (C2) use is authorized.
Value Range: [true / false]
Object: bts
Default Value: True
Type: DP
Release: V8
cellThreshold Class 2
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
Page 128 of 524 411-9001-124 18.16 1.0
Default Value: 1
Type: DP
cellType Class 3
Description: Type of the adjacent cell.
Value range: [normalType / umbrellaType / microType]
Default Value normalType
Type: DP
cellType Class 3
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).
cemId
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
for BSC 3000 and TCU 3000.
Object: cem
Type: DP
Release V13
cemPcmList class 3
Description: List of the PCM links for the cemRc provided with the sub-parameters:
• pcmInstance
• virtualPortNumber
Value range: [0 ... 335
Object: cemRc
Type: DP
411-9001-124 18.16 1.0 Page 129 of 524
Release: V18.0 P&C1

Note:
channel
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.
channel state
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
Page 130 of 524 411-9001-124 18.16 1.0
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.
channelReleaseOnAbisFailure
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
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
0 1 0 0 1 1 0
IEI = TD_S PARE 5_IEI
0 0 0 0 0 0 0
High part of spare 5
0 0 0 0 0 0/1 n/a
Low part of spare5
411-9001-124 18.16 1.0 Page 131 of 524
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.
channelType Class 2
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
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.
Page 132 of 524 411-9001-124 18.16 1.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:
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 below:
channelType Bits C5-C1

tCHFull BM + ACCH (SACCH/FACCH)
411-9001-124 18.16 1.0 Page 133 of 524
sDCCH SDCCH/8 + ACCH subchannels [0 to 7]

(SACCH/FACCH)
mainBCCH BCCH
RACH (Uplink)
PCH + AGCH (Downlink)
mainBCCHCom- BCCH
bined RACH (Uplink)
SDCCH/4 + ACCH subchannels [0 to 3]
bcchSdcch4CBC BCCH
H CBCH (= SDCCH No2)
RACH (Uplink)
sdcch8CBCH CBCH (= SDCCH No2)
(SACCH/FACCH)
cCH BCCH
RACH (Uplink)
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
Remark: SMS-CB function knowing.
The following counters have been multiplexed on TSs 0, 2, 4, and 6 for
the Extended CCCH feature: C1026, C1027, C1028, C1029, C1030,
Note: C1031, C1033, C1604, C1605.
No recommended value is specified since this parameter depends on
Comments: the strategy of the operator.
chanState
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.

Page 134 of 524 411-9001-124 18.16 1.0
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
chosenChannelAsscomp Class 1
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.
chosenChannelCompL3Info Class 1
Description: Whether the "Chosen channel" element is used in the COMPLETE
LAYER 3 INFORMATION messages (Phase II compliance).
Type: DP
Release: V8
BSC parameter chosenChannelCompL3Info needs to be set to
TRUE.
chosenChannelHoPerf Class 1
Description: Whether the "Chosen channel" element is used in the HANDOVER
PERFORMED messages (Phase II compliance).
Type: DP
411-9001-124 18.16 1.0 Page 135 of 524
Release: V8
TRUE.
chosenChannelHoReq Class 1
Description: Whether the "Chosen channel" element is used in the HANDOVER
REQUEST ACKNOWLEDGE messages
(Phase II compliance).
Type: DP
Release: V8
TRUE.
cic Class 0
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
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.
Page 136 of 524 411-9001-124 18.16 1.0
cId Class 3
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.
circuitGroupBlock Class 1
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)
Value range: [false / true]
Type: DP
Release: V8
circularFileId
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 and
temporary) / instrumentPanel]
Object: bscMdInterface - Circular file
Type: Id
Checks: [A]: The circular file is created.
411-9001-124 18.16 1.0 Page 137 of 524
circularFileState
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
clear time
Description: To select alarms cleared at that time.
Absolute time format entry forms are detailed in GSM OMC-R
Commands Reference - Security, Administration, SMS-CB, and Help
menus (411-9001-130).
Object: Cleared alarm log - Filter
Type: DP
cleared by
Description: To select alarms ceased by a given user. Enter the user’s
name as defined in the user’s profile.
Type: DP
clearing cause
Description: To select alarms according to the cause of ceasing.
Value range: [user command / object enabled / object deleted / clear event received /
automatic purge / cleared on low threshold crossing / circular file
saturation]
Type: DP
Page 138 of 524 411-9001-124 18.16 1.0
cn
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 modules
are also managed.
Object: controlNode
Type: DP
control Node Id
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
coderPoolConfiguration Class 2
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 +15
powerDL: -15 to +15
Object: transcoder
Type: DP
Release: V13
411-9001-124 18.16 1.0 Page 139 of 524
coderPoolConfiguration Class 2
Description: This attribute indicates enumerated speech coding algorithms
supported by the TCU.
Value range: List of [coderAlgo, minimumCall, powerULI, powerDLI], with:
ctmEnhancedFullRateCoder / amrFullHalfRateCoder /
amrWideBandFullRateCoder minimumCall: 1 to 65535 until V16 / 0 to
65535 for V17 and higher
powerUL: -15 to +15
powerDL: -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
coderPoolList
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:
ctmEnhancedFullRateCode / amrFullHalfRateCoder /
amrWideBandFullRateCoder archipelagoes: 0 to 65535
emptyArchipelago: 0 to 65535
maximumCall: 0 to 65535
currentCall: 0 to 65535
minimumCallsRespected: yes / no
Type: DD
Release: V13
Page 140 of 524 411-9001-124 18.16 1.0
codingScheme Class 2
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.
command classes
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.
Type: DP
command line
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 GSM OMC-R Commands
Reference - Security, Administration, SMS-CB, and Help menus (411-
9001-130).
Object: job
Type: DP
411-9001-124 18.16 1.0 Page 141 of 524
command number
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]
Object: commandFile - Abort
Type: DP
commandFile
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 GSM OMC-R Commands
9001-130)).
Value range: [case sensitive, 14 characters max.]
Object: commandFile - Create file
Type: Id
comment
Description: User-defined text
Value range: LString (0-510 symbols)
Default value: Empty string
comment
Description: User-defined text
Value range: LString (0-510 symbols)
Default value: Empty string
Type: P&C1
Page 142 of 524 411-9001-124 18.16 1.0
comment
Description: Text comment.
Object: report template
Type: DP
Release V11
comment
Description: Additional information coming with the short message. It is not
broadcast.
Object: short message
Type: DP
comments
Description: Additional information (such as creation date).
Object: software - Display markers
Type: DD
compressedModeUTRAN Class 3
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
computeSyntheticCounters
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.
411-9001-124 18.16 1.0 Page 143 of 524
Object: Display xxx report

Type: DP
concentAlgoExtMsRange Class 3
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
Checks: • [C/M]: concentAlgoExtMsRange concentAlgoIntMsRange

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
concentAlgoExtRxLev Class 3
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
concentAlgoExtRxLevUL Class 3
Description: Uplink RxLev threshold above which an intra-cell handover from the
large zone to the small zone is triggered.
Page 144 of 524 411-9001-124 18.16 1.0
Condition: To define if the associated bts object describes a concentric,

dualband or dualcoupling cell
Type: DP
Feature: Multi-zone cell enhancement
Release: V18.0
concentAlgoIntRxLevUL Class 3
Description: Uplink RxLev threshold below which an intra-cell handover
from the small zone to the large zone is triggered.
Value range: [less than -110, -110 to -109, ..., -49 to -48, more than -48]
dBB
Default value: less than -110
Type: DP
Release: V18
concentric cell Class 2

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
411-9001-124 18.16 1.0 Page 145 of 524
Note: Dualband cells are only available for S8000 DRX transceiver
architecture.
Dualcoupling cells are only available for BTSs equipped
with non mixed DCU4 or DRX transceiver architecture.
Release: V9
concentAlgoExtRxLevUL Class 3
Description: Uplink RxLev threshold above which an intra-cell handover from the
large zone to the small zone is triggered.
dualband or dualcoupling cell
Type: DP
Release: V18.0
concentAlgoIntMsRange Class 3
Description: MS to BTS distance from which a handover from the small
zone to the large zone will be requested.
The following inequality, that is not checked by the system, must be
true (refer to these entries in the Dictionary).
concentAlgoIntMsRange ≤ msRangeMax
Value range: [1 to 34] km (non-extended mode)
[1 to 120] km (extended mode)
Default value: 34 km
dualband or dualcoupling cell.
Type: DP
Checks: • [C/M]: concentAlgoIntMsRange ≤ concentAlgoExtM
sRange

bute of the associated bts object is "false".

bute of the bts object is "true".
Release: V9
Page 146 of 524 411-9001-124 18.16 1.0
concentAlgoIntRxLev Class 3
Description: Level of the MS signal strength below which a handover is
requested from the small zone to the large zone.
Value range: [less than -110, -110 to -109, ..., -49 to -48, more than -48] dB
dualband or dualcoupling cell.
Type: DP
Checks: • [C/M]: concentAlgoIntRxLev < concentAlgoExtRxLev
Release: V9
condition
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 =
equipment processor number alarm =
faultNumber alarm <=>
operationalState state change <=>
perceived severity alarm =
postMortem alarm =
usageState state change =
411-9001-124 18.16 1.0 Page 147 of 524
condition
Description: Condition for calling the counting mechanism when a
The following fields can be combined in the logical
expression:

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 ex-
pression:
• & 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
configRef
Description: Dual TDMA DLU references (QBx, KBx, MIx and NIx) shall not be
selected without the corresponding RTU
The 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 BDA
The 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 and no build BDA is
Value range: [1 to VVV]
Class 3
Type: DP
Page 148 of 524 411-9001-124 18.16 1.0
Checks: • There is a feature lock for dual TDMA configurations in V18.0, Get
these licenses before upgrading to V18.0.
• On unlocking the btsSiteManager object, select a Secured Loop

ConfigRef if the securedLoopActivation is set to enabled.
• A secured loop configRef is a configRef with the R2 field == 1.
• On unlocking the btsSiteManager object, if the configRef supports

SecuredLoop (configRef with R2 field set to 1), the OMC-R checks
the redundantPcmPresence parameter is set to "TRUE"
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.
configRefList
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
configurationType
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.
411-9001-124 18.16 1.0 Page 149 of 524
counter list
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
connectedHsaOnPort0 Class 3
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 Not applicable
value:
Type: DP
Release: V18.0
connectedHsaOnPort1 Class 3
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
value:
Type: DP
Release: V18.0
Page 150 of 524 411-9001-124 18.16 1.0
counter list filename

Description: Full pathname of the counter list file.
Type: DP
Release: V11
counterId
Description: Q3 name of a permanent BSS observation counter. See GSM BSS
Fundamentals — Operating Principles (411-9001-007).
Value range: [50 characters max., case sensitive]
Object: mdWarning - detection function = "outOfRangeCounter"
Type: DP
counters
Description: List of the Q3 names of the counters eligible for observation, which are
in the counter list filename.
Type: DP
Release: V11
counters
Description: List of counters (Q3 names) chosen for observation.
Value range: [list of Q3 counter names]
Type: DP
Release: V11
cpueNumber Class 0 or Class 1 (see note)

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)
411-9001-124 18.16 1.0 Page 151 of 524
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
cpueOccurrence
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
cRC 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
creator
Description: Report template creator name.
Type: DP
Release: V11
Page 152 of 524 411-9001-124 18.16 1.0
criteriaEventType
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
cSS7LocalSubSystemNumber Class 0
Description: SS7 local subsystem number for the BSSMAP application.
QAM activated)
Type: DP
Release: V15
Note: • The recommended value is 254 (0x00FE).
• This parameter is only available for BSC 3000.
• If A Flex - GSM Access or Quasi Associated Mode feature is acti-

RemoteSignallingPoint objects. However;
cSS7LocalSubSystemNumber parameter under SignallingLinkSet
object is not used and the default value will be “Empty”.
cSS7RemoteSubSystemNumber Class 0
Description: SS7 remote subsystem number for the BSSMAP application.
QAM activated)
Type: DP
Release: V15
Note: The recommended value is 254 (0x00FE).
411-9001-124 18.16 1.0 Page 153 of 524

If A Flex - GSM Access or Quasi Associated Mode feature is activat-
ed, this parameter will be available under SignallingLinkSet and Re-
moteSignallingPoint objects. However;
cSS7RemoteSubSystemNumber parameter under SignallingLinkSet
object is not used and the default value will be “Empty”.
CTU cable
Description: The CTU (cable transition unit) provides the physical interface to the
customer’s spans in the BSC 3000 and the TCU 3000.
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
current log size

Description: Current log size expressed in bytes.
Type: DP
Remark: The attributes of the log objects are not managed by users.
current synchronization mode

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
Page 154 of 524 411-9001-124 18.16 1.0
currentChannelHorqd Class 1
Description: Whether the "Current channel" element is used or not in the HANDO-
VER REQUIRED messages (Phase II compliance).
Default value: true
Type: DP
Release: V12
411-9001-124 18.16 1.0 Page 155 of 524
concentAlgoIntRxLev Class 3
Description: Level of the MS signal strength below which a handover is requested
from the small zone to the large zone.
Type: DP
Checks: • [C/M]: concentAlgoIntRxLev < concentAlgoExtRxLev
Release: V18.0
cypherModeReject Class 1
Description: Whether the CYPHER MODE REJECT messages are used (Phase II
compliance).
Type: DP
Release: V8
Page 156 of 524 411-9001-124 18.16 1.0
2.5. D
dARPPh1Priority class 2
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
data non transparent mode Class 3

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
Unit: 9.6
Type: DP
Checks: • [C/M]: The only allowed configurations are the following:
• "9.6"
• "9.6" and "14.4"

Release: V11
data non transparent mode Class 3

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
411-9001-124 18.16 1.0 Page 157 of 524
• "9.6"
• "9.6" and "14.4"

Release: V9
data transparent mode Class 3

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
data transparent mode Class 3

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
• 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
data14-4OnNoHoppingTs Class 3
Description: Whether data 14.4 kbit/s transmission rate is allowed at bts level on the
non hopping TSs.
Object: bts
Page 158 of 524 411-9001-124 18.16 1.0
Type: DP
Release: V12
dataOnNoHoppingTS
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.
Value range: disabled/enabled
Object: bts
Class: 3
Type: DP
Release: V18.0 P&C3
Note: [M]: The parameter “dataOnNoHoppingTS” has RTU semantic control
on SET.
date
Description: Date on which the observation report was created.
Date format entry forms are detailed in Nortel GSM OMC-R
Commands Reference - Security, Administration, SMS-CB,
and Help menus (411-9001-130).
Value range: [<date>]
Object: Display daily report
Type: DP
date
Description: Date on which data to archive were recorded.
Date format entry forms are detailed in GSM OMC-R Commands Ref-
erence - Security, Administration, SMS-CB, and Help menus (411-9001-
130).
Object: md - Archive
Type: DP
Note: Archiving fault, observation, or trace data is not possible for the current
day.
411-9001-124 18.16 1.0 Page 159 of 524
date
Description: Date on which data to restore were recorded.
Date format entry forms are detailed in GSM OMC-R Commands Refer-
ence - Security, Administration, SMS-CB, and Help menus (411-9001-
130).
Object: md - Restore
Type: DP
date
Description: Date on which data to archive were recorded.
130).
Object: omc - Archive/Restore
Type: DP
Note: Archiving fault, observation, or trace data is not possible for the current
day.
date
Description: Date on which data to restore were recorded.
130).
Object: omc - Restore
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"
Field Meaning Value
BSx Name x = [1.. 4]
ab Version [09..32]
cd Subversion Number [01..99]
ef Edition [01..99]
Page 160 of 524 411-9001-124 18.16 1.0
delivery
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 [01..99]
Subversion Number
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/ TRX/TR1/DRX/ CDR/EDG/
ICM 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
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.

411-9001-124 18.16 1.0 Page 161 of 524
day intervention
Description: Type of action associated with an alarm criterion in the daytime
configuration.
Value range: [noAlarm / critical / major / minor]
Type: DP
day to be purged
Description: Date on which the data to purge were recorded.
130).
Object: omc - Data purge
Type: DP
Release: V10
degradedCause
Description: Gives the reasons of the degraded or enabled state.
Value range: [Not significant, GPRS]
Object: bts
Type: DD
Release: V15
degradedCause
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
Page 162 of 524 411-9001-124 18.16 1.0
default3Gpriority
Description: Default 3G priority of a UTRAN frequency layer
Value range: (non significant, 0, 1, 2, 3, 4, 5, 6, 7)
Object: bts
Checks: • The value for Default3Gpriority parameter and each 3Gpriority value
from 3GReselection ARFCN parameter must be different from ltePri-
ority parameter value for each lteAdjacentCellReselection in bts ob-
ject.
• If the 3GReselectionOnPriority parameter is set to enabled and if at

least one ARFCN parameter from 3GReselection ARFCN structure
has its associated parameters (3Gpriority, threshold3Glow,
threshold3Ghigh and 3GQRxLevMin) set to "non significant", the 3
parameters "default3Gpriority", "defaultThreshold3G" and
"default3GQRxLevMin" must be different from "non significant".
Default value non significant
Type: DP
Release: V18
default3GQRxLevMin
Description: Default minimum RX level required for cells on the target UTRAN fre-
quency (dBm)
Value range: ( non significant, -119, -117, -115,, …,-59, -57)
Object: bts
Unit dBm
Type: DP
Checks: If the 3GReselectionOnPriority parameter is set to enabled and if at least
one ARFCN parameter from 3GReselection ARFCN structure has its
associated parameters (3Gpriority, threshold3Glow, threshold3Ghigh
Class 3
Release: V18 P&C4
Default not allowed LTE cells

Description: A structure visible at the MMI under the bts object and composed of the
Default not Allowed PCIDs (up to 8 PCIDs) and Default PCID Bitmap
Group parameters. It lists the default not allowed E-UTRAN cells identi-
fied by PCIDs and PCID bitmap group
Object: bts
411-9001-124 18.16 1.0 Page 163 of 524
Value range See“Default Not Allowed PCIDs” on page 163 and “Default PCID
Bitmap Group” on page 163.
Default value empty list ~ 000000
Type: DP
Class 3
Release: V18 P&C4
Default Not Allowed PCIDs

Description: A default list of not allowed PCIDs (belonging to Default not allowed LTE
cells composite attribute)
Value range List of Up to 8 PCIDs
Object: bts
Default value empty list
Type: DP
Class 3
Release: V18 P&C4
Default PCID Bitmap Group

Description: List of default not allowed E-UTRAN cells identified PCID bitmap group.
See “Default not allowed LTE cells” on page 162.
Object: bts
Value range (000000, 000001,000010,... to 111111)
Default value 000000
Type: DP
Class 3
Release: V18 P&C4
defaultThreshold3G
Description: Default reselection threshold towards UTRAN FDD or TDD cells
Value range: (non significant, 0 , 2, 4, 6 , …, 60, 62)
Object: bts
Unit dB
Checks: If the 3GReselectionOnPriority parameter is set to enabled and if at least
one ARFCN parameter from 3GReselection ARFCN structure has its
associated parameters (3Gpriority, threshold3Glow, threshold3Ghigh
Type: DP
Page 164 of 524 411-9001-124 18.16 1.0
Class 3
Release: V18 P&C4
delayBetweenRetrans Class 2
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
Object: bts
Default value: 0
Type: DP
Release: V8
deltaUtc
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 to the workstation internal
clock.
Note: This parameter cannot be modified.
detectionFunction
Description: Associated function.
Value range: [excessiveAnomalyRate / outOfRangeCounter]
Object: mdWarning
Type: DP
directAllocIntFrRxLevDL Class 3
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).
411-9001-124 18.16 1.0 Page 165 of 524
Type: DP
Remark: V18.0
directAllocIntFrRxLevUL Class 3
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
Remark: V18.0
directedRetry Class 3
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
directedRetryModeUsed Class 3
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.
Page 166 of 524 411-9001-124 18.16 1.0
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
directedRetryPrio Class 3
Description: Defines the number priority for directed retry handovers.
Object: bts
Type: DP
Remark: V12
directory
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
display Data Configuration

Description: A command applied on btsSiteManager to configure the data display.
Value range: normal EDGE
Object: Select the object instance and choose the command.
display Data Information

Description: A command applied on btssiteManager to state required data display.
Value range: normal EDGE
Object: Select the object instance and choose the command.
411-9001-124 18.16 1.0 Page 167 of 524
distHreqt Class 3
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).
distributionActivation Class 3
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.
Release: V15
distributionDuration Class 3
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
Default value: 0
Release: V15
Page 168 of 524 411-9001-124 18.16 1.0
distributionTime Class 3
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
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
distributionQualityThreshold Class 3
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
411-9001-124 18.16 1.0 Page 169 of 524
distWtsList Class 3
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.
Page 170 of 524 411-9001-124 18.16 1.0
diversity Class 2
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
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).
dlGMSKMCS1UpperThreshold Class 3
Description: The parameter allows to set the threshold between MCS1 and the next
code in the DL GMSK Only Link Adaptation tables and the DL GMSK Ta-
ble.
Object: bts
Default value: 0
Feature: EDGE Family C MCS-1 & 4 implementation
Type: DP
Release: V18 P&C5
Note For P&C5 release this parameter is made visible on OMCR MMI.
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
Release: V15
the two DL GMSK Only Link Adaptation tables and the DL GMSK table.
411-9001-124 18.16 1.0 Page 171 of 524
Object: bts
Default value: 0 (disabled MCS3 in the Link Adaption tables)
Type: DP
Release: V15
code in the DL GMSK Table.
Object: bts
Default value: 0
Type: DP
Release: V18 P&C5
dlMCS1UpperThreshold Class 3
code in the DL 8PSK Link Adaptation table.
Object: bts
Default value: 0
Type: DP
Release: V18 P&C5
the DL 8PSK Link Adaptation table.
Object: bts
Type: DP
Release: V15
Page 172 of 524 411-9001-124 18.16 1.0
Object: bts
Type: DP
Release: V15
code in the DL 8PSK Link Adaptation table.
Object: bts
Default value: 0
Type: DP
Release: V18 P&C5
Object: bts
Type: DP
Release: V15
Object: bts
411-9001-124 18.16 1.0 Page 173 of 524

Type: DP
Release: V15
Object: bts
Type: DP
Release: V15
Object: bts
Type: DP
Release: V15
diversityUTRAN Class 3
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.
drxTimerMax Class 3
Description: Maximum value allowed for mobile stations to request non-DRX mode
after packet transfer mode.
Page 174 of 524 411-9001-124 18.16 1.0
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: 0s
Type: DP
Release: V12
dtxMode Class 3
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.
duration
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
dwAckTime Class 3 (packetAckTime)

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
411-9001-124 18.16 1.0 Page 175 of 524
Type: DP
Release: V12
dynamicAbis class 2
Description: Enables and disables the dynamic abis feature
Value range: Disabled/Enabled
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
dynamicAgprsAllowed Class 2
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.
Page 176 of 524 411-9001-124 18.16 1.0
2.6. E
early classmark sending Class 3

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
earlyClassmarkSendingUTRAN Class 3
Description: Indicates whether UTRAN classmark change message will be sent with
the Early classmark sending
Object: bts
Type: DP
Release: V17
EATrafficLoadEnd Class 3
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
Type: DP
Release: V18.0
411-9001-124 18.16 1.0 Page 177 of 524
EATrafficLoadStart Class 3
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
edgeDataServiceType Class 2
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
edgeFavor Class 3
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
eDGEMixity Class 3
Description: Limitation of GPRS mobiles allocation on EDGE TDMA.
Object: bts
Feature: EDGE dynamic allocation (20230)
Default value: 100
Page 178 of 524 411-9001-124 18.16 1.0
Type: DP
Release: V15
efd
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.
efdType
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.
411-9001-124 18.16 1.0 Page 179 of 524
Object: efd
Type: DP
egprsIrULActivation Class 3
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
egprsServices Class 3
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
error message displayed.
Release: V15
Page 180 of 524 411-9001-124 18.16 1.0
emergencyCallPriority Class 3
Description: Index in the table allocPriorityTable for a TCH allocation request whose
cause is "emergency call".
Object: bts
Default value: 17
Type: DP
emergencyCallRestricted Class 3
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 0

to 9
– For mobiles with access classes 11 to 15, emergency calls are

forbidden for those whose classes are listed in the entries of the
notAllowedAccessClasses attribute
Object: bts
Default value: restricted
Type: DP
emergencyThreshold Class 3
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
411-9001-124 18.16 1.0 Page 181 of 524
eMLPPThreshold Class 3
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]
Feature: ASCI (GSM-R V12)
Default value: none
Type: DP
Release: V12
EnableE911OnFullRateChannelPreferred Class 3
Description: Enables or disables the E911OnFullRateChannelPreferred feature.
Value range: enabled/disabled
Object: bsc
Type: DP
Release: V18 P&C3
enableRepeatedFacchFr Class 2
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
enableRepeatedFacchHr Class 2
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
Page 182 of 524 411-9001-124 18.16 1.0

Type: DP
Note: The recommended value is HR 6.7 and lower.
Release: V18.0
enableRepeatedFacchWBFr class 2
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
encrypAlgoAsscomp Class 1
Description: Whether the "Chosen encryption algorithm" element is used in the AS-
SIGN COMPLETE messages (Phase II compliance).
Type: DP
Release: V8
encrypAlgoCiphModComp Class 1
Description: Whether the "Chosen encryption algorithm" element is used in
the CIPHER MODE COMPLETE messages (Phase II compliance).
Type: DP
Release: V8
411-9001-124 18.16 1.0 Page 183 of 524
encrypAlgoHoperf Class 1
Description: Whether the "Chosen encryption algorithm" element is used in the HAN-
DOVER PERFORMED messages (Phase II compliance).
Type: DP
Release: V8
encrypAlgoHoreq Class 1
Description: Whether the "Chosen encryption algorithm" element is used in the HAN-
DOVER REQUEST ACKNOWLEDGE messages (Phase II compli-
ance).
Type: DP
Release: V8
encryptionAlgorSupported Class 0
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
encryptionAlgorSupported Class 3
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
Page 184 of 524 411-9001-124 18.16 1.0
Object: bsc
Default value: none
Type: DP
Checks: • [C/M]: Only one type of ciphering capability is defined.
Version: V17
end date
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.
end date
Description: Date on which data were last recorded in the log (default is the current
date). It is on or after start date.
130).
Object: System session log - Filter
Type: DP
Checks: • [A]: end date is on or after start date.
end of probative Phase Type

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.16 1.0 Page 185 of 524
end time
Description: Absolute time of final job run if the job is to be periodically run over a lim-
ited period of time.
(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.
end time
Description: End of system log reading on the requested end date (default is 24:00).
(411-9001-130).
Value range: [<time>]
Type: DP
Checks: • [A]: If end date and start date are identical, end time is after start
time.
endAlarmFilter
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
Page 186 of 524 411-9001-124 18.16 1.0
endAlarmThreshold
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
endAlarmThreshold
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 GSM BSS Fundamentals — Operating Principles (411-
9001-007).
endCounterThreshold
Description: Maximum counting threshold when a counter is involved.
411-9001-124 18.16 1.0 Page 187 of 524
Condition: To define if a counter is associated with the criterion.

Type: DP
endSearchTime
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.
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.
(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.
endSearchTime
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.
(411-9001-130).
Object: List available permanent observations
Type: DP
Page 188 of 524 411-9001-124 18.16 1.0
endSearchTime
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 GSM OMC-R Com-
mands Reference - Security, Administration, SMS-CB, and Help
menus (411-9001-130).
Object: List available temporary observations
Type: DP
endSearchTime
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 GSM OMC-R Com-
mands Reference - Security, Administration, SMS-CB, and Help
menus (411-9001-130).
Type: DP
endSessionCriteriaDuration
Description: Definition of the criterion end a call path tracing session.
Value range: [5 to 1080] mins
Type: DP
Release: V11
411-9001-124 18.16 1.0 Page 189 of 524
endSessionCriteriaType
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.
enhancedTRAUFrameIndication
Description: Whether the BTS uses the Enhanced TRAU Frame (EFT = executable
Software) for TCU.
Value range: [notAvailable / available / active]
Object: bsc
Type: DI
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
enhCellTieringConfiguration
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 1000
hoMarginTiering: Hysteresis between the uCirDLH and lCirDLH tiering
thresholds to avoid ping-pong handovers, expressed in dB
Value range: Int [0 to 63] dB
Page 190 of 524 411-9001-124 18.16 1.0
Description: selfTuningObs: Indicating that the bts is in charge of sending PwCI dis-
tribution onto Abis interface
Value 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 0
Value X X 0 0 0 0 0 0
Note:
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
equipment identity
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)
Type: DP
Notes: During the command "create mdWarning", the operator can define ei-
ther "equipment identity" or "processor identity", but not both.
Release: V11
equipment processor number

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]
411-9001-124 18.16 1.0 Page 191 of 524

Type: DP
error concealment unit Class 2

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
estimatedSiteLoad Class 3
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
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
Page 192 of 524 411-9001-124 18.16 1.0
exclusive interval of codano

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
exclusive list of codano

Description: To select messages that do not contain one (or several) given fault
number(s).
Type: DP
Release: V12
executableSoftware
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
executableSoftwareId
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.
Type: Id
Release: V13
411-9001-124 18.16 1.0 Page 193 of 524
executableSoftwareName
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
extended cell Class 2

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.
Page 194 of 524 411-9001-124 18.16 1.0
extendedTimingAdvanceWindow
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 BDA
The 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 and no build BDA
is possible without a valid license.
Object: bts
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.
external alarm configuration Class 2

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.
Number of
protected external
BTS Type of board 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.
411-9001-124 18.16 1.0 Page 195 of 524
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
external battery cabinet Class 2

Description: Presence or absence of the optional equipment "ancillary battery cabi-
net" in S8000 Outdoor.
Value range: [Present / Absent]
Type: DP
Release: V9
externalTime
Description: Current OMC-R agent date and time.
(411-9001-130).
Object: md
Type: DP
Page 196 of 524 411-9001-124 18.16 1.0
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.
extUtbfNoData Class 3
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
2.7. F
facchPowerOffset Class 2
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
Family
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
411-9001-124 18.16 1.0 Page 197 of 524
Observed object: bts
Observation real A interface, synthetic

time (ORT)
Observation fast A interface, OMC interface Releases of communications in signaling
statistic (OFS) phase, Channel mode, ASCI, NONE, BSC 3G, synthetic
Observed object: bts
Observation real SDCCH allocations, Intra-bss handovers, Inter-bss handovers, TCH

time (ORT) allocations, Establishment, Global handovers
Observation fast SDCCH allocations, TCH allocations, Channel mode, Inter-bss
statistic (OFS) 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
Observed object: transceiverZone
Observation real SDCCH allocations on TrZone TCH allocations on TrZone

time (ORT)
Observation fast SDCCH allocations on TrZone, TCH allocations on TrZone, Layer One
statistic (OFS) Management on TrZone, GPRS on TrZone, AMR on TrZone, EDGE,
WPS
Observed object: transceiverEquipment
Observation real ----------------------

time (ORT)
Observation fast ----------------------
statistic (OFS)
Observed object: btsSiteManager

time (ORT)
Observation fast BSC 3G - Abis Level 1
statistic (OFS)
Observed object: pcmCircuit

time (ORT)
Observation fast PCM/synthetic
statistic (OFS)
Page 198 of 524 411-9001-124 18.16 1.0
Observed object: adjacentCellHandOver

time (ORT)
Observation fast Neighbor cells, AMR
statistic (OFS)
Observed object: omu

time (ORT)
Observation fast BSC 3G
statistic (OFS)
Observed object: tmu

time (ORT)
statistic (OFS)
Observed object: cc

time (ORT)
statistic (OFS)
Observed object: cem

time (ORT)
statistic (OFS)
Observed object: pcmPort

time (ORT)
Observation fast BSC 3G - PcmPort
statistic (OFS)
Observed object: signalingLink

time (ORT)
statistic (OFS)
411-9001-124 18.16 1.0 Page 199 of 524
Observed object: channel

time (ORT)
statistic (OFS)
faultNumber
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
fDDARFCN Class 3
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.
fDDMultiratReporting Class 3
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.
Page 200 of 524 411-9001-124 18.16 1.0
Type: DP
Checks:
Release: V17
fDDReportingThreshold Class 3
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)
Default value: Never
Type: DP
Checks:
Release: V17
fDDReportingThreshold2 Class 3
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.
fERThreshold1 Class 3
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
411-9001-124 18.16 1.0 Page 201 of 524
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
Type: DP
The 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
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
Page 202 of 524 411-9001-124 18.16 1.0
Default value: 0
Type: DP
Checks: • [C/M]: Following rule applies: fERThreshold1 <= fERThreshold2 <=
The purpose of this semantic check is to check coherency between FER

thresholds.
Release: V15
fhsRef Class 2
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.
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.
filteredTrafficCoefficient Class 3
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
411-9001-124 18.16 1.0 Page 203 of 524
Type: DP
Feature: AMR based on traffic
Release: V15
floor
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
flowControlMaxDelay
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
flowControlMaxRate
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
fnOffset class 2
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
Page 204 of 524 411-9001-124 18.16 1.0
Type: DP
Release: V15
forced handover algo Class 3

Description: Minimum signal strength level received by the mobiles to be granted ac-
cess to a neighbor cell in case of forced handover.
Type: DP
Release: V9
frAmrPriority Class 2
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
frequencyHoppingSystem
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
411-9001-124 18.16 1.0 Page 205 of 524
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
• [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).
frPowerControlTargetMode Class 3
Description: This attribute defines the target codec mode for AMR FR power control.
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
frPowerControlTargetModeDl Class 3
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
Type: DP
Release: V16
Page 206 of 524 411-9001-124 18.16 1.0
ftpUserPassword
Description: Password of the 'comu' user for connecting to the BSC through FTP.
Value range: 0 to 128 symbols’
Default value: null/empty string
Feature: Linux x86 platform installation and Converged OAM
Type: DI
Release: V18 P&C5
Note: • This parameter is available only for Linux x86 platform installation
and Converged OAM feature.
Checks • [M]: This parameter can be modified, when bscMdInterface object is
locked.
fullDlKa Class 3
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
fullHRCellLoadEnd Class 3
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
411-9001-124 18.16 1.0 Page 207 of 524
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:
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-
• 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
fullHRCellLoadStart Class 3
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:

Page 208 of 524 411-9001-124 18.16 1.0
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-
• fullHRCellLoadStart > fullHRCellLoadEnd.
• [C/M]: If the value of the hrCellLoadStart parameter is different from

100, it means that ABOT is activated and AMR maximization is not ac-
• 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
2.8. G
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.16 1.0 Page 209 of 524
geographical coordinates
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.
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: pcu, pcusn
Type: DI
Release: V12
globalInterBscNaccActivation
Description: This parameter serves as a flag for activation or deactivation of NACC
inter BSC/inter PCUSN with RIM feature.
Class 3
Value range: Disabled=0, Enabled=1
Object: PCU
Feature: NACC inter BSC/inter PCUSN with RIM feature
Type: DP
Release: V18 P&C5
Page 210 of 524 411-9001-124 18.16 1.0

Checks: • The globalInterBscNaccActivation parameter can not be set to
"enable", if the naccInterBscIntraPcusnActivation parameter
value is "disabled".
• Before modifying the naccInterBscIntraPcusnActivation pa-

rameter value, verify that globalInterBscNaccActivation param-
eter value is "disabled".
gprsAvgParam Class 3
Description: This parameter is composed of the following attributes:
• nAvgI
• nAvgT
• nAvgW
Refer to these entries in this dictionary.

Release: V12
gprsCellActivation Class 3
Description: This is a Flag used to activate the GPRS at cell level.
Object: bts
Type: DP
Release: V12
gprsNetworkModeOperation Class 3
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)
411-9001-124 18.16 1.0 Page 211 of 524
Type: DP
Release: V15
gprsPcuCrossConnectList Class 2
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
gprsNetworkModeOperation Class 3
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
gprsPcuCrossConnectList Class 2
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]
Page 212 of 524 411-9001-124 18.16 1.0
Feature: PCUSN - more than 12 Agprs PCMs per BSC (18749)

Release: V12
gprsPcuLockExtendedConf Class 2
• dynamicAgprsAllowed
• agprsTSharingProtection
Refer to these entries in this Dictionary.

Default value: [disabled / 0]
Release: V12
gprsPermittedAccess Class 3
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
gprsPreemption Class 3
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
Feature: GPRS (TF1121 - V12)
Type: DP
Release: V12
411-9001-124 18.16 1.0 Page 213 of 524
gprsPreemptionForHR Class 3
Description: Activation of PDTCH pre-emption for HR channel
Object: bsc
Default value: 0 (disabled)
Recommended 1 (enabled)
value:
Type: DP
Release: V17
gprsPreemptionProtection Class 3
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
gprsPriority Class 2 (gprsTranscvLockExtendedConf)

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
gprsState
Description: Reserved for future use.
Object: bts (cell)
Type: DD
Release: V15
Page 214 of 524 411-9001-124 18.16 1.0
gprsState
Object: transceiver
Type: DD
Release: V15
gsmPriority
Description: Used for the inter-RAT cell reselection algorithm based on priority. It
gives the GSM priority for serving cell.
Value range (0, 1, 2, 3, 4, 5, 6, 7)
Object: bts
Type: DP
Checks The GSM priority value must be different from all LTE priority values and
from all 3G priority values.
Perform the following checks on the bts object:
• "The gsmPrirority parameter value must be different from ltePriority
parameter value for each lteAdjacentCellReselection.
• "The gsmPrirority parameter value must be different from 3Gpriority

value from 3GReselection ARFCN parameter.
• "The gsmPrirority parameter value must be different from

default3Gpriority value.
Default value 0
Class 3
Release: V18 P&C4
gsmToLteReselection
Description: Used to activate or deactivate the GSM to LTE cell reselection feature
Value range: disabled (0)/enabled (1)
Object: Bts
Class 3
411-9001-124 18.16 1.0 Page 215 of 524
Check • Activation of GSM to LTE cell reselection requires the corresponding

RTU. For more information, see GSM BSS Fundamentals Operating
Principles (411-9001-007)
• If gsmToLteReselection parameter is enabled and

3GReselectionOnPriority is disabled, the ARFCN parameter from
3GReselection ARFCN structure should not be present .
• gsmToLteReselection being active is forbidden when no 4G neighbor

cells are defined.
– Set gsmToLteReselection=enabled is forbidden (in on-line only) if

no lteAdjacentCellReselection is created
– Create bts with gsmToLteReselection=enabled is forbidden (in on-

line only) (just because no lteAdjacentCellReselection created
yet)
– Delete of last lteAdjacentCellReselection is forbidden (in on-line

only) if gsmToLteReselection=enabled
– Build BDA is forbidden if gsmToLteReselection=enabled and no

lteAdjacentCellReselection is created
Type: DP
Release: V18
gsmTo3GReselection
Description: "gsmtoUMTSReselection" parameter renamed to
"gsmto3GReselection". gsmTo3GRe selection is composed of 5 sub-
parameters:
• 3GTechnology
• 3GSearchLevel
• 3GReselectionOffset
• 3GAccessMinLevel
• 3GAccessMinLevelOffset
• 3GReselectionThreshold
• 3GReselection ARFCN
– ARFCN
– 3Gpriority
– threshold3Ghigh
– threshold3Glow
– 3GQRxLevMin
Page 216 of 524 411-9001-124 18.16 1.0
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
gsmToUMTSServiceHo Class 3
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 takes
precedence over the MSC value)
Object: bsc
Default value: 3
Type: DP
Release: V17
This parameter is optional.
gsmToUMTSHoEnhancement Class 3
Description: Used to enable or disable the GSM to UMTS hand-over enhancement
feature
Value range: disabled (0) / enabled (1)
Object: bsc
Default value: disabled (0)
Type: DP
411-9001-124 18.16 1.0 Page 217 of 524
Release: V18 P&C4

GsmUmtsCombBcchTeiVal Class 2
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
2.9. H
handOver from signalling channel Class 3

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.
handOverControl
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.
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.
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.
Page 218 of 524 411-9001-124 18.16 1.0
hardware configuration Class 2

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/2
900 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
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 unlock
transceiverEquipment 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 case
of BTS different from BTS 6000 or BTS 18000 (btsModel = 910, 911,
900, 901), this
checks at unlock transceiverEquipment that
its Hardware Configuration is different from
Rm, 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 same
RM.
• [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 other
unlocked 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
411-9001-124 18.16 1.0 Page 219 of 524
hardwareRef Class 2
Description: Hardware reference of a site BCF. Check BSS upgrade file.
Type: DP
hardwareRef Class 2
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
hexa text
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 modified
by 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
highSpeedUplinkDistortionRemoval
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 BTS
Object: bts
Feature: GSM-R V18.0. Customer specific
Type: DP
Release: V18.0 P&C3
Page 220 of 524 411-9001-124 18.16 1.0
highSpeedUplinkDistortionRemovalOnPacketData
Description: This parameter is used to control the high speed uplink distortion remov-
al feature on packet data; when enabled, the BTS removes the uplink
distortion caused by high speed mobiles on (E-)GPRS.
Value range: [disabled (value 0)/ enabled(value 1)]
Object: bts
Class 2
Checks The activation of HSUDR on packet Data requires the corresponding
RTU. For more information see GSM BSS Fundamentals Operating
Principles (411-9001-007).
Feature: GSM-R V18.0. Customer specific
Type: DP
Release: V18.0 P&C4
hoMargin Class 3
Description: A margin to use for PBGT handovers to avoid subsequent
handover, in PBGT formula.
Default value: 4
Type: DP
hoMarginAMR 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
hoMarginAMRUTRAN Class 3
Description: Margin to be used for intercell quality handover to UMTS for AMR calls
Value range: -63...63
411-9001-124 18.16 1.0 Page 221 of 524
Default value: 63
Type: DP
Checks:
Release: V17
hoMarginBeg Class 3
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 hoMargin≤hoMar-
gin+ hoMarginBeg or hoMarginBeg ≥ 0
This parameter is not available for DCU2.
Release V11
hoMarginDist Class 3
Description: Margin to be used for Distance Handovers.
Default value: -24 dB
Type: DP
Release: V8
hoMarginDistUTRAN 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
Page 222 of 524 411-9001-124 18.16 1.0
hoMarginRxLev Class 3
Description: Margin to be used for signal strength Handovers.
Type: DP
Release: V8
hoMarginRxQual Class 3
Description: The margin is used for Signal Quality Handovers.
Type: DP
Release: V8
hoMarginTiering Class 3
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
hoMarginRxLevUTRAN Class 3
Description: Margin to be used for signal strength handover to UMTS
Default value: 63
Type: DP
Checks:
411-9001-124 18.16 1.0 Page 223 of 524
Release: V17
hoMarginRxQualUTRAN Class 3
Description: Margin to be used for signal quality handover to UMTS
Default value: 63
Type: DP
Checks:
Release: V17
hoMarginTrafficOffset Class 3
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.
hoMarginTrafficOffsetUTRAN Class 3
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
Checks:
Release: V17
Page 224 of 524 411-9001-124 18.16 1.0
hoMarginUTRAN Class 3
Description: Margin to be used for PBGT handover to UMTS
Default value: 63
Type: DP
Checks:
Release: V17
hoPingpongCombination Class 3
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
hoPingpongCombinationUTRAN 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.
411-9001-124 18.16 1.0 Page 225 of 524
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
hoPingpongTimeRejection Class 3
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 message
is ignored.
Value range: [0 to 60] s
Feature: General protection against ping-pong handovers (TF821-V12).
Default value: [30 sec]
Release: V12
hoPingpongTimeRejectionUTRAN Class 3
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
hoRejectionTimeOverloadUTRAN Class 3
Description: Time before trying a new handover attempt toward an overloaded
UMTS cell
Value range: 0 ... 60 seconds (0 means immediately)
Page 226 of 524 411-9001-124 18.16 1.0
Object: bsc
Default value: 30s
Type: DP
Checks:
Release: V17
Note: This parameters is only available for BSC 3000.
hoppingSequenceNumber Class 2
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 is
referenced by a channel object (fhsRef
attribute defined), the parent bsc object is
unlocked and the associated bts object is
locked.
hoSecondBestCellConfiguration Class 3
Description: Number of neighbor cells in which the BSC immediately
attempts 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
hoTraffic Class 3
Description: Whether handovers for traffic reasons at bsc level are allowed.
Object: bsc
411-9001-124 18.16 1.0 Page 227 of 524
Type: DP
Release: V12
Note: Enabling this parameter allows the related BTSs with DCU4 or DRX
transceiver architecture handle handovers for traffic reasons.
hoTraffic 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.
hrAmrPriority Class 2
Description: This attribute defines the AMR HR priority of a TDMA.
This attribute can be modified only if the corresponding ’bts’ object in-
stance is locked (objectMustBeLockedError).
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
Object: transceiver
Default value: 0
Type: DP
Release: V14
hrCellLoadEnd Class 3
Description: This attribute defines the cell load threshold used for AMR FR/HR deci-
sion. This attribute is modified by the Manager.
This attribute can only be modified if the ’bts’ object instance is unlocked.
Object: bts
Default value: 0
Page 228 of 524 411-9001-124 18.16 1.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:
• [C/M]: If the value of the hrCellLoadStart parameter is equal to 100
and the value of the fullHRCellLoa
dStart parameter is different from 100, it means that ABOT is not acti-
vated and AMR maximization is activated. Then a semantic control
fullHRCellLoadStart > fullHRCellLoadEnd.
hrCellLoadEnd Class 3
Checks: • [C/M]: If the value of the hrCellLoadStart parameter is different from
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
hrCellLoadStart Class 3
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
• fullHRCellLoadStart > fullHRCellLoadEnd >
hrCellLoadEnd
• [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 activated. Then a semantic control checks the fol-
lowing:
fullHRCellLoadStart > fullHRCellLoadEnd.
411-9001-124 18.16 1.0 Page 229 of 524
hrCellLoadStart Class 3
Checks: • [C/M]: If the value of the hrCellLoadStart parameter is different from
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
hrPowerControlTargetMode Class 3
Description: This attribute defines the target codec mode for AMR HR
power control.
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
hrPowerControlTargetModeDl Class 3
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
hsaPcmList Class 3
Description: List of pcmCircuit object instances connected to a HSA.
Page 230 of 524 411-9001-124 18.16 1.0
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
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.
and the A, A _Lb and Lb’ referenced PcmCircuits are connected to port
6 through port 27.
hsaPcmList Class 3
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
411-9001-124 18.16 1.0 Page 231 of 524
hsaRc
Description: The High Speed Access Resource Complex module, which provides the
optical interface for the OC3/STM1 interfaces.
Object: hsaRc
Type: DP
hysteresisPrio
Description: Gives the hysteresis used in the priority reselection algorithm.
Value range: (- infinity, 5 , 4 , 3 )
Object: bts
Default value -infinity
Class 3
Type: DP
Release V18 P&C4
2.10. I
identifier
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
identifier
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
Page 232 of 524 411-9001-124 18.16 1.0
identifier
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 the
Dictionary where the name formats are explained.
Value range: [BSxabvcdefgh]
Object: software-bsc - Display markers
Type: DD
identifier
Description: Identifier of a short message. It allows MSs to identify the short message
and discard it if already received.
Type: DD
iem
Description: The Interface Electronic Module, is part of the LSA RC (Low Speed Ac-
cess Resource Complex) module.
Object: iem
Type: DP
Note: V13
iemId
Description: Identifier of the ’iem’ object class. This identifier is allocated by the MD-
Object: iem
Type: DP
Release: V13
411-9001-124 18.16 1.0 Page 233 of 524
iMSIAttachDetach Class 2
Description: Whether MS attachment/detachment is allowed. Allowing enables the
system to take into account temporary MS absence to prevent unsuc-
cessful call attempts.
Object: bts
Default value: allowed
Type: DP
in
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
inactivity timeout
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.
inclusive interval of codano

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.
Value range: [0 to 65535 - 0 to 65535]
Type: DP
Release: V12
Page 234 of 524 411-9001-124 18.16 1.0
inclusive list of codano

Description: To select messages according to their fault number. The filter can con-
tain one (or several) fault number(s).
Type: DP
Release: V12
incomingHandOver Class 3
Description: Whether incoming handovers are allowed in a cell.
Type: DP
inhibitRequest
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).
inId
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
411-9001-124 18.16 1.0 Page 235 of 524
initialMCSDL Class 3
Description: Initial MCS in the DL direction.. It is selected by the PCU for the
initial DL-LA-CommandedMCS. Note the backhaul constraints
can reduce the MCS.
Value range: "MCS1" (value 1) "MCS2" (value 2)
"MCS3" (value 3) "MCS4" (value 4)
"MCS7" (value 7) "MCS8" (value 8) "MCS9" (value 9)
Default value: MCS2
Object: transceiver
Default value: MCS2
Type: DP
Release: V15
Note: MCS5 is the recommended value. If a cell with a low radio
quality is experiencing a high BLER in MCS5, it is then
recommended to use MCS2 or MCS3.
Note: In V18.0 P&C5 release, with the implementation of EDGE
Family C MCS-1 & 4 implementation feature, this parameter
modified to accept MCS1 and MCS4 as input.
initialMCSUL Class 3
Description: Initial MCS in the UL direction. It is selected by the PCU for the
initial UL-LA-CommandedMCS. Note the backhaul constraints
will reduce the MCS.
Value range: "MCS1" (value 1) "MCS2" (value 2)
"MCS7" (value 7) "MCS8" (value 8) "MCS9" (value 9)
Default value: MCS2
Object: transceiver
Default value: MCS2
Type: DP
Release: V15
Note In V18.0 P&C5 release, with the implementation of EDGE Family
C MCS-1 & 4 implementation feature, this parameter modified to
accept MCS1 and MCS4 as input.
Page 236 of 524 411-9001-124 18.16 1.0
interBscDirectedRetry Class 3
Description: Whether inter-bss directed retry handovers are allowed in a
BSS.
Object: bsc
Type: DP
Release: V9
Note: Queueing must also be activated at BSC level.
interBscDirectedRetryFromCell Class 3
Description: Whether inter-bss directed retry handovers are allowed in a cell.
Object: bts
Type: DP
Release: V9
interCellHOExtPriority Class 3
Description: Index in the allocPriorityTable defines the processing priority of
incoming inter-bss handovers in a cell.
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
Default value: 17
Type: DP
411-9001-124 18.16 1.0 Page 237 of 524
interCellHOIntPriority Class 3
Description: Index in the allocPriorityTable defines the processing priority of
incoming intra-bss handovers in a cell.
This priority is always used, whether radio resource allocation

queueing is authorized in the BSS or not.
Object: bts
Default value: 17
Type: DP
interferenceType Class 3
Description: Type of interference created by neighbor cell.
Value range: [notApplicable / adjacent / coChannel]
Default value: notApplicable
Type: DP
Release V12
interferenceMatrixRunningOnBsc
Description: Mediation of interferenceMatrixRunning attribute.
Value range: [yes (if at least one cell below BSC with the parameter is equal to “yes”
/ no (if no cell below BSC with the interferenceMatrixRunningOnBts
parameter is equal to “no”]
Object: bts
Feature: Switch Interference Matrix (16411)
Default value: 0
Type: DD
Page 238 of 524 411-9001-124 18.16 1.0
Note: This parameter is optional and read-only. It is applicable to BSC

3000 only. It is not present in CREATE or SET commands. This flag is
displayed at the OMC-R using the Get command.
Checks • [C/M]:
• This parameter checks the callDrop Activation and Distributio-
nActivation parameters.
• The OMC-R prevents a simultaneous activation of the call

dropped analysis and the switch interference matrix. The
IM_FREQUENCIES_MEASUREMENT TGE is prohibited on
the bsc that includes at least one cell with callDropActivation
parameter set to enabled. In this case, the following error mes-
sage is displayed: ”Interference Matrix cannot be launched
on a BSC performing Call Drop Analysis”.
• This check is performed when launching the interference matrix

(IM).
• Vice versa, when activating the dropped call analysis on a cell,

a control is run at the OMC-R. If in a BSC, the interferenceMa-
trixRunningOnBts parameter in at least one cell is still set to
”yes”, then the callDropActivation parameter cannot be set to
enable.
• The OMC-R prevents a simultaneous activation of measure-

ment distributions and the switch interference matrix. The
IM_FREQUENCIES_MEASUREMENT TGE is prohibited on
the bts that has the distributionActivation parameter set to
enabled. In this case, the following error message is dis-
played:”Interference Matrix cannot be launched on a cell per-
forming Measurement Distributions”.
• This check is performed when launching the Interference Matrix.
• Vice versa, when activating Measurement Distributions on a

cell, the OMC-R checks for the interferenceMatrixRunningOn-
Bts flag. If the cell is still running with interference matrix mea-
surements, the distributionActivation parameter cannot be set
to enable.
• C/M]: Bts shall not be deleted while IM is running. Checks that

interferenceMatrixRunningOnB sc is set to ”no” prior to deleting a
bts.
• C/M]: BCCH and BSIC values shall not be changed while IM is
running. If the interferenceMatrixRunningOnBts parameter is set
to ”yes” for one cell, the check prevents the setting of BCCH, BCC
and NCC parameters on bts and adjacentCellHandover objects
• C/M]: Neighboring cannot be changed while IM is running. If the

interferenceMatrixRunningOnBts parameter is set to “yes” for one
cell, the check prevents the creation or deletion of one adjacent-
CellHandover object.
411-9001-124 18.16 1.0 Page 239 of 524
interferenceMatrixRunningOnBts
Description: Mediation of interferenceMatrixRunning attribute.
Value range: [notApplicable / adjacent / coChannel]:
[0 / 1]
• 0 interferenceMatrixOnBts is not running.
• 1 interferenceMatrixOnBts is running.
Object: bts
Feature: Switch Interference Matrix (16411)
Default value: 0
Type: DD
Note: This parameter is optional and read-only. It is applicable to BSC
3000 only. It is not present in CREATE or SET commands. This
flag is displayed at the OMC-R using the Get command.
Checks: • [C/M]:
• This parameter checks the callDropActivation and
DistributionActivation parameters.
• The OMC-R prevents a simultaneous activation of
the call dropped analysis and the switch interfer-
ence matrix. The
IM_FREQUENCIES_MEASUREMENT TGE is pro-
hibited on the bsc that includes at least one cell with
callDropActivation parameter set to enabled. In this
case, the following error message is displayed: ”In-
terference Matrix cannot be launched on a BSC
performing Call Drop Analysis”.
• This check is performed when launching the inter-
ference matrix (IM).
• Vice versa, when activating the dropped call analy-
sis on a cell, a control is run at the OMC-R. If in a
BSC, the interferenceMatrixRunningOnBts param-
eter in at least one cell is still set to ”yes”, then the
callDropActivation parameter cannot be set to en-
able.
Page 240 of 524 411-9001-124 18.16 1.0
Checks • The OMC-R prevents a simultaneous activation of

(contd....):
measurement distributions and the switch interfer-
ence matrix. The
IM_FREQUENCIES_MEASUREMENT TGE is pro-
hibited on the bts that has the distributionActivation
parameter set to enabled. In this case, the following
error message is displayed: ”Interference Matrix
cannot be launched on a cell performing Measure-
ment Distributions”.
• This check is performed when launching the inter-
ference matrix (IM).
• Vice versa, when activating Measurement Distribu-
tions on a cell, the OMC-R checks for the interfer-
enceMatrixRunningOnBts flag. If the cell is still
running with interference matrix measurements, the
distributionActivation parameter cannot be set to
enable.
• [C/M]: Bts shall not be deleted while IM is running. Checks that
interferenceMatrixRunningOnBsc is set to ”no” prior to
deleting a bts.
• [C/M]: BCCH and BSIC values shall not be changed while IM is
running. If the interferenceMatrixRunningOnBts parame-
ter is set to ”yes” for one cell, the check prevents the set-
ting of BCCH, BCC and NCC parameters on bts and
adjacentCellHandover objects.
• [C/M]: Neighboring cannot be changed while IM is running. If the
interferenceMatrixRunningOnBts parameter is set to
“yes” for one cell, the check prevents the creation or de-
letion of one adjacentCellHandover object.
• [C/M]: Cannot create or delete an instance of adjace ntCellU-
TRAN and cannot change fDDARFCN or scramblingCode
parameter values if parameter interferenceMatrixRun-
ningOnBts is equal to yes. The purpose of this check is to
forbid UTRAN neighbour cell creation or deletion or UMTS
frequency plan change if Interference Matrix feature is ac-
tivated on the BSC.
interferer cancel algo usage Class 2

Description: Correlation ratio of the input signals received from the normal and diver-
sity antennas. This ratio enables to adapt the SPU software (the inter-
ferer cancellation algorithm) to the propagation conditions. Correlation
ratio = 0 means that the interferer cancellation algorithm is inactive.
Value range: [0 to 100]%
Object: bts
Default value: 0
Type: DP
Release: V10
411-9001-124 18.16 1.0 Page 241 of 524
interOmuEtherlinkOper
Description: Operational state of the inner OMU Ethernet link.
This attribute is dynamically managed by the BSS.
Value changes are not notified to the manager.
ISO operational state
This attribute is relevant for the BSC 3000.

Object: controlNode
Type: DD
Release: V13
intraCell Class 3
Description: Whether intra-bts handovers on TCH are allowed in a cell for interfer-
ence reasons or Cell Tiering reasons.
Value range: [cellTieringHandover/ intraCellHandover / handoverNotAll owed]
• cellTieringHandover: the intra-bts handovers are allowed for Cell-

Tiering reason
• intraCellHandover: the intra-bts handovers are allowed for inter-
ference reason
• handoverNotAllowed: the intra bts handovers are not allowed
Default value: handoverNotAllowed
Type: DP
intraBscDirectedRetry Class 3
Description: Whether intra-bss directed retry handovers are allowed in a BSS.
Object: bsc
Type: DP
Release: V9
Page 242 of 524 411-9001-124 18.16 1.0
intraBscDirectedRetryFromCell Class 3
Description: Whether intra-bss directed retry handovers are allowed in a cell.
Object: bts
Type: DP
Release: V9
intraCellHOIntPriority Class 3
an intra-bts handover in a cell.
This priority is always used, whether radio resource allocation queueing

is authorized in the BSS or not.
Object: bts
Default value: 17
Type: DP
intraCellQueueing Class 3
Description: Whether intra-bts handover requests are queued for a cell. This param-
eter is significant only when queuing radio resource allocation requests
is allowed in the BSS.
Refer to the bscQueueingOption entry in the Dictionary.

Object: bts
Type: DP
intraCellSDCCH Class 3
Description: Whether intra-bts handovers on SDCCH are authorized in a cell for in-
terference reasons.
411-9001-124 18.16 1.0 Page 243 of 524
Type: DP
Release: V8
iom
Description: The Interface Electronic Module, is part of the HSA RC (High Speed Ac-
cess Resource Complex) module.
Object: iom
Type: DP
Note: It is possible for this parameter to take on an infinite value.
• If so, it the time will not expire and there will be no automatic log-
out procedure.
IP@ of IBOS connected to IPM

Description: Defines the IP address of the IBOS connected to the IPM/RIPM/IPM-
USER/RIPM-USER.
Object: ipm
Type: DD
Note: V18
IPM IP@
Description: Defines the IP address of the IPM/RIPM/IPM-USER/ RIPM-USER.
Object: ipm
Type: DD
Note: V18
ipAggregateEthernetPortMonitored
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
Page 244 of 524 411-9001-124 18.16 1.0
Default value: 0
Release: V18.0
ipAggregateTraffic_TosDscp Class 3
Description: Defines the DSCP value that the BSC must set at the Layer 3 level for
the traffic on the Aggregate port. Corresponds to the 6 higher bits in the
"Type Of Service" 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 reliability
The chosen value must be compliant with what is available at the pro-
vider network side.
Value range: [0....63]
Object: ipgRc
Default value: 10
Recommended 10, 12, 14, 18, 20, 22, 26, 28, 30, 34, 36, 38
value:
Type: DP
Note: V18
ipAggregateTraffic_userPriority Class 3
Description: Defines the priority that the BSC must set at the Layer 2 level for the IP
traffic on the Aggregate interface. Meaningful only if VLAN tags are used
on the Aggregate interface. General recommendations are:
• 0: best effort (not recommended)

• 1-4: business critical data
• 5-6: delay sensitive data
• 7: network control information
vider network side.
Object: ipgRc
Default value: 4
Recommended 1, 2, 3, 4
value:
411-9001-124 18.16 1.0 Page 245 of 524
Type: DP
Note: V18
ipCompressionActivation 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
ipCompressionDepth Class 2
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 40
value:
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.
Page 246 of 524 411-9001-124 18.16 1.0
ipCRPnChannel_TosDscp Class 3
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
Default value: 46 (DSCP 46)
Recommended 46 (Expedited Forwarding PHB)
value:
Type: DP
Release: V18.0
ipCRPnChannel_userPriority Class 3
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:
• 7: network control information (not to use)
vider network side.
Object: ipgRc
Default value: 6
411-9001-124 18.16 1.0 Page 247 of 524
Recommended 5, 6
value:
Type: DP
Release: V18.0
ipDefaultGateway Class 3
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
value:
Type: DP
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)
ipDHCPServerList Class 3
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
Page 248 of 524 411-9001-124 18.16 1.0
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:
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)
ipgPcmList 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

411-9001-124 18.16 1.0 Page 249 of 524
ipgRc Reference
Description: Identifier of the ipgRc object.
Object: igm
Type: DP
Release: V18.0
ipIBOSEthernetPortMonitored Class 3
Description: Defines if some equipments are connected (directly or
through 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
ipIBOSEthernetPortUsed Class 3
Description: Defines if the IBOS is connected directly or through gateways on the
IBOS 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 used / Used]
Object: ipgRc
Default value: Not used
Type: DP
Note: V18
Page 250 of 524 411-9001-124 18.16 1.0
ipIBOSTraffic_TosDscp Class 3
the traffic on the IBOS port. Corresponds to the 6 higher bits in the "Type
Of Service" 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:

• 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 reliability
vider network side.
Object: ipgRc
Default value: 10
Recommended 10, 12, 14, 18, 20, 22, 26, 28, 30, 34, 36, 38
value:
Type: DP
Note: V18
ipIBOSTraffic_userPriority Class 3
Description: Defines the priority that the BSC must set at the Layer 2 level for the IP-
traffic on the IBOS interface. Meaningful only if VLAN tags are used on
the IBOS.
General recommendations are:

vider network side.
Object: ipgRc
Default value: 4
value:
411-9001-124 18.16 1.0 Page 251 of 524
Type: DP
Note: V18
ipIBOSTraffic_TosDscp Class 3
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.

packets (voice)
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 10, 12, 14, 18, 20, 22, 26, 28, 30, 34, 36, 38
value:
Type: DP
Release: V18.0
ipIBOSTraffic_userPriority Class 3
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:
The chosen value must be compliant with what is available at the

provider network side.
Object: ipgRc
Page 252 of 524 411-9001-124 18.16 1.0
Default value: 4
value:
Type: DP
Release: V18.0
ipLmuMatrix Class 3 (BSC 3000)

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
IPM IP subnet mask

Description: Mandatory if “DHCP use” = NO
Not applicable else.
Object: ipm
Default value: 0
Type: DD
Note: PC2
ipAggregateEthernetPortUsed Class 3
Description: Defines if the aggregate equipment are connected directly or through
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 used / Used]
Object: ipgRc
411-9001-124 18.16 1.0 Page 253 of 524
Default value: Not used

Type: DP
Release: V18
ipIpgRcCounterPeriod Class 3
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
bts
Description: Identifier of an ipm object.
Value range: [1]
Object: ipm
Type: Id
Release: V18.0
ipm MAC address Core A Class 3

Description: Defines the primary MAC address of the IPM / IPM-USER for the au-
thentication
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.
Page 254 of 524 411-9001-124 18.16 1.0
ipm MAC address Core B Class 3

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.
ipOtherAbisTraffic_TosDscp Class 3
the other Abis traffic (DSCP, ...).
Corresponds to the 6 higher bits in the "Type Of Service" field in the IP
header and must be compliant with the values defined in RFC2474,
RFC2475, and RFC3260.
•best effort PHB (DSCP 0)
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 reliability
The chosen value must be compliant with what is available at the provid-
er network side.
Object: ipgRc
Default value: 0
Recommended 10, 12, 14, 18, 20, 22, 26, 28, 30, 34, 36, 38
value:
Type: DP
Release: V18
ipOtherAbisTraffic_userPriority Class 3
Description: Defines the priority that the BSC must set at the Layer 2 level for other
traffic on the Abis interface (DSCP...). Meaningful only if VLAN tags are
used on the Abis backhaul. General recommendations are:
The chosen value must be compliant with what is available at the provid-
er network side.
411-9001-124 18.16 1.0 Page 255 of 524

Object: ipgRc
Default value: 0
Type: DP
Release: V18
ipPdvManualSet Class 2
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
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.
ipPdvSelfTuningRange Class 2
Description: If the automatic adjustment is activated, this parameter defines the list
of allowed sets.
Possible values : 1 to 15, with :
Bit0 = #1
Bit1 = #2
Bit2 = #3
Bit3 = #4
Example : 7 means #1, #2 and #3 are allowed.
Default value: 7
Type: DP
Release: V18.0
Checks: • [C/M]: Before changing the ipPdvSelfTuningRange parameter, the
Page 256 of 524 411-9001-124 18.16 1.0
ipPortAddress Class 3
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.
411-9001-124 18.16 1.0 Page 257 of 524
• [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:
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)
ipRedundancyProtocolOnAbisPort Class 3
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: VRRPn
Type: DP
Release: V18.0
ipRedundancyProtocolOnAggregatePort Class 3
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
Page 258 of 524 411-9001-124 18.16 1.0

Type: DP
Release: V18.0
ipRoutingProtocolOnAbisPort Class 3
Description: Defines the protocol used to provide external gateways on the Abis port
with the routing tables known by the ipgRc. It is used by router function
inside the BSC.
Value range: “static” (0)
Object: ipgRc
Default value: 0
Type: DP
Release: V18
Note: Only one value is defined in V18.0: “static”
ipRedundancyProtocolOnIBOSPort Class 3
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
Type: DP
Release: V18.0
ipRoutingProtocolOnAggregatePort Class 3
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.
Object: ipgRc
Default value: 0
Type: DP
Release: V18.0
411-9001-124 18.16 1.0 Page 259 of 524
ipRoutingProtocolOnIBOSPort Class 3
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.
Object: ipgRc
Default value: 0
Type: DP
Release: V18.0
ipRoutingTable Class 3
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"
Object: ipgRc
Type: DP
Release: V18.0
Page 260 of 524 411-9001-124 18.16 1.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 must
belong to one of the subnets declared in the
ipPortIPaddress_VRId_List parameter (all the subnets are known by
applying, for each
line, 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]
— 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 mask
The 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)
ipRTPnChannel_TosDscp Class 3
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.
packets
38): value recommended for packets which need to have a high level of
delivery reliability
vider network side.
Object: ipgRc
Default value: 46
Recommended 46
value:
Type: DP
Release: V18.0
411-9001-124 18.16 1.0 Page 261 of 524
ipRTPnChannel_userPriority Class 3
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:
vider network side.
Object: ipgRc
Default value: 6
Recommended 5, 6
value:
Type: DP
Release: V18.0
IPSEC Payload Class 3

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
ipSelfTuning Class 2
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 0
value:
Type: DP
Release: V18.0
Page 262 of 524 411-9001-124 18.16 1.0
ipServiceChannel_TosDscp
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 at
Layer 3 level for Service Channel on Abis port. When IBOS is connected
on
Abis 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.

Value range: 0..63
Object: ipgRc
Default value: 10 (Assured Forwarding PHB)
Recommended 10, 12, 14, 18, 20, 22, 26, 28, 30, 34, 36, 38
value:
Type: DP
Release: V18.0
ipServiceChannel_userPriority Class 3
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.
vider network side.
Object: ipgRc
Default value: 4
value:
Type: DP
Release: V18.0
411-9001-124 18.16 1.0 Page 263 of 524
ipSynchroPacketPeriod 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 21
value:
Type: DP
Release: V18.0
Checks: • [C/M]: Before changing the ipSy chroPacketPeriod parameter, the
ipSynchroType Class 2
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
value:
Type: DP
Release: V18.0
ipSynchroUplinkActivation Class 2
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 Not activated
value:
Type: DP
Release: V18.0
Checks: • [C/M]: Before changing the ipSynchroUplinkActivation parameter,
the OMC-R checks that the ipm object is locked.
Page 264 of 524 411-9001-124 18.16 1.0
ipTrafficPacketPeriod Class 2
Description: Defines the period between two RTPn IP packets.
Value range: [4]
Unit: ms
Default value: 4
Type: DP
Release: V18.0
Checks: • [C/M]: Before changing the ipTrafficPacketPeriod parameter, the
lteARFCN
Description: Absolute Radio Frequency Channel Number (EARFCN).
Value range: [0 – 65535]
Object: lteAdjacentCellReselection
Type: DP
Release: V18
411-9001-124 18.16 1.0 Page 265 of 524
2.11. J
job
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.
jobResult
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
jokerPerMainTarget Class 3
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
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
Page 266 of 524 411-9001-124 18.16 1.0
2.12. L
label
Description: Label of an archive cartridge.
When a label is set, all information already stored on the
cartridge is lost.
Object: md, omc - Display label
md, omc - Set label
md, omc - Archive
md, omc - Restore
md, omc - Display archive list.
Type: DP
language
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
lapdLink
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
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 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]:
411-9001-124 18.16 1.0 Page 267 of 524
• [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.
lapdLinkOMLRef Class 2
Description: Identifier of the lapdLink object with sapi = OML referenced by the
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 configuration
data).
• [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 ration
attribute value is "disabled", the defined
lapdTerminalNumber is not used.
lapdLinkOMLRef Class 2
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.
lapdLinkRSLRef Class 2
Description: Identifier of the lapdLink object with sapi = RSL referenced by the trans-
ceiverEquipment object.
Page 268 of 524 411-9001-124 18.16 1.0
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-
• [M]: The parent bsc object is unlocked, the parent btsSiteManager ob-
ject and the transceiverEquipment object are locked.
lapdTerminalNumber Class 0
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 SICD8
board [0 to 4] + port number [0 to 7]
Value range: [0 to 7] (BSC type 1)
[0 to 15] (BSC type 2)
[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
• [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-
411-9001-124 18.16 1.0 Page 269 of 524
layer3MsgCyphModComp Class 1
Description: Whether the "Layer 3 message" element is used in the CYPHER MODE
Type: DP
Release: V8
lcsType Class 0
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
level to process
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.
Licenses needed to put object in service

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.
Page 270 of 524 411-9001-124 18.16 1.0
Value range: [0..NNNN] (The range depends on the number of licenses configured,
used in total and on certain objects)
Object: md - Display RM capacity
bsc - Display RM capacity
btsSiteManager - Display RM capacity
Feature: AMR Feature Activation Control
EDGE Feature Activation Control
Release: V17
Licenses used by this object

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.
Release: V17
lightning protection Class 2

Description: Presence or absence of the optional equipment "lightning arrester" in
S8000 Outdoor.
Type: DP
Release: V9
line
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 recorded
command, line no.n corresponds to the last recorded command.
Object: commandFile - Run
Type: DP
411-9001-124 18.16 1.0 Page 271 of 524
locationAreaCode Class 3
Description: Code of a location area of the neighbor cell in the PLMN.
Type: DP
bor cells.
Description: Code of a location area of the neighbor cell in the PLMN.
Class: 3
Type: DP
lection object is enhanced for V18 P&C5 to include the LAC information
through this parameter and the LAC information of every BTS is commu-
nicated to PCU as a part of adjacentcellreseletion list.
bor cells.
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
bor cells.
locationAreaCodeUTRAN Class 3
Description: Location area code (LAC) of the UMTS neighbouring cell for HO
Value range: 0...65535
Default value: N.A.
Page 272 of 524 411-9001-124 18.16 1.0
Type: DP
Release: V17
log
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.
logFullAction
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.
logicalFiberInfo
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.
411-9001-124 18.16 1.0 Page 273 of 524
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
login command type

Description: Select login and user profile
Value range: [login request, server update]
longTbfLossThroughput Class 3
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
longTbfSizeThreshold Class 3
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
Page 274 of 524 411-9001-124 18.16 1.0
lRxLevDLH Class 3
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
lRxLevDLP Class 3
Description: Signal strength threshold in BTS-to-MS direction, below which the pow-
er control function increases power. .
Type: DP
lRxLevULH 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
lRxLevULP Class 3
Description: Signal strength threshold in MS-to-BTS direction, below which the power
control function increases power. It is lower than uRxLevULP.
Type: DP
411-9001-124 18.16 1.0 Page 275 of 524
lRxQualDLH Class 3
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
lRxQualDLP Class 3
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.
lRxQualULH Class 3
Description: Bit error rate threshold in MS-to-BTS direction, above which an inter cell
handover may be triggered.
Feature: Intracell handover enhancements (TF819 - V12)
Type: DP
lRxQualULP Class 3
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
Page 276 of 524 411-9001-124 18.16 1.0
Checks: • [C/M]: lRxQualULP uRxQualULP

Note: The uRxQualULP parameter is ignored when the BTS uses the
advanced "one shot" power control algorithm.
lsaPcmList Class 3
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.
and the A, A _Lb and Lb referenced PcmCircuits are connected to port
5 through port 20.
• [C/M]: A LSA under Transcoder module of T1 type handles 28 PCMs.
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
411-9001-124 18.16 1.0 Page 277 of 524
lsaRc
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
lsaRcId
Description: Identifier of the ’lsaRc’ object class. This identifier is allocated by the MD-
Object: lsaRc
Type: DP
Release: V13
lsaRc Reference
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
lteRxLevMin
Description: Minimum RX level required for cells on the target E-UTRAN frequency
(dBm)
Value range: (-140 , -138 , -136 , …, -80 , -78 )
Default value -140
Type: DP
Class 3
Release: V18 P&C4
Page 278 of 524 411-9001-124 18.16 1.0
lteARFCN
Description: Absolute Radio Frequency Channel Number (EARFCN)
Type: DP
Check The operator has to set this parameter for the creation of lteAdjacent-
CellReselection object. 8 instances are the maximum "lteAdjacentCell-
Reselection" objects which can be created for one cell. For one cell,
lteARFCN parameter value from each lteAdjacentCellReselection in-
stance must be unique.
Class 3
Release: V18 P&C4
ItePriority
Description: Priority of a E-UTRAN frequency layer
Value range: (0, 1, 2, 3, 4, 5, 6, 7) 0-lowest priority, 7-highest
Checks The value of ltePriority parameter for each lteAdjacentCellReselection in
bts object must be different from the Default3Gpriority parameter and
each 3Gpriority value from 3GReselection ARFCN parameter.
Type: DP
Class 3
Release: V18 P&C4
2.13. M
machine name
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.
411-9001-124 18.16 1.0 Page 279 of 524
machine name
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
BTS, BTSSM). All other symbols/characters are prohibied.
mainNetworkBand Class 0
Description: Indicates the main network band.
Object: jobResult
Type: DD
mainNetworkBand Class 0
Description: Indicates the main network band.
Value range: [900/1800/850/1900] network band
Object: bsc
Type: DP
Release: V15
maio Class 2
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
Page 280 of 524 411-9001-124 18.16 1.0
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).
managedObjectClass
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
managedObjectInstance
Description: Identification of an object in the class.
Object: alarmRecord, mdScanReportRecord, observationFileReadyRecord,
Type: DP
manager address type

Description: OMC-R manager address type
Value range: [internal / external]
Type: DP
Checks: • [C/M]: This attribute is not managed by users.
manager addresses
Description: Addresses of the OMC-R manager that receives the messages. They
are provided by the manager.
411-9001-124 18.16 1.0 Page 281 of 524
Type: DP
managerServer
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
manufacturerIntervention
Description: Type of action associated with an alarm criterion in the manufacturer
configuration.
Type: DP
marking type
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
masterBtsSMId class 2
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
Page 282 of 524 411-9001-124 18.16 1.0
max log size

Description: Maximum log size expressed in bytes.
Type: DP
Remark: The attributes of the log objects are not managed by the users.
maxAdjCHOARMPerBts
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
maxBscPerNetwork
Description: Maximum number of BSCs handled by an OMC-R (static OMC-R con-
figuration data).
Value range: [20]
Object: OMC-R
Type: DS
maxBsTransmitPowerInnerZone Class 3
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
maxBtsPerBtsSM
Description: Maximum number of radio cells controlled by a site (static OMC-R con-
figuration data).
Value range: [6 (BTS "conventional") / 4 (others)]
411-9001-124 18.16 1.0 Page 283 of 524
Object: OMC-R
Type: DS
maxBtsPerNetwork
Description: Maximum number of radio cells controlled by an OMC-R (static OMC-R
Value range: [3200]
Object: OMC-R
Type: DS
maxDnTbfP1P2Threshold Class 3
Description: Maximum number of downlink TBF on a P1 TDMA before selection of P2
TDMA.
Object: bts
Default value: 16
Release: V12
maxDnTbfPerTs Class 3
Description: Maximum number of downlink TBF per TDMA on a timeslot basis.
Object: bts
Default value: 8
Type: DP
Release: V12
maxDwAssign Class 3
Description: Maximum number of Immediate Assignment messages per second.
Value range: [1 to 32] blocks
Object: bts
Default value: 8
Type: DP
Page 284 of 524 411-9001-124 18.16 1.0
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.
maxFileSize Class 2
Description: Maximum size of the call path tracing data file in the BSC.
Value range: [30 to 500] kbit/s
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.
maximum acknowledgment time

Description: To select messages acknowledged at that time or before. Absolute time
format entry forms are detailed in GSM OMC-R Commands Reference -
Security, Administration, SMS-CB, and Help menus (411-9001-130).
Type: DP
Checks: • [A]: It is after minimum acknowledgment time when filled in.
maximum alarm number

Description: To select alarms with a number lower than or equal to that one.
Type: DP
Checks: • [A]: It is greater than or equal to minimum alarm number when filled
in.
411-9001-124 18.16 1.0 Page 285 of 524
maximum clear time

Description: To select alarms cleared at that time or before. Absolute time format en-
try forms are detailed in GSM OMC-R Commands Reference - Security,
Administration, SMS-CB, and Help menus (411-9001-130).
Type: DP
Checks: • [A]: It is after minimum clear time when filled in.
maximum event time

Description: To select messages issued at that time or before. Absolute time format
entry forms are detailed in GSM OMC-R Commands Reference - Secu-
rity, Administration, SMS-CB, and Help menus (411-9001-130).
Type: DP
Checks: • [A]: It is after minimum event time when filled in.
maximum MD notification number

Description: To select OMC-R agent notifications with a number lower than or equal
to that one.
Type: DP
Checks: • [A]: It is greater than or equal to minimum MD notification number
when filled in.
maximum OMC notification number

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.
Page 286 of 524 411-9001-124 18.16 1.0
maximum reception time

Description: To select messages received at that time or before.
(411-9001-130).
Type: DP
Checks: • [A]: It is after minimum reception time when filled in.
maxLapdChPerBtsSM
Description: Maximum number of LAPD channels used by a radio site (static OMC-
R configuration data).
Value range: [6]
Object: OMC-R
Type: DS
maxNbrConsMess
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
maxNbOfCells Class 2
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.
411-9001-124 18.16 1.0 Page 287 of 524
maxNbrPDAAssig Class 2 (gprsTranscvLockExtendedConf

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
maxNbrPUDWithoutVchange Class 2 (NN0002Max) gprsTran-

scvLockExtendedConf
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
maxNbrRLCEmptyBlock Class 2 (n3101Max) (gprsTranscv-

LockExtendedConf)
Description: Maximum number of USF where no data is received in the UL direction.
Object: transceiver
Default value: 10
Type: DP
Release: V12
Page 288 of 524 411-9001-124 18.16 1.0
maxNumberRetransmission Class 3
Description: Maximum number of RACH burst retransmissions allowed in a call in
case of non-system response.
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
maxPcmCPerBtsSM
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
maxPcmCPerTranscd
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
maxRACH Class 3
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.
• 0: disabled
• 1..15: enabled
Object: bts
Feature: Broadcast of PSI 13 (Feature 27358)
Default value: 0
Type: DP
Notes: • The recommended value is 1.
• Only applicable for BSC 3000.
Release: V12
411-9001-124 18.16 1.0 Page 289 of 524
maxRowCount
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
maxSigLPerSigLS
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
maxTeiPerLapdCh
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
maxTranscdBPerTranscd
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
maxTranscdPerBsc
Description: Maximum number of remote transcoders linked to a BSC (static OMC-R
Value range: [34 (BSC 3000)
2 (TCU3G)]
Page 290 of 524 411-9001-124 18.16 1.0
Object: OMC-R
Type: DS
maxUpTbfP1P2Threshold Class 3
Description: Maximum number of uplink TBF on a P1 TDMA before selection of P2
TDMA.
Object: bts
Type: DP
Default value: 16
Release: V12
maxUpTbfPerTs Class 3
Description: Maximum number of uplink TBF per TDMA on a timeslot basis.
Object: bts
Type: DP
Default value: 8
Release: V12
measurementBandwidth
Description: IMinimum value of the channel bandwidth of all valid E-UTRAN cells on
the specified EARFCN.
Value range: (6, 15, 25, 50, 75, 100)
Unit NRB
Default value 6
Class 3
Type: DP
Release V18 P&C4
411-9001-124 18.16 1.0 Page 291 of 524
md
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
md notification number
Description: To select OMC-R agent notifications with a given number.
Type: DP
mdArchive
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.
mdConfirm
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.
Page 292 of 524 411-9001-124 18.16 1.0
mdFileName
Description: Name of an observation file containing an elementary report. Refer to
the naming rules to GSM BSS Fundamentals — Operating Principles
(411-9001-007).
Object: mdScanReportRecord
Type: DP
mdGranularityPeriod
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.
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 cases
This note only applies to ODIAG observation.
mdGranularityPeriod
• [15, 30, 60] minutes...... permanent general bsc (GPO-BSC)
• [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: mdScanReportRecord
Type: DP
411-9001-124 18.16 1.0 Page 293 of 524
mdGranularityPeriod
• [15, 30, 60] minutes...... permanent general bsc (GPO-BSC)
• [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
mdId
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.
mdLog
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" (instrument
panel observation) and "logged" otherwise.
Value range: [logged / not logged]
Object: mdScanner
Type DP
Checks: • [M]: This attribute cannot be modified.
mdObjectList
Description: Identification of the observed object. It depends on the type of the de-
fined observation.
mdScannerType mdObjectList
permanent gen- md
eral md
permanent gen- bsc
eral bsc
Page 294 of 524 411-9001-124 18.16 1.0
mdObjectList
fined observation.
mdScannerType mdObjectList
general statistic bsc
(OGS)
fast statistic bsc
(OFS)
performance bsc
monitor
real time (ORT) bsc
temporary sig- bsc & signallingLink
nallingLink*
temporary Abis bsc & btsSiteManager & bts
Interface bts*
diagnostic bsc, bts, signallingLink, hardware transcoder 3G, transcoderEqpt,
(ODIAG) pcmPort, transceiverEqpt & btsSiteManager, pcmCircuit, adjacentCell
* This type only applies to V12 BSCs.
mdObjectList
fined observation.
Object: display xxx report
Type DP
mdObjectList
Description: Identification of the observed object. It depends on the type of observa-
tion defined.
Type: DP
mdScanner
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
411-9001-124 18.16 1.0 Page 295 of 524
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.
mdScannerType
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
mdScannerType
eral manager
Type: DP
mdScannerType
ference / temporary signallingLink / temporary Abis Interface bts / per-
manent general md / permanent general manager]
Object: Load formulae
Type: DP
mdScannerType
eral manager / pcuSN]
Page 296 of 524 411-9001-124 18.16 1.0
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.
mdScannerType
ference / temporary signallingLink / temporary Abis Interface bts / per-
manent general md / permanent general manager / pcuSN]r]
Type: DP
mdStorageDuration
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
mdTransferMode
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
411-9001-124 18.16 1.0 Page 297 of 524
mdWarning
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
MIB version
Description: Appears during creation of executableSoftware object and is an internal
representation of MIB version.
Feature: Flexible OMC-R
Type: DP
Release: V18.0
microCellCaptureTimer Class 3
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").
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.
Page 298 of 524 411-9001-124 18.16 1.0
microCellStability Class 3
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.
minimum acknowledgment time

Description: Selecting messages acknowledged at that time or after.
(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.
minimum alarm number

Description: To select alarms with a number greater than or equal to that one.
Type: DP
Checks: • [A]: It is lower than or equal to maximum alarm number when filled
in.
411-9001-124 18.16 1.0 Page 299 of 524
minimum clear time

Description: To select alarms cleared at that time or after.
(411-9001-130).
Type: DP
Checks: • [A]: It is before maximum clear time when filled in.
minimum event time

Description: To select messages issued at that time or after.
(411-9001-130).
Type DP
Checks: • [A]: It is before maximum event time when filled in.
minimum MD notification number

Description: To select OMC-R agent notifications with a number greater than or equal
to that one.
Type: DP
Checks: • [A]: It is lower than or equal to maximum MD notification number
when filled in.
minimum OMC notification number

Description: To select OMC-R manager notifications with a number greater than or
equal to that one.
Type: DP
Checks: • [A]: It is lower than or equal to maximum OMC notification number
when filled in.
Page 300 of 524 411-9001-124 18.16 1.0
minimum reception time

Description: To select messages received at that time or after.
(411-9001-130).
Type: DP
Checks: • [A]: It is before maximum reception time when filled in.
minNbOfJokersPerConnectedMain Class 3
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: V16
Note: This parameter is mandatory. It is only available for BSC
3000.
minNbOfTDMA Class 2
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.
411-9001-124 18.16 1.0 Page 301 of 524
minNbrGprsTs Class 3
Description: Minimum number of TS dedicated to GPRS in the cell.
Object: bts
Default value: 0
Type: DP
Release: V12
minTimeQualityIntraCellHO Class 3
Description: This attribute defines the minimum time between one intracell HO and
the next quality intracell HO.
stance is unlocked
Default value: 0
Type: DP
Release: V12
minTimeQualityIntraCellHO Class 3
Description: This attribute defines the minimum time between one intracell HO and
the next quality intracell HO.
stance is unlocked
Default value: 0
Type: DP
Release: V14
Note: Applies to a BSC 3000 architecture only.
missDistWt Class 3
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.
Page 302 of 524 411-9001-124 18.16 1.0

Default value: 110
Type: DP
missRxLevWt Class 3
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 by
this 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
missRxQualWt Class 3
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
mms
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
411-9001-124 18.16 1.0 Page 303 of 524
MMS disk scan state

Description: Used to view the status of MMS scan, whether MMS board scan is in
progress or not.
Value range: Scan is in progress / No scan in progress
Object: bsc
Type: DP
Release: V 18 P&C3
mmsId
Description: Identifier of the ’mms’ object class. This identifier is allocated by the MD-
Object: mms
Type: DP
Release: V 13
mmsUsage
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
mobileAllocation Class 2
Description: List of sixty-four frequencies allotted in the network frequency band to a
radio time slot obeying frequency hopping laws.
[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).
Page 304 of 524 411-9001-124 18.16 1.0
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.
mobileCountryCode Class 3
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.
Class: 3
Type: DP
Feature: NACC inter BSC/intra PCUSN feature.
lection object is enhanced for V18 P&C5 to include the MCC information
through this parameter and the MCC information of every BTS is com-
municated to PCU as a part of adjacentcellreseletion list.
bor cells.
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).
411-9001-124 18.16 1.0 Page 305 of 524
Condition: For a GSM-R network: mandatory as the MSC does not manage cell
global identifiers (CGI) for Group Call.
Type: DP
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
bor cells.
mobileCountryCodeUTRAN Class 3
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 and mobileNetworkCodeUTRAN must be
unique among all the instances of the objects adjacentCellUTRAN at-
tached to the same bts.
Release: V17
mobileNetworkCode Class 3
Description: Code of the PLMN in the country.
Type: DP
Checks: • [C]: This code is identical to the mobileNetworkCode attribute of the
bor cells.
Page 306 of 524 411-9001-124 18.16 1.0
Class: 3
Type: DP
lection object is enhanced for V18 P&C5 to include the MNC information
through this parameter and the MNC information of every BTS is com-
municated to PCU as a part of adjacentcellreseletion list.
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
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
bor cells.
mobileNetworkCodeUTRAN Class 3
Description: Mobile network code (MNC) of the UMTS neighbouring cell for HO
411-9001-124 18.16 1.0 Page 307 of 524
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
modeModifyMandatory Class 3
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
monitoredObjectClass
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
monitoredObjectInstance
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.
Page 308 of 524 411-9001-124 18.16 1.0
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
monitoredSpecificProblemsList
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]
Type: DP
month
Description: Identifies the month the observation report was created. Date format en-
try forms are detailed in 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
msBtsDistanceInterCell Class 3
Description: To determine whether inter-bts handovers are allowed in a cell for dis-
tance reasons.
Type: DP
msCapWeightActive Class 2
Description: To specify whether the Weight Fair Allocation algorithm is used or not.
Object: bts
411-9001-124 18.16 1.0 Page 309 of 524

Default value: yes
Type: DP
Release: V12
msLeakRate
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
msPowerClassToggle 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
msRangeMax Class 3
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".
Page 310 of 524 411-9001-124 18.16 1.0
msTxPwrMax Class 3
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. 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)
msTxPwrMax2ndBand Class 2
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:
Release: V12
411-9001-124 18.16 1.0 Page 311 of 524
msTxPwrMaxCCH Class 3
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:
msTxPwrMaxCell Class 3
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:
multi band reporting Class 3

Description: Minimum number of cells multibanding MSs, report their radio measure-
ments in each frequency band.
Page 312 of 524 411-9001-124 18.16 1.0
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
multiple site
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
multipleVocoders Class 1
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
muxNumber Class 3
Description: pcuSN mux identification
Value range: [noMux / oneMux / twoMux]
411-9001-124 18.16 1.0 Page 313 of 524
Object: pcusn
Type: DP
Release: V12
2.14. N
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
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
naccInterBscIntraPcusnActivation Class 3
Description: This parameter serves as a flag for activation or deactivation of NACC
inter BSC/intra PCUSN feature.
Class 3
Value range: Disabled = 0 , Enabled = 1
Page 314 of 524 411-9001-124 18.16 1.0
naccInterBscIntraPcusnActivation Class 3
Object: PCU
Type: DP
Feature: NACCInterBSCIntraPCUSN feature
Release: V18 P&C5
Note: This parameter is available for BSC 3000 only.
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.
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
Default value: 0
Type: DP
Release: V12
411-9001-124 18.16 1.0 Page 315 of 524
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
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 nbOfFrames
ForFER 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
Object: bts
Default value: 3
Type: DP
Release: V8
Page 316 of 524 411-9001-124 18.16 1.0
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
411-9001-124 18.16 1.0 Page 317 of 524
nCHPosition Class2
Description: Defines the number of blocks and position of the first block for NCH.
Value range: [0 block
1 block, first block 0
2 blocks, first block 0
7 blocks, first block 0]
Object: bts
Feature: (GSM-R V12)
Default value: 0 block
Type: DP
Release: V12
Note: nCHPosition - noOfBlocksForAccessGrant relation according to channel-
Type attribute
channelType nCHPosition noOfBlocksFor AccessGrant
mainBCCH 1 block, first block 0 to 6 >= 1
2 blocks, first block 0 to 5 >= 2
7 blocks, first block 0 =7
mainBCCHCo 1 block, first block 0 1 or 2
mbined 1 block, first block 1 = 12
2 blocks, first block 0 = 12
Page 318 of 524 411-9001-124 18.16 1.0
networkColourCode Class 3
Description: Network Colour Code (NCC) value of the AdjacentCellReselection ob-
ject.
Class: 3
Default value: -1
Type: DP
Release: V18 P&C5
Checks: The routingArea, baseColourCode and networkColourCode parameters
of the adjacentCellReselection object should be either all valid or all in-
valid. That means that for an AdjacentCellReselection object, if one of
the routingArea, baseColourCode and networkcolourCode parameters
has a valid value, then the 2 other parameters should also have a valid
value.
The valid values for the networkColourCode parameter are [0 to 7].
Invalid value for this parameter is -1.
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.
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
411-9001-124 18.16 1.0 Page 319 of 524
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.
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.
networkResourceIdentifierLength
Description: This parameter gives the length of the NRI, which the BSS has to extract
from the TMSI to recover the MSC identifier.
Setting this parameter value to 0 deactivates the A Flex - GSM Access
feature.
For more information about NRI, refer GSM BSS Fundamentals -
Operating Principles (411-9001-007).
Class: 0
Default Value: 0
Object: SignallingPoint
Type: DP
Checks: NetworkResourceIdentifier value must be < 2^networkResourceIdentifi-
erLength (on SignallingPoint). The check is done on:
• Create remoteSignalingPoint
• Set remoteSignalingPoint
• Set signallingPoint
Page 320 of 524 411-9001-124 18.16 1.0
networkResourceIdentifierLength
Feature A Flex - GSM Access or Quasi Associated Mode
Release: V 18 P&C5
Note: This parameter is available only for BSC 3000. Also, this parameter will
be available for configuration only if A Flex - GSM Access or Quasi As-
sociated Mode feature is activated.
networkResourceIdentifierList
Description: This parameter denotes the list of 0 to 32 Network Resource Identifiers
(NRIs). The NRI gives the MSC identifier, which the BSC recovers in the
TMSI.
Class: 3
Value range: List of up to 32 elements of integer type (0..1023 on MOD)
Default Value: Empty List
Object: RemoteSignallingPoint
Type: DP
Note: • As more NRIs are added to a remoteSignallingPoint (for MSC) in-
stance, operator has to ensure that the number of SLKs associated
with the remoteSignallingPoint instance are configured accordingly.
Feature A Flex - GSM Access or Quasi Associated Mode
Release: V 18 P&C5
new password 1st try

Description: User’s new password to use in the next login request. Following are the
rules for creating a new password:
• The password should begin with a letter (upper (A-Z) or lower case (
a-z)).
• The password should include at least one non-alphabetical character

in the first eight characters.
• The password is case-sensitive.
If the password does not comply with any of the above rules, an
appropriate warning message will be displayed.
Value range: [6 characters minimum]
Object: user profile - Change password
Type: DP
411-9001-124 18.16 1.0 Page 321 of 524
new password 1st try (Continued)

Checks: Following checks are done:
• If the password begins with a letter and contains one non-alphanu-

merical character among the first eight characters.
• if the password is at least six characters long.
• If the password is different from the N previous occurrences (N is set

in static configuration data).
Note: • When the password is typed, the characters are not displayed in
OMC-R GUI.
• If the new password is more than 8 characters, only the first 8 char-
acters are meaningful, though user can type more than 8 characters.
• If the user inputs a valid password (6-8 characters) followed by addi-

tional characters or symbols, the user will still be able to login to OMC-
R GUI successfully.
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
Page 322 of 524 411-9001-124 18.16 1.0
new power control algorithm Class 3

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
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.
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-
This parameter is used by all AMR HR HO not only FR=>HR.
stance is unlocked.
Default value: 34
Type: DP
Release: V14
411-9001-124 18.16 1.0 Page 323 of 524
night intervention
Description: This attribute modifies the "n" parameter in the AMR half rate "(n,p) vot-
This parameter is used by all AMR HR HO not only FR=>HR.
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.
Page 324 of 524 411-9001-124 18.16 1.0
not allowed cells

Description: A structure visible under lteAdjacentCellReselection object and com-
posed of not Allowed PCIDs and PCID Bitmap Group parameters.
Value range: See “not Allowed PCIDs” on page 324 and “PCID Bitmap Group”
on page 358
Class 3
Type: DP
Release V18 P&C4
not Allowed PCIDs

Description: List of PCIDs not allowed for reselection (belonging to Not allowed cells
composite attribute)
Value range: PCID range is [0-503]
Class 3
Type: DP
Release V18 P&C4
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
411-9001-124 18.16 1.0 Page 325 of 524
notAllowedAccessClasses Class 3
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
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
nullNRI
Description: This parameter represents the null NRI value for the current Public Land
Mobile Network (PLMN). The null NRI value is unique per PLMN.
Class: 0
Default Value: 1023
Object: SignallingPoint
Type: DP
Release: P&C5
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)
Page 326 of 524 411-9001-124 18.16 1.0
numberOfJokerDS0 Class 2
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
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
411-9001-124 18.16 1.0 Page 327 of 524
numberOfEnabledHDLCPorts
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.
numberOfSlotsSpreadTrans Class 3
Description: Number of radio time slots RACH transmission accesses are spread in
a random manner to avoid collisions.
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.
Page 328 of 524 411-9001-124 18.16 1.0
numberOfSlotsSpreadTrans Class 3
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
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 = 50
leads 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 dou-
ble allocation rate.
Therefore, for a network that handles a combination of
both types of mobiles, numberOflotsSpreadTrans
should be set to 32 (default value).
411-9001-124 18.16 1.0 Page 329 of 524
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
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
Page 330 of 524 411-9001-124 18.16 1.0
numberOfTCHQueuedToEndCongestion Class 3
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 Information
bsc - 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
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
411-9001-124 18.16 1.0 Page 331 of 524
2.15. O
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]
stateChangeRecord, tracFileReadyRecord,traceLogRecord.
Type: DP
objectInstance
Description: Scope of an alarm criteria. It covers all network objects when undefined.
Type: DP
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
Page 332 of 524 411-9001-124 18.16 1.0
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.
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.
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
411-9001-124 18.16 1.0 Page 333 of 524
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.
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
Page 334 of 524 411-9001-124 18.16 1.0
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
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-
by the BSC. This attribute cannot be modified and is relevant for BSC
3000 and TCU 3000.
Object: omu
Type: DP
Release: V13
411-9001-124 18.16 1.0 Page 335 of 524
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)
Type: DP
Checks: • [C/M]: Edge must be activated at cell level (egprsServices must be
equal to enabled ) if onePhaseAccess is equal to edgeEnabled or
gprsEdgeEnabled. 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)
Page 336 of 524 411-9001-124 18.16 1.0
onePhaseDnMsCapability Class 3
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
Type: DD
Release: V13
operationalState
The state parameter combinations for the bsc object are as follows:
administrative operational availability

State State 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.
411-9001-124 18.16 1.0 Page 337 of 524
operationalState
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:

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

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.
Page 338 of 524 411-9001-124 18.16 1.0
operationalState
Object: bts
Type: DD
operationalState
The state parameter combinations for the btsSiteManager object are as follows:

locked disabled {} The site has just been created or
locked.
unlocked disabled {} Downloading in the site BCF is in-
progress.
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:
administrative operational usage

State State 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).
411-9001-124 18.16 1.0 Page 339 of 524
operationalState
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:
operationalState availabilityStatus
disabled notInstalled
disabled {}
disabled failed
disabled dependency
enabled online
Object: cc
Type: DD
Release: V13
Page 340 of 524 411-9001-124 18.16 1.0
operationalState
The state parameter combinations for the cem object are as follows:
administrative
State 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:
administrative
State operational State availability Status
{} disabled {}
{} disabled failed
{} disabled degraded
{} enabled online
Object: controlNode
Type: DD
Release: V13
operationalState
Object: efd
Type: DD
411-9001-124 18.16 1.0 Page 341 of 524
operationalState
The state parameter combinations for the g3BscEqp object are as follows:
administrative operational
State State availability Status
{} disabled {}
{} enabled {}
Object: g3BscEqp
Type: DD
Release: V13
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
Page 342 of 524 411-9001-124 18.16 1.0
operationalState
disabled {}
Object: hsaRc
Feature: BSC 3000 optical
Type: DD
Release: V17
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:
operational State availability Meaning
Status
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, Aggre-
gation), optical fiber 0, optical fiber 1
Object: igm
Type: DD
Release: V18.0
411-9001-124 18.16 1.0 Page 343 of 524
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:
operational State availability Status

disabled dependency
disabled {}
degraded
disabled {}
Type: DD
Release: V13
operationalState
The state parameter combinations for the ipgRc object are as follows:
operationalState availabilityStatus
disabled notInstalled
disabled {}
Page 344 of 524 411-9001-124 18.16 1.0
operationalState (Continued)
enabled degraded
enabled {}
Object: igm
Type: DD
Release: V18.0
operationalState
The state parameter combinations for the ipm object are as follows:

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
operationalState
The state parameter combinations for the log object are as follows:
availability
operational State 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
411-9001-124 18.16 1.0 Page 345 of 524
operationalState
The state parameter combinations for the lsaRc object are as follows:
operational availability Status
State
disabled dependency
disabled {}
enabled degraded
disabled {}
Object: lsaRc
Type: DD
Release: V13
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:
availability
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
Object: mdScanner
Type: DD
Page 346 of 524 411-9001-124 18.16 1.0
operationalState
The state parameter combinations for the mms object are as follows:
administrative operational availability Status
State State
locked {} {}
Object: mms
Type: DD
Release: V13
operationalState
The state parameter combinations for the omu object are as follows:
State State
locked {} {}
Object: omu
Type: DD
Release: V13
operationalState
The state parameter combinations for the pcmCircuit object are as follows:

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.
411-9001-124 18.16 1.0 Page 347 of 524
Object: pcmCircuit
Type: DD
operationalState
The state parameter combinations for the pcu object are as follows:

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:
availability
disabled {} The pcusn has just been created.
disabled dependency The pcusn object does not work, or the PCM
link does not work.
enabled {} The pcusn object is working.
Object: pcusn
Type: DD
Release: V12
Page 348 of 524 411-9001-124 18.16 1.0
operationalState
The state parameter combinations for the signallingLink object are as follows:

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:
State State
{} disabled {}
{} disabled failed
{} enabled {}
Object: sw8kRm
Type: DD
Release: V13
411-9001-124 18.16 1.0 Page 349 of 524
operationalState
The state parameter combinations for the tmu object are as follows:
State State
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 the
messages to the OMC-R agent.
The state parameter combinations for the traceControl object are as follows:
availability
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
Type: DD
Page 350 of 524 411-9001-124 18.16 1.0
operationalState
The state parameter combinations for the transceiver object are as follows:
operational availability
State Status Meaning
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:

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.
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
411-9001-124 18.16 1.0 Page 351 of 524
operationalState
The state parameter combinations for the transcoder object are as follows:

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:
State State
locked disabled not installed
unlocked disabled {}
{} disabled failed
{} enabled {}
Object: trm
Type: DD
Release: V13
operationalState
The state parameter combinations for the xtp object are as follows:
administrative operational usage availability

State State State Status Meaning
locked disabled idle {} The CIC has just been
created or locked.
Page 352 of 524 411-9001-124 18.16 1.0
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".
Object: bts
Default value: 17
Type: DP
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
411-9001-124 18.16 1.0 Page 353 of 524
owner
Description: Name of the user creating the command file on the OMC-R.
Object: commandFile
Type: DP
2.16. P
packetAckTime Class 3
• dwAckTime
• upAckTime
The deactivation value is 64 for both of them.
Release: V12
Page 354 of 524 411-9001-124 18.16 1.0
packetFlowContext Class 3
• pfcArp1ConversationalCSCallProtection
• pfcArp1StreamingCSCallProtectin
• pfcNrtRequestedDnMbrCounterThreshold
• pfcNrtRequestedUpMbrCounterThreshold
• pfcPreemptionRatioGold
• pfcPreemptionRatioSilver
• pfcRtDowngradeAllowed
• pfcRtRequestedDnGbrCounterThreshold
• pfcRtRequestedUpGbrCounterThreshold
• pfcT6
• pfcT8
• pfcTsGuaranteedBitRateDl
• pfcTsGuaranteedBitRateUl
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 3
Description: Activation of the System Information Status feature in the cell.
Object: bts
411-9001-124 18.16 1.0 Page 355 of 524
packetSiStatus Class 3
Feature: Network Assisted Cell Change for release 4 MS
Type: DP
Release: V16
pagingOnCell Class 3
Description: Enables or disables paging requests in a cell.
Object: bts
Type: DP
Release: V9
pan Class 3
• panInc
• panDec
• panMax

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.
Page 356 of 524 411-9001-124 18.16 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
411-9001-124 18.16 1.0 Page 357 of 524
partialRecordCriteriaType Class 2
Description: 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 (partialRec
ordCriteriaEvent-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.
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.
partialRecordCriteriaEventType
Description: Create traceControl. Select this criterion when partialRecordCriteri-
aType is equal to "Event type".
Value range: handover
Type: DP
partialRecordCriteriaNbEvent
Description: Create traceControl. Enter the number of events when partialrecordCri-
teriaType is equal to "Numbered".
Type: DP
partialrecordCriteriaTimer
Description: This parameter should be set to "Hand over" when
partialRecordCriteriaType is equal to "Event type".
Type: DP
particular intervention
Description: Type of action associated with an alarm criteria in the specific configura-
tion.
Page 358 of 524 411-9001-124 18.16 1.0
particular intervention
Type: DP
password
Description: User’s current password as defined in the user’s profile. It is not dis-
played.
Type: DP
password
Description: 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 duration
Description: 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.
PCID Bitmap Group

Description: Identifies a group of cells where the reselection is not allowed (belonging
to Not allowed cells composite attribute)
Value range: (000000, 000001,000010,... to 111111)
Type: DP
Dafault value: 000000
Class 3
Release V18 P&C4
411-9001-124 18.16 1.0 Page 359 of 524
PCID to TA mapping
Description: List of PCIDs belonging to the same Tracking area
Value range: List of up to 8 elements where each element is composed of 8 PCID and
PCID Bitmap Group.
All 8 PCIDs must be defined in the range [-1 to 503]: -1 is the “non sig-
nificant” value (only significant values must be sent to a BSC)
Range PCID Bitmap Group is [000000 to 111111]
Type: DP
Dafault value: empty list
Class 3
Release V18 P&C4
pcmCircuit
Description: 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.
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)
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).
• [D]: If the application database of the related BSC is built, the pcmCir-
cuit object is locked.
• [D]: No btsSiteManager object (Abis PCM) or transcoder object (Ater
PCM) or pcu object (Agprs PCM) refers to the pcmCircuit object.
to the pcmCircuit object (no observation is running on the concerned
PCM).
• Setting the active PCM of a secured loop on a locked PCM must be
forbidden by OMC-R.
Page 360 of 524 411-9001-124 18.16 1.0
pcmCircuit
Description: 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.
• [D]: If the application database of the related BSC is built, the pcmCir-
cuit object is locked.
• [D]: No signallingLink or xtp object refers to the pcmCircuit object.
pcmCircuitBsc
Description: 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
pcmCircuitBtsSiteManager
Description: 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
pcmCircuitId
Description: 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
411-9001-124 18.16 1.0 Page 361 of 524
pcmCircuitId
Note: This parameter is only available for the lapdLink OML object on BSC
3000.
Type: DD
pcmCircuitId Class 2
Description: 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 2
Description: Description: Identifier of the PCM link used by a terrestrial circuit on the
A interface, defined with regard to the TCU.
Object: xtp
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 the
Dictionary).
pcmErrorCorrection Class 2
Description: 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 error
correction feature.
Page 362 of 524 411-9001-124 18.16 1.0
pcmErrorCorrection Class 2
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 2
Description: 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
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 ).
411-9001-124 18.16 1.0 Page 363 of 524
pcmType Class 0 (BSC 3000)

• [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.
pcu
Description: Identifier of a pcu object defined with regard to a bsc object.
Object: pcu
Type: Id
Release: V12
pcuCellState
Description: 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
pcusn
Description: Identifier of a pcusn object.
Object: pcusn
Type: Id
Release: V12
Page 364 of 524 411-9001-124 18.16 1.0
pcuSNName
Description: 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
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: _
penaltyTime Class 3
Description: 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 penaltyTime
seconds. 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 severity
Description: 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
411-9001-124 18.16 1.0 Page 365 of 524
periodicity
Description: 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 2
Description: Activates the Packet Flow Context feature in the cell.
Object: bts
Type: DP
Release: V16
pfcArp1ConversationalCSCallProtection Class 3
Description: 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 3
Description: Indicates if the real time PFCs Streaming of ARP 1 (allocation / retention
priorities 1) are protected against voice preemption.
Type: DP
Page 366 of 524 411-9001-124 18.16 1.0
Release: V16
eter is not used.
Type: DP
Release: V16
priorities 2) are protected against voice preemption.
Type: DP
Release: V16
eter is not used.
Type: DP
Release: V16
411-9001-124 18.16 1.0 Page 367 of 524
priorities 3) are protected against voice preemption. This parameter is
not used.
Type: DP
Release: V16
pfcFlowControlActivation Class 2
Description: Activates the flow control of the Packet Flow Context in the cell.
Object: bts
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 3
Description: 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 of
a 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.
Page 368 of 524 411-9001-124 18.16 1.0
pfcMinNumberOfJokersforTsGuaranteedBitRate Class 3
Description: This parameter represents the number of jokers that are required to en-
sure both the pfcTsGuaranteedBitRateUl and the pfcTsGuaranteedBi-
tRateDl. Refer to the pfcTsGuranteedBitRateUl 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
pfcNrtRequestedDnMbrCounterThreshold Class 3
Description: Threshold used by the pcuPfcNrtRequestedDnMbrGTThres counter
(C15267). For more information, refer to GSM BSS Performance Man-
agement — 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 3
Description: Threshold used by the pcuPfcNrtRequestedUpMbrGTThres counter
agement — Observation Counters Dictionary (411-9001-125).
Type: DP
Release: V16
411-9001-124 18.16 1.0 Page 369 of 524
pfcPreemptionRatioGold Class 3
Description: 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.
pfcPreemptionRatioSilver Class 3
Description: 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 3
Description: 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
Page 370 of 524 411-9001-124 18.16 1.0
pfcRtRequestedDnGbrCounterThreshold Class 3
Description: Threshold used by the pcuPfcRtRequestedDnGbrGTThres counter
(C15265). For more information, refer to GSM BSS Performance
Management — Observation Counters Dictionary (411-9001-125).
Type: DP
Release: V16
pfcRtRequestedUpGbrCounterThreshold Class 3
Description: Threshold used by the pcuPfcRtRequestedUpGbrGTThres counter
agement — Observation Counters Dictionary (411-9001-125).
Type: DP
Release: V16
pfcT6 Class 3
Description: 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 3
Description: 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
411-9001-124 18.16 1.0 Page 371 of 524
pfcT8 Class 3
Default value: 0
Type: DP
DP This parameter is part of the complex packetFlowContext attribute.
Release: V16
pfcTsGuaranteedBitRateDl Class 3
Description: This parameter represents the guaranteed throughput that can be
achieved in DL in any position of the cell for an EDGE MS.
Default value: 0
Value range [1 to 60] kbit/s
Type: DP
Note: This parameter is part of the complex packetFlowContext attribute. With
the implementation of PFC restriction removal feature, fixed values for
GPRS MS or EDGE MS, which are allotted a GPRS TBF are as follows:
• “pfcTsGuaranteedBitRateDl” = 11kbps, if the GPRS TBF is on a tdma

configured with CS2
• “pfcTsGuaranteedBitRateDl” = 8kbps, if the GPRS TBF is on a tdma

configured with CS1
with “pfcMinNumberOfJokersforTsGuaranteedBitRate”=0.
Release: V16
pfcTsGuaranteedBitRateUl Class 3
Description: This parameter represents the guaranteed throughput that can be
achieved in UL in any position of the cell for an EDGE MS.
Default value: 0
Value range: [1 to 60] kbit/s
Type: DP
Page 372 of 524 411-9001-124 18.16 1.0
pfcTsGuaranteedBitRateUl Class 3
Note: This parameter is part of the complex packetFlowContext attribute. With
the implementation of PFC restriction removal feature, fixed values for
GPRS MS or EDGE MS, which are allotted a GPRS TBF are as follows:
• “pfcTsGuaranteedBitRateUl” = 11kbps, if the GPRS TBF is on a tdma

configured with CS2
• “pfcTsGuaranteedBitRateUl” = 8kbps, if the GPRS TBF is on a tdma

configured with CS1
• with “pfcMinNumberOfJokersforTsGuaranteedBitRate”=0.
Release: V16
physicalFiberInfo
Description: Physical fiber and crossover info. List of four values:
• fiberRxState: state of the RX fiber connected to the CEM

• fiberTxState: state of the TX fiber connected to the CEM
• crossoverRxState: state of the RX signal received on the CEM
through the crossover (for the passive CEM, the value is set to
NotUsed)
• crossoverRxState: state of the TX signal received on the CEM
through the crossover (for the active CEM, the value is set to No-
tUsed)
Value range: List of physicalFiberInfo descriptions [[fiberRxState, fiberTxState, cross-
overRxState, crossoverTxState], with:
• fiberRxState: NotUsed / OK / KO / Undefined

• fiberTxState: NotUsed / OK / KO / Undefined
• crossoverRxState: NotUsed / OK / KO / Undefined
• crossoverRxState: NotUsed / OK / KO / Undefined
Object: cem3
Type: DD
Feature: Optical BSC/TCU High Capacity 4K
Release: V18
plmnPermitted Class 3
Description: 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
411-9001-124 18.16 1.0 Page 373 of 524
pODType
Description: 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 1
Description: 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]
QAM Activated)
Type: DP
RemoteSignallingPoint objects. However; pointCode parameter
under SignallingLinkSet object is not used and the default value will
be “Empty”.
pointCode Class 1
Description: 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 operational

Description: 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.
Value range: [enabled/disabled]
Object: omu
Type: DD
Release: V13
Page 374 of 524 411-9001-124 18.16 1.0
port Ethernet status

Description: 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.
Object: omu
Type: DD
Release: V13
positionInShelf
Description: 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
positionInShelf Class 0
Description: 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
Description: 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
411-9001-124 18.16 1.0 Page 375 of 524
Type: DP
Release: V18.0
powerBudgetInterCell Class 3
Description: Authorization to perform intercell handovers for power budget.
Type: DP
powerClass
Description: 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
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).
powerControl
Description: 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.
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.
Page 376 of 524 411-9001-124 18.16 1.0
powerControlIndicator Class 3
Description: 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 3
Description: 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’ object
instance is unlocked.
Default value: 4
Type: DP
Checks: • 0566CO01: The attribute ’powerIncrStepSizeUL’ must verify:
’1RxLevULP’ + ’powerIncrStepSizeUL’ <= ’uRxLevULP’
Release: V14
powerIncrStepSizeDownLink Class 3
Description: Increment step size for downlink power control. This is applicable to
BSC 3000 only.
locked.
Default value: 4
Type: DP
Checks: • 0565CO01 - The attribute ’powerIncrStepSizeDL’ must verify:
’1RxLevDLP’ + ’powerIncrStepSizeDL’ <= ’uRxLevDLP’
Release: V14
411-9001-124 18.16 1.0 Page 377 of 524
powerRedStepSizeDownLink Class 3
Description: Decrement step size for downlink power control. This is applicable to
BSC 3000 only.
locked.
Default value: 2
Type: DP
Checks: • 0567CO01 - The attribute ’powerRedStepSizeDL’ must verify: ’uRx-
LevDLP’ - ’powerRedStepSizeDL’ >= ’1RxLevDLP’
Release: V14
powerRedStepSizeUpLink Class 3
Description: Decrement step size for uplink power control. This is applicable to BSC
3000 only.
locked.
Default value: 2
Type: DP
Checks: • 0568CO01-The attribute ’powerRedStepSizeUL’ must verify: ’uRxLev-
ULP’ - ’powerRedStepSizeUL’ >= ’1RxLevULP’
Release: V14
preemptionAuthor Class 3
Description: 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.
Page 378 of 524 411-9001-124 18.16 1.0
preemptionConfiguration Class 3
Description: This parameter is composed of preemptionAuthor and eMLPPThresh-
old. Refer to these entries in the Dictionary.
Type: DP
Release: V14
preferredNonAdaptativeAMRcodec Class 3
Description: 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
Type: DP
Release: V18.0 P&C3
Note: This new parameter “preferredNonAdaptativeAMRcodec” is applicable
only for the AMR Group calls.
[M]:The parameter “preferredNonAdaptativeAMRcodec” has RTU se-
mantic control on SET.
pRequestedCodec Class 3
Description: This attribute defines the "p" parameter in the AMR "(n,p) voting" mech-
anism.
stance is unlocked.
Value range: Int [12 to 192] in steps of 12
Default value: 48
Type: DP
Release: V14
preemptionConfiguration Class 3
Description: This parameter is composed of preemptionAuthor and eMLPPThresh-
old. Refer to these entries in the Dictionary.
Type: DP
Release: V14
411-9001-124 18.16 1.0 Page 379 of 524
preSynchroTimingAdvance Class 3
Description: 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
priority Class 2
Description: 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.
privateMmsOmuRef
Description: 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 3
Description: Allows to segregate cells according to their mapping on Agprs PCM.
Value range: [no, yes]
Page 380 of 524 411-9001-124 18.16 1.0
privilegedCell Class 3
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.
probable cause
Description: To select messages according to the numerical value of the ISO proba-
bleCause field.
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 BSC 62
Call establishment error 4
Communication protocol error 5
Communication subsystem failure 6
Corrupt data 9
Degraded signal 12
DTE-DCE interface error 13
LAN error 25
Local node transmission error 27
Loss of frame 28
Loss of signal 29
Receive failure 40
Remote node transmission error 42
Transmit failure 54
Environmental External alarm loop 58
Enclosure door open 14
Fire detected 18
Heating, ventilation, or cooling system 21
Material supply exhausted 30
411-9001-124 18.16 1.0 Page 381 of 524
Equipment Equipment absent 60

Equipment malfunction 15
Heating, ventilation, or cooling system problem 21
Input/output device error 23
Input device error 24
Material supply exhausted 30
Power problem 35
Processor problem 37
Receive failure 40
Receiver failure 41
Storage capacity problem 49
Temperature unacceptable 50
Timing problem 52
Transmit failure 54
Transmitter failure 55
ProcessingError Cause of restart or switchover 59
No response 61
Application subsystem failure 2
Configuration or customization error 7
Corrupt data 9
File error 17
Out of memory 32
Queue size exceeded 39
Software error 46
Software program abnormally terminated 47
Software program error 48
Storage capacity problem 49
Underlying resource unavailable 56
Version mismatch 57
QualityOfService Shutdown 63
Congestion 8
Performance degraded 34
Queue size exceeded 39
Resource at or nearing capacity 43
Response time excessive 44
Retransmission rate excessive 45
Threshold crossed 51

Type: DP
processor identity
Description: 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
Page 382 of 524 411-9001-124 18.16 1.0
processor identity
Release: V11
Note: During the command "create mdWarning", the operator can define ei-
ther "equipment identity" or "processor identity", but not both.
pwciHrequave Class 3
Description: 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
2.17. Q
qsearchC Class 3
Description: The MS searches for UMTS
cells if level is above or
below the threshold when the
serving BCCH frequency is
part of the BA_List
Value range: 0:"<-98 dBm" QsearchC < -XX dBm: the HO
1: “< -94 dBm” towards theUMTS can be done only
2: “< -90 dBm” if the RxLev from the serving cell is
3: “< -86 dBm” below -XX.
4: “< -82 dBm” QsearchC > -XX dBm: the HO
5: “< -78 dBm” towards theUMTS canbe done only
6: “< -74 dBm” if the RxLevfromthe serving cell is
7: “always” above -XX. "values different
8: “> -78 dBm” from"always" and "never" areuseful
9: “> -74 dBm” only if serving BCCH ispart of
10: “> -70 dBm” BA_List in SI5"
11: “> -66 dBm”
12: “> -62 dBm”
13: “> -58 dBm”
14: “> -54 dBm”
15: “never”
Default value: 15
Type: DP
Checks:
Release: V17
Notes: This parameter is available only for BSC 3000.
411-9001-124 18.16 1.0 Page 383 of 524
2.18. R
radChanSelIntThreshold Class 3
Description: 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
FIGURE 9. Channels are allocated cyclically inside each pool
Default value: 1
Type: DP
Release: V8
Page 384 of 524 411-9001-124 18.16 1.0
radioLinkTimeOut Class 3
Description: 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".
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
411-9001-124 18.16 1.0 Page 385 of 524
radioSiteMask
Description: 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 set
using 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]
Class 2
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.

TS#31 does not belong to the radio site mask of each BTS for the giv-
en loop.
radioSiteMaskOffset Class 2
Description: 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.
Page 386 of 524 411-9001-124 18.16 1.0
radioSiteMaskOffset Class 2
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).
anager object is created with he btsType parameter set to IP, the ra-
dioSiteMaskOffset parameter must be equal to 0.
Release: V14
radioSiteName
Description: 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
Checks: • [C/M]: The name of a multiple site is unique to the OMC-R.
- 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 3
Description: Maximum time that SDCCH or TCH can be continuously occupied with-
out generating an alarm.
Value range: [1 to 18] hours
Object: bsc
411-9001-124 18.16 1.0 Page 387 of 524
radResSupBusyTimer Class 3
Default value: 3
Type: DP
Release: V8
radResSupervision Class 3
Description: 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 3
Description: 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
Type: DP
Release: V8
range
Description: 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
Page 388 of 524 411-9001-124 18.16 1.0
reception time
Description: To select messages received at that time.
(411-9001-130).
Type: DP
record reference
Description: 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.
redundantPcmNumber
Description: Number of the redundant PCM link defined on BSC end.
This dynamic attribute is displayed provided the btsSiteManager object
redundantPcmPresence attribute
value is "true".
Type: DD
Remark: A redundant link is not normally used for traffic or signaling connections.
redundantPcmPresence Class 2
Description: Presence of a redundant PCM link on a radio site
411-9001-124 18.16 1.0 Page 389 of 524
redundantPcmPresence Class 2
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.
On unlocking the btsSiteManager object, if the configRef supports Se-
curedLoop (configRef with R2 field set to 1), the OMC-R checks the re-
dundantPcmPresence parameter is set to "TRUE".
refPeriod
Description: Reference counting period when a counter is involved.
Condition: To define if a counter is associated with the criteria.
Type: DP
refPeriod
Description: 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 GSM BSS Fundamentals — Operating Principles (411-
9001-007).
Type: DP
related bts site manager list

Description: 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
Page 390 of 524 411-9001-124 18.16 1.0
relatedSoftwares
Description: 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
relay
Description: 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.
remoteSsuState
Description: 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
remoteSsuState
Description: 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
411-9001-124 18.16 1.0 Page 391 of 524
remoteNodeType
Description: This parameter indicates the type of remote node to reach; that is, MSC
or SMLC
Class: 0
Value range: MSC = 0, SMLC = 1 on MOD
Default Value: MSC
Type: DP
Release V 18 P&C5
Checks: When multiple instances of remoteSignallingPoint, whose node_type is
MSC, are created, the NRI_Length value should be non zero. License
checks are performed during the Build or Reset (BDA / TRX) / Cell or
Site unlock.
remoteSignallingPointInstance
Description: This parameter represents the instance of the remoteSignallingPoint ob-
ject which gives the pointCode the BSC has to address when it is related
to pcmA or xtp circuits. This parameter is only relevant when pcmType
= pcmA.
Class: 2
Default Value: • Empty (MMI)
• 0xFF (MOD)
Object: pcmCircuit
Type: DP
Release V 18 P&C5
Checks: Consistency check on the pcmCircuit object ensuring the remoteSignal-
lingPoint mapping only when A-Flex is activated. The check is done on:
• Build BDA
• Unlock PCM (when BDA is built)

Note: • This parameter is available only for BSC 3000. Also, this parameter
will be available for configuration only if A Flex - GSM Access or Qua-
si Associated Mode feature is activated.
• This parameter is only relevant when pcmType = pcmA. For the other
PCM types the remoteSignallingPointInstance parameter is filled with
"empty (0xFF)".
Page 392 of 524 411-9001-124 18.16 1.0
report range
Description: 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 template
Description: Identifier of the report template object defined with regard to the bsc ob-
ject.
Type: DP
Release: V11
report type
Description: A 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 several
objects
Type: DP
Release: V11
reportObjLevel
Description: 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.
411-9001-124 18.16 1.0 Page 393 of 524
reportTypeMeasurement Class 3
Description: 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 2
Description: 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
Checks: • [C/M]: retransDuration≥ (delayBetweenRetrans + 1) x nbOfRe-
peat
Release: V8
retry on error
Description: 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
Page 394 of 524 411-9001-124 18.16 1.0
rlf1 Class 2
Description: 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 2
Description: 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
Type: DP
Release: V8
rlf3 Class 2
Description: 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
411-9001-124 18.16 1.0 Page 395 of 524
rLCPolling Class 3
Description: Configuring the polling frequency for DL TBF.
• 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
rmpConfState
Description: 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
rNCId Class 3
Description: 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
Page 396 of 524 411-9001-124 18.16 1.0
rndAccTimAdvThreshold Class 3
Description: 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 35] 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".
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 2
Description: 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.
routingArea Class 3
Description: Routing Area Code value of the AdjacentCellReselection object.
Class: 3
Default value: -1
Type: DP
Feature: NACC InterBSC/intra PCUSN feature
Release: V18 P&C5
411-9001-124 18.16 1.0 Page 397 of 524
routingArea Class 3
Checks: The routingArea, baseColourCode and networkColourCode parameters
of the adjacentCellReselection object should be either all valid or all in-
valid. That means that for an AdjacentCellReselection object, if one of
the routingArea, baseColourCode and networkcolourCode parameters
has a valid value, then the 2 other parameters should also have a valid
value.
The valid values for the routingArea parameter are [0, 255].
Invalid value for routing Area parameter is -1.
rowPosition
Description: 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 3
Description: 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 3
Description: 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 3
Description: Number of "Measurement Results" messages received before the pow-
er control algorithm in a cell is triggered.
Object: bts
Default value: 4
Type: DP
Page 398 of 524 411-9001-124 18.16 1.0
rxLevAccessMin Class 3
Description: 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
Object: bts
Default value: less than -110 dB
Type: DP
rxLevDLIH Class 3
Description: Maximum interference level in BTS-to-MS direction, beyond which an in-
tra-cell handover may be triggered.
Type: DP
rxLevDLPBGT Class 3
Description: 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 the
situation.
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 3
Description: Downlink signal strength threshold above which handovers to UTRAN
for power budget are inhibited
Value range: <-110 ... >-48 dBm
411-9001-124 18.16 1.0 Page 399 of 524
rxLevDLPbgtUTRAN Class 3
Default value: 63 (on MOD), “>-48” (on MMI) ◦
Type: DP
Checks:
Release: V17
rxLevHreqave Class 3
Description: 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 Class3
Description: 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 3
Description: Number of arithmetic averages taken into account to compute the
weighted average signal strength in handover and power control algo-
rithms. Each is calculated from
rxLevHreqave signal strength measurements on a serving cell.
Default value: 1
Type: DP
Checks: • [C/M]: It is equal to the number of weights in
rxLevWtsList (refer to this entry in the
Dictionary).
Page 400 of 524 411-9001-124 18.16 1.0
rxLevMinCell Class 3
Description: Minimum signal strength level received by MS for being granted access
to a neighbor cell.
Default value: -95 to -94 dB (GSM 900 or 850), -93 to -92 (GSM 1800 or 1900)
Type: DP
rxLevMinCellUTRAN Class 3
Description: 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 3
Description: 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 3
Description: Defines the frequency of RxLev and RxQual distribution.
This is not used in this version.
Only values 0, 1 and 2 are valid.
Object: bts
411-9001-124 18.16 1.0 Page 401 of 524
rxLevRxQualDistributionActivation Class 3
Type: DP
Release: V14
rxLevULIH Class 3
Description: 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 Mapping
Feature is used.
Feature: Uplink Mapping (TF 876)
Type: DP
rxLevWtsList Class 3
Description: 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 3
Description: 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
Page 402 of 524 411-9001-124 18.16 1.0
rxQualAveBeg Class 3
Description: 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 3
Description: 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 3
Description: 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 3
Description: 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
411-9001-124 18.16 1.0 Page 403 of 524
rxQualULIH Class 3
Description: 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 3
Description: RxQual threshold for taking into account measurements in
RxLev and Interf matrix distributions.
Value range: [inferiorTo02 / between02and04 / between04and08 / between08and16 /
between16and32 / between32and64 / between64and128 /
superiorTo128]
Object: bts
Type: DP
Release: V14
rxQualWtsList Class 3
Description: 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
2.19. S
sIkAssociatedTmuPortPosition
Description: Gives the TMU and port number bearing the SS7 signaling.
Value range: [tmuPos / hardwareSlotPositionNMC / portNumber]
Page 404 of 524 411-9001-124 18.16 1.0
sIkAssociatedTmuPortPosition
Type: DD
Release: V14
sIkATerResource
Description: 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 2
Description: 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 2
Description: 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
sapi
Description: The Service Access Point Indicator defining the type of LAPD link use.
Value range: [RSL / OML]
Object: lapdLink
Type: DP
411-9001-124 18.16 1.0 Page 405 of 524
scannerId
Description: 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.
scannerId
Description: 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.
sCCPRoutingIndicator
Description: Indicated which route the SCCP takes.
Value range: [international/national]
Type: DP
scramblingCode Class 3
Description: Scrambling code of the UMTS cell
Default value: 0
Type: DP
Release: V17
Page 406 of 524 411-9001-124 18.16 1.0
scramblingCode Class 3
Checks: [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
• [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.
securedLoopActivation
Description: This parameter allows to activate secured loop feature
Value range: [disabled(0)/ enabled(1)]
Feature: BTS Secured Loop
Type: DP
411-9001-124 18.16 1.0 Page 407 of 524
securedLoopActivation (Continued)
Checks: Perform the following checks:
• Activation of the secured BTS loop feature requires the correspond-
ing RTU. For more information , see For more information, see GSM
BSS Fundamentals Operating Principles (411-9001-007)
• On unlocking the btsSiteManager object, a Secured Loop ConfigRef

has to be selected if the securedLoopActivation is set to enabled.
• A secured loop configRef is a configRef with the R2 field == 1.
• On unlocking the btsSiteManager object, pcm1 and pcm2 on bsc-

SitePcmList are not provisioned if the securedLoopActivation is en-
abled. This is available only for S8000 BTS family and not for
BTS18000 family

tion parameter is set to "enabled", the OMC-R checks no more than 2
PCMs are referenced.

TS#31 does not belong to the radio site mask of each BTS for the giv-
en loop.

BSC PCM identities belong to the same board:
– S8000 BTS :
• bscSitePcmList = (n ~ 0) & (n+1 ~ 3) with the PCM

identity "n" even and different of PCM 0,1,2,3,4 and 5
of LsaRC 0 (synchronizing ATER PCM)
– BTS9000 BTS :
• bscSitePcmList = (n ~ 0) & (n+1 ~ 1) with the PCM

identity "n" even and different of PCM 0,1,2,3,4 and 5
of LsaRC 0 (synchronizing ATER PCM)
• Unlocking any of btsSiteManager objects referencing the same PCMs

and having different values of the parameter securedLoopActivation
must be forbidden by OMC-R.
• On unlocking the btsSiteManager object, if the configRef supports

SecuredLoop (configRef with R2 field set to 1), the OMC-R checks the
redundantPcmPresence parameter is set to "TRUE".
• On unlocking the btsSiteManager object, the OMC-R checks the

teiBtsSiteManager parameter is different for each Bts Site Manager of
the secured loop when the secured loop is activated.
Release: V18 P&C4
Page 408 of 524 411-9001-124 18.16 1.0
selfAdaptActivation Class 3
Description: This attribute specifies if the automatic handover adaptation mechanism
is enabled/disabled.
This attribute is modified only if the ’bts’ object instance is unlocked.

Value range: [Enabled / Disabled]
Object: bts
Type: DP
Release: V14
selfTuningObs Class 3
Description: 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.
sequenceNumber
Description: Tracing the record identification number.
Object: traceFileReady
Type: DP
411-9001-124 18.16 1.0 Page 409 of 524
serial number
Description: 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 number
Description: 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 3
Description: 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
Page 410 of 524 411-9001-124 18.16 1.0
servingBandReportingOffset Class 3
Description: 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 3
Description: 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 mode

Description: Session context saving mode.
Value range: [automatic when logout / on user request]
Type: DP
Release: V10
sGSNRelease Class 3
Description: 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)
411-9001-124 18.16 1.0 Page 411 of 524
sGSNRelease Class 3
Type: DP
Release: V15
sharedPDTCHratio
Description: 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
shelfNumber
Description: 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 0
Description: Defines the shelf number for the IGM.
• for bscoptical_ip: 1
Object: igm
Type: DP
Release: V18.0
shelfNumber Class 0
Description: Defines the shelf number for the ipgRc.
• for bscoptical_ip: 1
Object: ipgRc
Page 412 of 524 411-9001-124 18.16 1.0
shelfNumber Class 0
Type: DP
Release: V18.0
short message
Description: 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.
signallingLink
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.
signallingLinkId
Description: Identifier of a signallingLink object defined with regard to a
signallingLinkSet object.
Type: Id
411-9001-124 18.16 1.0 Page 413 of 524
signallingLinkId
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).
Checks: • [D]: If the application database of the related BSC is built, the signal-
lingLink object is locked.
• [D]: No mdScanner object refers to the signallingLink object (no obser-
vation is running on that object).
signallingLinkResourcesStates
Description: 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
signallingLinkResState
Description: 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
Page 414 of 524 411-9001-124 18.16 1.0
signallingLinkResState field
Description: 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.
signallingLinkSet
Description: 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.
• [D]: The application database of the related BSC has been reset by an
Off line reset BDA command.
signallingLinkSetInstances List
Description: This parameter represents the list of routes (signallingLinkSet), which al-
lows to reach this remote node. For each signallingLinkSet instance
there is its associated priority.
Class: 0
Value range: List of 0 to16 elements. Each element includes 2 entities:
• signallingLinkSetInstance: value range = 0 to 15
• priority: value range = notApplicable(0), main (1), alternative (2)

Default Value: Empty List
Object: RemotesignallingPoint
Type: DP
Release: V 18 P&C5
411-9001-124 18.16 1.0 Page 415 of 524
signallingPoint
Description: 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.
• [D]: The application database of the related BSC has been reset by an
Off line reset BDA command.
sigPowerOverboost Class 3
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
site
Description: Name that identifies the site.
Value range: String [1 to 16 characters]
Type: DD
siteGsmFctList Class 2
Description: 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.
Page 416 of 524 411-9001-124 18.16 1.0
Response
GSM function Routing mode time
Without With
centralized centralized
O&M O&M
GSM entity relative tei bcf 10 seconds
Management
downloading relative tei relative tei 32 secon
ds
site Management relative tei bcf 120 seco
nds
abis Signalling bcf bcf 120 seco
Management nds
abis Traffic bcf bcf 120 seco
Management nds
radio frequency bcf bcf 120 seco
Transmission nds
radio frequency not none 0 second
Reception implemented
cell Management bcf bcf 120 seco
nds
frequency relative tei bcf 30 secon
hopping ds
Management
tdma relative tei bcf 30 secon
Management ds
time slot relative tei bcf 30 secon
Management ds
gsmTime not none 0 second
implemented
carrier 0 Filling not none 0 second
implemented
frequency bcf bcf 120 seco
Management nds
Default value: site Mgt/abisSig
Type: DP
411-9001-124 18.16 1.0 Page 417 of 524
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.
siteName
Description: 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
Checks: • [C/M]: The name of a site is unique to the OMC-R.
BTSSM). All other
symbols/characters are prohibited.
• 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 field
Description: 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 an
A resource has been assigned to this
Signaling Link (SLK) path.
Page 418 of 524 411-9001-124 18.16 1.0
slkAssociatedTmuPortPosition field
Description: 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 SLK
path.
slkAssociatedTmuPortPosition
Description: SLK CN termination identifier
Value range: Displayed fields:
• shelfNumber: Integer 0-1
• positionInShelf: Integer 1-15
• portNumber: Integer
Type: DD
Release: V17
Notes: This parameter is available only for
BSC 3000. This optional parameter is meaningful if a CN termination has
been assigned to Signaling Link path.
slkATerResource field
Description: SLK Ater section identifiers. It is a sub-parameter field of
signallingLinkResourcesStates.
Value range: • pcmInstance: Integer 0-363

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.
411-9001-124 18.16 1.0 Page 419 of 524
slkATerResource
Description: SLK Ater section identifiers
Value range: Displayed fields:
• pcmInstance: Integer 0-363
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 2
Description: Code of an SS7 channel. It is identical on BSC and MSC
ends.
Type: DP
Checks: • [C/M]: The code of an SS7 link is one-of-a-kind to the
BSC.
small to large zone HO priority Class 3

Description: 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 3
Description: Enables/disables the smart power management feature
Value range: [disabled/enabled/enhanced]
Type: DP
Release: V17
Page 420 of 524 411-9001-124 18.16 1.0
smartPowerManagementConfig Class 3
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)
The 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.
smartPowerSwitchOffTimer Class 3
Description: Set the timer before switching the PA OFF
Value range: 5-255 (minutes)
Type: DP
Release: V17
Notes: BSC 3000 only
smoke detector Class 2

Description: Presence or absence of the optional equipment "smoke
detector" in S8000 Outdoor.
Type: DP
Release: V9
smsCB Class 3
Description: Whether broadcasting of short messages in unacknowl-
edged mode is authorized in a cell.
Value range: [used / unused]
411-9001-124 18.16 1.0 Page 421 of 524
smsCB Class 3
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.
software
Description: 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: sWVersion
BackUp, 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.
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:
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:
bsc object is unlocked, the parent bts object is locked, and the transceiv-
erEquipment object is locked.
softwareLabel
Description: This attribute is a comment about the related software.
This attribute is modified by the Manager. Value changes
are notified to the Manager.
Page 422 of 524 411-9001-124 18.16 1.0
softwareLabel
Type: DP
Release: V13
source indicator
Description: Select messages according to the source of the operation.
Value range: [resource operation / management operation / unknown]
Type: DP
specific problems
Description: 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 3
Description: 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
411-9001-124 18.16 1.0 Page 423 of 524
speechMode Class 3
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
The 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 3
Description: 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
Checks: • [C/M]: The "full rate" value is mandatory; it must be defined in the list.
cense for AMR on the following operations:
• setting the value of the speechMode
parameter to "AMR half rate" or "AMR full rate"
• unlocking a TRX
• building a BSC
The 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.
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
Page 424 of 524 411-9001-124 18.16 1.0
speechOnHoppingTs Class 3
Description: This attribute is reserved for future use.
Value range: [true, false]
Object: bts
Type: DP
Release: V12
speechVersionAsscomp Class 1
Description: Whether the "Speech version" element is used or not in the ASSIGN
Default value: true
Type: DP
Release: V12
speechVersionHoperf Class 1
Description: 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 1
Description: Whether the "Speech version" element is used in the HANDOVER RE-
QUEST ACKNOWLEDGE messages (Phase II compliance).
Default value: true
Type: DP
Release: V12
411-9001-124 18.16 1.0 Page 425 of 524
speechVersionHorqd Class 1
Description: 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 3

Description: 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.
standard indicator AdjC Class 3

Description: 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
architecture.
standardIndicator Class 2
Description: 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]
Page 426 of 524 411-9001-124 18.16 1.0
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 MHz
EXTENDED 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:
• 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]
• f2 = f1 + 45 MHz
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 to
124] and [955 to 1023], which are 200 kHz apart:
• Downlink direction (BTS-to-MS) = 921 to 960 MHz
A frequency N corresponds to the following Uplink frequency:
• f1 = 876.2 + 0.2x(N - 955) MHz where N = [955 to 1023]
• 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 MHz
GSM 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:
• Downlink direction (BTS-to-MS) = 1930 to 1990 MHz A frequency N
corresponds to the following Uplink
frequency:
• f1 = 1850.2 + 0.2x(N - 512) MHz where N = [512 to 810]
• f2 = f1 + 80 MHz
GSM 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 1800
Network 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).
411-9001-124 18.16 1.0 Page 427 of 524
architecture. GSM 850
The 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 MHz
A frequency N corresponds to the following Uplink frequency:
• f1 = 824.2 + 0.2x(N - 128) MHz where N = [128 to 251]
• f2 = f1 + 45 MHz
Release: V9
standbyStatus
Description: ISO State
Value range: [hotStandby / coldStandby / providingService]
Object: atmRm, cem, iem, lsaRc, omu, sw8kRm, trm, hsaRc, hsaRcTcu, iom
Type: DD
Release: V13
standbyStatus
Description: 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 TMU
Description: 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
Page 428 of 524 411-9001-124 18.16 1.0
standbyStatus TMU
Type: DD
Release: V17
Note: This parameter is available in BSC 3000 only.
start date
Description: The date the first data is recorded in the log (default is the current date).
130).
Type: DP
start time
Description: Absolute time of first job run (default is the current date and time). Abso-
lute time format entry forms are detailed in GSM OMC-R Commands
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 time
Description: Start of system log reading on the requested start date (default is 00:00).
Time format entry forms are detailed in GSM OMC-R Commands Refer-
130).
Do not fill in if this criterion is not selected.
Value range: [<time>]
Type: DP
startAlarmFilter
Description: Condition for triggering an alarm when no
The following fields can be combined in the
logical expression:

administrativeState state change =
availabilityStatus state change =
411-9001-124 18.16 1.0 Page 429 of 524
startAlarmFilter
bsc equipment alarm =
name
bsc model alarm =
cause alarm <=>
btsSiteManager alarm =
model
bts equipment alarm =
name
equipment alarm <=>
processor number
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 (nom-
inal 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
notification. These notifications do not trigger alarms.
Condition: To define if no counter is associated to the criterion.
Type: DP
startAlarmThreshold
Description: 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
Page 430 of 524 411-9001-124 18.16 1.0
startAlarmThreshold
Description: Minimum (thresholdLow) / maximum (thresholdHigh) counting value in
the reference period, below/above which a start of "lower threshold/up-
per threshold" alarm message
is sent. The value must be checked by users. If thesholdType = "thresh-
oldLow", this attribute defines a
minimum 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 is
sent. It must be lower than startAlarmThreshold "low". If thesholdType =
"thresholdHigh", this attribute defines a maximum value for a one minute
reference period (or the
counter 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]
Type: DP
Remark: • The threshold limits depend on the associated counter.
• The BSS counter threshold crossing detection mechanism is described
in GSM BSS Fundamentals — Operating Principles (411-9001-007).
startCounterThreshold
Description: Minimum counting threshold when a counter is involved.
Condition: To define when a counter is associated with the criterion.
Type: DP
startTime
Description: 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
startTime
Description: 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
411-9001-124 18.16 1.0 Page 431 of 524
status
Description: This parameter is used to add (available status) or remove (notAvailable
/ deloading status) this instance from the available node list in case of
MSC de-loading for instance.
Class: 3
Value range: notAvailable (0) / deloading (1) / available (2)
Default Value: available
Type: DP
Release: V 18 P&C5
Checks: When only one MSC is configured, the "status" should be "available" al-
ways (if A-Flex is activated). The check is done on:
• Build BDA
• Set remoteSignallingPoint (when BDA is built)

stopTime
Description: Date and time the OMC-R agent will purge the restored
files.
Value range: [<date>, <time>]
Type: DP
stopTime
Description: Date and time the temporary observation will stop.
(411-9001-130).
Object: mdScanner - Create temporary observation
Type: DP
Page 432 of 524 411-9001-124 18.16 1.0
stopTime
Checks: • [C]: stopTime - startTime > mdGranularityPeriod
minutes
• [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.
subChanId
Description: 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.
subject
Description: 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
suffix
Description: 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 GSM BSS Fundamentals — Operating Principles (411-9001-007).
Object: Call monitoring - Transfer (SDO)
Type: DP
summary
Description: Text explaining the goal of the command file.
Object: commandFile
Type: DP
411-9001-124 18.16 1.0 Page 433 of 524
suspendResumeActivation Class 3
Description: 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 Area
Update message.
• The new value does not apply to ongoing calls. It
applies to new calls only.
Release: V15
supportingTransceiverEquipment
Description: 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.
sw8kRm
Description: The 8k Subrate Timeswitch Ressource Module, which adds sub-track
switching capability to the Interface Node.
Object: sw8kRm
Type: Id
Page 434 of 524 411-9001-124 18.16 1.0
sw8kRmId
Description: 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 3
Description: Defines the current version running.
Value range: String containing the IPM software name.
Object: ipm
Type: DP
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.
sWVersionBackUp
Description: 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
sWVersionFallBack
Description: 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
411-9001-124 18.16 1.0 Page 435 of 524
sWVersionNew
Description: Reference number of the new software release. It is updated following a
download or version change command. Refer to the sWVersionRunning
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 3
Description: Defines the software version in the IPM NON ACTIVE flash.
Value range: String containing the IPM software name.
Object: ipm
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 2
Description: 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.
Page 436 of 524 411-9001-124 18.16 1.0
synchronized Class 3
Description: 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
synchronizingCemRcFiber
Description: 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
synchronizingCemRcFiber
Description: 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
synchronizingHsaRc
Description: 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
411-9001-124 18.16 1.0 Page 437 of 524
synchronizingHsaRc
Object: bsc
Type: DD
Release: V17
synchronizing PCM
Description: 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
syntheticFaultNumber
Description: 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 2
Object: bts
Type: DP
Release: V15
2.20. T
t3101 Class 3
Description: 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
Page 438 of 524 411-9001-124 18.16 1.0
t3103 Class 3
Description: 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)
t3107 Class 3
Description: BSC timer triggered during the assignment command procedure. Use
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 3
Description: 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 is
sent 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
411-9001-124 18.16 1.0 Page 439 of 524
t3111 Class 3
Description: BSC timer triggered during the radio resource clearing procedure. Use
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 3
Description: Timer to wait for handover to UTRAN complete message
Value range: 2...255 seconds
Object: bts
Default value: 12
Type: DP
Checks:
Release: V17
t3122 Class 3
Description: Minimum time that mobiles must wait before issuing a channel
allocation request when an immediate assignment has failed.
Object: bts
Type: DP
t3168 Class 3
Description: 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
Page 440 of 524 411-9001-124 18.16 1.0
t3168 Class 3
Type: DP
Release: V14
t3172 Class 3
Description: 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
t3192 Class 3
Description: 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 2
Description: Activate/deactivates the advanced TA detection in eGPRS above 35 ki-
lometers.
Object: bts
Type: DP
411-9001-124 18.16 1.0 Page 441 of 524
taDetectionDataExtCell class 2
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
The 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
target Bda
Description: Target BDA for the On-line reset command See GSM OMC-R Com-
(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 2
Description: 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 the
following:
E1 0 1 2 3 4 5 6 7 8 9 1 11 1 13 1 15
0 2 4
T1 1 2 3 4 5 6 7 8 9 10 1 12
1
E1 1 17 1 19 20 2 2 23 24 2 2 27 2 29 3 31
6 8 1 2 5 6 8 0
T1 13 1 15 1 1 18 19 2 21 22 2 24
4 6 7 0 3
Page 442 of 524 411-9001-124 18.16 1.0
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
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, the
teiBtsSiteManager parameter must be equal to 0.
On unlocking the btsSiteManager object, the OMC-R checks the
teiBtsSiteManager parameter is different for each Bts Site Manager of
the secured loop when the secured loop is activated
teiLapdLink
Description: 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 2
Description: 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.
411-9001-124 18.16 1.0 Page 443 of 524
teiTranscoder Class 2
Description: 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
temporaryOffset Class 3
Description: 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 to
the 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 name
Description: 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.
is case sensitive, for ALL object names (such as TRX, BSC, BTS,
BTSSM). All othe symbols/characters are prohibited.
terminal profile
Description: 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.
Page 444 of 524 411-9001-124 18.16 1.0
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
text
Description: Contents of a short message. It is broadcast as it is.
Value range: [93 characters max]
Type: DP
text
Description: 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 2

Description: Presence or absence of the optional equipment "microwave terminal" in
4000 Outdoor.
Type: DP
Release: V9
tfoActivation class 3
Description: Indicates if TFO is activated or not.
Value range: [activated / deactivated]
Object: bsc
Feature: TFO support
Default value: deactivated
Type: DP
Release: V18.0
411-9001-124 18.16 1.0 Page 445 of 524
tGMMKeepAlive Class 3
Description: 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
Feature: 23038 - Disabling ’TBF Keep Alive’
Type: DP
Release: V15
This BSS is using license

Description: Indicates whether the BSC is using a 4K Erlangs license.
Value range: [yes/no]
Object: md - Display 4K Erlangs Information
Release: V17
threshold3Ghigh
Description: Reselection threshold towards UTRAN FDD or TDD cells.
Value range: ( non significant, 0 , 2 , 4 , 6 , …, 60 , 62 )
Object: bts
Type DP
Checks threshold3Ghigh parameter value from has to be different from "non
significant" .
Set the threshold3Ghigh parameter different from non significant, if one
of the parameters from the 3GReselection ARFCN structure (3Gpriority,
threshold3Glow and 3GQRxLevMin) has a value different from “non sig-
nificant”..
Class 3
Release: V18 P&C4
thresholdGSMlow
Description: Threshold below which the MS is allowed to reselect to cell with lower
priority from another technology.
Value range: (0 , 2 , 4 , 6 , …, 26 , 28 , - infinity )
Object: bts
Page 446 of 524 411-9001-124 18.16 1.0
thresholdGSMlow
Type DP
Default value - infinity
Class 3
Release: V18 P&C4
thresholdInterference Class 2
Description: 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.
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
411-9001-124 18.16 1.0 Page 447 of 524
thresholdLteHigh
Description: Reselection threshold towards E-UTRAN FDD or TDD cells
Value range: (0 , 2 , 4 , 6 ,... 60 , 62 )
Default value 62
Class 3
Type: DP
Release V18 P&C4
thresholdType
Description: 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]
Class 3
Type: DP
threshold3Glow
Description: Reselection threshold towards UTRAN FDD or TDD cells
Value range: ( non significant, 0 , 2 , 4 , 6 , …, 60 , 62 )
Object: bts
Type DP
Unit dB
Class 3
Release: V18 P&C4
thresholdLteLow
Description: Reselection threshold towards E-UTRAN FDD or TDD cell
Value range: (<empty>, 0 , 2 , 4 , 6 ,... 60 , 62 )
Default value empty
Type: DP
Class 3
Release V18 P&C4
Page 448 of 524 411-9001-124 18.16 1.0
thresholdPrioritySearch
Description: Gives the threshold for the serving cell that controls the measurement
of inter-RAT cells or the frequencies of lower priority when the priority
based cell reselection algorithm is used.
Value range: (-98 , -95 , -92 , …,-59 , -56 , - infinity )
Object: bts
Default value - infinity
Type: DP
Class 3
Release V18 P&C4
timeBetweenHOConfiguration Class 3
Description: 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 3
Description: Time between two FACCH notifications.
Default value: 2 (recommended)
Feature: ASCI
Type: DP
Release: GSM-R V15
timerPeriodicUpdateMS Class 3
Description: Time between two location update requests.
Value range: [0 to 255] 1/10th of hour. "0" means that no periodic
location update is requested.
Object: bts
Default value: 60
Feature: ASCI
411-9001-124 18.16 1.0 Page 449 of 524
timerPeriodicUpdateMS Class 3
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.
timerReselection
Description: Time hysteresis in the reselection algorithm
Value range: (5 , 10 , 15, 20)
Object: bts
Default value: 5
Unit s
Type: DP
Class 3
Release: V18 P&C4
timeSlotNumber
Description: 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
timeSlotNumber Class 2
Description: PCM time slot used by an SS7 channel on the A interface.
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).
Page 450 of 524 411-9001-124 18.16 1.0
timeSlotNumber
Description: 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.
tmu
Description: 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
tmuId
Description: Identifier of the ’tmu’ object class. This identifier is allocated by the MD-
Object: tmu
Type: DP
Release: V13
tnOffset class 2
Description: 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.
411-9001-124 18.16 1.0 Page 451 of 524
tnOffset class 2
Value range: [0..7]
Type: DP
Default value: 0
Release: V15
tNwExtUtbf Class 3
Description: Inactive period timer.
Maximum time of inactivity during which the UL radio resources are not
released.
From 0 to 250: (Step size: 20 ms)
From 251 to 255:
251 = 7 seconds
252 = 9 seconds
253 = 11 seconds
254 = 13 seconds
255 = 20 seconds
Object: bts
Default value: 0
Type: DP
Checks: • [M]: tNwExtUtbf value must be greater than or equal to tUsfExt value.
Release: V15
Note: With a PCUSN V18.0 PC5, the values 251, 252, 253, 254 and 255 of the
tNwExtUtbft parameter (during inactivity period timer) have been
changed.
Total licenses for this OMC-R

Description: Number of licenses (RM Capacity or 4K Erlangs Information) configured
on the OMC-R.
md - Display 4K Erlangs Information
Release: V17
Page 452 of 524 411-9001-124 18.16 1.0
Total unused licenses

Description: 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)
md - Display 4K Erlangs Information
Release: V17
traceConstraintList
Description: 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 GSM OMC-R Commands Reference - Security, Administration,
SMS-CB, and Help menus (411-9001-130) .
Type: DP
traceControl
Description: 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
411-9001-124 18.16 1.0 Page 453 of 524
traceDayAccessed
Description: Date of data recording
130).
Setting this parameter limits the display to trace data recorded on the
specified day.
Type: DP
traceFileName
Description: Name of a call tracing or call path tracing data file on the OMC-R agent
disks. The naming rules are described in GSM BSS Fundamentals —
Operating Principles (411-9001-007).
Object: traceFileReadyRecord
Type: DP
is case sensitive, for ALL object names (such as TRX, BSC, BTS,
traceInfoRequested
Description: List of information to display with respect to the type. See GSM OMC-R
Commands Reference - Configuration, Performance, and Maintenance
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
traceReference
Description: 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
Page 454 of 524 411-9001-124 18.16 1.0
traffic PCM allocation priority Class 2

Description: 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).
transceiver
Description: 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.
transceiver
Description: 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.
bsc object is unlocked and the parent bts object is locked.
411-9001-124 18.16 1.0 Page 455 of 524
transceiver equipment class Class 2

Description: 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 2

Description: 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
transceiverEquipment
Description: Identifier of a transceiverEquipment object defined with regard to a bts
object.
It defines the related transceiverEquipment object.
Object: software
Page 456 of 524 411-9001-124 18.16 1.0
Type: Id
Checks: • [C]: The transceiverEquipment object is created.
Description: 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.
bsc object is unlocked and the parent bts object is locked.
bsc object is unlocked, the parent btsSiteManager and bts objects are
locked, and the transceiverEquipment object is locked.
• [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 class

Description: 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
411-9001-124 18.16 1.0 Page 457 of 524
transceiver equipment class

Release: V9
Note: The transceiverZone objects are only created for bts objects that de-
scribe concentric cells.
transceiverZone
Description: 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
transcoder3GEqptId
Description: 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
transcoder
Description: 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.
Page 458 of 524 411-9001-124 18.16 1.0
transcoder
Description: 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 referenced lapdLink object (lapd LinkOMLRef) is created for
the parent bsc object.
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.
transcoderArchitecture
Description: 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
tcu3GOptical value
tcu3GOpticalHC value
transcoderId Class 2
Description: Identifier of the remote transcoder linked to the PCM link that carries the
SS7 channel on the A interface.
411-9001-124 18.16 1.0 Page 459 of 524
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.
Description: 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 2
Description: BSC 2nd class transparent attribute on bstSiteManager MO.
the Manager.
Value range: String [0 to 129]
Type: DP
Release: V14
transparentTeiAttrib2 Class 2
Description: BSC transparent attribute on bts MO. Transmitted to SUP-TEI AO and
then to the bts in LOAD_READY message.
the Manager.
Value range: String [0 to 27]
Object: bts
Type: DP
Release: V14
tResumeAck Class 3
Description: 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
Page 460 of 524 411-9001-124 18.16 1.0
tResumeAck Class 3
Object: bsc
Type: DP
Release: V15
Note: Value 0 is considered as 1 by the BSC.
trm
Description: The Transcoding Resource Module, which is responsible for GSM voc-
oding of the voice channels.
Object: trm
Type: Id
trmArchipelagoCalls
Description: 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
trmId
Description: Identifier of the ’trm’ object class. This identifier is allocated by the MD-
Object: trm
Type: DP
Release: V13
trmIncreaseCapacity Class 3
Description: Allows the TRM3 increase capacity activation.
411-9001-124 18.16 1.0 Page 461 of 524
trmIncreaseCapacity Class 3
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
The 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.
error message displayed.
tsConfiguration
Description: 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 3
Description: 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
Page 462 of 524 411-9001-124 18.16 1.0
tSuspendAck Class 3
Type: DP
Release: V15
Note: Value 0 is considered as 1 by the BSC.
tUsfExt Class 3
Description: 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.
Value range: [0..255] (1 unit = 20 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 2
Description: 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
411-9001-124 18.16 1.0 Page 463 of 524
type
• 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
type
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
type
• Fault data are restored to the "/CMN/base/save_rest" partition on the
• Observation data are restored to the "/OMC/obs" partition on the
• Trace data are restored to the "/CMN/base/save_rest" partition on the
• Other data files are restored to their source directory "/OMC/data" on
the manager disks.
Object: omc - Restore
Type: DP
Page 464 of 524 411-9001-124 18.16 1.0
type
Description: 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 several
objects
Type: DP
Release: V11
type of data to be purged

Description: Type of the OMC data to be purged.
Value range: [traceData]
Object: omc - Data purge
Type: DP
Release: V10
type of display
Description: 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.
2.21. U
ulBepPeriod Class 2
Description: 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
Type: DP
Release: V15
411-9001-124 18.16 1.0 Page 465 of 524
ulGMSKMCS1UpperThreshold Class 3
code in the UL GMSK Link Adaptation table.
Object: bts
Default value: 0
Type: DP
Release: V18 P&C5
Description: 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
code in the UL GMSK Only Link Adaptation table.
Object: bts
Type: DP
Release: V15
ulMCS1UpperThreshold Class 3
code in the UL Link Adaptation table
Object: bts
Default value: 0
Page 466 of 524 411-9001-124 18.16 1.0
Type: DP
Release: V18 P & C5
Description: 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
Type: DP
Release: V15
Object: bts
Default value: 0
Type: DP
Release: V18 P& C5
411-9001-124 18.16 1.0 Page 467 of 524
Object: bts
Type: DP
Release: V15
Object: bts
Type: DP
Release: V15
Object: bts
Type: DP
Release: V15
Object: bts
Type: DP
Release: V15
Page 468 of 524 411-9001-124 18.16 1.0
unequippedCircuit Class 1
Description: This attribute specifies if the automatic handover adaptation mechanism
is enabled/disabled.
the Manager. This attribute is modified only if the ’bts’ object instance is
unlocked.
Value range: [Enabled/Disabled]
Object: bts
Type: DP
Release: V14
unequippedCircuit Class 1
Description: 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
unit
Description: 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 3
Description: 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.
411-9001-124 18.16 1.0 Page 469 of 524
unknownNCellWarning Class 3
Object: bts
Type: DP
unmasked users alarms Class 2

Description: Configuration of the user (unprotected) external alarm loops controlled
by the BTS. When an alarm is unmasked, it means the relevant equip-
ment is monitored by the BTS. There are 6 user alarms per cabinet.
• on the S8000 Outdoor (up to 18 user alarms = 3 cabinets * 6 user

alarms per cabinet).
• on the S8002 BTS (up to 6 user alarms = 1 cabinet * 6 user
alarms)
A user alarm is used when an external equipment is inserted in the BTS
(for instance a microwave terminal) and does not require a new DLU.
Value range: [All masked, Base 1, Base 1 to 2, Base 1 to 3, Base 1 to 4, Base 1 to 5,
Base 1 to 6, Base 1 to 6 Ext0 1, Base 1 to 6 Ext0 1 to 2, Base 1 to 6 Ext0
1 to 3, Base 1 to 6 Ext0 1 to 4, Base 1 to 6 Ext0 1 to 5, Base 1 to 6 Ext0
1 to 6, Base 1 to 6 Ext0 1 to 6 Ext1 1 to 2, Base 1 to 6 Ext0 1 to 6 Ext1 1
to 4, Base 1 to 6 Ext0 1 to 6 Ext1 1 to 6]
For instance:
• Base 1: the first user alarm in the Base cabinet is unmasked

• Base 1 to 2: the first and second user alarm in the Base cabinet
are unmasked
• Base 1 to 6 Ext0 1: The 6 user alarms in the Base cabinet and the
first one in the Extension cabinet 0 are unmasked
Type: DP
Release: V9
Page 470 of 524 411-9001-124 18.16 1.0
unmasked users alarms

Value range enumerated
{ All masked, Base 1, Base 1 to 2, Base 1 to 3, Base 1 to
4, Base 1 to 5, Base 1 to 6, Base 1 to 6 Ext0 1
(if BTS9000 OUTDOOR : Base 1 to 7), Basem 1 to 6 Ext0 1 to 2 (if
BTS9000 OUTDOOR : Base 1 to 8), Base 1 to 6
Ext0 1 to 3 (if BTS9000 OUTDOOR : Base 1 to 9), Base 1 to 6 Ext0 1
to 4 (if
BTS9000 OUTDOOR : Base 1 to 10), Base 1 to 6 Ext0 1 to 5 (if
BTS9000
OUTDOOR : Base 1 to 11), Base 1 to 6 Ext0 1 to 6 (if BTS9000
OUTDOOR :
Base 1 to 12), Base 1 to 6 Ext0 1 to 6 Ext1 1 to 2 (if BTS9000
OUTDOOR : Base
1 to 13), Base 1 to 6 Ext0 1 to 6 Ext1 1 to 4 (if BTS9000 OUTDOOR :
All
unmasked), Base 1 to 6 Ext0 1 to 6 Ext1 1 to 6 (if BTS9000
OUTDOOR : Not
Applicable) }.
Object btsSiteManager
Type DP
Class 2
Release V18.0 P&C4
upAckTime Class 3 (packetAckTime)

Description: Defines the DL TBF pre-establishment timer.
Value range: [1 to 64] steps 100 ms for uplink transfer
Object: transceiver
Feature: GPRS (SV407 - V12 and TF1220 - V12.4c)
Default value:
Type: DP
Release: V12
upgradeStatus
Description: Stands whether an upgrade is complete, or is whether or not it is still in
progress.
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,
411-9001-124 18.16 1.0 Page 471 of 524
upgradeStatus (Continued)
Type: DD
Release: V13
upgradeStatus
progress.
Value range: [notInProgress / inProgress / performed / toBeUpgraded / aborted;
duplicateInProgress; frozen; failed; flashUpdated;
Unknown]
Object: igm
Type DD
Release: V18.0
upgradeStatus
progress.
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
Page 472 of 524 411-9001-124 18.16 1.0
uplinkPowerControl Class 3
Description: Whether power control in the MS-to-BTS direction is authorized at cell
level.
Type: DP
Release: V8
uplinkPwrCtrlDuringUTDOA Class 3
Object: bsc
Type: DP
Release V16
uplinkReply Class 3
Description: 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 3
Description: 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
411-9001-124 18.16 1.0 Page 473 of 524
uplinkReplyTimer Class 3
Feature: ASCI
Default value: 120
Type: DP
Release: GSM-R V15
uRxLevDLP Class 3
Description: Upper strength threshold for BTS txpwr decrease for step by step algo-
rithm.
Type: DP
uRxLevULP Class 3
Description: 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 3
Description: 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
Page 474 of 524 411-9001-124 18.16 1.0
uRxQualULP Class 3
Description: 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
usageState
Description: 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
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 list

Description: Whether the default counter list has to be used.
Value range: [yes]
411-9001-124 18.16 1.0 Page 475 of 524
use default list

Type: DP
Release: V11
user name
Description: Name of an OMC-R user as defined in the user’s profile
(default is the logged-in user’s name).
Type: DP
Checks: • [A]: The related user profile object is created on
the OMC-R.
user profile
Description: 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.
username
Description: Name of the OMC-R user, as defined in the user’s profile, who created
the job.
Type: DD
Object: job
username
Description: Name of the OMC-R user, as defined in the user’s profile, who created
the associated job.
Object: obResult
Page 476 of 524 411-9001-124 18.16 1.0
username
Type: DD
usfGranularity Class 3
Description: The type of granularity supported by PCU when dynamic allocation is
available.
Value range: [0]
Object: bts
Feature: EDGE dynamic allocation (20230)
Default value: 0 (granularity 1)
Type: DP
Release: V15
2.22. V
VEASDCCHOverflowAllowed Class 3
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
voiceBroadcastService Class 3
Description: Authorize Voice Broadcast Service.
Type: DP
Release: V12
411-9001-124 18.16 1.0 Page 477 of 524
voiceGroupCallService Class 3
Description: Authorize Voice Group Call Service.
Type: DP
Release: V12
VSWR meter Class 2

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
2.23. W
workstation name
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.
wPSManagement Class 3
Description: WPS feature is enabled or disabled.
Value range: [disabled 0 ; enabled 1]
Page 478 of 524 411-9001-124 18.16 1.0
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
wPSQueueStepRotation Class 3
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
Type: DP
Checks: [A]: The terminal profile object describing the workstation is created on
the OMC-R.
Release: V15
2.24. X
xtp
Description: Identifier of an xtp object (eXchange Termination Point) defined with re-
gard to a bsc object.
Object: xtp
Type: Id
411-9001-124 18.16 1.0 Page 479 of 524
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).
bsc object is unlocked and the xtp object is locked.
• [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.
Page 480 of 524 411-9001-124 18.16 1.0
2.25. Z
zI bss
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.
zI bss
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 other
BSCs already created.
zone frequency hopping Class 2

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
is locked.
411-9001-124 18.16 1.0 Page 481 of 524
Release: V9
zone frequency threshold Class 2

Description: Minimum number of frequencies needed to allow frequency reconfigu-
ration in the zone.
Default value: 1
Type: DP
is locked.
Release: V9
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 482 of 524 411-9001-124 18.16 1.0

411-9001-124 18.16 1.0 Page 483 of 524
A. Objects and parameters evolution
This appendix categorizes new configuration parameters and objects by release
A.1. V 18.0 P&C5 parameters
ATTENTION:
With the introduction of the A Flex - GSM Access and QAM features, the SignallingLinkSet object, which
is an instantiated object is modified (that is, some parameters from SignallingLinkSet object is copied to
a new object, remoteSignallingPoint object and some parameters are new). Following is the list of pa-
rameters, from SignallingLinkSet object which are copied to remoteSignallingPoint object:
• bssSccpConnEst
• bssSccpRelease
• bssSccpInactTx
• bssSccpInactRx
• bssSccpSubSystest
• css7LocalSubSystemNumber
• css7RemoteSubSystemNumber
• pointCode
Following are the new parameters included for this release:
Parameter Object
networkResourceIdentifierLength SignallingPoint
nullNRI SignallingPoint
remoteNodeType RemoteSignallingPoint
networkResourceIdentifierList RemoteSignallingPoint
signallingLinkSetInstancesList RemoteSignallingPoint
status RemoteSignallingPoint
adjacentPointCode SignallingLinkSet
remoteSignallingPointInstance pcmCircuit
naccInterBSCIntraPcusnActivation PCU
globalInterBscNaccActivation PCU
routingArea AdjacentCellReselection
baseColourCode AdjacentCellReselection
Page 484 of 524 411-9001-124 18.16 1.0
Parameter Object
dlGMSKMCS4UpperThreshold bts
networkColourCode AdjacentCellReselection
ftpUserPassword bscMdInterface
A.2. V18.0 Pick and choose 4 parameters

Parameter Object
highSpeedUplinkDistortionRemovalOnPacketData bts
securedLoopActivation btsSiteManager
gsmToLteReselection bts
3GReselectionOnPriority bts
lteARFCN lteAdjacentCellReselection
measurementBandwidth lteAdjacentCellReselection
ltePriority lteAdjacentCellReselection
thresholdLteHigh lteAdjacentCellReselection
thresholdLteLow lteAdjacentCellReselection
lteRxLevMin lteAdjacentCellReselection
not allowed cells lteAdjacentCellReselection
not Allowed PCIDs lteAdjacentCellReselection
PCID Bitmap Group lteAdjacentCellReselection
PCID to TA mapping lteAdjacentCellReselection
Default not allowed LTE cells bts
Default Not Allowed PCIDs bts
Default PCID Bitmap Group bts
gsmPriority bts
thresholdPrioritySearch bts
thresholdGSMlow bts
hysteresisPrio bts
timerReselection bts
3GPriority bts
threshold3Ghigh bts
411-9001-124 18.16 1.0 Page 485 of 524
Parameter Object
threshold3Glow bts
3GQRxLevMin bts
default3Gpriority bts
defaultThreshold3G bts
default3GQRxLevMin bts
3GReselection ARFCN (modified for this release) bts
A.3. V18.0 Pick and choose 3 parameters

Parameter Object
dataOnNoHoppingTS bts
bsc3000optical_ip bsc
A.4. V18.0 Pick and Choose 2 parameters
Parameter Object
AllocPriorityTimerT14Railways bts
Comment btsSiteManager
Comment bts
GsmUmtsCombBcchTeiVal bts
A.5. V18.0 Pick and Choose 1 parameters

Parameter Object
3GAccessMinLevelOffset bts
3GReselectionThreshold bts
administrativeState igm
administrativeState ipgRc
administrativeState ipm
amrWbDlAdaptationSet bts
amrWbNbMaxPdtchPreemption bts
amrWbSacchPowerOffsetSelection bts
amrWbUlAdaptationSet bts
amrWBIntercellCodecMThresh handOverControl
amrWBIntracellCodecMThresh handOverControl
Page 486 of 524 411-9001-124 18.16 1.0
Parameter Object
amrWBiRxLevDLH handOverControl
amrWBiRxLevULH handOverControl
amrWBPowerControlCIThresholdUl powerControl
availabilityStatus igm
availabilityStatus ipgRc
availabilityStatus ipm
btsType btsSiteManager
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
411-9001-124 18.16 1.0 Page 487 of 524
Parameter Object
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
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
Page 488 of 524 411-9001-124 18.16 1.0
Parameter Object
shelfNumber ipgRc
standbyStatus igm
sWVersionActive ipm
sWVersionPassive ipm
taDetectionDataExtCell bts
tfoActivation bsc
trmIncreaseCapacity transcoder
upgradeStatus igm
upgradeStatus ipm
VEASDCCHOverflowAllowed bts
A.6. New V17 parameters
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
411-9001-124 18.16 1.0 Page 489 of 524
Parameter Object
hoMarginUTRAN adjacentCellUTRAN
hoMarginAMRUTRAN adjacentCellUTRAN
hoMarginDistUTRAN adjacentCellUTRAN
hoMarginRxLevUTRAN adjacentCellUTRAN
hoMarginRxQualUTRAN adjacentCellUTRAN
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
Page 490 of 524 411-9001-124 18.16 1.0
Parameter Object
rNCId adjacentCellUTRAN
scramblingCode adjacentCellUTRAN
rxLevDLPbgtUTRAN adjacentCellUTRAN
rxLevMinCellUTRAN adjacentCellUTRAN
servingBandReporting bts
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 - md

Display 4K Erlangs - md
Total licenses for this OMC-R Display RM Capacity - bsc

Display 4K Erlangs - bsc
411-9001-124 18.16 1.0 Page 491 of 524
Parameter Object
Total licenses for this OMC-R Display RM Capacity - btsSiteManager
Total unused licenses Display RM Capacity - md

Display 4K Erlangs - md
Total unused licenses Display RM Capacity - bsc

Display 4K Erlangs - bsc
Total unused licenses Display RM Capacity - btsSiteManager

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
Page 492 of 524 411-9001-124 18.16 1.0
Parameter Object
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
privilegedCell bts
sacchPowerOffset bts
sacchPowerOffsetSelection bts
sigPowerOverboost bts
trmArchipelagoCalls trm
uplinkPwrCtrlDuringUTDOA bsc
Parameter Object
allocPriorityTable bts
allocPriorityTimers bts
amrUlHrAdaptationSet bts
amrDlHrAdaptationSet bts
amrUlFrAdaptationSet bts
411-9001-124 18.16 1.0 Page 493 of 524
Parameter Object
amrDlFrAdaptationSet bts
available synchronization sources bts
beacBatteryRemoteControllerPresence btsSiteManager
batteryRemoteControllerPresence btsSiteManager
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
Page 494 of 524 411-9001-124 18.16 1.0
Parameter Object
dlMCS2UpperThreshold bts
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
411-9001-124 18.16 1.0 Page 495 of 524
Parameter Object
masterBtsSMId btsSiteManager
msPowerClassToggle bts
nbLargeReuseDataChannels bts
numberOfJokerDS0 transceiver
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
Page 496 of 524 411-9001-124 18.16 1.0
Parameter Object
uplinkReply bsc
uplinkReplyTimer bts
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
411-9001-124 18.16 1.0 Page 497 of 524
Parameter Object
gsmToUmtsReselection bts
gsmToUmtsReselection bts
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
Page 498 of 524 411-9001-124 18.16 1.0
Parameter Object
offsetNeighbouringCell handOverControl
nFRRequestedCodec handOverControl
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
411-9001-124 18.16 1.0 Page 499 of 524
B. Parameters per feature
This appendix presents BSS parameters per feature.
B.1. A Flex - GSM Access
ATTENTION:
With the introduction of the A Flex - GSM Access feature, the SignallingLinkSet ob-
ject, which is an instantiated object is modified (that is, some parameters from Sig-
nallingLinkSet object is copied to a new object, remoteSignallingPoint object and
some parameters are new). Following is the list of parameters, from SignallingLink-
Set object which are copied to remoteSignallingPoint object:
• bssSccpConnEst
• bssSccpRelease
• bssSccpInactTx
• bssSccpInactRx
• pointCode
Following are the new parameters included in this release:
• networkResourceIdentifierLength (SignallingPoint)
• nullNRI (SignallingPoint)
• remoteNodeType (remoteSignallingPoint)
• networkResourceIdentifierList (remoteSignallingPoint)
• signallingLinkSetInstancesList (remoteSignallingPoint)
• status (remoteSignallingPoint)
• adjacentPointCode (SignallingLinkSet)
• remoteSignallingPointInstance (pcmCircuit)
Page 500 of 524 411-9001-124 18.16 1.0
B.1.1. A Flex - GSM Access Parameter Configuration Example

Following figure illustrates an example for configuring the parameters for A Flex - GSM
Access feature.
411-9001-124 18.16 1.0 Page 501 of 524
B.2. Quasi Associated Mode (QAM) - GSM Access
ATTENTION:
With the introduction of the QAM feature, the SignallingLinkSet object, which is an
instantiated object is modified (that is, some parameters from SignallingLinkSet ob-
ject is copied to a new object, remoteSignallingPoint object and some parameters
are new). Following is the list of parameters, from SignallingLinkSet object which are
copied to remoteSignallingPoint object:
• bssSccpConnEst
• bssSccpRelease
• bssSccpInactTx
• bssSccpInactRx
• pointCode
Following are the new parameters included for this release:
• networkResourceIdentifierLength (SignallingPoint)
• nullNRI (SignallingPoint)
• remoteNodeType (remoteSignallingPoint)
• networkResourceIdentifierList (remoteSignallingPoint)
• signallingLinkSetInstancesList (remoteSignallingPoint)
• status (remoteSignallingPoint)
• adjacentPointCode (SignallingLinkSet)
• remoteSignallingPointInstance (pcmCircuit)
B.2.1. QAM Parameter Configuration Example

Following figure illustrates an example for configuring the parameters for Quasi Associ-
ated Mode feature.
Page 502 of 524 411-9001-124 18.16 1.0
B.3. NACC Inter BSC/Intra PCUSN

Following are the new parameters introduced for NACC inter BSC/intra PCUSN feature
in V18 P&C5
• naccInterBscIntraPcusnActivation (PCU)
• routingArea (adjacentCellReselection)
• baseColourCode (adjacentCellReselection)
• networkColourCode (adjacentCellReselection)
B.4. NACC Inter BSC/Inter PCUSN with RIM

Following new parameter is introduced for NACC inter BSC/intra PCUSN feature in V18
P&C5
• globalInterBscNaccActivation (PCU)
B.5. EDGE Family C MCS-1 & 4 implementation

Following are the new parameters introduced for EDGE Family C MCS-1 & 4 implemen-
tation feature in V18 P&C5
• initialMCSUL (transceiver)
• initialMCSDL (transceiver)
• dlMCS1UpperThreshold (bts)
411-9001-124 18.16 1.0 Page 503 of 524
• ulMCS1UpperThreshold (bts)
• dlGMSKMCS1UpperThreshold (bts)
• ulGMSKMCS1UpperThreshold (bts)
Page 504 of 524 411-9001-124 18.16 1.0
B.6. AMR for group calls (VGCS or VBS)

• preferredNonAdaptativeAMRcodec
B.7. AMR based on traffic

• filteredTrafficCoefficient (bts)
B.8. AMR Optimizations

• amrDlFrAdaptationSet (bts)
• amrDlHrAdaptationSet (bts)
• amrUlFrAdaptationSet (bts)
• amrUlHrAdaptationSet (bts)
B.9. 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)
• 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)

411-9001-124 18.16 1.0 Page 505 of 524
B.10. BSC 3000 cell group management/load balancing

• associatedTMUPosition (btsSiteManager, signallingLinkSet, transcoder, pcu)
B.11. BSC 3000 switching increase capacity

• bscHighSwitchingCapacity (bsc)
B.12. BSC overload management

• processorLoadSupConf (bsc)
B.13. Dualband cell management

• biZonePowerOffset (adjacentCellHandOver)
• biZonePowerOffset (handOverControl)
• concentric cell (bts)
• msTxPwrMax2ndBand (bts)
• standard indicator AdjC (adjacentCellHandover)
• standard indicator AdjC (adjacentCellReselection)
• standardIndicator (bts)
B.14. EDGE dynamic allocation

• eDGEMixity (bts)
• usfGranularity (bts)
B.15. EDGE traffic management

• bEPPeriod (bts)
• edgeFavor (transceiver)
• egprsServices (bts)
• initialMCSDL (transceiver)
• initialMCSUL (transceiver)
• jokerPerMainTarget (transceiver)
• sGSNRelease (bts)
B.16. EDGE link adaptation

Page 506 of 524 411-9001-124 18.16 1.0
• ulBepPeriod (transceiver)
B.17. GSM-R V12

• additional supervised PCM 0 (btsSiteManager)
• additional unmasked users alarms (btsSiteManager)
• eMLPPThreshold (signallingPoint)
• nCHPosition (bts)
• preemptionAuthor (signallingPoint)
• preemptionConfiguration (signallingPoint)
• voiceBroadcastService (signallingPoint)
• voiceGroupCallService (signallingPoint)
411-9001-124 18.16 1.0 Page 507 of 524
B.18. GSM-R V15

• emergencyThreshold (signallingPoint)
• msPowerClassToggle (bts)
• timerGcchNotif (signallingPoint)
• uplinkReply (bsc)
• uplinkReplyTimer (bts)
B.19. 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)
• lapdTerminalNumber (lapdLink)
• longTbfLossThroughput (bts)
• longTbfSizeThreshold (bts)
• maxBsTransmitPowerInnerZone (bts)
Page 508 of 524 411-9001-124 18.16 1.0
• 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)
• pcmCircuit (pcmCircuit)
• pcmNbr (pcu)
• pcmType (pcmCircuit)
• pcu (pcu)
411-9001-124 18.16 1.0 Page 509 of 524
• pcuLapdEqptRefList (pcu)
• pcusn (pcusn)
• routingArea (bts)
• speechOnHoppingTs (bts)
• t3172 (bts)
• upAckTime (transceiver)
B.20. GPRS (TF1134 - NMO I)

• gprsNetworkModeOperation (bts)
B.21. GPRS (TF1121 - V12)

• gprsPreemption (bts)
• gprsPreemptionProtection (bts)
• gprsPriority (transceiver)
• minNbrGprsTs (bts)
B.22. GPRS TBF establishment improvement: one phase access

• onePhaseAccess (bts)
• onePhaseDnMsCapability (bts)
B.23. GPRS / EDGE Suspend and Resume

• suspendResumeActivation (bsc)
• tResumeAck (bsc)
• tSuspendAck (bsc)
B.24. PCUSN - more than 12 Agprs PCMs per BSC

• bscPcuPcmRefList (pcu)
• gprsPcuCrossConnectList (pcu)
B.25. Network Synchronization

• btsSMSynchroMode (btsSiteManager)
• dARPPh1Priority (transceiver)
• fnOffset (btsSiteManager)
• tnOffset (btsSiteManager)
B.26. BTS Synchronization

• available synchronization sources (bts)
Page 510 of 524 411-9001-124 18.16 1.0
• current synchronization mode (bts)
• masterBtsSMId (btsSiteManager)
B.27. Automatic Cell Tiering

• btsReserved3 (bts)
• hoMarginTiering (handOverControl)
• interferenceType (adjacentCellHandOver)
• intraCell (handOverControl)
• numberOfPwciSamples (handOverControl)
• selfTuningObs (handOverControl)
B.28. Handover for traffic reasons

• hoMarginTrafficOffset (adjacentCellHandOver)
• hoTraffic (bsc)
• hoTraffic (bts)
B.29. Handover decision (adjacent cell priority and load)

• offsetLoad (adjacentCellHandOver)
• offsetPriority (adjacentCellHandOver)
B.30. General protection against pingpong handover

• bts time between HO configuration (bts)
• directedRetryPrio (bts)
• hoPingpongCombination (adjacentCellHandOver)
• hoPingpongTimeRejection (adjacentCellHandOver)
• timeBetweenHOConfiguration (bsc)
B.31. Intracell handover enhancements

• lRxQualDLH (handOverControl)
• lRxQualULH (handOverControl)
411-9001-124 18.16 1.0 Page 511 of 524
B.32. AR 264
• cellReselectOffset (bts)
• penaltyTime (bts)
• temporaryOffset (bts)
B.33. Mixed hybrid and cavity combiner BTSs

• btsWithCavity (bts)
B.34. Call drop analysis

• callDropActivation (bts)
B.35. Extended CCCH

• channelType (channel)
B.36. CPU/BIFP load sharing

• cpueNumber (btsSiteManager)
B.37. Distribution on Radio measurements

• distributionActivation (bts)
• distributionDuration (bts)
• distributionTime (bts)
• distributionQualityThreshold (bts)
• fERThreshold1 (bts)
• nbOfFramesForFER (bts)
B.38. Extended UL TBF

• extUtbfNoData (bts)
• fullDlKa (bts)
• nUsfExt (bts)
• nwExtUtbf (bts)
• onlyExtUtbf (bts)
• tNwExtUtbf (bts)
• tUsfExt (bts)
Page 512 of 524 411-9001-124 18.16 1.0
B.39. Broadcast of PSI 13

• maxRACH (bts)
B.40. L1M evolutions for advanced features support

• measurementProcAlgorithm (bts)
B.41. Fast power control at TCH assignment

• new power control algorithm (bts)
B.42. Data Backhaul Evolution

• numberOfJokerDS0 (transceiver)
B.43. Disabling TBF Keep Alive

• tGMMKeepAlive (bts)
B.44. PCM error correction

• enhancedTRAUFrameIndication (bsc)
• pcmErrorCorrection (bts)
B.45. Unequipped circuit and circuit group block

• circuitGroupBlock (signallingPoint)
• unequippedCircuit (signallingPoint)
B.46. WPS public access bandwidth protection

• wPSQueueStepRotation (bts)
B.47. PS queuing management

• allocPriorityTable (bts)
• allocPriorityTimers (bts)
• allocWaitThreshold (bts)
B.48. BSC/TCU e3 GET DATA enhancement

• aterLapd (lsaRc)
• trmArchipelagoCalls (trm)
B.49. Network Assisted Cell Change for release 4 MS

• nAccActivation (bts)
• packetSiStatus (bts)
B.50. BSS Packet Flow Context

• packetFlowContext (powerControl)
• pfcActivation (bts)
• pfcArp1ConversationalCSCallProtection (powerControl)
• pfcArp1StreamingCSCallProtection (powerControl)
411-9001-124 18.16 1.0 Page 513 of 524
• 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)
B.51. BSC 3000 support of BTS background downloading

• bckgDLLayer3WindowSize (bsc)
B.52. Optimized Agprs cell allocation

• privilegedCell (bsc)
B.53. EDGE Dynamic Agprs

• dynamicAgprsAllowed (pcu)
• minNbOfJokersPerConnectedMain (transceiver)
B.54. Switch Interference Matrix

• interferenceMatrixRunningOnBts (bts)
• interferenceMatrixRunningOnBsc (bts)
Page 514 of 524 411-9001-124 18.16 1.0
B.55. Channel release policy on BTS after Abis failure

• channelReleaseOnAbisFailure (bts)
B.56. PM1270 - TDMA based counters

• monitoredObjectClass (mdWarning)
B.57. Tx power offset for signalling channels

• facchPowerOffset (bts)
• sacchPowerOffsetSelection (bts)
• sacchPowerOffset (bts)
• hrPowerControlTargetModeDl (PowerControl)
• frPowerControlTargetModeDl (PowerControl)
• sigPowerOverboost(bts)
B.58. Tx power overboost for signaling channels

• enableRepeatedFacchFr (bts)
B.59. U-TDOA support on the BSS

• uplinkPwrCtrlDuringUTDOA (bsc)
B.60. Enhanced Measurement Report (EMR) support

• servingBandReporting (bts)
• ServingBandReportingOffset (handOverControl)
B.61. 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)
411-9001-124 18.16 1.0 Page 515 of 524
• hoMarginRxLevUTRAN (adjacentCellUTRAN)
• 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)
B.62. Novel Adaptive Receiver

• adaptiveReceiver (transceiver)
B.63. 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)

Page 516 of 524 411-9001-124 18.16 1.0
B.64. Smart Power Management

• smartPowerManagementConfig (powerControl)
• smartPowerSwitchOffTimer (powerControl)
B.65. Software Preparation for BSC 3000 Optical Carriers Introduction

• synchronizingHsaRc (bsc)
B.66. AMR-HR on pre-empted PDTCH

• gprsPreemptionForHR (bsc)
B.67. Dynamic Abis interface readiness in V17

• dynamicAbis (btsSiteManager)
B.68. BSS paging coordination

• bssPagingCoordination (bts)
B.69. Permanent AAL-1 self-testing

• standbyStatus (TMU)
B.70. 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)
B.71. EDGE feature lock at OMC-R

See B.70. “AMR feature lock at OMC-R” on page 516
B.72. Abis over IP

• administrativeState (igm)
• administrativeState (ipgRc)
• administrativeState (ipm)
• availabilityStatus (igm)
• availabilityStatus (ipgRc)
• availabilityStatus (ipm)
• btsType (btsSiteManager)
411-9001-124 18.16 1.0 Page 517 of 524
• 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 518 of 524 411-9001-124 18.16 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)
B.73. AMR maximization

• fullHRCellLoadEnd (bts)
• fullHRCellLoadStart (bts)
• shared PDTCHratio (bts)
B.74. Enhanced very early assignment

• EATrafficLoadEnd (bts)
• EATrafficLoadStart (bts)
• VEASDCCHOverflowAllowed (bts)
B.75. FACCH repetition for TCH/HR

• enableRepeatedFacchHr(bts)
B.76. Fast Ack/Nack reporting

• evolvedEdgeLatRedActivation (bts)
B.77. Flexible OMC-R

• MIB version (executableSoftware)
411-9001-124 18.16 1.0 Page 519 of 524
B.78. GPRS/EDGE services on extended cell

• taDetectionDataExtCell(bts)
B.79. Multi-zone cell enhancement

• concentAlgoExtRxLevUL (handOverControl)
• concentAlgoIntRxLevUL (handOverControl)
• directAllocIntFrRxLevDL (handOverControl)
• directAllocIntFrRxLevUL (handOverControl)
B.80. TFO support

• tfoActivation (bsc)
B.81. TRM3 capacity increase

• trmIncreaseCapacity (transcoder)
B.82. 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)
B.83. Multiple ARFCN

• 3GAccessMinLevelOffset (bts)
• 3GReselectionThreshold (bts)
B.84. Additional comment field in site and sector parameters list

• Comment (btsSiteManager)
• Comment (bts)
B.85. High Speed Uplink Distortion Removal on Packet Data

• highSpeedUplinkDistortionRemovalOnPacketData(bts)
Page 520 of 524 411-9001-124 18.16 1.0
B.86. BTS Secured Loop on BSCe3

• securedLoopActivation (btsSiteManager)
B.87. 2G-4G Cell Reselection

• gsmToLteReselection
• 3GReselectionOnPriority
• lteARFCN
• measurementBandwidth
• ltePriority
• thresholdLteHigh
• thresholdLteLow
• lteRxLevMin
• not allowed cellsz‘
– not Allowed PCIDs
– PCID Bitmap Group
• PCID to TA mapping
• Default not allowed LTE cells
– Default Not Allowed PCIDs
– Default PCID Bitmap Group
• gsmPriority
• thresholdPrioritySearch
• thresholdGSMlow
• hysteresisPrio
• timerReselection
• 3GPriority
• threshold3Ghigh
• threshold3Glow
• 3GQRxLevMin
• default3Gpriority
411-9001-124 18.16 1.0 Page 521 of 524
• defaultThreshold3G
• default3GQRxLevMin
• 3GReselection ARFCN (modified for this release)

Page 522 of 524 411-9001-124 18.16 1.0
C. 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)

524

9001 124 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9001 124 PDF

Uploaded by

Copyright:

Available Formats

Kapsch CarrierCom France SAS

GSM BSS Parameter Reference

411-9001-124 Version 18.16 December 23, 2013 1.0

Global System for Mobile Communications (GSM)

Copyright © 2010-2013 Kapsch CarrierCom France S.A.S. All Rights Reserved.

411-9001-124 Version 18.16 December 23, 2013 1.0

411-9001-124 18.16 1.0 Page 3 of 524

December 23, 2013

Following feature is modified for P&C5 release:

• Trans-European Transport Network Executive Agency (TEN-T EA) features:

– “50034 - NACC inter BSC/inter PCUSN with RIM” on page 12

– “22915 - Extended Uplink TBF” on page 12

March 18, 2013

Following are the new features introduced for P&C5 release:

• “33296 - A Flex - GSM Access” on page 7

• “33296 - Quasi Associated Mode (QAM) - GSM Access” on page 8

• Trans-European Transport Network Executive Agency (TEN-T EA) features:

– “50032 - PFC restriction removal” on page 9

– “50031 - EDGE Family C MCS-1 & 4 implementation” on page 10

– “50033 - NACC inter BSC/intra PCUSN feature” on page 11

– “50034 - NACC inter BSC/inter PCUSN with RIM” on page 12

• “50035 - OMC-R installation on any SPARC platform” on page 13

• “50025 - Distinguish TX versus Rx fault at IOM” on page 13

May 21, 2012

PRM12/0000561 Deleted X.25 related information under section “BSC/TCU 3000” on

411-9001-124 18.16 1.0 Page 4 of 524

May 09, 2012

PRM12/0000479 Included the following missing parameters under appropriate alpha-

bscHopReconfUse Class 1, bscMSAccessClassBarringFunction Class 3, bts, concen-

February 14, 2012

PRM12/0000204 Updated "new password 1st try" on Page 287.

November 30, 2011

411-9001-124 18.16 1.0 Page 5 of 524

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

1.2. Different types of configuration parameters ............................................................................ 22

1.3. Description of dictionary entries.............................................................................................. 23

1.3.1. Header line ................................................................................................................... 23

2. Parameters listed in alphabetical order........................................................................... 26

2.4. C ........................................................................................................................................... 117

2.5. D ........................................................................................................................................... 156

2.6. E ........................................................................................................................................... 176

2.7. F............................................................................................................................................ 196

2.8. G ........................................................................................................................................... 208

2.9. H ........................................................................................................................................... 217

2.10. I ........................................................................................................................................... 231

2.11. J .......................................................................................................................................... 265

2.12. L .......................................................................................................................................... 266

2.13. M ......................................................................................................................................... 278

2.14. N ........................................................................................................................................ 313

2.15. O ......................................................................................................................................... 331

2.16. P ........................................................................................................................................ 353

2.17. Q ........................................................................................................................................ 382

2.18. R ........................................................................................................................................ 383

2.19. S ........................................................................................................................................ 403

2.20. T.......................................................................................................................................... 437

2.21. U ......................................................................................................................................... 464

Page 6 of 524 411-9001-124 18.16 1.0

2.22. V ......................................................................................................................................... 476

2.23. W ........................................................................................................................................ 477

2.24. X ......................................................................................................................................... 478

2.25. Z.......................................................................................................................................... 480

A. Objects and parameters evolution ................................................................................ 483

B. Parameters per feature ................................................................................................... 499