Nortel GSM BSS Parameter Reference: Global System For Mobile Communications (GSM)

Global System for Mobile Communications (GSM)
Nortel GSM BSS Parameter Reference

Release: 17.0 Document Revision: 17.09
www.nortel.com
411-9001-124 .
Global System for Mobile Communications (GSM) Release: 17.0 Publication: 411-9001-124 Document status: Standard Document release date: 12 March 2008 Copyright 1999, 2008 Nortel Networks All Rights Reserved.
Sourced in Canada, France, and the United States of America. LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice. Nortel, the Nortel logo, the Globemark, S2000, and S8000 are trademarks of Nortel Networks. All other trademarks are the property of their respective owners.
Contents
New in this release
Features 33 GSM to UMTS handover (2473) 34 Enhanced measurement report (EMS) support (21531) 35 EDGE - Dynamic Abis per site (25203) 35 On-line TMU load reconfiguration from OMC-BSC3000 (26530) 36 Downlink voice quality monitoring (27017) 36 PCUSN-54 : new PCUSN configuration (T1) (27222) 36 Support of A5/3 ciphering key (27392) 36 Novel Adaptive Receiver (27888) 36 Permanent AAL-1 self-testing to improve hardware failure detection BSC 3000 (28319) 36 PCUSN-54 : new PCUSN configuration (E1) (28727) 37 Signaling Link GET Dynamic Data Enhancement (29722) 37 AMR-HR on pre-empted PDTCH (30169) 37 Advanced Call Drop Analysis (32277) 37 Joint Diversity (32280) 37 CEM2 combined CEM and SRT boards (32291) 38 BSC 3000 optical carriers (32302) 38 BTS 6000 Differenciation in OMC-R (32361) 38 S4000, S2000, and S2000E removal (32730) 38 Software preparation for BSC 3000 optical carrier introduction (32736) 38 Shared disks scan for bad blocks prevention (33285) 38 TCU 3000 optical carriers (33303) 39 BSS paging coordination (34160) 39 BTS 18000/6000 Smart Power Management (34208) 40 AMR feature lock at OMC-R (34433) 40 EDGE feature lock at OMC-R (34434) 40 RM family renaming management at OMC (34439) 41 BSC and TCU 2G End Of Life (34649) 41 Other changes 41 gsmToUmtsReselection 41 Semantic check 41 hoPingpongCombination 41
Global System for Mobile Communications (GSM) Nortel GSM BSS Parameter Reference 411-9001-124 17.09 Standard 12 March 2008
Copyright 1999, 2008 Nortel Networks
33
4 microCellCaptureTimer and microCellStability 41 upgradeStatus 42 Others 42
Introduction Chapter 1 Introduction

1.1 Network configuration objects and their parameters 1.2 Different types of configuration parameters 50 1.3 Description of dictionary entries 51 1.3.1 Header line 51 1.3.2 Main body of entries 52 A 55 abisSpy Class 3 55 absoluteRFChannelNo Class 2 55 access time end 56 access time start 56 accessClassCongestion Class 3 57 accessibilityState 57 acknowledged by 57 acknowledgment time 58 activationObject 58 activationObject 58 adaptiveReceiver Class 59 additional supervised PCM 0 Class 2 59 additional supervised PCM 1 Class 2 60 additional supervised PCM 2 Class 2 60 additional supervised PCM 3 Class 2 61 additional supervised PCM 4 Class 2 62 additional supervised PCM 5 Class 2 62 additional unmasked users alarms Class 2 addresses 64 adjacent cell umbrella ref Class 3 64 adjacentCellHandOver 65 adjacentCellHandOverId 65 adjacentCellReselection 66 adjacentCellReselectionId 66 administrativeState 67 administrativeState 67 administrativeState 67 administrativeState 68 administrativeState 68 administrativeState 70 45
43 45
Chapter 2 Parameters listed in alphabetical order
55
63
5 administrativeState 71 administrativeState 72 administrativeState 72 administrativeState 72 administrativeState 73 administrativeState 73 administrativeState 73 administrativeState 73 administrativeState 74 administrativeState 74 administrativeState 74 administrativeState 74 administrativeState 75 administrativeState 75 administrativeState 75 administrativeState 75 administrativeState 76 administrativeState 76 administrativeState 76 administrativeState 76 administrativeState 77 administrativeState 77 administrativeState 77 administrativeState 77 administrativeState 78 administrativeState 79 administrativeState 80 administrativeState 80 agprsFilterCoefficient Class 3 81 agprsHysteresis Class 3 81 agprsThreshold Class 3 81 agprsTsSharingProtection Class 2 81 agpsTimer Class 3 82 alarm criteria 82 alarm criteria 83 alarm number 83 alarm severity 84 alarm state 84 alarmDuration 84 alarmPriority 84 allocationState 85 allocPriorityTable Class 3 86 allocPriorityThreshold Class 3 86 allocPriorityTimers Class 3 87
6 allocWaitThreshold Class 3 87 allOtherCasesPriority Class 3 87 amrAdaptationSet Class 3 88 amrDirectAllocIntRxLevDL Class 3 88 amrDirectAllocIntRxLevUL Class 3 89 amrDirectAllocRxLevDL Class 3 89 amrDirectAllocRxLevUL Class 3 89 amrDlFrAdaptationSet class 3 90 amrDlHrAdaptationSet class 3 90 amrFRIntercellCodecMode Class 3 90 amrFRIntracellCodecMode Class 3 91 amrHRIntercellCodecMode Class 3 91 amrHRToFRIntraCodecMode Class 3 91 amriRxLevDLH Class 3 92 amriRxLevULH Class 3 92 amrReserved1 93 amrReserved2 Class 3 93 amrUlFrAdaptationSet class 3 94 amrUlHrAdaptationSet class 3 94 answerPagingPriority Class 3 94 architecture 95 assignRequestPriority Class 3 95 associatedLog 95 associatedTMUPosition 96 aterLapd 96 atmRm 96 atmRmId 97 attenuation Class 2 97 auditBdaStatus 97 auditState 98 authorised user 98 availabilityStatus 98 availabilityStatus 98 availabilityStatus 99 availabilityStatus 99 availabilityStatus 99 availabilityStatus 100 availabilityStatus 100 availabilityStatus 100 availabilityStatus 100 available synchronization sources 101 averagingPeriod Class 2 101 B 101 backup manager addresses 101
7 backupServer 102 baseColourCode Class 3 102 baseColourCode Class 2 102 batteryRemoteControllerPresence Class 2 103 bCCHFrequency Class 3 103 bCCHFrequency Class 3 105 bCCHFrequency Class 2 105 bckgDLLayer3WindowSize Class 3 106 bdaNewBscState 107 bdaSelected 108 bdaState 108 bdaVersionBuild 109 bdaVersionNumber 109 beacBatteryRemoteControllerPresence Class 2 110 beginning date 110 beginSearchTime 110 beginSearchTime 111 beginSearchTime 111 beginSearchTime 111 beginSearchTime 112 bEPPeriod Class 3 112 biZonePowerOffset Class 3 113 biZonePowerOffset Class 3 113 bsc3GEqpt 114 bsc3GEqptId 114 bsc 114 bsc 115 bsc equipment name 115 bscList 116 bsc model 117 bscNumber 117 bscArchitecture Class 0 117 bscCapacityReduction Class 3 118 bscCounterList 118 bscDateTime 119 bscGprsActivation Class 3 119 bscHighSwitchingCapacity Class 3 119 bscHopReconfUse Class 1 120 bscIPFirstAdr Class 2 120 bscIPSecondAdr Class 2 121 bscList 121 bscLog 121 bscLogId 122 bscMdInterface 122
8 bscMdInterfaceRef 122 bscMdInterfaceVersionNumber 123 bscMSAccessClassBarringFunction Class 3 123 bscName 123 bscPcuPcmRefList Class 2 124 bscQueueingOption Class 1 125 bscRefList 125 bscReset 126 bscSitePcmList Class 2 126 bscTimeSlot 127 bscUsedAdr 127 bsCvMax Class 3 127 bscX25PrefAdr Class 2 128 bscX25SecAdr Class 2 128 bsPowerControl Class 3 129 bssMapT1 Class 1 129 bssMapT4 Class 1 129 bssMapT7 Class 1 130 bssMapT8 Class 1 130 bssMapT12 Class 1 130 bssMapT13 Class 1 131 bssMapT19 Class 1 131 bssMapT20 Class 1 131 bssMapTchoke Class 1 132 bssPagingCoordination 132 bssSccpConnEst Class 1 132 bssSccpInactRx Class 1 133 bssSccpInactTx Class 1 133 bssSccpRelease Class 1 133 bssSccpSubSysTest Class 1 134 bsTxPwrMax Class 3 134 bts 136 bts 137 bts equipment name 138 bts list 139 btsSMSynchroMode Class 2 139 bts time between HO configuration Class 3 140 btsDescription 140 btsHopReconfRestart Class 2 140 btsIsHopping Class 2 141 btsMSAccessClassBarringFunction Class 3 142 btsReserved3 Class 3 142 btsReserved4 Class 3 142 btsSensitivity Class 3 142
9 btsSensitivityInnerZone Class 3 143 btsSiteManager 143 btsSiteManager 144 btsSiteManager model 145 btsSiteManagerList Class 2 145 btsThresholdHopReconf Class 2 145 btsWithCavity Class 2 146 buildState 146 C 147 callClearing Class 3 147 callDropActivation class 3 147 callPathObservationArea Class 2 148 callPathTrace 148 callPathTraceType Class 2 149 callReestablishment Class 3 149 callReestablishmentPriority Class 3 150 capacityAlarmThreshold 150 capacityTimeRejection Class 3 151 cause 151 cCCHGprsAtBtsLevel Class 3 151 cc 151 ccId 152 cellAllocation Class 2 152 cellBarQualify Class 3 153 cellBarred Class 3 154 cellDeletionCount Class 3 154 cellDtxDownLink Class 3 155 cellIdentity Class 3 155 cellIdentity Class 3 155 cellIdentity Class 2 155 cellName 156 cellPagingState 156 cellReselectHysteresis Class 3 157 cellReselectOffset Class 3 158 cellReselInd Class 3 159 cellThreshold Class 2 159 cellType Class 3 159 cellType Class 3 159 cemId 160 chain 160 chain 160 channel 161 channel state 161 channelReleaseOnAbisFailure 162
10 channelType Class 2 163 chanState 166 chosenChannelAsscomp Class 1 167 chosenChannelCompL3Info Class 1 167 chosenChannelHoPerf Class 1 168 chosenChannelHoReq Class 1 168 cic Class 0 168 cId Class 3 169 circuitGroupBlock Class 1 170 circularFileId 170 circularFileState 171 clear time 171 cleared by 171 clearing cause 171 cn 172 control Node Id 172 coderPoolConfiguration Class 2 172 coderPoolList 173 codingScheme Class 2 173 command classes 174 command line 174 command number 175 commandFile 175 commandFile 175 comment 175 comment 176 comments 176 compressedModeUTRAN Class 3 176 computeSyntheticCounters 176 concentAlgoExtMsRange Class 3 177 concentAlgoExtRxLev Class 3 177 concentAlgoIntMsRange Class 3 178 concentAlgoIntRxLev Class 3 178 concentric cell Class 2 179 condition 180 configRef Class 3 181 configRefList 182 configurationType 182 counter list 182 counter list filename 182 counterId 183 counters 183 counters 183 cpueNumber Class 0 or Class 1 (see note)
183
11 cpueOccurrence 184 cRC Class 0 184 creator 184 criteriaEventType 185 cSS7LocalSubSystemNumber Class 0 185 cSS7RemoteSubSystemNumber Class 0 185 CTU cable 186 current log size 186 current synchronization mode 186 currentChannelHorqd Class 1 187 cypherModeReject Class 1 187 D 187 dARPPh1Priority class 2 187 data non transparent mode Class 3 188 data non transparent mode Class 3 188 data transparent mode Class 3 188 data transparent mode Class 3 189 data14-4OnNoHoppingTs Class 3 189 date 189 date 190 date 190 date 190 date 190 day intervention 191 day to be purged 191 degradedCause 191 degradedCause 191 delayBetweenRetrans Class 2 192 delivery 192 deltaUtc 194 detectionFunction 194 directedRetry Class 3 194 directedRetryModeUsed Class 3 194 directedRetryPrio Class 3 195 directory 195 display Data Configuration 196 display Data Information 196 distHreqt Class 3 196 distributionActivation Class 3 196 distributionDuration Class 3 197 distributionTime Class 3 197 distributionQualityThreshold Class 3 198 distWtsList Class 3 199 diversity Class 2 200
12 dlGMSKMCS2UpperThreshold Class 3 200 dlGMSKMCS3UpperThreshold Class 3 200 dlMCS2UpperThreshold Class 3 201 dlMCS3UpperThreshold Class 3 201 dlMCS5UpperThreshold Class 3 201 dlMCS6UpperThreshold Class 3 201 dlMCS7UpperThreshold Class 3 202 dlMCS8UpperThreshold Class 3 202 diversityUTRAN Class 3 202 drxTimerMax Class 3 203 dtxMode Class 3 203 duration 204 dwAckTime Class 3 (packetAckTime) 204 dynamicAbis class 2 204 dynamicAgprsAllowed Class 2 205 E 205 early classmark sending Class 3 205 earlyClassmarkSendingUTRAN Class 3 206 edgeDataServiceType Class 2 206 edgeFavor Class 3 206 eDGEMixity Class 3 206 efd 207 efdType 207 egprsIrULActivation Class 3 208 egprsServices Class 3 209 emergencyCallPriority Class 3 209 emergencyCallRestricted Class 3 210 emergencyThreshold Class 3 210 eMLPPThreshold Class 3 210 enableRepeatedFacchFr Class 2 211 encrypAlgoAsscomp Class 1 211 encrypAlgoCiphModComp Class 1 211 encrypAlgoHoperf Class 1 212 encrypAlgoHoreq Class 1 212 encryptionAlgorSupported Class 0 212 encryptionAlgorSupported Class 3 213 end date 213 end date 213 end of probative Phase Type 214 end time 214 end time 214 endAlarmFilter 215 endAlarmThreshold 215 endAlarmThreshold 215
13 endCounterThreshold 216 endSearchTime 216 endSearchTime 217 endSearchTime 217 endSearchTime 218 endSearchTime 218 endSessionCriteriaDuration 218 endSessionCriteriaType 219 enhancedTRAUFrameIndication 219 enhCellTieringConfiguration 220 equipment identity 221 equipment processor number 222 error concealment unit Class 2 222 estimatedSiteLoad Class 3 222 exclusive interval of codano 223 exclusive list of codano 223 executableSoftware 223 executableSoftwareId 224 executableSoftwareName 224 extended cell Class 2 224 external alarm configuration Class 2 225 external battery cabinet Class 2 226 externalTime 226 extUtbfNoData Class 3 227 F 227 facchPowerOffset Class 2 227 Family 227 faultNumber 230 fDDARFCN Class 3 230 fDDMultiratReporting Class 3 231 fDDReportingThreshold Class 3 232 fDDReportingThreshold2 Class 3 232 fERThreshold1 Class 3 232 fERThreshold2 Class 3 233 fERThreshold3 Class 3 233 fERThreshold4 Class 3 234 fhsRef Class 2 234 filteredTrafficCoefficient Class 3 235 floor 235 flowControlMaxDelay 236 flowControlMaxRate 236 fnOffset class 2 236 forced handover algo Class 3 237 frAmrPriority Class 2 237
14 frequencyHoppingSystem 237 frPowerControlTargetMode Class 3 238 frPowerControlTargetModeDl Class 3 238 fullDlKa Class 3 239 G 239 geographical coordinates 239 geographical coordinates 240 gprsAvgParam Class 3 240 gprsCellActivation Class 3 241 gprsNetworkModeOperation Class 3 241 gprsPcuCrossConnectList Class 2 241 gprsPcuLockExtendedConf Class 2 242 gprsPermittedAccess Class 3 242 gprsPreemption Class 3 243 gprsPreemptionForHR Class 3 243 gprsPreemptionProtection Class 3 243 gprsPriority Class 2 (gprsTranscvLockExtendedConf) gprsState 244 gprsState 244 gsmToUmtsReselection Class 3 244 gsmToUMTSServiceHo Class 3 246 H 246 handOver from signalling channel Class 3 246 handOverControl 246 hardware configuration Class 2 247 hardwareRef Class 2 249 hardwareRef Class 2 249 hexa text 249 hoMargin Class 3 249 hoMarginAMR Class 3 250 hoMarginAMRUTRAN Class 3 250 hoMarginBeg Class 3 250 hoMarginDist Class 3 251 hoMarginDistUTRAN Class 3 251 hoMarginRxLev Class 3 251 hoMarginRxQual Class 3 251 hoMarginTiering Class 3 252 hoMarginRxLevUTRAN Class 3 252 hoMarginRxQualUTRAN Class 3 252 hoMarginTrafficOffset Class 3 253 hoMarginTrafficOffsetUTRAN Class 3 253 hoMarginUTRAN Class 3 253 hoPingpongCombination Class 3 254 hoPingpongCombinationUTRAN Class 3 255
244
15 hoPingpongTimeRejection Class 3 255 hoPingpongTimeRejectionUTRAN Class 3 255 hoRejectionTimeOverloadUTRAN Class 3 256 hoppingSequenceNumber Class 2 256 hoSecondBestCellConfiguration Class 3 257 hoTraffic Class 3 257 hoTraffic Class 3 257 hrAmrPriority Class 2 258 hrCellLoadEnd Class 3 258 hrCellLoadStart Class 3 259 hrPowerControlTargetMode Class 3 259 hrPowerControlTargetModeDl Class 3 260 hsaPcmList Class 3 260 hsaRc 262 I 262 identifier 262 identifier 262 identifier 262 identifier 263 iem 263 iemId 263 iMSIAttachDetach Class 2 263 in 264 inactivity timeout 264 inclusive interval of codano 264 inclusive list of codano 264 incomingHandOver Class 3 265 inhibitRequest 265 inId 265 initialMCSDL Class 3 265 initialMCSUL Class 3 266 interBscDirectedRetry Class 3 266 interBscDirectedRetryFromCell Class 3 266 interCellHOExtPriority Class 3 267 interCellHOIntPriority Class 3 267 interferenceType Class 3 267 interferenceMatrixRunningOnBsc 268 interferenceMatrixRunningOnBts 269 interferer cancel algo usage Class 2 271 interOmuEtherlinkOper 272 intraBscDirectedRetry Class 3 272 intraBscDirectedRetryFromCell Class 3 272 intraCell Class 3 273 intraCellHOIntPriority Class 3 273
16 intraCellQueueing Class 3 273 intraCellSDCCH Class 3 274 iom 274 J 274 job 274 jobResult 274 jokerPerMainTarget Class 3 275 L 275 label 275 language 276 lapdLink 276 lapdLinkOMLRef Class 2 277 lapdLinkOMLRef Class 2 277 lapdLinkRSLRef Class 2 278 lapdTerminalNumber Class 0 278 layer3MsgCyphModComp Class 1 279 lcsType Class 0 280 level to process 280 Licenses needed to put object in service Licenses used by this object 281 lightning protection Class 2 281 line 282 locationAreaCode Class 3 282 locationAreaCode Class 3 282 locationAreaCode Class 2 282 locationAreaCodeUTRAN Class 3 283 log 283 logFullAction 284 login command type 284 longTbfLossThroughput Class 3 284 longTbfSizeThreshold Class 3 284 lRxLevDLH Class 3 285 lRxLevDLP Class 3 285 lRxLevULH Class 3 285 lRxLevULP Class 3 285 lRxQualDLH Class 3 286 lRxQualDLP Class 3 286 lRxQualULH Class 3 286 lRxQualULP Class 3 287 lsaPcmList Class 3 287 lsaRc 289 lsaRcId 289 lsaRc Reference 289 M 289
281
17 machine name 289 machine name 290 mainNetworkBand Class 0 290 maio Class 2 290 managedObjectClass 291 managedObjectInstance 291 manager address type 291 manager addresses 292 managerServer 292 manufacturerIntervention 292 marking type 292 masterBtsSMId class 2 292 max log size 293 maxAdjCHOARMPerBts 293 maxBscPerNetwork 293 maxBsTransmitPowerInnerZone Class 3 293 maxBtsPerBtsSM 294 maxBtsPerNetwork 294 maxDnTbfP1P2Threshold Class 3 294 maxDnTbfPerTs Class 3 294 maxDwAssign Class 3 295 maxFileSize Class 2 295 maximum acknowledgment time 295 maximum alarm number 296 maximum clear time 296 maximum event time 296 maximum MD notification number 297 maximum OMC notification number 297 maximum reception time 297 maxLapdChPerBtsSM 297 maxNbrConsMess 298 maxNbOfCells Class 2 298 maxNbrPDAAssig Class 2 (gprsTranscvLockExtendedConf) 298 maxNbrPUDWithoutVchange Class 2 (NN0002Max) gprsTranscvLockExtended Conf 299 maxNbrRLCEmptyBlock Class 2 (n3101Max) (gprsTranscvLockExtendedCon f) 299 maxNumberRetransmission Class 3 299 maxPcmCPerBtsSM 300 maxPcmCPerTranscd 300 maxRACH Class 3 300 maxRowCount 300 maxSigLPerSigLS 301 maxTeiPerLapdCh 301
18 maxTranscdBPerTranscd 301 maxTranscdPerBsc 301 maxUpTbfP1P2Threshold Class 3 302 maxUpTbfPerTs Class 3 302 md 302 md notification number 302 mdArchive 303 mdConfirm 303 mdFileName 303 mdGranularityPeriod 303 mdGranularityPeriod 304 mdGranularityPeriod 305 mdId 306 mdLog 306 mdObjectList 306 mdObjectList 307 mdObjectList 307 mdScanner 307 mdScannerType 308 mdScannerType 308 mdScannerType 308 mdScannerType 309 mdScannerType 309 mdStorageDuration 309 mdTransferMode 310 mdWarning 310 measurementProcAlgorithm Class 2 310 microCellCaptureTimer Class 3 311 microCellStability Class 3 312 minimum acknowledgment time 312 minimum alarm number 312 minimum clear time 313 minimum event time 313 minimum MD notification number 313 minimum OMC notification number 314 minimum reception time 314 minNbOfJokersPerConnectedMain Class 3 314 minNbOfTDMA Class 2 315 minNbrGprsTs Class 3 315 minTimeQualityIntraCellHO Class 3 315 missDistWt Class 3 316 missRxLevWt Class 3 316 missRxQualWt Class 3 317 mms 317
19 mmsId 317 mmsUsage 318 mobileAllocation Class 2 318 mobileCountryCode Class 3 318 mobileCountryCode Class 3 319 mobileCountryCode Class 1 319 mobileCountryCode Class 2 320 mobileCountryCodeUTRAN Class 3 320 mobileNetworkCode Class 3 320 mobileNetworkCode Class 3 321 mobileNetworkCode Class 1 321 mobileNetworkCode Class 2 321 mobileNetworkCodeUTRAN Class 3 322 modeModifyMandatory Class 3 322 monitoredObjectClass 323 monitoredObjectInstance 323 monitoredSpecificProblemsList 323 month 324 msBtsDistanceInterCell Class 3 324 msCapWeightActive Class 2 324 msLeakRate 324 msPowerClassToggle Class 3 325 msRangeMax Class 3 325 msTxPwrMax Class 3 325 msTxPwrMax2ndBand Class 2 326 msTxPwrMaxCCH Class 3 327 msTxPwrMaxCell Class 3 328 multi band reporting Class 3 328 multiple site 329 multipleVocoders Class 1 329 muxNumber Class 3 330 N 330 n3103 Class 3 330 n3105max Class 2 (gprsTranscvLockBtsExtendedConf) nACCActivation Class 3 331 nAvgl Class 3 (gprsAvgParam) 331 nAvgT Class 3 (gprsAvgParam) 331 nAvgW Class 3 (gprsAvgParam) 332 nbOfFramesForFER Class 3 332 nbOfRepeat Class 2 333 nbrFreeTchBeforeAnticipation Class 3 333 nbrFreeTchToEndAnticipation Class 3 334 nCapacityFRRequestedCodec Class 3 334 nCHPosition Class2 334
330
20 networkColourCode Class 3 335 networkColourCode Class 2 336 networkIndicator Class 1 336 new name 337 new password 1st try 337 new password 2nd try 337 new power control algorithm Class 3 338 next execution time 338 nFRRequestedCodec Class 3 339 nHRRequestedCodec Class 3 339 night intervention 339 noOfBlocksForAccessGrant Class 2 340 noOfMultiframesBetweenPaging Class 2 340 notAllowedAccessClasses Class 3 341 notification number 341 notification type 341 numberOfJokerDS0 Class 2 342 number of records 342 number of large reuse data channels Class 3 342 numberOfEnabledHDLCPorts 343 numberOfPwciSamples Class 3 343 numberOfSlotsSpreadTrans Class 3 344 numberOfTCHFreeBeforeCongestion Class 3 346 numberOfTCHFreeToEndCongestion Class 3 346 numberOfTCHQueuedBeforeCongestion Class 3 347 numberOfTCHQueuedToEndCongestion Class 3 347 Number of XTP under this BSS 347 nUsfExt Class 3 348 nwExtUtbf Class 3 348 O 348 objectClass 348 objectInstance 349 object Filter List 349 objects 350 objects assigned 350 observation type 350 observation type 351 observed counters 351 observed object class 351 occupationState 351 offsetLoad Class 3 352 offsetNeighbouringCell Class 3 352 offsetPriority Class 3 354 offsetPriorityUTRAN Class 3 354
21 oMC notification number 354 omuId 355 on error 355 onlyExtUtbf Class 3 355 onePhaseAccess Class 2 355 onePhaseDnMsCapability Class 3 356 operationalState 356 operationalState 357 operationalState 357 operationalState 358 operationalState 359 operationalState 359 operationalState 360 operationalState 360 operationalState 361 operationalState 361 operationalState 362 operationalState 362 operationalState 363 operationalState 363 operationalState 364 operationalState 364 operationalState 365 operationalState 365 operationalState 366 operationalState 366 operationalState 367 operationalState 367 operationalState 368 operationalState 368 operationalState 369 operationalState 369 operationalState 370 operationalState 370 operationalState 371 operationalState 371 operationalState 372 operationalState 373 operationalState 373 otherServicesPriority Class 3 374 output classes 374 output classes 375 owner 375 P 375
22 packetAckTime Class 3 375 packetFlowContext Class 3 376 packetSiStatus Class 3 377 pagingOnCell Class 3 377 pan Class 3 377 panDec Class 3 (pan) 377 panInc Class 3 (pan) 378 panMax Class 3 (pan) 378 parameter(s) 379 partialRecordCriteriaType Class 2 379 partialRecordCriteriaEventType 380 partialRecordCriteriaNbEvent 380 partialrecordCriteriaTimer 380 particular intervention 380 password 380 password 380 password duration 381 pcmCircuit 381 pcmCircuit 382 pcmCircuitBsc 383 pcmCircuitBtsSiteManager 383 pcmCircuitId 383 pcmCircuitId Class 2 383 pcmCircuitId Class 2 384 pcmErrorCorrection Class 2 384 pcmNbr Class 2 (gprsPcuCrossConnectList) 385 pcmTimeSlotNumber Class 2 385 pcmType Class 0 (BSC 3000) 385 pcu 386 pcuCellState 387 pcusn 387 pcuSNName 387 penaltyTime Class 3 388 perceived severity 389 periodicity 389 pfcActivation Class 2 389 pfcArp1ConversationalCSCallProtection Class 3 389 pfcArp1StreamingCSCallProtection Class 3 390 pfcArp2ConversationalCSCallProtection Class 3 390 pfcArp2StreamingCSCallProtection Class 3 390 pfcArp3ConversationalCSCallProtection Class 3 391 pfcArp3StreamingCSCallProtection Class 3 391 pfcFlowControlActivation Class 2 391 pfcMinNrtBandwidthPerTs Class 3 392
23 pfcMinNumberOfJokersforTsGuaranteedBitRate Class 3 392 pfcNrtRequestedDnMbrCounterThreshold Class 3 393 pfcNrtRequestedUpMbrCounterThreshold Class 3 393 pfcPreemptionRatioGold Class 3 394 pfcPreemptionRatioSilver Class 3 394 pfcRtDowngradeAllowed Class 3 394 pfcRtRequestedDnGbrCounterThreshold Class 3 395 pfcRtRequestedUpGbrCounterThreshold Class 3 395 pfcT6 Class 3 395 pfcT8 Class 3 396 pfcTsGuaranteedBitRateDl Class 3 396 pfcTsGuaranteedBitRateUl Class 3 396 plmnPermitted Class 3 397 pODType 397 pointCode Class 1 397 pointCode Class 1 397 port Ethernet operational 398 port Ethernet status 398 port 0 X25 status 398 port 1 X25 status 399 portChosen Class 2 399 portUsed 400 positionInShelf 400 powerBudgetInterCell Class 3 400 powerClass 400 powerControl 401 powerControlIndicator Class 3 401 powerIncrStepSizeUpLink Class 3 402 powerIncrStepSizeDownLink Class 3 403 powerRedStepSizeDownLink Class 3 403 powerRedStepSizeUpLink Class 3 404 preemptionAuthor Class 3 404 preemptionConfiguration Class 3 405 pRequestedCodec Class 3 405 preSynchroTimingAdvance Class 3 405 priority Class 2 406 privateMmsOmuRef 406 privilegedCell Class 3 406 probable cause 407 processor identity 409 pwciHrequave Class 3 409 qsearchC Class 3 410 R 411 radChanSelIntThreshold Class 3 411
24 radioLinkTimeOut Class 3 412 radioSiteMask Class 2 413 radioSiteMaskOffset Class 2 415 radioSiteName 416 radResSupBusyTimer Class 3 416 radResSupervision Class 3 417 radResSupFreeTimer Class 3 417 range 417 reception time 418 record reference 418 redundantPcmNumber 419 redundantPcmPresence Class 2 419 refPeriod 419 refPeriod 419 relatedSoftwares 420 relay 420 remoteSsuState 421 repetition rate 421 report range 421 report template 422 report type 422 reportObjLevel 422 reportTypeMeasurement Class 3 423 retransDuration Class 2 423 retry on error 423 rlf1 Class 2 424 rlf2 Class 2 424 rlf3 Class 2 425 rLCPolling Class 3 425 rmpConfState 426 rNCId Class 3 426 rndAccTimAdvThreshold Class 3 427 routingArea Class 2 427 rowPosition 428 runCallClear Class 3 428 runHandOver Class 3 428 runPwrControl Class 3 428 rxLevAccessMin Class 3 429 rxLevDLIH Class 3 429 rxLevDLPBGT Class 3 429 rxLevDLPbgtUTRAN Class 3 430 rxLevHreqave Class 3 430 rxLevHreqaveBeg Class3 430 rxLevHreqt Class 3 431
25 rxLevMinCell Class 3 431 rxLevMinCellUTRAN Class 3 431 rxLevNCellHreqaveBeg Class 3 432 rxLevRxQualDistributionActivation Class 3 432 rxLevULIH Class 3 432 rxLevWtsList Class 3 433 rxNCellHreqave Class 3 433 rxQualAveBeg Class 3 434 rxQualDLIH Class 3 434 rxQualHreqave Class 3 434 rxQualHreqt Class 3 435 rxQualULIH Class 3 435 rxQualThresholdDistribution Class 3 435 rxQualWtsList Class 3 436 S 436 sIkAssociatedTmuPortPosition 436 sIkATerResource 436 sacchPowerOffset Class 2 436 sacchPowerOffsetSelection Class 2 437 sapi 437 scannerId 437 scannerId 438 sCCPRoutingIndicator 438 scramblingCode Class 3 438 selfAdaptActivation Class 3 439 selfTuningObs Class 3 439 sequenceNumber 440 serial number 440 serial number 440 servingBandReporting Class 3 441 servingBandReportingOffset Class 3 441 servingFactorOffset Class 3 441 session context saving mode 442 sGSNRelease Class 3 442 shelfNumber 442 short message 443 signallingLink 443 signallingLinkId 444 signallingLinkResourcesStates 445 signallingLinkResState 445 signallingLinkResState field 446 signallingLinkSet 446 signallingPoint 446 sigPowerOverboost Class 3 447
26 site 447 siteGsmFctList Class 2 447 siteName 449 slkAResource field 450 slkAssociatedTmuPortPosition field 450 slkAssociatedTmuPortPosition 451 slkATerResource field 451 slkATerResource 451 slc Class 2 452 small to large zone HO priority Class 3 452 smartPowerManagementConfig parameter Class 3 452 smartPowerSwitchOffTimer Class 3 453 smoke detector Class 2 453 smsCB Class 3 453 software 454 softwareLabel 455 source indicator 455 specific problems 455 speechMode Class 3 456 speechMode Class 3 456 speechOnHoppingTs Class 3 457 speechVersionAsscomp Class 1 457 speechVersionHoperf Class 1 457 speechVersionHoreq Class 1 458 speechVersionHorqd Class 1 458 standard indicator AdjC Class 3 458 standard indicator AdjC Class 3 459 standardIndicator Class 2 459 standbyStatus 462 standbyStatus TMU 463 start date 463 start time 463 start time 464 startAlarmFilter 464 startAlarmThreshold 465 startAlarmThreshold 466 startCounterThreshold 466 startTime 466 startTime 467 stopTime 467 stopTime 467 subChanId 468 subject 468 suffix 468
27 summary 469 suspendResumeActivation Class 3 469 supportingTransceiverEquipment 469 sw8kRm 470 sw8kRmId 470 sWVersionBackUp 470 sWVersionFallBack 471 sWVersionNew 471 sWVersionRunning Class 2 472 synchronized Class 3 472 synchronizingHsaRc 473 synchronizing PCM 473 syntheticFaultNumber 473 systemInfoType2 Class 2 474 T 474 t3101 Class 3 474 t3103 Class 3 474 t3107 Class 3 475 t3109 Class 3 475 t3111 Class 3 475 t3121 Class 3 476 t3122 Class 3 476 t3168 Class 3 476 t3172 Class 3 477 t3192 Class 3 477 target Bda 477 teiBtsSiteManager Class 2 478 teiLapdLink 479 teiTransceiverEqpt Class 2 479 teiTranscoder Class 2 480 temporaryOffset Class 3 480 terminal name 480 terminal profile 481 text 481 text 481 text 481 tFH or RWM Class 2 481 tGMMKeepAlive Class 3 482 This BSS is using license 482 thresholdInterference Class 2 482 thresholdType 484 timeBetweenHOConfiguration Class 3 484 timerGcchNotif Class 3 484 timerPeriodicUpdateMS Class 3 485
28 timeSlotNumber 485 timeSlotNumber Class 2 485 timeSlotNumber 486 tmu 487 tmuId 487 tnOffset class 2 487 tNwExtUtbf Class 3 488 Total licenses for this OMC-R 488 Total unused licenses 488 traceConstraintList 489 traceControl 489 traceDayAccessed 490 traceFileName 490 traceInfoRequested 491 traceReference 491 traffic PCM allocation priority Class 2 491 transceiver 491 transceiver 492 transceiver equipment class Class 2 493 transceiver zone Ref Class 2 493 transceiverEquipment 494 transceiverEquipment 494 transceiver equipment class 495 transceiverZone 496 transcoder3GEqptId 497 transcoder 497 transcoder 497 transcoderArchitecture 498 transcoderId Class 2 498 transcoderId Class 2 499 transcoderMatrix 499 transparentSiteAttrib2 Class 2 501 transparentTeiAttrib2 Class 2 501 tResumeAck Class 3 502 trm 502 trmArchipelagoCalls 502 trmId 503 tsConfiguration 503 tSuspendAck Class 3 504 tUsfExt Class 3 504 txPowerMaxReduction Class 2 504 type 505 type 505 type 506
29 type 506 type 506 type of data to be purged 507 type of display 507 U 507 ulBepPeriod Class 2 507 ulGMSKMCS2UpperThreshold Class 3 507 ulGMSKMCS3UpperThreshold Class 3 508 ulMCS2UpperThreshold Class 3 508 ulMCS3UpperThreshold Class 3 508 ulMCS5UpperThreshold Class 3 509 ulMCS6UpperThreshold Class 3 509 ulMCS7UpperThreshold Class 3 509 ulMCS8UpperThreshold Class 3 509 UMTS access min level Class 3 510 UMTS reselection ARFCN Class 3 510 UMTS reselection offset Class 3 510 UMTS search min level Class 3 511 unequippedCircuit Class 1 511 unit 511 unknownNCellWarning Class 3 512 unmasked users alarms Class 2 512 upAckTime Class 3 (packetAckTime) 513 upgradeStatus 513 uplinkPowerControl Class 3 514 uplinkPwrCtrlDuringUTDOA Class 3 514 uplinkReply Class 3 514 uplinkReplyTimer Class 3 515 uRxLevDLP Class 3 515 uRxLevULP Class 3 515 uRxQualDLP Class 3 516 uRxQualULP Class 3 516 usageState 516 usageState 517 use default list 517 user name 517 user profile 518 username 518 username 518 usfGranularity Class 3 519 V 519 voiceBroadcastService Class 3 519 voiceGroupCallService Class 3 519 vSWR meter Class 2 519
30 W 520 workstation name 520 wPSManagement Class 3 520 wPSQueueStepRotation Class 3 520 X 521 X25 port 0 operational 521 X25 port 1 operational 521 xtp 521 Z 522 zI bss 522 zI bss 523 zone frequency hopping Class 2 524 zone frequency threshold Class 2 524 zone Tx power max reduction Class 2 524
Appendix A Objects and parameters evolution

A.1 A.2 A.3 A.4 New New New New V17 parameters V16 parameters V15 parameters V14 parameters 527 529 531 534
527
Appendix B Parameters per feature

B.1 AMR based on traffic 537 B.2 AMR Optimizations 537 B.3 BSC/TCU 3000 537 B.4 BSC 3000 cell group management/load balancing 538 B.5 BSC 3000 switching increase capacity 538 B.6 BSC overload management 538 B.7 Dualband cell management 538 B.8 EDGE dynamic allocation 539 B.9 EDGE traffic management 539 B.10 EDGE link adaptation 539 B.11 GSM-R V12 540 B.12 GSM-R V15 540 B.13 GPRS (SV407 - V12) 540 B.14 GPRS (TF1134 - NMO I) 542 B.15 GPRS (TF1121 - V12) 542 B.16 GPRS TBF establishment improvement: one phase access 542 B.17 GPRS / EDGE Suspend and Resume 543 B.18 PCUSN - more than 12 Agprs PCMs per BSC 543 B.19 Network Synchronization 543 B.20 BTS Synchronization 543 B.21 Automatic Cell Tiering 543 B.22 Handover for traffic reasons 544 B.23 Handover decision (adjacent cell priority and load) 544
537
31 B.24 B.25 B.26 B.27 B.28 B.29 B.30 B.31 B.32 B.33 B.34 B.35 B.36 B.37 B.38 B.39 B.40 B.41 B.42 B.43 B.44 B.45 B.46 B.47 B.48 B.49 B.50 B.51 B.52 B.53 B.54 B.55 B.56 B.57 B.58 B.59 B.60 B.61 B.62 B.63 B.64 B.65 General protection against pingpong handover 544 Intracell handover enhancements 544 AR 264 544 Mixed hybrid and cavity combiner BTSs 544 Call drop analysis 544 Extended CCCH 545 CPU/BIFP load sharing 545 Distribution on Radio measurements 545 Extended UL TBF 545 Broadcast of PSI 13 545 L1M evolutions for advanced features support 545 Fast power control at TCH assignment 546 Data Backhaul Evolution 546 Disabling TBF Keep Alive 546 PCM error correction 546 Unequipped circuit and circuit group block 546 WPS public access bandwidth protection 546 WPS queuing management 546 BSC/TCU e3 GET DATA enhancement 546 Network Assisted Cell Change for release 4 MS 547 BSS Packet Flow Context 547 BSC 3000 support of BTS background downloading 547 Optimized Agprs cell allocation 548 EDGE Dynamic Agprs 548 Switch Interference Matrix 548 Channel release policy on BTS after Abis failure 548 PM1270 - TDMA based counters 548 Tx power offset for signalling channels 548 Tx power overboost for signaling channels 548 U-TDOA support on the BSS 548 Enhanced Measurement Report (EMR) support 549 GSM to UMTS handover 549 Novel Adaptive Receiver 550 Signaling Link GET Dynamic Data enhancements 550 Smart Power Management 550 Software Preparation for BSC 3000 Optical Carriers Introduction AMR-HR on pre-empted PDTCH 550 Dynamic Abis interface readiness in V17 550 BSS paging coordination 551 Permanent AAL-1 self-testing 551 AMR feature lock at OMC-R 551 EDGE feature lock at OMC-R 551
550
Appendix C PCUSN components

553
32
33
New in this release

The following section detail what is new in Nortel GSM BSS Parameter Reference for the V17.0 release.
Features
See the following sections for information about feature changes:
GSM to UMTS handover (2473) Enhanced measurement report (EMS) support (21531) EDGE - Dynamic Abis per site (25203) On-line TMU load reconfiguration from OMC-BSC3000 (26530) Downlink voice quality monitoring (27017) PCUSN-54 : new PCUSN configuration (T1) (27222) Novel Adaptive Receiver (27888) Permanent AAL-1 self-testing to improve hardware failure detection BSC 3000 (28319) PCUSN-54 : new PCUSN configuration (E1) (28727) Support of A5/3 ciphering key (27392) Signaling Link GET Dynamic Data Enhancement (29722) AMR-HR on pre-empted PDTCH (30169) Advanced Call Drop Analysis (32277) Joint Diversity (32280) CEM2 combined CEM and SRT boards (32291) BSC 3000 optical carriers (32302) BTS 6000 Differenciation in OMC-R (32361) S4000 & S2000 & S2000E removal (32730) Software preparaton for BSC 3000 optical carrier introduction (32736) Shared disks scan for bad blocks prevention (33285)
34
New in this release
TCU 3000 optical carriers (33303) BSS paging coordination (34160) BTS 18000/6000 Smart Power Management (34208) AMR feature lock at OMC-R (34433) EDGE feature lock at OMC-R (34434) RM family renaming management at OMC (34439) BSC and TCU 2G End Of Life (34649)
GSM to UMTS handover (2473)

This feature allows 3G-capable handsets connected on a 2G layer to move to a 3G layer when necessary. Added the following parameters:
mobileCountryCodeUTRAN mobileNetworkCodeUTRAN locationAreaCodeUTRAN rNCId cId fDDARFCN scramblingCode diversityUTRAN QsearchC gsmToUMTSServiceHo hoRejectionTimeOverloadUTRAN earlyClassmarkSendingUTRAN fDDMultiratReporting t3121 compressedModeUTRAN hoMarginAMRUTRAN hoMarginRxLevUTRAN hoMarginRxQualUTRAN hoMarginDistUTRAN rxLevDLPbgtUTRAN
Features
35
hoMarginTrafficOffsetUTRAN hoPingpongCombinationUTRAN hoPingpongTimeRejectionUTRAN offsetPriorityUTRAN rxLevMinCellUTRAN
Also added a semantic check, [C/M], to parameter description of InteferenceMatrixRunningOnBts Also added semantic checks to parameter description of bCCHFrequency parameter of adjacentCellHandOver object
Enhanced measurement report (EMS) support (21531)

This feature introduces support for the GSM Measurement information message and the Enhanced Measurement Report message into the BSS product. Impacts:
servingBandReporting Class 3 (page 441) ServingBandReportingOffset servingBandReportingOffset Class 3 (page 441)
EDGE - Dynamic Abis per site (25203)

This feature extends the current dynamic Abis solution per TDMA, to a pool of EDGE TDMAs on one site, in downlink.
Added the parameter dynamicAbis and modified its semantic checks Updated parameter/objects table in Appendix A Updated parameters per feature information in Appendix B
36
New in this release
On-line TMU load reconfiguration from OMC-BSC3000 (26530)

This feature provides the capability to request a load-balancing reconfiguration from the OMC-R.
Added additional parameter details about estimatedSiteLoad and cpueOccurence
Downlink voice quality monitoring (27017)

This feature provides distributions at the TDMA level of measurements of radio interface. It also provides these measurements for the transceiver (TRX) of given cells for a specified time period.
Added an explanation of the purpose of a semantic checks for parameters ferThreshold1, ferThreshold2, ferThreshold3, ferThreshold4, distributionActivation, distributionDuration, and distributionTime added a semantic check for parameter nbOfFramesForFER
PCUSN-54 : new PCUSN configuration (T1) (27222)

This feature introduces a new PCUSN configuration offering 54 Agprs T1 PCM ports.
Modified the range of values for parameters bscPcuPcmRefList, gprsPcuCrossConnectList, and bscRefList
Support of A5/3 ciphering key (27392)

This feature improves the security of information transmitted over the GSM air interface by implementing the A5/3 encryption algorithm.
Added two values to parameter encryptionAlgorSupported
Novel Adaptive Receiver (27888)

This feature implements an adaptive receiver structure to improve the reception performance of GSM and EDGE radio communication. Added the parameter adaptiveReceiver
Permanent AAL-1 self-testing to improve hardware failure detection BSC 3000 (28319)
The aim of this feature is to supervise the AAL1 paths carrying LAPD channels between Control Node and Interface Node.
Added standbyStatus parameter for TMU Updated parameter/objects table in Appendix A Updated parameters per feature information in Appendix B
Features
37
PCUSN-54 : new PCUSN configuration (E1) (28727)

This feature introduces a new PCUSN configuration offering 54 Agprs E1 PCM ports.
Modified the range values for parameters bscPcuPcmRefList, gprsPcuCrossConnectList, and bscRefList
Signaling Link GET Dynamic Data Enhancement (29722)

This feature allows a network technician to use the OMC-R Graphic User Interface (GUI) to retrieve detailed information about the SS7 links. Added parameters slkATerResource, slkAssociatedTmuPortPosition, signallingLinkResourcesStates. Added the fields signallingLink, slkAssociatedTmuPortPosition, slkATerResource, slkAResource, signallingLinkResState
AMR-HR on pre-empted PDTCH (30169)

This feature allows a BSC to pre-empt a PDTCH channel for half-rate voice channels.
Added the parameter gprsPreemptionForHR Updated parameter/objects table in Appendix A Updated parameters per feature information in Appendix B
Advanced Call Drop Analysis (32277)

This feature allows activation of the functionality to retrieve call drop data at the OMC-R, per cell.
Added text to description of parameter callDropActivation Modified the text that describes the value range of parameter callDropActivation Modified the text that describes the semantic checks for the parameter callDropActivation
Joint Diversity (32280)

This feature improves uplink signal processing, especially 8-PSK channels. Added the value enhancedDiversity to the text about the parameter diversity
38
New in this release
CEM2 combined CEM and SRT boards (32291)

This feature introduces a new common equipment module for the BSC 3000, the CEM2, which replaces both the existing CEM and the 8K-SRT.
The parameter bscArchitecture is updated to include BSC30000Optical
BSC 3000 optical carriers (32302)

This feature introduces a new common equipment module for the BSC 3000, the CEM2, which replaces both the existing CEM and the 8K-SRT. Impacts appear under (32736)
BTS 6000 Differenciation in OMC-R (32361)

This feature allows the display at the OMC-R to distinguish between the BTS 18000 and BTS 6000 models. Modified text about the checks for the parameters hardware configuration, btsSMSynchroMode, sigPowerOverboost, and numberOfJokerDS0
S4000, S2000, and S2000E removal (32730)

This feature indicates the removal of the S2000, S2000E, and S4000 BTSs in V17.
Removed all references to these BTSs throughout the document but especially in the following parameters:
bts equipment name bts Site Manager model external alarm configuration Class 2 Smoke detector Class 2 Software preparation for BSC 3000 optical carrier introduction (32736)
This feature extends the OAM capabilities of the BSS software to manage the new hardware and logical configurations that will be introduced to support fiber-optic connectivity (OC-3 or STM-1) in the BSC 3000.
Added new parameter synchronizingHsaRc Updated parameter/objects table in Appendix A Updated parameters per feature information in Appendix B
Shared disks scan for bad blocks prevention (33285)

A periodical check of the MMS disk has to be performed to identify bad blocks and generate an alarm if needed through a disk scan.
Features
39
Added checks information to parameter mmsUsage.
TCU 3000 optical carriers (33303)

This feature allows a TCU 3000 to use optical carriers for the A and Ater interfaces. See impacts of this feature in the following locations:
updated the value of the transcoderArchitecture (page 498) parameter added the administrativeState (page 75) parameter for the hsaRcTcu object updated the administrativeState (page 74) parameter of the iom object added the availabilityStatus (page 99) parameter for the hsaRcTcu object added the hsaPcmList Class 3 (page 260) parameter for the hsaRcTcu object added the positionInShelf (page 400) parameter for the hsaRcTcu object added the shelfNumber (page 442) parameter for the hsaRcTcu object added the standbyStatus (page 462) parameter for the hsaRcTcu object updated Appendix A Objects and parameters evolution (page 527) updated Appendix B Parameters per feature (page 537)
BSS paging coordination (34160)

The BSS paging coordination is an additional mechanism for handling CS (Circuit Switch) paging. It provides a CS paging coordination without involving the packet core network and the Gs interface.
Added bssPagingCoordination parameter Updated parameter/objects table in Appendix A Updated parameters per feature information in Appendix B
40
New in this release
BTS 18000/6000 Smart Power Management (34208)

This feature reduces BTS power consumption by automatically switching the PA off after a configurable period of time elapses during which there is no circuit communication on the TRX.
Added smartPowerManagementConfig parameter Added smartPowerSwitchOffTimer parameter Updated parameter/objects table in Appendix A Updated parameters per feature information in Appendix B
AMR feature lock at OMC-R (34433)

This feature controls the activation of the AMR feature from the license mechanism. Nortel delivers a license to a customer against a proof of purchasing (purchase order or contract). Added check regarding license validation to speechMode parameter on signallingPoint object. Added output parameters related to Display RM Capacity and Display 4K Erlangs Information commands:
Added parameter Total licenses for this OMC-R. Added parameter Total unused licenses. Added parameter Licenses used by this object. Added parameter Licenses needed to put object in service. Added parameter This BSS is using license. Added parameter Number of XTP under this BSS.
EDGE feature lock at OMC-R (34434)

This feature controls the activation of the EDGE feature from the license mechanism. Nortel delivers a license to a customer against a proof of purchasing (purchase order or contract). Added check regarding license validation to egprsServices on bts object. Added output parameters related to Display RM Capacity and Display 4K Erlangs Information commands, see AMR feature lock at OMC-R (34433) (page 40)
Other changes
41
RM family renaming management at OMC (34439)

This feature simplifies management of the different RM variants and generations at the OMC-R by introducing a consistent set of naming conventions that identify each RM by its hardware generation, frequency, and power output. Added values for v17 to hardware configuration parameter.
BSC and TCU 2G End Of Life (34649)

This feature indicates the removal of the BSC 2G and TCU 2G in V17.0. Removed 106 parameters related to BSC 12000HC and TCU 2G. Modified 57 parameter descriptions that used to mention BSC 12000HC or TCU 2G.
Other changes
See the following section for non-feature related changes:
gsmToUmtsReselection (v17.01) semantic check to descriptions of parameters bCCHFrequency, baseColourCode and networkColourCode (v17.01) hoPingpongCombination parameter (v17.01) microCellCaptureTimer and microCellStability (v17.03) upgradeStatus (v17.05) others
gsmToUmtsReselection
Added detail about semantic check to description of parameter gsmToUmtsReselection (v17.01)
Semantic check
Added detail about semantic check to descriptions of parameters bCCHFrequency, baseColourCode and networkColourCode (v17.01)
hoPingpongCombination
Added detail about semantic check to description of hoPingpongCombi nation parameter (v17.01)
microCellCaptureTimer and microCellStability

Updated note regarding activation requirements (v17.03)
42
New in this release
upgradeStatus
Added upgradeStatus parameter description for the following objects: (v17.05)

Others
atmRm btsSiteManager cc cem controlNode hardware transcoder 3G iem interfaceNode omu sw8kRm tmu transceiverEquipment transcoder trm
Removed network protocolUsed parameter. Updated the description of the following parameters:
bscIPFirstAdr bscIPSecondAdr coderPoolConfiguration cpueNumber
43
Introduction
The Nortel GSM BSS Parameter Reference is a guide that describes all GSM BSS network element parameters that the user can access using the OMC-R.
ATTENTION
For a BSC 3000, there are no class 1 parameters; all these parameters are now class 0.
Prerequisites
Users must be familiar with networking principles. They must also be familiar with the following manuals: < 00 > : Nortel GSM BSS Documentation roadmap
Navigation
Chapter 1 Introduction (page 45) contains general information on BSS operating parameters. Chapter 2 Parameters listed in alphabetical order (page 55) describes all the operating parameters listed in alphabetical order, and explains their use. Appendix A Objects and parameters evolution (page 527) lists new configuration parameters and objects by release. Appendix B Parameters per feature (page 537) presents BSS parameters per feature.
44 Introduction
45
Chapter 1 Introduction
1.1 Network configuration objects and their parameters
This dictionary summarizes all the GSM BSS parameters used to define all the objects managed on the OMC-R. An object model is used to describe each managed network element. Each object is defined in terms of its parameters (also called attributes), and its relationships with other objects. A containment tree is used to depict the relationships among these objects (see Figure 1 "Object main tree structure" (page 45) to Figure 4 "Network subtree objects" (page 47)). For more information on objects and parameters, refer to NTP < 07 >, for parameters listed per object, refer to NTP < 128 >.
ATTENTION
For a BSC 3000, there are no more class 1 parameters; all these parameters are now class 0. Figure 1 Object main tree structure
46 Chapter 1 Introduction
Figure 2 omc subtree objects
Figure 3 md subtree objects
47
Figure 4 Network subtree objects
Figure 5 bsc 3000 subtree objects
Figure 6 btsSiteManager subtree objects
49
Users can create, modify, and delete objects using commands and actions displayed in the menus of the OMC-R Browser window (see Figure 7 "Menus in the OMC-R browser window" (page 49)). Parameters are widely used in all commands and actions. For more information on commands, refer to NTPs < 128 > to < 130 >.
Figure 7 Menus in the OMC-R browser window
For CT2000 and datafill purposes, the following remarks must be taken into consideration:
If not indicated, the parameters are considered mandatory in all cases. For example, if a parameter is marked as Not Mandatory at the OMC-R level, the user does not need to employ it in CT2000, there will not be any value in the command files to create the associated object. A parameter is dependant of an OMC feature only when indicated. For any parameter associated with an OMC feature, if the feature is
active at OMC-R then the parameter is mandatory at object creation otherwise it is not. Example: a parameter marked as "cell Tiering" dependant will only be used when the cellTiering feature is active at the OMC-R level.
A parameter is considered product-dependant only when indicated and to be used only when the product is used in the network. For example, a parameter marked "BSC 3000" dependant is mandatory when the object to create/modify belongs to the "BSC 3000" architecture. CT2000 is an offline, multi-release CM OAM tool. The CT2000 V3 phased with BSS V15 can also configure sub-BSS releases V14.2 and V14.3. Throughout this document, the user will be able to distinguish whether a parameter present in CT2000 DRF interface needs to be filled or not, depending upon the actual network configuration.
1.2 Different types of configuration parameters

There are two types of configuration parameters: customer and manufacturer parameters.
Customer parameters:
addressing parameters, which are relative to objects (for example:

bsc number)
design parameters, which are relative to contract characteristics

(for example: configRef, SiteName)
optimization parameters, which are relative to network tuning (for

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

example: cellBarred)
Manufacturer parameters:
system parameters, which can seriously affect system operation,

and which must be under the control of the manufacturer (for example: runPwrControl)
product parameters, which are incompatible with the current system

release (for example: sWVersionbackup) New configuration parameters are summarized in Appendix A Objects and parameters evolution (page 527).
1.3 Description of dictionary entries 51
1.3 Description of dictionary entries

Each parameter is described separately and arranged in alphabetical order. Dictionary entries fall into two parts:
the header line the main body, composed of several fields
1.3.1 Header line

The header line contains some or all of the following information (see following figure):

Figure 8 Header line
the name of the OMC-R parameter the class of the parameter (if any) the BSS version from which it applies
1.3.2 Main body of entries

The main body contains up to nine fields:
Description: parameter definition Value range: displayed in square brackets and the unit if any Example: [2 to 300] seconds Object: object name(s) in which the parameter is defined Default value: value which allows to deactivate the function Type: parameter type. The five accepted values are the following:
type meaning is handled by the Configuration Management application X X X X X X (7) X (6) is handled by any other applications (4) X (5)
DD DI DP DS Id
Dynamic data (1) Internal data (2) Permanent data (3) Static data Identifier
(1) : Dynamic parameters (DD) are not stored in databases. They are managed by the BSC applications, and they can be consulted on operator request. (2) : Internal parameters (DI) are stored in the OMC-R operation database (BDE) and are not sent to Network Elements. They supply additional information on how an object is configured at a given time. They can be consulted on operator request and some of them can also be modified. (3) : Permanent parameters (DP) are stored in the application database (BDA) and in the operation database (BDE). Most of them are mandatory and they are defined with the object that uses them. They are managed by the operator. (4) : Fault Management, Performance Management, Command Functions, 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 be used. Checks: Semantic checks performed by the OMC-R are indicated with the Create [C], Set [M], Delete [D], or specific action [A] commands.
1.3 Description of dictionary entries 53
Feature: Field introduced from V12. It indicates the reference of the Feature that impacts the parameter description. Restrictions: Applicable restrictions are indicated with the Create [C], Set [M], Delete [D], or specific action [A] commands. Remark: optional field containing comments.
55

For a BSC 3000, there are no more class 1 parameters; all these parameters are now class 0.
A
abisSpy Class 3
Description : Whether measurement reports from the BTS and the mobiles are forwarded to the BSC in order to spy on the Abis Interface. [in progress / not in progress] bts not in progress DP
Value range : Object : Default value : Type:
absoluteRFChannelNo Class 2
Description : Radio frequency used in the network frequency band by a radio time slot that does not obey frequency hopping laws. Setting this attribute forbids the radio time slot to obey frequency hopping laws. The frequency of the radio time slot that carries a cell BCCH in a TDMA frame (channelType = "mainBCCH", "mainBCCHCombined", or "bcchSdcch4CBCH") is not managed by users. When the parent bts object is unlocked, the system automatically assigns the cell bCCHFrequency to the concerned channel object and updates it whenever it is changed. Value range : [1 to 124] (GSM 900 network), [955 to 1023] / [0 to 124] (GSM-R), [975 to 1023] / [0 to 124] (E-GSM),
56 Chapter 2 Parameters listed in alphabetical order
Object : Condition : Type : Checks :
[512 to 885] (GSM 1800 network), [512 to 810] (GSM 1900 network), [128 to 251] (GSM 850 network), [955 / 1023] / [0 / 55] (GSM-R). channel To define if the TDMA does not hop DP
[C/M] :
The attribute is undefined when the radio time slot is authorized to hop or its channelType is "mainBCCH", "mainBCCHC ombined", or "bcchSdcch4CBCH". The attribute is defined when the radio time slot is not authorized to hop and its channelType is "tCHFull", "sDCCH", "sdcch8CBCH", or "cCH". When defined, the frequency is one of those allotted to the parent bts object (cellAllocation list). Concentric cell: When defined, the frequency is not used by the channel objects related to the transceiver objects allotted to the other cell zone. If the frequency hopping is not used, the absoluteRFChannelNo attribute indicates a radio frequency number which is located between [0 to 124] or [955 to 1023] when the standardIndicator attribute is equal to Rgsm.
[C/M] :
[C/M] :
[M] :
[C/M]:
access time end

Description : Value range : Object : Type : Checks : Time of the day after which the user is not allowed to log in. It is after access time start. [<time> (18:00)] user profile DP
[C/M] :
access time end is after access time start.
access time start

Description : Value range : Time of the day after which the user is allowed to log in. [<time> (09:00)]
57
Type : Checks :
DP
[C/M] :
access time start is before access time end.
accessClassCongestion Class 3
Description : Value range : Object : Type : Release : List of access classes that are not authorized in a cell during TCH congestion phase (class 10 not included). [0 to 9] User classes [11 to 15] Operator classes bts DP V9
accessibilityState
Description : Value range : MSC accessibility state [reachable / congested / unReachable]

Object : Type : DD
reachable................. congested.................
The remote signaling point is within reach. 80% of the BSC pool of buffers handling outgoing MSC messages is full. The remote signaling point is out of reach.
unReachable......
signallingLinkSet
acknowledged by
Description : To select alarms acknowledged by a given user. Enter the users name as defined in the users profile. Do not fill in if this criterion is not to be selected. Value range : Object : Type : [case sensitive] Alarm logs - Filter DP
acknowledgment time
Description : Value range : To select messages acknowledged at that time. [<date>,<time>] Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in if this criterion is not to be selected. Object : Type : Alarm logs - Filter DP
activationObject
Description : Value range : Object : Type : Checks : Identifier or name of the traced bsc object on the OMC-R. [bscId range] callPathTrace DP
[C]: [C]:
The bsc object is created. The callPathTrace object is not created for the bsc object. The Call path tracing function is unique in a given BSS. This attribute cannot be modified.
Restrictions :
[M]:
activationObject
Description : Value range : Object : Type : Checks : Identifier or name of the traced bsc object on the OMC-R. [bscId range] traceControl DP
[C]: [C]:
The bsc object is created. The traceControl object is not created for the bsc object. The Call tracing function is unique in a given BSS. This attribute cannot be modified.
Restrictions :
[M]:
59
adaptiveReceiver Class
Description: Allows a return to the initial receiver processing for either peculiar cell configurations or both of them. In a first step, the parameter is a simple switch, but more than one bit should be allocated to handle later extensions (automatic recognition of configurations requiring the initial receiver processing). 0/1 (0 : disabled, 1: enabled) transceiver disabled DP V17 This parameter is only available for BSC 3000. It is visible only in GPRS.
Value range: Object: Default value: Type: Release: Note:
additional supervised PCM 0 Class 2

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

Value range :
BTS 18000 S12000 S8000 BTS with BCF S8000 BTS with CBCF S8002 BTS with CBCF S2000 H/L BTS e-cell
[yes (the odd PCM link is supervised by the BTS) / no (the odd PCM link is not supervised by the BTS)] If PCM 0 belongs to the bscSitePCMList parameter the values YES or NO are equivalent (recommendation: NO)
Object : Feature :
btsSiteManager GSM-R V12
Type : Release :
DP V12


Value range :
Object : Feature : Type : Release :
btsSiteManager GSM-R V12 DP V12

BTS 18000 S12000 S8000 BTS with BCF
61

Value range :
S8000 BTS with CBCF S8002 BTS with CBCF S2000 H/L BTS e-cell


Value range :


Value range :

BTS 18000 S12000 S8000 BTS with BCF S8000 BTS with CBCF S8002 BTS with CBCF
63

Value range :
S2000 H/L BTS e-cell
additional unmasked users alarms Class 2

Description : Configuration of the new user (unprotected) external alarm loops controlled by the BTS (added to the already existing unprotected external alarms, see parameter "unmasked users alarms"). These additional alarms are detected by the RECAL board of the main cabinet. When an alarm is unmasked, it means the relevant equipment is monitored by the BTS. There are 24 additional user (unprotected) alarms on the S8002 BTS, 14 alarms on the S8000 Outdoor BTS, and 20 alarms on the S8000 Indoor BTS. A user alarm is used when an external item of equipment is inserted in the BTS (a microwave terminal for instance) and does not require a new DLU. Value range : [All alarms masked Alarm 1 unmasked Alarms 1 to 2 unmasked Alarms 1 to 3 unmasked Alarms 1 to 4 unmasked Alarms 1 to 5 unmasked Alarms 1 to 6 unmasked Alarms 1 to 7 unmasked Alarms 1 to 8 unmasked Alarms 1 to 9 unmasked Alarms 1 to 10 unmasked Alarms 1 to 11 unmasked Alarms 1 to 12 unmasked Alarms 1 to 13 unmasked Alarms 1 to 14 unmasked Alarms 1 to 15 unmasked
Alarms 1 to 16 Alarms 1 to 17 Alarms 1 to 18 Alarms 1 to 19 Alarms 1 to 20 Alarms 1 to 21 Alarms 1 to 22 Alarms 1 to 23 Alarms 1 to 24 Object : Feature : Type : Release : GSM-R V12 DP V12
unmasked unmasked unmasked unmasked unmasked unmasked unmasked unmasked unmasked]
btsSiteManager
addresses
Description : Definition of the OMC-R user(s) to whom the message is addressed. Select the all option to send the message to all OMC-R users. Select the users option to send the message to selected OMC-R users. Enter their names as defined in their profiles [case sensitive], separated by the "&" character. Object : Type : user message - Answer / New message DP
adjacent cell umbrella ref Class 3

Description : Identifier of the adjacentCelHandOver object that describes the neighbor cell towards which a directed retry will be triggered in BSC mode. [0 to 31] bts DP
Value range : Object : Type : Checks :
[C/M]: [C/M]:
The preferential umbrella cell must refer to an existing adjacentCellHandOver object instance. When the function "directed retry" is made by interrogation of the BTS, the preferential umbrella cell must not be indicated.
Release :
V9
65
adjacentCellHandOver
Description : Identifier of an adjacentCellHandOver object that defines a neighbor cell of a serving cell for handover management purposes. A bts object may reference up to thirty-two objects of this type. [0 to 31] adjacentCellHandOver Id
[C]:
The associated bts object is created and the adjacentCellHandOver object is not created for that object. The number of adjacentCellHandOver objects created for a bts object is limited to maxAdjCHOARMPerBts (static configuration data). The (baseColourCode, bCCHFrequency, networkColourCode) combination is unique in the set including a serving cell and its neighbor cells. If the related BSC application database is built, the parent bsc object is unlocked. The parent bsc object is unlocked. The adjacentCellHandOver object is created. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command. No mdScanner object refers to the adjacentCellHandOver object (no observation is running on that object). At least one adjacentCellHandOver object should be created for the bts object.
[C]:
[C/M]:

Release : V8
[C/D]: [M]: [M/D]: [D]:
[D]:
[D]:
adjacentCellHandOverId
Description : Identifier of an adjacentCellHandOver object that defines re-selection management parameters for a serving cell. A bts object may reference up to sixty-four objects of this type. [0 to 63] adjacentCellHandOver
Value range : Object :
Type : Release :
DP V14
adjacentCellReselection
Description : Identifier of an adjacentCellReselection object that defines re-selection management parameters for a serving cell. A bts object may reference up to thirty-two objects of this type. [0 to 31] adjacentCellReselection Id
[C]:
The bts object is created and the adjacentCellReselection object is not created for that object. The number of adjacentCellReselection objects created for a bts object is limited to maxAdjCHOARMPerBts (static configuration data). The parent bsc object is unlocked. If the application database of the related BSC is built, the parent bsc object is unlocked. The adjacentCellReselection object is created. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.
[C]:

Release : V8
[M]: [C/D]: [M/D]: [D]:
adjacentCellReselectionId
Description : Identifier of an adjacentCellReselection object that defines re-selection management parameters for a serving cell. A bts object may reference up to sixty-four objects of this type. [0 to 63] adjacentCellReselection DP V14
Value range : Object : Type : Release :
67
administrativeState
Description : Activation state of an alarm criteria. An alarm criteria is created in unlocked state. The OMC-R Fault Management function ignores the inactive criteria when processing notifications. Value range : Object : Type : [locked (inactive) / unlocked (active)] alarm criteria DP
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] atmRm BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : ISO state [locked / unlocked] A bsc object is created in locked state. Object : Type : Checks : bsc DP
[M]:
If mobileCountryCode and mobileNetworkC ode are defined for the bsc object, they match those of all dependent bts objects.
[M]:
The following check is only performed when the bsc object is unlocked:
The dependent software object is created and its sWVersionRunning attribute defines a software version downloaded to the BSC disk.
administrativeState
Description : Value range : ISO state [locked / unlocked] A bscMdInterface object is created in unlocked state. When the object is locked, the BSC involved in the BSS/OMC-R link described by this object cannot communicate with the OMC-R. Object : Type : Checks : bscMdInterface DP
[M]:
The concerned bsc object is unlocked.
administrativeState
Description : ISO state A bts object is created in locked state. When the object is unlocked, the described cell will be working if the carrier TDMA frame (or BCCH frame) is successfully configured in the BTS and at least <minNbOfTDMA> TDMA frames (including the carrier frame) are operating. Value range : Object : Type : Checks : [locked / unlocked / shuttingDown (soft release)] bts DP
[M]: [M]:
The parent bsc object is unlocked. It is not possible to change from "shuttingD own" to "unlocked" or from "locked" to "shuttingDown". It is not possible to change to "shuttingDown" if the application database of the related BSC is not built.
[M]:
The following checks are only performed when the bts object is unlocked:
69
The associated handOverControl and powerControl objects are created for the bts object. The mobileCountryCode and mobileNetworkCode attributes match those of the parent bsc object when they are defined for that object. The frequencies in the cellAllocation list comply with the standardIndicator attribute value. The minNbOfTDMA attribute value is less than or equal to the number of transceiver objects created for the bts object. Cavity cell: The number of dependent transceiver objects equals the number of frequencies in the cellAllocation list. Eight channel objects are created for each dependent transceiver object if the cell works in normal mode, four channel objects are created for each dependent transceiver object if the cell works in extended mode.
The following apply:
Only one of them has a channelType equal to "mainBCCH", "mainBCCHCombined", or "bcchSdcch4CBCH". If the smsCB attribute of the bts object is "used", one of them has a channelType equal to "sdcc8CBCH" or "bcchSdcch4CBCH". Concentric cell: Two transceiverZone objects are created for the bts object. Each dependent transceiver object refers to a transceiverZone object (transceiver zone Ref is defined). All channel objects describing the cell BCCH or common channels (channelType = "cCH") depend on transceiver objects allotted to the outer zone. If frequency hopping is allowed in a zone (zone frequency hopping), it is allowed in the cell (btsIshopping). The frequencies used by the transceiver objects in a zone are separate from the frequencies used by the transceiver objects in the other zone.
Releasing a bts object by shutting down sustains the calls supported by the described cell. The system actions are as follows:
Radio resources remain allocated until the calls end. Once a TDMA frame is released, a CLEAR CONFIG REQUEST message is sent to the partnered TRX/DRX. When all calls are terminated, the cell is released (administrativeState = "locked" and operationalState = "disabled") and the concerned TRX/DRXs and TDMA frames are unreachable (availabilityStatus = "{dependency}". It is recommended to bar direct access to the cell before initiating a soft release (cellBarred = "barred"), to prevent off-call mobiles from listening to the cell during the soft release phase, so they can immediately re-select another cell for receiving or sending calls. It is recommended also to forbid incoming handovers in the cell (incomingHandOver = "disabled"), to remove the cell from the list of eligible cells and, thus, avoid its selection if the BTS receives such a request. In order to speed up the soft release process, the Force HandOvers command can be used first to redirect the traffic currently handled by the serving cell towards its neighbor cells. If a hard lock request is sent during the soft release phase, all the calls supported by the cell are immediately released by the BSC. If the administrativeState of the object is unlocked and the availabilityStatus is unknown, the object status is undetermined. You must request the status of the bsc object on the OMC-R, to update the network view.
Notes :
administrativeState
Description : Value range : ISO state [locked / unlocked] A btsSiteManager object is created in locked state. Object : Type : btsSiteManager DP
71
Checks :
[M]:
The parent bsc object is unlocked.
The following checks are only performed when the btsSiteManager object is unlocked:
The scheduled time slot (pcmTimeSlotNumber) is masked in the btsSiteManager object radioSiteMask. The radioSiteMask of all btsSiteManager objects sharing a same PCM link in the BSS are dissociated and their scheduled time slots are different and masked in their radioSiteMask. The bscSitePcmList list includes at least two items if the btsSiteManager object redundantPcmPresence attribute is "true". All pcmCircuit objects referenced in the list (pcmCircuitBsc components) are created for the parent bsc object and assigned to the Abis interface. One of them identifies a PCM link with a pcmCircuitBt sSiteManager reference in the range [0 to 3] for clock synchronization. The greatest bts object identifier must be lower than the maxNbOfCells value of the parent btsSiteManager object. The configRef attribute defines a DLU file downloaded to the BSC disk. The dependent software object is created and its sWVersionRunning attribute defines a software version downloaded to the BSC disk. If the administrativeState of the object is unlocked and the availabilityStatus is unknown, the object status is undetermined. You must request the status of the bsc object on the OMC-R, to update the network view.
administrativeState
Description : Value range : ISO state. Locking the object blocks the collection of data and the generation of the associated messages. [locked / unlocked] A callPathTrace object is created in locked state. Unlock the object to start collecting data in the related BSC.
In that case, data collecting is stopped in the related BSC. However, current messages are stored by the BSC and notified to the OMC-R agent. Object : Type : Notes : callPathTrace DP
If trace data collecting is stopped by locking the object, the BSC continues to send the current trace messages to the OMC-R agent, but no notifications are issued. If trace data collecting is stopped by locking the object or on reaching the end-of-session criterion, it is automatically restarted whenever the callPathTrace object is unlocked. For instance, if the end-of-session criterion defines a period of time that elapsed, data collecting will restart for the entire period.
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] cc BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] cem BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : Object : Feature : ISO state [locked / unlocked] controlNode BSC/TCU e3: AR 1209
73
Type : Release :
DP V13
administrativeState
Description : ISO state. Locking the object blocks the transmission of the associated messages to the OMC-R manager. The administrativeState of an efd object is set by the user at object creation time and can be changed with the Modify command. Value range : Object : Type : [locked / unlocked] efd DP
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] g3BscEqp BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] hardware transcoder 3G BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] iem BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] iom BSC 3000 optical / TCU 3000 optical DP V17
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] interfaceNode BSC/TCU e3: AR 1209 DP V13
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 : Object : Type : Checks : [locked (inactive) / unlocked (active)] job DP
[M]:
The job is not running.
administrativeState
Description : Value range : ISO state. It is set by the OMC-R agent. [locked (= restored log) / unlocked (= current log)] An unlocked log object describes a current log on the OMC-R agent disks. A locked log object describes a log restored on the disks. Object : Type : Note : log - Display DP The attributes of the log objects are not managed by users.
75
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] lsaRc BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] hsaRc BSC 3000 optical DP V17
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] hsaRcTcu TCU 3000 optical DP V17
administrativeState
Description : ISO state. Locking the object blocks the generation of processed alarms when out-of-range conditions are met. The administrativeState of an mdWarning object is set by the user at object creation time and can be changed with the Modify command. A change of state is effective when the OMC-R is restarted. Whatever the state of the object, the related notifications are always forwarded to the OMC-R manager. Value range : Object : Type : [locked / unlocked] mdWarning DP
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] mms BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] omu BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : ISO state [locked / unlocked] A pcmCircuit object is created in locked state. Object : Type : Checks : pcmCircuit DP
[M]:
administrativeState
Description : Value range : ISO state [locked / unlocked] A pcu object is created in locked state. Object : Feature : Type : Checks : Release : pcu GPRS (SV407 - V12) DP
[M]:
V12
77
administrativeState
Description : Value range : ISO state [locked / unlocked] A signallingLink object is created in locked state. Object : Type : Checks : signallingLink DP
[M]:
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] sw8kRm BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] tmu BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : ISO state. Locking the object blocks the collection of data and the generation of the associated messages. [locked / unlocked] A traceControl object is created in locked state. Unlock the object to start collecting trace data in the related BSC. Object : traceControl
Type : Notes :
DP
If trace data collecting is stopped by locking the object, the BSC continues to send the current trace messages to the OMC-R agent, but no notifications are issued. If traced calls are not terminated when the object is locked, all trace information related to those calls will be lost, unless partial record generation was requested. In that case, only data that are not yet recorded will be lost. Trace data collecting is automatically restarted in the BSC whenever the traceControl object is unlocked.
administrativeState
Description : Value range :
ISO state [locked / unlocked / shuttingDown (soft release)] A transceiverEquipment object is created in locked state.
Object : Type : Checks :
transceiverEquipment DP
[M]: [M]:
The parent bsc object is unlocked. It is not possible to change from "shuttin gDown" to "unlocked" or from "locked" to "shuttingDown". It is not possible to change to "shuttingDow n" if the application database of the related BSC is not built.
[M]:
The following checks are only performed when the transceiverEquipment object is unlocked:
The lapdLinkOMLRef and lapdLink RSLRef attributes of the transceiverEquipment object refer to lapdLink objects using the same lapdTerminalNumber in the parent BSC. The related software object is created and its sWVersionRunning attribute defines a software version downloaded to the BSC disk.
Releasing a transceiverEquipment object by shutting down sustains the calls supported by the described TRX/DRX and the partnered TDMA frame. The system actions which may be carried out are the following:
79
To carry out a soft release. This action does not automatically cause a handover. By carrying out this action, the operator must wait for the end of the coms before the TRX/DRX changes to "blocked". To carry out a forced handover. A forced handover on the bts object will cause the DRX/TRX to change to "blocked" more quickly. If the TDMA frame affected by this operation has priority over other frames in the BSS, the BSC re-configures that frame on a different TRX/DRX and immediately transfers the current calls handled by the TRX/DRX being released. When all calls are transferred or terminated, the TRX/DRX is released (administrativeState = "locked" and operationalState = "disabled"), and the partnered TDMA frame is unreachable if it has not been reconfigured (availabilityStatus = "{dependency}".
Note :
If a hard lock request is sent during the soft release phase, all the calls handled by the TRX/DRX are immediately released by the BSC. If the administrativeState of the object is unlocked and the availabilityStatus is unknown, the object status is undetermined. You must request the status of the bsc object on the OMC-R, to update the network view.
administrativeState
Description : Value range : ISO state [locked / unlocked] A transcoder object is created in locked state. Object : Type : Checks : transcoder DP
[M]:
The following checks are only performed when the transcoder object is unlocked:
All transcoder objects created for the same parent bsc object refer to lapdLink objects that use the same lapdTerminalNumber in the BSC.
administrativeState
Description : Value range : Object : Feature : Type : Release : ISO state [locked / unlocked] trm BSC/TCU e3: AR 1209 DP V13
administrativeState
Description : Value range : ISO state [locked / unlocked / shuttingDown (soft release)] An xtp object is created in locked state. Object : Type : Checks : xtp DP
[M]: [M]:
The parent bsc object is unlocked. It is not possible to change from "shuttin gDown" to "unlocked" or from "locked" to "shuttingDown". It is not possible to change to "shuttingDown" if the application database of the related BSC is not built.
[M]:
The BSC will refuse to unlock a terrestrial traffic circuit that could break the OMC channel connection down. Releasing an xtp object by shutting down sustains the call supported by the described terrestrial traffic circuit. The system actions are as follows:

Notes :
Any further attempt of the MSC to allocate the terrestrial circuit is refused. When the call is completed, the terrestrial circuit is released (administrativeState = "locked" and operationalState = "disabled"). All terrestrial circuits supported by a given PCM link can be softly released at the same time. If the PCM link supports a signaling link, it remains operating. If a hard lock request is sent during the soft release phase, the call supported by the terrestrial circuit is immediately released by the BSC.
81
agprsFilterCoefficient Class 3
Description : The load of each cell considered in dynamic AGPRS algorithm is filtered with a forgetting factor given by agprsFilterCoefficient. [0 to 100] % bts 0 (deactivates the feature in the cell at the PCU level). DP V14
Value range : Object : Default value : Type : Release :
agprsHysteresis Class 3
Description : Value range : Object : Default value : Note : Type : Release : Not used. [0 to 100] bts 0 For a BSC version later than V15, agprsHysteresis is not available at the OMC-R. DP V14
agprsThreshold Class 3
Description : Value range : Object : Default value : Note : Type : Release : Not used. [not used] bts 0 For a BSC version later than V15, agprsThreshold is not available at the OMC-R. DP V14
agprsTsSharingProtection Class 2
Description : Value range : Object : Default value : Note : Protection Timer in case of BSC overload. [0 to 255] seconds pcu 0. Values from 0 to 9 are assimilated by PCU like 10.
Note :
For a BSC version later than V15, agprsTsSharingProtect ion is not available at the OMC-R, and PCU automatically set it to 10. DP V14
Type : Release :
agpsTimer Class 3
Description : Value range : Object : Default value : Type : Release : Note : Duration of an A-GPS location. [0 to 255] seconds bsc 0 second DP V15 This parameter is optional.
alarm criteria
Description : Value range : Active alarm configuration. [day configuration / night configuration / specific configuration / reference configuration] The active configuration is the alarm criteria configuration currently used by the OMC-R Fault Management function for fault processing. The names given to the alarm operating configurations (day / night / specific) only serve to identify them. Any configuration may be activated at any time by users, but only one can be active at a time. Object : Type : Notes : omc DP
When the OMC-R is started up or the active server is switched over, the OMC-R activates the configuration the name of which corresponds to the time of the day that start-up or switchover occurs. The following apply:
83
The daytime configuration is activated when the event occurs between 9:00 a.m. and 6:00 p.m. (static configuration data). The nighttime configuration is activated when the event occurs between 6:00 p.m. and 9:00 a.m. (static configuration data).
The active configuration can be forced by users at any other time. If a problem occurs while loading the selected configuration, the OMC-R uses the reference configuration and sends a warning message to the user.
alarm criteria
Description : Value range : Identifier of an alarm criterion on the OMC-R. [0 to 99 999] (manufacturer configuration) Users can lock / unlock alarmcriteria which IDs are lower than 100 000. Users can create / modify / delete criteria, which IDs are greater than or equal to 100 000. Object : Type : Checks : alarm criteria Id
[C]: [C]: [M/D]:
The alarm criteria identifier is in the range [100 001 to 2 147 483 646]. The alarm criteria does not exist in the operator configurations. The alarm criteria exists in the operator configurations.
alarm number
Description : To select alarms with a given number. Do not fill in if this criterion is not to be selected. Value range : Object : Type : [0 to 2147483646] Alarm logs - Filter DP
alarm severity
Description : To select alarms according to the severity. Do not fill in if this criterion is not to be selected. Value range : Object : Type : [critical / major / minor] Alarm logs - Filter DP
alarm state
Description : To select alarms according to the acknowledgement state. Do not fill in if this criterion is not to be selected. Value range : Object : Type : [acknowledged / unacknowledged] Alarm logs - Filter DP
alarmDuration
Description : Value range : Object : Condition : Type : Alarm hold duration when a counter is involved. [0 to 345600] second alarm criteria To define if a counter is associated with the criterion. DP
alarmPriority
Description : Value range : Alarm processing priority. [CLEARED / critical / indeterminate / major / minor / warning] There are six defined priority levels which provide an indication of how it is perceived that the capability of the managed object has been affected. The following definitions are used:
CLEARED: ......
The cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this managed object that have the same type, probable cause, and specific problems.
85
critical: .........
The critical severity level indicates that a service affecting condition has occurred and an immediate corrective action is required. The indeterminate severity level indicates that the severity level of the service affecting condition cannot be determined. The major severity level indicates that a service affecting condition has developed and a deferred corrective action is required. The minor severity level indicates the existence of a non-service affecting fault condition and that a corrective action should be taken in order to prevent a more serious fault. The warning severity level indicates the detection of a potential or impending service affecting fault, before any significant effects have been felt. An action should be taken to further diagnose and correct the problem in order to prevent it from becoming a more serious service affecting fault.
indeterminate: ....
major: ..........
minor: ..........
warning: .........
Object : Type :
mdWarning DP
allocationState
Description : Value range : TDMA frame allocation state [available / not available / not significant]
available .................
The SACCH FILLING messages containing the SYS INFO 5 and 6 have been acknowledged by the BTS.
not available ....
The SACCH FILLING messages containing the SYS INFO 5 and 6 have not been acknowledged by the BTS. The SACCH FILLING messages containing the SYS INFO 5 and 6 have not been sent to the BTS by the BSC.
not significant ....
Object : Type :
transceiver DD
allocPriorityTable Class 3
Description : Table of conversion of the 18 external priorities (14 are GSM external priorities) to 13 internal priorities. (See Default value below.) [0 to 7] (BSS V14 and V12) "0" defines the highest priority, [0 to 12] (BSS V15) "0" defines the highest priority. bts WPS queuing management (22463) BSS V15: 0 8 9 10 11 12 0 0 0 0 0 0 0 0 0 0 0 0 BSS V12 or V14: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 DP
Value range : Object : Feature : Default value : Type :
allocPriorityThreshold Class 3
Description : Number of free TCHs needed for processing a TCH allocation request with an internal priority higher than 1. These channels are reserved to allocation requests with a maximum internal priority (priority 0). The TCH allocation is performed according to this algorithm: Number of free TCH = 0 TCH re quest of priority 0 TCH re quest of priority > 0 - queueing if defined or - reject - queueing if defined or - reject 1 Number of free TCH allocPriorityThreshold TCH allocated Number of free TCH > allocPriorityThreshold TCH allocated
- queueing if defined or - reject
TCH allocated
87
Value range : Object : Default value : Type :
[0 to 2147483646] bts 0 DP
allocPriorityTimers Class 3
Description : Table of timers defining the maximum queuing time of TCH allocation requests (public and WPS requests), according to the internal priority. [List of 8 elements for BSS V12 and V14]: [0-255] seconds [List of 13 elements for BSS V15]: [0-255] seconds bts WPS queuing management (22463) For BSS V15: 0 0 0 0 0 0 0 0 28 28 28 28 28 For BSS V12 and V14: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 DP
allocWaitThreshold Class 3
Description : Table of thresholds defining the maximum number of TCH allocation requests queued (public and WPS), according to their internal priority. [List of 8 elements for BSS V12 and V14]: [0-63] [List of 13 elements for BSS V15]: [0-63] bts WPS queuing management (22463) For BSC V15: 0 0 0 0 0 0 0 0 5 5 5 5 5 For BSS V12 and V14: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 DP
allOtherCasesPriority Class 3
Description : Index in the allocPriorityTable that defines the processing priority of TCH allocation requests with cause "other cases". This priority is used in primo-allocations or when an SDDCH cannot be allocated for overload reasons. Value range : Object : Default value : Type : [0 to 17] bts 17 DP
amrAdaptationSet Class 3
Description : This attribute defines the lines of parameter used for the adaptation mechanism. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the bts object instance in unlocked. Value range : Object : Default value : Type : Release : Note : Note : Int [0 to 3] bts 0 DP V14 This parameter is available for all BSCs 3000 and applicable to versions earlier than V15.1.1. For a V15.1.1 BSC, amrAdaptationSet is replaced by the following parameters: amrDlFrAdaptationSet, amrDlHrAdaptationSet, amrUlFrAdaptationSet, and amrUlHrAdaptationSet. Refer to these entries in this dictionary. amrAdaptationSet is however present at the OMC-R.
amrDirectAllocIntRxLevDL Class 3
Description : Downlink RxLev threshold for direct AMR TCH allocation in the inner zone. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the handOverControl object instance in unlocked. Value range : Object : Default value : Type : Checks : Int [-110 to -47] handOverControl -80 to -79 dB DP
057CO01
- amrDirectAllocIntRxLevDL >= concentAlgoIntRxLev where concentAlgoIntRxLev is intRxLev in the ConcentAlgoData sequence of concentAlgoData attribute.
Release : Note :
V14 This parameter is only available for BSC 3000.
89
amrDirectAllocIntRxLevUL Class 3
Description : Uplink RxLev threshold for direct AMR TCH allocation in the inner zone. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the handOverControl object instance in unlocked. Value range : Object : Default value : Type : Release : Note : Int [110 to 48] handOverControl -80 to -79 dB DP V14 This parameter is only available for BSC 3000.
amrDirectAllocRxLevDL Class 3
Description : Downlink RxLev threshold for direct AMR TCH allocation. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the handOverControl object instance in unlocked. Value range : Object : Default value : Type : Release : Note : Int [-110 to -47] handOverControl -80 to -79 dB DP V14 This parameter is only available for BSC 3000.
amrDirectAllocRxLevUL Class 3
Description : This attribute defines the downlink RxLev threshold for direct AMR TCH allocation. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the handOverControl object instance in unlocked. Value range : Object : Default value : Int [-110 to -47] handOverControl -80 to -79 dB
Type : Release : Note :
DP V14 This parameter is only available for BSC 3000.
amrDlFrAdaptationSet class 3
Description : Object : Value range : Type : Feature : Default value : Release : Note : This attribute defines the lines of parameter used for the downlink AMR full rate adaptation mechanism. bts [0 to 3] DP AMR Optimizations 0 V15 This parameter is optional. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
amrDlHrAdaptationSet class 3
Description : Object : Value range : Type : Feature : Default value : Release : Note : This attribute defines the lines of parameter used for the downlink AMR half rate adaptation mechanism. bts [0 to 3] DP AMR Optimizations 0 V15 This parameter is optional. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
amrFRIntercellCodecMode Class 3
Description : Target codec mode to trigger an intercell quality handover from a RR channel. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the handOverControl object instance in unlocked. Value range : Object : [12.2 / 10.2 / 6.7 / 5.9 / 4.75] handOverControl
91
Default value : Type : Release : Note :
4.75 DP V14 This parameter is only available for BSC 3000.
amrFRIntracellCodecMode Class 3
Description : Target codec mode to trigger an intracell quality handover FR to FR. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the handOverControl object instance in unlocked. Value range : Object : Default value : Type : Release : Note : [12.2 / 10.2 / 6.7 / 5.9 / 4.75] handOverControl 4.75 DP V14 This parameter is only available for BSC 3000.
amrHRIntercellCodecMode Class 3
Description : Target codec mode to trigger an intercell quality handover from an HR channel. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the handOverControl object instance in unlocked. Value range : Object : Default value : Type : Release : Note : [7.4 / 6.7 / 5.9 / 4.75] handOverControl 4.75 DP V14 This parameter is only available for BSC 3000.
amrHRToFRIntraCodecMode Class 3
Description : Target codec mode to trigger an intracell quality handover from AMR HR to FR. This attribute is modified by the Manager.
Value changes are notified to the Manager. This attribute can only be modified if the handOverControl object instance in unlocked. Value range : Object : Default value : Type : Release : Note : [7.4 / 6.7 / 5.9 / 4.75] handOverControl 6.7 DP V14 This parameter is only available for BSC 3000.
amriRxLevDLH Class 3
Description : This attribute is the downlink RxLev threshold in case of AMR FR intracell handover. This attribute can only be modified if the handOverControl object instance in unlocked. Value range : Object : Default value : Type : Release : Note : [-110 to -47] handOverControl -75 to -74 dB DP V14 This parameter is only available for BSC 3000.
amriRxLevULH Class 3
Description : This attribute is the uplink RxLev threshold in case of AMR FR intracell handover. This attribute can only be modified if the handOverControl object instance in unlocked. Value range : Object : Default value : Type : Release : Note : Int [-110 to -47] handOverControl - 75 to - 74 dB DP V14 This parameter is only available for BSC 3000.
93
amrReserved1
Description : Value range : Object : Default value : Type : Release : Note 1: See information contained in the Attention paragraph below. [0 to 2] handOverControl 0 DP V16 This parameter is only available for BSC 3000.
ATTENTION
Parameter range evolution for amrReserved 1 is as follows:
0: RATSCCH procedure enabled (default value) 1: RATSCCH procedure disabled - initial Full Rate ACS is optimistic 2: RATSCCH procedure disabled - initial Full Rate ACS is pessimistic
amrReserved2 Class 3
Description : AMR L1m deactivation for: AMR FR intracell handover and AMR quality inter-cell handover and AMR power control mechanism. This parameter is available at the OMC-R level, managed by all NRPs, except the AMR activation NRP and this parameter is not managed by the CT2000 and the SDO. Value range : [0 to 3] Deactivations for this parameter are: Value 0 (default): AMR L1m algorithms are used. Value 1: AMR FR intracell handover and AMR quality inter cell handover are deactivated, but the AMR power control is activated. Value 2: AMR FR intracell handover and AMR quality inter cell handover are activated, and the AMR power control is deactivated. Value 3: AMR FR intracell handover, AMr quality inter cell handover and the AMR power control are deactivated. Object : Type : Release : Note : handOverControl DP V14 This parameter is only available for BSC 3000.
amrUlFrAdaptationSet class 3
Description : Object : Value range : Type : Feature : Default value : Release : Note : This attribute defines the lines of parameter used for the uplink AMR full rate adaptation mechanism. bts [0 to 3] DP AMR Optimizations 0 V15 This parameter is optional. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
amrUlHrAdaptationSet class 3
Description : Object : Value range : Type : Feature : Default value : Release : Note : This attribute defines the lines of parameter used for the uplink AMR half rate adaptation mechanism. bts [0 to 3] DP AMR Optimizations 0 V15 This parameter is optional. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1
answerPagingPriority Class 3
Description : Index in the allocPriorityTable that defines the processing priority of TCH allocation requests with cause "reply to paging". This priority is used in signaling mode on TCH only. Value range : Object : Default value : Type : [0 to 17] bts 17 DP
95
architecture
Description : Architecture of the OMC-R agent in terms of servers. It is provided by the OMC-R agent. The standard configuration is "one active with one passive" and the basic configuration is "one active without passive". Value range : [dual servers but passive not running dual servers running single server running] md - Display DP
[M]:
This attribute is not managed by users.
assignRequestPriority Class 3
Description : Index in the allocPriorityTable that defines the processing priority of TCH allocation requests with cause "immediate assignment". This priority is used when radio resource allocation queueing is not requested by the MSC or not authorized in the BSS (refer to the bscQueueingOption entry in the Dictionary). Value range : Object : Default value : Type : [0 to 17] bts 17 DP
associatedLog
Description : Identifier of the log object that describes the associated records on the OMC-R agent disks. For an mdScanner object, this attribute is displayed provided mdLog = "logged". Value range : Object : Type : Restrictions : [0 to 2147483646] callPathTrace, mdScanner, traceControl - Display DI
[C/M]:
associatedTMUPosition
Description : Value range : Object : Feature : Default value : Type : Release : Note : Gives the number of the TMU hosting the active associated core process (hardware slot position). [Shelf Number (0 or 1) and Slot Number (from 1 to 15) of the TMU] btsSiteManager, signallingLinkSet, transcoder and pcu BSC 3000 cell group management/load balancing - stage 1 (139111). None DD V13 This parameter is only available for BSC 3000.
aterLapd
Description : Value range : ATER LAPD distribution and status. List of ATER LAPD descriptions [pcmAterId, tsAterId, lapdIsPresent, lapdIsOpened], with: pcmAterId: 0 to 65535 tsAterId: 0 to 65535 lapdIsPresent: yes / no lapdIsOpened: yes / no lsaRc BSC/TCU e3 GET DATA enhancement DD V16
atmRm
Description : The ATM RM (ATM Resource Module), which provides a SONET OC-3c (Optical Carrier level 3c) interface to allow direct connection between the Interface Node and the Control Node. [0 to 2147483646] atmRm DP V13
97
atmRmId
Description : Identifier of the atmRm object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000. [0 to 2147483646] atmRm DP V13
attenuation Class 2
Description : Value range : Object : Default value : Type : Release : Note : Attenuation due to coupling system losses. This value depends on the BTS configuration. [0 to 14] dB btsSiteManager Depends on the equipment. DP V9 If the attenuation parameter is set [0 to 14], then the DLU attenuation is replaced by the OMC attenuation parameter.
auditBdaStatus
Description : Value range : Synthetic result of a BDA audit [no difference / some differences (see list below) / many differences (see partial list below)] The information is stored in sessions logs.
no difference ...... some differences ...
Object instances in BDA and BDE are identical. Less than ten object instances are different in BDA and BDE (they are listed in the session logs). More than ten object instances are different in BDA and BDE (the first ten are listed in the session logs).
many differences ..
Object : Type :
bsc DI
auditState
Description : Whether an audit is in-progress in the BSC. Access to a BSC are blocked whenever an audit of its application database is in-progress (Audit BDA command). This attribute is unknown to the BSC and cannot be directly modified by users. When an audit is in-progress in a BSC, all configuration commands involving the BSS are forbidden. Value range : Object : Type : [inProgress / notInProgress] bsc DI
authorised user
Description : List of the users authorized to copy, display and run the command file. Enter their names as defined in their profiles and use the "&" character to separate them. commandFile DP
Object : Type :
availabilityStatus
Description : ISO state Refer to the operationalState entries in the Dictionary for a description of possible state parameter combinations for these objects: administrativeState, availabilityStatus, operationalState. Value range : Object : Type : [{} / {disabled} / {failed} ] bsc, bscMdInterface, lapdLink, pcmCircuit, signallingLink, transcoder DD
availabilityStatus
Description : ISO state Refer to the operationalState entries in the Dictionary for a description of possible state parameter combinations for these objects: administrativeState, availabilityStatus, operationalState. Value range : Object : [{} / {disabled} / {failed} / {unknown}] btsSiteManager, transceiver, transceiverEquipment,
99
Type : Note :
DD If the administrativeState of the object is unlocked and the availabilityStatus is unknown, the object status is undetermined. You must request the status of the bsc object on the OMC-R, to update the network view.
availabilityStatus
Description : ISO state The "enabled" state for a bts object is a transitory state that follows a soft release request. Refer to the administrativeState entry related to the bts object in the Dictionary. Value range : Object : Type : Note : [{} / {dependency} / {failed} /{unknown}] bts DD If the administrativeState of the object is unlocked and the availabilityStatus is unknown, the object status is undetermined. You must request the status of the bsc object on the OMC-R, to update the network view.
availabilityStatus
Description : Value range : Object : Type : ISO state {notInstalled}/{}/{failed}/{dependency}/{}] atmRM, cc, cem, controlNode, iem, interfaceNode, lsaRc, mms, omu, sw8kRm, tmu, trm, hsaRc, hsaRcTcu, iom DD
availabilityStatus
Description : ISO state The "logFull" state applies to a log object that describes an observation or trace log, and indicates that the saving message directory on the OMC-R agent disks is full. Refer to the capacityAlarmThreshold entry in the Dictionary. Value range : Object : Type : [{} / {logFull}] log DD
100
availabilityStatus
Description : Value range : Object : Type : ISO state [{} (the associated observation is running) / {offDuty} (the associated observation has ended)] mdScanner DD
availabilityStatus
Description : ISO state Refer to the operationalState entry in the Dictionary for a description of possible state parameter combinations: administrativeState, availabilityStatus, operationalState. Value range : Object : Feature : Type : Release : [{} / {dependency} / {failed}] pcu GPRS (SV407 - V12) DD V12
availabilityStatus
Description : ISO state Refer to the operationalState entry in the Dictionary for a description of possible state parameter combinations: availabilityStatus and operationalState. Value range : Object : Feature : Type : Release : [{} / {dependency} / {failed}] pcusn GPRS (SV407 - V12) DD V12
availabilityStatus
Description : ISO state Refer to the operationalState entry in the Dictionary for a description of possible state parameter combinations: administrativeState, availabilityStatus, operationalState, and usageState. A state change notification is issued after the soft release. Value range : [{} / {dependency} / {failed}]
101
Object : Type :
xtp DD
available synchronization sources

Description : Available synchronization sources gives all the synchronization signals detected by the BTS, regardless of the BTS current synchronization mode and of the synchronization mode selected at the OMC. This parameter is used in response of the "Display Data Information" (normal) action. Value range : [Abis synchronization only / Abis + external synchronization source coming from a master BTS / Abis + GPS connection detected] bts BTS synchronization
Object : Feature :
averagingPeriod Class 2
Description : Number of SACCH multi-frames over which the interference levels are averaged. This averaging will be performed immediately before the transmission of the RESOURCE INDICATION message. This attribute, together with the "thresholdInterference" attribute, allows users to manage interferences in radio cells. Refer to this entry in the Dictionary. Value range : Object : Default value : Type : [0 to 255] SACCH frame (1 unit = 480 ms on TCH, 470 ms on SDCCH) handOverControl 20 DP
B
backup manager addresses
Description : Object : Type Restrictions : Backup addresses of the OMC-R manager that receives the messages. They are provided by the manager. efd - Display DI
[C/M]:
102
backupServer
Description : Name of the backup OMC-R agent server if any. It is provided by the OMC-R agent. In a mono-server configuration with redundancy, this attribute is not filled in. Object : Type : md - Display DP
baseColourCode Class 3
Description : Value range : Object : Type : Checks : Base station Color Code assigned to a neighbor cell. The (BCC, NCC) pair forms the cell BSIC. [0 to 7] adjacentCellHandOver DP
[M]:
Each defined (baseColourCode, bCCHFrequency, networkColourCode) combination is unique in the set including a serving cell and its neighbor cells.
baseColourCode Class 2
Description : Base station Color Code assigned to a serving cell. It is broadcast on the cell SCH and is used to distinguish cells that share the same BCCH frequency. The (BCC, NCC) pair forms the cell BSIC. The information is broadcasted on the cell SCH. Several BCCs may be assigned to a same BTS. Hence, different codes can be allotted to cells that may have overlapping areas (adjacent cells). The Base Station Identity Code (BSIC) is a 6-bit code: bits 6-5-4 = NCC (PLMN color code), bits 3-2-1 = BCC (Base station color code). At cell level, the NCC bits can be used to increase BCC color possibilities when the NCC is not needed. Value range : Object : Type : [0 to 7] bts DP
103
Checks :
[M]:
Each defined (baseColourCode, bCCHFreq uency, networkColourCode) combination is unique in the set including a serving cell and its neighbor cells. Modification of bCCHFrequency, baseColourC ode and networkColourCode is forbidden while interference matrix is running.
[M]:
batteryRemoteControllerPresence Class 2
Description : Value range : Whether BRC (Battery Remote Controller) board is present or not. [0, 1]

Object : Default value : Type : Release : 0 DP
0: Not present 1: present
btsSiteManager
V15
bCCHFrequency Class 3
Description : Radio frequency allocated to a neighbor cell BCCH in the network frequency band. The information is broadcast on the serving cell SACCH. Value range : [1 to 124] (GSM 900 network), [955 to 1023] / [0 to 124] (GSM-R), [975 to 1023] / [0 to 124] (E-GSM), [512 to 885] (GSM 1800 network), [512 to 810] (GSM 1900 network), [128 to 251] (GSM 850 network), [955 / 974] for GSM-R, [975 / 1023] / [0] for GSM-R (EGSM BCCH), [1 / 55] for GSM-R (PGSM BCCH). The standardIndicator for GSM-R values is Rgsm. adjacentCellHandOver DP
Note : Object : Type : Checks :
[M]:
104
[M]: [C/M]:
The bCCHFrequency value must be set according to the standardIndicator attribute. For an adjacentCellHandOverNortel object instance, the bCCHFrequency can take one of the following values: [1 to 124] (GSM 900 network), [512 to 885] (GSM 1800 network), [512 to 810] (GSM 1900 network), [0 to 124] or [975 to 1023] (E-GSM), [128 to 251] (GSM 850 network), [0 to 124] or [955 to 1023] (GSM-R).
[C]:
Cannot create a new instance of adj acentCellUTRAN if the number of different bCCHFrequency parameters in adjacentCellHandOver object is equal to 32. The purpose of this check is to forbid UTRAN neighbour cell creation if 32 different BCCH frequencies are already declared for GSM neighbour cells. Cannot set the bCCHFrequency parameter on an adjacentCellHandOver object to a 32nd different value in the subset of adjacentCellHandOver instances belonging to the same upper bts if at least one instance of adjacentCellUTRAN is created. The purpose of this check is to forbid existence 32 different BCCH frequencies on the GSM neighbour cells under the same GSM cell if at least one UTRAN neighbour cell is declared. Modification of bCCHFrequency, baseColourC ode and networkColourCode is forbidden while interference matrix is running. Customer should not validate IM activation on a cell with 32 instances of adjacentCell (existing IM control) or with 31 instances of adjacentCell with 31 different values of bCCFFrequeny parameter if at least one instance of adjacentCellUTRAN is created. The purpose of this check is to warn customer on IM activation if at least one UTRAN neighbour cell is declared and the cell already has real neighboring cells with 31 different BCCH.
[C]:
[M]:
[C]:
105
Description : Radio frequency used for selection and re-selection management. The information is broadcast on the serving cell BCCH. Value range : [1 to 124] (GSM 900 network), [955 to 1023] / [0 to 124] (GSM-R), [975 to 1023] / [0 to 124] (E-GSM network), [512 to 885] (GSM 1800 network), [512 to 810] (GSM 1900 network), [128 to 251] (GSM 850 network), [955 / 974] for GSM-R, [975 / 1023] / [0] for GSM-R (EGSM BCCH), [1 / 55] for GSM-R (PGSM BCCH). The standardIndicator for GSM-R values is Rgsm. adjacentCellReselection DP
Note : Object : Type : Checks : Checks :
[M]: [C/M]:
The bCCHFrequency value must be set according to the standardIndicator attribute. For an adjacentCellReselection object instance, the bCCHFrequency can take one of the following values: [1 to 124] (GSM 900 network), [512 to 885] (GSM 1800 network), [512 to 810] (GSM 1900 network), [0 to 124] or [975 to 1023] (E-GSM), [128 to 251] (GSM 850 network), [0 to 124] or [955 to 1023] for GSM-R.
Note :
An adjacentCellReselection object can use the same BCCH as the serving cell to which it is associated. This allows a mobile to immediately recover the cell on which it was "camping" after being switched off, then switched back on, and is especially useful in the selection process.
Description : Radio frequency allocated to a cell BCCH (Broadcast Control CHannel) in the network frequency band. The information is broadcast on the cell SACCH. The BCCH frequency is automatically assigned to the radio time slot carrying the cell BCCH when the cell is brought into service (absoluteRFChannelNo attribute of the channel object describing the carrier TDMA frame TS0). It is broadcast to the radio time slot whenever modified.
106
The BCCH is used by the BTS for broadcasting cell related system information to MS, such as frequency band and list of frequency channels used, authorized services and access conditions, list of neighbor cells, and radio parameters (maximum transmission strength, minimum reception strength, etc.). Value range : [1 to 124] (GSM 900 network), [955 to 1023] / [0 to 124] (GSM-R), [975 to 1023] / [0 to 124] (E-GSM network), [512 to 885] (GSM 1800 network), [512 to 810] (GSM 1900 network), [128 to 251] (GSM 850 network), [955 / 974] for GSM-R, if at least one of the cell allocation ERFCN is in the [955 / 974] range, the BCCH must be also included within this range. [975 / 1023] / [0] (GSM-R (EGSM BCCH)), [1 / 55] (GSM-R (PGSM BCCH)). The standardIndicator for GSM-R values is Rgsm. bts DP
[M]: [M]:
The BCCH frequency is included in the cellAllocation list. Each defined (baseColourCode, bCCHFrequency, networkColourCode) combination is unique in the set including a serving cell and its neighbor cells. For a dualband cell, the bCCHFrequency attribute must be in the primary band of frequencies.
[M]:
bckgDLLayer3WindowSize Class 3
Description : Anticipation window size to be used in the context of BTS background downloading. It is used by SPR for BTS Abis downloading. [1..8] bsc 1 BSC 3000 support of BTS background downloading DP
Value range : Object : Default value : Feature : Type :
107
Release : Note :
V16 This parameter is mandatory. It is applicable to BSC 3000 only.
bdaNewBscState
Description : Value range : Current bsc state related to the new BDA [ready for on-line reset / running on-line reset / waiting for on-line build / waiting for software change / waiting for Bda change / running software change / running Bda change / waiting for end of probative phase / { }] bsc DI This attribute is modified by the OMC-R agent when processing "end of probative phase", "Activate New BDA", "On line reset BDA", or "On-line reset cancel" actions or receiving an unsolicited message sent by the BSC. This attribute is NULL { } as long as the BSC has not been connected to the OMC-R agent. Note : For a V10 BSC, this attribute is always NULL { }. The different states are obtained according to the following:
Object : Type : Remark :
"ready for on-line reset": This state is reached after the following occurrences: BSC complete restart "end of probative phase" or BDA "new" activation or reset on-line cancel succeeded partial or complete spontaneous BSC restart BSC operating command aborted
"running on-line reset": BSC reset on-line is being executed "waiting for on-line build": BSC reset on-line has succeeded "waiting for software change": "BDA version" reset on-line has succeeded "waiting for Bda change": "BDA edition" reset on line has succeeded "running software change": BSC Type 5 EFT activation is being executed
108

Release :
"running Bda change": BSC BDA "new" activation is being executed "waiting for end of probative phase": BSC Type 5 EFT activation has succeeded
V11
bdaSelected
Description : Value range : Object : Type : Remark : Current BSC Application Database (BDA) [running / new] bsc DI This attribute is modified by the MD-R when processing "On line reset BDA" actions or receiving a BSC spontaneous event. This attribute is set "running" at the bsc object instance creation For a V10 BSC, this attribute is never modified and its value is "running". Note : The different states are obtained according to the following:

Release :
"new": BSC upgrades with prototype BDA change "running": BSC upgrades without prototype BDA change
V11
bdaState
Description : Whether the BSC application database (BDA) is built. No transactions with a BSC can be implemented prior to building its application database. When a bsc object is created or following a user Off line reset BDA command, the value of this attribute is "not built". This attribute is unknown to the BSC and cannot be directly modified by users. It is updated by the system after a user Build BDA command. Value range : [built / not built / inconsistency]
109
Object : Type :
bsc DI
bdaVersionBuild
Description : Version number of the BSC application database for rebuilding purposes. When the BSC is initialized or following a user Off line reset BDA command, the value of this attribute is "0" (BDA not built). The BSC then sends a "build database request" message, indicating that its database is defective and needs rebuilding. By issuing a Build BDA command, the user informs the OMC-R that the BSC database must be regenerated. Value range : Object : Type : Checks : [1 to 254] bsc - Build BDA DP
[A]:
If the command follows a BSC architecture change, the new architecture complies with the information 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 is assigned the bdaVersionBuild value sent with the user build command. If the BDA is being regenerated following an On line reset BDA command, this attribute gives the user the version number of the BDA currently used by the BSC. Value range : Object : Type : [0 to 254] bsc DD
110
beacBatteryRemoteControllerPresence Class 2
Description : Value range : Object : Type : Release : Whether the optional equipment Battery Remote Controller (BRC) is present or absent in S8000 outdoor or S8002. [Present, Absent] btsSiteManager DP V15
beginning date
Description : To select call monitoring data recorded on that date and thereafter. Do not fill in if information produced from the start is displayed. Value range : Object : Type : Checks : [mm/dd/yyyy hh:mm:ss] Call monitoring - Display SDO DP
[A]:
beginning date is on or before end date.
beginSearchTime
Description : Absolute time to start searching for the observation reports to cumulate. Observation data accumulating starts with the information contained in the last observation message collected in the requested period of time. Refer to the partnered endSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Checks : [<date> , <time>] Display custom report DP
[A]: [A]:
beginSearchTime is after endSearchTime. The defined period is less than or equal to six hours.
111
beginSearchTime
Description : Absolute time to start searching for the observation report to edit default is the current date and time). The report displays the information contained in the last observation message generated in the requested period of time. Refer to the partnered endSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Checks : Note : [<date>,<time>] Display raw report DP
[A]:
beginSearchTime is after endSearchTime.
If no permanent observation has been received within the specified period, a message is displayed.
beginSearchTime
Description : Absolute time to start searching for the available permanent observations to list (default is the current date and time). The first listed report is the last observation report generated in the requested period of time. Refer to the partnered endSearchTime entry in the Dictionary. Value range : Object : Type : Checks : [<date> , <time>] List available permanent observations DP
[A]:
beginSearchTime
Description : Absolute time to start searching for the available temporary observations to list (default is the current date and time). The first listed report is the last observation report generated in the requested period of time. Refer to the partnered endSearchTime entry in the Dictionary.
112
Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Checks : [<date> , <time>] List available temporary observations DP
[A]:
beginSearchTime
Description : Absolute time to end searching for the observation messages to list (default is twelve days before beginSearchTime). The last listed message is the first observation message generated in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Checks : [<date> , <time>] List observation messages DP
[A]:
bEPPeriod Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Note : When EDGE is activated in the cell, the field is present and indicates the BEP filter averaging period to the MS. 0 to 15 bts EDGE traffic management (20231) 0 DP V15 Values 11 to 15 are reserved in tge 3GPP specification and shall not be used. 10 is the recommended value.
113
biZonePowerOffset Class 3
Description : Power offset between the inner TRXs and the outer TRXs of the adjacentCellHandOver object of a dualband, dualcoupling, or concentric cell. Offset added in calculation formula to draw up the list of eligible cells for handover towards a dualband, dualcoupling, or concentric cell inner zone to take into account the difference of propagation models between the two bands of the cells and the difference of transmission power between TRXs of the two zones due to either BTS configuration or coupling. Value range : Object : Default value : Feature : Type : Release : Note : [-63 to 63] dB adjacentCellHandOver If main band = 850MHz 3dB If main band = 1900MHz -3 dB Dualband cell management (TF875 - V12) DP V12 This parameter is only available for S8000 or e-cell BTS DRX transceiver architecture.
biZonePowerOffset Class 3
Description : Power offset between inner and outer TRXs of the handOverControl object of a dualband, dualcoupling, or concentric cell. [-63 to 63] dB handOverControl Dualband cell management (TF875 - V12) If main band = 850MHz 3 dB If main band = 1900MHz -3 dB DP This parameter is only available for S8000 or e-cell BTS DRX transceiver architecture.
Value range : Object : Feature : Default value : Type : Note :
Release : V12
zoneTxPwrMaxReduction (inner zone)
114
bsc3GEqpt
Description : Value range : Object : Type : Release : Identification and dynamic data describing the hardware configuration of a BSC 3000 (global point of view). [0 to 0] bsc3GEqpt DP V13
bsc3GEqptId
Description : Identifier of the bsc3GEqpt object class. This identifier is allocated by the MD-R at object creation. The only value allocated by the MD-R is 0. This attribute cannot be modified. This attribute is relevant for BSC 3000. [0 to 0] bsc3GEqpt DP V13
bsc
Description : Identifier of a bsc object on the OMC-R. The bsc reference is part of all BSS configuration object identifiers. In all MMI commands, a bsc object can be referenced by name (bscName). When a bsc object is created and the referenced bscMdInterface object is unlocked, the system attempts to establish the BSS/OMC-R link connection. Value range : Object : Type : Checks : [1 to 255] bsc Id
[C]:
The number of BSCs managed by an OMC-R is limited to maxBscPerNetwork (static configuration data). The referenced bscMdInterface object (bscMdInterfaceRef) is created.
[C]:
115
[D]:
The BSC application database has been reset by an Off line reset BDA command (bdaState = "not built"). No mdScanner, traceControl, or callPathTrace object refers to the bsc object (no observation or trace function is active in the BSC).
[D]:
bsc
Description : Identifier or name of a bsc object on the OMC-R. It defines the parent bsc object. Value range : Object : [1 to 255] adjacentCellHandover, adjacentCellReselection, bts, btsSiteManager, channel, frequencyHoppingSystem, handOverControl, lapdLink, multiple site, pcmCircuit, powerControl, signallingLink, signallingLinkSet, signall ingPoint, software, transceiver, transceiverEquipment, transceiverZone, transcoder, xtp Id
Type : Checks :
[C]:
The bsc object is created.
bsc equipment name

Description : To select messages issued by a given type of BSC or TCU processor. Do not fill in if this criterion is not to be selected. Value range : [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/slti] Alarm and notification logs - Filter GPRS (SV407 - V12) DP "css7" identifies the BSC CCS7 boards; "signalling link" identifies the SS7 signalling links defined in the BSS and controlled by the CCS7 boards.
Object : Feature : Type : Remark :
116
bscList
Description : List of the BSCs simultaneously monitored for further data processing by the SDO machine. Fill in the list with BSC reference numbers or names, up to maxBscPerNetwork. Do the following to create the list:
To add a BSC, fill in the bscNumber field with the reference number of the BSC on the OMC-R and click Add. To remove one or more BSCs, select the lines that display their reference numbers and click Remove.
When the list is complete, click the option matching the desired command, as follows:
Start: ........... Stop: ............ Transfer: ......... Processing: .......
starts collecting call monitoring data in the selected BSCs. stops collecting call monitoring data in the selected BSCs. transfers the BSC selected data files to the OMC-R. copies and processes the selected data files in the SDO machine. A set of resultant ASCII data files is produced, it is identified as the Level 1 set.
Value range : Object : Type Checks :
[1 to 255] Call monitoring - Commands (SDO) DP
[A]:
The number of BSCs in the list is limited to maxBscPerNetwork (static configuration data). Each BSC occurs once in the list.
[A]:
Notes :
The user must make sure that the BSCs in the list are created on the OMC-R since no checks are performed by the system. Processing: The call monitoring data files are meant to exist in the "/MD/ftam/bsc" directory on the OMC-R agent disks. For each BSC in the list, all files saved in that directory whose name begins with "SDO_CM_BSCnnn" will be processed: "nnn" is the
117
BSC reference number on the OMC-R (if bsc = 5, then nnn is read "005"). See NTP < 07 >.
The bscList needs not be defined when selecting the Query command which displays the activity state of the Call monitoring function in all the BSCs connected to the OMC-R.
bsc model
Description : Value range : To select messages issued by a given model of BSC. bsc 3000 Do not fill in if this criterion is not to be selected. Object : Type : Note : Alarm and notification logs - Filter DP bsc30000 is the value that must be used for this parameter in case of a BSC 3000.
bscNumber
Description : Identifier [1 to 255] or name of a BSC to add to the bscList. Fill in this field and click Add to add the BSC to the list. Refer to the bscList entry in the Dictionary. Object : Type Call monitoring - Commands (SDO) DP
bscArchitecture Class 0
Description : Value range : Architecture of the BSC [bsc30000 / bsc30000 optical]

Object : Type : DP
bsc30000 is the value that must be used for this parameter in case of a BSC 3000. bsc30000 Optical
bsc
118
Checks :
[C/M]:
The maximum PCM number is set to 231 (E1) /308 (T1) at the OMC-R when the bscArchitecture parameter is set to bsc30000Optical. When bscArchitecture equals bsc30000Optical, valid pcmCircuitId are:
[C/M]:
[0, 104] for LsaRC E1 [147, 272] for HsaRC E1 [0, 139] for LsaRC T1 [196, 363] for HsaRC T1
This semantic check checks the validity of the pcmCircuitId when bscArchitecture equals bsc30000 Optical.v
ATTENTION
The bsc30000 Optical Capacity values apply to BSC 3000 only.
bscCapacityReduction Class 3
Description : This attribute allows to reduce the traffic on the BSC in order to protect the MSC against high traffic load. This attribute can only be modified if the bsc object instance is unlocked Value range : Object : Type : Release : Int [0 to 9] bsc, signallingPoint DP V14
bscCounterList
Description : Value range : Object : Type : Release : Identifier of the bscCounterList object defined with regards to the bsc object. [0 to 2147483646] bscCounterList Id V11
119
bscDateTime
Description : Current BSC reference date and time. This attribute is set by a user Synchronize bsc clock command, which broadcasts the current OMC-R agent date and time to the concerned BSC. It is also updated by the OMC-R agent in the following conditions:
A user Set command on the md object is run, which changes its 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-R manager when the time difference with a BSC drifts too much. Value range : Object : Type : [<date>,<time>] bsc DD
bscGprsActivation Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Flag used to activate the GPRS at BSC level. [disabled / enabled] bsc GPRS (SV407 - V12) disabled DP V12
bscHighSwitchingCapacity Class 3
Description : Value range : Object : Feature : Default value : This parameter on the BSC enables the DS512 feature. [disabled / enabled] bsc BSC 3000 switching increase capacity (24436) disabled
120
Type : Release :
DP V15
bscHopReconfUse Class 1
Description : Whether frequency hopping reconfiguration is authorized in BTSs that use cavity coupling. When frequency reconfiguration is authorized, it allows to automatically reconfigure the hopping sequence whenever a frequency is lost or recovered in the BTS. Value range : Object : Default value : Type : Checks : [true / false] bsc True DP
V8
[M]:
It can be "true" provided the btsHopReconfR estart of one of the related bts objects is also "true".
Release :
bscIPFirstAdr Class 2
Description : Indicates the first BSC IP address used for a bscMdInterface object instance. IP address corresponds to the subscriber number on the network used. This attribute is modified by the Manager. Value changes are notified to the Manager. Value range : Object : Type : Checks : [7 to 15] String bscMdInterface DP
[C/M]:
The IP address must not already be used in a first address for another bscMDInterface object instance. The IP address must not already be used in a second address for another bscMDInterface object instance.
[C/M]:
Release :
V13
121
bscIPSecondAdr Class 2
Description : Indicates the second BSC IP address used for a bscMdInterface object instance. IP address corresponds to the subscriber number on the network used. This attribute is modified by the Manager. Value changes are notified to the Manager. Value range : Object : Type : Checks : [7 to 15] String bscMdInterface DP
[C/M]:
The IP address must not already be used in a first address for another bscMDInterface object instance. The IP address must not already be used in a second address for another bscMDInterface object instance.
[C/M]:
Release :
V13
bscList
Description : This attribute indicates for which BSC(s) the units of software has been downloaded. This attribute is allocated by the MD-R at object creation. This attribute cannot be modified by the Manager. This attribute is updated by the MD-R when a "sWDownload" command is performed successfully. Value changes are notified to the Manager. Value range : Object : Type : Release : [0 to 41] executableSoftware DP V13
bscLog
Description : Value range : Object : bscLog modelizes the management of the BSC internal log files. [bscVers13 +Inf] bscLog
122
Type : Release :
DP V13
bscLogId
Description : Identifier of the bscLog object class. This identifier is allocated by the MD-R at object creation. This attribute cannot be modified. This attribute is relevant for BSC 3000. Value range : Object : Type : Release : [bscVers13 +Inf] bscLog DP V13
bscMdInterface
Description : Value range : Object : Type : Checks : Identifier of a bscMdInterface object defined with regard to the md object. [0 to 255] bscMdInterface Id
[D]:
No bsc object refers to the bscMdInterface object.
bscMdInterfaceRef
Description : Value range : Object : Type : Checks : Restrictions : Identifier of the bscMdInterface object that describes the BSS/OMC-R link involving the BSC. [0 to 255] bsc DP
[C]: [M]:
No bsc object refers to the bscMdInterface object. This attribute cannot be modified.
123
bscMdInterfaceVersionNumber
Description : Release number of the BSC/OMC-R interface. It is provided by the BSC when the BSS/OMC-R link is physically established. If the release number does not match the software version running in the BSC (sWVersionRunning attribute of the related software object), the BSC issues a start-of-fault message. Value range : Object : Type : Restrictions : [11 to 99] bsc - Display DI
[C/M]:
bscMSAccessClassBarringFunction Class 3
Description : Value range : Object : Default value : Type : Release : Enables or disables dynamic barring of access class at the bsc level. [enabled / disabled] bsc disabled DP V9
bscName
Descriptio n: Value range : Object : Type : Checks : Reference name of a bsc object on the OMC-R. It begins with a letter and is case sensitive. [30 characters max.] bsc DP
[C/M]:
The name of a BSC is unique to the OMC-R.
124
Release : Note :
V13 Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited. The valid symbols are: - letter characters: A, B, C..., Z, a, b, c..., z - digit symbols: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 - minus sign: - undescore: _ - space
bscPcuPcmRefList Class 2
Description : Value range: List of BSC-PCU PcmCircuit. BSC 3000 V15: [1 to 24] values in the range [0..167] BSC 3000 V16, E1 PCM: [1 to 32] values in the range [0..167] BSC 3000 V16, T1 PCM: [1 to 36] values in the range [0..167] BSC 3000 V17: [1 to 54] values in the range [0..167] BSC 3000 optical V17: T1 [1..54] values in range [0..363]; E1 [1..54] values in range [0..272] pcu 18749 (PCUSN - more than 12 Agprs PCMs per BSC), (step 1: up to one full PCUSN shelf per BSC). DP
Object : Feature : Type : Checks :
[C/M]: [C/M]: [C/M]:
All the referred pcmCircuit object instances of this attribute must exist. The referred pcmCircuit object instances must be of pcmAgprs type (pcmType attribute). The referred pcmCircuit object instances must not be already referred to another pcu object instance on the same BSC.
Release :
V12
125
bscQueueingOption Class 1
Description : Whether radio resource allocation requests are queued in the BSC when no resources are available. If no resource is available when an allocation request is received and queueing is not allowed, the allocation request is refused immediately. Value range : [allowed (MSC driven) / forced (O&M driven) / not allowed]
allowed ..........
Resource allocation request queueing depends on the type of operation and indicative items provided with the messages received from the MSC. Resource allocation request queueing depends on the type of operation only. Resource allocation request queueing is forbidden.

Object : Default value : Type : Note :
forced ...........
not allowed .......
signallingPoint forced DP Allocation requests for immediate assignments and inter-bss, intra-bss, and inter-bts handovers are never queued. Only TCH resource requests (assignments request and intraCell handover) are queued depending on the priority of the demand and the number of request present in the queue.
bscRefList
Description : Value range: List of the bsc objects managed by a pcuSN object. V15: [0 to 12] values in the range [1 to 255] V16, E1/T1 PCM: [0 to 18] values in the range [1 to 255] The BSS system does not take into account the value range [17 to 18] for an E1 configuration. V17: [0 to 27] values in the range [1 to 255] pcusn DP GPRS (SV407 - V12) V12
Object : Type : Feature : Release :
126
bscReset
Description : Value range : Object : Type : Release : Requests a control node reset. [0 to 1] bsc3GEqpt DP V13
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 that defines it on BSC end and BTS end. The Abis interface connects a BTS to a BSC through PCM links that are identified by the boards to which they are connected on both ends of the interface, that is DDTI boards on 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 a pcmCircuitBsc reference equal to "2i" or "2i+1" with regard to the BSC (each board manages two links at a time). Refer to Nortel GSM BSC Reference Manual. The same PCM link connected to DTI board no.j in the BTS has a pcmCircuitBtsSiteManager reference equal to "j" with regard to the BTS (each board manages one single link). Refer to Nortel GSM BTS Reference Manuals.
The number of pairs in the list sets the number of links allotted to the radio site. Value range : list (1..6) of (pcmCircuitBsc, pcmCircuitBtsSiteManager) pairs. Refer to pcmCircuitBsc and pcmCircuitBtsSiteManager entries for more information on their value ranges. Object : Type : Checks : btsSiteManager DP
[C]:
The number of PCM links allotted to a site is limited to maxPcmCPerBtsSM (static configuration data).
127
[C/M]:
The list contains at least one pair, two if the btsSiteManager object redundantPcmPresence attribute is "true". Each pair is unique in the list. Each pcmCircuitBsc reference matches a pcmCircuit object created for the parent bsc object and assigned to the Abis interface (pcmType = "pcmAbis"). If a pcmCircuitBsc reference is changed, the current link is not used by any dependent transceiverEquipment object.
[C/M]: [C/M]:
[M]:
bscTimeSlot
Description : PCM link (pcmCircuitId) and timeslot (timeSlotNumber) used by the radio timeslot on the Abis interface. The PCM link is identified on BSC end [0 to 47]. The information is displayed provided that the parent transceiver object is working. Refer to the operationalState entry for this object in the Dictionary. Value range : Object : Type : pcmCircuitId [0 to 47] timeSlotNumber [1 to 31 (E1 PCM) or 24 (T1 PCM)] channel DD
bscUsedAdr
Description : Value range : Object : Type : Release : BSC address actually used. This attribute is managed by the MD-R. Value changes are not notified to the Manager. [X25 / IP] bscMdInterface DP V13
bsCvMax Class 3
Description : Value range : Object : Feature : Default value : Number of packets left to transmit divided by the number of UL TS allocated to the MS. [1 to 15] bts GPRS (SV407 - V12) 1
128
Type : Remark : Release :
DP bsCvMax is broadcasted in the system information. V12
bscX25PrefAdr Class 2
Description : X.25 priority address used by the BSC. It corresponds to the subscribers number in the X.25 network. [15 decimal figures max.] bscMdInterface $BSC{bscId}_X25P DP
Value range : Object : Default value : Type : Checks :
[C/M]:
The X25 address must not already be used in a preferential address for another bsc object instance. The X25 address must not already be used in a secondary address for another bsc object instance.
[C/M]:
Note :
For a BSC 3000, this parameter is available and visible on the OMC-R MMI, but it is not used.
bscX25SecAdr Class 2
Description : X.25 address used by the BSC as backup. It is identical to the priority address when there is no redundancy. It corresponds to the subscribers number in the X.25 network. [15 decimal figures max.] bscMdInterface $BSC{bscId}_X25S DP
[C/M]:
The X25 address must not already be used in a secondary address for another bsc object instance. The X25 address must not already be used in a preferential address for another bsc object instance.
[C/M]:
Note :
For a BSC 3000, this parameter is available and visible on the OMC-R MMI, but it is not used.
129
bsPowerControl Class 3
Description : Value range : Object : Default value : Type : Whether BTS transmission power control is allowed at cell level. [enabled / disabled] powerControl disabled DP
bssMapT1 Class 1
Description : A interface timer triggered by the BSC in the BSSMAP management procedure. It is started on transmission of BLOCK or UNBLOCK by the BSC and canceled on receipt of BLOCK ACKNOWLEDGE or UNBLOCK ACKNOWLEDGE sent by the MSC. Value range : Object : Default value : Type : [2 to 300] seconds bsc 5 DP
bssMapT4 Class 1
Description : A interface timer triggered by the BSC in the BSSMAP management procedure. It is started on transmission of RESET and canceled on receipt of RESET ACKNOWLEDGE sent by the MSC. On elapse, the BSC sends RESET. Value range : Object : Default value : Type : [5 to 600] seconds bsc 60 DP
130
bssMapT7 Class 1
Description : A interface timer triggered by the BSC in the BSSMAP management procedure. It is started on transmission of HANDOVER REQUIRED and canceled on receipt of HANDOVER COMMAND, RESET, RESET CIRCUIT, CLEAR COMMAND or HANDOVER REQUIRED REJECT. Value range : Object : Default value : Type : [2 to 120] seconds bsc 7 DP
bssMapT8 Class 1
Description : A interface timer triggered by the BSC in the BSSMAP management procedure. It is greater than t3103 for all BTS object instances attached to the BSC. It is started on transmission of HANDOVER COMMAND and canceled on receipt of CLEAR COMMAND sent by the MSC or HANDOVER FAILURE sent by MS. Value range : Object : Default value : Type : Checks : [0 to 255] seconds bsc 15 DP
[C/M]:
bssMapT8 > t3103 for all BTS objects dependent on the BSC object.
bssMapT12 Class 1
Description : A interface timer triggered by the BSC in the BSSMAP management procedure. This timer is used with a Phase I MSC only. It is started on transmission of RESET CIRCUIT by the BSC and canceled on receipt of RESET CIRCUIT ACKNOWLEDGE sent by the MSC. Value range : Object : Default value : Type : [2 to 300] seconds bsc 5 DP
131
bssMapT13 Class 1
Description : A interface timer triggered by the BSC in the BSSMAP management procedure. It is started on receipt of RESET sent by the MSC. On elapse, the BSC sends RESET ACKNOWLEDGE to the MSC. Value range : Object : Default value : Type : [2 to 300] seconds bsc 32 DP
bssMapT19 Class 1
Description : A interface timer triggered by the BSC in the BSSMAP management procedure. This timer is used with a Phase II MSC only. It is started on transmission of RESET CIRCUIT by the BSC and canceled on receipt of RESET CIRCUIT ACKNOWLEDGE sent by the MSC. Value range : Object : Default value : Type : Release : [2 to 300] seconds bsc 32 DP V8
bssMapT20 Class 1
Description : A interface timer triggered by the BSC in the BSSMAP management procedure. It is started on transmission of CIRCUIT GROUP BLOCK or CIRCUIT GROUP UNBLOCK by the BSC and canceled on receipt of CIRCUIT GROUP BLOCK ACKNOWLEDGE or CIRCUIT GROUP UNBLOCK ACKNOWLEDGE sent by the MSC. Value range : Object : Default value : Type : Release : [2 to 300] seconds bsc 32 DP V8
132
bssMapTchoke Class 1
Description : A interface timer triggered by the BSC in the handover management procedure. It is started by the BSC when the last neighbor cell in the list is rejected. On timer elapse, the BSC asks the MSC to provide a new list of eligible cells. Value range : Object : Default value : Type : [1 to 255] seconds bsc 4 DP
bssPagingCoordination
Description : Value range : Object : Default value : Type : Enable BSS Cs paging coordination disabled/enabled bts 0 (recommended) DP
bssSccpConnEst Class 1
Description : A interface timer triggered by the BSC in the handover management procedure. It is set on transmission of CONNECTION REQUEST and canceled on receipt of CONNECTION CONFIRM or CONNECTION REFUSED. Value range : Object : signallingLinkSet (BSC 3000 from V15) Default value : Type : Checks : 5 DP [5 to 360, by steps of 5] seconds
[C/M]:
bssSccpConnEst parameters must have the same values for both A and Lb signallingLinkSet instances.
133
bssSccpInactRx Class 1
Description : A interface timer T(iar) triggered by the BSC in the SCCP inactivity detection procedure. It is set either on transmission or receipt of CONNECTION CONFIRM or on receipt of any other message during the connection and canceled on receipt of any message. Value range : Object : signallingLinkSet (BSC 3000 from V15) Default value : Type : Checks : 11 DP [2 to 30] minutes
[C/M]:
bssSccpInactRx parameters must have the same values for both A and Lb signallingLinkSet instances.
bssSccpInactTx Class 1
Description : A interface timer T(ias) triggered by the BSC in the SCCP inactivity detection procedure. It is set either on transmission or receipt of CONNECTION CONFIRM or on transmission of any other message during the connection and canceled on transmission of any message. Value range : Object : Default value : Type : Checks : [1 to 15] minutes signallingLinkSet (BSC 3000 from V15) 5 DP
[C/M]:
bssSccpInactTx parameters must have the same values for both A and Lb signallingLinkSet instances.
bssSccpRelease Class 1
Description : A interface timer T(rel) triggered by the BSC in the SCCP management procedure. It is set on transmission of RELEASE and canceled on receipt of RELEASED COMPLETE or RELEASED. Value range : Object : Default value : [1 to 20] seconds signallingLinkSet (BSC 3000 from V15) 10
134
Type : Checks :
DP
[C/M]:
bssSccpRelease parameters must have the same values for both A and Lb signallingLinkSet instances.
bssSccpSubSysTest Class 1
Description : A interface timer T(state info) triggered by the BSC in the SCCP management procedure. It is set on transmission of SST and canceled on receipt of SSA. Value range : Object : Default value : Type : Checks : [5 to 60, by steps of 5] seconds signallingLinkSet (BSC 3000 from V15) 30 DP
[C/M]:
bssSccpSubSysTest parameters must have the same values for both A and Lb signallingLinkSet instances.
bsTxPwrMax Class 3
Description : Maximum theoretical level of BTS transmission power in a cell. The BSC relays the information to the mobiles in the Abis CELL MODIFY REQUEST message.
For concentric cells, dualband cells and dualcoupling cells: The value of PwrReqSentToPowerAmplifier is equal to the value of bsTxPwrMax added to the value of DLU attenuation (depending on the coupling equipment type, that is for instance D, H2D, H4D, etc.) or Attenuation on the btsSiteManager (if Attenuation has a value), and reduced of the value of Zone Tx power max reduction of the transceiverZone. For PA: the value of PwrReqSentToPowerAmplifier must be between 31dB and 44dBm. This value range is valid for Radio Module (RM). For HePA: the value of PwrReqSentToPowerAmplifier must be between 34dB and 47dBm. This value range is valid for High Power Radio Module (HPRM). For MePA: the value of PwrReqSentToPowerAmplifier
135
between 33dB and 46dB. This value range is valid for Medium Power Radio Module (MPRM).
For mono zone cells:
Value range : Note : Object : Type : Checks :
The value of PwrReqSentToPowerAmplifier is equal to the value of bsTxPwrMax added to the value of DLU attenuation (depending on the coupling equipment type, that is for instance D, H2D, H4D, etc.) or Attenuation on the btsSiteManager (if Attenuation has a value). [2 to 51] dB The recommended value is 43 dB. powerControl DP
[M]:
For a normal cell, the use of the block edge channels must induce a cell power limitation to 40 dB for PCS networks, and 42 dB for GSM 850 networks. For a concentric cell, the use of the block edge channels in the large zone and in the small zone must induce a cell power limitation to 40 dB for PCS networks and 42 dB for GSM 850 networks (bsTxPwrMax zoneTxPwrMaxReduc) For a dualband cell and, the use of the block edge channels in the large zone and in the small zone must induce a cell power limitation to 40 dB for PCS - GSM850 networks and 42 dB for GSM850 - PCS networks (bsTxPwrMax zoneTxPwrMaxReduc) For a dualcoupling cell, the use of the block edge channels in the large zone and in the small zone must induce a cell power limitation to 40 dBm for PCS networks and 42 dBm for GSM850 networks (bsTxPwrMax - zoneTxPwrMaxReduc bizonePowerOffset)
[M]:
[M]:
[M]:
Note :
Some bsTxPowerMax values are not compatible with the effective power output by the BTS.
136
Remark :
For a GSM 1900 network (standardIndicator of bts object set to pcs1900), the MD-R checks the following: bsTxPwrMax < 32 (dB) when an edge frequency is defined for the cell (i.e. if the value is 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-R configuration file, MD/base/config/boundEdge.cfg. This file is can be configured off-line. To update the database according to the list of edge frequencies, use the shell /MD/install/shell/cm_configBde.sh.
bts
Description : Identifier of a bts object defined with regard to a btsSiteManager object. All channel, transceiver, and transceiverEquipment objects in a BSS are identified with regard to a bts object that defines the covering cell. In all MMI commands, a bts object can be referred to by the sequence "siteName.cellName" where siteName and cellName identify the covering site and the cell respectively by name. Value range : Object : Type : Checks : [0 to 5] bts Id
[C]:
The number of cells managed by an OMC-R is limited to maxBtsPerNetwork (static configuration data). The number of cells attached to a radio site is limited to maxNbOfCells (attribute of the parent btsSiteManager object). The software object related to the parent btsSiteManager object is created. The mobileCountryCode and mobileNetwork Code attributes match those of the parent bsc object if they are defined for that object (cell CGIs must comply).
[C]:
[C]: [C]:
137
[C/M]:
The adjacent cell umbrella Ref attribute is defined if the cell is a microcell (cellType) and directed retry handovers are processed in BSC mode (directedRetryModeUsed). If the application database of the related BSC is built, the parent bsc object is unlocked and the parent btsSiteManager object is locked. If the application database of the related BSC is built, the parent bsc object is unlocked, the parent btsSiteManager object is locked, and the bts object is locked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command. No adjacentCellHandOver object refers to the bts object (the described cell is not used as a neighbor cell of another serving cell). No mdScanner object describing a temporary observation refers to the bts object (no observation is running on the described cell). No traceControl or callPathTrace object refers to the bts object (no tracing is running on the described cell).
[C]:
[D]:

Note :
[D]:
[D]:
[D]:
[D]:
All cells covered by a given radio site must be created in numerical ascending order and deleted in the reverse order.
bts
Description : Value range : Object : Identifier or name of a bts object. It defines the associated bts object. [0 to 5] adjacentCellHandOver, adjacentCellReselection, channel, frequencyHoppingSystem, handOverControl, powerControl, software, transceiver, transceiverEquipment, transceiverZone. Id
Type : Checks :
[C]:
The bts object is created.
138
bts equipment name

Description : To select messages issued by a given type of BTS equipment. Do not fill in if this criterion is not to be selected. Value range : [[BTS main power / converterB/ converter C/ converterA/CSW1 / CSW2 / CSW1M/ TX / SYN / SYNO /ALAT / ALATO / DCC / DTI / RX splitter / TX splitter / antenna / column system RX / converter D / column system TX / door contact / fan system / RX fan / TX fan / cabinet fan / fans rack / MWT system / exchanger system / rectifiers groups / distribution system / fuses system / breakers / battery system / temperature system / smoke detector / CSWM/SYNC/ALCO/DSC/PCMI / GTW / PCM0 / PCM1 / rectifier 48V / converter F / converter BCF / battery disconnected switch /cooler system /LNA / VSWR / user system / distribution box / battery cabinet / main breaker / diu / external alarm / VGA/ DLNA/MNU/DCU/RX/ DBF / AMNU / DCU4 / DRX / FPRX / Lightning Protection / BCF Cabinet door / BCF Cabinet fan / SBCF / PA / AC power supply / DC power supply / transmit antenna / cabinet high temperature alarm/ cabinet low temperature alarm / EXTERNAL CONTACT ACCESS / drxmain reception chain / drx diversity reception chain / splitter output / high power module / splitter / low power RF module / rf supply module / CMCF / PCM / CPCMI / RECAL / rx splitterM / rx splitter D / combiner h4 lna / combiner h4 vswr / txFilter / combiner rx filter lna / combiner d vswr / rxMainConnector / rxDivConnector / dacsCooler / compact dacs cooler / compact distribution / PMNU / RDRX / PMOD / BTS Synchronisation / PSU / Heatsink / Preventive lightning protection / Battery / External Environment / SLTI / SALCO / not protected alarm / internal temperature / external temperature / Remote Tunable Cavity Combiner / Cavity /battery monitored / blower tray / S12000 rectifier / S12000 smoke detector / S12000 lightning protection / S12000 battery disconnected / S12000 cooler / Edge High PA / Edge DRX / Edge PA / CMCF phase 1 /CMCFphase2 /CMCFphase 3 /DRXND3/ ICM/ IFM/ABM / RM/ RM_PA / RM_TRX / HPRM / HPRM PA / HPRM TRX / MPRM / MPRM_TRX / MPRM_PA / TRX MAIN RECEPTION CHAIN / TRX DIV RECEPTION CHAIN / DDM / DDM MAIN LNA / DDM DIV LNA / DDM 1 VSWR / DDM 2 VSWR / DDM_H2 / DDM_H2 MAIN LNA / DDM_H2 DIV LNA / DDM_H2 1 VSWR / DDM_H2 2 VSWR / TX FILTER / TX FILTER VSWR / TX FILTER H2 / TX FILTER H2 VSWR / SICS / ECU / TRX / H4]
139
Object : Type :
Alarm and notification logs - Filter DP
bts list
Description : List of the cells involved in broadcasting the short message. Enter the (bsc, btsSiteManager, bts ) reference of each bts object. short message - Start broadcast DP
[A]: [A]:
Each bts object in the list is created. Each bts object in the list is assigned a CBCH, that is there is one channel object in the set of transceiver objects dependent on the bts object whose channelType is "bcchSdcch4CBCH" or "sdcch8CBCH". No more than five short messages are being broadcast in the cells at that time.
[A]:
btsSMSynchroMode Class 2
Description : Object : Value range : Type : Feature : Default value : Checks : Type of site synchronization. btsSiteManager [normal / master / slave / gpsBurstSync, gpsTimeSync / masterGpsBurstSync / masterGpsTimeSync] DP Network Synchronization normal (synchronized on Abis link)
[C/M]:
slave, gpsBurstSync or gpsTime Sync values are allowed only if btsModel is S8000 CBCF, S12000, or BTS 18000. slave, gpsBurstSync or gpsTime Sync values are allowed only if btsModel is S8000 CBCF, S12000, BTS 6000 or BTS 18000. master, masterGpsBurstSync or masterGpsTi meSync values are allowed only if btsModel is S8000 CBCF or S12000.
Checks:
[C/M]:
Release : Note :
C/M]:
V15 This parameter is optional. It is only available for BSC 3000 V.15 and later, and applicable since BSC 3000 V15.1.1.
140
bts time between HO configuration Class 3

Description : Whether the HOPingpongTimeRejection timer can be used at bts level when processing handovers. Refer to bts object btstimeBetweenHOConfiguration and adjacentCellHandOver object hoPingpongTimeRejection attributes in this Dictionary of Parameters. Value range : Object : Feature : Default value : Type : Release : [0 / 1] bts General protection against ping-pong handovers (TF821 - V12) 0 DP V9
btsDescription
Description : BTS configuration description (BTS type, configuration, coupling system, etc.) corresponding to the transcription of configRef attribute. [chain of characters] btsSiteManager DI V10 It designates the maximum configuration of the configRef file loaded on one of the BTSs. But it does not necessarily corresponds to the configuration of the btsSiteManager object concerned.
Value range : Object : Type : Release : Note :
btsHopReconfRestart Class 2
Description : Value range : Object : Default value : Type : Checks : Whether hopping frequency reconfiguration is authorized on TX restart in a cell. [true / false] bts true DP
V8
[C/M]:
If the attribute value is "true", the bscHopReco nfUse attribute of the parent bsc object is also "true".
Release :
141
btsIsHopping Class 2
Description : Value range : Object : Default value : Type : Checks : Whether frequency hopping is allowed in a cell. [hopping / noHopping / hoppingWithCarrierFilling (V8) / noHoppingWithCarrierFilling (V8)] bts Hopping DP
[M]:
If frequency hopping is allowed, the GSM "fhMgt" function is defined in the siteGsmFctList attribute of the parent btsSiteManager object. If it is disabled, no channel object dependent on the bts object is authorized to obey frequency hopping laws.
Note :
[M]:
The "xxxWithCarrierFilling" configuration means that the BTS covering the cell must use a TX for BCCH filling purposes. The following apply:
The BSC sends the information to the BTS in the Abis CELL CONFIGURATION REQUEST message. If the BTS does not have a redundant TRX/DRX, one of the operating TRX/DRXs is assigned to that purpose and the partnered TDMA frame is unreachable (refer to the operationalState entry for the transceiver object in the Dictionary). When this TRX/DRX is malfunctioning, the BTS re-configures the other TRX/DRXs. Users are then warned by the system, by means of a notification.
The "noHoppingWithCarrierFilling" configuration can be used in all BTSs, regardless of the coupling mode. The following apply:
Hybrid coupling: All cell TX configurations provide BCCH filling. Cavity coupling: Only the TX that transmits the cell BCCH frequency is configured to provide BCCH filling.
The "hoppingWithCarrierFilling" configuration can only be used in BTSs that use cavity coupling. The following apply:
142
Hybrid coupling: The BTS refuses the configuration. Cavity coupling: All cell TX configurations provide self-frequency filling.
btsMSAccessClassBarringFunction Class 3
Description : Value range : Object : Default value : Type : Release : Enable or disable dynamic barring of access class at the bts level. [enabled / disabled] bts disabled DP V9
btsReserved3 Class 3
Description : Mean number of logical channels belonging to the large frequency reuse pattern and used at the same time for data communications. [-16 to +16] bts Automatic Cell Tiering (TF995-V12) 0 DP V12
Value range : Object : Feature : Default value : Type : Release :
btsReserved4 Class 3
Description : Value range : Object : Type : Release : Attribute reserved for future use. [-32768 to 32767] bts DP V12
btsSensitivity Class 3
Description : Value range : Object : Target power needed for BTS decoding. This parameter has an influence on the power control efficiency. [0 to 255] bts
143
Default value : Feature : Type : Release : Note :
0 GPRS (SV407 - V12) DP V12 The power control function used is the Open Loop Control.
btsSensitivityInnerZone Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Minimum power needed for BTS decoding in the inner zone of a dual-band cell. [0 to 255] bts GPRS (SV407 - V12) 0 DP V12
btsSiteManager
Description : Identifier of a btsSiteManager object defined with regard to a bsc object. All bts, channel, transceiver, and transceiverEquipment objects in a BSS are identified with regard to a btsSiteManager object that defines the covering radio site. In all MMI commands, a btsSiteManager object can be referred to by name (siteName). Value range : Object : Type : Checks : [0 to 2147483646] btsSiteManager Id

[C]: [C]:
[C]: The software object related to the parent bsc object is created. The referenced lapdLink object (lapdLinkOMLRef) is created for the parent bsc object and assigned to the Abis interface.
144
[C]:
If the application database of the related BSC is built, the referenced pcmCircuit objects (bscSitePcmList) are created for the parent bsc object and assigned to the Abis interface (pcmType = "pcmAbis"). The bscSitePcmList list contains at least two pairs if the btsSiteManager object redundantPcmPresence attribute is "true". If one of the pcmCircuit objects in the list describes a PCM link that is shared with another site in the BSS, the radioSiteMask of the two btsSiteManager objects are dissociated. If the application database of the related BSC is built, the parent bsc object is unlocked. If the application database of the related BSC is built, the parent bsc object is unlocked and the btsSiteManager object is locked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.
[C/M]:
[C]:
[C]: [D]:
[D]:
btsSiteManager
Description : Identifier or name of a btsSiteManager object. It defines the parent btsSiteManager object. It defines the parent btsSiteManager object. By definition, a radio site (btsSiteManager object) is related to a BSC, a radio cell (bts object) is related to a radio site, a TRX/DRX (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 a btsSiteManager object can be identified at BSC or site level, whichever is the most convenient to users. Value range : Object : [0 to 499] adjacentCellHandOver, adjacentCellReselection, bts, channel, frequencyHoppingSystem, handOverControl, po werControl, software, transceiver, transceiverEquipment, transceiverZone.
145
Type : Note :
Id The maximum number of sites supported by a BSC 3000 is 500. The system accepts values between 0 and 499 (inclusive).
btsSiteManager model
Description : To select messages issued by a given model of BTS. Do not fill in if this criterion is not to be selected. Value range : / s8000 inDoor / s8000 outDoor / s8000 inDoor CBCF / s8000 outDoor CBCF / e-CELL / s8002 outdoor CBCF O2 / s12000 inDoor / s12000 outDoor / BTS18000 inDoor / BTS18000 outDoor] Alarm and notification logs - Filter DP
Object : Type :
btsSiteManagerList Class 2
Description : Value range : Object : Type : Checks : List of btsSiteManager objects attached to a multiple site object [0 to 146] multiple site DP
[C/M]: [M]:
Each btsSiteManager object is unique in the list and created for the parent bsc object. The parent bsc object is unlocked and the referenced btsSiteManager objects are locked.
Note :
The order in which the btsSiteManager objects are entered in the list must match the BTS chaining order, beginning with the BTS closest to the BSC.
btsThresholdHopReconf Class 2
Description : Minimum number of frequencies working in a cell to allow frequency hopping reconfiguration. If this attribute defines the nominal number of cell frequencies, the reconfiguration process is deactivated. Refer to the btsHopReconfRestart entry in the Dictionary. Value range : Object : Default value : [1 to 64] bts 1
146
Type : Checks : Release :
DP
V8
[M]:
This number is less than or equal to the number of transceiver objects created for the bts object.
btsWithCavity Class 2
Description : Value range : Object : Default value : Feature : Type : Release : Whether the bts object instance uses a transceiver equipment with cavity. [true / false] bts false Mixed hybrid and cavity combiner BTSs (PR1179 - V12) DP V12
buildState
Description : Whether BSC application database building is in-progress. Commands on all objects related to the bsc concerned object are refused while the BDA is being built. When the bsc object is created, the value of this attribute is enforced to "notInProgress". It is unknown to the BSC and cannot be directly modified by users. It is changed to "inProgress" by the system after a user Build BDA command on the bsc object as long as database building is in-progress. It is then changed back to "notInProgress" when the operation is complete. Value range : Object : Type : [inProgress / notInProgress] bsc DI
147
C
callClearing Class 3
Description : Maximum distance between MS and BTS before a call is cleared. It is greater than msRangeMax. This distance defines the cell maximum coverage area. Value range : Object : Default value : Type : Checks : [2 to 135] km (non-extended mode), [2 to 120] km (extended mode). bts 35 in non-extended mode, 90 in extended mode DP
[C/M]:
callClearing > msRangeMax (attribute of the handOverControl object associated with the bts object). The maximum distance is 35 km if the extended cell attribute of the bts object is "false". The maximum distance is 120 km if the extended cell attribute of the bts object is "true".
[C/M]:
[C/M]:
7 km for urban 35 km for rural
callDropActivation class 3
Description : Object : Value range : Type : Feature : Default value : Checks : Activation of cell call drop data retrieval of cell call drops at OMC-R. bts [Disabled (0) / traffic drops (1) / signaling drops (2) / traffic + signaling drops (3)] DP Call drop analysis 0
[C/M]:
callDropActivation parameter cannot be set to a value different from 0 in more than 80 cells per BSC. Call drop analysis feature cannot be activated on more than 80 cells at a time
148
[C/M]:
Call drop analysis feature cannot be activated on the cell if interference matrix is still running on this cell. This semantic checks forbids activation of interference matrix and call drop analysis features at the same time on a cell.
Release : Note :
V15 This parameter is mandatory. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
callPathObservationArea Class 2
Description : List of up to thirty-one same-type objects observed. Enter each object reference according to the type (bts, transceiverEquipment, xtp). [list of objects belonging to the same class] callPathTrace DP
[C/M]: [M]:
All observed objects belong to the same class. The callPathTrace object is locked.
callPathTrace
Description : Identifier of a callPathTrace object defined with regard to the md object. This object describes the Call path tracing function of a BSS (follow-up of calls using one or more common resources in the BSS). A callPathTrace object is created in locked state. Unlock the object to start collecting trace data. Value range : Object : Type : Checks : [0 to 2147483646] callPathTrace Id
[C]: [C/M/D]: [C/M/D]:
The callPathTrace object is not created for the md object. The application database of the related BSC is not being built. If the application database of the related BSC is built, the BSS/OMC-R link is established and no audit is running in the BSC.
149
Release : V8
[D]:
The callPathTrace object is created.
callPathTraceType Class 2
Description : Type of information stored by the BSC. The information stored with respect to the type is detailed in NTP < 07 >. If the request cannot be fulfilled, the BSC attempts to store another type of information, using the following rule: radio >>> hand over >>> radio. Value range : Object : Type : Checks : [basic / hand over / radio] callPathTrace DP
[M]:
The callPathTrace object is locked.
callReestablishment Class 3
Description : Whether call re-establishment in a cell is allowed when the radio link is broken off for propagation reasons. The information is broadcast to the mobiles at regular intervals on the cell BCCH. On receipt of a CHANNEL REQUIRED message with cause "call re-establishment", the BSC attempts to allocate a TCH in one of the cells where call re-establishment is allowed. Then, if no TCH is available the BSC attempts to allocate a SDCCH. Value range : Object : Default value : Type : [allowed / not allowed] bts not allowed DP
150
callReestablishmentPriority Class 3
Description : Index in the allocPriorityTable that defines the processing priority of TCH allocation requests with cause "call reestablishment". This priority is used in primo-allocations or when an SDDCH cannot be allocated for overload reasons. Value range : Object : Default value : Type : [0 to 17] bts 17 DP
capacityAlarmThreshold
Description : Filling threshold of the message saving partition on the OMC-R agent disks, beyond which a notification is triggered. The size of the saving partitions is indicated in the system commissioning files. This attribute is significant when the object describes a current log; it has no meaning when the object describes a restored log. When the threshold is reached, the OMC-R agent initiates the following actions:
A notification is sent to the OMC-R manager. For a current alarm log, old messages are deleted to make room in the partition. If all saved messages are of todays date, further notifications are not saved and the operationalState of the log object is forced to "disabled". For a current observation or trace log, the operationalState of the log object is forced to "disabled" and its availabilityStatus is forced to "logFull".
Value range : Object : Type : Note :
[0 to 2147483646]. "2147483646" defines a 100% threshold (the partition is full). log - Display DP The attributes of the log objects are not managed by users.
151
capacityTimeRejection Class 3
Description : Minimum time between one intracell HO and the next capacity intracell HO. This attribute can only be modified if the handOverControl object instance is unlocked. Value range : Object : Default value : Type : Release : Note : Int [0 to 120] seconds handOverControl 0 DP V1 4 This parameter is only available for BSC 3000.
cause
Description : To select messages according to one or more causes associated with a fault number. Refer to Nortel GSM BSS and OMC Maintenance Manuals. This parameter is a component of the specific problems filter. Refer to this entry in the Dictionary. Value range : Object : Type : [0 to 19070980] Alarm and notification logs - Filter DP
cCCHGprsAtBtsLevel Class 3
Description : Value range : Object : Default value : Type : Release : Used to activate the CCCH management at BTS level. [disabled / enabled] bts disabled DP V14
cc
Description : The Communication application module Controller, which is the ATM switch implementing the ATM network used as the Control Node backplane. This board also provides ATM on OC-3 (Optical Carrier level 3) connectivity towards the Interface Node. [0 to 2147483646]
Value range :
152
Object : Type : Release :
cc DP V13
ccId
Description : Identifier of the cc object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000. [0 to 2147483646] cc DP V13
cellAllocation Class 2
Description : List of no more than 64 frequencies allotted to a cell in the network frequency band. By definition, all cells covered by a given radio site use the same frequency band defined by the type of the network (standardIndicator). All cells declared as neighbor cells of a serving cell use the same frequency band as the serving cell. Value range : [1 to 124] (GSM 900 network), [512 to 885] (GSM 1800 network), [512 to 810] (PCS 1900 network), [0 to 124 / 955 to 1023] (GSM-R network), [0 to 124 / 975 to 1023] (extended GSM network), [128 to 251] (GSM 850 network), [99 / 1023] / [0 / 55] (GSM-R network). The standardIndicator for GSM-R values is Rgsm. bts DP
[C/M]:
Each frequency occurs once in the list and complies with the type of the network (refer to the standardIndicator entry in the Dictionary). GSM 900 / GSM-R / Extended GSM networks: The number of frequencies in the list is limited to 64. GSM 1800/1900/850 network: The number of frequencies in the list depends on the gap between the lowest and the greatest defined frequencies.
[C/M] :
[C/M] :
153
Maximum gap between frequencies between 257 and 512 between 129 and 256 between 113 and 128 between 1 and 112
Number of frequencies [2 to 18] [2 to 22] [2 to 29] [2 to 64]
[C/M]: [C/M]:
The cell BCCH frequency (bCCHFrequency) is part of the list. For dualband networks, the number of frequencies must be inferior or equal to 64 by frequency band. The frequencies allotted to the radio time slots (channel objects) of the set of TDMA frames related to the cell are part of the list. An element of the list of cellAllocation parameter can take one of the following values: [1 to 124] (GSM 900 network), [512 to 885] (GSM 1800 network) [512 to 810] (GSM 1900), [0 to 124] or [955 to 1023] (GSM-R network), [0 to 124 or [975 to 1023] (E-GSM network) [128 to 251] (GSM 850 network).
[M]:
[C/M]:
cellBarQualify Class 3
Description : Cell selection priority used in the C2 algorithm in Phase II. The information is broadcast to the mobiles at regular intervals on the cell BCCH. Value range : Object : Default value : Type : Release : [true (low priority) / false (normal priority)] bts False DP V8
154
cellBarred Class 3
Description : Whether direct cell access are barred to mobiles. The information is broadcast to the mobiles at regular intervals on the cell BCCH. During a call, it is transmitted on a signaling link. If the attribute value is changed to "barred", all in-progress calls can continue but the BSC will direct further mobile calls to another cell. Value range : Object : Default value : Type : Remark : [barred / not barred] bts not barred DP Even when cell access are barred to MSs, the cell may be indirectly accessible if incoming handovers are allowed (incomingHandOver attribute of the associated handOverControl object).
cellDeletionCount Class 3
Description : Number of consecutive "Measurement Result" messages which, if not received from a given neighbor cell, will cause all previously stored information related to that cell to be deleted. From V12, this number corresponds to the number of missing measurement reports after which this neighbor cell is no more eligible. The measurements related to this neighbor cell are not deleted as far as less than 10 consecutive measurements are missing. Value range : Object : Default value : Type : Note : [0 to 31] bts 5 in rural environment, 2 in microcell environment DP Any entered value superior than 10 is taken into account as 10 value.
155
cellDtxDownLink Class 3
Description : Value range : Object : Default value : Type : Remark : Whether the use of discontinuous transmission in BTS-to-MS direction is allowed in a cell. [enabled / disabled] bts enabled DP The dtxMode attribute allows users to control the use of discontinuous transmission on the uplink. Refer to this entry in the Dictionary.
cellIdentity Class 3
Description : Value range : Object : Type : Checks : Cell Identity code (CI) that identifying in a location area, a neighbor cell of the current cell. [0 to 65535] adjacentCellHandOver DP
[C/M]:
A CGI is unique in the set including a serving cell and its neighbor cells.
Description : Value range : Object : Type : Checks : Cell Identity code (CI) identifying in a location area, a neighbor cell of the current cell. [0 to 65535] adjacentCellReselection DP
[C/M]:
Description : Cell Identity code (CI) identifying a serving cell in a location area. A CGI (Cell Global Identifier) is unique in a location area. It identifies a cell in the PLMN and includes four fields: cellIdentity (CI), locationAreaCode (LAC), mobileCountryCode (MCC), and mobileNetworkCode (MNC). Value range : [0 to 65535]
156
bts DP
[C/M]:
cellName
Description : Value range : Object : Type : Checks : Note : Reference name of a bts object on the coverage site. It is case sensitive. [30 characters max.] bts DP
[C/M]:
The name of a cell is unique to the covering radio site.
Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited. The valid symbols are: - letter characters: A, B, C..., Z, a, b, c..., z - digit symbols: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 - minus sign: - undescore: _ - space
cellPagingState
Description : Value range : Processing mode of the paging requests in the cell. [allowed / not allowed / not significant] This attribute is dynamically managed by the BSC.
allowed ..........
The operationalState of the transceiver object describing the TDMA frame no.0 carrying the BCCH is "working" and SYS INFO 1, 2, 3, 4 have been acknowledged by the BTS.
157
not allowed .......
The operationalState of the transceiver object describing the TDMA frame no.0 carrying the BCCH is "working" and SYS INFO 1, 2, 3, 4 have not been acknowledged by the BTS. If no message has been acknowledged by the BTS, the notification 1256 "Non response to SYS INFO 1, 2, 3, 4 or 2bis" is issued. The operationalState of the transceiver object describing the TDMA frame no.0 carrying the BCCH is not "working".
not significant ....
Object : Type :
bts DD
cellReselectHysteresis Class 3
Description : Hysteresis to re-select towards a cell:
when the MS is in GSM - IDLE mode and re-selects a cell with a different LA (Location Area) when the MS is in GMM stand by state and re-selects a cell with a different LA (Location Area) or a different RA (Routing Area) when the MS is in GMM ready state and re-selects a different cell
A mobile can select a cell in another location area provided the re-selection parameter value of that cell oversteps the re-selection parameter values of all the cells in the same location area as the current camping cell by at least cellReselectHysteresis dB. The information is broadcast on the cell BCCH. The re-selection criterion (C1) formula is: C1 = (A - Max (B,0)) where A and B are as follows: A = average level of the received signal - rxLevAccessMin B = msTxPwrMaxCCH - Maximum RF output power of the MS
158
The re-selection criterion (C2) formula is given with the cellReselectOffset entry. Value range : Object : Default value : Type : Note : [0 to 14, by steps of 2] dB bts 6 dB DP The greater the value of cellReselectHysteresis, the later a new cell in another location area is selected. This prevents from switching back and forth two location areas.
cellReselectOffset Class 3
Description : Encouragement to re-select a cell (C2 criterion) for phase 2 MS. The re-selection criterion (C2) formula is: C2 = C1 + cellReselectOffset - temporaryOffset x H (penaltyTime - T)
C1 is defined with the cellReselectHysteresis entry. T is a timer that is started when the cell is placed by the MS on the list of most suitable cells to receive the calls, and is stopped when the cell is no longer on the list. H(penaltyTime - T) equals 0 when penaltyTime < T and penaltyTime T.
In the case when penaltyTime = 640, re-selection criterion formula becomes: C2 = C1 - cellReselectOffset Value range : Object : Feature : Default value : Type : Release : Note : [0 to 126, by steps of 2] dB bts AR 264 4 DP V8 The value given to this attribute allows to more or less encourage the mobiles to re-select the cell.
159
cellReselInd Class 3
Description : Value range : Object : Default value : Type : Release : Whether cell re-selection criterion (C2) use is authorized. [true / false] bts True DP V8
cellThreshold Class 2
Description : Needed number of transceiver object instances that must be in enabled state so that the cell is working. The value of this attribute must be less than or equal to the number of TDMA frames created for this cell This attribute can be modified only if the bts object instance is locked. This attribute can be modified only if the bsc object instance is unlocked. Value range : Object : Default value : Type : [f1 to 16] bts 1 DP
cellType Class 3
Description : Value range : Object : Default value : Type : Type of the adjacent cell. [normalType / umbrellaType / microType] adjacentCellHandOver normalType DP
cellType Class 3
Description : Value range : Object : Default value : Type of the serving cell. [normalType / umbrellaType / microType] bts normalType
160
Type : Checks :
DP
[C/M]:
The adjacent cell umbrella Ref attribute is defined if the cell is a microcell (cellType) and directed retry handovers are processed in BSC mode (directedRetryModeUsed).
cemId
Description : Identifier of the cem object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000. [0 to 2147483646] cem DP V13
chain
Description : Identifier of a BSC processing chain. It identifies the chain whose software markers are displayed. Value range : Object : Type : [A / B] software-bsc - Display markers DD
chain
Description : To select messages originating from a BSC processing chain. Do not fill in if this criterion is not to be selected. Value range : Object : Type : [chainA / chainB] Alarm and notification logs - Filter DP
161
channel
Description : Identifier of a channel object (radio time slot). In all MMI commands, a channel object can be referred to by the sequence "siteName.cellName.transceiver.channel", where siteName and cellName respectively identify the covering site and cell by name. Value range : Object : Type : Checks : [0 to 7] channel Id
[C]: [C/M]:
The number of channel objects dependent on a transceiver object is limited to eight. If the channel object does not obey frequency hopping laws, the absoluteRFChannelNo is defined unless it carries the parent cell BCCH, and fhsRef and maio are undefined. If the channel object obeys frequency hopping laws, the absoluteRFChannelNo is undefined, and fhsRef and maio are defined. If the application database of the related BSC is built, the parent bsc object is unlocked and the parent bts object is locked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.
[C/M]:
[C/D]:
[D]:
channel state
Description : Value range : Type: [BCCH / RACH / PCH AGCH / SDCCH/4 / SDCCH/8 / TCH (full rate) / CCH], [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] The channel is allocated, not blocked, and free. Type and resource state of the logical channels multiplexed on the radio time slot.
Resource state:
available ........
162

Object : Type : Notes : DD
busy ............ disabled ......... working, blocked .. disabled, blocked..
The channel is allocated, not blocked, and busy. The channel is not configured. The channel is allocated and blocked. The channel is not allocated and blocked.
channel - Display channel state
The types of logical channels that can be multiplexed on a radio time slot depend on its channelType. Refer to this entry in the Dictionary. The resource state of SDCCH no.2 is "disabled" if a CBCH is defined. A radio channel is blocked or released by means of a user Modify channel state command. A radio channel is allocated when the TDMA frame is configured (in the Abis way) and its radio time slots are mapped onto an Abis interface PCM link.
channelReleaseOnAbisFailure
Description : Channel Release on Abis Failure feature is enabled or disabled. The Channel release policy feature is allowed on the BTS S8000 CBCF and BTS S12000. The feature is allowed for BTS model which contains the string:

Value range : Object : Feature : Default value : bts
8000 12000
except for BTS model: BSS_btsModelS8000inDoor (CBCF) BSS_btsModelS8000outDoor (CBCF)
[disabled / enabled]
Channel release policy on BTS after Abis failure disabled
163
Type : Note :
DP
The recommended value is disabled. This parameter is mandatory. [C/M]: A spare of the TRX container (IEI TDMATranspAttr2 = 0x52) is used on bts object to activate the feature.
Spare 5 attribute ofTDMACONFIGCONTAINERofTDMA CONFIG message 8 IEI = TD_S PARE 5_IEI High part of spare 5 Low part of spare5 0 0 0 7 1 0 0 6 0 0 0 5 0 0 0 4 1 0 0 3 1 0 0/1 1 0 0 n/a
Default value = 0x0000 Bit 2 (from1 to 8) of the lowpart of spare 5 parameter can take the values: 0: Channel release policy after the ABIS failure is not activated 1: Channel release policy after the ABIS failure is activated.
channelType Class 2
Description : Value range : Type of logical channel supported by a radio TS. [tCHFull / sDCCH / mainBCCH / mainBCCHCombined / bcchsdcch4CBCH / sdcch8CBCH / cCH (V12) / pDTCH (V12)]. An SDCCH is only allocated to a mobile during call setup. Once the call is established, the SDCCH is released and a TCH supports the call, serving traffic and signaling needs. A CBCH (Cell Broadcast CHannel) configuration enables use of the Short Message Service -Cell Broadcast (SMS-CB) in a cell when a radio time slot of a TDMA frame related to the cell supports that type of channel. The CBCH can be combined with an SDCCH/8 or a BCCH+SDCCH/4. It takes the place of SDCCH no.2 in all cases.
164
If the time slot carries a cell BCCH, its type sets the cell BCCH configuration (combined or not combined). Object : Feature : Default value : Type : Checks : channel Extended CCCH (TF184 - V12) GPRS (SV407 - V12) None DP
[C/M]:
If the type is "mainBCCH", "mainBCCHCombin ed", or "bcchSdcch4CBCH", the channel object identifier is [0] and the object is not authorized to hop. The type "cCH" can only be used if TS 0 carries a BCCH logical channel ("main BCCH", "main BCCH combined"). The only allowed association of (BCCH + CCCH) timeslots are (0), (0, 2), (0, 2, 4), (0, 2, 4, 6). If the type is "sdcch8CBCH", the channel object identifier is in the range [0 to 3] if the covering cell works in normal mode, and it equals 0 or 2 if the cell works in extended mode (extended cell attribute of the parent bts object). If the type is "sdcch8CBCH", the noOfBlksForA ccessGrant attribute of the parent bts object has a value greater than 0. If the type is "bcchSdcch4CBCH" or "sdcch8CBCH", use of the SMS-CB service is authorized in the parent bts object (smsCB = "used"). Concentric cell: If the parent transceiver object belongs to the cell inner zone, the only authorized types are "bcchSdcch4CBCH" and "sdcch8CBCH". The "pDTCH" channelType is only allowed from V12 BSCs for GPRS.
[C/M]:
[C/M]: [C/M]:
[C/M]:
[C/M]:
[C/M]:
[M]:
A radio channel is identified by an 8-bit code built up by the OMC-R from the channel type and the number of the time slot that supports it: 8 C5 7 C4 6 C3 5 C2 4 C1 3 < TN > 2 1
165

00001 0001T 001TT 01TTT 10000 10001 10010
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:
ACCH with a TCH/FR (SACCH/FACCH) ACCH with a TCH/HR ACCH in an SDCCH/4 configuration ACCH in an SDCCH/8 configuration BCCH RACH (Uplink CCCH) PCH + AGCH (Downlink CCCH) The T bits indicate the subchannel number [0 to 7]:
00100 00101 00110 00111
There are four subchannels [0 to 3] in an SDCCH/4 configuration:
SDCCH/4 + ACCH subchannel no.0 SDCCH/4 + ACCH subchannel no.1 (combined CBCH) SDCCH/4 + ACCH subchannel no.2 SDCCH/4 + ACCH subchannel no.3
01000 01001 01010 01011 01100 01101 01110 01111
There are eight subchannels [0 to 7] in an SDCCH/8 configuration:
SDCCH/8 + ACCH subchannel no.0 SDCCH/8 + ACCH subchannel no.1 (CBCH) SDCCH/8 + ACCH subchannel no.2 SDCCH/8 + ACCH subchannel no.3 SDCCH/8 + ACCH subchannel no.4 SDCCH/8 + ACCH subchannel no.5 SDCCH/8 + ACCH subchannel no.6 SDCCH/8 + ACCH subchannel no.7 The logical channels that can be multiplexed on a radio time slot depend on its channelType. They are described in the following table.
channelType tCHFull sDCCH
Bits C5-C1 BM + ACCH (SACCH/FACCH) SDCCH/8 + ACCH subchannels [0 to 7] (SACCH/FACCH)
166
channelType mainBCCH
Bits C5-C1 BCCH RACH (Uplink) PCH + AGCH (Downlink) BCCH RACH (Uplink) PCH + AGCH (Downlink) SDCCH/4 + ACCH subchannels [0 to 3] BCCH CBCH (= SDCCH No2) RACH (Uplink) PCH + AGCH (Downlink) SDCCH/4 + ACCH subchannels [0 to 3] CBCH (= SDCCH No2) SDCCH/4 + ACCH subchannels [0 to 3] (SACCH/FACCH) BCCH RACH (Uplink) PCH + AGCH (Downlink)
mainBCCHCombined
bcchSdcch4CBCH
sdcch8CBCH
cCH
Remark :
Configuration of logical channels and broadcast of short messages are managed by two independent OMC-R functions. When a short message broadcast is started in a cell, the presence of a channel object with a CBCH dependent on the concerned bts object is checked. On the contrary, the SMS-CB function is not aware of changes made to that attribute. Consequently, withdrawing a CBCH from a cell configuration will implicitly stop any short message broadcast in the cell without the SMS-CB function knowing.
Note :
The following counters have been multiplexed on TSs 0, 2, 4, and 6 for the Extended CCCH feature: C1026, C1027, C1028, C1029, C1030, C1031, C1033, C1604, C1605. No recommended value is specified since this parameter depends on the strategy of the operator.
Comments :
chanState
Description : Value range : Object : Type : Whether or not, the radio channel is blocked. [locked / unlocked] channel - Set channel state DP
167
Checks :
[A]: [A]:
A BCCH or a CBCH, whether combined or not, cannot be blocked. The parent btsSiteManager and bts objects are unlocked.
Notes :
When a CBCH is defined for a cell, it always uses SDCCH no.2. Run a Display channel state command to check that the channel has switched to the specified state. Refer to the channel state entry in the Dictionary.
chosenChannelAsscomp Class 1
Description : Value range : Object : Default value : Type : Release : Note : Whether the "Chosen channel" element is used in the ASSIGN COMPLETE messages (Phase II compliance). [true / false] signallingPoint False DP V8 If the MSC parameter MULTIPLE_VOCODER_SUPPORT (Table OFCVAR) is set to ON (see 411-2231-455 for more details), then the BSC parameter chosenChannelAsscomp needs to be set to TRUE.
chosenChannelCompL3Info Class 1
Description : Whether the "Chosen channel" element is used in the COMPLETE LAYER 3 INFORMATION messages (Phase II compliance). [true / false] signallingPoint False DP V8 If the MSC parameter MULTIPLE_VOCODER_SUPPORT (Table OFCVAR) is set to ON (see 411-2231-455 for more details), then the BSC parameter chosenChannelCompL3Info needs to be set to TRUE.
Value range : Object : Default value : Type : Release : Note :
168
chosenChannelHoPerf Class 1
Description : Whether the "Chosen channel" element is used in the HANDOVER PERFORMED messages (Phase II compliance). [true / false] signallingPoint False DP V8 If the MSC parameter MULTIPLE_VOCODER_SUPPORT (Table OFCVAR) is set to ON (see 411-2231-455 for more details), then the BSC parameter chosenChannelCompL3Info needs to be set to TRUE.
chosenChannelHoReq Class 1
Description : Whether the "Chosen channel" element is used in the HANDOVER REQUEST ACKNOWLEDGE messages (Phase II compliance). [true / false] signallingPoint False DP V8 If the MSC parameter MULTIPLE_VOCODER_SUPPORT (Table OFCVAR) is set to ON (see 411-2231-455 for more details), then the BSC parameter chosenChannelCompL3Info needs to be set to TRUE.
cic Class 0
Description : Circuit Identity Code = numbers of the PCM link and time slot used by a terrestrial circuit on the A interface, defined with regard to the MSC (cic = 32xmscPcmNumber + mscPcmTsNumber). The cic is coded into 16 bits, as follows: xxxxxxxxxxxnnnnn = (32xmscPcmNumber) + mscPcmTsNum ber
169
Bits x identify the PCM link involved in the BSC/MSC link with regard to the MSC (mscPcmNumber), bits n identify the time slot used on that PCM link with regard to the MSC (mscPcmTsNumber). Value range : Object : Type : Checks : [0 to 65535] xtp DP
[C]: [C]:
A cic is unique to the parent bsc object. The PCM TS used by the terrestrial circuit on the A interface is identical on MSC end (mscPcmTsNumber component) and BSC end (timeSlotNumber), and is not allotted to another xtp or signallingLink object dependent on the parent bsc object. If PCM link no.3 is used on the A interface (pcmCircuitId), the TS number is in the range [1 to 27] if the PCM link is an E1 link and in the range [1 to 20] if the PCM link is a T1 link. Since the last four TSs on that link are not mapped on the Ater interface, they cannot be used. Refer to the transcoderMatrix entry in the Dictionary. This attribute cannot be modified.
[C]:
Restrictions :
[M]:
cId Class 3
Description: Value range: Object: Default value: Type: Release: cell identity of the UMTS neighbouring cell for HO 0...65535 adjacentCellUTRAN 0 DP V17
170
Checks:
[C]
The set of attributes cId, rNCId, mobileCountryCodeUTRAN and mobileNetworkCodeUTRAN must be unique among all the instances of the objects adjacentCellUTRAN attached to the same bts.
Note:
This parameter is only available for BSC 3000.
circuitGroupBlock Class 1
Description : Whether the CIRCUIT GROUP BLOCK and CIRCUIT GROUP UNBLOCK messages are used (Phase II compliance). If these messages are unused, the BLOCK and UNBLOCK messages are used. Value range : Object : Feature : Default value : Type : Release : [false / true] signallingPoint Unequipped circuit and circuit group block (UF1169.1 V12) False DP V8
circularFileId
Description : Identifier of a BSC circular file. BSC circular files are automatically created by the system: the FAULT files are created with the BSC, the PERF (observations) and TRACE (trace data) files are created when the BSC application database is built. Value range : Object : Type : Checks : [majorFault / minorFault / observation (permanent and temporary) / instrumentPanel] bscMdInterface - Circular file Id
[A]:
The circular file is created.
171
circularFileState
Description : State of a circular file. When a circular file is closed, the spontaneous messages stored are not forwarded to the OMC-R agent. This attribute is set by the system following a user Close circular file or Open circular file command. When a circular file is closed, the messages are stored until the file is reopened. Some messages may be lost if the capacity of the file is reached. Value range : Object : Type : [closed / opened] bscMdInterface - Display circular file state DP
clear time
Description : To select alarms cleared at that time. Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in if this criterion is not to be selected. Value range : Object : Type : [<date>,<time>] Cleared alarm log - Filter DP
cleared by
Description : To select alarms ceased by a given user. Enter the users name as defined in the users profile. Do not fill in if this criterion is not to be selected. Object : Type : Cleared alarm log - Filter DP
clearing cause
Description : To select alarms according to the cause of ceasing. Do not fill in if this criterion is not to be selected. Value range : [user command / object enabled / object deleted / clear event received / automatic purge / cleared on low threshold crossing / circular file saturation]
172
Object : Type :
Cleared alarm log - Filter DP
cn
Description : The Control Node, which provides the GSM protocol processing (CallProcessing, SS7 and LAPD), as well as BSS OA&M. A logical point of view and a sub-track (hardware) point of view are managed. The SIM modules are also managed. [0 to 0] controlNode DP
Value range : Object : Type :
control Node Id
Description : Identifier of a controlNode object class. This identifier is allocated by the MD-R at object creation. The only value allocated by the MD-R is 0. This attribute cannot be modified. This attribute is relevant for BSC 3000. [0 to 0] controlNode DP V13
coderPoolConfiguration Class 2
Description : Value range : This attribute indicates enumerated speech coding algorithms supported by the TCU. List of [coderAlgo, minimumCall, powerULI, powerDLI], with: coderAlgo (BSC version: from V16): fullRatecoder / enhancedFullRateCoder / ctmEnhancedFullRateCoder / amrFullHalfRateCoder minimumCall: 1 to 65535 until V16 / 0 to 65535 for V17 and higher powerULI: -15 to +15 powerDLI: -15 to +15 transcoder DP V13
173
coderPoolList
Description : Current partitioning of the coder pool. This attribute is dynamically managed by the BSS. It is set to NULL at object creation. Value changes are not notified to the Manager. This attribute is relevant for TCU 3000. for a V15 BSC, list of [coderAlgo, archipelagoes, maximumCall, currentCall] with : coderAlgo: fullRatecoder / enhancedFullRateCoder / phase1DataCoder / amrFullHalfRateCoder archipelagoes: 0 to 65535 maximumCall: 0 to 65535 CurrentCall: 0 to 65535 for a V16 BSC, list of [coderAlgo, archipelagoes, emptyArchipelago, maximumCall, currentCall, minimumCallsRespected] with: coderAlgo: fullRatecoder / enhancedFullRateCoder / ctmEnhancedFullRateCode / amrFullHalfRateCoder archipelagoes: 0 to 65535 emptyArchipelago: 0 to 65535 maximumCall: 0 to 65535 currentCall: 0 to 65535 minimumCallsRespected: yes / no hardware transcoder 3G DD V13
Value range :
codingScheme Class 2
Description : Value range : Object : Feature : Default value : Type : Release : Note : Channel coding scheme (CS) used for data in GPRS mode (UL and DL). [cs1, cs2] transceiver GPRS (SV407 - V12) cs1 DP V12 cs1 is used for control blocks. Depending on the codingScheme parameter, cs1 or cs2 is used for data blocks in UL and DL.
174
command classes
Description : List of no more than twenty-five authorized command classes that define a users command domain. MMI commands grant access to OMC-R functions. Each class defines a subset of commands (one of them provides access to all MMI commands). The comprehensive list of MMI commands, together with their class(es), can be displayed using the Display command classes command. Value range : Object : Type : [0 to 2147483646] user profile DP
command line
Description : Command associated with the job. Follow the Line mode syntax. If the job is meant to run a simple command, enter the sequence describing the command and its parameters. If the job is meant to run a command file, enter the following: Run-commandFile: object=(commandFile=/<directory>/<fil ename>); The command file must be created in the specified directory. The Line mode syntax is detailed in NTP < 130 >. Value range : Object : Type : [case sensitive] job DP
175
command number
Description : Serial number of the command to abort. It is assigned by the system and is registered in session logs. Every MMI command launched by the user is identified by a serial number assigned by the system. Open the user session log consultation window and search for that number. Value range : Object : Type : [1 to infinity] commandFile - Abort DP
commandFile
Description : Identifier (name) of a command file in the saving directory. Enter the file name only. If the file exists in the selected directory, the user can either overwrite its contents with the commands newly recorded or append the new commands to the existing file (see NTP < 130 >). Value range : Object : Type : [case sensitive, 14 characters max.] commandFile - Create file 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 saved in the same directory as the source file. Value range : Object : Type : [case sensitive, 14 characters max.] Command file editing - Save Id
comment
Description : Value range : Text comment. [256 characters max.]
176
report template DP V11
comment
Description : Value range : Object : Type : Additional information coming with the short message. It is not broadcast. [60 characters max.] short message DP
comments
Description : Object : Type : Additional information (such as creation date). software - Display markers DD
compressedModeUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Note: V17 This parameter is only available for BSC 3000. Flag to indicate whether compressed mode UTRAN is supported 0: disabled / 1: enabled bts 0 DP
computeSyntheticCounters
Description : Whether synthetic counters are included in the observation report. This parameter is significant only for permanent bsc and instrument panel observation report display requests. Value range : Object : Type : [enabled / disabled] Display xxx report DP
177
concentAlgoExtMsRange Class 3
Description : MS to BTS distance below which a handover is requested from the large zone to the small zone if the level criteria is verified. [1 to 34] km (non-extended mode), [1 to 120] km (extended mode). Object : Default value : Condition : Type : Checks : handOverControl 1 km To define if the associated bts object describes a concentric, dualband or dualcoupling cell DP concentAlgoExtMsRange concentAlgoIntMsRange The maximum distance is 34 km if the extended cell attribute of the associated bts object is "false". The maximum distance is 120 km if the extended cell attribute of the bts object is "true".
Value range :
[C/M]: [C/M]:
[C/M]:
Release :
V9
concentAlgoExtRxLev Class 3
Description : Value range : Object : Default value : Condition : Type : Checks : Release : The level of the MS signal strength from below which a handover is requested from the large zone to the small zone. [less than -110, -110 to -109, ..., -49 to -48, more than -48] dB handOverControl - 95 to - 94 To define if the associated bts object describes a concentric, dualband or dualcoupling cell DP
V9
[C/M]:
concentAlgoExtRxLev > concentAlgoIntRxLev
178
concentAlgoIntMsRange Class 3
Description : MS to BTS distance from which a handover from the small zone to the large zone will be requested. The following inequality, that is not checked by the system, must be true (refer to these entries in the Dictionary). concentAlgoIntMsRange msRangeMax Value range : [1 to 34] km (non-extended mode) [1 to 120] km (extended mode) Object : Default value : Condition : Type : Checks : handOverControl 34 km To define if the associated bts object describes a concentric, dualband or dualcoupling cell. DP concentAlgoIntMsRange concentAlgoExtM sRange The maximum distance is 34 km if the extended cell attribute of the associated bts object is "false". The maximum distance is 120 km if the extended cell attribute of the bts object is "true".
[C/M]: [C/M]:
[C/M]:
Release :
V9
concentAlgoIntRxLev Class 3
Description : Value range : Object : Default value : Condition : Type : Checks : Release : Level of the MS signal strength below which a handover is requested from the small zone to the large zone. [less than -110, -110 to -109, ..., -49 to -48, more than -48] dB handOverControl less than -110 To define if the associated bts object describes a concentric, dualband or dualcoupling cell. DP
V9
[C/M]:
concentAlgoIntRxLev < concentAlgoExtRxLev
179
concentric cell Class 2

Description : Whether the cell is monozone, concentric, dualband or dualcoupling: A concentric, dualband, or dualcoupling cell describes a combination of two transmission zones, the outer (or large) zone and the inner (or small) zone. The inner zone is entirely included in the outer zone. A dualband cell is a particular type of concentric cell for which GSM 900 and GSM1800 or GSM850 and GSM1900 TRXs/DRXs coexist and share the same BCCH. A dualcoupling cell is a particular type of concentric cell for which the TRXs/DRXs are combined with two types of combiners. For concentric configurations (concentric, dualband or dualcoupling), a TDMA frame belongs to one zone or the other, but never to both, and the frequencies used in each zone are separated. Value range : [monozone / concentric / dualband / dualcoupling]
monozone ....... concentric....... dualband.........
normal cell two concentric transmission zones two concentric transmissions zones with GSM 900 and GSM 1800 TRXs/DRXs for the one or GSM 850 GSM 1900 TRXs/DRXs for the other two concentric transmission zones with TRXs/DRXs combined with a one type of combiner for the one and with another type of combiner for the other
dualcoupling..
Object : Feature : Default value : Type :
bts Dualband cell management (TF875 - V12) dualband DP
180
Note :
Dualband cells are only available for S8000 DRX transceiver architecture. Dualcoupling cells are only available for BTSs equipped with non mixed DCU4 or DRX transceiver architecture.
Release :
V9
condition
Description : Condition for calling the counting mechanism when a counter is involved. The following fields can be combined in the logical expression:
Parameter administrativeState availabilityStatus bsc equipment name bsc model cause btsSiteManager model bts equipment name equipment processor number faultNumber operationalState perceived severity postMortem usageState
Notification type state change state change alarm alarm alarm alarm alarm alarm alarm state change alarm alarm state change
Operators = = = = <=> = = <=> <=> = = = =
181
The "postMortem" field can take two values, either "before BSC restart" or "after bsc restart". They have the following meaning:
before BSC restart means that the notification issued by the BSC was received by the OMC-R agent without the BSC having restarted (nominal conditions). after BSC restart means that the notification was issued by the BSC and the BSC was restarted before the OMC-R agent received the notification. These notifications do not trigger alarms.
The following logical operators can be used in the logical expression:

Value range : Object : Condition : Type :
& stands for the logical AND. | stands for the logical OR. ! stands for the logical NOT.
[logical expression] alarm criteria To define if a Counter is associated with the criterion. DP
configRef Class 3
Description : Value range : Object : Type : Checks : Note : Reference name of a DLU (Data Loading Unit) configuration file. Check BSS upgrade file. [1 to VVV] btsSiteManager DP
[C/M]:
The attribute value must be set according to a static configuration file.
If the attribute is nonzero, the user must check that the DLU configuration file exists on the concerned BSC disk, since no check is performed by the OMC-R. The configRef is an ASCII-coded integer in base 32 that allows to code the version of the DLU configuration file as seven characters (xxaYYYz). The btsDescription parameter gives the transcription of the configRef parameter.
182
configRefList
Description : This attribute identifies the list of available configRef for a btsSiteManager delivery. For another object class instance, this attribute is empty. This attribute is allocated by the MD-R at object creation. This attribute cannot be modified by the Manager. [0 to 150] executableSoftware DP V13
configurationType
Description : Type of configuration the alarm criterion belongs to: The manufacturer configuration is known as the reference configuration. The operator configurations are known as the daytime configuration, the nighttime configuration, and the specific (or particular) configuration. Refer to the alarm criteria entry in the Dictionary. Value range : Object : Type : Checks : [manufacturer / operator] alarm criteria DP
[M]:
This attribute cannot be modified.
counter list
Description : Value range : Type of the counter list displayed. [default / all]

Object : Type : Release : DP
"default": "all":
the default counter list the whole counter list
report template
V12
counter list filename

Description : Object : Full pathname of the counter list file. bscCounterList
183
Type : Release :
DP V11
counterId
Description : Value range : Object : Type : Q3 name of a permanent BSS observation counter. See NTP < 07 >. [50 characters max., case sensitive] mdWarning - detection function = "outOfRangeCounter" DP
counters
Description : Object : Type : Release : List of the Q3 names of the counters eligible for observation, which are in the counter list filename. bscCounterList DP V11
counters
Description : Object : Value range : Type : Release : List of counters (Q3 names) chosen for observation. report template [list of Q3 counter names] DP V11
cpueNumber Class 0 or Class 1 (see note)

Description : Gives the number of the cellgroup to which the object will be mapped. Allows to by-pass the BSC algorithm which distributes the sites into Cell Groups. Depends on BSC type and release:
Value range :

3G before V15.1: [0 to 95 or empty] (if not significant) 3G from V15.1: [0 to 53 or empty] (if not significant)
btsSiteManager CPU/BIFP load sharing (AR874 - V12) 0 DP
184
Checks :
[C]: [C]:
The btsSiteManager object is limited according to the cpueNumber attribute value. The transceiverEquipment object instance number is limited according to the cpueNumber attribute value.
Notes :
Depending on the BSC type, cpueNumber class is: for a BSC 3000, to modify this parameter the bdaState must be "not built" This parameter only applies to type 3 to type 5 BSCs.
Release :
V12
cpueOccurrence
Description : Gives the number of the cell-group to which the site has been mapped at site creation. This mapping is not modifiable, except by deleting the site. Depends on system release:
Value range :

Object : Type : Default value: DD
before V15.1: [0 to 95] from V15.1: [0 to 53]
btsSiteManager
None
cRC Class 0
Description : Whether the CRC (Cyclic Redundancy Check) test on PCM links is used by the CTMx board controlling the PCM link, whether it is a pcmCircuit object dependent on a bsc object (Abis or Ater interface) for a BSC 3000 or dependent on a transcoder object (A interface) for a TCU 3000. [used / not used] pcmCircuit not used DP
creator
Description : Value range : Report template creator name. [30 characters max.]
185
criteriaEventType
Description : Type of the notifications handled by the alarm criterion. Selecting "alarmNotification" includes all Q3 alarm notifications such as communicationAlarm, equipmentA larm, environmentalAlarm, processingError-Alarm, and qualityOfServiceAlarm. Selecting "stateChangeNotification" includes all Q3 state change notifications. Value range : Object : Type : [alarmNotification / stateChangeNotification] alarm criteria DP
cSS7LocalSubSystemNumber Class 0
Description : Value range : Object : Type : Notes : SS7 local subsystem number for the BSSMAP application. [2 to 254] signallingPoint (BSC 3000 V14) or signallingLinkSet (BSC 3000 from V15) DP
The recommended value is 254 (0x00FE). This parameter is only available for BSC 3000.
Release :
V15
cSS7RemoteSubSystemNumber Class 0
Description : Value range : Object : Type : Release : Note : Note : SS7 remote subsystem number for the BSSMAP application. [2 to 254] signallingPoint (bsc 3000 V14) or signallingLinkSet (bsc 3000 from V15) DP V15 The recommended value is 254 (0x00FE). This parameter is only available for BSC 3000.
186
CTU cable
Description : The CTU (cable transition unit) provides the physical interface to the customers spans in the BSC 3000 and the TCU 3000. [true / false] True value: No break in the copper connection from the CTU to the IEM module of the LSA. False value: The cable is improperly installed from the CTU to the IEM module of the LSA or some break in the copper connection from the CTU and the IEM module of the LSA. Object : Feature : Type : Release : iem (up to V15), lsaRc (from V16) AR 1209 - V13.1 DD V13
Value range :
current log size

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

Description : Current synchronized mode gives the current synchronization mode of the BTS according to the synchronization mode received in the set external contact message (if received) but regardless of the synchronization signals available. This parameter is used in response of the "Display Data Information" (normal) action. Value range : [normal Abis synchronization / slave BTS correctly synchronized on master signal 1/ Abis synchronization due to master synchronization not available / slave BTS synchronized on master SY but master GSM time has been lost / Abis synchronization due to loss of master SY / hold over mode / Abis synchronization due to GPS synchronization unavailable or lack of accuracy / hold over mode due to a loss of GPS synchronization / hold over mode due to a GPS synchronization lack of accuracy / Network GPS Synchronized]
187
Object : Feature :
bts BTS synchronization
currentChannelHorqd Class 1
Description : Whether the "Current channel" element is used or not in the HANDOVER REQUIRED messages (Phase II compliance). [false / true] signallingPoint true DP V12
cypherModeReject Class 1
Description : Value range : Object : Default value : Type : Release : Note : Whether the CYPHER MODE REJECT messages are used (Phase II compliance). [true / false] signallingPoint False DP V8 This parameter is only available for BSC 3000.
D
dARPPh1Priority class 2
Description : Object : Value range : Type : Feature : Default value : Release : Note : Specifies the priority of SAIC (Single Antenna Interference Cancellation) mobiles on the TDMA. transceiver [high priority, low priority] DP Network Synchronization high priority V15 This parameter is mandatory. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
188
data non transparent mode Class 3

Description : Set of transmission rates used for data non transparent mode transmission on the Radio interface (MS BTS) and Abis interface (BTS BSC). [9.6 / 14.4] (kbit/s) bts 9.6 DP
[C/M] :
The only allowed configurations are the following:

Release : V11
"9.6" "9.6" and "14.4"
data non transparent mode Class 3

Description : Set of transmission rates used for data non transparent mode transmission on the Radio interface (MS BTS) and Abis interface (BTS BSC). [9.6 / 14.4] (kbit/s) signallingPoint 9.6 kbit/s DP
[C/M] :

Release : V9
"9.6" "9.6" and "14.4"
data transparent mode Class 3

Description : Set of transmission rates used for data transparent mode transmission on the Radio interface (MS BTS) and Abis interface (BTS BSC). ["1.2/0.075" / 0.6 / 1.2 / 2.4 / 4.8 / 9.6 / 14.4] (kbit/s) bts DP
[C/M] :
189

Release : V11
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)
data transparent mode Class 3

Description : Set of transmission rates used for data transparent mode transmission on the Radio interface (MS BTS) and Abis interface (BTS BSC). ["1.2/0.075" / 0.6 / 1.2 / 2.4 / 4.8 / 9.6 / 14.4] (kbit/s) signallingPoint
DP
[C/M] :

Release : V9
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
Description : Value range : Object : Default value : Type : Release : Whether data 14.4 kbit/s transmission rate is allowed at bts level on the non hopping TSs. [disabled / enabled] bts disabled DP V12
date
Description : Date on which the observation report was created. Date format entry forms are detailed in NTP < 130 >. Value range : Object : Type : [<date>] Display daily report DP
190
date
Description : Date on which data to archive were recorded. Date format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Note : [<date>] md - Archive DP Archiving fault, observation, or trace data is not possible for the current day.
date
Description : Date on which data to restore were recorded. Date format entry forms are detailed in NTP < 130 >. Value range : Object : Type : [<date>] md - Restore DP
date
Description : Date on which data to archive were recorded. Date format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Note : [<date>] omc - Archive/Restore DP Archiving fault, observation, or trace data is not possible for the current day.
date
Description : Date on which data to restore were recorded. Date format entry forms are detailed in NTP < 130 >. Value range : Object : Type : [<date>] omc - Restore DP
191
day intervention
Description : Value range : Object : Type : Type of action associated with an alarm criterion in the daytime configuration. [noAlarm / critical / major / minor] alarm criteria DP
day to be purged
Description : Date on which the data to purge were recorded. Date format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Release : [<date>] omc - Data purge DP V10
degradedCause
Description : Value range : Object : Type : Release : Gives the reasons of the degraded or enabled state. [Not significant, GPRS] bts DD V15
degradedCause
Description : Value range : Gives the reasons of the degraded or enabled state. [Lack of Abis resources / Site not supporting Edge / Site insufficient number of DS0 / TRX insufficient Edge capability / Site not supporting CS3 CS4 / TRX insufficient Packet capability / Site not supporting neither CS3 CS4, neither Edge / Site not supporting CS3 CS4, with insufficient number of DS0 / TRX insufficient Edge capability in a site not supporting CS3 CS4 / TRX insufficient Edge and packet capability / Not significant] transceiver GPRS DD V15
192
delayBetweenRetrans Class 2
Description : Number of occurrences of a paging sub-group that separates two transmissions of the same paging message. The following inequality, that is not checked by the system, must be true (refer to these entries in the Dictionary): retransDuration (delayBetweenRetrans + 1) x nbOfRepeat Value range : Object : Default value : Type : Release : [0 to 22] bts 0 DP V8
delivery
Description : Name of executable software package to download to the BSC disk. The name of the delivery identifies the type and version of the BSS software for which it is designed as follows:
BSC 3000 software format = "BSxabcdefghi"
Field BSx ab cd ef gh i
Meaning Name Version Subversion Number Edition Patch Level Revision Factor
Value x = [1 .. 4] [09 . .32] [01 . .99] [01 . .99] [01 . .99] C
BSC 3000 software format = "B3Gabcdefghi" TCU 3000 software format = "TC3abcdefgh"
Field ab
Meaning Version
Value [13 . .32]
193
Field cd ef gh i
Meaning Subversion Number Edition Patch Level Debug Delivery
Value [01 . .99] [01 . .99] [01 . .99] D
TCB/BTS/TRX software format = "XXXabcdef"
BTS xxx BCF/ BC1/BC2/SBC/ CBC/PIC/IBC/ ICM [00 .. 32] A .. H [01 . .08] [01 .. 32]
TRX TRX/TR1/DRX/ CDR/EDG/ERM
ab c d ef
[00 .. 32] A .. H [01 . .08] [01 .. 32]
XXXabcdefghi (g, h and i are optional) software - Download DP
[A]:
Corresponding executableSoftware object must exist. That means that the software delivery must be previously installed from CD-ROM or gigatape on MD disk. The software being downloaded must be present on MD disk and accessible. There should be no downloading in progress of the same type of software. The software must match the architecture of BSC to which it is being downloaded. The parent bsc object is unlocked.
[A]: [A]: [A]: [A]:
194
deltaUtc
Description : Gap between the current OMC-R agent time and the GMT reference. Enter a positive value [+m] when the OMC-R agent is located east of the Greenwich meridian and a negative value [-m] when it is located west. [-1440 to +1440] minute The range of possible values allows to update the OMC-R reference time within 24 hours. Object : Type : Remark : md DP Setting this attribute does not change the time displayed in the system "Session informations" window which refers to the workstation internal clock. This parameter cannot be modified.
Value range :
Note :
detectionFunction
Description : Value range : Object : Type : Associated function. [excessiveAnomalyRate / outOfRangeCounter] mdWarning DP
directedRetry Class 3
Description : Minimum signal strength level received by the mobiles to be granted access to the neighbor cell, used in processing directed retry handovers in BTS mode. [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB adjacentCellHandOver >-48 dB DP V9
directedRetryModeUsed Class 3
Description : Specify how directed retry handovers are processed in a cell either directly by the BSC (microcells only) or by querying the BTS first. [bsc / bts] bts
195
Default value : Type : Checks :
bts DP
[C/M]:
The BSC mode is authorized if the cell is a microcell (cellType) and the adjacent cell umbrella Ref attribute is defined.
Note :
The micro cell should be entirely covered by the macro cell in order to use efficiently the bsc mode. The use of the bts mode is recommended in a hot spot when these are several micro cells under the umbrella. The bts mode allows the use of micro cells to rescue the umbrella cell and also avoids a saturation of the umbrella cell. The bts mode is also recommended for all other cases.
Release :
V9
directedRetryPrio Class 3
Description : Value range : Object : Feature : Type : Release : Defines the number priority for directed retry handovers. [0 to 17] bts General protection against ping-pong handovers (TF821 - V12) DP V12
directory
Description : Name of the directory created on the OMC-R agent disks for storing a delivery containing a BSS software version. The directory name identifies the type and version of the BSS software stored. Refer to the executableSoftware entry in the Dictionary. If the directory exists on the OMC-R agent disks, the user is warned. Value range : Object : Type : [BSxabvcdefgh (BSC software) / XXXabcdef (others)] md - Create delivery dir DP
196
display Data Configuration

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

Description : Value range : Object : A command applied on btssiteManager to state required data display. normal EDGE Select the object instance and choose the command.
distHreqt Class 3
Description : Number of distance measurements, used to compute the weighted average MS-to-BTS distance in handover algorithms. [1 to 16] handOverControl 4 DP
[C/M]:
distHreqt is equal to the number of weights in distWtsList (refer to the next entry).
distributionActivation Class 3
Description : Object : Value range : Type : Feature : Default value : Checks : Activation of distributions for observation purpose. bts [0/1: disabled / enabled] DP Distribution on Radio measurements 0
[C/M]:
Measurement distribution cannot be activated if interference matrix is running on this cell. The purpose of this semantic check is to forbid activation of interference matrix and distribution features at the same time on a cell.
Release : Note :
197
distributionDuration Class 3
Description : Object : Value range : Note : Type : Checks: Duration of the observation. bts [0..92] (1 unit = 15 minutes) 0 is interpreted as 1 DP
[C/M]
Feature : Default value : Release : Note :
Distribution on Radio measurements 0 V15 This parameter is mandatory. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
distributionTime Class 3
Description : Starting time of the observation period for distributions (OMC-R server current timer). bts [00:00 to 23:59] DP Distribution on Radio measurements 00:00
Object : Value range : Type : Feature : Default value :
198
Checks:
[C/M]
Note :
This parameter is mandatory. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1. The distributionTime parameter set by the operator is relative to the OMC-R server current timer, and not to the local BTS hour. In case of feature activation on all cells of a BSC, the time to compute all the corresponding TGEs can take up to 20 minutes. To ensure that the feature is not to be activated the day after, the operator must leave a margin of 30 minutes between activation time and distributionTime parameter.
Note :
Release :
V15
distributionQualityThreshold Class 3
Description : RxQual threshold for RxLev distribution. This parameter is used according to the following principles:
Uplink case: measurements are those given by the BTS. A measurement is taken into account in the uplink
199
RxLev distribution if the RxQual_UP is equal to or greater than distributionQualityThreshold.
Downlink case: measurements are those given by the MS. A measurement is taken into account in the downlink RxLev distribution if the RxQual_Dw is equal to or greater than distributionQualityThreshold. For RxQual distributions, all measurements are kept whatever their RxQual values are.
Object : Value range : Type : Feature : Default value : Release : Note : bts
[0 to 7] DP Distribution on Radio measurements 0 V15 This parameter is mandatory. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
distWtsList Class 3
Description : List of no more than sixteen weights, used to compute the average MS-to-BTS distance from distHreqt measurements. The L1M function balances distHreqt raw measurements with the weights defined in the distWtsList list. Each measurement is partnered with one weight in the list. Weight/measurement associations are set in the order which the weights are recorded. The latest received measurement is always partnered with the first weight in the list. Super-average = [ (measurement i x weighti)] / 100, i = 1 to distHreqt Value range : Object : Default value : Type : Checks : [0 to 100] % handOverControl 40 30 20 10 DP
[C/M]:
The number of weights in the list is equal to distHreqt and their sum equals 100.
200
diversity Class 2
Description : Whether reception diversity is allowed in a cell. This parameter is used to control the diversity activation and the choice of the algorithm [enabled / disabled] disabled (0) / enabled (1) / enhancedDiversity (3) bts disabled DP The Joint Diversity feature is applicable only on e-DRX and RM hardware. If the value enhancedDiversity is used for others types of TRX with diversity, then the V17 BTS shall apply the classic value (diversity enabled = 1).
Value range : Value range: Object : Default value : Type : Notes:
dlGMSKMCS2UpperThreshold Class 3
Description : The parameter sets the threshold between MCS2 and the next code in the two DL GMSK Only Link Adaptation tables and the DL GMSK table. [0 to 255] bts 0 (disabled MCS2 in the Link Adaptation tables) EDGE link adaptation (20219) DP V15
Value range : Object : Default value : Feature : Type : Release :
dlGMSKMCS3UpperThreshold Class 3
Description : The parameter sets the threshold between MCS3 and the next code in the two DL GMSK Only Link Adaptation tables and the DL GMSK table. [0 to 255] bts EDGE link adaptation (20219) 0 (disabled MCS3 in the Link Adaption tables) DP V15
201
dlMCS2UpperThreshold Class 3
Description : Value range : Object : Feature : Default value : Type : Release : The parameter sets the threshold between MCS2 and the next code in the DL 8PSK Link Adaptation table. [0 to 255] bts EDGE link adaptation (20219) 0 (disabled MCS2 in the Link Adaptation tables) DP V15
Description : Value range : Object : Feature : Default value : The parameter sets the threshold between MCS6 and the next code in the DL 8PSK Link Adaptation table. [0 to 255] bts EDGE link adaptation (20219) 0 (disabled MCS6 in the Link Adaptation tables)
202
Type : Release :
DP V15
diversityUTRAN Class 3
Description: Value range: Object: Default value: Type: Release: Note: Indicates if there is diversity in the cell or not 0: no diversity / 1: diversity adjacentCellUTRAN 0 DP V17 This parameter is only available for BSC 3000.
203
drxTimerMax Class 3
Description : Value range : Maximum value allowed for mobile stations to request non-DRX mode after packet transfer mode. [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 transfer non DRX mode is 0. Object : Feature : Default value : Type : Release : bts GPRS (SV407 - V12, and TF1220 V12.4c) 0s DP V12
dtxMode Class 3
Description : MS control of the discontinuous transmission mechanism in a cell. Discontinuous transmission is designed to lessen MS battery consumption and diminish interference by breaking off the transmission when no data or speech are being transmitted. Value range :
For BSC 3000: [frmsMayUseDtx_hrmsShallNotUseDtx, frmsShallUseDtx_hrmsShallNotUseDtx, frmsShallNotUseDtx_hrmsShallNotUseDtx , frmsMayUseDtx_hrmsMayUseDtx, frmsShallUseDtx_hrShallUseDtx, frmsShallNotUseDtx_hrShallUseDtx].
Object : Default value :
bts
DP
For BSC 3000: frmsMayUseDtx_hrmsMayUseDtx
Type : Remark :
The cellDtxDownlink attribute allows users to control the use of discontinuous transmission on the downlink. Refer to this entry in the Dictionary.
204
duration
Description : Time delay before running the next command. The Sleep command can be inserted in a command file as many times as necessary. Value range : Object : Type : [1 to 3600] seconds commandFile - Sleep command DP
dwAckTime Class 3 (packetAckTime)

Description : Value range : Object : Feature : Default value : Type : Release : Defines the DL TBF Keep-Alive timer. [1 to 64] steps 500 ms for downlink transfer transceiver GPRS (SV407 - V12 and TF1220 - V12.4c) 1 DP V12
dynamicAbis class 2
Description : Value range : Object : Default value : Checks : Enables and disables the dynamic abis feature Disabled/Enabled btsSiteManager Disabled
702CO01 "The dynamicAbis feature can not be activated on a btsSiteManager supporting more than 16 EDGE transceivers". 702CO02 "It is not allowed to set dynamicAbis parameter to "enabled" on a BTS e-cell and S8000 BCF or BTS version less V17". 11CO01 "The EDGE capability of a transceiver cannot be modified if the btsSiteManager is unlocked, and the dynamicAbis feature is enabled on it. The EDGE capability of a transceiver is set using the edgeDataServiceType parameter. ". It is forbidden to modify the numberOfJokerDS0 parameter on a transceiver object if the parent btsSiteManager instance is unlocked and the dynamic abis feature is activated. It is forbidden to add or remove an EDGE transceiver if the parent btsSiteManager instance is unlocked and the
205
dynamic abis feature is activated. An EDGE transceiver is a transceiver where edgeDataServiceType = fullCapabilityRequested.
Release : Note :
The egprsServices parameter on a bts object cannot be modified, if the parent btsSiteManager is unlocked, and the dynamicAbis feature is enabled on it. V17 This parameter is only available for BSC 3000.
dynamicAgprsAllowed Class 2
Description : Enables or disables the Dynamic Agprs feature on the whole PCU. Depending on BSC architecture and release:

Value range :
dynamicAgprsAllowed is a gprsPcuLockExtendedConf sub-parameter (BSC 3000 V14) dynamicAgprsAllowed is a stand-alone parameter (BSC V15)
Depending on BSC architecture and release:

Object : Default value : Release : Note :
[enabled / disabled] (BSC 3000 V14) [yes / no] (BSC V15)
pcu disabled or no (according to BSC architecture and release) V14 If EDGE is activated, enabling the dynamic Agprs feature is strongly recommended.
E
early classmark sending Class 3
Description : Whether Early classmark sending procedure initiated by a multiband MS is allowed. The information is broadcasted to the mobiles at regular intervals on the cell BCCH (SYS INFO 3). Value range : Object : Default value : Type : [Not Allowed/Allowed] bts Not Allowed DP
206
Note : Release :
The recommended value is Allowed. V10
earlyClassmarkSendingUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Note: V17 This parameter is only available for BSC 3000. Indicates whether UTRAN classmark change message will be sent with the Early classmark sending disabled/enabled bts Disabled DP
edgeDataServiceType Class 2
Description : Value range : Object : Default value : Type : Release : Type of EDGE packet data service which can be managed by one TDMA. capability not requested / full capability requested transceiver capability not requested DP V15
edgeFavor Class 3
Description : Value range : Object : Feature : Default value : Type : Release : The parameter is used by PCU to configure the relative offer of an EDGE TDMA. 1 to 5 (by step of 0,04) transceiver EDGE traffic management (20231) 1 DP V15
eDGEMixity Class 3
Description : Value range : Object : Limitation of GPRS mobiles allocation on EDGE TDMA. [0 to 100] bts
207
Feature : Default value : Type : Release :
EDGE dynamic allocation (20230) 100 DP V15
efd
Description : Identifier of an efd object defined with regard to the md object. Seven efd objects are automatically created for the md object, an "efdAlarm" type object, an "efdConfiguration" type object, an "efdObs" type object, an "efdSpecificNotif" type object, an "efdStateChange" type object, an "efdTrace" type object, and an "efdClass" type object. Refer to the efdType entry. The administrativeState attribute of an efd object sets the conditions for forwarding the associated messages to the OMC-R manager. Value range : Object : Type : Note : [0 to 2147483646] efd Id An efd object should be created in unlocked state.
efdType
Description : Value range : Type of the messages processed by the efd object. [efdAlarm / efdConfiguration / efdObs / efdSpecificNotif / efdStateChange / efdTrace / efdClass] An "efdAlarm" type object tallies alarm notifications issued by the OMC-R agent. An "efdConfiguration" type object tallies object create and set messages issued by the users and attribute value change messages issued by the BSC. An "efdObs" type object tallies observation messages collected by the OMC-R agent.
208
An "efdSpecificNotif" type object allows users to define sets of specific notification messages to process such as endOfArchival, endOfRestore, beginningOfBdeArchival, downloadEnd, endOfBdeArchival, endOfBdaBuiding, endOfMarkingConsultation, or endOfSoftwareChange. An "efdStateChange" type object tallies object state change notifications. An "efdTrace" type object tallies trace messages collected by the OMC-R agent. An "efdClass" type object tallies efd class objects creation and deletion messages. Thus these notifications enable to identify the external managers which are being connected to the MD-R. Object : Type : Restrictions : efd DP
[M]:
egprsIrULActivation Class 3
Description : Value range : Object : Default value : Type : Checks : Whether the uplink incremental redundancy feature is enabled or disabled. [disabled / enabled] bts disabled DP
[M] :
Uplink incremental redundancy can not be activated if EDGE feature is not activated on the cell. Refer to the egprsServices entry in this dictionary.
Release : Note:
V16 This parameter is mandatory.
209
egprsServices Class 3
Descriptio n: Activates EDGE in the cell. If 1, sets to 1 the EDGE presence bit in the GPRS CELL Options including BEP-PERIOD, EGPRS_PACKET_CHANNEL _REQUEST. If 0, sets to 0 the EDGE presence bit in the GPRS Cell Options omitting BEP-PERIOD and EGPRS_PACKET_CHANNEL_REQUEST. Disabled (value 0); Enabled (value 1) bts EDGE traffic management (20231) 0 DP
Value range : Object : Feature : Default value : Type : Checks:
[M] :
Checks are performed to determine the presence of a valid license for EDGE before the following operations:
setting the egprsService parameter on the bts object unlocking a TRX building a BSC resetting a BDA of a BSC
If the check fails, then the corresponding action is rejected and a clear error message displayed. Release : V15
emergencyCallPriority Class 3
Description : Index in the table allocPriorityTable for a TCH allocation request whose cause is "emergency call". This priority is used in primo-allocations or when an SDDCH cannot be allocated for overload reasons. Value range : Object : Default value : Type : [0 to 17] bts 17 DP
210
emergencyCallRestricted Class 3
Description : Value range : Whether emergency calls from mobiles are authorized in a cell. [not restricted / restricted]
not restricted .....
All emergency calls are accepted whichever is the mobile access class
restricted Emergency calls are forbidden for mobiles with access classes 0 to 9 For mobiles with access classes 11 to 15, emergency calls are forbidden for those whose classes are listed in the entries of the notAllowedAccessClasses attribute
Object : Default value : Type :
bts restricted DP
emergencyThreshold Class 3
Description : If the priority of a group call is equal or higher than emergencyThreshold, a notification is periodically sent. A mobile station entering a cell where such a high priority group call is ongoing is then notified. [none, priority 4, priority 3, priority 2, priority 1, priority 0, priority B, priority A] none is the lowest priority priority 0 is recommended signallingPoint ASCI priority 0 DP GSM-R V15
Value range :
Object : Feature : Default value : Type : Release :
eMLPPThreshold Class 3
Description : Defines the minimum value that the eMLPP Precedence of an incoming call must have to be taken into account by the BSS with inband signalling (paging and vbs/vgcs assignment request). [none / priority 4 / priority 3 / priority 2 / priority 1 / priority 0 / priority B / priority A]
Value range :
211
signallingPoint ASCI (GSM-R V12) none DP V12
enableRepeatedFacchFr Class 2
Description : Value range : Object : Feature : Default value : Type : Notes : Enables or disables the Repeated FACCH feature on AMR FR. [disabled / FR 4.75 kbps / FR 5.9 and lower / FR 6.7 and lower] bts Repeated Downlink FACCH disabled (0) DP
The recommended value is FR 6.7 and lower. This parameter applies to BSC 3000 V16 and higher.
Release :
V16
encrypAlgoAsscomp Class 1
Description : Whether the "Chosen encryption algorithm" element is used in the ASSIGN COMPLETE messages (Phase II compliance). [true / false] signallingPoint False DP V8
encrypAlgoCiphModComp Class 1
Description : Whether the "Chosen encryption algorithm" element is used in the CIPHER MODE COMPLETE messages (Phase II compliance). [true / false] signallingPoint False
Value range : Object : Default value :
212
Type : Release :
DP V8
encrypAlgoHoperf Class 1
Description : Whether the "Chosen encryption algorithm" element is used in the HANDOVER PERFORMED messages (Phase II compliance). [true / false] signallingPoint False DP V8
encrypAlgoHoreq Class 1
Description : Whether the "Chosen encryption algorithm" element is used in the HANDOVER REQUEST ACKNOWLEDGE messages (Phase II compliance). [true / false] signallingPoint False DP V8
encryptionAlgorSupported Class 0
Description : For BSC 3000. Type of ciphering capability supported by the BTSs of a BSS. When no ciphering capability is supported, users calls are not crypted.
Value range : Object : Default value : Type : Checks : Version :
[none / gsmEncryptionV1]
bsc none DP
[C/M]:
Only one type of ciphering capability is defined. V15-V16
213
encryptionAlgorSupported Class 3
Description : Type of ciphering capability supported by the BTSs of a BSS. When no ciphering capability is supported, users calls are not crypted.
Value range :
[none / gsmEncryptionV1] gsmEncryptionV3FallbackNoEncryption gsmEncryptionV3FallbackV1
Object : Default value : Type : Checks : Version :
bsc none DP
[C/M]:
Only one type of ciphering capability is defined. V17
end date
Description : To select call monitoring data recorded on that date and before. It is on or after beginning date. Do not fill in if information produced to the end should be displayed. Value range : Object : Type : Checks : [mm/dd/yyyy hh:mm:ss] Call monitoring - Display (SDO) DP
[A]:
end date is on or after beginning date.
end date
Description : Date on which data were last recorded in the log (default is the current date). It is on or after start date. Date format entry forms are detailed in NTP < 130 1>. Do not fill in if this criterion is not to be selected. Value range : Object : Type : Checks : [<date>] System session log - Filter DP
[A]:
end date is on or after start date.
214
end of probative Phase Type

Description : Value range : Object : Type : Release : Note : Whether the user validate or cancel the software change after new delivery activation. [validate software change / cancel software change] bsc - End of probative phase DP V11 This parameter only applies to BSC Upgrades with prototype BDA change (BSC Version Upgrade and BSC Edition Upgrade).
end time
Description : Absolute time of final job run if the job is to be periodically run over a limited period of time. Absolute time format entry forms are detailed in NTP <130>. If date matches the date in start time, fill in time with a value after start time. Value range : Object : Condition : Type : Checks : [<date>,<time>] job To define when a job periodicity is defined and only if the job life is limited (users choice). DP
[A]:
end time is after start time.
end time
Description : End of system log reading on the requested end date (default is 24:00). Absolute time format entry forms are detailed in NTP <130>. Do not fill in if this criterion is not to be selected. Value range : Object : Type : Checks : [<time>] System session log - Filter DP
[A]:
If end date and start date are identical, end time is after start time.
215
endAlarmFilter
Description : Condition for ceasing the alarm when no counter is involved. The fields that can be combined in the logical expression are described under the startAlarmFilter entry in the Dictionary. Value range : Object : Condition : Type : [logical expression] alarm criteria To define if no counter is associated with the criterion. DP
endAlarmThreshold
Description : Minimum counting value in the reference period, below which an end-of-alarm message is sent if the corresponding start-of-alarm message was sent first. The value must be checked by users. This attribute defines a minimum value read at the end of the defined refPeriod. It must be lower than startAlarmThreshold. Threshold changes are effective when the OMC-R is restarted. Value range : Object : Type : [0.00 to 2147483646] mdWarning if detectionFunction = "excessiveAnomalyRa te" DP
endAlarmThreshold
Description : Minimum (thresholdLow) / maximum (thresh oldHigh) counting value in the reference period, above/below which an end of "lower threshold/upper threshold" alarm message is sent if the corresponding start-of-alarm message was sent first. The value must be checked by users. If thesholdType is "thresholdLow", it defines a minimum value for a one minute reference period (or the counter collecting period for PCM unavailability counters), above which the end of "lower threshold" alarm message is sent. It must be greater than startAlarmThreshold "low".
216
If thesholdType is "thresholdHigh", it defines a maximum value for a one minute reference period (or the counter collecting period for PCM unavailability counters), below which the end of "upper threshold" alarm message is sent. It must be lower than startAlarmThreshold "high". Threshold changes are effective when the OMC-R is restarted. Value range : Object : Type : Remark : [0.00 to 2147483646] mdWarning if detectionFunction = "outOfRangeCounter" DP

endCounterThreshold
Description : Value range : Object : Condition : Type :
The threshold limits depend on the associated counter. The BSS counter threshold crossing detection mechanism is described in NTP < 07 >.
Maximum counting threshold when a counter is involved. [0 to 100] alarm criteria To define if a counter is associated with the criterion. DP
endSearchTime
Description : Absolute time to end searching for the observation reports to cumulate. It is six hours before beginSearchTime at the most. Observation data accumulating ends with the information contained in the first observation message collected in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Value range : Object : Type Checks : [<date> , <time>] Display custom report DP
[A]: [A]:
endSearchTime is before beginSearchTime. The defined period is less than or equal to six hours.
217
endSearchTime
Description : Absolute time to end searching for the observation report to edit (default is one hour before beginSearchTime). The report displays the information contained in the last observation message generated in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP <130>. Value range : Object : Type : Checks : Note : [<date> , <time>] Display raw report DP
[A]:
endSearchTime is before beginSearchTime.
If no permanent observation has been received within the specified period, a message is displayed.
endSearchTime
Description : Absolute time to end searching for the available permanent observations to list (default is twelve days before beginSearchTime). The last listed report is the first observation report generated in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP <130>. Value range : Object : Type : Checks : [<date> , <time>] List available permanent observations DP
[A]:
218
endSearchTime
Description : Absolute time to end searching for the available permanent observations to list (default is twelve days before beginSearchTime). The last listed report is the first observation report generated in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP <130>. Value range : Object : Type : Checks : [<date> , <time>] List available temporary observations DP
[A]:
endSearchTime
Description : Absolute time to end searching for the available permanent observations to list (default is twelve days before beginSearchTime). The last listed report is the first observation report generated in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP <130>. Object : Type : Checks : List observation messages DP
[A]:
endSessionCriteriaDuration
Description : Value range : Type : Release : Definition of the criterion end a call path tracing session. [5 to 1080] mins DP V11
219
endSessionCriteriaType
Description : Value range : Definition of the criterion that will end a call path tracing session. [duration / number (of calls) / oam (locking the callPathTrace object)]
duration ......... number .......... oam ............
endSessionCriteriaDuration = [5 to 1080] minutes endSessionCriteriaNbCall = [1 to 2500] administrativeState = "locked"
Only one criterion is defined. When it is true, the call follow-up session is stopped in the BSS. Refer to the usageState entry related to this object in the Dictionary. Object : Type : Checks : Note : callPathTrace DP
[M] :
The session is automatically restarted by unlocking the object, regardless of the end-of-session criterion.
enhancedTRAUFrameIndication
Description : Value range : Object : Type : Feature : Notes : Release : Whether the BTS uses the Enhanced TRAU Frame (EFT = executable Software) for TCU. [notAvailable / available / active] bsc DI PCM error correction (FM660 - V12) and PCM error correction removal (34533) Due to feature "PCM error correction removal", the only value allowed for this parameter is notAvailable V12
220
enhCellTieringConfiguration
Description : This attribute allows to configure the cell tiering algorithm at BTS level instead of the cellTieringConfiguration attribute from V14 release BSC. This parameter is composed of the following five parameters: pcwiHreqave: Averaging window size for PwCI Value range: Int [0 to 16] numberOfPcwiSamples: Minimum number of PwCI samples required to reach a reliable distribution (representative of the real distribution in the whole cell) x 1000 Value range: Int [0 to 60] hoMarginTiering: Hysteresis between the uCirDLH and lCirDLH tiering thresholds to avoid ping-pong handovers, expressed in dB Value range: Int [0 to 63] dB selfTuningObs: Indicating that the bts is in charge of sending PwCI distribution onto Abis interface Value range: [notSentByBts / sentEveryTime / sentEveryHour] nbLargeReuseDataChannels: Mean number of logical channels belonging to the large frequency reuse pattern and used at the same time for data communications Value range: Int [-16 to 16] Object : Type : handOverControl DP
221
Note :
Available bits are the following: Bit N: 7 6 5 4 3 2 1 0 Value X X 0 0 0 0 0 0 First bits (upper bits) indicate : - All bits set to 0 = PwCI distribution is gathered if tiering is activated (intracell attribute) but not sent onto Abis interface.
Checks :
[C/M] 522DI01:
Only ten cells at OMC-R level can be observed with this mode Only 40 cells at OMC-R level can be observed with this mode Bit six and seven can not be set at the same time All the handoverControl object instances of the OMC-R must have the same value for the selfTuningObs field when a bit is different from 0
Checks :
[C/M] 522DI02:
Checks : Checks :
[C/M] 522CO01: [C/M] 522CO02:
Note :
The bit numbers 0 to 5 (six lower bits) are reserved for future use. This attribute is modified by the Manager. Value changes are notified to the Manager.
Release :
V14
equipment identity
Description : This parameter is composed of the bts equipment name and the equipment processor number parameters. Refer to these entries in the Dictionary. mdWarning (create) DP V11 During the command "create mdWarning", the operator can define either "equipment identity" or "processor identity", but not both.
Object : Type : Release : Note :
222
equipment processor number

Description : To select a processor or an equipment in the preselected type Consult the corresponding notification messages ("Equipment number" field). Do not fill in if neither bsc equipment name nor bts equipment name is defined or if this criterion is not to be selected. Value range : Object : Type : [0 to 200] Alarm and notification logs - Filter DP
error concealment unit Class 2

Description : Whether the Error Concealment Unit (ECU) is used. The ECU provides a voice quality improvement on the uplink in bad radio propagation conditions. [not used, used] bts not used DP V11
estimatedSiteLoad Class 3
Description : This parameter is used
at site creation, in order to preset the Erlang consumption of the new Cell Group otherwise, in order to set the Erlang consumption of a site to a value either less or greater than the one calculated using the ERLANG_PER_N_TRX_CELL table
[0 to 1100] btsSiteManager 0 (the consumption is then calculated using the ERLANG_PER_N_TRX_CELL table) DP
223
Release : Notes:
V15 The internal erlang capacity of a TMU2 is 1100. A BSC filters the value of the estimatedSiteLoad parameter for a homogeneous TMU configuration (for example, either only TMU1 or only TMU2) that has been declared as a homogenous TMU configuration through the BSC Data Config, This filtering does not apply to homogeneous BSC configurations that are not declared as this type of configuration through the BSC Data Config. For a homogeneous TMU1 configuration, the BSC uses the value min(550,estimatedSiteLoad). For a homogenous TMU2 configuration, the BSC uses the value min(1100,estimatedSiteLoad).
exclusive interval of codano

Description : To select messages according to their fault number. The filter can contain one (or several) intervals defining the fault numbers not to be retrieved. For example, interval 5~8 enables to retrieve ALL the fault numbers except fault numbers 5, 6, 7, and 8. Value range : Object : Type : Release : [0 to 65535 - 0 to 65535] Alarm and notification logs - Filter DP V12
exclusive list of codano

Description : Value range : Object : Type : Release : To select messages that do not contain one (or several) given fault number(s). [0 to 65535] Alarm and notification logs - Filter DP V12
executableSoftware
Description : An instance of this managed object class is used to represent a unit of software that is separately identifiable and is ready to be used by the system. [0 to 255]
Value range :
224
Object : Type :
executableSoftware DP
executableSoftwareId
Description : Identifier of a executableSoftware object class. This identifier is allocated by the MD-R at object creation, if not given by the Manager. This attribute cannot be modified. [0 to 255] executableSoftware Id V13
executableSoftwareName
Description : Name of a software version. This attribute is allocated by the MD-R at object creation, if not given by the Manager. This attribute cannot be modified. [9 to 12] String executableSoftware DP V13
extended cell Class 2

Description : Whether the cell is extended (up to 120 km large) or not. The cell working mode governs the upper limit of the following attribute values (refer to theses entries in the Dictionary):

callClearing, msRangeMax, and rndAccTimAdvThres hold attributes of the bts object concentAlgoExtMsRange and concentAlgoIntMsRan ge attributes of the associated handOverControl object if the bts object describes a concentric cell
[true (extended) / false (normal)] bts false DP
225
Checks :
[M]:
If the attribute is changed to "true" and a CBCH is defined for the cell, this channel is carried by a radio time slot with an even identifier number. Refer to the channelType entry in the Dictionary.
Release : Note :
V9 In that mode, the radio time slots with odd identifier numbers are unknown to the BSC and the diversity functionality is not available in the cells.
external alarm configuration Class 2

Description : Configuration of the external alarm loops controlled by a BTS. Alarm loop "n" is monitored (not monitored) when the nth bit is set to 1 (0) in the binary field. The alarm mask is immediately displayed in the hexadecimal field just below. The alarm mask can be set using the hexadecimal field as well as the binary field. The number of connectors per alarm board depends on the type of the alarm boards installed in the BTS.
BTS
Type of board
Number of protected external alarms per cabinet 16 16 16 8
S8000 S12000 BTS 18000 BTS 6000 (See note below.)
ALCO RECAL (CBCF) ALCO RECAL (CBCF) ABM ABM/RICAM
The correspondence between those 48 bits and the external alarms of each site directly depends on three factors: the type of BTS, the number of cabinets, and the convention for numbering those cabinets.
226
S8000/S12000/BTS 18000:
48 external alarms max., up to 3 cabinets in the future - 16 alarms per cabinet (16 bits per cabinet). 24 external alarms max., up to 3 cabinets - 8 alarms per cabinet (8 bits per cabinet).
Value range : Object : Default value : Type : Note:
BTS 6000:
[48-bit register] btsSiteManager 48 bits equal to "0" DP If RICAM/ICAM is used instead in the BCF, the reduced connectivity leads to limitations in terms of ABMs. Then in term of total alarms:
BTS18000 with RICAM/ICAM max. configuration includes one full main cab + one half ext cab, that is 1 RICAM + 2 ABMs, so 24 DALE max. BT6000 with RICAM/ICAM max. configuration includes one main cab + one ext cab, that is 1 RICAM+ 1 ABM, so 16 DALE max.
Release :
V17
external battery cabinet Class 2

Description : Value range : Object : Type : Release : Presence or absence of the optional equipment "ancillary battery cabinet" in S8000 Outdoor. [Present / Absent] btsSiteManager DP V9
externalTime
Description : Current OMC-R agent date and time. Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : [<date> , <time>] md DP
227
Remark :
Setting this attribute does not change the time displayed in the system "Session informations" window which refers to the workstation internal clock. This parameter cannot be modified.
Note :
extUtbfNoData Class 3
Description : When this Extended UL TBF sub-feature is enabled, it makes possible that MSs do not send Packet Uplink Dummy Control Block during periods of inactivity. [disabled / enabled] bts disabled DP Extended UL TBF V15
Value range : Object : Default value : Type : Feature : Release :
F
facchPowerOffset Class 2
Description : Value range : Object : Type : Feature : Default value : Note : Release : Power offset that applies to FACCH signalling [0..10]; step = 2 bts DP Tx power offset for signalling channels 0 (no power offset) This parameter applies to BSC 3000 V16 and higher. V16
Family
Description : Family of counters in which are chosen the counters to be observed. The list of the available families depends on the Observed object class and the observation type selected in the report template definition of the observation. See Tables hereafter. Value range : Object : Type : [See tables below] report template DP
228
Checks :
[M] :
Family is used to include counters in observation report. Family is not saved with the report template as it is reset every time the template editor is open. Counters from different families can be included in the same report template.
Observed object: bsc
Observation real time (ORT) Observation fast statistic (OFS)
A interface, synthetic A interface, OMC interface Releases of communications in signaling phase, Channel mode, ASCI, NONE, BSC 3G, synthetic
Observed object: bts Observation real time (ORT) SDCCH allocations, Intra-bss handovers, Inter-bss handovers, TCH allocations, Establishment, Global handovers SDCCH allocations, TCH allocations, Channel mode, Inter-bss handovers, Intra-bss handovers, Intra-cell handovers, Dedicated channel assignment, Global handovers, Establishment, Releases of communications in signaling phase, Releases of communications in traffic phase, Layer One Management, Interferences, Directed retry, SMS, Abis Level 2, ASCI, NONE, GPRS, AMR, EDGE, WPS, synthetic
Observation fast statistic (OFS)
Observed object : transceiverZone Observation real time (ORT) SDCCH allocations on TrZone TCH allocations on TrZone
229
Observation fast statistic (OFS)
SDCCH allocations on TrZone, TCH allocations on TrZone, Layer One Management on TrZone, GPRS on TrZone, AMR on TrZone, EDGE, WPS -------------------------------------------
Observed object : transceiverEquipment Observation real time (ORT) Observation fast statistic (OFS)
Observed object : btsSiteManager Observation real time (ORT) Observation fast statistic (OFS) ---------------------BSC 3G - Abis Level 1
Observed object : pcmCircuit Observation real time (ORT) Observation fast statistic (OFS) ----------------------PCM/synthetic
Observed object : adjacentCellHandOver Observation real time (ORT) Observation fast statistic (OFS) Observed object : omu Observation real time (ORT) Observation fast statistic (OFS) Observed object : tmu Observation real time (ORT) Observation fast statistic (OFS) Observed object : cc Observation real time (ORT) --------------------------------------------BSC 3G ----------------------BSC 3G --------------------Neighbor cells, AMR
230
Observation fast statistic (OFS) Observed object : cem Observation real time (ORT) Observation fast statistic (OFS) Observed object : pcmPort Observation real time (ORT) Observation fast statistic (OFS)
BSC 3G
----------------------BSC 3G
---------------------BSC 3G - PcmPort
Observed object : signalingLink Observation real time (ORT) Observation fast statistic (OFS) Observed object : channel Observation real time (ORT) Observation fast statistic (OFS) -------------------------------------------------------------------------------------
faultNumber
Description : To select messages with a given fault number. This parameter is a component of the specific problems filter. Refer to this entry in the Dictionary. Value range : Object : Type : [0 to 40000] Alarm and notification logs - Filter DP
fDDARFCN Class 3
Description: Value range: Object: Default value: Type: Release: DP V17 UTRAN FDD frequency 0 ... 16383 adjacentCellUTRAN
231
Checks:
[M]:
AdjacentCellUtran objects belonging to the same bts cannot have more than 3 different fDD_ARFCN values. The set of attributes fDDARFCN and scramblingCode must be unique among all the instances of the objects adjacentCellUTRAN attached to the same bts The purpose of this check is to Check unicity of UTRAN radio neighbouring cells identifiers for one GSM cell . fDDARFCN or scramblingCode cannot be changed if Interference Matrix feature is activated on the bts. Check that there is no more than three different FDD_ARFCN values in all the adjacentCellUTRAN objects of one cell.
[C/M]:
[C/M]:
[C/M:
Note:
This parameter is only available for BSC 3000.
fDDMultiratReporting Class 3
Description: Value range: Number of FDD cells to be reported in the list of strongest cells in the EMR message 0...3, 0 = No UTRAN cell is favored, 1 = strongest UTRAN cell is favored. 2 = strongest UTRAN cells are favored. 3 = strongest UTRAN cells are favored. bts 0 - No UTRAN cell is favored. DP
Object: Default value: Type: Checks: Release: Note:
232
fDDReportingThreshold Class 3
Description: Value range: Apply priority reporting if the reported value is above threshold for FDD frequency band 0...6 on MOD (corresponds to -115, -109, -79 dBm RSCP values on MMI; + 7 on MOD corresponds to never on MMI) handoverControl Never DP
fDDReportingThreshold2 Class 3
Description: Value range: Indicates the CPICH Ec/N0 level above which UTRAN cells will be reported by the MS 0... 63 (0 means always reported) The Ec/No step is in half dB:

Object: Default value: Type: Checks: Release: Note: V17 handoverControl 0 DP
0 means always reported. In range 1 to 49, 1 means CPICH Ec/No -24 dB and 49 means CPICH Ec/No 0 dB. Values from 50 to 63 should not be used for Ec/No.
This parameter is available only for BSC 3000.
fERThreshold1 Class 3
Description : Object : Value range : Type : Lowest threshold taken into account for Frame Erasure Rate (FER) evaluation. bts [0 to 100], steps of 0.1 % DP
233
Feature : Default value : Note :
Distribution on Radio measurements 0 This parameter is mandatory. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
Checks :
[C/M]:
Following rule applies: fERThreshold1 <= fERThreshold2 <= fERThreshold3 <= fERThreshold4 The purpose of this semantic check is to check coherency between FER thresholds.
Release :
V15
Description : Object : Value range : Type : Feature : Default value : Note : Second threshold taken into account for FER evaluation. bts [0 to 100], steps of 0.1 % DP Distribution on Radio measurements 0 This parameter is mandatory. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
Checks :
[C/M]:
V15 Release :
Description : Object : Value range : Type : Feature : Default value : Third threshold taken into account for FER evaluation. bts [0 to 100], steps of 0.1 % DP Distribution on Radio measurements 0
234
Note :
This parameter is mandatory. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
Checks :
[C/M]:
Release :
V15
Description : Object : Value range : Type : Feature : Default value : Note : Highest threshold taken into account for FER evaluation. bts [0 to 100], steps of 0.1 % DP Distribution on Radio measurements 0 This parameter is mandatory. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
Checks :
[C/M]:
Release :
V15
fhsRef Class 2
Description : Identifier of the frequencyHoppingSystem object that defines the frequency hopping management parameters for the radio time slot. Setting this attribute and the maio attribute allows the time slot to obey frequency hopping laws. Value range : Object : Condition : Type : [0 to 63] channel To define if the time slot hops in frequencies. DP
235
Checks :
[C/M]:
This attribute is undefined if frequency hopping is not allowed for the parent bts object (btsIsHopping = "no hopping") or the channelType of the channel object is "mainBCCH", "mainBCCHCombined", or "bcchSdcch4CBCH". If the attribute is defined, the following is checked:
[C/M]:
The maio attribute is also defined. The referenced frequencyHoppingSystem object is created for the parent bts object. Each frequency occurs once in the mobileAllocatio n list and is allotted in the cellAllocation list of the parent bts object. The number of frequencies in the mobileAllocation list is greater than the maio attribute value. Concentric cell: The frequencies in the mobileAllocation list are not used in the zone to which the parent transceiver object does not belong.
filteredTrafficCoefficient Class 3
Description : Object : Value range : Type : Feature : Default value : Release : Filter coefficient which is taken into account in the cell load evaluation. bts [0 to 1, by step of 0.001] DP AMR based on traffic 0 V15
floor
Description : Value range : Object : Type : Floor number which identifies the localization in a building. [1 to 2 characters] transcoder, controlNode, interfaceNode, hardware transcoder 3G. DD
236
flowControlMaxDelay
Description : This attribute specifies the maximum time interval between two consecutive FLOW-CONTROL-MS messages sent to the SGSN. [5 to 6000] seconds pcusn 300 DP V14
flowControlMaxRate
Description : This attribute specifies the minimum interval between sending consecutive Flow-Control PDU for a given BVC or for a MS. It represents the C timer in the ETSI GPRS specifications. [1001 to 9999] ms pcusn 2000 DP V14
fnOffset class 2
Description : Allows to specify and control Frame Number (FN) difference between BTSs in case of network synchronization by GPS. Refer also to the tnOffset entry in this dictionary. Object : Value range : Type : Feature : Default value : Release : Note : btsSiteManager [0..84863] DP Network Synchronization 0 V15 This parameter is optional. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
237
forced handover algo Class 3

Description : Minimum signal strength level received by the mobiles to be granted access to a neighbor cell in case of forced handover. [less than -110, -110 to -109, ..., -49 to -48, more than -48] dB handOverControl less than -110 DP V9
frAmrPriority Class 2
Description : This attribute defines the AMR FR priority of a TDMA. This attribute is modified only if the corresponding bts object instance is locked (objectMustBeLockedError). Value range : Int [0 to 2] Priority 0 is given to a high priority TDMA Priority 1 is given to a low priority TDMA Priority 2 disables this service on the TDMA transceiver 0 DP V14 This parameter is only available for BSC 3000.
Object : Default value : Type : Release : Note :
frequencyHoppingSystem
Description : Identifier of a frequencyHoppingSystem object that defines frequency hopping management parameters for radio time slots that obey frequency hopping laws. A bts object may reference up to sixty-four objects of this type. Refer to the hoppingSequenceNumber and mobileAllocation entries in the Dictionary. Value range : Object : Type : Checks : [0 to 2147483646] frequencyHoppingSystem Id
[C]:
The associated bts object is created and the frequencyHoppingSystem object is not created for that object.
238
[C]:
The number of frequencyHoppingSystem objects created for a bts object is limited to sixty-four. If the application database of the related BSC is built, the parent bsc object is unlocked. The parent bsc object is unlocked and the associated bts object is locked. The frequencyHoppingSystem object is created. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command. No channel object dependent on the bts object refers to the frequencyHoppingSystem object (fhsRef attribute).
[C/D]: [M]: [M/D]: [D]:
[D]:
frPowerControlTargetMode Class 3
Description : This attribute defines the target codec mode for AMR FR power control. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute is modified if the powerControl object instance is unlocked. Value range : Object : Default value : Type : Release : Note : [FR 12.2 / FR 10.2 / FR 6.7 / FR 5.9 / FR 4.75] powerControl FR 12.2 DP V14 This parameter is only available for BSC 3000.
frPowerControlTargetModeDl Class 3
Description : Value range : Object : Feature : Default value : Type : Downlink AMR codec target used to define the downlink power control threshold for FR AMR calls. [FR 12.2 / FR 10.2 / FR 6.7 / FR 5.9 / FR 4.75] powerControl Tx power offset for signalling channels FR 12.2 DP
239
Notes : Release :
This parameter applies to BSC 3000 V16 and higher. V16
fullDlKa Class 3
Description : Whether the Full DL Keep Active feature is enabled or not. This feature allows MSs that operate in a non-extended UL TBF mode to increase their uplink throughput. Value range : Object : Feature : Default value : Type : Checks : [disabled / enabled] bts Extended UL TBF disabled DP
[C/M]:
The following flag combination is prohibited: nwExtUtbf = enabled and fullDlKa = disabled
Release :
V15
G
geographical coordinates
Description : Definition of the geographical coordinates of the equipment 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 .......... Min Lat .......... Hundreth of sec Lat ........ Direction Lat ....
[0 to 90] degrees [0 to 59] minutes [0 to 5999] hundredth second
[North / South]
Longitude is expressed by the four following fields: Deg Lon .......... Min Lon .......... Hundreth of sec Lon ........ Direction Lon .... [0 to 180] degrees [0 to 59] minutes [0 to 5999] hundredth second
[East / West]
240
Object :
bsc btsSiteManager md transcoder DI V11
Type : Release :
geographical coordinates
Description : Definition of the geographical coordinates of the pcuSN equipment in the network. These coordinates are defined by a latitude and a longitude, each expressed by four fields. Value range : Latitude is expressed by the four following fields:

Deg Lat .......... Min Lat .......... Hundreth of sec Lat ........... Direction Lat ....
[0 to 90] degrees [0 to 59] minutes [0 to 5999] hundredth second
[North / South]
Longitude is expressed by the four following fields: Deg Lon .......... Min Lon .......... Hundreth of sec Lon ........... Direction Lon .... [0 to 180] degrees [0 to 59] minutes [0 to 5999] hundredth second
[East / West]
pcu, pcusn GPRS (SV407 - V12) DI V12
gprsAvgParam Class 3
Description : This parameter is composed of the following attributes:
nAvgI nAvgT nAvgW
241
Refer to these entries in this dictionary. Release : V12
gprsCellActivation Class 3
Description : Value range : Object : Feature : Default value : Type : Release : This is a Flag used to activate the GPRS at cell level. [disabled / enabled] bts GPRS (SV407 - V12) disabled DP V12
gprsNetworkModeOperation Class 3
Description : Value range : Indicates the network mode of operation. [0..2] with:

Object : Feature : Default value : Type : Release : bts
0 = NMO II 1 = NMO I (recommended value, activates the feature from the MSs point of view) 2 = NMO III (forbidden in this release)
GPRS (TF1134 - NMO I) 0 (NMO II) DP V15
gprsPcuCrossConnectList Class 2
Description : This parameter is a list of pairs of the following attributes:
pcmNbr nbrTch
Refer to these entries in this dictionary.
242
Value range :
BSC 3000 V15: BSC 3000 V16, nbrTch] BSC 3000 V16, nbrTch] BSC 3000 V17:
[0 to 24] pairs of [pcmNbr, nbrTch] E1 PCM: [0 to 32] pairs of [pcmNbr, T1 PCM: [0 to 36] pairs of [pcmNbr, [0 to 54] pairs of pcmNbr, nbrTch]
Feature : Release :
PCUSN - more than 12 Agprs PCMs per BSC (18749) V12
gprsPcuLockExtendedConf Class 2

Default value : Release :
dynamicAgprsAllowed agprsTSharingProtection
Refer to these entries in this Dictionary. [disabled / 0] V12
gprsPermittedAccess Class 3
Description : It defines the Routing Area Color (3-bit length) of the cell. If the MS receives different values of the Routing Area Color field in two different cells, it shall interpret the cell re-selection information as if the two cells belonged to different RA. [0 to 7] bts 0 GPRS (SV407 - V12) DP V12
Value range : Object : Default value : Feature : Type : Release :
243
gprsPreemption Class 3
Description : Set to yes, it allows the PCU to refuse GSM preemption over shared GSM/GPRS TS if GPRS resources are not sufficient to ensure the minimum bandwidth for each MS. In the case of lack of GSM radio TS, the BSC has to allocate one shared GSM/GPRS radio TS to GSM and a preemption procedure is started. When one shared radio TS temporarily allocated to GSM is released (end of GSM allocation due to end of call or handover), then a reallocation procedure is started to increase the GPRS capacity. Value range : Object : Feature : Default value : Type : Release : [yes / no] bts GPRS (TF1121 - V12) yes DP V12
gprsPreemptionForHR Class 3
Description : Value range : Object : Default value : Recommended value : Type : Release : Activation of PDTCH pre-emption for HR channel disabled/enabled bsc 0 (disabled) 1 (enabled) DP V17
gprsPreemptionProtection Class 3
Description : Protection timer used by the BSC in order to reduce the load in case of PCU TDMA TS Status Nack message reception during a preemption procedure. This message is sent by the PCU. [1 to 60] second(s) bts GPRS (TF1121 - V12) 10
Value range : Object : Feature : Default value :
244
Type : Release :
DP V12
gprsPriority Class 2 (gprsTranscvLockExtendedConf)

Description : Priorities affected to the TDMA. Priority affected to the TDMA when allocating packet resources. Value range : Object : Default value : Feature : Type : Release : [p1 or p2 (high GPRS priority)] transceiver p1 GPRS (TF1121 - V12) DP V12
gprsState
Description : Object : Type : Release : Reserved for future use. bts (cell) DD V15
gprsState
Description : Object : Type : Release : Reserved for future use. transceiver DD V15
gsmToUmtsReselection Class 3
Description : Attribute specified to implement L1M features on PowerControl. This spare parameter is used to transit the attribute.
245
gsmToUmtsR eselection is composed of 4 parameters:

Default value : Object : Type : Checks: no bts DP
UMTS Access min level UMTS reselect ion ARFCN UMTS reselect ion offset UMTS search min level
[C/M]:
UMTS reselection ARFCN of the attribute gsmToUmtsReselection accept 0 (feature not activated) or frequencies must be in bands:
band I (UMTS 2000): 10562 to 10838 band II (UMTS 1900): 9662 to 9938 and 412, 437, 462, 487, 512, 537, 562, 587, 612, 637, 662, 687 band III (UMTS 1800): 1162 to 1513 band IV: (UMTS 1700/2100): 1537 to 1738 and 1887, 1912, 1937, 1962, 1987, 2012, 2037, 2062, 2087 band V (UMTS 850): 4357 to 4458 and 1007, 1012, 1032, 1037, 1062, 1087 band VI (UMTS 800): 4387 to 4413 and 1037, 1062 band VII (UMTS 2600): 2237 to 2563 and 2587, 2612, 2637, 2662, 2687, 2712, 2737, 2762, 2787, 2812, 2837, 2862, 2887, 2912
246

Release : V14
band VIII (UMTS 900): 2937 to 3088 band IX: (UMTS 1700): 9237 to 9387
gsmToUMTSServiceHo Class 3
Description: Allows the customer to set a value that the BSC uses when the MSC does not provide optional service handover information in ASSIGN_REQUEST or HANDOVER_REQUEST messages 0: should;1: should not; 2: shall not; 3:gsmToUMTSHoDisabled (always takes precedence over the MSC value) bsc 3 DP
Value range:
V17 This parameter is available only for BSC 3000. This parameter is optional.
H
handOver from signalling channel Class 3
Description : Value range : Object : Default value : Type : Remark : Authorization to perform intercell handovers on signalling channels (SDCCH or TCH in signalling mode). [enabled / disabled] handOverControl disabled DP The attribute was named TCH and sDCCHHandOver on the V8 OMC-R MMI.
handOverControl
Description : Identifier of a handOverControl object that defines handover management parameters in a cell. A bts object may reference one and only one object of this type. [0 to 2147483646]
Value range :
247
handOverControl Id
[C]:
The associated bts object is created and the handOverControl object is not created for that object. The parent bsc object is unlocked. If class 2 attributes are modified, the associated bts object is locked. If the application database of the related BSC is built, the parent bsc object is unlocked and the associated bts object is locked. The handOverControl object is created. The associated bts object is not referenced, except by a powerControl object. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.
[M]:
[C/D]:
[M/D]: [D]: [D]:
hardware configuration Class 2

Description : Type of architecture used in the transceiverEquipment. This parameter flags the TRX in HPRM, RM, MPRM or HPRM3T in the BTS 18000.
Value range :
[Dcu2 / Dcu4 / Drx / Rm / Hprm / Mrm / Other] for BSC V15 [Dcu2 / Dcu4 / Drx / Rm / Hprm / Mprm / HPRM3T / Other] for BSC V16 and subsequent releases [RM1/2 1800 30/30, RM2 1800 30/30, RM1/2 1800 50/30, RM2 1800 50/30, DCU2, DCU4, DRX, RM1/2 900 40/40, RM1 900 40/40, RM2 900 40/40, RM1 900 60/45, RM2 900 60/45, RM1/2 1900 30/30, RM1 1900 30/30, RM2 1900 30/30, RM2 1900 50/30, RM1 1800 30/30, RM1 1800 50/30, RM1 850 60/45/Other] for BSC V17 and subsequent releases
Object : Feature :
transceiverEquipment BTS 18000 introduction, BTS 18000 HPRM, differentiation of the BTS 18000 RMs with power transmit level of 40 Watts, and BTS 18000 HPRM3T differentiation at the OMC-R 0 DP
Default value : Type :
248
Checks :
[M]:
Checks that the default value is not left on BTS 18000. In case of BTS 18000 (btsModel = 910, 911, 900, 901), checks at unlock transceiverEquipment that its HardwareConfiguration is different from DRX, DCU2, DCU4. Checks that the default value is not left on BTS 6000 or BTS 18000. In case of BTS 6000 or BTS 18000 (btsModel = 910, 911, 900, 901), checks at unlock transceiverEquipment that its HardwareConfiguration is one of the following DCU2, DCU4. or "DRX" Checks that default value is set on other BTS than BTS 18000. In case of BTS different from BTS 18000 (btsModel = 910, 911, 900, 901), this checks at unlock transceiverEquipment that its Hardware Configuration is different from Rm, Hprm, Mprm, Hprm3t or Other. Checks that default value is set on other BTS than BTS 6000 or BTS 18000. In case of BTS different from BTS 6000 or BTS 18000 (btsModel = 910, 911, 900, 901), this checks at unlock transceiverEquipment that its Hardware Configuration is different from Rm, Hprm, Mprm, Hprm3t or Other. Consistency inside an RM definition. In case of BTS 18000 (btsModel = 910, 911, 900, 901), this checks at unlock transceiverEquipment that its hardware configuration is the same as the other unlocked transceiver equipment of the same RM. Consistency inside an RM definition. In case of BTS 6000 or BTS 18000 (btsModel = 910, 911, 900, 901), this checks at unlock transceiverEquipment that its hardware configuration is the same as the other unlocked transceiver equipment of the same RM. Software Reference coherency inside an RM. Existing check that must be run after previous checks.
Checks:
[M]:
[M]:
[M]:
[M]:
[M]:
Release : Note :
[M]:
V11 The value MRM is not supported. The value HPRM3T only applies to BSC 3000.
249
hardwareRef Class 2
Description : Value range : Object : Type : Hardware reference of a site BCF. Check BSS upgrade file. [0 to 65535] btsSiteManager DP
hardwareRef Class 2
Description : Hardware reference of a TRX/DRX. Check BSS upgrade file. When a TRX is a DCU4 or a DRX ( S8000, S12000, E-cell), the hardware reference field of the transceiver equipment object must be equal to 0. [0 to 65535] transceiverEquipment DP
hexa text
Description : Transcription in hexadecimal of the contents of a short message. The content of the hexa text parameter is displayed when using the command Display hexa. It cannot be modified by the user. Only the content of the text parameter is modified by the user. Refer to the text (short message) entry in the Dictionary. Value range : Object : Type : Release : [chain of characters] short message - Display hexa DI V12
hoMargin Class 3
Description : Value range : Object : Default value : Type : A margin to use for PBGT handovers to avoid subsequent handover, in PBGT formula. [-63 to 63] dB adjacentCellHandOver 4 DP
250
hoMarginAMR Class 3
Description : This attribute defines the handover margin linked to AMR quality handover. This attribute is modified if the adjacentCellHandOver object instance is unlocked. Value range : Object : Default value : Type : Release : [-63 to 63] dB adjacentCellHandOver -2 DP V14
hoMarginAMRUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Note: V17 This parameter is only available for BSC 3000. Margin to be used for intercell quality handover to UMTS for AMR calls -63...63 adjacentCellUTRAN 63 DP
hoMarginBeg Class 3
Description : Margin to be added to hoMargin until rxLevHreqave for early handover mechanism in order to compensate the lack of measurements. This parameter is coupled with hoMargin and rxLevHreqaveBeg. Value range : Object : Default value : Type : Checks : [0..63] dB bts 4 DP
[M] :
This parameter is inhibited when set to 63 dB.
251
Note :
This parameter shall be set such as hoMarginhoMargin+ hoMarginBeg or hoMarginBeg0 This parameter is not available for DCU2.
Release :
V11
hoMarginDist Class 3
Description : Value range : Object : Default value : Type : Release : Margin to be used for Distance Handovers. [-63 to 63] dB adjacentCellHandOver -24 dB DP V8
hoMarginDistUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Note: V17 This parameter is available only for BSC 3000. Margin to be used for distance handover to UMTS -63...63 dB adjacentCellUTRAN 63 DP
hoMarginRxLev Class 3
Description : Value range : Object : Default value : Type : Release : Margin to be used for signal strength Handovers. [-63 to 63] dB adjacentCellHandOver -24 dB DP V8
hoMarginRxQual Class 3
Description : Value range : Object : Default value : The margin is used for Signal Quality Handovers. [-63 to 63] dB adjacentCellHandOver -24 dB
252
Type : Release :
DP V8
hoMarginTiering Class 3
Description : Hysteresis between the uPwCIDLH and lPwCIDLH tiering thresholds to avoid ping-pong handovers (expressed in dB). This attribute allows to configure the CellTieringConfiguration at bts level. CellTiering mode must be activated. [0 to 63] dB handOverControl 4 dB Automatic Cell Tiering (TF995-V12) DP V12
Note : Value range : Object : Default value : Feature : Type : Release :
hoMarginRxLevUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Note: V17 This parameter is available only for BSC 3000. Margin to be used for signal strength handover to UMTS -63...63 dB adjacentCellUTRAN 63 DP
hoMarginRxQualUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Note: V17 This parameter is available only for BSC 3000. Margin to be used for signal quality handover to UMTS -63...63 dB adjacentCellUTRAN 63 DP
253
hoMarginTrafficOffset Class 3
Description : Minimum signal strength margin with the serving cell allowing the best neighbor cell selection when a handover is triggered for overload reasons. [0 to 63] dB adjacentCellHandOver Handover for traffic reasons (TF132 - V12) 0 dB DP
Value range : Object : Feature : Default value : Type : Checks :
[C/M]: [C/M]:
This attribute must be in the range [0 63]. When set to "0", the handovers for traffic reasons are not allowed in the adjacent cell.
Release : Note :
V12 This attribute only applies to BTSs equipped with non mixed DCU4 or DRX boards.
hoMarginTrafficOffsetUTRAN Class 3
Description: Offset to be subtracted to the hoMarginUTRAN to allow handover for traffic reason when the current cell is in overload 0...63 dB adjacentCellUTRAN 63 DP
Value range: Object: Default value: Type: Checks: Release: Note:
V17 This parameter is available only for BSC 3000.
hoMarginUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Note: V17 This parameter is only available for BSC 3000. Margin to be used for PBGT handover to UMTS -63...63 dB adjacentCellUTRAN 63 DP
254
hoPingpongCombination Class 3
Description : Two causes (HOInitialCause and HONonEssentialCause), indicating the causes of ping-pong handovers in overlapping areas. The following causes are defined with regard to the neighboring cell:
HOInitialCause indicates the essential handover cause which leads to enter the neighbor cell (cause of incoming handover). HONonEssentialCause indicates the non-essential handover cause which leads to leave the cell (cause of outgoing handover).
This parameter defines the combination for which the hoPingpongTimeRejection attribute is used. Value range : [rxQual, rxLev, distance, powerBudget, capture, directedRetry, OaM, traffic, all, allCapture, allPowerBudget, AMRquality] adjacentCellHandOver General protection against ping-pong handovers (TF821-V12) DP
[M]:
The parent bsc object is unlocked. Check that all the values of HOPingpong Combination attribute must be different. This element checks for non duplications of HOPingpongCombination values
[M]:
Notes :
allCapture cause (only applying to HONonEssentialCa use)matches the capture cause for all the micro-cells belonging to the current macro-cell . This cause has to be used in order to prevent ping-pong handovers between micro- and macro-layers. allPowerBudget cause (only applying to HONonEss entialCause) matches the powerBudget cause for all the neighboring cells of the current cell. This cause is used in order to restore the "Minimum time between handovers" (feature TF218).
Release :
V12
255
hoPingpongCombinationUTRAN Class 3
Description: List of couple of causes indicating the causes of ping-pong handovers in the overlapping areas (cause of incoming ho, cause of outgoing ho). It is possible for up to four elements to appear in the list . List of cause GSM to UMTS and cause UMTS to GSM (traffic, powerBudget, directedRetry, rxLev, rxQual, distance, OaM (forced ho), all, allPowerBudGeT) adjacentCellUTRAN ("rxQual", "powerBudget") DP
Value range:
hoPingpongTimeRejection Class 3
Description : Time before a new handover attempt is triggered. Refer to bsc object timeBetweenHOConfiguration and bts object bts time between HO configuration attributes in this Dictionary of Parameters for this timer activation. Refer to adjacentCellHandOver object hoPingpongCom bination attribute in this Dictionary of Parameters for the combinations for which this timer applies. To avoid ping-pong handovers this new timer is started after a successful handover. Up to the expiration of this timer, the receipt of HANDOVER INDICATION message is ignored. Value range : Object : Feature : Default value : Release : [0 to 60] s adjacentCellHandOver General protection against ping-pong handovers (TF821-V12). [30 sec] V12
hoPingpongTimeRejectionUTRAN Class 3
Description: Value range: Time before a new handover attempt to UMTS can be triggered 0...60 seconds (0 means immediately)
256
adjacentCellUTRAN 30s DP
hoRejectionTimeOverloadUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Note: V17 This parameters is only available for BSC 3000. Time before trying a new handover attempt toward an overloaded UMTS cell 0 ... 60 seconds (0 means immediately) bsc 30s DP
hoppingSequenceNumber Class 2
Description : Hopping sequence number used by a radio time slot which obeys frequency hopping laws. Select different HSNs for nearby cells that use the same set of frequencies. Value range : Object : Type : Checks : [0 to 63] frequencyHoppingSystem DP
[M]:
If the frequencyHoppingSystem object is referenced by a channel object (fhsRef attribute defined), the parent bsc object is unlocked and the associated bts object is locked.
257
hoSecondBestCellConfiguration Class 3
Description : Number of neighbor cells in which the BSC immediately attempts to perform a new handover when the previous handover attempt failed with return to the old channel. Giving the attribute a value greater than 2 allows the BSC to renew the handover request without waiting for a new set of radio measurements (the first attempt is included in this count). The same list of neighbor eligible cells is used to process the request (no new list is provided by the BTS). Value range : Object : Default value : Type : Release : [1 to 3] bsc 3 DP V9
hoTraffic Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Note : Whether handovers for traffic reasons at bsc level are allowed. [disabled / enabled] bsc Handover for traffic reasons (TF132 - V12) disabled DP V12 Enabling this parameter allows the related BTSs with DCU4 or DRX transceiver architecture handle handovers for traffic reasons.
hoTraffic Class 3
Description : Value range : Object : Feature : Default value : Type : Whether handovers for traffic reasons at bts level are allowed. [disabled / enabled] bts Handover for traffic reasons (TF132 - V12) enabled DP
258
Release : Note :
V12 This attribute is only available for DCU4 or DRX transceiver architecture.
hrAmrPriority Class 2
Description : This attribute defines the AMR HR priority of a TDMA. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can be modified only if the corresponding bts object instance is locked (objectMustBeLockedError). Value range : [0 to 2] Priority 0 is given to a high priority TDMA Priority 1 is given to a low priority TDMA Priority 2 disables this service on the TDMA transceiver 0 DP V14 This parameter is only available for BSC 3000.
Object : Default value : Type : Release : Note :
hrCellLoadEnd Class 3
Description : This attribute defines the cell load threshold used for AMR FR/HR decision. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the bts object instance is unlocked. Value range : Object : Default value : Type : Checks : Release : Note : [0 to 100] bts 0 DP
0570CO01 - hrCellLoadEnd <= hrCellLoadStart
259
hrCellLoadStart Class 3
Description : This attribute is used to trigger the beginning of AMR HR allocation in the cell. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the bts object instance is unlocked. In this version, this parameter has the following meaning:

Value range : Object : Default value : Type : Checks : Release : Note :
if HRCellLoadStart is equal to 0, then a FR radio channel is always allocated to the MS, if HRCellLoadStart is greater than 0, then a HR radio channel is allocated to the MS, according to its radio conditions.
[0 to 100] bts 100 DP
0570CO01 - hrCellLoadEnd <= hrCellLoadStart
hrPowerControlTargetMode Class 3
Description : This attribute defines the target codec mode for AMR HR power control. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the powerControl object instance is unlocked. Value range : Object : Default value : Type : [HR 7.4 / HR 6.7 / HR 5.9 / HR4.75] powerControl HR 7.4 DP
260
Release : Note :
hrPowerControlTargetModeDl Class 3
Description : Value range : Object : Type : Feature : Default value : Notes : Release : Downlink AMR codec target used to define the downlink power control threshold for HR AMR calls. [HR 7.4 / HR 6.7 / HR 5.9 / HR 4.75] PowerControl DP Tx power offset for signalling channels HR 7.4 This parameter applies to BSC 3000 V16 and higher. V16
hsaPcmList Class 3
Description : Note : List of pcmCircuit object instances connected to a HSA. The class is 3 since some new pcmCircuits may be connected without stopping the HSA. Moreover, for a given port, the pcmCircuit may be replaced provided that the old and new pcmCircuits are in the locked administrative State. The complete pcmCircuit list is always given. This attribute is monitored by the Manager. Value changes are notified to the Manager. This attribute can be modified only if the bsc object instance is unlocked. This attribute is relevant for BSC 3000 optical and TCU 3000 optical. This attribute has the following characteristics: pcmInstance, virtualPortNumber (not a physical port since it is multiplexed in the optical fiber but it has the same idea as the portNumber in lsaRc) Value range : Object : Feature : Type : [0 .. 83] iom, hsaRc, hsaRcTcu AR 1209 - V13.1 DP
261
Checks :
[C/M]: HsaRc under Bsc not possible for a non existing referenced PcmCircuit. [C/M]: HsaRc under Transcoder not possible for a non existing referenced PcmCircuit. [C/M]: HsaRc under Bsc not possible if a referenced pcmCircuit is already referenced by another HsaRc. [C/M]: HsaRc under Transcoder not possible if a referenced pcmCircuit is already referenced by another HsaRc. [C/M]: Creation/Modification HsaRc under Transcoder is not possible for referenced PcmCircuit different than Ate r, A, A_Lb or Lb types. [C/M]: A HSA under Transcoder module of E1 type handles 21 PCMs. The Ater referenced PcmCircuit are connected to port 0 through port 4 and the A, A _Lb and Lb referenced PcmCircuits are connected to port 5 through port 20. [C/M]: A HSA under Transcoder module of T1 type handles 28 PCMs. The Ater referenced PcmCircuit are connected to port 0 through port 5 and the A, A _Lb and Lb referenced PcmCircuits are connected to port 6 through port 27. [D]: Not possible to delete a PcmCircuit under bsc, still referenced to a HsaRc. [D]: Not possible to delete a PcmCircuit under transcoder, still referenced to a HsaRc. [C/M]: LsaRc under Bsc not possible with two referenced PcmCircuits on the same port number. [C/M]: HsaRc under Transcoder not possible with two referenced PcmCircuits on the same port number. [C/M]: HsaRc not possible for shelf position and slot position already used. [C/M]: L=HsaRc under Transcoder not possible for an A referenced PcmCircuit which is not defined under the same transcoder. [C/M]: HsaRc under Transcoder not possible for an A referenced PcmCircuit with a port number equal to 0, 1, 2 or 3. [C/M]: HsaRc under Transcoder is not possible for referenced PcmCircuit different than Ater or A type. [C/M]: The association between Pcm and port of LsaRc is incorrect.
Release :
V17
262
hsaRc
Description : Value range : Object : Type : The High Speed Access Resource Complex module, which provides the optical interface for the OC3/STM1 interfaces. [0 to 2147483646] hsaRc DP
I
identifier
Description : Name of a BSS software application followed by its version number. Refer to the executableSoftware entry related to the software object in the Dictionary where the name formats are explained. Value range : Object : Type : [XXXabcdef] software - Display markers DD
identifier
Description : Name of a BSC database configuration file followed by its version number. Refer to the executableSoftware entry related to the software object in the Dictionary where the name formats are explained. Value range : Object : Type : [BSxabvcdefgh] software-bsc - Display markers DD
identifier
Description : Name of a BSC database configuration file followed by its version number. Refer to the eft entry related to the software object in the Dictionary where the name formats are explained. Value range : Object : Type : [BSxabvcdefgh] software-bsc - Display markers DD
263
identifier
Description : Value range : Object : Type : Identifier of a short message. It allows MSs to identify the short message and discard it if already received. [0 to 65535] short message DD
iem
Description : Value range : Object : Type : Note : The Interface Electronic Module, is part of the LSA RC (Low Speed Access Resource Complex) module. [0 to 2147483646] iem DP It is possible for this parameter to take on an infinite value.
iemId
Description :
If so, it the time will not expire and there will be no automatic logout procedure.
Identifier of the iem object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000. [0 to 2147483646] iem DP V13
iMSIAttachDetach Class 2
Description : Whether MS attachment/detachment is allowed. Allowing enables the system to take into account temporary MS absence to prevent unsuccessful call attempts. [allowed / not allowed] bts allowed DP
264
in
Description : The Interface Node, which provides the network connectivity through PCM trunk or higher speed interfaces (OC-3 - Optical Carrier level 3 - or STM-1 - Synchronous Transport level 1) as well as the time switching capability. [0 to 0] interfaceNode DP
inactivity timeout
Description : Value range : Object : Type : Remark : Maximum time between two user commands, over which the system induces an automatic logout procedure. [2 to 2147483646] (5) minute user profile DP Moving the mouse inside an MMI window on the terminal screen resets the counter.
inclusive interval of codano

Description : To select messages according to their fault number. The filtering list can contain one (or several) interval(s). For example, interval 5~8 enables to retrieve fault numbers 15, 6, 7, and 8. Do not fill in if this criterion is not to be selected. Value range : Object : Type : Release : [0 to 65535 - 0 to 65535] Alarm and notification logs - Filter DP V12
inclusive list of codano

Description : To select messages according to their fault number. The filter can contain one (or several) fault number(s). Do not fill in if this criterion is not to be selected. Value range : Object : [0 to 65535] Alarm and notification logs - Filter
265
Type : Release :
DP V12
incomingHandOver Class 3
Description : Value range : Object : Default value : Type : Whether incoming handovers are allowed in a cell. [enabled / disabled] handOverControl enabled DP
inhibitRequest
Description : Value range : Object : Type : Checks : Remark : Whether the SS7 channel is inhibited. [true / false] signallingLink - Set inhibit DP
[M]:
The parent bsc object and the signallingLink object are unlocked.
An inhibit request may have no immediate effect and can even be refused. Run a Display all command on the signallingLink object to display the resource state of the SS7 channel and check that the system has applied the request (signallingLinkResState).
inId
Description : Identifier of an in object class. This identifier is allocated by the MD-R at object creation. The only value allocated by the MD-R is 0. This attribute cannot be modified. [0 to 0] interfaceNode DP V13
initialMCSDL Class 3
Description : Initial MCS in the DL direction.. It is selected by the PCU for the initial DL-LA-CommandedMCS. Note the backhaul constraints can reduce the MCS. MCS2 (value of 0 or 2), MCS3 = 3, MCS5 = 5, MCS6 = 6, MCS7 = 7, MCS8 = 8, MCS9 = 9 transceiver
266
Feature : Default value : Type : Release : Note :
EDGE traffic management (20231) MCS2 DP V15 MCS5 is the recommended value. If a cell with a low radio quality is experiencing a high BLER in MCS5, it is then recommended to use MCS2 or MCS3.
initialMCSUL Class 3
Description : Initial MCS in the UL direction. It is selected by the PCU for the initial UL-LA-CommandedMCS. Note the backhaul constraints will reduce the MCS. Value range : Object : Feature : Default value : Type : Release : MCS2 (value of 0 or 2), MCS3 = 3, MCS5 = 5, MCS6 = 6, MCS7 = 7, MCS8 = 8, MCS9 = 9 transceiver EDGE traffic management (20231) MCS2 DP V15
interBscDirectedRetry Class 3
Description : Value range : Object : Default value : Type : Release : Note : Whether inter-bss directed retry handovers are allowed in a BSS. [allowed / not allowed] bsc allowed DP V9 Queuing must also be activated at BSC level.
interBscDirectedRetryFromCell Class 3
Description : Value range : Object : Default value : Type : Whether inter-bss directed retry handovers are allowed in a cell. [allowed / not allowed] bts allowed DP
267
Release : Note :
V9 Queueing must also be activated at BSC level.
interCellHOExtPriority Class 3
Description : Index in the allocPriorityTable defines the processing priority of incoming inter-bss handovers in a cell. This priority is used when radio resource allocation queueing is not requested by the MSC or not authorized in the BSS (refer to the "bscQueueingOption" entry in the Dictionary). Value range : Object : Default value : Type : [0 to 17] bts 17 DP
interCellHOIntPriority Class 3
Description : Index in the allocPriorityTable defines the processing priority of incoming intra-bss handovers in a cell. This priority is always used, whether radio resource allocation queueing is authorized in the BSS or not. Value range : Object : Default value : Type : [0 to 17] bts 17 DP
interferenceType Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Type of interference created by neighbor cell. [notApplicable / adjacent / coChannel] adjacentCellHandOver Automatic Cell Tiering (TF995-V12) notApplicable DP V12
268
interferenceMatrixRunningOnBsc
Description : Mediation of interferenceMatrixRunning attribute.
Value range :
[yes (if at least one cell below BSC with the parameter is equal to yes / no (if no cell below BSC with the interferenceMatrixRunningOnBts parameter is equal to no] bts Switch Interference Matrix (16411) 0 DD This parameter is optional and read-only. It is applicable to BSC 3000 only. It is not present in CREATE or SET commands. This flag is displayed at the OMC-R using the Get command.
Object : Feature : Default value : Type : Note :
Checks :
[C/M]:
This parameter checks the callDrop Activation and DistributionActivation parameters. The OMC-R prevents a simultaneous activation of the call dropped analysis and the switch interference matrix. The IM_FREQUENCIES_MEASUREMENT TGE is prohibited on the bsc that includes at least one cell with callDropActivation parameter set to enabled. In this case, the following error message is displayed: Interference Matrix cannot be launched on a BSC performing Call Drop Analysis. This check is performed when launching the interference matrix (IM). Vice versa, when activating the dropped call analysis on a cell, a control is run at the OMC-R. If in a BSC, the interferenceMatrixRunningOnBts parameter in at least one cell is still set to yes, then the callDropActivation parameter cannot be set to enable. The OMC-R prevents a simultaneous activation of measurement distributions and the switch interference matrix. The IM_FREQUENCIES_MEASUREMENT
269
TGE is prohibited on the bts that has the distributionActivation parameter set to enabled. In this case, the following error message is displayed: Interference Matrix cannot be launched on a cell performing Measurement Distributions.
This check is performed when launching the Interference Matrix. Vice versa, when activating Measurement Distributions on a cell, the OMC-R checks for the interferenceMatrixRunningOnBts flag. If the cell is still running with interference matrix measurements, the distributionActivation parameter cannot be set to enable.
[C/M]:
Bts shall not be deleted while IM is running. Checks that interferenceMatrixRunningOnB sc is set to no prior to deleting a bts. BCCH and BSIC values shall not be changed while IM is running. If the interferenceMatrixRunningOnBts parameter is set to yes for one cell, the check prevents the setting of BCCH, BCC and NCC parameters on bts and adjacentCellHandover objects Neighboring cannot be changed while IM is running. If the interferenceMatrixRunningOnBts parameter is set to yes for one cell, the check prevents the creation or deletion of one adjacentCellHandover object.
[C/M]:
[C/M]:
interferenceMatrixRunningOnBts
Description : Value range : Mediation of interferenceMatrixRunning attribute. [notApplicable / adjacent / coChannel] [0 / 1]

Object : Feature : bts
0 interferenceMatrixOnBts is not running. 1 interferenceMatrixOnBts is running.
Switch Interference Matrix (16411)
270
Default value : Type : Note :
0 DD This parameter is optional and read-only. It is applicable to BSC 3000 only. It is not present in CREATE or SET commands. This flag is displayed at the OMC-R using the Get command.
Checks :
[C/M]:
This parameter checks the callDropActivati on and DistributionActivation parameters. The OMC-R prevents a simultaneous activation of the call dropped analysis and the switch interference matrix. The IM_FREQUENCIES_MEASUREMENT TGE is prohibited on the bsc that includes at least one cell with callDropActivation parameter set to enabled. In this case, the following error message is displayed: Interference Matrix cannot be launched on a BSC performing Call Drop Analysis. This check is performed when launching the interference matrix (IM). Vice versa, when activating the dropped call analysis on a cell, a control is run at the OMC-R. If in a BSC, the interferenceMatrixRunningOnBts parameter in at least one cell is still set to yes, then the callDropActivation parameter cannot be set to enable. The OMC-R prevents a simultaneous activation of measurement distributions and the switch interference matrix. The IM_FREQUENCIES_MEASUREMENT TGE is prohibited on the bts that has the distributionActivation parameter set to enabled. In this case, the following error message is displayed: Interference Matrix cannot be launched on a cell performing Measurement Distributions. This check is performed when launching the Interference Matrix. Vice versa, when activating Measurement Distributions on a cell, the OMC-R checks for the interferenceMatrixRunningOnBts flag. If the cell is still running with interference matrix measurements, the
271
distributionActivation parameter cannot be set to enable.
[C/M]:
Bts shall not be deleted while IM is running. Checks that interferenceMatrixRunningOnBsc is set to no prior to deleting a bts. BCCH and BSIC values shall not be changed while IM is running. If the interferenceMatrixRunningOnBts parameter is set to yes for one cell, the check prevents the setting of BCCH, BCC and NCC parameters on bts and adjacentCellHandover objects. Neighboring cannot be changed while IM is running. If the interferenceMatrixRunningOnBts parameter is set to yes for one cell, the check prevents the creation or deletion of one adjacentCellHandover object. Cannot create or delete an instance of adjace ntCellUTRAN and cannot change fDDARFCN or scramblingCode parameter values if parameter interferenceMatrixRunningOnBts is equal to yes. The purpose of this check is to forbid UTRAN neighbour cell creation or deletion or UMTS frequency plan change if Interference Matrix feature is activated on the BSC.
[C/M]:
[C/M]:
[C/M]:
interferer cancel algo usage Class 2

Description : Correlation ratio of the input signals received from the normal and diversity antennas. This ratio enables to adapt the SPU software (the interferer cancellation algorithm) to the propagation conditions. Correlation ratio = 0 means that the interferer cancellation algorithm is inactive. [0 to 100] % bts 0 DP V10
272
interOmuEtherlinkOper
Description : Operational state of the inner OMU Ethernet link. This attribute is dynamically managed by the BSS. Value changes are not notified to the manager. ISO operational state This attribute is relevant for the BSC 3000. Value range : Object : Feature : Type : Release : [disabled / enabled] controlNode AR 1209 - V13.1 DD V13
intraBscDirectedRetry Class 3
Description : Value range : Object : Default value : Type : Release : Note : Whether intra-bss directed retry handovers are allowed in a BSS. [allowed / not allowed] bsc allowed DP V9 Queueing must also be activated at BSC level.
intraBscDirectedRetryFromCell Class 3
Description : Value range : Object : Default value : Type : Release : Note : Whether intra-bss directed retry handovers are allowed in a cell. [allowed / not allowed] bts allowed DP V9 Queueing must also be activated at BSC level.
273
intraCell Class 3
Description : Value range : Whether intra-bts handovers on TCH are allowed in a cell for interference reasons or Cell Tiering reasons. [cellTieringHandover/ intraCellHandover / handoverNotAll owed]

cellTieringHandover: the intra-bts handovers are allowed for CellTiering reason intraCellHandover: the intra-bts handovers are allowed for interference reason handoverNotAllowed: the intra bts handovers are not allowed
handOverControl Automatic Cell Tiering (TF995-V12) handoverNotAllowed DP
intraCellHOIntPriority Class 3
Description : Index in the allocPriorityTable that defines the processing priority of an intra-bts handover in a cell. This priority is always used, whether radio resource allocation queueing is authorized in the BSS or not. Value range : Object : Default value : Type : [0 to 17] bts 17 DP
intraCellQueueing Class 3
Description : Whether intra-bts handover requests are queued for a cell. This parameter is significant only when queuing radio resource allocation requests is allowed in the BSS. Refer to the bscQueueingOption entry in the Dictionary. Value range : Object : Default value : Type : [enabled / disabled] bts disabled DP
274
intraCellSDCCH Class 3
Description : Value range : Object : Default value : Type : Release : Whether intra-bts handovers on SDCCH are authorized in a cell for interference reasons. [enabled / disabled] handOverControl disabled DP V8
iom
Description : Value range : Object : Type : Note : The Interface Electronic Module, is part of the HSA RC (High Speed Access Resource Complex) module. [0 to 2147483646] iom DP It is possible for this parameter to take on an infinite value.
J
job
Description : Value range : Object : Type : Checks :
If so, it the time will not expire and there will be no automatic logout procedure.
Identifier (name) of a job on the OMC-R. [case sensitive, unlimited number of characters]. The . and / characters are forbidden. job Id
[M/D]: The job is created on the OMC-R.
jobResult
Description : Identifier (name) of the associated job on the OMC-R. A results file stores the commands executed and the system responses to those commands during the associated job successive runs, beginning with the first run. Value range : Object : Type : [case sensitive] jobResult Id
275
jokerPerMainTarget Class 3
Description : Target number of joker AGPRS 16 kbit/s TSs to be assigned by both BSC and PCU to every main AGPRS 16 kbit/s TS (that is to every PDTCH linked with AGPRS). 0 to 4 transceiver EDGE traffic management (20231) 0 DP
Value range : Object : Feature : Default value : Type : Notes :
The recommended values are 2, 3 or 4, depending on operator Abis configuration (numberOfJokerDS0) and estimated EDGE TDMA throughput. Even if jokerPerMainTarget is a class 3 parameter, new values will not be immediately taken into account. The parameter will be used by BSC or PCU at the next AGPRS reconfiguration (when a TDMA_TS_STATUS message is sent from BSC to PCU) or when the PCU protection timer expires (agprsTsSharingProtection, internal timer set to 10s).
Release :
V15
L
label
Description : Label of an archive cartridge. When a label is set, all information already stored on the cartridge is lost. Value range : Object : [case sensitive, 64 characters max.] md, omc md, omc md, omc md, omc md, omc DP Display label Set label Archive Restore Display archive list.
Type :
276
language
Description : Language in which a short message is broadcasted. The information is used in the data coding scheme when the short message is broadcasted. Value range : [German / English / Italian / French / Spanish / Dutch / Swedish / Danish / Portuguese / Finnish / Norwegian / Greek / Turkish / Hungarian / Polish / unspecified / Multi Byte Character Set] short message DP
Object : Type :
lapdLink
Description : Identifier of a lapdLink object defined with regard to a bsc object. In all MMI commands, a LAPD link can be referenced by "bscName.lapdLink" where bscName is a permanent attribute of the parent bsc object that identifies it by name. Value range : Object : Type : Checks : [0 to 2147483646] lapdLink Id
[C]:
The number of LAPD links per BSC is limited to 841. Fourteen links can be assigned to the TCUs on the Ater interface or to the PCU on the Agprs interface, 147 links can be assigned to the radio sites on the Abis interface, and the remaining links can be assigned to the TRX/DRXs on the Abis interface, with two links per TRX/DRX. The software object related to the parent bsc object is created. The number of lapdLlink objects dependent on the same bsc object that use the same lapdTerminalNumber is limited to maxTeiPerLapdCh (static configuration data).
[C]: [C]:
[C]: [C/D]: [D]: If the application database of the related BSC is built, the parent bsc object is unlocked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.
277
Remark :
[D]:
No btsSiteManager, transceiverEquipment, or transcoder objects refer to the lapdLink object.
A lapdLink object has no administrativeState of its own; its operationalState depends on the administrativeState of the parent bsc object.
lapdLinkOMLRef Class 2
Description : Value range : Object : Type : Checks : Identifier of the lapdLink object with sapi = OML referenced by the btsSiteManager object. [0 to 2147483646] btsSiteManager DP
[C/M]: [C/M]: The number of objects dependent on a bsc object that refer to lapdLink objects using the same lapdTerminalNumber is limited to maxTeiPerLapdCh (static configuration data). The number of LAPD channels used by a site and the related TRX/DRXs is limited to maxLapdChPerBtsSM (static configuration data). If the lapdLink object lapdConcent ration attribute value is "enabled", the defined lapdTerminalNumber is used by no more than four btsSiteManager objects dependent on the same bsc object. If the lapdLink object lapdConcent ration attribute value is "disabled", the defined lapdTerminalNumber is not used.
[C]:
[C/M]:
[C/M]:
lapdLinkOMLRef Class 2
Description : Value range : Object : Type : Checks : Identifier of the lapdLink object with sapi = OML referenced by the transceiverEquipment object. [0 to 2147483646] transceiverEquipment DP
[C]:
The number of LAPD channels used by a site and its related TRX/DRXs is limited to maxLapdChPerBtsSM (static configuration data).
[C/M]:
278
[C/M]:
The number of btsSiteManager and transceiverEquipment objects dependent on a bsc object that refer to lapdLink objects using the same lapdTerminalNumber is limited to maxTeiPerLapdCh (static configuration data). The parent bsc object is unlocked, the parent btsSiteManager object and the transceiverEquipment object are locked.
[M]:
lapdLinkRSLRef Class 2
Description : Value range : Object : Type : Checks : Identifier of the lapdLink object with sapi = RSL referenced by the transceiverEquipment object. [0 to 2147483646] transceiverEquipment DP
[C]:
The number of LAPD channels used by a site and its related TRX/DRXs is limited to maxLapdChPerBtsSM (static configuration data).
[C/M]: [C/M]: The number of btsSiteManager and transceiverEquipment objects dependent on a bsc object that refer to lapdLink objects using the same lapdTerminalNumber is limited to maxTeiPerLapdCh (static configuration data). The parent bsc object is unlocked, the parent btsSiteManager object and the transceiverEquipment object are locked.
[M]:
lapdTerminalNumber Class 0
Description : BSC SICD port assigned to the LAPD link. For more information on the use of this parameter, refer to GSM BSS Engineering Rules, 411-9001-138. lapdTerninalNumber = 4 x number of the mother SICD4 board [0 to 9] + port number [0 to 3] lapdTerninalNumber = 8 x number of the mother SICD8 board [0 to 4] + port number [0 to 7]
279
Value range :
[0 [0 [0 [0 [0 [0
to 7] (BSC type 1) to 15] (BSC type 2) to 23] (BSC type 3) to 31] (BSC type 4) to 39] (BSC type 5) to 254] (BSC 3000)
Object : Default value : Feature : Type : Checks :
lapdLink
GPRS (SV407 - V12) DP
[C/M] :
The number of SICD ports in a BSC depends on its type, knowing that a SICD board manages four ports and a SICD8V board manages eight ports.
BSC type SICD ports
T1 8
T2 16
T3 24
T4 32
T5 40
[M] :
If the port is used by an Abis interface LAPD link, it cannot be used for TCU and PCU signaling. If the port is used by an Ater interface LAPD link, it cannot be used for BTS and PCU signaling. If the port is used by an Agprs interface LAPD link, it cannot be used for BTS and TCU signaling. The number of btsSiteManager and transceiverEquipment objects dependent on a bsc object that refer to lapdLink objects using the same lapdTerminalNumber is limited to maxTeiPerLapdCh (static configuration data).
[M] :
[M] :
[M]:
layer3MsgCyphModComp Class 1
Description : Whether the "Layer 3 message" element is used in the CYPHER MODE COMPLETE messages (Phase II compliance). [true / false] signallingPoint False
280
Type : Release :
DP V8
lcsType Class 0
Description : Value range : MS Location technical solution to use. According to the BSC version:

Object : Type : Note : Checks : DP
BSC V15: [nss based / tandem hybrid] BSC V16: [nss based / bss based]
bsc
This parameter is mandatory. It is only available for BSC 3000.
[M]:
If the value of lcsType is bss based then two signallingLinkSet instances must be created and at least one signallingLink must be created for the Lb interface signallingLinkSet(1). If the value of lcsType is nss based then only one signallingLinkSet instance must exist and be equal to 0. If the value of lcsType is tandem hybrid then only one signallingLinkSet instance must exist and be equal to 0.

Release :
[M]:
[M]:
V14
level to process
Description : Identifier of a set of SDO resultant data files. Level 1 identifies the latest set produced by the SDO machine. As many as three sets of resultant data files created from the same workstation can exist in the SDO machine. Any one can be selected for report display or purge purposes. Value range : Object : Type : Checks : [1, 2, 3] Call monitoring - Display/Management) (SDO) DP
[A]:
The set of files exists in the SDO machine.
281
Licenses needed to put object in service

Description : Number of licenses required to Build BDA on the bsc object or to unlock the btsSiteManager object. The parameter is equal to 0 if the BDA is already built or if the btsSiteManager object is already unlocked. Value range : Object : [0..NNNN] (The range depends on the number of licenses configured, used in total and on certain objects) md - Display RM capacity bsc - Display RM capacity btsSiteManager - Display RM capacity Feature : AMR Feature Activation Control EDGE Feature Activation Control Release : V17
Licenses used by this object

Description : Number of licenses (RM Capacity) used by the object (bsc or btsSiteManager). The parameter is equal to 0 if the bsc object is not build or if the btsSiteManager object is locked. Value range : Object : [0..NNNN] (The range depends on the number of licenses configured, used in total and on certain objects) md - Display RM capacity bsc - Display RM capacity btsSiteManager - Display RM capacity Feature : AMR Feature Activation Control EDGE Feature Activation Control Release : V17
lightning protection Class 2

Description : Value range : Presence or absence of the optional equipment "lightning arrester" in S8000 Outdoor. [Present / Absent]
282
btsSiteManager DP V9
line
Description : Line number of the first command to run (default is 1). Every command in a command file is assigned a line number. Line no.1 corresponds to the first recorded command, line no.n corresponds to the last recorded command. Value range : Object : Type : [1 to 2147483646] commandFile - Run DP
locationAreaCode Class 3
Description : Value range : Object : Type : Checks : Code of a location area of the neighbor cell in the PLMN. [0 to 65535] adjacentCellHandOver DP
[C/M]:
Description : Value range : Object : Type : Checks : Code of a location area of the neighbor cell in the PLMN. [0 to 65535] adjacentCellReselection DP
[C/M]:
Description : Code of a location area in the PLMN. A CGI (Cell Global Identifier) is unique in a location area. It identifies a cell in the PLMN and includes four fields: cellIdentity (CI), locationAreaCode (LAC), mobileCountryCode (MCC), and mobileNetworkCode (MNC). Value range : Object : [0 to 65535] bts
283
Type : Checks :
DP
[C/M]:
locationAreaCodeUTRAN Class 3
Description: Value range: Object: Default value: Type: Release: Note: Location area code (LAC) of the UMTS neighbouring cell for HO 0...65535 adjacentCellUTRAN N.A. DP V17 This parameter is only available for BSC 3000.
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 are created in ascending numerical order each time a new mdScanner object is created. Current trace logs are created in ascending numerical order each time a new callPathTrace or traceControl object is created. A restored log is created each time a Restore command on the md object related to faults, observations, or trace data is run. Value range : Object : Type : Checks : [0 to 2147483646] log Id
(on observation and trace logs) [D]: [D]: The observation or the associated trace function is stopped. The log object describing the current alarm log cannot be deleted.
Restrictions : Notes :
The log objects are created by the OMC-R agent and can be deleted by users under certain conditions (see above). The attributes of the log objects are not managed by users.
284
logFullAction
Description : Action taken by the OMC-R agent in case of storage directory capacity threshold overflow. The value "wrap" means that messages may be purged; the value "halt" means that further messages are not saved. Refer to the capacityAlarmThreshold entry in the Dictionary. Value range : Object : Type : Note : [wrap (alarm log) / halt (observation or trace log)] log - Display DP The attributes of the log objects are not managed by users.
login command type

Description : Value range : Object : Select login and user profile [login request, server update] user profile
longTbfLossThroughput Class 3
Description : Loss of throughput for long TBF in percentage of allocated bandwidth. Prioritize normal transfer over long data transfer. [0 to 100] in % bts GPRS (SV407 - V12) 0 DP V12
longTbfSizeThreshold Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Threshold for long TBF size, in Kbytes. This parameter is used in the functionality which penalizes long TBF. [1 to 65535] bts GPRS (SV407 - V12) 100 DP V12
285
lRxLevDLH Class 3
Description : Value range : Object : Default value : Type : Signal strength threshold in BTS-to-MS direction, below which a handover may be triggered. [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB handOverControl -101 to -100 dB (GSM 900 and GSM 850) -99 to -98 dB (GSM1800/1900) DP
lRxLevDLP Class 3
Description : Value range : Object : Default value : Type : Signal strength threshold in BTS-to-MS direction, below which the power control function increases power. . [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB powerControl -95 to -94 dB DP
lRxLevULH Class 3
Description : Value range : Object : Default value : Type : Signal strength threshold in MS-to-BTS direction, below which a handover may be triggered. [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB handOverControl -101 to -100 dB (GSM 900 and GSM 850) -99 to -98 dB (GSM 1800/1900) DP
lRxLevULP Class 3
Description : Signal strength threshold in MS-to-BTS direction, below which the power control function increases power. It is lower than uRxLevULP. [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB powerControl -95 to -94 dB
286
Type :
DP
lRxQualDLH Class 3
Description : Value range : Object : Feature : Default value : Type : Bit error rate threshold in BTS-to-MS direction, above which an inter cell handover may be triggered. [less than 0.2, 0.2 to 0.4, 0.4 to 0.8, ... , 6.4 to 12.8, more than 12.8] % handOverControl Intracell handover enhancements (TF819 - V12) 1.6 to 3.2 % DP
lRxQualDLP Class 3
Description : Bit error rate threshold in BTS-to-MS direction, above which the power control function increases power. It is greater than or equal to uRxQualDLP. [less than 0.2, 0.2 to 0.4, 0.4 to 0.8, ... , 6.4 to 12.8, more than 12.8] % powerControl 0.4 to 0.8 DP
Value range : Object : Default value : Type : Checks : Note :
[C/M]: lRxQualDLP uRxQualDLP
The uRxQualDLP parameter is ignored when the BTS uses the advanced "one shot" power control algorithm.
lRxQualULH Class 3
Description : Value range : Object : Default value : Feature : Type : Bit error rate threshold in MS-to-BTS direction, above which an inter cell handover may be triggered. [less than 0.2, 0.2 to 0.4, 0.4 to 0.8, ... , 6.4 to 12.8, more than 12.8] % handOverControl 1.6 to 3.2 % Intracell handover enhancements (TF819 - V12) DP
287
lRxQualULP Class 3
Description : Bit error rate threshold in MS-to-BTS direction, above which the power control function increases power. It is greater than or equal to uRxQualULP. [less than 0.2, 0.2 to 0.4, 0.4 to 0.8, ... , 6.4 to 12.8, more than 12.8] % powerControl 0.4 to 0.8 DP
Value range : Object : Default value : Type : Checks : Note :
[C/M]: lRxQualULP uRxQualULP
The uRxQualULP parameter is ignored when the BTS uses the advanced "one shot" power control algorithm.
lsaPcmList Class 3
Description : Note : List of pcmCircuit object instances connected to a LSA. The class is 3 since some new pcmCircuits may be connected without stopping the LSA. Moreover, for a given port, the pcmCircuit may be replaced provided that the old and new pcmCircuits are in the locked administrative State. The complete pcmCircuit list is always given. This attribute is monitored by the Manager. Value changes are notified to the Manager. This attribute can be modified only if the bsc object instance is unlocked. This attribute is relevant for 3G BSC and 3G TCU. Value range : Object : Feature : Type : [0 to 167] iem, lsaRc AR 1209 - V13.1 DP
288
Checks :
[C/M]: LsaRc under Bsc not possible for a non existing referenced PcmCircuit. [C/M]: LsaRc under Transcoder not possible for a non existing referenced PcmCircuit. [C/M]: LsaRc under Bsc not possible if a referenced pcmCircuit is already referenced by another LsaRc. [C/M]: LsaRc under Transcoder not possible if a referenced pcmCircuit is already referenced by another LsaRc. [C/M]: Creation/Modification LsaRc under Transcoder is not possible for referenced PcmCircuit different than Ate r, A, A_Lb or Lb types. [C/M]: A LSA under Transcoder module of E1 type handles 21 PCMs. The Ater referenced PcmCircuit are connected to port 0 through port 4 and the A, A _Lb and Lb referenced PcmCircuits are connected to port 5 through port 20. [C/M]: A LSA under Transcoder module of T1 type handles 28 PCMs. The Ater referenced PcmCircuit are connected to port 0 through port 5 and the A, A _Lb and Lb referenced PcmCircuits are connected to port 6 through port 27. [D]: Not possible to delete a PcmCircuit under bsc, still referenced to a LsaRc. [D]: Not possible to delete a PcmCircuit under transcoder, still referenced to a LsaRc. [C/M]: LsaRc under Bsc not possible with two referenced PcmCircuits on the same port number. [C/M]: LsaRc under Transcoder not possible with two referenced PcmCircuits on the same port number. [C/M]: LsaRc not possible for shelf position and slot position already used. [C/M]: LsaRc under Transcoder not possible for an A referenced PcmCircuit which is not defined under the same transcoder. [C/M]: LsaRc under Transcoder not possible for an A referenced PcmCircuit with a port number equal to 0, 1, 2 or 3. [C/M]: LsaRc under Transcoder is not possible for referenced PcmCircuit different than Ater or A type. [C/M]: The association between Pcm and port of LsaRc is incorrect.
Release :
V13
289
lsaRc
Description : The Low Speed Access Resource Complex module, which provides the electrical interface for the DS1 (Digital Signal level 1) or PCM30 interfaces. [0 to 2147483646] lsaRc DP
lsaRcId
Description : Identifier of the lsaRc object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000. [0 to 2147483646] lsaRc DP V13
lsaRc Reference
Description : Pointer to the associated lsaRc object instance. This attribute cannot be modified. It is set at iem creation as indicated by the BSS. Value range : Object : Feature : Release : [0 to 2147483646] iem AR 1209 - V13.1 V13
M
machine name
Description : Name of the machine (terminal or server), as defined in its profile for a terminal, in which the job is run (default is the logged-in users terminal). Enter "server" for the OMC-R server console. [case sensitive] job DP
290
Checks : Note :
[C/M]:
The machine is authorized to run jobs.
Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited.
machine name
Description : Name of the machine, as defined in its profile for a terminal, in which the associated job was run ("server" identifies the OMC-R server). jobResult DD Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited.
Object : Type : Note :
mainNetworkBand Class 0
Description : Value range : Object : Type : Release : Indicates the main network band. [900/1800/850/1900] network band bsc DP V15
maio Class 2
Description : Index in the list of frequencies allotted to a radio time slot which obeys frequency hopping laws. Setting this attribute, together with the fhsRef attribute, allows the time slot to obey frequency hopping laws. This offset allows to differentiate channel objects that reference frequencyHoppingSystem objects with identical attributes (orthogonality principle). Value range : Object : Type : Checks : [0 to N-1] N is the number of frequencies ( 64) allotted to the time slot. channel DP
[C/M]:
The attribute is in the range [0 to 63].
291
[C/M]:
It is undefined if frequency hopping is not allowed for the parent bts object (btsIsHopping = "no hopping") or the channelType of the channel object is "mainBCCH", "mainBCCHCombined", or "bcchSdcch4CBCH". If the attribute is defined, the fhsRef attribute is also defined. If the attribute is defined, its value is lower than the number of frequencies defined in the mobile Allocation list (attribute of the referenced frequencyHoppingSystem object).
[C/M]: [C/M]:
managedObjectClass
Description : Value range : Object class referenced. [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 / xtp] alarmRecord, mdScanReportRecord, observationFileReady Record, stateChangeRecord, traceFileReadyRecord, traceLogRecord. DP
Object :
Type :
managedObjectInstance
Description : Object : Identification of an object in the class. alarmRecord, mdScanReportRecord, observationFileRe adyRecord, stateChangeRecord, traceFileReadyRecord, traceLogRecord. DP
Type :
manager address type

Description : Value range : Object : Type : Checks : OMC-R manager address type. [internal / external] efd - Display DP
[C/M]:
292
manager addresses
Description : Object : Type : Restrictions : Addresses of the OMC-R manager that receives the messages. They are provided by the manager. efd - Display DP
[C/M]:
managerServer
Description : Name of the active OMC-R agent server. It is provided by the OMC-R agent. This server is referred to as the "NMC" server in the Q3 names of the permanent md observation counters related to the OMC-R agent active server. Object : Type : md - Display DP
manufacturerIntervention
Description : Value range : Object : Type : Type of action associated with an alarm criterion in the manufacturer configuration. [noAlarm / critical / major / minor] alarm criteria DP
marking type
Description : Type of software to consult. Selecting "prom" allows to display the software applications loaded in PROMs in the selected BSS entity. Selecting "soft" allows to display the software applications loaded in the processors of the selected BSS entity. Value range : Object : Type : [prom / soft] software - Display markers DP
masterBtsSMId class 2
Description : Object : When its value is not empty, this parameter identifies the master BTS (for synchronization purpose). btsSiteManager
293
Value range : Type : Feature : Default value : Release : Note :
[0 to 499 or empty] DP BTS Synchronization empty V15 This parameter is optional. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
max log size

Description : Object : Type : Remark : Maximum log size expressed in bytes. log - Display DP The attributes of the log objects are not managed by the users.
maxAdjCHOARMPerBts
Description : Maximum number of neighbor cells associated with a serving cell for handover and re-selection management (static OMC-R configuration data). [32] OMC-R DS
maxBscPerNetwork
Description : Value range : Object : Type : Maximum number of BSCs handled by an OMC-R (static OMC-R configuration data). [20] OMC-R DS
maxBsTransmitPowerInnerZone Class 3
Description : Value range : Object : Feature : Default value : Maximum level of BTS transmission power in the inner zone of a dual-band cell. [2 to 51] bts GPRS (SV407 - V12) 2
294
Type : Release :
DP V12
maxBtsPerBtsSM
Description : Value range : Object : Type : Maximum number of radio cells controlled by a site (static OMC-R configuration data). [6 (BTS "conventional") / 4 (others)] OMC-R DS
maxBtsPerNetwork
Description : Value range : Object : Type : Maximum number of radio cells controlled by an OMC-R (static OMC-R configuration data). [3200] OMC-R DS
maxDnTbfP1P2Threshold Class 3
Description : Value range : Object : Feature : Default value : Release : Maximum number of downlink TBF on a P1 TDMA before selection of P2 TDMA. [1 to 32] bts GPRS (SV407 - V12) 16 V12
maxDnTbfPerTs Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Maximum number of downlink TBF per TDMA on a timeslot basis. [1 to 8] bts GPRS (SV407 - V12) 8 DP V12
295
maxDwAssign Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Note : Maximum number of Immediate Assignment messages per second. [1 to 32] blocks bts GPRS (SV407 - V12) 8 DP V12 Because no TS partitioning is implemented in GPRS V12.4 b release, the number of maximum TBF establishment cannot exceed the number of TS configured in the cell. Recommended value has to be set to the number of PDTCH configured in the cell.
maxFileSize Class 2
Description : Value range : Object : Type : Checks : Notes : Maximum size of the call path tracing data file in the BSC. [30 to 500] kbit/s callPathTrace DP
[M]:
If trace data collecting is stopped by locking the object, the BSC continues to send the current trace messages to the OMC-R agent, but no notifications are issued. If trace data collecting is stopped by locking the object or on reaching the end-of-session criterion, it is automatically restarted whenever the callPathTrace object is unlocked. For instance, if the end-of-session criterion defines a period of time that elapsed, data collecting will restart for the entire period.
maximum acknowledgment time

Description : To select messages acknowledged at that time or before. Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in if this criterion is not to be selected. Value range : Object : [<date>,<time>] Alarm logs - Filter
296
Type : Checks :
DP
[A]:
It is after minimum acknowledgment time when filled in.
maximum alarm number

Description : To select alarms with a number lower than or equal to that one. Do not fill in if this criterion is not to be selected. Value range : Object : Type : Checks : [0 to 2147483646] Alarm logs - Filter DP
[A]:
It is greater than or equal to minimum alarm number when filled in.
maximum clear time

Description : To select alarms cleared at that time or before. Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in if this criterion is not to be selected. Value range : Object : Type : Checks : [<date>,<time>] Cleared alarm log - Filter DP
[A]:
It is after minimum clear time when filled in.
maximum event time

Description : To select messages issued at that time or before. Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in if this criterion is not to be selected. Value range : Object : Type : Checks : [<date>,<time>] Alarm and notification logs - Filter DP
[A]:
It is after minimum event time when filled in.
297
maximum MD notification number

Description : To select OMC-R agent notifications with a number lower than or equal to that one. Do not fill in if this criterion is not to be selected. Value range : Object : Type : Checks : [0 to 2147483646] Alarm and notification logs - Filter DP
[A]:
It is greater than or equal to minimum MD notification number when filled in.
maximum OMC notification number

Description : To select OMC-R manager notifications with a number lower than or equal to that one. Do not fill in if this criteria is not to be selected. Value range : Object : Type : Checks : [0 to 2147483646] Alarm and notification logs - Filter DP
[A]:
It is greater than or equal to minimum OMC notification number when filled in.
maximum reception time

Description : To select messages received at that time or before. Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in if this criterion is not to be selected. Value range : Object : Type : Checks : [<date>,<time>] Alarm and notification logs - Filter DP
[A]:
It is after minimum reception time when filled in.
maxLapdChPerBtsSM
Description : Value range : Maximum number of LAPD channels used by a radio site (static OMC-R configuration data). [6]
298
Object : Type :
OMC-R DS
maxNbrConsMess
Description : Maximum number of messages stored in the BSC log files. This number is allocated by the MD-R at object creation. This attribute can be modified only if the bsc object instance is locked. [1 to 7] bscLog DP V13
maxNbOfCells Class 2
Description : Value range : Object : Type : Checks : Maximum number of radio cells controlled by a site. [1 to maxBtsPerBtsSM] btsSiteManager DP
[C/M]:
The number of cells controlled by a site is limited to maxBtsPerBtsSM (refer to this entry in the Dictionary). This number must be greater than the bts object greatest identifier created for the btsSiteManager object.
[M]:
maxNbrPDAAssig Class 2 (gprsTranscvLockExtendedConf)

Description : Maximum number of:

Polling request messages sent on PDCH after immediate assignment message has been sent on CCCH. PDAS messages on old TS when changing TS allocation before going into failure.
[1 to 10] transceiver GPRS (SV407 - V12) 5 DP V12
299
maxNbrPUDWithoutVchange Class 2 (NN0002Max) gprsTranscvLockEx tendedConf

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). [1 to 255] transceiver GPRS (SV407 - V12) 10 DP V12
Value range : Object : Feature : Default value : Type Release :
maxNbrRLCEmptyBlock Class 2 (n3101Max) (gprsTranscvLockExtend edConf)

Description : Value range : Object : Feature : Default value : Type : Release : Maximum number of USF where no data is received in the UL direction. [1 to 255] transceiver GPRS (SV407 - V12) 10 DP V12
maxNumberRetransmission Class 3
Description : Maximum number of RACH burst retransmissions allowed in a call in case of non-system response. The information is broadcast to the mobiles at regular intervals on the cell BCCH. It defines the maximum number of times a mobile can renew access requests to the BTS on RACH. Value range : Object : Default value : Type : [one / two / four / seven] bts two DP
300
maxPcmCPerBtsSM
Description : Value range : Object : Type : Maximum number of PCM links used by a radio site on the Abis interface (static OMC-R configuration data). [6] OMC-R DS
maxPcmCPerTranscd
Description : Maximum number of PCM links used by a remote transcoder on the Abis interface (static OMC-R configuration data). [4] OMC-R DS
maxRACH Class 3
Description : Broadcast of the PSI 13 message on PACCH during uplink or downlink TBF. The parameter has an MMI constraint (visibility) of GPRS only for usage. Value range : [0 to 15]

Object : Feature : Default value : Type : Notes : bts
0: disabled 1..15: enabled
Broadcast of PSI 13 (Feature 27358) 0 DP
The recommended value is 1. Only applicable for BSC 3000.
Release :
V12
maxRowCount
Description : Value range : Maximum number of information lines per table to access. "0" means accessing all data. The default value is "1000". [0 to 1000]
301
Object : Type :
Trace data display DP
maxSigLPerSigLS
Description : Value range : Object : Type : Maximum number of SS7 channels linked to a BSC (static OMC-R configuration data). 16 (BSC 3000) OMC-R DS
maxTeiPerLapdCh
Description : Maximum number of TEI addresses allotted to a LAPD terminal (static OMC-R configuration data). It defines the maximum number of LAPD links that can use the same SICD port in the BSC (lapdTerminalNumber attribute of the lapdLink objects). Value range : Object : Type : [15] OMC-R DS
maxTranscdBPerTranscd
Description : Value range : Object : Type Maximum number of transcoding boards housed in a remote transcoder (static OMC-R configuration data). [10 in a GSM 900, E-GSM, GSM-R or 1800 network 8 in a GSM 1900 network] OMC-R DS
maxTranscdPerBsc
Description : Value range : Object : Type : Maximum number of remote transcoders linked to a BSC (static OMC-R configuration data). [34 (BSC 3000) 2 (TCU3G)] OMC-R DS
302
maxUpTbfP1P2Threshold Class 3
Description : Value range : Object : Feature : Type : Default value : Release : Maximum number of uplink TBF on a P1 TDMA before selection of P2 TDMA. [1 to 32] bts GPRS (SV407 - V12) DP 16 V12
maxUpTbfPerTs Class 3
Description : Value range : Object : Feature : Type : Default value : Release : Maximum number of uplink TBF per TDMA on a timeslot basis. [1 to 8] bts GPRS (SV407 - V12) DP 8 V12
md
Description : Identifier of the md object that describes the OMC-R agent. It is enforced by the system. The md object is unique to the OMC-R. It is created when the system is started. Value range : Object : Type : [1] md Id
md notification number
Description : Value range : Object : Type : To select OMC-R agent notifications with a given number. [0 to 2147483646] Alarm and notification logs - Filter DP
303
mdArchive
Description : Whether archiving the observation messages processed is allowed. The value of this attribute is "not archived" when mdScannerType = "performance monitor" (instrument panel observation) and "archived" otherwise. Value range : Object : Type Checks : [archived / not archived] mdScanner DP
[M]:
mdConfirm
Description : Whether the observation messages processed should be acknowledged. The value of this attribute is "not confirmed" when mdScannerType = "performance monitor" (instrument panel observation) and "confirmed" otherwise. Value range : Object : Type : Checks : [confirmed (yes) / not confirmed (no)] mdScanner - Display DP
[C/M]:
mdFileName
Description : Object : Type : Note : Name of an observation file containing an elementary report. Refer to the naming rules to NTP < 07 >. mdScanReportRecord DP Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited.
mdGranularityPeriod
Description : Value range : Recovery period of the observation messages by the OMC-R agent.
[5, 10, 15] minutes.......
permanent general md
304

[15, 30, 60] minutes...... [1440] minutes... [5, 10, 15] minutes....... [1, 2, 3, 4, 5] minutes...
Fast Statistic Observation (OFS) General Statistic Observation (OGS) Diagnostic Observation (ODIAG) performance monitor (Real Time Observation (ORT)) Temporary Observation (TO)
[5, 10, 15, 30, 60] minutes........
mdScanner DP
[C/M]:
The number of temporary observations running at the same time with a 5-minute recovery period in the BSSs managed on the OMC-R is limited to 50. This attribute cannot be modified if mdScannerType = "temporary xxx". Stop the observation if necessary by deleting the concerned mdScanner object and create it back with a new observation period.
Restrictions :
[M]:
Note :
For a BSC 3000 the mdGranularityPeriod can be reduced:
5 minutes if the mdObjectList contains 1 bts max. 10 minutes if the mdObjectList contains 2 bts max. 15 minutes in all other cases
This note only applies to ODIAG observation.
mdGranularityPeriod
[5, 10, 15] minutes....... [15, 30, 60] minutes...... [15, 30, 60] minutes......
permanent general md permanent general bsc (GPO-BSC) Fast Statistic Observation (OFS)
305
[1440] minutes... [15] minutes..... [1, 2, 3, 4, 5] minutes...
General Statistic Observation (OGS) Diagnostic Observation (ODIAG) performance monitor (Instrument Panel (IPO) or Real Time Observation (ORT)) Temporary Observation (TO) mdScanReportRecord DP
[5, 10, 15, 30, 60] minutes........
Object : Type :
mdGranularityPeriod
[5, 10, 15] minutes....... [15, 30, 60] minutes...... [15, 30, 60] minutes...... [1440] minutes... [15] minutes..... [1, 2, 3, 4, 5] minutes...
permanent general md permanent general bsc (GPO-BSC) Fast Statistic Observation (OFS) General Statistic Observation (OGS) Diagnostic Observation (ODIAG) performance monitor (Instrument Panel (IPO) or Real Time Observation (ORT)) Temporary Observation (TO)
Object : Type :
[5, 10, 15, 30, 60] minutes........
observationFileReadyRecord DP
306
mdId
Description : Identifier of the md object describing the OMC-R agent. It is enforced by the system. This attribute allows users to identify the md object on the OMC-R. Value range : Object : Type : Checks : [1] md - Display DP
[M]:
mdLog
Description : Whether the observation messages processed are saved on the OMC-R agent disks. The value of this attribute is "not logged" when mdScannerType = "performance monitor" (instrument panel observation) and "logged" otherwise. Value range : Object : Type Checks : [logged / not logged] mdScanner DP
[M]:
mdObjectList
Description : Identification of the observed object. It depends on the type of the defined observation.
mdScannerType permanent general md permanent general bsc general statistic (OGS) fast statistic (OFS) performance monitor real time (ORT) temporary signallingLink*
mdObjectList md bsc bsc bsc bsc bsc bsc & signallingLink
* This type only applies to V12 BSCs.
307
mdScannerType temporary Abis Interface bts* diagnostic (ODIAG)
mdObjectList bsc & btsSiteManager & bts bsc, bts, signallingLink, hardware transcoder 3G, transcoderEqpt, pcmPort, transceiverEqpt & btsSiteManager, pcmCircuit, adjacentCell
* This type only applies to V12 BSCs.
mdObjectList
Description : Value range : Object : Type Identification of the observed object. It depends on the type of the defined observation. [1 to 66] display xxx report DP
mdObjectList
Description : Value range : Object : Type : Identification of the observed object. It depends on the type of observation defined. [1 to 66] List observation messages DP
mdScanner
Description : Identifier of an mdScanner object defined with regard to the md object. The mdScanner object class describes the OMC-R agent and BSS observations. These objects are managed by the OMC-R "Performance Management" function. Value range : Object : Type : Checks : [0 to 2147483646] mdScanner Id
(performed only when the object describes a BSS observation)
308

Remark :
[C/M/D]
: The application database of the BSC is not being built. : If the application database of the BSC is not built, temporary observations cannot be managed. : If the application database of the BSC is built, the BSS/OMC-R link is established and no audit is in-progress in the BSC.
[C/M/D]
[C/M/D]
Deleting an mdScanner object that describes a temporary observation is always possible if the observation duration has elapsed (stopTime 1= 0) and the stop TGE has been sent to the BSC.
mdScannerType
Description : Value range : The type of observation. [fast Statistic / general statistic / real Time / diagnostic / temporary interference / temporary signallingLink / temporary Abis Interface bts / permanent general md / permanent general manager] Display xxx report DP
Object : Type :
mdScannerType
Description : Value range : The type of observation. [fast Statistic / general statistic / real Time / diagnostic / temporary interference / temporary signallingLink / temporary Abis Interface bts / permanent general md / permanent general manager List observation messages DP
Object : Type :
mdScannerType
Description : Value range : The type of observation. [fast Statistic / general statistic / real Time / diagnostic / temporary interference / temporary signallingLink / temporary Abis Interface bts / permanent general md / permanent general manager] Load formulae DP
Object : Type :
309
mdScannerType
Description : Value range : The type of observation. [fast Statistic / general statistic / real Time / diagnostic / temporary interference / temporary signallingLink / temporary Abis Interface bts / permanent general md / permanent general manager / pcuSN] mdScanner DP
Object : Type : Checks : Restrictions : Notes :
[C]: [M]:
The defined observation is not running. This attribute cannot be modified.
The permanent general md observation is unique to the OMC-R. The permanent general bsc and Instrument Panel observations are unique to a BSS (V10). The OGS is unique to a BSS (V11+). The OFS is unique to a BSS (V11+). The ORT is unique to a BSS (V11+). A temporary observation of a given type or ODIAG (V11+) is unique to a BSS.
mdScannerType
Description : Value range : The type of observation. [fast Statistic / general statistic / real Time / diagnostic / temporary interference / temporary signallingLink / temporary Abis Interface bts / permanent general md / permanent general manager / pcuSN]r] report template DP
Object : Type :
mdStorageDuration
Description : Storage duration of the observation messages processed on the OMC-R agent disks. Observation messages are kept on the OMC-R agent disks for a limited period of time, provided the mdLog attribute of the associated log object is "logged". They are
310
automatically purged at regular intervals. The user must archive the observation data, for data analysis occurring after the purge time set by the static configuration. Value range : [N] hour. N is a static configuration data. Since instrument panel observation messages are not kept, N equals zero for the log objects that describe these observations. Object : Type : Restrictions : mdScanner DP
[C/M]:
mdTransferMode
Description : Value range : Object : Type : Restrictions : Service used by the OMC-R agent to transmit the observation messages processed to the OMC-R manager. [FTAM (permanent general md and bsc observations) / CMIS (others)] mdScanner - Display DP
[C/M]:
mdWarning
Description : Identifier of a mdWarning object defined with regard to the md object. The mdWarning object class describes the processing conditions of BSS alarms of "outOfRangeCounter" and "excessiveAnomalyRate" type. These objects are managed by the OMC-R "Fault Management" function. Value range : Object : Type : [0 to 2147483646] mdWarning Id
measurementProcAlgorithm Class 2
Description : Value range : Whether the new L1M interface is used. [L1MV1, L1MV2]
L1MV1: L1MV2:
the older L1M is used the newer L1M is used
311
bts L1M evolutions for advanced features support (TF1089-V12) L1MV1 DP V12
microCellCaptureTimer Class 3
Description : Value range : Time used to confirm a capture (signal strength stability) when using micro-cell Algorithm type A. Time = N multiplied by <runHandOver>. According to microCellCaptureTimer value, N values are the following:

Object : Default value : Condition : Type : Checks : 0
[0 to 249] 250 251 252 253 254 255
N = [0 to 249] N = 512 N = 1024 N = 2048 N = 4096 N = 8192 N = 16384
adjacentCellHandOver
To define if A handover algorithm is activated DP
V8
[C]:
This attribute is defined if the described neighbor cell is a micro-cell (cellType = "microType").
Release : Note:
To activate the MicroCellAlgo feature for this parameter, 1. Set the MicroCellAlgo (in the omc_services.cfg of the OMC) to A. Stop the OMC-R application and perform the "omc_configure.sh -A" command. 2. For the BSCs to take effect of the new feature activation, perform a Build-BDA on all the BSCs on this OMC-R during the next maintenance window.
312
microCellStability Class 3
Description : Value range : Object : Default value : Condition : Type : Checks : Strength Level Stability Criterion for Capture Algorithm A. [0 to 255] dB adjacentCellHandOver 10 To define if A handover algorithm is activated DP
[C]:
This attribute is defined if the described neighbor cell is a micro-cell (cellType = "microType").
Note:
To activate the MicroCellAlgo feature for this parameter, 1. Set the MicroCellAlgo (in the omc_services.cfg of the OMC) to A. Stop the OMC-R application and perform the "omc_configure.sh -A" command. 2. For the BSCs to take effect of the new feature activation, perform a Build-BDA on all the BSCs on this OMC-R during the next maintenance window.
minimum acknowledgment time

Description : Selecting messages acknowledged at that time or after. Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in criterion if not to be selected. Value range : Object : Type : Checks : [<date>,<time>] Alarm logs - Filter DP
[A]:
It is before maximum acknowledgment time when filled in.
minimum alarm number

Description : To select alarms with a number greater than or equal to that one. Do not fill in criterion if not to be selected. Value range : Object : [0 to 2147483646] Alarm logs - Filter
313
Type : Checks :
DP
[A]:
It is lower than or equal to maximum alarm number when filled in.
minimum clear time

Description : To select alarms cleared at that time or after. Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in criterion if not to be selected. Value range : Object : Type : Checks : [<date>,<time>] Cleared alarm log - Filter DP
[A]:
It is before maximum clear time when filled in.
minimum event time

Description : To select messages issued at that time or after. Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in criterion if not to be selected. Value range : Object : Type Checks : [<date>,<time>] Alarm and notification logs - Filter DP
[A]:
It is before maximum event time when filled in.
minimum MD notification number

Description : To select OMC-R agent notifications with a number greater than or equal to that one. Do not fill in criterion if not to be selected. Value range : Object : Type : Checks : [0 to 2147483646] Alarm and notification logs - Filter DP
[A]:
It is lower than or equal to maximum MD notification number when filled in.
314
minimum OMC notification number

Description : To select OMC-R manager notifications with a number greater than or equal to that one. Do not fill in criterion if not to be selected. Value range : Object : Type : Checks : [0 to 2147483646] Alarm and notification logs - Filter DP
[A]:
It is lower than or equal to maximum OMC notification number when filled in.
minimum reception time

Description : To select messages received at that time or after. Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in criterion if not to be selected. Value range : Object : Type : Checks : [<date>,<time>] Alarm and notification logs - Filter DP
[A]:
It is before maximum reception time when filled in.
minNbOfJokersPerConnectedMain Class 3
Description : Minimum number of joker AGPRS 16 kbit/s TSs per main AGPRS 16 kbit/s TS, that cannot be preempted by the Dynamic Agprs feature. [0..4] step 0.125 transceiver 0 DP EDGE Dynamic Agprs minimum of joker TS
Value range : Object : Default value : Type : Feature : Checks :
[C/M]:
minNbOfJokersPerCon nectedMain must be lower than or equal to the target number of jokers per TDMA (parameter jokerPerMainTarget)
315
[C/M]:
minNbOfJokersPerConnectedMain must be equal to 0 when EDGE is not activated on TDMA (that is when edgeDataServiceType is equal to capability is not requested)
Release : Note :
V16 This parameter is mandatory. It is only available for BSC 3000.
minNbOfTDMA Class 2
Description : Minimum number of TDMA frames working for the cell itself. The frame carrying the cell BCCH must be among them and successfully configured. Value range : Object : Default value : Type : Checks : [1 to 16] bts 1 DP
[M]:
This number is less than or equal to the number of transceiver objects (TDMA frames) created for the bts object.
minNbrGprsTs Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Minimum number of TS dedicated to GPRS in the cell. [0 to 127] bts GPRS (TF1121 - V12) 0 DP V12
minTimeQualityIntraCellHO Class 3
Description : This attribute defines the minimum time between one intracell HO and the next quality intracell HO. This attribute can only be modified if the handOverControl object instance is unlocked Value range : Object : [0 to 120] % handOverControl
316
0 DP V14 Applies to a BSC 3000 architecture only.
missDistWt Class 3
Description : Weight applied to missing Distance measurement. The missing measurement is replaced by the latest received raw measurement weighed by this corrective factor when calculating the average MS-BTS distance. The range of permitted values makes missing distance measurements not favored. Value range : Object : Default value : Type : [100 to 200] % handOverControl 110 DP
missRxLevWt Class 3
Description : Weight applied in case of missing signal strength measurement report. The missing measurement is replaced by the latest computed arithmetic average, or by the latest received raw measurement if no average value is available, weighed by this corrective factor when calculating the average signal strength in the cell. Selecting the greatest value makes missing strength measurements not favored. Value range : Object : Default value : Type : [0 to 100] % handOverControl 90 DP
317
missRxQualWt Class 3
Description : Weight applied to missing Quality measurement. The missing measurement is replaced by the latest computed arithmetic average, or by the latest received raw measurement if no average value is available, weighed by this corrective factor when calculating the average bit error rate in the radio link. The range of permitted values makes missing quality measurements not favored. Value range : Object : Default value : Type : [100 to 200] % handOverControl 110 DP
mms
Description : The Memory Mass Storage module, which holds all the private data (for OMU) and those that must be secured and still accessible in the event of an OMU failure or disk failure (for Control Node). [0 to 2147483646] mms Id
mmsId
Description : Identifier of the mms object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000. [0 to 2147483646] mms DP V 13
318
mmsUsage
Description : Indicates whether the MMS is private (i.e. associated to an OMU) ; or shared-mirrored (associated to the Control Node). This attribute cannot be modified. It is set by the MD-R at MMS creation. Value range : Object : Feature : Type : Checks: [0 (Shared) to 1 (Private)] mms AR 1209 - V13.1 DP
[M]:
The MMS disc scan can be launched only for MMS objects that have the mmsUsage parameter set to mmsUsageShared.
Release :
V13
mobileAllocation Class 2
Description : List of sixty-four frequencies allotted in the network frequency band to a radio time slot obeying frequency hopping laws. [1 to 124] (GSM 900 network), [955 to 1023] / [0 to 124] (GSM-R), [975 to 1023] / [0 to 124] (E-GSM), [512 to 885] (GSM 1800 network), [512 to 810] (GSM 1900 network), [128 to 251] (GSM 850 network), [955 / 1023] / [0 /55] (GSM-R). frequencyHoppingSystem DP
Value range :
[C/M]:
Each frequency occurs once in the list and is allotted to the parent bts object (cellAlloc ation). If the frequencyHoppingSystem object is referenced by a channel object dependent on the associated bts object, the parent bsc object is unlocked and the associated bts object is locked.
[M]:
mobileCountryCode Class 3
Description : Code of the PLMN home country. Refer to the next entry. Value range : [0 to 999]
319
adjacentCellHandOver DP
[C]:
This code is identical to the mobileCountryCo de attribute of the parent bsc object when it is defined for that object. A CGI is unique in the set including a serving cell and its neighbor cells.
[C/M]:
Description : Code of the PLMN home country. Refer to the next entry. Value range : Object : Type : Checks : [0 to 999] adjacentCellReselection DP
[C]:
[C/M]:
Description : Code of the PLMN home country. It is defined when theMSC does not manage cell global identifiers (CGI). The MSC does not manage cell global identifiers (CGI) for a GSM-R network (Group call). Refer to the next entry. Value range : Object : Condition : Condition : Type : [0 to 999] bsc For a GSM network: to define when the MSC does not manage cell global identifiers (CGI). For a GSM-R network: mandatory as the MSC does not manage cell global identifiers (CGI) for Group Call. DP
320
Description : Code of the PLMN home country. A CGI (Cell Global Identifier) is unique within a location area. It identifies a cell unambiguously in the PLMN and includes four fields: cellIdentityCode (CI), locationAreaCode (LAC), mobileCountryCode (MCC), and mobileNetworkCode (MNC). Value range : Object : Type : Checks : [0 to 999] bts DP
[C]:
[C/M]:
mobileCountryCodeUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Mobile country code (MCC) of the UMTS neighbouring cell for HO 000..999 (string) adjacentCellUTRAN NA DP
[C]:
Release: Note:
mobileNetworkCode Class 3
Description : Code of the PLMN in the country. Refer to the next entry. Value range : Object : [0 to 999] adjacentCellHandOver
321
Type : Checks :
DP
[C]:
This code is identical to the mobileNetworkCo de attribute of the parent bsc object when it is defined for that object. A CGI is unique in the set including a serving cell and its neighbor cells.
[C/M]:
Description : Code of the PLMN in the country. Refer to the next entry. Value range : Object : Type : Checks : [0 to 999] adjacentCellReselection DP
[C]:
[C/M]:
Description : Code of the PLMN in the country. It must be defined when the MSC does not manage cell global identifiers (CGI). Refer to the next entry. Value range : Object : Type : [0 to 999] bsc DP
Description : Code of the PLMN in the country. A CGI (Cell Global Identifier) is unique within a location area. It identifies a cell unambiguously in the PLMN and includes four fields: cellIdentityCode (CI), locationAreaCode (LAC), mobileCountryCode (MCC), and mobileNetworkCode (MNC). Value range : Object : Type : [0 to 999] bts DP
322
Checks :
[C]:
[C/M]:
mobileNetworkCodeUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Mobile network code (MNC) of the UMTS neighbouring cell for HO 00..999 (string) adjacentCellUTRAN N.A. DP
[C]:
Release: Note:
modeModifyMandatory Class 3
Description : Value range : Object : Default value : Type : Checks : Whether a CHANNEL MODE MODIFY message is sent to the mobile after a directed retry handover in the BSS. [used (yes) / not used (no)] bsc not used DP
[C/M]:
The attribute value can only be "used" if directed retry handovers are allowed at BSC level. Refer to the interBscDirectedRetry and intraBs cDirectedRetry entries in the Dictionary.
Release :
V9
323
monitoredObjectClass
Description : Value range : Class of the serving object for the notifications processed. Lists the possible object classes to be monitored. [bsc / signallingPoint / transcoder / pcmCircuit / xtp / lapdLink / software / bscLog / btsSiteManager / signallingLinkSet / bts / signallingLink / transceiver / powerControl / frequencyHoppingSystem / adjacentCellHandOver / adjacentCellReselection / handOverControl / transceiverEquipment / channel / transceiverZone / pcu / pcusn / lsaRc Bsc / lsaRc Tcu / hardware bsc 3G / hardware transcoder 3G / interface node / control node / cem / iem / atmRm / sw8kRm / cc / omu / mms / trm / pcmCircuit] mdWarning PM1270 - TDMA based counters DP This parameter is mandatory. It is applicable to BSC 3000 only.
Object : Feature : Type : Note :
monitoredObjectInstance
Description : Identification of a serving object in the class. They identify the object that issued the processed notifications. Enter the concerned object identification sequence. Object : Type : mdWarning DP
monitoredSpecificProblemsList
Description : List of the specific problems taken into account in the process. This parameter filters the processed notifications according to the following criteria: cause number, fault number, and processor number. Value range : Object : Type : [(cause, faultNumber) pair] mdWarning if detectionFunction = "excessiveAnomalyRa te" DP
324
month
Description : Identifies the month the observation report was created. Date format entry forms are detailed in NTP < 130 >. Value range : Object : Type : [<date>] Display busiest day of the month report DP
msBtsDistanceInterCell Class 3
Description : Value range : Object : Default value : Type : To determine whether inter-bts handovers are allowed in a cell for distance reasons. [enabled / disabled] handOverControl enabled DP
msCapWeightActive Class 2
Description : Value range : Object : Feature : Default value : Type : Release : To specify whether the Weight Fair Allocation algorithm is used or not. [yes / no] bts GPRS (SV407 - V12) yes DP V12
msLeakRate
Description : This attribute specifies the leak rate parameter for one GPRS MS with 1 TS. This value is used only once at the MS Bucket creation time on SGSN side. For GPRS, (that is, if EDGE is not activated in the cell or there is no TDMA that is EDGE capable in the cell), this value is sent to the SGSN in the FLOW-CONTROL-BVC message as the default MS Leak Rate. (60kbps is considered as soon as one EDGE TDMA is activated in the cell). [2W, 8 W, 2W + 8 W] 2W + 8W V12
Value range : Default value : Release :
325
msPowerClassToggle Class 3
Description : Value range : Object : Feature : Default value : Type : Release : MS power class which needs dedicated statistics. [2W / 8W / 2W + 8W] bts Advanced Speech Call Items 2W + 8W DP V15
msRangeMax Class 3
Description : Maximum MS-to-BTS distance beyond which a handover may be triggered. It can be set to 1 for a microcell and is less than callClearing in all cases. The attributes msRangeMax and concentAlgoIntMsRange must verify msRangeMax >= concentAlgoIntMsRange. Value range : Object : Default value : Type : Checks : [1 to 134] km (non-extended mode), [1 to 120] km (extended mode). handOverControl 34 in non-extended mode, 89 in extended mode DP
[C/M]: [C/M]:
msRangeMax < callClearing (associated bts object attribute) The maximum distance is limited to 34 km if the extended cell attribute of the associated bts object is "false". The maximum distance is 120 km if the extended cell attribute of the bts object is "true".
[C/M]:
msTxPwrMax Class 3
Description : Value range : Maximum MS transmission power in a serving cell. It is equal to msTxPwrMaxCCH in a GSM 900 network. [5 to 43, by steps of 2] dB (GSM 900, GSM-R, E-GSM, GSM 850, GSM 850 - GSM 1900 and GSM 900 - GSM 1800 networks) [0 to 36, by steps of 2] dB (GSM 1800, and GSM 1800 GSM 900 networks) [0 to 33] dB (GSM 1900, E-GSM and 1900-850, GSM 850)
326
Object : Default value : Default value : Type : Checks : Note :
bts Typical value of 33 dB for GSM 900 handhelds lds and 30 dB for GSM 1800 and 1900 handhelds DP
[C/M]:
GSM 900 networks: msTxPwrMax = msTxPwrMaxCCH
The msTxPwrMax values [displayed by the OMC-R] / [typed by the OMC-R operator] are encoded values. The corresponding maximum MS transmission powers in a serving cell are compliant to GSM Rec 05.05, that is to say:
[5 to 39] dB (GSM 900 network)
msTxPwrMax2ndBand Class 2
Description : Maximum MS transmission power in the band 1 of the dualband cell depending on the network type (BCCH is only defined in band 0). [0 to 36] for GSM 900 - GSM 1800 (gsmdcs), [5 to 43] for GSM 1800 - GSM 900 (dcsgsm), [0 to 33] for GSM 850 - GSM 1900 (gsm850pcs), [5 to 43] for GSM 1900 - GSM 850 (pcsgsm850), for all in the steps of 2 + value = 33 for GSM 850 - GSM 1900 0..43 for other standardIndicator types. bts Typical value of 33 dB for GSM 900 and GSM 850 handhelds, 30 dB for GSM 1800 and 1900 Dualband cell management (TF875 - V12) DP
Value range :
Object : Default value : Feature : Type : Checks :
[C/M]:
464C001 The attribute value must be even and located between [0 to 36] dB when the standardIndicator attribute is equal to "gsmdcs". 464C002 The attribute value must be odd and located between [5 to 43] dB when the standardIndicator attribute is equal to "dcsgsm". 464C003 The attribute value must be even and located between [0 to 33] dB when the standardIndicato r attribute is equal to "gsm850pcs".
[C/M]:
[C/M]:
327
[C/M]:
464C004 The attribute value must be odd and located between [5 to 43] dB when the standardIndicator attribute is equal to "pcsgsm850".
Note :
The msTxPwrMax values [displayed by the OMC-R] / [typed by the OMC-R operator] are encoded values. The corresponding maximum MS transmission powers in a serving cell are compliant to GSM Rec 05.05, it means:

Release :
[5 to 39] dB (GSM 900 network) [0 to 36] dB (GSM 1800 network)
V12
msTxPwrMaxCCH Class 3
Description : Maximum MS transmission power in a cell CCCH. The BSC relays the information to the mobiles in the Abis CELL MODIFY REQUEST message. Value range : [[5 to 43, by steps of 2] dB (GSM 900, GSM 850, GSM-R, and GSM 900 - GSM 1800 networks) [0 to 36, by steps of 2] dB (GSM 1800, and GSM 1800 GSM 900 networks) [0 to 33] dB (GSM 1900, 1900-850, and GSM-R networks) Object : Default value : Type Remark : bts Typical value of 33 dB for GSM 900 and GSM 850 handhelds, 30 dB for GSM 1800 and 1900 DP If the cell is used as a neighbor cell of another serving cell in the network, msTxPwrMaxCCH must be identical to the msTxPwrMaxCell power defined for the corresponding adjacentCellHandOver object (the values must be checked by users). The msTxPwrMax values [displayed by the OMC-R] / [typed by the OMC-R operator] are encoded values. The corresponding maximum MS transmission powers in a serving cell are compliant to GSM Rec 05.05, that is to say:
Note :
[5 to 39] dB (GSM 900 network)
328
msTxPwrMaxCell Class 3
Description : Maximum MS transmission power in a neighbor cell. It is equal to msTxPwrMaxCCH when the cell is declared as a serving cell on the network (the value must be checked by users). [5 to 43, by steps of 2] dB (GSM 900, GSM-R, E-GSM, GSM 850, GSM 850 - GSM 1900 and GSM 900 - GSM 1800 networks) [0 to 36, by steps of 2] dB (GSM 1800 network and GSM 1800 - GSM 900) [0 to 33, by steps of 2 + value 33] dB (GSM 1900-850 networks) Object : Default value : Type : Remark : adjacentCellHandOver Typical value of 33 dB for GSM 900 or 850 handhelds and 30 dB for GSM 1800 and 1900 handhelds DP If the cell is used as a neighbor cell of another serving cell in the network, msTxPwrMaxCell should be identical to the msTxPwrMaxCCH power defined for the corresponding adjacentCellHandOver object (the values must be checked by users).
Value range :
Notes :
The msTxPwrMax values [displayed by the OMC-R] / [typed by the OMC-R operator] are encoded values.
The corresponding maximum MS transmission powers in a serving cell are compliant to GSM Rec 05.05, that is to say:
[5 to 39] dB (GSM 900 network) [0 to 36] dB (GSM 1800 network)
multi band reporting Class 3

Description : Value range : Minimum number of cells multibanding MSs, report their radio measurements in each frequency band. [the six strongest cells / the strongest cell out band / the two strongest cells out band / the three strongest cells out band]
329

Object : Default value : Type : Release : bts
six strongest allowed cells irrespective of their frequency band the strongest allowed cell outside the current frequency band the two strongest allowed cells outside the current frequency band the three strongest allowed cells outside the current frequency band
the six strongest cells DP V10
multiple site
Description : Value range : Object : Type : Checks : Identifier of a multiple site object defined with regard to a bsc object. [0 to 65535] multiple site Id
[C]: [C/M]:
The multiple site object is not created for the parent bsc object. The btsSiteManager objects in the btsSiteManagerList list are created for the parent bsc object and are not referenced by another multiple site object. The multiple site object is created and the current btsSiteManager objects referenced in the btsSiteMan agerList list are locked.
Release : V8
[M/D]:
multipleVocoders Class 1
Description : Whether the BSC is linked to one or more MSCs using different speech coding protocols. An MSC uses either the GSM protocol or the JTC protocol. "False" means that only the GSM protocol is compatible. Value range : Object : Default value : [true / false] bsc False
330
Type : Notes :
DP
If MSC parameter MULTIPLE_VOCODER_SUP PORT,
(Table OFCVAR) is set to ON (as detailed in NTP < 455 >), then the following BSC parameters must be set to TRUE:

Release : V8
chosenChannelAsscomp chosenChannelHoReq chosenChannelHoPerf chosenChannelCompL3Info
muxNumber Class 3
Description : Value range : Object : Feature : Type : Release : pcuSN mux identification [noMux / oneMux / twoMux] pcusn GPRS (SV407 - V12) DP V12
N
n3103 Class 3
Description : Value range : Object : Default value : Feature : Type : Release : Maximum number of repetition of a PUAN (Packet Uplink Ack/Nack) message. [1 to 64] bts 5 GPRS (SV407 - V12) DP V12
n3105max Class 2 (gprsTranscvLockBtsExtendedConf)

Description : Maximum number of consecutive RLC data blocks sent by the PCU with a valid RRBP and not having been acknowledged by the MS. [1 to 64] transceiver
331
Default value : Feature : Type : Release :
4 GPRS (SV407 - V12) DP V12
nACCActivation Class 3
Description : Value range : Object : Default value : Feature : Type : Release : Note : Activation of the Network Assisted Cell Change feature. [disabled / enabled] bts disabled Network Assisted Cell Change for release 4 MS DP V16 This parameter is mandatory. It is applicable to BSC 3000 only.
nAvgl Class 3 (gprsAvgParam)

Description : Signal strength filter used for MS output power control. It specifies the "Interference signal strength filter" constant for power control. NAVG -I = 2 (k/2) with k = nAvgI. Value range : Object : Default value : Feature : Type : Release : [0 to 15] bts 0 GPRS (SV407 - V12) DP V12
nAvgT Class 3 (gprsAvgParam)

Description : Signal strength filter used for MS output power control, which specifies the "Signal strength filter period" for power control in packet transfer mode. TAVG -T = 2 (k/2) /6 with k = nAvgT. [0 to 25] bts 0 GPRS (SV407 - V12) DP
Value range : Object : Default value : Feature : Type :
332
Checks : Release :
[M]:
V12
nAvgW Class 3 (gprsAvgParam)

Description : Signal strength filter used for MS output power control, which specifies the "Signal strength filter period" for power control in packet idle mode. TAVG -W = 2 (k/2) /6 with k = nAvgW. [0 to 25] bts GPRS (SV407 - V12) DP
Value range : Object : Feature : Type : Checks : Release : Note :
[M]:
V12 Tavg_w has no impact on frequency measurements and computations done by the MS, which is always equal to the frequency of paging blocks decoding.
nbOfFramesForFER Class 3
Description : Value range : Object : Type : Checks: Number of frames taken into account for FER (Frame Erasure Rate) evaluation. Int [0 to 65535] bts DP
[C/M]
The value for nbOfFrames ForFER must not be equal to [1..249]. The purpose of this semantic check is Forbid values 1 to 249 for nbOfFramesForFER.
Feature : Default value :
Distribution on Radio measurements 0
333
Release : Note :
nbOfRepeat Class 2
Description : Maximum number of times that paging messages are repeated to mobiles that belong to the same paging sub-group. It is set to "3" in former BSS versions (static configuration parameter). The following inequality, that is not checked by the system, must be true (refer to these entries in the Dictionary): retransDuration (delayBetweenRetrans + 1) x nbOfRepeat Value range : Object : Default value : Type : Release : [0 to 22] bts 3 DP V8
nbrFreeTchBeforeAnticipation Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Attribute reserved for future use. [0] bts GPRS (SV407 - V12) 0 DP V12
334
nbrFreeTchToEndAnticipation Class 3
Description : Value range : Object : Default value : Feature : Type : Release : Attribute reserved for future use. [0] bts 0 GPRS (SV407 - V12) DP V12
nCapacityFRRequestedCodec Class 3
Description : Number of 12.2 codec mode requested to trigger a capacity handover (FR to HR). This attribute can only be modified if the handover control object instance is unlocked. Value range : Object : Default value : Type : Release : Note : [0 to 196] handOverControl 44 DP V14 This parameter is only available for BSC 3000.
nCHPosition Class2
Description : Value range : Defines the number of blocks and position of the first block for NCH. [0 block 1 block, first block 0 1 block, first block 1 1 block, first block 2 1 block, first block 3 1 block, first block 4 1 block, first block 5 1 block, first block 6 2 blocks, first block 0 2 blocks, first block 1 2 blocks, first block 2 2 blocks, first block 3 2 blocks, first block 4 2 blocks, first block 5 3 blocks, first block 0 3 blocks, first block 1 3 blocks, first block 2
335
3 blocks, first 3 blocks, first 4 blocks, first 4 blocks, first 4 blocks, first 4 blocks, first 5 blocks, first 5 blocks, first 5 blocks, first 6 blocks, first 6 blocks, first 7 blocks, first Object : Feature : Default value : Type : Release : Note : bts (GSM-R V12) 0 block DP V12
block block block block block block block block block block block block
3 4 0 1 2 3 0 1 2 0 1 0]
nCHPosition - noOfBlocksForAccessGrant relation according to channelType attribute nCHPosition 1 block, first block 0 to 6 2 blocks, first block 0 to 5 3 blocks, first block 0 to 4 4 blocks, first block 0 to 3 5 blocks, first block 0 to 2 6 blocks, first block 0 to 1 7 blocks, first block 0 1 block, first block 0 1 block, first block 1 2 blocks, first block 0 noOfBlocksFor AccessGrant >= 1 >= 2 >= 3 >= 4 >= 5 >= 6 =7 1 or 2 = 12 = 12
channelType mainBCCH
mainBCCHCombined
networkColourCode Class 3
Description : Value range : Object : Type : Color code of the mobile network. The (BCC,NCC) pair forms the cell BSIC. [0 to 7] adjacentCellHandOver DP
336
Checks :
[M]:
Each defined (baseColourCode, bCCHFrequency, networkColourCode) combination is unique in the set including a serving cell and its neighbor cells. Modification of bCCHFrequency, baseColourCode and networkColourCode is forbidden while interference matrix is running.
[M]:
networkColourCode Class 2
Description : Color code of the mobile network. It allows countries with common borders to allocate BCCs and BCCH frequencies at their own convenience in international border areas. The (BCC,NCC) pair forms the cell BSIC. The information is broadcasted on the cell SCH. The Base Station Identity Code (BSIC) is a six-bit code: bits 6-5-4 = NCC (PLMN color code), bits 3-2-1 = BCC (Base station color code). Outside border areas, the NCC bits can be used to increase the number of BCC possibilities. Value range : Object : Type : Checks : [0 to 7] bts DP
[M]:
Remark :
The NCC should not be confused with the MCC (Mobile Country Code) nor the MNC (Mobile Network Code), which are part of the CGI (Cell Global Identifier). Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited.
Note :
networkIndicator Class 1
Description : Value range : Object : Identifier of the SS7 network. [nationalReserved / national / internationalReserved / international] signallingPoint
337
Type : Checks :
DP
[C/M]:
For 3G, any value in the value range can be used.
new name
Description : Value range : Object : Type : Checks : New name to give to the short message. It is different from the current short message identifier. [0 to 255] short message - Rename DP
[A]: [A]:
It is different from the current short message identifier. It does not exist on the OMC-R.
new password 1st try

Description : Users new password to use in the next login request. It begins with a letter, contains at least one non-alphabetical character among the first eight characters, and is case sensitive. It is not displayed. [6 characters min] user profile - Change password DP
[A]:
It begins with a letter and contains one non-alphanumerical character among the first eight characters. It is at least six-character long. It is different from the N previous occurrences (N is set in static configuration data).
[A]: [A]:
new password 2nd try

Description : Second definition of the users new password that will not be validated unless it is exactly the same as new password 1st try. It is not displayed. Refer to the new password 1st try entry in the dictionary. The new password is validated when opening a new session. Value range : [case sensitive]
338
user profile - Change password DP
[A]:
It begins with a letter and contains one non-alphanumerical character among the first eight characters. It is at least six-character long. It is different from the N previous occurrences (N is set in static configuration data).
[A]: [A]:
new power control algorithm Class 3

Description : Algorithm used by the BTS to control power in a cell. The "step by step" value refers to the standard power control algorithm. The "one shot" value refers to the advanced power control algorithm. The "enhanced one shot" value refers to the advanced power algorithm used in connection with the handOverControl object rxLevHreqaveBeg attribute used in the early handover mechanism. Value range : Object : Feature : Default value : Type : Notes : [step by step / one shot / enhanced one shot] bts Fast power control at TCH assignment (TF975 - V12) one shot DP
The "enhanced one shot" attribute value can only apply to non mixed DCU4 or DRX transceiver architecture. Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited.
Release :
V9
next execution time

Description : Value range : Object : Date and time of next job run. [<date> <time>] job - Display
339
Condition : Type :
This parameter is significant and displayed only when a job run periodicity is defined. DD
nFRRequestedCodec Class 3
Description : This attribute modifies the "n" parameter in the AMR full rate "(n,p) voting" mechanism used for FR->HR handovers. This parameter is used by all AMR FR HO not only FR=>HR. This attribute can only be modified if the handOverControl object instance is unlocked. Value range : Object : Default value : Type : Release : Note : Int [0 to 196] handOverControl 24 DP V14 This parameter is only available for BSC 3000.
nHRRequestedCodec Class 3
Description : This attribute modifies the "n" parameter in the AMR half rate "(n,p) voting" mechanism used for FR->HR handovers. This parameter is used by all AMR HR HO not only FR=>HR. This attribute can only be modified if the handOverControl object instance is unlocked. Value range : Object : Default value : Type : Release : Note : Int [0 to 196] handOverControl 34 DP V14 This parameter is only available for BSC 3000.
night intervention
Description : Value range : Type of action associated with an alarm criterion in the nighttime configuration. [noAlarm / critical / major / minor]
340
Object : Type :
alarm criteria DP
noOfBlocksForAccessGrant Class 2
Description : Number of CCCH blocks not used for paging. A BCCH is combined when it shares the same radio time slot with four SDCCHs which can include a CBCH (refer to the channelType entry in the Dictionary). In that case, the attribute value is no greater than to 2 (the value must be checked by users). Refer also to the nCHPosition entry in this dictionary. Value range : [0 to 2] if the cell uses a combined BCCH, [1 to 7] otherwise. "0" means that PCH blocks are used for sending immediate assignment messages as and when needed. Object : Default value : Type : Checks : bts 2 DP
[M]:
This number is greater than zero if the channelType of one of the channel objects dependent on the bts object is "sdcch8CBCH" (refer to this entry in the Dictionary). This number is strictly greater than zero if the SysInfo 2Q and/or SysInfo 13 on extended BCCH features are activated. If Bit 9 (SI13) or Bit 10 (SI2Quater) in value of label 64 in bscDataConfig table is set, the value of NoOfBlocksForAccessGrant in the bts object cannot be set to 0.
[M]:
[M]:
noOfMultiframesBetweenPaging Class 2
Description : Number of occurrences of a paging sub-group. The greater this number, the greater the number of paging sub-groups. Value range : Object : [2 to 9] multi-frame of fifty-one frames bts
341
6 DP
notAllowedAccessClasses Class 3
Description : List of mobile access classes that are forbidden in the cell, except case of congestion. This attribute, together with the emergencyCallRestricted attribute, allows to control access to a cell according to the service classes authorized. Value range : List of mobile access class:

Object : Default value : Type : Remark : bts
[0 to 9]: user classes [11 to 15]: operator classes
Leave the field empty DP General conditions mobiles are granted access to a cell are allotted at subscription time.
notification number
Description : Value range : Object : Reference number of the associated notification [0 to 2147483646] alarmRecord, mdScanReportRecord, observationFileReadyRecord, stateChangeRecord, traceFileReadyRecord, traceLogRecord. DP
Type :
notification type
Description : This is to select messages specific to the type of notifications. Do not fill in if this criterion is not to be selected. Value range : [attributeValueChange / communicationsAlarm / environmentalAlarm / equipmentAlarm / objectCreation / objectDeletion / processingErrorAlarm / qualityOfServiceAla rm / stateChange / specific]
342
Object : Type :
Alarm and notification logs - Filter DP
numberOfJokerDS0 Class 2
Description : Value range : Object : Feature : Default value : Type : Checks : Number of jokers DS0 associated to one TDMA. The description applies to the Abis interface. [0 to 8] transceiver Data Backhaul Evolution (19174) 0 DP
[C/M]: The numberOfJokerDS0 allowed values are: [0..4] for S8000 BCF BTS model [0..6] for S8000 CBCF, S12000 and e-cell BTS models [0..8] for BTS 18000 BTS models
Checks:
[C/M]: The numberOFJokerDS0 allowed values are: [0..4] for S8000 BCF BTS model [0..6] for S8000 CBCF, S12000 and e-cell BTS models [0..8] for BTS 6000 and BTS 18000 BTS models V15 The recommended value is linked to target QoS and radio conditions. The value may be set to a non-zero value even if EDGE is not activated in corresponding TDMA. Resources will be reserved and unused in that case. However, it may help to properly configure a TDMA before activating EDGE.
Release : Note :
number of records
Description : Object : Type : Remark : Number of records. log - Display DP The attributes of the log objects are not managed by the users.
number of large reuse data channels Class 3

Description : Mean number of logical channels belonging to the larger frequency reuse pattern and used at the same time for data communications which is used for cell tiering. [-16 to +16]
Value range :
343
handOvercontrol DP V15
numberOfEnabledHDLCPorts
Description : Number of enabled HDLC ports in the TMU or IEM module. Operational State of the HDLC channels in the TMU/IEM modules. Operational State of the HDLC channels in the TMU/LSA modules. The global Operational State of the HDLC feature is given by the number of ports/channels with an individual operational state set to enabled. This attribute is dynamically managed by the BSS. It is set to NULL at iem or tmu object instance creation. Value changes are not notified to the Manager. This attribute is relevant for BSC 3000. Value range : Object : Feature : Type : Release : Note : [0 to 65535] iem, tmu AR 1209 - V13.1 DD V13 BSC 3000 V16: this parameter no more exists.
numberOfPwciSamples Class 3
Description : Minimum number of PwCI samples required to reach a reliable distribution. This attribute allows the configuration of CellTieringConfiguration at bts level. [0 to 60] handOverControl Automatic Cell Tiering (TF995-V12) 20 DP V12 CellTiering mode must be activated.
Value range : Object : Feature : Default value : Type : Release : Note :
344
numberOfSlotsSpreadTrans Class 3
Description : Number of radio time slots RACH transmission accesses are spread in a random manner to avoid collisions. The information is broadcast to the mobiles at regular intervals on the cell BCCH. In the event of non-system response, the mobile renews the RACH bursts after a randomly defined period varying with numberOfSlotsSpreadTrans. MS Phase 1
The time T between two transmissions of the same RACH burst is the following: T= [D + (N+1) x 4.615]ms where
D is the maximum system response pending time: N is the randomly number generated by the mobile in the range [0 to numberOfSlotsSpreadTrans-1] 4.615 ms is the time occupied by a time slot.
MS Phase 2
345
The time T between two transmissions of the same RACH burst is the following (whichever is the BCCH, combined or not): T= 4.615 x [S+(N + 1)] ms where
S is a parameter depending on the BCCH configuration and on the value of numberOfSlotsSpreadTrans (see table hereafter) N is the randomly number generated by the mobile in the range [0 to numberOfSlotsSpreadTrans-1] 4.615 ms is the time occupied by a time slot.
NumberOfSlotsSpreadTrans
S on not combined BCCH 55 76 109 163 217
S on co mbined BCCH 41 52 58 86 11
3, 8, 14, 50 4, 9, 16 5, 10, 20 6, 11, 25 7, 12, 32
[3 to 12 / 14 / 16 / 20 / 25 / 32 / 50] time slots bts 32
346
Type : Note :
DP The choice will depend on the quantities of GSM phase 1 and GSM phase 2 mobiles. For Mobile phase 1, numberOfSlotsSpreadTrans = 50 leads to the lower double allocation rate. For Mobile phase 2, numberOfSlotsSpreadTrans = 6, 7, 11, 12, 25, 32 (respectively 5, 10, 20) for BCCH combined (respectively BCCH not combined) leads to the lower double allocation rate. Therefore, for a network that handles a combination of both types of mobiles, numberOfSlotsSpreadTrans should be set to 32 (default value).
numberOfTCHFreeBeforeCongestion Class 3
Description : Minimum number of free TCHs triggering the beginning of the TCH congestion phase and the beginning of the traffic overload condition. [0 to 128] bts 0 DP numberOfTCHFree BeforeCongestion numberOfTCHFreeToEndCongestion
Value range : Object : Default value : Type : Checks : Release :
V9
[C/M]:
numberOfTCHFreeToEndCongestion Class 3
Description : A threshold giving the number of free TCHs, which triggers the end of TCH congestion phase and the end of the traffic overload condition (additionally, this parameter takes into account the preempted PDTCH). [0 to 128] bts 0 DP numberOfTCHFreeToEndCongestion numberOfTCHFreeBeforeCongestion
V9
[C/M]:
347
numberOfTCHQueuedBeforeCongestion Class 3
Description : Maximum number of TCH allocation requests queued which triggers the beginning of the TCH congestion phase and the beginning of the traffic overload condition. [0 to 127] bts 0 DP numberOfTCHQueuedBeforeCongestion numberOfTCHQueuedToEndCongestion
V9
[C/M]:
numberOfTCHQueuedToEndCongestion Class 3
Description : Maximum number of TCH allocation requests queued triggering the end of the TCH congestion phase and the end of the traffic overload condition. [0 to 127] bts 0 DP numberOfTCHQueuedToEndCongestion numberOfTCHQueuedBeforeCongestion
V9
[C/M]:
Number of XTP under this BSS

Description : Value range : Object : Real number of XTP created under the BSC. [0..NNNN] md - Display 4K Erlangs Information bsc - Display 4K Erlangs Information Feature : AMR Feature Activation Control EDGE Feature Activation Control Release : V17
348
nUsfExt Class 3
Description : Value range : Note : USF frequency during the second phase of the extended UL period [0..100] (1 unit = 20 ms) Even if the nUsfExt parameter value is set to 0 or 1, the period remains equal to 40ms (nUsfExt=2); 2 being the minimum parameter value for PCU. bts Extended UL TBF 0 DP V15
nwExtUtbf Class 3
Description : Value range : Object : Feature : Default value : Type : Checks : Whether the Extended UpLink TBF feature is enabled or not. [disabled / enabled] bts Extended UL TBF disabled DP
[M]:
The following flag combination is prohibited: nwExtUtbf = enabled and fullDlKa = disabled
Release :
V15
O
objectClass
Description : Value range : Q3 object class [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 / xtp]
349
Object :
alarmRecord, mdScanReportRecord, observationFileRe adyRecord, stateChangeRecord, traceFileReadyRecord, traceLogRecord. DP
Type :
objectInstance
Description : Object : Type : Scope of an alarm criteria. It covers all network objects when undefined. alarm criteria DP
object Filter List

Description : To select messages issued by one or several objects, and their subtree (optional). The object Filter List parameter includes the following components: objects and scope. Click the Modify button to enter the names of the objects to be selected. The scope enables to select the subtree of an object. Value range : objects [adjacentCellHandOver / adjacentCellReselection / 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 / xtp] Alarm and notification logs - Filter DP V12
350
objects
Description : To select messages issued by one or several objects (50 objects max.), enter the concerned object class(es). This field must be empty to select all object classes. Do not fill in if this criterion is not to be selected. If a class is selected, the user may select one or more objects created in that class. If no object is selected, all messages issued by all objects created in the class are displayed. Value range : [adjacentCellHandOver / adjacentCellReselection / alarmRecord / bsc / bscCounterList / bscMdInterface / bts / btsSiteManager / callPathTrace / channel / efd / frequencyHoppingSystem / handOverControl / lapdLink / log / md / mdScanner / mdScanReportRecord / mdWarning / network / observationFileReadyRecord / omc / pcmCircuit / pcu / pcusn / powerControl / signallingLink / signallingLinkSet / signallingPoint / software / stateChangeRecord / traceControl / traceFileReadyRecord / traceLogRecord / transceiver / transceiverEquipment / transceiverZone / transcoder / xtp] Alarm and notification logs - Filter DP
Object : Type :
objects assigned
Description : Value range : Object : Type : Remark : List of the BSSs assigned to the relay. Fill in the list with bsc object identifiers or names. [1 to 255] relay DP A BSS can be assigned to several relays at the same time.
observation type
Description : Value range : Object : Type : Release : Type of the observation. [general Statistic / fast Statistic / real Time / diagnostic] bscCounterList DP V11
351
observation type
Description : Value range : Object : Type : Release : Type of the observation. [Observation real time / Observation fast statistic / Performance monitor] report template DP V11
observed counters
Description : Object : Value range : Type : Release : List of counters (Q3 names) chosen for observation. report template [list of Q3 counter names] DP V11
observed object class

Description : Value range : Class of object the user observes. [bsc / btsSiteManager / bts / pcmCircuit / adjacentCellHand Over / transceiverZone / transceiverEquipment / omu / tmu / cc / cem / pcmPort / signallingLink / channel / omc / md / machine] report template DP V11
occupationState
Description : Determines whether the PCM TS used by the terrestrial circuit is occupied by an SS7 channel. This attribute is significant provided the xtp object is unlocked. Value range : [preempted / notPreempted]

Object : Type : xtp DD
preempted........
The terrestrial circuit is mapped on a time slot occupied by an SS7 channel on the Ater interface. The PCM time slot is available for the traffic.
notPreempted.....
352
offsetLoad Class 3
Description : Value range : Object : Feature : Default value : Type : Checks : Notes : Load offset applied by the bsc to the cell selection process. [0 to 63] dB adjacentCellHandOver Handover decision according to adjacent cell priority and load (TF716 - V12) 0 DP
[C/M]:
This attribute must be in the range [0 to 63].
When set to "0", no offset is effective. This parameter is set to "0" for the cells that do not belong to the related bsc object.
Release :
V12
offsetNeighbouringCell Class 3
Description : This attribute modifies the offset linked to the neighboring cell, used to increase the HO margin, in some specific cases This attribute can only be modified if the handOverControl object instance is unlocked Value range : Object : Default value : Type : Int [-63 to 63] dB handOverControl 2 DP The following tables show for each case, the ho margin value and the averaging windows taking account into the PBGT handover mechanism according to:

Release : Note :
the MS type-fast or slow mobile or managed by a hopping TCH the number of measurement of the serving cell compared with the normal averaging window the number of measurement of the neighboring cell compared with the normal averaging window
V14 This parameter is available for BSC 3000 V14 and V15.
O Table 1 Mobile type: SFH MS cell Meas neighborin g cell meas < < cell meas avg neighboring cell avg Ho Margin
353
< <
RxLevHreqAveBe g RxLevHreqAveBe g RxLevHreqAve
RxNCellHreqAveBeg RxNCellHreqAve RxNCellHreqAve Beg
HoMargin+offset NeighbouringCell HoMargin HoMargin+offset NeighbouringCellservingfactorOffset HoMargin-serving factorOffset
RxLevHreqAve
RxNCellHreqAve
Table 2 Mobile type: slow non SFH MS cell Meas < < neighboring cell meas < < cell meas avg RxLevHreqAveBe g RxLevHreqAveBe g RxLevHreqAve RxLevHreqAve neighboring cell avg RxNCellHreqAveBeg RxNCellHreqAve RxNCellHreqAveBeg RxNCellHreqAve Ho Margin HoMargin+hoMarginB eg HoMargin+hoMarginB eg HoMargin+offset NeighbouringCell HoMargin
Table 3 Mobile type: fast non SFH MS cell Meas neighboring cell meas cell meas avg RxLevHreqAveBeg with: neighboring cell avg RxNCellHreqAve Beg Ho Margin HoMargin
< : number of available measurements is less than the normal window, : number of available measurements is greater than the normal window.
354
offsetPriority Class 3
Description : Value range : Object : Feature : Default value : Type : Checks : Release : Note : Priority offset applied by the bsc to the cell selection process. [1 to 5] adjacentCellHandOver Handover decision according to adjacent cell priority and load (TF716 - V12) 1 DP
[C/M]:
This attribute must be in the range [1 to 5].
V12 "1" is the highest priority.
offsetPriorityUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Note: V17 This parameter is only available for BSC 3000. Priority offset applied by the bsc to the cell selection process 1...5 adjacentCellUTRAN 1 DP
oMC notification number

Description : To select OMC-R manager notifications identified by a given number. Do not fill in this criterion if not to be selected. Value range : Object : Type : [0 to 2147483646] Alarm and notification logs - Filter DP
355
omuId
Description : Identifier of the omu object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified and is relevant for BSC 3000 and TCU 3000. [0 to 2147483646] omu DP V13
on error
Description : Value range : Object : Type : Whether to stop running commands when an applicative error is detected by the system (stop). [stop / continue] commandFile - Run DP
onlyExtUtbf Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Note : Whether only Extended UpLink TBF mode is supported. [disabled / enabled] bts Extended UL TBF disabled DP V15 The recommended value is enable.
onePhaseAccess Class 2
Description : Value range : One phase access activation parameter. BSC V15: int [0 to 1] BSC V16: [disabled / enabled / edgeEnabled / gprsEdgeEnabled] bts GPRS TBF establishment improvement: one phase access (15015) disabled DP
356
Checks :
[C/M]:
Edge must be activated at cell level (egprsServices must be equal to enabled ) if onePhaseAccess is equal to edgeEnabled or gprsEdgeEnabled. Edge must be activated (edgeDataService Type must be equal to full capabilities are requested) on BCCH TDMA (TDMA having lowest priority) if onePhaseAccess is equal to edgeEnabled or gprsEdgeEnabled
[C/M]:
Notes :
"0" stands for disabled "One phase access". "1" stands for enabled "One phase access".
Release :
V15
onePhaseDnMsCapability Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Note : Default number of DL TS to be considered for MS attempting a 1 phase access. [1 to 255] bts GPRS TBF establishment improvement: one phase access (15015) 1 DP V15 Values 0 and 9 to 255 are interpreted as default value by the PCU.
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the atmRm object are as follows: administrative State {} {} {} {} {} operationalState disabled disabled disabled disabled enabled availabilityStatus notInstalled {} failed dependency {}
357
atmRm BSC/TCU e3: AR 1209 DD V13
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the bsc object are as follows: administrative State locked unlocked unlocked operational State disabled disabled disabled availability Status {} {} dependency Meaning The BSC has just been created or locked. The BSC is in restart or BDA build phase. The BSS/OMC-R link is not created or the BSC database is not built. The BSC refuses every command, including resetting. The BSS/OMC-R link and the associations with the BSC are established, and the BSC database is built.
unlocked unlocked
disabled enabled
failed {}
Object : Type :
bsc DD
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the bscMdInterface object are as follows: administrative State locked operational State disabled availability Status {} Meaning The BSS/OMC-R link has been locked by a user.
358
administrative State unlocked
operational State disabled
availability Status {}
Meaning The link has just been created and the connection is not established yet (initial state). The link is down. The connection cannot be reestablished. The connection is established.
unlocked unlocked unlocked Object : Type :
disabled disabled enabled
dependency failed {}
bscMdInterface DD
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the bts object are as follows: administrative State locked unlocked operational State disabled disabled availability Status {} dependency Meaning The cell has just been created or locked. The radio site is not working or the TDMA frames are not correctly configured. The radio site is working and the number of TDMA frames correctly configured for the cell is reached. The radio cell is being released following a soft release command.
unlocked
enabled
{}
shutting Down
enabled
busy
Object : Type :
bts DD
359
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the btsSiteManager object are as follows: administrative State locked unlocked unlocked unlocked operational State disabled disabled disabled disabled availability Status {} {} dependency failed Meaning The site has just been created or locked. Downloading in the site BCF is in-progress. The PCM link used for the site LAPD signaling is faulty. Loss of Level 3 dialogue or configuration Abis message not correctly acknowledged or downloading problem The PCM is available for LAPD signaling, the Level 3 dialogue is established, and the configuration and Abis connection with the site BCF are OK.
unlocked
enabled
{}
Object : Type :
btsSiteManager DD
operationalState
Description : Value range : ISO state. "disabled" means the BSC cannot send the messages to the OMC-R agent. [enabled / disabled] The state parameter combinations for the callPathTrace object are as follows: administrative State locked operational State enabled usageState idle Meaning Call path tracing has just started in the BSC or has been stopped by the operator.
360
operational State enabled
usageState busy
Meaning Call path tracing is in-progress and messages are forwarded to the OMC-R agent. Call path tracing is stopped (end-of-session criterion is true). Call path tracing is in-progress but messages are not forwarded to the OMC-R agent.
unlocked
enabled
idle
unlocked
disabled
Object : Type :
callPathTrace DD
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the cc object are as follows: operationalState disabled disabled disabled disabled enabled Object : Feature : Type : Release : cc BSC/TCU e3: AR 1209 DD V13 availabilityStatus notInstalled {} failed dependency online
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the cem object are as follows:
361
administrative State {} {} {} {} {} Object : Feature : Type : Release : cem
operationalState disabled disabled disabled disabled enabled
availabilityStatus notInstalled {} failed dependency {}
BSC/TCU e3: AR 1209 DD V13
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the controlNode object are as follows: administrative State {} {} {} {} Object : Feature : Type : Release : controlNode BSC/TCU e3: AR 1209 DD V13 operationalState disabled disabled disabled enabled availabilityStatus {} failed degraded online
operationalState
Description : Value range : Object : Type : ISO state [enabled / disabled] efd DD
362
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the g3BscEqp object are as follows: administrative State {} {} {} Object : Feature : Type : Release : g3BscEqp BSC/TCU e3: AR 1209 DD V13 operationalState disabled enabled disabled availabilityStatus {} {} dependency
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the g3Transcoder object are as follows: administrative State {} {} {} {} {} Object : Feature : Type : Release : operationalState disabled disabled disabled enabled enabled hardware transcoder 3G BSC/TCU e3: AR 1209 DD V13 availabilityStatus {} failed dependency degraded {}
363
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the iem object are as follows: administrative State {} {} {} {} {} Object : Feature : Type : Release : iem BSC/TCU e3: AR 1209 DD V13 operationalState disabled disabled disabled disabled enabled availabilityStatus not installed {} failed dependency {}
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the iom object are as follows: administrative State {} {} {} {} {} Object : Feature : Type : Release : iom BSC 3000 optical / TCU 3000 optical DD V17 operationalState disabled disabled disabled disabled enabled availabilityStatus not installed {} failed dependency {}
364
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the interfaceNode object are as follows: operationalState disabled disabled enabled disabled Object : Feature : Type : Release : interfaceNode BSC/TCU e3: AR 1209 DD V13 availabilityStatus dependency {} degraded {}
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the log object are as follows: operational State disabled disabled enabled availability Status {} logFull {} Meaning The disk message saving partition is full (current alarm log). The disk message saving partition is full (current observation or trace log). The messages are actually saved in the partition.
Object : Type :
log DD
365
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the lsaRc object are as follows: operationalState disabled disabled enabled disabled Object : Feature : Type : Release : lsaRc BSC/TCU e3: AR 1209 DD V13 availabilityStatus dependency {} degraded {}
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the hsaRc object are as follows: operationalState disabled disabled enabled disabled Object : Feature : Type : Release : hsaRc BSC 3000 optical DD V17 availabilityStatus dependency {} degraded {}
366
operationalState
Description : Value range : ISO state. "disabled" means the BSC cannot send the messages to the OMC-R agent. [enabled / disabled] The state parameter combinations for the mdScanner object are as follows: operational State disabled disabled enabled enabled availability Status {} {offDuty} {} {offDuty} Meaning The observation is running but the messages cannot be forwarded to the OMC-R agent. The observation is stopped and the messages cannot be forwarded to the OMC-R agent. The observation is running and the messages are forwarded to the OMC-R agent. The observation is stopped and the messages are forwarded to the OMC-R agent.
Object : Type :
mdScanner DD
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the mms object are as follows: administrative State locked Object : Feature : Type : Release : mms BSC/TCU e3: AR 1209 DD V13 operationalState {} availabilityStatus {}
367
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the omu object are as follows: administrative State locked Object : Feature : Type : Release : omu BSC/TCU e3: AR 1209 DD V13 operationalState {} availabilityStatus {}
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the pcmCircuit object are as follows: administrative State locked unlocked unlocked operational State disabled disabled disabled availability Status {} dependency failed Meaning The PCM has just been created or locked. The TCU is faulty (A interface PCMs). The DDTI board or the internal PCM partner is faulty, or the connection is down. The DDTI board and the internal PCM partner are working and the connection is established.
unlocked
enabled
{}
Object : Type :
pcmCircuit DD
368
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the pcu object are as follows: administrative State locked unlocked operational State disabled disabled availability Status {} dependency Meaning The PCU has just been created or locked. The Level 2 is not established or the connection with the BSC is down (external PCM). The PCU is working.
unlocked Object : Feature : Type : Release :
enabled pcu
{}
GPRS (SV407 - V12) DD V12
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the pcu object are as follows: operational State disabled disabled enabled Object : Feature : Type : availability Status {} dependency {} pcusn GPRS (SV407 - V12) DD Meaning The pcusn has just been created. The pcusn object does not work, or the PCM link does not work. The pcusn object is working.
369
Release : Note :
V12 Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited.
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the signallingLink object are as follows: administrative State locked unlocked operational State disabled disabled availability Status {} dependency Meaning The SS7 link has just been created or locked. The PCM carrying the SS7 link is faulty or there is no MTP2 message between the BSC and the MSC. The CCS7 board is faulty. The PCM and CCS7 board are working and MTP2 messages are exchanged between the BSC and the MSC.
unlocked unlocked
disabled enabled
failed {}
Object : Type :
signallingLink DD
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the sw8kRm object are as follows: administrative State {} {} {} operationalState disabled disabled disabled availabilityStatus not installed {} failed
370
administrative State {} {} Object : Feature : Type : Release : sw8kRm
operationalState disabled enabled
availabilityStatus dependency {}
BSC/TCU e3: AR 1209 DD V13
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the tmu object are as follows: administrative State locked unlocked {} {} {} {} Object : Feature : Type : Release : tmu BSC/TCU e3: AR 1209 DD V13 operationalState disabled disabled disabled disabled enabled enabled availabilityStatus not installed {} failed dependency degraded {}
operationalState
Description : Value range : ISO state. "disabled" means the BSC cannot send the messages to the OMC-R agent. [enabled / disabled] The state parameter combinations for the traceControl object are as follows:
371
administrati ve State locked
Meaning Call tracing has not started or has been stopped, and the messages are forwarded to the OMC-R agent. Call tracing has been stopped and the messages cannot be forwarded to the OMC-R agent. Call tracing is in-progress in the BSC and the messages are forwarded to the OMC-R agent. Call tracing is in-progress but the messages cannot be forwarded to the OMC-R agent.
locked
disabled
unlocked unlocked
enabled disabled
Object : Type :
traceControl DD
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the transceiver object are as follows: operational State disabled disabled availability Status dependency failed Meaning The parent cell is not working or no TRX/DRX is available for the TDMA frame. The BTS has refused the TDMA frame configuration or is using the partnered TRX/DRX for BCCH filling purposes. The parent cell is working, a TRX/DRX is available for the TDMA frame, and the BTS has accepted the TDMA frame configuration.
enabled
{}
Object : Type :
transceiver DD
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the transceiverEquip ment object are as follows:
372
administrati veState locked unlocked unlocked
operationa lState disabled disabled disabled
availability Status {} {} dependency
Meaning The TRX/DRX has just been created or locked. Downloading in the TRX/DRX is in-progress. The parent radio site or the parent cell or the PCM link partner is not working. The TRX/DRX is assigned to BCCH filling by the BTS or loss of Level 3 dialogue or Abis configuration message not correctly acknowledged or downloading problem or status regression. The parent cell is working, a PCM is available to the TRX/DRX, and the Level 3 dialogue is established. The TRX/DRX is being released following a soft release command.
unlocked
disabled
failed
unlocked
enabled
{}
shutting Down
enabled
{}
Object : Type :
transceiverEquipment DD
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the transcoder object are as follows: administrative State locked unlocked operational State disabled disabled availability Status {} dependency Meaning The TCU has just been created or locked. The SICD, RCB, TSCB, or internal PCM partner is faulty or the Level 2 is not established or the connection with the BSC is down (external PCM). The TCU is working.
unlocked
enabled
{}
373
Object : Type :
transcoder DD
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the trm object are as follows: administrative State locked unlocked {} {} {} Object : Feature : Type : Release : trm BSC/TCU e3: AR 1209 DD V13 operationalState disabled disabled disabled disabled enabled availabilityStatus not installed {} failed dependency {}
operationalState
Description : Value range : ISO state [enabled / disabled] The state parameter combinations for the xtp object are as follows: administrative State locked operational State disabled usage State idle availability Status {} Meaning The CIC has just been created or locked. The PCM link partner is faulty. The CIC is preempted.
unlocked
disabled
idle
dependency
unlocked
disabled
idle
failed
374
usage State idle
availability Status {}
Meaning The CIC is working and traffic-free. The CIC is working and traffic-busy. The CIC is being released following a soft release command.
unlocked
enabled
busy
{}
shutting Down
enabled
busy
{}
Object : Type :
xtp DD
otherServicesPriority Class 3
Description : An index in the table allocPriorityTable for a TCH allocation request (in signaling mode) whose cause is "other services". This priority is used in primo-allocations or when an SDDCH cannot be allocated for overload reasons. Value range : Object : Default value : Type : [0 to 17] bts 17 DP
output classes
Description : List of authorized output classes defining a terminal output domain. Output classes grant access to various types of data. [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 screen outside work sessions. Object : Type : terminal profile DP
Value range :
375
output classes
Description : List of authorized output classes defining a users output domain. Output classes grant access to various types of data. [OMC-R browser / alarm window / performance monitor / command file manager / security manager / SMS-CB manager / description window / job scheduler window / alarm log window / system session log window / call traces window / Unix window / notification log window / notification window / relay manager / alarm criteria] The "notification log window" class gives access to the system notification log, while the "notification window" class gives access to the user notification log. Object : Type : user profile DP
Value range :
owner
Description : Value range : Object : Type : Name of the user creating the command file on the OMC-R. [case sensitive] commandFile DP
P
packetAckTime Class 3
dwAckTime upAckTime
The deactivation value is 64 for both of them. Refer to these entries in this Dictionary. Release : V12
376
packetFlowContext Class 3
pfcArp1ConversationalCSCallProtection pfcArp1StreamingCSCallProtection pfcArp2ConversationalCSCallProtection pfcArp2StreamingCSCallProtection pfcArp3ConversationalCSCallProtection pfcArp3StreamingCSCallProtection pfcNrtRequestedDnMbrCounterThreshold pfcNrtRequestedUpMbrCounterThreshold pfcPreemptionRatioGold pfcPreemptionRatioSilver pfcRtDowngradeAllowed pfcRtRequestedDnGbrCounterThreshold pfcRtRequestedUpGbrCounterThreshold pfcT6 pfcT8 pfcTsGuaranteedBitRateDl pfcTsGuaranteedBitRateUl
Refer to these entries in this Dictionary. These attributes have no effect on the BSS if the pfcActivation parameter is disabled. Object : Feature : Type : Release : Notes : powerControl BSS Packet Flow Context DP V16
This parameter is mandatory. It is applicable to BSC 3000 only. This parameter is part of the complex packetFlowConte xt attribute.
377
packetSiStatus Class 3
Description : Value range : Object : Default value : Feature : Type : Release : Note : Activation of the System Information Status feature in the cell. [disabled / enabled] bts disabled Network Assisted Cell Change for release 4 MS DP V16 This parameter is mandatory. It is applicable to BSC 3000 only.
pagingOnCell Class 3
Description : Value range : Object : Default value : Type : Release : Enables or disables paging requests in a cell. [enabled / disabled] bts enabled DP V9
pan Class 3

Release :
panInc panDec panMax
Refer to these entries in this Dictionary. V12
panDec Class 3 (pan)

Description : Value range : Object : Feature : Default value : The MS counter N3102 is decremented by panDec each time PUAN timer expires [0 (4s), 1 (8s), 2 (12s), 3 (16s), 4 (20s), 5 (24s), 6 (28s), 7 (32s)] bts GPRS (SV407 - V12) 0
378
Type : Release : Note :
DP V12 If the MS counter equals "0", an abnormal release is performed.
panInc Class 3 (pan)

Description : The MS counter N3102 is incremented by panInc each time a PUAN message which allows the transmit window to go forward is received. [0 (4s), 1 (8s), 2 (12s), 3 (16s), 4 (20s), 5 (24s), 6 (28s), 7 (32s)] bts GPRS (SV407 - V12) 0 DP V12 If the MS counter equals "0", an abnormal release is performed.
panMax Class 3 (pan)

Description : Maximum value of the counter N3102 (used in case of block acknowledgment time out), set by the MS at each cell reselection. [0 (4s), 1 (8s), 2 (12s), 3 (16s), 4 (20s), 5 (24s), 6 (28s), 7 (32s)] bts GPRS (SV407 - V12) 0 DP V12 If the MS counter equals "0", an abnormal release is performed.
379
parameter(s)
Description : List of parameters to define when running the command file. Their generic format is $XXX, where $ identifies such a parameter and XXX is a string of uppercase, alphanumerical characters that does not contain spaces. Object : Type : commandFile DP
partialRecordCriteriaType Class 2
Description : Value range : Criterion that defines the type of partial records to generate in the BSC. [event type / numbered / timed / no partial]
event type ........
The BSC generates partial records each time a handover is successful (partialRec ordCriteriaEvent-Type = "handover"). The BSC generates partial records every <N> successful handovers (partialRecordCrit eriaNb-Event = [1 to 64]). The BSC generates partial records every <N> seconds (partialRecord-Criteria-Timer = [1 to 60]). The BSC does not generate partial records.
numbered ........
timed ............
no partial ........
If "no partial" is selected, trace data are only recorded at the end of each traced call. If the traceControl object is locked before the end of a call, all related data are lost. Object : Type : Checks : traceControl DP
[M]:
The traceControl object is locked.
A traceControl object is created in locked state. Unlock the object to start collecting trace data in the related BSC.
380
partialRecordCriteriaEventType
Description : Value range : Type : Create traceControl. Select this criterion when partialRecordCriteriaType is equal to "Event type". handover DP
partialRecordCriteriaNbEvent
Description : Value range : Type : Create traceControl. Enter the number of events when partialrecordCriteriaType is equal to "Numbered". [1 to 64] DP
partialrecordCriteriaTimer
Description : Value range : Type : This parameter should be set to "Hand over" when partialRecordCriteriaType is equal to "Event type". [1 to 60] minutes DP
particular intervention
Description : Value range : Object : Type : Type of action associated with an alarm criteria in the specific configuration. [noAlarm / critical / major / minor] alarm criteria DP
password
Description : Value range : Object : Type : Users current password as defined in the users profile. It is not displayed. [case sensitive] user profile - Change password DP
password
Description : Users password. It begins with a letter, contains at least one non-alphabetical character among the first eight characters, and is case sensitive. [6 characters min] user profile - Create/Set
381
Type : Checks :
DP
[C/M]:
The password begins with a letter and contains one non-alphanumerical character among the first eight characters. The password is at least six-character long.
[C/M]:
password duration
Description : Value range : Maximum time during which the users current password is valid. [2 to 2147483646] days When a password validity duration runs out, the password must be changed on opening the next work session. The users access to MMI commands is barred until the password is changed. Refer to the password status entry. Object : Type : Note : user profile DP It is possible for this parameter to take on an infinite value. If so, the password will not expire.
pcmCircuit
Description : Identifier of a pcmCircuit object defined with regard to a bsc object (Abis, Ater, Lb, A_Lb, or Agprs interface). When the PCM link is allotted to a site on the Abis interface, it is also identified by a reference number defined with regard to the site (pcmCircuitBtsSiteManager). Refer to the bscSitePcmList entry in the Dictionary. Value range : [0..363] Max number of pcmCircuit T1: 0..168 (BSC 3000); 0..364 (BSC 3000 Optical); 0..88 (TCU 3G) Max number of pcmCircuit E1: 0..126 (BSC 3000); 0..252 (BSC 3000 Optical); 0..66 (TCU 3G) Object : Feature : Type : pcmCircuit (Abis, Ater, Lb, A_Lb and Agprs interfaces) GPRS (SV407 - V12) Id
382
Checks :
[C]:
The number of external PCM links allotted to a BSC on the Ater interface depends on the number of TCUs linked to the BSC (one TCU uses one link). The software object related to the parent bsc object is created. If the application database of the related BSC is built, the parent bsc object is unlocked. If the application database of the related BSC is built, the pcmCircuit object is locked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command. No btsSiteManager object (Abis PCM) or transcoder object (Ater PCM) or pcu object (Agprs PCM) refers to the pcmCircuit object. No mdScanner object describing a temporary observation refers to the pcmCircuit object (no observation is running on the concerned PCM).
[C]: [C/D]: [D]: [D]:
[D]:
[D]:
pcmCircuit
Description : Identifier of a pcmCircuit object defined with regard to a transcoder object (A interface).
[0 to 3] pcmCircuit (A interface) Id
[C]:
The number of PCM links connected to a remote transcoder on the A interface is limited to maxPcmCTPerTranscd (static configuration data). The parent transcoder object is created. If the application database of the related BSC is built, the parent bsc object is unlocked. If the application database of the related BSC is built, the pcmCircuit object is locked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command. No signallingLink or xtp object refers to the pcmCircuit object.
[C]: [C/D]: [D]: [D]:
[D]:
383
pcmCircuitBsc
Description : Identifier of a PCM link (pcmCircuit object) used by a radio site defined with regard to the BSC. It is related to the number of the DDTI board to which the link is physically connected in the BSC. Refer to the bscSitePcmList entry in the Dictionary, which defines the relationship between these two attributes. Value range : Depending on the BSC type, the value range is:
Object : Type : DP
[0 to 167] for a BSC 3000
btsSiteManager
pcmCircuitBtsSiteManager
Description : Identifier of the PCM link defined with regard to the BTS. It is related to the number of the DTI or PCMI board to which the link is physically connected in the BTS. Refer to the bscSitePcmList entry in the Dictionary, which defines the relationship between these two attributes. Value range : Object : Type : [0 to 5] btsSiteManager DP
pcmCircuitId
Description : Identifier of the PCM link used by a LAPD link. Since all radio sites have a switching facility, the BSC can directly allocate the PCM link that supports a LAPD link. Value range : Object : Note : Type : [0 to 167] for BSC 3000 lapdLink This parameter is only available for the lapdLink OML object on BSC 3000. DD
pcmCircuitId Class 2
Description : Value range : Identifier of the PCM link used by an SS7 channel on the A interface, defined with regard to the TCU. [0 to 2147483646]
384
signallingLink DP
[C/M]:
The pcmCircuit object is created for the transcoder object referenced by the signallingLink object (transcoderId). If the described link is PCMA no.3, the time slot used by the SS7 channel (timeSlotNumber) is in the range [1 to 27] if the PCM link is an E1 link and in the range [1 to 20] if the PCM link is a T1 link. Since the last four time slots of that link are not mapped on the Ater interface, they are unusable (refer to the transcoderMatrix entry in the Dictionary).
[C/M]:
pcmCircuitId Class 2
Description : Value range : Object : Type : Checks : Identifier of the PCM link used by a terrestrial circuit on the A interface, defined with regard to the TCU. [0 to 2147483646] xtp DP
[C/M]:
The pcmCircuit object is created for the transcoder object referenced by the xtp object (transcoderId). If the described link is PCMA no.3, the time slot used by the terrestrial circuit (timeSlotNumber ) is in the range [1 to 27] if the PCM link is an E1 link and in the range [1 to 20] if the PCM link is a T1 link. Since the last four time slots of that link are not mapped on the Ater interface, they are unusable (refer to the transcoderMatrix entry in the Dictionary).
[C/M]:
pcmErrorCorrection Class 2
Description : Whether the bts uses the new ETF (Enhanced TRAU Frame) frame (set to "1") or the ETSI "Rec 08.60" frame (set to "0"). [0 / 1] bts PCM error correction (FM660 - V12) 1
Value range : Object : Feature : Default value :
385
Type : Checks :
DP
[C/M]
The "PCM error correction" feature is not supported anymore. This attribute cannot be set to 1 to forbid switching on the PCM error correction feature.
Release : Note :
V12 This parameter is only available for BTSs equipped with non mixed DCU4 or DRX transceiver architecture.
pcmNbr Class 2 (gprsPcuCrossConnectList)

Description : Value range : Object : Feature : Default value : Type : Release : Number of PCM links used for Agprs interface. BSC 3000: [6 to 167] pcu GPRS (SV407 - V12) None DP V12
pcmTimeSlotNumber Class 2
Description : Value range : Object : Type : Checks : Scheduled time slot of a radio site on the Abis interface. [1 to 31] if the PCM link is an E1 link [1 to 24] if the PCM link is a T1 link btsSiteManager DP
[C/M]:
The scheduled time slot is masked in the bstSiteManager object radioSiteMask, so it cannot be allotted by the BSC.
Notes :
The relation "scheduled time slot = teiBtsSiteManager + 1" is always true at BTS level. It can be false at BSC level provided a PCM switching matrix is used between the BSC and the BTS; otherwise, it is true.
Release :
V8
pcmType Class 0 (BSC 3000)

Description : Value range : Interface on which the PCM link is used. [pcmA / pcmAbis / pcmAter / pcmAgprs / pcmA_Lb / pcm_Lb]
386
pcmCircuit GPRS (SV407 - V12) DP
[M]:
If the current attribute value is pcmA, no signallingLink or xtpobject refers to that object (pcmTimeSlotNumber). If the current attribute value is pcmAbis, no btsSiteManager object refers to that object (bscSitePcmList). If the current attribute value is pcmAter, no transcoder object refers to that object (pcmCircuitId ). If the current attribute value is pcmAgprs, no pcu object refers to that object (bscPcuPcmRefList ). pcmAbis is forbidden for pcmCircuitId equals 0, 2, 4, or 6. signallingLink of Lb interface must be referenced to pcmCircuit of pcmLb or pcmA_Lb type. signallingLink of A interface must be referenced to pcmCircuit of pcmA or pcmA_Lb type.
[M]:
[M]:
[M]:
[M]: [C/M]:
[C/M]:
pcu
Description : Value range : Object : Feature : Type : Release : Identifier of a pcu object defined with regard to a bsc object. [0 to 2147483646] pcu GPRS (SV407 - V12) Id V12
387
pcuCellState
Description : From the BSC point of view, this parameter corresponds to the GPRS configuration of the cell in the PCU. This is made possible through the messages exchanged between the BSC and the PCU. [0, Not Significant; 1, GPRS: no PDTCH channels created; 2, GPRS: out of service; 3, GPRS: service OML configuring; 4, GPRS: service RSL configuring; 5, GPRS: in service; 6, GPRS: service unavailable - OML; 7, GPRS: service unavailable - Gb down; 8, GPRS: service unavailable - BVC KO] Object : Type : Release : pcu DD V16
Value range :
pcusn
Description : Value range : Object : Feature : Type : Release : Identifier of a pcusn object. [0 to 255] pcusn GPRS (SV407 - V12) Id V12
pcuSNName
Description : Reference name of a PCUSN object on the OMC-R. It begins with a letter and is case sensitive. Value range : Object : Type : [30 characters max.] pcusn DP
388
Checks : Release : Note :
[C/M]:
The name of a pcuSN is unique to the OMC-R.
V12 Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited. The valid symbols are: - letter characters: A, B, C..., Z, a, b, c..., z - digit symbols: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 - minus sign: - undescore: _
penaltyTime Class 3
Description : Timer used by an idle mobile before re-selecting a cell (C2 criterion). When a mobile places the cell on the list of strongest carriers, it starts a timer that stops after penaltyTime seconds. This timer is reset when the mobile removes the cell from the list. For the entire timer duration, the re-selection criterion (C2) is assigned a negative temporaryOffset value. Refer to the cellReselectOffset entry in the Dictionary. Value range : [20 to 640, by steps of 20] seconds. The value "640" is reserved and indicates that the temporary offset is ignored in the re-selection criterion (C2) calculation. It also changes the sign in the C2 formula. bts AR 264 20 DP V8
389
perceived severity
Description : To select messages according to the priority. The alarm processing priority provides an indication of how it is perceived that the capability of the managed object has been affected. Refer to the alarmPriority entry in the Dictionary where the priority levels are explained. Value range : [cleared / critical / indeterminate / major / minor / warning] Do not fill in if this criterion is not to be selected. Object : Type : Alarm and notification logs - Filter DP
periodicity
Description : Value range : Object : Condition : Type : Time between two runs if the job is to be periodically run. [1 to 2147483646] minute(s) job To define if it is a periodic job. DP
pfcActivation Class 2
Description : Value range : Object : Default value : Feature : Type : Release : Note : Activates the Packet Flow Context feature in the cell. [disabled / enabled] bts disabled BSS Packet Flow Context DP V16 This parameter is mandatory. It is applicable to BSC 3000 only.
pfcArp1ConversationalCSCallProtection Class 3
Description : Indicates if the real time PFCs Conversational of ARP 1 (allocation / retention priorities 1) are protected against voice preemption. This parameter is not used. [false / true] powerControl false
390
Feature : Type : Note : Release :
BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
pfcArp1StreamingCSCallProtection Class 3
Description : Indicates if the real time PFCs Streaming of ARP 1 (allocation / retention priorities 1) are protected against voice preemption. [false / true] powerControl false BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. This parameter is part of the complex packetFlowContext attribute. V16
Value range : Object : Default value : Feature : Type : Note : Note : Release :
Description : Indicates if the real time PFCs Conversational of ARP 2 (allocation / retention priorities 2) are protected against voice preemption. This parameter is not used. [false / true] powerControl false BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
Value range : Object : Default value : Feature : Type : Note : Release :
Description : Indicates if the real time PFCs Streaming of ARP 2 (allocation / retention priorities 2) are protected against voice preemption. [false / true]
Value range :
391
Object : Default value : Feature : Type : Note : Release :
powerControl false BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
Description : Indicates if the real time PFCs Conversational of ARP 3 (allocation / retention priorities 3) are protected against voice preemption. This parameter is not used. [false / true] powerControl false BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
Description : Indicates if the real time PFCs Streaming of ARP 3 (allocation / retention priorities 3) are protected against voice preemption. This parameter is not used. [false / true] powerControl false BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
pfcFlowControlActivation Class 2
Description : Value range : Activates the flow control of the Packet Flow Context in the cell. [disabled / enabled]
392
Object : Default value : Feature : Type : Checks : Release : Note :
bts disabled BSS Packet Flow Context DP
[M]:
If pfcActivation is disabled, it is not allowed to enable pfcFlowControlActivation.
V16 This parameter is optional. It is applicable to BSC 3000 only.
pfcMinNrtBandwidthPerTs Class 3
Description : Specifies the percentage of each TS of the TDMA which is reserved for non real time PFC (including MSs with no PFC). This parameter is used for the admission control of a real time PFC. [0 to 100] % transceiver 0 BSS Packet Flow Context DP V16 This parameter is mandatory. It is applicable to BSC 3000 only. The value 0 or a very low value may result in a TBF with only NRT PFC not being allocated enough bandwidth. This results in TBF drops. The value 0 is internally converted to 1 inside the PCU. The value 100 or a very high value may result in all RT PFC being downgraded or deleted. This value is internally converted to 99 inside PCU.
Value range : Object : Default value : Feature : Type : Release : Note : Note :
Note :
pfcMinNumberOfJokersforTsGuaranteedBitRate Class 3
Description : Number of jokers that are needed to guarantee both uplink and downlink throughputs in any location of the cell. Refer to the pfcTsGuranteedBitRateUl and the pfcTsGuranteedBitRateDl entries in this dictionary. [0 to 4] 16 kbit/s PCM TS transceiver 0 BSS Packet Flow Context
Value range : Object : Default value : Feature :
393
Type : Checks :
DP
[C/M]:
pfcMinNumberOfJoker sforTsGuarante edBitRate must be lower than or equal to minNbOfJokersPerConnectedMain so that real timePFC can be accepted when dynamic Agprs is activated.
Note : Release :
This parameter is part of the complex packetFlowContext attribute. V16
pfcNrtRequestedDnMbrCounterThreshold Class 3
Description : Threshold used by the pcuPfcNrtRequestedDnMbrGTThres counter (C15267). For more information, refer to NTP <125>. [0..568] kbit/s powerControl 0 (all requests are taken into account) BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
pfcNrtRequestedUpMbrCounterThreshold Class 3
Description : Threshold used by the pcuPfcNrtRequestedUpMbrGTThres counter (C15268). For more information, refer to NTP <125>. [0..568] kbit/s powerControl 0 (all requests are taken into account) BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
394
pfcPreemptionRatioGold Class 3
Description : Defines the percentage of raw radio bandwidth a gold NRT PFC (THP1) may preempt from silver and bronze NRT PFC (THP2 or THP3 or background or MS without PFC support) [0.00 to 93.750] by step of 0.5% powerControl 0 (no preemption) DP V14 (renamed in V16) The value may be decreased to lower the impact on Silver and Bronze subscribers when the traffic is high.
pfcPreemptionRatioSilver Class 3
Description : Defines the percentage of raw radio bandwidth a silver NRT PFC (THP2) may preempt from bronze NRT PFC (THP3 or background or MS without PFC support) [0.00 to 93.750] by step of 0.5% powerControl 0 (no preemption) DP V14 (renamed in V16) The value may be decreased to lower the impact on Bronze subscribers when the traffic is high.
pfcRtDowngradeAllowed Class 3
Description : In case the guaranteed bit rate of a real time PFC cannot be granted, this parameter indicates whether the PFC is deleted or downgraded into a non real time PFC. If it is downgraded into a non real time PFC, the parameter specifies which traffic class and PFC are used for the downgrade. [downgrade not allowed / downgrade to interactive THP1 / downgrade to interactive THP2 / downgrade to interactive THP3 / downgrade to background] powerControl downgrade not allowed BSS Packet Flow Context DP
Value range :
Object : Default value : Feature : Type :
395
Note : Release :
pfcRtRequestedDnGbrCounterThreshold Class 3
Description : Threshold used by the pcuPfcRtRequestedDnGbrGTThres counter (C15265). For more information, refer to NTP <125>. [0..568] kbit/s powerControl 0 (all requests are taken into account) BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
pfcRtRequestedUpGbrCounterThreshold Class 3
Description : Threshold used by the pcuPfcRtRequestedUpGbrGTThres counter (C15266). For more information, refer to NTP <125>. [0..568] kbit/s powerControl 0 (all requests are taken into account) BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
pfcT6 Class 3
Description : Value range : Object : Default value : Feature : Type : pfcT6 is the guard timer for the Download Packet Flow Context procedure. [0.1 to 10] seconds by step of 0.1 second powerControl 0 BSS Packet Flow Context DP
396
Note : Release :
pfcT8 Class 3
Description : Value range : Object : Default value : Feature : Type : Note : Release : pfcT8 is the guard timer for the Modify Packet Flow Context procedure. [0.1 to 10] seconds by step of 0.1 second powerControl 0 BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
pfcTsGuaranteedBitRateDl Class 3
Description : Object : Default value : Feature : Type : Note : Release : For an EDGE MS, specifies the downlink throughput which is guaranteed in any location of the cell. powerControl 0 BSS Packet Flow Context DP This parameter is part of the complex packetFlowContext attribute. V16
pfcTsGuaranteedBitRateUl Class 3
Description : Value range : Object : Default value : Feature : Type : For an EDGE MS, specifies the uplink throughput which is guaranteed in any location of the cell. [1 to 60] kbit/s powerControl 0 BSS Packet Flow Context DP
397
Note : Release :
plmnPermitted Class 3
Description : List of NCC of the PLMNs on which MSs are allowed to take measurements for handovers. Listening to the PLMN to which the cell belongs must be authorized. [0 to 7] bts
DP
pODType
Description : Value range : Object : Type : Type of the BSC or BTS involved, as defined in the Physical Objects Dictionary. [ BTSoutdoor / BTSindoor / BTSmicro / BTSsmart ] alarm criteria DP
pointCode Class 1
Description : Value range : MSC identifier in the SS7 network (Destination Point Code).

DP
in ETSI SS7 protocol [0 to 16383] in ANSI SS7 protocol [0 to 16777215]
Object : Type :
signallingLinkSet
pointCode Class 1
Description : Value range : BSC identifier in the SS7 network (Origin Point Code).

DP
in ETSI SS7 protocol [0 to 16383] in ANSI SS7 protocol [0 to 16777215]
Object : Type :
signallingPoint
398
port Ethernet operational

Description : Operational state of the OMU external Ethernet port. ISO operational state (enabled/disabled). This attribute is dynamically managed by the BSS. Value changes are not notified to the Manager. This attribute is relevant for BSC 3000. Value range : Object : Feature : Type : Release : [enabled/disabled] omu AR 1209 - V13.1 DD V13
port Ethernet status

Description : Availability status of the OMU module external Ethernet port. ISO availability status ({}, {dependency}, {failed}). This attribute is dynamically managed by the BSS. Value changes are not notified to the Manager. This attribute is relevant for BSC 3000. Value range : Object : Feature : Type : Release : [{} / {dependency} / {failed}] omu AR 1209 - V13.1 DD V13
port 0 X25 status

Description : Operational state of the OMU module external X.25 port 0. ISO operational state (enabled/disabled). This attribute is dynamically managed by the BSS. Value changes are not notified to the Manager. This attribute is relevant for BSC 3000. Value range : [{} / {dependency} / {failed}]
399
omu AR 1209 - V13.1 DD V13
port 1 X25 status

Description : Availability status of the OMU external X.25 port 1. ISO availability status ({}, {dependency}, {failed}). This attribute is dynamically managed by the BSS. Value changes are not notified to the Manager. This attribute is relevant for BSC 3000. Value range : Object : Feature : Type : Release : [{} / {dependency} / {failed}] omu AR 1209 - V13.1 DD V13
portChosen Class 2
Description : Value range : Number of the port currently used on the OMC-R end. [port0 / port1 / automaticChoice (selection by the OMC-R agent)] If the port is not uniquely selected, it will be dynamically assigned by the OMC-R agent. Selecting "automaticChoice" is recommended since it allows the OMC-R agent to reconfigure the port currently used when a problem occurs. Object : Type : Checks : bscMdInterface DP
[M] :
The bscMdInterface object is locked.
400
portUsed
Description : Value range : Number of the port currently used on the OMC-R end. [port0 / port1] This dynamic attribute identifies the OMC-R port currently used. It can be different from portChosen since the OMC-R agent switches the transport connection with a BSC over to the other port as and when needed. No information is displayed unless the BSS/OMC-R link is established. Object : Type : bscMdInterface DI
positionInShelf
Description : Value range : Object : Feature : Type : Release : Indicates the position of a module in a shelf. [1 to 15] atmRm, cc, cem, iem, lsaRc, mms, omu, sw8kRm, tmu, trm, hsaRc, hsaRcTcu, iom AR 1209 - V13.1 DD V13
powerBudgetInterCell Class 3
Description : Value range : Object : Default value : Type : Authorization to perform intercell handovers for power budget. [enabled / disabled] handOverControl enabled DP
powerClass
Description : Value range : Transmission power class of a TDMA frame. [powerClass5 (GSM 900 network, GSM-R network, E-GSM, GSM 850 - GSM 1900 and GSM 900 - GSM 1800 network) powerClass1 (GSM 1800 network, GSM 1900 network, GSM 1800 - GSM 900 network and GSM 1900 - GSM 850)] transceiver
Object :
401
Default value : Type : Checks :
powerClass1 DP
[C]:
The attribute value complies with the type of network in which the TDMA frame is used. Refer to the standardIndicator entry in the Dictionary (attribute of the parent bts object). This attribute cannot be modified.
Restrictions :
[M]:
powerControl
Description : Identifier of a powerControl object that defines the power control management parameters in a cell. A bts object may reference one and only one object of this type. [0 to 2147483646] powerControl Id
[C]:
The associated bts object is created and the powerControl object is not created for that object. If the application database of the related BSC is built, the parent bsc object is unlocked and the associated bts object is locked. The parent bsc object is unlocked. The powerControl object is created. The associated bts object is not referenced, except by an handOverControl object. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.
[C/D]:
[M]: [M/D]: [D]: [D]:
powerControlIndicator Class 3
Description : Whether MS signal strength measurements include measurements on BCCH. BCCH measurements must not be included when the following two conditions are met:
402

Value range :
The radio channel hops at least on two different frequencies, including the BCCH frequency. Power control on the downlink is used.
[include BCCH measurements / do not include BCCH measurements] This parameter should only be used with cavity coupling.
bts include BCCH measurements DP
powerIncrStepSizeUpLink Class 3
Description : Increment step size for uplink power control. This is applicable to BSC 3000 only. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the bsc object instance is unlocked. This attribute can only be modified if the bts object instance is unlocked. Value range : Object : Default value : Type : Checks : [2 to 30] dB powerControl 4 DP
0566CO01: The attribute powerIncrStepSizeUL must verify:
1RxLevULP + powerIncrStepSizeUL <= uRxLevULP Release : Note : V14 This parameter is only available for BSC 3000.
403
powerIncrStepSizeDownLink Class 3
Description : Increment step size for downlink power control. This is applicable to BSC 3000 only. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the bsc object instance is unlocked. This attribute can only be modified if the bts object instance is unlocked. Value range : Object : Default value : Type : Checks : [2 to 30] dB powerControl 4 DP
0565CO01 - The attribute powerIncrStepSizeDL must verify:
1RxLevDLP + powerIncrStepSizeDL <= uRxLevDLP Release : V14
powerRedStepSizeDownLink Class 3
Description : Decrement step size for downlink power control. This is applicable to BSC 3000 only. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the bsc object instance is unlocked. This attribute can only be modified if the bts object instance is unlocked. Value range : Object : Default value : Type : [2 to 8] dB powerControl 2 DP
404
Checks :
0567CO01 - The attribute powerRedStepSizeDL must verify:
uRxLevDLP - powerRedStepSizeDL >= 1RxLevDLP Release : Note : V14 This parameter is only available for BSC 3000.
powerRedStepSizeUpLink Class 3
Description : Decrement step size for uplink power control. This is applicable to BSC 3000 only. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the bsc object instance is unlocked. This attribute can only be modified if the bts object instance is unlocked. Value range : Object : Default value : Type : Checks : [2 to 30] dB powerControl 2 DP
0568CO01-The attribute powerRedStepSizeUL must verify:
uRxLevULP - powerRedStepSizeUL >= 1RxLevULP Release : Note : V14 This parameter is only available for BSC 3000.
preemptionAuthor Class 3
Description : Value range : Defines the preemption management [forbidden, authorizedWithRelease, authorizedForcedHO] signallingPoint forbidden ASCI (GSM-R V12) DP
Object : Default value : Feature : Type :
405
Release : Note :
V12 authorizedWithRelease and authorizedForcedHO options are not available.
preemptionConfiguration Class 3
Description : Object : Type : Release : This parameter is composed of preemptionAuthor and eMLPPThreshold. Refer to these entries in the Dictionary. signallingPoint DP V14
pRequestedCodec Class 3
Description : This attribute defines the "p" parameter in the AMR "(n,p) voting" mechanism. This attribute can only be modified if the handOverControl object instance is unlocked. Value range : Object : Default value : Type : Release : Note : Int [12 to 192] in steps of 12 handOverControl 48 DP V14 This parameter is only available for BSC 3000.
preSynchroTimingAdvance Class 3
Description : Pre-defined timing advance used in a pre-synchronized handover procedure between the serving cell and this neighbor 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 a phase 2 MS goes from the serving cell to this neighbor cell approximately at the same place (railway, highway). Value range : Object : Default value : Type : Release : [0 to 35] (km) adjacentCellHandOver Refer to parameter synchronized DP V10
406
priority Class 2
Description : Priority level of a TDMA frame. Among the set of TDMA frames attached to the cell, only the one carrying the cell BCCH must be allotted the highest priority [0]. At least <minNbOfTDMA> TDMA frames related to a cell (refer to this entry in the Dictionary) must be successfully configured for the cell to be working. They include the TDMA frame carrying the cell BCCH and those with the highest priority(ies). If this is true when the cell is brought into service, then, the cell will be working. Otherwise, its operationalState will be "disabled" and its availabilityStatus will be "{dependency}". Value range : Object : Type : Checks : [0 to 255] transceiver DP
[M]:
The parent bsc object is unlocked and the associated bts object is locked.
privateMmsOmuRef
Description : Pointer to the associated omu object instance for private MMS, NULL for shared-mirrored MMS. This attribute cannot be modified. It is set by the MD-R at MMS creation. Value range : Object : Feature : Type : Release : [0 to 2147483646] mms AR 1209 - V13.1 DP V13
privilegedCell Class 3
Description : Value range : Object : Allows to segregate cells according to their mapping on Agprs PCM. [no, yes] bts
407
Default value : Feature : Type : Release : Notes :
no Optimized Agprs cell allocation DP V16
This parameter is mandatory. It is applicable to BSC 3000 only. This parameter is of class 3. No modification of its value is taken into account by the BSC immediately and it does not trigger any re-configuration of Agprs.
probable cause
Description : To select messages according to the numerical value of the ISO probableCause field. Do not fill in if this criterion is not to be selected. The following table indicates the messages displayed according to the probable cause. Alarm type Communications Probable cause Execution failure of a MD request by the BSC Call establishment error Communication protocol error Communication subsystem failure Corrupt data Degraded signal DTE-DCE interface error LAN error Local node transmission error Loss of frame Loss of signal Receive failure Remote node transmission error Transmit failure Value 62 4 5 6 9 12 13 25 27 28 29 40 42 54
408
Alarm type Environmental
Probable cause External alarm loop Enclosure door open Fire detected Heating, ventilation, or cooling system Material supply exhausted
Value 58 14 18 21 30 60 15 21 23 24 30 35 37 40 41 49 50 52 54 55 59 61 2 7 9 17 32 39 46 47 48 49
Equipment
Equipment absent Equipment malfunction Heating, ventilation, or cooling system problem Input/output device error Input device error Material supply exhausted Power problem Processor problem Receive failure Receiver failure Storage capacity problem Temperature unacceptable Timing problem Transmit failure Transmitter failure
ProcessingError
Cause of restart or switchover No response Application subsystem failure Configuration or customization error Corrupt data File error Out of memory Queue size exceeded Software error Software program abnormally terminated Software program error Storage capacity problem
409
Alarm type
Probable cause Underlying resource unavailable Version mismatch
Value 56 57 63 8 34 39 43 44 45 51
QualityOfService
Shutdown Congestion Performance degraded Queue size exceeded Resource at or nearing capacity Response time excessive Retransmission rate excessive Threshold crossed
[1 to 150] Alarm and notification logs - Filter DP
processor identity
Description : This parameter is composed of the bsc equipment name and the equipment processor number parameters. Refer to these entries in the Dictionary. mdWarning (create) DP V11 During the command "create mdWarning", the operator can define either "equipment identity" or "processor identity", but not both.
Object : Type : Release : Note :
pwciHrequave Class 3
Description : Cell Tiering Mode parameter. This is the averaging window size for powerControl. This attribute allows to configure the cellTieringConfigura tion parameter at bts level. Note : Value range : Object : Cell Tiering mode must be activated. [0 to 16] handOverControl
410
8 DP
qsearchC Class 3
Description: The MS searches for UMTS cells if level is above or below the threshold when the serving BCCH frequency is part of the BA_List 0:"<-98 dBm" 1: < -94 dBm 2: < -90 dBm 3: < -86 dBm 4: < -82 dBm 5: < -78 dBm 6: < -74 dBm 7: always 8: > -78 dBm 9: > -74 dBm 10: > -70 dBm 11: > -66 dBm 12: > -62 dBm 13: > -58 dBm 14: > -54 dBm 15: never Object: Default value: Type: Checks: Release: Notes: V17 This parameter is available only for BSC 3000. handoverControl 15 DP "values different from "always" and "never" are useful only if serving BCCH is part of BA_List in SI5" QsearchC > -XX dBm: the HO towards the UMTS can be done only if the RxLev from the serving cell is above -XX. QsearchC < -XX dBm: the HO towards the UMTS can be done only if the RxLev from the serving cell is below -XX.
Value range:
411
R
radChanSelIntThreshold Class 3
Description : Maximum interference level on free radio channels, below which are arranged in groups of priority allocation. The information is used to allocate free channels with the lowest interference level. The levels depend on the thresholdInterference attribute value defined for the cell. Refer to this entry in the Dictionary. The BSC distributes free radio channels among two groups:
The first group contains the list of channels with a measured averaged interference level equal to or lower than the defined level. The second group contains the list of channels with a measured averaged interference level higher than the defined level, and recently released channels for which no measurement is available.
Four resource pools are defined for each SDCCH or TCH type of channel:
low interference level radio channels that are authorized to hop low interference level radio channels not authorized to hop high interference level radio channels authorized to hop high interference level radio channels not authorized to hop
412
Chapter 2 Parameters listed in alphabetical order Channels are allocated cyclically inside each pool.
[0 to 4] handOverControl 1 DP V8
radioLinkTimeOut Class 3
Description : Maximum value of the counter (S) associated with the downlink SACCH messages, beyond which the radio link is cut off. It is lower than or equal to t3109. Mobiles comply with system operating conditions when the counter (S) is assigned a value lower than or equal to t3109. If the receiver is unable to decode a downlink SACCH message (BTS-to-MS direction), the counter is decreased by 1. If the message is received, the counter is increased by 2. When the counter goes down to zero, the radio link is declared "faulty".
413
Value range : Object : Default value : Type : Checks : Notes :
[4 to 64, by steps of 4] SACCH frames (1 unit = 480 ms on TCHs, 470 ms on SDCCHs) bts 20 SACCH DP radioLinkTimeOut t3109.
[C/M]:
The rlf1 attribute serves the same goal on the uplink. The system does not check consistent values of the two attributes.
radioSiteMask Class 2
Description : Definition of the PCM time slots used by a site. TS n is masked when bit n is set to 0, it is used when bit n is set to 1 in the binary field. The radio site mask is immediately displayed in the hexadecimal field just below. The radio site mask is set using the hexadecimal field as well as the binary field. The mask defines the time slots used in each PCM link allotted to a given radio site. Time slot allocation is managed by the BSC; a time slot available on a site is used either by a radio time slot for traffic purposes or by a LAPD link which does not carry the link with the site BCF for signaling.
414
A PCM E1 link carries thirty-two time slots. TS 0 (least significant bit) is always masked since it cannot be used. The radioSiteMask of a site using E1 links is as follows:
radioSiteMask = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx0 ||||| TS31 23 15 7 TS0 A PCM T1 link carries twenty-four time slots. The radioSiteMask of a site using T1 links is as follows: radioSiteMask = XXXXXXXXXXXXXXXXXXXXXXXX || TS24 TS1 Sites that do not share PCM links are assigned the full set. In a BTS chain, the scheduled time slots of each radio site must be allotted in ascending order (TS1, TS2, TS3, etc.), beginning with the site closest to the BSC. Refer to the pcmTimeSlotNumber entry. Value range : Object : Type : Checks : [32-bit mask] btsSiteManager DP
[C/M]: [C/M]: [C/M]:
TS 0 cannot be assigned. If PCM T1 links are used, TSs 25 to 31 cannot be assigned. The radioSiteMask of all sites sharing a same PCM link (drop and insert connections) are dissociated. The scheduled time slot of the radio site (pcmTimeSlotNumber) is masked [0] since it cannot be used.
[M]:
415
radioSiteMaskOffset Class 2
Description : The radioSiteMaskOffset parameter provides the de-correlation of the radio site mask used on BTS site with the radio site mask used on BSC side (refer to the radioSiteMask entry). On BTS side, the mask is the result of a calculation using the radioSiteMask value and the radioSiteMaskOffset parameter. According to the radioSiteMaskOffset value (named s below), the radio site mask on BTS side (RSMbts) is:
s = 0: RSMbts and RSMbsc are identical s > 0: If RSMbsc is [TSm..TSn] then RSMbts is [TSm-s..TSn-s] s < 0: If RSMbsc is [TSm..TSn] then RSMbts is [TSm+|s|..TSn+|s|]
Example 1: if RSMbsc is [TS31..TS28] and s = +26, then RSMbts is [TS05..TS02]. Example 2: if RSMbsc is [TS05..TS02] and s = -19, then RSMbts is [TS24..TS21]. Value range : Object : Type : Checks : Int [-28 to 28] btsSiteManager DP
[C/M]:
If the radioSiteMaskOffset is positive, the lowest TS number of the resultant BTS radio site mask must be greater than or equal to 1. If the radioSiteMaskOffset is negative, the greatest TS number of the resultant BTS radio site mask must be lower than or equal to 31 (case of an E1 PCM) or to 24 (case of a T1 PCM). the radioSiteMaskOffset is in the range [-28, +28] (case of an E1 PCM) or in the range [-21, +21] (case of a T1 PCM).
[C/M]:
Release :
[C/M]:
V14
416
radioSiteName
Description : Reference name of a multiple site object on the OMC-R. It begins with a letter and is case sensitive. The name of a multiple site can be used in all MMI commands to reference the multiple site on the OMC-R. Value range : Object : Type : Checks : Note : [30 characters max.] multiple site DP
[C/M]:
The name of a multiple site is unique to the OMC-R.
Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited. The valid symbols are: - letter characters: A, B, C..., Z, a, b, c..., z - digit symbols: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 - minus sign: - undescore: _ - space
radResSupBusyTimer Class 3
Description : Value range : Object : Default value : Type : Release : Maximum time that SDCCH or TCH can be continuously occupied without generating an alarm. [1 to 18] hours bsc 3 DP V8
417
radResSupervision Class 3
Description : Indicates whether radio resources are controlled at the cell level (both busy resources and free resources). When no control is performed, no alarm related to the use or non use of an SDCCH or TCH is generated. Refer to the radResSupBusyTimer and radResSupFreeTimer entries in the Dictionary. Value range : Object : Default value : Type : Notes : [true / false] bts true DP
radResSupBusyTimer and radResSupFreeTimer can be set automatically by the OMC-R calendar function. The activation of this feature does not induce any signaling or CPU overload. Only the BSS-OMC-R link is overloaded at a rate of radResSupBusyTimer or radResSupFreeTimer.
Release :
V8
radResSupFreeTimer Class 3
Description : Value range : Object : Default value : Type : Release : Maximum time an SDCCH or TCH can be continuously free without generating an alarm. [1 to 18] hours bsc 18 DP V8
range
Description : Value range : Object : Time period chosen over which the counter values are read. [5 min / 15 min / 30 min / 60 min / 2 hours] report template
418
Notes :
The authorized values for OFS observation type are 60 min, 2 hours, 6 hours, 12 hours, and 24 hours. The authorized values for ORT and Performance Monitor observation types are 5 min, 15 min, 30 min, 60 min, and 2 hours.
Type :
DP
reception time
Description : To select messages received at that time. Absolute time format entry forms are detailed in NTP < 130 >. Do not fill in if this criterion is not to be selected. Value range : Object : Type : [<date>,<time>] Alarm and notification logs - Filter DP
record reference
Description : Value range : Object : Type : Checks : Identifier of a user call as recorded in a call monitoring data file. [0 to 63] Call monitoring - Display (SDO) DP
[A]: [A]:
It is in the range [0 to 63]. This parameter is mandatory when a user call report (Events option) or a radio measurements report (Measurements option) is requested. It can be undefined when a synthesis report (Synthesis option) is requested. In that case, a summary of all user recorded calls is displayed.
[A]:
419
redundantPcmNumber
Description : Number of the redundant PCM link defined on BSC end. This dynamic attribute is displayed provided the btsSiteManager object redundantPcmPresence attribute value is "true". Value range : Object : Type : Remark : [0 to 47] btsSiteManager DD A redundant link is not normally used for traffic or signalling connections.
redundantPcmPresence Class 2
Description : Value range : Object : Type : Checks : Presence of a redundant PCM link on a radio site [true / false] btsSiteManager DP
[M]:
If the attribute value is "true", the object bscSitePcmList attribute includes two items, one identifies the PCM active link, and the other identifies the PCM redundant link.
refPeriod
Description : Value range : Object : Condition : Type : Reference counting period when a counter is involved. [0 to 345600] seconds alarm criteria To define if a counter is associated with the criteria. DP
refPeriod
Description : Reference counting period used by the "excessiveAnomal yRate" function. This attribute is not used by the detection "outOfRangeCo unter" function. In that case, the reference period is set as follows:
420
For cumulative counters, the thresholds define total values not to be reached during a one minute reference period. For load or value counters, the thresholds define maximum or minimum average values not to be reached during a 1 minute reference period, except for the PCM unavailability counters for which they define total values not to be reached during the reference observation period.
The BSS observation counter threshold crossing detection mechanism is described in NTP < 07 >. Value range : Object : Type : [0 to 2147483646] minutes mdWarning if detectionFunction = "excessiveAnomalyRate" DP
relatedSoftwares
Description : This attribute identifies the list of software identified separately. This list represents the units of software ready for equipment use. This attribute is allocated by the MD-R at object creation. This attribute is not modified by the Manager. [0 to 10] executableSoftware DP V13
relay
Description : Identifier of a BSS alarm relay which activates an external alarm loop when the counter of immediate unacknowledged alarms shows a nonzero value for one of the BSSs assigned to the relay. BSS relays transfer the state of the associated BSS immediate action alarm counters to remote sites. A BSS relay is associated with several BSCs. Conversely, a BSC is simultaneously assigned to several relays. Value range : Object : [4 to 64] relay
421
Type : Reminder :
Id OMC-R relays are used to transfer the state of system alarm counters to remote sites and are not managed by users.
remoteSsuState
Description : Value range : State of the remote subsystem (BSSAP) [inService / outOfService]

Object : Type : DD
inService ................. outOfService .....
The MSC BSSAP service is working for the BSC. The MSC BSSAP service is not working.
signallingLinkSet
repetition rate
Description : Periodicity of short message broadcasting. Each concerned BSC repeatedly sends the selected short message to the BTSs covering the selected cells at the repetition rate defined by the user. Each BTS repeatedly broadcasts the short message to all mobiles under its control, using the same repetition rate. Value range : Object : Type : [2 sec. / 30 sec. / 1 min. / 2 min. / 4 min. / 8 min. / 16 min. / 32 min.] short message - Start broadcast DP
report range
Description : Value range : Object : Type : Time period over which the counter values are read. [5 min. / 15 min. / 30 min. / 60 min. / 2 hours / 6 hours / 12 hours / 24 hours] report template DP
422
Notes :
The authorized values for OFS observation type are 60 min., 2 hours, 6 hours, 12 hours, and 24 hours. The authorized values for ORT and Performance Monitor observation types are 5 min., 15 min., 30 min., 60 min., and 2 hours.
Release :
V11
report template
Description : Value range : Object : Type : Release : Identifier of the report template object defined with regard to the bsc object. [30 characters max.] report template DP V11
report type
Description : Value range : A type of observation report. [single observed instance / several observed instance]

single observed instance ........
several observed counters on a single object single counter observed on several objects
several observed instance .......
reportObjLevel
Description : Level of the report to edit. Fill in only when editing a permanent bsc report. Examples: "bsc = all" or "bsc = 1 & bsc = 2". Value range : Object : Type : Checks : [adjacentCellHandOver / bsc / bts / transceiverZone / hardwareTcu3G] Display xxx report DP
[A]:
If specific objects are entered, they all belong to the same class.
423
reportTypeMeasurement Class 3
Description: Value range: Object: Default value: Type: Checks: Type of measurement: normal or enhanced Measurement report (0) / Enhanced Measurement Report (1) bts 0 DP
M:
Parameter reportTypeMeasurement shall not be changed if interferenceMatrixRunningOnBts is equal to yes. This purpose of this check is to forbid activation and deactivation of EMR if interference matrix feature is already activated on the cell.
Release:
V17
retransDuration Class 2
Description : Maximum number of occurrences of a same paging sub-group separating the first and last transmissions of the same paging message. [0 to 22] bts 10 DP retransDuration (delayBetweenRetrans + 1) x nbOfRepeat
V8
[C/M]:
retry on error
Description : Whether commands are rerun when the system detects an application error. This parameter has priority over the on error parameter. When its value is "True", the error command is rerun; when it is "False", the on error parameter is analyzed. The errors involved, the time between reruns, and the maximum number of reruns are defined in static configuration data. Value range : [true / false] (default is False)
424
Object : Type :
commandFile - Run DP
rlf1 Class 2
Description : Value to compute the initial and maximum value of the (CT) counter used in the BTS radio link control algorithm. The FP (FrameProcessor) in the BTS runs the following algorithm to monitor the uplink SACCHs (MS-to-BTS direction):
The FP sets the CT counter to 0 at channel activation. On each correct SACCH, the following occurs: if (CT=0) then CT=4*rlf1 + 4 else CT=min (4*rlf1 + 4, CT+rlf2)
On each incorrect SACCH, the following occurs: CT = max(0, CT-rlf3) When CT reaches 0, a CONNECTION FAILURE INDICATION message is sent to the BSC every T3115 until a Deactivate SACCH or RF CHANNEL RELEASE message is received.
Value range : Object : Default value : Type : Notes :
[0 to 15] bts 4 DP
The radioLinkTimeOut attribute serves the same goal on the downlink. The system does not check that the values of the two attributes are consistent.
Release :
V8
rlf2 Class 2
Description : Step value by which the (CT) counter is increased by the radio link control algorithm when an uplink SACCH is decoded. Refer to the rlf1 entry. Value range : Object : [1 to 4] SACCH frames bts
425
Default value : Type : Release :
2 DP V8
rlf3 Class 2
Description : Step value by which the (CT) counter is decreased by the radio link control algorithm when an uplink SACCH is not decoded. Refer to the rlf1 entry. Value range : Object : Default value : Type : Release : [1 to 4] SACCH frames bts 1 DP V8
rLCPolling Class 3
Description : Value range : Configuring the polling frequency for DL TBF. [0 to 2]

Object : Default value : Type : Release : bts 0 DP
0 selects the original polling frequency of 240 ms and deactivates this feature 1 selects a polling frequency which doubles the original to every 120 ms (during the first 240 ms, then adding one opportunity to setup a UL TBF) 2 selects a polling frequency which quadruples the original to every 60 ms (during the first 240 ms, then adding three opportunities to setup a UL TBF)
V15
426
rmpConfState
Description : Value range : State of radio measurement processing in the TDMA frame. [configured / not configured / not significant]
configured: The CURRENT CELL PARAMETER, NEIGHBOUR CELL PARAMETER (and EXTENDED NEIGHBOUR CELL PARAMETER when more than sixteen defined neighbor cells) messages have been acknowledged by the BTS. not configured: The messages have not been acknowledged by the BTS. If a CURRENT CELL PARAMETER message is not acknowledged, the notification 1258 "Non response during the configuration of the remote L1M" is issued. If a NEIGHBOUR CELL PARAMETER or EXTENDED NEIGHBOUR CELL PARAMETER message is not acknowledged, the notification 1259 "Negative acknowledgement of a distant L1M command" is issued. not significant: The BTS has not sent the messages to the BSC (either the TDMA frame is not working or SYS INFO was not acknowledged).
Object : Type :
transceiver DD
rNCId Class 3
Description: RNC identity of the UMTS neighbouring cell for HO 0...4095 adjacentCellUTRA N N.A. DP
Value range: Object: Default value: Type: Checks:
[C]:
The set of attributes cId, rNCId, mobileCountryCodeUTRAN and mobileNetworkCodeUTRANmust be unique among all the instances of the objects adjacentCellUTRAN attached to the same bts.
427
Release: Notes:
rndAccTimAdvThreshold Class 3
Description : MS-to-BTS distance beyond which mobile access requests to a cell are refused. It defines the maximum timing advance value accepted. The effective timing advance value is broadcast in the CHANNEL REQUIRED message sent by the BTS to the BSC. If it is above the user defined threshold, the BSC ignores the request. Value range : Object : Default value : Type : Checks : [2 to 135] km (non-extended mode) [2 to 120] km (extended mode) bts 35 DP
[C/M]: [C/M]:
The maximum distance is 35 km if the bts object extended cell attribute is "false". The maximum distance is 120 km if the extended cell attribute of the bts object is "true".
Release : Note :
V8 The number of access requests that are refused for that reason is accounted by the BSC (permanent bsc observation counter 1161/6) and fed back to the OMC-R.
routingArea Class 2
Description : Value range : Object : Feature : Default value : Release : Note : GPRS Cell Global Identifier (locationAreaCode + cellIdentity + routingArea). [0 to 255] bts GPRS (SV407 - V12) 0 V12 A Routing Area is necessarily included in a Location Area.
428
rowPosition
Description : Value range : Object : Type : Position number which identifies the position within a row. String from 1 to 4 characters transcoder, controlNode, interfaceNode, hardware transcoder 3G DP
runCallClear Class 3
Description : Value range : Object : Default value : Number of "Measurement Results" messages received before the call clearing algorithm in a cell is triggered. [1 to 31] SACCH frames (1 unit = 480 ms on TCHs, 470 ms on SDCCHs) bts 16
runHandOver Class 3
Description : Value range : Object : Default value : Type : Number of "Measurement Results" messages received before the handover algorithm in a cell is triggered. [1 to 31] SACCH frames (1 unit = 480 ms on TCHs, 470 ms on SDCCHs) bts 1 DP
runPwrControl Class 3
Description : Value range : Object : Default value : Type : Number of "Measurement Results" messages received before the power control algorithm in a cell is triggered. [1 to 31] SACCH frames (1 unit = 480 ms on TCHs, 470 ms on SDCCHs) bts 4 DP
429
rxLevAccessMin Class 3
Description : Minimum signal strength level received by the mobiles for being granted access to a cell. The information is sent to MS prior to registering. As an example, a threshold level of -104 dB corresponds to an acceptable BER of approximately 10-2 (minimum recommended value). Value range : Object : Default value : Type : [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB bts less than -110 dB DP
rxLevDLIH Class 3
Description : Value range : Object : Default value : Type : Maximum interference level in BTS-to-MS direction, beyond which an intra-cell handover may be triggered. [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB handOverControl -85 to -84 dB DP
rxLevDLPBGT Class 3
Description : Downlink signal strength threshold above which handovers for power budget are inhibited. In certain issues, the operator may prevent handover for power budget in case of the received level in the serving cell is good enough that a handover does not improve the situation. This parameter shall be set such as rxLevDLPBGT lRxLevDLH. Value range : Object : Default value : Type : [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB adjacentCellHandOver more than -48 DP
430
Notes :
This parameter is disabled by setting it to the default value: more than -48 (dB). This parameter is only available for DCU4 or DRX transceiver architecture. It is disabled for DCU2 architecture.
Release :
V11
rxLevDLPbgtUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Note: V17 This parameter is available only for BSC 3000. Downlink signal strength threshold above which handovers to UTRAN for power budget are inhibited <-110 ... >-48 dBm adjacentCellUTRAN 63 (on MOD), >-48 (on MMI) DP
rxLevHreqave Class 3
Description : Number of signal strength measurements performed on a serving cell, used to compute arithmetic strength averages in handover and power control algorithms. [1 to 10] number of measurement results handOverControl 8 DP
rxLevHreqaveBeg Class3
Description : Number of measurement reports on current cell for signal strength arithmetic average for early handover mechanism. Refer to the rxLevHreqave entry in the Dictionary. This parameter is coupled with hoMarginBeg and rxNC ellHreqaveBeg use. Value range : Object : Default value : Type : [1 to 10] handOverControl 2 DP
431
Notes :
This parameter is set such as rxLevHreqaveBeg rxLevHreqave. This parameter is only available for DCU4 or DRX transceiver architecture.
Release :
V11
rxLevHreqt Class 3
Description : Number of arithmetic averages taken into account to compute the weighted average signal strength in handover and power control algorithms. Each is calculated from rxLevHreqave signal strength measurements on a serving cell. [1 to 16] handOverControl 1 DP
[C/M]:
It is equal to the number of weights in rxLevWtsList (refer to this entry in the Dictionary).
rxLevMinCell Class 3
Description : Value range : Object : Default value : Type : Minimum signal strength level received by MS for being granted access to a neighbor cell. [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB adjacentCellHandOver -95 to -94 dB (GSM 900 or 850), -93 to -92 (GSM 1800 or 1900) DP
rxLevMinCellUTRAN Class 3
Description: Value range: Object: Default value: Type: Checks: Minimum signal strength level received by MS for being granted access to an UMTS neighbour cell <-110...>-48 adjacentCellUTRAN 63 (on MOD), >-48 (on MMI) DP
432
Release: Note:
rxLevNCellHreqaveBeg Class 3
Description : Number of measurement results used in early handover algorithm to compute the average neighboring signal strength. Refer to the rxNCellHreqave entry in this dictionary. This parameter is coupled with hoMarginBeg and rxLevHreqaveBeg use. Value range : Object : Default value : Type : Int [1 to 10] handoverControl 2 DP
rxLevRxQualDistributionActivation Class 3
Description : Defines the frequency of RxLev and RxQual distribution. This is not used in this version. Only values 0, 1 and 2 are valid. This attribute is modified by the Manager. Value changes are notified to the Manager. Value range : Object : Type : Release : Int [0 to 128] bts DP V14
rxLevULIH Class 3
Description : Value range : The maximum interference level in MS-to-BTS direction, beyond which an intra-cell handover is triggered. [less than -110, -110 to -109, ..., -49 to -48, more than -48] dB, without Uplink Mapping Feature activated. [less than -117, ... , more than -42] dB, when the Uplink Mapping Feature is used. handOverControl Uplink Mapping (TF 876)
Object : Feature :
433
-85 to -84 dB DP
rxLevWtsList Class 3
Description : Values of weights used for signal strength weighed average. The L1M function first calculates rxLevHreqave arithmetic averages from raw measurements, and balances rxLevHreqt averages among those with the weights defined in rxLevWtsList. Each arithmetic average is partnered with one weight in the list. Weight/average associations are set in the order the weights are recorded. The latest computed arithmetic average is always partnered with the first weight in the list. Super-average = [ (averagei x weighti)] / 100, i = 1 to rxLevHreqt Value range : Object : Default value : Type : Checks : [0 to 100] % handOverControl 100 DP
[M]:
The number of weights in the list is equal to rxLevHreqt and their sum equals 100.
rxNCellHreqave Class 3
Description : Number of measurement results used in the Power Budget algorithm to compute the average neighboring signal strength. No weighted average is computed for this category of measurement. Value range : Object : Default value : Type : [1 to 10] number of measurement results handOverControl 8 DP
434
rxQualAveBeg Class 3
Description : This attribute defines the number of quality measures used by the power control mechanism, in case of hopping TS or fast MS. This attribute is modified if the handOverControl object instance is unlocked. Value range : Object : Default value : Type : Release : Note : [1 to 10] handOverControl 2 DP V14 This parameter is only available for BSC 3000.
rxQualDLIH Class 3
Description : Value range : Object : Default value : Type : Release : Bit error rate threshold in BTS-to-MS direction for intracell handover, above which a handover may be triggered. [less than 0.2, 0.2 to 0.4, 0.4 to 0.8, ... , 6.4 to 12.8, more than 12.8] % handOverControl 1.6 to 3.2 % DP V12
rxQualHreqave Class 3
Description : Number of arithmetic averages taken into account to compute the weighted average bit error rate in handover and power control algorithms. Each is calculated from rxQualHreqave bit error rate (BER) measurements on a radio link. [1 to 16] handOverControl 1 DP
435
rxQualHreqt Class 3
Description : Number of bit error rate measurements performed on a radio link, used to compute arithmetic bit error rate averages in handover and power control algorithms. [1 to 10] number of measurement results handOverControl 8 DP
rxQualULIH Class 3
Description : Value range : Object : Default value : Type : Release : Bit error rate threshold in MS-to-BTS direction for intracell handover, above which a handover may be triggered. [less than 0.2, 0.2 to 0.4, 0.4 to 0.8, ... , 6.4 to 12.8, more than 12.8] % handOverControl 1.6 to 3.2 % DP V14
rxQualThresholdDistribution Class 3
Description : RxQual threshold for taking into account measurements in RxLev and Interf matrix distributions. This attribute is modified by the Manager. Value changes are notified to the Manager. Value range : [inferiorTo02 / between02and04 / between04and08 / between08and16 / between16and32 / between32and64 / between64and128 / superiorTo128] bts DP V14
436
rxQualWtsList Class 3
Description : List of up to sixteen weights used to compute the average bit error rate on a radio link. The L1M function calculates rxQualHreqave arithmetic averages from raw measurements, and balances rxQualHreqt averages among those with the weights defined in rxQualWtsList. Each arithmetic average is partnered with one weight in the list. Weight/average associations are set in the order the weights are recorded. The latest computed arithmetic average is always partnered with the first weight in the list. Value range : Object : Default value : Type : [0 to 100] % handOverControl 100 DP
S
sIkAssociatedTmuPortPosition
Description : Value range : Object : Type : Release : Gives the TMU and port number bearing the SS7 signalling. [tmuPos / hardwareSlotPositionNMC / portNumber] signallingLink DD V14
sIkATerResource
Description : Value range : Object : Type : Release : Gives the Ater PCM and TS bearing SS7 signalling. pcmRef [0 to 167] ts [1 to 31] signallingLink DD V14
sacchPowerOffset Class 2
Description : Value range : Object : Describes the power offset that applies to SACCH frames [0..6] dB; step = 2 bts
437
Type : Feature : Default value : Notes : Release :
DP Tx power offset for signalling channels 0 (no power offset) This parameter applies to BSC 3000 V16 and higher. V16
sacchPowerOffsetSelection Class 2
Description : Value range : Object : Type : Feature : Default value : Note : Release : Describes the CODEC selection for applying a power offset on SACCH messages. [NULL / FR 4.75 kbps / FR 5.9 and lower / FR 6.7 and lower] bts DP Tx power offset for signalling channels NULL (no power offset for SACCH) This parameter applies to BSC 3000 V16 and higher. V16
sapi
Description : Value range : Object : Type : Restrictions : The Service Access Point Indicator defining the type of LAPD link use. [RSL / OML] lapdLink DP
[M]:
scannerId
Description : Value range : The identifier of the mdScanner object describing the observation. [0 to 2147483646] "0" identifies the OMC-R permanent manager observation. For a BSS observation or the OMC-R agent permanent observation, this parameter must match the reference number of an mdScanner object. Object : Display xxx report
438
Type Checks :
DP
[A]:
If the request concerns a BSS observation or the OMC-R agent permanent observation, the related mdScanner object is created.
scannerId
Description : Value range : The identifier of the mdScanner object describing the observation. [0 to 2147483646] "0" identifies the OMC-R permanent manager observation. For a BSS observation or the OMC-R agent permanent observation, this parameter must match the reference number of an mdScanner object. Object : Type : Checks : List observation messages DP
[A]:
If the request concerns a BSS observation or the OMC-R agent permanent observation, the related mdScanner object is created.
sCCPRoutingIndicator
Description : Value range : Object : Type : Note : Indicated which route the SCCP takes. [international/national] signallingPoint DP This parameter is only available for BSC 3000.
scramblingCode Class 3
Description: Value range: Object: Default value: Type: Release: Checks: Scrambling code of the UMTS cell 0...511 adjacentCellUTRAN 0 DP V17
[C/M]:
The set of attributes fDDARFCN and scramblingCode must be unique among all the instances of the objects adjacentCellUTRAN attached to the same bts
439
[C/M/D]:
fDDARFCN or scramblingCode cant be changed if Interference Matrix feature is activated on the bts
Note:
This parameter is only available for the BSC 3000.
selfAdaptActivation Class 3
Description : This attribute specifies if the automatic handover adaptation mechanism is enabled/disabled. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute is modified only if the bts object instance is unlocked. Value range : Object : Default value : Type : Release : Note : [Enabled/Disabled] bts Disabled DP V14 This parameter is only available for BSC 3000.
selfTuningObs Class 3
Description : BTS mode sending the PwCI distribution on the Abis interface. This attribute allows the configuration of CellTieringConfiguration at BTS level. CellTiering mode must be activated. [pwCi distribution not sent, pwCi distribution sent after gathering, one pwCi distribution sent per hour] handOverControl Automatic Cell Tiering (TF995-V12) DP V12 PWCI distribution may be gathered and sent onto the Abis interface independently of tiering activation.
Note : Value range :
Object : Feature : Type : Release : Note :
440
sequenceNumber
Description : Object : Type : Tracing the record identification number. traceFileReady DP
serial number
Description : Three fields (geographical scope, message code, update number) identify a particular message from the source and type indicated by the Message Identifier are altered every time a given Message Identifier is changed. [geographical scope, message code, update number]
Value range :
geographical scope ..
[immediate cell wide normal PLMN wide normal location area wide normal cell wide] [0 to 1023]
message code .....
differentiate messages from same source and type (same Message Identifier)
update number ....
[0 to 15]
differentiate older and newer versions of the same message Object : Type : short message - Display broadcast characteristics DP
serial number
Description : Three fields (geographical scope, message code, update number) identify a particular message from the source and type indicated by the Message Identifier are altered every time a given Message Identifier is changed. [geographical scope, message code, update number]
Value range :
geographical scope ..
[immediate cell wide normal PLMN wide normal location area wide normal cell wide] [0 to 1023]
message code .....
differentiate messages from same source and type (same Message Identifier)
update number ....
[0 to 15]
441
differentiate older and newer versions of the same message Object : Type : short message - Display broadcast characteristics DP
servingBandReporting Class 3
Description: Value range: Number of GSM cells in the serving band to be reported in the list of strongest cells in the EMR message 0: 1: 2: 3: No inband cell is favoured 1 strongest inband cell is favoured 2 strongest inband cells are favoured 3 strongest inband cells are favoured
Object: Default value: Type: Release: Notes:
bts 3 DP V17 This parameter is only available for BSC 3000.
servingBandReportingOffset Class 3
Description: Value range: Offset to apply to the reported value when prioritizing the cells for reporting for GSM serving frequency band 0..7 on MOD (corresponding to 0, 6, , 42 dB. on MMI), + 0xFF on MOD corresponding to not significant on MMI handoverControl not significant DP V17 This parameter is only available for BSC 3000.
servingFactorOffset Class 3
Description : This attribute defines the offset linked to the serving cell, used to decrease the HO margin, in some specific cases. This attribute is only modified if the handOverControl object instance is unlocked. Value range : Object : [-63 to 63] dB handOverControl
442
-2 DP V14 This parameter is only available for BSC 3000.
session context saving mode

Description : Value range : Object : Type : Release : Session context saving mode. [automatic when logout / on user request] user profile DP V10
sGSNRelease Class 3
Description : Value range : Object : Default value : Feature : Type : Release : The parameter is set to 0 when the SGSN supports rel98 or older and set to 1 when the SGSN supports rel99. "SGSN is rel98 or older" (SGSNR = 0) "SGSN is rel99 onwards" (SGSNR = 1) bts 0 EDGE Traffic Management (20231) DP V15
shelfNumber
Description : Value range : Object : Feature : Type : Release : Indicates the position of a module in a shelf. [0 to 1] atmRm, cc, cem, iem, lsaRc, mms, omu, sw8kRm, tmu, trm, hsaRc, hsaRcTcu, iom AR 1209 - V13.1 - V13.1 DD V13
443
short message
Description : An identifier (name) of a short message on the OMC-R. A message name identifies the short message on the OMC-R; it is not relayed to the BSC during broadcasting. It can be changed by the Rename command (see the new name entry in the Dictionary). Setting a short message characteristics does not affect the current broadcast of the message. The change will be effective when a new broadcast command is launched. A short message broadcasting is identified on the OMC-R by a unique serial number assigned by the system when broadcasting is initiated (refer to this entry in the Dictionary). Value range : Object : Type : Checks : [case sensitive, 20 characters max.] short message Id
C]: [M]: [D]:
The name of a short message is unique to the OMC-R. The short message is created. The short message is not being broadcast.
signallingLink
Description: This field provides the Signaling Link (SLK) identifier. It is a sub-parameter field of SignallingLinkResourcesStates See signallingLinkObjectInstance; signallingLinkId range. signallingLinkSet Not applicable DD V17 This parameter is only for BSC 3000. Only the signallingLinkId part of this field is displayed at the MMI.
Value range: Object: Default value: Type: Release: Note:
444
signallingLinkId
Description : Value range : Object : Type : Checks : Identifier of a signallingLink object defined with regard to a signallingLinkSet object. [0 to 2147483646] signallingLink Id
[C]:
The number of signaling links controlled by a BSC is limited to maxSigLPerSigLS (static configuration data). The maximum number of signallingLink objects for Lb interface is 2. The referenced pcmCircuit object (pcmCircuitId) is assigned to the A interface and depends on the same transcoder object (transcoderId) as the signallingLink object. The referenced PCM,TS pair (pcmCircuitId and timeSlotNumber) is not already assigned to a signallingLink or xtp object dependent on the same transcoder object, and the time slot is not mapped on the TS used by the OMC channel on the Ater interface. If the SS7 link uses PCMA link no.3 (pcmCircuitId), the timeSlotNumber is in the range [1 to 27] if the PCM link is an E1 link or in the range [1 to 20] if the PCM link is a T1 link. Since the last four time slots of that link are not mapped on the Ater interface, they are unusable (refer to the transcoderMatrix entry in the Dictionary). If the application database of the related BSC is built, the parent bsc object is unlocked. If the application database of the related BSC is built, the signallingLink object is locked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command. No mdScanner object refers to the signallingLink object (no observation is running on that object).
[C]: [C/M]:
[C/M]:
[C/M]:
[C/D]: [D]: [D]:
[D]:
445
signallingLinkResourcesStates
Description: Gives Dynamic Datas (DDs) on all SLKs below the signallingLinkSet object. This parameter is composed of the following sub-parameter fields: signallingLInk, slkAssociatedTmuPortPosition, slkATerResource, slkAResource, signallingLinkResState Contains up to 16 elements signallingLinkSet, Not applicable DD
Value range: Object: Default value: Type: Notes:
This parameter is available only for BSC 3000. This parameter is an array with a variable amount of elements. Each element carries information about the path of one SLK of the beam.
Release:
V17
signallingLinkResState
Description : Value range : SS7 channel resource state. It is a sub-parameter field of signallingLinkResourcesStates. [blocked / inhibited / inhibitedLocal / inhibitedDistant / inhibitedL ocalDistant / inhibitedBlocked / notInhibitedNotBlocked]

Object : Type :
inhibited ............. inhibitedLocal ......... inhibitedDistant ........ inhibitedLocalDistant .. blocked ..............
state enforced by a user SetInhibit command state enforced by a user state enforced by the MSC state enforced by a user and the MSC state enforced by the MSC following a loss of dialogue between MTP2 and MTP3
signallingLink DD
446
signallingLinkResState field
Description: Value range: This field provides Signaling Link (SLK) resource state. See the SignallingLinkResStateN MCType type. [inhibited/blocked, localInhibited/ distantInhibited/ distantLocalInhibited] signallingLinkSet Not applicable DD V17 This field is only for BSC 3000. Note that the state available will be displayed when this variable length array will contain no item.
Object: Default value: Type: Release: Note:
signallingLinkSet
Description : Identifier of a signallingLinkSet object describing the route (not the linkset) between the BSC and MSC, or the BSC and SMLC. [0 to 1] where signallingLinkSet[0] represents A interface and signallingLinkSet[1] represents Lb interface. signallingLinkSet Id
[C]: [C]: [D]:
The signallingLinkSet object is not created for the parent signallingPoint object. If the application database of the related BSC is built, the parent bsc object is unlocked. The application database of the related BSC has been reset by an Off line reset BDA command.
signallingPoint
Description : Value range : Object : Type : Checks : Identifier of a signallingPoint object describing a BSC-MSC link on the BSC. [0 to 2147483646] signallingPoint Id
[C]:
The signallingPoint object is not created for the parent bsc object.
447
[C]: [C]: [D]:
The software object related to the parent bsc object is created. If the application database of the related BSC is built, the parent bsc object is unlocked. The application database of the related BSC has been reset by an Off line reset BDA command.
sigPowerOverboost Class 3
Description : Value range : Object : Default value : Type : Checks : Reserved for future use. [0dB to 1.6dB] bts 0dB DP
[C/M]:
sigPowerOverboost cannot be set to 1.6 because bsPowerControl is not enabled or bts is not a BTS18000 or is not operating in 1900 MHz frequency band sigPowerOverboost cannot be set to 1.6 because bsPowerControl is not enabled or bts is not a BTS 6000 or BTS18000 or is not operating in 1900 MHz frequency band
Checks:
[C/M]:
Release :
V16
site
Description : Value range : Object : Type : Name that identifies the site. String [1 to 16 characters] transcoder, controlNode, interfaceNode, hardware transcoder 3G DD
siteGsmFctList Class 2
Description : Value range : List of up to 14 elements identifying the GSM functions configured in a site BCF. [entityMgt / download / siteMgt / abisSig / abisTraf / rfTrans / rfRecep / cellMgt / fhMgt / tdmaMgt / tsMgt / gsmTime / car0Fil / freqMgt]
448
Routing mode The routing mode of the messages handled by the GSM functions, enabling the Abis interface to identify the GSM entity to which the messages are sent, and the maximum response time of each GSM function summarized in the following table. GSM function Routing mode Without centralized O&M GSM entity Management downloading site Management abis Signalling Management abis Traffic Management radio frequency Transmission radio frequency Reception cell Management frequency hopping Management tdma Management time slot Management gsmTime carrier 0 Filling frequency Management relative tei relative tei relative tei bcf bcf bcf not implemented bcf relative tei relative tei relative tei not implemented not implemented bcf With ce ntralized O&M bcf relative tei bcf bcf bcf bcf none bcf bcf bcf bcf none none bcf 10 secon ds 32 secon ds 120 seco nds 120 seco nds 120 seco nds 120 seco nds 0 second 120 seco nds 30 secon ds 30 secon ds 30 secon ds 0 second 0 second 120 seco nds Response time
Object : Default value : Type : Checks :
btsSiteManager site Mgt/abisSig DP
[C/M]:
Each function occurs once in the list.
449

Notes :
[C/M]: [C/M]: [M]:
The "entityMgt", "download", "tdmaMgt", and "tsMgt" functions are included in the list. The "freqMgt" function is only allowed for a BTS using cavity coupling. The "fhMgt" function is included in the list if bts objects dependent on the btsSiteManager object are authorized to hop (btsIsHopping).
The GSM functions whose routing mode is "not implemented" must not be included in the list. See the preceding table. The GSM entities managing these GSM functions are BCF and TRX.
siteName
Description : Reference name of a radio site on the OMC-R. It begins with a letter and is case sensitive. The name of a site can be used in all MMI commands to reference the site on the OMC-R. Value range : Object : Type : Checks : Note : [30 characters max.] btsSiteManager DP
[C/M]:
The name of a site is unique to the OMC-R.
Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited. The valid symbols are:
letter characters: A, B, C..., Z, a, b, c..., z. digit symbols: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9. minus sign: undescore: _ space:
450
slkAResource field
Description: This field provides SLK A section related data. It is a sub-parameter field of signallingLinkResourcesStates. MMI displayed fields:
Value range:

pcmInstance: 0-167 ts: Integer 1-13
signallingLinkSet Not applicable DD V17 This field is only for BSC 3000. This optional field is meaningful if an A resource has been assigned to this Signaling Link (SLK) path.
slkAssociatedTmuPortPosition field
Description : Value range : SLK CN termination identifier. It is a sub-parame ter field of signallingLinkResourcesStates
shelf number: Integer 0-1 positionInShelf: Integer 1-15 portNumber: Integer
Object : Default value: Type : Release: Notes :
signallingLinkSet Not applicable DD V17
This parameter is only available for BSC 3000. This optional field is meaningful if a CN termination has been assigned to this SLK path.
451
slkAssociatedTmuPortPosition
Description: Value range: SLK CN termination identifier Displayed fields:

shelfNumber: Integer 0-1 positionInShelf: Integer 1-15 portNumber: Integer
signallingLink Not applicable DD V17 This parameter is available only for BSC 3000. This optional parameter is meaningful if a CN termination has been assigned to Signaling Link path.
slkATerResource field
Description : Value Range : SLK Ater section identifiers. It is a sub-parameter field of signallingLinkResourcesStates.
pcmInstance: Integer 0-363 ts: Integer 1-31
Object : Default value: Type : Release: Notes :
signallingLinkSet Not applicable DD V17
This field is only available for BSC 3000. This optional field is meaningful if an Ater resource has been assigned to a Signaling Link (SLK) path.
slkATerResource
Description: Value range: SLK Ater section identifiers Displayed fields:

Object:
pcmInstance: Integer 0-363 ts: Integer 1-31
signallingLink
452
Default value: Type: Release: Notes:
Not applicable DD v17 This field is available only for BSC 3000. This optional parameter is meaningful if an Ater resource has been assigned to this Signaling Link (SLK) path.
slc Class 2
Description : Value range : Object : Type : Checks : Code of an SS7 channel. It is identical on BSC and MSC ends. [0 to 15] signallingLink DP
[C/M]:
The code of an SS7 link is one-of-a-kind to the BSC.
small to large zone HO priority Class 3

Description : External priority of inter-zone handovers from the inner zone to the outer zone in a concentric cell. This attribute is defined if the associated bts object describes a concentric cell. Value range : Object : Default value : Condition : Type : Release : [0 to 17] handOverControl 17 To define if the associated bts object describes a concentric cell. DP V9
smartPowerManagementConfig parameter Class 3

Description : Value range : Enable/disable the smart power management feature 0..1 0/disabled 1/enabled Default value/0/disabled
453
Object : Type : Release : Notes :
Power control DP V17 BSC 3000 only
smartPowerSwitchOffTimer Class 3
Description : Value range : Object : Type : Release : Notes : Set the timer before switching the PA OFF 5-255 (minutes) Power control DP V17 BSC 3000 only
smoke detector Class 2

Description : Value range : Object : Type : Release : Presence or absence of the optional equipment "smoke detector" in S8000 Outdoor. [Present / Absent] btsSiteManager DP V9
smsCB Class 3
Description : Value range : Object : Default value : Type : Checks : Whether broadcasting of short messages in unacknowledged mode is authorized in a cell. [used / unused] bts used DP
[M]:
The attribute value is "used" if the channelType of one of the channel objects dependent on the bts object is "bcchSdcch4CBCH" or "sdcch8CBCH" .
Remark :
Configuration of logical channels and broadcast of short messages are managed by two separate OMC-R functions. When a short message broadcast is started, the presence of a CBCH in the channelType of a channel object dependent on a concerned bts object is checked.
454
However, the SMS-CB function is not aware of changes made to that attribute. Consequently, withdrawing a CBCH from the configuration will stop any short message broadcast in the concerned cell without the SMS-CB function knowing.
software
Description : Identifier of a software object. The software object class allows users to manage the software releases of bsc objects (BSC), btsSiteManager objects (BCF), transceiverEquipment objects (TRX). Software objects are managed by the OMC-R "Software Management" function. The software objects have four attributes: sWVersion BackUp, sWVersionFallback, sWVersionNew, and sWVersionRunning. They are managed by the system according to the following user commands: Download, Activate new version, and Return to previous version. Value range : Object : Type : Checks : [0 to 2147483646] software Id Checks common to all software objects:
[C]: [D]:
The software object is not created for the parent managed object. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.
Additional checks performed on the software-bsc object:
[C]: [C/D]: [D]: If the application database of the related BSC is built, the bsc object is locked. All objects dependent on the bsc object are deleted.
Additional checks performed on the software-btsSiteMan ager object:
[C/D]:
If the application database of the related BSC is built, the parent bsc object is unlocked and the btsSiteManager object is locked.
455
[D]:
All objects dependent on the btsSiteManager object are deleted.
Additional check performed on the software-transceiverE quipment object:
[C/D]:
If the application database of the related BSC is built, the parent bsc object is unlocked, the parent bts object is locked, and the transceiverEquipment object is locked.
softwareLabel
Description : This attribute is a comment about the related software. This attribute is modified by the Manager. Value changes are notified to the Manager. [1 to 80] executableSoftware DP V13
source indicator
Description : Select messages according to the source of the operation. Do not fill in if this criterion is not to be selected. Value range : Object : Type : [resource operation / management operation / unknown] Alarm and notification logs - Filter DP
specific problems
Description : Selecting messages according to a (cause, fault number) pair. This parameter allows selection of a fault number with one or more associated causes. Refer to these entries in the Dictionary. Do not fill in if this criterion is not selected. Object : Type : Alarm and notification logs - Filter DP
456
speechMode Class 3
Description : List of the speech algorithms associated with channel use modes in the cell. The "full rate" value refers to the standard algorithm. Value range : list of [algoid] where: algoid id : full rate, enhanced, full rate, AMR full rate, AMR half rate bts [full rate, enhanced full rate] DP
Object : Default value : Type : Checks : Release :
V8
[C/M]:
The "full rate" value is mandatory; it must be defined in the list.
speechMode Class 3
Description : List of the speech algorithms associated with channel use modes on the A interface. The "full rate" value refers to the standard algorithm. Value range : list of [algoid] where: algoid id: full rate, enhanced, full rate, AMR full rate, AMR half rate signallingPoint [full rate, enhanced full rate] DP
Object : Default value : Type : Checks :
[C/M]: [C/M]:
The "full rate" value is mandatory; it must be defined in the list. Checks are performed to determine the presence of a valid license for AMR before the following operations:
setting the value on the speechmode parameter on signallingPoint object to "AMR half rate" or "AMR full rate" unlocking a TRX building a BSC resetting a BDA of a BSC
457
The attempt to set an "AMR half rate" or "AMR full rate" value of the speechMode parameter on the signallingPoint object is possible only when a valid license is available. When there is a signallingPoint object with the speechMode parameter value set to "AMR half rate" or "AMR full rate", then no TRX unlocking, no BDA build and no BDA reset is possible on the related BSC without a valid license. If the check fails, then the corresponding action is rejected and a clear error message displayed Release : V8
speechOnHoppingTs Class 3
Description : Value range : Object : Feature : Default value : Type : Release : This attribute is reserved for future use. [true, false] bts GPRS (SV407 - V12) false DP V12
speechVersionAsscomp Class 1
Description : Value range : Object : Default value : Type : Release : Whether the "Speech version" element is used or not in the ASSIGN COMPLETE messages (Phase II compliance). [false / true] signallingPoint true DP V12
speechVersionHoperf Class 1
Description : Whether the "Speech version" element is used or not in the HANDOVER PERFORMED messages (Phase II compliance). [false / true]
Value range :
458
Object : Default value : Type : Release :
signallingPoint
DP V12
speechVersionHoreq Class 1
Description : Whether the "Speech version" element is used in the HANDOVER REQUEST ACKNOWLEDGE messages (Phase II compliance). [false / true] signallingPoint true DP V12
speechVersionHorqd Class 1
Description : Value range : Object : Default value : Type : Release : Whether the "Speech version" element is used or not in the HANDOVER REQUIRED messages (Phase II compliance). [false / true] signallingPoint true DP V12
standard indicator AdjC Class 3

Description : Value range : Object : Feature : Default value : Type : Release : Note : Type of network in which this neighbor cell is working. [gsm / extended gsm / dcs 1800 / pcs 1900 / R gsm / gsm850 / gsmdcs / dcsgsm / pcsgsm850 / gsm850pcs] adjacentCellHandover Dualband cell management (TF875 - V12) gsm DP V10 "gsmdcs" and "dcsgsm" are only available for S8000 DRX transceiver architecture.
459
standard indicator AdjC Class 3

Description : Value range : Object : Default value : Feature : Type : Release : Note : Type of network in which this neighbor cell is working. [gsm / extended gsm / dcs 1800 / pcs 1900 / R gsm / gsm850 / gsmdcs / dcsgsm / pcsgsm850 / gsm850pcs] adjacentCellReselection gsm Dualband cell management (TF875 - V12) DP V10 "gsmdcs" and "dcsgsm" are only available for S8000 DRX transceiver architecture.
standardIndicator Class 2
Description : Type of network in which the cell is working. From the value given to this attribute, the OMC-R determines the network frequency band and the frequencies used by all radio entities (cells and radio time slots) in the related site. Value range : [gsm / extended gsm / dcs1800 / pcs1900 / R gsm / gsmdcs / dcsgsm / gsm 850 / gsm850pcs / pcsgsm850 / gsm450 / gsm480 / gsm750 / egsmdcs / dcsegsm] bts Dualband cell management (TF875 - V12) DP GSM 900 network (gsm) The GSM 900 frequency band is 2*25 MHz wide and includes 124 pairs of carrier frequencies, numbered [1 to 124], which are 200 kHz apart:
Object : Feature : Type : Note :
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 Uplink frequency:
f1 = 890 + 0.2xN MHz where N = [1 to 124]
For the Downlink frequency there is the following shift:
460
f2 = f1 + 45 MHz
EXTENDED GSM network (extended gsm) The extended GSM frequency band is 2*35 MHz wide and includes 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]
Note :
f2 = f1 + 45 MHz
The extended GSM frequency band defined above is the definition of the ETSI. GSM-R network (R gsm) The GSM-R frequency band is 2*39 MHz wide and includes 194 pairs of carrier frequencies, numbered [0 to 124] and [955 to 1023], which are 200 kHz apart:
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
461
Note :
The GSM-R frequency band defined hereabove is the definition of the ETSI. GSM 1800 network (dcs1800) The GSM 1800 frequency band is 2*75 MHz wide and includes 374 pairs of carrier frequencies, numbered [512 to 885], which are 200 kHz apart:
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 and includes 299 pairs of carrier frequencies, numbered [512 to 810], which are 200 kHz apart:
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 Network paragraph).
462
The secondary band is GSM 1800 (see above GSM 1800 Network paragraph). GSM 1800 - GSM 900 network (dcsgsm) The primary band is GSM 1800 (see above GSM 1800 Network paragraph). The secondary band is GSM 900 (see above GSM 900 Network paragraph). Note : "gsmdcs" and "dcsgsm" are only available for S8000 DRX transceiver architecture. GSM 850 The GSM 850 frequency band is 2*25 MHz wide and includes 124 pairs of carrier frequencies, numbered [128 to 251],
Uplink direction = 824 to 849 MHz Downlink direction = 869 to 894 MHz
f1 = 824.2 + 0.2x(N - 128) MHz where N = [128 to 251]
Release : V9
f2 = f1 + 45 MHz
standbyStatus
Description : Value range : Object : Feature : Type Release : ISO State [hotStandby / coldStandby / providingService] atmRm, cem, iem, lsaRc, omu, sw8kRm, trm, hsaRc, hsaRcTcu, iom AR 1209 - V13.1 DD V13
463
standbyStatus TMU
Description : This data provides the duplex operational status of the TMU board. It can be either (for a TMU) providingService when TMU is distributed or coldStandby when TMU is started but not (yet) distributed. INTEGER with:
Value range :

Object : Type : Release: Note: DD
hotStandby (0) coldStandby (1) providingService (2) notSignificant (15)
TMU
V17 This parameter is available in BSC 3000 only.
start date
Description : The date the first data is recorded in the log (default is the current date). Date format entry forms are detailed in NTP < 130 >. Value range : Object : Type : [<date>] System session log - Filter DP
start time
Description : Absolute time of first job run (default is the current date and time). Absolute time format entry forms are detailed in NTP < 130 >. If date matches the current date, set time to a value at least one minute after the current time. Value range : Object : Type : [<date>,<time>] job DP
464
start time
Description : Start of system log reading on the requested start date (default is 00:00). Time format entry forms are detailed in NTP < 130 >. Do not fill in if this criterion is not selected. Value range : Object : Type : [<time>] System session log - Filter DP
startAlarmFilter
Description : Condition for triggering an alarm when no counter is involved. The following fields can be combined in the logical expression: Parameter administrativeState availabilityStatus bsc equipment name bsc model cause btsSiteManager model bts equipment name equipment processor number faultNumber operationalState perceived severity postMortem usageState Notification type state change state change alarm alarm alarm alarm alarm alarm alarm state change alarm alarm state change Operators = = = = <=> = = <=> <=> = = = =
465
The following logical operators can be used in the logical expression:
& stands for the logical AND. | stands for the logical OR. ! stands for the logical NOT.
The "postMortem" field can take two values, either "before BSC restart" or "after BSC restart". They have the following meaning:
before BSC restart means that the notification issued by the BSC was received by the OMC-R agent without the BSC having restarted (nominal conditions). after BSC restart means that the notification was issued by the BSC, then, the BSC was restarted before the OMC-R agent received the notification. These notifications do not trigger alarms.
Value range : Object : Condition : Type :
[logical expression] alarm criteria To define if no counter is associated to the criterion. DP
startAlarmThreshold
Description : The maximum counting value in the reference period when a start-of-alarm message is sent. The value must be checked by users. This attribute defines a maximum value read at the end of the defined refPeriod. It must be greater than endAlarmThreshold. Threshold changes are effective when the OMC-R is restarted. Value range : Object : Type : [0.00 to 2147483646] mdWarning if detectionFunction = "excessiveAnomalyRate" DP
466
startAlarmThreshold
Description : Minimum (thresholdLow) / maximum (thresholdHigh) counting value in the reference period, below/above which a start of "lower threshold/upper threshold" alarm message is sent. The value must be checked by users. If thesholdType = "thresholdLow", this attribute defines a minimum value for a one minute reference period (or the counter collecting period for PCM unavailability counters), below which a start of "lower threshold" alarm message is sent. It must be lower than startAlarmThreshold "low". If thesholdType = "thresholdHigh", this attribute defines a maximum value for a one minute reference period (or the counter collecting period for PCM unavailability counters), above which a start of "upper threshold" alarm message is sent. It must be greater than startAlarmThreshold "high". Threshold changes are effective when the OMC-R is restarted. Value range : Object : Type : Remark : [0.00 to 2147483646] mdWarning if detectionFunction = "outOfRangeCounter" DP

startCounterThreshold
Description : Value range : Object : Condition : Type :
The threshold limits depend on the associated counter. The BSS counter threshold crossing detection mechanism is described in NTP < 07 >.
Minimum counting threshold when a counter is involved. [0 to 100] alarm criteria To define when a counter is associated with the criterion. DP
startTime
Description : Value range : Object : Date and time the files were restored on the OMC-R agent disks. [<date> <time>] log - Display
467
Condition : Type :
This attribute is significant and displayed only when the log object describes a log restored on the OMC-R agent disks. DP
startTime
Description : Date and time the temporary observation started. This information is provided by the system and indicates the exact time when the observation counters are collected for the first time. Value range : Object : Type : [<date> <time>] mdScanner - Display DI
stopTime
Description : Value range : Object : Condition : Type : Date and time the OMC-R agent will purge the restored files. [<date>, <time>] log - Display This attribute is significant and displayed only when the log object describes a log restored on the OMC-R agent disks. DP
stopTime
Description : Date and time the temporary observation will stop. Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Checks : [<date>,<time>] mdScanner - Create temporary observation DP
[C]: [C]: [M]:
stopTime - startTime > mdGranularityPeriod minutes stopTime - startTime < 1440 minutes (24 hours) This attribute cannot be modified. Stop the observation if necessary by deleting the mdScanner object and restart it by creating a new mdScanner object with the appropriate attributes.
Restrictions :
468
subChanId
Description : AGCH subchannel number: Do not fill in when the channelType of the radio time slot is "tchFull" or "mainBCCH". [0 to 7] when channelType = "sDCCH" or "sdch8CBCH", [0 to 3] otherwise channel - Set channel state DP
Value range : Object : Type : Checks : Reminder :
[A]:
The parent btsSiteManager and bts objects are unlocked.
A BCCH or a CBCH cannot be blocked.
subject
Description : Identifier (name) of a user message in the OMC-R. It is displayed in the "Inter-user message manager" window of the message addressees and allows them to identify the message before reading. Value range : Object : Type : [40 characters max.] user message Id
suffix
Description : Optional string of characters to add to the name of the call monitoring data files when saved in the OMC-R. When a suffix is defined, a call monitoring data file transferred to the OMC-R by running the Transfer command is saved under the name "SDO_CM_BSCnnn_<suffix>.yyyymmdd ", where "nnn" identifies the BSC hosting the data file (if bsc = 5, then nnn is read "005") and "yyyymmdd" is the file saving date. See to NTP < 07 >. Value range : Object : Type [10 characters max.] Call monitoring - Transfer (SDO) DP
469
summary
Description : Object : Type : Text explaining the goal of the command file. commandFile DP
suspendResumeActivation Class 3
Description : Value range : Default value : Object : Feature : Type : Notes : Enables or disables the Suspend/Resume feature. [disabled / enabled]. The recommended value is "enabled". disabled bsc GPRS / EDGE Suspend and Resume DP
When disabled: The Suspend is still performed. The Resume is performed through the Routing Area Update message. The new value does not apply to ongoing calls. It applies to new calls only.
Release :
V15
supportingTransceiverEquipment
Description : Identifier of the TRX associated with the TDMA frame by the BSC. This dynamic attribute allows the user to know the TDMA-TRX/DRX association established by the BSC. It is displayed provided the transceiver object operationalState is "enabled". Refer to this entry in the Dictionary. If the TRX/DRX is declared faulty because of a frequency loss, the system takes the following actions:
attempt to reconfigure the associated TDMA frame on the redundant TRX/DRX if there is no redundant TRX/DRX, reconfiguration of the TDMA frame on another TRX/DRX if its priority is higher than the priority of the TDMA frame currently configured
470
If the associated TDMA frame cannot be re-configured for some reason, all frames that were using the frequency lost by the TRX/DRX will be disturbed. Value range : Object : Type : Remark : [0 to 2147483646] transceiver DD Only BTSs using cavity coupling manage dynamic reconfiguration of hopping frequencies.
sw8kRm
Description : Value range : Object : Type : The 8k Subrate Timeswitch Ressource Module, which adds sub-track switching capability to the Interface Node. [0 to 2147483646] sw8kRm Id
sw8kRmId
Description : Identifier of the sw8kRm object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000. [0 to 2147483646] sw8kRm DP V13
sWVersionBackUp
Description : Reference number of the backup software release. It is identical to sWVersionRunning. Refer to the sWVersionRunning entry in the Dictionary. Value range : Object : Type : [Bsxabvcdefgh (BSC software) / XXXabcdef (others)] software DP
471
sWVersionFallBack
Description : Reference number of the previous software release. It is updated following a version change command. Refer to the sWVersionRunning entry in the Dictionary. This attribute is undefined when the object is created. As a result of an Activate new version command, the system updates the sWVersionFallBack attribute with the reference of the software release previously running in the related BSS entity. As a result of a Return to previous version command, the system sets the sWVersionFallBack attribute undefined. Value range : Object : Type : [Bsxabvcdefgh (BSC software) / XXXabcdef (others)] software DP
sWVersionNew
Description : Reference number of the new software release. It is updated following a download or version change command. Refer to the sWVersionRunning entry in the Dictionary. This attribute is undefined when the object is created. As a result of an Activate new version command, the system sets the sWVersionNew attribute undefined. As a result of a Download or Return to previous version command, the system updates the sWVersionNew attribute with the reference of the software release downloaded or that was presently running in the related BSS entity. Value range : Object : Type : [9 to 12] String software DP
472
sWVersionRunning Class 2
Description : Reference number of the software release currently running. It is defined by the user at object creation time and is updated following version change commands. This parameter identifies the type and version of the software currently running in the related BSS entity. Check the BSS delivery descriptor file to fill it in when creating the software object. As a result of an Activate new version or Return to previous version command, the system updates the sWVersionRunning attribute with the reference of the software release newly activated in the related BSS entity. For more information on the reference number formats for each type of BSS entity driven by software, refer to the "delivery" entry in this Dictionary. Value range : Object : Type : Checks : String from 9 to 12 characters software DP
[C]: [C]:
The attribute is defined (nonzero value). The first three letters of the reference number match the type of the managed object related to the software object.
synchronized Class 3
Description : Value range : Whether the neighbor cell and the associated serving cell are synchronous, and is attached to the same BTS. [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 serving cell are not attached to the same BTS "synchronized cells": the neighbor cell and the serving cell are attached to the same BTS "pre sync HO with timing advance": the handover procedure between the neighbor cell and the serving cell is pre-synchronized with the GSM Real Time Difference between the neighbor cell and the serving cell in the "HANDOVER COMMAND" message "pre sync HO, default timing advance": a pre-defined timing advance is used in the pre-synchronized
473
handover procedure between the serving cell and the neighbor cell. Refer to "preSynchroTimingAdvance" parameter. adjacentCellHandOver not synchronized cells DP
synchronizingHsaRc
Description : Value range : Source HsaRC of the clock synchronization
0: HsaRC 0 is the source of the clock synchronisation 1: HsaRC 1 is the source of the clock synchronisation Not significant: none of the HsaRC is the source of the clock synchronisation
Object : Default value: Type : Release :
bsc Not applicable DD V17
synchronizing PCM
Description : Value range : Object : Type : Release : Synchronizing PCM choice (on Ater interface). [synchro mic 0, synchro mic 2, synchro mic 4, synchro mic 6, synchro internal clock] bsc DD V10
syntheticFaultNumber
Description : Value range : Object : Condition : Type : Checks : A synthetic fault number assigned to the alarm when a counter is involved. [39500 to 39549] alarm criteria To define when a counter is associated to the criterion. DP
[C/M]:
The number is in the range [39500 to 39549].
474
systemInfoType2 Class 2
Description : Value range : Object : Type : Release : Reserved for future use. disabled/enabled bts DP V15
T
t3101 Class 3
Description : BSC timer triggered during the immediate assignment procedure. Use the suggested system value. It is set on transmission of CHANNEL ACTIVATION by the BSC and canceled on receipt of ESTABLISH INDICATION sent by the BTS. Value range : Object : Default value : Type : [1 to 255] seconds bts 3 DP
t3103 Class 3
Description : BSC timer triggered during the handover procedure. Use the suggested system value. It is set on transmission of HANDOVER COMMAND by the BSC and canceled on receipt of either HANDOVER COMPLETE or HANDOVER FAILURE sent by the MS (intra-bss handover), or CLEAR COMMAND sent by the MSC (inter-bss handover). At expiry of T3103, the channel is released. Value range : Object : Default value : Type : Checks : [2 to 255] seconds (t3103 < bssMapT8) bts 5 seconds DP
[C/M]:
t3103 < bssMapT8 (attribute of the parent bsc object)
475
t3107 Class 3
Description : BSC timer triggered during the assignment command procedure. Use the suggested system value. It is set on transmission of ASSIGN COMMAND by the BSC and canceled on receipt of either ASSIGN COMPLETE or ASSIGN FAILURE sent by MS. Value range : Object : Default value : Type : [2 to 255] seconds bts 10 seconds DP
t3109 Class 3
Description : BSC timer triggered during the SACCH deactivation procedure. Use the suggested system value. It is set on receipt of DEACTIVATE SACCH ACKNOWLEDGE sent by the BTS and canceled on receipt of RELEASE INDICATION sent by the BTS. If the timer expires, an RF CHANNEL RELEASE message is sent to the BTS and an RF CHANNEL RELEASE ACK is expected. Mobiles comply with system operating conditions when the counter (S) associated with SACCH messages is assigned a value below or equal to t3109. Value range : Object : Default value : Type : Checks : [2 to 255] seconds (t3109 radioLinkTimeout) bts 12 seconds DP t3109 radioLinkTimeout
[C/M]:
t3111 Class 3
Description : BSC timer triggered during the radio resource clearing procedure. Use the suggested system value. It is set on receipt of RELEASE INDICATION sent by the BTS. On elapse, the BSC sends RF CHANNEL RELEASE. Value range : Object : [1 to 255] seconds bts
476
2 seconds (1 second in a GSM-R context) DP
t3121 Class 3
Description: Value range: Object: Default value: Type: Checks: Release: Notes: V17 This parameter is only available for BSC 3000. Timer to wait for handover to UTRAN complete message 2...255 seconds bts 12 DP
t3122 Class 3
Description : Minimum time that mobiles must wait before issuing a channel allocation request when an immediate assignment has failed. [0 to 255] seconds bts 10 seconds DP
t3168 Class 3
Description : This timer is used at the MS side to define when to stop waiting for the PUAS message after sending either a PRR message or a Channel Request in a PDAN. [0 (500 ms) 1 (1000 ms) 2 (1500 ms) 3 (2000 ms) 4 (2500 ms) 5 (3000 ms) 6 (3500 ms) 7 (4000 ms)] bts 0 DP V14
Value range :
Object : Default value : Type : Release :
477
t3172 Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Value of the timer started by the mobile on reception of a Packet Access Reject message (in seconds) [1 to 255] bts GPRS (SV407 - V12) 20 DP V12
t3192 Class 3
Description : Wait for DL TBF release after reception of the final block. This timer is used on the MS side to define when the MS received all the RLC data blocks. When the timer expires, the MS releases the resources associated with the TBF and begins to monitor its paging group (DRX mode). [0 (500 ms) 1 (1000 ms) 2 (1500 ms) 3 (0 ms) 4 (80 ms) 5 (120 ms) 6 (160 ms) 7 (200 ms)] bts DP 0 V14
Value range :
Object : Type : Default value : Release :
target Bda
Description : Target BDA for the On-line reset command See NTP < 130 >. Value range : [running / new / old]
"running" for "BDA Edition" reset on-line (i.e. basic BDA change without prototype BDA change) "new" or "old" for "BDA Version" reset on line (i.e. BSC upgrades with prototype BDA change)
478
bsc - On-line reset DP V11
teiBtsSiteManager Class 2
Description : TEI address of the site BCF in the LAPD protocol. In a BTS chain, the TEI addresses must be allocated in ascending order (TEI0, TEI1, TEI2, etc.), beginning with the BTS closest to the BSC. In a BTS loop configuration, the TEI addresses must be allocated in ascending order (TEI0, TEI1, TEI2, etc.), beginning with the BTS directly linked to the BSC that uses DTI board no.0 for the Abis link input. The following TEI values 3, 7, 11, 15, and 19 are forbidden when T1 PCMs on Abis interface are used. The relationship between internal E1 PCM TSs (DTI, PCMI or CPCMI) or BSC (DDTI) and external PCM TSs is the following:
E1 T1 E1 T1
1 1
2 2 18 14
3 3
5 4
6 5
7 6
9 7 25
10 8 26 20
11 9 27 21
12
13 10
14 11 30 23
15 12 31 24
16
17 13
19 20 21 22 23 24 15 16 17 18 19
28
29 22
E1 PCM TSs 4, 8, 12, 16, 20, 24, and 28 are not mapped onto T1 PCM TSs. The scheduled or "rendez-vous" TSs (=teiBtsSiteManager +1) cannot be defined on these internal E1 PCM TSs Value range : Depending on the BTS type, the value range is:

Object : Type : DP
[0 to 9] for a BTS 18000 [0 to 13] for an S12000 [0 to 15] for all other BTSs
btsSiteManager
479
Checks :
[C/M]:
The number of TEI addresses allotted to a LAPD channel is limited to maxTeiPerLapdCh (static configuration data). Values 3, 7, 11 and 15 are forbidden in T1 mode.
[C/M]:
teiLapdLink
Description : TEI address of the LAPD link in the LAPD protocol. It is updated by the OMC-R agent according to the TEI address allotted by the user to the entity (BCF, TRX/DRX, TCU) using the LAPD link. [0 to 127] lapdLink - Display DP
Value range : Object : Type : Restrictions :
[C/M]:
teiTransceiverEqpt Class 2
Description : Value range : TEI address of the TRX/DRX in the LAPD protocol. The value range is:

Object : Type : Checks : DP
[14 to 55], case of an S12000 [14 to 79], case of a BTS 18000 and a BSC 3000 [16 to 63], in other cases
transceiverEquipment
[C/M]:
The number of TEI addresses allotted to a LAPD channel is limited to maxTeiPerLapdCh (static configuration data). The TEI address is not assigned to another transceiverEquipment object dependent on the same bts object. HPRM does not support following TEIs: 14, 17, 18, 21, 22, 25, 34, 37, 42, 45, 50, 53, 64, 67, 70, 73, 76, 79 No mdScanner object refers to the transceiverEquipment object (no observation is running on the TRX/DRX or the parent cell). The parent bsc object is unlocked, the parent bts object and the transceiverEquipment object are locked.
[C/M]:
[C/M]:
[M]:
[M]:
480
teiTranscoder Class 2
Description : Value range : Object : Type : Checks : TEI address of the TCU in the LAPD protocol. [0 to 126] transcoder DP
[C/M]:
Bsc 3000: No check. The TEI address is not used by BSC 3000. 0 teiTranscoder 126
[C/M]:
temporaryOffset Class 3
Description : Negative offset applied during Penalty Time for re-selecting a cell (C2 criterion). This negative offset is applied during the entire penaltyTime duration and allows to prevent speeding mobiles from selecting the cell. Refer to the cellReselectOffset entry in the Dictionary. Value range : Object : Feature : Default value : Type : Release : [0 to 70, by steps of 10] dB bts AR 264 70 DP V8
terminal name
Description : Name of a terminal as defined in its profile (default is the logged-in users terminal). Do not fill in if this criterion is not to be selected. Value range : Object : Type : Checks : Note : [case sensitive] System session log - Filter DP
[A]:
The terminal is known to the OMC-R.
Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL object names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited.
481
terminal profile
Description : Value range : Object : Type : Checks : Identifier (name) of an OMC-R terminal [case sensitive, 1 character min.] terminal profile Id
[C]: [M/D]:
The name of a terminal is unique to the OMC-R. The terminal profile object is created.
text
Description : Comment to display before running the next command The Echo : text = blah blah blah command can be inserted anywhere in a command file, and as many times as necessary. The text is displayed as it is in session logs when the command file is run. Value range : Object : Type : [unlimited number of characters] commandFile - Echo command DP
text
Description : Value range : Object : Type : Contents of a short message. It is broadcast as it is. [93 characters max] short message DP
text
Description : Value range : Object : Type : Contents of a user message. It is sent as it is. [unlimited number of characters] user message DP
tFH or RWM Class 2

Description : Value range : Object : Presence or absence of the optional equipment "microwave terminal" in 4000 Outdoor. [Present / Absent] btsSiteManager
482
Type : Release :
DP V9
tGMMKeepAlive Class 3
Description : Value range : Configures the GMM Keep Alive mechanism. [0..64]

Object : Feature : Type : Release : bts
0: the feature is disabled (the same Keep Alive timer is used for data and GMM procedures) [1..63] (1 unit = 100 ms): enables the feature and sets the GMM Keep Alive timer duration. The recommended value is 5 64: the Keep Alive mechanism is disabled for GMM procedures
23038 - Disabling TBF Keep Alive DP V15
This BSS is using license

Description : Value range : Object : Indicates whether the BSC is using a 4K Erlangs license. [yes/no] md - Display 4K Erlangs Information bsc - Display 4K Erlangs Information Feature : AMR Feature Activation Control EDGE Feature Activation Control Release : V17
thresholdInterference Class 2
Description : List of four thresholds defined in ascending order, used to sort idle channels on the basis of measured interference levels. This attribute, together with the averagingPeriod attribute, allows to manage interferences in a radio cell. The classification is used by the radio resource allocator. The interference processing algorithm for a cell is as follows:
483
For each idle radio channel, the BTS permanently measures the signal strength level RXLEV. When averagingPeriod "Measurement results" messages have been received, the L1M function in the BTS calculates interference level averages, sorts the idle channels according to the five defined interference levels (Level 0 corresponds to the lowest interference level), and sends the information to the BSC.
The BSC tallies the interference levels and, if the temporary "interference" observation is running for the bsc object, sends the channelIdleLevelMax and channelIdleLevelEch counters every <mdGranularityPeriod> minutes to the OMC-R agent.
Refer also to C1619 permanent observation counters. Value range : Object : Default value: Type : Checks : [-128 to 0] dB handOverControl -100 -90 -80 -70 DP
[C/M]: [M]:
The thresholds are defined in ascending order. The parent bsc object is unlocked and the associated bts object is locked.
484
thresholdType
Description : Type of thresholds managed The startAlarmThreshold and endAlarmThreshold attribute values, which trigger permanent BSS observation counter threshold overflow messages, depend on the type of thresholds managed by the mdWarning object. Refer to these entries in the Dictionary. Value range : Object : Type : [thresholdLow / thresholdHigh] mdWarning if detectionFunction = "outOfRangeCounter" DP
timeBetweenHOConfiguration Class 3
Description : Whether the hoPingpongTimeRejection timer can be used in a BSS when processing handovers. Refer to bts object bts time between HO configuration and adjacentCellHandOver object hoPingpongTimeReject ion attributes in this Dictionary of Parameters. Value range : Object : Feature : Default value : Type : Release : [used / not used] bsc General protection against ping-pong handovers (TF821 - V12) used DP V9
timerGcchNotif Class 3
Description : Value range : Object : Default value : Feature : Type : Release : Time between two FACCH notifications. [0 to 65535] seconds signallingPoint 2 (recommended) ASCI DP GSM-R V15
485
timerPeriodicUpdateMS Class 3
Description : Value range : Object : Default value : Type : Remark : Time between two location update requests. [0 to 255] 1/10th of hour. "0" means that no periodic location update is requested. bts 60 DP The operator must be aware that the input of low values for this attribute causes an important traffic load during the location update procedures. For instance, entering the value "1" for this attribute leads to that all Mobiles will execute an update of 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 can directly map the LAPD link onto a PCM time slot. Value range : Object : Note : Type : Remark : [1 to 24] (GSM 1900/850 networks), [1 to 31] (other networks). lapdLink This parameter is only available for the lapdLink OML object on BSC 3000. DD The LAPD link with a radio site BCF always uses TSn = pcmTimeSlotNumber (radio site scheduled time slot). Refer to this entry in the Dictionary.
timeSlotNumber Class 2
Description : Value range : Object : Type : PCM time slot used by an SS7 channel on the A interface [1 to 24] signallingLink DP
486
Checks :
[C/M]:
The time slot is not already assigned on the A interface to a signallingLink or xtp object dependent on the same bsc object and is not mapped on the TS used by the OMC channel on the Ater interface. If the SS7 link uses PCMA link no.3 (pcmCircuitId), the timeslot is in the range [1 to 27] if the PCM link is an E1 link or in the range [1 to 20] if the PCM link is a T1 link. Since the last four time slots of that link are not mapped on the Ater interface, they are unusable (refer to the transcoderMatrix entry in the Dictionary).
[C/M]:
timeSlotNumber
Description : Value range : Object : Type : Checks : PCM time slot used by a terrestrial circuit on the A interface [1 to 24] (GSM 1900/850 networks), [1 to 31] (other networks). xtp DP
[C]:
The time slot is identical to the mscPcmTsNu mber component of the xtp object cic attribute (refer to this entry in the Dictionary). The time slot is not already assigned on the A interface to an xtp or signallingLink object dependent on the same bsc object, and is not mapped on the TS used by the OMC channel on the Ater interface. If the terrestrial circuit uses PCMA link no.3 (pcmCircuitId), the timeslot is in the range [1 to 27] if the PCM link is an E1 link or in the range [1 to 20] if the PCM link is a T1 link. Since the last four time slots of that link are not mapped on the Ater interface, they are unusable (refer to the transcoderMatrix entry in the Dictionary). This attribute cannot be modified due to its relationship with the mscPcmTsNumber component of the cic attribute.
[C]:
[C]:
Restrictions :
[M]:
487
tmu
Description : The Traffic Management Unit, which is responsible for managing the GSM protocol : it provides processing power for Call Processing, terminates GSM protocol (A, Abis and Ater interfaces), terminates low level GSM protocol (LAPD and SS7). [0 to 2147483646] tmu Id V13
tmuId
Description : Identifier of the tmu object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000. [0 to 2147483646] tmu DP V13
tnOffset class 2
Description : Allows to specify and control Timeslot Number (TN) difference between BTSs in case of network synchronization by GPS. Refer also to the fnOffset entry in this dictionary. Object : Value range : Type : Feature : Default value : Release : Note : btsSiteManager [0..7] DP Network Synchronization 0 V15 This parameter is optional. It is only available for BSC 3000 V15 and later, and applicable since BSC 3000 V15.1.1.
488
tNwExtUtbf Class 3
Description : Inactive period timer. Maximum time of inactivity during which the UL radio resources are not released. Value range : Object : Default value : Type : Feature : Checks : Release : [0..255] (1 unit = 20 ms) bts 0 DP Extended UL TBF
[M]:
tNwExtUtbf value must be greater than or equal to tUsfExt value.
V15
Total licenses for this OMC-R

Description : Number of licenses (RM Capacity or 4K Erlangs Information) configured on the OMC-R. [0..NNNN] (The range depends on the number of licenses configured, used in total and on certain objects) md - Display RM capacity bsc - Display RM capacity btsSiteManager - Display RM capacity md - Display 4K Erlangs Information bsc - Display 4K Erlangs Information Feature : AMR Feature Activation Control EDGE Feature Activation Control Release : V17
Total unused licenses

Description : Value range : Number of licenses free to be used or exported to another OMC-R. [0..NNNN] (The value can be negative when licenses have been exported from the OMC-R while all of them are used by objects)
489
Object :
md - Display RM capacity bsc - Display RM capacity btsSiteManager - Display RM capacity md - Display 4K Erlangs Information bsc - Display 4K Erlangs Information
Feature :
AMR Feature Activation Control EDGE Feature Activation Control
Release :
V17
traceConstraintList
Description : List of logical expressions that allow to filter the information to display. The following filter criteria are used: [bsPower / bssTraceType / bssTraceTypeUsed / establishmentCause / hoCauseClass / hoClauseValue / hoRrResult / mobileId / msPower / pcm / recordingEntity / rrCause / timeSlot / timingAdvance / tracedBts / traceRecId / traceReferenceC rit / trStartTime / trStopTime. / trxIdrxId]. See NTP < 130> . Object : Type : Trace data display DP
traceControl
Description : Identifier of a traceControl object defined with regard to the md object. It describes the Call tracing function of a BSC. A traceControl object is created in locked state. Unlock the object to start collecting data in the related BSC. Value range : Object : Type : [0 to 2147483646] traceControl Id
490
Checks :
[C]: [C/M/D]: [C/M/D]:
The traceControl object is not created for the md object. The application database of the related BSC is not being built. If the application database of the related BSC is built, the BSS/OMC-R link is established and no audit is in-progress in the BSC. The traceControl object is created.
Release : V8
[M/D]:
traceDayAccessed
Description : Date of data recording Date format entry forms are detailed in NTP < 130 >. Setting this parameter limits the display to trace data recorded on the specified day. Value range : Object : Type : [<date>] Trace data display DP
traceFileName
Description : Name of a call tracing or call path tracing data file on the OMC-R agent disks. The naming rules are described in NTP < 07 >. traceFileReadyRecord DP Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL object names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited.
Object : Type : Note :
491
traceInfoRequested
Description : List of information to display with respect to the type. See NTP < 129 >. Value range : [abisInfo / bsicInfo / bssMapInfo / btsInfo / ChannelInfo / cicInfo / dtapInfo / handoverInfo / manufacturerExtInfo A and Ater / manufacturerExtInfo Abis / measurementInfo / msClassmarkInfo / powerControlIn fo / rrInfo / timingAdvanceInfo / trxInfo / txPowerInfo] Trace data display DP
Object : Type :
traceReference
Description : Value range : Object : Type : Reference of a trace message received from the MSC. [0 to 63] (Phase I) [0 to 65535] (Phase II) traceFileReadyRecord DP
traffic PCM allocation priority Class 2

Description : Allocation priority of a TDMA frame on the covering site PCMs. This attribute is used in case of Abis PCM reconfiguration. Value range : Object : Type : Checks : Release : Note : [0 to 255] transceiver DP
V9
[M]:
The parent bsc object is unlocked and the parent bts object is locked.
"0" should be assigned to the highest priority frame(s).
transceiver
Description : Identifier of a transceiver object defined with regard to a bts object. It defines the parent transceiver object. Value range : Object : [0 to 15] channel
492
Type : Checks :
Id
[C]:
The transceiver object is created.
transceiver
Description : Identifier of a transceiver object defined with regard to a bts object. By definition, a TDMA frame is related to a cell, a cell is related to a site, and a site is related to a BSC. In all MMI commands, a transceiver object can be referred to by the sequence "siteName.cellName.transceiver", where siteName and cellName respectively identify the covering site and cell by name. A TDMA frame is brought in service on the network at creation time. It is working when the parent bts object is unlocked. Value range : Object : Type : Checks : [0 to 15] transceiver Id
[C]:
The number of TDMA frames per cell is limited to 16, regardless of the type of the BSC that controls the cell. The handOverControl and powerControl objects are created for the parent bts object. If the parent bts object describes a concentric cell, two transceiverZone objects are created for that object. If the application database of the related BSC is built, the parent bsc object is unlocked and the parent bts object is locked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.
[C]: [C]:
[C/D]:
[D]:
493
transceiver equipment class Class 2

Description : The class of a TRX/DRX. The class of a TRX/DRX sets, among others, its maximum transmission power. The attribute possible values have the following meaning:
Class 1 corresponds to GSM 900 class 5 or GSM 1800/1900 class 1 (20W to 40W transmitters). Class 2 corresponds to GSM 900 class 6 which is not supported or GSM 1800/1900 class 2 (10W to 20W transmitters).
When dual band (concentric cell) is used, the class of a TRX/DRX enables to distinguish which DRX and which TDMA are used in the outer zone or inner zone. Class 1 corresponds to a TDMA in the frequency band carrying BCCH so belonging to transceiverZone = 0 (large/outer zone). Class 2 corresponds to a TDMA in the frequency band not carrying BCCH so belonging to transceiverZone = 1 (small/inner zone). When cell is dualband, transceiver equipment class values differentiate TRX of the main band (for which the class value is 1) and TRX of the extended band (for which the class value is 2). Value range : Object : Type : Checks : [0 (reserved) / 1 / 2] transceiverEquipment DP
[M]:
Concentric cell: If the TRX/DRX is partnered with a TDMA frame, its class matches the TRX/DRX class allotted to the zone to which the TDMA frame belongs (refer to the next entry).
Release :
V9
transceiver zone Ref Class 2

Description : Value range : Identifier of the transceiverZone object that defines the zone to which a TDMA frame belongs in a concentric cell. [0 (large or outer zone) / 1 (small or inner zone)]
494
Object : Condition : Type : Checks :
transceiver To define if the covering cell is concentric DP
[C]: [M]:
The referenced transceiverZone object is created for the parent bts object. The parent bsc object is unlocked and the parent bts object is locked.
Release :
V9
Description : Identifier of a transceiverEquipment object defined with regard to a bts object. It defines the related transceiverEquipment object. Value range : Object : Type : Checks : [0 to 15] software Id
[C]:
The transceiverEquipment object is created.
Description : Identifier of a transceiverEquipment object defined with regard to a bts object. By definition, a TRX/DRX is related to a cell, a cell is related to a site, and a site is related to a BSC. In all MMI commands, a transceiverEquipment object can be referred to by the sequence "siteName.cellName.tr ansceiverEquipment", where siteName and cellName respectively identify the covering site and cell by name. Value range : Object : Type : [0 to 15] transceiverEquipment Id
495
Checks :
[C]:
The number of TRX/DRXs per site is limited to 24, regardless of the type of the BSC that controls the site. The number of TRX/DRXs per cell is limited to 16, regardless of the type of the BSC that controls the cell. The handOverControl and powerControl objects are created for the parent bts object. The referenced lapdLink objects (lapdLinkO MLRef and lapdLinkRSLRef) are created for the parent bsc object. If the application database of the related BSC is built, the parent bsc object is unlocked and the parent bts object is locked. If the application database of the related BSC is built, the parent bsc object is unlocked, the parent btsSiteManager and bts objects are locked, and the transceiverEquipment object is locked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command. No traceControl or callPathTrace object refers to the transceiverEquipment object (the BSC Call tracing or Call path tracing function does not monitor that object).
[C]:
[C]: [C]:
[C]:
[D]:
[D]:
[D]:
transceiver equipment class

Description : Class of the TRX/DRXs partnered with the TDMA frames of the zone. The class of a TRX/DRX sets, among others, its maximum transmission power. Refer to the previous entry. When dual band (concentric cell) is used, the class of a TRX/DRX enables to distinguish which DRX and which TDMA are used in the outer zone or inner zone. Class 1 corresponds to a TDMA in the frequency band carrying BCCH so belonging to transceiverZone = 0 (large/outer zone).
496
Class 2 corresponds to a TDMA in the frequency band not carrying BCCH so belonging to transceiverZone = 1 (small/inner zone). Value range : Object : Type : Restrictions : Release : Note : [1 / 2] transceiverZone DP
V9
[M]:
The transceiverZone objects are only created for bts objects that describe concentric cells.
transceiverZone
Description : Identifier of a transceiverZone object that describes the large zone or the small zone of a concentric cell. The transceiverZone objects are only significant for the bts objects that describe concentric cells. Two transceiverZone objects are created for each created concentric bts object; one describes the large or outer transmission zone, and the other describes the small or inner transmission zone. Value range : Object : Type : Checks : [0 (large or outer zone) / 1 (small or inner zone)] transceiverZone Id
[C]:
The associated bts object is created and the transceiverZone object is not created for that object. The number of transmission zones in a concentric cell equals 2. Each transceiverZone object is one-of-a -kind to the associated bts object. If the application database of the related BSC is built, the parent bsc object is unlocked and the associated bts object is locked. The parent bsc object is unlocked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.
[C]:
[C/D]:
[M]: [D]:
497
Release : V9
[D]:
No transceiver object refers to the transceiverZone object.
transcoder3GEqptId
Description : Identifier of the hardware transcoder 3G object class. This identifier is allocated by the MD-R at object creation. The only value allocated by the MD-R is 0. This attribute cannot be modified. This attribute is relevant for TCU 3000. [0 to 0] hardware transcoder 3G DP V13
transcoder
Description : Identifier of a transcoder object defined with regard to a bsc object. It defines the parent transcoder object. Value range : Object : Type : Checks : [0 to 33] (BSC 3000, E1 PCM network), [0 to 33] (BSC 3000, T1 PCM network) pcmCircuit (A interface) Id
[C]:
The transcoder object is created.
transcoder
Description : Value range : Object : Type : Identifier of a transcoder object defined with regard to a bsc object. [0 to 33] (BSC 3000, E1 PCM network), [0 to 33] (BSC 3000, T1 PCM network) transcoder Id
498
Checks :
[C]:
The number of remote transcoders linked to a BSC is limited to maxTranscdPerBsc (static configuration data). The software object related to the parent bsc object is created. The referenced lapdLink object (lapd LinkOMLRef) is created for the parent bsc object. If the application database of the related BSC is built, the parent bsc object is unlocked. If the application database of the related BSC is built, the parent bsc object is unlocked and the transcoder object is locked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command.
[C]: [C]:
[C]: [D]:
[D]:
transcoderArchitecture
Description : Indicates the TCU hardware configuration. This attribute is modified by the Manager. Value changes are notified to the Manager. This attribute can only be modified if the BDA is not built. [tcu3G / tcu3GOptical] transcoder
DP V13
transcoderId Class 2
Description : Value range : Object : Type : Checks : Identifier of the remote transcoder linked to the PCM link that carries the SS7 channel on the A interface. [0 to 33] signallingLink DP
[C/M]:
The referenced transcoder object is created and the pcmCircuit object used by the signallingLink object (pcmCircuitId) is related to that object.
499
transcoderId Class 2
Description : Value range : Object : Type : Checks : Identifier of the remote transcoder linked to the PCM link that carries the terrestrial circuit on the A interface. [0 to 33] xtp DP
[C/M]:
The referenced transcoder object is created and the pcmCircuit object used by the xtp object (pcmCircuitId) is related to that object.
transcoderMatrix
Description : Configuration of the TCU switching matrix = mapping PCM Ater TS <=> PCM A TS. This attribute describes the relation between the TSs of the four PCM A links used by the TCU (A interface) and the TSs of the PCM Ater link used by the TCU (Ater interface). The following tables show the correspondence when PCM E1 or T1 links are used. Object : Type : Restrictions : transcoder - Display DP
[C/M]:
PCM E1 links
TS PCM Ater 1 (LAPD channel) 2 3 4 5 6 7 8 9
PCM A 0 0 0 0 0 0 0 0
TS PCM A no equivalence 1 5 9 13 17 21 25 29 2 6 10 14 18 22 26 30 3 7 11 15 19 23 27 31 4 8 12 16 20 24 28
500
TS PCM Ater 9 10 11 12 13 14 15 16 17 17 18 19 20 21 22 23 24 25 25 26 27 28 29 30 31 -
PCM A 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3
TS PCM A 1 5 9 13 17 21 25 29 2 6 10 14 18 22 26 30 3 7 11 15 19 23 27 31
2 6 10 14 18 22 26 30 3 7 11 15 19 23 27 31 4 8 12 16 20 24 28
3 7 11 15 19 23 27 31 4 8 12 16 20 24 28 1 5 9 13 17 21 25 29
4 8 12 16 20 24 28 1 5 9 13 17 21 25 29 2 6 10 14 18 22 26 30
PCM T1 links
TS PCM Ater 1 (LAPD channel) 2 3 4 5 6 7
PCM A 0 0 0 0 0 0
TS PCM A no equivalence 1 5 9 13 17 21 2 6 10 14 18 22 3 7 11 15 19 23 4 8 12 16 20 24
501
TS PCM Ater 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 -
PCM A 1 1 1 1 1 1 2 2 2 2 2 2 3 3 3 3 3 3 1 5 9 13 17 21 1 5 9 13 17 21 1 5 9 13 17 21 2 6 10 14 18 22 2 6 10 14 18 22 2 6 10 14 18 22
TS PCM A 3 7 11 15 19 23 3 7 11 15 19 23 3 7 11 15 19 23 4 8 12 16 20 24 4 8 12 16 20 24 4 8 12 16 20 24
transparentSiteAttrib2 Class 2
Description : BSC 2nd class transparent attribute on bstSiteManager MO. This attribute is modified by the Manager. Value changes are notified to the Manager. Value range : Object : Type : Release : String [0 to 129] btsSiteManager DP V14
transparentTeiAttrib2 Class 2
Description : BSC transparent attribute on bts MO. Transmitted to SUP-TEI AO and then to the bts in LOAD_READY message. This attribute is modified by the Manager. Value changes are notified to the Manager. Value range : String [0 to 27]
502
bts DP V14
tResumeAck Class 3
Description : Timer used by the bsc waiting for an MS Resume Ack from a pcu. On timer expiry, the procedure is canceled. A TCH Release is sent to the MS, requesting this MS to send a Routing Area Update. [0..10] (1 unit = 100 ms). The recommended value is 1. 0 bsc GPRS / EDGE Suspend and Resume DP V15 Value 0 is considered as 1 by the BSC.
Value range : Default value : Object : Feature : Type : Release : Note :
trm
Description : Value range : Object : Type : The Transcoding Resource Module, which is responsible for GSM vocoding of the voice channels. [0 to 2147483646] trm Id
trmArchipelagoCalls
Description : Value range : Number of calls per archipelago and per TRM. List of 3 archipelagoes. Each of them is a list [coderAlgo, maximumNumberOfCalls, currentNumberOfCalls] with: coderAlgo: fullRatecoder / enhancedFullRateCoder / ctmEnhancedFullRateCode / amrFullHalfRateCoder maxi mumNumberOfCalls: 0 to 65535 currentNumberOfCalls: 0 to 65535 trm BSC/TCU e3 GET DATA enhancement DD V16
503
trmId
Description : Identifier of the trm object class. This identifier is allocated by the MD-R at object creation, depending on the shelf and slot numbers indicated by the BSC. This attribute cannot be modified. This attribute is relevant for BSC 3000 and TCU 3000. [0 to 2147483646] trm DP V13
tsConfiguration
Description : Configuration of the radio TDMA frame time slots. This dynamic attribute indicates, for each time slot, the reconfiguration state, the type of logical channel supported, the frequency channel used (absoluteRFChannelNo) if the time slot does not hop, the list of frequency channels used (mobileAllocation), the maio, and the hoppingSequenceNumber if the time slot hops. When frequency hopping is used if "reconfiguration state" is "true", it means that BSC has recalculated the frequency hopping law following the loss of one or several TRX (defence of TDMA carrying the BCCH. If "reconfiguration state" is "false", it means that the TDMA configuration is the original one. When frequency hopping is not used, this boolean has no meaning and would be set to "false". Value range : Object : Type : Remark : [true / false] transceiver DD Since the time slots are reconfigured after each dynamic reconfiguration of the hopping frequencies, the data can be different from those defined by the user when creating the channel objects. V8
Release :
504
tSuspendAck Class 3
Description : Timer used by the bsc waiting for an MS Suspend Ack message from a pcu. On timer expiry, the Suspend message is repeated. After three unsuccessful attempts, the procedure is canceled. [1..10] seconds. The recommended value is 1. 1 bsc GPRS / EDGE Suspend and Resume DP V15 Value 0 is considered as 1 by the BSC.
Value range : Default value : Object : Feature : Type : Release : Note :
tUsfExt Class 3
Description : Throughput optimization timer. On timer expiry, the USF allocation is optimized in order to give priority to active MSs that share the TS with the inactive MS. Value range : Object : Default value : Feature : Type : Checks : Release : [0..255] (1 unit = 20 ms) bts 0 Extended UL TBF DP
[C/M]:
tUsfExt value must be lower than or equal to tNwExtUtbf value.
V15
txPowerMaxReduction Class 2
Description : Value range : Object : Default value : Type : Checks : Remark : Maximum transmission power level allowed in a TDMA frame (attenuation versus bsTxPowerMax) per transceiver. [0 to 30 by step of 2] dB. "0" is the only value accepted. transceiver 0 DP
[C/M]:
The only value accepted by the system is 0 dB.
Since the system accepts only one value for this attribute, changing it has no meaning.
505
type
Description : Value range : Type of data to archive or restore. [faults / observations / trace data / backup / other data]

Object : Type :
Fault data are stored in the "/MD/notif" partition on the OMC-R agent disks. Observation data are stored in the "/MD/obs" partition on the OMC-R agent disks. Trace data are stored in the "/MD/trace_function" partition on the OMC-R agent disks. Backup data are stored on the OMC-R agent disks. Other data files are defined in the "/MD/config" partition on the OMC-R agent disks.
md - Archive DP
type

Object : Type :
Fault data are restored to the "/MD/restored/notif" partition on the OMC-R agent disks. Observation data are restored to the "/MD/restored/obs" partition on the OMC-R agent disks. Trace data are restored in the "/MD/restored/trace_funct ion" partition on the OMC-R agent disks. Other data files are restored to their source directory on the OMC-R agent disks.
md - Restore DP
506
type
Description : Value range : Type of data to archive or restore. [faults / observations / trace data / backup / backup without eft / PCUOAM / other data]

Object : 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 on the OMC-R manager disks. Trace data are stored in the "/CMN/base/save_rest" partition on the OMC-R manager. Backup data are stored on the OMC-R manager disks. Other data files are defined in the "/OMC/data" partition on the OMC-R manager disks.
omc - Archive DP
type

Object : 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" partition on the OMC-R manager disks. Trace data are restored to the "/CMN/base/save_rest" partition on the OMC-R manager disks. Other data files are restored to their source directory "/OMC/data" on the manager disks.
omc - Restore DP
type
Description : Value range : Type of observation report. [single observed instance / several observed instance]
single observed instance .......
several observed counters on a single object
507
several observed instance .......
single counter observed on several objects
type of data to be purged

Description : Value range : Object : Type : Release : Type of the OMC data to be purged. [traceData] omc - Data purge DP V10
type of display
Description : Value range : Object : Type : Release : Choice of the observation counter display mode. [Chart / Table / Text] report template DP V11
U
ulBepPeriod Class 2
Description : The parameter is used by BTS to derive the forgetting factor used in the UL to compute averaged MEAN-BEP and CV-BEP. [0 to 15] transceiver EDGE link adaptation (20219) 0 DP V15
ulGMSKMCS2UpperThreshold Class 3
Description : The parameter allows the operator to set the threshold between MCS2 and the next code in the UL GMSK Only Link Adaptation table. [0 to 255]
Value range :
508
bts EDGE link adaptation (20219) 0 (disabled MCS2 in the Link Adaptation Tables) DP V15
ulGMSKMCS3UpperThreshold Class 3
Description : The parameter allows to set the threshold between MCS3 and the next code in the UL GMSK Only Link Adaptation table. [0 to 255] bts EDGE link adaptation (20219) 0 (disabled MCS3 in the Link Adaptation Tables) DP V15
ulMCS2UpperThreshold Class 3
Description : Value range : Object : Feature : Default value : Type : Release : The parameter is used to set the threshold between MCS2 and the next code in the UL Link Adaptation table. [0 to 255] bts EDGE link adaptation (20219) 0 (disabled MCS2 in the Link Adaptation Tables) DP V15
509
Description : Value range : Object : Feature : Default value : The parameter is used to set the threshold between MCS8 and the next code in the UL Link Adaptation table. [0 to 255] bts EDGE link adaptation (20219) 0 (disabled MCS8 in the Link Adaptation Tables)
510
Type : Release :
DP V15
UMTS access min level Class 3

Description : Value range : Object : Default value : Type : Release : A minimum threshold for Ec/No for UTRAN FDD cell re-selection (3GPP reference: FDD_Qmin). V15: [-20 / -19 / -18 / -17 / -16 / - 15 / -14 / -13] dB V16: [-20 / -18 / -16 / -14 / -12 / -10 / -8 / -6] dB bts V15: -20 dB V16: -12 dB DP V14
UMTS reselection ARFCN Class 3

Description : Neighboring UMTS cell ARFCN. Although no control is performed on the value, it shall be indicated on the OMC-R display as a comment that a UTRAN ARFCN FDD is from 10562 to 10838 (3GPP reference: FDD_Qmin). Value range : Object : Default value : Type : Release : [0 to 16383] bts 0 DP V14
UMTS reselection offset Class 3

Description : Value range : Object : Default value : Type : Release : Applies an offset to RLA_C for cell re-selection to access technology / mode FDD (3GPP reference: FDD_Qmin). [infinity / -28 / -24 / -20 / -16 / -12 / -8 / -4 / 0 / 4 / 8 / 12 / 16 / 20 / 24 / 28] dB bts infinity dB DP V14
511
UMTS search min level Class 3

Description : Value range : Object : Default value : Type : Release : Search for 3G cell if signal level is below or above the threshold (3GPP reference: Qsearch_I). [<-98 / <-94 / <-90 / <-86 / <-82 / <-78 / <-74 / Always / >-78 / > -74 / >-70 / >-66 / >-62 / >-58 / >-54 / Never] dB bts <-98 dB DP V14
unequippedCircuit Class 1
Description : Value range : Object : Feature : Default value : Type : Checks : Remark : Release : Whether the UNEQUIPPED CIRCUIT messages are used (Phase II compliance). [false / true] signallingPoint Unequipped circuit and circuit group block (UF1169.1 V12) False DP
[C/M]:
The only accepted value is "false" in V10 and V11.
Since the system accepts only one value for this attribute in V10 and V11, changing it has no meaning. V8
unit
Description : Value range : Object : Type : Note : The name that identifies the unit. String [1 to 2 characters] transcoder, controlNode, interfaceNode, hardware transcoder 3G DD This parameter is applicable for TCU3G only.
512
unknownNCellWarning Class 3
Description : Whether feedback of measurements performed by mobiles on neighbor cells that are unknown to the BSC is allowed. When feedback of measurements is enabled, notifications with codano 1260 are generated. These notifications indicate that measurements are performed on cells which use the same BCCH as a neighbor cell of the serving cell but have different BSICs. Value range : Object : Default value : Type : [enabled / disabled] bts disabled DP
unmasked users alarms Class 2

Description : Configuration of the user (unprotected) external alarm loops controlled by the BTS. When an alarm is unmasked, it means the relevant equipment is monitored by the BTS. There are 6 user alarms per cabinet.
on the S8000 Outdoor (up to 18 user alarms = 3 cabinets * 6 user alarms per cabinet). on the S8002 BTS (up to 6 user alarms = 1 cabinet * 6 user alarms)
A user alarm is used when an external equipment is inserted in the BTS (for instance a microwave terminal) and does not require a new DLU. Value range : [All masked, Base 1, Base 1 to 2, Base 1 to 3, Base 1 to 4, Base 1 to 5, Base 1 to 6, Base 1 to 6 Ext0 1, Base 1 to 6 Ext0 1 to 2, Base 1 to 6 Ext0 1 to 3, Base 1 to 6 Ext0 1 to 4, Base 1 to 6 Ext0 1 to 5, Base 1 to 6 Ext0 1 to 6, Base 1 to 6 Ext0 1 to 6 Ext1 1 to 2, Base 1 to 6 Ext0 1 to 6 Ext1 1 to 4, Base 1 to 6 Ext0 1 to 6 Ext1 1 to 6] For instance:
513

Base 1: the first user alarm in the Base cabinet is unmasked Base 1 to 2: the first and second user alarm in the Base cabinet are unmasked Base 1 to 6 Ext0 1: The 6 user alarms in the Base cabinet and the first one in the Extension cabinet 0 are unmasked
btsSiteManager DP V9
upAckTime Class 3 (packetAckTime)

Description : Value range : Object : Feature : Default value : Type : Release : DP V12 Defines the DL TBF pre-establishment timer. [1 to 64] steps 100 ms for uplink transfer transceiver GPRS (SV407 - V12 and TF1220 - V12.4c)
upgradeStatus
Description : Stands whether an upgrade is complete, or is whether or not it is still in progress. This attribute is dynamically managed by the BSS. Value changes are notified to the manager. Value range : [notInProgress / inProgress / performed / toBeUpgraded / aborted; duplicateInProgress; frozen; failed; flashUpdated; Unknown] transcoder, atmRm, cc, cem, controlNode, iem, iom, interfaceNode, omu, tmu, trm, hardware transcoder 3G, sw8kRm, btsSiteManager, transceiverEquipment AR 1209 - V13.1 DD V13
Object :
Feature : Type : Release :
514
uplinkPowerControl Class 3
Description : Value range : Object : Default value : Type : Release : Whether power control in the MS-to-BTS direction is authorized at cell level. [enabled / disabled] powerControl enabled DP V8
uplinkPwrCtrlDuringUTDOA Class 3
Description : Value range : Object : Default value : Type : Release : Reserved for future use. [enabled / disabled] bsc disabled DP V16
uplinkReply Class 3
Description : Defines the use of the uplink-reply procedure, which applies to VBS and VGCS calls for radio resources optimization. [0 to 2] with:
Value range :

0: Disabled (recommended value for non-GSM-R customers) 1: Enabled on all group calls (recommended value for GSM-R customers) 2: Enabled on all group calls except on emergency group calls (optional value for GSM-R customers)
bsc ASCI 0 DP GSM-R V15
515
uplinkReplyTimer Class 3
Description : Value range : Timer value of the uplink-reply procedure. [0 to 65535] seconds, with:

Object : Feature : Default value : Type : Release : bts
0: the feature is not allowed 6: recommended minimum value 120: recommended value
ASCI 120 DP GSM-R V15
uRxLevDLP Class 3
Description : Upper strength threshold for BTS txpwr decrease for step by step algorithm. It is greater than lRxLevDLP. Value range : Object : Default value : Type : [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB powerControl -85 to -84 dB DP
uRxLevULP Class 3
Description : Upper strength threshold for MS txpwr decrease for step by step algorithm. It is greater than lRxLevULP. Value range : Object : Default value : Type : Note : [less than -110, -110 to -109, ... , -49 to -48, more than -48] dB powerControl -85 to -84 dB DP This parameter is significant only when the BTS uses the standard "step by step" power control algorithm.
516
uRxQualDLP Class 3
Description : Upper quality threshold to reduce BTS txpwr for step by step algorithm. It is lower than or equal to lRxQualDLP. Value range : Object : Default value : Type : Checks : Note : [less than 0.2, 0.2 to 0.4, 0.4 to 0.8, ... , 6.4 to 12.8, more than 12.8] % powerControl 0.2 to 0.4 DP uRxQualDLP lRxQualDLP
[M]:
This parameter is significant only when the BTS uses the standard "step by step" power control algorithm.
uRxQualULP Class 3
Description : Upper quality threshold to reduce MS txpwr for step by step algorithm. It is lower than or equal to lRxQualULP. Value range : Object : Default value : Type : Checks : Note : [less than 0.2, 0.2 to 0.4, 0.4 to 0.8, ... , 6.4 to 12.8, more than 12.8] % powerControl 0.2 to 0.4 DP uRxQualULP lRxQualULP
[M]:
This parameter is significant only when the BTS uses the standard "step by step" power control algorithm.
usageState
Description : Activity state of the Call path tracing function in the BSC. Refer to the endSessionCriteriaType entry in the Dictionary and the operationalState entry related to the callPathTrace object which describes the possible state parameter combinations for this type of object. Value range : [idle / busy ]
idle .............
The PCM time slot that conveys the terrestrial circuit is traffic-free.
517
Object : Type :
busy .............
The PCM time slot conveys the terrestrial circuit is working and carrying traffic.
callPathTrace DP
usageState
Description : ISO state Refer to the operationalState entry related to the xtp object which describes the possible state parameter combinations for this type of object. Value range : [idle / busy / active]

Object : Type : xtp DD
idle ............. busy .............
The PCM time slot that conveys the terrestrial circuit is traffic-free. The PCM time slot conveys the terrestrial circuit is working and carrying traffic. The PCM time slot that conveys the terrestrial circuit is active.
active ...........
use default list

Description : Value range : Object : Type : Release : Whether the default counter list has to be used. [yes] bscCounterList DP V11
user name
Description : Name of an OMC-R user as defined in the users profile (default is the logged-in users name). Do not fill in if this criterion is not to be selected. Value range : Object : Type : [case sensitive] System session log - Filter DP
518
Checks : Note :
[A]:
The related user profile object is created on the OMC-R.
user profile
Description : Value range : Object : Type : Checks : Identifier (name) of an OMC-R user. [case sensitive, 2 characters min] user profile DP
[C]: [M/D]:
The name of a user is one-of-a-kind to the OMC-R. The user profile object is created.
username
Description : Value range : Type : Object : Note : Name of the OMC-R user, as defined in the users profile, who created the job. [case sensitive] DD job Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited.
username
Description : Value range : Object : Type : Note : Name of the OMC-R user, as defined in the users profile, who created the associated job. [case sensitive] jobResult DD Use only alphanumeric characters (30 max.), beginning with a letter and is case sensitive, for ALL parameter names (TRX, BSC, BTS, BTSSM, etc.). All other symbols/characters are prohibited.
519
usfGranularity Class 3
Description : Value range : Object : Feature : Default value : Type : Release : The type of granularity supported by PCU when dynamic allocation is available. [0] bts EDGE dynamic allocation (20230) 0 (granularity 1) DP V15
V
voiceBroadcastService Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Authorize Voice Broadcast Service. [enabled / disabled] signallingPoint (GSM-R V12) disabled DP V12
voiceGroupCallService Class 3
Description : Value range : Object : Feature : Default value : Type : Release : Authorize Voice Group Call Service. [enabled / disabled] signallingPoint (GSM-R V12) disabled DP V12
vSWR meter Class 2

Description : Value range : Object : Type : Release : Presence or absence of the optional equipment "voltage stationary wave rate meter" in S8000 Indoor or Outdoor. [Present / Absent] btsSiteManager DP V9
520
W
workstation name
Description : Value range : Object : Type : Checks : Note : Name of a workstation as defined in its profile (default is the logged-in users workstation). [case sensitive] omc - Display workstation markers DP
[A]:
The terminal profile object describing the workstation is created on the OMC-R.
wPSManagement Class 3
Description : Value range : Object : Feature : Default value : Type : Checks : Release : WPS feature is enabled or disabled. [disabled 0 ; enabled 1] bsc WPS queuing managment (22463) Disabled DP
[A]:
V15
wPSQueueStepRotation Class 3
Description : One out of the WPSQueueStepRotation value to first have an evaluation of the WPS queues in the radio resource allocator. [1 to 10] bts WPS public access bandwidth protection (22465) 4 DP
Value range : Object : Feature : Default value : Type : Checks : Release :
[A]:
V15
521
X
X25 port 0 operational
Description : Operational State of the OMU module external X.25 port 0. ISO operational state (enabled/disabled). This attribute is dynamically managed by the BSS. Value changes are not notified to the Manager. This attribute is relevant for BSC 3000. Value range : Object : Feature : Type : Release : [enabled / disabled] omu AR 1209 - V13.1 DD V13
X25 port 1 operational

Description : Operational State of the OMU module external X.25 port 1. ISO operational state (enabled/ disabled). This attribute is dynamically managed by the BSS. Value changes are not notified to the Manager. This attribute is relevant for BSC 3000. Value range : Object : Feature : Type : Release : [enabled / disabled] omu AR 1209 - V13.1 DD V13
xtp
Description : Value range : Object : Type : Checks : Identifier of an xtp object (eXchange Termination Point) defined with regard to a bsc object. [0 to 2147483646] xtp Id
[C]:
The software object related to the bsc object is created.
522
[C/M]:
The referenced pcmCircuit object (pcmCircuitId) is assigned to the A interface and depends on the same transcoder object (transcoderId) as the xtp object. The time slot used by the xtp object (timeSlotNumber) is identical to the mscPcmTsNumber component of the cic attribute. The referenced PCM,TS pair (pcmCircuitId and timeSlotNumber) is not already assigned to an xtp or signallingLink object dependent on the same transcoder object, and the time slot is not mapped on the TS used by the OMC channel on the Ater interface. If the terrestrial circuit uses PCMA link no.3 (pcmCircuitId), the timeSlotNumber is in the range [1 to 27] if the PCM link is an E1 link or in the range [1 to 20] if the PCM link is a T1 link. Since the last four time slots of that link are not mapped on the Ater interface, they are unusable (refer to the transcoderMatrix entry in the Dictionary). If the application database of the related BSC is built, the parent bsc object is unlocked. If the application database of the related BSC is built, the parent bsc object is unlocked and the xtp object is locked. If the application database of the related BSC is not built, it has been reset by an Off line reset BDA command. No traceControl or callPathTrace object refers to the xtp object (the Call tracing and Call path tracing functions do not monitor that object). The cic and timeSlotNumber attributes of an xtp object cannot be modified.
[C]:
[C/M]:
[C/M]:

Restrictions :
[C]: [D]:
[D]:
[D]:
[M]:
Z
zI bss
Description : List of selected BSCs that defines a BSS zone of interest. Enter "all" to include all the BSCs created on the OMC-R. If the ZI bss list should include only a subset of BSCs, fill in the list as follows:
523
The Add button allows to add a BSC to the list. The Delete button allows to remove selected BSCs from the list.
A BSS terminal zone of interest allows users to filter the unsolicited messages (output domain) that can be output on the terminal outside users work sessions according to the BSS entities that send them. Object : Type : Note : terminal profile DP The user can enter a BSC in the list that is not created yet. When it is created, this BSC will be handle as the other BSCs already created.
zI bss
Description : List of selected BSCs that defines a BSS zone of interest. Enter "all" to include all the BSCs created on the OMC-R. If the ZI bss list should include only a subset of BSCs, fill in the list as follows:
The Add button allows to add a BSC to the list. The Delete button allows to remove selected BSCs from the list.
A BSS users zone of interest defines the BSS entities the user is entitled to work on. It allows to filter both the MMI commands they can enter (command domain) according to the objects managed by these commands and the unsolicited messages (output domain) they have access to according to the BSS entities that send them. Object : Type : Note : user profile DP The user can enter a BSC in the list that is not created yet. When it is created, this BSC will be handle as the other BSCs already created.
524
zone frequency hopping Class 2

Description : Whether frequency hopping is authorized in the zone. If frequency hopping is not allowed in a zone, the channel objects that describe the radio time slots of the TDMA frames used in the zone cannot be allowed to hop. Value range : Object : Default value : Type : Checks : Release : Note : [hopping / not hopping] transceiverZone not hopping DP
V9
[M]:
zone frequency threshold Class 2

Description : Value range : Object : Default value : Type : Checks : Release : Note : Minimum number of frequencies needed to allow frequency reconfiguration in the zone. [1 to 64] transceiverZone 1 DP
V9
[M]:
zone Tx power max reduction Class 2

Description : Value range : Object : Default value : Type : Attenuation vs bsTxPowerMax that defines the maximum TRX/DRX transmission power in the zone. [0 to 55] dB transceiverZone 0 DP
525
Checks :
[C/M]:
zone Tx power max reduction equals zero if the transceiverZone object describes the cell outer zone. It is greater than zero if the transceiverZone object describes the cell inner zone. The parent bsc object is unlocked and the associated bts object is locked.
Release : Note : V9
[M]:
526
527

This appendix categorizes new configuration parameters and objects by release.
A.1 New V17 parameters

Parameter adaptiveReceiver administrativeState administrativeState availabilityStatus availabilityStatus bssPagingCoordination cId compressedModeUTRAN diversityUTRAN dynamicAbis earlyClassmarkSendingUTRAN fDDARFCN fDDMultiratReporting fDDReportingThreshold fDDReportingThreshold2 gsmToUMTSServiceHo gprsPreemptionForHR hoMarginUTRAN hoMarginAMRUTRAN hoMarginDistUTRAN hoMarginRxLevUTRAN Object transceiver hsaRc hsaRcTcu hsaRc hsaRcTcu bts adjacentCellUTRAN bts adjacentCellUTRAN btsSiteManager bts adjacentCellUTRAN bts handoverControl handoverControl bsc bsc adjacentCellUTRAN adjacentCellUTRAN adjacentCellUTRAN adjacentCellUTRAN
528
Parameter hoMarginRxQualUTRAN hoMarginTrafficOffsetUTRAN hoPingpongCombinationUTRAN hoPingpongTimeRejectionUTRAN hoRejectionTimeOverloadUTRAN hsaPcmList hsaPcmList Licenses needed to put object in service Licenses needed to put object in service Licenses needed to put object in service Licenses used by this object Licenses used by this object Licenses used by this object locationAreaCodeUTRAN mobileCountryCodeUTRAN mobileNetworkCodeUTRAN Number of xtp under this BSS Number of xtp under this BSS offsetPriorityUTRAN operationalState operationalState positionInShelf positionInShelf qsearchC reportTypeMeasurement rNCId scramblingCode rxLevDLPbgtUTRAN rxLevMinCellUTRAN servingBandReporting ServingBandReportingOffset shelfNumber shelfNumber signallingLink field
Object adjacentCellUTRAN adjacentCellUTRAN adjacentCellUTRAN adjacentCellUTRAN bsc hsaRc hsaRcTcu Display RM Capacity - md Display RM Capacity - bsc Display RM Capacity - btsSiteManager Display RM Capacity - md Display RM Capacity - bsc Display RM Capacity - btsSiteManager adjacentCellUTRAN adjacentCellUTRAN adjacentCellUTRAN Display 4K Erlangs - md Display 4K Erlangs - bsc adjacentCellUTRAN hsaRc hsaRcTcu hsaRc hsaRcTcu handoverControl bts adjacentCellUTRAN adjacentCellUTRAN adjacentCellUTRAN adjacentCellUTRAN bts handoverControl hsaRc hsaRcTcu signallingLinkSet
529
Parameter signallingLinkResourcesStates signallingLinkResState slkAResource field slkAssociatedTmuPortPosition slkAssociatedTmuPortPosition field slkATerResource slkATerResource field smartPowerManagementConfig smartPowerSwitchOffTimer standbyStatus standbyStatus standbyStatus synchronizingHsaRc t3121 This BSS is using license This BSS is using license Total licenses for this OMC-R Total licenses for this OMC-R Total licenses for this OMC-R Total unused licenses Total unused licenses Total unused licenses
Object signallingLinkSet signallingLinkSet signallingLinkSet signallingLink signallingLinkSet signallingLink signallingLinkSet powerControl powerControl hsaRc hsaRcTcu TMU bsc bts Display 4K Erlangs - md Display 4K Erlangs - bsc Display RM Capacity - md Display 4K Erlangs - md Display RM Capacity - bsc Display 4K Erlangs - bsc Display RM Capacity - btsSiteManager Display RM Capacity - md Display 4K Erlangs - md Display RM Capacity - bsc Display 4K Erlangs - bsc Display RM Capacity - btsSiteManager

Parameter aterLapd bckgDLLayer3WindowSize channelReleaseonAbisFailure eGPRSlrUlActivation enableRepeatedFacchFr facchPowerOffset lsaRc bsc bts bts bts bts Object
530
Parameter frPowerControlTargetModeDl hrPowerControlTargetModeDl interferenceMatrixRunningOnBts interferenceMatrixRunningOnBsc minNbOfJokersPerConnectedMain monitoredObjectClass nACCActivation packetFlowContext packetSiStatus pcuCellState pfcActivation pfcArp1ConversationalCSCallProtection pfcArp1StreamingCSCallProtection pfcArp2ConversationalCSCallProtection pfcArp2StreamingCSCallProtection pfcArp3ConversationalCSCallProtection pfcArp3StreamingCSCallProtection pfcFlowControlActivation pfcMinNrtBandwidthPerTs pfcMinNumberOfJokersforTsGuaranteedBitR ate pfcNrtRequestedDnMbrCounterThreshold pfcNrtRequestedUpMbrCounterThreshold pfcPreemptionRatioGold pfcPreemptionRatioSilver pfcRtDowngradeAllowed pfcRtRequestedDnGbrCounterThreshold pfcRtRequestedUpGbrCounterThreshold pfcT6 pfcT8 pfcTsGuaranteedBitRateDl pfcTsGuaranteedBitRateUl privilegedCell sacchPowerOffset
Object PowerControl PowerControl bts bsc transceiver mdWarning bts powerControl bts pcu bts powerControl powerControl powerControl powerControl powerControl powerControl bts transceiver transceiver powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl bts bts
531
Parameter sacchPowerOffsetSelection sigPowerOverboost trmArchipelagoCalls uplinkPwrCtrlDuringUTDOA bts bts trm bsc
Object

Parameter allocPriorityTable allocPriorityTimers amrUlHrAdaptationSet amrDlHrAdaptationSet amrUlFrAdaptationSet amrDlFrAdaptationSet available synchronization sources beacBatteryRemoteController Presence batteryRemoteControllerPres ence bEPPeriod bscHighSwitchingCapacity bssSccpConnEst bssSccpInactRx bssSccpInactTx bssSccpRelease bssSccpSubSysTest btsSMSynchroMode callDropActivation concentricCell cpueNumber css7LocalSubSystemNumber css7RemoteSubSystemNumb er current synchronization mode dARPPh1Priority bts bts bts bts bts bts bts btsSiteManager btsSiteManager bts bsc signallingPoint or signallingLinkSet signallingPoint or signallingLinkSet signallingPoint or signallingLinkSet signallingPoint or signallingLinkSet signallingPoint or signallingLinkSet btsSiteManager bts bts btsSiteManager signallingLinkSet signallingLinkSet bts transceiver Object
532
Parameter degradedCause degradedCause delivery distributionActivation distributionDuration distributionQualityThreshold distributionTime diversity dlGMSKMCS2UpperThreshold dlGMSKMCS3UpperThreshold dlMCS2UpperThreshold dlMCS3UpperThreshold dlMCS5UpperThreshold dlMCS6UpperThreshold dlMCS7UpperThreshold dlMCS8UpperThreshold edgeDataServiceType edgeFavor eDGEMixity egprsServices emergencyThreshold agpsTimer estimatedSiteLoad extUtbfNoData fERThreshold1 fERThreshold2 fERThreshold3 fERThreshold4 filteredTrafficCoefficient floor fnOffset fullDlKa gprsNetworkModeOperation gprsState bts transceiver bts bts bts bts bts bts bts bts bts bts bts bts bts bts transceiver transceiver bts bts signallingPoint bsc btsSiteManager bts bts bts bts bts bts bts btsSiteManager bts bts bts
Object
533
Parameter gprsState initialMCSDL initialMCSUL jokerPerMainTarget mainNetworkBand masterBtsSMId msPowerClassToggle nbLargeReuseDataChannels numberOfJokerDS0 nUsfExt nwExtUtbf onePhaseAccess onePhaseDnMsCapability onlyExtUtbf reportTypeMeas rLCPolling sGSNRelease standardIndicator suspendResumeActivation systemInfoType2 tGMMKeepAlive timerGcchNotif tnOffset tNwExtUtbf tResumeAck tSuspendAck tUsfExt ulBepPeriod ulGMSKMCS2UpperThreshold ulGMSKMCS3UpperThreshold ulMCS2UpperThreshold ulMCS3UpperThreshold ulMCS5UpperThreshold ulMCS6UpperThreshold transceiver transceiver transceiver transceiver bsc btsSiteManager bts bts transceiver bts bts bts bts bts bts bts bts bts bsc bts bts signallingPoint btsSiteManager bts bsc bsc bts transceiver bts bts bts bts bts bts
Object
534
Parameter ulMCS7UpperThreshold ulMCS8UpperThreshold uplinkReply uplinkReplyTimer usfGranularity wPSManagement wPSQueueStepRotation bts bts bsc bts bts bsc bts
Object

Parameter peakThroughputLimitation upQoSCriterion dwQoSCriterion minThroughputGold minThroughputSilver minThroughputBronze preemptionRatioGold preemptionRatioSilver voicePreemptionGold voicePreemptionSilver voicePreemptionBronze admissionCtrlGold admissionCtrlSilver admissionCtrlBronze frPowerControlTargetMode hrPowerControlTargetMode powerIncrStepSizeDL powerIncrStepSizeUL powerRedStepSizeDL powerRedStepSizeUL gsmToUmtsReselection uMTSSearchLevel uMTSReselectionOffset uMTSAccessMinLevel powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl powerControl bts bts bts bts Object
535
Parameter uMTSReselectionARFCN amrAdaptationSet hrCellLoadEnd hrCellLoadStart selfAdaptActivation hrAmrPriority nbOfFramesForFER rxLevRxQualDistributionActiv ation rxQualThresholdDistribution transparentTeiAttrib2 amrDirectAllocIntRxLevDL amrDirectAllocIntRxLevUL amrDirectAllocRxLevDL amrDirectAllocRxLevUL amrFRIntracellCodec amrHRIntercellCodec amrHRToFRIntraCodec amrReserved1 amrReserved2 amriRxLevDLH amriRxLevULH capacityTimeRejection enhCellTieringConfiguration nCapacityFRRequestedCodec offsetNeighbouringCell nFRRequestedCodec nHRRequestedCodec pRequestedCodec minTimeQualityIntraCellHO rxQualAveBeg servingFactorOffset adjacentCellReselectionId adjacentCellHandOverId bts bts bts bts bts transceiver bts bts bts bts handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl handOverControl
Object
adjacentCellReselection adjacentCellHandOver
536
Parameter hoMarginAMR bscCapacityReduction frAmrPriority lcsType sIkAssociatedTmuPortPosition sIkATerResource transparentSiteAttrib2 dynamicAgprsAllowed cCCHGprsAtBtsLevel agprsFilterCoefficient t3168 t3192 flowControlMaxDelay
Object adjacentCellHandOver bsc, signallingPoint transceiver bsc signallingLink signallingLink btsSiteManager pcu bts bts bts bts pcusn
537

This appendix presents BSS parameters per feature.
B.1 AMR based on traffic filteredTrafficCoefficient (bts) B.2 AMR Optimizations amrDlFrAdaptationSet (bts) amrDlHrAdaptationSet (bts) amrUlFrAdaptationSet (bts) amrUlHrAdaptationSet (bts) B.3 BSC/TCU 3000 administrativeState (atmRm, cc, cem, controlNode, hardware bsc
3G, hardware transcoder 3G, iem, interfaceNode, lsaRc, mms, omu, sw8kRm, tmu, trm, hsaRc, hsaRcTcu, iom)
availabilityStatus (hsaRcTcu) operationalState (atmRm, cc, cem, controlNode, hardware bsc 3G, hardware transcoder 3G, iem, interfaceNode, lsaRc, mms, omu, sw8kRm, tmu, trm, hsaRc, hasRcTcu, iom) cTU cable (iem) hsaPcmList (hsaRcTcu, iom) hsaRc Reference (iom) interOmuEtherlinkOper (controlNode) lsaPcmList (iem, lsaRc)
538
lsaRc Reference (iem) mmsUsage (mms) numberOfEnabledHDLCPorts (iem, tmu) port Ethernet operational (omu) port Ethernet status (omu) port 0 X25 status (omu) port 1 X25 status (omu) positionInShelf (atmRm, cc, cem, iem, hsaRc, hsaRcTcu, lsaRc, mms, omu, sw8kRm, tmu, trm, iom, hsaRc) shelfNumber (hsaRc, hsaRcTcu, iem, iom, lsaRc) standbyStatus (hsaRc, hsaRcTcu, iem, iom, lsaRc)
B.4 BSC 3000 cell group management/load balancing associatedTMUPosition (btsSiteManager, signallingLinkSet,
transcoder, pcu)
B.5 BSC 3000 switching increase capacity bscHighSwitchingCapacity (bsc) B.6 BSC overload management processorLoadSupConf (bsc) B.7 Dualband cell management biZonePowerOffset (adjacentCellHandOver) biZonePowerOffset (handOverControl) concentric cell (bts) msTxPwrMax2ndBand (bts) standard indicator AdjC (adjacentCellHandover) standard indicator AdjC (adjacentCellReselection) standardIndicator (bts)
B.10 EDGE link adaptation
539
B.8 EDGE dynamic allocation eDGEMixity (bts) usfGranularity (bts) B.9 EDGE traffic management bEPPeriod (bts) edgeFavor (transceiver) egprsServices (bts) initialMCSDL (transceiver) initialMCSUL (transceiver) jokerPerMainTarget (transceiver) sGSNRelease (bts) B.10 EDGE link adaptation dlGMSKMCS2UpperThreshold (bts) dlGMSKMCS3UpperThreshold (bts) dlMCS2UpperThreshold (bts) dlMCS3UpperThreshold (bts) dlMCS5UpperThreshold (bts) dlMCS6UpperThreshold (bts) dlMCS7UpperThreshold (bts) dlMCS8UpperThreshold (bts) ulBepPeriod (transceiver) ulGMSKMCS2UpperThreshold (bts) ulGMSKMCS3UpperThreshold (bts) ulMCS2UpperThreshold (bts) ulMCS3UpperThreshold (bts) ulMCS5UpperThreshold (bts) ulMCS6UpperThreshold (bts) ulMCS7UpperThreshold (bts) ulMCS8UpperThreshold (bts)
540
B.11 GSM-R V12 additional supervised PCM 0 (btsSiteManager) additional supervised PCM 1 (btsSiteManager) additional supervised PCM 2 (btsSiteManager) additional supervised PCM 3 (btsSiteManager) additional supervised PCM 4 (btsSiteManager) additional supervised PCM 5 (btsSiteManager) additional unmasked users alarms (btsSiteManager) eMLPPThreshold (signallingPoint) nCHPosition (bts) preemptionAuthor (signallingPoint) preemptionConfiguration (signallingPoint) voiceBroadcastService (signallingPoint) voiceGroupCallService (signallingPoint) B.12 GSM-R V15 emergencyThreshold (signallingPoint) msPowerClassToggle (bts) timerGcchNotif (signallingPoint) uplinkReply (bsc) uplinkReplyTimer (bts) B.13 GPRS (SV407 - V12) administrativeState (pcu) associatedInterface (lapdLink) availabilityStatus (pcu) availabilityStatus (pcusn) bscGprsActivation (bsc) bscRefList (pcusn) bsCvMax (bts) btsSensitivity (bts)
B.13 GPRS (SV407 - V12)
541
btsSensitivityInnerZone (bts) channelType (channel) codingScheme (transceiver) drxTimerMax (bts) dwAckTime (transceiver) geographical coordinates (pcusn) gprsCellActivation (bts) gprsPermittedAccess (bts) lapdConcentration (lapdLink) lapdTerminalNumber (lapdLink) longTbfLossThroughput (bts) longTbfSizeThreshold (bts) maxBsTransmitPowerInnerZone (bts) maxDnTbfP1P2Threshold (bts) maxDnTbfPerTs (bts) maxDwAssign (bts) maxNbrPDAAssig (transceiver) maxNbrPUDWithoutVchange (transceiver) maxNbrRLCEmptyBlock (transceiver) maxUpTbfP1P2Threshold (bts) maxUpTbfPerTs (bts) msCapWeightActive (bts) muxNumber (pcusn) n3103 (bts) n3105max (transceiver) nAvgl (bts) nAvgT (bts) nAvgW (bts) nbrFreeTchBeforeAnticipation (bts) nbrFreeTchToEndAnticipation (bts) nbrTch (pcu) operationalState (pcu)
542
operationalState (pcusn) panDec (bts) panInc (bts) panMax (bts) pcmCircuit (pcmCircuit) pcmNbr (pcu) pcmType (pcmCircuit) pcu (pcu) pcuLapdEqptRefList (pcu) pcusn (pcusn) routingArea (bts) speechOnHoppingTs (bts) t3172 (bts) upAckTime (transceiver)
B.14 GPRS (TF1134 - NMO I) gprsNetworkModeOperation (bts) B.15 GPRS (TF1121 - V12) gprsPreemption (bts) gprsPreemptionProtection (bts) gprsPriority (transceiver) minNbrGprsTs (bts) B.16 GPRS TBF establishment improvement: one phase access onePhaseAccess (bts) onePhaseDnMsCapability (bts)
B.21 Automatic Cell Tiering
543
B.17 GPRS / EDGE Suspend and Resume suspendResumeActivation (bsc) tResumeAck (bsc) tSuspendAck (bsc) B.18 PCUSN - more than 12 Agprs PCMs per BSC bscPcuPcmRefList (pcu) gprsPcuCrossConnectList B.19 Network Synchronization btsSMSynchroMode (btsSiteManager) dARPPh1Priority (transceiver) fnOffset (btsSiteManager) tnOffset (btsSiteManager) B.20 BTS Synchronization available synchronization sources current synchronization mode masterBtsSMId (btsSiteManager) B.21 Automatic Cell Tiering btsReserved3 (bts) hoMarginTiering (handOverControl) interferenceType (adjacentCellHandOver) intraCell (handOverControl) numberOfPwciSamples (handOverControl) selfTuningObs (handOverControl)
544
B.22 Handover for traffic reasons hoMarginTrafficOffset (adjacentCellHandOver) hoTraffic (bsc) hoTraffic (bts) B.23 Handover decision (adjacent cell priority and load) offsetLoad (adjacentCellHandOver) offsetPriority (adjacentCellHandOver) B.24 General protection against pingpong handover bts time between HO configuration (bts) directedRetryPrio (bts) hoPingpongCombination (adjacentCellHandOver) hoPingpongTimeRejection (adjacentCellHandOver) timeBetweenHOConfiguration (bsc) B.25 Intracell handover enhancements lRxQualDLH (handOverControl) lRxQualULH (handOverControl) B.26 AR 264
cellReselectOffset (bts) penaltyTime (bts) temporaryOffset (bts)
B.27 Mixed hybrid and cavity combiner BTSs btsWithCavity (bts) B.28 Call drop analysis callDropActivation (bts)
B.34 L1M evolutions for advanced features support
545
B.29 Extended CCCH channelType (channel) B.30 CPU/BIFP load sharing cpueNumber (btsSiteManager) B.31 Distribution on Radio measurements distributionActivation (bts) distributionDuration (bts) distributionTime (bts) distributionQualityThreshold (bts) fERThreshold1 (bts) fERThreshold2 (bts) fERThreshold3 (bts) fERThreshold4 (bts) nbOfFramesForFER (bts) B.32 Extended UL TBF extUtbfNoData (bts) fullDlKa (bts) nUsfExt (bts) nwExtUtbf (bts) onlyExtUtbf (bts) tNwExtUtbf (bts) tUsfExt (bts) B.33 Broadcast of PSI 13 maxRACH (bts) B.34 L1M evolutions for advanced features support measurementProcAlgorithm (bts)
546
B.35 Fast power control at TCH assignment new power control algorithm (bts) B.36 Data Backhaul Evolution numberOfJokerDS0 (transceiver) B.37 Disabling TBF Keep Alive tGMMKeepAlive (bts) B.38 PCM error correction enhancedTRAUFrameIndication (bsc) pcmErrorCorrection (bts) B.39 Unequipped circuit and circuit group block circuitGroupBlock (signallingPoint) unequippedCircuit (signallingPoint) B.40 WPS public access bandwidth protection wPSQueueStepRotation (bts) B.41 WPS queuing management allocPriorityTable (bts) allocPriorityTimers (bts) allocWaitThreshold (bts) B.42 BSC/TCU e3 GET DATA enhancement aterLapd (lsaRc) trmArchipelagoCalls (trm)
B.45 BSC 3000 support of BTS background downloading
547
B.43 Network Assisted Cell Change for release 4 MS nAccActivation (bts) packetSiStatus (bts) B.44 BSS Packet Flow Context packetFlowContext (powerControl) pfcActivation (bts) pfcArp1ConversationalCSCallProtection (powerControl) pfcArp1StreamingCSCallProtection (powerControl) pfcArp2ConversationalCSCallProtection (powerControl) pfcArp2StreamingCSCallProtection (powerControl) pfcArp3ConversationalCSCallProtection (powerControl) pfcArp3StreamingCSCallProtection (powerControl) pfcFlowControlActivation (bts) pfcMinNrtBandwidthPerTs (transceiver) pfcMinNumberOfJokersforTsGuaranteedBitRate (transceiver) pfcNrtRequestedDnMbrCounterThreshold (powerControl) pfcNrtRequestedUpMbrCounterThreshold (powerControl) pfcPreemptionRatioGold (powerControl) pfcPreemptionRatioSilver (powerControl) pfcRtDowngradeAllowed (powerControl) pfcRtRequestedDnGbrCounterThreshold (powerControl) pfcRtRequestedUpGbrCounterThreshold (powerControl) pfcT6 (powerControl) pfcT8 (powerControl) pfcTsGuaranteedBitRateDl (powerControl) pfcTsGuaranteedBitRateUl (powerControl) B.45 BSC 3000 support of BTS background downloading bckgDLLayer3WindowSize (bsc)
548
B.46 Optimized Agprs cell allocation privilegedCell (bsc) B.47 EDGE Dynamic Agprs dynamicAgprsAllowed (pcu) minNbOfJokersPerConnectedMain (transceiver) B.48 Switch Interference Matrix interferenceMatrixRunningOnBts interferenceMatrixRunningOnBsc B.49 Channel release policy on BTS after Abis failure channelReleaseOnAbisFailure B.50 PM1270 - TDMA based counters monitoredObjectClass B.51 Tx power offset for signalling channels facchPowerOffset sacchPowerOffsetSelection sacchPowerOffset hrPowerControlTargetModeDl frPowerControlTargetModeDl sigPowerOverboost B.52 Tx power overboost for signaling channels enableRepeatedFacchFr B.53 U-TDOA support on the BSS uplinkPwrCtrlDuringUTDOA (bsc)
B.55 GSM to UMTS handover
549
B.54 Enhanced Measurement Report (EMR) support servingBandReporting ServingBandReportingOffset B.55 GSM to UMTS handover cId compressedModeUTRAN diversityUTRAN earlyClassmarkSendingUTRAN fDDARFCN fDDMultiratReporting fDDReportingThreshold fDDReportingThreshold2 gsmToUMTSServiceHo hoMarginAMRUTRAN hoMarginDistUTRAN hoMarginRxLevUTRAN hoMarginRxQualUTRAN hoMarginTrafficOffsetUTRAN hoMarginUTRAN hoPingpongCombinationUTRAN hoPingpongTimeRejectionUTRAN hoRejectionTimeOverloadUTRAN locationAreaCodeUTRAN mobileCountryCodeUTRAN mobileNetworkCodeUTRAN offsetPriorityUTRAN qsearchC rNCId rxLevDLPbgtUTRAN rxLevMinCellUTRAN
550
scramblingCode t3121
B.56 Novel Adaptive Receiver adaptiveReceiver B.57 Signaling Link GET Dynamic Data enhancements slkATerResource slkAssociatedTmuPortPosition signallingLinkResourcesStates signallingLink field slkATerResource field slkAssociatedTmuPortPosition field slkAResource field signallingLinkResState field B.58 Smart Power Management smartPowerManagementConfig smartPowerSwitchOffTimer B.59 Software Preparation for BSC 3000 Optical Carriers Introduction synchronizingHsaRc B.60 AMR-HR on pre-empted PDTCH gprsPreemptionForHR B.61 Dynamic Abis interface readiness in V17 dynamicAbis
B.65 EDGE feature lock at OMC-R
551
B.62 BSS paging coordination bssPagingCoordination B.63 Permanent AAL-1 self-testing standbyStatus B.64 AMR feature lock at OMC-R Licenses used by this object Licenses needed to put object in service Number of XTP under this BSS This BSS is using license Total licenses for this OMC-R Total unused licenses B.65 EDGE feature lock at OMC-R
See B.64 AMR feature lock at OMC-R (page 551)
552
553

The PCUSN components are described in the following NTPs:
Nortel Networks Multiservice switch 7400, 15000, 20000 Component PcGtl (241-5701-060_PcGtl) Nortel Networks Multiservice switch 7400, 15000, 20000 Component Psusa (241-5701-060_Pcusa) Nortel Networks Multiservice switch 7400, 15000, 20000 Component Psusn (241-5701-060_Pcusn)
For more information on the PCUSN components, refer to:
Nortel Networks Multiservice switch 7400, 15000, 20000 Component Overview (241-5701-060)
554
Global System for Mobile Communications (GSM)
Nortel GSM BSS Parameter Reference

Copyright 1999, 2008 Nortel Networks All Rights Reserved.
Release: 17.0 Publication: 411-9001-124 Document status: Standard Document revision: 17.09 Document release date: 12 March 2008
To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback. www.nortel.com Sourced in Canada, France, and the United States of America. LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice. Nortel, the Nortel logo, the Globemark, S2000, and S8000 are trademarks of Nortel Networks. All other trademarks are the property of their respective owners.

Nortel GSM BSS Parameter Reference: Global System For Mobile Communications (GSM)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nortel GSM BSS Parameter Reference: Global System For Mobile Communications (GSM)

Uploaded by

Copyright:

Available Formats

Global System for Mobile Communications (GSM)

Nortel GSM BSS Parameter Reference

4 microCellCaptureTimer and microCellStability 41 upgradeStatus 42 Others 42

Introduction Chapter 1 Introduction

Chapter 2 Parameters listed in alphabetical order

Appendix A Objects and parameters evolution

Appendix B Parameters per feature

Appendix C PCUSN components

New in this release

Copyright 1999, 2008 Nortel Networks

New in this release

GSM to UMTS handover (2473)

hoMarginTrafficOffsetUTRAN hoPingpongCombinationUTRAN hoPingpongTimeRejectionUTRAN offsetPriorityUTRAN rxLevMinCellUTRAN

Enhanced measurement report (EMS) support (21531)

servingBandReporting Class 3 (page 441) ServingBandReportingOffset servingBandReportingOffset Class 3 (page 441)

EDGE - Dynamic Abis per site (25203)

New in this release

On-line TMU load reconfiguration from OMC-BSC3000 (26530)

Added additional parameter details about estimatedSiteLoad and cpueOccurence

Downlink voice quality monitoring (27017)

PCUSN-54 : new PCUSN configuration (T1) (27222)

Support of A5/3 ciphering key (27392)

Added two values to parameter encryptionAlgorSupported

Novel Adaptive Receiver (27888)

Copyright 1999, 2008 Nortel Networks

PCUSN-54 : new PCUSN configuration (E1) (28727)

Signaling Link GET Dynamic Data Enhancement (29722)

AMR-HR on pre-empted PDTCH (30169)

Advanced Call Drop Analysis (32277)

Joint Diversity (32280)

New in this release

CEM2 combined CEM and SRT boards (32291)

The parameter bscArchitecture is updated to include BSC30000Optical

BSC 3000 optical carriers (32302)

BTS 6000 Differenciation in OMC-R (32361)

S4000, S2000, and S2000E removal (32730)

Shared disks scan for bad blocks prevention (33285)

Added checks information to parameter mmsUsage.

TCU 3000 optical carriers (33303)

BSS paging coordination (34160)

New in this release

BTS 18000/6000 Smart Power Management (34208)

AMR feature lock at OMC-R (34433)

EDGE feature lock at OMC-R (34434)

RM family renaming management at OMC (34439)

BSC and TCU 2G End Of Life (34649)

microCellCaptureTimer and microCellStability

New in this release

bscIPFirstAdr bscIPSecondAdr coderPoolConfiguration cpueNumber

Figure 2 omc subtree objects

Figure 3 md subtree objects

1.1 Network configuration objects and their parameters

Figure 4 Network subtree objects

Figure 5 bsc 3000 subtree objects

Figure 6 btsSiteManager subtree objects

1.1 Network configuration objects and their parameters

1.2 Different types of configuration parameters

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

design parameters, which are relative to contract characteristics

optimization parameters, which are relative to network tuning (for

operating parameters, which are relative to network operation (for

system parameters, which can seriously affect system operation,

product parameters, which are incompatible with the current system