You are on page 1of 487

CHAPTER 1

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

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

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

Positin mark for TED spine

SYS02
GSR5/
AGSR

Issue 12 Rev 2

SYS02 GSR5/AGSR
BSS Database

E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999


All Rights Reserved
Printed in the U.K.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Issue 12 Rev 2

Copyrights, notices and trademarks


Copyrights
The Motorola products described in this document may include copyrighted Motorola computer
programs stored in semiconductor memories or other media. Laws in the United States and other
countries preserve for Motorola certain exclusive rights for copyright computer programs, including the
exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any
copyright Motorola computer programs contained in the Motorola products described in this document
may not be copied or reproduced in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by
implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of
Motorola, except for the rights that arise by operation of law in the sale of a product.

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

and MOTOROLA are registered trademarks of Motorola Inc.


Aspira, Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.

ii

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Important notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1
1
1
2
2

First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1
BSS Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11
11

GSM Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Bursts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12
12

Timing Advance and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14

GSM Control Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


BCCH Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CCCH Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DCCH Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16
16
16
16

Mapping Logical Channels onto the TDMA Frame Structure . . . . . . . . . . . . . . . . . . . . . .


Bursts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The 51-frame Control Channel Multiframe BCCH/CCCH . . . . . . . . . . . . . . . . . .

18
18
110

Multiframes and Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


The 51-frame Control Channel Multiframe BCCH/CCCH . . . . . . . . . . . . . . . . . .
The 102-frame Dedicated Control Channel Multiframe SDCCH and SACCH .
The 102-frame Control Channel Multiframe Combined Structure . . . . . . . . . . .

112
112
114
116

Multiframes and Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


The 26-frame Traffic Channel Multiframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

118
118

Mobile Activity Transmit and Receive Timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

120

Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

122

BSC Initialisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

124

Initialisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

126

Configuration Management (CM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

128
128

CM Database Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

130

CM Database and Central Authority Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


To Change Site Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Change Remote BTS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

132
132
134

Database Level Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

136

BSS Radio Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

138
138

BSS Configuration and Fault Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layer 1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layer 2 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSS A-bis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

140
140
140
140
140

Handover Detection and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

142

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

The Base Station System (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


The Base Station Controller (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Base Transceiver Station (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24
24
24

Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

26

Command/Database Parameter Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

28

RXCDR/BSS/SITE/CAB/CAGE Numbering Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

210

Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipping the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

212
212

Equipping the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

BSC/ BTS Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

230

GPROC Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

232

Remote Loss Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

236

Site Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

238

Slip Loss Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

240

BER Loss Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

242

BER Monitoring Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

244

N Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

246

Integrated M-Cell HDSL interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv

144
144
146
146
146
146
148
148
148

248
248
248
248
248

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Physical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

250
250
250

HDSL Monitoring Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

252

HDSL SNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

254

HDSL Loss of Sync Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

256

Site Configuration Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Site Configuration Exercise 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Configuration Exercise 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

258
258
260

Chapter 3
Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31
31

Cell Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

34

Location Area Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

36

Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

38
38

Frequency Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

310

Base Station Identity Code (BSIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

312

PLMN Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

314

MS Transmit Power Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Common Control Channel (CCCH) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

328

Common Control Channel (CCCH) Block Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .

330

MS Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

332

Extended Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

334

Periodic Updates/rr_t3212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

336

Attach/Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

338

Cell Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

340

Emergency Call Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

342

Channel Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

344

Wait Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

346

Signalling Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
rr_t3101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

348
348

Channel Allocation by Interference Band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

350
352

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Issue 12 Rev 2

Channel Allocation by Interference Band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Assignment of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

354

Queue Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SDCCH Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

356
356

Channel Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

358

Preferred Number of SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

360

SDCCH Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

362

SDCCH Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

364

Measurement Reporting for Handovers and Power Control . . . . . . . . . . . . . . . . . . . . . . .

366

BA Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BA Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

368
368

Signal Strength Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

370

Signal Quality Reporting RXQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

372

BSS Processing and Threshold Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Measurements Reported by MS on SACCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measurements Performed by RSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

374
374
374

Threshold Comparison Process Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

376

Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

378
378
380

alt_qual_proc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

382
384

Handover RXQUAL, RXLEV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

386

Handover Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

388

MS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS Maximum Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

390
390

BTS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

392

BTS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

394

Rapid MS Power Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

396

Optimized Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3100

Optimized Power Control Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3102

Discontinuous Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3104

Handover Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3106

Handovers Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3108

SDCCH Access handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3110

Handovers Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Budget Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3112
3114

Timing Advance MS Maximum Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3116

HandoverMS Maximum Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3118

Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Incoming Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intra-Cell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inter-Cell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi

353

3120
3120
3122
3122

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

TCH Resources Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3124

Preferred Target Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3126

Handover Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Evaluating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3128
3128
3128

Handover Power Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3130

Calculated Handover Power Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Default Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3132
3132
3134

Handover Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
rr_t3103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3136
3136

Handover Channel Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3138

RSS Link Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Radio Link Revival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3140
3142

Loss of Radio Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3144

Timers rr_t3109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uplink Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3146
3146
3146

Timers rr_t3109, rr_ t3111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Normal Channel Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
rf_chan_rel_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Device and Function Dependency In-Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

42

Device and Function Dependency M-Cell/Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

44

Kilo-Port Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

46

KSW Extension/Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

48

KSW Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

410
410

Generic Clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

414

Base Site Processor (BSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

416

Code Storage Facility Processor (CSFP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

418

Base Transceiver Processor (BTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Digital Host Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

420
420

Generic Processor Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


GPROC Function Preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

422
422

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

vii

Issue 12 Rev 2

Equipage of GPROC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Base Transceiver Function (BTF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link Control Function (LCF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operations and Maintenance Function (OMF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digital Radio Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digital Radio Interface In-Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digital Radio Interface M-Cell/Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Redundancy Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RTF Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Antenna Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use of Tuneable Combiner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Combiner Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Combiner Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cavity Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diversity Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
fm cell type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typical Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Tuneable Combiner (RTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiport Serial Interface (MSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In-Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M-Cell/Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Path Equipage Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16 KBIT/S RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RTF Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Receive Transmit Function (RTF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Signalling Link (RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Transfer Link (MTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operations and Maintenance Link (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell Broadcast Link (CBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipage Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

Special key sequences


Special key sequences are represented as follows:
CTRL-c
ALT-f

Press the Alt and f keys at the same time.

Press the pipe symbol key.

CR or RETURN

Press the Control and c keys at the same time.

Press the Return (Enter) key. The Return key is


identified with the symbol on both the X terminal and
the SPARCstation keyboards. The SPARCstation
keyboard Return key is also identified with the word
Return.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

First aid in case of electric shock

Issue 12 Rev 2

First aid in case of electric shock


Warning
WARNING

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.

Do not attempt to remove clothing adhering to the burn.

2.

If help is available, or as soon as artificial respiration is no longer required, cover


the wound with a dry dressing.

3.

Do not apply oil or grease in any form.

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.

Make the equipment concerned safe, for example, by removing power.

2.

Make no further attempt to tamper with the equipment.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

First aid in case of electric shock

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.

CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High


Frequency (10 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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

First aid in case of electric shock

Issue 12 Rev 2

Definitions
NOTE

The above result applies only in the direction of maximum


radiation of the antenna. Actual installations may employ
antennas that have defined radiation patterns and gains that
differ from the example set forth above. The distances calculated
can vary depending on the actual antenna pattern and gain.

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.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

First aid in case of electric shock

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.

Take care when removing components connected to electrostatic sensitive


devices. These components may be providing protection to the device.

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.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Chapter 1

BSS Review

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Issue 12 Rev 2

ii

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Chapter 1
BSS Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11
11

GSM Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Bursts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12
12

Timing Advance and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14

GSM Control Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


BCCH Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CCCH Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DCCH Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16
16
16
16

Mapping Logical Channels onto the TDMA Frame Structure . . . . . . . . . . . . . . . . . . . . . .


Bursts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The 51-frame Control Channel Multiframe BCCH/CCCH . . . . . . . . . . . . . . . . . .

18
18
110

Multiframes and Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


The 51-frame Control Channel Multiframe BCCH/CCCH . . . . . . . . . . . . . . . . . .
The 102-frame Dedicated Control Channel Multiframe SDCCH and SACCH .
The 102-frame Control Channel Multiframe Combined Structure . . . . . . . . . . .

112
112
114
116

Multiframes and Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


The 26-frame Traffic Channel Multiframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

118
118

Mobile Activity Transmit and Receive Timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

120

Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

122

BSC Initialisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

124

Initialisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

126

Configuration Management (CM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

128
128

CM Database Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

130

CM Database and Central Authority Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


To Change Site Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Change Remote BTS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

132
132
134

Database Level Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

136

BSS Radio Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

138
138

BSS Configuration and Fault Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layer 1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layer 2 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSS A-bis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

140
140
140
140
140

Handover Detection and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

iii

Issue 12 Rev 2

Comparison GSM and Motorola Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iv

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

150

EMOTOROLA LTD. 2001

BSS Review

Issue 12 Rev 2

BSS Review
Objectives
On completion of this chapter the student will be able to:
S

Air Interface

1.

Explain the Air Interface Structure.

2.

State the functions of the BCCH, CCCH and DCCH.

3.

Explain the activity of the MS when in dedicated mode.

4.

Timing Advance and Power Control.

Software review

Describe the download and Initialization Process.


1.

Explain how the database is distributed within a BSS.

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.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

11

Issue 12 Rev 2

GSM Air Interface

GSM Air Interface


Bursts
Each carrier frequency used in GSM is divided into 8 independent timeslots and into
each of these timeslots a burst is placed. The diagram shows the general form of a GSM
burst.
The receiver can only receive the burst and decode it if it is received within the timeslot
designated for it. The timing, therefore, must be extremely accurate but the structure
does allow for a small margin of error by incorporating a guard period as shown in the
diagram. To be precise, the timeslot is 0.577ms long, whereas the burst is slightly
shorter at 0.546ms. Eight bursts occupy one Time Division Multiple Access (TDMA)
frame.
The flag-bits are set when the frame has been stolen by the Fast Associated Control
Channel (FACCH). The training sequence is used by the receivers equaliser as it
estimates the transfer characteristic of the physical path between the Base Station (BSS)
and the mobile (MS).

12

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

GSM Air Interface

Issue 12 Rev 2

GSM Burst and TDMA Frame

Frame 1
0

GUARD
PERIOD

Frame 2
5

TRAINING SEQUENCE

GUARD
PERIOD

NORMAL BURST

INFORMATION

INFORMATION

FLAG BITS
TAIL BITS

SYS02_Ch1_01

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

13

Timing Advance and Power Control

Issue 12 Rev 2

Timing Advance and Power Control


To simplify the design of the mobile, the GSM Recommendations specify an offset of
three time-slots between the BSS and MS timing thus avoiding the necessity for the
mobile to transmit and receive simultaneously. The facing diagram illustrates this.
However, the synchronisation of a TDMA system is critical because bursts have to be
transmitted and received within the real-time time slots allotted to them. The further the
MS is from the BSS then, obviously, the longer it will take for the bursts to travel the
distance between them. The GSM BSS caters for this problem by instructing the MS to
advance its timing (i.e. transmit earlier) to compensate for the increased propagation
delay.
This advance is then superimposed upon the 3 time-slot nominal offset, as shown.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Timing Advance and Power Control

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

15

Issue 12 Rev 2

GSM Control Channels

GSM Control Channels


These are:

Broadcast Control Channel (BCCH).


Common Control Channel (CCCH).
Dedicated Control Channel (DCCH).

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.

The Synchronisation Channel (SCH) carries information for frame synchronisation


and includes the BSIC.

The Frequency Control Channel (FCCH) provides information for carrier


synchronisation.

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

Standalone Dedicated Control Channel (SDCCH) which supports the transfer of


Data to and from the MS during call setup, location updating and Short Message
Service (SMS).
Associated Control Channel (ACCH). This consists of slow ACCH which is used
for system information, radio link measurements and power control messages.
Fast ACCH is used to pass event type messages e.g. handover and disconnect
commands. Both FACCH and SACCH operate in uplink and downlink directions.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

GSM Control Channels

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

SDCCH SACCH FACCH

TRAFFIC
CHANNELS

TCH/F

TCH/H

SYS02_Ch1_03

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

17

Issue 12 Rev 2

Mapping Logical Channels onto the TDMA Frame Structure

Mapping Logical Channels onto the TDMA Frame Structure


Bursts
The diagram shows the five types of burst employed in the GSM air-interface and shows
that all bursts, of whatever type, have to be timed so that they are received within the
appropriate timeslot of the TDMA frame. The burst is the sequence of bits transmitted
by the BSS or MS the timeslot is the discrete period of real time within which it must
arrive in order to be correctly decoded by the receiver.
Each burst is enclosed by tail bits to indicate the beginning and the end of each burst.
The guard period is provided because it is required for the MSs that transmission be
attenuated for the period between bursts with the necessary ramp up and down.

1. Normal Burst:
S

Carries speech, data and control information within encrypted bits.

Training sequence is a set pattern of bits as defined by GSM Recommendations


05.02.

2. Frequency Correction Burst:


S

This burst is equivalent to an unmodulated carrier with a 67.7 KHz frequency


offset, above the nominal carrier frequency.

Used as a reference point by the BTSs to mark timeslot zero for the mobiles.

3. Synchronization Burst:
S

Synchronization sequence is as defined by GSM Recommendations 05.02

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.

5. Access Burst (Channel Request):


S

Synchronisation Sequence is a set state as defined by GSM Recommendations


05.02.

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.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Mapping Logical Channels onto the TDMA Frame Structure

Issue 12 Rev 2

GSM Burst Types

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

SYNCHRONISATION BURST (SB)


Encrypted Bits
39

6
3

Encrypted Bits
57

Fixed Bits
142

TB

1
1
FREQ CORRECTION BURST (FB)

TB

TB

NORMAL BURST (NB)


Encrypted Bits
57

TB

GP
68.25

3
156.25 Bit Durations
SYS02_Ch1_04

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

19

Issue 12 Rev 2

Multiframes and Timing

Multiframes and Timing


There are eight timeslots within each TDMA frame, enabling eight physical channels to
share a single physical resource the RF carrier. In turn, each physical channel may be
shared by a number of logical control or traffic channels.
In order to understand how a single physical channel is shared by various logical
channels, it is necessary to introduce the GSM multiframe structures that make it
possible.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Multiframes and Timing

Issue 12 Rev 2

51-Frame Multiframe Control Channel

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

111

Issue 12 Rev 2

Multiframes and Timing

Multiframes and Timing


The 51-frame
Control Channel
Multiframe
BCCH/CCCH
The BCCH/CCCH 51-frame structure illustrated on the opposite page will apply to
timeslot 0 of each TDMA frame on the BCCH carrier (the RF carrier frequency to which
BCCH is assigned on a per cell basis). In the diagram, each vertical step represents one
repetition of the timeslot (= one TDMA frame), with the first repetition (numbered 0) at the
bottom.
Looking at the uplink (MSBSS) direction, all timeslot 0s are allocated to RACH. This is
fairly obvious because RACH is the only control channel in the BCCH/CCCH group which
works in the uplink direction. In the downlink direction (BSSMS), the arrangement is
more complex Starting at frame 0 of the 51-frame structure, the first timeslot 0 is
occupied by a frequency correction burst (F in the diagram), the second by a
synchronisation burst (S) and then the following four repetitions of timeslot 0 by BCCH
System Information data (B) in frames 25. The following four repetitions of timeslot 0 in
frames 69 are allocated to CCCH traffic (C) that is, to either PCH (mobile paging
channel) or AGCH (access grant channel). Then follows, in timeslot 0 of frames 10 and
11, a repeat of the frequency and synchronising bursts (F and S), four further CCCH
bursts (C) and so on ..... Note that the last timeslot 0 in the sequence (the fifty-first
frame frame 50) is idle where the BTS will transmit a dummy burst.

112

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

50

50

40

S
F

40

SYS02 GSR5/AGSR: BSS Database

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

Multiframes and Timing

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

Issue 12 Rev 2

BCCH/CCCH Multiframe

EMOTOROLA LTD. 2001

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

Multiframes and Timing

Multiframes and Timing


The 102-frame
Dedicated
Control Channel
Multiframe
SDCCH and
SACCH
The diagram shows the 51-frame structure used to accommodate 8 SDCCHs although,
as it takes two repetitions of the multiframe to complete the entire sequence, it may be
more logical to think of it as a 102-frame structure! This structure will be used on a
physical channel selected by the system software it is not placed in a timeslot or on an
RF carrier specifically defined by GSM Recommendations.
Note that the 8 SACCHs (shaded) are associated with the 8 SDCCHs. It is important to
remember that each SDCCH has an SACCH just like a traffic channel.

114

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Multiframes and Timing

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

115

Issue 12 Rev 2

Multiframes and Timing

Multiframes and Timing


The 102-frame
Control Channel
Multiframe
Combined
Structure
The structure illustrated can be used where traffic density is low perhaps in a rural area
in cells with few RF carriers and only light traffic. Again, as it takes two repetitions of the
51-frame multiframe to complete the sequence, this is really a 102-frame structure.
In this case, all the control channel types (with the exception of the frame-stealer
FACCH) can share the BCCH carrier timeslot 0. In this configuration more SDCCH can
still be configured in the cell, albeit in other timeslots, however no more CCCH can be
defined.

116

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Multiframes and Timing

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

117

Issue 12 Rev 2

Multiframes and Timing

Multiframes and Timing


The 26-frame
Traffic Channel
Multiframe
The illustration opposite shows the time relationship between timeslot, TDMA frame, and
the 26-frame multiframe. Some of the times shown are approximate numbers as the
GSM Recommendations actually state the exact values as fractions rather than in
decimal form (eg. the exact duration of a timeslot is 15/26ms).
Note that frame 12 (the 13th frame in the 26 frame sequence) is used by the Slow
Associated Control Channel (SACCH) which carries link control information to and from
the mobile and base station. Also note that frame 25 is depicted as idle. The reason
why this frame is called idle is because uplink and downlink transmissions are temporarily
suspended. The MS, during this period, will go into search mode in an effort to
interrogate a neighbouring Base Transceiver Identity Code (BSIC).

118

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Multiframes and Timing

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

119

Mobile Activity Transmit and Receive Timeslots

Issue 12 Rev 2

Mobile Activity Transmit and Receive Timeslots


As the mobile only transmits or receives its own physical channel (normally containing
TCH and SACCH) for one-eighth of the time, it uses the remaining time to monitor the
BCCH frequency of adjacent cells. It completes this process every 480ms, or four
26-TCH multiframes. The message that it sends to the BSS (on SACCH, uplink)
contains the Receive Signal Strength Indication (RSSI) of the adjacent cells, plus that of
the link from the BSS itself and also an indication of the quality of the current connection.
This quality measurement is somewhat similar to a bit-error rate test. Just as the MS
completes one series of measurements, it completes sending the previous series to the
BSS and starts to send the latest series: thus the processes of compilation and
transmission form a continuous cycle.

120

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Mobile Activity Transmit and Receive Timeslots

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Software Architecture

Issue 12 Rev 2

BSS Software

Code object files

Code object files


can create a
system process

All procesors at the same site are downloaded


with all code object files

SYS02_Ch1_11

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

123

Issue 12 Rev 2

BSC Initialisation Process

BSC Initialisation Process


The BSC executive process is responsible for starting the initialisation of the GPROC,
using the initialisation process (IP), which is stored on Flash eeprom.
1.

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)

if site is a BSC > from OMC


if site is a BTS > from BSC

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.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

BSC Initialisation Process

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

127

Configuration Management (CM)

Issue 12 Rev 2

Configuration Management (CM)


Overview
The Configuration Management (CM) software is responsible for managing and updating
the main configuration database at either a BSC or a BTS. This is the database that is
downloaded as an object file in the download code. In this database is held all the site
parameters such as carrier frequencies, site configuration, surrounding site information
and handover parameters. Also stored in this database is device functionality and
distribution as well as all timing information for the site.
All application processes have access to this database but their access is read only. If
the CM database is required to be changed, the CM process performs this task. This
process has both read/write access to the CM Database.

128

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Configuration Management (CM)

Issue 12 Rev 2

Configuration Management Overview

Read Only
All Other Processes
CM
DATABASE
CM Process
Read/Write

SYS02_Ch1_14

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

131

Issue 12 Rev 2

CM Database and Central Authority Interaction

CM Database and Central Authority Interaction


To Change Site
Database
When outside of Sysgen mode any changes that are to be made to the CM database
have first to be checked and approved by the CA. This is done to ensure that the desired
changes are possible given the state of the devices in the system.
1.

Changes to database downloaded to MMI process from OMCR.

2.

The changes are downloaded to the CM process from the MMI process.

3.

The CM process writes the changes into the CM database.

4.

The CM process transfers the proposed changes to the CA.

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.

Operation outcome uploaded to the OMCR.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

CM Database and Central Authority Interaction

Issue 12 Rev 2

To Change Site Database

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

133

Issue 12 Rev 2

CM Database and CA Interaction

CM Database and CA Interaction


To Change
Remote BTS
Database
The process for changing elements of the database outside of Sysgen at a remote BTS
is basically similar to the process of changing a single site database.
1.

The OMCR downloads the proposed changes to the BSC MMI process.

2.

The BSC MMI downloads the changes to the BSC CM process.

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.

The CA replies yes or no to changes.

7.

The BTS CM process tells the BSC CM Process yes or no as to whether


changes possible.

8.

If answer from CA is yes, both CM processes now broadcast database


changes to all CM databases on their respective LANs.

9.

BSC CM process then tells BSC MMI the outcome of the operation, i.e.
whether changes have been completed or not.

10. BSC MMI uploads the operation outcome up to the OMCR.

134

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

CM Database and CA Interaction

Issue 12 Rev 2

To change Remote Database

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

135

Issue 12 Rev 2

Database Level Numbers

Database Level Numbers


Subsequent changes to a database during call processing can be made from the OMC
using a number of input mechanisms, these are TTY, Forms, Batch and Detailed view. In
any case the update is sent to the required entities using the procedure outline in the
previous pages.
The whole database for a BSS is stored in every entity of the BSS, the BSC for example
will initially have the same database as each BTS. Subsequent changes during call
processing will cause a disparity between databases held in different entities. If, for
example four consecutive changes are made to the database of BTS 3 using forms at
the OMC. The level number for BTS 3 at the BSC will be incremented by four, likewise
the level number at BTS 3 will also be incremented by four. Even though the database at
BTS 3 has changed the alterations are not passed on to BTS 1 or 2, they will still have
the old database for BTS 3 in store. Certain changes to a BTS database may be copied
to other BTSs, these changes will be necessary for the correct operation of the handover
procedure.
In the example shown opposite four changes have been made to the database of BTS 3
and one change has been made to the database of BTS 2. For each change made to an
individual site the database level number is incremented on a site basis, for each change
made to a BSS database the level number of the BSC is incremented.
If these changes are made using TTY, Batch, Forms or Detailed View at the OMC the
changes are made in the BSS as discussed but are not copied to the master database
held by the OMC. Hence any changes made to the BSS database should be followed at
some stage with a database upload to renew the database in the OMC. If this procedure
is not carried out, upon a BSC reset, the OMC could potentially download an old
database not current with any recent changes that have been made. As the OMC is
deemed the master entity the BSC would abandon any database it held and implement
the one being held and subsequently downloaded by the OMC.

136

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Database Level Numbers

Issue 12 Rev 2

Database Level Numbers

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

137

Issue 12 Rev 2

BSS Radio Subsystem

BSS Radio Subsystem


Overview
The Radio Subsystem (RSS) is a collection of application processes whose purpose is to
manage the BSS RF hardware and the radio link to the MSs. The RSS functions include
the Layer 2 interface to the MS LAPDm and radio link control including the handover
detection and power control process.
The RSS portion of the BSS implements the interconnection between the application
layer (Layer 3) and the physical channel hardware (layer 1). Currently one instance of
RSS has the messaging capability to handle six carriers, although an instance of RSS
would normally handle Layer 2 control for only 2 or 3 DRIMs, depending on the traffic
model in use. RSS runs on a single or multiple GPROCs which must be physically
located in the same cage as the Digital Radio Interface boards it controls.
The RSS is comprised of five components:
1.
2.

Layer 1 Interface

3.

Layer 2 Protocol

4.

RSS A-bis interface

5.

138

RSS configuration and fault management

Handover detection and power control

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

BSS Radio Subsystem

Issue 12 Rev 2

Radio Subsystem (RSS)

Software interface procedures between BSS RF hardware and MS

One subsystem has the capability to control 6 DRCUs.

SYS02_Ch1_19

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

139

BSS Configuration and Fault Management Interface

Issue 12 Rev 2

BSS Configuration and Fault Management Interface


Overview
This process controls the configuration of its related DRCUs, and is the interface to the
BTS fault management system. With regard to configuration, this process is responsible
for informing the hardware as to its configuration, and instructing the DRCU as to the
usage of each timeslot (e.g. BCCH, SDCCH 8 channel or TCH/FS). The process also
has the responsibility of downloading the DRIM board during the initialisation of the base
site, as well as the loading and configuration of the DRCU before call processing is
achieved.
The collection of alarm and error messages is also the responsibility of this process. The
alarm and error indications are then forwarded to the Fault Collection Process (FCP) of
the GPROC on which the RSS functionality exists.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

BSS Configuration and Fault Management Interface

Issue 12 Rev 2

Radio Subsystem (RSS)

To call processing

To fault management

Abis

RSS
CFM

Layer 2
HDPC

Layer 1

To the radio hardware


SYS02_Ch1_20

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

141

Handover Detection and Power Control

Issue 12 Rev 2

Handover Detection and Power Control


This process has by far the most functions to fulfil inside the RSS. It controls the
transmission power of the MS (uplink) and also the transmission power of its related TCU
(downlink) on a per timeslot basis. The object is to keep both the MS and the TCU on the
lowest possible transmission power to help reduce interference between system users.
This process is also responsible for calculating the MSs timing advance to keep the
mobile inside its allocated timeslot.
The handover detection and power control process takes responsibility for initiating the
handover process for a MS. It decides when the handover is necessary, i.e. the MS is on
maximum power but the received level at the BSS is still too low or the MS is on
maximum timing advance. It follows the handover procedure as suggested in GSM
Recommendation 5.08 plus a number of special Motorola algorithms can be
implemented.
When TCHs are idle, this process monitors the ambient noise in the receive slot period.
After processing, the average noise level per TCH is passed to call processing.
Once a call to a MS has been established, if a MS leaves the system without terminating
the call, the system will waste its resources if the MS channel remains in operation. To
reduce this, the handover detection and power control process monitors the SACCH
messages from all MS on its busy TCHs. If a number of consecutive SACCH messages
from a particular MS fail to appear, the process informs call processing software to close
down the resources allocated to that MS.
All messaging to and from the handover detection and power control process are in the
A-bis format. Therefore the location of this process is in theory interchangeable,
depending upon which A-bis format is chosen.

142

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Handover Detection and Power Control

Issue 12 Rev 2

Handover Detection and Power Control

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Call Processing

Issue 12 Rev 2

Call Processing

Collection of Layer 3 procedures

Functions
Call setup
Airinterface encryption
Control of handovers
Signalling (MSC to BSS)
(BSS to MS)

SYS02_Ch1_22

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Call Processing

Issue 12 Rev 2

Call Processing Flow Chart

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Call Processing

Issue 12 Rev 2

Radio Channel Allocation

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

149

Comparison GSM and Motorola Systems

Issue 12 Rev 2

Comparison GSM and Motorola Systems


Under the GSM defined system, most of the intelligence of the BSS is kept at the BSC.
All handover decisions, allocation of TCHs and monitoring of active radio channels is
done at the BSC itself. This means that a great deal of control messaging/signalling must
pass between the BTS and the BSC along the A-bis interface, the greatest overhead
being MS uplink measurement reports.
Due to the large amount of signalling/message transfer, there is a large requirement for
Radio Signalling Link (RSL) timeslots between the BSC and BTS.
These RSL timeslots utilise the Link Access Protocol Data Layer 2 protocol to carry the
signalling and BTS control messages. Each LAPD signalling link will occupy a complete
64 Kbit/second timeslot on the A-bis Interface.

150

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Comparison GSM and Motorola Systems

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

151

Comparison GSM and Motorola Systems

Issue 12 Rev 2

Comparison GSM and Motorola Systems


Using the Motorola system, the control of the radio and terrestrial circuits is divided
between the BSC and the BTS. The BSC retains the processes which control the
Terrestrial links up to the MSC and the final decision process concerning handovers.
Meantime, the BTS has all the processes to monitor and control the radio channels. The
Motorola application generally needs 1 RSL per BTS site.
This reduction in dedicated Abis links is achieved because far fewer control/signalling
messages are required between the BSC and the essentially more intelligent BTS. Using
less 2MB timeslots for signalling allows more TCH channels and hence more economic
use of the BSC-BTS link.
From GSR 5, automatic allocation of traffic channels is also carried out on the Ater
Interface between the RXCDR and the BSC. Using the dynamic switching capability of
the transcoder, the Ater traffic channels are held in a pool and are allocated to calls as
and when they are needed, rather than being statically mapped between the RXCDR and
BSC. This process requires the operation of 2 new logical devices; the Associate Remote
Transcoder (AXCDR) at the BSC and the Associate Base Station System (ABSS) at the
transcoder. The 2 devices act to allocate channels dynamically using the Allocation
Manager process responding to control messages sent on the Transcoder Basesite Link
(XBL) control channel, which has been enhanced in importance to fulfil this capability.

152

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Comparison GSM and Motorola Systems

Issue 12 Rev 2

Motorola System (GSR 5)

MSC

Switch
Manager

Allocation
Manager

RXCDR
ABSS
A ter interface

XBL
AXCDR

BSC

MTP L3/SCCP Preprocessor

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

153

Comparison GSM and Motorola Systems

154

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Issue 12 Rev 2

EMOTOROLA LTD. 2001

Chapter 2

Site Configuration

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Issue 12 Rev 2

ii

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Chapter 2
Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21
21

Configuring a BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22

The Base Station System (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


The Base Station Controller (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Base Transceiver Station (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24
24
24

Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

26

Command/Database Parameter Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

28

RXCDR/BSS/SITE/CAB/CAGE Numbering Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

210

Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipping the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

212
212

Equipping the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

BSC/ BTS Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

230

GPROC Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

232

Remote Loss Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

236

Site Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

238

Slip Loss Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

240

BER Loss Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

242

BER Monitoring Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

244

N Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

246

Integrated M-Cell HDSL interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

248
248
248
248
248

Physical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

250
250
250

HDSL Monitoring Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

252

HDSL SNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

254

HDSL Loss of Sync Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

256

Site Configuration Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Site Configuration Exercise 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Configuration Exercise 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

258
258
260

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

iii

Issue 12 Rev 2

iv

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Site Configuration

Issue 12 Rev 2

Site Configuration
Objectives
On completion of this chapter the student will be able to:
S

Describe the device/function interdependency with the database structure.

Describe typical BSS configuration and terrestrial traffic and signalling links.

Equip and understand the database fields associated with site configuration.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Configuring a BSS

Issue 12 Rev 2

General Database Script

EQUIP BSS, RXCDR or SITE

EQUIP AXCDR or ABSS

EQUIP CABINET
EQUIP CAGE

SITE CONFIGURATION
(CHANGE ELEMENTS)
ADD CELL [BTS/BSS ONLY]

EQUIP DEVICES (DIGITAL BOARDS)

EQUIP FUNCTIONS
SYS02_Ch2_01

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

23

Issue 12 Rev 2

The Base Station System (BSS)

The Base Station System (BSS)


A BSS can be divided into three functions, the BSC, the BTS and the XCDR.

The Base Station


Controller (BSC)
The BSC is the digital control function which performs the following:
1.

Controls all associated Base Transceiver Stations (BTS).

2.

Performs call processing

3.

Supports operations and maintenance

4.

Supports the interface between the BSS and Mobile Switching Centre (MSC).

5.

Supports the interface between the BSC and BTS.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

The Base Station System (BSS)

Issue 12 Rev 2

BSC Site Configuration

Site 1

Site 2
BTS

BTS
LAN
Fibre Optic
cable

BTS

BSC
WITH
XCDR

Site 0

MSC

Operations and Maintenance


Link (OML)

OMC
SYS02_Ch2_02

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

27

Command/Database Parameter Types

Issue 12 Rev 2

Command/Database Parameter Types


MMI commands and database parameters are classified on the basis of whether or not a
user action is required to enter the command or change the value of the database
parameter.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Command/Database Parameter Types

Issue 12 Rev 2

Command Types

Type A
No operator actions

Type B
Special conditions exist
(refer to W23 BSS command reference manual)

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

29

Issue 12 Rev 2

RXCDR/BSS/SITE/CAB/CAGE Numbering Scheme

RXCDR/BSS/SITE/CAB/CAGE Numbering Scheme


Motorola have developed a conventional numbering scheme that must be adhered to in
the equipage of a RXCDR, BSS, SITE, Cabinet and Cage. Cage references are for
In-Cell stations, cages are not explicitly equipped at M-Cell sites because the cabinet
does not have a cage structure.
From GSR 5, the term SITE is used for BTS sites.
RXCDR, and BSCs (both with local transcoding and with remote transcoding) are
equipped separately as RXCDR and BSS; both BSS and RXCDR will be created as site
0 within the initial equip command, but also require a unique network identity (id)
number between 1 and 128. A BSC and RXCDR are thereafter known as BSS xxx or
RXCDR xxx within a network.
For example a network will henceforth have a BSS 1, possibly a RXCDR 1 (some
networks may decide to use the range of 1 - 128 to differentiate between BSS and
RXCDRs).
Within a BSS system, BTS SITES will have site numbers as now from 1 to 100. The BSS
system will focus on the BSS itself and its dependant BTS sites, although a BSS may be
served by more than 1 RXCDR (up to 5). Likewise, a RXCDR may serve up to 5 BSS
systems.

RXCDR/BSS/SITE/CAB/CAGE NUMBERING CHART


SITE TYPE

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

Shown opposite are some typical examples of this scheme.


Notes:
1. A BSS, whether with local or remote transcoding, may or may not be of standalone
type with DRIs (ie a BSC/BTS).
2. The previous parameter fm_site_type is no longer used following upgrade to GSR 5.
The site type is equipped in the equip_0/bsc_bss, rxcdr or site command. Within the
prompts which follow equip_0/bsc_BSS and equip_0/bsc_RXCDR, the command
prompts will automatically set the fm_site_type element to the correct value. If the local
site number is greater than zero, fm_site_type is always set to BTS. If the local site
number is zero, fm_site_type will be either RXCDR, BSC or collocated BSC/BTS. To
distinguish between these three options, the user can use the command disp_bss to
determine if the site is a RXCDR or BSC. If the site is a BSC, the operator may use
disp_equip on the BSS to determine if the site is a collocated BSC/BTS (DRIs are
located at the BSC) or a standalone BSC (DRIs are not located at the BSC).

210

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

RXCDR/BSS/SITE/CAB/CAGE Numbering Scheme

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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 or bsc> RXCDR


1st prompt (identifier)
This prompt specifies the transcoder network number between 1 and 128.
Following the RXCDR equipage, an associate BSS must be equipped for each BSC to
which the RXCDR is connected.

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.

2nd prompt (whether EFR is enabled)


This prompt specifies whether enhanced full range voice is enabled in the connected
BSS.

3rd prompt (Volume control)


This prompt indicates whether overall volume control is exercised at the RXCDR.

4th prompt (downlink volume control level)


This prompt sets the downlink volume control level within the RXCDR.

5th prompt (uplink volume control)


This prompt sets the uplink volume control in the RXCDR.
212

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Site Configuration

Issue 12 Rev 2

Site Configuration
equip <0 or bsc> RXCDR
S

Enter the RXCDR id:


(range 1 128)
equip <0 or bsc> abss

Enter the abss device id:


(range 1 128)

Enter the value for EFR enabled:


0 = no EFR
1 = EFR enabled

Enter the volume control type:


0 = no volume control
1 = volume control applied at RXCDR

Enter the downlink audio level offset:


range 15 to +15 dB gain applied

Enter the uplink audio level offset:


range 15 to +15 dB gain applied

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

213

Issue 12 Rev 2

Equipping the BSS

Equipping the BSS


The first line in a database script will equip the BSS. After the first line, additional
prompts will appear. Again, following the equipage of the BSS, it will be necessary to
equip an AXCDR for each RXCDR to which the BSC is connected.

equip <0 or bsc> BSS


1st prompt (identifier)
This prompt specifies the local BSC number between 1 and 128.

2nd prompt (whether DRIs are co-located)


This prompt specifies whether the site is a combined BSS/BTS.

3rd prompt (whether local transcoding is performed)


This prompt specifies whether the site is a BSS with local transcoding.

equip <0 or bsc> AXCDR


1st prompt (identifier)
This value corresponds to the network identity of the RXCDR represented by this
AXCDR.

2nd prompt (CIC Validation Mode)


This prompt defines whether the Ater (BSS - RXCDR) is operating in a dynamic
(Auto-Connect) mode, i.e. that Ater circuits will be allocated to calls automatically.

214

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Equipping the BSS

Issue 12 Rev 2

Site Configurations

equip <0 or bsc> bss


S

Enter the bss id:


(range 1 128)

Are DRIs co-located at the BSC?


Yes/No

Is local transcoding performed at the BSC?


Yes/No
equip <0 or BSC> AXCDR

Enter the AXCDR device id:


Range 1 to 128

Enter CIC validation mode:


Yes/No

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

equip <0 or bsc> SITE


1st prompt (identifier)
This prompt will be a number between 1 and 100, which will identify the BTS within the
Base Station System.

2nd prompt (BSP/LCF)


This prompt denotes whether a BSP or LCF is supporting the RSLs for the site.

3rd prompt (BSP/LCF)


This prompt denotes the unique identifier of the BSP or LCF supporting the RSLs.

4th prompt (RSL rate)


This prompt specifies the RSL rate to be implemented. The prompt is displayed only if
the site is remote and the 16k RSL option is enabled.

5th prompt (Dynamic allocation)


This prompt only appears if:
The dynamic allocation feature is unrestricted.
The site being equipped is a standalone BTS
The prompt refers to dynamic allocation of Abis traffic channels where a DYNET device
is used (this will only occur if the BTS is In-Cell, M-Cell Access or Horizon Office).

216

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Equipping a SITE

Issue 12 Rev 2

Site Configurations

equip <0 or bsc> SITE


S

Enter the site identifier


1 to 100

Enter the type of BSP or LCF


BSP or LCF

Enter the function identifier for the BSP or LCF


0 or 1
0 to 24

Enter the RSL type


16 or 64

Does the site use dynamic allocation of terrestrial backing


resources
Yes/No

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

217

Issue 12 Rev 2

Site Type

Site Type
The BSS is very flexible and can have many configurations consisting of three elements;
1.

Base Station Controller (BSC)

2.

Base Transceiver Station (BTS)

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

1st prompt (identifier):


This prompt specifies the unique identifier fo the cabinet.

2nd prompt (cabinet type)


An integer code or equivalent test string is used to specify the cabinet type being
equipped, this is necessary for the IAS to process and accurately report alarms.
In the case of entering 15 or M_Cellcity, 16 or M_Cellarena and 20 or
M_Cellarena_Macro the following prompt will appear:
Is an internal HDSL modem present: Yes/No
In the case of entering 15 or M_Cellcity, 16 or M_Cellarena the following prompt will
appear:
Is an internal integrated antenna present: Yes/No
These two prompts are only relevent to the M-Cellcity product. In the case of remote
M-Cell cabinets (those having no MCU) integers 12 and 13 should be specified
depending on cabinet type.
Cabinet types 18 and 19 can also now be used with PCS 1900.

3rd prompt (frequency type):


An integer code, or unique text string is used to specifiy the frequency ranges used within
the specified cabinet.
Note: If the frequency type entered contains GSM850 as a selection, the cabinet type
must be 18 or 19.

220

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

2nd prompt (KSW pair)


Up to four pairs of KSWs (03) can be equipped at a site. This parameter identifies
which pair manages that particular cage and therefore, which TDM highway the cage is
being served by. This field must equal the first i.d. of the KSW equipage, the Highway
supported by the KSW.

3rd/4th prompts (KSW Extension)


It is possible to extend a TDM highway driven by a particular KSW/TSW to a number of
extension cages. If redundancy has been implemented then each TDM highway has
associated with it a pair of KSWs. The next two parameters identify which KSWX(R)
(slot position) in the parent connects the cage to the source active and redundant KSW.
These two parameters are optional and are only required if the cage being equipped is an
extension (child) cage. A cage backplane diagram is at page 41 of section 1.2. The 04
code being used signifies the A0A4 or B0B4 KSWX(R) slots being used in the parent
shelf

5th prompt (cabinet)


This parameter defines the cabinet in which the cage belongs.

6th prompt (ias)


This is an optional parameter and is necessary to specify whether the cage has a
connection to the Internal Alarm System (IAS) equipment (PAB, DAB etc ...). In most
cases the answer will be yes, the exception to this being a BSSC cabinet where 2
cages can be fitted, only one of which having the IAS connection.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Cage Equipage

Issue 12 Rev 2

Cage Equipage

equip <site number> CAGE

Enter the identifier for the cage:


0 13 BSC
0/1 RXCDR
15 2 BTS

Enter the KSW pair that manages the cage: 0 3

Enter the KSWX connecting cage to KSW for TDM 0: 0 4

Enter the KSWX connecting cage to KSW for TDM 1: 0 4

Enter the cabinet to which the cage belongs: 0 15

Is an IAS connected? Yes/No

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Transcoder Location

Issue 12 Rev 2

Transcoder Location

30 x 64 kbs channels

30 x 16 kbs channels

XCDR

chg_element transcoder_location <*><SITE No>


*

0 = Transcoding remotely
1 = Transcoding locally (BSC/CoLocated)
SYS02_Ch2_06

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

229

Issue 12 Rev 2

BSC/ BTS Types

BSC/ BTS Types


If the incorrect site type is entered in the database problems will arise during the
initialisation process. The site will be downloaded as normal, but on configuration,
discrepancies will arise in the database.
If for example a BTS site was configured as a type 1 instead of 0 on configuration it will
expect to find GPROCs to become Digital Host Processors (DHP) which may not
physically be either there or equipped in the database. Therefore, configuration of the
site will not take place.

230

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

BSC/ BTS Types

Issue 12 Rev 2

BSC/BTS types

chg_element bsc_type <*><SITE No>

chg_element bts_type <*> <SITE No>


(not required at an M-Cell site)

* 0 =

BTS type 0

1 =
2 =

EMOTOROLA LTD. 2001

BSC/BTS type 1
BSC type 2

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

GPROC Slots

Issue 12 Rev 2

GPROC Slots

chg_element gproc_slots <*><SITE No>

EMOTOROLA LTD. 2001

16 or 32

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Site Synchronisation

Issue 12 Rev 2

Sync Loss

Alarm locked out

HOURS
Alarm threshold
reached

SYS02_Ch2_10

chg_element sync_loss_daily <*><SITE No> Default 16

chg_element sync_loss_hourly <*><SITE No> Default 20

chg_element sync_loss_oos <*><SITE No> Default 511


* Number of alarm conditions
Range 0 to 65535

chg_element sync_loss_restore <*><SITE No> Default 6000


* integer (100mS periods)

EMOTOROLA LTD. 2001

Range 0 to 65535

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

235

Issue 12 Rev 2

Remote Loss Alarms

Remote Loss Alarms


As previously mentioned the MSI/XCDR can track sync alarms from its own transmit by
receipt of the remote flag from the distant end.
This flag allows the monitoring of restore sync losses in much the same way as the sync
loss parameters on the previous page.

236

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Remote Loss Alarms

Issue 12 Rev 2

Remote Loss Alarms

chg_element remote_loss_daily <*><SITE No> Default 16

chg_element remote_loss_hourly <*><SITE No> Default 20

chg_element remote_loss_oos <*><SITE No> Default 511


* Number of alarms

Range 0 to 65535

chg_element remote_loss_restore <*><SITE No> Default 6000


* integer (100mS periods)

EMOTOROLA LTD. 2001

Range 0 to 65535

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

chg_element sync_time_oos <*><SITE No> DEFAULT = 25

chg_element sync_time_restore <*><SITE No>DEFAULT = 150

chg_element remote_time_oos<*><SITE No>DEFAULT = 5

chg_element remote_time_restore<*><SITE No>DEFAULT = 5


* integer (100mS periods)
Range 0 to 65535

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

239

Issue 12 Rev 2

Slip Loss Alarms

Slip Loss Alarms


The MSI/XCDR contains an elastic 2 frame buffer to account for slip loss, if this loss
exceeds the size of the buffer a TDM frame will be lost as the buffer resets, each time
the buffer resets, a slip loss alarm is generated. Each slip loss alarm is counted and
subject to similar thresholds mentioned.

240

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Slip Loss Alarms

Issue 12 Rev 2

Slip Loss Alarms

chg_element slip_loss_daily <*><SITE No> Default 4

chg_element slip_loss_hourly <*><SITE No> Default 4

chg_element slip_loss_oos <*><SITE No>Default 255


* Number of slip loss alarms

Range 0 to 65535

chg_element slip_loss_restore <*><SITE No> Default 6000


* integer (100mS periods)

EMOTOROLA LTD. 2001

Range 0 to 65535

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

241

Issue 12 Rev 2

BER Loss Alarms

BER Loss Alarms


Bit Error Rates (BER) are constantly being checked by an MSI/XCDR card, the period
over which they are assessed for out of service purposes is controlled by
ber_oos_mon_period.
An alarm will be generated when the daily and hourly thresholds for BER are exceeded.

242

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

BER Loss Alarms

Issue 12 Rev 2

BER Loss Alarms

chg_element ber_loss_daily <*><SITE No> DEFAULT = 6

chg_element ber_loss_hourly <*><SITE No>DEFAULT = 4

ber rate
e.g. 4= 10e4
Range 3 to 6

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

243

Issue 12 Rev 2

BER Monitoring Periods

BER Monitoring Periods


The MSI/XCDR card monitors the Bit error rate of the incoming 2MB, the BER can be
determined using the fixed bits of the Frame Alignment Word and Frame Data Word.
The fixed Bits do not alter and therefore are ideal to calculate BER.
The ber_oos_mon_period is the period that an in-service MMS must exceed the set
BER rate before it is taken out of service. The BER rate is set in firmware at 10e3.
The ber_restore_mon_period is the amount of time an out of service MMS must
exceed the set BER rate before it can be put back in service. The location for both of
these periods can be set individually for each site but more usually is set to all to include
every site in the BSS.

244

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

BER Monitoring Periods

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

modify_value<location>ber_oos_mon_period <*> MMS


* 1-60 seconds
Default 1
modify_value<location>ber_restore_mon_period<*> MMS
* integer (100mS periods)
* 1-18000
Default 6000

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

N Bit

Issue 12 Rev 2

N Bit

TIMESLOT 0 STRUCTURE

I.U
1

SYNC
REMOTE
N BIT
TOGGLE ALARM

I.U
5

SPARE SPARE SPARE FDW


6

8
SYS02_Ch2_13

modify_value<location>nbit<*>MMS
*

EMOTOROLA LTD. 2001

0 disabled
1 enabled

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

247

Issue 12 Rev 2

Integrated M-Cell HDSL interface

Integrated M-Cell HDSL interface


The implementation of this optional feature introduces a High bit-rate Digital Subscriber
Line (HDSL) interface into the Motorola BSS product line. HDSL is a data transmission
mechanism which supports duplex high speed digital communication (at E1 rates) on one
or more unshielded twisted pair lines.

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.

Between integrated HDSL NIUs at M-Cell sites, as shown fig 3.

An integrated HDSL NIU is able to contain up to a maximum of two HDSL


modems, one per span. An HDSL modem is required at both ends of the HDSL
interface, one end must be designated the master, the other the slave.

Implementation of this feature also provides the following new functionality to


support an integrated HDSL interface:

HDSL link management at an M-Cell site.

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.

The following constraints are applicable:

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.

The configuration of an HDSL interface using external HDSL modems is not


supported by this feature.

Requirements

Functionality

Constraints

248

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Integrated M-Cell HDSL interface

Issue 12 Rev 2

External modem at a BSC connected to an integrated


HDSL NIU

Fig 1
BSC

Key

E1

Slave
Modem

Master
Modem

M
MCell

External modem at an M-Cell site connected to an integrated


HDSL NIU
E1

Fig 2

MCell

Key
S

E1

Slave
Modem

Master
Modem

HDSL

MCell
SYS02_Ch2_14

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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 interface is supported on a minimum of one or a maximum of two


unshielded twisted pair carriers.

The HDSL NIU can be unequipped and re-equipped to change the number of
64kbit/s timeslots supported on a span.

An HDSL interface supports a minimum of 16 64kbit/s timeslots, bearing in mind


that only 15 of these timeslots are available for use. Timeslot 0 is the E1
synchronisation timeslot and is unavailable for traffic.

An HDSL interface supports a maximum of 32 64kbit/s timeslots, bearing in mind


that only 31 of these timeslots are available for use. Timeslot 0 is the E1
synchronisation timeslot and is unavailable for traffic.

The M-Cellcity+ and M-Cellarena support a maximum of two HDSL interfaces on a


single HDSL NIU.

MMS clock extraction is supported on HDSL links.

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.

The default status of the local HDSL NIU is set to:

HDSL (master) on MMS0, HDSL (slave) on MMS1.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Physical interface

Issue 12 Rev 2

HDSL interface between integrated HDSL NIUs

Fig 3
E1
MCell
S

Key
S

Slave
Modem

Master
Modem

M
MCell
SYS02_Ch2_15

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

251

Issue 12 Rev 2

HDSL Monitoring Period

HDSL Monitoring Period


hdsl_oos_mon_period sets the time monitoring period to ascertain on OOS condition.
hdsl_oos_restore_period sets the time monitoring period for expiry of an OOS
condition.

252

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

HDSL Monitoring Period

Issue 12 Rev 2

HDSL Monitoring Period

modify_value <location> hdsl_oos_mon_period <*>


mms <MMS_1D1> <MMS_ID2>

modify_value<location>hdsl_restore_mon_period<*>
mms <MMS_ID1> <MMS_ID2>

<*>

Integer, representing a period in seconds.


(2 to 14,400 in steps of 2s)

default:

EMOTOROLA LTD. 2001

2 for hdsl_oos_mon_period
600 for hdsl_restore_mon_period

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

HDSL SNR

Issue 12 Rev 2

HDSL Signal to Noise Ratio

chg_element hdsl_snr_hourly <*> <location>


chg_element hdsl_snr_daily <*> <location>
chg_element hdsl_snr_oos <*> <location>
chg_element hdsl_snr_restore <*> <location>
<*>

Integer, representing thresholds in 0.5 dB steps


(range 6 to 44)

default values:

18 for hdsl_snr_hourly
16 for hdsl_snr_daily
14 for hdsl_snr_oos
16 for hdsl_snr_restore

chg_element hdsl_snr_daily_mon_period <*> <location>

S chg_element hdsl_snr_hourly_mon_period <*> <location>


<*> Integer, in seconds (065534)

EMOTOROLA LTD. 2001

default values: 20 sec

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

255

Issue 12 Rev 2

HDSL Loss of Sync Word

HDSL Loss of Sync Word


hdsl_losw_oos specifies the loss of sync word out of service threshold period.
hdsl_losw_restore specifies the loss of sync word restoral period.
These parameters may only be changed at an M-Cell site. If changed, all master
modems at the local M-Cell are affected. All slave modem alarm thresholds are identical
to the master modem alarm thresholds.

256

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

HDSL Loss of Sync Word

Issue 12 Rev 2

HDSL Loss of Sync Word

chg_element hdsl_losw_oos <*> <location>

chg_element hdsl_losw_restore <*> <location>

Integer value representing a period in seconds


(0 65535)
Default value = 6

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

257

Issue 12 Rev 2

Site Configuration Exercises

Site Configuration Exercises


Site
Configuration
Exercise 1
The following exercise will give the student the opportunity to practice the theory
presented in this section. The page opposite gives a diagramatic representation of a
typical BSC site running GSR 5, showing only the equipment necessary to allow the
student to build this first part of the database. Blank parameters are also available to
populate the required database fields.
The BSC site consists of one BSSC dab cabinet utilising both cages. There are multiple
working GPROC 2s at this site all having a maximum number of TDM highway slots.
If a prolonged synchronisation alarm of 10 seconds is suffered by any 2MB terminated at
site 0 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 0 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.
The network uses the PGSM band.

258

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Site Configuration Exercises

Issue 12 Rev 2

Site Configuration Exercise Number 1


chg_element bsc_type
chg_element gproc_slots

# BSC SITE (1 128)


# LOAD 1.6.2.0 (GSR 5)
equip bsc bss
>
>
>
>
>
equip bsc axcdr
>
>
freq_types_allowed 5
equip bsc cab
>
>
>
equip cage
>
>
>
>
>
>
equip cage
>
>
>
>
>
>

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

EMOTOROLA LTD. 2001

Cabinet 0 Cage 1

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

SYS02_Ch2_16

259

Issue 12 Rev 2

Site Configuration Exercises

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Site Configuration Exercises

Issue 12 Rev 2

Site Configuration Exercise Number 2

#
#

BTS SITE 12
LOAD 1.6.0.0 (GSR4)

equip bsc SITE


>
>
>
>
equip 12 CAB
>
>
>
equip 12 CAB
>
>
>

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

261

Issue 12 Rev 2

Site Configuration Exercises

262

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Chapter 3

Cells

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Issue 12 Rev 2

ii

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Chapter 3
Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31
31

Cell Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

34

Location Area Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

36

Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

38
38

Frequency Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

310

Base Station Identity Code (BSIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

312

PLMN Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

314

MS Transmit Power Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Common Control Channel (CCCH) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

328

Common Control Channel (CCCH) Block Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .

330

MS Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

332

Extended Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

334

Periodic Updates/rr_t3212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

336

Attach/Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

338

Cell Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

340

Emergency Call Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

342

Channel Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

344

Wait Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

346

Signalling Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
rr_t3101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

348
348

Channel Allocation by Interference Band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

350
352

Channel Allocation by Interference Band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

353

Assignment of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

354

Queue Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SDCCH Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

356
356

Channel Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

358

Preferred Number of SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

360

SDCCH Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

362

SDCCH Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

364

Measurement Reporting for Handovers and Power Control . . . . . . . . . . . . . . . . . . . . . . .

366

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

iii

Issue 12 Rev 2

BA Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BA Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signal Strength Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

370

Signal Quality Reporting RXQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

372

BSS Processing and Threshold Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Measurements Reported by MS on SACCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measurements Performed by RSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

374
374
374

Threshold Comparison Process Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

376

Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

378
378
380

alt_qual_proc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

382
384

Handover RXQUAL, RXLEV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

386

Handover Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

388

MS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS Maximum Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

390
390

BTS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

392

BTS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

394

Rapid MS Power Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

396

Optimized Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3100

Optimized Power Control Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3102

Discontinuous Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3104

Handover Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3106

Handovers Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3108

SDCCH Access handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3110

Handovers Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Budget Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3112
3114

Timing Advance MS Maximum Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3116

HandoverMS Maximum Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3118

Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Incoming Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intra-Cell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inter-Cell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3120
3120
3122
3122

TCH Resources Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3124

Preferred Target Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3126

Handover Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Evaluating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3128
3128
3128

Handover Power Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3130

Calculated Handover Power Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Default Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv

368
368

3132
3132
3134

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Handover Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
rr_t3103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3136
3136

Handover Channel Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3138

RSS Link Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Radio Link Revival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3140
3142

Loss of Radio Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3144

Timers rr_t3109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uplink Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3146
3146
3146

Timers rr_t3109, rr_ t3111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Normal Channel Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
rf_chan_rel_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Issue 12 Rev 2

vi

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Cells

Issue 12 Rev 2

Cells
Objectives
On completion of this chapter the student will be able to:
S

EMOTOROLA LTD. 2001

Equip and understand the database fields associated with adding a cell.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Cell Identity

Issue 12 Rev 2

Cell Identification

Mobile
Country Code

Mobile
Network Code

Location
Area Code

Cell
Identity

Location Area Identification

Cell Global Identification

SYS02_Ch3_02

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

35

Issue 12 Rev 2

Location Area Codes

Location Area Codes


The Mobile Country Code (MCC) is a threedigit number that identifies the country to
which the system belongs. Two octets are dedicated to the MCC, octet A for the first two
digits, the first four bits of octet B for the third digit. The last four bits of Octet B are
normally set to 1s.
Some countries may have more than one GSM system, so the MCC will be common to
each. To identify the particular system within the country that a GSM cell belongs to,
each country has been allocated two, Mobile Network Codes (MNC). If there are more
than two systems within a particular country, then an MNC can be borrowed from another
country. Octet C is dedicated for the two digits of the MNC. However, if an operator is
using PCS 1900 or GSM 850, they have the option of a third MNC digit. In this case the
four bits of Octet B that are normally set to 1s are used.
Mobiles have to periodically inform the system as to where they are within the system.
These are called Location Updates. The system has to know the whereabouts of a
particular MS so that resources in a particular part of the system can page the MS to
inform it of an incoming call. If the whereabouts of the MS were unknown then system
wide paging would have to take place, which is inefficient.
Location updates may occur periodically, after a set period of time and when a MS
moves from one area to the system to another. The only way a MS can detect that it has
changed areas, is by reading the Location Area Code (LAC) that is transmitted on the
BCCH of each cell.
Two octets, D and E are allocated for the LAC, giving it a range of 0 65535.
Octets F and G are to identify the cell in a particular location area. As two octets are
allocated for this purpose, the Cell Identity (CI) range is 065535.
The MCC, MNC, LAC and CI together provide the cell global identification.

36

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Location Area Codes

Issue 12 Rev 2

Location Area Identity

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

Example shown is a non-PCS1900 and GSM850 system


SYS02_Ch3_03

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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 database parameter has a default value this may be engaged by simply


pressing return.

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.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Frequency Type

Issue 12 Rev 2

Frequency Type

freq_type = <*>

<*>

= 1 Frequency type of the cell is GSM900


primary band.
= 2 Frequency type of the cell is GSM900
extended band.
= 4 Frequency type of the cell is GSM1800
band.
= 8 Frequency type of the cell is PCS1900
band.
= 16 Frequency type of the cell is GSM850 band.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

311

Base Station Identity Code (BSIC)

Issue 12 Rev 2

Base Station Identity Code (BSIC)


Every cell has a BSIC that allow an MS to distinguish between different neighbouring
cells. The BSIC is encoded on the SCH and is one octet in length. It consists of the
Network Colour Code (NCC) and Base Station Colour Code (BCC).
The BSIC may be reused but it is important that neighbour cells do not share the same
BSIC and BCCH RF carrier.

312

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Base Station Identity Code (BSIC)

Issue 12 Rev 2

Base Station Identity Code (BSIC)

NCC
011 = 3

101 = 5

3 bits

NCC

BCC

3 bits

BCC
1

BSIC = 29 (1D HEX)

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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)

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

SYS02_Ch3_07

315

Issue 12 Rev 2

MS Transmit Power Access

MS Transmit Power Access


Because of the nature of cellular systems the output power of MS and BSS should be
kept as low as possible to minimise the effects of introducing interference into the
system and maximising the battery life duration of the portable MS. Power control of the
MS and BSS is a function of the BSS. Before the BSS can control the output power of
the MS, the MS must have accessed the cell so that the BSS has a reference signal
strength to use.
When accessing a cell on the RACH and before receiving the first power command
during communication on a SDCCH or TCH the MS must use the power level defined by
in the ms_txpwr_max_cch field in the database or the maximum transmit power of the
MS as defined by its power class, whichever is the lower.

316

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

MS Transmit Power Access

Issue 12 Rev 2

MS Access Power Output

ms_txpwr_max_cch=<*>
*

for GSM 900/EGSM/GSM 850


2 = 39 dBm
.
19 = 5 dBm
*

for GSM 1800/PCS 1900


0 = 30 dBm
1 = 28 dBm
2 = 26 dBm
.
15 = 0 dBm

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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=

> Good downlink path


> Poor downlink path

B=

318

+ value
value
value
+ value

> Good uplink path


> Poorer uplink path

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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= <*>

1 - C2 parameters are to be broadcasted


0 - C2 parameters are not to be broadcasted

cell_reselect_offset= <*>
*

integer code for dB offset


0= 0dB
1= 2dB
2= 4dB
.
.
63= 126dB

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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= <*>
*

integer code for 10's of dBs offset


0= 0dB
1= 10dB
2= 20dB
3= 30dB
.
.
.
7= infinity

S penalty_time= <*>
*

integer code for 20 sec periods


0= 0 sec
1= 20 sec
.
.
.
30= 620 sec
31= Temporary_offset ignored,
cell_reselect_offset is negative

S cell_bar_qualify= <*>
0 - Normal
1 - Low
EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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=

(P1= rxlev_acess_min dBm)


=

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

C2 Reselection Exercise

Issue 12 Rev 2

C2 Reselection Example

S SERVING CELL DATABASE PARAMETERS


CELL IDENTITY=
rxlev_access_min=
ms_txpwr_max_cch=
cell_reselect_param_ind=
cell_reselect_offset=
Temporary_offset=
Penalty_time=

234 10 255 038


20
5
1
3
3
5

S BEST NEIGHBOUR CELL DATABASE PARAMETERS


CELL IDENTITY=
rxlev_access_min=
ms_txpwr_max_cch=
cell_reselect_param_ind=
cell_reselect_offset=
Temporary_offset=
Penalty_time=

234 10 262 042


20
1
1
2
1
12

S Rxlev Average
Serving= -70 dBm
Best neighbour= -63 dBm
S cell_reselect_hysteresis= 2
S Mobile power class= 2 (8w [ 39 dBm)

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

327

Common Control Channel (CCCH) Configuration

Issue 12 Rev 2

Common Control Channel (CCCH) Configuration


Up to four timeslots on the BCCH carrier can be used for the CCCH. Each timeslot
forming a subchannel and each subchannel being divided into subgroups.
ccch_conf is a parameter which is broadcast on system information messages to an idle
mobile it is one of three parameters used by the MS, to determine its paging group
The ccch_conf field determines the configuration of the CCCH on the BCCH carrier. It
must be consistent with the sdcch_preferred value in order to correctly assign combined
or non-combined multiframes.

328

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Common Control Channel (CCCH) Configuration

Issue 12 Rev 2

Common Control Channel (CCCH) Configuration

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

329

Issue 12 Rev 2

Common Control Channel (CCCH) Block Configuration

Common Control Channel (CCCH) Block Configuration


On the non combined BCCH/CCCH multiframe, there are nine CCCH blocks. In the
downlink direction these blocks must serve the paging and access granted functions and
must be configured accordingly.
On the combined multiframe structure the number of blocks available is reduced to three
because it now supports four SDCCH/SACCH.
The bs_ag_blks_res field sets the number of blocks reserved for access grant per 51
TDMA multiframe. Therefore the number of paging blocks available are reduced by the
number of blocks reserved for access grant messages. The choice of value will be
determined by the consideration of the ratio of MS originated to MS terminated calls.
This parameter is broadcast on BCCH system information messages to an idle MS and is
used by the MS to determine its paging group.

330

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Common Control Channel (CCCH) Block Configuration

Issue 12 Rev 2

CCCH Block Configuration

S bs_ag_blks_res=<*>
*

Number of AGCH Blocks

(blocks reserved for ccch_conf= 1 0-2)


(blocks reserved for ccch_conf0 1 0-7)

Combined

CCCH Blocks

NO
NO
NO
NO
NO
NO
NO
NO
YES
YES
YES

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

MS Paging

Issue 12 Rev 2

Transmission of Paging Messages

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Periodic Updates/rr_t3212

Issue 12 Rev 2

Timers t3212

rr_t3212= <*>

* decihours
(valid range 0 to 255)
(default value 10)

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Attach/Detach

Issue 12 Rev 2

Attach/Detach

attach_detach = <*>

* 0 = disabled
1 = enabled

IMSI Detach Indication


Mobile
leaves
Network

BSS

MS

LAC = 126

BCCH System Info


MS

BSS

stored LAC
= 126

Mobile rejoins
network in the
same location
area

Mobile rejoins
network in a
different
location area

Attach/Detach enabled

MS

Location update IMSI


Attach type

stored LAC
= 126

LAC = 126

BSS
LAC = 126

LAC same as last known LAC


Location Update Normal

MS
stored LAC
= 126

BSS
LAC different to last known LAC

LAC = 172

SYS02_Ch3_19

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Cell Access

Issue 12 Rev 2

Cell Access

cell_bar_access_switch = <*>

* 0 = Cell is not barred


1 = Cell is barred

cell_bar_access_class = <*>

* 4 digit hexadecimal number


SYS02_Ch3_20a

Hexadecimal Digit
Value/Position
X

Classes Barred
15

12

10

13

11

14
6

Example 1: Access classes to


be barred 2 and 3
0

0
1

X
X

X
X

Example 2: Access classes to


be barred 8 and 10

X
X
X
X
SYS02_Ch3_20b

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

341

Issue 12 Rev 2

Emergency Call Access

Emergency Call Access


The cell_bar_access_class field in the database is mapped onto the cells BCCH
system information and informs all MS camped onto that cell which classes of MS are
permitted to access it. Part of the BCCH system information messages contains the
emergency_class_switch field informing the MS that either all MS are permitted to
make emergency call or only those belonging to MS classes 1115.

342

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Emergency Call Access

Issue 12 Rev 2

Emergency Call Access

emergency_class_switch=<*>

0= Emergency calls permitted


for all MS
1= Emergency calls permitted
for MS in classes 11-15

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

Responding to a paging message.

2.

Emergency call.

3.

User request (making a call, location update, etc.)

4.

Trying to salvage an established call.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

Sets timer T3122 for 20s


and returns to Idle mode

MS

Cell

Cell

wait_indication_parameters = <*>

* Time in seconds (0 255)


default = 5

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

chg_element rr_t3101 = <*>

* Time in milliseconds
Valid range 0 to 1000000
Default value 5000
SYS02_Ch3_24

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

349

Channel Allocation by Interference Band

Issue 12 Rev 2

Channel Allocation by Interference Band


The Cell Resource Manager (CRM) is the BSS radio channel database and is
responsible for allocating a radio channel of the right type when requested.
The CRM will search and allocate channels on a best channel available to worst channel
available basis.
All idle radio channels are monitored for noise interference by the Handover Detection
and Power Control (HDPC) process in the Radio Subsystem Software (RSS). This
monitoring leads to a number of samples which are in turn averaged by the HDPC. After
averaging, each idle channel will be allocated an interfere band, the HDPC then informs
the CRM of which band each idle channel falls into. The CRM uses this to ensure that
the best radio channel available is allocated first.
The five interference bands are based on absolute noise level values of each carrier at
five different Rx levels, interference band 0 being the lowest Rx level (therefore the better
channel) and interference band 4 being the highest Rx level and therefore the worst
channel.
The CRM will automatically allocate channels on a best to worst basis, this parameter
does not actually control this feature. This parameter is not supported.

350

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Channel Allocation by Interference Band

Issue 12 Rev 2

Channel Allocation by Interference Band

interfer_bands, 0 = <*>
interfer_bands, 1 = <*>
.
.
.
interfer_bands, 4 = <*>
*

Range 0 - 63

EMOTOROLA LTD. 2001

0 = -110 dBm
1 = -109 dBm
.
.
.
63 = -47 dBm

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

351

Channel Allocation by Interference Band

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Channel Allocation by Interference Band

Issue 12 Rev 2

Channel Allocation by Interference Band

Threshold <*> (default 7)


<*> Number of attempts
Valid Range 0 255

INFORMATION ELEMENT IDENTIFIER


CELL IDENTITY
EM
BIT

MTL NUMBER

RSL NUMBER
LSB

RSL NUMBER
MSB

RANDOM NUMBERS

SYS02_Ch3_26

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Assignment of Resources

Issue 12 Rev 2

Assignment of Resources

immediate_assign_mode= <*> (default 0)

0 - If SDCCH not available drop channel


request
1 - If SDCCH not available use TCH

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Queue Management

Issue 12 Rev 2

TCH Queueing
S

queue_management_information=<*>

0= Queuing not permitted


w1= Number of MS permitted to queue
(Default 50)

Half Rate/Full Rate TCH Queue


S

max_q_length_full_rate_channel= <*>

0= Queuing not permitted


w1= Number of MS permitted to queue
(Default 0)

SDCCH Queuing
S

max_q_length_sdcch= <*>

0 - 50

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

TDMA Frame on Initialisation

Timeslot 0 = FCCH + SCH + BCCH + CCCH + SDCCH/4 + SACCH/C4


Timeslot 1 = TCH/F + FACCH/F + SACCH/TF

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

TDMA Frame after Reconfiguration

Timeslot 0 = FCCH + SCH + BCCH + CCCH + SDCCH/4 + SACCH/C4


Timeslot 1 = SDCCH/8 + SACCH/C8
SYS02_Ch3_29

D
*

EMOTOROLA LTD. 2001

channel_reconfiguration_switch= <*>
0=
1=

Reconfiguration not permitted


Reconfiguration permitted

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

359

Issue 12 Rev 2

Preferred Number of SDCCH

Preferred Number of SDCCH


On initialisation the CRM is informed of the number_sdcchs_preferred field in the
database which will control the number of SDCCHs that will be configured in a particular
cell. The number of SDCCHs is dependent upon the configuration of timeslot 0 on the
BCCH carrier, whether it supports 4 SDCCHs or whether all SDCCHs are on their own
timeslot at 8 SDCCHs per timeslot.

360

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Preferred Number of SDCCH

Issue 12 Rev 2

Preferred Number of SDCCHs

S number_sdcchs_preferred= <*>

Number of SDCCHs
Combined Multiframe - 4,12,20,28...44
Noncombined Multiframe - 8,16,24...48

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

SDCCH Allocation

Issue 12 Rev 2

Maximum Number of SDCCHs

max_number_of_sdcchs= <*>

Number of SDCCHs
Combined multiframe - 4, 12,20,28 . . . .44
Noncombined multiframe - 8,16,24. . . .48

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

Conditions for TCH to SDCCH Reconfiguration to occur

1.

Number of SDCCHs after reconfiguration must not exceed max_number_of


sdcch.

2.

Idle number of free SDCCHs must be lower than sdcch_need_high_water_mark.

3.

Current number of idle TCHs must be greater than


tch_full_need_low_water_mark.

Conditions for SDCCH to TCH Reconfiguration to occur

1.

Total number of SDCCHs after the reconfiguration must not be lower than
number_sdcch_preferred.

2.

Present number of free SDCCHs must be greater than the


sdcch_need_low_water_mark.

A dependency written into this feature is:

1.

364

sdch_need_low_water_mark  number_sdcch_preferred by 9

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

S sdcch_need_high_water_mark=<*> (default 2) 1-39


S sdcch_need_low_water_mark=<*> (default 12) 10-48

Number of sdcchs free

S tch_full_need_low_water_mark=<*> (default 255) 0-255

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

365

Measurement Reporting for Handovers and Power Control

Issue 12 Rev 2

Measurement Reporting for Handovers and Power Control


Each cell in the PLMN will have its own dedicated BCCH. The BCCH will be
continuously transmitted at a constant power output and any idle timeslots on the BCCH
carrier will be filled with dummy bursts.
The MS is provided with a list of neighbour BCCH carriers to which it must retune for
signal strength measurement reporting.
Cellular systems depend upon the reusing of RF channels available to support the
maximum number of subscribers with the frequency band allocated. It is therefore very
important that the MS has some mean of determining that the BCCH carrier it is
measuring actually belongs to the cell intended and not another cell using the same
carrier frequency. The BCCH multiframe contains the SCH in which is contained the
BSIC. The MS therefore not only has to measure the received signal strength of BCCH
carriers but must also demodulate the SCH on the BCCH carriers and decode the BSIC
as often as possible and as a minimum at least once every 10 seconds.
If during the measurement process the MS detects BCCH carriers among the six
strongest, whose BCCHs are not currently being assessed but are on the neighbour list
the MS will then as a matter of priority attempt to decode their BSICs. If after a period of
5 seconds it has not managed to decode the BSICs it will revert to confirming existing
BSICs.
If the BSIC of a surrounding cell cannot be demodulated or indicates that the cell is part
of another PLMN then all signal strength measurements for that BCCH will be discarded.
If decoding of a BSIC is not achieved after three successive attempts it will be
considered lost and any existing signal signal strength measurement will be discarded.
The MS maintain a list of the six strongest BCCH carriers. If one of those BCCH carriers
is found to be no longer one of the six strongest the information collected on that BCCH
will be retained for at least 10 seconds. This is in case a handover is initiated to that cell
soon after reporting procedures on that cell have stopped but requiring timing and BSIC
information gathered on it.

366

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Measurement Reporting for Handovers and Power Control

Issue 12 Rev 2

Measurement Reporting

BCCH allocation

BSIC

IDLE FRAME

Received Signal Strength

Best six

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

BA Indication

Issue 12 Rev 2

BA Indication

ba_alloc_proc = <*>

* 0 = Reinitialization disabled
1 = Reinitialization enabled

1
octet 1

Neighbour Cells Description IEI


Bit
128

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

369

Issue 12 Rev 2

Signal Strength Measurements

Signal Strength Measurements


Radio link measurements are used in the handover and RF power control processes. An
RSS directed handover is defined as a change of channel either because of degradation
of quality of the current serving cell (BER and SSI) the availability of another channel that
will provide the same or better quality radio link using a lower transmit power output
(power budget) or to prevent an MS from exceeding the cells boundaries.
Both MS and RSS are reporting the signal strength at their receiver input. The MS is
measuring the signal strength in the channel downlink direction and that of neighbour
BCCH. The RSS is measuring the signal strength in the channel uplink direction.
The reported parameters are averaged out by the RSS and MS using measurement
samples taken during 480mS blocks. During the averaging process, samples taken
during a previous 480mS block are discarded, but the averages are retained by the RSS.
When assigned a TCH, SDCCH or camped on a BCCH the MS shall measure the signal
strength of:
1.

The BCCH carriers as indicated in the BCCH Allocation (BA).

2.

On all bursts of the TCH or SDCCH channel it is on including SACCH bursts. If


frequency hopping is supported using the BCCH carrier then measurement of that
carrier is dependent upon the PWRC field.

The RSS shall measure the signal strength of:


1.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Signal Strength Measurements

Issue 12 Rev 2

Signal Strength Measurements

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

371

Signal Quality Reporting RXQUAL

Issue 12 Rev 2

Signal Quality Reporting RXQUAL


The RSS measures the quality of the TCH/SDCCH in the uplink direction and the MS in
the downlink direction.
The RXQUAL values are produced during 480mS blocks and as with the signal strength
measurements, those measurements taken during previous 480mS blocks are discarded.
Eight levels of RXQUAL are defined.

372

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Signal Quality Reporting RXQUAL

Issue 12 Rev 2

Quality Measurements

MS
S Downlink SDCCH/TCH

Radio SubSystem (RSS)


S Uplink SDCCH/TCH
RXQUAL Range
BER

0=
1=
2=
3=
4=
5=
6=
7=

EMOTOROLA LTD. 2001

Less than 0.2%


0.2 - 0.4%
0.4 - 0.8%
0.8 - 1.6%
1.6 - 3.2%
3.2 - 6.4%
6.4 - 12.8%
Greater than 12.8%

ASSUMED BER

0.14%
0.28%
0.57%
1.13%
2.26%
4.53%
9.05%
18.1%

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

373

BSS Processing and Threshold Comparisons

Issue 12 Rev 2

BSS Processing and Threshold Comparisons


For the purpose of handovers and power control the BSS will be continuously processing
the following information.

Measurements
Reported by MS
on SACCH
1.

Downlink receive signal strength (RXLEV)

2.

Downlink quality (RXQUAL)

3.

Downlink surrounding cell RXLEV (neighbour BCCH)

1.

Uplink RXLEV

2.

Uplink RXQUAL

3.

MSBS Distance (Timing Advance)

4.

Interference levels in idle timeslots

Measurements
Performed by
RSS

The RSS will produce a new processed value for each of the measurements shown
above every 480mS (SACCH multiframe)

374

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

BSS Processing and Threshold Comparisons

Issue 12 Rev 2

BSS Processing and Threshold Comparisons

Reported by MS
S Downlink Received Signal Strength
S Downlink Quality
S Downlink Surrounding Cell RXLEV
Performed by RSS
S
S
S
S

Uplink Received Signal Strength


Uplink Quality
MS-BS Distance
Interference levels in idle timeslots

S Processed Value every 480mS

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

375

Threshold Comparison Process Power Control

Issue 12 Rev 2

Threshold Comparison Process Power Control


The MS and BSS are continuously providing Received Signal Strength Indications (RSSI)
on the radio resource allocated. The MS is measuring the RSSI in the downlink direction
which is proportional to the BSS transmit output power and the BSS is measuring the
RSSI in the uplink direction being proportional to the MS transmit output power.
These measurements are averaged by the RSS and this value is then used for power
control purposes. Thresholds are set in the database and if a number of averaged
values produced by the BSS exceed these thresholds then the power output of the BSS
or MS will be increased or decreased.
The number of averaged values to be considered in the decision process can be set in
database.

376

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Threshold Comparison Process Power Control

Issue 12 Rev 2

MS/BSS Power Control

Uplink/Downlink measurement taken

Averages produced

A number of the averages are compared


against threshold

Threshold exceeded

Power output adjusted

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Power Control

Issue 12 Rev 2

Power Control BSS

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Power Control

Issue 12 Rev 2

Power Control RXQUAL


Value

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=<*>
*

0-1810 steps of 0.01%

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

385

Issue 12 Rev 2

Handover RXQUAL, RXLEV

Handover RXQUAL, RXLEV


RXQUAL and RXLEV measurements are also used to support handovers. If an MS is
moving out of a cells coverage area then RXLEV and RXQUAL measurements will cause
the BSS and MS to increase their power output. This process will continue until the MS
reaches its maximum permitted output power and then a handover will be required.
The handover thresholds are set in the fields l_rxlev_ul_h, l_rxlev_dl_h, l_rxqual_ul_h
and l_rxqual_dl_h. The number of averaged values that must exceed there thresholds
are determined by a similar process to that used for power control.

386

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Handover RXQUAL, RXLEV

Issue 12 Rev 2

Handover RXLEV, RXQUAL


RXLEV

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

01810 steps of 0.01%

decision_1_n5=<*>
decision_1_p5=<*>
decision_1_n6=<*>
decision_1_p6=<*>
*131 Averages
n5, p5=

RXLEV

n6, p6=

RXQUAL

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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= <*>
*

0-63 (-110 to -47dBm)

decision_1_n7= <*>
decision_1_p7= <*>
*

EMOTOROLA LTD. 2001

0-31 Averages

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

Power Control Algorithms


At present two power control algorithms are available, the standard Motorola algorithm
and an alternate algorithm. The algorithm to be used for both uplink and downlink power
control must be specified by decision_alg_num
A number of fields control MS adaptive power:

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

max_tx_ms=<*>
*
5-39 (GSM 900) (odd values only)
*
0-30 (DCS 1800) (even values only)

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

391

Issue 12 Rev 2

BTS Power Control

BTS Power Control


Power control of the BTS is optional. If it is to be supported the
bts_power_control_allowed field must be enabled (set to 1). When enabled the BSS
may use up to 15 steps of power control levels with the same step sizes and tolerances
as defined for MS of power class 1.

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.

BTS MAXIMUM POWER


The max_tx_bts field determines the maximum output power for a base station
transmitter by setting the level at which the maximum power output available can be
attenuated. This parameter can be used to tailor the cell size. The BCCH output power
is equal to max_tx_bts.

392

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

BTS Power Control

Issue 12 Rev 2

BTS Power Control


S

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

6 steps of 2 dbs for MCellmicro, Horizonoffice,


McellAccess and Mcellarena

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

393

Issue 12 Rev 2

BTS Power Control

BTS Power Control


pow_inc_step_size_dl
Sets the step size for downlink power increases.

pow_red_step_size_dl
Sets the step size for downlink power decreases.

394

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

BTS Power Control

Issue 12 Rev 2

BTS Power Control

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

395

Issue 12 Rev 2

Rapid MS Power Down

Rapid MS Power Down


RF Problems can exist when a MS initially begins a call, transmitting a power level that is
too high in relation to the proximity of the BTS antenna system. These problems include
intermodulation and uplink interference to other carriers and cells especially in a
microcellular environment where distributed antennas and leaky feeders are frequently
employed.
The rapid power down feature can be employed to decrease the MS transmit power to an
acceptable perceived level, as seen by the BTS, this desired level will probably be
configured to be in the middle of the power box. This mechanism can be made to work
much faster than the normal power control algorithm and indeed is independent of the
usual pow_dec_step_size normally employed.
The rapid power down algorithm is quite simple and relies on a number of parameters set
in add_cell. The feature is triggered by the strength of the received power level as
perceived by the BTS. This power level, ul_rxlev, as measured by the BTS is an
average that is made up of a number of previously received reports. The number of
reports necessary and hence the speed of the initiation of this feature is controlled by
rpd_period. The RSS will perform rapid power down when the perceived power level
exceeds rpd_trigger. The formula simply calculates the necessary attenuation to
reduce the MSs output power to the desired perceived level. If the outcome of the
calculation is below the minimum (15) then the minimum value is used.
It should be remembered that an MS utilises 15 power control steps as ordered by the
BTS. Each step being 2 dB of attenuation from the maximum. Class two MSs can only
use a maximum of 2 (39 dBm) and class four MSs a maximum of 5 (33 dBm).
The worked example opposite should help with the understanding of this algorithm.

396

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Rapid MS Power Down

Issue 12 Rev 2

Rapid MS Power Down

-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 +

(UL_RXLEV - TRIGGER + OFFSET)


2

EXAMPLE
=2+

=2+

ORDERED POWER LEVEL

EMOTOROLA LTD. 2001

(-64 -(-68) + 12)


2
16
2
= 10 (23 dBm)

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

397

Issue 12 Rev 2

Rapid MS Power Down

Rapid MS Power Down


rapid_pwr_down
This parameter will enable/disable this feature. This feature will always be active, it is not
just for the initial setting up of the call. It will essentially work independently of normal
power control. After a power down instruction has resulted from this feature
ms_p_con_interval will be enforced, preventing any further action until expiry.
ms_p_con_interval, will however be overridden if the lower rxlev or rxqual thresholds
are exceeded, this will recover the ms from being in the situation where the ordered
power level is actually too low.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Rapid MS Power Down

Issue 12 Rev 2

Rapid MS Power Down

rpd_pwr_down = <*>
*

rpd_period = <*>
*

0 - 63 (-110 to -47 dBm)

rpd_offset = <*>
*

EMOTOROLA LTD. 2001

1 - 32 SACCH periods

rpd_trigger = <*>
*

0 - OFF
1 - ON

0 - 63 dBm

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

399

Issue 12 Rev 2

Optimized Power Control

Optimized Power Control


This feature gives the operator more flexibility in that the BSS can now administer unique
step sizes for MS (UL) and BTS (DL) power control. This is done by creating two
increment and two decrement step size elements for both uplink and downlink direction.
Further enhancements to this feature also allows the BSS to dynamically change the
increment and decrement step sizes based on current power levels and the proximity to
the defined upper and lower power thresholds.
The calculations are shown over page and use the database parameters shown
opposite.

3100

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Optimized Power Control

Issue 12 Rev 2

Optimized Power Control

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)

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3101

Optimized Power Control Algorithms

Issue 12 Rev 2

Optimized Power Control Algorithms


The algorithms used for the optimized power control feature, based on Power levels and
on Quality levels are shown opposite. These will only be used if the dyn_step_adj flag is
enabled.

3102

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Optimized Power Control Algorithms

Issue 12 Rev 2

Optimized Power Control


Dynamic power increase due to low level
DYN_POW_INCR_XX_L=
fhigh (l_rxlev_xx_p - av_rxlev_xx + pow_inc_step_size_xx)

Dynamic power increase due to high level


DYN_POW_RED_XX_L=
fhigh (av_rxlev_xx - u_rxlev_xx_p + pow_red_step_size_xx)

Dynamic power increase due to poor quality


DYN_POW_INCR_XX_Q=
max (pow_inc_step_size_xx, fhigh (l_rxlev_xx_p - av_rxlev_xx +
pow_inc_step_size_xx)

Dynamic power reduction due to good quality


DYN_POW_RED_XX_Q=
max (pow_red_step_size_xx, flow
(av_rxlev_xx - u_rxlev_xx_p))

dyn_step_adj_fmpr
10

where:
flow

fhigh

xx

EMOTOROLA LTD. 2001

an indication of the rounding down of a


value to the neatest multiple of 2dB.
an indication of the rounding up of a
value to the nearest multiple of 2dB.
UL/DL

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

MS will use DTX

3.

3104

MS may use DTX

MS will not use DTX

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Discontinuous Transmission

Issue 12 Rev 2

Discontinuous Transmission

dtx_required=<*>

0= DTX MAY BE USED


1= DTX WILL BE USED
2= DTX WILL NOT BE USED

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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.

EMOTOROLA LTD. 2001

Uplink quality

Power budget

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3109

Issue 12 Rev 2

SDCCH Access handovers

SDCCH Access handovers


An MS is allocated an SDCCH to carry out the call set up procedures including,
authentication, validation of equipment and subscriber, the setting of encryption and the
allocation of a TCH if required. An SDCCH is also used for SMS delivery and location
updating.
It is possible that an MS utilising an SDCCH slot may have the need to perform an interor intra-cell handover. This need will be calculated by the HDPC algorithms using
uplink calculations and SACCH reports in the normal way. SDCCH handovers are
permitted by the setting of the sdcch_ho flag. This handover though, will only occur if
the MS has occupied the SDCCH for at least the period set in sdcch_timer_ho.
External SDCCH handovers have to be enabled by the MSC, not all MSCs support this
feature.

3110

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

SDCCH Access handovers

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Handovers Interference

Issue 12 Rev 2

Handover Interference

interfer_ho_allowed= <*>
*

0=

disabled

1=

enabled

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

Serving RXLEV downlink (adapted)

3.

Neighbour RXLEV downlink

4.

MS maximum power allowed

5.

3114

Maximum uplink power permitted on serving and adjacent cells

Handover margin

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Handovers Interference

Issue 12 Rev 2

Power Budget Handover

S pwr_handover_allowed=<*>
*

0 - disabled
1 - enabled

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3115

Issue 12 Rev 2

Timing Advance MS Maximum Range

Timing Advance MS Maximum Range


The RSS is able to instruct the MS to advance its timing to compensate for the
propagation delay incurred on the uplink radio path. Even though the RF signal is
travelling at the speed of light the nature of the TDMA timing could make any delay
critical. The Training Sequence Code (TSC) position in the TDMA timeslot is constantly
monitored and the BSS software calculates by how much the MS timing needs to be
advanced to keep it centralised. The timing advance setting is then transmitted to the
MS on the downlink SACCH.
The interval between timing advance changes is determined by the
timing_advance_period field.

3116

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Timing Advance MS Maximum Range

Issue 12 Rev 2

Timing Advance MS Maximum Range

S timing_advance_period=<*>
*

EMOTOROLA LTD. 2001

0 = 0 SACCH multiframes
1 = 2 SACCH multiframes
.
.
.
.
.
.
31 = 62 SACCH multiframes

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3117

Issue 12 Rev 2

HandoverMS Maximum Range

HandoverMS Maximum Range


Before a handover can be initiated due to the MS approaching its maximum range the
ms_distance_allowed field must be set to 1 (enabled).
The maximum timing advance setting can compensate for a distance 34.892 km over 63
steps. The ms_max_range field can be set to any one of these 63 steps effectively
determining the cells radius. As it is the RSS calculating the timing advance, it will be
aware of the MS approaching its maximum range and if all or a proportion of timing
advance averaged values exceed the ms_max_range field a handover recognised
message will be generated.
ms_max_range is also used by the PRSM to reject (ignore) channel requests from
distant mobiles. This feature is invoked by enabling chg_element
poor_initial_assignment .
decision_1_n8 and decision_1_p8 are the voting parameters used to trigger a distance
handover.

3118

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

HandoverMS Maximum Range

Issue 12 Rev 2

Handover MS Maximum Range

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= <*>
*

EMOTOROLA LTD. 2001

0-31 Averages

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Handovers

Issue 12 Rev 2

Incoming Handovers

S en_incom_ho = <*>
*

0 - incoming handovers are inhibited


1 - incoming handovers are allowed
Default 1

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

Not performed by BSS. An intra_cell ho may still be performed but it


will be controlled by the MSC. The handover required message will be
sent to the MSC and may contain the server as a potential
candidate along with the other targets specified by RSS.

Performed by BSS if applicable. Only if RSS specifies the cause


value in the ho_recognised message as being one of qual or interfer,
then an intra_cell ho may be attempted. If the cause value is qual then
the intra_cell ho is only attempted when other targets are exhausted.
If the cause value is interfer then the intra_cell ho is attempted first
and only if that fails will the specified targets be tried.

Not permitted An intra_cell ho will not be performed by the BSS and


a handover required message will not be despatched to the MSC
in respect of this handover.

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

The control of internal inter-cell handovers is enabled in BSC.

The control of internal inter-cell handovers is disabled at the BSC.


These handovers will not be executed by the MSC either as the BSC
will not format the handover required message in repect of them.
External handovers will be executed in the normal way.

3122

The contol of internal inter-cell handovers is disabled at the BSC, all


internal handovers will be treated the same as external ones in that
a handover required message will be despatched to the MSC.

The execution of internal and external inter-cell handovers is disabled


at the BSC. These handovers will not be executed by the MSC either
as the BSC will not format the handover required message in repect
of them.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Handovers

Issue 12 Rev 2

Inter/Intra-cell Handovers

intra_cell_handover_allowed=<*>

0 - Not performed by BSS


1 - Performed by BSS if
applicable
2 - Not permitted

inter_cell_handover_allowed=<*>

0 - Not performed by BSS


1 - Performed by BSS if
applicable
2 - Internal disabled
External enabled
3 - Internal disabled
External disabled

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3123

Issue 12 Rev 2

TCH Resources Reporting

TCH Resources Reporting


The number of dedicated traffic channels in use within a BSS may be useful information
for the MSC to enable it for instance to balance the traffic between cells. The number of
TCHs currently allocated can be indicated to the MSC with a BSSMAP RESOURCE
INDICATION MESSAGE. The message can be sent in various cases controlled by the
MSC and solicited with BSSMAP RESOURCE REQUEST MESSAGE. One of these
cases is spontaneous mode which is the sending of information when certain conditions
are met. These conditions are set in database high and low watermark fields for full rate
channels.
When the number of available TCH rises to the high watermark values or falls to the low
watermark values the MSC will be informed if the resource request message has been
received from the MSC indicating spontaneous mode.

3124

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

TCH Resources Reporting

Issue 12 Rev 2

TCH Resource Reporting

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3125

Issue 12 Rev 2

Preferred Target Cell

Preferred Target Cell


A MS is continually monitoring the signal strength of neighbour BCCHs, generating
measurement reports and transmitting them to the BSS. The MS is able to monitor up to
32 BCCHs for handover purposes, the BSS has got to be able to detect when a
handover is required and then evaluate the measurement data provided by the MS to
provide a list of preferred cells that the MS should be handed over to.
The requirement for handover is detected by the Radio SubSystem associated with the
cell. The RSS is processing the measurements provided by the MS and when the
parameters are met for handover a handover recognised message is sent to the
Signalling Connection Control Part State Machine (SSM) at the BSC. Included as part of
the handover recognised message is a list (up to 32) of target cells that meet the
required criteria. The list of target cells is given in order of predicted best performance.
The list is evaluated by the BSC and it is determined whether an intra- or inter-BSS
handover is required. If an intra-BSS handover is required then it will be controlled by the
BSC, if the handover is to a cell in a different BSS then the MSC will control it.
In the case of an inter BSS handover a handover required message is transmitted from
the BSC to MSC. Contained in this message is a list of preferred cells, the number of
which being determined by the number_of_preferred_cells field.

3126

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Preferred Target Cell

Issue 12 Rev 2

Preferred Target Cells

Measurement
Reports

RSS
BTS

MS

SSM
BSC

Measurement
Reports

Handover Recognised

RSS
MS

List of Target Cells

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
*

max number of target cells contained in the


handover required" message.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Handover Reporting

Issue 12 Rev 2

Handover Reporting
HDPC

SSM
handover_recognized

handover_recognized_period
Range 2 to 64
SACCH Multiframes

[Handover decision processes


inhibited]

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3129

Issue 12 Rev 2

Handover Power Level

Handover Power Level


The power level the MS must use to access the target cell is included in the handover
command. This power level, along with other Layer 3 information regarding the new
channel such as channel type, frequency, slot etc will be provided by the target cell. The
power level to be used for all incoming handovers is the add_cell element
handover_power_level. This level is used for all inter_cell handovers, external and
internal.

3130

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Handover Power Level

Issue 12 Rev 2

Handover Power Level

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3131

Issue 12 Rev 2

Calculated Handover Power Level

Calculated Handover Power Level


Overview
When a mobile hands over into a new cell, its first transmission into the new cell is
transmitted at a certain level.
This level can be fixed by the handover_power_level parameter, but this level is often
fairly high, resulting in immediate power control activity to reduce the mobiles transmit
power.
Instead, the mobile can be instructed to use a calculated level that lies inside the power
control window right from the start. This facility is set up using the
use_derived_ho_power parameter and uses the following formula:
Handover power level= min (C+(AB), D, P)
where:

A=

max_tx_bts of the target cell

B=

rxlev_dl from the target cell

C=

u_rxlev_ul_p ) l_rxlev_ul_p
= centre of the target cells uplink power
2
window

D=

max_tx_ms of the target cell

P=

power class of the mobile

This facility is only supported for intra_BSS handovers.

3132

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Calculated Handover Power Level

Issue 12 Rev 2

Calculated Handover Power Level

use_derived_ho_power=<*>
*

0= use handover_power_level
1= use calculated handover level

handover level= min (C+(A-B), D, P)


where

A=

max_tx_bts of target cell

B=

rxlev_dl from target cell

C=

u_rxlev_ul_p ) l_rxlev_ul_p =
2
centre of target cell's uplink power
window

D=
P=

EMOTOROLA LTD. 2001

max_tx_ms of target cell


power class of mobile

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3133

Calculated Handover Power Level

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Calculated Handover Power Level

Issue 12 Rev 2

Handover Default Information

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=<*>
*

EMOTOROLA LTD. 2001

0= -110 dBm
1= -109 dBm
2= -108 dBm
.
.
63= -47 dBm

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3137

Handover Channel Establishment

Issue 12 Rev 2

Handover Channel Establishment


An MS that has just handed over to a new traffic channel sends a number of handover
access messages to provide the RSS with the RF characteristics necessary to calculate
timing advance. The RSS having calculated the timing advance and power control sends
this information in the form of a physical information message to the MS.
When sending the physical information message timer rr_t3105 is started. If rr_t3105
expires before correct response from the MS has been received rr_t3105 is reset and
the physical information message is repeated. This process is repeated a number of
times until either the MS correctly responds or the maximum number of repetitions (NY1)
is reached.
If the maximum number of repetitions is reached the newly allocated channels are
released and the handover abandoned.

3138

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Handover Channel Establishment

Issue 12 Rev 2

Handover Channel Establishment


MS

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

S rr_t3105 = < * >


*

0 to 200 (in 20 ms steps)


Default 60

S rr_ny1_rep = < * >


*

EMOTOROLA LTD. 2001

number of repetitions
0 to 200
Default 20
SYS02 GSR5/AGSR: BSS Database

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

3139

Issue 12 Rev 2

RSS Link Fail

RSS Link Fail


If an MS, established on a radio resource, is lost for whatever reason the RSS must have
a means of detecting its loss. If not then the resources that had been allocated would
continue to support an MS that is no longer there and would not be made available for
other MS.
To maximise the efficient use of resources the RSS is able to monitor the receipt of
SACCH from the MS. If SACCH is not received for a database determined period of time
then the MS is assumed to be lost and the allocated resources are then made available
for other MS.
The link_fail parameter sets the maximum value of a counter(s). If the RSS is unable to
decode a SACCH message S is decreased by one. If the RSS successfully decodes a
SACCH message S is increased by two. In either case S should be equal to or more
than the value set in the radio_link_timeout field.

3140

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

RSS Link Fail

Issue 12 Rev 2

RSS Uplink Failure Detection

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

SYS02_Ch3_49

3141

Issue 12 Rev 2

RSS Link Fail

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

RSS Link Fail

Issue 12 Rev 2

Radio Link Revival

S full_power_rfloss=<*>
*

0= disabled
1= enabled

S link_about_to_fail= <*>
*

EMOTOROLA LTD. 2001

0 = 0 SACCH MULTIFRAMES
1 = 4 SACCH MULTIFRAMES
.
.
.
15 = 60 SACCH MULTIFRAMES

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3143

Issue 12 Rev 2

Loss of Radio Link

Loss of Radio Link


The criteria for radio link failure by an MS is based on the radio link counter(S). If the MS
is unable to decode a SACCH message S is decreased by 1. In the case of a successful
reception S is increased by 2.
The maximum value of S is set in the radio_link_timeout field. If S reaches 0 then
radio link failure is assumed and the MS will abort the radio resource connection.
The radio_link_timeout parameter is transmitted on the BCCH of each cell and is used
by the MS to set T100, it is applicable once the MS is on a SDCCH or TCH.
In the example opposite the field has been set to 0. (4 SACCH messages).

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Loss of Radio Link

Issue 12 Rev 2

Radio Link Timeout

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

Waits for rr_t3109


to expire before
terminating resources

BCCH

T100
exceeded

MS
Return to idle

T>t
SYS02_Ch3_51

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3147

Issue 12 Rev 2

Timers rr_t3109, rr_ t3111

Timers rr_t3109, rr_ t3111


Normal Channel
Release
The system initiates the release of a channel by sending a channel release message to
the MS and will start an internal timer rr_t3109, coincidentally SACCH messages are
deactivated. On receipt of the channel release, the MS will start an internal timer (t3110)
and disconnect the main signalling link by sending a Layer 2 disconnect frame. When
t3110 times out or when the signalling is disconnect confirmed on receipt of a layer 2
numbered acknowledgement, the MS deactivates all RF links and returns to BCCH idle
mode.
On the system side, when the Layer 2 disc is received the BSS will stop rr_t3109 and
start rr_t3111. When rr_t3111 has expired all RF links are terminated and are then free
to be allocated to other MS. The purpose of rr_t3111 is to allow time for the disconnect
frame to be acknowledged with a Unnumbered Acknowledgement (UA) frame and to
protect the channel in case the acknowledge frame is lost. Additionally, as rr_t3111 runs
for a shorter time than rr_t3109, the channel is able to be reassigned far quicker.
If rr_t3109 times out all RF channels will be deactivated and are then free to be allocated
to other MSs. The value of rr_t3109 should always be greater than t3110 so that there is
a high probability of normal termination.
N.B. The value of rr_t3111 must be set to a value equal to the value of rr_t3110.

3148

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Timers rr_t3109, rr_ t3111

Issue 12 Rev 2

Normal Channel Release


t3110

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

S rr_t3109 = < * >


(valid range 0 to 1000000)
default value (14400)
* milliseconds
S rr_t3111 = < * >
(valid range 0 to 1000000)
default value 1500
* milliseconds
rr_t3111 = rr_t3110
EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

CRM Timers

Issue 12 Rev 2

CRM Timers

rf_chanl_rel_ack = <*>

RSS

CRM

RRSM

RF Channel Release

RF channel release ack

RF channel release ack received


If timer is allowed to expire
channel will be marked as free
* milliseconds
Valid range 0 to 1000000
Default value 5000ms
SYS02_Ch3_53

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Call Re-establishment

Issue 12 Rev 2

Call Re-establishment

S
*

reestablish_allowed= <*>
0= reestablishment allowed
1= reestablishment not allowed

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

CRM Timers

Issue 12 Rev 2

CRM Timers
dealloc_inact = <*>

RSS

CRM

RRSM

Error Indication (cause GSM 08.58)

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

internal handover assignment ack


If Timer expires channel will
be marked as free
* milliseconds
Valid range 0 to 1000000
Default value 5000

EMOTOROLA LTD. 2001

SYS02_Ch3_55

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

3155

Issue 12 Rev 2

Cell Exercise

Cell Exercise
Adding a Cell
1.
2.

The two cells use the EGSM frequency band.

3.

If resources requested by an MS are not available, then it must, on receipt of an


immediate assignment reject message wait 3 seconds on cell 1 and 10 seconds
on cell 2 before reattempting.

4.

No form of queuing is permitted on either cell.

5.

Channel reconfiguration is permitted.

6.

The preferred number of SDCCHs is 8 for both cells

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.

Normal paging is in operation and there will be an interval of approximately one


second between transmission of paging messages to MSs of the same group.

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.

Access to either cell is not restricted in anyway.

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.

DTX will not be used on cell 1 and may be used on cell 2.

18.

Attach/detach is not supported on either cell.

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.

If an MS receives no response to a channel request message it may repeat the


request up to five times on both cells.

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

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

EMOTOROLA LTD. 2001

Cell Exercise

Issue 12 Rev 2

23.

Periodic updates are not supported on either cell.

24.

If on request an SDCCH is not available then the channel request is to be dropped.

25.

If an MS is required to handover into both of these cells, it should send handover


access bursts at a power level of 43 dBm.

26.

If the MS is unable to decode a SACCH message for approximately 12 seconds


then it will assume radio link failure and abort the radio resource connection.

27.

Call re-establishment is allowed on cell 1 and not allowed on cell 2.

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.

The maximum number of target cells to be specified in a handover required


message will be 6 for both cell 1 and 2.

33.

After a handover_recognised message has been generated the handover trigger


mechanism will be inhibited for approximately 4 seconds.

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.

The thresholds for BSS power control are


90 dBm and 75 dBm for cell 1 and
104 dBm and 95 dBm for cell 2.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

Handovers due to power budget are not allowed.

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.

Handovers due to RXLEV, RXQUAL, interference and timing advance allowed.

51.

Cell 1 should have a maximum timing advance of 50 and cell 2, 40.

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.

The BCC for cell 1 is 2 (decimal) and for cell 2 is 3 (decimal).

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.

If the neighbour list is changed dynamically from the OMC, subsequent


measurement reports using the old BA list shall still be processed by the HDPC in
the normal way for both cells.

59.

A mobile shall be allowed to handover whilst in dedicated mode on an SDCCH, but


only after it has been on the sdcch for 3 seconds on cell 1 and 2 seconds on cell 2.

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.

Both cell 1 and 2 shall be considered normal priority cells.

62.

The cell reselect offset for cell 2 should be 4dB.

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

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

EMOTOROLA LTD. 2001

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

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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 =

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Chapter 4

Device/Function Equipage

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Issue 12 Rev 2

ii

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Chapter 4
Device/Function Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device/Function Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

41
41

Device and Function Dependency In-Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

42

Device and Function Dependency M-Cell/Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

44

Kilo-Port Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

46

KSW Extension/Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

48

KSW Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

410
410

Generic Clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

414

Base Site Processor (BSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

416

Code Storage Facility Processor (CSFP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

418

Base Transceiver Processor (BTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Digital Host Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

420
420

Generic Processor Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


GPROC Function Preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

422
422

Equipage of GPROC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Base Transceiver Function (BTF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

424
424

Link Control Function (LCF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Operations and Maintenance Function (OMF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

426
426

Digital Radio Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

428

Digital Radio Interface In-Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

430

Digital Radio Interface M-Cell/Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Redundancy Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RTF Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Antenna Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use of Tuneable Combiner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Combiner Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Combiner Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cavity Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diversity Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
fm cell type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

436
436
438
438
438
440
440
440
440
440
440

Typical Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

442

Remote Tuneable Combiner (RTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

444

Multiport Serial Interface (MSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


In-Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M-Cell/Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

446
446
448

Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

450

Path Equipage Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

452

16 KBIT/S RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

454

RTF Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

456

Receive Transmit Function (RTF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

458

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

iii

Issue 12 Rev 2

Radio Signalling Link (RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Optional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Transfer Link (MTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

466

Operations and Maintenance Link (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

468

Cell Broadcast Link (CBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

470

Equipage Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iv

464
464

472
472

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Device/Function Equipage

Issue 12 Rev 2

Device/Function Equipage
Objectives
On completion of this chapter the student will be able to:
S

State and understand the dependency of one device on another device/function.

Understand and implement the MMI involved with the equipping of


device/functions.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

41

Device and Function Dependency In-Cell

Issue 12 Rev 2

Device and Function Dependency In-Cell


Some devices/functions are dependent upon other devices having already been
equipped to support them. For example, before a Receive Transmit Function (RTF) can
be equipped a Digital Radio Interface Extended Memory (DRIM) must be equipped to
support it. The chart opposite shows the device and equipment hierarchy for non M-Cell
systems

42

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Device and Function Dependency In-Cell

Issue 12 Rev 2

Device and Function Dependency In-Cell

BSS SITE (BSC)

CAB

BTS SITE

CELL

COMB KSW GCLK

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

NOTE: * indicates an automatically equipped device

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

43

Device and Function Dependency M-Cell/Horizon

Issue 12 Rev 2

Device and Function Dependency M-Cell/Horizon


As with In-Cell sites a logical order exists with respect to equipping devices and functions
in the CM. It is logical for example that an NIU be equipped before a path statement, as
the path statement will nominate certain NIUs for its traffic route. The chart opposite
shows the dependency chart in respect of M-Cell/Horizon systems.

44

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Device and Function Dependency M-Cell/Horizon

Issue 12 Rev 2

Device and Function Dependency M-Cell/Horizon

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

1st prompt (highway)


This prompt specifies which highway is being managed by this KSW/TSW. Highway
number 0 is conventionally used first. The system will not display this prompt for
Horizonoffice BTS. Will automatically set this to 0 for Horizonoffice BTS.

2nd prompt (identifier)


This figure specifies the unique first identifier of this KSW/TSW. If set to 0 the board
must be fitted in card slot L27, if set to 1 the board should be fitted in card slot L1.

3rd prompt (cage)


This figure specifies the cage where the KSW has been fitted. The system will
automatically set this to 15 for Horizonoffice BTS. This prompt will not be displayed for
Horizonoffice BTS.

4th prompt (DRIMs)


The highway can be optionally configured to serve DRIM cards by the use of this flag, if
yes is entered then 352 highway timeslots are reserved for DRIM card service. The
system will set this value to no for Horizonoffice BTS. The system will not display this
prompt for Horizonoffice BTS. This prompt will not appear for RXCDR sites.

46

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Kilo-Port Switch

Issue 12 Rev 2

KSW Equipage

equip (site number) KSW

S enter portion of TDM highway managed: 0-3


S enter the TDM identifier: 0 or 1
S enter the cage number: BSS
BSC
RXCDR
BTS

0-13
0-13
0/1
15-2

S DRIM's allowed on highway managed by this KSW: yes/no

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

KSW Extension/Expansion

Issue 12 Rev 2

KSWX Configuration diagram showing extension and


expansion for 2 KSWs

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

Extension cabinets 210


Sys02_4_4

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

KSW Configuration

Issue 12 Rev 2

KSW Configuration

chg_ksw_config <SITE No><KSW Pair> <H/W0><H/W1><H/W2><H/W3>

EXAMPLE

SITE KSW Pair H/W 0

H/W 1

H/W 2

H/W 3

chg_ksw_config

chg_ksw_config

chg_ksw_config

chg_ksw_config

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

413

Issue 12 Rev 2

Generic Clock (GCLK)

Generic Clock (GCLK)


GCLKs are equipped on a site basis and its functionality can be extended to other cages
via clock extender boards. One GCLK must be equipped per site and two if redundancy
is to be implemented. This device may not be explicitly equipped at M-Cell sites, it is
automatically equipped with the first BTP. The command to equip an In-Cell GCLK is as
follows:
equip <site number> GCLK

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.

CLKX prompts (In-cell sites only)


The three CLKX prompts are used to indicate whether GCLK extension is used at this
site, and if so which CLKXs support it. This is important, as slots U5, U6 and U7 can
support either CLKX or KSWX cards, and if the same slot is specified for two cards then
the CM must reject the equipage.

414

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Generic Clock (GCLK)

Issue 12 Rev 2

GCLK Equipage

equip (site number) GCLK:


S enter the device identification for the GCLK: 0/1
S enter the cage number: 0-15
S Is CLKX 0 (slot U7) present?: Yes or No
S Is CLKX 1 (slot U6) present?: Yes or No
S Is CLKX 2 (slot U5) present?: Yes or No

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

415

Issue 12 Rev 2

Base Site Processor (BSP)

Base Site Processor (BSP)


The BSP is the master processor type at a BSC and also at a RXCDR. Its functionality
is dependant upon the BSC type, at the smallest BSC it will carry out all processing
required, then as the BSS grows in functionality certain software entities migrate away
from BSP and use other processor types which must be created. To equip a BSP the
following command must be used:
equip (site number) BSP

1st prompt (identifier)


This prompt gives the BSP its unique identifier, a maximum of two BSPs can be
equipped at any one site, the second being redundant.

2nd prompt (cage)


This identifies the cage in which the BSP is to be equipped.

3rd prompt (slot)


Valid card slots are 20/24 for a BSU cage and 25/26 for an RXU cage.

4th prompt (MTLs)


This field allows the FM to load MTLs onto the specified BSP. At a BSC or BSS
(fm_site_type 0 or 1), when the bsc_type=1 this prompt will not appear, the MTP
software in these cases will appear in multiple instances on LCFs. At a BSC or BSS
where the bsc_type=0 then this prompt will appear and must be answered with a one. At
an RXCDR, (fm_site_type=3), this prompt will not appear, after all a RXCDR will never
process an MTL.

416

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Base Site Processor (BSP)

Issue 12 Rev 2

Base Site Processor Equipage

equip <0 or bsc>BSP

S enter the BSP identifier:

0/1

S enter the cage number:

0/1

S enter the slot number:

20/24 (BSC)
25/26 (RXCDR)

S enter the maximum MTLs this BSP may manage: 0/1


(only for fm_site_type 0 or 1 when bsc_type= 0)

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

417

Code Storage Facility Processor (CSFP)

Issue 12 Rev 2

Code Storage Facility Processor (CSFP)


The Code Storage Facility Processor (CSFP) is a GPROC device which facilitates the
propagating of new software instances with reduced system downtime. A software
instance is a complete set of software and firmware objects including the database
object.
New software loads can be downloaded from OMC to BSC and consequently BSC to
BTS, without a CSFP this download will result in system downtime whilst the BSC or
BTS is in ROM utilising the IP. This system downtime is dependent on link throughput
(number of OMLs) and system topology (number and connection of BTSs). If used, the
CSFP will reduce this system down time as the download can take place to the BSC or
BTS whilst the system is on-line and call processing.
After the software has been downloaded to all entities in the BSS a special BSS reset is
performed for the activation of the new software instance. Since the new software
instance exists locally, network outage time is drastically reduced.
The CSFP feature also provides optional CSFP fallback. As previously described a new
software instance is distributed to all CSFPs in a BSS. After the reset, all non-CSFP
GPROCs begin executing the new software load, while the fallback CSFP retains the old
software load.
At M-Cell sites, this device cannot be explicitly equipped. It is automatically equipped with
the first BTP.
To equip a CSFP the following command must be used:
equip (site number) CSFP

1st prompt (identification)


This parameter identifies the CSFP within site 0 only. At sites 150 the prompt will not
appear.

2nd prompt (cage)


This field identifies the cage in which the GPROC acting as the CSFP has been fitted.

3rd prompt (slot)


This field identifies the cage slot position in which the GPROC acting as the CSFP has
been fitted.

418

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Code Storage Facility Processor (CSFP)

Issue 12 Rev 2

CSFP Equipage

equip (site number) CSFP

S Enter the CSFP identifier:


(only prompted at site 0)
S Enter the cage number:
BSC
BSS
RXCDR
BTS
S Enter the slot number:

EMOTOROLA LTD. 2001

0/1

0-13
0-13
0/1
15-2
18-25 (BSU)
25-26 (RXU)

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

419

Issue 12 Rev 2

Base Transceiver Processor (BTP)

Base Transceiver Processor (BTP)


The BTP is the master processor at a BTS. Its load and functionality is dependant upon
the BTS type, at the smallest BTS it will carry out all the processing required. As more
processing power is required at a site software entities will appear in multiple instances
on other designated processors. To equip a BTP the following command must be used:
equip <site number> BTP

1st prompt (identifier/card frame)


This prompt gives the BTP its unique identifier, a maximum of two BTPs can be equipped
at any one site, the second being redundant. In M-Cell products this prompt identifies the
card frame in which the MCU is being equipped. In the case of M-Cell this prompt must
be answered 0 first in the CM. 0 is the valid entry for M-Cellmicro.

2nd prompt (cage)


This identifies the cage in which the BSP is to be equipped. Not prompted for M-Cell
products.

3rd prompt (slot)


Valid slot ranges are 20/24 for cage 15 and 20 for cage 14. Not prompted for M-Cell
products.

4th prompt (DRIMs)


This prompt specifies the maximum number of DRIMs that the CA will allow the BTP to
support. Not prompted for M-Cell products.

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

1st prompt (cage)


This prompt acts as the 1st identifier for the DHP and defines the cage where the DHP is
fitted. The system will automatically set this value to 15 for Horizonoffice BTS.

2nd prompt (identifier)


This prompt gives the DHP its unique identifier in the specified cage.

3rd prompt (slot)


Valid slot ranges are 1825.

4th prompt (DRIMs)


This prompt specifies the maximum number of DRIMs that the CA will allow the DHP to
support.
420

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Base Transceiver Processor (BTP)

Issue 12 Rev 2

Base Transceiver Processor (BTP)


equip <site number> BTP
S enter the BTP identifier:

0/1 (InCell)
0/1 (card frame, MCell/Horizon)

S enter the cage number:

15/14

S enter the slot number:

20/24 (cage 15)


20 (cage 14)

S enter the maximum DRIMs supported by this BTP:


0-6

Digital Host Processor (DHP)

equip <site number> DHP


S enter the cage number for this DHP: 0 - 15
S enter the unique DHP number in the cage: 0 - 7
S enter the slot number: 18 - 25
S enter the maximum number of DRIMs supported by this DHP: 1 - 6

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

421

Issue 12 Rev 2

Generic Processor Equipage

Generic Processor Equipage


Depending on the site type, certain software processes and functions will have to be
created to support the site functionality. When a function such as an LCF, OMF or BTF
is to be equipped then a GPROC platform must be equipped in advance to support it. In
the case of a processor such as a BSP or BTP the GPROC platform does not have to be
previously equipped, see the dependency table at the beginning of this section. This
device cannot be equipped at an M-Cell site.
To equip a GPROC the following command must be entered:

equip (site number) GPROC


1st prompt (identifier)
This prompt specifies the unique identifier of the GPROC.

2nd prompt (cage)


This figure specifies the cage where the GPROC has been fitted. Automatically set to
15 for Horizonoffice BTS. This prompt will not appear for Horizonoffice BTS.

3rd prompt (slot)


This figure denotes the card slot location of the GPROC being equipped.

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

Intra Function 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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Generic Processor Equipage

Issue 12 Rev 2

GPROC Equipage

equip (site number) GPROC


S enter the GPROC identifier: 1-111
S enter the cage number:
BSS
BSC
RXCDR
BTS

0-13
0-13
0-1
15-2

S enter the slot number:


BSS
BSC
BTS
RXCDR

18-25
18-25
18-25
25-26

chg_element

EMOTOROLA LTD. 2001

pool_gproc_preemption
0 = disable (no preemption)
1 = Function priority preemption
2 = Function and intrafunction
preemption

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

423

Issue 12 Rev 2

Equipage of GPROC Functions

Equipage of GPROC Functions


Base Transceiver
Function (BTF)
The main processor type at a BSC is the BSP and at a BTS is a BTP. As both processor
types are responsible for the main control of a site there is a lot of common functionality
between them.
If a site consists of standalone BSS then there is no requirements for both a BSP and
BTP. A BSS consists of a colocated BSC and BTS. One major difference at a BSC is
that the KSW is dynamic and requires its own software process called the Switch
Manager to control it. The Switch Manager must run on a BSP which will be the main
processor type at a standalone BSS.
However, what the BSP does not have is any RF functionality which is required at a BTS.
A function is created called the BTF which will run on a equipped GPROC at a colocated
BSS.
To equip a BTF the following command must be used:
equip bsc BTF

prompt 1 (DRIMs)
This prompt specifies the maximum number of DRIMs that the CA will allow the BTF to
support.

424

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Equipage of GPROC Functions

Issue 12 Rev 2

BTF Equipage

equip (0 or bsc) BTF


S Enter the maximum number of DRIMs supported by this BTF: 1-6

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

425

Issue 12 Rev 2

Link Control Function (LCF)

Link Control Function (LCF)


The BSC has interface signalling information to and from the MSC and BTS sites. LCFs
can only be equipped at BSC site type 1 or 2.
LCPs are assigned the LCF which is equipped in the database. As with the BTF it is not
necessary to specify a particular GPROC to be assigned the LCF. A GPROC has to be
equipped at the site and functionality is distributed on initialisation. To equip an LCF the
following command must be used:
equip (Specify a DRI in a network from the OMC-R Navigation Tree).
unequip (Delete a DRI from a network at the OMC-R Navigation Tree).

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Link Control Function (LCF)

Issue 12 Rev 2

LCF Equipage

equip (0 or bsc) LCF

S enter the function identifier for the LCF: 0-24


S enter the number of MTLs the LCF can manage: 0-2
NB, 2 is only valid for GPROC2
S enter the number of Cell Broadcast Links (CBLs) the LCF can manage: 0/1

OMF Equipage

equip (0 or bsc) OMF


(No prompts.)

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

427

Issue 12 Rev 2

Digital Radio Interface

Digital Radio Interface


In-Cell and M-Cell system hardware differs at the Digital Radio Interface. In-Cell systems
utilises the DRIM, DRIX and DRCU/SCU combination, whereas M-Cell utilises the
Tranceiver Control Unit (TCU) and possibly the FOX and FMUX. This difference is
reflected in the equip dri command.
The DRIM provides the interface between the digital and RF domains. It performs the
following function:
1.
2.

Interleaving/deinterleaving

3.

channel coding/decoding

4.

Base band hopping

5.

Encryption function

6.

428

Logical to physical channel mapping.

Supports control/signalling between processor and DRCU

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Digital Radio Interface

Issue 12 Rev 2

Digital Radio Interface

S Logical to physical channel mapping


S Interleaving/deinterleaving
S Channel coding/decoding
S Base band hopping
S Encryption
S Interfaces control/signalling

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

429

Issue 12 Rev 2

Digital Radio Interface In-Cell

Digital Radio Interface In-Cell


Redundancy Group
Current software provides RTF\DRIM redundancy, in order for this feature to function
correctly DRIMs belonging to the same cell (connected to the same antenna) are
grouped together using this first identifier called the redundancy group. If an RTF is
functioning on a DRIM\DRCU that goes faulty, it will automatically move to a
DRIM\DRCU that is redundant (if present), this move will only take place if the first
identifier (redundancy group) of the faulty DRIM\DRCU is the same as the
spare\redundant DRIM\DRCU. This first identifier is also matched by that of the RTF. If
it is the BCCH RTF that is functioning on a DRIM\DRCU that goes faulty, this RTF will
move to a DRIM\DRCU in the same redundancy group (unless the cell has only one
carrier) replacing a non-BCCH RTF if necessary. The second identifier uniquely identifies
the DRIM within its redundancy group.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Digital Radio Interface In-Cell

Issue 12 Rev 2

DRIM Equipage
S equip (site number) DRI
Enter the 1st and 2nd DRI id:

(0-5) (0-11)

Enter the cabinet identifier:

0-15

Enter the DRI board type:

DRIM (or integer code 0)

Enter the cage number:

BSC 0 - 13
BTS 15 - 2

Enter the slot number:

(7, 9, 11, 13, 15, 17)

Enter the TRU identifier:

0-6

Typical Arrangement

D
R
C
U

D
R
C
U

D
R
C
U

EMOTOROLA LTD. 2001

D
R
C
U

D
R
C
U

D
R
C
U

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Sys02_4_5a

431

Issue 12 Rev 2

Digital Radio Interface In-Cell

Digital Radio Interface In-Cell


RTF Identifier
An RTF contains the frequency information for a particular cell and is equipped as a
function after the DRIM. This first part of the identifier determines which group of RTFs
that the DRIM must use to obtain its frequency information. A DRIM 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 DRIMs.

This prompt is optional and a value should only be added if equipment sharing (future
feature) is implemented.

432

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Digital Radio Interface In-Cell

Issue 12 Rev 2

DRIM Equipage

S enter the 1st and 2nd RTF id: (0-5) (0-11)

NOTE:
S Non equipment sharing R TFs assigned on initialisation
S Equipment sharing R TFs must be specified

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

433

Issue 12 Rev 2

Digital Radio Interface In-Cell

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Digital Radio Interface In-Cell

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

S Enter the diversity flag for this DRI:


0-Diversity disabled
1-Diversity enabled
S Does this DRI use tuneable combining: Yes/No
S Enter the tuneable combining type: (0, 1 or 2)
S Enter the COMB identifier: (0-13)
S Enter the cavity number for this COMB: (0-5)
S Enter the fm_cell_type:
0-Nondiversity mode
4-Full diversity

R CU
DR CU
DR CU

EMOTOROLA LTD. 2001

Diversity flag
0
0
1

fm_cell_type
0
0 (non diversity)
4 (full diversity)

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

435

Digital Radio Interface M-Cell/Horizon

Issue 12 Rev 2

Digital Radio Interface M-Cell/Horizon


Redundancy
Group
Within an MCell/Horizon set up the DRM is actually a TCU.
Current software provides RTF/TCU redundancy, in order for this feature to function
correctly TCUs belonging to the same cell (connected to the same antenna) are grouped
together using this first identifier called the redundancy group. If an RTF is functioning
on a TCU that goes faulty, it will automatically move to a TCU that is redundant (if
present), this move will only take place if the first identifier (redundancy group) of the
faulty TCU is the same as the spare\redundant TCU. This first identifier is also matched
by that of the RTF. If it is the BCCH RTF that is functioning on a TCU that goes faulty,
this RTF will move to a TCU in the same redundancy group (unless the cell has only one
carrier) replacing a non-BCCH RTF if necessary. The second identifier uniquely identifies
the TCU within its redundancy group.

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 / FMUX connection


The response to this and the next prompt will specify the method of connection to the
MCU. A number of alternatives exist for this field. The first, fox indicates that the TCU
is connected via one of the fox ports in the master card frame (the one supporting the
MCU). Three further alternatives exist to describe the fmux to fmux connection in the
case of a remoted cage. The fmux specified being the one in the master cage, this
directly correlates to the shelf map numbering. The last alternative is direct, this
indicates that the TCU is connected to one of the ports on the MCU front panel. Text
strings or integer codes can be entered in response to this prompt. In the case of an
M-Cellmicro, M-Cellcity, M-Cellarena this prompt should be answered with direct or 4.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Digital Radio Interface M-Cell/Horizon

Issue 12 Rev 2

TCU Equipage
S

equip (site number) DRI

Enter the 1st and 2nd DRI id: (0-5) (0-11)

Enter the cabinet identifier: 0-15


Note: if using PCS 1900/GSM850 with Horizonmacro/Ext ensure tx_pwer_cap = 1

Enter the type of connection to the BTP:


0 or fox
1 or fmux0
2 or fmux1
3 or fmux2
4 or direct

Enter the port to which the TCU is connected: 0-5


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

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

437

Digital Radio Interface M-Cell/Horizon

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Digital Radio Interface M-Cell/Horizon

Issue 12 Rev 2

TCU Equipage

S Enter the 1st and 2nd RTF id: (0-5) (0-11)


S Enter the GSM cell id where the DRI appears: Cell id/cell name
S Enter the antenna select number of this cell: 1-3

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

Antenna Select Number


Sys02_4_7

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

439

Digital Radio Interface M-Cell/Horizon

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Digital Radio Interface M-Cell/Horizon

Issue 12 Rev 2

TCU Equipage

S Enter comb 1st & 2nd ID;

0-13

S Enter cavity number:

0-5

S Does this DRI use tuneable combining: Yes/No


S Enter the tuneable combining type: (0, 1 or 2)
S Enter the COMB identifier: (0-13)
S Enter the cavity number for this COMB: (0-5)
S Enter the diversity flag for this DRI:
0-Diversity disabled
1-Diversity enabled
S Enter the fm_cell_type: (0-4)
0-Nondiversity mode
1-3 Not currently supported
4-Full diversity

R CU
DR CU
DR CU

EMOTOROLA LTD. 2001

Diversity flag
0
0
1

fm_cell_type
0
0 (non diversity)
4 (full diversity)

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

441

Issue 12 Rev 2

Typical Examples

Typical Examples

In-cell with RTC


equip 12 dri
01
0
drim
15
9
<CR>
<CR>
2 3 4 1 0 368 39
1
yes
2
0
1
0
0

In-cell without RTC


i
id
cab
type
cage
slot
TRU
RTF
Cell
Ant
use RTC
RTC (controlled)
comb
cav
diversity disabled
cell type

M-cell6 with CCB


(standalone 6 carrier omni)
equip 12 dri
01
0
fox
1
<CR>
2 3 4 1 0 368 39
1
yes
1
1
1
0
4

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

M-cell2 (without CCB)


(standalone 2 carrier omni)
equip 12 dri
01
0
4
1
<CR>
2 3 4 1 0 368 39
1
no
0
<CR>
<CR>
0
4

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

id
cab
FOX/FMUX
port
RTF
cell
ant
no comb
none
comb
cav
diversity disabled
cell type

EMOTOROLA LTD. 2001

Typical Examples

Issue 12 Rev 2

Typical DRI Examples


InCell
With RTC:

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

MCell with CCB


(standalone 6 carrier)

MCell without CCB


(standalone 2carrier)

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

443

Remote Tuneable Combiner (RTC)

Issue 12 Rev 2

Remote Tuneable Combiner (RTC)


From GSR 5, the DRI-Combiner heirarchy is modified to simplify the equipage of both
DRI devices and combiners. Previously, the RTC had to be equipped before the DRI; this
is no longer the case and now the DRI device may be equipped first. Also whereas
previously the equipage of a single combiner created 2 logical combiner devices, now the
equipage of the combiner creates a single device which may be controlled by 2 DRI
devices, a first and second controlling DRI.
The combiner parameters Combiner address, DRI combining type and cavity may also
be modified after equipage by the use of the modify_value command.
Note that a combiner may be connected to up to 6 RCU/TCU/CTU devices, but only max
2 of them can be in a controlling mode.
The Combiner is equipped by the following commands:
equip<site number>COMB
prompt 1 (identifier)
This first prompt uniquely identifies the TCB within the site. Range is 0 - 13.
prompt 2 (address)
This field provides the TCB address, which must be equal to the hardware address
straps on the TCB itself. Essentially all TCBs at the same site could have the same
address, the only use for this address is when one TCU is controlling two TCBs, this may
be the case in equipment sharing (a future feature).
Note: As a result of the upgrade to GSR 5, the relationship of the RTC to a controlling
DRIM is now contained in the equip_0_dri command and the logical structure of RTCs
to DRIs has been simplified so that one only RTC will exist per equipage.

444

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Remote Tuneable Combiner (RTC)

Issue 12 Rev 2

COMB Equipage

equip (site number) COMB

enter first COMBiner identifier:

0-13

enter COMBiner address:

0-255

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

445

Issue 12 Rev 2

Multiport Serial Interface (MSI)

Multiport Serial Interface (MSI)


The equip command associated with an MSI can equip a number of 2Mb termination
modules namely the MSI, XCDR, MSI2 and the NIU. Both the MSI and NIU modules are
capable of terminating 2 x 2Mb links, where as a XCDR performs the GSM TRAU
function and can only terminate one E1 2Mb link. The MSI2 module is capable of
terminating either two E1 links or two T1 links. It can also be configured to terminate one
E1 (span A) and one T1 (span B), with E1 to T1 conversion within the module itself, this
will be necessary in T1 systems as the XCDR module is exclusively E1. The MSI card is
only capable of terminating two E1 links, whereas the NIU is capable of terminating two
E1 links or two T1 links. chg_element land_layer1_mode is the database command
which will enable either a T1 or E1 network to function, it is written on a BSS basis, ie all
termination modules within the network will terminate in the same L1 mode.
The prompts associated with the equip MSI command are dependant upon the type of
site, M-Cell or In-Cell.

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.

Protocol type MMS 0


This prompt only appears if the integrated M-Cell HDSL feature is enabled and the
msi_type is niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.

Timslots supported on MMS 0


This prompt only appears is the integrated M-Cell HDSL feature is enabled and the
msi_type is niu_hdsl, niu_ext_hdsl or msi_ext_hdsl and the protocol type is HDSL.

446

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Multiport Serial Interface (MSI)

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)

S Enter the cage number:

0-15

S Enter the slot number:

BSS, BSC, BTSs: 6-17


RXCDR: MSI type 0: 6-10
MSI type 1: 6-24

S Enter the MSI type:

0 - MSI
1 - XCDR
2 - GDP
7 - msi_ext_hdsl
12 - RF_unit
(Horizonoffice only)
255 - msi2_conv

S Enter MMS 0 protocol type: E1 or HDSL


S Enter number of timeslots
supported on MMS 0:
16 or 32
S Enter MMS 1 protocol type: E1 or HDSL
S Enter number of timeslots
supported on MMS1:
16 or 32
EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

447

Issue 12 Rev 2

Multiport Serial Interface (MSI)

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.

Protocol type MMS 0


This field only appears if the integrated M-Cell HDSL feature is enabled and the msi_type
is niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.

Timeslots supported on MMS 0


This prompt only appears is the integrated M-Cell HDSL feature is enabled and the
msi_type is niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.

Modem setting on MMS 0


This prompt only appears if the integrated M-Cell HDSL feature is enabled and the
msi_type is niu_hdsl.

Protocol type MMS 1


This field only appears if the integrated M-Cell HDSL feature is enabled and the msi_type
is niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.

Timslots supported on MMS 1


This prompt only appears is the integrated M-Cell HDSL feature is enabled and the
msi_type is niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.

Modem setting on MMS 1


This prompt only appears if the integrated M-Cell HDSL feature is enabled and the
msi_type is niu_hdsl.

448

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Multiport Serial Interface (MSI)

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

S Enter the MCU card frame in


which the NIU exists: 0-1
S Enter the NIU slot number:
S Enter the MSI type:

NIU
9=
3=
8=
9=

0-1
niu_ext_hdsl
niu
niu_hdsl
niu_ext_hdsl

MCell2
MCell6
MCellcity
MCellarena

S Enter MMS 0 protocol type:

E1 or HDSL

S Enter number of timeslots


supported on MMS 0:

16 or 32

S Enter MMS 0 modem setting:

Master or slave

S Enter MMS 1 protocol type:

E1 or HDSL

S Enter number of timeslots


supported on MMS 1:

16 or 32

S Enter MMS 1 modem setting:

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

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

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

Prompt 1 (Terminating site ID)


This is the ID of the BTS site terminating the path.

Prompt 2 (Unique Path ID)


Each BTS site can have upto 10 unique paths, conventionally, numbering of paths start
at 0.

Prompt 3 (BSC MSI ID)


This is the ID of the terminating MSI card and MMS port at the BSC.

Prompt 4 (Site ID)


This is the identity of the next BTS site in the chain.
If the aggregate A-bis feature is enabled the system will accept ts_switch as the site Id.
If is ts_switch is used, the system will not prompt for upstream MSI, upstream MMS,
downstream MSI and downstream MMS identifiers.

Prompt 5 (Upstream MSI ID)


This is the identity of the MSI card and MMS port at the first BTS in the chain, facing
upstream towards the BSC.

Prompt 6 (Downstream MSI ID)


This is the identity of the MSI card and MMS port at the first BTS in the chain, facing
downstream towards the terminating site.
A path can proceed through a number of BTS sites before reaching its terminating BTS.
To that end, the last three parameters are repeated for each intermediate site.

450

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Path

Issue 12 Rev 2

Path Equipage

equip <0 or bsc> Path

S enter the terminating SITE ID: 1-100


S enter the unique PATH ID: 0-9
S enter the BSC MSI ID: 0-55, 0 or 1
S enter the SITE ID: 1-100 or ts_switch
S enter the upstream MSI ID:

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)

S enter the downstream MSI ID:

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

451

Issue 12 Rev 2

Path Equipage Exercise

Path Equipage Exercise


The diagram opposite contains the information necessary to equip 2 paths to BTS site
16. Use the working area below to equip both paths, path 0 should be made the
shortest.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Path Equipage Exercise

Issue 12 Rev 2

Path Equipage Exercise

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

16 KBIT/S RSL

Issue 12 Rev 2

Fully equipped RTF

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

16 kbit/s subchannel used for 16 kbit/s RSL


16 kbit/s subchannel available for voice traffic
Sys02_4_10a

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

455

Issue 12 Rev 2

RTF Types

RTF Types

Type

Options

1
2

A fully equipped BCCH R TF with no associated 16 kbit/s R SL.

A fully equipped non-BCCH R TF with an associated 16 kbit/s R SL.

A fully equipped non-BCCH R TF with no associated 16 kbit/s R SL.

A subequipped BCCH R TF with an associated 16 kbit/s R SL.

A subequipped BCCH R TF with no associated 16 kbit/s R SL.

A subequipped nonBCCH R TF with an associated 16 kbit/s R SL.

456

A fully equipped BCCH R TF with an associated 16 kbit/s R SL.

A subequipped nonBCCH R TF with no associated 16 kbit/s R SL.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

16 kbit/s subchannel used for 16 kbit/s RSL


16 kbit/s subchannel available for voice traffic
Sys02_4_10

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

457

Issue 12 Rev 2

Receive Transmit Function (RTF)

Receive Transmit Function (RTF)


A RTF is assigned to a DRIM/TCU, by the CA, providing it with the necessary RF
channel information.

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.

First and second identifier


An RTF is assigned to one of 6 redundancy groups (1st id). A BTS site is able to support
six cells (each cell having its own allocated DRIMs and RTFs). An RTF is automatically
assigned to a DRIM of the same redundancy group. This second identifier is used to
identify a particular RTF within a redundancy group.

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.

Optional prompts for 16 kbit RSL


Should the site employ a 16 kbit/s RSL, additional prompts will appear. 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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Receive Transmit Function (RTF)

Issue 12 Rev 2

RTF Equipage
equip (site number) RTF

S enter capacity of carrier: FULL or SUB


S enter type of carrier: bcch or non_bcch
S enter the 1st and 2nd RTF Id: (0-5)(0-11)
(0-23)(0-3) Horizonoffice
S enter the primary unique PATH Id: 0-9
S enter the 2nd identifier for the associated RSL
S enter the optional secondary unique PATH Id: 0-9

Only prompted for


site equipped with
16 kbit/s RSL

S enter the optional 2nd identifier for the associated


RSL

S enter the GSM cell to which this carrier is assigned:


cell id/cell name
S enter carrier absolute radio frequency channel:
1-124 - PGSM/EGSM
0,975-1023 NON BCCH EGSN
512-885 DCS 1800
512-810 PCS 1900
128-251 GSM 850

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

459

Receive Transmit Function (RTF)

Issue 12 Rev 2

Frequency Hopping Indicator (FHI)


This field is required for frequency hopping MS allocation per slot, Hopping Sequence
Number (HSN) and hopping mode form a frequency hopping system. It is then possible
to allocate a frequency hopping system on a carrier and timeslot basis. Each frequency
hopping system is allocated a Frequency Hopping Indicator (FHI). It is then possible
when equipping an RTF to allocate an FHI to each of the eight timeslots. All 8 FHIs are
entered on a single line with one space separating each value. A value of 03 indicates
the defined slot will hop using the specified hopping system. A value of 255 indicates that
the slot will not hop. A value of 255 must be entered in the case of M-Cellmicro sites. The
default for this prompt is 255, but a restriction exists in that either no entry is made or all
8 entries are made, nothing in between.

Training Sequence Code (TSC)


The TSC is a fixed pattern of 26 bits that forms the centre part of both normal and
dummy bursts. It supports a number of functions:
1.

Used for timing advance calculations

2.

Used as a channel identifier

3.

Used for equalisation purposes

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Receive Transmit Function (RTF)

Issue 12 Rev 2

RTF Equipage

S enter the 8 carrier FHIs: 0-3


255

S enter the 8 carrier TSCs: 0-7

S enter the KSW pair that manages this carrier: 0-3

S enter cell zone: 0 or 1

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

461

Receive Transmit Function (RTF)

Issue 12 Rev 2

TRX transmit power reduction


This parameter is only prompted for non-BCCH carriers when concentric cells feature is
enabled and the cell_zone=1. This element is only used by the BSS if the inner zone
algorithm is set to power_based.

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.

SDCCH placement priority


This prompt is used to specify the priority of a carrier in configuring SDCCHs. The
prompt only appears if sdcch_load is greater than zero.

Channel allocation priority


This prompt specifies the priority of a carrier when utilising the radio channel
(SDCCH/TCH) allocation algorithm.The radio channel timeslot is allocated primarily on
interfer band. If two timeslots have the same interfer band, then the timeslot will be
allocated based on its channel allocation priority.

462

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Receive Transmit Function (RTF)

Issue 12 Rev 2

RTF Equipage

S enter trx power reduction: GSM900


0 - 43 dBm
(must be greater than or
.
equal to max_tx_bts_ if
.
the inner_zone_alg=1)
.
21 - 1 dBm
This parameter is only
prompted if cell_zone=1

S enter the number of


extended range timeslots
allowed:

DCS1800
0 - 39 dBm
.
.
.
21 - 3dBm
0 - 4 (Default 0)

S enter sdcch load: 0-2


S enter sdcch placement priority: 0-250
0 - highest
250 - lowest
S enter channel allocation priority: 0-250
0 - highest
250 - lowest

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

463

Issue 12 Rev 2

Radio Signalling Link (RSL)

Radio Signalling Link (RSL)


The RSL is the LAPD 64 kbps timeslot between the BTS and BSC to support BSCBTS
signalling.

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Radio Signalling Link (RSL)

Issue 12 Rev 2

RSL Equipage

S equip (BSC or 0) RSL:

S Enter the 1st device ID for the RSL: 1-100 (Site)

S Enter the 2nd device ID for the RSL:0-7 - IN-CELL


05 MCELL 2/6, Horizon
S Enter the unique path ID: 0-9

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

465

Issue 12 Rev 2

Message Transfer Link (MTL)

Message Transfer Link (MTL)


The MTL is the 64 kbps PCM timeslot that is used to convey C7 Signalling information
between MSC and BSC. It cannot be equipped at an RXCDR site.

1st prompt (identifier)


Identifies a specific MTL associated with a site.

2nd prompt (MSI)


Specifies the first identifiers of the MSI/XCDR to which the MTL is associated.

3rd prompt (PORT)


Specifies the second identifier of MMS to which the MTL is associated ie the MSI/XCDR
port.

4th prompt (timeslot)


Specifies which of the thirty two 64 kbps is to be assigned the MTL, conventionally
timeslot 16 is always used.

466

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Message Transfer Link (MTL)

Issue 12 Rev 2

MTL Equipage

equip (site number) MTL

S Enter the device ID for the MTL: 0-15

S Enter the first MMS description for this MTL: 0-55 (MSI)

S Enter the second MMS description for this MTL: 0-1 (port)

S Enter timeslot on MMS where this MTL appears: 1-31

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

467

Issue 12 Rev 2

Operations and Maintenance Link (OML)

Operations and Maintenance Link (OML)


The OML is the X.25 64 kbps timeslot between the BSC and OMC to support the remote
Operation and Maintenance function of the OMC. It cannot be equipped on an HDSL
Link.

1st prompt (identifier)


Identifies a particular OML.

2nd prompt (MSI/XCDR)


Identifies the MSI/XCDR board supporting the OML. For initialisation purposes the OML
is defaulted to timeslot 1 of a port associated with an MSI in slot 16 or 14 of cage 0 or 16
in cage 1.

3rd prompt (port)


Identifies a particular port on a XCDR/MSI board.

4th prompt (timeslot)


Identifies the 64 kbps timeslot to which the OML has been allocated.

468

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Operations and Maintenance Link (OML)

Issue 12 Rev 2

OML Equipage

equip (site number) OML

S Enter the device ID for the OML: 0-3

S Enter the first MMS description for this OML: 0-55 (BSC)
0-71 (RXCDR)

S Enter the second MMS description for this OML: 0-1

S Enter timeslot on MMS where this device appears: 1-31 (E1)


1-24 (T1)

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

469

Issue 12 Rev 2

Cell Broadcast Link (CBL)

Cell Broadcast Link (CBL)


This bi-directional data link, the CBL, will allow communications between the BSS and
the Cell Broadcast Centre (CBC). The link will activate an underlying connection with an
X.25 network and establish a switch virtual circuit with the CBC. The CBC is responsible
for downloading cell broadcast messages to the BSC, together with an indication of the
repetition rate and the number of broadcasts per message. The BSC will in turn interpret
these messages and transmit each request to the appropriate BTSs.
The CBL feature is purchasable and will only support a single 64 kbs, non-redundant link
using LAPB as the Layer 2 protocol. DTE addresses need to be configured via MMI in
order for the X.121 connection to be made. In addition to the X.121 address, operator
names must also be specified. These are included in t he N-connect message used to
establish the SVC and must be consistent at both ends. The device will reside upon the
the LCF for both type 1 and type 2 BSC sites. The link is not supported at a bsc type 0.
The CBL can be connected directly from the X.25 network into the BSC via a 2MB link
Alternatively it may be connected via a 64kbs cross connect in the RXCDR.
The database command and prompts necessary to configure a CBL are as follows:
equip 0/bsc CBL

1st prompt (identifier)


Identifies the CBL, allows one of ID 0.

2nd prompt (MSI/XCDR)


Identifies the MSI/XCDR board supporting the CBL.

3rd prompt (port)


Identifies the MSI/XCDR port.

4th prompt (timeslot)


Identifies the 64kbs timeslot the CBL has been allocated.

5th prompt (BSS operator)


This field specifies the BSS operators name. This field must be entered between double
quotes.

6th prompt (CBC operator)


This field specifies the CBC operators name. This field must be entered between double
quotes.

470

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Cell Broadcast Link (CBL)

Issue 12 Rev 2

Cell Broadcast Link

CBC

X.25

BSC

CBC

X.25

RXCDR

BSC

Sys02_4_11

equip 0/bsc CBL


S

enter the device ID for the CBL: 0

enter the first MMS identifier for this device: 0-55

enter the second MMS identifier for this device: 0/1

enter the timeslot on MMS where this device appears:

enter the BSS operator= 20 characters"

enter the CBC operator= 20 characters"

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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.

This BTS site supports 2 cells and is a BTS site type 1.

2.

There are two paths equipped to the site 0 and 1, 0 being the primary path for all
traffic and signalling.

3.

The RSL used is full 64 kbit/s

4.

No hopping is performed at the site.

5.

All equipment identities follow convention.

6.

The following information is necessary when equipping an RSL


LapD T200 timer= 2500
N200 timer= 3
k value=7

472

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

Cell ID: 234 01 10724 54


Radios in diversity mode
BCC = 3
All TSCs = timeslot 0
BCH carrier

D
R
C
U

Cell ID: 234 01 10724 54


Radios in diversity mode
BCC = 3
All TSCs timeslot 0
BCH carrier

Site 12
SYS02_Ch4_12

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

473

Issue 12 Rev 2

Equipage Exercise

474

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

GPROC 2
GPROC 1

XCDR 1 MSI 1
DRI(M) 4 XCDR 2 MSI 2

DRI(M) 3XCDR 4 MSI 4


XCDR 5 MSI 5

DRI(M) 1 XCDR 8 MSI 8

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

DRI(M) 0 XCDR 10 MSI 10

PIX0 or BBBX

DR1

L8

XCDR 9 MSI 9

PIX1 or BBBX

DR2

XCDR 7 MSI 7

PIX2 or BBBX

MS2

DRI(M) 2 XCDR 6 MSI 6

LANX A

DR3

XCDR 3 MSI 3

LANX A

DR4

DRI(M) 5XCDR 0 MSI 0

EXP KSWX A0

MS1

Key = CARD NOT FITTED

SYS02 GSR5/AGSR: BSS Database

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

EMOTOROLA LTD. 2001

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

equip _ _ _ _ DRI
____
____
____
____
____
____
____
____
____
____
____
____

equip _ _ _ _ DRI
____
____
____
____
____
____
____
____
____
____
____
____

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

477

Issue 12 Rev 2

equip _ _ _ _ DRI
____
____
____
____
____
____
____
____
____
____
____
____

equip _ _ _ _ RTF
____
____
____
____
____
____
____
____
____

equip _ _ _ _ RTF
____
____
____
____
____
____
____
____
____

478

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

equip _ _ _ _ RTF
____
____
____
____
____
____
____
____
____

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

479

Issue 12 Rev 2

480

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Appendix A
GSM Channel Frequency Table

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Appendix B
Hexadecimal/Decimal Conversion Chart

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Appendix C
SACCH Multiframes

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Ci

Issue 12 Rev 2

Several parameters in the BSS database are configured in multiples of SACCH


multiframes. This Appendix provides the user with conversion between SACCH
multiframes and seconds for ones better understanding.
Note: SACCHs may be associated with either traffic channels (TCH) or stand-alone
dedicated control channels (SDCCHs). So the user must decide if the SDCCH he is
considering is associated with either TCHs or SDCCHs. When a SACCH is associated
with SDCCH, the SACCH multiframe has a repeat length of 102 TDMA frames; when a
SACCH is associated with TCH, the SACCH multiframe has a repeat length of 104
TDMA frames.

SA assoc, with SDCCHSA assoc, with TCH


#mf
seconds
#mf
seconds
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

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Appendix D
Database Script Building Charts

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Di

Issue 12 Rev 2

BSC

EQUIP SITE

EQUIP CABINET

EQUIP CAGE
CHANGE ELEMENT
(SITE CONFIGURATION)

EQUIP DEVICES

CHANGE ELEMENT (TIMERS)

ADD CIRCUITS

KSW CONFIGURATION

App Dii

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

RXCDR

EQUIP RXCDR

EQUIP ABSS

EQUIP CABINET

EQUIP CAGE

EQUIP DEVICES
(DIGITAL BOARDS AND FUNCTIONS)

NAIL CONTROL LINKS

EQUIP CICs (CIRCUITS)

CHANGE ELEMENT
(SITE CONFIG/TIMERS)
SYS02_AppD_01

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Diii

Issue 12 Rev 2

BSS

EQUIP BSS

EQUIP AXCDR

EQUIP CABINET

EQUIP CAGE

CHANGE ELEMENT
(SITE CONFIGURATION)

EQUIP DEVICES (DIGITAL BOARDS)

EQUIP DEVICES (FUNCTIONS)

ADD CIRCUITS

CHANGE ELEMENT (TIMERS)

KSW CONFIGURATION
SYS02_AppD_02

App Div

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

BTS

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Dv

Issue 12 Rev 2

EQUIP SITE

EQUIP CABINET

EQUIP CAGE

CHANGE ELEMENT
(SITE CONFIG/TIMERS)

ADD CELL

EQUIP DEVICES

CHANGE ELEMENT (TIMERS)

KSW CONFIGURATION

H/O PARAMETERS

App Dvi

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

PATH

EQUIP PATH

EQUIP RSL

EQUIP RTF

ADD NEIGHBOUR

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Dvii

Issue 12 Rev 2

App Dviii

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Appendix E
add_cell Command Prompts

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Ei

Issue 12 Rev 2

Table 4-1 add_cell command prompts


Prompt

Input

Enter the Frequency Type:

freq_type=x

Range
1 (pgsm)
2 (egsm)
4 (dcs1800)
8 (pcs1900)

Default
None

Use numeric values


or text string.
Enter BSS identity code:

bsic=x

0 to 63

None

Enter wait indication parameters:

wait_indication_parameters=x

0 to 255

Enter common control channel


configuration:

ccch_conf=x

0, 1, 2, 4, 6

Enter blocks reserved for access grant:

bs_ag_blks_res=x

0 to 7

Enter multiframes between transmissions of


paging messages:

bs_pa_mfrms=x

0 to 7

Enter extended paging active:

extended_paging_active=x

0 or 1

Enter number of SDCCHs preferred:

number_sdcchs_preferred=x

0 to 44
(if ccch_conf=1)
8 to 48
(if ccch_conf1)

Enter enable incoming handover:

en_incom_ho=x

0 or 1

Enter intra cell handover allowed:

intra_cell_handover_allowed=x

0 to 2

Enter inter cell handover allowed:

inter_cell_handover_allowed=x

0 to 3

Enter number of preferred cells:

number_of_preferred_cells=x

1 to 16

16

Enter handover margin default:

ho_margin_def=x

63 to 63

Enter handover recognized period:

handover_recognized_period=x

2 to 64

Enter uplink rxqual handover allowed:

ul_rxqual_ho_allowed=x

0 or 1

Enter downlink rxqual handover allowed:

dl_rxqual_ho_allowed=x

0 or 1

Enter uplink rxlev handover allowed

ul_rxlev_ho_allowed=x

0 or 1

Enter downlink rxlev handover allowed:

dl_rxlev_ho_allowed=x

0 or 1

Enter alternate flag for SDCCH handover:

sdcch_ho=x

0 or 1

Enter alternate SDCCH handover timer


value:

sdcch_timer_ho=x

1 to 31

Enter interference handover allowed:

interfer_ho_allowed=x

0 or 1

Enter power handover allowed:

pwr_handover_allowed=x

0 or 1

Enter MS distance allowed:

ms_distance_allowed=x

0 or 1

Enter alternate flag for MS power control


processing

mspwr_alg=x

0 or 1

Enter handover power level:

handover_power_level=x

2 to 19

None

App Eii

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Table 4-1 add_cell command prompts


Prompt

Input

Enter power control indicator for hopping


through BCCH:

pwrc=x

Range
0 or 1

Default
1
. . . continued

Enter interference measurement averaging


period (intave):

intave=x

1 to 31

Enter timing advance period:

timing_advance_period

1 to 31

Enter MS power control period:

ms_p_con_interval=x

0 to 31

Enter MS timeout for MS power control:

ms_p_con_ack=x

0 to 31

Enter MS power control allowed:

ms_power_control_allowed=x

0 or 1

Enter BTS power control interval:

bts_p_con_interval=x

0 to 31

Enter BTS timeout for BTS power control:

bts_p_con_ack=x

0 to 31

Enter BTS power control allowed:

bts_power_control_allowed=x

0 or 1
(0 for M-Cellmicro)

Enter power increment step size:

pow_inc_step_size=x

2 to 4, 6 EVEN

Enter power reduction step size:

pow_red_step_size=x

2 to 4 EVEN

Enter maximum BTS transmit power:

max_tx_bts=x

0 to 21
(0 to 6 for
M-Cellmicro)

Enter maximum transmit MS:

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

Enter MS transmit power maximum default:

ms_txpwr_max_def=x

5 to 39 (GSM900)
0 to 30 (DCS1800
and PCS1900)
See Note, above

39
30

Enter decision algorithm number:

decision_alg_num=x

0 to 31

Enter decision alg 1 dl rxlev avg h:

decision_1_dl_rxlev_av_h=x

0 to 3

Enter decision alg 1 dl rxlev avg ih:

decision_1_dl_rxlev_av_ih=x

0 to 3

Enter decision alg 1 dl rxlev avg p:

decision_1_dl_rxlev_av_p=x

0 to 3

Enter decision alg 1 dl rxqual avg h:

decision_1_dl_rxqual_av_h=x

0 to 3

Enter decision alg 1 dl rxqual avg p:

decision_1_dl_rxqual_av_p=x

0 to 3

Enter decision alg 1 n1:

decision_1_n1=x

1 to 31

Enter decision alg 1 n2:

decision_1_n2=x

1 to 31

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Eiii

Issue 12 Rev 2

Table 4-1 add_cell command prompts


Prompt

Input

Range

Default

Enter decision alg 1 n3:

decision_1_n3=x

1 to 31

Enter decision alg 1 n4:

decision_1_n4=x

1 to 31

Enter decision alg 1 n5:

decision_1_n5=x

1 to 31

Enter RSS decision alg 1 n6:

decision_1_n6=x

1 to 31

1
. . . continued

Enter RSS decision alg 1 n7:

decision_1_n7=x

1 to 31

Enter RSS decision alg 1 n8:

decision_1_n8=x

1 to 31

Enter decision alg 1 ncell rxlev avg h calc:

decision_1_ncell_rxlev_av_h_
calc=x

0 to 3

Enter decision alg 1 p1:

decision_1_p1=x

1 to 31

Enter decision alg 1 p2:

decision_1_p2=x

1 to 31

Enter decision alg 1 p3:

decision_1_p3=x

1 to 31

Enter decision alg 1 p4:

decision_1_p4=x

1 to 31

Enter decision alg 1 p5:

decision_1_p5=x

1 to 31

Enter decision alg 1 p6:

decision_1_p6=x

1 to 31

Enter decision alg 1 p7:

decision_1_p7=x

1 to 31

Enter decision alg 1 p8:

decision_1_p8=x

1 to 31

Enter decision alg 1 power budget rxlev:

decision_1_p_bgt_rxlev_av_h=x

0 to 3

Enter decision alg 1 timing advance alg:

decision_1_tim_adv_av_alg=x

0 to 3

Enter decision alg 1 ul rxlev avg h:

decision_1_ul_rxlev_av_h=x

0 to 3

Enter decision alg 1 ul rxlev avg ih:

decision_1_ul_rxlev_av_ih=x

0 to 3

Enter decision alg 1 ul rxlev avg p:

decision_1_ul_rxlev_av_p=x

0 to 3

Enter decision alg 1 ul rxqual avg h:

decision_1_ul_rxqual_av_h=x

0 to 3

Enter decision alg 1 ul rxqual avg p:

decision_1_ul_rxqual_av_p=x

0 to 3

Enter quality band processing allowed:

alt_qual_proc=x

0 or 1

Enter power control threshold l_rxqual_ul_p: l_rxqual_ul_p=x

If alt_qual_proc = 0,
0 to 1810
If alt_qual_proc = 1,
0 to 7

226 BER
or
4 QBand

Enter power control threshold l_rxqual_dl_p: l_rxqual_dl_p=x

If alt_qual_proc = 0,
0 to 1810
If alt_qual_proc = 1,
0 to 7

226 BER
or
4 QBand

Enter power control threshold


u_rxqual_ul_p:

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Table 4-1 add_cell command prompts


Prompt

Input

Range

Default

Enter power control threshold


u_rxqual_dl_p:

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

Enter handover threshold l_rxqual_ul_h:

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

Enter handover threshold l_rxqual_dl_h:

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

Enter handover threshold l_rxlev_ul_h:

l_rxlev_ul_h=x

0 to 63

None

Enter handover threshold l_rxlev_dl_h:

l_rxlev_dl_h=x

0 to 63

None

Enter handover threshold u_rxlev_ul_ih:

u_rxlev_ul_ih=x

0 to 63

None

Enter handover threshold u_rxlev_dl_ih:

u_rxlev_dl_ih=x

0 to 63

None

Enter handover threshold mobile max


range:

ms_max_range=x

0 to 63

None

Enter power control threshold l_rxlev_ul_p:

l_rxlev_ul_p=x

0 to 63

None

Enter power control threshold l_rxlev_dl_p:

l_rxlev_dl_p=x

0 to 63

None

Enter power control threshold u_rxlev_ul_p:

u_rxlev_ul_p=x

0 to 63

None

Enter power control threshold u_rxlev_dl_p:

u_rxlev_dl_p=x

0 to 63

None

Enter alternate flag for neighbor cell


process:

ncell_proc=x

0 or 1

None

Enter alternate flag for missing report:

missing_rpt=x

0 or 1

None

Enter alternate flag for BA allocating


process:

ba_alloc_proc=x

0 or 1

None

Enter RSS link fail:

link_fail=x

0 to 15

Enter link about to fail:

link_about_to_fail=x

0 to 15

Enter alternate flag for full power RF loss:

full_pwr_rfloss=x

0 or 1

Enter cell bar access switch:

cell_bar_access_switch=x

0 or 1

Enter cell bar access class:

cell_bar_access_class=x

0 to
ffff(hexadecimal)

Enter emergency class switch:

emergency_class_switch=x

0 or 1

Enter report resource TCH full high water


mark:

report_resource_tch_f_high_
water_mark=x

0 to 255

None

Enter report resource TCH full low water


mark:

report_resource_tch_f_low_
water_mark=x

0 to 255

None

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Ev

Issue 12 Rev 2

Table 4-1 add_cell command prompts


Prompt

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

Enter uplink dtx preference:

dtx_required=x

0 to 2

Enter IMSI attach detach:

attach_detach=x

0 or 1

Enter NCC of PLMN allowed:

ncc_of_plmn_allowed=x

0 to 255

255

Enter maximum retransmissions on RACH:

max_retran=x

0 to 3

Enter maximum mobile transmit power on


CCCH:

ms_txpwr_max_cch=x

2 to 19

Enter tx_integer for RACH retransmit


spacing:

tx_integer=x

0 to 15

Enter radio link timeout:

radio_link_timeout=x

0 to 15

Enter MS reestablish allowed:

reestablish_allowed=x

0 or 1

0
. . . continued

Enter cell reselect hysteresis:

cell_reselect_hysteresis=x

0 to 7

None

Enter C2 cell reselection parameter


indicator:

cell_reselect_param_ind=x

0 or 1

Enter C2 cell bar qualify:

cell_bar_qualify=x

0 or 1

Enter C2 cell reselection offset:

cell_reselect_offset=x

0 to 63

Enter C2 temporary offset:

temporary_offset=x

0 to 7

Enter C2 penalty time:

penalty_time=x

0 to 31

Enter rapid power down procedure active:

rapid_pwr_down=x

0 or 1

Enter rapid power down trigger threshold:

rpd_trigger=x

0 to 63

45

Enter rapid power down level offset:

rpd_offset=x

0 to 63

Enter rapid power down averaging period:

rpd_period=x

1 to 32

App Evi

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Appendix F
Typical BSS Script

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Fi

Issue 12 Rev 2

# BSC No. 1 Answers


# 1.6.0.0 (GSR 4)
freq_types_allowed 7
equip 0 SITE
0
chg_element fm_site_type 1 0
equip 0 CAB
0
3
5
equip 0 CAGE
0
0
0
yes
chg_element transcoder_location 0 0
chg_element gproc_slots 32 0
chg_element bsc_type 1 0
chg_element ber_loss_daily 4 0
chg_element ber_loss_hourly 6 0
chg_element remote_loss_daily 20 0
chg_element remote_loss_hourly 16 0
chg_element remote_loss_oos 511 0
chg_element remote_loss_restore 10 0
chg_element remote_time_oos 500 0
chg_element remote_time_restore 500 0
chg_element slip_loss_daily 10 0
chg_element slip_loss_hourly 4 0
chg_element slip_loss_oos 255 0
chg_element slip_loss_restore 10 0
chg_element sync_loss_daily 20 0
chg_element sync_loss_hourly 16 0
chg_element sync_loss_oos 511 0
chg_element sync_time_oos 90 0
chg_element sync_time_restore 30 0
equip 0 KSW
0
0
0
no
equip 0 KSW
0
1
0
no
equip 0 BSP
0
App Fii

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

chg_element SS7_L2_T2 77000 0


chg_element SS7_L2_T3 1250 0
chg_element SS7_L2_T4 500 0
chg_element SS7_L2_T5 100 0
chg_element SS7_L2_T6 4500 0
chg_element SS7_L2_T7 1250 0
chg_element SCCP_TCONN_EST 30000 0
chg_element CLEAR_COMMAND 30000 0
chg_element RADIO_CHAN_RELEASED 30000 0
chg_element CIPHERING_SUCCESSFUL 30000 0
chg_element HO_SUCCESSFUL 4100 0
chg_element HO_ALLOCATION 30000 0
chg_element SCCP_RELEASED 30000 0
chg_element ASSIGN_SUCCESSFUL 4100 0
chg_element BSC_AUDIT 30001 0
chg_element SM_AUDIT_RESPONSE 30000 0
chg_element SCCP_TIAS 420000 0
chg_element SCCP_TIAR 900000 0
chg_element BSSMAP_T7 10000 0
chg_element BSC_AUDIT_RESPONSE 30000 0
chg_element BSSMAP_TQHO 30000 0
chg_element HO_REQUEST 30000 0
chg_element EXT_HO_ALLOCATION 30000 0
chg_element SCCP_TREL 15000 0
chg_element BSSMAP_T20 30000 0
chg_element BSSMAP_T19 30000 0
chg_element BSSMAP_T1 20000 0
chg_element BSSMAP_T13 1000 0
chg_element BSSMAP_T4 20000 0
chg_element CIRCUIT_RESET_ACK 70000 0
chg_element SPI 10000 0
chg_element START_ACK 20000 0
# EQUIP CIRCUITS
equip 0 CIC
5 to 15
10
2
0
equip 0 CIC
17 to 23
10
4
3
# MISCELLANEOUS
chg_element wait_for_reselection 240 0
modify_value 0 mms_priority 255 mms 1 0
chg_element clk_src_fail_reset_period 24 0
chg_element lta_alarm_range 10 0
chg_element phase_lock_gclk 1 0
chg_element mb_preference 0 0
chg_element dpc 33 0
chg_element opc 15 0
chg_element ni 2 0
EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

chg_cell_element rr_t3212 0 2 3 4 1 1 368 39


chg_cell_element dealloc_inact 10000 2 3 4 1 1 368 39
chg_cell_element ho_ack 10000 2 3 4 1 1 368 39
chg_cell_element rf_chan_rel_ack 20000 2 3 4 1 1 368 39
chg_element handover_required_reject_switch 0 0 cell_number=2 3 4 1 1 368 39
chg_cell_element rr_t3103 4100 2 3 4 1 1 368 39
chg_cell_element rr_t3101 1700 2 3 4 1 1 368 39
chg_cell_element interfer_bands,0 0 2 3 4 1 1 368 39
chg_cell_element interfer_bands,1 8 2 3 4 1 1 368 39
chg_cell_element interfer_bands,2 13 2 3 4 1 1 368 39
chg_cell_element interfer_bands,3 18 2 3 4 1 1 368 39
chg_cell_element interfer_bands,4 25 2 3 4 1 1 368 39
chg_cell_element rach_load_period 5 2 3 4 1 1 368 39
chg_cell_element ccch_load_period 5 2 3 4 1 1 368 39
chg_cell_element rr_ny1_rep 10 2 3 4 1 1 368 39
# AVERAGING ALGORITHM CONFIGURATION
chg_act_alg_data surround_cell 2 3 4 1 1 368 39 0 0 8,0
chg_act_alg_data surround_cell 2 3 4 1 1 368 39 0 0 1,1
chg_act_alg_data rel_tim_adv 2 3 4 1 1 368 39 0 0 4,0
chg_act_alg_data rel_tim_adv 2 3 4 1 1 368 39 0 0 2,1
chg_act_alg_data rxlev_dl_ho 2 3 4 1 1 368 39 0 0 8,0
chg_act_alg_data rxlev_dl_ho 2 3 4 1 1 368 39 0 0 4,1
chg_act_alg_data rxlev_dl_pc 2 3 4 1 1 368 39 0 0 8,0
chg_act_alg_data rxlev_dl_pc 2 3 4 1 1 368 39 0 0 4,1
chg_act_alg_data rxlev_ul_ho 2 3 4 1 1 368 39 0 0 8,0
chg_act_alg_data rxlev_ul_ho 2 3 4 1 1 368 39 0 0 4,1
chg_act_alg_data rxlev_ul_pc 2 3 4 1 1 368 39 0 0 8,0
chg_act_alg_data rxlev_ul_pc 2 3 4 1 1 368 39 0 0 4,1
chg_act_alg_data rxqual_dl_ho 2 3 4 1 1 368 39 0 0 2,0
chg_act_alg_data rxqual_dl_ho 2 3 4 1 1 368 39 0 0 2,1
chg_act_alg_data rxqual_dl_ho 2 3 4 1 1 368 39 0 0 0,3
chg_act_alg_data rxqual_dl_ho 2 3 4 1 1 368 39 0 0 0,4
chg_act_alg_data rxqual_dl_ho 2 3 4 1 1 368 39 0 0 2,6
chg_act_alg_data rxqual_dl_pc 2 3 4 1 1 368 39 0 0 2,0
chg_act_alg_data rxqual_dl_pc 2 3 4 1 1 368 39 0 0 2,1
chg_act_alg_data rxqual_ul_ho 2 3 4 1 1 368 39 0 0 2,0
chg_act_alg_data rxqual_ul_ho 2 3 4 1 1 368 39 0 0 2,1
chg_act_alg_data rxqual_ul_ho 2 3 4 1 1 368 39 0 0 0,3
chg_act_alg_data rxqual_ul_ho 2 3 4 1 1 368 39 0 0 0,4
chg_act_alg_data rxqual_ul_ho 2 3 4 1 1 368 39 0 0 4,6
chg_act_alg_data rxqual_ul_pc 2 3 4 1 1 368 39 0 0 2,0
chg_act_alg_data rxqual_ul_pc 2 3 4 1 1 368 39 0 0 2,1
# DEVICE\FUNCTION EQUIPAGE
equip 1 KSW
0
0
15
yes
equip 1 BTP
0
15
20
3
equip 1 DHP
EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Fxi

Issue 12 Rev 2

chg_element wait_for_reselection 240 1


chg_element clk_src_fail_reset_period 24 1
chg_element lta_alarm_range 10 1
chg_element carriers_ins_pwr_fail 2 1
chg_element carrier_disable_time 300 1
chg_element tch_flow_control 1 1 cell_number=2 3 4 1 1 368 39
chg_element tch_busy_norm_threshold 85 1
chg_element tch_busy_critical_threshold 95 1
chg_element rf_res_ind_period 20 1
chg_element cbch_enabled 1 1 cell_number=2 3 4 1 1 368 39
chg_smscb_msg 0 200 3 1023 1 2 cell_number=2 3 4 1 1 368 39
MOTOROLA GSM
chg_smscb_msg 1 200 3 1022 1 2 cell_number=2 3 4 1 1 368 39
FREE CALLS TODAY
# PATHS
# Path 0,Site 1
equip 0 path
1
0
30
1
10
# Path 1,Site 1
equip 0 path
1
1
20
3
00
01
2
00
01
1
30
# RSLs Site 1
equip 0 RSL
1
0
0
2500
3
7
equip 0 RSL
1
App Fxii

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

App Fxiii

Issue 12 Rev 2

App Fxiv

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Glossary of Terms

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

Fourth Generation Language.

A interface

Interface between MSC and BSS.

A3

Authentication algorithm that produces SRES, using RAND and Ki.

A5

Stream cipher algorithm, residing on an MS, that produces ciphertext out


of plaintext, using Kc.

A8

Ciphering key generating algorithm that produces Kc using RAND and


Ki.

AB

Access Burst.

AB

Alarm Board (generic term refering to both AB2 and AB6).

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

Access Class (C0 to C15).

AC

Application Context.

AC

Alternating Current

ACC

Automatic Congestion Control.

ACCH

Associated Control Channel.

ACK

ACKnowledgement.

ACM

Address Complete Message.

ACSE

Associated Control Service Element.

ACU

Antenna Combining Unit.

A/D

Analogue to Digital (converter).

ADCCP

Advanced Communications Control Protocol.

ADM

ADMinistration processor.

ADMIN

ADMINistration.

ADN

Abbreviated Dialling Number.

ADPCM

Adaptive Differential Pulse Coded Modulation.

AE
Glosii

Answer Bid Ratio.

Application Entity.
SYS02 GSR5/AGSR: BSS Database

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

AEF

Additional Elementary Functions.

AFC

Automatic Frequency Control.

AFN

Absolute Frame Number.

AGC

Automatic Gain Control.

AGCH

Access Grant CHannel. A GSM common control channel used to assign


MS to a SDCCH or a TCH.

Ai

Action indicator.

AI

Artificial Intelligence.

AIB

Alarm Interface Board.

Air interface

The radio link between the BTS and the MS.

ALT

Accelerated Life Testing

AM

Amplitude Modulation.

AMA

Automatic Message Accounting (processor).

AM/MP

Cell broadcast MS terminated message. A message broadcast to all


MSs in a cell.

ANSI

American National Standards Institute.

AOC

Automatic Output Control.

AP

Application Process.

APSM

AC Power Supply Module

ARFCN

Absolute Radio Frequency Channel Number. An integer which defines


the absolute RF channel number.

ARQ

Automatic ReQuest for retransmission.

ARP

Address Resolution Protocol.

ASCE

Association Control Service Element. An ASE which provides an AP with


the means to establish and control an association with an AP in a remote
NE. Maps directly onto the Presentation layer (OMC).

ASE

Application Service Element (OMC)

ASE

Application Specific Entity (TCAP).

ASN.1

Abstract Syntax Notation One.

ASP

Alarm and Status Panel.

ASR

Answer Seizure Ratio.

ATB

All Trunks Busy.

ATI

Antenna Transceiver interface.

ATT (flag)

Attach.

ATTS

Automatic Trunk Testing Subsystem.

AU

Access Unit.

AUC

AUthentication Centre. A GSM network entity which provides the


functionality for verifying the identity of an MS when requested by the
system. Often a part of the HLR.

AUT(H)

Authentication.

AUTO

AUTOmatic mode.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosiii

Issue 12 Rev 2

B
BA
BBH

Base Band Hopping.

BCC

BTS Colour Code.

BCCH

Broadcast Control CHannel. A GSM control channel used to broadcast


general information about a BTS site on a per cell or sector basis.

BCD

Binary Coded Decimal.

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

Bearer Capability Information Element.

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

Bit Error Ratio. A measure of signal quality in the GSM system.

BES

Business Exchange Services.

BFI

Bad Frame Indication.

BHCA

Busy Hour Call Attempt.

BIB

Balanced-line Interconnect Board. Provides interface to 12 balanced


(6-pair) 120-ohm (37-pin D-type connector) lines for 2 Mbit/s circuits
(See also T43).

BLLNG

BiLLiNG.

bit/s

Bits per second (bps).

Bm

Traffic Channel (full rate).

BN

Bit Number. Number which identifies the position of a particular bit period
within a timeslot.

BPF

Bandpass Filter.

BPSM

BCU Power Supply Module.

BRI

Basic Rate Interface.

BS

Basic Service (group).

BS

Bearer Service. A type of telecommunication service that provides the


capability for the transmission of signals between user-network
interfaces. The PLMN connection type used to support a bearer service
may be identical to that used to support other types of
telecommunication service.

BSC

Base Station Controller. A network component in the GSM PLMN which


has the digital control function of controlling all BTSs. The BSC can be
located within a single BTS cabinet (forming a BSS) but is more often
located remotely and controls several BTSs (see BCF, BCU, and BSU).

BSG
Glosiv

BCCH Allocation. The radio frequency channels allocated in a cell for


BCCH transmission.

Basic Service Group.


SYS02 GSR5/AGSR: BSS Database

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

BSIC

Base Tranceiver Station Identity Code. A block of code, consisting of the


GSM PLMN colour code and a base station colour code. One Base
Station can have several Base Station Colour Codes.

BSIC-NCELL

BSIC of an adjacent cell.

BSP

Base Site control Processor.

BSS

Base Station System. The system of base station equipment


(tranceivers, controllers and so on) which is viewed by the MSC through
a single interface as defined by the GSM 08 series of recommendations,
as being the entity responsible for communicating with MSs in a certain
area. The radio equipment of a BSS may cover one or more cells. A
BSS may consist of one or more base stations. If an internal interface is
implemented according to the GSM 08.5x series of recommendations,
then the BSS consists of one BSC and several BTSs.

BSSAP

BSS Application Part (of signalling system No. 7) (DTAP + BSSMAP).

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

Base Station System Management Application Part.

BSSOMAP

BSS Operation and Maintenance Application Part (of signalling system


No. 7).

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

Bus Terminator Card.

BTCU

Backwards Compatible Transceiver Control Unit

BTP

Base Transceiver Processor

BTS

Base Transceiver Station. A network component in the GSM PLMN


which serves one cell, and is controlled by a BSC. The BTS contains one
or more Tranceivers (TRXs).

Burst

A period of modulated carrier less than one timeslot. The physical


content of a timeslot.

C7

CCITT Signalling System #7 (SS7).

CA

Cell Allocation. The radio frequency channels allocated to a particular


cell.

CA

Central Authority.

CAI

Charge Advice Information.

CB

Circuit Breaker.

CBC

Cell Broadcast Centre.

CBCH

Cell Broadcast CHannel.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosv

Issue 12 Rev 2

CBF

Combined Bandpass Filter.

CBL

Cell Broadcast Link

CBSMS

Cell Broadcast Short Message Service.

CC

Country Code.

CC

Call Control.

CCB

Cavity Combining Block.

CCCH

Common Control Channels. A class of GSM control channels used


to control paging and grant access. Includes AGCH, PCH, and
RACH.

CCCH_GROUP

Group of MSs in idle mode.

CCD

Common Channel Distributor.

CCDSP

Channel Coding Digital Signal Processor.

CCF

Conditional Call Forwarding.

CCH

Control channel. Control channels are channels which carry system


management messages.

CCH

Council for Communications Harmonization (referred to in GSM


Recommendations).

CCITT

Comit Consultatif International Tlgraphique et Tlphonique.

CCPE

Control Channel Protocol Entity.

CCS

Hundred call-seconds. The unit in which amounts of telephone traffic


are measured. A single call lasting one hundred seconds is one
CCS. See also erlang.

Cct

Circuit.

CCU

Channel Coder Unit.

CDB

Control Driver Board.

CDR

Call Detail Records.

CEB

Control Equalizer Board (BTS).

Cell

By GSM definition, a cell is an RF coverage area. At an omni-site,


cell is synonymous with site; at a sectored site, cell is synonymous
with sector. This differs from analogue systems where cell is taken to
mean the same thing as site. (See Figure 1).

1 Cell =
1 Sector

Omni Site
1Cell Site
(1 BTS)

Glosvi

6Sector Site
or
6Cell Site
(6 BTS's)

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Definition of GSM cell, sector, and site


CEPT

Confrence des administrations Europn des Postes et


Tlcommunications.

CF

Conversion Facility.

CF

All Call Forwarding services.

CFC

Conditional Call Forward.

Channel

A means of one-way transmission. A defined sequence of periods (for


example, timeslots) in a TDMA system; a defined frequency band in an
FDMA system; a defined sequence of periods and frequency bands in a
frequency hopped system.

CHV

Card Holder Verification.

CKSN

Ciphering Key Sequence Number.

C/I, CIR

Carrier to Interference ratio.

CI

Cell Identity. A block of code which identifies a cell within a location area.

CI

CUG Index.

Ciphertext

Unintelligible data produced through the use of encipherment.

CKSN

Ciphering Key Sequence Number.

CLI

Calling Line Identity.

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

Comms Power Supply Module.

CM

Configuration Management. An OMC application.

CM

Connection Management.

CMD

Command.

CMM

Channel Mode Modify.

CMIP

Common Management Information Protocol.

CMISE

Common Management Information Service Element. An ASE which


provides a means to transfer management information via CMIP
messages with another NE over an association established by ASCE
using ROSE (OMC).

CMR

Cellular Manual Revision.

CODEX

Manufacturers name for a type of multiplexer and packet switch


commonly installed at the Motorola OMC-R.

COM

Code Object Manager.

COM

Complete.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosvii

Issue 12 Rev 2

COMM, comms COMMunications.


CONF

CONFerence circuit.

CONFIG

CONFIGuration Control Program.

CP

Call Processing.

CPU

Central Processing Unit.

C/R

Command/Response field bit.

CR

Carriage Return (RETURN).

CRC

Cyclic Redundancy Check (3 bit).

CRE

Call RE-establishment procedure.

CRM

Cell Resource Machine/Manager.

CRM-LS/HS

Cellular Radio Modem-Low Speed/High Speed. Low speed modem used


to interwork 300 to 2400 bit/s data services under V.22bis, V.23, or V.21
standards. High speed modem used to interwork 1200 to 9600 bit/s data
services under V.22bis, V.32, or V.29/V.27ter/V.21 standards.

CRT

Cathode Ray Tube (video display terminal).

CSFP

Code Storage Facility Processor.

CSP

Central Statistics Process. The statistics process in the BSC.

CSPDN

Circuit Switched Public Data Network.

CT

Channel Tester.

CUG

Closed User Group supplementary service.

D/A

Digital to Analogue (converter).

DAN

Digital Announcer (for recorded announcements on MSC).

DAS

Data Acquisition System.

Db

Decibel. A unit of power ratio measurement.

DB

DataBase.

DB

Dummy Burst (see Dummy burst).

DBA

DataBase Administration/Database Administrator.

DBMS

DataBase Management System.

dc

Direct Current.

DCB

Diversity Control Board (p/o DRCU).

DCCH

Dedicated Control Channels. A class of GSM control channels used to


set up calls and report measurements. Includes SDCCH, FACCH, and

SACCH.
DCE
DCF
Glosviii

Data Circuit terminating Equipment.


Data Communications Function.
SYS02 GSR5/AGSR: BSS Database

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

DCN

Data Communications Network. A DCN connects Network Elements with


internal mediation functions or mediation devices to the Operations
Systems.

DCS

Digital Communication/Cellular System. A non-GSM cellular phone


network using digital techniques similar to those used in GSM but
operating on different frequencies.

DDS

Direct Digital Synthesis.

DEQB

Diversity Equalizer Board.

DET

Detach.

DFE

Decision Feedback Equalizer.

DHP

Digital Host Processor.

DIA

Drum Intercept Announcer.

DIQ

Diversity In phase and Quadrature phase.

DIR

Device Interface Routine.

DISC

DISConnect.

DL

Data Link (layer).

DLCI

Data Link Connection Identifier.

DLD

Data Link Discriminator.

DLNB

Diversity Low Noise Block.

DLSP

Data Link Service Process

Dm

Control Channel (ISDN terminology applied to mobile service).

DMA

Deferred Maintenance Alarm. An alarm report level; an immediate or


deferred response is required (see also PMA).

DMA

Direct Memory Access

DMX

Distributed Electronic Mobile Exchange (Motorolas networked EMX


family).

DN

Directory Number.

DNIC

Data Network Identifier.

Downlink

Physical link from the BTS towards the MS (BTS transmits, MS


receives).

DP

Dial/Dialled Pulse.

DPC

Destination Point Code. A part of the label in a signalling message that


uniquely identifies, in a signalling network, the (signalling) destination
point of the message.

DPC

Digital Processing and Control.

DPNSS

Digital Private Network Signalling System (BT standard for PABX


interface).

DPP

Dual path preselector.

DPSM

Digital Power Supply Module.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosix

Issue 12 Rev 2

DRAM

Dynamic Random Access Memory.

DRC

Data Rate Converter board. Provides data and protocol conversion


between PLMN and destination network for 8 circuits (p/o IWF).

DRCU

Diversity Radio Channel Unit. Contains transceiver, digital control


circuits, and power supply (p/o BSS) (see RCU).

(D)RCU

Generic term for radio channel unit. May be standard RCU or diversity
radio channel unit DRCU.

DRI

Digital Radio Interface. Provides encoding/decoding and


encryption/decryption for radio channel (p/o BSS).

DRIM

Digital Radio Interface extended Memory. A DRI with extra memory.

DRIX
BSS).

DRI Extender half size board. Fibre optic link from DRI to BCU (p/o

DRX, DRx

Discontinuous Reception. A means of saving battery power (for example


in hand-portable units) by periodically and automatically switching the
MS receiver on and off.

DS-2

German term for 2 Mbit/s line (PCM interface).

DSE

Data Switching Exchange.

DSP

Digital Signal Processor.

DSS1

Digital Subscriber Signalling No 1.

DSSI

Diversity Signal Strength Indication.

DTAP

Direct Transfer Application Part.

DTE

Data Terminal Equipment.

DTF

Digital Trunk Frame.

DTI

Digital Trunk Interface.

DTMF

Dual Tone Multi-Frequency (tone signalling type).

DTX, DTx

Discontinuous Transmission. A means of saving battery power (for


example in hand-portable units) and reducing interference by
automatically switching the transmitter off when no speech or data are to
be sent.

Dummy burst

A period of carrier less than one timeslot whose modulation is a defined


sequence that carries no useful information. A dummy burst fills a
timeslot with an RF signal when no information is to be delivered to a
channel.

See Erlang.

E1

CEPT 2.048 Mbit/s-1 standard 32 timeslot link.

EA

External Alarms.

EAS

External Alarm System.

Eb/No

Energy per Bit/Noise floor.

Glosx

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

EBSG

Elementary Basic Service Group.

EC

Echo Canceller.

EC

European Commission.

ECB

Provides echo cancelling for telephone trunks for 30 channels (EC).

ECID

The Motorola European Cellular Infrastructure Division.

ECM

Error Correction Mode (facsimile).

Ec/No

Ratio of energy per modulating bit to the noise spectral density.

EEPROM

Electrically Erasable Programmable Read Only Memory.

EGSM

Extended GSM.

EGSM

Extened Global System for Mobile Communications.

EIR

Equipment Identity Register.

EIRP

Effective Isotropic Radiated Power.

EIRP

Equipment Identity Register Procedure.

EM

Event Management. An OMC application.

EMC

Electro Magnetic Compatibility.

EMF

Electro Motive Force.

EMI

Electro Magnetic Interference.

EMX

Electronic Mobile Exchange (Motorolas MSC family).

EN

European Norm(e)

en bloc

Fr. all at once (a CCITT #7 Digital Transmission scheme); En bloc


sending means that digits are sent from one system to another ~ (that is,
all the digits for a given call are sent at the same time as a group). ~
sending is the opposite of overlap sending. A system using ~ sending
will wait until it has collected all the digits for a given call before it
attempts to send digits to the next system. All the digits are then sent as
a group.

EOT

End of Tape.

Erlang

International (dimensionless) unit of traffic intensity defined as the ratio


of time a facility is occupied to the time it is available for occupancy.
One erlang is equal to 36 ccs. In the US this is also known as a traffic
unit (TU).

EPROM

Erasable Programmable Read Only Memory.

EPSM

Exhancec power supply module.

EQB

Equalizer Board. Control circuit for equalization for 8 time slots each with
equalizing circuitry and a DSP (p/o RCU).

EQ DSP

Equalizer Digitizer Signal Processor.

ERP

Effective Radiated Power.

ESP

Electro-static Point.

ESQL

Embedded SQL (Structured Query Language). An RDBMS programming

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosxi

Issue 12 Rev 2

interface language.
E-TACS

Extended TACS (analogue cellular system, extended).

ETR

ETSI Technical Report.

ETS

European Telecommunication Standard.

ETSI

European Telecommunications Standards Institute.

ETX

End of Transmission.

EU

European Union.

EXEC

Executive Process.

FA

Fax Adaptor.

FA

Full Allocation.

FA

Functional Area.

FAC

Final Assembly Mode.

FACCH

Fast Associated Control Channel. A GSM dedicated control channel


which is associated with a TCH and carries control information after a
call is set up (see SDCCH).

FACCH/F

Full rate Fast Associated Control Channel.

FACCH/H

Half rate Fast Associated Control Channel.

FB

Frequency Correction Channel. A GSM broadcast control channel which


carries information for frequency correction of the mobile (MS).

FCP

Fault Collection Process (in BTS).

FCS

Frame Check Sequence.

FD

Full Rate Data.

FDMA

Frequency Division Multiple Access.

FEC

Forward Error Correction.

FEP

Front End Processor.

FER

Frame Erasure Ratio.

FFS, FS

For Further Study.

FHI

Frequency Hopping Indicator.

FIR

Finite Impulse Response (filter type).

FK

Foreign Key. A database column attribute; the foreign key indicates an


index into another table.

FM

Fault Management (at OMC).

FM

Frequency Modulation.

FMUX

Fibre Multiplexer Board.

FN

Frame Number. Identifies the position of a particular TDMA frame within


a hyperframe.

FOA

First Office Application.

FPCU

Fan power conversion unit.

FOX

Fibre Optic Extender board

FR

Glosxii

Frequency correction Burst (see Frequency correction burst).

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

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

EMOTOROLA LTD. 2001

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

Field replacement unit.

FS

Frequency Synchronization.

FS

Full rate speech.

FSL

Free Space Loss. The decrease in the strength of a radio signal as it


travels between a transmitter and receiver. The FSL is a function of the
frequency of the radio signal and the distance the radio signal has
travelled from the point source.

FTAM

File Transfer, Access, and Management. An ASE which provides a


means to transfer information from file to file (OMC).

FTP

Fault Translation Process (in BTS).

FTP

File Transfer Program

FW

Firmware.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

GSM Multiplexer Board (p/o BSC).

GMR

GSM Manual Revision.

GMSC

Gateway Mobile services Switching Centre (see Gateway MSC).

GMSK
GSM.

Gaussian Minimum Shift Keying. The modulation technique used in

GND

Ground

GOS

Grade of Service.

GPA

GSM PLMN Area.

GPC

General Protocol Converter.

GPROC

Generic Processor board. GSM generic processor board: a 68030 with 4


to 16 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR).

GPS

Global Positioning by Satellite.

GSA

GSM Service Area. The area in which an MS can be reached by a fixed


subscriber, without the subscribers knowledge of the location of the MS.
A GSA may include the areas served by several GSM PLMNs.

GSA

GSM System Area. The group of GSM PLMN areas accessible by GSM
MSs.

GSM

Groupe Spcial Mobile (the committee).

GSM

Global System for Mobile communications (the system).

GT

Global Title.

Guard period

Period at the beginning and end of timeslot during which MS


transmission is attenuated.

GUI

Graphical User Interface.

GWY

Glosxiv

Generic Clock board. System clock source, one per site (p/o BSS, BTS,
BSC, IWF, RXCDR).

GateWaY (MSC/LR) interface to PSTN.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

H
H-M

Human-Machine Terminals.

HAD, HAP

HLR Authentication Distributor.

Handover

The action of switching a call in progress from one radio channel to


another radio channel. Handover allows established calls to continue by
switching them to another radio resource, as when an MS moves from
one BTS area to another. Handovers may take place between the
following GSM entities: timeslot, RF carrier, cell, BTS, BSS and MSC.

HDLC

High level Data Link Controller.

HDSL

High bit rate Digital Subscriber Line.

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

Heat Management System. The system that provides environmental


control of the components inside the ExCell cabinet.

HO

HandOver. The action of switching a call in progress from one radio


channel to another radio channel. Handover allows established calls to
continue by switching them to another radio resource, for example, when
MSs move from one base station area to another.

HPU

Hand Portable Unit.

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

HLR Subscriber Management.

HSN

Hopping Sequence Number.

HW

Hardware.

Hyperframe

2048 superframes. The longest recurrent time period of the frame


structure.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosxv

Issue 12 Rev 2

I
I
IA5

International Alphanumeric 5.

IADU

Integrated Antenna Distribution Unit.

IAM

Initial Address Message.

IAS

Internal Alarm System.

IC

Integrated Circuit.

IC

Interlock Code (closed user group supplementary service).

ICB

Incoming Calls Barred.

ICM

In-Call Modification.

ICMP

Internet Control Message Protocol.

ID, id

Identification/Identity.

IDN

Integrated Digital Network.

IE

Signalling Information Element.

IEC

Internet electrotechnical commission.

IEEE

Institute of Electrical and Electronic Engineers.

IEI

Information Element Identifier.

IF

Intermediate Frequency.

IFAM

Initial and Final Address Message.

IM

InterModulation.

IMACS

Intelligent Monitor And Control System.

IMEI

International Mobile station Equipment Identity. Electronic serial number


that uniquely identifies the MS as a piece or assembly of equipment. The
IMEI is sent by the MS along with request for service.

IMM

IMMediate assignment message.

IMSI

International Mobile Subscriber Identity. Published mobile number (prior


to ISDN) (see also MSISDN) that uniquely identifies the subscription. It
can serve as a key to derive subscriber information such as directory
number(s) from the HLR.

IN

Intelligent Network.

IN

Interrogating Node. A switching node that interrogates an HLR, to route


a call for an MS to the visited MSC.

INS

IN Service.

INS

Intelligent Network Service.

Interworking

The general term used to describe the inter-operation of networks,


services, supplementary services and so on. See also IWF.

I/O
Glosxvi

Information (frames).

Input/Output.
SYS02 GSR5/AGSR: BSS Database

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

EMOTOROLA LTD. 2001

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

International Switching Centre.

ISDN

Integrated Services Digital Network. An integrated services network that


provides digital connections between user-network interfaces.

ISO

International Standards Organisation.

ISQL

Informix Structured Query Language.

ISUP

ISDN User Part (of signalling system No. 7).

ITC

Information Transfer Capability.

ITU

International telecommunication union

IWF

InterWorking Function. A network functional entity which provides


network interworking, service interworking, supplementary service
interworking or signalling interworking. It may be a part of one or more
logical or physical entities in a GSM PLMN.

IWMSC

InterWorking MSC.

IWU

InterWorking Unit.

kilo (103).

Constraint length of the convolutional code.

Kb

Kilo-bit.

kbit/s, kbps

kilo-bit per second.

Kc

Ciphering key. A sequence of symbols that controls the operation of


encipherment and decipherment.

kHz

kilo-Hertz (103).

Ki

Individual subscriber authentication Key (p/o authentication process of


AUC).

KSW

Kiloport SWitch board. TDM timeslot interchanger to connect calls (p/o


BSS).

KSWX

KSW Expander half size board. Fibre optic distribution of TDM bus (p/o
BSS).

kW

kilo-Watt.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosxvii

Issue 12 Rev 2

L
L1
L2ML

Layer 2 Management Link.

L2R

Layer 2 Relay function. A function of an MS and IWF that adapts a


users known layer2 protocol LAPB onto RLP for transmission between
the MT and IWF.

L2R BOP

L2R Bit Orientated Protocol.

L2R COP

L2R Character Orientated Protocol.

L3

Layer 3.

LA

Location Area. An area in which an MS may move freely without


updating the location register. An LA may comprise one or several base
station areas.

LAC

Location Area Code.

LAI

Location Area Identification (identity). The information indicating the


location area in which a cell is located.

LAN

Local Area Network.

LANX

LAN Extender half size board. Fibre optic distribution of LAN to/from
other cabinets (p/o BSS etc).

LAPB

Link Access Procedure B (balanced) channel (of CCITT Rec. X.25).

LAPD

Link Access Procedure D (data) channel.

LAPDm

Link Access Procedure Dm (mobile D) channel.

LC

Inductor Capacitor (type of filter).

LCF

Link Control Function.

LCP

Link Control Processor.

LE

Local Exchange.

LED

Light Emitting Diode.

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

Traffic channel (half rate).

LMS

Least Mean Square.

LMSI

Local Mobile Station Identity. A unique identity temporarily allocated to


visiting mobile subscribers in order to speed up the search for subscriber
data in the VLR, when the MSRN allocation is done on a per cell basis.

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.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

LPC

Linear Predictive Code.

LR

Location Register. The GSM functional unit where MS location


information is stored. The HLR and VLR are location registers.

LTA

Long Term Average. The value required in a BTSs GCLK frequency


register to produce a 16.384 Mhz clock.

LTE

Local Terminal Emulator.

LTP

Long Term Predictive.

LTU

Line terminating unit.

LV

Length and Value.

LVD

Low voltage disconnect.

Mega (106).

M&TS

Maintenance and Troubleshooting. Functional area of Network


Management software which (1) collects and displays alarms, (2)
collects and displays Software/Hardware errors, and (3) activates test
diagnostics at the NEs (OMC).

MA

Mobile Allocation. The radio frequency channels allocated to an MS for


use in its frequency hopping sequence.

MAC

Medium Access Control.

MACN

Mobile Allocation Channel Number.

MAF

Mobile Additional Function.

MAI

Mobile Allocation Index.

MAIDT

Mean Accumulated Intrinsic Down Time.

MAINT

MAINTenance.

MAIO

Mobile Allocation Index Offset.

MAP

Mobile Application Part (of signalling system No. 7). The inter-networking
signalling between MSCs and LRs and EIRs.

MAPP

Mobile Application Part Processor.

MCAP

Motorola Cellular Advanced Processor.

MCC

Mobile Country Code.

MCU

Main control unit.

MCU-m

Main control unit micro (used in M-cellmicro)

MDL

(mobile) Management (entity) - Data Link (layer).

ME

Maintenance Entity (GSM Rec. 12.00).

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosxix

Issue 12 Rev 2

ME

MEF

Maintenance Entity Function (GSM Rec. 12.00).

MF

MultiFrame.

MF

Multi-Frequency (tone signalling type)

MF

MultiFunction block.

MGMT

Management.

MGR

Manager.

MHS

Message Handling System.

MHS

Mobile Handling Service.

MHz

Mega-Hertz (106).

MI

Maintenance Information.

MIB

Management Information Base. A Motorola OMC-R database. There is a


CM MIB and an EM MIB.

MIC

Mobile Interface Controller.

MIT

Management Information Tree. Name of a file on the Motorola OMC-R.

MM

Mobility Management.

MME

Mobile Management Entity.

MMI

Man Machine Interface. The method in which the user interfaces with the
software to request a function or change parameters.

MML

Man Machine Language. The tool of MMI.

MMS

Multiple Serial Interface Link.

MNC

Mobile Network Code.

MNT

MaiNTenance.

MO

Mobile Originated.

MO/PP

Mobile Originated Point-to-Point messages.

MOMAP

Motorola OMAP.

MoU

Memorandum of Understanding.

MPC

Multi Personal Computer (was p/o OMC).

MPH

(mobile) Management (entity) - PHysical (layer) [primitive].

MPX

MultiPleXed.

MRN

Mobile Roaming Number.

MS

Mobile Station. The GSM subscriber unit.

MSC
Glosxx

Mobile Equipment. Equipment intended to access a set of GSM PLMN


and/or DCS telecommunication services, but which does not contain
subscriber related information. Services may be accessed while the
equipment, capable of surface movement within the GSM system area,
is in motion or during halts at unspecified points.

Mobile services Switching Centre.


SYS02 GSR5/AGSR: BSS Database

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

MSCM

Mobile Station Class Mark.

MSCU

Mobile Station Control Unit.

msec

millisecond (.001 second).

MSI

Multiple Serial Interface board. Intelligent interface to two 2 Mbit/s digital


links (see 2 Mbit/s link and DS-2) (p/o BSS).

MSIN

Mobile Station Identification Number.

MSISDN

Mobile Station International ISDN Number. Published mobile number


(see also IMSI ). Uniquely defines the mobile station as an ISDN terminal.
It consists of three parts: the Country Code (CC), the National
Destination Code (NDC) and the Subscriber Number (SN).

MSRN

Mobile Station Roaming Number. A number assigned by the MSC to


service and track a visiting subscriber.

MSU

Message Signal Unit. A signal unit containing a service information octet


and a signalling information field which is retransmitted by the signalling
link control, if it is received in error.

MT

Mobile Terminated. Describes a call or short message destined for an


MS.

MT (0,1,2)

Mobile Termination. The part of the MS which terminates the radio


transmission to and from the network and adapts terminal equipment
(TE) capabilities to those of the radio transmission. MT0 is mobile
termination with no support for terminal, MT1 is mobile termination with
support for an S-type interface and MT2 is mobile termination with
support for an R-type interface.

MTM

Mobile-To-Mobile (call).

MTP

Message Transfer Part.

MT/PP

Mobile Terminated Point-to-Point messages.

MTBF

Mean Time Between Failures.

MTL

Message Transfer Link.

MTL

MTP Transport Layer Link (A-Interface).

MTP

Message Transfer Part.

MTTR

Mean Time To Repair.

Multiframe

Two types of multiframe are defined in the system: a 26-frame


multiframe with a period of 120ms and a 51-frame multiframe with a
period of 3060/13ms.

MUMS

Multi User Mobile Station.

MUX

Multiplexer.

NB

Normal Burst (see Normal burst).

NCC

Network (PLMN) Colour Code.

NCELL

Neighbouring (or current serving) Cell.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosxxi

Issue 12 Rev 2

ND
NDC

National Destination Code.

NDUB

Network Determined User Busy.

NE

Network Element (Network Entity).

NEF

Network Element Function block.

NF

Network Function.

NI

Network Interface.

NIC

Network Independent Clocking.

NIU

Network interface unit.

NLK

Network LinK processor(s).

Nm

Newton metres.

NM

Network Management (manager). NM is all activities which control,


monitor and record the use and the performance of resources of a
telecommunications network in order to provide telecommunication
services to customers/users at a certain level of quality.

NMASE

Network management application service element.

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

National Mobile Station Identification number.

NMT

Nordic Mobile Telephone system.

NN

No Nulls. A database column attribute meaning the column must contain


a value in all rows.

Normal burst

A period of modulated carrier less than a timeslot.

NPI

Number Plan Identifier.

NPSM

Negative power supply module.

NRZ

Non Return to Zero.

NSAP

Network Service Access Point.

NSP

Network Service Provider.

NT

Network Termination.

NT

Non Transparent.

NTU

Network terminating unit.

NUA

Network User Access.

NUI

Network User Identification.

NUP

National User Part (of signalling system No. 7).

NVRAM

Non-Volatile Random Access Memory.

nW

Nano-Watt (109).

N/W

Glosxxii

No Duplicates. A database column attribute meaning the column


contains unique values (used only with indexed columns).

NetWork

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

O
O&M

Operations and Maintenance.

OACSU

Off-Air Call SetUp. The procedure in which a telecommunication


connection is being established whilst the RF link between the MS and
the BTS is not occupied.

OCB

Outgoing Calls Barred within the closed user group.

OFL

% OverFlow.

OMAP

Operations and Maintenance Application Part (of signalling system No.


7) (was OAMP).

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

Operations and Maintenance Centre Radio Part.

OMCS

Operations and Maintenance Centre Switch Part.

OML

Operations and Maintenance Link.

OMP

Operation and Maintenance Processor.

OMS

Operation and Maintenance System (BSCOMC).

OMSS

Operation and Maintenance SubSystem.

OOS

Out Of Service.

OPC

Originating Point Code. A part of the label in a signalling message that


uniquely identifies, in a signalling network, the (signalling) origination
point of the message.

ORAC

Olympus radio architecture control board (part of TCU-m)

OS

Operating System.

OSI

Open Systems Interconnection

OSF

Operation Systems Function block.

OSF/MOTIF

Open Software Foundation Motif. The basis of the GUI used for the
Motorola OMC-R MMI.

OSS

Operator Services System.

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.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosxxiii

Issue 12 Rev 2

P
PA
PAB

Power Alarm Board.

PABX

Private Automatic Branch eXchange.

PAD

Packet Assembler/Disassembler facility.

Paging

The procedure by which a GSM PLMN fixed infrastructure attempts to


reach an MS within its location area, before any other network-initiated
procedure can take place.

PATH

CEPT 2 Mbit/s route through the BSS network.

PBX

Private Branch eXchange.

PC

Personal Computer.

PC

Power converter

PCH

Paging CHannel. A GSM common control channel used to send paging


messages to the MSs.

PCM

Pulse Code Modulation (see also 2 Mbit/s link which is the physical
bearer of PCM).

PCMCIA

Personal computer memory card industry association (PC cards).

PCN

Personal Communications Network.

PCR

Preventative Cyclic Retransmission. A form of error correction suitable


for use on links with long transmission delays, such as satellite links.

PCU

Power converter unit.

PCS

Personal communications system.

pd

Potential difference.

PD

Protocol Discriminator.

PD

Public Data.

PDB

Power Distribution Board.

PDF

Power Distribution Frame (MSC/LR).

PDN

Packet Data Network.

PDU

Power Distribution Unit

PDU

Protected Data Unit.

PEDC

Pan European Digital Cellular.

PH

Packet Handler.

PH

PHysical (layer).

PHI

Packet Handler Interface.

PID

Process IDentifier.

PI

Presentation Indicator.

PIM
Glosxxiv

Power Amplifier.

PCM Interface Module (MSC).


SYS02 GSR5/AGSR: BSS Database

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

PIN

Personal Identification Number.

PIX

Parallel Interface Extender half size board. Customer alarm interface


(p/o BSS).

PK

Primary Key. A database column attribute, the primary key is a not-null,


non-duplicate index.

Plaintext

Unciphered data

PLL

Phase Lock Loop (refers to phase locking the GCLK in the BTS).

PLMN

Public Land Mobile Network. The mobile communications network.

PM

Performance Management. An OMC application.

PM-UI

Performance Management User Interface.

PMA

Prompt Maintenance Alarm. An alarm report level; immediate action is


necessary (see also DMA).

PMS

Pseudo MMS.

PMUX

PCM MUltipleXer.

PN

Permanent Nucleus (of GSM).

POTS

Plain Old Telephone Service (basic telephone services).

p/o

Part of.

pp, pp

Peak-to-peak.

PP

Point-to-Point.

ppb

Parts per billion.

ppm

Parts per million (x 106).

PPS

Pulses per second.

PPSM

Positive power supply module.

PRI

Primary rate interface.

PROM

Programmable Read Only Memory.

PSAP

Presentation Services Access Point.

PSM

Power supply module

PSPDN

Public Switched Packet Data Network. Public data communications


network. X.25 links required for NE to OMC communications will probably
be carried by PSPDN.

PSTN

Public Switched Telephone Network. The UK landline telephone network.

PSU

Power supply unit.

PSW

Pure Sine Wave.

PTO

Public Telecommunications Operator.

PVC

Permanent Virtual Circuit.

PWR

Power.

PXPDN

Private eXchange Packet Data Network.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosxxv

Issue 12 Rev 2

Q
Q-adapter

Used to connect MEs and SEs to TMN (GSM Rec. 12.00).

QAF

Q-Adapter Function Block.

QEI

Quad European Interface. Interfaces four 2 Mbit/s circuits to TDM switch


highway (see MSI).

QOS

Quality Of Service.

RAB

Random Access Burst.

RACCH

Random Access Control CHannel. A GSM common control channel


used to originate a call or respond to a page.

RACH

Random Access CHannel.

RAM

Random Access Memory.

RAND

RANDom number.

RAx

Rate Adaptation.

RBCU

Remote BTS control unit.

RBDS

Remote BSS Diagnostic System (a discontinued Motorola diagnostic


facility).

RBER

Residual Bit Error Ratio.

RBTS

Remote Base Tranceiver Station

RCB

Radio Control Board (p/o DRCU).

RCI

Radio Channel Interface

RCP

Radio Control Processor.

RCU

Radio Channel Unit. Contains transceiver, digital control circuits, and


power supply (p/o BSS) (see DRCU).

RCVR

Receiver.

RDBMS

Relational Database Management System.

RDB

Requirements database.

RDN

Relative Distinguished Name. A series of RDN form a unique identifier,


the distinguished name, for a particular network element.

REC, Rec.

RECommendation.

REL

RELease.

RELP

Residual Excited Linear Predictive.

RELP-LTP

RELP Long Term Prediction. A name for GSM full rate (see full rate).

REQ

REQuest.

RES

Radio equipment and systems

RF

Radio Frequency.

Glosxxvi

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

RFC, RFCH

Radio Frequency Channel. A partition of the system RF spectrum


allocation with a defined bandwidth and centre frequency.

RFE

Receiver Front End (shelf).

RFEB

Receiver Front End Board (p/o DRCU II).

RFI

Radio Frequency Interference.

RFN

Reduced TDMA Frame Number.

RISC

Reduced Instruction Set Computer.

RLP

Radio Link Protocol. An ARQ protocol used to transfer user data


between an MT and IWF. See GSM 04.22.

rms

Root Mean Square (value).

RMSU

Remote Mobile Switching Unit.

ROM

Read Only Memory.

ROSE

Remote Operations Service Element. An ASE which carries a message


between devices over an association established by ASCE (a CCITT
specification for O & M) (OMC).

Roundtrip
propagation
delay

Time period between transmit and receive instant of a timeslot in the


BTS, determined by the response behaviour of the MS and the MS to
BTS distance.

RPE

Regular Pulse Excited.

RPE-LTP

Regular Pulse Excitation - Long Term Prediction. The GSM digital


speech coding scheme.

RPR

Read Privilege Required. Access to the column is allowed only for


privileged accounts.

RR

Radio Resource management.

RR

Receive Ready (frame).

RRSM

Radio Resource State Machine.

RSE

Radio System Entity.

RSL

Radio Signalling Link.

RSLF

Radio System Link Function.

RSS

Radio SubSystem (replaced by BSS).

RSSI

Received Signal Strength Indication.

RTC

Remotely Tuneable Channel Combiner.

RTE

Remote Terminal Emulator.

RU

Rack Unit.

Rx

Receive(r).

RXCDR

Remote Transcoder.

RXLEV-D

Received signal level downlink.

RXLEV-U

Received signal level uplink.

RXQUAL-D

Received signal quality downlink.

RXQUAL-U

Received signal quality uplink.

RXU

Remote Transcoder Unit. The shelf which houses the remote transcoder
modules in a BSSC cabinet at a remote transcoder site.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosxxvii

Issue 12 Rev 2

S
SABM
SACCH

Slow Associated Control CHannel. A GSM control channel used by the


MS for reporting RSSI and signal quality measurements.

SAGE

A brand of trunk test equipment.

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

System Audits Process.

SAPI

Service Access Point Indicator (identifier).

SAW

Surface Acoustic Wave.

SB

Synchronization Burst (see Synchronization burst).

SC

Service Centre (used for Short Message Service).

SC

Service Code.

SCCA

System Change Control Administration. Software module which allows


full or partial software download to the NE (OMC).

SCCP

Signalling Connection Control Part.

SCEG

Speech Coding Experts Group (of GSM).

SCH

Synchronization CHannel. A GSM broadcast control channel used to


carry information for frame synchronization of MSs and identification of
base stations.

SCI

Status Control Interface.

SCIP

Serial Communication Interface Processor.

SCM

Status Control Manager.

SCN

Sub-Channel Number. One of the parameters defining a particular


physical channel in a BS.

SCP

Service Control Point (an intelligent network entity).

SCU

Slim carrier unit.

SDCCH

Stand-alone Dedicated Control CHannel. A GSM control channel where


the majority of call setup occurs. Used for MS to BTS communications
before MS assigned to TCH.

SDH

Synchronous digital hierarchy.

SDR

Special Drawing Rights (an international basket currency for billing).

SE

Support Entity (GSM Rec. 12.00).

SEF

Support Entity Function (GSM Rec.12.00).

SFH

Slow Frequency Hopping.

SFRAS

System feature requirements and architecture specification.

SI
Glosxxviii

Set Asynchronous Balanced Mode. A message which establishes the


signalling link over the air interface.

Screening Indicator.
SYS02 GSR5/AGSR: BSS Database
FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

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

Subscriber Identity Module. Removable module which is inserted into a


mobile equipment; it is considered as part of the MS. It contains security
related information (IMSI, Ki, PIN), other subscriber related information
and the algorithms A3 and A8.

SIO

Service Information Octet. Eight bits contained in a message signal unit,


comprising the service indicator and sub-service field.

SITE

BSC, BTS or collocated BSC-BTS site.

SIX

Serial Interface eXtender. Converts interface levels to TTL levels. Used


to extend 2 serial ports from GPROC to external devices (RS232,
RS422, and fibre optics).

SK

Secondary Key. A database column attribute, the secondary key


indicates an additional index and/or usage as a composite key.

SLNK

Serial Link.

SLTM

Signalling Link Test Message.

SM

Switch Manager.

SMAE

System Management Application Entity (CCITT Q795, ISO 9596).

SME

Short Message Entity.

SMP

Motorola Software Maintenance Program.

SMS

Short Message Service.

SMSCB

Short Message Service Cell Broadcast.

SMS-SC

Short Message Service - Service Centre.

SMS/PP

Short Message Service/Point-to-Point.

SN

Subscriber Number.

SND

SeND.

SNDR

SeNDeR.

SNR

Serial Number.

SOA

Suppress Outgoing Access.

SP

Service Provider. The organisation through which the subscriber obtains


GSM telecommunications services. This may be a network operator or
possibly a separate body.

SP

Signalling Point.

SP

Special Product.

SPC

Signalling Point Code.

SPC

Suppress Preferential (closed user group).

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosxxix

Issue 12 Rev 2

SPI

Signalling Point Inaccessible.

SQL

Structured Query Language.

SRD

Service Request Distributor.

SRES

Signed RESponse (authentication).

SS7, SS#7

CCITT Signalling System No. 7 (alias C7).

SS

Supplementary Service. A modification of, or a supplement to, a basic


telecommunication service.

SSA

SCCP messages, Subsystem-allowed (see CCITT Q.712 para 1.15).

SSC

Supplementary Service Control string.

SSF

Subservice Field. The level 3 field containing the network indicator and
two spare bits.

SSM

SCCP State Machine.

SSP

Service Switching Point (an intelligent network element).

SSP

SCCP messages, Subsystem-prohibited (see CCITT Q.712 para 1.18).

SSS

Switching SubSystem (comprising the MSC and the LRs)

STAN

Statistical ANalysis (processor).

STAT

STATistics.

stats

Statistics.

STC

System Timing Controller.

STP

Signalling Transfer Point.

Superframe

51 traffic/associated control multiframes or 26 broadcast/common control


multiframes (period 6.12s).

SVC

Switch Virtual Circuit.

SVM

SerVice Manager.

SW

Software.

SWFM

SoftWare Fault Management.

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.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

T
T1

ANSI 1.555 Mbit/s standard 24 timeslot link.

T43

Type 43 Interconnect Board. Provides interface to 12 unbalanced (6-pair)


75-ohm (T43 coax connectors) lines for 2 Mbit/s circuits (See BIB).

TA

Terminal Adaptor. A physical entity in the MS providing terminal


adaptation functions (see GSM 04.02).

TA

Timing Advance.

TAC

Type Approval Code.

TACS

Total Access Communications System (European analogue cellular


system).

TAF

Terminal Adaptation Function.

TATI

Transmit antenna transceiver interface.

TBD

To Be Determined.

TC

Transaction Capabilities.

TC shelf

Transmit combiner shelf.

TCAP

Transaction Capabilities Application Part (of signalling system No. 7).

TCH

Traffic CHannel. GSM logical channels which carry either encoded


speech or user data. A Traffic channel can be one of the following:
TCH/F (full rate TCH), TCH/F2.4 (full rate TCH at < 2.4kbit/s), TCH/F4.8
(full rate TCH at 4.8kbit/s), TCH/F9.6 (full rate TCH at 9.6kbit/s), TCH/FS
(full rate speech TCH), TCH/H (half rate TCH), TCH/H2.4 (half rate TCH
at 2.4kbit/s), TCH/H4.8 (half rate TCH at 4.8kbit/s) or TCH/HS (half rate
speech TCH).

TCI

Tranceiver Control Interface.

TCP/IP

Transmission Control Protocol/Internet Protocol.

TCU

Transceiver control unit.

TCU-m

Transceiver control unit micro (combination of ORAC and RF boards).

TDM

Time Division Multiplexing.

TDMA

Time Division Multiple Access.

TDU

Topcell Data Unit

TE

Terminal Equipment. Equipment that provides the functions necessary


for the operation of the access protocols by the user.

Tei

Terminal endpoint identifier.

TEI

Terminal Equipment Identity.

TEMP

TEMPorary.

TEST

TEST control processor.

TFA

Transfer Allowed.

TFP

Transfer Prohibited.

TFTP

Trivial File Transfer Protocol.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

TDM Modem Interface board. Provides analogue interface from IWF to


modems for 16 circuits (p/o IWF).

TMM

Traffic Metering and Measuring.

TMN

Telecommunications Management Network. The implementation of the


Network Management functionality required for the PLMN is in terms of
physical entities which together constitute the TMN.

TMSI

Temporary Mobile Subscriber Identity. A unique identity temporarily


allocated by the MSC to a visiting mobile subscriber to process a call.
May be changed between calls and even during a call, to preserve
subscriber confidentiality.

TN

Timeslot Number.

Traffic
channels

Channels which carry users speech or data (see also TCH).

Traffic unit

Equivalent to an erlang.

Training
sequence

Sequence of modulating bits employed to facilitate timing recovery


and channel equalisation in the receiver.

TRAU

Transcoder Rate Adaption Unit.

TRX

TRansceiver(s). A network component which can serve full duplex


communication on 8 full-rate traffic channels according to specification
GSM 05.02. If Slow Frequency Hopping (SFH) is not used, then the TRX
serves the communication on one RF carrier.

TS

Telecommunications standard.

TS

Teleservice.

TS

TimeSlot (see Timeslot).

TSA

TimeSlot Acquisition.

TSDA

Tranceiver Speech & Data Interface.

TSC

Training Sequence Code.

TSI

Time Slot Interchange.

TSM

Transceiver station manager board (part of TCV).

TTL

Transistor to Transistor Logic.

TTY

TeleTYpe (refers to any terminal).

TU

Traffic Unit.

TUP

Telephone User Part (of signalling system No. 7).

Tx
Glosxxxii

Traffic Manager.

Transmit(ter)
SYS02 GSR5/AGSR: BSS Database

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL


NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

U
mS

micro-second (106).

UA

Unnumbered Acknowledgment. A message sent from the MS to the BSS


to acknowledge release of radio resources when a call is being cleared.

UDP

User Datagram Protocol.

UDUB

User Determined User Busy.

UHF

Ultra High Frequency.

UI

Unnumbered Information frame.

Um

Air interface (User part modified).

UMTS

Universal Mobile Telecommunication System.

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

Vitirbi Algorithm (used in channel equalizers).

VAD

Voice Activity Detection. A process used to identify presence or absence


of speech data bits. VAD is used with DTX.

VCO

Voltage Controlled Oscillator.

VLR

Visitor Location Register. A GSM network element which provides a


temporary register for subscriber information for a visiting subscriber.
Often a part of the MSC.

VLSI

Very Large Scale Integration (in ICs).

VOX

Voice Operated Transmission.

VSP

Vehicular Speaker Phone.

VSWR

Voltage Standing Wave Ratio.

WPA

Wrong Password Attempts (counter).

WS

Work Station. The remote device via which O&M personnel execute
input and output transactions for network management purposes.

WSF

Work Station Function block.

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Glosxxxiii

Issue 12 Rev 2

X
X.25
X.25 link

A communications link which conforms to X.25 specifications and uses


X.25 protocol (NE to OMC links).

XBL

Transcoder to BSS Link. The communications link between the


Transcoder (XCDR) and the BSS.

XCB

Tranceiver Control Board (p/o tranceiver).

XCDR

Full-rate Transcoder. Provides speech transcoding and 4:1


submultiplexing (p/o BSS, BSC or XCDR).

XID

Glosxxxiv

CCITT specification and protocols for public packet-switched networks


(see PSPDN).

Exchange Identifier.

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Answers

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Answers1

Issue 12 Rev 2

Answers2

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Answers Site configuration Exercise Number 1

#
#

BSC SITE 0
LOAD 1.6.0.0 (GSR4)

chg_element bsc_type 1 0
chg_element gproc_slots 16 0

equip bsc SITE


0
chg_element fm_site_type 1 0
equip 0 CAB
0
5
1
equip 0 CAGE
0
0
<CR>
<CR>
0
yes
equip 0 CAGE
1
0
0
<CR>
0
no

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Answers3

Issue 12 Rev 2

Answers4

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Issue 12 Rev 2

Answers Site configuration Exercise Number 2

#
#

BTS SITE 12
LOAD 1.5.1.0 (GSR3)

equip bsc SITE


12
LCF
2
64
No
equip 12 CAB
0
11
2
equip 12 CAB
1
13
4

EMOTOROLA LTD. 2001

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

C2 Reselection Exercise

Issue 12 Rev 2

Working Area

SERVING (working out C1 first)


A=

Rxlev Av

P1

(P1= rxlev_access_min= (90) dBm)

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

(P1= rxlev_access_min= (90) 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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Answers7

Issue 12 Rev 2

C2 Reselection Exercise

Answers8

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

ADD_CELL Working Area

Issue 12 Rev 2

ADD_CELL Working Area


CELL 1

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Answers9

Issue 12 Rev 2

ADD_CELL Working Area

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

ADD_CELL Working Area...

Issue 12 Rev 2

ADD_CELL Working Area...


CELL 1

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Answers11

Issue 12 Rev 2

ADD_CELL Working Area...

link_fail=5
link_about_to_fail=4

Answers12

link_fail=5
link_about_to_fail=4

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

ADD_CELL Working Area...

Issue 12 Rev 2

ADD_CELL Working Area...


CELL 1

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Answers13

Issue 12 Rev 2

CHANGE_ELEMENT Working Area

CHANGE_ELEMENT Working Area


CELL 1

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Equipage Exercise Answers

Issue 12 Rev 2

Equipage Exercise Answers


equip 12 KSW
0
0
15
yes

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Answers15

Issue 12 Rev 2

Equipage Exercise Answers . . .

Equipage Exercise Answers . . .


equip 12 DRI
00
0
drim
15
7
<CR>
<CR>
2 3 4 0 1 10724 52
1
<CR>
1
4
equip 12 DRI
01
0
drim
15
9
<CR>
<CR>
2 3 4 0 1 10724 52
1
<CR>
1
4
equip 12 DRI
10
0
drim
15
11
<CR>
<CR>
2 3 4 0 1 10724 54
1
<CR>
1
4
Answers16

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

Equipage Exercise Answers . . .

Issue 12 Rev 2

Equipage Exercise Answers . . .


equip 12 RTF
bcch
00
0
1
2 3 4 0 1 10724 52
48
255 255 255 255 255 255 255 255
3 3 3 3 3 3 3 3
0

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

EMOTOROLA LTD. 2001

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

Answers17

Issue 12 Rev 2

Path Equipage Exercise Answers

Path Equipage Exercise Answers


equip< 0 >PATH

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

SYS02 GSR5/AGSR: BSS Database


FOR TRAINING PURPOSES ONLY THIS MANUAL WILL
NOT BE UPDATED

EMOTOROLA LTD. 2001

You might also like