Professional Documents
Culture Documents
BSS REVIEW
CHAPTER 2
SITE CONFIGURATION
CHAPTER 3
CELLS
CHAPTER 4
DEVICE/FUNCTION
EQUIPAGE
APPENDICES
GLOSSARY
ANSWERS
BSS Database
SYS02
GSR5/AG
SR
Issue 12 Rev 2
Training Manual
BSS Database
Training Manual
Issue 12 Rev 2
SYS02 GSR5/AGSR
BSS Database
Training
Manual
Issue 12 Rev 2
FOR TRAINING
PURPOSES ONLY THIS
MANUAL WILL NOT BE
UPDATED
SYS02
GSR5/
AGSR
Issue 12 Rev 2
SYS02 GSR5/AGSR
BSS Database
Issue 12 Rev 2
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license
agreement and may be used and/or disclosed only in accordance with the terms of the agreement.
Software and documentation are copyright materials. Making unauthorized copies is prohibited by
law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored
in a retrieval system, or translated into any language or computer language, in any form or by any
means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola
assumes no liability resulting from any inaccuracies or omissions in this document, or from the use
of the information obtained herein. Motorola reserves the right to make changes to any products
described herein to improve reliability, function, or design, and reserves the right to revise this
document and to make changes from time to time in content hereof with no obligation to notify any
person of revisions or changes. Motorola does not assume any liability arising out of the application
or use of any product or circuit described herein; neither does it convey license under its patent
rights of others.
Trademarks
ii
Issue 12 Rev 2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Important notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1
1
2
2
Chapter 1
BSS Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
12
12
14
16
16
16
16
18
18
110
112
112
114
116
118
118
120
Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
122
124
Initialisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
126
128
128
CM Database Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
130
132
132
134
136
138
138
140
140
140
140
140
142
iii
Issue 12 Rev 2
Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MTP L3/SCCP Preprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connectionless Manager (CLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCCP State Machine (SSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell Resource Manager (CRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Resource State Machine (RRSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Channel Interface (RCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Comparison GSM and Motorola Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
150
Chapter 2
Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
Configuring a BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
24
24
24
Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
28
210
Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipping the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212
212
214
Equipping a SITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
216
Site Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
218
Cabinet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
220
Cage Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
equip <site number> CAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
222
222
Transcoder Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
224
BSC Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
226
BTS Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
228
230
GPROC Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
232
236
Site Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
238
240
242
244
N Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
246
144
144
146
146
146
146
148
148
148
248
248
248
248
248
Issue 12 Rev 2
Physical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
250
250
250
252
HDSL SNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
254
256
258
258
260
Chapter 3
Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
Cell Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
36
Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
38
Frequency Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
310
312
PLMN Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
314
316
Cell Selection/Reselection C1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
318
BCCH Reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
320
Cell Reselection C2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Temporary_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Penalty_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
cell_bar_qualify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
322
324
324
324
C2 Reselection Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
326
328
330
MS Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
332
Extended Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
334
Periodic Updates/rr_t3212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
336
Attach/Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
338
Cell Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
340
342
Channel Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
344
Wait Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
346
Signalling Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
rr_t3101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
348
348
350
352
Issue 12 Rev 2
354
Queue Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SDCCH Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
356
356
Channel Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
358
360
SDCCH Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
362
SDCCH Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
364
366
BA Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BA Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
368
368
370
372
374
374
374
376
Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
378
378
380
alt_qual_proc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
382
384
386
Handover Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
388
MS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS Maximum Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
390
390
392
394
396
3100
3102
Discontinuous Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3104
Handover Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3106
Handovers Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3108
3110
Handovers Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Budget Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3112
3114
3116
3118
Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Incoming Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intra-Cell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inter-Cell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
353
3120
3120
3122
3122
Issue 12 Rev 2
3124
3126
Handover Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Evaluating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3128
3128
3128
3130
3132
3132
3134
Handover Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
rr_t3103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3136
3136
3138
3140
3142
3144
Timers rr_t3109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uplink Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3146
3146
3146
3148
3148
3150
Call Re-establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3152
CRM Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
dealloc_inact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ho_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3154
3154
3154
Cell Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add_cell Working Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3156
3156
3159
Chapter 4
Device/Function Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device/Function Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
41
42
44
Kilo-Port Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
KSW Extension/Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
KSW Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
410
410
414
416
418
420
420
422
422
vii
Issue 12 Rev 2
424
424
426
426
428
430
436
436
438
438
438
440
440
440
440
440
440
442
444
446
446
448
450
452
454
456
458
464
464
466
468
470
472
472
Appendix A
GSM Channel Frequency Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App Ai
Appendix B
Hexadecimal/Decimal Conversion Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App Bi
Appendix C
SACCH Multiframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App Ci
Appendix D
Database Script Building Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App Di
Appendix E
add_cell Command Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App Ei
Appendix F
Typical BSS Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App Fi
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
Glosi
Glosii
Issue 12 Rev 2
A . ..................................................................
Glosii
B . ..................................................................
Glosiv
C . ..................................................................
Glosv
D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosviii
E . ..................................................................
Glosx
F . ..................................................................
Glosxii
G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxiv
H . ..................................................................
Glosxv
I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxvi
K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxvii
L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxviii
M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxix
N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxi
O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxiii
P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxiv
Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxvi
R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxvi
S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxviii
T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxxi
U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxxiii
V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxxiii
W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxxiii
X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxxiv
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers1
C2 Reselection Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers6
ADD_CELL Working Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers9
ADD_CELL Working Area... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers11
ADD_CELL Working Area... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers13
CHANGE_ELEMENT Working Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers14
Equipage Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers15
Equipage Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers16
Equipage Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers17
Path Equipage Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers18
ix
General information
Issue 12 Rev 2
General information
Important notice
If this manual was obtained when attending a Motorola training course, it will not be
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then corrections will be supplied automatically by Motorola in the form of
General Manual Revisions (GMRs).
Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel
in the operation, installation and maintenance of the Motorola cellular infrastructure
equipment and ancillary devices. It is recommended that all personnel engaged in such
activities be properly trained by Motorola.
WARNING
Failure to comply with Motorolas operation, installation and maintenance
instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by
Motorola, although they can be used to supplement and enhance the knowledge gained
through such training.
Issue 12 Rev 2
General information
Cross references
Throughout this manual, cross references are made to the chapter numbers and section
names. The section name cross references are printed bold in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top of
each page, and are listed in the table of contents.
Text conventions
The following conventions are used in the Motorola GSM manuals to represent keyboard
input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
CR or RETURN
Issue 12 Rev 2
Do not touch the victim with your bare hands until the
electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry
insulating material and pull or push the victim clear of the
conductor.
Artificial
respiration
In the event of an electric shock it may be necessary to carry out artificial respiration.
Send for medical assistance immediately.
Burns treatment
If the patient is also suffering from burns, then, without hindrance to artificial respiration,
carry out the following:
1.
2.
3.
Whenever a safety issue arises, carry out the following procedure in all instances.
Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
1.
2.
3.
Report the problem directly to the Customer Network Resolution Centre, Swindon
+44 (0)1793 565444 or China +86 10 68437733 (telephone) and follow up with a
written report by fax, Swindon +44 (0)1793 430987 or China +86 10
68423633 (fax).
4.
Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning
labels fitted to the equipment. Warning labels must not be removed, painted over or
obscured in any way.
EMOTOROLA LTD. 2001
Issue 12 Rev 2
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single
phase or 415 V ac three phase supply which is potentially lethal. Therefore, the areas
where the ac supply power is present must not be approached until the warnings and
cautions in the text and on the equipment have been complied with.
To achieve isolation of the equipment from the ac supply, the ac input isolator must be
set to off and locked.
Within the United Kingdom (UK) regard must be paid to the requirements of the
Electricity at Work Regulations 1989. There may also be specific country legislation
which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment
when in operation. Ensure that all transmitters are switched off when any antenna
connections have to be changed. Do not key transmitters connected to unterminated
cavities or feeders.
Refer to the following standards:
S
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated fibre optic
cables connected to data in/out connectors.
Lifting
equipment
When dismantling heavy assemblies, or removing or replacing equipment, the competent
responsible person must ensure that adequate lifting facilities are available. Where
provided, lifting frames must be used for these operations. When equipments have to be
manhandled, reference must be made to the Manual Handling of Loads Regulations
1992 (UK) or to the relevant manual handling of loads legislation for the country in which
the equipment is used.
Do not ...
... substitute parts or modify equipment.
Because of the danger of introducing additional hazards, do not install substitute parts or
perform any unauthorized modification of equipment. Contact Motorola if in doubt to
ensure that safety features are maintained.
Lithium batteries
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithium
batteries must not be removed or replaced. Any boards containing defective lithium
batteries must be returned to Motorola for repair.
4
Issue 12 Rev 2
Definitions
NOTE
Observe the following cautions during operation, installation and maintenance of the
equipment described in the Motorola manuals. Failure to comply with these cautions or
with specific cautions elsewhere in the Motorola manuals may result in damage to the
equipment. Motorola assumes no liability for the customers failure to comply with these
requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution
labels fitted to the equipment. Caution labels must not be removed, painted over or
obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this
manual. These must be observed by all personnel at all times when working with the
equipment, as must any other cautions given in text, on the illustrations and on the
equipment.
Fibre optics
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge.
Although the damage caused by static discharge may not be immediately apparent,
CMOS devices may be damaged in the long term due to static discharge caused by
mishandling. Wear an approved earth strap when adjusting or handling digital boards.
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied
to the leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into
high insulation packing material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads shorted
together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into
conductive plastic foam. Provided the leads are shorted it is safe to handle the device.
Issue 12 Rev 2
Special handling
techniques
In the event of one of these devices having to be replaced, observe the following
precautions when handling the replacement:
S
Always wear an earth strap which must be connected to the electrostatic point
(ESP) on the equipment.
Leave the short circuit on the leads until the last moment. It may be necessary to
replace the conductive foam by a piece of wire to enable the device to be fitted.
Do not wear outer clothing made of nylon or similar man made material. A cotton
overall is preferable.
If possible work on an earthed metal surface. Wipe insulated plastic work surfaces
with an anti-static cloth before starting the operation.
All metal tools should be used and when not in use they should be placed on an
earthed surface.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less
susceptible to electrostatic damage. However PCBs should be handled with care,
preferably by their edges and not by their tracks and pins, they should be transferred
directly from their packing to the equipment (or the other way around) and never left
exposed on the workbench.
Chapter 1
BSS Review
Issue 12 Rev 2
ii
Issue 12 Rev 2
Chapter 1
BSS Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
12
12
14
16
16
16
16
18
18
110
112
112
114
116
118
118
120
Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
122
124
Initialisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
126
128
128
CM Database Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
130
132
132
134
136
138
138
140
140
140
140
140
142
Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MTP L3/SCCP Preprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connectionless Manager (CLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCCP State Machine (SSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell Resource Manager (CRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Resource State Machine (RRSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Channel Interface (RCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
144
144
146
146
146
146
148
148
148
iii
Issue 12 Rev 2
iv
150
BSS Review
Issue 12 Rev 2
BSS Review
Objectives
On completion of this chapter the student will be able to:
S
Air Interface
1.
2.
3.
4.
Software review
2.
State the software processes involved and how they support database
modification.
3.
Explain the function of each call processing software function and the Radio
Subsystem.
4.
Explain the difference between Mbis and GSM defined Abis and state the
advantages.
11
Issue 12 Rev 2
12
Issue 12 Rev 2
Frame 1
0
GUARD
PERIOD
Frame 2
5
TRAINING SEQUENCE
GUARD
PERIOD
NORMAL BURST
INFORMATION
INFORMATION
FLAG BITS
TAIL BITS
SYS02_Ch1_01
13
Issue 12 Rev 2
Power Control allows the operator to not only compensate for the distance from MS to
BSS, but can also cause the BSS and MS to adjust their power output to take account of
the path loss. The closer the MS is to the BSS, the less the power it and the BSS will be
required to transmit. This feature saves radio battery power at the MS, and helps to
reduce co-channel and adjacent channel interference.
Note:
GSM Recommendations state that uplink power control is mandatory, whereas downlink
power control is optional.
14
Issue 12 Rev 2
Timing Advance
Frame 2
0
Downlink
5
BSS MS
3 TS offset
Timing
Advance
Frame 1
Uplink
0
MSBSS
SYS02_Ch1_02
15
Issue 12 Rev 2
BCCH Group
The Broadcast Control Channels (BCCH) are downlink only (BSS to MS) and comprise
the following:
S
BCCH system information broadcasts allow the MS to correctly camp onto a cells
transmission. These messages also contain information concerning idle
neighbours.
CCCH Group
The Common Control Channel Group is bi-directional ie, it works in both uplink and
downlink directions.
S
Random Access Channel (RACH) is the uplink used by MSs to gain access to
the system.
Paging Channel (PCH) and Access Granted Channel (AGCH) operate in the
downlink direction. The AGCH is used to assign resources to the MS, usually a
Standalone Dedicated Control Channel (SDCCH), although a TCH can be
assigned in this way. The PCH is used by the system to page a MS. The PCH
and AGCH are never used at the same time.
DCCH Group
Dedicated Control Channels (DCCH) are assigned to a single MS to allow point to point
signalling transactions.
S
16
Issue 12 Rev 2
Control Channels
LOGICAL
CHANNELS
COMMON
CHANNELS
COMMON
CONTROL
CHANNELS
BROADCAST
CHANNELS
FCCH
SCH
BCCH
DEDICATED
CHANNELS
PCH
RACH AGCH
DEDICATED
CONTROL
CHANNELS
TRAFFIC
CHANNELS
TCH/F
TCH/H
SYS02_Ch1_03
17
Issue 12 Rev 2
1. Normal Burst:
S
Used as a reference point by the BTSs to mark timeslot zero for the mobiles.
3. Synchronization Burst:
S
Encrypted bits identifies the BSIC and the Reduced Frame Number, as defined by
GSM Recommendations 04.08.
4. Dummy Burst:
S
Should any remaining timeslots on the BCCH carrier be in an idle state then the
BTS will transmit a series of dummy bursts to maintain the required BCCH power
level.
18
The burst is of much shorter duration than the other types. The increased guard
period is necessary because the timing advance necessary for transmission to the
BTS is unknown when the MS is in an idle state.
Encrypted bits identify the cause value and the random reference as defined by
GSM Recommendations 04.08.
Issue 12 Rev 2
Frame 1
0
Frame 2
5
3
TB
Training Sequence
26
3
Encrypted Bits
39
Training Sequence
26
Fixed Bits
57
1
Encrypted Bits
36
TB
8.25
TB GP
8.25
ACCESS BURST
Synchronisation Sequence
41
8.25
TB GP
DUMMY BURST
Fixed Bits
57
8.25
TB GP
Synchronisation Sequence
64
TB GP
6
3
Encrypted Bits
57
Fixed Bits
142
TB
1
1
FREQ CORRECTION BURST (FB)
TB
TB
TB
GP
68.25
3
156.25 Bit Durations
SYS02_Ch1_04
19
Issue 12 Rev 2
The 51-frame
Control Channel
Multiframe
BCCH/CCCH
The 51-frame structure used for control channels is considerably more complex than the
26-frame structure used for the traffic channels and occurs in several forms, depending
on the type of control channel and the system operators requirements.
110
Issue 12 Rev 2
0.577ms
4.615ms
2
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Multiframe
50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
235.365mS
Time
SYS02_Ch1_05
111
Issue 12 Rev 2
112
50
50
40
S
F
40
30
S
F
C
20
S
F
Key
30
R=
B=
F=
S=
C=
I =
RACH (Random)
BCCH (Broadcast)
FCCH (Frequency)
SCH (Sync.)
CCCH (Common)
Idle
20
10
S
F
10
SYS02_Ch1_06
113
Downlink
0
S
F
Uplink
0
Issue 12 Rev 2
BCCH/CCCH Multiframe
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
Issue 12 Rev 2
114
Issue 12 Rev 2
A1
A5
A2
A6
A3
I
I
I
I
I
I
A7
D0
D0
10
D1
D1
20
D2
D2
D4
D4
D3
D5
D5
D3
D6
D6
30
D7
D7
40
A4
50
A0
DCCH Multiframe
Uplink
Key
D0
D0
D1
D1
D2
D3
D3
D2
10
D4
D5
D4
D6
D6
D5
20
D7
D7
A4
A0
30
A5
A6
A2
A1
A7
A3
40
I
I
I
50
I
I
I
D = SDCCH/8 (Dedicated)
A = SACCH/C8 (Associated)
I = Idle
Downlink
SYS02_Ch1_07
115
Issue 12 Rev 2
116
Issue 12 Rev 2
D3
R
R
R
R
D3
A0
A2
10
A1
A3
20
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
30
D0
D1
D1
D0
R
R
R
R
40
D2
50
D2
Combined Multiframe
Uplink
D0
S
F
S
F
D0
S
F
S
F
S
F
D1
D1
S
F
S
F
S
F
D2
D2
D3
D3
10
S
F
S
F
20
A2
A0
30
A3
A1
40
50
Key
R = RACH (Random)
B = BCCH (Broadcast)
F = FCCH (Frequency)
S = SCH (Sync.)
C = CCCH (Common)
D = SDCCH/4 (Dedicated)
A = SACCH/C4 (Associated)
I = Idle
Downlink
SYS02_Ch1_08
117
Issue 12 Rev 2
118
Issue 12 Rev 2
26-Frame Multiframe
0.577ms
4.615ms
2
7 6 5
4 3 2
Idle
1
1 0
7 6 5
4 3
0
2 1 0
7 6
5 4 3
2 1
SACCH
Multiframe
25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9
119.99mS
Time
SYS02_Ch1_09
119
Issue 12 Rev 2
120
Issue 12 Rev 2
MS activity
A Mobile Receives
Serving
Neighbour
C Mobile Transmits
D
B Mobile
Retunes
TDMA
0
Downlink
D
Sample
1ms
0
Mobile retunes
and listens to
Neighbour cell
and retunes to
serving cell
2ms
2
Uplink
SYS02_Ch1_10
121
Issue 12 Rev 2
Software Architecture
Software Architecture
The BSS software is made up of a number of different files called code objects.
These files are downloaded into a site by various means.
All the processors resident in a cabinet receive all the downloaded code object files,
which are stored in the RAM memory.
Each code object file has the capability of becoming a system application process, but
with certain exceptions the first being the database, the second is the executive, and
the third being the object list.
The applications created on individual processors is decided by the fault management
software during the initialisation of the site.
122
Software Architecture
Issue 12 Rev 2
BSS Software
SYS02_Ch1_11
123
Issue 12 Rev 2
The GPROC starts off in the ROM exec monitor mode. In this mode the IP
has no database to work with. Therefore it works with default values written
into the IP. At this stage the master GPROC may or may not have code, this
will be determined by checking the object list if available.
2.
The IP first initialises the LAN, so that any GPROCs may talk to one another.
On LAN initialisation, the GPROC audits the LAN to ascertain how many
GPROCs there are on the LAN.
3. The IP then decides which GPROC is to become the master. (The master
GPROC is normally a GPROC in the slot defined in the IP)
4.
The IP then tests KSWs, MSI, and XCDR boards which are defined in the IP.
5.
Then the IP must determine whether any code exists on the ANY GPROC.
6.
If code exists on a GPROC which is not the master, the Master GPROC will
arrange to load all other GPROCS from that code source, provided the code is
the same as the code held at the OMC. This is determined once the object
list that is received from the OMC is compared against the stored object list.
7.
If no code exists on the Master GPROC, download the code from an available
source.The code sources are:
a)
b)
8.
9.
124
When the Master GPROC has received all the required code, the IP on the
Master GPROC will cross-load all the other GPROCS on the LAN.
Once the Master GPROC has received confirmation from the other GPROCS
that the cross-load has been successful, a message is broadcast to all
GPROCS to go to RAM exec monitor.
Issue 12 Rev 2
Initialisation Process
In ROM
Check object list
Bring up LAN
Audit LAN for GPROCS
Determine Master GPROC
Tests selected KSW, MSI and XCDR Boards
Determine if code exists YES
Wait for OMCR connection
Check object list from OMC/BSC
Determine if code exists NO
Download code if required
a. If BSC > From OMC
b. If BTS > From BSC
Master XLoad all GPROCS
Go to RAM
SYS02_Ch1_12
125
Issue 12 Rev 2
Initialisation Process
Initialisation Process
Once in RAM the first check that is made is for a valid database, this is carried out by
calculating a checksum based on the stored database and comparing this against the
stored checksum. Although apparently correct, there may be level number differences
which will cause the download of a new database.
Now in RAM the IP once again initialises the LAN, because when moving from ROM
EMON to RAM EMON the LAN deactivates.
If no database exists, then the IP waits 45 seconds before rebooting the site and
starting the initialisation process again.
A system operator has this time period to enter the MMI Command Sysgen on. This tells
the IP software that a database is going to be provided. The IP will re-initialise the site
and go through the IP from the start, but will stop at this point. The system operator can
then provide a database. Once the database has been provided, the operator uses
another MMI command, Sysgen off, and the master GPROC will then cross-load this
new database to each GPROC on the LAN.
On completion of database crossloading to all GPROCs, the IP initiates the Central
Authority (CA) process. When this happens it is the CA process that now looks after the
initialisation of the site. The IP performs one more task if the site is a BSC it helps the
Central Authority to bring up the remote BTSs. The CA informs each BTS site its site
number then each BTS is downloaded by the BSC. The database contains information
relating to the entire BSS and is downloaded in its entirety.
Each BTS site will follow a similar IP, however these will differ between In-Cell and
M-Cell. The major exception being that unlike the BSC, a BTS has to set up its signalling
link to the BSC and not the OMC. This link is called the Radio Signalling Link (RSL) and
used for the download process.
Once the BTS has been downloaded from the BSC including the BSS database it will
activate that part of database relevant to it.
126
Initialisation Process
Issue 12 Rev 2
Initialisation Process
GPROC
In RAM
Bring up LAN
Find out if Database exists
If required, Load Database to all GPROCS
Initialise CA Process
If a BSC, work with BSC CA to bring up remote BTSs
SYS02_Ch1_13
127
Issue 12 Rev 2
128
Issue 12 Rev 2
Read Only
All Other Processes
CM
DATABASE
CM Process
Read/Write
SYS02_Ch1_14
129
Issue 12 Rev 2
CM Database Distribution
CM Database Distribution
The CM database is distributed across all active GPROCs on any particular LAN. On the
LAN, one GPROC is designated to have the master CM database and hence the CM
application process is also present on this GPROC.
If there are to be any changes to the CM database, the new information is written into the
master CM database via the CM application process. Once the CM database has
checked with other system processes, and is happy that the changes are usable, the
master CM database then broadcasts these changes to all CM databases of all GPROCs
on its particular LAN. If the CM process is at the BSC, this process will also broadcast
any changes to each BTS site.
130
CM Database Distribution
Issue 12 Rev 2
CM Database Distribution
GPROC
GPROC
GPROC
Process A
Process Y
Process B
Process C
Process Z
Database
Copy
Database
Copy
Database
Copy
CM
Master
Database
GPROC
SYS02_Ch1_15
131
Issue 12 Rev 2
2.
The changes are downloaded to the CM process from the MMI process.
3.
4.
5.
The CA replies as to whether the desired changes are possible. (Yes or No).
6.
If the CA answers yes, the CM process then broadcasts the changes to all
the CM databases of GPROCs on its site. If the answer is no, the CM
process instructs the CM database to erase the changes.
7.
The CM process uploads the outcome of the operation to the MMI process,
i.e. changes possible or not possible.
8.
With the release of GSR3 (1.5.1.0) all database change commands will only be allowed
at the BSC. At times it is necessary to update the database while visiting a site. This
can be done using rlogin to set up a remote login to a GPROC at the BSC from the BTS.
This then allows MMI commands to be entered from the BTS as though from the BSC.
132
Issue 12 Rev 2
CENTRAL
AUTHORITY
4
FROM
OMC/R
2
MMI
PROCESS
CM
PROCESS
CM
DATABASE
MASTER
GPROC
GPROC
GPROC
CM
Database
CM
Database
CM
Database
LAN
SYS02_Ch1_16
133
Issue 12 Rev 2
The OMCR downloads the proposed changes to the BSC MMI process.
2.
3.
The BSC CM process then writes the proposed changes into the BSC master
CM database. The BSC CM process also sends the proposed changes to the
BTS CM process.
4.
The BTS CM process then writes the changes into the BTS master CM
database.
5.
The BTS CM process sends the proposed changes to the CA for the BTS site.
6.
7.
8.
9.
BSC CM process then tells BSC MMI the outcome of the operation, i.e.
whether changes have been completed or not.
134
Issue 12 Rev 2
FROM
OMC/R
2
MMI
PROCESS
10
CM
PROCESS
9
CM
DATABASE
MASTER
GPROC
GPROC
CM
Database
GPROC
CM
Database
CM
Database
LAN
3
5
BTS
CENTRAL
AUTHORITY
Abis Link
6
BTS
CM
PROCESS
BTS CM
DATABASE
MASTER
GPROC
GPROC
CM
Database
GPROC
CM
Database
CM
Database
LAN
SYS02_Ch1_17
135
Issue 12 Rev 2
136
Issue 12 Rev 2
TTY
BATCH
FORMS
OMC
DETAILED VIEW
LEVEL = 5
BTS 1 = 0
BSC
BTS 2 = 1
BTS 3 = 4
BTS 1
LEVEL = 0
BTS 2
LEVEL = 1
BTS 3
LEVEL = 4
BSC
BSC
BSC
BTS 1
BTS 1
BTS 1
BTS 2
BTS 2
BTS 2
BTS 3
BTS 3
BTS 3
SYS02_Ch1_18
137
Issue 12 Rev 2
Layer 1 Interface
3.
Layer 2 Protocol
4.
5.
138
Issue 12 Rev 2
SYS02_Ch1_19
139
Issue 12 Rev 2
Layer 1 Interface
The Layer 1 process translates the message protocol used in the GPROC into the
message protocol used by the DRIM. Also, the addressing used by the higher system
layers must be translated into the actual memory location addressing used by the DRIM.
This process stacks paging messages and access granted messages until the relevant
timeslot appears on the control channels.
Layer 2 Protocol
This process is responsible for translating any signalling information for the MS received
from the MSC into GSM signalling used on the air interface on a per timeslot basis. This
process handles all LAPDm protocol messaging for the MS.
The Layer 2 is responsible for setting up the link to the MS, over the air interface, to
support the SMS data transfer, irrespective of whether the SMS is MS originated or MS
terminated.
RSS A-bis
Interface
This process is responsible for the translating of all messages generated inside the RSS
into A-bis format messages for transmission to any Layer 3 application processes. Any
messages received by this process are verified to make sure they are complete.
If the system becomes overloaded by traffic, the RSS A-bis Interface intercepts any
random access messages and automatically gives a no access message back to the
MS. This action is undertaken in response to commands from the call processing
software. When traffic becomes lower, RSS A-bis Interface allows random access
messages to proceed to call processing software.
140
Issue 12 Rev 2
To call processing
To fault management
Abis
RSS
CFM
Layer 2
HDPC
Layer 1
141
Issue 12 Rev 2
142
Issue 12 Rev 2
Functions
Controls transmission power of MS
Controls the timing advance of MS
Controls the transmission power of the BSS
Determine the need for handover
Monitors the interference level on idle channels
Detects loss of SACCH messages (conserving resources)
SYS02_Ch1_21
143
Issue 12 Rev 2
Call Processing
Call Processing
Overview
BSS call processing is a collection of Layer 3 application processes whose purpose is to
deal with the high level control of MS calls.
The call processing software is responsible for the call setup and clearing of all
MS-originated calls, as well as Mobile Switching Centre (MSC)-originated MS pages. The
BSS software undertakes all encryption tasks for the system, only over-the-air interface.
All messages on the system terrestrial links are in plain language.
Once a MS is established on a channel, be it a traffic channel or control channel, all
signalling between the MS and the MSC are transparent to the BSS software. All the
BSS software undertakes is to maintain the channel to the MS, whilst passing on any
signalling to the MS. The BSS software does not track the identity of a MS.
The decision to handover is made by CP and it chooses the target cell in response to the
choices provided by the RSS. The BSS controls all intra-cell and intra-BSS handovers,
whilst in an inter-BSS handover, the BSS informs the MSC of the MSs choices of target
cells and the MSC controls the MSs transfer to the new cell. In an intra-cell and
intra-BSS handover, the MS will remain on the same terrestrial trunk connection to the
MSC.
144
Call Processing
Issue 12 Rev 2
Call Processing
Functions
Call setup
Airinterface encryption
Control of handovers
Signalling (MSC to BSS)
(BSS to MS)
SYS02_Ch1_22
145
Issue 12 Rev 2
Call Processing
Call Processing
MTP L3/SCCP
Preprocessor
This process handles the protocol adaption of messages when transmitting or receiving
messages on the A interface. It also determines which process each message is
destined for by interrogating the message header, it then addresses the message
accordingly.
Connectionless
Manager (CLM)
The CLM deals with the global control of a BSS. This process deals with the
non-connection orientated portion of the C7 signalling.
SCCP State
Machine (SSM)
The Signalling Control Connection Part State Machine (SSM) is responsible for handling
all the connection orientated portion of the C7 Signalling.
The SCCP State Machine is responsible for co-ordinating all intra-BSS and intra-cell
handovers. It makes sure that the target cell is informed of the handover request and
ensures that a radio channel is allocated to the mobile station. This process generates all
the required messaging/signalling to co-ordinate a handover, it will also inform the MSC
when this procedure has been completed . The SCCP State Machine informs the source
cell of a successful handover in order that radio resources can be deallocated.
Switch Manager
(SM)
The function of the SM is to connect a MSs terrestrial trunk from the MSC (designated
by the MSC), to the radio channel given to a MS by the cell resource manager in the
BSS software.
146
Call Processing
Issue 12 Rev 2
MTP L3
SCCP
Preprocessor
Connectionless
Manager
(CLM)
SCCP
State Machine
(SSM)
Radio Resource
Stste Machine
(RRSM)
Radio Channel
Interface (RCI)
Switch
Manager
(SM)
Cell Resource
Manager
(CRM)
Radio
Subsystem
(RSS)
SYS02_Ch1_23
147
Issue 12 Rev 2
Call Processing
Cell Resource
Manager (CRM)
The CRM is responsible for the allocation of radio channels in response to either a MS
accessing the system or the MSC paging a MS. The CRM keeps a dynamic database
concerning the state of each of its channels, and uses the interference information
provided by the RSS to allocate the best available resource.
When the traffic loading on a BTS site or cell becomes too heavy, the CRM can instigate
flow control. The CRM tells the A-bis Interface in the RSS software to block any further
Random Access requests from MS on that cell or site. When traffic load reduces, this
flow control will be removed.
Radio Resource
State Machine
(RRSM)
The Radio Resource State Machine (RRSM) is the call processing software entity
responsible for the initiation and maintenance of physical connections.
This process is responsible for the activation of the radio channels sourced from the
CRM. When a MS no longer requires a radio channel, the RRSM is responsible for
closing the channel down.
Radio Channel
Interface (RCI)
The RCI process changes the address of a MS used in the RSS into the address used
by the Layer 3 call processing processes.
The RSS addresses MS by using its channel number, whilst the Layer 3 Call Processing
processes address messages for a MS using the SCCP reference number.
These processes can be located dependant on which form of A-bis is chosen. Under
Motorola systems these reside at the BTS cabinet.
148
Call Processing
Issue 12 Rev 2
BSC
MTL
BSP
LCF
MTPL2
MTPL3
SCCP PRE PRO
CLM
SM
HO
EVAL
SSM
LCF
LCF
MTPL2
MTPL3
SCCP PRE PRO
SSM
BTP
RRSM
RCI
DHP
RSS
MTPL3
SCCP PRE PRO
HO
EVAL
InCell
BTS
MTPL2
HO
EVAL
SSM
InCell
BTS
BTP
RRSM
RCI
CRM
DHP
RSS
MCell
BTS
DHP
RSS
DHP
MCU
RRSM
RCI
CRM
DHP
RSS
RSS
CRM
TCU
RSS
SYS02_Ch1_24
149
Issue 12 Rev 2
150
Issue 12 Rev 2
GSM System
MSC
MTP L3/SCCP
PREPROCESSOR
SCCP
State
Machine
Connectionless
Manager
Radio
Resource
State
Machine
Switch
Manager
Cell
Resource
Manager
BSC
Radio
Channel
Interface
Abis LINK
Radio
Subsystem
Radio
Subsystem
BTS
SYS02_Ch1_25
151
Issue 12 Rev 2
152
Issue 12 Rev 2
MSC
Switch
Manager
Allocation
Manager
RXCDR
ABSS
A ter interface
XBL
AXCDR
BSC
Connectionless
Manager
A bis
interface
SCCP
State
Machine
Allocation
Manager
Switch
Manager
BTS
Radio
Resource
State
Machine
Radio
Channel
Interface
Cell
Resource
Manager
Radio
Subsystem
Radio
Subsystem
SYS02_Ch1_26
153
154
Issue 12 Rev 2
Chapter 2
Site Configuration
Issue 12 Rev 2
ii
Issue 12 Rev 2
Chapter 2
Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
Configuring a BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
24
24
24
Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
28
210
Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipping the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212
212
214
Equipping a SITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
216
Site Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
218
Cabinet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
220
Cage Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
equip <site number> CAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
222
222
Transcoder Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
224
BSC Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
226
BTS Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
228
230
GPROC Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
232
236
Site Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
238
240
242
244
N Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
246
248
248
248
248
248
Physical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
250
250
250
252
HDSL SNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
254
256
258
258
260
iii
Issue 12 Rev 2
iv
Site Configuration
Issue 12 Rev 2
Site Configuration
Objectives
On completion of this chapter the student will be able to:
S
Describe typical BSS configuration and terrestrial traffic and signalling links.
Equip and understand the database fields associated with site configuration.
21
Issue 12 Rev 2
Configuring a BSS
Configuring a BSS
The flowchart on the facing page details the sequence of building a database script, the
order and content of which will change depending on its function, whether supporting
RXCDR, BSS, BSC, BTS or Path.
The parameters used to equip each type of site have changed with the upgrade to
GSR5.
Appendix 6 shows a more detailed flow chart for each script type.
22
Configuring a BSS
Issue 12 Rev 2
EQUIP CABINET
EQUIP CAGE
SITE CONFIGURATION
(CHANGE ELEMENTS)
ADD CELL [BTS/BSS ONLY]
EQUIP FUNCTIONS
SYS02_Ch2_01
23
Issue 12 Rev 2
2.
3.
4.
Supports the interface between the BSS and Mobile Switching Centre (MSC).
5.
The BSC and BTS function can be combined in a single In-Cell cabinet to form a
standalone BSS, can be co-located with its associated BTSs or the BSC can be remotely
located from the BTSs.
The Base
Transceiver
Station (BTS)
The BTS provides the Radio Frequency (RF) equipment that supports the radio path to
the mobile station (MS) and the digital control functions to support it.
24
Issue 12 Rev 2
Site 1
Site 2
BTS
BTS
LAN
Fibre Optic
cable
BTS
BSC
WITH
XCDR
Site 0
MSC
OMC
SYS02_Ch2_02
25
Issue 12 Rev 2
Transcoder
Transcoder
The transcoder (XCDR) is the digital signal processing equipment that performs GSM
defined speech encoding and decoding. The transcoding function can be performed
within the BSC or remotely, normally at the MSC location.
From GSR 5, up to 5 transcoders may support a single BSS/BSC, and a single
BSS/BSC may be connected to up to 5 transcoders.
26
Transcoder
Issue 12 Rev 2
Transcoding
MSC
OMC
OMLs
(BSC &
XCDR)
TCHs
MTLs
RXCDR
RXCDR
BSS with
Transcoding
TCHs
MTLs
XBLs
OMLs
A ter
Interface
BSC
BSC
A bis
Interface
TCHs
RSLs
BTS
BTS
BTS
BTS
SYS02_Ch2_03
27
Issue 12 Rev 2
Type A
No special user action is required to enter a Type A command or change a Type A
database parameter.
Type B
Special conditions must exist in the system when entering a Type B command or
changing a Type B database parameter. The special conditions are included in the
Operator Actions listing of each command and database parameter description.
28
Issue 12 Rev 2
Command Types
Type A
No operator actions
Type B
Special conditions exist
(refer to W23 BSS command reference manual)
29
Issue 12 Rev 2
R XCDR
SITE
0
CAB
CAGE
NETWORK IDENTITY
NUMBER
01
1 128
BSS(remote 0
0 13
0 13
1 128
BSS (local 0
transcoding)
0 13
0 13
1 128
BTS
0 13
15 2
transcoding)
1 100
210
Issue 12 Rev 2
Site Equipage
MSC
RXCDR 1 128
RXCDR 1 128
RXCDR
CAB
CAGE
CAGE
RXCDR
CAB
CAGE
CAGE
0
0
0
1
0
0
0
1
BSS 1 128
BSS 1 128
BSS
CAB
CAGE
CAGE
BSS
CAB
CAGE
0
0
0
1
0
0
0
BTS (MCell)
BTS (InCell)
SITE
CAB
CAB
CAGE
CAGE
1
0
1
15
14
BTS (InCell)
SITE
CAB
CAGE
2
0
15
BTS (MCell)
SITE
CAB
SITE
CAB
1
0
3
0
SYS02_Ch2_04
211
Issue 12 Rev 2
Site Configuration
Site Configuration
From GSR 5, RXCDR, BSS, and BTS sites will be equipped individually, defining the site
as a RXCDR, BSS or SITE where the device being equipped is a BTS.
All types of site are equipped under SYSGEN ON mode, using the equip_0_xxx
command. The 3 types of site equipage command strings are shown below and on the
following page.
For each of the RXCDR and BSS sites, an additional logical device is also now equipped:
for the RXCDR an Associate BSS (ABSS) and for the BSS an Associate XCDR
(AXCDR). The equipage of these devices follows immediately after the main device
which each supports. These Associate devices are logical representations of their parent
sites, created within the opposing site to allow the provisioning of resources (traffic
circuits from the MSC and Ater circuits between the RXCDR and BSS) so that the
system can operate in Auto Connect (dynamic) mode.
Since each RXCDR may be connected to up to 5 BSCs, and each BSC may be served
by up to 5 RXCDRs, there may be up to 5 ABSS equipped in each RXCDR, and up to 5
AXCDR equipped in each BSC.
Equipping the
RXCDR
The first line in a database script will equip the RXCDR. After the first line, additional
prompts will appear.
equip_0_abss
1st prompt (identifier)
This prompt specifies the network identity between 1 and 128 for the BSS to which the
RXCDR is connected. Note that there may be up to 5 ABSS devices equipped in a
RXCDR.
Site Configuration
Issue 12 Rev 2
Site Configuration
equip <0 or bsc> RXCDR
S
213
Issue 12 Rev 2
214
Issue 12 Rev 2
Site Configurations
215
Issue 12 Rev 2
Equipping a SITE
Equipping a SITE
The first line will equip the Site. After the first prompt, additional prompts will appear as
shown.
216
Equipping a SITE
Issue 12 Rev 2
Site Configurations
217
Issue 12 Rev 2
Site Type
Site Type
The BSS is very flexible and can have many configurations consisting of three elements;
1.
2.
3.
Transcoding
The BSC and BTS functions can be in different locations, at the same location or even
within the same cabinet.
The main processing within the BSC and BTS is performed by modules called Generic
Processors (GPROCS). The GPROCs within a BSS have to be able to communicate
with one another for BSS control, signalling and software downloading.
If the BSC and BTS are in the same location then communication is via an I.EEE 802.5
Local Area Network (LAN). If the BSC and BTS are in separate locations then
communication must be via the LAPD signalling link on the 2.048 Mbit/s links.
The site type parameter also determines other site related features. If the site type is 1
i.e. a standalone BSC, then timeslots on the TDM highway of that site will not be
allocated to digital radio interface boards as they will only be found at a BSS or BTS.
Under GSR5, the Fm_site_type is no longer entered. The type is set to the correct
value when the site type is equipped.
218
Site Type
Issue 12 Rev 2
Site Type
MSC
RXCDR
SITE TYPE 1
SITE TYPE 3
BSC
LAN
BSC
BTS
SITE TYPE 0
BSS
SITE TYPE 0
BTS
BTS
BTS
SITE TYPE 2
SITE TYPE 2
SITE TYPE 2
SYS02_Ch2_05
219
Issue 12 Rev 2
Cabinet Configuration
Cabinet Configuration
The second device to be equipped in any BSC, RXCDR, BSS ot BTS database will be
the cabinet.
equip <site number> CAB
220
Cabinet Configuration
Issue 12 Rev 2
Cabinet Configuration
equip <site number> CAB
S enter the CABINET identifiers: 0 15
S Enter the cabinet type: 0 20
10 m_cell_2
11 m_cell_6
12 tcu_2
13 tcu_6
14 m_cell_micro
15 m_cellcity
16 m_cellarena
17 horizonoffice
18 horizonmacro
19 horizonmacro_ext
20 M-Cellarena_macro
0 bts4d_48V
1 bts4d_27V
2 bssc_48V
3 bssc_27V
4 bts_dab
5 bssc_dab
6 excell_4
7 excell_6
8 topcell
9 bts_5
S Enter the frequency type: 1 31
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
PGSM
EGSM
PGSM, EGSM
DCS1800
PGSM, DCS1800
EGSM, DCS1800
PGSM, EGSM,
DCS1800
PCS1900
PGSM, PCS1900
EGSM, PCS1900
PGSM, EGSM,
PCS1900
DCS1800, PCS1900
PGSM, DCS1800,
PCS1900
EGSM, DCS1800,
PCS1900
PGSM, EGSM,
DCS1800, PCS1900
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
GSM850
PGSM, GSM850
EGSM, GSM850
PGSM, EGSM, GSM850
DCS1800, GSM850
PGSM, DCS1800, GSM850
EGSM, DCS1800, GSM850
PGSM, EGSM, DCS1800,
GSM850
PCS1900, GSM850
PGSM, PCS1900, GSM850
EGSM, PCS1900, GSM850
PGSM, EGSM, PCS1900,
GSM850
DCS1800, PCS1900, GSM850
PGSM, DCS1800, PCS1900,
GSM850
EGSM, DCS1800, PCS1900,
GSM850
PGSM, EGSM, DCS1800,
PCS1900, GSM850
221
Issue 12 Rev 2
Cage Equipage
Cage Equipage
Equipage of cages at a site is not as straightforward as that for cabinets and sites. There
are five parameters that need to be entered when equipping a cage.
equip <site
number> CAGE
1st prompt (identifier)
Up to 16 cages can be equipped at any one site being numbered from 015. Valid
identifiers for a BSC cage are 013, the first two BSC cages being number 0 and another
ID number respectively. If there is only one BSC cage it must be numbered 0 or 1.
Valid BTS identifiers for cages are 215. The first BTS at a site must be numbered either
15 or 14, conventionally 15.
The cage ID allocated must be equal to the switch setting on the LANX board in that
cage.
Note:
This device is not explicitly equipped at M-Cell sites. It is automatically equipped when
the first Base Transceiver Process (BTP) at a site is entered.
222
Cage Equipage
Issue 12 Rev 2
Cage Equipage
223
Issue 12 Rev 2
Transcoder Location
Transcoder Location
The transcoding function is to convert a 64 kbps TCH to a gross channel rate of 16 kbps.
This is necessary to minimise the required amount of RF bandwidth when the traffic data
is digitally modulated and transmitted across the air interface.
Transcoding as a function can theoretically take place either remotely (normally at the
MSC), at the BSC or BTS. Currently Motorola only support the first two options.
After transcoding has taken place it is possible to subrate multiplex four 16 kbps traffic
channels into one 64 kbps timeslot thus quadrupling the traffic channel capacity of a
2.048 Mbit/s resulting in increased efficiency.
The BSS database only has to include the location of the transcoding function.
224
Transcoder Location
Issue 12 Rev 2
Transcoder Location
30 x 64 kbs channels
30 x 16 kbs channels
XCDR
0 = Transcoding remotely
1 = Transcoding locally (BSC/CoLocated)
SYS02_Ch2_06
225
Issue 12 Rev 2
BSC Types
BSC Types
GPROCS are software machines. Their functionality is dependant upon the size or type
of site. On small size sites all of the necessary software processes to support that site
can run on one GPROC.
That GPROC becomes a certain processor type depending on whether it is at a BSC or
BTS.
As the site increases in size the software processes necessary to support the site
become too large to reside on one GPROC so some of those processes are moved onto
another GPROC creating other processor types. The site will then become another
BSC/BTS type.
The smallest BSC type is a BSC Type 0, but this is no longer supported under GSR5.
As the loading on the BSC increases, more processing will be required to support the
signalling coming into and going out of the BSC. The software processes that support
this is the Message Transfer Part (MTP) and the Signalling Connection Control Part
State Machine (SSM). These two processes are removed from the BSP and placed onto
a new device type called a Link Control Function (LCF). This is now a BSC Type 1.
The largest type of BSC is a type 2. As the amount of signalling is increased this can be
catered for by adding additional LCFs. The bottle neck will now probably be the BSP. To
reduce the load on the BSP the Operations and Maintenance System is placed on its
own processor type, the Operations and Maintenance Processor (OMP).
226
BSC Types
Issue 12 Rev 2
BSC Type 1
BSP
LCF
LCF
CLM
MTP
MTP
SM
SSM
SSM
OMS
BSC Type 2
BSP
OMF
SM
OMS
LCF
MTP
CLM
LCF
MTP
SSM
SSM
SYS02_Ch2_08
227
Issue 12 Rev 2
BTS Types
BTS Types
There are three types of BTS, types 0, 1 and 2. The smallest is a type 0 where all of the
software processes required to support the BTS are resident on one GPROC called the
Base Transceiver Processor (BTP).
As the BTS grows the RF equipment will require the most processing so the relevant
software process, the Radio Subsystem (RSS), is moved from the BTP and placed on a
new processor type, the Digital Radio Host Processor (DHP). This is a BTS type 1.
If the BTS is to grow further, a layer 3 process called the Radio Resource State Machine
is moved onto a new processor type called the Radio Signalling Link Processor (RSLP)
as that process can be allocated on an individual cell basis whereas the Cell Resource
Manager (CRM) controls a number of cells and therefore remains on the main processor.
A BTS type 2 presently does not exist in the Motorola BTS software.
This parameter is not necessary at an M-Cell site.
228
BTS Types
Issue 12 Rev 2
BTS Types
BTS Type 0
BTP
RRSM
CRM
RSS
Type 1
BTP
DHP
DHP
RSS
RSS
RRSM
CRM
Type 2
BTP
DHP
DHP
CRM
RSS
RSS
RSSM
RSSM
RSLP
RSLP
SYS02_Ch2_09
229
Issue 12 Rev 2
230
Issue 12 Rev 2
BSC/BTS types
* 0 =
BTS type 0
1 =
2 =
BSC/BTS type 1
BSC type 2
231
Issue 12 Rev 2
GPROC Slots
GPROC Slots
Data, primarily traffic, will be coming into and going out of the BSS on the 2.048 Mbit/s
links. All downlink traffic data going into the transcoder function will be serial PCM at 64
kbps and after the transcoding function will be at 16 kbps. On entering the BSS
equipment it is converted from serial to parallel and routed within the equipment via the
TDM highway.
The TDM highway is interfaced by all full sized boards with the exception of the Generic
Clocks. All boards are allocated timeslots during which to take the data off and for
putting the data on. The Kiloport Switch (KSW) provides the timeslot interchange
function.
The Generic Processor (GPROC) boards need to interface to the TDM highway for
transmitting information between the BSC and MSC (SS#7), all control and management
information from the OMC including software downloads (X.25) and all signalling between
BSC GPROCs and BTS GPROCs (LAPD) must go over the 2.048 Mbit/s links. The only
way that the GPROCs can interface to this signalling data is via the TDM highway. The
GPROC is able to support up to thirty two 64 kbps serial channels, however GPROC 1
will only support 8 or 16, GPROC 2 will support16 and 32 timeslots.
If a value of greater than 16 is entered, the operator will be warned that GPROC 2
boards are required.
232
GPROC Slots
Issue 12 Rev 2
GPROC Slots
16 or 32
233
Issue 12 Rev 2
Site Synchronisation
Site Synchronisation
For site synchronisation each site will have two Generic Clock (GCLK) modules.
All terrestrial circuits interfacing to a site will do so on standard 2.048 Mbit/s PCM links
and the GCLK is able to derive its reference from these links or alternatively free run in
case of reference failure.
The GCLK enables the site to synchronise to the 2.048 Mbit/s links so that frame and
multiframe alignment can be achieved.
Synchronisation loss thresholds can be set on both an hourly and daily basis so that
when these thresholds are reached an alarm message can be generated by the
MSI/XCDR card to the FM.
Both of these periods are chronological, i.e. if an alarm condition has been reached in the
first 10 minutes of an hour, that alarm is then locked out until the next chronological hour
begins.
The parameter sync_loss_oos provides an upper limit of sync loss alarms, upon
reading this threshold the XCDR/MSI will notify the FM which in turn will take the MMS
out of service. This threshold works on a daily basis.
If an MMS has been taken out of service as a result of the sync_loss_oos threshold
being reached, the FM will not put it back in service until the sync_loss_restore time
has expired. For this timer to activate no sync loss alarms must occur, a single sync
alarm will reset it.
234
Site Synchronisation
Issue 12 Rev 2
Sync Loss
HOURS
Alarm threshold
reached
SYS02_Ch2_10
Range 0 to 65535
235
Issue 12 Rev 2
236
Issue 12 Rev 2
Range 0 to 65535
Range 0 to 65535
237
Issue 12 Rev 2
Site Synchronization
Site Synchronization
The four parameters shown opposite are interrelated. The sync_time_oos field
indicates the permitted time that the receive leg of the 2MB link can have a prolonged
synchronization alarm. When this time is exceeded the MSI/XCDR card will inform the
FM. The FM will initiate the MMS into a state of unlocked/disabled.
The sync_time_restore field indicates the length of time that the receive leg of a 2MB
link must maintain synchronization before the MSI/XCDR card will inform the FM. The
FM will activate the MMS to a state of unlocked/enabled.
Immediately a synchronization alarm occurs on the receive leg of a 2MB the MSI/XCDR
card will set the remote alarm flag (timeslot 0) on the transmit leg. At the distant end, on
receipt of this alarm condition, the remote timer starts, if no clear indication is received
before the remote_time_oos expires then the MSI/XCDR will inform the Fault
Management (FM). The FM will initiate a state of unlocked/disabled for the MMS. The
remote_time_restore field sets the time that a remote alarm flag must be in a clear
condition before the MSI/XCDR notifies the FM. The FM will activate the MMS to a state
of unlock/enabled.
238
Site Synchronization
Issue 12 Rev 2
Site Synchronization
Direction of Traffic
Tx
remote_time_oos
remote_time_retore
Rx
Rx
sync_time_oos
sync_time_restore
Tx
Remote flag
Direction of Traffic
Remote flag
remote_time_oos
Tx
sync_time_oos
sync_time_restore
Rx
Rx
Tx
remote_time_restore
SYS02_Ch2_11
239
Issue 12 Rev 2
240
Issue 12 Rev 2
Range 0 to 65535
Range 0 to 65535
241
Issue 12 Rev 2
242
Issue 12 Rev 2
ber rate
e.g. 4= 10e4
Range 3 to 6
243
Issue 12 Rev 2
244
Issue 12 Rev 2
BER Monitoring
TIMESLOT 0 STRUCTURE
FIXED BITS
CRC
Check
EVEN
FRAMES
(FAW)
SYNC TOGGLE
I.U
REMOTE
N BIT
ALARM
I.U
5
ODD
SPARE SPARE SPARE FRAMES
(FDW)
6
7
8
FIXED BIT
I.U = International usage
SYS02_Ch2_12
245
Issue 12 Rev 2
N Bit
N Bit
It is possible to set an extra remote alarm bit, the n bit. The bit which is used for this
purpose is bit 4 of the frame data word. The actual use of this bit is specified by the
customer but the bit must be enabled using the modify_value command. Again this bit
can be enabled for all sites using the all location index, although any in-service MMSs
will not use it until they are reset.
246
N Bit
Issue 12 Rev 2
N Bit
TIMESLOT 0 STRUCTURE
I.U
1
SYNC
REMOTE
N BIT
TOGGLE ALARM
I.U
5
8
SYS02_Ch2_13
modify_value<location>nbit<*>MMS
*
0 disabled
1 enabled
247
Issue 12 Rev 2
Configurations
The HDSL interface introduced is supported on 16 (one twisted pair/loop) and 32 (two
twisted pair/loops) 64kbit/s timeslots and can be configured in the following ways:
S
By attaching external HDSL modems to the MSI of a BSC or collocated BSS site,
where the site is connected to an integrated HDSL Network Interface Unit (NIU),
as shown opposite.
HDSL alarms which report problems on, and monitor the quality of, the HDSL
interface (E1 alarms which currently exist are still supported as it is an E1 signal
being passed over the HDSL interface). HDSL alarms, for both master and slave,
are only reported by the HDSL modem which has been designated the master on
the HDSL link.
An HDSL NIU enables HDSL and E1 links to be mixed on the same HDSL NIU.
An HDSL NIU is only valid in slot 0 of a card frame. If a card frame supports an
HDSL NIU, an additional HDSL NIU cannot be equipped in slot 1.
An HDSL link can be considered as a transport mechanism for the E1 link, thus
supporting all E1 alarms and configuration parameters.
Requirements
Functionality
Constraints
248
Issue 12 Rev 2
Fig 1
BSC
Key
E1
Slave
Modem
Master
Modem
M
MCell
Fig 2
MCell
Key
S
E1
Slave
Modem
Master
Modem
HDSL
MCell
SYS02_Ch2_14
249
Issue 12 Rev 2
Physical interface
Physical interface
General
With the implementation of this feature, the following physical interface conditions and
restrictions apply:
S
The HDSL NIU can be unequipped and re-equipped to change the number of
64kbit/s timeslots supported on a span.
Daisy Chaining between M-Cell BTSs with HDSL NIUs is supported by this
feature.
Daisy Chaining between an M-Cell BTS supporting HDSL NIUs and a BSC,
collocated BSS, or M-Cell BTSs with remote modems is also supported by this
feature.
Data
With the implementation of this feature, the following initialization and configuration data
conditions and restrictions apply:
S
Initialization data required to configure the HDSL NIU interface at site initialization
is stored in MCU flash memory. If a redundant MCU is present, the HDSL settings
stored on the master MCU will be used.
At installation, the operator must set all external modems to be in the slave
configuration. The BSS software expects this configuration.
Configuration data required by the HDSL NIU interface is provided by the M-Cell
BTS at the master end of the interface. Configuration data required by the external
HDSL modem is provided by the M-Cell BTS at the master end of the interface.
Note:
The slave configuration data is stored at the master modem.
250
Physical interface
Issue 12 Rev 2
Fig 3
E1
MCell
S
Key
S
Slave
Modem
Master
Modem
M
MCell
SYS02_Ch2_15
251
Issue 12 Rev 2
252
Issue 12 Rev 2
modify_value<location>hdsl_restore_mon_period<*>
mms <MMS_ID1> <MMS_ID2>
<*>
default:
2 for hdsl_oos_mon_period
600 for hdsl_restore_mon_period
253
Issue 12 Rev 2
HDSL SNR
HDSL SNR
These parameters set the alarm thresholds for signal to noise ratio on the HDSL link.
Also, if the signal to noise ratio of the HDSL link goes below hdsl_snr_oos then the link
will be taken out of service.
The link will only be brought into service if the signal to noise ratio is above the
hdsl_snr_restore value.
For the hdsl_snr_hourly alarm, if the snr level drops below the hdsl_snr_hourly
threshold for an accumulated period of hdsl_snr_hourly_mon_period within a given 60
minute period, an hourly alarm is generated.
For the hdsl_snr_daily alarm. If the snr drops below the hdsl_snr_daily threshold for
an accumulated period of hdsl_snr_daily_mon_period within a given 24 hour period, a
daily alarm is generated
254
HDSL SNR
Issue 12 Rev 2
default values:
18 for hdsl_snr_hourly
16 for hdsl_snr_daily
14 for hdsl_snr_oos
16 for hdsl_snr_restore
255
Issue 12 Rev 2
256
Issue 12 Rev 2
257
Issue 12 Rev 2
258
Issue 12 Rev 2
chg_element synch_time_oos
chg_element synch_time_restore
chg_element remote_time_oos
chg_element remote_time_restore
chg_element synch_loss_oos
chg_element synch_loss_restore
chg_element synch_loss_daily
chg_element synch_loss_hourly
chg_element remote_loss_oos
chg_element remote_loss_restore
chg_element remote_loss_daily
chg_element remote_loss_hourly
chg_element slip_loss_oos
chg_element slip_loss_restore
chg_element slip_loss_daily
chg_element slip_loss_hourly
chg_element ber_loss daily
chg_element ber_loss_hourly
SYS02_Ch2_16a
Fibre Connectors
KSWX
KSWX
K
S
W
Cabinet 0 Cage 0
Cabinet 0 Cage 1
SYS02_Ch2_16
259
Issue 12 Rev 2
Site
Configuration
Exercise 2
Site 12 consists of a 12 carrier M-Cell6 site using the EGSM and 1800DCS RF
equipment. The Radio Signalling Link for site 12 is processed by LCF number 2 at the
BSC.
If a prolonged synchronisation alarm of 10 seconds is suffered by any 2MB terminated at
site 12 then FM should remove the link from service. If synchronization is established for
more than 5 seconds the 2MB should be restored to service. The remote values should
be consistent with the receive synchronization parameters.
If any 2MB at site 12 should lose sync more than 20 times in a 24 hour period the FM
should remove the link from service. If no synchronization alarms occur for a period of 5
seconds then the 2MB should be restored to service. The alarms associated with
synchronization losses should be triggered at 5 alarms hourly and 15 alarms daily. The
remote values should be consistent with the receive synchronization loss parameters.
Only 20 slip loses should be allowed within any 24 hour period before FM removes the
affected 2MB from service. Before FM restores the 2MB to traffic there should be no slip
losses for at least 1 minute. Slip loss conditions should generate alarms when they
exceed the following period thresholds, 2 per hour and 15 per day.
Bit error rate alarms should be generated at 10e4 on an hourly basis and 10e6 on a
daily basis.
260
Issue 12 Rev 2
#
#
BTS SITE 12
LOAD 1.6.0.0 (GSR4)
chg_element bts_type
chg_element
chg_element
chg_element
chg_element
sync_time_oos
sync_time_restore
remote_time_oos
remote_time_restore
chg_element
chg_element
chg_element
chg_element
sync_loss_oos
sync_loss_restore
sync_loss_daily
sync_loss_hourly
chg_element
chg_element
chg_element
chg_element
remote_loss_oos
remote_loss_restore
remote_loss_daily
remote_loss_hourly
chg_element
chg_element
chg_element
chg_element
chg_element
chg_element
slip_loss_oos
slip_loss_restore
slip_loss_daily
slip_loss_hourly
ber_loss_daily
ber_loss_hourly
261
Issue 12 Rev 2
262
Chapter 3
Cells
Issue 12 Rev 2
ii
Issue 12 Rev 2
Chapter 3
Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
Cell Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
36
Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
38
Frequency Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
310
312
PLMN Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
314
316
Cell Selection/Reselection C1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
318
BCCH Reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
320
Cell Reselection C2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Temporary_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Penalty_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
cell_bar_qualify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
322
324
324
324
C2 Reselection Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
326
328
330
MS Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
332
Extended Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
334
Periodic Updates/rr_t3212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
336
Attach/Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
338
Cell Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
340
342
Channel Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
344
Wait Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
346
Signalling Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
rr_t3101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
348
348
350
352
353
Assignment of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
354
Queue Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SDCCH Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
356
356
Channel Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
358
360
SDCCH Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
362
SDCCH Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
364
366
iii
Issue 12 Rev 2
BA Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BA Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signal Strength Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
370
372
374
374
374
376
Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
378
378
380
alt_qual_proc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
382
384
386
Handover Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
388
MS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS Maximum Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
390
390
392
394
396
3100
3102
Discontinuous Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3104
Handover Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3106
Handovers Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3108
3110
Handovers Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Budget Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3112
3114
3116
3118
Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Incoming Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intra-Cell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inter-Cell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3120
3120
3122
3122
3124
3126
Handover Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Evaluating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3128
3128
3128
3130
368
368
3132
3132
3134
Issue 12 Rev 2
Handover Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
rr_t3103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3136
3136
3138
3140
3142
3144
Timers rr_t3109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uplink Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3146
3146
3146
3148
3148
3150
Call Re-establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3152
CRM Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
dealloc_inact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ho_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3154
3154
3154
Cell Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add_cell Working Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3156
3156
3159
Issue 12 Rev 2
vi
Cells
Issue 12 Rev 2
Cells
Objectives
On completion of this chapter the student will be able to:
S
Equip and understand the database fields associated with adding a cell.
31
Issue 12 Rev 2
Cells
Cells
The flexibility of the BSS equipment enables each BTS site to support up to six cells.
One site could consist of a single In-Cell cabinet, ExCell or Top-Cell base Station
supporting up to three cells. The M-Cell range of BTS equipment supports one cell with
the exception of M-Cell6 which can support upto three cells per cabinet.
Each cell within the site will be allocated its own Broadcast Control Channel (BCCH),
Common Control Channel (CCCH) and Dedicated Control Channel (DCCH) and have
other database set parameters unique to that cell even though more than one cell can
exist at the same site.
Cells are configured using the add_cell command. The chg_element or
chg_cell_element commands are used to change the settings of a number of
parameters that are automatically assigned default values.
32
Cells
Issue 12 Rev 2
Cells
Site 5
Site 1
Site 4
CI = 14
CI = 15
CI = 17
CI = 6
CI = 8
CI = 16
CI = 13
CI = 9
CI = 12
CI = 10
CI = 11
CI = 7
Site 3
Site 2
SYS02_Ch3_01
33
Issue 12 Rev 2
Cell Identity
Cell Identity
Each GSM system has to be distinguishable from other GSM systems by the MS. This
is achieved by a series of codes that identify the country, network, area of the network
and finally the actual cell. This information is being transmitted by the BCCH of each
cell. When in the idle mode the MS selects the BCCH of the strongest cell and monitors
the information.
Each GSM subscriber will have a Subscriber Identity Module (SIM) and on that card will
be the International Mobile Subscriber Identity number (IMSI). Part of that number
corresponds to the country and network code of the system that the card is subscribed
to. This information is used when the subscriber tries to gain access to both its own and
other Public Land Mobile Networks (PLMN).
34
Cell Identity
Issue 12 Rev 2
Cell Identification
Mobile
Country Code
Mobile
Network Code
Location
Area Code
Cell
Identity
SYS02_Ch3_02
35
Issue 12 Rev 2
36
Issue 12 Rev 2
8
0
MCC DIG 2
Octet A
Octet B
Octet C
MCC DIG 1
MCC DIG 3
Location
Area
Identity
MNC DIG 2
0
MNC DIG 1
LAC
LAC
CI
CI
Octet D
Octet E
Octet F
Octet G
37
Issue 12 Rev 2
Command Line
Command Line
A cell is added to a site by using the add_cell command. It must be qualified with the
cell global identification followed by the site number, and optionally a cell name.
If using PGSM/EGSM and DCS1800, the data is entered in either 4 or 7 element format.
7 element format is used if the 3rd MNC digit is used.
If using PCS 1900/GSM 850, the 4 element format must be used.
The type format used is set by:
mmi_cell_id_format
Defaults
After the add_cell command is invoked a series of prompts will be presented where the
database parameters describing the cell are entered.
S
S
If a database parameter has a default value and a value outside of the parameters
valid range is entered then the default value will be used.
If the parameter does not have a default value and an out of range value is
entered the add_cell command will terminate.
38
If a parameter does not have a default, failure to enter a value in that field will also
result in the termination of the add_cell command.
Command Line
Issue 12 Rev 2
Command Line
mmi_cell_id_format <+>
0 = 7 ELEMENT
1 = 4 ELEMENT
2
2382
612
12
new cell
LAC
CI
Site ID
Cell Name
(optional)
1234
311
LAC
CI
Site ID
add_cell
MCC
MNC
MCC
1 5
MNC
SYS02_Ch3_04a
Country
MCC
MNC
China
460
01, 02
Denmark
238
01, 02
Finland
244
05, 91
France
208
01, 10
Germany
262
01, 02
Hong Kong
454
04, 00, 06
Italy
222
01
Kuwait
419
02
Lebanon
415
03, 01
Netherlands
204
08
Norway
242
01, 02
Portugal
268
01, 06
Qatar
427
01
Spain
214
07
Sweden
240
01, 07, 08
Switzerland
228
01
UAE
424
02
United Kingdom
234
10, 15
South Africa
655
Cell Name
(optional)
01, 10
SYS02_Ch3_04b
39
Issue 12 Rev 2
Frequency Type
Frequency Type
The parameter supports the multiband environment. It enables the operator to define the
frequency type on a per cell basis thereby determining the single frequency band
capability of a cell in operation.
310
Frequency Type
Issue 12 Rev 2
Frequency Type
freq_type = <*>
<*>
311
Issue 12 Rev 2
312
Issue 12 Rev 2
NCC
011 = 3
101 = 5
3 bits
NCC
BCC
3 bits
BCC
1
NCC as PLMN
BCC
NCC
10
11
12
13
14
15
16 10 17 11 18 12 19 13 20 14 21 15
24 18 25 19 26 1A 27 1B 28 1C 29 1D 30 1E 31 1F
32 20 33 21 34 22 35 23 36 24 37 25
40 28 41 29 42 2A 43 2B 44 2C 45 2D 46 2E 47 2F
48 30 49 31 50 32 51 33 52 34 53 35
56 38 57 39 58 3A 59 3B 60 3C 61 3D 62 3E 63 3F
= Decimal
22 16
38 26
54 36
23 17
39 27
55 37
= Hex
SYS02_Ch3_06
313
Issue 12 Rev 2
PLMN Allowed
PLMN Allowed
When an MS is active on an SDCCH or TCH it will start its measurement reporting
process. Before being allocated the SDCCH/TCH it will have been camped on a BCCH
receiving system information. This information would have contained a list of BCCH
frequencies that the MS was to monitor as part of its measurement reporting process.
What the MS must do is measure the Rx level for each BCCH carrier, process it and then
forward the best six reports to the BSS where it can be used for handover purposes.
In a cellular system radio channels must be reused to support the total number of
subscriber active on the system. Before the MS processes the Rx measurement taken
on a particular BCCH frequency it must identify that the one it is measuring is the correct
one and not an interferer. Each BCCH will be allocated a Base Station Identity Code
(BSIC) the first part of which consists of the Network Colour Code. The MS must decode
BSIC periodically to prove that the BCCH is the correct one and not one from a
neighbouring PLMN. The ncc_of_plmn_allowed defines the first part of the BSIC of
BCCHs on which measurement reporting can take place.
314
PLMN Allowed
Issue 12 Rev 2
PLMN Allowed
128
64
32
16
NCC = 7
NCC = 6
NCC = 5
NCC = 4
NCC = 3
NCC = 2
NCC = 1
NCC = 0
NCC = 0, 4
NCC = 1, 5
NCC = 2, 6
NCC = 3, 7
Austria
Finland
France
Greece
Iceland
Netherlands
San Marino
South Africa
Belgium
Denmark
Malta
Spain
Switzerland
Vatican
Italy
Liechtenstein
Luxembourg
Sweden
Turkey
UK
Cyprus
Germany
Ireland
Monaco
Norway
Portugal
Yugoslavia
ncc_of_plmn_allowed = <*>
* 0 255 (0 ffh)
SYS02_Ch3_07
315
Issue 12 Rev 2
316
Issue 12 Rev 2
ms_txpwr_max_cch=<*>
*
317
Issue 12 Rev 2
Cell Selection/Reselection C1
Cell Selection/Reselection C1
The MS, when not in the process of making a call, will camp on the most suitable BCCH
assuming the MS is switched on, contains a SIM card and is in the system coverage
area.
Whilst in this idle state the MS receives a list of neighbour cell frequencies broadcast on
the BCCH of the serving cell.
The MS will tune to each of these frequencies in turn, gain synchronisation and check the
following information towards a possible cell reselection.
1.
2.
3.
4.
Correct PLMN
Cell bar
Location area
P1 & P2 (C1 parameters)
Assuming the first two of these criteria are met the major factor used by the MS for cell
reselection is the perceived transmission quality between the MS and the potential cell
known as C1.
One of the major factors used by the MS for cell selection is the perceived transmission
quality between the MS and the potential cell known as C1. The criterion on which C1 is
calculated takes into account the RXLEV of the BCCH, the maximum output power of
MS and other cell specific parameters.
C1= (A Max. (B, 0))
A= RXLEV Average P1
B= P2 Max O/P Power of MS
P1 and P2 are the cell specific parameters
P1= rxlev_access_min which determines the min RXLEV required for the MS to access
the system.
P2= ms_txpwr_max_cch which determines the maximum output power at which the MS
can access the system.
The MS will only select cells of positive C1 and when a choice between cells of the same
location area has to be made the cell of best C1 is chosen.
In the formula A determines the down downlink path, and B, the uplink. To reach a
positive C1 value A must be positive, this will indicate that the received downlink power
is greater than the minimum required for that cell. If the value for B falls negative, this
indicates that the mobile is more than capable of meeting the required access power, in
this case a value of 0 is used instead. A positive value for B indicates a poorer uplink
path.
The following statement summarises this calculation:
A=
B=
318
+ value
value
value
+ value
Cell Selection/Reselection C1
Issue 12 Rev 2
Cell Selection/Reselection
C1:
A:
B:
= (A-Max (B,0))
= Rxlev Average-p1
= p2-Max RF Power of MS
p1=rxlev_access_min= <*>
0= -110 dBm
1= -109 dBm
2= -108 dBm
.
.
.
63=-47 dBm
p2=ms_txpwr_max_cch= <*>
*
for GSM900
2= 39 dBm
3= 37dBm
.
.
19= 5 dBm
for DCS1800
0= 30 dBm
1= 28 dBm
.
.
15= 0 dBm
319
Issue 12 Rev 2
BCCH Reselection
BCCH Reselection
When considering BCCH reselection from one cell to another with the same location area
the value of C1 for potential cell must be greater than that for the source cell. When the
potential cell is in another location area then the value of C1 must be greater than that of
the source cell by a database set parameter, the cell_reselect_hysteresis field.
320
BCCH Reselection
Issue 12 Rev 2
BCCH Reselection
cell_reselect_hysteresis = <*>
* 0 = 0 dB RXLEV
1 = 2 dB RXLEV
2 = 4 dB RXLEV
3 = 6 dB RXLEV
4 = 8 dB RXLEV
5 = 10 dB RXLEV
6 = 12 dB RXLEV
7 = 14 dB RXLEV
Location Area A
Location Area B
BSS
BCCH
C1 > x
BCCH
C1 = x + 4 dB
BTS
BCCH
C1 = x
BTS
SYS02_Ch3_10
321
Issue 12 Rev 2
Cell Reselection C2
Cell Reselection C2
C2 is an option GSM feature which can only be used for cell reselection, it can be
enabled or disabled on a cell basis. If C2 parameters are not being broadcast the C1
process is used for reselection. The formula below shows that C2 is firmly based on the
original C1 calculation.
C2= C1 + cell_reselect_offset temporary offset * H (penalty_time T)
(for penalty_time <31)
H= 0 if T > penalty_time
H= 1 if T < penalty_time
C2= C1 cell_reselect_offset
(for penalty_time= 31)
Whilst idle the mobile will maintain a list of the strongest 6 neighbours being monitored
from the idle ba list. This will be constantly updated and reselection parameters regularly
checked. At least every 5 seconds the MS will calculate C2 for the server and C2 for
neighbours, if the C2 for the best neighbour exceeds that of the server for a period of 5
seconds then reselection will take place. If the neighbour is in a different location area
then cell_reselect_hysteresis is also considered for the same period.
The parameters affecting C2 are broadcast on BCCH system information to an idle
mobile and are described below:
cell_reselect_param_ind
This parameter is used by CRM to determine if C2 parameters should be broadcasted or
not. In any case, this field will be broadcasted and read by the MS as the PI bit. A
phase 2 MS will read the C2 parameters, if present, and use them for reselection. A
phase 1 MS is not capable of using C2 parameters, the C1 algorithm will be used for
reselection.
cell_reselect_offset
An integer code specifies the cell_reselect_offset in dBs. This offset could be either
positive or negative depending on the value of penalty_time.
322
Cell Reselection C2
Issue 12 Rev 2
Cell Reselection C2
C2=C1+cell_reselect_offset-temporary_offset*H
(for penalty_time database value 0-30)
H = 0 if T > penalty_time
H = 1 if T penalty_time
C2
= C1 - cell_reselect_offset
(for penalty_time= 31)
cell_reselect_param_ind= <*>
cell_reselect_offset= <*>
*
323
Issue 12 Rev 2
Cell Reselection C2
Temporary_offset
This negative temporary_offset is imposed only for the duration of the penalty time, and
is then disregarded.
Penalty_time
Penalty_time is the duration for which the negative temporary_offset is considered,
and is compared with Time T in the algorithm. Time T is the length of time the MS has
maintained the neighbour in its top six measured cells. If penalty_time is set to 31 the
temporary_offset is ignored and the cell_reselect_offset becomes constantly negative.
cell_bar_qualify
cell_bar_qualify is used only in cell selection to prioritize a cell as being normal or
low priority. The MS will always select cells with normal priority providing their C1
calculation is greater than zero. Only if a normal priority cell cannot be found will a
low priority cell (providing C1 > 0) be selected.
324
Cell Reselection C2
Issue 12 Rev 2
Cell Reselection C2
C2=C1+cell_reselect_offset-temporary_offset*H
(for penalty_time database value 0-30)
H = 0 if T > penalty_time
H = 1 if T penalty_time
C2 = C1 - cell_reselect_offset
(for penalty_time= 31)
S temporary_offset= <*>
*
S penalty_time= <*>
*
S cell_bar_qualify= <*>
0 - Normal
1 - Low
EMOTOROLA LTD. 2001
325
Issue 12 Rev 2
C2 Reselection Exercise
C2 Reselection Exercise
The parameters and levels specified on the facing page are typical values experienced
by a mobile in the reselection process. Use these values to determine whether the
mobile will reselect to the neighbour cell. The mobile has been in the server well over
one hour, and the best neighbour has been in the top six measured cells for exactly 4
minutes.
WORKING AREA
SERVING (working out C1 first)
A=
R xlev Av
- P1
A=
B=
dBm
P2 - Max R F Power of MS
(P2=ms_txpwr_max_cch=
B=
dBm
C1=
dBm
C2=
dBm)
dBm
NEIGHBOUR
A=
R xlev Av
- P1
A=
B=
(P1= rxlev_access_min=
=
P2 - Max R F Power of MS
dBm)
dBm
(P2=ms_txpwr_max_cch=
B=
dBm
C1=
dBm
dBm)
dBm
C2=
FOR RESELECTION
C2 (server) < C2 (neighbour) - cell_reselect_hysteresis
326
C2 Reselection Exercise
Issue 12 Rev 2
C2 Reselection Example
S Rxlev Average
Serving= -70 dBm
Best neighbour= -63 dBm
S cell_reselect_hysteresis= 2
S Mobile power class= 2 (8w [ 39 dBm)
327
Issue 12 Rev 2
328
Issue 12 Rev 2
S ccch_conf=<*>
ccch_conf
Physical Channels
Combined
1 timeslot (0)
1 timeslot (0)
2 timeslots (0, 2)
3 timeslots (0, 2, 4)
4 timeslots (0, 2, 4, 6)
NO
YES
NO
NO
NO
(*)
0
1
2
4
6
329
Issue 12 Rev 2
330
Issue 12 Rev 2
S bs_ag_blks_res=<*>
*
Combined
CCCH Blocks
NO
NO
NO
NO
NO
NO
NO
NO
YES
YES
YES
9
9
9
9
9
9
9
9
3
3
3
AGCH Block
PCH Blocks
0
1
2
3
4
5
6
7
0
1
2
9
8
7
6
5
4
3
2
3
2
1
331
Issue 12 Rev 2
MS Paging
MS Paging
An MS is required to receive and analyse the paging messages on its paging group.
If the paging message uses the TMSI number, then four pages can be packed into one
paging group, which takes four consecutive bursts in timeslot 0 to transmit. If IMSI is
used the number of MSs that can be paged in one message is only two.
The field bs_pa_mfrms indicates the number of 51 frame multiframes between
transmission of paging messages to MS of the same group.
Therefore, the total number of paging groups per control channel is the total number of
CCCH blocks per timeslot, minus the bs_ag_blks_res multiplied by the bs_pa_mfrms
field. MS are normally required to monitor every nth block where n equals the number of
available blocks in total.
This parameter is broadcast on BCCH System Information messages and is one of the
fields used by an idle mobile along with ccch_conf, bs_ag_blks_res and the IMSI
number of the MS, to determine its paging group (formula in GSM 5.02).
332
MS Paging
Issue 12 Rev 2
bs_pa_mfrms = <*>
* 0 = 2 multiframes
1 = 3 multiframes
.
.
.
7 = 9 multiframes
Example:
ccch_conf =
0
bs_ag_blks_res = 1
bs_pa_mfrms =
2
SYS02_Ch3_16a
16
24
32
15
23
31
14
22
30
13
21
29
12
20
28
11
19
27
10
18
26
17
25
AGCH
AGCH
AGCH
AGCH
AGCH
BCCH
BCCH
BCCH
BCCH
BCCH
235.5 mS
SYS02_Ch3_16b
333
Issue 12 Rev 2
Extended Paging
Extended Paging
If there are more than four pages for a particular subgroup then the fifth through eight
pages can be packed into the next but one paging subgroup if extended paging is
permitted. The MS is informed by the page mode flag in the paging message that
extended paging has been dynamically activated. The MS will then switch on and
interrogate the next-but-one paging group ahead. Extended paging can be deactivated
by disabling this flag in the add_cell.
Any more than eight pages for a particular subgroup would not be broadcast until the
reappearance of that paging subgroup.
334
Extended Paging
Issue 12 Rev 2
MS Paging
T
M
S
I
BUFFER
2
S
F
T T T
M M M
S S S
I I I
extended_paging_active = <*>
* 0 = Normal Paging
1 = Extended Paging
BCCH
S
F
SYS02_Ch3_17
335
Issue 12 Rev 2
Periodic Updates/rr_t3212
Periodic Updates/rr_t3212
As well as performing location updates due to geographical boundaries it can be
implemented on time basis by setting rr_t3212 which governs the MS periodic location
update procedure. rr_t3212 starts when mobility management service or when mobility
management signalling is terminated and stops when mobility management service or
signalling is initiated. A value of 0 decihours indicates an infinite timeout value.
336
Periodic Updates/rr_t3212
Issue 12 Rev 2
Timers t3212
rr_t3212= <*>
* decihours
(valid range 0 to 255)
(default value 10)
337
Issue 12 Rev 2
Attach/Detach
Attach/Detach
A database field can be used to invoke system attach/detach procedures. These are
used to inform the PLMN that the MS has become active on the system or has been
deactivated either due to it being turned off or because the SIM card has been removed.
If an MS is either switched off or the SIM card is removed, assuming that the
attach_detach field is set to 1, then the MS will invoke detach procedure and send an
IMSI detach indication message to the PLMN. The PLMN will then be aware that the MS
is inactive and will not allocate resources to that MS for paging purposes.
On insertion of the SIM and/or switching the MS on it will camp onto a BCCH and read
the System Information messages. Assuming the attach/detach procedures are required
and the Location Area Identification (LAI) being sent on the BCCH is the same as that
stored in the MS as being its last LAI then the MS will generate an location update type
IMSI attach indication message.
If the LAI being received by the MS is different to that stored in its memory as being the
last known LAI then the MS will perform a location update.
338
Attach/Detach
Issue 12 Rev 2
Attach/Detach
attach_detach = <*>
* 0 = disabled
1 = enabled
BSS
MS
LAC = 126
BSS
stored LAC
= 126
Mobile rejoins
network in the
same location
area
Mobile rejoins
network in a
different
location area
Attach/Detach enabled
MS
stored LAC
= 126
LAC = 126
BSS
LAC = 126
MS
stored LAC
= 126
BSS
LAC different to last known LAC
LAC = 172
SYS02_Ch3_19
339
Issue 12 Rev 2
Cell Access
Cell Access
Cell bar information is transmitted within system information messages to an idle MS.
The network operator, via MMI, is able to completely bar access to all normal subscribers
in a particular cell, using the cell_bar_access_switch field. Barring may be
implemented when a BTS is not functioning correctly, when new cells have been
introduced into the network and being tested or when a cell is being reserved for
handover purposes only. When the cell is barred by the operator and system info reflects
this, normal MSs will not attempt to access the cell. Users of test phones may employ a
mask to override the MSs usual action upon detecting the bar. These test MSs will be
able to make calls, which will not be rejected by the BSS. Pages will still be transmitted
in cells which are barred and therefore test MS will be able to receive calls. However,
existing calls may be handed over to a cell which is barred, when the MS completes the
call in this barred cell, then re-selection will be attempted.
Cell barring is an all or nothing situation. By using the cell_bar_access_class field
access to a cell can be limited to particular classes of MS. All SIMs are allocated one of
ten access classes, referred to as access classes 09. There are five additional classes
1115 which are normally reserved for emergency services, VIPs etc. Class 10, in terms
of a subscriber class does not exist, and indeed no subscriber will have it allocated. The
cell_bar_access_class field does not stop any MS from camping on a cell but will
restrict access to those classes indicated on the BCCH and could be used to cope with
abnormally high traffic load or emergency situations. In the case of class 10 it is
unimportant which value 0 or 1 it is assigned in this bit map as this value is overwritten by
the emergency_class_switch also broadcasted to the MS.
When a cell is barred from access normal MSs will not be able to select this cell even if it
has the best signal. The MS will select the second best cell.
340
Cell Access
Issue 12 Rev 2
Cell Access
cell_bar_access_switch = <*>
cell_bar_access_class = <*>
Hexadecimal Digit
Value/Position
X
Classes Barred
15
12
10
13
11
14
6
0
1
X
X
X
X
X
X
X
X
SYS02_Ch3_20b
341
Issue 12 Rev 2
342
Issue 12 Rev 2
emergency_class_switch=<*>
343
Issue 12 Rev 2
Channel Requests
Channel Requests
An MS requests resources from a cell by transmitting an access burst containing the
channel request message. The access burst has to be scheduled so that it is
transmitted during a frame that has been configured as a RACH. This scheduling is
performed with the aid of a calculated wait period.
After the first channel request has been sent without reply, the next one is sent after a
wait period, made up of a random number of RACH slots. This wait period is in the set
(S, S+1 . . . S+T 1), where T is a value dependent on tx_integer (broadcast on BCCH
system information) and S is a preset number dependent on the value of T and
multiframe type. The table opposite shows these values which are in the firmware of the
MS.
Channel requests will only be repeated upto M+1 times where M is equal to max_retran,
broadcast on BCCH system information. After the last channel request T3126 is started
in the MS, on expiry the channel request procedure will be aborted.
344
Channel Requests
Issue 12 Rev 2
Channel Requests
MS
Channel Request
BTS
wait period
Random value in
Set (S, S + 1, . . . . . S + T 1)
Channel Request
Channel Request
Channel Request
Channel Request
M+1
New wait period
T3126
ABORT
SYS02_Ch3_22
tx_integer = <*>
valid range 0 to 15
0
3
1
4
2
5
.
.
.
.
15
50
max_retran = <*>
valid range 0 to 3
0 Max 1 Retran
1
2 Retran
2
4 Retran
3
7 Retran
Default 0
* integer code for number
of retransmissions
Value of S
T
NonComb
(RACH Slots) CCCH
3, 8, 14, 50
55
4, 9, 16
76
5, 10, 20
109
6, 11, 25
163
7, 12, 32
217
COMB
CCCH
41
52
58
86
115
SYS02_Ch3_22a
345
Issue 12 Rev 2
Wait Indication
Wait Indication
When a MS gains access to a cell with an access burst it is requesting radio resources to
perform one of the following functions:
1.
2.
Emergency call.
3.
4.
If there is not radio resources available the network may send the MS an Immediate
Assignment Reject message in unacknowledged mode on the Common Control
Channel. The message will contain the request reference and a wait indication. On
receipt of the Immediate Assignment Reject message the MS will start an internal timer
(T3122) with the indicated value taken from the wait indication information element
contained within the Immediate Assignment Reject message and returns to idle mode.
The MS is not permitted to make a new attempt to establish a radio resource connection
in the same cell until T3122 expires.
The wait_indication_parameters is set in the BSS database and is the value that the
MS will use to set T3122.
346
Wait Indication
Issue 12 Rev 2
Wait Indication
Channel Request
MS
RACH
Immediate Assignment Reject
Wait Indication 20s
MS
AGCH
MS
T3122 Expires
MS
Channel Request
RACH
Cell
MS
Cell
Cell
wait_indication_parameters = <*>
SYS02_Ch3_23
347
Issue 12 Rev 2
Signalling Establishment
Signalling Establishment
rr_t3101
An MS will request radio resources by sending a channel request message on the
RACH. The PLMN will inform the MS via the AGCH as to what resources have been
allocated and will start timer rr_t3101.
Once the main signalling link between MS and PLMN is established rr_t3101 will be
stopped. If rr_t3101 expires before the signalling link is established the newly allocated
resources will be released and the channel request message forgotten.
rr_t3101 must be set to value higher than the time necessary to set up the signalling link
between MS and PLMN.
348
Signalling Establishment
Issue 12 Rev 2
Signalling Establishment
MS
BTS
Channel Request
Immediate Assignment
RACH
AGCH
rr_t3101
L2 SABM
(L3 Initial Message)
rr_t3101 Stopped
* Time in milliseconds
Valid range 0 to 1000000
Default value 5000
SYS02_Ch3_24
349
Issue 12 Rev 2
350
Issue 12 Rev 2
interfer_bands, 0 = <*>
interfer_bands, 1 = <*>
.
.
.
interfer_bands, 4 = <*>
*
Range 0 - 63
0 = -110 dBm
1 = -109 dBm
.
.
.
63 = -47 dBm
351
Issue 12 Rev 2
Threshold
When attempting to allocate a radio channel the CRM must assign an SCCP number to
the request. Although part of this number is similar for each channel at a BTS, there is
also a unique part which is allocated by the CRM on a random basis. The threshold
parameter determines the maximum number of attempts the CRM will make to allocate
this unique part. If this number of attempts is exceeded then the call request will be
dropped and a Software Fault Management (SWFM) will be generated.
352
Issue 12 Rev 2
MTL NUMBER
RSL NUMBER
LSB
RSL NUMBER
MSB
RANDOM NUMBERS
SYS02_Ch3_26
353
Issue 12 Rev 2
Assignment of Resources
Assignment of Resources
When an MS requires the network to set up a call, the initial request for resources is sent
as an access burst on the RACH. Acknowledgement of the request will be sent via the
AGCH and the MS will then be allocated an SDCCH. Whilst on the SDCCH
authentication and validation of the subscriber and the setting of encryption normally
takes place.
If all SDCCHs are busy and SDCCH reconfiguration has reached a maximum, or is not
enabled then the operator is left with two choices. Either the initial request for resources
from the MS is rejected or it can be immediately assigned a TCH to carry out the SDCCH
process. In the case that resources are immediately assigned, a TCH in the GSM900
band will be allocated, EGSM frequencies will not be used. The immediate assignment
option is indicated in the immediate_assign_mode field in add_cell.
354
Assignment of Resources
Issue 12 Rev 2
Assignment of Resources
355
Issue 12 Rev 2
Queue Management
Queue Management
A MS requests radio resources via the Random Access Channel (RACH). It does so by
sending an access burst containing a channel request message. Assuming resources
are available the MS will be assigned one of a number of Standalone Dedicated Control
Channels (SDCCH) where the remainder of call set up procedures will take place prior to
being allocated a Traffic Channel (TCH).
It may occur that once the MS has finished on the SDCCH there may not be a TCH
available at that particular moment. The system is able to place the MS in a queue
along with other MS awaiting assignment of a TCH.
The length of the queue is dependent upon the value set in the
queue_management_information field of the BSS database. The range of this field
represents the arithmetic sum of the number of MS that can wait in a queue for the
assignment of a TCH or SDCCH. A value of 0 must be entered if queuing is not
permitted. A MS could obviously not wait for an indefinite time in this queue,
bss_map_t11 controls the maximum time the MS will wait before the request is dropped.
This parameter is used by the Cell Resource Manager (CRM), and must be aligned to
the value entered in the MSC.
This parameter must be greater that or equal to the sum of
max_q_length_full_rate_channel and max_q_length_sdcch.
SDCCH Queuing
Channel requests cannot be queued, either an SDCCH is available or not. However,
MSC originating, SDCCH handover requests can be queued, this parameter controls the
length of that queue. This parameter is more usually set to 0 as MSC SDCCH handover
requests are not common.
356
Queue Management
Issue 12 Rev 2
TCH Queueing
S
queue_management_information=<*>
max_q_length_full_rate_channel= <*>
SDCCH Queuing
S
max_q_length_sdcch= <*>
0 - 50
357
Issue 12 Rev 2
Channel Reconfiguration
Channel Reconfiguration
On initialisation the CRM ensures that each air interface timeslot is configured as per
fields set in the database.
Once the BSS is call processing the CRM is capable of dynamic channel reconfiguration.
That is, the CRM is capable of changing the mix of channel configuration. If a high
proportion of SDCCHs are in use and more SDCCH requests are received the CRM is
able to reconfigure a TCH timeslot into SDCCHs.
In the example shown timeslot 0 of carrier 0 is configured to include FCCH, SCH, BCCH,
CCCH, 4 SDCCH with 4 SACCH. Another timeslot on that carrier is configured as a full
rate TCH with FACCH and SACCH. The CRM is able to reconfigure the TCH timeslot
into 8 SDCCH + 8 SACCH giving this particular cell 12 SDCCH at the expense of one
TCH timeslot.
The channel_reconfiguration_switch field in the BSS database specifies whether the
CRM may or may not perform dynamic channel reconfiguration.
358
Channel Reconfiguration
Issue 12 Rev 2
Channel Reconfiguration
SACCH
SDCCH
CCCH
BCCH
SCH
FCCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
SACCH
SDCCH
CCCH
BCCH
SCH
FCCH
SACCH
SDCCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
TCH
SACCH
FACCH
D
*
channel_reconfiguration_switch= <*>
0=
1=
359
Issue 12 Rev 2
360
Issue 12 Rev 2
S number_sdcchs_preferred= <*>
Number of SDCCHs
Combined Multiframe - 4,12,20,28...44
Noncombined Multiframe - 8,16,24...48
361
Issue 12 Rev 2
SDCCH Allocation
SDCCH Allocation
The number_sdcchs_preferred field (as discussed previously) also sets the minimum
number of SDCCHs that the reconfiguration algorithm tries to maintain. When channel
reconfiguration is enabled (channel_reconfiguration_switch=1 ) the CRM will attempt
to maintain the preferred number of SDCCHs for allocation and may reconfigure idle
TCHs to SDCCHs before all SDCCHs are busy and, when the demand falls, reconfigure
the SDCCHs back to TCHs. The number of available SDCCHs after reconfiguration will
never exceed max_number_of_sdcchs.
362
SDCCH Allocation
Issue 12 Rev 2
max_number_of_sdcchs= <*>
Number of SDCCHs
Combined multiframe - 4, 12,20,28 . . . .44
Noncombined multiframe - 8,16,24. . . .48
363
Issue 12 Rev 2
SDCCH Reconfiguration
SDCCH Reconfiguration
The sdcch_need_high_water_mark and sdcch_need_low_water_mark are used
by the reconfiguration algorithm to trigger the reconfiguration process. The high
watermark determines the number of free SDCCHs remaining before TCH to SDCCH
reconfiguration should occur. tch_full_need_low_water_mark also has an effect on
such a reconfiguration to ensure that some idle traffic channels will still be left after the
conversion. The SDCCH low watermark determines the number of free SDCCHs before
the SDCCHs obtained by previous reconfiguration can be converted back to TCHs. The
dynamic reconfiguration algorithm is shown below.
The low and high watermarks are only in effect if the channel_reconfiguration_switch
is enabled.
1.
2.
3.
1.
Total number of SDCCHs after the reconfiguration must not be lower than
number_sdcch_preferred.
2.
1.
364
sdch_need_low_water_mark number_sdcch_preferred by 9
SDCCH Reconfiguration
Issue 12 Rev 2
SDCCH Reconfiguration
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
HWM = 2
TCH before
reconfiguration
SDCCH Preferred = 16
MAX = 24
HWM = 2
TCH before
reconfiguration
MAX = 24
HWM=2
LWM = 18
Available SDCCHs
MAX = 24
0
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
SDCCHs in use
SYS02_Ch3_32
365
Issue 12 Rev 2
366
Issue 12 Rev 2
Measurement Reporting
BCCH allocation
BSIC
IDLE FRAME
Best six
367
Issue 12 Rev 2
BA Indication
BA Indication
BA Indicator
A neighbour list (BA List) is included in system information message type 2 to an idle MS
and system information type 5 to a MS in traffic. Each of these lists is qualified by a
ba_indication bit. This is important in the case of a MS in traffic as the BA list is
conveyed in sys info 5 by use of a bit map. When the MS sends a measurement report
the frequency of the neighbour being reported is conveyed by its position in the bit map
of the last received system information 5 message. If a neighbour is added or indeed
deleted, the bit map in system 5 would be altered, and therefore the reported neighbour
measurements need to be qualified as using the old or the new list (bit map).
This qualification is specified by use of the ba_indication which will automatically toggle
between 0 and 1 to indicate a different list. This ba_indication is returned in the uplink
measurement report to validate which list was being used at the time of measurement.
There are two distinct ba_ind elements, ba_ind_sacch (system information 5, MS in
traffic) and ba_ind_bcch (system information 2, MS idle). Neither of these indicators
can be set by the operator. The ba_ind_sacch will toggle automatically if a neighbour is
added or deleted, although the ba_ind_bcch remains fixed.
The ba_alloc_proc field provides an alternate method of handling the processing of
Neighbour measurements reported by the MS, when there is a change made to the
neighbour list. Once the list has been changed the alternate method will cause the
HDPC to ignore any subsequent reports having the old ba_ind_sacch value. All stored
averages based on previously received neighbour measurement reports are also
discarded. The HDPC shall resume processing of measurements only when the MS
begins to use the new ba_ind_sacch value. When a 0 is entered in this field this
reinitialization is disabled, the HDPC will process remaining measurement reports despite
the ba_ind_sacch not yet having toggled, it will also retain previous reports as normal.
368
BA Indication
Issue 12 Rev 2
BA Indication
ba_alloc_proc = <*>
* 0 = Reinitialization disabled
1 = Reinitialization enabled
1
octet 1
Bit
127
EXT
IND
BA
IND
Bit
124
Bit
123
Bit
122
Bit
121
octet 2
Bit
120
Bit
119
Bit
118
Bit
117
Bit
116
Bit
115
Bit
114
Bit
113
octet 3
Bit
008
Bit
007
Bit
006
Bit
005
Bit
004
Bit
003
Bit
002
Bit
001
octet 17
SYS02_Ch3_34
369
Issue 12 Rev 2
2.
Any TCH or SDCCH that has been assigned to an MS including the SACCH.
The RXLEV value will be within the range of 063 depending on the signal strength
measurements
370
Issue 12 Rev 2
MS
Neighbour
BCCH
RSS
TCH/SDCCH
TCH/SDCCH
RXLEV Range
63 = Greater than 47 dBm
62 = 48 dBm
.
.
.
2 = 109 to 108 dBm
1 = 110 to 109 dBm
0 = Less than 110 dBm
BCCH
Neighbour RXLEV
TCH/SDCCH RXLEV
SYS02_Ch3_35a
BCCH
Neighbour Cell
BSS
RSS
Uplink RXLEV
Serving Cell
Neighbour Cell
BSS
SYS02_Ch3_35b
371
Issue 12 Rev 2
372
Issue 12 Rev 2
Quality Measurements
MS
S Downlink SDCCH/TCH
0=
1=
2=
3=
4=
5=
6=
7=
ASSUMED BER
0.14%
0.28%
0.57%
1.13%
2.26%
4.53%
9.05%
18.1%
373
Issue 12 Rev 2
Measurements
Reported by MS
on SACCH
1.
2.
3.
1.
Uplink RXLEV
2.
Uplink RXQUAL
3.
4.
Measurements
Performed by
RSS
The RSS will produce a new processed value for each of the measurements shown
above every 480mS (SACCH multiframe)
374
Issue 12 Rev 2
Reported by MS
S Downlink Received Signal Strength
S Downlink Quality
S Downlink Surrounding Cell RXLEV
Performed by RSS
S
S
S
S
375
Issue 12 Rev 2
376
Issue 12 Rev 2
Averages produced
Threshold exceeded
377
Issue 12 Rev 2
Power Control
Power Control
BSS
The MS provides averaged RSSI measurement samples on the downlink radio path to
the RSS. The RSS then performs its own averaging and these values are compared
against the power control thresholds. All, or a proportion of the averaged values being
considered must exceed the threshold value before any action will be taken.
The proportion of averaged values that must exceed the threshold is determined by two
database fields, decision_1_n1 and decision_1_p1 for increasing the output power and
decision_1_n2 and decision_1_p2 for decreasing the output power. The n
parameters represent the number of previously averaged values to be considered and
the p parameters are the proportion of those averages that must exceed the threshold
value. If p and n were set to the same value then all averaged values considered by
the RSS must exceed the threshold value.
Two threshold values are required, one to determine when the BSS output power level
should be increased and another to determine when the BSS output power level should
be decreased. These thresholds are set in the l_rxlev_dl_p (power increase required)
and u_rxlev_dl_p (power decrease required).
378
Power Control
Issue 12 Rev 2
Threshold Value
63
40
Signal Strength
.
.
.
47dBm
70dBm
75dBm
u_rxlev_dl_p= 35
30
80dBm
85dBm
l_rxlev_dl_p= 25
20
10
Comparison
S
S
100dBm
Threshold
90dBm
110dBm
l_rxlev_dl_p=<*>
u_rxlev_dl_p=<*>
* 0-63 (-110 to -47dBm)
S
S
S
S
decision_1_n1=<*>
decision_1_p1=<*>
decision_1_n2=<*>
decision_1_p2=<*>
* 1-31 Averages
S
S
S
n1, p1=
power increase
n2, p2= power decrease
p out of n averages must exceed threshold
379
Issue 12 Rev 2
Power Control
Power Control
MS
The RSS measures the uplink signal strength received from the MS. The RSS then
averages these samples and the averaged values are compared against the power
control thresholds. All, or a proportion of the averaged values being considered must
exceed the threshold value before any action will be taken.
The same database fields as used in BSS power control are used to determine what
proportion of averaged values must exceed the threshold before increasing or decreasing
its output power.
Two threshold values are required, one to determine when the MS output power should
be increased and another to determine when it should be decreased. These thresholds
are set in the l_rxlev_ul_p and u_rxlev_ul_p fields.
380
Power Control
Issue 12 Rev 2
Power Control MS
Threshold
Value
Signal Strength
63
40
.
.
.
47dBm
70dBm
75dBm
80dBm
30
u_rxlev_ul_p= 30
85dBm
l_rxlev_ul_p= 20
Comparison
100dBm
S
S
90dBm
10
Threshold
20
110dBm
l_rxlev_ul_p=<*>
u_rxlev_ul_p=<*>
Range 0- 63 (-110 to -47 dBm)
S
S
S
S
decision_1_n1=<*>
decision_1_p1=<*>
decision_1_n2=<*>
decision_1_p2=<*>
* 1-31 Averages
S
S
S
n1, p1=
power increase
n2, p2= power decrease
p out of n averages must exceed threshold
381
Issue 12 Rev 2
alt_qual_proc
alt_qual_proc
The database command alt_qual_proc determines if BER values or Quality Bands are
used to process quality measurement.
382
alt_qual_proc
Issue 12 Rev 2
alt_qual_proc
alt_qual_proc = <*>
0 = BER values
1 = Quality Bands
BER
RANGE
DEF
BAND
DEF
l_rxqual_ul_p
01810
226
07
l_rxqual_dl_p
01810
226
07
u_rxqual_ul_p
01810
28
07
u_rxqual_dl_p
01810
28
07
l_rxqual_ul_h
01810
453
07
l_rxqual_dl_h
01810
453
07
383
Issue 12 Rev 2
Power Control
Power Control
RXQUAL
The MS and RSS not only provide measurements for the RXLEV of the uplink and
downlink radio paths but also measure the quality of these paths. The RXQUAL
measurements are averaged by the RSS and compared against upper and lower
thresholds set in the database. If all or a proportion of the averaged values being
considered exceed the threshold value then the power output of the MS and BSS can be
adjusted accordingly.
384
Power Control
Issue 12 Rev 2
u_rxqual_ul_p= 0
u_rxqual_dl_p= 0
Assumed BER
0.14%
0.57%
2.26%
9.05%
18.10%
l_rxqual_ul_p=800
l_rxqual_dl_p=800
Threshold
S
S
S
S
l_rxqual_ul_p=<*>
l_rxqual_dl_p=<*>
u_rxqual_ul_p=<*>
u_rxqual_dl_p=<*>
*
Comparison
S decision_1_n3=<*>
S decision_1_p3=<*>
S decision_1_n4=<*>
S decision_1_p4=<*>
*
S
S
S
1-31 Averages
n3, p3=
power increase
n4, p4= power decrease
p out of n averages must exceed threshold
385
Issue 12 Rev 2
386
Issue 12 Rev 2
Threshold Value
63
40
.
.
.
-47 dBm
Threshold Value
u_rxqual_ul/dl_p=0
-80 dBm
20
-90 dBm
l_rxlev_ul/dl_p=25
l_rxlev_ul_h= 12
l_rxlev_dl_h= 12
10
-100 dBm
0.14%
0.57%
u_rxlev_ul/dl_p=35
0
2
-70 dBm
30
RXQUAL (ASSUMED)
2.26%
l_rxqual_ul/dl_p=500
l_rxqual_ul_h= 1000
l_rxqual_dl_h= 1000
9.05%
18.10%
-110 dBm
Threshold
l_rxlev_ul_h=<*>
l_rxlev_dl_h=<*>
*
063(110 to 47dBm)
l_rxqual_ul_h=<*>
l_rxqual_dl_h=<*>
*
Comparison
decision_1_n5=<*>
decision_1_p5=<*>
decision_1_n6=<*>
decision_1_p6=<*>
*131 Averages
n5, p5=
RXLEV
n6, p6=
RXQUAL
387
Issue 12 Rev 2
Handover Interference
Handover Interference
RXLEV measurements are used to support handovers due to interference if enabled.
The processes involved are identical to that for other handover types in that the RXLEV
measurements are averaged and then compared to a threshold value.
388
Handover Interference
Issue 12 Rev 2
Handover Interference
Threshold
Value
RXLEV
63
.
.
.
40
Threshold Value
-47dBm
RXQUAL
0.14%
0.57%
-80dBm
2.26%
20
-90dBm
9.05%
10
-100dBm
18.10%
Threshold
30
u_rxlev_ul_ih= 20
u_rxlev_dl_ih= 20
-70dBm
-110dBm
S
S
Comparison
S
S
l_rxqual_ul_h=1000
l_rxqual_dl_h=1000
u_rxlev_ul_ih= <*>
u_rxlev_dl_ih= <*>
*
decision_1_n7= <*>
decision_1_p7= <*>
*
0-31 Averages
389
Issue 12 Rev 2
MS Power Control
MS Power Control
The nature of a cellular system requires that the output power of the BSS and MS should
be set as low as possible. With the limited resource of the RF spectrum cellular systems
depend upon the reuse of RF channels. The re-use distance between these channels
depends mainly upon the subscriber density in a particular area, the greater the density
the shorter the re-use distance. By keeping the MS and BSS at the minimum acceptable
power output it reduces the chances of interference, particularly co-channel.
Another benefit of effective power control is that the battery life of handportable is
extended, thus maximising available talktime.
ms_power_control_allowed
Enables or disables uplink power control, if disabled the MS shall use the value specified
in max_tx_ms or its maximum power output whichever is the lower. Adaptive uplink
power is a GSM requirement.
ms_p_con_interval
Determines the minimum time interval between successive power control change
commands. Uplink power control voting is suspended whilst this timer is running.
ms_p_con_ack
When the MS is sent a new power control instruction, it will implement the instruction and
then echo this change back in the L1 part of the uplink sacch message. Only when this
timer has expired or ordered power control = echoed power control will
ms_p_con_interval begin. This parameter is only effective when
decision_alg_number=1.
pow_inc_step_size_ul
Sets the step sizes for uplink and downlink power increases.
pow_red_step_size_ul
sets the step sizes for uplink and downlink power decreases.
MS Maximum
Power
The RSS is responsible for the power control of MS. It is measuring the signal strength
and quality of the uplink radio path, averaging the measurements and comparing them to
the threshold values.
The max_tx_ms sets the maximum MS output power and the MS will not be told by the
RSS increase its power to a level above that set in this field.
390
MS Power Control
Issue 12 Rev 2
MS Power Control
S
decision_alg_number = <*>
*
0 = Motorola alg
1 = Alternate alg
ms_power_control_allowed= <*>
*
0 = Power Control Disabled
1 = Power Control Enabled
ms_p_con_ interval=<*>
*
0 = 0 sacch multiframes
1 = 2 sacch multiframes
.
.
31 = 62 sacch multiframes
ms_p_con_ack=<*>
*
0 = 0 sacch multiframes
1 = 2 sacch multiframes
.
.
31 = 62 sacch multiframes
Pow_inc_step_size_ul
*
2= 2dB, 4= 4dB . . . 12=12dB, 14=14dB
Pow_red_step_size_ul
*
2= 2dB, 4= 4dB
MS Maximum Power
S
max_tx_ms=<*>
*
5-39 (GSM 900) (odd values only)
*
0-30 (DCS 1800) (even values only)
391
Issue 12 Rev 2
bts_p_con_interval
Determines the minimum time interval between successive power control changes.
Downlink power control voting is suspended whilst this timer is running.
bts_p_control_ack
Determines the maximum time the HDPC will wait for an acknowledgement from the
DRIM card that the power control instructor has been carried out. Only when this timer
has expired or ordered BTS power= actual BTS power (acknowledge returned), will
bts_p_con_interval begin. This parameter is only effective when
decision_alg_number=1.
392
Issue 12 Rev 2
bts_power_control_allowed=<*>
*
0 - disabled
1 - enabled
bts_p_con_interval=<*>
*
0 = 0 sacch multiframes
1 = 2 sacch multiframes
.
.
.
31 = 62 sacch multiframes
S
bts_p_con_ack=<*>
*
0 = 0 sacch blocks
1 = 2 sacch blocks
2 = 4 sacch blocks
.
.
.
31 = 62 sacch blocks
S
max_tx_bts=<*>
*
21 steps of 2 dBs of attenuation from 43 dBm
in GSM900/EGSM/GSM850, or 39 dBm in the case
of DCS1800
393
Issue 12 Rev 2
pow_red_step_size_dl
Sets the step size for downlink power decreases.
394
Issue 12 Rev 2
pow_inc_step_size_dl=<*>
*
2 = 2 dB
4 = 4 dB
.
.
14 = 14 dB
S
pow_red_step_size_dl= <*>
*
2 = 2 dB
4 = 4 dB
395
Issue 12 Rev 2
396
Issue 12 Rev 2
-64
UL_RXLEV
TRIGGER
-68
OFFSET
(12)
-75
u_rxlev_ul_p
-80
-85
MS POWER SCALE
0 - 43 dBm
1 - 41 dBm
.
.
15-13 dBm
desired level
l_rxlev_ul_p
MS TXPWR = 39 dBm/2
ALGORITHM
ORDERED POWER LEVEL = CURRENT POWER LEVEL +
EXAMPLE
=2+
=2+
397
Issue 12 Rev 2
rpd_period
The averaging and voting mechanisms employed by the normal power control algorithm
are not utilised by this feature. No voting will occur and the hreqave value will effectively
be rpd_period. This is the number of previously received uplink reports from layer one,
which are used to make up the ul_rxlev average value.
rpd_trigger
This feature will not be initiated until the perceived uplink power level (ul_rxlev) exceeds
the value of rpd_trigger.
rpd_offset
The value of rpd_offset is used in the calculation, and is the difference between the
trigger value and the desired power level.
398
Issue 12 Rev 2
rpd_pwr_down = <*>
*
rpd_period = <*>
*
rpd_offset = <*>
*
1 - 32 SACCH periods
rpd_trigger = <*>
*
0 - OFF
1 - ON
0 - 63 dBm
399
Issue 12 Rev 2
3100
Issue 12 Rev 2
dyn_step_adj = <*>
Used to determine whether the dynamic step adjust
algorithm is enabled or disabled.
*
0 disabled (default 0)
1 enabled (excludes power reduction)
2 enabled (includes power reduction)
dyn_step_adj_fmpr = <*>
Used to control the rapidity of a dynmaic power reduction
*
0 10 (default 10)
3101
Issue 12 Rev 2
3102
Issue 12 Rev 2
dyn_step_adj_fmpr
10
where:
flow
fhigh
xx
3103
Issue 12 Rev 2
Discontinuous Transmission
Discontinuous Transmission
Discontinuous transmission (DTX) is a feature available mainly on handportables MS
which maximises the battery life of handportables by disabling the transmit function when
the subscriber is not speaking during a call and will help to reduce interference.
There are three options that can be set in the dtx_required field;
1.
2.
3.
3104
Discontinuous Transmission
Issue 12 Rev 2
Discontinuous Transmission
dtx_required=<*>
3105
Issue 12 Rev 2
Handover Evaluation
Handover Evaluation
The cause value contained within the handover recognised message will affect the
evaluation process in the BSC. The handover evaluator in the SSM will determine the
need for either an internal or external handover upon analysis of the qualified targets
within the message. The SSM will be supporting a number of RRSMs and hence could
possibly be receiving multiple handover recognised messages in quick succession
during busy periods. These messages are queued and are dealt with in the priority
shown opposite.
3106
Handover Evaluation
Issue 12 Rev 2
Handover Evaluation
Handover Priority
1.
2.
Uplink interference
3.
Downlink quality
4.
Downlink interference
5.
Uplink level
6.
Downlink level
7.
Distance
8.
Uplink quality
Power budget
3107
Issue 12 Rev 2
Handovers Allowed
Handovers Allowed
There are a number of reasons as to why an MS may need to be handed over from one
channel to another. These include RXLEV uplink/downlink and RXQUAL uplink/downlink.
Before a handover can take place either due to the quality or strength of the signal that
type of handover must first be enabled in the database.
3108
Handovers Allowed
Issue 12 Rev 2
Handovers Allowed
S ul_rxqual_ho_allowed=<*>
S dl_rxqual_ho_allowed=<*>
S ul_rxlev_ho_allowed=<*>
S dl_rxlev_ho_allowed=<*>
*
0 - disabled
1 - enabled
3109
Issue 12 Rev 2
3110
Issue 12 Rev 2
SDCCH Handover
sdcch_ho= <*>
0
1
S
*
Handover disabled
Handover enabled
(governed by sdcch_timer_ho)
sdcch_timer_ho= <*>
1 = 2 SACCH multiframes
2 = 4 SACCH multiframes
.
.
.
.
31 = 62 SACCH multiframes
3111
Issue 12 Rev 2
Handovers Interference
Handovers Interference
If the RXQUAL of either the uplink or downlink reaches the threshold that would normally
cause a handover but the RXLEV is at a value higher that the threshold requiring a power
increase then a handover may be initiated due to interference, if the
interfer_ho_allowed field is enabled. This type of handover would be intra-cell.
3112
Handovers Interference
Issue 12 Rev 2
Handover Interference
interfer_ho_allowed= <*>
*
0=
disabled
1=
enabled
3113
Issue 12 Rev 2
Handovers Interference
Power Budget
Handover
A field in the database determines whether the use of the power budget assessment
process for handover purposes can be used or not.
If an MS on an allocated resource during its measurement reporting process sees
another channel that would provide an equal or better quality radio link requiring a lower
output power then a handover may be initiated. Handovers due to power budget ensure
that the MS is always linked to the cell with the minimum path loss even though the
quality and level thresholds, may not have been exceeded.
The pwr_handover_allowed field enables/disables power budget handover. If enabled
for each established radio link and neighbour BCCHs, defined in the BCCH allocation,
the BSS will use the following to determine whether a handover is required.
1.
2.
3.
4.
5.
3114
Handover margin
Handovers Interference
Issue 12 Rev 2
S pwr_handover_allowed=<*>
*
0 - disabled
1 - enabled
3115
Issue 12 Rev 2
3116
Issue 12 Rev 2
S timing_advance_period=<*>
*
0 = 0 SACCH multiframes
1 = 2 SACCH multiframes
.
.
.
.
.
.
31 = 62 SACCH multiframes
3117
Issue 12 Rev 2
3118
Issue 12 Rev 2
S ms_distance_allowed=<*>
*
0= disabled
1= enabled
Threshold:
S ms_max_range=<*>
*
0 to 63
Comparison:
S decision_1_n8= <*>
S decision_1_p8= <*>
*
0-31 Averages
3119
Issue 12 Rev 2
Handovers
Handovers
Incoming
Handovers
Incoming handovers to a cell can be enabled/disabled, regardless of cell barring, using
the en_incom_ho flag. en_incom_ho is a per cell CRM Element and if set to 0 will
reject any handover requests.
3120
Handovers
Issue 12 Rev 2
Incoming Handovers
S en_incom_ho = <*>
*
3121
Issue 12 Rev 2
Handovers
Intra-Cell
Handovers
Intra-cell handovers is an optional feature in the GSM system and would normally only be
required if an MS is on a radio channel that is subjected to co-channel interference. Poor
signal strength measurements taken on the original radio channel would not normally be
improved by performing intra-cell handovers as the signal strength of all radio channels
within that cell would be similar. Intra cell handovers can occur through quality although
interference problems will generally be the cause.
Three options are specified for this database field:
0
Inter-Cell
Handovers
Handovers fall into one of two categories, either internal or external. Internal
handovers exist between two cells controlled by the same BSC. External handovers will
take place between two cells connected to different BSCs. In all cases external
handovers will be controlled by the MSC. Internal handovers may be dealt with by the
BSC or indeed referred to the MSC, this flag will determine the controlling entity.
0
3122
Handovers
Issue 12 Rev 2
Inter/Intra-cell Handovers
intra_cell_handover_allowed=<*>
inter_cell_handover_allowed=<*>
3123
Issue 12 Rev 2
3124
Issue 12 Rev 2
report_resource_tch_f_high_water_mark=<*>
+ number of TCHs
Valid range 0 254
report_resource_tch_f_low_water_mark=<*>
* Number of TCH's
Valid Range 1 - 255
3125
Issue 12 Rev 2
3126
Issue 12 Rev 2
Measurement
Reports
RSS
BTS
MS
SSM
BSC
Measurement
Reports
Handover Recognised
RSS
MS
BTS
BSC
List of Target
Cells Evaluated
Measurement
Reports
RSS
SSM
BTS
MS
SSM
BSC
Handover
Required
MSC
SYS02_Ch3_45
S number_of_preferred_cells=<*> 1 - 16
*
3127
Issue 12 Rev 2
Handover Reporting
Handover Reporting
The handover detection and power control process in the RSS software is responsible for
detecting the need for a connection to be handed over to another cell. When all the
relevant criteria have been met this process will generate a handover recognised
message which will be sent to the SSM for evaluation. This message will contain a
cause value, expressing the reason why this handover is necessary, and also a number
of qualified neighbours. Although this message is processed by the SSM it is actually
transmitted via the RRSM to pick up relevant connection identities. When the message
is sent the HDPC starts the handover_recognized_period timer for that connection.
Whilst this timer is running the handover triggering mechanism, which initially produced
the recognised message, is inhibited, hence whilst this timer is running another handover
recognised message for this connection could not be generated. In most circumstances
this timer would not expire as a handover will have been executed and the connection will
be deleted from that cell. If the timer were allowed to expire then the handover triggering
mechanism will begin again for that connection.
Handover
Evaluating
Upon receipt of the handover recognised message the handover evaluator in the SSM
will, upon examination of the neighbours, determine if an external or internal handover is
necessary. Should the handover be external then the SSM will generate a handover
required message which will be sent to the MSC, this message is very similar to the
handover recognised message. When this message is sent the SSM will start GSM
timer T7 (BSSMAP_t7), whilst this timer is running no more handover required
messages will sent with reference to same connection. When this timer expires the SSM
may generate another message, but only if a new handover recognised message has
been received from the HDPC. This timer is not a repetition timer, the same handover
required message will not simply be repeated. This functionality is important as in this
elapsed time the cause for handover may have changed along with the number of
qualified neighbours.
Handover
Rejection
The element handover_required_reject_switch may effect the above process. If set to
on the handover required message will only contain the external neighbour specified in
the handover recognised message, any internal neighbours will not be included. If the
MSC is unable to hand the connection over, possibly because of congestion or
subscription reasons it will send the BSC a handover required reject message. The SSM
will then re-examine the handover recognised message and attempt to commit an
internal handover. If the handover_required_reject_switch is off the BSC will include
all the neighbours specified in the handover recognised message in the the handover
required message. In this case the MSC will not return the handover required reject
message in the case of failure.
Note:
This parameter is set in chg_element.
3128
Handover Reporting
Issue 12 Rev 2
Handover Reporting
HDPC
SSM
handover_recognized
handover_recognized_period
Range 2 to 64
SACCH Multiframes
Default 2
Expired
handover_recognized
SYS02_Ch3_46a
Handover Reporting
SSM
handover_recognized
MSC
handover_required
T7
handover_recognized
Range 0 to 1000000 ms
Default 30000
Expired
handover_required
T7
SYS02_Ch3_46b
3129
Issue 12 Rev 2
3130
Issue 12 Rev 2
handover_power_level= <*>
* = GSM900/GSM850
2 39 dBm
.
.
.
19 5 dBm
* = DCS1800 and PCS1900
0 30 dBm
1 28 dBm
2 26 dBm
.
.
.
15 0 dBm
3131
Issue 12 Rev 2
A=
B=
C=
u_rxlev_ul_p ) l_rxlev_ul_p
= centre of the target cells uplink power
2
window
D=
P=
3132
Issue 12 Rev 2
use_derived_ho_power=<*>
*
0= use handover_power_level
1= use calculated handover level
A=
B=
C=
u_rxlev_ul_p ) l_rxlev_ul_p =
2
centre of target cell's uplink power
window
D=
P=
3133
Issue 12 Rev 2
Handover Default
Information
The handover default parameters found in add_cell are GSM parameters which specify
database fields for a handover to an unknown cell. A handover to an unknown cell, one
which is not specified in the BA list, is not possible using Motorolas infrastructure.
Motorola uses these parameters for a similar purpose to default handover fields not
specified in add_neighbor.
None of the default parameters are used in the case of an external handover,
ms_txpwr_max_cell, ho_margin_cell and rxlev_min_cell must be specified in the
add_neighbor command.
For an internal handover however, ho_margin_cell and rxlev_min_cell can be
optionally specified in add_neighbor. If they are not specified in add_neighbor the
default parameters in add_cell will be used. ms_txpwr_max_def will never be used for
either case internal or external handovers. The uplink parameter used in the handover
decision process is max_tx_ms of the neighbour, in the case of an internal or
ms_txpwr_max_cch of the neighbour (found in the add_neighbor command) in the
case of external.
3134
Issue 12 Rev 2
S ms_txpwr_max_def=<*>
* 5-39
(GSM900/GSM850/EGSM)
0-36 (DCS1800)
0-32 (PCS1900)
S ho_margin_def=<*>
*
-63 to +63dB
S rxlev_min_def=<*>
*
0= -110 dBm
1= -109 dBm
2= -108 dBm
.
.
63= -47 dBm
3135
Issue 12 Rev 2
Handover Initiation
Handover Initiation
rr_t3103
The handover procedure is initiated by the network sending a handover command
message to the MS. The handover command message contains information regarding
the target TCH, initial power setting to access the target cell, necessary signalling
procedures and a handover reference.
On sending the initiate handover message to the source RRSM, the SSM begins timer
rr_t3103. In the normal chain of events, this timer should never be allowed to expire. It
is guarding the receipt of either the unsuccessful handover message from the source
RRSM or the handover successful message from the target RRSM. The receipt of either
of these messages will stop the timer. If this timer is allowed to expire then a clear
request will be sent to the MSC in a bid to clear the connection. It should be noted that
further timers in the source and target RRSMs are also guarding the receipt of similar
messages from the MS. Should these timers expire without the receipt of the handover
complete (target RRSM) or handover failure (source RRSM), then the RRSM in each
case will release the channel and inform the SSM, these messages also have the effect
of stopping rr_t3103.
3136
Handover Initiation
Issue 12 Rev 2
rr_t3103
SSM
Source RRSM
Initiate handover
MS
rr_t3103
Handover command
Handover failure
Unsuccessful handover
rr_t3103
Expired
OR
Target
RRSM
Handover complete
Handover successful
rr_t3103
Expired
SYS02_Ch3_47
rr_t3103= <*>
* milliseconds
Valid range 0 to 1000000
Default value 3000
3137
Issue 12 Rev 2
3138
Issue 12 Rev 2
RSS (S)
RRSM (S)
SSM
initiate handover
ho_cmd
ho_cmd
ho_access
RSS(t)
RRSM(t)
ho_access
ho_access
ho_access
ho_detection
ho_detect received
Phys info
SABM
Establish indication
UA
ho_cmplt
ho_cmplt
ho_succ
SYS02_Ch3_48
number of repetitions
0 to 200
Default 20
SYS02 GSR5/AGSR: BSS Database
3139
Issue 12 Rev 2
3140
Issue 12 Rev 2
S link_fail=<*>
*
0 = 4 SACCH MULTIFRAMES
1 = 8 SACCH MULTIFRAMES
.
.
.
15 = 64 SACCH MULTIFRAMES
3
Counter S
2
0
SACCH Multiframes
Decoded
Not decoded
SYS02_Ch3_49
3141
Issue 12 Rev 2
Radio Link
Revival
The full_pwr_rfloss field enables or disables the ability of the RSS to instruct the MS
and BSS to go to maximum output power in an attempt to save the link before it is timed
out. This feature is triggered by the link_fail counter reaching the lower threshold
link_about_to_fail.
3142
Issue 12 Rev 2
S full_power_rfloss=<*>
*
0= disabled
1= enabled
S link_about_to_fail= <*>
*
0 = 0 SACCH MULTIFRAMES
1 = 4 SACCH MULTIFRAMES
.
.
.
15 = 60 SACCH MULTIFRAMES
3143
Issue 12 Rev 2
REMINDER
1 26Frame (TCH) Multiframe = 120ms
1 SACCH Message = 4 TCH Multiframes @ 480 ms (approx 1/2 sec)
1 Step = 4 SACCH Multiframes = 4 x 480 ms approx 2 sec
3144
Issue 12 Rev 2
S
*
radio_link_timeout= <*>
0 = 4 SACCH MULTIFRAMES
1 = 8 SACCH MULTIFRAMES
.
.
.
15 = 64 SACCH MULTIFRAMES
link_fail
link_about_to_fail
full_pwr_rfloss
radio_link_timeout
SYS02_Ch3_50
3145
Issue 12 Rev 2
Timers rr_t3109
Timers rr_t3109
rr_t3109 is started when a lower layer failure is detected by the network or in the channel
release procedure. Its purpose is to release the channel for further use.
Uplink Failure
In order to monitor both uplink and downlink radio paths both the MS and BSS will
monitor the appearance of SACCH messages. Should an uplink failure occur and the
threshold of lost SACCH messages is reached (link_fail parameter) the BSS will activate
rr_t3109. In addition to this the BSS will no longer transmit SACCH messages to the
MS. The MS will now no longer receive SACCH messages and its own threshold of lost
SACCHs, T100 (set to radio_link_timeout) will eventually be reached.
When T100 has expired the MS will return to the idle mode and monitor the cell BCCH.
The BSS will also release the channel resources but only after rr_t3109 expires which
will be after T100.
Downlink Failure
A downlink fail will follow the same pattern, T100 will expire in the MS and SACCHs will
no longer be sent uplink. Lack of SACCHs will cause link_fail to exceed at the BSS and
subsequently cause rr_t3109 to activate and eventually expire.
rr_t3109 must be set to higher value than T100 as it is used by the system when lower
link failure is detected. T100 should therefore expire before rr_t3109 ensuring that the
system holds on to radio link long enough for the MS to release it. If not, it will be
possible to have two on the same TCH.
3146
Timers rr_t3109
Issue 12 Rev 2
Link Failure
SACCH
MS
BSS
T100 (radio_link_timeout)
activated
MS
Downlink SACCH
deactivated
BSS
Link_fail exceeded
rr_t3109 activated
t
T100 running
(radio_link_timeout)
T
BSS
rr_t3109 running
BSS
MS
BCCH
T100
exceeded
MS
Return to idle
T>t
SYS02_Ch3_51
3147
Issue 12 Rev 2
3148
Issue 12 Rev 2
CHANNEL RELEASE
MM
rr_t3109
MM
MS
BSS
SACCH DEACTIVATED
t3110
Layer 2 DISCONNECT
MS
t3110
FRAME
Layer 2
UA
MS
Layer 2
rr_t3109
BSS
rr_t3111
Stopped on
receipt of
disc
Activated
on receipt
of disc
Layer 2
BSS
Stopped on receipt
of disc
rr_t3111
BCCH
MS
BSS
Radio resources
released on
rr_t3111 expiry
SYS02_Ch3_52
3149
Issue 12 Rev 2
CRM Timers
CRM Timers
rf_chan_rel_ack
During the channel release procedure to end a call, the CRM sends an RF channel
release message to RSS, at this point the timer is started. Once the RSS has released
the physical circuit it will send an RF channel release acknowledge message to the
RRSM, which is then forwarded to the CRM. When CRM receives this message the
channel can be marked as available and can be allocated to another subscriber. If the
timer is allowed to expire the channel will be marked as available anyway.
3150
CRM Timers
Issue 12 Rev 2
CRM Timers
rf_chanl_rel_ack = <*>
RSS
CRM
RRSM
RF Channel Release
3151
Issue 12 Rev 2
Call Re-establishment
Call Re-establishment
In the event of a radio link failure, a feature of GSM is call re-establishment.
If a radio link has failed, due to an MS passing through a tunnel for example, the MS will
sample the received signal strength of BCCH carriers including the original serving cell,
average the measurements taken and then select the cell having the highest average.
Assuming that the selected cell is one of the home PLMN cell or one supporting roaming,
the cell is not barred and the reestablish_allowed field is set to 0 (call re-establish
permitted) then the MS will attempt to re-establish the call.
If the MS is unsuccessful on the selected cell it may attempt the same process on five
other cells offering the highest received signal strength measurement. If still
unsuccessful re-establishment will be aborted.
3152
Call Re-establishment
Issue 12 Rev 2
Call Re-establishment
S
*
reestablish_allowed= <*>
0= reestablishment allowed
1= reestablishment not allowed
3153
Issue 12 Rev 2
CRM Timers
CRM Timers
In addition to rr_t3109, rr_t3111 and rr_t3212 there are two other timers needed by the
CRM on a per cell basis. Their function is as described below:
dealloc_inact
When an error indication is received from RSS to indicate a fatal error at Layer 2 this
timer is started. If the call is to be dropped the RRSM will return a deallocate inactive
dch to the CRM which will in turn release the channel. If the CRM does not receive a
deallocate inactive dch it will assume the RRSM has recovered the connection and will
not release the channel.
ho_ack
This timer is used during the intra_cell handover procedure when the serving timeslot
goes Out Of Service (OOS). It is started when the CRM sends an internal handover
assignment message to the RRSM specifying the target channel to be used. After
further messaging between the RRSM and SSM to switchover the terrestrial trunk in the
BSC, the RRSM will return an acknowledgment to the CRM. If the timer is allowed to
expire and no acknowledgment is received the CRM re-marks the newly assigned
channel as free and available for further allocation to another subscriber.
3154
CRM Timers
Issue 12 Rev 2
CRM Timers
dealloc_inact = <*>
RSS
CRM
RRSM
RSS Error
Deallocate inactive dch
If Timer expires connection
is maintained
* milliseconds
Valid range 0 to 1000000
Default value 5000
SYS02_Ch3_54
ho_ack = <*>
RSS
CRM
RRSM
internal handover assignment
SYS02_Ch3_55
3155
Issue 12 Rev 2
Cell Exercise
Cell Exercise
Adding a Cell
1.
2.
3.
4.
5.
6.
7.
The maximum number of SDCCHs for cell 1 is 24 and for cell 2 is 32.
8.
In both cells, if there are just 2 free SDCCHs available then reconfiguration from
TCH to SDCCH should occur. To allow this reconfiguration 5 or more traffic
channels should be idle.
9.
In both cells, if 14 free SDCCHs are available then reconfiguration from SDCCH to
TCH should occur.
10.
A total of 9 CCCH blocks are available of which four are reserved for AGCH on cell
1 and 3 on cell 2.
11.
12.
The CRM will allocate channels on a best-to-worst basis, each channel being
placed in one of five interference bands ranging from an absolute noise level of
85 dBm, 90 dBm, 95 dBm, 100 and 105 dBm.
13.
The CRM will attempt to allocate an SCCP reference number up to eight times for
cell 1 and seven times for cell 2.
14.
15.
An MS, when first accessing either cell, will do so at a power level of 37 dBm.
16.
The MSC must be informed when the number of full rate channels available rises
to eight or drops to two.
17.
18.
19.
A roaming agreement exists between the Swiss PLMN (NCC of 1), both Italian
systems and both French systems. Cell 1 is positioned on the border facing Italy
and cell 2 is located on the border facing France.
20.
21.
On detection of a lower layer failure and during the channel release procedure the
system will hold onto a channel for 15.5 seconds for cell 1 and 100 seconds for cell
2.
22.
3156
The two cells being equipped are part of the Swiss PLMN, both in Location Area
255 and are numbered 1 and 2 at site 1.
During normal channel release once the main signalling link has been terminated
and the BSS receives a disconnect frame from the MS the RF link will be
terminated after 7.68 seconds for cell 1 and 5 seconds for cell 2.
SYS02 GSR5/AGSR: BSS Database
Cell Exercise
Issue 12 Rev 2
23.
24.
25.
26.
27.
28.
When considering cell reselection to another location area the target cells C1 or
C2 must be 4dB higher than that of the server for cell 1 and 2dB higher than that
of the server for cell 2.
29.
The MS receive level must be at least 106 dBm from cell 1 and 95 dBm from
cell 2 before attempting to access.
30.
When allocated a hopped TCH which includes the BCCH carrier, measurement
reporting of the BCCH frequency should be carried out on cell 1 and should not be
carried out on cell 2.
31.
Intra- and Inter-cell handovers are permitted and can, if applicable, be controlled
by the BSC.
32.
33.
34.
If resources are not available at a target cell for handovers from cell 1 then the
source BSC must be informed by the switch. For handovers from cell 2 the BSC
need not be informed.
35.
If the network does not receive either a handover complete message on the new
channel, a failure message on the old channel or the MS re-establishing the call
after the MS has been told to handover from cell 1 for 4.1 seconds and from cell 2
for 1.5 seconds then the source channel will be released and all references to that
MS cleared.
36.
If after requesting radio resources the signalling link is not established in 1.7
seconds for cell 1 and 1.5 seconds for cell 2 the allocated resources will be
released and the channel request message ignored.
37.
MS power control is allowed, the minimum time between power control orders
being approximately 10 seconds for cell 1 and 6 seconds for cell 2. The maximum
MS output power that the MS will be told to go to is 39 dBm. Power increments
will be 6 dB steps and will be reduced in 4 dB steps for uplink and downlink.
38.
BTS power control is allowed and the maximum output power for cell 1 will be 39
dBm and for cell 2, 43 dBm.
39.
The minimum interval between BTS power changes is approximately 2 seconds for
cell 1 and 1 second for cell 2.
40.
For handover, timing advance and power control functions 66% of 12 averaged
values must exceed the set threshold for cell 1 and 75% of 8 averaged values for
cell 2.
41.
3157
Issue 12 Rev 2
Cell Exercise
42.
43.
The threshold for handovers due to RXLEV in both the uplink and downlink
directions are 100 dBm for cell 1 and 98 dBm for cell 2.
44.
The lower threshold for power control in both the uplink and downlink direction due
to RXQUAL is a BER 13.5% for cell 1 and 16% for cell 2.
45.
The thresholds for handovers due to interference are a BER of 10% and a RXLEV
of 95 dBm for cell 1 and a BER of 10% with a RXLEV of 95 dBm for cell 2 in
either the uplink or downlink direction.
46.
47.
Default values for RXLEV minimum if not known by source BSS are 100 dBm for
cell 1 and 95 dBm for cell 2.
48.
Default value for MS maximum power in a target cell if not know by source BSS
are 39 dBm for both cell 1 and 2.
49.
The default values for the handover margin is 16 dB for cell 1 and cell 2.
50.
51.
52.
The minimum interval between timing advance changes for cell 1 is 4.8 seconds
for cell 2 in 2.88 seconds.
53.
If the RSS does not decode consecutive SACCH bursts on any link to an MS for a
period 12 seconds on both cells, the link will be assumed to be lost. When the
RSS has failed to decode consecutive SACCH bursts for a period of 8 seconds the
downlink and uplink power shall be increased to the cell maximum for both cells.
54.
55.
The RSS will check the loading of the RACH for cell 1 every 31 seconds and for
cell 2 every 37.66 seconds.
56.
The RSS will check the loading of the RACH slots, when an overload condition has
been flagged in the previous period, every 40 seconds for cell 1 and every 47
seconds for cell 2.
57.
If after successfully handing over the MS does not acknowledge the receipt of a
physical information message within 60 ms for cell 1 and 20 mS for cell 2 the
physical information message can be retransmitted, upto a maximum of 20 times
for cell 1 and 30 times for cell 2.
58.
59.
60.
Both cells shall employ the rapid pwr down feature. The feature will be initiated on
no less than 4 reports and trigger at 60 dBm. The desired BTS rxlev after power
down should be 80 dBm.
61.
62.
63.
3158
The thresholds for MS power control are 90 dBm and 75 dBm for cell 1 and
104 dBm and 95 dBm for cell 2.
The cell reselect offset for cell 1 should be +2dB. The temporary offset should be
20dBs for 3 minutes.
SYS02 GSR5/AGSR: BSS Database
Cell Exercise
Issue 12 Rev 2
Add_cell
Working Area
CELL 1
add_cell
freq_type=
bsic=
wait_indication_parameters=
ccch_conf=
bs_ag_blks_res=
bs_pa_mfrms=
extended_paging_active=
number_sdcchs_preferred=
en_incom_ho=1
intra_cell_handover_allowed=
inter_cell_handover_allowed=
number_of_preferred_cells=
ho_margin_def=
handover_recognized_period=
ul_rxqual_ho_allowed=
dl_rxqual_ho_allowed=
ul_rxlev_ho_allowed=
dl_rxlev_ho_allowed=
sdcch_ho=
sdcch_timer_ho=
interfer_ho_allowed=
pwr_handover_allowed=
ms_distance_allowed=
mspwr_alg = 0
handover_power_level=
pwrc=
intave = 8
timing_advance_period=
ms_p_con_interval=
ms_p_con_ack=0
ms_power_control_allowed=
bts_p_con_interval=
bts_p_con_ack=0
bts_power_control_allowed=
pow_inc_step_size_ul=
pow_inc_step_size_dl=
pow_red_step_size_ul=
pow_red_step_size_dl=
dyn_step_adj=0
dyn_step_adj_fmpr=10
max_tx_bts=
max_tx_ms=
rxlev_min_def=
ms_txpwr_max_def=
EMOTOROLA LTD. 2001
CELL 2
add_cell
freq_type=
bsic=
wait_indication_parameters=
ccch_conf=
bs_ag_blks_res=
bs_pa_mfrms=
extended_paging_active=
number_sdcchs_preferred=
en_incom_ho = 1
intra_cell_handover_allowed=
inter_cell_handover_allowed=
number_of_preferred_cells=
ho_margin_def=
handover_recognized_period=
ul_rxqual_ho_allowed=
dl_rxqual_ho_allowed=
ul_rxlev_ho_allowed=
dl_rxlev_ho_allowed=
sdcch_ho=
sdcch_timer_ho=
interfer_ho_allowed=
pwr_handover_allowed=
ms_distance_allowed=
mspwr_alg = 0
handover_power_level=
pwrc=
intave = 8
timing_advance_period=
ms_p_con_interval=
ms_p_con_ack=0
ms_power_control_allowed=
bts_p_con_interval=
bts_p_con_ack=0
bts_power_control_allowed=
pow_inc_step_size_ul=
pow_inc_step_size_dl=
pow_red_step_size_ul=
pow_red_step_size_dl=
dyn_step_adj=0
dyn_step_adj_fmpr=10
max_tx_bts=
max_tx_ms=
rxlev_min_def=
ms_txpwr_max_def=
SYS02 GSR5/AGSR: BSS Database
3159
Issue 12 Rev 2
Cell Exercise
decision_alg_num=0
decision_1_dl_rxlev_av_h=0
decision_1_dl_rxlev_av_ih=0
decision_alg_num=0
decision_1_dl_rxlev_av_h=0
decision_1_dl_rxlev_av_ih=0
Add_cell
Working Area
CELL 1
CELL 2
decision_1_dl_rxlev_av_p=0
decision_1_dl_rxqual_av_h=0
decision_1_dl_rxqual_av_p=0
decision_1_n1=
decision_1_n2=
decision_1_n3=
decision_1_n4=
decision_1_n5=
decision_1_n6=
decision_1_n7 =
decision_1_n8=
decision_1_ncell_rxlev_av_h_calc=0
decision_1_p1=
decision_1_p2=
decision_1_p3=
decision_1_p4=
decision_1_p5=
decision_1_p6=
decision_1_p7=
decision_1_p8=
decision_1_p_bgt_rxlev_av_h=0
decision_1_tim_adv_av_alg =0
decision_1_ul_rxlev_av_h=0
decision_1_ul_rxlev_av_ih=0
decision_1_ul_rxlev_av_p=0
decision_1_ul_rxqual_av_h=0
decision_1_ul_rxqual_av_p=0
alt_qual_proc = 0
l_rxqual_ul_p=
l_rxqual_dl_p=
u_rxqual_ul_p=
u_rxqual_dl_p=
l_rxqual_ul_h=
l_rxqual_dl_h=
l_rxlev_ul_h=
l_rxlev_dl_h=
u_rxlev_ul_ih=
u_rxlev_dl_ih=
ms_max_range=
l_rxlev_ul_p=
decision_1_dl_rxlev_av_p=0
decision_1_dl_rxqual_av_h=0
decision_1_dl_rxqual_av_p=0
decision_1_n1=
decision_1_n2=
decision_1_n3=
decision_1_n4=
decision_1_n5=
decision_1_n6=
decision_1_n7 =
decision_1_n8=
decision_1_ncell_rxlev_av_h_calc=0
decision_1_p1=
decision_1_p2=
decision_1_p3=
decision_1_p4=
decision_1_p5=
decision_1_p6=
decision_1_p7=
decision_1_p8=
decision_1_p_bgt_rxlev_av_h=0
decision_1_tim_adv_av_alg =0
decision_1_ul_rxlev_av_h=0
decision_1_ul_rxlev_av_ih=0
decision_1_ul_rxlev_av_p=0
decision_1_ul_rxqual_av_h=0
decision_1_ul_rxqual_av_p=0
alt_qual_proc = 0
l_rxqual_ul_p=
l_rxqual_dl_p=
u_rxqual_ul_p=
u_rxqual_dl_p=
l_rxqual_ul_h=
l_rxqual_dl_h=
l_rxlev_ul_h=
l_rxlev_dl_h=
u_rxlev_ul_ih=
u_rxlev_dl_ih=
ms_max_range=
l_rxlev_ul_p=
3160
Cell Exercise
Issue 12 Rev 2
l_rxlev_dl_p =
u_rxlev_ul_p=
u_rxlev_dl_p=
ncell_proc=0
missing_rpt=0
ba_alloc_proc=
link_fail=
link_about_to_fail=
l_rxlev_dl_p
u_rxlev_ul_p=
u_rxlev_dl_p=
ncell_proc=0
missing_rpt=0
ba_alloc_proc=
link_fail=
link_about_to_fail=
Add_cell
Working Area
CELL 1
CELL 2
full_pwr_rfloss=
cell_bar_access_switch=
cell_bar_access_class=
emergency_class_switch=
report_resource_tch_f_high_water_mark=
report_resource_tch_f_low_water_mark=
rxlev_access_min=
dtx_required=
attachdetach=
ncc_of_plmn_allowed=
max_retran=
ms_txpwr_max_cch=
tx_integer= 10
radio_link_timeout=
reestablish_allowed=
cell_reselect_hysteresis=
cell_reselect_param_ind=
cell_bar_qualify=
cell_reselect_offset=
temporary_offset=
penalty_time=
rapid_pwr_down =
rpd_trigger =
rpd_offset =
rpd_period =
full_pwr_rfloss=
cell_bar_access_switch=
cell_bar_access_class=
emergency_class_switch=
report_resource_tch_f_high_water_mark=
report_resource_tch_f_low_water_mark=
rxlev_access_min=
dtx_required=
attachdetach=
ncc_of_plmn_allowed=
max_retran=
ms_txpwr_max_cch=
tx_integer= 10
radio_link_timeout=
reestablish_allowed=
cell_reselect_hysteresis=
cell_reselect_param_ind=
cell_bar_qualify=
cell_reselect_offset=
temporary_offset=
penalty_time=
rapid_pwr_down =
rpd_trigger =
rpd_offset =
rpd period =
3161
Issue 12 Rev 2
Cell Exercise
chg_element
Working Area
CELL 1
CELL 2
queue_management_information=
max_q_length_full_rate_channel=
max_q_length_sdcch=0
channel_reconfiguration_switch=
threshold =
max_number_of_sdcchs=
sdcch_need_low_water_mark=
sdcch_need_high_water_mark=
immediate_assign_mode=
rr_t3109=
rr_t3111=
rr_t3212=
handover_required_reject_switch=
rr_t3103=
rr_t3101=
interfer_bands,0=
interfer_bands,1=
interfer_bands,2=
interfer_bands,3=
interfer_bands,4=
rach_load_threshold=
rach_load_period=
ccch_load_period=
rr_t3105=
rr_ny1_rep=
dealloc_inact = 1000
ho_ack = 23000
rf_chan_rel_ack = 20000
queue_management_information=
max_q_length_full_rate_channel=
max_q_length_sdcch=0
channel_reconfiguration_switch=
threshold =
max_number_of_sdcchs=
sdcch_need_low_water_mark=
sdcch_need_high_water_mark=
immediate_assign_mode=
rr_t3109=
rr_t3111=
rr_t3212=
handover_required_reject_switch=
rr_t3103=
rr_t3101=
interfer_bands,0=
interfer_bands,1=
interfer_bands,2=
interfer_bands,3=
interfer_bands,4=
rach_load_threshold=
rach_load_period=
ccch_load_period=
rr_t3105=
rr_ny1_rep=
dealloc_inact = 10000
ho_ack = 23000
rf_chan_rel_ack = 20000
3162
Chapter 4
Device/Function Equipage
Issue 12 Rev 2
ii
Issue 12 Rev 2
Chapter 4
Device/Function Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device/Function Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
41
42
44
Kilo-Port Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
KSW Extension/Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
KSW Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
410
410
414
416
418
420
420
422
422
424
424
426
426
428
430
436
436
438
438
438
440
440
440
440
440
440
Typical Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
442
444
446
446
448
Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
450
452
16 KBIT/S RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
454
RTF Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
456
458
iii
Issue 12 Rev 2
466
468
470
Equipage Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
464
464
472
472
Device/Function Equipage
Issue 12 Rev 2
Device/Function Equipage
Objectives
On completion of this chapter the student will be able to:
S
41
Issue 12 Rev 2
42
Issue 12 Rev 2
CAB
BTS SITE
CELL
PCU
DYNET
AXCDR
CAGE
BSP
BTP
GPROC CSFP
DHP
EAS MSI
MMS *
(See Note
below)
DRI
RF_Unit
LCF OMF RSLF BTF
GSL MTL
OML
PATH
16 kbit/s RSL
RTF
CIC
CBL
XBL
64 kbit/s RSL
Associated RTF
43
Issue 12 Rev 2
44
Issue 12 Rev 2
BSS
Site
Cell
Cab
COMB
MCU (BTP)
NIU (MSI)
TCU (DRI)
GCLK
CSFP
Path
RTF
16 kbit/s RSL
64 kbit/s RSL
Associated RTF
sys02_4_3
45
Issue 12 Rev 2
Kilo-Port Switch
Kilo-Port Switch
To equip a KSW/TSW the following command must be entered:
equip (site number) KSW
The site number identifies the site in which the KSW is to be equipped. Valid entries are
0 (or BSC) to 100. This device cannot be equipped at an M-Cell site. After the initial
command a series of identifiers must be added.
46
Kilo-Port Switch
Issue 12 Rev 2
KSW Equipage
0-13
0-13
0/1
15-2
47
Issue 12 Rev 2
KSW Extension/Expansion
KSW Extension/Expansion
As the TDM highway function uses timeslot allocation, depending on the size of the site
one TDM highway may not be sufficient to support the digital boards or may be sufficient
to support a number of cages.
A single KSW (1 TDM highway) can be extended to five digital cages although extension
does not increase the TDM Highway capacity. It is simply the sharing of the available
timeslots over a number of digital cages.
In a large site 1 TDM highway may not be sufficient to meet the timeslot allocation
requirement of the digital boards. To overcome this the TDM highway can be expanded
by interconnecting up to four KSWs. This would increase the number of timeslots from
1024 to up to 4096 which is the maximum expansion configuration. When expanded
each KSW has access to any of the input ports of interconnected KSW but can only
output to its own 1024 ports.
Extension and expansion is achieved by the use of Kiloport Switch Extender boards. An
additional KSW can be equipped for redundancy, giving 4 KSW pairs when maximum
expansion is implemented.
48
KSW Extension/Expansion
Issue 12 Rev 2
R R R R
K
S
W
CLKX
1
CLKX
Switch cabinet
R R R R
K
S
W
6
Switch cabinet
Extension cabinets 25
L
R = Remote KSWXR
L = Local KSWXL
E = Expansion KSWXE
49
Issue 12 Rev 2
KSW Configuration
KSW Configuration
Overview
When maximum expansion is implemented at a site, four KSW pairs are required with full
redundancy.
Each active KSW has to be able to interface to each of the other three active KSWs via
KSWX EXP cards, as well as placing data onto its local highway. Shown opposite is a
schematic diagram showing full expansion, the cards shown as A0, A1, and A2 are
expansion slot positions 21, 22, 23 of the upper shelf and are filled with KSWX cards.
The interconnection between these cards is provided by optical fibre. Each of the four
highways is provided by a single KSW, redundancy is not shown.
410
KSW Configuration
Issue 12 Rev 2
KSW Expansion
A
0
Cage 1 (Pair 0)
A
1
A
2
K
S
W
Slot 27
A
0
Cage 2 (Pair 0)
A
1
K
S
W
A
2
A
0
Cage 3 (Pair 0)
Slot 27
A
1
A
2
K
S
W
Slot 27
A
0
Cage 4 (Pair 0)
A
1
K
S
W
Slot 27
HW 0
HW 1
HW 2
HW 3
Site 0
Sys02_4_5
411
A
2
Issue 12 Rev 2
KSW Configuration
The chg_ksw_ config field is used to determine the Switch managers viewpoint of the
KSW configuration, specifically the mapping of the TDM highway numbers for a particular
KSW pair and is used to equip the Switch Managers database.
Each KSW pair must be informed which highway is being received on which KSWX (A0,
A1 or A2) in the upper shelf. The following table is essential:
I/P
KSWX
0
1
2
3
ITSELF
A0
A1
A2
Shown opposite is an example using the schematic on the previous page. Take KSW
pair 2, physically in cage 3 of the site. H/W 0 is received on KSWX A0, using the table,
gives a value of 1. H/W 1 is received on KSWX A1, using the table gives a value of 2.
H/W 2 is not received by a KSWX card, the KSW in cage 3 is providing this highway,
using the table gives a value of 0 H/W 3 is received on KSWX A2, using the table gives a
value of 3.
412
KSW Configuration
Issue 12 Rev 2
KSW Configuration
EXAMPLE
H/W 1
H/W 2
H/W 3
chg_ksw_config
chg_ksw_config
chg_ksw_config
chg_ksw_config
413
Issue 12 Rev 2
Device ID
This field specifies the unique identifier for the GCLK, the card identified as 0 must be
fitted in card slot 5 and identifier 1 must be fitted in card slot 3.
Cage number
The parameter identifies the cage in which the GCLK is fitted.
414
Issue 12 Rev 2
GCLK Equipage
415
Issue 12 Rev 2
416
Issue 12 Rev 2
0/1
0/1
20/24 (BSC)
25/26 (RXCDR)
417
Issue 12 Rev 2
418
Issue 12 Rev 2
CSFP Equipage
0/1
0-13
0-13
0/1
15-2
18-25 (BSU)
25-26 (RXU)
419
Issue 12 Rev 2
Digital Host
Processor
The DHP will be required to support one instance of the RSS function at a BTS type 1.
This device cannot be equipped at an M-Cell site.
equip <site number> DHP
Issue 12 Rev 2
0/1 (InCell)
0/1 (card frame, MCell/Horizon)
15/14
421
Issue 12 Rev 2
GPROC Function
Preemption
In the event of a GPROC which is hosting a high priority function going out of service, but
where there is no alternative pool GPROC in an Enabled-Unlocked condition available to
host the function, the new feature GPROC Function Preemption searches for a
Busy-Unlocked GPROC running a lower priority function. If such a GPROC is found, the
lower priority function is pre-empted by the higher priority function.
For example at a Type 2 BSC the ATER channel allocation is hosted by the OMF (rather
than the BSP) to reduce the load on the BSP. IF the OMF goes out of service, calls
cannot be processed because the XBL also terminates on the OMF, and if the XBL is
disabled, the circuits are blocked. Thus the OMF becomes the highest priority function
and critical to the operation fo the BSC. For call processing to continue it must be
re-hosted by an alternative GPROC. Preemption is reasonable to allow this to occur, and
the function would move to a B-U GPROC hosting a lower-priority function.
The preemption function is enabled by the parameter.
chg_element pool_gproc_preemption whose settings are:
S
No preemption
Function level preemption operates by preempting a function of a lower priority than that
which has lost its host. If no lower priority functions are available on any GPROC, the
feature stops.
Intra-Function preemption first seeks a function of a lower priority, but if it does not find
one, then seeks a lower priority function within the function type which has lost its host
GPROC.
422
Issue 12 Rev 2
GPROC Equipage
0-13
0-13
0-1
15-2
18-25
18-25
18-25
25-26
chg_element
pool_gproc_preemption
0 = disable (no preemption)
1 = Function priority preemption
2 = Function and intrafunction
preemption
423
Issue 12 Rev 2
prompt 1 (DRIMs)
This prompt specifies the maximum number of DRIMs that the CA will allow the BTF to
support.
424
Issue 12 Rev 2
BTF Equipage
425
Issue 12 Rev 2
prompt 1 (identifier)
This field specifies the LCF identification (024)
prompt 2 (MTLs)
This prompt specifies the maximum number of MTLs that the LCF can manage.
The value 2 can only be entered for a GPROC2.
prompt 3 (CBLs)
This field specifies the maximum number of Cell Broadcast Links (CBLs) that the LCF
can manage.
Operations and
Maintenance
Function (OMF)
This GPROC device can only be equipped at a BSC type 2. When a BSC type 2 is
specified it causes the software controlling both the XBL and OML to migrate to the
available OMF. To equip an OMF the following command must be used:
equip (0 or bsc) OMF
(there are no prompts.)
426
Issue 12 Rev 2
LCF Equipage
OMF Equipage
427
Issue 12 Rev 2
Interleaving/deinterleaving
3.
channel coding/decoding
4.
5.
Encryption function
6.
428
Issue 12 Rev 2
429
Issue 12 Rev 2
cabinet id
This field identifies the cabinet in which the DRIM is fitted. Range 015.
DRIM type
This field identifies the DRIM type in use. For an In-Cell system the only allowable
response is 0 or the text string drim.
Cage
This identifies the cage in which the DRIM is fitted. This prompt is only presented in the
DRI board type is DRIM.
slot
This field identifies the card slot number in which the DRIM is fitted. This prompt is only
presented if the DRI board type is DRIM.
TRU id
This parameter is only necessary when equipping a DRIM in a Topcell Data Unit (TDU).
It is optional and can be replaced by a carriage return or alternatively a zero, for non TDU
cages. The range available is 06, to identify up to 6 TRUs. This prompt will only be
presented if the DRI board type is DRIM. This prompt will only be presented if the DRI
board type is DRIM.
430
Issue 12 Rev 2
DRIM Equipage
S equip (site number) DRI
Enter the 1st and 2nd DRI id:
(0-5) (0-11)
0-15
BSC 0 - 13
BTS 15 - 2
0-6
Typical Arrangement
D
R
C
U
D
R
C
U
D
R
C
U
D
R
C
U
D
R
C
U
D
R
C
U
Sys02_4_5a
431
Issue 12 Rev 2
This prompt is optional and a value should only be added if equipment sharing (future
feature) is implemented.
432
Issue 12 Rev 2
DRIM Equipage
NOTE:
S Non equipment sharing R TFs assigned on initialisation
S Equipment sharing R TFs must be specified
433
Issue 12 Rev 2
Cell id
This prompt requires the cell identity or the cell name that the DRIM is serving.
Antenna id
This parameter is used to engage the correct bay level offset tables calibrated by the
field engineer when the radio was commissioned. These calibrations are usually stored
in the 1st antenna memory area and hence this field is normally set to 1.
Diversity flag
This field specifies the use of diversity within the radio.
Tuneable Combining
This prompt determines whether the DRI utilises a combining device (RTC or CCB) or
not. The responses are yes or no.
Combiner Type
If the previous prompt declared that the DRI uses a combining device, this prompt
appears. It defines whether no combining is used, or whether the combining is in
controlled or non-controlled mode.
Combiner id
This optional parameter nominates the Combiner (e.g. RTC) being used by the DRIM.
The response consists of a single combiner device number between 0 and 13. The
combiner may be controlled by two DRIs.
Note: This parameter was modified in GSR 5 to simplify the equipage of COMB devices.
Whereas prior to GSR 5 the combiner referred to 2 separate processors, the updated
parameter refers to one processor only, and therefore the Combiner id is confined to a
single number between 0 and 13.
Cavity Number
If the Combiner id above has been entered the MMI will prompt for the cavity number.
Each RTC has 5 cavities (0 - 4) clearly labelled in hardware. The cavity in use by this
DRIM/DRCU should be entered in this field.
fm_cell_type
The field will nominate which receive coaxial connectors are in use in the diversity
summation. This feature is not supported at present.
Only certain combinations of the above two flags may be configured, they can be seen in
the table opposite.
When a DRCU is not in diversity mode the bottom connector (branch 1) should be used
as the coaxial input, fm_cell_type can be set to a 0, 1 or 2; in all cases the input to this
connector will be processed.
434
Issue 12 Rev 2
DRIM Equipage
S Enter the GSM cell ID where the DRI appears: GSM Cell
id/Cell name
S Enter antenna select number for this cell: 1-6
S Enter comb1st and 2nd ID: 0-13
S Enter cavity no:
0-5
R CU
DR CU
DR CU
Diversity flag
0
0
1
fm_cell_type
0
0 (non diversity)
4 (full diversity)
435
Issue 12 Rev 2
Cabinet id
This field identifies the cabinet in which the TCU is fitted. This entry will directly match
that entered in the equip cabinet command. If the cabinet id points to Horizonmacro/ext
and the frequency is PCS1900/GSM850 (tx_power_cap) must be set for a high power
cell.
FOX Port
The FOX card has 6 optical interfaces, each one being physically numbered on the front
panel. The TCU being equipped may be connected to one of these ports, the number of
the port is entered in this field. Again there is a direct correlation between the database
entry and the front panel labelling. In an M-cell6 cabinet the TCU would normally be
connected to the FOX.
The port number entered here could also be referring to one of the 2 ports (0 and 1) on
the front panel of the MCU. For this to be the case the previous prompt must be entered
as direct. For an M-cell micro TRX0 is referred to as port 0 and TRX1 is referred to as
port 1.
436
Issue 12 Rev 2
TCU Equipage
S
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
FOX
1 KM
FMUX
FOX
FMUX0
MCU
FMUX1
T
C
U
T
C
U
T
C
U
T
C
U
FMUX2
FOX
Master Card Frame
FMUX
Sys02_4_6
437
Issue 12 Rev 2
RTF Identifier
An RTF contains the frequency information for a particular cell and is equipped as a
function after the TCU. This first part of the identifier determines which group of RTFs
that the TCU must use to obtain its frequency information. A TCU belonging to a
particular redundancy group will automatically use an RTF from the same group, and
therefore, this field is optional. The second part of the field completes the RTF
identification and identifies a particular RTF within a group of RTFs. RTFs are identified
in an identical way to the TCUs.
This prompt is optional and a value should only be entered if equipment sharing (future
feature) is implemented.
Cell ID
This prompt requires the cell identity or the cell name that the TCU is serving.
Antenna Identity
This enables two different mechanisms to correctly operate within the receiver RF
sub-system. Firstly, this parameter points to the bay level offset antenna memory area to
be engaged by the TCU. These offsets will have been calibrated when the TCU
hardware was initially commissioned.
The second use for this entry is only meaningful when an Integrated Antenna Distribution
Unit (IADU) is in use (M-cell6). This entry points to the DLNB connection point on the
IADU which is to be connected through to the TCU. The TCU will communicate this
parameter to the IADU for the correct switch to be enabled.
Shown opposite is a typical example of a 4/4/4 configuration. Given the antenna settings
at the bottom of the diagram, the internal switching of the IADU is shown. The third
Diversity Low Noise Block (DLNB) port on the IADU can be used to extend the receive
signal to an IADU in a different cabinet, the internal IADU connections to make the
extension port effective are enabled by dip switch settings on the IADU itself. Diversity
connections can be seen as ghosted lines in the diagram.
438
Issue 12 Rev 2
TCU Equipage
D
L
N
B
1
0
I
A
D
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
439
Issue 12 Rev 2
Use of Tuneable
Combiner
This parameter informs the system whether the TCU is using a tuneable combiner or not.
Combiner Type
This optional parameter describes which type of combiner is in use. This specifies
whether no combining is used by this DRI (enter 0); or if combining is used whether this
DRI is controlling the combiner (enter 1) or not controlled by this DRI (enter 2). Up to two
DRIs may exercise control over it, and up to 6 DRIs total may be connected.
0 = none
1 = non-controlling
2 = controlling
Combiner
Identity
This parameter informs the system of the combiner number. The prompt is mandatory if
a combiner has been declared.
Cavity Number
Only if the combiner id (above) has been entered will the MMI prompt for the cavity
number. Each CCB has 3 cavities, each being physically numbered from right to left (0 5), this field points to the cavity in use by this TCU.
Diversity Flag
This field specifies the use of diversity within the radio.
fm cell type
This field will nominate which receive coaxial connectors are in use in the diversity
summation. This feature is not supported at present.
Only certain combinations of the above two flags may be configured, they can be seen in
the table opposite.
When a DRCU is not in diversity mode the bottom connector (branch 1) should be used
as the coaxial input, fm_cell_type can be set to a 0, 1 or 2 in all cases the input to this
connector will be processed.
Note:
The modify_value command has been updated under GSR 5 to enable the operator to
modify the following configuration parameters of the combiner; Combiner Address, DRI
Combining Type, Combiner id and Cavity. These may be modified after the device has
been equipped, if this is required.
440
Issue 12 Rev 2
TCU Equipage
0-13
0-5
R CU
DR CU
DR CU
Diversity flag
0
0
1
fm_cell_type
0
0 (non diversity)
4 (full diversity)
441
Issue 12 Rev 2
Typical Examples
Typical Examples
442
id
cab
FOX/FMUX
port
RTF
cell
ant
use CCB
CCB (not controlled)
comb
cav
diversity disabled
cell type
equip 12 dri
01
0
drim
15
9
<CR>
<CR>
2 3 4 1 0 368 39
1
no
0
<CR>
<CR>
0
0
id
cab
type
cage
slot
TRU
RTF
Cell
Ant
use RTC
none
comb
cav
diversity disabled
cell type
id
cab
FOX/FMUX
port
RTF
cell
ant
no comb
none
comb
cav
diversity disabled
cell type
Typical Examples
Issue 12 Rev 2
Without RTC:
equip 12 DRI
01
0
drim
15
9
<CR>
<CR>
2 3 4 10 368 39
1
yes
2
0
1
0
0
equip 12 DRI
01
0
drim
15
9
<CR>
<CR>
2 3 4 10 368 39
1
no
0
<CR>
<CR>
0
0
equip 12 DRI
01
0
fox
1
<CR>
2 3 4 10 368 39
1
yes
1
1
1
0
4
equip 12 DRI
01
0
4
1
<CR>
2 3 4 10 368 39
1
no
0
<CR>
<CR>
0
4
443
Issue 12 Rev 2
444
Issue 12 Rev 2
COMB Equipage
0-13
0-255
445
Issue 12 Rev 2
In-Cell
Identifier
The field specifies a unique identifier on site basis
Cage
This prompt specifies the cage in which the termination card is fitted.
Slot
The field specifies the slot in which the module is fitted, restrictions exist depending upon
default positions and cage type (BSU and RXU)
Type
The field specifies the module type fitted, MSI, XCDR or E1/T1 converter.
446
Issue 12 Rev 2
MSI/XCDR Equipage
InCell
equip (site number) MSI
S Enter the MSI identifier:
0-55 (BSC)
0-9 (BTS)
0-71 (RXCDR)
0-15
0 - MSI
1 - XCDR
2 - GDP
7 - msi_ext_hdsl
12 - RF_unit
(Horizonoffice only)
255 - msi2_conv
447
Issue 12 Rev 2
M-Cell/Horizon
Identifier
Valid identifiers are dependent on site type, either M-Cell6/2 or M-Cellmicro/M-Cellcity.
Only identifier 0 is valid at an M-Cellmicro/M-Cellcity.
Card frame
Two card frames exist in an M-Cell6 and an M-Cell2 and hence the identifies 0 and 1.
Only identifier 0 is valid at an M-Cellmicro/M-Cellcity.
Slot
This field identifies the card slot in which the NIU is fitted. 0 is the only possible value for
M-Cell2 and M-Cellmicro/M-Cellcity.
Type
This field states what type of module is used, NIU, NIU with integrated HDSL modem,
NIU with external HDSL modem.
448
Issue 12 Rev 2
MSI/XCDR Equipage
MCell/Horizon
equip (site number) MSI
S Enter the MSI identifier:
0-1 MCell2
0-3 MCell6/HorizonMacro
0 MCellmicro/MCellcity
NIU
9=
3=
8=
9=
0-1
niu_ext_hdsl
niu
niu_hdsl
niu_ext_hdsl
MCell2
MCell6
MCellcity
MCellarena
E1 or HDSL
16 or 32
Master or slave
E1 or HDSL
16 or 32
Master or slave
MSC
MSC
E1
T1
XCDR
E1
MSI2
255
1
0
MSI
XCDR
1
0
MSI2
E1
R
X
C
D
R
T1
MSI
MSI2
B
S
C
B
S
C
Sys02_4_8
land_layer1_mode=0
EMOTOROLA LTD. 2001
land_layer1_mode=1
SYS02 GSR5/AGSR: BSS Database
449
Issue 12 Rev 2
Path
Path
The specific transmission route which traffic and signalling will take from a BTS, perhaps
via intermediate BTSs, to the BSC is largely determined by the software. To enable this
to occur Paths have to be built using the available MSI cards and port numbers through
each BTS, starting from the BSC. The path command is very simple and is as follows:
equip 0 PATH
450
Path
Issue 12 Rev 2
Path Equipage
BSC
0-55, 0 or 1
BTS
0-9, 0 or 1 (Non MCell)
0-3, 0 or 1 (MCell 6Horizonmacro)
0-1, 0 or 1 (MCell 2)
0, 0 or 1 (MCell Micro)
BSC
0-55, 0 or 1
BTS
0-9, 0 or 1 (Non MCell)
0-3, 0 or 1 (MCell 6Horizonmacro)
0-1, 0 or 1 (MCell 2)
0, 0 or 1 (MCell Micro)
Repeat
451
Issue 12 Rev 2
equip <
> PATH
equip <
> PATH
terminating site id
path id
BSC MSI id
Site id
upstream MSI id
downstream MSI id
Site id
upstream MSI id
downstream MSI id
Site id
upstream MSI id
452
Issue 12 Rev 2
BSC
MSI 3
Port 0
Port 0
MSI 1
M
S
I
3
BTS 14
MSI 1
Port 0
Port 0
Port 0
Port 0
NIU 0
MSI 3
BTS 15
N
I
U
1
Port 0
Port 0
M
S
I
1
BTS 16
Sys02_4_9
453
Issue 12 Rev 2
16 KBIT/S RSL
16 KBIT/S RSL
The purpose of the 16 kbit/s RSL is to reduce the interconnection costs between the
BSC and BTS (A-bis interface) for single carrier sites in particular.
At present, a single carrier BTS requires three E1/T1 64 kbit/s timeslots; one for the 64
kbit/s RSL and two for the 16 kbit/s traffic channels. The two 64 kbit/s timeslots
dedicated to the traffic channels can accommodate eight traffic channels normally.
In the case of a single carrier site, it is not possible to use all eight traffic channels of the
two 64 kbit/s timeslots. The reason is that, in the case of a single carrier site, the carrier
will be the BCCH carrier, and the air interface timeslot zero of the BCCH carrier is
reserved for BCCH information. This information is generated at the BTS not the BSC.
The TSW at the BTS routes the traffic channels from the two specified timeslots on the
A-bis interface to the dedicated radio for transmission.
Due to this the traffic channel on the A-bis interface corresponding to the timeslot zero on
the air interface cannot be used because if it was, the information mapped from the A-bis
interface would interfere with the BCCH information. This results in one 16 kbit/s
sub-channel unused on the A-bis interface, a waste of resources.
With the introduction of the 16 kbit/s RSL it is possible to place it on this unused
sub-channel because the RSL is not transmitting on the air interface. The advantage is
that it frees up one 64 kbit/s timeslot on the A-bis interface reducing the requirement to
only two 64 kbit/s timeslots. This operates with M-Cell BTSs and In-Cell BTSs using
KSW switching.
454
16 KBIT/S RSL
Issue 12 Rev 2
FullyEquipped
RTF
NonBCCH
BCCH
16 kbit/s
BTS only
16 kbit/s
BTS only
Associated
16 kbit/s RSL
Configuration
No Associated
16 kbit/s RSL
2
Associated
16 kbit/s RSL
3
No Associated
16 kbit/s RSL
4
Timeslot X
Timeslot Y
16 kbit/s subchannel unavailable for use
Key
455
Issue 12 Rev 2
RTF Types
RTF Types
Type
Options
1
2
456
RTF Types
Issue 12 Rev 2
Sub-equipped RTF
SubEquipped
RTF
NonBCCH
BCCH
16 kbit/s
BTS only
16 kbit/s
BTS only
Associated
16 kbit/s RSL
Configuration
No Associated
16 kbit/s RSL
6
Associated
16 kbit/s RSL
No Associated
16 kbit/s RSL
Timeslot X
Timeslot Y
Key
457
Issue 12 Rev 2
Capacity of carrier
This field specifies whether the capacity of the RTF if full or sub. This prompt will not
display if the RTF is equipped to a BTS using dynamic allocation.
Carrier type
This field specifies whether this RTF supports a BCCH or non-BCCH carrier.
Primary path
This field identifies which path is to be used for the 2 x 64kbs timeslots resulting from this
RTF. This prompt is only presented for RTFs at remote BTS sites. This prompt will not
display if the RTF is equipped to a BTS using dynamic allocation.
Secondary path
This field identifies which optional secondary path will support the traffic from this RTF,
should the primary path fail. This prompt is only presented for RTFs at remote BTS sites.
This prompt will not display if the RTF is equipped to a BTS using dynamic allocation.
Cell id/name
An RTF is dedicated to a particular cell, this identity should be the same as that
nominated in the DRIM/TCU equippage for the same redundancy group.
Frequency
This field allocates the GSM radio channel number and therefore the downlink and uplink
frequencies. The channels which maybe specified are as follows:
GSM 900
BCCH
NON_BCCH
1124
1124
SM 900 (Extended)
BCCH_
NON_BCCH
1124
0, 1124,
9751023
DCS 1800
BCCH
NON_BCCH
512885
512885
PCS 1900
BCCH
NON_BCCH
BCCH
NON_BCCH
512810
512810
128251
128251
GSM850
458
Issue 12 Rev 2
RTF Equipage
equip (site number) RTF
459
Issue 12 Rev 2
2.
3.
The TSC is equipped on a TDMA timeslot basis. A GSM Recommendation (Rec 5.02)
specifies that the TSC of timeslot 0 of the BCCH carrier should be equal to the BCC of
the cell. All 8 TSCs are entered on a single line rather like the FHIs above.
KSW pair
All traffic channel data will be passed via the KSW in the BSS. The KSW will interface
Traffic Channels (TCH) data being received from an MSI/XCDR and perform the
interchange function to route that data to the correct DRIM and TCH data received from
a DRIM will be routed to an MSI/XCDR via the KSW. On an RTF basis the KSW pair
assigned to support that RTF must be equipped. This parameter will not appear in the
case of M-Cell sites.
Cell zone
This prompt only appears for non-BCCH carriers and only if the concentric cells feature is
unrestricted 0= Outer, 1 = Inner zone.
460
Issue 12 Rev 2
RTF Equipage
461
Issue 12 Rev 2
Extended range
This prompt only appears if the extended range feature is unrestricted. The extended
range timeslots maybe configured on outer zone carriers if the concentric cell feature is
unrestricted. Extended range timeslots are not configurable for inner zone timeslots.
SDCCH load
This prompt specifies the maximum number of SDCCH/8 timeslots configurable per
carrier. If Concentric Cells feature is unrestricted then the system displays this prompt
for outer zone carriers (cell_zone= 0) only.
462
Issue 12 Rev 2
RTF Equipage
DCS1800
0 - 39 dBm
.
.
.
21 - 3dBm
0 - 4 (Default 0)
463
Issue 12 Rev 2
First device ID
This identifies the site number associated with the RSL.
Second device ID
This identifies a particular RSL associated with the site.
Path ID
Identifies the unique path ID.
Optional
Parameters
LAPD T200 timer
This is the maximum time the LAPD (Layer 2) transmitter will wait for an
acknowledgement before making a retransmission.
LAPD N200
This is the maximum number of retransmissions a transmitter will make.
LAPD K
This is the maximum number of unacknowledged Information frames a transmitter will
allow before holding up transmission.
464
Issue 12 Rev 2
RSL Equipage
Optional Parameters
S Enter the LAPD T200 timer value for this device: 1400-5000
(ms, values in multiples of 50)
Default = 2500
S Enter the LAPD N200 value for this device: 1-5 Default = 3
S Enter the LAPD K value for this device: 1-10 Default = 7
465
Issue 12 Rev 2
466
Issue 12 Rev 2
MTL Equipage
S Enter the first MMS description for this MTL: 0-55 (MSI)
S Enter the second MMS description for this MTL: 0-1 (port)
467
Issue 12 Rev 2
468
Issue 12 Rev 2
OML Equipage
S Enter the first MMS description for this OML: 0-55 (BSC)
0-71 (RXCDR)
469
Issue 12 Rev 2
470
Issue 12 Rev 2
CBC
X.25
BSC
CBC
X.25
RXCDR
BSC
Sys02_4_11
T1: 1-24
E1: 1-31
471
Issue 12 Rev 2
Equipage Exercise
Equipage Exercise
Using the following information and answer sheets provided, fill in the necessary details
to equip each function and device.
Site Details
1.
2.
There are two paths equipped to the site 0 and 1, 0 being the primary path for all
traffic and signalling.
3.
4.
5.
6.
472
Equipage Exercise
Issue 12 Rev 2
Equipage Exercise
BCCH Channel = 48
NonBCCH Channel = 64
BCCH Channel = 53
D
R
C
U
D
R
C
U
D
R
C
U
Site 12
SYS02_Ch4_12
473
Issue 12 Rev 2
Equipage Exercise
474
GPROC 2
GPROC 1
XCDR 1 MSI 1
DRI(M) 4 XCDR 2 MSI 2
DRIX 1
DRIX 0
EXP KSWX B0
EXP KSWX B1
CLKX A0EXP KSWX B2
CLKX A1EXP KSWX B0
CLKX A2EXP KSWX B1
CLKX B0EXP KSWX B2
CLKX B1EXP KSWX B3
CLKX B2EXP KSWX B4
LCLKSWX A
LCLKSWX B
Equipage Exercise
BTC1
DRIX 2
KS1
L1 UL
KSW/TSW B
DRIX 3
DR0
L3
475
GCLK B
DRIX 4
GK0
L5
GCLK A
XCDR 11MSI 11
DRIX 5
MS3
L7 L6
Sys02_4_13
PIX0 or BBBX
DR1
L8
XCDR 9 MSI 9
PIX1 or BBBX
DR2
XCDR 7 MSI 7
PIX2 or BBBX
MS2
LANX A
DR3
XCDR 3 MSI 3
LANX A
DR4
EXP KSWX A0
MS1
GPROC 0
EXP KSWX A1
DR5
GPROC 3
EXP KSWX A2
Issue 12 Rev 2
GPROC 4
RMT KSWX A0
KS0
GPROC 5
RMT KSWX A1
MS0
GPROC 6
RMT KSWX A2
SITE 12 BSU
GPROC 7
RMT KSWX A3
Site 12 BSU
A10
spare
RMT KSWX A4
A11
A12
KSW/TSW A
U28 U27 U26 U25 U24 U23 U22 U21 U20 U19 U18 U17 U16 U15 U14 U13 U12 U11 U10 U9 U8 U7 U6 U5 U4 U3 U2 U1 U0
L28 L27 L26 L25 L24 L23 L22 L21 L20 L19 L18 L17 L16 L15 L14 L13 L12 L11 L10 L9
BTC0
Issue 12 Rev 2
equip _ _ _ _ KSW
____
____
____
____
equip _ _ _ _ BTP
____
____
____
____
equip _ _ _ _DHP
____
____
____
____
equip _ _ _ _ GCLK
____
____
equip _ _ _ _ MSI
____
____
____
____
equip _ _ _ _ RSL
____
____
____
____
____
____
476
Issue 12 Rev 2
equip _ _ _ _ DRI
____
____
____
____
____
____
____
____
____
____
____
____
equip _ _ _ _ DRI
____
____
____
____
____
____
____
____
____
____
____
____
477
Issue 12 Rev 2
equip _ _ _ _ DRI
____
____
____
____
____
____
____
____
____
____
____
____
equip _ _ _ _ RTF
____
____
____
____
____
____
____
____
____
equip _ _ _ _ RTF
____
____
____
____
____
____
____
____
____
478
Issue 12 Rev 2
equip _ _ _ _ RTF
____
____
____
____
____
____
____
____
____
479
Issue 12 Rev 2
480
Issue 12 Rev 2
Appendix A
GSM Channel Frequency Table
App Ai
Issue 12 Rev 2
Channel
Decimal
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
App Aii
RX Frequency
Hexadecimal
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
11
12
13
14
15
16
17
18
19
1A
1B
1C
1D
1E
1F
20
21
22
23
24
25
26
27
28
TX Frequency
mHz
mHz
890.20
890.40
890.60
890.80
891.00
891.20
891.40
891.60
891.80
892.00
892.20
892.40
892.60
892.80
893.00
893.20
893.40
893.60
893.80
894.00
894.20
894.40
894.60
894.80
895.00
895.20
895.40
895.60
895.80
896.00
896.20
896.40
896.60
896.80
897.00
897.20
897.40
897.60
897.80
898.00
935.20
935.40
935.60
935.80
936.00
936.20
936.40
936.60
936.80
937.00
937.20
937.40
937.60
937.80
938.00
938.20
938.40
938.60
938.80
939.00
939.20
939.40
939.60
939.80
940.00
940.20
940.40
940.60
940.80
941.00
941.20
941.40
941.60
941.80
942.00
942.20
942.40
942.60
942.80
943.00
Issue 12 Rev 2
Channel
Decimal
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
RX Frequency
Hexadecimal
29
2A
2B
2C
2D
2E
2F
30
31
32
33
34
35
36
37
38
39
3A
3B
3C
3D
3E
3F
40
41
42
43
44
45
46
47
48
49
4A
4B
4C
4D
4E
4F
50
TX Frequency
mHz
mHz
898.20
898.40
898.60
898.80
899.00
899.20
899.40
899.60
899.80
900.00
900.20
900.40
900.60
900.80
901.00
901.20
901.40
901.60
901.80
902.00
902.20
902.40
902.60
902.80
903.00
903.20
903.40
903.60
903.80
904.00
904.20
904.40
904.60
904.80
905.00
905.20
905.40
905.60
905.80
906.00
943.20
943.40
943.60
943.80
944.00
944.20
944.40
944.60
944.80
945.00
945.20
945.40
945.60
945.80
946.00
946.20
946.40
946.60
946.80
947.00
947.20
947.40
947.60
947.80
948.00
948.20
948.40
948.60
948.80
949.00
949.20
949.40
949.60
949.80
950.00
950.20
950.40
950.60
950.80
951.00
App Aiii
Issue 12 Rev 2
Channel
RX Frequency
Decimal
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
207
208
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
App Aiv
Hexadecimal
51
52
53
54
55
56
57
58
59
5A
5B
5C
5D
5E
5F
60
61
62
63
64
65
66
67
68
69
6A
6B
6C
6D
6E
6F
70
71
72
73
74
75
76
77
78
79
7A
7B
7C
mHz
906.20
906.40
906.60
906.80
907.00
907.20
907.40
907.60
907.80
908.00
908.20
908.40
908.60
908.80
909.00
909.20
909.40
909.60
909.80
910.00
910.20
910.40
910.60
910.80
911.00
911.20
911.40
911.60
911.80
912.00
912.20
912.40
912.60
912.80
913.00
913.20
913.40
913.60
913.80
914.00
914.20
914.40
914.60
914.80
TX Frequency
mHz
951.20
951.40
951.60
951.80
952.00
952.20
952.40
952.60
952.80
953.00
953.20
953.40
953.60
953.80
954.00
954.20
954.40
954.60
954.80
955.00
955.20
955.40
955.60
955.80
956.00
956.20
956.40
956.60
956.80
957.00
957.20
957.40
957.60
957.80
958.00
958.20
958.40
958.60
958.80
959.00
959.20
959.40
959.60
959.80
Issue 12 Rev 2
Appendix B
Hexadecimal/Decimal Conversion Chart
App Bi
Issue 12 Rev 2
Channel
Channel
Decimal
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
App Bii
Hexadecimal
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
10
11
12
13
14
15
16
17
18
19
1A
1B
1C
1D
1E
1F
20
21
22
23
24
25
26
27
28
29
2A
2B
2C
2D
2E
2F
30
31
32
33
34
35
36
37
Decimal
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
Channel
Hexadecimal
38
39
3A
3B
3C
3D
3E
3F
40
41
42
43
44
45
46
47
48
49
4A
4B
4C
4D
4E
4F
50
51
52
53
54
55
56
57
58
59
5A
5B
5C
5D
5E
5F
60
61
62
63
64
65
66
67
68
69
6A
6B
6C
6D
6E
Decimal
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
Hexadecimal
6F
70
71
72
73
74
75
76
77
78
79
7A
7B
7C
7D
7E
7F
80
81
82
83
84
85
86
87
88
89
8A
8B
8C
8D
8E
8F
90
91
92
93
94
95
96
97
98
99
9A
9B
9C
9D
9E
9F
A0
A1
A2
A3
A4
A5
Issue 12 Rev 2
Channel
Decimal
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
Channel
Hexadecimal
A6
A7
A8
A9
AA
AB
AC
AD
AE
AF
B0
B1
B2
B3
B4
B5
B6
B7
B8
B9
BA
BB
BC
BD
BE
BF
C0
C1
C2
C3
Decimal
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
Channel
Hexadecimal
C4
C5
C6
C7
C8
C9
CA
CB
CC
CD
CE
CF
D0
D1
D2
D3
D4
D5
D6
D7
D8
D9
DA
DB
DC
DD
DE
DF
E0
E1
Decimal
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
Hexadecimal
E2
E3
E4
E5
E6
E7
E8
E9
EA
EB
EC
ED
EE
EF
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
FA
FB
FC
FD
FE
FF
App Biii
Issue 12 Rev 2
App Biv
Issue 12 Rev 2
Appendix C
SACCH Multiframes
App Ci
Issue 12 Rev 2
App Cii
0.0471
0.942
1.883
2.825
3.767
4.708
5.650
6.592
7.533
8.475
9.417
10.358
11.300
12.242
13.183
14.125
15.067
16.008
16.950
17.892
18.833
19.775
20.717
21.658
22.600
23.542
24.483
25.425
26.367
27.308
28.250
29.192
30.133
1
2
4
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
50
52
54
56
58
60
62
64
0.480
0.960
1.920
2.880
3.841
4.801
5.761
6.721
7.681
8.641
9.601
10.561
11.522
12.482
13.442
14.402
15.362
16.322
17.282
18.242
19.203
20.163
21.123
22.083
23.043
24.003
24.963
25.923
26.884
27.844
28.804
29.764
30.724
Issue 12 Rev 2
Appendix D
Database Script Building Charts
App Di
Issue 12 Rev 2
BSC
EQUIP SITE
EQUIP CABINET
EQUIP CAGE
CHANGE ELEMENT
(SITE CONFIGURATION)
EQUIP DEVICES
ADD CIRCUITS
KSW CONFIGURATION
App Dii
Issue 12 Rev 2
RXCDR
EQUIP RXCDR
EQUIP ABSS
EQUIP CABINET
EQUIP CAGE
EQUIP DEVICES
(DIGITAL BOARDS AND FUNCTIONS)
CHANGE ELEMENT
(SITE CONFIG/TIMERS)
SYS02_AppD_01
App Diii
Issue 12 Rev 2
BSS
EQUIP BSS
EQUIP AXCDR
EQUIP CABINET
EQUIP CAGE
CHANGE ELEMENT
(SITE CONFIGURATION)
ADD CIRCUITS
KSW CONFIGURATION
SYS02_AppD_02
App Div
Issue 12 Rev 2
BTS
App Dv
Issue 12 Rev 2
EQUIP SITE
EQUIP CABINET
EQUIP CAGE
CHANGE ELEMENT
(SITE CONFIG/TIMERS)
ADD CELL
EQUIP DEVICES
KSW CONFIGURATION
H/O PARAMETERS
App Dvi
Issue 12 Rev 2
PATH
EQUIP PATH
EQUIP RSL
EQUIP RTF
ADD NEIGHBOUR
App Dvii
Issue 12 Rev 2
App Dviii
Issue 12 Rev 2
Appendix E
add_cell Command Prompts
App Ei
Issue 12 Rev 2
Input
freq_type=x
Range
1 (pgsm)
2 (egsm)
4 (dcs1800)
8 (pcs1900)
Default
None
bsic=x
0 to 63
None
wait_indication_parameters=x
0 to 255
ccch_conf=x
0, 1, 2, 4, 6
bs_ag_blks_res=x
0 to 7
bs_pa_mfrms=x
0 to 7
extended_paging_active=x
0 or 1
number_sdcchs_preferred=x
0 to 44
(if ccch_conf=1)
8 to 48
(if ccch_conf1)
en_incom_ho=x
0 or 1
intra_cell_handover_allowed=x
0 to 2
inter_cell_handover_allowed=x
0 to 3
number_of_preferred_cells=x
1 to 16
16
ho_margin_def=x
63 to 63
handover_recognized_period=x
2 to 64
ul_rxqual_ho_allowed=x
0 or 1
dl_rxqual_ho_allowed=x
0 or 1
ul_rxlev_ho_allowed=x
0 or 1
dl_rxlev_ho_allowed=x
0 or 1
sdcch_ho=x
0 or 1
sdcch_timer_ho=x
1 to 31
interfer_ho_allowed=x
0 or 1
pwr_handover_allowed=x
0 or 1
ms_distance_allowed=x
0 or 1
mspwr_alg=x
0 or 1
handover_power_level=x
2 to 19
None
App Eii
Issue 12 Rev 2
Input
pwrc=x
Range
0 or 1
Default
1
. . . continued
intave=x
1 to 31
timing_advance_period
1 to 31
ms_p_con_interval=x
0 to 31
ms_p_con_ack=x
0 to 31
ms_power_control_allowed=x
0 or 1
bts_p_con_interval=x
0 to 31
bts_p_con_ack=x
0 to 31
bts_power_control_allowed=x
0 or 1
(0 for M-Cellmicro)
pow_inc_step_size=x
2 to 4, 6 EVEN
pow_red_step_size=x
2 to 4 EVEN
max_tx_bts=x
0 to 21
(0 to 6 for
M-Cellmicro)
max_tx_ms=x
5 to 39 (GSM900)
0 to 30 (DCS1800
and PCS1900)
See Note, below.
39
30
Note:
The range of values for max_tx_ms is system-dependent:
Odd values in the range of 5 39 for GSM900 (PGSM and EGSM).
Even values in the range of 0 30 for DCS1800 and PCS1900.
Enter receive level minimum default:
rxlev_min_def=x
0 to 63
15
ms_txpwr_max_def=x
5 to 39 (GSM900)
0 to 30 (DCS1800
and PCS1900)
See Note, above
39
30
decision_alg_num=x
0 to 31
decision_1_dl_rxlev_av_h=x
0 to 3
decision_1_dl_rxlev_av_ih=x
0 to 3
decision_1_dl_rxlev_av_p=x
0 to 3
decision_1_dl_rxqual_av_h=x
0 to 3
decision_1_dl_rxqual_av_p=x
0 to 3
decision_1_n1=x
1 to 31
decision_1_n2=x
1 to 31
App Eiii
Issue 12 Rev 2
Input
Range
Default
decision_1_n3=x
1 to 31
decision_1_n4=x
1 to 31
decision_1_n5=x
1 to 31
decision_1_n6=x
1 to 31
1
. . . continued
decision_1_n7=x
1 to 31
decision_1_n8=x
1 to 31
decision_1_ncell_rxlev_av_h_
calc=x
0 to 3
decision_1_p1=x
1 to 31
decision_1_p2=x
1 to 31
decision_1_p3=x
1 to 31
decision_1_p4=x
1 to 31
decision_1_p5=x
1 to 31
decision_1_p6=x
1 to 31
decision_1_p7=x
1 to 31
decision_1_p8=x
1 to 31
decision_1_p_bgt_rxlev_av_h=x
0 to 3
decision_1_tim_adv_av_alg=x
0 to 3
decision_1_ul_rxlev_av_h=x
0 to 3
decision_1_ul_rxlev_av_ih=x
0 to 3
decision_1_ul_rxlev_av_p=x
0 to 3
decision_1_ul_rxqual_av_h=x
0 to 3
decision_1_ul_rxqual_av_p=x
0 to 3
alt_qual_proc=x
0 or 1
If alt_qual_proc = 0,
0 to 1810
If alt_qual_proc = 1,
0 to 7
226 BER
or
4 QBand
If alt_qual_proc = 0,
0 to 1810
If alt_qual_proc = 1,
0 to 7
226 BER
or
4 QBand
If alt_qual_proc = 0,
0 to 1810
If alt_qual_proc = 1,
0 to 7
28 BER
or
1 QBand
App Eiv
u_rxqual_ul_p=x
Issue 12 Rev 2
Input
Range
Default
u_rxqual_dl_p=x
If alt_qual_proc = 0,
0 to 1810
If alt_qual_proc = 1,
0 to 7
28 BER
or
1 QBand
l_rxqual_ul_h=x
If alt_qual_proc = 0,
0 to 1810
If alt_qual_proc = 1,
0 to 7
453 BER
or
5 QBand
l_rxqual_dl_h=x
If alt_qual_proc = 0,
0 to 1810
If alt_qual_proc = 1,
0 to 7
453 BER
or
5 QBand
. . . continued
l_rxlev_ul_h=x
0 to 63
None
l_rxlev_dl_h=x
0 to 63
None
u_rxlev_ul_ih=x
0 to 63
None
u_rxlev_dl_ih=x
0 to 63
None
ms_max_range=x
0 to 63
None
l_rxlev_ul_p=x
0 to 63
None
l_rxlev_dl_p=x
0 to 63
None
u_rxlev_ul_p=x
0 to 63
None
u_rxlev_dl_p=x
0 to 63
None
ncell_proc=x
0 or 1
None
missing_rpt=x
0 or 1
None
ba_alloc_proc=x
0 or 1
None
link_fail=x
0 to 15
link_about_to_fail=x
0 to 15
full_pwr_rfloss=x
0 or 1
cell_bar_access_switch=x
0 or 1
cell_bar_access_class=x
0 to
ffff(hexadecimal)
emergency_class_switch=x
0 or 1
report_resource_tch_f_high_
water_mark=x
0 to 255
None
report_resource_tch_f_low_
water_mark=x
0 to 255
None
App Ev
Issue 12 Rev 2
Input
Range
Default
Note:
The value for report_resource_tch_f_high_ water_mark must be set less than the value for
report_resource_tch_f_low_water_mark. The system will reject the add_cell command if the
report_resource_tch_f_high_ water_mark is greater than the report_resource_tch_f_low_water_mark.
Enter receive level access minimum:
rxlev_access_min=x
0 to 63
None
dtx_required=x
0 to 2
attach_detach=x
0 or 1
ncc_of_plmn_allowed=x
0 to 255
255
max_retran=x
0 to 3
ms_txpwr_max_cch=x
2 to 19
tx_integer=x
0 to 15
radio_link_timeout=x
0 to 15
reestablish_allowed=x
0 or 1
0
. . . continued
cell_reselect_hysteresis=x
0 to 7
None
cell_reselect_param_ind=x
0 or 1
cell_bar_qualify=x
0 or 1
cell_reselect_offset=x
0 to 63
temporary_offset=x
0 to 7
penalty_time=x
0 to 31
rapid_pwr_down=x
0 or 1
rpd_trigger=x
0 to 63
45
rpd_offset=x
0 to 63
rpd_period=x
1 to 32
App Evi
Issue 12 Rev 2
Appendix F
Typical BSS Script
App Fi
Issue 12 Rev 2
Issue 12 Rev 2
0
20
equip 0 CSFP
0
0
18
equip 0 GPROC
1
0
19
equip 0 GPROC
3
0
21
equip 0 GPROC
4
0
22
equip 0 LCF
0
0
0
equip 0 LCF
1
0
0
equip 0 LCF
2
1
1
equip 0 MSI
1
0
16
0
equip 0 MSI
2
0
15
0
equip 0 MSI
3
0
14
0
equip 0 MSI
4
0
13
0
EMOTOROLA LTD. 2001
App Fiii
Issue 12 Rev 2
equip 0 GCLK
0
0
no
no
no
equip 0 GCLK
1
0
no
no
no
# XBL to BSC 1
equip bsc XBL
0
64
1
0
25
2500
3
7
equip 0 MTL
0
1
0
16
equip 0 OML
0
1
0
1
equip 0 CBL
0
1
0
8
sys03test
cbctest
# TIMER CONFIGURATION
chg_element SS7_L3_T1 850 0
chg_element SS7_L3_T2 1350 0
chg_element SS7_L3_T12 1150 0
chg_element SS7_L3_T13 1150 0
chg_element SS7_L3_T14 2500 0
chg_element SS7_L3_T17 1150 0
chg_element SS7_L3_T22 270000 0
chg_element SS7_L3_T23 270000 0
chg_element SS7_SLT_T1 8000 0
chg_element SS7_L3_T4 850 0
chg_element SS7_L3_T5 850 0
chg_element SS7_L2_T1 45000 0
App Fiv
Issue 12 Rev 2
App Fv
Issue 12 Rev 2
chg_element stat_interval 60 0
chg_element option_alg_a5_1 1 0
chg_element option_alg_a5_2 1 0
chg_a5_alg_pr 1 2 0
chg_element option_emergency_preempt 1 0
chg_ksw_config 0 0 0 1 2 3
chg_eas_alarm 1 2 High Temperature
chg_eas_alarm 2 2 Low Temperature
chg_eas_alarm 3 2 Door Intruder Alarm
chg_eas_alarm 4 2 Burglar Alarm
chg_eas_alarm 5 2 Window Intruder Alarm
equip 0 SITE
1
LCF
0
64
no
equip 1 CAB
0
9
pgsm
equip 1 CAGE
15
0
0
yes
# SITE CONFIGURATION
chg_element bts_type 1 1
chg_element gproc_slots 16 1
# MMS THRESHOLDS DEFAULTED
# SMS OPTIONS
chg_element sms_dl_allowed 1 1
chg_element sms_ul_allowed 1 1
chg_element sms_tch_chan 2 1
add_cell 2 3 4 1 1 368 39 1
frequency_type = pgsm
bsic = 16
wait_indication_parameters = 20
ccch_conf = 2
bs_ag_blks_res = 1
bs_pa_mfrms = 1
extended_paging_active = 1
number_sdcchs_preferred = 8
en_incom_ho = 1
intra_cell_handover_allowed = 1
inter_cell_handover_allowed = 1
number_of_preferred_cells = 6
ho_margin_def = 8
handover_recognized_period = 12
ul_rxqual_ho_allowed = 1
App Fvi
Issue 12 Rev 2
dl_rxqual_ho_allowed = 1
ul_rxlev_ho_allowed = 1
dl_rxlev_ho_allowed = 1
sdcch_ho = 0
sdcch_timer_ho = 1
interfer_ho_allowed = 1
pwr_handover_allowed = 1
ms_distance_allowed = 0
mspwr_alg = 0
handover_power_level = 6
pwrc = 1
intave = 3
timing_advance_period = 6
ms_p_con_interval = 2
ms_p_con_ack = 2
ms_power_control_allowed = 1
bts_p_con_interval = 4
bts_p_con_ack = 2
bts_power_control_allowed = 0
pow_inc_step_size_ul = 6
pow_inc_step_size_dl = 6
pow_red_step_size_ul = 4
pow_red_step_size_dl = 4
dyn_step_adj = 0
dyn_step_adj_fmpr = 10
max_tx_bts = 0
max_tx_ms = 33
rxlev_min_def = 0
ms_txpwr_max_def = 33
decision_alg_num = 0
decision_1_dl_rxlev_av_h = 0
decision_1_dl_rxlev_av_ih = 0
decision_1_dl_rxlev_av_p = 0
decision_1_dl_rxqual_av_h = 0
decision_1_dl_rxqual_av_p = 0
decision_1_n1 = 4
decision_1_n2 = 4
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 4
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_ncell_rxlev_av_h_calc = 0
decision_1_p1 = 3
decision_1_p2 = 3
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 3
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
decision_1_p_bgt_rxlev_av_h = 0
decision_1_tim_adv_av_alg = 0
decision_1_ul_rxlev_av_h = 0
decision_1_ul_rxlev_av_ih = 0
decision_1_ul_rxlev_av_p = 0
App Fvii
Issue 12 Rev 2
decision_1_ul_rxqual_av_h = 0
decision_1_ul_rxqual_av_p = 0
alt_qual_proc = 0
l_rxqual_ul_p = 1800
l_rxqual_dl_p = 1800
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 2
link_about_to_fail = 1
full_pwr_rfloss = 1
cell_bar_access_switch = 0
cell_bar_access_class = 0
emergency_class_switch = 0
report_resource_tch_f_high_water_mark = 1
report_resource_tch_f_low_water_mark = 5
rxlev_access_min = 0
dtx_required = 2
attach_detach = 0
ncc_of_plmn_allowed = 68
max_retran = 3
ms_txpwr_max_cch = 5
tx_integer = 12
radio_link_timeout = 2
reestablish_allowed = 1
cell_reselect_hysteresis = 2
cell_reselect_param_ind = 0
cell_bar_qualify = 0
cell_reselect_offset = 0
temporary_offset = 0
penalty_time = 0
rapid_pwr_down = 1
rpd_trigger = 45
rpd_offset = 12
rpd_period = 2
chg_cell_element queue_management_information 0 2 3 4 1 1 368 39
chg_cell_element max_q_length_sdcch 0 2 3 4 1 1 368 39
chg_cell_element channel_reconfiguration_switch 1 2 3 4 1 1 368 39
chg_cell_element max_number_of_sdcchs 32 2 3 4 1 1 368 39
chg_cell_element sdcch_need_low_water_mark 12 2 3 4 1 1 368 39
chg_cell_element sdcch_need_high_water_mark 2 2 3 4 1 1 368 39
chg_cell_element tch_full_need_low_water_mark 5 2 3 4 1 1 368 39
chg_cell_element rr_t3109 12000 2 3 4 1 1 368 39
chg_cell_element rr_t3111_tch 1500 2 3 4 1 1 368 39
App Fviii
Issue 12 Rev 2
App Fix
Issue 12 Rev 2
15
2
22
3
equip 1 DHP
15
1
24
3
equip 1 GCLK
0
15
no
no
no
equip 1 MSI
1
15
16
0
equip 1 MSI
3
15
14
0
equip 1 COMB
0
255
00
01
equip 1 EAS
0
15
16
1111
00010001
12348
12346789
equip 1 DRI
00
0
drim
15
7
2 3 4 1 1 368 39
1
00
0
1
4
equip 1 DRI
App Fx
Issue 12 Rev 2
01
0
drim
15
9
2 3 4 1 1 368 39
1
00
1
1
4
equip 1 DRI
02
0
drim
15
11
2 3 4 1 1 368 39
1
00
2
1
4
equip 1 DRI
03
0
drim
15
13
2 3 4 1 1 368 39
1
00
3
1
4
equip 1 DRI
04
0
drim
15
15
2 3 4 1 1 368 39
1
00
4
1
4
# TIMERS DEFAULTED
EMOTOROLA LTD. 2001
App Fxi
Issue 12 Rev 2
Issue 12 Rev 2
1
1
2500
3
7
# RTFs
# RTFs, Site 1
equip 1 RTF
FULL
BCCH
00
0
1
2 3 4 1 1 368 39
65
255 255 255 255 255 255 255 255
00000000
0
0
equip 1 RTF
FULL
NON_BCCH
01
0
1
2 3 4 1 1 368 39
55
255 255 255 255 255 255 255 255
00000000
0
0
0
# MMS Priorities
modify_value 1 mms_priority 250 mms 1 0
modify_value 1 mms_priority 0 mms 3 0
modify_value 2 mms_priority 250 mms 0 1
modify_value 2 mms_priority 0 mms 0 0
modify_value 3 mms_priority 250 mms 0 0
modify_value 3 mms_priority 249 mms 0 1
# Enable GCLK sync
chg_element phase_lock_gclk 1 1
chg_element phase_lock_gclk 1 2
chg_element phase_lock_gclk 1 3
# LINK PARAMETERS
modify_value all nbit 0 MMS
modify_value all ber_oos_mon_period 50 MMS
modify_value all ber_restore_mon_period 1800 MMS
# NEIGHBOUR DEFINITIONS
add_neighbor 2 3 4 1 1 368 36 2 3 4 1 1 368 37 internal
1
EMOTOROLA LTD. 2001
App Fxiii
Issue 12 Rev 2
App Fxiv
Issue 12 Rev 2
Glossary of Terms
Glosi
Issue 12 Rev 2
Numbers
Numbers
#
Number.
2 Mbit/s link
As used in this manual set, the term applies to the European 4-wire
2.048 Mbit/s digital line or link which can carry 30 A-law PCM channels
or 120 16 kbit/s GSM channels.
4GL
A interface
A3
A5
A8
AB
Access Burst.
AB
A-bis interface Interface between BSC and BTS. Motorola offers a GSM standard and
a unique Motorola A-bis interface. The Motorola interface reduces the
amount of message traffic and thus the number of 2 Mbit/s lines required
between BSC and BTS.
ABR
AC
AC
Application Context.
AC
Alternating Current
ACC
ACCH
ACK
ACKnowledgement.
ACM
ACSE
ACU
A/D
ADCCP
ADM
ADMinistration processor.
ADMIN
ADMINistration.
ADN
ADPCM
AE
Glosii
Application Entity.
SYS02 GSR5/AGSR: BSS Database
Issue 12 Rev 2
AEF
AFC
AFN
AGC
AGCH
Ai
Action indicator.
AI
Artificial Intelligence.
AIB
Air interface
ALT
AM
Amplitude Modulation.
AMA
AM/MP
ANSI
AOC
AP
Application Process.
APSM
ARFCN
ARQ
ARP
ASCE
ASE
ASE
ASN.1
ASP
ASR
ATB
ATI
ATT (flag)
Attach.
ATTS
AU
Access Unit.
AUC
AUT(H)
Authentication.
AUTO
AUTOmatic mode.
Glosiii
Issue 12 Rev 2
B
BA
BBH
BCC
BCCH
BCD
BCF
Base station Control Function. The GSM term for the digital control
circuitry which controls the BTS. In Motorola cell sites this is a normally
a BCU which includes DRI modules and is located in the BTS cabinet.
BCIE
BCU
Base station Control Unit. A functional entity of the BSS which provides
the base control function at a BTS site. The term no longer applies to a
type of shelf (see BSC and BSU).
BER
BES
BFI
BHCA
BIB
BLLNG
BiLLiNG.
bit/s
Bm
BN
Bit Number. Number which identifies the position of a particular bit period
within a timeslot.
BPF
Bandpass Filter.
BPSM
BRI
BS
BS
BSC
BSG
Glosiv
Issue 12 Rev 2
BSIC
BSIC-NCELL
BSP
BSS
BSSAP
BSSC
Base Station System Control cabinet. The cabinet which houses one or
two BSU shelves at a BSC or one or two RXU shelves at a remote
transcoder.
BSSMAP
BSSOMAP
BSU
Base Station Unit shelf. The shelf which houses the digital control
modules for the BTS (p/o BTS cabinet) or BSC (p/o BSSC cabinet).
BT
British Telecom
BT
Bus Terminator.
BTC
BTCU
BTP
BTS
Burst
C7
CA
CA
Central Authority.
CAI
CB
Circuit Breaker.
CBC
CBCH
Glosv
Issue 12 Rev 2
CBF
CBL
CBSMS
CC
Country Code.
CC
Call Control.
CCB
CCCH
CCCH_GROUP
CCD
CCDSP
CCF
CCH
CCH
CCITT
CCPE
CCS
Cct
Circuit.
CCU
CDB
CDR
CEB
Cell
1 Cell =
1 Sector
Omni Site
1Cell Site
(1 BTS)
Glosvi
6Sector Site
or
6Cell Site
(6 BTS's)
Issue 12 Rev 2
CF
Conversion Facility.
CF
CFC
Channel
CHV
CKSN
C/I, CIR
CI
Cell Identity. A block of code which identifies a cell within a location area.
CI
CUG Index.
Ciphertext
CKSN
CLI
CLK
Clock.
CLKX
Clock Extender half size board. The fibre optic link that distributes GCLK
to boards in system (p/o BSS etc).
CLM
Connectionless Manager.
CLR
CLeaR.
CPSM
CM
CM
Connection Management.
CMD
Command.
CMM
CMIP
CMISE
CMR
CODEX
COM
COM
Complete.
Glosvii
Issue 12 Rev 2
CONFerence circuit.
CONFIG
CP
Call Processing.
CPU
C/R
CR
CRC
CRE
CRM
CRM-LS/HS
CRT
CSFP
CSP
CSPDN
CT
Channel Tester.
CUG
D/A
DAN
DAS
Db
DB
DataBase.
DB
DBA
DBMS
dc
Direct Current.
DCB
DCCH
SACCH.
DCE
DCF
Glosviii
Issue 12 Rev 2
DCN
DCS
DDS
DEQB
DET
Detach.
DFE
DHP
DIA
DIQ
DIR
DISC
DISConnect.
DL
DLCI
DLD
DLNB
DLSP
Dm
DMA
DMA
DMX
DN
Directory Number.
DNIC
Downlink
DP
Dial/Dialled Pulse.
DPC
DPC
DPNSS
DPP
DPSM
Glosix
Issue 12 Rev 2
DRAM
DRC
DRCU
(D)RCU
Generic term for radio channel unit. May be standard RCU or diversity
radio channel unit DRCU.
DRI
DRIM
DRIX
BSS).
DRI Extender half size board. Fibre optic link from DRI to BCU (p/o
DRX, DRx
DS-2
DSE
DSP
DSS1
DSSI
DTAP
DTE
DTF
DTI
DTMF
DTX, DTx
Dummy burst
See Erlang.
E1
EA
External Alarms.
EAS
Eb/No
Glosx
Issue 12 Rev 2
EBSG
EC
Echo Canceller.
EC
European Commission.
ECB
ECID
ECM
Ec/No
EEPROM
EGSM
Extended GSM.
EGSM
EIR
EIRP
EIRP
EM
EMC
EMF
EMI
EMX
EN
European Norm(e)
en bloc
EOT
End of Tape.
Erlang
EPROM
EPSM
EQB
Equalizer Board. Control circuit for equalization for 8 time slots each with
equalizing circuitry and a DSP (p/o RCU).
EQ DSP
ERP
ESP
Electro-static Point.
ESQL
Glosxi
Issue 12 Rev 2
interface language.
E-TACS
ETR
ETS
ETSI
ETX
End of Transmission.
EU
European Union.
EXEC
Executive Process.
FA
Fax Adaptor.
FA
Full Allocation.
FA
Functional Area.
FAC
FACCH
FACCH/F
FACCH/H
FB
FCP
FCS
FD
FDMA
FEC
FEP
FER
FFS, FS
FHI
FIR
FK
FM
FM
Frequency Modulation.
FMUX
FN
FOA
FPCU
FOX
FR
Glosxii
FCCH
Full Rate. Refers to the current capacity of a data channel on the GSM
air interface, that is, 8 simultaneous calls per carrier (see also HR Half
Rate).
SYS02 GSR5/AGSR: BSS Database
Issue 12 Rev 2
Frequency
correction
burst
Period of RF carrier less than one timeslot whose modulation bit stream
allows frequency correction to be performed easily within an MS.
FRU
FS
Frequency Synchronization.
FS
FSL
FTAM
FTP
FTP
FW
Firmware.
Glosxiii
Issue 12 Rev 2
G
Gateway MSC An MSC that provides an entry point into the GSM PLMN from another
network or service. A gateway MSC is also an interrogating node for
incoming PLMN calls.
GCLK
GF
Ground fixed.
GHz
Giga-Hertz (109).
GMB
GMR
GMSC
GMSK
GSM.
GND
Ground
GOS
Grade of Service.
GPA
GPC
GPROC
GPS
GSA
GSA
GSM System Area. The group of GSM PLMN areas accessible by GSM
MSs.
GSM
GSM
GT
Global Title.
Guard period
GUI
GWY
Glosxiv
Generic Clock board. System clock source, one per site (p/o BSS, BTS,
BSC, IWF, RXCDR).
Issue 12 Rev 2
H
H-M
Human-Machine Terminals.
HAD, HAP
Handover
HDLC
HDSL
HLC
High Layer Compatibility. The HLC can carry information defining the
higher layer characteristics of a teleservice active on the terminal.
HLR
Home Location Register. The LR where the current location and all
subscriber parameters of an MS are permanently stored.
HMS
HO
HPU
HR
Half Rate. Refers to a type of data channel that will double the current
GSM air interface capacity to 16 simultaneous calls per carrier (see also
FR Full Rate).
HS
HandSet.
HSM
HSN
HW
Hardware.
Hyperframe
Glosxv
Issue 12 Rev 2
I
I
IA5
International Alphanumeric 5.
IADU
IAM
IAS
IC
Integrated Circuit.
IC
ICB
ICM
In-Call Modification.
ICMP
ID, id
Identification/Identity.
IDN
IE
IEC
IEEE
IEI
IF
Intermediate Frequency.
IFAM
IM
InterModulation.
IMACS
IMEI
IMM
IMSI
IN
Intelligent Network.
IN
INS
IN Service.
INS
Interworking
I/O
Glosxvi
Information (frames).
Input/Output.
SYS02 GSR5/AGSR: BSS Database
Issue 12 Rev 2
IP
Initialisation Process.
IP
Internet Protocol.
IPC
Inter-Process Communication.
IP, INP
INtermodulation Products.
IPR
Intellectual Property.
IPSM
Integrated PSM.
ISC
ISDN
ISO
ISQL
ISUP
ITC
ITU
IWF
IWMSC
InterWorking MSC.
IWU
InterWorking Unit.
kilo (103).
Kb
Kilo-bit.
kbit/s, kbps
Kc
kHz
kilo-Hertz (103).
Ki
KSW
KSWX
KSW Expander half size board. Fibre optic distribution of TDM bus (p/o
BSS).
kW
kilo-Watt.
Glosxvii
Issue 12 Rev 2
L
L1
L2ML
L2R
L2R BOP
L2R COP
L3
Layer 3.
LA
LAC
LAI
LAN
LANX
LAN Extender half size board. Fibre optic distribution of LAN to/from
other cabinets (p/o BSS etc).
LAPB
LAPD
LAPDm
LC
LCF
LCP
LE
Local Exchange.
LED
LF
Line Feed.
LI
Length Indicator.
LI
Line Identity.
LLC
Lower Layer Compatibility. The LLC can carry information defining the
lower layer characteristics of the terminal.
Lm
LMS
LMSI
Location area
Glosxviii
Layer 1.
An area in which a mobile station may move freely without updating the
location register. A location area may comprise one or several base
station areas.
Issue 12 Rev 2
LPC
LR
LTA
LTE
LTP
LTU
LV
LVD
Mega (106).
M&TS
MA
MAC
MACN
MAF
MAI
MAIDT
MAINT
MAINTenance.
MAIO
MAP
Mobile Application Part (of signalling system No. 7). The inter-networking
signalling between MSCs and LRs and EIRs.
MAPP
MCAP
MCC
MCU
MCU-m
MDL
ME
Glosxix
Issue 12 Rev 2
ME
MEF
MF
MultiFrame.
MF
MF
MultiFunction block.
MGMT
Management.
MGR
Manager.
MHS
MHS
MHz
Mega-Hertz (106).
MI
Maintenance Information.
MIB
MIC
MIT
MM
Mobility Management.
MME
MMI
Man Machine Interface. The method in which the user interfaces with the
software to request a function or change parameters.
MML
MMS
MNC
MNT
MaiNTenance.
MO
Mobile Originated.
MO/PP
MOMAP
Motorola OMAP.
MoU
Memorandum of Understanding.
MPC
MPH
MPX
MultiPleXed.
MRN
MS
MSC
Glosxx
Issue 12 Rev 2
MSCM
MSCU
msec
MSI
MSIN
MSISDN
MSRN
MSU
MT
MT (0,1,2)
MTM
Mobile-To-Mobile (call).
MTP
MT/PP
MTBF
MTL
MTL
MTP
MTTR
Multiframe
MUMS
MUX
Multiplexer.
NB
NCC
NCELL
Glosxxi
Issue 12 Rev 2
ND
NDC
NDUB
NE
NEF
NF
Network Function.
NI
Network Interface.
NIC
NIU
NLK
Nm
Newton metres.
NM
NMASE
NMC
Network Management Centre. The NMC node of the GSM TMN provides
global and centralised GSM PLMN monitoring and control, by being at
the top of the TMN hierarchy and linked to subordinate OMC nodes.
NMSI
NMT
NN
Normal burst
NPI
NPSM
NRZ
NSAP
NSP
NT
Network Termination.
NT
Non Transparent.
NTU
NUA
NUI
NUP
NVRAM
nW
Nano-Watt (109).
N/W
Glosxxii
NetWork
Issue 12 Rev 2
O
O&M
OACSU
OCB
OFL
% OverFlow.
OMAP
OMC
Operations and Maintenance Centre. The OMC node of the GSM TMN
provides dynamic O&M monitoring and control of the PLMN nodes
operating in the geographical area controlled by the specific OMC.
OMCR
OMCS
OML
OMP
OMS
OMSS
OOS
Out Of Service.
OPC
ORAC
OS
Operating System.
OSI
OSF
OSF/MOTIF
Open Software Foundation Motif. The basis of the GUI used for the
Motorola OMC-R MMI.
OSS
Overlap
Overlap sending means that digits are sent from one system to another
as soon as they are received by the sending system. A system using ~
will not wait until it has received all digits of a call before it starts to send
the digits to the next system. This is the opposite of en bloc sending
where all digits for a given call are sent at one time.
Glosxxiii
Issue 12 Rev 2
P
PA
PAB
PABX
PAD
Paging
PATH
PBX
PC
Personal Computer.
PC
Power converter
PCH
PCM
Pulse Code Modulation (see also 2 Mbit/s link which is the physical
bearer of PCM).
PCMCIA
PCN
PCR
PCU
PCS
pd
Potential difference.
PD
Protocol Discriminator.
PD
Public Data.
PDB
PDN
PDU
PDU
PEDC
PH
Packet Handler.
PH
PHysical (layer).
PHI
PID
Process IDentifier.
PI
Presentation Indicator.
PIM
Glosxxiv
Power Amplifier.
Issue 12 Rev 2
PIN
PIX
PK
Plaintext
Unciphered data
PLL
Phase Lock Loop (refers to phase locking the GCLK in the BTS).
PLMN
PM
PM-UI
PMA
PMS
Pseudo MMS.
PMUX
PCM MUltipleXer.
PN
POTS
p/o
Part of.
pp, pp
Peak-to-peak.
PP
Point-to-Point.
ppb
ppm
PPS
PPSM
PRI
PROM
PSAP
PSM
PSPDN
PSTN
PSU
PSW
PTO
PVC
PWR
Power.
PXPDN
Glosxxv
Issue 12 Rev 2
Q
Q-adapter
QAF
QEI
QOS
Quality Of Service.
RAB
RACCH
RACH
RAM
RAND
RANDom number.
RAx
Rate Adaptation.
RBCU
RBDS
RBER
RBTS
RCB
RCI
RCP
RCU
RCVR
Receiver.
RDBMS
RDB
Requirements database.
RDN
REC, Rec.
RECommendation.
REL
RELease.
RELP
RELP-LTP
RELP Long Term Prediction. A name for GSM full rate (see full rate).
REQ
REQuest.
RES
RF
Radio Frequency.
Glosxxvi
Issue 12 Rev 2
RFC, RFCH
RFE
RFEB
RFI
RFN
RISC
RLP
rms
RMSU
ROM
ROSE
Roundtrip
propagation
delay
RPE
RPE-LTP
RPR
RR
RR
RRSM
RSE
RSL
RSLF
RSS
RSSI
RTC
RTE
RU
Rack Unit.
Rx
Receive(r).
RXCDR
Remote Transcoder.
RXLEV-D
RXLEV-U
RXQUAL-D
RXQUAL-U
RXU
Remote Transcoder Unit. The shelf which houses the remote transcoder
modules in a BSSC cabinet at a remote transcoder site.
Glosxxvii
Issue 12 Rev 2
S
SABM
SACCH
SAGE
SAP
Service Access Point. In the reference model for OSI, SAPs of a layer
are defined as gates through which services are offered to an adjacent
higher layer.
SAP
SAPI
SAW
SB
SC
SC
Service Code.
SCCA
SCCP
SCEG
SCH
SCI
SCIP
SCM
SCN
SCP
SCU
SDCCH
SDH
SDR
SE
SEF
SFH
SFRAS
SI
Glosxxviii
Screening Indicator.
SYS02 GSR5/AGSR: BSS Database
FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED
Issue 12 Rev 2
SI
Service Interworking.
SID
SIlence Descriptor.
SIF
Signal Information Field. The bits of a message signal unit that carry
information for a certain user transaction; the SIF always contains a
label.
SIM
SIO
SITE
SIX
SK
SLNK
Serial Link.
SLTM
SM
Switch Manager.
SMAE
SME
SMP
SMS
SMSCB
SMS-SC
SMS/PP
SN
Subscriber Number.
SND
SeND.
SNDR
SeNDeR.
SNR
Serial Number.
SOA
SP
SP
Signalling Point.
SP
Special Product.
SPC
SPC
Glosxxix
Issue 12 Rev 2
SPI
SQL
SRD
SRES
SS7, SS#7
SS
SSA
SSC
SSF
Subservice Field. The level 3 field containing the network indicator and
two spare bits.
SSM
SSP
SSP
SSS
STAN
STAT
STATistics.
stats
Statistics.
STC
STP
Superframe
SVC
SVM
SerVice Manager.
SW
Software.
SWFM
SynchronizationPeriod of RF carrier less than one timeslot whose modulation bit stream
burst
carries information for the MS to synchronize its frame to that of the
received signal.
SYS
SYSGEN
Glosxxx
SYStem.
SYStem GENeration. the Motorola procedure for loading a configuration
database into a BTS.
Issue 12 Rev 2
T
T1
T43
TA
TA
Timing Advance.
TAC
TACS
TAF
TATI
TBD
To Be Determined.
TC
Transaction Capabilities.
TC shelf
TCAP
TCH
TCI
TCP/IP
TCU
TCU-m
TDM
TDMA
TDU
TE
Tei
TEI
TEMP
TEMPorary.
TEST
TFA
Transfer Allowed.
TFP
Transfer Prohibited.
TFTP
Glosxxxi
Issue 12 Rev 2
TI
Transaction Identifier.
Timeslot
The multiplex subdivision in which voice and signalling bits are sent over
the air. Each RF carrier is divided into 8 timeslots.
Timing advance A signal sent by the BTS to the MS. It enables the MS to advance the
timing of its transmission to the BTS so as to compensate for
propagation delay.
TM
TMI
TMM
TMN
TMSI
TN
Timeslot Number.
Traffic
channels
Traffic unit
Equivalent to an erlang.
Training
sequence
TRAU
TRX
TS
Telecommunications standard.
TS
Teleservice.
TS
TSA
TimeSlot Acquisition.
TSDA
TSC
TSI
TSM
TTL
TTY
TU
Traffic Unit.
TUP
Tx
Glosxxxii
Traffic Manager.
Transmit(ter)
SYS02 GSR5/AGSR: BSS Database
Issue 12 Rev 2
U
mS
micro-second (106).
UA
UDP
UDUB
UHF
UI
Um
UMTS
UPD
Up to Date.
Uplink
Physical link from the MS towards the BTS (MS transmits, BTS
receives).
Useful part of
burst
That part of the burst used by the demodulator; differs from the full burst
because of the bit shift of the I and Q parts of the GMSK signal.
USSD
Unstructured SS Data.
VA
VAD
VCO
VLR
VLSI
VOX
VSP
VSWR
WPA
WS
Work Station. The remote device via which O&M personnel execute
input and output transactions for network management purposes.
WSF
Glosxxxiii
Issue 12 Rev 2
X
X.25
X.25 link
XBL
XCB
XCDR
XID
Glosxxxiv
Exchange Identifier.
Issue 12 Rev 2
Answers
Answers1
Issue 12 Rev 2
Answers2
Issue 12 Rev 2
#
#
BSC SITE 0
LOAD 1.6.0.0 (GSR4)
chg_element bsc_type 1 0
chg_element gproc_slots 16 0
chg_element sync_time_oos100 0
chg_element sync_time_restore 50 0
chg_element remote_time_oos 100 0
chg_element remote_time_restore 50 0
chg_element sync_loss_oos 20 0
chg_element sync_loss_restore 50 0
chg_element sync_loss_daily 15 0
chg_element sync_loss_hourly 5 0
chg_element remote_loss_oos 20 0
chg_element remote_loss_restore 50 0
chg_element remote_loss_daily 15 0
chg_element remote_loss_hourly 5 0
chg_element slip_loss_oos 20 0
chg_element slip_loss_restore 600 0
chg_element slip_loss_daily 15 0
chg_element slip_loss_hourly 2 0
chg_element ber_loss_daily 6 0
chg_element ber_loss_hourly 4 0
Answers3
Issue 12 Rev 2
Answers4
Issue 12 Rev 2
#
#
BTS SITE 12
LOAD 1.5.1.0 (GSR3)
chg_element sync_time_oos100 12
chg_element sync_time_restore 50 12
chg_element remote_time_oos 100 12
chg_element remote_time_restore 50 12
chg_element sync_loss_oos 20 12
chg_element sync_loss_restore 50 12
chg_element sync_loss_daily 15 12
chg_element sync_loss_hourly 5 12
chg_element remote_loss_oos 20 12
chg_element remote_loss_restore 50 12
chg_element remote_loss_daily 15 12
chg_element remote_loss_hourly 5 12
chg_element slip_loss_oos 20 12
chg_element slip_loss_restore 600 12
chg_element slip_loss_daily 15 12
chg_element slip_loss_hourly 2 12
chg_element ber_loss_daily 6 12
chg_element ber_loss_hourly 4 12
Answers5
Issue 12 Rev 2
C2 Reselection Exercise
C2 Reselection Exercise
The parameters and levels specified on the facing page are typical values experienced
by a mobile in the reselection process. Use these values to determine whether the
mobile will reselect to the neighbour cell. The mobile has been in the server well over
one hour, and the best neighbour has been in the top six measured cells for exactly 4
minutes.
Answers6
C2 Reselection Exercise
Issue 12 Rev 2
Working Area
Rxlev Av
P1
A=
(70)
(90)
B=
P2 Max RF Power of MS
B=
33
39
= (6) dBm
C1=
20
20 dBm
C2=
20
+ 6
26 dBm
= 20 dBm
(P2=ms_txpwr_max_cch=
dBm)
NEIGHBOUR
A=
Rxlev Av
P1
A=
(63)
(90)
B=
P2 Max RF Power of MS
B=
41
39
2 dBm
C1=
27
25 dBm
C2=
25
19 dBm
10
27 dBm
(P2=ms_txpwr_max_cch=
dBm)
FOR RESELECTION
C2 (server) < C2 (neighbour) cell_reselect_hysteresis
C2 server= 26
C2 Neighbour= 19
C2 Neighbour cell_reselect_hysteresis= 15 No reselection
Answers7
Issue 12 Rev 2
C2 Reselection Exercise
Answers8
Issue 12 Rev 2
CELL 2
add_cell 2 2 8 0 1 255 1 1
bsic=10
wait_indication_parameters= 3
ccch_conf=0
bs_ag_blks_res=4
bs_pa_mfrms=2
extended_paging_active=0
number_sdcchs_preferred=8
en_incom_ho = 1
intra_cell_handover_allowed=1
inter_cell_handover_allowed=1
number_of_preferred_cells=6
ho_margin_def=16
handover_recognized_period=8
ul_rxqual_ho_allowed=1
dl_rxqual_ho_allowed=1
ul_rxlev_ho_allowed=1
dl_rxlev_ho_allowed=1
sdcch_ho=1
sdcch_timer_ho= 3
interfer_ho_allowed=1
pwr_handover_allowed=0
ms_distance_allowed=1
mspwr_alg = 0
handover_power_level=0
pwrc=0
intave =
timing_advance_period=10
ms_p_con_interval=9
ms_p_con_ack=0
ms_power_control_allowed=1
bts_p_con_interval=2
bts_p_con_ack=0
bts_power_control_allowed=1
pow_inc_step_size_ul=6
pow_inc_step_size_dl=6
pow_red_step_size_ul=4
pow_red_step_size_dl=4
dyn_step_adj=0
dyn_step_adj_fmpr=10
max_tx_bts=2
max_tx_ms=39
rxlev_min_def=10
ms_txpwr_max_def=39
decision_alg_num=0
decision_1_dl_rxlev_av_h=0
add_cell 2 2 8 0 1 255 2 1
bsic=11
wait_indication_parameters=10
ccch_conf=0
bs_ag_blks_res=3
bs_pa_mfrms=2
extended_paging_active=0
number_sdcchs_preferred=8
en_incom_ho = 1
intra_cell_handover_allowed=1
inter_cell_handover_allowed=1
number_of_preferred_cells=6
ho_margin_def=16
handover_recognized_period=8
ul_rxqual_ho_allowed=1
dl_rxqual_ho_allowed=1
ul_rxlev_ho_allowed=1
dl_rxlev_ho_allowed=1
sdcch_ho=1
sdcch_timer_ho= 2
interfer_ho_allowed=1
pwr_handover_allowed=0
ms_distance_allowed=1
mspwr_alg = 0
handover_power_level=0
pwrc=1
intave =
timing_advance_period=6
ms_p_con_interval=5
ms_p_con_ack=0
ms_power_control_allowed=1
bts_p_con_interval=1
bts_p_con_ack=0
bts_power_control_allowed=1
pow_inc_step_size_ul=6
pow_inc_step_size_dl=6
pow_red_step_size_ul=4
pow_red_step_size_dl=4
dyn_step_adj=0
dyn_step_adj_fmpr=10
max_tx_bts=0
max_tx_ms=39
rxlev_min_def=15
ms_txpwr_max_def=39
decision_alg_num=0
decision_1_dl_rxlev_av_h=0
Answers9
Issue 12 Rev 2
decision_1_dl_rxlev_av_ih=0
decision_1_dl_rxlev_av_p=0
Answers10
decision_1_dl_rxlev_av_ih=0
decision_1_dl_rxlev_av_p=0
Issue 12 Rev 2
CELL 2
decision_1_dl_rxqual_av_h=0
decision_1_dl_rxqual_av_p=0
decision_1_n1=12
decision_1_n2=12
decision_1_n3=12
decision_1_n4=12
decision_1_n5=12
decision_1_n6=12
decision_1_n7=12
decision_1_n8=12
decision_1_ncell_rxlev_av_h_calc=0
decision_1_p1=8
decision_1_p2=8
decision_1_p3=8
decision_1_p4=8
decision_1_p5=8
decision_1_p6=8
decision_1_p7=8
decision_1_p8=8
decision_1_p_bgt_rxlev_av_h=0
decision_1_tim_adv_av_alg =0
decision_1_ul_rxlev_av_h=0
decision_1_ul_rxlev_av_ih=0
decision_1_ul_rxlev_av_p=0
decision_1_ul_rxqual_av_h=0
decision_1_ul_rxqual_av_p=0
alt_qual_proc = 0
l_rxqual_ul_p=1350
l_rxqual_dl_p=1350
u_rxqual_ul_p=0
u_rxqual_dl_p=0
l_rxqual_ul_h=1000
l_rxqual_dl_h=1000
l_rxlev_ul_h=10
l_rxlev_dl_h=10
u_rxlev_ul_ih=15
u_rxlev_dl_ih=15
ms_max_range=50
l_rxlev_ul_p=20
l_rxlev_dl_p=20
u_rxlev_ul_p=35
u_rxlev_dl_p=35
ncell_proc=0
missing_rpt=1
ba_alloc_proc=0
decision_1_dl_rxqual_av_h=0
decision_1_dl_rxqual_av_p=0
decision_1_n1=8
decision_1_n2=8
decision_1_n3=8
decision_1_n4=8
decision_1_n5=8
decision_1_n6=8
decision_1_n7=8
decision_1_n8=8
decision_1_ncell_rxlev_av_h_calc=0
decision_1_p1=6
decision_1_p2=6
decision_1_p3=6
decision_1_p4=6
decision_1_p5=6
decision_1_p6=6
decision_1_p7=6
decision_1_p8=6
decision_1_p_bgt_rxlev_av_h=0
decision_1_tim_adv_av_alg =0
decision_1_ul_rxlev_av_h=0
decision_1_ul_rxlev_av_ih=0
decision_1_ul_rxlev_av_p=0
decision_1_ul_rxqual_av_h=0
decision_1_ul_rxqual_av_p=0
alt_qual_proc = 0
l_rxqual_ul_p=1600
l_rxqual_dl_p=1600
u_rxqual_ul_p=0
u_rxqual_dl_p=0
l_rxqual_ul_h=1000
l_rxqual_dl_h=1000
l_rxlev_ul_h=12
l_rxlev_dl_h=12
u_rxlev_ul_ih=15
u_rxlev_dl_ih=15
ms_max_range=40
l_rxlev_ul_p=6
l_rxlev_dl_p=6
u_rxlev_ul_p=15
u_rxlev_dl_p=15
ncell_proc=0
missing_rpt=1
ba_alloc_proc=0
Answers11
Issue 12 Rev 2
link_fail=5
link_about_to_fail=4
Answers12
link_fail=5
link_about_to_fail=4
Issue 12 Rev 2
CELL 2
full_pwr_rfloss=1
cell_bar_access_switch= 0
cell_bar_access_class=0
emergency_class_switch=0
report_resource_tch_f_high_water_mark=2
report_resource_tch_f_low_water_mark=8
rxlev_access_min=4
dtx_required=2
attach_detach=0
ncc_of_plmn_allowed=70
max_retran=2
ms_txpwr_max_cch=3
tx_integer= 10
radio_link_timeout=5
reestablish_allowed=0
cell_reselect_hysteresis=2
cell_reselect_param_ind=1
cell_bar_qualify=0
cell_reselect_offset=1
temporary_offset=2
penalty_time=8
rapid_pwr_down =1
rpd_trigger =50
rpd_offset =20
rpd_period =4
full_pwr_rfloss=1
cell_bar_access_switch= 0
cell_bar_access_class=0
emergency_class_switch=0
report_resource_tch_f_high_water_mark=2
report_resource_tch_f_low_water_mark=8
rxlev_access_min=15
dtx_required=0
attach_detach=0
ncc_of_plmn_allowed=19
max_retran=2
ms_txpwr_max_cch=3
tx_integer= 10
radio_link_timeout=5
reestablish_allowed=1
cell_reselect_hysteresis=1
cell_reselect_param_ind=1
cell_bar_qualify=0
cell_reselect_offset=2
temporary_offset=0
penalty_time=31
rapid_pwr_down =1
rpd_trigger =50
rpd_offset =20
rpd period =4
Answers13
Issue 12 Rev 2
CELL 2
queue_management_information=0
max_q_length_full_rate_channel=0
max_q_length_sdcch=0
channel_reconfiguration_switch=1
threshold =8
max_number_of_sdcchs=24
sdcch_need_low_water_mark=13
sdcch_need_high_water_mark=3
tch_full_need_low_water_mark= 4
immediate_assign_mode=0
rr_t3109=15500
rr_t3111=7680
rr_t3212=0
handover_required_reject_switch=1
rr_t3103=4100
rr_t3101=1700
interfer_bands,0=5
interfer_bands,1=10
interfer_bands,2=15
interfer_bands,3=20
interfer_bands,4=25
rach_load_period=132
ccch_load_period=170
rr_t3105=60
rr_ny1_rep=20
dealloc_inact = 1000
ho_ack = 23000
rf_chan_rel_ack = 20000
queue_management_information=0
max_q_length_full_rate_channel=0
max_q_length_sdcch=0
channel_reconfiguration_switch=1
threshold =7
max_number_of_sdcchs=32
sdcch_need_low_water_mark=13
sdcch_need_high_water_mark=3
tch_full_need_low_water_mark= 4
immediate_assign_mode=0
rr_t3109=100000
rr_t3111=5000
rr_t3212=0
handover_required_reject_switch=0
rr_t3103=150000
rr_t3101=1500
interfer_bands,0=5
interfer_bands,1=10
interfer_bands,2=15
interfer_bands,3=20
interfer_bands,4=25
rach_load_period=160
ccch_load_period=200
rr_t3105=20
rr_ny1_rep=30
dealloc_inact = 10000
ho_ack = 23000
rf_chan_rel_ack = 20000
Answers14
Issue 12 Rev 2
equip 12 BTP
0
15
20
3
equip 12 DHP
15
0
25
3
equip 12 GCLK
0
15
equip 12 MSI
1
15
16
0
equip 0 RSL
12
0
0
2500
3
7
EMOTOROLA LTD. 2001
Answers15
Issue 12 Rev 2
Issue 12 Rev 2
equip 12 RTF
non_bcch
01
0
1
2 3 4 0 1 10724 52
64
255 255 255 255 255 255 255 255
3 3 3 3 3 3 3 3
0
equip 12 RTF
bcch
10
0
1
2 3 4 0 1 10724 54
53
255 255 255 255 255 255 255 255
3 3 3 3 3 3 3 3
Answers17
Issue 12 Rev 2
equip< 0 >PATH
terminating site id
16
16
path id
BSC MSI id
Site id
14
upstream MSI id
downstream MSI id
Site id
15
upstream MSI id
downstream MSI id
Site id
16
upstream MSI id
Answers18
14
16
3