Nortel GSM BSS 13 Parameter Dictionary

Wireless Service Provider Solutions

BSS Parameter DictionaryPE/DCL/DD/0124 13.04/EN Standard March 2002411–9001–124

< 124 > : BSS Parameter Dictionary

Wireless Service Provider Solutions

BSS Parameter DictionaryDocument number: PE/DCL/DD/0124

411–9001–124Document status: StandardDocument issue: 13.04/ENProduct release: GSM/BSS V13Date: March 2002

Copyright 2000–2002 Nortel Networks, All Rights Reserved

Printed in France

NORTEL NETWORKS CONFIDENTIAL:

The information contained in this document is the property of Nortel Networks. Except as specifically authorized inwriting by Nortel Networks, the holder of this document shall keep the information contained herein confidential andshall protect same in whole or in part from disclosure and dissemination to third parties and use for evaluation,operation and maintenance purposes only.

You may not reproduce, represent, or download through any means, the information contained herein in any way or inany form without prior written consent of Nortel Networks.

The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate logo,the NORTEL Globemark, UNIFIED NETWORKS, DMS, DMS–MSC, BSC6000, S2000, S4000, S8000.GSM is a trademark of France Telecom. Sun, Ultrastation are registered trademarks of Sun Microsystems, Inc.All SPARC trademarks are used under license and are trademarks or registered trademarks ofSPARC International, Inc. in the United States and other countries. Sybase is a registered trademark of Sybase, Inc.Windows is a U.S. registered trademark of Microsoft Corp.

All other brand and product names are trademarks or registred trademarks of their respective holders.

Publication HistoryNortel Networks Confidential iii

BSS Parameter Dictionary

PUBLICATION HISTORY

System release : GSM/BSS V13

March 2002

Issue 13.04/EN Standard

Answer to CR (Change Request) Q00181313

The following parameters were added:

bscIPFirstAdr

bscIPSecondAdr

mainNetworkBand

bsMsmtProcessingMode

btsWithCavity

network protocolUsed

uplinkMappingMeasurementMode

The following parameters were modified:

geographicalCoordinates

unequippedCircuit

bscArchitecture

networkIndicator

errorCorrectionMethod

transcoderArchitecture

coderPoolConfig

signallingTerminalNumber

timeSlotNumber

associatedTMUPosition

cpueOccurrence

concentric cell

codingScheme

operationalState

positionInShelf

Nortel Networks Confidentialiv Publication History

PE/DCL/DD/0124411–9001–124

Standard 13.04/EN March 2002 GSM/BSS V13

interOmuEtherlinkOper

CTU cable

upgradeStatus

lsaRc Reference

port0X25Status

The following parameters were deleted:

bscIPAdr

protocolUsed

pwciHreqave

rxLevNCellHreqaveBeg

rxNCellHreqave

rxQualDLIH

rxQualHreqave

rxQualULIH

rxQualWtsList

selfTuningObs

lapdexists

lsaPcmList

hardwareSlotPosition

Answer to CR (Change Request) Q00216666

Updated the following parameter:

administrativeState for transceiverEquipment

October 2001

Issue 13.03/EN Preliminary

Update after internal review according to PE/DCL/GES/248 V01.01/EN

October 2001

Issue 13.02/EN Draft



Publication HistoryNortel Networks Confidential v


executableSoftwareId

executableSoftwareName

relatedSoftwares

configRefList

bscList

softwareLabel

bsc2GEqptId

tSCBNumber

tSCBUse

aLAIntState

bsc3GEqptId

bscReset

bscLogId

maxNbrConsMess

transcoder2GEqptId

transcoderAlarmList

transcoderMatrix

transcoderIntPcmIntState

transcoder3GEqptId

lapdLinkCallPLoad

coderPoolList

associatedTMUPosition

atmRmId

bscUsedAdr

ccId

cemId

cnId

iemId

inId

lsaRcId

mmsId

omuId

Nortel Networks Confidentialvi Publication History

PE/DCL/DD/0124411–9001–124


protocolUsed

sw8kRmId

tmuId

trmId

September 2001



administrativeState

availabilityStatus

operationalState

upgradeStatus

standbyStatus

positionInShelf

shelfNumber

CTU cable

lsaRc Reference

NumberOfEnabledHDLCPorts

lapdexists

lsaPcmList

privateMmsOmuRef

mmsUsage

portEthernetOperational

portEthernetStatus

X25Port0Operational

X25Port1Operational

port0X25Status

port1X25Status

Publication HistoryNortel Networks Confidential vii


System release : GSM/BSS V12

June 2001


Answer to Service Requests:

• SREE10379: Updated the class value of cpueNumber parameter(btsSiteManager object), in Chapter 2

• SREE11026: Updated the description ofnumberOfTCHFreeToEndCongestion parameter (bts object), in Chapter2

• SR30358404: Updated the value range of pointCode parameter (signallingpoint and signallingLinkSet objects), in Chapter 2

The following changes were made in individual chapters:

Chapter 2 “Parameters listed in alphabetical order”

• updated the description of maxNbrPDAAssig parameter (transceiver object)

• updated the description of maxNbrRLCEmptyBlock parameter (transceiverobject)

• completed the description of numberOfTCHFreeBeforeCongestionparameter (bts object)

V12.4 release update after internal review according to PE/DCL/GES/224V01.01/FR

April 2001



• SREE10565: updated the value range of longTbfLossThroughput parameter(bts object), in chapter 2

• SREE00527: updated the value range of intracell parameter(HandOverControl object), in chapter 2



• added the default value for several parameters

• completed the descritpion of reserved5 parameter (bts object)

Nortel Networks Confidentialviii Publication History

PE/DCL/DD/0124411–9001–124


February 2001





• removed the table in the description of adjacentCellHandOver parameter

• removed the table in the description of adjacentCellReselection parameter

• updated the value range of endCounterThreshold

• changed the class of gprsTranscvLockBtsExtendedConf

• updated the value range of log parameter

• updated the value range of longTbfLossThroughput parameter

• explained the meaning of the value range of maxRACH parameter

• updated the value range of mdScanner parameter

• updated the value range of Observed object class parameter

• changed the class of reserved1 (pcu), reserved1 (transceiver), reserved2(pcu), reserved2 (transceiver), reserved3 (pcu), reserved3 (transceiver),reserved4 (pcu), reserved4 (transceiver), reserved5 (pcu), reserved5(transceiver) parameters

• updated the value range of t3101 parameter

January 2001




• modified bscMdInterfaceVersionNumber, backup manager addressesparameters type (DI, not DP)

• completed the description of bsCvMax parameter

• added bsMsmtProcessingMode parameter

• completed the description of cellReselectHysteresis parameter

• updated the value range of circuitGroupBlock parameter following theintroduction of feature UF–1169–1 Unequipped circuit and circuit groupblock (unblock)

• completed the description of configRef parameter

Publication HistoryNortel Networks Confidential ix


• completed the description of drxTimerMax parameter following theintroduction of GPRS feature TF1220 “TBF establishment improvements”

• completed the description of gprsCellActivation parameter

• completed the description of gprsPreemption parameter

• added hexa text parameter

• updated the value range of language parameter

• completed the description of checks of msTxPwrMaxCCH parameter

• completed the description of checks of numberOfTCHQueued–BeforeCongestion parameter

• added Object Filter List parameter

• updated the value range of objects parameter

• completed the description of packetAckTime parameter according to feature“TF1220 – TBF establishment improvements”

• completed the description of pan parameter

• completed the description of reserved3 (T3168) parameter

• completed the description of reserved4 (T3192) parameter

• completed the description of sigPReserved1 parameter according to featurePM1251.1 “BSC capacity control”

• changed the name of states parameter (now called system state)

• updated the value range of unequippedCircuit parameter according to theintroduction of feature UF–1169–1 Unequipped circuit and circuit groupblock (unblock)


• SR30315339: a note was added (in June 2000, in 12.03/EN release) inbtsDescription parameter (maximum configuration loaded on one of theBTSs)

• GV00302 (clone 30340279): added the following parameters: exclusiveinterval of codano, inclusive interval of codano, exclusive list of codano,inclusive list of codano

• SR30068156 (master 30067821): completed the description of externalalarm configuration parameter and radioSiteMask parameter

• SR30334467 (master 30320056): updated the value range of maxDwAsignparameter

• SR30331543 (30328124): updated the value range of maxRach parameter

• SR EE00499 (30340234): updated the description of checks and value rangeof msTxPwrMax parameter

Nortel Networks Confidentialx Publication History

PE/DCL/DD/0124411–9001–124


• SR30315359 (30109408): changed the class of standard indicator Adjparameter

• SR30315346 (30136216): updated the value range of teiTranscoderparameter

• SREE00911: updated the value range of type parameter (new partition names)(omc object)

September 2000

Issue 12.04/EN Standard



• added additional unmasked users alarms parameter following theintroduction of the GSM–R feature “Additional external alarms on CBCFBTS – FM1158”

• added additional supervised PCMn (n=0 to 5) parameters following theintroduction of the GSM–R feature “D&I PCM fault management – FM1189”

• completed the description of gprsAvgParam parameter

• completed the description of gprsPermittedAccess parameter

• updated btsSensitivity parameter value range

• completed the description of longTbfLossThroughput parameter

• completed the description of maxDwAssign parameter

• completed the value range of reserved3 (bts) and reserved4 (bts) parameters

• updated t3101 parameter value range

• completed the description of unmasked users alarms parameter

• answer to Service Request:

– EE00527: updated intraCell parameter value range

June 2000




A note was added in btsDescription parameter (maximum configuration loaded onone of the BTSs), Chapter 2.

Publication HistoryNortel Networks Confidential xi



30104649: Data14.4OnNoHoppingTs parameter added, Chapter 2

30127416: eMLPPThreshold parameter and preemptionAuthor parameter hadtheir class changed (3 instead of 1), Chapter 2

EE00531: numberOfTCHFreeOfCongestion parameter value range update,Chapter 2

30315382: Uplink mapping rxLevUL value extension, Chapter 2

30315351: Timers T3168 and T3192, Chapter 2

30315352: Dual–band cell and power control (new parameters:btsSensitivityInnerZone and maxBsTransmitPowerInnerZone), Chapter 2

30315354: processorLoadSupConf parameter value range update, Chapter 2

30320757: password and new password 1st try parameters definition update,Chapter 2

March 2000


V12.4 release update



• added GPRS parameters

• added parameters related to feature “TF995 Automatic cell tiering”

• added parameters related to feature “TF876 Uplink mapping”

January 2000


Creation:

Chapter 1 “Introduction” contains the former Paragraphs 3.1.1 and 3.1.2 whichwere removed from NTP < 07 >.

Chapter 2 “Parameters listed in alphabetical order” contains the former Chapter 3“Dictionary of parameters” which was removed from NTP < 07 >.

Nortel Networks Confidentialxii Publication History

PE/DCL/DD/0124411–9001–124


PAGE INTENTIONALLY LEFT BLANK

Table of contentsNortel Networks Confidential xiii


About this document 0–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicability 0–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Precautionary message 0–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Audience 0–2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites 0–2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Related documents 0–2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How this document is organized 0–2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Vocabulary conventions 0–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 Introduction 1–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Network configuration objects and their parameters 1–1 . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 The different types of configuration parameters 1–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Description of dictionary entries 1–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.1 Header line 1–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.2 Main body of the entries 1–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 Parameters listed in alphabetical order 2–1 . . . . . . . . . . . . . . . . . . . . . .

A 2–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B 2–44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C 2–90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D 2–139 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E 2–154 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

F 2–175 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

G 2–179 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

H 2–185 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

I 2–193 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

J 2–203 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

L 2–204 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M 2–219 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

N 2–260 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

O 2–275 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

P 2–298 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

R 2–322 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

S 2–346 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

T 2–377 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

U 2–415 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of contents Nortel Networks Confidentialxiv

PE/DCL/DD/0124411–9001–124


V 2–423 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

W 2–425 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

X 2–426 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Z 2–430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A Objects and parameters evolution 3–1 . . . . . . . . . . . . . . . . . . . . .

A.1 New V13 parameters 3–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.1.1 New V12 parameters 3–2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.2 V12 parameters 3–2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.2.1 New V12 parameters 3–2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.2.2 Parameter updates linked to new feature introduction 3–5 . . . . . . . . . . . . . . . . . . . . . . . .

Appendix B Configuration parameter list 4–1 . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of figuresNortel Networks Confidential xv


Figure 1–1 Object main tree structure 1–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1–2 omc subtree objects 1–2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1–3 md subtree objects 1–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1–4 network subtree objects 1–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1–5 Menus in the OMC–R browser window 1–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1–6 Header line 1–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of figures Nortel Networks Confidentialxvi

PE/DCL/DD/0124411–9001–124



About this documentNortel Networks Confidential 0–1


ABOUT THIS DOCUMENTThis BSS Parameter Dictionary is a reference guide that describes all GSM BSSnetwork element parameters that can be accessed through the OMC–R.

Applicability

This document applies to the GSM900, GSM1800, and GSM1900 digital wirelesssystems.

The present edition of the dictionary applies to V13 BSS operations by default.

In V13 release, the OMC–R manages V13, V12 and V11 BSSs with BSCs 6000,12000, and 30000. Some differences or restrictions may apply when the OMC–Rmanages V12 and V11 BSSs. The user is informed when it is necessary to refer tospecific subsystem features.

The BSS Parameter Dictionary is part of the BSS NTP Suite. It is closely associatedto the following manuals:

The BSS Operating Principles Manual (NTP < 07 >) describes general operatingprinciples and explains the mechanisms that enable Man-Machine interfacecommands.

The Observation Counter Dictionary (NTP < 125 >) describes all theobservation counters used in performance management commands.

The OMC–R User Manual (NTPs < 128 > to < 130 >) is a user-oriented guide toperforming Man-Machine interface commands.

The BSS Operating Procedures Manual (NTP < 34 >) describes variousprocedures that help users operate or reconfigure a BSS.

Precautionary message

The following message:

CAUTIONGSM–R specific

Indicates that specific equipment and specific software (such asspecific software in the BSC) dedicated to Railway application isused and that therefore the feature is not available for all standardGSM users.

GSM–R specific parameters listed in this dictionary contain “GSM–R V12” in the“Feature” field.

Nortel Networks Confidential0–2 About this document

PE/DCL/DD/0124411–9001–124


Audience

This document is intended for:

OMC–R administrators

OMC–R maintenance attendants

GSM network engineers

users who want to know more about OMC–R

Prerequisites

Users must be familiar with networking principles.

They must also be familiar with the following manuals:

< 00 > : BSS Product Documentation Overview

< 01 > : BSS Overview

< 06 > : OMC–R Architecture and Reference Manual

< 07 > : BSS Operating Principles

< 16 > : TCU Reference Manual

< 22 > : BSC Reference Manual

< 32 > : OMC–R Preventive and Corrective Maintenance Manual

< 34 > : BSS Operating procedures

< 125 > : Observation Counter Dictionary

< 128 > : OMC–R User Manual – Volume 1 of 3: Object and Fault menus

< 129 > : OMC–R User Manual – Volume 2 of 3: Configuration, Performance,and Maintenance menus

< 130 > : OMC–R User Manual – Volume 3 of 3: Security, Administration,SMS–CB, and Help menus

Related documents

The NTPs listed in the above paragraph are quoted in the document.

How this document is organizedChapter 1 “Introduction” contains general information on BSS operatingparameters.

Chapter 2 “Parameters listed in alphabetical order” describes all the operatingparameters listed in alphabetical order, and explains their use.

About this documentNortel Networks Confidential 0–3


Vocabulary conventions

The glossary is presented in NTP < 00 >.

To help users operate configuration objects and parameters, the items are identifiedaccording to the release of the BSSs managed on the OMC–R. The following ruleapplies:

Vn means that the item is only significant for a BSS of release n.

Vn+ means that the item is only significant for a BSS of release n and above.

Vn– means that the item is only significant for a BSS of release n and under.

No identification means that the item does not depend on a BSS release.

Nortel Networks Confidential0–4 About this document

PE/DCL/DD/0124411–9001–124



IntroductionNortel Networks Confidential 1–1


1 INTRODUCTION

1.1 Network configuration objects and their parameters

This dictionary summarizes all the GSM BSS parameters used to define all theobjects managed on the OMC–R. An object model is used to describe each managednetwork element. Each object is defined in terms of its parameters (also calledattributes), and its relationships with other objects. A containment tree is used todepict the relationships among these objects (see Figure 1–1 to Figure 1–4). Formore information on objects and parameters, refer to NTP < 07 >, andNTP < 128 >.

root

md network omc

23 1

bscbscMdInterface

Figure 1–1 Object main tree structure

Nortel Networks Confidential1–2 Introduction

PE/DCL/DD/0124411–9001–124


omc

userProfile

terminalProfile

commandFile shortMessageuserMessage

sessionLog

job

jobResult

clearedAlarmLog currentAlarmListnotificationLogrelay

directory

alarmCriteria

machine

1

Figure 1–2 omc subtree objects



md

mdScanner bscMdInterface

traceControl

logefd mdWarning

alarmRecord

callPathTrace

mdScanReportRecord

stateChangeRecord

observationFileReadyRecordtraceFileReadyRecord

traceLogRecord

3

bsc

: Referenced objects with no hierarchical relationship: Functional objects

executableSoftware

Figure 1–3 md subtree objects


PE/DCL/DD/0124411–9001–124


network

bscMdInterface

signallingPoint

bsc

2

pcusn

signallingLinkSet

signallingLink

xtp

pcmCircuit(A)

transcoder

transcoderBoard

software

tcu

tdti

tcu e3

btsSiteManager

pcmCircuit(Abis / Ater)

lapdLink software

bsc 2G

bscCounterList

pcu

software

cem trm lsaRc

iem

: referenced objects with no hierarchical relationship

: Functional objects

bsc e3

bsc log

Figure 1–4 network subtree objects



Users can create, modify, and delete objects using commands and actions displayedin the menus of the OMC–R Browser window (see Figure 1–5). Parameters arewidely used in all commands and actions.

For more information on commands, refer to NTPs < 128 > to < 130 >:

Described in Manual < 130 > Chapter 13

Described in Manual < 130 > Chapters 9to 12








Figure 1–5 Menus in the OMC–R browser window


PE/DCL/DD/0124411–9001–124


1.2 The different types of configuration parameters

There are two types of configuration parameters: customer and manufacturerparameters.

Customer parameters:

• addressing parameters, which are relative to objects (for example: bscnumber)

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

• optimization parameters, which are relative to network tuning (for example:cellReselectHysteresis)

• operating parameters, which are relative to network operation (for example:cellBarred)

Manufacturer parameters:

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

• product parameters, which are incompatible with the current system release(for example: sWVersionbackup)

Configuration parameters are summarized in tables in Appendix A.



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 followingfigure):

the name of the OMC–R parameter

the class of the parameter (if any)

the BSS version from which it applies


PE/DCL/DD/0124411–9001–124


bssMapT20 Class 1 V8

Only DP parameters have a class.

� Class 0: the parameter can be set only beforethe application database of the parent BSC isbuilt (bdaState: “not built”).

� Class 1: the parameter can be set only whenthe parent bsc object is locked(administrativeState: “locked”).

� Class 2: the parameter can be set only whenthe object is locked and the parent bsc objectis unlocked.

� Class 3: the parameter can be set only whenthe parent bsc object is unlocked.

For more information, refer to NTP < 07 > .

parameter name

� “Vn” means the parameter applies from the VnBSS version, that is to say Vn, Vn + 1 and so on.

� “ ”: when there is no version, it means that thisparameter is applicable from the V7 BSS releasewhich was the release where the Q3 model hasbeen introduced.

Figure 1–6 Header line

1.3.2 Main body of the 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 wich allows to deactivate the function

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



type meaning is handled by the Con-figuration Managementapplication

is handled by any otherapplications (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 bythe BSC applications, and they can be consulted on operator request.

(2) : Internal parameters (DI) are stored in the OMC–R operation database (BDE)and they cannot be modified by the operator. They supply additional informationon how an object is configured at a given time, and they can be consulted onoperator request.

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

(4) : Fault Management, Performance Management, Command Functions, etc.

(5) : parameter displayed in command output

(6) : parameter entered by users

(7) : parameter which is either entered by users, or displayed in command output

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

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

Feature: Field introduced from V12. It indicates the reference of the Feature thatimpacts 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.


PE/DCL/DD/0124411–9001–124



Parameters listed in alphabetical orderNortel Networks Confidential 2–1


2 PARAMETERS LISTED IN ALPHABETICAL ORDER

A

abisSpy Class 3

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

The number of measurement reports is limited to four(respectively eight) communications per SICD (respectivelySICD8V) port.

Value range : [in progress / not in progress]Object : bts

Default value : not in progress

Type : DP

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

Note : Allowing spying increases the BSC SICD(8V) board load.

absoluteRFChannelNo Class 2

Description : Radio frequency used in the network frequency band by aradio time slot that does not obey frequency hopping laws

Setting this attribute forbids the radio time slot to obeyfrequency hopping laws.

The frequency of the radio time slot that carries a cell BCCHin a TDMA frame (channelType = “mainBCCH”,“mainBCCHCombined”, or “bcchSdcch4CBCH”) is notmanaged by users. When the parent bts object is unlocked, thesystem automatically assigns the cell bCCHFrequency to theconcerned channel object and updates it whenever it ischanged.

Value range : [1 to 124] (GSM 900 network / Extended GSM network),[0 to 1023] (GSM–R),[512 to 885] (GSM 1800 network),[512 to 810] (GSM 1900 network)

Object : channel

Condition : To define if the TDMA does not hop

Type : DP

Nortel Networks Confidential2–2 Parameters listed in alphabetical order

PE/DCL/DD/0124411–9001–124


Checks : [C/M] : The attribute is undefined when the radio time slotis authorized to hop or its channelType is“mainBCCH”, “mainBCCHCombined”, or“bcchSdcch4CBCH”.

[C/M] : The attribute is defined when the radio time slot isnot authorized to hop and its channelType is“tCHFull”, “sDCCH”, “sdcch8CBCH”, or“cCH”.

[C/M] : When defined, the frequency is one of thoseallotted to the parent bts object (cellAllocationlist).

[M] : Concentric cell: When defined, the frequency isnot used by the channel objects related to thetransceiver objects allotted to the other cell zone.

[M] : The parent bsc object is unlocked and the parentbts object is locked.

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.

accessClassCongestion Class 3 A1 V9

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

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

Object : bts

Type : DP




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

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 theuser’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 : [<date>,<time>]

Absolute time format entry forms are detailed in NTP < 130 >.


Object : Alarm logs – Filter

Type : DP


PE/DCL/DD/0124411–9001–124


activationObject

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

Value range : [1 to 255]Object : callPathTrace

Type : DP

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

[C]: The callPathTrace object is not created for the bscobject. The Call path tracing function is unique ina 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 : [1 to 255]Object : traceControl

Type : DP


[C]: The traceControl object is not created for the bscobject. The Call tracing function is unique in agiven BSS.


active (passive) chain disk state V10

Description : Chain disk state

Value range : [Working, Degraded, Partially degraded, Not significant]Object : bsc

Type : DD

Note : This parameter is only available for BSC 2G

active (passive) chain Dmux state V10

Description : State of passive equipment of chain controlled by ECI boardvia alarm loops

Value range : [working, fault]Object : bsc

Type : DD




active (passive) chain ECI board state V10

Description : Chain ECI board state


Type : DD


active (passive) chain REM link state V11

Description : Used BSC/OMC–R link state

Value range : [Working / Degraded / Partially degraded / Not significant]Object : bsc

Type : DD


active (passive) chain Sic board state V10

Description : Chain SIC chain state

Value range : [Number, card type (CCS7, SICD, SICX), internal state(working, fault)]

Object : bsc

Type : DD


active (passive) chain sic channels state V10

Description : Chain SIC channel state (LAPD and SS7 channel state)


Type : DD


active (passive) chain sls board state V10

Description : SLS board state


Type : DD



PE/DCL/DD/0124411–9001–124


active (passive) chain state V10

Description : Chain state

Value range : [nominal state, deteriorated state]Object : bsc

Type : DD


active (passive) chain switching capacity V10

Description : Chain switching capacity


Type : DD


active (passive) chain tcu accessibility V10

Description : Chain TCU state


Type : DD


active (passive) chain ute board state V10

Description : DDTI, BSCB, TSCB, and ALA board state


Type : DD


active rem link V10

Description : BSC/OMC–R link used

Value range : [rem link 0, rem link 1]Object : bsc

Type : DD




activeChain

Description : Identifier of the BSC active chain

Value range : [chainA / chainB]Object : bsc

Type : DD


additional supervised PCM 0 Class 2 V12

Description : Configuration of a new alarm controlled by a BTS in Drop andInsert configuration. The alarm is sent when a level 1transmission network link failure is detected by the BTS, andis caused by an odd PCM port connected with a physical PCMlink on the Abis interface between the BSC and one of thefollowing BTSs:

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 oddPCM link is not supervised by the BTS)]

If PCM 0 belongs to the bscSitePCMList parameter the valuesYES or NO are equivalent (recommendation: NO)

Object : btsSiteManager

Feature : GSM–R V12

Type : DP

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


PE/DCL/DD/0124411–9001–124




S8000 BTS with BCF

S8000 BTS with CBCF

S8002 BTS with CBCF

S2000 H/L BTS

e–cell





Type : DP




S8000 BTS with BCF

S8000 BTS with CBCF

S8002 BTS with CBCF

S2000 H/L BTS

e–cell







Type : DP




S8000 BTS with BCF

S8000 BTS with CBCF

S8002 BTS with CBCF

S2000 H/L BTS

e–cell





Type : DP



PE/DCL/DD/0124411–9001–124




S8000 BTS with BCF

S8000 BTS with CBCF

S8002 BTS with CBCF

S2000 H/L BTS

e–cell





Type : DP




S8000 BTS with BCF

S8000 BTS with CBCF

S8002 BTS with CBCF

S2000 H/L BTS

e–cell







Type : DP


additional unmasked users alarms Class 2 V12

Description : Configuration of the new user (unprotected) external alarmloops controlled by the BTS (added to the already existingunprotected external alarms, see parameter “unmasked usersalarms”). These additional alaarms are detected by theRECAL board of the main cabinet. When an alarm isunmasked, it means the relevant equipment is monitored bythe BTS.

There are 24 additional user (unprotected) alarms on theS8002 BTS, 14 alarms on the S8000 Outdoor BTS, and 20alarms on the S8000 Indoor BTS.

A user alarm is used when an external item of equipment isinserted in the BTS (a microwave terminal for instance) anddoes not require a new DLU.

Value range : [All alarms maskedAlarm 1 unmaskedAlarms 1 to 2 unmaskedAlarms 1 to 3 unmaskedAlarms 1 to 4 unmaskedAlarms 1 to 5 unmaskedAlarms 1 to 6 unmaskedAlarms 1 to 7 unmaskedAlarms 1 to 8 unmaskedAlarms 1 to 9 unmaskedAlarms 1 to 10 unmaskedAlarms 1 to 11 unmaskedAlarms 1 to 12 unmaskedAlarms 1 to 13 unmaskedAlarms 1 to 14 unmaskedAlarms 1 to 15 unmasked


PE/DCL/DD/0124411–9001–124


Alarms 1 to 16 unmaskedAlarms 1 to 17 unmaskedAlarms 1 to 18 unmaskedAlarms 1 to 19 unmaskedAlarms 1 to 20 unmaskedAlarms 1 to 21 unmaskedAlarms 1 to 22 unmaskedAlarms 1 to 23 unmaskedAlarms 1 to 24 unmasked ]



Type : DP

Checks : [M] : The parent bsc object is unlocked and thebtsSiteManager object is locked

addresses

Description : Definition of the OMC–R user(s) to whom the message isaddressed

Select the all option to send the message to all OMC–R users.

Select the users option to send the message to selectedOMC–R users. Enter their names as defined in their profiles[case sensitive], separated by the “&” character.

Object : user message – Answer / New message

Type : DP

adjacent cell umbrella ref Class 3 A2 V9

Description : Identifier of the adjacentCelHandOver object that describesthe neighbor cell towards which a directed retry will betriggered in BSC mode

Value range : [0 to 31]Object : bts

Type : DP

Checks : [C/M]: The preferential umbrella cell must refer to anexisting adjacentCellHandOver object instance.

[C/M]: When the function “directed retry” is made byinterrogation of the BTS, the preferentialumbrella cell must not be indicated.

[M]: The parent bsc object is unlocked.



adjacentCellHandOver V8

Description : Identifier of an adjacentCellHandOver object that defines aneighbor cell of a serving cell for handover managementpurposes. A bts object may reference up to thirty-two objectsof this type.

Value range : [0 to 31]

Object : adjacentCellHandOver

Type : Id

Checks : [C]: The associated bts object is created and theadjacentCellHandOver object is not created forthat object.

[C]: The number of adjacentCellHandOver objectscreated for a bts object is limited tomaxAdjCHOARMPerBts (static configurationdata).

[C/M]: The (baseColourCode, bCCHFrequency,networkColourCode) combination is unique inthe set including a serving cell and its neighborcells.

[C/D]: If the related BSC application database is built, theparent bsc object is unlocked.


[M/D]: The adjacentCellHandOver object is created.

[D]: If the application database of the related BSC isnot built, it has been reset by an Off line reset BDAcommand.

[D]: No mdScanner object refers to theadjacentCellHandOver object (no observation isrunning on that object).

[D]: At least one adjacentCellHandOver object shouldbe created for the bts object.


PE/DCL/DD/0124411–9001–124


adjacentCellReselection V8

Description : Identifier of an adjacentCellReselection object that definesreselection management parameters for a serving cell. A btsobject may reference up to thirty-two objects of this type.

Value range : [0 to 31]Object : adjacentCellReselection

Type : Id

Checks : [C]: The bts object is created and theadjacentCellReselection object is not created forthat object.

[C]: The number of adjacentCellReselection objectscreated for a bts object is limited tomaxAdjCHOARMPerBts (static configurationdata).


[C/D]: If the application database of the related BSC isbuilt, the parent bsc object is unlocked.

[M/D]: The adjacentCellReselection object is created.


adjCHOReserved3 Class 3 A3 V12

Description : Attribute reserved for future use

Value range : [–32768 to 32767]Object : adjacentCellHandOver

Default value :

Type : DP

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

adjCHOReserved4 Class 3 A4 V12


Value range : [–32768 to 32767]Object : adjacentCellHandOver

Default value :

Type : DP




administrativeState

Description : Activation state of an alarm criteria

An alarm criteria is created in unlocked state.

The OMC–R Fault Management function ignores the inactivecriteria when processing notifications.

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

Type : DP

administrativeState V13

Description : ISO state

Value range : [locked / unlocked]Object : atmRm

Feature : BSC/TCU e3: AR 1209

Type : DP

administrativeState


Value range : [locked / unlocked]

A bsc object is created in locked state.Object : bsc

Type : DP

Checks : [M]: If mobileCountryCode andmobileNetworkCode are defined for the bscobject, they match those of all dependent btsobjects.

[M]: The lapdLinkOMLRef attributes of alldependent transcoder objects refer to lapdLinkobjects using the same lapdTerminalNumber inthe BSC.

The following check is only performed when the bsc object isunlocked:

• The dependent software object is created and itssWVersionRunning attribute defines a software versiondownloaded to the BSC disk.


PE/DCL/DD/0124411–9001–124


administrativeState



A bscMdInterface object is created in unlocked state.

When the object is locked, the BSC involved in theBSS/OMC–R link described by this object cannotcommunicate with the OMC–R.

Object : bscMdInterface

Type : DP

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

administrativeState


A bts object is created in locked state.

When the object is unlocked, the described cell will beworking if the carrier TDMA frame (or BCCH frame) issuccessfully configured in the BTS and at least<minNbOfTDMA> TDMA frames (including the carrierframe) are operating.

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

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” ifthe application database of the related BSC is notbuilt.

The following checks are only performed when the bts objectis unlocked:

The associated handOverControl and powerControlobjects are created for the bts object.

The mobileCountryCode and mobileNetworkCodeattributes match those of the parent bsc object when they aredefined for that object.



The frequencies in the cellAllocation list comply with thestandardIndicator attribute value.

The minNbOfTDMA attribute value is less than or equalto the number of transceiver objects created for the btsobject.

Cavity cell: The number of dependent transceiver objectsequals the number of frequencies in the cellAllocation list.

Eight channel objects are created for each dependenttransceiver object if the cell works in normal mode, fourchannel objects are created for each dependent transceiverobject 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 ofthem has a channelType equal to “sdcc8CBCH” or“bcchSdcch4CBCH”.

Concentric cell:

• Two transceiverZone objects are created for the btsobject.

• Each dependent transceiver object refers to atransceiverZone object (transceiver zone Ref isdefined).

• All channel objects describing the cell BCCH orcommon channels (channelType = “cCH”) depend ontransceiver objects allotted to the outer zone.

• If frequency hopping is allowed in a zone (zonefrequency hopping), it is allowed in the cell(btsIshopping).

• The frequencies used by the transceiver objects in a zoneare separate from the frequencies used by the transceiverobjects in the other zone.


PE/DCL/DD/0124411–9001–124


Releasing a bts object by shutting down sustains the callssupported by the described cell. The system actions are asfollows:

Radio resources remain allocated until the calls end.

Once a TDMA frame is released, a CLEAR CONFIGREQUEST 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 TDMAframes are unreachable (availabilityStatus =“{dependency}”.

Notes : It is recommended to bar direct access to the cell beforeinitiating a soft release (cellBarred = “barred”), to preventoff-call mobiles from listening to the cell during the softrelease phase, so they can immediately reselect another cellfor receiving or sending calls.It is recommended also to forbid incoming handovers in thecell (incomingHandOver = “disabled”), to remove the cellfrom the list of eligible cells and, thus, avoid its selectionif the BTS receives such a request.

In order to speed up the soft release process, the ForceHandOvers command can be used first to redirect the trafficcurrently handled by the serving cell towards its neighborcells.

If a hard lock request is sent during the soft release phase,all the calls supported by the cell are immediately releasedby the BSC.

administrativeState



A btsSiteManager object is created in locked state.Object : btsSiteManager

Type : DP




The following checks are only performed when thebtsSiteManager object is unlocked:

The scheduled time slot (pcmTimeSlotNumber) ismasked in the btsSiteManager object radioSiteMask.

The radioSiteMask of all btsSiteManager objects sharinga same PCM link in the BSS are dissociated and theirscheduled time slots are different and masked in theirradioSiteMask.

The bscSitePcmList list includes at least two items if thebtsSiteManager object redundantPcmPresence attributeis “true”.

All pcmCircuit objects referenced in the list(pcmCircuitBsc components) are created for the parentbsc object and assigned to the Abis interface.

One of them identifies a PCM link with apcmCircuitBtsSiteManager reference in the range [0 to3] for clock synchronization.

The maxNbOfCells attribute value is greater than or equalto the number of bts objects created for the btsSiteManagerobject.

The configRef attribute defines a DLU file downloaded tothe BSC disk

The dependent software object is created and itssWVersionRunning attribute defines a software versiondownloaded to the BSC disk.

administrativeState

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


A callPathTrace object is created in locked state. Unlock theobjet 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 notifiedto the OMC–R agent.

Object : callPathTrace

Type : DP


PE/DCL/DD/0124411–9001–124


Notes : If trace data collecting is stopped by locking the object, theBSC continues to send the current trace messages to theOMC–R agent, but no notifications are issued.

If trace data collecting is stopped by locking the object oron reaching the end-of-session criterion, it is automaticallyrestarted whenever the callPathTrace object is unlocked.For instance, if the end-of-session criterion defines a periodof time that elapsed, data collecting will restart for theentire period.



Value range : [locked / unlocked]Object : cc


Type : DP



Value range : [locked / unlocked]Object : cem


Type : DP



Value range : [locked / unlocked]Object : cn


Type : DP



administrativeState

Description : ISO state. Locking the object blocks the transmission of theassociated messages to the OMC–R manager.

The administrativeState of an efd object is set by the user atobject creation time and can be changed with the Modifycommand.

Value range : [locked / unlocked]Object : efd

Type : DP



Value range : [locked / unlocked]Object : g3BscEqp


Type : DP



Value range : [locked / unlocked]Object : g3TranscoderEqpt


Type : DP



Value range : [locked / unlocked]Object : iem


Type : DP



Value range : [locked / unlocked]Object : in


Type : DP


PE/DCL/DD/0124411–9001–124


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.

Value range : [locked (inactive) / unlocked (active)]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–Ragent disks. A locked log object describes a log restored on thedisks.

Object : log – Display

Type : DP

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



Value range : [locked / unlocked]Object : lsaRc


Type : DP

administrativeState

Description : ISO state. Locking the object blocks the generation ofprocessed alarms when out-of-range conditions are met.

The administrativeState of an mdWarning object is set by theuser at object creation time and can be changed with theModify command.

A change of state is effective when the OMC–R is restarted.Whatever the state of the object, the related notifications arealways forwarded to the OMC–R manager.

Value range : [locked / unlocked]Object : mdWarning

Type : DP






Object : mms


Type : DP




Object : omu


Type : DP

administrativeState



A pcmCircuit object is created in locked state.

Object : pcmCircuit

Type : DP





A pcu object is created in locked state.

Object : pcu

Feature : GPRS (SV407 – V12)

Type : DP

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


PE/DCL/DD/0124411–9001–124


administrativeState



A signallingLink object is created in locked state.

Object : signallingLink

Type : DP





Object : sw8kRm


Type : DP




Object : tmu


Type : DP

administrativeState

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


A traceControl object is created in locked state. Unlock theobject to start collecting trace data in the related BSC.

Object : traceControl

Type : DP



Notes : If trace data collecting is stopped by locking the object, theBSC continues to send the current trace messages to theOMC–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 BSCwhenever the traceControl object is unlocked.

administrativeState


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


The following checks are only performed when thetransceiverEquipment object is unlocked:

The lapdLinkOMLRef and lapdLinkRSLRef attributesof the transceiverEquipment object refer to lapdLinkobjects using the same lapdTerminalNumber in theparent BSC.

The related software object is created and itssWVersionRunning attribute defines a software versiondownloaded to the BSC disk.

Releasing a transceiverEquipment object by shutting downsustains the calls supported by the described TRX/DRX andthe partnered TDMA frame. The system actions which may becarried out are the following:

To carry out a soft release. This action does notautomatically cause a handover. By carrying out thisaction, the operator must wait for the end of the comsbefore the TRX/DRX changes to “blocked”.


PE/DCL/DD/0124411–9001–124


To carry out a forced handover. A forced handover on thecell object will cause the DRX/TRX to change to“blocked” more quickly.

If the TDMA frame affected by this operation has priorityover other frames in the BSS, the BSC reconfigures thatframe on a different TRX/DRX and immediately transfersthe current calls handled by the TRX/DRX being released.

When all calls are transferred or terminated, the TRX/DRXis released (administrativeState = “locked” andoperationalState = “disabled”), and the partnered TDMAframe is unreachable if it has not been reconfigured(availabilityStatus = “{dependency}”.

Note : If a hard lock request is sent during the soft release phase, allthe calls handled by the TRX/DRX are immediately releasedby the BSC.

administrativeState



A transcoder object is created in locked state.

Object : transcoder

Type : DP


The following checks are only performed when the transcoderobject is unlocked:

All transcoder objects created for the same parent bscobject refer to lapdLink objects that use the samelapdTerminalNumber in the BSC.

<maxTranscdBPerTranscd> dependent transcoderBoardobjects are created for the transcoder object.



administrativeState



A transcoderBoard object is created in locked state.Object : transcoderBoard

Type : DP


The following check is only performed when thetranscoderBoard object is unlocked:

The related software object is created and itssWVersionRunning attribute defines a software versiondownloaded to the BSC disk.



Value range : [locked / unlocked]Object : trm


Type : DP

administrativeState


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

An xtp object is created in locked state.Object : xtp

Type : DP


[M]: It is not possible to change from “shuttingDown”to “unlocked” or from “locked” to“shuttingDown”.


The BSC will refuse to unlock a terrestrial traffic circuit thatcould break the OMC channel connection down.


PE/DCL/DD/0124411–9001–124


Releasing an xtp object by shutting down sustains the callsupported by the described terrestrial traffic circuit. Thesystem actions are as follows:

Any further attempt of the MSC to allocate the terrestrialcircuit 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 canbe softly released at the same time. If the PCM linksupports 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 immediatelyreleased by the BSC.

aLAIntState

Description : Internal state of the BSC ALA board

Value range : [working / fault]

working The board is correctly configured..

fault The board configuration was unsuccessful.. . . .

Object : bsc

Type : DD

alarm criteria

Description : Active alarm configuration

Value range : [day configuration / night configuration / specificconfiguration / reference configuration]

The active configuration is the alarm criteria configurationcurrently used by the OMC–R Fault Management function forfault processing.

The names given to the alarm operating configurations (day /night / specific) only serve to identify them. Any configurationmay be activated at any time by users, but only one can beactive at a time.

Object : omc

Type : DP



Notes : When the OMC–R is started up or the active server isswitched over, the OMC–R activates the configuration thename of which corresponds to the time of the day thatstart-up or switchover occurs. The following apply:

• The daytime configuration is activated when the eventoccurs between 9:00 a.m. and 6:00 p.m. (staticconfiguration data).

• The nighttime configuration is activated when the eventoccurs between 6:00 p.m. and 9:00 a.m. (staticconfiguration data).

The active configuration can be forced by users at any othertime. If a problem occurs while loading the selectedconfiguration, the OMC–R uses the referenceconfiguration and sends a warning message to the user.

alarm criteria

Description : Identifier of an alarm criterion on the OMC–R

Value range : [0 to 999] (manufacturer configuration), [1000 to 65535](operator configurations)

Users can manage operator configuration alarm criteria. Themanufacturer reference configuration alarm criteria can onlybe displayed.

Object : alarm criteria

Type : Id

Checks : [C]: The alarm criteria identifier is in the range [1000to 65535].

[C]: The alarm criteria does not exist in the operatorconfigurations.

[M/D]: The alarm criteria exists in the operatorconfigurations.

alarm number

Description : To select alarms with a given number


Value range : [0 to 2147483646]Object : Alarm logs – Filter

Type : DP


PE/DCL/DD/0124411–9001–124


alarm severity

Description : To select alarms according to the severity


Value range : [critical / major / minor]Object : Alarm logs – Filter

Type : DP

alarm state

Description : To select alarms according to the acknowledgement state


Value range : [acknowledged / unacknowledged]Object : Alarm logs – Filter

Type : DP

alarmDuration

Description : Alarm hold duration when a counter is involved

Value range : [0 to 345600] secondObject : alarm criteria

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

Type : DP

alarmListConverter

Description : State of the TCU converters

Value range : [working / failed]Object : transcoder

Type : DD


alarmListFan

Description : State of the TCU fans

Value range : [working / failed]Type : DD




alarmListFanBoard

Description : State of the TCU fan boards


Type : DD


alarmListVCOTension

Description : State of the TCU VCO voltage


Type : DP



PE/DCL/DD/0124411–9001–124


alarmPriority

Description : Alarm processing priority

Value range : [CLEARED / critical / indeterminate / major / minor /warning]

There are six defined priority levels which provide anindication of how it is perceived that the capability of themanaged object has been affected. The following definitionsare used:

CLEARED: The cleared severity level indicates. . . . . . the clearing of one or morepreviously reported alarms. Thisalarm clears all alarms for thismanaged object that have the sametype, probable cause, and specificproblems.

critical: The critical severity level indicates. . . . . . . . . that a service affecting condition hasoccurred and an immediatecorrective action is required.

indeterminate: The indeterminate severity level. . . . indicates that the severity level of theservice affecting condition cannot bedetermined.

major: The major severity level indicates. . . . . . . . . . that a service affecting condition hasdeveloped and a deferred correctiveaction is required.

minor: The minor severity level indicates the. . . . . . . . . . existence of a non–service affectingfault condition and that a correctiveaction should be taken in order toprevent a more serious fault.



warning: The warning severity level indicates. . . . . . . . . the detection of a potential orimpending service affecting fault,before any significant effects havebeen felt. An action should be takento further diagnose and correct theproblem in order to prevent it frombecoming a more serious serviceaffecting fault.

Object : mdWarning

Type : DP

AlgoId V8

Description : Definition of the speech algorithms used in a TCB

This parameter is a component of the algorithm Usedattribute. Refer to this entry in the Dictionary.

Value range : [full rate / enhanced full rate]Type : DP

Object : transcoderBoard

Default value : full rate

algorithm Used Class 2 V8

Description : Speech processing algorithm parameters used in the SPUprocessors of a TCB

Value range : AlgoId = [full rate / full rate & enhanced full rate],powerDownLink = [–15 to +15] dB,powerUpLink = [–15 to +15] dB

AlgoId speech algorithms used. . . . . . . . . .

powerDownLink power gain on the downlink. . .

powerUpLink power gain on the uplink. . . . . Object : transcoderBoard

Type : DP

Checks : [C/M]: The AlgoId component contains “full rate”.

[C/M]: The AlgoId component also contains “enhancedfull rate” if the parent transcoder object versionattribute value is “TCB_2”.

[M]: The parent bsc object is unlocked and thetranscoderBoard object is locked.


PE/DCL/DD/0124411–9001–124


allocationState

Description : TDMA frame allocation state

Value range : [available / not available / not significant]

available The SACCH FILLING messages. . . . . . . . containing the SYS INFO 5 and 6have been acknowledged by the BTS.

not available The SACCH FILLING messages. . . . . containing the SYS INFO 5 and 6have not been acknowledged by theBTS.

not significant The SACCH FILLING messages. . . . containing the SYS INFO 5 and 6have not been sent to the BTS by theBSC.

Object : transceiver

Type : DD

allocBitmap Class 3 V12

Description : Maximum size of the allocation bitmap provided to the MSand error rate in the cell used by the PCU to build theallocation bitmap

Value range : [maxSize / blockErrorRate]

maxSize [0 to 127] blocks

blockErrorRate [0 to 100] %


Default value : 24 blocks, 8%


Type : DP




allocPriorityTable Class 3 A5

Description : Table of eighteen elements that define the internal prioritiesfor processing TCH queued allocation requests for eachexternal priority defined (among them, fourteen are GSMpriorities)

TCH is always allocated using the internal priority.

Value range : [0 to 7]. “0” defines the highest priority.

Object : bts

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

Type : DP


allocPriorityThreshold Class 3 A6

Description : Number of free TCHs needed for processing a TCH allocationrequest with an internal priority higher than 1

These channels are reserved to allocation requests with amaximum internal priority (priority 0).

The TCH allocation is performed according to this algorithm:

Number of freeTCH = 0

1 ≤ Number of freeTCH ≤

allocPriorityThreshold

Number of free TCH> allocPriorityThre-

shold

TCHrequest ofpriority 0

– queueing ifdefined or– reject

TCH allocated TCH allocated

TCHrequest ofpriority > 0

– queueing ifdefined or– reject

– queueing if definedor– reject

TCH allocated

Value range : [0 to 2147483646]

Object : bts

Default value : 0

Type : DP



PE/DCL/DD/0124411–9001–124


allocPriorityTimers Class 3 A7

Description : Table of eight timers that defines for each internal processingpriority the maximum waiting time of TCH allocationsrequests

Value range : [0 to 2147483646] seconds

Object : bts

Default value : 0 0 0 0 0 0 0 0

Type : DP


allocWaitThreshold Class 3 A8

Description : Table of eight elements that defines for each internalprocessing priority, the maximum number of TCH allocationrequests that can be queued

A TCH request of priority Pi, P0<Pi≤P7, is queued if the totalnumber of requests of priority Pj, with j≤i, already in the queuedoes not exceed the waiting threshold of the queue “i”(element “i” of the allocWaitThreshold table).

Value range : [0 to 2147483646]

Object : bts

Default value : 0 0 0 0 0 0 0 0

Type : DP


allOtherCasesPriority Class 3 A9

Description : Index in the allocPriorityTable that defines the processingpriority of TCH allocation requests with cause “other cases”

This priority is used in primo-allocations or when an SDDCHcannot be allocated for overload reasons.


Object : bts

Default value : 17

Type : DP




answerPagingPriority Class 3 A10

Description : Index in the allocPriorityTable that defines the processingpriority of TCH allocation requests with cause “reply topaging”

This priority is used in signaling mode on TCH only.


Default value : 17

Type : DP


architecture

Description : Architecture of the OMC–R agent in terms of servers. It isprovided 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 runningdual servers runningsingle server running]

Object : md – Display

Type : DP

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

assignRequestPriority Class 3 A11

Description : Index in the allocPriorityTable that defines the processingpriority of TCH allocation requests with cause “immediateassignment”

This priority is used when radio resource allocation queueingis not requested by the MSC or not authorized in the BSS (referto the bscQueueingOption entry in the Dictionary).


Default value : 17

Type : DP



PE/DCL/DD/0124411–9001–124


associatedInterface

Description : Interface on which a LAPD link is used

Value range : [Abis / Ater / Agprs]

A LAPD link used on the Abis interface carries BTS signaling.A LAPD link used on the Ater interface carries TCU signaling.A LAPD link used on the Agprs interface carries PCUsignaling.

Object : lapdLink


Type : DP

Checks : [C]: The value is whether “Abis” or “Agprs” if thelapdConcentration attribute value is “disabled”.

[C]: The value is whether “Abis” or “Ater” if thelapdConcentration attribute value is “enabled”.

[C]: The “Agprs” value is only allowed for PCUlapdLink interface from V12 BSCs.

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


associatedLog

Description : Identifier of the log object that describes the associated recordson the OMC–R agent disks

For an mdScanner object, this attribute is displayed providedmdLog = “logged”.

Value range : [0 to 2147483646]Object : callPathTrace, mdScanner, traceControl – Display

Type : DI

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

associatedTMUPosition V13

Description : Indicates the TMU position. Dynamically managed by theBsc.

Value range : [{0 to 1} / {1 to 15}]Object : btsSiteManager

Type : DP



atmRmId V13

Description : Identifier of the ‘atmRm’ object class. This identifier isallocated by the MD–R at object creation, depending on theshelf and slot numbers indicated by the BSC. This attributecannot be modified. This attribute is relevant for BSC e3.

Value range : [0 to 2147483646]

Object : atmRm

Type : DP

Attenuation Class 2 A12 V9

Description : Attenuation due to coupling system losses. This value dependson the BTS configuration and should not be modified by theoperator.

Value range : [0 to 14] dB


Default value : Depends on the equipment

Type : DP

Checks : [M] : The parent bsc object is unlocked and thebtsSiteManager is locked

Note : If the Attenuation parameter is not set (value = NULL), thenthe DLU attenuation value is used.

If the Attenuation parameter is set [0 to 14] then the DLUattenuation is replaced by the OMC attenuation parameter.


PE/DCL/DD/0124411–9001–124


auditBdaStatus

Description : Synthetic result of a BDA audit

Value range : [no difference / some differences (see list below) / manydifferences (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 arelisted in the session logs).

many differences More than ten object instances are. . different in BDA and BDE (the firstten are listed in the session logs).

Object : bsc

Type : DI

auditState

Description : Whether an audit is in-progress in the BSC. Access to a BSCare blocked whenever an audit of its application database isin-progress (Audit BDA command).

This attribute is unknown to the BSC and cannot be directlymodified by users.

When an audit is in-progress in a BSC, all configurationcommands involving the BSS are forbidden.

Value range : [inProgress / notInProgress]

Object : bsc

Type : DI

authorised user

Description : List of the users authorized to copy, display and run thecommand file. Enter their names as defined in their profilesand use the “&” character to separate them.

Object : commandFile

Type : DP



availabilityStatus


Refer to the operationalState entries in the Dictionary for adescription of possible state parameter combinations for theseobjects: administrativeState, availabilityStatus,operationalState.

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

Object : bsc, bscMdInterface,btsSiteManager,lapdLink, pcmCircuit,signallingLink, transceiver,transceiverEquipment, transcoder,transcoderBoard

Type : DD

availabilityStatus


The “enabled” state for a bts object is a transitory state thatfollows a soft release request. Refer to theadministrativeState entry related to the bts object in theDictionary.


Object : bts

Type : DD

availabilityStatus


The “logFull” state applies to a log object that describes anobservation or trace log, and indicates that the saving messagedirectory on the OMC–R agent disks is full. Refer to thecapacityAlarmThreshold entry in the Dictionary.

Value range : [{} / {logFull}]

Object : log

Type : DP


PE/DCL/DD/0124411–9001–124


availabilityStatus


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

Object : mdScanner

Type : DD

availabilityStatus V12


Refer to the operationalState entry in the Dictionary for adescription of possible state parameter combinations:administrativeState, availabilityStatus, operationalState.

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


Type : DD

availabilityStatus V12


Refer to the operationalState entry in the Dictionary for adescription of possible state parameter combinations:availabilityStatus and operationalState.

Value range : [{} / {dependency}]Object : pcusn


Type : DD

availabilityStatus


Refer to the operationalState entry in the Dictionary for adescription of possible state parameter combinations:administrativeState, availabilityStatus, operationalState, andusageState.

A state change notification is issued after the soft release.

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

Type : DD



averagingPeriod Class 2 A13

Description : Number of SACCH multiframes over which the interferencelevels are averaged. This averaging will be performedimmediately before the transmission of the RESOURCEINDICATION message.

This attribute, together with the “thresholdInterference”attribute, allows users to manage interferences in radio cells.Refer to this entry in the Dictionary.

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

Object : handOverControl

Default value : 20

Type : DP

Checks : [M]: The parent bsc object is unlocked and theassociated bts object is locked.


PE/DCL/DD/0124411–9001–124


B

backup manager addresses

Description : Backup addresses of the OMC–R manager that receives themessages. 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 providedby the OMC–R agent.

In a mono-server configuration with redundancy, this attributeis not filled in.


Type : DP

baseColourCode Class 3

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, networkColourCode)combination is unique in the set including a servingcell and its neighbor cells.




baseColourCode Class 2 B2

Description : Base station Color Code assigned to a serving cell. It isbroadcast on the cell SCH and is used to distinguish cells thatshare the same BCCH frequency.

The (BCC, NCC) pair forms the cell BSIC.

The information is broadcast on the cell SCH.

Several BCCs may be assigned to a same BTS. Hence,different codes can be allotted to cells that may haveoverlapping 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 beused to increase BCC color possibilities when the NCC is notneeded.


Object : bts

Type : DP

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

[M]: The parent bsc object is unlocked and the btsobject is locked.

bCCHFrequency Class 3

Description : Radio frequency allocated to a neighbor cell BCCH in thenetwork frequency band

The information is broadcast on the serving cell SACCH.



Type : DP


PE/DCL/DD/0124411–9001–124



[M]: The bCCHFrequency value must be setaccording to the standardIndicator attribute.



Description : Radio frequency used for selection and reselectionmanagement

The information is broadcast on the serving cell BCCH.


Object : adjacentCellReselection

Type : DP

Checks : [M]: The bCCHFrequency value must be setaccording to the standardIndicator attribute.


Note : An adjacentCellReselection object can use the same BCCH asthe serving cell to which it is associated. This allows a mobileto immediately recover the cell on which it was “camping”after being switched off, then switched back on, and isespecially useful in the selection process.


Description : Radio frequency allocated to a cell BCCH (Broadcast ControlCHannel) in the network frequency band

The information is broadcast on the cell SACCH.

The BCCH frequency is automatically assigned to the radiotime slot carrying the cell BCCH when the cell is brought intoservice (absoluteRFChannelNo attribute of the channelobject describing the carrier TDMA frame TS0). It isbroadcast to the radio time slot whenever modified.



The BCCH is used by the BTS for broadcasting cell relatedsystem information to MS, such as frequency band and list offrequency channels used, authorized services and accessconditions, list of neighbor cells, and radio parameters(maximum transmission strength, minimum receptionstrength, etc).


Object : bts

Type : DP

Checks : [M]: The BCCH frequency is included in thecellAllocation list.

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

[M]: For a dualband cell, the bCCHFrequency attributemust be in the primary band of frequencies.


bda activation type V11

Description : Whether the Build BDA should be automatic or commanded

See to NTP < 128 > .

Value range : [automatic / commanded]

Object : bsc – Build BDA

Type : DP

Remark : For a V11+ BSC the value can be as follows:

“automatic”: basic BDA change without prototype BDAchange

“commanded”: basic BDA change without prototype BDAchange or BSC upgrade with prototype BDA change (BSCEdition Upgrade or BSC Version Upgrade)

For a V10 BSC the value must be “automatic”.


PE/DCL/DD/0124411–9001–124


bdaNewBscState V11

Description : Current bsc state related to the new BDA

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

Object : bsc

Type : DI

Remark : This attribute is modified by the OMC–R agent whenprocessing “end of probative phase”, “Activate New BDA”,“On line reset BDA”, or “On–line reset cancel” actions orreceiving an unsolicited message sent by the BSC.

This attribute is NULL { } as long as the BSC has not beenconnected 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 thefollowing occurrences:

• BSC complete restart

• “end of probative phase” or BDA “new” activation orreset on–line cancel succeeded

• partial or complete spontaneous BSC restart

• BSC operating command aborted“running on–line reset”: BSC reset on–line is beingexecuted

“waiting for on–line build”: BSC reset on–line hassucceeded

“waiting for software change”: “BDA version” reseton–line has succeeded

“waiting for Bda change”: “BDA edition” reset on line hassucceeded

“running software change”: BSC Type 5 EFT activation isbeing executed

“running Bda change”: BSC BDA “new” activation isbeing executed

“waiting for end of probative phase”: BSC Type 5 EFTactivation has succeeded



bdaSelected V11

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 “Online reset BDA” actions or receiving a BSC spontaneousevent.

This attribute is set “running” at the bsc object instancecreation

For a V10 BSC, this attribute is never modified and its valueis “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

bdaState

Description : Whether the BSC application database (BDA) is built. Notransactions with a BSC can be implemented prior to buildingits application database.

When a bsc object is created or following a user Off line resetBDA command, the value of this attribute is “not built”.

This attribute is unknown to the BSC and cannot be directlymodified by users. It is updated by the system after a user BuildBDA command.

Value range : [built / not built / inconsistency]

Object : bsc

Type : DI


PE/DCL/DD/0124411–9001–124


bdaVersionBuild

Description : Version number of the BSC application database forrebuilding purposes

When the BSC is initialized or following a user Off line resetBDA command, the value of this attribute is “0” (BDA notbuilt). The BSC then sends a “build database request”message, indicating that its database is defective and needsrebuilding.

By issuing a Build BDA command, the user informs theOMC–R that the BSC database must be regenerated.

Value range : [1 to 254]Object : bsc – Build BDA

Type : DP

Checks : [A]: If the command follows a BSC architecturechange, the new architecture complies with theinformation in the last “build database request”message received from the BSC.

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 isassigned the bdaVersionBuild value sent with the user buildcommand.

If the BDA is being regenerated following an On line resetBDA command, this attribute gives the user the versionnumber of the BDA currently used by the BSC.

Value range : [0 to 254]Object : bsc

Type : DD

Beginning date

Description : To select call monitoring data recorded on that date and after

Do not fill in if information produced from the start should bedisplayed.

Value range : [mm/dd/yyyy hh:mm:ss]Object : Call monitoring – Display SDO

Type : DP

Checks : [A]: Beginning date is on or before End date.



beginSearchTime

Description : Absolute time to start searching for the observation reports tocumulate

Observation data accumulating starts with the informationcontained in the last observation message collected in therequested period of time. Refer to the partneredendSearchTime entry in the Dictionary.


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

beginSearchTime

Description : Absolute time to start searching for the observation report toedit default is the current date and time)

The report displays the information contained in the lastobservation message generated in the requested period of time.Refer to the partnered endSearchTime entry in theDictionary.



Object : Display raw report

Type : DP



PE/DCL/DD/0124411–9001–124


beginSearchTime

Description : Absolute time to start searching for the available temporaryobservations to list (default is the current date and time)

The first listed report is the last observation report generatedin the requested period of time. Refer to the partneredendSearchTime entry in the Dictionary.


Value range : [<date>,<time>]Object : List available temporary observations

Type : DP


beginSearchTime

Description : Absolute time to start searching for the observation messagesto list (default is the current date and time)

The first listed message is the last observation messagegenerated in the requested period of time. Refer to thepartnered endSearchTime entry in the Dictionary.



Object : List observation messages

Type : DP




biZonePowerOffset Class 3 B3 V12

Description : Power offset between the inner TRXs and the outer TRXs ofthe adjacentCellHandOver object of a dualband,dualcoupling, or concentric cell.

Offset added in calculation formula to draw up the list ofeligible cells for handover towards a dualband, dualcoupling,or concentric cell inner zone to take into account the differenceof propagation models between the two bands of the cells andthe difference of transmission power between TRXs of the twozones due to either BTS configuration or coupling.

Value range : [–63 to 63] dB


Default value : 63

Type : DP

Feature : Dualband cell management (TF875 – V12)


Note : This parameter is only available for S8000 or e–cell BTS DRXtransceiver architecture.

biZonePowerOffset Class 3 B4 V12

Description : Power offset between inner and outer TRXs of thehandOverControl object of a dualband, dualcoupling, orconcentric cell.



Default value : 3

Type : DP



Note : This parameter is only available for S8000 or e–cell BTS DRXtransceiver architecture.

• zoneTxPwrMaxReduction (inner zone)

bsc2GEqptId V13


PE/DCL/DD/0124411–9001–124


Description : Identifier of the ‘bsc2GEqpt’ object class. This identifier isallocated by the MD–R at object creation. The only valueallocated by the MD–R is 0. This attribute cannot bemodified. This attribute is relevant for BSC 2G.

Value range : [1 to 255]Object : bsc2GEqpt

Type : DP

bsc3GEqptId V13

Description : Identifier of the ‘bsc3GEqpt’ object class. This identifier isallocated by the MD–R at object creation. The only valueallocated by the MD–R is 0. This attribute cannot bemodified. This attribute is relevant for BSC e3.


Type : DP

bsc

Description : Identifier of a bsc object on the OMC–R.

The bsc reference is part of all BSS configuration objectidentifiers.

In all MMI commands, a bsc object can be referenced by name(bscName).

When a bsc object is created and the referencedbscMdInterface object is unlocked, the system attempts toestablish the BSS/OMC–R link connection.


Type : Id

Checks : [C]: The number of BSCs managed by an OMC–R islimited to maxBscPerNetwork (staticconfiguration data).

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

[D]: The BSC application database has been reset by anOff line reset BDA command (bdaState = “notbuilt”).

[D]: No mdScanner, traceControl, or callPathTraceobject refers to the bsc object (no observation ortrace 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, multiple site, pcmCircuit,powerControl, signallingLink, signallingLinkSet,signallingPoint, software, transceiver,transceiverEquipment, transceiverZone, transcoder,transcoderBoard, xtp

Type : Id


bsc equipment name

Description : To select messages issued by a given type of BSC or TCUprocessor


Value range : [ddti / ala / eci / sicx / sicd / swm / cpue / O.M.N.communication / cabling and PCM cross connect / css7 /cpu486Se / sup / LAPD channel / signalling link / sls / tdti /tuc / internal PCM–TCU / tcb / swe / swc / sw16 / tscb / msw/ sic lapd (8 channels) / 2nd generation of TCB board / bscb/ CPUE pentium 120 / mmu / mmu ide / cpum133 / cpue133/ sup2 / sls2 / pcu element]

Object : Alarm and notification logs – Filter


Type : DP

Remark : “css7” identifies the BSC CCS7 boards; “signalling link”identifies the SS7 signalling links defined in the BSS andcontrolled by the CCS7 boards.


PE/DCL/DD/0124411–9001–124


BSC list

Description : List of the BSCs simultaneously monitored for further dataprocessing by the SDO machine. Fill in the list with BSCreference numbers or names, up to maxBscPerNetwork.

Do the following to create the list:

To add a BSC, fill in the BSC number field with thereference number of the BSC on the OMC–R and click Add.

To remove one or more BSCs, select the lines that displaytheir reference numbers and click Remove.

When the list is complete, click the option matching thedesired command, 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 ofresultant ASCII data files isproduced, it is identified as the Level1 set.


Object : Call monitoring – Commands (SDO)

Type : DP

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

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

Notes : The user must make sure that the BSCs in the list are createdon the OMC–R since no checks are performed by thesystem.



Processing: The call monitoring data files are meant toexist in the “/MD/ftam/bsc” directory on the OMC–R agentdisks. For each BSC in the list, all files saved in thatdirectory whose name begins with “SDO_CM_BSCnnn”will be processed: “nnn” is the BSC reference number onthe OMC–R (if bsc = 5, then nnn is read “005”). See toNTP < 07 >.

The BSC list needs not be defined when selecting the Querycommand which displays the activity state of the Callmonitoring function in all the BSCs connected to theOMC–R.

bsc model

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

Value range : [bsc 12000 / bsc 6000 / bsc 2000]

Do not fill in if this criterion is not to be selected.Object : Alarm and notification logs – Filter

Type : DP

BSC number

Description : Identifier [1 to 255] or name of a BSC to add to the BSC list

Fill in this field and click Add to add the BSC to the list. Referto the BSC list entry in the Dictionary.

Object : Call monitoring – Commands (SDO)

Type : DP

bscAlarmMask Class 3

Description : Configuration of the eight external alarm loops managed bythe BSC ALA board. The alarm loop number “32+n” ismonitored (not monitored) when the nth bit is set to 1 (0).

Value range : 8 bit register numbered 0 to 7

bscAlarmMask = x x x x x x x x

| |

alarm 39 alarm 32

Object : bsc

Default value : 11111111

Type : DP

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


PE/DCL/DD/0124411–9001–124


bscArchitecture Class 0

Description : Architecture of the BSC

This attribute, together with the bsc object bscType attributeand the related software object sWVersionRunning attribute,defines the dimensioning constraints.

Value range : [bsc6000 / bsc12000 / bsc30000]Object : bsc

Default value : BSC6000 (for V8 and lower BSC release)

Type : DP

Checks : [C/M]: The type of the BSC (bscType) complies with thenew architecture.

[M]: The BSC application database is reset (bdaState= “not built”).

bscChainId

Description : BSC processing chain(s) to reset

The consequences are as follows:

activeChain: The active chain is reset and becomes. . . . . . passive, and the passive chainbecomes active. Class 1 DPs are notreconfigured.

passiveChain: The passive chain is reset if it can be. . . . . reached.

bothChain: Both chains are reset and the BSC is. . . . . . . restarted. Class 1 DPs arereconfigured.

Value range : [activeChain / passiveChain / bothChain]Object : bsc – Kill chain

Type : Id

bscCounterList V11

Description : Identifier of the bscCounterList object defined with regards tothe bsc object

Value range : [0 to 2147483646]Object : bscCounterList

Type : Id

Default value :



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 tothe concerned BSC.

It is also updated by the OMC–R agent in the followingconditions:

A user Set command on the md object is run, which changesits externalTime 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–Rmanager when the time difference with a BSC drifts too much.

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

Type : DD

bscGprsActivation Class 3 V12

Description : Flag used to activate the GPRS at BSC level

Value range : [disabled / enabled]

Object : bsc


Type : DP

Default value : disabled



PE/DCL/DD/0124411–9001–124


bscHopReconfUse Class 1 B5 V8

Description : Whether frequency hopping reconfiguration is authorized inBTSs that use cavity coupling

When frequency reconfiguration is authorized, it allows toautomatically reconfigure the hopping sequence whenever afrequency is lost or recovered in the BTS.

Value range : [true / false]

Object : bsc

Default value : True

Type : DP

Checks : [M]: It can be “true” provided thebtsHopReconfRestart of one of the related btsobjects is also “true”.

[M]: The bsc object is locked.

bscIPFirstAdr V13

Description : Indicates the first BSC IP address used for a ’bscMdInterface’object instance.

IP address corresponds to the subscriber number on thenetwork used.

At least one IP address must be specified if protocolUsed is IP;it may be specified otherwise.

This attribute is modified by the Manager.

Value changes are notified to the Manager.

This attribute can be modified only if the ’bscMdInterface’object instance is locked.

Value range : [7 to 15] String


Type : DP



bscIPSecondAdr V13

Description : Indicates the second BSC IP address used for a’bscMdInterface’ object instance.

IP address corresponds to the subscriber number on thenetwork used.

At least one IP address must be specified if protocolUsed is IP;it may be specified otherwise.


Value changes are notified to the Manager.

This attribute can be modified only if the ’bscMdInterface’object instance is locked.



Type : DP

bscList V13

Description : This attribute indicates for which BSC(s) the units of softwarehas been downloaded. This attribute is allocated by the MD–Rat object creation. This attribute cannot be modified by theManager. This attribute is updated by the MD–R when a“sWDownload” command is performed successfully.Value changes are notified to the Manager.


Object : executableSoftware

Type : DP

bscLogId V13

Description : Identifier of the ‘bscLog’ object class. This identifier isallocated by the MD–R at object creation. This attributecannot be modified. This attribute is relevant for BSC e3.

Value range : [ bscVers13 +Inf ]

Object : bscLog

Type : DP


PE/DCL/DD/0124411–9001–124


bscMdInterface

Description : Identifier of a bscMdInterface object defined with regard tothe md object

Value range : [0 to 255]Object : bscMdInterface

Type : Id

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

bscMdInterfaceRef

Description : Identifier of the bscMdInterface object that describes theBSS/OMC–R link involving the BSC


Type : DP

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


bscMdInterfaceVersionNumber

Description : Release number of the BSC/OMC–R interface. It is providedby the BSC when the BSS/OMC–R link is physicallyestablished.

If the release number does not match the software versionrunning in the BSC (sWVersionRunning attribute of therelated software object), the BSC issues a start-of-faultmessage.

Value range : [11 to 99]Object : bsc – Display

Type : DI


bscMSAccessClassBarringFunction Class 3 B6 V9

Description : Enable or disable dynamic barring of access class at the bsclevel

Value range : [enabled / disabled]Object : bsc


Type : DP




bscName V13

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.

bscPcuPcmRefList Class 2 V12

Description : List of BSC–PCU PCM link numbers

Value range : [1 to 12] values in the range [0 to 47]

Object : pcu


Type : DP

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

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

[C/M]: The referred pcmCircuit object instances must notbe already referred to another pcu object instanceon the same BSC.

[M]: The parent bsc object is unlocked and the pcuobject is locked.

Note : Only one Agprs PCM is used to connect the BSC and one PCU.


PE/DCL/DD/0124411–9001–124


bscQueueingOption Class 1 B7

Description : Whether radio resource allocation requests are queued in theBSC when no resources are available

If no resource is available when an allocation request isreceived and queueing is not allowed, the allocation request isrefused immediately.

Value range : [allowed (MSC driven) / forced (O&M driven) / not allowed]

allowed Resource allocation request queueing. . . . . . . . . . depends on the type of operation andindicative items provided with themessages received from the MSC.

forced Resource allocation request queueing. . . . . . . . . . . depends on the type of operationonly.

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

Object : signallingPoint

Default value : forced

Type : DP

Checks : [M]: The bsc object is locked.

Note : Allocation requests for immediate assignments and inter-bss,intra-bss, and inter-bts handovers are never queued. Only TCHresource requests (assigments request and intraCell handover)are queued depending on the priority of the demand and thenumber of request present in the queue.

bscRefList Class 3 V12

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

Value range : [1 to 12] values in the range [0 to 2147483646]Object : pcusn

Type : DP


bscReset V13

Description : Requests a control node reset


Type : DP



bscSitePcmList Class 2

Description : List of the PCM links allotted to a site on the Abis interface,up to maxPcmCPerBtsSM. Each link is identified by a(pcmCircuitBsc, pcmCircuitBtsSiteManager) pair thatdefines it on BSC end and BTS end.

The Abis interface connects a BTS to a BSC through PCMlinks that are identified by the boards to which they areconnected on both ends of the interface, that is DDTI boardson BSC end and DTI boards on BTS end.

The following rule is applied:

A PCM link connected to DDTI board no.i in the BSC has apcmCircuitBsc reference equal to “2i” or “2i+1” withregard to the BSC (each board manages two links at a time).Refer to BSC Reference Manual.

The same PCM link connected to DTI board no.j in the BTShas a pcmCircuitBtsSiteManager reference equal to “j”with regard to the BTS (each board manages one singlelink). Refer to BTS Reference Manuals.

The number of pairs in the list sets the number of links allottedto the radio site.

Value range : [0 to 2147483646] (pcmCircuitBsc),[0 to 5] (pcmCircuitBtsSiteManager)


Type : DP

Checks : [C]: The number of PCM links allotted to a site islimited to maxPcmCPerBtsSM (staticconfiguration data).

[C/M]: The list contains at least one pair, two if thebtsSiteManager object redundantPcmPresenceattribute is “true”.

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


PE/DCL/DD/0124411–9001–124


[C/M]: Each pcmCircuitBsc reference matches apcmCircuit object created for the parent bsc objectand assigned to the Abis interface (pcmType =“pcmAbis”).

[M]: If a pcmCircuitBsc reference is changed, thecurrent link is not used by any dependenttransceiverEquipment object.

[M]: The parent bsc object is unlocked and thebtsSiteManager object is locked.

bscTimeSlot

Description : PCM link (pcmCircuitId) and time slot (timeSlotNumber)used by the radio time slot on the Abis interface. The PCMlink is identified on BSC end [0 to 47].

The information is displayed provided the parent transceiverobject is working. Refer to the operationalState entry for thisobject in the Dictionary.

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

Object : channel

Type : DD



bscType Class 0

Description : Type of the BSC. It defines the BSC configuration in terms ofequipment boards.

See the table listing BSC configuration types in NTP < 07 >.

Value range : [type1 / type2 / type3 / type4 / type5]Object : bsc

Default value : type5

Type : DP

Checks : [M]: number of SICD(8V) ports available in the BSC:See NTP < 07 >.

[M]: number of PCM links connected to the BSC: SeeNTP < 07 >.

[M]: number of sites managed by the BSC: SeebtsSiteManager entry in the Dictionary.

[M]: The lapdTerminalNumber attributes of thedependent lapdLink objects comply with thenumber of SICD(8V) ports available in the BSC.

[M]: The BSC application database is reset (bdaState= “not built”).


bscUsedAdr V13

Description : BSC address actually used. This attribute is managed by theMD–R. Value changes are not notified to the Manager.

Value range : [X25 / IP]Object : bscMdInterface

Type : DP

bsCvMax Class 3 V12

Description : Number of packets left to transmit divided by the number ofUL TS allocated to the MS.


Default value : 1


Type : DP


Comments : bsCvMax is broadcast in the system information.


PE/DCL/DD/0124411–9001–124


bscX25PrefAdr Class 2

Description : X.25 priority address used by the BSC.It corresponds to the subscriber’s number in the X.25network.

Value range : [15 decimal figures max]


Default value : $BSC{bscId}_X25P

Type : DP

Checks : [C/M]: The X25 address must not already be used in apreferential address for another bsc objectinstance.

[C/M]: The X25 address must not already be used in asecondary address for another bsc object instance.

[M]: The bscMdInterface object is locked.


bscX25SecAdr Class 2

Description : X.25 address used by the BSC as backup. It is identical to thepriority address when there is no redundancy.It corresponds to the subscriber’s number in the X.25network.



Default value : $BSC{bscId}_X25S

Type : DP

Checks : [C/M]: The X25 address must not already be used in asecondary address for another bsc object instance.

[C/M]: The X25 address must not already be used in apreferential address for another bsc objectinstance.

[M]: The bscMdInterface object is locked.




bscX25UsedAdr

Description : X.25 outgoing address currently used by the BSC

This dynamic attribute allows the user to know the addressselected by the system when the connection is established bybringing the link into service.



Type : DD


bsMsmtProcessingMode Class 2 B8

Description : Whether radio measurements collected by the mobiles for acell are processed by the BTS or the BSC

Value range : [preProcessedMeasurementReporting (BTS) /basicMeasurementReporting (BSC)]

Object : bts

Default value : preProcessedMeasurementReporting

Type : DP

Checks : [C/M]: The attribute value equals“preProcessedMeasurementReporting”.


Remark : Since radio measurements are always preprocessed by theBTS, changing this attribute has no meaning.

bsPowerControl Class 3 B9

Description : Whether BTS transmission power control is allowed at celllevel

Value range : [enabled / disabled]

Object : powerControl


Type : DP



PE/DCL/DD/0124411–9001–124


bssMapT1 Class 1 B10

Description : A interface timer triggered by the BSC in the BSSMAPmanagement procedure.

It is started on transmission of BLOCK or UNBLOCK by theBSC and canceled on receipt of BLOCK ACKNOWLEDGEor UNBLOCK ACKNOWLEDGE sent by the MSC.

Value range : [2 to 300] secondsObject : bsc

Default value : 5

Type : DP



Description : A interface timer triggered by the BSC in the BSSMAPmanagement procedure. This timer is used with a Phase IMSC only.

It is started on transmission of RESET CIRCUIT by the BSCand canceled on receipt of RESET CIRCUITACKNOWLEDGE sent by the MSC.


Default value : 5

Type : DP



Description : A interface timer triggered by the BSC in the BSSMAPmanagement procedure.

It is started on receipt of RESET sent by the MSC. On elapse,the BSC sends RESET ACKNOWLEDGE to the MSC.


Default value : 32

Type : DP




bssMapT19 Class 1 B13 V8

Description : A interface timer triggered by the BSC in the BSSMAPmanagement procedure. This timer is used with a Phase IIMSC only.

It is started on transmission of RESET CIRCUIT by the BSCand canceled on receipt of RESET CIRCUITACKNOWLEDGE sent by the MSC.


Default value : 32

Type : DP


bssMapT20 Class 1 B14 V8

Description : A interface timer triggered by the BSC in the BSSMAPmanagement procedure

It is started on transmission of CIRCUIT GROUP BLOCK orCIRCUIT GROUP UNBLOCK by the BSC and canceled onreceipt of CIRCUIT GROUP BLOCK ACKNOWLEDGE orCIRCUIT GROUP UNBLOCK ACKNOWLEDGE sent bythe MSC.


Default value : 32

Type : DP




It is started on transmission of RESET and canceled on receiptof RESET ACKNOWLEDGE sent by the MSC. On elapse,the BSC sends RESET.


Default value : 60

Type : DP



PE/DCL/DD/0124411–9001–124




It is started on transmission of HANDOVER REQUIRED andcanceled on receipt of HANDOVER COMMAND, RESET,RESET CIRCUIT, CLEAR COMMAND or HANDOVERREQUIRED REJECT.


Object : bsc

Default value : 7

Type : DP



Description : A interface timer triggered by the BSC in the BSSMAPmanagement procedure. It is greater than t3103 for each cellmanaged by the BSC

It is started on transmission of HANDOVER COMMAND andcanceled on receipt of CLEAR COMMAND sent by the MSCor HANDOVER FAILURE sent by MS.


Object : bsc

Default value : 15

Type : DP

Checks : [C/M]: bssMapT8 > t3103 for all bts objects dependenton the bsc object.




bssMapTchoke Class 1 B18

Description : A interface timer triggered by the BSC in the handovermanagement procedure

It is started by the BSC when the last neighbor cell in the listis rejected. On timer elapse, the BSC asks the MSC to providea new list of eligible cells.


Default value : 4

Type : DP


bssSccpConnEst Class 1 B19

Description : A interface timer triggered by the BSC in the handovermanagement procedure

It is set on transmission of CONNECTION REQUEST andcanceled on receipt of CONNECTION CONFIRM orCONNECTION REFUSED.

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

Default value : 5

Type : DP

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

Note : The default value is 5 seconds

bssSccpInactRx Class 1

Description : A interface timer T(iar) triggered by the BSC in the SCCPinactivity detection procedure.

It is set either on transmission or receipt of CONNECTIONCONFIRM or on receipt of any other message during theconnection and canceled on receipt of any message.

Value range : [2 to 30] minutesObject : signallingPoint

Default value : 11

Type : DP



PE/DCL/DD/0124411–9001–124


bssSccpInactTx Class 1

Description : A interface timer T(ias) triggered by the BSC in the SCCPinactivity detection procedure.

It is set either on transmission or receipt of CONNECTIONCONFIRM or on transmission of any other message during theconnection and canceled on transmission of any message.

Value range : [1 to 15] minutes


Default value : 5

Type : DP


bssSccpRelease Class 1

Description : A interface timer T(rel) triggered by the BSC in the SCCPmanagement procedure.

It is set on transmission of RELEASE and canceled on receiptof RELEASED COMPLETE or RELEASED.



Default value : 10

Type : DP


bssSccpSubSysTest Class 1

Description : A interface timer T(state info) triggered by the BSC in theSCCP management procedure.

It is set on transmission of SST and canceled on receipt ofSSA.

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


Default value : 30

Type : DP




bsTxPwrMax Class 3 B20

Description : Maximum theoretical level of BTS transmission power in acell

The BSC relays the information to the mobiles in the AbisCELL MODIFY REQUEST message.

Value range : [2 to 51] dBmObject : powerControl

Default value : 43

Type : DP


[M]: The use of the block edge channels induces a cellpower limitation to 32 dBm for GSM 1900networks (See Remark hereafter).

Note : Some bsTxPowerMax values are not compatible with theeffective power output by the BTS. See NTP < 07 >.

Remark : For a GSM 1900 network (standardIndicator of bts objectset to ‘pcs1900’), the MD–R checks the following:

bsTxPwrMax < 32 (dBm)

when an edge frequency is defined for the cell (i.e. if the valueis included 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–Rconfiguration file, MD/base/config/boundEdge.cfg. Thisfile is off–line configurable. To update the database accordingto the list of edge frequencies, use the shell/MD/install/shell/cm_configBde.sh.


PE/DCL/DD/0124411–9001–124


bts

Description : Identifier of a bts object defined with regard to abtsSiteManager object

All channel, transceiver, and transceiverEquipment objects ina BSS are identified with regard to a bts object that defines thecovering cell.

In all MMI commands, a bts object can be referred to by thesequence “siteName.cellName” where siteName andcellName identify the covering site and the cell respectivelyby name.


Object : bts

Type : Id

Checks : [C]: The number of cells managed by an OMC–R islimited to maxBtsPerNetwork (staticconfiguration data).

[C]: The maximum number of cells controlled by aBSC is as follows:

BSC 12000/6000

T1 T2 T3 T4 T5

120 120 160 160 160

[C]: The number of cells attached to a radio site islimited to maxNbOfCells (attribute of the parentbtsSiteManager object).

[C]: The software object related to the parentbtsSiteManager object is created.

[C]: The mobileCountryCode andmobileNetworkCode attributes match those ofthe parent bsc object if they are defined for thatobject (cell CGIs must comply).



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

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

[D]: If the application database of the related BSC isbuilt, the parent bsc object is unlocked, the parentbtsSiteManager object is locked, and the bts objectis locked.


[D]: No adjacentCellHandOver object refers to the btsobject (the described cell is not used as a neighborcell of another serving cell).

[D]: No mdScanner object describing a temporaryobservation refers to the bts object (no observationis running on the described cell).

[D]: No traceControl or callPathTrace object refers tothe bts object (no tracing is running on thedescribed cell).

Note : All cells covered by a given radio site must be created innumerical ascending order and deleted in the reverse order.

bts

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


Object : adjacentCellHandOver, adjacentCellReselection,channel, frequencyHoppingSystem, handOverControl,powerControl, software, transceiver,transceiverEquipment, transceiverZone

Type : Id

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


PE/DCL/DD/0124411–9001–124


bts equipment name

Description : To select messages issued by a given type of BTS equipment


Value range : [main power / converter B / converter C / converter A / CSW1 /CSW2 / CSW1M / TX / SYN / SYNO / ALAT / ALATO / DCC/ DTI /RX splitter / TX splitter / antenna / column system RX /converter D / column system TX / fan system / RX fan / TX fan/ cabinet fan / fans rack / MWT system / exchanger system /rectifier system / rectifier groups / fuses system / breakers / batterysystem / temperature system / door contact / smoke detector /CSWM / SYNC / ALCO / DSC / PCMI / GTW / PCM0 / PCM1/ rectifier 48V / converter F / converter BCF / internal batterysystem / cooler system / LNA / VSWR / user system / distributionsystem / battery cabinet / main breaker / diu / external alarm / VGA/ DLNA / MNU / DCU / RX / DBF / AMNU / DCU4 / DRX /FPRX / Lightning protection / BCF Cabinet door / BCF Cabinetfan / SBCF / PA / AC power supply / DC power supply / transmitantenna / cabinet high temperature alarm / cabinet low temperaturealarm / drx main reception chain / drx diversity reception chain /splitter output / high power module / splitter / low power RFmodule / rf supply module / CMCF / PCM / CPCMI / RECAL/ rx splitter M / rx splitter D / combiner h4 lna / combiner h4 vswr/ txFilter / combiner d lna / combiner d vswr / rxMainConnector/ rxDivConnector / dacsCooler / compact dacs cooler / compactdistribution / PMNU / RDRX / PMOD / ABIS BTSSynchronization / PSU / Heatsink / Preventive lightning protection/ Battery / External Environment / SALCO / not protected alarm/ internal temperature / external temperature / Remote TunableCavity Combiner / Cavity]


Type : DP



bts list

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

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, thatis there is one channel object in the set oftransceiver objects dependent on the bts objectwhose channelType is “bcchSdcch4CBCH” or“sdcch8CBCH”.

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

bts time between HO configuration Class 3 B21 V9

Description : Whether the HOPingpongTimeRejection timer can be used atbts level when processing handovers

Refer to bts object btstimeBetweenHOConfiguration andadjacentCellHandOver object HOPingpongTimeRejectionattributes in this Dictionary of Parameters.

Value range : [0 to 60] second for V9 to V11[0 / 1] for V12

In a V12 BSS, the range value meaning is the following:

“0”: The timer is disabled.

“1”: The timer is used.

Object : bts

Feature : General protection against pingpong handovers(TF821 – V12)

Default value : 0

Type : DP



PE/DCL/DD/0124411–9001–124


btsDescription V10

Description : BTS configuration description (BTS type, configuration,coupling system...) corresponding to the transcription ofconfigRef attribute

Value range : [chain of characters]


Type : DI

Note : It designates the maximum configuration of the configRef fileloaded on one of the BTSs. But it does not necessarilycorresponds to the configuration of the btsSiteManager objectconcerned.

btsHopReconfRestart Class 2 B22 V8

Description : Whether hopping frequency reconfiguration is authorized onTX restart in a cell


Object : bts

Default value : true

Type : DP

Checks : [C/M]: If the attribute value is “true”, thebscHopReconfUse attribute of the parent bscobject is also “true”.

[C/M]: The parent bsc object is unlocked and the btsobject is locked.

btsIsHopping Class 2 B23

Description : Whether frequency hopping is allowed in a cell

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

Object : bts

Default value : Hopping

Type : DP



Checks : [M]: If frequency hopping is allowed, the GSM“fhMgt” function is defined in thesiteGsmFctList attribute of the parentbtsSiteManager object.

[M]: If it is disabled, no channel object dependent onthe bts object is authorized to obey frequencyhopping laws.


Note : The “xxxWithCarrierFilling” configuration means that theBTS covering the cell must use a TX for BCCH fillingpurposes. The following apply:

The BSC sends the information to the BTS in the AbisCELL CONFIGURATION REQUEST message.

If the BTS does not have a redundant TRX/DRX, one of theoperating TRX/DRXs is assigned to that purpose and thepartnered TDMA frame is unreachable (refer to theoperationalState entry for the transceiver object in theDictionary).

When this TRX/DRX is malfunctioning, the BTSreconfigures the other TRX/DRXs. Users are then warnedby the system, by means of a notification.

The “noHoppingWithCarrierFilling” configuration can beused in all BTSs, regardless of the coupling mode. Thefollowing apply:

Hybrid coupling: All cell TX configurations provideBCCH filling.

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

The “hoppingWithCarrierFilling” configuration can only beused in BTSs that use cavity coupling. The following apply:

Hybrid coupling: The BTS refuses the configuration.

Cavity coupling: All cell TX configurations provideself-frequency filling.


PE/DCL/DD/0124411–9001–124


btsLockedReserved2 Class 3 B24 V12


Value range : [–32768 to 32767]Object : bts

Default value : 0

Type : DP


btsMSAccessClassBarringFunction Class 3 B25 V9

Description : Enable or disable dynamic barring of access class at the btslevel

Value range : [enabled / disabled]Object : bts


Type : DP


btsReserved3 Class 3 V12

Description : Mean number of logical channels belonging to the largefrequency reuse pattern and used at the same time for datacommunications

Value range : [–16 to +16]Object : bts

Default value : 0

Feature : Automatic Cell Tiering (TF995–V12)

Type : DP


btsReserved4 Class 3 B26 V12


Value range : [–32768 to 32767]Object : bts

Type : DP




btsSensitivity Class 3 V12

Description : Target power needed for BTS decoding. This parameter has aninfluence on the power control efficiency.


Default value : 0


Type : DP


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

btsSensitivityInnerZone Class 3 (gprsBtsExtendedConf) V12

Description : Minimum power needed for BTS decoding in the inner zoneof a dual–band cell



Default value : 0

Type : DP


btsSiteManager

Description : Identifier of a btsSiteManager object defined with regard to absc object

All bts, channel, transceiver, and transceiverEquipmentobjects in a BSS are identified with regard to a btsSiteManagerobject that defines the covering radio site.

In all MMI commands, a btsSiteManager object can bereferred to by name (siteName).

Value range : [0 to 146]Object : btsSiteManager

Type : Id

Checks : [C]: The maximum number of radio sites controlled bya BSC depends on its type and architecture(numbers in ordinary brackets apply to a BSC thatdoes not concentrate BTS LAPD signaling).


PE/DCL/DD/0124411–9001–124


BSC 12000/6000

T1 T2 T3 T4 T5

28(7)

60(15)

92(23)

124(31)

147(39)

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

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

[C]: If the application database of the related BSC isbuilt, the referenced pcmCircuit objects(bscSitePcmList) are created for the parent bscobject and assigned to the Abis interface(pcmType = “pcmAbis”).

[C/M]: The bscSitePcmList list contains at least twopairs if the btsSiteManager objectredundantPcmPresence attribute is “true”.

[C]: If one of the pcmCircuit objects in the listdescribes a PCM link that is shared with anothersite in the BSS, the radioSiteMask of the twobtsSiteManager objects are dissociated.

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

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




btsSiteManager

Description : Identifier or name of a btsSiteManager object. It defines theparent btsSiteManager object.

It defines the parent btsSiteManager object.

By definition, a radio site (btsSiteManager object) is related toa BSC, a radio cell (bts object) is related to a radio site, aTRX/DRX (transceiverEquipment 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 abtsSiteManager object can be identified at BSC or site level,whichever is the most convenient to users.


Object : adjacentCellHandOver, adjacentCellReselection, bts,channel, frequencyHoppingSystem, handOverControl,powerControl, software, transceiver,transceiverEquipment, transceiverZone

Type : Id

Checks : [C]: The btsSiteManager object is created.

btsSiteManager model

Description : To select messages issued by a given model of BTS


Value range : [s2000 inDoor / s2000E inDoor / s2000E outDoor / s4000inDoor / s4000C inDoor / s4000 outDoor / s4000 smart /s8000 inDoor / s8000 outDoor / s2000 Low Power O1 / s2000Low Power O2 / s2000 Low Power S11 / s2000 High PowerO1 / s2000 High Power O2 / s2000 High Power S11 / s8000inDoor CBCF / s8000 outDoor CBCF / s2000 Low PowerEnhanced Packaging O1 / s2000 Low Power EnhancedPackaging O2 / s2000 Low Power Enhanced Packaging 2O4/ s2000 High Power Enhanced Packaging O1 / s2000 HighPower Enhanced Packaging O2 / s2000 High PowerEnhanced Packaging 2O4 / s2000 High Power EnhancedPackaging S11 / e–CELL / s8002 outdoor CBCF O2]


Type : DP


PE/DCL/DD/0124411–9001–124


btsSiteManagerList Class 2

Description : List of btsSiteManager objects attached to a multiple siteobject


Object : multiple site

Type : DP

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

[M]: The parent bsc object is unlocked and thereferenced btsSiteManager objects are locked.

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

btsSMReserved1 Class 2 B27 V12

Description : This space is used for RadioSiteMask offset parameter

Value range : [–32768 to 32767]


Default value :

Type : DP

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

btsSMReserved2 Class 2 B28 V12

Description : This space is used for RadioSiteMask offset parameter

Value range : [–32768 to 32767]


Default value :

Type : DP




btsThresholdHopReconf Class 2 B29 V8

Description : Minimum number of frequencies that must be working in acell to allow frequency hopping reconfiguration

If this attribute defines the nominal number of cellfrequencies, the reconfiguration process is deactivated. Referto the btsHopReconfRestart entry in the Dictionary.


Object : bts

Default value : 1

Type : DP

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


btsWithCavity Class 2 V12

Description : Whether the bts object instance uses a transceiver equipmentwith cavity

Value range : [true / false]Object : bts

Default value : false

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

Type : DP

Checks : [M]: The parent bsc object is unlocked and the btsobject is locked.


PE/DCL/DD/0124411–9001–124


buildState

Description : Whether BSC application database building is in-progress.Commands on all objects related to the bsc concerned objectare refused while the BDA is being built.

When the bsc object is created, the value of this attribute isenforced to “notInProgress”. It is unknown to the BSC andcannot be directly modified by users.

It is changed to “inProgress” by the system after a user BuildBDA command on the bsc object as long as database buildingis in-progress. It is then changed back to “notInProgress” whenthe operation is complete.

Value range : [inProgress / notInProgress]

Object : bsc

Type : DI



C

callClearing Class 3 C1

Description : Maximum distance between MS and BTS before 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 thehandOverControl object associated with the btsobject).

[C/M]: The maximum distance is 35 km if the extendedcell attribute of the bts object is “false”.

[C/M]: The maximum distance is 120 km if the extendedcell attribute of the bts object is “true”.


7 km for urban

35 km for rural

callPathObservationArea

Description : List of up to thirty-one same-type objects observed. Enter eachobject 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.


PE/DCL/DD/0124411–9001–124


callPathTrace V8

Description : Identifier of a callPathTrace object defined with regard to themd object

This object describes the Call path tracing function of a BSS(follow–up of calls using one or more common resources inthe BSS).

A callPathTrace object is created in locked state. Unlock theobject to start collecting trace data.

Value range : [0 to 2147483646]Object : callPathTrace

Type : Id

Checks : [C]: The callPathTrace object is not created for the mdobject.

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

[C/M/D]: If the application database of the related BSC isbuilt, the BSS/OMC–R link is established and noaudit is running in the BSC.

[D]: The callPathTrace object is created.

callPathTraceType

Description : Type of information stored by the BSC

The information stored with respect to the type is detailed inNTP < 07 >.

If the request cannot be fulfilled, the BSC attempts to storeanother type of information, using the following rule: radio>>> hand over >>> radio.

Value range : [basic / hand over / radio]Object : callPathTrace

Type : DP

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



callReestablishment Class 3 C2

Description : Whether call re–establishment in a cell is allowed when theradio link is broken off for propagation reasons

The information is broadcast to the mobiles at regular intervalson the cell BCCH.

On receipt of a CHANNEL REQUIRED message with cause“call re–establishment”, the BSC attempts to allocate a TCHin one of the cells where call re–establishment is allowed.Then, if no TCH is available the BSC attempts to allocate aSDCCH.

Value range : [allowed / not allowed]Object : bts

Default value : not allowed

Type : DP


callReestablishmentPriority Class 3 C3

Description : Index in the allocPriorityTable that defines the processingpriority of TCH allocation requests with cause “callreestablishment”



Default value : 17

Type : DP


capacityAlarmThreshold

Description : Filling threshold of the message saving partition on theOMC–R agent disks, beyond which a notification is triggered

The size of the saving partitions is indicated in the systemcommissioning files.

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

When the threshold is reached, the OMC–R agent initiates thefollowing actions:

A notification is sent to the OMC–R manager.


PE/DCL/DD/0124411–9001–124


For a current alarm log, old messages are deleted to makeroom in the partition. If all saved messages are of today’sdate, further notifications are not saved and theoperationalState of the log object is forced to “disabled”.

For a current observation or trace log, the operationalStateof the log object is forced to “disabled” and itsavailabilityStatus is forced to “logFull”.

Value range : [0 to 2147483646]. “2147483646” defines a 100% threshold(the partition is full).


Type : DP


��

Description : To select messages according to one or more causes associatedwith a fault number. Refer to BSS and OMC MaintenanceManuals.

This parameter is a component of the specific problems filter.Refer to this entry in the Dictionary.



Type : DP

ccId V13

Description : Identifier of the ‘cc’ object class. This identifier is allocated bythe MD–R at object creation, depending on the shelf and slotnumbers indicated by the BSC. This attribute cannot bemodified. This attribute is relevant for BSC e3.

Value range : [0 to 2147483646]

Object : cc

Type : DP



cellAllocation Class 2 C4

Description : List of no more than 64 frequencies allotted to a cell in thenetwork frequency band

By definition, all cells covered by a given radio site use thesame frequency band defined by the type of the network(standardIndicator). All cells declared as neighbor cells ofa serving cell use the same frequency band as the serving cell.


Object : bts

Type : DP

Checks : [C/M]: Each frequency occurs once in the list andcomplies with the type of the network (refer to thestandardIndicator entry in the Dictionary).

[C/M] : GSM 900 / GSM–R / Extended GSM networks:The number of frequencies in the list is limited to64.

[C/M] : GSM 1800 or 1900 network: The number offrequencies in the list depends on the gap betweenthe lowest and the greatest defined frequencies.

Maximum gap betweenfrequencies

Number of frequencies

between 257 and 512 [2 to 18]




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

[C/M]: For dualband networks, the number of frequenciesmust 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 framesrelated to the cell are part of the list.



PE/DCL/DD/0124411–9001–124


cellBarQualify Class 3 C5 V8

Description : Cell selection priority used in the C2 algorithm in Phase II


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

Default value : False

Type : DP


cellBarred Class 3 C6

Description : Whether direct cell access are barred to mobiles


During a call, it is transmitted on a signaling link.

If the attribute value is changed to “barred”, all in-progresscalls can continue but the BSC will direct further mobile callsto 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 beindirectly accessible if incoming handovers are allowed(incomingHandOver attribute of the associatedhandOverControl object).



cellDeletionCount Class 3 C7

Description : Number of consecutive “Measurement Result” messageswhich, if not received from a given neighbor cell, will causeall previously stored information related to that cell to bedeleted.

From V12, this number corresponds to the number of missingmeasurement reports after which this neighbour cell is nomore eligible. The measurements related to this neighbour cellare not deleted as far as less than 10 consecutive measurementsare missing.


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

Type : DP


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

cellDtxDownLink Class 3 C8

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


Object : bts

Default value : enabled

Type : DP


Remark : The dtxMode attribute allows users to control the use ofdiscontinuous transmission on the uplink. Refer to this entryin the Dictionary.


PE/DCL/DD/0124411–9001–124


cellIdentity Class 3

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



Type : DP

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



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



Type : DP




Description : Cell Identity code (CI) that identifies a serving cell in alocation area

A CGI (Cell Global Identifier) is unique in a location area. Itidentifies a cell in the PLMN and includes four fields:cellIdentity (CI), locationAreaCode (LAC),mobileCountryCode (MCC), and mobileNetworkCode(MNC).


Object : bts

Type : DP





cellName

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


Object : bts

Type : DP

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

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 describing theTDMA frame no.0 carrying theBCCH is “working” and SYS INFO1, 2, 3, 4 have been acknowledged bythe BTS.

not allowed The operationalState of the. . . . . . . transceiver object describing theTDMA frame no.0 carrying theBCCH is “working” and SYS INFO1, 2, 3, 4 have not been acknowledgedby the BTS.If no message has beenacknowledged by the BTS, thenotification 1256 “Non response toSYS INFO 1, 2, 3, 4 or 2bis” is issued.

not significant The operationalState of the. . . . transceiver object describing theTDMA frame no.0 carrying theBCCH is not “working”.

Object : bts

Type : DD


PE/DCL/DD/0124411–9001–124


cellReselectHysteresis Class 3C9

Description : Hysteresis to reselect towards a cell:

when the MS is in GSM – IDLE mode and reselects a cellwith a different LA (Location Area)

when the MS is in GMM stand by state and reselects a cellwith a different LA (Location Area) or a different RA(Routing Area)

when the MS is in GMM ready state and reselects a differentcell

A mobile can select a cell in another location area provided thereselection parameter value of that cell oversteps thereselection parameter values of all the cells in the samelocation area as the current camping cell by at leastcellReselectHysteresis dB.

The information is broadcast on the cell BCCH.

The reselection 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 theMS

The reselection criterion (C2) formula is given with thecellReselectOffset entry.

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

Object : bts

Default value : 6 dB

Type : DP


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



cellReselectOffset Class 3C10 V8

Description : Encouragement to reselect a cell (C2 criterion) for phase 2 MS

The reselection criterion (C2) formula is:

C2 = C1 + cellReselectOffset – temporaryOffsetx H (penaltyTime – T)

C1 is defined with the cellReselectHysteresis entry.

T is a timer that is started when the cell is placed by the MSon the list of most suitable cells to receive the calls, and isstopped when the cell is no longer on the list.

H(penaltyTime – T) equals 0 when penaltyTime < T andequals 1 when penaltyTime ≥ T.

In the case when penaltyTime = 640, reselection criterionformula becomes:

C2 = C1 – cellReselectOffset


Object : bts

Feature : AR 264

Default value : 4

Type : DP


Note : The value given to this attribute allows to more or lessencourage the mobiles to reselect the cell.

Type : DP

cellReselInd Class 3 C11 V8

Description : Whether cell reselection criterion (C2) use is authorized


Object : bts


Type : DP



PE/DCL/DD/0124411–9001–124


cellType Class 3 C12

Description : Type of the adjacent cell

Value range : [normalType / umbrellaType / microType]Object : adjacentCellHandOver

Default value : normalType

Type : DP


cellType Class 3 C13

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 isdefined if the cell is a microcell (cellType) anddirected retry handovers are processed in BSCmode (directedRetryModeUsed).


cemId V13

Description : Identifier of the ‘cem’ object class. This identifier is allocatedby the MD–R at object creation, depending on the shelf andslot numbers indicated by the BSC. This attribute cannot bemodified. This attribute is relevant for BSC e3 and TCU e3.

Value range : [0 to 2147483646]Object : cem

Type : DP

chain

Description : Identifier of a BSC processing chain

It identifies the chain whose software markers are displayed.

Value range : [A / B]Object : software–bsc – Display markers

Type : DD



chain

Description : To select messages originating from a BSC processing chain


Value range : [chainA / chainB]


Type : DP

chainId


It identifies the chain whose characteristics are displayed.

Value range : [chainA / chainB]

Object : bsc – Display chain information

Type : Id


chainId


The consequences of the command are as follows:

If the chain is active at the time the BSC receives the order,it is reset and the operations are switched over to the passivechain.

If the chain is passive when the BSC receives the order, it isreset if it can be reached.

To determine which chain is currently active in a BSC, run aDisplay all command on the concerned bsc object: theactiveChain attribute identifies the active chain.

Value range : [chainA / chainB]Object : bsc – Suicide chain

Type : Id


PE/DCL/DD/0124411–9001–124


channel

Description : Identifier of a channel object (radio time slot)

In all MMI commands, a channel object can be referred to bythe sequence “siteName.cellName.transceiver.channel”,where siteName and cellName respectively identify thecovering site and cell by name.


Object : channel

Type : Id

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

[C/M]: If the channel object does not obey frequencyhopping laws, the absoluteRFChannelNo isdefined unless it carries the parent cell BCCH, andfhsRef and maio are undefined.

[C/M]: If the channel object obeys frequency hoppinglaws, the absoluteRFChannelNo is undefined,and fhsRef and maio are defined.

[C/D]: If the application database of the related BSC isbuilt, the parent bsc object is unlocked and theparent bts object is locked.




channel state

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

Value range :

Type: [BCCH / RACH / PCH AGCH /SDCCH/4 / SDCCH/8 / TCH (fullrate) / CCH],

Resource state: [not created / disabled / working / free/ busy / blocking / working, blocked/ blocking, removing / disabled,blocked / free, blocked / removing /available / working not CBCH /disabled not CBCH / working CBCH/ disabled CBCH]

available The channel is allocated, not blocked,. . . . . . . . and free.

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

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

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

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

Object : channel – Display channel state

Type : DD

Notes : The types of logical channels that can be multiplexed on aradio time slot depend on its channelType. Refer to thisentry in the Dictionary.

The resource state of SDCCH no.2 is “disabled” if a CBCHis defined.

A radio channel is blocked or released by means of a userModify channel state command.

A radio channel is allocated when the TDMA frame isconfigured (in the Abis way) and its radio time slots aremapped onto an Abis interface PCM link.


PE/DCL/DD/0124411–9001–124


channelType Class 2 C14

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 TCHsupports the call, serving traffic and signaling needs.

A CBCH (Cell Broadcast CHannel) configuration enables useof the Short Message Service –Cell Broadcast (SMS–CB) ina cell when a radio time slot of a TDMA frame related to thecell supports that type of channel. The CBCH can be combinedwith an SDCCH/8 or a BCCH+SDCCH/4. It takes the place ofSDCCH no.2 in all cases.

If the time slot carries a cell BCCH, its type sets the cell BCCHconfiguration (combined or not combined).

Object : channel

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

Default value : None

Type : DP

Checks : [C/M]: If the type is “mainBCCH”,“mainBCCHCombined”, or“bcchSdcch4CBCH”, the channel objectidentifier is [0] and the object is not authorized tohop.

[C/M]: The type “cCH” can only be used if TS 0 carriesa BCCH logical channel (“main BCCH”, “mainBCCH 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 objectidentifier is in the range [0 to 3] if the covering cellworks in normal mode, and it equals 0 or 2 if thecell works in extended mode (extended cellattribute of the parent bts object).

[C/M]: If the type is “sdcch8CBCH”, thenoOfBlksForAccessGrant attribute of the parentbts object has a value greater than 0.



[C/M]: If the type is “bcchSdcch4CBCH” or“sdcch8CBCH”, use of the SMS–CB service isauthorized in the parent bts object (smsCB =“used”).

[C/M]: Concentric cell: If the parent transceiver objectbelongs to the cell inner zone, the only authorizedtypes are “bcchSdcch4CBCH” and“sdcch8CBCH”.

[M]: The “pDTCH” channelType is only allowed fromV12 BSCs for GPRS.

[M]: The parent bsc object is unlocked and the parentbts object is locked.

A radio channel is identified by an 8-bit code built up by theOMC–R from the channel type and the number of the time slotthat 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

10000 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/4configuration:

00100 SDCCH/4 + ACCH subchannel no.0

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



• There are eight subchannels [0 to 7] in an SDCCH/8configuration:



PE/DCL/DD/0124411–9001–124


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







The logical channels that can be multiplexed on a radio timeslot depend on its channelType. They are described in thefollowing table.

channelType Bits C5–C1

tCHFull BM + ACCH (SACCH/FACCH)

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

mainBCCH BCCHRACH (Uplink)PCH + AGCH (Downlink)

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

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

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

cCH BCCHRACH (Uplink)PCH + AGCH (Downlink)

Remark : Configuration of logical channels and broadcast of shortmessages are managed by two independent OMC–R functions.

When a short message broadcast is started in a cell, thepresence of a channel object with a CBCH dependent on theconcerned bts object is checked. On the contrary, the SMS–CBfunction is not aware of changes made to that attribute.



Consequently, withdrawing a CBCH from a cell configurationwill implicitly stop any short message broadcast in the cellwithout the SMS–CB function knowing.

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

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

chanState

Description : Whether the radio channel should be 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 areunlocked.

Notes : When a CBCH is defined for a cell, it always uses SDCCHno.2.

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

chosenChannelAsscomp Class 1 V8

Description : Whether the “Chosen channel” element is used in the ASSIGNCOMPLETE messages (Phase II compliance)

Value range : [true / false]Object : signallingPoint


Type : DP



PE/DCL/DD/0124411–9001–124


chosenChannelCompL3Info Class 1 V8

Description : Whether the “Chosen channel” element is used in theCOMPLETE LAYER 3 INFORMATION messages (Phase IIcompliance)




Type : DP


chosenChannelHoPerf Class 1 V8

Description : Whether the “Chosen channel” element is used in theHANDOVER PERFORMED messages (Phase IIcompliance)




Type : DP


chosenChannelHoReq Class 1 V8

Description : Whether the “Chosen channel” element is used in theHANDOVER REQUEST ACKNOWLEDGE messages(Phase II compliance)




Type : DP




cic

Description : Circuit Identity Code = numbers of the PCM link and time slotused by a terrestrial circuit on the A interface, defined withregard 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 linkwith regard to the MSC (mscPcmNumber), bits n identify thetime slot used on that PCM link with regard to the MSC(mscPcmTsNumber).

Value range : [0 to 65535]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 theA interface is identical on MSC end(mscPcmTsNumber component) and BSC end(timeSlotNumber), and is not allotted to anotherxtp or signallingLink object dependent on theparent 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 therange [1 to 20] if the PCM link is a T1 link. Sincethe last four TSs on that link are not mapped on theAter interface, they cannot be used. Refer to thetranscoderMatrix entry in the Dictionary.



PE/DCL/DD/0124411–9001–124


circuitGroupBlock Class 1 V8

Description : Whether the CIRCUIT GROUP BLOCK and CIRCUITGROUP UNBLOCK messages are used (Phase IIcompliance)

If these messages are unused, the BLOCK and UNBLOCKmessages are used.

Value range : [false / true]


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


Type : DP


[C/M]: The only accepted value in V10 and V11 is “false”.

Remark : Since the system accepts only one value in V10 and V11,changing it has no meaning.

circularFileId

Description : Identifier of a BSC circular file

BSC circular files are automatically created by the system: theFAULT files are created with the BSC, the PERF(observations) and TRACE (trace data) files are created whenthe BSC application database is built.

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

Object : bscMdInterface – Circular file

Type : Id

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



circularFileState

Description : State of a circular file. When a circular file is closed, thespontaneous messages stored are not forwarded to theOMC–R agent.

This attribute is set by the system following a user Closecircular file or Open circular file command.

When a circular file is closed, the messages are stored until thefile is reopened. Some messages may be lost if the capacity ofthe 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



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

Type : DP

cleared by

Description : To select alarms ceased by a given user. Enter the user’s nameas defined in the user’s profile.

Do not fill in if this criterion is not to be selected.Object : Cleared alarm log – Filter

Type : DP

clearing cause

Description : To select alarms according to the cause of ceasing


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

Object : Cleared alarm log – Filter

Type : DP


PE/DCL/DD/0124411–9001–124


cnId V13

Description : Identifier of a ‘cn’ object class. This identifier is allocated bythe MD–R at object creation. The only value allocated by theMD–R is 0. This attribute cannot be modified. This attributeis relevant for BSC e3.


Object : cn

Type : DP

coderPoolList V13

Description : Current partitioning of the coder pool. This attribute isdynamically managed by the BSS. It is set to NULL at objectcreation. Value changes are not notified to the Manager. Thisattribute is relevant for TCU e3.


Object : transcoder3GEqpt

Type : DP

codingScheme Class 2 V12

Description : Channel coding scheme that the MS (Mobile Station) shall usewhen transmitting data on UL.

Value range : [cs1, cs2]


Default value : cs1


Type : DP


Note : cs1 (respectively cs2) is recommended for data blocks(respectively signaling blocks).



command classes

Description : List of no more than twenty-five authorized command classesthat define a user’s command domain. MMI commands grantaccess to OMC–R functions.

Each class defines a subset of commands (one of themprovides access to all MMI commands). The comprehensivelist of MMI commands, together with their class(es), can bedisplayed using the Display command classes command.

Value range : [0 to 2147483646]

Object : user profile

Type : DP

command line

Description : Command associated with the job. Follow the Line modesyntax.

If the job is meant to run a simple command, enter the sequencedescribing 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 NTP < 130 >.

Value range : [case sensitive]

Object : job

Type : DP

command number

Description : Serial number of the command to abort. It is assigned by thesystem and is registered in session logs.

Every MMI command launched by the user is identified by aserial number assigned by the system. Open the user sessionlog consultation window and search for that number.

Object : commandFile – Abort

Type : DP


PE/DCL/DD/0124411–9001–124


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 eitheroverwrite its contents with the commands newly recorded orappend the new commands to the existing file (see toNTP < 130 >).

Value range : [case sensitive, 14 characters max]Object : commandFile – Create file

Type : Id

commandFile

Description : Saving name of the command file after being edited

Enter the file name only.

If the file is a new one, preselect the saving directory in the“Command file manager” window. If the file exists, it is savedin the same directory as the source file.

Value range : [case sensitive, 14 characters max]Object : Command file editing – Save

Type : Id

comment V11

Description : Text comment

Value range : [256 characters max]Object : report template

Type : DP

comment

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

Value range : [60 characters max]Object : short message

Type : DP

comments

Description : Additional information (such as creation date)

Object : software – Display markers

Type : DD



ComputeSyntheticCounters

Description : Whether synthetic counters are included in the observationreport

This parameter is significant only for permanent bsc andinstrument panel observation report display requests.

Value range : [enabled / disabled]Object : Display xxx report

Type : DP

concentAlgoExtMsRange Class 3 C15 V9

Description : MS to BTS distance below which a handover is requested fromthe large zone to the small zone if the level criteria is verified



Default value : 1

Condition : To define if the associated bts object describes a concentric,dualband or dualcoupling cell

Type : DP

Checks : [C/M]: concentAlgoExtMsRange ≤concentAlgoIntMsRange

[C/M]: The maximum distance is 34 km if the extendedcell attribute of the associated bts object is “false”.




PE/DCL/DD/0124411–9001–124


concentAlgoExtRxLev Class 3 C16 V9

Description : The level of the MS signal strength from below which ahandover is requested from the large zone to the small zone

Value range : [less than –110, –110 to –109, ... , –49 to –48, morethan –48] dBm


Default value : – 95 to – 94


Type : DP

Checks : [C/M]: concentAlgoExtRxLev ≤concentAlgoIntRxLev


concentAlgoIntMsRange Class 3 C17 V9

Description : MS to BTS distance from which a handover from the smallzone 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



Default value : 34


Type : DP

Checks : [C/M]: concentAlgoIntMsRange ≥concentAlgoExtMsRange

[C/M]: The maximum distance is 34 km if the extendedcell attribute of the associated bts object is “false”.





concentAlgoIntRxLev Class 3 C18 V9

Description : Level of the MS signal strength below which a handover isrequested from the small zone to the large zone



Default value : less than –110


Type : DP

Checks : [C/M]: concentAlgoIntRxLev ≥concentAlgoExtRxLev



PE/DCL/DD/0124411–9001–124


concentric cell Class 2 C19 V9

Description : Whether the cell is monozone, concentric, dualband ordualcoupling

A concentric, dualband, or dualcoupling cell describes acombination of two transmission zones, the outer (or large)zone and the inner (or small) zone. The inner zone is entirelyincluded in the outer zone.

A dualband cell is a particular type of concentric cell for whichGSM 900 and GSM1800 TRXs/DRXs coexist and share thesame BCCH.

A dualcoupling cell is a particular type of concentric cell forwhich the TRXs/DRXs are combined with two types ofcombiners.

For concentric configurations (concentric, dualband ordualcoupling), a TDMA frame belongs to one zone or theother, but never to both, and the frequencies used in each zoneare separated.

Value range : [monozone / concentric / dualband / dualcoupling]

monozone.......normal cell

concentric.......two concentric transmission zones

dualband.........two concentric transmissions zones withGSM 900 TRXs/DRXs for the one andGSM 1800 TRXs/DRXs for the other

dualcoupling..two concentric transmission zones withTRXs/DRXs combined with a one type ofcombiner for the one and with another typeof combiner for the other

Object : bts


Default value : monozone

Type : DP


Note : Dualband cells are only available for S8000 DRX transceiverarchitecture.

Dualcoupling cells are only available for BTSs equipped withnon mixed DCU4 or DRX transceiver architecture.



condition

Description : Condition for calling the counting mechanism when a counteris involved

The following fields can be combined in the logicalexpression:

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 processornumber

alarm < = >

faultNumber alarm < = >

operationalState state change =

perceived severity alarm =

postMortem alarm =

usageState state change =

The “postMortem” field can take two values, either “beforeBSC restart” or “after bsc restart”. They have the followingmeaning:

before BSC restart means that the notification issued by theBSC was received by the OMC–R agent without the BSChaving restarted (nominal conditions).

after BSC restart means that the notification was issued bythe BSC and the BSC was restarted before the OMC–Ragent received the notification. These notifications do nottrigger alarms.


PE/DCL/DD/0124411–9001–124


The following logical operators can be used in the logicalexpression:

& stands for the logical AND.

| stands for the logical OR.

! stands for the logical NOT.

Value range : [logical expression]Object : alarm criteria

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

Type : DP

configRef Class 2

Description : Reference name of a DLU (Data Loading Unit) configurationfile. Check BSS upgrade file.

Value range : [1 to VVV]Object : btsSiteManager

Type : DP

Checks : [C/M]: The attribute value must be set according to astatic configuration file.


Note : If the attribute is nonzero, the user must check that the DLUconfiguration file exists on the concerned BSC disk, since nocheck is performed by the OMC–R.

The configRef is an ASCII-coded integer in base 32 thatallows to code the version of the DLU configuration file asseven characters (xxaYYYz).

The btsDescription parameter gives the transcription of theconfigRef parameter.

configRefList V13

Description : This attribute identifies the list of available configRef for abtsSiteManager EFT. For another object class instance, thisattribute is empty. This attribute is allocated by the MD–R atobject creation. This attribute cannot be modified by theManager.

Value range : [0 to 150]Object : executableSoftware

Type : DP



configurationType

Description : Type of configuration the alarm criterion belongs to

The manufacturer configuration is known as the referenceconfiguration. The operator configurations are known as thedaytime configuration, the nighttime configuration, and thespecific (or particular) configuration. Refer to the alarmcriteria entry in the Dictionary.

Value range : [manufacturer / operator]Object : alarm criteria

Type : DP

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

confusion Class 1 V8

Description : Whether the CONFUSION messages are used (Phase IIcompliance)

Value range : [false]Object : signallingPoint


Type : DP

Checks : [C/M]: The only accepted value is “false”.

[M]: The parent bsc object is locked.

Remark : Since the system accepts only one value for this attribute,changing it has no meaning.

Counter list V12

Description : Type of the counter list displayed

Value range : [default / all]

“default”: the default counter list

“all”: the whole counter listObject : report template

Type : DP

counter list filename V11

Description : Full pathname of the counter list file

Object : bscCounterList

Type : DP


PE/DCL/DD/0124411–9001–124


counterId

Description : Q3 name of a permanent BSS observation counter. See toNTP < 125 >.

Value range : [50 characters max, case sensitive]Object : mdWarning – detection function = “outOfRangeCounter”

Type : DP

counters V11

Description : List of the Q3 names of the counters eligible for observation,which are in the counter list filename

Object : bscCounterList

Type : DP

cpueNumber Class 1 C20 V12

Description : Number of the CPU/BIFP board chosen for managing theradio site and its related equipment.

BSC CPUE 0 CPUE 1

BSC 12000 “HC”,12000/6000types 3, 4, 5

BIFP0 BIFP 1

Value range : [noValue / 0 / 1]

“noValue”: let BSC determine BIFP board number onwhich the new site is attached

“0”: attach the new site to BIFP0

“1”: attach the new site to BIFP1Object : btsSiteManager

Default value : no value, 0

Type : DP

Feature : CPU/BIFP load sharing (AR874 – V12)

Checks : [C]: The btsSiteManager object is limited according tothe cpueNumber attribute value.

[C]: The transceiverEquipment object instancenumber is limited according to the cpueNumberattribute value.

[C/M]: This attribute can only be modified if the BSCBDA is not built.

Note : This parameter only applies to type 3 to type 5 BSCs.



cpueOccurrence

Description : Number of the CPU/BIFP board selected by the BSC formanaging the radio site and its common equipment.

This attribute is dynamically managed by the BSC.


Type : DD

cRC Class 2

Description : Whether the CRC (Cyclic Redundancy Check) test on PCMlinks is used by the DDTI board controlling the PCM link

pcmCircuit object dependent on a bsc object (Abis or Aterinterface):

If a CRC frame checking method is used, the DDTI board inthe BSC and the DTI board in the BTS to which the PCM linkis connected must be appropriately configured, as follows:

DDTI board: CS17 or CS18 jumper is ON (seeNTP < 22 >).

DTI board: CS17 jumper is ON (see BTS ReferenceManuals).

PCMI board: SW2 or SW3 jumper is ON (see BTSReference Manuals)

pcmCircuit object dependent on a transcoder object (Ainterface):

If a CRC frame checking method is used, the DDTI board inthe TCU to which the PCM link is connected must beappropriately configured: CS17 and CS18 jumpers are ON(see NTP < 16 >).

In case of mismatch, the DDTI configuration takes precedenceover the CRC state and a fault message is sent to the OMC–R.

Value range : [used / not used]Object : pcmCircuit

Default value : not used

Type : DP

Checks : [M]: The parent bsc is unlocked and the pcmCircuitobject is locked.


PE/DCL/DD/0124411–9001–124


creator V11

Description : Report template creator name


Type : DP

criteriaEventType

Description : Type of the notifications handled by the alarm criterion

Selecting “alarmNotification” includes all Q3 alarmnotifications such as communicationAlarm,equipmentAlarm, environmentalAlarm,processingError-Alarm, and qualityOfServiceAlarm.

Selecting “stateChangeNotification” includes all Q3 statechange notifications.

Value range : [alarmNotification / stateChangeNotification]Object : alarm criteria

Type : DP

CTU cable V13

Description : The CTU (cable transition unit) provides the physical interfaceto the customer’s spans in the BSC e3 and the TCU e3.


True value: No break in the copper connection from the CTUto the IEM module of the LSA.

False value: The cable is improperly installed from the CTUto the IEM module of the LSA or some break in the copperconnection from the CTU and the IEM module of the LSA.

Object : iem

Type : DD

Feature : AR 1209 – V13.1

current log size

Description : Current log size expressed in bytes


Type : DP

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



currentChannelHorqd Class 1 C21 V12

Description : Whether the “Current channel” element is used or not in theHANDOVER REQUIRED messages (Phase II compliance).




Type : DP


cypherModeReject Class 1 V8

Description : Whether the CYPHER MODE REJECT messages are used(Phase II compliance)



Type : DP



PE/DCL/DD/0124411–9001–124


D

data mode 14.4 kbit/s Class 2 V11

Description : Whether data 14.4 kbit/s transmission rate is allowed

Value range : [disabled / enabled]Object : transcoderBoard


Type : DP

Checks : [M] : Related software object release must be V11+release.

[M] : The version attribute of the parent transcoderobject must be set at “TCB_2”.

[M] : The parent bsc object is unlocked and thetranscoderBoard is unlocked.

data non transparent mode Class 3 V11

Description : Set of transmission rates used for data non transparent modetransmission on the Radio interface (MS ↔ BTS) and Abisinterface (BTS ↔ BSC)

Value range : [9.6 / 14.4] (kbit/s)

Object : bts

Default value : 9,6

Type : DP

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

[C/M]: The only allowed configurations are thefollowing:

• “9.6”

• “9.6” and “14.4”



data non transparent mode Class 3 V9

Description : Set of transmission rates used for data non transparent modetransmission on the Radio interface (MS ↔ BTS) and Abisinterface (BTS ↔ BSC)

Value range : [9.6 / 14.4] (kbit/s)


Default value : 9.6 kbit/s

Type : DP



• “9.6”

• “9.6” and “14.4”

data transparent mode Class 3 V11

Description : Set of transmission rates used for data transparent modetransmission on the Radio interface (MS ↔ BTS) and Abisinterface (BTS ↔ BSC)

Value range : [“1.2/0.075” / 0.6 / 1.2 / 2.4 / 4.8 / 9.6 / 14.4] (kbs)

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)


PE/DCL/DD/0124411–9001–124


data transparent mode Class 3 V9

Description : Set of transmission rates used for data transparent modetransmission on the Radio interface (MS ↔ BTS) and Abisinterface (BTS ↔ BSC)

Value range : [“1.2/0.075” / 0.6 / 1.2 / 2.4 / 4.8 / 9.6 / 14.4] (kbit/s)Object : signallingPoint

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)

Data14_4OnNoHoppingTs Class 3 V12

Description : Whether data 14.4 kbit/s transmission rate is allowed at btslevel on the non hopping TSs

Value range : [disabled / enabled]Object : bts


Type : DP


date

Description : Date on which the observation report was created

Date format entry forms are detailed in NTP < 130 >.

Value range : [<date>]Object : Display daily report

Type : DP

date

Description : Date on which data to archive were recorded


Value range : [<date>]Object : md – Archive

Type : DP

Note : Archiving fault, observation, or trace data is not possible forthe current day.



date

Description : Date on which data to restore were recorded


Value range : [<date>]Object : md – Restore

Type : DP

date

Description : Date on which data to archive were recorded


Value range : [<date>]Object : omc – Archive/Restore

Type : DP

Note : Archiving fault, observation, or trace data is not possible forthe current day.

date

Description : Date on which data to restore were recorded


Value range : [<date>]Object : omc – Restore

Type : DP

day intervention

Description : Type of action associated with an alarm criterion in thedaytime configuration

Value range : [noAlarm / critical / major / minor]Object : alarm criteria

Type : DP

Day to be purged V10

Description : Date on which the data to purge were recorded


Value range : [<date>]Object : omc – Data purge

Type : DP


PE/DCL/DD/0124411–9001–124


dDTIIntState

Description : Internal state of the DDTI board controlling the PCM link


working The board is correctly configured.. . . . . . . . .

fault The board configuration was. . . . . . . . . . . . unsuccessful.

Object : pcmCircuit

Type : DD


delayBetweenRetrans Class 2 D1 V8

Description : Number of occurences of a paging sub-group that separatestwo transmissions of the same paging message.


retransDuration ≥ (delayBetweenRetrans + 1) x nbOfRepeat


Default value : 0

Type : DP


deltaUtc

Description : Gap between the current OMC–R agent time and the GMTreference. Enter a positive value [+m] when the OMC–Ragent is located east of the Greenwich meridian and a negativevalue [–m] when it is located west.

Value range : [–1440 to +1440] minute

The range of possible values allows to update the OMC–Rreference time within ± 24 hours.

Object : md

Type : DP

Remark : Setting this attribute does not change the time displayed in thesystem “Session informations” window which refers to theworkstation internal clock.



detectionFunction

Description : Associated function

Value range : [excessiveAnomalyRate / outOfRangeCounter]Object : mdWarning

Type : DP

directedRetry Class 3D2 V9

Description : Minimum signal strength level received by the mobiles to begranted access to the neighbor cell, used in processingdirected retry handovers in BTS mode



Default value : >–48 dBm

Type : DP


directedRetryModeUsed Class 3 D3 V9

Description : Specify how directed retry handovers are processed in a celleither directly by the BSC (microcells only) or by queryingthe 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 amicrocell (cellType) and the adjacent cellumbrella Ref attribute is defined.


Note : The micro cell should be entirely covered by the macro cell inorder to use efficiently the bsc mode.

The use of the bts mode is recommended in a hot spot whenthese are several micro cells under the umbrella. The bts modeallows the use of micro cells to rescue the umbrella cell andalso avoids a saturation of the umbrella cell.

The bts mode is also recommended for all other cases.


PE/DCL/DD/0124411–9001–124


directedRetryPrio D4 V12

Description : Defines the number priority for directed retry handovers


Object : bts

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

Type : DP

directory

Description : Name of the directory to create on the OMC–R agent disks forstoring an EFT containing a BSS software version

The directory name identifies the type and version of the BSSsoftware to be later stored. Refer to the eft entry in theDictionary.

If the directory exists on the OMC–R agent disks, the user iswarned.

Value range : [BSxabvcdefgh (BSC software) / XXXabcdef (others)]

Object : md – Create EFT dir

Type : DP

distHreqt Class 3 D5

Description : Number of distance measurements, used to compute theweighted average MS-to-BTS distance in handoveralgorithms



Default value : 4

Type : DP

Checks : [C/M]: distHreqt is equal to the number of weights indistWtsList (refer to the next entry).




distWtsList Class 3 D6

Description : List of no more than sixteen weights, used to compute theaverage MS-to-BTS distance from distHreqt measurements

The L1M function balances distHreqt raw measurements withthe weights defined in the distWtsList list. Each measurementis partnered with one weight in the list. Weight/measurementassociations are set in the order which the weights arerecorded. The latest received measurement is alwayspartnered with the first weight in the list.

Super-average = [∑ (measurementi x weighti)] / 100, i = 1 to distHreqt

Value range : [0 to 100] %Object : handOverControl

Default value : 40 30 20 10

Type : DP

Checks : [C/M]: The number of weights in the list is equal todistHreqt and their sum equals 100.


diversity Class 2

Description : Whether reception diversity is allowed in a cell



Type : DP


dLPwrValue Class 3 V12

Description : Power reduction applied to PDCH compared to BCCH

Value range : [0 to 3]Object : transceiver

Default value : 0


Type : DP



PE/DCL/DD/0124411–9001–124


drxTimerMax Class 3 V12

Description : Maximum value allowed for mobile stations to requestnon–DRX mode after packet transfer mode

Value range : [0 (0s), 1 (1s), 2 (2s), 3 (4s), 4 (8s), 5 (16s), 6 (32s), 7 (64s)]

The deactivation value for the sub–feature TF1220.3 transfernon DRX mode is 0.


Default value : 0 s

Feature : GPRS (SV407 – V12, and TF1220 V12.4c)

Type : DP


dtxMode Class 3 D7

Description : MS control of the discontinuous transmission mechanism in acell

Discontinuous transmission is designed to lessen MS batteryconsumption and diminish interference by breaking off thetransmission when no data or speech are being transmitted.

Value range : [msMayUseDtx / msShallUseDtx / msShallNotUseDtx]

Object : bts

Default value : msMayUseDtx

Type : DP


Remark : The cellDtxDownlink attribute allows users to control the useof discontinuous transmission on the downlink. Refer to thisentry in the Dictionary.



duplex link state V10

Description : Active/passive chain link state


Type : DD

duration

Description : Time delay before running the next command

The Sleep command can be inserted in a command file as manytimes as necessary.


Object : commandFile – Sleep command

Type : DP

dwAckTime Class3 (packetAckTime) V12

Description : Time defining the period for the acknowledgments fordownlink transfers

Value range : [1 to 64] steps 100 ms for downlink transfer (step size is100 msec)


Feature : GPRS (SV407 – V12 and TF1220 – V12.4c)

Type : DP



PE/DCL/DD/0124411–9001–124


E

early classmark sending Class 3 E1 V10

Description : Whether Early classmark sending procedure initiated by amultiband MS is allowed.

The information is broadcast to the mobiles at regular intervalson the cell BCCH (SYQ INFO 3).

Value range : [Not Allowed, Allowed]Object : bts

Default value : Not Allowed

Type : DP

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

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 “efdObs” type object, an “efdSpecificNotif” type object, an“efdStateChange” type object, an “efdTrace” type object, andan “efdClass” type object. Refer to the efdType entry.

The administrativeState attribute of an efd object sets theconditions for forwarding the associated messages to theOMC–R manager.

Value range : [0 to 2147483646]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 /efdStateChange / efdTrace / efdClass]

An “efdAlarm” type object tallies alarm notifications issuedby the OMC–R agent.

An “efdConfiguration” type object tallies object create and setmessages issued by the users and attribute value changemessages issued by the BSC.

An “efdObs” type object tallies observation messagescollected by the OMC–R agent.

An “efdSpecificNotif” type object allows users to define setsof specific notification messages to process such asendOfArchival, endOfRestore, beginningOfBdeArchival,downloadEnd, endOfBdeArchival, endOfBdaBuiding,endOfMarkingConsultation, or endOfSoftwareChange.

An “efdStateChange” type object tallies object state changenotifications.

An “efdTrace” type object tallies trace messages collected bythe OMC–R agent.

An “efdClass” type object tallies efd class objects creation anddeletion messages. Thus these notifications enable to identifythe external managers which are being connected to theMD–R.

Object : efd

Type : DP



PE/DCL/DD/0124411–9001–124


eft

Description : Name of an EFT (set of transferable files) containing a BSSsoftware version

The name of the EFT identifies the type and version of the BSSsoftware it contains. Refer to the eft entry related to thesoftware object in the Dictionary.

The Create EFT command validates EFT downloading on theOMC–R agent disks, in the matching directory created for thatpurpose. Refer to the directory entry in the Dictionary.

The software can then be dowloaded to the concerned BSCdisk with a Download command on the software object relatedto an object of the same type. Refer to the eft entry related tothe software object in the Dictionary.


Object : md – Create EFT / Delete EFT

Type : DP

Checks : [C]: If mergeEFT is “False”, the EFT does not exist inthe matching directory on the OMC–R agentdisks.

[D]: The EFT exists in the matching directory on theOMC–R agent disks and no software object refersto the software version contained in the EFT.

eft

Description : Name of an EFT (set of transferable files) containing a BSSsoftware version

The name of the EFT identifies the type and version of the BSSsoftware it contains. Refer to the eft entry related to thesoftware object in the Dictionary.

This command copies the EFT stored on the OMC–R managerdisks by a Read Gigatape command to the matching directoryon the OMC–R agent disks.


Object : omc – Download EFT to md

Type : DP

Checks : [A]: The EFT exists on the OMC–R manager disks.



eft

Description : Name of the EFT to download to the BSC disk. It must matchthe type of the parent object related to the software object.

The name of the EFT identifies the type and version of the BSSsoftware to donwload, as follows:

BSC software: Format = “BSxabvcdefgh”

Field Meaning Value

BSx Type of software x = [1 .. 3]

ab Version number [09 .. 32]

v Reserved

cd Sub-version number [01 .. 99]

ef Edition number [01 .. 99]

gh Revision factor [01 .. 99]

BTS and TCU software: Format = “XXXabcdef”

Field Meaning Value

XXX Type of software BCF : BCF / BC1 / BC2 / SBC / PICTRX : TRX / DRX / TR1 / PICTCB : TCB/TC1/TC2


c Sub-versionnumber

BCF : [A .. H]TRX : [A .. H]TCB : [A .. H]


PE/DCL/DD/0124411–9001–124


Field ValueMeaning

d Edition number BCF : [1 .. 8]TRX : [1 .. 8]TCB : [1 .. 8]

ef Revision factor BCF : [01 .. 32]TRX : [01 .. 32]TCB : [01 .. 64]

If downloading is successful, the system sets the value of thesWVersionNew attribute of the software object to the versionof the new software downloaded to the BSC disk.


Object : software – Download

Type : DP

Checks : [A]: The first three letters of the EFT name match thetype of the managed object related to the softwareobject. For a software-bsc object, themanufacturing release corresponds to thebscType attribute of the related bsc object.

[A]: Downloading of the EFT on the OMC–R agentdisks is validated. Refer to the eft entry related tothe md or omc object in the Dictionary.

[A]: No directory creation command is in-progress forthe EFT. Refer to the directory entry in theDictionary.

[A]: The parent bsc object is unlocked.

emergencyCallPriority Class 3 E2

Description : Index in the table allocPriorityTable for a TCH allocationrequest whose cause is “emergency call”



Object : bts

Default value : 17

Type : DP




eMLPPThreshold Class 3 E3 V12

Description : Defines the minimum value that the eMLPP Precedence of anincoming call must have to be taken into account by the BSSwith inband signalling (paging and vbs/vgcs assignmentrequest)

Value range : [none / priority 4 / priority 3 / priority 2 / priority 1 / priority 0/ priority B / priority A]


Default value : none

Type : DP

Feature : ASCI (GSM–R V12)


encrypAlgoAsscomp Class 1 V8

Description : Whether the “Chosen encryption algorithm” element is usedin the ASSIGN COMPLETE messages (Phase II compliance)




Type : DP


encrypAlgoCiphModComp Class 1 V8

Description : Whether the “Chosen encryption algorithm” element is usedin the CIPHER MODE COMPLETE messages (Phase IIcompliance)




Type : DP



PE/DCL/DD/0124411–9001–124


encrypAlgoHoperf Class 1 V8

Description : Whether the “Chosen encryption algorithm” element is usedin the HANDOVER PERFORMED messages (Phase IIcompliance)




Type : DP


encrypAlgoHoreq Class 1 V8

Description : Whether the “Chosen encryption algorithm” element is usedin the HANDOVER REQUEST ACKNOWLEDGEmessages (Phase II compliance)




Type : DP


encryptionAlgorSupported Class 1

Description : Type of ciphering capability supported by the BTSs of a BSS.When no ciphering capability is supported, users’ calls are notcrypted.

Value range : [none / gsmEncryptionV1 (A5.1) / gsmEncryptionV2 (A5.2)]

Object : bsc

Default value : gsmEncryptionV1

Type : DP

Checks : [C/M]: Only one type of ciphering capability is defined.




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

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 thecurrent date). It is on or after start date.



Value range : [<date>]

Object : System session log – Filter

Type : DP

Checks : [A]: end date is on or after start date.

End of probative Phase Type V11

Description : Whether the user validate or cancel the software change afternew EFT activation

See to NTP < 128 >.

Value range : [validate software change / cancel software change]Object : bsc – End of probative phase

Type : DP

Note : This parameter only applies to BSC Upgrades with prototypeBDA change (BSC Version Upgrade and BSC EditionUpgrade).


PE/DCL/DD/0124411–9001–124


end time

Description : Absolute time of final job run if the job is to be periodicallyrun over a limited period of time


If date matches the date in start time, fill in time with a valueafter start time.


Object : job

Condition : To define when a job periodicity is defined and only if the joblife is limited (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 (defaultis 24:00)



Value range : [<time>]


Type : DP

Checks : [A]: If end date and start date are identical, end timeis 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 aredescribed under the startAlarmFilter entry in the Dictionary.

Value range : [logical expression]


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

Type : DP



endAlarmThreshold

Description : Minimum counting value in the reference period, below whichan end-of-alarm message is sent if the correspondingstart–of–alarm message was sent first. The value must bechecked by users.

This attribute defines a minimum value read at the end of thedefined refPeriod. It must be lower thanstartAlarmThreshold.

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 (thresholdHigh)counting value in the reference period, above/below which anend of “lower threshold/upper threshold” alarm message issent if the corresponding start-of-alarm message was sentfirst. The value must be checked by users.

If thesholdType is “thresholdLow”, it defines a minimumvalue for a one minute reference period (or the countercollecting period for PCM unavailability counters), abovewhich the end of “lower threshold” alarm message is sent. Itmust be greater than startAlarmThreshold “low”.

If thesholdType is “thresholdHigh”, it defines a maximumvalue for a one minute reference period (or the countercollecting period for PCM unavailability counters), belowwhich the end of “upper threshold” alarm message is sent. Itmust be lower than startAlarmThreshold “high”.


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 mechanismis described in NTP < 07 >.


PE/DCL/DD/0124411–9001–124


endCounterThreshold

Description : Maximum counting threshold when a counter is involved



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

Type : DP

endSearchTime

Description : Absolute time to end searching for the observation reports tocumulate. It is six hours before beginSearchTime at the most.

Observation data accumulating ends with the informationcontained in the first observation message collected in therequested period of time. Refer to the partneredbeginSearchTime 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 sixhours.

endSearchTime

Description : Absolute time to end searching for the observation report toedit (default is one hour before beginSearchTime)

The report displays the information contained in the lastobservation message generated in the requested period of time.Refer to the partnered beginSearchTime entry in theDictionary.



Object : Display raw report

Type : DP




endSearchTime

Description : Absolute time to end searching for the avalaible permanentobservations to list (default is twelve days beforebeginSearchTime)

The last listed report is the first observation report generatedin the requested period of time. Refer to the partneredbeginSearchTime entry in the Dictionary.


Value range : [<date>,<time>]Object : List available permanent observations messages

Type : DP


endSearchTime

Description : Absolute time to end searching for the avalaible permanentobservations to list (default is twelve days beforebeginSearchTime)

The last listed report is the first observation report generatedin the requested period of time. Refer to the partneredbeginSearchTime entry in the Dictionary.


Value range : [<date>,<time>]Object : List available temporary observations messages

Type : DP


endSearchTime

Description : Absolute time to end searching for the observation messagesto list (default is twelve days before beginSearchTime)

The last listed message is the first observation messagegenerated in the requested period of time. Refer to thepartnered beginSearchTime entry in the Dictionary.


Value range : [<date>,<time>]Object : List observation messages

Type : DP



PE/DCL/DD/0124411–9001–124


endSessionCriteriaType

Description : Definition of the criterion that will end a call path tracingsession

Value range : [duration / number (of calls) / oam (locking the callPathTraceobject)]

duration endSessionCriteriaDuration =. . . . . . . . . [5 to 1080] minutes

number endSessionCriteriaNbCall =. . . . . . . . . . [1 to 2500]

oam administrativeState = “locked”. . . . . . . . . . . .

Only one criterion is defined. When it is true, the callfollow–up session is stopped in the BSS. Refer to theusageState entry related to this object in the Dictionary.


Type : DP

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

Note : The session is automatically restarted by unlocking the object,regardless of the end-of-session criterion.

enhancedTRAUFrameIndication E4 V12

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)

Notes : This attribute is set to “available” only if thetranscoderBoards of all the related TCUs are of TCB2board type and their software are V12.

This attribute is set to “active” only if thepcmErrorCorrection attribute of one bts object related tothe BSC is set to “1”.

Only BTSs equipped with non mixed DCU4 or DRXtransceiver architecture can support the Enhanced TRAUFrame.



equipment processor number

Description : To select a processor or an equipment in the preselected type

Consult the corresponding notification messages (“Equipmentnumber” field).

Do not fill in if neither bsc equipment name nor btsequipment name is defined or if this criterion is not to beselected.



Type : DP

error concealment unit Class 2 V11

Description : Whether the Error Concealment Unit (ECU) is used. The ECUprovides a voice quality improvement on the uplink in badradio propagation conditions.

Value range : [not used, used]

Object : bts

Default value : used

Type : DP

Checks : [M] : The parent bsc object is unlocked and the btsobject is locked

errorCorrectionMethod Class 3

Description : Type of correction method used on the A interface

Value range : [basicRetr (only value accepted) / prevCyclRetr]


Default value : basicRetr

Type : DP

Checks : [C/M]: The only accepted value is “basicRetr”.




PE/DCL/DD/0124411–9001–124


exclusive interval of codano V12

Description : To select messages according to their fault number.

The filter can contain one (or several) intervals defining thefault numbers not to be retrieved. For example, interval 5~8enables to retrieve ALL the fault numbers except faultnumbers 5, 6, 7, and 8.

Value range : [0 to 65535 – 0 to 65535]


Type : DP

exclusive list of codano V12

Description : To select messages that do not contain one (or several) givenfault number(s).



Type : DP

executableSoftwareId V13

Description : Identifier of a ‘executableSoftware’ object class. Thisidentifier is allocated by the MD–R at object creation, if notgiven by the Manager. This attribute cannot be modified.



Type : DP

executableSoftwareName V13

Description : Name of a software version. This attribute is allocated by theMD–R at object creation, if not given by the Manager. Thisattribute cannot be modified.



Type : DP



extCommsInt

Description : State of the X.25 links set up from the BSC chain X.25 ports[working / fault]. Each port is identified with regard to themother SICX board

working The X.25 link is correctly initialized.. . . . . . . . .

fault An error was detected (SLS board. . . . . . . . . . . . faulty, etc.).

Value range : [0 to 65535]Object : bsc – Display chain information

Type : DD


extended cell Class 2 E5 V9

Description : Whether the cell is extended (up to 120 km large) or not

The cell working mode governs the upper limit of thefollowing attribute values (refer to theses entries in theDictionary):

callClearing, msRangeMax, andrndAccTimAdvThreshold attributes of the bts object

concentAlgoExtMsRange andconcentAlgoIntMsRange attributes of the associatedhandOverControl object if the bts object describes aconcentric cell

Value range : [true (extended) / false (normal)]Object : bts


Type : DP

Checks : [M]: If the attribute is changed to “true” and a CBCHis defined for the cell, this channel is carried by aradio time slot with an even identifier number.Refer to the channelType entry in the Dictionary.


Note : In that mode, the radio time slots with odd identifier numbersare unknown to the BSC and the diversity functionality is notavailable in the cells.


PE/DCL/DD/0124411–9001–124


external alarm configuration Class 2 V9

Description : Configuration of the external alarm loops controlled by a BTS.Alarm loop “n” is monitored (not monitored) when the nth bitis set to 1 (0) in the binary field. The alarm mask isimmediately displayed in the hexadecimal field just below.The alarm mask can be set using the hexadecimal field as wellas the binary field.

The number of connectors per alarm board depends on the typeof the alarm boards installed in the BTS.

BTS Type of board Number of protectedexternal alarms

per cabinet

S2000 ALATO 4

S2000H/L SBCF 6

S4000 Indoor ALAT 4

S4000 Outdoor ALATO 4

S4000 Smart ALATO 4

S8000 ALCO 16

The correspondence between those 48 bits and the externalalarms of each site directly depends on three factors: the typeof BTS, the number of cabinets, and the convention fornumbering those cabinets.

S4000: 24 external alarms max., 6 cabinets – 4 externalsalarms per cabinet. Therefore 4 bitsby cabinets placed on the mask on thesame order of the numbering of thecabinets.Exemple: to unmask all the externalalarms of S4000 Indoor S22 thealarm mask would be:

“1111 0000 1111 0000 0000 0000 0000 0000 0000 0000 0000 0000”

Base cabinet1st cabinet of the 1st sector

Extension cabinet1st cabinet of 2nd sector

Extension cabinet2nd cabinet of 1er sector



S8000: 48 external alarms max., up to 3 cabinets in thefuture – 16 alarms per cabinet (16 bits percabinet).

S2000H/L: 18 external alarms max., up to 3 cabinets in thefuture – 6 alarms per cabinet (6 bits percabinet).

Value range : [48-bit register]Object : btsSiteManager

Default value : 48 bits equal to “0”

Type : DP


external battery cabinet Class 2 V9

Description : Presence or absence of the optional equipment “ancillarybattery cabinet” in S8000 Outdoor

Value range : [Present / Absent]


Type : DP


externalTime

Description : Current OMC–R agent date and time



Object : md

Type : DP

Remark : Setting this attribute does not change the time displayed in thesystem “Session informations” window which refers to theworkstation internal clock.


PE/DCL/DD/0124411–9001–124


F

Family V11

Description : Family of counters in which are chosen the counters to beobserved

The list of the available families depends on the Observedobject class and the observation type selected in the reporttemplate definition of the observation. See Tables hereafter.

Value range : [A interface / ABIS interface / Abis interface / BSC / BSCBSCB / BSC CPUM / BSC SICD / BSC TSCB / CCCHmonitoring / Channel mode / CPUE / Dedicated channelassignment / Directed retry / Establishment / Globalhandovers / Handovers / Inter–bss handovers / Intra–cellhandovers / Layer One Management / OMC interface /Releases of communications / SDCCH allocations / SMS /synthetic / TCH allocations]

Object : report template

Type : DP

Checks : [M] : Only one family type of counters can be selectedfor each observation report.

Observed object: bsc

Observation real time (ORT) A interfaceBSCsynthetic

Observation fast statistic(OFS)

A interfaceOMC interfaceReleases of communicationsChannel modeTCH allocationsBSCBSC SICDCPUEBSC CPUMABIS interfaceBSC BSCBBSC TSCBsynthetic



Observed object: bts

Observation real time (ORT) SDCCH allocationsTCH allocationsEstablishmentGlobal handovers


SDCCH allocationsTCH allocationsChannel modeIntra–bss handoversInter–bss handoversDedicated channel assign-mentGlobal handoversEstablishmentReleases of communicationsLayer One ManagementInterferencesDirected retrySMSAbis interfaceCCCH monitoringsynthetic

Observed object : transceiverZone

Observation real time (ORT) SDCCH allocationsTCH allocations


SDCCH allocationsTCH allocationsIntra–cell handovers

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


PE/DCL/DD/0124411–9001–124


fhsRef Class 2 F1

Description : Identifier of the frequencyHoppingSystem object that definesthe frequency hopping management parameters for the radiotime slot

Setting this attribute and the maio attribute allows the time slotto obey frequency 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 isnot allowed for the parent bts object(btsIsHopping = “no hopping”) or thechannelType of the channel object is“mainBCCH”, “mainBCCHCombined”, or“bcchSdcch4CBCH”.

[C/M]: If the attribute is defined, the following ischecked:

• The maio attribute is also defined.

• The referenced frequencyHoppingSystem object iscreated for the parent bts object.

• Each frequency occurs once in the mobileAllocationlist and is allotted in the cellAllocation list of the parentbts object.

• The number of frequencies in the mobileAllocation listis greater than the maio attribute value.

• Concentric cell: The frequencies in themobileAllocation list are not used in the zone to whichthe parent transceiver object does not belong.




forced handover algo Class 3 F2 V9

Description : Minimum signal strength level received by the mobiles to begranted access to a neighbor cell in case of forced handover

Value range : [less than –110, –110 to –109, ..., –49 to –48, morethan –48] dBm


Default value : less than –110

Type : DP


frequencyHoppingSystem

Description : Identifier of a frequencyHoppingSystem object that definesfrequency hopping management parameters for radio timeslots that obey frequency hopping laws. A bts object mayreference up to sixty-four objects of this type.

Refer to the hoppingSequenceNumber andmobileAllocation entries in the Dictionary.

Value range : [0 to 2147483646]Object : frequencyHoppingSystem

Type : Id

Checks : [C]: The associated bts object is created and thefrequencyHoppingSystem object is not createdfor that object.

[C]: The number of frequencyHoppingSystem objectscreated for a bts object is limited to sixty-four.


[M]: The parent bsc object is unlocked and theassociated bts object is locked.

[M/D]: The frequencyHoppingSystem object is created.


[D]: No channel object dependent on the bts objectrefers to the frequencyHoppingSystem object(fhsRef attribute).


PE/DCL/DD/0124411–9001–124


G

geographical coordinates V11

Description : Definition of the geographical coordinates of the equipment inthe network

These coordinates are defined by a latitude and a longitude,each expressed 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. . . . . . . . .

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

Hundrethof sec Lon [0 to 5999] hundredth second. . . . . . .

Direction Lon [East / West]. . . . Object : bsc

btsSiteManagermdtranscoder

Type : DI

geographical coordinates V12

Description : Definition of the geographical coordinates of the pcuSNequipment in the network

These coordinates are defined by a latitude and a longitude,each expressed 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 ofsec 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 ofsec Lon [0 to 5999] hundredth second. . . . . . . . .

Direction Lon [East / West]. . . .

Object : pcusn


Type : DI

gprsAvgParam Class 3 V12

Description : This parameter is composed of the following attributes:

nAvgI

nAvgT

nAvgW

Refer to these entries in the NTP < 124 >.

gprsBtsExtendedConf V12


minNbrGprsTs

gprsPreemption

gprsPreemptionProtection

T3172

N3103

maxDwAssign

maxUpTbfP1P2Threshold

maxDnTbfP1P2Threshold

maxUpTbfPerTs

maxDnTbfPerTs

longTbfSizeThreshold

longTbfLossThroughput

nbrFreeTchBeforeAnticipation


PE/DCL/DD/0124411–9001–124


nbrFreeTchToEndAnticipation

btsSensitivityInnerZone

maxBsTransmitPowerInnerZone

reserved3

reserved4

reserved5


gprsBtsLockExtendedConf V12


radioAllocator

msCapWeightActive

speechOnHoppingTs


gprsCellActivation Class 3 V12

Description : Flag used to activate the GPRS at cell level


Object : bts



Type : DP


gprsPcuCrossConnectList V12


pcmNbr

nbrTch

Refer to these entries in this Dictionary.



gprsPcuLockExtendedConf Class 2 V12


reserved1

reserved2

reserved3

reserved4

reserved5

Refer to these entries in this Dictionary..

gprsPermittedAccess Class 3 V12

Description : It defines the Routing Area Color (3–bit length) of the cell. Ifthe MS receives different values of the Routing Area Colorfield in two different cells, it shall interpret the cell reselectioninformation as if the two cells belonged to different RA.


Default value : 0


Type : DP


gprsPreemption Class 3 (gprsBtsExtendedConf) V12

Description : Set to yes, it allows the PCU to refuse GSM preemption overshared GSM/GPRS TS if GPRS resources are not sufficientto ensure the minimum bandwidth for each MS.

In the case of lack of GSM radio TS, the BSC has to allocateone shared GSM/GPRS radio TS to GSM and a preemptionprocedure is started. When one shared radio TS temporarilyallocated to GSM is released (end of GSM allocation due toend of call or handover), then a reallocation procedure isstarted to increase the GPRS capacity.

Value range : [yes / no]Object : bts

Feature : GPRS (TF1121 – V12)

Type : DP

Default value : yes



PE/DCL/DD/0124411–9001–124


gprsPreemptionProtection Class 3 (gprsBtsExtendedConf) V12

Description : Protection timer used by the BSC in order to reduce the loadin case of PCU TDMA TS Status Nack message receptionduring a preemption procedure. This message is sent by thePCU.

Value range : [1 to 60] second(s)Object : bts


Default value : 10

Type : DP


Comments : None

gprsPriority Class 2 (gprsTranscvLockExtendedConf) V12

Description : Priorities that can be affected to the TDMA

Priority affected to the TDMA when allocating packetressources.

Value range : [p1 or p2 (hight GPRS priority)]Object : transceiver

Default value : p1


Type : DP

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

gprsTimerWaitPUAM Class 3 V12

Description : Waiting timer for the reception of the uplink assignment aftersending a PACKET RESOURCE REQUEST message

This timer is used on the MS side to define when to stopwaiting for Packet Uplink Assignment Message after sendingof a PACKET RESOURCE REQUEST message

Value range : [500ms, 1s, 2s, 4s]Object : bts

Default value : 0.5 s


Type : DP




gprsTimerWaitRLC Class 3 V12

Description : Waiting timer for release of the TBF after reception of the finalblock

This timer is used on the MS side to define when the MS hasreceived all the RLC data blocks. When the timer expires theMS releases the resources associated with the TBF and beginsto monitor its paging.

Value range : [500ms , 1s, 2s, 4s]

Object : bts

Default value : 0 s


Type : DP


gprsTranscvLockBtsExtendedConf Class 2 V12


gprsPriority

maxNbrPDAAssig

N3105max

maxNbrRLCEmptyBlock

maxNbrPUDWithoutVChange

reserved1

reserved2

reserved3

reserved4

reserved5



PE/DCL/DD/0124411–9001–124


H

HandOver from signalling channel Class 3 H1

Description : Authorization to perform intercell handovers on signallingchannels (SDCCH or TCH in signalling mode)




Type : DP

Remark : The attribute was named TCH and sDCCHHandOver on theV8 OMC–R MMI.

handOverControl

Description : Identifier of a handOverControl object that defines handovermanagement parameters in a cell. A bts object may referenceone and only one object of this type.

Value range : [0 to 2147483646]


Type : Id

Checks : [C]: The associated bts object is created and thehandOverControl object is not created for thatobject.

[M]: The parent bsc object is unlocked. If class 2attributes are modified, the associated bts object islocked.

[C/D]: If the application database of the related BSC isbuilt, the parent bsc object is unlocked and theassociated bts object is locked.

[M/D]: The handOverControl object is created.

[D]: The associated bts object is not referenced, exceptby a powerControl object.




hardware configuration V11

Description : Type of architecture of the transceiverEquipment

Value range : [Dcu2 / Dcu4 / Drx]

Object : transceiverEquipment

Default value : Drx

Type : DP

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.



Type : DP

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

hardwareRef Class 2

Description : Hardware reference of a TCB. Check BSS upgrade file.



Type : DP

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


PE/DCL/DD/0124411–9001–124


hexa text V12

Description : Transcription in hexadecimal of the contents of a shortmessage.

The content of the hexa text parameter is displayed when usingthe command Display hexa. It cannot be modified by the user.Only the content of the text parameter can be modified by theuser.

Refer to the text (short message) entry in the Dictionary.

Value range : [chain of characters]Object : short message – Display hexa

Type : DI

hoMargin Class 3 H2

Description : Margin to use for PBGT handovers to avoid subsequenthandover, in PBGT formula

Value range : [–63 to 63] dBObject : adjacentCellHandOver

Default value : 4

Type : DP


hoMarginBeg Class 3 H3 V11

Description : Margin to be added to hoMargin until rxLevHreqave forearly handover mechanism in order to compensate the lack ofmeasurements

This parameter is coupled with hoMargin andrxLevHreqaveBeg.

Value range : [–63 to 63] dBObject : bts

Default value : 4

Type : DP


[M] : This parameter is inhibited when set to 63 dB.

Note : This parameter shall be set such as hoMargin ≤hoMarginBeg

This parameter is only available for DCU4 or DRX transceiverarchitecture.



hoMarginDist Class 3 H4 V8

Description : Margin to be used for Distance Handovers



Default value : –24 dB

Type : DP


hoMarginRxLev Class 3 H5 V8

Description : Margin to be used for signal strength Handovers




Type : DP


hoMarginRxQual Class 3 H6 V8

Description : Margin to be used for Signal Quality Handovers

Value range : [–63 to 63] dBObject : adjacentCellHandOver


Type : DP


hoMarginTiering Class 3 V12

Description : Hysteresis between the uCirDLH and lCirDLH tieringthresholds to avoid ping–pong handovers (expressed in dB)





Type : DP


PE/DCL/DD/0124411–9001–124


hoMarginTrafficOffset Class 3 H7 V12

Description : Minimum signal strength margin with the serving cell thatallows to select the best neighbor cell when a handover istriggered for overload reasons




Feature : Handover for traffic reasons (TF132 – V12)

Type : DP

Checks : [C/M]: This attribute must be in the range [0 63].

[C/M]: When set to “0”, the handovers for traffic reasonsare not allowed in the adjacent cell.


Note : This attribute only applies to BTSs equipped with non mixedDCU4 or DRX boards.

HOPingpongCombination Class3 H8 V12

Description : List of couples of causes (HOInitialCause andHONonEssentialCause) indicating the causes of ping–ponghandovers in the overlapping areas

The following causes are defined with regard to theneighboring cell:

HOInitialCause indicates the essential handover causewhich leads to enter the neighbor cell (cause of incominghandover).

HONonEssentialCause indicates the non–essentialhandover cause which leads to leave the cell (cause ofoutgoing handover).

This parameter defines the combination for which theHOPingpongTimeRejection attribute is used.



Value range : [rxQual, rxLev, distance, powerBudget, capture,directedRetry, OaM, traffic, all, allCapture, allPowerBudget]


Type : DP

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


Restrictions : For the moment the essential and non essential causes takeninto account are the following:

Only rxQual and rxLev causes apply to HOInitialCause.

Only powerBudget and capture causes apply toHONonEssentialCause.

Notes : The HOPingpongCombination list can hold up to 4 couplesof causes.

allCapture cause (only applying toHONonEssentialCause)matches the capture cause for allthe micro–cells belonging to the current macro–cell . Thiscause has to be used in order to prevent ping–ponghandovers between micro– and macro–layers.

allPowerBudget cause (only applying toHONonEssentialCause) matches the powerBudget causefor all the neighboring cells of the current cell. This causeis used in order to restore the “Minimum time betweenhandovers” (feature TF218).

HOPingpongTimeRejection Class 3 H9 V12

Description : Time before a new handover attempt can be triggered

Refer to bsc object timeBetweenHOConfiguration and btsobject bts time between HO configuration attributes in thisDictionary of Parameters for this timer activation.

Refer to adjacentCellHandOver objectHOPingpongCombination attribute in this Dictionary ofParameters for the combinations for which this timer applies.

To avoid ping–pong handovers this new timer is started aftera successful handover. Up to the expiration of this timer, thereceipt of HANDOVER INDICATION message is ignored.


PE/DCL/DD/0124411–9001–124


Value range : [0 to 60] s


Default value : [30 sec]

Feature : General protection against pingpong handovers (TF821–V12)


hoppingSequenceNumber Class 2 F3

Description : Hopping sequence number used by a radio time slot whichobeys frequency hopping laws.

Select different HSNs for nearby cells that use the same set offrequencies.


Object : frequencyHoppingSystem

Type : DP

Checks : [M]: If the frequencyHoppingSystem object isreferenced by a channel object (fhsRef attributedefined), the parent bsc object is unlocked and theassociated bts object is locked.

HOSecondBestCellConfiguration Class 3 H10 V9

Description : Number of neighbor cells in which the BSC immediatelyattempts to perform a new handover when the previoushandover attempt failed with return to the old channel

Giving the attribute a value greater than 2 allows the BSC torenew the handover request without waiting for a new set ofradio measurements (the first attempt is included in thiscount). The same list of neighbor eligible cells is used toprocess the request (no new list is provided by the BTS).


Object : bsc

Default value : 3

Type : DP




hoTraffic Class 3 H11 V12

Description : Whether handovers for traffic reasons at bsc level are allowed.

Value range : [disabled / enabled]Object : bsc


Type : DP



Note : Enabling this parameter allows the related BTSs with DCU4or DRX transceiver architecture handle handovers for trafficreasons.

hoTraffic Class 3 H12 V12

Description : Whether handovers for traffic reasons at bts level are allowed.

Value range : [disabled / enabled]Object : bts


Type : DP



Note : This attribute is only available for DCU4 or DRX transceiverarchitecture.


PE/DCL/DD/0124411–9001–124


I

identifier

Description : Identifier of a short message. It allows MSs to identify theshort message and discard it if already received.

Short message identifiers are assigned by the networkoperator.

Value range : [0 to 65535]Object : short message

Type : DP

identifier

Description : Name of a BSS software application followed by its versionnumber

Refer to the eft entry related to the software object in theDictionary where the name formats are explained.

Value range : [XXXabcdef]Object : software – Display markers

Type : DD

identifier

Description : Name of a BSC database configuration file followed by itsversion number

Refer to the eft entry related to the software object in theDictionary where the name formats are explained.

Value range : [BSxabvcdefgh]Object : software–bsc – Display markers

Type : DD

iemId V13

Description : Identifier of the ‘iem’ object class. This identifier is allocatedby the MD–R at object creation, depending on the shelf andslot numbers indicated by the BSC. This attribute cannot bemodified. This attribute is relevant for BSC e3 and TCU e3.

Value range : [0 to 2147483646]Object : iem

Type : DP



iMSIAttachDetach Class 2

Description : Whether MS attachment/detachment is allowed. Allowingenables the system to take into account temporary MS absenceto prevent unsuccessful call attempts.

Value range : [allowed / not allowed]Object : bts

Default value : allowed

Type : DP


inactivity timeout

Description : Maximum time between two user commands, over which thesystem induces an automatic logout procedure

Value range : [2 to 2147483646] (5) minuteObject : user profile

Type : DP

Remark : Moving the mouse inside an MMI window on the terminalscreen resets the counter.

inclusive interval of codano V12

Description : To select messages according to their fault number. Thefiltering list can contain one (or several) interval(s).

For example, interval 5~8 enables to retrieve fault numbers5, 6, 7, and 8.


Value range : [0 to 65535 – 0 to 65535]Object : Alarm and notification logs – Filter

Type : DP

inclusive list of codano V12

Description : To select messages according to their fault number. The filtercan contain one (or several) fault number(s).


Value range : [0 to 65535]Object : Alarm and notification logs – Filter

Type : DP


PE/DCL/DD/0124411–9001–124


incomingHandOver Class 3

Description : Whether incoming handovers are allowed in a cell

Value range : [enabled / disabled]Object : handOverControl


Type : DP


inhibitRequest

Description : Whether the SS7 channel should be inhibited

Value range : [true / false]Object : signallingLink – Set inhibit

Type : DP

Checks : [M]: The parent bsc object and the signallingLinkobject are unlocked.

Remark : An inhibit request may have no immediate effect and can evenbe refused. Run a Display all command on the signallingLinkobjet to display the resource state of the SS7 channel andcheck that the system has applied the request(signallingLinkResState).

inId V13

Description : Identifier of an ‘in’ object class. This identifier is allocated bythe MD–R at object creation. The only value allocated by theMD–R is 0. This attribute cannot be modified.

Value range : [0 to 0]Object : in

Type : DP

interBscDirectedRetry Class 3 I1 V9

Description : Whether inter-bss directed retry handovers are allowed ina BSS

Value range : [allowed / not allowed]Object : bsc


Type : DP


Note : Queuing must also be activated at BSC level.



interBscDirectedRetryFromCell Class 3 I2 V9

Description : Whether inter-bss directed retry handovers are allowed in acell

Value range : [allowed / not allowed]

Object : bts


Type : DP


Note : Queueing must also be activated at BSC level.

interCellHOExtPriority Class 3 I3

Description : Index in the allocPriorityTable that defines the processingpriority of incoming inter-bss handovers in a cell

This priority is used when radio resource allocation queueingis not requested by the MSC or not authorized in the BSS (referto the “bscQueueingOption” entry in the Dictionary).


Object : bts

Default value : 17

Type : DP


interCellHOIntPriority Class 3 I4

Description : Index in the allocPriorityTable that defines the processingpriority of incoming intra-bss handovers in a cell

This priority is always used, whether radio resource allocationqueueing is authorized in the BSS or not.


Object : bts

Default value : 17

Type : DP



PE/DCL/DD/0124411–9001–124


interferenceType Class 3 V12

Description : Type of interference created by neighbour cell

Value range : [notApplicable / adjacent / coChannel]


Default value : notApplicable


Type : DP


interferer cancel algo usage Class 2 I5 V10

Description : Correlation ratio of the input signals received from the normaland diversity antennas. This ratio enables to adapt the SPUsoftware (the interferer cancellation algorithm) to thepropagation conditions. Correlation ratio = 0 means that theinterferer cancellation algorithm is inactive.

Value range : [0 to 100] %

Object : bts

Default value : 0

Type : DP

Checks : [M] : The parent bsc object is unlocked and the btsobject is locked

internal DMUX alarm state

Description : State of the BSC chain equipment controlled by the ECI boardby means of alarm loops

Value range : The following is a list of equipment in alphabetical order:

Control bayextractor [all working / one failed]. . . . . . . . .

Control bay extractorpower supply [all working / one failed]. . . .

EQP fans [all working / one failed]. . . . . . . .

MPU converters [all working / one failed]. . .

MPU converter



(other channel) [all working / one failed]. . . .

MPU fan powersupply [all working / one failed]. . . . . . . . . . .

MPU fans [all working / one failed]. . . . . . . .

RCB0 [present / absent]. . . . . . . . . . .



Right MPUconverter [all working / one failed]. . . . . . . .

SWD converter [all working / one failed]. . .

BSC 2000

EQPD converter [all working / one failed]. . .

EQPM converter [all working / one failed]. .

EQPM EQPD fan [all working / one failed]. .

BSC 12000/6000

EQPD0 converter [all working / one failed]. .

EQPD0 EQPD1EQPI shelves fans [all working / one failed].

EQPD1 converter [all working / one failed]. .

EQPI converter [all working / one failed]. . .

EQPT fans [all working / one failed]. . . . . . .

EQPT and SWGshelf fans [all working / one failed]. . . . . . . .




Type : DD



PE/DCL/DD/0124411–9001–124


internal DMUX state

Description : Internal state of the BSC chain ECI board


working The board has been successfully. . . . . . . . . initialized.

fault A fault was detected on the board.. . . . . . . . . . . .


Type : DD


internal PCM states

Description : State of the internal PCM links of the BSC chain. Each link isidentified by a serial number: [0 to 15] (BSC type 1), [0 to 31](BSC types 2, 3, 4), [0 to 63] (BSC type 5.).


working The internal PCM link is working.. . . . . . . . .

fault A fault was detected on the link.. . . . . . . . . . . .


Type : DD

internal switching matrix

Description : State of the BSC chain switching unit

Value range : [working / fault)]

working The switching boards are correctly. . . . . . . . . initialized.

fault A fault was detected on a switching. . . . . . . . . . . . board.


Type : DD



interOmuEtherlinkOper V13

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 3G BSC.


Object : cn

Type : DD


intraBscDirectedRetry Class 3 I6 V9

Description : Whether intra-bss directed retry handovers are allowed in aBSS


Object : bsc


Type : DP



intraBscDirectedRetryFromCell Class 3 I7 V9

Description : Whether intra-bss directed retry handovers are allowed in acell


Object : bts


Type : DP




PE/DCL/DD/0124411–9001–124


intraCell Class 3 I8

Description : Whether intra-bts handovers on TCH are allowed in a cell forinterference reasons or Cell Tiering reasons

Value range : [cellTieringHandover/ intraCellHandover / handoverNotAllowed]

cellTieringHandover: the intra–bts handovers are allowedfor CellTiering reason

intraCellHandover: the intra–bts handovers are allowed forinterference reason

handoverNotAllowed: the intra bts handovers are notallowed



Default value : handoverNotAllowed

Type : DP


intraCellHOIntPriority Class 3 I9

Description : Index in the allocPriorityTable that defines the processingpriority of an intra-bts handover in a cell

This priority is always used, whether radio resource allocationqueueing is authorized in the BSS or not.


Default value : 17

Type : DP


intraCellQueueing Class 3 I10

Description : Whether intra-bts handover requests are queued for a cell. Thisparameter is significant only when queuing radio resourceallocation requests is allowed in the BSS.

Refer to the bscQueueingOption entry in the Dictionary.



Type : DP




intraCellSDCCH Class 3 I11 V8

Description : Whether intra-bts handovers on SDCCH are authorized in acell for interference reasons




Type : DP



PE/DCL/DD/0124411–9001–124


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 result file stores the commands that are executed and thesystem responses to those commands during the associated jobsuccessive runs, beginning with the first run.


Object : jobResult

Type : Id



L

label

Description : Label of an archive cartridge

When a label is set, all information already stored on thecartridge is lost.

Value range : [case sensitive, 64 characters max]Object : md, omc – Display label

md, omc – Set labelmd, omc – Archivemd, omc – Restoremd, omc – Display archive list

Type : DP

language

Description : Language in which a short message is broadcast

The information is used in the data coding scheme when theshort message is broadcast.

Value range : [German / English / Italian / French / Spanish / Dutch / Danish/ Portuguese / Finnish / Norwegian / Data / Multi ByteCharacter Set / unspecified]

Object : short message

Type : DP


PE/DCL/DD/0124411–9001–124


lapdConcentration

Description : Whether information concentration is authorized on a LAPDlink


Object : lapdLink

Type : DP


Checks : [C]: The attribute value can be “enabled”or “disabled”if the link carries BTS signaling on the Abisinterface in a BSS that manages BTS LAPDsignaling concentration.

[C]: The attribute value is “enabled” if the link carriesTCU signaling on the Ater interface.

[C]: The attribute value is “disabled” if the link carriesPCU signaling on the Agprs interface.





lapdLink

Description : Identifier of an lapdLink object defined with regard to a bscobject

In all MMI commands, an LAPD link can be referenced by“bscName.lapdLink” where bscName is a permanent attributeof the parent bsc object that identifies it by name.

Value range : [0 to 2147483646]

Object : lapdLink

Type : Id

Checks : [C]: The number of LAPD links per BSC is limited to841. Fourteen links can be assigned to the TCUson the Ater interface or to the PCU on the Agprsinterface, 147 links can be assigned to the radiosites on the Abis interface, and the remaininglinks can be assigned to the TRX/DRXs on theAbis interface, with two links per TRX/DRX.


[C]: The number of lapdLlink objects dependent on thesame bsc object that use the samelapdTerminalNumber is limited tomaxTeiPerLapdCh (static configuration data).

[C]: All lapdLlink objects dependent on the same bscobject that use the same lapdTerminalNumberhave identical associatedInterface andlapdConcentration attributes.



[D]: No btsSiteManager, transceiverEquipment, ortranscoder objects refer to the lapdLink object.

Remark : An lapdLink object has no administrativeState of its own; itsoperationalState depends on the administrativeState of theparent bsc object.


PE/DCL/DD/0124411–9001–124


lapdLinkCallPLoad V13

Description : Number of ‘lapdLink’ object instances used by the CallProcessing on the Ater interface. This attribute isdynamically managed by the BSS. It is set to NULL at objectcreation. Value changes are not notified to the Manager.

Value range : [0 to 65535]Object : transcoder3GEqpt

Type : DP

lapdLinkOMLRef Class 2

Description : Identifier of the lapdLink object with sapi = OML referencedby the btsSiteManager object


Type : DP

Checks : [C/M]: The referenced lapdLink object depends on thesame bsc object as the btsSiteManager object, itis assigned to the Abis interface(associatedInterface), its sapi attribute value is“OML”.

[C/M]: The number of objects dependent on a bsc objectthat refer to lapdLink objects using the samelapdTerminalNumber is limited tomaxTeiPerLapdCh (static configuration data).

[C]: The number of LAPD channels used by a site andthe related TRX/DRXs is limited tomaxLapdChPerBtsSM (static configurationdata).

[C/M]: If the lapdLink object lapdConcentrationattribute value is “enabled”, the definedlapdTerminalNumber is used by no more thanfour btsSiteManager objects dependent on thesame bsc object.

[C/M]: If the lapdLink object lapdConcentrationattribute value is “disabled”, the definedlapdTerminalNumber is not used.





Description : Identifier of the lapdLink object with sapi = OML referencedby the transceiverEquipment object

Value range : [0 to 2147483646]Object : transceiverEquipment

Type : DP

Checks : [C]: The number of LAPD channels used by a site andits related TRX/DRXs is limited tomaxLapdChPerBtsSM (static configurationdata).

[C/M]: The referenced lapdLink objects depend on thesame bsc object as the transceiverEquipmentobject, they are assigned to the Abis interface(associatedInterface), they use the samelapdTerminalNumber, their sapi attributematches the type of use (“OML” or “RSL”).

[C/M]: The number of btsSiteManager andtransceiverEquipment objects dependent on a bscobject that refer to lapdLink objects using thesame lapdTerminalNumber is limited tomaxTeiPerLapdCh (static configuration data).

[M]: The parent bsc object is unlocked, the parentbtsSiteManager object and thetransceiverEquipment object are locked.


Description : Identifier of the lapdLink object with sapi = OML referencedby the transcoder object

Value range : [0 to 2147483646]Object : transcoder

Type : DP

Checks : [C/M]: The referenced lapdLink object depends on thesame bsc object as the transcoder object, it isassigned to the Ater interface(associatedInterface = “Ater”), its sapi attributevalue is “OML”.

[M]: The application database of the parent BSC is notbuilt (bdaState = “not built”).



PE/DCL/DD/0124411–9001–124


lapdLinkRSLRef Class 2

Description : Identifier of the lapdLink object with sapi = RSL referencedby the transceiverEquipment object

Value range : [0 to 2147483646]


Type : DP

Checks : [C]: The number of LAPD channels used by a site andits related TRX/DRXs is limited tomaxLapdChPerBtsSM (static configurationdata).

[C/M]: The referenced lapdLink objects depend on thesame bsc object as the transceiverEquipmentobject, they are assigned to the Abis interface(associatedInterface), they use the samelapdTerminalNumber, their sapi attributematches the type of use (“OML” or “RSL”).

[C/M]: The number of btsSiteManager andtransceiverEquipment objects dependent on a bscobject that refer to lapdLink objects using thesame lapdTerminalNumber is limited tomaxTeiPerLapdCh (static configuration data).

[M]: The parent bsc object is unlocked, the parentbtsSiteManager object and thetransceiverEquipment object are locked.



lapdTerminalNumber Class 0 L1

Description : BSC SICD port assigned to the LAPD link

lapdTerninalNumber = 4 x number of the mother SICD4board [0 to 9] + port number [0 to 3]

lapdTerninalNumber = 8 x number of the mother SICD8board [0 to 4] + port number [0 to 7]

Value range : [0 to 7] (BSC type 1)[0 to 15] (BSC type 2)[0 to 23] (BSC type 3)[0 to 31] (BSC type 4)[0 to 39] (BSC type 5)

Note : For BSC e3 value range = [0 to inf]Object : lapdLink

Default value :


Type : DP

Checks : [C/M] : The number of SICD ports in a BSC depends onits type, knowing that a SICD board manages fourports and a SICD8V board manages 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 LAPDlink, it cannot be used for BTS and TCU signaling.

[M]: The number of btsSiteManager andtransceiverEquipment objects dependent on a bscobject that refer to lapdLink objects using thesame lapdTerminalNumber is limited tomaxTeiPerLapdCh (static configuration data).

[M]: The application database of the parent BSC is notbuilt (bdaState = “not built”).


PE/DCL/DD/0124411–9001–124


layer3MsgCyphModComp Class 1 V8

Description : Whether the “Layer 3 message” element is used in theCYPHER MODE COMPLETE messages (Phase IIcompliance)



Type : DP


Level to process

Description : Identifier of a set of SDO resultant data files. Level 1 identifiesthe latest set produced by the SDO machine.

As many as three sets of resultant data files created from thesame workstation can exist in the SDO machine. Any one canbe 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.

lightning protection Class 2 V9

Description : Presence or absence of the optional equipment “lightningarrester” in S8000 Outdoor

Value range : [Present / Absent]Object : btsSiteManager

Type : DP


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.ncorresponds to the last recorded command.

Value range : [1 to 2147483646]Object : commandFile – Run

Type : DP



locationAreaCode Class 3

Description : Code of a location area of the neighbor cell in the PLMN



Type : DP




Description : Code of a location area of the neighbor cell in the PLMN



Type : DP




Description : Code of a location area in the PLMN

A CGI (Cell Global Identifier) is unique in a location area. Itidentifies a cell in the PLMN and includes four fields:cellIdentity (CI), locationAreaCode (LAC),mobileCountryCode (MCC), and mobileNetworkCode(MNC).


Object : bts

Type : DP




PE/DCL/DD/0124411–9001–124


log

Description : Identifier of a log object defined with regard to the md object.It is assigned by the OMC–R agent.

The current alarm log is no.1. Current observations logs arecreated inascending numerical order each time a newmdScanner object is created. Current trace logs are created inascending numerical order each time a new callPathTrace ortraceControl object is created.

A restored log is created each time a Restore command on themd object related to faults, observations, or trace data is run.

Value range : [0 to 2147483646]

Object : log

Type : Id

Checks : (on observation and trace logs)

[D]: The observation or the associated trace function isstopped.

Restrictions : [D]: The log object describing the current alarm logcannot be deleted.

Notes : The log objects are created by the OMC–R agent and canbe 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 directorycapacity threshold overflow

The value “wrap” means that messages may be purged; thevalue “halt” means that further messages are not saved. Referto the capacityAlarmThreshold entry in the Dictionary.

Value range : [wrap (alarm log) / halt (observation or trace log)]


Type : DP




longTbfLossThroughput Class 3 (gprsBtsExtendedConf) V12

Description : Loss of throughput for long TBF in percentage of allocatedbandwidth. Prioritize normal transfer over long data transfer.

Value range : [0 to 100] in %

Object : bts


Type : DP

Default value : 0


longTbfSizeThreshold Class 3 (gprsBtsExtendedConf) V12

Description : Threshold for long TBF size, in Kbytes. This parameter is usedin the functionality which penalizes long TBF.


Object : bts


Type : DP

Default value : 100


lRxLevDLH Class 3 L2

Description : Signal strength threshold in BTS-to-MS direction, belowwhich a handover may be triggered



Default value : –101 to –100 dBm (GSM 900)–99 to –98 dBm (GSM1800/1900)

Type : DP



PE/DCL/DD/0124411–9001–124


lRxLevDLP Class 3 L3

Description : Signal strength threshold in BTS-to-MS direction, belowwhich the power control function increases power. It is lowerthan uRxLevDLP.



Default value : –95 to –94 dBm

Type : DP

Checks : [M]: lRxLevDLP + powerIncrStepSize ≤ uRxLevDLP

[M]: uRxLevDLP – powerRedStepSize ≥ lRxLevDLP


Note : The powerIncrStepSize, powerRedStepSize, anduRxLevDLP parameters are ignored when the BTS uses theadvanced “one shot” power control algorithm.

lRxLevULH Class 3 L4

Description : Signal strength threshold in MS-to-BTS direction, belowwhich a handover may be triggered



Default value : –101 to –100 dBm (GSM 900)–99 to –98 dBm (GSM 1800/1900)

Type : DP




lRxLevULP Class 3 L5

Description : Signal strength threshold in MS-to-BTS direction, belowwhich the power control function increases power. It is lowerthan uRxLevULP.




Type : DP

Checks : [M]: lRxLevULP + powerIncrStepSize ≤ uRxLevULP

[M]: uRxLevULP – powerRedStepSize ≥ lRxLevULP


Note : The powerIncrStepSize, powerRedStepSize, anduRxLevULP parameters are ignored when the BTS uses theadvanced “one shot” power control algorithm.

lRxQualDLH Class 3 L6

Description : Bit error rate threshold in BTS-to-MS direction, above whichan 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, morethan 12.8] %


Default value : 1.6 to 3.2 %

Type : DP

Feature : Intracell handover enhancements (TF819 – V12)



PE/DCL/DD/0124411–9001–124


lRxQualDLP Class 3 L7

Description : Bit error rate threshold in BTS-to-MS direction, above whichthe power control function increases power. It is greater thanor equal to uRxQualDLP.



Default value : 0.4 to 0.8

Type : DP

Checks : [C/M]: lRxQualDLP ≥ uRxQualDLP[M]: The parent bsc object is unlocked.

Note : The uRxQualDLP parameter is ignored when the BTS usesthe advanced “one shot” power control algorithm.

lRxQualULH Class 3 L8

Description : Bit error rate threshold in MS-to-BTS direction, above whichan inter cell handover may be triggered



Default value : 1.6 to 3.2 %

Type : DP

Feature : Intracell handover enhancements (TF819 – V12)


lRxQualULP Class 3 L9

Description : Bit error rate threshold in MS-to-BTS direction, above whichthe power control function increases power. It is greater thanor equal to uRxQualULP.




Type : DP

Checks : [C/M]: lRxQualULP ≥ uRxQualULP[M]: The parent bsc object is unlocked.

Note : The uRxQualULP parameter is ignored when the BTS usesthe advanced “one shot” power control algorithm.



lsaRcId V13

Description : Identifier of the ‘lasRc’ object class. This identifier isallocated by the MD–R at object creation, depending on theshelf and slot numbers indicated by the BSC. This attributecannot be modified. This attribute is relevant for BSC e3 andTCU e3.

Value range : [0 to 2147483646]Object : lsaRc

Type : DP

lsaRc Reference V13

Description : Pointer to the associated ‘lsaRc’ object instance.

This attribute cannot be modified. It is set at ‘iem’ creation asindicated by the BSS.

Value range : [0 to 2147483646]Object : iem



PE/DCL/DD/0124411–9001–124


M

machine name

Description : Name of the machine (terminal or server), as defined in itsprofile for a terminal, in which the job is run (default is thelogged-in user’s terminal). Enter “server” for the OMC–Rserver console.

Value range : [case sensitive]Object : job

Type : DP

Checks : [C/M]: The machine is authorized to run jobs.

machine name

Description : Name of the machine, as defined in its profile for a terminal,in which the associated job was run (“server” identifies theOMC–R server)

Object : jobResult

Type : DD

mainNetworkBand

Description : Indicates the main network band.

Value range : [900/1800] network band

maio Class 2 M1

Description : Index in the list of frequencies allotted to a radio time slotwhich obeys frequency hopping laws.

Setting this attribute, together with the fhsRef attribute, allowsthe time slot to obey frequency hopping laws.

This offset allows to differentiate channel objects thatreference frequencyHoppingSystem objects with identicalattributes (orthogonality principle).

Value range : [0 to N–1] N is the number of frequencies (≤ 64) allotted to thetime slot.

Object : channel

Type : DP

Checks : [C/M]: The attribute is in the range [0 to 63].



[C/M]: It is undefined if frequency hopping is not allowedfor the parent bts object (btsIsHopping = “nohopping”) or the channelType of the channelobject is “mainBCCH”, “mainBCCHCombined”,or “bcchSdcch4CBCH”.

[C/M]: If the attribute is defined, the fhsRef attribute isalso defined.

[C/M]: If the attribute is defined, its value is lower than thenumber of frequencies defined in themobileAllocation list (attribute of the referencedfrequencyHoppingSystem object).


managedObjectClass

Description : Object class referenced

Value range : [adjacentCellHandOver / adjacentCellReselection / bsc /bscMdInterface / bts / btsSiteManager / callPathTrace /channel / efd / frequencyHoppingSystem / handOverControl/ lapdLink / log / md / mdScanner / mdWarning / pcmCircuit/ powerControl / signallingLink / signallingLinkSet /signallingPoint / software / traceControl / transceiver /transceiverEquipment / transceiverZone / transcoder /transcoderBoard / xtp]

Object : alarmRecord,mdScanReportRecord,observationFileReadyRecord,stateChangeRecord,traceFileReadyRecord,traceLogRecord

Type : DP

managedObjectInstance

Description : Identification of an object in the class


Type : DP


PE/DCL/DD/0124411–9001–124


Manager address type

Description : OMC–R manager address type

Value range : [internal / external]Object : efd – Display

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.

Object : efd – Display

Type : DP


managerServer

Description : Name of the active OMC–R agent server. It is provided by theOMC–R agent.

This server is referred to as the “NMC” server in the Q3 namesof the permanent md observation counters related to theOMC–R agent active server.


Type : DP

manufacturerIntervention

Description : Type of action associated with an alarm criterion in themanufacturer configuration


Type : DP



marking type

Description : Type of software to consult

Selecting “prom” allows to display the software applicationsloaded in PROMs in the selected BSS entity. Selecting “soft”allows to display the software applications loaded in theprocessors of the selected BSS entity.

Value range : [prom / soft]

Object : software – Display markers

Type : DP

max log size

Description : Maximum log size expressed in bytes


Type : DP


maxAdjCHOARMPerBts

Description : Maximum number of neighbor cells associated with a servingcell for handover and reselection management (static OMC–Rconfiguration data)

Value range : [32]

Object : OMC–R

Type : DS

maxBscPerNetwork

Description : Maximum number of BSCs handled by an OMC–R (staticOMC–R configuration data)

Value range : [20]Object : OMC–R

Type : DS


PE/DCL/DD/0124411–9001–124


maxBsTransmitPowerInnerZone Class 3 (gprsBtsExtendedConf) V12

Description : Maximum level of BTS transmission power in the inner zoneof a dual–band cell


Object : bts


Default value : 2, 10

Type : DP


maxBtsPerBtsSM

Description : Maximum number of radio cells controlled by a site (staticOMC–R configuration data)

Value range : [6 (BTS “conventional”) / 4 (others)]

Object : OMC–R

Type : DS

maxBtsPerNetwork

Description : Maximum number of radio cells controlled by an OMC–R(static OMC–R configuration data)

Value range : [3200]

Object : OMC–R

Type : DS

maxDnTbfP1P2Threshold Class 3 (gprsBtsExtendedConf) V12

Description : Maximum number of downlink TBF on a P1 TDMA beforeselection of P2 TDMA


Object : bts


Default value : 16




maxDnTbfPerTs Class 3 (gprsBtsExtendedConf) V12

Description : Maximum number of downlink TBF per TDMA on a timeslotbasis


Object : bts


Type : DP

Default value : 8


maxDwAssign Class 3 (gprsBtsExtendedConf) V12

Description : Maximum number of Immediate Assignment messages persecond.

Value range : [1 to 32] blocks

Object : bts


Type : DP

Default value : 8


Because no TS partitioning is implemented in GPRS V12.4 brelease, the number of maximum TBF establishment cannotexceed the number of TS configured in the cell.Recommended value has to be set to the number of PDTCHconfigured in the cell.

maxFileSize

Description : Maximum size of the call path tracing data file in the BSC

Value range : [30 to 500] kbytes


Type : DP

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


PE/DCL/DD/0124411–9001–124


maximum acknowledgment time

Description : To select messages acknowledged at that time or before



Value range : [<date>,<time>]Object : Alarm logs – Filter

Type : DP

Checks : [A]: It is after minimum acknowledgment time whenfilled 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 alarmnumber when filled in.

maximum clear time

Description : To select alarms cleared at that time or before




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



Value range : [<date>,<time>]Object : Alarm and notification logs – Filter

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 lowerthan or equal to that one



Type : DP

Checks : [A]: It is greater than or equal to minimum MDnotification number when filled in.

maximum OMC notification number

Description : To select OMC–R manager notifications with a number lowerthan 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 OMCnotification number when filled in.

maximum reception time

Description : To select messages received at that time or before




Type : DP

Checks : [A]: It is after minimum reception time whenfilled in.

maxLapdChPerBtsSM

Description : Maximum number of LAPD channels used by a radio site(static OMC–R configuration data)


Type : DS


PE/DCL/DD/0124411–9001–124


maxNbrConsMess V13

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 modified only if the ‘bsc’ object instanceis locked.

Value range : [1 to 7]Object : bscLog

Type : DP

maxNbOfCells Class 2

Description : Maximum number of radio cells controlled by a site

Value range : [1 to maxBtsPerBtsSM]Object : btsSiteManager

Type : DP

Checks : [C/M]: The number of cells controlled by a site is limitedto maxBtsPerBtsSM (refer to this entry in theDictionary).

[M]: This number is greater than or equal to the numberof bts objects created for the btsSiteManagerobject.


maxNbrPDAAssig Class 2 (gprsTranscvLockExtendedConf) V12

Description : Maximum number of:

Polling request messsages sent on PDCH after immediateassigment message has been sent on CCCH.

PDAS messages on old TS when changing TS allocationbefore going into failure.


Default value : 5


Type : DP




maxNbrPUDWithoutVchange Class 2 (NN0002Max) gprsTranscvLockExtendedConf V12

Description : Maximum number of PUAN (Packet Uplink Ack/Nack)consecutively sent without V(A) has changed (respectively,maximum number of PDAN (Packet Downlink Ack/Nack)consecutively sent without V(Q) has changed).


Default value : 10


Type : DP


maxNbrRLCEmptyBlock Class 2 (N3101Max)(gprsTranscvLockExtendedConf) V12

Description : Maximum number of USF where no data is received in the ULdirection


Default value : 10


Type : DP


maxNumberRetransmission Class 3 M2

Description : Maximum number of RACH burst retransmissions allowed ina call in case of non–system response

The information is broadcast to the mobiles at regular intervalson the cell BCCH. It defines the maximum number of times amobile can renew access requests to the BTS on RACH.

Value range : [one / two / four / seven]Object : bts

Default value : two

Type : DP



PE/DCL/DD/0124411–9001–124


maxPcmCPerBtsSM

Description : Maximum number of PCM links used by a radio site on theAbis 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 transcoderon the A interface (static OMC–R configuration data)

Value range : [4]

Object : OMC–R

Type : DS

maxRACH Class 3 V12

Description : Maximum number of RACH messages accepted by the PCUper second

Value range : [0 to 15] blocks

Range to be considered at the MMI is [0 to 15], which meansfor the PCU from 1 to 16 RACH per second.

Object : bts

Default value : 0


Type : DP


maxRowCount

Description : Maximum number of information lines per table to access. “0”means accessing all data. The default value is “1000”.


Object : Trace data display

Type : DP



maxSigLPerSigLS

Description : Maximum number of SS7 channels linked to a BSC (staticOMC–R configuration data)

Value range : [2 (BSC 6000 types 1, 2) 4 (BSC 6000 types 3, 4, 5) 2 (BSC 12000 type 1) 4 (BSC 12000 types 2, 3, 4) 6 (BSC 12000 type 5)]

Object : OMC–R

Type : DS

maxTeiPerLapdCh

Description : Maximum number of TEI addresses allotted to a LAPDterminal (static OMC–R configuration data)

It defines the maximum number of LAPD links that can use thesame SICD port in the BSC (lapdTerminalNumber attributeof the lapdLink objects).


Type : DS

maxTranscdBPerTranscd

Description : Maximum number of transcoding boards housed in a remotetranscoder (static OMC–R configuration data)

Value range : [10 in a GSM 900, E–GSM, GSM–R or 1800 network8 in a GSM 1900 network]

Object : OMC–R

Type : DS

maxTranscdPerBsc

Description : Maximum number of remote transcoders linked to a BSC(static OMC–R configuration data)

Value range : [7 (BSC 6000) / 12 (BSC 12000) for E1 PCMs 9 (BSC 6000 / 14 (BSC 12000) for T1 PCMs]

Object : OMC–R

Type : DS


PE/DCL/DD/0124411–9001–124


maxUpTbfP1P2Threshold Class 3 (gprsBtsExtendedConf) V12

Description : Maximum number of uplink TBF on a P1 TDMA beforeselection of P2 TDMA



Type : DP

Default value : 16


maxUpTbfPerTs Class 3 (gprsBtsExtendedConf) V12

Description : Maximum number of uplink TBF per TDMA on a timeslotbasis



Type : DP

Default value : 8


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 thesystem 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 isallowed

The value of this attribute is “not archived” whenmdScannerType = “performance monitor” (instrument panelobservation) and “archived” otherwise.

Value range : [archived / not archived]

Object : mdScanner

Type : DP


mdConfirm

Description : Whether the observation messages processed should beacknowledged

The value of this attribute is “not confirmed” whenmdScannerType = “performance monitor” (instrument panelobservation) 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.

mdFileName

Description : Name of an observation file containing an elementary report.Refer to the naming rules to NTP < 07 >.

Object : mdScanReportRecord

Type : DP


PE/DCL/DD/0124411–9001–124


mdGranularityPeriod

Description : Recovery period of the observation messages by the OMC–Ragent

Value range :[5, 10, 15] minutes permanent general md. . . . . . .

[15, 30, 60] minutes permanent general bsc (BSC). . . . . .

[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 atthe same time with a 5–minute recovery period inthe BSSs managed on the OMC–R is limitedto 50.

[C/M]: The number of instrument panel observationsrunning at the same time with a 1–minute recoveryperiod is limited to 10.

Restrictions : [M]: This attribute cannot be modified ifmdScannerType = “temporary xxx”. Stop theobservation if necessary by deleting the concernedmdScanner object and create it back with a newobservation period.

mdGranularityPeriod


Value range :[5, 10, 15] minutes permanent general md. . . . . . .

[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) orReal Time Observation(ORT))

[5, 10, 15, 30, 60] minutes Temporary Observation. (TO)

Object : mdScanReportRecord

Type : DP

mdGranularityPeriod


Value range :

[5, 10, 15] minutes permanent general md. . . . . . .

[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) orReal Time Observation(ORT))

[5, 10, 15, 30, 60] minutes Temporary Observation. (TO)

Object : observationFileReadyRecord

Type : DP


PE/DCL/DD/0124411–9001–124


mdId

Description : Identifier of the md object that describes the OMC–R agent.It is enforced by the system.

This attribute allows users to identify the md object on theOMC–R.

Value range : [1]Object : md – Display

Type : DP

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

mdLog

Description : Whether the observation messages processed are saved on theOMC–R agent disks

The value of this attribute is “not logged” whenmdScannerType = “performance monitor” (instrument panelobservation) and “logged” otherwise.

Value range : [logged / not logged]

Object : mdScanner

Type : DP


mdObjectList

Description : Identification of the observed object. It depends on the type ofthe defined observation.

mdScannerType mdObjectList

permanent general md md

permanent general bsc bsc

general statistic (OGS) bsc

fast statistic (OFS) bsc

performance monitor (IPO) bsc

real time (ORT) bsc

temporary interference* bsc & btsSiteManager& bts

temporary signallingLink* bsc & signallingLink



mdScannerType mdObjectList

temporary pcmCircuit* bsc & pcmCircuit

temporary handOver* bsc & btsSiteManager& bts

temporary Abis Interface bts* bsc & btsSiteManager& bts

diagnostic (ODIAG) bsc, bts, signallingLink,transcoder3G,transcoderEqpt,pcmPort,transceiverEqpt &btsSiteManager

* This type only applies to V12 bsc’sObject : mdScanner

Type : DP


mdObjectList


Object : Display xxx report

Type : DP

mdObjectList



Type : DP

��

Description : Identifier of an mdScanner object defined with regard to themd object

The mdScanner object class describes the OMC–R agent andBSS observations. These objects are managed by the OMC–R“Performance Management” function.

Value range : [0 to 2147483646]Object : mdScanner

Type : Id


PE/DCL/DD/0124411–9001–124


Checks : (performed only when the object describes a BSSobservation)

[C/M/D]: The application database of the BSC is not beingbuilt.

[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, theBSS/OMC–R link is established and no audit isin-progress in the BSC.

Remark : Deleting an mdScanner object that describes a temporaryobservation is always possible if the observation duration haselapsed (stopTime = 0) and the stop TGE has been sent to theBSC.

mdScannerType

Description : Type of the observation

Value range : [general Statistic (V11+) / fast Statistic (V11+) / real Time(V11+) / diagnostic (V11+) / permanent general bsc (V10) /permanent general md / permanent general manager /performance monitor (IPO V10) / temporary interference /temporary signallingLink / temporary pcmCircuit (V10) /temporary handOver (V10) / temporary pair of bts (V8) /temporary Abis Interface bts]


Type : DP

mdScannerType


Value range : [general Statistic (V11+) / fast Statistic (V11+) / real Time(V11+) / diagnostic (V11+) / permanent general bsc (V10) /permanent general md / permanent general manager /temporary interference / temporary signallingLink /temporary pcmCircuit (V10) / temporary handOver (V10) /temporary pair of bts (V8) / temporary Abis Interface bts]


Type : DP



mdScannerType


Value range : [general Statistic (V11+) / fast Statistic (V11+) / real Time(V11+) / permanent general bsc / permanent general md /permanent general manager / performance monitor(instrument panel) (V10)]

Object : Load formulae

Type : DP

mdScannerType


Value range : [general Statistic (V11+) / fast Statistic (V11+) / real Time(V11+) / diagnostic (V11+) / permanent general md /permanent general manager / temporary interference /temporary signallingLink / temporary pair of bts (V8) /temporary Abis Interface bts]

Object : mdScanner

Type : DP

Checks : [C]: The defined observation is not running.


Notes : The permanent general md observation is unique to theOMC–R.

The permanent general bsc and Instrument Panelobservations 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.


PE/DCL/DD/0124411–9001–124


mdStorageDuration

Description : Storage duration of the observation messages processed on theOMC–R agent disks

Observation messages are kept on the OMC–R agent disks fora limited period of time, provided the mdLog attribute of theassociated log object is “logged”. They are automaticallypurged at regular intervals. The user will have to archive theobservation data, should data analysis occur after the purgetime set by static configuration.

Value range : [N] hour. N is a static configuration data.

Since instrument panel observation messages are not kept,N equals zero for the log objects that describe theseobservations.

Object : mdScanner

Type : DP


mdTransferMode

Description : Service used by the OMC–R agent to transmit the observationmessages processed to the OMC–R manager

Value range : [FTAM (permanent general md and bsc observations) / CMIS(others)]


Type : DP


mdWarning

Description : Identifier of a mdWarning object defined with regard to the mdobject

The mdWarning object class describes the processingconditions of BSS alarms of “outOfRangeCounter” and“excessiveAnomalyRate” type. These objects are managed bythe OMC–R “Fault Management” function.

Value range : [0 to 2147483646]Object : mdWarning

Type : Id



measurementProcAlgorithm Class 2 V12

Description : Whether the new L1M interface is used

Value range : [L1MV1, L1MV2]

L1MV1: the older L1M is used

L1MV2: the newer L1M is usedObject : bts

Default value : L1MV1

Feature : L1M evolutions for advanced features support (TF1089–V12)

Type : DP

Checks : [M] : The parent bsc object is unlocked and the btsobject is locked.

mergeEft

Description : Whether the EFT should be merged in an existing EFT

The attribute value can only be “True” if the EFT contains asite BCF software.

If the EFT exists on the OMC–R agent disks, the followingapply:

If mergeEFT = “True”, the EFT is updated with the newDLU files.

If mergeEFT = “False”, the command is refused.

Value range : [true / false]Object : md – Create EFT

Type : DP

mergeEft






Value range : [true / false]Object : md – Validate EFT

Type : DP


PE/DCL/DD/0124411–9001–124


mergeEft






Value range : [true / false]Object : omc – Download and validate EFT from gigatape to md

Type : DP

microCellCaptureTimer Class 3 M3 V8

Description : Time used to confirm a capture (signal strength stability) whenusing microcell Algorithm type A

Value range : [0 to 255] multiple of <runHandOver>Object : adjacentCellHandOver

Default value : 0

Condition : To define if A handover algorithm is activated

Type : DP

Checks : [C]: This attribute is defined if the described neighborcell is a microcell (cellType = “microType”).


microCellStability Class 3 M4

Description : Strength Level Stability Criterion for Capture Algorithm A

Value range : [0 to 255] dBObject : adjacentCellHandOver

Default value : 10

Condition : To define if A handover algorithm is activated

Type : DP

Checks : [C]: This attribute is defined if the described neighborcell is a microcell (cellType = “microType”).




minimum acknowledgment time

Description : To select messages acknowledged at that time or after



Value range : [<date>,<time>]Object : Alarm logs – Filter

Type : DP

Checks : [A]: It is before maximum acknowledgment timewhen 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 alarmnumber when filled in.

minimum clear time

Description : To select alarms cleared at that time or after




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




Type : DP

Checks : [A]: It is before maximum event time when filled in.


PE/DCL/DD/0124411–9001–124


minimum MD notification number

Description : To select OMC–R agent notifications with a number greaterthan or equal to that one



Type : DP

Checks : [A]: It is lower than or equal to maximum MDnotification number when filled in.

minimum OMC notification number

Description : To select OMC–R manager notifications with a numbergreater than or equal to that one


Value range : [0 to 2147483646]


Type : DP

Checks : [A]: It is lower than or equal to maximum OMCnotification number when filled in.

minimum reception time

Description : To select messages received at that time or after




Type : DP

Checks : [A]: It is before maximum reception time whenfilled in.



minNbOfTDMA Class 2 M5

Description : Minimum number of TDMA frames that must be working inorder for the cell itself to be working.

The frame carrying the cell BCCH must be among them andis successfully configured.


Default value : 1

Type : DP

Checks : [M]: This number is less than or equal to the number oftransceiver objects (TDMA frames) created forthe bts object.

[M]: The parent bsc objet is unlocked and the bts objectis locked.

minNbrGprsTs Class 3 (gprsBtsExtendedConf) V12

Description : Minimum number of TS dedicated to GPRS in the cell



Type : DP

Default value : 0


missDistWt Class 3 M6

Description : Weight applied to missing Distance measurement

The missing measurement is replaced by the latest receivedraw measurement weighed by this corrective factor whencalculating the average MS-BTS distance.

The range of permitted values makes missing distancemeasurements not favored.


Default value : 110

Type : DP

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


PE/DCL/DD/0124411–9001–124


missRxLevWt Class 3 M7

Description : Weight applied in case of missing signal strengthmeasurement report

The missing measurement is replaced by the latest computedarithmetic average, or by the latest received raw measurementif no average value is available, weighed by this correctivefactor when calculating the average signal strength in the cell.

Selecting the greatest value makes missing strengthmeasurements not favored.


Default value : 90

Type : DP


missRxQualWt Class 3 M8

Description : Weight applied to missing Quality measurement

The missing measurement is replaced by the latest computedarithmetic average, or by the latest received raw measurementif no average value is available, weighed by this correctivefactor when calculating the average bit error rate in the radiolink.

The range of permitted values makes missing qualitymeasurements not favored.


Default value : 110

Type : DP


mmsId V13

Description : Identifier of the ‘mms’ object class. This identifier is allocatedby the MD–R at object creation, depending on the shelf andslot numbers indicated by the BSC. This attribute cannot bemodified. This attribute is relevant for BSC e3 and TCU e3.

Value range : [0 to 2147483646]Object : mms

Type : DP



mmsUsage V13

Description : Indicates whether the MMS is private (i.e. associated to anOMU) ; or shared–mirrored (associated to the Control Node)

This attribute cannot be modified. It is set by the MD–R atMMS creation.

Value range : [0 (Shared) to 1 (Private)]Object : mms

Type : DP


mobileAllocation Class 2 M9

Description : List of up to sixty-four frequencies allotted in the networkfrequency band to a radio time slot which obeys frequencyhopping laws


Object : frequencyHoppingSystem

Type : DP

Checks : [C/M]: Each frequency occurs once in the list and isallotted to the parent bts object (cellAllocation).

[M]: If the frequencyHoppingSystem object isreferenced by a channel object dependent on theassociated bts object, the parent bsc object isunlocked and the associated bts object is locked.

mobileCountryCode Class 3

Description : Code of the PLMN home country

Refer to the next entry.

Value range : [0 to 999]Object : adjacentCellHandOver

Type : DP

Checks : [C]: This code is identical to the mobileCountryCodeattribute of the parent bsc object when it is definedfor that object.

[C/M]: A CGI is unique in the set including a serving celland its neigbor cells.



PE/DCL/DD/0124411–9001–124







Type : DP





Description : Code of the PLMN home country. It must be defined when theMSC does not manage cell global identifiers (CGI).



Condition : To define when MSC does not manage cell global identifiers(CGI).

Type : DP






A CGI (Cell Global Identifier) is unique within a location area.It identifies a cell unambiguously in the PLMN and includesfour fields: cellIdentityCode (CI), locationAreaCode(LAC), mobileCountryCode (MCC), andmobileNetworkCode (MNC).


Object : bts

Type : DP




mobileNetworkCode Class 3

Description : Code of the PLMN in the country



Type : DP

Checks : [C]: This code is identical to the mobileNetworkCodeattribute of the parent bsc object when it is definedfor that object.




PE/DCL/DD/0124411–9001–124







Type : DP





Description : Code of the PLMN in the country. It must be defined when theMSC does not manage cell global identifiers (CGI).



Object : bsc

Type : DP




A CGI (Cell Global Identifier) is unique within a location area.It identifies a cell unambiguously in the PLMN and includesfour fields: cellIdentityCode (CI), locationAreaCode(LAC), mobileCountryCode (MCC), andmobileNetworkCode (MNC).


Object : bts

Type : DP





[M]: The parent bsc object is unlocked and bts object islocked.

modeModifyMandatory Class 3 M10 V9

Description : Whether a CHANNEL MODE MODIFY message should besent to the mobile after a directed retry handover in the BSS

Value range : [used (yes) / not used (no)]

Object : bsc

Default value : not used

Type : DP

Checks : [C/M]: The attribute value can only be “used” if directedretry handovers are allowed at BSC level. Referto the interBscDirectedRetry andintraBscDirectedRetry entries in theDictionary.

[M]: The bsc object is unlocked.

monitoredObjectClass

Description : Class of the serving object for the notifications processed

Value range : [adjacentCellHandOver / adjacentCellReselection / bsc / bts /btsSiteManager / channel / frequencyHoppingSystem /handOverControl / lapdLink / pcmCircuit / pcu / pcusn /powerControl / signallingLink / signallingLinkSet /signallingPoint / software / transceiver /transceiverEquipment / transceiverZone / transcoder /transcoderBoard / xtp]

Object : mdWarning

Type : DP


PE/DCL/DD/0124411–9001–124


monitoredObjectInstance

Description : Identification of a serving object in the class

They identify the object that issued the processednotifications. Enter the concerned object identificationsequence.

Object : mdWarning

Type : DP

monitoredSpecificProblemsList

Description : List of the specific problems taken into account in the process

This parameter allows to filter the processed notificationsaccording to the following criteria: cause number, faultnumber, and processor number.

Value range : [(cause, faultNumber) pair]

Object : mdWarning if detectionFunction = “excessiveAnomalyRate”

Type : DP

month

Description : Month on which the observation report was created



Object : Display busiest day of the month report

Type : DP

msBtsDistanceInterCell Class 3 M11

Description : Whether inter-bts handovers are allowed in a cell for distancereasons




Type : DP




msCapWeightActive Class 2 (gprsBtsLockExtendedConf) V12

Description : It specifies whether the Weight Fair Allocation algorithm isused or not

Value range : [yes / no]

Object : bts


Default value : yes

Type : DP


msRangeMax Class 3 M12

Description : Maximum MS-to-BTS distance beyond which a handovermay be triggered. It can be set to 1 for a microcell and is lessthan callClearing in all cases.

If the associated serving cell is a concentric cell, the followinginequality, that is not checked by the system, must be true(refer to this entry in the Dictionary):

msRangeMax ≥ concentAlgoExtMsRange



Default value : 34 in non–extended mode, 89 in extended mode

Type : DP

Checks : [C/M]: msRangeMax < callClearing (associated btsobject attribute)

[C/M]: The maximum distance is limited to 34 km if theextended cell attribute of the associated bts objectis “false”.




PE/DCL/DD/0124411–9001–124


msTxPwrMax Class 3 M13

Description : Maximum MS transmission power in a serving cell. It is equalto msTxPwrMaxCCH in a GSM 900 network.

Value range : [5 to 43, by steps of 2] dBm (GSM 900, GSM–R, E–GSM, andGSM 900 – GSM 1800 networks)[0 to 36, by steps of 2] dBm (GSM 1800, andGSM 1800 – GSM 900 networks)[0 to 33] dBm (GSM 1900 network)

Object : bts

Default value : Typical value of 33 dBm for GSM 900 handhelds and 30 dBmfor GSM 1800 and 1900 handhelds

Type : DP

Checks : [C/M]: GSM 900 networks: msTxPwrMax =msTxPwrMaxCCH


Note : The msTxPwrMax values [displayed by the OMC–R] /[typed by the OMC–R operator] are encoded values. Thecorresponding maximum MS transmission powers in a servingcell are compliant to GSM Rec 05.05, that is to say:

[5 to 39] dBm (GSM 900 network)

msTxPwrMax2ndBand Class 2 M14 V12

Description : Maximum MS transmission power in the band 1 of thedualband cell depending on the network type (BCCH is onlydefined in band 0)

Value range : [0 to 36, by steps of 2] dBm (GSM 900 – GSM 1800 network)[5 to 43, by steps of 2] dBm (GSM 1800 – GSM 900 network)

Object : bts

Default value : Typical value of 33 dBm for GSM 900 handhelds, 30 dBm forGSM 1800 and 1900

Type : DP




Checks : [C/M]: The attribute value is within the range [0 to 36] andeven when the bts object standardIndicatorattribute is “gsmdcs”.

[C/M]: The attribute value is within the range [5 to 43] andodd when the bts object standardIndicatorattribute is “dcsgsm”.





msTxPwrMaxCCH Class 3M15

Description : Maximum MS transmission power in a cell CCCH

The BSC relays the information to the mobiles in the AbisCELL MODIFY REQUEST message.

Value range : [5 to 43, by steps of 2] dBm (GSM 900, GSM–R, E–GSM, andGSM 900 – GSM 1800 networks)[0 to 36, by steps of 2] dBm (GSM 1800 andGSM 1800 – GSM 900 networks) [0 to 33] dBm (GSM 1900 network)

Object : bts

Default value : Typical value of 33 dBm for GSM 900 handhelds, 30 dBm forGSM 1800 and 1900

Type : DP


Remark : If the cell is used as a neighbor cell of another serving cell inthe network, msTxPwrMaxCCH must be identical to themsTxPwrMaxCell power defined for the correspondingadjacentCellHandOver object (the values must be checked byusers).




PE/DCL/DD/0124411–9001–124


msTxPwrMaxCell Class 3 M16

Description : Maximum MS transmission power in a neighbor cell. It isequal to msTxPwrMaxCCH when the cell is declared as aserving cell on the network (the value must be checked byusers).

Value range : [5 to 43, by steps of 2] dBm (GSM 900, GSM–R, E–GSM, andGSM 900 – GSM 1800 networks)[0 to 36, by steps of 2] dBm (GSM 1800 networkand GSM 1800 – GSM 900) [0 to 33] dBm (GSM 1900 network)


Default value : Typical value of 33 dBm for GSM 900 handhelds and 30 dBmfor GSM 1800 and 1900 handhelds

Type : DP


Remark : If the cell is used as a neighbor cell of another serving cell inthe network, msTxPwrMaxCell should be identical to themsTxPwrMaxCCH power defined for the correspondingadjacentCellHandOver object (the values must be checked byusers).






multi band reporting Class 3 M17 V10

Description : Minimum number of cells that multiband MSs must report intheir radio measurements in each frequency band

Value range : [the six strongest cells / the strongest cell out band / the twostrongest cells out band / the three strongest cells out band]

six strongest allowed cells irrespective of their frequencyband

the strongest allowed cell outside the current frequencyband

the two strongest allowed cells outside the currentfrequency band

the three strongest allowed cells outside the currentfrequency band

Object : bts

Default value : the six strongest cells

Type : DP


multiple site V8

Description : Identifier of a multiple site object defined with regard to a bscobject



Type : Id

Checks : [C]: The multiple site object is not created for theparent bsc object.

[C/M]: The btsSiteManager objects in thebtsSiteManagerList list are created for the parentbsc object and are not referenced by anothermultiple site object.

[M/D]: The multiple site object is created and the currentbtsSiteManager objects referenced in thebtsSiteManagerList list are locked.


PE/DCL/DD/0124411–9001–124


multipleVocoders Class 1 V8

Description : Whether the BSC can be linked to one or other MSC that usedifferent speech coding protocols

An MSC uses either the GSM protocol or the JTC protocol.“False” means that only the GSM protocol is compatible.

Value range : [true / false]Object : bsc


Type : DP


muxNumber Class 3 V12

Description : pcuSN mux identification

Value range : [noMux / oneMux / twoMux]

Object : pcusn


Type : DP



N

N3103 Class 3 (gprsBtsExtendedConf) V12

Description : Maximum number of repetition of a PUAN (Packet UplinkAck/Nack) message


Default value : 5


Type : DP


N3105max Class 2 (gprsTranscvLockBtsExtendedConf) V12

Description : Maximum number of consecutive RLC data blocks sent by thePCU with a valid RRBP and not having been acknowledgedby the MS


Default value : 4


Type : DP


nAvgl Class 3 (gprsAvgParam) V12

Description : Signal strength filter used for MS output power control

It specifies the “Interference signal strength filter” constant forpower control. NAVG –I = 2 (k/2) with k = nAvgI.


Default value : 0


Type : DP



PE/DCL/DD/0124411–9001–124


nAvgT Class 3 (gprsAvgParam) V12

Description : Signal strength filter used for MS output power control, whichspecifies the “Signal strength filter period” for power controlin packet transfer mode. TAVG –T = 2 (k/2) /6 with k = nAvgT.



Type : DP


nAvgW Class 3 (gprsAvgParam) V12

Description : Signal strength filter used for MS output power control, whichspecifies the “Signal strength filter period” for power controlin packet idle mode. TAVG –W = 2 (k/2) /6 with k = nAvgW.



Type : DP


Note : Tavg_w has no impact on frequency measurements andcomputations done by the MS, which is always equal to thefrequency of paging blocks decoding.

nbOfRepeat Class 2 N1 V8

Description : Maximum number of times that paging messages are repeatedto mobiles that belong to the same paging sub–group

It is set to “3” in former BSS versions (static configurationparameter).


retransDuration ≥ (delayBetweenRetrans + 1) x nbOfRepeat


Default value : 3

Type : DP




nbrFreeTchBeforeAnticipation Class 3 (gprsBtsExtendedConf) V12


Value range : [0]Object : bts

Default value : 0


Type : DP


nbrFreeTchToEndAnticipation Class 3 (gprsBtsExtendedConf) V12


Value range : [0]

Object : bts

Default value : 0


Type : DP


nbrTch Class 2 (gprsPcuCrossConnectList) V12

Description : Number of TSs used for each Agprs PCM link


Object : pcu

Default value : 0


Type : DP

Checks : [M]: The parent bsc object is unlocked and the pcuobject is locked.



PE/DCL/DD/0124411–9001–124


NCHPosition Class2 N2 V12

Description : Defines the number of blocks and position of the first block forNCH

Value range : [0 block1 block, first block 01 block, first block 11 block, first block 21 block, first block 31 block, first block 41 block, first block 51 block, first block 62 blocks, first block 02 blocks, first block 12 blocks, first block 22 blocks, first block 32 blocks, first block 42 blocks, first block 53 blocks, first block 03 blocks, first block 13 blocks, first block 23 blocks, first block 33 blocks, first block 44 blocks, first block 04 blocks, first block 14 blocks, first block 24 blocks, first block 35 blocks, first block 05 blocks, first block 15 blocks, first block 26 blocks, first block 06 blocks, first block 17 blocks, first block 0]

Object : bts

Default value : 0 block

Type : DP

Feature : (GSM–R V12)

Checks : [M] : The parent bsc object is unlocked and the btsobject is locked.

Note : NCHPosition – noOfBlocksForAccessGrant relationaccording to channelType attribute



channelType NCHPosition noOfBlocksForAccessGrant

mainBCCH 1 block, first block 0 to 62 blocks, first block 0 to 53 blocks, first block 0 to 44 blocks, first block 0 to 35 blocks, first block 0 to 26 blocks, first block 0 to 17 blocks, first block 0

>1>2>3>4>5>6= 7

mainBCCHCombined 1 block, first block 02 blocks, first block 0

1 < value ≤ 2= 2

network protocolUsed V13

Description : Indicates which protocol is used (X.25 or IP). This attributeis modified by the Manager. Value changes are notified to theManager. This attribute can be modified only if the‘bscMdInterface’ object instance is locked.

Value range : [X25 / IP]Object : bscMdInterface

Type : DP

networkColourCode Class 3

Description : Color code of the mobile network. The (BCC,NCC) pair formsthe cell BSIC.



Type : DP




PE/DCL/DD/0124411–9001–124


networkColourCode Class 2

Description : Color code of the mobile network. It allows countries withcommon borders to allocate BCCs and BCCH frequencies attheir own convenience in international border areas. The(BCC,NCC) pair forms the cell BSIC.

The information is broadcast on the cell SCH.

The Base Station Identity Code (BSIC) is a six-bit code: bits6–5–4 = NCC (PLMN color code), bits 3–2–1 = BCC (Basestation color code). Outside border areas, the NCC bits can beused to increase the number of BCC possibilities.


Object : bts

Type : DP



Remark : The NCC should not be confused with the MCC (MobileCountry Code) nor the MNC (Mobile Network Code), whichare part of the CGI (Cell Global Identifier).

networkIndicator Class 1

Description : Identifier of the SS7 network

Value range : [nationalUse/internationalUse]


Type : DP

Checks : [C/M]: The only value accepted by the system is“nationalUse”.


Remark : Since the system accepts only one value for this attribute,changing it has no meaning. To change its value, consultNTP < 34 >.



networkIndicator Class 1

Description : Identifier of the SS7 network

Value range : [nationalUse]Object : signallingPoint

Type : DP

Checks : [C/M]: The only value accepted by the system is“nationalUse”.


Remark : Since the system accepts only one value for this attribute,changing it has no meaning. To change its value, consultNTP < 34 >.


new name

Description : New name to give to the short message. It is different from thecurrent short message identifier.

Value range : [case sensitive, 20 characters max]Object : short message – Rename

Type : DP

Checks : [A]: It is different from the current short messageidentifier.

[A]: It does not exist on the OMC–R.

new password 1st try

Description : User’s new password to use in the next login request. It beginswith a letter, contains at least one non–alphabetical characteramong the first eight characters, and is case sensitive. It is notdisplayed.

Value range : [6 characters min]Object : user profile – Change password

Type : DP

Checks : [A]: It begins with a letter and contains onenon–alphanumerical character among the firsteight characters.

[A]: It is at least six-character long.

[A]: It is different from the N previous occurrences (Nis set in static configuration data).


PE/DCL/DD/0124411–9001–124


new password 2nd try

Description : Second definition of the user’s new password that will not bevalidated 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


Object : user profile – Change password

Type : DP

Checks : [A]: It begins with a letter and contains onenon–alphanumerical character among the firsteight 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 N3 V9

Description : Algorithm used by the BTS to control power in a cell

The “step by step” value refers to the standard power controlalgorithm.

The “one shot” value refers to the advanced power controlalgorithm.

The “enhanced one shot “ value refers to the advanced poweralgorithm used in connection with the handOverControlobject rxLevHreqaveBeg attribute used in the early handovermechanism.

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


Note : The “enhanced one shot” attribute value can only apply to nonmixed DCU4 or DRX transceiver architecture.



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 jobrun periodicity is defined.

Type : DD

night intervention

Description : Type of action associated with an alarm criterion in thenighttime configuration

Value range : [noAlarm / critical / major / minor]


Type : DP

noOfBlocksForAccessGrant Class 2 N4

Description : Number of CCCH blocks not used for paging

A BCCH is combined when it shares the same radio time slotwith four SDCCHs which can include a CBCH (refer to thechannelType entry in the Dictionary). In that case, theattribute value is no greater than to 2 (the value must bechecked by users).

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 immediateassignment messages as and when needed.

Object : bts

Default value : 0

Type : DP

Checks : [M]: This number is greater than zero if thechannelType of one of the channel objectsdependent on the bts object is “sdcch8CBCH”(refer to this entry in the Dictionary).



PE/DCL/DD/0124411–9001–124


noOfMultiframesBetweenPaging Class 2 N5

Description : Number of occurences of a paging sub-group

The greater this number, the greater the number of pagingsub-groups.

Value range : [2 to 9] multi-frame of fifty-one framesObject : bts

Default value : 6

Type : DP


notAllowedAccessClasses Class 3 N6

Description : List of mobile access classes that are forbidden in the cell,except case of congestion.

This attribute, together with the emergencyCallRestrictedattribute, allows to control access to a cell according to theservice classes authorized.

Value range : List of mobile access class:

[0 to 9]: user classes

[11 to 15]: operator classesObject : bts

Default value : Leave the field empty

Type : DP


Remark : General conditions mobiles are granted access to a cell areallotted at subscription time.

notification number

Description : Reference number of the associated notification

Value range : [0 to 2147483646]Object : alarmRecord,

mdScanReportRecord,observationFileReadyRecord,stateChangeRecord,traceFileReadyRecord,traceLogRecord

Type : DP



notification type

Description : To select messages according to the type of the notifications


Value range : [attributeValueChange / communicationsAlarm /environmentalAlarm / equipmentAlarm / objectCreation /objectDeletion / processingErrorAlarm /qualityOfServiceAlarm / stateChange / specific]


Type : DP

number of records

Description : Number of records


Type : DP


numberOfEnabledHDLCPorts V13

Description : Number of ‘enabled’ HDLC ports in the TMU or IEM module.

Operational State of the HDLC channels in the TMU/IEMmodules.

Operational State of the HDLC channels in the TMU/LSAmodules. The global Operational State of the HDLC feature isgiven by the number of ports/channels with an individualoperational state set to ‘enabled’.

This attribute is dynamically managed by the BSS. It is set toNULL at ‘iem’ or ‘tmu’ object instance creation. Valuechanges are not notified to the Manager.

This attribute is relevant for BSC e3.


Object : iem, tmu

Type : DD



PE/DCL/DD/0124411–9001–124


numberOfPwciSamples Class 3 V12

Description : Minimum number of PwCI samples required to reach areliable distribution (representative of the real distribution inthe whole cell) * 1000



Default value : 20


Type : DP


numberOfSlotsSpreadTrans Class 3 N7

Description : Number of radio time slots over which RACH transmissionaccess are spread in a random way to avoid collisions


In the event of non–system response, the mobile will renew theRACH bursts after a randomly defined period that varies withnumberOfSlotsSpreadTrans.

MS Phase 1

Fixed Delay

1st access 2nd access

Time0250 or 350 ms

Variable delay from 0 to(numberOfSlotsSpreadTrans –1) slots

The time T between two transmissions of the same RACHburst is the following:

T= [D + (N+1) x 4.615]ms where

D is the maximum system response pending time:

N is the randomly number generated by the mobile in the



range [0 to numberOfSlotsSpreadTrans–1]

4.615 ms is the time occupied by a time slot.

MS Phase 2

Fixed Delay

1st access 2nd access

Time0S TS RACH

Variable delay from 0 to(numberOfSlotsSpreadTrans –1) slots

The time T between two transmissions of the same RACHburst is the following (whichever is the BCCH, combined ornot):

T= 4.615 x [S+(N + 1)] ms where

S is a parameter depending on the BCCH configuration andon the value of numberOfSlotsSpreadTrans (see tablehereafter)

N is the randomly number generated by the mobile in therange [0 to numberOfSlotsSpreadTrans–1]

4.615 ms is the time occupied by a time slot.

NumberOfSlotsSpreadTransS on not

combinedBCCH

S oncombined

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 slotsObject : bts

Default value : 32

Type : DP



PE/DCL/DD/0124411–9001–124


Note : The choice will depend on the quantities of GSM phase 1 andGSM phase 2 mobiles.

For Mobile phase 1, numberOfSlotsSpreadTrans = 50 leadsto 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 doubleallocation rate.

Therefore, for a network that handles a combination of bothtypes of mobiles, numberOfSlotsSpreadTrans should be setto 32 (default value).

numberOfTCHFreeBeforeCongestion Class 3 N8 V9

Description : Minimum number of free TCHs which triggers the beginningof the TCH congestion phase and the beginning of the trafficoverload condition (this parameter takes also into account thepreempted PDTCH)

Value range : [0 to infinite]Object : bts

Default value : 0

Type : DP


[C/M]: numberOfTCHFreeBeforeCongestion ≤numberOfTCHFreeToEndCongestion

numberOfTCHFreeToEndCongestion Class 3 N9 V9

Description : Threshold that gives the number of free TCHs, which triggersthe end of TCH congestion phase and the end of the trafficoverload condition (this parameter takes also into account thepreempted PDTCH)


Default value : 0

Type : DP


[C/M]: numberOfTCHFreeToEndCongestion ≥numberOfTCHFreeBeforeCongestion



numberOfTCHQueuedBeforeCongestion Class 3 N10 V9

Description : Maximum number of TCH allocation requests queued whichtriggers the beginning of the TCH congestion phase and thebeginning of the traffic overload condition

Value range : [0 to infinite]

Object : bts

Default value : 0

Type : DP


[C/M]: numberOfTCHQueuedBeforeCongestion ≥numberOfTCHQueuedToEndCongestion

numberOfTCHQueuedToEndCongestion Class 3 N11 V9

Description : Maximum number of TCH allocation requests queued whichtriggers the end of TCH congestion phase and the end of thetraffic overload condition


Default value : 0

Type : DP


[C/M]: numberOfTCHQueuedToEndCongestion ≤numberOfTCHQueuedBeforeCongestion


PE/DCL/DD/0124411–9001–124


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 / signallingLink / signallingLinkSet /signallingPoint / software / stateChangeRecord / traceControl/ traceFileReadyRecord / traceLogRecord / transceiver /transceiverEquipment / transceiverZone / transcoder /transcoderBoard / xtp]


Type : DP

objectInstance

Description : Scope of an alarm criteria. It covers all network objects whenundefined.


Type : DP



Object Filter List V12

Description : To select messages issued by one or several objects, and theirsubtree (optional).

The Object Filter List parameter includes the followingcomponents: objects and scope.

Click the Modify button to enter the names of the objects tobe selected.

The scope enables to select the subtree of an object.

Value range : objects [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 / powerControl / signallingLink /signallingLinkSet / signallingPoint / software /stateChangeRecord / traceControl / traceFileReadyRecord /traceLogRecord / transceiver / transceiverEquipment /transceiverZone / transcoder / transcoderBoard / xtp]


Type : DP

objects

Description : To select messages issued by one or several objects (50 objectsmax), enter the concerned object classe(s). This field has to beempty to select all object classes.


If a class is selected, the user may select one or more objectscreated in that class. If no object is selected, all messagesissued by all objects created in the class are displayed.


PE/DCL/DD/0124411–9001–124


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 / powerControl / signallingLink /signallingLinkSet / signallingPoint / software /stateChangeRecord / traceControl / traceFileReadyRecord /traceLogRecord / transceiver / transceiverEquipment /transceiverZone / transcoder / transcoderBoard / xtp]


Type : DP

objects assigned

Description : List of the BSSs assigned to the relay. Fill in the list with bscobject identifiers or names.

Value range : [1 to 255]Object : relay

Type : DP

Remark : A BSS can be assigned to several relays at the same time.

observation type V11


Value range : [general Statistic / fast Statistic / real Time /diagnostic]Object : bscCounterList

Type : DP

observation type V11


Value range : [Observation real time / Observation fast statistic /Performance monitor]


Type : DP

Observed counters V11

Description : List of counters (Q3 names) chosen for observation


Value range : [list of Q3 counter names]Type : DP



Observed object class V11

Description : Class of object the user wants to observe

Value range : [bsc / btsSiteManager / bts / pcmCircuit /adjacentCellHandOver / transceiverZone /transceiverEquipment (V12 only) / omc (V12 only) /md (V12 only) / machine (V12 only)]


Type : DP

occupationState

Description : Whether the PCM TS used by the terrestrial circuit is occupiedby an SS7 channel

This attribute is significant provided the xtp object isunlocked.

Value range : [preempted / notPreempted]

preempted The terrestrial circuit is mapped on a. . . . . . . . time slot occupied by an SS7 channelon the Ater interface.

notPreempted The PCM time slot is available for the. . . . . traffic.

Object : xtp

Type : DD


offsetLoad Class 3 O1 V12

Description : Load offset applied by the bsc to the cell selection process



Default value : 0

Feature : Handover decision according to adjacent cell priority and load(TF716 – V12)

Type : DP

Checks : [C/M]: This attribute must be in the range [0 to 63].



PE/DCL/DD/0124411–9001–124


Notes : When set to “0”, no offset is effective.This parameter is set to “0” for the cells that do not belongto the related bsc object.

offsetPriority Class 3 O2 V12

Description : Priority offset applied by the bsc to the cell selection process


Default value : 1

Type : DP

Feature : Handover decision according to adjacent cell priority and load(TF716 – V12)

Checks : [C/M]: This attribute must be in the range [1 to 5].


Note : “1” is the highest priority.

OMC notification number

Description : To select OMC–R manager notifications with a given number



Type : DP

omuId V13

Description : Identifier of the ‘omu’ object class. This identifier is allocatedby the MD–R at object creation, depending on the shelf andslot numbers indicated by the BSC. This attribute cannot bemodified. This attribute is relevant for BSC e3 and TCU e3.

Value range : [0 to 2147483646]Object : omu

Type : DP

on error

Description : Whether to stop running commands when an applicative erroris detected by the system (stop)

Value range : [stop / continue]Object : commandFile – Run

Type : DP



operationalState V13



The state parameter combinations for the atmRm object are asfollows:

administrative State operationalState availabilityStatus

{} disabled notInstalled

{} disabled {}

{} disabled failed

{} disabled dependency

{} enabled {}

Object : atmRm


Type : DD

operationalState



The state parameter combinations for the bsc object are asfollows:

administrativeState

operationalState

availabilityStatus

Meaning

locked disabled {} The BSC has just been created orlocked.

unlocked disabled {} The BSC is in restart or BDA buildphase.

unlocked disabled dependency The BSS/OMC–R link is not createdor the BSC database is not built.

unlocked disabled failed The BSC refuses every command,including resetting.

unlocked enabled {} The BSS/OMC–R link and theassociations with the BSC areestablished, and the BSC database isbuilt.

Object : bsc

Type : DD


PE/DCL/DD/0124411–9001–124


operationalState



The state parameter combinations for the bscMdInterfaceobject are as follows:

administrativeState

operationalState

availabilityStatus

Meaning

locked disabled {} The BSS/OMC–R link has beenlocked by a user.

unlocked disabled {} The link has just been created andthe connection is not established yet(initial state).

unlocked disabled dependency The link is down.

unlocked disabled failed The connection cannot bereestablished.

unlocked enabled {} The connection is established.


Type : DD

operationalState



The state parameter combinations for the bts object are asfollows:

administrativeState

operationalState

availabilityStatus

Meaning

locked disabled {} The cell has just been created orlocked.

unlocked disabled dependency The radio site is not working or theTDMA frames are not correctlyconfigured.

unlocked enabled {} The radio site is working and thenumber of TDMA frames correctlyconfigured for the cell is reached.

shuttingDown

enabled busy The radio cell is being releasedfollowing a soft release command.

Object : bts

Type : DD



operationalState



The state parameter combinations for the btsSiteManagerobject are as follows:

administrativeState

operational State

availabilityStatus

Meaning

locked disabled {} The site has just been created orlocked.

unlocked disabled {} Downloading in the site BCF isin-progress.

unlocked disabled dependency

The PCM link used for the site LAPDsignaling is faulty.

unlocked disabled failed Loss of Level 3 dialogue orconfiguration Abis message notcorrectly acknowledged ordownloading problem

unlocked enabled {} The PCM is available for LAPDsignaling, the Level 3 dialogue isestablished, and the configuration andAbis connection with the site BCF areOK.


Type : DD

operationalState

Description : ISO state. “disabled” means that the BSC cannot send themessages to the OMC–R agent.


The state parameter combinations for the callPathTrace objectare as follows:

administrativeState

operationalState

usageState Meaning

locked enabled idle Call path tracing has just started inthe BSC or has been stopped by theoperator.

unlocked enabled busy Call path tracing is in-progress andmessages are forwarded to theOMC–R agent.


PE/DCL/DD/0124411–9001–124


administrativeState

MeaningusageStateoperationalState

unlocked enabled idle Call path tracing is stopped(end-of-session criterion is true).

unlocked disabled Call path tracing is in-progress butmessages are not forwarded to theOMC–R agent.


Type : DD




The state parameter combinations for the cc object are asfollows:

operationalState availabilityStatus

disabled notInstalled

disabled {}

disabled failed

disabled dependency

enabled online

Object : cc


Type : DD




The state parameter combinations for the cem object are asfollows:


{} disabled notInstalled

{} disabled {}



administrative State availabilityStatusoperationalState

{} disabled failed


{} enabled {}

Object : cem


Type : DD




The state parameter combinations for the cn object are asfollows:


{} disabled {}

{} disabled failed

{} disabled degraded

{} enabled online

Object : cn


Type : DD

operationalState


Value range : [enabled / disabled]Object : efd

Type : DD




The state parameter combinations for the g3BscEqp object areas follows:


PE/DCL/DD/0124411–9001–124



{} disabled {}

{} enabled {}


Object : g3BscEqp


Type : DD




The state parameter combinations for the g3Transcoder objectare as follows:


{} disabled {}

{} disabled failed


{} enabled degraded

{} enabled {}

Object : g3TranscoderEqpt


Type : DD




The state parameter combinations for the iem object are asfollows:


{} disabled not installed

{} disabled {}

{} disabled failed



administrative State availabilityStatusoperationalState


{} enabled {}

Object : iem


Type : DD




The state parameter combinations for the in object are asfollows:


disabled dependency

disabled {}

enabled degraded

disabled {}

enabled failed

Object : in


Type : DD

operationalState



The state parameter combinations for the lapdLink object areas follows:

operationalState

availabilityStatus

Meaning

disabled dependency Loss of Level 1

disabled failed SICD board faulty or TSCB faulty (Ater LAPD link) orBSCB faulty (Abis LAPD link)

enabled {} The Level 1 is established and the SICDs, RCBs, andrelated internal PCMs are working.

Object : lapdLink

Type : DD


PE/DCL/DD/0124411–9001–124


operationalState



The state parameter combinations for the log object are asfollows:

operationalState

availabilityStatus

Meaning

disabled {} The disk message saving partition is full (current alarmlog).

disabled logFull The disk message saving partition is full (currentobservation or trace log).

enabled {} The messages are actually saved in the partition.

Object : log

Type : DD




The state parameter combinations for the lsaRc object are asfollows:


disabled dependency

disabled {}

enabled degraded

disabled {}

enabled failed

Object : lsaRc


Type : DD



operationalState



The state parameter combinations for the mdScanner objectare as follows:

operationalState

availabilityStatus

Meaning

disabled {} The observation is running but the messages cannot beforwarded to the OMC–R agent.

disabled {offDuty} The observation is stopped and the messages cannotbe forwarded to the OMC–R agent.

enabled {} The observation is running and the messages areforwarded to the OMC–R agent.

enabled {offDuty} The observation is stopped and the messages areforwarded to the OMC–R agent.

Object : mdScanner

Type : DD




The state parameter combinations for the mms object are asfollows:


locked {} {}

Object : mms


Type : DD




The state parameter combinations for the omu object are asfollows:


PE/DCL/DD/0124411–9001–124



locked {} {}

Object : omu


Type : DD

operationalState



The state parameter combinations for the pcmCircuit objectare as follows:

administrativeState

operationalState

availabilityStatus

Meaning

locked disabled {} The PCM has just been created orlocked.

unlocked disabled dependency The TCU is faulty (A interfacePCMs).

unlocked disabled failed The DDTI board or the internal PCMpartner is faulty, or the connection isdown.

unlocked enabled {} The DDTI board and the internalPCM partner are working and theconnection is established.

Object : pcmCircuit

Type : DD






The state parameter combinations for the pcu object are asfollows:

administrativeState

operationalState

availabilityStatus

Meaning

locked disabled {} The PCU has just been created orlocked.

unlocked disabled dependency The Level 2 is not established or theconnection with the BSC is down(external PCM).

unlocked enabled {} The PCU is working.

Object : pcu


Type : DP




The state parameter combinations for the pcu object are asfollows:

operationalState

availabilityStatus

Meaning

disabled {} The pcusn has just been created.

disabled dependency The pcusn object does not work, or the PCM link doesnot work.

enabled {} The pcusn object is working.

Object : pcusn


Type : DP


PE/DCL/DD/0124411–9001–124


operationalState



The state parameter combinations for the signallingLinkobject are as follows:

administrativeState

operationalState

availabilityStatus

Meaning

locked disabled {} The SS7 link has just been createdor locked.

unlocked disabled dependency The PCM carrying the SS7 link isfaulty or there is no MTP2 messagebetween the BSC and the MSC.

unlocked disabled failed The CCS7 board is faulty.

unlocked enabled {} The PCM and CCS7 board areworking and MTP2 messages areexchanged between the BSC and theMSC.


Type : DD




The state parameter combinations for the sw8kRm object areas follows:


{} disabled not installed

{} disabled {}

{} disabled failed


{} enabled {}

Object : sw8kRm


Type : DD






The state parameter combinations for the tmu object are asfollows:


locked disabled not installed

unlocked disabled {}

{} disabled failed


{} enabled degraded

{} enabled {}

Object : tmu


Type : DD

operationalState



The state parameter combinations for the traceControl objectare as follows:

administrativeState

operationalState

Meaning

locked enabled Call tracing has not started or has been stopped,and the messages are forwarded to the OMC–Ragent.

locked disabled Call tracing has been stopped and the messagescannot be forwarded to the OMC–R agent.

unlocked enabled Call tracing is in-progress in the BSC and themessages are forwarded to the OMC–R agent.

unlocked disabled Call tracing is in-progress but the messages cannotbe forwarded to the OMC–R agent.


Type : DD


PE/DCL/DD/0124411–9001–124


operationalState



The state parameter combinations for the transceiver objectare as follows:

operationalState

availabilityStatus

Meaning

disabled dependency The parent cell is not working or no TRX/DRX isavailable for the TDMA frame.

disabled failed The BTS has refused the TDMA frame configuration oris using the partnered TRX/DRX for BCCH fillingpurposes.

enabled {} The parent cell is working, a TRX/DRX is available forthe TDMA frame, and the BTS has accepted the TDMAframe configuration.


Type : DD

operationalState



The state parameter combinations for thetransceiverEquipment object are as follows:

administrativeState

operationalState

availabilityStatus

Meaning

locked disabled {} The TRX/DRX has just been created orlocked.

unlocked disabled {} Downloading in the TRX/DRX isin-progress.

unlocked disabled dependency The parent radio site or the parent cell orthe PCM link partner is not working.

unlocked disabled failed The TRX/DRX is assigned to BCCH fil-ling by the BTS or loss of Level 3 dial-ogue or Abis configuration message notcorrectly acknowledged or downloadingproblem or status regression.



administrativeState

MeaningavailabilityStatus

operationalState

unlocked enabled {} The parent cell is working, a PCM isavailable fo the TRX/DRX, and the Level3 dialogue is established.

shuttingDown

enabled {} The TRX/DRX is being releasedfollowing a soft release command.


Type : DD

operationalState



The state parameter combinations for the transcoder object areas follows:

administrativeState

operationalState

availabilityStatus

Meaning

locked disabled {} The TCU has just been created orlocked.

unlocked disabled dependency The SICD, RCB, TSCB, or internalPCM partner is faulty or the Level 2is not established or the connectionwith the BSC is down (externalPCM).

unlocked enabled {} The TCU is working.

Object : transcoder

Type : DD

operationalState



The state parameter combinations for the transcoderBoardobject are as follows:

administrativeState

operationalState

availabilityStatus

Meaning

locked disabled {} The TCB has just been created orlocked.

unlocked disabled {} Downloading in the TCB isin-progress.


PE/DCL/DD/0124411–9001–124


administrativeState


operationalState

unlocked disabled dependency The parent TCU is not working.

unlocked disabled failed The UTE board or internal PCMpartner is faulty or downloadingproblem or a severe error wasdetected.

unlocked enabled {} The TCB is working.


Type : DD




The state parameter combinations for the trm object are asfollows:


locked disabled not installed

unlocked disabled {}

{} disabled failed


{} enabled {}

Object : trm


Type : DD

operationalState



The state parameter combinations for the xtp object are asfollows:

administrativeState

operationalState

usageState

availabilityStatus

Meaning

locked disabled idle {} The CIC has just beencreated or locked.

unlocked disabled idle dependency The PCM link partneris faulty.



administrativeState


usageState

operationalState

unlocked disabled idle failed The CIC is preempted.

unlocked enabled idle {} The CIC is workingand traffic-free.

unlocked enabled busy {} The CIC is workingand traffic-busy.

shuttingDown

enabled busy {} The CIC is beingreleased following asoft release command.

Object : xtp

Type : DD

otherServicesPriority Class 3 O3

Description : Index in the table allocPriorityTable for a TCH allocationrequest (in signaling mode) whose cause is “other services”



Object : bts

Default value : 17

Type : DP

output classes

Description : List of authorized output classes that define a terminal outputdomain. Output 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 automatically displayed on the terminal screenoutside work sessions.

Object : terminal profile

Type : DP


PE/DCL/DD/0124411–9001–124


output classes

Description : List of authorized output classes that define a user’s outputdomain. Output classes grant access to various types of data.

Value range : [OMC–R browser / alarm window / performance monitor /command file manager / security manager / SMS–CBmanager / description window / job scheduler window / alarmlog window / system session log window / call traces window/ Unix window / notification log window / notificationwindow / relay manager/ alarm criteria]

The “notification log window” class gives access to the systemnotification log, while the “notification window” class givesaccess to the user notification log.


Type : DP

owner

Description : Name of the user who created the command file on theOMC–R



Type : DP



P

packetAckTime Class 3 V12


dwAckTime

upAckTime

The deactivation value is 64 for both of them.


pagingOnCell Class 3 P1 V9

Description : Enable or disable paging requests in a cell



Type : DP


pan Class 3 V12


panInc

panDec

panMax


panDec Class 3 (pan) V12

Description : The MS counter N3102 is decremented by panDec each timePUAN 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


Note : If the MS counter equals “0”, an abnormal release isperformed.


PE/DCL/DD/0124411–9001–124


panInc Class 3 (pan) V12

Description : The MS counter N3102 is incremented by panInc each timea PUAN message which allows the transmit window to goforward is received


Object : bts

Default value : 0


Type : DP



panMax Class 3 (pan) V12

Description : Maximum value of the counter N3102 (used in case of blockacknowledgment time out), set by the MS at each cellreselection


Object : bts

Default value : 0


Type : DP



parameter(s)

Description : List of parameters to define when running the command file

Their generic format is $XXX, where $ identifies such aparameter and XXX is a string of uppercase, alphanumericalcharacters that does not contain spaces.


Type : DP



partialRecordCriteriaType

Description : Criterion that defines the type of partial records to generate inthe BSC

Value range : [event type / numbered / timed / no partial]

event type The BSC generates partial records. . . . . . . . each time a handover is successful(partialRecordCriteriaEvent–Type = “handover”).

numbered The BSC generates partial records. . . . . . . . every <N> successful 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 theend of each traced call. If the traceControl object is lockedbefore the end of a call, all related data are lost.


Type : DP

Checks : [M]: The traceControl object is locked.

particular intervention

Description : Type of action associated with an alarm criteria in the specificconfiguration


Type : DP

password

Description : User’s current password as defined in the user’s profile. It isnot displayed.

Value range : [case sensitive]Object : user profile – Change password

Type : DP


PE/DCL/DD/0124411–9001–124


password

Description : User’s password. It begins with a letter, contains at least onenon–alphabetical 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 onenon-alphanumerical character among the firsteight characters.

[C/M]: The password is at least six–character long.

password duration

Description : Maximum time during which the user’s current password isvalid

Value range : [2 to 2147483646] days

When a password validity duration runs out, the passwordmust be changed on opening the next work session. The user’saccess to MMI commands is barred until the password ischanged. Refer to the password status entry.


Type : DP

pcmCircuit

Description : Identifier of a pcmCircuit object defined with regard to a bscobject (Abis,Ater, or Agprs interface). It is related to thenumber of the DDTI board to which the PCM described linkis physically connected in the BSC.

PCM links are identified by the DDTI boards to which they areconnected in the BSC. A PCM link connected to DDTI boardno.i has a reference equal to “2i” or “2i+1” (each boardmanages two links at a time). See to NTP < 22 >, which givethe relationship between the number of a board and its physicallocation 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 regardto the site (pcmCircuitBtsSiteManager). Refer to thebscSitePcmList entry in the Dictionary.



Value range : [0 to 47]Object : pcmCircuit (Abis, Ater, and Agprs interfaces)


Type : Id

Checks : [C]: The maximum number of external PCM linksallotted to a BSC depends on its type andarchitecture:

BSC 12000/6000T1 T2 T3 T4 T5

external PCMs 12 20 28 40 48

[C]: The number of external PCM links allotted to aBSC on the Ater interface depends on the numberof TCUs linked to the BSC (one TCU uses onelink).



[D]: If the application database of the related BSC isbuilt, the pcmCircuit object is locked.


[D]: No btsSiteManager object (Abis PCM) ortranscoder object (Ater PCM) or pcu object(Agprs PCM) refers to the pcmCircuit object.

[D]: No mdScanner object describing a temporaryobservation refers to the pcmCircuit object (noobservation is running on the concerned PCM).

pcmCircuit

Description : Identifier of a pcmCircuit object defined with regard to atranscoder object (A interface). It is related to the number ofthe TDTI board to which the PCM described link is physicallyconnected in the TCU.

PCM links are identified by the TDTI boards to which they arephysically connected in the TCU.


PE/DCL/DD/0124411–9001–124


PcmCircuit TDTI N° Port N°0 0 0

1 1 0

2 1 1

3 2 0

2 1

Unused

Value range : [0 to 3]Object : pcmCircuit (A interface)

Type : Id

Checks : [C]: The number of PCM links connected to a remotetranscoder on the A interface is limited tomaxPcmCTPerTranscd (static configurationdata).

[C]: The parent transcoder object is created.

[C]: <maxTranscdBPerTranscd> transcoderBoardobjects are created for the parent transcoderobject.


[D]: If the application database of the related BSC isbuilt, the pcmCircuit object is locked.


[D]: No signallingLink or xtp object refers to thepcmCircuit object.

pcmCircuitBsc

Description : Identifier of a PCM link (pcmCircuit object) used by a radiosite defined with regard to the BSC. It is related to the numberof the DDTI board to which the link is physically connectedin the BSC.

Refer to the bscSitePcmList entry in the Dictionary, whichdefines the relationship between these two attributes.


Type : DP



pcmCircuitBtsSiteManager

Description : Identifier of the PCM link defined with regard to the BTS. Itis related to the number of the DTI or PCMI board to whichthe link is physically connected in the BTS.

Refer to the bscSitePcmList entry in the Dictionary, whichdefines 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 candirectly allocate the PCM link that supports a LAPD link.

Value range : [0 to 47]Object : lapdLink

Type : DD

pcmCircuitId Class 2

Description : Identifier of the PCM link used by an SS7 channel on the Ainterface, defined with regard to the TCU

Value range : [0 to 3]Object : signallingLink

Type : DP

Checks : [C/M]: The pcmCircuit object is created for thetranscoder object referenced by thesignallingLink object (transcoderId).

[C/M]: If the described link is PCMA no.3, the time slotused by the SS7 channel (timeSlotNumber) is inthe range [1 to 27] if the PCM link is an E1 link andin the range [1 to 20] if the PCM link is a T1 link.Since the last four time slots of that link are notmapped on the Ater interface, they are unusable(refer to the transcoderMatrix entry in theDictionary).

[M]: The parent bsc object is unlocked and thesignallingLink object is locked.


PE/DCL/DD/0124411–9001–124



Description : Identifier of the PCM link used by a TCU on the Ater interface,defined with regard to the BSC


Object : transcoder

Type : DP

Checks : [C/M]: The pcmCircuit object is created for the parent bscobject.

[C/M]: It is not used on the Abis interface by abtsSiteManager object nor on the Ater interface byanother transcoder object dependent on the sameparent bsc object.

[M]: The parent bsc object is unlocked, and thetranscoder object and the signallingLink objectsthat refer to it are locked.



Description : Identifier of the PCM link used by a terrestrial circuit on theA interface, defined with regard to the TCU


Object : xtp

Type : DP

Checks : [C/M]: The pcmCircuit object is created for thetranscoder object referenced by the xtp object(transcoderId).

[C/M]: If the described link is PCMA no.3, the time slotused by the terrestrial circuit (timeSlotNumber)is in the range [1 to 27] if the PCM link is an E1link and in the range [1 to 20] if the PCM link isa T1 link. Since the last four time slots of that linkare not mapped on the Ater interface, they areunusable (refer to the transcoderMatrix entry inthe Dictionary).

[M]: The parent bsc object is unlocked and the xtpobject is locked.



pcmErrorCorrection Class 2 P2 V12

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

Value range : [0 / 1]Object : bts

Default value : 1

Type : DP

Feature : PCM error correction (FM660 – V12)

Checks : [C/M] This attribute can be set to “1” only ifenhancedTRAUFrameIndication attribute isset to “available” or “active”

[M]: The parent bsc is unlocked and the bts object islocked.

Note : This parameter is only available for BTSs equipped with nonmixed DCU4 or DRX transceiver architecture.

pcmNbr Class 2 (gprsPcuCrossConnectList) V12

Description : Number of the PCM used for Agprs interface

Value range : [0 to 47]Object : pcu

Default value : 0


Type : DP



pcmTimeSlotNumber Class 2 V8

Description : Scheduled time slot of a radio site on the Abis interface

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 thebstSiteManager object radioSiteMask, so itcannot be allotted by the BSC.



PE/DCL/DD/0124411–9001–124


Notes : The relation “scheduled time slot = teiBtsSiteManager + 1”is always true at BTS level.

It can be false at BSC level provided a PCM switchingmatrix is used between the BSC and the BTS; otherwise, itis true.

pcmType Class 3

Description : Interface on which the PCM link is used

Value range : [pcmA / pcmAbis / pcmAter / pcmAgprs]

Object : pcmCircuit


Type : DP

Checks : [M]: If the current attribute value is “pcmA”, nosignallingLink or xtpobject refers to that object(pcmTimeSlotNumber).

[M]: If the current attribute value is “pcmAbis”, nobtsSiteManager object refers to that object(bscSitePcmList).

[M]: If the current attribute value is “pcmAter”, notranscoder object refers to that object(pcmCircuitId).

[M]: If the current attribute value is “pcmAgprs”, nopcu object refers to that object(bscPcuPcmRefList).

[M]: “pcmAbis” is forbidden for pcmCircuitId equals0, 2, 4, or 6.


pcu V12

Description : Identifier of a pcu object defined with regard to a bsc object

Value range : [0 to 2147483646]

Object : pcu


Type : Id



pcuLapdEqptRefList Class 2 V12

Description : List of LAPD equipment numbers used by the pcu object

Value range : [0 to 12] values in the range [0 to + infinite]

Object : pcu


Type : DP

Checks : [C/M]: All the referred LAPD equipment object instancesof this attribute must exist

[C/M]: The sapi attribute of the referred lapdLink objectinstances must have been set to ’OML’. TheassociatedInterface attribute of the referredlapdLink object instances must have been set to’Agprs’.

[C/M]: A lapdLink object instance can be referred by onlyone pcu object instance

[M]: The parent bsc object is unlocked and the pcuobject is locked.


pcusn V12

Description : Identifier of a pcusn object


Object : pcusn


Type : Id

pcuSNName V12

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.


PE/DCL/DD/0124411–9001–124


pcuSNReserved1 Class 3 V12


Value range : [–32768 to 32767]

Object : pcusn


Type : DP

pcuSNReserved2 Class 3 V12


Value range : [–32768 to 32767]

Object : pcusn


Type : DP

penaltyTime Class 3 P3 V8

Description : Timer used by an idle mobile before reselecting a cell (C2criterion)

When a mobile places the cell on the list of strongest carriers,it starts a timer that stops after penaltyTime seconds. Thistimer is reset when the mobile removes the cell from the list.

For the entire timer duration, the reselection criterion (C2) isassigned 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” isreserved and indicates that the temporary offset is ignored inthe reselection criterion (C2) calculation. It also changes thesign in the C2 formula.

Object : bts

Feature : AR 264

Default value : 20

Type : DP




perceived severity

Description : To select messages according to the priority

The alarm processing priority provides an indication of howit is perceived that the capability of the managed object hasbeen affected. Refer to the alarmPriority entry in theDictionary 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.Object : Alarm and notification logs – Filter

Type : DP

periodCCCHLoadIndication Class 3

Description : Periodicity at which the BTS sends the CCCH payload to theBSC (“9.2” is the only value accepted)

Value range : [0.00 to 2147483646] secondObject : bts

Type : DP

Checks : [C/M]: The only value accepted by the system is “9.2”.



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

plmnPermitted Class 3

Description : List of NCC of the PLMNs on which MSs are allowed to takemeasurements for handovers. Listening to the PLMN towhich the cell belongs must be authorized.


Default value :Type : DP



PE/DCL/DD/0124411–9001–124


PODType

Description : Type of the BSC or BTS involved, as defined in the PhysicalObjects Dictionary

Value range : [BSC1GT / BSC2GT / BTSoutdoor / BTSindoor / BTSmicro/ BTSsmart / BTSoutdoor2G]


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]


Type : DP

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

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

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

portEthernetOperational V13

Description : Operational state of the OMU external Ethernet port.

ISO operational state (enabled/disabled).

This attribute is dynamically managed by the BSS. Valuechanges are not notified to the Manager.


Value range : [enabled/disabled]Object : omu

Type : DD




portEthernetStatus V13

Description : Availability status of the OMU module external Ethernet port.

ISO availability status ({}, {dependency}, {failed}).




Object : omu

Type : DD


port0X25Status V13

Description : Operational state of the OMU module external X.25 port 0




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

Type : DD


port1X25Status V13

Description : Availability status of the OMU external X.25 port 1.

ISO availability status ({}, {dependency}, {failed}).


Value changes are not notified to the Manager.



Object : omu

Type : DD



PE/DCL/DD/0124411–9001–124


portChosen Class 2

Description : Number of the SUN port to use on the OMC–R end

Value range : [port0 / port1 / automaticChoice (selection by the OMC–Ragent)]

If the port is not uniquely selected, it will be dynamicallyassigned by the OMC–R agent.

Selecting “automaticChoice” is recommended since it allowsthe OMC–R agent to reconfigure the port currently used whena problem occurs.


Type : DP

Checks : [M] : The bscMdInterface object is locked.

portUsed

Description : Number of the SUN port currently used

Value range : [port0 / port1]

This dynamic attribute identifies the OMC–R port currentlyused. It can be different from portChosen since the OMC–Ragent switches the transport connection with a BSC over to theother port as and when needed.

No information is displayed unless the BSS/OMC–R link isestablished.


Type : DD

positionInShelf V13

Description : Indicates the position of a module in a shelf


Object : atmRm, cc, cem, iem, lsaRc, mms, omu, sw8kRm, tmu, trm

Type : DD




powerBudgetInterCell Class 3 P4

Description : Authorization to perform intercell handovers for powerbudget




Type : DP


powerClass

Description : Transmission power class of a TDMA frame

Value range : [powerClass5 (GSM 900 network, GSM–R network, E–GSM,or GSM 900 – GSM 1800 network)powerClass1 (GSM 1800 network, GSM 1900 network,or GSM 1800 –GSM 900 network)]


Default value : powerClass1

Type : DP

Checks : [C]: The attribute value complies with the type ofnetwork in which the TDMA frame is used. Referto the standardIndicator entry in the Dictionary(attribute of the parent bts object).



PE/DCL/DD/0124411–9001–124


powerControl

Description : Identifier of a powerControl object that defines the powercontrol management parameters in a cell. A bts object mayreference one and only one object of this type.

Value range : [0 to 2147483646]


Type : Id

Checks : [C]: The associated bts object is created and thepowerControl object is not created for that object.



[M/D]: The powerControl object is created.

[D]: The associated bts object is not referenced, exceptby an handOverControl object.


powerControlIndicator Class 3 P5

Description : Whether MS signal strength measurements includemeasurements on BCCH

BCCH measurements must not be included when thefollowing two conditions are met:

The radio channel hops at least on two differentfrequencies, including the BCCH frequency.

Power control on the downlink is used.

Value range : [include BCCH measurements / do not include BCCHmeasurements]

Object : bts

Default value : include BCCH measurements

Type : DP




powerDownlink V8

Description : Power gain in the BTS-to-MS direction used by the speechprocessing algorithm in a TCB

This parameter is a component of the algorithm Used attribute.Refer to this entry in the Dictionary.

Value range : [–15 to +15] dBType : DP


Default value : 0

powerIncrStepSize Class 3 P6

Description : Step for increasing MS or BTS txpwr when using step by stepalgorithm

Value range : [2, 4, 6] dBObject : powerControl


Type : DP

Checks : [M]: lRxLevDLP + powerIncStepSize ≤ uRxLevDLP.

[M]: lRxLevULP + powerIncStepSize ≤ uRxLevULP.


Note : This parameter is significant only when the BTS uses thestandard “step by step” power control algorithm.

powerRedStepSize Class 3 P7

Description : Step for reducing MS or BTS txpwr when using step by stepalgorithm

Value range : [2, 4] dBObject : powerControl


Type : DP

Checks : [M]: uRxLevDLP – powerRedStepSize ≥ lRxLevDLP.

[M]: uRxLevULP – powerRedStepSize ≥ lRxLevULP.




PE/DCL/DD/0124411–9001–124


powerUplink V8

Description : Power gain in the MS-to-BTS direction used by the speechprocessing algorithm in a TCB

This parameter is a component of the algorithm Used attribute.Refer to this entry in the Dictionary.

Value range : [–15 to +15] dBType : DP


Default value : 0

preemptionAuthor Class 3 P8 V12

Description : Defines the preemption management

Value range : [forbiddenauthorizedWithReleaseauthorizedForcedHO]


Default value : forbiden

Type : DP

Feature : ASCI (GSM–R V12)


Note : authorizedForcedHO option is not available.

preSynchroTimingAdvance Class 3 P9 V10

Description : Pre–defined timing advance used in a pre–synchronizedhandover procedure between the serving cell and thisneighbor cell.

This value of timing advance is used when the parameter“synchronized” is set to “pre sync HO with timing advance”.The operator defines a predefined timing advance when aphase 2 MS goes from the serving cell to this neighbor cellapproximately at the same place (railway, highway).

Value range : [1 to 35] (km)Object : adjacentCellHandOver

Default value : Refer to parameter synchronized

Type : DP




priority Class 2 P10

Description : Priority level of a TDMA frame.

Among the set of TDMA frames attached to a cell, the onecarrying the cell BCCH must always be allotted the highestpriority [0].

At least <minNbOfTDMA> TDMA frames related to a cell(refer to this entry in the Dictionary) must be successfullyconfigured for the cell to be working. They include the TDMAframe carrying the cell BCCH and those with the highestpriority(ies).

If this is true when the cell is brought into service, then, the cellwill be working. Otherwise, its operationalState will be“disabled” and its availabilityStatus will be “{dependency}”.



Type : DP


privateMmsOmuRef V13

Description : Pointer to the associated ‘omu’ object instance for privateMMS, NULL for shared–mirrored MMS.

This attribute cannot be modified.

It is set by the MD–R at MMS creation.

Value range : [0 to 2147483646]

Object : mms

Type : DP


probable cause

Description : To select messages according to the numerical value of the ISOprobableCause field


The following table indicates the messages displayedaccording to the probable cause.


PE/DCL/DD/0124411–9001–124


Alarm type Probable cause Value

Communications Execution failure of a MD request by the BSCCall establishment errorCommunication protocol error

6245

Communication subsystem failureCorrupt dataDegraded signal

69

12

DTE–DCE interface errorLAN errorLocal node transmission error

132527

Loss of frameLoss of signalReceive failure

282940

Remote node transmission errorTransmit failure

4254

Environmental External alarm loopEnclosure door openFire detected

581418

Heating, ventilation, or cooling systemMaterial supply exhausted

2130

Equipment Equipment absentEquipment malfunctionHeating, ventilation, or cooling system problem

601521

Input/output device errorInput device errorMaterial supply exhausted

232430

Power problemProcessor problemReceive failure

353740

Receiver failureStorage capacity problemTemperature unacceptable

414950

Timing problemTransmit failureTransmitter failure

525455

ProcessingError Cause of restart or switchoverNo responseApplication subsystem failure

59612

Configuration or customization errorCorrupt dataFile error

79

17

Out of memoryQueue size exceededSoftware error

323946



Alarm type ValueProbable cause

Software program abnormally terminatedSoftware program errorStorage capacity problem

474849

Underlying resource unavailableVersion mismatch

5657

QualityOfService ShutdownCongestionPerformance degraded

638

34

Queue size exceededResource at or nearing capacityResponse time excessive

394344

Retransmission rate excessiveThreshold crossed

4551



Type : DP

processorLoadSupConf Class 3 L10 V8

Description : Threshold used in the load control algorithm by the BSC

The table hereafter gives the % of the theorical load usablevalues for each type of board.

value OMU (level 1, 2, 3) Other boards Comments

0 80–90–100 80–90–100 nominal value

1 80–90–100 90–100–100 permissive value

2 80–90–100 75–85–95 restrictive value

3 100–100–100 100–100–100 simplex mode (see Note 1)

4 80–90–100 80–90–100 nominal value (see Note 2)

5 80–90–100 90–100–100 permissive value (see Note 2)

6 80–90–100 75–85–95 restrictive value (see Note 2)

7 80–90–100 50–60–70 exceptional value (see Note 3)


PE/DCL/DD/0124411–9001–124


value CommentsOther boardsOMU (level 1, 2, 3)

8 80–90–100 80–90–100 reserved value (see Note 4)

9 80–90–100 90–100–100 reserved value (see Note 4)

Note 1: This value must be used when the operator wantsto decrease the impact induced by the simplexmode.

Note 2: For these attribute values (4, 5, and 6), the CPUweighing factor of the OMU board is morerestrictive than for the attribute values 0 to 2, andthis factor must be used in case of high load on thisboard.

Note 3: This value must be used in case of exceptionalevents, in order to manage high blocking rate onthe Air and A interface.

Note 4: The thresholds of these two sets of parameters aremodifiable by using the “BSC data config”functionality.

Value range : [0 to 9] (V11–)[0] (V12)

Object : bsc

Feature : BSC overload management (FM877 – V12)

Default value : 1

Type : DP

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

Remark : C1400, C1506, C1803, C1834, and C1835 counters allow tocheck BSC overload problems.

This parameter was used in the previous releases only tocontrol the load on the BSC CPU boards.



R

rACHLoadAveragingSlots Class 3

Description : Number of RACH access on which RACH measurements areperformed (2000 is the only value accepted)


Type : DP

Checks : [C/M]: The only value accepted by the system is “2000”.



radChanSelIntThreshold Class 3 R1 V8

Description : Maximum interference level on free radio channels, belowwhich the channels are ranged in the group of allocationpriority channels

The information is used to first allocate the free channels withthe lowest interference level. The levels depend on thethresholdInterference attribute value defined for the cell.Refer to this entry in the Dictionary.

The BSC distributes the free radio channels among twogroups:

The first group contains the list of channels with a measuredaveraged interference level equal to or lower than thedefined level.

The second group contains the list of channels with ameasured averaged interference level higher than thedefined level, and recently released channels for which nomeasurement is available.

Four resource pools are defined for each SDCCH or TCH typeof channel:

low interference level radio channels that are authorized tohop

low interference level radio channels that are notauthorized to hop


PE/DCL/DD/0124411–9001–124


high interference level radio channels that are authorized tohop

high interference level radio channels that are notauthorized to hop

Channels are allocated cyclically inside each pool.

dBm– 128 0

Level 0 Level 1 Level 2 Level 3 Level 4

– 108 – 106 – 104 – 102

THRESHOLDINTERFER-ENCE = 1




radChanSelIntThreshold = 0

radChanSelIntThreshold =1






Default value : 1

Type : DP


radioAllocator Class 2 (gprsBtsLockExtendedConf) V12

Description : Radio allocator type used in the cell

Value range : [voice + dataCircuit,voice + dataCircuit + packetData]

Object : bts


Default value : voice + dataCircuit

Type : DP




radioLinkTimeOut Class 2

Description : Maximum value of the counter (S) associated with thedownlink SACCH messages, beyond which the radio link iscut off. It is lower than or equal to t3109.

Mobiles comply with system operating conditions when thecounter (S) is assigned a value lower than or equal to t3109.

If the receiver is unable to decode a downlink SACCHmessage (BTS-to-MS direction), the counter is decreasedby 1. If the message is received, the counter is increased by 2.When the counter goes down to zero, the radio link is declared“faulty”.

decoded expected but not decodedradio link failure

4

0

Value range : [4 to 64, by steps of 4] SACCH frames (1 unit = 480 ms onTCHs, 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 does not check that the values of the twoattributes are consistent.


PE/DCL/DD/0124411–9001–124


radioSiteMask Class 2

Description : Definition of the PCM time slots that can be used by a site. TSn is masked when bit n is set to 0, it can be used when bit n isset to 1 in the binary field. The alarm mask is immediatelydisplayed in the hexadecimal field just below. The alarm maskcan be set using the hexadecimal field as well as the binaryfield. TS 0 (least significant bit) is always masked since itcannot be used.

The mask defines the time slots that can be used in each PCMlink allotted to a given radio site. Time slot allocation ismanaged by the BSC; a time slot available on a site can be usedeither by a radio time slot for traffic purposes or by a LAPDlink which does not carry the link with the site BCF forsignaling.

A PCM E1 link carries thirty-two time slots. TheradioSiteMask of a site using E1 links is as follows:

radioSiteMask = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx0

| | | | |

TS31 23 15 7 TS0

A PCM T1 link carries twenty-four time slots. TheradioSiteMask of a site using T1 links is as follows:

radioSiteMask = 0000000xxxxxxxxxxxxxxxxxxxxxxxx0

| | | | |

TS31 23 15 7 TS0

Sites that do not share PCM links may be assigned the full set.

In a BTS chain, the scheduled time slots of each radio site mustbe allotted in ascending order (TS1, TS2, TS3, etc.), beginningwith the site closest to the BSC. Refer to thepcmTimeSlotNumber entry.

Value range : [32-bit mask]


Type : DP

Checks : [C/M]: TS 0 cannot be assigned.

[C/M]: If PCM T1 links are used, TSs 25 to 31 cannot beassigned.



[C/M]: The radioSiteMask of all sites sharing a samePCM link (drop and insert connections) aredissociated.

[M]: The scheduled time slot of the radio site(pcmTimeSlotNumber) is masked [0] since itcannot be used.


radioSiteName

Description : Reference name of a multiple site object on the OMC–R. Itbegins with a letter and is case sensitive.

The name of a multiple site can be used in all MMI commandsto reference the multiple site on the OMC–R.



Type : DP

Checks : [C/M]: The name of a multiple site is unique to theOMC–R.

radResSupBusyTimer Class 3 R2 V8

Description : Maximum time that SDCCH or TCH can be continuouslyoccupied without generating an alarm

Value range : [1 to 18] hours

Object : bsc

Default value : 3

Type : DP



PE/DCL/DD/0124411–9001–124


radResSupervision Class 3 R3 V8

Description : Indicates whether radio resources are controlled at the celllevel (both busy resources and free resources)

When no control is performed, no alarm related to the use ornon-use of an SDCCH or TCH is generated. Refer to theradResSupBusyTimer and radResSupFreeTimer entries inthe Dictionary.


Object : bts


Type : DP


Note : radResSupBusyTimer and radResSupFreeTimer can be setautomatically by the OMC–R calendar function.

The activation of this feature does not induce any signaling orCPU overload. Only the BSS–OMC–R link is overloaded ata rate of radResSupBusyTimer or radResSupFreeTimer.

radResSupFreeTimer Class 3 R4 V8

Description : Maximum time an SDCCH or TCH can be continuously freewithout generating an alarm

Value range : [1 to 18] hours

Object : bsc

Default value : 18

Type : DP


reception time

Description : To select messages received at that time




Type : DP



Record reference

Description : Identifier of a user call as recorded in a call monitoring datafile

Value range : [0 to 63]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 callreport (Events option) or a radio measurementsreport (Measurements option) is requested.

[A]: It can be undefined when a synthesis report(Synthesis option) is requested. In that case, asummary of all user recorded calls is displayed.

redundantPcmNumber

Description : Number of the redundant PCM link defined on BSC end

This dynamic attribute is displayed provided thebtsSiteManager object redundantPcmPresence attributevalue is “true”.


Type : DD

Remark : A redundant link is not normally used for traffic or signallingconnections.

redundantPcmPresence Class 2

Description : Presence of a redundant PCM link on a radio site

Value range : [true / false]Object : btsSiteManager

Type : DP

Checks : [M]: If the attribute value is “true”, the objectbscSitePcmList attribute includes two items, oneidentifies the PCM active link, and the otheridentifies the PCM redundant link.



PE/DCL/DD/0124411–9001–124


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“excessiveAnomalyRate” function

This attribute is not used by the detection“outOfRangeCounter” function. In that case, the referenceperiod is set as follows:

For cumulative counters, the thresholds define total valuesnot to be reached during a one minute reference period.

For load or value counters, the thresholds define maximumor minimum average values not to be reached during a 1minute reference period, except for the PCM unavailabilitycounters for which they define total values not to be reachedduring the reference observation period.

The BSS observation counter threshold crossing detectionmechanism is described in NTP < 07 >.

Value range : [0 to 2147483646] minutes


Type : DP

relatedSoftwares V13

Description : This attribute identifies the list of software that are separatelyidentifiable. This list represents the unit of software that isready to be used by the equipment. This attribute is allocatedby the MD–R at object creation. This attribute cannot bemodified by the Manager.



Type : DP



relay

Description : Identifier of a BSS alarm relay which activates an externalalarm loop when the counter of immediate unacknowledgedalarms shows a nonzero value for one of the BSSs assigned tothe relay

BSS relays are used to transfer the state of the associated BSSimmediate action alarm counters to remote sites.

A BSS relay can be associated with several BSCs. Conversely,a BSC can be simultaneously assigned to several relays.

Value range : [4 to 64]Object : relay

Type : Id

Reminder : OMC–R relays are used to transfer the state of system alarmcounters 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

repetition rate

Description : Periodicity of short message broadcasting

Each concerned BSC repeatedly sends the selected shortmessage to the BTSs covering the selected cells at therepetition rate defined by the user.

Each BTS repeatedly broadcasts the short message to allmobiles under its control, using the same repetition rate.

Value range : [2 sec / 30 sec / 1 min / 2 min / 4 min / 8 min / 16 min / 32 min]Object : short message – Start broadcast

Type : DP


PE/DCL/DD/0124411–9001–124


Report range V11

Description : Time period chosen 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 Monitorobservation types are 5 min, 15 min, 30 min, 60 min, and2 hours.

report template V11

Description : Identifier of the report template object defined with regard tothe bsc object


Type : DP

reportObjLevel

Description : Level of the report to edit. 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 tothe same class.

reserved1 Class 2 (gprsPcuLockExtendedConf) V12




Type : DP




reserved1 Class 2 (gprsTranscvLockExtendedConf) V12



Default value :


Type : DP





Object : pcu


Type : DP





Default value :


Type : DP



PE/DCL/DD/0124411–9001–124


reserved3 (T3168) Class 3 (gprsBtsExtendedConf) V12

Description : This timer is used at the MS side to define when to stop waitingfor the Packet UL Assignment message after sending aPacket Resource Request message.

Value range : [0 (500 msec)1 (1000 msec)2 (1500 msec)3 (2000 msec)4 (2500 msec)5 (3000 msec)6 (3500 msec)7 (4000 msec)]

Object : bts


Type : DP

Default value : 0






Type : DP






Type : DP




reserved4 (T3192) Class 3 (gprsBtsExtentedConf) V12

Description : Wait for DL TBF release after reception of the final block. Thistimer T3192 is used on the MS side to define when the MSreceived all the RLC data blocks. When the timer expires, theMS releases the resources associated with the TBF and beginsto monitor its paging group (DRX mode).

Value range : [0 (500 msec)1 (1000 msec)2 (1500 msec)3 (0 msec)4 (80 msec)5 (120 msec)6 (160 msec)7 (200 msec)]

Object : bts


Type : DP

Default value : 0






Type : DP





Default value :


Type : DP



PE/DCL/DD/0124411–9001–124


reserved5 Class 3 (gprsBtsExtendedConf) V12


This parameter allows to configure the MAC mode to be usedin UL direction.


In V12.4c release, only “USF” is provided.

“0 = USF”. Value 0 selected: USF

Object : bts

Default value : 0


Type : DP





Object : pcu


Type : DP






Default value :


Type : DP




resetCircuitRepeat Class 1 V8

Description : Whether the RESET CIRCUIT message is repeated onbssMap19 timer elapse if the acknowledgment message wasnot received from the MSC (Phase II compliance)

Value range : [false]Object : signallingPoint


Type : DP

Checks : [C/M]: The only accepted value is “false”.



retransDuration Class 2 R5 V8

Description : Maximum number of occurrences of a same paging sub-groupthat separates the first and the last transmissions of the samepaging message.


Default value : 10

Type : DP


[C/M]: retransDuration ≥ (delayBetweenRetrans + 1)x nbOfRepeat

retry on error

Description : Whether commands are rerun when the system detects anapplication error

This parameter has priority over the on error parameter. Whenits value is “True”, the errored command is rerun; when it is“False”, the on error parameter is analyzed.

The errors involved, the time between reruns, and themaximum number of reruns are defined in static configurationdata.

Value range : [true / false] (default is False)Object : commandFile – Run

Type : DP


PE/DCL/DD/0124411–9001–124


rlf1 Class 2 R6 V8

Description : Value to compute the initial and maximum value of the (CT)counter used in the BTS radio link control algorithm

The FP runs the following algorithm to monitor the uplinkSACCHs (MS-to-BTS direction):

The CT counter is reset to zero when the FP receives aCHANNEL ACTIVATION message.

On each occurence of an uplink SACCH, the followingoccurs:

• if the channel is decoded and CT = 0, then CT = 4 * rlf1 + 4

• if the channel is decoded and CT ≠ 0, then CT = min(rlf1, CT+rlf2)

• if the channel is not decoded, then CT = max (0,CT–rlf3)

When the CT counter goes down to zero, the radio link isbroken and the BTS sends a CONNECTION FAILUREINDICATION message to the BSC.


Default value : 4

Type : DP


Notes : The radioLinkTimeOut attribute serves the same goal onthe downlink.The system does not check that the values of the twoattributes are consistent.

rlf2 Class 2 R7 V8

Description : Step value by which the (CT) counter is increased by the radiolink control algorithm when an uplink SACCH is decoded

Refer to the rlf1 entry.

Value range : [1 to 4] SACCH framesObject : bts

Default value : 2

Type : DP




rlf3 Class 2 R8 V8

Description : Step value by which the (CT) counter is decreased by the radiolink control algorithm when an uplink SACCH is not decoded

Refer to the rlf1 entry.

Value range : [1 to 4] SACCH framesObject : bts

Default value : 1

Type : DP


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 EXTENDEDNEIGHBOUR CELL PARAMETER when more thansixteen defined neighbor cells) messages have beenacknowledged by the BTS.

not configured: The messages have not been acknowledgedby the BTS. If a CURRENT CELL PARAMETER messageis not acknowledged, the notification 1258 “Non responseduring the configuration of the remote L1M” is issued. If aNEIGHBOUR CELL PARAMETER or EXTENDEDNEIGHBOUR CELL PARAMETER message is notacknowledged, the notification 1259 “Negativeacknowledgement of a distant L1M command” is issued.

not significant: The BTS has not sent the messages to theBSC (either the TDMA frame is not working or SYS INFOwas not acknowledged).


Type : DD


PE/DCL/DD/0124411–9001–124


rndAccTimAdvThreshold Class 3 R9 V8

Description : MS-to-BTS distance beyond which mobile access requests toa cell are refused.

It defines the maximum timing advance value accepted.

The effective timing advance value is broadcast in theCHANNEL REQUIRED message sent by the BTS to the BSC.If it is above the user defined threshold, the BSC ignores therequest.


Object : bts

Default value : 35 (non–extended cell), 90 (extended cell)

Type : DP

Checks : [C/M]: The maximum distance is 35 km if the bts objectextended cell attribute is “false”.



Note : The number of access requests that are refused for that reasonis accounted by the BSC (permanent bsc observationcounter 1161/6) and fed back to the OMC–R.

routingArea Class 2 V12

Description : GPRS Cell Global Identifier (locationAreaCode + cellIdentity+ routingArea)


Object : bts

Default value : 0


Type :

Checks : [M]: The parent bsc object is unlocked and the parentbts is locked.

Note : A Routing Area is necessarily included in a Location Area.



runCallClear Class 3 R10

Description : Number of “Measurement Results” messages that must bereceived before the call clearing algorithm in a cell istriggered

Value range : [1 to 31] SACCH frames (1 unit = 480 ms on TCHs, 470 mson SDCCHs)

Object : bts

Default value : 16


runHandOver Class 3 R11

Description : Number of “Measurement Results” messages that must bereceived before the handover algorithm in a cell is triggered.


Object : bts

Default value : 1

Type : DP


runPwrControl Class 3 R12

Description : Number of “Measurement Results” messages that must bereceived before the power control algorithm in a cell istriggered.


Object : bts

Default value : 4

Type : DP



PE/DCL/DD/0124411–9001–124


rxLevAccessMin Class 3 R13

Description : Minimum signal strength level received by the mobiles forbeing granted access to a cell. The information is sent to MSprior to registering.

As an example, a threshold level of –104 dBm corresponds toan acceptable BER of approximately 10–2 (minimumrecommended value).


Object : bts

Default value : less than –110 dBm

Type : DP


rxLevDLIH Class 3 R14

Description : Maximum interference level in BTS-to-MS direction, beyondwhich an intra cell handover may be triggered




Type : DP




rxLevDLPBGT Class 3 R15 V11

Description : Downlink signal strength threshold above which handoversfor power budget are inhibited

In certain issues, the operator may want to prevent handoverfor power budget in case of the received level in the servingcell is good enough so that a handover would not improve thesituation.

This parameter shall be set such as rxLevDLPBGT ≥lRxLevDLH.

Value range : [less than –110, –110 to –109,..., –49 to –48, morethan –48] dBm


Default value : more than –48

Type : DP


Notes : This parameter shall be disabled by setting it to its defaultvalue: more than –48 (dBm).

This parameter is only available for DCU4 or DRXtransceiver architecture. It shall be disabled for DCU2architecture.

rxLevHreqave Class 3 R16

Description : Number of signal strength measurements performed on aserving cell, used to compute arithmetic strength averages inhandover and power control algorithms

Value range : [1 to 10] number of measurement results


Default value : 8

Type : DP



PE/DCL/DD/0124411–9001–124


rxLevHreqaveBeg Class3 R17 V11

Description : Number of measurement reports on current cell for signalstrength arithmetic average for early handover mechanism

Refer to the rxLevHreqave entry in the Dictionary. Thisparameter is coupled with hoMarginBeg andrxNCellHreqaveBeg use.



Default value : 2

Type : DP


Notes : This parameter shall be set such as rxLevHreqaveBeg ≤rxLevHreqave.This parameter is only available for DCU4 or DRXtransceiver architecture.

rxLevHreqt Class 3 R18

Description : Number of arithmetic averages taken into account to computethe weighted average signal strength in handover and powercontrol algorithms. Each is calculated from rxLevHreqavesignal strength measurements on a serving cell.



Default value : 1

Type : DP

Checks : [C/M]: It is equal to the number of weights inrxLevWtsList (refer to this entry in theDictionary).




rxLevMinCell Class 3 R19

Description : Minimum signal strength level received by MS for beinggranted access to a neighbor cell



Default value : –95 to –94 dBm (GSM 900), –93 to –92 (GSM 1800)

Type : DP


rxLevULIH Class 3 R20

Description : Maximum interference level in MS-to-BTS direction, beyondwhich an intra cell handover may be triggered

Value range : [less than –110, –110 to –109, ... , –49 to –48, morethan –48] dBm, without Uplink Mapping Feature activated.[less than –117, ... , more than –42] dBm, when the UplinkMapping Feature is used.


Feature : Uplink Mapping (TF 876)


Type : DP



PE/DCL/DD/0124411–9001–124


rxLevWtsList Class 3 R21

Description : Values of weights to be used for signal strength weighedaverage

The L1M function first calculates rxLevHreqave arithmeticaverages from raw measurements, and balances rxLevHreqtaverages among those with the weights defined inrxLevWtsList.

Each arithmetic average is partnered with one weight in thelist. Weight/average associations are set in the order which theweights are recorded. The latest computed arithmetic averageis always partnered with the first weight in the list.

Super-average = [∑ (averagei x weighti)] / 100,i = 1 to rxLevHreqt

Value range : [0 to 100] %


Default value : 100

Type : DP

Checks : [M]: The number of weights in the list is equal torxLevHreqt and their sum equals 100.




S

sapi

Description : Service Access Point Indicator that defines the type of LAPDlink use

Value range : [RSL / OML]Object : lapdLink

Type : DP


scannerId

Description : 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 permanentobservation, this parameter must match the reference numberof an mdScanner object.


Type : DP

Checks : [A]: If the request concerns a BSS observation or theOMC–R agent permanent observation, therelated mdScanner object is created.

scannerId

Description : 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 permanentobservation, this parameter must match the reference numberof an mdScanner object.


Type : DP

Checks : [A]: If the request concerns a BSS observation or theOMC–R agent permanent observation, therelated mdScanner object is created.


PE/DCL/DD/0124411–9001–124


sequenceNumber

Description : Trace record identification number

Object : traceFileReady

Type : DP

serial number

Description : 3 fields (geographical scope, message code, update number)which identify a particular message from the source and typeindicated by the Message Identifier and are altered every timethe message with a given Message Identifier is changed

Value range : [geographical scope, message code, update number]

geographical scope. .[immediate cell widenormal PLMN widenormal location area widenormal cell wide]

message code [0 to 1023]. . . . .

differentiate messages from same source and type (sameMessage 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 : 3 fields (geographical scope, message code, update number)which identify a particular message from the source and typeindicated by the Message Identifier and are altered every timethe message with a given Message Identifier is changed

Value range : [geographical scope, message code, update number]

geographical scope. .[immediate cell widenormal PLMN widenormal location area widenormal cell wide]

message code [0 to 1023]. . . . .

differentiate messages from same source and type (sameMessage Identifier)

update number [0 to 15]. . . .

differentiate older and newer versions of the same message

Object : short message – Display broadcast characteristics

Type : DP

session context saving mode V10

Description : Session context saving mode

Value range : [automatic when logout / on user request]


Type : DP

shelfNumber V13

Description : Indicates the position of a module in a shelf

Value range : [0 to 1]Object : atmRm, cc, cem, iem, lsaRc, mms, omu, sw8kRm, tmu, trm.

Type : DP

Feature : AR 1209 – V13.1 – V13.1


PE/DCL/DD/0124411–9001–124


short message

Description : 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 bechanged by the Rename command (see the new name entry inthe Dictionary).

Setting a short message characteristics does not affect thecurrent broadcast of the message. The change will be effectivewhen a new broadcast command is launched.

A short message broadcasting is identified on the OMC–R bya unique serial number assigned by the system whenbroadcasting is initiated (refer to this entry in the Dictionary).

Value range : [case sensitive, 20 characters max]

Object : short message

Type : Id

Checks : C]: The name of a short message is unique to theOMC–R.

[M]: The short message is created.

[D]: The short message is not being broadcast.

sicBoardsInt

Description : State of the BSC chain SIC boards. Each board is identified byits type [SICD / SICX / CCS7] and a number in the type.


working The SIC board was correctly. . . . . . . . . initialized.

fault An error has been detected on the. . . . . . . . . . . . board.

The number of SICX, SICD, and CCS7 boards in a BSCdepends on its hardware architecture. Refer to the bscTypeentry in the Dictionary.


Type : DD




signallingLink

Description : Identifier of a signallingLink object defined with regard to asignallingLinkSet object

Value range : [0 to 2147483646]


Type : Id

Checks : [C]: The number of signaling links controlled by aBSC is limited to maxSigLPerSigLS (staticconfiguration data).

[C/M]: The referenced pcmCircuit object(pcmCircuitId) is assigned to the A interface anddepends on the same transcoder object(transcoderId) as the signallingLink object.

[C/M]: The referenced PCM,TS pair (pcmCircuitId andtimeSlotNumber) is not already assigned to asignallingLink or xtp object dependent on thesame transcoder object, and the time slot is notmapped on the TS used by the OMC channel onthe Ater interface.

[C/M]: If the SS7 link uses PCMA link no.3(pcmCircuitId), the timeSlotNumber is in therange [1 to 27] if the PCM link is an E1 link or inthe range [1 to 20] if the PCM link is a T1 link.Since the last four time slots of that link are notmapped on the Ater interface, they are unusable(refer to the transcoderMatrix entry in theDictionary).


[D]: If the application database of the related BSC isbuilt, the signallingLink object is locked.


[D]: No mdScanner object refers to the signallingLinkobject (no observation is running on that object).


PE/DCL/DD/0124411–9001–124


signallingLinkResState

Description : SS7 channel resource state

Value range : [blocked / inhibited / inhibitedLocal / inhibitedDistant /inhibitedLocalDistant / 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 dialoguebetween MTP2 and MTP3


Type : DD

signallingLinkSet

Description : Identifier of a signallingLinkSet object describing aBSC–MSC link on MSC end

Value range : [0 to 2147483646]


Type : Id

Checks : [C]: The signallingLinkSet object is not created for theparent signallingPoint object.


[D]: The application database of the related BSC hasbeen reset by an Off line reset BDA command.



signallingPoint

Description : Identifier of a signallingPoint object describing a BSC–MSClink on BSC end

Value range : [0 to 2147483646]


Type : Id

Checks : [C]: The signallingPoint object is not created for theparent bsc object.



[D]: The application database of the related BSC hasbeen reset by an Off line reset BDA command.

signallingPointType

Description : Whether the BSC–MSC link acts as an STP (SignalingTransfer Point)

Value range : [STP / noSTP (only value accepted)]Object : signallingPoint

Default value : noSTP

Type : DP

Checks : [C/M]: The only value accepted by the system is“noSTP”.



PE/DCL/DD/0124411–9001–124


signallingTerminalNumber Class 2

Description : Number of the CCS7 port used by an SS7 channel in the BSC= 2 x number of the mother CCS7 board [0 to 1] + port number[0 to 1]

Value range : [0 to 1] (BSC 6000 types 1, 2),[0 to 3] (BSC 6000 types 3, 4, 5),[0 to 1] (BSC 12000 type 1),[0 to 3] (BSC 12000 types 2, 3, 4),[0 to 5] (BSC 12000 type 5).


Type : DP

Checks : [C/M]: The port number is one-of-a-kind to the BSC (aCCS7 port controls one and only one SS7 link).



sigPReserved1 Class 3 S1 V12

Description : Reduction factor used to reduce the BSC capacity, so as toadjust the BSC capacity to the MSC.

Value range : [–32768 to 32767]

Only 0 to 9 values are taken into account.


Feature : BSC capacity control (FM1251.1 – V12)

Default value : 0

Type : DP


Notes : If the sigPReserved1 parameter is set to 0, the number ofRAD_CNX contexts is not reduced, and the BSC capacityis full.

If the sigPReserved1 parameter is set to 9, the number ofRAD_CNX contexts is reduced, and the BSC capacity isreduced by 90%.



sigPReserved2 Class 3 S2 V12


Value range : [–32768 to 32767]Object : signallingPoint

Default value : 0

Type : DP


siteGsmFctList Class 2 S3

Description : List of up to 14 elements that identify the GSM functionsconfigured in a site BCF

Value range : [entityMgt / download / siteMgt / abisSig / abisTraf / rfTrans/ rfRecep / cellMgt / fhMgt / tdmaMgt / tsMgt / gsmTime /car0Fil / freqMgt]

Routing modeThe routing mode of the messages handled by the GSMfunctions, which enables the Abis interface to identify theGSM entity to which the messages are sent, and the maximumresponse time of each GSM function are summarized in thefollowing table.

GSM function Routing mode Response time

Withoutcentralized O&M

With centralizedO&M

GSM entityManagement

relative tei bcf 10 seconds

download ing relative tei relative tei 32 seconds

site Management relative tei bcf 120 seconds

abis SignallingManagement

bcf bcf 120 seconds

abis TrafficManagement

bcf bcf 120 seconds

radio frequencyTransmission

bcf bcf 120 seconds

radio frequencyReception

not implemented none 0 second

cell Management bcf bcf 120 seconds

frequency hoppingManagement

relative tei bcf 30 seconds


PE/DCL/DD/0124411–9001–124


GSM function Response timeRouting mode

With centralizedO&M

Withoutcentralized O&M

tdma Management relative tei bcf 30 seconds

time slot Management relative tei bcf 30 seconds

gsmTime not implemented none 0 second

carrier 0 Filling not implemented none 0 second

frequency Management bcf bcf 120 seconds


Default value : site Mgt/abisSig

Type : DP

Checks : [C/M]: Each function occurs once in the list.

[C/M]: The “entityMgt”, “download”, “tdmaMgt”, and“tsMgt” functions are included in the list.

[C/M]: The “freqMgt” function is only allowed for a BTSusing cavity coupling.

[M]: The “fhMgt” function is included in the list if btsobjects dependent on the btsSiteManager objectare authorized to hop (btsIsHopping ).


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

siteName

Description : Reference name of a radio site on the OMC–R. It begins witha letter and is case sensitive.

The name of a site can be used in all MMI commands toreference the site on the OMC–R.



Type : DP

Checks : [C/M]: The name of a site is unique to the OMC–R.



slc Class 2

Description : Code of an SS7 channel. It is identical on BSC and MSC ends.

Value range : [0 to 15]Object : signallingLink

Type : DP

Checks : [C/M]: The code of an SS7 link is one-of-a-kind to theBSC.


small to large zone HO priority Class 3 V9

Description : External priority of inter-zone handovers from the inner zoneto the outer zone in a concentric cell

This attribute is defined if the associated bts object describesa concentric cell.

Value range : [0 to 17]Object : handOverControl

Default value : 17

Condition : To define if the associated bts object describes a concentric cell

Type : DP


smoke detector Class 2 V9

Description : Presence or absence of the optional equipment “smokedetector” in S4000 Oudoor, S4000 Smart or S8000 Outdoor



Type : DP



PE/DCL/DD/0124411–9001–124


smsCB Class 3

Description : Whether broadcasting of short messages in unacknowledgedmode is authorized in a cell

Value range : [used / unused]

Object : bts


Type : DP

Checks : [M]: The attribute value is “used” if the channelTypeof one of the channel objects dependent on the btsobject is “bcchSdcch4CBCH” or“sdcch8CBCH”.


Remark : Configuration of logical channels and broadcast of shortmessages are managed by two separate OMC–R functions.

When a short message broadcast is started, the presence of aCBCH in the channelType of a channel object dependent ona concerned bts object is checked.

However, the SMS–CB function is not aware of changes madeto that attribute.

Consequently, withdrawing a CBCH from the configurationwill stop any short message broadcast in the concerned cellwithout the SMS–CB function knowing.



software

Description : Identifier of a software object

The software object class allows users to manage the softwarereleases of bsc objects (BSC), btsSiteManager objects (BCF),transceiverEquipment objects (TRX), and transcoderBoardobjects (TCB). Software objects are managed by the OMC–R“Software Management” function.

The software objects have four attributes:sWVersionBackUp, sWVersionFallback, sWVersionNew,and sWVersionRunning. They are managed by the systemaccording to the following user commands: Download,Activate new version, and Return to previous version.

Value range : [0 to 2147483646]Object : software

Type : Id

Checks : Checks common to all software objects:

[C]: The software object is not created for the parentmanaged object.

[C]: The sWVersionRunning attribute is defined(nonzero value).


Additional checks performed on the software-bsc object:

[C]: The sWVersionRunning attribute matches thebscType of the bsc object.

[C/D]: If the application database of the related BSC isbuilt, the bsc object is locked.

[D]: All objects dependent on the bsc object aredeleted.

Additional checks performed on the software-btsSiteManagerobject:

[C/D]: If the application database of the related BSC isbuilt, the parent bsc object is unlocked and thebtsSiteManager object is locked.

[D]: All objects dependent on the btsSiteManagerobject are deleted.


PE/DCL/DD/0124411–9001–124


Additional check performed on thesoftware-transceiverEquipment object:

[C/D]: If the application database of the related BSC isbuilt, the parent bsc object is unlocked, the parentbts object is locked, and the transceiverEquipmentobject is locked.

Additional check performed on the software-transcoderBoardobject:

[C/D]: If the application database of the related BSC isbuilt, the parent bsc object is unlocked and thetranscoderBoard object is locked.

softwareLabel V13

Description : This attribute is a Manager comment about the relatedsoftware. This attribute is modified by the Manager. Valuechanges are notified to the Manager.



Type : DP

source indicator

Description : To select messages according to the source of the operation


Value range : [resource operation / management operation / unknown]


Type : DP

specific problems

Description : To select messages according to a (cause, fault number) pair

This parameter allows to select a fault number with one ormore associated causes. Refer to these entries in theDictionary.



Type : DP



speechMode Class 3 V8

Description : List of the speech algorithms associated with channel usemodes in the cell

The “full rate” value refers to the standard algorithm. The“enhanced full rate” value only applies when all the TCUslinked to the BSC are equipped with TCB2 boards (refer to theversion entry in the Dictionary).

Value range : [full rate / enhanced full rate]

Object : bts


Type : DP

Checks : [C/M]: The “full rate” value is mandatory; it must bedefined in the list.

[C/M]: The “enhanced full rate” value is defined in the listif at least one of the TCUs linked to the BSC isequipped with TCB2 boards.


speechMode Class 3 V8

Description : List of the speech algorithms associated with channel usemodes on the A interface

The “full rate” value refers to the standard algorithm. The“enhanced full rate” value only applies when all the TCUslinked to the BSC are equipped with TCB2 boards.

Value range : [full rate / enhanced full rate]



Type : DP

Checks : [C/M]: The “full rate” value is mandatory; it must bedefined in the list.

[C/M]: The “enhanced full rate” value is defined in the listif at least one of the TCUs linked to the BSC isequipped with TCB2 boards.



PE/DCL/DD/0124411–9001–124


speechOnHoppingTs Class 3 (gprsBtsLockExtendedConf) V12


Value range : [true, false]Object : bts


Type : DP



speechVersionAsscomp Class 1 S4 V12

Description : Whether the “Speech version” element is used or not in theASSIGN COMPLETE messages (Phase II compliance).

Value range : [false / true]Object : signallingPoint


Type : DP


speechVersionHoperf Class 1 S5 V12

Description : Whether the “Speech version” element is used or not in theHANDOVER PERFORMED messages (Phase IIcompliance)


Default value :

Type : DP


speechVersionHoreq Class 1 S6 V12

Description : Whether the “Speech version” element is used in theHANDOVER REQUEST ACKNOWLEDGE messages(Phase II compliance)



Type : DP




speechVersionHorqd Class 1 S7 V12

Description : Whether the “Speech version” element is used or not in theHANDOVER REQUIRED messages (Phase II compliance).




Type : DP


standard indicator AdjC Class 3 S8 V10

Description : Type of network in which this neighbor cell is working

Value range : [gsm / extended gsm / dcs1800 / pcs1900 / R gsm /gsmdcs (V12) / dcsgsm (V12)]

Object : adjacentCellHandover


Default value : gsm

Type : DP


Note : “gsmdcs” and “dcsgsm” are only available for S8000 DRXtransceiver architecture.

standard indicator AdjC Class 3S9 V10

Description : Type of network in which this neighbor cell is working



Default value : gsm

Type : DP





PE/DCL/DD/0124411–9001–124


standardIndicator Class 2 V9

Description : Type of network in which the cell is working

From the value given to this attribute, the OMC–R determinesthe network frequency band and the frequencies that can beused by all radio entities (cells and radio time slots) in therelated site.


Object : bts

Type : DP



GSM 900 network (gsm)

The GSM 900 frequency band is 2*25 MHz wide and includes124 pairs of carrier frequencies, numbered [1 to 124], whichare 200 kHz apart:

Uplink direction (MS–to–BTS) = 890 to 915 MHz

Downlink direction (BTS–to–MS) = 935 to 960 MHz

A frequency N corresponds to the following Uplinkfrequency:

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 frequency band is 2*35 MHz wide andincludes 174 pairs of carrier frequencies, numbered [0 to 124]and [975 to 1023], which are 200 kHz apart:




f1 = 880.2 + 0.2x(N – 975) MHz where N = [975 to 1023]

f1 = 890 + 0.2xN MHz where N = [0 to 124]




f2 = f1 + 45 MHz

Note : The extended GSM frequency band defined hereabove is thedefinition of the ETSI.

GSM–R network (R gsm)

The GSM–R frequency band is 2*39 MHz wide and includes194 pairs of carrier frequencies, numbered [0 to 124] and [955to 1023], which are 200 kHz apart:




f1 = 876.2 + 0.2x(N – 955) MHz where N = [955 to 1023]

f1 = 890 + 0.2xN MHz where N = [0 to 124]


f2 = f1 + 45 MHz

Note : The GSM–R frequency band defined hereabove is thedefinition of the ETSI.

GSM 1800 network (dcs1800)

The GSM 1800 frequency band is 2*75 MHz wide andincludes 374 pairs of carrier frequencies, numbered [512 to885], which are 200 kHz apart:




f1 = 1710.2 + 0.2x(N – 512) MHz where N = [512 to 885]


f2 = f1 + 95 MHz

GSM 1900 network (pcs1900)

The GSM 1900 frequency band is 2*60 MHz wide andincludes 299 pairs of carrier frequencies, numbered [512 to810], which are 200 kHz apart:



PE/DCL/DD/0124411–9001–124




f1 = 1850.2 + 0.2x(N – 512) MHz where N = [512 to 810]


f2 = f1 + 80 MHz

GSM 900 – GSM 1800 network (gsmdcs)

The primary band is GSM 900 (see above GSM 900 Networkparagraph).

The secondary band is GSM 1800 (see above GSM 1800Network paragraph).

GSM 1800 – GSM 900 network (dcsgsm)

The primary band is GSM 1800 (see above GSM 1800Network paragraph).

The secondary band is GSM 900 (see above GSM 900 Networkparagraph).


standbyStatus V13

Description : ISO State

Value range : [hotStandby / coldStandby / providingService]

Object : atmRm, cem, iem, lsaRc, omu, sw8kRm

Type : DD


start date

Description : Date on which data were first recorded in the log (default is thecurrent date)




Type : DP



start time

Description : Absolute time of first job run (default is the current date andtime)

Absolute time format entry forms are detailed inNTP < 130 >.

If date matches the current date, set time to a value at least oneminute after the current time.

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

Type : DP

start time

Description : Start of system log reading on the requested start date (defaultis 00:00)

Time format entry forms are detailed in NTP < 130 >.


Value range : [<time>]


Type : DP


PE/DCL/DD/0124411–9001–124


startAlarmFilter

Description : Condition for triggering an alarm when no counter is involved

The following fields can be combined in the logicalexpression:

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 =

The following logical operators can be used in the logicalexpression:

& stands for the logical AND.

| stands for the logical OR.

! stands for the logical NOT.

The “postMortem” field can take two values, either “beforeBSC restart” or “after BSC restart”. They have the followingmeaning:

before BSC restart means that the notification issued by theBSC was received by the OMC–R agent without the BSChaving restarted (nominal conditions).



after BSC restart means that the notification was issued bythe BSC, then, the BSC was restarted before the OMC–Ragent received the notification. These notifications do nottrigger alarms.

Value range : [logical expression]


Condition : To define if no counter is associated to the criterion.

Type : DP

startAlarmThreshold

Description : Maximum counting value in the reference period, abovewhich a start-of-alarm message is sent. The value must bechecked by users.

This attribute defines a maximum value read at the end of thedefined refPeriod. It must be greater thanendAlarmThreshold.


Value range : [0.00 to 2147483646]


Type : DP

startAlarmThreshold

Description : Minimum (thresholdLow) / maximum (thresholdHigh)counting value in the reference period, below/above which astart of “lower threshold/upper threshold” alarm message issent. The value must be checked by users.

If thesholdType = “thresholdLow”, this attribute defines aminimum value for a one minute reference period (or thecounter collecting period for PCM unavailability counters),below which a start of “lower threshold” alarm message issent. It must be lower than startAlarmThreshold “low”.

If thesholdType = “thresholdHigh”, this attribute defines amaximum value for a one minute reference period (or thecounter collecting period for PCM unavailability counters),above which a start of “upper threshold” alarm message is sent.It must be greater than startAlarmThreshold “high”.



PE/DCL/DD/0124411–9001–124


Value range : [0.00 to 2147483646]

Object : mdWarning if detectionFunction = “outOfRangeCounter”

Type : DP

Remark :

The treshold limits depend on the associated counter.

The BSS counter threshold crossing detection mechanismis described in NTP < 07 >.

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 at which files were restored on the OMC–Ragent disks



Condition : This attribute is significant and displayed only when the logobject describes a log restored on the OMC–R agent disks.

Type : DP

startTime

Description : Date and time at which the temporary observation started

This information is provided by the system and indicates theexact time when the observation counters are collected for thefirst time.



Type : DI



stopTime

Description : Date and time at which the OMC–R agent will purge therestored files

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


Condition : This attribute is significant and displayed only when the logobject describes a log restored on the OMC–R agent disks.

Type : DP

stopTime

Description : Date and time at which the temporary observation will stop



Object : mdScanner – Create temporary observation

Type : DP

Checks : [C]: stopTime – startTime > mdGranularityPeriodminutes

[C]: stopTime – startTime < 1440 minutes (24 hours)

Restrictions : [M]: This attribute cannot be modified. Stop theobservation if necessary by deleting the mdScanner objectand restart it by creating a new mdScanner object with theappropriate attributes.

subChanId

Description : AGCH subchannel number: Do not fill in when thechannelType 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 areunlocked.

Reminder : A BCCH or a CBCH cannot be blocked.


PE/DCL/DD/0124411–9001–124


subject

Description : Identifier (name) of a user message in the OMC–R

It is displayed in the “Inter-user message manager” window ofthe message addressees and allows them to identify themessage before reading.

Value range : [40 characters max]Object : user message

Type : Id

Suffix

Description : Optional string of characters to add to the name of the callmonitoring data files when saved in the OMC–R

When a suffix is defined, a call monitoring data file transferredto the OMC–R by running the Transfer command is savedunder the name “SDO_CM_BSCnnn_<Suffix>.yyyymmdd”,where “nnn” identifies the BSC hosting the data file (if bsc =5, then nnn is read “005”) and “yyyymmdd” is the file savingdate. See to NTP < 07 >.

Value range : [10 characters max]Object : Call monitoring – Transfer (SDO)

Type : DP

summary

Description : Text explaining the goal of the command file


Type : DP



supportingTransceiverEquipment

Description : Identifier of the TRX associated with the TDMA frame by theBSC

This dynamic attribute allows the user to know theTDMA–TRX/DRX association established by the BSC. It isdisplayed provided the transceiver object operationalState is“enabled”. Refer to this entry in the Dictionary.

If the TRX/DRX is declared faulty because of a frequencyloss, the system takes the following actions:

attempt to reconfigure the associated TDMA frame on theredundant TRX/DRX

if there is no redundant TRX/DRX, reconfiguration of theTDMA frame on another TRX/DRX if its priority is higherthan the priority of the TDMA frame currently configured

If the associated TDMA frame cannot be reconfigured forsome reason, all frames that were using the frequency lost bythe TRX/DRX will be disturbed.


Type : DD

Remark : Only BTSs using cavity coupling manage dynamicreconfiguration of hopping frequencies.

sw8kRmId V13

Description : Identifier of the ‘sw8kRm’ object class. This identifier isallocated by the MD–R at object creation, depending on theshelf and slot numbers indicated by the BSC. This attributecannot be modified. This attribute is relevant for BSC e3 andTCU e3.

Value range : [0 to 2147483646]Object : sw8kRm

Type : DP


PE/DCL/DD/0124411–9001–124


sWVersionBackUp

Description : Reference number of the backup software release. It isidentical 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 isupdated following a version change command.


This attribute is undefined when the object is created.

As a result of an Activate new version command, the systemupdates the sWVersionFallBack attribute with the referenceof the software release previously running in the related BSSentity.

As a result of a Return to previous version command, thesystem sets the sWVersionFallBack attribute undefined.


Type : DP

sWVersionNew

Description : Reference number of the new software release. It is updatedfollowing a download or version change command.


This attribute is undefined when the object is created.

As a result of an Activate new version command, the systemsets the sWVersionNew attribute undefined.

As a result of a Download or Return to previous versioncommand, the system updates the sWVersionNew attributewith the reference of the software release downloaded or thatwas presently running in the related BSS entity.


Type : DP



sWVersionRunning

Description : Reference number of the software release currently running.It is defined by the user at object creation time and is updatedfollowing version change commands.

This parameter identifies the type and version of the softwarecurrently running in the related BSS entity. Check the BSSdelivery descriptor file to fill it in when creating the softwareobject.

As a result of an Activate new version or Return to previousversion command, the system updates thesWVersionRunning attribute with the reference of thesoftware release newly activated in the related BSS entity.

The following tables show the reference number formats foreach type of BSS entity driven by software.

BSC software: Format = “BSxabvcdefgh”

Field Meaning Value

BSx Type of software x = [1 .. 3]


v Reserved

cd Sub-version number [01 .. 99]

ef Edition number [01 .. 99]

gh Revision factor [01 .. 99]

BTSs and all TCUs software: Format = “XXXabcdef”

Field Meaning Value

XXX Type of software BCF : BCF/BC1/BC2TRX : TRX/DRXTCB : TCB


c Sub-version number BCF : [A .. H]TRX : [A .. H]TCB : [A .. H]

d Edition number BCF : [1 .. 8]TRX : [1 .. 8]TCB : [1 .. 8]

ef Revision factor BCF : [01 .. 32]TRX : [01 .. 32]TCB : [01 .. 64]


PE/DCL/DD/0124411–9001–124


Value range : [Bsxabvcdefgh (BSC software) / XXXabcdef (others)]

Object : software

Type : DP

Checks : [C]: The attribute is defined (nonzero value).

[C]: The first three letters of the reference numbermatch the type of the managed object related to thesoftware object.

[C]: For a software-bsc object, the version numbercomplies with the bscType of the parent bscobject.

synchronized Class 3 S1S2

Description : Whether the neighbor cell and the associated serving cell aresynchronous, that is attached to the same BTS

Value range : [not synchronized cells / synchronized cells /pre sync HO with timing advance / pre sync HO,default timing advance]

“not synchronized cells”: the neighbor cell and the servingcell are not attached to the same BTS.

“synchronized cells”: the neighbor cell and the serving cellare attached to the same BTS

“pre sync HO with timing advance”: the handoverprocedure between the neighbor cell and the serving cell ispre–synchronized with the GSM Real Time Differencebetween the neighbor cell and the serving cell in the“HANDOVER COMMAND” message

“pre sync HO, default timing advance”: a pre–definedtiming advance is used in the pre–synchronized handoverprocedure between the serving cell and the neighbor cell.Refer to “preSynchroTimingAdvance” parameter.


Default value : not synchronized cells

Type : DP




synchronizing PCM V10

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

syntheticFaultNumber

Description : Synthetic fault number to assign to the alarm when a counteris involved

Value range : [39500 to 39549]Object : alarm criteria

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

system state

Description : State of the configurable BSC boards and state of the traffic tothe MSC

Value range : The following is a list of equipment in alphabetical order:

active – passive link [opened / closed]

bsc [simplex / duplex]. . . . . . . . . . . . .

chain [active / passive]. . . . . . . . . . . .

chain [ready / not ready]. . . . . . . . . . . .

ECI DDTI ALA SWM initialisation [allowed / not allowed]

reset MSCL [in progress / not in progress]. . . . . . .

other chain [ready / not ready]. . . . . . .


Type : DD


PE/DCL/DD/0124411–9001–124


T

t3101 Class 3 T1

Description : BSC timer triggered during the immediate assignmentprocedure. Use the suggested system value.

It is set on transmission of CHANNEL ACTIVATION by theBSC and canceled on receipt of ESTABLISH INDICATIONsent by the BTS.


Object : bts

Default value : 3

Type : DP


t3103 Class 3 T2

Description : BSC timer triggered during the handover procedure. Use thesuggested system value.

It is set on transmission of HANDOVER COMMAND by theBSC and canceled on receipt of either HANDOVERCOMPLETE or HANDOVER FAILURE sent by the MS(intra-bss handover), or CLEAR COMMAND sent by theMSC (inter-bss handover). At expiry of T3103, the channel isreleased.

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 bscobject )




t3107 Class 3 T3

Description : BSC timer triggered during the assignment commandprocedure. Use the suggested system value.

It is set on transmission of ASSIGN COMMAND by the BSCand canceled on receipt of either ASSIGN COMPLETE orASSIGN FAILURE sent by MS.


Object : bts


Type : DP


t3109 Class 3 T4

Description : BSC timer triggered during the SACCH deactivationprocedure. Use the suggested system value.

It is set on receipt of DEACTIVATE SACCHACKNOWLEDGE sent by the BTS and canceled on receiptof RELEASE INDICATION sent by the BTS. If the timerexpires, a RF CHANNEL RELEASE message is sent to theBTS and a RF CHANNEL RELEASE ACK is expected.

Mobiles comply with system operating conditions when thecounter (S) associated with SACCH messages is assigned avalue below or equal to t3109.

Value range : [2 to 255] seconds (t3109 ≥ radioLinkTimeout)Object : bts


Type : DP

Checks : [C/M]: t3109 ≥ radioLinkTimeout



PE/DCL/DD/0124411–9001–124


t3111 Class 3 T5

Description : BSC timer triggered during the radio resource clearingprocedure. Use the suggested system value.

It is set on receipt of RELEASE INDICATION sent by theBTS. On elapse, the BSC sends RF CHANNEL RELEASE.


Object : bts


Type : DP


t3122 Class 3 T6

Description : Minimum time that mobiles must wait before issuing achannel allocation request when an immediate assignment hasfailed.


Object : bts


Type : DP


T3172 Class 3 (gprsBtsExtendedConf) V12

Description : Value of the timer started by the mobile on reception of aPacket Access Reject message (in seconds)


Object : bts


Type : DP

Default value : 5




target Bda V11

Description : Target BDA for the On–line reset command

See to NTP < 130 >.

Value range : [running / new / old]

“running” for “BDA Edition” reset on–line (i.e. basic BDAchange without prototype BDA change)

“new” or “old” for “BDA Version” reset on line (i.e. BSCupgrades with prototype BDA change)

Object : bsc – On–line reset

Type : DP

Note : For a V10 BSC this parameter is not requested for the On–linereset command.

teiBtsSiteManager Class 2

Description : TEI address of the site BCF in the LAPD protocol

In a BTS chain, the TEI addresses must be allocated inascending order (TEI0, TEI1, TEI2, etc.), beginning with theBTS closest to the BSC.

In a BTS loop configuration, the TEI addresses must beallocated in ascending order (TEI0, TEI1, TEI2, etc.),beginning with the BTS directly linked to the BSC that usesDTI board no.0 for the Abis link input.

The following TEI values 3, 7, 11, 15, 19, 23 , and 27 areforbidden when T1 PCMs on Abis interface are used.

The relationship between internal E1 PCM TSs (DTI, PCMIor CPCMI) or BSC (DDTI) and external PCM TSs is thefollowing:

E1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

T1 1 2 3 4 5 6 7 8 9 10 11 12

E1 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

T1 13 14 15 16 17 18 19 20 21 22 23 24

E1 PCM TSs 4, 8, 12, 16, 20, 24, and 28 are not mapped ontoT1 PCM TSs. The scheduled or “rendez–vous” TSs(=teiBtsSiteManager +1) cannot be defined on these internalE1 PCM TSs


PE/DCL/DD/0124411–9001–124



Type : DP

Checks : [C/M]: The number of TEI addresses allotted to a LAPDchannel is limited to maxTeiPerLapdCh (staticconfiguration data).

[M] : The parent bsc object is unlocked and thebtsSiteManager object is locked.

teiLapdLink

Description : TEI address of the LAPD link in the LAPD protocol. It isupdated by the OMC–R agent according to the TEI addressallotted by the user to the entity (BCF, TRX/DRX, TCU)using the LAPD link.

Value range : [0 to 127]Object : lapdLink – Display

Type : DP


teiTransceiverEqpt Class 2

Description : TEI address of the TRX/DRX in the LAPD protocol

For more information on BTS TEI numbering rules, see toNTP < 07 >.

Value range : [32 to 39] (monosectorial site), [32 to 47] (bisectorial site),[32 to 55] (trisectorial site), [32 to 63] (hexasectorial site)


Type : DP

Checks : [C/M]: The number of TEI addresses allotted to a LAPDchannel is limited to maxTeiPerLapdCh (staticconfiguration data).

[C/M]: The TEI address is not assigned to anothertransceiverEquipment object dependent on thesame bts object.

[M]: No mdScanner object refers to thetransceiverEquipment object (no observation isrunning on the TRX/DRX or the parent cell).

[M]: The parent bsc object is unlocked, the parent btsobject and the transceiverEquipment object arelocked.



teiTranscoder Class 2

Description : TEI address of the TCU in the LAPD protocol

Value range : [0 to 126]Object : transcoder

Type : DP

Checks : [C/M]: The TEI address is not assigned to anothertranscoder object dependent on the same bscobject.

[M]: The parent bsc object is unlocked and thetranscoder object is locked.

[C/M]: 0≤ teiTranscoder ≤ 126

temporaryOffset Class 3T7 V8

Description : Negative offset applied during Penalty Time for reselecting acell (C2 criterion)

This negative offset is applied during the entire penaltyTimeduration and allows to prevent speeding mobiles fromselecting the cell. Refer to the cellReselectOffset entry in theDictionary.


Object : bts

Feature : AR 264

Default value : 70

Type : DP


terminal name

Description : Name of a terminal as defined in its profile (default is thelogged-in user’s terminal)


Value range : [case sensitive]Object : System session log – Filter

Type : DP

Checks : [A]: The terminal is known to the OMC–R.


PE/DCL/DD/0124411–9001–124


terminal profile

Description : Identifier (name) of an OMC–R terminal

Value range : [case sensitive, 1 character min]Object : terminal profile

Type : Id

Checks : [C]: The name of a terminal is unique to the OMC–R.

[M/D]: The terminal profile object is created.

text

Description : Comment to display before running the next command

The Echo : text = blah blah blah command can be insertedanywhere in a command file, and as many times as necessary.The text is displayed as it is in session logs when the commandfile 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]Object : short message

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 V9

Description : Presence or absence of the optional equipment “microwaveterminal” in S4000 Outdoor

Value range : [Present / Absent]Object : btsSiteManager

Type : DP




thresholdCCCHLoadIndication Class 3

Description : Threshold used by the BTS to inform the BSC about a CCCHcongestion (104 is the only value accepted)


Object : bts

Type : DP

Checks : [C/M]: The only value accepted by the system is “104”.



thresholdInterference Class 2 T8

Description : List of four thresholds defined in ascending order, used to sortidle channels on the basis of measured interference levels

This attribute, together with the averagingPeriod attribute,allows to manage interferences in a radio cell. Theclassification is used by the radio resource allocator.

The interference processing algorithm for a cell is as follows:

For each idle radio channel, the BTS permanently measuresthe signal strength level RXLEV.

When averagingPeriod “Measurement results” messageshave been received, the L1M function in the BTS calculatesinterference level averages, sorts the idle channelsaccording to the five defined interference levels (Level 0corresponds to the lowest interference level), and sends theinformation to the BSC.


PE/DCL/DD/0124411–9001–124


dBm– 128 0

Level 0 Level 1 Level 2 Level 3 Level 4

– 108 – 106 – 104 – 102

thresholdInterference = 1





radChanSelIntThreshold =1




The BSC tallies the interference levels and, if the temporary“interference” observation is running for the bsc object,sends the channelIdleLevelMax and channelIdleLevelEchcounters every <mdGranularityPeriod> minutes to theOMC–R agent.

Refer also to C1619 permanent observation counters.

Value range : [–128 to 0] dBm


Default value : –100 –90 –80 –70

Type : DP

Checks : [C/M]: The thresholds are defined in ascending order.


thresholdType

Description : Type of thresholds managed

The startAlarmThreshold and endAlarmThresholdattribute values, which trigger permanent BSS observationcounter threshold overflow messages, depend on the type ofthresholds managed by the mdWarning object. Refer to theseentries in the Dictionary.

Value range : [thresholdLow / thresholdHigh]

Object : mdWarning if detectionFunction = “outOfRangeCounter”

Type : DP



timeBetweenHOConfiguration Class 3 T9 V9

Description : Whether the HOPingpongTimeRejection timer can be usedin a BSS when processing handovers

Refer to bts object bts time between HO configuration andadjacentCellHandOver object HOPingpongTimeRejectionattributes in this Dictionary of Parameters.

Value range : [used / not used]Object : bsc

Feature : General protection against pingpong handovers(TF821 – V12)


Type : DP


timerPeriodicUpdateMS Class 3 T10

Description : Time between two location update requests

Value range : [0 to 255] 1/10th of hour. “0” means that no periodic locationupdate is requested.

Object : bts

Default value : 60

Type : DP


Remark : The operator must be aware that the input of low values for thisattribute causes an important traffic load during the locationupdate procedures. For instance, entering the value “1” forthis attribute leads to that all Mobiles will execute an updateof their LAC every 6 minutes.

timeSlotNumber

Description : PCM time slot used by a LAPD link

Since all radio sites house a switching facility, the BSC candirectly map the LAPD link onto a PCM time slot.

Value range : [1 to 24] (GSM 1900 network)[1 to 31] (other networks)

Object : lapdLink

Type : DD

Remark : The LAPD link with a radio site BCF always uses TSn =pcmTimeSlotNumber (radio site scheduled time slot). Referto this entry in the Dictionary.


PE/DCL/DD/0124411–9001–124


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 Ainterface to a signallingLink or xtp objectdependent on the same bsc object and is notmapped on the TS used by the OMC channel onthe Ater interface.

[C/M]: If the SS7 link uses PCMA link no.3(pcmCircuitId), the time slot is in the range[1 to 27] if the PCM link is an E1 link or in therange [1 to 20] if the PCM link is a T1 link. Sincethe last four time slots of that link are not mappedon the Ater interface, they are unusable (refer tothe transcoderMatrix entry in the Dictionary).


timeSlotNumber

Description : PCM time slot used by a terrestrial circuit on the A interface


Object : xtp

Type : DP

Checks : [C]: The time slot is identical to the mscPcmTsNumbercomponent of the xtp object cic attribute (refer tothis entry in the Dictionary).

[C]: The time slot is not already assigned on the Ainterface to an xtp or signallingLink objectdependent on the same bsc object, and is notmapped on the TS used by the OMC channel onthe Ater interface.



[C]: If the terrestrial circuit uses PCMA link no.3(pcmCircuitId), the time slot is in the range[1 to 27] if the PCM link is an E1 link or in therange [1 to 20] if the PCM link is a T1 link. Sincethe last four time slots of that link are not mappedon the Ater interface, they are unusable (refer tothe transcoderMatrix entry in the Dictionary).

Restrictions : [M]: This attribute cannot be modified due to itsrelationship with the mscPcmTsNumber component of thecic attribute.

tmuId V13

Description : Identifier of the ‘tmu’ object class. This identifier is allocatedby the MD–R at object creation, depending on the shelf andslot numbers indicated by the BSC. This attribute cannot bemodified. This attribute is relevant for BSC e3 and TCU e3.

Value range : [0 to 2147483646]Object : tmu

Type : DP

traceConstraintList

Description : List of logical expressions that allow to filter the informationto display. The following filter criteria are used: [bsPower /bssTraceType / bssTraceTypeUsed / establishmentCause /hoCauseClass / hoClauseValue / hoRrResult / mobileId /msPower / pcm / recordingEntity / rrCause / timeSlot /timingAdvance / tracedBts / traceRecId / traceReferenceCrit/ trStartTime / trStopTime. / trxIdrxId]

See to NTP < 130 >.


Type : DP


PE/DCL/DD/0124411–9001–124


traceControl V8

Description : Identifier of a traceControl object defined with regard to themd object

It describes the Call tracing function of a BSC.

A traceControl object is created in locked state. Unlock theobjet to start collecting data in the related BSC.

Value range : [0 to 2147483646]


Type : Id

Checks : [C]: The traceControl object is not created for the mdobject.

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

[C/M/D]: If the application database of the related BSC isbuilt, the BSS/OMC–R link is established and noaudit is in-progress in the BSC.

[M/D]: The traceControl object is created.

traceDayAccessed

Description : Date of data recording


Setting this parameter limits the display to trace data recordedon the specified day.



Type : DP

traceFileName

Description : Name of a call tracing or call path tracing data file on theOMC–R agent disks. The naming rules are described inNTP < 07 >.

Object : traceFileReadyRecord

Type : DP



traceInfoRequested

Description : List of information to display with respect to the type

See to NTP < 129 >.

Value range : [abisInfo / bsicInfo / bssMapInfo / btsInfo / ChannelInfo /cicInfo / dtapInfo / handoverInfo / manufacturerExtInfo Aand Ater / manufacturerExtInfo Abis / measurementInfo /msClassmarkInfo / powerControlInfo / 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

traffic PCM allocation priority Class 2 T11 V9

Description : Allocation priority of a TDMA frame on the covering sitePCMs

This attribute is used in case of Abis PCM reconfiguration.


Type : DP

Checks : [M]: The parent bsc object is unlocked and the parentbts object is locked.

Note : “0” should be assigned to the highest priority frame(s).

transcdBReserved1 Class 3 T12 V12


Value range : [–32768 to 32767]Type : DP


Default value : 0



PE/DCL/DD/0124411–9001–124


transcdBReserved2 Class 3 T13 V12


Value range : [–32768 to 32767]

Type : DP


Default value : 0


transceiver

Description : Identifier of a transceiver object defined with regard to a btsobject

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 btsobject

By definition, a TDMA frame is related to a cell, a cell isrelated to a site, and a site is related to a BSC.

In all MMI commands, a transceiver object can be referred toby the sequence “siteName.cellName.transceiver”, wheresiteName and cellName respectively identify the coveringsite and cell by name.

A TDMA frame is brought in service on the network atcreation time. It is working when the parent bts object isunlocked.



Type : Id



Checks : [C]: The maximum number of TDMA framescontrolled by a BSC depends on its type andhardware version, as shown in the followingtable:

BSC 12000/6000T1 T2 T3 T4 T5

120 120 160 160 160

[C]: The number of TDMA frames per cell is limitedto 16, regardless of the type of the BSC thatcontrols the cell.

[C]: The handOverControl and powerControl objectsare created for the parent bts object.

[C]: If the parent bts object describes a concentric cell,two transceiverZone objects are created for thatobject.

[C/D]: If the application database of the related BSC isbuilt, the parent bsc object is unlocked and theparent bts object is locked.


transceiver equipment class Class 2 V9

Description : Class of a TRX/DRX

The class of a TRX/DRX sets, among others, its maximumtransmission power. The attribute possible values have thefollowing meaning:

Class 1 corresponds to GSM 900 class 5 or GSM 1800/1900class 1 (20W to 40W transmitters).

Class 2 corresponds to GSM 900 class 6 which is notsupported or GSM 1800/1900 class 2 (10W to 20Wtransmitters).


PE/DCL/DD/0124411–9001–124


Value range : [0 (reserved) / 1 / 2]


Type : DP

Checks : [M]: Concentric cell: If the TRX/DRX is partneredwith a TDMA frame, its class matches theTRX/DRX class allotted to the zone to which theTDMA frame belongs (refer to the next entry).

[M]: The parent bsc object is unlocked and thetransceiverEquipment object is locked.

transceiver equipment class V9

Description : Class of the TRX/DRXs partnered with the TDMA frames ofthe zone

The class of a TRX/DRX sets, among others, its maximumtransmission power. Refer to the previous entry.

Value range : [1 / 2]

Object : transceiverZone

Type : DP


Note : The transceiverZone objects are only created for bts objectsthat describe concentric cells.

transceiver zone Ref Class 2 V9

Description : Identifier of the transceiverZone object that defines the zoneto which a TDMA frame belongs in a concentric cell

Value range : [0 (large or outer zone) / 1 (small or inner zone)]


Condition : To define if the covering cell is concentric

Type : DP

Checks : [C]: The referenced transceiverZone object is createdfor the parent bts object.




transceiverEquipment

Description : Identifier of a transceiverEquipment object defined withregard to a bts object

It defines the related transceiverEquipment object.


Object : software

Type : Id

Checks : [C]: The transceiverEquipment object is created.

transceiverEquipment

Description : Identifier of a transceiverEquipment object defined withregard to a bts object

By definition, a TRX/DRX is related to a cell, a cell is relatedto a site, and a site is related to a BSC.

In all MMI commands, a transceiverEquipment object can bereferred to by the sequence“siteName.cellName.transceiverEquipment”, wheresiteName and cellName respectively identify the coveringsite and cell by name.



Type : Id

Checks : [C]: The number of TRX/DRXs per site is limited to24, regardless of the type of the BSC that controlsthe site.

[C]: The number of TRX/DRXs per cell is limited to16, regardless of the type of the BSC that controlsthe cell.

[C]: The handOverControl and powerControl objectsare created for the parent bts object.

[C]: The referenced lapdLink objects(lapdLinkOMLRef and lapdLinkRSLRef) arecreated for the parent bsc object.

[C]: If the application database of the related BSC isbuilt, the parent bsc object is unlocked and theparent bts object is locked.


PE/DCL/DD/0124411–9001–124


[D]: If the application database of the related BSC isbuilt, the parent bsc object is unlocked, the parentbtsSiteManager and bts objects are locked, and thetransceiverEquipment object is locked.


[D]: No traceControl or callPathTrace object refers tothe transceiverEquipment object (the BSC Calltracing or Call path tracing function does notmonitor that object).

transceiverZone V9

Description : Identifier of a transceiverZone object that describes the largezone or the small zone of a concentric cell

The transceiverZone objects are only significant for the btsobjects that describe concentric cells. Two transceiverZoneobjects are created for each created concentric bts object; onedescribes the large or outer transmission zone, and the otherdescribes the small or inner transmission zone.

Value range : [0 (large or outer zone) / 1 (small or inner zone)]


Type : Id

Checks : [C]: The associated bts object is created and thetransceiverZone object is not created for thatobject.

[C]: The number of transmission zones in a concentriccell equals 2. Each transceiverZone object isone-of-a-kind to the associated bts object.




[D]: No transceiver object refers to thetransceiverZone object.



transcoder2GEqptId V13

Description : Identifier of the ‘transcoder2GEqpt’ object class. Thisidentifier is allocated by the MD–R at object creation. Theonly value allocated by the MD–R is 0. This attribute cannotbe modified. This attribute is relevant for TCU 2G.



Type : DP

transcoder3GEqptId V13

Description : Identifier of the ‘transcoder3GEqpt’ object class. Thisidentifier is allocated by the MD–R at object creation. Theonly value allocated by the MD–R is 0. This attribute cannotbe modified. This attribute is relevant for TCU e3.



Type : DP

transcoder

Description : Identifier of a transcoder object defined with regard to a bscobject

It defines the parent transcoder object.

Value range : [0 to 6] (BSC 6000, E1 PCM network),[0 to 8] (BSC 6000, T1 PCM network),[0 to 11] (BSC 12000, E1 PCM network),[0 to 13] (BSC 12000, T1 PCM network).

Object : pcmCircuit (A interface)

Type : Id

Checks : [C]: The transcoder object is created.


PE/DCL/DD/0124411–9001–124


transcoder


Value range : [0 to 6] (BSC 6000, E1 PCM network),[0 to 8] (BSC 6000, T1 PCM network),[0 to 11] (BSC 12000, E1 PCM network),[0 to 13] (BSC 12000, T1 PCM network)[0 to 33] (BSC 30000, E1 PCM network)[0 to 33] (BSC 30000, T1 PCM network).

Object : transcoder

Type : Id

Checks : [C]: The number of remote transcoders linked to a BSCis limited to maxTranscdPerBsc (staticconfiguration data).


[C]: The referenced lapdLink object(lapdLinkOMLRef) is created for the parent bscobject.


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


transcoder


It defines the parent transcoder object.

Value range : [0 to 6] (BSC 6000, E1 PCM network),[0 to 8] (BSC 6000, T1 PCM network),[0 to 11] (BSC 12000, E1 PCM network),[0 to 13] (BSC 12000, T1 PCM network).


Type : Id

Checks : [C]: The transcoder object is created.



transcoderAlarmList V13

Description : This attribute is relevant only for BSC 2G. Activation state ofthe internal alarm loops of the transcoder. The manager mayeither display it (in French) without previous decoding, ordecode provided raw data for displaying in English. Thisattribute is dynamically managed by the BSS. Value changesare not notified to the Manager.

Value range : [KO/OK]Object : transcoder2GEqpt

Type : DP

transcoderAlarmMask Class 3

Description : Configuration of external alarms in a TCU [xx]: The externalalarm loop is monitored (not monitored) when bit 0 is set to1 (0), bit 1 indicates whether operating anomalies of the TCUexternal clock are notified (1) or not (0) to the OMC–R.

Object : transcoder

Default value : 11

Type : DP




PE/DCL/DD/0124411–9001–124


transcoderBoard

Description : Identifier of a transcoderBoard object defined with regard toa transcoder object



Type : Id

Checks : [C]: The number of transcoding boards housed in aTCU is limited to maxTranscdBPerTranscd(static configuration data).


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


transcoderBoard

Description : Identifier of a transcoderBoard object defined with regard toa transcoder object

It defines the related transcoderBoard object.


Object : software-transcoderBoard

Type : Id

Checks : [C]: The transcoderBoard object is created.

transcoderBoardIntState

Description : TCB internal state


working The board is working.. . . . . . . . .

fault An error was detected on the board.. . . . . . . . . . . .


Type : DD



transcoderId Class 2

Description : Identifier of the remote transcoder linked to the PCM link thatcarries the SS7 channel on the A interface



Type : DP

Checks : [C/M]: The referenced transcoder object is created and thepcmCircuit object used by the signallingLinkobject (pcmCircuitId) is related to that object.


transcoderId Class 2

Description : Identifier of the remote transcoder linked to the PCM link thatcarries the terrestrial circuit on the A interface


Object : xtp

Type : DP

Checks : [C/M]: The referenced transcoder object is created and thepcmCircuit object used by the xtp object(pcmCircuitId) is related to that object.

[M]: The parent bsc object is unlocked and the xtpobject is locked.

transcoderIntPcmIntState

Description : State of the TCU internal PCM links. Each link is identifiedby a serial number n = [0 to 15].

Value range : [0 to 15] [working / fault]

working The internal PCM is working.. . . . . . . . .

fault An error was detected on the PCM. . . . . . . . . . . . link.

Object : transcoder

Type : DD



PE/DCL/DD/0124411–9001–124


transcoderMatrix

Description : Configuration of the TCU switching matrix = mapping PCMAter TS <=> PCM A TS

This attribute describes the relation between the TSs of thefour PCM A links used by the TCU (A interface) and the TSsof the PCM Ater link used by the TCU (Ater interface). Thefollowing tables show the correspondence when PCM E1 orT1 links are used.

Object : transcoder – Display

Type : DP


PCM E1 links

TS PCMAter

PCM A TS PCM A

1 (LAPDchannel)

– no equivalence

23456789

00000000

1 2 3 45 6 7 89 10 11 1213 14 15 1617 18 19 2021 22 23 2425 26 27 2829 30 31

91011121314151617

111111111

12 3 4 56 7 8 910 11 12 1314 15 16 1718 19 20 2122 23 24 2526 27 28 2930 31



TS PCMAter

TS PCM APCM A

171819202122232425

222222222

1 23 4 5 67 8 9 1011 12 13 1415 16 17 1819 20 21 2223 24 25 2627 28 29 3031

25262728293031–

33333333

1 2 34 5 6 78 9 10 1112 13 14 1516 17 18 1920 21 22 2324 25 26 2728 29 30 31

PCM T1 links

TS PCMAter

PCM A TS PCM A

1 (LAPDchannel)

– no equivalence

234567

000000

1 2 3 45 6 7 89 10 11 1213 14 15 1617 18 19 2021 22 23 24

89

10111213

111111

1 2 3 45 6 7 89 10 11 1213 14 15 1617 18 19 2021 22 23 24


PE/DCL/DD/0124411–9001–124


TS PCMAter

TS PCM APCM A

141516171819

222222

1 2 3 45 6 7 89 10 11 1213 14 15 1617 18 19 2021 22 23 24

2021222324–

333333

1 2 3 45 6 7 89 10 11 1213 14 15 1617 18 19 2021 22 23 24

transcvEReserved1 Class 3 T14 V12


Value range : [–32768 to 32767]


Type : DP


transcvEReserved2 Class 3 T15 V12


Value range : [–32768 to 32767]


Type : DP


trmId V13

Description : Identifier of the ‘trm’ object class. This identifier is allocatedby the MD–R at object creation, depending on the shelf andslot numbers indicated by the BSC. This attribute cannot bemodified. This attribute is relevant for BSC e3 and TCU e3.

Value range : [0 to 2147483646]

Object : trm

Type : DP



tSCBNumber V13

Description : This attribute is significant only for BSC 2G. This attributeindicates which is the number of the TSCB (TranscoderSignalling Concentration Board) board, managing thesignalling for transcoders, and the number of the BSCB (BTSsignalling Concentration Board) board, managing thesignalling for BTS. This board is redundant at BSC level.


Type : DP

tSCBUse V13

Description : This attribute is significant only for BSC 2G. xSCB BoardsUse: indicates the internal state and LAPD mapping for eachcreated TSCB and BSCB board. This attribute is dynamicallymanaged by the BSS. Value changes are notified to theManager.


Object : bsc2GEqpt

Type : DP

tsConfiguration V8

Description : Configuration of the radio TDMA frame time slots

This dynamic attribute indicates, for each time slot, thereconfiguration state, the type of logical channel supported,the frequency channel used (absoluteRFChannelNo) if thetime slot does not hop, the list of frequency channels used(mobileAllocation), the maio, and thehoppingSequenceNumber if the time slot hops.


PE/DCL/DD/0124411–9001–124


When frequency hopping is used if “reconfiguration state” is“true“, it means that BSC has recalculated the frequencyhopping law following the loss of one or several TRX (defenceof TDMA carrying the BCCH. If “reconfiguration state” is“false”, it means that the TDMA configuration is the originalone.

When frequency hopping is not used, this boolean has nomeaning and would be set to “false”.

Value range : [true / false]Object : transceiver

Type : DD

Remark : Since the time slots are reconfigured after each dynamicreconfiguration of the hopping frequencies, the data can bedifferent from those defined by the user when creating thechannel objects.

txPowerMaxReduction Class 2

Description : Maximum transmission power level allowed in a TDMAframe (attenuation versus bsTxPowerMax) per transceiver

Value range : [0 to 30 by step of 2] dB. “0” is the only value accepted.


Default value : 0

Type : DP

Checks :

[C/M]: The only value accepted by the system is 0 dB.

[M]: The parent bsc object is unlocked and thetransceiver object is locked.




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 theOMC–R agent disks.

Observation data are stored in the “/MD/obs” partition onthe OMC–R agent disks.

Trace data are stored in the “/MD/trace_function” partitionon the OMC–R agent disks.

Backup data are stored on the OMC–R agent disks.

Other data files are defined in the “/MD/config” partitionon the OMC–R agent disks.

Object : md – Archive

Type : DP

type



Fault data are restored to the “/MD/restored/notif” partitionon 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–Ragent disks.

Other data files are restored to their source directory on theOMC–R agent disks.

Object : md – Restore

Type : DP


PE/DCL/DD/0124411–9001–124


type



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 onthe 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 onthe OMC–R manager disks.

Object : omc – Archive

Type : DP

type



Fault data are restored to the “/CMN/base/save_rest”partition on the OMC–R manager disks.

Observation data are restored to the “/OMC/obs” partitionon the OMC–R manager disks.

Trace data are restored to the “/CMN/base/save_rest”partition on the OMC–R manager disks.

Other data files are restored to their source directory“/OMC/data” on the manager disks.

Object : omc – Restore

Type : DP



type V11

Description : Type of observation report

Value range : [single observed instance / several observed instance]

single observed instance .several observed. . . . . . . counters on a singleobject

several observed instance single counter. . . . . . . observed on severalobjects


Type : DP

Type of data to be purged V10

Description : Type of the OMC data to be purged

Value range : [traceData]

Object : omc – Data purge

Type : DP

Type of display V11

Description : Choice of the observation counter display mode

Value range : [Chart / Table / Text]Object : report template

Type : DP


PE/DCL/DD/0124411–9001–124


U

unequippedCircuit Class 1 V8

Description : Whether the UNEQUIPPED CIRCUIT messages are used(Phase II compliance)



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


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 inV10 and V11, changing it has no meaning.

unknownNCellWarning Class 3

Description : Whether feedback of measurements performed by mobiles onneighbor cells that are unknown to the BSC is allowed

When feedback of measurements is enabled, notificationswith codano 1260 are generated. These notifications indicatethat measurements are performed on cells which use the sameBCCH as a neigbor cell of the serving cell but have differentBSICs.


Object : bts


Type : DP




unmasked users alarms Class 2 V9

Description : Configuration of the user (unprotected) external alarm loopscontrolled by the BTS. When an alarm is unmasked, it meansthe relevant equipment is monitored by the BTS. There are 6user alarms per cabinet

on the S8000 Outdoor (up to 18 user alarms = 3 cabinets * 6user alarms per cabinet).

on the S8002 BTS (up to 6 user alarms = 1 cabinet * 6 useralarms)

A user alarm is used when an external equipment is insertedin the BTS (for instance a microwave terminal) and does notrequire a new DLU.

Value range : [All masked, Base 1, Base 1 to 2, Base 1 to 3, Base 1 to 4, Base1 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 Ext01 to 5, Base 1 to 6 Ext0 1 to 6, Base 1 to 6 Ext0 1 to 6 Ext1 1to 2, Base 1 to 6 Ext0 1 to 6 Ext1 1 to 4, Base 1 to 6 Ext0 1 to6 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 Basecabinet are unmasked

Base 1 to 6 Ext0 1: The 6 user alarms in the Base cabinet andthe first one in the Extension cabinet 0 are unmasked


Type : DP


upAckTime Class3 (packetAckTime) V12

Description : Time defining the period for the acknowledgments for ULtransfers

Value range : [1 to 64] steps 100 ms for uplink transfer (step size is500 msec)


Feature : GPRS (SV407 – V12 and TF1220 – V12.4c)

Type : DP



PE/DCL/DD/0124411–9001–124


upgradeStatus V13

Description : Stands whether an upgrade has currently been performed, isstill in progress or not.


Value changes are notified to the manager.

Value range : [notInProgress / inProgress / performed]

Object : atmRm, cc, cem, iem, omu, sw8kRm, tmu, trm.

Type : DD


uplinkMappingChannelNumber Class 2 U1 V12

Description : Channel number used for uplink mapping as the monitored TS


Object : bts

Default value : 7

Type : DP

Feature : Uplink mapping (TF876 – V12)


[C/M]: The attribute must contain an even value in case ofan extended cell (2, 4, 6). In case of a multi CCCHcell it must contain an odd value (1, 3, 5, 7).

uplinkMappingFreq Class 2 U2 V12

Description : Frequency (f0) used for uplink mapping


Object : bts

Default value : 0

Type : DP





uplinkMappingMeasurementMode

Description : This attribute is relevant from V11 BTS.

This attribute indicates if the uplink mapping is active (TRUE)or inactive (FALSE) on the BTS.

Once active BTS sends collected data to BSC.


This attribute can be modified only if the ‘bts’ object instanceis locked.

This attribute can be modified only if the ‘bsc’object instanceis unlocked.


Type : DP

uplinkMappingProcessingMode Class 3 U3 V12

Description : Whether uplink mapping is active on the BSC or not


Object : bsc


Type : DP



uplinkPowerControl Class 3U4 V8

Description : Whether power control in the MS-to-BTS direction isauthorized at cell level




Type : DP



PE/DCL/DD/0124411–9001–124


uRxLevDLP Class 3 U5

Description : Upper strength threshold for BTS txpwr decrease for step bystep algorithm

It is greater than lRxLevDLP.




Type : DP

Checks : [M]: lRxLevDLP + powerIncrStepSize ≤ uRxLevDLP

[M]: uRxLevDLP – powerRedStepSize ≥ lRxLevDLP



uRxLevULP Class 3 U6

Description : Upper strength threshold for MS txpwr decrease for step bystep algorithm

It is greater than lRxLevULP.




Type : DP

Checks : [M]: lRxLevULP + powerIncrStepSize ≤ uRxLevULP

[M]: uRxLevULP – powerRedStepSize ≥ lRxLevULP





uRxQualDLP Class 3 U7

Description : Upper quality threshold to reduce BTS txpwr for step by stepalgorithm

It is lower than or equal to lRxQualDLP.




Type : DP

Checks : [M]: uRxQualDLP ≤ lRxQualDLP



uRxQualULP Class 3 U8

Description : Upper quality threshold to reduce MS txpwr for step by stepalgorithm

It is lower than or equal to lRxQualULP.




Type : DP

Checks : [M]: uRxQualULP ≤ lRxQualULP




PE/DCL/DD/0124411–9001–124


usageState

Description : Activity state of the Call path tracing function in the BSC

Refer to the endSessionCriteriaType entry in the Dictionaryand the operationalState entry related to the callPathTraceobject which describes the possible state parametercombinations 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 working andcarrying traffic.


Type : DD

��


Refer to the operationalState entry related to the xtp objectwhich describes the possible state parameter combinations forthis 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 working andcarrying traffic.

active The PCM time slot that conveys the. . . . . . . . . . . terrestrial circuit is active.

Object : xtp

Type : DD

use default list V11

Description : Whether default counter list has to be used

Value range : [yes]Object : bscCounterList

Type : DP



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 theOMC–R.

user profile

Description : Identifier (name) of an OMC–R user

Value range : [case sensitive, 2 characters min]


Type : Id

Checks : [C]: The name of a user is one-of-a-kind to theOMC–R.

[M/D]: The user profile object is created.

username

Description : Name of the OMC–R user, as defined in the user’s profile, whocreated the job


Object : job

Type : DD

username

Description : Name of the OMC–R user, as defined in the user’s profile, whocreated the associated job


Object : jobResult

Type : DD


PE/DCL/DD/0124411–9001–124


V

version Class 2 V8

Description : Version number of the remote transcoder TCBs

Version 1 TCB software only manages the FR (Full Rate)service.Version 2 TCB software manages both FR and EFR(Enhanced Full Rate) services.

The following apply:

All TCBs in a given TCU are the same version.

All TCUs in a BSS must be equipped with Version 2 TCBsfor the EFR service to be provided.

Value range : [TCB_1 / TCB_2]Object : transcoder

Default value : TCB_2

Type : DP

Checks : [M]: The attribute value is “TCB_2” if thespeechMode attribute of the dependenttranscoderBoard objects contains “enhanced fullrate”.

[M]: The parent bsc object is unlocked and thetranscoder object is locked.

voiceBroadcastService Class 3 V1 V12

Description : Authorize Voice Broadcast Service

Value range : [enabled / disabled]Object : signallingPoint


Type : DP


voiceGroupCallService Class 3 V2 V12

Description : Authorize Voice Group Call Service

Value range : [enabled / disabled]Object : signallingPoint


Type : DP




VSWR meter Class 2 V9

Description : Presence or absence of the optional equipment “voltagestationary wave rate meter” in S8000 Indoor or Outdoor



Type : DP



PE/DCL/DD/0124411–9001–124


W

workstation name

Description : Name of a workstation as defined in its profile (default is thelogged-in user’s workstation)


Object : omc – Display workstation markers

Type : DP

Checks : [A]: The terminal profile object describing theworkstation is created on the OMC–R.



X

X25Port0Operational V13

Description : Operational State of the OMU module external X.25 port 0.



Value changes are not notified to the Manager.



Object : omu

Type : DD


X25Port1Operational V13

Description : Operational State of the OMU module external X.25 port 1.

ISO operational state (enabled/ disabled).




Object : omu

Type : DD



PE/DCL/DD/0124411–9001–124


xSCBConfiguration Class 0 V8

Description : Number of TSCBs and BSCBs that concentrate LAPDsignaling in the BSC

The TSCBs are used for TCU signaling on the Ater interface.The BSCBs are used for BTS signaling on the Abis interface.

A BSC which manages BTS LAPD signaling concentrationcan control up to 138 radio sites with redundancy, or 147 radiosites without redundancy.

When a BSC does not manage BTS LAPD signalingconcentration, the number of radio sites it controls is limitedto the number of SICD ports available, minus 1 (which isreserved for TCU LAPD signaling), that is 39 sites.


Default value : 2

Type : DP

Checks : [M]: The application database of the parent bsc is notbuilt (bdaState = “not built”).

xSCBNumber

Description : Number of the TSCB that concentrates TCU LAPD signalingin the BSC

This dynamic attribute is managed by the BSC.


Type : DD


xSCBUse V8

Description : State and assignment of the BSC TSCBs and BSCBs

This dynamic attribute indicates, for each TSCB and BSCBhoused in the BSC, its operational state and the list of theLAPD links it concentrates.

Value range : [working / fault]Object : bsc

Type : DD



xtp

Description : Identifier of an xtp object (eXchange Termination Point)defined with regard to a bsc object

Value range : [0 to 2147483646]Object : xtp

Type : Id

Checks : [C]: The number of terrestrial circuits linked to a BSC12000 (BSC 6000) is limited to 1288 (840) ifPCM E1 links are used and to 1440 (828) if PCMT1 links are used. The number of terrestrialcircuits linked to a BSC 2000 is limited to 360.

[C]: The software object related to the bsc object iscreated.

[C/M]: The referenced pcmCircuit object(pcmCircuitId) is assigned to the A interface anddepends on the same transcoder object(transcoderId) as the xtp object.

[C]: The time slot used by the xtp object(timeSlotNumber) is identical to themscPcmTsNumber component of the cic attribute.

[C/M]: The referenced PCM,TS pair (pcmCircuitId andtimeSlotNumber) is not already assigned to anxtp or signallingLink object dependent on thesame transcoder object, and the time slot is notmapped on the TS used by the OMC channel onthe Ater interface.

[C/M]: If the terrestrial circuit uses PCMA link no.3(pcmCircuitId), the timeSlotNumber is in therange [1 to 27] if the PCM link is an E1 link or inthe range [1 to 20] if the PCM link is a T1 link.Since the last four time slots of that link are notmapped on the Ater interface, they are unusable(refer to the transcoderMatrix entry in theDictionary).


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


PE/DCL/DD/0124411–9001–124



[D]: No traceControl or callPathTrace object refers tothe xtp object (the Call tracing and Call pathtracing functions do not monitor that object).

Restrictions : [M]: The cic and timeSlotNumber attributes of an xtpobject cannot be modified.



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, fillin the list as follows:

The Add button allows to add a BSC to the list.

The Delete button allows to remove selected BSCs fromthe list.

A BSS terminal zone of interest allows users to filter theunsolicited messages (output domain) that can be output onthe terminal outside users’ work sessions according to theBSS entities that send them.

Object : terminal profile

Type : DP

Note : The user can enter a BSC in the list that is not created yet. Whenit is created, this BSC will be handle as the other BSCs alreadycreated.

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, fillin the list as follows:

The Add button allows to add a BSC to the list.

The Delete button allows to remove selected BSCs fromthe list.

A BSS user’s zone of interest defines the BSS entities theuser is entitled to work on. It allows to filter both the MMIcommands they can enter (command domain) according tothe objects managed by these commands and theunsolicited messages (output domain) they have access toaccording to the BSS entities that send them.


Type : DP

Note : The user can enter a BSC in the list that is not created yet. Whenit is created, this BSC will be handle as the other BSCs alreadycreated.


PE/DCL/DD/0124411–9001–124


ZI omc

Description : Whether output of unsolicited messages issued by theOMC–R applications to a terminal is allowed when no useris logged in

Value range : [OMC included / OMC excluded]Object : terminal profile

Type : DP

ZI omc

Description : Whether user access to unsolicited messages issued by theOMC–R applications is granted

Value range : [OMC included / OMC excluded]Object : user profile

Type : DP

zone frequency hopping Class 2 V9

Description : Whether frequency hopping is authorised in the zone

If frequency hopping is not allowed in a zone, the channelobjects that describe the radio time slots of the TDMA framesused in the zone cannot be allowed to hop.

Value range : [hopping / not hopping]Object : transceiverZone

Default value : not hopping

Type : DP



zone frequency threshold Class 2 V9

Description : Minimum number of frequencies needed to allow frequencyreconfiguration in the zone

Value range : [1 to 64]Object : transceiverZone

Default value : 1

Type : DP





zone Tx power max reduction Class 2 Z1 V9

Description : Attenuation vs bsTxPowerMax that defines the maximumTRX/DRX transmission power in the zone

Value range : large zone = [0] dB, small zone = [1 to 55] dB


Default value : 0

Type : DP

Checks :

[C/M]: zone Tx power max reduction equals zero if thetransceiverZone object describes the cell outerzone. It is greater than zero if the transceiverZoneobject describes the cell inner zone.




PE/DCL/DD/0124411–9001–124



Objects and parameters evolutionNortel Networks Confidential 3–1


APPENDIX A OBJECTS AND PARAMETERSEVOLUTION

This appendix presents BSS V13 and V12 configuration parameters and objects

A.1 New V13 parameters

Parameter Object

administrativeState cc, cem, cn, bsc3GEqpt, transcoder3GEqpt, iem, in,lsaRc, mms, omu, sw8kRm, tmu, trm

associatedTMUPosition btsSiteManageratmRmId atmRmavailabilityStatus cc, cem, cn, bsc3GEqpt, transcoder3GEqpt, iem, in,

lsaRc, mms, omu, sw8kRm, tmu, trmbsc2GEqptId bsc2GEqptbsc3GEqptId bsc3GEqptbscList executableSoftwarebscLogId bscLogbscName bscbscReset bsc3GEqptbscUsedAdr bscMdInterfaceccId cccemId cemcnId cncoderPoolList transcoder3GEqptconfigRefList executableSoftwareCTU cable iemexecutableSoftwareId executableSoftwareexecutableSoftwareName executableSoftwareiemId ieminId ininterOmuEtherlinkOper cnlapd exists iem, lsaRclapdlinkCallPLoad transcoder3GEqptlsaPcmList iem, lsaRclsaRcId lsaRclsaRc Reference iemmaxNbrConsMess bscLogmmsId mmsmmsUsage mmsnumberOfEnabledHDLCPorts iem, tmuomuId omuoperationalState atmRm, cc, cem, cn, bsc3GEqpt, transcoder3GEqpt, iem,

in, lsaRc, mms, omu, sw8kRm, tmu, trmport Ethernet Operational omu

Nortel Networks Confidential3–2 Objects and parameters evolution

PE/DCL/DD/0124411–9001–124


Parameter Object

port Ethernet Status omuport0X25Status omuport1X25Status omupositionInShelf atmRm, cc, cem, iem, lsaRc, mms, omu, sw8kRm, tmu,

trmprivateMmsOmuRef mmsprotocolUsed bscMdInterfacerelatedSoftwares executableSoftwareshelfNumber atmRm, cc, cem, iem, lsaRc, mms, omu, sw8kRm, tmu,

trmsoftwareLabel executableSoftwarestandbyStatus atmRm, cem, iem, lsaRc, omu, sw8kRmsw8kRmId sw8kRmtmuId tmutranscoder2GEqptId transcoder2GEqpttranscoder3GEqptId transcoder3GEqpttranscoderAlarmList transcoder2GEqpttrmId trmtSCBNumber bsc2GEqpttSCBUse bsc2GEqptupgradeStatus atmRm, cc, cem, iem, omu, sw8kRm, tmu, trmX25Port0Operational omuX25Port1Operational omu



A.2 New V12 parameters

Parameter Object Feature

additional supervised PCM 0 btsSiteManager FM1189additional supervised PCM 1 btsSiteManager FM1189additional supervised PCM 2 btsSiteManager FM1189additional supervised PCM 3 btsSiteManager FM1189additional supervised PCM 4 btsSiteManager FM1189additional supervised PCM 5 btsSiteManager FM1189additional unmasked users alarms btsSiteManager FM1158adjCHOReserved3 adjacentCellHandOver FM1189adjCHOReserved4 adjacentCellHandOver FM1189administrativeState pcu SV407allocBitmap transceiver SV407availabilityStatus pcu SV407availabilityStatus pcusn SV407biZonePowerOffset adjacentCellHandOver

handOverControlTF875

bscGprsActivation bsc SV407btsLockedReserved2 bts V12bscPcuPcmRefList pcu SV407bscRefList pcusn SV407bsCvMax bts SV407btsReserved3 bts TF995btsReserved4 bts V12btsSensitivity bts SV407btsSensitivityInnerZone bts SV407btsSMReserved1 btsSiteManager V12btsSMReserved2 btsSiteManager V12btsWithCavity bts PR1179codingScheme transceiver SV407cpueNumber btsSiteManager AR874currentChannelHorqd signallingPoint V12Data14.4OnNoHoppingTs bts V12directedRetryPrio bts TF821dLPwrValue transceiver SV407drxTimerMax bts SV407eMLPPThreshold signallingPoint ASCIenhancedTRAUFrameIndication bsc FM660geographical coordinates pcusn SV407gprsAvgParam bts SV407gprsCellActivation bts SV407gprsPermittedAccess bts SV407gprsPreemption bts TF1121gprsPreemptionProtection bts TF1121gprsPriority transceiver TF1121


PE/DCL/DD/0124411–9001–124


Parameter FeatureObject

gprsTimerWaitPUAM bts SV407gprsTimerWaitRLC bts SV407hoMarginTiering handoverControl TF995hoMarginTrafficOffset adjacentCellHandOver TF132HOPingpongCombination adjacentCellHandOver TF821HOPingpongTimeRejection adjacentCellHandOver TF821hoTraffic bsc

btsTF132

interferenceType adjacentCellHandOver TF995longTbfLossThroughput bts SV407longTbfSizeThreshold bts SV407maxBsTransmitPowerInnerZone bts SV407maxDnTbfP1P2Threshold bts SV407maxDnTbfPerTs bts SV407maxDwAssign bts SV407maxNbrPDAAssig transceiver SV407maxNbrPUDWithoutVChange transceiver SV407maxNbrRLCEmptyBlock transceiver SV407maxRach bts SV407maxUpTbfP1P2Threshold bts SV407maxUpTbfPerTs bts SV407measurementProcAlgorithm bts TF1089minNbrsGprsTs bts TF1121msCapWeightActive bts SV407msTxPwrMax2ndBand bts TF875muxNumber pcusn SV407N3103 bts SV407N3105max bts SV407nbrFreeTchBeforeAnticipation bts SV407nbrFreeTchToEndAnticipation bts SV407nbrTch pcu SV407NCHPosition bts ASCInumberOfPwciSamples handOverCOntrol TF995offsetLoad adjacentCellHandOver TF716offsetPriority adjacentCellHandOver TF716operationalState pcu SV407operationalStatus pcusn SV407packetAckTime transceiver SV407pan bts SV407pcmErrorCorrection bts FM660pcmNbr pcu SV407pcu pcu SV407pcuLapdEqptRefList pcu SV407pcusn pcusn SV407



Parameter FeatureObject

pcuSNName pcusn SV407pcuSNReserved1 pcusn SV407pcuSNReserved2 pcusn SV407preemptionAuthor signallingPoint ASCIpwciHreqave handOverControl TF995radioAllocator bts TF1121reserved1 pcu SV407reserved1 transceiver SV407reserved2 pcu SV407reserved2 transceiver SV407reserved3 bts SV407reserved3 pcu SV407reserved3 transceiver SV407reserved4 bts SV407reserved4 pcu SV407reserved4 transceiver SV407reserved5 bts SV407reserved5 pcu SV407reserved5 transceiver SV407routingArea bts SV407rxQualDLIH handOverControl TF819rxQualULIH handOverControl TF819selfTuningObs handOverControl TF995sigPReserved1 signallingPoint V12sigPReserved2 signallingPoint V12speechOnHoppingTs bts SV407speechVersionAsscomp signallingPoint V12speechVersionHoperf signallingPoint V12speechVersionHoreq signallingPoint V12speechVersionHorqd signallingPoint V12T3172 bts SV407transcdBReserved1 transcoderBoard V12transcdBReserved2 transcoderBoard V12transcvEReserved1 transceiverEquipment V12transcvEReserved2 transceiverEquipment V12uplinkMappingChannelNumber bts TF876uplinkMappingFreq bts TF876uplinkMappingMeasurementMode bts TF876uplinkMappingProcessingMode bsc TF876voiceBroadcastService signallingPoint ASCIvoiceGroupCallService signallingPoint ASCI


PE/DCL/DD/0124411–9001–124


A.2.1 Parameter updates linked to new feature introduction

Parameter Object Feature

associatedInterface lapdLink SV407bsc equipment name Alarm and notification logs

– FilterSV407

bts time between HO configuration bts TF821channelType channel TF184

SV407concentric cell bts TF875intraCell handOverControl TF995lapdConcentration lapdLink SV407lapdLink lapdLink SV407lapdTerminalNumber lapdLink SV407new power control algorithm bts TF975pcmCircuit pcmCircuit SV407pcmType pcmCircuit SV407processorLoadSupConf bsc FM874rxLevULIH handOverControl FM876standard indicator bts TF875standard indicator AdjC adjacentCellHandOver

adjacentCellReselectionTF875

timeBetweenHOConfiguration bsc TF821

Configuration parameter listNortel Networks Confidential 4–1


APPENDIX B CONFIGURATION PARAMETER LISTTable B–1 lists the configuration parameters of a BSS in alphabetical order, with their type,their class, and the object class to which they are related.

The following should be noted:

Dynamic data (DDs) and internal data (DIs) are not classified.

Some permanent data (DPs) are not classified. This includes object administrativeStateattributes, object name attributes, attributes that cannot be modified, and attributes thatare not managed by users.

Parameter Type Class Object class

abisSpy DP 3 bts

absoluteRFChannelNo DP 2 channel

accessClassCongestion DP 3 bts

accessibilityState DD signallingLinkSet

active (passive) chain disk state DD bsc

active (passive) chain Dmux state DD bsc

active (passive) chain ECI boardstate

DD bsc

active (passive) chain REM linkstate

DD bsc

active (passive) chain Sic boardstate

DD bsc

active (passive) chain sicchannels state

DD bsc

active (passive) chain sls boardstate

DD bsc

active (passive) chain state DD bsc

active (passive) chain switchingcapacity

DD bsc

active (passive) chain tcuaccessibility

DD bsc

active (passive) chain ute boardstate

DD bsc

active rem link DD bsc

activeChain DD bsc

adjacent cell umbrella Ref DP 3 bts

adjCHOReserved3 DP 3 adjacentCellHandOver

adjCHOReserved4 DP 3 adjacentCellHandOver

Nortel Networks Confidential4–2 Configuration parameter list

PE/DCL/DD/0124411–9001–124


Parameter Object classClassType

administrativeState DP – bsc, bscMdInterface, bts,btsSiteManager, pcm-Circuit, pcu, signallingLink,transceiverEquipment, transcoder,transcoder-Board, xtp, cc, cem, cn, bsc3GEqpttranscoder3GEqpt, iem, in, lsaRcmms, omu, sw8kRm, tmu, trm

aLAIntState DD bsc

alarmListConverter DD transcoder

alarmListFan DD transcoder

alarmListFanBoard DD transcoder

alarmListVCOTension DD transcoder

AlgoId DP – transcoderBoard

algorithm Used DP 2 transcoderBoard

allocationState DD transceiver

allocBitmap DP 3 transceiver

allocPriorityTable DP 3 bts

allocPriorityThreshold DP 3 bts

allocPriorityTimers DP 3 bts

allocWaitThreshold DP 3 bts

allOtherCasesPriority DP 3 bts

answerPagingPriority DP 3 bts

assignRequestPriority DP 3 bts

associatedInterface DP – lapdLink

associatedTMUPosition DP – btsSiteManager

atmRmId DP – atmRm

Attenuation DP 2 btsSiteManager

auditBdaStatus DI – bsc

auditState DI – bsc

availabilityStatus DD – bsc, bscMdInterface, bts,btsSiteManager, lapdLink, pcmCircuit,pcu, signallingLink, transceiver,transceiver-Equipment, transcoder,transcoderBoard, xtp, cc, cem, cnbsc3GEqpt, transcoder3GEqptiem, in, lsaRc, ms, omu, sw8kRmtmu, trm




averagingPeriod DP 2 handOverControl

backupServer DP – md

baseColourCode DP 23

btsadjacentCellHandOver

bCCHFrequency DP 233

btsadjacentCellHandOveradjacentCellReselection

bdaNewBscState DI – bsc

bdaSelected DI bsc

bdaState DI bsc

bdaVersionNumber DD bsc

biZonePowerOffset DP 33

adjacentCellHandOverhandOverControl

bsc2GEqptId DP – bsc2GEqpt

bsc3GEqptId DP – bsc3GEqpt

bscAlarmMask DP 3 bsc

bscArchitecture DP 0 bsc

bscDateTime DD bsc

bscGprsActivation DP 3 bsc

bscHopReconfUse DP 1 bsc

bscList DP – executableSoftware

bscLogId DP – bscLog

bscMdInterfaceRef DP – bsc

bscMdInterfaceVersionNumber DP – bsc

bscMSAccessClassBarring-Function

DP 3 bsc

bscName DP – bsc

bscPcuPcmRefList DP 2 pcu

bscQueuingOption DP 1 signallingPoint

bscRefList DP 3 pcusn

bscReset DP – bsc3GEqpt

bscSitePcmList DP 2 btsSiteManager

bscTimeSlot DD channel

bscType DP 0 bsc

bscUsedAdr DP – bscMdInterface

bsCvMax DP 3 bts

bscX25PrefAdr DP 2 bscMdInterface


PE/DCL/DD/0124411–9001–124



bscX25SecAdr DP 2 bscMdInterface

bscX25UsedAdr DD bscMdInterface

bsPowerControl DP 3 powerControl

bssMapT1 DP 1 bsc

bssMapT12 DP 1 bsc

bssMapT13 DP 1 bsc

bssMapT19 DP 1 bsc

bssMapT20 DP 1 bsc

bssMapT4 DP 1 bsc

bssMapT7 DP 1 bsc

bssMapT8 DP 1 bsc

bssMapTchoke DP 1 bsc

bssSccpConnEst DP 1 signallingPoint

bssSccpInactRx DP 1 signallingPoint

bssSccpInactTx DP 1 signallingPoint

bssSccpRelease DP 1 signallingPoint

bssSccpSubSysTest DP 1 signallingPoint

bsTxPwrMax DP 3 powerControl

bts time between HOconfiguration

DP 3 bts

btsDescription DI – btsSiteManager

btsHopReconfRestart DP 2 bts

btsIsHopping DP 2 bts

btsLockedReserved2 DP 3 bts

btsMSAccessClassBarring-Function

DP 3 bts

btsReserved3 DP 3 bts

btsReserved4 DP 3 bts

btsSensitivity DP 3 bts

btsSensitivityInnerZone DP 3 bts

btsSiteManagerList DP 2 multiple site

btsSMReserved1 DP 2 btsSiteManager

btsSMReserved2 DP 2 btsSiteManager

btsThresholdHopReconf DP 2 bts

btsWithCavity DP 2 bts

buildState DI bsc




callClearing DP 3 bts

callReestablishment DP 3 bts

callReestablishmentPriority DP 3 bts

ccId DP – cc

cellBarQualify DP 3 bts

cellBarred DP 3 bts

cellDeletionCount DP 3 bts

cellDtxDownlink DP 3 bts

cellIdentity DP 233

btsadjacentCellHandOveradjacentCellReselection

cellName DP – bts

cellPagingState DD bts

cellReselectHysteresis DP 3 bts

cellReselectOffset DP 3 bts

cellReselInd DP 3 bts

cellType DP 33

adjacentCellHandOverbts

cemId DP – cem

channel state DP 2 channel

channelType DD channel

chanState DP – channel

chosenChannelAsscomp DP 1 signallingPoint

chosenChannelCompL3Info DP 1 signallingPoint

chosenChannelHoPerf DP 1 signallingPoint

chosenChannelHoReq DP 1 signallingPoint

cic DP – xtp

circuitGroupBlock DP 1 signallingPoint

cnId DP – cn

coderPoolList DP – transcoder3GEqpt

codingScheme DP 2 transceiver

concentAlgoExtMsRange DP 3 handOverControl

concentAlgoExtRxLev DP 3 handOverControl

concentAlgoIntMsRange DP 3 handOverControl

concentAlgoIntRxLev DP 3 handOverControl

concentric cell DP 2 bts


PE/DCL/DD/0124411–9001–124



configRef DP 2 btsSiteManager

configRefList DP – executableSoftware

confusion DP 1 signallingPoint

counter list filename DP – bscCounterList

counters DP – bscCounterList

cpueNumber DP – btsSiteManager

cpueOccurrence DD btsSiteManager

cRC DP 2 pcmCircuit

CTU cable DD – iem

currentChannelHorqd DP 1 signallingPoint

cypherModeReject DP 1 signallingPoint

data mode 14.4 kbit/s DP 2 transcoderBoard

data non transparent mode DP 33

btssignallingPoint

data transparent mode DP 33

btssignallingPoint

Data14.4OnNoHoppingTs DP 3 bts

dDTIIntState DD pcmCircuit

delayBetweenRetrans DP 2 bts

deltaUtc DP – md

directedRetry DP 3 adjacentCellHandOver

directedRetryModeUsed DP 3 bts

directedRetryPrio DP – bts

distHreqt DP 3 handOverControl

distWtsList DP 3 handOverControl

diversity DP 2 bts

dLPwrValue DP 3 transceiver

drxTimerMax DP 3 bts

dtxMode DP 3 bts

duplex link state DD bsc

early classmark sending DP 3 bts

emergencyCallRestricted DP 3 bts

emergencyCallPriority DP 3 bts

eMLPPThreshold DP 1 signallingPoint

encrypAlgoAsscomp DP 1 signallingPoint

encrypAlgoCiphModComp DP 1 signallingPoint




encrypAlgoHoperf DP 1 signallingPoint

encrypAlgoHoreq DP 1 signallingPoint

encryptionAlgorSupported DP 1 bsc

enhancedTRAUFrameIndication DI – bsc

error concealment unit DP 2 bts

errorCorrectionMethod DP 3 signallingLinkSet

executableSoftwareId DP – executableSoftware

executableSoftwareName DP – executableSoftware

extCommsInt DD bsc

extended cell DP 2 bts

external alarm configuration DP 2 btsSiteManager

external battery cabinet DP 2 btsSiteManager

externalTime DP – md

fhsRef DP 2 channel

forced handover algo DP 3 adjacentCellHandOver

geographical coordinates DI btsSiteManagerbscmdpcutranscoder

gprsAvgParam DP 3 bts

gprsCellActivation DP 3 bts

gprsPermittedAccess DP 3 bts

gprsPreemption DP 3 bts

gprsPreemptionProtection DP 3 bts

gprsPriority DP 3 transceiver

gprsTimerWaitPUAM DP 3 bts

gprsTimerWaitRLC DP 3 bts

HandOver from signalling channel DP 3 handOverControl

hardware configuration DP 2 transceiverEquipment

hardwareRef DP 222

btsSiteManagertransceiverEquipmenttranscoderBoard

hoMargin DP 3 adjacentCellHandOver

hoMarginBeg DP 3 bts

hoMarginDist DP 3 adjacentCellHandOver

hoMarginRxLev DP 3 adjacentCellHandOver


PE/DCL/DD/0124411–9001–124



hoMarginRxQual DP 3 adjacentCellHandOver

hoMarginTiering DP 3 handOverControl

hoMarginTrafficOffset DP 3 adjacentCellHandOver

HOPingpongCombination DP 3 adjacentCellHandOver

HOPingpongTimeRejection DP 3 adjacentCellHandOver

hoppingSequenceNumber DP 2 frequencyHoppingSystem

HOSecondBestCellConfiguration DP 3 bsc

hoTraffic DP 33

bscbts

iemId DP – iem

iMSIAttachDetach DP 2 bts

incomingHandOver DP 3 handOverControl

inId DP – in

interBscDirectedRetry DP 3 bsc

interBscDirectedRetryFromCell DP 3 bts

interCellHOExtPriority DP 3 bts

interCellHOIntPriority DP 3 bts

interferenceType DP 3 adjacentCellHandOver

interferer cancel algo usage DP 2 bts

interOmuEtherlinkOper DD – cn

intraBscDirectedRetry DP 3 bsc

intraBscDirectedRetryFromCell DP 3 bts

intraCell DP 3 handOverControl

intraCellHOIntPriority DP 3 bts

intraCellQueueing DP 3 bts

intraCellSDCCH DP 3 handOverControl

lapdConcentration DP – lapdLink

lapdexists DD – iem, lsaRc

lapdLinkCallPLoad DP – transcoder3GEqpt

lapdLinkOMLRef DP 022

transcoderbtsSiteManagertransceiverEquipment

lapdLinkRSLRef DP 2 transceiverEquipment

lapdTerminalNumber DP 0 lapdLink

layer3MsgCyphModComp DP 1 signallingPoint

lightning protection DP 2 btsSiteManager




locationAreaCode DP 332

adjacentCellHandOveradjacentCellReselectionbts

longTbfLossThroughput DP 3 bts

longTbfSizeThreshold DP 3 bts

lRxLevDLH DP 3 handOverControl

lRxLevDLP DP 3 powerControl

lRxLevULH DP 3 handOverControl

lRxLevULP DP 3 powerControl

lRxQualDLH DP 3 handOverControl

lRxQualDLP DP 3 powerControl

lRxQualULH DP 3 handOverControl

lRxQualULP DP 3 powerControl

lsaPcmList DP 3 iem, lsaRc

lsaRcId DP – lsaRc

lsaRc Reference DP – iem

maio DP 2 channel

managerServer DP – md

maxBsTransmitPowerInnerZone DP 3 bts

maxDnTbfP1P2Threshold DP 3 bts

maxDnTbfPerTs DP 3 bts

maxDwAssign DP 3 bts

maxNbOfCells DP 2 btsSiteManager

maxNbrConsMess DP – bscLog

maxNbrPDAAssig DP 2 transceiver

maxNbrPUDWithoutVChange DP 2 transceiver

maxNbrRLCEmptyBlock DP 2 transceiver

maxNumberRetransmission DP 3 bts

maxRach DP 3 bts

maxUpTbfP1P2Threshold DP 3 bts

maxUpTbfPerTs DP 3 bts

mdId DP – md

measurementProcAlgorithm DP 2 bts

microCellCaptureTimer DP 3 adjacentCellHandOver (A algorithm)

microCellStability DP 33

adjacentCellHandOver (A algorithm)bts (B algorithm)


PE/DCL/DD/0124411–9001–124



minNbOfTDMA DP 2 bts

minNbrGprsTs DP 3 bts

missDistWt DP 3 handOverControl

missRxLevWt DP 3 handOverControl

missRxQualWt DP 3 handOverControl

mmsId DP – mms

mmsUsage DP – mms

mobileAllocation DP 2 frequencyHoppingSystem

mobileCountryCode DP 1233

bscbtsadjacentCellHandOveradjacentCellReselection

mobileNetworkCode DP 1233

bscbtsadjacentCellHandOveradjacentCellReselection

modeModifyMandatory DP 3 bsc

msBtsDistanceInterCell DP 3 handOverControl

msCapWeightActive DP 2 bts

msRangeMax DP 3 handOverControl

msTxPwrMax DP 3 bts

msTxPwrMax2ndBand DP 2 bts

msTxPwrMaxCCH DP 3 bts

msTxPwrMaxCell DP 3 adjacentCellHandOver

multi band reporting DP 3 bts

multipleVocoders DP 1 bsc

muxNumber DP 3 pcusn

N3103 DP 3 bts

N3105max DP 2 transceiver

nbOfRepeat DP 2 bts

nbrFreeTchBeforeAnticipation DP 3 bts

nbrFreeTchToEndAnticipation DP 3 bts

nbrTch DP 2 pcu

NCHPosition DP 2 bts

networkColourCode DP 23

btsadjacentCellHandOver

networkIndicator DP 11

signallingPointsignallingLinkSet




new power control algorithm DP 3 bts

noOfBlocksForAccessGrant DP 2 bts

noOfMultiframesBetween-Paging

DP 2 bts

notAllowedAccessClasses DP 3 bts

numberOfPwciSamples DP 3 handOverControl

numberOfEnabledHDLCPorts DD – iem, tmu

numberOfSlotsSpreadTrans DP 3 bts

numberOfTCHFreeBefore-Congestion

DP 3 bts

numberOfTCHFreeToEnd-Congestion

DP 3 bts

numberOfTCHQueuedBefore-Congestion

DP 3 bts

numberOfTCHQueuedToEnd-Congestion

DP 3 bts

observationType DP – bscCounterList

occupationState DD xtp

offsetLoad DP 3 adjacentCellHandOver

offsetPriority DP 3 adjacentCellHandOver

omuId DP – omu

operationalState DD bsc, bscMdInterface, bts,btsSiteManager, lapdLink, pcmCircuit,pcu, signallingLink, transceiver,transceiver-Equipment, transcoder,transcoderBoard, xtp, atmRmcc, cem, cn, bsc3GEqpttranscoder3GEqpt, iem, in, lsaRcmms, omu, sw8kRm, tmu, trm

otherServicesPriority DP 3 bts

packetAckTime DP 3 transceiver

pagingOnCell DP 3 bts

pan DP 3 bts

pcmCircuitBsc DP – btsSiteManager

pcmCircuitBtsSiteManager DP – btsSiteManager

pcmCircuitId DD lapdLink


PE/DCL/DD/0124411–9001–124



pcmCircuitId DP 222

signallingLinktranscoderxtp

pcmErrorCorrection DP 2 bts

pcmNbr DP 2 pcu

pcmTimeSlotNumber DP 2 btsSiteManager

pcmType DP 3 pcmCircuit

pcuLapdEqptRefList DP 2 pcu

pcuSNName DP – pcusn

pcuSNReserved1 DP 3 pcusn

pcuSNReserved2 DP 3 pcusn

penaltyTime DP 3 bts

periodCCCHLoadIndication DP 3 bts

plmnPermitted DP 3 bts

pointCode DP 11

signallingLinkSetsignallingPoint

port0X25Status DD – omu

port1X25Status DD – omu

portChosen DP 2 bscMdInterface

portEthernetOperational DD – omu

portEthernetStatus DD – omu

portUsed DD bscMdInterface

positionInShelf DD – atmRm, cc, cem, iem, lsaRc, mmsomu, sw8kRm, tmu, trm

powerBudgetInterCell DP 3 handOverControl

powerClass DP – transceiver

powerControlIndicator DP 3 bts

powerDownlink DP – transcoderBoard

powerIncrStepSize DP 3 powerControl

powerRedStepSize DP 3 powerControl

preemptionAuthor DP 1 signallingPoint

preSynchroTimingAdvance DP 3 adjacentCellHandOver

priority DP 2 transceiver

privateMmsOmuRef DP – mms

processorLoadSupConf DP 3 bsc

protocolUsed DP – bscMdInterface




rACHLoadAveragingSlots DP 3 bts

radChanSellIntThreshold DP 3 handOverControl

radioAllocator DP 2 bts

radioLinkTimeout DP 3 bts

radioSiteMask DP 2 btsSiteManager

radioSiteName DP – multiple site

radResSupBusyTimer DP 3 bsc

radResSupervision DP 3 bts

radResSupFreeTimer DP 3 bsc

redundantPcmNumber DD btsSiteManager

redundantPcmPresence DP 2 btsSiteManager

relatedSoftwares DP – executableSoftware

remoteSsuState DD signallingLinkSet

reserved1 DP 2 pcu

reserved1 DP 2 transceiver

reserved2 DP 2 pcu


reserved3 DP 2 bts

reserved3 DP 2 pcu


reserved4 DP 2 bts

reserved4 DP 2 pcu


reserved5 DP 3 bts

reserved5 DP 2 pcu


resetCircuitRepeat DP 1 signallingPoint

retransDuration DP 2 bts

rlf1 DP 2 bts

rlf2 DP 2 bts

rlf3 DP 2 bts

rmpConfState DD transceiver

rndAccTimAdvThreshold DP 3 bts

routingArea DP 2 bts

runCallClear DP 3 bts


PE/DCL/DD/0124411–9001–124



runHandOver DP 3 bts

runPwrControl DP 3 bts

rxLevAccessMin DP 3 bts

rxLevDLIH DP 3 handOverControl

rxLevDLPBGT DP 3 adjacentCellHandOver

rxLevHreqave DP 3 handOverControl

rxLevHreqaveBeg DP 3 handOverControl

rxLevHreqt DP 3 handOverControl

rxLevMinCell DP 3 adjacentCellHandOver

rxLevNCellHreqaveBeg DP 3 handOverControl

rxLevULIH DP 3 handOverControl

rxLevWtsList DP 3 handOverControl

rxNCellHreqave DP 3 handOverControl

rxQualDLIH DP 3 handOverControl

rxQualHreqave DP 3 handOverControl

rxQualHreqt DP 3 handOverControl

rxQualULIH DP 3 handOverControl

rxQualWtsList DP 3 handOverControl

sapi DP – lapdLink

selfTuningObs DP 3 handOverControl

shelfNumber DP – atmRm, cc, cem, iem, lsaRcmms, omu, sw8kRmtmu, trm

signallingLinkResState DD signallingLink

signallingPointType DP – signallingPoint

signallingTerminalNumber DP 2 signallingLink

sigPReserved1 DP 3 signallingPoint

sigPReserved2 DP 3 signallingPoint

siteGsmFctList DP 2 btsSiteManager

siteName DP – btsSiteManager

slc DP 2 signallingLink

small to large zone HO priority DP 3 handOverControl

smoke detector DP 2 btsSiteManager

smsCB DP 3 bts

softwareLabel DP – executableSoftware




speechMode DP 33

btssignallingPoint

speechOnHoppingTs DP 3 bts

speechVersionAsscomp DP 1 signallingPoint

speechVersionHoperf DP 1 signallingPoint

speechVersionHoreq DP 1 signallingPoint

speechVersionHorqd DP 1 signallingPoint

standard indicator AdjC DP 2 adjacentCellHandOveradjacentCellReselection

standardIndicator DP 2 bts

standbyStatus DD – atmRm, cem, iem, lsaRcomu, sw8kRm

supportingTransceiverEquipment DD transceiver

sw8kRmId DP – sw8kRm

sWVersionBackUp DP – software

sWVersionFallback DP – software

sWVersionNew DP – software

sWVersionRunning DP – software

synchronized DP 3 adjacentCellHandOver

synchronizing PCM DD bsc

t3101 DP 3 bts

t3103 DP 3 bts

t3107 DP 3 bts

t3109 DP 3 bts

t3111 DP 3 bts

t3122 DP 3 bts

T3172 DP 3 bts

teiBtsSiteManager DP 2 btsSiteManager

teiLapdLink DP – lapdLink

teiTransceiverEqpt DP 2 transceiverEquipment

teiTranscoder DP 2 transcoder

temporaryOffset DP 3 bts

TFH or RWM DP 2 btsSiteManager

thresholdCCCHLoadIndication DP 3 bts

thresholdInterference DP 2 handOverControl

timeBetweenHOConfiguration DP 3 bsc


PE/DCL/DD/0124411–9001–124



timerPeriodicUpdateMS DP 3 bts

timeSlotNumber DD lapdLink

timeSlotNumber DP 2–

signallingLinkxtp

tmuId DP – tmu

traffic PCM allocation priority DP 2 transceiver

transcdBReserved1 DP 3 transcoderBoard

transcdBReserved2 DP 3 transcoderBoard

transceiver equipment class DP 2–

transceivertransceiverZone

transceiver zone Ref DP 2 transceiver

transcoderAlarmMask DP 3 transcoder

transcoderBoardIntState DD transcoderBoard

transcoder2GEqptId DP – transcoder2GEqpt

transcoder3GEqptId DP – transcoder3GEqpt

transcoderAlarmList DP – transcoder2GEqpt

transcoderId DP 22

signallingLinkxtp

transcoderIntPcmIntState DD transcoder

transcoderMatrix DP – transcoder

transcvEReserved1 DP 3 transceiverEquipment

transcvEReserved2 DP 3 transceiverEquipment

trmId DP – trm

tSCBNumber DP – bsc2GEqpt

tSCBUse DP – bsc2GEqpt

tsConfiguration DD transceiver

txPwrMaxReduction DP 2 transceiver

unequippedCircuit DP 1 signallingPoint

unknownNCellWarning DP 3 bts

unmasked users alarms DP 2 btsSiteManager

upgradeStatus DD – atmRm, cc, cem, iem, omusw8kRm, tmu, trm

uplinkMappingChannelNumber DP 2 bts

uplinkMappingFreq DP 2 bts

uplinkMappingMeasurementMode DP 2 bts

uplinkMappingProcessingMode DP 2 bsc




uplinkPowerControl DP 3 powerControl

uRxLevDLP DP 3 powerControl

uRxLevULP DP 3 powerControl

uRxQualDLP DP 3 powerControl

uRxQualULP DP 3 powerControl

usageState DD xtp

version DP 2 transcoder

voiceBroadcastService DP 3 signallingPoint

voiceGroupCallService DP 3 signallingPoint

VSWR meter DP 2 btsSiteManager

X25Port0Operational DD – omu

X25Port1Operational DD – omu

xSCBConfiguration DP 0 bsc

xSCBNumber DD bsc

xSCBUse DD bsc

zone frequency hopping DP 2 transceiverZone

zone frequency threshold DP 2 transceiverZone

zone Tx power max reduction DP 2 transceiverZone

Table B–1 Configuration parameter list

In the standard OMC–R configuration, the disks of the active and backup servers aremirrored. Any change to the active server disks updates the standby server disks.

A directory name specified in this chapter beginning with “/xxx” should be understood as“/xxx_SRV” when applied to the active server and “/xxx_BKP” when applied to the standbyserver.

The various operands that can be applied to a parameter are detailed in NTP < 130 > asfollows:

in Paragraph 12.2.2, for scope & filter commands

in Appendix A “Filter parameter”, for trace data display commands


PE/DCL/DD/0124411–9001–124



Index of parametersNortel Networks Confidential i


AabisSpy, 2–1

absoluteRFChannelNo, 2–1

access time end, 2–2

access time start, 2–2

accessClassCongestion, 2–2

accessibilityState, 2–3

acknowledged by, 2–3

acknowledgment time, 2–3

activationObjectcallPathTrace, 2–4 traceControl, 2–4

active chain disk state, 2–4

active chain Dmux state, 2–4

active chain ECI board state, 2–5

active chain REM link state, 2–5

active chain Sic board state, 2–5

active chain sic channels state, 2–5

active chain sls board state, 2–5

active chain state, 2–6

active chain switching capacity, 2–6

active chain tcu accessibility, 2–6

active chain ute board state, 2–6

active rem link, 2–6

activeChain, 2–7

additional supervised PCM 0, 2–7






additional unmasked users alarms, 2–11

addresses, 2–12

adjacent cell umbrella ref, 2–12

adjacentCellHandOver, 2–13

adjacentCellReselection, 2–14

adjCHOReserved3, 2–14

adjCHOReserved4, 2–14

administrativeState, 2–22 alarm criteria, 2–15

Index of parameters Nortel Networks Confidentialii

PE/DCL/DD/0124411–9001–124


atmRm, 2–15 bsc, 2–15 bscMdInterface, 2–16 bts, 2–16 btsSiteManager, 2–18 callPathTrace, 2–19 cc, 2–20 cem, 2–20 cn, 2–20 efd, 2–21 g3BscEqp, 2–21 g3Transcoder, 2–21 iem, 2–21 in, 2–21 log, 2–22 lsaRc, 2–22 mdWarning, 2–22 mms, 2–23 omu, 2–23 pcmCircuit, 2–23 pcu, 2–23 signallingLink, 2–24 sw8kRm, 2–24 tmu, 2–24 traceControl, 2–24 transceiverEquipment, 2–25 transcoder, 2–26 transcoderBoard, 2–27 trm, 2–27 xtp, 2–27

aLAIntState, 2–28

alarm criteriaalarm criteria, 2–29 omc, 2–28

alarm number, 2–29

alarm severity, 2–30

alarm state, 2–30

alarmDuration, 2–30

alarmListConverter, 2–30

alarmListFan, 2–30

alarmListFanBoard, 2–31

alarmListVCOTension, 2–31

alarmPriority, 2–32

AlgoId, 2–33

algorithm Used, 2–33

allocationState, 2–34

Index of parametersNortel Networks Confidential iii


allocBitmap, 2–34

allocPriorityTable, 2–35

allocPriorityThreshold, 2–35

allocPriorityTimers, 2–36

allocWaitThreshold, 2–36

allOtherCasesPriority, 2–36

answerPagingPriority, 2–37

architecture, 2–37

assignRequestPriority, 2–37

associatedInterface, 2–38

associatedLogcallPathTrace, 2–38 mdScanner, 2–38 traceControl, 2–38

associatedTMUPosition, 2–38

atmRmId, 2–39

Attenuation, 2–39

auditBdaStatus, 2–40

auditState, 2–40

authorised user, 2–40

availabilityStatusbsc, 2–41 bscMdInterface, 2–41 bts, 2–41 btsSiteManager, 2–41 lapdLink, 2–41 log, 2–41 mdScanner, 2–42 pcmCircuit, 2–41 pcu, 2–42 pcusn, 2–42 signallingLink, 2–41 transceiver, 2–41 transceiverEquipment, 2–41 transcoder, 2–41 transcoderBoard, 2–41 xtp, 2–42

averagingPeriod, 2–43

Bbackup manager addresses, 2–44

backupServer, 2–44

baseColourCodeadjacentCellHandOver, 2–44 bts, 2–45

Index of parameters Nortel Networks Confidentialiv

PE/DCL/DD/0124411–9001–124


bCCHFrequencyadjacentCellHandOver, 2–45 adjacentCellReselection, 2–46 bts, 2–46

bda activation type, 2–47

bdaNewBscState, 2–48

bdaSelected, 2–49

bdaState, 2–49

bdaVersionBuild, 2–50

bdaVersionNumber, 2–50

Beginning date, 2–50

beginSearchTimeDisplay custom report, 2–51 Display raw report, 2–51 List available temporary observations, 2–52 List observation messages, 2–52

biZonePowerOffsetadjacentCellHandOver, 2–53 handOverControl, 2–53

bscadjacentCellHandover, 2–55 adjacentCellReselection, 2–55 bsc, 2–54 bts, 2–55 btsSiteManager, 2–55 channel, 2–55 frequencyHoppingSystem, 2–55 handOverControl, 2–55 lapdLink, 2–55 multiple site, 2–55 pcmCircuit, 2–55 powerControl, 2–55 signallingLink, 2–55 signallingLinkSet, 2–55 signallingPoint, 2–55 software, 2–55 transceiver, 2–55 transceiverEquipment, 2–55 transceiverZone, 2–55 transcoder, 2–55 transcoderBoard, 2–55 xtp, 2–55

bsc equipment name, 2–55

BSC list, 2–56

bsc model, 2–57

BSC number, 2–57

Index of parametersNortel Networks Confidential v


bsc2GEqptId, 2–53

bsc3GEqptId, 2–54

bscAlarmMask, 2–57

bscArchitecture, 2–58

bscChainId, 2–58

bscCounterList, bscCounterList, 2–58

bscDateTime, 2–59

bscGprsActivation, 2–59

bscHopReconfUse, 2–60

bscIPFirstAdr, 2–60

bscIPSecondAdr, 2–61

bscList, 2–61

bscLogId, 2–61

bscMdInterface, 2–62

bscMdInterfaceRef, 2–62

bscMdInterfaceVersionNumber, 2–62

bscMSAccessClassBarringFunction, 2–62

bscName, 2–63

bscPcuPcmRefList, 2–63

bscQueueingOption, 2–64

bscRefList, 2–64

bscReset, 2–64

bscSitePcmList, 2–65

bscTimeSlot, 2–66

bscType, 2–67

bscUsedAdr, 2–67

bsCvMax, 2–68

bscX25PrefAdr, 2–68

bscX25SecAdr, 2–69

bscX25UsedAdr, 2–69

bsMsmtProcessingMode, 2–70

bsPowerControl, 2–70

bssMapT1, 2–70

bssMapT12, 2–71

bssMapT13, 2–71

bssMapT19, 2–71

bssMapT20, 2–72

bssMapT4, 2–72

bssMapT7, 2–72

bssMapT8, 2–73

Index of parameters Nortel Networks Confidentialvi

PE/DCL/DD/0124411–9001–124


bssMapTchoke, 2–73

bssSccpConnEst, 2–74

bssSccpInactRx, 2–74

bssSccpInactTx, 2–74

bssSccpRelease, 2–75

bssSccpSubSysTest, 2–75

bsTxPwrMax, 2–75

btsadjacentCellHandOver, 2–78 adjacentCellReselection, 2–78 bts, 2–77 channel, 2–78 frequencyHoppingSystem, 2–78 handOverControl, 2–78 powerControl, 2–78 software, 2–78 transceiver, 2–78 transceiverEquipment, 2–78 transceiverZone, 2–78

bts equipment name, 2–79

bts list, 2–80

bts time between HO configuration, 2–80

btsDescription, 2–81

btsHopReconfRestart, 2–81

btsIsHopping, 2–81

btsLockedReserved2, 2–83

btsMSAccessClassBarringFunction, 2–83

btsReserved3, 2–83

btsReserved4, 2–83

btsSensitivity, 2–84

btsSensitivityInnerZone, bts, 2–84

btsSiteManageradjacentCellHandOver, 2–86 adjacentCellReselection, 2–86 bts, 2–86 btsSiteManager, 2–84 channel, 2–86 frequencyHoppingSystem, 2–86 handOverControl, 2–86 powerControl, 2–86 software, 2–86 transceiver, 2–86 transceiverEquipment, 2–86 transceiverZone, 2–86

Index of parametersNortel Networks Confidential vii


btsSiteManager model, 2–86

btsSiteManagerList, 2–87

btsSMReserved1, 2–87

btsSMReserved2, 2–87

btsThresholdHopReconf, 2–88

btsWithCavity, 2–88

buildState, 2–89

CcallClearing, 2–90

callPathObservationArea, 2–91

callPathTrace, 2–91

callPathTraceType, 2–92

callReestablishment, 2–92

callReestablishmentPriority, 2–93

capacityAlarmThreshold, 2–93

Cause, 2–94

ccId, 2–94

cellAllocation, 2–95

cellBarQualify, 2–96

cellBarred, 2–97

cellDeletionCount, 2–98

cellDtxDownLink, 2–99

cellIdentityadjacentCellHandOver, 2–100 adjacentCellReselection, 2–100 bts, 2–101

cellName, 2–101

cellPagingState, 2–102

cellReselectHysteresis, 2–103

cellReselectOffset, 2–105

cellReselInd, 2–106

cellTypeadjacentCellHandOver, 2–106 bts, 2–107

cemId, 2–107

chainFault logs, 2–108 software–bsc, 2–108

chainIdbsc – Display chain information, 2–108 bsc – Suicide chain, 2–108

Index of parameters Nortel Networks Confidentialviii

PE/DCL/DD/0124411–9001–124


channel, channel, 2–109

channel state, 2–110

channelType, 2–111

chanState, 2–114

chosenChannelAsscomp, 2–115

chosenChannelCompL3Info, 2–115

chosenChannelHoPerf, 2–115

chosenChannelHoReq, 2–116

cic, 2–117

circuitGroupBlock, 2–118

circularFileId, 2–118

circularFileState, 2–119

clear time, 2–119

cleared by, 2–119

clearing cause, 2–119

cnId, 2–120

coderPoolList, 2–120

codingScheme, 2–120

command classes, 2–122

command line, 2–122

command number, 2–122

commandFileCommand file editing, 2–123 commandFile, 2–123

commentreport template, 2–123 short message, 2–123

comments, 2–124

ComputeSyntheticCounters, 2–124

concentAlgoExtMsRange, 2–124

concentAlgoExtRxLev, 2–125

concentAlgoIntMsRange, 2–126

concentAlgoIntRxLev, 2–127

concentric cell, 2–129

condition, 2–130

configRef, 2–132

configRefList, 2–132

configurationType, 2–133

confusion, 2–133

Counter list, 2–133

Index of parametersNortel Networks Confidential ix


counter list filename, 2–133

counterId, mdWarning (outOfRangeCounter), 2–134

counters, 2–134

cpueNumber, 2–134

cpueOccurence, 2–135

cRC, 2–136

creator, 2–137

criteriaEventType, 2–137

CTU cable, 2–137

current log size, 2–137

currentChannelHorqd, 2–138

cypherModeReject, 2–138

Ddata mode 14.4 kbit/s, 2–139

data non transparent modebts, 2–139 signallingPoint, 2–140

data transparent modebts, 2–140 signallingPoint, 2–141

Data14_4OnNoHoppingTs, 2–141

dateDaily observation report, 2–141 md – Archive, 2–142 md – Restore, 2–142 omc – Archive, 2–142 omc – Restore, 2–142

day intervention, 2–142

Day to be purged, 2–143

dDTIIntState, 2–143

delayBetweenRetrans, 2–143

deltaUtc, 2–144

detectionFunction, 2–144

directedRetry, 2–145

directedRetryModeUsed, 2–146

directedRetryPrio, 2–147

directory, 2–147

distHreqt, 2–148

distWtsList, 2–149

diversity, 2–150

Index of parameters Nortel Networks Confidentialx

PE/DCL/DD/0124411–9001–124


dLPwrValue, 2–150

drxTimerMax, 2–151

dtxMode, 2–152

duplex link state, 2–152

duration, 2–152

dwAckTime, 2–153

Eearly classmark sending, 2–154

efd, efd, 2–154

efdType, 2–155

eftmd, 2–156 omc, 2–156 software, 2–157

emergencyCallPriority, 2–158

eMLPPThreshold, 2–159

encrypAlgoAsscomp, 2–159

encrypAlgoCiphModComp, 2–159

encrypAlgoHoperf, 2–160

encrypAlgoHoreq, 2–160

encryptionAlgorSupported, 2–160

End date, 2–161

end date, 2–161

End of probative Phase Type, 2–161

end timejob, 2–162 system session log, 2–162

endAlarmFilter, 2–162

endAlarmThresholdmdWarning (excessiveAnomalyRate), 2–163 mdWarning (outOfRangeCounter), 2–163

endCounterThreshold, 2–164

endSearchTimeDisplay custom report, 2–164 Display raw report, 2–164 List available permanent observations, 2–165 List available temporary observations, 2–165 List observation messages, 2–166

endSessionCriteriaType, 2–166

enhancedTRAUFrameIndication, 2–167

Index of parametersNortel Networks Confidential xi


equipment processor number, 2–167

error concealment unit, 2–167

errorCorrectionMethod, 2–168

exclusive interval of codano, 2–168

exclusive list of codano, 2–168

executableSoftwareId, 2–168

executableSoftwareName, 2–169

extCommsInt, 2–169

extended cell, 2–170

external alarm configuration, 2–170

external battery cabinet, 2–172

externalTime, 2–172

FFamily, 2–175

faultNumber, 2–176

fhsRef, 2–177

forced handover algo, 2–178

frequencyHoppingSystem, 2–178

Ggeographical coordinates

bsc, 2–179 btsSiteManager, 2–179 md, 2–179 pcusn, 2–179 transcoder, 2–179

gprsAvgParam, 2–180

gprsBtsExtendedConf, 2–180

gprsBtsLockExtendedConf , 2–181

gprsCellActivation, 2–181

gprsPcuCrossConnectList, 2–181

gprsPcuLockExtendedConf, 2–182

gprsPermittedAccess, 2–182

gprsPreemption, 2–182

gprsPreemptionProtection, 2–183

gprsPriority, 2–183

gprsTimerWaitPUAM, 2–183

gprsTimerWaitRLC, 2–184

gprsTranscvLockBtsExtendedConf , 2–184

Index of parameters Nortel Networks Confidentialxii

PE/DCL/DD/0124411–9001–124


HHandOver from signalling channel, 2–185

handOverControl, 2–185

hardware configuration, 2–186

hardwareRefbtsSiteManager, 2–186 transceiverEquipment, 2–186 transcoderBoard, 2–186

hexa text, 2–187

hoMargin, 2–187

hoMarginBeg, 2–187

hoMarginDist, 2–188

hoMarginRxLev, 2–188

hoMarginRxQual, 2–188

hoMarginTiering, 2–188

hoMarginTrafficOffset, 2–189

HOPingpongCombination, 2–189

HOPingpongTimeRejection, 2–190

hoppingSequenceNumber, 2–191

HOSecondBestCellConfiguration, 2–191

hoTrafficbsc, 2–192 bts, 2–192

Iidentifier

short message, 2–193 software, 2–193 software–bsc, 2–193

iemId, 2–193

iMSIAttachDetach, 2–194

inactivity timeout, 2–194

inclusive interval of codano, 2–194

inclusive list of codano, 2–194

incomingHandOver, 2–195

inhibitRequest, 2–195

inId, 2–195

interBscDirectedRetry, 2–195

interBscDirectedRetryFromCell, 2–196

interCellHOExtPriority, 2–196

Index of parametersNortel Networks Confidential xiii


interCellHOIntPriority, 2–196

interferenceType, 2–197

interferer cancel algo usage, 2–197

internal DMUX alarm state, 2–197

internal DMUX state, 2–199

internal PCM states, 2–199

internal switching matrix, 2–199

interOmuEtherlinkOper, 2–200

intraBscDirectedRetry, 2–200

intraBscDirectedRetryFromCell, 2–200

intraCell, 2–201

intraCellHOIntPriority, 2–201

intraCellQueueing, 2–201

intraCellSDCCH, 2–202

Jjob, 2–203

jobResult, 2–203

Llabel

md – Archive, 2–204 md – Display archive list, 2–204 md – Display label, 2–204 md – Restore, 2–204 md – Set label, 2–204 omc – Archive, 2–204 omc – Display archive list, 2–204 omc – Display label, 2–204 omc – Restore, 2–204 omc – Set label, 2–204

language, 2–204

lapdConcentration, 2–205

lapdLink, 2–206

lapdLinkCallPLoad, 2–207

lapdLinkOMLRefbtsSiteManager, 2–207 transceiverEquipment, 2–208 transcoder, 2–208

lapdLinkRSLRef, 2–209

lapdTerminalNumber, 2–210

Index of parameters Nortel Networks Confidentialxiv

PE/DCL/DD/0124411–9001–124


layer3MsgCyphModComp, 2–211

Level to process, 2–211

lightning protection, 2–211

line, 2–211

locationAreaCodeadjacentCellHandOver, 2–212 adjacentCellReselection, 2–212 bts, 2–212

log, log, 2–213

logFullAction, 2–213

longTbfLossThroughput, 2–214

longTbfSizeThreshold, 2–214

lRxLevDLH, 2–214

lRxLevDLP, 2–215

lRxLevULH, 2–215

lRxLevULP, 2–216

lRxQualDLH, 2–216

lRxQualDLP, 2–217

lRxQualULH, 2–217

lRxQualULP, 2–217

lsaRc Reference, 2–218

lsaRcId, 2–218

Mmachine name

job, 2–219 jobResult, 2–219

mainNetworkBand, 2–219

maio, 2–219

managedObjectClassalarmRecord, 2–220 mdScanReportRecord, 2–220 observationFileReadyRecord, 2–220 stateChangeRecord, 2–220 traceFileReadyRecord, 2–220 traceLogRecord, 2–220

managedObjectInstancealarmRecord, 2–220 mdScanReportRecord, 2–220 observationFileReadyRecord, 2–220 stateChangeRecord, 2–220 traceFileReadyRecord, 2–220 traceLogRecord, 2–220

Index of parametersNortel Networks Confidential xv


Manager address type, 2–221

Manager addresses, 2–221

managerServer, 2–221

manufacturerIntervention, 2–221

marking type, 2–222

max log size, 2–222

maxAdjCHOARMPerBts, 2–222

maxBscPerNetwork, 2–222

maxBsTransmitPowerInnerZone, bts, 2–223

maxBtsPerBtsSM, 2–223

maxBtsPerNetwork, 2–223

maxDnTbfP1P2Threshold, 2–223

maxDnTbfPerTs, 2–224

maxDwAssign, 2–224

maxFileSize, 2–224

maximum acknowledgment time, 2–225

maximum alarm number, 2–225

maximum clear time, 2–225

maximum event time, 2–226

maximum MD notification number, 2–226

maximum OMC notification number, 2–226

maximum reception time, 2–227

maxLapdChPerBtsSM, 2–227

maxNbOfCells, 2–228

maxNbrConsMess, 2–227

maxNbrPDAAssig, 2–228

maxNbrRLCEmptyBlock, 2–229

maxNbrWithoutVchange, 2–229

maxNumberRetransmission, 2–229

maxPcmCPerBtsSM, 2–230

maxPcmCPerTranscd, 2–230

maxRACH, 2–230

maxRowCount, 2–230

maxSigLPerSigLS, 2–231

maxTeiPerLapdCh, 2–231

maxTranscdBPerTranscd, 2–231

maxTranscdPerBsc, 2–231

maxUpTbfP1P2Threshold, 2–232

maxUpTbfPerTs, 2–232

md, 2–232

Index of parameters Nortel Networks Confidentialxvi

PE/DCL/DD/0124411–9001–124


MD notification number, 2–232

mdArchive, 2–233

mdConfirm, 2–233

mdFileName, 2–233

mdGranularityPeriodmdScanner, 2–234 mdScanReportRecord, 2–234 observationFileReadyRecord, 2–235

mdId, 2–236

mdLog, 2–236

mdObjectListDisplay xxx report, 2–237 List observation messages, 2–237 mdScanner, 2–236

mdScanner, 2–237

mdScannerTypeDisplay xxx report, 2–238 List observation messages, 2–238 Load formulae, 2–239 mdScanner, 2–239

mdStorageDuration, 2–240

mdTransferMode, 2–240

mdWarning, mdWarning, 2–240

measurementProcAlgorithm, 2–241

mergeEftmd – Create EFT, 2–241 md – Validate EFT, 2–241 omc – Download and validate EFT from gigatape to md, 2–242

microCellCaptureTimer, 2–242

microCellStability, 2–242

minimum acknowledgment time, 2–243

minimum alarm number, 2–243

minimum clear time, 2–243

minimum event time, 2–244

minimum MD notification number, 2–244

minimum OMC notification number, 2–244

minimum reception time, 2–245

minNbOfTDMA, 2–245

minNbrGprsTs, 2–245

missDistWt, 2–246

missRxLevWt, 2–246

missRxQualWt, 2–247

Index of parametersNortel Networks Confidential xvii


mmsId, 2–247

mmsUsage, 2–247

mobileAllocation, 2–248

mobileCountryCodeadjacentCellHandOver, 2–248 adjacentCellReselection, 2–249 bsc, 2–249 bts, 2–250

mobileNetworkCodeadjacentCellHandOver, 2–250 adjacentCellReselection, 2–251 bsc, 2–251 bts, 2–251

modeModifyMandatory, 2–252

monitoredObjectClass, 2–252

monitoredObjectInstance, 2–253

monitoredSpecificProblemsList, 2–253

month, 2–253

msBtsDistanceInterCell, 2–253

msCapWeightActive, 2–254

msRangeMax, 2–254

msTxPwrMax, 2–255

msTxPwrMax2ndBand, 2–255

msTxPwrMaxCCH, 2–256

msTxPwrMaxCell, 2–257

multi band reporting, 2–258

multiple site, 2–258

multipleVocoders, 2–259

muxNumber, 2–259

NN3103, 2–260

N3105max, 2–260

nAvgl, 2–260

nAvgT, 2–261

nAvgW, 2–261

nbOfRepeat, 2–261

nbrFreeTchBeforeAnticipation, 2–262

nbrFreeTchToEndAnticipation, 2–262

nbrTch, 2–262

NCHPosition, 2–263

Index of parameters Nortel Networks Confidentialxviii

PE/DCL/DD/0124411–9001–124


network protocolUsed, 2–264

networkColourCodeadjacentCellHandOver, 2–264 bts, 2–265

networkIndicatorsignallingLinkSet, 2–265 signallingPoint, 2–266

new name, 2–266

new password 1st try, 2–266

new password 2nd try, 2–267

new power control algorithm, 2–267

next execution time, 2–268

night intervention, 2–268

noOfBlocksForAccessGrant, 2–268

noOfMultiframesBetweenPaging, 2–269

notAllowedAccessClasses, 2–269

notification numberalarmRecord, 2–269 mdScanReportRecord, 2–269 observationFileReadyRecord, 2–269 stateChangeRecord, 2–269 traceFileReadyRecord, 2–269 traceLogRecord, 2–269

notification type, 2–270

number of records, 2–270

numberOfEnabledHDLCPorts, iem, 2–270

numberOfPwciSamples, 2–271

numberOfSlotsSpreadTrans, 2–271

numberOfTCHFreeBeforeCongestion, 2–273

numberOfTCHFreeToEndCongestion, 2–273

numberOfTCHQueuedBeforeCongestion, 2–274

numberOfTCHQueuedToEndCongestion, 2–274

OObject Filter List, 2–276

objectClassalarmRecord, 2–275 mdScanReportRecord, 2–275 observationFileReadyRecord, 2–275 stateChangeRecord, 2–275 traceFileReadyRecord, 2–275 traceLogRecord, 2–275

Index of parametersNortel Networks Confidential xix


objectInstance, 2–275

objects, 2–276

objects assigned, 2–277

observation typebscCounterList, 2–277 report template, 2–277

Observed counters, 2–277

Observed object class, 2–278

occupationState, 2–278

offsetLoad, 2–278

offsetPriority, 2–279

OMC notification number, 2–279

omuId, 2–279

on error, 2–279

operationalStateatmRm, 2–280 bsc, 2–280 bscMdInterface, 2–281 bts, 2–281 btsSiteManager, 2–282 callPathTrace, 2–282 cc, 2–283 cem, 2–283 cn, 2–284 efd, 2–284 g3BscEqp, 2–284 g3Transcoder, 2–285 iem, 2–285 in, 2–286 lapdLink, 2–286 log, 2–287 lsaRc, 2–287 mdScanner, 2–288 mms, 2–288 omu, 2–288 pcmCircuit, 2–289 pcu, 2–290 pcusn, 2–290 signallingLink, 2–291 sw8kRm, 2–291 tmu, 2–292 traceControl, 2–292 transceiver, 2–293 transceiverEquipment, 2–293 transcoder, 2–294 transcoderBoard, 2–294 trm, 2–295 xtp, 2–295

Index of parameters Nortel Networks Confidentialxx

PE/DCL/DD/0124411–9001–124


otherServicesPriority, 2–296

output classesterminal profile, 2–296 user profile, 2–297

owner, 2–297

PpacketAckTime, 2–298

pagingOnCell, 2–298

pan, 2–298

panDec, 2–298

panInc, 2–299

panMax, 2–299

parameter(s), 2–299

partialRecordCriteriaType, 2–300

particular intervention, 2–300

passive chain disk state, 2–4

passive chain Dmux state, 2–4

passive chain ECI board state, 2–5

passive chain REM link state, 2–5

passive chain Sic board state, 2–5

passive chain sic channels state, 2–5

passive chain sls board state, 2–5

passive chain state, 2–6

passive chain switching capacity, 2–6

passive chain tcu accessibility, 2–6

passive chain ute board state, 2–6

passworduser profile – Change password, 2–300 user profile – Create/Set, 2–301

password duration, 2–301

pcmCircuitpcmCircuit (A interface), 2–302 pcmCircuit (Abis, Ater, and Agprs interfaces), 2–301

pcmCircuitBsc, 2–303

pcmCircuitBtsSiteManager, 2–304

pcmCircuitIdlapdLink, 2–304 signallingLink, 2–304 transcoder, 2–305 xtp, 2–305

Index of parametersNortel Networks Confidential xxi


pcmErrorCorrection, 2–306

pcmNbr, 2–306

pcmTimeSlotNumber, 2–306

pcmType, 2–307

pcu, 2–307

pcuLapdEqptRefList, 2–308

pcusn, 2–308

pcuSNName, 2–308

pcuSNReserved1, 2–309

pcuSNReserved2, 2–309

penaltyTime, 2–309

perceived severity, 2–310

periodCCCHLoadIndication, 2–310

periodicity, 2–310

plmnPermitted, 2–310

PODType, 2–311

pointCodesignallingLinkSet, 2–311 signallingPoint, 2–311

port0X25Status, 2–312

port1X25Status, 2–312

portChosen, 2–313

portEthernetOperational, 2–311

portEthernetStatus, 2–312

portUsed, 2–313

positionInShelf, iem, 2–313

powerBudgetInterCell, 2–314

powerClass, 2–314

powerControl, powerControl, 2–315

powerControlIndicator, 2–315

powerDownlink, 2–316

powerIncrStepSize, 2–316

powerRedStepSize, 2–316

powerUplink, 2–317

preemptionAuthor, 2–317

preSynchroTimingAdvance, adjacentCellHandOver, 2–317

priority, 2–318

privateMmsOmuRef, 2–318

probable cause, 2–318

processorLoadSupConf, 2–320

Index of parameters Nortel Networks Confidentialxxii

PE/DCL/DD/0124411–9001–124


RrACHLoadAveragingSlots, 2–322

radChanSelIntThreshold, 2–322

radioAllocator, 2–323

radioLinkTimeOut, 2–324

radioSiteMask, 2–325

radioSiteName, 2–326

radResSupBusyTimer, 2–326

radResSupervision, 2–327

radResSupFreeTimer, 2–327

reception time, 2–327

Record reference, 2–328

redundantPcmNumber, 2–328

redundantPcmPresence, 2–328

refPeriodalarm criteria, 2–329 mdWarning (excessiveAnomalyRate), 2–329

relatedSoftwares, 2–329

relay, 2–330

remoteSsuState, 2–330

repetition rate, 2–330

Report range, 2–331

report template, report template, 2–331

reportObjLevel, 2–331

reserved1pcu, 2–331 transceiver, 2–332

reserved2pcu, 2–332 transceiver, 2–332

reserved3bts, 2–333 pcu, 2–333 transceiver, 2–333



Index of parametersNortel Networks Confidential xxiii


resetCircuitRepeat, 2–336

retransDuration, 2–336

retry on error, 2–336

rlf1, 2–337

rlf2, 2–337

rlf3, 2–338

rmpConfState, 2–338

rndAccTimAdvThreshold, 2–339

routingArea, 2–339

runCallClear, 2–340

runHandOver, 2–340

runPwrControl, 2–340

rxLevAccessMin, 2–341

rxLevDLIH, 2–341

rxLevDLPBGT, 2–342

rxLevHreqave, 2–342

rxLevHreqaveBeg, 2–343

rxLevHreqt, 2–343

rxLevMinCell, 2–344

rxLevULIH, 2–344

rxLevWtsList, 2–345

Ssapi, 2–346

scannerIdDisplay xxx report, 2–346 List observation messages, 2–346

sequenceNumber, 2–347

serial number, short message – Display broadcast characteristics, 2–347 , 2–348

session context saving mode, 2–348

shelfNumber, mms, 2–348

short message, 2–349

sicBoardsInt, 2–349

signallingLink, 2–350

signallingLinkResState, 2–351

signallingLinkSet, 2–351

signallingPoint, 2–352

signallingPointType, 2–352

signallingTerminalNumber, 2–353

Index of parameters Nortel Networks Confidentialxxiv

PE/DCL/DD/0124411–9001–124


sigPReserved1, 2–353

sigPReserved2, 2–354

siteGsmFctList, 2–354

siteName, 2–355

slc, 2–356

small to large zone HO priority, 2–356

smoke detector, 2–356

smsCB, 2–357

software, 2–358

softwareLabel, 2–359

source indicator, 2–359

specific problems, 2–359

speechModebts, 2–360 signallingPoint, 2–360

speechOnHoppingTs, 2–361

speechVersionAsscomp, 2–361

speechVersionHoperf, 2–361

speechVersionHoreq, 2–361

speechVersionHorqd, 2–362

standard indicator AdjCadjacentCellHandOver, 2–362 adjacentCellReselection, 2–362

standardIndicator, 2–363

standbyStatus, iem, 2–365

start date, 2–365

start timejob, 2–366 System session log, 2–366

startAlarmFilter, 2–367

startAlarmThresholdmdWarning (excessiveAnomalyRate), 2–368 mdWarning (outOfRangeCounter), 2–368

startCounterThreshold, 2–369

startTimelog, 2–369 mdScanner, 2–369

stopTimelog, 2–370 mdScanner, 2–370

subChanId, 2–370

subject, 2–371

Index of parametersNortel Networks Confidential xxv


Suffix, 2–371 summary, 2–371

supportingTransceiverEquipment, 2–372 sw8kRmId, 2–372

sWVersionBackUp, 2–373 sWVersionFallBack, 2–373

sWVersionNew, 2–373 sWVersionRunning, 2–374

synchronized, 2–375 synchronizing PCM, 2–376

syntheticFaultNumber, 2–376

system state, 2–376

Tt3101, 2–377

t3103, 2–377 t3107, 2–378

t3109, 2–378 t3111, 2–379

t3122, 2–379 T3172, 2–379

target Bda, 2–380 teiBtsSiteManager, 2–380

teiLapdLink, 2–381 teiTransceiverEqpt, 2–381

teiTranscoder, 2–382

temporaryOffset, 2–382 terminal name, 2–382

terminal profile, 2–383 text

commandFile, 2–383 short message, 2–383 user message, 2–383

TFH or RWM, 2–383

thresholdCCCHLoadIndication, 2–384 thresholdInterference, 2–384

thresholdType, 2–385

timeBetweenHOConfiguration, 2–386 timerPeriodicUpdateMS, 2–386

timeSlotNumberlapdLink, 2–386 signallingLink, 2–387 xtp, 2–387

Index of parameters Nortel Networks Confidentialxxvi

PE/DCL/DD/0124411–9001–124


tmuId, 2–388

traceConstraintList, 2–388

traceControl, 2–389

traceDayAccessed, 2–389

traceFileName, 2–389

traceInfoRequested, 2–390

traceReference, 2–390

traffic PCM allocation priority, 2–390

transcdBReserved1, 2–390

transcdBReserved2, 2–391

transceiver, 2–391 channel, 2–391

transceiver equipment classtransceiverEquipment, 2–392 transceiverZone, 2–393

transceiver zone Ref, 2–393

transceiverEquipmentsoftware, 2–394 transceiverEquipment, 2–394

transceiverZone, 2–395

transcoderpcmCircuit, 2–396 transcoder, 2–397 transcoderBoard, 2–397

transcoder2GEqptId, 2–396

transcoder3GEqptId, 2–396

transcoderAlarmList, 2–398

transcoderAlarmMask, 2–398

transcoderBoard, 2–399 software, 2–399

transcoderBoardIntState, 2–399

transcoderIdsignallingLink, 2–400 xtp, 2–400

transcoderIntPcmIntState, 2–400

transcoderMatrix, 2–401

transcvEReserved1, 2–403

transcvEReserved2, 2–403

trmId, 2–403

tSCBNumber, 2–404

tSCBUse, 2–404

tsConfiguration, 2–404

Index of parametersNortel Networks Confidential xxvii


txPowerMaxReduction, 2–405

typemd – Archive, 2–406 md – Restore, 2–406 omc – Archive, 2–407 omc – Restore, 2–407 report template, 2–408

Type of data to be purged, 2–408

Type of display, 2–408

UunequippedCircuit, 2–415

unknownNCellWarning, 2–415

unmasked users alarms, 2–416

upAckTime, 2–416

upgradeStatus, omu, 2–417

uplinkMappingChannelNumber, 2–417

uplinkMappingFreq, 2–417

uplinkMappingMeasurementMode, 2–418

uplinkMappingProcessingMode, 2–418

uplinkPowerControl, 2–418

uRxLevDLP, 2–419

uRxLevULP, 2–419

uRxQualDLP, 2–420

uRxQualULP, 2–420

usageStatecallPathTrace, 2–421 xtp, 2–421

use default list, 2–421

user name, 2–422

user profile, 2–422

usernamejob, 2–422 jobResult, 2–422

Vversion, 2–423

voiceBroadcastService, 2–423

voiceGroupCallService , 2–423

VSWR meter, 2–424

Index of parameters Nortel Networks Confidentialxxviii

PE/DCL/DD/0124411–9001–124


Wworkstation name, 2–425

XX25Port0Operational, 2–426

X25Port1Operational, 2–426

xSCBConfiguration, 2–427

xSCBNumber, 2–427

xSCBUse, 2–427

xtp, 2–428

ZZI bss

terminal profile, 2–430 user profile, 2–430

ZI omcterminal profile, 2–431 user profile, 2–431

zone frequency hopping, 2–431

zone frequency threshold, 2–431

zone Tx power max reduction, 2–432

Wireless Service Provider SolutionsBSS Parameter Dictionary

Copyright 2000–2002 Nortel Networks, All Rights Reserved

NORTEL NETWORKS CONFIDENTIAL:

The information contained in this document is the property of NortelNetworks. Except as specifically authorized in writing by NortelNetworks, the holder of this document shall keep the informationcontained herein confidential and shall protect same in whole or in partfrom disclosure and dissemination to third parties and use for evaluation,operation and maintenance purposes only.

You may not reproduce, represent, or download through any means, theinformation contained herein in any way or in any form without priorwritten consent of Nortel Networks.

The following are trademarks of Nortel Networks: *NORTELNETWORKS, the NORTEL NETWORKS corporate logo, the NORTELGlobemark, UNIFIED NETWORKS, DMS, DMS–MSC, BSC6000,S2000, S4000, S8000. GSM is a trademark of France Telecom.Sun, Ultrastation are registered trademarks of Sun Microsystems, Inc.All SPARC trademarks are used under license and are trademarks orregistered trademarks of SPARC International, Inc. in the United Statesand other countries. Sybase is a registered trademark of Sybase, Inc.Windows is a U.S. registered trademark of Microsoft Corp.All other brand and product names are trademarks or registredtrademarks of their respective holders.

Publication ReferencePE/DCL/DD/0124 411–9001–12413.04/ENMarch 2002Printed in France

For more information, please contact:

For all countries, except USA:

Documentation Department1, Place des Frères MontgolfierGUYANCOURT78928 YVELINES CEDEX 9FRANCEEmail : umts–[email protected] : (33) (1) 39–44–50–29

In the USA:

2221 Lakeside BoulevardRichardson TX 75082USATel: 1–800–4 NORTEL1–800–466–7838 or (972) 684–5935

Internet Address:

http://www.nortelnetworks.com

Documents

Nortel GSM BSS 13 Parameter Dictionary