59032723 GSM Parameter

Version 2.0401-380-007

October 2000

Lucent Technologies - ProprietaryThis document contains proprietary information

of Lucent Technologies and is not to be disclosed or usedexcept in accordance with applicable agreements

Copyright 2000 Lucent TechnologiesUnpublished and Not for Publication

All Rights Reserved

Parameter CataloguePC:GSM

Network Release 8.0

Copyright 2000 by Lucent Technologies. All Rights Reserved.This material is protected by the copyright laws of the United States and other countries. It may not bereproduced, distributed, or altered in any fashion by any entity (either internal or external to LucentTechnologies), except in accordance with applicable agreements, contracts, or licensing, without theexpress written consent of the Customer Training and Information Products organization and thebusiness management owner of the material.

NoticeEvery effort was made to ensure that the information in this information product (IP) was complete andaccurate at the time of printing. However, information is subject to change.

GSM Parameter Catalogue – NR 8.0

Version 2.0 - October 2000 Lucent Technologies – ProprietarySee Notice on first page

iii

Contents

1 A_DIST_HO 2

2 A_LEV_HO 3

3 A_LEV_NC 4

4 A_LEV_PC 5

5 A_PBGT_HO 6

6 A_QUAL_HO 7

7 A_QUAL_PC 8

8 AC_CN 9

9 ACC CARD VERSION 10

10 ACC CLOCK SOURCE 11

11 ACC DATA ENCODING 12

12 ACC FRAME MODE 13

13 ACC PORT MODE 14

14 ALARM STATE (N) 15

15 ARFCN_NC(N) 16

16 ASSOC. FH-SYSTEM 17

17 ATT 18

18 BACKUP CAPABILITY 19

19 BARRING SEQUENCE 20

20 BCC (IN BSIC) 21

21 BCC_NC(N) 22

22 BCCH_ARFCN_NC(N) 23

23 BCCH_FREQ 24

24 BS_AG_BLKS_RES 25

25 BS_PA_MFRMS 26

26 BS_TXPWR_RED 27

27 BTS-ABIS-POSITION 28

28 C_MICRO_DELAYED_HO 29

29 C_MICRO_HO 30


iv Lucent Technologies –ProprietarySee Notice on first page

Version 2.0 - October 2000

30 C_UMBRELLA_MICRO_HO 31

31 CA_ARFCN 32

32 CCCH LOAD IND. THRESHOLD (PAGING_LOAD_THR) 33

33 CCCH_COMB_WITH_SDCCH 34

34 CCCH_LOAD_IND_PERIOD 35

35 CELL_BAR_ACCESS 36

36 CELL_BAR_QUALIFY 37

37 CELL_RES_OFFSET 38

38 CELL_RESELECT_HYST. 39

39 CELL_RESELECT_PARAM_IND 40

40 CELL_TYPE 41

41 CELL_TYPE_NC(N) 42

42 CH_TYPE 43

43 CHANNEL-USAGE 44

44 CI (IN CGI) 45

45 CI_NC(N) 46

46 CIRCUIT ID CODE CIC 47

47 CLOCK_SOURCE 48

48 CLOCK_SOURCE (REDUNDANT) 49

49 CONNECTED ACC E1 50

50 CRC 4 FRAMING 51

51 DIVERSITY INDICATION 52

52 DOWNLINK DTX DATA 53

53 DOWNLINK DTX SPEECH 54

54 DTX 55

55 E1 PORT TYPE 56

56 E1 ALLOCATION(BCON) 57

57 E1 ALLOCATION(MCON) 58

58 EN_ACC_BARRING 59

59 EN_BS_PC 60

60 EN_BSS_HO 61


Version 2.0 - October 2000 Lucent Technologies –ProprietarySee Notice on first page

v

61 EN_CCCH_LOAD_IND 62

62 EN_DIST_HO 63

63 EN_INCOM_HO 64

64 EN_INTER_HO 65

65 EN_INTRA_HO 66

66 EN_LOAD_REGARD 67

67 EN_MS_PC 68

68 EN_PBGT_HO 69

69 EN_RF_RES_IND 70

70 EN_RXLEV_HO 71

71 EN_RXQUAL_HO 72

72 EN_SDCCH_HO 73

73 EN_SDCCH_TCH_HO 74

74 EXT. ERROR ID (N) 75

75 EXTC-TYPE 76

76 FHE SLICE ADDRESS 77

77 FIS_SYN_DELAY 78

78 FREEFACTOR_X (X=1..5) 79

79 FREELEVEL_X (X=1..4) 80

80 HO_MARGIN(0,N) 81

81 HOPPING MODE 82

82 HSN 83

83 INIT_FREQ 84

84 INPUT HYSTERESE (N) 85

85 INPUT POINT ADR (N) 86

86 INT_BOUND_X 87

87 INTAVE 88

88 IP ADDRESS 89

89 L_RXLEV_DL_H 90

90 L_RXLEV_DL_P 91

91 L_RXLEV_UL_H 92


vi Lucent Technologies –ProprietarySee Notice on first page


92 L_RXLEV_UL_P 93

93 L_RXQUAL_DL_H 94

94 L_RXQUAL_DL_P 95

95 L_RXQUAL_UL_H 96

96 L_RXQUAL_UL_P 97

97 LAC (IN LAI) 98

98 LAC_NC(N) 99

99 LIC-ALARM MASK (N) 100

100 LIC-CLOCK-INPUT (N) 101

101 LIC-INPUT-LINE A (N) 102

102 LIC-INPUT-LINE B (N) 103

103 LIC-NUMBER (N) 104

104 LIC-POSITION (N) 105

105 LIC-RACK (N) 106

106 LINK SERVICEPR. SLC 107

107 LINK SERVICEPR. STC 108

108 LINKFACTOR(0,N) 109

109 M1 110

110 M2 111

111 MA_ARFCN 112

112 MAX_RETRANS 113

113 MCC (IN LAI) 114

114 MCC_NC(N) 115

115 MEMORY AVAILABILITY 116

116 MNC (IN LAI) 117

117 MNC_NC(N) 118

118 MS_DIST_MAX 119

119 MS_TXPWR_MAX 120

120 MS_TXPWR_MAX(N) 121

121 MS_TXPWR_MAX_CCH 122

122 MULTIBAND_REPORTING 123



vii

123 N (N_TARGET_CELL) 124

124 N1 125

125 N2 126

126 NCC (IN BSIC) 127

127 NCC_NC(N) 128

128 NI_BSC 129

129 NI_MSC 130

130 NO. OF CCCH 131

131 NS_TRX 132

132 P_CON_ACK 133

133 P_CON_INTERVAL 134

134 PENALTY_TIME 135

135 PG-TYPE 136

136 PLMN_PERMITTED 137

137 PMC ALLOCATION (EXTC) 138

138 PMC ALLOCATION (PG) 139

139 POW_INCR_STEP_SIZE 140

140 POW_RED_STEP_SIZE 141

141 PTA_HO(N,0) 142

142 Q_THRESHOLD_VAL 143

143 RACH_BUSY_THRES 144

144 RACH_MEAS_PERIOD 145

145 RADIO-/TERR. LINK ASC. 146

146 RADIO_LINK_TIMEOUT (T100) 147

147 RBS-TYPE 148

148 RE 149

149 RT RACK ID. 150

150 RT SHELF ID. 151

151 RXLEV_ACCESS_MIN 152

152 RXLEV_DL_IH 153

153 RXLEV_MIN(N) 154


viii Lucent Technologies –ProprietarySee Notice on first page


154 RXLEV_UL_IH 155

155 SDFU/TCU VERSION 156

156 SDU BAD SECTORS 157

157 SDU HIGHER THRESHOLD 158

158 SDU LOWER THRESHOLD 159

159 SDU NO. OF SECTORS 160

160 SERVERALLOCATION 161

161 SERVICEPROVIDER L2 (BTC) 162

162 SERVICEPROVIDER L2 (RT) 163

163 SERVICEPROVIDER PG (TCG) 164

164 SERVICEPROVIDER PPC (BTC) 165

165 SERVICEPROVIDER PPC (RT) 166

166 SIGN.-SLOT BTC 167

167 SIGN.-SLOT RT 168

168 SIGNALLING LINK CODE 169

169 SIGSLOTSRESERVED 170

170 SPC_BSC 171

171 SPC_MSC 172

172 SYNC_NC(N,0) 173

173 T_MK 174

174 T_QHO (MAP-TIMER) 175

175 T_SDCCH_HO_ALLOWED 176

176 T1 (MAP-TIMER) 177

177 T10 (MAP-TIMER) 178

178 T11 (MAP-TIMER) 179

179 T13 (MAP-TIMER) 180

180 T17 (MAP-TIMER) 181

181 T18 (MAP-TIMER) 182

182 T19 (MAP-TIMER) 183

183 T3101 (UM-TIMER) 184

184 T3107 (UM-TIMER) 185



ix

185 T3109 (UM-TIMER) 186

186 T3111 (UM-TIMER) 187

187 T3212 188



190 T7_IHO 191


192 TEMPORARY_OFFSET 193

193 THRES_PC_RLF 194

194 TIC[TCE_CODE] 195

195 TIC[TCG_CODE] 196

196 TIC[TCGQ_CODE] 197

197 TOTAL_NUM_Q_PLACE_AVAIL 198

198 TRAFFIC SLOTS RT 199

199 TRANSCODING CAPABILITY 200

200 TRC INPUT SLOT 201

201 TRC OUTPUT SLOT 202

202 TRC SERVICE PROVIDER 203

203 TRR3 (MAP-TIMER) 204

204 TRR5 (MAP-TIMER) 205

205 TSC 206

206 TX_INTEGER 207

207 U_RXLEV_DL_P 208

208 U_RXLEV_UL_P 209

209 U_RXQUAL_DL_P 210

210 U_RXQUAL_UL_P 211

211 UMBRELLA_MICRO_HYST 212

212 W_QUAL_HO 213

213 W_QUAL_PC 214

214 ANNEX A 215

A.1 Mapping: Object/AUI -> GUI and GSM Name 215


x Lucent Technologies –ProprietarySee Notice on first page


A.2 Mapping: Object/GUI -> AUI and GSM Name 219

A.3 Mapping: GSM Name -> Object, AUI and GUI 223



1

Purpose

The purpose of this document is as follows:

To provide a cross reference between the Bosch OMC, Lucent OMC 2000 GUI, Lucent OMC 2000 AUIand GSM ‘Standard’ terminology.

The user is given a more detailed description of system parameters than those contained in the OMC2000 User Documentation. This is to assist in routine work that involves management of the BSSparameters (which are controlled from the OMC 2000)

The following table describes the fields that are defined:

Section Title GSM Name of parameterDefault A meaningful default value that is used or could be usedRange The value range of the parameterRange Semantics The semantics of the parameter value, e.g. mapping of integers to dB values.Modification State Parameters are contained in objects. Objects can be administratively locked

or unlocked. For modifiable parameters this field determines whether modificationscan be done in locked (LO) and/or unlocked (UL) state

Short Description A short description of the parameterOMC (Object, GUI,AUI)

Description of the parameter as displayed at the Lucent OMC. This includesthe object class, the name at the Graphical User Interface (GUI) and the nameat the ASCII User Interface (AUI)

Bosch OMC (Object,AUI, Comments)

Description of the parameter as displayed at the Bosch OMC LM4.0. This includesthe object class, the name at the ASCII User Interface (BMML) and a commentif there are any discrepancies at the Bosch OMC

Long Description Contains a long description of the parameter and references to other parametersthat are closely related.

Dependency Dependencies to other parametersGSM 12.20 (Class,Attribute)

Class and Attribute name of the attribute in the GSM 12.20 recommendationthat more or less corresponds to this parameter


2 Lucent Technologies –ProprietarySee Notice on first page


1 A_DIST_HORecommended DefaultValue:

1920 msec = 4

Range: 1-31 (480 msec - 14880 msec)Range Semantics: multiples of SACCH period (480 msec for TCH resp. 470.77 msec for

SDCCH channels)Modification State: LO/ULShort Description: Averaging window size for distance measurements between BTS and MS

concerning distance handoverOMC Object: HOCTRLOMC AUI: DISTAVGPEROMC GUI: Distance: Averaging PeriodBosch OMC Object: HOBosch OMC AUI: HOCDIST-bBosch OMC Comments: -Long Description: The number of the most recent distance measurement values which are

used in the distance averaging procedure. The distance measurement iscarried out by the BTS. An averaged measurement value is normally givenevery SACCH block period by the averaging procedure which is located inthe BSC. The averaged measurement value is used in the followingdistance handover comparison procedures.If the network planning is relying on Distance HO, the averaging windowshoud be increasedSee also EN_DIST_HO

Dependency: -GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: hoAveragingDistParam



3

2 A_LEV_HORecommended DefaultValue:

2880 msec = 6


SDCCH channels)Modification State: LO/ULShort Description: Averaging window size for receive power level measurements concerning

handoverOMC Object: HOCTRLOMC AUI: ALEVHOOMC GUI: Signal Strength: Averaging PeriodBosch OMC Object: HOBosch OMC AUI: HOCSS-cBosch OMC Comments: -Long Description: The number of the most recent power level measurement values which

are used in the power level averaging procedure concerning handover isgiven by the O&M parameter A_LEV_HO. A_LEV_HO is used for theuplink and downlink by the BSC. An averaged measurement value isnormally given every SACCH block period by the averaging procedure.The averaged measurement value is compared with the correspondingthresholds for handover decisions.After channel allocation intracell handovers are disabled for a time periodof A_LEV_HO.See also A_LEV_NC, A_PBGT_HO, A_LEV_PC, EN_RXLEV_HO

Dependency: Typically: A_LEV_NC <= A_LEV_HO <= A_PBGT_HOA_LEV_PC <= A_LEV_HO

GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: hoAveragingLevParam




3 A_LEV_NCRecommended DefaultValue:

2880 msec = 6


SDCCH channels)Modification State: LO/ULShort Description: Averaging window size for receive power level measurements of NCs

concerning handover target cell identification process.OMC Object: HOCTRLOMC AUI: PWRACAVGOMC GUI: Adjacent Cell Averaging PeriodBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: A_LEV_NC gives the number of the most recent downlink power level

measurement values concerning the neighbouring cells, which are used inthe handover target cell identification process. The averagedmeasurement values are normally given every SACCH block period by theaveraging procedure. The averaged measurement values are used in caseof inter-cell handover for setting up a list of preferred target cells.See also A_LEV_HO, A_PBGT_HO, EN_PBGT_HO, A_LEV_PC

Dependency: Typically: A_LEV_NC <= A_LEV_HO <= A_PBGT_HOGSM 12.20 Class: -GSM 12.20 Attribute: -



5

4 A_LEV_PCRecommended DefaultValue:

960 msec = 2


SDCCH channels)Modification State: LO/ULShort Description: Averaging window size for receive power level measurements concerning

Power ControlOMC Object: POWEROMC AUI: ALEVPCOMC GUI: Signal Strength: AveragingBosch OMC Object: PCBosch OMC AUI: SSAVPERBosch OMC Comments: -Long Description: The number of the most recent power level measurement values which

are used in the power level averaging procedure concerning power controlis given by the O&M parameter A_LEV_PC. A_LEV_PC is used for theuplink and downlink by the BSC. An averaged measurement value isnormally given every SACCH block period by the averaging procedure.See also EN_MS_PC, EN_BS_PC

Dependency: Typically: A_LEV_PC <= A_LEV_HOGSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: pcAveragingLev




5 A_PBGT_HORecommended DefaultValue:

3840 msec = 8


SDCCH channels)Modification State: LO/ULShort Description: Averaging window size for power budget calculation for handoverOMC Object: HOCTRLOMC AUI: PWRBGAVGOMC GUI: Power Budget Averaging PeriodBosch OMC Object: HOBosch OMC AUI: AVPERBosch OMC Comments: -Long Description: The number of the most recent downlink power level measurement values

concerning the serving cell and the neighbouring cells, which are used inthe power budget averaging procedure for handover. The averagedmeasurement values are normally given every SACCH block period by theaveraging procedure.The bigger the window size (number of measurements) is, the moreprecise the values of the averaged parameters are. When the values arenot precise enough, the probability of an incorrect handover decision willincrease. However, a too big window size can cause a delayed handoverdecision, and so dragging the call. It could cause bad quality and a higherinterference probability due to the an unnecessary increased transmitpower of the currently serving base station.See also EN_PBGT_HO, HO_MARGIN(0,n), A_LEV_HO

Dependency: Typically: A_LEV_HO <= A_PBGT_HO, A_LEV_NC <= A_PBGT_HOGSM 12.20 Class: -GSM 12.20 Attribute: -



7

6 A_QUAL_HORecommended DefaultValue:

2880 msec = 6


SDCCH channels)Modification State: LO/ULShort Description: Averaging window size for quality measurements concerning handoverOMC Object: HOCTRLOMC AUI: AQUALHOOMC GUI: Signal Quality: Averaging PeriodBosch OMC Object: HOBosch OMC AUI: HOCSQ-cBosch OMC Comments: -Long Description: The number of the most recent quality measurement values, which are

used in the quality averaging procedure for handover. A_QUAL_HO isused for the uplink and downlink by the BSC. The averaged measurementvalue is normally given every SACCH block period by the averagingprocedure. The averaged measurement value is compared with thecorresponding thresholds for handover decisions.The recommended default value applies for disabled DTX. With DTXenabled the weighting factor for Full measurements is considered andshould be set to 2. To get a effective window size of 4 the recommendeddefault value for this attribute with DTX enabled is 8.See also A_QUAL_PC, EN_RXQUAL_HO, W_QUAL_HO, DTX, DownlinkDTX Speech, Downlink DTX Data

Dependency: Typically: A_QUAL_PC <= A_QUAL_HOGSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: hoAveragingQualParam




7 A_QUAL_PCRecommended DefaultValue:

960 msec = 2


SDCCH channels)Modification State: LO/ULShort Description: Averaging window size for quality measurements concerning Power

ControlOMC Object: POWEROMC AUI: AQUALPCOMC GUI: Signal Quality: AveragingBosch OMC Object: PCBosch OMC AUI: SQAVPERBosch OMC Comments: -Long Description: The number of the most recent quality measurement values, which are

used in the quality averaging procedure for power control, is given by theO&M parameter A_QUAL_PC. A_QUAL_PC is used for the uplink anddownlink by the BSC. The averaged measurement value is normally givenevery SACCH block period by the averaging procedure. The averagedmeasurement value is used in the handover comparison procedure.See also EN_MS_PC, EN_BS_PC

Dependency: Typically: A_QUAL_PC <= A_QUAL_HOGSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: pcAveragingQual



9

8 AC_CNRecommended DefaultValue:

no class barred

Range: 0-15Range Semantics: 0-9: normal subscriber, 10: emergency calls, 11-15: special or restrictedModification State: LO/ULShort Description: Access Control Class N is used to bar MSs of specific access classes.OMC Object: BTSOMC AUI: ACCESSCLASSOMC GUI: Not Allowed Access ClassesBosch OMC Object: CELLBosch OMC AUI: ACCBosch OMC Comments: -Long Description: The Parameter AC_CN is used to prevent MSs belonging to special

access classes from making access attempts (including emergency callattempts) or responding to paging messages in the specified area. Theuse of this facility allows the network operator to prevent overload of thecell under critical conditions. It is not intended that access control be usedunder normal operating conditions.The integers specified define the classes inaccessible to the MS. Theaccess classes the MS is allowed to use are stored on its SubscriberIdentity Module (SIM). If the access for a certain class is barred, this is noreason for an MS for cell reselection, i.e. the MS can not access thenetwork.If there is an overload on the RACH, it should be tried prior of barring anaccess class to reduce the number of access attempts by decreasingparameter 'MAX_RETRANS'.See also for automatic barring in overload situations: Barring Sequence,EN_ACC_BARRING, M1, M2, N1, N2

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: notAllowedAccessClasses




9 ACC Card VersionRecommended DefaultValue:

-

Range: TextRange Semantics: -Modification State: -Short Description: Version information about the BCF Advanced Communications Controller

(ACC) CardBSC of type BCF only.

OMC Object: ACC / accCardOMC AUI: ROMMODNAME, ROMREVCODE, ROMUPDTIME, TYPEOMC GUI: Interface Card Type, ROM Update Time, ROM Module Name, ROM

Revision CodeBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: The ACC Card Version attribute contains following information:

Card Type (20 bytes)ROM update time (24 bytes) e.g. Thu Jan 18 11:00:00 1996ROM module name (12 bytes)ROM revision code (8 bytes)

Dependency: -GSM 12.20 Class: GSM1220_gsmEquipmentGSM 12.20 Attribute: version



11

10 ACC Clock SourceRecommended DefaultValue:

-

Range: 0-1Range Semantics: 0 = internal-baud-generator, 1 = external-clockModification State: -Short Description: The ACC Card E1 Port Clock Source defines the source of the clock being

used in generating and sampling the raw bit stream.BSC of type BCF only.

OMC Object: ACCE1PORTOMC AUI: CLKSOURCEOMC GUI: Clock SourceBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: The source of the clock can be derived either from externally located

equipment or from the ACC card itself.Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -




11 ACC Data EncodingRecommended DefaultValue:

-

Range: 0-2Range Semantics: 0 = high-density-bipolar-3-zeros, 1 = bipolar-8-zero-substitution, 2 =

alternating-mark-inversionModification State: -Short Description: The ACC Card E1 Port Data Encoding defines the way in which timing

(clock) information is being embedded and extracted from within thetransmitted and received raw bit streams.BSC of type BCF only.

OMC Object: ACCE1PORTOMC AUI: DATAENCODEOMC GUI: Data EncodingBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



13

12 ACC Frame ModeRecommended DefaultValue:

-

Range: 0,1,3-6Range Semantics: 0 = frame-4-multiframe, 1 = frame-12-multiframe, 3 = extended-

superframes, 4 = remote-switch-mode, 5 = double frame, 6 = crc-multiframe

Modification State: -Short Description: The ACC Card E1 Port Frame Mode defines the way in which the raw bit

stream is split up into frames.BSC of type BCF only.

OMC Object: ACCE1PORTOMC AUI: FRAMEMODEOMC GUI: Frame ModeBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: Techniques such as bit-stuffing and start and end bit flags are used to

distinguish frames which also might include CRC checksum algorithms.Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -




13 ACC Port ModeRecommended DefaultValue:

-

Range: 0-3Range Semantics: 0 = e1TwistedPair, 1 = e1CoaxBNC, 2 = t1TwistedPair, 3 = loopbackModification State: -Short Description: The ACC Card E1 Port Mode defines the various types of transmission

media that are chosen to connect external equipment to the ACC cardsports.BSC of type BCF only.

OMC Object: ACCE1PORTOMC AUI: PORTMODEOMC GUI: Port ModeBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



15

14 Alarm State (n)Recommended DefaultValue:

0 (low)

Range: 0-1Range Semantics: 0 = low, 1 = highModification State: LO/ULShort Description: Indicates an alarm state at this input point.

BTS of type RBS900 only.OMC Object: BTC-ARUOMC AUI: ALRMSTATExOMC GUI: Alarm StateBosch OMC Object: BTCBosch OMC AUI: DIP-cBosch OMC Comments: Range:LOW = 0, HIGH = 1Long Description: The digital input point parameters contain information required by the BTC

to assign individual configuration data to each input line on the ControlAlarm and Control Port (CAP/CCP) for the RBS900 or the external alarmbox (EAB) for the BTS2000. Depending on the BTS type up to 24 externaldevices can be connected to the BTC, but only 16 are visible on the OMC.This parameter defines the physical input potential (high or low) to beconsidered as 'alarm active'.See also Input Point Adr (n), Input Hysterese (n), Ext. Error Id (n)

Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -




15 ARFCN_NC(n)Recommended DefaultValue:

-

Range: 1-1024Range Semantics: GSM900: 1-124; GSM1800: 512-885Modification State: LO/ULShort Description: Absolute Radio Frequency Channel Number of the BCCH frequency of

neighbour cell n. Used by MS in connected mode for handoverOMC Object: ADJCELLOMC AUI: BCCHOMC GUI: BCCH FrequencyBosch OMC Object: NCELLBosch OMC AUI: CDESC-gBosch OMC Comments: -Long Description: Absolute Radio Frequency Channel Number of the BCCH of neighbour cell

n. This frequency is used by a connected MS for handover purposes. Thisdata is sent to the MS, so that measurements from all adjacent cells canbe sent to the controlling BSC.Frequency allocation is matter of cellular network planning. All frequencyrelated attributes (CA_ARFCN, INIT_FREQ, BCCH_FREQ, MA_ARFCN,ARFCN_NC(n), BCCH_ARFCN_NC(n)) shall adhere to this planning.ARFCN_NC(n) is normally equal to or a subset of BCCH_ARFCN_NC(n).Formerly: BA_SACCH.In the GSM standards this parameter is called BCCH_FREQ_NCELL.

Dependency: Parameter BCCH_FREQ of the neighbour cell and all ARFCN_NC(n) andBCCH_ARFCN_NC(n) referencing this cell is required to have the samevalue.

GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: bCCHFrequency



17

16 Assoc. FH-SystemRecommended DefaultValue:

255 (no hopping)

Range: 0-7,255Range Semantics: 0-7: RDN value of associated FH object, 255: no hopping channelModification State: LO/ULShort Description: Specifies the associated Frequency Hopping System or no frequency

hopping.OMC Object: CHNOMC AUI: FREQHOPRELOMC GUI: Frequency UsageBosch OMC Object: CHNBosch OMC AUI: FHRELBosch OMC Comments: Range:FH0 = 0, .., FH7 = 7, NOFH = 255Long Description: Assigns the channel to an existing frequency hopping system.

See also CH_TYPEDependency: For frequency hopping the referenced FH object shall exist and the

channel shall not be of type mainBCCH, mainBCCHCombined(-CB) orCCCH.For modification of this attribute the 'old' and the 'new' associated FHobject are required to be administratively locked.The frequency (INIT_FREQ) of the RT serving the channel has to becontained in the frequency list (MA_ARFCN) of the associated FH system.The frequencies of a hopping system FH associated to a hopping channelare not used within other hopping systems FH which have beenassociated to other CHN using the same physical timeslot.All CHN using the same timeslot are not to be set to non hopping, as soonas the initial frequency (INIT_FREQ) of a serving RT is assigned to anassociated FH.

GSM 12.20 Class: channelGSM 12.20 Attribute: frequencyUsage




17 ATTRecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: This parameter indicates whether the MS is allowed to apply the IMSI

attach and detach procedures.OMC Object: BTSOMC AUI: WIMSIATTDETOMC GUI: Allow IMSI Attach DetachBosch OMC Object: BTSBosch OMC AUI: CONFCCH-cBosch OMC Comments: -Long Description: Specifies whether the VLR in the network supports IMSI attaching and

detaching. If enabled, each MS that is switched off transmits the 'IMSIdetach' message to the network before powering down. When it isswitched on again, it will send the 'IMSI attach' message. If the VLR entryof the MS specifies that the MS is currently detached, no paging to this MSwill take place. Instead, any call termination attempt to the detached MScan be directly routed to congestion tone, or an announcement by thenetwork. If there is an overload on the paging channel, ATT may be ameans to reduce the overload.

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: allowIMSIAttachDetach



19

18 Backup CapabilityRecommended DefaultValue:

0 (no backup)

Range: 0-2Range Semantics: 0 = no backup, 1 = bcch backup, 2 = sdcch backupModification State: LO/ULShort Description: Defines RT as backup for BCCH or SDCCH RTOMC Object: RTOMC AUI: BACKUPOMC GUI: Backup CapabilityBosch OMC Object: RTBosch OMC AUI: RTMODEBosch OMC Comments: Range:NOBACKUP = 0, BCCHBACKUP = 1, SDCCHBACKUP = 2Long Description: For automatic reconfiguration the management function must know which

RT can be used as backup for BCCH/SDCCH. If BCCH and SDCCH areconfigured on the same RT, only the backup for BCCH needs to bedefined.On BCCH/SDCCH reconfiguration between backup and backed-up RT thefollowing parameters are exchanged: Diversity Indication, RT Rack Id., RTShelf Id, FHE Slice Address.

Dependency: Only RTs carrying traffic channels only can be configured as backup RT.GSM 12.20 Class: -GSM 12.20 Attribute: -




19 Barring SequenceRecommended DefaultValue:

11,12,..,15,10

Range: 10-15Range Semantics: 10: emergency calls, 15: PLMN Staff, 14: Emergency Services, 13: Public

Utilities (e.g. water/gas suppliers), 12: Security Services, 11: For PLMNUse

Modification State: LO/ULShort Description: This parameter defines the sequence of the access classes are going to

be barred in case of overload in the BSS if access classes 0-9 are alreadybarred. Up to all six of the access classes 10-15 may be mentioned.

OMC Object: BTSOMC AUI: BARSEQ10_15OMC GUI: Access Class Overload Control: Classes 10 to 15: Bar SequenceBosch OMC Object: CELLBosch OMC AUI: OVERLOAD-fBosch OMC Comments: -Long Description: Barring is used to prevent MSs belonging to special access classes from

making access attempts (including emergency call attempts) orresponding to paging messages in the specified area. The use of thisfacility allows to recover from overload.The MS stores the access control class on its Subscriber Identity Module(SIM). If the access for a certain class is barred, MSs with that class mayonly try to get a connection in the neighbour cells.Automatic barring is done by the BSS in case of overload. Depending onthe severity of overload the BSS starts with barring access classes 0-9with random starting class and step size M1 (unbarring with step size M2).If classes 0-9 are barred and there is still an overload situation, the BSScontinues barring with access classes 10-15. The barring sequence foraccess classes 10-15 is given in parameter 'Barring Sequence' and thestep size in N1 (unbar: N2). The timer T17 (MAP-Timer) and T18 (MAP-Timer) are used for barring resp. unbarring. Automatic barring can beenabled/disabled with flag EN_ACC_BARRING.See also: EN_ACC_BARRING, M1, M2, N1, N2, T17 (MAP-Timer), T18(MAP-Timer)The operator can bar manually special MS access classes with parameterAC_CN.




21

20 BCC (in BSIC)Recommended DefaultValue:

-

Range: 0-7Range Semantics: -Modification State: LOShort Description: The Base Station Colour Code (BCC) is part of the BSIC. The BSIC is a

local colour code that allows a MS to distinguish between differentneighbouring base stations. The BCC is used to distinguish betweendifferent neighbouring cells using the same frequency.

OMC Object: BTSOMC AUI: BSIDBCCOMC GUI: BS Identity Code: BCCBosch OMC Object: CELLBosch OMC AUI: BSIC-bBosch OMC Comments: -Long Description: The Base Station Identity Code (BSIC) consists of the Network Colour

Code (NCC) and the Base Station Colour Code (BCC).The BSIC is a local colour code that allows a MS to distinguish betweendifferent neighbouring base stations. The BSIC is broadcast on thesynchronisation channel SCH. The MS uses the BSIC in the following way:1. In idle mode the MS shall attempt to check the BSIC for each of the 6strongest non-serving cell BCCH carriers at least every 30 seconds, toconfirm that it is monitoring the same cell. If a change of BSIC is detectedthen the carrier shall be treated as a new carrier and the BCCH dataredetermined.2. In connected mode the MS shall demodulate the SCH on the BCCHcarrier of each surrounding cell and decode the BSIC as often as possible,and as a minimum at least once every 10 seconds.For broadcast (BCCH) and common control channels (PCH and AGCH)the BCC is used as TSC, i.e. the TSC set by operator is ignored.The BSIC shall only be changed on request of cellular network planning.See also: NCC (in BSIC), BCC_NC(n), NCC_NC(n), PLMN_PERMITTED,TSC

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: bsIdentityCode.BTSColourCode




21 BCC_NC(n)Recommended DefaultValue:

-

Range: 0-7Range Semantics: -Modification State: LO/ULShort Description: The Base Station Colour Code of Neighbour Cell n (BCC_NC) is part of

the BSIC_NC. The BSIC_NC is a local colour code that allows a MS todistinguish between different neighbouring base stations. The BCC is usedto distinguish between different neighbouring cells using the samefrequency.

OMC Object: ADJCELLOMC AUI: BSIDBCCOMC GUI: BS Identity Code: BCCBosch OMC Object: NCELLBosch OMC AUI: CDESC-cBosch OMC Comments: -Long Description: The Base Station Identity Code of a neighbour cell (BSIC_NC) consists of

the Network Colour Code (NCC_NC) and the Base Station Colour Code(BCC_NC) of that neighbour cell.The BSIC is a local colour code that allows a MS to distinguish betweendifferent neighbouring base stations. The BSIC is broadcast on thesynchronisation channel SCH. The MS uses the BSIC in the following way:1. In idle mode the MS shall attempt to check the BSIC for each of the 6strongest non-serving cell BCCH carriers at least every 30 seconds, toconfirm that it is monitoring the same cell. If a change of BSIC is detectedthen the carrier shall be treated as a new carrier and the BCCH dataredetermined.2. In connected mode the MS shall demodulate the SCH on the BCCHcarrier of each surrounding cell and decode the BSIC as often as possible,and as a minimum at least once every 10 seconds.The BSIC shall only be changed on request of cellular network planning.See also: BCC (in BSIC), NCC (in BSIC), NCC_NC(n),PLMN_PERMITTED, TSC

Dependency: BCC_NC(n) is required to have the same value as parameter BCC of thatneighbour cell.

GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: bsIdentityCode.BTSColourCode



23

22 BCCH_ARFCN_NC(n)Recommended DefaultValue:

-

Range: 1-1024Range Semantics: GSM900: 1-124; GSM1800: 512-885Modification State: LO/ULShort Description: BCCH frequency of neighbour cell used by MS in idle mode for reselectionOMC Object: ADJRESOMC AUI: BCCHOMC GUI: BCCH FrequencyBosch OMC Object: NCELLBosch OMC AUI: ADCCHBosch OMC Comments: -Long Description: Absolute Radio Frequency Channel Number of the BCCH of neighbour cell

n. This frequency is used by an idle MS for (re-)selection.The BCCH frequency is fixed for a cell. The operator has to care for thatthe correct value is used every time it is referenced as neighbour cell.Frequency allocation is matter of cellular network planning. All frequencyrelated attributes (CA_ARFCN, INIT_FREQ, BCCH_FREQ, MA_ARFCN,ARFCN_NC(n), BCCH_ARFCN_NC(n)) shall adhere to this planning.See also ARFCN_NC(n).Formerly: BA_BCCH.In the GSM standards this parameter is called BA (BCCH Allocation).

Dependency: Parameter BCCH_FREQ of the neighbour cell and all ARFCN_NC(n) andBCCH_ARFCN_NC(n) referencing this cell are required to have the samevalue.

GSM 12.20 Class: adjacentCellReselectionGSM 12.20 Attribute: bCCHFrequency




23 BCCH_FREQRecommended DefaultValue:

-

Range: 1-1024Range Semantics: GSM900: 1-124; GSM1800: 512-885Modification State: -Short Description: Absolute RF Channel Number of BCCH ChannelOMC Object: BTSOMC AUI: BCCHOMC GUI: BCCH FrequencyBosch OMC Object: BTSBosch OMC AUI: BCCHFBosch OMC Comments: -Long Description: Read only attribute, which displays the ARFCN of the BCCH channel of a

cell. The BCCH channel is determined by the object CHN with parameterCH_TYPE value 4 (mainBCCH), 5 (mainBCCHCombined) or 8(mainBCCHCombinedCB), respectively.Frequency allocation is matter of cellular network planning. All frequencyrelated attributes (CA_ARFCN, INIT_FREQ, BCCH_FREQ, MA_ARFCN,ARFCN_NC(n), BCCH_ARFCN_NC(n)) shall adhere to this planning.




25

24 BS_AG_BLKS_RESRecommended DefaultValue:

0 for non SMSCB systems, 1 for SMSCB systems

Range: 0-7Range Semantics: Number of reserved blocksModification State: LO/ULShort Description: Number of CCCH (Common Control Channel) blocks within a multiframe

reserved for Access Grant Messages. The number of PCH (PagingChannel) blocks is reduced by the same number.

OMC Object: BTSOMC AUI: BLKACCGRNTOMC GUI: No. of Blocks For Access GrantBosch OMC Object: BTSBosch OMC AUI: CONFCCH-aBosch OMC Comments: -Long Description: The Paging Channel (PCH) and the Access Grant Channel (AGCH) share

the same TDMA frame mapping when combined onto a basic physicalchannel. The channels are shared on a block by block basis, andinformation within each block allows a mobile to determine whether theblock contains paging messages or access grants. Every PCH can beused by the system as AGCH, but it is not allowed to the system to useAGCH-blocks to transmit paging requests. However, to ensure a mobilesatisfactory access to the system, a variable number of the availableblocks in each 51-multiframe can be reserved for access grants only.BS_AG_BLKS_RES gives the number of blocks reserved and is broadcaston the BCCH.It is useful, to set this parameter to the smallest value and let the systemorganise the channel usage. In the case of Mobile Originated Calls moreAGCHs will be needed, in the case of Mobile Terminated Calls thenecessity for PCHs increases. In the average, the number of MobileOriginated Calls is very much higher than the number of MobileTerminated Calls.If this parameter is chosen too high with the result of a PCH-shortage inthe case of high traffic density, there may arise an overload-indication ofthe PCH.See also CH_TYPE

Dependency: Range depends on CH_TYPE of BCCH channel:- 0-7: if BCCH channel is of type mainBCCH- 0-2: if BCCH channel is of type mainBCCHCombined- 1-2: if BCCH channel is of type mainBCCHCombinedCBIf CellBroadcast is enabled for a cell, BS_AG_BLKS_RES must not be setto 0.

GSM 12.20 Class: btsGSM 12.20 Attribute: noOfBlocksForAccessGrant




25 BS_PA_MFRMSRecommended DefaultValue:

4

Range: 0-7Range Semantics: Number of multiframes = BS_PA_MFRMS + 2Modification State: LO/ULShort Description: BS_PA_MRFMS gives the number of 51 TDMA multiframes between

transmissions of paging messages to mobiles of the same paging group.OMC Object: BTSOMC AUI: MULTIFRMPGOMC GUI: No. Of Multiframes Between PagingBosch OMC Object: BTSBosch OMC AUI: CONFCCH-bBosch OMC Comments: -Long Description: When BS_PA_MFRMS is increased , the number of paging groups is

increased too with the advantage that idle subscribers have to be lessactive.BS_PA_MFRMS should be chosen in an appropriate way. If the value istoo small, there may be an overload due to a shortage of paging channels.If the value is too high so that the time between two paging calls is high, itmay occur an overload situation in the paging queue in the BSS.The available paging blocks per CCCH is determined by the BCCHchannel type (9 in case of mainBCCH, 3 in case of mainBCCHCombined)reduced by BS_AG_BLKS_RES (number of blocks reserved for accessgrant) and this multiplied with BS_PA_MFRMS + 2.See also CH_TYPE, BS_AG_BLKS_RES

Dependency: Value should be chosen dependent on CH_TYPE of BCCH channel andBS_AG_BLKS_RES.

GSM 12.20 Class: btsGSM 12.20 Attribute: noOfMultiframesBetweenPaging



27

26 BS_TXPWR_REDRecommended DefaultValue:

0dB = 0

Range: 0-6Range Semantics: Unit: -2 dBModification State: LO/ULShort Description: Base Station TX transmitter power reduction. The maximum power level

which can be used by the BTS is the Base Station Transmitter Peak Powerreduced by BS_TXPWR_RED.

OMC Object: POWEROMC AUI: BSTXPWRREDOMC GUI: BS Tx Power ReductionBosch OMC Object: PCBosch OMC AUI: TXPWRREDBosch OMC Comments: -Long Description: This parameter is used to reduce the BS transmitter maximum peak power

with six steps of nominally 2dB. This allows a fine adjustment of thecoverage by the network operator. This power reduction is set normallyonly once during cell installation. It is a static power reduction and does notrefer to dynamic power control.Note: This parameter is not affected by EN_BS_PC

Dependency: -GSM 12.20 Class: radioCarrierGSM 12.20 Attribute: txPwrMaxReduction




27 BTS-Abis-PositionRecommended DefaultValue:

NoPredecessor

Range: ChoiceRange Semantics: "Predecessor Cell" and distinguished name of predecessor BTS,

"Connected to BSC" or "Prodecessor Unknown"Modification State: LO/ULShort Description: Position of a BTS in a multidrop chain.OMC Object: BTSOMC AUI: PRDBTSUNDEF, PRDBTSOMC GUI: BTS Position, Predecessor CellBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: This parameter allows the BSC to determine how the different BTS are

concatenated in a multidrop chain. In case of an Abis link break the BSCcalculates, which BTSs are affected.If the attribute is set to 'No predecessor cell', then the BTS is the first BTSin the chain. If different objects BTS have the same 'predecessor cell', thenthey form a multicell site (not in case of RBS900).At the GUI the attribute 'BTS Position' can be set to one of the values"Predecessor Cell", "Connected to BSC" or "Prodecessor Unknown". If"Predecessor Cell" is selected the attribute 'Predessor Cell' has to be setto the distinguished name of the predecessor BTS.At the AUI the attribute 'PRDBTSUNDEF' defines whether the BTSposition is known (value 'false') or not known (value 'true'). If the position isknown the attribute 'PRDBTS' has to be set to an empty string if the BTS isconnected directly to the BSC, or set to the distinguished name of thepredecessor BTS if the BTS is connected to another BTS.




29

28 C_MICRO_DELAYED_HORecommended DefaultValue:

40 seconds (=83)

Range: 0-127Range Semantics: multiples of SACCH period (480 msec for TCH resp. 470.77 msec for

SDCCH channels)Modification State: LO/ULShort Description: Threshold for the duration of stay counter, Cdos, of an MS in a Lower

Layer cell. Used during the handover target cell evaluation process tocontrol handovers to neighbouring Lower and Middle Layer cells.Also used to control the use of power budget (PBGT_HO) handoversbetween neighbouring Lower Layer cells.This parameter is ignored for Upper and Middle Layer and Standard cells.

OMC Object: HOCTRLOMC AUI: LOWSLOWOMC GUI: HO from Lower Cell/for Slower MSBosch OMC Object: HOBosch OMC AUI: HOMICROCELL-bBosch OMC Comments: -Long Description: After an assignment to a SDCCH or TCH of a Lower Layer cell (i.e. after

an intercell handover) the duration of stay of the MS in the serving cell ismeasured using the Cdos counter. On assignment the Cdos counter isstarted from 0 and is incremented by 1 for every SACCH multiframe.If a mandatory handover is requested and the Cdos counter is greater thanthe threshold defined by C_MICRO_HO but less than the thresholddefined by C_MICRO_DELAYED_HO the resulting handover shall beperformed with preference to Middle Layer cells. If a handover is triggeredand the Cdos counter has reached the threshold defined byC_MICRO_DELAYED_HO the resulting handover shall be performed withpreference to Lower Layer cells.On call set-up in a Lower Layer cell, the Cdos counter is set to itsthreshold value, C_MICRO_DELAYED_HO, and the MS is immediatelyconsidered to be 'slow' moving (i.e. first handover after call set-up will beperformed with preference to a neighbouring Lower Layer cell).For MS served by Lower Layer cells, power budget handover(PBGT_HOs) are only permitted once the MS has been classified as slowmoving, i.e. Cdos > C_MICRO_DELAYED_HOSee also: C_MICRO_HO, CELL_TYPE, C_UMBRELLA_MICRO_HO

Dependency: Typically: C_MICRO_DELAYED_HO > C_MICRO_HOGSM 12.20 Class: -GSM 12.20 Attribute: -




29 C_MICRO_HORecommended DefaultValue:

20 seconds (=42)


SDCCH channels)Modification State: LO/ULShort Description: Threshold for the duration of stay, Cdos counter,of a MS in a lower (Lower

or Middle) layer cell. Used during the handover target cell evaluationprocess to control handovers from lower to upper cell layer.This parameter is ignored for Upper Layer and Standard cells.

OMC Object: HOCTRLOMC AUI: MICROTHRESHOMC GUI: HO to Higher Cell/for Faster MSBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: After an assignment to a SDCCH or TCH of a Lower or Middle Layer cell

(i.e. after an intercell handover) the duration of stay of the MS in theserving cell is measured using the Cdos counter. On assigment the Cdoscounter is started from 0 and incremented by 1 for every SACCHmultiframe.For Lower and Middle Layer Cell the following holds: If a mandatoryhandover is requested and the Cdos counter is less than the thresholddefined by C_MICRO_HO the resulting handover shall be performed withpreference into Upper Layer cells. A handover into an adjacent lower layercell is only allowed if a target cell of the higher hierarchical cell layer(Upper or Middle Layer) is not available.For Middle Layer Cells the following holds: If a mandatory handover isrequested and the Cdos counter has reached the C_MICRO_HO thresholdthe resulting handover shall be performed with preference to neighbouringMiddle Layer cells (assuming the cdosnc(i) counter has not reached itsC_UMBRELLA_MICRO_HO threshold, in which case a 'layer down'handover to a neighbouring Lower Layer cell will be performed).For Lower Layer Cells the following holds: If a mandatory handover isrequested and the Cdos counter is greater than the threshold defined byC_MICRO_HO but less than the threshold defined byC_MICRO_DELAYED_HO the resulting handover shall be performed withpreference into Middle Layer cells. A handover into an adjacent LowerLayer cell is only allowed if a target cell of the higher hierarchical cell layer(Middle Layer preferred) is not availableAt call set-up on a Lower or Middle Layer cell, the Cdos counter is set to itsthreshold value for that particular layer, C_MICRO_DELAYED_HO (forLower Layer cells) and C_MICRO_HO (for Middle Layer cells). The firsthandover encountered after call set-up will be performed with preferenceto neighbouring cells of the same layer.See also: C_MICRO_DELAYED_HO, CELL_TYPE, C_MICRO_HO,C_UMBRELLA_MICRO_HO, UMBRELLA_MICRO_HYST

Dependency: Typically: C_MICRO_HO < C_MICRO_DELAYED_HOGSM 12.20 Class: -GSM 12.20 Attribute: -



31

30 C_UMBRELLA_MICRO_HORecommended DefaultValue:

40 seconds (=83)


SDCCH channels)Modification State: LO/ULShort Description: Threshold for the duration of stay, Cdosnc(i) counter, of a MS in the

coverage area of a neighbour cell of a lower layer (Middle or Lower). Usedto control handovers from upper to lower cell layer using 'layer down'criteria.This parameter is ignored for Lower Layer and Standard cells.

OMC Object: HOCTRLOMC AUI: UMBTHRESHOMC GUI: Umbrella Cell ThresholdBosch OMC Object: HOBosch OMC AUI: HOUMBRCELL-bBosch OMC Comments: -Long Description: After channel allocation on a SDCCH or TCH of a Middle or Upper Layer

cell the duration of stay of the MS in the coverage area of all lower layerneighbour cells (Lower or Middle Cell Layer) is measured. On assignmentof a SDCCH channel the Cdosnc(i) counter is started for all neighbouringlower layer cells that satisfy the TH5 condition.The Cdosnc(i) counter ranges from 0 to C_UMBRELLA_MICRO_HO. Thecounter is incremented by 1 for every SACCH multiframe that the receivedlevel for lower layer neighoubring cells satisfies the TH5 condition. If theTH5 condition is not met or the rxlev for a cell is not available in themeasurement report, the counter is decremented by 1.If the duration of stay in the coverage area of a lower layer neighbour cellreaches the threshold defined for this counter,C_UMBRELLA_MICRO_HO, a 'layer down' handover is triggeredSee also UMBRELLA_MICRO_HYST, CELL_TYPE, C_MICRO_HO,C_MICRO_DELAYED_HO





31 CA_ARFCNRecommended DefaultValue:

empty

Range: 1-1024Range Semantics: GSM900: 1-124; GSM1800: 512-885Modification State: LO/ULShort Description: Cell Allocation Absolute RF Channel Number. This information is used for

frequency hopping and lists all frequencies that are allowed to be used forFH in the cell.

OMC Object: BTSOMC AUI: CELLALLOCOMC GUI: Cell AllocationBosch OMC Object: CELLBosch OMC AUI: CABosch OMC Comments: -Long Description: The CA_ARFCN is part of the information element cell channel description

and is used to provide the absolute radio frequency channel numbers thatcan be used for hopping. The parameter MA_ARFCN selects thefrequencies actually used for a specific frequency hopping system fromthis list.Frequency allocation is matter of cellular network planning. All frequencyrelated attributes (CA_ARFCN, INIT_FREQ, BCCH_FREQ, MA_ARFCN)shall adhere to this planning.See also MA_ARFCN

Dependency: INIT_FREQ, BCCH_FREQ, MA_ARFCN must belong to same frequencyband.Modification of the attribute is possible in BTS state locked. Formodification in BTS state unlocked all FH systems have to be in statelocked.

GSM 12.20 Class: btsGSM 12.20 Attribute: cellAllocation



33

32 CCCH Load Ind. Threshold(PAGING_LOAD_THR)

Recommended DefaultValue:

63

Range: 0-32767Range Semantics: -Modification State: LO/ULShort Description: Defines the number of busy slots to start/stop sending messages between

the BTS and BSC.OMC Object: BTSOMC AUI: THRCCCHLDINDOMC GUI: Threshold CCCH Load IndicationBosch OMC Object: BTSBosch OMC AUI: LDINDCCH-aBosch OMC Comments: -Long Description: Used for the load indication of CCHs.

See also EN_CCCH_LOAD_IND and CCCH_LOAD_IND_PERIODDependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: thresholdCCCHLoadIndication




33 CCCH_COMB_WITH_SDCCH


-

Range: BooleanRange Semantics: False: mainBCCH, True: mainBCCHCombined(-CB)Modification State: -Short Description: Indicates whether the CCCH is combined with Stand-alone Dedicated

CCH (SDCCH)OMC Object: BTSOMC AUI: CCCHWSDCHOMC GUI: CCCH Combined with SDCCHBosch OMC Object: BTSBosch OMC AUI: NRCCCH.COMBINED_WITH_SDCCHBosch OMC Comments: -Long Description: This is a read-only parameter which can only be set implicitly via

parameter CH_TYPE during creation of object CHN.If this parameter has the value 'True' the timeslot 0 of the BCCH frequencyis of type mainBCCHCombined (channel type v), otherwise it is of typemainBCCH (channel type iv)GSM name: BS_CCCH_SDCCH_COMBSee also 'No. of CCCH', CH_TYPE

Dependency: channelTypeGSM 12.20 Class: -GSM 12.20 Attribute: -



35

34 CCCH_LOAD_IND_PERIODRecommended DefaultValue:

240 sec = 255

Range: 1-255Range Semantics: Unit: 4 * 51 TDMA multiframes = 941.5 msecModification State: LO/ULShort Description: Defines the time between CCCH_LOAD_INDICATION messages.OMC Object: BTSOMC AUI: PRDCCCHLDINDOMC GUI: Period CCCH Load IndicationBosch OMC Object: BTSBosch OMC AUI: LDINDCCH-bBosch OMC Comments: -Long Description: Used for the load indication of CCHs. This parameter specifies the

periodicity of the message load indication CCH which is sent from the BTSto the BSC. The load indication is calculated with the parametersRACH_MEAS_PERIOD and RACH_BUSY_THRES. If the received signallevel is greater than or equal to the value of RACH_BUSY_THRES thenthe RACH burst in question will be indicated as busy (one or more MSshave tried to access the network).See also EN_CCCH_LOAD_IND, CCCH Load Ind. Threshold(PAGING_LOAD_THR), RACH_BUSY_THRES, RACH_MEAS_PERIOD

Dependency: CCCH_LOAD_IND_PERIOD >= RACH_MEAS_PERIODGSM 12.20 Class: btsGSM 12.20 Attribute: periodCCCHLoadIndication




35 CELL_BAR_ACCESSRecommended DefaultValue:

False

Range: BooleanRange Semantics: False: Cell is unbarred, True: Cell is barredModification State: LO/ULShort Description: This attribute indicates whether MSs are prevented from accessing the cell

for (re)selection.OMC Object: BTSOMC AUI: CELLBAROMC GUI: Cell BarredBosch OMC Object: CELLBosch OMC AUI: CBARBosch OMC Comments: -Long Description: A MS can only camp on those cells, which are not barred. In case of

emergency calls, the access to the net is allowed. Handover into a barredcell is possible. This parameter is used to configure "handover-only" cells(i.e. this parameter does not effect a mobile's behaviour in dedicatedmode).It should be taken care, that not too many cells of a network are barred atthe same time to avoid overload in unbarred neighbour cells and to allowsubscribers to find another cell, where calls are allowed.For cell selection according to the C2 criteria for GSM phase 2 MS seealso CELL_BAR_QUALIFY. The barred status of a cell with C2 criteriadepends both on CELL_BAR_ACCESS and on the cell's priority indicatedby CELL_BAR_QUALIFY.A cell can also be barred only for certain access classes, see AC_CN.

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: cellBarred



37

36 CELL_BAR_QUALIFYRecommended DefaultValue:

False

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: This attribute indicates the affecting cell priority for cell selection with C2

criteria.OMC Object: BTSOMC AUI: CELLBARQOMC GUI: Cell Reselection: Cell Bar QualifyBosch OMC Object: CELLBosch OMC AUI: C2CRIT-eBosch OMC Comments: -Long Description: A phase 2 MS selects only a cell of low priority if there is no cell of normal

priority. This parameter has no influence on cell reselection.The priority of cells is used for hierarchical cells. lower layer cells are set tonormal priority. A MS that is not moving selects the lower layer cell andcamps there. A moving MS when reselecting another cell does not obeythe cell priority and can reselect a upper layer cell.The barred status of a cell depends both on CELL_BAR_ACCESS and onthe cell's priority indicated by CELL_BAR_QUALIFY. IfCELL_BAR_QUALIFY is set the cell priority is low independent onCELL_BAR_ACCESS. If CELL_BAR_QUALIFY is not set the normalmeaning of CELL_BAR_ACCESS applies.See also CELL_RESELECT_PARAM_IND, CELL_RES_OFFSET,TEMPORARY_OFFSET and PENALTY_TIME, which specify the criteriafor cell (re)selection according to the C2 criteria for GSM phase 2 MS.





37 CELL_RES_OFFSETRecommended DefaultValue:

5

Range: 0-63Range Semantics: 2 * CELL_RES_OFFSET dBModification State: LO/ULShort Description: This attribute applies an offset to the C2 reselection criteria for that cellOMC Object: BTSOMC AUI: CELLOFFOMC GUI: Cell Reselection: Cell OffsetBosch OMC Object: CELLBosch OMC AUI: C2CRIT-bBosch OMC Comments: -Long Description: The CELL_RES_OFFSET is a static offset that can be added to or

subtracted from the C2 re-selection criterion in order to either encourageor discourage mobiles from re-selecting certain cells.CELL_RES_OFFSET is added to the C2 reselection criteria ifPENALTY_TIME is in the range 0 to 30. For a cell with PENALTY_TIMEset to 31 the C2 reselection criteria is reduced by CELL_RES_OFFSET.CELL_RES_OFFSET can also be used in dual band networks toencourage mobiles to re-select one band in preference to another.See also CELL_RESELECT_PARAM_IND, TEMPORARY_OFFSET,PENALTY_TIME. These parameters specify the criteria for cell reselectionaccording to the C2 criteria for GSM phase 2 MS.

Dependency: Should be set to 0 in case of Hierarchical Cell Networks.GSM 12.20 Class: -GSM 12.20 Attribute: -



39

38 CELL_RESELECT_HYST.Recommended DefaultValue:

6dB = 3

Range: 0-7Range Semantics: Unit: 2dBModification State: LO/ULShort Description: This parameter specifies the RF power threshold value an MS has to

receive in idle mode in order to reselect another cell of another locationarea.

OMC Object: BTSOMC AUI: CELLRESELHYSTOMC GUI: Cell Reselect HysteresisBosch OMC Object: RADIOBosch OMC AUI: CRESHYSTBosch OMC Comments: -Long Description: This parameter is used in case of cell (re)selection on the border of two

different location areas. If an idle MS moves through an area, on theborder of two cells, which are part of two different location areas, too manylocation updates would occur, if there was no cell reselect hysteresis set.With the hysteresis set, the new cell is only selected if the RX (receive)level exceeds the specified hysteresis value for 5 seconds.

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: cellReselectHysteresis




39 CELL_RESELECT_PARAM_IND


False

Range: BooleanRange Semantics: False: disable C2 (C1 is used), True: enable C2Modification State: LO/ULShort Description: Enables the C2 criterion for cell re-selectionOMC Object: BTSOMC AUI: C2ENABLEOMC GUI: Cell Reselection: C2 CriterionBosch OMC Object: CELLBosch OMC AUI: C2CRIT-aBosch OMC Comments: -Long Description: The CELL_RESELECT_PARAM_IND parameter is used to enable the C2

criterion for cell re-selection during Idle Mode. IfCELL_RESELECT_PARAM_IND is disabled the C1 criterion will beapplied. The C2 reselection criteria was introduced to support hierarchicalcell structures to encourage mobiles to 'camp-on' different cell layers inaccordance with its speed by using static and dynamic offsets. A MSshould reselect a cell layer that corresponds to its speed, i.e. a MS, that ismoving very slowly or not moving at all, should reselect a lower layer cell,and a fast moving MS should reselect a upper layer cell.C2 is calculated for all cells in a mobile's strongest server list that exhibit apositive C1 value. If C1 < 0, C2 is not calculated for that cell.See also CELL_RES_OFFSET, TEMPORARY_OFFSET,PENALTY_TIME. These parameters specify the criteria for cell reselectionaccording to the C2 criteria for GSM phase 2 MS.

Dependency: The C2 criterion is only applicable to Phase 2 mobilesGSM 12.20 Class: -GSM 12.20 Attribute: -



41

40 CELL_TYPERecommended DefaultValue:

StandardCell

Range: 0-15Range Semantics: 0 = Standard, 1 = Lower, 2 = Middle, 3 = Upper, 4-15 spareModification State: LO/ULShort Description: Defines the cell type (cell layer) . The cell type definition determines the

type of Handover Threshold Comparison algorithm employed in that cellwhich also influences the Handover Target Cell Identification process.

OMC Object: BTSOMC AUI: CELLTYPEOMC GUI: Cell TypeBosch OMC Object: CELLBosch OMC AUI: CTYPEBosch OMC Comments: Range:STANDARDCELL = 0, MICROCELL = 1, MACROCELL = 2,

UMBRELLACELL = 3Long Description: A cell may be defined as a Standard Cell, Lower Layer cell, Middle Layer

cell, or Upper Layer cell.Special cell layers can be identified by capitals at the beginning of thename of the respective cell layer (Lower Layer, Middle Layer, Upper Layer)while the relations between Cell Layers are described by small letters (alower cell layer, a upper cell layer).The cell layer determines the algorithm used for handover and the priorityranking of neighbour cells.In non-hierarchical networks only cells of Standard Layer shall be used. Inhierarchical cell structures all cell layers are allowed.See also : C_MICRO_DELAYED_HO, C_MICRO_HO,C_UMBRELLA_MICRO_HO, CELL_TYPE_NC(n)

Dependency: The value for CELL_TYPE and CELL_TYPE_NC(n) referencing the samecell are normally equal.

GSM 12.20 Class: -GSM 12.20 Attribute: -




41 CELL_TYPE_NC(n)Recommended DefaultValue:

StandardCell

Range: 0-15Range Semantics: 0 = Standard, 1 = Lower, 2 = Middle, 3 = Upper, 4-15 spareModification State: LO/ULShort Description: Defines the cell type (cell layer) of the neighbour cell to be considered in

handover algorithm.OMC Object: ADJCELLOMC AUI: CELLTYPEOMC GUI: Cell TypeBosch OMC Object: NCELLBosch OMC AUI: CDESC-lBosch OMC Comments: -Long Description: The CELL_TYPE_NC(i) parameter defines the cell type of a cell in the

neighbour lists of its neighbouring cells. A cell may be defined as aStandard cell, Lower Layer cell, Middle Layer cell, or Upper Layer cell.Special cell layers can be identified by capitals at the beginning of thename of the respective cell layer (Lower Layer, Middle Layer, Upper Layer)while the relations between Cell Layers are described by small letters (alower cell layer, a upper cell layer).The cell layer NC determines the priority ranking of neighbour cells.In non-hierarchical networks only cells of Standard Layer shall be used. Inhierarchical cell structures all cell layers are allowed.See also : C_MICRO_DELAYED_HO, C_MICRO_HO,C_UMBRELLA_MICRO_HO, CELL_TYPE

Dependency: The value for CELL_TYPE and CELL_TYPE_NC(n) referencing the samecell are normally equal.




43

42 CH_TYPERecommended DefaultValue:

-

Range: 0,3-8Range Semantics: 0 = TCHFull, 3 = SDCCH, 4 = mainBCCH, 5 = mainBCCHCombined, 6 =

CCCH, 7 = SDCCHCB, 8 = mainBCCHCombinedCBModification State: -Short Description: CHannel TYPEOMC Object: CHNOMC AUI: CHANTYPEOMC GUI: Channel TypeBosch OMC Object: CHNBosch OMC AUI: CHTYPEBosch OMC Comments: Range:TCHF = 0, TCHFH = 2, SDCCH = 3, BCCH = 4, BCCHC = 5,

CCCH = 6, SDCCHB = 7, BCCHCB = 8Long Description: Possible Channel types are:

0 = i (TCHFull): TCH/F + FACCH/F + SACCH/TF3 = vii (SDCCH): SDCCH/8 + SACCH/C84 = iv (mainBCCH): FCCH + SCH + BCCH + CCCH5 = v (mainBCCHCombined): FCCH + SCH + BCCH + CCCH + SDCCH/4+ SACCH/C46 = vi (CCCH): BCCH + CCCH7 = vii+ (SDCCHCB): This channel type is derived from channel type 3such that CBCH replaces SDCCH number 2.8 = v+ (mainBCCHCombinedCB): This channel type is derived fromchannel type 5 such that CBCH replaces SDCCH number 2.If multiple CCCHs are necessary the mobiles are ordered to a maximum of4 groups according to their IMSI (International Mobile Subscriber Identity).Each group will listen to paging messages or make random accesses onlyon this specific CCCH. The first CCCH shall always use timeslot 0, theremaining CCCHs shall use timeslots 2,4, and 6.The BSS Local Configuration Area defines the maximum number of CCCHchannels in MAX_CCCH_SLOTS

Dependency: -GSM 12.20 Class: channelGSM 12.20 Attribute: channelCombination




43 Channel-UsageRecommended DefaultValue:

-

Range: 0-3Range Semantics: 0: not used, 1: idle TCH, 2: busy TCH, 3: Control ChannelModification State: -Short Description: Determines the current usage state of each channel which is controlled by

the RT.OMC Object: RTOMC AUI: GETUSAGE-RTOMC GUI: Channel UsageBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: The usage state of the channel is defined as follows:

Not used: The channel is not usable due to any reason (not yet created,not in the operational state Active...)Idle TCH: The TCH channel currently is not in use.Busy TCH: The TCH channel currently is in use.Control Channel: The channel is of type BCCH/CCCH or SDCCH




45

44 CI (in CGI)Recommended DefaultValue:

-

Range: 0-65535Range Semantics: -Modification State: LO/ULShort Description: Cell Identification of this cell.OMC Object: BTSOMC AUI: CELLIDOMC GUI: Cell Global Identity: Cell IdentificationBosch OMC Object: CELLBosch OMC AUI: CIBosch OMC Comments: -Long Description: Uniquely identifies the current cell within the LocationArea.

The Cell Global Identity (CGI) consisting of LAI and CI uniquely identifies acell within the whole world. The Location Area Identification (LAI) consistsof the concatenation of MCC, MNC and LAC.See also MCC (in LAI), MNC (in LAI), LAC (in LAI)

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: cellGlobalIdentity.CellIdentity




45 CI_NC(n)Recommended DefaultValue:

-

Range: 0-65535Range Semantics: -Modification State: LO/ULShort Description: Cell Identification of neighbour cell n.OMC Object: ADJCELLOMC AUI: CELLIDOMC GUI: Cell Global Identity: Cell IdentificationBosch OMC Object: NCELLBosch OMC AUI: CDESC-aBosch OMC Comments: -Long Description: Uniquely identifies a neighbour cell within the LocationArea.

The Cell Global Identity (CGI) consisting of LAI and CI uniquely identifies acell within the whole world. The Location Area Identification (LAI) consistsof the concatenation of MCC, MNC and LAC.For every radio cell in a GSM PLMN, a number of up to 32 neighbouringcells can be specified to be monitored by every MS with a call in progress.The MS takes signal strength measurements on the BCCH carriers ofthese neighbour cells and reports them to the BSS. In the BSC, themeasurement result reports of every MS are evaluated and form the basisfor handover decisions. In order to identify the neighbour cells, the MSdecodes the Base Station Identity Code (BSIC) of every monitoredneighbour cell and includes this information together with information onthe respective BCCH carrier frequency in the measurement result reports.In handover required messages sent from the BSC to the MSC, thepreferred target cells for handover are identified by LAC (DMCS) resp. LAI(Ericsson) and CI. Therefore, in the BSC, the cell identification informationprovided by the MS has to be mapped onto the LAC/LAI and CI used toidentify radio cells in the PLMN.See also MCC_NC(n), MNC_NC(n), LAC_NC(n)

Dependency: CI_NC(n) shall have the same value as parameter CI of that neighbourcell.

GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: cellGlobalIdentity.CellIdentity



47

46 Circuit Id Code CICRecommended DefaultValue:

-

Range: 0-65535Range Semantics: -Modification State: -Short Description: Circuit Identity Code of a 64 kbit/s timeslot in the E1/T1 link (A interface)

between MSC and BSS (TCE/STF).OMC Object: TRCOMC AUI: CIDCPCM, CIDCTSOMC GUI: Circuit Id: PCM, TSBosch OMC Object: TRCBosch OMC AUI: MSCCIC-a-bBosch OMC Comments: -Long Description: The circuit identity code is unique in the MSC and defines the address of a

64 kbit/s timeslot in the A interface as seen by the MSC.If a 2048Kbits/s (E1) or 1544Kbits/s (T1) digital path is used then thecircuit identification code contains in the 5 least significant bits a binaryrepresentation of the actual number of the timeslot which is assigned tothe circuit. The remaining bits in the CIC are used where necessary, toidentify one among several systems interconnecting an originating anddestination point.





47 Clock_SourceRecommended DefaultValue:

2 (pcm)

Range: 1,2,5Range Semantics: 1 = acg, 2 = pcm, 5 = extModification State: LOShort Description: This attribute specifies the type of clock source that the primary CCG shall

use.This parameter is only for RBS900.

OMC Object: CCGOMC AUI: CLKSRCOMC GUI: Clock SourceBosch OMC Object: CCGBosch OMC AUI: CLKSRC-aBosch OMC Comments: -Long Description: Possible clock sources for the primary CCG are:

The Auxiliary Clock Generator (ACG) is an additional board in the BTScentral unit, which provides the BTS with a stabilised clock signal with anaccuracy of 0.05 ppm or better. The PCM clock is derived from anavailable PCM line from the LIC. The external clock is derived from anexternal device, e.g. from a co-located BTS.This parameter is not supported by the other BTS types than RBS900because it is HW dependent and has to be set during installation at BTSsite.See also 'Clock_Source (Redundant)'




49

48 Clock_Source (Redundant)Recommended DefaultValue:

2 (pcm)

Range: 0,1,2,5Range Semantics: 0 = no redundant clock source, 1 = acg, 2 = pcm, 5 = extModification State: LOShort Description: This optional attribute specifies the type of clock source to be used by a

redundant CCG if it exists.This parameter is only for RBS900.

OMC Object: CCGOMC AUI: RDTCLKSRCOMC GUI: Redundant Clock SourceBosch OMC Object: CCGBosch OMC AUI: CLKSRC-bBosch OMC Comments: -Long Description: Possible clock sources for the redundant CCG are:

The Auxiliary Clock Generator (ACG) is an additional board in the BTScentral unit, which provides the BTS with a stabilised clock signal with anaccuracy of 0.05 ppm or better. The PCM clock is derived from anavailable PCM line from the LIC. The external clock is derived from anexternal device, e.g. from a co-located BTS.This parameter is not supported by the other BTS types than RBS900because it is HW dependent and has to be set during installation at BTSsite.See also Clock_Source





49 Connected ACC E1Recommended DefaultValue:

-

Range: structureRange Semantics: Identification of an ACCE1PORTModification State: -Short Description: The Connected ACC E1 parameter models the connection between the

SRS E1 port and the ACC E1 port.BSC of type BCF only.

OMC Object: SDFUE1PORTOMC AUI: ACCE1OMC GUI: Connected ACC E1Bosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: -Dependency: This parameter is only required at creation if the parameter 'E1 Port Type'

has value 'internal'.GSM 12.20 Class: -GSM 12.20 Attribute: -



51

50 CRC 4 FramingRecommended DefaultValue:

-

Range: BooleanRange Semantics: -Modification State: -Short Description: The CRC 4 Framing parameter indicates whether a crc4 error detection

algorithm is being applied to timeslot 0 of the SDFU E1 port.BSC of type BCF only.

OMC Object: SDFUE1PORTOMC AUI: CRC4OMC GUI: CRC4 FramingBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -




51 Diversity IndicationRecommended DefaultValue:

True

Range: BooleanRange Semantics: False: without diversity, True: with diversityModification State: -Short Description: Indicates whether two receiving antennas are connected for diversity.

This parameter is only for RBS900.OMC Object: RTOMC AUI: DIVERSITYOMC GUI: DiversityBosch OMC Object: RTBosch OMC AUI: DIVBosch OMC Comments: -Long Description: Diversity employs two spatially separated receiving antennas in order to

improve uplink signal quality.This parameter is not supported by the other BTS types than RBS900because it is HW dependent and has to be set during installation at BTSsite.See also: Backup Capability




53

52 Downlink DTX DataRecommended DefaultValue:

False

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: This attribute indicates whether the Discontinuous Transmission (DTX) on

downlink data TCHs is enabled or disabled.OMC Object: BTSOMC AUI: DTXDATAOMC GUI: DTX: Downlink DataBosch OMC Object: CELLBosch OMC AUI: DTXDL-aBosch OMC Comments: -Long Description: This attribute indicates whether the Discontinuous Transmission (DTX) on

downlink for non-transparent data on TCHs is enabled or disabledindependent on the MSC request.See also DTX, Downlink DTX Speech, W_QUAL_PC, W_QUAL_HO

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: dtxDownlink




53 Downlink DTX SpeechRecommended DefaultValue:

False

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: This attribute indicates whether the Discontinuous Transmission (DTX) on

downlink for speech on TCHs is used, if the MSC does not explicitly forbidthe usage of DTX for the specific speech call.

OMC Object: BTSOMC AUI: DTXSPOMC GUI: DTX: Downlink SpeechBosch OMC Object: CELLBosch OMC AUI: DTXDL-bBosch OMC Comments: -Long Description: If DTX is used and there is no speech, frames between BTS and MS are

only sent for comfort noise and measurements. (In the DTX mode, full ratespeech is encoded at 13 kbit/s when the user is effectively speaking, but ina speech pause information is transmitted at a bit rate around 500 bit/s.This low rate flow is sufficient to encode the comfort noise, which isregenerated to ensure that the listener does not think that the connectionis broken.)When DTX is applied, actual transmission on the radio path is reduced.This will reduce the overall interference level in the network. Note thattransmitting in DTX mode does not save timeslots on the air-interface.See also DTX, Downlink DTX Data, W_QUAL_PC, W_QUAL_HO

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: dtxDownlink



55

54 DTXRecommended DefaultValue:

0 (mayBeUsed)

Range: 0-2Range Semantics: 0 = mayBeUsed, 1 = shallBeUsed, 2 = shallNotBeUsedModification State: LO/ULShort Description: This attribute specifies whether the Discontinuous Transmission (DTX)

mode on the uplink is allowed, applied or not applied, respectively.OMC Object: BTSOMC AUI: DTXOMC GUI: DTX: UplinkBosch OMC Object: CELLBosch OMC AUI: DTXULBosch OMC Comments: Range:MAY = 0, SHALL = 1, SHALLNOT = 2Long Description: If DTX is used and there is no speech, frames between MS and BTS are

only sent for comfort noise and measurements. (In the DTX mode, full ratespeech is encoded at 13 kbit/s when the user is effectively speaking, but ina speech pause information is transmitted at a bit rate around 500 bit/s.This low rate flow is sufficient to encode the comfort noise, which isregenerated to ensure that the listener does not think that the connectionis broken.)When DTX is applied, actual transmission on the radio path is reduced.This will save battery power in the MS and reduce the overall interferencelevel in the network. Note that transmitting in DTX mode does not savetimeslots on the air-interface.See also 'Downlink DTX Data', 'Downlink DTX Speech'

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: dtxUplink




55 E1 Port TypeRecommended DefaultValue:

-

Range: 0-3Range Semantics: 0 = mlink, 1 = abis, 2 = internal, 3 = unusedModification State: -Short Description: The SDFU E1 Port Type specifies what the E1 link is used for. It can be a

link to the MSC, an Abis link, internal server link or unused.BSC of type BCF only.

OMC Object: SDFUE1PORTOMC AUI: TYPEOMC GUI: E1 Port TypeBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



57

56 E1 Allocation(BCON)Recommended DefaultValue:

-

Range: Full distinguished name of the SDFU E1 Port of type Abis-linkRange Semantics: -Modification State: -Short Description: Identifies the SDFU E1 Port which provides the Abis-interface link

represented by the BCON object.BCF only

OMC Object: BCONOMC AUI: E1ALLOCOMC GUI: Available E1 Allocation PortBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -




57 E1 Allocation(MCON)Recommended DefaultValue:

-

Range: Full distinguished name of the SDFU E1 Port of type M-linkRange Semantics: -Modification State: -Short Description: Identifies the SDFU E1 Port which provides the M-interface link

represented by the MCON object.BCF only

OMC Object: MCONOMC AUI: E1ALLOCOMC GUI: Available E1 Allocation PortBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



59

58 EN_ACC_BARRINGRecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enables automatic access class BARRING in case of overload.OMC Object: BTSOMC AUI: ACCCLASSBAROMC GUI: Access Class Overload Control: Barring EnabledBosch OMC Object: CELLBosch OMC AUI: OVERLOAD-aBosch OMC Comments: -Long Description: Barring is used to prevent MSs belonging to special access classes from

making access attempts (including emergency call attempts) orresponding to paging messages in the specified area. The use of thisfacility allows to recover from overload.The MS stores the access control class on its Subscriber Identity Module(SIM). If the access for a certain class is barred, MSs with that class mayonly try to get a connection in the neighbour cells.Automatic barring is done by the BSS in case of overload. Depending onthe severity of overload the BSS starts with barring access classes 0-9with random starting class and step size M1 (unbarring with step size M2).If classes 0-9 are barred and there is still an overload situation, the BSScontinues barring with access classes 10-15. The barring sequence isgiven in parameter 'Barring Sequence' and the step size in N1 (unbar: N2).The timer T17 (MAP-Timer) and T18 (MAP-Timer) are used for barringresp. unbarring.Access class barring can only be enabled if it is enabled in the localconfiguration area, too.See also: Barring Sequence, M1, M2, N1, N2, T17 (MAP-Timer), T18(MAP-Timer)The operator can bar manually special MS access classes with parameterAC_CN.





59 EN_BS_PCRecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable dynamic power control for the BS (downlink)OMC Object: POWEROMC AUI: BSRFPWROMC GUI: Enable BS RF Power ControlBosch OMC Object: PCBosch OMC AUI: ENBSRFPCBosch OMC Comments: -Long Description: This parameter is used to enable or disable dynamic downlink RF power

control in a specific cell. If BS power control is enabled, the RF outputpower on every activated downlink channel except for the carrier of theBCCH channel is dynamically adapted to the current radio conditions,otherwise the BTS always transmits at maximum power.Note: BS_TXPWR_RED is not affected by this flag.See also related power control POW_INCR_STEP_SIZE,POW_RED_STEP_SIZE, A_QUAL_PC, W_QUAL_PC, A_LEV_PC,L_RXQUAL_DL_P, L_RXLEV_DL_P, U_RXQUAL_DL_P,U_RXLEV_DL_P, P_CON_ACK, P_CON_INTERVAL, EN_MS_PC




61

60 EN_BSS_HORecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enables the BSS to perform intercell handover. When it is disabled, the

MSC will decide and perform handover.OMC Object: HOCTRLOMC AUI: INTERDECOMC GUI: Enable Handover: Intercell DecisionBosch OMC Object: HOBosch OMC AUI: ENICDECBosch OMC Comments: -Long Description: Intercell handover for TCH and SDCCH may be performed by the MSC

(MSC-controlled / external) or autonomously by the BSC (BSC-controlled /internal). The O&M flag EN_BSS_HO is used to enable or disable BSC-internal intercell handover for handover requests originating in a specificcell of a BSS. This flag is independent of the flag EN_INTER_HO whichenables or disables the generation of requests for intercell handover in theindividual cells of a BSS. However, the flag EN_BSS_HO is onlymeaningful if intercell handover is enabled.Disabling BSS-controlled intercell handover gives the MSC the full decisionauthority on handover requests and increases the handover processingload in the MSC.BSC-controlled internal intracell handover is not affected by the flagEN_BSS_HO.See also EN_INTER_HO

Dependency: -GSM 12.20 Class: bscGSM 12.20 Attribute: enableInternalInterCellHandover




61 EN_CCCH_LOAD_INDRecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable CCCH (RACH and PCH) LOAD Indication recognition proceduresOMC Object: BTSOMC AUI: LOADINDOMC GUI: Load Indication EnabledBosch OMC Object: BTSBosch OMC AUI: ENLDINDBosch OMC Comments: -Long Description: This parameter is used to enable/disable the periodic sending of Common

Control Channel Load Indication messages from the BTS to the BSC for aspecific cell.If enabled, CCCH LOAD Indication messages containing information onthe current load situation on the random access channels (RACH) and thepaging channels (PCH) of the concerned cell are periodically sent from theBTS to the BSC. The sending rate is determined by the O&M parameterCCCH_LOAD_IND_PERIOD. In the case of multiple CCCH, independentCCCH LOAD Indication messages are sent for each CCCH subchannel.In the BSC, the CCCH LOAD Indication messages are evaluated in orderto detect overload situations and to initiate appropriate countermeasures.Disabling CCH LOAD Indication may be useful in some critical situations toprevent Abis interface from signalling overload or the BSC from processoroverload. Normally, however, CCCH LOAD indication should be enabled toallow RACH and PCH overload detection and appropriatecountermeasures in the BSC or OMC.See also CCCH Load Ind. Threshold and CCCH_LOAD_IND_PERIOD




63

62 EN_DIST_HORecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enables MS distance handover processOMC Object: HOCTRLOMC AUI: MSDITPROCOMC GUI: Enable Handover: Optional MS DistanceBosch OMC Object: HOBosch OMC AUI: ENBSSHOC-cBosch OMC Comments: -Long Description: This parameter is used to enable or disable intercell handover due to the

MS-BS distance criterion. If the timing advance for the MS becomes toobig, because it is too far away from the BS, handover has to take place toa cell that is closer to the MS.No handover is executed if intercell handover is disabled by the parameterEN_INTER_HO.See also EN_INTER_HO and MS_DIST_MAX

Dependency: -GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: enableOptHandoverProc




63 EN_INCOM_HORecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: enable Incoming intercell handover (in case of service)OMC Object: HOCTRLOMC AUI: INCOMHOOMC GUI: Enable Handover: IncomingBosch OMC Object: HOBosch OMC AUI: ENINCOMHOBosch OMC Comments: -Long Description: This parameter enables or disables incoming intercell handover in the

individual cells of a BSS. It affects intercell handover from TCH to TCH aswell as intercell handover from SDCCH to SDCCH and SDCCH to TCH.Temporarily disabling incoming handovers may be useful in case ofmaintenance at that cell.This function is independent of the flag EN_INTER_HO which enables ordisables the execution of intercell handover originating at the concernedcell.




65

64 EN_INTER_HORecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable intercell handoverOMC Object: HOCTRLOMC AUI: INTERHOOMC GUI: Enable Handover: Internal Inter-CellBosch OMC Object: HOBosch OMC AUI: ENBSSHOC-aBosch OMC Comments: -Long Description: The flag EN_INTER_HO enables or disables the handover comparison

process for outgoing intercell handover in the individual cells of a BSS. Itaffects intercell handover from TCH to TCH as well as intercell handoverfrom SDCCH to SDCCH. If intercell handover is disabled, requests forintercell handover (BSC-controlled or MSC-controlled) originating in theconcerned cell are inhibited, regardless of the current radio linkmeasurements of the calls in progress. Temporarily disabling outgoinghandovers from a specific cell may be useful during updates of handovercontrol parameters or to prevent neighbouring cells or network elements(BSC, MSC) from handover accesses or handover load, respectively.If intercell handover is enabled, requests for intercell handover originatingin the concerned cell initiate a BSC controlled (internal) or MSC-controlled(external) intercell handover.This function is independent of the flag EN_BSS_HO which enables ordisables the BSS-internal execution of intercell handover and ofEN_INTRA_HO which enables or disables intracell handover.See also EN_RXLEV_HO, EN_RXQUAL_HO, EN_DIST_HO,EN_PBGT_HO, EN_INTRA_HO, EN_SDCCH_HO, EN_BSS_HO,EN_LOAD_REGARD, CELL_TYPE, T7 (MAP-Timer)





65 EN_INTRA_HORecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable intracell handoverOMC Object: HOCTRLOMC AUI: INTRAHOOMC GUI: Enable Handover: Internal Intra-CellBosch OMC Object: HOBosch OMC AUI: ENBSSHOC-dBosch OMC Comments: -Long Description: Specifies whether handovers within the cell are enabled or not. An intracell

handover is used to switch a call from one TCH (traffic channel) orSDCCH to another within the same cell (either on the same or on differentfrequencies). The reason to do so is the receive quality. Preferable anotherfrequency or at least a distant time slot on the same frequency should beselected.If intracell handover is disabled, requests for intracell handover due tointerference are inhibited. Note that an inhibited request for intracellhandover is not automatically substituted by a request for intercellhandover.This function is independent of all intercell handover O&M parameters(e.g. EN_INTER_HO).Intracell handover is disabled if frequency hopping (FH) is activated andfor a time period of A_LEV_HO after channel allocation.See also RXLEV_DL_IH, RXLEV_UL_IH, EN_INTER_HO, T7_IHO

Dependency: -GSM 12.20 Class: bscGSM 12.20 Attribute: enableInternalIntraCellHandover



67

66 EN_LOAD_REGARDRecommended DefaultValue:

False

Range: BooleanRange Semantics: False: disregard traffic load, True: regard traffic loadModification State: LO/ULShort Description: Enable handover regarding traffic load.OMC Object: HOCTRLOMC AUI: LOADREGOMC GUI: Enable Handover: Load RegardBosch OMC Object: HOBosch OMC AUI: ENLOADREGBosch OMC Comments: -Long Description: In addition to the handover target cell evaluation process which sets up a

list of preferred adjacent cells depending on the path loss criteria of therespective neighbouring cells, the procedure handover regarding trafficload is used to arrange the target cell list taking into account the trafficload, too. If a hierarchical cell system is used the list of preferred targetcells regarding traffic load is only evaluated for handover within the samecell layer.See also FREElevel_X (X=1..4), FREEfactor_X (X=1..5), LINKfactor(0,n),EN_INTER_HO





67 EN_MS_PCRecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable dynamic power control for all MSs in a cell (uplink).OMC Object: POWEROMC AUI: PWRCTRLMSOMC GUI: Enable MS RF Power ControlBosch OMC Object: PCBosch OMC AUI: ENMSPCBosch OMC Comments: -Long Description: Specifies whether dynamic uplink power control is enabled or not. If True,

the MS adopts power according to the power control commands from theBSC. This will save the MS battery. The main reason for power control is,however, improving the spectral efficiency within the network (cell).Reducing power on BTS or MS, whilst keeping similar communicationquality, decreases interference caused on other calls in the surroundingarea. If this parameter is False, the MS will always transmit at maximumpower level, that is calculated by the BSC as the minimum level of the MSpower class and MS_TXPWR_MAX.Disabling MS power control may be useful for test purposes but isinappropriate during regular network operation since cellular networkplanning (frequency reuse) is based on the assumption of dynamic RFpower control on the uplink.See also MS_TXPWR_MAX, POW_INCR_STEP_SIZE,POW_RED_STEP_SIZE, A_QUAL_PC, W_QUAL_PC, A_LEV_PC,L_RXQUAL_UL_P, U_RXQUAL_UL_P, L_RXLEV_UL_P,U_RXLEV_UL_P, P_CON_ACK, P_CON_INTERVAL, EN_BS_PC




69

68 EN_PBGT_HORecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable handover due to power budget (PBGT)OMC Object: HOCTRLOMC AUI: PWRBGHOOMC GUI: Enable Handover: Optional Power BudgetBosch OMC Object: HOBosch OMC AUI: ENBSSHOC-bBosch OMC Comments: -Long Description: This parameter is used to enable or disable intercell handover due to

power budget criteria in a specific cell. Of all handovers, this handover isthe most common. A power budget handover takes place as soon as abetter cell with respect to the power budget is available to handle the call.A power budget handover is based on the path loss on the downlink. Theassumption is made that the path loss is equivalent in both directions. Thepath loss is the difference between the actual transmit power of the BTSand the signal level received by the MS. Generally, the MS will switch tothe BTS with the lowest path loss.If power budget handover is disabled the power budget criterion is stillevaluated in the BSC to compile the list of preferred target cells forhandover requests with other causes. If power budget handover is enabledand intercell handover is enabled (EN_INTER_HO), requests for intercellhandover with cause 'better cell' (power budget) may be generated andinitiate an intercell handover under control of the BSC or MSC.See also A_PBGT_HO, HO_MARGIN(0,n), MS_TXPWR_MAX,MS_TXPWR_MAX(n), EN_INTER_HO

Dependency: -GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: enableOptHandoverProc




69 EN_RF_RES_INDRecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable/disable flag for sending of RF Resource Indication from BTS/TRX

to BSC.OMC Object: HOCTRLOMC AUI: IDLECHNSUPVOMC GUI: Enable Idle Channel SupervisionBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: The idle channel supervision is used for the interference quality of

channels, which are candidates for channel allocation, intracell andintercell handover. The philosophy is to direct every MS onto an idlechannel with an interference level as low as possible. This is applied forTCHs. For the allocation of SDCCHs of a BTS the consideration ofinterference bands is not required.The EN_RF_RES_IND flag enables/disables the measurement ofinterference levels on idle TCHs in the BTS/TRX, the sending of theresults as RF resource indication messages from the BTS/TRX to theBSC, and channel allocation regarding interference level in the BSC.See also INTAVE, INT_BOUND_XFormerly: EN_IDLE_CHN_SUP




71

70 EN_RXLEV_HORecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable intercell handover due to receive levelOMC Object: HOCTRLOMC AUI: RXLEVHOOMC GUI: Enable Handover: Rx LevelBosch OMC Object: HOBosch OMC AUI: ENBSSHOS-bBosch OMC Comments: -Long Description: If the BSC determines that either the signals have too low quality or too

low level, the BSC can perform power control for both the MS and the BSor initiate a handover. If power control is not done because of the cell typeor not helpful anymore, the BS normally starts the intercell handoverprocedure.This parameter is used to enable or disable intercell handover due toRXLEV criterion (received signal strength) in a specific cell. If RXLEVhandover is enabled and intercell handover is enabled (EN_INTER_HO),requests for intercell handover with cause 'RXLEV' may be generated andinitiate an intercell handover under control of the BSC or MSC.See also EN_INTER_HO, L_RXLEV_UL_H, L_RXLEV_DL_H





71 EN_RXQUAL_HORecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable receiver quality handoverOMC Object: HOCTRLOMC AUI: RXQUALHOOMC GUI: Enable Handover: Rx QualityBosch OMC Object: HOBosch OMC AUI: ENBSSHOS-aBosch OMC Comments: -Long Description: If the BSC determines that either the signals have too low quality or too

low level, it decides to perform power control for both the MS and the BS.If power control is not helpful anymore, the BS normally starts the intercellhandover procedure.This parameter is used to enable or disable intercell handover due toRXQUAL criterion (received signal quality) in a specific cell. If RXQUALhandover is enabled and intercell handover is enabled (EN_INTER_HO),requests for intercell handover with cause 'RXQUAL' may be generatedand initiate an intercell handover under control of the BSC or MSC.See also EN_INTER_HO, L_RXQUAL_UL_H, L_RXQUAL_DL_H




73

72 EN_SDCCH_HORecommended DefaultValue:

True

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable SDCCH - SDCCH handoverOMC Object: HOCTRLOMC AUI: SDCCHHOOMC GUI: Enable Handover: SDCCHBosch OMC Object: HOBosch OMC AUI: ENBSSHOS-cBosch OMC Comments: -Long Description: Specifies whether SDCCH intercell and intracell handovers are enabled or

not. Usually, handovers take place on the TCH, when the call is in thespeech stage. However, in rare cases it may be necessary to perform ahandover when, e.g. the call is still in establishment phase. In that case theSDCCH will be handed over to another frequency or time slot. This type ofhandover is more likely to take place during the transmission of shortmessages (SMS).This parameter is only meaningful if either intracell handover(EN_INTRA_HO) or intercell handover (EN_INTER_HO) or both of themare enabled.MSC 5ESS GSM8.0 is not supporting the feature.

Dependency: MSC has also to support SDCCH - SDCCH HO. If not, only BSC controlledHO of this type will be possible.





73 EN_SDCCH_TCH_HORecommended DefaultValue:

False

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Enable Directed Retry (SDCCH - TCH Handover)OMC Object: HOCTRLOMC AUI: SDCCHTCHHOOMC GUI: Enable Handover: SDCCHTCHBosch OMC Object: HOBosch OMC AUI: ENDIRRETBosch OMC Comments: -Long Description: Directed Retry allows a MS assigned to a SDCCH in a congested cell with

no TCHs available to be handed over to a TCH of an appropriateneighbour cell. This feature is triggered by assignment or handoverprocedure and employs internal or external handover procedures.See also: T_SDCCH_HO_ALLOWED

Dependency: Sales option Directed Retry has to be enabled within the LocalConfiguration Area of the BSC (DIRRETC1/DIRRETC2).To ensure successful operation of DR the BSS shall also support 'BSSAPQueuing'. In case of Handover during Queueing, the Directed Retry will notbe executed before the timer T_SDCCH_HO_ALLOWED is expired.For full DR functionality the MSC shall also support DR and Queuing; ifthis is not the case the operator has to accept a reduced DR functionaloty.




75

74 Ext. Error Id (n)Recommended DefaultValue:

-

Range: 512-527 (RBS900 Indoor), 528-543 (RBS900/4 Outdoor), 8704-8711(BTS2000 and BTS2000/2C Outdoor), 8704-8727 (BTS2000 Indoor)

Range Semantics: -Modification State: LO/ULShort Description: This parameter contains the error code (external error id) the digital input

point will be associated with.OMC Object: BTC-ARUOMC AUI: ERRORIDxOMC GUI: Error IdBosch OMC Object: BTCBosch OMC AUI: DIP-dBosch OMC Comments: -Long Description: The digital input point parameters contain information required by the BTC

to assign individual configuration data to each input line on the ControlAlarm and Control Port (CAP/CCP) for the RBS900 or the external alarmbox (EAB) for the BTS2000. Depending on the BTS type up to 24 externaldevices can be connected to the BTC (see table below), but only 16 arevisible on the OMC.This parameter defines the error id of the alarm message, which isgenerated if the physical input potential changes to high or low (defined bythe parameter 'Alarm State (n)').The ranges of the external error ids are predefined in the BTS and aredifferent for each BTS type:RBS900 - indoor: 512-527 (16)RBS900/4 - outdoor: 528-543 (16)BTS2000/2C - outdoor: 8704-8711 (8)BTS2000 - outdoor: 8704-8711 (8)BTS2000 - indoor: 8704-8727 (24)For the BTS2000 family the external error ids are defined fix for each inputline and cannot be changed from the OMC. The BSC does not forward thevalues defined on the OMC to the BTS2000. The external error ids on theOMC are only used as a reference for the OMC parameter 'external alarmstring'.The connection of physical devices to the input points is also fix. TheRBS900 uses the external error ids and an exact range check isperformed. For the RBS900 the operator can assign for different BTSesdifferent error ids to the same input line. For the RBS900 indoor evendifferent physical devices can be connected to the input lines. For theRBS900 outdoor this connection is fix.See also Input Point Adr (n), Input Hysterese (n), Alarm State (n)





75 EXTC-TypeRecommended DefaultValue:

-

Range: 0-3Range Semantics: 0 = PPP, 1 = D2MX, 2 = PPCX, 3 = CEPModification State: -Short Description: Extension card type

BSC of type BCE only.OMC Object: EXTCOMC AUI: CARDTYPEOMC GUI: EXTC TypeBosch OMC Object: EXTCBosch OMC AUI: EXTCTYPEBosch OMC Comments: Range:PPP = 0, D2MX = 1, PPCX = 2, CEP = 3Long Description: The extension card can be of type PPP, CEP, PPCX or D2MX. In case of

PPCX or D2MX the parameter 'PMC Allocation' is mandatory.Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



77

76 FHE Slice AddressRecommended DefaultValue:

RDN of RT

Range: 0-23Range Semantics: -Modification State: -Short Description: Address of the FHE Slice that the RT is connected to.

This parameter is only for RBS900.OMC Object: RTOMC AUI: FHEOMC GUI: FHE Slice AddressBosch OMC Object: RTBosch OMC AUI: FHESLICE-aBosch OMC Comments: -Long Description: The Frequency Hopping Equipment (FHE) is used in the RBS900 for

baseband hopping. The RTs are split in a digital and a transceiver part thatare connected by the FHE switch. The transceiver part has a fixconnection to the FHE. The digital part is connected with wires. Theoperator must set this parameter for each RT to indicate which FHE slicethe RT is wired to.This parameter reflects the physical hardware of the RBS900. Therefore itis not supported by the other BTS types.

Dependency: Value must be unique among RTs within the same BTS.GSM 12.20 Class: -GSM 12.20 Attribute: -




77 Fis_Syn_DelayRecommended DefaultValue:

not sync.

Range: not sync, 0, 1, 2Range Semantics: 0 = 0m < X < 10m, 1 = 10m < X < 30m, 2 = 30m < X < 50mModification State: LOShort Description: This parameter specifies the synchronisation delay to be considered, when

the BTS is synchronised with another BTS.This parameter is only for RBS900.

OMC Object: CCGOMC AUI: ISSYNC, SYNCHRONOMC GUI: Master/Slave Mode, Sync DelayBosch OMC Object: CCGBosch OMC AUI: CCGMODE-a-bBosch OMC Comments: -Long Description: If the clock is synchron (i.e. the BTS is synchronised with another BTS)

this parameter contains the information to compensate the delay causedby the distance, e.g. cable length (measured in Meters (m)), betweensynchronised BTSs. The value specifies the cable length from the slaveBTS to the master BTS.This parameter is not supported by the other BTS types than RBS900because it is not foreseen to synchronise cells over rack bounderies.Note, that the BTS2000 is able to house up to 3 cells within one rack.




79

78 FREEfactor_X (X=1..5)Recommended DefaultValue:

14,15,16,17,18

Range: 0-32Range Semantics: 0 = -16dB, 1 = -15dB, ..., 32 = +16dBModification State: LO/ULShort Description: Correction factor concerning the number of free channels in the handover

target cell identification process regarding traffic load.OMC Object: HOCTRLOMC AUI: FREEFACOMC GUI: Cell Order Criterion: Free FactorBosch OMC Object: CELLBosch OMC AUI: LDREG-bBosch OMC Comments: Range:(-16)-16Long Description: The parameters FREElevel_X and FREEfactor_X control the ranking of

target cells for handover regarding traffic load. To classify the traffic loadsituation in the cells the number of free channels is mapped into one offive traffic load bands defined by FREElevel_X. To each of these bands afactor is defined by FREEfactor_X that determines the correction factor,i.e. the weight of the traffic load situation, for the handover target cellidentification.If the traffic load information of an NC is not available in the serving cell,i.e. this target cell is not part of the same BSS area, the BCE_CHautonomously uses the default value FREEfactor(n)=0 for the respectiveNC.See also FREElevel_X (X=1..4), LINKfactor(0,n), EN_LOAD_REGARD





79 FREElevel_X (X=1..4)Recommended DefaultValue:

1,2,3,4

Range: 0-255Range Semantics: Unit: channelsModification State: LO/ULShort Description: The count of the free channels is divided by these boundary parameters

into five bands that are used as traffic load indication of the cell forhandover target cell identification.

OMC Object: HOCTRLOMC AUI: FREELEVOMC GUI: Cell Order Criterion: Free LevelBosch OMC Object: CELLBosch OMC AUI: LDREG-aBosch OMC Comments: -Long Description: The parameters FREElevel_X and FREEfactor_X control the ranking of

target cells for handover regarding traffic load. To classify the traffic loadsituation in the cells the number of free channels is mapped into one offive traffic load bands defined by FREElevel_X. To each of these bands afactor is defined by FREEfactor_X that determines the correction factor,i.e. the weight of the traffic load situation, for the handover target cellidentification.See also FREEfactor_X (X=1..5), LINKfactor(0,n), EN_LOAD_REGARD

Dependency: FREElevel_1 < FREElevel_2 < FREElevel_3 < FREElevel_4GSM 12.20 Class: -GSM 12.20 Attribute: -



81

80 HO_MARGIN(0,n)Recommended DefaultValue:

5dB = 29

Range: 0-48Range Semantics: 0 = -24dB, 1 = -23dB, ..., 48 = +24dBModification State: LO/ULShort Description: This parameter defines the margins for power budget handover from the

current cell to the neighbouring cells.OMC Object: ADJCELLOMC AUI: HOMGRNOMC GUI: Handover MarginBosch OMC Object: NCELLBosch OMC AUI: CDESC-jBosch OMC Comments: Range:(-24) - 24 dBLong Description: A basic radio criterion for handover decisions in the BSC is the power

budget (PBGT) criterion. The power budget is a relative measure of theMS link power budget on a potential new link to a neighbouring cell withrespect to the current link in the serving cell. Basically, the MS shouldalways communicate with or be handed over to the cell or BTS with thelowest possible link power budget. Evaluating the power budget criterioninvolves the parameter HO_MARGIN(0,n) for every neighbouring cellwhich is subtracted from the respective PBGT(n) results, thus, producing a'handover margin'. By proper choice of the parameters HO_MARGIN(0,n)in adjacent cells, it is possible to shift cell boundaries and to achieve ahandover hysteresis which prevents repetitive handovers betweenadjacent cells.If the list of neighbouring cells is being altered, it should be ensured thathandover processing is only active if all lists of neighbouring cell evaluationparameters are properly installed by O&M, i.e. the individual lists have theright relation to each other. If necessary, the handover processing may besuspended during a change until this is guaranteed.Higher values: fewer handovers will be triggered but the size of the cell willbe bigger and so the spectral efficiency will decrease.Lower values: more handovers will be triggered which will cause moresignaling traffic and can lead to ping pong situations.This parameter is unique for the relation between a cell and a neighbourcell.See also EN_PBGT_HO, A_PBGT_HO

Dependency: If HO_MARGIN(A,B) is the margin for a handover from cell A to theadjacent cell B (specified in cell A) and vice versa, then the dB valuesshould adhere to: HO_MARGIN(A,B) + HO_MARGIN(B,A) > 0dB

GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: hoMargin




81 Hopping ModeRecommended DefaultValue:

-

Range: 0-1Range Semantics: 0: baseband hopping, 1: synthesiser hoppingModification State: -Short Description: Frequency hopping mode the BTS is able to support.OMC Object: BTSOMC AUI: HOPMODEOMC GUI: Hopping ModeBosch OMC Object: CELLBosch OMC AUI: HOPPMODEBosch OMC Comments: Range:BASEBAND = 0, SYNTHESIZER = 1Long Description: Baseband hopping: One RT for each frequency that is used for frequency

hopping is required. Recommended for cells with 4 or more TRX's.Synthesiser hopping: Each RT is able to hop over a number of frequenciesindependent of the existance of other RTs.The RBS900 is only able to support baseband hopping. For the other BTStypes the hopping mode can be modified locally with the RBT dependingon the hardware capabilities.




83

82 HSNRecommended DefaultValue:

0 (cyclic)

Range: 0-63Range Semantics: 0 = Cyclic hopping, 1-63 = Random hoppingModification State: LOShort Description: The Hopping Sequence Number is used to derive the order in which the

allocated frequencies are used.OMC Object: FHOMC AUI: HOPSEQNOOMC GUI: Hopping Sequence NumberBosch OMC Object: FHSBosch OMC AUI: HSNRBosch OMC Comments: -Long Description: HSN is a constant parameter in the frequency generator equation used in

the frequency hopping algorithm. In case of HSN=0 a cyclic hoppingsequence of the frequencies defined by the mobile allocation (MA, seealso MA_ARFCN) is generated. In all other cases a quasi randomsequence is generated which is well calculable by linked BTS and MS. Thefeature of random frequency hopping is the statistical distribution ofcochannel interference and adjacent channel interference by choosingdifferent values for HSN in cochannel cells (same frequency in next cellclusters) and adjacent cells (different frequencies in same cluster). Fromthe viewpoint of cellular network planning it is useful to test the individualinterference relation between two cells by using a cyclic hopping sequenceHSN=0. This would be applicable in systems with a great number ofallocated frequencies or in synchronised systems.Physical channels on the same timeslot with equal MA and HSN arediscriminated by the index offset MAIO, which is calculated by the BSS.Due to an MS procedure for measurement reporting with DTX enabled, theuse of cyclic hopping where N mod 13 = 0 should be avoided (N being thenumber of frequencies in the MA).

Dependency: -GSM 12.20 Class: frequencyHoppingSystemGSM 12.20 Attribute: hoppingSequenceNumber




83 INIT_FREQRecommended DefaultValue:

-

Range: 1-1024Range Semantics: GSM900: 1-124; GSM1800: 512-885Modification State: LOShort Description: Each RT in a BTS is assigned a fixed Initial carrier Frequency.OMC Object: RTOMC AUI: INITFREQOMC GUI: Initial FrequencyBosch OMC Object: RTBosch OMC AUI: IFBosch OMC Comments: -Long Description: This parameter specifies the Absolute RF Channel Number (ARFCN)

which is assigned to a TRX. Every ARFCN defines a particular pair offrequencies in the uplink and downlink frequency band. The initial ARFCNsgiven by INIT_FREQ for all TRXs of a BTS shall be different.Frequency allocation is matter of cellular network planning. All frequencyrelated attributes (CA_ARFCN, INIT_FREQ, BCCH_FREQ, MA_ARFCN,ARFCN_NC(n) BCCH_ARFCN_NC(n)) shall adhere to this planning.The initial frequency is used in case of non hopping.

Dependency: -GSM 12.20 Class: radioCarrierGSM 12.20 Attribute: carrierFrequencyList



85

84 Input Hysterese (n)Recommended DefaultValue:

1000 msec = 100

Range: 0-255Range Semantics: Unit: 10 msecModification State: LO/ULShort Description: The delay a state change at the input point is surveyed by the BTC before

reporting the alarm.BTS of type RBS900 only.

OMC Object: BTC-ARUOMC AUI: HYSTTIMExOMC GUI: Hysteresis TimeBosch OMC Object: BTCBosch OMC AUI: DIP-bBosch OMC Comments: -Long Description: The digital input point parameters contain information required by the BTC

to assign individual configuration data to each input line on the ControlAlarm and Control Port (CAP/CCP) for the RBS900 or the external alarmbox (EAB) for the BTS2000. Depending on the BTS type up to 24 externaldevices can be connected to the BTC, but only 16 are visible on the OMC.This parameter specifies the time the signal at the input point must bestable before an alarm is reported or ceased, respectively.This parameter is not supported by the BTS2000 because the BTS2000has fixed assigned Input Hysterese.See also Input Point Adr (n), Alarm State (n), Ext. Error Id (n)





85 Input Point Adr (n)Recommended DefaultValue:

-

Range: 0-15Range Semantics: -Modification State: LO/ULShort Description: Address of the input point.

BTS of type RBS900 only.OMC Object: BTC-ARUOMC AUI: SCANPOINTxOMC GUI: Input PointBosch OMC Object: BTCBosch OMC AUI: DIP-aBosch OMC Comments: -Long Description: The digital input point parameters contain information required by the BTC

to assign individual configuration data to each input line on the ControlAlarm and Control Port (CAP/CCP) for the RBS900 or the external alarmbox (EAB) for the BTS2000. Depending on the BTS type up to 24 externaldevices can be connected to the BTC, but only 16 are visible on the OMC.This parameter specifies the address (number) of the input point 'n' that isconfigured by the parameter Input Hysterese (n), Alarm State (n), and Ext.Error Id (n) at index 'n'.This parameter is not supported by the BTS2000 because the BTS2000has fixed assigned Input Points.




87

86 INT_BOUND_XRecommended DefaultValue:

4,9,15,20,25

Range: 0-63Range Semantics: -110 + INT_BOUND_X dBm (0 = less than -110 dBm, 63 = greater than -

48 dBm)Modification State: LO/ULShort Description: five Interference Boundaries for idle mode interference classification,

X=1,2,3,4,5OMC Object: HOCTRLOMC AUI: IATHRESH0 - IATHRESH4OMC GUI: Interference Averaging: ThresholdsBosch OMC Object: RADIOBosch OMC AUI: INTAVTHRBosch OMC Comments: -Long Description: The idle channel supervision is used for the interference quality of

channels, which are candidates for channel allocation, intracell andintercell handover. The philosophy is to direct every MS onto an idlechannel with an interference level as low as possible. This is applied forTCHs. For the allocation of SDCCHs of a BTS the consideration ofinterference bands is not required.For this idle channel supervision, the interference of an idle channel ismeasured and classified into five interference classes. The interferenceclasses are defined by the units of this parameter.See also EN_RF_RES_IND, INTAVEGSM name: O-X5

Dependency: INT_BOUND_1 < INT_BOUND_2 < .. < INT_BOUND_5GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: hoThresholdInterferenceParam




87 INTAVERecommended DefaultValue:

2880 msec = 6

Range: 1-31 (480 msec - 14880 msec)Range Semantics: multiples of SACCH period (480 msec)Modification State: LO/ULShort Description: Interference Averaging period defined in terms of the number of SACCH

multiframes.OMC Object: HOCTRLOMC AUI: IAPERIODOMC GUI: Interference Averaging: PeriodBosch OMC Object: RADIOBosch OMC AUI: INTAVPERBosch OMC Comments: -Long Description: The idle channel supervision is used for the interference quality of

channels, which are candidates for channel allocation, intracell andintercell handover. The philosophy is to direct every MS onto an idlechannel with an interference level as low as possible. This is applied forTCHs. For the allocation of SDCCHs of a BTS the consideration ofinterference bands is not required.The procedure for measurement of interference is based on the gaining ofRXLEV measurements on idle TCHs of each TRX averaged over anumber of SACCH multiframes specified by parameter INTAVE. Thisperiod is also used as sending period from the BTS/TRX to the BSC.See also EN_RF_RES_IND, INT_BOUND_X, A_LEV_HO

Dependency: -GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: interferenceAveragingParam



89

88 IP AddressRecommended DefaultValue:

-

Range: structureRange Semantics: dot separated integersModification State: -Short Description: The IP Address of the server.

BSC of type BCF only.OMC Object: SERVEROMC AUI: IPADDROMC GUI: IP AddressBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: The IP Address is set by the BMA.Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -




89 L_RXLEV_DL_HRecommended DefaultValue:

GSM900: 8; GSM1800: 10

Range: 0-63Range Semantics: -110 + L_RXLEV_DL_H dBm (0 = less than -110 dBm, 63 = greater than -

48 dBm)Modification State: LO/ULShort Description: Lower signal level threshold for handover regarding downlink levelOMC Object: HOCTRLOMC AUI: LRXLEVDLHOMC GUI: Signal Strength: Lower Downlink LimitBosch OMC Object: HOBosch OMC AUI: HOCSS-bBosch OMC Comments: -Long Description: If the averaged measurement value RXLEV_DL is lower than the threshold

L_RXLEV_DL_H a handover is initiated. Dependent on the cell layer(CELL_TYPE) the BSC performs power control by increasing the BTStransmit power prior to handover.L_RXLEV_DL_P should be larger than L_RXLEV_DL_H to assure that nohandover occurs before the power control process is used.L_RXLEV_DL_H should be less than RXLEV_ACCESS_MIN andRXLEV_MIN of the serving cell and all neighbour cells to avoid a handoverimmediately after the MS is assigned to the cell.See also RXLEV_DL_IH, L_RXLEV_DL_P, RXLEV_MIN(n),RXLEV_ACCESS_MIN, EN_RXLEV_HO, A_LEV_HO

Dependency: L_RXLEV_DL_H <= L_RXLEV_DL_PL_RXLEV_DL_H <= RXLEV_DL_IHL_RXLEV_DL_H < RXLEV_MIN(for this cell) in all NCsL_RXLEV_DL_H < RXLEV_ACCESS_MIN

GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: hoThresholdLevParam



91

90 L_RXLEV_DL_PRecommended DefaultValue:

GSM900: 25; GSM1800: 27

Range: 0-63Range Semantics: -110 + L_RXLEV_DL_P dBm (0 = less than -110 dBm, 63 = greater than -

48 dBm)Modification State: LO/ULShort Description: Lower signal level threshold for downlink power control.OMC Object: POWEROMC AUI: LRXLEVDLPOMC GUI: Signal Strength: Downlink Power IncreaseBosch OMC Object: PCBosch OMC AUI: SSDL-aBosch OMC Comments: -Long Description: A power increase is carried out on the downlink if the averaged

measurement value RXLEV_DL is lower than the thresholdL_RXLEV_DL_P. The power increase is even be done if the signal qualitywould lead to power decrease.L_RXLEV_DL_P should be larger than L_RXLEV_DL_H to assure that nohandover occurs before the power control process is used.L_RXLEV_DL_P should be equal or larger than RXLEV_MIN andRXLEV_ACCESS_MIN, which represent the cell boundary. The lower it ischosen the higher the probability for Power Control operations and for thisthe reduction of interference and transmitter power will be.POW_INCR_STEP_SIZE should be chosen smaller than the rangebetween the upper and lower power control boundaries.See also U_RXLEV_DL_P, L_RXLEV_DL_H, EN_BS_PC

Dependency: L_RXLEV_DL_P >= L_RXLEV_DL_HL_RXLEV_DL_P < U_RXLEV_DL_PU_RXLEV_DL_P - L_RXLEV_DL_P > POW_INCR_STEP_SIZERXLEV_MIN(n) <= L_RXLEV_DL_PRXLEV_ACCESS_MIN <= L_RXLEV_DL_P

GSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: pcLowerThresholdLevParam




91 L_RXLEV_UL_HRecommended DefaultValue:

-104 dBm = 6

Range: 0-63Range Semantics: -110 + L_RXLEV_UL_H dBm (0 = less than -110 dBm, 63 = greater than -

48 dBm)Modification State: LO/ULShort Description: Lower signal level threshold for handover regarding uplink levelOMC Object: HOCTRLOMC AUI: LRXLEVULHOMC GUI: Signal Strength: Lower Uplink LimitBosch OMC Object: HOBosch OMC AUI: HOCSS-aBosch OMC Comments: -Long Description: If the averaged measurement value RXLEV_UL is lower than the threshold

L_RXLEV_UL_H a handover is initiated. Dependent on the cell layer(CELL_TYPE) the BSC performs power control by increasing the MStransmit power prior to handover.L_RXLEV_UL_P should be larger than L_RXLEV_UL_H to assure that nohandover occurs before the power control process is used.See also RXLEV_UL_IH, L_RXLEV_UL_P, EN_RXLEV_HO, A_LEV_HO

Dependency: L_RXLEV_UL_H <= L_RXLEV_UL_PL_RXLEV_UL_H <= RXLEV_UL_IH

GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: hoThresholdLevParam



93

92 L_RXLEV_UL_PRecommended DefaultValue:

-90 dBm = 20 (GSM900 & GSM1800)

Range: 0-63Range Semantics: -110 + L_RXLEV_UL_P dBm (0 = less than -110 dBm, 63 = greater than -

48 dBm)Modification State: LO/ULShort Description: Lower signal level threshold for uplink power control.OMC Object: POWEROMC AUI: LRXLEVULPOMC GUI: Signal Strength: Uplink Power IncreaseBosch OMC Object: PCBosch OMC AUI: SSUL-aBosch OMC Comments: -Long Description: A power increase is carried out on the uplink if the averaged measurement

value RXLEV_UL is lower than the threshold L_RXLEV_UL_P. The powerincrease is even be done if the signal quality would lead to powerdecrease.L_RXLEV_UL_P should be larger than L_RXLEV_UL_H to assure that nohandover occurs before the power control process is used.POW_INCR_STEP_SIZE should be chosen smaller than the rangebetween the upper and lower power control boundaries.See also U_RXLEV_UL_P, L_RXLEV_UL_H, EN_MS_PC

Dependency: L_RXLEV_UL_P >= L_RXLEV_UL_HL_RXLEV_UL_P < U_RXLEV_UL_PU_RXLEV_UL_P - L_RXLEV_UL_P > POW_INCR_STEP_SIZE

GSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: pcLowerThresholdLevParam




93 L_RXQUAL_DL_HRecommended DefaultValue:

4: 1.6% to 3.2%

Range: 0-7Range Semantics: 0: Bit Error Rate (BER) less than 0.2%, 1: 0.2% to 0.4%, 2: 0.4% to 0.8%,

3: 0.8% to 1.6%, 4: 1.6% to 3.2%, 5: 3.2% to 6.4%, 6: 6.4% to 12.8%, 7:greater than 12.8%

Modification State: LO/ULShort Description: Lower signal quality threshold for handover regarding downlink levelOMC Object: HOCTRLOMC AUI: LRXQUALDLHOMC GUI: Signal Quality: Lower Downlink LimitBosch OMC Object: HOBosch OMC AUI: HOCSQ-bBosch OMC Comments: -Long Description: If the averaged measurement value RXQUAL_DL is worse than the

threshold L_RXQUAL_DL_H a handover is initiated.Note that a low parameter value stands for a high quality (i.e. low Bit ErrorRate (BER)).See also: L_RXQUAL_DL_P, EN_RXQUAL_HO, A_QUAL_HO

Dependency: L_RXQUAL_DL_H shall be set to a lower quality than L_RXQUAL_DL_P,i.e. L_RXQUAL_DL_H > L_RXQUAL_DL_P

GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: hoThresholdQualParam



95

94 L_RXQUAL_DL_PRecommended DefaultValue:

3: 0.8% to 1.6%



Modification State: LO/ULShort Description: Lower signal quality threshold for downlink power control.OMC Object: POWEROMC AUI: LRXQUALDLPOMC GUI: Signal Quality: Downlink Power IncreaseBosch OMC Object: PCBosch OMC AUI: SQDL-aBosch OMC Comments: -Long Description: A power increase is carried out on the downlink if the averaged

measurement value RXQUAL_DL is worse than the thresholdL_RXQUAL_DL_P. The power increase is even be done if the signal levelwould lead to power decrease.Note that a low value stands for a high quality (i.e. low Bit Error Rate(BER)).See also U_RXQUAL_DL_P, L_RXQUAL_DL_H, EN_BS_PC

Dependency: L_RXQUAL_DL_P shall be set to a higher quality than L_RXQUAL_DL_H,i.e. L_RXQUAL_DL_P < L_RXQUAL_DL_HL_RXQUAL_DL_P shall be set to a lower quality than U_RXQUAL_DL_P,i.e. L_RXQUAL_DL_P > U_RXQUAL_DL_P

GSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: pcLowerThresholdQualParam




95 L_RXQUAL_UL_HRecommended DefaultValue:

4: 1.6% to 3.2%



Modification State: LO/ULShort Description: Lower signal quality threshold on the uplink for handoverOMC Object: HOCTRLOMC AUI: LRXQUALULHOMC GUI: Signal Quality: Lower Uplink LimitBosch OMC Object: HOBosch OMC AUI: HOCSQ-aBosch OMC Comments: -Long Description: If the averaged measurement value RXQUAL_UL is worse than the

threshold L_RXQUAL_UL_H a handover is initiated.Note that a low parameter value stands for a high quality (i.e. low Bit ErrorRate (BER)).See also L_RXQUAL_UL_P, EN_RXQUAL_HO, A_QUAL_HO

Dependency: L_RXQUAL_UL_H shall be set to a lower quality than L_RXQUAL_UL_P,i.e. L_RXQUAL_UL_H > L_RXQUAL_UL_PFor FH this parameter might need an adaption on a per cell basisregarding Performance Measurements and Drive Tests.

GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: hoThresholdQualParam



97

96 L_RXQUAL_UL_PRecommended DefaultValue:

3: 0.8% to 1.6%



Modification State: LO/ULShort Description: Lower signal quality threshold on the uplink for power control.OMC Object: POWEROMC AUI: LRXQUALULPOMC GUI: Signal Quality: Uplink Power IncreaseBosch OMC Object: PCBosch OMC AUI: SQUL-aBosch OMC Comments: -Long Description: A power increase is carried out on the uplink if the averaged measurement

value RXQUAL_UL is worse than the threshold L_RXQUAL_UL_P. Thepower increase is even be done if the signal level would lead to powerdecrease.Note that a low value stands for a high quality (i.e. low Bit Error Rate(BER)).See also U_RXQUAL_UL_P, L_RXQUAL_UL_H, EN_MS_PC

Dependency: L_RXQUAL_UL_P shall be set to a higher quality than L_RXQUAL_UL_H,i.e. L_RXQUAL_UL_P < L_RXQUAL_UL_HL_RXQUAL_UL_P shall be set to a lower quality than U_RXQUAL_UL_P,i.e. L_RXQUAL_UL_P > U_RXQUAL_UL_P

GSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: pcLowerThresholdQualParam




97 LAC (in LAI)Recommended DefaultValue:

-

Range: 0-65535Range Semantics: -Modification State: LO/ULShort Description: The Location Area Code of this cell.OMC Object: BTSOMC AUI: LAIDLACOMC GUI: Cell Global Identity: Location Area: LACBosch OMC Object: CELLBosch OMC AUI: LAI-cBosch OMC Comments: -Long Description: Uniquely identifies the location area of the current cell within a PLMN.

The Location Area Identification (LAI) consists of the concatenation ofMCC, MNC and LAC. MCC and MNC are fixed numbers assigned toidentify the country and the GSM PLMN in that country. The LAC identifiesa location area within the PLMN. It consists of one or more cells identifiedby CI.See also MCC (in LAI), MNC (in LAI), CI (in CGI)

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: cellGlobalIdentity.LocationAreaIdentity.LocationAreaCode



99

98 LAC_NC(n)Recommended DefaultValue:

-

Range: 0-65535Range Semantics: -Modification State: LO/ULShort Description: The Location Area Code of Neighbour Cell n.OMC Object: ADJCELLOMC AUI: LAIDLACOMC GUI: Cell Global Identity: Location Area: LACBosch OMC Object: NCELLBosch OMC AUI: CDESC-fBosch OMC Comments: -Long Description: Uniquely identifies the location area of neighbour cell n within a PLMN.

The Location Area Identification (LAI) consists of the concatenation ofMCC, MNC and LAC. MCC and MNC are fixed numbers assigned toidentify the country and the GSM PLMN in that country. The LAC identifiesa location area within the PLMN. It consists of one or more cells identifiedby CI.For every radio cell in a GSM PLMN, a number of up to 32 neighbouringcells have to be specified to be monitored by every MS with a call inprogress. The MS takes signal strength measurements on the BCCHcarriers of these neighbour cells and reports them to the BSS. In the BSC,the measurement result reports of every MS are evaluated and form thebasis for handover decisions. In order to identify the neighbour cells, theMS decodes the Base Station Identity Code (BSIC) of every monitoredneighbour cell and includes this information together with information onthe respective BCCH carrier frequency in the measurement result reports.In handover required messages sent from the BSC to the MSC, thepreferred target cells for handover are identified by LAC (DMCS) resp. LAI(Ericsson) and CI. Therefore, in the BSC, the cell identification informationprovided by the MS has to be mapped onto the LAC/LAI and CI used toidentify radio cells in the PLMN.See also MCC_NC(n), MNC_NC(n), CI_NC(n)

Dependency: LAC_NC(n) is required to have the same value as parameter LAC (in LAI)of that neighbour cell.

GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: cellGlobalIdentity.LocationAreaIdentity.LocationAreaCode




99 LIC-Alarm Mask (n)Recommended DefaultValue:

1st rack: 0x00F0D5, 2nd rack: 0x0000D4

Range: 0-0xFFFFFFRange Semantics: -Modification State: LO/ULShort Description: Defines an alarm mask for the 24 inputs of the LIC interface.

This parameter is only for RBS900.OMC Object: BTCOMC AUI: LICALRMMSK0, LICALRMMSK1OMC GUI: LIC Data: Alarm MaskBosch OMC Object: BTCBosch OMC AUI: LIC-gBosch OMC Comments: -Long Description: Besides the Abis interface the Link Interface Concentrator (LIC) panel

provides additionally 24 alarm inputs. These inputs can be used e.g. forantenna or rack alarms. Depending on the rack and antenna configuration,the LIC has to mask out some alarm inputs.The operator can define a hexadecimal number of 3 Bytes for the AlarmMask. Each bit of the 3 Bytes represents an alarm input. To disable analarm input, set the appropriate bit to OFF (0), to enable an alarm input,set the bit to ON (1).This parameter is not supported by the BTS2000 because the BTS2000has no LIC alarm inputs.




101

100 LIC-Clock-Input (n)Recommended DefaultValue:

0 (input0)

Range: 0-1Range Semantics: 0 = input0, 1 = input1Modification State: -Short Description: Identifies the Abis link which provides the CCG's clock input.

This parameter is only for RBS900.OMC Object: BTCOMC AUI: CLKINP0, CLKINP1OMC GUI: LIC Data: Clocking InputBosch OMC Object: BTCBosch OMC AUI: LIC-fBosch OMC Comments: -Long Description: The Link Interface Concentrator (LIC) panel provides two E1 line

interfaces. This parameter selects one of both as clock source for theCCG.This parameter reflects the different rack configurations and theline&switching interfaces of the RBS900.This parameter is not supported by the other BTS types because theyhave only one rack and one line&switching interface.See also LIC-Position (n), LIC-Number (n), LIC-Input-Line A (n), LIC-Input-Line B (n), LIC-Rack (n)





101 LIC-Input-Line A (n)Recommended DefaultValue:

0

Range: 0-31 (BCE), 0-127 (BCF)Range Semantics: -Modification State: -Short Description: Identifies the Abis E1/T1 link which is connected to the A-input of the LIC

panel.This is the only LIC parameter that is used not only by RBS900 but allRBSs.

OMC Object: BTCOMC AUI: PCMPORTA0, PCMPORTA1OMC GUI: LIC Data: PCM Port ABosch OMC Object: BTCBosch OMC AUI: LIC-cBosch OMC Comments: -Long Description: For RBS900: This parameter identifies the Abis E1/T1 link which is

connected to the A-input of the LIC panel. The identification is doneaccording to the numbering in the BSC. In the BCE the identification isused as the identifier of the PPC which serves this E1/T1 line.The RBS900 supports up to two LIC panels for each rack. Note that thereare different configurations possible, because the RBS900 can have moreracks and does not have to use two LICs per rack. LIC-Input-Line A (0)identifies the line number of the Abis E1/T1 line connected to the first LICin the rack and LIC-Input-Line A (1) to the second LIC in the rack ifpresent. If a specific slot in the Abis shall be identified for signaling ortraffic purposes, this is done by specification of the E1/T1 line number andthe slot number. Via correlation of the E1/T1 line numbers the BTScalculates which LIC it has to access.For BTS2000: This parameter identifies all Abis E1/T1 links which areconnected to the BTS. The identification is done accordingly to thenumbering in the BSC. In the BCE the identification is the identifier of thePPC which represents this E1/T1 line.To the BTS2000 up to three Abis lines can be connected. Two are usedfor input and one as output for multidrop configurations. The operator candefine the two input lines only. LIC-Input-Line A(0) identifies the linenumber of the first Abis E1/T1 link and LIC-Input-Line A(1) of the secondAbis E1/T1 link connected to the BTS2000. If a specific slot in the Abisshall be identified for signaling or traffic purposes, this is done byspecification of the E1/T1 line number and the slot number.Parameters that define signaling and traffic slots are: 'Sign.-Slot BTC','Sign.-Slot RT', 'Traffic Slots RT'See also LIC-Clock-Input (n), LIC-Position (n), LIC-Number (n), LIC-Input-Line B (n), LIC-Rack (n)




103

102 LIC-Input-Line B (n)Recommended DefaultValue:

1

Range: 0-31 (BCE), 0-127 (BCF)Range Semantics: -Modification State: -Short Description: Identifies the Abis E1 link which is connected to the B-input of the LIC

panel.This parameter is only for RBS900.

OMC Object: BTCOMC AUI: PCMPORTB0, PCMPORTB1OMC GUI: LIC Data: PCM Port BBosch OMC Object: BTCBosch OMC AUI: LIC-dBosch OMC Comments: -Long Description: This parameter identifies the Abis E1 link which is connected to the B-input

of the LIC panel. The identification is done according to the numbering inthe BSC. In the BCE the identification is used as the identifier of the PPCwhich serves this E1 line.For further description see RBS900 part of the parameter LIC-Input-Line A(n).This parameter reflects the different rack configurations and theline&switching interfaces of the RBS900.This parameter is not supported by the other BTS types because theyhave only one rack and one line&switching interface.See also LIC-Clock-Input (n), LIC-Position (n), LIC-Number (n), LIC-Input-Line A (n), LIC-Rack (n)





103 LIC-Number (n)Recommended DefaultValue:

0

Range: 0-1Range Semantics: -Modification State: -Short Description: The LIC Number specifies the number of the LIC panel in a rack. The

parameters LIC-Rack and LIC-Number together identify a LIC panel of aRBS900.This parameter is only for RBS900.

OMC Object: BTCOMC AUI: LIC0, LIC1OMC GUI: LIC Data: Lic NumberBosch OMC Object: BTCBosch OMC AUI: LIC-bBosch OMC Comments: -Long Description: This parameter reflects the different rack configurations and the

line&switching interfaces of the RBS900.This parameter is not supported by the other BTS types because theyhave only one rack and one line&switching interface.See also LIC-Clock-Input (n), LIC-Position (n), LIC-Input-Line A (n), LIC-Input-Line B (n), LIC-Rack (n)




105

104 LIC-Position (n)Recommended DefaultValue:

0 (front)

Range: 0,1,255Range Semantics: 0 = front, 1 = end, 255 = middleModification State: -Short Description: Identifies the position of the LIC in a multidrop arrangement.

This parameter is only for RBS900.OMC Object: BTCOMC AUI: LICFEP0, LICFEP1OMC GUI: LIC Data: Front End PointBosch OMC Object: BTCBosch OMC AUI: LIC-eBosch OMC Comments: Range:FRT = 0, END = 1, MID = 255Long Description: This attribute is only used within the RBS900 to determine that switching of

the unused slots of the Abis link has to be performed in case of 'front' and'middle'. In a multidrop arrangement there are several LICs sequentiallyconnected. The LIC that is directly connected to the BSC is in the 'front'.The last LIC in the multidrop line is at the 'end'. Any LIC in between is inthe 'middle'.This parameter reflects the different rack configurations and theline&switching interfaces of the RBS900.This parameter is not supported by the other BTS types because theyhave only one rack and one line&switching interface.See also LIC-Clock-Input (n), LIC-Number (n), LIC-Input-Line A (n), LIC-Input-Line B (n), LIC-Rack (n)





105 LIC-Rack (n)Recommended DefaultValue:

0

Range: 0-7Range Semantics: -Modification State: -Short Description: The LIC-Rack specifies the number of the rack the LIC panel is contained

in. The parameters LIC-Rack and LIC-Number together identify a LICpanel of a RBS900. This parameter is only for RBS900.

OMC Object: BTCOMC AUI: RACK0, RACK1OMC GUI: LIC Data: Rack NumberBosch OMC Object: BTCBosch OMC AUI: LIC-aBosch OMC Comments: -Long Description: This parameter reflects the different rack configurations and the

line&switching interfaces of the RBS900.This parameter is not supported by the other BTS types because theyhave only one rack and one line&switching interface.See also LIC-Clock-Input (n), LIC-Position (n), LIC-Number (n), LIC-Input-Line A (n), LIC-Input-Line B (n)




107

106 Link Servicepr. SLCRecommended DefaultValue:

-

Range: 0-3Range Semantics: -Modification State: -Short Description: This parameter identifies one of four possible SLCs (Signal Link Control)

beyond STC for the LINK.BSC of type BCE only.

OMC Object: LINKOMC AUI: SLCDNOMC GUI: SLC Service Provider: SLC IdBosch OMC Object: LINKBosch OMC AUI: SLCPROV-bBosch OMC Comments: -Long Description: This parameter is part of the identification of the physical service provider

for the link. It identifies one of four possible SLCs (Signalling Link Control).See also 'Link Servicepr. STC'





107 Link Servicepr. STCRecommended DefaultValue:

-

Range: 0-1Range Semantics: -Modification State: -Short Description: This parameter identifies one of two possible STCs (Signal Terminal

Control) with its related SLCs for the link. The STC has a connection to theactive and standby CCMP (Common Channel Management Processor).BSC of type BCE only.

OMC Object: LINKOMC AUI: STCDNOMC GUI: SLC Service Provider: STC IdBosch OMC Object: LINKBosch OMC AUI: SLCPROV-aBosch OMC Comments: -Long Description: This parameter is part of the identification of the physical service provider

for the link. It identifies one of two possible STCs (Signalling TerminalControl) with its related SLCs for the link.See also 'Link Servicepr. SLC'




109

108 LINKfactor(0,n)Recommended DefaultValue:

0dB = 24

Range: 0-48Range Semantics: 0 = -24dB, 1 = -23dB, ..., 48 = +24dBModification State: LO/ULShort Description: This attribute defines a link factor regarding traffic load for the handover

target cell rankingOMC Object: ADJCELLOMC AUI: LINKFACTOMC GUI: Link FactorBosch OMC Object: NCELLBosch OMC AUI: CDESC-mBosch OMC Comments: Range:(-24)-24Long Description: This parameter is an absolute value settable by the user in weighting

different neighbor cells for the neighbor cell evaluation when handoverregarding traffic load is enabled.This value is used in the traffic load equation which determines the cellwith the highest Order(n) ranking. The highest Order(n) is the mostpreferable cell to which a handover is performed.The traffic load equation is as follows:Order(n) = PBGT(n) - HO_MARGIN(0,n) + LINKfactor(0,n) +FREEfactor_X(n)See also FREEfactor_X (X=1..5), FREElevel_X (X=1..4),EN_LOAD_REGARD





109 M1Recommended DefaultValue:

4

Range: 1-10Range Semantics: -Modification State: LO/ULShort Description: Step size for access control classes 0-9 to be barred in case of overload in

the BSS.OMC Object: BTSOMC AUI: BARSTEP0_9OMC GUI: Access Class Overload Control: Classes 0 to 9: Bar Step SizeBosch OMC Object: CELLBosch OMC AUI: OVERLOAD-bBosch OMC Comments: -Long Description: Barring is used to prevent MSs belonging to special access classes from

making access attempts (including emergency call attempts) orresponding to paging messages in the specified area. The use of thisfacility allows to recover from overload.The MS stores the access control class on its Subscriber Identity Module(SIM). If the access for a certain class is barred, MSs with that class mayonly try to get a connection in the neighbour cells.Automatic barring is done by the BSS in case of overload. Depending onthe severity of overload the BSS starts with barring access classes 0-9with random starting class and step size M1 (unbarring with step size M2).If classes 0-9 are barred and there is still an overload situation, the BSScontinues barring with access classes 10-15. The barring sequence isgiven in parameter 'Barring Sequence' and the step size in N1 (unbar: N2).The timer T17 (MAP-Timer) and T18 (MAP-Timer) are used for barringresp. unbarring. Automatic barring can be enabled/disabled with flagEN_ACC_BARRING.See also: EN_ACC_BARRING, Barring Sequence, M2, N1, N2, T17(MAP-Timer), T18 (MAP-Timer)The operator can bar manually special MS access classes with parameterAC_CN.




111

110 M2Recommended DefaultValue:

2

Range: 1-10Range Semantics: -Modification State: LO/ULShort Description: Step size for access control classes 0-9 to be unbarred in case of the

overload situation in the BSS is ceased.OMC Object: BTSOMC AUI: UNBARSTEP0_9OMC GUI: Access Class Overload Control: Classes 0 to 9: Unbar Step SizeBosch OMC Object: CELLBosch OMC AUI: OVERLOAD-cBosch OMC Comments: -Long Description: Barring is used to prevent MSs belonging to special access classes from

making access attempts (including emergency call attempts) orresponding to paging messages in the specified area. The use of thisfacility allows to recover from overload.The MS stores the access control class on its Subscriber Identity Module(SIM). If the access for a certain class is barred, MSs with that class mayonly try to get a connection in the neighbour cells.Automatic barring is done by the BSS in case of overload. Depending onthe severity of overload the BSS starts with barring access classes 0-9with random starting class and step size M1 (unbarring with step size M2).If classes 0-9 are barred and there is still an overload situation, the BSScontinues barring with access classes 10-15. The barring sequence isgiven in parameter 'Barring Sequence' and the step size in N1 (unbar: N2).The timer T17 (MAP-Timer) and T18 (MAP-Timer) are used for barringresp. unbarring. Automatic barring can be enabled/disabled with flagEN_ACC_BARRING.See also: EN_ACC_BARRING, Barring Sequence, M1, N1, N2, T17(MAP-Timer), T18 (MAP-Timer)The operator can bar manually special MS access classes with parameterAC_CN.





111 MA_ARFCNRecommended DefaultValue:

-

Range: 1-1024Range Semantics: GSM900: 1-124; GSM1800: 512-885Modification State: LOShort Description: Mobile Allocation Absolute RF Channel Numbers for frequency hoppingOMC Object: FHOMC AUI: ALLOCFREQOMC GUI: Mobile AllocationBosch OMC Object: FHSBosch OMC AUI: AFBosch OMC Comments: -Long Description: This parameter contains the list of all frequencies, which are assigned to a

Frequency Hopping system (FH).The frequency hopping algorithm determines the actual choice of thesefrequencies in a cyclic or quasi-random way and ensures that nofrequency collision may occur with other connected mobiles.Frequency allocation is matter of cellular network planning. All frequencyrelated attributes (CA_ARFCN, INIT_FREQ, BCCH_FREQ, MA_ARFCN)shall adhere to this planning.

Dependency: All frequencies shall occur in CA_ARFCN of container BTS.GSM 12.20 Class: frequencyHoppingSystemGSM 12.20 Attribute: mobileAllocation



113

112 MAX_RETRANSRecommended DefaultValue:

4 retransmission attempts = 2

Range: 0-3Range Semantics: 0: 1 retransmission attempt, 1: 2, 2: 4, 3: 7Modification State: LO/ULShort Description: After MAX_RETRANS random access attempts the MS shall reselect a

new cell.OMC Object: BTSOMC AUI: MAXRETRANOMC GUI: Max Number RetransmissionBosch OMC Object: CELLBosch OMC AUI: MAXRETBosch OMC Comments: -Long Description: When a MS tries to access a system it sends an access request on the

Random Access Channel (RACH). If no answer is receipt during a certaintime, e.g. because another MS had sent an access request at the sametime, the MS tries another access request after a random number oftimeslots (TDMA frames). The random number is less or equal to thevalue given by TX_INTEGER. MAX_RETRANS specifies the maximumallowed number of random access attempts to a cell. The MS is requiredto reselect a new cell, if a random access attempt to a cell is stillunsuccessful after the specified number of cell access repetitions.

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: maxNumberRetransmission




113 MCC (in LAI)Recommended DefaultValue:

-

Range: 0-999Range Semantics: -Modification State: LO/ULShort Description: The Mobile Country Code of this cell.OMC Object: BTSOMC AUI: LAIDMCCOMC GUI: Cell Global Identity: Location Area: MCCBosch OMC Object: CELLBosch OMC AUI: LAI-aBosch OMC Comments: -Long Description: Uniquely identifies the country of the current cell.

The Location Area Identification (LAI) consists of the concatenation ofMCC, MNC and LAC. MCC and MNC are fixed numbers assigned toidentify the country and the GSM PLMN in that country. The LAC identifiesa location area within the PLMN. It consists of one or more cells identifiedby CI.See also LAC (in LAI), MNC (in LAI), CI (in CGI)

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: cellGlobalIdentity.LocationAreaIdentity.MobileCountryCode



115

114 MCC_NC(n)Recommended DefaultValue:

-

Range: 0-999Range Semantics: -Modification State: LO/ULShort Description: The Mobile Country Code of Neighbour Cell n.

Only for Ericsson A interface.OMC Object: ADJCELLOMC AUI: LAIDMCCOMC GUI: Cell Global Identity: Location Area: MCCBosch OMC Object: NCELLBosch OMC AUI: CDESC-dBosch OMC Comments: -Long Description: Uniquely identifies the country of neighbour cell n.

The Location Area Identification (LAI) consists of the concatenation ofMCC, MNC and LAC. MCC and MNC are fixed numbers assigned toidentify the country and the GSM PLMN in that country. The LAC identifiesa location area within the PLMN. It consists of one or more cells identifiedby CI.For every radio cell in a GSM PLMN, a number of up to 32 neighbouringcells have to be specified to be monitored by every MS with a call inprogress. The MS takes signal strength measurements on the BCCHcarriers of these neighbour cells and reports them to the BSS. In the BSC,the measurement result reports of every MS are evaluated and form thebasis for handover decisions. In order to identify the neighbour cells, theMS decodes the Base Station Identity Code (BSIC) of every monitoredneighbour cell and includes this information together with information onthe respective BCCH carrier frequency in the measurement result reports.In Handover Required messages sent from the BSC to the MSC, thepreferred target cells for handover are identified by LAC (DMCS) resp. LAI(Ericsson) and CI. Therefore, in the BSC, the cell identification informationprovided by the MS has to be mapped onto the LAC/LAI and CI used toidentify radio cells in the PLMN.See also LAC_NC(n), MNC_NC(n), CI_NC(n)

Dependency: MCC_NC(n) is required to have the same value as parameter MCC (inLAI) of that neighbour cell.

GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: cellGlobalIdentity.LocationAreaIdentity.MobileCountryCode




115 Memory AvailabilityRecommended DefaultValue:

-

Range: 0-8388607Range Semantics: (Memory Availability * 8kBModification State: -Short Description: Available memory space for storing peripheral software images in the BCE

BSC of type BCE only.OMC Object: BSCOMC AUI: MEMAVAILOMC GUI: Memory AvailableBosch OMC Object: BSCBosch OMC AUI: MEMORY AVAILABLEBosch OMC Comments: -Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



117

116 MNC (in LAI)Recommended DefaultValue:

-

Range: 0-99Range Semantics: -Modification State: LO/ULShort Description: The Mobile Network Code of this cell.OMC Object: BTSOMC AUI: LAIDMNCOMC GUI: Cell Global Identity: Location Area: MNCBosch OMC Object: CELLBosch OMC AUI: LAI-bBosch OMC Comments: -Long Description: Uniquely identifies the PLMN of the current cell within the country.

The Location Area Identification (LAI) consists of the concatenation ofMCC, MNC and LAC. MCC and MNC are fixed numbers assigned toidentify the country and the GSM PLMN in that country. The LAC identifiesa location area within the PLMN. It consists of one or more cells identifiedby CI.See also LAC (in LAI), MCC (in LAI), CI (in CGI)

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: cellGlobalIdentity.LocationAreaIdentity.MobileNetworkCode




117 MNC_NC(n)Recommended DefaultValue:

-

Range: 0-99Range Semantics: -Modification State: LO/ULShort Description: The Mobile Network Code of Neighbour Cell n.

Only for Ericsson A interface.OMC Object: ADJCELLOMC AUI: LAIDMNCOMC GUI: Cell Global Identity: Location Area: MNCBosch OMC Object: NCELLBosch OMC AUI: CDESC-eBosch OMC Comments: -Long Description: Uniquely identifies the PLMN of neighbour cell n within the country.

The Location Area Identification (LAI) consists of the concatenation ofMCC, MNC and LAC. MCC and MNC are fixed numbers assigned toidentify the country and the GSM PLMN in that country. The LAC identifiesa location area within the PLMN. It consists of one or more cells identifiedby CI.For every radio cell in a GSM PLMN, a number of up to 32 neighbouringcells have to be specified to be monitored by every MS with a call inprogress. The MS takes signal strength measurements on the BCCHcarriers of these neighbour cells and reports them to the BSS. In the BSC,the measurement result reports of every MS are evaluated and form thebasis for handover decisions. In order to identify the neighbour cells, theMS decodes the Base Station Identity Code (BSIC) of every monitoredneighbour cell and includes this information together with information onthe respective BCCH carrier frequency in the measurement result reports.In Handover Required messages sent from the BSC to the MSC, thepreferred target cells for handover are identified by LAC (DMCS) resp. LAI(Ericsson) and CI. Therefore, in the BSC, the cell identification informationprovided by the MS has to be mapped onto the LAC/LAI and CI used toidentify radio cells in the PLMN.See also LAC_NC(n), MCC_NC(n), CI_NC(n)

Dependency: MNC_NC(n) is required to have the same value as parameter MNC (inLAI) of that neighbour cell.

GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: cellGlobalIdentity.LocationAreaIdentity.MobileNetworkCode



119

118 MS_DIST_MAXRecommended DefaultValue:

34.1 km = 31

Range: 0-31 (0 km - 34.1km)Range Semantics: multiples of 1.1kmModification State: LO/ULShort Description: Threshold for the maximum permitted distance between MS and current

BTS before handover is performed.OMC Object: HOCTRLOMC AUI: MSRANGEMXOMC GUI: Distance: MS Range MaximumBosch OMC Object: HOBosch OMC AUI: HOCDIST-aBosch OMC Comments: -Long Description: If the maximum distance is exceeded, a handover because of distance will

be performed. The maximum value for this parameter is set lower than thetheoretical maximum distance (In the field this theoretical maximumdistance cannot be reached, is overruled by other handover reasons orleads to too much calls lost).Formerly: MS_RANGE_MAXSee also A_DIST_HO, EN_DIST_HO

Dependency: -GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: hoThresholdDistParam




119 MS_TXPWR_MAXRecommended DefaultValue:

GSM900: 2, GSM1800: 0

Range: 0-19Range Semantics: Allowed range depends on frequency band: GSM900 (Range 2-19): [(43 -

2 * MS_TXPWR_MAX) dBm], GSM1800 (Range 0-15): [(30 - 2 *MS_TXPWR_MAX) dBm]

Modification State: LO/ULShort Description: Maximum TX power a MS is permitted to use on a dedicated control

channel or a traffic channel within the serving cell.OMC Object: HOCTRLOMC AUI: MSTXMAXTCHOMC GUI: MS Tx Power MaximumBosch OMC Object: HOBosch OMC AUI: HOCBosch OMC Comments: -Long Description: For power control this parameter and the power class of the MS

(depending on the Phase of the MS) determine the maximum power levelthat the BSC instructs the MS to use on a dedicated control channel or atraffic channel. This parameter is used for power control and handoverdecision in the BSC. It is not sent to the MS but influences the powercontrol commands for the MS.This parameter should be set to a value that is needed as maximumpower level in the cell, i.e. that allows the MS to communicate with the BTSat every place in the cell even under bad radio conditions.For handover control this parameter is used for the power budget criterion.The power budget (PBGT) is a relative measure of the MS link powerbudget on a potential new link to a neighbour cell with respect to thecurrent link in the serving cell. Basically, the MS should alwayscommunicate with or be handed over to the cell or BTS with the lowestpossible link power budget. In the BSC, the PBGT of a given MS iscalculated for every neighbour cell specified for the current serving cell.The calculation of the PBGT requires knowledge of the maximum allowedMS RF output powers MS_TXPWR_MAX on the dedicated channels of therespective neighbour cells and of the current serving cell that is given bythis parameter.See also EN_MS_PC, MS_TXPWR_MAX(n), MS_TXPWR_MAX_CCH,EN_PBGT_HO




121

120 MS_TXPWR_MAX(n)Recommended DefaultValue:

GSM900: 2, GSM1800: 0


2 * MS_TXPWR_MAX(n)) dBm], GSM1800 (Range 0-15): [(30 - 2 *MS_TXPWR_MAX(n)) dBm]

Modification State: LO/ULShort Description: Maximum TX power a MS is permitted to use on a dedicated control

channel or a traffic channel within the neighbour cell n.OMC Object: ADJCELLOMC AUI: MSTXMAXOMC GUI: MS Tx Power Maximum CellBosch OMC Object: NCELLBosch OMC AUI: CDESC-iBosch OMC Comments: -Long Description: For every radio cell in a GSM PLMN, a number of up to 32 neighbouring

cells have to be specified to be monitored by every MS with a call inprogress. The MS takes signal strength measurements on the BCCHcarriers of these neighbour cells and reports them to the BSS. In the BSC,the measurement result reports of every MS are evaluated and form thebasis for handover decisions.A basic radio criterion for handover decisions in the BSC is the powerbudget criterion. The power budget (PBGT) is a relative measure of theMS link power budget on a potential new link to a neighbour cell withrespect to the current link in the serving cell. Basically, the MS shouldalways communicate with or be handed over to the cell or BTS with thelowest possible link power budget. In the BSC, the PBGT of a given MS iscalculated for every neighbour cell specified for the current serving cell.The calculation of the PBGT requires knowledge of the maximum allowedMS RF output powers MS_TXPWR_MAX on the dedicated channels of therespective neighbour cells that is given by this parameter.See also MS_TXPWR_MAX, EN_PBGT_HO

Dependency: MS_TXPWR_MAX(n) is required to have the same value as parameterMS_TXPWR_MAX of the referenced neighbour cell.

GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: msTxPwrMaxCell




121 MS_TXPWR_MAX_CCHRecommended DefaultValue:

GSM900: 2, GSM1800: 0


2 * MS_TXPWR_MAX_CCH) dBm], GSM1800 (Range 0-15): [(30 - 2 *MS_TXPWR_MAX_CCH) dBm]

Modification State: LO/ULShort Description: Maximum transmit power level an MS may use in the cell when accessing

on the common control channel. This parameter is also used for the C1cell (re)selection criteria.

OMC Object: BTSOMC AUI: MSTXMAXCCHOMC GUI: MS Tx Power Maximum CCHBosch OMC Object: RADIOBosch OMC AUI: TXPWRCCHBosch OMC Comments: -Long Description: This defines the maximum power the MS is allowed to transmit when first

accessing a cell on the RACH (random access channel) and beforereceiving the first power command on a DCCH or TCH. The MS shall useeither the power level defined by this parameter, that is broadcast on theBCCH, or the maximum TXPWR of the MS as defined by its power class,whichever is the lower. The maximum transmit power may be reduced toavoid interference. The maximum power must be correlated to the BTSmaximum power to ensure good reception for uplink and downlink. Thisparameter should be set to a value that is needed as maximum powerlevel in the cell, i.e. that allows the MS to communicate with the BTS atevery place in the cell even under bad radio conditions.This parameter is also used to define together with other parameters theC1 path loss criterion (power budget - PBGT) for cell (re)selection.See also RXLEV_ACCESS_MIN, MS_TXPWR_MAX

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: msTxPwrMaxCCH



123

122 MULTIBAND_REPORTINGRecommended DefaultValue:

1 = normalReporting

Range: 1-4Range Semantics: 1=normalReporting, 2=reportStrongestCells, 3=reportTwoStrongestCells,

4=reportThreeStrongestCellsModification State: LO/ULShort Description: This attribute is related to network support of dual band operation (

GSM900 and GSM1800 ). It allows the operator to control themeasurement reporting done by the MS.BSC of type BCF only.

OMC Object: BTSOMC AUI: MULTIBREPOMC GUI: Multiband ReportingBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: For a multi band MS the number of cells, for each frequency band

supported, which shall be included in the measurement report is indicatedby the parameter, MULTIBAND_REPORTING. The meaning of differentvalues of the parameter is specified as follows:1 - Normal reporting of the six strongest cells, with known and allowedNCC part of BSIC, irrespective of the band used.2 - The MS shall report the strongest cell, with known and allowed NCCpart of BSIC, in each of the frequency bands in the BA list, excluding thefrequency band of the serving cell. The remaining positions in themeasurement report shall be used for reporting of cells in the band of theserving cell. If there are still remaining positions, these shall be used toreport the next strongest identified cells in the other bands irrespective ofthe band used.3 - The MS shall report the two strongest cells, with known and allowedNCC part of BSIC, in each of the frequency bands in the BA list, excludingthe frequency band of the serving cell. The remaining positions in themeasurement report shall be used for reporting of cells in the band of theserving cell. If there are still remaining positions, these shall be used toreport the next strongest identified cells in the other bands irrespective ofthe band used.4 - The MS shall report the three strongest cells, with known and allowedNCC part of BSIC, in each of the frequency bands in the BA list, excludingthe frequency band of the serving cell. The remaining positions in themeasurement report shall be used for reporting of cells in the band of theserving cell. If there are still remaining positions, these shall be used toreport the next strongest identified cells in the other bands irrespective ofthe band used.





123 n (N_TARGET_CELL)Recommended DefaultValue:

6

Range: 0-16Range Semantics: -Modification State: ULShort Description: The maximum number of preferred target cells which may be included in

the message HANDOVER REQUIRED sent from BSC to MSC.OMC Object: BSCOMC AUI: PREFCELLSOMC GUI: Number of Preferred CellsBosch OMC Object: BSCBosch OMC AUI: GENHORM-aBosch OMC Comments: -Long Description: Part of the information which is needed to generate the HANDOVER

REQUIRED message.This parameter should be set to a value not bigger than 6, because the MStakes only measurements of up to 6 of the best neighbour cells, i.e. theprobability for sufficient measurements results for more than 6 neighbourcells is low.

Dependency: This value is required to be not bigger than the corresponding value at theMSC. If this value is to big, calls may be dropped when a handover isattempted.

GSM 12.20 Class: bscGSM 12.20 Attribute: handoverReqParam



125

124 N1Recommended DefaultValue:

2

Range: 1-6Range Semantics: -Modification State: LO/ULShort Description: Step size for access control classes 10-15 to be barred in case of overload

in the BSS if access classes 0-9 are already barred.OMC Object: BTSOMC AUI: BARSTEP10_15OMC GUI: Access Class Overload Control: Classes 10 to 15: Bar Step SizeBosch OMC Object: CELLBosch OMC AUI: OVERLOAD-dBosch OMC Comments: -Long Description: Barring is used to prevent MSs belonging to special access classes from

making access attempts (including emergency call attempts) orresponding to paging messages in the specified area. The use of thisfacility allows to recover from overload.The MS stores the access control class on its Subscriber Identity Module(SIM). If the access for a certain class is barred, MSs with that class mayonly try to get a connection in the neighbour cells.Automatic barring is done by the BSS in case of overload. Depending onthe severity of overload the BSS starts with barring access classes 0-9with random starting class and step size M1 (unbarring with step size M2).If classes 0-9 are barred and there is still an overload situation, the BSScontinues barring with access classes 10-15. The barring sequence isgiven in parameter 'Barring Sequence' and the step size in N1 (unbar: N2).The timer T17 (MAP-Timer) and T18 (MAP-Timer) are used for barringresp. unbarring. Automatic barring can be enabled/disabled with flagEN_ACC_BARRING.See also: EN_ACC_BARRING, Barring Sequence, M1, M2, N2, T17(MAP-Timer), T18 (MAP-Timer)The operator can bar manually special MS access classes with parameterAC_CN.





125 N2Recommended DefaultValue:

1

Range: 1-6Range Semantics: -Modification State: LO/ULShort Description: Step size for access control classes 10-15 to be unbarred in case of the

overload situation in the BSS is ceased.OMC Object: BTSOMC AUI: UNBARSTEP10_15OMC GUI: Access Class Overload Control: Classes 10 to 15: Unbar Step SizeBosch OMC Object: CELLBosch OMC AUI: OVERLOAD-eBosch OMC Comments: -Long Description: Barring is used to prevent MSs belonging to special access classes from

making access attempts (including emergency call attempts) orresponding to paging messages in the specified area. The use of thisfacility allows to recover from overload.The MS stores the access control class on its Subscriber Identity Module(SIM). If the access for a certain class is barred, MSs with that class mayonly try to get a connection in the neighbour cells.Automatic barring is done by the BSS in case of overload. Depending onthe severity of overload the BSS starts with barring access classes 0-9with random starting class and step size M1 (unbarring with step size M2).If classes 0-9 are barred and there is still an overload situation, the BSScontinues barring with access classes 10-15. The barring sequence isgiven in parameter 'Barring Sequence' and the step size in N1 (unbar: N2).The timer T17 (MAP-Timer) and T18 (MAP-Timer) are used for barringresp. unbarring. Automatic barring can be enabled/disabled with flagEN_ACC_BARRING.See also: EN_ACC_BARRING, Barring Sequence, M1, M2, N1, T17(MAP-Timer), T18 (MAP-Timer)The operator can bar manually special MS access classes with parameterAC_CN.




127

126 NCC (in BSIC)Recommended DefaultValue:

-

Range: 0-7Range Semantics: -Modification State: LOShort Description: The Network Colour Code is part of the BSIC. The BSIC is a local colour

code that allows a MS to distinguish between different neighbouring basestations.

OMC Object: BTSOMC AUI: BSIDNCCOMC GUI: BS Identity Code: NCCBosch OMC Object: CELLBosch OMC AUI: BSIC-aBosch OMC Comments: -Long Description: The Base Station Identity Code (BSIC) consists of the Network Colour

Code (NCC) and the Base Station Colour Code (BCC).The BSIC is a local colour code that allows a MS to distinguish betweendifferent neighbouring base stations. The BSIC is broadcast on thesynchronisation channel SCH. The MS uses the BSIC in the following way:1. In idle mode the MS shall attempt to check the BSIC for each of the 6strongest non-serving cell BCCH carriers at least every 30 seconds, toconfirm that it is monitoring the same cell. If a change of BSIC is detectedthen the carrier shall be treated as a new carrier and the BCCH dataredetermined.2. In connected mode the MS shall demodulate the SCH on the BCCHcarrier of each surrounding cell and decode the BSIC as often as possible,and as a minimum at least once every 10 seconds.The BSIC shall only be changed on request of cellular network planningSee also: BCC (in BSIC), BCC_NC(n), NCC_NC(n), PLMN_PERMITTED,TSC

Dependency: If NCC is changed it shall be changed also in PLMN_PERMITTED.GSM 12.20 Class: btsGSM 12.20 Attribute: bsIdentityCode.NetworkColourCode




127 NCC_NC(n)Recommended DefaultValue:

-

Range: 0-7Range Semantics: -Modification State: LO/ULShort Description: The Network Colour Code of Neighbour Cell n (NCC_NC) is part of the

BSIC_NC. The BSIC_NC is a local colour code that allows a MS todistinguish between different neighbouring base stations.

OMC Object: ADJCELLOMC AUI: BSIDNCCOMC GUI: BS Identity Code: NCCBosch OMC Object: NCELLBosch OMC AUI: CDESC-bBosch OMC Comments: -Long Description: The Base Station Identity Code of a neighbour cell (BSIC_NC) consists of

the Network Colour Code (NCC_NC) and the Base Station Colour Code(BCC_NC) of that neighbour cell.The BSIC is a local colour code that allows a MS to distinguish betweendifferent neighbouring base stations. The BSIC is broadcast on thesynchronisation channel SCH. The MS uses the BSIC in the following way:1. In idle mode the MS shall attempt to check the BSIC for each of the 6strongest non-serving cell BCCH carriers at least every 30 seconds, toconfirm that it is monitoring the same cell. If a change of BSIC is detectedthen the carrier shall be treated as a new carrier and the BCCH dataredetermined.2. In connected mode the MS shall demodulate the SCH on the BCCHcarrier of each surrounding cell and decode the BSIC as often as possible,and as a minimum at least once every 10 seconds.The BSIC shall only be changed on request of cellular network planning.See also: BCC (in BSIC), NCC (in BSIC), BCC_NC(n),PLMN_PERMITTED, TSC

Dependency: NCC_NC(n) is required to have the same value as parameter NCC (inBSIC) of that neighbour cell.

GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: bsIdentityCode.NetworkColourCode



129

128 NI_BSCRecommended DefaultValue:

2

Range: 0-3Range Semantics: 0 = international network, 1 = spare, 2 = national network, 3 = reserved

national useModification State: -Short Description: The Network Indicator specifies the type of the CCS7 network to which the

BSC belongs.OMC Object: OPCOMC AUI: NIOMC GUI: Network IndicatorBosch OMC Object: OPCBosch OMC AUI: NETINDBosch OMC Comments: Range:INT = 0, SPA = 1, NAT = 2, RES = 3Long Description: A point code in the CCS7 network consists of the Network Indicator (NI)

and the Signalling Point Code (SPC). The point code is unique for theCCS7 network.The parameter NI_BSC specifies the type of CCS7 network to which theBSC belongs. The parameter SPC_BSC specifies the Signalling PointCode (SPC) of the BSC in the CCS7 network.See also NI_MSC, SPC_BSC, SPC_MSC

Dependency: Shall be the same as NI_MSCGSM 12.20 Class: -GSM 12.20 Attribute: -




129 NI_MSCRecommended DefaultValue:

2

Range: 0-3Range Semantics: 0 = international network, 1 = spare, 2 = national network, 3 = reserved

national useModification State: -Short Description: The Network Indicator specifies the type of the CCS7 network to which the

MSC belongs.OMC Object: LSETOMC AUI: NIOMC GUI: Network IndicatorBosch OMC Object: LSETBosch OMC AUI: NETINDBosch OMC Comments: Range:INT = 0, SPA = 1, NAT = 2, RES = 3Long Description: A point code in the CCS7 network consists of the Network Indicator (NI)

and the Signalling Point Code (SPC). The point code is unique for theCCS7 network.The parameter NI_MSC specifies the type of CCS7 network to which theMSC belongs. The parameter SPC_MSC specifies the Signalling PointCode (SPC) of the MSC in the CCS7 network.See also NI_BSC, SPC_BSC, SPC_MSC

Dependency: Shall correspond to the value in the MSC and to parameter NI_BSCGSM 12.20 Class: -GSM 12.20 Attribute: -



131

130 No. of CCCHRecommended DefaultValue:

-

Range: 0-4Range Semantics: -Modification State: -Short Description: Number of Common Control Channels (channel type vi) provided by the

BTSOMC Object: BTSOMC AUI: NOCCCHOMC GUI: Number of CCCHBosch OMC Object: BTSBosch OMC AUI: NRCCCH.NUMBER_OF_CCCHBosch OMC Comments: -Long Description: This is a read-only parameter which can only be set implicitly by

appropriate setting of parameter CH_TYPE during creation of object CHN.Formerly: NO_CCCHThis parameter gives the number of configured CCCHs. This number canbe different to the number of active CCCHs. Thus, this parameter is notequal to the parameter BS_CC_CHANS defined by GSM.See also CCCH_COMB_WITH_SDCCH, CH_TYPE

Dependency: channelTypeGSM 12.20 Class: -GSM 12.20 Attribute: -




131 NS_TRXRecommended DefaultValue:

True

Range: BooleanRange Semantics: -Modification State: LO/ULShort Description: This attribute indicates whether this RT will be active during the

emergency for minimum configuration. Only few RTs can be active for ashort time due to the limited capacity of the battery.

OMC Object: RTOMC AUI: EMERGENCYRTOMC GUI: Emergency RTBosch OMC Object: RTBosch OMC AUI: EMPWRTRXBosch OMC Comments: -Long Description: NS_TRX: "Not-Strom Transceiver"

See also: T_MKDependency: It is required, that the RT carrying the BCCH-channel and at least one RT

with a channel of type SDCCH/* (GSM channel combination: v, v+, vii, vii+)always has to be defined as emergency-RT.




133

132 P_CON_ACKRecommended DefaultValue:

1920 msec = 2

Range: 0-31 (0 msec - 29760 msec)Range Semantics: multiples of 2*480 msec for TCH resp. 2*470.77 msec for SDCCH

channels (2 SACCH periods)Modification State: LO/ULShort Description: Power Control Acknowledge timeOMC Object: POWEROMC AUI: ACKTIMEPWRCTRLOMC GUI: Power Control Acknowledge TimeBosch OMC Object: PCBosch OMC AUI: ACKTPCBosch OMC Comments: -Long Description: After a power command is sent to the MS the BSC waits for the

confirmation. This waiting time is monitored by the time P_CON_ACK. IfP_CON_ACK elapses before a confirmation of the power command isreceived, the power control is resumed. If the power command wassuccessful the timer P_CON_INTERVAL is started on receipt of theconfirmation. The next power command is issued at the earliest afterexpiration of P_CON_INTERVAL.See also EN_MS_PC, P_CON_INTERVAL

Dependency: -GSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: powerControlInterval




133 P_CON_INTERVALRecommended DefaultValue:

960 msec = 1

Range: 0-31 (0 msec - 29760 msec)Range Semantics: multiples of 2*480 msec for TCH resp. 2*470,77 msec for SDCCH

channels (2 * SACCH period)Modification State: LO/ULShort Description: Minimum interval between successive modification of the radio frequency

power levelOMC Object: POWEROMC AUI: MINTIMBETPWRCTRLOMC GUI: Power Control IntervalBosch OMC Object: PCBosch OMC AUI: PCINTBosch OMC Comments: -Long Description: After a power command is sent to the MS the BSC waits for the

confirmation. This waiting time is monitored by the time P_CON_ACK. IfP_CON_ACK elapses before a confirmation of the power command isreceived, the power control is resumed. If the power command wassuccessful the timer P_CON_INTERVAL is started on receipt of theconfirmation. The next power command is issued at the earliest afterexpiration of P_CON_INTERVAL.When configuring P_CON_INTERVAL the parameter A_LEV_PC shouldbe considered to ensure an averaged measurement value that reflects thesignal strength after power control.See also EN_MS_PC, P_CON_ACK, A_LEV_PC

Dependency: -GSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: powerControlInterval



135

134 PENALTY_TIMERecommended DefaultValue:

31

Range: 0-31Range Semantics: 0-30: (PENALTY_TIME + 1) * 20 seconds, 31: special caseModification State: LO/ULShort Description: The PENALTY_TIME indicates the time for which the

TEMPORARY_OFFSET shall be applied to a cell in idle mode (i.e. thetime a cell should be put at a disadvantage for cell reselection inhierarchical cells).

OMC Object: BTSOMC AUI: PENTIMEOMC GUI: Cell Reselection: Penalty TimeBosch OMC Object: CELLBosch OMC AUI: C2CRIT-dBosch OMC Comments: -Long Description: The PENALTY_TIME indicates the time a cell should be put at a

disadvantage. The cell reselection criteria is reduced byTEMPORARY_OFFSET during this time. Typically a cell of a lower layerhas a high and a cell of a upper layer a low PENALTY_TIME. For a cellwith PENALTY_TIME set to 31 the reselection criteria is reduced byCELL_RES_OFFSET.See also CELL_RESELECT_PARAM_IND, CELL_RES_OFFSET,TEMPORARY_OFFSET. These parameters specify the criteria for cellreselection according to the C2 criteria for GSM phase 2 MS.





135 PG-TypeRecommended DefaultValue:

-

Range: 0-3Range Semantics: 0 = ppc, 1 = iop, 2 = d2m, 3 = roiModification State: -Short Description: Type of Peripheral GroupOMC Object: PGOMC AUI: PGTYPEOMC GUI: PG TypeBosch OMC Object: PGBosch OMC AUI: PGTYPEBosch OMC Comments: Range:PPC = 0, IOP = 1, D2M = 2, ROI = 3Long Description: At the B-interface, PG-PPC provides the interface to the BTS (Abis/OB),

PG-PPC contains the following objects: BCON, EXTC-PPCX, EXTC-CEP,EXTC-PPPAt the M-interface, PG-D2M provides the interface to the STF/TCE, PG-D2M contains the following objects: MCON, EXTC-D2MX.The PG-IOP provides the CCSS7 controlling function.The PG-ROI provides the interface to the OMC. Therefore this object ispredefined in BSS.The BSC of type BCE supports all 4 PG types; the BCF supports PG-PPCand PG-D2M, only.




137

136 PLMN_PERMITTEDRecommended DefaultValue:

-

Range: 0-255Range Semantics: -Modification State: ULShort Description: PLMN_PERMITTED is the Public Land Mobile Network permitted flag. It

indicates the network colour codes (NCC) of the networks that the MS canmonitor.

OMC Object: BSCOMC AUI: PLMNOMC GUI: PLMN PermittedBosch OMC Object: BSCBosch OMC AUI: PLMNPERMBosch OMC Comments: Range:0-0xff, Bit0 = PLMN0, ..., Bit7 = PLMN7Long Description: The purpose of PLMN_PERMITTED is to provide a definition of the

allowed NCCs on the BCCH carriers to be monitored by the MSs in the celland report measurement results to the network. Only networks aremonitored which have a roaming agreement with the serving network.In the GSM standards this attribute is referred to as 'NCC permitted'.See also BCC (in BSIC), NCC (in BSIC)

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: plmnPermitted




137 PMC Allocation (EXTC)Recommended DefaultValue:

-

Range: 1,3,4..31Range Semantics: -Modification State: -Short Description: The physical assignment of an extension card (D2MX or PPCX) to a PMC,

which connects the extension card to the BSS Switching Unit (BSU).BSC of type BCE only.

OMC Object: EXTCOMC AUI: PMCIDOMC GUI: PMC AllocationBosch OMC Object: EXTCBosch OMC AUI: PMCIDBosch OMC Comments: -Long Description: This parameter contains the assignment between EXTC instances of type

PPCX or D2MX and the associated PMC links inside the BCE. PMCnumber 0 and 2 are occupied by the two BSS Central Controller.

Dependency: The assigned values shall be unique for all PGs and EXTCs in one BCE.GSM 12.20 Class: -GSM 12.20 Attribute: -



139

138 PMC Allocation (PG)Recommended DefaultValue:

-

Range: 1,3,4..31Range Semantics: -Modification State: -Short Description: The physical assignment of a PG to a PMC, which connects the PG to the

BSS Switching Unit (BSU).BSC of type BCE only.

OMC Object: PGOMC AUI: PMCIDOMC GUI: PMC AllocationBosch OMC Object: PGBosch OMC AUI: PMCIDBosch OMC Comments: -Long Description: This parameter contains the assignment between PG instances of type

PPC, IOP, D2M, and ROI and the associated PMC links inside the BCE.PMC number 0 and 2 are occupied by the two BSS Central Controller.Only one PMC may be assigned.

Dependency: The assigned values shall be unique for all PGs and EXTCs in one BCE.GSM 12.20 Class: -GSM 12.20 Attribute: -




139 POW_INCR_STEP_SIZERecommended DefaultValue:

6dB = 2

Range: 0-2Range Semantics: 0 = 2dB, 1 = 4dB, 2 = 6dBModification State: LO/ULShort Description: Step size used when increasing the MS and BTS transmit power by

dynamic power controlOMC Object: POWEROMC AUI: PWRINCRSTEPOMC GUI: MS Tx Power IncreaseBosch OMC Object: PCBosch OMC AUI: PWRINCBosch OMC Comments: -Long Description: Specifies the power increment step size for both MS and BTS. Power is

normally increased in steps of the specified value when power controldecides to increase power, i.e. when the averaged received power levelfalls below L_RXLEV_XX_P. In case of rapid level changes the powercontrol process uses a variable step size (dynamic power control).POW_INCR_STEP_SIZE should be chosen bigger thanPOW_RED_STEP_SIZE in order to assure a secure communication and asufficiently high stability of the PC processes.See also POW_RED_STEP_SIZE, EN_MS_PC, EN_BS_PC,L_RXLEV_XX_P where XX stands for UL or DL

Dependency: POW_INCR_STEP_SIZE > POW_RED_STEP_SIZEGSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: powerIncrStepSize



141

140 POW_RED_STEP_SIZERecommended DefaultValue:

4dB = 1

Range: 0-1Range Semantics: 0 = 2dB, 1 = 4dBModification State: LO/ULShort Description: Step size used when reducing the MS and BTS transmit power by dynamic

power controlOMC Object: POWEROMC AUI: PWRREDSTEPOMC GUI: MS Tx Power ReductionBosch OMC Object: PCBosch OMC AUI: PWRREDBosch OMC Comments: -Long Description: Specifies the power reduction step size for both MS and BTS. Power is

reduced in steps of the specified value when power control decides toreduce power, i.e. when the averaged received power level exceedsU_RXLEV_XX_P.POW_RED_STEP_SIZE should be chosen smaller thanPOW_INCR_STEP_SIZE in order to assure a secure communication anda sufficiently high stability of the PC processes.See also POW_INCR_STEP_SIZE, EN_MS_PC, EN_BS_PC,RXLEV_XX_IH and U_RXLEV_XX_P where XX stands for UL or DL

Dependency: POW_RED_STEP_SIZE < POW_INCR_STEP_SIZEGSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: powerRedStepSize




141 PTA_HO(n,0)Recommended DefaultValue:

0

Range: 0-63Range Semantics: Unit: 0.55 kmModification State: LO/ULShort Description: Predicted Timing Advance value is used in a handover command

message for a MS from neighbour cell 'n' into the serving cell '0' in case ofSYNC_NC is 'pre-synchronised'.

OMC Object: ADJCELLOMC AUI: TIMEADVOMC GUI: Predict Time AdvanceBosch OMC Object: NCELLBosch OMC AUI: CDESC-nBosch OMC Comments: -Long Description: The synchronisation of a handover concerns the timing advance which has

to be considered in intercell handovers.If the synchronisation is set to pre-synchronised (see SYNC_NC), thisparameter specifies the predicted timing advance that is given in thehandover command message.This parameter is unique for the relation between a cell and a neighbourcell.See also SYNC_NC(n,0)

Dependency: Depends on RF cell planning.Only applicable if parameter SYNC_NC(n,0) of same cell has the value"pre-synchronised(2)" for the same neighbour cell.




143

142 Q_THRESHOLD_VALRecommended DefaultValue:

90%

Range: 0-100Range Semantics: Unit: percentModification State: LO/ULShort Description: Threshold in percentage of max. queue entriesOMC Object: BTSOMC AUI: QUEUETHRESHOMC GUI: Queueing: Threshold Queue EntriesBosch OMC Object: BTSBosch OMC AUI: QUEUEM-bBosch OMC Comments: -Long Description: TCH assignment and handover requests may be queued in the BSS. The

queuing is guarded by the timer T11 (MAP-Timer) and T_qho (MAP-Timer), respectively. For both, assignment and handover the same queueis used. The parameter TOTAL_NUM_Q_PLACE_AVAIL defines thelength of this queue. The parameter Q_THRESHOLD_VAL defines athreshold in percentage of max. queue entries. The crossing of thisthreshold is counted for performance measurements.See also T11 (MAP-Timer), T_qho (MAP-Timer),TOTAL_NUM_Q_PLACE_AVAIL





143 RACH_BUSY_THRESRecommended DefaultValue:

GSM900: 8 (-102 dBm); GSM1800: 10 (-100 dBm)

Range: 0-63Range Semantics: -110 dBm to > -48dBmModification State: LO/ULShort Description: The RACH BUSY count signal level Threshold is used to control the

detection of MS access attempts on the RACH. This is required for loadmeasurement and overload detection on the RACH.

OMC Object: BTSOMC AUI: RACHBUSYTHOMC GUI: RACH Busy ThresholdBosch OMC Object: BTSBosch OMC AUI: BSYCRACHBosch OMC Comments: -Long Description: Determines the threshold of the RACH receive level in the BTS. The level

of each RACH timeslot is evaluated. All the RACH timeslots that are abovethe defined level are used for the load measurements, and are forwardedto the BSC.See also RACH_MEAS_PERIOD, CCCH_LOAD_IND_PERIOD,EN_CCCH_LOAD_IND

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: rACHBusyThreshold



145

144 RACH_MEAS_PERIODRecommended DefaultValue:

240 sec = 255

Range: 1-255Range Semantics: Unit: 4 * 51 multiframes = 941.5 msecModification State: LO/ULShort Description: Used for ascertainment whether the RACH timeslot can be assumed as

busy or notOMC Object: BTSOMC AUI: RACHBUSYSLOTOMC GUI: RACH Load Averaging SlotsBosch OMC Object: BTSBosch OMC AUI: BSYCRPERBosch OMC Comments: -Long Description: This parameter specifies the period of RACH measurements. It is used to

calculate the total number of RACH bursts for which a measurement isperformed and compared to RACH_BUSY_THRES.The result is reported to the BSC in the intervalCCCH_LOAD_IND_PERIOD. If the value of RACH_MEAS_PERIOD ischosen smaller than the value of CCCH_LOAD_IND_PERIOD, nomeasurement values are recorded.

Dependency: RACH_MEAS_PERIOD <= CCCH_LOAD_IND_PERIODGSM 12.20 Class: btsGSM 12.20 Attribute: rACHLoadAveragingSlots




145 Radio-/Terr. Link Asc.Recommended DefaultValue:

-

Range: StructureRange Semantics: Line number: 0 - 31 (BCE), 0 - 127 (BCF); Slot number: 1 - 31 (E1), 1 - 24

(T1); Subslot number: 1 - 4Modification State: -Short Description: Associates the radio time slot (channel) to a terrestrial channel on the Abis

E1/T1 interface. The radio slot will be mapped onto a 16 kbit subslotidentified by this parameter.

OMC Object: CHNOMC AUI: PCM, SLOT, SUBSLOT0OMC GUI: ABIS TCH Slot InfoBosch OMC Object: CHNBosch OMC AUI: ATCHSLI-a-b-c-dBosch OMC Comments: -Long Description: This is only required in case of creating a traffic channel

(CH_TYPE=TCHFull).Dependency: The line number shall correspond to the value of parameter 'LIC-Input-Line

A (n)' of object BTCGSM 12.20 Class: -GSM 12.20 Attribute: -



147

146 RADIO_LINK_TIMEOUT(T100)


11520 msec = 6

Range: 1-16Range Semantics: multiples of 4*480 msec for TCH resp. 4*470.77 msec for SDCCH

channels (4 SACCH periods)Modification State: LO/ULShort Description: Timeout before the MS is disconnected from a call, in case of repeated

failures to decode the SACCH messages. Corresponds to T100OMC Object: BTSOMC AUI: RADIOLKTOOMC GUI: Radio Link: TimeoutBosch OMC Object: RADIOBosch OMC AUI: RLTOBosch OMC Comments: -Long Description: During each call, the radiolink (Um) is monitored for successful message

decoding on the SACCH. If too many errors occur for the duration of theradiolink timeout, the call is either re-established or released in a definedmatter.If a single SACCH block could not be decoded a timer (initialised withRADIO_LINK_TIMEOUT) is decremented by 1, if it could be decoded it isincremented by 2 not exceeding the threshold given inRADIO_LINK_TIMEOUT. If the timer gets to 0 the radio path is cut off.The radiolink timeout becomes important only if neither handover norpower control can improve the RX/TX quality for this call.See also THRES_PC_RLF

Dependency: RADIO_LINK_TIMEOUT > THRES_PC_RLFGSM 12.20 Class: btsGSM 12.20 Attribute: radioLinkTimeout




147 RBS-TypeRecommended DefaultValue:

-

Range: 0-2,4Range Semantics: 0:RBS900, 1:BTS2000, 2:BTS2000/2C, 4:BTS2000(P)Modification State: -Short Description: Type of the RBSOMC Object: BTSOMC AUI: RBSTYPEOMC GUI: RBS TypeBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: This OMC-only parameter is used in the OMC to distinguish between

different RBS types. For example the operator is presented with the ARUcreation screen for a BTS of type RBS900, only. The attribute has to beset by the operator during creation of object BTS.With the BTC object creation the information about the actual RBS type isuploaded from the BTS via Abis-interface parameter RBS_Capability andOA-interface parameter BtsHardware of object BTC. The value range ofBtsHardware is: unknown(0), RBS900(1), RBS918(2), RBS918 withMRIF(3), Cube(4). The value 'unknown' can only occur during upgradefrom a previous release to NR8.0.If the value of BtsHardware is not 'unknown' and this value does not matchthe value of RBS-Type, an OMC system alarm is created.Mapping between the two attributes RBS-Type -> BtsHardware: RBS900 -> RBS900, BTS2000 -> RBS918 with MRIF, BTS2000(P) -> RBS918,BTS2000/2C -> Cube

Dependency: There is a dependency with the OA-interface attribute BtsHardware of theobject BTC. Refer to Long Description.




149

148 RERecommended DefaultValue:

False

Range: BooleanRange Semantics: False: disable feature, True: enable featureModification State: LO/ULShort Description: Indicates whether call recovery (re-establishment) is allowed in the cellOMC Object: BTSOMC AUI: CALLREESTBOMC GUI: Call Reestablishment AllowedBosch OMC Object: CELLBosch OMC AUI: CALLREEBosch OMC Comments: -Long Description: If this parameter is true, the network can attempt to re-establish a call after

a lower layer failure. This will only work if the layer 3 connection is stillavailable.Call Reestablishment can be initiated by the MS after loss of a radioconnection. The MS selects a new cell which allows call reestablishmentand does an access attempt with reason call reestablishment. There isonly a short time available for this procedure, because the MSC stores thecontext of a connection only for a short time after connection break.This flag is transmitted on the BCCH.

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: callReestablishmentAllowed




149 RT Rack Id.Recommended DefaultValue:

0

Range: 0-7Range Semantics: -Modification State: -Short Description: The rack number in which the RT is installed. Only for RBS900 this may

have another value as 0.OMC Object: RTOMC AUI: RACKNOOMC GUI: Location: Rack No.Bosch OMC Object: RTBosch OMC AUI: RTLOC-aBosch OMC Comments: -Long Description: See also: RT Shelf Id., Backup CapabilityDependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



151

150 RT Shelf Id.Recommended DefaultValue:

-

Range: 0-11Range Semantics: -Modification State: -Short Description: The hardware identification of the installed RT. To be interpreted

depending on the RBS type.OMC Object: RTOMC AUI: SHELFNOOMC GUI: Location: Shelf No.Bosch OMC Object: RTBosch OMC AUI: RTLOC-bBosch OMC Comments: -Long Description: See also: RT Rack Id., Backup CapabilityDependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -




151 RXLEV_ACCESS_MINRecommended DefaultValue:

GSM900: 8; GSM1800: 10

Range: 0-63Range Semantics: -110 + RXLEV_ACCESS_MIN dBm (0 = less than -110 dBm, 63 = greater

than -48 dBm)Modification State: LO/ULShort Description: The minimum power level an MS has to receive before it is allowed to

access the cell for (re-)selection.OMC Object: BTSOMC AUI: RXLEVACCOMC GUI: Rx Level Access MinimumBosch OMC Object: RADIOBosch OMC AUI: RXLEVBosch OMC Comments: -Long Description: This parameter defines the minimum received signal level at the MS

required for access to the system. It is used together with otherparameters to define the path loss criterion C1 for cell (re)selection (andC2 re-selection criterion).RXLEV_ACCESS_MIN is a part of the message System Information Type3. This message is regularly broadcast on the BCCH by the network to allmobiles within the cell.Setting it to a high value means, that only those MSs are allowed to makean access attempt to the cell which are already in a location, where thereception of the Base Station is very good. This should result in anincreased quality of the connection, but also in a decrease of the area ofservice availability. RXLEV_ACCESS_MIN shall be harmonised at leastwith L_RXLEV_XX_H and RXLEV_MIN(n). It may not be smaller than thelowest level in the handover process because of immediate handover afterlocation update of any MS in that cell.See also MS_TXPWR_MAX_CCH, L_RXLEV_DL_H, RXLEV_MIN(n)

Dependency: RXLEV_ACCESS_MIN > L_RXLEV_DL_HRXLEV_ACCESS_MIN >= RXLEV_MIN(for this cell) in all NCs

GSM 12.20 Class: btsGSM 12.20 Attribute: rxLevAccessMin



153

152 RXLEV_DL_IHRecommended DefaultValue:

GSM900: 25; GSM1800: 27

Range: 0-63Range Semantics: -110 + RXLEV_DL_IH dBm (0 = less than -110 dBm, 63 = greater than -48

dBm)Modification State: LO/ULShort Description: Signal level threshold on downlink for intracell (interference) handoverOMC Object: HOCTRLOMC AUI: RXLEVDLIHOMC GUI: Signal Strength: Downlink LimitBosch OMC Object: HOBosch OMC AUI: HOCSS-eBosch OMC Comments: -Long Description: If the averaged measurement value RXLEV_DL is greater than the

threshold RXLEV_DL_IH and the averaged measurement valueRXQUAL_DL is worse than the threshold L_RXQUAL_DL_H, an intracellhandover is initiated. For this intracell handover it is not necessary that theadjusted transmission power for the downlink has already reached themaximum.See also L_RXQUAL_DL_H, EN_INTRA_HO, L_RXLEV_DL_P,L_RXLEV_DL_H

Dependency: RXLEV_DL_IH > L_RXLEV_DL_HGSM 12.20 Class: -GSM 12.20 Attribute: -




153 RXLEV_MIN(n)Recommended DefaultValue:

-96dBm = 14

Range: 0-63Range Semantics: -110 + RXLEV_MIN(n) dBm (0 = less than -110 dBm, 63 = greater than -

48 dBm)Modification State: LO/ULShort Description: The minimum signal level that has to be received by an MS to be allowed

to handover to that cell.OMC Object: ADJCELLOMC AUI: RXMINOMC GUI: MS Rx Level Minimum CellBosch OMC Object: NCELLBosch OMC AUI: CDESC-hBosch OMC Comments: -Long Description: RXLEV_MIN(n) defines the minimum received BCCH level which must be

achieved for a respective neighbouring cell 'n' before the MS is allowed tohandover to this particular cell.The selection of proper values for RXLEV_MIN depends on cell sizes, celllayouts, propagation conditions and the interference situation in the cells,and is matter of cellular network planning.See also L_RXLEV_DL_H, RXLEV_ACCESS_MIN,UMBRELLA_MICRO_HYST

Dependency: RXLEV_MIN(n) for a neighbour cell n should have the same value in allcells referencing this neighbour cell.RXLEV_MIN(for this cell) in all NCs > L_RXLEV_DL_HRXLEV_MIN(for this cell) in all NCs <= RXLEV_ACCESS_MIN

GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: rxLevMinCell



155

154 RXLEV_UL_IHRecommended DefaultValue:

25

Range: 0-63Range Semantics: -110 + RXLEV_UL_IH dBm (0 = less than -110 dBm, 63 = greater than -48

dBm)Modification State: LO/ULShort Description: Signal level threshold on uplink for intracell (interference) handover.OMC Object: HOCTRLOMC AUI: RXLEVULIHOMC GUI: Signal Strength: Uplink LimitBosch OMC Object: HOBosch OMC AUI: HOCSS-dBosch OMC Comments: -Long Description: If the averaged measurement value RXLEV_UL is greater than the

threshold RXLEV_UL_IH and the averaged measurement valueRXQUAL_UL is worse than the threshold L_RXQUAL_UL_H, an intracellhandover is initiated. For this intracell handover it is not necessary that theadjusted transmission power for the uplink has already reached themaximum.See also L_RXQUAL_UL_H, EN_INTRA_HO, L_RXLEV_UL_P,L_RXLEV_UL_H

Dependency: RXLEV_UL_IH > L_RXLEV_UL_HGSM 12.20 Class: -GSM 12.20 Attribute: -




155 SDFU/TCU VersionRecommended DefaultValue:

-

Range: TextRange Semantics: -Modification State: -Short Description: Version information about the BCF Sub-Rate Digital Facility Unit (SDFU)

and Traffic Control Unit (TCU)BSC of type BCF only.

OMC Object: SDFU/TCUOMC AUI: BOARDTYPE, FWSERIES, FWVER, SERIALNO, PACKID, ARTMASTER,

HWSERIES, HWVEROMC GUI: Board Type, Firmware Series, Firmware Version, Serial Number, Pack

Identifier, Art Master, Hardware Series, Hardware VersionBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: The SDFU/TCU Version attribute contains the following information:

- BoardType: 0 = TCU, 1 = SDFU- Firmware Information: This is the boot ROM firmware (not the applicationsoftware). This includes Boot ROM firmware release and Boot ROMfirmware version (each a hexadecimal byte).- Serial Number (WES#): 12 digit number which indicates date and placeof manufacture and Warranty Eligibility System information. This is inyyNGmmnnnnnn format where: yy=year, NG indicates the Nurembergfactory, mm=month, nnnnnnn is a 6 digit number.- Circuit Pack Identifier : MABnn where MAB is the board family nn is a 1digit number followed by a blank or a 2 digit number e.g. a 120 ohm SDFUis a MAB6, a TCU is a MAB20.- Art Master : The Art Master is the printed wiring board layout. The formatis nWm where n is a 1 digit number indicating the actual circuit boardphysical layout represents working issue, m is a one digit numberindicating different physical information on the board e.g. 1W1, 2W1.- HW Series: Snn where S represents 'Series' nn is a 1 digit numberfollowed by a blank or a 2 digit number e.g. S1, S25.- HW Vintage: Vnn where V represents 'Vintage' nn is a 1 digit numberfollowed by a blank or a 2 digit number e.g. V2, V15.

Dependency: -GSM 12.20 Class: GSM1220_gsmEquipmentGSM 12.20 Attribute: version



157

156 SDU bad sectorsRecommended DefaultValue:

-

Range: 0-100Range Semantics: Unit: percent, '0' in case of SCSI discModification State: -Short Description: Storage Disk Unit (SDU) sector information. This parameter shows the

percentage of bad sectors on the SDU in the BCE.BSC of type BCE only.

OMC Object: SDUOMC AUI: BADSECOMC GUI: Percentage Bad SectorsBosch OMC Object: SDUBosch OMC AUI: SDUSECI.PERCENTAGE_OF_BAD_SECTORSBosch OMC Comments: -Long Description: See also 'SDU higher threshold', 'SDU lower threshold' and 'SDU No. of

sectors'Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -




157 SDU higher thresholdRecommended DefaultValue:

-

Range: 0-100Range Semantics: Unit: percent, '0' in case of SCSI discModification State: -Short Description: Higher threshold in percentage for Storage Disk Unit (SDU) bad sectors in

the BCE.BSC of type BCE only.

OMC Object: SDUOMC AUI: HIGHTHROMC GUI: Sector Threshold HighBosch OMC Object: SDUBosch OMC AUI: SECTHR-SECTOR_THRESHOLD_HIGHBosch OMC Comments: -Long Description: See also 'SDU bad sectors', 'SDU lower threshold' and 'SDU No. of




159

158 SDU lower thresholdRecommended DefaultValue:

-

Range: 0-100Range Semantics: Unit: percent, '0' in case of SCSI discModification State: -Short Description: Lower threshold in percentage for Storage Disk Unit (SDU) bad sectors in

the BCE.BSC of type BCE only.

OMC Object: SDUOMC AUI: LOWTHROMC GUI: Sector Threshold LowBosch OMC Object: SDUBosch OMC AUI: SECTHR-SECTOR_THRESHOLD_LOWBosch OMC Comments: -Long Description: See also 'SDU bad sectors', 'SDU higher threshold' and 'SDU No. of





159 SDU No. of sectorsRecommended DefaultValue:

-

Range: 0-32767Range Semantics: Unit of 'kilo' (1024) sectorsModification State: -Short Description: Storage Disk Unit (SDU) sector information. This parameter shows the

number of sectors on the SDU in the BCE.BSC of type BCE only.

OMC Object: SDUOMC AUI: NRSECOMC GUI: No. of 'kilo' SectorsBosch OMC Object: SDUBosch OMC AUI: SDUSECI.NUMBER_OF_KILO_SECTORSBosch OMC Comments: Range:1-526Long Description: See also 'SDU bad sectors', 'SDU higher threshold' and 'SDU lower

threshold'Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



161

160 ServerAllocationRecommended DefaultValue:

-

Range: StructureRange Semantics: Name of server and related E1 portsModification State: -Short Description: The server and SDFU E1 ports which support the signalling for this PG

(type PPC).BCF only

OMC Object: PGOMC AUI: SERVERNAME, E1PORTxOMC GUI: Server AllocationBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: The server allocation is dynamically set by the BCF during recovery of

LTEVM, server or whole BCF.Dependency:GSM 12.20 Class: -GSM 12.20 Attribute: -




161 Serviceprovider L2 (BTC)Recommended DefaultValue:

1

Range: 1-6Range Semantics: -Modification State: -Short Description: Part of the identification of the Abis link that is used for signalling purposes

between BSC and BTC.OMC Object: BTC-LAPDOMC AUI: ABISSPL2SPOMC GUI: ABIS SigSlot Info: EXTC IDBosch OMC Object: BTCBosch OMC AUI: ABISPROV-bBosch OMC Comments: Range:0-6Long Description: A 64 kbit/s slot of the Abis link is used by BSC and BTC for O&M related

signalling.In the BCE the EXTC-PPP defined by this parameter supports the Layer 2functionality needed for the communication between the BTC and BSC.In the BCF this parameter identifies a BCF internal resource and can notbe set by the operator.See also 'Serviceprovider PPC (BTC)' and 'Sign.-Slot BTC'




163

162 Serviceprovider L2 (RT)Recommended DefaultValue:

-

Range: 1-6Range Semantics: -Modification State: -Short Description: Part of the identification of the Abis link that is used for signalling purposes

between BSC and RT.OMC Object: RT-LAPDOMC AUI: ABISSPL2SPOMC GUI: ABIS SigSlot Info: EXTC IDBosch OMC Object: RTBosch OMC AUI: ABISPROV-bBosch OMC Comments: -Long Description: A 64 kbit/s slot of the link served by the EXTC is used by BSC and RT for

O&M and call handling related signalling. Up to four 64 kbit/s slots of thislink are used by the RT for traffic channels.In the BCE the EXTC-PPP defined by this parameter supports the Layer 2functionality needed for the communication between the RT and BSC.In the BCF this parameter identifies a BCF internal resource and can notbe set by the operator.See also 'Serviceprovider PPC (RT)', 'Traffic Slots RT' and 'Sign.-Slot RT'

Dependency: EXTC-ExistenceGSM 12.20 Class: -GSM 12.20 Attribute: -




163 Serviceprovider PG (TCG)Recommended DefaultValue:

-

Range: 0-29 (BCE), 0-69 (BCF)Range Semantics: -Modification State: -Short Description: Part of the identification of the M interface link between BSC and TCG.

This parameter identifies the service provider PG-D2M which serves thisE1/T1 link.

OMC Object: TCGOMC AUI: PGIDOMC GUI: PCM Service Provider: PG IdBosch OMC Object: TCGBosch OMC AUI: PCMPROV-aBosch OMC Comments: -Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



165

164 Serviceprovider PPC (BTC)Recommended DefaultValue:

-

Range: 0-29 (BCE), 0-69 (BCF)Range Semantics: -Modification State: -Short Description: Part of the identification of the Abis link that is used for signalling purposes

between BSC and BTC. This parameter identifies the service provider PGof type PPC.

OMC Object: BTC-LAPDOMC AUI: ABISSPPGIDOMC GUI: ABIS SigSlot Info: PG IDBosch OMC Object: BTCBosch OMC AUI: ABISPROV-aBosch OMC Comments: -Long Description: A 64 kbit/s slot of this link is used by BSC and BTC for O&M related

signalling.See also 'Serviceprovider L2 (BTC)' and 'Sign.-Slot BTC'

Dependency: PG-ExistenceGSM 12.20 Class: -GSM 12.20 Attribute: -




165 Serviceprovider PPC (RT)Recommended DefaultValue:

-

Range: 0-29 (BCE), 0-69 (BCF)Range Semantics: -Modification State: -Short Description: Part of the identification of the Abis link that is used for traffic and

signalling purposes between BSC and RT. This parameter identifies theservice provider PG of type PPC.

OMC Object: RT-LAPDOMC AUI: ABISSPPGIDOMC GUI: ABIS SigSlot Info: PG IDBosch OMC Object: RTBosch OMC AUI: SBosch OMC Comments: -Long Description: A 64 kbit/s slot of this link is used by BSC and RT for O&M and call

handling related signalling. Up to four 64 kbit/s slots of this link are usedby the RT for traffic channels.See also 'Serviceprovider L2 (RT)', 'Traffic Slots RT' and 'Sign.-Slot RT'

Dependency: PG-ExistenceGSM 12.20 Class: -GSM 12.20 Attribute: -



167

166 Sign.-Slot BTCRecommended DefaultValue:

-


(T1)Modification State: -Short Description: This parameter associates a 64 kbit/s time slot in the Abis link between

BSC and BTC for O&M related signalling. Must match with the sitedependent configuration.

OMC Object: BTC-LAPDOMC AUI: SIGPCM, SIGSLOTOMC GUI: ABIS SigSlot Info: PCM System / Slot NumberBosch OMC Object: BTCBosch OMC AUI: ASIGSLI-a-bBosch OMC Comments: -Long Description: The signalling channel for the BTC can be concentrated with the signalling

channels of up to 3 RTs.See also 'Serviceprovider L2 (BTC)', 'Serviceprovider PPC (BTC)', 'Sign.-Slot RT'

Dependency: The line number shall correspond to the value of parameter 'LIC-Input-LineA (n)' of object BTC.Concentration is only supported by BTS2000 (with MRIF) and BTS2000/C.

GSM 12.20 Class: lapdLinkGSM 12.20 Attribute: abisSigChannel




167 Sign.-Slot RTRecommended DefaultValue:

-


(T1)Modification State: -Short Description: This parameter associates a 64 kbit/s time slot in the Abis link between

BSC and RT for O&M and call handling related signalling.OMC Object: RT-LAPDOMC AUI: SIGPCM, SIGSLOTOMC GUI: ABIS SigSlot Info: PCM System / Slot NumberBosch OMC Object: RTBosch OMC AUI: ASIGSLI-a-bBosch OMC Comments: -Long Description: The signalling channels of up to 4 RTs or 1 BTC and 3 RTs can be

concentrated.See also 'Serviceprovider L2 (RT)', 'Serviceprovider PPC (RT)', 'TrafficSlots RT', 'Sign.-Slot BTC'

Dependency: The line number shall correspond to the value of parameter 'LIC-Input-LineA (n)' of object BTC.Concentration is only supported by BTS2000 (with MRIF) and BTS2000/C.

GSM 12.20 Class: lapdLinkGSM 12.20 Attribute: abisSigChannel



169

168 Signalling Link CodeRecommended DefaultValue:

-

Range: 0-15Range Semantics: -Modification State: -Short Description: This parameter identifies a signalling link within a signalling link set (LSET)

as numbered by the MSC. The link code assigned is required to beidentical to the one assigned in the MSC.

OMC Object: LINKOMC AUI: SLCOMC GUI: Signalling Link CodeBosch OMC Object: LINKBosch OMC AUI: LINKCODEBosch OMC Comments: -Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -




169 SigSlotsReservedRecommended DefaultValue:

-

Range: 1-15Range Semantics: -Modification State: LOShort Description: Minimum number of signalling timeslots to be reserved for this PPC at the

interface "cell server" <-> "sdfu" (which serves BCON).PG of type PPC only, BCF only

OMC Object: PGOMC AUI: MINRSVDTSOMC GUI: Min Reserved Signal TimeslotsBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: This parameter is not settable for BCF R1Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



171

170 SPC_BSCRecommended DefaultValue:

-

Range: 0-16383Range Semantics: -Modification State: -Short Description: The Origination Signalling Point Code specifies the address of the BSC

within the CCS7 network.OMC Object: OPCOMC AUI: OPCOMC GUI: Signaling Point CodeBosch OMC Object: OPCBosch OMC AUI: SPC/SPCBBosch OMC Comments: Range:StructureLong Description: A point code in the CCS7 network consists of the Network Indicator (NI)

and the Signalling Point Code (SPC). The point code is unique for theCCS7 network.The parameter NI_BSC specifies the type of CCS7 network to which theBSC belongs. The parameter SPC_BSC specifies the Signalling PointCode (SPC) of the BSC in the CCS7 network.See also NI_BSC, NI_MSC, SPC_MSC





171 SPC_MSCRecommended DefaultValue:

-

Range: 0-16383Range Semantics: -Modification State: -Short Description: The Destination Signalling Point Code specifies the address of the MSC

within the CCS7 network.OMC Object: LSETOMC AUI: DPCOMC GUI: Signaling Point CodeBosch OMC Object: LSETBosch OMC AUI: SPC/SPCBBosch OMC Comments: Range:StructureLong Description: A point code in the CCS7 network consists of the Network Indicator (NI)

and the Signalling Point Code (SPC). The point code is unique for theCCS7 network.The parameter NI_MSC specifies the type of CCS7 network to which theMSC belongs. The parameter SPC_MSC specifies the Signalling PointCode (SPC) of the MSC in the CCS7 network.See also NI_BSC, NI_MSC, SPC_BSC




173

172 SYNC_NC(n,0)Recommended DefaultValue:

0 (non-synchronised)

Range: 0-3Range Semantics: 0 = non-synchronised, 1 = synchronised, 2 = pre-synchronised (, 3 =

pseudo-synchronised - not supported)Modification State: LO/ULShort Description: Synchronisation indication for handover from Neighbour Cell n to cell 0OMC Object: ADJCELLOMC AUI: SYNCIDOMC GUI: Synchronized / Synch IdentificationBosch OMC Object: NCELLBosch OMC AUI: CDESC-kBosch OMC Comments: Range:NOSYNC = 0, SYNC = 1, PRESYNC = 2, PSEUSYNC = 3Long Description: The synchronisation of a handover concerns the timing advance which has

to be considered in incoming intercell handovers. Typically this is used forsectored cell configurations in order to accelerate the handover procedure.In order to enable a synchronised handover between synchronised radiocells, for every radio cell served by a particular BSC, this parametercontains the synchronisation state of all neighbour cells. Thesynchronisation state of the new cell with respect to the old cell isconveyed to the BSC serving the old cell via the handover requestacknowledge and handover command messages on the BSC-MSCinterface and is forwarded to the concerned MS in the old cell via thehandover command message on the air interface.synchronised: the timing advance is given in advance; non-synchronised:the timing advance is given by the physical information message from theBTS; pre-synchronised: the timing advance is given in the handovercommand message or a default value is used. Phase 1 MSs do notsupport pre-synchronised and will be executed as non-synchronised.pseudo-synchronised: the timing advance is computed by the real timedifference given in the handover command. Pseudo-synchronised is notsupported and will be executed as non-synchronised if configured.This parameter is unique for the relation between a cell and a neighbourcell.Whether sychronised handover is possible between cells is dependent onthe BTS type and physical configuration.See also PTA_HO(n,0)

Dependency: -GSM 12.20 Class: adjacentCellHandOverGSM0508GSM 12.20 Attribute: synchronized




173 T_MKRecommended DefaultValue:

120 min = 12

Range: 0-24Range Semantics: Unit: 10 minModification State: LO/ULShort Description: This attribute defines the maximum allowed duration of a minimum

configuration in case of a mains fault in the BTS site.OMC Object: BTSOMC AUI: TMINCFGOMC GUI: Emergency Configuration TimerBosch OMC Object: BTSBosch OMC AUI: TMINCONFBosch OMC Comments: Range:0-240 step 10Long Description: This parameter decides how long the minimum configuration will be kept

for the BTS. After this time the BTS will be switched off.The BSS informs the OMC about the following events by means of internalalarms: power down of power supply, switching to minimum configuration,switching off the BTS, restoring power supply, restarting normal operation.See also: NS_TRX




175

174 T_qho (MAP-Timer)Recommended DefaultValue:

2 sec

Range: 1s-30sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Handover resource allocation

queuing guard timer (maximum allowed queuing time for handover)OMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: TqhoBosch OMC Object: BSCBosch OMC AUI: MAPT-20-b-cBosch OMC Comments: -Long Description: After the HANDOVER REQUEST message without having the necessary

TCH available the HANDOVER REQUEST shall be put into a queue; theQUEUING INDICATION message shall be returned to the MSC and thetimer T_qho shall be started. The timer value T_qho specifies themaximum queuing delay and is determined by the operator.The procedure shall be terminated with a successful or unsuccessfulreservation of the required traffic channel by sending a HANDOVERREQUEST ACKNOWLEDGE or a HANDOVER FAILURE message,respectively, to the MSC.If the timer T_qho expires the HANDOVER REQUEST shall be removedfrom the queue and a HANDOVER FAILURE message shall be sent to theMSC with the Cause value 'no radio resource available'.Too low values: Even low values increase probability of a successful hand-over resource allocation. Concrete values depend on offered traffic,number of available TCH and requested blocking rate and have to betaken from a table of the Erlang distribution.Too high values: Call may be dropped if the Assignment Request isqueued too long and therefore prohibits Handover to excute.See also T11 (MAP-Timer), Q_THRESHOLD_VAL,TOTAL_NUM_Q_PLACE_AVAIL, MSC Timer: HO ACK T101 (TRR2).

Dependency: Tqho < MSC Timer: HO ACK T101 (TRR2)Queuing has to be supported

GSM 12.20 Class: btsGSM 12.20 Attribute: timeLimitHandover




175 T_SDCCH_HO_ALLOWEDRecommended DefaultValue:

2824 msec = 3

Range: 1-31Range Semantics: multiples of 2*470.77 msec for SDCCH channels (2 SACCH periods)Modification State: LO/ULShort Description: The time allowed for SDCCH - SDCCH handover and SDCCH - TCH

handover in case of handover during queueing. If an SDCCH is allocatedfor handover purposes to an MS, SDCCH - SDCCH handover is blockedfor this MS for this time.

OMC Object: HOCTRLOMC AUI: TIMSDCCHHOOMC GUI: SDCCH HO Time AllowedBosch OMC Object: HOBosch OMC AUI: TSDCCHHOBosch OMC Comments: -Long Description: If a SDCCH is allocated to a MS this timer is started and a SDCCH-

SDCCH handover is blocked for this specific MS until the timer expires. Ifthe timer has expired and SDCCH-SDCCH handover is enabled ahandover request may be generated if required due to radio or othercriteria.The timer also applies to SDCCH TCH Handover in case of Handoverduring Queueing.See also EN_SDCCH_HO, EN_SDCCH_TCH_HO

Dependency: SDCCH - SDCCH Handover (EN_SDCCH_HO) has to be enabledGSM 12.20 Class: -GSM 12.20 Attribute: -



177

176 T1 (MAP-Timer)Recommended DefaultValue:

2 sec

Range: 1s-60sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Blocking/Unblocking guard timerOMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: T1Bosch OMC Object: BSCBosch OMC AUI: MAPT-1-b-cBosch OMC Comments: -Long Description: The MSC chooses the terrestrial resources to be used. The MSC therefore

needs to be informed of any terrestrial circuits that are out of service at theBSS. This is performed by using a simple blocking/unblocking procedure.The timer T1 watches over the reception of the Blocking/UnblockingAcknowledge message from the MSC and is started after the BSC sendsa blocking/unblocking message to the MSC. T1 is stopped after receivinga Blocking Acknowledge/Unblocking Acknowledge from the MSC.After a first T1 expiration the BSS repeats the Blocking/Unblockingmessage and restarts T1.After a second expiration the BSS marks the belonging circuits asblocked/unblocked without waiting for the acknowledge. The BSCcontinues Blocking procedure with the next CIC.Too low values: Blocking procedure lasts longer as BSC re-sendsmessages in case of MSC not answering in time.Message rate on A interface increases.Too high values: Blocking procedures lasts longer in case of MSC notanswering.

Dependency: T1 > time needed by MSC to process message under nominal loadGSM 12.20 Class: bscGSM 12.20 Attribute: bssMapT1





25 sec

Range: 1s-30sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC-Assignment guard timer on the old

channel. Used during dedicated Assignment and Intracell HandoverOMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: T10Bosch OMC Object: BSCBosch OMC AUI: MAPT-10-b-cBosch OMC Comments: -Long Description: The timer is started with sending the ASSIGNMENT_COMMAND

message (dedicated assignment, old channel) to the MS and is normallystopped when the MS has correctly seized the new channel (whenreceiving the Assignment Complete message from the MS) or if anAssignment Failure is received from the MS on the old channel. Itspurpose is to keep the old channel sufficiently long for the MS to be able toreturn to the old channel, and to release the channel if the MS is lost.On receipt of the ASSIGNMENT_COMPLETE message or timer expiry theold channel is released.On time out an Assignment Failure message is sent to the MSC. Thetiomer is not re-started.Too low values result in a low call success rate. Values below about 10sec are not useable.Too high values result in a high resource usage on the SDCCH or theoriginating TCH, respectively, in case of failed assignments. This mayresult in a high resource blocking.See also T3107 (Um-Timer), MSC Timer: ASSIGN (TRR1)

Dependency: T10 (MAP-Timer) > T3107 (Um-Timer)The value of Trr1 in the MSC shall be higher than T10 plus thetransmission time of ASSignment REQuest and ASSignment COMpletemessage.

GSM 12.20 Class: bscGSM 12.20 Attribute: bssMapT10



179


4 sec

Range: 1s-5minRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Queuing timer. Used during

Dedicated Assignment. Maximum allowed queuing time for traffic channelassignment

OMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: T11Bosch OMC Object: BSCBosch OMC AUI: MAPT-11-b-cBosch OMC Comments: -Long Description: After the ASSIGNMENT REQUEST message without having the

necessary TCH available the ASSIGNMENT REQUEST message is putinto a queue; the QUEUING INDICATION message is returned to the MSCand the timer T11 is started. The timer value T11 specifies the maximumqueuing delay and is determined by the operator.The procedure is terminated with a successful or unsuccessful assignmentof the required traffic channel by sending an ASSIGNMENT COMPLETEor an ASSIGNMENT FAILURE message to the MSC.If the timer T11 expires, directed retry is enabled and all the criterias aremet, directed retry will be performed.If the timer T11 expires and directed retry is not enabled, the TCH requestis removed from the queue and an ASSIGNMENT FAILURE message issent to the MSC, with the Cause 'no radio resource available'.Too low values: Even low values increase probability of a successfulchannel assignment. Concrete values depend on offered traffic, number ofavailable TCH and requested blocking rate and have to be taken from atable of the Erlang distribution.Too high values: Some Assignment Requests will be queued very longwithout the originating party having any indication of the call being queuedand without increasing the mean probability of a TCH being available.See also T_qho (MAP-Timer), Q_THRESHOLD_VAL,TOTAL_NUM_Q_PLACE_AVAIL, MSC Timer: ASSIGN (TRR1), Queing

Dependency: Queuing has to be supportedGSM 12.20 Class: btsGSM 12.20 Attribute: timeLimitCall





10 sec

Range: 5s-30sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Reset Acknowledge TimerOMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: T13Bosch OMC Object: BSCBosch OMC AUI: MAPT-13-b-cBosch OMC Comments: -Long Description: This timer is started after the reception of a Reset message in the BSS. It

gives time for the BSS to release all affected calls. After expiration of thistimer the BSS sends a Reset Acknowledge message to the MSC.On time out the Reset Acknowledge message is sent to the MSC. Thetimer is not restarted.Too low values: Increase system unavailability in case of BSS outage ifT13 expires prior to resource clearance.Too high values: Increases system unavailability in case of BSS outage.See also: T16 (MSC-BSC Timers for GSM 8.0)

Dependency: The value of the "Wait for Acknowledge timer" T16 in the MSC shall behigher than the value of T13 plus the transmission time of the reset andthe reset acknowledge message (i.e. T13 > time needed by BSS to clearresources).




181


30 sec

Range: 30s-120sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Overload timer for access class

barring procedure (Note: If this timer is running overload messages fromMSC are ignored)

OMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: T17Bosch OMC Object: BSCBosch OMC AUI: MAPT-17-b-cBosch OMC Comments: -Long Description: T17 is started after receiving the OVERLOAD message from the MSC. All

received overload messages or signalling point congested information areignored during this time in order not to reduce the traffic too rapidly.On receipt of the first OVERLOAD message or signalling point congestedinformation, the traffic is reduced by one step. At the same time, timersT5(T17) and T6(T18) are started. During T5(T17) all received overloadmessages or signalling point congested information are ignored in ordernot to reduce the traffic too rapidly. Reception of an OVERLOAD messageor signalling point congested information after expiry of T5(T17) but stillduring T6(T18) , will decrease the traffic load by one more step, andrestart T5(T17) and T6(T18).This step by step reduction of traffic is continued until maximum reductionis obtained by arriving at the last step. If T6(T18) expires (i.e. noOVERLOAD message or signalling point congested information isreceived during T6(T18)) the traffic will be increased by one step andT6(T18) will be started, unless full load has been resumed.Too low values: Traffic may be reduced more than appropriate.Too high values: Traffic may be reduced less than appropriate, resulting into high load on the MSC.NOTE: Timers T5 and T6 are running in the MSC whilst Timers T17 andT18 are running in the BSS.Formerly: T5See also: EN_ACC_BARRING, Barring Sequence, M1, M2, N1, N2, T18(MAP-Timer).

Dependency: 30s <= T17 (MAP-Timer) < T18 (MAP-Timer)GSM 12.20 Class: bscGSM 12.20 Attribute: bssMapT17





60 sec

Range: 30s-120sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Overload timer for access class

unbarring procedureOMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: T18Bosch OMC Object: BSCBosch OMC AUI: MAPT-18-b-cBosch OMC Comments: -Long Description: If this timer expires, the traffic will be increased by one step (step size

given in parameter M2 resp. N2) and the timer will be started, unless fullload has been resumed.On receipt of the first OVERLOAD message or signalling point congestedinformation, the traffic is reduced by one step. At the same time, timersT5(T17) and T6(T18) are started. During T5(T17) all received overloadmessages or signalling point congested information are ignored in ordernot to reduce the traffic too rapidly. Reception of an OVERLOAD messageor signalling point congested information after expiry of T5(T17) but stillduring T6(T18) , will decrease the traffic load by one more step, andrestart T5(T17) and T6(T18).This step by step reduction of traffic is continued until maximum reductionis obtained by arriving at the last step. If T6(T18) expires (i.e. noOVERLOAD message or signalling point congested information isreceived during T6(T18)) the traffic will be increased by one step andT6(T18) will be started, unless full load has been resumed.Too low values: If T18 has a similar value as T17, it becomes unlikely thatfurther overload messages are received during the time after expiry of T17and before expiry of T18. Thus, traffic is not reduced further but increasedagain. Thise leads to a toggling barring/unbarring of access classes.Too high values: Access classes remain barred very long, although thereis no overload situation anymore.NOTE: Timers T5 and T6 are running in the MSC whilst Timers T17 andT18 are running in the BSS.Formerly: T6See also: EN_ACC_BARRING, Barring Sequence, M1, M2, N1, N2, T17(MAP-Timer)

Dependency: T18 > T17 (MAP-Timer) >= 30sT18 >= 60sNote: Both these dependencies must be fulfilled




183


10 sec

Range: 1s-60sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Reset Circuit Guard TimerOMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: T19Bosch OMC Object: BSCBosch OMC AUI: MAPT-19-b-cBosch OMC Comments: -Long Description: If a circuit has to be put to idle at the BSS due to an abnormal SCCP-

connection release, a RESET CIRCUIT message will be sent to the MSCand T19 will start. When the MSC receives this message, it clears thepossible call and puts the circuit, if known, to the idle state. If the circuit isknown, a RESET CIRCUIT ACKNOWLEDGE message is returned to theBSS and T19 is stopped. If the circuit is unknown in the MSC, anUNEQUIPPED CIRCUIT message is returned to the BSS.Timer T19 is used at the BSS to supervise the reset circuit procedure. Ifthe timer elapses before a response (RESET, RESET CIRCUITACKNOWLEDGE or UNEQUIPPED CIRCUIT) is returned to the BSS, theprocedure is repeated.Too low values: Increased message rate and delayed re-availability of CICif message is repeated prior to MSC response.Too high values: delayed re-availability in case of lost Reset CircuitAcknowledge messages

Dependency: T19 > time needed by MSC to process and answer Reset Circuit messageunder nominal MSC load.





183 T3101 (Um-Timer)Recommended DefaultValue:

3 sec

Range: 1s-10sRange Semantics: -Modification State: LOShort Description: Um interface timer in BSC - Guard Timer on SDCCH, used during

Immediate AssignmentOMC Object: BTSOMC AUI: AIRTIMER (-Vx, -Ux) (i.e. AIRTIMERV1, AIRTIMERU1)OMC GUI: Air Timer: T3101Bosch OMC Object: TIMERBosch OMC AUI: BTSAT-T3101-b-cBosch OMC Comments: -Long Description: The timer is started after sending the Immediate Assignment Command

message to the MS.Timer is stopped after receiving the initial layer 3 message (e.g. CMService Request or Paging Response) in the BSC. If T3101 times out, theassigned SDCCH is released. That means the RF Channel Releasemessage is sent to the BTS.Very low values: Result in low Immediate Assignment Success rate,resulting in continued attempts by MS to acquire SDCCH, resulting in highresource usage, which may result in high resource blocking.Too high values: Result in high resource usage in case of unsuccessfulImmediate Assignments, may result in high resource blocking..

Dependency: T3101 > time needed by MS to seize SDCCHGSM 12.20 Class: btsGSM 12.20 Attribute: t31xx.t3101



185


23 sec

Range: 1s-60sRange Semantics: -Modification State: LOShort Description: Um interface timer in BSC - Assignment guard timer on new channel, used

during Dedicated Assignment.Assignment guard timer on target TCH, used during intra cell Handover.

OMC Object: BTSOMC AUI: AIRTIMER (-Vx, -Ux) (i.e. AIRTIMERV7, AIRTIMERU7)OMC GUI: Air Timer: T3107Bosch OMC Object: TIMERBosch OMC AUI: BTSAT-T3107-b-cBosch OMC Comments: -Long Description: The timer is started after activating the new channel on Abis interface

(receiving Channel Activation Acknowledge from the BTS) and is normallystopped when the MS has correctly seized the new channel If AssignmentComplete is received on the new channel, or if Assignment Failure isreceived on the old channel.If T3107 expires before an ASSIGNMENT_COMPLETE or anASSIGNMENT_FAILURE message has been received from the MS, thealready allocated resources on the new channel have to be released andan ASSIGNMENT_FAILURE is sent to the MSC.Too low values: Low call success rate. Values below approx. 10 secondsare not useable.Too high values: Result in high resource usage on the new channel. Thismay result in high resource blocking.See also T10 (MAP-Timer), TRR1 (MSC-BSC Timers for GSM 8.0)

Dependency: T3107 > time needed by MS to revert to old channel (SDCCH/TCH,Approx. 10 seconds).T3107 >> time needed to seize new TCH. This is approx. 4 seconds.T3107 (Um-Timer) < T10 (MAP-Timer)

GSM 12.20 Class: btsGSM 12.20 Attribute: t31xx.t3107





12 sec

Range: 1s-30sRange Semantics: -Modification State: LOShort Description: Timer for the Um interface to guard the reception of RELEASE

INDICATION.OMC Object: BTSOMC AUI: AIRTIMER (-Vx, -Ux) (i.e. AIRTIMERV9, AIRTIMERU9)OMC GUI: Air Timer: T3109Bosch OMC Object: TIMERBosch OMC AUI: BTSAT-T3109-b-cBosch OMC Comments: -Long Description: Waiting time for channel deactivation on network side.

It is used in the channel release procedure. Its purpose is to release thechannels in case of loss of communication.NOTE: Its value should be large enough to ensure that the mobile stationdetects a radio link failure.The timer is started on sending the DEACT_SACCH message to the BTS.If no Release_Indication is received during this time, the messageRF_Channel_Release is sent to the BTS.See also T3101 (Um-Timer), T3107 (Um-Timer), T3111 (Um-Timer)

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: t31xx.t3109



187


1 sec

Range: 1s-30sRange Semantics: -Modification State: LOShort Description: Timer for the Um interface to delay the release of channel resources in the

BTS after disconnection of the main signalling link.OMC Object: BTSOMC AUI: AIRTIMER (-Vx, -Ux) (i.e. AIRTIMERV11, AIRTIMERU11)OMC GUI: Air Timer: T3111Bosch OMC Object: TIMERBosch OMC AUI: BTSAT-T3111-b-cBosch OMC Comments: -Long Description: Time out value for channel release on network side.

This timer is used to delay the channel deactivation after disconnection ofthe main signalling link. Its purpose is to let some time for possiblerepetition of the disconnection.It is started on receiving a Release_Indication message. After the timegiven in T3111 the message RF_Channel_Release is sent to the BTS.See also T3101 (Um-Timer), T3107 (Um-Timer), T3109 (Um-Timer)

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: t31xx.t3111




187 T3212Recommended DefaultValue:

120 deci-hours (12 hours) if IMSI detach/attach is enabled30 deci-hours (3 hours), IMSI detach/attach is disabled

Range: 0-255Range Semantics: Unit: 6 min (1 deci-hour), 0-1530minModification State: LO/ULShort Description: Periodic Location Update Timer (Indicates the interval for the MS periodic

location updates)OMC Object: BTSOMC AUI: INTVMSLOCUPDOMC GUI: Timer Periodic Update MSBosch OMC Object: BTSBosch OMC AUI: CONFCCH-dBosch OMC Comments: -Long Description: Periodic updating may be used to notify periodically the availability of the

MS to the network. Periodic updating is performed by using the locationupdating procedure. The timer is started when a signalling activity hastaken place on the radio path. When the MS is powered down the timervalue is kept in memory. When the MS is powered up the timer continues.When timer T3212 reaches its time out value, the MS initiates a locationupdating (Locataion Update Request) and the timer is restarted.Most service provider set this parameter to a high value to reduce load forBSC, MSC and VLR.The value 0 indicates that no periodic update should be used within thecell.See also: ATT

Dependency: If IMSI Detach is used, value should be as high as possibleIf Time based implicit detach is used, the MSC timer for this function hasto be higher than T3212

GSM 12.20 Class: btsGSM 12.20 Attribute: timerPeriodicUpdateMS



189


10 sec

Range: 4s-60sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Reset guard timerOMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: T4Bosch OMC Object: BSCBosch OMC AUI: MAPT-4-b-cBosch OMC Comments: -Long Description: The timer starts after sending a RESET message to the MSC and stops at

the reception of a RESET ACKNOWLEDGE message from the MSC. Ifthe timer expires the RESET MESSAGE is sent anew and the timerstarted again. The RESET message can be sent up toRESET_REP_COUNTER times.After RESET_REP_COUNTER retries, continue with 20*T4Too low values: May time out before MSC send Reset Acknowledge andincrease system unavailability.Too high values: Increase system unavailability in case of MSC outage.See also: T2 ('MSC-BSC Timers for GSM 8.0')

Dependency: The value shall be higher than the value of the MSC timer T2 plus thetransmission time of the Reset and the Reset Acknowledge messages (i.e.T4 >> T2).






10 sec

Range: 5s-60sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Handover Required guard timerOMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: T7Bosch OMC Object: BSCBosch OMC AUI: MAPT-7-b-cBosch OMC Comments: -Long Description: If the BSS has detected that a radio reason exists for a MSC controlled

handover to occur, the BSS sends a HANDOVER REQUIRED message tothe MSC. After sending this HANDOVER REQUIRED message the T7timer is started. Radio Link Control will not produce further HANDOVERREQUIRED messages while the timer T7 is running. After receiving aHANDOVER COMMAND or HANDOVER REQUIRED REJECT messagefrom the MSC the timer is stopped.On time out Radio Link Control resumes normal operation which mayresult in further Handover Required messages.Timer values smaller than 9 sec should be avoided (MSC is not able to doHandover Resource Allocation in second cell if first target cell fails)Timer values smaller than 4 sec are unusable (Handover ResourceAllocation in first target cell probably not completed on receipt of secondHandover Required message by MSC).Too low values: Increase the MSC load and A interface message rateToo high values: Calls can drop due to delayed handover in case of MSCnot being able to allocate resources in any potential target cell.See also T7_IHO, T_qho (MAP-Timer), MSC Timer RQST ACK T201.,TRR2

Dependency: T7 > T_qho (Queuing of MSC controlled HO)T7 > T7_IHO (BSC controlled HO)T7 > time needed by MSC to do one successful handover resourceallocationNote: All dependencies must be fulfilled.




191

190 T7_IHORecommended DefaultValue:

8 sec

Range: 1s-30sRange Semantics: -Modification State: ULShort Description: Timer in BSC - Intra Cell Handover guard timer (Note: This timer is not

specified within GSM - it is specified by Lucent)OMC Object: BSCOMC AUI: DTCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSS DTC: TIhoBosch OMC Object: BSCBosch OMC AUI: MAPTD-11-b-cBosch OMC Comments: -Long Description: If the handover process in the BSC recognises that an intracell handover is

required, the T7_IHO timer is started and no further intracell handoverrequest will be generated for this mobile during this time. The timer isstopped after receiving a Assignment Complete message from the MS. Ontime out the Radio Link Control resumes normal operation which mayresult in further handover attempts.Too low value: Increased BSC load.Values < approx. 4 s should be avoided.Values < approx. 2 s are unusable.Too high values: Call drops due to delayed handovers in case of BSC notbeing able to allocate resources in target cell.See also T7 (MAP-Timer)

Dependency: T7_IHO < T7T7_IHO > time needed by BSC to do successful HO Resource allocation.






32 sec

Range: 1s-60sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Handover guard timer in originating

cellOMC Object: BSCOMC AUI: BSCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSC: T8Bosch OMC Object: BSCBosch OMC AUI: MAPT-8-b-cBosch OMC Comments: -Long Description: Handover execution in the context of the BSS/MSC interface is the

process whereby an MSC instructs an MS to tune to a new dedicated radioresource which may be on a different cell. The HANDOVER COMMANDmessage is generated by the MSC and transmitted to the old BSS which iscurrently supporting the concerned MS. On receipt of the HANDOVERCOMMAND message the T8 timer is started in the originating BSS. Aradio interface HANDOVER COMMAND message is then sent by the oldBSS, to the concerned MS. The message contains a handover referencenumber, previously allocated by the new BSS.The timer is stopped after receiving a Clear Command message withcause Handover Complete from the MSC.If the timer T8 times out, then the old BSS requests the release of thededicated radio resources with a CLEAR_REQUEST message sent to theMSC. The timer is not restarted.Too low values: Resource in originating cell will be released even if MShas not completed the handover. The MS is not able to revert to the oldcell. This results in a higher handover drop rate.Too high values: Higher resource usage in originating cell in case ofquadruple fault (MS not seizing target cell and not reverting to old cell,TRR3 in target BSS not expiring, TRR7 in MSC not expiring).See also: TRR3, TRR7 (MSC-BSC Timer for GSM 8.0)

Dependency: T8 >= TRR7 >= Trr3 (MAP-Timer)GSM 12.20 Class: bscGSM 12.20 Attribute: bssMapT8



193

192 TEMPORARY_OFFSETRecommended DefaultValue:

0

Range: 0-7Range Semantics: 10 * TEMPORARY_OFFSET dB, 7: infiniteModification State: LO/ULShort Description: TEMPORARY_OFFSET is a dynamic offset applied to a particular cell in

order to discourage mobiles in idles mode from re-selecting this cell for apre-defined period of time.The value of TEMPORARY_OFFSET is subtracted from a cells C1 valuefor a period of time defined by PENALTY_TIME.

OMC Object: BTSOMC AUI: TEMPOFFOMC GUI: Cell Reselection: Temporary OffsetBosch OMC Object: CELLBosch OMC AUI: C2CRIT-cBosch OMC Comments: -Long Description: TEMPORARY_OFFSET is a dynamic offset applied to a particular cell in

order to discourage mobiles in idle mode from re-selecting the cell for apre-defined period of time. The time for which this offset iss applied isdefined by the PENALTY_TIME parameter and cen be set by the operator.The C2 reselection criteria is reduced by TEMPORARY_OFFSET duringthis time.When the C2 criterion is employed, a TEMPORARY_OFFSET is typicallyapplied to Lower Layer cells for the period in which they are classified as'fast' moving. Once a mobile is considered to be 'slow' moving theTEMPORARY_OFFSET can be removed. The use ofTEMPORARY_OFFSET (in association with PENALTY_TIME) cantherefore be used to encourage 'slow' moving mobiles to re-select LowerLayer cells, whilst discouraging 'fast' moving mobiles from 'camping-on'this cell layer.A TEMPORARY_OFFSET is not typically applied to Upper Layer cells.The value of TEMPORARY_OFFSET should be chosen according to thesize of the cell and the cell layers.See also CELL_RESELECT_PARAM_IND, CELL_RES_OFFSET,PENALTY_TIME. These parameters specify the criteria for cell reselectionaccording to the C2 criteria for GSM phase 2 MS.





193 THRES_PC_RLFRecommended DefaultValue:

7680 msec = 4

Range: 0-15Range Semantics: multiples of 4*480 msec for TCH resp. 4*470.77 msec for SDCCH

channels (4 SACCH periods), 0 = disabledModification State: LO/ULShort Description: Threshold for power control concerning radio link failure warning.OMC Object: BTSOMC AUI: RADIOLKFAILOMC GUI: Radio Link: Fail WarningBosch OMC Object: RADIOBosch OMC AUI: RLFWBosch OMC Comments: -Long Description: During each call, the radiolink (Um) is monitored for successful message

decoding on the SACCH. If a single SACCH block could not be decoded atimer (initialised with RADIO_LINK_TIMEOUT) is decremented by 1, if itcould be decoded it is incremented by 2 not exceeding the threshold givenin RADIO_LINK_TIMEOUT. If the timer gets equal or lower thanTHRES_PC_RLF, the 'radio link failure warning' alarm occurs and thetransmitter power of both BTS and MS are set to maximum. Thisprocedure becomes important only if neither handover nor power controlwas able to improve the RX/TX quality for this call before.Formerly: N_BS_TXPWR_MSee also RADIO_LINK_TIMEOUT (T100)

Dependency: THRES_PC_RLF < RADIO_LINK_TIMEOUT (T100)GSM 12.20 Class: -GSM 12.20 Attribute: -



195

194 TIC[TCE_CODE]Recommended DefaultValue:

-

Range: 0-63Range Semantics: -Modification State: LO/ULShort Description: TransCoder Equipment (TCE) rack ID. Must match with the site

dependent configuration.OMC Object: TCGOMC AUI: RACKOMC GUI: Transcoder Id Code: TCE Rack IdBosch OMC Object: TCGBosch OMC AUI: TRCID-aBosch OMC Comments: -Long Description: The Transcoder Id Code (TIC) consists of the parameters

TIC[TCE_CODE], TIC[TCG_CODE], TIC[TCGQ_CODE].The TIC is used to identify the faulty object in TCE/STF alarms. The BSCmaps the TIC to the appropriate TCG/TCB/TRC instance.See also 'TIC[TCG_CODE]' and 'TIC[TCGQ_CODE]'





195 TIC[TCG_CODE]Recommended DefaultValue:

-

Range: 0-3Range Semantics: -Modification State: LO/ULShort Description: TransCoder Group (TCG) code. Must match with the site dependent

configuration.OMC Object: TCGOMC AUI: CODEOMC GUI: Transcoder Id Code: TCG CodeBosch OMC Object: TCGBosch OMC AUI: TRCID-cBosch OMC Comments: -Long Description: The Transcoder Id Code (TIC) consists of the parameters

TIC[TCE_CODE], TIC[TCG_CODE], TIC[TCGQ_CODE].The TIC is used to identify the faulty object in TCE/STF alarms. The BSCmaps the TIC to the appropriate TCG/TCB/TRC instance.See also 'TIC[TCE_CODE]' and 'TIC[TCGQ_CODE]'




197

196 TIC[TCGQ_CODE]Recommended DefaultValue:

-

Range: 0-2Range Semantics: -Modification State: LO/ULShort Description: TransCoder Group (TCG) quartet. Must match with the site dependent

configuration.OMC Object: TCGOMC AUI: QUARTOMC GUI: Transcoder Id Code: TCG QuartettBosch OMC Object: TCGBosch OMC AUI: TRCID-bBosch OMC Comments: -Long Description: The Transcoder Id Code (TIC) consists of the parameters

TIC[TCE_CODE], TIC[TCG_CODE], TIC[TCGQ_CODE].The TIC is used to identify the faulty object in TCE/STF alarms. The BSCmaps the TIC to the appropriate TCG/TCB/TRC instance.See also 'TIC[TCE_CODE]' and 'TIC[TCG_CODE]'





197 TOTAL_NUM_Q_PLACE_AVAIL


5

Range: 0-100Range Semantics: -Modification State: LOShort Description: This attribute is used to set the size of the incoming call queue. The value

0 disables queuing.OMC Object: BTSOMC AUI: TOTQUEUEOMC GUI: Queueing: Total Number of Queue Entries / Enable QueueingBosch OMC Object: BTSBosch OMC AUI: QUEUEM-aBosch OMC Comments: Range:0-30Long Description: TCH assignment and handover requests may be queued in the BSS. The

queuing is guarded by the timer T11 (MAP-Timer) and T_qho (MAP-Timer), respectively. For both, assignment and handover the same queueis used. The parameter TOTAL_NUM_Q_PLACE_AVAIL defines thelength of this queue. Setting the length to 0 disables queuing.See also T11 (MAP-Timer), T_qho (MAP-Timer), Q_THRESHOLD_VAL

Dependency: Sales option Queuing has to be enabled within the Local ConfigurationArea of the BSC (QUEPROV).The serving MSC has also to support Queuing.

GSM 12.20 Class: btsGSM 12.20 Attribute: maxQueueLength



199

198 Traffic Slots RTRecommended DefaultValue:

-


(T1)Modification State: -Short Description: This parameter associates up to two 64 kbit/s time slots in the Abis link

between BSC and RT for traffic (TCH) data.OMC Object: RT-LAPDOMC AUI: TRAFPCM, TRAFSLOTOMC GUI: Traffic Slot Info: PCM System / Slot NumberBosch OMC Object: RTBosch OMC AUI: ATSLI-a-bBosch OMC Comments: -Long Description: An RT supports up to 8 traffic channels. For each traffic channels a 16

kbit/s subslot must be reserved on the Abis interface, i.e. up to two 64kbit/s slots are needed.See also 'Serviceprovider L2 (RT)', 'Serviceprovider PPC (RT)' and 'Sign.-Slot RT'

Dependency: The line number shall correspond to the value of parameter 'LIC-Input-LineA (n)' of object BTC

GSM 12.20 Class: channelGSM 12.20 Attribute: terrTrafChannel




199 Transcoding CapabilityRecommended DefaultValue:

0 (fullRate)

Range: 0,2Range Semantics: 0 = fullRate, 2 = enhancedFullRateModification State: ULShort Description: Specifies whether the BSC is allowed to support fullrate or

enhancedFullRate (depends on transcoder capability).OMC Object: BSCOMC AUI: TRANSCODEOMC GUI: BSS Transcoding CapabilityBosch OMC Object: BSCBosch OMC AUI: TRANSCAPBosch OMC Comments: Range:FULL = 0, DUAL = 1Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -



201

200 TRC Input SlotRecommended DefaultValue:

-

Range: StructureRange Semantics: Line number: 0 - 31, Slot number: 1 - 31 (E1), 1 - 24 (T1)Modification State: -Short Description: This parameter specifies line number and the time slot of the A-Interface

as seen by the MSC.BSC of type BCE only.

OMC Object: TRCOMC AUI: INPCM, INSLOTOMC GUI: InputBosch OMC Object: TRCBosch OMC AUI: TRCIN-a-bBosch OMC Comments: -Long Description: At the MSC the line interfaces are numbered. This parameter specifies the

MSC number of the line that is connected to the A-interface side of theTCG and the 64 kbit/s time slot the TRC is connected to.This parameter is not used in the BSS, because the information isimplicitly contained in the Circuit Id Code (CIC).





201 TRC Output SlotRecommended DefaultValue:

-

Range: StructureRange Semantics: Identification of signalling or traffic slotModification State: -Short Description: This parameter specifies the time slot and the E1 link to the M-Interface,

i.e. the number of the E1 link as seen by the BSC.OMC Object: TRCOMC AUI: OUTPCM, OUTSLOT, OUTSUBSLOTOMC GUI: OutputBosch OMC Object: TRCBosch OMC AUI: TRCOUTT-a-b-c / TRCOUTS-a-bBosch OMC Comments: -Long Description: A transcoder (TRC) output is connected to the BSC via a slot or subslot of

an E1 link on the M interface. For traffic channels 16 kbit/s subslots andfor signalling channels 64 kbit/s slots are used.The slot is identified by the line number (range: 0 - 31) and slot number(range: 1 - 31). In case of a traffic channel the subslot number (range: 1 -4) is given additionally.




203

202 TRC Service ProviderRecommended DefaultValue:

-

Range: Full distinguished name of TRCRange Semantics: -Modification State: -Short Description: Identifies the TRC which is nailed up for the LINK to carry SS7 signalling.

BCF onlyOMC Object: LINKOMC AUI: TRCPROVOMC GUI: TRC Service ProviderBosch OMC Object: -Bosch OMC AUI: -Bosch OMC Comments: -Long Description: -Dependency: -GSM 12.20 Class: -GSM 12.20 Attribute: -




203 Trr3 (MAP-Timer)Recommended DefaultValue:

24 sec

Range: 1s-60sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Handover guard timer in the target

cell. (Note: This timer is not specified within GSM. It is specified byLucent).

OMC Object: BSCOMC AUI: DTCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSS DTC: Trr3Bosch OMC Object: BSCBosch OMC AUI: MAPTD-3-b-cBosch OMC Comments: -Long Description: Time to receive a successful HO-complete on the new channel.

Trr3 is started after sending the Channel Activation to the BTS andstopped on receipt of the HandoverComplete message from MS.On time out of this timer a Clear Request message is sent to the MSC.The timer is not restarted.Related timers: TRR3, TRR8, T8, HO CMPLT CON T102, HO COMPLTNC T202, SUBSQNT INT MSC T104, NTWRK ST NCMSC T204Too low vales: Result in higher handover drop rate as the target cell iscleared before MS has completed the handoverToo high values: Result in higher resource usage in target cell in case ofquadruple fault (MS not seizing target cell and not reverting to old cell, T8in originating cell not expiring, TRR7 in MSC not expiring).

Dependency: T8 >= TRR7 >= Trr3 (MAP-Timer)GSM 12.20 Class: -GSM 12.20 Attribute: -



205

204 Trr5 (MAP-Timer)Recommended DefaultValue:

4 sec

Range: 1s-60sRange Semantics: -Modification State: ULShort Description: Mobile Application Part Timer in BSC - Clear Request guard timer (Note:

This timer is not specified within GSM. It is specified by Lucent).OMC Object: BSCOMC AUI: DTCTIMER (-Vx, -Ux)OMC GUI: BSS MAP Timer in BSS DTC: Trr5Bosch OMC Object: BSCBosch OMC AUI: MAPTD-5-b-cBosch OMC Comments: -Long Description: If the radio communication breaks down on one channel, a 'Clear Request'

is sent to MSC and this timer is started. When the 'Clear Command' isreceived, the timer is stopped.On first time out the Clear Request is repeated and timer TRR5 isrestarted. On second time a SCCP Released message is sent to the MSC.Too low values: Increased message rate on A interface.Unnecessary escalation of clear procedure to SCCP release procedure.Too high values: Resources are unnecessarily occupied in case of MSCfault (MSC not responding to Clear Request message).

Dependency: TRR5 > time needed by MSC to respond to Clear Request.GSM 12.20 Class: -GSM 12.20 Attribute: -




205 TSCRecommended DefaultValue:

-

Range: 0-7Range Semantics: -Modification State: LOShort Description: This parameter specifies which of 8 possible training sequences will be

included in normal bursts or dummy bursts.OMC Object: RTOMC AUI: TSCOMC GUI: Training Sequence CodeBosch OMC Object: RTBosch OMC AUI: TSCBosch OMC Comments: -Long Description: A fixed bit pattern (26 bits) positioned in the middle of a burst. The MS

uses this pattern to synchronise to the network and for error control. Thebit pattern is related to the BCC (base station colour code).For broadcast (BCCH) and common control channels (PCH and AGCH)the TSC is required to be equal to the BCC. The BTS secures this byignoring the parameter TSC and automatically using the BCC.See also: BCC (in BSIC)

Dependency: For broadcast (BCCH) and common control channels (PCH and AGCH)the BSS will automatically use the BCC. In this case the OMC specifiedTSC value will be ignored, but still be displayed on the OMC.




207

206 TX_INTEGERRecommended DefaultValue:

50 time slots = 15

Range: 0-15Range Semantics: 0 = 3 time slots, .., 9 = 12, 10 = 14, 11 = 16, 12 = 20, 13 = 25, 14 = 32, 15

= 50Modification State: LO/ULShort Description: This attribute indicates the maximum number of RACH timeslots the MS

waits before it retries to access the systemOMC Object: BTSOMC AUI: NOSLOTTRSPOMC GUI: No. of Slots Spread TransmissionBosch OMC Object: CELLBosch OMC AUI: NRSSTBosch OMC Comments: -Long Description: When a MS tries to access a system it sends an access request on the

Random Access Channel (RACH). The MS waits a certain time for ananswer. If no answer is receipt during this time, e.g. because another MShad sent an access request at the same time, the MS tries another accessrequest. The maximal number of retries is given with parameterMAX_RETRANS.The number of timeslots (TDMA frames) between two successive channelrequest messages is a random value drawn randomly for each newtransmission with uniform probability destribution in the value range S toS+T-1. Here T is the number of timeslots given by TX-INTEGER and S isdepending on the CCCH configuration and on T as defined below:S = 55 (41) if T has one of the values 3, 8, 14, 50S = 76 (52) if T has one of the values 4, 9, 16S = 109 (58) if T has one of the values 5, 10, 20S = 163 (86) if T has one of the values 6, 11, 25S = 217 (115) if T has one of the values 7, 12, 32The value for S given outside of the parenthesis is in case of a noncombined CCH whereas the value inside is in case of a combinedCCH/SDCCH.

Dependency: -GSM 12.20 Class: btsGSM 12.20 Attribute: noOfSlotsSpreadTrans




207 U_RXLEV_DL_PRecommended DefaultValue:

GSM900: 35; GSM1800: 37

Range: 0-63Range Semantics: -110 + U_RXLEV_DL_P dBm (0 = less than -110 dBm, 63 = greater than -

48 dBm)Modification State: LO/ULShort Description: Upper signal level threshold for downlink power control.OMC Object: POWEROMC AUI: URXLEVDLPOMC GUI: Signal Strength: Downlink Power ReductionBosch OMC Object: PCBosch OMC AUI: SSDL-bBosch OMC Comments: -Long Description: A power decrease is carried out on the downlink if the averaged

measurement value RXLEV_DL is higher than the thresholdU_RXLEV_DL_P. The power decrease is not done if the signal qualityleads to power increase.POW_INCR_STEP_SIZE should be chosen smaller than the rangebetween the upper and lower power control boundaries.See also L_RXLEV_DL_P, EN_BS_PC

Dependency: L_RXLEV_DL_P < U_RXLEV_DL_PU_RXLEV_DL_P - L_RXLEV_DL_P > POW_INCR_STEP_SIZE

GSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: pcUpperThresholdLevParam



209

208 U_RXLEV_UL_PRecommended DefaultValue:

-80 dBm = 30

Range: 0-63Range Semantics: -110 + U_RXLEV_UL_P dBm (0 = less than -110 dBm, 63 = greater than -

48 dBm)Modification State: LO/ULShort Description: Upper signal level threshold for uplink power control.OMC Object: POWEROMC AUI: URXLEVULPOMC GUI: Signal Strength: Uplink Power ReductionBosch OMC Object: PCBosch OMC AUI: SSUL-bBosch OMC Comments: -Long Description: A power decrease is carried out on the uplink if the averaged

measurement value RXLEV_UL is higher than the thresholdU_RXLEV_UL_P. The power decrease is not done if the signal qualityleads to power increase.POW_INCR_STEP_SIZE should be chosen smaller than the rangebetween the upper and lower power control boundaries.See also L_RXLEV_UL_P, EN_MS_PC

Dependency: L_RXLEV_UL_P < U_RXLEV_UL_PU_RXLEV_UL_P - L_RXLEV_UL_P > POW_INCR_STEP_SIZE

GSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: pcUpperThresholdLevParam




209 U_RXQUAL_DL_PRecommended DefaultValue:

1: 0.2% to 0.4%



Modification State: LO/ULShort Description: Upper signal quality threshold for downlink power control.OMC Object: POWEROMC AUI: URXQUALDLPOMC GUI: Signal Quality: Downlink Power ReductionBosch OMC Object: PCBosch OMC AUI: SQDL-bBosch OMC Comments: -Long Description: A power decrease is carried out on the downlink if the averaged

measurement value RXQUAL_DL is better than the thresholdU_RXQUAL_DL_P. The power decrease is not done if the signal levelleads to power increase.Note that a low value stands for a high quality (i.e. low Bit Error Rate(BER)).See also L_RXQUAL_DL_P, EN_BS_PC, L_RXQUAL_DL_H

Dependency: U_RXQUAL_DL_P shall be set to a higher quality than L_RXQUAL_DL_H,i.e. U_RXQUAL_DL_P < L_RXQUAL_DL_HU_RXQUAL_DL_P shall be set to a higher quality than L_RXQUAL_DL_P,i.e. U_RXQUAL_DL_P < L_RXQUAL_DL_P

GSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: pcUpperThresholdQualParam



211

210 U_RXQUAL_UL_PRecommended DefaultValue:

1: 0.2% to 0.4%



Modification State: LO/ULShort Description: Upper signal quality threshold for uplink power control.OMC Object: POWEROMC AUI: URXQUALULPOMC GUI: Signal Quality: Uplink Power ReductionBosch OMC Object: PCBosch OMC AUI: SQUL-bBosch OMC Comments: -Long Description: A power decrease is carried out on the uplink if the averaged

measurement value RXQUAL_UL is better than the thresholdU_RXQUAL_UL_P. The power decrease is not done if the signal levelleads to power increase.Note that a low value stands for a high quality (i.e. low Bit Error Rate(BER)).See also L_RXQUAL_UL_P, EN_MS_PC, L_RXQUAL_UL_H

Dependency: U_RXQUAL_UL_P shall be set to a higher quality than L_RXQUAL_UL_H,i.e. U_RXQUAL_UL_P < L_RXQUAL_UL_HU_RXQUAL_UL_P shall be set to a higher quality than L_RXQUAL_UL_P,i.e. U_RXQUAL_UL_P < L_RXQUAL_UL_P

GSM 12.20 Class: powerControlGSM0508GSM 12.20 Attribute: pcUpperThresholdQualParam




211 UMBRELLA_MICRO_HYSTRecommended DefaultValue:

5dB = 5

Range: 0-31Range Semantics: 0-31dBModification State: LO/ULShort Description: Hysteresis value used as part of the 'layer down receive level', TH5

condition for initiating a 'layer down' handover from an upper (Upper orMiddle) to a lower (Middle or Lower) layer cell.

OMC Object: HOCTRLOMC AUI: UMBHYSTOMC GUI: Umbrella Cell HysteresisBosch OMC Object: HOBosch OMC AUI: HOUMBRCELL-aBosch OMC Comments: -Long Description: The UMBRELLA_MICRO_HYST parameter can be used to influence the

receive level 'entry threshold' to lower layer cells before a 'layer down'handover can be executed.After channel allocation on a SDCCH of a Middle or Upper Layer cell theduration of stay of the MS in the coverage area of a lower layer NC ismeasured using the Cdosnc(n) counter. The Cdosnc(n) counter isincremented by 1 if the averaged receive level for a particular lower layercell is greater than the TH5 condition, defined by;AV_RXLEV_NCELL_S(n) > RXLEV_MIN(n) + TH5(n)Where;TH5 = UMBRELLA_MICRO_HYST + 2*MAX(0,P-MS_TXPWR_MAX(n))Otherwise it is decremented by 1. The counter is also decremented by 1 ifno rxlev measurements are received for that SACCH frame. If theduration of stay in a lower layer NC, Cdosnc(n), reaches its thresholddefined by C_UMBRELLA_MICRO_HO a 'layer down' handover istriggered.See also CELL_TYPE, CELL_TYPE_NC, C_UMBRELLA_MICRO_HO,C_MICRO_HO and C_MICRO_DELAYED_HO




213

212 W_QUAL_HORecommended DefaultValue:

1

Range: 1-3Range Semantics: -Modification State: LO/ULShort Description: The weighting factor is applied to handover control signal quality

measurements to account for effects of DTX (discontinuous transmission)during averaging process.

OMC Object: HOCTRLOMC AUI: WQUALHOOMC GUI: Signal Quality: Weighting FactorBosch OMC Object: HOBosch OMC AUI: HOCSQ-dBosch OMC Comments: -Long Description: This parameter specifies the weight of full-set quality measurements with

respect to sub-set quality measurements in the averaging process. Theeffective averaging period is reduced by the weighting factor if DTX is notactive.W_QUAL_HO and A_QUAL_HO should be considered together to get ameaningful averaging period.The recommended default value applies for disabled DTX. With DTXenabled the weighting factor for Full measurements should be set to 2. Toget a effective window size of 4 the recommended default value forA_QUAL_HO with DTX enabled is 8.See also EN_RXQUAL_HO, A_QUAL_HO, DTX, Downlink DTX Speech,Downlink DTX Data

Dependency: -GSM 12.20 Class: handoverControlGSM0508GSM 12.20 Attribute: hoAveragingQualParam




213 W_QUAL_PCRecommended DefaultValue:

1

Range: 1-3Range Semantics: -Modification State: LO/ULShort Description: The weighting factor is applied to power control signal quality

measurements to account for effects of DTX (discontinuous transmission)during averaging process.

OMC Object: POWEROMC AUI: WQUALPCOMC GUI: Signal Quality: Weighting FactorBosch OMC Object: PCBosch OMC AUI: SQWFBosch OMC Comments: -Long Description: This parameter specifies the weight of full-set quality measurements with

respect to sub-set quality measurements in the averaging process. Theeffective averaging period is reduced by the weighting factor if DTX(discontinuous transmission) is not active. If DTX is used, the powermeasurements are not very reliable.W_QUAL_PC and A_QUAL_PC should be considered together to get ameaningful averaging period.




215

214 ANNEX AA.1 Mapping: Object/AUI -> GUI

and GSM Name

Object AUI GUI GSM NameACC / accCard ROMMODNAME,

ROMREVCODE,ROMUPDTIME, TYPE

Interface Card Type, ROM Update Time, ROMModule Name, ROM Revision Code

ACC Card Version

ACCE1PORT CLKSOURCE Clock Source ACC Clock SourceACCE1PORT DATAENCODE Data Encoding ACC Data EncodingACCE1PORT FRAMEMODE Frame Mode ACC Frame ModeACCE1PORT PORTMODE Port Mode ACC Port ModeADJCELL BCCH BCCH Frequency ARFCN_NC(n)ADJCELL BSIDBCC BS Identity Code: BCC BCC_NC(n)ADJCELL BSIDNCC BS Identity Code: NCC NCC_NC(n)ADJCELL CELLID Cell Global Identity: Cell Identification CI_NC(n)ADJCELL CELLTYPE Cell Type CELL_TYPE_NC(n)ADJCELL HOMGRN Handover Margin HO_MARGIN(0,n)ADJCELL LAIDLAC Cell Global Identity: Location Area: LAC LAC_NC(n)ADJCELL LAIDMCC Cell Global Identity: Location Area: MCC MCC_NC(n)ADJCELL LAIDMNC Cell Global Identity: Location Area: MNC MNC_NC(n)ADJCELL LINKFACT Link Factor LINKfactor(0,n)ADJCELL MSTXMAX MS Tx Power Maximum Cell MS_TXPWR_MAX(n)ADJCELL RXMIN MS Rx Level Minimum Cell RXLEV_MIN(n)ADJCELL SYNCID Synchronized / Synch Identification SYNC_NC(n,0)ADJCELL TIMEADV Predict Time Advance PTA_HO(n,0)ADJRES BCCH BCCH Frequency BCCH_ARFCN_NC(n)BCON E1ALLOC Available E1 Allocation Port E1Allocation(BCON)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T1 T1 (MAP-Timer)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T10 T10 (MAP-Timer)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T11 T11 (MAP-Timer)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T13 T13 (MAP-Timer)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T17 T17 (MAP-Timer)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T18 T18 (MAP-Timer)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T19 T19 (MAP-Timer)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T4 T4 (MAP-Timer)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T7 T7 (MAP-Timer)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T8 T8 (MAP-Timer)BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: Tqho T_qho (MAP-Timer)BSC DTCTIMER (-Vx, -Ux) BSS MAP Timer in BSS DTC: TIho T7_IHOBSC DTCTIMER (-Vx, -Ux) BSS MAP Timer in BSS DTC: Trr3 Trr3 (MAP-Timer)BSC DTCTIMER (-Vx, -Ux) BSS MAP Timer in BSS DTC: Trr5 Trr5 (MAP-Timer)BSC MEMAVAIL Memory Available Memory AvailabilityBSC PLMN PLMN Permitted PLMN_PERMITTEDBSC PREFCELLS Number of Preferred Cells n (N_TARGET_CELL)BSC TRANSCODE BSS Transcoding Capability Transcoding CapabilityBTC CLKINP0, CLKINP1 LIC Data: Clocking Input LIC-Clock-Input (n)BTC LIC0, LIC1 LIC Data: Lic Number LIC-Number (n)BTC LICALRMMSK0,

LICALRMMSK1LIC Data: Alarm Mask LIC-Alarm Mask (n)

BTC LICFEP0, LICFEP1 LIC Data: Front End Point LIC-Position (n)BTC PCMPORTA0,

PCMPORTA1LIC Data: PCM Port A LIC-Input-Line A (n)

BTC PCMPORTB0,PCMPORTB1

LIC Data: PCM Port B LIC-Input-Line B (n)

BTC RACK0, RACK1 LIC Data: Rack Number LIC-Rack (n)BTC-ARU ALRMSTATEx Alarm State Alarm State (n)BTC-ARU ERRORIDx Error Id Ext. Error Id (n)BTC-ARU HYSTTIMEx Hysteresis Time Input Hysterese (n)BTC-ARU SCANPOINTx Input Point Input Point Adr (n)BTC-LAPD ABISSPL2SP ABIS SigSlot Info: EXTC ID Serviceprovider L2 (BTC)BTC-LAPD ABISSPPGID ABIS SigSlot Info: PG ID Serviceprovider PPC (BTC)




Object AUI GUI GSM NameBTC-LAPD SIGPCM, SIGSLOT ABIS SigSlot Info: PCM System / Slot Number Sign.-Slot BTCBTS ACCCLASSBAR Access Class Overload Control: Barring

EnabledEN_ACC_BARRING

BTS ACCESSCLASS Not Allowed Access Classes AC_CNBTS AIRTIMER (-Vx, -Ux) (i.e.

AIRTIMERV1,AIRTIMERU1)

Air Timer: T3101 T3101 (Um-Timer)

BTS AIRTIMER (-Vx, -Ux) (i.e.AIRTIMERV11,AIRTIMERU11)






BTS BARSEQ10_15 Access Class Overload Control: Classes 10 to15: Bar Sequence

Barring Sequence

BTS BARSTEP0_9 Access Class Overload Control: Classes 0 to9: Bar Step Size

M1

BTS BARSTEP10_15 Access Class Overload Control: Classes 10 to15: Bar Step Size

N1

BTS BCCH BCCH Frequency BCCH_FREQBTS BLKACCGRNT No. of Blocks For Access Grant BS_AG_BLKS_RESBTS BSIDBCC BS Identity Code: BCC BCC (in BSIC)BTS BSIDNCC BS Identity Code: NCC NCC (in BSIC)BTS C2ENABLE Cell Reselection: C2 Criterion CELL_RESELECT_PARAM_I

NDBTS CALLREESTB Call Reestablishment Allowed REBTS CCCHWSDCH CCCH Combined with SDCCH CCCH_COMB_WITH_SDCCHBTS CELLALLOC Cell Allocation CA_ARFCNBTS CELLBAR Cell Barred CELL_BAR_ACCESSBTS CELLBARQ Cell Reselection: Cell Bar Qualify CELL_BAR_QUALIFYBTS CELLID Cell Global Identity: Cell Identification CI (in CGI)BTS CELLOFF Cell Reselection: Cell Offset CELL_RES_OFFSETBTS CELLRESELHYST Cell Reselect Hysteresis CELL_RESELECT_HYST.BTS CELLTYPE Cell Type CELL_TYPEBTS DTX DTX: Uplink DTXBTS DTXDATA DTX: Downlink Data Downlink DTX DataBTS DTXSP DTX: Downlink Speech Downlink DTX SpeechBTS HOPMODE Hopping Mode Hopping ModeBTS INTVMSLOCUPD Timer Periodic Update MS T3212BTS LAIDLAC Cell Global Identity: Location Area: LAC LAC (in LAI)BTS LAIDMCC Cell Global Identity: Location Area: MCC MCC (in LAI)BTS LAIDMNC Cell Global Identity: Location Area: MNC MNC (in LAI)BTS LOADIND Load Indication Enabled EN_CCCH_LOAD_INDBTS MAXRETRAN Max Number Retransmission MAX_RETRANSBTS MSTXMAXCCH MS Tx Power Maximum CCH MS_TXPWR_MAX_CCHBTS MULTIBREP Multiband Reporting MULTIBAND_REPORTINGBTS MULTIFRMPG No. Of Multiframes Between Paging BS_PA_MFRMSBTS NOCCCH Number of CCCH No. of CCCHBTS NOSLOTTRSP No. of Slots Spread Transmission TX_INTEGERBTS PENTIME Cell Reselection: Penalty Time PENALTY_TIMEBTS PRDBTSUNDEF,

PRDBTSBTS Position, Predecessor Cell BTS-Abis-Position

BTS PRDCCCHLDIND Period CCCH Load Indication CCCH_LOAD_IND_PERIODBTS QUEUETHRESH Queueing: Threshold Queue Entries Q_THRESHOLD_VALBTS RACHBUSYSLOT RACH Load Averaging Slots RACH_MEAS_PERIODBTS RACHBUSYTH RACH Busy Threshold RACH_BUSY_THRESBTS RADIOLKFAIL Radio Link: Fail Warning THRES_PC_RLFBTS RADIOLKTO Radio Link: Timeout RADIO_LINK_TIMEOUT

(T100)BTS RBSTYPE RBS Type RBS-TypeBTS RXLEVACC Rx Level Access Minimum RXLEV_ACCESS_MINBTS TEMPOFF Cell Reselection: Temporary Offset TEMPORARY_OFFSETBTS THRCCCHLDIND Threshold CCCH Load Indication CCCH Load Ind. Threshold

(PAGING_LOAD_THR)BTS TMINCFG Emergency Configuration Timer T_MK



217

Object AUI GUI GSM NameBTS TOTQUEUE Queueing: Total Number of Queue Entries /

Enable QueueingTOTAL_NUM_Q_PLACE_AVAIL

BTS UNBARSTEP0_9 Access Class Overload Control: Classes 0 to9: Unbar Step Size

M2

BTS UNBARSTEP10_15 Access Class Overload Control: Classes 10 to15: Unbar Step Size

N2

BTS WIMSIATTDET Allow IMSI Attach Detach ATTCCG CLKSRC Clock Source Clock_SourceCCG ISSYNC, SYNCHRON Master/Slave Mode, Sync Delay Fis_Syn_DelayCCG RDTCLKSRC Redundant Clock Source Clock_Source (Redundant)CHN CHANTYPE Channel Type CH_TYPECHN FREQHOPREL Frequency Usage Assoc. FH-SystemCHN PCM, SLOT, SUBSLOT0 ABIS TCH Slot Info Radio-/Terr. Link Asc.EXTC CARDTYPE EXTC Type EXTC-TypeEXTC PMCID PMC Allocation PMC Allocation (EXTC)FH ALLOCFREQ Mobile Allocation MA_ARFCNFH HOPSEQNO Hopping Sequence Number HSNHOCTRL ALEVHO Signal Strength: Averaging Period A_LEV_HOHOCTRL AQUALHO Signal Quality: Averaging Period A_QUAL_HOHOCTRL DISTAVGPER Distance: Averaging Period A_DIST_HOHOCTRL FREEFAC Cell Order Criterion: Free Factor FREEfactor_X (X=1..5)HOCTRL FREELEV Cell Order Criterion: Free Level FREElevel_X (X=1..4)HOCTRL IAPERIOD Interference Averaging: Period INTAVEHOCTRL IATHRESH0 -

IATHRESH4Interference Averaging: Thresholds INT_BOUND_X

HOCTRL IDLECHNSUPV Enable Idle Channel Supervision EN_RF_RES_INDHOCTRL INCOMHO Enable Handover: Incoming EN_INCOM_HOHOCTRL INTERDEC Enable Handover: Intercell Decision EN_BSS_HOHOCTRL INTERHO Enable Handover: Internal Inter-Cell EN_INTER_HOHOCTRL INTRAHO Enable Handover: Internal Intra-Cell EN_INTRA_HOHOCTRL LOADREG Enable Handover: Load Regard EN_LOAD_REGARDHOCTRL LOWSLOW HO from Lower Cell/for Slower MS C_MICRO_DELAYED_HOHOCTRL LRXLEVDLH Signal Strength: Lower Downlink Limit L_RXLEV_DL_HHOCTRL LRXLEVULH Signal Strength: Lower Uplink Limit L_RXLEV_UL_HHOCTRL LRXQUALDLH Signal Quality: Lower Downlink Limit L_RXQUAL_DL_HHOCTRL LRXQUALULH Signal Quality: Lower Uplink Limit L_RXQUAL_UL_HHOCTRL MICROTHRESH HO to Higher Cell/for Faster MS C_MICRO_HOHOCTRL MSDITPROC Enable Handover: Optional MS Distance EN_DIST_HOHOCTRL MSRANGEMX Distance: MS Range Maximum MS_DIST_MAXHOCTRL MSTXMAXTCH MS Tx Power Maximum MS_TXPWR_MAXHOCTRL PWRACAVG Adjacent Cell Averaging Period A_LEV_NCHOCTRL PWRBGAVG Power Budget Averaging Period A_PBGT_HOHOCTRL PWRBGHO Enable Handover: Optional Power Budget EN_PBGT_HOHOCTRL RXLEVDLIH Signal Strength: Downlink Limit RXLEV_DL_IHHOCTRL RXLEVHO Enable Handover: Rx Level EN_RXLEV_HOHOCTRL RXLEVULIH Signal Strength: Uplink Limit RXLEV_UL_IHHOCTRL RXQUALHO Enable Handover: Rx Quality EN_RXQUAL_HOHOCTRL SDCCHHO Enable Handover: SDCCH EN_SDCCH_HOHOCTRL SDCCHTCHHO Enable Handover: SDCCHTCH EN_SDCCH_TCH_HOHOCTRL TIMSDCCHHO SDCCH HO Time Allowed T_SDCCH_HO_ALLOWEDHOCTRL UMBHYST Umbrella Cell Hysteresis UMBRELLA_MICRO_HYSTHOCTRL UMBTHRESH Umbrella Cell Threshold C_UMBRELLA_MICRO_HOHOCTRL WQUALHO Signal Quality: Weighting Factor W_QUAL_HOLINK SLC Signalling Link Code Signalling Link CodeLINK SLCDN SLC Service Provider: SLC Id Link Servicepr. SLCLINK STCDN SLC Service Provider: STC Id Link Servicepr. STCLINK TRCPROV TRC Service Provider TRC Service ProviderLSET DPC Signaling Point Code SPC_MSCLSET NI Network Indicator NI_MSCMCON E1ALLOC Available E1 Allocation Port E1Allocation(MCON)OPC NI Network Indicator NI_BSCOPC OPC Signaling Point Code SPC_BSCPG MINRSVDTS Min Reserved Signal Timeslots SigSlotsReservedPG PGTYPE PG Type PG-TypePG PMCID PMC Allocation PMC Allocation (PG)PG SERVERNAME,

E1PORTxServer Allocation ServerAllocation




Object AUI GUI GSM NamePOWER ACKTIMEPWRCTRL Power Control Acknowledge Time P_CON_ACKPOWER ALEVPC Signal Strength: Averaging A_LEV_PCPOWER AQUALPC Signal Quality: Averaging A_QUAL_PCPOWER BSRFPWR Enable BS RF Power Control EN_BS_PCPOWER BSTXPWRRED BS Tx Power Reduction BS_TXPWR_REDPOWER LRXLEVDLP Signal Strength: Downlink Power Increase L_RXLEV_DL_PPOWER LRXLEVULP Signal Strength: Uplink Power Increase L_RXLEV_UL_PPOWER LRXQUALDLP Signal Quality: Downlink Power Increase L_RXQUAL_DL_PPOWER LRXQUALULP Signal Quality: Uplink Power Increase L_RXQUAL_UL_PPOWER MINTIMBETPWRCTRL Power Control Interval P_CON_INTERVALPOWER PWRCTRLMS Enable MS RF Power Control EN_MS_PCPOWER PWRINCRSTEP MS Tx Power Increase POW_INCR_STEP_SIZEPOWER PWRREDSTEP MS Tx Power Reduction POW_RED_STEP_SIZEPOWER URXLEVDLP Signal Strength: Downlink Power Reduction U_RXLEV_DL_PPOWER URXLEVULP Signal Strength: Uplink Power Reduction U_RXLEV_UL_PPOWER URXQUALDLP Signal Quality: Downlink Power Reduction U_RXQUAL_DL_PPOWER URXQUALULP Signal Quality: Uplink Power Reduction U_RXQUAL_UL_PPOWER WQUALPC Signal Quality: Weighting Factor W_QUAL_PCRT BACKUP Backup Capability Backup CapabilityRT DIVERSITY Diversity Diversity IndicationRT EMERGENCYRT Emergency RT NS_TRXRT FHE FHE Slice Address FHE Slice AddressRT GETUSAGE-RT Channel Usage Channel-UsageRT INITFREQ Initial Frequency INIT_FREQRT RACKNO Location: Rack No. RT Rack Id.RT SHELFNO Location: Shelf No. RT Shelf Id.RT TSC Training Sequence Code TSCRT-LAPD ABISSPL2SP ABIS SigSlot Info: EXTC ID Serviceprovider L2 (RT)RT-LAPD ABISSPPGID ABIS SigSlot Info: PG ID Serviceprovider PPC (RT)RT-LAPD SIGPCM, SIGSLOT ABIS SigSlot Info: PCM System / Slot Number Sign.-Slot RTRT-LAPD TRAFPCM, TRAFSLOT Traffic Slot Info: PCM System / Slot Number Traffic Slots RTSDFU/TCU BOARDTYPE,

FWSERIES, FWVER,SERIALNO, PACKID,ARTMASTER,HWSERIES, HWVER

Board Type, Firmware Series, FirmwareVersion, Serial Number, Pack Identifier, ArtMaster, Hardware Series, Hardware Version

SDFU/TCU Version

SDFUE1PORT ACCE1 Connected ACC E1 Connected ACC E1SDFUE1PORT CRC4 CRC4 Framing CRC 4 FramingSDFUE1PORT TYPE E1 Port Type E1 Port TypeSDU BADSEC Percentage Bad Sectors SDU bad sectorsSDU HIGHTHR Sector Threshold High SDU higher thresholdSDU LOWTHR Sector Threshold Low SDU lower thresholdSDU NRSEC No. of 'kilo' Sectors SDU No. of sectorsSERVER IPADDR IP Address IP AddressTCG CODE Transcoder Id Code: TCG Code TIC[TCG_CODE]TCG PGID PCM Service Provider: PG Id Serviceprovider PG (TCG)TCG QUART Transcoder Id Code: TCG Quartett TIC[TCGQ_CODE]TCG RACK Transcoder Id Code: TCE Rack Id TIC[TCE_CODE]TRC CIDCPCM, CIDCTS Circuit Id: PCM, TS Circuit Id Code CICTRC INPCM, INSLOT Input TRC Input SlotTRC OUTPCM, OUTSLOT,

OUTSUBSLOTOutput TRC Output Slot



219

A.2 Mapping: Object/GUI -> AUIand GSM Name

Object GUI AUI GSM NameACC / accCard Interface Card Type, ROM Update Time, ROM

Module Name, ROM Revision CodeROMMODNAME,ROMREVCODE,ROMUPDTIME, TYPE

ACC Card Version

ACCE1PORT Clock Source CLKSOURCE ACC Clock SourceACCE1PORT Data Encoding DATAENCODE ACC Data EncodingACCE1PORT Frame Mode FRAMEMODE ACC Frame ModeACCE1PORT Port Mode PORTMODE ACC Port ModeADJCELL BCCH Frequency BCCH ARFCN_NC(n)ADJCELL BS Identity Code: BCC BSIDBCC BCC_NC(n)ADJCELL BS Identity Code: NCC BSIDNCC NCC_NC(n)ADJCELL Cell Global Identity: Cell Identification CELLID CI_NC(n)ADJCELL Cell Global Identity: Location Area: LAC LAIDLAC LAC_NC(n)ADJCELL Cell Global Identity: Location Area: MCC LAIDMCC MCC_NC(n)ADJCELL Cell Global Identity: Location Area: MNC LAIDMNC MNC_NC(n)ADJCELL Cell Type CELLTYPE CELL_TYPE_NC(n)ADJCELL Handover Margin HOMGRN HO_MARGIN(0,n)ADJCELL Link Factor LINKFACT LINKfactor(0,n)ADJCELL MS Rx Level Minimum Cell RXMIN RXLEV_MIN(n)ADJCELL MS Tx Power Maximum Cell MSTXMAX MS_TXPWR_MAX(n)ADJCELL Predict Time Advance TIMEADV PTA_HO(n,0)ADJCELL Synchronized / Synch Identification SYNCID SYNC_NC(n,0)ADJRES BCCH Frequency BCCH BCCH_ARFCN_NC(n)BCON Available E1 Allocation Port E1ALLOC E1Allocation(BCON)BSC BSS MAP Timer in BSC: T1 BSCTIMER (-Vx, -Ux) T1 (MAP-Timer)BSC BSS MAP Timer in BSC: T10 BSCTIMER (-Vx, -Ux) T10 (MAP-Timer)BSC BSS MAP Timer in BSC: T11 BSCTIMER (-Vx, -Ux) T11 (MAP-Timer)BSC BSS MAP Timer in BSC: T13 BSCTIMER (-Vx, -Ux) T13 (MAP-Timer)BSC BSS MAP Timer in BSC: T17 BSCTIMER (-Vx, -Ux) T17 (MAP-Timer)BSC BSS MAP Timer in BSC: T18 BSCTIMER (-Vx, -Ux) T18 (MAP-Timer)BSC BSS MAP Timer in BSC: T19 BSCTIMER (-Vx, -Ux) T19 (MAP-Timer)BSC BSS MAP Timer in BSC: T4 BSCTIMER (-Vx, -Ux) T4 (MAP-Timer)BSC BSS MAP Timer in BSC: T7 BSCTIMER (-Vx, -Ux) T7 (MAP-Timer)BSC BSS MAP Timer in BSC: T8 BSCTIMER (-Vx, -Ux) T8 (MAP-Timer)BSC BSS MAP Timer in BSC: Tqho BSCTIMER (-Vx, -Ux) T_qho (MAP-Timer)BSC BSS MAP Timer in BSS DTC: TIho DTCTIMER (-Vx, -Ux) T7_IHOBSC BSS MAP Timer in BSS DTC: Trr3 DTCTIMER (-Vx, -Ux) Trr3 (MAP-Timer)BSC BSS MAP Timer in BSS DTC: Trr5 DTCTIMER (-Vx, -Ux) Trr5 (MAP-Timer)BSC BSS Transcoding Capability TRANSCODE Transcoding CapabilityBSC Memory Available MEMAVAIL Memory AvailabilityBSC Number of Preferred Cells PREFCELLS n (N_TARGET_CELL)BSC PLMN Permitted PLMN PLMN_PERMITTEDBTC LIC Data: Alarm Mask LICALRMMSK0,

LICALRMMSK1LIC-Alarm Mask (n)

BTC LIC Data: Clocking Input CLKINP0, CLKINP1 LIC-Clock-Input (n)BTC LIC Data: Front End Point LICFEP0, LICFEP1 LIC-Position (n)BTC LIC Data: Lic Number LIC0, LIC1 LIC-Number (n)BTC LIC Data: PCM Port A PCMPORTA0,

PCMPORTA1LIC-Input-Line A (n)

BTC LIC Data: PCM Port B PCMPORTB0,PCMPORTB1

LIC-Input-Line B (n)

BTC LIC Data: Rack Number RACK0, RACK1 LIC-Rack (n)BTC-ARU Alarm State ALRMSTATEx Alarm State (n)BTC-ARU Error Id ERRORIDx Ext. Error Id (n)BTC-ARU Hysteresis Time HYSTTIMEx Input Hysterese (n)BTC-ARU Input Point SCANPOINTx Input Point Adr (n)BTC-LAPD ABIS SigSlot Info: EXTC ID ABISSPL2SP Serviceprovider L2 (BTC)BTC-LAPD ABIS SigSlot Info: PCM System / Slot Number SIGPCM, SIGSLOT Sign.-Slot BTCBTC-LAPD ABIS SigSlot Info: PG ID ABISSPPGID Serviceprovider PPC (BTC)BTS Access Class Overload Control: Barring

EnabledACCCLASSBAR EN_ACC_BARRING

BTS Access Class Overload Control: Classes 0 to9: Bar Step Size

BARSTEP0_9 M1




Object GUI AUI GSM NameBTS Access Class Overload Control: Classes 0 to

9: Unbar Step SizeUNBARSTEP0_9 M2

BTS Access Class Overload Control: Classes 10 to15: Bar Sequence

BARSEQ10_15 Barring Sequence

BTS Access Class Overload Control: Classes 10 to15: Bar Step Size

BARSTEP10_15 N1

BTS Access Class Overload Control: Classes 10 to15: Unbar Step Size

UNBARSTEP10_15 N2

BTS Air Timer: T3101 AIRTIMER (-Vx, -Ux) (i.e.AIRTIMERV1,AIRTIMERU1)

T3101 (Um-Timer)


T3107 (Um-Timer)


T3109 (Um-Timer)


T3111 (Um-Timer)

BTS Allow IMSI Attach Detach WIMSIATTDET ATTBTS BCCH Frequency BCCH BCCH_FREQBTS BS Identity Code: BCC BSIDBCC BCC (in BSIC)BTS BS Identity Code: NCC BSIDNCC NCC (in BSIC)BTS BTS Position, Predecessor Cell PRDBTSUNDEF,

PRDBTSBTS-Abis-Position

BTS Call Reestablishment Allowed CALLREESTB REBTS CCCH Combined with SDCCH CCCHWSDCH CCCH_COMB_WITH_SDCCHBTS Cell Allocation CELLALLOC CA_ARFCNBTS Cell Barred CELLBAR CELL_BAR_ACCESSBTS Cell Global Identity: Cell Identification CELLID CI (in CGI)BTS Cell Global Identity: Location Area: LAC LAIDLAC LAC (in LAI)BTS Cell Global Identity: Location Area: MCC LAIDMCC MCC (in LAI)BTS Cell Global Identity: Location Area: MNC LAIDMNC MNC (in LAI)BTS Cell Reselect Hysteresis CELLRESELHYST CELL_RESELECT_HYST.BTS Cell Reselection: C2 Criterion C2ENABLE CELL_RESELECT_PARAM_I

NDBTS Cell Reselection: Cell Bar Qualify CELLBARQ CELL_BAR_QUALIFYBTS Cell Reselection: Cell Offset CELLOFF CELL_RES_OFFSETBTS Cell Reselection: Penalty Time PENTIME PENALTY_TIMEBTS Cell Reselection: Temporary Offset TEMPOFF TEMPORARY_OFFSETBTS Cell Type CELLTYPE CELL_TYPEBTS DTX: Downlink Data DTXDATA Downlink DTX DataBTS DTX: Downlink Speech DTXSP Downlink DTX SpeechBTS DTX: Uplink DTX DTXBTS Emergency Configuration Timer TMINCFG T_MKBTS Hopping Mode HOPMODE Hopping ModeBTS Load Indication Enabled LOADIND EN_CCCH_LOAD_INDBTS Max Number Retransmission MAXRETRAN MAX_RETRANSBTS MS Tx Power Maximum CCH MSTXMAXCCH MS_TXPWR_MAX_CCHBTS Multiband Reporting MULTIBREP MULTIBAND_REPORTINGBTS No. of Blocks For Access Grant BLKACCGRNT BS_AG_BLKS_RESBTS No. Of Multiframes Between Paging MULTIFRMPG BS_PA_MFRMSBTS No. of Slots Spread Transmission NOSLOTTRSP TX_INTEGERBTS Not Allowed Access Classes ACCESSCLASS AC_CNBTS Number of CCCH NOCCCH No. of CCCHBTS Period CCCH Load Indication PRDCCCHLDIND CCCH_LOAD_IND_PERIODBTS Queueing: Threshold Queue Entries QUEUETHRESH Q_THRESHOLD_VALBTS Queueing: Total Number of Queue Entries /

Enable QueueingTOTQUEUE TOTAL_NUM_Q_PLACE_AVA

ILBTS RACH Busy Threshold RACHBUSYTH RACH_BUSY_THRESBTS RACH Load Averaging Slots RACHBUSYSLOT RACH_MEAS_PERIODBTS Radio Link: Fail Warning RADIOLKFAIL THRES_PC_RLFBTS Radio Link: Timeout RADIOLKTO RADIO_LINK_TIMEOUT

(T100)BTS RBS Type RBSTYPE RBS-TypeBTS Rx Level Access Minimum RXLEVACC RXLEV_ACCESS_MIN



221

Object GUI AUI GSM NameBTS Threshold CCCH Load Indication THRCCCHLDIND CCCH Load Ind. Threshold

(PAGING_LOAD_THR)BTS Timer Periodic Update MS INTVMSLOCUPD T3212CCG Clock Source CLKSRC Clock_SourceCCG Master/Slave Mode, Sync Delay ISSYNC, SYNCHRON Fis_Syn_DelayCCG Redundant Clock Source RDTCLKSRC Clock_Source (Redundant)CHN ABIS TCH Slot Info PCM, SLOT, SUBSLOT0 Radio-/Terr. Link Asc.CHN Channel Type CHANTYPE CH_TYPECHN Frequency Usage FREQHOPREL Assoc. FH-SystemEXTC EXTC Type CARDTYPE EXTC-TypeEXTC PMC Allocation PMCID PMC Allocation (EXTC)FH Hopping Sequence Number HOPSEQNO HSNFH Mobile Allocation ALLOCFREQ MA_ARFCNHOCTRL Adjacent Cell Averaging Period PWRACAVG A_LEV_NCHOCTRL Cell Order Criterion: Free Factor FREEFAC FREEfactor_X (X=1..5)HOCTRL Cell Order Criterion: Free Level FREELEV FREElevel_X (X=1..4)HOCTRL Distance: Averaging Period DISTAVGPER A_DIST_HOHOCTRL Distance: MS Range Maximum MSRANGEMX MS_DIST_MAXHOCTRL Enable Handover: Incoming INCOMHO EN_INCOM_HOHOCTRL Enable Handover: Intercell Decision INTERDEC EN_BSS_HOHOCTRL Enable Handover: Internal Inter-Cell INTERHO EN_INTER_HOHOCTRL Enable Handover: Internal Intra-Cell INTRAHO EN_INTRA_HOHOCTRL Enable Handover: Load Regard LOADREG EN_LOAD_REGARDHOCTRL Enable Handover: Optional MS Distance MSDITPROC EN_DIST_HOHOCTRL Enable Handover: Optional Power Budget PWRBGHO EN_PBGT_HOHOCTRL Enable Handover: Rx Level RXLEVHO EN_RXLEV_HOHOCTRL Enable Handover: Rx Quality RXQUALHO EN_RXQUAL_HOHOCTRL Enable Handover: SDCCH SDCCHHO EN_SDCCH_HOHOCTRL Enable Handover: SDCCHTCH SDCCHTCHHO EN_SDCCH_TCH_HOHOCTRL Enable Idle Channel Supervision IDLECHNSUPV EN_RF_RES_INDHOCTRL HO from Lower Cell/for Slower MS LOWSLOW C_MICRO_DELAYED_HOHOCTRL HO to Higher Cell/for Faster MS MICROTHRESH C_MICRO_HOHOCTRL Interference Averaging: Period IAPERIOD INTAVEHOCTRL Interference Averaging: Thresholds IATHRESH0 -

IATHRESH4INT_BOUND_X

HOCTRL MS Tx Power Maximum MSTXMAXTCH MS_TXPWR_MAXHOCTRL Power Budget Averaging Period PWRBGAVG A_PBGT_HOHOCTRL SDCCH HO Time Allowed TIMSDCCHHO T_SDCCH_HO_ALLOWEDHOCTRL Signal Quality: Averaging Period AQUALHO A_QUAL_HOHOCTRL Signal Quality: Lower Downlink Limit LRXQUALDLH L_RXQUAL_DL_HHOCTRL Signal Quality: Lower Uplink Limit LRXQUALULH L_RXQUAL_UL_HHOCTRL Signal Quality: Weighting Factor WQUALHO W_QUAL_HOHOCTRL Signal Strength: Averaging Period ALEVHO A_LEV_HOHOCTRL Signal Strength: Downlink Limit RXLEVDLIH RXLEV_DL_IHHOCTRL Signal Strength: Lower Downlink Limit LRXLEVDLH L_RXLEV_DL_HHOCTRL Signal Strength: Lower Uplink Limit LRXLEVULH L_RXLEV_UL_HHOCTRL Signal Strength: Uplink Limit RXLEVULIH RXLEV_UL_IHHOCTRL Umbrella Cell Hysteresis UMBHYST UMBRELLA_MICRO_HYSTHOCTRL Umbrella Cell Threshold UMBTHRESH C_UMBRELLA_MICRO_HOLINK Signalling Link Code SLC Signalling Link CodeLINK SLC Service Provider: SLC Id SLCDN Link Servicepr. SLCLINK SLC Service Provider: STC Id STCDN Link Servicepr. STCLINK TRC Service Provider TRCPROV TRC Service ProviderLSET Network Indicator NI NI_MSCLSET Signaling Point Code DPC SPC_MSCMCON Available E1 Allocation Port E1ALLOC E1Allocation(MCON)OPC Network Indicator NI NI_BSCOPC Signaling Point Code OPC SPC_BSCPG Min Reserved Signal Timeslots MINRSVDTS SigSlotsReservedPG PG Type PGTYPE PG-TypePG PMC Allocation PMCID PMC Allocation (PG)PG Server Allocation SERVERNAME,

E1PORTxServerAllocation

POWER BS Tx Power Reduction BSTXPWRRED BS_TXPWR_REDPOWER Enable BS RF Power Control BSRFPWR EN_BS_PCPOWER Enable MS RF Power Control PWRCTRLMS EN_MS_PCPOWER MS Tx Power Increase PWRINCRSTEP POW_INCR_STEP_SIZE




Object GUI AUI GSM NamePOWER MS Tx Power Reduction PWRREDSTEP POW_RED_STEP_SIZEPOWER Power Control Acknowledge Time ACKTIMEPWRCTRL P_CON_ACKPOWER Power Control Interval MINTIMBETPWRCTRL P_CON_INTERVALPOWER Signal Quality: Averaging AQUALPC A_QUAL_PCPOWER Signal Quality: Downlink Power Increase LRXQUALDLP L_RXQUAL_DL_PPOWER Signal Quality: Downlink Power Reduction URXQUALDLP U_RXQUAL_DL_PPOWER Signal Quality: Uplink Power Increase LRXQUALULP L_RXQUAL_UL_PPOWER Signal Quality: Uplink Power Reduction URXQUALULP U_RXQUAL_UL_PPOWER Signal Quality: Weighting Factor WQUALPC W_QUAL_PCPOWER Signal Strength: Averaging ALEVPC A_LEV_PCPOWER Signal Strength: Downlink Power Increase LRXLEVDLP L_RXLEV_DL_PPOWER Signal Strength: Downlink Power Reduction URXLEVDLP U_RXLEV_DL_PPOWER Signal Strength: Uplink Power Increase LRXLEVULP L_RXLEV_UL_PPOWER Signal Strength: Uplink Power Reduction URXLEVULP U_RXLEV_UL_PRT Backup Capability BACKUP Backup CapabilityRT Channel Usage GETUSAGE-RT Channel-UsageRT Diversity DIVERSITY Diversity IndicationRT Emergency RT EMERGENCYRT NS_TRXRT FHE Slice Address FHE FHE Slice AddressRT Initial Frequency INITFREQ INIT_FREQRT Location: Rack No. RACKNO RT Rack Id.RT Location: Shelf No. SHELFNO RT Shelf Id.RT Training Sequence Code TSC TSCRT-LAPD ABIS SigSlot Info: EXTC ID ABISSPL2SP Serviceprovider L2 (RT)RT-LAPD ABIS SigSlot Info: PCM System / Slot Number SIGPCM, SIGSLOT Sign.-Slot RTRT-LAPD ABIS SigSlot Info: PG ID ABISSPPGID Serviceprovider PPC (RT)RT-LAPD Traffic Slot Info: PCM System / Slot Number TRAFPCM, TRAFSLOT Traffic Slots RTSDFU/TCU Board Type, Firmware Series, Firmware

Version, Serial Number, Pack Identifier, ArtMaster, Hardware Series, Hardware Version

BOARDTYPE,FWSERIES, FWVER,SERIALNO, PACKID,ARTMASTER,HWSERIES, HWVER

SDFU/TCU Version

SDFUE1PORT Connected ACC E1 ACCE1 Connected ACC E1SDFUE1PORT CRC4 Framing CRC4 CRC 4 FramingSDFUE1PORT E1 Port Type TYPE E1 Port TypeSDU No. of 'kilo' Sectors NRSEC SDU No. of sectorsSDU Percentage Bad Sectors BADSEC SDU bad sectorsSDU Sector Threshold High HIGHTHR SDU higher thresholdSDU Sector Threshold Low LOWTHR SDU lower thresholdSERVER IP Address IPADDR IP AddressTCG PCM Service Provider: PG Id PGID Serviceprovider PG (TCG)TCG Transcoder Id Code: TCE Rack Id RACK TIC[TCE_CODE]TCG Transcoder Id Code: TCG Code CODE TIC[TCG_CODE]TCG Transcoder Id Code: TCG Quartett QUART TIC[TCGQ_CODE]TRC Circuit Id: PCM, TS CIDCPCM, CIDCTS Circuit Id Code CICTRC Input INPCM, INSLOT TRC Input SlotTRC Output OUTPCM, OUTSLOT,

OUTSUBSLOTTRC Output Slot



223

A.3 Mapping: GSM Name ->Object, AUI and GUI

GSM Name Object AUI GUIA_DIST_HO HOCTRL DISTAVGPER Distance: Averaging PeriodA_LEV_HO HOCTRL ALEVHO Signal Strength: Averaging PeriodA_LEV_NC HOCTRL PWRACAVG Adjacent Cell Averaging PeriodA_LEV_PC POWER ALEVPC Signal Strength: AveragingA_PBGT_HO HOCTRL PWRBGAVG Power Budget Averaging PeriodA_QUAL_HO HOCTRL AQUALHO Signal Quality: Averaging PeriodA_QUAL_PC POWER AQUALPC Signal Quality: AveragingAC_CN BTS ACCESSCLASS Not Allowed Access ClassesACC Card Version ACC / accCard ROMMODNAME,

ROMREVCODE,ROMUPDTIME, TYPE

Interface Card Type, ROM Update Time, ROMModule Name, ROM Revision Code

ACC Clock Source ACCE1PORT CLKSOURCE Clock SourceACC Data Encoding ACCE1PORT DATAENCODE Data EncodingACC Frame Mode ACCE1PORT FRAMEMODE Frame ModeACC Port Mode ACCE1PORT PORTMODE Port ModeAlarm State (n) BTC-ARU ALRMSTATEx Alarm StateARFCN_NC(n) ADJCELL BCCH BCCH FrequencyAssoc. FH-System CHN FREQHOPREL Frequency UsageATT BTS WIMSIATTDET Allow IMSI Attach DetachBackup Capability RT BACKUP Backup CapabilityBarring Sequence BTS BARSEQ10_15 Access Class Overload Control: Classes 10 to

15: Bar SequenceBCC (in BSIC) BTS BSIDBCC BS Identity Code: BCCBCC_NC(n) ADJCELL BSIDBCC BS Identity Code: BCCBCCH_ARFCN_NC(n) ADJRES BCCH BCCH FrequencyBCCH_FREQ BTS BCCH BCCH FrequencyBS_AG_BLKS_RES BTS BLKACCGRNT No. of Blocks For Access GrantBS_PA_MFRMS BTS MULTIFRMPG No. Of Multiframes Between PagingBS_TXPWR_RED POWER BSTXPWRRED BS Tx Power ReductionBTS-Abis-Position BTS PRDBTSUNDEF,

PRDBTSBTS Position, Predecessor Cell

C_MICRO_DELAYED_HO HOCTRL LOWSLOW HO from Lower Cell/for Slower MSC_MICRO_HO HOCTRL MICROTHRESH HO to Higher Cell/for Faster MSC_UMBRELLA_MICRO_HO HOCTRL UMBTHRESH Umbrella Cell ThresholdCA_ARFCN BTS CELLALLOC Cell AllocationCCCH Load Ind. Threshold(PAGING_LOAD_THR)

BTS THRCCCHLDIND Threshold CCCH Load Indication

CCCH_COMB_WITH_SDCCH BTS CCCHWSDCH CCCH Combined with SDCCHCCCH_LOAD_IND_PERIOD BTS PRDCCCHLDIND Period CCCH Load IndicationCELL_BAR_ACCESS BTS CELLBAR Cell BarredCELL_BAR_QUALIFY BTS CELLBARQ Cell Reselection: Cell Bar QualifyCELL_RES_OFFSET BTS CELLOFF Cell Reselection: Cell OffsetCELL_RESELECT_HYST. BTS CELLRESELHYST Cell Reselect HysteresisCELL_RESELECT_PARAM_IND

BTS C2ENABLE Cell Reselection: C2 Criterion

CELL_TYPE BTS CELLTYPE Cell TypeCELL_TYPE_NC(n) ADJCELL CELLTYPE Cell TypeCH_TYPE CHN CHANTYPE Channel TypeChannel-Usage RT GETUSAGE-RT Channel UsageCI (in CGI) BTS CELLID Cell Global Identity: Cell IdentificationCI_NC(n) ADJCELL CELLID Cell Global Identity: Cell IdentificationCircuit Id Code CIC TRC CIDCPCM, CIDCTS Circuit Id: PCM, TSClock_Source CCG CLKSRC Clock SourceClock_Source (Redundant) CCG RDTCLKSRC Redundant Clock SourceConnected ACC E1 SDFUE1PORT ACCE1 Connected ACC E1CRC 4 Framing SDFUE1PORT CRC4 CRC4 FramingDiversity Indication RT DIVERSITY DiversityDownlink DTX Data BTS DTXDATA DTX: Downlink DataDownlink DTX Speech BTS DTXSP DTX: Downlink SpeechDTX BTS DTX DTX: UplinkE1 Port Type SDFUE1PORT TYPE E1 Port TypeE1Allocation(BCON) BCON E1ALLOC Available E1 Allocation Port




GSM Name Object AUI GUIE1Allocation(MCON) MCON E1ALLOC Available E1 Allocation PortEN_ACC_BARRING BTS ACCCLASSBAR Access Class Overload Control: Barring

EnabledEN_BS_PC POWER BSRFPWR Enable BS RF Power ControlEN_BSS_HO HOCTRL INTERDEC Enable Handover: Intercell DecisionEN_CCCH_LOAD_IND BTS LOADIND Load Indication EnabledEN_DIST_HO HOCTRL MSDITPROC Enable Handover: Optional MS DistanceEN_INCOM_HO HOCTRL INCOMHO Enable Handover: IncomingEN_INTER_HO HOCTRL INTERHO Enable Handover: Internal Inter-CellEN_INTRA_HO HOCTRL INTRAHO Enable Handover: Internal Intra-CellEN_LOAD_REGARD HOCTRL LOADREG Enable Handover: Load RegardEN_MS_PC POWER PWRCTRLMS Enable MS RF Power ControlEN_PBGT_HO HOCTRL PWRBGHO Enable Handover: Optional Power BudgetEN_RF_RES_IND HOCTRL IDLECHNSUPV Enable Idle Channel SupervisionEN_RXLEV_HO HOCTRL RXLEVHO Enable Handover: Rx LevelEN_RXQUAL_HO HOCTRL RXQUALHO Enable Handover: Rx QualityEN_SDCCH_HO HOCTRL SDCCHHO Enable Handover: SDCCHEN_SDCCH_TCH_HO HOCTRL SDCCHTCHHO Enable Handover: SDCCHTCHExt. Error Id (n) BTC-ARU ERRORIDx Error IdEXTC-Type EXTC CARDTYPE EXTC TypeFHE Slice Address RT FHE FHE Slice AddressFis_Syn_Delay CCG ISSYNC, SYNCHRON Master/Slave Mode, Sync DelayFREEfactor_X (X=1..5) HOCTRL FREEFAC Cell Order Criterion: Free FactorFREElevel_X (X=1..4) HOCTRL FREELEV Cell Order Criterion: Free LevelHO_MARGIN(0,n) ADJCELL HOMGRN Handover MarginHopping Mode BTS HOPMODE Hopping ModeHSN FH HOPSEQNO Hopping Sequence NumberINIT_FREQ RT INITFREQ Initial FrequencyInput Hysterese (n) BTC-ARU HYSTTIMEx Hysteresis TimeInput Point Adr (n) BTC-ARU SCANPOINTx Input PointINT_BOUND_X HOCTRL IATHRESH0 -

IATHRESH4Interference Averaging: Thresholds

INTAVE HOCTRL IAPERIOD Interference Averaging: PeriodIP Address SERVER IPADDR IP AddressL_RXLEV_DL_H HOCTRL LRXLEVDLH Signal Strength: Lower Downlink LimitL_RXLEV_DL_P POWER LRXLEVDLP Signal Strength: Downlink Power IncreaseL_RXLEV_UL_H HOCTRL LRXLEVULH Signal Strength: Lower Uplink LimitL_RXLEV_UL_P POWER LRXLEVULP Signal Strength: Uplink Power IncreaseL_RXQUAL_DL_H HOCTRL LRXQUALDLH Signal Quality: Lower Downlink LimitL_RXQUAL_DL_P POWER LRXQUALDLP Signal Quality: Downlink Power IncreaseL_RXQUAL_UL_H HOCTRL LRXQUALULH Signal Quality: Lower Uplink LimitL_RXQUAL_UL_P POWER LRXQUALULP Signal Quality: Uplink Power IncreaseLAC (in LAI) BTS LAIDLAC Cell Global Identity: Location Area: LACLAC_NC(n) ADJCELL LAIDLAC Cell Global Identity: Location Area: LACLIC-Alarm Mask (n) BTC LICALRMMSK0,

LICALRMMSK1LIC Data: Alarm Mask

LIC-Clock-Input (n) BTC CLKINP0, CLKINP1 LIC Data: Clocking InputLIC-Input-Line A (n) BTC PCMPORTA0,

PCMPORTA1LIC Data: PCM Port A

LIC-Input-Line B (n) BTC PCMPORTB0,PCMPORTB1

LIC Data: PCM Port B

LIC-Number (n) BTC LIC0, LIC1 LIC Data: Lic NumberLIC-Position (n) BTC LICFEP0, LICFEP1 LIC Data: Front End PointLIC-Rack (n) BTC RACK0, RACK1 LIC Data: Rack NumberLink Servicepr. SLC LINK SLCDN SLC Service Provider: SLC IdLink Servicepr. STC LINK STCDN SLC Service Provider: STC IdLINKfactor(0,n) ADJCELL LINKFACT Link FactorM1 BTS BARSTEP0_9 Access Class Overload Control: Classes 0 to

9: Bar Step SizeM2 BTS UNBARSTEP0_9 Access Class Overload Control: Classes 0 to

9: Unbar Step SizeMA_ARFCN FH ALLOCFREQ Mobile AllocationMAX_RETRANS BTS MAXRETRAN Max Number RetransmissionMCC (in LAI) BTS LAIDMCC Cell Global Identity: Location Area: MCCMCC_NC(n) ADJCELL LAIDMCC Cell Global Identity: Location Area: MCCMemory Availability BSC MEMAVAIL Memory AvailableMNC (in LAI) BTS LAIDMNC Cell Global Identity: Location Area: MNCMNC_NC(n) ADJCELL LAIDMNC Cell Global Identity: Location Area: MNC



225

GSM Name Object AUI GUIMS_DIST_MAX HOCTRL MSRANGEMX Distance: MS Range MaximumMS_TXPWR_MAX HOCTRL MSTXMAXTCH MS Tx Power MaximumMS_TXPWR_MAX(n) ADJCELL MSTXMAX MS Tx Power Maximum CellMS_TXPWR_MAX_CCH BTS MSTXMAXCCH MS Tx Power Maximum CCHMULTIBAND_REPORTING BTS MULTIBREP Multiband Reportingn (N_TARGET_CELL) BSC PREFCELLS Number of Preferred CellsN1 BTS BARSTEP10_15 Access Class Overload Control: Classes 10 to

15: Bar Step SizeN2 BTS UNBARSTEP10_15 Access Class Overload Control: Classes 10 to

15: Unbar Step SizeNCC (in BSIC) BTS BSIDNCC BS Identity Code: NCCNCC_NC(n) ADJCELL BSIDNCC BS Identity Code: NCCNI_BSC OPC NI Network IndicatorNI_MSC LSET NI Network IndicatorNo. of CCCH BTS NOCCCH Number of CCCHNS_TRX RT EMERGENCYRT Emergency RTP_CON_ACK POWER ACKTIMEPWRCTRL Power Control Acknowledge TimeP_CON_INTERVAL POWER MINTIMBETPWRCTRL Power Control IntervalPENALTY_TIME BTS PENTIME Cell Reselection: Penalty TimePG-Type PG PGTYPE PG TypePLMN_PERMITTED BSC PLMN PLMN PermittedPMC Allocation (EXTC) EXTC PMCID PMC AllocationPMC Allocation (PG) PG PMCID PMC AllocationPOW_INCR_STEP_SIZE POWER PWRINCRSTEP MS Tx Power IncreasePOW_RED_STEP_SIZE POWER PWRREDSTEP MS Tx Power ReductionPTA_HO(n,0) ADJCELL TIMEADV Predict Time AdvanceQ_THRESHOLD_VAL BTS QUEUETHRESH Queueing: Threshold Queue EntriesRACH_BUSY_THRES BTS RACHBUSYTH RACH Busy ThresholdRACH_MEAS_PERIOD BTS RACHBUSYSLOT RACH Load Averaging SlotsRadio-/Terr. Link Asc. CHN PCM, SLOT, SUBSLOT0 ABIS TCH Slot InfoRADIO_LINK_TIMEOUT(T100)

BTS RADIOLKTO Radio Link: Timeout

RBS-Type BTS RBSTYPE RBS TypeRE BTS CALLREESTB Call Reestablishment AllowedRT Rack Id. RT RACKNO Location: Rack No.RT Shelf Id. RT SHELFNO Location: Shelf No.RXLEV_ACCESS_MIN BTS RXLEVACC Rx Level Access MinimumRXLEV_DL_IH HOCTRL RXLEVDLIH Signal Strength: Downlink LimitRXLEV_MIN(n) ADJCELL RXMIN MS Rx Level Minimum CellRXLEV_UL_IH HOCTRL RXLEVULIH Signal Strength: Uplink LimitSDFU/TCU Version SDFU/TCU BOARDTYPE,

FWSERIES, FWVER,SERIALNO, PACKID,ARTMASTER,HWSERIES, HWVER

Board Type, Firmware Series, FirmwareVersion, Serial Number, Pack Identifier, ArtMaster, Hardware Series, Hardware Version

SDU bad sectors SDU BADSEC Percentage Bad SectorsSDU higher threshold SDU HIGHTHR Sector Threshold HighSDU lower threshold SDU LOWTHR Sector Threshold LowSDU No. of sectors SDU NRSEC No. of 'kilo' SectorsServerAllocation PG SERVERNAME,

E1PORTxServer Allocation

Serviceprovider L2 (BTC) BTC-LAPD ABISSPL2SP ABIS SigSlot Info: EXTC IDServiceprovider L2 (RT) RT-LAPD ABISSPL2SP ABIS SigSlot Info: EXTC IDServiceprovider PG (TCG) TCG PGID PCM Service Provider: PG IdServiceprovider PPC (BTC) BTC-LAPD ABISSPPGID ABIS SigSlot Info: PG IDServiceprovider PPC (RT) RT-LAPD ABISSPPGID ABIS SigSlot Info: PG IDSign.-Slot BTC BTC-LAPD SIGPCM, SIGSLOT ABIS SigSlot Info: PCM System / Slot NumberSign.-Slot RT RT-LAPD SIGPCM, SIGSLOT ABIS SigSlot Info: PCM System / Slot NumberSignalling Link Code LINK SLC Signalling Link CodeSigSlotsReserved PG MINRSVDTS Min Reserved Signal TimeslotsSPC_BSC OPC OPC Signaling Point CodeSPC_MSC LSET DPC Signaling Point CodeSYNC_NC(n,0) ADJCELL SYNCID Synchronized / Synch IdentificationT_MK BTS TMINCFG Emergency Configuration TimerT_qho (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: TqhoT_SDCCH_HO_ALLOWED HOCTRL TIMSDCCHHO SDCCH HO Time AllowedT1 (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T1T10 (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T10




GSM Name Object AUI GUIT11 (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T11T13 (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T13T17 (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T17T18 (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T18T19 (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T19T3101 (Um-Timer) BTS AIRTIMER (-Vx, -Ux) (i.e.

AIRTIMERV1,AIRTIMERU1)

Air Timer: T3101

T3107 (Um-Timer) BTS AIRTIMER (-Vx, -Ux) (i.e.AIRTIMERV7,AIRTIMERU7)

Air Timer: T3107


Air Timer: T3109


Air Timer: T3111

T3212 BTS INTVMSLOCUPD Timer Periodic Update MST4 (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T4T7 (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T7T7_IHO BSC DTCTIMER (-Vx, -Ux) BSS MAP Timer in BSS DTC: TIhoT8 (MAP-Timer) BSC BSCTIMER (-Vx, -Ux) BSS MAP Timer in BSC: T8TEMPORARY_OFFSET BTS TEMPOFF Cell Reselection: Temporary OffsetTHRES_PC_RLF BTS RADIOLKFAIL Radio Link: Fail WarningTIC[TCE_CODE] TCG RACK Transcoder Id Code: TCE Rack IdTIC[TCG_CODE] TCG CODE Transcoder Id Code: TCG CodeTIC[TCGQ_CODE] TCG QUART Transcoder Id Code: TCG QuartettTOTAL_NUM_Q_PLACE_AVAIL

BTS TOTQUEUE Queueing: Total Number of Queue Entries /Enable Queueing

Traffic Slots RT RT-LAPD TRAFPCM, TRAFSLOT Traffic Slot Info: PCM System / Slot NumberTranscoding Capability BSC TRANSCODE BSS Transcoding CapabilityTRC Input Slot TRC INPCM, INSLOT InputTRC Output Slot TRC OUTPCM, OUTSLOT,

OUTSUBSLOTOutput

TRC Service Provider LINK TRCPROV TRC Service ProviderTrr3 (MAP-Timer) BSC DTCTIMER (-Vx, -Ux) BSS MAP Timer in BSS DTC: Trr3Trr5 (MAP-Timer) BSC DTCTIMER (-Vx, -Ux) BSS MAP Timer in BSS DTC: Trr5TSC RT TSC Training Sequence CodeTX_INTEGER BTS NOSLOTTRSP No. of Slots Spread TransmissionU_RXLEV_DL_P POWER URXLEVDLP Signal Strength: Downlink Power ReductionU_RXLEV_UL_P POWER URXLEVULP Signal Strength: Uplink Power ReductionU_RXQUAL_DL_P POWER URXQUALDLP Signal Quality: Downlink Power ReductionU_RXQUAL_UL_P POWER URXQUALULP Signal Quality: Uplink Power ReductionUMBRELLA_MICRO_HYST HOCTRL UMBHYST Umbrella Cell HysteresisW_QUAL_HO HOCTRL WQUALHO Signal Quality: Weighting FactorW_QUAL_PC POWER WQUALPC Signal Quality: Weighting Factor

Documents

59032723 GSM Parameter