V17.0 BSS (Access) Parameters User Guide - bPUG

V17.
0 BSS Parameter User Guide (BPUG)

Document number: PE/DCL/DD/000036
Document issue: 17.03 / EN
Document status: Standard
Date: 03/03/2008
External document
Copyright© 2008 Nortel Networks, All Rights Reserved
Printed in France
NORTEL CONFIDENTIAL
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in
writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential
and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for
evaluation, operation and maintenance purposes only.
The content of this document is provided for information purposes only and is subject to modification. It does not
constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information
contained herein, including but not limited to the suitability and performances of the product or its intended
application.
This is the Way. This is Nortel, Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All
other trademarks are the property of their owners.
V17.0 BSS Parameter User Guide (BPUG)
PUBLICATION HISTORY
System release: GSM/BSS V17
March 2008
Issue 17.03/EN
Update for v17 Channel Readiness.
Update of Enhanced Measurement Reporting Parameters (§4.8.24); update of GSM to UMTS
handovers parameters (§4.5.8); clarification on msTxPwrMax2ndBand on Power Control
Parameters section (§ 5.16)
October 2007
Issue 17.02/EN
Update for v17 Customer Readiness.
Update of GSM to UMTS handover with normal measurement reporting (§4.8.24); update of
legacy measurement reporting to include UTRAN neighbours (§4.5.8); update of reporting
priority criteria used in EMR (§4.6.5); summary of differences between MR and EMR (§4.6.8);
new section on eMLPP Preemption (§4.12); clarification of types of TDMA priorities (§6.27.2);
new recommendation for trafficPCMAllocationPriority; new range for hoMarginBeg;
clarification of bscHopReconfUse; diversity mandatory for ICA (§4.18); end of support of PCM
Error Correction (§4.20); list of Railway parameters (§3.3); update of handover decision table
for AMR TCH (§4.8.4); clarification of Downlink DTX activation (§4.11.10).
July 2007
Issue 17.01/EN
Update for v17 Business Readiness + 21 weeks:
Legacy measurement report (§4.5); Enhanced Measurement Report (§4.6); Downlink FER
(§4.6.11); GSM to UMTS Handover (§4.8.24, §7.7); Single BCCH Multizone Enhancement
(§4.8.2, §4.8.6, §4.10.6, §6.30); AMR-HR on preempted pDTCH (§4.25.6, impact on AboT
§4.25.8); A5/3 Encryption (§4.30); Smart BTS Power management (§4.31); Novel adaptive
receiver (§4.29); BSS CS Paging Coordination (§4.13.8); H3 impact on BTS cabinet power
setting (§4.16); new recommended values for modeModifyMandatory (§5.18); addition of
RxQual criteria for interzone handovers (§4.8.6); removal of reference to gsmProtocol in ICA
(§5.30); Sysinfo broadcast cycle (§4.17.3).
Nortel confidential
PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 2/629

March 2007
Issue 16.04/EN
Update for V16 ChR + 8 Weeks: Update of Network Synchronization (§ 4.34); Update of TX
Power Offset for signalling Channels parameters (§ 5.34); Update of network Synchronization
Impacts (§ 6.36); Addition of Network Synchronization Engineering planning (§ 6.37) and
Network Synchronization First Trial Results (§ 6.38)
November 2006
Issue 16.03/EN
Update for V16 ChR after review: Update of CellAllocation (§ 5.21); update PCM error
correction (§ 4.17.3); update of AMR based on traffic parameters (§ 5.34)
October 2006
Issue 16.02/EN
Update for V16 ChR: Update of TEPMOS for AMR and not EFR calls (§ 6.32.2 and § 6.32.6)
I Multipaging command message (§ 4.10.5); UI Multipaging command message (§ 4.10.6);
Tx Power Offset for signalling Channels (§ 4.23.9); update coderPoolConfiguration (§ 5.34);
update PCM error correction (§ 4.17.3); update rescue Handover (§ 4.6.1) and PBGT formula
(§ 4.5.1); PCM priority (§ 6.27.5); update Cabinet power description (§ 4.13.1)
May 2006
Issue 16.01/EN
Update for V16 CuR: 6.16 Frequency Spacing Between Two TRXs of the Same Area
March 2006
Issue 16.0/EN
Update for V16. CuR: Repeated Downlink FACCH (§ 4.23.8); Tx Power Offset for signalling
Channels (§ 4.23.9); Directed Retry Handover and queuing (§ 4.5.5, § 4.23.5 removed from
WPS description); updates on CellAllocation and mobileAllocation description (§ 5.21);updates
on AMR mechanism (§ 4.23.2, §4.23.4);updates on TCH allocation management (§ 4.9.1,
§4.9.2); updates on interference cancellation (§ 4.15, 6.22); update on lRxQualDLH and
lRxQualULH description (§ 5.10);update on dARPPh1Priority description (§ 5.36); update
coderPoolConfiguration (§ 5.34); update on extended cell description (§ 5.12)
Nortel confidential

October 2005
Issue 15.10/EN
Update for V15.1.1 CuR: AMR based on traffic (§ 4.22.7, § 6.35); AMR improvements (amr
adaptation table : § 4.22.2, § 4.22.3, § 6.32.3, § 5.34); Network Synchronization (§ 3.2.46, §
4.25, § 5.36, § 6.36); Automatic Handover Adaptation (§ 4.5.22 frequency hopping, §6.33.2
Fine Tuning); NMO I (§ 4.9.5, § 5.37); list of possible dual band network (§ 6.20.3); update of
cell models (§ 6.27.4); update on concentricCell with HePA (§ 4.5.6 and § 5.16
bizonePowerOffset and concentricCell, § 6.6.1 bizonePowerOffset, § 6.6.2
ZoneTxPowerMaxReduction); update CellAllocation and mobileAllocation description (§ 5.21)
September 2005
Issue 15.09/EN
Update for V15.1 ChR + 8 weeks: overhaul of Concentric Cell matter (§ 4.5.6
Concentric/DualCoupling/DualBand Cell Handover, § 5.16 Concentric Cell Parameters and §
6.6 Concentric Cell) and Microcell matter (§ 6.21 Microcell Benefits) based on recent field
feedback, add of a guideline for traffic HO (§ 6.34 Handover for traffic reasons activation
guideline), update on the appendix B: Erlang table, add of § 4.5.10 Ad-Hoc Frequency plan,
update on amrReserved2 and uMTSAccessMinLevel parameters.
July 2005
Issue 15.08/EN
Update for V15.1 ChR: add of Satellite Abis Interface description, Automatic Handover
Adpatation field field feedback
March 2005
Issue 15.07/EN
Update for V15.1 CuR: update of existing features on BSC12000 (Automatic Handover
Adaptation, support of S18000, configure sending SI2Quater & SI13 on NORM or EXT
BCCH), update on Cell Group Management and Load Balancing, Changed
microCellCaptureTimer parameter range of values
April 2005
Issue 15.06/EN
Update for V15.0.1 ChR: correction for noOfBlocksForAccessGrant parameter (it is greater
than zero if the SysInfo 2Q and/or SysInfo 13 on extended BCCH features are activated)
November 2004
Issue 15.05/EN
Update for V15.0.1 CuR: AMR field feedback and GSM products update
Nortel confidential

September 2004
Issue 15.04/EN
Update for V15.0 ChR
June 2004
Issue 15.03/EN
Update for AMR
December 2003
Issue 15.00/EN
Update for Wireless Priority Service
June 2004
Issue 14.05/EN
Update for AMR
December 2003
Issue 14.04/EN
Update for V14.3 ChR
December 2002
Issue 14.03/EN
September 2002
Issue 14.02/EN
Update with V14
September 2002
Issue 13.02/EN
Update with V13
Nortel confidential

May 2001
Issue 12.02/EN
Update with V12 (Chapters 1 to 4 except the counters and GSM fields in Chapter 3
“Algorithms Parameters”).
January 2000
Issue 12.01/EN
Modifications after Review.
Nortel confidential

CONTENTS
1. ABOUT THIS DOCUMENT .........................................................................................................16
1.1. OBJECT ..................................................................................................................................16

1.2. SCOPE ...................................................................................................................................16
1.3. AUDIENCE FOR THIS DOCUMENT ..............................................................................................16
1.4. DISCLAIMER ...........................................................................................................................16
1.5. DOCUMENT STRUCTURE ..........................................................................................................17
1.6. UPDATES TO PREVIOUS RECOMMENDATIONS ............................................................................18
1.6.1 between V16 and V17...................................................................................................18
1.6.2 between V15.1.1 and V16.............................................................................................18
1.6.3 between V15.1 and V15.1.1..........................................................................................19
1.6.4 between V15.0 and V15.1.............................................................................................20
2. RELATED DOCUMENTS ............................................................................................................22
2.1. APPLICABLE DOCUMENTS ........................................................................................................22

2.2. REFERENCE DOCUMENTS .......................................................................................................22
3. CLASSIFICATION OF BSS PARAMETERS ..............................................................................25
3.1. PARAMETER LIST ....................................................................................................................25

3.2. GSM UNUSED PARAMETERS ....................................................................................................34
3.3. RAILWAY-SPECIFIC PARAMETERS (GSM-R)..............................................................................34
3.4. PARAMETERS VERSUS BSS FEATURES AND PROCEDURES .......................................................36
3.4.1 2G Cell Selection and Reselection ...............................................................................36
3.4.2 2G-3G Cell Reselection ................................................................................................36
3.4.3 Legacy Measurement Reporting ...................................................................................36
3.4.4 Enhanced Measurement Reporting ..............................................................................36
3.4.5 Level averaging.............................................................................................................36
3.4.6 Quality averaging ..........................................................................................................36
3.4.7 Distance averaging .......................................................................................................36
3.4.8 Cell eligibility..................................................................................................................36
3.4.9 Radio Link Failure .........................................................................................................37
3.4.10 Interference management .............................................................................................37
3.4.11 PCH and RACH control parameters .............................................................................37
3.4.12 Concentric Cell ..............................................................................................................37
3.4.13 Extended cell.................................................................................................................37
3.4.14 Queuing and priority management................................................................................37
3.4.15 eMLPP Preemption .......................................................................................................37
3.4.16 SMS-CB ........................................................................................................................37
3.4.17 Frequency Hopping.......................................................................................................37
3.4.18 Dynamic barring of access class ..................................................................................38
3.4.19 DTX ...............................................................................................................................38
3.4.20 Uplink Power control .....................................................................................................38
3.4.21 Downlink Power control.................................................................................................38
3.4.22 Directed retry handover.................................................................................................38
3.4.23 Uplink intracell handover...............................................................................................38
3.4.24 Downlink intracell handover ..........................................................................................38
3.4.25 Intercell handover on bad uplink quality criterion..........................................................38
3.4.26 Intercell handover on bad downlink quality criterion .....................................................38
3.4.27 Intercell handover on bad uplink level criterion.............................................................39
3.4.28 Intercell handover on bad downlink level criterion ........................................................39
3.4.29 Intercell handover on power budget criterion................................................................39
Nortel confidential

3.4.30 Microcellular algorithm ..................................................................................................39

3.4.31 Intercell handover on distance criterion ........................................................................39
3.4.32 Handover for traffic reasons..........................................................................................39
3.4.33 Handover decision according to adjacent cell (V12).....................................................39
3.4.34 General protection against HO PingPong.....................................................................39
3.4.35 Call clearing...................................................................................................................39
3.4.36 Frequency Band favouring ............................................................................................39
3.4.37 Minimum Time between Handover (before V12) ..........................................................40
3.4.38 Radio resource control at cell level ...............................................................................40
3.4.39 Pre-synchronised Handover..........................................................................................40
3.4.40 Interferer cancellation....................................................................................................40
3.4.41 Early HO decision .........................................................................................................40
3.4.42 Maximum RxLev for PBGT ...........................................................................................40
3.4.43 Cell Tiering ....................................................................................................................40
3.4.44 TTY support on BSC/TCU 3000....................................................................................40
3.4.45 Protection against intracell HO Ping-pong ....................................................................40
3.4.46 Automatic Handover adaptation....................................................................................40
3.4.47 GSM to UMTS Handover ..............................................................................................41
3.4.48 Adaptative Full/Half Rate ..............................................................................................41
3.4.49 Wireless Priority Service ...............................................................................................41
3.4.50 Network Synchronization ..............................................................................................41
3.4.51 Repeated Downlink FACCH..........................................................................................41
3.4.52 Tx Power Offset for Signalling.......................................................................................41
3.4.53 Novel adaptive Receiver ...............................................................................................41
3.4.54 A5/3 Encryption Algorithm.............................................................................................42
3.4.55 BTS Smart Power Management ...................................................................................42
4. ALGORITHMS .............................................................................................................................43
4.1. INTRODUCTION .......................................................................................................................43

4.2. CONVENTIONS AND UNITS .......................................................................................................43
4.2.1 Unit ................................................................................................................................43
4.2.2 Phase 2 BTS and MS maximum transmitting output powers .......................................44
4.2.3 GSM Products sensitivity and power ............................................................................46
4.2.4 Conversion rules ...........................................................................................................47
4.2.5 Accuracy related to measurements ..............................................................................47
4.2.6 Frequency band ............................................................................................................48
4.3. 2G CELL SELECTION AND RESELECTION ..................................................................................49
4.3.1 Overview .......................................................................................................................49
4.3.2 Selection or reselection between cells of current Location Area ..................................50
4.3.3 Reselection to a cell of a different Location Area..........................................................50
4.3.4 Additional reselection criterion (for phase 2).................................................................50
4.4. 2G - 3G CELL RESELECTION ...................................................................................................54
4.4.1 UE algorithm in GSM circuit mode................................................................................54
4.4.2 3G neighbouring cell information in SI2quater..............................................................55
4.4.3 Control Information in SI2Quater ..................................................................................56
4.5. LEGACY MEASUREMENT REPORTING .......................................................................................57
4.5.1 Principle.........................................................................................................................57
4.5.2 Neighbour cell Monitoring .............................................................................................57
4.5.3 Serving cell monitoring..................................................................................................58
4.5.4 Reporting Period ...........................................................................................................58
4.5.5 Neighbour Cell Lists ......................................................................................................58
4.5.6 Measurement Report Content.......................................................................................59
4.5.7 Multiband reporting (V10)..............................................................................................60
4.5.8 UTRAN cell reporting using legacy measurement reports (V17)..................................60
4.5.9 Note on powerControlIndicator parameter....................................................................63
Nortel confidential

4.5.10 Note on Rxlev Uplink/Downlink difference ....................................................................64

4.6. ENHANCED MEASUREMENT REPORTING (EMR) .......................................................................65
4.6.1 Principle.........................................................................................................................65
4.6.2 Reporting period............................................................................................................65
4.6.3 Enhanced Measurement Report content ......................................................................65
4.6.4 Neighbour Cell lists .......................................................................................................66
4.6.5 Order of reporting priority of neighbour cells.................................................................67
4.6.6 Measurement Information message .............................................................................67
4.6.7 MI/SACCH scheduling ..................................................................................................69
4.6.8 Main differences between Normal and Enhanced Measurement Reporting ................70
4.6.9 New BSS parameters....................................................................................................70
4.6.10 Impact of EMR on Interference Matrix ..........................................................................71
4.6.11 Impact of EMR on Radio Measurement Distribution (RMD) .........................................72
4.7. UPLINK MEASUREMENT PROCESSING ......................................................................................73
4.7.1 Principle.........................................................................................................................73
4.7.2 Averaging process ........................................................................................................74
4.7.3 Rescaling.......................................................................................................................75
4.7.4 Missing downlink measurements ..................................................................................75
4.8. DIRECT TCH ALLOCATION AND HANDOVER ALGORITHMS .........................................................78
4.8.1 General formulas...........................................................................................................78
4.8.2 Direct TCH Allocation....................................................................................................81
4.8.3 Handovers .....................................................................................................................85
4.8.4 Handovers decision priority...........................................................................................87
4.8.5 Directed Retry Handover...............................................................................................89
4.8.6 Concentric/DualCoupling/DualBand Cell Handover .....................................................92
4.8.7 Rescue Handover .........................................................................................................98
4.8.8 Power Budget Handover ............................................................................................ 100
4.8.9 Handover for traffic reasons (from V12)..................................................................... 100
4.8.10 Handover decision according to adjacent cell priorities and load (from V12)............ 103
4.8.11 Automatic cell tiering (from V12) ................................................................................ 104
4.8.12 Microcellular Handover .............................................................................................. 109
4.8.13 Forced Handover ....................................................................................................... 112
4.8.14 Early HandOver Decision........................................................................................... 113
4.8.15 Maximum RxLev for Power Budget ........................................................................... 114
4.8.16 Pre-synchronized HO................................................................................................. 115
4.8.17 Radio channel allocation ............................................................................................ 115
4.8.18 Define eligible neighbor cells for intercell handover (except directed retry) .............. 116
4.8.19 Handover to 2nd best candidate when return to old channel .................................... 117
4.8.20 Protection against RunHandover=1 ........................................................................... 117
4.8.21 General protection against HO ping-pong (from V12) ............................................... 118
4.8.22 Automatic handover adaptation ................................................................................. 120
4.8.23 Protection against Intracell HO Ping-Pong ................................................................ 123
4.8.24 GSM to UMTS handover............................................................................................ 126
4.9. HANDOVER ALGORITHMS ON THE MOBILE SIDE ..................................................................... 137
4.10. POWER CONTROL ALGORITHMS ........................................................................................... 138
4.10.1 Step by step Power Control ....................................................................................... 138
4.10.2 One shot Power Control............................................................................................. 139
4.10.3 Fast Power Control at TCH assignment .................................................................... 141
4.10.4 Power Control on mobile side .................................................................................... 142
4.10.5 AMR Power Control ................................................................................................... 142
4.10.6 Power adaptation after an interzone ho ..................................................................... 143
4.11. TCH ALLOCATION MANAGEMENT ......................................................................................... 146
4.11.1 TCH Allocation and Priority ........................................................................................ 146
4.11.2 Queuing...................................................................................................................... 150
Nortel confidential

4.11.3 Barring of access class .............................................................................................. 154

4.11.4 Radio link failure process (run by the MS) ................................................................. 159
4.11.5 Radio link failure process (run by the BTS) ............................................................... 159
4.11.6 Call reestablishment procedure ................................................................................. 160
4.11.7 Call Clearing Process (run by BTS) ........................................................................... 161
4.11.8 Interference Management (BTS and BSC) ................................................................ 161
4.11.9 Uplink DTX ................................................................................................................. 161
4.11.10 Downlink DTX......................................................................................................... 163
4.12. EMLPP PREEMPTION .......................................................................................................... 165
4.12.1 Principle of eMLPP..................................................................................................... 165
4.12.2 End-to-end perspective .............................................................................................. 166
4.12.3 Preemption attributes ................................................................................................. 168
4.12.4 BSS Radio Resource preemption algorithm .............................................................. 169
4.12.5 Activation parameter .................................................................................................. 172
4.12.6 eMLPP preemption versus PDTCH preemption ........................................................ 172
4.12.7 Interworking................................................................................................................ 173
4.12.8 Restrictions................................................................................................................. 174
4.13. PCH AND RACH CHANNEL CONTROL ................................................................................... 175
4.13.1 Paging command Process ......................................................................................... 175
4.13.2 Paging command repetition process (run by BTS) .................................................... 177
4.13.3 Request access command process ........................................................................... 179
4.13.4 Request access command repetition process ........................................................... 179
4.13.5 I Multipaging command message .............................................................................. 180
4.13.6 UI Multipaging command message............................................................................ 182
4.13.7 Network Mode of Operation I support in BSS ............................................................ 184
4.13.8 BSS CS Paging Coordination .................................................................................... 186
4.14. FREQUENCY HOPPING ......................................................................................................... 188
4.14.1 Frequency hopping principles .................................................................................... 188
4.14.2 Main benefits of frequency hopping ........................................................................... 189
4.14.3 Synthesised frequency hopping................................................................................. 191
4.14.4 Baseband frequency Hopping.................................................................................... 192
4.14.5 Ad-Hoc frequency plan............................................................................................... 194
4.15. BSC OVERLOAD MANAGEMENT MECHANISMS....................................................................... 195
4.15.1 BSC12000 Overload Management ............................................................................ 195
4.15.2 BSC3000 Overload Management .............................................................................. 198
4.15.3 Load Balancing .......................................................................................................... 200
4.15.4 V15.1 Evolution of Load Balancing ............................................................................ 200
4.16. CABINET OUTPUT POWER SETTING ...................................................................................... 202
4.16.1 Cabinet power description.......................................................................................... 202
4.16.2 Pr computation ........................................................................................................... 203
4.16.3 Ps computation .......................................................................................................... 205
4.17. SYSTEM INFORMATION MESSAGES RELATED FEATURES ........................................................ 207
4.17.1 Dual Band Handling ................................................................................................... 207
4.17.2 SI2Quater & SI13 on Extended or Normal BCCH...................................................... 210
4.17.3 Summary of SYSINFO Scheduling ............................................................................ 211
4.18. INTERFERENCE CANCELLATION ............................................................................................ 213
4.19. EXTENDED CCCH ............................................................................................................... 215
4.19.1 Customer/service provider benefits ........................................................................... 215
4.19.2 Feature functional description .................................................................................... 215
4.20. PCM ERROR CORRECTION .................................................................................................. 216
4.20.1 Feature principle ........................................................................................................ 216
Nortel confidential

4.20.2 Feature benefits ......................................................................................................... 217

4.20.3 Feature activation....................................................................................................... 217
4.21. CELLULAR TELEPHONE TEXT MODEM (TTY) ......................................................................... 218
4.21.1 TTY principle .............................................................................................................. 218
4.21.2 TTY impact ................................................................................................................. 219
4.22. LOCATION SERVICES............................................................................................................ 221
4.22.1 Principle...................................................................................................................... 221
4.22.2 Performances ............................................................................................................. 221
4.23. SMS-CELL BROADCAST....................................................................................................... 222
4.23.1 Principle...................................................................................................................... 222
4.23.2 Performances ............................................................................................................. 223
4.24. BSC/TCU 3000 INTRODUCTION ........................................................................................... 225
4.25. AMR - ADAPTATIVE MULTI RATE FR/HR .............................................................................. 226
4.25.1 Basics and specific terminology................................................................................. 226
4.25.2 AMR mechanisms ...................................................................................................... 228
4.25.3 Traffic Management mechanisms.............................................................................. 231
4.25.4 AMR L1m ................................................................................................................... 235
4.25.5 Legacy L1M................................................................................................................ 245
4.25.6 pDTCH Preemption by AMR FR or HR calls ............................................................. 245
4.25.7 Engineering rules ....................................................................................................... 247
4.25.8 AMR based on traffic.................................................................................................. 249
4.25.9 Repeated Downlink FACCH....................................................................................... 254
4.25.10 Tx Power Offset for Signaling Channels ................................................................ 257
4.26. WPS - WIRELESS PRIORITY SERVICE ................................................................................... 262
4.26.1 Principle...................................................................................................................... 262
4.26.2 WPS – Queuing management ................................................................................... 262
4.26.3 WPS – Access class barring with class periodic rotation .......................................... 265
4.26.4 WPS – Public access bandwith protection................................................................. 266
4.27. SATELLITE ABIS INTERFACE .................................................................................................. 268
4.27.1 Principle...................................................................................................................... 268
4.27.3 Feature Interworking .................................................................................................. 269
4.28. NETWORK SYNCHRONIZATION .............................................................................................. 270
4.28.1 Global description ...................................................................................................... 270
4.28.3 Feature impacts expectations .................................................................................... 273
4.29. NOVEL ADAPTIVE RECEIVER................................................................................................. 274
4.29.1 Principle...................................................................................................................... 274
4.29.2 HW/SW dependence.................................................................................................. 274
4.29.3 Activation Guidelines.................................................................................................. 274
4.30. A5/3 ENCRYPTION ALGORITHM ............................................................................................. 276
4.30.1 Principle...................................................................................................................... 276
4.30.2 Hardware dependence............................................................................................... 276
4.30.3 Ciphering activation rules........................................................................................... 276
4.30.4 Performance impact ................................................................................................... 278
4.31. BTS SMART POWER MANAGEMENT ...................................................................................... 279
4.31.1 Definitions................................................................................................................... 279
4.31.2 Principle...................................................................................................................... 279
4.31.3 Pre V17 Behaviour ..................................................................................................... 279
Nortel confidential

4.31.4 Post V17 Behaviour ................................................................................................... 280

4.31.5 Hardware dependence............................................................................................... 281
4.31.6 Activation Guidelines.................................................................................................. 281
5. ALGORITHM PARAMETERS .................................................................................................. 284
5.1. INTRODUCTION .................................................................................................................... 284

5.2. 2G CELL SELECTION AND RESELECTION PARAMETERS .......................................................... 285
5.3. 2G-3G CELL RESELECTION PARAMETERS ............................................................................. 290
5.4. LEGACY MEASUREMENT REPORTING PARAMETERS ............................................................... 292
5.5. ENHANCED MEASUREMENT REPORTING PARAMETERS .......................................................... 293
5.6. RADIO LINK FAILURE PARAMETERS ....................................................................................... 297
5.7. SIGNAL QUALITY AVERAGING PARAMETERS .......................................................................... 300
5.8. SIGNAL STRENGTH AVERAGING PARAMETERS....................................................................... 302
5.9. NEIGHBOR CELL AVERAGING PARAMETERS .......................................................................... 305
5.10. DISTANCE AVERAGING PARAMETERS .................................................................................... 307
5.11. HANDOVER (GLOBAL) PARAMETERS ..................................................................................... 309
5.12. INTRACELL HANDOVER PARAMETERS.................................................................................... 322
5.13. INTERCELL HANDOVER THRESHOLD PARAMETERS ................................................................ 325
5.14. HANDOVER FOR MICROCELLULAR NETWORK PARAMETERS ................................................... 329
5.15. DISTANCE MANAGEMENT PARAMETERS ................................................................................ 331
5.16. POWER CONTROL PARAMETERS........................................................................................... 335
5.17. TCH ALLOCATION MANAGEMENT PARAMETERS .................................................................... 343
5.18. EMLPP RADIO RESOURCE PREEMPTION PARAMETER ........................................................... 357
5.19. DIRECTED RETRY HANDOVER PARAMETERS ......................................................................... 358
5.20. CONCENTRIC CELL PARAMETERS ......................................................................................... 362
5.21. INTERFERENCE LEVEL PARAMETERS .................................................................................... 370
5.22. RADIO RESSOURCES CONTROL AT CELL LEVEL .................................................................... 373
5.23. BSS TIMERS ....................................................................................................................... 374
5.24. PAGING PARAMETERS .......................................................................................................... 381
5.25. FREQUENCY HOPPING PARAMETERS .................................................................................... 386
5.26. BSC LOAD MANAGEMENT PARAMETERS ............................................................................... 393
5.27. DUALBAND CELL PARAMETERS ............................................................................................ 394
5.28. DTX PARAMETERS .............................................................................................................. 401
5.29. MISCELLANEOUS ................................................................................................................. 402
5.30. INTERFERENCE CANCELLATION PARAMETERS ....................................................................... 405
5.31. PCM ERROR CORRECTION PARAMETERS ............................................................................. 407
5.32. CELL TIERING PARAMETERS ................................................................................................. 408
5.33. ENCODING PARAMETERS ..................................................................................................... 411
5.34. SMS-CELL BROADCAST PARAMETERS ................................................................................. 412
5.35. PROTECTION AGAINST INTRACELL HO PING-PONG PARAMETERS .......................................... 413
5.36. AUTOMATIC HANDOVER ADAPTATION PARAMETERS .............................................................. 414
5.37. GSM TO UMTS HANDOVER PARAMETERS............................................................................. 416
5.38. AMR - ADAPTATIVE MULTI RATE FR/HR PARAMETERS ......................................................... 424
5.39. WPS - WIRELESS PRIORITY SERVICES PARAMETERS ............................................................ 442
5.40. NETWORK SYNCHRONIZATION PARAMETERS ......................................................................... 443
5.41. NETWORK MODE OF OPERATION PARAMETERS ..................................................................... 445
5.42. BSS CS PAGING COORDINATION PARAMETER ...................................................................... 445
5.43. NOVEL ADAPTIVE RECEIVER PARAMETER .............................................................................. 446
5.44. A5/3 ENCRYPTION ALGORITHM PARAMETERS ........................................................................ 447
5.45. BTS SMART POWER MANAGEMENT PARAMETERS................................................................. 450
6. ENGINEERING ISSUES........................................................................................................... 451
6.1. GSM/GPRS TS SHARING: PRIORITY HANDLING AND QUEUING ............................................. 451

6.1.1 Resources reserved for priority 0 and preemption..................................................... 451
6.1.2 GSM/GPRS TS sharing and queuing: ....................................................................... 452
6.1.3 Resources strategy .................................................................................................... 453
Nortel confidential

6.2. LAYER 1 MANAGEMENT: CHANGES BETWEEN V1 AND V2 ...................................................... 454

6.2.1 Main differences......................................................................................................... 454
6.2.2 Benefit ........................................................................................................................ 462
6.2.3 Change in Handover performance after L1mV2 implementation............................... 462
6.3. ONE-SHOT POWER CONTROL .............................................................................................. 463
6.4. MINIMUM TIME BETWEEN HANDOVER.................................................................................... 464
6.4.1 Micro-cellular network ................................................................................................ 464
6.4.2 Non micro-cellular network......................................................................................... 466
6.5. DIRECTED RETRY HANDOVER BENEFIT ................................................................................. 467
6.5.1 Benefit of feature on mono-layer structure................................................................. 467
6.5.2 Benefit of feature on multi-layers structure ................................................................ 468
6.6. CONCENTRIC CELLS ............................................................................................................ 471
6.6.1 Concentric Cell Parameter Definition......................................................................... 472
6.6.2 Concentric Cell Field Experience ............................................................................... 475
6.7. IMPACT OF DTX ON AVERAGING ........................................................................................... 479
6.8. BEST NEIGHBOUR CELLS STABILITY ..................................................................................... 480
6.9. TCH ALLOCATION GENERAL RULES ..................................................................................... 481
6.10. GENERAL RADIO FREQUENCY RULES ................................................................................... 482
6.11. DIFFERENCE BETWEEN UPLINK AND DOWNLINK LEVELS ........................................................ 483
6.12. EFFECTS OF “NOOFMULTIFRAMESBETWEENPAGING” ON MOBILE BATTERIES AND RESELECTION
REACTIVITY ...................................................................................................................................... 484
6.13. EFFECTS OF SMS-CELL BROADCAST USE ON “NOOFBLOCKSFORACCESSGRANT”................. 486
6.14. IMPACT OF THE AVERAGING ON THE HANDOVERS .................................................................. 487
6.14.1 Global statistics .......................................................................................................... 487
6.14.2 Study of reactivity....................................................................................................... 488
6.14.3 Ping pong vs Reactivity.............................................................................................. 488
6.15. IMPACT OF CALL RE-ESTABLISHMENT ON THE NETWORK ....................................................... 489
6.15.1 Impact on capacity ..................................................................................................... 489
6.15.2 Impact on call drops ................................................................................................... 489
6.16. FREQUENCY SPACING BETWEEN TWO TRXS OF THE SAME AREA .......................................... 490
6.16.1 Intra_cell..................................................................................................................... 490
6.16.2 Intra_site..................................................................................................................... 490
6.16.3 Inter_site..................................................................................................................... 490
6.17. LINK BUDGET (LB)............................................................................................................... 491
6.17.1 Gains and losses........................................................................................................ 491
6.17.2 Designs margins ........................................................................................................ 492
6.17.3 Environmental factors margins................................................................................... 492
6.17.4 Link budget balance or disbalance (∆)....................................................................... 493
6.18. MINIMUM COUPLING LOSS (MCL)......................................................................................... 495
6.18.1 Broadband noise ........................................................................................................ 495
6.18.2 Blocking...................................................................................................................... 495
6.18.3 How to improve the MCL............................................................................................ 496
6.19. GENERAL RULES FOR SYNTHESISED FREQUENCY HOPPING .................................................. 497
6.19.1 Nortel choice between Baseband and Synthesised Frequency hopping .................. 497
6.19.2 Fractional load............................................................................................................ 499
6.19.3 Maximum TRX configuration (homogeneous sites of configuration Sxxx) ................ 500
6.19.4 SFH parameter setting for 1X1 pattern: strategy 1 .................................................... 501
6.19.5 SFH parameter setting for 1X3 pattern: Strategy 2 ................................................... 506
6.20. DUALBAND NETWORKS ........................................................................................................ 512
Nortel confidential

6.20.1 Frequency band favouring ......................................................................................... 512

6.20.2 Frequency band defavouring ..................................................................................... 514
6.20.3 Possible dualband network ........................................................................................ 515
6.21. MICROCELL BENEFITS .......................................................................................................... 516
6.21.1 Frequency super reuse .............................................................................................. 516
6.21.2 Traffic Homogenization .............................................................................................. 516
6.21.3 Radio conditions improvement................................................................................... 516
6.21.4 Microcell Field Experience ......................................................................................... 517
6.22. INTERFERENCE CANCELLATION USAGE ................................................................................. 518
6.23. SET UP PRINCIPLES OF A NEIGHBORING LIST AND A BCC PLAN ............................................. 519
6.23.1 Introduction................................................................................................................. 519
6.23.2 4/12 reuses pattern .................................................................................................... 519
6.23.3 1X3 and 1X1 Fractional reuse pattern specific case ................................................. 521
6.23.4 Set-up principles of a BSIC plan ................................................................................ 523
6.24. STREET CORNER ENVIRONMENT .......................................................................................... 524
6.24.1 Description ................................................................................................................. 524
6.24.2 Case A: Mobile moving straight ................................................................................. 525
6.24.3 Case B: Mobile turning at the cross road................................................................... 526
6.25. SYNCHRONIZED HO VERSUS NOT SYNCHRONIZED HO .......................................................... 527
6.25.1 Introduction................................................................................................................. 527
6.25.2 OMC-R Parameter settings........................................................................................ 527
6.25.3 Timing HO .................................................................................................................. 528
6.26. BTS SENSITIVITY ................................................................................................................. 532
6.26.1 Definition of sensitivity................................................................................................ 532
6.26.2 Static and dynamic sensitivity .................................................................................... 533
6.26.3 Typical / guaranteed sensitivity .................................................................................. 533
6.26.4 Space diversity gains ................................................................................................. 533
6.26.5 Cross-polarization antenna use ................................................................................. 534
6.26.6 Circular polarization and crosspolar antennas........................................................... 535
6.27. SDCCH DIMENSIONING AND TDMA PRIORITIES .................................................................... 537
6.27.1 SDCCH Dimensioning................................................................................................ 537
6.27.2 TDMA priorities .......................................................................................................... 538
6.28. ENGINEERING GUIDELINES FOR EXCEPTIONAL EVENTS .......................................................... 540
6.28.1 BSS prerequisite ........................................................................................................ 540
6.28.2 BSS: Suggestions for parameters to be modified for the special event .................... 541
6.28.3 NSS level.................................................................................................................... 542
6.29. ENGINEERING LIMITS WITH BSC OVERLOAD CONTROL MECHANISM ....................................... 545
6.29.1 “CPU Engineering limit” meaning............................................................................... 545
6.29.2 “CPU Call Processing limit” meaning......................................................................... 546
6.30. POWER CONTROL COMPENSATION IN INTERZONE HANDOVER ................................................ 547
6.30.1 Important note ............................................................................................................ 547
6.30.2 Dualband cell ............................................................................................................. 547
6.30.3 Concentric cell............................................................................................................ 550
6.30.4 Dualcoupling cell ........................................................................................................ 550
6.31. GSM PAGING REPETITION PROCESS TUNING ....................................................................... 552
6.31.1 Paging parameters..................................................................................................... 552
6.31.2 Field examples: BSS paging repetition tuning ........................................................... 553
6.31.3 Field examples: NSS paging repetition tuning ........................................................... 554
Nortel confidential

6.32. AMR FIELD FEEDBACK ........................................................................................................ 555

6.32.1 NSS Interaction .......................................................................................................... 555
6.32.2 AMR Theoretical Performances ................................................................................. 556
6.32.3 AMR Engineering Studies .......................................................................................... 559
6.32.4 Half Rate Penetration Analysis .................................................................................. 565
6.32.5 AMR User Behaviour Effect ....................................................................................... 568
6.32.6 Voice Quality Analysis................................................................................................ 570
6.32.7 AMR Monitoring ......................................................................................................... 572
6.33. IMPACT OF AUTOMATIC HANDOVER ADAPTATION ACTIVATION ................................................. 578
6.33.1 Related parameters.................................................................................................... 578
6.33.2 Deployment Optimization and Monitoring .................................................................. 579
6.34. HANDOVER FOR TRAFFIC REASONS ACTIVATION GUIDELINE .................................................. 583
6.34.1 Algorithms and Parameters Definition ....................................................................... 583
6.34.2 Expected effects and recommended parameters ...................................................... 585
6.35. DISABLING AMR BASED ON TRAFFIC IN V15.1.1 .................................................................... 589
6.36. NETWORK SYNCHRONIZATION IMPACTS ................................................................................. 590
6.36.1 Collision Probability.................................................................................................... 590
6.36.2 TSC Impacts............................................................................................................... 592
6.36.3 FN Offset Impacts ...................................................................................................... 593
6.36.4 Interference Cancellation ........................................................................................... 595
6.37. NETWORK SYNCHRONIZATION ENGINEERING PLANNING ........................................................ 598
6.37.1 TSC Planning ............................................................................................................. 598
6.37.2 FN Offset Planning..................................................................................................... 598
6.37.3 TN Offset Planning..................................................................................................... 599
6.37.4 Synchronization Strategies ........................................................................................ 600
6.38. NETWORK SYNCHRONIZATION FIRST TRIAL RESULTS ............................................................. 601
7. APPENDIX A: MAIN EXCHANGE PROCEDURES AT BSC LEVEL...................................... 604
7.1. ESTABLISHMENT PROCEDURE .............................................................................................. 604

7.2. CHANNEL MODE PROCEDURE .............................................................................................. 605
7.3. DEDICATED CHANNEL ASSIGNMENT ...................................................................................... 606
7.4. INTRACELL HANDOVER PROCEDURE ..................................................................................... 607
7.5. INTRABSS HANDOVER PROCEDURE ..................................................................................... 608
7.6. INTERBSS HANDOVER PROCEDURE ..................................................................................... 609
7.7. 2G-3G HANDOVER PROCEDURE ........................................................................................... 610
7.8. RESOURCE RELEASE PROCEDURE (EXAMPLE)...................................................................... 611
7.9. SACCH DEACTIVATION PROCEDURE ................................................................................... 612
7.10. MOBILE TERMINATING CALL ................................................................................................. 613
7.11. MOBILE ORIGINATING CALL .................................................................................................. 614
8. APPENDIX B: ERLANG TABLE.............................................................................................. 615
9. ABBREVIATIONS & DEFINITIONS ......................................................................................... 618
9.1. ABBREVIATIONS ................................................................................................................... 618

9.2. DEFINITIONS ........................................................................................................................ 624
10. INDEX ....................................................................................................................................... 627
Nortel confidential

1. ABOUT THIS DOCUMENT
1.1. OBJECT
This document describes BSS GSM and Nortel algorithms and parameters from an
engineering point of view.
This document is written by Nortel BSS experts and contains extensive Nortel BSS
parameters setting know-how. Informations coming from experiments, studies, simulations are
also related in the document.
The parameters are called by the name used in the features and algorithms. For their
corresponding name (when different) at the OMC, refer to [R6].
The parameters described in this document are the ones used in the features and algorithms.
Refer to [R2] to have a description of all BSS parameters.
1.2. SCOPE
This version is issued for the ChR milestone of the V17 BSS GSM release.
1.3. AUDIENCE FOR THIS DOCUMENT

Draft and preliminary: Nortel R&D, PLM and Eng'
Standard: customers and Nortel R&D, Product Line Management and Engineering teams.'
1.4. DISCLAIMER
Depending on particular objective, call profile and network characteristics, a parameter setting
can never be judged as being universally optimized.
The recommended setting presented in this document should result in good network
performance; however several iterations and improvements may be required in order to be
optimal according to customer specificities. Every effort is made to incorporate suggestions
and feedback received from customers.
PRELIMINARY VERSION
The recommended setting has been validated with product and system tests in lab. This
document will be updated and adjusted after the first results from VO site or new Product
Test/End-to-end labs if available.
STANDARD VERSION
This is a living document and the contents will be modified based on feedback received from
R&D, Engineering and customers.
Nortel confidential

1.5. DOCUMENT STRUCTURE

In chapter §3 CLASSIFICATION OF BSS PARAMETERS, BSS algorithm parameters are
presented in alphabetic order according to their group. Process and related objects are also
provided.
Chapter §4 ALGORITHMS describes the GSM Nortel BSS algorithms and recommends ways
to use them efficiently.
BSS parameters used in the algorithms are described in chapter §5 ALGORITHM
PARAMETERS. For each parameter, a recommended value and a default value are given.
Engineering rules explain how to select the parameter value.
In chapter §6 ENGINEERING ISSUE, engineering issues resulting from studies on parameter
setting and on products, simulations and experiments are developped.
Chapter §7 APPENDIX A: MAIN EXCHANGE PROCEDURES AT BSC LEVEL gives the main
exchange procedures at BSC level.
In chapter §8 APPENDIX B: ERLANG TABLE, an Erlang table presents the maximum offered
load according to the number of channels and the blocking rate.
In chapter §9 ABBREVIATIONS & DEFINITIONS, the signification of all the abbrevations used
in this document and some key-definitions are explained.
Nortel confidential

1.6. UPDATES TO PREVIOUS RECOMMENDATIONS
1.6.1 BETWEEN V16 AND V17

modeModifyMandatory:
New recommended value set to “not used”. This parameter is no longer useful but setting to
“used” may yield undesirable side-effects in particular circumstances.
enhancedTRAUframeIndication :
This parameter is no longer useful in V17 due to the end of support of the PCM Error
Correction feature.
pcmErrorCorrection :
This parameter is no longer useful in V17 duie to the end of support of the PCM Error
Correction feature.
bscHopReconfUse :
New recommended value for BSC that manage only BTS with hybrid coupling.
Old recommendation : “false (mandatory for hybrid coupling).”
New recommendation : “the value (true or false) is indifferent for a BSC that manages only
BTS with hybrid coupling”.
trafficPCMAllocationPriority :
New recommended value for BCCH TDMA.
Old recommendation : highest priority (0) for BCCH TDMA.
New recommendation : lowest priority (255) for BCCH TDMA.
1.6.2 BETWEEN V15.1.1 AND V16

amrReserved1:
This new parameter was introduced to enable/disable RATSCCH procedure for AMR FR.
Recommended value set to 0 (enable RATSCCH procedure)
hrCellLoadEnd
New recommended value set to 60, instead of 5 or 10 in urban areas and 50 or 60 in rural
areas. Now the value depends on the number of DRXs on the cell.
hrCellLoadStart
New recommended value set to 80, instead of 70 or 80 in rural areas, and 20 or 30 in urban
areas. Now the value depends on the number of DRXs on the cell.
Nortel confidential

1.6.3 BETWEEN V15.1 AND V15.1.1

hrCellLoadEnd:
New recommended value set to 5 -10 in urban areas and 50 - 60 in rural areas, instead of 0
hrCellLoadStart:
New recommended value set to a fix value i.e 20-30 in urban areas and 70-80 in rural areas
instead of a value greater than 0
hoMarginTrafficOffset:
New recommended value set to 6 instead of 2; HoMarginTrafficOffset should be tune such as
the resulting margin should be equivalent to the one for rescue HO.
early classmark sending:
New recommended value set this value to Allowed even if dual band network is not used. This
parameter allows MS to send its capacity downlink Advanced Receiver performance.
Nortel confidential

1.6.4 BETWEEN V15.0 AND V15.1.

RadioLinkTimeOut:
New recommended value set to 32 instead of 20. when AMR is activated RLT drop calls
contribution is usually much higher in coverage limited or rural areas because calls are being
dragged at cell edges and the overlap between neighboring sites is less important than in
urban areas. This recommendation helps to reduce the contribution of RLT drop
Rlf1:
New recommended value set to 7 instead of 4. This new recommendation is linked to RLT one
when AMR is activated
HoMarginBeg:
New recommended value set to 2dB instead of 4 when Automatic Handover Adaptation is
activated. This new setting helps to get effective margin of 6 dB
AllocPriorityTimer:
New recommended value set to [5 0 5 5 0 0 0 0 28 28 28 28 28 28] instead of [0 0 3 0 0 0 0 0
28 28 28 28 28 28].
AllocWaitThreshold:
New recommended value set to [n 0 n n 0 0 0 0 5 5 5 5 5] instead of [0 0 n 0 0 0 0 0 5 5 5 5 5].
CallReestablishmentPriority:
New recommended value set to 15 instead of 16.
IntraCellHOIntPriority:
DirectedRetryPrio:
New recommended value set to 17 instead of no recommended value.
biZonePowerOffset:
New recommended value depends on the engineering rules, in v15.0 it was 63 dB for
monozone and 3 dB otherwise.
ConcentAlgoMsRange:
New recommended value set to 34 instead of depending on the radius of the site.
Small to large HO priority
Nortel confidential

T3103
New recommended value set to 9 seconds instead of 5. From a handover perspective it is
recommended to use 9s in order to offer a wider window of good completion of the procedure
at cell edge where the quality might be poorer.
noOfBlocksForAccessGrant
Addition of a recommended value for SI2Quater or/and SI13 on ext BCCH.
Data non transparent mode
New recommended value set to TBD instead of 9.6kb/s
Serving factor offset

New recommended value set to 0 instead of -2. It means it will actually favor the server or
disfavor in order word the neighbor greatly.
amrReserved2
New recommended values will depend of in what is base AMR alarm handovers and AMR
power control. Old value was 3.
amrFRIntercellCodecMThresh
New recommended value set to 10k2 instead of 6k7.
Nortel confidential

2. RELATED DOCUMENTS
2.1. APPLICABLE DOCUMENTS

[A1] PE/DCL/DD/000136 Access (EGPRS) Parameter User Guide
2.2. REFERENCE DOCUMENTS

[R1] PE/SYS/DD/000065 Configuration parameters for BSS
[R2] PE/DCL/DD/000007 BSS Operating Principles
[R3] PE/DCL/DD/000000 BSS Product Documentation Overview
[R4] PE/DCL/DD/0124 BSS Parameter Dictionary
[R5] PE/DCL/DD/0125 Observation Counter Dictionary
[R6] PE/MD/DD/000008 GDMO Configuration Management
[R7] PE/DCL/DD/000138 GSM/GPRS/EDGE BSS Engineering Rules
[R8] PE/BTS/DD/1514 SFS of Layer 1 Management

[R9] PE/SYS/DD/0272 TF875: Dual band cells management
[R10] PE/SYS/INF/0225 Concentric cell improvements (CM888/TF889)
[R11] PE/SYS/DD/6293 FN for stepped coupling
[R12] PE/SYS/INF/0140 Handover for traffic reasons: TF132
[R13] PE/SYS/INF/0190 Handover decision according to adjacent cell
priorities and load TF716
[R14] PE/SYS/DD/279 TF 995: Automatic Cell Tiering
[R15] PE/BTS/DD/0421 TF809: Early handover decision
[R16] PE/SYS/DD/0291 TF821: General protection against HO Ping-pong
[R17] PE/SYS/DD/0330 TF1216: Automatic handover adaptation
[R18] PE/SYS/DD/0331 TF1217: Protection against intra-cell HO Ping-
pong
[R19] PE/SYS/DD/0482 22464: WPS - Access class barring with class
periodic rotation
[R20] PE/SYS/DD/010888 27318 Configure sending of SI2Quater and SI13
on Ext or Norm BCCH
[R21] PE/SYS/INF/0242 TF184: Extended CCCH
[R22] PE/SYS/DD/0356 SV1322: TTY on BSC/TCU e3

[R23] PE/SYS/DD/0432 AR1526 - SMS-CB Usability improvement
[R24] UMT/SYS/DD/29 GSM to UMTS mobility
Nortel confidential

[R25] PE/SYS/DD343 SV713 : AMR Full Rate; SV885 AMR Half Rate
[R26] PE/SYS/DD/486 22463: WPS - Queuing management
[R27] PE/SYS/DD/487 22465 : WPS - Public access bandwidth
protection
[R28] PE/SYS/DD/005776 24394 : Directed retry without queuing activation
[R29] PE/BSS/APP/012435 AMR Engineering Handbook
[R30] PE/SYS/DD/005321 Advanced Speech Call Items Evolutions
[R31] PE/SYS/DD/0231 PM990 Satellite ABIS interface
[R32] PE/IRC/APP/014199 Satellite Abis Interface - Engineering Guideline
[R33] PE/BSS/APP/0115 Reference Manual for BSC data configuration

[R34] PE/IRC/APP/021006 Network Synchronisation Handbook
[R35] PE/SYS/DD/016451 30296 – Repeated Downlink FACCH
[R36] PE/SYS/DD/016458 30293 – Tx Offset for Signalling Channels

[R37] PE/DCL/DD/018141 Lb Interface Engineering Rules
[R38] PE/SYS/DD/012303 21531 - Enhanced Measurement Report (EMR)
[R39] PE/SYS/DD/005337 2473 - GSM to UMTS handover

[R40] PE/SYS/DD/16945 30169 - AMR-HR on preempted PDTCH
[R41] PE/SYS/DD/16359 27392 - Support of A5/3 Encryption Algorithm
[R42] PE/SYS/DD/21289 28703 - Multi-zone cell enhancement

[R43] PE/SYS/DD/11409 Distributions on Radio measurements
[R44] PE/SYS/DD/021592 34208 - BTS6k/18k Smart Power Management
[R45] PE/SYS/DD/012171 27288 - Novel Adaptive Receiver
[R46] PE/SYS/DD/019402 32280 - Joint Diversity
[R47] PE/DCL/DD/014271 BTS S2000L Engineering Rules
[R48] PE/DCL/DD/014272 BTS S2000H Engineering Rules
[R49] PE/DCL/DD/014273 BTS S4000 Outdoor Engineering Rules
[R50] PE/DCL/DD/014274 BTS S4000 Indoor Engineering Rules
[R51] PE/DCL/DD/014275 BTS eCell Engineering Rules

[R52] PE/DCL/DD/014276 BTS S8000-S8003 Indoor & S8000 Outdoor
Engineering Rules
[R53] PE/DCL/DD/014277 BTS S12000 Indoor & Outdoor Engineering

Rules
[R54] PE/DCL/DD/014278 BTS 18000 Indoor & Outdoor Engineering Rules
[R55] PE/DCL/DD/014289 BTS 18000 GSM-UMTS Indoor & Outdoor
Engineering Rules
Nortel confidential

[R56] PE/DCL/DD/018541 BTS 6000 GSM Indoor & Outdoor Engineering

Rules
[R57] PE/SYS/DD/21412 34160 - BSS Paging Coordination
[R58] PE/DCL/DD/14283 Radio Interface Engineering Rules
Nortel confidential

3. CLASSIFICATION OF BSS PARAMETERS
3.1. PARAMETER LIST

The following table gives a classification of the main BSS tunable parameters sorted by
alphabetical order, the object they are associated to at the OMC-R (as they are described in
[R1]) and the main features using those parameters.
Parameter name BSS Object- Feature(s) using this parameter
accessClassCongestion V9 bts Barring of access class

adaptiveReceiver V17 transceiver Novel Adaptive Receiver
adjacent_cell_umbrella_ref V9 bts Directed Retry Handover
allocPriorityTable V7 bts TCH Allocation and Priority
Queuing
WPS – Queuing management
allocPriorityThreshold V7 bts TCH Allocation and Priority
Queuing
allocPriorityTimers V7 bts Queuing
allocWaitThreshold V7 bts Queuing
allOtherCasesPriority V7 bts TCH Allocation and Priority
Queuing
amrUlFrAdaptationSet V15 bts AMR Codec mode adaptation
amrUlHrAdaptationSet V15 bts AMR Codec mode adaptation
amrDlFrAdaptationSet V15 bts AMR Codec mode adaptation
amrUlHrAdaptationSet V15 bts AMR Codec mode adaptation
amrDirectAllocIntRxLevDL V14 bts AMR Handover mechanisms
Direct TCH Allocation
amrDirectAllocIntRxLevUL V14 bts AMR Handover mechanisms
amrDirectAllocRxLevDL V14 bts AMR Handover mechanisms
amrDirectAllocRxLevUL V14 bts AMR Handover mechanisms
amrFRIntercellCodecMThresh V14 handOverControl AMR Handover mechanisms
amrFRIntracellCodecMThresh V14 handOverControl AMR Handover mechanisms
amrHRIntercellCodecMThresh V14 handOverControl AMR Handover mechanisms
amrHRtoFRIntracellCodecMThresh V14 handOverControl AMR Handover mechanisms
amriRxLevDLH V14 handOverControl AMR Handover mechanisms
amriRxLevULH V14 handOverControl AMR Handover mechanisms
amrReserved1 V16 handOverControl AMR RATSCCH Proceudre
amrReserved2 V14 handOverControl AMR Legacy L1M
answerPagingPriority V7 bts TCH Allocation and Priority
Queuing
Nortel confidential

assignRequestPriority V7 bts TCH Allocation and Priority

Queuing
averagingPeriod V7 handOverControl Radio channel allocation
Interference Management
baseColourCode V7 bts Network Synchronization
bCCHFrequency V7 adjacentCellHandover
bCCHFrequency V7 adjacentCellReselecti
on
bCCHFrequency V7 bts
biZonePowerOffset V12 adjacentCellHandover General formulas
Concentric/DualCoupling/DualBand Cell
Handover
biZonePowerOffset V12 handoverControl General formulas
Handover
bscHopReconfUse V8 bsc Reconfiguration procedure
bscMSAccessClassBarringFunction V9 bsc Barring of access class
bscQueuingOption V7 signallingPoint Queuing
bsMsmtProcessingMode V7 bts Measurement Processing
bsPowerControl V7 powerControl Power Control Algorithms
AMR Power Control
bssMapT1 V7 bsc
bssMapT12 V7 bsc
bssMapT13 V7 bsc
bssMapT19 V8 bsc
bssMapT20 V8 bsc
bssMapT4 V7 bsc
bssMapT7 V7 bsc
bssMapT8 V7 bsc
bssMapTchoke V7 bsc
bssPagingCoordination V17 bts BSS CS Paging Coordination
bssSccpConnEst V7 signallingPoint
bsTxPwrMax V7 powerControl General formulas
Cabinet Output Power Setting
btsSMSynchroMode V15 btsSiteManager Network Synchronization
bts Time Between HO configuration V9 bts Minimum time between Handover
V12 General protection against HO ping-pong
btsHopReconfRestart V8 bts Reconfiguration procedure
btsIsHopping V7 bts Frequency Hopping
btsMSAccessClassBarringFunction V9 bts Barring of access class
btsThresholdHopReconf V8 bts Reconfiguration procedure
callClearing V7 bts Call Clearing Process
callReestablishment V7 bts Radio link failure process,
Call reestablishment procedure
callReestablishmentPriority V7 bts TCH Allocation and Priority
Queuing
capacityTimeRejection V14 handOverControl Protection against Intracell HO Ping-Pong
AMR Handover mechanisms
Nortel confidential

cellAllocation V7 bts Frequency Hopping

cellBarQualify V8 bts Selection, Reselection Algorithms
cellBarred V7 bts Selection, Reselection Algorithms
cellDeletionCount V7 bts Measurement Processing
Handovers screening
cellDtxDownLink V7 bts DTX
cellReselectHysteresis V8 bts Selection, Reselection Algorithms
cellReselectOffset V7 bts Selection, Reselection Algorithms
cellReselInd V8 bts Selection, Reselection Algorithms
cellType V7 adjacentCellHandOver Microcellular Algo
cellType V7 bts Microcellular Algo
channelType V7 channel
cId V17 adjacentCellUTRAN GSM to UMTS handover
coderPoolConfiguration V14 transcoder AMR Channel allocation

Cellular Telephone Text Modem (TTY)
compressedModeUTRAN V17 bts GSM to UMTS handover
concentAlgoExtMsRange V9 handOverControl Direct TCH Allocation

Handover
concentAlgoExtRxLev V9 handOverControl Direct TCH Allocation
Handover
concentAlgoIntMsRange V9 handOverControl Concentric/DualCoupling/DualBand Cell
Handover
concentAlgoIntRxLev V9 handOverControl Concentric/DualCoupling/DualBand Cell
Handover
concentric_cell V9 bts Concentric/DualCoupling/DualBand Cell
V12 Handover
cpueNumber V12 btsSiteManager Cell Group Management

CPU/BIFP LOAD SHARING
cypherModeReject V8 signallingPoint A5/3 Encryption algorithm
dARPPh1Priority V15 transceiver Network Synchronization
Data14_4OnNoHoppingTs V12 bts PCM Error Correction
data mode 14.4 kbit/s V11 transcoder board PCM Error Correction
data non transparent mode V11 bts PCM Error Correction
data non transparent mode V11 signallingPoint PCM Error Correction
data transparent mode V11 bts PCM Error Correction
data transparent mode V11 signallingPoint PCM Error Correction
delayBetweenRetrans V8 bts Paging command repetition process
directedRetry V9 adjacentCellHandOver Directed Retry Handover
directedRetryModeUsed V9 bts Directed Retry Handover
directedRetryPrio V12 bts Directed Retry Handover
distHreqt V7 handOverControl Measurement Processing
distWtsList V7 handOverControl Measurement Processing
diversity V7 bts Interference Cancellation
diversityUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
dtxMode V7 bts DTX
V14
Nortel confidential

early classmark sending V10 bts Modified SYS INFO 3

Location Services
earlyClassmarkSendingUTRAN V17 bts GSM to UMTS handover
emergencyCallPriority V7 bts TCH Allocation and Priority
Queuing
enableRepeatedFacchFr V16 bts Repeated Downlink FACCH
encrypAlgoAssComp V8 signallingPoint A5/3 Encryption algorithm
encrypAlgoCiphModComp V8 signallingPoint A5/3 Encryption algorithm
encrypAlgoHoPerf V8 signallingPoint A5/3 Encryption algorithm
encrypAlgoHoReq V8 signallingPoint A5/3 Encryption algorithm
encryptionAlgorSupported V7 bsc A5/3 Encryption algorithm
enhancedTRAUFrameIndication V12 bsc PCM Error Correction
enhCellTieringConfiguration V14 handOverControl Cell Tiering Parameters
estimatedSiteLoad V15 btsSiteManager V15.1 Evolution of Load Balancing
extended cell V9 bts
facchPowerOffset V16 bts Tx Power Offset for Signalling
fDDARFCN V17 adjacentCellUTRAN GSM to UMTS handover
fDDMultiratReporting V17 bts Enhanced Measurement Reporting
GSM to UMTS handover
UTRAN cell reporting using legacy
measurement reports (V17)
fDDreportingThreshold V17 handOverControl Enhanced Measurement Reporting
fDDreportingThreshold2 V17 handOverControl Enhanced Measurement Reporting
fhsRef V7 channel Frequency Hopping
filteredTrafficCoefficient V15 bts AMR based on traffic
fnOffset V15 btsSiteManager Network Synchronization
forced handover algo V9 adjacentCellHandOver Forced Handover
frAMRPriority V14 transceiver AMR Channel allocation
frPowerControlTargetMode V14 transceiver AMR Power Control
frPowerControlTargetModeDl V16 powerControl AMR Power Control
gprsNetworkModeOperation V15 bts Network Mode of Operation I support in BSS
gprsPreemptionForHR V17 bsc pDTCH Preemption by AMR HR calls
gsmToUmtsReselection V14 bts 2G - 3G Cell Reselection
gsmToUMTSServiceHo V17 bsc GSM to UMTS handover
handOver from signalling channel V7 handOverControl Direct TCH Allocation and Handover
Algorithms
hoMargin V7 adjacentCellHandOver Handovers
Power budget formula
Handover for traffic reasons
Define eligible neighbor cells for intercell
handover
Automatic handover adaptation
hoMarginAMR V14 adjacentCellHandOver AMR Handover mechanisms
Handovers
hoMarginAMRUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
Nortel confidential

hoMarginBeg V11 bts Handovers

Early HandOver Decision
hoMarginDist V8 adjacentCellHandOver Handover condition for leaving a cell on
distance
handover
hoMarginDistUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
hoMarginRxLev V8 adjacentCellHandOver Handovers
handover
hoMarginRxLevUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
hoMarginRxQual V8 adjacentCellHandOver Handovers
handover
hoMarginRxQualUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
hoMarginTiering V14 handOverControl Automatic cell tiering
hoMarginTrafficOffset V12 adjacentCellHandOver Handover for traffic reasons
hoMarginTrafficOffsetUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
hoMarginUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
hoPingpongCombination V12 adjacentCellHandOver General protection against HO ping-pong
V14
hoPingpongCombinationUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
hoPingpongTimeRejection V12 adjacentCellHandOver General protection against HO ping-pong
hoPingpongTimeRejectionUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
hoppingSequenceNumber V7 frequencyHopSystem Synthesised frequency hopping
hoRejectionTimeOverloadUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
hoSecondBestCellConfiguration V9 bsc Handover to 2nd best candidate when return
to old channel
hoTraffic V12 bsc Handover for traffic reasons
hoTraffic V12 bts Handover for traffic reasons
hrAMRPriority V14 transceiver AMR Channel allocation
hrCellLoadEnd V14 bts AMR Channel allocation
hrCellLoadStart V14 bts AMR Channel allocation
hrPowerControlTargetMode V14 powerControl AMR Power Control
hrPowerControlTargetModeDl V16 powerControl AMR Power Control
incomingHandOver V7 handOverControl Handovers
interBscDirectedRetry V9 bsc Directed Retry Handover
interBscDirectedRetryFromCell V9 bts Directed Retry Handover
interCellHOExtPriority V7 bts TCH Allocation and Priority
Queuing
interCellHOIntPriority V7 bts TCH Allocation and Priority

Queuing
interferenceType V12 adjacentCellHandover Automatic cell tiering
interferer cancel algo usage V10 bts Interference Cancellation
intraBscDirectedRetry V9 bsc Directed Retry Handover
intraBscDirectedRetryFromCell V9 bts Directed Retry Handover
intraCell V7 handOverControl Intracell Handover decision for signal quality
V12
Nortel confidential

intraCellHOIntPriority V7 bts TCH Allocation and Priority

Queuing
intraCellQueuing V8 bts Queuing
intraCellSDCCH V8 handOverControl Intracell Handover decision for signal quality
layer3MsgCyphModComp V8 signallingPoint A5/3 Encryption algorithm
locationAreaCodeUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
lRxLevDLH V7 handOverControl Handover condition for leaving a cell on rxlev
handover
lRxLevDLP V7 powerControl Power Control Algorithms
AMR Power Control
lRxLevULH V7 handOverControl Handover condition for leaving a cell on rxlev
lRxLevULP V7 powerControl Power Control Algorithms
AMR Power Control
lRxQualDLH V7 handOverControl Handover condition for leaving a cell on rxqual
lRxQualDLP V7 powerControl Power Control Algorithms
AMR Power Control
lRxQualULH V7 handOverControl Handover condition for leaving a cell on rxqual
lRxQualULP V7 powerControl Power Control Algorithms
AMR Power Control
maio V7 channel Synthesised frequency hopping
masterBtsSmId V15 btsSiteManager Network Synchronization
maxNumberRetransmission V8 bts Request access command repetition process
measurementProcAlgorithm V12 bts Measurement Processing
Direct TCH Allocation and Handover
Algorithms
microCellCaptureTimer V8 adjacentCellHandOver Microcellular Algo
microCellStability V8 adjacentCellHandOver Microcellular Algo
minNbOfTDMA V7 bts
missDistWt V7 handOverControl Measurement Processing
missRxLevWt V7 handOverControl Measurement Processing
missRxQualWt V7 handOverControl Measurement Processing
mobileCountryCodeUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
mobileNetworkCodeUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
mobileAllocation V7 frequencyHopSystem Synthesised frequency hopping
Baseband Frequency Hopping
modeModifyMandatory V9 bsc Directed Retry Handover
msBtsDistanceInterCell V7 handOverControl Handovers screening
Handover condition for leaving a cell on
distance
msRangeMax V7 handOverControl Handover condition for leaving a cell on
distance
msTxPwrMax V7 bts Accuracy related to measurements
General formulas
Forced Handover
Power Control Algorithms
msTxPwrMax2ndBand V12 bts Concentric/DualCoupling/DualBand Cell
Handove
msTxPwrMaxCCH V7 bts Selection, Reselection Algorithms
msTxPwrMaxCell V7 adjacentCellHandOver General formulas
Handovers screening
Nortel confidential

Directed Retry Handover: BTS

Forced Handover
handover
Power Control Algorithms
multi band reporting V10 bts Multiband reporting
Enhanced Measurement Reporting
nbLargeReuseDataChannels V14 bts Automatic cell tiering
nbOfRepeat V8 bts Paging command repetition process
nCapacityFRRequestedCodec V14 handOverControl AMR Handover mechanisms
neighDisfavorOffset V14 handOverControl Automatic handover adaptation
new power control algorithm V9 powerControl Power Control Algorithms
V12
nFRRequestedCodec V14 handOverControl AMR Handover mechanisms
nHRRequestedCodec V14 handOverControl AMR Handover mechanisms
noOfBlocksForAccessGrant V7 bts Paging command Process
noOfMultiframesBetweenPaging V7 bts Paging command Process
notAllowedAccessClasses V7 bts Barring of access class
numberOfPwciSamples V14 handOverControl Automatic cell tiering
numberOfSlotsSpreadTrans V7 bts Request access command repetition process
numberOfTCHFreeBeforeCongestion V9 bts Barring of access class
numberOfTCHFreeToEndCongestion V9 bts Barring of access class
numberOfTCHQueuedBeforeCongestion V9 bts Barring of access class
numberOfTCHQueuedToEndCongestion V9 bts Barring of access class
offsetLoad V12 adjacentCellHandover Handover decision according to adjacent cell
priorities ans load
offsetPriority V12 adjacentCellHandover Handover decision according to adjacent cell
priorities ans load
offsetPriorityUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
otherServicesPriority V7 bts TCH Allocation and Priority
Queuing
pagingOnCell V9 bts PCH and RACH channel control
pcmErrorCorrection V12 bts PCM Error Correction
penaltyTime V8 bts Selection, Reselection Algorithms
powerBudgetInterCell V7 handOverControl Handovers screening
powerControlIndicator V7 bts Power Control Algorithms
powerIncrStepSizeDL V14 powerControl Power Control Algorithms
powerIncrStepSizeUL V14 powerControl Power Control Algorithms
powerRedStepSizeDL V14 powerControl Power Control Algorithms
powerRedStepSizeUL V14 powerControl Power Control Algorithms
preemptionAuthor V15 signallingPoint eMLPP Preemption
pRequestedCodec V14 handOverControl AMR Handover mechanisms
preSynchroTimingAdvance V10 adjacentCellHandOver Pre-synchronized HO
priority V7 transceiver
Nortel confidential

processorLoadSupConf V8 bsc BSC Overload Management Mechanisms

V12
pwciHreqave V14 handOverControl Automatic cell tiering
minTimeQualityIntraCellHO V14 handOverControl Protection against Intracell HO Ping-Pong
AMR Handover mechanisms
qsearchC V17 handOverControl Enhanced Measurement Reporting
radChanSelIntThreshold V8 handOverControl Interference Management
radioAllocator V12 bts
radioLinkTimeout V7 bts Radio link failure process
radResSupBusyTimer V8 bsc
radResSupervision V8 bts
radResSupFreeTimer V8 bsc
reportTypeMeasurement V17 bts Enhanced Measurement Reporting
retransDuration V8 bts
rlf1 V8 bts Radio link failure process
rNCId V17 adjacentCellUTRAN GSM to UMTS handover
rndAccTimAdvThreshold V8 bts Request access command process
runCallClear V7 bts Call Clearing Process
runHandOver V7 bts Handovers
Microcellular Algo
Protection against RunHandover=1
runPwrControl V7 bts Power Control Algorithms
AMR Power Control
rxLevAccessMin V7 bts Selection, Reselection Algorithms
rxLevDLIH V7 handOverControl Intracell Handover decision for signal quality
rxLevDLPBGT V11 adjacentCellHandOver Handovers screening
Maximum RxLev for Power Budget
rxLevDLPbgtUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
rxLevHreqave V7 handOverControl Measurement Processing
rxLevHreqaveBeg V11 handOverControl Early HandOver Decision
Fast power control at TCH assignment
rxLevHreqt V7 handOverControl Measurement Processing
rxLevMinCell V7 adjacentCellHandOver General formulas
Handovers screening
handover
rxLevMinCellUTRAN V17 adjacentCellUTRAN GSM to UMTS handover
rxLevNCellHreqaveBeg V11 handOverControl Early HandOver Decision
rxLevULIH V7 handOverControl Intracell Handover decision for signal quality
rxLevWtsList V7 handOverControl Measurement Processing
rxNCellHreqave V7 handOverControl Measurement Processing
Nortel confidential


rxQualAveBeg V14 handOverControl Automatic handover adaptation
rxQualDLIH V7 handOverControl Intracell Handover decision for signal quality
rxQualHreqave V7 handOverControl Measurement Processing
rxQualHreqt V7 handOverControl Measurement Processing
rxQualULIH V12 handOverControl Intracell Handover decision for signal quality
rxQualWtsList V12 handOverControl Measurement Processing
sacchPowerOffset V16 bts Tx Power Offset for Signalling
sacchPowerOffsetSelection V16 bts Tx Power Offset for Signalling
scramblingCode V17 adjacentCellUTRAN GSM to UMTS handover
selfAdaptActivation V14 bts Automatic handover adaptation
selfTuningObs V12 handOverControl Automatic cell tiering
servingBandReporting V17 bts Enhanced Measurement Reporting
servingBandReportingOffset V17 handOverControl Enhanced Measurement Reporting
servingfactorOffset V14 handOverControl Automatic handover adaptation
siteGsmFctList V7 btsSiteManager
small to large zone HO priority V9 handOverControl TCH Allocation and Priority
Queuing
smartPowerManagementConfig V17 PowerControl BTS Smart Power Management
smartPowerSwitchOffTimer V17 PowerControl BTS Smart Power Management
smsCB V7 bts SMS-Cell Broadcast
speechMode V8 bts AMR - Adaptative Multi Rate FR/HR
V14
speechMode V8 signallingPoint AMR - Adaptative Multi Rate FR/HR
V14
standard indicator AdjC V10 adjacentCellHandover Dual Band Handling
V12
standard indicator AdjC V10 adjacentCellReselect Dual Band Handling
V12
standardIndicator V12 bts Concentric/DualCoupling/DualBand Cell
Handover
synchronized V7 adjacentCellHandOver Pre-synchronized HO
Handover Algorithms on the Mobile Side
t3101 V9 bts
t3103 V9 bts
t3107 V9 bts
t3109 V9 bts
t3111 V9 bts
t3121 V17 bts GSM to UMTS handover
t3122 V9 bts
temporaryOffset V8 bts Selection, Reselection Algorithms
thresholdInterference V7 handOverControl Radio channel allocation
Interference Management
timeBetweenHOConfiguration V9 bsc Power Budget Handover
V12 General protection against HO ping-pong
timerPeriodicUpdateMS V7 bts
tnOffset V15 btsSiteManager Network Synchronization
trafficPCMAllocationPriority V9 transceiver
Nortel confidential

transceiver equipment class V9 transceiverEquipment Concentric/DualCoupling/DualBand Cell

Handover
transceiver equipment class V9 transceiverZone Concentric/DualCoupling/DualBand Cell
Handover
transceiverZone V9 transceiver Concentric/DualCoupling/DualBand Cell
Handover
uMTSAccessMinLevel V14 bts 2G - 3G Cell Reselection
uMTSReselectionARFCN V14 bts 2G - 3G Cell Reselection
uMTSReselectionOffset V14 bts 2G - 3G Cell Reselection
uMTSSearchLevel V14 bts 2G - 3G Cell Reselection
uplinkPowerControl V8 powerControl Power Control Algorithms
AMR Power Control
uRxLevDLP V7 powerControl Power Control Algorithms
uRxLevULP V7 powerControl Power Control Algorithms
uRxQualDLP V7 powerControl Power Control Algorithms
uRxQualULP V7 powerControl Power Control Algorithms
wPSManagement V15 bsc WPS - Wireless Priority Service
wPSQueueStepRotation V15 bts WPS - Wireless Priority Service
zone Tx power max reduction V9 transceiverZone Concentric/DualCoupling/DualBand Cell
Handover
zoneFrequencyHopping V9 transceiverZone Concentric/DualCoupling/DualBand Cell
Handover
zoneFrequencyThreshold V9 transceiverZone Concentric/DualCoupling/DualBand Cell
Handover
3.2. GSM UNUSED PARAMETERS

The table presented below summarizes the GSM parameter still “reserved for future use”.
Parameter name BSS Object- Feature(s) using this parameter
sigPowerOverboost V16 bts Tx Power Overboost for Signalling Channels

extendedTimingAdvanceWindow V16 bts Extended TA Window (GSM-R only, RM2 only)
highSpeedUplinkDistortionRemoval V16 bts High Speed Distorsion removal (GSM-R only,
RM2 only)
3.3. RAILWAY-SPECIFIC PARAMETERS (GSM-R)

Before V16, the GSM-R specific parameters did not appear on the OMC-R MMI of GSM
customers.
Starting in v16, the MMI is common between GSM and GSM-R. It means that public GSM
customers have visibility on GSM-R specific parameters that are of no use for public GSM.
This list is provided in this section for information only : GSM customers must not change the
default values for these parameters. The definition and use of these parameters is explained
in a separate Railway-specific Parameter User Guide document that is provided to GSM-R
customers only.
Nortel confidential

Parameter name BSS Object- GSM-R Feature(s) using this parameter
batteryRemoteControllerPresence V15.1R btssitemanager BTS Battery Remote Monitoring

emergencyThreshold V15.1R signallingPoint ASCI Evolutions
eMLPPThreshold V12.4d signallingPoint Enhanced Multilevel Precedence and
Preemption
msPowerClassToggle V15.1R bts Mobile class sensiticity counters
nCHPosition V12.4d bts Advanced Speech Call Items
preemptionAuthor (*) V12.4d signallingPoint Enhanced Multilevel Precedence and
Preemption
timerGCCHNotif V15.1R signallingPoint ASCI Evolutions
uplinkReply V15.1R bsc ASCI Evolutions
uplinkReplyTimer V15.1R bts ASCI Evolutions
voiceBroadcastService V12.4d signallingPoint Advanced Speech Call Items
voiceGroupCallService V12.4d signallingPoint Advanced Speech Call Items
(*) Since v15.1, this parameter is also used in GSM for activation of eMLPP radio resource
preemption in the BSS. Other eMLPP parameters are useful only in GSM-R for group calls
(emergencyThreshold and eMLPPThreshold).
Nortel confidential

3.4. PARAMETERS VERSUS BSS FEATURES AND PROCEDURES

Here is the list of the main BSS tunable parameters sorted by procedure or feature.
3.4.1 2G CELL SELECTION AND RESELECTION

cellBarQualify, cellBarred, rxLevAccessMin, msTxPwrMaxCCH, cellReselInd,
cellReselectHysteresis, cellReselectOffset, temporaryOffset, penaltyTime,
rndAccTimAdvThreshold.
3.4.2 2G-3G CELL RESELECTION

uMTSAccessMinLevel, uMTSReselectionARFCN, uMTSReselectionOffset,
uMTSSearchLevel.
3.4.3 LEGACY MEASUREMENT REPORTING

multiBandReporting, powerControlIndicator, fDDMultiratReporting, fDDreportingThreshold2,
qsearchC
3.4.4 ENHANCED MEASUREMENT REPORTING

multiBandReporting, reportTypeMeasurement, servingBandReportingOffset,
servingBandReporting, fDDMultiratReporting, fDDreportingThreshold,
fDDreportingThreshold2, qsearchC
3.4.5 LEVEL AVERAGING

rxLevHreqave, rxLevHreqt, rxLevWtsList, missRxLevWt, rxLevHreqaveBeg.
3.4.6 QUALITY AVERAGING

rxQualHreqave, rxQualHreqt, rxQualWtsList, missRxQualWt.
3.4.7 DISTANCE AVERAGING

distHreqt, distWtsList, missDistWt.
3.4.8 CELL ELIGIBILITY

rxLevMinCell, rxNCellHreqave, cellDeletionCount, rxLevHreqave, missRxLevWt,
msTxPwrMaxCell, msTxPwrMax, hoSecondBestCellConfiguration, rxLevNCellHreqaveBeg.
Nortel confidential

3.4.9 RADIO LINK FAILURE

radioLinkTimeOut, rlf1, rlf2, rlf3, t3111, t3109.
3.4.10 INTERFERENCE MANAGEMENT

averagingPeriod, thresholdInterference, radChanSelIntThreshold.
3.4.11 PCH AND RACH CONTROL PARAMETERS

delayBetweenRetrans, maxNumberRetransmission, nbOfRepeat, noOfBlocksForAccessGrant,
noOfMultiframesBetweenPaging, numberOfSlotsSpreadTrans, pagingOnCell, retransDuration,
t3122, gprsNetworkModeOperation, bssPagingCoordination.
3.4.12 CONCENTRIC CELL

concentric cell, concentAlgoExtMsRange, concentAlgoExtRxLev, concentAlgoIntMsRange,
concentAlgoIntRxLev, transceiverEquipmentClass, transceiverZone, zoneFrequencyHopping,
zoneFrequencyThreshold, small to large zone HO Priority, zone Tx power max reduction,
biZonePowerOffset, biZonePowerOffset(n), rxLevMinCell(n).
3.4.13 EXTENDED CELL

extended cell, rndAccTimAdvThreshold, msRangeMax, callClearing, channelType.
3.4.14 QUEUING AND PRIORITY MANAGEMENT

allocPriorityTable, allocPriorityTimers, allocPriorityThreshold, allocWaitThreshold,
allOtherCasesPriority, answerPagingPriority, assignRequestPriority, bscQueuingOption,
callReestablishmentPriority, emergencyCallPriority, interCellHOExtPriority,
interCellHOIntPriority, intraCellHOIntPriority, otherServicesPriority, small to large zone HO
Priority, directedRetryPrio, intraCellQueuing.
3.4.15 EMLPP PREEMPTION

preemptionAuthor.
3.4.16 SMS-CB
smsCB, noOfBlocksForAccessGrant, channelType.
3.4.17 FREQUENCY HOPPING

btsIsHopping, hoppingSequenceNumber, maio, siteGsmFctList, cellAllocation,
mobileAllocation, fhsRef, bscHopReconfUse, btsHopReconfRestart, btsThresholdHopReconf,
zoneFrequencyHopping, zoneFrequencyThreshold.
Nortel confidential

3.4.18 DYNAMIC BARRING OF ACCESS CLASS

bscMsAccessClassBarringFunction, btsMsAccessClassBarringFunction,
accessClassCongestion, numberOfTCHFreeBeforeCongestion,
numberOfTCHFreeToEndCongestion, numberOfTCHQueuedBeforeCongestion,
numberOfTCHQueuedToEndCongestion, notAllowedAccessClasses.
3.4.19 DTX
dtxMode, cellDtxDowlink.
3.4.20 UPLINK POWER CONTROL

uplinkPowerControl, new power control algorithm, runPowerControl, , powerIncrStepSizeUL,
powerRedStepSizeUL, lRxQualULP, uRxQualULP, lRxLevULP, uRxLevULP, msTxPwrMax,
msTxPwrMax2ndBand.
3.4.21 DOWNLINK POWER CONTROL

bsPowerControl, new power control algorithm, runPwrControl, powerIncrStepSizeDL,
powerRedStepSizeDL, lRxQualDLP, uRxQualDLP, lRxLevDLP, uRxLevDLP.
3.4.22 DIRECTED RETRY HANDOVER

interBscDirectedRetry, intraBscDirectedRetry, interBscDirectedRetryFromCell,
intraBscDirectedRetryFromCell, modeModifyMandatory, directedRetryModeUsed,
msTxPwrMaxCell, msTxPwrMax, directedRetry, adjacent cell umbrella ref, directedRetryPrio.
3.4.23 UPLINK INTRACELL HANDOVER

intraCell, intraCellSDCCH, runHandOver, rxLevULIH, lrxQualULH, rxQualULIH.
3.4.24 DOWNLINK INTRACELL HANDOVER

intraCell, intraCellSDCCH, runHandOver, rxLevDLIH, lRxQualDLH, rxQualDLIH.
3.4.25 INTERCELL HANDOVER ON BAD UPLINK QUALITY

CRITERION
handOver from signalling channel, runHandOver, lrxQualULH, hoMarginRxQual.
3.4.26 INTERCELL HANDOVER ON BAD DOWNLINK QUALITY

CRITERION
handOver from signalling channel, runHandOver, lRxQualDLH, hoMarginRxQual.
Nortel confidential

3.4.27 INTERCELL HANDOVER ON BAD UPLINK LEVEL CRITERION

handOver from signalling channel, runHandOver, lRxLevULH, hoMarginRxLev.
3.4.28 INTERCELL HANDOVER ON BAD DOWNLINK LEVEL

CRITERION
handOver from signalling channel, runHandOver, lRxLevDLH, hoMarginRxLev.
3.4.29 INTERCELL HANDOVER ON POWER BUDGET CRITERION

handOver from signalling channel, runHandOver, powerBudgetInterCell, hoMargin,
rxLevDLPBGT.
3.4.30 MICROCELLULAR ALGORITHM

handOver from signalling channel, runHandOver, cellType, microCellCaptureTimer,
microCellStability, rxNCellHreqave.
3.4.31 INTERCELL HANDOVER ON DISTANCE CRITERION

msBtsDistanceInterCell, handOver from signalling channel, runHandOver,hoMarginDist.
3.4.32 HANDOVER FOR TRAFFIC REASONS

handOver from signalling channel, runHandOver, hoTraffic, hoMarginTrafficOffset.
3.4.33 HANDOVER DECISION ACCORDING TO ADJACENT CELL

(V12)
handOver from signalling channel, runHandOver, offsetLoad, offsetPriority.
3.4.34 GENERAL PROTECTION AGAINST HO PINGPONG

hoPingpongCombination, hoPingpongTimeRejection.
3.4.35 CALL CLEARING

callClearing, runCallClear.
3.4.36 FREQUENCY BAND FAVOURING

early classmark sending, multi band reporting, cellBarred, cellBarQualify, hoMargin,
hoMarginDist, hoMarginRxQual, hoMarginRxLev, offsetPriority.
Nortel confidential

3.4.37 MINIMUM TIME BETWEEN HANDOVER (BEFORE V12)

timeBetweenHOConfiguration, bts Time Between HO configuration.
3.4.38 RADIO RESOURCE CONTROL AT CELL LEVEL

radResSupervision, radResSupBusyTimer, radResSupFreeTimer.
3.4.39 PRE-SYNCHRONISED HANDOVER

synchronised, preSynchroTimingAdvance.
3.4.40 INTERFERER CANCELLATION

interferer cancel algo usage, diversity
3.4.41 EARLY HO DECISION

hoMarginBeg, rxLevHreqaveBeg, rxLevNCellHreqaveBeg.
3.4.42 MAXIMUM RXLEV FOR PBGT

rxLevDLPBGT.
3.4.43 CELL TIERING

interferenceType, intraCell, measurementProcAlgorithm, nbLargeReuseDataChannels,
hoMarginTiering, pwciHreqave, numberOfPwciSamples, selfTuningObs.
3.4.44 TTY SUPPORT ON BSC/TCU 3000

coderPoolConfiguration.
3.4.45 PROTECTION AGAINST INTRACELL HO PING-PONG

capacityTimeRejection, minTimeQualityIntraCellHO.
3.4.46 AUTOMATIC HANDOVER ADAPTATION

selfAdaptActivation, servingfactorOffset, neighDisvaforOffset, rxQualAveBeg.
Nortel confidential

3.4.47 GSM TO UMTS HANDOVER

gsmToUMTSServiceHO, earlyClassmarkSendingUTRAN, compressedModeUTRAN,
mobileCountryCodeUTRAN, mobileNetworkCodeUTRAN, locationAreaCodeUTRAN, rNCId,
cId, fDDARFCN, scramblingCode, diversityUTRAN, t3121, rxLevMinCellUTRAN,
rxLevDLPbgtUTRAN, hoMarginUTRAN, hoMarginAMRUTRAN, hoMarginRxLevUTRAN,
hoMarginRxQualUTRAN, hoMarginDistUTRAN, hoMarginTrafficOffsetUTRAN,
offsetpriorityUTRAN, hoPingpongCombinationUTRAN, hoPingpongTimeRejectionUTRAN,
hoRejectionTimeOverloadUTRAN
3.4.48 ADAPTATIVE FULL/HALF RATE

amrDlFrAdaptationSet, amrDlHrAdaptationSet, amrUlFrAdaptationSet, amrUlHrAdaptationSet,
coderPoolConfiguration, speechMode, HRCellLoadStart, HRCellLoadEnd, frAMRPriority,
hrAMRPriority, hrPowerControlTargetMode, hrPowerControlTargetModeDl,
frPowerControlTargetMode, frPowerControlTargetModeDl, bsPowerControl,
uplinkPowerControl, pRequestedCodec, nHRRequestedCodec, nFRRequestedCodec,
amrFRIntercellCodecMThresh, amrFRIntracellCodecMThresh, amrHRIntercellCodecMThresh,
amrHRtoFRIntracellCodecMThresh, hoMarginAMR, amriRxLevDLH, amriRxLevULH,
nCapacityFRRequestedCodec, amrDirectAllocIntRxLevDL, amrDirectAllocIntRxLevUL,
amrDirectAllocRxLevDL, amrDirectAllocRxLevUL, filteredTrafficCoefficient,
gprsPreemptionForHR.
3.4.49 WIRELESS PRIORITY SERVICE

allocPriorityTable, allocPriorityTimers, allocWaitThreshold, bscQueuingOption,
wPSManagement, wPSQueueStepRotation.
3.4.50 NETWORK SYNCHRONIZATION

btsSMSynchroMode, tnOffset, fnOffset, dARPPh1Priority, masterBtsSmId, baseColourCode
3.4.51 REPEATED DOWNLINK FACCH

enableRepeatedFacchFr
3.4.52 TX POWER OFFSET FOR SIGNALLING

facchPowerOffset, sacchPowerOffset, sacchPowerOffsetSelection
3.4.53 NOVEL ADAPTIVE RECEIVER

adaptiveReceiver
Nortel confidential

3.4.54 A5/3 ENCRYPTION ALGORITHM

cypherModeReject, encrypAlgoAssComp, encrypAlgoCiphModComp, encrypAlgoHoPerf,
encrypAlgoHoReq, encryptionAlgorSupported, layer3MsgCyphModComp
3.4.55 BTS SMART POWER MANAGEMENT

smartPowerManagementConfig, smartPowerSwitchOffTimer
Nortel confidential

4. ALGORITHMS
4.1. INTRODUCTION
This chapter describes major BSS GSM algorithms using OMC-R algorithm parameters, both
on the BTS and the MS side.
4.2. CONVENTIONS AND UNITS

In this chapter, the following abbreviations are used:
• RXQUAL_DL: weighted average for DL signal quality (MS measurements)

• RXQUAL_UL: weighted average for UL signal quality (BTS measurements)
• RXLEV_DL: weighted average for DL signal strength (MS measurements)
• RXLEV_UL: weighted average for UL signal strength (BTS measurements)
• MS_BS_Dist: weighted average of MS distance from BTS (MS timing advance)
• RXLEV_NCELL(n): arithmetic average for signal strength on neighbor cell
(reported by the MS)
4.2.1 UNIT
Thresholds on signal quality are given in RXQUAL values. Samples measurements are also
reported in RXQUAL values. When internal calculations are performed, RXQUAL values are
converted into bit error rates (BER) using mean values and compared to thresholds which are
also converted into bit error rate. From the V9 BSS release, the comparison is done with the
upper or the lower limit of the BER range.
RxQual value BER range value Mean BER value

0 BER < 0.2% 0.14%
1 0.2% < BER < 0.4% 0.28%
2 0.4% < BER < 0.8% 0.57%
3 0.8% < BER < 1.6% 1.13%
4 1.6% < BER < 3.2% 2.26%
5 3.2% < BER < 6.4% 4.53%
6 6.4% < BER < 12.8% 9.05%
7 12.8% < BER 18.10%
Signal strength thresholds are given in dBm (from -110 dBm to -47 dBm).
Signal strength measurements reported by the mobiles and the BTS are given in the rxlev
format (from 0 to 63).
The average signal strength measurement values, which are compared to the rxlev
thresholds, are the integer part of the average result.
Nortel confidential

4.2.2 PHASE 2 BTS AND MS MAXIMUM TRANSMITTING OUTPUT POWERS
MOBILE PHASE 2 MAXIMUM TRANSMITTING OUTPUT POWER
Power GSM 850 / GSM 900 DCS 1800 PCS 1900 Tolerance for
Class Nominal Maximum Nominal Maximum Nominal Maximum condition
Output Power Output Power Output Power
Normal Extreme
1 restricted MS Phase 1 1W (30 dBm) 1W (30 dBm) +/- 2 dB +/- 2,5 dB
2 8W (39 dBm) 0,25W (24 dBm) 0,25W (24 dBm) +/- 2 dB +/- 2,5 dB
3 5W (37 dBm) 4W (36 dBm) 2W (33 dBm) +/- 2 dB +/- 2,5 dB
4 2W (33 dBm) +/- 2 dB +/- 2,5 dB
5 0,8W (29 dBm) +/- 2 dB +/- 2,5 dB
ASSOCIATED POWER CONTROL LEVELS
GSM 850 / GSM 900 DCS 1800 PCS 1900
Power Nominal Tolerance Power Nominal Tolerance Power Nominal Tolerance

control Output (dB) for control Output (dB) for control Output (dB) for
level power conditions level power conditions level power conditions
(dBm) (dBm) (dBm)
N E N E N E
0-2 39 ±2 ± 2,5 29 36 ±2 ± 2,5 22-29 Reserved
3 37 ±3 ±4 30 34 ±3 ±4 30 33 ±3 ±4
4 35 ±3 ±4 31 32 ±3 ±4 31 32 ±3 ±4
5 33 ±3 ±4 0 30 ±3 ±4 0 30 ±3 ±4
6 31 ±3 ±4 1 28 ±3 ±4 1 28 ±3 ±4
7 29 ±3 ±4 2 26 ±3 ±4 2 26 ±3 ±4
8 27 ±3 ±4 3 24 ±3 ±4 3 24 ±3 ±4
9 25 ±3 ±4 4 22 ±3 ±4 4 22 ±3 ±4
10 23 ±3 ±4 5 20 ±3 ±4 5 20 ±3 ±4
11 21 ±3 ±4 6 18 ±3 ±4 6 18 ±3 ±4
12 19 ±3 ±4 7 16 ±3 ±4 7 16 ±3 ±4
13 17 ±3 ±4 8 14 ±3 ±4 8 14 ±3 ±4
14 15 ±3 ±4 9 12 ±4 ±5 9 12 ±4 ±5
15 13 ±3 ±4 10 10 ±4 ±5 10 10 ±4 ±5
16 11 ±5 ±6 11 8 ±4 ±5 11 8 ±4 ±5
17 9 ±5 ±6 12 6 ±4 ±5 12 6 ±4 ±5
18 7 ±5 ±6 13 4 ±4 ±5 13 4 ±4 ±5
19-31 5 ±5 ±6 14 2 ±5 ±6 14 2 ±5 ±6
15-28 0 ±5 ±6 15 0 ±5 ±6
16-21 Reserved
Nortel confidential

BASE STATION PHASE 2 MAXIMUM TRANSMITTING OUTPUT POWERS
GSM 850 / GSM 900 GSM 1800 / GSM 1900 Tolerance for condition
Normal Extreme
CLASS 1: [320 - 640[ W [55 - 58[ dBm CLASS 1: [20 - 40[ W [43 - 46[ dBm +/- 2 dB +/- 2,5 dB
CLASS 2: [160 - 320[ W [55 - 58[ dBm CLASS 2: [10 - 20[ W [40 - 43[ dBm +/- 2 dB +/- 2,5 dB
CLASS 3: [80 -160[ W [49 - 52[ dBm CLASS 3: [5 - 10[ W [37 - 40[ dBm +/- 2 dB +/- 2,5 dB
CLASS 4: [40 - 80[W [46 - 49[ dBm CLASS 4: [2.5 - 5[ W [34 - 37[ dBm +/- 2 dB +/- 2,5 dB
CLASS 5: [20 - 40[ W [43 - 46[dBm +/- 2 dB +/- 2,5 dB
CLASS 6: [10 - 20[ W [40 - 43[ dBm +/- 2 dB +/- 2,5 dB
CLASS 7: [5 - 10[ W [37 - 40[ dBm +/- 2 dB +/- 2,5 dB
CLASS 8: [2.5 - 5[ W [34 - 37[ dBm +/- 2 dB +/- 2,5 dB
Settings will be provided to allow output power to be reduced from its maximum level to at
least six steps of nominally 2 dB with an accuracy of ≈1 dB to allow a fine adjustment of the
coverage by the network operator. In addition, the actual absolute output power at each static
RF power step (N) shall be 2*N dB below the absolute output power at static RF power step 0
with a tolerance of ≈3 dB under normal conditions and ≈4dB under extreme conditions. The
static RF power step 0 will be the actual output power according to the TRX power class.
Nortel confidential

4.2.3 GSM PRODUCTS SENSITIVITY AND POWER
Please refer to the following documents for information on main RF characteristics of the
Nortel BTS portfolio :
BTS S2000L Engineering Rules : [R47]

BTS S2000H Engineering Rules : [R48]
BTS S4000 Outdoor Engineering Rules : [R49]
BTS S4000 Indoor Engineering Rules : [R50]

BTS eCell Engineering Rules : [R51]
BTS S8000-S8003 Indoor & S8000 Outdoor Engineering Rules : [R52]
BTS S12000 Indoor & Outdoor Engineering Rules : [R53]

BTS 18000 Indoor & Outdoor Engineering Rules : [R54]
BTS 18000 GSM-UMTS Indoor & Outdoor Engineering Rules : [R55]
BTS 6000 GSM Indoor & Outdoor Engineering Rules : [R56]
Nortel confidential

4.2.4 CONVERSION RULES
POWER CONVERSION
The main power conversion rules are provided below.
P (dB) = P (dBW) = 10 log (PW)

P (dBm) = P (dBmW) = 10 log (PmW)
P (dB) = P (dBm) - 30
E (dBV / m) = P (dBm) + 20 log FHz + 77,2
DISTANCE - TIMING ADVANCE CONVERSION
The table below gives the conversion rules of the timing advance versus the distance.
One bit corresponds to 554 m and the accuracy is 0.25 bit (i.e 138.5 m)
Timing Advance Distance (m) Recommendation accuracy

0 [0..554[ 25 %
1 [554..1108[ 12.5 %
2 [1108..1662[ 6.1 %
3 [1662.. 3.1 %
…
63 [34 902..35456[ 0.4 %
Due to multipath and to MS synchronization accuracy, the gap of timing advances between
two different MS for a given distance can reach 3 bits (i.e. 1,6 km).
The value of the timing advance has an impact on decision taking for handover and call
clearing. The timing advance is calculated by taking into account all the rays coming from a
same signal.
The timing advance must be used carefully as a handover and call clearing criteria, especially
in a microcellular configuration.
4.2.5 ACCURACY RELATED TO MEASUREMENTS

The GSM recommendation specifies the absolute and relative accuracy of the MS and BTS
measurements (Rec. GSM 05.08 § 8.1.2). The table below provides the GSM absolute
accuracy recommendation.
MS and BTS absolute measurement accuracy

from - 110 dBm to - 70 dBm under normal conditions +/- 4 dB
from - 110 dBm to - 48 dBm under normal conditions +/- 6 dB
from - 110 dBm to - 48 dBm under extreme conditions +/- 6 dB
Nortel confidential

The overlap between the different ranges (see above normal condition cases) are specified in
the recommendation.
This recommendation is not restrictive and most of the BTS and MS may provide better
results. However, these figures show that the threshold accuracy handover and power
control field strength may be off by a few dB.
The relative accuracy depends on the gap between measurement levels and sensivity levels.
The table below provides the GSM relative accuracy recommendation of a difference between
two measurements lower than 20 dB.
MS and BTS absolute measurement accuracy

lower measured level > sensitivity + 14 dB + 2 / - 2 dB
sensitivity + 14 dB> lower measured level > sensitivity + 1 dB + 2 / - 3 dB
sensitivity + 1 dB > lower measured level + 2 / - 4 dB
For example, the level difference between two field strengths, which are higher than the
sensivity + 14 dBm, must be within the range of [-2 dB to +2 dB].
Output power tolerance must also be considered in the parameters setting because the
parameters bsTxPwrMax and msTxPwrMax are used in the algorithms.
4.2.6 FREQUENCY BAND

Frequency band Fl(n) [lower band] n range Fu(n) [upper band]
P-GSM 900 Fl(n) = 890 + 0,2 * n 1 ≤ n ≤ 124 Fu(n) = Fl(n) + 45
Fl(n) = 890 + 0,2 * n 0 ≤ n ≤ 124
E-GSM 900 Fu(n) = Fl(n) + 45
Fl(n) = 890 + 0,2 * (n - 1024) 975 ≤ n ≤ 1023
Fl(n) = 890 + 0,2 * n 0 ≤ n ≤ 124
R-GSM 900 Fu(n) = Fl(n) + 45
Fl(n) = 890 + 0,2 * (n - 1024) 955 ≤ n ≤ 1023
DCS 1800 Fl(n) = 1710,2 + 0,2 * (n - 512) 512 ≤ n ≤ 885 Fu(n) = Fl(n) + 95
PCS 1900 Fl(n) = 1850,2 + 0,2 * (n - 512) 512 ≤ n ≤ 810 Fu(n) = Fl(n) + 80
GSM 450 Fl(n) = 450,6 + 0,2 * (n - 259) 259 ≤ n ≤ 293 Fu(n) = Fl(n) + 10
GSM 480 Fl(n) = 479 + 0,2 * (n - 306) 306 ≤ n ≤ 340 Fu(n) = Fl(n) + 10
GSM 850 Fl(n) = 824,2 + 0,2 * (n - 128) 128 ≤ n ≤ 251 Fu(n) = Fl(n) + 45
GSM 750 Fl(n) = 747,2 + 0,2 * (n - 438) 438 ≤ n ≤ 511 Fu(n) = Fl(n) + 30
Frequencies are in MHz.
Nortel confidential

4.3. 2G CELL SELECTION AND RESELECTION
4.3.1 OVERVIEW
NETWORK SELECTION
At switch-on, the mobile is required to select, among a set of PLMNs that is further defined
below, the highest priority PLMN that is both :
• "available"
• and "allowable"
An available PLMN is a PLMN on which a cell has been found that is not barred and where
Rxlev > rxLevAccessMin
An allowable PLMN is a PLMN which is not in the list of "forbidden PLMNs" in the MS.
The set of possible PLMNs and their decreasing order of priority is :
• the last PLMN on which the MS performed a successful registration (Location area
update);
• the Home PLMN (this is the PLMN where the MCC and MNC of the PLMN identity
match the MCC and MNC of the IMSI);
• other PLMNs, in the order explicitely defined in the SIM.
This order of priority is valid, whether the MS is a roamer or not.
CELL SELECTION PROCEDURE:
• The selection process begins with a signal strength measurement averaging on

the whole frequency band lasting approximately three seconds in order to sort
channels according to their strength.
• Then, for the most powerful channel, the MS tries to detect the FCH channel, then
decodes the SCH channel, and if the MNC and MCC are not forbidden, it listens to
SYSTEM INFORMATION 1 to 4 to get full information on that cell and possibly
select it depending on the selection criterion.
• If one of the steps fails, the next powerful channel is tried and so on.
CELL RESELECTION PROCEDURE:
• Reselection criteria are calculated every 5 to 60 seconds period (depending on the

number of cells for which BCCH is in BCCH Allocation and number of multiframes
between paging) because MS must perform at least 5 measurements on every cell
listed in the BCCH Allocation before averaging is allowed. For phase 1 MS, C1
path loss criterion is used whereas for phase 2 MS, the C2 criterion is used.
• Then, for the most powerful channel, the MS attempts to detect the FCH channel,
then decodes the SCH channel, and if the NCC and BCC are not forbidden, it will
Nortel confidential

listen to SYSTEM INFORMATION 1 to 4 to get full information on that cell and

possibly select it depending on the selection criterion.
4.3.2 SELECTION OR RESELECTION BETWEEN CELLS OF

CURRENT LOCATION AREA
In Phase 1, MS checks that cellBarred flag is not set to “barred” before sorting eligible cells.
In Phase 2, MS checks cellBarred and cellBarQualify flags in order to define the cell’s access
(normal,low,barred).
C1 is the path loss criterion for unbarred cells of allowed PLMN.
To be selected, a cell must have a positive C1:
C1 = RXLEV - rxLevAccessMin - Max (B,0) >0

with B = msTxPwrMaxCCH - P
P = maximum RF output power of the MS
Received levels must be higher than rxlevAccessMin and if a mobile state has a classmark
lower than msTxPwrMaxCCH, it must get closer to the cell to have access to it.
4.3.3 RESELECTION TO A CELL OF A DIFFERENT LOCATION AREA

This is an additionnal criteria for reselection towards a “y” cell having a different Location Area
from the current one. A choice must be made between C1 values for cell having a different
Location Area:
C1(x) < C1(y) - cellReselectHysteresis
The value used for the parameter cellReselectHysteresis is the-one set in the current serving
cell.
4.3.4 ADDITIONAL RESELECTION CRITERION (FOR PHASE 2)

In Phase 2, MS checks cellBarred and cellBarQualify flags in order to define the cell’s access
(normal, low, barred).
To activate this feature, the cellReselInd parameter will be set to “true”.
Nortel confidential

The C1 criterion did not provide a way of preventing a fast moving mobile station from
reselecting a “fugitive cell” nor avoiding ping-pong reselection. The idea is to give a cell a
tunable access for reselection and to prevent mobiles from reselecting a cell if that cell is new
to the mobile or if it was recently the serving cell:
C2 = C1 + cellReselectOffset - temporaryOffset * H (penaltyTime - t)

for penaltyTime ≠ 640
C2 = C1 - cellReselectOffset
for penaltyTime = 640
where t is a timer started as soon as a cell enters the mobile best cell list:
• t = penaltyTime if the new cell in the list is the previous serving cell
• t = 0 otherwise
and H(x) is a function:
• H(penaltyTime - t) = 0 if t ≥ penaltyTime
• H(penaltyTime - t) = 1 if t < penaltyTime
temporaryOffset is a negative offset.
By adding an offset (cellReselectOffset) it is possible to give different priorities, for example, to
different types of cells in case of a multilayer network or to different bands when multiband
operation is used.
The timer penaltyTime ensures that the mobile will reselect a cell which has been received
with a sufficient level for a sufficient time. Some microcellular handover algorithms are based
on this C2 reselection principle.
Nortel confidential

Priority of access: cellBarred and cellBarQualify parameters.

The parameters are used to give each cell the authorization to be selected or reselected, and
for all of them a priority of access is given.
The selection procedure is mainly concerned by this priority introduction.
SELECTION
For the server cell and the neighboring cells, the C1 algorithm is computed. The C2 algorithm
is computed only if cell reselection is used (cellReselInd = true).
A priority is affected to each eligible cell and is only applied to Phase II MS.
IF cellBarQualify = TRUE THEN the cell priority is “low”, whatever the “cellBarred” value is.
IF cellBarQualify = FALSE AND IF the cell is barred (cellBarred set to “barred”) THEN the cell
priority is null (the cell can not be reselected in idle mode).
IF cellBarQualify = FALSE AND IF the cell is not barred THEN the priority is “normal”.
For a mobile Phase II: if no cell with NORMAL priority is eligible (cell contained in the eligible
list constituted using the C1 algorithm), then the cells with LOW priority are scanned. So even
if a cell is barred, a phase II mobile is able to select this cell, but it will not be able to perform a
call on it.
For a mobile Phase I: it is not possible to reselect a cell that is barred.
Nortel confidential

cellBarred cellBarQualify Priority

barred false no selection possible
barred true low
not barred false normal
not barred true low
Note: To forbid the access of a cell to a MS, the cellBarred set to “not barred” and
incomingHandover set to ”disabled”, is not sufficient. Care must be taken with the
cellBarQualify that gives the priority.
RESELECTION
There is only one kind of priority which is NORMAL.
IF the cell is barred

AND IF cellBarQualify is false
THEN the reselection is not authorized.

barred true normal
not barred true normal
Nortel confidential

4.4. 2G - 3G CELL RESELECTION

In v14.2, GSM to UMTS mobility is only provided to mobiles in Idle Mode using the cell
reselection algorithm with BSC12000 and BSC3000. The 2G-3G mobility in connected mode
is addressed by the 2G-3G Handover feature (V17).
This part only considers reselection from a GSM cell to a UMTS FDD cell.
As UMTS is deployed, if GSM access network does not provide "GSM to UMTS mobility" for
mobiles in idle mode, all the dual-mode mobiles (e.g. mobile supporting both GSM and
UTRAN/FDD radio access technologies) will be stuck on GSM cells:
• when leaving UMTS coverage the mobile will reselect a GSM cell
• when on a GSM cell a dual-mode mobile will only reselect a GSM cell
• switching off-on the mobile will not make the mobile reselect UMTS, since the
mobile is first looking for its last "Registered technology" at power on
• using a different PLMN for UMTS (being the mutimode subscriber HPLMN) and
GSM layers can help, but this will not work for the operators not taking this option
4.4.1 UE ALGORITHM IN GSM CIRCUIT MODE

Instead of the C2 criterion used in GSM only network, the dual-mode cell reselection uses a
criteria based on RLA_C (Received Level Averages for Circuit services), which is an
unweighted average of the received signal levels measured in dBm.
The UE starts measuring 3G cells when RLA_C in serving cell is below or above Qsearch_I
(depending on the value of Qsearch_I). Main reason is to save mobile battery.
The UTRAN/FDD neighbouring cell n is reselected by the UE if the 2 following conditions are
met:
(CPICH_RSCP(n) > RLA_Cserving + FDD_Qoffset) during 5 seconds
(CPICH Ec/No)(n) > FDD_Qmin
• CPICH_RSCP(n): is the Received Signal Code Power on one code measured on

the Primary CPICH
• (CPICH Ec/No)(n): is the received energy per chip on the Primary CPICH divided
by the power density in the band
The 1st condition ensures a minimum signal level is available from cell n.
The 2nd condition ensures the quality (level of interference) of cell n is acceptable.
The parameters used by the mobile to perform intersystem cell reselection are the following.
Nortel Parameter Name 3GPP Parameter Name Description

uMTSSearchLevel Qsearch_I Search for 3G cells if signal level is bellow
uMTSReselectionOffset FDD_Qoffset Applies an offset to C2 to cell re-selection to
access technology FDD UMTS access min level
uMTSAccessMinLevel FDD_Qmin A minimum threshold for Ec/No for UTRAN FDD
cell re-selection
Nortel confidential

Nortel Parameter Name 3GPP Parameter Name Description

uMTSReselectionARFCN FDD_ARFCN Neighbouring UMTS cell ARFCN
These parameters are controlled by O&M and broadcasted on BCCH in the System
Information 2quater message.
LCAUTION!
In order to enable the broadcasting of the SI2Quater on the BCCH the parameter
uMTSReselectionARFCN must be set to a non-null value.
PROCESS IN THE BSS
The cell reselection does not require any specific algorithm in the GSM-BSS. The intersystem
reselection only requires new piece of information to be broadcast on the BCCH by the GSM-
BSS:
• new intersystem cell reselection control parameters (as described above)

• neighboring UMTS cell list
The broadcast of this new information is ensured using the "System Information 2quater"
message.
When the information is updated (following a change at the OMC-R), the CHANGE MARK bit
is set to a new value.
The System Information 2quater is scheduled either on Normal or Extended BCCH (see
chapter SI2Quater & SI13 on Extended or Normal BCCH):
• If sent on Normal BCCH:

it shall be sent when TC = 5 if neither of 2bis and 2ter are used
otherwise it shall be sent at least once within any of 4 consecutive
occurrences of TC = 4
• If sent on BCCH Ext, it is sent at least once within any of 4 consecutive
occurrences of TC = 5
As a consequence, System Information 3 message has been updated in order to indicate to
the mobile:
• whether or not SI2quater is broadcast

• if broadcast is done on Normal or Extended BCCH
4.4.2 3G NEIGHBOURING CELL INFORMATION IN SI2QUATER

The GSM standard offers different possibilities to broadcast 3G neighbouring cell information
using SI2quater:
• 1) The BSS broadcast FDD_ARFCN and primary scrambling code for each of the
UMTS FDD neighbouring cells.
• 2) The BSS only broadcast FDD_ARFCN. This is the most simple solution from a
Network point of view.
Nortel confidential

In Nortel’s choice, neighboring cell scrambling codes will not be broadcast, and it will be
assumed that only one UTRAN/FDD carrier is deployed by cell, e.g. it possible to have
different carriers on different cell but only one per cell.
As it will take "some" additional time with that solution (the mobile have to decode the UTRAN
FDD neighbouring cells scrambling codes) 2 additional informations are provided and used by
the network and the mobile when the mobile reports measurement in connected mode:
• a one bit 3G-BA_IND field used to correlate the measurements with a neighbouring
cell list
• a Absolute_Index_Start_EMR used for building the neighbouring cell list in the
mobile. The value of this parameter is dynamic, and depends on the number of 2G
neighbouring cells (this allows shorter Meas. Report messages from the UE).
4.4.3 CONTROL INFORMATION IN SI2QUATER

The following Control information is broadcast by SI2quater message :
• FDD_Qoffset (uMTSReselectionOffset)
• FDD_Qmin (uMTSAccessMinLevel)
• Qsearch_I (uMTSSearchLevel)
Nortel confidential

4.5. LEGACY MEASUREMENT REPORTING
4.5.1 PRINCIPLE
Legacy measurement reporting consists in a mobile in dedicated mode - on a TCH or an
SDCCH - sending downlink signal measurements to the network, at regular intervals.
The BSS then uses these measurements in the uplink power control and handover
procedures.
4.5.2 NEIGHBOUR CELL MONITORING
DOWNLINK SIGNAL STRENGTH MEASUREMENTS
In this entire section, the mobile is assumed to be in dedicated mode.

While in dedicated mode, the mobile performs signal strength monitoring on all declared
neighbouring BCCH carriers. Signal strength measurements are done in every TDMA frame
on at least one of the BCCH carriers indicated in the BCCH allocation (BA), one after another.
As an exception, a dual-mode MS may omit GSM measurements during up to 9 TDMA frames
per SACCH multiframe and use these periods for measurements on UMTS.
Furthermore, an MS on SDCCH is allowed to schedule the measurements freely within the

multiframe as long as the total number of measurement samples is maintained and the
samples on each carrier are evenly spaced.
BSIC DECODING
It is essential for the MS to identify precisely which surrounding BTS is being measured in
order to ensure reliable handover. Because of frequency re-use with small cluster sizes, the
BCCH carrier frequency may not be sufficient to uniquely identify a neighbouring cell, i.e. the
cell in which the MS is situated may have more than one surrounding cell using the same
BCCH frequency. Thus it is necessary for the MS to synchronize to and identify the base
station identification code (BSIC). The 6-bit BSIC shall be transmitted by the network on the
SCH channel of each cell.
The MS shall use at least 4 spare frames per SACCH block period for the purpose of decoding
the BSICs (e.g. in the case of TCH, the four idle frames per SACCH block period). These
frames are termed "search" frames.
The MS shall attempt to demodulate the SCH on the BCCH carrier of as many neighbouring
cells as possible, and decode the BSIC as often as possible, and as a minimum at least once
every 10 seconds.
Nortel confidential

4.5.3 SERVING CELL MONITORING
DOWNLINK SIGNAL STRENGTH MEASUREMENTS
For each channel, the measured downlink RXLEV shall be the average of the received
downlink signal level measurement samples in dBm taken on the TCH or SDCCH channel
within the reporting period of length one SACCH multiframe.
Signal strength measurement samples shall be taken on all bursts of the physical channel that
carries the TCH or the SDCCH, including those of the SACCH.
DOWNLINK SIGNAL QUALITY MEASUREMENTS
The received downlink signal quality shall be measured by the mobile in a manner that can be
related to the average BER before channel decoding, assessed over all received bursts in the
multiframe, except bursts carrying a portion of a SACCH frame.
4.5.4 REPORTING PERIOD

A measurement report contains values averaged over samples collected over 104 TDMA
frames for a TCH (480 ms = duration of 4 TCH multiframes) and 102 TDMA frames for an
SDCCH (471 ms = duration of 2 SDCCH multiframes).
The mobile sends 1 measurement report every 480 ms for a TCH, and every 471 ms for an
SDCCH. Measurements performed during that measurement period are reported on the next
SACCH block occurrence.
The transmission of a single measurement report message is done on four consecutive bursts
of the SACCH channel :
• For a TCH, there is one SACCH burst available every 120 ms.
• For an SDCCH, the 4 SACCH bursts occur in 4 TDMA frames in immediate
succession, but these 4 TDMAs in succession occur once every 471 ms.
Note : The BTS also performs uplink signal strength and uplink signal quality measurements .
However, the BTS delays the processing of these uplink measurements by 480 ms or 471 ms
to ensure that they are synchronised with the downlink measurements from the mobile (i.e.
they relate to the same reporting period as the downlink measurements, which the BTS
receives with a 480 ms or 471 ms delay).
4.5.5 NEIGHBOUR CELL LISTS

Reporting with the MEASUREMENT REPORT message is usually performed on the BCCH
allocation list (i.e. GSM cells only), but could also use cells from the 3G neighbour list in the
case of 2G/3G mobiles.
Nortel confidential

The BCCH Allocation list is provided by the network to the mobile through SI5 messages on
SACCH. The number of neighbour cell BCCH carriers in the BCCH allocation cannot exceed
32.
The UTRAN neighbour list is provided to the 2G/3G mobile through Measurement Information
messages sent on SACCH.
4.5.6 MEASUREMENT REPORT CONTENT
2G MEASUREMENT REPORT
Each measurement report contains the following data :

• (neighbour cells) RXLEV_NCELL : RXLEV computed from samples taken on the
BCCH frequency of the 6 cells with the highest signal level. For each of the 6 cells, the
number of samples that is used to compute the RXLEV of that cell depends on the
total number of neighbours to be monitored (this number is the size of the BCCH
Allocation list).
• (serving cell) RXLEV_FULL : RXLEV computed from 100 (resp. 12) measurement
samples of the mobile’s TCH (resp. SDCCH). The samples are measured in each of
the 100 (resp. 12) TDMA frames that transmit either the TCH burst (resp. SDCCH) or
the SACCH burst, over the measurement period.
• (serving cell) RXQUAL_FULL : RXQUAL computed from 100 (resp. 12) measurement
samples of the mobile’s TCH (resp. SDCCH)
• (serving cell) RXLEV_SUB : For a TCH, RXLEV computed from 12 samples taken
from the 4 SACCH bursts and – in case of speech only - the 8 Silence Descriptor
(SID) frames. Not applicable for SDCCH because DTX is not allowed on SDCCH : in
that case, RXLEV_SUB = RXLEV_FULL.
• (serving cell) RXQUAL_SUB : For a TCH, RXQUAL computed from the same 12
samples as RXLEV_SUB. Not applicable for SDCCH and in that case, RXQUAL_SUB
= RXQUAL_FULL.
The mobile reports every 480 ms for a TCH and every 471 ms for an SDCCH.
3G MEASUREMENT REPORT
The measurement report is the same as for 2G, except for the RXLEV_NCELL of neighbour
UTRAN cells. The RXLEV_NCELL neighbour cell measurement is replaced by the appropriate
measurement for UTRAN. The measurement quantity reported by mobiles could be either
“CPICH RSCP” or “CPICH Ec/N0”. In Nortel implementation, mobiles are told by the network
to report only RSCP measurements on CPICH channels. However, the mobile selects the
UTRAN cells to report, based on internal measurements of the CPICH Ec/N0.
Nortel confidential

4.5.7 MULTIBAND REPORTING (V10)

For a multi band MS the number of cells, for each frequency band supported, which must be
included in the measurement report is indicated by the value of the parameter
MULTIBAND_REPORTING, broadcast by the network in SI2ter on BCCH and SI5ter on
SACCH.
The value of this parameter is set by the BSS parameter multiBandReporting (class 3, bts
object) :
• Value 0 : reporting of the six strongest cells, irrespective of the band used. No band is
favoured.
• Value 1, 2 or 3 : reporting of the 1, 2 or 3 strongest neighbour cell(s) in the non-
serving band. The remaining positions in the measurement report shall be used for
reporting of cells in the band of the serving cell. If there are still remaining positions,
these shall be used to report the next strongest identified cells in the other bands
irrespective of the band used.
4.5.8 UTRAN CELL REPORTING USING LEGACY MEASUREMENT

REPORTS (V17)
If GSM to UMTS Handover feature is enabled (see §4.8.24), the network may request the
2G/3G mobiles to report on UTRAN cells as well as on GSM cells, using either :
• Legacy measurement reports : this option is covered in this subsection.

• Enhanced measurement reports : this option is covered in §4.6
Note that 2G only mobiles never report UTRAN cells. UTRAN cells’ reporting only concerns
2G-3G mobiles and is performed by these mobiles using normal measurement reports only
when HO 2G-3G is enabled (parameter gsmToUMTSServiceHo not equal to
gsmtoUMTSDisabled) and EMR is disabled. In that case, the network informs the 2G/3G
mobiles of the type of measurement report to be used by sending a parameter called
REPORT_TYPE (3GPP name) / reportTypeMeasurement (Nortel BSS parameter name)
which can take only 2 values : “enhanced measurement report” or “normal measurement
report”. It is sent on SACCH inside a message called MEASUREMENT INFORMATION.
BSS PARAMETERS
The choice criteria of 2G and 3G cells that the 2G/3G mobile must include in the Measurement
Report in the list of the 6 cells are driven by 4 network parameters, the use of which is detailed
further on in this subsection :
• fDDMultiratReporting (v17, bts object)
• fDDreportingThreshold2 (v17, handoverControl object)
• qsearchC (v17, handoverControl object)
• multiBandReporting (v10, bts object)
Nortel confidential

PARAMETER FDDMULTIRATREPORTING (V17)
A 2G/3G mobile must report the number of best valid UTRAN cells belonging to the neighbour
cell list, according to the value of the parameter fDDMultiratReporting. fDDMultiratReporting
indicates the number of UTRAN cells that the 2G/3G mobile must include in the measurement
report.
The fDDMultiratReporting parameter is sent by the network to the 2G/3G mobile inside a
Measurement Information message on SACCH.
PARAMETER FDDREPORTINGTHRESHOLD2 (V17)
Only UTRAN cells with a CPICH Ec/No value equal or higher than fDDreportingThreshold2
shall be reported. If that criterion is met, the reported quantity is the CPICH RSCP.
“Valid” UTRAN cells are identified cells where the primary CPICH has been received when
using the scrambling code provided for that frequency in the neighbour cell list.
The fDDreportingThreshold2 parameter is sent by the network to the 2G/3G mobile inside a
Measurement Information message on SACCH.
PARAMETER MULTIBANDREPORTING (V10)
The remaining positions in the measurement report shall be used for reporting of GSM cells as
defined by multiBandReporting parameter. If there are still remaining positions, these shall be
used to report the next best valid UTRAN cells.
PARAMETER QSEARCHC (V17)
The qsearchC parameter is sent by the network to the 2G/3G mobile inside a Measurement
Information message on SACCH.
For a 2G/3G mobile, qsearchC defines a power level threshold (in dBm) and also indicates
whether these tasks shall be performed when RXLEV of the BCCH of the serving cell is
below or above the threshold :
• search for UTRAN cells if RXLEV of the BCCH of the serving cell is below
threshold (values 0 to 7): - 98, - 94, … , - 74 dBm, ∞ (always)
• or search for UTRAN cells if RXLEV of the BCCH of the serving cell iis above
threshold (values 8 to 15): - 78, - 74, … , - 54 dBm, ∞ (never)
If the serving cell is not included in the GSM neighbour list defined for handover purposes (this
is always the case according to Nortel Engineeering best practice), and if the dedicated
channel is not on the BCCH frequency, and if qsearchC is not equal to 15, then the mobile
must ignore the qsearchC parameter value and must always search for UTRAN cells.
If qsearchC is equal to 15, the MS must never search for UTRAN cells.
Nortel confidential

If the dedicated channel (TCH or SDCCH) uses the BCCH frequency, then qsearchC is
meaningful. However, in that case, the recommended Nortel value is 7 (always search for
UTRAN cells regardless of the downlink power level of the serving cell BCCH carrier).
Conclusion : with Nortel’s recommended value qsearchC = 7, the 2G/3G mobile is required to
always search for and measure UTRAN cells, regardless of the downlink power level of the
serving cell BCCH carrier
CELL CHOICE ALGORITHM
The MS fills the normal measurement report with measurements from 6 neighbour cells
chosen in the following order :
• Strongest valid UTRAN FDD cells :
o a valid UTRAN cell is an identified cell where the primary CPICH has been
received by the mobile when using the scrambling code provided for that
frequency in the neighbour cell list.
o to be eligible, a valid cell’s Ec/N0 must also be greater than

fDDReportingThreshold2.
o these valid and eligible cells are ranked according to the CPICH RSCP value
and the strongest are included first. The number of such reported cells is
defined by the fDDMultiratReporting parameter.
• Strongest GSM cells (including GSM cells of unknown BSIC) in each of the non-
serving frequency bands in the neighbour list. The number of such reported cells is
defined by the multiBandreporting parameter.
• Strongest GSM cells (including unknown BSIC) in the frequency band of the serving
cell. There is no limitation on the number of such reported cells.
• Remaining strongest GSM cells in each of the non-serving frequency bands in the BA
list.
• Remaining strongest UTRAN FDD cells.
Comments:
• Unlike EMR (§4.6), this algorithm does not discriminate between GSM cells with
known BSIC and GSM cells with unknown BSIC.
• Unlike EMR (§4.6), the RxLev of serving band GSM cells are not required to exceed a
reporting threshold.
• Unlike EMR (§4.6), the RSCP of UTRAN cells is not required to exceed a reporting
threshold.
• Unlike EMR (§4.6), UTRAN cells are included before GSM cells.
Nortel confidential

ENGINEERING RECOMMENDATION
Unlike EMR, a normal measurement report contains 6 cells. Therefore, it is necessary to

exercise caution when setting the parameters fDDMultiRatReporting and multiBandReporting.
These parameters define the number of UTRAN cells and non-serving band GSM cells,
repsectively, that must be included by the mobile in the list of strongest cells in the
measurement report. Therefore it leaves (6 - fDDMultiRatReporting - multiBandReporting)
spaces for the serving band cells.
Therefore, if EMR is disabled, it is recommended not to exceed fDDMultiRatReporting = 2 and
multiBandReporting = 2.
4.5.9 NOTE ON POWERCONTROLINDICATOR PARAMETER

powerControlIndicator is a BSS parameter that sets the value of the flag "PWRC". "PWRC" is
a field that is broadcast on BCCH channel inside SYSTEM INFORMATION n°3 messages.
PWRC = 1 is equivalent to powerControlIndicator = "do not include BCCH measurements"
PWRC = 0 is equivalent to powerControlIndicator = "include BCCH measurements"
The mobiles are required to interpret this flag as follows :

• if frequency hopping is not used : MS ignores the PWRC flag
• if frequency hopping is used and the BCCH frequency is not part of the Mobile
Allocation frequency list : MS ignores the PWRC flag
• if frequency hopping is used and the BCCH frequency is part of the Mobile Allocation
frequency list :
o if PWRC = 1 : in the RXLEV averaging process, the MS shall discard the
samples measured on the TCH channel's Downlink bursts that have been
transmitted by the BTS on the BCCH frequency
o if PWRC = 0 : in the RXLEV averaging process, the MS shall use the samples
measured on the TCH channel's Downlink bursts that have been transmitted
by the BTS on the BCCH frequency
In practice, in our networks :
• In case of Synthesized Frequency Hopping, there is one TRX which is dedicated to
transmitting the BCCH frequency all 8 Timeslots of the TDMA. If the BCCH frequency
was part of the hopping list of a TCH (on another TRX, of course), then there would be
systematic collisions. Therefore, in case of SFH, BCCH frequency cannot be part of
the hopping frequency list. Therefore, in case of SFH, the setting of
powerControlIndicator is irrelevant.
• In case of Baseband Frequency Hopping (BB FH is the only hopping scheme possible
with Cavity coupling), it is theoretically possible - but not recommended by Nortel - to
include the BCCH frequency in the hopping frequency list. If, in spite of our
recommendation, the BCCH frequency is part of the hopping frequency, then :
Nortel confidential

o if downlink power control is activated, then the TCH channel's Downlink bursts
transmitted on the BCCH frequency should not be used in the Rxlev
averaging process because, unlike the samples from other frequencies, they
are transmitted at full power : so, PWRC must be = 1 and
powerControlIndicator = "do not include BCCH measurements".
o if downlink power control is not activated, then the TCH channel's Downlink
bursts transmitted on the BCCH frequency may be used in the Rxlev
averaging process : PWRC = 0 and powerControlIndicator = "include BCCH
measurements"
4.5.10 NOTE ON RXLEV UPLINK/DOWNLINK DIFFERENCE

On the mobile side, every downlink sample is made up of measurements performed on
several bursts in dBm. On the BTS side, uplink measurements are performed in Watts. So, the
uplink RxLEv average is first computed in Watts before it is converted into dBm.
These two different ways of calculating the RxLev average yield results that are artificially
approximately 2,5 dB higher for the uplink than for the downlink (see chapter Difference
Between Uplink and Downlink Levels.
Nortel confidential

4.6. ENHANCED MEASUREMENT REPORTING (EMR)
4.6.1 PRINCIPLE
Compared to Legacy Measurement Reporting, Enhanced Measurement Reporting allows the
mobile to:
• Report more GSM neighbouring cells and, if required, 3G cells
• Enhance the information reported about the quality of the signal received by the
mobile (MEAN_BEP and CV_BEP, downlink FER).
Enhanced Measurement Reporting by the mobile may be used in the context of 2G-3G
handover but is not a mandatory prerequisite.
4.6.2 REPORTING PERIOD

Same as Measurement Reporting.
4.6.3 ENHANCED MEASUREMENT REPORT CONTENT

The Enhanced Measurement Report contains the following information :
• (GSM neighbour cells) RXLEV computed from samples taken on the BCCH frequency
of GSM neighbour cells with the highest signal level. The number of neighbour cells to
be reported belonging to the serving GSM band on the one hand, and to the non-
serving GSM band on the other hand, depends on the values of parameters sent by
the network multibandReporting (v10 parameter), servingBandReporting (v17.0
parameter), and servingBandReportingOffset (v17.0 parameter)
• (3G neighbour cells) The reported value for 3G neighbour cells is the CPICH RSCP.
The CPICH Ec/N0 is not reported in Nortel’s current implementation. The number of
neighbour cells to be reported belonging to the 3G technology depends on the values
of parameters sent by the network fDDMultiratReporting (v17.0 parameter),
fDDreportingThreshold (v17.0 parameter) and fDDreportingThreshold2 (v17.0
parameter)
• (GSM serving cell) : The reported values for the GSM serving cell are :
o RXLEV_VAL : The average over the reporting period of RXLEV measured on
bursts whose associated FACCH, SID, or traffic frame has been the last time
slots of each fully received and correctly decoded data block and on all
SACCH frames. For speech traffic channels, blocks that have not been
erased, shall be considered as correctly decoded. For non-transparent data,
blocks are considered as correctly decoded according the CRC received. For
transparent data, all blocks are considered as correctly decoded.
Nortel confidential

o MEAN_BEP : The average over the reporting period of the Mean Bit Error
Probability, computed from each fully received and correctly decoded data
block and from all SACCH frames.
o CV_BEP : The average over the reporting period of the Coefficient of

Variation of the Mean Bit Error Probability, computed from each fully received
and correctly decoded data block.
o RXQUAL_FULL : RXQUAL computed over the reporting period from 100
measurement samples of the mobile’s dedicated traffic channel TCH
o NBR_RCVD_BLOCKS : the number of correctly decoded TCH blocks that
were completed during the measurement report period.
4.6.4 NEIGHBOUR CELL LISTS

EMR reporting is performed on the Neighbour Cell List.
The Neighbour Cell List is the concatenation of 2 lists

• The GSM neighbour cell list
• The 3G neighbour cell list (if any)
GSM NEIGHBOUR CELL LIST
The GSM neighbour cell list is the combination of the BCCH Allocation list received in
SI5/SI5bis/SI5ter with the BSIC list received in one or more instance of the MEASUREMENT
INFORMATION message.
3G NEIGHBOUR CELL LIST
This applies only to a 2G-3G mobile. One or more instances of the Measurement Information
message may provide UTRAN Neighbour Cell Description information. This is used to build
the 3G Neighbour Cell list.
MAXIMUM LIST SIZE
In Nortel’s v17 implementation, the maximum number of cells of the lists in the Measurement
Information message is :
• maximum 32 UMTS cells
• If the 3G list is void, maximum 32 GSM cells
• If the 3G list is non-void, maximum 31 GSM cells
Nortel confidential

4.6.5 ORDER OF REPORTING PRIORITY OF NEIGHBOUR CELLS

The Mobile includes measurement results of neighbour cells using the following priority order:
• Highest priority : the number of strongest GSM cells with known and valid BSIC in the
frequency band of the serving cell, according to the value of servingBandReporting;
• 2nd highest priority : the number of strongest GSM cells with known and valid BSIC in
each of the frequency bands in the BCCH Allocation list, excluding the frequency band
of the serving cell, according to the value of multiBandReporting;
• 3rd highest priority : the number of best valid UTRAN cells with a reported value equal
or greater than fDDReportingThreshold in the 3G neighbour cell list, according to the
value of fDDmultiRatReporting. Additionally the CPICH Ec/No shall be equal or
greater than fDDReportingThreshold2. A valid cell is an identified cell where the
primary CPICH has been received when using the scrambling code provided for that
frequency in the neighbour cell list.
• 4th highest priority : the remaining GSM cells with known and valid BSIC or, if allowed
by the flag INVALID_BSIC_REPORTING, with known and allowed NCC part of the
BSIC in any frequency band.
• Last priority : remaining valid UTRAN cells
For each of the priority levels above, the mobile shall apply the following rules :
• if the number of valid cells is less than indicated, the unused positions in the report
shall be left for cells of lower priority;
• if there is not enough space in the report for all valid cells of a given priority, cells shall
be ranked according to :
o for GSM cells belonging to the serving band : RxLev +
servingBandReportingOffset. Note that this ranking criterion shall not affect
the value that is effectively included in the report, which remains RxLev.
o for GSM cells belonging to the non-serving band : RxLev. (reporting offset =
0)
o for UTRAN cells : RSCP. (reporting offset = 0)
4.6.6 MEASUREMENT INFORMATION MESSAGE
PURPOSE OF MI MESSAGE
The activation of EMR in the network requires the network to inform the relevant mobiles that
EMR reports are expected from them.
To do this, the network sends a new information message to the mobiles, called Measurement
Information. The Measurement Information message is regularly sent by the network to the
mobiles in dedicated mode on the SACCH, in addition to System information messages 5,
5bis, 5ter, and 6.
Nortel confidential

The following mobiles receive MI messages :

• 2G-3G mobiles that are at least Release 99
• 2G-only mobiles that are at least Release 4
CONTENT
In the version of EMR reporting currently implemented, the MI message contains essentially
the following information :
• EMR activation flag. The value of this flag is set by the reportTypeMeasurement
parameter.
• Information enabling the mobile to derive the full list of GSM neighbour cells, i.e.
(BCCH frequency, BSIC) pairs, that may be reported in EMR reports.
• INVALID_BSIC_REPORTING : 0 for disabled, 1 for enabled. When set to 1, report on

cells with invalid BSIC and allowed NCC part of BSIC is allowed. The value 1 is
mandatory if feature “switch interference matrix” is activated.
• Number of GSM neighbour cells of the serving band that the Mobile shall include in
the list of strongest cells in the EMR report (up to 3). The value of this number is set
by the servingBandReporting parameter.
• Threshold power level above which serving band cells may be reported among the
servingBandReporting number of reported cells. In v17 implementation, this threshold
is -110 dBm, meaning that all serving band cells may be reported regardless of their
power level.
• (applicable to multi-band mobiles only) Number of GSM neighbour cells of the other
band that the Mobile shall include in the list of strongest cells in the EMR report (up to
3). The value of this number is set by the multiBandReporting parameter (v10
parameter).
• (applicable to multi-band mobiles only) Offset to apply to the reported value when
prioritizing the cells for reporting for GSM serving frequency band. The value of this
offset is set by the servingBandReportingOffset parameter
• (applicable to 2G-3G mobiles only) UTRAN neighbour cell list : list of FDD (ARFCN,
scrambling code, diversity) triplets, identifying each 3G neighbour cell. The values of
these triplets are set by the following AdjacentCellUTRAN object parameters :
o fDDARFCN,
o scramblingCode,
o diversityUTRAN
• (applicable to 2G-3G mobiles only) UTRAN cells’ measurement parameters :
o Number of FDD cells to be reported in the list of strongest cells in the EMR
message. This number is set by the O&M network parameter
fDDMultiRatReporting.
Nortel confidential

o CPICH RSCP level above which the mobile will apply a higher priority to
UTRAN cells in the EMR message. The value of this level is set by the O&M
network parameter fDDReportingThreshold.
o CPICH Ec/N0 level above which the mobile will report UTRAN cells in the
EMR message. The value of this level is set by the O&M network parameter
fDDReportingThreshold2.
o Serving cell BCCH frequency power threshold above which, or below which,
the mobile may search for UTRAN cells. The value of this level is set by the
O&M network parameter qsearchC.
o Type of reporting quantity (value always equal to RSCP in v17

implementation)
RELATION WITH 2G-3G HANDOVER
Note that 2 different versions of the Measurement Information message may be sent by the
network depending on the mobile’s radio access capability (2G or 2G-3G) :
• If EMR reporting is activated but not 2G-3G handover (i.e. the gsmToUMTSServiceHo
parameter is set to "gsmToUMTSDisabled") :
o the BSC only sends 2G Measurement Information to the BTS. However, the
BSC does send the whole L1M configuration to the BTS. The BTS is therefroe
aware of the UTRAN neighbouring cells.
o The BTS only sends 2G Measurement Information messages to 2G-3G
Release 99 mobiles and Release 4 2G mobiles. Thus UMTS cells are hidden
from the mobiles so that mobiles do not report 3G measurement results in
vain, which could adversely affect their performance.
• If both EMR reporting and 2G-3G handover are activated (i.e. the
gsmToUMTSServiceHo parameter is not set to "gsmToUMTSDisabled") :
o the BSC sends to the BTS both the 2G Measurement Information and the
2G/3G Measurement Information messages.
o The BTS sends the 2G/3G Measurement Information to 2G-3G Release 99
mobiles and the 2G Measurement Information to the Release 4 2G mobiles.
4.6.7 MI/SACCH SCHEDULING

The scheduling of Mesaurement Information and System Information messages in the SACCH
channel is :
SI 5
SI5bis
SI 5ter
SI 6
Nortel confidential

MI
SI 5
... etc.
4.6.8 MAIN DIFFERENCES BETWEEN NORMAL AND ENHANCED

MEASUREMENT REPORTING
This section attempts at summarising the main differences between normal measurement
reporting (§4.5) and enhanced measurement reporting (§4.6).
MR EMR
An enhanced measurement report contains up to 32
A normal measurement report contains up to 6 neighbour cells
neighbour cells
No reporting offset is applied to rank cells. Competing cells are servingBandReportingOffset is applied to the RxLev of serving
ranked based only on the strongest RxLev (GSM) and RSCP band GSM cells for ranking purposes. No offset is applied for
(UTRAN) values non-serving band GSM cells and UTRAN cells
One (1) reporting threshold is used to define eligible UTRAN 2 reporting thresholds are used to define eligible UTRAN cells
cells : fDDReportingThreshold2 for Ec/No (non-reported : fDDReportingThreshold for RSCP (reported quantity) and
quantity). No threshold for RSCP. fDDReportingThreshold2 for Ec/No (non-reported quantity)
A parameter (fDDMultiRatReporting) defines the number of A parameter (fDDMultiRatReporting) defines the number of
UTRAN cells to be included in the report as a matter of priority UTRAN cells to be included in the report as a matter of priority
A parameter (MultiBandReporting) defines the number of non- A parameter (MultiBandReporting) defines the num ber of non-
serving band GSM cells to be included in the report as a serving band GSM cells to be included in the report as a
matter of priority matter of priority
A parameter (servingBandReporting) defines the number of
There is no required minimum number of serving band GSM
serving band GSM cells to be included in the report as a
cells in the report
matter of priority
GSM cells with known BSIC and GSM cells with unknown
GSM cells with known and valid BSIC have higher priority
BSIC are treated the same
UTRAN cells have top priority in the report Sering and GSM cells have top priority in the report
4.6.9 NEW BSS PARAMETERS

The following parameters are created in v17.0 and are needed to support Enhanced
Measurement Reporting :
Parameter name Definition Equivalent in GSM specification

Number of FDD UTRAN cells to be reported in the list
fDDMultiratReporting FDD_MULTIRAT_REPORTING
of strongest cells in the EMR message
defines the CPICH RSCP level above which the MS will
fDDReportingThreshold apply a higher priority to UTRAN cells in the enhanced FDD_REPORTINGTHRESHOLD
measurement report message
defines the CPICH Ec/N0 level above which the MS will
fDDReportingThreshold2 report UTRAN cells in the enhanced measurement FDD_REPORTINGTHRESHOLD2
report message
search for UTRAN cells if signal level on BCCH of
qsearchC Qsearch_C
serving cell :
Nortel confidential

is below threshold (0-7):

-98, -94, … , -74 dBm, ∞ (always)
or is above threshold (8-15):
-78, -74, … , -54 dBm, ∞ (never)
If the serving BCCH frequency is not part of the
BA(SACCH) list, the dedicated channel is not on the
BCCH carrier, and qsearchC is not equal to 15, the MS
shall ignore the qsearchC parameter value and always
search for UTRAN cells. If qsearchC is equal to 15, the
MS shall never search for cells on 3G.
type of measurement report to be reported on this cell :
reportTypeMeasurement enhanced measurement report or legacy measurement REPORT_TYPE
report
defines the number of cells from the GSM serving
servingBandReporting frequency band that shall be included in the list of SERVING_BAND_REPORTING
strongest cells in the measurement report.
If there is not enough space in the report for all valid
cells, the cells shall be reported that have the highest
sum of the reported value (RXLEV) and the parameter
XXX_REPORTING_OFFSET
servingBandReportingOffset servingBandReportingOffset
(XXX=900,1800,400,850,1900)
(XXX_REPORTING_OFFSET) for the serving GSM
band. Note that this parameter shall not affect the value
itself of the reported measurement.
4.6.10 IMPACT OF EMR ON INTERFERENCE MATRIX
IMPROVED ACCURACY
There are more GSM neighbours reported with EMR than with legacy measurement reporting
:
• With EMR, up to 32 GSM neighbours if no UTRAN cells are defined in the Neighbour
Cell List
• With standard MR, 6 neighbour cells.
This means that the statistical processing induces less systematic bias error in the case of
EMR.
GREATER NUMBER OF CYCLES
If no 3G cells are declared as neigbours, the number of cycles depends only on the number of
declared real neighbours and the number of fake neighbours, so it is not impacted by EMR.
However, if 3G cells are declared as neighbours, the maximum number of GSM neighbours
(real + fake) is 31 instead of 32. Therefore, more cycles may be required if 3G cells are
present in the Neighbouring Cell List.
Nortel confidential

CHANGE OF TRAFFIC DISTRIBUTION
If, during the Interference Matrix campaign in a dual band network, the reporting of serving
band neighbours is deliberately favoured by using the servingBandReportingOffset, then, as a
side-effect, the traffic distribution may be modified. This undesirable side-effect may in turn
modify the results of the IM measurements, whjich therefore may no longer reflect the real
situation in the field once the IM has ceased.
Therefore it is recommended to ensure that the chosen value of servingBandReportingOffset
does not cause unacceptable changes in the traffic distribution.
4.6.11 IMPACT OF EMR ON RADIO MEASUREMENT DISTRIBUTION

(RMD)
Thanks to enhanced measurement reports, the downlink FER indicator is available to the
network. Specific distributions are added for the different codec types.
Also, a distribution of estimated downlink voice quality is added. This indicator is based on the
same principle as MOS for uplink, but is a marginally less accurate because the mobile does
not provide the distribution of codecs used during the measurement period.
The post processing tool WQA is modified accordingly.
DOWNLINK FRAME ERASURE RATE
In the EMR message, the mobile provides the number of received traffic frames :
NBR_RCVD_BLOCKS. The BTS knows the number of times each codec have been used
during the measurement period so it is now possible to get a rough estimate of the probable
number of frames, per codec, that have not been decoded by the mobile and a rough
estimate, per codec, of the probable downlink FEP (Frame Erasure Probability). Note that
each sum of estimated number of bad frames is rounded to the nearest integer value at the
end of the connection.
Thanks to RMD feature, downlink FER distributions at the OMC-R level are made available
for the following types of circuit calls:
• EFR and FR speech calls,
• AMR FR speech calls,
• AMR HR speech calls.
DOWNLINK VOICE QUALITY INDICATOR
With EMR, it is possible to estimate the downlink voice quality (DVQI) in the same way as
TEPMOS estimates the uplink voice quality.
Distinction is done for the different codec types (EFR (and FR), AMR FR and AMR HR).
As the downlink FER per codec is an estimated one, the downlink voice quality indicator will
be less precise than TEPMOS, but the formula used to calculate DVQI is similar to the
TEPMOS one.
Nortel confidential

4.7. UPLINK MEASUREMENT PROCESSING
4.7.1 PRINCIPLE
Each sample on the uplink side used by the Layer 1 Management in the average computation
is composed of measurements performed in Watts on several bursts. So the uplink samples
are first computed in Watts before being translated into dBm.
The general idea is to perform arithmetic averages. These averages are stored, and each time
a decision has to be taken, an other average (weighted-average) is computed. This weighted-
average is based on a defined number (Hreqt) of arithmetic averages, which are weighted in
order to favor the latest results.
In the new version of the Layer 1 Management (L1mV2), the process of averaging is based on
fully sliding windows.
Examples for Hreqave = 8, Hreqt = 1, run xx = 4
Nortel confidential

4.7.2 AVERAGING PROCESS

• for quality and level:
rxLevHreqave, rxQualHreqave: number of measurement results to compute
an arithmetic average.
rxLevHreqt, rxQualHreqave: number of arithmetic averages necessary to
compute a weighted average, each one being associated to rxLevWtsList
and rxQualWtsList (highest weight for the most recent data).
missRxLevWt, missRxQualWt: weight applied to latest arithmetic average if
existing or latest received value to replace a missing downlink
measurement. In case there have been no previous measurements, a
default value is used.
• for distance, weighted average applies directly to distHreqt raw figures.
• for neighbor cells, only the arithmetic average is computed. Furthermore, for
L1mV2, when 10 SACCH blocks are missing, that cell is no longer considered and
corresponding data is deleted.
Note: cellDeletionCount is used as an eligibility criterion.
Arithmetic averaging is performed with xx_Hreqave period whereas weighted averaging is
done before algorithm processing, thus, weighted average is executed if run_xx is not a
multiple of xx_Hreqave.
Example for Hreqave = 3, Hreqt = 2, run xx = 4
Notes: In L1mV2, the weighted average is done with the latest not overlapped arithmetic
averages.
Reactivity of the L1mV2 has been improved. The measurements done by the MS and the BTS
during the first SACCH block period is proceeded by the BTS during the second SACCH block
period instead of the third SACCH block period.
Nortel confidential

4.7.3 RESCALING
Measurements are stored along with the MS and BS power level (meas_txpwr) reported in
MEAS RESULT, latest power control (MS or BS) is also stored (ref_txpwr).
From the L1mV2, rescaling is done at maximum transmission power (txPwrMax). It means that
the values or averages are adjusted as follows
newLev = oldLev + ((txPwrMax – meas_txPwr) * Pwr_to_dbm)
In this way BTS attenuation is already included in RxLevDL and handovers are better
anticipated.
4.7.4 MISSING DOWNLINK MEASUREMENTS

In case of Air interface problems, it’s possible to loose some SACCH blocks. Four rules of
substitution are applied to compensate for the missing measurements.
RULE 1
If averaged values are available, missing measurements are replaced by the latest averaged
value multiplied by a weighting factor (missDistWt, missRxLevWt, missRxQualWt).
r1 r2 r3 r4 r5 r6 r7 r8
m1 m5
m2
time
m3
m4
Example: If r8 is missing, then r8 = m4 X weighting factor.
RULE 2
If no average value is available, missing measurements are replaced by the latest

measurement value multiplied by a weighting factor (missDistWt, missRxLevWt,
missRxQualWt).
Nortel confidential

r1 r2 r3 r4 r5 r6 r7 r8
m1 m5
m2
time
m3
m4
Example: If r3 is missing, then r3 = r2 X weighting factor.
RULE 3
If no measurement value is available, the missing measurement is replaced by a default value.
r1 r2 r3 r4 r5 r6 r7 r8
m1 m5
m2
time
m3
m4
Example: If r1 is missing, then r1 = default value.
RULE 4:
In the following, the substitution of a missing value is only done when 6 neighbouring cells are
reported during the considered period.
From L1mV2 missing measurements for neighboring cells are replaced as follows; for both
cases, inputs are:
• Ncell1 no longer belongs to the list of 6 preferred cells at T+1 period,

• T, T+1 correspond to measurement periods.
First case:
IF RxLevNCell1(T) ≤ min(RxLevNCell(T+1) of the 6 reported cells)
THEN RxLevNCell1(T+1) = RxLevNCell1(T)
Second case:
Nortel confidential

IF RxLevNCell1(T) > min(RxLevNCell(T+1) of the 6 reported cells)
THEN RxLevNCell1(T+1) = min(RxLevNCell(T+1)) - missOffsetdB
missOffset has a fixed value of 3 dB.
Nortel confidential

4.8. DIRECT TCH ALLOCATION AND HANDOVER ALGORITHMS

Since V14, a new version of the Layer 1 Management (L1mV2) is applicable (see chapter
Measurement Processing)
LCAUTION!
It is understood in all the following formulas that RxLev_XX is computed with L1mV2.
4.8.1 GENERAL FORMULAS
PBGT
The general PBGT formula is computed in the band0 because HO_MARGIN is always specific
to the band0:
PBGT(n) = Min [msTxPwrCapability(Band0), msTxPwrMax]

- Min [msTxPwrCapabilityCell(n), msTxPwrMaxCell(n)]
+ (RxLevNCell(n)ave - RxLevDLave))
• msTxPwrCapability: maximum transmission power capability of the MS according

to the BCCH frequency (Band0) and its power class (§ 4.2.2).
• msTxPwrMax: maximum transmission power level the MS is allowed to use on a
traffic channel in the current cell.
• msTxPwrMaxCapabilityCell(n): maximum transmission power capability of the MS
(in the BCCH frequency band) of an adjacent cell (n), according to:
o the BCCH frequency band of the adjacent cell (n)
o the power class of the mobile in this band (§ 4.2.2)
• msTxPwrMaxCell(n): maximum transmission power level the MS is allowed to use
on a traffic channel of neighbour cell n (or the band0 of the neighbour dual band
cell n)
• RxLevNCell(n) ave: averaged downlink signal strength of the neighbour cell n
• RxLevDLave: averaged downlink signal strength of the serving cell
However, if the MS is in band1 the PBGT formula is changed.
Indeed, RxLevNCell(n)ave should be replaced by RxLevNCell(n)ave + biZonePowerOffset in
order to simulate what the field strength would be like in band0.
Nortel confidential

EXP1
The expression named EXP1 used for defining eligible cells:
EXP1(n) = RxLevNCell(n) ave - [ rxLevMinCell(n) + Max(0, msTxPwrMaxCell(n) -

msTxPwrCapability(n) ) ]
It is also used in the following process:
EXP1Capture(n) = RxLevNCell(n) ave - rxLevMinCell(n)
EXP1DirectedRetry(n) = RxLevNCell(n) ave - [directedRetry(n) + Max(0,

msTxPwrMaxCell(n) - msTxPwrCapability(n)]
EXP1Forced HO (n) = RxLevNCell(n) ave - [forced handover algo(n) + Max(0,

• RxLevNCell(n) ave: averaged downlink signal strength of the neighbour cell n

• rxLevMinCell(n): minimum RXLEV value required for a MS to handover towards
cell n
• msTxPwrMaxCell(n): maximum transmission power level the MS is allowed to use
on a traffic channel of neighbour cell n / in the band0 of the neighbour dual band
cell
• msTxPwrCapability(n): maximum transmission power capability of the MS
according to the power class of the mobile and the BCCH frequency (the band0)
of the neighbour cell n
• directedRetry(n): minimum signal strength level received by the MS to process
directed retry handovers in BTS mode
• forced handover algo(n): minimum signal strength level received by the mobiles to
be granted access to a neighbor cell in case of forced handover.
Note: If HO decision is made toward the inner zone of a multizone cell, then related
EXP1XX(n) is computed with biZonePowerOffset(n).
Nortel confidential

EXP2
The expression named EXP2 used for defining suitable cells:
EXP2PBGT(n) = Pbgt(n) - AdaptedHoMargin(n)
EXP2Traffic(n) = Pbgt(n) - [hoMargin(n) - hoMarginTrafficOffset(n)]
EXP2Quality(n) = Pbgt(n) - hoMarginRxQual(n)
EXP2Strength(n) = Pbgt(n) - hoMarginRxLev(n)
EXP2Distance(n) = Pbgt(n) - hoMarginDist(n)
EXP2AMR(n) = Pbgt(n) - hoMarginAMR(n)
EXP2bis(n) = rxLevDLPBGT(n) - RxLevDL ave
• AdaptedHoMargin(n): margin computed when AHA feature is enabled. It takes into

account neighDisfavorOffset and servingfactorOffset parameters (see chapter
Automatic handover adaptation)
• hoMargin(n): margin to be used for power budget HO
• hoMarginTrafficOffset(n): offset to be applied to hoMargin(n) for traffic HO decision
(when current cell is overloaded)
• hoMarginRxQual(n): margin to be used for quality HO
• hoMarginRxLev(n): margin to be used for signal strength HO
• hoMarginDist(n): margin to be used for distance HO
• hoMarginAMR(n): margin to be used for quality intercell HO defined for AMR TCH
channels
• rxLevDLPBGT(n): maximum downlink RxLev received from serving cell to allow a
power budget or traffic HO towards this NCell
Note: If HO decision is made in the inner zone of a multizone cell, then related EXP2XX(n) is
computed with (hoMarginXX(n) + biZonePowerOffset).
Nortel confidential

4.8.2 DIRECT TCH ALLOCATION

This chapter describes the Direct TCH Allocation feature which applies to the dualband cell,
the concentric cell and the dualcoupling cell features. Direct TCH Allocation has been
enhanced in v17.0.
PRINCIPLE
The principle of “Direct TCH Allocation” is manifold. It consists in the following aspects :
• At call setup, to allocate a FR TCH directly into the inner-zone of a multizone cell
• At call setup, to allocate an HR TCH directly into the outer-zone of a multizone cell
• At call setup, to allocate an HR TCH directly into the inner-zone of a multizone cell
• On intercell handover, to allocate a TCH directly into the inner-zone of the target
multizone cell.
At call setup, while the mobile is still on SDCCH (SDCCH is always allocated in the large zone
of a multi-zone cell), the BSC asks the BTS if the call (FR or HR) may be directed to the
appropriate zone by sending the BTS an “Abis Connection state request” message. The
acknowledgement of this request by the BTS provides the BSC with the information allowing
the BSC to decide to perform the requested TCH allocation.
The BTS uses several criteria to decide which zone is eligible. These criteria have been
altered in v17.0 as explained in the next section.
V17.0 ENHANCEMENT PRINCIPLE
Call setup
In initial phase of call establishment, the time spent on SDCCH is usually too short for the BTS
to compute a weighted average on downlink Rxlev measurement before the BST receives the
Abis connection state request from the BSC. Therefore, the allocation criteria for direct TCH
allocation use, by decreasing order of priority:
• a weighted average computed with RxLevHreqAve*RxLevHreqT latest measurements
(unlikely to happen on SDCCH).
• an arithmetic average computed with RxLevHreqAve latest measurements (unlikely to
happen on SDCCH)
• a short and fully reliable average (RxLevHreqAveBeg measurements) in the sense of
the Automatic handover Adaptation feature if this feature is enabled and if the MS is
fast enough or hopping on enough frequencies to filter the Raleigh fading.
• a short, not fully reliable average (from RxLevHreqAveBeg up to RxLevHreqAve-1
measurements) in all other cases.
In the last case, the v17 enhancement consists in the L1M compensating for the lower
reliability of the short average by adding the hoMarginBeg margin to the various allocation
thresholds. For all other cases, there is no change in v17.0.
Nortel confidential

Note : If hoMarginBeg parameter is set to 63, the Direct TCH allocation procedure only uses
normal averages.
Intercell handover
Some handover decisions (Early Power budget or Directed Retry) may be taken using less
than RxLevNcellHreqAve measurements on the neighbouring cell. So, the allocation
information for direct TCH allocation uses by decreasing order of priority:
• an arithmetic average computed with RxLevNcellHreqAve latest measurements.
• a short and fully reliable average (RxLevNcellHreqAveBeg measurements) in the
sense of the Automatic Handover Adaptation feature if this feature is enabled and if
the MS is going fast enough to filter the Raleigh fading
• a short not fully reliable average (from RxLevNcellHreqAveBeg up to
RxLevNcellHreqAve -1 measurements) in all other cases.
In the last case, the L1M now compensates for the lower RxlevNcell average reliability by
adding the hoMarginBeg margin to the BizonePowerOffset(n) parameter in order to ensure the
same grade of service.
Note : If hoMarginBeg parameter is set to 63, inter-cell handover Direct TCH allocation
procedure only uses normal averages.
DIRECT FR TCH ALLOCATION IN INNER-ZONE, AT CALL SETUP
In v17, if using a not fully reliable short average, hoMarginBeg is added to the following
thresholds :
• concentAlgoExtRxLev
CONCENTRIC CELLS
The criteria for a successful direct TCH allocation in the inner-zone are :
RxLevDL > concentAlgoExtRxLev
and
MS_BS_Dist < concentAlgoExtMsRange (timing advance criterion)
DUALBAND OR DUALCOUPLING CELLS
The timing advance criterion is disabled for a dualcoupling or dualband cell since the algorithm
only needs to check that the BS Tx power in the innerzone is sufficient to maintain the
communication.
For dualband cells, obviously, a test is also performed on the capability of the mobile to
support the band1.
The criterion for a successful direct TCH allocation in the inner-zone is :
Nortel confidential

RxLevDL > concentAlgoExtRxLev
DIRECT HR TCH ALLOCATION IN OUTER-ZONE, AT CALL SETUP
thresholds :
• amrDirectAllocRxLevDL
• amrDirectAllocRxLevUL
CONCENTRIC CELLS
The criteria for a successful direct HR TCH allocation in the outer-zone are :
RxLevDL > amrDirectAllocRxLevDL
and
RxLevUL > amrDirectAllocRxLevUL
The criteria for a successful direct HR TCH allocation in the outer-zone are :
RxLevDL > amrDirectAllocRxLevDL
and
RxLevUL > amrDirectAllocRxLevUL
DIRECT HR TCH ALLOCATION IN INNER-ZONE, AT CALL SETUP
thresholds :
• amrDirectAllocIntRxLevDL
• amrDirectAllocIntRxLevUL
CONCENTRIC CELLS
The criteria for a successful direct HR TCH allocation in the inner-zone are :
Nortel confidential

RxLevDL > amrDirectAllocIntRxLevDL
and
RxLevUL > amrDirectAllocIntRxLevUL
and
MS_BS_Dist < concentAlgoExtMsRange (timing advance criterion)
The criteria for a successful direct HR TCH allocation in the inner-zone are :
RxLevDL > amrDirectAllocIntRxLevDL
and
RxLevUL > amrDirectAllocIntRxLevUL
DIRECT TCH ALLOCATION ON INTER-CELL HANDOVER
In v17, if using a not fully reliable short average, hoMarginBeg is added to bizonePowerOffset.
If the target cell for handover is a multi-zone cell, the BTS is in charge of indicating to the BSC
if a TCH can be allocated in the inner zone of the target cell. This information is provided in the
"additional cells information” IEI within Abis Handover indication or Connection state ack
messages :
This capability (to handover directly in the innerzone/band1 of the adjacent cell) is inhibited
when biZonePowerOffset(n) is set to 63.
CONCENTRIC OR DUALCOUPLING CELLS
The criterion for the inner-zone of the neighbour cell to be eligible is :
RxLevNCell(n)ave > rxLevMinCell (n) + bizonePowerOffset (n) + Max(0, msTxPwrMaxCell(n) -

msTxPwrCapabilityCell(n) )
DUALBAND CELLS
The criteria for the inner-zone (band 1) of the neighbour dualband cell to be eligible are :
MS supports band 1 of NCell
Nortel confidential

and
RxLevNCell(n)ave > rxLevMinCell (n) + bizonePowerOffset (n) + Max(0, msTxPwrMaxCell(n) -

msTxPwrCapabilityCell(n) )
REMARK ON OUTER TO INNER ZONE INTRA CELL HANDOVER
It should be noted that the BTS provides the same allocation information to the BSC on an
intra-cell handover initiated from a TCH belonging to the Large zone. However, no
hoMarginBeg margin applies to allocation thresholds because a Weighted average is always
available.
4.8.3 HANDOVERS
Each runHandOver, after L1M initialisation process for handover, the BTS performs handover
decision process based on regular uplink and downlink measurements on the current cell
(level and quality) and neighbouring cells (level only); the main steps of this process are:
• Triggering: the BTS detects that a handover is needed by comparison with

thresholds: lRxLevXLH for alarm on level; lRxQualXLH for alarm on Quality;
msRangeMax for alarm on distance, there is no “triggering” for handover on PBGT
• Screening: the BTS determines what are the n best suitable cells (n=6 from V12)
for the handover (preferred cells list) and sends them to the BSC in the Handover
Indication message; to be in the preferred cells list, a cell must first be eligible
(eligibility checking) then sorted (Ncells list sorting); the preferred cells list is an
ordered list of sorted cells.
• Selecting: the BSC determines THE target cell according to the resource found
after reducing the preferred cells list to a maximum of three elements
• Executing: allocation, activation, assignment of the new channel, switching onto
this channel
HANDOVERS TRIGGERING
Intercell handover normally occurs for two main reasons:
• Rescue handovers: when the MS gets too far from the BS (Distance) and/or radio
link measurements show low received signal strength (DL/UL signal Strength)
and/or signal quality on the current serving cell (DL/UL signal Quality)
• Network Optimization Handovers: a better signal strength is available on an
adjacent cell (Power Budget), the serving cell gets overloaded (Traffic) or in the
particular case of a multilayer network (Capture)
Note: new intercell handover decisions have been introduced for AMR channels
Intracell handovers normally occur for the following reasons:
• Interference handover: radio measurements show a low received signal quality but
a high received signal strength on the serving cell.
• inter-zone handover from a "zone" of a multizone cell to another "zone".
Nortel confidential

• frequency tiering handover

• specific intracell handover for AMR TCH channels,
HANDOVERS SCREENING
To a given handover is associated (hard coded) a set of expressions used both to check
eligibility of a neighbour cell (a cell from the list of Ncells reported by the MS is eligible if all
expressions attached to this HO cause and neighbour cell are strictly positive) and to sort
target cells list.
See the chapter General formulas to get the detail of each expression.
According to the handover cause, the candidate cell’s expressions must then fulfil the
following formulas to be declared eligible
HO cause / connection state request type Eligibility criteria

powerBudgetInterCell(n) = true
EXP1(n) > 0
Power Budget EXP2PBGT(n) > 0
EXP2bis(n) > 0
deleteCounter(n) < cellDeletionCount(n)
trafficInterCell(n) = true
EXP1(n) > 0
Traffic
EXP2Traffic(n) > 0
EXP2bis(n) > 0
ul/dlQualityInterCell(n) = true
UL / DL signal quality EXP1(n) > 0
EXP2Quality(n) > 0
ul/dlSignalStrengthInterCell(n) = true
UL / DL signal strength EXP1(n) > 0
EXP2Strength(n) > 0
msBtsDistanceInterCell(n) = true
Distance EXP1(n) > 0
EXP2Distance(n) > 0
captureInterCell(n) = true
Capture
EXP1Capture(n) > 0
interBtsForcedHO(n) = true
Forced HO
EXP1ForcedHO(n) > 0
interBsDirectedRetry(n) = true
Directed Retry
EXP1Directedretry(n) > 0
ul/dlAMRQualityInterCell(n) = true
Quality intercell HO on UL / DL mode for AMR EXP1(n) > 0
TCH channels EXP2AMR(n) > 0
EXP2bis(n) > 0
Nortel confidential

4.8.4 HANDOVERS DECISION PRIORITY
HANDOVER DECISION FUNCTIONS FOR SDCCH & TCH/F CHANNELS
The whole set of HO decision functions currently implemented for non AMR channels, with
their priority, is defined in the table below (handover functions are executed in increasing order
of priority as shown below):
HO decision function early HO intercell HO priority comment

Capture false intercell 1
UL signal quality false intercell 2
DL signal quality false intercell 3
UL signal strength false intercell 4
DL signal strength false intercell 5
Distance false intercell 6
Power Budget true intercell 7
Traffic false intercell 8 (d)
Intracell on UL signal strength & quality false intracell 9 (a) (c)
Intracell on DL signal strength & quality false intracell 10 (a) (c)
Interband HO (dualband cells) false intracell 11 (b) (c)
Interband HO (concentric cells) false intracell 11 (b) (c)
Interband HO (dualcoupling cells) false intracell 11 (b) (c)
Frequency tiering false intracell 12 (a) (c)
Directed Retry false intercell 0
(a) intracell and tiering handover functions are exclusive from each other
(b) these handover functions are exclusive from each other (a given cell may be of only one
type among concentric, dual-coupling & dual-band) and do not apply to SDCCH channels.
(c) these intracell handover functions are ihnibited when in directed retry mode.
(d) only for a monozone cell or in the large zone of a multizone cell.
Note: The so-called "Directed Retry" handover is a "pseudo" handover indication message
sent upon request from the BSC. This specific case is mainly intended to provide BSC with a
target cells list for intercell HO and is discussed in chapter Directed Retry Handover.
Nortel confidential

HANDOVER DECISION FUNCTIONS FOR AMR TCH CHANNELS
HO decision function early HO intercell HO priority comment

Capture false intercell 1
quality intercell HO on UL codec mode false intercell 2
quality intercell HO on DL codec mode false intercell 3
UL signal strength false intercell 4
DL signal strength false intercell 5
Distance false intercell 6
Power Budget false intercell 7
Traffic false intercell 8 (d)
capacity intracell HO on UL / DL codec modes false intracell 9 (b) (c)
quality intracell HO on UL codec mode false intracell 10 (b)
quality intracell HO on DL codec mode false intracell 11 (b)
Interband HO (dualband cells) false intracell 12 (a) (b)
Interband HO (concentric cells) false intracell 12 (a) (b)
Interband HO (dualcoupling cells) false intracell 12 (a) (b)
Frequency tiering false intracell 13 (b)
Directed Retry false intercell 0
(a) these handover functions are exclusive from each other (a given cell may be of only one
type among concentric, dual-coupling & dual-band).
(b) these intracell handover functions are ihnibited when in directed retry mode or in dual
tranfer mode.
(c) this intracell handover function applies to TCH/AFS (Full Rate) channels only.
(d) only for a monozone cell or in the large zone of a multizone cell.
Note: The so-called "Directed Retry" handover is a "pseudo" handover indication message
sent upon request from the BSC. This specific case is mainly intended to provide BSC with a
target cells list for intercell HO and is discussed in chapter Directed Retry Handover.
Nortel confidential

4.8.5 DIRECTED RETRY HANDOVER

After the initial establishment procedure, if the MS is attached to a SDCCH and if there is no
TCH resource available, a directed retry handover is required.
The following parameters enable this feature:
• intraBscDirectedRetry (bsc)
• interBscDirectedRetry (bsc)
• intraBscDirectedRetryFromCell (bts)
• interBscDirectedRetryFromCell (bts)
Previously to V15.0, it is mandatory to activate the Queuing when the Directed Retry is
enabled. From V15.0, the feature “Directed retry without queuing activation” removes this
constraint and allows the activation indepently from queuing.
DIRECTED RETRY HANDOVER: BSC (OR LOCAL) MODE
This mode is enabled by the bts object parameter directedRetryModeUsed set to “bsc”. Until
V9, bsc mode could only be applied from a micro cell towards a macro cell (system rule).
One of the adjacent cells is predefined as the one used for directed retry. The
adjacentCellUmbrellaRef parameter gives the position of this cell in the neighbor list.
LCAUTION!
In this mode, there is no check of the RF conditions on the predefined target cell before the
directed retry HO occurs: the predefined cell must cover the whole area of the current cell.
To ensure that the MS is pre-synchronised with the predefined target cell (MS has decoded
GSM time and the BSIC), the neighbor cell BCCH must be put in the adjacentCellReselection
parameter bCCHFrequency.
Nortel confidential

DIRECTED RETRY HANDOVER: BTS (OR DISTANT) MODE
This mode is enabled by the bts object parameter directedRetryModeUsed set to “bts”. It is
used, for example in the case of a high traffic cell covered by several neighbors.
When the BSC receives the Assign Request message from the MSC, the BSC requests the
BTS through a Connection State Request message to return a list of eligible neighbor cells
generated by the following criteria. This list is immediately sent through a Connection State
Acknowledgement message to the BSC. If the list is empty, the BTS tries to regenerate it later.
As soon as handover conditions are fulfilled for at least one neighbouring cell, the BTS sends
the BSC a spontaneous Handover Indication message with the specific cause “Directed
Retry”.
If RxLevNcell(n) > directedRetry(n) + Max[0, (msTxPwrMaxCell(n) - P)]

where P = maximum RF output power of the MS
then cell n is candidate for Directed Retry Handover
If RxLevNcell(m) = Max(RxLevNcell(n))
then Cell m is chosen by the BSC as the target cell for the Directed Retry HO
LCAUTION!
The Directed Retry criterion is based on only one measurement of RxLevNcell(n) and not on
NCellHreqave measurements.
In a microcell network, a directed retry HO may handover a call from a macro cell to a micro
cell even if the stability criteria is not fulfilled (microcellular handover type A). In this
environment, to avoid a ping-pong HO, one may put a high value to the adjacentCellHandOver
parameter directedRetryAlgo.
DIRECTED RETRY AND QUEUING
Before V15.0, queuing must be activated to enable directed retry. In that case, when the BSC
receives from the MSC an Assignment Request and there is no TCH available in the cell, then
the request is queued and the directed retry procedure is started. The BSC sends to the MSC
a Queuing Indication message.
• If there is a resource in the target cell, the directed retry procedure is successful
and the communication is established, and the resources of the serving cell are
released
• If there is no resource available in the target cell, the directed retry procedure fails
and the request remains queued in the source cell until a TCH is available, the
timer associated to the queue expires (allocPriorityTimers), a handover indication
is received from the BTS and is successfully executed, or other events which lead
to the release of the communication (MS is lost, MS disconnect the call …).
Nortel confidential

• If there is no neighbouring cells indicated by the BTS in the connection state ack
message, then the request remains queued in the source cell until a TCH is
available, the timer associated to the queue expires, a handover indication (cause
“directed retry”) is received from the BTS and successfully executed, or other
events which lead to the release of the communication (MS is lost, MS disconnect
the call …).
In case the request could not be queued (queue full for instance), BSS sends an Assignment
failure (cause “no radio resource available”) message to the MSC.
From V15.0, as soon as the directed retry is enabled in the BSS, whatever is the queuing
activation, the directed retry is processed. In that case,
• if queuing is activated, it is the same behavior as before V15.0. The only change is
that if the request could not be queued, the directed retry (if allowed) is processed
independently from the queuing.
• If queuing is desactivated, (or if the request could not be queued), then the
procedure is as follow: when the BSC receives from the MSC an Assignment
Request and there is no TCH available in the cell, then the directed retry
procedure is started and the BSC sends to the MSC a Queuing Indication
message to inform the MSC of a delay in the TCH allocation, and the MS remains
on SDCCH channel.
If there is a resource in the target cell, the directed retry procedure is
successful and the communication is established.
If there is no resource available in the target cell, the directed retry
procedure fails and the BSS sends an Assignment failure (cause “no radio
resource available”) message to the MSC.
If there is no neighbouring cells indicated by the BTS in the connection state
ack message, it means that neighbouring cells information are not available
in the BTS (it depends also on the MS performances) or handover conditions
are not met. Then the BSC starts an internal timer
directedRetryWithNoQueuingTimer (5 seconds, non configurable) in order to
wait for a handover indication message (cause “directed retry”) the BTS
sends if the handover conditions are fulfilled. The BSC processes this
handover indication message as described here above. In case the timer
directedRetryWithNoQueuingTimer expires, the BSC sends an Assignment
failure message (cause “no radio resource available”) to the MSC.
Note: during a directed retry procedure, if there is no TCH available in the target cell, the
procedure can neither be queued, nor execute another directed retry from the target cell.
Nortel confidential

4.8.6 CONCENTRIC/DUALCOUPLING/DUALBAND CELL HANDOVER
CONCENTRIC CELL PRINCIPLES
From V9 a cell is defined as concentric if two pools of ressources (TDMAs) are defined using
Rxlev and optionally Timing Advance as allocation criteria. One or two types of TRXs can be
used.
From V12, the concept is enlarged and concentric cell parameter may have 4 possible values:
monozone, concentric, dualband or dualcoupling.
CONCENTRIC CELL
Definition: a cell is defined as concentric if it exists two transceiverzones configured to transmit

at different power resulting in two different coverage areas. For the two different
transceiverzones, the same antenna is used.
Outerzone
Innerzone
BCCH and
traffic signalling
channels channels
The principle of the concentric cells is to share the ressources in both zones assuming that the
TRXs are transmitting at different power. The BCCH and the signalling channels use the high
power TRXs (outer zone) thus the BTS needs to check if the link budget MS-BTS is sufficient
to allocate a ressource of the inner zone. Furthermore, to avoid a subsequent intracell
handover, the BSC is checking this condition with the BTS each time a first TCH has to be
allocated at the end of the call setup, i.e an Assign Request has been sent by the MSC. The
same checking is done by the curent BTS when an intercell handover is required.
The smaller range of the frequencies in the internal zone, due to low maximum available
power for transmission, means that these internal zone frequencies can be reused a short
distance away. With this greater re-utilization of frequencies an operator can achieve the same
coverage using less bandwidth.
From V12 functionalities have been deployed allowing an easier frequency planning in case of
frequency hopping (fractional reuse techniques), and a major enhancement with the TCH
allocation directly in the relevant zone in case of calll setup and handover.
Note: a configuration with HePA on the outer zone and ePA on the inner zone is a kind of
concentric cell and not a kind of dualcoupling cell, eventhough the biZonePowerOffset
parameter has to be set accordingly to that particular case.
Please refer to the associated Functional Note [R10] Concentric cell improvements
(CM888/TF889). See also chapter Concentric Cells.
Nortel confidential

DUALBAND CELL
Definition: a cell is defined as dualband if GSM900 TRXs and DCS1800 TRXs coexist and
share the same BCCH. The propagation loss being different, it results in two different
coverage areas.
Outerzone
Innerzone / band1 band0
GSM (or DCS)
DCS (or GSM)
BCCH and
traffic channels
signalling
channels
Main benefits of dualband cell functionality are:
• The number of cells to configure and monitor is roughly divided by two

• No BCCH pattern has to be defined in the second band
• Frequency Hopping, Power Control, Downlink DTX are available on all second
band DRX’s (instead of all but one with conventional management)
• Slight increase in capacity: one TS saving + DCS and GSM DRX’s in one pool,
which provides more network control of the traffic distribution
• Intra cells Handover between DCS and GSM DRX’s of a same cell instead of
synchronous inter cell handovers reduce the muting time
Please refer to the associated Functional Note [R9] Dual band cells management:TF875. See
also chapter Concentric Cells.
DUALCOUPLING CELL
Definition: a cell is defined as dualcoupling if the TRXs are not combined with the same type of
combiner and thus have not the same coupling loss resulting in two different coverage areas.
Outerzone
Innerzone
H2D
H4D
traffic BCCH and
channels signalling
channels
In a dualcoupling cell, as the TRXs are not combined with the same type of combiner the most
powerful TRXs define the large zone. Such cells are managed with the concentric cell principle
and dualcoupling cell feature take advantage of it using different coupling modules rather than
a mono type coupling module in a sector.
Please refer to the associated Functional Note [R11] FN for stepped coupling. See also
chapter Concentric Cells.
Nortel confidential

INTERZONE HANDOVERS FOR CONCENTRIC CELL / DUALCOUPLING

CELL
LARGE ZONE TO SMALL ZONE
The MS is permitted to migrate from the large zone to the small zone if:
• the MS is close to the BTS (Timing Advance used to estimate the MS to BTS
distance, only for concentric cells))
• and if RF conditions are good enough (RxLev downlink).
Note: The transceiverZone object parameter zone Tx power max reduction value is always set
to 0 for the large zone, and in the range of [1 to 55]dB for the small zone.
The Concentric/Dualcoupling Cell Handover from Large to Small zone is triggered if:
RxLev_DL > concentAlgoExtRxLev

AND (only for concentric cells)
MS_BS_Dist < concentAlgoExtMsRange
SMALL ZONE TO LARGE ZONE
The MS is handed over from the small zone to the large one if:
• the MS is far from the BTS (Timing Advance, used to estimate the MS to BTS
distance, only for concentric cells)
• or if RF conditions are too bad (RxLev downlink, RxQual uplink and downlink).
Nortel confidential

For a non-AMR channel, or an AMR channel with legacy L1M, the Concentric/Dualcoupling
cell handover from small to large zone is triggered if:
RxLev_DL < concentAlgoIntRxLev

OR
RxQual_DL > lRxQualDLH
OR
RxQual_UL > lRxQualULH
OR
(only for concentric cells)
MS_BS_Dist > concentAlgoIntMsRange
For an AMR channel with AMR L1M, the Concentric/Dualcoupling cell handover from small to
large zone is triggered if:
RxLev_DL < concentAlgoIntRxLev

OR
(only for concentric cells)
MS_BS_Dist > concentAlgoIntMsRange

OR
Quality intercell HO on UL codec mode criterion is satisfied
OR
Quality intercell HO on DL codec mode criterion is satisfied
Please note that an external priority [0...17] can be given to the Concentric Cell Handover from
a Small to Large zone, because of the small to large Zone HO priority parameter.
INTERZONE HANDOVERS FOR DUALBAND CELLS (FROM V12)
Convention:
• if BCCH gsm, then band 0 = gsm, band 1 = dcs and standardIndicator = gsmdcs
• If BCCH dcs, then band 0 = dcs, band 1 = gsm and standardIndicator = dcsgsm
The algorithms created for concentric cell are the same for dualband cells, except the timing
advance criterion is not used and the dualband capability of the mobile is checked.
Nortel confidential

SUMMARY OF CONCENTRIC/DUALCOUPLING/DUALBAND CELL HO
Interzone HO: band1 to band 0

Non AMR :
rxLevDL < concentAlgoIntRxLev
OR RxQual_DL > lRxQualDLH
OR RxQual_UL > lRxQualULH
OR (only for concentric cells) MS_BS_Dist>concentAlgoIntMsRange
AND (only for dual-band cells)
MS_Band_supported(standardIndicatorBand0) is true
AMR :
rxLevDL < concentAlgoIntRxLev
OR Quality intercell HO on UL codec mode criterion is satisfied
OR Quality intercell HO on DL codec mode criterion is satisfied
OR (only for concentric cells) MS_BS_Dist>concentAlgoIntMsRange
AND (only for dual-band cells)
Interzone HO: band0 to band 1
1) rxLevDL > concentAlgoExtRxLev
2) (only for dual-band cells)
3) (only for concentric cells) MS_BS_Dist<concentAlgoExtMsRange
Intracell intraband HO: band0 --> band0 or band1--> band1

normal intracell HO
Intercell intraband HO: band0 --> band0:

normal intercell inter or intra BSS
Intercell interband HO: band0 --> band1

1) EXP1(n) + biZonePowerOffset(n) > 0
2) EXP2PBGT(n) > 0
3) MS_Band_supported(standardIndicatorBand1) is true
Note : in v17, if only short not fully unreliable averages are available,
hoMarginbeg is added to bizonePowerOffset
Intercell intraband HO: band1 --> band1

1) EXP1(n) + biZonePowerOffset(n) > 0
2) EXP2PBGT(n) + biZonePowerOffset > 0
where PBGT uses msTxPwrMax2ndBand
3) MS_Band_supported(standardIndicatorBand1) is true
Note : in v17, if only short not fully unreliable averages are available,
hoMarginbeg is added to bizonePowerOffset
Intercell interband HO: band1 --> band0
Nortel confidential

1) EXP1(n) > 0
2) EXP2PBGT(n) + biZonePowerOffset > 0
where PBGT uses msTxPwrMax2ndBand
POWER ADAPTATION AFTER INTERZONE HO
In V17.0, the system implements a mechansim to compensate for the power gap between the
old and new channel channels in the inner (or outer) and outer (or inner) zones immediately
after a handover.
Please refer to the section Power adaptation after an interzone ho (V17).
Nortel confidential

4.8.7 RESCUE HANDOVER
INTRACELL HANDOVER DECISION FOR SIGNAL QUALITY
The interferences are generally related to a specific TDMA. When signal quality is bad but
signal strength is sufficient, the BSC allocates another channel in the current cell.
Condition to be fulfilled is:
(((RXLEV_UL > rxLevULIH) AND (RXQUAL_UL > rxQualULIH))

OR
((RXLEV_DL > rxlevDLIH) AND (RXQUAL_DL > rxQualDLIH))
Thresholds should be set in order to ensure good subjective voice quality (rxqualXLIH 5 with
frequency hopping or rxqualXLIH 4 without hopping).
This feature is enabled by intraCell or intraCellSDCCH flags.
LCAUTION!
In order to avoid the choice of a more interfered channel, channels are allocated in the 2 low
interference pools (hopping and not hopping); if no free channel is detected among these 2
pools and although queuing is allowed, the intracell HO must not be done; if queuing is
allowed, the request is queued then satisfied only after reception of suitable interference level
on idle channels (RF_RESOURCE_INDICATION message); when TDMA removals leads to
intracell HO, the first free resource is taken whatever its interference level.
Note: RF_RESOURCE_INDICATION message is received from BTS and induces the

interference level of channels of a particular TDMA. Therefore a channel has 3 states for the
BTS:
• Busy
• Free with interference measure level available
• Free without interference measure level available (for example the channel has just
been release and the measure are not yet done)
No interference level management is performed on PDTCH channels. The level status of
PDTCH resource is always high (bad level). So intracell HO is not performed on PDTCH
Nortel confidential

HANDOVER CONDITION FOR LEAVING A CELL ON RXQUAL
There is no parameter to disable this feature but this can be done by assigning thresholds
rxqual maximum value (7). Thresholds should be set in order to ensure good subjective quality
(rxqual 5 with frequency hopping or rxqual 4 without hopping).
This handover is triggered when quality exceeds signal quality thresholds:
(RXQUAL_DL > lRxQualDLH)

OR
(RXQUAL_UL > lRxQualULH)
HANDOVER CONDITION FOR LEAVING A CELL ON RXLEV
There is no parameter to disable this feature but this can be done by assigning threshold
RxLev minimum value (-110 dBm).
This handover is triggered when the signal strength falls below the following thresholds:
(RXLEV_DL< lRxLevDLH)
OR
(RXLEV_UL < lRxLevULH)
HANDOVER CONDITION FOR LEAVING A CELL ON DISTANCE
This feature is enabled by the msBtsdistanceIntercell parameter.
MS_BS_Dist > MsRangeMax
Nortel confidential

4.8.8 POWER BUDGET HANDOVER
POWER BUDGET FORMULA
If powerBudgetInterCell parameter is set to “enabled” (handover on Power Budget is allowed),

the following formula is used to determine handover condition for power budget reason. This
handover is preventive and ensures best allocation of a serving cell for a given
communication. The formula used to determine handover condition for power budget reason
is:
EXP2PBGT(n) = Pbgt(n) - AdaptedHoMargin(n)
AdaptedHoMargin(n) is the margin computed when AHA feature is enabled. It takes into
account neighDisfavorOffset and servingfactorOffset parameters (see chapter Automatic
handover adaptation)
MINIMUM TIME BETWEEN HANDOVER
From V12 this feature is replaced by the General protection against HO ping-pong feature.
However, in order for the new feature to be enabled the timeBetweenHOConfiguration
parameter must be set to “used”, and the bts Time Between HO configuration parameter must
be set to “1”.
4.8.9 HANDOVER FOR TRAFFIC REASONS (FROM V12)

This feature introduced in V12 aims at improving the network behaviour when one or several
cells are overloaded by attempting to redirect the most appropriate calls in progress to
neighbour cells with a PBGT handover procedure.
Please refer to the associated Functional Note [R12] Handover for traffic reasons: TF132. See
also chapter Handover for Traffic Reasons Activation Guideline.
This feature is enabled by the new BSC object parameter hoTraffic and by the new BTS object
parameter hoTraffic. For each neighboring cell of the cell (adjacentCellHandover object), a
parameter is defined: hoMarginTrafficOffset is the offset to (negatively) apply to the hoMargin
parameter linked to the power budget when the cell status becomes overloaded (if 0, the
handover for traffic reason is not allowed for this adjacent cell).
This features relies on the definition of the overload condition ; a cell overload condition can
only be determined by the radio resource allocator when the detection mechanism is
activated; it is activated as soon as the handover for traffic reasons feature or the Barring of
access class feature is authorized.
Nortel confidential

This overload detection mechanism is based on the number of free TCH or the number of
queued TCH requests in the cell ; TCH resources reserved for maximum priority requests are
not taken into account ; in a concentric cell, TCH resources of the small zone are not taken
into account (no queuing procedure in the small zone) ; in a dualband cell, TCH resources of
the band1 are not taken into account (no queuing procedure in the band1) ; no more operator
warning is sent at the beginning and the end of the overload phase.
The overload begins when:
the number of free TCH <= numberOfTCHFreeBeforeCongestion

OR
the number of queued TCH requests >= numberOfTCHQueuedBeforeCongestion
The overload ends when:
the number of free TCH >= numberOfTCHFreeToEndCongestion

OR
the number of queued TCH requests <= numberOfTCHQueuedToEndCongestion
When the cell status becomes overloaded, a request is done to the L1M to consider a new
ho_margin (hoMargin-hoMarginTrafficOffset) ; this request is sent only to the TRXs which
belong to the large zone/band0 (for concentric/dualband cells).
In case of intra BSS handover (for traffic reasons), the BSC checks the target cell status
during the handover selection phase and if overload condition is set, the BSC will try on the
following cell of the list (a handover between the band0 of a serving cell and the band1 of a
target cell is possible if the eligibility of band1 is indicated in the handover indication
message).
In case of inter BSS handover (for traffic reasons), the target cell overload status is not known
until the HO procedure is launched (HO request). Also, a handover between the band0 of a
serving cell and the band1 of a target cell is not possible (due to the present A interface).
It is advised to set the General protection against HO ping-pong feature with this feature in
order to overcome the associated risk of ping-pong.
LCAUTION!
This feature is not applicable for S4000/S2000E-DCU2 or S4000/S2000E-DCU2/DCU4.

This feature is applicable for all cases where PBGT handover is possible; so, handover for
traffic reasons is not possible between microcell and macrocell.
This feature is applicable to concentric/dualband cells but is restricted to the large zone/band0
since the thresholds used to define the overload conditions concern the large zone/band0 ; if a
handover indication is received by the BSC with a cause set to traffic reasons and concerns a
communication established in the small zone/band1 of the cell, the message is discarded.
Nortel confidential

This feature is not applicable to a network which sets all the TCH request priorities to the
maximum priority since the cell is always overloaded whatever are the cell overload
thresholds.
Since the handover for traffic reasons feature uses the PBGT handover procedure, the
powerBudgetInterCell parameter shall be set to “true” (the BSC does not control this flag to
modify the hoMarginTrafficOffset). The BTS never transmits the Handover for traffic reasons if
this flag is not set.
There is no standby chain updating for the cell overload status ; thus, in case of switch-over,
the L1M value for hoMarginTrafficOffset is set to 0 and the cell is no longer overloaded.
About hoMarginTrafficOffset setting:
Typically, when hoMargin is reduced by 1dB (which implies that hoMarginTrafficOffset=1 dB),
this affects around 13% of the mobiles, assuming that cell overlapping is larger than the
hoMargin; roughly:
• 1dB of power reduction decreases the cell radius by 6.8% thus the cell coverage
by 13%
• 2dB of power reduction decreases the cell radius by 14%
• 3dB of power reduction decreases the cell radius by 21.9%
If hoMarginTrafficOffset is set to 0 dB, the HO traffic is somehow disabled since PBGT will be
done before the traffic has a chance to be done (higher priority).
Nortel confidential

4.8.10 HANDOVER DECISION ACCORDING TO ADJACENT CELL

PRIORITIES AND LOAD (FROM V12)
The objective of this feature is to optimize the traffic distribution both between layers according
to cell priorities and cells of the same layer according to their overload conditions.
In the selection phase, the BSC places the cells in descending order according to their priority
and if cells have the same priority, the order given in the “handover indication” message is
maintained. Then, for those cells, the BSC calculates the following expression:
EXP4(n) = EXPi(n) – [offsetLoad(n) * stateLoad(n)]
where EXPi(n) = EXP1(n) for the handover causes capture or directed retry in distant mode
or EXPi(n) = EXP2(n) for other causes
EXP1 or EXP2 are added in the “handover indication” message from V12 ; offsetLoad(n) is a
neighbour cell parameter in dB and stateLoad is an overload status parameter.
stateLoad=1 for an intra BSS neighbor cell which is overloaded and 0 otherwise, including an
inter BSS neighbor cell overloaded ; the BSC sorts the cells that have the same priority by
decreasing values of EXP4 before reducing the preferred cells list from six to three.
offsetLoad(n) corresponds to the new offsetLoad parameter, offsetPriority defines the range of
the priority from 1 to 5 (1 is the highest level).
The overload detection relies on the same principle as that described in the Handover for
traffic reasons feature. If the overload detection is not activated, obviously, the priority is the
only criterion which is taken into account.
With such an algorithm, it can be noticed that the priority parameter is an important criterion in
a multi-layer network and that the overload situation is an important criterion in a network
where the cells have the same priority.
For multi-layer networks, a problem may occur when the higher priority cell (which captures
traffic) becomes consequently overloaded and then induces HOs for traffic in the other
adjacent cells ; this can be awkward when the overlapping area between the higher priority
cell and its adjacent cells is wide ; in such a case, too much traffic is captured and this
prevents from doing new calls in this cell.
In a network where the cells have the same priority, another problem could be noticed: the
overload condition of adjacent cells is not managed in a uniform way if the adjacent cells do
not belong to the same BSC ; the overload condition for cells belonging to another BSC is not
considered and may induce longer handover procedure if this one is overloaded. Indeed , the
overload state will only be known when the HO is triggered. Then, if the cell is overloaded, the
request will be refused and the BSC will try the next cell on the list of preferred cells.
Nortel confidential

4.8.11 AUTOMATIC CELL TIERING (FROM V12)
PREREQUISITE
It requires the implementation of L1mV2 and is exclusively applicable to fractional reuse

pattern networks (see chapter Frequency Hopping).
GOAL
The frequency tiering technique aims at decreasing the global interference level in a fractional
reuse pattern network and offers efficient traffic management at a TRX level through the self-
tuning system at the BTS
EXPECTED GAINS
The main benefits expected are:
• A large capacity increase: The cell tiering increases the fractional load capabilities,
therefore, permits bigger BTS configurations with the same amount of available
frequencies.). In a 1x1 network, the fractional load can go up to 33.3% and up to
100% in 1x3.
• A better network quality (worst communications, typically at the cell boundary, do
no longer corrupt other communications). The reduction of the global level of
interference may also significantly decrease the global number of dropped calls
and other faults in particularly loaded networks.
• A better uplink/downlink balancing (the uplink interference cancellation gain is
balanced by a significant downlink cell tiering improvement)
PRINCIPLES
The mechanism relies on simple dynamic resources allocation strategies that are intended to
allocate the worst communications, in terms of downlink Carrier on Interference ratio (CIR), to
the non-hopping frequencies (like BCCH), taking advantage of their larger reuse pattern and
consequently of their better resistance to interference, while the best communications are
driven to the hopping frequencies.
Evaluation of the calls is based on a ratio (in Watts) of the RxLevDL measured for the serving
cell over the sum of RxLevNCell measured for the BCCH of each neighbour, weighted
according to the type of interference brought (adjacent or co-channel).
This evaluation, called Potential Worst C/I (PWCI), potential because it does not include the
frequency hopping gain, is meant to simulate what the interference on the small pattern would
be like.
Nortel confidential

The PWCI is computed by the BTS for all the calls in progress in the cell and arranged into an
averaged PWCI distribution that provides 2 handover decision parameters: lCirDLH (low) and
uCirDLH (high):
• lCirDLH is the abscissa corresponding to an ordinate of P% (percentage of TCH

resources in the large pattern) on the averaged PWCI distribution curve.
• uCirDLH is determined from: uCirDLH = lCirDLH + hoMarginTiering
In V12 P% is calculated as follow:
Number of non hopping TCH - nbLargeReuseDataChannel

P%=
Total number of TCH in the cell - nbLargeReuseDataChannel
In V14, with AMR introduction P% is now calculated as follow:
(Number of non hopping TCH – nbLargeReuseDataChannel) * (1 + Non_FH_HR%)

P%=
(Total number of TCH in the cell – nbLargeReuseDataChannel) * (1 + HR%)
• FH_HR% is the percent of HR calls managed by the hopping pattern in the cell,
• HR% is the percent of HR calls managed in the cell.
The tiering handover decision can be summarised as:
• If PWCI > uCirDLH => HO is performed from large to small pattern

• If PWCI < lCirDLH => HO is performed from small to large pattern
The number of values required to trace the PWCI distribution curve may be modified via MMI
with the numberOfPwciSamples parameter (whereas cell tiering HO thresholds cannot be
tuned via MMI).
The lCirDLH is defined from the available traffic channels (i.e. TCH & PDTCH) in the non
hopping layer (because these one will be allocated to communications with worst PWCI). In
order to manage speech and data interworking, the averaged number of TCHs reserved for
data is defined with the nbLargeReuseDataChannels parameter.
To avoid the introduction of new configuration parameters or thresholds required by such a

function, the associated selfTuningObs functionality enables to set tiering working parameters
at their most relevant values, fitting with cell real radio profile and dynamically adapted to O&M
events or radio environment modifications ensuring that the gains of the tiering strategy are
always optimum.
Nortel confidential

Formula of PWCI in Watts:
RxLevDL Watts
PWCI=
SUM [RXLevNCell (i)] Watts SUM [RXLevNCell (j) - ADC] Watts
With
• RXLEV(0) the DL signal strength in Watts received from the serving cell, re-scaled
at maximum power (RxLev_DL + BS_Att)
• RXLEV (i) is the level in Watts measured on the BCCH of a neighbor cell using the
same TCH frequencies set as the current cell. These neighbors generate co-
channel interferences.
• RXLEV (j) is the level in Watts measured on the BCCH of a neighbor cell using a
TCH frequencies set different from that of the current cell. These neighbors
generate adjacent channel interferences.
• ADC corresponds to the first adjacent channel protection factor which is fixed in the
BTS software typically to 18dB
The PWCI value is the same whatever the effective load.
COMPATIBILITY WITH MULTIZONE CELLS
With concentric/dualband/dualcoupling cells, ACT is only applicable within the large zone.
Indeed, the tiering handover decision relies on the following algorithm:
• IF the TDMA bearing the considered channel belongs to the small pattern AND
does not belong to the small zone of a multizone cell:
IF pwCi < lCirDLH
THEN the channel will be put on the large pattern
• IF the TDMA bearing the considered channel belongs to the large pattern (which
implies that it belongs to the large zone):
IF pwCi > uCirDLH
THEN the channel will be put on the small pattern
Nortel confidential

In this case, P is computed by considering exclusively the resources in the large zone
(hopping as well as non hopping). In order to perform a tiering handover, the communication
must be in the large zone and there must be fractional reuse in it. The large pattern will only
be the BCCH frequency (the other TRXs in the large zone must hop) and the communication
will stay in the Large zone.
CELL TIERING MONITORING
The PWCI statistics and uCirDLH/lCirDLH may be transmitted on the Abis interface according
to the selfTuningObs parameter; these statistics are available independently of the activation
of the feature.
The hoRequiredTch counter C1138 has 2 new screenings (tiering handover from large to
small pattern and tiering handover from small to large pattern) ; two new counters are added:
C1802 (hoSuccessTieringTch) and C1801 (hoFailureTieringTchNorr) with 2 screenings each
(0: large pattern to small pattern & 1: small pattern to large pattern).
The table below gives indicative values for the time required to gather nbPwCISamples
measurements for different cell configurations, assuming the average TCH occupancy rate is
75% and that one TCH provides 1 PwCI measurement every 480 ms which is roughly 2 PwCI
measurements per second:
Cell configuration 20000 nbPwCISamples 60000 nbPwCISamples

O2 (14 TCH) # 16 min # 48 min
O4 (29 TCH) # 8 min # 24 min
O8 (59 TCH) # 4 min # 12 min
O16 (121 TCH) # 2 min # 6 min
The time required to reach a sufficient statistics as well as the time between two consecutive
tiering threshold updates depends on the number of samples required, and the capacity
(number of TCH) and load of the cell.
So a way to decrease the period between 2 consecutive threshold updates is about the half of
the time required to reach a first reliable statistics.
CAUTIONS
Because it takes advantage of BTS O&M centralization, this feature applies also to 2G
products (equipped exclusively with DRXs).
The activation of this feature implies a previous activation of the L1mV2.
The statistics (for PWCI) are not kept during upgrade and must be gathered again after the
site reconfiguration.
Intracell handover for quality and intracell tiering handover are exclusive (choice managed with
the intracell parameter of the handOverControl object). For mobiles at cells boundaries, if for
PBGT reasons, a handover is decided towards a new cell on a hopping TCH, a subsequent
handover for tiering reasons will be possible towards a non hopping TCH and so on, so
Nortel confidential

inducing a risk of ping-pong handovers ; this drawback will be avoided with the well tuning of
hoMarginTiering parameter.
No tiering handover decision is possible if the TDMA bearing the current TCH belongs to the
small zone/band1 of a multizone/dualband cell.
If tiering is activated, no tiering decision is undertaken by the BTS as long as a reliable
statistics has not been gathered (minimum nbPwCISamples for PWCI measurements); field
experiments have shown that at least 20000 PWCI samples are needed.
In V12, statistics are not maintained on the BCF passive chain.
The cell tiering configuration relies on a correct definition of interferes for each cell (through
interfererType). This feature is based on values of PWCI that depend on the overlap, the
available spectrum and the sites' density but neither on the traffic nor the fractional load.
However, when the traffic is low, there are fewer samples than at the busy hour and the PWCI
distribution is therefore a touch less relevant.
Nortel confidential

4.8.12 MICROCELLULAR HANDOVER
HANDOVER PECULIARITIES IN MICROCELL ENVIRONMENT
Microcellular algorithms were initially defined to avoid issues due to fast moving mobiles
connected to microcells. People thought that fast moving mobiles would not have enough time
to receive handover information coming from the network or would jump some microcells. To
avoid communication failures, specific handover algorithms were defined to send fast moving
mobiles to the macro layer.
However, experiments performed on several microcellular networks demonstrated that fast
moving mobiles linked to outdoor microcells do not present any issues. Microcellular
algorithms are used mainly to split traffic loads on the two layers, regardless of mobile speed.
Most microcellular algorithms are based on a “capture” threshold. Mobiles linked to a
macrocell perform a handover towards the micro layer as soon as the field strength received
from a microcell is sufficiently high (whatever the field strength received from the macrocell)
for a sufficient duration.
The microcellular handover algorithm type A is also based on the stability of the signal. Before
V12, with L1mV1, the stability was checked on the best neighbouring microcell, now L1mV2
launches in parallel the confirmation process for the 6 best microcells.
L1mV2: Selection of the 6 best microcells
MS stability check on these 6 microcells
Selection of the 6 new best microcells

(transmitted to BSC)
Handover execution
MICROCELLULAR ALGO TYPE A
The following table describes permitted handover causes according to the type of the serving
cell and the neighbor cell.
Note: the traffic handover is only possible from a large zone (or monozone).
The capture handover algorithm can only be defined from a macrocell to a microcell. However
the type of a cell is defined relative to the type of the neighboring one. It means that the type of
a cell A can be a macrocell from the cell B point of view but can be a microcell from the cell C
point of view. This way, it is possible to use the capture handover algorithm on both sides,
macrocell to microcell and microcell to macrocell.
Nortel confidential

Neighbour cell cellType [adjacentCellHandover]

normalType umbrellaType microType
signal quality
signal quality signal quality
signal strength
signal strength signal strength
distance
distance distance
power budget
normalType power budget power budget
traffic
traffic traffic
directedRetry (BTS
directedRetry (BTS mode) directedRetry (BTS mode)
mode)
forced handover forced handover
forced handover
Serving cell cellType [bts]
signal quality
signal quality
signal strength
signal strength
distance
distance capture
power budget
umbrellaType power budget directedRetry (BTS mode)
traffic
traffic forced handover
directedRetry (BTS
directedRetry (BTS mode)
mode)
forced handover
forced handover
signal quality
signal quality
signal strength signal quality
signal strength
distance signal strength
distance
power budget distance
microType power budget
traffic directedRetry
traffic
directedRetry (BTS (BTS mode)
directedRetry (BTS mode)
mode) forced handover
forced handover
forced handover
However the Type A handover algorithm has not been specifically defined to perform
handovers from microcells to the macrocell layer.
A timer linked to that algorithm is tunable via the microCellCaptureTimer parameter. That timer
prevents the BSC from doing a handover on capture reason during a fixed period.
See also General formulas for the capture expression:
EXP1Capture(n) = RxLevNCell(n) ave - rxLevMinCell(n)
Furthermore a strength level stability Criterion (microCellStability) has to be respected before

triggering a handover toward the microcell.
While microCellCaptureTimer(n) goes on, if a normal handover decision is verified, a handover
towards a cell of the same type or a normal cell is allowed.
While a handover is decided, the list of eligible cells is provided at each runHandover
(microCellCaptureTimer (n) is not reinitialised).
The threshold microCellStability(n) must be put previously to 63 dB. This value ensures that a
handover is performed as long as the field strength received from the neighbor cell is higher
than the “capture” threshold. The value can then be reduced case by case.
Nortel confidential

LCAUTION!
The microcellular feature is an OMC-R option (must be activated at OMC-R installation).
From V15.1 and thanks to the Advanced Speech Call Items Evolution functionality (refer to
[R30]) the range of the microCellCaptureTimer has been modified.
Initially that modification was designed for GSM-R applications: microcellCaptureTimer at 500s
is to avoid to be captured by a railway station cell for a communication established in the train
and thus to avoid that an on going communication from a train arriving in a railway station with
no stop, is captured by the railway station cells and when leaving the railway station, leads to
a new handover to the railways track cells.
Before V15.1 microCellCaptureTimer, on adjacentCellHandover object, has a range [0 … 255]
which means a maximum of about 255 * runHandOver (runHandOver is expressed in
multiples of 480 ms for SACCH frames and multiples of 470 ms for SDCCH frames) for a
communication, before being captured by a neighbouring cell which has a minimum and a
stable rxlev during this period.
The request consists in increasing the range of this parameter, so as it is kept as it is, but the
meaning of specific values are changed to give them greater values (conversion to a value
greater than 255).
microCellCaptureTimer microCellCapture value used by the BTS for the computation

value received by the BTS (number of reporting period x*480ms)
0 to 249 0 to 249
250 512 Æ 245 s
251 1024 Æ 491 s
252 2048 Æ 983 s
253 4096 Æ 1966 s
254 8192 Æ 3932 s
255 16384 Æ 7864 s
This table is applicable for a runHandOver = 1. If runHandOver = 2, then 491 seconds are
obtained with MicrocellCapture value set to 250.
Note: if the Handover on SDCCH feature is activated, the timer must be computed by
multiplying the BTS used value by 470 ms.
Nortel confidential

4.8.13 FORCED HANDOVER

This feature is used to force a handover towards neighboring cells. If a cell is to be shut down,
forcing handovers avoids dropped calls.
It has to be used in addition to the soft blocking feature (barring of incoming Handover, barring
of new calls).
Through a Connection State Request message, the BSC requests that the BTS sends it a list
of eligible neighbor cells. This list, immediately sent through a Connection State
Acknowledgement message to the BSC, is generated by the following criteria:
EXP1Forced HO =(n) RxLevNCell(n) ave - [forced handover algo(n) + Max(0,

By putting a low value to forced handover algo(n) , the HO becomes easier: the cell is
released more rapidly.
LCAUTION!
A forced HO is possible after a certain communication duration:
duration = Max( rxQualHreqave * rxQualHreqt, rxLevHreqave * rxLevHreqt,

rxNCellHreqave).
Therefore, when integrating this feature in the soft blocking procedure, the operating mode is
the following:
• soft blocking,
• wait a certain time (20 seconds),
• trigger the forced HO.
There is only one attempt per cell.
Another reason to use a Forced HO with soft blocking is that a Forced HO may interrupt a
Directed Retry HO (if the Connection State Request message of the Forced HO arrives before
the Handover Indication cause Directed Retry message). One must wait a period of time after
the soft blocking so that all calls have time to move from SDCCH channels to TCH channels.
Nortel confidential

4.8.14 EARLY HANDOVER DECISION
PROBLEM DESCRIPTION
The time for a mobile to reselect a cell in idle mode is quite long. So, a mobile can start a
communication while camping in another cell, leading to a call drop in the worst case.
cell A actually selected
cell B
cell A
End Beginning
of last call of new call
If the reselection algorithm execution occurs close to the border of cell A the mobile can setup
a call a short moment after in the cell B while the cell A is still selected. Unfortunately, the MS
has to wait a certain period of time before being able to make an handover. The system has to
perform some measurements before taking some handovers decisions.
This period of time is quite critical, there are some risks of call drop because of the low level of
the signal.
Another issue is concerned by this feature ; that is the problem of a mobile turning at a street
corner, when the RxLev suddenly decreases in the serving cell and increases for a neighbour
cell.
FEATURE DESCRIPTION
The principle is not to speed the selection process but to allow a handover on PBGT quicker.
Cell A
1
Risk 1 sel/reselection
of algo execution
call 2 call setup in cell A
drop 3 HO toward cell B
2
3 Cell B
Time
Nortel confidential

From V11, two shorter averages are defined for the level of the serving cell
(rxLevHReqaveBeg) and for the level of the neighbouring cells (rxLevNCellHReqaveBeg).
The L1M will use this new shorter averages at the beginning of the call until Max
(rxLevHreqave*rxLevHreqt, rxQualHreqave*rxQualHreqt) is reached and after loss and
recovery of BSIC.
So from V11, the L1M must only wait:
• shorter level arithmetic average of serving cell (rxLevHReqaveBeg)

• shorter level average of the neighbouring cell (rxLevNCellHReqaveBeg)
Therefore, the handover can be performed more quickly and with less measurements.
The principle is not to speed the selection process but to allow a handover on PBGT quicker.
It allows to reduce the zone which represents the critical period of time. The first impact of this
feature is to reduce the probability of establishment failure and the call drop ratio.
A third parameter has been created (HOMarginBeg) in order to compensate the lack of
measurements by increasing the HOMargin.
The parameter rxLevNCellHReqaveBeg is used each time a new cell is detected by the
mobile. Therefore, it increases the system reactivity.
EXP2PBGT(n) early = Pbgt(n) - [hoMargin(n) + hoMarginBeg(n)]
UNTIL
Max(rxLevHreqave * rxLevHreqt, rxQualHreqave * rxQualHreqt) is reached
4.8.15 MAXIMUM RXLEV FOR POWER BUDGET

One of the issues to solve, in a microcellular network, is street corner (cross road)
environment:
In case of mobile moving straight the cross road (two orthogonal cells A and B), a handover
for Power Budget may be processed from cell B to cell A. Once the cross is passed, the
mobile is handed again over the cell B.
This ping-pong handover shall be avoided as useless handover leads to voice quality
degradation and signalling increase.
Another advantage of this feature is the possibility to reduce unnecessary handovers at border
of Location Area, interBSC or interMSC HO. In this case the need to perform Power Budget
handovers is diminished against the extra load on NSS and the voice quality.
The feature provides a solution by preventing handover for power budget from the serving cell
if the RXLEV downlink serving cell level exceed a specific threshold
To prevent handovers for power budget from the serving cell if the RXLEV downlink serving
cell level exceed a specific threshold (rxLevDLPBGT), the following expression used in
combination with existing cell selection criteria is actually:
RXLEV_DL < rxLevDLPBGT
Nortel confidential

4.8.16 PRE-SYNCHRONIZED HO
During an asynchronous handover, the MS repeats the HO access bursts until it receives the
physical information message containing the timing advance of the new cell. So the speech
cut duration may last as long as the MS receives the new TA (Timing Advance) applied in the
new cell.
The pre-synchronized handover feature allows a Phase 2 MS to make a synchronized
handover between two (2) cells not belonging to the same site but managed by the same
BSC. The procedure is the same as for an intra-site synchronized handover, excepted that the
TA is set in advance and is transmitted to the MS at the beginning of the HO procedure.
LCAUTION!
Only intra BSC synchronized handover are possible.
There are two possibilities to set the timing advance in case of pre-synchronized HO:
Presynchro with default value or with a determined Timing Advance.
Two parameters are impacted in the adjacentCellHandOver object to enable this feature:
• synchronized is set to the value “pre sync HO, with timing advance” or “pre sync
HO,default timing advance”.
• preSynchroTimingAdvance indicates the value of the TA.
By comparing not synchronized handovers with synchronized handover, a phonetic gain from
20ms to 40 ms is expected. This is due to the Physical_Info message suppression, which is
not necessary because on pre-synchronized handover, the timing advance value is carried by
the Handover_Command message. Moreover, only four Handover_Access messages are
used on pre-synchronized handover instead of more than four in case of not synchronized
handover.
4.8.17 RADIO CHANNEL ALLOCATION

The radio channel allocation is based on the interference levels computed on the BTS free
channels (SDCCH and TCH).
Every averagingPeriod the BTS sends RF RESOURCE INDICATION messages to the BSC.
These messages are related to one TRX and contain the level of interference of the free
channels. These interference levels are classified into one from the five possible interference
bands (thresholdInterference parameter). In each of the five bands, the resources are sorted
from the least to the most recently used.
At the BSC level the free channels are divided into two new groups depending on whether
their interference level is above or below the RadChanSellIntThreshold value. Each group is
itself divided into two sub-groups, depending on whether the resource supports the Frequency
Hopping.
Nortel confidential

LCAUTION!
• If, during three (3) successive RF RESOURCE INDICATION messages, an
incoherency is noticed at the BSC level concerning the avaibility of a radio
channel, the channel is released and is returned free to the allocator.
• When a resource is released upon a call termination, it always returns to the pool
of worst interference level, whatever its level before the allocation. The next
measurement received from the BTS for this resource will be used to update the
level and, consequently, to find the appropriate pool.
• The inner zone of a concentric cell does not support SDCCH channels. Till V11,
although they belong to the same cell, TCH pools for the inner zone are separated
from the same pools of the outer zone, and there are no possible channel
exchanges between the two zones.
• When a SDCCH is requested and no SDCCH is available, the external priorities
are considered as a TCH can be allocated instead of a SDCCH, following the TCH
allocation principles.
• If a TCH is requested and the priority threshold is reached, only priority 0 requests
will be served. Other priorities will generate negative responses from the allocator.
4.8.18 DEFINE ELIGIBLE NEIGHBOR CELLS FOR INTERCELL

HANDOVER (EXCEPT DIRECTED RETRY)
When an intercell handover is required, the BTS sends a list of at most n best suitable cells
(n=6 from V12) according to EXP1 and EXP2 formulas.
The following diagram shows an example of cell interlapping produced by different values of
lRxLevDLH (threshold out of Cell A) and rxLevMinCell (threshold in Cell B, assuming it is a 2W
mobile and msTXPwrMaxcell is set to 33dB). If values are too restrictive, then Cell B will not
be considered as an eligible cell for handover and the call might be dropped. This might be the
case especially in rural areas where cells have little overlap.
Putting a high value for rxLevMinCell(n) or a high value for msTXPwrMaxCell(n) results in
restricting access to that cell (see following diagram).
Cell A Cell B
lRxLevDLH rxLevMinCell (B)
-100 dBm -95 dBm
HO 1 HO 2
-98 dBm -92 dBm
There is a different margin for each handover cause:
hoMarginDist, hoMarginRxLev, hoMarginRxQual (can be negative), hoMargin (for power

budget), thus compliance to that formula becomes mandatory i.e a handover can only be
performed towards a neigbourCell for which the (PBGT(n) - hoMargin(dist, rxqual, rxlev)) is
positive.
Nortel confidential

4.8.19 HANDOVER TO 2ND BEST CANDIDATE WHEN RETURN TO

OLD CHANNEL
This feature is triggered by a handover failure during the execution phase.
If hoSecondBestCellConfiguration = 1
then no HO attempt to 2nd best candidate cell
then HO attempt to 2nd best candidate cell
then HO attempt to 2nd best candidate cell and to 3rd best candidate cell
(if the HO attempt to 2nd best candidate cell fails)
When the HO attempt towards the last candidate fails, the bssMapTchoke starts at the BSC.
At the expiry of the timer, the BSC asks the BTS to provide a new list of eligible cells.
4.8.20 PROTECTION AGAINST RUNHANDOVER=1

The objective is to get a more responsive handover detection mechanism. To reach this goal,
the HO algorithm shall be run every 480 milliseconds (i.e runHandover =1 SACCH period).
This feature is useful for call drop rate improvement.
With this configuration (runHandover=1), a protection shall be implemented to avoid BSC

overload.
In case of saturated network (no free TCH) the request for handover (HO-Indication message)
will be repeated every 480 ms by the BTS, even if the target cell list has not changed.
This could cause SICD overload problems at the BSC. Although the BSC is protected against
this, such a situation should be avoided as much as possible in order not to disturb cells not
concerned by the congestion situation that could also be supported by the overloaded SICD.
As a consequence, the HO_Indication shall be repeated every 2 SACCH periods (1 second) in
case of run HO = 1.
If the content of the “preferred cell list” IE is modified (i.e. the content or the order of the cell
list), the HO_IND message shall be repeated every runHandover (even if runHandover=1).
In addition to that, the HO_IND message has also to be sent if the reason for handover has
changed, for the reason that there is no “preferred cell list” IE in case of intracell handover for
example.
The value of 1 second is justified by the fact that existing operational networks are currently
working with the value of runHandover=2, and therefore no strongest protection is needed.
Nortel confidential

4.8.21 GENERAL PROTECTION AGAINST HO PING-PONG (FROM

V12)
This feature allows to easily solve some ping-pong handover problems (like ping-pong after
directed retry or ping-pong microcell -> macrocell -> microcell or ping-pongs already managed
by the previous feature Minimum time between Handover).
It is enabled by the BSC object parameter timeBetweenHOConfiguration and by the BTS
object parameter bts Time Between HO configuration (0 means “not used” and value greater
than 0 means “used”).
For each neighboring cell of a cell (adjacentCellHandover object), two new (from V12)
parameters are defined: hoPingpongCombination defines up to four combinations (incoming
cause, outgoing cause) used in order to define forbidden handovers during
hoPingpongTimeRejection seconds for all combinations.
When the BSC receives from the BTS a Handover Indication, it calculates the time spent in
the cell since the last handover (named connection_time) and removes from the preferred
cells list the eligible cells for which the connection_time is lower than the corresponding
timeRejection and for which the combination (incoming cause, outgoing cause) corresponds to
a combination defined in HOPingpongCombination.
The incoming causes may be: RXLEV (indifferently for uplink and downlink), RXQUAL
(indifferently for uplink and downlink), DISTANCE, PBGT, CAPTURE, DIRECTED_RETRY,
O&M (for forced handovers), TRAFFIC, AMRQUALITY, ALL (if the incoming cause matches
all the preceding causes), ALLCAPTURE, ALLPBGT.
The outgoing causes may be:
• RXLEV (indifferently for uplink and downlink)

• RXQUAL (indifferently for uplink and downlink)
• DISTANCE
• PBGT
• CAPTURE
• O&M (for forced handovers)
• TRAFFIC
• AMR QUALITY
• ALL (if the incoming cause matches all the preceding causes)
• ALLCAPTURE (if the outgoing cause matches the CAPTURE cause for all the
microcells belonging to the current macrocell)
• ALLPBGT (if the outgoing cause matches the PBGT cause for all the neighboring
cells of the current cell ; this cause can be used to restore the “Minimum time
between handovers” feature used from V9 to V11).
This feature works even if the BSC V12 is in front of BTS V11 or V10.
AMR QUALITY cause has been introduced in V14.3 fro AMR purpose. See also chapter
General protection against HO Ping Pong in the feature interworking part of AMR chapter.
Nortel confidential

LCAUTION!
The parameters hoPingpongCombination and hoPingpongTimeRejection must be defined at
the “entering cell” (relatively to the first HO of the combination) level, for the neighbouring cell
(adjacentCellHandover object) corresponding to the “left cell” (still relatively to the first HO of
the combination). Thus, these parameters are known by the “new BSC” whatever the type of
HO is (intra or interBSC).
For interBSS handovers, if the Cause element is not included in the HANDOVER_REQUEST
message sent from the MSC to the target BSC, then this feature is not applied except when
the incoming_cause in hoPingpongCombination parameter is set to ALL.
During upgrades to V12, if bts Time Between HO configuration is greater than 0, then bts Time
Between HO configuration is set to 1, hoPingpongTimeRejection is set to the previous value of
bts Time Between HO configuration and hoPingpongCombination is set to (all, allPBGT) and if
bts Time Between HO configuration is equal to 0, then it keeps the same value,
hoPingpongTimeRejection is set to 0 and hoPingpongCombination is set to empty.
The C1166 counter related to the “Minimum time between handover” feature is removed and
replaced by the C1782 counter incremented when a cell is removed of the preferred cells list
(so, for one handover indication message, it can be incremented several times).
This feature gives no protection against intracell or interzone ping-pong handovers and gives
no protection against ping-pong handovers between more than 2 cells except for allCapture or
allPBGT outgoing causes.
Nortel confidential

4.8.22 AUTOMATIC HANDOVER ADAPTATION

This feature adapts handover parameters to radio environment of each call, taking into
account mobile speed and frequency hopping (this BSS feature is available from V14.3). The
objective is to minimize call drops and bad quality transients.
That feature is available from V15.1 for BSC3000 and BSC12000.
PRINCIPLE
In order to eliminate the fading in the measurement processing, some averaging mechanisms
are implemented. But the frequency hopping and the mobile speed introduce frequency and
space diversity and average the attenuation of the received signal:
As shown on the diagram above, the faster the mobile moves the less the fading is impacting
(space diversity).
Mobiles can also be sensitive to the frequency diversity as shown on the diagram below. The
more hopping frequencies are used the less fading is impacting.
Nortel confidential

The principle of this feature is to use these averages introduced by the frequency hopping and
the MS speed, in order to decrease the number of measurements take into account or the
handover margin.
DECISIONS FACTORS
FREQUENCY HOPPING
In order to have a sufficient averaging of the Rayleigh fading, the number of frequencies in the
hopping law has to be greater or equal than 4. If the number of frequencies in the hopping law
is less than 4, mobiles are considered as non-hopping, and all processing defined for non
hopping mobiles are applied.
This criterion and all associated mechanisms are applied to the following channels:
• TCH full rate whatever the channel coding (data circuit, EFR, FR, AMR…),
• TCH half rate,
• SDCCH.
MS SPEED EVALUATOR
From internal studies and simulation, a mobile can be considered as a fast mobile, if the
standard deviation in dB of the Rxlev during one period of measurement (i.e. 104 bursts, thus
480ms) is less than 1.4dB.
This standard deviation represents approximately:
• 20 km/h in GSM900,
• 10km/h in GSM1800 and GSM1900,
and is sufficient to have a good averaging of the Rayleigh fading.
Nortel confidential

HALF RATE AND SDCCH CHANNELS
For half rate channels, the number of bursts during one period is sufficient to evaluate with a
correct accuracy the standard deviation criteria, then all treatments associated to this criteria
are relevant for this kind of channels.
UPLINK DTX
In case of uplink DTX activation during the period, the number of bursts received is decreased,
thus the accuracy of the calculated standard deviation is decreased. In this case, the standard
deviation is not evaluated and the last calculated standard deviation is taken.
UPLINK POWER CONTROL
In case of uplink power control, the BTS is not able to distinguish between a variation due to
Rayleigh fading and one due to a power control attenuation. Thus if the power control required
a variation of more than 8 dB during the period, then the standard deviation is not evaluated
and the last calculated standard deviation is taken.
AUTO ADAPTATION MECHANISMS
This feature is activated if the selfAdaptActivation parameter is set to “enabled”.
PBGT HANDOVER ADAPTATION
For this mechanism, two new parameters are added: servingfactorOffset, neighDisfavorOffset
and the previous factor hoMarginBeg from V11 is reused.
Following tables show for each case, the AdaptedHoMargin value and the averaging windows
taken into account in the PBGT handover mechanism according to
• the MS type: fast or slow mobile or managed by a hopping TCH,

• the number of measurement of the serving cell compared with the normal
averaging window,
• the number of measurement of the neighbouring cell compared with the normal
averaging window.
See chapter EXP2 to understand how AdaptedHoMargin is used.
For each cases of measurement, the tables below give the HO Margin result.
Example:
IF
number of available measurements for the cell < normal window
AND IF
number of available measurements for the neighbour cell < normal window
THEN
AdaptedHoMargin = hoMargin+ neighDisfavorOffset
Nortel confidential

Mobile Type: SFH MS
cell measurement neighbour cell measurement AdaptedHoMargin

< rxLevHreqaveBeg < rxLevNCellHreqaveBeg hoMargin + neighDisfavorOffset
< rxLevHreqaveBeg ≥ rxNCellHreqave hoMargin
≥ rxLevHreqave < rxLevNCellHreqaveBeg hoMargin + neighDisfavorOffset - servingfactorOffset
≥ rxLevHreqave ≥ rxNCellHreqave hoMargin - servingfactorOffset
Mobile Type: Slow non SFH MS
cell measurement neighbour cell measurement AdaptedHoMargin
< rxLevHreqaveBeg < rxLevNCellHreqaveBeg hoMargin + hoMarginBeg
< rxLevHreqaveBeg ≥ rxNCellHreqave hoMargin + hoMarginBeg
≥rxLevHreqave < rxLevNCellHreqaveBeg hoMargin + neighDisfavorOffset
≥ rxLevHreqave ≥ rxNCellHreqave hoMargin
Mobile Type: Fast non SFH MS
cell measurement average neighbour cell average AdaptedHoMargin

rxLevHreqaveBeg rxLevNCellHreqaveBeg hoMargin
POWER CONTROL ADAPTATION
For this mechanism, a new parameter is added: rxQualAveBeg.
The following table shows for each case, the averaging taken into account in the power control
mechanism.
Mobile type RxLev average RxQual average

SFH MS rxLevHreqaveBeg rxQualAveBeg
“Fast” non SFH MS rxLevHreqaveBeg rxQualAveBeg
“Slow” non SFH MS no modification
In case of short averaging, due to the measurement quality, no specific value of K (refer to
chapter One shot power control (Pc_2) for more details on this value) is taken into account.
For slow mobile, Fast power control at TCH assignment (Pc_3) is still available in order to
reduce the power control activation time, but the first decision of power control is now taken
with Max[rxLevHreqAveBeg, rxQualAveBeg] measurements, instead of rxLevHreqAveBeg.
4.8.23 PROTECTION AGAINST INTRACELL HO PING-PONG

This feature controls the overall handover process, to avoid oscillations or so called "ping-
pong" handovers, to deal with the complexity introduced by all various situations with
BSC3000 (this BSS feature is available from V14.3).
Nortel confidential

There are various reasons where intracell handovers needs to be triggered, for instance:
• RxQual degradation with high RxLev,

• transition from inner zone to outer zone in a multi-zone cell
but also
• transition from AMR-FR to AMR-HR,

• transition from outer zone to inner zone in a multi-zone cell.
The first two cases are required to maintain call quality, whereas the last two cases are
decided to optimise system capacity.
PRINCIPLE
For this feature, two kinds of intracell handover are distinguished:
• capacity intracell handover: this expression groups all intracell handovers, which
are triggered in order to increase the network capacity:
interzone handover from the outer to the inner zone,
AMR handover from FR to HR TCH,
tiering from BCCH to TCH frequency pattern.
• quality intracell handover: this expression groups all intracell handovers, which are
triggered if the quality of the call is not sufficient:
normal intracell handover,
inter-zone handover from the inner to the outer zone,
AMR handover from HR to FR TCH,
tiering from TCH to BCCH frequency pattern.
The principle of this feature is to introduce two timers, associated to the intracell handover
type, which delay an intracell handover after an intracell handover:
• capacityTimeRejection: defines the rejection time of a capacity intracell handover

after an intracell handover,
• minTimeQualityIntraCellHO: defines the rejection time of a quality intracell
handover after an intracell handover.
Quality intracell Capacity intracell

HO request HO request
First intracell HO
minTimeQualityIntraCell HO
capacityTimeRejection
Nortel confidential

In order to avoid some load, this filtering is done at the BTS level, thus at the L1M activation
for the dedicated channel the BSC has to precise the cause:
• initial assignment,
• capacity intracell handover
• quality intracell handover
• intercell handover.
Due to the following handover non AMR priority:
• RXQUAL
• RXLEV
• DISTANCE
• PBGT
• TRAFFIC
• INTRACELL
• AMR INTRACELL
• INTERZONE
the BTS has to check if one cause of a lower priority is fullfilled.
At the TS release, the BTS sends in the Stop Measurement Ack, to the BSC the number of
each kinds of filtered intracell handovers. The BSC uses this information in order to generate 2
counters.
The feature is deactivated at the OMC-R, if the capacityTimeRejection and

minTimeQualityIntraCellHO parameters are set to 0.
LCAUTION!
Due to AMR L1m introduction, a new cause value is added in hoPingpongCombination:
• AMRquality.
This value is used in case of AMR handover triggered for alarm purpose. This type of
handover can be chosen via the parameter amrReserved2
In case of interBSC handover, in order to distinguish between RxQual handover and AMR
quality handover (according to amrReserved2 chosen), the BSC uses following rules:
IF the handover cause = RxQual

AND IF the speech version <> AMR
THENHandover cause = RxQual.
IF the handover cause = RxQual

AND IF the speech version = AMR
THEN Handover cause = AMR quality.
Nortel confidential

4.8.24 GSM TO UMTS HANDOVER
PRINCIPLE
Thanks to this feature, GSM to UMTS handover is possible for dual-mode mobiles in areas of
2G-3G coverage.
This feature requires the setting of O&M parameters in the following domains :
• Normal or Enhanced Measurement Reporting activation and configuration

• UTRAN classmark activation and configuration
• Declaration of neighbouring cells belonging to the UTRAN
• Handover timers, thresholds and margins
PREREQUISITES
Note that EMR is not a preequisite for 2G-3G handover. The system can perform handover on
mobiles that perform normal reporting.
EARLY CLASSMARK SENDING ACTIVATION
Early classmark sending consists in the mobile sending as early as possible after access a
CLASSMARK CHANGE message to provide the network with additional classmark
information.
Early classmark sending activation is mandatory as EMR capability and FDD radio capability
is provided by the mobile to the BSS in the Classmark 3 IE sent in the CLASSMARK CHANGE
message.
Rule :
earlyClassmarkSending (v10 parameter) = allowed.
3G CLASSMARK SENDING ACTIVATION
Although it is not used by the BSS, the UTRAN classmark information is mandatory to perform
a GSM to UMTS handover as the "INTER RAT HANDOVER INFO" IE shall be included by the
BSC in HANDOVER REQUIRED message.
The activation flag earlyClassmarkSendingUTRAN is used by the BSC and the MS:
• when the “3G Early Classmark Sending Restriction” field in SYSTEM INFORMATION
TYPE 3 message is set 1 (enabled), the MS is asked to the send its UTRAN
capabilites at the call set-up in the UTRAN CLASSMARK CHANGE message
subsequent to the CLASSMARK CHANGE one.
Nortel confidential

• on an incoming handover, if the UTRAN capabilities have not been received by the
the target BSC in the HANDOVER REQUEST message, this BSC sends a
CLASSMARK ENQUIRY message in order to ask the MS to send the UTRAN
CLASSMARK CHANGE message.
Rule :
earlyClassmarkSendingUTRAN = ”enabled”.
USE OF MEASUREMENT INFORMATION MESSAGE
The MEASUREMENT INFORMATION message is used for 3 different purposes:

• declaration of UTRAN neighbouring cells and configuration of UTRAN reporting
requirements
• activation/deactivation of EMR feature
The feature GSM to UMTS handover can be used with either normal measurement reporting
or enhanced measurement reporting. The part of the MEASUREMENT INFORMATION
message related to EMR feature activation is fully described in §4.6.6.
When the mobile does not have the UMTS FDD RAT capability, it shall not receive information
about UTRAN cells. As a consequence, the BSC sends two different version of Measurement
information to the BTS: a 2G version with GSM cell information only and a 2G/3G version with
both GSM and UTRAN cell information. The BTS then broadcasts the appropriate message
according to each mobile’s capability and according to the status of the “GSM to UMTS
handover” activation, as specified in the table below.
GSM to UMTS HO disabled GSM to UMTS HO enabled

EMR disabled EMR enabled EMR disabled EMR enabled
Release 4 2G only No MI message MI 2G message None MI 2G message
mobiles
2G-3G mobiles No MI message MI 2G message MI 2G-3G message MI 2G-3G message
The 2G measurement information message (2G MI) contains mainly the following information:
• reportTypeMeasurement : parameter that defines the type of measurement report that

the mobiles are required to use
• common (EMR and non-EMR) reporting configuration parameters :
multiBandReporting
• EMR-specific configuration parameters : servingBandReporting,
servingBandReportingOffset
The 2G-3G measurement information message (2G-3G MI) contains mainly the following
information:
Nortel confidential

• reportTypeMeasurement : parameter that defines the type of measurement report that

the mobiles are required to use
• common (EMR and non-EMR) reporting configuration parameters :
multiBandReporting, qsearchC, fDDMultiRatReporting, fDDReportingThreshold2
• EMR-specific reporting configuration parameters : fDDReportingThreshold,
servingBandReporting, servingBandReportingOffset
• UTRAN cells definition : mobileCountryCodeUTRAN, mobileNetworkCodeUTRAN,
locationAreaCodeUTRAN, rNCId, cId, fDDARFCN, scramblingCode, diversityUTRAN
NEIGHBOUR CELL LISTS
DEFINITION
The Neighbouring Cell List is built by a concatenation of two lists:
• The GSM Neighbour Cell List : it is the list of GSM cells, ordered by ARFCN and
BSIC, as defined in the BSIC_Description parameter of the
MEASUREMENT_INFORMATION message, which takes the first position in the list
• The 3G Neighbour Cell list: it is the list of UMTS cells, ordered by ARFCN &
scrambling code (the ARFCN are ordered the same way as received from the
network. For each ARFCN, scrambling codes are ordered in increasing number).
MAXIMUM SIZE
In this version the list is limited to 32 GSM cells and 32 UMTS cells.
When at least one UTRAN neighbouring cells is declared, only 31 different BCCH frequencies
for GSM neighbouring cells can be declared.
NEW BSS PARAMETERS
CREATION OF A NEW OBJECT
A new object is created alongside adjacentCellHandover: adjacentcellUTRAN.
2G-3G HANDOVER ACTIVATION : GSMTOUMTSSERVICE HO

PARAMETER
The following parameter (gsmToUMTSServiceHO) belonging to bsc object serves to

deactivate the 2G-3G Handover feature in all cells of the BSC or to provide a default GSM to
UMTS handover strategy when the MSC has failed to set one for the call :
Nortel confidential

gsmToUMTSServiceHO value range :

• Shall not
• Should not
• Should
• GsmToUMTSDisabled
The MSC may include a similar “service handover” field in BSSMAP “ASSIGNMENT
REQUEST” and BSSMAP “HANDOVER REQUEST” messages sent to the BSS:
• Shall not: the BTS shall never hand off the communication to UTRAN (No UMTS
neighbouring cell can be present in the candidate cells list)
• Should not: the BTS shall not hand off the communication to UTRAN for a PBGT
reason but other criteria are nevertheless authorized to avoid call drop (handover for
alarm reason) or to reduce the load of the current cell when in congestion state
(handover for traffic reason)
• Should: It can be understood either as “immediate” or as “when possible or if
necessary”. The hoMarginUtran(n) parameter setting allows dual-mode MS to go
more or less easily on UTRAN layer. With a very negative values, the PBGT emulates
a capture in order to recover the UTRAN service as soon as possible.
For each call, we must differentiate the following cases :
• Case n°1 : gsmToUMTSServiceHO is set to GsmToUMTSDisabled.
Handover to UMTS is disabled.

• Case n°2 : "service handover" is provided by the MSC, and gsmToUMTSServiceHO
value is different from GsmToUMTSDisabled.
The MSC "service handover" value is sent to the BTS and the handover strategy is
decided by the MSC (according to OMC hoMarginXX setting).
• Case n°3 : "service handover" field is not provided by the MSC and
gsmToUMTSServiceHO is different from GsmToUMTSDisabled
Then, the default OMC "service handover" (i.e. the gsmToUMTSServiceHO
parameter) value is sent to the BTS and the handover strategy is decided by the
Access network instead of the Core network.
Note: In case the gsmToUMTSServiceHO is modified, the change only applies to new calls (or
after a handover) except for a feature deactivation.
Nortel confidential

CONFIGURATION PARAMETERS OF CLASSMARK SENDING
The following parameter should be set to “enabled” to allow the mobile to send its UTRAN
Classmark at call setup :
• earlyClassmarkSendingUTRAN
The UTRAN_CLASSMARK_CHANGE message takes about 2 or 3 radio frames to transmit.

However, when supported by the UTRAN network, it is possible to reduce the size of the
message thanks to the compression of UE radio access capabilities and predefined
configuration Information Elements :
compressedModeUTRAN = enabled
Note: During IOT activities, it is recommended to disable this compression.
UMTS NEIGHBOUR CELLS DECLARATION PARAMETERS
The following 8 new parameters belonging to adjacentcellUTRAN object define the UMTS
neighbours :
• mobileCountryCodeUTRAN
• mobileNetworkCodeUTRAN
• locationAreaCodeUTRAN
• rNCId
• cId
• fDDARFCN
• scramblingCode
• diversityUTRAN
Up to 32 UMTS neighbours and 31 GSM neighbours may be declared.
MEASUREMENT REPORTING PARAMETERS
EMR must be activated for 2G-3G handover. The following 7 new parameters serve to
configure the Enhanced Measurement Reporting for 2G-3G handover purposes:
• reportTypeMeasurement
• qsearchC
• fDDMultiRatReporting
• fDDReportingThreshold
• fDDReportingThreshold2
Nortel confidential

• servingBandReporting
• servingBandReportingOffset
2G-3G HANDOVER TIMER
t3121 has the same use as t3103 in the GSM inter-BSC handover procedure. It sets the value
before countdown of T3121 timer deined in the GSM specification:
• T3121 starts when the BSC sends an INTER SYSTEM TO UTRAN HANDOVER
message to the mobile.
• T3121 stops when the mobile has correctly seized the UTRAN channel. The purpose
of this timer is for the BSC to keep the old channels long enough for the mobile to be
able to return to the old channels.
• On expiry of T3121 (indicating the mobile is lost), the BSC may release the channels.
2G-3G HANDOVER THRESHOLDS
The following new parameters serve to configure thresholds :

• rxLevMinCellUTRAN
• rxLevDLPbgtUTRAN
These parameters have the same meaning as their counterparts on adjacentCellHandOver
object, but apply to a UTRAN neighbouring cell instead of a GSM neighbour cell.
2G-3G HANDOVER MARGINS
The following new parameters serve to configure margins for various types of handovers to 3G
cells :
• hoMarginUTRAN
• hoMarginAMRUTRAN
• hoMarginRxLevUTRAN
• hoMarginRxQualUTRAN
• hoMarginDistUTRAN
• hoMarginTrafficOffsetUTRAN
• offsetpriorityUTRAN
All these parameters have the same meaning as their counterpart on adjacentCellHandOver
object, but apply to a UTRAN neighbouring cell instead of a GSM neighbour cell.
In practice, all handovers algorithms except Capture and Directed retry are allowed towards
an UMTS neighbouring cell.
Note : the Power Budget handover as defined in GSM may be used to emulate a capture by
UTRAN layer.
Nortel confidential

CONFIGURATION PARAMETERS OF PING-PONG MECHANISM FOR 2G-

3G HANDOVERS
The existing mechanism to protect against ping-pong handover is used also for 2G-3G
handovers.
The list of outgoing causes for handovers towards UMTS neighbour cells is : traffic, pbgt,
rxLev, rxQual, dist, O&M (forced ho), all. This list is defined by setting the new parameter
hoPingpongCombinationUTRAN.
A specific timer is defined for time Rejection : hoPingpongTimeRejectionUTRAN.
If a pair of causes in the hoPingpongCombinationUTRAN parameter list refers to an incoming
or an outgoing cause that is not implemented in the source or in the target system, the existing
causes will be ignored.
On an incoming UMTS to GSM handover, if the BSC has not received the source "UTRAN
Cell identifier" (HANDOVER REQUIRED message / Old BSS to new BSS information"
container / “Cell load information group” IE), no rejection timer will be started for that UTRAN
cell.
UMTS CELL LOAD MANAGEMENT
UMTS cell load management is managed three different ways:

• Through existing anti ping-pong mechanism for incoming 3G to 2G handovers
• Through a new mechanism for outgoing handover failures : When a UMTS cell rejects
the handover, the 2G-MSC sends a BSSMAP HANDOVER REQUIRED REJECT
message including cause “Traffic Load in the target cell higher than in the source cell”
or “no radio resource available”. The BSC stores this information and does not attempt
a new handover towards this cell for a given time equal to
hoRejectionTimeOverloadUTRAN parameter.
• Through a new mechanism for incoming handover from UTRAN :
o if the handover cause in the BSSMAP HANDOVER REQUEST message is

either “traffic”, “directed retry” or “reduce load in serving cell” ,
o and if the source RNC and the MSC have implemented the “old BSS to new
BSS information” container
o and if the source RNC has included the “Cell load information group” within
this container
o then the BSC stores the information and will not try a handover towards this
UTRAN cell for a given time equal to hoRejectionTimeOverloadUTRAN
parameter,
o otherwise, the BSC does not start any rejection timer for that UTRAN cell.
SUMMARY OF HO 2G-3G PARAMETERS (V17)
Nortel confidential

Parameter name Definition object

adjacentCell
cId Cell identity of the UMTS neighbouring cell for handover
UTRAN
flag to indicate whether compressed mode UTRAN is supported or
not. This flag is used by the network to indicate to mobiles whether to
compressedModeUTRAN bts
use a compressed version of the INTER RAT HANDOVER INFO
message (UE to UTRAN message).
flag indicating whether there is deiversity in the neighbouring UTRAN adjacentCell
diversityUTRAN
cell UTRAN
flag indicating whether UTRAN classmark change message shall be
earlyClassmarkSendingUTRAN bts
sent with Early Classmark Sending
adjacentCell
fDDARFCN fDD channel number of the UTRAN neighbouring cell
UTRAN
Number of FDD UTRAN cells to be reported in the list of strongest
fDDMultiratReporting bts
cells in the MR or EMR message
(used in EMR only) defines the CPICH RSCP level above which the
Handover
fDDReportingThreshold MS will apply a higher priority to UTRAN cells in the enhanced
control
(used in MR and EMR) defines the CPICH Ec/N0 level above which
Handover
fDDReportingThreshold2 the MS will report UTRAN cells in the normal or enhanced
control
This parameter serves to disable 2G-3G handover at BSC level or to
gSMToUMTSServiceHO indicate the preference (2G versus 3G cells) to be applied for bsc
handovers
adjacentCell
hoMarginUTRAN Handover margin for PBGT handover to a UMTS cell
UTRAN
Handover margin for intercell quality handovers to UMTS, for AMR adjacentCell
hoMarginAMRUTRAN
calls UTRAN
adjacentCell
hoMarginDistUTRAN handover margin for handover to UMTS on distance criterion
UTRAN
adjacentCell
hoMarginRxLevUTRAN handover margin for signal strength handover to UMTS
UTRAN
adjacentCell
hoMarginRxQualUTRAN handover margin for signal quality handover to UMTS
UTRAN
offset to be subtracted to the homarginUTRAN to allow handover for adjacentCell
hoMarginTrafficOffsetUTRAN
traffic reason when the current cell is congested UTRAN
list of pair of causes indicating the causes of ping-pong handovers in adjacentCell
hoPingpongCombinationUTRAN
the overlapping areas. UTRAN
time that must elapse before attempting another handover towards adjacentCell
hoPingpongTimeRejectionUTRAN
an UTRAN cell. UTRAN
time that must elapse before attempting another handover towards a adjacentCell
hoRejectionTimeOverloadUTRAN
congested UTRAN cell UTRAN
adjacentCell
locationAreaCodeUTRAN Location area code of the UMTS neighbouring cell
UTRAN
adjacentCell
mobileCountryCodeUTRAN Mobile country code of the UMTS neighbouring cell
UTRAN
adjacentCell
mobileNetworkCodeUTRAN Mobile network code of the UMTS neighbouring cell
UTRAN
priority offset applied by the BSC when selecting the candidate cell adjacentCell
offsetPriorityUTRAN
for the handover process UTRAN
search for UTRAN cells if signal level on the BCCH of serving cell :
is below threshold (0-7):
-98, -94, … , -74 dBm, ∞ (always)
or is above threshold (8-15):
Handover
qsearchC -78, -74, … , -54 dBm, ∞ (never) control
If the serving BCCH frequency is not part of the BA(SACCH) list, and
if the dedicated channel is not on the BCCH carrier, and if qsearchC
is not equal to 15, the MS shall ignore the qsearchC parameter value
and always search for UTRAN cells. If qsearchC is equal to 15, the
MS shall never search for UTRAN cells.
Nortel confidential

Parameter name Definition object

type of measurement report to be reported on this cell : enhanced
reportTypeMeasurement bts
measurement report or legacy measurement report
adjacentCell
rNCId identity of the UTRAN neighbouring cell’s RNC
UTRAN
downlink signal strength threshold above which handovers to UTRAN adjacentCell
rxLevDLPbgtUTRAN
for cause power budget are inhibited UTRAN
minimum signal strength level that the MS must measure on an
adjacentCell
rxLevMinCellUTRAN UMTS neighbour cell to be able to be granted a handover to this
UTRAN
UMTS neighbour cell
adjacentCell
scramblingCode Scrambling code of the UMTS neighbouring cell
UTRAN
defines the number of cells from the GSM serving frequency band
servingBandReporting that shall be included in the list of strongest cells in the measurement bts
report.
If there is not enough space in the report for all valid cells, the cells
shall be reported that have the highest sum of the reported value
(RXLEV) and the parameter servingBandReportingOffset Handover
servingBandReportingOffset
(XXX_REPORTING_OFFSET) for the serving GSM band. Note that control
this parameter shall not affect the value itself of the reported
measurement.
t3121 has the same use as t3103 in the GSM inter-BSC handover
procedure. It sets the value before countdown of T3121 timer defined
in the GSM specification .
T3121 starts when the BSC sends an INTER SYSTEM TO UTRAN
t3121 HANDOVER message to the mobile. T3121 stops when the mobile bts
has correctly seized the UTRAN channel. The purpose of this timer is
for the BSC to keep the old channels long enough for the mobile to
be able to return to the old channels if necessary. On expiry of T3121
(indicating the mobile is lost), the BSC may release the channels.
2G-3G HANDOVER ALGORITHMS
REPORTING QUANTITY
In the Enhanced Measurement Report message, the downlink received power level of UMTS
neighbouring cells may be reported by the mobiles using one of two possible reporting
quantities :
• either CPICH RSCP
• or CPICH Ec/N0
In our v17.0 implementation, the reporting quantity that mobiles are expected to report to the
network is always CPICH RSCP. The mobiles are informed of this obligation by the
FDD_REP_QUANT flag that is sent by the network on SACCH in Measurement Information
messages.
MAPPING BETWEEN RSCP (3G) AND RXLEV (2G)
This CPICH RSCP value is directly comparable to a “classical” RxLev value.

According to the mapping specified in the GSM specification, we can define the following
conversion table between RSCP values and the reported values in range [0..63]. Values below
0 are reported as 0 and values above 63 are reported as 63 by the mobiles. The L1M then
subtracts 5 to the reported value to obtain the equivalent Rxlev signal strength.
Nortel confidential

RSCP (unit : dBm) Reported value inside EMR L1M converted value (no RxLev “equivalent” in dBm
(no unit) unit)
RSCP<-120 0 0 <-110
-120<RSCP<-119 0 0 <-110
-119<RSCP<-118 0 0 <-110
-118<RSCP<-117 0 0 <-110
-117<RSCP<-116 0 0 <-110
-116<RSCP<-115 0 0 <-110
-115<RSCP<-114 1 0 <-110
-114<RSCP<-113 2 0 <-110
-113<RSCP<-112 3 0 <-110
-112<RSCP<-111 4 0 <-110
-111<RSCP<-110 5 0 <-110
-110<RSCP<-109 6 1 -110<RxLev<-109
… … … …
-54<RSCP<-53 62 57 -54<RxLev<-53
-53<RSCP<-52 63 58 -53<RxLev<-52
-52<RSCP<-51 63 58 -53<RxLev<-52
… … … …
-26<RSCP<-25 63 58 -53<RxLev<-52
-25<RSCP 63 58 -53<RxLev<-52
ALGORITHMS
Once the power level of all 2G and 3G neighbouring cells can be compared with one another,
all L1M handover algorithms are directly reusable.
For example, the algorithm for a Power Budget handover to UTRAN can be described as
follows :
• The MS listens to UTRAN cells if RxLev < qsearchC
• The MS reports the measured RSCP of the UTRAN cells for which CPICH Ec/N0 ≥
fDDReportingThreshold2
• The “service handover” shall be set to “should”
• The BTS discards UTRAN cells for which :
o either CPICH RSCP < rxLevMinCellUTRAN(n)
o or RxLev of the serving cell > rxlevDLPbgtUTRAN(n)
• PBGT handover decision is taken if :

o CPICH RSCP(neighbour 3G cell) > RxLev (serving 2G cell) +
hoMarginUtran(neighbour 3G cell).
• UTRAN cells are sorted according to EXP2() values
Nortel confidential

IMPACT OF HO 2G-3G ON INTERFERENCE MATRIX
UMTS cells are not measured by the Interference Matrix feature.
EMR CASE
The introduction of UTRAN neighbouring cells has an impact on Interference Matrix feature
because of the number of GSM neighbour cells it induces.
If at least one UTRAN neighbour cell is declared, no more than 31 GSM neighbour cells can
be declared, instead of 32. The impacts on IM are the following:
• The algorithm that calculates the number of cycles (used by launching tool on OMC-R
and by BSC for cycle definition) shall be done with only 31 BCCH frequencies
• UTRAN neighbour cell creation must be forbidden if 32 different BCCH frequencies
are already declared for GSM neighbour cells
• GSM neighbour cell creation with a 32nd different BCCH frequency must be forbidden
if at least one UTRAN neighbour cell is declared.
• UTRAN neighbour cell creation, UTRAN neighbour cell deletion, fDDARFCN change,
scramblingCode change, must be forbidden while Interference Matrix feature is
running on the BSC.
• the control that warns the operator if he tries to activate Interference matrix when one
cell has 32 GSM neighbouring cells (this control exists already in this case) must be
extended to the case where one cell has 31 GSM neighbouring cells and at least one
UTRAN neighbouring cell.
NORMAL MR CASE
Although fewer possibilities are available with MR than with EMR, the way GSM and UTRAN
neighbouring cells are reported in Measurement report messages is manageable, thanks to
multiBandReporting and fDDMultiratReporting parameters. Unlike EMR, the number of
reported non-serving band GSM and UTRAN valid neighbouring cells has an impact on the
number of remaining spare places in the Measurement report message that could be used for
fake neighbours in Interference Matrix.
Nortel confidential

4.9. HANDOVER ALGORITHMS ON THE MOBILE SIDE

For an intracell handover, the mobile receives an ASSIGNMENT COMMAND and simply
switches to another timeslot belonging to any TDMA of the cell.
For an intercell handover, upon reception of the HANDOVER COMMAND, the mobile checks
if it has the synchronization information. If not a handover failure is reported and
communication remains on old channel.
Then, if it is a synchronized handover, four access bursts are sent on the new channel before
actually switching to it.
If it is a non synchronized handover, the mobile will send contiguous access bursts on new
cell, expecting a PHYSICAL INFORMATION message to be sent back by the BTS, in order to
know the Timing Advance to be used on the new channel and actually switch to it. If that
message is not received within one second, then there is a handover failure and the mobile
returns to the old channel.
Once on the new cell, the mobile tries to establish level 2 connexion (SABM and UA exchange
procedure). If that procedure fails, then the mobile returns to the old channel, but if it succeeds
the synchronization information with previous best cells is kept for updating with new cell
parameters.
To conclude this paragraph, one realizes that a handover can be a rather lengthy process,
which should not be performed too late in order to ensure its success and not too often to
maintain a smooth voice or data flow.
Nortel confidential

4.10. POWER CONTROL ALGORITHMS

The aim of the Power Control feature is to reduce the average interference level on the
Network and to save mobile batteries.
4.10.1 STEP BY STEP POWER CONTROL
LCAUTION!
From V14 in L1mV2, RxLevXX is always rescaled at the maximum power output (see chapter
Measurement Processing)
This algorithm is a step by step full path loss compensation. The algorithm determines the gap
between the received level at Pmax (theoretical maximum power without taking into account
Power Control) and the power control threshold (lRxLevDLP, lRxLevULP) and compensates
the path loss step by step until the received level reaches the threshold. That algorithm has
been improved in L1mV2 with the introduction of a limitation based on the one shot
computation when there is a need to re-compute the attenuation (high level and good quality)
The basic idea of the step by step power control algorithm is:
• to reduce transmitted power when reception level is high and quality is good
• to compute a new transmitted power with total path loss compensation when
reception level is high and quality is good
At every runPwrControl event, the Weighted Average is computed at Pmax (SAveRxlev) and
the following algorithm is perfomed by Ms/Bs:
IF (SAveRxLev < lRxLevP) OR (SAveRxQual > lRxQualP)

NewAttRequestdB = Max (CurrentAttRequestdB - IncStepSizeXX, 0)
ELSE IF [(SAveRxLev > uRxLevP) AND (SAveRxQual < uRxQualP)]

TempAttRequestdB = SAveRxLev – lRxLevP
IF (TempAttRequestdB < CurrentAttRequest –IncrStepSizeXX)

NewAttRequestdB = CurrentAttRequestdB – IncStepSizeXX
ELSE IF (TempAttRequestdB > CurrentAttRequest + RedStepSizeXX)
NewAttRequestdB = CurrentAttRequestdB + RedStepSizeXX

ELSE NewAttRequestdB = TempAttRequestdB
ELSE ((lRxLevP≤SAveRxLev ≤ uRxLevP) OR (uRxQualP≤ SAveRxQual ≤ lRxQualP))
NewAttRequestdB = LastCommandedAttRequestdB
The resultfor the new attenuation request is stored into NewAttRequestdB
Nortel confidential

The figure below summarizes the command for (UL or DL) transmission power according to
RxLev/RxQual values.
RxQual
Increase Tx Power
lRxQual
No new command for MS
(or BS) transmission power
uRxQual
New Tx Power
computation
lRxLev uRxLev RxLev
LCAUTION!
When the MS or the BTS is in the “NEW TX POWER COMPUTATION” zone, the re-
computation of the attenuation does not lead necessarily to a reduction of the emitted power.
Note: This feature is activated at the BTS level by setting the following parameters:
• powerControl object: uplinkPowerControl = enabled and bsPowerControl =

enabled
• bts object: new power control algorithm = step by step
4.10.2 ONE SHOT POWER CONTROL
LCAUTION!
Measurement Processing).
The enhanced power control is a one shot partial path loss compensation algorithm.
The one shot power control algorithm determines the “optimal” transmit power by computing a
partial path loss compensation and compensates it in one step.
This feature is activated at the BTS level by setting the following parameters:

enabled
• BTS object: new power control algorithm = one shot
Nortel confidential

At every runPwrControl event, the Weighted Average is computed at Pmax (SAveRxlev) and
the following algorithm is perfomed by Ms/Bs:
IF (SAveRxLev < lRxLevP) OR (SAveRxQual > lRxQualP)

NewAttRequestdB = 0
ELSE
NewAttRequestdB = K * (SaveRxLev - lRxLevP)
The values of K depend on the activation of frequency hopping and of the RxQual. Here are
the values of K, which come from simulation results:
RXQUAL 0 1 2 3 4 5 6 7
K with Frequency Hopping 0,9 0,8 0,7
K without Frequency Hopping 0,7 0,6 0,5
The figure below summarizes the command for (UL or DL) transmission power according to
RxLev/RxQual values.
RxQual
Tx Power max
(MS or BS attenuation = 0)
lRxQual
New Tx Power
computation
lRxLev RxLev
Please note that if NewAttRequestdB = 0 then the MS power becomes equal to the maximum
power possible in the cell, i.e. Min(msTXPwrMaxCell(n), MSTxPwrMax). The limitation can
come from the mobile (MSTxPwrMax) or from the cell (msTxPwrMax).
Concerning the BTS, the attenuation (difference between current power and max power) is
considered, so if NewAttRequestdB = 0 then the BTS power becomes equal to the maximum
static power possible.
Nortel confidential

LCAUTION!
From V12, an 8 dB limitation applies on decrease, e.g.the BTS will never decrease its power
by more than 8 dB (some mobiles would lose the BTS)
4.10.3 FAST POWER CONTROL AT TCH ASSIGNMENT
LCAUTION!
Measurement Processing).
This V12 feature is an improvement of the one shot power control (described above). One
shot power control reactivity is improved by deciding power control on SDCCH allocation and
on TCH allocation with only rxLevHreqaveBeg or rxQualAveBeg measurements. With this
feature, attenuation (possibly decided on SDCCH) is kept at TCH assignment and for each
channel switch-over (start on SDCCH, SDCCH to TCH or TCH to TCH), the few first
measurements (from Max[rxLevHreqAveBeg, rxQualAveBeg] to Max[rxLevHreqave *
rxLevHreqt, rxQualHreqave * rxQualHreqt]-1) may be used to decide power control.
This feature is activated by setting the following parameters:

enabled
• BTS object: new power control algorithm = enhanced one shot
The triggering of the one shot power control is accelerated because rxLevHreqaveBeg or
rxQualAveBeg measurements are taken into account.
Until Max[rxLevHreqave * rxLevHreqt, rxQualHreqave * rxQualHreqt] is reached, the

attenuaton is computed with the compensation factor K for uplink and downlink. This factor no
more depends on the rxQualHreqave measurements but only on the frequency activation:
NewAttRequestdB = K * (SaveRxLev - lRxLevP)
• K = 0.5 in case of non hopping channel,

• K = 0.7 in case of hopping channel,
When Max[rxLevHreqAveBeg, rxQualAveBeg] > Max[rxLevHreqave * rxLevHreqt,
rxQualHreqave * rxQualHreqt] this feature is no more activated.
When Max[rxLevHreqave * rxLevHreqt, rxQualHreqave * rxQualHreqt] is reached the usual
average of the one shot power control described before is computed with the K value
depending of the rxQualHreqave measurements.
LCAUTION!
This feature is not supported with DCU2 boards or with a mix of DCU2/DCU4 boards.
Note: In some very specific cases with a poor quality and a good level strength (very interfered
environment) the Fast Power Control algorithm may prevent from powering up after a TCH
assignment until max(rxLevHreqave*rxLevHreqt, rxQualHreqave*rxQualHreqt) is reached.
Nortel confidential

4.10.4 POWER CONTROL ON MOBILE SIDE

In RACH phase, the MS power is equal to Min [msTxPwrMax, msTxPwrMaxCCH].
When the MS switches from RACH to SDCCH or TCH, it keeps the same power.
In dedicated mode, the mobile transmits at the power required in the POWER COMMAND
message transmitted in the layer1 header of SACCH blocks. This command will be received at
the end of a reporting period (102 frames in SDCCH, 104 in TCH). It will be applied at the
beginning of the following period at a rate of 2dB per 13 frames.
Before triggering an intercell handover due to uplink causes (RXQUAL or RXLEV) and only
step by step power control and for L1mV1 (only), the BTS should request the MS to transmit to
its maximum power capability. In such cases, if the MS can increase its transmit power, no
Handover Indication is transmitted by the BTS.
In the case of a handover, the maximum transmitted power allowed in the target cell is sent to
the mobile in the handover command message (msTxPwrMaxCell).
In case of intracell handover, the power reduction is kept.

The current txpwr value is saved so that it can be sent in the next transmitted uplink SACCH.
For the BTS, the duration of the entire process (from order to acknowledgment) is three
multiframes.
BTS sends PC andTA BTS gets the

commands in a One SACCH reporting period Measurement
SACCH block 26 * 4 = 104 frames (480 ms) Report
SA0 SA1 SA2 SA3 SA0 SA1 SA2 SA3 SA0 SA1 SA2 SA3
MS starts applying
New PC and TA
MS starts transmitting
MS gets the SACCH concerning
SACCH block Previous multiframe
4.10.5 AMR POWER CONTROL

With the introduction of the AMR feature a new Layer 1 Management has been desgined to
take into account AMR channels specificity, including new algorithm for Power Control.
Please refer to section Power Control in the chapter AMR - Adaptative Multi Rate FR/HR.
Nortel confidential

4.10.6 POWER ADAPTATION AFTER AN INTERZONE HO

This section is only applicable to RF power control in multizone cells (see
Concentric/DualCoupling/DualBand Cell Handover).
PURPOSE
Before V17.0, after an inter-zone handover, the BSC sets the BTS and MS initial powers on
the new channel of the new zone to values that are identical to those used on the previous
channel in the other zone. As a result, the strength of the uplink and the downlink received
signal may decrease significantly on the establishment on the new channel. The risk is that the
handover could fail or the voice quality could deteriorate until the BTS has adjusted the BTS
and MS output TX power on the first run of the L1M power control process.
In v17.0, if the BSC expects the reception level to decrease following the interzone handover,
the BSC shall adapt the BTS and the MS output power, when activating the new channel, to
ensure a constant reception level for the MS and for the BTS. If on trhen other hand, the BSC
expects the reception level to increase, the BSC shall keep the BTS and MS power levels
unchanged and will simply wait for the L1M to adjust them via the standard power control
process.
ESTIMATION OF THE THEORETICAL POWER GAP
The BSC has to estimate the power gap in uplink and in downlink that would exist after an
inner to outer zone handover and an outer to inner handover :
• Delta_RxLev_DL_oz_to_iz : DL signal strength gap following an outer to inner HO
• Delta_RxLev_UL_oz_to_iz : UL signal strength gap following an outer to inner HO
• Delta_RxLev_DL_iz_to_oz : DL signal strength gap following an inner to outer HO
• Delta_RxLev_UL_iz_to_oz : UL signal strength gap following an inner to outer HO
This estimation depends only on the following O&M parameters :

• concentric_cell (bts object): parameter defining the type of multizone cell : concentric,
dualband or dualcoupling.
• zoneTxPowerMaxreduction (transceiverZone object): attenuation to be applied to
bsTxPwrMax (maximum theoretical level of BTS transmission power in a cell),
defining the maximum TRX/DRX transmission power in the zone.
• bizonePowerOffset (handoverControl object): Estimated downlink power offset
between inner zone and outer zone TRXs of a multizone cell. For a dual-band cell,
this parameter has to be estimated in a worst case (edge of band1 zone). For a
concentric or dualcoupling cell, bizonePowerOffset = zoneTxPowerMaxreduction
The 3 different cases of concentric cell give different resultrs for the power gap :
Nortel confidential

Concentric Dual-coupling Dual-band

Delta_RxLev_DL_ ZoneTxPowerMaxReduction [oz] ZoneTxPowerMaxReduction [oz] ZoneTxPowerMaxReduction [oz]
oz_to_iz - ZoneTxPowerMaxReduction - ZoneTxPowerMaxReduction - ZoneTxPowerMaxReduction
3 4
[iz] [iz] [iz] - bizonePowerOffset( )( )
1 1 3
Delta_RxLev_UL_ 0( ) 0( ) - bizonePowerOffset ( )
oz_to_iz
Delta_RxLev_DL_ -(Delta_RxLev_DL_oz_to_iz) -(Delta_RxLev_DL_oz_to_iz) -(Delta_RxLev_DL_oz_to_iz)
5
iz_to_oz( )
1 1
Delta_RxLev_UL_ 0( ) 0( ) bizonePowerOffset
5
iz_to_oz( )
Notes :
(1) : for concentric and dualcoupling cells, there is no uplink signal strength gap. The uplink
gap only applies to dualband cells.
(2) : the type of coupler (D, H2D etc) does not impact the formula because the BTS takes the
coupling into account to reach the required output power which is equal to bstxpwrmax -
zonetxpowermaxreduction. So it is the same formula as concetric cell.
(3) : The higher the frequency, the steeper the signal strength decrease as a function of MS-
BTS distance. “bizonePowerOffset” is a worst case assessment of this path loss performed at
the inner-zone boundary.
(4) : As both heterogeneous coupling and dual-band could be applied simultaneously to a cell,
zoneTxPwrMaxReduction must be taken into account in te downlink formula
(5) : We hold this truth to be self-evident, that the inner-to-outer zone power gap is the
opposite of the outer-to-inner zone power gap.
CORRECTION OF THE POWER GAP
Upon activating the channel in the destination zone, the BSC considers the relevant
theoretical power gap as well as the last BTS transmission power and MS transmission power
used on the channel of the initial zone. These are reported by the BTS to the BSC in the Abis
connection state ack message.
MS TRANSMISSION POWER ADAPTATION
As explained above, no power adaptation is required on the uplink for a Concentric cell or a
Dual-coupling cell.
In a Dual-band cell :
• if the uplink power gap is less than zero, this power loss shall be corrected with a
command sent to the MS to increase its transmission power
• if the uplink power gap is more than zero, the last MS transmission power level shall
be kept unchanged. However, the new MS transmission power level shall not be
allowed to exceed the maximum power allowed by the network and the maximum MS
output power allowed in that band.
Nortel confidential

BTS TRANSMISSION POWER ADAPTATION
Unlike MS transmission power adaptation, BTS transmission power adaptation applies to all
three types of multizone cells :
• If the downlink power gap is less than zero, this power loss shall be corrected with a
BTS transmission power increase (i.e. BTS attenuation decrease)
• If the downlink power gap is more than zero, the last BTS transmission power level
shall be kept unchanged.
The new BS transmission power level is sent by the BSC to the BTS inside the Abis Channel
activate message (used to initialise the BTS transmission power for the channel) as well as in
the Abis Start measurement Req message (used to initialise the L1M power control algorithm).
REMARKS
If BTS power control is disabled, there is in effect no power adaptation, as the BTS shall emit
at the maximum power allowed in the zone.
A dedicated TCH channel shall be activated at full BTS transmission power if it belongs to the
BCCH TDMA.
Nortel confidential

4.11. TCH ALLOCATION MANAGEMENT
4.11.1 TCH ALLOCATION AND PRIORITY
ALLOCATION AND PRIORITY (RUN BY THE BSC) (ALL_1)
Different priorities are defined in GSM to prioritise TCH resource usage for the different types
of procedures. Basically, GSM procedures can be divided into the following types:
• Assignment Request Messages: coming from MSC. It includes Public calls and
WPS calls. The only difference between the types of Assignment Requests is
basically the priority included in the message.
• InterBSC Handovers
• IntraBSC Intercell Handovers
• Directed Retry Handovers
• IntraCell Handovers: normal Intracell HO, small to Large zone, AMR, cell tiering …
• TCH overflow cases: this includes different procedures in the signaling phase when
trying to get a resource SDCCH. If this one is not available, a resource TCH will be
requested instead.
For certain procedures like the handovers, where reactivity is crucial, it is important to
immediately have TCH resources available. This can be done by reserving some resources for
them. For other procedures like the Assignment Requests where the communication is not
established yet, it might be more interesting to allow the queuing of the requests for some
seconds in order to gain access to the network even if it is a few seconds later. The reactivity
time in this last context is not as important as for the handovers. To be able to control this, a
priority system has been created.
Priorities can be divided into two different groups: external and internal. The BSC is in charge
of converting external priorities into internal ones. Conversion rules will be detailed.
Two kinds of external priorities, NSS external priorities and BSS external, can be defined:
• NSS external priorities are those included in the BSSMAP message coming from
the MSC. As only the Assignment Requests and the Handover Requests (for
interBSC HO) can generate this type of messages, these are the only procedures
having an external NSS priority.
• BSS external priorities are defined via OMC parameter settings. They are set for all
types of procedures, even for the Assignment Requests.
The type of external priority of the Assignment Request procedures taken for conversion to an
internal priority is depending on the value of another OMC parameter (bscQueuingOption) that
indicates if the mode is “MSC driven” or “OMC driven”.
The mode “MSC driven” means that it is the NSS external priority which is taken into account
for internal priority conversion of Assignment Request Procedures. For Handover Request and
TCH overflow, it is BSS external priority that is used for conversion.
The mode “OMC driven” means it is the BSS external priority which is taken into account for
conversion, whatever the procedure.
Nortel confidential

LCAUTION!
Note that if we are in “MSC driven” mode there might be different Assignment Requests
coming from MSC with different priorities, meaning that we could treat them differently
according to the type of call.
However, in “OMC driven” mode there is only one priority, set with a parameter, for all the
types of Assignment Requests. In particular, assignment requests with cause emergency call
are not differentiated from the other assignment requests.
At this point we can start introducing some of the main OMC parameters used for the TCH
allocation management:
ALLOCATION AND PRIORITY PARAMETERS
bscQueuingOption
bscQueuingOption = allowed bscQueuingOption = forced bscQueuingOption = not allowed

MSC driven mode OMC driven mode OMC driven mode
Queuing is allowed Queuing is allowed Queuing is not allowed

NSS external priorities are taken BSS external priorities are BSS external priorities are taken into
into account for Assignment taken into account for all account all procedures.
Request. procedures
BSS external priorities are taken
into account for handover request
and TCH overflow
allocPriorityTable
It is probably the most important parameter for the allocation priority management. It is used to
make the conversion between external and internal priorities and it consists of a vector
containing 18 values. The values can go from 0 to 12 and define the internal priorities
associated to the different procedures. The association between external and internal priority
is done using the index number (or slot number) in this table that goes from 0 to 17. The index
in the table represents the BSS external priority. When NSS external priority is used, in order
to convert into internal priority, we look in the slot NSS external priority - 1.
NSS external priority contained in the BSSMAP message can take a value from 1 to 14. Slots
1 to 5 are reserved for WPS call treatment.
Example: allocPriorityTable = 0 8 9 10 11 12 2 2 2 2 2 2 2 2 3 0 4 2
Slot number 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
allocPriorityTable 0 8 9 10 11 12 2 2 2 2 2 2 2 2 3 0 4 2
With this example in MSC driven mode, for a BSS external priority = 16, the internal priority
defined is 4 and for a NSS external priority = 5, we have to look at the slot number = 5 – 1 = 4,
so the internal priority is 11.
Nortel confidential

"forced" OMC driven

bscQueuingOption
"allowed" MSC driven
BSS ext. Priority = NSS ext. Priority - 1

(only for Ass. Requests)
Slot nb. (BSS Ext. Prio.) 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

WPS
allocPriorityThreshold
Parameter that defines the number of TCH resources reserved for procedures with internal
priority = 0. This internal priority is typically used for Handovers procedures where the
reactivity time is very important. For all the other procedures with an internal priority > 0 a TCH
will be assigned if at least allocPriorityThreshold + 1 TCH resources are free. If that is not the
case the procedure will be rejected or queued depending on the provisioning and type of
procedure (see chapter Queuing).
LCAUTION!
The ressource reservation for priotity 0 procedures is independent from the queuing process,
i.e. even if the parameter bscQueuingOption = not allowed, the TCH reservation is effective.
Note also that this induces two pools of prioritie :
• {0}, for which TCH resources are reserved according to the parameter
allocPriorityThreshold
• [1..12], for which the TCH resources reserved for priority 0 procedures are not
available.
BSS EXTERNAL PRIORITY PARAMETERS
Parameters that are used to associate a BSS external priority to the different types of
procedures. As the NSS external priorities can go from 1 to 14, so slots 0 to 13 in the
AllocPriorityTable, we recommend using values from 14 to 17 for these parameters.
Assign request procedures:
• assignRequestPriority: BSS external priority for Assignment Request messages

used when OMC driven mode is used.
Note: If the MSC driven mode is used and the priority is not included in the incoming
Assignment Request message from the MSC, the assignRequestPriority parameter will be
used instead.
Nortel confidential

Handover procedures :
• directedRetryPrio: BSS external priority for incoming Directed Retry Handovers.

• interCellHOExtPriority: BSS external priority for interBSC interCell Handovers.
• interCellHOIntPriority: BSS external priority for intraBSC interCell Handovers.
• intraCellHOIntPriority: BSS external priority for intraCell Handovers (normal
intracell Handovers, cell tiering Handovers or AMR intracell Handovers).
• small to large zone HO priority: BSS external priority for Small to Large Zone
intracell Handovers in concentric/dualband/dualcouplig cells.
Note: these are external priority taken into account whatever the value of bscQueuingOption.
TCH overflow procedures :
• answerPagingPriority: BSS external priority used for TCH overflow procedures for
an answer to paging.
• callReestablishmentPriority: BSS external priority used for TCH overflow
procedures during the signaling phase of a Call Reestablishment.
• emergencyCallPriority: BSS external priority used for TCH overflow procedures
during the signaling phase of an Emergency Call.
• allOtherCasesPriority: BSS external priority used for TCH overflow procedures
during the signaling phase of a call establishment with cause “other services”.
• otherServicesPriority: BSS external priority used for TCH overflow procedures
during the signaling phase of a call establishment with cause “other services”.
Note: these are external priority taken into account whatever the value of bscQueuingOption.
The table below presents the sum up of recommanded setting for each BSS External priority
and the mapping of each internal priority via the allocPriorityTable parameter:
Parameter BSS Ext Internal Meaning

priority priority
interCellHOExtPriority 15 0 Assigning the internal priority 0 to these procedure will allow to
reserveTCH resources for them (using allocPriorityThreshold
interCellHOIntPriority
parameter)
emergencyCallPriority
callReestablishmentPriority
1 reserved for future use
assignRequestPriority 17 2 Internal priority 2 is assigned to assignment requests in order to
perform some queuing as we will see in next section.
directedRetryPrio
Directed Retry Handovers are considered to have the same
priority than assignment requests, even if queuing is not allowed
for this type procedure
intraCellHOIntPriority 14 3 Internal priority 3 is assigned to IntraCell Handovers in order to
perform some queuing as we will see in next section
small to large zone HO
priority
allOtherCasesPriority 16 4 Internal priority 4 is assigned to the TCH overflow procedures
answerPagingPriority
otherServicesPriority
Nortel confidential

4.11.2 QUEUING
Queuing is used to put TCH allocation request into a waiting queue when no TCH resource is
available. Some types of procedures are interesting to queue up: the TCH requests wait
during a certain time if these ones are not satisfied the first time. In this way the requests is
more likely to succeed if TCH resources become free during the queuing time.
This is typically the case of Assignment Requests or Intracell Handovers. By performing some
queuing on the Assignment Request the end-user impact is a little increase in the call
establishment duration. In the case of Intracell Handovers, as the call is already established,
the effect of the queuing from an end-user point of view is barely perceptible.
Assignment Requests and Intracell Handovers (normal intracell Handovers, small to large
zone, cell tiering, AMR) are the only procedures for which queuing is allowed. TCH overflow
procedures and intercell handovers are never queued.
The activation of the Queuing must be viewed as a solution to prevent an exceptionnal
saturation of TCH. For the waiting queue, a maximum waiting time (allocPriorityTimers) and a
maximum number of TCH allocation requests affected to this queue and the queues of greater
priorities (allocWaitThreshold) are defined via OMC-R parameters.
Note: as intercell handover procedures can not be queued, the allocPriorityThreshold

parameter must be correctly set to reserve TCH resource for incoming handovers (ie priority 0
for these procedures).
LCAUTION!
Please note that when an assignment request is queued, the MS is still attached to a SDCCH
channel and the measurement process keeps on going to allow the MS to perform a handover
on SDCCH. One must so pay attention to:
• enable or not the feature intraBTS handovers on SDCCH (see intraCellSDCCH).

• Correctly dimension the allocWaitThreshold parameter to spare SDCCH resources
QUEUING DRIVEN BY THE MSC (ALL_2)
The MSC driven mode is enabled by the bscQueuingOption parameter set to “allowed”.
In this mode queuing is used according to the priority defined in the message coming from the
MSC for the assignment requests (Slots from 0 to 13) and those defined with BSS external
priorities(Slots from 14 to 17) for the other procedures. As the NSS external priorities can take
values from 1 to 14 and, according to the conversion rule (Slot Nb =NSS Priority - 1), these
priorities match slots from 0 to 13 in the allocPriorityTable. According to this rule, the
Assignment Requests with NSS internal priority set to 1, usualy for emergency calls, will be
mapped to internal priority 0.
In order to make a clear difference between NSS external priorities and BSS external
priorities, the recommend values for BSS external priority parameters are from 14 to 17 (see
chapter Allocation and priority Parameters).
Interest of MSC driven mode is to allow distinction between assignment request and then the
possibility to set different priority for them (WPS calls, VIP users …).
Nortel confidential

LCAUTION!
From V15, if WPS is activated, Slots from 1 to 5 are reserved for WPS priorities, as the
assignment request coming from the MSC for WPS requests can go from 2 to 6 (see chapter
WPS - Wireless Priority Service).
QUEUING DRIVEN BY THE BSC (ALL_3)
The OMC drive mode is enabled by the bscQueuingOption parameter set to “forced”.
In this mode queuing is used according uniquely to the priority defined with the BSS external
priorities (Slots from 14 to 17).
Queuing is managed by the BSC whatever queuing information coming from the MSC are. So
an assignment request priority is set accordingly to assignRequestPriority and the mapping
associated to in the allocPriorityTable.
LCAUTION!
In this mode, WPS can not be efficient because resource allocation request queuing depends
on the type of operation only: thus the priority in the WPS assignement request is not
considered (see chapter WPS - Wireless Priority Service).
In the same way, assignment request with cause emergency calls cannot be differentiated in
this mode, and are treated with priority according to assignRequestPriority.
QUEUING PROCESS
Whatever the queuing mode is, a queue is defined by its size and the maximum waiting time
beyond which it is not allowed to queue the request anymore,. set by these two parameters:
allocWaitThreshold
This parameter is a 13 slot vector. The slot number (0…12) represents the internal priority
queues and the values define the maximum number of TCH allocation requests queued for
each internal priority. The last five slots set to 5 are reserved for WPS call treatment. These
values are accumulative, so the value for one queue represents the maximum number of
requests for that queue and all the queues with lower priorities. Note that the serving
preference for these queues has an increasing order, e.g. if there are two TCH allocation
requests waiting in two different queues, when a TCH resource is released, the request with
the lowest priority is served.
Slot number 0 1 2 3 4 5 6 7 8 9 10 11 12
allocWaitThreshold n 0 n n 0 0 0 0 5 5 5 5 5
n is the integer part of (number of SDCCH sub-channels in the cell)/2.

Note: that while the TCH request is queued it remains in a SDCCH sub-channel. A queue size
longer than the number of sub-channels SDCCH in the cell is so useless. On the other hand a
value closed to the number of SDCCH channels may cause an increase of SDCCH blocking
rate due to the lack of SDCCH resources.
Nortel confidential

allocPriorityTimers
This parameter is a 13 slot vector. The slot number (0…12) represents the internal priority
queues and the values mean the maximum waiting time (in seconds) in the queue of a TCH
allocation request for each internal priority. The last five slots set to 28 are reserved for WPS
call treatment.
Slot number 0 1 2 3 4 5 6 7 8 9 10 11 12
allocPriorityTimers 5 0 5 5 0 0 0 0 28 28 28 28 28
Note: a too long timer is unrealistic as an user will not wait indefinetely.
Sum up of the recommanded value
Slot number 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Internal priority /
0 1 2 3 4 5 6 7 8 9 10 11 12
queue number
allocWaitThreshold n 0 n n 0 0 0 0 5 5 5 5 5
allocPriorityTimers 5 0 5 5 0 0 0 0 28 28 28 28 28
• procedures coming with an external priority 0 or 15 are associated to internal

priority and queue 0, but queuing is not allowed for intercell handovers (system
rule). In this configuration, only Emergency Call can be queued for the external
priority 0.
• internal priority and queue 1 are reserved for future use
• procedures coming with an external priority from [6 to 13] or 17 are associated to
internal priority and queue 2 and queuing is allowed
• procedures coming with an external priority 14 are associated to internal priority
and queue 3 and queuing is allowed
• procedures coming with an external priority 16 are associated to internal priority
and queue 4 but queuing is not allowed
• procedures coming with an external priority from [1 to 5] are associated to internal
priorities and queues [8 to 12] and queuing is allowed (if WPS activated)
• internal priorities and queues [5 to 7] are not used
LCAUTION!
• There is no queuing for TCH in “signaling mode” (TCH overflow).
• It is important to note that even if Directed Retry Handovers are associated to an
internal priority 2 queuing is not allowed for this type of procedure, as for the other
intercell handover procedures.
• Queuing set for procedures with internal priority 0 has been intentionally configured
for Assignment Requests cause “Emergency Call” (which should have in this case
a NSS external priority set to 1 if in MSC driven mode). Indeed, the only other
procedures with priority 0 are intercell handover for which queuing is forbidden.
Nortel confidential

• It is recommended to give different BSS external priorities for the Assignment

Requests and intracell Handovers in order to prioritise the queued allocations for
Assignment Requests. This type of procedure is more sensitive from an end-user
point of view. A user not succeeding in the assignment request will experience an
establishment failure and have to re-establish the call, whereas in the intracell
Handovers, the call is already established and even in case of Intracell Handover
failure that does not necessarily mean a call drop. The intracell Handover may be
re-tried without a real end-user impact.
Below is the flowchart summarizing the TCH allocation handling if queuing is configured as
recommended in MSC driven mode:
Note: if directed retry handover is activated, another way of leaving the queue is a directed
retry handover. Refer to Directed Retry Handover for more details.
Nortel confidential

4.11.3 BARRING OF ACCESS CLASS

On SYS INFO messages, the list of mobile access classes that can not start a call on the cell
is broadcast. Up to V8, this list is represented by the OMC-R parameter
notAllowedAccessClasses. From V9, a feature allows the modification of what is sent on SYS
INFO in case of congestion.
LCAUTION!
As the MS reads SYS INFO messages every 30 seconds in idle mode, there could be a time
window where non-authorized mobiles will still be allowed, e.g. if the MS did not read the
message before the cell selection, it could start a call.
DYNAMIC BARRING OF ACCESS CLASS (ALL_4)
The mechanism consists of temporarily forbidding cell access to some of the mobiles
(according to their access class) when a congestion situation is observed. The congestion
condition is based on:
• The number of free TCH channels.

Note that TCH resources reserved for maximum priority requests (internal
priority = 0) are not considered as free TCH channels.
The parameters are numberOfTCHFreeBeforeCongestion and
numberOfTCHFreeToEndCongestion.
or
• The number of queued requests in the cell.

The parameters are numberOfTCHQueuedBeforeCongestion and
numberOfTCHQueuedToEndCongestion.
The feature is enabled at bsc level by the attribute bscMSAccessClassBarringFunction, and at
bts level by the attribute btsMSAccessClassBarringFunction.
PRINCIPLE
In case of non-congestion, only the list of mobile access classes in notAllowedAccessClasses

is not allowed to select the cell.
In case of congestion, the list of mobile access classes in accessClassCongestion is not
allowed.
NO YES
Congestion ?
notAllowedAccessClasses accessClassCongestion
Forbidden in the cell Forbidden in the cell
Nortel confidential

CONGESTION DETERMINATION
To enter a congestion state, either the number of free TCH must be less than
numberOfTCHFreeBeforeCongestion or the number of queued TCH requests must be greater
than numberOfTCHQueuedBeforeCongestion.
To leave a congestion state, either the number of free TCH is greater than
numberOfTCHFreeToEndCongestion or the number of queued TCH request is less than
numberOfTCHQueuedToEndCongestion.
Example with a one TRX cell where one time slot is reserved for requests with an internal
priority equal to 0:
numberOfTCHFreeBeforeCongeston = 1
SA0
BCCH SA1 SA2 SA3 SA0 SA1 SA2 SA3 T: TDMA enter in congestion
SA0
BCCH SA1 SA2 SA3 SA0 SA1 SA2 SA3 T+1: TDMA is still in congestion
SA0
BCCH SA1 SA2 SA3 SA0 SA1 SA2 SA3 T+2: TDMA gets out of congestion
numberOfTCHFreeToEndCongeston = 3 time
reserved TS
SA1 Used TCH SA0 Free TCH SA3 for priority 0
A congestion situation may be detected each time one of the following events occurs:
• allocation of a TCH resource

• queuing of a TCH resource request
• blocking of a TCH resource (O&M action)
• TDMA removal for defense or O&M reason
• detection thresholds modification
End of congestion situation may be detected each time one of the following events occurs:
• release of a TCH resource

• a queued TCH resource request is served or aborted
• unblocking of a TCH resource (O&M action)
• TDMA attribution
• detection thresholds modification
Note: The overload state duration of a cell can be monitored thanks to the counter C1714, but
that counter is effectively reported to the OMC-R only if the load of the cell is taken into
account (i.e. only if hoTraffic = enabled at cell and BSC levels).
Nortel confidential

V15.0 CHANGES OF DYNAMIC BARRING OF ACCESS CLASS (ALL_4)
The previous “access class barring” mechanism can be improved on 3 main points:
• The list of forbidden access classes is fixed, so the same customers are always
impacted.
• The number of barred access classes is fixed, so the number of barred access
classes may be insufficient.
• The mechanism is triggered on TCH allocation or release basis, but due to the
Erlang law (which induces sudden traffic modification) and because the MS
rereads the SYS INFO (only every 30 seconds), that mechanism could be
improved.
To ensure the functionning of the new mechanism, two levels of barring are created and run at
the same time:
• One level (low level) to provide point 1 and point 3

• One level (high level) to provide point 2
This feature is controlled by bscMSAccessClassBarringFunction on the bsc object and
btsMSAccessClassBarringFunction on the bts object.
HIGH LEVEL MECHANISM DESCRIPTION
To provide point 2, the number of access classes can be modified (additional or less) in order
to adapt to the length of congestion level. Once the cell enters in the congestion state, a
supervision timer is set, and every 3 minutes (system rule), an adaptation is made based on
the new cell congestion state:
• If the cell is still in the congestion state, 2 additional access classes are barred
(assuming they are not all barred)
• If the cell is not in the congestion state, 2 less access classes are barred (until
none are barred)
Once the cell is no longer in the congestion state, and if no access classes are barred, the
supervision timer (3 minutes) is stopped.
Congestion level
Beginning of
congestion Beginning of congestion:
3 minutes timer is set No more classes
End of congestion :
barred: 3 minutes
3 minutes timer
timer is stopped
End of is running
congestion
3 minutes
time
Number of access
classes barred [0 to 2] [2 to 4] [4 to 6] [6 to 4] [4 to 2] [2 to 0]
This mechanism is independent of the low level of barring mechanism.

Nortel confidential

The barred access classes rotate inside the 3 minute time period according to the low level
mechanism of barring described below:
LOW LEVEL MECHANISM DESCRIPTION
Two parameters are important in this mechanism: the periodicity and the
accessClassCongestion parameter.
Periodicity: the congestion condition is still triggered on a TCH allocation or TCH release
basis, but once the congestion condition is triggered, a 60 seconds interval (system rule) is
used to periodically change which access classes are barred.
accessClassCongestion parameter: this parameter is a list of access classes which are

eligible to be barred during the congestion condition. The principle is that, during each 60
seconds interval of congestion, a different subset of access classes (and thus a different set of
mobile sets) may be barred. Access classes 11 to 15 are managed and can be automatically
barred if they are included in the accessClassCongestion parameter. They can not be
automatically barred if they are not in the accessClassCongestion parameter.
LOW AND HIGH LEVEL MECHANISM EXAMPLE
Congestion level
Beginning of
congestion Beginning of congestion:
3 minutes timer is set
End of
congestion
60 seconds
3 minutes
time
Number of access classes [0 to 2] [2] [2] [2 to 4] [4] [4] [4 to 2]

barred
Barred access classes [0,1] [2,3] [4,5] [6,7,8,9] [0,1,2,3] [4,5,6,7] [8,9]
Let us take an example for the accessClassCongestion = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9].

Next time the cell is in congestion, since the last barred access classes are memorised in the
BSC, the new barred access class are the 2 followings in the list of access classes indicated in
the accessClassCongestion parameter.
In case the BSC12000 switchover, TMU reset for BSC3000 or lock/unlock of the cell, the first
barred access class is the first one in the list of access classes indicated in the
accessClassCongestion parameter.
In case the feature is turned off (cell or BSC level), the BSC sends immediately the system
information with notAllowedAccessClasses parameter included whatever is the cell congestion
status.
Nortel confidential

In case the accessClassCongestion parameter is modified while the cell is in congestion, the
list of access classes to be barred will be re-evaluated on the 60s timer expiry, and on the 3
minutes timer expiry, the evaluation will be done on this new list (and not on the list of the
previous 3 minutes timer expiry).
NOTALLOWEDACCESSCLASSES PARAMETER MANAGEMENT
Until BSS V15, the following principle applies:
• In case of non congestion, only the list of mobile access classes in

“notAllowedAccessClasses” is not allowed to select the cell
• In case of congestion, the list of mobile access classes in
“accessClassCongestion” is not allowed.
Usually all users are authorized, and the notAllowedAccessClasses list is empty.
With the redefinition of the access class barring functionality, the management of the
notAllowedAccessClasses parameter is modified in the following way:
• In case of non congestion, only the list of mobile access classes in the
“notAllowedAccessClasses” parameter is not allowed to select the cell: there is no
modification compared to the previous management.
• In case of congestion, the accessClassCongestion parameter is used to process
access classes rotation on all the access classes listed in the
accessClassCongestion except on the access classes listed in the
notAllowedAccessClasses parameter, which remain barred during the congestion.
Let us take the example for the accessClassCongestion = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] and
notAllowedAccessClasses = [3, 4].
This means, as described here above, that access class rotation will be done on the following
access class list = [0, 1, 2, 5, 6, 7, 8, 9] and that access classes 3 and 4 remain barred during
the congestion.
Nortel confidential

4.11.4 RADIO LINK FAILURE PROCESS (RUN BY THE MS)

It is performed by the MS in dedicated mode on SACCH blocks.
RLC counter is initialized to radioLinkTimeout at the beginning of a dedicated mode.
IF good SACCH block

THEN RLC = Min[RLC+2, radioLinkTimeout]
IF bad SACCH block

THEN RLC = RLC - 1
If RLC reaches 0, then call is dropped and re-establishment is tried if reselection is made on a
cell with CallReestablishment set.
4.11.5 RADIO LINK FAILURE PROCESS (RUN BY THE BTS)
The FrameProcessor sets the CT counter to 0 at channel activation

On each correct SACCH:
IF good SACCH block AND IF (CT = 0)

THEN CT = 4*rlf1 + 4
ELSE CT = Min[4*rlf1 + 4,CT+rlf2]
IF bad SACCH block

CT = max(0,CT-rlf3)
If CT reaches 0, a connection Failure Indication is sent to the BSC every T3115, until a
Deactivate Sacch or RF Channel Release message is received.
This process is started when the first SACCH frame is received correctly, and the CT counter
is set according to rlf1 value. If SACCH frame is not received, then the radio link failure
process is not started, CT value is kept to zero and is not modificated.
Interest of the algorithm: the quality of an uplink communication is now considered for the
decision to cut a communication.
Nortel confidential

4.11.6 CALL REESTABLISHMENT PROCEDURE

The call re-establishment procedure allows a mobile station to resume a connection in
progress after a radio link failure, possibly in a new cell and possibly in a new location area.
So this feature avoids losing calls, improving in that way the quality of service. Moreover, in
case of call drop, it reduces the SICD load by avoiding the subscriber to hang off and on.
The Call Re-establishment can be launched following 2 different procedures depending on the
entity which detects the radio link failure:
• a) The radio failure is first seen at the MS side (RadioLinkTimeOut value):

The mobile sends a call-reestablishment on a selected cell (previous one or
new one) and the MSC re-allocate new resources. The old resources are
free by the BSS after the rlf1 timer has expired.
• b) The radio failure is first seen at the BSS side:
The BTS send a radio_link_failure message to the BSC after rlf1 has
expired, the BSC releases the radio resources and in the same time the
MSC activates the t3109 timer and waits a call-reestablishment. Then, when
the MS has detected the radio link failure as well, it performs the selection
and sends a channel request on the selected cell.
To attempt a call re-establishment on a cell, the parameter callReestablisment of the cell will
be set to “allowed” and the cell will not be barred (see chapter Barring of access class).
The mobile station is not allowed under any circumstance, to access a cell to attempt call re-
establishment later than 20 seconds after it detects the radio link failure causing the call re-
establishment attempt.
The mobile station shall perform the following algorithm to determine which cell to use for the
call re-establishment attempt within 5 seconds max:
• 1) The level measurement samples taken on the serving cell BCCH carrier and on
neigbhor cells carriers (carriers indicated in the BA (SACCH) received on the
serving cell) received in the last 5 seconds shall be averaged.
• The carried with the highest average received level is selected.
• 2) On this carrier the MS shall attempt to decode the BCCH data block containing
the parameters affecting cell selection.
• 3) If the parameter C1 is greater than zero call re-establishment shall be attempted
on this cell.
• 4) If the MS is unable to decode the BCCH data block or if the call re-establishment
is not allowed, the carrier with the next highest average received level shall be
taken, and the MS shall repeat steps 2) and 3) above.
• 5) If the cells with the 6 strongest average received level values have been tried
but cannot be used, the call re-establishment attempt shall be abandoned.
Beware, during a re-establishment attempt the mobile station does not return to idle mode,
thus no location updating is performed even if the mobile is not updated in the location area of
the selected cell, however the mobile station will update its location area at the end of the call.
Generally a call re-establishment procedure lasts from 4 seconds to 20 seconds max.
Nortel confidential

4.11.7 CALL CLEARING PROCESS (RUN BY BTS)

This process is used to drop calls with mobiles which are located too far away from a serving
cell and that may disturb other communications on adjacent time slots.
Every runCallClear:
IF (MS_BS_Dist > CallClearing)

THEN call needs clearing.
4.11.8 INTERFERENCE MANAGEMENT (BTS AND BSC)

All interference measurements performed by the BTS on the idle channels are performed in
Watts. Each sample is computed in Watt before being translated in dBm and sent to the L1M.
This method of calculation provides a result which is 2.5 dB higher than the one directly
performed in dB.
Every averagingPeriod, BTS computes Interference levels of idle channels (SDCCH and TCH)
according to the 4 defined thresholdInterference (resulting in 5 Interference ranges) and sends
this information to the BSC. It is therefore possible to monitor interference levels at the OMC.
From V8, the BSC will use RadChanSelIntThreshold parameter in order to sort available
channels according to their interference level. Thus the BSC will allocate channels using the
following priority:
• Hop and low_IF

• NoHop and low_IF
• Hop and (high_IF or just released)
• NoHop and (high_IF or just released).
Note: No interference level management is performed for PDTCH channel, Therefore the level
status of PDTCH resource is always high level (bad level).
4.11.9 UPLINK DTX

DTX is possible both downlink and uplink, but configuration and activation are uncorrelated in
the 2 mechanisms.
The uplink DTX feature is enabled when dtxMode parameter is set to “msShallUseDtx” (the
shall is dependent on the MS decision or capability.
When uplink DTX is activated on the network, MS gets the information from the BTS
(activation parameter). Then it is allowed to perform uplink DTX, i.e. to transmit
discontinuously only a subset of TCH bursts.
If the MS perform DTX on a call, the minimum number of transmitted bursts is 12 (out of 104
for a complete reporting period of 480ms).
The 12 bursts correspond to the 4 SACCH + 8 fixed positioned TCH bursts.
Nortel confidential

Compared to a full TCH frame (120ms to be multiplied by 4 for a complete message):
DTX deactivated
DTX activated
1 SACCH 1 idle
12 bursts TCH 12 bursts TCH
(given fixed positions are only examples; for speech, a SID frame (Silence Descriptor frame:
used to describe comfort noise) made of 8 consecutive TSs shall be sent at the start of every
inactivity period and more are sent regularly, at least twice per second, as long as inactivity
lasts)
• Full frame x 4:
(24 TCH + 1 SACCH + 1 idle) x 4 = 96 TCH + 4 SACCH + 4 Idle
= 104 bursts
• With DTX:
(1 SACCH) x4 + 8 TCH = 12 bursts minimum
Then, depending on the communications (presence of silences), the MS can use DTX or not.
Note: To the minimum number of bursts (12) can be added other transmitted bursts depending
on some criteria (user traffic activity and interleaving depth).
The MS sends to the BTS 2 kinds of measurements, RxQual/RxLev Full, and RxQual/RxLev
Sub.
RxQual/RxLev Full corresponds to an average of measurements performed over 100 out of
104 frames in a SACCH reporting period. These measurements are valid if DTX has not been
used by the MS.
RxQual / RxLev Sub correspond to an average of measurements performed over 12 frames
(instead of 100), these 12 frames being fixed as explained previously. These measurements
are valid if DTX has been used by the MS.
With these measurements, the MS has to send to the BTS a notification that it has performed
DTX or not (uplink DTX status), so that the BTS can choose the average which is valid
(RxQual / RxLev Full or Sub) for L1M purposes. This notification is done via the DTX-used bit
in the Measurement Report.
Nortel confidential

4.11.10 DOWNLINK DTX

In the same way as the mobile, the BTS is able to transmit discontinuously (cellDtxDownLink
parameter, bts object).
The activation of downlink DTX follows depends on :
• authorisation for the BSS to use DL DTX, given by the MSC to the BSC at
assignment request, dynamically on a call-by-call basis
• The value of cellDtxDownLink parameter (bts object)
• The type of radio channel : voice half-rate, voice full-rate, cicuit data
• The values of certain bits in the bscDataConfig file (bits n°1, n°2 and n°3 of label 64)
MSC AUTHORISATION
On a call per call basis, the MSC may forbid the BSS to use Downlink DTX.
The MSC indicates this to the BSC by including a 1-bit long field called “DTX Downlink Flag”
inside BSSMAP Assignment Request (for call setup) or BSSMAP VBS/VGCS Assignment
Request (for group call setup, GSM-R only) or BSSMAP Handover Request (for incoming
external handover of a call coming from another BSS) :
- If “DTX Downlink Flag” is present and if DTX Downlink Flag = 1, then the MSC forbids the
use of DL DTX for that particular call
- If “DTX Downlink Flag” is absent or if DTX Downlink Flag is present and DTX Downlink
Flag = 0, then the MSC does not forbid the use of DL DTX for that particular call
In the second case, the decision to use DL DTX for that call is left entirely up to the BSS and
depends on BSS configuration parameters and the type of channel.
CELLDTXDOWNLINK
If cellDtxDownLink = disabled in the cell, then Downlink DTX is unconditionally turned off in
the cell for all types of call (voice and circuit-switched data).
So, cellDtxDownLink = enabled is a necessary condition to activate downlink DTX in the cell,
but it is not sufficient. It further depends on the type of channel (circuit data, voice half-rate,
voice full-rate).
Nortel confidential

TYPE OF CHANNEL
CIRCUIT-SWITCHED DATA CHANNELS
DTX downlink is unconditionally turned off for circuit-switched data channels, even if
cellDtxDownLink = enabled.
Note : Bit n°1 of label 64 of bscDataConfigfile, called “DTX Downlink in data”, is not used any
longer in the software. Whatever its value, and whatever the value of cellDtxDownLink, DTX
Downlink is disabled for CS data channels.
FULL-RATE VOICE CHANNELS
If bit n°2 of label 64, called “DTX Downlink FR”, is equal to 1 : DTX Downlink is unconditionally
turned off for FR voice channels. This applies to all types of full-rate codecs supported by the
BSS : AMR FR, EFR and FR.
If bit n°2 = 0, and if cellDtxDownLink = “enabled” in the cell, then downlink DTX is used on all
FR Voice channels, provided that its use has not been explicitly forbidden by the MSC at
assignment request stage.
By default, label 64 bit n°2 = 0 so by default DL DTX is activated for FR voice calls.
HALF-RATE VOICE CHANNELS
If bit n°3 of label 64, called “DTX Downlink HR”, is equal to 1 : DTX Downlink is unconditionally
turned off for AMR HR voice channels.
If bit n°3 of label 64 = 0, and if cellDtxDownLink = “enabled” in the cell, then downlink DTX is
used on all AMR HR Voice channels, provided that its use has not been explicitly forbidden by
the MSC at assignment request stage.
By default, label 64 bit n°3 = 0 so by default DL DTX is activated for FR voice calls.
SUMMARY
The table below summarises the activation scenarios of DL DTX :
DTX DL flag cellDtxDown Label 64 bit Label 64 bit Label 64 bit DL DTX for DL DTX for DL DTX for
(from MSC) Link 1 2 3 CS data FR voice HR voice
1 any value any value any value any value disabled disabled disabled
0 or absent disabled any value any value any value disabled disabled disabled
0 or absent enabled 0 0 0 disabled enabled enabled
0 or absent enabled 0 0 1 disabled enabled disabled
0 or absent enabled 0 1 0 disabled disabled enabled
0 or absent enabled 0 1 1 disabled disabled disabled
0 or absent enabled 1 0 0 disabled enabled enabled
0 or absent enabled 1 0 1 disabled enabled disabled
0 or absent enabled 1 1 0 disabled disabled enabled
0 or absent enabled 1 1 1 disabled disabled disabled
Nortel confidential

4.12. EMLPP PREEMPTION
4.12.1 PRINCIPLE OF EMLPP
DEFINITIONS
eMLPP priority : eMLPP priority associated to a call for preemption purposes. The BSC
transparently conveys eMLPP priority between the mobile and the NSS. The BSC does not
process this eMLPP priority.
NSS external priority (also known as BSSMAP priority) : priority associated to a call by the
NSS in the assignment or handover procedure. This priority is sent by the NSS to the BSS and
may then be used by the BSS for queuing or for preemption. Unlike the eMLPP priority, it is
transparent to the mobile.
BSS external priority : queuing priority defined via OMC parameter settings. Each type of
procedure is associated to a BSS external priority for queuing. This priority is used by the BSS
but it is strictly local, therefore the NSS and MS are not aware of it.
internal priority : this priority is local to the BSS. Therefore the NSS and MS are not aware of it.
It is an output of the allocprioritytable.
PRINCIPLE
eMLPP is an extension to GSM networks of the existing MLPP service for fixed lines.
eMLPP covers 2 basic aspects :

• Resource preemption for mobile originated or mobile terminated call establishment
procedures
• Called party preemption for mobile terminated calls
RESOURCE PREEMPTION
eMLPP allows the network to preempt resources from ongoing calls (circuits on the A interface
and/or radio resources in the BSS) to allocate them to an incoming call of greater priority :
o Preemption on the A interface is fully managed (decision and execution), on a per call
basis, by the NSS.
o Preemption on the Radio interface is executed, on a per call basis, by the BSS.
However, the decision to allow the preemption comes from the NSS because the NSS
is in charge of the Call Control procedures.
Nortel confidential

CALLED PARTY PREEMPTION
In the case where the called subscriber has a subscription for eMLPP and for CW (Call
Waiting supplementary service), the mobile station shall be informed of the priority of the
incoming high priority call together with the CW indication. On reception of the set-up message
for the incoming call the compatible mobile station decides on called party pre-emption. If
called party pre-emption applies, the mobile station shall automatically accept the incoming
waiting call and send a hold message to the network. If a hold acknowledge is received, the
waiting call is accepted.
CW is mandatory for called party preemption.
4.12.2 END-TO-END PERSPECTIVE

eMLPP is an extension to GSM networks of the existing MLPP service for fixed lines.
In GSM, eMLPP is a Supplementary Service that is essentially under the control of the NSS. It
allows the network to preempt resources (circuits on the A interface and/or radio resources in
the BSS) for a particular call.
The eMLPP precedence level is selected by the subscriber on a per call basis. The subscriber
may select any precedence level up to and including his maximum authorized precedence
level. The service provider at the subscriber’s originating exchange ensures that the selected
precedence level does not exceed the maximum level assigned to that subscriber.
EMLPP PRIORITY
eMLPP defines seven priority levels as A, B, 0, 1, 2, 3, and 4 (“A” being the strongest and “4”
the weakest priority). Mobile users may subscribe to all priority levels A, B, 0, 1, 2, 3, or 4.
However, priority levels A and B may only be used locally, i.e. in the domain of one MSC. The
other five priority levels are offered for subscription and may be applied globally, e.g. on inter-
MSC links, and also for interworking with ISDN networks that provide the MLPP service.
The precedence level is selected by the subscriber on a per call basis. The subscriber may
select any precedence level up to and including his maximum authorized precedence level.
The service provider at the subscriber’s originating exchange ensures that the selected
precedence level does not exceed the maximum level assigned to that subscriber at
subscription.
In public GSM, the eMLPP priority is transparent for the BSS. It is meaningful only for the
mobile and for the NSS. It is included in the following messages :
• By the mobile in the CM SERVICE REQUEST message sent to the NSS, for mobile-
originated call establishment. It indicates to the NSS the eMLPP priority requested by
the mobile for the call establishment.
Nortel confidential

• By the BSS in the PAGING REQUEST type 1, 2 ,3 messages sent to the mobile on
the PCH channel. The purpose of including eMLPP priority in paging requests is used
by mobiles who are engaged as listeners in a group call to decide to leave the group
call or not.
• By the NSS in the PAGING message sent to the BSS. The purpose of including
eMLPP priority in BSSMAP PAGING message is so that the BSS may include it in the
Paging Request (see previous bullet point)
• By the NSS in the SETUP message sent to the mobile for mobile-terminated call
establishment. It indicates to the mobile already engaged in a call whether to perform
called party preemption or not.
• By the NSS in the CALL PROCEEDING message by the network to the mobile. This
message is sent by the network to the calling mobile station to indicate that the
requested call establishment information has been received. In this message, the NSS
indicates to the mobile station the eMLPP priority level that the NSS has granted to
the call.
EMLPP SUBSCRIPTION
Two precedence levels are defined by subscriber and stored at the HLR:
• Subscriber’s Maximum Precedence Level. The subscriber may originate a call with a
precedence level up to his maximum precedence level
• Subscriber’s Default Priority Level. In the case no precedence level is sent in the “CM
service request” message, this level is used as the priority of the call
EMLPP PRIORITY SETTING AT MO CALL SETUP
For Mobile Originated point to point calls, the eMLPP priority precedence level is included
inside the CM SERVICE REQUEST message sent by the mobile to the network. Its value is
set as follows.
EMLPP SUBSCRIBER
The user may select an eMLPP priority value for the call. If he does not, the precedence is set
to its default value by the mobile.
The mobile checks that the priority is within the provisioned range.
The MSC validates the priority value, and possibly reduces it to the subscriber’s maximum
precedence stored in the VLR
Nortel confidential

NON-EMLPP SUBSCRIBER
A default priority level is set by the MSC.
4.12.3 PREEMPTION ATTRIBUTES
OVERVIEW
Each call that comes into a BSC from the NSS (via ASSIGNMENT REQUEST or HANDOVER
REQUEST) has radio resource preemption capabilities, that have been allocated to it by the
NSS.
BSS Radio resource Preemption works as follows. In case of a lack of available radio
resources, the BSC is capable of allocating currently occupied resources to incoming calls that
have a preemption capability, by preempting resources of ongoing calls that are preemption-
vulnerable.
Only TCH channels in dedicated mode, or PDTCH channels used for a CS call, are subject to
preemption.
The preemption mechanism of radio resources that is detailed here is based on the “BSSMAP
Priority” Information Element carried in ASSIGNMENT REQUEST or HANDOVER REQUEST
messages at the BSSMAP layer of the A interface. The BSSMAP priority is the input given to
the BSC by the MSC. The “BSSMAP Priority” Information Element contains preemption
attributes that are the result of the eMLPP functionality implementation in the NSS.
PREEMPTION ATTRIBUTES
The BSSMAP priority information element of a given call is optional and contained in
ASSIGNMENT REQUEST and HANDOVER REQUEST. It is sent by the NSS to the BSS, and
it provides the BSS with the eMLPP preemption capability of the call.
IF THE BSSMAP PRIORITY IS PRESENT
The BSSMAP priority information element is made up of the following 4 attributes : PCI, PVI,
QA and Priority.
PCI: preemption capability indicator. The PCI attribute is a flag that specifies whether the call
is allowed to preempt another one or not. It is applicable while negotiating the allocation of
resources :
• PCI = 0 : this allocation request (resulting from assignment or handover) cannot
trigger the preemption procedure.
• PCI = 1 : this allocation request (resulting from assignment or handover) can trigger
the running of the preemption procedure.
Nortel confidential

PVI: preemption vulnerability indicator. The PVI attribute is a flag that specifies whether the
call is allowed to be preempted by another call or not.
• PVI = 0 : this connection is not vulnerable to preemption.
• PVI = 1 : this connection is vulnerable to preemption.
QA: queueing allowed indicator. The QA attribute is a flag that specifies whether the call is
allowed to b a queueing procedure or not :
• QA = 0 : queuing is not allowed
• QA = 1 : queuing is allowed
PRIORITY : priority level. The priority attribute is an integer value in the range 1 ... 14 that
specifies the level that is applied to the call. Values 0 and 15 indicate “priority not used”.
It is built by the MSC thanks to a hardcoded lookup table that maps the eMLPP priority of the
call to the BSSMAP priority.
eMLPP priority value BSSMAP priority value

A (strongest priority) 1
B 2
0 3
1 4
2 5
3 6
4 (weakest priority) 7
IF THE BSSMAP PRIORITY IS ABSENT
If the BSSMAP priority is absent, the assignment request for that call is treated by the BSS as
though the flags were defined as follows :
• PCI = 0: no preemption capability;
• PVI = 0: no vulnerability;
• QA = 0: queueing not allowed;

• priority level = 0: no priority.
4.12.4 BSS RADIO RESOURCE PREEMPTION ALGORITHM
PROCEDURE
Definition : a vulnerable resource is a radio resource whose PVI is defined and equals 1.
Nortel confidential

Upon receiving an ASSIGNMENT REQUEST or a HANDOVER REQUEST, the BSC follows

the following allocation algorithm :
• If there is an available radio resource, the BSC immediately performs the allocation
without invoking the preemption procedure;
• If there is no available radio resource :
o If PCI = 1 attribute is set for the request, and if a vulnerable resource (PVI = 1)
is available whose priority is strictly weaker than the request’s priority, the
BSC triggers the preemption procedure : the BSC starts the release of the
active call using this vulnerable resource and starts a specific internal timer
(Tpreempt).
If the release of the vulnerable resource is completed before expiry of
Tpreempt, or if another resource is freed up in the meantime, the
assignment is successful.
if Tpreempt expires before the resource is freed up, the preemption
procedure stops and the BSC declares an assignment failure. No
queuing or directed retry is attempted.
o If PCI is absent or if PCI = 0 or if no vulnerable resource exists or if the
weakest priority of the existing vulnerable (PVI =1) resources is at least as
strong as the request’s priority, the BSC does not start a preemption
procedure. Instead :
If allowed, the queuing and directed retry procedures are started,
Otherwise the BSC declares an assignment failure.
PREEMPTION TIMER
The preemption timer value Tpreempt is computed from T3111 timer (t3111 parameter) as
follows:
Tpreempt = TdeactAck + (4 x T3111)

Tdeactack = 5 seconds (hard-coded).
VULNERABLE TCH SELECTION CRITERIA
The selection algorithm differs depending on the type of transceiver : DRX and DCU2. To
simplify, we assume that only DRX are used (not DCU2).
RANKING OF OCCUPIED TCH RESOURCES
To be considered a possible candidate for preemption by the BSC, a TCH must first fulfill the
following requirements :
o the TCH must be occupied by a FR voice call,
Nortel confidential

o and the TCH must be allocated in the large zone in case of concentric cell,
o and the PVI of the call must be equal to value 1 (preemption possible),
Such a TCH is called a “busy TCH”.
The BSC puts these potential candidates in 2 separate pools :

o hopping busy TCH pool
o non-hopping busy TCH pool
In each of these pools, the BSC classifies the TCH according to the BSSMAP priority of the
call :
o BSSMAP = 0 first (value “0” means “spare” in the GSM specs)
o Next BSSMAP = 14 (weakest priority)

o Next BSSMAP = 13
o …
o Finally, BSSMAP = 1 (strongest priority)
Busy TCH of equal BSSMAP priority are ranked as follows :
1. TCH allocated to VBS/VGCS initiators are always in front : the most recent
ones first, followed by the second most recent etc. The oldest ones are last in
the list.
2. TCH allocated to point-to-point calls or to VBS/VGCS listeners come next :

the most recent ones first, followed by the second most recent etc. The oldest
ones are last in the list.
SELECTION ALGORITHM FOR PREEMPTION
VOICE CALL ALLOCATION REQUEST

For a preemption-capable allocation request concerning a voice call, the BSC selects the TCH
timeslot to preempt based on the following algorithm :
o Choice of “busy TCH” pool : hopping TCH pool is preferred. If the “hopping busy TCH”
pool is empty, the BSC searches instead inside the non-hopping busy TCH pool.
o Once the correct pool is selected, the BSC chooses the first busy TCH in the list
(according to the ranking explained above) whose priority is strictly weaker than the
allocation request.
CIRCUIT DATA CALL ALLOCATION REQUEST

The only difference with speech concerns the choice of busy TCH pool (hopping or non-
hopping) :
Nortel confidential

o If the circuit data allocation request concerns the CSD 14.4 service and if the bts
object parameter data14-4OnNoHoppingTs = enabled, the preferred “busy TCH” pool
is the non-hopping one.
o If the circuit data allocation request concerns the CSD 14.4 service and if the bts
object parameter data14-4OnNoHoppingTs = disabled, the preferred “busy TCH” pool
is the hopping one (same a speech allocation request).
o If the circuit data allocation request concerns CSD services other than 14.4, the
preferred “busy TCH” pool is the non-hopping one(same a speech allocation request).
4.12.5 ACTIVATION PARAMETER

BSS Radio resource preemption must be authorised by a specific O&M parameter :
preemptionAuthor :
• Class 3
• signallingPoint object
• range : forbidden, authorizedWithRelease, authorizedWithForcedHO

preemptionAuthor = “forbidden” means that the BSC never performs radio resource
preemption, whatever the priority and PCI/PVI flags’ values.
preemptionAuthor = “authorizedWithRelease” means that the BSC is allowed to perform radio

resource preemption if necessary and if authorised by the MSC.A successful preemption
results in the preempted call being released.
preemptionAuthor = “authorizedWithForcedHO” means the same thing as preemptionAuthor =

“authorizedWithRelease” in the current implementation, despite the different name.
4.12.6 EMLPP PREEMPTION VERSUS PDTCH PREEMPTION

PDTCH “preemption” consists in the BSC negotiating with the PCU to be allowed to use (to
“preempt”) a PDTCH for a CS call.
Although the same word is used, PDTCH “preemption” is not the same as eMLPP preemption.
In particular, PDTCH preemption is targeted on a chosen resource, whereas eMLPP
preemption is not.
PDTCH PREEMPTION
o The BSC receives an allocation request from the MSC

o The BSC chooses a radio resource for that particular allocation request.
o If the chosen resource is a PDTCH, the BSC starts the preemption negotiation with
the PCU. No other resource can be used instead, even if a TCH is freed in the
meantime.
Nortel confidential

EMLPP PREEMPTION
o The BSC receives an allocation request from the MSC

o The BSC chooses a preemptable radio resource and starts the release of the call
currently using that resource.
o In parallel, while the preemption procedure is ongoing, the BSC puts the allocation
request that was the cause of the preemption inside a special queue entirely
dedicated to preemption-capable allocation requests.
o The first radio resource that becomes available is allocated to the preemption request
that is at the front of the queue. Therefore the radio resource that was preempted
originally is not necessarily allocated to the request which initially triggered that
particular preemption.
4.12.7 INTERWORKING
HANDOVER
During handover procedures, preemption in best cell is always preferred than fallback to
another one. Preemption leads to favour attempting to obtain a radio resource in the first cell
of the handover list (ensures better quality, but may cause additional delay to the handover
procedure completion), even though a radio resource may be immediately free in a further cell
in the list.
DIRECTED RETRY
If preemption is authorised (i.e. preemptionAuthor = “authorizedWithRelease”), and if no

resource is free, the BSC first looks to see, based on the PVI flag and the relative BSSMAP
priorities, whether a resource could be preempted.
If so, the BSC starts the preemption procedure. Then, either the preemption (and the
assignment) succeeds, or the BSC returns an assignment failure. Directed Retry cannot be
attempted as a fallback.
Therefore, Directed retry may be attempted only after the BSC has decided not to trigger the
preemption procedure (due to lack of potential candidate resources, e.g. PVI of all TCH = 0).
QUEUING
As for Directed retry, queuing may be attempted only after the BSC has decided not to trigger
the preemption procedure (due to lack of potential candidate resources, e.g. PVI of all TCH =
0). To solve a congestion issue, preemption is always considered first by the BSC. If a
preemption procedure is started and if it fails, queuing may not be attempted as a fallback : the
assignment request results in an assignment failure.
Nortel confidential

Also, the BSS priority table (allocPriorityTable) is not used by the BSS in the preemption
procedure. Only the external BSSMAP priority given by the MSC is considered by the BSC in
the preemption algorithm, regardless of the corresponding internal priority given by the BSS
priority table.
RESERVED RADIO RESOURCES
Reminder : it is possible to reserve radio resources to assignment requests of internal priority

= 0 thanks to the allocPriorityThreshold parameter. When the number of free resources falls
below allocPriorityThreshold , these remaining free resources may only be allocated to
assignment requests of internal priority = 0.
Even preemption-capable assignment requests cannot use these free timeslots if the value of
their internal priority is different from 0. They have to preempt ongoing calls on other timeslots
and leave these reserved timeslots free.
4.12.8 RESTRICTIONS
Network resources (both radio channels and fixed circuits) used by emergency calls (TS12
service) may not be preempted.
SDCCH channels may not be preempted.

The following TCH channels may not be preempted :
o TCH channels used for signalling (TCH overflow)
o TCH channels used for HR calls
All other TCH, including those used for data calls, are preemptable provided that PVI = 1.
In the very first phase of a mobile originated call establishment, in case there are no SDCCH
and no TCH available, a Channel Request is not capable of triggering a preemption.
Nortel confidential

4.13. PCH AND RACH CHANNEL CONTROL
4.13.1 PAGING COMMAND PROCESS

Paging process is triggered by the system when a mobile needs to be found (incoming calls or
short messages) in a location area (LA). The paging command is broadcast over all the cells
of the LA where the mobile is located. In idle mode, the mobile listens to the broadcast
channel (BCCH).
Paging messages are carried by the CCCH which is a sub-channel of the BCCH. It is divided
into 3 logical channels:
• Uplink: RACH (Channel Request)

• Downlink: AGCH (Immediate assignment)
• Downlink: PCH (Paging command)
Four (4) CCCH frames are necessary to transmit a complete paging message due to bursts
interleaving.
For the mobile, listening to the broadcast channels is battery consuming. Therefore the paging
messages broadcast has been optimized. Instead of listening continuously to the paging
channel, the mobile waits for specific occurrences of paging message. A set of mobiles are
associated to a specific occurrence of the paging channel, they belong to a so-called paging
group.
In order for a mobile to find its associated paging group among N groups, the following rule is
applied:
Nb of paging group = (IMSI mod1000) mod N
Dimensioning the paging means determining the number of paging groups needed to meet
incoming calls requirements inside a specific LAC. Two basic factors are taken into account:
• the number of subscribers

• the average amount of paging messages per subscriber (or average number of
subscribers that receive a paging message at the same time)
PAGING CHANNEL CONFIGURATION
According to the required number of paging groups, the CCCH configuration is consequently
tuned. This configuration depends on the TDMA model and on 2 parameters:
• TDMA Model: is the BCCH combined or not

• noOfBlockForAccessGrant: bts object parameter (class 2)
• noOfMultiframesBetweenPaging: bts object parameter (class 2)
Nortel confidential

CONSEQUENCES OF THE TDMA MODEL
The number of CCCH occurrences depends on the BCCH model, i.e., if the BCCH is
combined or not. If the BCCH is combined, there are less Frames dedicated to the CCCH.
BCCH COMBINED CASE
BCCH Multiframe representation in combined configuration
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
BCCH
CCCH
CCCH
CCCH
CCCH
BCCH
BCCH
BCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
FCCH
FCCH
FCCH
FCCH
FCCH
IDLE
SCH
SCH
SCH
SCH
SCH
When using a TDMA model with BCCH combined, there are 3 occurrences of CCCH per
multiframe of 51 frames.
BCCH NOT COMBINED CASE:
BCCH Multiframe representation in not combined configuration

CCCH
CCCH
BCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
BCCH
BCCH
BCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
FCCH
FCCH
FCCH
FCCH
FCCH
IDLE
SCH
SCH
SCH
SCH
SCH
When not combined, a BCCH multiframe carries 9 CCCH occurrences.
CONSEQUENCES OF NOOFBLOCKSFORACCESSGRANT.
From V9, whatever the value of noOfBlocksForAccessGrant, AGCH messages overlap on

PCH channels each time AGCH channels are full. The aim was to use when needed the
preemption mechanism which is better than booking a specific CCCH for Immediate
Assignment. It means that it has been defined to be sure AGCH will be treated as soon as
possible in any configuration. In that case, new priorities are applied. This gives the possibility
of a higher priority for paging messages repetitions if required on the network.
• Priority 1: Immediate assignment message never sent

• Priority 2: Paging message never sent
• Priority 3: Paging message already sent
• Priority 4: Immediate assignment message already sent
Note: see chapter Paging Parameters for more information on this parameter advised values.
SMS-CB use has some influence on noOfBlocksForAccessGrant value (see chapter Effects of
SMS-Cell Broadcast Use on “noOfBlocksForAccessGrant”).
CONSEQUENCES OF NOOFMULTIFRAMESBETWEENPAGING: CCCH

CONFIGURATION
The noOfMultiframesBetweenPaging parameter defines the frequency of a paging group

occurrence. For instance, if noOfMultiframesBetweenPaging = 3, 1 multiframe out of 3 will
carry an occurrence of a paging group.
Using the same example as above with BCCH combined, noOfBlocksForAccessGrant = 1,

and noOfMultiframesBetweenPaging = 2, one can see that one out of 2 multiframes won’t
Nortel confidential

transmit paging messages for the paging group A. This space is necessary to locate several
paging groups.
FN0
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
Block Paging Paging
BCCH
BCCH
BCCH
BCCH
FCCH
FCCH
FCCH
FCCH
FCCH
IDLE
SCH
SCH
SCH
SCH
SCH
booked group group
for AGCH nb0 (A) nb1
FN1
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
Block Paging Paging
BCCH
BCCH
BCCH
BCCH
FCCH
FCCH
FCCH
FCCH
FCCH
IDLE
SCH
SCH
SCH
SCH
SCH
booked group group
for AGCH nb2 nb3
FN2
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
SACCH
Block Paging Paging
BCCH
BCCH
BCCH
BCCH
FCCH
FCCH
FCCH
FCCH
FCCH
IDLE
SCH
SCH
SCH
SCH
SCH
booked group group

for AGCH nb0 (A) nb1
This parameter is deeply involved in the time needed to establish a call when a paging
message is coming. For instance, if a paging command is to be transmitted in a paging group
P1 just after the paging group P1 occurrence, the paging command will have to wait for at
least noOfMultiframesBetweenPaging x 240ms to be transmitted.
If noOfMultiframesBetweenPaging = 8, the time waited to transmit a paging message can be
of 2 seconds without any other delays.
From the configuration, paging group occurences are determined. In the previous example,
the paging groups will be split as follows:
Nb of Paging groups = (na - nb) x nc
• na = number of CCCH groups per BCCH multiframe

• nb = noOfBlocksForAccessGrant
• nc = noOfMultiframesBetweenPaging
Note: see chapter Paging Parameters for more information on this parameter recommended
values.
noOfMultiframesBetweenPaging has also an influence on mobile battery consumption and on
reselection reactivity (see chapter Effects of “noOfMultiFramesBetweenPaging” on Mobile
Batteries and Reselection Reactivity).
4.13.2 PAGING COMMAND REPETITION PROCESS (RUN BY BTS)

Paging messages are systematically repeated. From V8, three (3) parameters will manage
paging message repetitions:
• nbOfRepeat
defines the number of times a paging message will be repeated by the BTS
• delayBetweenRetrans
defines the number of occurrence between 2 repetitions of the same paging
group
• retransDuration
defines the maximum time allocated to broadcast a paging message
Nortel confidential

The following rule is checked at the OMC-R:
retransDuration > (delayBetweenRetrans + 1) x nbOfRepeat
This inequality is to insure at least nbOfRepeat paging transmissions when there is no

blocking on paging channel.
See chapter Paging Parameters and chapter GSM Paging Repetition Process Tuning to find
engineering rules to set these parameters.
Nortel confidential

4.13.3 REQUEST ACCESS COMMAND PROCESS

RACH are used when mobiles request a channel to establish a communication (both
terminated and initiated calls, see chapters Mobile Terminating Call and Mobile Originating
Call). Request management is configurated (nb of repetitions, time between repetitions...) at
the OMC-R thanks to different parameters.
4.13.4 REQUEST ACCESS COMMAND REPETITION PROCESS

After sending the initial CHANNEL REQUEST message, the MS starts a timer (T3120) and
listens to AGCH logical channel. When this timer expires and number of retransmissions does
not exceed maxNumberRetransmission, the MS repeats the CHANNEL REQUEST.
See also chapter GSM Paging Repetition Process Tuning.
PHASE 1 MOBILES
When the timer is started, a random value n is drawn with equal probability between 0 and N-1
where N is:
• for the initial access: max (8, numberOfSlotsSpreadTrans)

• for next attempts: numberOfSlotsSpreadTrans
T3120 is set so that there are n RACH slots between T1 and the expiry of T3120. T1 is a fixed
delay thanks to the configuration of the BCCH:
• before initial access, T1 = 0

• after initial access, T1 = 250 ms (for non combined CCCH)
• after initial access, T1 = 350 ms (for combined CCCH)
Fixed delay whose Variable delay from 0 to

value depends on numberOfSlotsSpreadTrans – 1
whether or not the RACCH
BCCH is combined
time
Nortel confidential

PHASE 2 MOBILES
Rec 04.08 have been modified to avoid double allocation (see chapter Paging Parameters).
When the timer is started, a random value n is drawn with uniform probability distribution in the
interval [S, S+1, ..., S+T-1]:
• where T is numberOfSlotsSpreadTrans
• where S depends on the BCCH configuration and on T (see following table).
numberOfSlotsSpreadTrans S on non-combined BCCH S on combined BCCH

3, 8, 14, 50 55 41
4, 9, 16 76 52
5, 10, 20 109 58
6, 11, 25 163 86
7, 12, 32 217 115
Fixed delay whose Variable delay set according to

value depends on numberOfSlotsSpreadTrans
BCCH configuration and
numberOfSlotsSpreadTrans
time
4.13.5 I MULTIPAGING COMMAND MESSAGE

The multipaging command message is a Nortel Specificity. The principle of this
implementation is to form group of paging on the Abis interface. Before BSS V14.3.1, for each
paging message receives from the MSC; one paging message is sent on Abis interface to a
target cell.
The aim of this feature is to reduce the congestion and overload messages on Abis interface.
In order to achieve this goal, a new BSC timer Called T_Paging_Group was introduced, to
define the minimum of time between two occurrences of multi paging command messages on
Abis interface.
Therefore, at emission of one multi paging command message, the BSC starts
T_Paging_Group.
If during T_Paging_Group, more than 10 paging messages are received, then only the 10
first messages are stored, thus others messages are discarded.
Nortel confidential

At T_Paging_Group expiry, either no paging message is received from the MSC or at least
more than one paging message is stored and the BSC sends these messages to the BTS.
In both cases the BSC restarts the timer.
Note: Since BSS V14.3.2 and V15.1 this maximum length is 12 paging messages.
From V15.1.1, a multi paging command is sent by the BSC in two cases:
• As soon as the 12 first paging are received by the BSC, a paging group message
is sent to the BTS leading to avoid discarding paging messages and waiting for
T_Paging_Group timer expiry.
• If T_Paging_Group timer is reached and at least one paging message is
received, a multi paging command is sent
LCaution!
The value of this T_Paging_Group is set to 200ms. Only CS paging use I Multipaging
command, therefore the PS pagings are not combined. Thus a single paging I is used for data
paging.
The following figure illustrates the principles of multipaging command
BTS
MSC BSC
Paging MS1
T_Paging_group
Paging MS2
Paging MS3 Multi paging command
MS1, MS2, MS3
T_Paging_group
Paging MS4
Multi paging command

MS4
The two major improvements bring by this feature are:
• a large Lap D bandwidth associated to the BCCH for non-paging messages, which
provides a better quality of service,
• a reduction of the CPU load generated by paging messages at BSC and BTS
levels.
However, it induces a delay (average=100ms, min=0ms, max=200ms) during the paging
management at the BSC level, and the mobile terminated call setup time is lightly increased.
LCAUTION!
Note: As this feature increases the BSS capacity, since BSS V14.3.1 it is activated by default.
Nortel confidential

4.13.6 UI MULTIPAGING COMMAND MESSAGE
PRINCIPLE
Each time a data request message (I frame on LapD) is used to convey a multipaging
message to the BTS, the BSC has to wait for an acknowledgement before sending the
next multipaging message. Therefore, the paging process is RTD dependent.
Using the Unit Data Request message (UI frame on the LapD), no acknowledgement
is required before sending the next frame, which decreases the lapd bandwidth
associated to the BCCH TRX for paging messages.
Hence, whatever is the paging number per second, the quality of service is increased
and more especially in case of large location area which generates high number of
paging messages or during exceptional events.
This feature is introduced in V15.1.1 and it allows, at equivalent paging messages
number, to better fill the downlink lapd bandwidth associated to the BCCH for paging
messages and to decrease the use of the uplink lapd bandwidth. Hence it increases
the lapd bandwidth associated to the BCCH for non-paging messages.
SPECIFICATIONS OF THE UI MULTIPAGING COMMAND MESSAGE
UI Multipaging command message uses the same mechanisms (to group the paging
command messages) as the I Multipaging command message described in below
except the ones described here under.
In order to build the UI Multipaging message, the BSC timer T_Paging_Group is
used, which defines the maximum time between 2 occurrences of UI Multi Paging
Command message on the Abis interface.
The BSC starts T_Paging_Group at emission of one UI Multi Paging Command

message.
Until T_Paging_Group expiry, as soon as a MultiPaging command message has
stored 12 unit paging command messages, it is transmitted immediately to the BTS.
At T_Paging_Group expiry, if one or more than one paging command messages are
currently stored:
• the MultiPaging command message is transmitted to the BTS and
T_Paging_Group timer is restarted
• otherwise T_Paging_Group timer is restarted
Hence, all paging requests messages accepted by the BSC filter are all sent to the
BTS which means up to 105 paging command / second.
Note: The value of this T_Paging_Group is set to 200ms and can not be modified
even via the bsc data config tool.
Nortel confidential

The Packet paging message, received from the PCU, are sent by the BSC to the BTS
(on the SAPI GSL) whereas the Circuit paging message from MSC are sent to the
BTS by the BSC on the SAPI RSL. Therefore PS and CS pagings are not sent into the
same multipaging message command.
With I multipaging command message the process of combining paging messages
into one multipaging command message is supported by CS paging only.
The restriction is removed with UI multipaging command feature as it allows
combining the packet paging messages before sending them to the BTS.
FEATURE ACTIVATION
The feature is deactivated by default and can be activated thanks to a build on line.
Recommended upgrade steps are the following:
• Upgrade of the BSC without activation of the UI MultiPaging feature (type 4)
• Upgrade of the BTS supported by the BSC
• Activation of the UI Multipaging feature in the BSC (via a build on line)
LCAUTION!
In order to identify bad PCM links and fix it, the operator should monitor the quality of
all the PCM links before the feature activation.
As soon as the BSCe3 and the TRXs of BTS are able to manage this feature, the BSC
sends UI MultiPaging Command messages.
The BSC is aware of the BTS capacity for the Circuit Service thanks to the DRX
catalog file and especially the bit 8 (from 0 to 31) of the hardware mask defined as
follow:
• 0: UI MultiPaging Command message for Circuit Service not supported
• 1: UI MultiPaging Command message for Circuit Service supported
As all types of DRX support this feature (except DCU2), there is no modification of the
"display all" feature, in order to know the activation state of this feature.
Note: As this feature is not implemented on BSC12000 and due to upgrade
constraints, then the BTS has to manage the following types of paging messages: I
paging command, I MultiPaging and UI MultiPaging command messages.
Nortel confidential

4.13.7 NETWORK MODE OF OPERATION I SUPPORT IN BSS
The Network Mode of Operation 1 (NMO1) takes benefit of the Gs interface to exchange
messages between the MSC and SGSN in order to coordinate the CS and PS paging
management and to optimize some signaling procedures.
Note that Gs interface (between SGSN and MSC) is a pre-requesite before using NMO1.
The feature should be enabled with gprsNetworkModeOperation (bts object). The parameter is
at BTS object but must be consistent at Routing Area level, i.e. activated (or de-activated) in
all cells of a given Routing Area.
PAGING MANAGEMENT
If NMO1 is activated, CS-Paging are managed through Gb interface for any GPRS-attached
MS. ClassB MS may be simultaneously attached to GSM and GPRS services but cannot
simultaneously perform CS and PS transfer.
If the MS is not attached to GPRS services, the CS-Paging procedure is not modified and
done through the A interface.
If the MS is attached to GPRS, the CS-Paging is sent from the MSC to the SGSN (Gs
interface) and then to the PCU (Gb interface):
• If the target mobile is in GMM STANDBY state, the PCU transmits the Paging
message to the BSC on the SAPI RSL. Therefore the BSC has to broadcast this
message on the CCCH of all target cells.
• If the mobile is in GMM READY state, the PCU sends the Paging on the PACCH of
the TBF or on the CCCH of the cell if there is not an established TBF for the target
mobile. In case Paging is sent on PACCH, the PCU repeats the paging message 3
times (1 emission + 3 repetitions), with a delay between 2 occurrences equal to
480 ms. This enhances the probability of success of the Paging procedure.
The 3 different cases (MS not GPRS-attached, MS in GPRS STANDY state and MS in GPRS
READY state) are illustrated below.
Note that the load of some interfaces is impacted by NMO1 activation:
• less paging on A interface Æ less load on A interface.

• more paging on AGPRS interface Æ more load on AGPRS LAPD TS.
Nortel confidential

MS attached to MS attached to
MS not attached to
GPRS services & GPRS services &
GPRS services
standby state ready state
SGSN MSC/VLR SGSN MSC/VLR SGSN MSC/VLR
PCU PCU PCU
BSC BSC BSC
BTS BTS BTS BTS BTS BTS BTS BTS BTS BTS BTS BTS
Paging on:
Paging procedure not BSC broadcasts paging
modified on CCCH • PACCH if TBF established
• CCCH if no TBF established
COMBINED SIGNALING PROCEDURES
Two procedures are combined when using NMO1:
• Combined GSM / GPRS Attach

• Combined LA / RA update.
Each procedure is performed with a single access on packet channels. This is transparent for
the PCU, which manages it as usual without any particular action. The SGSN then informs the
MSC through the Gs inteface.
The following gains are expected:
• decrease of SDCCH occupancy

• less load on A and Abis interfaces
• less load on BSC
• faster cell reselection between 2 LA.
Notes:
• As the combined procedures are performed on packet channels, it is critical to

protect the access to GPRS service and thus set minNbrGprsTs > 0
• There is a LAPD impact on Agprs interface due to the addition of cs_paging
messages for the data attached mobiles.
Nortel confidential

4.13.8 BSS CS PAGING COORDINATION

For details please refer to the functional note ([R57] and also to the aPUG document ([A1]).
PRINCIPLE
When NMO II is used, the network sends all paging messages on the PCH paging channel
even if the mobile has been assigned a packet data channel, which might require the MS to
leave the packet channel to monitoring the occurrence of paging messages. Compared to
NMO II, the BSS CS Paging Coordination is an additional mechanism for handling CS paging.
It provides an NMO I-like mechanism (BSS CS Paging Coordination) without involving the
packet core and Gs interface. This maximizes the end-user availability for receiving CS calls
and the related revenues.
While the network is running with NMO II, the BSC sends all CS paging messages received on
A interface both to the BTS and, with BSS CS Paging Coordination feature activated, to the
PCU as well. The PCU then checks whether the corresponding MS is engaged in a PS
session, by checking the IMSI. If so, the PCU sends the CS paging message to the mobile on
PACCH channel.
BSS CS PAGING COORDINATION MECHANISM
ACTIVATION PARAMETER
The activation parameter of this feature is bssPagingCoordination (class 3, bts objet).

If the network is running in Network Mode of Operation II and if BSC and PCUSN support the
BSS CS Paging Coordination feature, the bssPagingCoordination parameter serves to set
BSS_PAGING_COORDINATION bit in GPRS Cell Options to “1” to enable the BSS CS
Paging Coordination mechanism for all GPRS/EDGE mobiles.
Therefore, the behaviour of class B mobiles (from Release 97) is modified when enabling this
new BSS CS Paging Coordination in the network, provided that both the BSC and the PCUSN
support the feature.
SI13 UPDATE
The BSC updates the System Information 13 message to indicate the activation/deactivation
of the feature and sends PCU BROADCAST INFO MODIFY to provide the updated content of
the SI13 to the PCU.
DETAILED PAGING COORDINATION MECHANISM
Nortel confidential

PCUSN
SGSN MSC/VLR
SPM
p SPM p All CS pages
SPM are transferred to
the PCUSN
SPM
PCUSN nCS Pages
SPM
SPM
SPM
qSPM has
found that a BS o CS Pages
TBF is alive
for this MS
C broadcast on CCCH
o o
r CS pages BTS BTS
on PACCH
BTS BTS
BTS
No TBF alive
CS pages on
TBF alive CCCH
If the network is running in Network Mode of Operation II, when the BSC receives a CS paging
from A interface :
• the BSC broadcasts this paging message in the target cells (as it has always done so
far), regardless of bssPagingCoordination parameter value,
• and, if bssPagingCoordination is enabled on at least one cell of the area, the BSC
sends the paging message in a single BSC CS Paging message to the PCU (even if
the CS paging addressee is a list of cells) on one of the available Agprs PCM (with a
round-robin mechanism to spread the CS paging load on all Agprs PCMs connected
to this BSC).
When a PCU element receives a CS paging on its Agprs PCM, it broadcasts this message to
all PCU elements connected to the same BSC that issued the CS paging message. Each PCU
element then checks whether the IMSI value included in the BSC CS Paging message
corresponds to one of the existing MS context (i.e. a mobile that is known as currently having
an established TBF). In this case :
• if the bssPagingCoordination parameter is set to “enable BSS paging coordination” in

the corresponding cell, the PCU sends the CS paging on PACCH using the
mechanism used for Network mode of Operation I (see §4.13.7).
• otherwise the paging is discarded.
Nortel confidential

4.14. FREQUENCY HOPPING
4.14.1 FREQUENCY HOPPING PRINCIPLES

Basically, Frequency Hopping aims at spreading the spectrum of the signal to minimise the
impact of potential interferers. Frequency Hopping consists in changing the frequency used by
a channel at regular intervals.
In GSM, the transmission frequency remains the same during the transmission of a whole
burst. Thus, it is possible to have different frequencies on each burst of a frame. The radio
interface of GSM uses then slow Frequency Hopping.
According to the type of coupler used in the BTS, two (2) main types of Frequency Hopping
mechanism can be used:
• Synthesised mode for Hybrid couplers with duplexers: hopping time slots can hop
on a large band of frequencies.
• Baseband mode using Cavity couplers with duplexers: hopping time slots can hop
on a set of frequencies limited by the number of TRXs (only available with S4000
BTS).
Note: using frequency hopping allows to adapt and maximise the frequency re-use pattern
efficiency by maximising the capacity in term of offered Erlang/Mhz/km2. The pattern to use
will depend on the available frequency band and the traffic requirement.
It is possible (and recommended) to mix different frequency re-use technique, as 4X12 for
BCCH and 1X3 or 1X1 for TCH. Indeed, a traditional 4X12 reuse pattern is appropriate to a
wide spectrum allocation as for BCCH frequency (only one frequency per cell is needed).
However, in order to increase the number of TRX per cell with a given frequency band, while
keeping a low interference level, the only solution is to use more restricting reuse pattern, as
1X1 or 1X3.
See also chapter General Rules For Synthesised Frequency Hopping.
Nortel confidential

4.14.2 MAIN BENEFITS OF FREQUENCY HOPPING

• the higher the number of frequencies in the hopping law, the smaller the Fading
margin taken into account in the link budget (due to Rayleigh fading).
RXLEV cdf versus SFH
100
1 freq
2 freq
4 freq
8 freq
% 10
8 4
1
-2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
FADING MARGIN (dB)
• the smaller the mobile speed and the higher the number of frequencies, the higher
the benefit of the frequency hopping.
Frame Erasure Rate versus SFH at –104 dBm (DCS)
12.00
0.5
0.5 km/h
10.00 1.5
1.5 km/h
8.00
2.5 km/h
2.5 5 km/h
FER (%)
6.00 25 km/h
4.00
5
2.00
25
0.00
1 2 3 4 5 6 7 8
NUMBER OF FREQUENCIES FOR HOPPING
• the higher the number of frequencies in the hopping law, the narrower the Rxqual
distribution. However Rxqual mean remains the same (see figure below). Hence
the Frequency Hopping eliminates the number of bad Rxqual samples but it also
reduces the number of good Rxqual ones.
Nortel confidential

cdf RxQual with SFH, at 0.5 km/h, -104 dBm (DCS)

100
90
80
70
60
50
40
30
1 freq
4 freq
20 8 freq
4 8 16 freq
10
16
0
0 2 4 6 8 10
BER %
• Increase resistance to Rayleigh fading:

re-centred RxQual distribution for slow moving mobiles
better stability of the received signal level (smoothing effect)
completion of diversity task on uplink and full benefit on downlink
high improvement for areas of weaker signal strength (inside buildings and
on street level)
• Resistance to interference
spread of interference over all RF spectrum
spread of interference over time
highly loaded sites benefit from lower load on adjacent sites
more efficient error correction gain from digital processing
Nortel confidential

4.14.3 SYNTHESISED FREQUENCY HOPPING

Using synthesised frequency hopping, each TX is associated to one FP (TDMA) and can
transmit on all the frequencies. It is used with hybrid coupling systems then more frequencies
than TRXs can be used.
The main issue is to ensure that the frequency BCCH is transmitted all the time (on all the TS
of the TDMA) at a constant power even if there is no call to transmit (no voice or data burst).
This is done by a specific configuration which consists in dedicating a TRX to the BCCH
frequency (so the TDMA called BCCH does not hop).
Generally, the number of frequencies is greater than the number of TRX in order to have the
smallest Fading margin in the link budget.
BCCH Freq
TDMA1 TX1
TDMA2 TX2
TDMA3 TX3
TDMA4 TX4
MAIO
MA frequency list
The TDMA configurations in case of synthesised frequency hopping are defined as follows:
• F1 is the BCCH frequency.

• the other two TDMA of the cell have the same MA. HSN and MAIO can be
different.
Nortel confidential

4.14.4 BASEBAND FREQUENCY HOPPING
PRINCIPLE
Using baseband frequency hopping, each TX is dedicated to one frequency and is connected
to all the Frame Processor (TDMA) via the FH bus. It is used with cavity coupling system. It
uses exactly the same number of frequencies as TRXs.
The filling is done by the FP according to the configuration of the TDMA (all the parameters for
the frequency hopping are static and not per call basis; so even if there is no call the FP
knows if it has to transmit on the BCCH frequency).
Moreover the TX can have a carrier filling functionality which is not useful for the BCCH
frequency (Carrier filling is already done by the FP) but which can be used in case of other
frequencies carrier filling with the use of a specific BCF load.
BCCH Freq
FP1 TX1
FP2 TX2
FP3 TX3
FP4 TX4
Filling burst when there is no information If filling is needed on other frequencies,

to transmit on the BCCH frequency. it is managed by the TXs.
For a given cell with the previous configuration (4 TRX), one Mobile Allocation should be
defined:
• MA0 contains all the frequencies except the BCCH frequency (3 frequencies in the
exemple).
The baseband frequency hopping configuration is the following:
• hopping on TCH, no hopping on BCCH
Nortel confidential

TS 0 1 2 3 4 5 6 7
TDMA 0 F1 F1 F1 F1 F1 F1 F1 F1 MAIO=0
TDMA 1 MA0 MA0 MA0 MA0 MA0 MA0 MA0 MA0 MAIO=1
• MA: Mobile Allocation (list of hopping frequencies for a TRX)

• MAIO: Mobile Allocation Index Offset between 0 and (Nb of Freq in MA - 1).
• F1: BCCH frequency
LCAUTION!
It is not recommended to hop on BCCH frequency when using baseband frequency hopping,
because it can lead to some troubles when downlink DTX or downlink power control are
enabled.
RECONFIGURATION PROCEDURE
This procedure is not applicable to BTS that use hybrid coupling.

With the baseband frequency hopping mechanism (used only by BTS that have cavity
couplers), it is possible to reconfigure the frequencies in certain cases. In case of equipment
failure/recovery within a TRX, the BSC starts the reconfiguration process for a Radio Cell
which supports frequency hopping and uses the Frequency Management GSM function.
This function is supported by the TRX and allows the BSC to configure or to reset a frequency
on a TX which is identified by the TEI of the corresponding TRX. The loss of one TX implies
the loss of one frequency (which is not the BCCH) and of one TDMA (the one defined with the
lowest priority) if no redundant TRX.
Two symmetric mechanisms are managed by the BSC to handle the automatic frequency
reconfiguration in the case of frequency hopping cavity coupling BTS:
• loss of a frequency
the cell is stopped and restarted with new set of frequencies. This may lead
to release the calls if there is more live TX than btsThresholdHopReconf
• recovery of all frequencies
an automatic reconfiguration is triggered by the BSC when all the
frequencies are recovered. This may lead to release the calls
There will be a reconfiguration if the flag bscHopReconfUse is set to “true” (defined at BSC
level) and if there are more frequencies than the threshold btsThresholdHopReconf (defined at
BTS level). Otherwise the cell is badly configured.
When a end of fault occurs if the flag btsHopReconfRestart is set to “true” and if there are
more frequencies than the threshold (btsThresholdHopReconf), there is a complete cell
reconfiguration.
Nortel confidential

4.14.5 AD-HOC FREQUENCY PLAN

The Ad-Hoc frequency hopping does not reproduce a pattern all over the network. Frequency
planning is done (HSN, MAIO, MA lists) according to the interference matrix. The particularity
is that the number of hopping TRX = the number of hopping frequencies in most of the cases.
A frequency plan optimizes frequency hopping list of each sector in order to reduce the
interferences. The length of the frequency hopping list is variable (it should be at least equal to
the number of TRx on the sector).
BCCH Freq
TDMA1 TX1
TDMA2 TX2
TDMA3 TX3
TDMA4 TX4
MA frequency list: n frequencies for n TRX
For ad-hoc frequency planning, an interference matrix or a very intense and accurate drive
tests campaign is needed. A frequency planing tool can also be used.
For each method the principle is the same: take into account DL BCCH and HO interactions
between cells. The frequencies on the list are planned intelligently in order to avoid collision
with the neighboring cells, allocating same frequencies on the hopping list to cells which are
far in distance or that the interaction between them is the minimum as possible.
There is a reduction on the number of frequencies on the frequency hoping list. It is
recommended to space the maximum as possible (at least 3 channels) the frequencies used
in the same frequency list to maximize frequency hopping gain (fading reduction)
Every sector of one site has a different HSN in order to minimize co-channel or adjacent
collisions.
The main drawback is the cost to maintain the plan since regularly it is recommended to
review the plan in order to optimize its performances.
Ad-hoc should be considered as a spectral efficiency feature in a constraining bad condition

assuming the cost associated. In case of non frequency band constraining conditions, 1x1 has
shown a great cost-performance trade-off and is worth to use in the case of a fast growing
network in order to minimize operational impacts.
In summary Ad-Hoc frequency plan allows good performances if the calculation method is
very precise (either Interference matrix, drive tests or frequency planning tool) and number of
hopping frequencies per TDMA is sufficicent (at least MA list ≥ 4 frequencies)
Nortel confidential

4.15. BSC OVERLOAD MANAGEMENT MECHANISMS

The aim of such a feature is to avoid BSC restart or crash because of overload conditions.
Without defense mechanism, an overload of one of the BSC boards will imply a suicide of the
active chain, a switch to the passive chain and at last a suicide of the new active chain. This
implies a suppression of all the communications and an interruption of service.
For further details on this feature please refer to BSS Engineering Rules in chapter Reference
Documents
4.15.1 BSC12000 OVERLOAD MANAGEMENT

This overLoad management mechanism is based on the following principles:
• Current CPU load for MPU / BIFP / OMU / SICD and memory resources are
supervised (including also OMU-SUP-SWC chained boards)
• Resources fluctuation trends are analysed and taken into account for anticipation
purpose
• Each board monitors its own load and neighboring involved board load, and
makes decisions dependent of all others
• Decisions are taken only on traffic stimuli, not O&M stimuli
Such a mechanism is able to take into account not only traffic CPU load but O&M CPU load
and to trigger an upstream or downstream protection (but based only on traffic stimuli).
BSC12000 DIMENSIONING RULES
LOCAL CARD SYNTHETIC LOAD
A local card “synthetic” load is generated each second by each board.

This synthetic load is given as the result of:
• the CPU load occupancy,

• the memory resource occupancy,
• the resources fluctuation trends (only positive variations of CPU/memory
occupancy values according to the previous one are taken into account for
anticipation purpose)
Note: CPU or memory resource occupancy is corrected to give the higher weight to the more
critical factor (i.e. a lack of timer may lead to a BSC switchover, thus timers have a weighting
factor more important than CPU load).
LOCAL CARD OVERLOAD LEVEL
This local card synthetic load, compared with the overLoad threshold value associated with
current board, is converted into a local card overLoad level [levels 0..3] and sent to a
centralized overLoad control task located on the OMU board.
Nortel confidential

OMU-SUP-SWC CHAINED BOARDS
By the same way, the OMU-SUP-SWC cain is monitored in order to generate an associated
overload level.
GSM OBJECT & OPERATION OVERLOAD LEVEL
Thus firstly, this centralized task collects and computes different overLoad levels to determine:
• the overLoad level of each cellGroup, showing the overLoad level of each BIFP
board (used for instance by TMG to select BIFP board to “propagate” a
pagingRequest from A-I/F or an incoming external handover)
• the overLoad level of each CELL, showing the highest overLoad level between
SICD boards handling this GSM object instance
• the overLoad level of each SITE, showing the highest overLoad level between
• the overLoad level of each TCU, showing the highest overLoad level between
COMPUTED INFORMATION REDISTRIBUTED
Then secondly, this centralized task collects and computes different overLoad levels to
determine the overLoad level of the operation family (i.e Paging Request, Network Access,
Location Updating...) indicating the highest overLoad level between potentially impacted
boards OMU / MPU / SICD / BIFP / OMU-SUP-SWC.
OVERLOAD LEVEL CONTROL
Lastly, before processing any operation, each board (i.e. each applicative task located on this
board, impacted by this operation) must check:
• its local overLoad level,

• the overLoad level associated to the current operation,
• the overLoad level of the impacted object instances
Example:
Before processing a pagingResponse at BIFP level, TMG (TMG-RAD and TMG-CNX located
on BIFP board) checks:
• its local overLoad level (i.e.its own overlLoad level... at BIFP level)
• the overLoad level of the “network access” operation family (i.e. overLoad levels of
OMU-SUP-SWC, OMU and MPU boards involved)
• the overLoad level of the each CELL impacted by this operation (i.e. over-Load
levels of the impacted SICD board)
List of the operations to be filtered
Despite the fact, this mechanism is defined as a “centralized” overLoad control method,
actions are triggered at local level (i.e. by each board). Following actions can be done only on
traffic reduction purpose according overLoad level and operation type:
Nortel confidential

• overLoad level 1: traffic reduction around 33% by filtering 1 request out of 3 of the
following messages:
Paging Request,
Channel Request with cause different from “Emergency call”,
All First Layer 3 messages with cause different from “Emergency call”,
HandOver for traffic reason,
HandOver for O&M reason,
Directed Retry.
• overLoad level 2: traffic reduction around 66% by filtering 2 requests out of 3 of
the previous messages.
• overLoad level 3: no new traffic is accepted by screening all previous and
following messages:
All First Layer 3 messages,
All Channel Request (including causefor “Emergency Call”),
All Handover Indication,
All Handover Request.
Note: when communications need to be filtered to reduce the load of the BSC, it can be done
for all the BTSs or CELLs supported by the overLoaded board !
PROTECTION AT STARTING OR SWITCHING
During the first 30mn of a BSC restart, all thresholds are decreased by 30%, in order to give
more power to the O&M operations.
When a BSC is in simplex mode, all thresholds are decreased by 20%, in order to reduce the
risk of outage in this phase.
CHOOSING PARAMETERS
The internal overload parameters have been .validated in R&D for V12 and upper releases
and must not be changed.
Refer to the processorLoadSupConf parameter.
CAPACITY IMPACT
As overLoad mechanism is based on real measurement, robustness has been increased as

rejected rate for incoming calls. In other terms, same traffic can be carried by the BSC but with
higher rejected rate for incoming calls in case of overload.
ALARM NOTIFICATION
Alarm notification number is 1490 “BSC OverLoad”.

This alarm is triggered for the first card which is in overLoad level 3 for 5sec at less and ended
when all cards are under the OverLoadLevel 3 for 5sec at less.
Nortel confidential

4.15.2 BSC3000 OVERLOAD MANAGEMENT

The Overload software manages the board load and the global load of the system so as to
avoid the crash in case of overload. On the BSC sub-system an overload situation is mainly
due to the traffic management which is computed on the TMU module. The overload software
uses system indicators to calculate overload levels that allow applications to decrease the load
level.
BSC3000 DIMENSIONING RULES
The BSC is responsible for accepting or rejecting sites creation or reparenting in order to
ensure that the hardware capacity is sufficient to handle the traffic.
The maximum dimensioning of a BSC 3000 is 3000 Erlang, 500 Sites, 600 Cells, 1000 TRX,
16 SS7 links, 567 LAPD links. A good dimensioning lead to the following relations:
Carried Traffic ≤ BSC hardware capacity (number of TMU)
Offered Traffic ≤ BSC hardware capacity (number of TMU)
CARRIED TRAFFIC
The carried traffic (or real traffic) is the number of simultaneous voice communication a BSC
handles at the busy hour. The carried traffic is given by the customer for an area or can be
observed with monitoring. It is necessary to consider a margin carried traffic for a lot of
reasons (GPRS traffic is increasing lightly the load on the TMU, Load balancing algorithm
shares fairly the load between TMU, The operator wants to be able to absorb additional traffic
in case of special Event).
As a consequence it is recommanded to use a margin of about 20-25 % when considering the
carried traffic.
Moreover AMR handset penetration should be considered if half rate vocoder is used on a
network since it increases offered capacity on radio sites.
OFFERED TRAFFIC
The offered traffic in a cell is the number of simultaneous users that can use a resource with a
target quality of service objective (blocking rate). This step will consist in determining the
values of table ERLANG_PER_N_TRX_CELL in order to let the BSC computes the most
adapted offered erlang.
TMU NUMBER
To set the appropriate number of TMU boards please refer to the BSS Engineering Rules
(Reference Documents).
Nortel confidential

BSC3000 OVERLOAD MECHANISM
The overload mechanism only applies to TMU boards. TMU boards are SBC and PMC, from
V16.0 a new TMU was introduced:TMU2 . This new TMU has only one board, the SBC one.
OMU and interface node overload are not managed.
This overload mechanism is based on the following principles:
• Decisions are only taken on traffic stimuli, not on O&M stimuli. On the BSC sub-
system, an overload situation is mainly due to the traffic management, which is
computed on the TMU module
• Each TMU monitors its overload level and decisions will be applied to all the cell-
groups it manages.
The overload management concerns overload levels of two boards of the TMU:
• SBC board (based on CPU usage, memory and waiting time of messages in the
mailbox)
• PMC board (based only on CPU usage).
For TMU2 the overload management concerns one board only (therefore the monitoring
counter pegged is the one associated to SBC )
Overload architecture is hierarchically organized:
• 1) the elementary overload level is returned from SBC and PMC by comparing their
level of CPU, memory and mailbox resources to specific thresholds
• 2) the maximum of these elementary overload level gives the local overLoad level
• 3) for each new local overload level received, each TMU computes its
TMUOvLevel(i) as the maximum of all the local overload levels of the boards it
manages. TMUOvLevel(i) is then sent to a centralized overload control task
located on the OMU that will trigger the appropriate action for TMU(i).
The actions are triggered at TMU level, as TMU are rather independent one from the other in
terms of overload handling. When a TMU is in overload, it will filter partially the new coming
traffic requests related to the cell-groups it manages.
LIST OF OPERATIONS TO BE FILTERED
• Overload level 1: filtering 33,33% requests of the following messages:

Paging request
Channel request with cause different from “Emergency call”
All first layer 3 messages with cause different from emergency call
Handover for traffic reason
Directed retry
• Overload level 2: filtering 66,66% requestsof the messages described above
• Overload level 3: no new traffic is accepted by filtering all previous and following
messages
All first layer 3 messages
All handover indication
All handover requests
Nortel confidential

PARAMETERS
No specific new counters or configuration parameters are introduced with this feature.
4.15.3 LOAD BALANCING

The Load Balancing is a mechanism that allows a distribution as balanced as possible (from
the traffic weight point of view) of the Cell Groups (CG) among the existing TMUs (See
chapter BSC Boards Management) during the initialization phase. It also allows a
redistribution of the CG on the TMUs (if all the CG are duplex), without disturbing the
established calls when:
• A TMU module fails or comes into operation (for hardware or operator reasons)
• An imbalance of the TMU loads is detected by the BSC (on online operations such
as new TMU board, new BTS, or new TRX). In this case, the load balancing can
be manually started.
For further details on this feature please refer to the corresponding chapter in the BSS
Engineering Rules (chapter Reference Documents).
4.15.4 V15.1 EVOLUTION OF LOAD BALANCING

In V15.1 some evolutions are introduced in the Cell Group Management and Load Balancing
algorithms used by the BSCe3. These evolutions are made in order to take into account the
introduction of new TMU boards (TMU2), to better introduce new big site configurations.
MAIN EVOLUTIONS
Global dimensioning constraints for the BSC remain unchanged: the BSC capacity is, as in
V14.3, V14.3.1 and V15.0 limited by the following maximum number of managed objects:
• Maximum of 1000 TRX per BSC

• Maximum of 600 Cells per BSC
• Maximum of 500 Sites per BSC
• Maximum of 1 PCUSN per BSC
• Maximum of 2 TCUe3 per BSC
• Maximum of 32 TCU2G per BSC
Concerning the maximum site configuration supported in V15.1, the limitations are the
following:
• Maximum of 16 TRX per Cell

• Maximum of 48 TRX per Site
Moreover, the maximum capacity of the BSC remains 3000 Erlang.
The rules to respect the same dimensioning constraints for the TMU and TMU2 boards are
defined in the BSS Engineering Rules (see chapter Reference Documents), as well as those
existing for the Cell Group definitions.
Nortel confidential

PACKAGING OF CG IN ERLANG
The previous packaging of site in CG was previously based on the number of TRX. The
addition of a site of N TRX in an existing CG was roughly done if the CG had no more than 16-
N TRX, else an empty CG was chosen. The maximum number of TRX per CG (48) could be
an issue in the case of site extension or big site introduction in V15.0.1 (with more than 40
TRX).
In V15.1, the packaging of sites in CG is now based on a target in Erlang. The weight of each
site is estimated and this estimation is used for the packaging of the CG: the objective is to
have a target of 84 Erlang per CG. So the principle of the algorithm remains the same: the
addition of a site with N TRX in an existing CG is roughly done if this one has no more than 84
Erlang. If no more empty CG remains, the site is added in the existing CG with a maximum
constraint of 10 sites per CG. A site created on line is considered with a value of Erlang
corresponding to a site of one Cell with 8 TRX.
ESTIMATEDSITELOAD PARAMETER
In V15.1 is introduced a new parameter called estimatedSiteLoad. This parameter (applicable

to the btsSiteManager object) allows specifying the value in Erlang for a given site. This
parameter is optional (default value 0).
If this parameter is not specified (value of 0), the BSC will use the ERLANG_PER_N_TRX
table for the estimation of the site’s weight, else it is the estimatedSiteLoad value that is used.
This weight will be considered for the placement of the site into a CG and naturally also for the
CG distribution on the TMU.
This parameter is a class 3 parameter. Thus, this one may be used at site creation (off line or
on line) but may also be changed at any moment while the site is operational. On an online
change of this parameter, the BSC will regenerate the site weight estimation (and the CG
weight estimation) and will perform a new CG re-balancing if needed (as in case of a TRX
addition for instance: the packaging of sites in CG are not re-performed, but the distribution of
the CG according to new CG weight will be reconsidered: if the capacity of the TMU hosting
the active CG or the passive CG reach their limits, the algorithm considers if it can move these
CG to other TMU. Otherwise, it suppresses the CG that can not fit).
Please refer to the BSS Engineering Rules (see chapter Reference Documents) for further
informations on the use of that parameter.
Nortel confidential

4.16. CABINET OUTPUT POWER SETTING

This section aims at describing the way to determine the output power of a BTS knowing its
coupling and its associated parameter setting. As described in following figure, two OMC
parameters are involved: bsTxPwrMax (powerControl object) and from V9, attenuation
(btsSiteManager object).
4.16.1 CABINET POWER DESCRIPTION

There are three steps in the cabinet output power evaluation.
OMC attenuation
(since V9)
DLU
attenuation OR
(until V8)
Tx
Tx
bsTxPwrMax Pc Pr Coupling
Coupling
Ps
translation
translation system
system
SUM
table
table
Pc: bsTxPwrMax + DLU/OMC attenuation

Pr: given by a translation table
Ps: Cabinet output power
Nortel confidential

4.16.2 PR COMPUTATION
S8000/S12000 FAMILY
This is the table mapping the bsTxPwrMax and the Pr for S8000 and S12000 products (in
function of the coupling system).
BTS S8000 (In/Out) & S12000 (In/Out)

Coupling system ⇒ Duplexor & Tx filter H2D H4D
DLU attenuation or
1 4 8
OMC attenuation ⇒
Pr Pr Pr
BsTxPwrMax
⇓ ⇓ ⇓
⇓
PA / ePA HePA PA / ePA HePA PA / ePA HePA
51 Nack Nack Nack Nack Nack Nack
46 Nack Pmax Nack Nack Nack Nack
45 Nack Pmax Nack Nack Nack Nack
44 Nack Pmax -2 Nack Nack Nack Nack
43 Pmax Pmax -2 Nack Pmax Nack Nack
42 Pmax Pmax -4 Nack Pmax Nack Nack
41 Pmax -2 Pmax -4 Nack Pmax -2 Nack Nack
40 Pmax -2 Pmax -6 Pmax Pmax -2 Nack Nack
39 Pmax -4 Pmax -6 Pmax Pmax -4 Nack Pmax
38 Pmax -4 Pmax -8 Pmax -2 Pmax -4 Nack Pmax
37 Pmax -6 Pmax -8 Pmax -2 Pmax -6 Nack Pmax -2
36 Pmax -6 Pmax -10 Pmax -4 Pmax -6 Pmax Pmax -2
35 Pmax -8 Pmax -10 Pmax -4 Pmax -8 Pmax Pmax -4
34 Pmax -8 Pmax -12 Pmax -6 Pmax -8 Pmax -2 Pmax -4
33 Pmax -10 Pmax -12 Pmax -6 Pmax -10 Pmax -2 Pmax -6
32 Pmax -10 Nack Pmax -8 Pmax -10 Pmax -4 Pmax -6
29 Nack Nack Pmax -10 Nack Pmax -6 Pmax -10
26 Nack Nack Nack Nack Pmax -10 Pmax -12
25 Nack Nack Nack Nack Pmax -10 Nack
22 Æ 0 Nack Nack Nack Nack Nack Nack
For more details on the Pmax per products, please refer to the Engineering Rules (ref. [R47]
to ref. [R56]).
Nortel confidential

LCAUTION!
There is no exact match between the power emitted with a PA/ePA (even power) and the
power emitted with a HePA (odd power)
BTS18K/6K FAMILY
This is the table mapping the bsTxPwrMax and the Pr for BTS6000 & BTS18000 product (in
function of the configuration). Note: That H4 is not used for BTS6000
RM 30W RM 40W RM 50W RM 60W – HPRM 60W

Configuration
D H2 H3 H4 D H2 H3 H4 D H2 H3 H4 D H2 H3 H4
attenuation 1 4 6 8 1 4 6 8 1 4 6 8 1 4 6 8
Pmin-Pmax 31-44 33-46 34-47 34-47
bsTxPwrMax
51 -> 48 Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack
47 Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack
46 Nack Nack Nack Nack Nack Nack Nack Nack Pmax Nack Nack Nack Pmax Nack Nack Nack
45 Nack Nack Nack Nack Pmax Nack Nack Nack Pmax Nack Nack Nack Pmax Nack Nack Nack
44 Nack Nack Nack Nack Pmax Nack Nack Nack Pmax -2 Nack Nack Nack Pmax -2 Nack Nack Nack
43 Pmax Nack Nack Nack Pmax -2 Nack Nack Nack Pmax -2 Pmax Nack Nack Pmax -2 Pmax Nack Nack
42 Pmax Nack Nack Nack Pmax -2 Pmax Nack Nack Pmax -4 Pmax Nack Nack Pmax -4 Pmax Nack Nack
41 Pmax -2 Nack Nack Nack Pmax -4 Pmax Nack Nack Pmax -4 Pmax -2 Pmax Nack Pmax -4 Pmax -2 Pmax Nack
40 Pmax -2 Pmax Nack Nack Pmax -4 Pmax -2 Pmax Nack Pmax -6 Pmax -2 Pmax Nack Pmax -6 Pmax -2 Pmax Nack
39 Pmax -4 Pmax Nack Nack Pmax -6 Pmax -2 Pmax Nack Pmax -6 Pmax -4 Pmax -2 Pmax Pmax -6 Pmax -4 Pmax -2 Pmax
38 Pmax -4 Pmax -2 Pmax Nack Pmax -6 Pmax -4 Pmax -2 Pmax Pmax -8 Pmax -4 Pmax -2 Pmax Pmax -8 Pmax -4 Pmax -2 Pmax
37 Pmax -6 Pmax -2 Pmax Nack Pmax -8 Pmax -4 Pmax -2 Pmax Pmax -8 Pmax -6 Pmax -4 Pmax -2 Pmax -8 Pmax -6 Pmax -4 Pmax -2
36 Pmax -6 Pmax -4 Pmax -2 Pmax Pmax -8 Pmax -6 Pmax -4 Pmax -2 Pmax -10 Pmax -6 Pmax -4 Pmax -2 Pmax -10 Pmax -6 Pmax -4 Pmax -2
35 Pmax -8 Pmax -4 Pmax -2 Pmax Pmax -10 Pmax -6 Pmax -4 Pmax -2 Pmax -10 Pmax -8 Pmax -6 Pmax -4 Pmax -10 Pmax -8 Pmax -6 Pmax -4
34 Pmax -8 Pmax -6 Pmax -4 Pmax -2 Pmax -10 Pmax -8 Pmax -6 Pmax -4 Pmax -12 Pmax -8 Pmax -6 Pmax -4 Pmax -12 Pmax -8 Pmax -6 Pmax -4
33 Pmax -10 Pmax -6 Pmax -4 Pmax -2 Pmax -12 Pmax -8 Pmax -6 Pmax -4 Pmax -12 Pmax -10 Pmax -8 Pmax -6 Pmax -12 Pmax -10 Pmax -8 Pmax -6
32 Pmax -10 Pmax -8 Pmax -6 Pmax -4 Pmax -12 Pmax -10 Pmax -8 Pmax -6 Nack Pmax -10 Pmax -8 Pmax -6 Nack Pmax -10 Pmax -8 Pmax -6
31 Pmax -12 Pmax -8 Pmax -6 Pmax -4 Nack Pmax -10 Pmax -8 Pmax -6 Nack Pmax -12 Pmax -10 Pmax -8 Nack Pmax -12 Pmax -10 Pmax -8
30 Pmax -12 Pmax -10 Pmax -8 Pmax -6 Nack Pmax -12 Pmax -10 Pmax -8 Nack Pmax -12 Pmax -10 Pmax -8 Nack Pmax -12 Pmax -10 Pmax -8
29 Nack Pmax -10 Pmax -8 Pmax -6 Nack Pmax -12 Pmax -10 Pmax -8 Nack Nack Pmax -12 Pmax -10 Nack Nack Pmax -12 Pmax -10
28 Nack Pmax -12 Pmax -10 Pmax -8 Nack Nack Pmax -12 Pmax -10 Nack Nack Pmax -12 Pmax -10 Nack Nack Pmax -12 Pmax -10
27 Nack Pmax -12 Pmax -10 Pmax -8 Nack Nack Pmax -12 Pmax -10 Nack Nack Nack Pmax -12 Nack Nack Nack Pmax -12
26 Nack Nack Pmax -12 Pmax -10 Nack Nack Nack Pmax -12 Nack Nack Nack Pmax -12 Nack Nack Nack Pmax -12
25 Nack Nack Pmax -12 Pmax -10 Nack Nack Nack Pmax -12 Nack Nack Nack Nack Nack Nack Nack Nack
24 Nack Nack Nack Pmax -12 Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack
23 Nack Nack Nack Pmax -12 Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack
≤ 22 Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack Nack
Nortel confidential

4.16.3 PS COMPUTATION
Then, the effective cabinet output power is:
Ps = Pr - cablesLoss - couplingLoss
Pr is derived from Pc (where Pc = bsTxPwrMax + OMCattenuation or DLU attenuation) based

on the translation table (§ 4.13.2). Pr can only be equivalent to Pmax in case when the
operator has chosen the maximum value for bsTxPwrMax for a given coupling system.
POWER AMPLIFIER 30W
The nominal output power output for PA is 44.8 dBm (+/- 0.5dBm). This nominal output is the
same for all frequencies.
HIGH POWER EDGE POWER AMPLIFIER (HEPA)
The nominal power output for HePA depends on the frequencies and on the product. Please
note that not all product support HePA for all the frequency bands.
For more details on HePA output power as a function of the product and the frequency band,
please refer to the appropriate Engineering rules document ([R47] to [R56])..
COUPLING SYSTEM
To know the input power, it is important to factor in the system coupling losses. Please refer to
the appropriate Engineering rules document ([R47] to [R56]).
CABLE LOSS
For the values of the losses depending on the BTS configuration and frequency band, please
refer to the appropriate Engineering rules document ([R47] to [R56]).
RF/IO CABLE
It is the RF cable connecting the Antenna connector of the duplexer to the output connector (to
connect the antenna feeder).
Each cable is specifically dedicated to a frequency band. This particularity is due to the quarter
wave lightning protector which must be adapted to the frequency band.
S8000 Example: Maximum insertion attenuation (guaranted):
• GSM 900: 0.2 dB Outdoor BTS, 0.25 dB Indoor BTS
Nortel confidential

• GSM1800&1900: 0.3 dB Outdoor BTS, 0.35 Indoor BTS

• Characteristic impedance: 50
• Total length: 290 mm
• Maximum cable diameter: 7 mm
CABLE BETWEEN PA AND COUPLING SYSTEM
It is the RF cable connecting the PA (Power Amplifier) output connector to the input connector
of the Hybrid combiner.
S8000 Example: Maximum insertion attenuation (guaranted):
• Cable total length: L ≤ 305 mm

• GSM 900: 0.25 dB Outdoor BTS, 0.35 dB Indoor BTS
• GSM1800&1900: 0.40 dB Outdoor BTS, 0.5 dB Indoor BTS
• Characteristic impedance: 50
• Maximum cable diameter: 5.5 mm
PS COMPUTATION EXAMPLE
Calculation for S8000 Outdoor coupling duplexor, GSM 900 band :
• Pr = 44.8 dBm +/- 0.5 dB

• PA-coupling system cable loss = 0.25 dB
• RF/IO cable loss = 0.2 dB
• Duplexor loss = 1.0 dB

Therefore : Ps = 44.8 (+/- 0.5dB) – (0.2+0.25) – 1= 43.35dB (+/-0.5dB)
Nortel confidential

4.17. SYSTEM INFORMATION MESSAGES RELATED FEATURES
4.17.1 DUAL BAND HANDLING

The purpose of this feature is to allow an operator with licenses in several frequency bands to
support the use of multiband mobile stations in all its bands. In addition, it also allows the
operator to support the use of single band mobile stations in each band of the license. The
specification indicates that GSM900 and GSM1800 frequency bands can be combined. No
frequency band is treated as the primary band. However, parameter setting can help
multiband MS to give a higher priority to one of the bands.
LCAUTION!
It has been experimented that with some mobile brands a delay in the other band neighbor
cells reports occurs, i.e. a minimum time is necessary for those mobiles to send
measurements from neighbors transmitting of the other band to the current cell.
MULTIBAND MOBILE STATION
A multiband mobile station is a mobile station which:
• supports more than one band

• has the functionality to perform handover, directed retry, channel assignment, cell
selection and cell reselection between the different bands in which it can operate
(within the PLMN)
• has the functionality to make PLMN selection in the different bands in which can it
operate
• has 2 receivers, one specific to each band
• has 2 transmitters, one specific to each band
MODIFIED SYS INFO 3
Two new fields have been added to SYS INFO 3:
EARLY_CLASSMARK_SENDING_CONTROL
It indicates if multiband MS is authorized to send the early Classmark Change message to the
BSC via the BTS. This allows the MSC to receive as soon as possible the multiband
information and to pass it to the target BSC. It will speed up call set-ups and allows to perform
Handover and directed retry when needed. The Classmark Change indicates the frequency
bands supported by the MS and MS power classes to perform HO procedures in the best
conditions.
The corresponding parameter is the class 3 attribute early classmark sending belonging to bts
objects. If it is set to “enabled”, the Classmark_Change message is sent just after the SABM
and UA frames exchange on the Immediate_Assignment procedure. This message makes
interband handover procedures possible. Moreover this parameter allows the mobile to send
its capacity downlink Advanced Receiver performance. That helps to have SAIC mobile
penetration
Nortel confidential

In single band networks, early classmark sending will be set to “disabled”.

Note: indeed monoband network may forbid a dual band mobile to use the Early Classmark
sending procedure in order to prevent phase 2 mobiles to send useless information to the
network, and to cope with any potential problems with this feature in the mobiles.
SYS_INFO_2TER_INDICATOR
It is used to inform multiband MS that SYS INFO 2ter information is available.
NEW SYS INFO MESSAGES
The neighbouring cell lists for handover and cell reselection are broadcast towards multiband
and single band mobile stations. The frequencies of neighbouring cells in other frequency
bands than the current cell will be carried by new SYS INFO messages:
• SYS INFO 2ter for reselection neighbours.

• SYS INFO 5ter for handover neighbours.
A single band mobile station will only use frequencies from SYS INFO 2 and 5 and if
necessary, 2bis and 5bis for reselection and handover purposes, i.e. frequencies from the
frequency band it supports. The BSC selects neighbour cells from the other band out of the
neighbour list and sends them in SYS INFO 2ter and 5ter (see table below).
Sys info 2 Sys info 2bis Sys info 2ter

Sys info 5 Sys info 5bis Sys info 5ter
GSM900 cell GSM900 nei list - GSM1800 nei list
GSM 1800 cell GSM1800 nei list GSM1800 nei list GSM900 nei list
NEIGHBOUR CELL LIST IN SYS INFO
The new SYS INFO 2ter and 5ter messages carry parameters which are needed by multiband
mobile stations to perform respectively cell reselection (2ter) and handover (5ter) towards cell
from another band:
• Multiband Reporting: indicates to multiband MS the minimum number of cells to

report in their measurement report outside the current frequency band. Its value is
equal to the Multiband reporting parameter in the SYS INFO 5ter message.
• Neighbouring Cells List: coding of the frequencies of neighbouring cells.
LCAUTION!
Some single band mobiles are disturbed by the receipt of SYS INFO 5ter. They react by
sending an RR status message, that can load the BSC. To avoid this, the sending of these
messages is controlled by the BTS. On the opposite, single band mobile stations are not
disturbed by 2ter messages because they ignore them.
No field called ‘Sys_Info_5ter_Indicator’ exists. To know if 5ter messages are sent, SACCH
filling messages are used.
The parameter cellBarQualify is not used by some dual band MS in selection and reselection
algorithms.
Nortel confidential

MULTIBAND REPORTING
Multiband mobile stations report cells from different frequency bands according to Multiband
Reporting parameter (corresponding to class 3 attribute ‘multi band reporting’ of bts objects)
broadcast in SYS INFO messages:
• the six strongest cells: default value. The multiband MS reports the six strongest
allowed cells regardless of the frequency band.
• 1, 2, 3: the multiband MS reports the strongest or the two, three strongest allowed
cells outside the current frequency band. The remaining space in the report is
used to give information about cells in the current frequency band. If there are still
some remaining positions (not enough neighbours in the current frequency band),
these positions are used to report cells outside the current frequency band.
LCAUTION!
A maximum of six cells will be reported. Only a maximum of n ”best” cells (according to the
L1M algorithm) will be transmitted to the BSC by the L1M in a Handover_Indication message
(n = 3 before V12 ; n = 6 from V12).
OHER PROCEDURES
The handling of multiband MS did not need specific changes in L1M. Main changes are on MS
side. However, main procedures can be reviewed with the differences that occur in V10.
• PLMN selection: a single band MS only selects a PLMN from its frequency band.
A multiband MS can select PLMNs of both bands.
• Cell selection & reselection: a single band MS only selects or re-selects cells from
its frequency band. A multiband MS can select or re-select cells of both bands.
Priority can be given to one band (see chapter Selection, Reselection Algorithms).
• Handovers: a new attribute is introduced in both adjacentCellReselection and
adjacentCellHandover objects. Its name is standardIndicator Adjc and tells the
type of network where the neighboring cell operates (“gsm” or “dcs” or “gsmdcs” or
“dcsgsm”). A single band MS only performs handovers towards cells from its
frequency band. A multiband MS can perform handovers towards cells of both
bands if classmark 3 is supported on NSS side.
If local mode directed retry is chosen, as it is performed towards a specific neighbour, one
type of single band MS (the one which does not support the frequency band of adjacent cell
umbrella ref) will not use this feature.
For multiband MS, formulas like PBGT or thresholds are the same as single band ones, their
power class is replaced according to the band of the cell they are in (se chapter General
formulas).
Nortel confidential

4.17.2 SI2QUATER & SI13 ON EXTENDED OR NORMAL BCCH
PRINCIPLE
This feature has been designed to allow configuring the sending of System Information 13
(SI13) and System Information 2Quater (SI2Quater) messages either on normal or extended
BCCH.
This configuration is possible on a per BSC basis and done via the BSC Data Config tool.
That feature is avalaible from V15.1 for BSC3000 and BSC12000.
3GPP recommendations gives:
SI2QUATER
It is sent if needed, as determined by the system operator. If sent on BCCH Norm, it shall be
sent when TC = 5 if neither of SI2bis and SI2ter are used, otherwise it shall be sent at least
once within any of 4 consecutive occurrences of TC = 4. If sent on BCCH Ext, it is sent at least
once within any of 4 consecutive occurrences of TC = 5.
SI13
It is only related to the GPRS service. SI13 need only be sent if GPRS support is indicated in
one or more of System Information Type 3 or 4 or 7 or 8 messages. These messages also
indicate if the message is sent on the BCCH Norm or if the message is transmitted on the
BCCH Ext. In the case that the message is sent on the BCCH Norm, it is sent at least once
within any of 4 consecutive occurrences of TC = 4.
Today SI13 and SI2Quater are allocated on Norm BCCH.

CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
BCCH
BCCH
BCCH
BCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
FCCH
FCCH
FCCH
FCCH
FCCH
IDLE
SCH
SCH
SCH
SCH
SCH
The feature allows configuring separately SI2Quater and SI13 per BSC either on Norm BCCH
or Ext BCCH.
CCCH
BCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
BCCH
BCCH
BCCH
BCCH
BCCH
BCCH
BCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
CCCH
FCCH
FCCH
FCCH
FCCH
FCCH
IDLE
SCH
SCH
SCH
SCH
SCH
As a consequence, SI3 message has been updated in order to indicate to the mobile:
• whether or not SI2quater and SI13 is broadcast

• if broadcast is done on Normal or Extended BCCH
PERFORMANCES
The BCCH channel has a repeat period of 8 multi-frames. One multi-frame has 51 frames and
one frame is approximately 4,615ms long. Therefore, the BCCH repeat period is
8*51*4.615ms, or 1,88 seconds. Each period of the BCCH channel is given a number in the
Nortel confidential

range 0 to 7. This number is called TC. The 3GPP specifications define in which BCCH repeat
period (TC value) a specific SYS INFO message can be sent.
SI2Ter, SI13 and SI2quater can be sent when TC=4.
This means that:
• if 1 of SI2Ter, SI13 and SI2Quater messages has to be sent, it will be sent every
1.88 seconds.
• if 2 of SI2Ter, SI13 and SI2Quater messages has to be sent, each will be sent
every 3.76 seconds.
• if all of SI2Ter, SI13 and SI2Quater messages has to be sent, each will be sent
every 5.64 seconds.
Redirection procedure duration is directly linked to the time the MS needs to read system
information messages.
On the contrary, the sending of system information on extended BCCH increase load on
AGCH/PCH channel.
BENEFITS
Customers are facing MS issues:
• Devices being unable to read SI13 messages when these are sent on the
Extended BCCH. The impact of the failure to read this message was that the
device is partially or completely unable to connect to GPRS services.
• Devices seeing valid SI messages containing 3G NCells (SI2Quater) as
“corrupted” when sent on the Normal BCCH; continued reception of these
messages resulted in the device rebooting or failing to set up CS calls.
So if customers don’t wish to recall affected MS the feature allows to modify the allocation of
SI2Quater and SI13 messages
SI2Quater and SI13 on Ext BCCH allow as well speeding up 3G toward 2G cell reselection
(see chapter Mobility 2G - 3G Reselection).
The drawback is a PCH / AGCH capacity lost.
LCAUTION!
When this feature is enabled, e.g. if SI2Quater and/or SI13 on extended BCCH features are
activated, the parameter noOfBlocksForAccessGrant has to be greater than 0.
4.17.3 SUMMARY OF SYSINFO SCHEDULING

For each multi-frame, the BCCH block is used to transmit a BCCH system information. TC
defines the index of the multiframe in which the Sysinfo message is sent by the network. The
broadcast cycle is 8 multiframes therefore the TC index ranges from TC = 0 to TC = 7.
In the absence of option SYSINFO messages, the basic cycle is :
SYSINFO 1, SYSINFO 2, SYSINFO 3, SYSINFO 4, SYSINFO 1, SYSINFO 2, SYSINFO 3,
SYSINFO 4.
Nortel confidential

TC5 may be preempted by the optional SYSINFO 2x that has the highest priority, where 2bis
priority > 2ter priority > 2quater priority. TC4 is shared by remaining optional SYSINFO
messages one after the other in the following order : SYSINFO 2ter, SYSINFO 2quater and
SYSINFO 13.
Optional SYSINFO to
TC=0 TC=1 TC=2 TC=3 TC=4 TC=5 TC=6 TC=7
broadcast
None (Si n°) 1 (SI n°) 2 (SI n°) 3 (SI n°) 4 (SI n°) 1 (SI n°) 2 (SI n°) 3 (SI n°) 4
2bis or
2bis only or 2ter only or
1 2 3 4 1 2ter or 3 4
2quater only
2quater
13 only 1 2 3 4 13 2 3 4
2ter or
2bis & (2ter or 2quater or
1 2 3 4 2quater 2bis 3 4
13)
or 13
2quater
2ter & (2quater or 13) 1 2 3 4 2ter 3 4
or 13
2quater & 13 1 2 3 4 13 2quater 3 4
1 2 3 4 2ter 2bis 3 4
2bis & 2ter & (2quater or
13) 2quater
1 2 3 4 2bis 3 4
or 13
1 2 3 4 2quater 2bis 3 4
2bis & 2quater & 13
1 2 3 4 13 2bis 3 4
1 2 3 4 2quater 2ter 3 4
2ter & 2quater & 13
1 2 3 4 13 2ter 3 4
1 2 3 4 2ter 2bis 3 4
2bis & 2ter & 2quater &
1 2 3 4 2quater 2bis 3 4
13
1 2 3 4 13 2bis 3 4
Nortel confidential

4.18. INTERFERENCE CANCELLATION

Note : to activate interference cancellation feature, it is necessary to have receive diversity
enabled. Interference cancellation is a very important feature in a mobile network, especially
when capacity is a critical issue and aggressive frequency reuse schemes are applied to
maximize it. Experience has shown gains with an adhoc frequency plan. Preliminary studies
had indicated that in a 1X3 reuse frequency pattern network, capacity could be limited by
uplink interferers. In general, even if capacity is not limited by uplink interferers, it is essential
to mitigate their effect for quality improvement. Moreover it has been experienced that even if
capacity is not UL limited, Interference Cancellation ensures improvements on data
performance in UL, vocal quality in UL and measurement reports in UL, which improve
mobility management. This results in a descreasing number of radio drops (study done with
half MS quite UL weak, half MS quite DL weak).
A BTS-based interference cancellation algorithm is of great interest. Nortel has designed a
proprietary signal processing scheme aimed at cancelling the interferers. It works on the Base
Stations equipped with all DRX S8K/S12K and with BTS18000. The effect of the feature
depends on diversity: on a site without diversity, the feature Interference Cancelation will have
no benefit. The algorithm works as well with or without frequency hopping and it can remove
any kind of interferer that has some spatial or temporal coherence (co-channel, adjacent
channel, CDMA signal leaking in the PCS band, TV transmitter, etc..). It can be viewed as a
digital beam-forming technique in which a null of the radiation pattern is pointed towards the
interferer.
8 interfering MS ’s
on the 8 TS ’s of F0
BS#2
MS driving away BS#1

call drop: from serving BS
too high C/I
The algorithm is based on the use of the Maximum Ratio Combining diversity technique and
the midamble in the GSM burst that is used to gain some indication of the channel
characteristics, and hence an estimate of the noise present. This noise is approximately made
up of interference and thermal-noise. The midamble is a known sequence of bits, which
undergoes changes after propagation. The interference estimation is necessarily biaised since
it is estimated on a short period of time (22 Tsymbol compared to the 148 Tsymbol) and the
interference cancellation in the absence of interference will result in decreasing the SNR ratio.
To avoid this problem, a parameter ρ is introduced.
Nortel confidential

Thus, it is better not to try to estimate the noise but to put as ’an a priori information’ that there
is only white noise. However when there are interferers, it is necessary to estimate them and
the algorithm can do it only on the 22 signal samples where the useful signal is known.
The ρ parameter is the interferer cancel algo usage parameter that can be set from the OMC.
The ρ parameter is a compromise parameter that can trade-off the pure noise performances
against the dominant interferer case. The algorithm finds the maximum of the modified signal-
to-noise ratio:
• ρ = 0 implies that we have a constant term at the denominator, the noise energy,
and the processing finds the linear combination that maximizes the signal (under
the constraint that |a|2+|b|2=1), i.e. it performs the maximal ratio combiner (MRC).
• ρ = 1 (100%) means that we remove the constant term i.e. the a priori information
on the noise. When there is no interference an approximate MRC combiner is
performed.
• other ρ values like e.g. .5 (50%) mean that a compromise is made between
performances at high interference and at pure noise situations.
MRC is Nortel equipment’s diversity combining technique which is known to be the linear
combination of signals received on the two antennas, that maximises the S/N ratio when there
is only thermal noise (for example it is 1.5dB better than selection combining). It suffers about
2dB loss when there are strong interferers. Simulations have been carried out to show how
with the use of MRC, the required Carrier-to-Int+Noise ratio (C/(I+N)) to maintain a particular
BER reduces, as the presence of synchronus/asynchronus interferers increases. Although
following the same trend, ICA simulation showed the use of a lower C/(I+N) to maintain the
same BER as opposed to only using MRC.
Before V15.1.1, gain of interferer cancellation was not optimal in case of low Rxlev. Since
V15.1.1 interferer cancellation algorithm has been improved to take into account all range
value for parameter "interferer cancel algo usage" (called rejection factor ρ) for all RxLev
range
Nortel confidential

4.19. EXTENDED CCCH

This V12 feature consists in the implementation of the extended CCCH feature The need of
this feature has been identified in some configuration where only one CCCH is not sufficient,
due to a high rate of paging and immediate assignment.
4.19.1 CUSTOMER/SERVICE PROVIDER BENEFITS

This feature allows increasing the rate of paging and immediate assignment messages related
to a cell and thus:
• Allows managing large location area with up to 16 TRX per cell,

• Gives the ability to manage multi-layers networks
• Allows managing GPRS traffic.
4.19.2 FEATURE FUNCTIONAL DESCRIPTION

Up to V.11, only one CCH could be configured at the OMC-R. From V12 you can allow the
configuration of extended CCCH on TS 2, 4 and 6 of the BCCH TDMA.
The following CCCH configurations are now available :
• CCCH_Conf = 0:
TS 0 = FCCH+SCH+BCCH+CCCH
• CCCH_Conf = 1:
TS 0 = FCCH+SCH+BCCH+CCCH+SDCCH/4+SACCH/4
• CCCH_Conf = 2:
TS 2 = CCCH
• CCCH_Conf = 4:
TS 2 = CCCH
TS 4 = CCCH
• CCCH_Conf = 6:
TS 2 = CCCH
TS 4 = CCCH
TS 6 = CCCH
Note: By increasing the number of CCCH, we decrease the number of TCH, so it leads to
reduction of the capacity. For example, an O8 with 1 BCCH has a capacity of 48,65 Erlangs
(with 2% of blocking rate); with 4 CCCH its capacity drops to 45,88 Erlangs.
To configuration of a CCCH block on a TS the channelType parameter must be set to “cCH’.
See also chapter SDCCH Dimensioning an TDMA Models.
Nortel confidential

4.20. PCM ERROR CORRECTION

This feature, introduced in v12, is no longer supported as of v17. It is automatically
deactivated by the OMC-R v17 :
• enhancedTRAUFrameIndication parameter is automatically set to value “not available”
by the OMC-R v17
• the value 1 for pcmErrorCorrection parameter is automatically forbidden by the OMC-
R v17.
Therefore, the following sections (§4.20.1, §4.20.2, §4.20.3) are applicable only to BSS
releases prior to V17.
4.20.1 FEATURE PRINCIPLE

(applicable only to releases before V17)
This feature had been introduced in V12 to reduce the number of errors due to PCM.
The principle of this feature is quite simple; it is to replace the ETSI TRAU frames and to
define a new frame (ETF) by introduction of a CRC on the uplink and the downlink path in
order to detect and correct erroneous frames due to PCM error rate.
The ETF can be used for the following frames:
• Full rate,
• Enhanced full rate,
• Data up to 14.4 kbit/s
The CRC is designed for three functions:
• Firstly, it synchronizes the ETF (CRC 26),

• Then, it detects errors on the received ETF,
• And it corrects them until 2 pairs of bits.
According to the frame transmission direction (downlink or uplink), the functions of the BTS
and the TCU are different:
• On uplink direction: the BTS(DRX boards) build the frame(ETF) while the TCU
(TCB2 boards) synchronizes, detects, corrects and monitors the frame. If an error
is not corrected, the TCU mutes the frame. At the end of the communication, the
RF_channel_Release_Ack message carries the synthetic information about the
PCM link status.
• On downlink direction: the BTS(DRX boards) synchronizes, detects, corrects and
monitors the frame while the TCU builds the frame. If an error is not corrected, the
BTS sends a filled frame to the MS.
During a BSC HO, if the TCU losses the frame synchronization, the communication is cut until
the synchronization is found back (duration around 1 or 2 frames: it means around 20 or 40
ms). Moreover, if the BSC manages different frame formats (ETSI TRAU 8.620, ETF), the
PCM error correction performance on the voice depends on the transmission direction:
• On uplink direction: no degradation in relation to the current state

Nortel confidential

• On downlink direction: 60 ms of supplementary muting
4.20.2 FEATURE BENEFITS

For users, the benefits of this feature are:
• Improvement of the voice quality,

• Better data transmissions.
4.20.3 FEATURE ACTIVATION

This feature needs to be activated at two levels: the BSC one and the BTS one. At the BSC
level, the parameter enhancedTRAUFrameIndication is set to “available”, only if the
transcoder boards of all the related TCUs are on TCB2 boards type with V12 software. Since
V14.3 the feature is available for TC3000
Moreover, at the BTS level pcmerrorCorrection must be set to “1” (but it can only be set to 1 if
the enhancedTRAUFrameIndication is set to available).
LCAUTION!
Some simulations with FR and different PCM error rate have shown that pcm error correction
feature is efficient on FR whatever the PCM quality. But with EFR, according to the PCM
quality the activation of PCM error correction may lead to a worst voice quality:
• Good PCM: pcm error correction for EFR is useless

• Not too bad PCM: pcm error correction may be useful
• Bad PCM: no pcm error correction activation is better for EFR.
As a result PCM error correction feature is efficient with:
• EFR when PCM quality is not too bad

• FR whatever the PCM quality
For the other codec: PCM error correction feature is not available on data circuit codec.
Furthermore, Nortel has not designed this feature for AMR codec as this feature is useless for
AMR calls, moreover, in case of activation with AMR, the feature gain decrease when AMR
penetration increases.
Nortel confidential

4.21. CELLULAR TELEPHONE TEXT MODEM (TTY)

Deaf, hard of hearing, and speech-impaired persons have been using specific Text Telephone
(referred to as TTY in North America) equipment in the fixed network for many years to
transmit text and speech through ordinary speech traffic channels.
To answer US FCC requirements, NORTEL V12.4 (or V14.3 with BSC/TCU 3000 introduction)
BSS includes now the Cellular text Telephone Modem (CTM) solution for reliable transmission
of a Text Telephone conversation via the speech channel of cellular or PSTN networks.
4.21.1 TTY PRINCIPLE

Data transmission methods exist in the wireless services, but for various reasons, a text
telephone transmission method for the speech path is desired. Two reasons are:
• text telephony is acknowledged as a way to contact the emergency services, and

emergency services in wireless networks are so far only defined for speech calls.
• alternating speech and text in a call is desired, and one simple way to accomplish
that without special service support (like multimedia) is by alternating the use of
the speech channel.
CTM allows reliable transmission of a text telephone conversation alternating with a speech
conversation through the existing speech communication paths in cellular mobile phone
systems. This reliability is achieved by an improved modulation technique, including error
protection, interleaving and synchronization.
The CTM is intended for use in end terminals (on the mobile or fixed side) and within the BSS
network for the adaptation between CTM and existing traditional text telephone standards.
The signal adaptation Baudot CTM is localized in the TCU-TCB2 in a pool TCB2 boards (or in
the TCU 3000 in each TRM board).
NORMAL CASE
“SPEECH/DATA INDICATOR” = “SPEECH + CTM”
If an ASSIGNMENT REQUEST or HANDOVER REQUEST message is received from the

MSC with:
• Circuit Identity Code compatible with TCB2 (or TRM_DSP) capability (FR+CTM)
• “Speech/data indicator” = “Speech + CTM”
• and “permitted speech version identifiers” = EFR & FR,
an ASSIGNMENT COMPLETE or HANDOVER COMPLETE message will be sent to the MSC
with Speech Version (Chosen) = FR (or EFR).
Nortel confidential

“SPEECH/DATA INDICATOR” = “SPEECH”
If an ASSIGNMENT REQUEST or HANDOVER REQUEST message is received from the

MSC with:
• Circuit Identity Code compatible with TCB2 (or TRM_DSP) capability (FR+CTM)
• “Speech/data indicator” = “Speech”
• and “permitted speech version identifiers” = EFR & FR or FR (or EFR & FR)
• and unavailable archipelago EFR and FR resource (SPU)
an ASSIGNMENT COMPLETE or HANDOVER COMPLETE message will be sent to the MSC
with Speech Version (Chosen) = FR (or EFR).
ABNORMAL CASE
On reception by the BSC of an ASSIGNMENT REQUEST or HANDOVER REQUEST

message with:
• Circuit Identity Code incompatible with TCB2 (or TRM_DSP) capability (the circuit
pool implied by the CIC information element is incompatible with the channel type
indicated)
• “Speech/data indicator” = “Speech + CTM”
• and “permitted speech version identifiers” = EFR & FR
• and unavailable archipelago EFR_CTM resource (SPU)
In a first step an ASSIGNMENT FAILURE or HANDOVER FAILURE message will be sent to
the MSC.
In a second step an ASSIGNMENT COMPLETE or HANDOVER COMPLETE message will be
sent to the MSC with Speech Version (Chosen) = EFR (or FR according to the archipelago
resource availability).
4.21.2 TTY IMPACT
TCU-TCB2
The TCU-TCB2 capacity is not impacted by the CTM implementation.

The TCU-TCB2 performances are the following:
Manage up to 8 TCB2 boards and 4 A interface PCM (24 TS available on PCMA 0-1-2 and
only 20 TS available on PCMA 3 fir ss#7, X25 or circuit)
Each TCB2 board is downloaded with either the FR + EFR load and FR + CTM load
Each TCB2 manages 12 communications whatever the associated CODEC type (FR + EFR
and FR + CTM) exept for the #7 TCB2 which manages 8 communications.
Nortel confidential

TCU 3000
The TCU 3000 capacity is affected by the CTM implementation according to the configured
archipelagos EFR_CTM number.
TCU 3000 architecture supports until 10 TRM max: (9+1 for redundancy))
Each TRM manages 3 archipelagos i.e. 36 SPU:
• FR codec: up to 6 communications corresponding to 72 calls per archipelago

• EFR codec: up to 6 communications corresponding to 72 calls per archipelago
• EFR_CTM codec: up to 4 communications corresponding to 48 calls per
archipelago
• AMR: up to 5 communications
Each TRM2 (introduced in V16.0) manages 3 archipelagos:

• FR codec: up to 96 calls per archipelago
• EFR codec: up to 96 calls per archipelago
• EFR_CTM codec: up to 84 calls per archipelago

• AMR: up to 96 calls per archipelago
The TCU 3000 capacity can be formulated on maximum of communications.
If X = number of configured archipelago FR

If Y = number of configured archipelago EFR
If Z = number of configured archipelago EFR_CTM
Capacity = X*72 + Y*72 + Z*48 = 2138
No new parameters or counters are introduced with this feature.
However, new information is available through the “Channel Type” message, and the field
“Speech / data indicator”. We have the new request: “Speech + CTM Text Telephony”.
LCAUTION!
CTM provides a solution that:
• works with EFR and FR codecs (for example AMR)

• allows roaming between networks of different operators
• allows the users to transmit speech and text alternately (“Voici Carry Over VCO /
Hearing Carry Over HCO)
Nortel confidential

4.22. LOCATION SERVICES

The objective of this feature is to allow the GSM network to geographically position Mobile
Stations with BSC12000 (this BSS feature is available from V13.2) and BSC3000.
The position of the MS is obtained using handset-based methods, namely EOTD and Network
Assisted GPS. Additionally, the Cell Id and Timing Advance methods may be used as fallback
methods. The determination of the positioning method is done outside the BSS at Mobile
Location Center level.
4.22.1 PRINCIPLE
The Enhanced Observed Time Difference (EOTD) positioning method combines the relative
time of arrival of the signals from several BTSs reported by the target MS with the signals
received by a fixed measuring point known as the Location Measurement Unit (LMU) whose
location is known. Typically one LMU is needed for every 3 to 4 BTS sites.
Note that there are two possible types of LMU:
• Type A LMU communicates with the BTS over the air, it requires an additional
antenna for this purpose. This is known as the ‘GSM Tx/Rx’ antenna. The
signaling protocol for the LMU to SMLC interface is known as the LMU LCS
Protocol (LLP) and is described in GSM 04.71.
• Type B LMU communicates with the BTS over a dedicated wired interface. The
Type B interface uses the serial communications port on the LMU and will require
a proprietary connection to the BTS (such as the Q1 bus or similar).
The Network Assisted GPS solution uses the GPS information measured by the MS if it
supports this functionality. To ensure efficient service, assistance data needs to be sent by the
network to the MS. Nortel has adopted a NSS-based architecture and will provide a combined
Gateway Mobile Location Center and Serving Mobile Location Center (GMLC/SMLC) into a
single platform, the Mobile Location Server. This server is therefore connected to the MSC.
The BSS acts as a relay between the mobiles and the LMUs on one side and the Mobile
Location Server on the other. Location Measurements Units (LMUs), if required (EOTD
method), are wireless devices (type A) provided by a third party. It should be noted that the
positioning accuracy is dependant on many factors, but mainly the algorithms implemented in
the MS and in the SMLC. Therefore, the BSS is not responsible for the final location accuracy.
Interface Lb is introduced for BSS based solution in V16.0 (see Engineering rules [R37]).
4.22.2 PERFORMANCES
New signaling messages are introduced for this feature management:
• RR Layer: Application Information message

• BSSMAP Layer: Connection Oriented Information message
• New BSSLAP Layer, including 7 messages needed for signaling between SMLC
and BSC.
Note: the class 3 parameter early classmark sending of the bts object class must be set to
“allowed” by the OMC-R user.
Nortel confidential

4.23. SMS-CELL BROADCAST

The objective of this feature is to support new broadcast services as advertising or
information’s with BSC12000 and BSC3000 (this BSS feature is available from V14.2)
The goal is to offer an interface for the SMS-CB that allows to send easily the same message
on every cell of a list of BSCs and so that the system can update all the cells in a quicker time.
BS
OMC
BS
Cell BSC
SMS-CB
Broadcast BS
manager
Center
BS
BSC
BS
4.23.1 PRINCIPLE
In the Nortel network’s structure of Cell Broadcast Service a Cell Broadcast Center is
interfaced with the OMC via a non Q3 interface. The OMC act as the SMS-CB manager and
broadcast SMS over all the BSCs placed under its control.
The new requirements concern:
• the broadcast of the same short messages on all the cells which are managed by
an OMC-R or a BSC list.
• the change rate of these short messages: 13 seconds are required;
• The current implementation about the short message broadcast involves several
limitations and OAM constrains which should be raised:
• CBC/OMC-R interface throughput which must be compliant with the user activity
performance.
• OMC-R/BSC interface throughput which must be compliant with the number of
message (TGE) to be processed by the BSC (from 1 up to 2 TGE/sec for all
transactions).
• Heavy OAM constraint to update the data base CBC when network (re)
configuration occurs.
Nortel confidential

4.23.2 PERFORMANCES
The following table depicts the number of messages:
CBC / OMC / I/F OMC / BSC / I/F

Messages Old New Old New
Create short message 1 1
Start broadcast (first time) X*Y 1 Y 1
Set short message (continued) 1 1
Stop broadcast (continued) X*Y 0 Y 0
Start broadcast (continued) X*Y 1 Y 1
Stop broadcast (last) X*Y 1 Y 1
Periodic MMI commands
(1+2*X*Y)*n 2*n
number
2*y*n
Periodic TGEs number 320*n max or n
1200*n max
X: BSC number [1:30]

Y: Cell number / BSC12000 [1:160]
X*Y: Cell number / OMC [1:2400]
n: Number of updates of messages
With this solution, SMS-CB has been dimensioned for following capacities:
• 5 messages maximum per cell (broadcast in loop)

• message format: 1 page / 93 characters
• broadcast periodicity (30 sec, 1 mn, 2mn, 4 mn, 8 mn or 16 mn), 2 sec (1
message / cell) corresponding to the CBCH maximum capacity
The whole users activity can be:
• on an average: 1 MMI command every 10 sec. for the whole set of users. Or, 1
MMI unitary command every 160 sec. per users, with a maximum of 16 users.
• on a maximum: 1 MMI unitary command every 2 sec. for the whole set users,
during 2 hours maximum. Or 1 MMI unitary command every 32 sec. per users,
during 2 hours maximum, with a maximum of 16 users.
The CBC can be associated to n users among 16 ones: then the number of MMI commands
on the CBC / OMC interface is n every 32 sec.
Every short message modifications involves 2 MMI unitary commands (set short message &
start broadcast) the short message change rate is 32*2n.
Note:
When the OMC-R receives one command for all the cells of one or several BSC, it checks for
each cell if there is a CBCH channel and if the limit of 5 short messages is not exceeded. That
defines a “compliant” cell. It then checks if a threshold S (per BSC) corresponding to a max of
tolerated non compliant cells is reached.
Nortel confidential

If the limit of 5 messages is exceeded for one or several cells and if the number of non
compliant cells exceeds the threshold S for one or several BSC, the OMC-R rejects the
command and does not sent the TGEs. The TGEs will not be sent for these BSC(s), but will be
sent for the others. The response (FAILED) to the CBC will report per BSC the non compliant
bts identities (up to the first S bts identities per BSC).
If the number of non compliant cells does not exceed the threshold S for any BSC, the OMC-R
accepts the command and sends the TGEs. The response (SUCCEEDED) to the CBC will
report per BSC the non compliant bts identities (up to S bts identities per BSC).
CBCH CHANNEL RECOMMENDATION
On the air interface the CBCH channel takes 4 TS bursts (4*0.577 ms) on one 51 multiframe.
The CBCH channel takes the place of one SDCCH channel.
The SDCCH channel can be mapped on two different ways on TDMA: with BCCH combined
(SDCCH/4) or on one reserved TS for SDCCH (SDCCH/8). Thus it is the same thing for
CBCH.
The CBCH is not using the radio resources of the CCCH. It is using the radio resources of one
SDCCH channel. The activation and the use of the SMS-CB will not impact the load on the
CCCH.
The activation of the CBCH will take 1 SDCCH channel and so will increase the SD
congestion. After the activation of the CBCH one needs to follow the SDCCH congestion and
maybe if necessary on some cells to increase the number of SDCCH channels.
Once defined on the cell the CBCH channel can only be used to send SMS-CB. Thus the
quantity of SMS-CB sent will not impact the load of the radio channels other than the CBCH.
Throughput calculation:
The CBCH (idem to SDCCH) offers 184 bits for a block message (or 4TS).
The corresponding throughput offered by the CBCH carried on 51 multitrame:
Throughput = 184 * 4 / 4.615 ms / 51 = 781 b/s
The limitations described in the FN are:
• SMS of 88 bytes
• 5 messages per cell
• 2 seconds between each message.
This means a throughput of: 88 * 8 * 5 / 2= 1760 b/s, which is more than 2 times the max
throughput of the CBCH channel.
Nortel confidential

4.24. BSC/TCU 3000 INTRODUCTION

With the BSC3000 introduction (this BSS equipment is available from V14.3), a lot of new
features will be implemented:
• Automatic handover adaptation (see HO adaptation feature TF 1216 in chapter

Automatic handover adaptation)
• Protection againts Intracell HO Ping-pong (see HO Ping-pong feature TF 1217 in
chapter Protection against intracell HO Ping-pong)
• TTY Support on TCU 3000 (see TTY feature in chapter CELLULAR TELEPHONE
TEXT MODEM (TTY))
• BSC 3000 overload (see chapterBSC3000 Overload Management)
• AMR HR/FR ( see AMR feature SV885/SV713 in chapterAMR - Adaptative Multi
Rate FR/HR)
Nortel confidential

4.25. AMR - ADAPTATIVE MULTI RATE FR/HR

Nortel BSS has evolved to introduce sophisticated traffic management features dealing with
call quality management and capacity improvements. This feature manages AMR services,
which allow high gains and good trade-off between these 2 objectives.
4.25.1 BASICS AND SPECIFIC TERMINOLOGY

In GSM, speech is transmitted on a radio channel (using a speech coder also called source
coder) which has a fixed raw bit rate. The coder delivers speech frames every 20 ms. From
that standpoint, speech quality tends to improve when the source coder bit rate is increased.
If we use a high coder rate, the speech quality will be very good in excellent radio conditions,
as long as speech frames can be decoded properly. But in bad radio conditions, a high
proportion of speech frames will not be decoded, in which case some interpolation will be
done by the decoder, and speech quality actually drops. If we use a low coder rate, speech
quality will be medium or low, but will resist very well to radio channel impairments, due to the
high level of redundancy. Consequently, present techniques like FR or EFR are the result of
compromises between the source coder rate, and the channel coding, within the boundaries of
the raw bit rate of a GSM channel.
AMR techniques are adaptive, and multirate. It means that it allows adapting the compromise
between source coder rate and channel coding/redundancy to actual radio conditions. AMR
may operate in full rate channels, or half rate channels. This is called the “channel type”
(TCH/FR or TCH/HR). Uplink and downlink always apply the same channel type.
Basis of AMR is that within the channel (FR or HR), there is a set of voice coders, along with
associated channel coding, among which the best combination can be selected to maximize
speech quality according to conditions met on the radio link. This is “codec mode adaptation”.
For codec mode adaptation the receiving side performs link quality measurements of the
incoming link. The measurements are processed yielding a Quality Indicator.
For uplink adaptation, the Quality Indicator, as measured in the BTS is compared to certain
thresholds and generates, also considering possible constraints from network control, a Codec
Mode Command (CMC) indicating the codec mode to be used on the uplink. The Codec Mode
Command is then transmitted inband to the mobile side where the incoming speech signal is
encoded in the corresponding codec mode. For downlink adaptation, the DL Mode Request
Generator within the mobile compares the DL Quality indicator with certain thresholds and
generates a Codec Mode Request (CMR) indicating the preferred codec mode for the
downlink.
Both for uplink and downlink, the presently applied codec mode is transmitted inband as
Codec Mode Indication (CMI) together with the coded speech data. At the decoder, the Codec
Mode Indication is decoded and applied for decoding of the received speech data.
Nortel confidential

The following figure provides the AMR data flow from a "CMR, CMC and CMI" point of view
and explains the CMI, CMC and CMR period.
MS BTS
CMI
CMI
20ms
40ms CMR 20ms
CMC 40ms
CMI
CMI
CMR
CMC
AMR is introduced to choose in real time the repartition between rate of the source vocoder
and channel protection:
Half Rate
Source coding
Global throughput = 11,4 kBits/s
Channel coding
Full Rate
Global throughput = 22,8 kBits/s
• when the transmission is good, a high rate vocoder is chosen and the number of
bits dedicated to the channel protection is low,
• in case of degraded radio conditions, the vocoder rate is decreased, in order to
provide a better channel protection and allow a better voice quality.
Nortel confidential

4.25.2 AMR MECHANISMS

AMR introduces algorithms based on requested codec mode, which are fixed using an
approximation of C/I and a set of thresholds and hysteresis. Depending on the channel used,
the set of codec mode is different:
• For AMR FR, 5 codec modes can be requested: 12k2, 10k2, 6k7, 5k9, 4k75 (12k2
is a virtual mode)
• For AMR HR, 4 codec modes can be requested: 7k4, 6k7, 5k9, 4k75 (7k4 is a
virtual mode)
CODEC MODE ADAPTATION
The purpose of AMR codec mode adaptation is to provide the "best" compromise between
data rate of codec mode and channel protection, according to the link quality. This adaptation
is done for uplink and downlink and there is no interdependence between the 2 links, but both
sets of codec have to be identical.
Each 40ms, according to the requested codec mode and the applied codec mode, the BTS:
• increases by one step the rate of the codec mode, if the requested codec mode
(CMR) is greater than the applied codec mode,
• decreases by one step the rate of the codec mode, if the requested codec mode
(CMR) is lower than the applied codec mode,
• keeps the same codec mode, if the requested codec mode (CMR) is equal to the
applied codec mode.
DOWNLINK REQUESTED CODEC MODE
A comparison of the estimated uplink C/I is then made with the network parameters to see to
which codec mode the C/I corresponds.
C/I
Codec Mode 4
Thresold_3 + Hysteresis_3 = Threshold_Max_Up(3)
Thresold_3 = Threshold_Max_Dn(4)
Codec Mode 3
Codec Mode 2
Codec Mode 1
Nortel confidential

UPLINK REQUESTED CODEC MODE
The BTS computes for each burst the SNR criteria, which provides a good approximation of
C/I. In order to have a smooth variation of these criteria, the BTS applies the following filter:
(SNR)(k) = ß * (SNR)(k) + (1 - ß) * (SMR)(k - 1)
Where ß is equal to:
• 0.05 in case of FR no frequency hopping channel and slow moving mobile,

• 0.1 in others cases of FR channels,
• 0.1 in case of HR no frequency hopping channel and slow moving mobile,
• 0.2 in others cases of HR channels.
In case of DTX, the BTS cannot evaluate the SNR criteria, thus during the DTX period, the last
value of (SNR)k is taken into account and at the end of the DX period, a time exponential filter
is used in order to increase the weight of the new measures and keep the same period of
filtering. This filtered SNR is compared to a set of thresholds and allows determining the
requested codec mode. If no uplink correct frames is received, the BTS has no way to
evaluate the quality of the downlink path, the BTS decreases the applied downlink codec
mode of one step each 40ms. This procedure is repeated until an uplink frame is correctly
received or the 4k75 codec mode is selected for the downlink path.
LCAUTION! Before V16.0 there was a limitation on UL SNR in order to have homogeneous
behavior for AMR calls with every kind of DRX. From now, UL SNR measurements are
truncated at 24dB (48 in 0.5dB) at SDO level, whatever hardware is used. The 48 value given
from the BTS corresponds to 24dB and more. This new implementation improves the power
control reactivity. That impacts on the AMR metric. Therefore C/I metric values for both AMR
and EFR calls cannot be compared.
PARAMETERS
For each mobile, the following set of parameters has to be defined:
• for each link direction (upLink or DownLink), one threshlod per subsequent codec
in the defined Active Codec Set (ACS),
• one hysteresis (the same value is used for each codec mode, but one for FR and
another one for HR channel).
But these parameters are linked to a set of factors, some of them being determined by the
BTS (frequency hopping, MS speed), others being network dependent (environment profile…).
The following table is implemented in the BSS:
Nortel confidential

uplink downlink
slow MS - fast MS - ideal FH SFH 900
< 4 FH
no FH no FH (>= 4 freq) TU3
5k9 to 4k75 81 90 99 108 117
6k7 to 5k9 82 91 100 109 118
FR thresholds
10k2 to 6k7 83 92 101 110 119
12k2 to 10k2 84 93 102 111 120
FR hysteresis 85 94 103 112 121
5k9 to 4k75 86 95 104 113 122
HR thresholds 6k7 to 5k9 87 96 105 114 123
7k4 to 6k7 88 97 106 115 124
HR hysteresis 89 98 107 116 125
According to the network configuration, and for each combination of codec mode and link
direction, the operator selects the appropriate thresholds by using the parameters
amrUlFrAdaptationSet, amrUlHrAdaptationSet, amrDlFrAdaptationSet, amrDlHrAdaptationSet
(or the single parameter amrAdaptationSet before V15.1.1). These parameters allow to
choose between 3 sets of pre-defined tables (optimistic, pessimistic and typical settings) plus
one set of tables which is user-defined The BSS using the TS configuration and the MS speed
applies the appropriate column for the uplink path.
As specifed in the GERAN recommendations (05.09) the mobile shall use the downlink
thresholds provided by the BSS defined for a reference environement: Typical Urban 3 km/h
with ideal frequency hopping at 900 MHz. The MS shall then apply a normalization factor to
normalize with respect to different channel types. The normalization factor is mobile
dependant.
See also chapter AMR Field Feedback for further informations on the codec adaptation table.
RATSCCH MANAGEMENT
This new channel is used in order to change the set of codec modes (see "L1m" section), and
has the following main characteristics:
• frame stealing (1 speech frame for a FR channel, 2 speech frames for a HR

channel),
• priority of RATSCCH frames is lower than FACCH priority,
• a RATSCCH message has to be acknowledged in the next 3 frames by the MS,
• the content of RATSCCH message is applicable 12 frames after this message,
• in case of failure (ACK_ERR message), a RATSCCH procedure is repeated twice.
If the procedure completely fails, the MS and the BTS use the previous set of
codec modes.
When amrReserved1 is set to enabled, this procedure is used by the L1m to modify the set of
codec modes, for a FR channel and in case of handover failure with return on the old FR
channel, in order to avoid inconsistency between the BTS and the MS (the BTS sends the
AMR_CONFIG_REQ message).
Nortel confidential

For TCH/FR, the default transmission phase shall be such that Codec Mode Indications are
sent aligned with TDMA frame 0 in the uplink and with TDMA frame 4 in the downlink. For
TCH/HR, the default transmission phase shall be such that Mode Indications are sent aligned
with TDMA frame 0 or 1 depending on the subchannel in the uplink and with TDMA frame 4 or
5 depending on the subchannel, in the downlink.
If at call setup or after a handover, the Codec Mode Indication is not aligned, an Ater
procedure is engaged in order to change the default phase in downlink direction.
PRINCIPLES
The RATSCCH as the FACCH shares the dedicated channel of the TCH. Contrarily to the
FACCH the RATSCCH is time synchronous. The RATSCCH allows modification of the AMR
configuration (CMI/CMC phasing, Adaptation Thresholds, ACS). From V14, the introduction of
the AMR, Nortel Networks BTS will support the RATSCCH (All Nortel’s BTS from the S4000
DCU4 to the most recent BTS will support the AMR speech service.)
The RATSCCH message is composed of a preamble and of a message part. Several
messages have been defined. These messages correspond to different procedures. At the
moment the following have been defined:
• Changing of the Active Codec Set

• Changing of the thresholds and hysteresis
PRE-HANDOVER
In case of intracell or intercell handover, the adaptation mechanism has to be frozen to the
ICM. For this result, the BTS has to intercept:
• the Assignment Command in case of intracell,

• the Handover Command in case of intercell handover,
and to perform up to 2 codec mode adaptations, in order to activate the initial codec mode
(5k9 kbits in all cases) and to stop the adaptative mechanism.
This induces:
• an increase of around 150ms on the handover duration from the BSS point of view,
• a delay of around 150ms on the handover starting time from a MS point of view,
but no impact for the end-user in term of voice quality (i.e. same speech gap).
In case of handover failure when the MS returns on the old channel, the adaptation
mechanism is restarted by the BTS at reception of the Start Measurement message
4.25.3 TRAFFIC MANAGEMENT MECHANISMS
CHANNEL ALLOCATION
TCH channel allocation is triggered by the reception of an Assignment request or a Handover

request message from the MSC, or in case of an intraBSC handover. The BSC should
Nortel confidential

determine whether AMR is to be used, and select between FR or HR. This mechanism is
based on proprietary algorithms, which provide to the operator a full control of the allocation.
These decisions are made based on several criteria:
• OAM flags which indicate if the BSC, the TCU, and the cell support AMR, and
strategy selected
• MS capability, which is reported by the MSC in Assignment request or Handover
request messages
• radio context, for instance as evaluated during the SDCCH phase.
The BSC also has to control the BSS version: an AMR channel is activated only if all nodes
managing the call are at least in V14.
FLAG MANAGEMENT
We use the two following parameters:
• coderPoolConfiguration (AMR, fullrate, enhancedfullrate) attribute. This attribute

indicates enumerated speech coding algorithms supported by the TCU.
• speechMode (halfRateAMR, fullRateAMR, fullrate, enhancedfullrate) attribute. This
attribute indicates speech coding algorithms supported by the cell.
CHANNEL TYPE MANAGEMENT
In order to select the channel type associated to the connection, the BSC uses the channel
rate and type and permitted speech version information, in order to know the MS capability in
term of:
• FR/HR management
• Speech codec
But the chosen channel type is fixed according to radio criteria and some O&M parameters,
and the BSS has the possibility to modify the channel type during the connection, in all cases.
So at reception of the Assignment Request or Handover Request, the following mediation is
done on the Channel Type octet 4:
IF Target TCH = FR TCH
THEN the BSC always allocates a FR TCH
IF Target TCH = HR TCH

AND IF AMR HR is allowed in the cell
THEN the BSC allocates a HR TCH
ELSE the BSC allocates a FR TCH.
Nortel confidential

CELL LOAD STATE
The cell load state is used in order to choose between a FR or a HR channel, and is defined
using following parameters:
• hrCellLoadStart
• hrCellLoadEnd
• filteredTrafficCoefficient
Previously to V15.1.1, if hrCellLoadStart = 0, then FR radio channel is always allocated to the

MS, and if hrCellLoadStart > 0, then HR radio channel is allocated to the MS, according to its
radio conditions. For one call, the cell load state is evaluated at the first TCH allocation in the
cell, thus in case of intracell handover, the cell load state is not reevaluated.
In V15.1.1, the feature AMR based on traffic is introduced. The goal is to enhance the HR
allocation in order to take into account the cell load: AMR HR channels are allocated only
during loaded period. The cell load state is evaluated every 10s (see Filtered Erlang traffic and
cell load state)
ASSIGNMENT
In case of assignment, according to:
• the speechMode parameter value of the target cell (signalingPoint +

TranscoderBoard + bts parameters)
• the cell load of the target cell
• the radio condition of the MS
the BSC selects the target Channel Type.
To know the radio conditions, the BSC sends to the BTS a Connection State Request and in
the Connection State Ack the BTS gives the following bit map:
• “small zone” bit indicates if the small zone of the serving is eligible in case of multi-
zone cell
• “HR large” bit indicates if the MS has sufficient radio conditions to manage a HR
channel in the large zone of a mullti-zone cell or in normal cell
• “HR small” bit indicates if the MS has sufficient radio conditions to manage a HR
channel in the small zone of a mullti-zone cell or in normal cell
Nortel confidential

Using these bits and the following priority order between channel type and zone:
Priority Preferred zone

++ HR small zone
+ HR large zone
- FR small zone
-- FR large zone
the BSC selects the channel type and the zone for the MS.
RADIO ALLOCATOR
The radio allocator is improved in order to manage AMR calls. Due to intrinsic quality of FR
AMR and HR AMR, 2 new parameters are created on the transceiver object, in order to give
an AMR priority to each TDMA:
• frAMRprioriry
• hrAMRPriority
where
• Priority 0 is given to a high priority TDMA

• Priority 1 is given to a low priority TDMA
• Priority 2 disables this service on the TDMA
Thus according these new parameters, the BSC chooses the radio TS using the following
order:
• Interference level,
• TDMA priority,
• TDMA number (from the smallest to the biggest: 0 to n),
• TS number (from the biggest to the smallest: TS7 to TS0).
In case of HR request, the BSC applies the following rules:
• Always fill the holes in term of tree half (between 2 holes, the BSC uses priority
rules previously defined
• If there is no hole, then the BSC allocates the highest priority TS using the rules
previously defined
• This radio allocator is not improved in order to manage AMR calls, thus if an AMR
request occurs and this radio allocator is selected, then:
• an other vocoder (EFR or FR) is selected using priority order given in the channel
type element
• the allocated channel type is always a full rate TCH.
Nortel confidential

4.25.4 AMR L1M

Up to V14, L1m algorithms are common for all types of dedicated channel, but due to
performances of AMR channels:
• A FR AMR channel, specially with low codec mode, is more resistant than the
normal FR channel
• A HR AMR channel, is more sensitive to interference than the normal FR channel
Some new mechanisms dedicated for AMR channels based on "requested codec mode" in
uplink and downlink paths, which are the best representation of the quality in this case, are
designed.
For this reason, RxQual criterion is not used in AMR L1m algorithm, dealing with AMR
channel.
12K2 AND 7K4 CODEC MODE FALSE ACTIVATION
As seen before following codec mode sets are implemented in the BTS:
AMR FR AMR HR
10k2
6k7 6k7
5k9 5k9
4k75 4k75
In AMR L1m mechanisms, the main criterion for L1m is the requested codec mode provided
by the MS or the BTS. With this set of codec modes, it is impossible to detect if the quality is
good or very good (in both cases the MS and the BTS provide the 10k2 or 6k7 codec mode
according to the channel type).
In order to solve this problem, for an half rate channel, a fourth codec mode (7k4) is added to
the list allowing to distinguished between good and very good radio conditions. Thus the half
rate codec mode set becomes:
AMR HR
7k4
6k7
5k9
4k75
For a full rate channel:
• if the radio conditions are good for uplink and downlink, then the 12k2 kbits codec
mode is configured and the 4k75 discarded allowing to distinguish between good
and very good radio conditions (using RATSCCH channel).
• if the radio conditions are bad for uplink or downlink, then the 12k2 kbits codec
mode is removed and the 4k75 is set back (using RATSCCH channel).
Nortel confidential

Thus the codec mode set becomes:
AMR FR AMR FR
12k2
10k2 10k2
6k7 6k7
5k9 5k9
4k75
The following algorithm details the way of changing the codec mode set, for both paths:
1) initial state: the active codec mode set is {12k2, 10k2, 6k7, 5k9}
2) during the last 480ms period, at least one 4k75 code mode or 3 * 5k9 codec mode
are requested for uplink or downlink paths, then the active codec mode set is change
to {10k2, 6k7, 5k9, 4k75}
3) if the active code mode set is {10k2, 6k7, 5k9, 4k75} and during the last 2*480ms
period, no 5k9 nor 4k75 code mode is requested for uplink and downlink paths, then
the active codec mode set is change to {12k2, 10k2, 6k7, 5k9}.
POWER CONTROL
The Power Control feature reduces the average interferences level on the Network and saves
mobile batteries.
Power control algorithms are redesigned for AMR calls, in order to take into account the
requested codec mode. With the following parameters (powerControl object), the operator
defines the target codec mode of each channel type:
Uplink target codec
• hrPowerControlTargetMode
• frPowerControlTargetMode
Downlink target codec
• hrPowerControlTargetModeDl
• frPowerControlTargetModeDl
For the uplink path, SNR and CMR criteria are available, but the SNR is more accurate than
the CMR. For the downlink path only the CMR is available. Thus the AMR power control does
not apply same principles for both paths. This new power control mechanism is also controlled
by the 2 classical power control parameters:
• bsPowerControl for the downlink path,

• uplinkPowerControl for the uplink path.
Nortel confidential

UPLINK POWER CONTROL
For the uplink path, the criterion is the SNR, averaged on 2 measurement periods. As this
mechanism shall guarantee a voice quality, the target SNR is the upper threshold of the
adaptation mechanism:
Note: for the 12k2 (or 7k4) value, the BTS takes into account the 10k2 (or 6k7) value plus the
FR (or HR) hysteresis.
At each measurement period, the BTS calculates the new MS power using the following
formula:
IF (Filtered_SNR – Target _SNR) > 0

THEN MS_txpwr(N) = MS_txpwr(N-1) – 0.7*( Filtered_SNR – Target _SNR)
ELSE IF
THEN MS_txpwr(N) = MS_txpwr(N-1) + 1.4*( Target _SNR -Filtered_SNR)
Note: From V 16, the reactivity of UL power control is improved as UL SNR measurements
limited to 24 dB (48 in 0.5 dB) are taken out.
DOWNLINK POWER CONTROL
The power control principle is:
• To decrease the power level of one step if the last requested codec mode of the
480 ms is greater than the target codec mode,
• To increase the power level of one step if the last requested codec mode of the
480 ms is lower than the target codec mode
Note: in AMR like in EFR, the parameter lRxLevDLP indicates the threshold below which
power control is inhibited.
HANDOVER MECHANISMS
The following table describes which handover mechanisms are impacted by the AMR
introduction
Handover type modified

uplink and downlink quality yes
uplink and downlink strength no
distance no
power budget no
uplink and downlink intra-cell handover yes
capture no
inter-zone yes
directed retry no
Traffic no
Nortel confidential

PRINCIPLE
These 4 handovers are based on "(n,p) voting" principle, using the requested codec mode.
The (n,p) voting principle considers the last p requested codec modes, it compares them to
two parameters: a codec mode threshold defined for the procedure and the specific n value
pRequestedCodec
Handover
decision
used for the procedure.
If p is set to 2 SACCH periods (2*12), n is set to 10, the target codec mode is the green one,
and then a handover is triggered in the following example:
This principle applies in uplink and downlink direction independently.
This mechanism is managed by the L1m and triggered at the end of each period of
measurement, thus p has to be a multiple of the number of requested codec mode in one
measurement period (i.e. 480 / 40 = 12).
The following parameters are defined in the handOverControl object:
• pRequestedCodec
• nHRRequestedCodec
• nFRRequestedCodec
If the n parameter is set to a value greater than the p parameter, then all associated features
are deactivated. If the target codec mode is the smallest, then the associated feature is
deactivated.
INTERBSC HANDOVER
In case of interBSC handover, according to:
• the speechMode parameter value of the target cell (signallingPoint +

transcoderBoard + bts parameters)
• the cell load of the target cell
• the Current Channel element
• the Cause element
the BSC selects the target Channel Type:
• if one out of these last 2 optional A interface elements is not set in the Handover
Request message, the chosen channel type is FR
• if these 2 elements are present and the half rate is allowed in the target cell, then
the following table is applied:
Nortel confidential

Current Channel type 1

HR FR
Cause
uplink quality FR FR
uplink strength FR FR
downlink quality FR FR
downlink strength FR FR
Distance FR FR
O&M intervention FR FR
Better cell HR FR
Directed retry FR FR
Traffic HR FR
In all other case, a FR channel is allocated.
INTRABSC INTERCELL HANDOVER
In case of intraBSC handover, following transitions are defined in order to determine the target
channel type:
Initial Channel type

HR AMR FR AMR
Handover cause
AMR quality FR AMR FR AMR
DISTANCE FR AMR FR AMR
PBGT HR AMR FR AMR
TRAFFIC HR AMR FR AMR
Forced HO FR AMR FR AMR
Capture FR AMR FR AMR
Directed retry FR AMR FR AMR
The speechMode parameter value of the target cell and the cell load are also checked in order
to verify that the half rate is allowed in the cell.
With AMR calls, RxLev and RxQual criteria for uplink and downlink are not used and replaced
by an algorithm based on "(n,p) voting" principle, using the requested codec mode.
Following parameters are introduced in order to specify the target requested codec mode for
FR and HR AMR channel:
• amrHRIntercellCodecMThresh
• amrFRIntercellCodecMThresh
In order to manage the eligible cell list, a new handover margin is introduced in the
adjacentCellHandOver object: hoMarginAMR this parameter is used in order to calculate the
Exp2 (this expression is used to evaluate the PBGT criteria for each cell and to classify eligible
cells, please refer to chapter EXP2).
Nortel confidential

IF N(Uplink) ≥ nXXRequestedCodec
OR N(Downlink) ≥ nXXRequestedCodec
THEN the Handover is triggered
With N the number of requested codec mode for the uplink or the downlink strictly lower than
AMRXXIntercellCodecModeThreshold (XX stands for HR or FR)
INTRABSC INTRACELL HANDOVER
In order to select the channel type, the BSC applies the following table:
Handover cause original channel type target channel type

normal intra-cell FR FR
Small to large zone FR or HR FR
large to small zone FR FR or HR according to radio conditions*
large to small zone HR HR**
tiering FH to no FH FR FR
tiering FH to no FH HR FR
tiering no FH to FH FR FR
tiering no FH to FH HR HR
AMR FR to HR FR HR
AMR HR to FR HR FR
*The radio conditions are given by the BTS to the BSC using the Current Cell Add information
element in the Handover Indication message.
**If radio conditions are not sufficient in the small zone to manage this HR MS, the MS
remains in the large one, due to the HR priority.
Intracell handover principle is to give to the mobile a better resource in term of interference, if
its C/I is low, with a high C value.
This principle is only applicable to FR AMR mobiles, due to interaction with HR >FR handover:
in these radio conditions, it is really more efficient to allocate a FR radio TS to a HR AMR
mobile, than to perform a handover from an HR TS to a HR TS. This intracell handover is
triggered only if the intracell parameter of handovercontrol object is set to enable.
The following parameter is introduced on the handoverControl object, in order to specify the
target requested codec mode for FR AMR channel:
• amrFRIntracellCodecMThresh
The minimum level to perform an AMR intracell handover is defined by following parameters
on the handoverControl object:
• amriRxLevDLH
• amriRxLevULH
Nortel confidential

So the intracell handover uses the following criteria:
IF N(Uplink) ≥ nFRRequestedCodec AND RxLevUL > amriRxLevULH

OR N(Downlink) ≥ nFRRequestedCodec AND RxLevDL > amriRxLevDLH
THEN the handover is triggered.
With N the number of requested codec mode for the uplink or the downlink strictly lower than
amrFRIntracellCodecMThresh for the uplink or the downlink
INTRACELL HANDOVER AMR FR AMR HR
This handover is used to change the channel type of a mobile from FR to HR if the quality is
sufficient.
Due to the high C/I requirement for HR channel, the requested codec mode of "(n,p) voting"
mechanism is fixed by default to 12k2 kbits/s and a dedicated "n" parameter allows to set the
trade-off between quality and capacity:
• nCapacityFRRequestedCodec
The handover is triggered if the "(n,p) voting" principle is fulfilled in both directions.
Note:
• this mechanism is not linked to the intracell parameter of handovercontrol object.

• this mechanism is deactivated if nCapacityFRRequestedCodec is greater than
pRequestedCodec.
So the handover AMR FR to HR uses the following criteria:
IF N(Uplink) ≥ nCapacityFRRequestedCodec
AND N(Downlink) ≥ nCapacityFRRequestedCodec
THEN the capacity handover is triggered.
With N the number of requested codec mode for 12k2 in the p requested codec mode for the
uplink and the downlink path,
INTRACELL HANDOVER AMR HR AMR FR
This handover is used to change the channel type of a mobile from HR to FR if the quality is
not sufficient.
The handover is triggered if the "(n,p) voting" principle is fulfilled in one direction.
The following parameter is introduced on the handoverControl object, in order to specify the
target requested codec mode for this handover:
• amrHRtoFRIntracellCodecMThresh
Note: this mechanism is not linked to the intracell parameter of handovercontrol object, and it
is deactivated if amrHRtoFRIntracellCodecMThresh is set to 4k75.
Nortel confidential

DIRECT HALF RATE TCH ALLOCATION
In order to avoid some unnecessary handover from FR to HR channel, it is mandatory to

evaluate the radio conditions at following stages:
• primo allocation: SDCCH to TCH in a normal cell,

• primo allocation: SDCCH to large zone TCH in a multi-zones cell,
• primo allocation: SDCCH to small zone TCH in a multi-zones cell,
• inter-zone handover from large to small in a multi-zones cell.
and allocate immediately a HR channel if radio conditions are sufficient.
The principle of this mechanism is to compare the RxLev uplink and downlink to dedicated
thresholds, in order to estimate the MS HR capability.
Following parameters are introduced on the handoverControl object, in order to specified
RxLev thresholds for this handover:
• amrDirectAllocIntRxLevDL
• amrDirectAllocIntRxLevUL
• amrDirectAllocRxLevDL
• amrDirectAllocRxLevUL
So the direct half rate TCH allocation uses the following criteria:
In a normal cell or in the large zone:
IF RxLevDL > amrDirectAllocRxLevDL and RXLevUL > amrDirectAllocRxLevUL

THEN the direct HR TCH allocation is eligible
In a small zone:
IF RxLevDL > amrDirectIntAllocRxLevDL and RXLevUL > amrDirectIntAllocRxLevUL

THEN the direct HR TCH allocation is eligible
In v17.0, the Direct TCH Allocation mechanism has been improved to take into account the
case where only a short, not fully reliable, measurement average is available. In that case, all
algorithm criteria are tightened by adding the hoMarginBeg parameter to the appropriate
thresholds (amrDirectAllocIntRxLevDL, amrDirectAllocIntRxLevUL, amrDirectAllocRxLevDL,
amrDirectAllocRxLevUL).
Nortel confidential

SUMMARY
The following table presents a summary of all new L1m decisions:
HO decision channel type p value for (n,p) voting n value for (n,p) voting target codec
quality intercell UL / DL
TCH FR pRequestedCodec nFRRequestedCodec amrFRIntercellCodecMThresh
TCH HR pRequestedCodec nHRRequestedCodec amrHRIntercellCodecMThresh
quality intracell UL / DL
FR Æ FR TCH FR pRequestedCodec nFRRequestedCodec amrFRIntracellCodecMThresh
HR Æ FR TCH HR pRequestedCodec nHRRequestedCodec amrHRtoFRIntracellCodecMThresh
capacity intracell
FR Æ HR TCH FR pRequestedCodec nCapacityFRRequestedCodec fixed to FR codec 12k2
Direct HR TCH allocation channel type averaging window thresholds

outer zone SDCCH 1 … rxLevHreqt* amrDirectAllocRxLevDL
rxLevHreqave amrDirectAllocRxLevUL
inner zone SDCCH 1 … rxLevHreqt* amrDirectAllocIntRxLevDL
TCH FR rxLevHreqave amrDirectAllocIntRxLevUL
TCH HR
* in this case, all available measures, up to rxLevHreqt are taken into account.0
Nortel confidential

Following figures illustrate all possible transitions for an AMR call, in a multi-zones cell
environment:
INTRACELL HANDOVERS ON QUALITY
Tiering BCCH to FH FR FR
Tiering BCCH to FH HR
Intracell FR or HR FR
Interzone FR or HR FR
Intracell FR or HR FR
INTRACELL HANDOVERS ON CAPACITY
Tiering BCCH to FH FR FR
Tiering BCCH to FH HR HR
Interzone FR FR or HR
Interzone HR HR Capacity FR HR
Capacity FR HR
FR or HR
HR
FR or HR Direct TCH
allocation
Nortel confidential

INTERCELL HANDOVERS:
FR FR Target Cell FR FR
HR
HR
PBGT Alarm
Traffic Capture
HR
HR
HR HR
FR FR Source Cell
FR FR
FR
FR
Directed
Retry
4.25.5 LEGACY L1M

Type of power control and quality handover can be chosen via the parameter amrReserved2.
While legacy L1m bases its decision on RxQual/RxLev measurements (please refer to chapter
Measurement Processing), AMR L1m base trigger its algorithms on C/I estimations (please
refer to chapter AMR L1m).
The choice between legacy or AMR power control or handover management is up to the
operator’s strategy.
4.25.6 PDTCH PREEMPTION BY AMR FR OR HR CALLS

The GSM/GPRS TS sharing feature allows the BSC to preempt some GPRS radio resources,
in case of lack of circuit radio resources.
Nortel confidential

AMR FR REQUEST
In case of AMR FR request, there is no specific mechanism. The request is granted in the
same conditions as for a non-AMR circuit-switched call.
AMR HR REQUEST
Before v17.0, in case of an AMR HR request, if a preemption has to be done, then the
allocated channel following preemption is an AMR FR channel.
From v17.0, if the “AMR-HR on preempted pDTCH” feature is activated (v17 parameter
gprsPreemptionForHr = enabled), then the BSC is able to preempt a shared GPRS timeslot to
serve an AMR-HR request. The algorithm is as follows :
When the BSC receives an assignement or a handover request for a half-rate speech channel,
the BSC searches for an available HR channel in the following order of preference :
• free half-rate channel of a TCH physical channel whose other half-rate channel is
already allocated to a voice AMR HR call (no dialog between BSC and PCU is
needed)
• free TCH physical channel (no dialog between BSC and PCU is needed)
• free half-rate channel of an already preempted PDTCH whose other half-rate channel
is already allocated to a voice AMR HR call (no dialog between BSC and PCU is
needed)
• half-rate channel of a newly preempted PDTCH (BSC and PCU must negotiate)
This feature for AMR-HR preemption may have an impact on the AMR based on Traffic
threshold settings, see 4.23.7
Nortel confidential

4.25.7 ENGINEERING RULES
QUEUING/PRIORITY 0
• queuing is not possible for an HR only request,

• for a FR or HR request in queue, only a FR TCH can be allocated.
The number of priority 0 TS takes into account only radio TS which are completely free (i.e. a
free half rate TS is count for 0).
TCH SIGNALLING
A signaling half rate TCH can not be activated at reception of Channel Required.
If a “signaling” Assignment Request (channel type: “speech/ data indicator” field), for a mobile
using a half rate TCH, an assignment procedure is triggered to a SDCCH channel and the
associated CIC is released (this case occurs at the end of a speech call, if a SMS procedure is
started and not finished).
If a “signaling” Assignment Request (channel type: “speech/ data indicator” field), for a mobile
using a full rate TCH, a channel mode modify procedure is triggered to a signaling TCH
channel and the associated CIC is released (this case occurs at the end of a speech call, if a
SMS procedure is started and not finished).
If an AMR HR or FR Assignment Request is received for a mobile using a signaling FR TCH,
the BSC modifies the current signaling FR TCH to a AMR FR TCH and later, if radio
conditions are sufficient, then a handover from AMR FR to AMR HR will be triggered by the
BTS (see section “Principles/ L1m/Handover mechanisms/ handover HR->FR”).
AUTOMATIC CELL TIERING
In V12.4, according to PWCI distribution and hopping TCH percentage, the BTS is able to
automatically set the used threshold in order to trigger tiering handover.
In V14, this mechanism has to be enhanced as show below, in order to take into account AMR
HR calls:
• in V12.4: P% is evaluated as:
Number of non hopping TCH - nbLargeReuseDataChannel

P%=
Total number of TCH in the cell - nbLargeReuseDataChannel
• in V14: P% is evaluated as:
(Number of non hopping TCH – nbLargeReuseDataChannel) * (1 + Non_FH_HR%)

P%=
(Total number of TCH in the cell – nbLargeReuseDataChannel) * (1 + HR%)
• FH_HR% is the percent of HR calls managed by the hopping pattern in the cell,
• HR% is the percent of HR calls managed in the cell.
Nortel confidential

These 2 percentages are calculated by the BTS.
GENERAL PROTECTION AGAINST HO PING PONG
Due to AMR L1m introduction, a new cause value is added in hoPingPongCombination:

AMRquality. This value is used in case of AMR handover triggered for alarm purpose.
In case of interBSC handover, in order to distinguish between RxQual handover and AMR
quality handover, the BSC uses following rules:
• If the handover cause = RxQual and the speech version <> AMR then the
Handover cause = RxQual.
• If the handover cause = RxQual and the speech version = AMR then the Handover
cause = AMR quality.
HANDOVER EFR/FR - AMR
For handover from an AMR cell to a non-AMR cell it is performed via the A interface using
external handover mechanism, in order to allow the fallback to EFR or FR channel (according
to Assignment Request order).
For handover from a non-AMR cell to an AMR cell, in order to decrease the MSC load, the call
is not upgraded to AMR and a normal EFR handover occurs.
Note that interBSC procedure may increase the number of dropped call, so it is recommended
to minimize that trnasition period.
TDMA CONFIGURATION
Due to the half rate channel introduction and to limit the number of contexts in the BSC, the
number of SDCCH per TDMA is limited as following:
normal cell:
• Maximum number of SDCCH per TDMA: 2,

• only one SDCCH TS managed by odd TS per TDMA,
• only one SDCCH TS managed by even TS per TDMA.
extended cell:
• Maximum number of SDCCH per TDMA: 1.
LCAUTION!
It is highly recommended to respect that TDMA configuration in case of activation of AMR.
AMR HR-FR INTERWORKING
In case of deactivation of AMR FR service, following points have to be highlighted:
• direct HR TCH allocation is available, even if AMR FR is not configured in the cell,
• handovers from FR radio TS to AMR HR are triggered on “requested codec mode”
criterion, but this criterion is available only for AMR calls, thus this kind of
Nortel confidential

handover is not possible from a FR or EFR channel and decreases the AMR HR
efficiency,
• handovers from (or to) an AMR HR channel to (or from) EFR channel are
performed using an external handover procedure and thus induce:
• more load on the MSC,
• more perturbations on the voice quality, thus it is mandatory to activate AMR FR
service, in case of AMR HR activation.
4.25.8 AMR BASED ON TRAFFIC
PRINCIPLE
Previously to V15.1.1, the choice between an half rate and full rate channel was based only on
radio criteria, thus in order to guarantee the voice quality at any time the operator had to tune
the network with conservative values.
With the introduction of AMR based on traffic, AMR HR channels are allocated only during
loaded period, so the operator could choose more aggressive radio thresholds and then get
more radio capacity for the same number of TRX.
In order to minimize impacts of this strategy, this feature tunes the half rate penetration
according to the cell load:
HR capacity
HR
FR capacity
FR
This feature is based on a smooth mechanism, which allows anticipating the cell load and
switching the allocation into HR mode, when an Erlang threshold is reached.
The following picture illustrates the interworking between these 2 kinds of mechanisms over
24 hours:
Nortel confidential

Blocking managed
Traffic thanks to directed retry
and HO traffic
Max HR
capacity
Number of
allocated TCH
Half rate area

Max FR
capacity
FR->HR threshold
Blocking managed
thanks to directed retry
and HO traffic
Full rate area Avg Erlang
t
24 hours
Two typical periods are observed:
• Low traffic: all calls are allocated in full rate mode and the blocking is managed
thanks to directed retry and traffic handovers features.
• High traffic: call are allocated in half or full rate modes, according to radio
conditions of each calls and the ultimate blocking is managed thanks to directed
retry and traffic handovers features.
FILTERED ERLANG TRAFFIC AND CELL LOAD STATE
busy_TCH_TS
Filtered_TCH_ration = a* + (1 - a)* Filtered_TCH_ration-1
available_TCH_TS
where:
• Filtered_TCH_ration is the busy TCH ratio managed by the cell at period n.

• α is the filter coefficient (filteredTrafficCoefficient parameter).
• busy_TCH_TS is the number of TCH TS allocated to a FR or a HR TCH call (in
case of multi-zones cell, traffic of both zones is taken into account).
• Available_TCH_TS is the number of TCH TS configured and available in the cell
(in case of multi-zones cell, traffic of both zones is taken into account).
The initial value of Filtered_TCH_ration is set to 0.
This filtered busy TCH ratio is then compared to the 2 thresholds HRCellLoadStart and
HRCellLoadEnd in order to determine the cell load state:
• If (Filtered_TCH_ration < HRCellLoadEnd),

Nortel confidential

then Cell_Load_Staten = min(max (0, Cell_Load_Staten-1 -1); nb of in service DRX)
• Else if (Filtered_TCH_ration >= HRCellLoadStart),
then Cell_Load_Staten = min(nb of in service DRX, Cell Load_Staten-1 +1).
• Else Cell_Load_Staten = min(Cell_Load_Staten-1; nb of in service DRX)

The initial value of this Cell_Load_Staten is set to 0.
This mechanism is activated whatever values of all associated parameters (AMR FR and / or
HR activated or not, HRCellLoadStart, HRCellLoadEnd …), in order to allow the monitoring at
the OMC-R level of this mechanism.
PDTCH TS (preempted or not) are not taken into account in this mechanism in order to
decrease PDTCH preemption.
In case of TDMA / TRX defense mechanism, the BSC has to take into account the new
number of DRX in service at the next period, in order to evaluate the cell load state.
TRAFFIC MANAGEMENT PRINCIPLE
The 3 algorithms used to allocate a HR channel to a mobile are tuned in order to be adapted
to the cell load.
DIRECT HALF-RATE ALLOCATION
Direct half rate allocation: the range between the OMC-R RxLev threshold and -48dBm (the
deactivation value) is divided in N sub-range, thus new subthresholds are dynamically created
by the BSC. At each cell load state modification, appropriate sub-thresholds is used by the
BTS:
Nortel confidential

Cell load state

RxLev
Smax distribution
S4
S3
S2
S1
S0
-110 amrDirectAlloc RxLev4 RxLev3 RxLev2 RxLev1 -48 dBm

(Int)RxLevxx
The principle is for the BSC to adapt the following OMC-R parameters according to the cell
load state:
• AMRDirectAllocRxLevUL
• AMRDirectAllocRxLevDL
• AMRDirectAllocIntRxLevUL
• AMRDirectAllocIntRxLevDL
The threshold associated to the cell load state i is evaluated according to the following
formula:
⎡ Nb_DRX-i ⎤
Threshold_i = int ⎢ AMRDirectAllocyyRxlevxx + (-48 - AMRDirectAllocyyRxlevxx)*
⎣ Nb_DRX ⎥⎦
Where:
• xx is used for UL or DL,

• yy is used for int or nothing.
Every 10 seconds if needed, new thresholds are sent to all DRX.
The initial value of this mechanism is the threshold_0 (-48dBm),

At the end of a defense TDMA procedure, current thresholds are sent to the BTS.
This mechanism is activated only if:
• at least one OMC-R threshold is not equal to -48.

• The AMR HR service is activated in the cell (speechMode parameters of the BSC
& cell object)
In case of modification of one AMRDirectAllocyyRxlevxx parameter, the new value is taken
into account at the next period.
Nortel confidential

FR TO HR HANDOVER
FR to HR handover: this handover is activated DRX per DRX according to the cell load state:
• S0: no DRX is configured in order to allow the FR to HR handover

• Si: i DRX are configured in order to allow the FR to HR handover and N-i-1 are
configured in order to deactivate this handover.
The BSC chooses the i DRX in the cell according to the AMR FR radio allocator priority.
Highest priority TDMA are switched in FR->HR mode in first. Every 10 seconds if needed, new
parameters are sent to all DRX.
The initial is no DRX activated, especially at the end of a defense TDMA procedure.
In case of modification of any AMR FR to HR handover parameter, the new value is taken into
account at the next period.
All Handover Indication messages sent by the BTS, have to be managed by the BSC
whatever the cell load state.
This mechanism is activated only if:
• nCapacityFRRequestedCodec not greater than pRequestedCodec.

• The AMR HR service is activated in the cell (speechMode parameters of the BSC
& cell object)
HR TO HR INTER-CELL HANDOVER
HR to HR inter-cell handover: this half rate allocation is full deactivated in case of S0 cell load
state and fully activated in all others cases.
This mechanism is activated only if the AMR HR service is activated in the cell (speechMode
parameters of the BSC & cell object)
IMPACT ON ABOT OF “HR CHANNEL ALLOCATION ON PREEMPTED

PDTCH (V17)”
The cell load that is used to set thresholds for the AMR based on traffic feature is defined by
the number of busy TCH versus the number of free TCH. The formula does not take into
account the pDTCH channels which, thanks to pDTCH preemption for HR channels feature,
could be preempted for HR.
When PDTCH preemption for HR channels (V17) is activated, operators may want to increase
the number of pDTCH defined in the cell, at the expense of TCH, because this increase in
pDTCH will come at no voice capacity cost (HR may preempt these channels) while increasing
the maximum throughput available for data traffic. As the number of TCH changes, so will the
cell load used in AboT, and therefore Direct HR allocation may occur for a lower cell load than
is strictly necessary.
Nortel confidential

4.25.9 REPEATED DOWNLINK FACCH
The purpose of the feature ‘Repeated downlink FACCH’ is to secure the handover procedure
in poor radio condition (with AMR FR) by retransmitting the FACCH frames in downlink after
about 40ms, i.e. without waiting for the mobile acknowledgement
Thanks to this feature end-users will experience a better call retainability in badly covered or
interfered area. Acceptable voice quality will be maintained thanks the robust AMR/FR codec
usage. On the other hand voice quality being slightly degraded during handover procedures
due to repeated frame stealing; the preventive retransmission scheme should be triggered
only in bad radio conditions.
PRINCIPLE OF THE FEATURE
The Repeated Downlink FACCH functionality is applicable when sending LAPDm command
frames on the TCH/F channel. The BSS uses the Repeated Downlink FACCH functionality
when AMR FR codec used is less than a defined threshold (settable at OMC-R) and when the
first transmission fails (T200 expires).
A repeated FACCH block is sent in such a way that, if the first burst of the downlink FACCH
block containing the first instance of a LAPDm frame is sent in TDMA frame M, the first burst
of the downlink FACCH block containing the repeated instance of the LAPDm frame is sent in
TDMA frame M+ 8 or M+ 9 (the latter corresponding to the case where the two FACCH blocks
are separated by either a SACCH frame or an idle frame).
The MS shall, when receiving a downlink FACCH block, always attempt to decode it without
combining with any previously received FACCH block
If the current FACCH block is successfully decoded and an identical FACCH block was
previously received (successfully decoded and spaced in time from the current FACCH block
as specified here-above):
• The MS (Release 6 and subsequent) shall not send the LAPDm frame of the current
FACCH block to the LAPDm entity.
• Pre-release 6 MS may send a REJ message upon receiving repeated frame, but this
does not prevent this MS to get the benefit from the repetition mechanism.
If the current FACCH block is successfully decoded and there was no such previously
received identical FACCH block, the LAPDm frame of the current FACCH block is sent to the
LAPDm entity.
FEATURE ACTIVATION
A dedicated cell class 2 parameter, enableRepeatedFacchFr, is used to enable the feature by

chosing a codec threshold or to disable the support of Repeated FACCH in each cell.
Nortel confidential

MECHANISM OF THE FEATURE
When the Repeated FACCH feature has been enabled on the cell, each time the AMNU entity
needs to re-transmit an I-frame on FACCH due to T200 expiry, it sends this frame again to the
SPU entity (with a flag related to the retransmission). The SPU entity sends first the I-frame on
FACCH in TDMA frame M as it does when the feature is disabled. And if the selected CODEC
is lower than the threshold set to activate the feature, it stores the LAPDm frame to be
repeated in TDMA frame M+ 8 or M+ 9
When repeating FACCH messages, T200 is started when transmitting the subsequent FACCH
(~ 40 ms later) to cope with the case where an MS fails to decode the downlink FACCH block
used to send the first instance of a repeated LAPDm frame.
Nortel confidential

PERFORMANCE
When repeating a frame, the applicable T200 duration is increased by about 40 ms (~20%).
This induces a longer time for drop call detection with T200 mechanism because N200 cannot
be modified.
In addition, a new MS shall soft combine the frames to optimize the decoding probability
whereas legacy mobile will simply see an increased probability of decoding Lapdm frame. The
expected benefit for mobiles using soft combining is about 4 dB gain and about 2 dB gain for
legacy mobiles.
This graph presents the expected benefits on softcombining MS and lecacy MS.
Legacy MS gain
Soft combining gain
Nortel confidential

4.25.10 TX POWER OFFSET FOR SIGNALING CHANNELS

In order to increase the signaling channels (FACCH and SACCH) robustness in downlink, BTS
may use a power offset (above the Tx power applicable for speech) to transmit the signaling
bursts.
The benefit in term of C/I is depending on the power offset for the signaling robustness and
allows the operator increasing the fractional load and thus the spectrum efficiency. Voice
quality can be still acceptable thanks to the use of robust AMR codec.
PRINCIPLE OF THE FEATURE
The Tx Power Offset for Signaling Channels is applicable to:

• The first transmission of HO COMMAND and ASSIGNMENT COMMAND for all AMR
calls in order to maximize the likelihood of decoding these messages from the first
instance,
• Every re-transmission of I-frame on FACCH for all AMR calls (HR and FR) in order to
maximise the likelihood of decoding these messages.
• Every RR and REJect frame on FACCH corresponding to an uplink retransmission for
all AMR calls (HR and FR) in order to improve the two-ways robustness.
• Every UA (respectively DM) frame on FACCH corresponding to an uplink re-
transmission of SABM (respectively DISC) frames for all AMR calls (HR and FR) in
order to improve the two-ways robustness.
• The transmission of all SACCH frames for AMR FR 4.75 kbps, 5.9 kbps and 6.7 kbps
calls (tunable with an OMC-R parameter) in order to avoid radio link time-out (that
leads to drop calls.
On theses messages a power offset (tunable from the OMC-R) is applied up to the nominal Tx
power.
Note: The power offset applies (up to the nominal Tx power of the BTS) on BTS18000, ecell,
as well as S8000 and S12000 fitted with e-DRX or DRX-ND3. For other BTS hardware, the
feature does not apply. In addition this feature is not applicable on BCCH TRX (PA is always
transmitting with Pmax and transmitting power should not fluctuate).
Nortel confidential

FEATURE ACTIVATION
This feature is activated at cell level; dedicated class 2 parameters are used to enable/disable
the feature in each cell. The parameters related to tune the feature are the following:
• facchPowerOffset
• sacchPowerOffset
• sacchPowerOffsetSelection
Note: If the BTS hardware (DRX or RM) does not support the signalling offset mode (up to
Pnominal), the facchPowerOffset and sacchPowerOffset provisioning is not considered and
the DRX or RM behaves as it behaves when facchPowerOffset and sacchPowerOffset are set
to 0 dB.
FEATURE DESCRIPTION
The Tx Power Offset for Signaling Channels is applicable to different type of message;
hereafter the process for each specific handling:
SPECIFIC HANDLING OF HO COMMAND AND ASSIGNMENT COMMAND
For all AMR calls, these messages are transmitted with the maximum power (considering
facchPowerOffset) from the first instance in order to maximize the likelihood of decoding these
messages with no LAPDm repetition at all, and therefore avoid as far as possible the drop
calls during (inter-cell or AMR triggered) handover procedure.
Since these messages can be segmented, the power offset applies on all segments: the level
3 entity flags all frames of the HO COMMAND and ASSIGNMENT COMMAND messages then
SPU entity checks this flag in each I-frame to apply (or not) the power offset
(facchPowerOffset) on the transmitted frame.
When applying the power offset,
First case:
IF PWR + facchPowerOffset ≤ Pnominal

THEN
SPU modifies the dynamic power control in accordance with PWR + facchPowerOffset
Nortel confidential

Second case:
IF PWR + facchPowerOffset > Pnominal

THEN
SPU set the dynamic power control to: 0 BTS transmits the frame at Pnominal
Note: PWR is the BTS transmit power computed by L1M power control algorithm and
applicable for speech and Pnominal is the BTS Tx power set by the static power control
SPECIFIC HANDLING OF RE-TRANSMITTED I-FACCH FRAMES, RR AND

REJECT CORRESPONDING TO RE-TRANSMITTED UPLINK FACCH
FRAMES AND UA CORRESPONDING TO RE-TRANSMITTED SABM OR
DM
For all AMR calls, every re-transmission of FACCH frames as well as:
• UA (with F bit set to 1) corresponding to a retransmitted SABM or Disconnect Mode,
• and RR and REJect frames on FACCH (with F bit set to 1) corresponding to an uplink
retransmission of a FACCH frame
are transmitted with the maximum power in order to maximise the likelihood of decoding
these messages and therefore avoid as far as possible the drop calls due to N200 overrun.
The BTS LAPDm entity flags each FACCH frame mentioned here-above then SPU entity
checks this flag and apply (or not) the power offset (facchPowerOffset) on the re-transmitted
frame.
When applying the power offset:
SPU (as describes for HO command and assignment command) either modifies the dynamic
power control in accordance with PWR + facchPowerOffset or set this power control to 0
leading the BTS to transmit the frame at Pnominal.
SPECIFIC HANDLING OF SACCH FRAMES
For AMR calls, depending on sacchPowerOffsetSelection provisioning, the transmission of

SACCH frames for AMR FR 4.75 kbps, 5.9 kbps and 6.7 kbps calls are transmitted with the
maximum power (considering sacchPowerOffset) in order to avoid radio link time-out (that
leads to drop calls) and the drop calls due to N200 overrun (for re-transmission).
For SACCH transmission, SPU entity, according to the last selected AMR CODEC and
sacchPowerOffsetSelection provisioning, applies (or not) the power offset (sacchPowerOffset)
on the transmitted bursts.
Nortel confidential

When applying the power offset:

First case:
IF PWR + sacchPowerOffset ≤ Pnominal

THEN
SPU modifies the dynamic power control in accordance with PWR +
sacchPowerOffset
Second case:
IF PWR + sacchPowerOffset > Pnominal

THEN
SPU set the dynamic power control to: 0 BTS transmits the frame at Pnominal
Note: Correction of RxLev (to remove the impact of the power offset on Tx power control
mechanism) can be approximated by SPU entity and conveyed to the L1m. In another hand,
correction of CMR is not possible since BTS does not have the SNR info from MS. The impact
on the choice of AMR CODEC cannot be by-passed see [R36]
Nortel confidential

ENHANCEMENT OF AMR POWER CONTROL MECHANISM
Since this feature improves the downlink robustness, new parameters are introduced to define
dedicated target for uplink and downlink AMR CODEC.
The existing parameters (hrPowerControlTargetMode and frPowerControlTargetMode) still
apply on uplink and two new parameters are introduced for downlink targets:
• hrPowerControlTargetModeDl: downlink AMR codec target to define the downlink
power control threshold for HR AMR calls,
• frPowerControlTargetModeDl: downlink AMR codec target to define the downlink

power control threshold for FR AMR calls,
With setting a lower codec as a Downlink Power control target:

• A more protected AMR speech codec is used in downlink,
• Overall BS attenuation is higher and the overall interference level is decreased

accordingly.
So, in poor radio condition, the transmission power for signaling burst may stay identical
thanks to the Power offset while interference level has decreased.
Since the low target codec for Downlink Power control cannot be reached if the RxLev Power
control threshold limits the BS attenuation and if the Tx Power Offset for Signaling Channels
feature is enabled, lRxLevDLP for AMR communication is set to:
LRxLevDLP - min (facchPowerOffset, sacchPowerOffset).
Nortel confidential

4.26. WPS - WIRELESS PRIORITY SERVICE

The current United States industry focus in support of National Security and Emergency
Preparedness telecommunications services is to specify the requirements for Wireless Priority
Services. The initial deployment of WPS is intended to allow qualified and authorized NS/EP
users to obtain priority access to radio traffic channels during situation when Commercial
Mobile Radio Service (CMRS) network congestion is blocking call attempts.
WPS is intended to facilitate emergency response and recovery operations in response to
natural and man-made disasters and events, such as floods, earthquakes, hurricanes, and
terrorist attacks. WPS is also intended to support both national and international emergency
communications.
4.26.1 PRINCIPLE
If a Service user invokes WPS (Wireless Priority Service) and no radio traffic channel is
available in the cell, the WPS request shall be queued according to the WPS priority, the call
initiation time and the state of the queue for the cell.
This feature is an improvement of the queuing services available to WPS users.
The WPS queuing principle is the following:
• The eight (8) current queues are kept unchanged

• Five (5) new queues are added an dedicated to WPS request
For public queue management and related parameters, refer to chapter Queuing.
4.26.2 WPS – QUEUING MANAGEMENT

The new queuing management of WPS requests is activated when queuing is driven by the
MSC (bscQueuingOption parameter is set to “allowed”) and WPS management is activated
(wPSManagement parameter is set to “enabled”)
LCAUTION!
The bscQueuingOption is a class 1 parameter, which means that parameter can be set only
when the parent bsc object is locked.
It is important to underline that the internal queues associated with WPS requests and the
internal queues associated with public requests are treated in completely separate ways.
CHARACTERISTIC OF THE WPS QUEUE
Each WPS queue is defined with:
• Its associated priority Pi

• Its queue size Ni, the maximum number of WPS call requests (of priority Pi or
higher) which can be queued simultaneously
• Its own T11 timer value, which represents the maximum time a WPS call request of
a given priority Pi can remain in queue
Nortel confidential

The priority Pi is received from the MSC in the assignement request message.
The size Ni of a given WPS queue is set according to the allocWaitThreshold parameter. In
order to be in accordance with the WPS industry requirement and configuration, each queue
size threshold Ni (with 8< i <12) should be equal (N8=N9=N10=N11=N12) and equals the
maximum number of WPS requests allowed in the WPS queues.
The timer T11 for a given queue can be defined with the allocPriorityTimers parameter. It is
understood that the request will immediately be denied with a cause “no radio resource
available” if this timer is set to “0”.
PROCEDURE TO QUEUE SERVICE REQUEST USER WPS
FIRST CASE: MS IS PUT IN QUEUE
As no radio channel is available, and as the queue size threshold Ni of the queue
corresponding to the WPS priority Pi is not reached, the WPS call request is put in queue i. A
queuing indication message is sent to the MSC.
SECOND CASE: MS IS DENIED (QUEUE FULL)
As no radio channel is available, and as the queue size threshold Ni of the queue
corresponding to the WPS priority Pi is reached, the WPS call request is denied. An
assignement failure message with cause “no radio resource available “is returned to the MSC.
THIRD CASE: MS IS PUT IN QUEUE TAKING THE PLACE OF AN OTHER

MS
As no radio resource is available, if the queue size threshold Ni corresponding to the WPS
priority Pi is not reached, but if adding the call request to queue i would cause the threshold Nj
of another internal WPS queue j to be violated, and if the WPS request priority (Pi) is higher
than at least one WPS request (Pk) already in queue in the cell, the BSS takes the following
actions:
• the BSS shall remove the WPS request with the lowest priority (Pk) and the most
recent initiation time from the queue. It sends an assignment failure for this
removed WPS request with the cause “no radio resource available”.
• the BSC shall place the newly arrived WPS request in the queue i according to the
initiation time and the priority level.
A queuing indication for the WPS call request of priority Pi and an assignement failure for the
WPS call request of priority Pk are sent to to the MSC.
Nortel confidential

MANAGEMENT OF SERVICE REQUEST USER WPS PUT IN QUEUE
RESOURCE AVAILABLE
If a radio traffic channel becomes available when there are WPS requests in queue, the
process of ressource allocation decribed in the WPS – Public access bandwith protection
(see chapter WPS – Public access bandwith protection below) has to be followed.
T11 EXPIRY
If the WPS request is in queue i for a radio traffic channel and the maximum time allowed for
that queue expires, the WPS request is removed from the queue and the call is cleared. A
clear request with the cause “no radio resource available” is then sent to the MSC.
RADIO CONTACT WITH THE MS IS LOST
If the WPS request is in queue for a radio traffic channel but radio contact with the mobile is
lost (detected by the BTS which informs the BSC), the WPS request is removed from the
queue and the call cleared. A clear request with the cause “Radio Interface Failure” is sent to
the MSC.
MS DISCONNECTS THE CALL
If the MS decides to disconnect the call while the WPS request is queued, the BSC receives a
clear command message from the MSC and processes the release of the call including the
request removing from the WPS queue.
FEATURE ACTIVATION
If the bscQueuingOption parameter is set to “not allowed” then queuing is not performed, i.e.
no request goes into any of the queues 0 to 12, whatever the wPSManagement value is. In all
the following cases, the bscQueuingOption flag is considered as “allowed (MSC driven)”.
One has to well understand the two levels of queuing in “MSC Driven” queuing mode:
• At the MSC level the call request is described by two fields in the assignement
request message: “queuing allowed” set to allowed / not allowed, and “priority
level” (14 are defined)
• At the BSC level the queuing management of the call requests is set to allowed, so
the BSC takes into account the 2 fields described above
WPS queuing is so done according both to the “queuing allowed” field value set in the
assignment request message sent by the MSC (if this field value is set to “queuing not
allowed”, then there is no queuing) and the WPS priority (1 to 5).
In all the following cases, this field value is considered as “queuing allowed” for all WPS and
public call requests.
Nortel confidential

WPSMANAGEMENT FLAG IS ENABLED
The WPS request is queued according to the mapping (GSM 08.08 priority / internal priority)
done by the customer at the OMC-R.
Internal priorities correspond to the queues 0 to 7 for public requests, and queues 8 to 12 for
WPS requests.
When the wPSManagement flag is enabled, a recommended mapping of the allocPriorityTable
has to be respected.
When the wPSManagement flag is turned on, it also enables the PURQ AC algorithm feature.
(see chapter WPS – Public access bandwith protection below)
WPSMANAGEMENT FLAG IS DISABLED
It is recommended that the customer sets the mapping (GSM 08.08 priority / internal priority)
at the OMC-R, so that only internal priority 0-7 are used when the wPSManagement flag is
disabled. In this case, if a WPS request is received by the BSC, the request will be managed
like a public call since it will be queued in the public queues.
If no mapping is specified by the customer, the default mapping is done to the internal queue
0.
4.26.3 WPS – ACCESS CLASS BARRING WITH CLASS PERIODIC

ROTATION
In normal conditions, the number of WPS Users should be sufficiently small that there is little
likelihood of them having a significant impact on public use. But in case of exceptional events,
the number of initial access is dramatically increased and can induce a full blocking of the
system.
In V9, a feature called "access class barring" was designed in order to avoid this kind of
problem, thanks to a dynamic barring of a significant part of users. An enhancement of this
feature has been designed, in order to allow users to access periodically to the network,
without huge network congestion.
To synthesize, one can say that this feature allows users to access the network periodically
during network congestion by modifying the number of barred access classes in function of the
congestion state of the cell, and by periodically changing which access classes are barred.
There are no specific access class parameters that can be tuned in order to optimize WPS
use.
For further details about this change of access class baring, see chapter Barring of access
class.
Nortel confidential

4.26.4 WPS – PUBLIC ACCESS BANDWITH PROTECTION

The public access bandwidth protection is required in case of cell congestion with WPS users
in the cell. Assuming that the number of WPS users is less important than public users, and
taking into account that WPS users are priority users, this feature ensures that a radio network
bandwidth is available to public users during cell congestion (lack of radio resources).
PRINCIPLE
The idea of the algorithm is to allocate a specified portion of the traffic channels (as they
become free) with preference to public calls, and to allocate a second portion of the traffic
channels (as they become free) with preference to WPS calls.
The BSC radio resource allocator processes the algorithm which favors WPS calls 1 out of
wPSQueueStepRotation times and then process the algorithm which favors public calls P out
of wPSQueueStepRotation times (P = wPSQueueStepRotation – 1).
With this choice, 1 out of wPSQueueStepRotation of the call capacity can be allocated for
WPS users, wPSQueueStepRotation being 1,2, …,10. (recommended value is 4 and hence
25% can be allocated with preference to WPS requests)
PURQ-AC ALGORITHM WITH SUPERCOUNT
PURQ-AC stands for Public Use Reservation for Queuing - All Calls
This algorithm is only activated if If the wPSManagement flag (BSC level) authorizes the WPS
requests management
When the algorithm is turned on (i.e at the startup of a BSC or after a lock/unlock of the cell),
the priority is given to a WPS call request (1 out of wPSQueueStepRotation times), the
algorithm proceeds to some checks about the state of the WPS queues (left side on the
schema below), then the priority is given to public call requests (P out of
wPSQueueStepRotation times) and the algorithm proceeds also to some checks about the
state of the WPS queues (right side of the schema below).
The aim of the supercount is to allow “10 call running deficit” over allocation, and enhanced
small cell performances. It smoothes out short term variations, and decreases delay. The
Supercount tigger value of 10 is a fixed value. Supercount is initialised to 0 and is reset to 0
when a lock/unlock action is done on the cell for instance.
FEATURE ACTIVATION
If the wPSManagement flag (BSC level) is disabled but queuing indications in the assignement
request message still give the priority to WPS call requests, in case of cell congestion, the
WPS users may use all the cell bandwidth (due to their priority) and public users may not have
an access to the network. However that case could only occur if WPS queues are mapped on
internal queues 0-7 instead of the queues dedicated for WPS, because only internal queues 0-
7 are evaluated to serve a queued request when wPSManagementFlaf is turned off. The new
algorithm has a cell based internal management that does not impact any other cells in term of
traffic management.
Nortel confidential

This feature is linked with the queuing management (public and WPS requests) and hence
parameters related to the queue management have to bet set in order to take advantage of
the benefits provided by the PURQ AC algorithm.
Nortel confidential

4.27. SATELLITE ABIS INTERFACE

From V15.1 the use of Satellite Abis links will be possible to allow the connection between
BSC and BTS.
BTS
BSC
Abis
Agprs
Ater Abis
BTS
Abis
In some network areas, there is no earth terrestrial transmission infrastructure between the
BSC and the BTS. This feature solves this problem thanks to a satellite link between these 2
nodes.
To get detailed information about the implementation of this feature, please refer to document
[R31].
4.27.1 PRINCIPLE
The principle of this feature is to allow the implementation of satellite links, instead of
terrestrial links on the Abis interface.
The main issue is to take the propagation delay between BSC to BTS which changes of some
ms to about 240 ms (2*36000 km/300.000 km/s):
• The Abis link has to be modified, in order to take into account this supplementary
delay
• The channel Request / Immediate Assignment has to be improved in order to allow
an efficient channel allocation.
Details on how these changes are done are fully detailled in the Functional Note.
Nortel confidential


To activate this feature on a given BSS, some appropriate parameters will have to be
specified. These parameters will be provided through the “BSC data config” functionality. They
are presented in document [R31] and correspond:
• to the LAPD T200 timer value and anticipation window size to be used for Abis
LAPD Data Links
• to the type of Abis configuration concerned (terrestrial or satellite) at a BTS level
Thus a dedicated build will be needed to activate this feature with the corresponding
parameters.
At the BTS site, installation has to be done with software release compatible with satellite
links. Else it will not be possible to switch in service these equipments.
The introduction of this feature will also imply specific engineering rules mainly due to very big
transmission delays induced by satellite links usage and due to specific implementation
choices. The current document will not focus on engineering rules related to this feature as
they are described in detail in the Satellite Abis Interface - Engineering Guideline (refer to
document [R32]).
LCAUTION!
The applicable BSS Engineering rules presented on document [R7] may be overwriten by the
specific rules applicable to the case where Abis satellite links are used.
4.27.3 FEATURE INTERWORKING
INTERWORKING WITH NON SATELLITE EQUIPMENTS
The system behaviour is not guaranteed if:
• a satellite BTS is equipped with a DRX, which is not a eDRX,

• a satellite BTS is equipped with a CMCF phase 1,
• a satellite BTS is connected to a non satellite BSC,
• a non satellite BTS (i.e. this type of BTS or the BTS release do not support this
feature) is connected to a satellite BSC.
COMBINED BCCH
It is recommended to not use a combined BCCH for a satellite cell because of:
• Channel Request: the MS timer between Channel Request and Immediate

Assignment is shorter, in case of combined BCCH, thus the risk of triple Channel
Request is increased
• Lapd load: in order to distribute the signaling load over all DRX.
More details on recommended parameter associated to feature restrictions are given in the
Satellite Abis Interface - Engineering Guideline (refer to document [R32])
Nortel confidential

4.28. NETWORK SYNCHRONIZATION
4.28.1 GLOBAL DESCRIPTION
ASYNCHRONOUS NETWORK
When NW synchronization is not applied (asynchronous network), cells get their time base
through the PCM time. As PCM of different cells are not correlated, it can be considered that,
comparing to the hypothetical network time reference, the not co-site cells have on a site
basis:
• Random time bit offsets (from 0 to 156,25)

• Random time slot offsets (integer from 0 to 7)
• Random frame numbers offsets (integer from 0 to 2 715 647).
Consequently, as shown in the figure below, between two not co-site cells there are random:
• Δtime bit offsets

• Δtime slot offsets
• Δframe numbers offsets
FN x-1 FN x-1 FN x-1 FN x FN x FN x FN x FN x FN x

cell 1 5 6 7 0 1 3 4 5 6
Δ time bit offset (random)

Δ time slot offset
(random)
FN y-1 FN y FN y FN y FN y FN y FN y FN y FN y
cell 2 7 0 1 2 3 4 5 6 7
Δ frame number offset = y-x

(random)
General case of non synchronization
It has to be noted that a MS computes - using its timebase counter - the time offset by
measuring the time from the beginning of TS0 on its BCCH carrier and the beginning of the
first TS0 on a neighbor BCCH carrier. Also, the data found on these 2 TS0 may be used for
calculating the FNOffset between its cell and the neighbor cell.
Nortel confidential

SYNCHRONIZED NETWORK
With NW synchronization feature, all cells of a network could be synchronized on the same
clock, the GPS clock, through an additional external GPS receiver.
There are 2 ways this can be implemented:
• Burst synchronization in which all burst are aligned to the GPS clock
• Time synchronization in which all burst are aligned to the GPS clock and also a
absolute time (or a way to deduce it) is provided, as well, to all the equipments
FN x-1 FN x-1 FN x-1 FN x FN x FN x FN x FN x FN x

cell 1 5 6 7 0 1 3 4 5 6
Δ time slot offset

(random in burst synch)
(known&controlled in time synch)
FN y-1 FN y FN y FN y FN y FN y FN y FN y FN y
cell 2 7 0 1 2 3 4 5 6 7
Δ frame number offset = y-x

(random in burst synch)
(known&controlled in time synch)
General case of synchronization
Both type of synchronizations are implemented in Nortel’s portfolio and are supported by
addition of equipments (TMU) and parameters.
BURST SYNCHRONIZED NETWORK
In a burst synchronized network, it can be considered that, comparing to the hypothetical

network time reference, the not co-site cells have on a site basis:
• Time bit offsets = 0

• Random time slot offsets (integer from 0 to 7)
• Random frame numbers offsets (integer from 0 to 2 715 647).
It has to be noted that in a burst synchronized network these time slot offsets and frame
number offsets cannot be controlled and that every time a site is locked-unlocked these offsets
change randomly.
Nortel confidential

Consequently, see general case of synchronization figure on previous page, between two not
co-site burst synchronized cells there are:
• Δtime bit offsets = 0

• Random Δtime slot offsets
• Random Δframe numbers offsets
As in the case of an asynchronous network, the co-site cells have the same time bit offsets,
time slot offsets and frame number offsets.
TIME SYNCHRONIZED NETWORK
In a time synchronized network, it can be considered that, comparing to the hypothetical

network time reference, the not co-site cells have on a site basis:
• Time bit offsets = 0

• Known & controlled time slot offsets
• Known&controlled frame numbers offsets
Also, similar to the asynchronous network, the co-site cells have the same time bit offsets,
time slot offsets and frame number offsets.
Consequently, see general case of synchronization figure on previous page, between two not
co-site time synchronized cells there are:
• Δtime bit offsets = 0

• Known & controlled Δtime slot offsets
• Known&controlled Δframe numbers offsets
It has to be noted that the main difference between a time synchronized and a burst
synchronized network is that time slot offset planning and frame number offset
planning are possible only in a time synchronized network.

The parameters related to tune the feature are the following:
• btsSMSynchroMode
• tnOffset,
• fnOffset
• masterBtsSmId
Note: Other network existing parameters may have a significant impact on network
performances when network synchronization is applied:
• baseColourCode TSC (TSC=BCC) planning and therefore whole BSIC (NCC&

BCC) planning.
Nortel confidential

• Hopping laws parameters (HSN, MAIO, MA list)

• dARPPh1Priority
Also, it has to be noted that more parameters (for handovers, location services etc…) may
have to be eventually retuned for an optimal functioning when network synchronization feature
is deployed.
4.28.3 FEATURE IMPACTS EXPECTATIONS

Network synchronization simple deployment may have positive impact on location services as
the location precision will improve with a better synchronization of the network elements.
However, synchronizing all BTS in a network, meaning synchronizing interferers and their
victims, doesn’t provide alone any gain of RF quality or RF capacity. On the contrary, the
network synchronization may degrade the network RF performances if no additional feature or
engineering solution is applied. (The main degradation is mainly due to the eventual TSC
collisions if a traditional BSIC -NCC/BCC- planning as for an asynchronous network is used)
Therefore, for improving the RF quality and capacity, a network synchronization deployment
must be accompanied by additional features and significant engineering parameter planning.
Please refer to chapter Network synchronization engineering planning methodologies.
After Activing NW synchronization significant modifications of the NW behavior may occur at

various levels:
• Quantity of interferences:
being able to control cell FN Offsets, it may be possible to use some
carefully chosen of hopping laws (HSN, MAIO, MA list, FN) in order to
decrease the collision probability between one or more couples of cells
being able to control cell TN and FN Offsets, it is possible to completely
avoid the collisions between two cells which are not co-site when using a
fractional reuse frequency plan
Note: all this eventual control of the quantity of interferences is possible only
when time synchronizing the network as it is required to control and plan the
FN Offsets (and TN Offsets as well);
• Impact of interferences:
the various features of interferences cancellation and noise cancellation for
both BTS and MS are expected to work optimally (or better) when
synchronizing the network
• Others
HO reactivity, LCS precision …
Nortel confidential

4.29. NOVEL ADAPTIVE RECEIVER
4.29.1 PRINCIPLE
This v17.0 feature introduces a novel digital processing approach developed by Nortel
Networks for improving reception performances of GSM and EDGE radio communications. It
has been developed to enhance performances in real radio conditions (multipath profiles), with
a particular focus on interference from other radio channels (a major cause of disturbance for
reception performances).
Usual reception schemes are optimal under one specific noise assumption only, basically
thermal noise. However, digital communication faces in practice other noise sources, namely
adjacent channel and/or co-channel interferences, the statistics of which strongly differ from
thermal noise. The consequence is lower reception performances in presence of interferers,
leading to a poorer speech quality or lower throughput for the end-user. The approach
developed by Nortel consists in a scheme that adapts itself to the interference condition
affecting each received burst. In addition, a new filter design strategy has been developed in
order to come out, for each basic noise situation, with a filtering process yielding the minimal
BER.
This new method calls, prior to processing the burst, for an estimation of the noise situation.
This is achieved by a filter bank detector for the adjacent interferers; co-channels interferences
are taken into account later on, after channel sounding. According to the adjacent interference
noise estimated by the detector, a filter matching the noise situation is designed and applied to
the current burst.
Reception performance is significantly improved in most situations, especially with adjacent
interference conditions.
These benefits apply both to GMSK and 8PSK modulations, traffic and data applications. It
thus provides the end-user with an increased throughput for data transmission as well as an
improved quality of service for voice calls.
For more details, please refer to the Functional Note ([R45]).
4.29.2 HW/SW DEPENDENCE

This feature is applicable to :
• Hardware : BTS 6000/BTS18000 Radio Modules, 1900 MHz band only
• Software : v17.0 release.
4.29.3 ACTIVATION GUIDELINES
O&M PARAMETER
adaptiveReceiver is a new Class 2, transceiver object, parameter that serves to activate or

deactivate the Novel Adaptive Receiver. It can take two values :
Nortel confidential

• “enabled” : use of the Novel Adaptive Receiver

• “disabled” : use of the legacy signal processing
RECOMMENDATIONS
HILLY TERRAIN PROFILES
For cells operating under very specific radio conditions, namely hard Hilly Terrain profiles, the
Novel Adaptive Receiver structure may possibly cause a slight performance loss compared
with the initial processing. Therefore, it is recommended to disable the adaptive receiver for
these cells. :
adaptiveReceiver = disabled
INTERWORKING WITH RX DIVERSITY
If Rx diversity is used, best receiver performance is achieved by activating both Joint diversity
and Novel Adaptive Receiver features :
adaptiveReceiver = enabled; diversity = enhancedDiversity.
INTERWORKING WITH EXTENDED CELL
Novel Adaptive Receiver does not interwork with the Extended Cell feature.
Therefore, for extended cells, the Novel Adaptive Receiver must be deactivated :
adaptiveReceiver = false.
Nortel confidential

4.30. A5/3 ENCRYPTION ALGORITHM
4.30.1 PRINCIPLE
For details, please refer to the Functional Note ([R41]).
PURPOSE OF THE FEATURE
Before v17.0, the only available encryption algorithms available in the BSS were :
• No encryption
• Encryption algorithm version 1, also called A5/1
• Encryption algorithm version 2 (also called A5/2). A5/2 was removed from the GSM
networks at the end of 2006 in compliance with the 3GPP recommendations, as a
consequence of the published attacks against A5/2.
This v17.0 feature provides a new encryption algorithm in the BSS called A5/3.
Also, this feature changes the class of the existing parameter encryptAlgorSupported from
class 0 to class 3 to limit service disruption when changing its setting.
A5/3 ALGORITHM OVERVIEW
The A5/3 algorithm is stream cipher that is used to encrypt/decrypt blocks of data under a
confidentiality key Kc. The algorithm is based on the KASUMI algorithm, which is specified in
3GPP TS 35.202. KASUMI is a block cipher that produces a 64-bit output from a 64-bit input
under the control of a 64-bit ciphering key.
4.30.2 HARDWARE DEPENDENCE

A5/3 is supported on :
• DRX ND3
• eDRX
• RM.
4.30.3 CIPHERING ACTIVATION RULES
BSS PARAMETERS
ENCRYPTION ALGORITHM ACTIVATION
The BSS can select A5/3, on MSC request, for a call, assuming that :
• A5/3 is supported by the TRX
• A5/3 is supported by the mobile
Nortel confidential

• A5/3 is configured at the O&M level as the preferred encryption algorithm in the BSS
Since the A5/3 encryption algorithm is neither supported by all types of TRX nor by all
mobiles, and more especially by legacy mobiles already deployed by the operators, a fallback
encryption algorithm needs to be available whenever the A5/3 encryption algorithm is
requested by the MSC. In such a case, based on the value of the O&M parameter
encryptAlgorSupported , either “no encryption” or “A5/1” may be defined at O&M level as the
fallback encryption algorithm to be used by the BSS.
The encryptAlgorSupported parameter is an existing parameter which has been modified in

v17.0 as follows :
• The class is changed in v17.0 from class 0 to class 3. Thus, no BDA build is
necessary when changing the value of this parameter : no interruption of service
• The range of values has been expanded and now includes the following values :
o “None” : the BSS will not cipher any calls
o “gsmEncryptionV1” : all the BTS of the BSS will use A5/1 for ciphering, if
requested and allowed by the NSS
o (new value) “gsmEncryptionV3FallbackNoEncryption” : A5/3 is the preferred
algorithm for the BTSs of the BSS, but if this algorithm cannot be used for a
specific call in a specific cell (due to mobile capability limitation or TRX
capability limitation or MSC request), the BSS will not cipher the call
o (new value) “gsmEncryptionV3FallbackV1” : A5/3 is the preferred algorithm
for the BTSs of the BSS, but if this algorithm cannot be used for a specific call
in a specific cell (due to mobile capability limitation or TRX capability limitation
or MSC request), the BSS will attempt to use A5/1 instead.
BSSMAP MESSAGES CONFIGURATION PARAMETERS
With a Nortel BSS supporting the A5/3 feature, the NSS must be able to understand ciphering
information fields conveyed by the BSS to the NSS in the following BSSMAP messages :
• CIPHER MODE REJECT
• ASSIGNMENT COMPLETE
• HANDOVER PERFORMED
• HANDOVER REQUEST ACKNOWLEDGE
• CIPHER MODE COMPLETE.
Today (2007), all NSS software on the market supports these messages. Therefore, these
BSSMAP messages and fields must be enabled on the BSS side, otherwise the BSS will not
send them to the NSS, and this risks causing the ciphering procedure to operate in a less-
than-optimal manner.
To prevent this happening, the following BSS parameters must be set to value “true” :
• cypherModeReject
Nortel confidential

• encrypAlgoAssComp
• encrypAlgoCiphModComp
• encrypAlgoHoPerf
• encrypAlgoHoReq
• layer3MsgCyphModComp
NSS PARAMETERS
A5/3 is supported by the NSS Nortel since GSM07 by feature AD8028.

A5/3 is datafilled in the MSC by setting the following Office Parameters :
• GMSC_CIPHERING (OFCOPT table) : enables ciphering and deciphering of the radio
interface control between the MSC and the radio network subsystem (RNS) for the
transmission of user data or confidential network parameters.
• GSM_CIPHER_ALGORITHM_SUPPORTED” (OFCENG table) : indicates which GSM
ciphering algorithms are supported, in addition to the “no” encryption option. There are
seven defined algorithms (A5/1, A5/2, A5/3, A5/4, A5/5, A5/6, and A5/7).
4.30.4 PERFORMANCE IMPACT
BTS PROCESSING TIME
The ciphering processing time of the A5/3 encryption algorithm is not degraded compared to
the A5/1 processing time inside the BTS.
CALL SETUP TIME
On the other hand, since the “ciphering mode setting field” may be included in the Radio
Interface ASSIGNMENT COMMAND message, adding 1 byte, the BSS may need to send an
additional frame on the radio interface SDCCH channel in case the existing frame is already
full without this field. This additional frame could lead to 235 ms additional delay at the call
setup.
HANDOVER DURATION
In the same way, since the “ciphering mode setting field” may be added in the Radio Interface
HANDOVER COMMAND message, adding 1 byte, the BSS may need to send an additional
frame on the radio interface dedicated channel in case the existing frame is already full without
this field. This additional frame could lead to 235 ms (handover on SDCCH) or 20 ms
(handover on TCH) additional delay during the handover.
Nortel confidential

4.31. BTS SMART POWER MANAGEMENT
4.31.1 DEFINITIONS
Several definitions will be used in this section :
• Configured TRX : TRX that is mapped to a TDMA. The state of a configured TRX’s PA
depends on whether the TRX is active or idle (see definitions below) and on the
circumstances.
• Unconfigured TRX : transient state of the TRX that exists while the TRX has not yet
received the “current cell parameters” from the BTS
• Deconfigured TRX : state of a TRX that exists after having received a “clear config”
command from the BTS
• Spare TRX : TRX that is not mapped to a TDMA. The PA of a spare TRX may be in
state “ON” or state “OFF” depending on the circumstances, as explained in what
follows.
• Active TRX : configured TRX that is being used by signaling or traffic on at least one
of the TDMA’s radio timeslots. The PA of an active TRX is always “ON”.
• Idle TRX : configured TRX whose TDMA is not currently carrying any ongoing traffic or
signalling. The PA of an idle TRX may be in state “ON” or state “OFF” depending on
the circumstances, as explained in what follows.
4.31.2 PRINCIPLE
This feature switches off the PA after the TRX has been idle for a certain amount of time
(configurable via an O&M parameter). The PA is automatically switched back on again when a
circuit call is set up on one of its timeslots.
The PA can be switched “OFF” or “ON” thanks to an electronic switch. This switch can be set
to “ON” or “OFF” by software, thanks to a dedicated new TX firmware function.
4.31.3 PRE V17 BEHAVIOUR

Before v17.0, the BTS behaviour is the following :
When the TRX restarts (BTS start up, TRX lock/unlock, TRX trap … ) the PA is in an un-
powered state. It remains un-powered until it has received an RF Trans message from the
BSC.
Once the PA has been powered on, it remains so until the next reset or lock of the TRX.
This behaviour applies to all TRX regardless of their state :
• configured TRX (by definition, a configured TRX is mapped to a TDMA),
• spare TRX (by definition, a spare TRX is not mapped to a TDMA)
Nortel confidential

4.31.4 POST V17 BEHAVIOUR
FEATURE DEACTIVATED
CASE OF CONFIGURED TRX
In v17.0, if the feature is deactivated, the TRX behaves as before v17.0.
CASE OF SPARE, UNCONFIGURED OR DECONFIGURED TRX
The feature cannot be activated on a spare, unconfigured or deconfigured TRX. However, the
behaviour has been modified between v16.0 and v17.0 so that a spare or unconfigured or
deconfigured TRX is systematically switched off after a certain time For this, a 30 second
internal timer is started when the “enable TRX procedure” (RF Trans un-configuring) is
performed. When this timer expires, if no TDMA has been configured on the TRX, the PA is
switched off and its display hardware state is set to “OK – OFF cause
SmartPowerManagement”
As soon as the TRX is configured with a TDMA, this PA will be switched on.
FEATURE ACTIVATED
CASE OF TRX CONFIGURED WITH SPECIFIC TDMA
The TRX that are mapped to specific TDMA configurations are not allowed to turn off their PA.
The feature, even if it is activated, does not apply to them. These TDMA configurations are the
following :
• TDMA containing a BCCH channel
• TDMA containing a combined BCCH/SDCCH channel without CBCH
• TDMA containing a combined BCCH/SDCCH channel with CBCH
• TDMA containing a non-combined SDCCH/8 channel with CBCH channel
• TDMA containing a pDTCH channel
ALL OTHER CASES OF CONFIGURED TRX
For all other configured TRX whose TDMA is not in one of the above categories, if the feature
has been activated, the TRX automatically switches its PA OFF after the TDMA has been idle
a certain amount of time (configurable timer). The TRX switches its PA on again when a
channel is activated on the TDMA for a circuit-switched call establishment or for an incoming
handover.
More precisely :
• when the BTS receives a channel activation message from the BSC :
o If the PA had been switched off, it is switched back on. PA hardware state is
set to OK (or KO).
Nortel confidential

o If the PA is still on but the TRX is idle, meaning that the smart Power Switch-
Off timer is running, then this timer is immediately stopped.
• when the BTS receives a channel release message from the BSC : if there are no
more ongoing circuit-switched calls on the TRX (TRX has become idle), the
countdown of the smart Power Switch-Off timer is started.
The fact that the PA is switched off has no impact on the TRX operational state : the TRX
remains in the “in service” state.
The PA switching off has no impact on the TRX receive chain.
CASE OF SPARE TRX
The feature does not operate on a spare, unconfigured or deconfigured TRX, even if the
feature is activated on the cell.
However, the behaviour has been modified between v16.0 and v17.0 so that a spare,
unconfigured, or deconfigured TRX is systematically switched off, regardless of the activation
or deactivation of the smart power management feature. For this, a 30-second internal timer is
started when the “enable TRX procedure” (RF Trans un-configuring) is performed. When this
timer expires, if no TDMA has been configured on the TRX, the PA is switched off and its
display hardware state is set to “OK – OFF cause SmartPowerManagement”
As soon as the TRX is configured with a TDMA, it ceases to be a spare, unconfigured or

deconfigured TRX and its PA will be switched on.
4.31.5 HARDWARE DEPENDENCE

This feature is applicable to RM family only.
4.31.6 ACTIVATION GUIDELINES
O&M PARAMETERS
ACTIVATION PARAMETER
This feature is activated thanks to a new v17.0 BSS parameter called

smartPowerManagementConfig :
• Class 3
• object : powercontrol
• range : “enabled”; “disabled”
Nortel confidential

POWER SWITCH-OFF TIMER
A timer can be configured to delay the switching off for a certain time after the TRX has
become idle. The start value of this timer is defined by setting the parameter
smartPowerSwitchOffTimer :
• Class 3
• Object : powercontrol
• range : 5 to 255 minutes
The timer is used as follows :

• start condition : last active channel managed by this TRX is released
• stop condition : a channel for a new call or an incoming handover is allocated on the
TRX
• action on expiry : PA is switched off.
RECOMMENDATIONS
CONFIGURATION OF LOGICAL CHANNELS ON TDMA
As the TRX supporting pDTCH never switches off its PA, to take full benefit of this feature, it is
recommended not to configure more pDTCH than are strictly necessary.
As TDMAs that carry BCCH, SDCCH or pDTCH are never switched off, it is recommended to
collect these channels as far as possible on the same TDMA rather than spread them onto
several TDMAs.
MINIMUM TIMER VALUE
In the current BTS behaviour (without the feature), if there is no call on a TRX for 5 minutes at
least, the VVA consign of the PA is reduced by 2 dB.
The aim is to avoid untimely a “high current” alarm when the PA starts transmitting again after
a while without transmission. Such an alarm could occur if the PA gain, which depends on the
VVA consign, is not consistent with the “new” temperature of the PA when it starts transmitting
again (temperature goes down when PA stops transmitting).
With the “smart power management” feature activated, the temperature will fall all the more
as, on top of not transmitting, the PA is actually completely switched off. Moreover, this “off”
state may last the whole night causing even further temperature drop.
Therefore, before a PA is switched off, it is vital that the VVA consign should have been
reduced by 2dB so that when the PA is switched back on again, there are no high current
alarms. To ensure this VVA is reduced by 2dB, as explained above, 5 minutes must elapse
after the last call on the TDMA has been released. If the smart power timer is less than 5
minutes, the PA would be switched off before a VVA consign reduction cpuld be applied. So,
when the PA is switched back on again, it will apply the old consign corresponding to a high
Nortel confidential

temperature, whereas the PA will have significantly cooled down. This risks triggering an
alarm ans dpossibly damaging the PA.
To prevent this, the smart power swicth off timer minimum value has, by design, been set to 5
minutes.
OPTIMUM TIMER VALUE
The smaller the switch-off timer :

• the more reactive the power management will be to the minute-by-minute changes to
the call profile as the day progresses towards quieter moments
• the more power is likely to be saved as a result.
• but the more frequently the PA is likely to go through off/on cycles, especially at the
transition from busy hour to quieter hours, thus possibly impacting its life expectancy.
Furthermore, the more TRX per cell, the more TRX are eligible for switch-off, and therefore the
more the feature is expected to make a difference to the power consumption.
Nortel confidential

5. ALGORITHM PARAMETERS
5.1. INTRODUCTION
This chapter lists parameters, sorted according to their group, as they were defined in the
previous Chapter.
The following information is provided for each parameter:
• a brief description
• value range and unit
• the recommended value: takes the best benefit of the feature in a standard network
configuration and environment.
• process in which it is used (see Chapter 2)
• some engineering rules that must be considered for the parameter setting
• the object that contains this parameter
• the default value. Most of the time, the default value inhibits the feature
characterized by this parameter
• corresponding GSM name
• GSM Recommendation
• parameter type and OMC-R class (see note below)
Note: The recommended value is established from Nortel experience and studies. This value
has to be adapted according to the network specificities. For the recommended value in GSM
900, it is the same value for eGSM and GSM-R when nothing else is recommended for these
two networks. This value is not contractual, and it could change with Nortel new studies results
and experience growth.
The following types of parameters can be distinguished:
• Customer engineering parameters:

Addressing: relative to an object
Design: contract characteristic
Optimization:network tuning
Operation: network operation
• Manufacturer parameters:
System: modifying such a parameter seriously impacts system
behaviour
Product: parameters related to the current system release
DP: stands for permanent data
OMC-R class gives rules to be followed when modifying a parameter:
CLASS Rules
Class 0 Implies reconstruction of the BDA
Put BSC out of service (i.e. BSC state set to “locked”), takes new parameters into account by
Class 1
resetting active chain and passive chains
Class 2 Declares the object (or its parent) temporarily out-of-service before modification
Class 3 Modification is dynamically taken into account
Nortel confidential

5.2. 2G CELL SELECTION AND RESELECTION PARAMETERS
cellReselectHysteresis Class3 V7
Description: Hysteresis to reselect towards a cell:
when the MS is in IDLE mode and reselects a cell with a different
LA (Location Area)
when the MS is in GPRS STANDBY mode and reselects a cell with
a different LA (Location Area) or a different RA (Routing Area)
when the MS is in GPRS ready state and reselects a different cell
Value range: [0 to 14, by steps of 2] dB
Object: bts
Default value: 6 dB
Type: DP, Optimization
Rec. value: 6 dB (rural / low cell overlap), 10 dB (urban / high cell overlap)
Used in: Criteria for reselection towards a cell of a different Location Area
(Sel_2)
Eng. Rules: GSM case:
A high value prevents the MS from making frequent location updates
and may also prevent an MS from performing adequate location
updates, thus risking not receiving calls. The level variation of the
signal is more important in an urban context, so a higher value of
hysteresis should be set. To avoid frequent location updates, there is
also a timer forbidding the reselection of the previous server cell. For
a reselection with change of location area, the value is 15 seconds.
GPRS case:
In order to minimize the impact of the introduction of the GPRS in an
existing GSM network, it is recommended not to modify the current
value of CellReselectHysteresis used for voice. A high value would
keep the link for a long time hence some communications would have
a high BLER due to an important load of the cell. The throughput
would then decrease because of the retransmission at RLC/MAC
layer.
On the other hand a low value would ease the cell reselection ping-
pong in data mode which could severely decrease the overall user
throughput due to the gap of transmission during the reselection.
In case of cell overlap (i.e. urban environment, site covered in several

frequency bands), 10dB should be considered in order to minimize
ping-pong reselections.
Nortel confidential

cellReselectOffset Class 3 V8
Description: Encouragement to reselect a cell (C2 criterion) for phase 2 MS
Object: bts
Default value: 4
Rec. value: Between 4 and 10
Used in: Additional reselection criterion (for phase 2) (Sel_3)
Eng. Rules: Otherwise, if there is no privileged layer, the recommended value
remains the same for both sites, between 4 dB and 10 dB.
cellReselInd Class 3 V8
Description: Whether cell reselection criterion (C2) use is authorized
Value range: [true / false]
Object: bts
Default value: true
Rec. value: True
Eng. Rules: See chapter Selection, Reselection Algorithms
msTxPwrMaxCCH Class 3 V7
Description: Maximum MS transmission power in a cell CCCH
The BSC relays the information to the mobiles in the Abis CELL
MODIFY REQUEST message.
Value range: [5 to 43, by steps of 2] dBm (GSM 900, GSM-R, GSM850, GSM850-
GSM1900 and GSM 900& 850MHz - GSM 1800 networks)
[0 to 36, by steps of 2] dBm (GSM 1800 and GSM 1900 - GSM 900 &
850MHz networks)
[0 to 33] dBm (GSM 1900 network and 1900-850 network)
[0 to 33] dBm (E-GSM network)
Object: bts
Default value: Typical value of 33 dBm for GSM 900 & 850MHz handhelds, 30 dBm
for GSM 1800 and 1900
Rec. value: 33 dBm for GSM 900 & 850MHz, 30 dBm for GSM 1800 and 1900
Used in: Selection or reselection between cells of current Location Area
(Sel_1), Criteria for reselection towards a cell of a different Location
Area (Sel_2), Additional reselection criterion (for phase 2) (Sel_3)
Nortel confidential

Eng. Rules: In GSM 900 & 850MHz, msTxPwrMax = msTxPwrMaxCCH. In GSM

1800 or 1900, msTxPwrMaxCCH ≤ msTxPwrMax. Both are verified at
OMC-R level. This value is related to typical mobile (handheld or
vehicle-mounted) and assumed an environment (urban, rural). If the
cell is rural, it is possible to put a higher value because lot of mobiles
have car kits (can transmit at a higher power). In urban environment,
the density of mobile increases and care should be taken to reduce
interferences. Furthermore, the major part of the mobile market are
handsets.
Remark: If the cell is used as a neighbor cell of another serving cell in the
network, msTxPwrMaxCCH must be identical to the msTxPwrMaxCell
power defined for the corresponding adjacentCellHandOver object
(the values must be checked by users).
penaltyTime Class 3 V8
Description: Timer used by an idle mobile before reselecting a cell (C2 criterion)
When a mobile places the cell on the list of strongest carriers, it starts
a timer that stops after penaltyTime seconds. This timer is reset when
the mobile removes the cell from the list.
For the entire timer duration, the reselection criterion (C2) is assigned
a negative temporaryOffset value.
Refer to the cellReselectOffset parameter in the Dictionary.
Value range: [20 to 640, by steps of 20] seconds.
The value “640” is reserved and indicates that the temporary offset is
ignored in the reselection criterion (C2) calculation. It also changes
the sign in the C2 formula.
Object: bts
Default value: 20
Rec. value: 20
Eng. Rules: The longer this timer is, the longer a penalty is applied for reselecting
that cell. The value should be correlated with the expected mobiles
speeds, which are to be managed by that cell.
Nortel confidential

rxLevAccessMin Class 3 V7
Description: Minimum signal strength level received by the mobiles for being
granted access to a cell. The information is sent to MS prior to
registering.
As an example, a threshold level of -104 dBm corresponds to an
acceptable BER of approximately 10-2 (minimum recommended
value).
Value range: [less than -110, -110 to -109, ... , -49 to -48, more than -48] dBm
Object: bts
Default value: less than -110 dBm
Rec. value: GSM 900/GSM 850: -101 to -100 dBm,
GSM 1800/1900: -99 to -98 dBm
(Sel_1), Criteria for reselection towards a cell of a different Location
Area (Sel_2), Additional reselection criterion (for phase 2) (Sel_3)
Eng. Rules: Main parameter for selection or reselection.
Notice that the tuning of this parameter strongly depends on the
operator strategy. Decreasing the value eases the access to the
network by reducing the quality. This parameter defines the cell
access size.
Remark: The difference between GSM 900/GSM 850 and GSM 1800/1900 is
due to MS sensitivity (-104 dBm (GSM 900/GSM 850), -102 dBm
(GSM 1800/1900)).
Example:
RxLevAccessMin 1 = -100 dBm

RxLevAccessMin 2 = -99 dBm
A rough calculation gives the following impact on the cell access
surface: Access Zone 1 = Access Zone 2 x 1.2
LCAUTION! A very low value of RxlevAccessMin allows mobiles to camp and
attempt calls. Most of calls attempts at very low field levels fail, or lead
to a call drop a few seconds after the call has been established. This
assessment is also true for GPRS/EDGE procedure, a very
permissive value of RxlevAccessMin leads to data establishment
failure and TBF drop.
Nortel confidential

temporaryOffset Class 3 V8
Description: Negative offset applied during Penalty Time for reselecting a cell (C2
criterion)
This negative offset is applied during the entire penaltyTime duration
and allows to prevent speeding mobiles from selecting the cell. Refer
to the cellReselectOffset entry in the Dictionary.
Object: bts
Default value: 70
Rec. value: 0 (microcell & macrocell in mono-layer),
70 (macrocell in multi-layers)
Eng. Rules: The value prevents a mobile from reselecting a cell during
PenaltyTime. By giving the highest possible value, which is higher
than the field strength range (0 to 63), we ensure that the mobile will
not reselect the cell before the timer expires. Then, the value 70
means the applied offset is infinite.
It could be dangerous on a microcell or macrocell in a mono-layer
environment to have a high value, because it slows down the
reselection process. However, on a macrocell in a multi-layers
environment, it is recommended to prevent from reselecting a cell
(value 70), in keeping a low value for “penaltyTime” (20 seconds).
Nortel confidential

5.3. 2G-3G CELL RESELECTION PARAMETERS
gsmToUmtsReselection Class 3 V14

Description: gsmToUmtsReselection is composed of 4 parameters:
uMTSsearchMinLevel
uMTSreselectionOffset
uMTSAccessMinLevel
uMTSReselectionARFCN
Object: bts
Type: DP
uMTSAccessMinLevel Class 3 V14

Description: A minimum threshold for Ec/No for UTRAN FDD cell re-selection
(GSM spec 45.008 name for this parameter is FDD_Qmin)
Value range: [0: - 20 dB, 1: - 6 dB, 2: - 18 dB, 3: - 8 dB, 4: - 16 dB, 5: - 10 dB, 6: -
14 dB, 7: - 12 dB]
Object: bts
Default value: - 12 dB
Type: DP
Rec. value: - 12 dB
Used in: 2G - 3G Cell Reselection
Eng. Rules: below the recommended value UE may not be able to reach the 3G
network in good conditions.
Note: The SI2Quater message broadcasted by the BSS is an index [0 to 7]
that is interpreted by the mobile depending on the release date of that
mobile:
Index Mobiles’ interpretation Mobiles’ interpretation
before October 2003 after October 2003
0 - 20 dB - 20 dB
1 - 19 dB - 6 dB
2 - 18 dB - 18 dB
3 - 17 dB - 8 dB
4 - 16 dB - 16 dB
5 - 15 dB - 10 dB
6 - 14 dB - 14 dB
7 - 13 dB - 12 dB
One should be advised that OMC-R may eventualy display “old”

values while the offset is broadcasted.
uMTSReselectionARFCN Class 3 V14

Description: Neighbouring UMTS cell ARFCN. Although no control is performed on
the value, it shall be indicated on the OMC-R display as a comment
that a UTRAN ARFCN FDD is from 10562 to 10838.
(GSM spec 45.008 name for this parameter is FDD_ARFCN)
Nortel confidential

Value range: 0 to 16383

Object: bts
Default value: 0
Type: DP
Rec. value: a non-null value to broadcast the SI2Quater on the BCCH
Eng. Rules:
uMTSReselectionOffset Class 3 V14

Description: Applies an offset to RLA_C for cell reselection to access technology /
mode FDD (GSM spec 45.008 name for this parameter is
FDD_Qoffset)
Value range: [-∞dB, -28 dB, -24 dB, -20 dB, -16 dB, -12 dB, -8 dB, -4 dB, 0 dB, 4
dB, 8 dB, 12 dB, 16 dB, 20 dB, 24 dB,28 dB]
Object: bts
Default value: -∞dB
Type: DP
Checks:
Rec. value: see Engineering Rules
Eng. Rules: that parameter allows a fine tuning in UMTS re-selection by
introducing a favorable/defavorable offset toward a UMTS cell.
The recommanded value by default is “0 dB”. This parameter should
set according to the operator strategy. Indeed 3G layers can be seen
as an 1800 Layer, therefore the reselection 2G 3G layer should be as
reselection strategy between 900 and 1800 layer.
uMTSSearchLevel Class 3 V14

Description: Search for 3G cell if signal level is below or above the threshold
(GSM spec 45.008 name for this parameter is Qsearch_I)
Value range: [0: “< -98 dBm”, 1: “< -94 dBm”, 2: “< -90 dBm”, 3: “< -86 dBm”, 4: “< -
82 dBm”, 5: “< -78 dBm”, 6: “< -74 dBm”, 7: “Always”, 8: “> -78 dBm”,
9: “> -74 dBm”, 10: “> -70 dBm”,11: “> -66 dBm”, 12: “> -62 dBm”, 13:
“> -58 dBm”, 14: “> -54 dBm”, 15: “Never”]
Object: bts
Default value: -98 dBm
Type: DP
Eng. Rules: this parameter set whether UE should search for UMTS cells or not. It
can allow UE to search above a certain level, below a certain level, or
always. Note that in this last case the UE battery autonomy can be
impacted.
Nortel confidential

5.4. LEGACY MEASUREMENT REPORTING PARAMETERS
powerControlIndicator Class 3 V7
Description: Whether MS signal strength measurements on the TCH or SDCCH
should include measurements on BCCH frequency or not.
Value range: [include BCCH measurements / do not include BCCH measurements]
Object: bts
Default value: include BCCH measurements
Rec. value: See Eng. Rules
Used in: Power Control Algorithms
Eng. Rules: Downlink measurements performed by the mobile on TCH or SDCCH
should not include measurements done when the channel frequency
is the BCCH frequency if the following two conditions are met:
The radio channel hops at least on two different frequencies, on of
which is the BCCH frequency.
Power control on the downlink is used.
LCAUTION! This parameter is only relevant with BTS using cavity coupling
because only cavity coupling allows to use BCCH frequency as part of
the hopping frequency list. For BTS using hybrid coupling, the BCCH
frequency is never part of the hopping list, so this parameter is
irrelevant in that case. See §4.5.9 for details.
Nortel confidential

5.5. ENHANCED MEASUREMENT REPORTING PARAMETERS
fDDMultiratReporting Class 3 V17

Description: (applicable both to normal measurement reporting and EMR) Number
of UTRAN FDD cells to be reported by the mobile in the list of
strongest cells inside the normal or Enhanced Measurement Report
message.
Value range: 0: “no UTRAN cell is favoured”
1: “1 UTRAN strongest cell is favoured”
2: “2 strongest UTRAN cells are favoured”
3: “3 strongest UTRAN cells are favoured”
Object: bts
Default value: 0
Rec. value: see Eng. Rules
Used in: Enhanced Measurement Reporting (EMR)
UTRAN cell reporting using legacy measurement reports (V17)
Eng. Rules: The value depends on the network operator strategy.
However, in case of HO2G-3G enabled with normal measurement
reporting (EMR disabled), it is necessary to exercise caution when
setting the parameters fDDMultiRatReporting and
multiBandReporting. These parameters define the number of UTRAN
cells and non-serving band GSM cells, respectively, that must be
included by the mobile in the list of strongest cells in the measurement
report. Therefore it leaves (6 - fDDMultiRatReporting -
multiBandReporting) spaces for the serving band GSM cells.
Therefore, if EMR is disabled, it is recommended not to exceed
fDDMultiRatReporting = 2 and multiBandReporting = 2.
fDDreportingThreshold Class 3 V17

Description: CPICH RSCP level measured on UTRAN cells, above which the
mobile shall apply a higher priority to UTRAN cells in the enhanced
Value range: -115 dBm, -109 dBm, -103 dBm, -97 dBm, -91 dBm, -85 dBm, -79
dBm, never
Object: handoverControl
Default value: never
Rec. value: -97 dBm
Eng. Rules: An operator willing to unload GSM network to UMTS network but
keeping calls in good conditions should set this parameter to at least -
97dBm, ensuring a high probability of good Ec/No value after the HO
and limiting the high increase of UTRAN incoming HO due to ping
pong handover.
Nortel confidential

This parameter must be in accordance with 3G to 2G HO parameters.
In order to limit ping pong effect, a hysteresis of 5 dB is recommended

between fDDreportingThreshold and UTRAN hard HO 3G to 2G
CPICH RSCP threshold.
fDDreportingThreshold2 Class 3 V17

Description: (applicable both to normal measurement reporting and EMR,
applicable from MS release 5) CPICH Ec/N0 level measured on
UTRAN cells, above which the mobile shall report UTRAN cells in the
enhanced measurement report message
Value range: 0 to 63 (0 means “always reported”)
Default value: 0 (“always reported”)
Rec. value: 28
Eng. Rules: To ensure a good quality after the handover, a simultaneously not too
restrictive and good C/I value must be required.
Setting this parameter at 28 which corresponds to Ec/No = -10 dB
seems to be a good compromise.
This parameter must be in accordance with 3G to 2G HO parameters.
In order to limit ping pong effect, a hysteresis of 2 dB is recommended
between fDDreportingThreshold2 and UTRAN hard HO 3G to 2G
Ec/No threshold.
Note: The Ec/No step is in half dB:
- “0” means always reported
- In range 1 to 49, “1” means “CPICH Ec/No ≥ -24 dB” and “49” means
“CPICH Ec/No ≥ 0 dB”.
CPICH Ec/N0 level measured = - 24 + fDDreportingThreshold2/2
- Values from 50 to 63 should not be used for Ec/No.
qsearchC Class 3 V17

Description: (applicable both to normal measurement reporting and EMR). This
parameter is called Qsearch_C in the GSM specification. It gives the
serving cell’s BCCH level below which the MS must listen to
neighbours. If the serving BCCH frequency is not part of the
BA(SACCH) list, the dedicated channel is not on the BCCH carrier,
and qsearchC is not equal to 15, the MS shall ignore the qsearchC
parameter value and always search for UTRAN cells. If qsearchC is
equal to 15, the MS shall never search for UTRAN cells.
Value range: 0: “< -98 dBm”
1: “< -94 dBm”
2: “< -90 dBm”
3: “< -86 dBm”
4: “< -82 dBm”
5: “< -78 dBm”
Nortel confidential

6: “< -74 dBm”

7: “always”
8: “> -78 dBm”
9: “> -74 dBm”
10: “> -70 dBm”
11: “> -66 dBm”
12: “> -62 dBm”
13: “> -58 dBm”
14: “> -54 dBm”
15: “never”
QsearchC < -XX dBm: the HO towards the UMTS can be done only if
the RxLev from the serving cell is below -XX dBm.
QsearchC > -XX dBm: the HO towards the UMTS can be done only if
the RxLev from the serving cell is above -XX dBm.
Default value: 15 (“never”)
Rec. value: 7 (“always”)
Eng. Rules: Cases where a different value from “always” could be useful have not
been identified. Therefore value “always” is recommended.
reportTypeMeasurement Class 3 V17

Description: type of measurement report to be reported on this cell : enhanced
measurement report or legacy measurement report
Value range: 0 : Measurement report
1 : Enhanced Measurement Report
Object: bts
Default value: 0
Rec. value: 1
Eng. Rules: To take advantage of EMR benefits it is recommended to activate

EMR.
In case of HO 2G -3G activation either EMR or legacy measurement
does not have any impact on the Handover 2G to 3G efficiency.
Nortel confidential

servingBandReporting Class 3 V17

Description: (applicable to EMR only) This parameter sets the value of the
SERVING_BAND_REPORTING field in Measurement Information
messages.
It defines the number of cells from the GSM serving frequency band
that shall be included in the list of strongest cells in the enhanced
measurement report.
Value range: 0 : “no inband cell is favoured”
1: “1 strongest inband cell is favoured”
2: “2 strongest inband cells are favoured”
3: “3 strongest inband cells are favoured”
Object: bts
Default value: 3
Rec. value: 3
Eng. Rules: Depends on the network operator strategy.
servingBandReportingOffset Class 3 V17

Description: (applicable to EMR only) This parameter sets the value of the
XXX_REPORTING_OFFSET field in Measurement Information
messages, for the GSM band (XXX =900 or 1800 or 400 or 850 or
1900).
If there is not enough space in the report for all valid cells, the cells
shall be reported that have the highest sum of the reported value
(RXLEV) and the parameter servingBandReportingOffset
(XXX_REPORTING_OFFSET) for the serving GSM band. Note that
this parameter shall not affect the value itself of the reported
measurement.
Value range: 0, 1, ... 7, 0xFF : 0 dB, 6 dB, …, 42 dB, “not significant”
Default value: empty
Eng. Rules: This parameter should be tuned if EMR is used during an IM
campaign. If, during the Interference Matrix campaign in a dual band
network, the reporting of serving band neighbours is deliberately
favoured by using the servingBandReportingOffset , then, as a side-
effect, the traffic distribution may be modified. This undesirable side-
effect may in turn modify the results of the IM measurements, which
therefore may no longer reflect the real situation in the field once the
IM has ceased. Therefore it is recommended to ensure that the
chosen value of servingBandReportingOffset does not cause
unacceptable changes in the traffic distribution.
Nortel confidential

5.6. RADIO LINK FAILURE PARAMETERS
callReestablishment Class 3 V7
Description: Whether call re-establishment in a cell is allowed when the radio link
is broken off for propagation reasons
The information is broadcast to the mobiles at regular intervals on the
cell BCCH.
On receipt of a CHANNEL REQUIRED message with cause “call re-
establishment”, the BSC attempts to allocate a TCH in one of the cells
where call re-establishment is allowed. Then, if no TCH is available
the BSC attempts to allocate a SDCCH.
Value range: [allowed / not allowed]
Object: bts
Default value: not allowed
Rec. value: allowed
Used in: Radio link failure process (run by the MS),
Call reestablishment procedure
Eng. Rules: Enabling or not this feature is a MSC capability issue
radioLinkTimeout Class 2 V7
Description: Maximum value of the counter (S) associated with the downlink
SACCH messages, beyond which the radio link is cut off. It is lower
than or equal to t3109.
Mobiles comply with system operating conditions when the counter
(S) is assigned a value lower than or equal to t3109.
If the receiver is unable to decode a downlink SACCH message
(BTS–to–MS direction), the counter is decreased by 1. If the message
is received, the counter is increased by 2. When the counter goes
down to zero, the radio link is declared “faulty”.
Value range: [4 to 64, by steps of 4] SACCH frames (1 unit = 480 ms on TCHs, 470
ms on SDCCHs)
Object: bts
Default value: 20 SACCH
Rec. value: 20
32 when AMR is activated
Nortel confidential

Used in: Radio link failure process (run by the MS),

AMR - Adaptative Multi Rate FR/HR
Eng. Rules: radioLinkTimeOut < t3109.
If surrounding cells accept re-establishment (from GSM08 for DMS
MSC), overall process should not be too long.
Small value: call might be dropped before a move to a more
favorable environment could occur.
High value: in case of permanent bad conditions, user’s anger and
taxation increase before actual call’s end or reestablishment.
Remark: The rlf1 attribute serves the same goal on the uplink, but the system
does not check that the values of the two attributes are consistent.
rlf1 Class 2 V8
Description: Value to compute the initial and maximum value of the (CT) counter
used in the BTS radio link control algorithm
The FP runs the following algorithm to monitor the uplink SACCHs
(MS–to–BTS direction):
The CT counter is reset to zero when the FP receives a CHANNEL
ACTIVATION message.
On each occurence of an uplink SACCH, the following occurs:
if the channel is decoded and CT = 0, then CT = 4 * rlf1 + 4
if the channel is decoded and CT ≠ 0, then CT = min (4 * rlf1 + 4,
CT+rlf2)
if the channel is not decoded, then CT = max (0, CT - rlf3)
When the CT counter goes down to zero, the radio link is broken and
the BTS sends a CONNECTION FAILURE INDICATION message to
the BSC.
Value range: [0 to 15]
Object: bts
Default value: 4
Rec. value: 4
7 when AMR is activated
Used in: Radio link failure process (run by the BTS),
Eng. Rules: The resulting CT value is the same as “radioLinkTimeOut” value.
There is no reason to recommend to cut a communication more
rapidly in the uplink or downlink direction. In a network with a lot of
traffic or with many zones of interference, a lower value (between 2
and 4) of this parameter is recommended. Typically the value, in such
a case should be 2.
Notes: The radioLinkTimeOut attribute serves the same goal on the downlink,
but the system does not check that the values of the two attributes are
consistent.
Nortel confidential

rlf2 Class 2 V8
Description: Step value by which the (CT) counter is increased by the radio link
control algorithm when an uplink SACCH is decoded.
Refer to the rlf1 entry.
Value range: [1 to 4] SACCH frames
Object: bts
Default value: 2
Rec. value: 2
Used in: Radio link failure process (run by the BTS)
Eng. Rules: The value should be higher than rlf3 value, in order to encourage the
continuity of service. The higher the value, the longer an MS will keep
a bad quality communication in a disturbed zone. The choice of this
value must be made by the operator, in keeping with its service quality
level.
rlf3 Class 2 V8
Description: Step value by which the (CT) counter is decreased by the radio link
control algorithm when an uplink SACCH is not decoded
Refer to the rlf1 entry.
Value range: [1 to 4] SACCH frames
Object: bts
Default value: 1
Rec. value: 1
Used in: Radio link failure process (run by the BTS)
Eng. Rules: It is recommended to fix this value to 1. This allows the use of the rlf1
value to set the maximal duration of consecutive non-reception of
SACCH frame.
Nortel confidential

5.7. SIGNAL QUALITY AVERAGING PARAMETERS
missRxQualWt Class 3 V7
Description: Weight applied to missing Quality measurement
The missing measurement is replaced by the latest computed
arithmetic average, or by the latest received raw measurement if no
average value is available, weighed by this corrective factor when
calculating the average bit error rate in the radio link. The range of
permitted values makes missing quality measurements not favored.
Value range: [100 to 200] %
Object: handOverControl
Default value: 110
Rec. value: 110
Used in: Missing Downlink Measurements
Eng. Rules: The higher the value is, the higher the missing measurement will be
weighted.
rxQualHreqave Class 3 V7
Description: Number of bit error rate measurements performed on a serving cell,
used to compute arithmetic BER averages in handover and power
control algorithms
Value range: [1 to 10] number of measurement results
Default value: 8
Rec. value: 4 in urban environment,
> 8 in rural environment
Used in: Measurement Processing
Eng. Rules: In order to minimize calculation of temporary averages it is better if
runHandOver and runPwrControl are multiples or sub multiples of
rxQualHreqAve. Length of weighed average window should be
reduced when the cell is small or environment requires quick
reactivity. Studies have shown that a reduction of the window size
value (from 8 to 4 for instance) does not increase the number of
handovers on a network and does not change handover causes.
However, it has a positive impact, because it leads to a greater
reactivity.Then, the weighted average window size (rxQualHreqAve *
rxQualHreqt) has to be correlated to the hoMargin value to keep a low
ping-pong probability.
The larger the window size, the lower the hoMargin should be.
Nortel confidential

rxQualHreqt Class 3 V7
Description: Number of arithmetic averages taken into account to compute the
weighted average bit error rate in handover and power control
algorithms. Each is calculated from rxQualHreqave bit error rate
(BER) measurements on a radio link.
Default value: 1
Rec. value: 1
Eng. Rules: The quality and signal strength weighted average window should
encompass the same period. For the sake of simplicity, the default
value disables weighting. The weighed average window size
(rxQualHeqAve * rxQualHreqt) must be correlated to the hoMargin
value to keep a low ping-pong probability.
rxQualWtsList Class 3 V7
Description: List of up to sixteen weights used to compute the average bit error
rate on a radio link
The L1M function calculates rxQualHreqave arithmetic averages from
raw measurements, and balances rxQualHreqt averages among those
with the weights defined in rxQualWtsList.
Each arithmetic average is partnered with one weight in the list.
Weight/average associations are set in the order in which the weights
are recorded. The latest computed arithmetic average is always
partnered with the first weight in the list.
Super–average = [∑ (averagei x weighti)] / 100, i = 1 to rxQualHreqt
Default value: 100
Rec. value: 100
Eng. Rules: Values add up to 100.
If there are several values, the biggest weights must be used for more
recent reports.
In rural environment, rxLev and rxQual weighed average window will
not refer to the same time window.
Nortel confidential

5.8. SIGNAL STRENGTH AVERAGING PARAMETERS
missRxLevWt Class 3 V7
Description: Weight applied in case of missing signal strength measurement
report
The missing measurement is replaced by the latest computed
arithmetic average, or by the latest received raw measurement if no
average value is available, weighed by this corrective factor when
calculating the average signal strength in the cell.
Selecting the greatest value makes missing strength measurements
not favored.
Default value: 90
Rec. value: 90
Eng. Rules:
rxLevHreqave Class 3 V7
Description: Number of signal strength measurements performed on a serving cell,
used to compute arithmetic strength averages in handover and power
control algorithms
Default value: 8
Rec. value: 6 for small cells (Dintersite < 800m)
between 8 and 10 for large cells (Dintersite > 1600m)
Eng. Rules: In order to minimize calculation of temporary averages it is better if
runHandOver and runPwrControl are multiples or sub multiples of
rxLevHreqAve. In an urban environment, the window size should be
minimized and the hoMargin value should be high. However, choosing
too small a value leads to averaging meaningless measures in case of
DTX activation uplink or downlink. Then, in an urban environment,
according to building density, antenna height and global environment,
the window size can fluctuate between 6 and 8. The minimum value,
6, may be preferred, because it ensures a good reactivity without bad
influence if the parameter hoMargin is well chosen.
Nortel confidential

rxLevHreqaveBeg Class3 V11

Description: Number of measurement reports used in short averaging algorithm on
current cell for signal strength arithmetic average
Refer to the rxLevHreqave entry in the Dictionary.
Default value: 2
Rec. value: 2
Used in: Early HandOver Decision
Eng. Rules: rxLevHreqaveBeg < rxLevHreqave
This parameter has to be coupled with hoMarginBeg and
rxLevNCellHreqaveBeg.
Remark: This parameter is only available for DCU4 or DRX transceiver
architecture.
rxLevHreqt Class 3 V7
Description: Number of arithmetic averages taken into account to compute the
weighted average signal strength in handover and power control
algorithms. Each is calculated from rxLevHreqave signal strength
measurements on a serving cell.
Default value: 1
Rec. value: 1
Eng. Rules: In a urban environment, the window size should be minimized and the
hoMargin value should be high.
For the sake of simplicity, weighted averaging is disabled by default
value.
LCAUTION! The weighted average is not used for the PBGT. The weighed
average window size (rxLevHreqAve * rxLevHreqt) has to be
correlated to the hoMargin value to keep a low ping-pong probability.
Nortel confidential

rxLevWtsList Class 3 V7
Description: Values of weights to be used for signal strength weighed average
The L1M function first calculates rxLevHreqave arithmetic averages
from raw measurements, and balances rxLevHreqt averages among
those with the weights defined in rxLevWtsList.
Each arithmetic average is partnered with one weight in the list.
Weight/average associations are set in the order which the weights
are recorded. The latest computed arithmetic average is always
partnered with the first weight in the list.
Super–average = [ ∑ (averagei x weighti)] / 100, i = 1 to rxLevHreqt
Default value: 100
Rec. value: 100
Eng. Rules: Arithmetic law to be preferred, biggest weight for most recent reports
Nortel confidential

5.9. NEIGHBOR CELL AVERAGING PARAMETERS
cellDeletionCount Class 3 V7
Description: The cellDeletionCount is to be compared to the number of
consecutive Measurement Results messages not containing
information on one of the neighbour cells that would result in the cell
being no longer eligible.
Before V12, the neighbour cells information of such a cell would be
discarded.
From V12 (TF 1089-2), from a number ≥ cellDeletionCount the cell will
be non eligible, but the information of that neighbour cell will only be
discarded when the number of consecutive Measurement Results with
no information on the cell will reach 10 (i.e. 5 sec).
Object: bts
Default value: 5 in rural environment, 2 in microcell environment
Type: DP, Design
Rec. value: 5 in rural,
2 in urban environment
Handovers screening
Eng. Rules: As there is no weighting factors on neighboring cells, low values of
cellDeletionCount are advised and so the rule cellDelectionCount <
rxNcellHrequave. A mobile is required to keep synchronization
information at least 10 seconds after a cell was removed from the best
cells list. This synchronisation becomes quickly obsolete in the case of
fast moving mobiles.
LCAUTION! This mechanism applies only for Power budget handover.
Remark: Further informations are provided in chapter Best Neighbor Cells
Stability
Nortel confidential

rxNCellHreqave Class 3 V7
Description: Number of measurement results used in the PBGT algorithm to
compute the average neighboring signal strength
No weighed average is computed for this category of measurement
Default value: 8
Rec. value: 6 for small cells (Dintersite < 800m)
between 8 and 10 for large cells (Dintersite > 1600m)
Eng. Rules: In the PBGT formula, the RXLEV_DL is the last arithmetic signal
strength on the current cell. In order to use the same time base, we
should have rxNcellHreqAve = rxLevHreqAve.
rxLevNCellHreqaveBeg Class 3 V11

Description: Number of measurement results used in short averaging algorithm to
compute the average neighboring signal strength
Default value: 2
Rec. value: 2
Used in: Early HandOver Decision
Eng. Rules: rxLevNCellHreqaveBeg < rxLevNCellHreqave
This parameter has to be coupled with hoMarginBeg and
rxLevHreqaveBeg.
architecture.
Nortel confidential

5.10. DISTANCE AVERAGING PARAMETERS
distHreqt Class 3 V7
Description: Number of distance measurements, used to compute the weighted
average MS–to–BTS distance in handover algorithms
Default value: 4
Rec. value: 4
Eng. Rules: For distance handover and Call Clearing, a weighted average of the
MS-BS distance is computed from timing-advance results.
distWtsList Class 3 V7
Description: List of no more than sixteen weights, used to compute the average
MS–to–BTS distance from distHreqt measurements
The L1M function balances distHreqt raw measurements with the
weights defined in the distWtsList list. Each measurement is partnered
with one weight in the list. Weight/measurement associations are set
in the order which the weights are recorded. The latest received
measurement is always partnered with the first weight in the list.
Super–average = [∑ (measurementi x weighti)] / 100, i = 1 to distHreqt
Default value: 40 30 20 10
Rec. value: 40 30 20 10
Eng. Rules: A supply weights to distHreqt values, highest value for latest
measurements. Choosing an arithmetic law enables to enhance latest
values while not putting too much weight upon the period of time
which might not be representative of the current trend.
Nortel confidential

missDistWt Class 3 V7
Description: Weight applied to missing Distance measurement.
The missing measurement is replaced by the latest received raw
measurement weighed by this corrective factor when calculating the
average MS–BTS distance.
The range of permitted values makes missing distance measurements
not favored.
Default value: 110
Rec. value: TBD
Eng. Rules: The higher the value is, the higher the missing measurement will be
weighted.
Nortel confidential

5.11. HANDOVER (GLOBAL) PARAMETERS
bts time between HO configuration Class 3 V9

Description: Whether the hoPingpongTimeRejection timer can be used at bts level
when processing handovers
Value range: [0 / 1]
“0”:The timer is disabled.
“1”:The timer is used.
Object: bts
Default value: 0
Rec. value: 1
Used in: Minimum time between Handover
General protection against HO ping-pong (from V12)
Eng. Rules: New semantic in V12 in order to restore the minimum time between
HO feature (TF218, V9):
timeBetweenHOconfiguration = used
bts time between HO configuration = 1
ho Pingpong combinaison = (all, allPBGT)
ho Pingpong Time Rejection > 0
forced handover algo Class 3 V9

Description: Minimum signal strength level received by the mobiles to be granted
access to a neighbor cell in case of forced handover
Value range: [less than -110, -110 to -109, ..., -49 to -48, more than -48] dBm
Object: adjacentCellHandover
Default value: less than -110
Rec. value: = rxLevMinCell -1
Used in: Forced Handover
Eng. Rules: The neighbour cell eligibility criterion for forced handover compares
the Rxlev received by the mobile from the neighbour cells with the
value of "forced handover algo". If the Rxlev is greater than "forced
handover algo", then the forced handover is triggered. Therefore :
the higher the value of "forced handover algo" parameter, the
less efficient the forced handover feature, because fewer mobiles
will comply with the eligibility criterion. The mobiles who are
located too far away from the strongest neighbour cell will be
kept by the network on the current cell. So, it will take longer to
empty the cell because the operator has to wait for all mobiles to
move around and get closer to a neighbour cell. Note that it does
not make sense to set "forced handover algo" to a higher value
than "rxLevMinCell", although nothing prevents from doing so.
the smaller the value of "forced handover algo" parameter, the
faster mobiles will be forced out of the current cell. On the
downside, if "forced handover algo" is significantly lower than
"rxlevMinCell", quality of service for the mobile on the destination
cell will be poorer with a risk, ultimately, of call drop.
Nortel confidential

Therefore a compromise should be found, and BPUG recommends

that forced handover algo = RxlevMinCell - 1dB. This is only a
recommendation. A different value may be chosen by the customer.
handOver from signalling channel Class 3 V7

Description: Authorization to perform intercell handovers on signalling channels
(SDCCH or TCH in signalling mode)
Value range: [enabled / disabled]
Default value: disabled
Type: DP, Design
Rec. value: disabled
Used in: Direct TCH Allocation and Handover Algorithms
Eng. Rules: It is recommended to enable this feature when queuing is activated.
hoMargin Class 3 V7
Description: Margin to use for PBGT handovers to avoid subsequent handover, in
PBGT formula
Value range: [-63 to 63] dB
Object: adjacentCellHandOver
Default value: 4
Rec. value: between 4 and 6 for small cells
(4 in an 1X1 pattern, 5 or 6 otherwise),
5 for large cells.
Used in: Handovers
Handover for traffic reasons (from V12)
Define eligible neighbor cells for intercell handover (except directed
retry)
Eng. Rules: As a general rule, this parameter enables to harden access to a new
cell in order to avoid a subsequent return to the current cell (provided
rxLevMinCell is set to its minimal value and does not already take into
account ping-pong handover protection).
The value of this hoMargin must be correlated to the window size
value to keep a low ping-pong probability. In case of ping-pong,
handover hoMargin value must be incremented, and the window size
value must be decremented.
For a dual Band Network where one frequency band is privileged, it is
advised to increase this value in neighbouring objects with a
frequency belonging to the low priority frequency band. Thus, these
neighbours will be underprivileged.
Nortel confidential

hoMarginBeg Class 3 V11

Description: Margin that is added to hoMargin, concentAlgoExtRxLev,
amrDirectAllocRxLevUL, amrDirectAllocRxLevDL,
amrDirectAllocIntRxLevUL, amrDirectAllocRxLevDL,
bizonePowerOffset, until rxLevHreqave for short averaging algorithm
in order to compensate the lack of reliable measurements
This parameter is coupled with hoMargin, concentAlgoExtRxLev,
amrDirectAllocRxLevUL, amrDirectAllocRxLevDL,
amrDirectAllocIntRxLevUL, amrDirectAllocRxLevDL,
bizonePowerOffset and rxLevHreqaveBeg.
Value range: [0 to 63] dB
Object: bts
Default value: 4 dB
Rec. value: 4 dB
2 dB with Automatic Handover Adaptation
Used in: Handovers
Eng. Rules:
architecture.
hoMarginDist Class 3 V8
Description: Margin to be used for Distance Handovers
Rec. value: - 2 dB
Depends on the environment and on the value of the
msRangeMax Threshold.
Used in: Handover condition for leaving a cell on distance
retry)
Eng. Rules: Because the priority of the handover on Distance cause is lower than
the Quality and Strength causes, it is performed while the quality and
the signal strength on the current cell are still acceptable. Setting a
negative value decreases the interference.
L CAUTION! PBGT hoMargin in the target cell should be set in order to avoid a
ping-pong handover. For a dual Band Network where one frequency
band is privileged, it is advised to increase this value in neighbouring
objects with a frequency belonging to the low priority frequency band.
Thus, these neighbours will be underprivileged.
Nortel confidential

hoMarginRxLev Class 3 V8
Description: Margin to be used for signal strength Handovers
Value range: [- 63 to 63] dB
Rec. value: From 3 to 6 dB in urban environment, from 1 to 3 in rural
environment. Depends on the environment and the value of
lRxLevXXH. threshold.
Used in: Handovers
retry)
Eng. Rules: In rural environments, the hoMargin value on signal strength should
be between 1 and 3.
On the contrary, due to fast radio signal variations in urban
environments, this criteria must be selective to allow good reactivity.
Furthermore, this criteria can be selective due to site density in urban
environments.
The value of this hoMargin must be correlated to the window size
value to keep a low ping-pong probability. In case of ping-pong
handover, hoMargin value must be incremented, and the window size
value must be decremented.
This parameter, defined per neighbor, is used to select and sort
neighbors.
The setting of hoMarginRxLev depends of the gap between
rxLevMinCell and lRxLevXXH. The higher the difference between
these two values is, the higher the hoMarginRxLev.
advised to increase this value in neighbouring objects with a
frequency belonging to the low priority frequency band. Thus, these
neighbours will be underprivileged.
hoMarginRxQual Class 3 V8
Description: Margin to be used for Signal Quality Handovers
Rec. value: in [- 2; 0] without SFH,
in [1; (hoMargin - 2)] with SFH (#2 or 3)
Used in: Handovers
retry)
Eng. Rules: Handover cause on Signal Quality: case where access to another cell
should be encouraged, provided target cell field strength is not much
lower than the current one. If bad quality remains there is a risk of
return handover but there is nothing much to be done.
Nortel confidential

LCAUTION! PBGT hoMargin in target cell should be set in order to avoid a ping-
pong handover. This parameter, defined per neighbor, is used to
select and sort neighbors. For a dual Band Network where one
frequency band is privileged, it is advised to increase this value in
neighbouring objects with a frequency belonging to the low priority
frequency band. Thus, these neighbours will be underprivileged.
hoMarginTrafficOffset Class 3 V12

Description: Minimum signal strength margin with the serving cell that allows to
select the best neighbor cell when a handover is triggered for overload
reasons
Default value: 0 dB
Rec. value: 6 dB (if overlapping exists)
Used in: Handovers
Eng. Rules: Since the HO for traffic reasons uses the PBGT HO procedure, the
parameter powerBudgetInterCell shall be “enabled”.
It is advised to combine the HO for traffic reason with the feature HO
decision according to priority and Load.
This parameter shall be set at a value which guarantees that cell
overlapping exists with (hoMargin -hoMarginTrafficOffset).
See Paragraph 2.5k9 for more details.
When set to “0”, handovers for traffic reasons are not allowed in the
adjacent cell (the PBGT HO is done before because it has a higher
priority than the HO for traffic).
LCAUTION Only applicable to BTSs equipped with non mixed DCU4, or DRX
boards
hoPingpongCombination Class3 V12

Description: List of couples of causes (HOInitialCause and HONonEssentialCause)
indicating the causes of ping-pong handovers in the overlapping areas
The following causes are defined with regard to the neighboring cell:
HOInitialCause indicates the essential handover cause which leads
to enter the neighbor cell (cause of incoming handover).
HONonEssentialCause indicates the non-essential handover
cause which leads to leave the cell (cause of outgoing handover).
This parameter defines the combination for which the
HOPingpongTimeRejection attribute is used.
Value range: [rxQual, rxLev, distance, powerBudget, capture, directedRetry, OaM,
traffic, all, allCapture, allPowerBudget, AMRquality]
Default value:
Rec. value: (all, PBGT)
Used in: General protection against HO ping-pong (from V12)
Nortel confidential

Eng. Rules: This parameter shall be known by the new BSC (whatever the type of
HO is intra or inter BSC) ; so, it must be defined at the “entering cell”
(relatively to the first HO of the combination) level, for the
neighbouring cell (adjacentCellHandover object) corresponding to the
“left cell” (still relatively to the first HO of the combination).
Example: if you perform a handover from cell A to cell B for quality
reason and you want to protect against pingpong HO for PBGT
reason (from B to A), you have to declare (rxQual, PBGT) as one of
the forbidden handover combinations at cell B level (for the
neighbouring cell A).
Note: The hoPingpongCombination list can hold up to 4 couples of causes.
LCAUTION! No protection against intracell or interzone pingpongHO
No protection against pingpong HO between more than 2 cells except
for allcapture / all PBGT causes.
Directed retry can only be an initial cause.
timeBetweenHOConfiguration and bts Time Between HO
configuration shall be set accordingly in order for the feature to be
activated.
hoPingpongTimeRejection Class 3 V12

Description: Time before a new handover attempt can be triggered
Refer to bsc object timeBetweenHOConfiguration and bts object bts
time between HO configuration attributes in this Dictionary of
Parameters for this timer activation.
Refer to adjacentCellHandOver object HOPingpongCombination
attribute in this Dictionary of Parameters for the combinations for
which this timer applies.
To avoid ping-pong handovers this new timer is started after a
successful handover. Up to the expiration of this timer, the receipt of
HANDOVER INDICATION message is ignored.
Value range: [0 to 60] s
Default value: 30 s
Rec. value: between 8 and 30 s
Used in: General protection against HO ping-pong (from V12)
Eng. Rules: The value of “HOPingpongTimeRejection” may be between 8 and 30
to have a real impact. The following rule can be applied:
HOPingpongTimeRejection = 50% TCH effective occupancy average
in a cell.
If the rescue handovers are disabled in the network a too high value
can result in dropped calls.
The value depends on the speed of the mobile, the size of the cell and
the type of cell (micro-micro etc).
For an area where there are ping-pong handovers on “Quality” cause
(the first HO occurs on “Quality” reason, the second one on PBGT),
the value corresponds to the distance between the interference point
and the limit of the cell.
Care must be taken for small cells with high speed mobiles.
See also chapter Minimum Time Between Handover
Nortel confidential

hoSecondBestCellConfiguration Class 3 V9
Description: Number of neighbor cells in which the BSC immediately attempts to
perform a new handover when the previous handover attempt failed
with return to the old channel
Giving the attribute a value greater than 2 allows the BSC to renew
the handover request without waiting for a new set of radio
measurements (the first attempt is included in this count). The same
list of neighbor eligible cells is used to process the request (no new list
is provided by the BTS).
Object: bsc
Default value: 3
Type: DP, Design
Rec. value: 3
Used in: Handover to 2nd best candidate when return to old channel
Eng. Rules: The value 1 means no new attempt after a handover failure, 2 means
one new attempt and 3 corresponds to another new attempt if the first
new attempt has failed. The recommended value optimizes the
handover completion rate.
Comment about the process: when all handover attempts have failed,
the mobile returns on the previous channel. The measurement history
is then complety lost, and the BTS will wait until the next (HReqAve x
HReqt) period to relaunch a handover request.
See also chapter Directed Retry Handover Benefit
hoTraffic Class 3 V12

Description: Whether handovers for traffic reasons at bts level are allowed.
Value range: [disabled / enabled]
Object: bts
Default value: enabled
Rec. value: enabled
Used in: Handover for traffic reasons (from V12)
Eng. Rules: “enabled” will be effective only if it is also “enabled” for the bsc object.
In order to activate the feature “handover decision according to
adjacent cell priority and load” (TF716), either hoTraffic shall be
“enabled” or btsMSAccessClassBarringFunction shall be “enabled”
(with also bscMSAccessClassBarringFunction).
See parameter hoMarginTrafficOffset
hoTraffic Class 3 V12

Description: Whether handovers for traffic reasons at bsc level are allowed.
Object: bsc
Nortel confidential

Rec. value: enabled (only if “hot spot”cells linked to the BSC)

Used in: Handover for traffic reasons (from V12)
Eng. Rules: See parameter hoMarginTrafficOffset
incomingHandOver Class 3 V7
Description: Whether incoming handovers are allowed in a cell.
Type: DP
Rec. value: enabled
Used in:
Eng. Rules:
msTxPwrMax Class 3 V7
Description: Maximum MS transmission power in a serving cell. It is equal to
msTxPwrMaxCCH in a GSM 900 network.
Value range: [5 to 43, by steps of 2] dBm (GSM 900, GSM850, GSM-R, GSM850-
GSM1900 and GSM 900 - GSM 1800 networks)
[0 to 36, by steps of 2] dBm (GSM 1800, and GSM 1800 - GSM 900
networks)
[0 to 33] dBm (GSM 1900 network)
[0 to 33] dBm (E-GSM network and 1900-850 network)
[0 to 33] dBm (GSM850 network)
Object: bts
Default value: Typical value of 33 dBm for GSM 900 handhelds and 30 dBm for
GSM 1800 and 1900 handhelds
Rec. value: 33 dBm for GSM 900 in urban environment
39 dBm for GSM 900 in rural environment handhelds
30 dBm for GSM 1800 and 1900 handhelds
33 dBm for GSM 850s
Used in: Accuracy related to measurements
General formulas
Forced Handover
One shot power control
Power control on mobile side
Eng. Rules: We must have msTxPwrMax = msTxPwrMaxCCH for GSM 900
Networks and msTxPwrMaxCCH ≤ msTxPwrMax for GSM 1800 and
1900 Networks (check done at OMC-R). This parameter is adapted to
mobile classes taken into account in Network Design.
Nortel confidential

msTxPwrMaxCell Class 3 V7
Description: Maximum MS transmission power in a neighbor cell. It is equal to
msTxPwrMaxCCH when the cell is declared as a serving cell on the
network (the value must be checked by users).
Value range: [5 to 43, by steps of 2] dBm (GSM 900, GSM850, GSM-R and GSM
900 - GSM 1800 networks)
[0 to 36, by steps of 2] dBm (GSM 1800 network
and GSM 1800 - GSM 900)
[0 to 33] dBm (GSM 1900 network)
[0 to 33] dBm (E-GSM network)
[0 to 33] dBm (GSM 1900-850 network)
Default value: Typical value of 33 dBm for GSM 900/850 handhelds and 30 dBm for
GSM 1800 and 1900 handhelds
Rec. value: msTxPwrMaxCell = msTxPwrMaxCCCH of the current cell
Used in: General formulas
Handovers screening
Directed Retry Handover: BTS (or distant) mode
Forced Handover
retry)
Power control on mobile side
See Paragraph 2.5.1 and Paragraph 2.7.
Eng. Rules: If this value is higher than the actual MS classmark, then MS will apply
its own capability.
Remark: If the cell is used as a neighbor cell of another serving cell in the
network, msTxPwrMaxCell should be identical to the
msTxPwrMaxCCH power defined for the corresponding
adjacentCellHandOver object (the values must be checked by users).
Nortel confidential

offsetLoad Class 3 V12

Description: Load offset applied by the bsc in the cell selection process of the
Handover algorithm.
Default value: 0 dB
Rec. value: 3 dB
offsetLoad ≥ hoMarginTrafficOffset (Handovers for traffic reason
feature activated)
Used in: Handover decision according to adjacent cell priorities and load (from
V12)
Eng. Rules: When set to “0”, no offset is effective.
This parameter is set to “0” for the cells that do not belong to the
related bsc object.
This parameter allows to put a disadvantage to overloaded eligible
cells for HO (for cells with the same offsetPriority).
In order to take into account this parameter, the overload detection
must be activated ; so either hoTraffic shall be “enabled” (bsc and bts
objects) or btsMSAccessClassBarringFunction shall be “enabled”
(with also bscMSAccessClassBarringFunction).
A bad offset load parameter tuning can induce a risk of ping-pong HO
or longer handover procedures; so, it is advised to set the “General
protection against HO ping-pong” feature with
HOPingpongCombination including (traffic, all PBGT).
See also chapter Handover for Traffic Reasons Activation Guideline.
offsetPriority Class 3 V12

Description: Priority offset applied by the bsc to the cell selection process in the
Handover algorithm
Default value: 1
Rec. value: 1
Used in: Handover decision according to adjacent cell priorities and load (from
V12)
Eng. Rules: “1” is the highest priority.
This parameter allows to classify eligible cells according to its value;
so, it is used to optimize the traffic distribution between layers.
See also chapter DualBand Networks.
Nortel confidential

powerBudgetInterCell Class 3 V7
Description: Authorization to perform intercell handovers for power budget
Rec. value: enabled
Used in: Handovers screening
Eng. Rules: Handover on PBGT should be enabled, because for an optimized
network it ensures the best quality of service.
runHandOver Class 3 V7
Description: Number of Measurement Results messages that must be received
before the handover algorithm in a cell is triggered
Value range: [1 to 31] SACCH frames (1 unit = 480 ms on TCHs, 470 ms on
SDCCHs)
Object: bts
Default value: 1
Type: DP, System
Rec. value: 1
Used in: Handovers
Microcellular Algo type A
Protection against RunHandover=1
Eng. Rules: Should be run as often as possible, main impact is upon BSS load.
The V11 feature protection against runHandover=1 allows some
protections in order to avoid that the setting of this parameter to 1
leads some overload problems (SICD overload)..
Therefore, runHandOver may be set to 1 in some environments where
the reactivity is crucial (microcell, high-speed environment). So from
V11, it is recommended to set this parameter to 1. However, this
parameter setting must be done in accordance with the value of
handover thresholds, margins and timers.
See also chapter Impact of the Averaging on the Handovers and
chapter Street Corner Environment
Nortel confidential

rxLevMinCell Class 3 V7
Description: Minimum signal strength level received by MS for being granted
access to a neighbor cell
Default value: - 95 to -94 dBm (GSM 900 & 850), - 93 to - 92 (GSM 1800 & 1900)
Rec. value: - 95 to - 94 dBm (GSM 900 & 850)
- 93 to - 92 dBm (GSM 1800& 1900) in urban environment
RxLevMinCell = lRxLevDLH if HOmargin ≥ 0 in rural environment
Handovers screening
retry)
Eng. Rules: A method to estimate this value is to use MS sensitivity (-104 dBm in
GSM 900 for handheld, and -102 dBm in GSM 1800/1900 for
handheld, otherwise -104 dBm) and applying a margin to it. However,
if most of communications are handled in an indoor environment, or
overlap between cell coverage is not sufficient, these recommended
values can be decreased.
advised to set this parameter to a lower value in neighbour cells
belonging to the priority frequency band. Thus, this band will be
preferred. However, it may be greater than the value rxLevAccessMin.
Thus the recommended value is -99 to -98 dBm (GSM900) or -97 to -
96 dBm (GSM1800) for neighbour cells belonging to the priority
frequency band.
Studies have shown that the subjective quality depends on the way
erroneous bits are spread into each frame. Experiments have shown
that with frequency hopping in TU3 (Typical urban at 3 Km/h) up to
Rxqual = 5 the subjective quality seems to be good, on the other hand
without frequency hopping Rxqual = 4 seems to be the maximum
value for which subjective quality is good.
The table below gives examples of the margins that could be taken
into account for an infinite C/I and for different mobile speeds.
t 50 km/h u 50 km/h - t 80 km/h u 80 km/h

margin with FH 2 dB 2 dB 2 dB
margin without FH 5 dB 4 dB - 2 dB 2 dB
And that other table below shows the different margins that could be
taken into account in a slow mobile area depending of the C/I.
C/I = 35 C/I = 20 C/I = 15

margin with FH 2 dB 3 dB 4 dB
margin without FH 5 dB 6 dB 10 dB
See also chapter Directed Retry Handover Benefit and chapter

DualBand Networks.
Nortel confidential

synchronized Class 3 V7
Description: Whether the neighbor cell and the associated serving cell are
synchronous, that is attached to the same BTS
Value range: [not synchronized cells / synchronized cells / pre sync HO with timing
advance / pre sync HO, default timing advance]
“not synchronized cells”: the neighbor cell and the serving cell are
not attached to the same BTS.
“synchronized cells”: the neighbor cell and the serving cell are
attached to the same BTS
“pre sync HO with timing advance”: the handover procedure
between the neighbor cell and the serving cell is pre–synchronized
with the real Time Advance.
“pre sync HO, default timing advance”: a pre–defined timing
advance is used in the pre–synchronized handover procedure
between the serving cell and the neighbor cell. Refer to
preSynchroTimingAdvance parameter.
Default value: not synchronized cells
Used in: Pre-synchronized HO
Handover Algorithms on the Mobile Side
Eng. Rules: It is recommended to use pre-synchronized HO in microcellular
environment because in small cells the timing advance when
handovers are triggered is generally a low value (less than 3).
It is also interesting to use this feature for determined path such as
railways, highways, and tunnels where handovers between two cells
happen always at the same place.
See also chapter Synchronized HO versus Not Synchronized HO
timeBetweenHOConfiguration Class 3 V9
Description: Whether the HOPingpongTimeRejection timer can be used in a BSS
when processing handovers. Refer to bts object bts time between HO
configuration and adjacentCellHandOver object
HOPingpongTimeRejection attributes in this Dictionary of Parameters.
Value range: [used / not used]
Object: bsc
Default value: used
Type: DP, Design
Rec. value: used
Used in: Power Budget Handover
General protection against HO ping-pong (from V12)
Eng. Rules: see Engineering Rules for the parameter bts time Between HO
Configuration.
See also chapter Minimum Time Between Handover and chapter
Directed Retry Handover Benefit.
Nortel confidential

5.12. INTRACELL HANDOVER PARAMETERS
intraCell Class 3 V7
Description: Whether intra–bts handovers on TCH are allowed in a cell for
interference reasons or Cell Tiering reasons
Value range: [cellTieringHandover / intraCellHandover / handoverNotAllowed]
cellTieringHandover: the intraBTS handovers are allowed for
CellTiering reason
intraCellHandover: the intraBTS handovers are allowed for
interference reason
handoverNotAllowed: the intra bts handovers are not allowed
Default value: handoverNotAllowed
Type: DP, Design
Rec. value: cellTieringHandover
Used in: Intracell Handover decision for signal quality
Eng. Rules: For mono-TRX cell, do not enable intracell handover
(handoverNotAllowed).
As the MS power is not checked before performing an intracell
handover, it is not advised to enable this feature as intraCellHandover.
It would lead to a high ratio of intracell handover.
In V7, the resource allocator does not classify free TCH resources
according to their interference level. From V8, the channel is selected
from the best not empty pool.
To enable “tiering”, the cell tiering conditions shall be fulfilled and the
cell tiering advantages shall be estimated as well (see chapter
Automatic cell tiering (from V12) and hoMarginTiering parameter).
intraCellSDCCH Class 3 V8
Description: Whether intraBTS handovers on SDCCH are authorized in a cell for
interference reasons
Eng. Rules: None except system ability.
Note that, some mobiles have been reported to drop the call when
that feature is performed.
Nortel confidential

rxLevDLIH Class 3 V7
Description: Maximum interference level in BTS–to–MS direction, beyond which an
intraCell handover may be triggered
Value range: [less than -110, -110 to -109,..., -49 to -48, more than -48] dBm
Default value: -85 to -84 dBm
Rec. value: -85 to -84 dBm
Eng. Rules:
LCAUTION! Path balance must be looked for this threshold parameter setting.
rxLevULIH Class 3 V7
Description: Maximum interference level in MS–to–BTS direction, beyond which an
intra cell handover may be triggered
Value range: [less than -110, -110 to -109, ... , -49 to -48, more than -48] dBm.
Eng. Rules:
LCAUTION! Path balance must be looked for this threshold parameter setting.
Nortel confidential

rxQualDLIH Class 3 V12

Description: Bit error rate threshold in BTS-to-MS direction for intracell handover,
above which a handover may be triggered.
Value range: [less than 0.2, 0.2 to 0.4, 0.4 to 0.8, ... , 6.4 to 12.8, more than 12.8] %
Default value: 1.6 to 3.2 %
Rec. value: rxQualDLIH ≤ lRxQualDLH
Eng. Rules: From V12, intracell HO for signal quality uses a different threshold
than the intercell one and intracell HO can only use either hopping
channels having low interference or non hopping channels having low
interference. This should improve the voice quality and the
performance.
The possible drawback could be to increase queuing at BSC level for
networks experiencing interferences.
To favor intracell HO for quality (compared to intercell HO for quality),
the following rule shall be satisfied: rxQualDLIH < lRxQualDLH.
From V12, the intracell HO has a lower priority than the intercell HO
for quality.
rxQualULIH Class 3 V12

Description: Bit error rate threshold in MS-to-BTS direction for intracell handover,
above which a handover may be triggered.
Rec. value: rxQualULIH ≤ lRxQualULH
Eng. Rules: From V12, intracell HO for signal quality uses a differentthreshold than
the intercell one and intracell HO can only use either hopping
channels having low interference or non hopping channels having low
interference. This should improve the voice quality and the
performance.
The possible drawback could be to increase queuing at BSC level for
networks experiencing interferences.
To favor intracell HO for quality (compared to intercell HO for quality),
the following rule shall be satisfied: rxQualULIH < lRxQualULH.
From V12, the intracell HO has a lower priority than the intercell HO
for quality.
Nortel confidential

5.13. INTERCELL HANDOVER THRESHOLD PARAMETERS
lRxLevDLH Class 3 V7
Description: Signal strength threshold in BTS–to–MS direction, below which a
handover may be triggered
Default value: -101 to -100 dBm (GSM 900) / -99 to -98 dBm (GSM1800/1900)
Rec. value: -95 to -94 dBm in urban environment (900 MHz or 850 MHz)
-101 to -100 dBm in rural environment (900 MHz or 850 MHz)
Used in: Handover condition for leaving a cell on rxlev
retry)
Eng. Rules: This threshold must be set from the MS sensitivity. A margin must be
taken to consider shadowing, fast fading and MS measurement
accuracy. At least, a 3 dB margin can be taken into account in a rural
environment and a 10 dB margin in an urban environment.
LCAUTION! where the cell is declared as a neighbor, we should have: lRxLevDLH
< rxlevMinCell, and path balance must be considered for this
threshold parameter setting.
See also chapter lRxlevDLH and lRxlevULH Definition.
lRxLevULH Class 3 V7
Description: Signal strength threshold in MS–to–BTS direction, below which a
handover may be triggered
Default value: -101 to -100 dBm (GSM 900) / -99 to -98 dBm (GSM 1800/1900)
Rec. value: -95 to -94 dBm in urban environment (900 MHz or 850 MHz)
-101 to -100 dBm in rural environment (900 MHz or 850 MHz)
Used in: Handover condition for leaving a cell on rxlev
Eng. Rules: The recommended values given above correspond to the worst case
BTS (e-cell). An e-cell has -104 dBm Rx sensitivity in all frequency
bands and diversity is not applicable, thus leading to "-95 to -94" for
urban environments and "-101 to -100" for rural environments when
applying a 3dB margin in a rural environment and a 10 dB margin in
an urban environment. In fact, these thresholds depend on BTS
sensitivity. Values should be increased if one of the following points is
verified:
the thresholds on quality are permissive
run-handover 3 scarce
mobile speed is high
initial tuning causes frequent level strength handover failure rate
Nortel confidential

At least, a 3 dB margin can be taken into account in a rural

environment and a 10 dB margin in an urban environment.
LCAUTION! where the cell is declared as a neighbor, we should have: lRxLevULH

< rxLevMinCell, and path balance must be considered for this
threshold parameter setting.
See also chapter lRxlevDLH and lRxlevULH Definition.
lRxQualDLH Class 3 V7
Description: Bit error rate threshold in BTS–to–MS direction, above which an inter
cell handover may be triggered
Rec. value: 1.6 to 3.2 % (4 in rxqual GSM unit) without frequency hopping.
See Engineering Rules in case of frequency hopping.
Used in: Handover condition for leaving a cell on rxqual
Eng. Rules: According to some experiments and studies, 4 in GSM unit is the
upper limit for TU3 no hopping, while 5 in GSM unit for TU3 hopping.
Suggested values become 4 in GSM unit (no frequency hopping or
MS speed > 80km/h) and 5 in GSM unit (frequency hopping and low
urban speed). High BER rate for threshold is dangerous (risk of
handover failure). On the contrary, if a tight rxqual threshold is linked
with a short averaging period, the risk is that a single bad quality
report will affect the whole result (ie: if 8 samples without weighting
and a threshold of 2 in GSM unit: if 7 of these samples are 2 in GSM
unit and 1 of them is 5 in GSM unit, handover decision will be taken
on a wrong basis). Experience shows whatever the MS speed, rxQual
= 6 does not provide a comfortable voice quality.
The average in the above is equal to:
(7 * 0.57 + 4.53) B 8 = 1.065 greater than 0.57 (2 in GSM unit).
In case of using synthesized frequency hopping, this threshold has to
be increased in order to limit the increase of the number of handover
on quality criteria.
In a 1X1 pattern, it is advised to set this value to 5 or 6 (3.2 to 6.4 %
or 6.4 to 12.8 %).
In case of a 1X3 pattern, the recommended value is 4 or 5 (1.6 to 3.2
% or 3.2 to 6.4 %).
DTX is often used with Frequency Hopping. There are less
measurement reports with DTX, and thus the RxQual_average may
be less reliable. But no degradation was observed when using both
features therefore there is no need to disable handovers on quality
criteria in this case.
Nortel confidential

lRxQualULH Class 3 V7
Description: Bit error rate threshold in MS–to–BTS direction, above which an inter
cell handover may be triggered
Rec. value: 1.6 to 3.2 % (4 rxqual GSM unit) without frequency hopping.
See Engineering Rules in case of frequency hopping.
Used in: Handover condition for leaving a cell on rxqual
Eng. Rules: According to some experiments and studies, 4 in GSM unit is the
upper limit for TU3 no hopping while 5 in GSM unit for TU3 hopping.
Suggested value becomes 4 in GSM unit (no frequency hopping or
MS speed > 80km/h) and 5 in GSM unit (frequency hopping and low
urban speed). High BER rate for threshold is dangerous (risk of
handover failure). On the contrary, if a tight rxqual threshold is linked
with a short averaging period, the risk is that a single bad quality
report will affect the whole result (ie: if 8 samples without weighting
and a threshold of 2: if 7 of these samples are 2 and 1 of them is 5,
handover decision will be taken on the wrong basis).
In case of using synthesized frequency hopping, this threshold has to
be increased in order to limit the increase of the number of handover
on quality criteria.
In a 1X1 pattern, it is advised to set this value to 5 or 6 (3.2 to 6.4 %
or 6.4 to 12.8 %).
In case of a 1X3 pattern, the recommended value is 4 or 5 (1.6 to 3.2
% or 3.2 to 6.4 %).
DTX is often used with Frequency Hopping. There are less
measurement reports with DTX, and thus the RxQual_average may
be less reliable. But no degradation was observed when using both
features therefore there is no need to disable handovers on quality
criteria in this case.
Nortel confidential

rxLevDLPBGT Class 3 V11

Description: Downlink signal strength threshold above which handovers for power
budget are inhibited
In certain issues, the operator may want to prevent handover for
power budget in case of the received level in the serving cell is good
enough so that a handover would not improve the situation.
This parameter shall be set such as rxLevDLPBGT > lRxLevDLH.
Value range: [less than -110, -110 to -109,..., -49 to -48, more than -48] dBm
Default value: more than -48
Rec. value: TBD
Maximum RxLev for Power Budget
Eng. Rules: rxLevDLPBGT > lRxLevDLH
This parameter has to be managed carefully because it can prevent
all the handover for power budget when set to less than -110.
Moreover, the setting of this parameter has to be done with the help of
some radio measurement campaigns.
This parameter shall be disabled by setting the value to more than –
48 (dBm).
architecture. It shall be disabled for DCU2 architecture.
Nortel confidential

5.14. HANDOVER FOR MICROCELLULAR NETWORK

PARAMETERS
cellType Class 3 V7
Description: Type of the adjacent cell
Value range: [normalType / umbrellaType / microType]
Default value: normalType
Type: DP, Design
Rec. value: normalType
Used in: Microcellular Algo type A
Eng. Rules: To run a capture handover (umbrella to micro) on a neighbor, which
must be microType, the bts must be declared as umbrellaType. It is
possible to manage a three layer network by declaring cell A and cell
B as umbrellaType, neighbor B and neighbor C as microType for cell
A, neighbor A as umbrellaType and neighbor C as microType for cell
B, and finally neighbor B as umbrellaType for cell C.
See also chapter Minimum Time Between Handover
cellType Class 3 V7
Description: Type of the serving cell
Value range: [normalType / umbrellaType / microType]
Object: bts
Default value: normalType
Type: DP, Design
Rec. value: normalType
Eng. Rules: To run a capture handover (umbrella to micro) on a neighbor, which
must be microType, the bts must be declared as an umbrellaType. It
is possible to manage a three layer network by declaring cell A and
cell B as umbrellaType, neighbor B and neighbor C as microType for
cell A, neighbor A as umbrellaType and neighbor C as microType for
cell B, and finally neighbor B as umbrellaType for cell C.
Remark: The adjacent cell umbrella Ref attribute is defined at the OMC-R if the
cell is a microcell (cellType) and directed retry handovers are
processed in BSC mode (directed-RetryModeUsed).
Nortel confidential

microCellCaptureTimer Class 3 V8
Description: Time used to confirm a capture (signal strength stability) when using
microcell Algorithm type A
Value range: Time = N multiplied by runHandOver.
According to microCellCaptureTimer value, N values are the
following:
[0 to 249] N = [0 to 249]
250 N = 512
251 N = 1024
252 N = 2048
253 N = 4096
254 N = 8192
255 N = 16384
Default value: 0
Type: DP, Design
Rec. value: 8s, whatever runHandOver value
(e.g. if runHandOver = 2 Æ N = 8, if runHandOver = 1 Æ N = 16)
Eng. Rules: Experiments done in urban areas show that a timer of 8 seconds to 10
seconds allows a better use of the capture.
See also chapter Impact of the Averaging on the Handovers.
microCellStability Class 3 V8
Description: Strength Level Stability Criterion for Capture Algorithm A
Default value: 10 dB
Type: DP, Design
Rec. value: 63 dB
Eng. Rules: To allow handovers on capture this parameter has to be set at a value
greater than 0. A value of microCellStability equal to 63 dB has to be
set first, because with such a value, the stability constraints are
always verified.
The value of this parameter can then be decreased case by case.
Nortel confidential

5.15. DISTANCE MANAGEMENT PARAMETERS
callClearing Class 3 V7
Description: Maximum distance between MS and BTS before call is cleared
It is greater than msRangeMax.
This distance defines the cell maximum coverage area.
Value range: [2 to 35] km (non-extended mode)
[2 to 120] km (extended mode)
Object: bts
Default value: 35 in non-extended mode, 90 in extended mode
Type: DP, Product
Rec. value: Depends on the environment, typical value = (1.5 * cell diameter)
+ 2 km or best cell distance coverage server
Generaly for non-extended mode: 7 km for urban, 35 km for rural
Used in: Call Clearing Process (run by BTS) (Cc)
Eng. Rules: The value should be related to the current cell coverage. A margin is
taken by using the 1.5 coefficient. A 2km margin is also considered to
compensate lack of mobile timing advance accuracy.
If the observation counter shows a high number of call clearings, it
may mean that handover parameters on that cell are too permissive or
badly tuned.
At the OMC-R, a control exists: callClearing > msRangeMax
extended cell Class 2 V9
Description: Whether the cell is extended (up to 120 km large) or not
The cell working mode governs the upper limit of the following
attribute values (refer to theses entries in the Dictionary):
callClearing, msRangeMax, and rndAccTimAdvThreshold
attributes of the bts object
concentAlgoExtMsRange and concentAlgoIntMsRange attributes
of the associated handOverControl object if the bts object
describes a concentric cell
Value range: [true (extended) / false (normal)]
Object: bts
Default value: false
Used in:
Eng. Rules: Extended cells will be used to reach mobiles that are far from the BTS
(in the case of sea shores and pleasure boats, for example).
In an extended cell, two consecutive time slots are reserved for each
channel. The capacity is then decreased.
LCAUTION! Up to V10, an extended cell cannot be concentric. Whatever the MS-
BTS distance is, two consecutive time slots are reserved on Air
interface.
See also chapter SDCCH Dimensioning an TDMA Models.
LCAUTION! GPRS/EDGE is not supported when extended cell feature is activated.
Nortel confidential

msRangeMax Class 3 V7
Description: Maximum MS–to–BTS distance beyond, which a handover may be
triggered. It can be set to 1 for a microcell and is less than callClearing
in all cases.

Default value: 34 in non-extended mode, 89 in extended mode
Rec. value: = callClearing - 1 km
Used in: Handover condition for leaving a cell on distance
Eng. Rules: If the associated serving cell is a concentric cell, the following
inequality, that is not checked by the system, must be true (refer to
this entry in the Dictionary):
concentAlgoExtMsRange ≤ concentAlgoIntMsRange ≤ msRangeMax
LCAUTION! callClearing > msRangeMax is controled at the OMC level. It must be

adapted to current cell extent in order to be an efficient preventive
handover. If value is too small, there is a big risk of ping-pong
handover.
LCAUTION! Due to lack of mobile timing advance accuracy this parameter must
not be set at a too low value (not < 2). Generaly for non-extended
mode (6 km for urban and 34 km for rural)
msBtsDistanceInterCell Class 3 V7
Description: Whether inter–bts handovers are allowed in a cell for distance
reasons
Rec. value: enabled
Handover condition for leaving a cell on distance
Eng. Rules: Due to the imprecision of some MS on Timing Advance (see chapter
Distance - timing advance conversion) and due to the delay spread in
a very urban environment, it is possible to set this parameter to
“disabled” (in an urban environment). However, for all cells with a
radius of more than 1 km, handover on distance must be authorized.
Nortel confidential

preSynchroTimingAdvance Class 3 V10

Description: Pre-defined timing advance used in a pre-synchronized handover
procedure between the serving cell and this neighbor cell.
Value range: [1 to 35] (km)
Default value: Refer to parameter synchronized
Type: DP, Design
Used in: Pre-synchronized HO
Eng. Rules: This value of timing advance is used when the parameter
synchronized is set to “pre sync HO with timing advance”. A
predefined timing advance can be defined when phase 2 MSs always
handove from the serving cell to this neighbor cell approximately at
the same place (railway, highway).
If the parameter synchronized is set to “presyncho HO, default timing
advance”, the default TA value is “-1” (554 m).
If the parameter synchronized is set to “presyncho HO, with timing
advance”, the parameter preSynchroTimingAdvance must be tuned to
the estimated value of TA.
See also chapter Synchronized HO versus Not Synchronized HO.
LCAUTION! preSynchroTimingAdvance value is not controlled at the OMC-R
rndAccTimAdvThreshold Class 3 V8
Description: MS–to–BTS distance beyond which mobile access requests to a cell
are refused.
It defines the maximum timing advance value accepted.
The effective timing advance value is broadcast in the CHANNEL
REQUIRED message sent by the BTS to the BSC. If it is above the
user defined threshold, the BSC ignores the request.
Object: bts
Default value: 35 (non-extended cell), 90 (extended cell)
Rec. value: msRangeMax (= call clearing - 1km = 1.5* cell diameter + 2 km -1
km)
Generally for non-extended mode: 6 km for urban, 35 km for rural
Used in: Request access command process (RA)
Eng. Rules: The maximum authorized value will inhibit the feature.
By adjusting the value to the size of the cell (see recommended
value), parasite RACH (noise which is decoded by the system like a
RACH) are filtered. This avoids the unnecessary assigment of
SDCCH.
For example, for small cells, if the value is 35 km, almost 30% of the
RACHs are parasite. If the value is modified to 2, almost no parasites
RACH are detected.
Nortel confidential

runCallClear Class 3 V7
Description: Number of “Measurement Results” messages that must be received
before the call clearing algorithm in a cell is triggered
Value range: [1 to 31] SACCH frames (1 unit = 480 ms on TCHs, 470 ms on
SDCCHs)
Object: bts
Default value: 16
Type: DP, System
Rec. value: 16
Used in: Call Clearing Process (run by BTS) (Cc)
Eng. Rules: It is not necessary to run Cc too often, since those calls are going to
be ended anyway. Nevertheless, traffic out of a cell’s range interferes
on other cells or timeslots.
Nortel confidential

5.16. POWER CONTROL PARAMETERS
bsMsmtProcessingMode Class 2 V7
Description: Whether radio measurements collected by the mobiles for a cell are
processed by the BTS or the BSC
Value range: [preProcessedMeasurementReporting (BTS) /
basicMeasurementReporting (BSC)]
Object: bts
Default value: preProcessedMeasurementReporting
Type: DP, Product
Rec. value: preProcessedMeasurementReporting
Eng. Rules: Since radio measurements are always preprocessed by the BTS,
changing this attribute has no meaning.
bsPowerControl Class 3 V7
Description: Whether BTS transmission power control is allowed at cell level
Object: powerControl
Rec. value: enabled
Used in: Step by step Power control
Power Control (AMR)
Eng. Rules: Not useful for mono-TRX cells, because BTS power control on BCCH
frequency is not allowed.
LCAUTION! During a measurement field campaign, it can be normal to disable this
feature in order to have the real signal strength and not the adjusted
one.
bsTxPwrMax Class 3 V7
Description: Maximum theoretical level of BTS transmission power in a cell
The BSC relays the information to the mobiles in the Abis CELL
MODIFY REQUEST message.
Value range: [0 to 47] dBm
Default value: 43 dBm
Rec. value: depends on the equipment
Cabinet Output Power Setting
Nortel confidential

Eng. Rules: This power is used to calculate the cabinet output power. From V9, it
depends on the attribute “attenuation” of btsSiteManager objects (see
chapter Pr computation), because the value of the parameter
“attenuation” is then taken into account as DLU attenuation.
Remark: For a GSM 1900 network (standardIndicator of bts object set to
‘pcs1900’), the MD-R checks the following: bsTxPwrMax < 32 (dBm)
when an edge frequency is defined for the cell (i.e. if the value is
included in the cellAllocation attribute values).
Some bsTxPwrMax values are not compatible with the effective power
output by the BTS (see chapter Pr computation).
lRxLevDLP Class 3 V7
Description: Signal strength threshold in BTS–to–MS direction, below which the
power control function increases power. It is lower than uRxLevDLP.
Rec. value: -95 to -94 dBm (step by step)
-85 to -84 dBm (one shot)
Power Control (AMR)
Eng. Rules: The difference between lower and upper thresholds must be greater
or equal to max (powerIncrStrepSize, powerRedStepSize), because it
is controled at the OMC level.
lRxLevDLP > lRxLevDLH, up to V7, because power Control and
handover algorithms are decorrelated.
LCAUTION! In case the AMR power control algorithm is activated ( refer to the
amrReserved2 parameter) that parameter defines the threshold below
which the AMR power control is inhibited.
In that case the recommended values remain the same if the AMR
penetration is low, and the same + 2dB if the AMR penetration is high.
lRxLevULP Class 3 V7
Description: Signal strength threshold in MS–to–BTS direction, below which the
power control function increases power. It is lower than uRxLevULP.
Rec. value: -95 to -94 dBm (step by step)
-85 to -84 dBm (one shot)
Power Control (AMR)
Nortel confidential

Eng. Rules: lRxLevULP > lRxLevULH, up to V7, because power Control and
handover algorithms are decorrelated.
LCAUTION! In case the AMR power control algorithm is activated ( see
amrReserved2 parameter) that parameter defines the threshold below
which the AMR power control is inhibited.
In that case the recommended values remain the same if the AMR
penetration is low, and the same + 2dB if the AMR penetration is high.
lRxQualDLP Class 3 V7
Description: Bit error rate threshold in BTS–to–MS direction, above which the
power control function increases power. It is greater than or equal to
uRxQualDLP.
Default value: 0.4 to 0.8
Rec. value: 0.8 to 1.6 % (RxQual = 3 in GSM unit) without SFH
3.2 to 6.4 % (RxQual = 5 in GSM unit) with SFH
Power Control (AMR)
Eng. Rules: This value must be lower than lRxQualDLH in order to maintain
priority between power control and handover.
lRxQualULP Class 3 V7
Description: Bit error rate threshold in MS–to–BTS direction, above which the
power control function increases power. It is greater than or equal to
uRxQualULP.
Power Control (AMR)
Eng. Rules: This value must be lower than lRxQualULH in order to maintain
Nortel confidential

msTxPwrMax2ndBand Class 3 V12

Description: Maximum MS transmission power in the band 1 of the dualband cell
depending on the network type (BCCH is only defined in band 0)
Value range: [0 to 36] for GSM 900 – GSM 1800 (gsmdcs),
[5 to 43] for GSM 1800 – GSM 900 (dcsgsm)
[0 to 33] for GSM 850 – GSM 1900 (gsm850pcs)
[5 to 43] for GSM 1900 – GSM 850 (pcsgsm850)
for all in the steps of 2 + value = 33 for GSM 850 – GSM 1900
0..43 for other standardIndicator types
Object: bts
Default value: Typical value of 33 dBm for GSM 900 & 850 handhelds, 30 dBm for
GSM 1800 and 1900
Rec. value: 33 dBm for dcsgsm
30 dBm for gsmdcs & 850
Used in: Concentric/DualCoupling/DualBand Cell Handover
Eng. Rules: This parameter is only used for power control.
The attribute value is within the range [0 to 36] and even when the bts
object standardIndicator attribute is “gsmdcs”.
The attribute value is within the range [5 to 43] and odd when the bts
object standardIndicator attribute is “dcsgsm”.
new power control algorithm Class 3 V9

Description: Algorithm used by the BTS to control power in a cell
“step by step” value refers to the standard power control algorithm.
“one shot” value refers to the advanced power control algorithm.
“enhanced one shot “ value refers to the advanced power algorithm
used in connection with the handOverControl object
rxLevHreqaveBeg attribute used in the early handover mechanism.
Value range: [step by step / one shot / enhanced one shot]
Object: bts
Default value: one shot
Rec. value: one shot (if DCU2 boards)
enhanced one shot (otherwise)
Eng. Rules:
LCAUTION! “Enhanced one shot” is not supported with DCU2 boards or with a mix
of DCU2/DCU4 boards
Nortel confidential

powerIncrStepSizeDL Class 3 V14

Description: Increment step size for downlink power control.
Value range: [2, 30] dB
Default value: 4 dB
Rec. value: 4 dB
Eng. Rules: A high step is required to be reactive in increasing the power when
entering an area where propagation is not acceptable.
A higher step (6 dB) is recommended for specific networks or
environment (high speed trains for example).
The attribute powerIncrStepSizeDL must verify: lRxLevDLP +
powerIncrStepSizeDL ≤ uRxLevDLP
LCAUTION! Not used in one shot power control nor in AMR power control.
powerIncrStepSizeUL Class 3 V14

Description: Increment step size for uplink power control.
Default value: 4 dB
Rec. value: 4 dB
Eng. Rules: A high step is required to be reactive in increasing the power when
entering an area where propagation is not acceptable.
A higher step (6 dB) is recommended for specific networks or
environment (high speed trains for example).
The attribute powerIncrStepSizeUL must verify:lRxLevULP +
powerIncrStepSizeUL ≤ uRxLevULP
LCAUTION! Not used in one shot power control nor in AMR power control.
powerRedStepSizeDL Class 3 V14

Description: Decrement step size for downlink power control.
Default value: 2 dB
Rec. value: 2 dB
Eng. Rules: Small steps are enough to adapt two subsequent changes in quality
and strength. Moreover, calls become sensitive to low MS or BS
TxPower.
Nortel confidential

The attribute powerIncrStepSizeDL must verify: uRxLevDLP –

powerRedStepSizeDL ≥ lRxLevDLP
LCAUTION! Not used in one shot power control.
powerRedStepSizeUL Class 3 V14

Description: Decrement step size for uplink power control.
Default value: 2 dB
Rec. value: 2 dB
Eng. Rules: Small steps are enough to adapt two subsequent changes in quality
and strength. Moreover, calls become sensitive to low MS or BS
txPower.
The attribute powerRedStepSizeUL must verify: uRxLevULP –
powerRedStepSizeUL ≥ lRxLevULP
runPwrControl Class 3 V7
Description: Number of Measurement Results messages that must be received
before the power control algorithm in a cell is triggered.
Value range: [1 to 31] frames (1 unit = 480 ms on TCH, 470 ms on SDCCH)
Object: bts
Default value: 4
Type: DP, System
Rec. value: 2
Power Control (AMR)
Eng. Rules: The lowest is the parameter value, the best will be the reactivity;
nevertheless, it is better to wait for the effect of MS power decrease
on the uplink quality.
uplinkPowerControl Class 3 V8
Description: Whether power control in the MS–to–BTS direction is authorized at
cell level
Rec. value: enabled
Power Control (AMR)
Eng. Rules:
Nortel confidential

uRxLevDLP Class 3 V7
Description: Upper strength threshold for BTS txpwr decrease for step by step
algorithm (it is greater than IRxLevDLP)
Rec. value: = lRxLevDLP + Max (powerIncrStepSizeDL,
powerRedStepSizeDL) typically
Eng. Rules: Difference between the lower and upper thresholds must be greater or
equal to the maximum power step size.
uRxLevULP Class 3 V7
Description: Upper strength threshold for MS txpwr decrease for step by step
algorithm (it is greater than lRxLevULP).
Rec. value: lRxLevULP + Max (powerIncrStepSizeUL, powerRedStepSizeUL)
typically
Eng. Rules: Difference between the lower and upper threshold, must be greater or
equal to the maximum power step size.
uRxQualDLP Class 3 V7
Description: Upper quality threshold to reduce BTS txpwr for step by step algorithm
(it is lower than or equal to lRxQualDLP).
Eng. Rules: This value must be lower than lRxQualDLH in order to maintain
Nortel confidential

uRxQualULP Class 3 V7
Description: Upper quality threshold to reduce MS txpwr for step by step algorithm
(it is lower than or equal to lRxQualULP).
1.6 to 3.2 % (RxQual = 4 in GSM unit) wtih SFH
Eng. Rules: This value must be lower than lRxQualULH in order to maintain
There is no reason why this value should differ from uRxQualDLP.
Nortel confidential

5.17. TCH ALLOCATION MANAGEMENT PARAMETERS
accessClassCongestion Class 3 V9
Description: List of access classes that are not authorized in a cell during TCH
congestion phase (class 10 not included)
Value range: [0 to 9] User classes
[11 to 15] Operator classes
Object: bts
Default value: [0,1,2,3,4,5,6,7,8,9]
Type: DP, Design
Used in: Dynamic barring of access class (All_4)
V15.0 Changes of dynamic barring of access class (All_4)
Eng. Rules: Usually, in a low capacity cell (between 1 and 2 TRXs), many classes
must be forbidden in case of congestion (few resources available). In
a high capacity cell, only a few classes must be forbidden.
allocPriorityTable Class 3 V7
Description: Table of eighteen elements that define the internal priorities for
processing TCH queued allocation requests for each external priority
defined (among them, fourteen are GSM priorities)
TCH is always allocated using the internal priority.
Value range: [0 to 12]. “0” defines the highest priority.
Object: bts
Default value: 000000000000000000
Type: DP, System
Rec. value: 02222222222223042
0 8 9 10 11 12 2 2 2 2 2 2 2 2 3 0 4 2 for WPS use
Used in: Allocation and priority (run by the BSC) (All_1)
Queuing driven by the MSC (All_2)
Queuing driven by the BSC (All_3)
Eng. Rules: The default set means that all TCH allocation requests have the same
priority, which is equal to 0.
When queuing is activated, set the following parameters in order not
to disadvantage the interCell handover procedures:
Priority for interCell handover: 0
Priority for other procedures: ≠ 0
allocPriorityThreshold > 0
LCAUTION! When WPS Queuing Management is activated, the WPS priorities (8
to 12) have to be set as recommended, otherwise WPS queues will be
managed like internal public queues.
Nortel confidential

allocPriorityThreshold Class 3 V7
Description: Number of free TCHs needed for processing a TCH allocation request
with an internal priority higher than 1
These channels are reserved to allocation requests with a maximum
internal priority (priority 0).
The TCH allocation is performed according to this algorithm:
1 ≤ Nb of free TCH ≤ Nb of free TCH >
Nb of free TCH = 0
allocPriorityThreshold allocPriorityThreshold
TCH request queuing if defined or

TCH allocated TCH allocated
of priority 0 rejected
TCH request queuing if defined or queuing if defined or

TCH allocated
of priority > 0 rejected rejected
For GPRS with shared PDTCH, the allocation is performed according

to this algorithm: free resources are composed of free TCH and
shared PDTCH not already used by a GSM call:
1 ≤ Nb of free TCH ≤ Nb of free TCH >
Nb of free TCH = 0
allocPriorityThreshold allocPriorityThreshold
TCH allocated if TCH TCH allocated if TCH
free > 0 free > 0
if preemption is if preemption is
authorized and PCU authorized and PCU
TCH request queuing if defined or ACK, allocation of a ACK, allocation of a
of priority 0 rejected shared PDTCH shared PDTCH
if preemption is not if preemption is not
authorized or PCU authorized or PCU
NACK, queuing if NACK, queuing if
defined or rejected defined or rejected
TCH allocated if TCH
free > 0
if preemption is
authorized and PCU
TCH request queuing if defined or queuing if defined or ACK, allocation of a
of priority > 0 rejected rejected shared PDTCH
if preemption is not
authorized or PCU
NACK, queuing if
defined or rejected

Object: bts
Default value: 0
Type DP, Design
Rec. value: n, with n TRX
Nortel confidential

Eng. Rules: When TCH channels are reserved and the internal priority for
assignRequest is ≠ 0, the capacity for incoming calls decreases:
Example:
1 TRX, 7 TCH, 2 % blocking rate, allocPriorityThreshold = 0,
capacity for incoming calls = 2,88 Erlang
1 TRX, 7 TCH, 2 % blocking rate, allocPriorityThreshold = 1,
capacity for incoming calls = 2,23 Erlang
Queuing spreads out the TCH allocation request. As incoming
handover requests are not queued, such requests are disadvantaged.
A solution is to reserve 1 TCH channel (for 1 or 2 TRXs) or 2 TCH
channels (for at least 2 TRX) for calls of internal priority 0, and set the
priority 0 for incoming handovers only.
Note that when TCH channels are reserved for handovers, the
capacity for incoming calls decreases.
allocPriorityTimers Class 3 V7
Description: Table of timers defining the maximum waiting time of TCH allocations
request (public and WPS request), according to the internal priority.
Value range: [0 … 65535] for BSC3000
[0 … 2147483646] for BSC12000
Object: bts
Default value: 0 0 0 0 0 0 0 0 28 28 28 28 28
Type: DP, System
Rec. value: 5 0 5 5 0 0 0 0 28 28 28 28 28
Used in: Queuing driven by the MSC (All_2)
Eng. Rules: A high value of timer is not realistic, since a subscriber will not wait
unless the last TCH is available quickly. The last five parameters in
the table (those set to 28) define the waiting time of WPS calls
queued.
Nortel confidential

allocWaitThreshold Class 3 V7
Description: Table of thresholds defining the maximum number of TCH allocation
requests queued (public and WPS), according to their internal priority.
A TCH request of priority Pi, P0<Pi<P7, is queued if the total number
of requests of priority Pj, with j<i, already in the queue does not
exceed the waiting threshold of the queue “i” (element “i” of the
allocWaitThreshold table).
A WPS request priority is queued according to the rules of WPS
queuing.
Value range: [0 to 63] MMI Range
Object: bts
Default value: 0000000055555
Type: DP, System
Rec. value: n 0 n n 0 0 0 0 5 5 5 5 5, with n = integer part of (number of
SDCCH subchannels / 2)
Eng. Rules: The maximum size in each queue must be lower than the number of
SDCCH channels in the cell.
For an incoming call, when the assignRequest is queued, it remains
on the SDCCH subchannel.
The last five parameters in the table are determining the maximum
number of WPS calls of the same priority that can be queued.
allOtherCasesPriority Class 3 V7
Description: Index in the allocPriorityTable that defines the processing priority of
TCH allocation requests with cause “other cases”
This priority is used in primo–allocations or when an SDDCH cannot
be allocated for overload reasons.
Object: bts
Default value: 17
Type: DP, System
Rec. value: 16
Eng. Rules: The associated internal priority is > 0.
A TCH allocation request (in signaling mode) whose cause is “other
case” is acknowledged when at least allocPriorityThreshold + 1
channels are free.
Refer also to the allocPriorityTable parameter.
Nortel confidential

answerPagingPriority Class 3 V7
TCH allocation requests with cause “reply to paging”
This priority is used in signaling mode on TCH only.
Object: bts
Default value: 17
Type: DP, System
Rec. valueb 16
Eng. Rules: The associated internal priority is > 0.
A TCH allocation request (in signaling mode) whose cause is “other
case” is acknowledged when at least allocPriorityThreshold + 1
channels are free.
assignRequestPriority Class 3 V7
TCH allocation requests with cause “immediate assignment”
This priority is used when radio resource allocation queuing is not
requested by the MSC or not authorized in the BSS (refer to the
bscQueuingOption parameter).
Object: bts
Default value: 17
Type: DP, System
Rec. value: 17
Eng. Rules: When queuing driven by the MSC is used, this parameter is not
significant.
It is recommended not to associate an internal priority equal to 0.
There is no queuing for TCH in “signaling mode”.
Nortel confidential

bscMSAccessClassBarringFunction Class 3 V9
Description: Enable or disable dynamic barring of access class at the bsc level
Object: bsc
Type: DP, Design
Rec. value: enabled, see Engineering Rules
Eng. Rules: Set to disabled, this parameter allows to inhibit the dynamic barring of
access class feature for the whole BSC whatever the values of the
other parameters related to All_4 are.
If queuing or directed retry is activated, the following parameters must
be used:
numberOfTCHQueuedBeforeCongestion
numberOfTCHQueuedToEndCongestion
bscQueuingOption Class 1 V7
Description: Whether radio resource allocation requests are queued in the BSC
when no resources are available
If no resource is available when an allocation request is received and queuing is not
allowed, the allocation request is refused immediately.
Value range: [allowed (MSC driven) / forced (O&M driven) / not allowed]
allowed: resource allocation request queuing depends on the type
of operation and indicative items provided with the messages
received from the MSC.
forced: resource allocation request queuing depends on the type of
operation only.
not allowed: resource allocation request queuing is forbidden.
Object: signallingPoint
Default value: forced
Type: DP, Design
Rec. value: forced (O&M driven)
allowed (MSC driven) for WPS use
Eng. Rules: When queuing is activated, the queued procedures (assignRequest
and intraCellHO if OMC driven) statistically take advantage on the
other procedures. If all the TCH channels are already allocated, the
queued procedures stay in the queue during a defined time (see
allocPriorityTimers), when the others are rejected.
Nortel confidential

Suppose the operator expects to enable the queuing later. Due to the
class of the parameter bscQueuingOption, it is recommended not to
set “not allowed”. Otherwise, the BSC will need to be switched off to
implement the feature.
LCAUTION! WPS Queuing Management can be activated only if
bscQueuingOption is set to “allowed”, i.e if MSC can handle different
priorities of assignement request.
btsMSAccessClassBarringFunction Class 3 V9
Description: Enable or disable dynamic barring of access class at the bts level
Object bts
Type: DP, Design
Rec. value: See Engineering Rules
Eng. Rules: To enable dynamic barring of access class at the bts level, this
parameter and the bscMSAccessClassBarringFunction parameter of
the corresponding bsc must be set to enabled.
This feature globally reduces the cell capacity.
The fewer the number of TRXs on the cell, the more the capacity is
reduced.
callReestablishmentPriority Class 3 V7
TCH allocation requests with cause “call reestablishment”
Objectb bts
Default value: 17
Type: DP, System
Rec. value: 15
Eng. Rules: The value that must be given should correspond to a priority 0.
Refer to the allocPriorityTable parameter.
Nortel confidential

cellBarQualify Class 3 V8
Description: Cell selection priority used in the C2 algorithm in Phase II
cell BCCH.
Value range: [true (low priority) / false (normal priority)]
Object: bts
Default value: False
Rec. value: False
(Sel_1)
Additional reselection criterion (for phase 2) (Sel_3)
New SYS INFO messages
Eng. Rules: refer to Sel_3 algorithm, see also chapter DualBand Networks.
cellBarred Class 3 V7
Description: Whether direct cell access are barred to mobiles
cell BCCH.During a call, it is transmitted on a signaling link.
If the attribute value is changed to “barred”, all in–progress calls can
continue but the BSC will direct further mobile calls to another cell.
Value range: [barred / not barred]
Object: bts
Default value: not barred
Rec. value: not barred
(Sel_1)
Additional reselection criterion (for phase 2) (Sel_3)
Eng. Rules: refer to Sel_3 algorithm, see also chapter DualBand Networks.
channelType Class 2 V7
Description: Type of logical channel supported by a radio TS
Value range: [tCHFull / sDCCH / mainBCCH / mainBCCHCombined /
bcchsdcch4CBCH / sdcch8CBCH / cCH (V12) / pDTCH (V12)]
Object: channel
Default value: None
Rec. value: None.
No recommended value is specified since this parameter
depends on the strategy of the operator.
Used in:
Eng. Rules: In the case of GSM, refer to chapter SDCCH Dimensioning an TDMA
Models for the rules with SDCCH.
Nortel confidential

emergencyCallPriority Class 3 V7
Description: Index in the table allocPriorityTable for a TCH allocation request
whose cause is “emergency call”
Object: bts
Default value: 17
Type: DP, System
Rec. value: 15
Eng. Rules: The internal priority associated is 0. A TCH allocation request (in
signaling mode) whose cause is “emergency call” is acknowledged
when at least 1 channel is free.
interCellHOExtPriority Class 3 V7
incoming inter–bss handovers in a cell
This priority is used when radio resource allocation queuing is not
requested by the MSC or not authorized in the BSS (refer to the
bscQueuingOption parameter).
Object: bts
Default value: 17
Type: DP, System
Rec. value: 15
Eng. Rules: The internal priority associated is 0. A TCH allocation request (in
signaling mode) on interBSC handover is aknowledged when at least
1 channel is free.
When queuing is used, it is recommended to give the priority 0 and
reserve the TCH channels (allocPriorityThreshold) since it
disadvantages requests that cannot be queued.
Nortel confidential

interCellHOIntPriority Class 3 V7
incoming intra–bss handovers in a cell
This priority is always used, whether radio resource allocation queuing
is authorized in the BSS or not.
Object: bts
Default value: 17
Type: DP, System
Rec. value: 15
Eng. Rules: The internal priority associated is 0.
A TCH allocation request (in signaling mode) on intraBSC handover is
aknowledged when at least 1 TCH is free.
When queuing is used, it is recommended to give the priority 0 and
reserve the TCH channels (allocPriorityThreshold) since it
disadvantages requests that cannot be queued.
intraCellHOIntPriority Class 3 V7
Description: Index in the allocPriorityTable that defines the processing priority of an
intra–bts handover in a cell
This priority is always used, whether radio resource allocation queuing
is authorized in the BSS or not.
Object: bts
Default value: 17
Type: DP, System
Rec. value: 14
Eng. Rules: Refer also to the allocPriorityTable parameter.
Nortel confidential

directedRetryPrio V12
Description: Index in the allocPriorityTable that defines the processing priority for
directed retry handovers
Object: bts
Default value:
Rec. value: 17
Used in: TCH Allocation Management
Eng. Rules: Before V12, the directed retry used the incoming handover priority,
which is the highest priority; to avoid this, this new priority is
introduced.
intraCellQueuing Class 3 V8
Description: Whether intra–bts handover requests are queued for a cell. This
parameter is significant only when queuing radio resource allocation
requests is allowed in the BSS.
Refer to the bscQueuingOption parameter.
Object: bts
Rec. value: Enabled
Eng. Rules: None.
minNbOfTDMA Class 2 V7
Description: Minimum number of TDMA frames that must be working in order for
the cell itself to be working.
The frame carrying the cell BCCH must be among them and is
successfully configured.
Object: bts
Default value: 1
Rec. value: 1
Used in:
Eng. Rules: None.
Nortel confidential

notAllowedAccessClasses Class 3 V7
Description: List of mobile access classes that are forbidden in the cell, except
case of congestion.
This attribute, together with the emergencyCallRestricted attribute,
allows to control access to a cell according to the service classes
authorized.
Value range: List of mobile access class:
[0 to 9]: user classes
[11 to 15]: operator classes
Object: bts
Default value: Leave the field empty
Type: DP,Operation
Rec. value: “null” (empty list)
Eng. Rules: This parameter contains the list of forbidden access classes. Usually
all users are authorized, in this case, the list must be empty.
numberOfTCHFreeBeforeCongestion Class 3 V9
Description: Minimum number of free TCHs which triggers the beginning of the
TCH congestion phase and the beginning of the traffic overload
condition
Value range: [0 to infinite]
Object: bts
Default value: 0
Type: DP, Design
Rec. value: 1 for cells with 1-2 TRXs
2 or 3 for cells with more than 3 TRXs
Eng. Rules: Note that the congestion feature does not distinguish between
reserved or unreserved TCHs. A reserved TCH is a TCH booked for a
priority 0 procedure. Setting this parameter must consider the number
of reserved TCHs.
Nortel confidential

numberOfTCHFreeToEndCongestion Class 3 V9
Description: Threshold that gives the number of free TCHs, which triggers the end
of TCH congestion phase and the end of the traffic overload condition.
Object: bts
Default value: 0
Type: DP, Design
Rec. value: 2 for cells with 1-2 TRXs
3 or 4 cells with more than 3 TRXs
Eng. Rules: numberOfTCHFreeToEndCongestion >
numberOfTCHFreeBeforeCongestion
Note, this inequality is not checked at the OMC.
numberOfTCHQueuedBeforeCongestion Class 3 V9
Description: Maximum number of TCH allocation requests queued which triggers
the beginning of the TCH congestion phase and the beginning of the
traffic overload condition
Object: bts
Default value: 0
Type: DP, Design
Rec. value: TBD
Eng. Rules:
numberOfTCHQueuedToEndCongestion Class 3 V9
Description: Maximum number of TCH allocation requests queued which triggers
the end of TCH congestion phase and the end of the traffic overload
condition
Object: bts
Default value: 0
Type: DP, Design
Rec. value: TBD
Eng. Rules:
Nortel confidential

otherServicesPriority Class 3 V7
Description: Index in the table allocPriorityTable for a TCH allocation request (in
signaling mode) whose cause is “other services”
This priority is used in primo–allocations or when an SDDCH cannot be allocated for
overload reasons.
Object: bts
Default value: 17
Type: DP, System
Rec. value: 16
Eng. Rules: The internal priority associated is > 0. A TCH allocation request (in
signaling mode) whose cause is “other services” is acknowledged
when at least allocPriorityThreshold + 1 channels are free.
priority Class 2 V7
Description: Priority level of a TDMA frame for mapping TDMA onto TRXs.
At least minNbOfTDMA TDMA frames related to a cell must be
successfully configured for the cell to be working.
They include the TDMA frame carrying the cell BCCH and those with
the other priority(ies).
Object: transceiver
Default value:
Used in:
Eng. Rules: Refer to section SDCCH Dimensioning and TDMA priorities.
Nortel confidential

5.18. EMLPP RADIO RESOURCE PREEMPTION PARAMETER

Note that other parameters related to eMLPP Radio Resource Preemption
(emergencyThreshold and eMLPPThreshold) are only meaningful in GSM-R, therefore they
are not described in this document.
preemptionAuthor Class 3 V15

Description: This parameter activates or deactivates radio resource preemption
capability in the BSS (used in the context of eMLPP supplementary
service).
This parameter and the radio resource preemption capability
introduced in V12.4 used to be GSM-R only. They are available in
public GSM from v15.1 onwards.
Value range: [forbidden, authorizedWithRelease, authorizedForcedHO]
Default value: forbidden
Type: DP
Rec. value: see Eng Rules
Used in: eMLPP Preemption
Eng. Rules: preemptionAuthor = “forbidden” means that the BSC never performs
radio resource preemption, whatever the priority and PCI/PVI flags’
values.
preemptionAuthor = “authorizedWithRelease” means that the BSC is
allowed to perform radio resource preemption if necessary and if
authorised by the MSC.A successful preemption results in the
preempted call being released.
preemptionAuthor = “authorizedWithForcedHO” means the same thing
as preemptionAuthor = “authorizedWithRelease” in the current
implementation, despite the different name
Nortel confidential

5.19. DIRECTED RETRY HANDOVER PARAMETERS
adjacent cell umbrella ref Class 3 V9

Description: Identifier of the adjacentCelHandOver object that describes the
neighbor cell towards which a directed retry will be triggered in BSC
mode
Object: bts
Default value:
Type: DP, Design
Rec. value: Identifier of the adjacentCellHandOver of the macrocell which
totally covers the micro cell.
Used in: Directed Retry Handover: BSC (or local) mode
Eng. Rules: BSC mode is especially used in a two layer network. For micro cells,
directed retry needs to be triggered towards the macro cell. However,
if the recovering of each micro cell is good enough,
adjacentUmbrellaRef can identify a micro cell.
To facilitate the procedure, the BCCH frequency of the target neighbor
cell must be in the reselection list.
See also chapter Directed Retry Handover Benefit.
directedRetry Class 3 V9
Description: Minimum signal strength level received by the mobiles to be granted
access to the neighbor cell, used in processing directed retry
handovers in BTS mode
Default value: more than -48 dBm
Rec. value: = rxLevMinCell + 3 to 25 dB
Used in: Directed Retry Handover: BTS (or distant) mode
Eng. Rules: The choice of recommended value has to be done regarding the
general design of the network. A 3 dB margin must be considered as
a minimum on a network to eliminate field strength bumps effect due
to multipath. However, this margin must be increased in an urban
environment or with the use of reuse pattern (overall for a 1X1
pattern) because of the generated interference when the MS is not on
the best server cell.
LCAUTION! Directed retry is not allowed between 2 zones of a concentric cell.
possible to set this parameter to a higher value in neighbour cells
belonging to the low priority frequency band. Thus, this band will be
underprivileged. However, it will impact the directed retry for
monoband MS on this band (less directed retry).
Nortel confidential

directedRetryModeUsed Class 3 V9
Description: Specify how directed retry handovers are processed in a cell either
directly by the BSC (microcells only) or by querying the BTS first
Value range: [bsc / bts]
Object: bts
Default value: bts
Type: DP, Design
Rec. value: bts
Eng. Rules: The micro cell should be entirely covered by the macro cell in order to
use efficiently the bsc mode.
The use of the bts mode is recommended in a hot spot when there are
several micro cells under the umbrella. The bts mode allows the use
of micro cells to rescue the umbrella cell and also avoids a saturation
of the umbrella cell.
interBscDirectedRetry Class 3 V9
Description: Whether inter–bss directed retry handovers are allowed in a BSS
Object: bsc
Default value: allowed
Type: DP, Design
Rec. value: allowed
Eng. Rules: See also chapter Directed Retry Handover Benefit.
interBscDirectedRetryFromCell Class 3 V9
Description: Whether inter–bss directed retry handovers are allowed in a cell
Object: bts
Rec. value: allowed
Eng. Rules: If the value is “not allowed” then, the value of
interBscDirectedRetryFromCell must be set to “not allowed” for the
concerned cells.
Nortel confidential

intraBscDirectedRetry Class 3 V9
Description: Whether intra–bss directed retry handovers are allowed in a BSS
Object: bsc
Type: DP, Design
Rec. value: allowed
Eng. Rules: See also chapter Directed Retry Handover Benefit.
intraBscDirectedRetryFromCell Class 3 V9
Description: Whether intra–bss directed retry handovers are allowed in a cell
Object: bts
Rec. value: allowed
Eng. Rules: If the value is “not allowed” then, the value of
intraBscDirectedRetryFromCell must be set to “not allowed” for the
concerned cells.
modeModifyMandatory Class 3 V9
Description: Whether a CHANNEL MODE MODIFY message should be sent to the
mobile after a directed retry handover in the BSS
Value range: [used (yes) / not used (no)]
Object: bsc
Default value: not used
Rec. value: not used
Used in: Directed Retry Handover
Nortel confidential

Eng. Rules: In the early days of GSM, this parameter was useful for mobiles
belonging to specific brands, that used not to be able to switch directly
from signaling (SDCCH) to speech (TCH) when executing a Directed
retry procedure. For that reason, this parameter used to be set to
"used" so that a Channel Mode Modify procedure could be done,
forcing an explicit change of channel upon the mobile. However,
today, as these mobile bugs have now presumably been corrected,
with few or no faulty mobiles remaining in the field today, the
systematic invokation of the CMM procedure is no longer required.
Setting to "used" may, in addition, have detrimental side-effects for
some kinds of inter-cell handovers (problem noted on instances of
intercell 3G-2G Handovers) which will systematically invoke a
Channel Mode Modify. Therefore it is recommended to set this
parameter systematically to value “not used”.
Nortel confidential

5.20. CONCENTRIC CELL PARAMETERS
biZonePowerOffset Class 3 V12

Description: Offset added in calculation formula to draw up the list of eligible cells
for handover towards a dualband, dualcoupling, or concentric cell
inner zone to take into account the difference of propagation models
between the two bands of the cells and the difference of transmission
power between TRXs of the two zones due to either BTS
configuration or coupling.
Default value: if main band = 850 MHz biZonePowerOffset = 3 dB
if main band = 1900 MHz biZonePowerOffset = -3 dB
Direct TCH allocation
Concentric/DualCoupling/DualBand Cell Handover
Eng. Rules: Used for intercell handover to control whether the inner zone is
“eligible” or not.
to inhibit Direct TCH Allocation on an adjacent cell (when the
adjacent cell is declared as monozone / concentric / dualband /
dualcoupling) biZonePowerOffset(n) = 63
to allow Direct TCH Allocation on an adjacent cell (when the
adjacent cell is declared as concentric / dualband / dualcoupling)
biZonePowerOffset(n) =concentAlgoExtRxLev(n) - rxLevMinCell(n)
Note: Shall be 63 for a monozone adjacent cell.
The higher (in positive) is the value, the more difficult it will be to
handover in the inner zone of the adjacent cell.
It is advised to set a value higher than the max offset (in rxLevDL
band 0) corresponding to the biggest difference of coverages between
the 2 bands (for the adjacent cell) otherwise an intercell handover to
the inner zone would be wrongly decided.
LCAUTION! If HO decision is made toward the inner zone of a multizone cell, then
related EXP1XX(n) is computed with biZonePowerOffset(n).
See also chapters Concentric Cells and DualBand Networks.
Nortel confidential

biZonePowerOffset Class 3 V12

Description: Power offset between inner and outer TRXs of the handOverControl
object of a dualband, dualcoupling, or concentric cell.
Default value: if main band = 850 MHz, biZonePowerOffset = 3 dB
if main band = 1900 MHz, biZonePowerOffset = -3 dB
Direct TCH allocation
Eng. Rules:
monozone cell:
biZonePowerOffset = 63
concentric cell:
biZonePowerOffset = zone Tx powermax reduction
concentric cell with HePA only on outer zone:
dualband cell (main band = 850 or 900 MHz):
dualband cell (main band = 1800 or 1900 MHz):
biZonePowerOffset = - 6
dualcoupling cell:
biZonePowerOffset = zone Tx powermax reduction = coupling losses
difference between inner and outer zone
dualband + dualcoupling cell combination:
biZonePowerOffset = coupling losses + propagation losses
LCAUTION! When using dualcoupling cell DLU attenuation should be NULL and
compensated by the zone Tx power max reduction, see concentric
cell parameter
Note: Shall be 63 for a monozone adjacent cell.
LCAUTION! If HO decision is made in the small zone of a multizone cell then
related EXP2xx(n) = hoMarginxx(n) + biZonePowerOffset.
Nortel confidential

concentAlgoExtMsRange Class 3 V9
Description: MS to BTS distance below which a handover is requested from the
large zone to the small zone if the level criteria is verified
Default value: 1
Type: DP, Design
Rec. value: 34
Used in: Direct TCH Allocation
Concentric cell / dualcoupling cell intracell handovers
Eng. Rules: The calculated distance between the MS and the BTS is based on
timing advance (TA), which has an accuracy of ± 3 bits (corresponding
to more than 1,5 km), thus not very useful in urban areas where the
cell size is relatively small and multipath affect the MS_BS distance.
However this parameter can be useful in rural areas or suburban
areas, and concentAlgoExtMsRange should respect following rules:
concentAlgoExtMsRange = concentAlgoIntMsRange - 1 km
concentAlgoExtMsRange < concentAlgointMsRange
concentAlgoExtMsRange < msRangeMax
Note: 34 disable the parameter since condition is always fullfilled.
concentAlgoIntMsRange Class 3 V9
Description: MS to BTS distance from which a handover from the small zone to the
large zone will be requested
Default value: 34
Type: DP, Design
Rec. value: 34
Used in: Concentric cell / dualcoupling cell intracell handovers
Eng. Rules: The calculated distance between the MS and the BTS is based on
timing advance (TA), which has an accuracy of ± 3 bits (corresponding
to more than 1,5 km), thus not very useful in urban areas where the
cell size is relatively small and multipath affect the MS_BS distance.
However this parameter can be useful in rural areas or suburban
areas, and concentAlgoIntMsRange should respect following rules:
concentAlgoIntMsRange > concentAlgoExtMsRange
concentAlgoIntMsRange < msRangeMax
Note: 34 disable the parameter since condition is always fullfilled.
Nortel confidential

concentAlgoExtRxLev Class 3 V9
Description: The level of the MS signal strength above which a handover is
requested from the large zone to the small zone
Default value: - 95 to - 94
Type: DP, Design
Used in: Direct TCH Allocation
Eng. Rules: The recommended value depends on the network design. Depending
on capacity distribution between inner and outer zone, CPT can be
used to match the RxLev DL number of samples to
concentAlgoExtRxLev, which defines when users interzone handover
from outer to inner zone, i.e. inner zone traffic load.
The following rules shall be respected:
concentAlgoExtRxLev > concentAlgoIntRxLev
concentAlgoExtRxLev ≤ rxLevMinCell + biZonePowerOffset
concentAlgoIntRxLev Class 3 V9
Description: Level of the MS signal strength below which a handover is requested
from the small zone to the large zone
Default value: less than -110
Type: DP, Design
Eng. Rules: In order to avoid unnecessary ping-pong interzone HO a Hysteresis
Margin should be added:
concentAlgoIntRxLev = concentAlgoExtRxLev - biZonePowerOffset
- Hysteresis Margin
where recommended Hysteresis Margin = 4 dB
Nortel confidential

concentric cell Class 2 V9

Description: Whether the cell is monozone, concentric, dualband or dualcoupling
A concentric, dualband, or dualcoupling cell describes a combination
of two transmission zones, the outer (or large) zone and the inner (or
small) zone. The inner zone is entirely included in the outer zone.
A dualband cell is a particular type of concentric cell for which GSM
900 and GSM1800 (or GSM 850 and GSM1900) TRXs/DRXs coexist
and share the same BCCH.
A dualcoupling cell is a particular type of concentric cell for which the
TRXs/DRXs are combined with two types of combiners.
For concentric configurations (concentric, dualband or dualcoupling),
a TDMA frame belongs to one zone or the other, but never to both.
Value range: [monozone / concentric / dualband / dualcoupling] from V12
monozone: normal cell
concentric: two concentric transmission zones
dualband: two concentric transmissions zones with GSM 900
TRXs/DRXs for the one and GSM 1800 TRXs/DRXs for the other
dualcoupling: two concentric transmission zones with TRXs/DRXs
combined with one type of combiner for the one and with another
type of combiner for the other
Object: bts
Default value: monozone
Eng. Rules:
concentric cell:
From V12, it is possible to allocate directly a TCH in the innerzone for
call set-up or HO and to reuse the same frequency in both zones, and
hopping concerns the total available number of frequencies.
A cell configuration with HePA only on outer zone is concentric cell,
not a dualcoupling cell.
dualband cell:
The dualband combining into one cell allows to save up to one
SDCCH in particular configurations, the combining of GSM 900 / GSM
1800 (or GSM 850 / GSM 1900) resources into one pool allows to
increase the traffic capacity.
LCAUTION! dualband is not supported on S4000 with DCU2/DCU4, S4000 with
DCU2, S4000 with DCU4
dualcoupling cell:
The DLU attenuation shall be used: so configure the “attenuation”
parameter (btsSiteManager object) to null, configure the max power
for the cell to the desired max power (power for the outer zone) and
configure zone Tx power max reduction for the inner zone to the delta
value.
LCAUTION! dualcoupling is not supported on mixed DCU4 or DRX transceiver
architecture.
Nortel confidential

small to large zone HO priority Class 3 V12

Description: External priority of inter-zone handovers from the inner zone to the
outer zone in a concentric cell. This attribute is defined if the
associated bts object describes a concentric cell.
Default value: 17
Type: DP
Rec. value: 14
Eng. Rules: Refer also to the allocPriorityTable parameter.
transceiver equipment class Class 2 V9

Description: Class of a TRX/DRX.
The class of a TRX/DRX sets, among others, its maximum
transmission power. The attribute possible values have the following
meaning:
Class 1 corresponds to GSM 850/900 class 5 or GSM 1800/1900
class 1 (20W to 40W transmitters)
Class 2 corresponds to GSM 900 class 6 which is not supported or
GSM 1800/1900 class 2 (10W to 20W transmitters)
Value range: [0 (reserved) / 1 / 2]
Object: transceiverEquipment
Type: DP
Rec. value: monozone: 1
concentric cell: outer=1, inner=1
dualband cell: outer=1, inner=2
dualbcoupling cell: outer=1, inner=2
Eng. Rules: When dual band is used, the class of a TRX/DRX enables to
distinguish which DRX and which TDMA are used in the outer zone or
inner zone.
Class 1 corresponds to to a TDMA in the frequency band carrying
BCCH so belonging to transceiverZone = 0 (large/outer zone).
Class 2 corresponds to a TDMA in the frequency band not carrying
BCCH so belonging to transceiverZone = 1 (small/inner zone).
If the TRX/DRX is partnered with a TDMA frame, its class matches the
TRX/DRX class allotted to the zone to which the TDMA frame belongs
(refer to the next parameter).
Note: In case of concentric cell configuration, setting inner and outer class to
“1” allows a reconfiguration of TRX/DRX from the inner to the outer if
needed.
Nortel confidential

transceiver equipment class V9

Description: Class of the TRX/DRXs partnered with the TDMA frames of the zone.
The class of a TRX/DRX sets, among others, its maximum
transmission power. Refer to the previous parameter.
Object: transceiverZone
Type: DP
Rec. value: monozone: 1
concentric cell: outer=1, inner=1
dualband cell: outer=1, inner=2
dualbcoupling cell: outer=1, inner=2
Eng. Rules: When dual band is used, the class of a TRX/DRX enables to
distinguish which DRX and which TDMA are used in the outer zone or
inner zone.
Class 1 corresponds to to a TDMA in the frequency band carrying
BCCH so belonging to transceiverZone = 0 (large/outer zone).
Class 2 corresponds to a TDMA in the frequency band not carrying
BCCH so belonging to transceiverZone = 1 (small/inner zone).
Note: In case of concentric cell configuration, setting inner and outer class to
“1” allows a reconfiguration of TRX/DRX from the inner to the outer if
needed.
transceiverZone Class 2 V12

Description: Identifier of the transceiverZone object that defines the zone to which
a TDMA frame belongs in a concentric cell.
The transceiverZone objects are only significant for the bts objects
that describe concentric cells. Two transceiverZone objects are
created for each created concentric bts object; one describes the
large or outer transmission zone, and the other describes the smallor
inner transmission zone.
Value range: [0 (large outer zone) / 1 (small or inner zone)]
Type: DP
Rec. value: 0 for outer zone
1 for inner zone
Eng. Rules: When a concentric/dualband/dualcoupling cell is created the
transceiverZone outer zone must set to “0” and the transceiverZone
inner zone must be set to “1”.
It is not applicable for monozone cells.
Nortel confidential

zone Tx power max reduction Class 2 V9

Description: Attenuation vs bsTxPwrMax that defines the maximum TRX/DRX
transmission power in the zone
Value range: large zone = [0] dB, small zone = [1 to 55] dB
Default value: 0 dB
Type: DP, Design
Used in: Concentric cell / dualcoupling cell intracell handovers
Eng. Rules:
concentric cell:
zone Tx Power Max Reduction(outer) = 0
zone Tx Power Max Reduction(inner) ≤ zone Tx Power Max
Reduction(outer)
(zone Tx Power Max Reduction(inner) = 0 is recommanded)
dualband cell (homogeneous coupling):
zone Tx Power Max Reduction(outer) = 0
zone Tx Power Max Reduction(inner) = 1
dualcoupling cell:
zone Tx Power Max Reduction(outer)=0
zone Tx Power Max Reduction(inner)=3 simulates the D/H2D
configuration
zone Tx Power Max Reduction(inner)=4 simulates the H2D/H4D
configuration
LCAUTION! when using dualcoupling cell DLU attenuation should be NULL and
compensated by the zone Tx power max reduction, see concentric
cell parameter
Nortel confidential

5.21. INTERFERENCE LEVEL PARAMETERS
averagingPeriod Class 2 V7
Description: Number of SACCH multiframes over which the interference levels are
averaged. This averaging will be performed immediately before the
transmission of the RESOURCE INDICATION message.
This attribute, together with the “thresholdInterference” attribute,
allows users to manage interferences in radio cells. Refer to this entry
in the Dictionary.
Value range: [0 to 255] SACCH frame (1 unit = 480 ms on TCH, 470 ms on
SDCCH)
Default value: 20
Type: DP, System
Rec. value: 20
Used in: Radio channel allocation
Interference Management (BTS and BSC) (If)
Eng. Rules: Performing this message broadcast has a great impact on the system
load and should not be done too often.
Reducing this value speeds-up the channel allocation algorithm, since
it checks temporary channel interference non frequently. However, the
main purpose of this algorithm is to take into account long term
interference and not short term interference which do not have a
statistically large impact on call quality.
Nortel confidential

radChanSelIntThreshold Class 3 V8
Description: Maximum interference level on free radio channels, below which the
channels are ranged in the group of allocation priority channels
The information is used to first allocate the free channels with the
lowest interference level. The levels depend on the
thresholdInterference attribute value defined for the cell. Refer to this
entry in the Dictionary.
The BSC distributes the free radio channels among two groups:
The first group contains the list of channels with a measured
averaged interference level equal to or lower than the defined
level.
The second group contains the list of channels with a measured
averaged interference level higher than the defined level, and
recently released channels for which no measurement is available.
Four resource pools are defined for each SDCCH or TCH type of
channel:
low interference level radio channels that are authorized to hop
low interference level radio channels that are not authorized to hop
high interference level radio channels that are authorized to hop
high interference level radio channels that are not authorized to
hop
Default value: 1
Rec. value: 3
1 (for 1X1 & 1X3)
Used in: Interference Management (BTS and BSC) (If)
Eng. Rules: A high value for this parameter means a tolerant interference sorting.
It is easier to change the value of this pointer than to tune the
thresholds themselves since the thresholds are used in the lower layer
of signal processing at the BTS.
The radChanSellIntThreshold counter can be set after interference
counters monitoring. Ideally, it should depend on the average traffic
load expected on the cell and on the interference distribution.
With low Traffic per TCH, radChanSellIntThreshold can be set to 1.
This means that the selection of the non interefered channels is very
selective. The few TCH selected are sufficient for the traffic to be
carried. RadChanSellIntThreshold can be decreased to 1 when using
1X1 or 1X3 reuse pattern in order to use as more BCCH resources as
possible.
With high Traffic per TCH, radChanSellIntThreshold can be set to 4.
This means MS will get allocated to a channel regardless of the
interference as long as there are resources available.
Nortel confidential

thresholdInterference Class 2 V7
Description: List of four thresholds defined in ascending order, used to sort idle
channels on the basis of measured interference levels
This attribute, together with the averagingPeriod attribute, allows
managing interferences in a radio cell. The classification is used by
the radio resource allocator.
For each idle radio channel, the BTS permanently measures the
signal strength level RXLEV.
When averagingPeriod “Measurement results” messages have been
received, the L1M function in the BTS calculates interference level
averages, sorts the idle channels according to the five defined
interference levels, and sends the information to the BSC.
Level 0 corresponds to: RXLEV < threshold 1
Level 1 corresponds to: threshold 1 < RXLEV < threshold 2
Level 4 corresponds to: threshold 4 < RXLEV
Value range: [-128 to 0] dBm
Default value: -100 -90 -80 -70
Rec. value: -114, -112, -108, -100
Used in: Radio channel allocation
Interference Management (BTS and BSC) (If)
Eng. Rules: Those values define 5 interference level ranges, so free channel
classification can be displayed at the OMC-R level. The setting of the
threshold Interference level should be linked to the interference level
distribution in the cell. As a first definition, thresholds can be evenly
distributed over the defined range.
Nortel confidential

5.22. RADIO RESSOURCES CONTROL AT CELL LEVEL
radResSupBusyTimer Class 3 V8
Description: Maximum time that SDCCH or TCH can be continuously occupied
without generating an alarm
Value range: [1 to 18] hours
Object: bsc
Default value: 3
Type: DP, System
Rec. value: 10 or 3 (see Engineering Rules)
Used in:
Eng. Rules: Useful, for example, to see problems of resource deallocation.
10 during busy day for high traffic area
3 for other cases (at night, in rural areas).
radResSupervision Class 3 V8
Description: Indicates whether radio resources are controlled at the cell level (both
busy resources and free resources)
When no control is performed, no alarm related to the use or non–use
of an SDCCH or TCH is generated. Refer to the
radResSupBusyTimer and radResSupFreeTimer parameters.
Object: bts
Default value: True
Type: DP, System
Rec. value: True
Used in:
Eng. Rules: It is recommended to use this control mainly after a frequency plan
update, to regularly supervise the network.
radResSupFreeTimer Class 3 V8
Description: Maximum time an SDCCH or TCH can be continuously free without
generating an alarm
Value range: [1 to 18] hours
Object: bsc
Default value: 18
Type: DP, System
Rec. value: 10 or 3 (see Eng. Rules)
Used in:
Eng. Rules: Useful, for example, to see problems of design at busy hours or if
some channels are jammed.
10 during busy day for high traffic area
3 for other cases (at night, in rural areas).
Nortel confidential

5.23. BSS TIMERS
bssMapT1 Class 1 V7
Description: A interface timer triggered by the BSC in the BSSMAP management
procedure.
It is started on transmission of BLOCK or UNBLOCK by the BSC and
cancelled on receipt of BLOCK ACKNOWLEDGE or UNBLOCK
ACKNOWLEDGE sent by the MSC.
Value range: [2 to 300] seconds
Object: bsc
Default value: 5
Type: DP, System
Rec. value: 5, 60 (if using DMS switch)
Used in:
Eng. Rules:
bssMapT12 Class 1 V7
procedure.
This timer is used with a Phase I MSC only. It is started on
transmission of RESET CIRCUIT by the BSC and cancelled on receipt
of RESET CIRCUIT ACKNOWLEDGE sent by the MSC.
Object: bsc
Default value: 5
Type: DP, System
Rec. value: 5, 60 (if using DMS switch)
Used in:
Eng. Rules:
Description: An interface timer triggered by the BSC in the BSSMAP management
procedure.
It is started on receipt of RESET sent by the MSC. On elapse, the
BSC sends RESET ACKNOWLEDGE to the MSC.
Object: bsc
Default value: 32
Type: DP, System
Rec. value: 32
Used in:
Eng. Rules:
Nortel confidential

procedure.
This timer is used with a Phase II MSC only. It is started on
transmission of RESET CIRCUIT by the BSC and cancelled on receipt
of RESET CIRCUIT ACKNOWLEDGE sent by the MSC.
Object: bsc
Default value: 32
Type: DP, System
Rec. value: 32
Used in:
Eng. Rules:
procedure.
It is started on transmission of CIRCUIT GROUP BLOCK or CIRCUIT
GROUP UNBLOCK by the BSC and cancelled on receipt of CIRCUIT
GROUP BLOCK ACKNOWLEDGE or CIRCUIT GROUP UNBLOCK
ACKNOWLEDGE sent by the MSC.
Object: bsc
Default value: 32
Type: DP, System
Rec. value: 32
Used in:
Eng. Rules:
bssMapT4 Class 1 V7
procedure.
It is started on transmission of RESET and cancelled on receipt of
RESET ACKNOWLEDGE sent by the MSC. On elapse, the BSC
sends RESET.
Object: bsc
Default value: 60
Type: DP, System
Rec. value: 60
Used in:
Eng. Rules:
Nortel confidential

bssMapT7 Class 1 V7
procedure.
It is started on transmission of HANDOVER REQUIRED and
cancelled on receipt of HANDOVER COMMAND, RESET, RESET
CIRCUIT, CLEAR COMMAND or HANDOVER REQUIRED REJECT.
Object: bsc
Default value: 7
Rec. value: 7
Used in:
Eng. Rules:
bssMapT8 Class 1 V7
procedure.
It is greater than t3103 for each cell managed by the BSC. It is started
on transmission of HANDOVER COMMAND and cancelled on receipt
of CLEAR COMMAND sent by the MSC or HANDOVER FAILURE
sent by MS.
Object: bsc
Default value: 15
Rec. value: 15
Used in:
Eng. Rules: It is greater than t3103 for each cell managed by the BSC.
bssMapTchoke Class 1 V7
Description: A interface timer triggered by the BSC in the handover management
procedure.
It is started by the BSC when the last neighbour cell in the list is
rejected. On timer elapse, the BSC asks the BTS to provide a new list
of eligible cells.
Object: bsc
Default value: 4
Type: DP, System
Rec. value: 4
Used in:
Eng. Rules: It is strongly recommended to keep this value.
Nortel confidential

bssSccpConnEst Class 1 V7
Description: A interface timer triggered by the BSC in the handover management
procedure.
It is set on transmission of CONNECTION REQUEST and cancelled
on receipt of CONNECTION CONFIRM or CONNECTION REFUSED.
Value rang: [5 to 360, by steps of 5] seconds
Default value: 5
Type: DP, System
Rec. value: 5
Used in:
Eng. Rules: A high value is dangerous in case of slowing down on A interface.
Then, the minimum value (5 s) must be chosen for this parameter; it is
strongly recommended not to modify this value.
t3101 Class 3 V7
Description: BSC timer triggered during the immediate assignment procedure. Use
the suggested system value.
It is set on transmission of CHANNEL ACTIVATION by the BSC and
cancelled on receipt of ESTABLISH INDICATION sent by the BTS.
Object: bts
Default value: 3
Type: DP, System
Rec. value: 3
Used in:
Eng. Rules: Most of the time, the timer expires in the case of double allocation (i.e,
when two RACHs are sent by the same mobile to the network). The
higher the timer is the longer unnecessary signaling resources are
reserved. Up to 30% of signaling resources are allocated for a second
RACH for phase 1 MS according to numberOfSlotsSpreadTrans (32).
To optimize signaling resources (especially in case of Queuing), it
could be useful to decrease the timer value. The minimum time
between the two messages is 600 ms and the maximum for a lightly
loaded BSS is almost 1.8 seconds when MS is answering.
Nortel confidential

t3103 Class 3 V7
Description: BSC timer triggered during the handover procedure. Use the
suggested system value.
It is set on transmission of HANDOVER COMMAND by the BSC and
cancelled on receipt of either HANDOVER COMPLETE or
HANDOVER FAILURE sent by the MS (intra–bss handover), or
CLEAR COMMAND sent by the MSC (inter–bss handover). At expiry
of T3103, the channel is released.
Value range: [2 to 255] seconds (t3103 < bssMapT8)
Object: bts
Default value: 5 seconds
Rec. value: 9 seconds
Used in:
Eng. Rules: The longest procedure (inter BSS handover) is taken as an example.
The timer is set on receipt of the HO command and reset on clear
complete. It means that as long as the timer runs, 2 channels are
kept: one on the originating BSC and one on the target BSC. If the
timer is too long, two resources are used which can be a bad in case
of capacity problems.
Tests showed that t3103 set to 9 seconds offers the best compromise
between the execution of the procedure and the hold of ressources.
t3107 Class 3 V7
Description: BSC timer triggered during the assignment command procedure. Use
It is set on transmission of ASSIGN COMMAND by the BSC and
cancelled on receipt of either ASSIGN COMPLETE or ASSIGN
FAILURE sent by MS.
Object: bts
Rec. value: 10 seconds in a network without any capacity problems.
If not, the value can be decreased. The minimum theoretical
value is 5 seconds.
Used in:
Eng. Rules: At expiry of the timer, the mobile is assumed to be lost and its
resource can be used by another mobile. Mobile on SDCCH is a
constraining case: the timer T200 leads to a 230 ms wait instead of
180 ms on TCH, before repeating a message. If no message is
repeated, this procedure lasts about 1 second. However, if the radio
link is bad, it is necessary to repeat some messages. The maximum
time before resetting t3107 is approximately 5 seconds: after this time,
the timer will expires: no new message will be received to reset t3107.
The default value of 10 seconds is then a good value to ensure that
the link is not cut too early.
Nortel confidential

t3109 Class 3 V7
Description: BSC timer triggered during the SACCH deactivation procedure. Use
It is set on receipt of DEACTIVATE SACCH ACKNOWLEDGE sent by
the BTS and cancelled on receipt of RELEASE INDICATION sent by
the BTS. If the timer expires, a RF CHANNEL RELEASE message is
sent to the BTS and a RF CHANNEL RELEASE ACK is expected.
Mobiles comply with system operating conditions when the counter
(S) associated with SACCH messages is assigned a value below or
equal to t3109.
Value range: [2 to 255] seconds (t3109 ≥ radioLinkTimeout)
Object: bts
Rec. value: 12 seconds (related to radioLinkTimeOut value)
Used in:
Eng. Rules: On receipt of the Deactivate SACCH message, the radio link control
algorithm will lead to a decrease on the value of the
‘radioLinkTimeOut’ timer and this on MS side or on BTS side
according to the situation. t3109 added to t3111 must be greater than
radioLinkTimeOut and greater than the time corresponding to rlf1:
t3109 ≥ radioLinkTimeOut
If t3109 is too small, the ressources could be allocated even if
radiolinkTimeOut did not reach zero yet.
LCAUTION! When AMR is activated that parameter should be set to 17.
t3111 Class 3 V7
Description: BSC timer triggered during the radio resource clearing procedure. Use
It is set on receipt of RELEASE INDICATION sent by the BTS. On
elapse, the BSC sends RF CHANNEL RELEASE.
Object: bts
Type: DP, System
Used in:
Eng. Rules: This timer is used to delay the channel deactivation after
disconnection of the main signalling link. Its purpose is to allow time
for the possible repetition of the disconnection by the BTS to the MS.
After Release Indication, resources are kept until t3111 expires. In
case of capacity problems, t3111 must be as little as possible. The
smallest possible value is 2 seconds (range 2-255 seconds).The
minimum theoretic value is 5 times the repetition time which is less
than 2 seconds No advantage has been found to have a higher value
than the smallest possible one.
This timer is also used in the formula to compute the preemtion timer :
Tpreempt = Tdeactack + 4* T3111
Nortel confidential

t3122 Class 3 V7
Description: Minimum time that mobiles must wait before issuing a channel
allocation request when an immediate assignment has failed. In a
similar way, in GPRS mode, this value is indicated in the Packet
Access Reject (PAREJ) to inform the MS with the waiting time before
sending a new Channel Request. The timer is called T3172 in GPRS
mode, with T3172 = T3122.
Object: bts
Used in:
Eng. Rules: This value is broadcast to the mobile stations. When an immediate
assignment reject command is received (when no SDCCH and no
TCH in signalling mode is available or when the A-interface is down),
mobile stations wait t3122 seconds before sending the request again.
In case of BSC Overload, t3122 is automatically increased or
decreased between its value set by O&M and 30s according to a
specific algorithm.
This parameter can be used to solve a problem of a load pick. By
increasing the value, the access to the network is regulated.
timerPeriodicUpdateMS Class 3 V7
Description: Time between two location update requests
Value range: [0 to 255] 1/10th of hour. “0” means that no periodic location update is
requested.
Object: bts
Default value: 60
Rec. value: 10 (not loaded network)
20 (loaded network)
Used in:
Eng. Rules: Location updatings are performed when initiating a call or when
entering a new location area in idle mode. When those events do not
occur, timerPeriodicUpdateMS is used to ensure a maximum time
between two location update requests. The value of this timer should
be set regarding the value of the same timer used in the switch
(‘attach mobile audit’ for a DMS)
If the value chosen is low, the load of the BSC is severely increased.
On the contrary, a too high value would lead to a smaller reactivity of
the mobile (e.g. if a mobile is in a hole of coverage and a short
message is sent to it, it will be aware of it only at the next location
update which could be several hours later). A good trade-off is 2
hours.
Nortel confidential

5.24. PAGING PARAMETERS
delayBetweenRetrans Class 2 V8
Description: Number of occurences of a paging sub–group that separates two
transmissions of the same paging message.
Object: bts
Default value: 0
Rec. value: 0
Used in: Paging command repetition process (run by BTS) (Pag_rep)
Eng. Rules: The recommended value is 0 because the time between two paging
commands broadcast must not be too long, otherwise there is a risk of
double allocation. This phenomenon occurs when the suscriber
answers and hangs up very quickly. In that case, the mobile is ready
to receive a new paging message, for example the previous one if it is
resent. The value of this parameter is linked to the values of the
nbOfRepeat and retransDuration parameters. Furthermore, the
following inequality, that is not checked by the system, must be true:
retransDuration ≥ (delayBetweenRetrans + 1) x nbOfRepeat
maxNumberRetransmission Class 3 V8
Description: Maximum number of RACH burst retransmissions allowed in a call in
case of non-system response. The information is broadcast to the
mobiles at regular intervals on the cell BCCH. It defines the maximum
number of times a mobile can renew access requests to the BTS on
RACH.
Value range: [one / two / four / seven]
Object: bts
Default value: two
Rec. value: two in non-interfered areas
four in interfered areas
Used in: Request access command repetition process (RA_rep)
Eng. Rules: In interfered areas, it is necessary to repeat RACHs because of bad
conditions. Even if it increases a little overall noise, the gain in
decreasing the number of RACHs not received should be significant
(under study). In non-interfered areas, the value of ‘two’ is sufficient.
‘one’ is not advised because mobile stations can be in holes of
coverage due to multipath fading and, in these cases, at least one
retransmission is necessary.
Nortel confidential

nbOfRepeat Class 2 V8
Description: Maximum number of times that paging messages are repeated to
mobiles that belong to the same paging sub-group
It is set to “3” in former BSS versions (static configuration parameter).
The following inequality, that is not checked by the system, must be
true (refer to these entries in the Dictionary):
Object: bts
Default value: 3
Eng. Rules: The value of 3 ensures a good quality of service. With less repetition,
paging messages can be lost, and, as the repetitions are performed
systematically, a signicantly higher value would increase the load of
the system and the risk to page a mobile twice. The value of this
parameter is linked to the values of the delayBetweenRetrans and
retransDuration parameters.
That parameter can be tuned regarding the paging parameters and
the TDMA configuration, but very cautiously with some metric
monitoring (see chapter GSM Paging Repetition Process Tuning)
noOfBlocksForAccessGrant Class 2 V7
Description: Number of CCCH blocks not used for paging
A BCCH is combined when it shares the same radio time slot with four
SDCCHs, which can include a CBCH (refer to the channelType entry
in the Dictionary). In that case, the attribute value is no greater than to
2 (the value must be checked by users).
Value range: [0 to 2] if the cell uses a combined BCCH,
[1 to 7] otherwise.
“0” means that PCH blocks are used for sending immediate
assignment messages as and when needed.
Object: bts
Default value: 0
Type: DP, System
Rec. value: 0 if no SMS-CB or SMS-CB with combined BCCH
1 if SMS-CB with non-combined BCCH
> 0 if SI2Quater or/and SI13 on ext BCCH are activated
Used in: Paging command Process (Pag)
Effects of SMS-Cell Broadcast Use on “noOfBlocksForAccessGrant”
SI2Quater & SI13 on Extended or Normal BCCH
Eng. Rules: See also chapter GSM Paging Repetition Process Tuning.
Nortel confidential

noOfMultiframesBetweenPaging Class 2 V7
Description: Number of occurrences of a paging sub–group
The greater this number, the greater the number of paging sub–
groups.
Value range: [2 to 9] multi–frame of fifty-one frames
Object: bts
Default value: 6
Rec. value: 6 for rural environments
2 or 4 for urban environments
Used in: Paging command Process (Pag)
Eng. Rules: This parameter has an impact on the use of mobile batteries
(determine when an MS needs to listen to paging channels) and on
reselection selectivity. For this operation, frequency of measurements
performed on idle neighbours thanks to the formula: mesurements
done every Max (5 seconds, ((5*nb of idle neighbors + 6) DIV 7) *
noOfMultiframesBetweenPaging /4).
Regarding mobile batteries, a value of 6 is sufficient to have a trade-
off between the saving of energy and effective paging. In rural
environments, the maximum size of reselection list is usually 4/5. 5
seconds is then the maximum in the formula, so it does not slow down
the reselection mechanism. The value of 6 is then advised.
In urban environments, the size of the list is a bit higher. Furthermore,
in this kind of environment, reselection reactivity is a key issue. The
way to avoid having more than 5 seconds in the formula is to
decrease noOfMultiframesBetweenPaging to 2 or 4 even if it
increases battery consumption. Some studies are in progress to
determine the value with more accuracy.
See also chapter Effects of “noOfMultiFramesBetweenPaging” on

Mobile Batteries and Reselection Reactivity.
Nortel confidential

numberOfSlotsSpreadTrans Class 3 V7
Description: Number of radio time slots over which RACH transmission access are
spread in a random way to avoid collisions
cell BCCH. In the event of non-system response, the mobile will
renew the RACH bursts after a randomly defined period that varies
with numberOfSlotsSpreadTrans.
MS Phase 1
The time T between two transmissions of the same RACH burst is the
following:
T= [D + (N+1) x 4.615]ms
D is the maximum system response pending time:
D= 250 ms for BCCH not combined (i.e. 55 time slots)
D= 350 ms for BCCH combined (i.e. 77 time slots)
N is the randomly number generated by the mobile in the range [0
to numberOfSlotsSpreadTrans-1]
4.615 ms is the time occupied by a time slot.
MS Phase 2
The time T between two transmissions of the same RACH burst is the
following (whatever the BCCH is combined or not):
T= 4.615 x [S+(N + 1)] ms where
S is a parameter depending on the BCCH configuration and on the
value of numberOfSlotsSpreadTrans (see table hereafter)
N is the randomly number generated by the mobile in the range [0
to numberOfSlotsSpreadTrans-1]
4.615 ms is the time occupied by a time slot.
S on non-combined S on combined
numberOfSlotsSpreadTrans
BCCH BCCH
3, 8, 14, 50 55 41
4, 9, 16 76 52
5, 10, 20 109 58
6, 11, 25 163 86
7, 12, 32 217 115
Value range: [3 to 12, 14, 16, 20, 25, 32, 50] time slots
Object: bts
Default value: 32
Rec. value: 32
Used in: Request access command repetition process (RA_rep)
Eng. Rules: From Rec 04.08, numberOfSlotsSpreadTrans has a different meaning
for phase 1 and phase 2 mobiles. For phase 1 mobiles, if the value is
too small, two resources may be allocated to the same mobile (double
allocation). For phase 2 mobiles, it is different. The best trade-off is to
take “32” which is very good for phase 2 mobiles and not too bad for
phase 1 mobiles.
The choice will depend on the quantities of GSM phase 1 and GSM
phase 2 mobiles.
Nortel confidential

For Mobile phase 1, numberOfSlotsSpreadTrans = 50 leads to the

lower double allocation rate.
For Mobile phase 2, numberOfSlotsSpreadTrans = 6, 7, 11, 12, 25, 32
(respectively 5, 10, 20) for BCCH combined (respectively BCCH not
combined) leads to the lower double allocation rate.
Therefore, for a network that handles a combination of both types of
mobiles, numberOfSlotsSpreadTrans should be set to 32 (default
value).
pagingOnCell Class 3 V9
Description: Enable or disable paging requests in a cell
Object: bts
Rec. value: enabled but can be disabled on special occasions (see
Engineering Rules)
Used in: PCH and RACH channel control
Eng. Rules: When pagingOnCell is set to disabled, the BSC does not send any
PAGING_COMMAND to the cell. This feature is used when operators
want to forbid mobile terminated call set-up in specific cells. It can be
useful during special events or in places like cinemas, theaters...
retransDuration Class 2 V8
Description: Maximum number of occurrences of a same paging sub-group that
separates the first and the last transmissions of the same paging
message.
Object: bts
Default value: 10
Rec. value: 10
Eng. Rules: If many paging commands must be broadcast, repetitions of old
paging messages are delayed because fresh paging has a higher
priority. Therefore, repetitions could be so delayed that it leads to
double paging. By setting this parameter to an accurate value
retransDuration , the risk of sending very old paging messages is
limited. Anyway, the value of this parameter is linked to the ones of
nbOfRepeat and retransDuration. Furthermore, the following
inequality, that is not checked by the system, must be true:
Nortel confidential

5.25. FREQUENCY HOPPING PARAMETERS
bscHopReconfUse Class 1 V8
Description: Whether frequency hopping reconfiguration is authorized in BTSs that
use cavity coupling
When frequency reconfiguration is authorized, it allows to
automatically reconfigure the hopping sequence whenever a
frequency is lost or recovered in the BTS.
This parameter is only useful if there is at least one BTS with cavity
coupling in the BSS. Otherwise its effect is neutral regardless of the
value.
Object: bsc
Default value: true
Type: DP, Design
Rec. value: true for a BSC that manages at least one BTS using cavity
coupling
The value (true or false) is indifferent for a BSC that manages
only BTS with hybrid coupling
Used in: Reconfiguration procedure
Eng. Rules: If the value is ‘True’ then the value of btsHopReconfRestart (bts
object) must be true in case of cavity coupling in the BTS.
However, when enabling frequency hopping, it is advised to use
hybrid coupling and synthesized frequency hopping.
In order to facilitate the further use of frequency hopping in the
network, the parameter bscHopReconfUse can be set to “True”,
even if frequency hopping is not used yet.
btsHopReconfRestart Class 2 V8
Description: Whether hopping frequency reconfiguration is authorized on TX
restarts in a cell
Object: bts
Default value: true
Rec. value: true (for a BTS using cavity coupling)
false (for a BTS using hybrid coupling)
Eng. Rules: If the value is ‘True’ then the value of bscHopReconfUse must be true.
However, when enabling frequency hopping, it is advised to use
hybrid coupling and synthesized frequency hopping.
With cavity coupling, in order to facilitate the further use of
frequency hopping in the network, the parameter
btsHopReconfRestart can be set to “True”, even if frequency
hopping is not used yet.
Nortel confidential

btsIsHopping Class 2 V7
Description: Whether frequency hopping is allowed in a cell
Value range: [hopping / noHopping / hoppingWithCarrierFilling /
noHoppingWithCarrierFilling]
Object: bts
Default value: Hopping
Type: DP, Design
Rec. value: Hopping
Used in: Frequency Hopping
Eng. Rules: The two main advantages of using Frequency Hopping are interferer
and frequency diversities. Enabling frequency hopping allows to adapt
and maximize the frequency reuse efficiency by maximizing the
capacity in terms of offered Erlang/MHz/km². Moreover, enabling
frequency hopping makes easier the task of frequency planning and
TRXs addition. Although when using DTX there is a few number of
RxQual measurements, there is no need to disable handovers on
quality criteria, as no degradation was observed.
LCAUTION! When TRX are hopping, it is highly recommended to modify some
TDMA configuration. Channel SDCCH must be set on time slot 1 of
the concerned TDMA. Moreover this modification can be introduced
before enabling frequency hopping.
LCAUTION! It is also recommended not to use Power Control with Frequency
Hopping in case of cavity couplers. Indeed, with cavity couplers, the
BCCH frequency can be part of the Mobile Allocation List (that is not
possible in case of Hybrid couplers) and then the gap between the
emitted power of two adjacent bursts could be at its maximum.
Remark: Except this particular case (cavity coupler + FH + PWC) there is no
restriction in combining Frequency hopping with Power Control.
btsThresholdHopReconf Class 2 V8
Description: Minimum number of frequencies that must be working in a cell to allow
frequency hopping reconfiguration. If this attribute defines the nominal
number of cell frequencies, the reconfiguration process is deactivated.
Refer to the btsHopReconfRestart parameter.
Object: bts
Default value: 1
Rec. value: 1
Eng. Rules: This parameter is checked before reconfiguration is started, for cavity
coupling. If there are less remaining frequencies than the value of this
parameter, the cell is deconfigured. The minimum value (1) allows a
cell to be reconfigured even if there is only one frequency still
available.
Nortel confidential

cellAllocation Class 2 V7
Description: List of no more than 64 frequencies allocated to a cell in the network
frequency band.
Normally, the maximum number of frequencies that can be set up with
this parameter is 64 per frequency band. However, due to SI13 size
constraints, when GPRS or EDGE is activated in the cell and there is
at least one hopping data TDMA, the limitation becomes a maximum
of 55 frequencies (in V15.0 and V15.0.1) ,52 frequencies (in V15.1
and V15.1.1), 49 frequencies (from V16).
By definition, all cells covered by a given radio site use the same
frequency band defined by the type of the network (standardIndicator).
All cells declared as neighbor cells of a serving cell use the same
frequency band as the serving cell.
Value range: [1 to 124] (GSM 900 network),
[975 to 1023] & [0 to 124] (E-GSM network),
[955 to 1023] & [0 to 124] (GSM-R network),
[512 to 885] (GSM 1800 network),
[512 to 810] (GSM 1900 network)
[128 to 251] (GSM 850 network)
Object: bts
Default value:
Used in:
Eng. Rules: This list must include all the frequencies used by TRX of the cell, even
the BCCH frequency and shall respect following rules:
With cavity couplers, two (2) consecutive frequencies must be
spaced of at least 600 kHz in order to avoid interference
With hybrid couplers, considering UL power control activated:
in case of intra cell and intrasite configuration Nortel recommends
400kHz frequency spacing between TRX with or without frequency
hopping.
in case of intersite configuration, 200kHz frequency spacing are
necessary between TRX with or without frequency hopping.
These frequency spacings (400kHz in intrasite and intracell, 200kHz
in intersite) guarantee a minimum of 12dB in C/I. This can provide
certain quality of service. With particular applications (e.g. EDGE), an
upper frequency spacing is needed (600kHz for EDGE).
It is recommended to declare only 1 hopping frequency list by band
(the use of the frequency band is optimal with all hopping
frequencies in the same list and it is much easier for OAM).
If at least one of the cell allocation ARFCN is in the range [975;
1023] & [0], the BCCH should be in that range also (this monoband
EGSM cell does not support monoband PGSM MS nor dualband
PGSM/DCS1800 MS), else BCCH should be a PGSM one.
Nortel confidential

LCAUTION! When setting CellAllocation, a check is performed at OMCR in order to

verify the number of frequencies. This number is limited by the spread
of frequencies
• if 1 =< spread of frequencies =< 112

Then max number of frequencies = 64
The spread of frequencies is the maximal distance between the value
of frequence calculed as (Fmax – Fmin +1).This spread of frequencies
verification is performed for each band separately. For standard
indicators like e-gsm and r-gsm, which have 2 ranged bands, the
following must be taken into account:
For E-GSM the range is [0..124]U[975..1023] ; so by realigning the
frequence the result is [975…1022, 1023, 1,..124]. the distance for
example100 and 1000 is 125 (not 901) because:
100 belongs to [0...124] spread of frequencies is 101
1000 belong to [975…1023] spread of frequencies is 24
fhsRef Class 2 V7
Description: Identifier of the frequencyHoppingSystem object that defines the
frequency hopping management parameters for the radio time slot
Setting this attribute and the maio attribute allows the time slot to obey
frequency hopping laws.
Object: channel
Default value:
Used in:
Eng. Rules: It is advised to use only one (1) fhsRef per cell (when the Mobile
Allocation is the same for all its TRX), because it is time saving for
creation at the OMC.
Nortel confidential

hoppingSequenceNumber Class 2 V7
Description: Hopping sequence number used by a radio time slot which obeys
frequency hopping laws.
Select different HSNs for nearby cells that use the same set of
frequencies.
Object: frequencyHoppingSystem
Default value:
Used in: Synthesised frequency hopping
Eng. Rules: In case of synthesized frequency hopping, whatever the fractional
reuse pattern for TCH, using a unique HSN per site allows to avoid
frequency collisions. However, it leads to a specific MAIO plan, more
restricting than with the use of different HSN in cells (needs more
frequencies). Indeed, the frequency load would be higher with
different HSN. But it is possible to reach the maximum fractional load
(value limited by RF constraints to 16,6 % for 1X1 pattern and 50 %
for 1X3 pattern in case of no intra-site collision). When intra-site
collision is allowed, field experience has shown that with an
appropriate tuning of the parameters, 1X1 can go up to 20% fractional
load and 1X3 up to 58% while keeping a very good quality for the
offered capacity.) with a unique HSN per site and then systematically
avoiding frequency adjacencies.
See also chapter General Rules For Synthesised Frequency Hopping
maio Class 2 V7
Description: Index in the list of frequencies allotted to a radio time slot, which
obeys frequency hopping laws.
Setting this attribute, together with the fhsRef attribute, allows the time
slot to obey frequency hopping laws.
Value range: [0 to N-1] N is the number of frequencies allotted to the time slot.
Object: channel
Default value:
Eng. Rules: The MAIO must be different for each TRX within a cell in order to
avoid frequency collision. If the Mobile Allocation contains adjacent
frequencies, the difference between two TRX MAIO within a cell must
be greater or equal than two (2).
However, for a 1X3 pattern, it is possible to use the same MAIO
sequence in all cells of a same site. Moreover, for such a pattern, if
each list of MA frequencies does not contain adjacent frequencies,
adjacent MAIO can be used.
For a 1X1 pattern, different MAIO for each TRX must be used and no
adjacent MAIO if there are adjacent frequencies in the MA list.
See also chapter General Rules For Synthesised Frequency Hopping
Nortel confidential

mobileAllocation Class 2 V7
Description: List of frequencies allocated in the network frequency band to a radio
time slot which obeys frequency hopping laws.
Normally, the maximum number of frequencies that can be set up with
this parameter is 63 i.e. 64 – BCCH frequency. However, due to SI13
size constraints, when GPRS or EDGE is activated in the cell and
there is at least one hopping data TDMA (carrying at least one
PDTCH), the limitation becomes a maximum of 55 – n frequencies (for
V15.0 and V15.0.1) or 52 – n frequencies (for V15.1 and V15.1.1),or
49 – n frequencies (from V16) where n is the number of non-hopping
frequencies in the cell.

[975 to 1023] & [0 to 124] (E-GSM network),
[955 to 1023] & [0 to 124] (GSM-R),
[512 to 885] (GSM 1800 network),
[512 to 810] (GSM 1900 network)
[128 to 251] (GSM 850 network).
Object: frequencyHoppingSystem
Baseband Frequency Hopping
Eng. Rules: This list must include all the hopping frequencies used by a TRX. As
the first TRX of a cell does not hop, it is not related to a MA (TRX
channels frequency is BCCH).
The following TRXs may have a common MA containing all the
hopping frequencies (not including the BCCH frequency).
With cavity couplers, two (2) consecutive frequencies must be
spaced of at least 600 kHz in order to avoid interference, because
of material constraints.
With hybrid couplers, considering UL power control activated:
in case of intra cell and intrasite configuration Nortel recommends
400kHz frequency spacing between TRX with or without frequency
hopping.
in case of intersite configuration, 200 kHz frequency spacing are
necessary between TRX with or without frequency hopping.
These frequency spacings (400kHz in intrasite and intracell, 200kHz
in intersite) guarantee a minimum of 12dB in C/I. This can provide
certain quality of service. With particular applications (e.g. EDGE), an
upper frequency spacing is needed (600kHz for EDGE).
It is recommended to declare only 1 hopping frequency list by band
(the use of the frequency band is optimal with all hopping
frequencies in the same list and it is much easier for OAM).
Nortel confidential

trafficPCMAllocationPriority Class 2 V9
Description: Allocation priority of a TDMA frame on the covering site PCMs
This attribute is used in case of Abis PCM reconfiguration.
Object: transceiver
Default value:
Rec. value: 255 for the TDMA supporting the BCCH
0 for the others
Used in:
Eng. Rules: see chapter SDCCH Dimensioning and TDMA priorities.
zoneFrequencyHopping Class 2 V9
Description: Whether frequency hopping is authorised in the zone.
If frequency hopping is not allowed in a zone, a channel objects that
describe the radio time slots of the TDMA frames used in the zone
cannot be allowed to hop.
Value range: [hopping / not hopping]
Default value: not hopping
Type: DP
Used in:
Eng. Rules: In case of a dualband cell and if PDTCHs are configured on the inner
zone, that parameter must be set to “not hopping” on the
transceiverZone corresponding to the inner zone.
In any other case that parameter must be set to “hopping”.
zoneFrequencyThreshold Class 2 V9
Description: Minimum number of frequencies needed to allow frequency
reconfiguration in the zone.
Default value: 1
Type: DP
Rec. value: TBD
Used in:
Eng. Rules:
Nortel confidential

5.26. BSC LOAD MANAGEMENT PARAMETERS
processorLoadSupConf Class 3 V8
Description: Threshold used in the load control algorithm by the BSC
Value range: [0] The only accepted value is 0 (outOfRangeError).
Object: bsc
Default value: 0
Rec. value: 0
Used in: Mechanism up to V11
Mechanism defined from V12
Eng. Rules: This parameter was used before V12 release only to control the load
on the BSC CPU boards.
LCAUTION! This parameter is valid for BSC12000 only.
estimatedSiteLoad Class 3 V15

Description: This parameter is used:
at site creation, in order to preset the erlang consumption of the
new Cell Group
ortherwise, in order to set the erlang consumption
Value range: [0 to 1100] erlangs. 1100 is the internal erlang capacity of a TMU2.
Object: btsSiteManager
Default value: 0
Type: DP
Used in: V15.1 Evolution of Load Balancing
Eng. Rules: It is usually recommended to try to set the estimatedSiteLoad of a site
at the creation of this site (with the maximum configuration wanted for
this site) to be sure that at this time the global dimensioning of the
BSC is correct.
It may also help in handling exceptional events on some parts of
the network.
LCAUTION! This parameter is available only from V15.1
Nortel confidential

5.27. DUALBAND CELL PARAMETERS
early classmark sending Class 3 V10

Description: Whether Early classmark sending procedure initiated by a multiband
mobile and/or a 2G-3G mobile is allowed.
cell BCCH (SYSTEM INFORMATION n°3).
Value range: [Not Allowed, Allowed]
Object: bts
Default value: Not Allowed
Type: DP, Design
Rec. value: Allowed
Used in: Modified SYS INFO 3
Location Services
GSM to UMTS handover (v17)
Eng. Rules: When this parameter is set to “allowed”, the mobile sends the
Classmark_Change message just after the SABM and UA frames
exchanged during the Immediate_Assignment procedure. This
message enables interband handover procedures (handovers on TCH
and SDCCH, Directed Retry); Morever this parameter allows the
mobile to send its capacity downlink Advanced Receiver performance.
In GSM cells where handover to UTRAN is possible, or UTRAN
measurement reporting is expected from the mobile, the "early
classmark sending" must also be requested from the mobile.
Therefore, if the operator is interested to have the SAIC mobile
penetration, it is recommended to set this parameter to “Allowed”
In single band networks where no handover to 3G is required, “early
classmark sending” will be set to “not allowed”.
In dual-band networks and in networks where handover to 3G may be
requested, then early classmark sending will be set to “allowed”.
multi band reporting Class 3 V10

Description: Indication of the number of cells to be reported for each GSM
frequency band in multiband operation. This parameter is used both
for normal and enhanced measurement reporting.
Value range: [0 : “no outband cell is favoured” / 1 : “1 strongest outband cell is
favoured” / 2 : “2 strongest outband cells are favoured” / 3 : “3
strongest outband cells are favoured”
Object: bts
Default value: 0 : “no outband cell is favoured”
Rec. value: “two strongest outband cells are favoured” (case of privileged
band)
”no outband cell is favoured” (case of no privileged band)
Used in: Multiband reporting
Enhanced Measurement Reporting (EMR)
Nortel confidential

Eng. Rules: For values indicating the one (1), two (2) or three (3) strongest cells
out band, the multiband MS respectively reports the one, two or three
strongest allowed cells outside the current frequency band. The
remaining space in the report (at least 5, 4 or 3 cells) is used to give
information about cells in the current frequency band. If there are still
some remaining positions, they are used to report cells outside the
current frequency band.
When the operator wants to privilege one of the frequency band, it is
advised to report two (2) cells outside the current frequency band, for
cells in the privileged frequency band. Then, neighbour cells in the
priority frequency band will be privileged.
Actually, if multibandReporting is set to “1”, the risk is to report five (5)
priority frequency band neighbour cells with a bad quality or signal
strength (near priority frequency band boundaries for example) and
one (1) good neighbour cell in the low priority frequency band, but
under congestion. Thus the MS will not make a handover toward a
good neighbour cell and the quality of service may be impacted.
For cells outside the privileged frequency band, it is advised to report
three (3) cells outside the current frequency band. Thus, it ensures the
report of all (if less than 3) or at least three (3) neighours in the priority
frequency band.
In case no frequency band is preferred, the report of the “the six
strongest cells” allows to make a handover toward the best neighbour
cell, whatever the current cell is.
In case of 2G-3G handover being enabled, and EMR disabled (use of

normal measurement reporting), it is necessary to exercise caution
when setting the parameters fDDMultiRatReporting and
multiBandReporting . These parameters define the number of UTRAN
cells and non-serving band GSM cells, respectively, that must be
included by the mobile in the list of strongest cells in the measurement
report. Therefore it leaves (6 - fDDMultiRatReporting -
multiBandReporting ) spaces for the serving band GSM cells.
Therefore, if EMR is disabled, it is recommended not to exceed
fDDMultiRatReporting = 2 and multiBandReporting = 2.
standard indicator AdjC Class 3 V10

Description: Type of network in which this neighbour cell is working
Value range: [gsm / extended gsm / dcs1800 / pcs1900 / R gsm / gsmdcs (V12) /
dcsgsm (V12) / gsm850 / gsm850pcs / pcsgsm850]
Object: adjacentCellHandover
Default value: gsm
Rec. value: extended gsm if available in the network. See Engineering Rules
Used in: Oher procedures (Dual Band Handling)
Eng. Rules: The indicates standard indicator must have the same value in
adjacentCellHandover or adjacentCellReselection objects and in the
associated neighbour bts object.
Refer to the standardIndicator parameter engineering rules to get
more information about neighbours management.
LCAUTION! “gsmdcs” and “dcsgsm” are only available for S8000 DRX transceiver
architecture.
“eGSM” is only available for S8000 CBCF transceiver architecture.
Nortel confidential

standard indicator AdjC Class 3 V10

Description: Type of network in which this neighbor cell is working
dcsgsm (V12) / gsm850 / gsm850pcs / pcsgsm850]
Object: adjacentCellReselection
Default value: gsm
Rec. value: extended gsm if available in the network. See Engineering Rules
Used in: Oher procedures (Dual Band Handling)
Eng. Rules: The standard indicator must have the same value in
adjacentCellHandover or adjacentCellReselection objects and in the
associated neighbour bts object
Refer to the standardIndicator parameter engineering rules to get
more information about neighbours management.
LCAUTION! “gsmdcs” and “dcsgsm” are only available for S8000 DRX transceiver
architecture.
“eGSM” is only available for S8000 CBCF transceiver architecture.
bCCHFrequency Class 3 V7
Description: Radio frequency allocated to a neighbour cell BCCH in the network
frequency band.
The information is broadcast on the serving cell SACCH.
[512 to 885] (DCS 1800 network),
[512 to 810] (PCS 1900 network),
[955 to 1023] & [0 to 124] (R–GSM network),
[975 to 1023] & [0 to 124] (E–GSM network),
[128 to 251] (GSM 850 network).
Type: DP
Rec. value:
Used in:
Eng. Rules:
Description: Radio frequency used for selection and reselection management. The
information is broadcast on the serving cell BCCH.
Value range: [1 to 124] (GSM 900 network ),
[512 to 885] (DCS 1800 network),
[512 to 810] (PCS 1900 network),
[975 to 1023] & [0 to 124] (E–GSM network).
Object: adjacentCellReselection
Type: DP
Nortel confidential

Rec. value:
Eng. Rules:
Note: An adjacentCellReselection object can use the same BCCH as the
serving cell to which it is associated. This allows a mobile to
immediately recover the cell on which it was “camping” after being
switched off, then switched back on, and is especially useful in the
selection process.
Description: Radio frequency allocated to a cell BCCH (Broadcast Control
CHannel) in the network frequency band.
The information is broadcast on the cell SACCH.
The BCCH frequency is automatically assigned to the radio time slot
carrying the cell BCCH when the cell is brought into service
(absoluteRFChannelNo attribute of the channel object describing the
carrier TDMA frame TS0). It is broadcast to the radio time slot
whenever modified.
The BCCH is used by the BTS for broadcasting cell related system
information to MS, such as frequency band and list of frequency
channels used, authorized services and access conditions, list of
neighbour cells, and radio parameters (maximum transmission
strength, minimum reception strength, etc).
Value range: [1 to 124] (GSM 900 network ),
[512 to 885] (DCS 1800 network),
[512 to 810] (PCS 1900 network),
[975 to 1023] & [0 to 124] (E–GSM network).
Object: bts
Type: DP
Rec. value:
Used in:
Eng. Rules: If at least one of the cell allocation ARFCN is in the range [975; 1023]
& [0], the BCCH should be in that range also (this monoband EGSM
cell does not support monoband PGSM MS nor dualband
PGSM/DCS1800 MS), else BCCH should be a PGSM one.
Nortel confidential

standardIndicator Class 2 V10

Description: Type of network in which the cell is working
From the value given to this attribute, the OMC–R determines the
network frequency band and the frequencies that can be used by all
radio entities (cells and radio time slots) in the related site.
dcsgsm (V12) / gsm 850 / gsm850pcs / pcsgsm850]
Object: bts
Type: DP
Rec. value:
Checks:
GSM 900 network (gsm)
The GSM 900 frequency band is 2*25 MHz wide and includes 124
pairs of carrier frequencies, numbered [1 to 124], which are 200 kHz
apart:
Uplink direction (MS–to–BTS) = 890 to 915 MHz
f1 = 890 + 0.2xN MHz where N = [1 to 124]
Downlink direction (BTS–to–MS) = 935 to 960 MHz
f2 = f1 + 45 MHz
GSM 850 network

pairs of carrier frequencies, numbered [1 to 124], which are 200 kHz
apart:
f1 = 824.2 + 0.2x N MHz where N = [1 to 124]
f2 = f1 + 45 MHz
EXTENDED GSM network (extended gsm)

The extended GSM frequency band is 2*35 MHz wide and includes
174 pairs of carrier frequencies, numbered [0 to 124] and [975 to
1023], which are 200 kHz apart:
f1 = 880.2 + 0.2x(N – 975) MHz where N = [975 to 1023]
f1 = 890 + 0.2xN MHz where N = [0 to 124]
f2 = f1 + 45 MHz
GSM–R network (R gsm)

The GSM–R frequency band is 2*39 MHz wide and includes 194 pairs
of carrier frequencies, numbered [0 to 124] and [955 to 1023], which
are 200 kHz apart:
f1 = 876.2 + 0.2x(N – 955) MHz where N = [955 to 1023]
f1 = 890 + 0.2xN MHz where N = [0 to 124
f2 = f1 + 45 MHz
GSM 1800 network (dcs1800)

Nortel confidential

pairs of carrier frequencies, numbered [512 to 885], which are 200
kHz apart:
f1 = 1710k2 + 0.2x(N – 512) MHz where N = [512 to 885]
f2 = f1 + 95 MHz
GSM 1900 network (pcs1900)

pairs of carrier frequencies, numbered [512 to 810], which are 200
kHz apart:
f1 = 1850.2 + 0.2x(N – 512) MHz where N = [512 to 810]
f2 = f1 + 80 MHz
GSM 900 – GSM 1800 network (gsmdcs)

The primary band is GSM 900
The secondary band is GSM 1800
GSM 1800 – GSM 900 network (dcsgsm)

GSM 850 – GSM 1900 network (gsmdcs)

GSM 1900 – GSM 850 network (dcsgsm)

Remark: The frequency bands defined hereabove are the definition of the
ETSI.
Eng. Rules:
As P-GSM range is included in E-GSM one, the following table gives
for each current cell standard indicator, the type (main or other) of
neighbouring cells according to their standard indicator:
standard indicator Adjc (neighbouring cell)
PGSM E GSM GSM 1800
GSM 900 main other other
standardIndicator
E GSM main main other
(current cell)
GSM 1800 other other main
If one of a cell ARFCN is in [975;1023] & [0] range, this monoband

EGSM (RGSM or EGSM) cell does not support monoband PGSM MS
nor dualband PGSM/DCS1800 MS.
If a EGSM cell has a BCCH in PGSM band, a PGSM mobile will listen
to it and may be handed over in that cell on a TCH in the E band. In
that case, the mobile will send a handover failure.
Sys-infos management:
Nortel confidential

According to recommendations, only « main » frequencies can be

present in the SI2 and SI2bis (resp. 5 and 5bis).
Following table gives the standard indicator of the neighbouring cells
that can be included in the different sys_info messages.
(extended gsm is noted EGSM in the table).
SYS_INFO
SI2 / SI5 SI2 bis / SI5 bis SI2 ter / SI5 ter
E GSM + GSM
GSM 900 GSM GSM if needed
1800 (1)
standardIndicator GSM + E GSM + E GSM if
E GSM GSM 1800
(current cell) GSM needed
GSM 1800 if
GSM 1800 GSM 1800 GSM + E GSM
needed
Note (1): In that case, the number of frequencies in the frequency list
is limited due to their large range.
=> Thus, due to the range of frequencies in EGSM + GSM 1800

bands, and the fact that only 1 message (ter) can contain such
neighbours info (if StandardIndicator = GSM), it is strongly
recommended to set the standard indicator of PGSM cells containing
EGSM neighbours to extended gsm (2 messages to encode EGSM
neighbours).
Nortel confidential

5.28. DTX PARAMETERS
cellDtxDownLink Class 3 V7
Description: Whether the use of discontinuous transmission in BTS–to–MS
direction is allowed in a cell
Object: bts
Used in: Downlink DTX
Eng. Rules: DTXDownLink is particularly interesting in case of low interfered
networks with fractional reuse patterns for frequency plan. In this
case, it is recommended to uses a reactive configuration with a short
delay between HO decision (runHandover=1) and with short average
windows (Hreqt = 1, HreqAve = 4). Ho margins can also be lowered.
LCAUTION! Using this feature may create a more sensitivity to bad values (fading,
frequencies collision). Activation of DTXDownlink when DTX is
already used leads to a diminution in the precision of the
measurement on the cell, on quality and on level.
dtxMode Class 3 V7
Description: MS control of the discontinuous transmission mechanism in a cell
Discontinuous transmission is designed to lessen MS battery
consumption and diminish interference by breaking off the
transmission when no data or speech are being transmitted.
Value range: [FRmsmayuseDTX / HRmsshallnotuseDTX, FRmsshalluseDTX /
HRmsshallnotuseDTX, FRmsmayuseDTX / HrmsmayuseDTX,
FRmsshallnotuseDTX / HRmsshallnotuseDTX, FRmsshalluseDTX /
HrmsshalluseDTX, FRmsshallnotuseDTX / HRmsshalluseDTX]
Object: bts
Default value: msMayUseDtx
Rec. value: msShallUseDtx
Used in: Uplink DTX
Eng. Rules:
LCAUTION! When AMR is activated that parameter should be set to
FRmsshalluseDTX / HRmsshalluseDTX
See also chapter Impact of DTX on Averaging
Nortel confidential

5.29. MISCELLANEOUS
Data14_4OnNoHoppingTs Class 3 V12

Description: Whether data 14.4 kbit/s transmission rate is allowed at bts level on
the non hopping TSs
Object: bts
Rec. value: TBD
Used in:
Eng. Rules:
data mode 14.4 kbit/s Class 2 V12

Description: Whether data 14.4 kbit/s transmission rate is allowed
Object: transcoderBoard
Type: DP
Rec. value: TBD
Used in:
Eng. Rules:
data non transparent mode Class 3 V12

Description: Set of transmission rates used for data non transparent mode
transmission of the Radio interface and Abis interface.
Value range: [9.6 / 14.4] (kbit/s)
Object: bts
Default value: 9.6 kbit/s
Type: DP
Rec. value: TBD
Used in:
Eng. Rules:
data non transparent mode Class 3 V12
Description: Set of transmission rates used for data non transparent mode
transmission of the Radio interface and Abis interface.
Value range: [9.6 / 14.4] (kbit/s)
Default value: 9.6 kbit/s
Type: DP
Rec. value: TBD
Used in:
Eng. Rules:
Nortel confidential

data transparent mode Class 3 V12

Description: Set of transmission rates used for data transparent mode transmission
of the Radio interface and Abis interface.
Value range: [“1.2/0.075” / 0.6 / 1.2 / 2.4 / 4.8 / 9.6 / 14.4] (kbit/s)
Object: bts
Default value:
Type: DP
Rec. value: TBD
Used in:
Eng. Rules:
data transparent mode Class 3 V12

Description: Set of transmission rates used for data transparent mode transmission
of the Radio interface and Abis interface.
Value range: [“1.2/0.075” / 0.6 / 1.2 / 2.4 / 4.8 / 9.6 / 14.4] (kbit/s)
Default value:
Type: DP
Rec. value: TBD
Used in:
Eng. Rules:
measurementProcAlgorithm Class 2 V12

Description: Whether the new L1M interface is used
Value range: [L1MV1, L1MV2]
L1MV1: the older L1M is used
L1MV2: the newer L1M is used
Object: bts
Rec. value: L1MV2
Direct TCH Allocation and Handover Algorithms
Eng. Rules: L1MV2 is not supported on DCU2.
It is not recommended to set L1MV2 on a DCU2/DCU4 BTS mixed
configuration since the enhancements offered will be available only on
part of the site so with a call processing not homogeneous on the
whole communications.
Major benefits are:
ability to support advanced capacity and coverage features such
as “Automated cell tiering”
capture process more reactive
less handover failure (better updating of eligible cells)
Nortel confidential

early decisions more accurate (0.5 s saved on the processing

delay of first measurements)
Refer also to chapter Layer 1 Management: Changes Between V1
and V2
siteGsmFctList Class 2 V7
Description: List of up to 14 elements that identify the GSM functions configured in
a site BCF
Value range: [entityMgt / download / siteMgt / abisSig / abisTraf / rfTrans / rfRecep /
cellMgt / fhMgt / tdmaMgt / tsMgt / gsmTime / car0Fil / freqMgt]
Default value: site Mgt/abisSig
Rec. value: [entityMgt / download / siteMgt / abisSig / abisTraf / rfTrans /
cellMgt / fhMgt / tdmaMgt / tsMgt]
Used in:
Eng. Rules: It is always useless to put the elements “rfRecep”, “gsmTime” and
“car0Fill” in the list because these functions are not yet implemented.
The function “freqMgt” must be included in the list only when using
cavity coupling.
It is advised to put the function “fhMgt” even if frequency hopping is
not used in the network, in order to avoid a class 2 parameter change
when introducing this feature.
Nortel confidential

5.30. INTERFERENCE CANCELLATION PARAMETERS
interferer cancel algo usage Class 2 V10

Description: Correlation ratio of the input signals received from the normal and
diversity antennas. This ratio enables to adapt the SPU software (the
interferer cancellation algorithm) to the propagation conditions.
Correlation ratio = 0 means that the interferer cancellation algorithm is
inactive.
Object: bts
Default value: 0
Type: DP, Design
Used in: Interference Cancellation
Eng. Rules: Three values are necessary and sufficient to cover the client’s needs
according to the sold options (it is quite unlikely that a more refined
fine-tuning will bring anything more):
- 0%: Maximum Ratio Combining (best pure thermal noise
sensitivity): no interference cancellation, minimum speed
correction.
- 50%: MRC when no interferers (same pure thermal noise
sensitivity as 0%): interference cancellation, medium speed
correction.
- 100%: Approximate MRC when no interferers: interference
cancellation, best speed correction.
See also chapter Interference Cancellation Usage.
diversity Class 2 V7
Description: Activation parameter of Receive diversity in a cell. This parameter is
used to control the activation of receive diversity and the choice of the
diversity uplink signal processing algorithm.
Value range: before v17.0 : “enabled”/”disabled”
In v17.0 and after : “enabled”/”disabled”/”enhancedDiversity”
Object: bts
Type: DP
Rec. value: see Eng. rules
Used in: Joint Diversity (v17) and Interference Cancellation. Note that Joint
Diversity is useful specifically for EDGE, not for speech services.
Please refer to aPUG document ([A1])
Eng. Rules: To activate the interference cancellation feature, diversity must be
activated.
1/ Before v17.0 :
Nortel confidential

diversity = “enabled”, provided diversity antenna(s) have been fitted to

the BTS.
diversity = “disabled” otherwise
2/ In and after v17.0 :

diversity = “enhancedDiversity”, for eDRX and Radio Module family,
provided diversity antenna(s) have been fitted to the BTS.
diversity = “disabled” in other cases.
Nortel confidential

5.31. PCM ERROR CORRECTION PARAMETERS

Note : this feature is no longer supported as of V17.
enhancedTRAUFrameIndication V12
Description: before V17 : Whether the BTS uses the Enhanced TRAU Frame
(ETF) for TCU
After V17 : This parameter is no longer useful in V17 as the feature
PCM Error Correction is no longer supported
Value range: [notAvailable / available / active]
Object: bsc
Default value: n/a
Type: DI, Optimization
Rec. value: n/a
Used in: PCM Error Correction
Eng. Rules: The PCM Error Correction is no longer supported as of BSS V17
release. This parameter is no longer useful and the OMC-R V17
automatically forces its value to “notAvailable”.
pcmErrorCorrection Class 2 V12

Description: Before V17 : whether the bts uses the new ETF (Enhanced TRAU
Frame) frame (set to “1”) or the ETSI “Rec 08.60” frame (set to “0”).
After V17 : This parameter is no longer useful in V17 as the feature
PCM Error Correction is no longer supported.
Object: bts
Default value: n/a
Rec. value: n/a
Used in: PCM Error Correction
Eng. Rules: The PCM Error Correction is no longer supported as of BSS V17
release. This parameter is no longer useful and the OMC-R V17
automatically forces its value to 0.
Nortel confidential

5.32. CELL TIERING PARAMETERS
enhCellTieringConfiguration Class 3 V14

Description: This attribute allows to configure the cell tiering algorithm at BTS level
instead of the cellTieringConfiguration attribute from V14 release
BSC.
This parameter is composed of the following five parameters:
hoMarginTiering
nbLargeReuseDataChannels
numberOfPcwiSamples
pwciHreqave
selfTuningObs
hoMarginTiering Class 3 V14

Description: Hysteresis between the uCirDLH and lCirDLH tiering thresholds. Used
to avoid ping-pong handovers (expressed in dB)
Default value: 4 dB
Rec. value: 4dB (to be optimized with the HO cell tiering monitoring)
Used in: Automatic cell tiering (from V12)
Eng. Rules:
interferenceType Class 3 V14

Description: It is used for identifying the type of interference created by a neighbor
cell. The possible values are not applicable (no interference), adjacent
interference or cochannel interference.
Value range: [notApplicable / adjacent / coChannel]
Default value: notApplicable
Rec. value: This parameter should be set according to frequency plan
strategy.
Eng. Rules:
Nortel confidential

nbLargeReuseDataChannels Class 3 V14

Description: Mean number of logical channels belonging to the large frequency
reuse pattern and used at the same time for data communications
Value range: [-16 to +16]
Default value: 0
Rec. value: To be determined according to configuration (see below)
Eng. Rules: This parameter gives the mean number of radio TS in the large reuse
pattern (BCCH) used for data communications (and consequently not
available for tiering).
nbLargeReuseDataChannels = number of timeslots dedicated GPRS
+ average number of timslots for 14.4 if the parameter data 14.4
OnNoHoppingTs is set to 1.
This last value can be obtained through the counters 1705/2 and
1707/2.
numberOfPwciSamples Class 3 V14

Description: Minimum number of PwCI samples required to reach a reliable
distribution (representative of the real distribution in the whole cell) *
1000
Default value: 20
Rec. value: 20. However, it is a deal between PWCI distribution refresh time
and accurancy (see below).
Eng. Rules: It gives the minimum number of PWCI samples required to reach a
reliable distribution of PWCI that will be representative of the real
distribution in the whole cell x 1000.
The number of samples before a PWCI distribution is undertaken is :
1000 x numberOfPwciSamples.
For example, in a cell bearing 29 TCHs and loaded at 75%, at each
moment, 0.75x29=21.75 TCHs are occupied. Then, every 480 ms
we’ll have 21.75 samples available and every second
(1000*21.75)/480=45.3 samples. If we set numberOfPwciSamples at
20, a PWCI distribution will be computed when 20000 samples will be
available, wich means that a PWCI distribution will be computed every
20000/45.3 = 441.5 seconds ( almost every 7 minutes and a half).
Nortel confidential

pwciHreqave Class 3 V12

Description: Averaging window size for PwCI. It defines the number of
measurement reports for a PWCI arithmetic averaging.
Default value: 8
Rec. value: 8
Eng. Rules: In a given cell, each communication in the cell reports its
measurements every 480 ms which allows computing the PWCI.
When 20000 samples are gathered in the cell, a distribution of all the
PWCI is computed and, lCirDLH and uCirDLH are determined for the
cell.
In order to take a tiering decision, a PWCI is averaged over a
pwciHreqAve window, for each communication and compared to
lCirDLH and uCirDLH obtained from the previous distribution, to lead
(or not) to a handover decision.
selfTuningObs Class 3 V12

Description: BTS mode of the sending the PwCI distribution on the Abis interface.
This allows a closer monitoring of the cell tiering feature behavior
once activated.
Value range: [pwCi distribution not sent,
pwCi distribution sent after gathering,
one pwCi distribution sent per hour]
Default value: pwCi distribution not sent
Rec. value: Other than “pwCi distribution not sent” when fine tuning the
feature, with close monitoring needed.
Eng. Rules: The possible values are pwCi distribution not sent (PWCI distribution
is gathered but not sent onto the Abis interface), pwCi distribution sent
after gathering (the distribution is sent each time a new tiering
threshold is computed for a maximum of 10 cells) or one pwCi
distribution sent per hour (the distribution is sent when a new tiering
threshold is computed but no more than one message every hour for
a maximum of 40 cells).
Remark: PWCI distribution may be gathered and sent onto the Abis interface
independantly of tiering activation.
Nortel confidential

5.33. ENCODING PARAMETERS
speechMode Class 3 V12

Description: List of the speech algorithms associated with channel use modes in
the cell
The “full rate” value refers to the standard algorithm. The “enhanced
full rate” value only applies when all the TCUs linked to the BSC are
equipped with TCB2 boards.
Value range: list of [algoid] where algoid id: full rate, enhanced, full rate, AMR full
rate, AMR half rate
Object: bts
Default value: [full rate, enhanced full rate]
Type: DP
Rec. value: [full rate, enhanced full rate]
Used in: AMR - Adaptative Multi Rate FR/HR
Eng. Rules:
LCAUTION! When AMR is activated, SpeechMode must be set to full rate,
enhanced full rate, AMR full rate, AMR half rate
speechMode Class 3 V12

Description: List of the speech algorithms associated with channel use modes on
the A interface. The “full rate” value refers to the standard algorithm.
The “enhanced full rate” value only applies when all the TCUs linked
to the BSC are equipped with TCB2 boards.
Value range: list of [algoid] where algoid id: full rate, enhanced, full rate, AMR full
rate, AMR half rate
Default value: [full rate, enhanced full rate]
Type: DP
Rec. value: [full rate, enhanced full rate]
Used in: AMR - Adaptative Multi Rate FR/HR
Eng. Rules:
LCAUTION! When AMR is activated, SpeechMode must be set to full rate,
enhanced full rate, AMR full rate, AMR half rate
Nortel confidential

5.34. SMS-CELL BROADCAST PARAMETERS
smsCB Class 3 V12

Description: Whether broadcasting of short messages in unacknowledged mode is
authorized in a cell.
Value range: [used / unused]
Object: bts
Default value: used
Type: DP
Rec. value:
Used in: SMS-Cell Broadcast
Eng. Rules: Configuration of logical channels and broadcast of short messages
are managed by two separate OMC-R functions.
When a short message broadcast is started, the presence of a CBCH
in the channelType of a channel object is dependent on a concerned
bts object.
However, the SMS-CB function are not aware of changes made to
that attribute.
Consequently, withdrawing a CBCH from the configuration will stop
any short message broadcast in the concerned cell without th SMS-
CB function knowing.
Nortel confidential

5.35. PROTECTION AGAINST INTRACELL HO PING-PONG

PARAMETERS
capacityTimeRejection Class 3 V14

Description: Rejection time of a capacity intracell handover after an intracell
handover
Value range: [0 to 120 s.]
Default value: 0 s.
Type: DP
Rec. value: [15 to 30 s.]
Used in: Protection against Intracell HO Ping-Pong
Handover mechanisms (AMR)
Eng. Rules:
Remark: Applies to a BSC 3000 architecture only.
LCAUTION! When AMR is activated that parameter should be set to 40 s
minTimeQualityIntraCellHO Class 3 V14

Description: Rejection time of a quality intracell handover after an intracell
handover
Value range: [0 to 120 s.]
Default value: 0 s.
Type: DP
Rec. value: [0 to 10 s.]
Used in: Protection against Intracell HO Ping-Pong
Eng. Rules:
Remark: Applies to a BSC 3000 architecture only.
Note: That parameter can be named qualityTimeRejection in the literature.
LCAUTION! When AMR is activated that parameter should be set to 5 s
Nortel confidential

5.36. AUTOMATIC HANDOVER ADAPTATION PARAMETERS
selfAdaptActivation Class 3 V12

Description: Use for activate the Automatic Handover adaptation
Object: bts
Type: DP
Rec. value: enabled
Used in: Automatic handover adaptation
Eng. Rules:
servingfactorOffset Class 3 V12

Description: This attribute defines the offset linked to the serving cell, used to
decrease the HO margin, in some specific cases
Value range: [-63 to 63]
Default value: -2
Type: DP
Rec. value: 0
Eng. Rules:
Nortel confidential

neighDisfavorOffset Class 3 V12

Description: This attribute modifies the offset linked to the neighbouring cell, used
to increase the HO marging, in some specific cases
Value range: [-63 to 63]
Default value: 2
Type: DP
Rec. value: 2
Eng. Rules:
Note: That parameter can be named offsetNeighbouringCell at the MMI.
rxQualAveBeg Class 3 V12

Description: This attribute defines the number of quality measurement results used
by the power control mechanism, in short averaging algorithm
Default value: 2
Type: DP
Rec. value: same as RxlevHreqAveBeg
Fast Power Control at TCH assignment (Pc_3)
Eng. Rules:
Nortel confidential

5.37. GSM TO UMTS HANDOVER PARAMETERS
cId Class 3 V17

Description: Cell identity of the UMTS neighbouring cell for handover
Value range: 0..65535
Object: adjacentCellUTRAN
Default value: 0
Type: DP
Rec. value: n/a
Used in: GSM to UMTS handover (v17)
Eng. Rules: N/A
compressedModeUTRAN Class 3 V17

Description: flag to indicate whether compressed mode UTRAN is supported or
not. This flag is used by the network to indicate to mobiles whether to
use a compressed version of the INTER RAT HANDOVER INFO
message (UE to UTRAN message).
Value range: enabled/disabled
Object: bts
Type: DP
Eng. Rules: The UTRAN_CLASSMARK_CHANGE message sent by UE to the
BSS takes about 2 or 3 radio frames. However, when supported by
the UTRAN network, it is possible to reduce the size of this message
thanks to the compression of UE radio access capabilities and
predefined configuration IE. This option is indicated in
IMMEDIATE_ASSIGNMENT message sent to the UE (IA rest octets
fields). For that purpose, the parameter compressedModeUTRAN
indicates whether compression of UE information elements is
supported.
diversityUTRAN Class 3 V17

Description: flag indicating whether there is diversity in the neighbouring UTRAN
cell
Value range: no diversity/diversity
Default value: no diversity
Type: DP
Rec. value: see Eng. rules
Nortel confidential


Eng. Rules: Please refer to diversity
earlyClassmarkSendingUTRAN Class 3 V17

Description: flag indicating whether UTRAN classmark change message shall be
sent with Early Classmark Sending
Value range: disabled/enabled
Object: bts
Type: DP
Rec. value: enabled
Eng. Rules: earlyClassmarkSendingUTRAN shall be set to “enabled” before
handover 2G to 3G feature is activated.
fDDARFCN Class 3 V17

Description: fDD channel number of the UTRAN neighbouring cell
Default value: N/A
Type: DP
Rec. value: N/A
Eng. Rules: N/A
gsmToUMTSServiceHo Class 3 V17

Description: This parameter serves to disable 2G-3G handover at BSC level or to
indicate the preference (2G versus 3G cells) to be applied for
handovers
Value range: “should”/”should not”/”shall not”/”gsm to UMTS HO disabled”
Object: bsc
Default value: “gsm to UMTS HO disabled”
Type: DP
Rec. value: “should”
Eng. Rules: See GSM to UMTS handover (v17) section. This parameter is useful
in only 2 cases :
Case n°1 : the “service handover” field in HANDOVER REQUEST and
ASSIGNMENT REQUEST is missing.
Nortel confidential

Case n°2 : the network operator wants to disable the 2G to 3G

handover on the BSC, regardless of the presence, and/or the value, of
the “service handover” field.
hoMarginUTRAN Class 3 V17

Description: Handover margin for PBGT handover to a UMTS cell
Value range: -63 dB to 63 dB, in 1dB steps
Type: DP
Rec. value: -6
Eng. Rules: If the operator wants to unload GSM traffic:
UMTS RSCP is lower than GSM Rxlev where a quite a high value is
required for a good quality. This margin controls the probability to
perform a handover.
Note that a the quality of UTRAN neighboring is ensured by the
fDDreportingThreshold and fDDreportingThreshold2 parameter
hoMarginAMRUTRAN Class 3 V17

Description: Handover margin for intercell quality handovers to UMTS, for AMR
calls
Type: DP
Eng. Rules: TBD
hoMarginRxLevUTRAN Class 3 V17

Description: handover margin for signal strength handover to UMTS
Type: DP
Eng. Rules: TBD
Nortel confidential

hoMarginRxQualUTRAN Class 3 V17

Description: handover margin to be used for signal quality handover to UMTS
Type: DP
Eng. Rules: TBD
hoMarginDistUTRAN Class 3 V17

Description: handover margin for handover to UMTS on distance criterion
Type: DP
Eng. Rules: TBD
hoMarginTrafficOffsetUTRAN Class 3 V17

Description: offset to be subtracted to the homarginUTRAN to allow handover for
traffic reason when the current cell is congested
Value range: 0 dB to 63 dB, in 1dB steps
Type: DP
Eng. Rules: TBD
Nortel confidential

hoPingpongCombinationUTRAN Class 3 V17

Description: list of pair of causes indicating the causes of ping-pong handovers in
the overlapping areas. Each pair is structured as follows : (incoming
HO cause, outgoing HO cause). Incoming HO cause indicates the
essential handover cause which leads to enter the neighbour cell.
outgoing HO cause indicates the non-essential handover cause which
leads to leave the neigbour cell.
Value range: list of pairs of causes (GSM to UMTS HO, UMTS to GSM HO): traffic,
powerbudget, directed retry, Rxlev, Rxqual, distance, O&M (forced
HO), all, allpowerbudget.
Default value: (rxqual, pbgt)
Type: DP
Rec. value: (all, pbgt)
Eng. Rules:
hoPingpongTimeRejectionUTRAN Class 3 V17

Description: time that must elapse before attempting another handover towards an
UTRAN cell. Refer to HOPingpongCombinationUTRAN attribute for
the combinations of HO causes for which this timer applies. To avoid
ping-pong handovers this new timer is started after a successful
handover. Up to the expiry of this timer, any HANDOVER
INDICATION message received from the BTS is ignored by the BSC.
Value range: list of pairs of causes (GSM to UMTS HO, UMTS to GSM HO): traffic,
powerbudget, directed retry, Rxlev, Rxqual, distance, O&M (forced
HO), all, allpowerbudget.
Default value: (Rxqual, pbgt)
Type: DP
Rec. value: (all, pbgt)
Eng. Rules:
hoRejectionTimeOverloadUTRAN Class 3 V17

Description: time that must elapse before attempting another handover towards a
congested UTRAN cell
Value range: 0..60 (60 means “immediately”)
Object: bsc
Type: DP
Eng. Rules:
Nortel confidential

locationAreaCodeUTRAN Class 3 V17

Description: Location area code of the UMTS neighbouring cell
Default value: N/A
Type: DP
Rec. value: N/A
Eng. Rules: N/A
mobileCountryCodeUTRAN Class 3 V17

Description: Mobile Country Code (MCC) of the UTRAN neighbouring cell
Value range: 000…999 (string)
Default value: N/A
Type: DP
Rec. value: N/A
Eng. Rules: N/A
mobileNetworkCodeUTRAN Class 3 V17

Description: Mobile Network Code (MNC) of the UTRAN neighbouring cell
Value range: 000…999 (string)
Default value: N/A
Type: DP
Rec. value: N/A
Eng. Rules: N/A
offsetPriorityUTRAN Class 3 V17

Description: priority offset applied by the BSC when selecting the candidate cell for
the handover process
Value range: 1..5
Default value: 1
Type: DP
Rec. value: 1
Eng. Rules:
Nortel confidential

rNCId Class 3 V17

Description: identity of the UTRAN neighbouring cell’s RNC
Default value: N/A
Type: DP
Rec. value: N/A
Eng. Rules: N/A
rxLevDLPbgtUTRAN Class 3 V17

Description: downlink signal strength threshold above which handovers to UTRAN
for cause power budget are inhibited
Value range: <-110 dBm, -110<x<-109, … to >-48 dBm
Default value: >-48
Type: DP
Rec. value: see Eng. Rule
Eng. Rules: This parameter has to be managed carefully because it can prevent
all the UTRAN handover for power budget when set to less than -110.
Moreover, the setting of this parameter has to be done with the help of
some radio measurement campaigns.
This parameter shall be disabled by setting the value to more
than –48 (dBm).
rxLevMinCellUTRAN Class 3 V17

Description: minimum signal strength level that the MS must measure on an UMTS
neighbour cell to be able to be granted a handover to this UMTS
neighbour cell
Value range: <-110 dBm, -110<x<-109, … to >-48 dBm
Default value: >-48
Type: DP
Rec. value: see Eng. Rule
Eng. Rules: The value of rxLevMinCellUTRAN must be greater than the value of
minimumCpichRscpValueForHO UTRAN parameter.
Nortel confidential

scramblingCode Class 3 V17

Description: scrambling code of the UTRAN neighbouring cell
Value range: 0..511
Default value: N/A
Type: DP
Rec. value: N/A
Eng. Rules: N/A
t3121 Class 3 V17

Description: t3121 has the same use as t3103 in the GSM inter-BSC handover
procedure. It sets the value before countdown of T3121 timer defined
in the GSM specification .
T3121 starts when the BSC sends an INTER SYSTEM TO UTRAN
HANDOVER message to the mobile. T3121 stops when the mobile
has correctly seized the UTRAN channel. The purpose of this timer is
for the BSC to keep the old channels long enough for the mobile to be
able to return to the old channels if necessary. On expiry of T3121
(indicating the mobile is lost), the BSC may release the channels.
Value range: 2..255 seconds
Object: bts
Type: DP
Eng. Rules: T3121 purpose is very similar to T3103 one. However,
INTERSYSTEM TO UTRAN HANDOVER COMMAND message from
BSS to Mobile is much larger than the HANDOVER COMMAND
message so it takes about one second more to send the inter system
message to the MS. An additional safety margin should therefore be
considered for LAPDm repetitions.
Nortel confidential

5.38. AMR - ADAPTATIVE MULTI RATE FR/HR PARAMETERS
BTS OBJECT
amrUlFrAdaptationSet Class 3 V15

Description: Define the lines of parameter used for the adaptation mechanism.
It sets the C/I thresholds when AMR speech codecs are used on a FR
channel in UL.when AMR speech codecs are used.
Value range: [0 to3]
Object: bts
Default value: 0
Type: DP
Rec. value: 3
Used in: Codec mode adaptation
Eng. Rules:
0: typical radio condition
1: optimistic radio condition
2: pessimistic radio condition
3: personalize with the BSC data configuration table
The recommanded value of 0 offers a good compromise between HR
penetration and radio environment.
For optimization of the table amrUlFrAdaptationSet should be turn to 3
(refer to AMR Activation Guideline PE/BSS/APP/11438 in Reference
Documents)
See also chapter AMR Engineering Studies.
amrUlHrAdaptationSet Class 3 V15

Object: bts
Default value: 0
Type: DP
Rec. value: 3
Eng. Rules:
For optimization of the table amrUlHrAdaptationSetshould be turn to 3
Documents)
Nortel confidential

amrDlFrAdaptationSet Class 3 V15

Object: bts
Default value: 0
Type: DP
Rec. value: 3
Eng. Rules:
For optimization of the table amrDlFrAdaptationSetshould be turn to 3
Documents)
amrDlHrAdaptationSet Class 3 V15

Object: bts
Default value: 0
Type: DP
Rec. value: 3
Eng. Rules:
For optimization of the table amrDlHrAdaptationSetshould be turn to 3
Documents)
Nortel confidential

filteredTrafficCoefficient Class 3 V15

Description: Filter coefficient taken into account in the cell load evaluation.
Value range: [0..1] step 0.001
Object: bts
Default value: 0
Type: DP
Rec. value: 0.5
Used in: AMR based on traffic
Eng. Rules: The parameter shoud be set to 1 to reach V15.1 behaviour (HR calls
allocated on RxLev criterion only)
hrCellLoadEnd Class 3 V14
Description: This attribute is used to trigger the end of AMR HR allocation in the
cell.
Object: bts
Default value: 0
Type: DP
Rec. value: 60
Used in: Channel allocation

Eng. Rules: The parameter should be set to 0 to reach V15.1 behaviour (HR calls
allocated on RxLev criterion only).
This value should be tuned according to the operator strategy and the
number of TCH (preemptable PDTCH are not taken into account).
60 is a good compromise but it can be increased for cells with more
than 12 TCH.
hrCellLoadStart Class 3 V14

Description: This attribute is used to trigger the beginning of AMR HR allocation in
the cell.
Object: bts
Default value: 100
Type: DP
Rec. value: 0 for AMR FR only, different from 0 to trigger the HR allocation in
the cell.
80 for AMR based on Traffic
Eng. Rules: This parameter shall be different from “0” to use Half Rate allocation.
The parameter should be set to 1 to reach V15.1 behaviour (HR
calls allocated on RxLev criterion only)
This value should be tuned according to the operator strategy and the
number of TCH (preemptable PDTCH are not taken into account).
80 is a good compromise but it can be increased for cells with more
than 12 TCH.
Nortel confidential

radioAllocator Class 2 V12

Description: Radio allocator type used in the cell
Value range: [voice + dataCircuit, voice + dataCircuit + packetData]
Object: bts
Default value: voice + dataCircuit
Type: DP
Rec. value: voice + dataCircuit + packetData
Used in:
Eng. Rules: Lab tests have shown that the recommended value has to be set to
voice + dataCircuit + packetData when AMR is activated
TRANSCODER OBJECT
coderPoolConfiguration Class 2 V12

Description: This attribute indicates enumerated speech coding algorithms
supported by the TCU.
List of algoid [minimumCalls, powerUplink, powerDownlink]
Value range: Algoid: fullRateCoder, enhancedFullRateCoder,
amrFullHalfRateCoder, ctmEnhancedFullRateCoder
MinimumCall: 0 to 65535
PowerUL: -15 to +15
PowerDL: -15 to +15
Object: Transcoder
Default value: fullRateCoder, minimumCall = 1, pwrUL = 0, pwrDL = 0
enhancedFullRateCoder, minimumCalls = 1, pwrUL = 0, pwrDL = 0
amrFullHalfRateCoder, minimumCalls = 1, pwrUL = 0, pwrDL = 0
ctmEnhancedFullRateCoder, minimumCalls = 1, pwrUL = 0, pwrDL =
0
Type: DP
Used in: Channel allocation (AMR)
Cellular Telephone Text Modem (TTY)
Eng. Rules: Used for the AMR, TTY activation at the TCU level (downlink and
uplink amplification level and use to define the minimum of AMR
communications on the TCU level).
Each coded has to be present only if is is activated by the operator,
FR is mandatory.
During normal operation, it dynamically reallocates the resources
between the TRMs to meet traffic demand. For the EFR and FR
codecs, the archipelago capacity is 72, i.e. 216 circuits per TRM. For
the AMR codec, the archipelago capacity is 60, i.e.180 circuits per
TRM. For the EFR+TTY codec, the archipelago capacity is 48, i.e. 144
circuits per TRM.
The customer can set for each enabled vocoder type (FR, EFR, AMR)
a warrantied minimum number of communications. This field is called
minimumCalls and is used for the initial distribution.
Nortel confidential

The TCU assigns CODEC to each available archipelago in an round-

robin manner until the TCU satisfies the minimumCalls condition for
each enabled CODEC. Remaining archipelagoes are configured in
order to achieve as close as possible the CODEC ratios given by
minimumCalls parameters.
Let nbMinimumCalls = sum of minimumCalls of each enable CODEC.
The ratio to achieve for a given CODEC is computed as follows:
CODEC_rate = (minimumCalls (for this CODEC) / nbMinimumCalls).
Examples:
For E1 network with 20% FR, 40% EFR and 40% AMR setting could
be:
FullRateCoder, minimumCalls = 4, powerUL = 0, powerDL = 0
EnhancedFullRateCoder, minimumCalls = 8, powerUL = 0,
powerDL = 0
amrFullHalfRateCoder, minimumCalls = 8, powerUL = 0,
powerDL = 0
Remark: Whatever is the repartition between the codecs, the two parameters
powerUL and powerDL should always be set to “0“.
For T1 network, no TTY CODEC is available at the MMI. So when

theTCU receives TRM related config messages indicating for each
CODEC(FR, EFR and AMR) their minimumCalls, the equivalent
EFR+TTYCODEC is enabled with a minimumCalls set to 1 by default.
LCAUTION! All TCUe3 releases below V16.0, if the transmission network uses the
T1 PCM, TTY is activated by default. For any TCUe3 upgrade from
V14/V15 to release V16.0, TTY must be explicitly set at MMI on
G3Trans object via the coderPoolConfiguration field.
Nortel confidential

TRANSCEIVER OBJECT
frAMRPriority Class 2 V14

Description: defines TDMA allocation priority for AMR FR calls.
Object: Transceiver
Default value: 0
Type: DP
Rec. value: 1 for BCCH TDMA
0 for hopping TDMA
Used in: Channel allocation (AMR)
Eng. Rules: BCCH and non-hopping TDMA should be set to low priority, i.e. 1,
while hopping TDMA should be set to high priority, i.e. 0.
Priority 0 is given to a high priority TDMA,
Priority 1 is given to a low priority TDMA,
Priority 2 disables this service on the TDMA.
See also chapter Isolated Areas in AMR Monitoring.
LCAUTION! Priority 2 is not recommended as it could introduce an AMR
congestion on the cell due to a barring of access to some TDMAs for
AMR calls. However, that setting could be interesting in some specific
cases.
hrAMRPriority Class 2 V14

Description: defines TDMA allocation priority for AMR HR calls.
Object: Transceiver
Default value: 0
Type: DP
Rec. value: 1 for BCCH TDMA
0 for hopping TDMA
Eng. Rules: BCCH and non-hopping TDMA should be set to low priority, i.e. 1,
while hopping TDMA should be set to high priority, i.e. 0
Priority 0 is given to a high priority TDMA,
Priority 1 is given to a low priority TDMA,
Priority 2 disables this service on the TDMA.
See also chapter Isolated Areas in AMR Monitoring.
LCAUTION! Priority 2 is not recommended as it could introduce an AMR
congestion on the cell due to a barring of access to some TDMAs for
AMR calls. However, that setting could be interesting in some specific
cases.
Nortel confidential

POWER CONTROL OBJECT
Since the introduction of the ML0, there is a treshold preventing from doing Power Control
below a defined level when using AMR power control (refer to the amrReserved2 parameter).
The two parameters lRxLevDLP and lRxlevULP setting that threshold are defined in chapter
Power Control Parameters.
hrPowerControlTargetMode Class 3 V14

Description: AMR codec target to define the Uplink power control threshold for HR
AMR calls
Value range: [4k75, 5k9, 6k7, 7k4]
Object: power control
Default value: 7k4
Type: DP
Rec. value: 7k4
Used in: Power Control (AMR)
Eng. Rules: Power has to be decreased when call quality is very good and
increased when the quality could be better.
Even if 7k4 AMR HR is set, which corresponds to the most
constraining Power control value, AMR Power control has shown to
be more aggressive than EFR Legacy L1m. If cell radio conditions are
very good, optimization to 6k7 HR target could be justified.
Power control has to be triggered before handover for quality reason.
AMRHRIntercellCodecModeThreshold<hrPowerControlTargetMode
frPowerControlTargetMode Class 3 V14

Description: AMR codec target to define the Uplink power control threshold for FR
AMR calls
Value range: [4k75, 5k9, 6k7, 10k2, 12k2]
Default value: 12k2
Type: DP
Rec. value: 12k2
very good, optimization to 10k2 FR target could be justified.
AMRFRIntercellCodecModeThreshold<frPowerControlTargetMode
Nortel confidential

hrPowerControlTargetModeDl Class 3 V16

Description: AMR codec target to define the downlink power control threshold for
HR AMR calls
Default value: 7k4
Type: DP
Rec. value: 7k4
very good, optimization to 6k7 HR target could be justified.
AMRHRIntercellCodecModeThreshold<hrPowerControlTargetModeDl
frPowerControlTargetModeDl Class 3 V16

Description: AMR codec target to define the downlink power control threshold for
FR AMR calls
Default value: 12k2
Type: DP
Rec. value: 12k2
very good, optimization to 10k2 FR target could be justified.
AMRFRIntercellCodecModeThreshold<frPowerControlTargetModeDl
Nortel confidential

HANDOVER OBJECT
amrDirectAllocRxLevUL Class 3 V14

Description: Uplink RxLev threshold for direct AMR TCH allocation in a normal cell
or in the large zone of a bizone cell (in conjunction with
amrDirectAllocRxlevDL).
Default value: - 80 dBm
Used in: Handover mechanisms (AMR)
Eng. Rules: Direct HR allocation enables to avoid some unnecessary handovers
from FR to HR channels. To define the value of those parameters it is
necessary to study the distribution of RxLev for the codec mode
defined as the target for the HR to FR intra cell HO to avoid a
immediate come back on a FR channel after a direct HR allocation.
The uplink parameter may be set considering a threshold
corresponding to 90% of C/I values higher than 16 dB (proposed
value, depends on the network quality). Furthermore, it has to be
checked that the RxLev value is more restrictive than the threshold to
go back to the large zone to avoid an immediate comeback on the
large zone.
See also chapter Half Rate Penetration Analysis.
amrDirectAllocRxLevDL Class 3 V14

Description: Downlink RxLev threshold for direct AMR TCH allocation in a normal
cell or in the large zone of a bizone cell (in conjunction with
amrDirectAllocRxlevUL).
Eng. Rules: Direct HR allocation enables to avoid some unnecessary handovers

from FR to HR channels. To define the value of those parameters it is
necessary to study the distribution of RxLev for the codec mode
defined as the target for the HR to FR intra cell HO to avoid a
immediate come back on a FR channel after a direct HR allocation.
The uplink parameter may be set considering a threshold
corresponding to 90% of C/I values higher than 16 dB (proposed
value, depends on the network quality). Furthermore, it has to be
checked that the RxLev value is more restrictive than the threshold to
go back to the large zone to avoid an immediate comeback on the
large zone.
Nortel confidential

See also chapter Half Rate Penetration Analysis.
amrDirectAllocIntRxLevUL Class 3 V14

Description: UplinkRxLev threshold for directAMR TCH allocation in the inner zone
of a bizone cell (in conjunction with amrDirectAllocIntRxlevDL).
Eng. Rules: see Engineering Rules of amrDirectAllocRxLevUL.
amrDirectAllocIntRxLevDL Class 3 V14

Description: Downlink RxLev threshold for directAMR TCH allocation in the inner
zone of a bizone cell (in conjunction with amrDirectAllocIntRxlevUL).
Eng. Rules: see Engineering Rules of amrDirectAllocRxLevUL.
Furthermore, it has to be checked that the RxLev value is more
restrictive than the threshold to go back to the large zone to avoid an
immediate comeback on the large zone.
amrDirecAllocIntRxLevDL ≥ concentAlgoIntRxLev
amrFRIntercellCodecMThresh Class 3 V14

Description: Target codec mode to trigger an intercell AMR quality handover.
Default value: 6k7
Rec. value: 10k2
Eng. Rules: The target codec mode has to be more restrictive than the one for
intracell handover otherwise intracell handover will not be possible
most of the time.
amrFRIntercellCodecMThresh<amrFRIntracellCodecMThresh.
On the other hand, the codec mode threshold for intercell handover
has to be smaller than the target codec for power control.
amrFRIntercellCodecMThresh<frPowerControlTargetMode
Nortel confidential

This parameter is directly linked to AMR adaptation set and the C/I
threshold. Intercell codec target, which directly applies on a C/I target,
has to be aligned to C/I relation with RxQual. CPT could be used.
C/I associated to HO intercell codec target should be between 7dB
and 14 dB depending on radio environment
amrFRIntracellCodecMThresh Class 3 V14

Description: Target codec mode to trigger an intracell quality handover FR to FR
Default value: 4k75
Rec. value: 4k75 (AMR intracell deactivation value)
Eng. Rules: The target codec mode has to be less restrictive than the one for
intercell handover otherwise intracell handover will not be possible
most of the time.
amrFRIntercellCodecMThresh<amrFRIntracellCodecMThresh
amrHRIntercellCodecMThresh Class 3 V14

Description: Target codec mode to trigger an intercell quality handover from a HR
channel.
Default value: 5k9
Rec. value: 5k9
Eng. Rules: The target codec mode has to be more restrictive than the one for
intracell handover otherwise intracell handover will not be possible
most of the time.
amrHRIntercellCodecMThresh<amrHRtoFRIntracellCodecMThresh.
On the other hand, the codec mode threshold for intercell handover
has to be smaller than the target codecs for power control.
amrHRIntercellCodecMThresh<hrPowerControlTargetMode.
amrHRtoFRIntracellCodecMThresh Class 3 V14

Description: Target codec mode to trigger an AMR intracell quality handover from
AMR HR to FR
Default value: 6k7
Rec. value: 6k7
Nortel confidential

Eng. Rules: The target codec mode has to be less restrictive than the one for
intercell handover otherwise intracell handover will not be possible
most of the time. In case same intercell and intracell codec target is
chosen, intercell has the priority.
amrHRIntercellCodecMThresh<AMRHRtoFRIntracellCodecMThresh
If the operator’s strategy is to increase capacity versus quality, low
values for AMRHRtoFRIntracellCodecModeThreshold can be chosen
to delay a come back on a FR channel.
Change of AMR adaptation set could also be used for HR penetration
increase (see chapter Half Rate Maximization Analysis)
amriRxLevDLH Class 3 V14

Description: Minimum downlink level to receive to trigger an intracell handover FR
to FR
Value range: [less than -110, -110 to -109, ..., -49 to -48, more than -48] dBm
Eng. Rules: Since AMR coding is better than standard coding, the threshold for
intracell AMR handover must be more restrictive than the one for
standard calls: amriRxLevDLH>rxLevDLIH.
amriRxLevULH Class 3 V14

Description: Minimum uplink level to receive to trigger an intracell handover FR to
FR
Eng. Rules: Since AMR coding is better than standard coding, the threshold for
intracell AMR handover must be more restrictive than the one for
standard calls: amriRxLevULH>rxLevULIH.
Nortel confidential

amrReserved1 Class 3 V16

Description: Allows the activation of RATSCCH procedure for AMR FR calls
0: RATSCCH procedure enabled (default value)
1: RATSCCH procedure disabled - initial Full Rate ACS if optimistic
therefore; ACS is [12.2k, 10.2k, 6.7k, and 5.9k]
2: RATSCCH procedure disabled - initial Full Rate ACS if pessimistic
therefore; ACS is [10.2k, 6.7k, 5.9k and 4.75]
Default value: 0
Type: DP
Rec. value: 0
Used in: AMR Legacy L1M
Eng. Rules: Before v15.1.1, in case of poor uplink radio conditions, the BTS is
sometimes unable to detect RATSCCH acknowledgements from
mobiles. This triggers a mismatch between the AMR Codec Set used
by the mobile and the one used by the BTS. Then the BTS (or MS)
cannot correctly decode the codec used by the MS (or BTS). This
sequence leads to a mute call until the next RATSCCH procedure is
correctly executed.
A workaround for this problem of mute call consists in setting
amrReserved1 to value “1” which means “RATSCCH disabled and
initial ACS optimistic” : only codec 5k9, 6k7, 10k2 and 12k2 will be
used. The only drawback of the workaround is that this parameter
setting prevents the usage of 4,75 AMR FR codec, useful in case of
very degraded radio conditions.
In v16, an improvement of the L1M has been implemented which
consists in the BTS repeating the RATSCCH command until it
receives an acknowledgment from the mobile.
In v17, a further improvement has been implemented. It consists in
improving the robustness of the detection of the acknowledgement
message received from the mobile : this increases the probability of
correctly decoding this message when it is first received.
Thanks to these 2 improvements, amrReserved1 should be set to "0"
in V16 and V17.
Warning: pessimistic Codec Set 10,2 / 6,7 / 5,9 /4,75 (amRreserved1
= 2) must not be chosen because it would inhibit capacity HO i.e.
handover from AMR FR to AMR HR (as 12.2 cannot be used).
amrReserved2 Class 3 V12

Description: Legacy L1m procedures (Power control and Handover) or AMR L1m
mechanisms (based on (n,p) voting algorithm and codec target) can
be chosen
Nortel confidential

Default value: 0
Type: DP
Used in: AMR Legacy L1M
Eng. Rules:
AMR alarm handovers AMR PowerControl
amrReserved2
based on algorithm based on
0 CMR/CMC [(n,p) voting] CMR/CMC
1 RxQual CMR/CMC
2 CMR/CMC [(n,p) voting] RxQual
3 RxQual RxQual
LCAUTION! A mix between AMR L1m for Power Control and Legacy L1m for AMR
alarm HO is recommended at this stage (amrReserved2 = 1); however
AMR activation with full AMR algorithms on HO management and
Power Control has shown good performances.
nCapacityFRRequestedCodec Class 3 V14

Description: Number of 12k2 codec mode requested to trigger a capacity handover
(FR to HR)
Default value: 44
Rec. value: set to 100% of pRequestedCodec, i.e. 48
Eng. Rules: The recommended value was chosen in order to increase capacity in
real good conditions: 100% of the requested codecs should be 12k2
meaning the radio conditions are really good. If the operator’s strategy
is to increase capacity vs. quality, low value for
nCapacityFRRequestedCodec can be chosen.
Higher nCapacityFRRequestedCodec assures a better HR radio
conditions and reduce probability intraHO ping pong.
See also chapter Half Rate Settings.
nFRRequestedCodec Class 3 V14

Description: Minimum number of codecModeRequest out of pRequestedCodec in
the (n,p) voting mechanism to trigger an AMR HO while in FR mode.
Default value: 24
Eng. Rules:
Nortel confidential

nHRRequestedCodec Class 3 V14

Description: Minimum number of codecModeRequest out of pRequestedCodec in
the (n,p) voting mechanism to trigger an AMR HO while in HR mode.
Default value: 34
Eng. Rules:
pRequestedCodec Class 3 V14

Description: Number of codec mode requests to consider in the (n,p) voting
decisions.
Value range: [12 to 192] (step of 12)
Default value: 48
Rec. value: 48
Eng. Rules: A similar reactivity between AMR and non-AMR calls should be
reached. The recommended value corresponds to the same quality
averaging window as for standard calls in urban environment. Field
experimentation should give further information as for the value of
pRequestedCodec.
Nortel confidential

ADJACENTCELLHANDOVER
hoMarginAMR Class 3 V14

Description: HO margin taken into account in an intercell quality handover for AMR
calls in order to manage the eligible cell list.
Object: AdjacentCellHandover
Default value: -2
Rec. value: same as hoMarginRxQual
Handovers screening
Eng. Rules: In case of AMR L1mis activated (cf. amrReserved2) Handover cause
AMR quality: case where access to another cell should be
encouraged, provided target cell field strength is not much lower than
the current one. If bad quality remains, there is a risk of return
handover but there is nothing much to be done.
Depending on radio environment:
Interfered environment:
It is better to have a low C/I threshold for Quality HO (chosen via AMR
adaptation set or intercell HO codec target) and have homarginAMR =
hoMarginRxQual
Coverage limited environment:
It is better to have a high C/I threshold for Quality HO (chosen via
AMR adaptation set or intercell HO codec target) and have hoMargin
= hoMarginRxQual + 2
Nortel confidential

REPEATED DOWNLINK FACCH
enableRepeatedFacchF Class 2 V16

Description: Enable/ disable the Repeated FACCH feature on AMR FR calls
Value range: Disable / FR 4.75 / FR 5.9 and lower / FR 6.7 and lower
Object: bts
Default value: Disable
Rec. value: FR 6.7 and lower
Eng. Rules:
TX POWER OFFSET FOR SIGNALLING CHANNELS
facchPowerOffset Class 2 V16

Description: Power offset to be applied on FACCH signalling
Value range: [0 to 10] dB (with 2 dB step)
Object: bts
Default value: 0
Rec. value: 6
Used in: This parameter is used to tune the power offset to be applied on
FACCH re-transmission, specific FACCH messages (for first
transmission) as well as RR and REJect frames on FACCH
corresponding to an uplink re-transmission (F bit set to 1) and UA
frames corresponding to an uplink re-transmission of SABM or DISC
frames (F bit set to 1).
Eng. Rules:
sacchPowerOffset Class 2 V16

Description: Power offset to be applied on SACCH signalling
Value range: [0 to 6] dB (with 2 dB step)
Object: bts
Default value: 2
Rec. value: 6
Used in: This parameter is used to tune the power offset to be applied on
selected SACCH frames transmission
Eng. Rules:
Nortel confidential

sacchPowerOffsetSelection Class 2 V16

Description: CODEC selection for applying a power offset on SACCH
Value range: NULL / FR 4.75 kbps / FR 5.9 and lower / FR 6.7 and lower
Object: bts
Default value: NULL
Rec. value: FR 6.7 and lower
Used in:
Eng. Rules:
AMR-HR CHANNEL ON PREEMPTED PDTCH
gprsPreemptionForHR Class 3 V17

Description: Activation of PDTCH pre-emption for HR channel
Object: bsc
Rec. value: enabled
Used in: pDTCH Preemption by AMR FR or HR calls (V17)
Eng. Rules: “AMR based on traffic” thresholds may need to be retuned if the
PDTCH preemption for HR channels is enabled.
Nortel confidential

5.39. WPS - WIRELESS PRIORITY SERVICES PARAMETERS
wPSManagement Class 3 V15

Description: WPS feature is enabled or disabled
Value range: [disabled ; enabled ]
Object: bsc
Type: DP, System
Rec. value: enabled for WPS use
Used in: WPS - Wireless Priority Service
Eng. Rules: In order to enabled the new queuing management of WPS requests
the wPSManagement flag has to be set to the value “enabled”
LCAUTION! Queuing management of WPS requests can only be activated if the
bscQueuingOption parameter is set to “allowed” (MSC driven) and the
WPS priorities have been set properly
wPSQueueStepRotation Class 3 V15

Description: One out of the wPSQueueStepRotation value to first have an
evaluation of the WPS queues in the radio resource allocator.
Object: bts
Default value: 4
Type: DP, System
Rec. value: 4
Used in: WPS - Wireless Priority Service
Eng. Rules: If the operator choose to activate WPS queuing management on its
network this parameter can ensure a minimum amount of non-WPS
calls (with low priorities) that can access the network even if it is very
congested
With that parameter fixed to “4”, when a radio resource become free
and there are WPS or public call requests queued, the priority is given
1 out of 4 times to a WPS call request and 3 out of 4 times to a public
call. In that case WPS calls are favored in 25% of the time.
LCAUTION! The operator can choose to enable queuing uniquely on WPS calls,
hence public calls are never queued and this parameter becomes
obsolete.
The Algorithm for the traffic channel allocation applies at a cell level in
the BSC, and hence wPSQueueStepRotation is a cell parameter.
Nortel confidential

5.40. NETWORK SYNCHRONIZATION PARAMETERS
btsSMSynchroMode Class 2 V15

Description: Type of site synchronization.
Activation of the Synchronisation feature (either site synchro either
network synchro features). Its value defines also the synchronization
mode (burst or time)
Value range: [normal, master, slave, gprBurstSync, gpsTimeSync,
masterGpsBurstSync, masterGpsTimeSync]
Default value: normal
Rec. value: normal
Used in: Network Synchronization
Eng. Rules:
tnOffset Class 2 V15
Description: Its value allows to specify and control TN difference between BTS in
case of network synchronisation by GPS
Value range: [0..7]
Default value: 0
Rec. value: 0
Eng. Rules:
fnOffset Class 2 V15

Description: Its value allows to specify and control FN difference between BTS in
case of network synchronisation by GPS
Value range: [0..84863]
Default value: 0
Rec. value: N/A
Eng. Rules:
dARPPh1Priority Class 2 V15
Description: Its value allows specifying the priority of SAIC mobiles on the TDMA.
Value range: [high priority, low priority]
Object: transceiver
Default value: high priority
Nortel confidential


Rec. value: high priority
Eng. Rules: Actually, for radio resource allocation only SDCCH requests are not
differentiated depending if the mobile requesting is SAIC capable or
not.
masterBtsSmId Class 2 V15

Description: Gives the identity of the master BTS if the BTSSMSynchroMode is
slave and remains empty if the BTS is master or normal
Value range: Master BTS id or empty
Default value: Empty
Rec. value: Depends on context
Eng. Rules:
baseColourCode Class 2 V7
Description: Base station Color Code assigned to a serving cell. It is broadcast on
the cell SCH and is used to distinguish cells that share the same
BCCH frequency.
The (BCC, NCC) pair forms the cell BSIC.
The information is broadcast on the cell SCH.
Several BCCs may be assigned to a same BTS. Hence, different
codes can be allotted to cells that may have overlapping areas
(adjacent cells).
The Base Station Identity Code (BSIC) is a 6–bit code: bits 6-5-4 =
NCC (PLMN color code), bits 3-2-1 = BCC (Base station color code).
At cell level, the NCC bits can be used to increase BCC color
possibilities when the NCC is not needed.
The BCC value is determining the TSC (training sequence code) of

the cell.
Object: bts
Default value: N/A
Rec. value: N/A
Eng. Rules: Several BCCs may be assigned to cells of a same site. Hence,
different codes can be allotted to cells that may have overlapping
areas (adjacent cells). See also chapter Set Up Principles of a
Neighboring List and a BCC Plan
Nortel confidential

5.41. NETWORK MODE OF OPERATION PARAMETERS
gprsNetworkModeOperation Class 3 V15

Description: Flag to choose the network mode of operation.
Value Range: [0 - 2] ; 0 = NMO II , 1 = NMO I , 2 = NMO 3 (value forbidden) .
Object: bts.
Default value: 0.
Rec. value: 1.
Used in: Network Mode of Operation I support in BSS
Eng. rules: NMO 1 must be activated or deactivated at RA level: the setting must
be consistent in all cells of a RA.
NMO1 activation is recommended when GPRS is activated on all cells
of the network: NMO1 should not be activated on a LA where some
cells do not affer GPRS service.
As combined procedures are performed on PDTCH with NMO1
(combined attach/detach and combined LA/RA update), it is strongly
recommended to guaranty the continuity of GPRS service by setting
minNbrGprsTs > 0.
The feature must be activated first at Core Network level and then at
BSS level.
The bscDataConfig must be modified to take the value of
gprsNetworkModeOperation into account. (see [R36] for details)
5.42. BSS CS PAGING COORDINATION PARAMETER
bssPagingCoordination Class 3 V17

Description: Activation parameter of BSS CS Paging Coordination feature
Value range: 0: disable BSS CS paging coordination/ 1: enable BSS CS paging
coordination
Object: bts
Default value: disable BSS CS paging coordination
Used in: BSS CS Paging Coordination
Eng. Rules: On (legacy) PCUSP board, the processing load is expected to
consume a significant proportion of the available processing
capability. In that case, the impact of the feature activation should be
monitored. See section Performance of BSS CS Paging coordination
Nortel confidential

5.43. NOVEL ADAPTIVE RECEIVER PARAMETER
adaptiveReceiver Class 2 V17

Description: Activation parameter of the novel adaptive receiver
Object: transceiver
Rec. value: enabled
Used in: Novel Adaptive Receiver
Eng. Rules: 1/ For cells operating under very specific radio conditions, namely
hard Hilly Terrain profiles, the Novel Adaptive Receiver structure may
possibly cause a slight performance loss compared with the initial
processing. Therefore, it is recommended to disable the adaptive
receiver for these cells.
2/ If Rx diversity is used, best receiver performance is achieved by
activating both the Joint diversity and the Novel Adaptive Receiver
features
3/ Novel Adaptive Receiver does not interwork with the Extended Cell
feature. Therefore, for extended cells, the Novel Adaptive Receiver
must be deactivated.
Nortel confidential

5.44. A5/3 ENCRYPTION ALGORITHM PARAMETERS
cypherModeReject Class 1 V8
Description: Whether the CIPHER MODE REJECT messages are used (Phase II
compliance).
Value range: true/false
Type: DP
Rec. value: true
Used in: A5/3 Encryption algorithm (V17)
Eng. Rules: This parameter must be set to true for the ciphering procedures to
operate correctly between the BSS and the NSS
encrypAlgoAssComp Class 1 V8
Description: Whether the "Chosen encryption algorithm" element is used in the
ASSIGN COMPLETE messages (Phase II compliance).
Type: DP
Rec. value: true
encrypAlgoCiphModComp Class 1 V8
CIPHER MODE COMPLETE messages (Phase II compliance).
Type: DP
Rec. value: true
Nortel confidential

encrypAlgoHoPerf Class 1 V8
HANDOVER PERFORMED messages (Phase II compliance).
Type: DP
Rec. value: true
encrypAlgoHoReq Class 1 V8
HANDOVER REQUEST ACKNOWLEDGE messages (Phase II
compliance).
Type: DP
Rec. value: true
encryptionAlgorSupported Class 3 V8
Description: Type of ciphering capability supported by the BTSs of a BSS. When
no ciphering capability is supported, users’ calls are not encrypted by
the BSS over the air interface.
Value range: [none, gsmEncryptionV1, gsmEncryptionV3FallbackNoEncryption,
gsmEncryptionV3FallbackV1]
Object: bsc
Default value: none
Type: DP
Eng. Rules: The setting of this parameter depends on the level of data integrity
and security required by the network operator. A5/3 is more powerful
than A5/1 but may slightly impact Call setup time and handover
duration.
Nortel confidential

Notes: 1/This parameter’s class has been modified from class 0 to class 3 in
v17.0.
2/This parameter’s range has been modified from [none /
gsmEncryptionV1 / gsmEncryptionV2] to [none, gsmEncryptionV1,
gsmEncryptionV3FallbackNoEncryption,
gsmEncryptionV3FallbackV1] in v17.0.
3/A5/2 must no longer be used in any network, as of December 2006.
layer3MsgCyphModeComp Class 1 V8
Description: Whether the "Layer 3 message" element is used in the CIPHER
MODE COMPLETE messages (Phase II compliance).
Type: DP
Rec. value: true
Nortel confidential

5.45. BTS SMART POWER MANAGEMENT PARAMETERS
smartPowerManagementConfig Class 3 V17

Description: Enable/disable the smart power management feature.
Type: DP
Rec. value: enabled
see Eng. Rules
Used in: BTS Smart Power Management (V17)
Eng. Rules: 1/ It is recommended to put combined BCCH and SDCCH/8 TS on the
same TDMA as BCCH.
2/ As a TRX supporting a PDTCH never switches its PA off, it is
recommended not to configure more PDTCH TS than necessary.
smartPowerSwitchOffTimer Class 3 V17

Description: Sets the initial countdown value of the timer that must expire before
the PA may be switched OFF.
Value range: 5 to 255 minutes in 1-minute steps
Default value: 5 minutes
Type: DP
Rec. value: 5 minutes
see Eng. Rules
Used in: BTS Smart Power Management (V17)
Eng. Rules: The smaller the switch-off timer :
• the more reactive the power management will be to the
minute-by-minute changes to the call profile as the day
progresses towards quieter moments
• the more power is likely to be saved as a result.
• but the more frequently the PA is likely to go through off/on
cycles, especially at the transition from busy hour to quieter
hours, thus possibly impacting its lifespan.
Nortel confidential

6. ENGINEERING ISSUES
6.1. GSM/GPRS TS SHARING: PRIORITY HANDLING AND

QUEUING
With GSM/GPRS TS sharing, the operator’s strategy can be of three main different kinds:
• Minimize the impact of GPRS introduction on GSM.

• Guarantee GPRS quality of service thus impacting on GSM if no resources are
added
• Find a trade-off impacting GSM as little as possible and guaranteeing GPRS as
much as possible.
The tuning of priority handling, queuing and also the use of the preemption mechanism
depends on the adopted strategy.
6.1.1 RESOURCES RESERVED FOR PRIORITY 0 AND

PREEMPTION
allocPriorityThreshold is a parameter used to reserve resources for priority 0 TCH allocation
requests. This reservation of resources decreases the capacity for incoming calls when
resources are reserved for handovers. Depending on the difference between
allocPriorityThreshold and the number of shared PDTCH, several phenomenon can happen.
IF allocPriorityThreshold ≥ shared PDTCH
THEN GPRS preemption mechanism is reserved for priority 0 TCH allocation requests
This behaviour is normal and comes from the definition of allocPriorityThreshold and the
allocation strategy that allocates in priority free TCH.
On the contrary:
IF allocPriorityThreshold ≤ Number of shared PDTCH

THEN the only free resources left for priority 0 TCH allocation request are shared
PDTCH.
• Reestablishment will not be enabled at those periods of time (no reestablishment

on shared PDTCH is allowed).
• A more frequent issue will come from GprsPreemption set to yes enabling the PCU
to NACK a preemption requested by the BSC. This phenomenon decreases the
efficiency of allocPriorityThreshold: reserved resources considered free by the
BSC might not be used to serve a TCH allocation request when the PCU NACKs
the preemption. This phenomenon will only happen in case of heavy GPRS traffic
at the same time as heavy GSM traffic.
Nortel confidential

The table below proposes a setting of GSM/GPRS TS dynamic sharing with priority handling
with or without reestablishment (MinNbOfGprsTs is only indicative). With reestablishment, two
sets of values are sometimes proposed, one of them for less GPRS capacity.
Number of shared
Number of TRX allocPriorityThreshold minNbOfGprsTs
PDTCH
1 TRX with or without reestablishment 1 1 0
2 TRX with or without reestablishment 2 1 1
3 TRX without reestablishment 2 2 2
2 2 1
3 TRX with reestablishment
3 2 2
4 TRX without reestablishemnt 2 2 2
2 2 1
4TRX with reestablishment
3 2 2
6.1.2 GSM/GPRS TS SHARING AND QUEUING:

No queued allocation request can use the preemption mechanism to leave the queue. The
allocation request must wait until a TCH is free. Hence, a too high number of shared PDTCH
(without adding a TDMA) increases the time a queued request will stay in the queue.
A solution to decrease the length of the queue is to forbid intracell queuing (intraCellQueuing
set to disabled). The intracell handover request will be repeated later (increases the BSC
signaling load) if no resource is free but thanks to the repetition of the handover request if the
radio conditions are still bad, the shared PDTCH preemption will be allowed (not the case if
put in queue).
For example on a 2 TDMA cell queuing can be done on 14 TCH TS, but in the case of a 2
TDMA cell with 3 shared PDTCH and minNbOfGprsTs = 0 the queuing can only be done on
11 TCH TS, so queued requests will leave the queue less quickly and one could see an
increase in the number of discarded requests.
Nortel confidential

6.1.3 RESOURCES STRATEGY
MINIMIZE IMPACT OF GPRS INTRODUCTION ON GSM
• Gprspreemption is set to no
• MinNbGprsTS is set to 0
It means that all PDTCH configurated are shared by GSM and GPRS and thePCU is not
allowed to NACK the preemption requested by the BSC.Impact on queuing, impact on
preemption depending on allocPriorityThreshold value.
GUARANTEE GPRS QUALITY OF SERVICE
• GprsPreemption set to yes

• MinNumberGprsTs > 0
It means that some resources are always dedicated to GPRS and that the PCU can NACK a
pre-emption requested by the BSC.
Impact on queuing and preemption efficiency since the PCU can NACK the preemption
It might be interesting to activate HO traffic so as to enable a spatial repartition of traffic on
overlapping cells (with protection against HO ping pong): this spatial repartition of traffic will
save PDTCH channels for GPRS traffic and guarantee a constant availability of preemptable
PDTCH.
TRADE-OFF ON GSM AND GPRS
• GprsPreemption set to no
• minNumberGprsTs> 0
IMPACT ON QUEUING.
Minimum resources are guaranteed to GPRS and all the other resources can be used by GSM
calls if needed since the PCU can never NACK a preemption. It might be interesting to
activate HO traffic so as to enable a spatial repartition of traffic on overlapping cells (with
protection against HO ping pong): this spatial repartition of traffic will save PDTCH channels
for GPRS traffic and guarantee a constant availability of preemptable PDTCH.
Nortel confidential

6.2. LAYER 1 MANAGEMENT: CHANGES BETWEEN V1 AND V2

L1M corresponds to the BTS software; it manages radio measurements and their processing.
Within the context of Automated Cell Tiering introduction, a new version of the L1m application
software (L1mV2) has been developed to support advanced features. This new version is
mandatory since V14.
This chapter is intended to highlight the major improvements of L1mV2 compared to L1mV1.
6.2.1 MAIN DIFFERENCES

In addition to the ability to support advanced features, L1mV2 brings enhancement on the
following points:
• Measurement processing
• Rescaling
• Capture process
• Neighbouring cell management
• Power Control Algorithm
MEASUREMENT PROCESSING
The measurement processing ensures that the network and mobiles communicate with each
other with the minimum interference, at the lowest possible transmission power and the best
transmission quality. With the L1mV2:
• The measurement processing is optimized in order to provide valid measurements

as early as possible: the MS and BTS measurements are available as soon as MS
measurements are received by the BTS, i.e. 1 SACCH period (480ms) delay
instead of 2 SACCH (960 ms) periods with L1mV1.
• The process of averaging/superaveraging is based on fully sliding windows in order
to take into account the most updated samples.
• In case of missing measurement, the last sliding average will be used instead of
the last synchronous average. That gives a better missing measurement update.
These major improvements will allow earlier decisions on SDCCH/TCH to be more accurate
since 0.5 seconds (over 1second) are saved on the processing delay of first measurements.
This will decrease the number of assignment failure. Moreover, the new measurement
processing will provide more reactive handover and power control decisions, enhancing the
global quality of the network.
Nortel confidential

RESCALING
RxLevel (UL & DL) measurement are rescaled in order to take into account the difference
between the reference Power and the real transmitted Power
• L1mV1: Reference power = Last value of power control command

• L1mV2: Reference power = maximum transmission power (Pmax)
Example:
Rescaling with msTxPwrMax = 30, rxLevHreqave = 4

lRxLevULP = -97 to -96
uRxLevULP = -93 to -92
L1mV1 Reference: last msTxPower = mr4 = 26

mr1 mr2 mr3 mr4
msTxPower 20 24 26 26
RxLev - 93 - 93 - 95 - 97
Delta 6 2 0 0 Average
Rescaled RxLev - 87 - 91 - 95 - 97 - 92,5
L1mV2 Reference: msTxPwrMax = 30

mr1 mr2 mr3 mr4
msTxPower 20 24 26 26
RxLev - 93 - 93 - 95 - 97
Delta 10 6 4 4 Average
Rescaled RxLev - 83 - 87 - 91 - 93 - 88,5
• computed Delta for rescaling = msTxPower - Ref_msTxPower

• computed Rescaled RxLev = OldRxLev - Delta
The rescaling performed by L1mV2 ( taking as the reference power = Pmax ) gives a RxLev
that is closer to real conditions. So L1mV2 will anticipate the decision of Power control and
Handover earlier than L1mV1.
CAPTURE PROCESS
Before L1mV2, the capture was launched only on the best microcell reported by the mobile,
and then the algorithm waited for the failure of the confirmation process before starting
another capture on the second best cell.
With L1mV2, this sub-feature launches in parallel the confirmation process for all the
microcells which verify the capture threshold providing a better reactivity of the system. If a
confirmation fails for a cell, the capture can be performed rapidly towards another cell
satisfying the criterion, increasing the probability to capture a microcell in a dense area.
Nortel confidential

NEIGHBOURING CELL MANAGEMENT
For the neighbouring cells monitoring and measurements, the mobile Measurement Report
contains received level from the 6 best neighbouring cells RXLEV_NCELL(n) and associated
BSICs + frequencies. The new L1m the Neighbouring cell management feature brings two
enhancements on the cellDeletionCount parameter and on the update of the neighbouring
informations.
CELLDELETIONCOUNT
The parameter cellDeletionCount is considered as a pure eligibility criterion. With L1mV1, the
neighbour cell information was discarded if the number of consecutive measurement reports
which does not contain measurements for this neighbouring cell was equal to
cellDeletionCount.
With L1mV2, the CellDeletionCount corresponds to the number of missing measurements
reports after which the neighbour cell is not eligible for a PBGT handover. But the
measurements related to this neighbour cell are not deleted as far as less than 10 consecutive
measurements (i.e. 5 seconds) are missing. That always allows a rescue handover after the
CellDeletionCount
Example: CellDeletionCount = 5
Rn measurement report n of a neighboring cell C by the MS
Rn+1 cell_Deletion_Counter = 4, Nb_of_Missing = 1

No more PBGT HO possible on this neighbouring cell
Rn+6 Nb_of_Missing = 6
this cell is no more candidate whatever the HO type, measurement reports for this cell are
deleted from the L1M.
Nortel confidential

Update on neighbouring informations

The other benefit concerns the updating of information for a neighbour cell not reported for
less than 5 seconds: when the number of neighbour cell reported by the MS is 6 (the
maximum), the RxlevNcell of non reported neighbour cells are update, for this period, by
taking the minimum value between:
• The RxLevNcell reported at the previous period

• And the lower RxLevNcell reported by the MS for this period and for a neighbour
cell in the same frequency band, degraded by 3 dB.
This process degrades gradually the level of a missing neighbouring cell, only when it is not
any more among the 6 best cells.
POWER CONTROL IMPROVEMENT
RF power control is used to minimize the transmit power required by the MS or BTS while
maintaining the quality of the radio links.
With the new version of L1m, the “step by step” power control algorithm is defined as “path
loss compensation” algorithm, with the introduction of a limitation based on the one shot
computation when there is a need to re-compute the attenuation (high level and good quality)
ALGORITHM STEP BY STEP
When Signal strength is bad (high path loss) or the quality is poor:
SAveRxLev < lRxLevXXP OR SAveRxQual > lRxQualXXP
with SAveRxLev is the weighted averages, there is no difference between L1mV2 and L1mV1.
Both compute a new attenuation request:
NewAttRequestdB = Max (CurrentAttRequestdB - IncrStepSize, 0)
When reception level and quality are good:
SAveRxLev > uRxLevXXP AND SAveRxQual < uRxQualXXP
L1mV1 always decrease the Tx power with the reduce step size set at the OMCR while
L1mV2 compute a new transmission power with total path loss compensation (increase or
decrease). The new increase (or reduce) step size is not necessarily the same as the one set
at the OMCR but it can not be higher than IncrStepSizeXX (or RedStepSizeXX)
Main Step for the new Tx power computed by L1mV2:
NewAttRequestdB = K* (SAveRxLev - lRxLevXXP)
with K=1 for the algorithm step by step

Limitation of attenuation Request
Nortel confidential

Case1:
IF NewAttRequestdB < CurrentAttRequest - IncrStepSize

THEN ordered attenuation = CurrentAttRequest - IncrStepSize
Case2:
IF NewAttRequestdB > CurrentAttRequest + RedStepSize
THEN ordered attenuation = CurrentAttRequest + RedStepSize
Case3:
IF CurrentAttRequest - IncrStepSize ≤ NewAttRequestdB ≤ CurrentAttRequest +

RedStepSize
THEN ordered attenuation = NewAttRequestdB
Note: The ordered attenuation request is always in the range [0, AttMaxdB], and with L1mV1
the SAveRxLev is the rescaled RxLev at last power command.
EXAMPLE 1: MS UPLINK POWER CONTROL WITH L1MV2
lRxLevULP = -97 to -96, RedStepSizeUL = 4

URxLevULP = -93 to -92, IncrStepSizeUL = 4
RxQual = 0.2 to 0.4
CurrentAttRequest + RedStepSizeUL
CurrentAttRequest - IncrStepSizeUL
ordered attenuation
CurrentAttRequest
NewMsAttRequest
CurrentMsPower
NewMsTx Power
MsTxPowerMax
Rxlev rough
RxLevUL
Step
Stable Rxlev at Pmax = -87
1 30 26 4 -91 -87 10 0 8 8 22
2 30 22 8 -95 -87 10 4 12 10 20
3 30 20 10 -97 -87 10 6 14 10 20
Path loss of 3 dB Rxlev at Pmax =-90
4 30 20 10 -100 -90 7 6 14 7 23
5 30 23 7 -97 -90 7 3 11 7 23
6 30 23 7 -97 -90 7 3 11 7 23
Path gain of 4 dB Rxlev at Pmax =-86
7 30 23 7 -93 -86 11 3 11 11 19
8 30 19 11 -97 -86 11 7 15 11 19
Rxlev Rough = RxlevPmax - currentAttRequest
Nortel confidential

RxLev Rough is the RxLev before the rescaling.

Here, the RxLevrough tends to reach lRxLevP when signal strength at Pmax is good,
furthermore the reduce step size and increase step size set at the OMCR are not necessarily
used.
Note: we have on the step 1 a decrease of 4 dB then on step 2 a decrease of 2 dB (even if the
reduce step size set at the OMC is 4 dB), this makes the Power Control distribution with
algorithm step-by-step different in L1mV1 from L1mV2.
EXAMPLE 2: MS UPLINK POWER CONTROL WITH L1M V1
CurrentAttRequest
CurrentMsPower
NewMsTx Power
MsTxPowerMax
Rxlev rough
Step
1 30 26 4 -91 22
2 30 22 NOP -95 22
3 30 22 NOP -95 22
Path loss of 3 dB
4 30 22 4 -98 26
5 30 26 NOP -94 26
6 30 26 NOP -94 26
Path gain of 4 dB
7 30 26 4 -90 22
8 30 22 NOP -94 22
Here the NewMsTxPower computed by L1mV1 is often higher than the MsTxPower computed
with the new version. So L1mV2 gains in efficiency.
Initial Power control "Step by step" decrease

-1 0
08
04
02
00
-1 6
1
8
6
2
0
6
4
8
6
4
2
0
2
0
-9
-9
-8
-8
-7
-7
-1
-1
-1
-1
-9
-9
-9
-8
-8
-8
-7
-7
-90 Path loss (RxLevPmax in dBm)

No new com mand between
-92
-94
-97 and -92dBm
-96
RxLev resul
-98
-100 Target R xLev V1
Medium Target RxLev V1
-102
Target R xLev V2
-104
-106
-108
-110
Note: the RxLev result in this graph corresponds to the RxLevrough
Nortel confidential

The figures below summarize the command for (UL or DL) transmission power according to
Rxlev and RxQual.
L1MV1
RxQual
Increase Tx Power
lRxQual
uRxQual
Decrease
Tx Power
lRxLev uRxLev RxLev
L1MV2
RxQual
Increase Tx Power
lRxQual
uRxQual
New Tx Power
computation
lRxLev uRxLev RxLev
Nortel confidential

STEP BY STEP POWER CONTROL EFFICIENCY
With the aim of minimizing the transmit power required by the MS or BTS, the new algorithm
“step by step” uses a realistic Rxlev (Rxlev rescaled at Pmax), this leads to a better
anticipation of the power control decisions.
Histograms below show an example of a RxLev downlink power control distribution for L1M V1
and L1M V2
DL RxLev Distribution (L1MV1)
600 110%
500 90%
# of Samples
400
70%
300
50%
200
100 30%
0 10%
10
04
07
01
1
4
-9
-8
-8
-7
-9
-9
-8
-8
-7
-7
-1
-1
-1
-1
Rx Lev
DL RxLev Distribution (L1MV2)
700 110%
600
90%
# of Samples
500
400 70%
300 50%
200
30%
100
0 10%
10
07
04
1
01
3
-8
-8
-8
-7
-7
-7
-9
-9
-9
-8
-1
-1
-1
-1
Rx Lev
One can see 50% time RxLev is better than -87 dB for L1mV1 and better than -89 dB for
L1MV2, so for the same percentage of time with L1mV2 lower power levels are used.
This explains the gain in the power control efficiency.
Nortel confidential

6.2.2 BENEFIT
The major benefit of L1mV2 is the ability to support advanced capacity and coverage features
such as Automated Cell Tiering (fromV12) which enhances quality and/or capacity of fractional
reuse in loaded networks.
In addition, as shown in the next chapter other benefits will be perceived on the network
thanks to introduction of some modifications
• In microcellular dense areas, the capture process will be more reactive thanks to
the parallel launch of confirmation process for all the micro cells reported by the
mobile.
• In dense urban areas where the neighbouring cells reported by the mobile are
numerous and fluctuant, with a better updating of eligible cells, the operator will
experience less handover failure.
• The uplink and downlink RxLev handover and intracell handover processes will be
triggered considering the RxLev which could correspond to a transmission at
maximum power, by comparing RxLev + attenuation (instead of RxLev) to the
handover threshold. This will result in less call drop, better quality. Handover
which could be avoided by powering up transmission will not be performed.
Moreover the interference level on the network will be decreased as mobiles will
remain as much as possible on the best server cell.
• Early Handover decisions on SDCCH/TCH will be more accurate since 0.5
seconds (over 1second) are saved on the processing delay of first measurements.
This will decrease the number of assignment failure. Moreover, the new averaging
of measurements based on sliding window will provide more reactive handover
and power control decisions, enhancing the global quality of the network.
• The power control is more efficient thanks to the rescaling performed by L1M V2; it
gives a better approach to real conditions.
6.2.3 CHANGE IN HANDOVER PERFORMANCE AFTER L1MV2

IMPLEMENTATION
When L1mV1 is activated, with mobiles in bad radio conditions (limit of cell coverage for
example), it can lead to a Radio Link Failure drop call. In same conditions, when L1mV2 is
activated, as missing measurements are better managed more handovers will be requested by
the BTS, that can save the call if the HO succeeds. As the mobile is in bad radio conditions,
some of these HO can fail but some of them succeed.
That’s why with L1mV2 (compare to L1mV1) one can see more HO failures (the system tries
to perform more HO in bad radio conditions) and less Radio Link Failures. Some of these HO
succeed instead of leading to a Radio Link Failure, thus the total number of dropped calls
decreases, leading to an improvement of the call drop ratio. Then, globally we can say that the
QoS is improved.
Many trials were performed on different networks to try to quantify this improvement. We can
assess that the repartition between Radio Link Failure drops and handover drops is modified:
less Radio_Link samples and more T3103 samples are observed after L1mV2 activation;
nevertheless the global call drop ratio is slightly improved.
Nortel confidential

6.3. ONE-SHOT POWER CONTROL

The one-shot power control algorithm allows high path loss compensation. However, some
mobiles are perturbed by high received signal strength variations and hence, several of their
measurements are wrong. If the mobile is near the base station antenna, with a few types of
mobiles the BTS will first decrease in a one-shot its transmit power, and then, because of
wrong measurements performed by the mobile, will increase its power to its maximum, this is
an oscillating effect.
Due to this effect, a maximum variation step of 8 dB has been introduced. During each
SACCH period, the power can be modified by 8 dB. From V12, the 8dB limitation applies only
for decrease.
One of the V8 step-by-step power control improvements consists of correlating both handover
and power control algorithms. However, this is not the case for the one-shot power control
algorithm (V9), hence it is possible to handoff even if the MS (or BTS) does not transmit at its
maximum power. This difference is due to the fact that the one-shot power control algorithm
should be reactive enough to be decorrelated from the handover algorithm.
With the step-by-step power control algorithm, an order to transmit at maximum power is sent
as soon as a handover is triggered. With the one-shot power control algorithm, the same order
is sent as soon as the power control is triggered.
The non correlation between both algorithms will not lead to avoid the increase of the power
before a handover. So the L_RXQUAL_XX_P shall be lower than L_RXQUAL_XX_H. A
difference of one step between both values provides an effective power control and keeps a
good reactivity for handovers.
Example: L_RXQUAL_XX_P = 3 and L_RXQUAL_XX_H = 4
A rapid variation of the quality (from 2 to 5) will trigger the handover algorithm and not the
power control algorithm. In the above example, a value equal to 4 for the power control
threshold (L_RXQUAL_XX_P) would be insufficient to keep a good reactivity for handovers.
During the algorithm validation period, a comparison was made between “one shot” power
control algorithm and “step-by-step” one. The conclusions were expressed as follows:
The “one shot” power control is correctly implemented according to functional specifications.
Without any deterioration of uplink and downlink quality, “one shot” power control activation
contribues to the following advantages:
• more power attenuation globally in the cell,

• quicker decrease to low power,
• quicker increase to maximum power.
Furthermore, the reactivity of the algorithm allows to set the one shot power control thresholds
to the step-by-step low ones without any impact on uplink and downlink quality.
One shot QoS metrics are also better than step-by-step ones.
However, these results come from a study over few days and in a specific configuration. It is
difficult to say that the “one shot” power control algorithm is simply better than the “step-by-
step” one. The quality is not degraded and it seems to lead to more power attenuation but
nothing allows to conclude surely that this algorithm is the one to use in all cases.
Nortel confidential

6.4. MINIMUM TIME BETWEEN HANDOVER

Different cases of handovers are given, and for each, the parameter setting influence is
described.
6.4.1 MICRO-CELLULAR NETWORK
HANDOVER MICROCELL TO MICROCELL
Avoiding handover ping-pong is important but a mobile could cross a cell in 2 or 3 seconds. A
delay (bts Time Between HO configuration) should not be used in this case.
The parameter setting should be:
• timeBetweenHOConfiguration = true, because the feature may be important for

other cells in the BSS.
• bts Time Between HO configuration = minimal value, e.g. = rxLevHreqave *
rxLevHreqt * 0.48 sec
Actually, even in such configuration, the value of the delay depends on the speed of the
mobiles. If the speed is low and the mobile speed in the cell is homogeneous then the delay
can be significant and have an action on ping-pong handover. If the speed is non
homogeneous then the most “rapid-moving mobiles” must be considered for the value of the
delay, though ping-pong handovers could occur. The lower the most rapid moving mobiles’
speed, the more important the delay is”. Then bts Time Between HO configuration is a
function of the cell size and the mobile speed.
In such situation, the problem of field variation is solved:
• If the mobile speed is low then the delay will help to avoid a ping-pong handover
• If the mobile speed is high, the averaging will not show all these variations.
HANDOVER MICROCELL TO MACROCELL
microCell means: its bts object cellType is set to microcell.
macroCell means: in the microcell adjacentCellHandOver object, the cellType field

corresponding to this macrocell is set to “umbrella” whatever the value of its cellType field in
its bts object (normal cell, umbrella or microCell). In this way a microCell can be seen as an
umbrella for another microCell.
This kind of handover is only triggered on alarm cause. So, in this case the delay is not very
useful.
Let’s consider the following case:
Nortel confidential

macroCell B
microCell A
microCell C
With a macroCell, the delay can be used for the microCell. A mobile that goes from microCell
A to macroCell B will perform a handover (on alarm cause). Then, it is worth setting a delay on
cell A to avoid a ping-pong handover (between A and C).
Therefore, this delay is beneficial for a mobile in cell C that turns into the street of cell A. The
same is true in opposite direction.
The only restriction is for a mobile coming from macro B and going to micro C. The delay has
a negative influence for the handover microA-microB. It is the same case as before.
In V12, the feature General Protection against HO ping-pong can solve this kind of problem.
For instance, in this particular case, the parameter hoPingPongCombination should be set to
(alarm, capture) and hoPingPongTimeRejection should be set to the previous V9 value of bts
Time Between HO configuration.
HANDOVER MACROCELL TO MACROCELL
The timer is usefull for a cell intersection where there is much interference.
Let’s take as an example a handover with cause “quality” triggered from macroCell A towards
macroCell B. But just after this change of cell, a handover with cause “power budget” is
attempted. Using an appropriate delay, depending on the speed of the mobile, many ping-
pong handovers may be avoided.
In V12, this is also achieved through the General Protection against HO PingPong feature
(see chapter General protection against HO ping-pong). In this particular case, the parameter
hoPingPongCombination should be set to (quality, PBGT) and hoPingPongTimeRejection
should be set to the previous V9 value of bts Time Between HO configuration. In order to
inhibit completely the ping-pong hoPingPongCombination should be set to (all, all).
Nortel confidential

6.4.2 NON MICRO-CELLULAR NETWORK.

The solution is the use of the minimum time between handover. The value of the delay
depends on the distance between the interference point and the point where macroA and
MacroB have the same level. With the hypothesis that the following neighbor cell is far away,
the value of the delay depends on the minimun speed of the mobile.
It is not really obvious to recommend a value because it is a question of interference point
position. So, before test and measurement results, the recommended value is the default
value: 16, that corresponds to 8 seconds.
There are two ways to determine the best value:
• system test: the counters show that ping-pong handovers exist. With a little
variation of the delay (bts Time Between HO configuration), it is possible to see
the influence (always with counters). So with only some steps of delay variation
the best value to avoid ping-pong handover and radio link failure can be found.
• measurements: with mobile measurements, the point of interference and the
equivalence point can be found. Then the delay value can be deduced from the
distance between both points.
However the following “light constraints” are applied to the value of the delay:
• average time of a mobile in the cell (weighted if nedeed for each speed)
• bts Time Between HO configuration.
Those constraints could also be a way to find the best value of minimum time between
handover.
In V12, same remark as before.
Nortel confidential

6.5. DIRECTED RETRY HANDOVER BENEFIT

This paragraph provides theorical studies results of the benefit that Directed Retry can provide
in mono and multi-layers Networks.The Directed Retry is mainly a benefit in the case of small
congestion zone in the network. In others cases the network is either under-dimensioned or
the queuing gives better results. Moreover, the HOTraffic feature must be favoured instead of
using Directed Retry.
Long duration
Directed Retry Network

under dimensioned
Duration of
congestion
Normal
situation Call
Large surface
6.5.1 BENEFIT OF FEATURE ON MONO-LAYER STRUCTURE
HYPOTHESIS
• 12 macroCells with 3 TRX/cell

• Non-combined BCCH
• 22 TCH available for the 12 cells
• 9 cells with 41% use rate (i.e. 9 TCH/22) and 3 overloaded cells with 26 channels
requested for 22 available (i.e. 24% of blocking rate)
• 25% of cell overlapping
WITHOUT DIRECTED RETRY
The carried capacity is:
• 9 cells * 9 TCH + 3 * 76% * 26= 140 Erlang

• the highest blocking rate is over 24%
Nortel confidential

WITH DIRECTED RETRY
The added carried capacity is:
• 25% cell overlapping => 25% * (24% * 26 requests * 3) = 4,7 Erlang

• the highest blocking rate is over 18%
With Directed Retry and 25% overlapping: gain on traffic 3,3% on the whole set of 12 cells of
this example and gain on blocking rate.
6.5.2 BENEFIT OF FEATURE ON MULTI-LAYERS STRUCTURE
HYPOTHESIS
• blocking rate of 2% max on the macroCell

• 3 TRX (22 TCH) with 9 TCH used / 22 (41% use rate)
• 1 TRX per μ -cell with not combined BCCH
• 10 requests for 6 TCH on the μ -cell (48% of blocking rate)
WITHOUT DIRECTED RETRY
Carried capacity of “n” μ-cell under 1 macroCell: = n μ-cell * 52% + 1 macro * 9 * 100%
For “n” μ-cell under 1 umbrella cell: number of carried Erlangs = 5,2n + 9
If n = 1, we have carried 14,2 Erlangs.
WITH DIRECTED RETRY
When the Macrocell begins to be full (the blocking rate will become low (from 2% to 3%)) then
no more calls are redirected from the µ-cell to the macro.
Capacity of microCell + macroCell: we aim to satisfy the 10 + 9 requests (i.e. 19 Erl needed):
n micro * X% * 10 + 1 macro * 9
The macro cell is able to carry: 14.9 Erlang
• 9 requests from the macroCell

• 5.9 requests from the μ-cells
Then, the macroCells keep: X% * ((n macroCell * 10) – 5.9)
WITH N = 1:
The Erlang law gives X = 87.6% (a blocking rate of 12.4%), the carried traffic is:
14.9 + 87.6% * (10-5.9) = 18.5 Erl
Gain 30% on ONE μ-cell and the highest blocking rate is over 12.4% (instead of 48%).
Nortel confidential

WITH SEVERAL N:
microCells transfer their calls into one umbrella-cell, and with the hypothesis of our example,
the gain should be (en = enabled, dis = disabled):
Erl carried DR(en) X(n) * (10n – 5,9) – (5,2n + 9)

Gain%= -1 Gain%=
Erl carried DR(dis) 5,2n + 9
As a consequence Gain(%) = f (number of µ-cells under one umbrella).
The best cells to implement directed retry are the cells that have potential problems due to a
lack of TCH resources. Directed Retry may solve the problem of load if the cell is the only one
to have this kind of problem in the close area. If the entire area is congested, almost no
improvement will be observed.
If queuing is enabled on the cell, the parameter setting of the queuing should lead to queues
of size 3 and a waiting timer of 6 seconds in the candidate cell.
From V15.0, Directed Retry can be also activated without queuing. See chapter Directed retry
without queuing activation for further informations.
The last value to set is the rxLev threshold used in the feature to choose a “good” neighbor
cell (distant mode). As the decision is taken on the basis of one measurement, a margin of a
few dBs needs to be taken to deal with multipath fading. Then, the advised value should be at
least rxLevMinCell + 3 dB.
Nortel confidential

EXAMPLE OF POSSIBLE CONFIGURATIONS:
At BSC level:
• interBscDirectedRetry = allowed
• intraBscDirectedRetry = allowed
• modeModifyMandatory = used
• bscQueuingOption = forced
• timeBetweenHOConfiguration = true
• HOSecondBestCellConfiguration = 3
At Cell level (where directed retry is implemented):
• allocPriorityTimers = 0 0 6 0 0 0 0 0
• allocWaitThreshold = 0 0 3 0 0 0 0 0
• directedRetryModeUsed = bts
• interBscDirectedRetryFromCell = allowed
• intraBscDirectedRetryFromCell = allowed
At neighbor cell level:
• directedRetry = rxLevMinCell + 3 dB
• hoPingPongTimeRejection = 30 (= the previous V9 value of bts Time Between HO
configuration
• hoPingPongCombination = (DirectedRetry , all) or for instance (DirectedRetry,
PBGT)
At cell level for neighbor cells:
• bts Time Between HO configuration = 1 (V12 update, the parameter changes its
possible vallues)
• allocPriorityThreshold = 3
Nortel confidential

6.6. CONCENTRIC CELLS

The concentric cell feature has been introduced from the BSS version V9.1. The main
principle is to define two zones in a cell: inner (or small) and outer (or large) zone. BCCH and
signaling channels use TMDAs of outer zone.
Outerzone
Innerzone
(large zone)
(small zone)
traffic BCCH and
channels signalling
channels
This feature enables the system to have two separate zones within the same cell using
different TDMAs and giving the operator flexibility to have separate frequency hopping
systems. Therefore, concentric cell zones give better spectral efficiency through mobility
management between zones and being able to increase inner zone frequency reuse.
For a good understanding of this feature, please refer to the chapter
Concentric/DualCoupling/DualBand Cell Handover, and the associated Functional Notes [R10]
Concentric cell improvements (CM888/TF889) and [R11] FN for stepped coupling.
Expected Network Impacts:
• Radio Quality Improvement: C/I and RxQual improvement and an overall RF and
HO drops improvement
• Slight increase in intracell HO drops, inherent to concentric cell interzone traffic
management.
Nortel confidential

6.6.1 CONCENTRIC CELL PARAMETER DEFINITION
concentAlgoIntRxLev
concentAlgoExtRxLev (inner to outer
(outer to inter threshold) threshold)
biZonePowerOffset
+ hysteresis Margin
As shown on the figure above, the definition of inner zone coverage depends mainly on
concentAlgoExtRxLev; concentAlgoIntRxLev and biZonePowerOffset+hysteresis parameters.
Main related parameters to the concentric cell feature are listed below:
Parameter Description
concentric cell enable the concentric cell feature on the cell (also used for dualband / dualcoupling)
level threshold used for TCH Direct Allocation in the inner zone or to trigger an interzone HO from the
concentAlgoExtRxLev
outer to the inner zone
concentAlgoIntRxLev level threshold used to trigger an interzone HO from th inner to the outer zone
offset used to simulate the power difference between TDMAs of the inner and the outer zone (power
biZonePowerOffset
difference either due to power emission, coupling losses or propagation losses)
zone Tx power max reduction set the power difference between the two zones of a concentric/dualaband/dualcoupling cell
distance threshold used for TCH Direct Allocation in the inner zone or to trigger an interzone HO from
concentAlgoExtMsRange
the outer to the inner zone (not used for dualband functionality)
concentAlgoIntMsRange distance threshold used to trigger an interzone HO from th inner to the outer zone
offset used to reflect the difference of propagation between the two zones of an adjacent cell in case of
biZonePowerOffset(n)
handover toward the inner zone
rxLevMinCell(n) minimum signal strength level received by MS for being granted access to a neighbor cell
CONCENTALGOEXTRXLEV
The concentAlgoExtRxLev value can be set depending on how TRXs capacity in the cell is
shared between the inner and outer zone. The following figure shows CPT cumulative
distribution of RxLev uplink and downlink of a cell before concentric cell activation.
concentAlgoExtRxLev may be deduced from the downlink RxLev distribution which represents
samples of communications in function of the strength level.
Nortel confidential

On the figure above we can see that only 10% of the traffic is handled with a level under -86
dBm. So if the traffic size of inner zone (% of TS in the inner zone with regard to total number
of TS in the cell) is 90% of the outer zone, it means that 90% of downlink Rxlev sample may
be inside of inner zone, and 10% is outside. A downlink RxLev value L90, L75 or L50 should
then correpsond to 90%, 75% or 50% of traffic on the inner zone.
concentAlgoExtRxLev = LXX (use of the CPT tool)
BIZONEPOWEROFFSET (HANDOVERCONTROL OBJECT)
biZonePowerOffset is used to simulate the power offset between TDMAs of the inner and the
outer zone.
CONCENTRIC CELL CASE
In this case biZonePowerOffset simulates the power difference between the two zones
introduced by zone Tx power max reduction of the inner zone.
• zoneTxPowerMaxReduction(outer) = 0
• zoneTxPowerMaxReduction(inner) = 0, best value tested (see chapter zone Tx
power max reduction)
biZonePowerOffset = zone Tx power max reduction(inner)
DUALCOUPLING CELL CASE
introduced by coupling losses.
• zone Tx power max reduction(outer)=0

• zone Tx power max reduction(inner)=3 simulates the D/H2D configuration
• zone Tx power max reduction(inner)=4 simulates the H2D/H4D configuration
biZonePowerOffset = zone Tx power max reduction(inner)
Note: DLU Attenuation should be NULL and replaced by zone Tx power max reduction as
explained in the parameter description: zone Tx power max reduction and concentric cell.
Nortel confidential

DUALBAND CELL CASE
introduced by propagation losses. It should then be set according to the band used on the cell.
biZonePowerOffset = +3 dB (dualband: main band= 850 or 900 MHz)

biZonePowerOffset = -3 dB (dualband: main band= 1800 or 1900 MHz)
CONCENTALGOINTRXLEV
To avoid ping-pong interzone HO, a hysterisis margin is recommended. The level threshold to
trigger an interzone HO from the inner to the outer zone could be calculated as follow:
concentAlgoIntRxLev = concentAlgoExtRxLev - Hysteresis Margin -

biZonePowerOffset
where Hysteresis Margin = 4 dB is recommended.
BIZONEPOWEROFFSET(N) (ADJACENTCELLHANDOVER OBJECT)
biZonePowerOffset(n) in adjacentCellHandover object reflects the difference of propagation

between the two zones of an adjacent cell in case of handover toward the inner zone. When
attempting an HO directly to the inner zone of an adjacent cell EXP2xx(n) = hoMarginxx(n) +
biZonePowerOffset (n) > 0 shall be respected. So in order to avoid HO in sequence after
incoming HO into inner zone, it’s necessary to respect the following relation:
biZonePowerOffset (n) = concentAlgoExtRxLev(n) - r xLevMinCell(n)
rxLevMinCell(n)
concentAlgo
ExtRxLev(n)
cellA cellB
Nortel confidential

6.6.2 CONCENTRIC CELL FIELD EXPERIENCE
RADIO QUALITY IMPROVEMENT
Inner zone isolation-capacity trade-off is found in concentric cell. The smaller the inner zone
coverage, the better inner zone isolation is found but less traffic, which takes profit of higher
inner zone fractional reuse pattern, is carried. Concentric cell success on improving KPI
performances is based on this balance.
On one hand reducing inner zone coverage:
• provides better isolation of inner zone interferences by keeping only the calls with
very good RxLev to enter the inner zone
• allows deploying a more constraining inner zone frequency plan (or a consequent
inner zone radio quality improvement) and reducing 3107 drops since inter HO are
done in better radio conditions.
On the other hand, one of the inherent risks of using this approach is to block on the outer
zone while resource availability remains on the inner zone. Even though inner zone blocking is
not customer perceived (calls can overflow onto the outer zone radios if available TCH
resources), a compromise exists between the traffic distribution between the zones, and the
improvement in KPI. Therefore, additional tuning of the concentAlgoExt/IntRxLev thresholds
may be necessary on certain sites to set an appropriate threshold for transitioning from and to
the inner zone.
INNER-OUTER ZONE CAPACITY TRADE-OFF
It is recommended having more than 1 TDMA on outer zone since it allows redundancy in
case BCCH TDMA is lost, and also because TDMAs carrying SDCCH channels must also be
on the outer zone. Furthemore, it is advised to have higher capacity in the outer than in the
inner zone, because it minimizes the probability that outer zone is blocked, which would cause
a capacity cell reduction even if inner zone TS are available.
60%-40% outer-inner capacity is recommended.
CONGESTION TARGET FOR HO TRAFFIC
Capacity is shared between inner and outer zone depending on TDMAs allocated in each
zone. Outer zone congestion targets should be updated to take into account reduction in terms
of TDMAs in outer zone. Inner zone is not considered for congestion since no congestion for
the user is found when all TS are occupied.
SDCCH DIMENSIONING
It should be noted that with Concentric Cell SDCCH channels cannot be configured in the
inner zone and all the SDCCH channels will have to be re-mapped to the outer zone radios.
All the sectors prior to implementation of Concentric Cell in the concerned BSCs must follow
Nortel’s recommended rule of spreading the SDCCH channels amongst different radios and
therefore had to be re-mapped carefully such that SDCCH congestion is not encountered.
Nortel confidential

CONCENTRIC CELL PARAMETER TUNING
ZONE TX POWER MAX REDUCTION
This parameter is used to reduce the output power of the BTS on the inner zone TDMAs to
improve inner zone isolation. Simulations show it is preferred to keep the inner zone reduction
at 0 dB and rely on power control efficiency to reduce power level. Like this, power control is
always capable to power up to maximum power to save worst call who received punctual
interferences. Inner zone power reduction has not brought any significant KPI improvement
when it has been tested on field trials.
Simplified power control simulation results are shown on graph below. 250 meters of cell
radius in 1900MHz (150 meters for inner zone coverage which corresponds to 40% inner zone
capacity for a uniform traffic distribution) and perfect power control to attempt DL RxLev target
of -86 dBm are considered.
BTS Power and RxLev evolution depending on

BTSoffset parameter
50 -84,0
45 -86,0
40 -88,0
BTS Power [dBm]
35 -90,0
RxLev[dBm]
30 -92,0
25 -94,0
20 -96,0
15 -98,0
BTSPower(Offsetpower0)
10 BTSPower(Offsetpower8dB) -100,0
InnerZone Coverage (40%)
5 -102,0
RxLev(Offsetpower0)
0 RxLev(Offsetpower8dB) -104,0
0,00 0,05 0,10 0,15 0,20 0,25
Cell Range [km]
If BTS inner zone TDMA are not attenuated at all (0dB), 14,8 dBm mean BTS TX DL power
would be found while if 8 dB output power would be attenuated, mean BTS TX DL Power
would become 13,4 dBm. Therefore the impact on interference and isolation on innerzone is
very limited and it is preferred to leave power control the possibility to power up rather than
induce an external attenuation
CONCENTALGOEXT/INTRXLEV
It is recommended to set concentAlgoExtRxLev using CPT tool. DL RxLev number of samples

repartition found in CPT is a good indicator on how traffic load is spread around the cell.
concentAlgoExtRxLev threshold can be defined to match inner/outer zone capacity repartition.
It is recommended to define concentAlgoExtRxLev instead of concentAlgoIntRxLev through
CPT methodology. Like this, inner zone RxLev samples are slightly underestimated (signal
Nortel confidential

level from concentAlgoExtRxLev and concentAlgoIntRxLev could also be allocated in inner

zone) and a margin to pack the inner zone TDMAs is left.
concentAlgoExt/IntRxLev impact on inner/outer traffic load has not shown to be very sensible
to their value. Same mean values have been spread all over clusters in field trials and they
have required little tuning to avoid outer zone blocking and KPI improvements.
CONCENTALGOEXT/INTMSRANGE
concentAlgoExtMsRange and concentAlgoIntMsRange could be used to reinforce or to

complement inner and outer inter zone handovers using concentAlgoExt/IntRxLev.
The calculated distance between the MS and the BTS is based on timing advance (TA), which
has an accuracy of ± 3 bits (corresponding to more than 1,5 km), due to the shift of
synchronization of some MSs. Thus, this parameter is not very useful in urban areas where
the cell size is relatively small and due to the multipath effect, the MS to BS distance is not
very accurate. However this parameter could be used in rural areas or suburban areas.
BIZONEPOWEROFFSET IN DUALBAND CELLS
6 dB Rxlev DL level difference has been found between 900 MHz and 1800 MHz calls due to
propagation losses in field trials. When a call who is allocated in the outer zone (900MHz) is
inter handover to inner zone (1800MHz), 6 dB level loss is expected to be found due to
propagation loss.
Since biZonePowerOffset is taken into account in power budget handovers, there is a trade-off
between biZonePowerOffset value and number of power budgets of inner zone calls. Having a
biZonePowerOffset too big can reduce significantly power budget of inner cell provoking calls
to be dragged to inner zone cell edge because of overestimating own BCCH level of the
outerzone.
6 dB presents a good trade-off and it is the value recommended.
INTRACELL HANDOVER DROP SLIGHT INCREASE
On activation of concentric cell feature, interzone handovers get triggered based on signal
level within the same cell, increasing the probability of dropped calls. The key to successful
implementation of Concentric Cell is to reduce the other drop call components such as T3103
and RLT Drops.
HYSTERISIS MARGIN DEFINITION
The inner to outer Hysteresis Margin corresponds to the delta between concentAlgoIntRxLev
and concAlgoExtRxLev minus zone TX power maximum reduction. The delta should be
adequate so that the captured traffic in the inner zone (which is the key to spectral efficiency)
is not immediately allocated back to outer zone via a ping-pong handover. A big hysterisis
zone helps to contain the users in the inner zone and keeps this zone packed in order to avoid
losing capacity and interzone HO, therefore it reduces T3107 drops.
Nortel confidential

L1M REACTIVITY
It is not recommended to increase L1m reactivity when concentric cell is used for HO
decisions since it can increase significantly interzone HO with the consequent increase on
T3107 drops. An average of 8 frames is recommended.
CONCENTRIC CELL IMPACT ON AMR HR PENETRATION
Interzone handover from inner to outer zone is considered as a quality handover. Therefore,
even though an AMR HR call was on going in the inner zone, after a quality inner to outer
interzone handover AMR FR is allocated in outer zone.
Depending on AMR FR to HR and HR to FR thresholds, this interzone handovers can cause
an increase of intracell HO from HR to FR (inner to outer zone) and immediately from FR to
HR (in the outer zone), reducing AMR HR penetration on the cell.
Nortel confidential

6.7. IMPACT OF DTX ON AVERAGING

The RxLev_Full measured on a dedicated channel is the arithmetic mean of 104 received time
slots power, excepted in the case of DTX: then it is the arithmetic mean of only 12 received
time slots power.
A study was done to compare the difference (RxLev_Full - RxLev_Sub). It was based on
10800 measurements from a single network, characterized by a great proportion of microcells
and a high RxLev mean value.
The following array presents the results of this study. We considered the difference
(RxLev_Full - RxLev_Sub), without averaging (1 measurement), and then with averaging on 2,
3, 4 and 8 measurements.
number of values for averaging 1 2 3 4 8

mean value of RxLev_Full - RxLev_Sub (dB) - 0,15 - 0,15 - 0,15 - 0,15 - 0,15
standard deviation (dB) 2,12 1,48 1,19 1,03 0,72
The results show that, for an averaging on 4 measurements, the standard deviation is only 1
dB. This is insignificant enough to consider that we can run simulations, and analyze the
measurements with one of the two levels, if we don’t know which one is used.
Moreover, the measurement processing used for the neighbor cells is close to the process
used in the case of DTX: it is the arithmetic mean of about (104/N) received time slots power,
where N is the number of neighbor cells declared, between 1 and 32.
If 6 < N < 12, which is often the case, the two processes are quite comparable. 8 to 10 for
neighbor; standard deviation on RxLev_Sub can be extended to RxLev(i).
This means that the RxLev_NCell(i) measured on a neighbor cell, is close to the RxLev that
would be measured if it was the current cell.
Nortel confidential

6.8. BEST NEIGHBOUR CELLS STABILITY

The parameter CellDeletionCount is used to keep a neighbor cell eligible, even if a few
measurements are lost.
A study was done with a measurement file of 2 hours, without handover. Each time one of the
6 best neighbor cells disappeared, the time before it re-appeared, called absent_time, was
calculated. 420 absent_times were found; that follow this distribution:
absent_time (s) % % cumulate

0,66 1,18 1,18
1,32 1,89 3,07
1,98 4,01 7,08
2,64 5,42 12,5
3,3 1,89 14,39
3,96 4,01 18,4
4,62 4,48 22,88
5,28 1,65 24,53
5,94 1,42 25,94
6 to 11 8,02 33,96
> 11 66,04 100
Note: absent_time values are multiples of 0,66 seconds.
For instance, for the recommended value 5 and according to these measurements, in 12,5
percent of the cases the neighbor cell concerned is accessible after 2,64 seconds, in 87,5
percent, it is still missing.
Nortel confidential

6.9. TCH ALLOCATION GENERAL RULES

When no queuing is allowed, as no request can be treated by the BSC at the same time, there
are two kinds of TCH allocation requests:
• priority 0: the request is acknowledged if there is at least one free TCH

• priority > 0: the request is acknowledged if there is at least allocPriorityThreshold +
1 free TCHs
If allocPriorityThreshold equals 0, all the requests are treated in the same manner.
If queuing is in OMC driven mode (run by the BSC), incoming handovers cannot be queued.
The highest priority must be given to incoming handovers.
The queuing plays a part when, there is not enough TCH resources. When traffic increases to
a blocking state, the queuing has no impact on the total ratio of TCH allocation success: the
more call attempts that are acknowledged, the more incoming handovers are refused.
The queuing is prefered when all TCH resources are busy during a short time; it cannot
replace a resource.
Please refer to chapter TCH Allocation Management.
Nortel confidential

6.10. GENERAL RADIO FREQUENCY RULES

1) In dB, the path loss slope with distance, decreases as 1/D. This means that the received
signal variation, in dB/m, is greater at the close vicinity of the base station and decreases with
the distance. It depends directly on the propagation exponent.
2) We can assume stationnarity (during some seconds) of the median path loss in dB,
assumption is more and more valid since the MS is far from its antenna cell, close to the
handover area.
3) Shadowing is due to obstruction of the signal paths, created by obstacles. It is known that
these obstacles create log_normal variations of the received signal, ie the received power at a
distance, expressed in dBm, fluctuates as a gaussian random variables.
4) The shadowing “depth” is strongly linked to the position of the mobile as compared with the
dominant building, and as a consequence, that shadowing decorrelates when different
buildings are involved. With a building mean width d = 30m, shadowing can be considered
completely decorrelated.
5) The higher the mobile speed, the smaller the impact of the shadowing on the average
signal.
6) The higher the average window size is, the smaller the impact of the shadowing on the
average signal is.
7) The variance of the signal due to the Rayleigh fading, depends on the speed of the mobile
and of the frequency in use. About 30 to 50 wavelengths must be spanned to ”filter out” the
fading variations with a residual error less than 1 dB. If the number of samples is equal to N =
10 the mean matches the true local mean to within 2 dB at 90%.
8) Whatever the mobile speed, from a certain window size the increase of the size does not
modify the average Rayleigh standard deviation. From 8 to 16 samples, even at a very low
speed the gain is inferior than 0.5 dB.
9) The dispersion of two MRC combined Rayleigh is decreased by more than 1.5 dB for an
MRC order 2, compared to a single channel. It means that diversity reception can help
average out the fading faster than a single channel, i.e the local mean is tracked faster. If d >
20 l, an efficient 2 order space diversity has the same effect as multiplying the speed by 3 to 4.
10) .With Rayleigh fading, it is known that the mean in dB of samples in Watts is greater than
the mean in dB of samples in dBm. The limit is 2.5 dB, that means that the RXLEV tends to be
artificially 2.5 dB higher for the uplink than for the downlink.
11) The RxLev_Full as measured on a dedicated channel is the arithmetic mean of 104
received time slots power, in the case of DTX, only 12 times.
Nortel confidential

6.11. DIFFERENCE BETWEEN UPLINK AND DOWNLINK LEVELS

At the BTS, averages are performed from measurements made in Watts before . On the
contrary, some MS make measurements in dBm and then, perform their averages. In Rayleigh
environment, the first method of calculating can be up to 2.51 dB higher than the second
method.
This comes from the fact that in Rayleigh fading environment, the information goes through
several paths (at least two) between the BTS and the MS. At the antenna, according to the
phase of the signal, the different path can add up or not. This varies with time and it can vary
from complete cancellation (hole) or, on the contrary, perfect adding. This effect is called
multipath fading.
This effect implies that received levels follow a Gaussian law and its mean has an exponential
density. The evaluation of the bias between the mean of the decibels and the mean in
decibels is then:
10 .Log (e) ξ = 2.51 dB
This comes from the following expression that relates the mean of the natural logarithm of an
exponential random variable of mean one to the Euler constant (ξ):
∑ Ln (x) exp (- x) dx = ξ = 0,57721
The 10.Log (e) factor just accounts for the base 10 log.
In this normalised example:
• averaged mean of Watt samples converted in dB = 0 = BTS calculation

• averaged mean of dB samples = 2.51 dB = MS calculation
So, the maximum difference between the two ways of calculating the average power is 2.51
dB. The uplink value will be the higher.
However, here, the hypothesis of the Rayleigh fading lead to deal with two paths, if there are
many paths, the value of the correction needs to be decreased.
Nortel confidential

6.12. EFFECTS OF “NOOFMULTIFRAMESBETWEENPAGING” ON

MOBILE BATTERIES AND RESELECTION REACTIVITY
The parameter noOfMultiframesBetweenPaging determines how often the mobile must listen
to its paging group. It has a great influence on the mobile batteries. Therefore, this value
should be raised as far as possible, so the mobile will consume less energy by listening to the
paging messages channel less often.
Changing noOfMultiframesBetweenPaging from 2 to 6 leads to a gain of at least 18% of the
batteries duration.
On the other hand, this parameter is involved in the computation of the measurements number
that a mobile averages in idle mode over reselection list.
The exact formula is:
Max(5, ((5xN+6)DIV7)x NoOfMultiframesBetweenPaging /4) seconds
with N = number of BCCHs to monitor.

This formula, confirmed by field tests, shows that increasing the parameter
noOfMultiframesBetweenPaging slows down the cell reselection mechanism.
Two different cases must be studied in order to find a trade-off:
• In a rural environment
the reselection list usually contains a maximum of 5 reselection neighbours.
Up to 5 reselection BCCHs, a noOfMultiframesBetweenPaging equal to 6
does not slow down the reselection mechanism too much. So it is possible to
advise an increase of the default value.
• In a urban environment
cells size and mobiles speed generate an important constraint in terms of
reactivity. Moreover, an urban cell has much more BCCH frequencies in its
reselection list. Therefore, noOfMultiframesBetweenPaging should not be
too high to keep a good reselection reactivity.
The following curves have been drawn using the formula Max(5, ((5xN+6)DIV7)x
NoOfMultiframesBetweenPaging /4) seconds with N = number of BCCH to monitor, to
compute the periodicity of reselection measurements average.
Nortel confidential

Periodicity of noOfMultiframesBetweenPaging = 2
reselection noOfMultiframesBetweenPaging = 4
(in seconds) noOfMultiframesBetweenPaging = 6
25
20
15
10
0
0 3 6 9 12 15
Number of BCCH to monitor
From those curves, one can define a value of noOfMultiframesBetweenPaging that doesn’t
slow down the reselection mechanism depending on the number of BCCH to monitor in the
reselection list:
numbers of BCCH in the reselection list noOfMultiframesBetweenPaging

≤4 6
≤6 4
≤ 13 2
from 13 to 32 none
With more than 13 neighbours in the reselection list, any value for
NoOfMultiframesBetweenPaging will slow down the reselection mechanism.
Therefore, with a cell that has up to 4 BCCHs in its reselection list, it is advised to set
noOfMultiframesBetweenPaging = 6. In that case, the lost of reselection reactivity will
correspond to 10% (5,57 seconds instead of 5), and the gain for batteries is very important.
LCAUTION!
noOfMultiframesBetweenPaging is also used in the paging algorithm. A higher value will
decrease the paging reactivity and might lead to double paging response (in case of paging
repetitions) if the call is set up and released quickly . A trade-off between the saving of
batteries and effective paging has to be found.
Please also refer to chapter GSM Paging Repetition Process Tuning.
Nortel confidential

6.13. EFFECTS OF SMS-CELL BROADCAST USE ON

“NOOFBLOCKSFORACCESSGRANT”
If the SMS-CB feature is activated, SMS-CB messages are carried on the CBCH, a sub
channel of the SDCCH. The TDMA model mapping of the SDCCH becomes SDCCH-CBCH/8,
and the CBCH occurs from frame number 8 to frame number 11 of the SDCCH multiframe.
If noOfBlocksForAccessGrant = 0, then a paging message can be transmitted on frames
number 8 and 9.
Then, if the SDCCH is transmitted on the Time Slot 0 of another TDMA than the one carrying
the BCCH, a collision will occur.
In that case, the mobile must choose between an incoming call and a SMS-CB, by selecting
one kind of data to listen.
Setting noOfBlocksForAccessGrant to a value superior or equal to 1 avoids this problem: only
AGCH can be transmitted on that block.
This rule
NoOfBlocksForAccessGrant > 1
is a recommendation requirement on not combined CBCH.

In that case, on the frame number 8 and 9, the MS can just receive an Immediate Assignment.
If an Immediate Assigment message is transmitted, it means that the mobile has sent a
channel request, and is not in idle mode any more. Therefore, the MS won’t listen to the
CBCH channel.
Please also refer to chapter Consequences of NoOfBlocksForAccessGrant.
Nortel confidential

6.14. IMPACT OF THE AVERAGING ON THE HANDOVERS

The following study applies only to L1M V1.
Simulations have been performed with NMC Engineering tools to determine the impact of
some BSS parameters values in terms of handover reactivity. The simulations were performed
from real RF measurements and network field configuration.
Four Simulations have been performed with the following sets of parameters:
runHandOver Hreqt
1 2 2
2 2 1
3 1 2
4 1 1
The results are spread on three items:
• Global statistics: number of HO in each configuration.

• Study of reactivity: impact of parameters on reactivity.
• Reactivity vs ping-pong.
6.14.1 GLOBAL STATISTICS
HO CAUSE PBGT AND QUALITY DL
For each of the four sets of parameters presented, the amount of HO on quality DL and PBGT
is the same.
HO CAUSE LEVEL DL
The modification of the parameters has a low impact on the total amount of HO detected on
Level DL cause.
HO CAUSE CAPTURE
For each of the four sets of parameters used, the total amount of handovers is the same. The
difference is not significant because microCellCaptureTimer * runHandover is kept constant.
CONCLUSION
The simulations show that:
• Setting Hreqt=1 instead of 2 has a very low impact on the total amount of
handovers (less than 4%)
• Same conclusion for runHandover=1 instead of 2
Nortel confidential

6.14.2 STUDY OF REACTIVITY

The second item of the study is to show the impact of runHandover and Hreqt on the
reactivity: how much sooner do the handovers occur ?
RUNHANDOVER=1
Field simulations have shown that such a value of runHandOver has low impact on reactivity
compared to runHandOver=2. The increase of reactivity due to runHandOver=1 is less than or
equal to 0,5 second.
HREQT=1
The influence of Hreqt on reactivity is much more decisive, 15% are being advanced by setting
Hreqt=1 (hoMargin unchanged). Two reasons can explain this:
• After the beginning of communication on a new TCH, L1M waits for a fixed delay
before a new HO: HreqAve*Hreqt*0,48 sec. Among the HO performed within 8
seconds1 after a callsetup or another HO, 45% are advanced thanks to
Hreqt=1.This can be very helpful if, for example, the callsetup was initiated on a
bad cell, because of Reselection failure.
• Reducing the length of the weighted averaging window can make the variations of
the weighted average less smooth. This effect is observed for only 2% of the HO.
For this particular case, it is still possible to tune hoMargin. The low impact of this
measure can be explained as follows.
HREQT=2
That configuration does not always double the size of the averaging window.
Example: runHandover=1, HreqAve=4, Hreqt=2. Every runHandover, the L1M calculates a
weighted average based on the last average stored and the sliding average of the moment.
These two averages can have up to 3 measures in common.
CONCLUSION
• Hreqt=1 is an efficient way to increase reactivity for 15% of the HO.

• Among the HO performed within 8 seconds (after call setup or another HO), 45%
are performed sooner with Hreqt=1 (in average 1,6 sec sooner).
• Among the HO performed long after the beginning of the communication, only 2%
are performed sooner because Hreqt=1 makes the weighted average less
smooth.It is still possible to tune hoMargin.
• runHandOver=1 can not advance HO of more than 0,5 sec.
6.14.3 PING PONG VS REACTIVITY

Among the 15% of HOs that were advanced for more than 1 second by Hreqt=1, simulations
show that without changing hoMargin, no supplementary ping pong handover was observed.
Nortel confidential

6.15. IMPACT OF CALL RE-ESTABLISHMENT ON THE NETWORK
6.15.1 IMPACT ON CAPACITY

The Call-Reestablishment feature has a big impact on the MSC resources occupation. Without
Call Re-establishment, T3109 (BSC timer) is usually set to a small value (>
Min(radioLinkTimeOut, 4*rlf1+4) which is given in SACCH block) in order to free resources as
soon as possible after a radio link failure (see t3109 recommanded value).
Setting a large value to T3109 for Call Re-establishment leads the MSC to freeze the resource
for the call waiting for a Channel Request from the MS. Therefore, if the MS is unable to select
a destination cell, or if the radio link failure is due to coverage limits (border cells), the
resource is frozen for nothing.
Call Re-establishment should not be activated on border cells, or the impact could be reduced
by decreasing the value of T3109 on these specific locations.
On the other hand, on Sunday network, tests have been performed showing that, after the Call
Re-establishment activation, nearly no trunk erlangs have been noticed by Mandarin Radio
Engineers.
Please also refer to chapter Call reestablishment procedure (Cr).
6.15.2 IMPACT ON CALL DROPS

The Call Re-establishment doesn’t decrease the amount of call drops from a counter point of
view, even if it improves the quality of service. The subscriber is satisfied to get back his
communication after few seconds instead of totally loosing it, but this procedure is launched
after a call drop detection, counted by the system.
Moreover, the Call Re-establishment can increase in some cases the overall number of call
drops. For instance, when a temporary destination cell is selected by the MS without providing
a long term solution:
The operator can deduce that Call Re-establishment has a bad influence on call drops
amount. Actually, the communication lasts longer, maybe allowing the subscriber to end his
call properly.
Nortel confidential

6.16. FREQUENCY SPACING BETWEEN TWO TRXS OF THE SAME

AREA
At present, Nortel BTSs use only the hybrid coupling technology.
The following recommendations take into account the minimum C/I requirements presented in
GSM 05.05:
• C/I>=-9dB for first adjacent channels (200kHz)
• C/I>=-41dB for second adjacent channels (400KHz)
• C/I>=-49dB for third adjacent channels (600KHz)
6.16.1 INTRA_CELL
Considering the UL power control activated, Nortel recommends a minimum of 400khz
frequency spacing between TRX on a same cell with or without frequency hopping, to
guarantee voice quality.
6.16.2 INTRA_SITE
No hopping case:
Considering the UL power control activated, Nortel recommends a minimum of 400 kHz
frequency spacing between TRX on a same cell without frequency hopping, to ensure a
satisfactory service quality.
Hopping:
Generally, when hopping and considering the UL power control activated, the minimum
recommended frequency spacing between TRX on a same site is 400 KHz. However, the
frequency spacing between TRX on a same site could go down to 200 KHz in the following
cases when some intra-site adjacencies allows a satisfactory service quality:
- 1x1 or 1x3 hopping plan when the site fractional load <= 60 %;
- adhoc hopping plan when different HSN s are used by the co-site cells;
6.16.3 INTER_SITE
Nortel recommends a minimum of 200 kHz frequency spacing between inter-site TRX with or
without frequency hopping, to ensure a satisfactory service quality.
Nortel confidential

6.17. LINK BUDGET (LB)

The Link Budget is composed of the Uplink & Downlink gains and losses, and of system and
propagation parameters, to determine the path loss.
UPLINK BUDGET:
MS_pwr + MS_ant_gain - (BTS_sen - BTS_ant_gain - Others_UL_gains +

Others_UL_losses)
• Others_UL_gains = BTS_div_gain, OR LNA_gain (for external LNA only)

• Others_UL_losses = BTS_feeder_loss + Body_loss
DOWNLINK BUDGET:
BTS_pwr + BTS_ant_gain - Others_DL_gains + Others_DL_losses - (MS_sen -

MS_ant_gain)
• Others_DL_losses = BTS_feeder_loss + XP_loss + Body_loss

• XP_loss is for slant polarization loss when using cross-polarized antennas
Others_XX_gains and Others_XX_losses (XX stands for UL or DL) represents all the margins
that can be taken into account in the LB. Those margins can be grouped into 3 major groups
which are:
• Gains and losses on the BTS side margins,

• Design margins,
• Environmental factors margins.
6.17.1 GAINS AND LOSSES

Gains and losses on the BTS side margins are composed of
DIVERSITY
It can be seen as a quality improvement. There are three kinds of diversity: space diversity
(mostly used), angle diversity, and polarization diversity.
The space diversity uses two antennas far apart enough. The two received signals suffer
uncorrelated degradation, allowing to extract a diversity gain from their simultaneous process.
This technique is used to decrease the Raleigh fading for slow moving mobiles, fast moving
mobiles being less disturbed by this fading. Therefore, this technique is mostly used in
suburban and urban areas. More generally, it is applicable in all contexts where the gain
brought by diversity can be useful to balance the link budget.
Nortel confidential

MAST HEAD EQUIPMENT
In order to reduce the feeder loss, the PA can be deported to the mast equipment.
For the reception part, LNAs are not deported anymore for cost-reduction reasons (they are
placed in the RF combiner for S8000 only). This is not a problem given the good sensitivity of
the BTS. If the LNA is external, there is an UL gain.
COMBINING STRATEGIES
A combiner allows several frequencies to be handled by the same antenna.

Those losses are taken into account in the BTS_sen, NORTEL giving its BTS sensitivity at the
antenna connector
6.17.2 DESIGNS MARGINS

Design margins are composed of
OVERLAPPING MARGIN
Designed to prevent the field of the current cell from dropping under a critical value before the
MS locks on the next cell. The value given for this margin depends mainly on two factors: the
speed of the mobile and the speed of decreasing signal experienced by the mobile.
PENETRATION FACTORS
They can be defined with average value based on measurements.
• Incar: designed to take into account a MS used in a car in standard conditions.

• Indoor: designed to take into account a MS used in a building, using an outdoor
network.
Note: in the calculation of the link budget, only consider the maximum of (overlapping margin
+ incar penetration factor) and (indoor penetration factor).
6.17.3 ENVIRONMENTAL FACTORS MARGINS

Those factors are due to the fact that a radio signal won’t propagate the same way in a rural
environment or in an urban one.
SHADOW MARGIN
Shadowing effects due to obstacles have been studied in many articles and its probability is
described as a Log-normal law. The mean square value depends on the environment (terrain
variation and vegetation) and frequency.
This margin allows the determination of an x% coverage over the cell surface (typically 90%)
by the integration of the Log-normal law over this surface.
Nortel confidential

For a cell without a surrounding cell, coverage is provided by one server only. Thus, there can
have many uncovered areas (behind buildings in an urban environment for example), requiring
a high shadow margin. In a multiple servers configuration, the probability of coverage is
increased, and a better coverage continuity is achieved at cell edges. The delay introduced in
the handover process reduces this gain.
ENVIRONMENT CORRECTION FACTOR
This factor exists because for the same output power, the signal will propagate much farther in
a rural environment than in an urban one, creating more interference.
This parameter is defined upon field measurements and a high level of experience is needed
to evaluate this value when no measurement is available. If it’s badly defined, it can have a
dramatic effect on the coverage range.
Note: it is always possible to add more margin to increase the quality of coverage but:
• it will increase the interference level

• a system limit exists on the quality of service (around 98%) due to high number of
handovers, neighboring cells to declare...
6.17.4 LINK BUDGET BALANCE OR DISBALANCE (∆)

∆ = DL_budget - UL_budget
The worst link budget between uplink and downlink will be taken as path loss in order to do the
cell planning.
• If ∆ = 0: the link budget is balanced, so either DL or UL_budget is good for path

loss
• If ∆ > 0: the link budget is uplink limited, take the UL_budget as path loss
• If ∆ < 0: the link budget is downlink limited, take the DL_budget as path loss
Example: a link budget calculation with Nortel values for the S8000 Outdoor BTS using
duplexor, in GSM1800:
Downlink Uplink
BTS_Pwr 43,3 dBm MS_Pwr 30 dBm
BTS BTS_Ant_Gain 17 dBi MS MS_Ant_Gain - 2 dBi
BTS_Feeder_Loss - 2 dB Body_Loss 3 dB
EIRP 58 dB EIRP 28 dB
MS_Sen - 102 dBm BTS_Sen - 110 dBm

MS MS_Ant_Gain -2 dBi BTS_Ant_Gain 17 dBi
BTS
Body_Loss 3 dB BTS_Div_Gain 5 dB
BTS_Feeder_Loss 2 dB
DL budget 155,3 UL budget 155
Nortel confidential

IMPORTANCE OF A GOOD LINK BUDGET
In the following table, it appears that a path loss increase of 1 dB can improve the coverage
range by 7% and reduces the number of sites by 12%, but 5 dB less in the path loss
corresponds to a coverage range cut by 28% and a number of sites increased by 90% (figures
are slightly higher for linear coverage, typically road coverage).
Worst Link Budget Coverage range Coverage area Number of sites

125 dBm 72 % 52 % 190 %
129 dBm 93 % 88 % 114 %
130 dBm 100 % 100 % 100 %
131 dBm 107 % 114 % 88 %
135 dBm 132 % 190 % 52 %
Nortel confidential

6.18. MINIMUM COUPLING LOSS (MCL)

The Minimum Coupling Loss is the minimal value recommended in the link budget to avoid
problems in the transmission.
The MCL is calculated to avoid the two major problems which may occur, broadband noise
and blocking. It is mainly used in a micro-cellular and pico-cellular environment where MSs are
likely to operate in the vicinity of the BTS antennas.
6.18.1 BROADBAND NOISE

The Broadband noise takes into account all kinds of noise which disturb the BTS and the MSs.
According to GSM Recommendation 05.05, the MS must keep its output noise level 60 dB
below its power level (for a frequency spacing of 600 kHz). On the BTS part, the received
noise level must be at least 9 dB below its sensitivity.
The decoupling value is the difference between the maximum output noise level and the
maximum received noise level.
Considering a S2000L BTS and a GSM 1800 MS, values are the following in both uplink and
downlink:
UPLINK DOWNLINK
Transmitter Max Power A (dBm) 30 33
Output Noise Level Margin B (dB) 60 60
Max Output Noise Level C (dBm) = A - B -30 -27
Receiver Sensitivity D (dBm) -104 -101
Input Noise Level Margin E (dB) 9 9
Max Input Noise Level F (dBm) -113 -110
Noise Decoupling Value G (dB) = C - F 83 83
As we can notice in the results of the upper table, the values are the same for uplink and
downlink.
6.18.2 BLOCKING
The Blocking takes into account the interferences generated by the others MSs.
The BTS can handle, for the 600 kHz adjacent frequency, a received signal strength 35 dB
below the maximum received power of the current frequency. Over this value, a phenomenon
of flashing occurs.
The flashing phenomenon consists in a BTS or a MS which would emit at a very high value,
and would by this way interfere the communication of the others MSs. The effect of this
phenomenon is the deterioration of the wanted signal.
The decoupling value is the difference between the maximum output power and the maximum
received signal level.
Considering an S2000L BTS and a GSM 1800 MS, values are the following in both uplink and
downlink:
Nortel confidential

UPLINK DOWNLINK
Transmitter Max Power A (dBm) 30 33
Max Received Signal Strength B (dB) -35 -44
Decoupling Value C (dB) = A - B 65 77
Moreover, in the blocking case, the probability of collision of the burst between MS and BTS
must be taken into account.
In the blocking case, the downlink is more affected than the uplink. However, this difference is
not very important (except if the study is done at the frequency of the interferer) since the
decoupling value for the Broadband noise is more restricting than the decoupling values for
blocking.
6.18.3 HOW TO IMPROVE THE MCL

If the MCL is not respected, the communications will be deteriorated and will have a poor
quality. To improve that quality (or decrease the probability of such problems to occur), its to
say respect the MCL, solutions consist in increasing the frequency spacing between the cell
and the neighboring cells and/or ensure a better decoupling between BTS antenna and MS.
Nortel confidential

6.19. GENERAL RULES FOR SYNTHESISED FREQUENCY

HOPPING
6.19.1 NORTEL CHOICE BETWEEN BASEBAND AND SYNTHESISED

FREQUENCY HOPPING
In case of cavity (or filter) coupling system, the only way to perform frequency hopping is to
use baseband frequency hopping. The wideband coupling system (duplexer or hybrid-2ways
and duplexer) allows the use of both types of frequency hopping; however, it is more
appropriate with synthesised frequency hopping.
Here below are listed the main comparison points between baseband and synthesised
frequency hopping. It allows to decide the most appropriate frequency hopping mechanism.
USE OF DOWNLINK DTX AND DOWNLINK POWER CONTROL
Tests have shown that if DTX downlink and Power Control downlink are activated
simultaneously when using baseband frequency hopping, it could lead to quality degradation
and eventually to call drops for some mobile brands.
With synthesised frequency hopping, this behaviour has never been encountered whatever
the mobile brand is. So with simultaneous activation of these two features, interference are
significantly reduced.
Beside, PowerControl DownLink associated with Baseband frequency hopping may lead to
interference, because the BCCH frequency included in the hopping sequence does not
perform power control.
PARAMETER SETTINGS
The parameter setting for the synthesised frequency hopping with a fractional re-use pattern is
easily performed due to the fact that the set of frequencies is the same for each cell (1*1
pattern) or a group of cells (for example 1*3 pattern). Implementation of new sites implies a
new frequency planning for the BCCH layer, but is not needed for the TCH layer.
On the contrary, two different MA per cell are needed when using baseband frequency
hopping:
• one for the TS0 of all the TRXs except the one carrying the BCCH, without the
BCCH frequency
• one for the TS1 to TS7 for all the TRXs, including the BCCH frequency
TS 0 TS 1 TS 2 TS 3 TS 4 TS 5 TS 6 TS 7
TDMA 0 F1 MA1 MA1 MA1 MA1 MA1 MA1 MA1 MAIO = 0
TDMA 1 MA0 MA1 MA1 MA1 MA1 MA1 MA1 MA1 MAIO = 1
Nortel confidential

CAPACITY AND QUALITY IMPACT IN CASE OF TRX LOSS
In case of baseband frequency hopping, the number of used frequencies is equal to the
number of TRX. As a result, in case of TRX loss, the capacity of the site will be reduced, and
the number of frequencies in the hopping sequence is also reduced by one. Therefore, the
overall benefit of the frequency hopping (i.e. voice quality) is reduced.
In case of synthesised frequency hopping, the capacity of the site is also reduced, but the
overall load of the fractional pattern is reduced (the number of frequency in the hopping
sequence is still the same, but the number of in-service TRX is reduced by one) ; the
frequency hopping gain will be maintained.
MTBF IMPACT OF THE COUPLING SYSTEM
Cavity combiners, which are mechanical equipment, have smaller MTBF than hybrid coupler
combiners which are passive equipment. Therefore, the synthesised solution with wideband
coupling system shall be more reliable than the baseband solution with cavity coupling
system.
COUPLING LOSS IMPACT
On one hand, cavity coupling systems have an insertion loss around 4,5 dB ; on the other
hand, duplexer and hybrid 2-ways coupling systems have a respective insertion loss of 1,3 dB
and 4,8 dB. Therefore, when using duplexers, a lower loss in the downlink budget allows to
have a lower downlink budget (3.2 dB) to balance the path loss. Otherwise, the use of hybrid
2-ways coupling systems does not badly impact the link budget, in comparison with cavity
coupling systems.
FREQUENCY HOPPING EFFICIENCY
For limited frequency spectrum networks, the maximum configuration of BTS is limited to few
TRX in case of baseband frequency hopping. This means that every timeslot is hopping on a
few frequencies (often less than 4).
When using synthesised frequency hopping, every timeslot (except those of the BCCH TRX)
is hopping on more frequencies (not limited by the number of TRX).
FADING DIVERSITY
From Nortel experience, to get the full benefit of frequency hopping, a minimum of six (6)
different frequencies shall be used in each cell. This benefit is increased up to 8 frequencies
available within the hopping sequence concerning fading effects.
INTERFERER DIVERSITY
Beyond 8 frequencies, the additional interferer benefits are still increasing.
Nortel confidential

TRX ADDITION IN A GIVEN CELL
In case of synthesised frequency hopping, it is not always mandatory to stop a sector when
adding a TRX in this sector (it only requires that this additional TRX was previously declared
within the OMC database).
On the contrary, in case of baseband frequency hopping, this is not possible due to the fact
that every time a TRX is added, the quantities of frequencies used in the cell have to be
increased.
Then it is easier to add a TRX in a cell using Synthesised Frequency Hopping as long as the
fractional load is under the upper limit.
6.19.2 FRACTIONAL LOAD

The fractional reuse pattern which can be implemented on a network depends on the
fractional load.
NbHopTRXCell
FractLoadCell =
Nhfcell
• NbHopTRXCell: number of hopping TRX in a cell

• Nhfcell: number of hopping frequencies in a cell (= number of freq in the MA)
It is obvious that the defined fractional load is not comparable in a 1X1 pattern and a 1X3
pattern. In both cases there are three times more TRX in a trisectorial site than in each of its
cell. However, though there are also three times more TCH frequencies in a trisectorial site
than in each if its cell for a 1X3 pattern, there is the same number of hopping frequencies in a
trisectorial site than in each of if its cell for a 1X1 pattern. For that matter, we also need to
define a fractional load at the site level that allows us to compare both reuse patterns. We
need to mention that when dealing with non homogeneous sites of configuration Sxyz (with
x<y<z) this fractional load per site is important.
Note: By homogeneous sites (Sxxx) we mean cells that have the same number of TRXs and
hopping TRXs.
NbHopTRXSite
FractLoadSite =
Nhfsite
• NbHopTRXSite: number of hopping TRX in a cell

• Nhfsite: number of hopping frequencies in a site
The table below shows the fractional re-use pattern that can be implemented according to the
maximum fractional load. The results in this table come from simulations and field experience.
Then they have to be understood as maximum values for a “good RF quality” in the network.
They are available only in case of using power control and DTX, both uplink and downlink.
Otherwise, the maximum fractional load would be smaller.
Nortel confidential

Cell tiering allows to raise the fractional load limit because of its gains in quality. Simulations
have proved that the fractional load can go up to 33% in 1*1 and 100% in 1*3. In those cases,
all the frequencies are used at the same time which also means that all the MAIOs are used at
the same time.
Fractional re-use pattern Fractional Load max

FractLoadCell max Frational Load max
Hommogenous with Automatic
without intraSite collisions with intraSite collisions
configuration (Sxxx) Cell Tiering
1X1 16,6 % 20 % 33 %
1X3 50 % 58 % 100 %
LCAUTION!
20% and 58% can be reached with an appropriate tuning of the parameters and in this case
offer a very good quality for the given capacity (field experience).
The maximum fractional load is the basis of the following study for engineering rules
concerning HSN and MAIO. Indeed, as the fractional load is a limitation, the aim of HSN and
MAIO plans is to be as close as possible to this limitation, and to have as less interference as
possible (no adjacent frequency).
6.19.3 MAXIMUM TRX CONFIGURATION (HOMOGENEOUS SITES OF

CONFIGURATION SXXX)
We suppose here that the frequency reuse pattern for the BCCH is 4*12.
With the previous results, it is possible to determine the maximum site configuration according
to the number of frequencies and the re-use pattern (1*1, 1*3 or 4*12), and taking into
account the results of maximum fractional load.
The following tables show the maximum site configuration according to the number of
frequencies and the re-use pattern (considering a 4X12 re-use pattern for the BCCH), and
taking into account the results of maximum frequency load.
number of frequencies 96 84 72 60 48 45 47
1X3 fractional re-use pattern S888 S777
1X1 fractional re-use pattern S888
4X12 re-use pattern S888 S777 S666 S555 S444
number of frequencies 42 39 37 36 33 32 30
1X3 fractional re-use pattern S666 S555 S444
4X12 re-use pattern S333
number of frequencies 27 24 22 18 17 12
1X1 fractional re-use pattern S444 S333 S222 S111
4X12 re-use pattern S222 S111
Nortel confidential

6.19.4 SFH PARAMETER SETTING FOR 1X1 PATTERN: STRATEGY 1

This strategy means the use of the same frequency group of TCH (Mobile Allocation) for all
cells in the network.
The values of maximum fractional load in a cell show that for a given fractional band, this
strategy (1X1 pattern) leads to a capacity increase (more TRX per cell).
However, this maximum fractional load must be obtained without an increase of interference.
Then, the aim of the following study is to show what are the best HSN and MAIO plans to
reach the maximum frequency load without increasing the interference.
HSN AND MAIO GENERAL RULES
• In case of 1X1 fractional re-use pattern it is obviously forbidden to re-use the same
value of HSN and MAIO on two different cells of a same site. As they are
synchronised, it would systematically lead to frequency collision.
• For a 1X1 re-use pattern, it is forbidden to use different HSN in cells of a same site.
It would lead to a frequency collision ratio of 1 / n for all the TSs of the
communication.
• Moreover, if some frequencies inside the group are adjacent (general case), the
use of two adjacent MAIO in a same site is also extremely inadvisable because it
would lead to interference (minimum frequency spacing of 400 kHz).
• Spread the MAIOs as much as possible
• Distribute equally the MAIOs in order to have the same distance (e.g. 600 kHz)
between used frequencies.
STRATEGY 1A: ADJACENT FREQUENCIES
Frequency band for hopping TRX: F1, F1+200, F1+400, F1+600,...
CASE 1: NO INTRA-SITE COLLISION
RULE:
same HSN for all cells within the same site

MAIO given according to a step 2 rule and by considering all the TRXs by order (TRX1
of cell 1, TRX1 of cell 2, TRX1 of cell 3, TRX2 of cell 1, TRX2 of cell 2, ...).
The maximum number of used MAIOs in the site (which correspond to the maximum number
of hopping TRXs in the site) is given by the following rule:
NbMaxOfusedMAIOsite = ROUNDDOWN(Nhfcell/2)
with ROUNDDOWN[x] the function that returns the round part of x down-wise (for instance
ROUNDDOWN(7.9) = 7)
Note: this rule can obviously not be exactly applied in the case of non-homogeneous sites.
Refer to the following examples.
Nortel confidential

Let us consider a tri-sectorial site. As defined previously we have for each cell with 1 < i < 3
FractLoadCelli = NbHopTRXCell i / Nhfcelli
Since we are in 1X1, we have Nhfcell1 = Nhfcell2 = Nhfcell3 = Nhfsite

In order to avoid intra-site channel collision, we use a step 2 MAIO which enables us to put a
400kHz distance between the frequencies at each moment. To have hopping TRXs in 3 cells
according to step 2 MAIO is like putting all the hopping TRXs in one cell with still the step 2
MAIO and none in the 2 other cells. In this case, we will be using every other frequency which
means that the fractional load of the site must be below 50%.
In this case the rule is FractLoadSite ≤ 50%

Since FractLoadSite = NbHopTRXSite / Nhfsite = (NbHopTRXcell1 + NbHopTRXcell2+
NbHopTRXcell3) / Nhfsite = FractLoadCell1 + FractLoadCell2 + FractLoadCell3, we can
deduce that the condition for no intra-site collision is then (Sxxx or Sxyz):
FractLoadCell1 + FractLoadCell2 + FractLoadCell3 ≤ 50%
In the particular case of a homogeneous site (Sxxx) and since NbHopTRXCell1 =

NbHopTRXCell2 = NbHopTRXCell3 and thus FractLoadCell1 = FractLoadCell2 =
FractLoadCell3, this condition becomes:
FractLoadCell ≤ 16.6%
These results can be summarized in the following table:
Homogeneous: Sxxx Non homogeneous: Sxyz

NO intraSite FractLoadSite ≤ 50% FractLoadSite ≤ 50%
collision FractLoadCell ≤ 16.6% SUM(FractLoadCelli) ≤ 50%
LCAUTION!
The MAIO tuning depends on the case.
Nortel confidential

Example:
Let us call the frequencies according to the following rule: f1=F1, f2=F1+200, f3=F1+400,
f4=F1+600, ...
Homogeneous site: S333

Let us consider 12 hopping frequencies {f1,f2,f3,f4,f5,f6,f7,f8,f9,f10,f11,f12}. Then,
NbMaxOfusedMAIO = 6 which means that of the 12 available MAIOs we can attribute 6 of
them at the most in order to respect the non intra-site collision. Since the site is homogeneous
we can use 2 hopping TRXs per cell at the most. Then, FractLoadCell is 2/12=16.6%.
MAIO 0 1 2 3 4 5 6 7 8 9 10 11
cell 1 f1 f2 f3 f4 f5 f6 f7 f8 f9 f10 f11 f12
As we can see, at each moment (using NORTEL’s BTS which are synchronized), the
frequencies used by all TRXs will be spaced by at least 400kHz. This is guaranteed by the
step 2 MAIO and the choice of frequencies spaced by 200 kHz.
HSN = 1
MAIO 0,6
HSN = 1 HSN = 1
MAIO 4,10 MAIO 2,8
Non homogeneous site:

S432
MAIO 0 1 2 3 4 5 6 7 8 9 10 11
FractLoadCell1=3/12=25% and FractLoadCell2=2/12=16.6% & FractLoadCell3=1/12=8.3%
FractLoadSite = (3+2+1)/12 = 50%. We can see here that the rule of MAIO setting has been
adapted because of the non homogeneity of the site: the TRXs were not completely
considered by order.
Nortel confidential

If we want to add a TRX on the third sector for instance, the site becoming now S433, we
need to add 2 more frequencies in order to respect the non intra-site collision and the
fractional load limitations:
MAIO 0 1 2 3 4 5 6 7 8 9 10 11 12 13
cell 1 f1 f2 f3 f4 f5 f6 f7 f8 f9 f10 f11 f12 f13 f14
FractLoadCell1 = 3/14 = 21.4% and FractLoadCell2 = FractLoadCell3 = 2/14 = 14.3%

FractLoadSite = (3+2+2)/14 = 50%
CASE 2: INTRA-SITE COLLISION ALLOWED
RULE:

MAIO given according to a step 2 rule as long as possible and by considering all the
TRXs by order (TRX1 of cell 1, TRX1 of cell 2, TRX1 of cell 3, TRX2 of cell 1, TRX2 of
cell 2, ...). When it is not possible anymore, down to step 1 MAIO.
The step 1 MAIO will create the adjacent intra-site interferences as frequencies spaced by
only 200 kHz (step 1 MAIO) will be used at the same time in the site. It is up to us to decide
where to create the interferences by choosing where to put the step 1 MAIOs. The
recommendations are to put them in the cell which has the smallest overlap with its neighbors.
If the overlap is similar in all cells of the same site then choose the cell with the smallest traffic
as this will have less impact. Field experience with homogeneous sites has shown that with a
proper tuning of the parameters it was possible to go up to FractLoadCell=20% while keeping
a very good quality in the cell for the capacity offered. Then, we can say that in general
FractLoadSite must be ≤ 60% in order keep a very good quality with intra-site collision. In
other words:

IntraSite 50% ≤ FractLoadSite ≤ 60% 50% ≤ FractLoadSite ≤ 60%
collision 16.6% ≤ FractLoadCell ≤ 20% 50% ≤ SUM(FractLoadCelli) ≤ 60%
Example:
Let us consider a S333 with 10 hopping frequencies {f1,f2,f3,f4,f5,f6,f7,f8,f9,f10}. With 2
hopping TRXs per cell FractLoadCell is 2/10=20%. Let us assume that at one moment the
HSN starts by f3, the frequencies that will be used at each moment are:
MAIO 0 1 2 3 4 5 6 7 8 9
cell 1 f3 f4 f5 f6 f7 f8 f9 f10 f1 f2
cell 2 f3 f4 f5 f6 f7 f8 f9 f10 f1 f2
cell 3 f3 f4 f5 f6 f7 f8 f9 f10 f1 f2
Nortel confidential

We can see here that we attribute the MAIO according to the step 2 rule as long as we can in
order to avoid the intra-site collision (up to MAIO 8 here) and then we have to use the step 1
rule (MAIO 9). In this particular case, we have decided to create most of the collisions on
sector 3 as the interferences are created by the simultaneous use of f1, f2 and f3.
In order to add a TRX in cell 1 for instance, the site becoming now non homogeneous (S433),
we need to add 2 frequencies in order to respect the fractional load limitations:
MAIO 0 1 2 3 4 5 6 7 8 9
FractLoadCell1 = 3/12 = 25% and FractLoadCell2 = FractLoadCell3 = 2/12 = 16.6%

FractLoadSite = (3+2+2)/12 = 58.3%
Note: it is important to keep a certain coherence between the fractional loads of each cell
within a site. Indeed, if the fractional load of one cell is very high compared to the one of the
other cells, it could lead to much more intercell interferences and this should be avoided.
STRATEGY 1B: NO ADJACENT FREQUENCY
Frequency band for hopping TRX: F1, F1+400, F1+800, F1+1200, ...
Frequency band for no hopping TRX: F1+200, F1+600, F1+1000, ... for instance
This strategy leads to permanent collisions between the BCCH and the TCH time slots.
Moreover, this strategy is not applicable at all when using PowerControl on the TCH time
slots.
This strategy is not recommended at all.
Nortel confidential

6.19.5 SFH PARAMETER SETTING FOR 1X3 PATTERN: STRATEGY 2

This strategy is studied here below in the case of a trisectorial site with an homogeneous
repartition of TRX in the cells. This strategy also means the use of the same frequency group
(T1) for all sectors 1 (cell 1) in the network, another group (T2) for sectors 2 (cell 2) and a third
(T3) for sectors 3 (cell 3). Those 3 groups are completely disjoint and have the same number
of frequencies. If this is not respected, it is not 1X3, rather an hybrid version of 1X3 and the
following do not apply anymore.
HSN AND MAIO GENERAL RULES
• If both HSN and MAIO are the same for each cell of a same site, there will be
systematical frequency adjacencies. Then, this configuration is not recommended.
• In order to systematically ensure a non-adjacency, the only way is to use a unique
HSN but different MAIO for consecutive cells within a site.
• The MAIO can be adjacent within a cell, because two (2) consecutive frequencies
in a cell are not adjacent (non-continuous frequency bands).
• The use of different HSN and MAIO in each cell of a site is not recommended
because it would lead to frequency adjacencies, then to an increase of
interference.
• Spread the MAIOs as much as possible
• Distribute equally the MAIOs in order to have the same distance (e.g. 600 kHz)
between used frequencies.
STRATEGY 2A: 3 NON-CONTINUOUS FREQUENCY BANDS
group T1 (for cell 1): F1, F1+600, F1+1200,...

group T1 (for cell 2): F1+200, F1+800, F1+1400,...
group T1 (for cell 3): F1+400, F1+1000, F1+1600,...
CASE 1: NO INTRA-SITE COLLISION
RULE:
MAIO given according to a step 2 rule within a cell knowing that , the setting for cell 2
will be the one for cell 1up-shifted by 1 step and the one for cell 3 will be the same one
than for cell 1.
Note: This rule can obviously not exactly be applied in the case of non-homogeneous sites.
Refer to the following examples.
Let us consider a tri-sectorial site. As defined previously we have for each cell with 1 < i < 3
FractLoadCelli = NbHopTRXCell i / Nhfcelli
Nortel confidential

Since we are in 1X3 (not hybrid), the spectrum of the site is 3 times bigger than the spectrum
of each cell and thus Nhfsite=Nhfcell1+Nhfcell2+Nhfcell3 = 3*Nhfcelli. Thus FractLoadCelli =
3*(NbHopTRXCell i / Nhfsite)
The previous rule can be seen differently: indeed the frequencies used at a given moment are:
MAIO 0 1 2 3 4
cell 1 f1 f4 f7 f10 ...
cell 2 f2 f5 f8 f11 ...
cell 3 f3 f6 f9 f12 ...
If we look at it by a site point of view, we can consider the site as one big cell with one
spectrum (equal to the 3 groups: {T1, T2, T3}). Then it becomes:
Site f1 f2 f3 f4 f5 f6 f7 f8 f9 f10 f11 f12
In this case, we are brought back to 1X1 (refer to the strategy 1A). Since the frequencies are
spaced by 200 kHz, we can avoid intra-site channel collision by using a step 2 MAIO which
enables us to put a 400kHz distance between the frequencies at each moment. In this case,
we will be using every other frequency which means that the fractional load of the site must be
below 50%.
In this case the rule is FractLoadSite ≤ 50%

Since FractLoadSite = NbHopTRXSite / Nhfsite = 3 * [(NbHopTRXcell1 + NbHopTRXcell2 +
NbHopTRXcell3)] / Nhfsite = 3 * (FractLoadCell1 + FractLoadCell2 + FractLoadCell3), we can
deduce that the condition for no intra-site collision is then (Sxxx or Sxyz):
3*(FractLoadCell1+FractLoadCell2+FractLoadCell3) ≤ 50%
In the particular case of a homogeneous site (Sxxx) and since NbHopTRXCell1 =

NbHopTRXCell2 = NbHopTRXCell3 and thus FractLoadCell1 = FractLoadCell2 =
FractLoadCell3, this condition becomes:
FractLoadCell ≤ 50%
Then we can deduce the following rule on the maximum number of possible used MAIOs in a
site at a given moment. This number will correspond to the maximum number of hopping
TRXs in the site. It is given by the following rule following the previous limitation FractLoadCell
≤ 50%:
NbMaxOfusedMAIOsite=ROUNDDOWN(Nhfsite/2)=ROUNDDOWN((3*Nhfell)/2)
With ROUNDDOWN[x] the function that returns the round part of x down-wise (for instance
ROUNDDOWN(7.9) = 7).
Nortel confidential

These results can be summarized in the following table:

NO IntraSite FractLoadSite ≤ 50% FractLoadSite ≤ 60%
collision FractLoadCell ≤ 50% SUM(FractLoadCelli) ≤ 150%
Example:
Let us call the frequencies according to the following rule: f1=F1 , f2=F1+200 , f3=F1+400 ,
f4=F1+600, ...
Let us consider 3 groups of hopping frequencies: T1={f1, f4, f7, f10, f13, f16}; T2={f2, f5, f8,
f11, f14, f17} & T3={f3, f6, f9, f12, f15, f18}.
Homogeneous site:
Then, NbMaxOfusedMAIOsite=9 which means that we can attribute 3 TRXs per cell at the
most in order to respect the non intra-site collision. FractLoadCell is 3/6=50% and we have a
S444.
MAIO 0 1 2 3 4 5
cell 1 f1 f4 f7 f10 f13 f16
cell 2 f2 f5 f8 f11 f14 f17
cell 3 f3 f6 f9 f12 f15 f18
As we can see, at each moment (using NORTEL’s BTS which are synchronized), the
frequencies used by all TRXs will be spaced by at least 400kHz. This is guaranteed by the
step 2 MAIO and the choice of frequencies spaced by 200 kHz.
HSN = 1
MAIO 0,2,4
HSN = 1 HSN = 1
MAIO 0,2,4 MAIO 1,3,5
Nortel confidential

Non homogeneous site:

We have NbMaxOfusedMAIOsite=ROUNDDOWN(Nhfsite/2)=10: 10 TRXs at the most that we
can distribute between the 3 cells. The MAIO setting rule needs to be adapted according to
the wanted configuration:
S454
MAIO 0 1 2 3 4 5 6
cell 1 f1 f4 f7 f10 f13 f16 f19
cell 2 f2 f5 f8 f11 f14 f17 f20
cell 3 f3 f6 f9 f12 f15 f18 f21
FractLoadCell1=FractLoadCell3=42.8% & FractLoadCell2=57.1%

FractLoadSite=47.6%
S544
MAIO 0 1 2 3 4 5 6
cell 1 f1 f4 f7 f10 f13 f16 f19
cell 2 f2 f5 f8 f11 f14 f17 f20
cell 3 f3 f6 f9 f12 f15 f18 f21
FractLoadCell1=57.1% & FractLoadCell2=FractLoadCell3=42.8%
FractLoadSite=47.6%
Nortel confidential

CASE 2: INTRA-SITE COLLISION ALLOWED
RULE:
MAIO given according to a step 2 rule within a cell knowing that, the setting for cell 2
will be the one for cell 1 up-shifted by 1 step and the one for cell 3 will be the same
one than for cell 1. When it is not possible anymore to do a step 2, down to step 1
MAIO within the cell.
The step 1 MAIO will create the adjacent intra-site interferences between the 3 cells as the
frequencies are spaced by only 200 kHz between cells (step 1 MAIO. It is up to us to decide
where to create the interferences by choosing where to put the step 1 MAIOs. The
recommendations are to put them in the cell which has the smallest overlap with its neighbors.
If the overlap is similar in all cells of the same site then choose the cell with the smallest traffic
as this will have less impact. Field experience with homogeneous sites has shown that with a
proper tuning of the parameters it was possible to go up to FractLoadCell=58% while keeping
a very good quality in the cell for the capacity offered. Then, we can say that in general
FractLoadSite must be ≤ 58% in order keep a very good quality with intra-site collision. In
other words:

NO IntraSite 50% ≤ FractLoadSite ≤ 58% 50% ≤ FractLoadSite ≤ 58%
collision 50% ≤ FractLoadCell ≤ 58% 150% ≤ SUM(FractLoadCelli) ≤ 174%
Example:
Let us call the frequencies according to the following rule: f1=F1, f2=F1+200, f3=F1+400,
f4=F1+600, ...
Let us consider 3 groups of hopping frequencies: T1={f1, f4, f7, f10, f13, f16, f19}; T2={f2, f5,
f8, f11, f14, f17, f20} & T3={f3, f6, f9, f12, f15, f18, f21}.
FractLoadCell is 4/7=57.1% and we have a S555.
MAIO 0 1 2 3 4 5 6
cell 1 f1 f4 f7 f10 f13 f16 f19
cell 2 f2 f5 f8 f11 f14 f17 f20
cell 3 f3 f6 f9 f12 f15 f18 f21
In order to see better the interferences, let us assume that at one moment the HSN starts by
the third frequency of each group (same HSN), the frequencies that will be used at each
moment are:
MAIO 0 1 2 3 4 5 6
cell 1 f7 f10 f13 f16 f19 f1 f4
cell 2 f8 f11 f14 f17 f20 f2 f5
cell 3 f9 f12 f15 f18 f21 f3 f6
Nortel confidential

In this particular case, the interferences are equally created between the cells. Indeed, the
simultaneous use of f13, f14 and f15 creates collisions between (cell1, cell2) and (cell2, cell3).
We also have the simultaneous use of f6 & f7 f15 creating collisions between (cell1, cell3).
For a non homogeneous S544 for instance:
MAIO 0 1 2 3 4 5
cell 1 f1 f4 f7 f10 f13 f16
cell 2 f2 f5 f8 f11 f14 f17
cell 3 f3 f6 f9 f12 f15 f18
FractLoadCell1=57.1% and FractLoadCell2=FractLoadCell3=42.8%

FractLoadSite=10/18=55.5%
The interferences are localized mostly in cell 1.
Note: it is important to keep a certain coherence between the fractional loads of each cell
within a site. Indeed, if the fractional load of one cell is very high compared to the one of the
other cells, it could lead to much more intercell interferences and this should be avoided.
Nortel confidential

6.20. DUALBAND NETWORKS

This chapter does not consider the new dualband cell feature (introduced in V12). For this new
feature, nevertheless, each of these new cells can be considered as monoband at a selection /
reselection point of view, the monoband type being defined by the BCCH frequency.
Some information must be taken into account to define coverage and parameter setting for
Dual Band networks. To optimize network capacity, it is necessary to evaluate balance load
between the two bands and to avoid expensive procedures like LAC optimization (leads to
frequent location updates) or network topology (for interBSS handovers). Furthermore, the
percentage of dualband handsets and the percentage of coverage of each band are also
important to know.
Two different strategies can be used: adjacent coverage (one layer) or super-imposed
coverage (at least, two layers). Parameter setting for a multi-layer network will be similar to
microcell case. In both cases, inter-sites distance is also a key parameter to design the
network.
6.20.1 FREQUENCY BAND FAVOURING
SELECTION
To give a lower priority to band 1 cells, it is only necessary to set the parameter cellBarQualify
to “true” for these cells, and to “false” for band 2 (with cellBarred set to “not barred” in both
cases). A multiband MS (phase 2 MS) will choose a band 1 cell only if no band 2 cells are
found with a positive C1.

barred true low
not barred true low
RESELECTION
Multiband mobile stations are phase 2 mobile stations. Cell reselection will involve C2
computation (if cellReselInd= true). Here is the used formula:
C2 = C1 + cellReselectOffset - temporaryOffset *H(x)

where: x=penaltyTime - t
when: penaltyTime <> 640
C2 = C1 - cellReselectOffset
when: penaltyTime = 640
Nortel confidential

Furthermore, as C1 is the criterion used to choose one cell, one band is favoured when using
advised parameter setting. Here is the formula used to compute C1:
C1 = RXLEV - rxLevAccessMin - Max (B,0)
• B = msTxPwrMaxCCH - P
• P = maximum RF output power of the MS
In both bands, usually Max(B,0) will be equal to 0. As the recommended value for
rxLevAccessMin is “-101 to -100 dBm” for GSM 900 and “-99 to -98 dBm” for GSM 1800. It
means that for an identical value of RxLev, GSM 900 selection is favoured (2dB) if
recommended values are used for both types of cells.
However, cell reselect offset can be used in the computing of C2 criteria to advantage one
frequency band. Two different cellReselectOffset values can be used according to the cell
frequency band. With penaltyTime <> 640, the higher the cellReselectOffset value, the higher
the value of C2. Other parameters can be set as follow if no special care needs to be taken for
fast mobile stations: penaltyTime <> 640, temporaryOffset = 0.
Then, cellReselectOffset can be set to 30 in the favoured frequency band between 4 and 10 in
the other-one (some tests using 20 and 0 respectively provided good results). The 2 dB
difference for the C1 criteria between GSM900 and GSM1800 can be ignored in this case
because the recommended parameter setting for cellReselectOffset leads to a difference of
more than 20 dB for the C2 criteria.
Another way of favouring one frequency band is to only declare reselection neighbours
belonging to the priority frequency band.
DIRECTED RETRY
For distant mode, the eligible cell list is obtained from a level criteria directedRetry in the
adjacentCellHO object. A way to have an underprivileged frequency band is to choose two
sets of value for directedRetry, one for each band and to take the higher value for neighbour
cells belonging to the low priority frequency band. However, it will impact the directed retry for
monoband MS on this band (less directed retry).
HANDOVERS
If an offset was used to select (rather re-select) the cell, one must be aware that the cell may
not be the best one. To avoid going back to another band because it is the best cell, this offset
must be taken into account as well during handovers (hoMargin). Another way is also to inhibit
power budget handovers from the priority band towards the non-priority one.
To penalize handovers towards band 1 cells, it is only necessary to modify the different
hoMargin for band 1 neighbouring cells, here-in called hoMargin_nei_cell_band1.
hoMargin_nei_cell_band1 > hoMargin_nei_cell_band2.
Nortel confidential

During interband handovers, care must be taken when GSM900 sites and GSM1800 sites are
on different BSCs. This will awfully increase signaling because of interBSS procedures. To
avoid this case, interband HO on alarms must also be limited (by modifying thresholds).
Interband handovers can also be reduced by limiting the number of outband neighbours for
each cell. This will depend on operator priorities.
In V12, the feature HO decision according to priority and load allows to favour one band (or
just a group of cells) through the parameter offsetPriority, 1 being the highest priority.
MICROCELL ALGORITHM
Microcell capture A algorithm can also be used to make mobile stations “stay” in the same
frequency band.
SUM-UP OF THE RECOMMENDED PARAMETER SETTING TO FAVOUR

ONE FREQUENCY BAND
High Priority band Low priority band Note

Multiband reporting 3 2
cellBarQualify false true
cellReselectOffset 30 between 4 and 10
hoMarginRxQual, hoMargin_nei_cell_band1
hoMargin_nei_cell_band1 for hoMargin_nei_cell_band2 for
hoMarginRxLev... >
adjacentCellHO object adjacentCellHO object
hoMargin_nei_cell_band2
directedRetryAlgo rxLevMinCell + 3 dB rxLevMinCell + 3 dB
offsetPriority 1 2 to 5
6.20.2 FREQUENCY BAND DEFAVOURING
SELECTION
To give the same priority to both band cells, it is only necessary to set the parameters
cellBarQualify to “false” and cellBarred to “not barred” for all cells.
However, as GSM900 selection is favoured of 2 dB with the recommended values for
rxLevAccessMin for both bands, a balance can be found in setting rxLevAccessMin to “-100 to
-99 dBm” for all cells.
RESELECTION
No change may be done to the recommended parameter setting, then all cells may have the
same values for the parameters cellReselectOffset, temporaryOffset and penaltyTime.
As in cell selection, the parameter rxLevAccessMin may be set to “-100 to -99 dBm” for all
cells.
Nortel confidential

OTHER FEATURES
For all other features (Directed Retry or handover), the same parameter setting may be kept
for both band cells.
The remark about interband handovers (see above) is particularly crucial to take into account
in the case of no band is favoured. Indeed, a interband handover must be reduced to the
minimum (by modifying thresholds) and a particular neighbour plan may be elaborated in order
to avoid frequent interBSC handovers when GSM900 sites and GSM1800 sites are not on the
same BSC.
In V12, the feature HO decision according to priority and load allows not to favour one by
setting the parameter offsetPriority to the default value for all cells.
SUM-UP OF THE RECOMMENDED PARAMETER SETTING FOR TWO

EQUAL FREQUENCY BANDS
GSM 900 band GSM 1800 band Note

Multiband reporting the six strongest cells the six strongest cells
cellBarQualify false false
cellReselectOffset between 4 and 10 between 4 and 10
rxLevAccessMin - 100 to - 99 dBm - 100 to - 99 dBm
hoMarginRxQual, Value 900
Value 900 for Value 1800 for
hoMarginRxLev... =
adjacentCellHO object adjacentCellHO object
Value 1800
directedRetry 900
directedRetryAlgo directedRetry 900 directedRetry 1800 =
directedRetry 1800
offsetPriority 1 1
6.20.3 POSSIBLE DUALBAND NETWORK

Here is a list of the possible dualband networks:
• gsm900 - dcs1800,
• gsm850 - pcs1900,
• E-gsm - dcs1800,
• gsm900 - pcs1900, (warning : mono-BCCH dualband cells 900-are not supported)
• gsm850 - dcs1800, (warning : mono-BCCH dualband cells 850-1800 are not
supported)
Nortel confidential

6.21. MICROCELL BENEFITS

Microcell is a spectral efficiency feature. This algorithm enables us to shift traffic irrespective of
the traffic condition based on downlink signal strength and mobile speed. This gives flexibility
in filling the micro layer first before loading the macro/umbrella layer.
Different gain can be obtained depending on microcell deployment strategy, e.g. capacity gain,
indoor coverage gain, voice quality improvement… Several microcell strategies should be
considered:
6.21.1 FREQUENCY SUPER REUSE

In a good isolated micro layer network, a separated frequency plan can be allocated for
microcells with a few frequencies for BCCH and high fractional reuse pattern increasing
spectral efficiency increasing capacity keeping same QoS.
6.21.2 TRAFFIC HOMOGENIZATION

One of the most critical frequency plan challenge is high configuration sites. Indeed they are
difficult to control since they create interferences with no way to minimize the collisions.
Declaring cells as microcell allows shifting traffic and homogenizes site configurations having
a cleaner frequency plan.
Benefits of this feature could be realized by rearranging the DRX counts and carrying more
traffic in the micro layer traffic channels and simultaneously carrying lesser traffic and DRXs in
the umbrella layer thus giving room to reduce spectrum from the Macro layer which is more
interfered. This allows a cleaner and more manageable frequency plan avoiding high
configurations
6.21.3 RADIO CONDITIONS IMPROVEMENT

Cells with low antenna height are normally better isolated by environment protection. If these
cells are declared as micro, shifted traffic generates less interference creating a cleaner
frequency plan. Less interferences are traduced in a better voice quality or feasibility to
increase fractional reuse pattern keeping same voice quality.
On one hand microcell deployment is a good strategy to improve radio conditions., thus the
operator can whether increase fractional reuse and therefore increase network capacity or
increase voice quality, keeping same fractional reuse pattern.
On the other hand, microcell deployment is a good strategy to improve indoor coverage in a
specific area, such as business or travelling hot spots.
Nortel confidential

6.21.4 MICROCELL FIELD EXPERIENCE
MICROCELL IMPACT ON AMR HR PENETRATION
Microcell deployment reduces AMR HR penetration. Indeed, in microcell PBGT HO are

disabled, and yet when PBGT HO are activated we assume to be on the best serving cell, so
in the best C/I conditions. This effect has an impact on AMR HR penetration as good C/I
conditions are required for Half Rate, which slightly reduces its penetration.
LRXLEVDLH AND LRXLEVULH DEFINITION
When a micro to umbrella relationship is declared between two different cells, it is important to
have a close look on Call Trace / Call Path Trace in order to determine lRxlevDLH and
lRxlevULH. Depending on micro and macro cell layer design, it has been found some cases
where a call, which is allocated in the micro cell and getting close to the micro cell limits,
receives an RxLev signal from the macro cell which is even lower than micro cell RxLev
signal. Since Power Budget is deactivated when micro-umbrella relationship is declared, this
phenomenon makes that rescue RxLev handover rarely executed and calls are dragged until
quality handover is triggered, which could happen too late to save the call, increasing the call
drop rate.
In this case, it is recommended to analyze with CT/CPT the level of microcell and the
neighboring macrocell level received to declare the suitable value where level handover can
safely occur.
Nortel confidential

6.22. INTERFERENCE CANCELLATION USAGE

All the field results so far lead to the following conclusion:
• 50% for interferer cancel algo usage is a very good compromise between
interference cancellation and pure thermal noise sensitivity: it does not degrade
the sensitivity and gives almost the same interference cancellation performance as
100% with 5dB cancellation loss in the range I/N=0 to 20dB. For instance, it will be
very useful in a medium traffic area, where the isolated interferers will be very well
removed with no coverage degradation.
• When pure thermal noise sensitivity is not an issue (not coverage but interference
limited situation), 100% achieves the best interference cancellation.
• In an actual network, some particular synchronization patterns may exhibit a
performance loss when interference cancellation is applied although there are
many interferers. However, on the overall network a typical net gain of about 1dB
will be obtained with 50% (remember that 1dB is 26% increased capacity if the
network capacity is limited by the uplink interferers).
The following guidelines should be applied: when the interference cancellation is available,
50% is an excellent compromise between coverage and interference cancellation. When
speed is the main problem (high speed train coverage) 100% is the best value.
Improvement appears when there is an update from a previous v15.1.1 BSS to a later one.
Indeed, before V15.1.1, gain of interferer cancellation was not optimal in case of low Rxlev.
Since V15.1.1 interferer cancellation algorithm has been improved to take into account all
range value for parameter “interferer cancel algo usage” for all RxLev range.
Nortel confidential

6.23. SET UP PRINCIPLES OF A NEIGHBORING LIST AND A BCC

PLAN
6.23.1 INTRODUCTION
An optimum neighboring plan consists in having the best compromise between the quality of
service and the network load. Indeed, the higher the number of neighboring cells in the
neighboring list, the more loaded the traffic due to HO procedures.
Moreover, an efficient neighboring plan ensures a better network reliability by avoiding an
excessive call drop rate resulting from HO failures.
Neighboring plan optimization is a trade off between:
• many neighbors which can lead to excessive HO, and thus signaling overload.
Moreover, as measurements are performed on all neighbors in the list,
measurements on the more used neighbors are less often performed than with a
shorter list. Then the system is less reactive to perform handover.
• few neighbors which would lead to call drop and poor quality of service due to HO
failures.
Hereafter are the engineering rules to follow when initializing a neighboring plan, depending
on the type of pattern used for the frequency plan.
6.23.2 4/12 REUSES PATTERN
INITIALIZATION OF THE NEIGHBOR LIST
The first step when initializing a neighbor list consists in choosing a cell as a neighbor of the
serving cell if they share a common border in the best server map. The neighboring list will
then define a geographical ring (first ring) around the serving cell.
Each cell belonging to this first ring of the given cell will be automatically included in the
neighboring list without selection on geometrical or mean field level criteria.
However, using only the list of first ring neighbor cells can lead to dropped calls or ping-pong
handover, because the coverage of some first ring neighbor cells can be thick between the
serving cell and a second ring neighbor cell.
ESTABLISHING A LIST OF CELLS ON GEOMETRICAL CRITERIA
Some neighbors must be added to the previous list, in order to avoid the mentioned troubles.
One solution could be to define another geographical ring (second ring) but this solution would
often lead to a very high number of neighbors in the neighbor list, and consequently to an
excessive number of handover. Thus, the risk is to have signaling overload.
Then, a good solution consists in defining a distance criteria, that must be fulfilled by a cell for
being considered as a neighbor.
Nortel confidential

This distance is the one separating the server cell site location, and the other cells contours.
This method corresponds to the definition of a circle with a specified diameter. Any cell
coverage being totally included within this circle, or having a part of the surface within the
circle is added in the neighbor list.
This distance can be the same for all the cells of the network. But this method is more efficient
if the distance criteria is a multiple of the cell radius. The cell radius should correspond to the
maximum length separating the cell site location and any point belonging to its coverage.
Note: height and roads are important aspects to keep in mind for neighboring plan:
• Indeed, two sites neighbor from a geometrical point of view but separated by a high
hill should not be declared as neighbor if no signal is expected to cross the
mountain.
• Also as the channel effect is very important, especially in town, neighborhood
should take into account the main roads. Two cells not neighbor with statistical
prediction models, have high probability of being really neighbor if they are located
just on a large avenue not too far apart.
RESURGENCE PROBLEMS
If the resurgence area is large and not too far from the serving cell, it can be considered as a
real cell. Consequently, this situation is equivalent to a normal cell’s neighborhood assignment
and all the cells surrounding the resurgence must be added to the serving cell neighborhood.
This situation is well handled by the automatic tools.
However, there are several other situations where the resurgence should not be taken into
account:
• The resurgence is reduced to a small area. Then the resurgence coverage is not
enough significant to be considered as a suitable cell for the handover or selection
issue. Any HO operation performs on the cell’s resurgence will lead to a “ ping-
pong ” handover from the cell resurgence to the surrounding cells.
• The resurgence is located far from the serving cell (with several cells between the
resurgence and the serving cell). This situation leads to a poor stability of the
received signal. As the serving cell is far away from the MS, the MS could easily
lose the signal and thus almost immediatly perform a handover to another cell
(signaling load).
That is why, all the cells assigned as neighbor of a serving cell because of this kind of
resurgence should then be removed from the neighbor list.
Then, such cells with resurgence which were first assigned as neighbor of a serving cell (after
distance criteria application) must be removed from the neighbor list.
Nortel confidential

CONCLUSION
Initialization with the first ring
Current cell: Candidate cell:

antenna, Azimuth, Eligibility criteria antenna, azimuth,
emission power, (distance criteria) geographical position
frequency From the current cell
List of candidate cells
Taking into account

resurgency
List of neighbours cells
6.23.3 1X3 AND 1X1 FRACTIONAL REUSE PATTERN SPECIFIC

CASE
When enabling frequency hopping on a network, a 1X3 or 1X1 pattern is generally used for
the TCH frequency plan (see chapter Frequency Hopping). Then, if the quality thresholds for
handover are not changed, the number of handover on quality criteria will increase because
the RxQual distribution is narrower (less bad RxQual samples but also less good RxQual
samples).
Thus using a distance criteria to create the neighbor list can lead to handover on TCH from a
serving cell using the same TCH frequency group than the destination (neighbor) cell. Now if
the handover is on quality criteria, the risk is high to arrive on this cell with also a bad quality
(and perhaps worst than before). Then a new handover will be triggered.
Nortel confidential

FIRST RING NEIGHBOR LIST (1X3 REUSE PATTERN)
In the case of a 1X3 reuse pattern, a way to avoid this kind of handover is to declare only the
first crown of neighbors. In the following schema, the cells in orange are not declared
neighbors to the serving cell S.
N1, T2 N6, T3 N7, T1
N2, T3 S, T1 N5, T2
N3, T2 N4, T3
N8, T1
In case of hot traffic spot, as this solution leads to a few number of cells in the neighbor list,
there is a risk of handover failure due to channel unavailability. In order to avoid this, 2
channels in every cell must be reserved for handover (allocPriorityThreshold = 2).
The only exceptions for this rule are the following:
• Coverage hole
• Limited coverage due to shadowing effect
However, this solution means a few number of neighbors in the list and then can lead to call
drop and handover failures (see scheme with first ring neighbor list before).
DISTANCE CRITERIA NEIGHBOR LIST (1X3 AND 1X1 PATTERNS)
A good solution would be to put at a disadvantage handover on quality criteria toward

neighbor cells using the same TCH group than the serving cell. It would be done in setting the
parameter hoMarginRxQual to 24 for these neighbors. However, this solution could be a good
solution for optimization but not for basic neighbor plan, because it needs a study for each cell.
A compromise is to increase the handover quality thresholds (lRxQualDLH and lRxQualULH)

as it is recommended when enabling frequency hopping. Thus, the global number of handover
will not increase and the risk of handover on quality criteria toward a cell using the same TCH
group will be low.
Then the recommended solution in the case of fractional reuse pattern (1X3 or 1X1) is the
same than for a 4X12 pattern.
Nortel confidential

HANDOVER LIST VERSUS RESELECTION LIST.
For all reuse patterns, the same cells should be declared in both handover and reselection list.
Moreover, the serving cell should be declared in the reselection list. In case of hole of
coverage, this will allow the MS to reselect the best cell and not a distant cell.
However, for 1X3 and 1X1 reuse pattern, if only the first ring is used for the neighbor list, a
higher number of reselection cells (first ring + second ring or distance criteria) than handover
cells (only the first ring) must be declared.
6.23.4 SET-UP PRINCIPLES OF A BSIC PLAN

Three main procedures can be used to set easily the BCC parameter of each cell. For all
these methods, one should take into account a distance criteria in order to minimize the
probability of BSIC / BCCH conflict between nearby cells.
• The first method is based on geographical BCC values gathering. It is done by

selecting the BCC value of a cell among the values already taken by its neighbor
cells. The chosen BCC is the-one not leading to a BSIC / BCCH conflict. The
advantage of this solution is an homogeneous distribution of the BCC among the
network. However, it is long and difficult to apply by hand and is generally used
when allocating BCC with automatic tools.
• The second method consists in using as less BCC values as possible. Then, for
each cell, first BCC equal to 0 is tried. The tried value is increased by one if it
leads to a BSIC / BCCH conflict. This operation is repeated until no conflict is
detected. This method has the advantage to minimize the number of used BCC.
Then when adding new cells, generally a BCC for this cell can be found without
creating BSIC / BCCH conflict and without modifying the BCC of existing cells.
However, it is long and difficult to apply by hand and is generally used when
allocating BCC with automatic tools.
• The third method consists in allocating a specific BCC to each occurrence of the
BCCH reuse pattern. The occurrences having the same BCC must be as far as
possible from each other. It is the most currently used method when BSIC plans
are done by hand, because it is easy and quick to apply. However it means that a
neighbor cell can not have the same BCCH than its serving cell, what is restrictive.
Nortel confidential

6.24. STREET CORNER ENVIRONMENT
6.24.1 DESCRIPTION
Especially in micro-cellular network, where the antennas are under the roof, the level received
by the mobile can dramatically fluctuate. Ping pong handovers and call drop were experienced
in this type of environment, and led to bad quality of service as well as a significant increase in
signalling traffic. One of the toughest issues to solve in a micro cellular network is street corner
environment.
cell A
cell B
Two cases must be distinguished:
• The first one deals with mobile moving straight the cross road. In the case, the
handover toward the cell A must be avoided.
• Mobiles turning at the cross road is the second case. The handover from cell B to
A must be performed quickly before the field of the current cell dropped under a
critical value, leading a call drop.
Nortel confidential

6.24.2 CASE A: MOBILE MOVING STRAIGHT

In the case of a mobile moving straight the cross road, a handover for PBGT may be
processed from cell B to cell A. Once the cross is passed, the mobile is handed again over the
cell B. This ping pong handover shall be avoided as useless handover leads to voice quality
degradation.
The parameter rxLevDLPBGT allows to cope with that case. Actually, if the signal received by
the mobile from the serving cell exceeds this threshold, then the handovers with power-budget
criteria are prevented.
cell A
cell B
RxLev
rxLevDLPBGT
cell B
cell A
Time
Nortel confidential

6.24.3 CASE B: MOBILE TURNING AT THE CROSS ROAD

In a microcell environment, the size of cells is very small (40 to 400 meters). The overlapping
margin between cells is not very important. Moreover, a fast moving mobile may cover a few
hundred meters during the handover process (in the worst configuration, the duration time of a
handover can be more than 1.5 s). The overlapping margin can be insufficient to prevent the
field of the current cell from dropping under a critical value before mobile locks on the next cell
(with standard parameters values). In such environment, reactivity is essential, handovers
have to be performed as quickly as possible.
cell A
cell B
RxLev
cell A
cell B
Time
The problem is solved by the combination of the following features:
• Early Handover decision (see chapter Early HandOver Decision)

• Protection against runHandOver = 1: in a microcell environment reactivity is
essential (see chapter Protection against RunHandover=1).
• Max rxLev for PBGT: the problem of handover toward cell A when mobile goes
straight forward is solved by a negative hoMargin for PBGT that can be set in
order to help handover when mobile turns (see chapter Maximum RxLev for
Power Budget)
Nortel confidential

6.25. SYNCHRONIZED HO VERSUS NOT SYNCHRONIZED HO
6.25.1 INTRODUCTION
Some tests have been carried in order to compare the timing HO of the three kinds of
handovers. No interBSC handovers were performed as synchronized handovers are only
available for intraBSC HO.
The test plan was the following:
Intra BSC / Intra BTS HO
• Not synchronized HO from Cell A to Cell B (UL & DL)

• Synchronized HO from Cell A to Cell B (UL & DL)
• Pre–synchronized HO from Cell A to Cell B (UL & DL) with different values of the
PresynchTimingAdvance parameter.
Intra BSC / Inter BTS HO
• Not synchronized HO from Cell A to Cell B (UL & DL)

• Pre–synchronized HO from Cell A to Cell B (UL & DL) with different
• values of the PresynchTimingAdvance parameter.
6.25.2 OMC-R PARAMETER SETTINGS

It has to be noted that ECU was enabled on both Cell A and Cell B. ECU may have an
influence on UL measurements.
SYNCHRONIZED HO
Parameters Cell A Cell B

adjacentCellHO object
CellId Cell B Id Cell A Id
Synchronized Synchronized Synchronized
hoMargin -24 -24
NOT SYNCHRONIZED HO

adjacentCellHO object
Synchronized Not Synchronized Not Synchronized
hoMargin -24 -24
Nortel confidential

PRE-SYNCHRONIZED HO

AdjacentCellHO object
Synchronized Pre sync HO with timing advance Pre sync HO with timing advance
0 0
1 1
2 2
3 3
PreSynchroTA
4 4
5 5
6 6
30 30
hoMargin -24 -24
Note: the value - 1 for the PreSynchroTA parameter stands for a TA value equal to 1 (554 m).
6.25.3 TIMING HO
PROCEDURE
The test procedure was based on tone recordings. A specific tone is sent for UL (resp. DL)
from the MS (resp. the land line). The tone is a pattern of a 3 second 500 Hz signal and a 3
second 700 Hz signal. The use of 2 contiguous signal is needed because problems of no
signal emission occurred when a one frequency tone signal is used.
The tone was sent for a minute. An HO occurred approximately every 5,7 seconds. Each
record has a serial of about 10 HOs.
All the averages shown in that study are calculated from these 10 values.
SYNCHRONIZED HO RESULTS
COLLECTED DATA
HO # Muting (ms) Silence (ms) Demuting (ms) Total (ms)

1 26 55 28 109
2 14 60 21 95
3 21 57 15 93
4 31 61 14 106
5 14 52 15 81
6 26 50 19 95
7 70 26 19 115
8 66 28 26 120
9 43 25 46 114
10 49 10 38 97
11 29 18 36 83
Nortel confidential

The (1,2,3,4,5,6) HO # are HOs which occurred in the 500 Hz frequency part of the tone.
The (7,8,9,10,11) HO # are HOs which occurred in the 700 Hz frequency part of the tone.
STATISTICS & COMMENTS
• HOs in 500 Hz frequency tone part
Muting (ms) Silence (ms) Demuting (ms) Total (ms)

22 56 19 97
14 50 14 78
31 61 28 120
7 4 5 16
• HOs in 700 Hz frequency tone part

51 21 33 106
29 10 19 58
70 28 46 144
17 7 11 35
For both frequencies, the average timing HO of a synchronized HO is the same, around 100
ms. The interesting part is that the time repartition between the muting, silence and demuting
phases are not the same.
The muting and demuting phases appear to be dependent on the frequency. However, the
muting and demuting algorithms at the TCB are not dependent on the frequency. Actually, the
ECU activation on both cells may be responsible of this dependence. It seems that the ECU
algorithm at the BTS makes the muting and demuting dependent on frequency.
When ECU is enabled, it seems that the muting and demuting slopes are correlated to the
frequency.
NOT SYNCHRONIZED HO RESULTS
COLLECTED DATA
HO # Muting (ms) Silence (ms) Demuting (ms) Total (ms)

1 25 133 4 162
2 47 113 84 244
3 40 114 43 197
4 20 137 47 204
5 24 131 43 198
6 48 93 33 174
7 18 123 46 187
8 38 143 38 219
9 25 109 44 178
Nortel confidential

The (1,2,3,4,5,6,7,8,9) HO # are HOs which occurred in the 500 Hz tone part of the signal.
STATISTICS & COMMENTS

32 122 42 196
18 93 4 162
48 143 84 244
12 16 20 25
The Not Synchronized Timing HO is around 200 ms. Unfortunately, the high standard
deviation value does not allow any conclusion on this specific duration.
Note: Not synchronized HO procedure
Here is a brief example of the L3 radio protocol of such a HO:
• DL: HANDOVER COMMAND

• UL: HANDOVER ACCESS
• DL: PHYSICAL INFO
• UL: HANDOVER COMPLETE
The TA is indicated from the target BTS to the MS in the PHYSICAL INFO.
We can make the statement that the not synchronized HO is twice slower than the
synchronous one. It is mainly due to the PHYSICAL INFO expectation of the MS.
PRE-SYNCHRONIZED HO RESULTS
PRINCIPLE
The pre-synchronized handover procedure is exactly the same than the synchronized
handover procedure.
After the Handover Access bursts which shall be sent with a TA value of 0 the MS shall use a
TA as specified in the HO Command by the old BTS, or a default value of 1, if the old BTS did
not provide a TA value.
The BSC indicates in the HO Command message that the handover will be pre-synchronized
and, if needed, the predefined Timing Advance to be used by the MS in the new cell
(preSynchroTimingAdvance parameter).
COLLECTED DATA
The real TA of both cells is 0 (but fluctuant sometimes to a TA value of 1). The aim of these
tests is to evaluate the voice quality loss and/or gain of a pre-synchronized HO versus the
preSynchroTimingAdvance value set at the OMC-R.
Nortel confidential

STATISTICS
PreSynchroTA (kms) 0 -1 1 2 3 4 5 6 30
Average (ms) 120 122 89 105 436 739 756 684 705
Minimum 108 94 65 89 79 524 606 532 533
Maximum 129 144 126 105 958 971 970 947 945
Standard Deviation 8 18 17 13 334 172 133 132 133
COMMENTS
It has to be understood that the pre-synchronized handover has been implemented in order to
fasten the handover procedure in a dense (size <2kms) environment or in a railway / highway
optimization. As the setting of the preSynchroTimingAdvance parameter is not that easy (on-
field measurements and TA distributions after HO per pair of cells), the behavior of the MS for
a wrong (2 or 3 steps of TA) and a very wrong (greater than 3 steps of TA) TA value is very
interesting for the network optimization.
Actually, regarding the timing HO results versus different preSynchroTimingAdvance values, it
seems that the MS is able to re-synchronize with the BTS. The drawback is that the speech
cut duration and the handover procedure are highly increased (up to 1 second).
CONCLUSION
Regarding the results of that study, it clearly appears that the synchronized handover is the
faster type of handover. It is available for intraBTS or intracell handovers, or if the Network
Synchronisation is activated. In this case, if the two cells are synchronized by GPS, and they
have the same TNOffset, handover can be synchronized, even if the two cells are not in the
same BSC.
However, the pre-synchronized handover has shown very good results (almost the same
performance than the synchronized one) if the TA after HO is previously known.
Therefore, pre-synchronized HO is a good solution to fasten handover and to decrease (up to
80 ms) the speech cut duration. The fields of appliance should be dense (cell size < 2kms),
railway or highway environment to ensure that the distance after handover is known.
Not synchronized handover still remains the only setting for InterBSC handovers.
Anyway, the UL results of that memo show that the speech cut duration is less than 250 ms.
This value allows to keep a pretty good voice quality during handovers.
Nortel confidential

6.26. BTS SENSITIVITY
6.26.1 DEFINITION OF SENSITIVITY

In this chapter, sensitivity figures are clarified, knowing that such notions as static, dynamic,
guaranteed and typical may often lead to confusion.
The sensitivity is completely defined in the GSM recommendation 05.05. §6.2., as the input
level for which all performances in terms of frame erasure, bit error or residual error rates are
met. A reference table specifies rates varying according to the type of GSM channel (traffic,
signaling) and the type of propagation channel (static, urban, rural, hilly terrain).
Sensitivity is measured at antenna connector, and by definition this figure takes into account
all RF elements losses included in BTS cabinet, as shown on the following figure:
Antenna
Common
Cable losses
Rx sensivity
Antenna connector
Duplexor
Combiner Rx diversity gain
Power Amplifier Base Station
Nortel confidential

6.26.2 STATIC AND DYNAMIC SENSITIVITY

Static sensitivity could be viewed as the level at which sensitivity performance is met in the
static channel mode. Yet, the static mode is only one of the propagation models among others
specified in the GSM Recs. reference table. The static mode is the most favorable case
(excepted a few cases of fully not correlated antennas and 2-branchs diversity). In terms of
radio, it can be understood that for a given signal input, less communication errors are
expected within a configuration where there are no multi-path effects at all.
6.26.3 TYPICAL / GUARANTEED SENSITIVITY

Typical sensitivity is 1dB better than the worst-case used, mainly due to the variation in
performance of the RF front end and not the variation in the DRX module. The variation in
performance of DRXs on a per cell basis is therefore very tightly controlled. For more details,
please refer to the BTS Engineering Rules ([R47] to [R56]).
6.26.4 SPACE DIVERSITY GAINS
FADING CORRELATION
One major parameter to assess space diversity gain is the fading correlation, which depends
on many factors, such as radio environment (angular distribution of reflectors), antenna
configuration (spacing between antennas) and position of the mobile respective to the BTS.
The sensitivity for fully correlated antennas and not correlated antennas (correlation 0.2) can
be viewed respectively as the worst case and quasi-best case situations. In reality, the
correlation figure lies ‘somewhere between’ both figures, depending on the factors mentioned
previously.
To assess correlation values applicable to engineering is not an easy task. Yet, it can be
observed that by taking 10 wavelengths of antenna separation (recommended distance is 20),
the correlation factor is as low as 0.2 for an angular spread of only 1 degree .These results
give us enough confidence to interpolate the sensitivity at values near the not correlated case,
in such environments as built-up areas (urban, suburban), as well as hilly terrain, which offer a
multiplicity of reflectors. However, this appears less obvious for open area environments,
typically flat rural, for which we will assume a more conservative correlation factor.
BRANCH SENSITIVITY
Diversity gains are calculated by doing the difference between “with” and “without” 2 antennas
figures. Then diversity gains vary a lot with correlation and propagation channels. Yet, it can
be observed that after rounding figures, the overall sensitivity + diversity figure stays relatively
constant, independently of the configuration. The trend is a cumulated figure of -113 dBm for
the S8000 without enhanced coverage option, and -115 dBm for the S8000 with enhanced
coverage option.
This observation partly justifies the uniformity of the diversity gain of 5 dB for the S8000. It
must be stressed that this artifice is only meant to provide separate figures for sensitivity and
diversity gain, which are still distinguished when discussing link budgets
Nortel confidential

6.26.5 CROSS-POLARIZATION ANTENNA USE

The use of cross-polarization antenna has followed a growing trend, due to the flexibility
offered in terms of site installation (two antenna packaged into one, offering diversity gain and
coupling 2 TRXs on a single antenna without hybrid coupling).
Cross polar antenna is characterized by:
• 2RF ports for one antenna

• slant polarized transmission.
Hence use of cross polar antennas implies:
• simplification of the coupling stage.

• radio link performances modification.
• diversity of polarization.
SIMPLIFICATION OF COUPLING STAGES
It should be understood that with the same number of antennas as for spatial diversity
crosspolar antennas provide 2 times more RF ports. This means that on one feeder, the
number of supported DRX is divided by two, and the size of the coupling stage too.
RADIO LINK PERFORMANCES
Radio link performances are affected by the transmission over slanted polarization:
measurement reports indicate performances of crosspolar antennas compared to vertical
antenna are lower:
• in urban area of 1dB in 900 MHz and 2dB in 1800 MHz.

• in flat rural area of 3dB in 900 MHz and 1800 MHz.
Note: performances of crosspolar antennas are strongly dependent on environment, and
mainly on reflectors and scatterers: the more they are, the better the performances.
For link budget purposes, crosspolar antennas recommended typical losses are:
• in all environment, 1.5dB in 900 MHz and 1800 MHz.

• in flat open area, 3dB in 900 MHz and 1800 MHz.
POLARIZATION DIVERSITY
Polarization diversity is obtained by processing the two signals coming from the two branches
of one crosspolar antenna. Polarization diversity is estimated after measurements of signal
decorrelation between the two diversity receiving branches of one crosspolar.
Nortel confidential

LINK BUDGET FIGURES
Proposed link budget figures for crosspolar antenna use are summarized in the table below:
all environments flat rural, flat open

900 MHz & 1800 MHz 900 MHz & 1800 MHz
radio link performances (DL & UL) -1.5dB -3dB
diversity gain +4dB (5dB)* +4dB (5dB)*
(*) Crosspolar antennas offer as diversity solution:
• polarization diversity (4dB gain) when 1 crosspolar antenna is used.

• spatial diversity(5dB gain) with 2 crosspolar antennas.
6.26.6 CIRCULAR POLARIZATION AND CROSSPOLAR ANTENNAS

This system, Nortel patented, combines two types of advantages:
• the crosspolar antenna benefit of the 2 antennas connectors within one antenna
chassis.
• the robustness of circular polarization against depolarization effect and mobile
positioning.
This system relies on a single 3dB-90° dephaser-hybrid coupler located at the bottom of the
crosspolar antenna feeding the two ports of the crosspolar antenna with exactly the same
feeder length. The system scheme is shown below:
BTS with BTS with

polarization space
diversity diversity
Nortel confidential

In term of radio figures, the benefits of the crosspolar antenna use combined with the 3dB-
coupler are:
• the radio transmission is no more affected by the slanted polarization due to the
transmission of the whole signal over a circular polarized wave. Whatever the
position, the mobile receives all the power
• the combining stages are divided by 2
• the diversity gain is:
4dB with 1 crosspolar antenna the polarization diversity gain
5dB with 2 crosspolar antenna the space diversity gain
Recommended figures for this system are
all environments 900 MHz & 1800 MHz

diversity gain polarization diversity +4dB
space diversity +5dB
radio link performances
0dB
(UL and DL)
Nortel confidential

6.27. SDCCH DIMENSIONING AND TDMA PRIORITIES

The aim of this chapter is to define engineering rules associated to SDCCH dimensioning and
TDMA priorities .
6.27.1 SDCCH DIMENSIONING

An SDCCH assignment is provided when one of the following Layer 3 message is received:
• CM Service Request (includes IMSI attach)

• Paging Response
• IMSI Detach
• Location Update
So the number of these messages has to be taken into account in the dimensioning of the
SDCCH channels. Some rules are defined here below.
PARASITE SDCCH ALLOCATION
The level of noise can provide a parasite SDCCH allocation, the BTS seems to receive an
RACH and allocates an SDCCH channel. In this case the SDCCH is assigned for a short
duration (free after T3101 (3 sec by default)). The parasite SDCCH assignment depends of
the BCCH TDMA model. Note that from V8B7 the number of parasite SDCCH becomes
negligible with new DRX.
BTS GEOGRAPHICAL POSITION IN THE LAC
The location update frequency must also be considered for the evaluation of the blocking rate
ratio for SDCCH. For BTS located at the border of a Location Area, a lot of location updates
are performed. Then, the signaling traffic is very high. In this case (as for area with a high
SMS traffic), the number of SDCCH channels must be quite high. Therefore, the blocking rate
ratio to consider for SDCCH must be lower than the-one for TCH.
Thus, a table can be established for the blocking rates to consider, depending on the load of
the network and the kind of signaling.
TCH SDCCH Blocking rate

Blocking rate Middle LAC LAC border
Normal load 2% 0.1 % 0.1 %
Very loaded 5% 0.1 % 0.1 %
DOUBLE SDCCH ALLOCATION
The double SDCCH allocation occurs when a second RACH is sent by the mobile before the
Immediate Assignment message of the first RACH is received.
The double allocation issue depends on the numberOfSlotsSpreadTrans value.
Nortel confidential

ACTIVATION OF SMS-CB
The SMS-CB is multiplexed with the SDCCH. So the activation of the SMS-CB reduces the
number of SDCCH sub-channels and so the signaling capacity of the BTS. For example:
• SDCCH/4 + SMS-CB => 3 SDCCH available (combined case)

• SDCCH/8 + SMS-CB => 7 SDCCH available (not combined case)
TDMA Model Capacity (erlang)

SDCCH/4 0.439
SDCCH/3 0.194
SDCCH/7 1.579
SDCCH/8 2.057
So the activation of the SMS-CB has a great impact on the signaling capacity of cell (see also
chapter SMS-Cell Broadcast)
Note: in case of SMS-CB, the SDCCH TS number has to be lower than 4 (< 4)
SUBSCRIBERS MOBILITIES
In a high mobility area (rural, highway) a none negligible number of the RACH are requested
for Location Updates. The total number of RACH is then higher than in a low mobility area, it is
then better to increase the number of SDCCH channels.
In a very high mobility area (high speed train) the number of Location Area are generally
reduced in order to avoid a BSS signaling overload due to the LA update. Moreover the TCH
allocation has to be as fast as possible in order to avoid dropped calls set-up. So for the cells
which are dedicated to the coverage of very high mobility area only, (e.g. cells which cover
only the high speed train railways and not surrounding roads or villages) it is better to reduce
the SDCCH channels number. If the cell is at the boundary of a location area the SDCCH
channels have to be set according to the Location Area update load.
NUMBER OF NETWORKS
The SIM card can contain the Id of only 4 forbidden networks, i.e if there are more than four
networks in a country a mobile can attempted a Location Update on other networks (->
Location Reject). So wherever there are more than four competitors in the same frequency
band it is recommended to increase the number of SDCCH channels.
6.27.2 TDMA PRIORITIES

It is possible to allocate “priorities” to TDMA frames. Each TDMA has two priorities, each
serving a different purpose :
- the “TRX/TDMA mapping priority”, represented by the parameter priority (transceiver
object)
- the “PCM allocation priority”, represented by the parameter trafficPCMallocationPriority

(transceiver object)
Nortel confidential

TRX/TDMA MAPPING PRIORITY (PARAMETER : PRIORITY)
This priority defines the order with which the BTS allocates the available hardware resources
(the transceivers) to the TDMA frames. In practice, if due to a hardware failure, there are fewer
TRX than TDMA, then only the TDMAs of higher priority will be mapped onto a TRX.
The parameter is called priority (transceiver object).
Among the set of TDMA frames attached to a cell, it is mandatory for the one carrying the
BCCH to have the highest priority allocated and to be the only one to have that priority.
For the TDMA carrying SDCCH channels, that priority should be the second highest priority,
i.e. not as high as the BCCH priority.
For the TDMA carrying only TCH channels that priority should be the lowest.
The generic rule to set the TRX/TDMA mapping priorities is the following :
BCCH TDMA : priority = 0

SDCCH TDMA : priority = 1
TCH TDMA : priority = 2
The typical values for priority of each TDMA model is defined in detail in the Radio Interface
Engineering Rules ([R58]).
PCM ALLOCATION PRIORITY (PARAMETER :

TRAFFICPCMALLOCATIONPRIORITY)
The parameter trafficPCMAllocationPriority (transceiver object) defines the priority level of a

TDMA frame for mapping onto a PCM on the A-bis interface. In case of failure of one or more
Abis PCMs, TDMAs of highest such priorities are allocated DS0 on the remaining Abis PCM
links before TDMAs of lower priority.
The engineering rule associated to this parameter will depend on the strategy the operator
wants to use for the corresponding site.
The default engineering rule is to give the lowest priority (255) to the TDMA supporting the
BCCH, because the BCCH is conveyed on a LAPD TS, which is always present. So the BCCH
signalling and the SDCCH signalling is never lost. As the TDMA supporting the BCCH has
fewer traffic channels than other TDMA, it makes sense to save these other TDMA before
saving the BCCH TDMA.
However, one can privilege:
• the traffic in one of the sectors: for example on a site linked by two PCMs if a cell is
considered as more important by the operator (strategic coverage), one can give
to the TDMAs of that cell a higher priority than those of the other cell. Thus, during
a PCM failure, those TDMA will be re-configured in priority on the left PCM.
• circuit traffic instead of packet data traffic, by setting a higher priority for TDMAs
having only TCH compared to TDMA that have also pDTCH
Nortel confidential

6.28. ENGINEERING GUIDELINES FOR EXCEPTIONAL EVENTS

This chapter is intended to provide guidelines on how to prepare Nortel GSM networks for
“exceptional events” from an engineering perspective. An exceptional event, as described in
this document, is a temporary event which is known in advance and which will generate an
exceptional high traffic load on the network. Nortel’s estimation is that it is economically not
justifiable to dimension a GSM network for these special events. Commonly, a GSM network
is dimensioned to carry the traffic of the busy hour. The actions proposed in this document are
intended to optimize the behaviour of the network during an exceptional event. The document
covers recommended actions on the NSS and on the BSS. On the NSS, the document
describes a set of recommended verifications that Nortel encourages the operator to do in
order to optimize the DMS behaviour. In addition a set of recommended office parameter
settings on the MSC is given with the aim of optimizing the behaviour of the BSC. On the BSS
side, this document presents the list of strongly recommended verifications and a set of
parameters values to be applied for any wide area special event. Nortel recommends that the
normal parameter setting should be reconfigured after the exceptional event.
On the NSS side, the document is applicable to GSM09, GSM10, GSM11 and GSM12. It is
assumed that all required patches on NSS and BSS are applied. Apart from the paragraphs on
CM, LPP and NSS recommendations in Chapter 4.31.3.1, most of the NSS recommendations
can also easily be applied on non-Nortel NSS equipment.
As signalling is the bottleneck during a high load situation on the BSS, the guiding idea here is
to reduce as much as possible unnecessary signalling during the exceptional event. Nortel’s
estimation is that this should improve the behaviour of the BSC.
The control of this situation is done by various verifications and parameter modifications. The
proposal is organised in 4 main levels:
• Prerequisite
• Basic tuning of parameters
• Overload configuration change
• Other parameter modification
6.28.1 BSS PREREQUISITE
CHECKS
SANITY CHECKS
Should be done at least one month before the foreseen event :
• Verification of the state of the different BSC: no BSC boards should be in a faulty
state
• Recommended values are applied
• Dimensioning rules are respected
Nortel confidential

NETWORK:
Each BSC is fully operational and a switchover should be done, LapD load balancing over
TMU, LapD loadsharing, Location Area (LA) sizing,, TCH congestion (this is particularly
important in case of concentric cell use), Call Drop rate, HandOver failure rate (and
neighbouring reciprocity).
CHECKS CORRELATED WITH THE SPECIAL EVENT
The Nortel Recommendation is that these checks be done a few hours before the special
event.
LIMITATION OF THE OAM ACTIVITIES
The Operation, Administration and Maintenance shall be minimum. So:
• all Call Traces and Call Path Traces shall be stopped/discarded

• Observations should be limited; temporization for permanent observation should be
set to at least 30 minutes
• Freeze of the network operation: No reparenting activity or NRP should be
performed during the critical period
Moreover, no modification of the network during the special event (such as command files,
OMC commands, …) shall be done.
LIMITATION OF THE SIGNALIZATION TOWARDS THE BSC
• Periodic location updates should be limited on the BSS side (recommended value
for timerPeriodicUpdateMS = 60)
• Operator advertising using SMS should be avoided
• If a degradation of the QoS is acceptable during the corresponding critical period:
Paging repetition at NSS side should be reduced / suppressed,
Notification of voice mail through SMS should be limited / deactivated
Authentication procedures should be limited / deactivated at NSS level
Ciphering should be limited at NSS level
6.28.2 BSS: SUGGESTIONS FOR PARAMETERS TO BE MODIFIED

FOR THE SPECIAL EVENT
It is suggested that the following parameters be modified before the special event and set
back to the previous value afterwards (when the amount of traffic is back to a ”normal” level):
These parameters are split into 3 categories.
• The modification of parameters of the 1st category does not lead to any service
interruption. These modifications may be done very quickly and a few hours before
the event.
• Parameters of the 2 nd category are only applied if it can be done without service
interruption (refer to chapter ALGORITHM PARAMETERS).
• Modification of parameters of the 3 rd category is optional and only applicable on
networks in which queuing is already activated. It requires a quite long preparation
Nortel confidential

and should be decided at least three months before the special event. It does not
lead to service interruption.
Parameters to modify:
• abisSpy = “not in progress”

• unknownCellWarning = “disabled”
• interBscDirectedRetry = “not allowed”
• intraBscDirectedRetry = “not allowed”
• Multipaging timer on Abis interface = 200 ms
• maxNumberRetransmission = 1
• bscCapacityLoadReduction feature is not available for BSC3000, but dedicated
overload mechanism for BSC3000 exist (see chapterBSC3000 Overload
Management)
6.28.3 NSS LEVEL
DMS PREPARATION
Note: the recommendations in this Chapter should also be followed after the exceptional
event.
COMPUTING MODULE (CM)
The Computing Module (CM) of the DMS is protected by a highly efficient overload
mechanism. This mechanism allows the DMS to stand a significant overload.
In order to maintain the craftsperson’s capability to access the DMS in the expected overload
situation, it is suggested that verification is made to ensure that at least the 2 MAP terminals
as well as the ETAS modems are declared as guaranteed background task for the CPU. This
is done by setting for these devices in table TERMDEV the GUAR field to Y. A maximum of 5
devices can be declared in this way. Refer to NTP 411-3001-451 Customer Service Data
Schema Vol 3.
LINK PERIPHERAL PROCESSOR (LPP)
The behaviour of the LPP under heavy traffic conditions can be improved by optimizing the
allocation of BSSAP instances to LIU7s. It should be checked that the following
recommendations are followed.
Context
Table GSMSSI defines the subsystem instances of the BSSAP local subsystem. These
instances reside on an LIU7 and serve SCCP Class 2 connections between the BSS and the
DMS-MSC.
Table GSMSSI allows the customer to associate BSSAP instances with LIU7s.
BSSAP instances are used only for A-interface messaging. They can be datafilled on any LIU7
in the MSC. Also, there is no restriction that an A-interface LIU7 must have a BSSAP datafilled
against it. However, datafilling the BSSAPs in a non-optimal manner can negatively impact
the DMS-MSC’s performance under heavy messaging conditions.
Nortel confidential

Further information about table GSMSSI and the BSSAP instances can be obtained in The
CCS7 Application Guide, NTP #411-2231-310. This document includes a datafill example for
GSMSSI.
Recommendations
The recommendation is that all customers apply the following guidelines:
• BSSAP instances in table GSMSSI should only be defined against LIU7s which
have an inservice link to a BSC.
• Each A-interface linkset should at least have one BSSAP instance assigned to it.
The remaining instances (total of 32) should be spread out among the remaining
A-interface LIU7s. Priority should be given to the highest traffic linksets.
SS7 LINK
Underprovisioned SS7 links can result in link congestion, which potentially inhibit mobile call
processing. It is therefore recommended to audit the link provisioning in the network before the
special event. During the busy hour the mean link occupancy should not exceed 40%. The
expected subscriber growth in the network has to be taken into account. This check should be
done about 4 months before the special event in order to allow potential HW extensions.
LAC DATAFILL
The Location Area Code (LAC) is a configurable parameter on the BSS and on the NSS (table
LAC). If the values are not the same, Mobile location updates on the MSC will fail. This will
result in all mobiles to repeat the locationupdate attempt. The resulting high signaling load can
decrease stability of the LPP due to the increased signaling traffic. It is therefore highly
recommended to verify that the LAC values on BSS and NSS match up before the special
event.
BSC PROTECTION
Reduction of the signaling load on the BSC optimizes its behavior in a high traffic situation.
This chapter proposes actions in the NSS, which will help to decrease the signaling load on
the BSC.
SMS VOICEMAIL NOTIFICATION
Most of the GSM networks use voicemail notification via SMS. SMS traffic is real-time cost
intensive on the BSC processors. Furthermore, in a high traffic situation with degraded QoS,
the Voicemail traffic is expected to significantly increase. The operator should consider to
deactivate the notification of voicemails via SMS. Under very high load the notified subscribers
will not be able to consult their voicemails anyway, due to the high blocking rate at the Air
interface. The deactivation should be done either on the VMS or on the SMSC.
AUTHENTICATION
Authentication in GSM aims at ensuring that only mobiles with an official SIM card can access
the network. Reducing authentication reduces the signaling on the BSS. The operator should
consider to disable the optional authentication activities in the network. This can be done by
Nortel confidential

modifying parameter AUTH_CONTROL_PARM in table OFCVAR. To configure to a minimum

activity the parameter has to be set as follows
GSM09: AUTH_CONTROL_PARM = NORM_0 PER_0 ATT_0 MO_0 MT_0
IMPACT
It should be noted that even with this minimum setting the authentication procedure will be
executed at the first Attach or Inter-VLR-location update of a mobile at the MSC. This implies
that a reasonable degree of security is reached. The default value of NORM_20 PER_20
ATT_20 MO_20 MT_20 configures that every 20th call, location update and attach will trigger
the authentication procedure. The above described minimum value results in only the first
location update (inter-VLR or attach) to trigger authentication.
The parameter allows to individually set authentication rates for normal (NORM), periodic
(PER) location updates location, Attachs (ATT), mobile originated (MO) and mobile terminated
(MT) calls.
PAGE RETRY
The Paging message sent to the BSC is highly costly in terms of BSC CPU processing. After a
timer expires without a response from a mobile, the DMS sends a second Paging message.
Monitoring of live networks has shown that only an insignificant portion of the second paging
message is successfully responded by a mobile. Due to this it is recommended to deactivate
the paging retry. This is done by setting the parameter GSM_PAGE_RETRY in table
GSMVAR to 0.
CIPHERING
Ciphering guarantees confidentiality of GSM communications on the radio interface.

Deactivating Ciphering reduces the signaling on the BSC. The operator should consider
whether the deactivation of ciphering is acceptable during the special event. To deactivate, the
officeparameter GMSC_CIPHERING in table OFCENG of the MSC has to be set to OFF.
Nortel confidential

6.29. ENGINEERING LIMITS WITH BSC OVERLOAD CONTROL

MECHANISM
The main objective of the BSC overload control mechanism (introduced in V12) is to maintain
BSC robustness during a traffic overload period.
The BSC controls achieve this by filtering of Mobile Originated calls, Mobile Terminated calls,
Location Updates, Handover or Random Access Channel messages. This results in a Quality
of Service degradation when the overload is reached (through an increasing “Call Attempts
reject rate”), as illustrated below:
Mean CPU occupancy Offered traffic
100 %
CPU call processing OAM & internal process

limit (ex: 70%)
Carried traffic
CPU engineering
limit (ex: 55%)
QoS decrease
BSC’s maximum BSC overload control

throughput with mechanism is triggered
the highest QoS
Mean Call Attempts
6.29.1 “CPU ENGINEERING LIMIT” MEANING

The “CPU Engineering limit” is defined as the limit of mean CPU occupancy (used for Call
Processing only) not to be exceeded in order to maintain the highest Quality Of Service.
When exceeding this engineering limit, the probability that the Quality of Service is degraded
due to the triggering of the overload control mechanism cannot be neglected.
The following set of “CPU Engineering limits” is based on lab performance reports and
validated in the field. Below these limits, no QoS degradation has been observed.
BSC2G Board CPU engineering limits

MPU & BFIP 55 %
SICD 60 %
BSCB 60 %
OMU - SUP- SWC 90 %
Nortel confidential

6.29.2 “CPU CALL PROCESSING LIMIT” MEANING

The “CPU Call Processing limit” is defined as the limit of mean CPU occupancy (used for Call
Processing only) not to be exceeded by the different boards, regardless of Quality of Service.
The overload control mechanism acts to keep the mean Call Processing CPU occupancy due
to the traffic below this limit.
The remaining x% is reserved for other processes required for OAM signaling and internal
processes. The following set of “CPU Call Processing limit” is based on field experience and
lab performance reports.
BSC2G Board CPU call processing limits

MPU & BFIP 70 %
SICD 70 %
BSCB 70 %
OMU - SUP- SWC 100 %
The monitored average TMU1-SBC processor load should keep below 70%.
The monitored average TMU1-PMC processor load should keep below 85%.
The monitored average TMU2-SBC processor load should keep below 80%.
Nortel confidential

6.30. POWER CONTROL COMPENSATION IN INTERZONE

HANDOVER
6.30.1 IMPORTANT NOTE

This chapter deals with the theoretical pre-v17.0 behaviour of the power control during
interzone handovers for the 3 concerned cell types (concentric cell, dualcoupling cell,
dualband cell) and for each Power Control algorithm (step by step, one shot).
Note that in v17.0, a new feature enables the BSS to compensate for the power gap that used
to exist between old and new channel, each in a different zone, when performing an interzone
handover. The v17.0 behaviour is explained in the Power adaptation after an interzone ho
(V17) section of this document and in even more detail in the functional note [R42].
For the study that follows, only the pre v17.0 behaviour is described.
3 phases are defined:
• Phase 1: the MS is handled by a TDMA belonging to the band0/outerzone and the

TX power is stable
• Phase 2: the MS is handed over toward a TDMA belonging to the
band1/innerzone; the power control is not running
• Phase 3: the power control is started and the power becomes stable
6.30.2 DUALBAND CELL
STEP BY STEP ALGORITHM
In this example, we suppose that BS transceivers have the same maximum power in each
band. The studied case is the RxLev_DL but the RxLev_UL is similar.
Nortel confidential

interZone handover
RxLev DL
biZonePowerOffset
SACCH
2
BS Pwr Att
SACCH
2
Band 0 Band 1
There is no power compensation during the handover: the initial power after a handover
doesn’t take into account the difference of radio propagation between the two bands. So, there
is a signal drop (approximately biZonePowerOffset).
However the condition on level for the Interzone handover ensures that the signal drop has no
effect.
The Step by step algorithm keeps the RxLev_DL in the interval L_RXLEV_DL_P,
U_RXLEV_DL_P. Thus the attenuation on BS power decreases in order to compensate the
signal drop.
CONCLUSION
The Step by step algorithm compensates the signal drop.

Note: If the initial attenuation (in level) after the handover is less than biZonePowerOffset, the
definitive power compensation is reduced.
ONE SHOT ALGORITHM
ONE SHOT APPLIED TO THE BS POWER
The BS transceivers have the same maximum power in each band.

DL_TxPwr_BandX dB are attenuations resulting from the one shot algorithm.
Interzone handover toward Band1: there is no power compensation on the HO, e.g. the initial
power after a handover doesn’t take into account the difference of radio propagation between
the two bands. So, there is a signal drop (approximately biZonePowerOffset).
Band1 after the Power control:
Nortel confidential

RxLev DL_Band1 = RxLev DL _Band0 - biZonePowerOffset + K_DL *

Bizone_power_offset / VAL_PWRLEV_TO_DB
(with VAL_PWRLEV_TO_DB = 2)
Note: if the DL_TxPwr_Band0 (dB) is lower than K_DL * biZonePowerOffset, the power
compensation is reduced.
Example:
Bizone_power_offset = 3 level (6 dB)
• Bad quality without frequency hopping: K_DL = 0.5, RxLev DL_Band1 - RxLev
DL_Band0 = -3 + 0.5*3/2 = -3 level (-6 dB)
• Good quality with frequency hopping: K_DL = 0.9, RxLev DL_Band1 - RxLev
DL_Band0 = -3 + 0.9*3/2 = -1 level (-2 dB)
ONE SHOT APPLIED TO THE MS POWER
There is an MS transceiver maximum output power for each band:
• Pm0 (max transmitting MS power in band0) depends on the MS_classmark in

Band0 and on the network parameter MS_TXPWR_MAX.
• Pm1 (max transmitting MS power in band1) depends on the MS_classmark in
Band1 and on the network parameter MS_TXPWR_MAX_BAND1.
DPMS = Pm0 - Pm1.
UL_TxPwr_BandX dBm are absolute powers resulting from one shot algorithm.
There is no power compensation on the HO: the initial power after a handover doesn’t take
into account the difference of radio propagation between the two bands. So, there is a signal
drop (approximately biZonePowerOffset).
Band1 after the Power control:
RxLev UL_Band1 = RxLev UL _Band0 - biZonePowerOffset + (K_UL *

biZonePowerOffset - (1-K_UL) * DPMS ) / VAL_PWRLEV_TO_DB
(with VAL_PWRLEV_TO_DB = 2)
Example:
Bizone_power_offset = 3 level (6 dB)
DPMS = 3 dB
• Bad quality without frequency hopping: K_UL = 0.5, RxLev UL_Band1 -

RxLevUL_Band0 = -3 + (0.5*3 - 0.5*3) / 2 = -3 level (-6 dB)
• Good quality with frequency hopping: K_UL = 0.9, RxLev UL_Band1 -
RxLevUL_Band0 = -3 + (0.9*3 - 0.1*3) / 2 = -2 level (-4 dB)
Nortel confidential

CONCLUSION
The definitive power compensation with the One shot algorithm is reduced especially when the
frequency hopping is not used. However the condition on level for the Interzone handover
ensures that the compensation is not indispensable.
In comparable conditions, the difference of level (resulting from the Power control) between
the two bands of a Dual Band cell always exist. It is not tied to the handover example.
6.30.3 CONCENTRIC CELL
ONE SHOT ALGORITHM
The BSC knows the BS maximum output TX power in each zone, so the attenuation is
compensated during an Interzone handover.
RxLev DL_Zone1 = RxLev DL _Zone0 - (1-K_DL )*DP BS ) /VAL_PWRLEV_TO_DB
RxLev UL_Zone1 = RxLev UL _Zone0 (with VAL_PWRLEV_TO_DB = 2)
Example: DPBS = 15dB
• Bad quality without frequency hopping: K_DL = 0.5, RxLev DL_Zone1 - RxLev
DL_Zone0 = - 0.5*15/2 = -3.7 level (-6 dB)
• Good quality with frequency hopping: K_DL = 0.9, RxLev DL_Zone1 - RxLev
DL_Zone0 = - 0.1*15/2 = -0.7 level (-0 dB)
6.30.4 DUALCOUPLING CELL
ONE SHOT ALGORITHM
The BS maximum output TX power is the same in each zone (DP BS ), but the difference
comes from different coupling losses (downlink) which have the same effect than a difference
of radio propagation.
The power is not compensated during an Interzone handover. The Power control result is
nearly the same in the two zones.
RxLev DL_Zone1 = RxLev DL _Zone0 - Bizone_power_offset + K DL *

Bizone_power_offset / VAL_PWRLEV_TO_DB
RxLev UL_Zone1 = RxLev UL _Zone0 (with VAL_PWRLEV_TO_DB = 2)
Example:
Coupling D (loss about1dB) and H2D (loss about 4dB)
Nortel confidential

Bizone_power_offset = 3dB = “1.5 level”
• Bad quality without frequency hopping: K_DL = 0.5, RxLev DL_Zone1 - RxLev
DL_Zone0 = - 1.5 + 0.5*1.5/2 = -1.1 level (-2 dB)
• Good quality with frequency hopping: K_DL = 0.9, RxLev DL_Zone1 - RxLev
DL_Zone0 = - 1.5 + 0.9*1.5/2 = -0.8 level (-0 dB)
The One shot associated with Dual coupling cells has a good behavior.
Nortel confidential

6.31. GSM PAGING REPETITION PROCESS TUNING

The paging repetition process is designed to improve the paging answering performances of a
network (repetition normally take place at a LAC level). Paging messages broadcasted to
locate a mobile are systematically repeated in order to maximize the probability of answering,
and the repetition is performed eventhough the mobile answers from the first paging message.
This repetition depends on some parameters but also the configuration of the cells
broadcasting the paging messages.
The paging repetition process can be tuned to avoid in specific cases repeating too much
paging messages and thus decrease the number of paging messages queued or discarded.
6.31.1 PAGING PARAMETERS
BSS PARAMETERS
On the BSS side many parameters have an influence on the paging and the paging repetition
process:
• noOfBlocksForAccessGrant: it defines the number of blocks reserved to transmit

Immediate Assignment messages among the PCH-AGCH blocks of a multiframe.
It should be set to 0 if no SMS-CB is activated or in case of SMS-CB with
combined BCCH, and set to 1 if SMS-CB is activated without combined BCCH.
• noOfMultiframesBetweenPaging: it defines the periodicity of a paging group
occurrence (paging group A for instance). The unit is the multiframe, and it should
be set to 6 in rural environments and to 2 or 4 in urban environments.
• nbOfRepeat: defines the number of times a paging message will be repeated by
the BTS. By setting this parameter to 3 one ensure to maximize the probability of
paging answering even in bad radio conditions.
• delayBetweenRetrans: defines the number of occurrences between 2 repetitions
of the same paging group. It should be set to 0 in order to avoid double allocation.
• retransDuration: defines the maximum time allocated to broadcast a paging
message. It should be set according to the following inequality retransDuration ≥
(delayBetweenRetrans + 1) X nbOfRepeat.
The combination of these parameters allow to delay or speed up the broadcasting for a group
of mobile and maximize the probability of reception of a paging message, but also to decrease
the number of re-emission of paging messages if the radio conditions allow it.
NSS PARAMETERS
On the NSS side, only one parameter may be taken into account, GSM_PAGING_RETRY
which allows to repeat the Paging Command message on the A interface.
It is possible to choose between paging repetition at a BSS or a NSS level: one can prefer
NSS paging repetition or be dependent on an other vendor NSS paging repetition. In this case
BSS paging repetition parameters should be set accordingly.
NSS repetition can bring some improvements, as described in chapter Field examples: NSS
paging repetition tuning.
Nortel confidential

TDMA CONFIGURATION
Depending on if the CCCH is combined or not on the cell, the number of frames dedicated to
the paging are different: it goes from 3 CCCH occurrences in the combined case to 9
occurences. The TDMA configuration can drastically reduce the number of free channels
available for paging messages and thus should be taken into account for the number of
repetition.
See also chapter Consequences of the TDMA Model.
6.31.2 FIELD EXAMPLES: BSS PAGING REPETITION TUNING

The optimal way to optimize the number of repetition on a network (BSS side) is to proceed to
a step by step analysis of the number of paging messages successfully sent at the first
attempt, successfully sent at the following attempts, and all the paging messages discarded.
LAC Traffic (Erl) Page now Page 1w Page 2w Page more Paging discarded
10000 305 8011 132 2 0 422
17500 401 12550 91 2 0 1
18000 500 17625 437 8 1 7205
18100 441 16397 358 8 1 1182
18500 422 16118 174 3 0 1364
With this example we can see that 3 LACs show a large number of discarded paging
messages. At this step we can not determine if those discarded messages have been
successfully sent previously or not (the repetition take place eventhough the mobile already
answer).
The first step will be to audit the type of the BTS and the TDMA configuration. In case the
CCCH is combined to the BCCH, a reconfiguration should be plan.
Then the number of repetition on the NSS side should be taken into account, and set to 0 if it
is not the case (in this particular case the GSM_PAGING_RETRY was already set to 0)
Finally the BSS parameters could be checked and compared to the recommended values (and
especially the noOfMultiframeBetweenPaging that depends on the environment), before trying
to tune the nbOfRepeat, and the retransDuration.
If good radio conditions are met on the cell, one could try to decrease the nbOfRepeat very
cautiously, and subsequently the retransDuration which is correlated.
Parameter September’s value January’s value

noOfBlocksForAccessGrant 1 1&5
noOfMultiframesBetweenPaging 5 5
nbOfRepeat 3 0
retransDuration 10 3
delayBetweenRetrans 0 0
The number of repetition has been set to 0, and the restransmission duration down to 3. Other
parameters were still at recommended value.
Nortel confidential

In that particular case, the decrease was done because good radio conditions were met. We
can observe a very good improvement on the number of paging messages discarded, without
affecting the QoS (traffic and paging success).
LAC Traffic (Erl) Sum of Page now Page 1w Page 2w Page more Paging discarded
10000 337 1808577 1671 3 0 0
10200 246 990583 1693 14 1 0
17500 469 2378638 3463 14 0 0
18000 396 1265792 6449 87 0 0
18100 392 3605562 37715 278 8 0
18200 634 3270930 25417 384 17 0
18500 399 1711766 1837 7 0 0
From a BSS tuning point of view, the nbOfRepeat has a major influence on the paging queue.
Modifying this parameter is a good way to optimize the number of paging messages, as long
as good radio conditions are met.
6.31.3 FIELD EXAMPLES: NSS PAGING REPETITION TUNING
1800 1.60%
1600 Action 1 Action 2 1.40%

1400 1.20%
1200
1.00% Call Drop(Include C1164/17)
1000
0.80%
800 System Call Drop
0.60% Rate(Include C1164/17)
600
400 0.40%
200 0.20%
0 0.00%
26
27
28
10
1
2
3
5
6
7
8
9
4
3/
3/
3/
3/
3/
3/
3/
3/
3/
2/
2/
2/
3/
That field example shows the good impact of NSS Timers tuning on the Call Drop ratio.
Action 1 corresponds to a reduction of timers T305 and T308 from 30 to 1second and Action 2
corresponds to a reduction of timer T102 from 5 to 30 seconds.
(T305: started when a DISCONNECT message without progress indication is sent and
stopped when the network has received a RELEASE or DISCONNECT message; T308:
started when a RELEASE message is sent and stopped when the network has received a
RELEASE_COMPLETE or a RELEASE message; T102: used by MSC−A when a
HANDOVER_COMMAND message is sent and stopped when a HANDOVER_COMPLETE
message is received)
Nortel confidential

6.32. AMR FIELD FEEDBACK

AMR is the new feature introduced in release v14.3 in order to:
• Increase voice quality in degraded radio conditions,

• Increase radio capacity due to robustness of Full Rate AMR and introduction of
Half Rate channels.
The principle of this feature is described in chapter AMR - ADAPTATIVE MULTI RATE FR/HR,
and this chapter try to quantify the gain of AMR regarding the two objectives listed above.
Note: most of the findings in terms of monitoring and feature optimization are based on the
experience gained during the VO activity and the rollout phase that followed. As the Legacy
L1m was activated for most of these testings, we recommend and support today the AMR
feature with this L1m algorithm enabled.
6.32.1 NSS INTERACTION
MULTIPLE VOCODER AT MSC SIDE
Field tests have raised in some cases an issue on handovers from one channel type to
another channel type.
This issue was due to a MSC parameter belonging to OFCVAR table :
multiple_vocoder_support. This parameter was positioned on “on_no_changes” and that
prevented the MSC to be able to change the channel type if the target cell of another BSC did
not support the channel mode of the originating cell.
This behavior was fixed by setting multiple_vocoder_support to "on_with_changes" thus
handovers from AMR HR channels could go to EFR.
CHOSEN CHANNEL BETWEEN MSC AND BSS
Another issue was raised concerning the following parameters located on the signallingPoint
object of the BSS that have to be set to “TRUE”:
• chosenChannelAsscomp
• chosenChannelHoReq
• chosenChannelHoPerf
Indeed, the GSM specifications (3GPP TS 48.008) precise that the chosen channel shall be
included in the message between the BSS and the MSC (ASSIGNEMENT COMPLETE,
HANDOVER REQUEST ACKNOLEDGE, HANDOVER PERFORMED) at least when the
channel rate/type choice was done by the BSS.
Issues have been noticed on the field with other vendor Core network when those parameters
are not properly set, in this case in particular it was impossible to establish half rate calls.
Nortel confidential

6.32.2 AMR THEORETICAL PERFORMANCES

The following figures show theoretical AMR FR and HR performances vs. EFR. They are
usually expressed in terms of MOS or DMOS vs. C/I. A new voice quality indicator has been
defined, the TEPMOS, which is recommended for AMR calls.
VOICE QUALITY INDICATORS
MOS and DMOS

MOS or DMOS are subjective notes given by people who compare the quality of the original
(ACR tests) or a reference signal (DCR tests) and the signal at the output of the coder.
MOS and DMOS are always a value between 1 and 5: a value equal to 1 means that the
listening is unintelligible and a value equal to 5 means that the two signals are the same
(which is never the case). One estimate that a value higher than 4 corresponds to an excellent
voice quality. A good quality corresponds to a MOS higher than 3.5 and a fair quality is higher
than 3-3.2.
TEPMOS
TEPMOS stands for theoretical extrapolated PMOS. It is theoretical because it is based on
simulations in order to translate FER to PMOS values. It is extrapolated, because TEPMOS
weight usage of each one of different AMR codecs PMOS in order to establish AMR
TEPMOS.
AMR FULL RATE
The figure below shows the performances recorded for the best AMR Full Rate codec mode
for each C/I, with the corresponding performance of EFR (and also FR in car noise conditions)
and the related AMR performance requirement (curve Sel. Requir.)
Nortel confidential

The figure shows that the combination of all 8 AMR FR codec modes allows to:
• provide a robust quality down to 4 dB C/I in Clean Speech, which means up to 6

dB improvement compared to EFR,
• provide a robust quality down to 4 dB C/I in Background Noise, which means also
significant improvement compared to EFR and GSM FR.
In other terms also, capacity can be increased by operating a tighter frequency reuse pattern
or by operating a higher fractional load, which is equivalent in the two cases to a higher
number of Erl/km2/frequency.
AMR HALF RATE
Here one compares the performances recorded for the best AMR Half Rate codec mode for
each C/I, with the corresponding performance of EFR, GSM FR and HR speech codecs and
the related AMR performance requirement (curve Sel.Requir.)
This figure shows that the combination of all 6 AMR HR codec modes allows to:
• provide a good quality down to 16 dB C/I in Clean Speech, always significantly better
than the GSM FR and GSM HR,
• provide good performances in Background Noise down to 16-13 dB C/I, equivalent to
GSM FR otherwise.
It means that AMR HR offers the possibility to have in good radio conditions a capacity
increase in term of Erlang (two users can be mapped on the same TS instead of one) keeping
comparable quality of a FR speech.
Nortel confidential

QUALITY PERCEPTION SYNTHESIS
The above graph shows the different AMR FR codec performances taken individually in terms
of PMOS for a given propagation profile (TU3iFH). The AMR Link Adaptation principle will
consist in choosing according to the radio conditions (C/I measured) the appropriate codec in
order to provide the best PMOS quality. The below graph provides a simplified view of the
voice quality perception (Excellent to Bad quality) between the EFR (12k2 fixed codec) with
the AMR FR and AMR HR Link adaptation.
C/I 16 dB 13 dB 10 dB 7 dB 4 dB 1 dB
RxQual 3 (0.8%<BER<1.6%) 4 (1.6%<BER<3.2%) 5 (3.2%<BER<6.4%) 6 (6.4%<BER<12.8%) 7 (BER>12.8%)
EFR Quality Excellent Good Fair Poor to Bad
FR-AMR (LA) Quality Excellent Good Fair Poor to Bad
HR-AMR (LA) Quality Excellent Good Fair Poor to Bad
SACCH FER 1% 3% 20% 50%
FACCH FER 1% 3% 20% 50%
It is interesting to see that:
• down to the limit of acceptable SACCH/FACCH BLER (20%), HR and EFR

provide the same level of voice quality (Poor to Bad), slightly better though for
EFR. This has driven us in our recommendation of maximizing HR penetration in
areas where RLT is not the limiting factor
• above the 20% of SACCH/FACCH BLER, voice quality for AMR-FR is still fair
which may lead to potential drop calls while the speech is still fair from a user
perspective. This has driven in our recommendation to extend the radio link
timeout timer in order to compensate somehow the user behavior in places where
the coverage or low C/I are the limiting factors
Nortel confidential

6.32.3 AMR ENGINEERING STUDIES
DEFINITIONS
ENGINEERING TESTS CHARACTERISTICS
• DL results are only presented

• DL collected traces are given by two TEMS T62u mobiles which are ran in parallel,
one set to AMR mode and the other to EFR mode connected to same PC
• Both mobile were connected to same and external antenna
• All engineering tests presented in this document were done at night during
maintenance window
• 2 hours tests were done in order to collect maximum samples as possible in a
wide range of radio conditions
• Cells were bared to avoid having other users than test mobiles in victim cell
• Both incoming and outgoing HO for EFR and AMR calls were disabled
• DTX was de-activated
• A VQ server was called and used as a “speech player” with a continuous
sequence of speech for DL measurements
• Different adaptation codec tables were used to compare adaptation thresholds on
performances
ADAPTATION CODEC SET TABLE
The link adaptation consists in adapting the “best” codec to speech frames according to the
link quality estimated by both entities. Each codec mode, whether used in Uplink or Downlink,
and whether used for FR or for HR channel, corresponds to one couple of threshold and
hysteresis. The value for these couples depends also on a set of factors: MS speed, FH or no
FH, propagation profile. Finally, all these parameters associated to the choice of the codecs
are compiled into a table called amrAdaptationSet table. It is composed of 4 subtables each
dedicated to a combination of channel type and link direction. In order to optimize the
adaptation, NORTEL has implemented 3 sets of pre-defined tables (optimistic, pessimistic and
typical settings) plus one set of tables which is user-defined. The
parametersamrDlFrAdaptationSet, amrDlHrAdaptationSet, amrUlFrAdaptationSet,
amrUlHrAdaptationSet allow the operator to define an amrAdaptationSet table independently
for FR and HR mode and for DL and UL. Moreover, this allows more flexibility in the
amrAdaptationSet table management since updating the optimized tables requires a change in
the Bsc Data Config.
LCAUTION! Please note that all values expressed in the tables hereunder are in dB.
Nortel confidential

TYPICAL TABLE (not modifiable)
uplink downlink
< 4 FH
5k9 to 4k75 8 2,5 3,5 2,5 4
6k7 to 5k9 10 4 5 4 5,5
FR thresholds
10k2 to 6k7 12,5 6,5 7,5 6,5 7,5
12k2 to 10k2 17,5 12,5 12,5 12,5 13,5
FR hysteresis 2,5 1,5 2 1,5 2
5k9 to 4k75 12,5 10 10,5 10 11
HR thresholds 6k7 to 5k9 14 12 12,5 12 12,5
7k4 to 6k7 19 17 17,5 17 16,5
HR hysteresis 3,5 2 2 2 3
OPTIMISTIC TABLE (not modifiable)
uplink downlink
< 4 FH
5k9 to 4k75 5,5 2 2,5 2 4
6k7 to 5k9 6,5 3,5 4 3,5 4,5
FR thresholds
10k2 to 6k7 10 5,5 6,5 5,5 7
12k2 to 10k2 15 12 11,5 12 12
5k9 to 4k75 9,5 8,5 9 8,5 10,5
HR thresholds 6k7 to 5k9 10,5 10,5 10,5 10,5 12
7k4 to 6k7 15,5 15,5 15,5 15,5 17
HR hysteresis 3,5 3 3 3 2
PESSIMISTIC TABLE (not modifiable)
uplink downlink
< 4 FH
5k9 to 4k75 11 6 7 6 5
6k7 to 5k9 12,5 6,5 8 6,5 6
FR thresholds
10k2 to 6k7 16 9,5 11 9,5 8,5
12k2 to 10k2 20,5 14 16 14 13,5
FR hysteresis 3 2 2 2 3
5k9 to 4k75 14,5 13 13,5 13 12,5
HR thresholds 6k7 to 5k9 15 13,5 14 13,5 13
7k4 to 6k7 19 18,5 19 18,5 18
HR hysteresis 4,5 2,5 2,5 2,5 3
Nortel confidential

AMR OPTIMIZED TABLE (customized)
uplink downlink
< 4 FH
5k9 to 4k75 5,5 2 2,5 2 4
6k7 to 5k9 6,5 3,5 4 3,5 4,5
FR thresholds
10k2 to 6k7 10 5,5 6,5 5,5 7
12k2 to 10k2 19,5 14 16 14 17,5
5k9 to 4k75 12,5 10 10,5 10 12,5
7k4 to 6k7 18 18,5 19 18,5 19
HR hysteresis 2 2,5 2,5 3 3
AMR 10k2 ONLY TABLE (customized)
uplink downlink
< 4 FH
5k9 to 4k75 0 0 0 0 0
6k7 to 5k9 0 0 0 0 0
FR thresholds
10k2 to 6k7 0 0 0 0 0
12k2 to 10k2 19,5 14 16 14 17,5
FR hysteresis 0 0 0 0 0
5k9 to 4k75 12,5 10 10,5 10 12,5
7k4 to 6k7 18 18,5 19 18,5 19
HR hysteresis 2 2,5 2,5 2,5 3
LCAUTION!
In the case of the customized tables defined via the BSC Data config, values are to be entered
in ½ dB. For example the threshold to switch from a 12k2 codec to a 10k2 codec in the case of
a slow MS non hopping in the table above should be 39 in the BSC Data config to express a
C/I of 19,5 dB. Note: The AMR threshold set in the bscdataconfigeditor -- labels 81--125
should to be set with a value small than 63.
RATSCCH CODING SPECIFICITY
When an Assignment Command or a Handover Command message is sent from the BSC to
the BTS in order to provide all AMR L1m and codec mode adaptation informations the
hysteresis described in the adaptation codec table is coded on 4 bits, hence can take values
from [0 to 7.5] dB with steps of 0.5 dB.
Now when the Active Codec Set has to be modified via a RATSCCH message, the coding of
that hysteresis becomes:
Bit 34 … 32 31 30 29 … 28 27 … 20 19 … 18 17 … 12 11 … 6 5…0
Value 001 1 1 ICM ACS HYSTc THRESH3 THRESH2 THRESH1
Nortel confidential

One can see that in this case the hysteresis is coded only on 2 bits (as recommended by the
GSM Rec 05.09) thus can only take 4 different values, that are:
Set value at the OMC-R Coded value in the RATSCCH Corresponding value
0 / 0,5 / 1 / 1,5 00 1 dB
2 / 2,5 01 2 dB
3 / 3,5 10 3 dB
4 / more than 4 11 4 dB
Please note that this case is only applicable in downlink AND for a change of Active Codec
Set via a RATSCCH message (refer to RATSCCH management).
Consequently, if one wants to use the customized values in the amrAdaptationSet table
(parameter amrXXYYAdaptationSet = 3) it is recommended to set cunningly the related
downlink hysteresis in the customized AMR adaptation table,that is to say in order to respect
the only 4 values that hysteresis can take via a RATSCCH message.
Nortel confidential

AMR VERSUS EFR
AMR FR VS EFR IN BCCH LAYER IN INTERFERENCE LIMITED

ENVIRONMENT
The purpose of this test was to characterize AMR performances in a degraded radio
environment to show AMR codec performance on the BCCH layer, but it also included
comparative results with EFR performance with different adaptation sets.
Same BCCH frequency was set for 2 neighboring cells in order to create interference to the
victim cell, and the Pessimistic default table has been compared with a customized table
proposed by the operator.
Observations:
• AMR gain is critically dependant on voice quality target. A trade-off capacity-voice

quality is found. The lower the voice quality target, the higher is capacity increase
available. This capacity increase could be obtained by increasing network
frequency load.
• For a given radio condition, TEPMOS from AMR is better than EFR. AMR
increases voice quality or area reliability is improved.
• In very good radio conditions, e.g. more than 14 dB, lower codecs present worse
performances than 10k2 FR
• Adapting to lower codecs in a higher C/I tends to slightly decrease voice quality
but going faster to lower codec in bad radio conditions improve the voice quality
performance in bad radio conditions.
Note: higher gain is found in AMR in frequency hopping layer than in non-hopping BCCH
layer, and frequency diversity adds an extra gain to lower codec robustness.
AMR HR VS EFR IN BCCH LAYER IN INTERFERENCE LIMITED

ENVIRONMENT
The purpose of this test was to evaluate AMR HR performances and to compare them with
EFR. Calls were established in very good radio conditions and algorithms to intracell HO from
HR to FR were set impossible to be triggered (setting amrHRtoFRIntracellCodecMThresh
target to 4k75 AMR HR).
Observations:
• Test results show how AMR HR presents a very good performance with regard to
EFR in good radio conditions. Degradation could be quantified from 3.7 to 3.5
TEPMOS which is neglected by human ear. Moreover, when radio conditions are
degraded, AMR HR performance keeps a good performance and even at 3
TEPMOS voice quality target can presents a better performance than EFR
• This test shows that it would be perfectly possible, when radio conditions allow it,
to maximize AMR HR penetration and obtain interesting performance comparable
to EFR with the benefit of more resource availability thanks to HR usage
Nortel confidential

AMR FR VS EFR IN COVERAGE LIMITED ENVIRONMENT
The purpose of this test was to evaluate the coverage enhancement with AMR feature and to
compare its performance with EFR calls.
Radio Link TimeOut timer was extended to 64 to allow increasing coverage as much as
possible. One mobile was set in AMR FR only mode while another was logged on EFR mode
only. Calls were dragged on a coverage limited areas to the limits of the cell. Intercell
handovers were disabled to hold them in serving cell. Low ranges of RxLev signal samples
were obtained. No interferences are found since tests were done during maintenance window
and no traffic was detected at this hour.
RxLev measurements are suitable for performance comparison since no interference were
found in coverage limited environment.
Observations:
• More than 3 dB coverage gain can be obtained using low AMR codecs in low
signal strengths.
EXECUTIVE RESULTS
In summary of these tests:
• there is definitely a trade-off between AMR gain versus voice quality. This will be
up to the operator to define it
• PMOS target for voice quality impacts critically AMR gain
• Adaptation codec set table impacts voice quality and AMR gain
• Low codec usage in good radio condition degrades voice quality
• AMR FR could achieve a gain of 3-3.5 dB on BCCH layer
• AMR FR could achieve a gain of 3.5-4 dB on frequency hopping layer
• AMR FR could achieve a gain of 3-4 dB on coverage could be obtained
• AMR HR presents a comparable voice quality compared to EFR
Nortel confidential

6.32.4 HALF RATE PENETRATION ANALYSIS

AMR penetration is a trade-off between quality target for HR users and capacity required. The
more voice quality the operator is ready to sacrifice, i.e. the lower the C/I thresholds is set to
handover from HR to FR, the more HR capacity would be.
HR penetration depends on different AMR HR related parameters: adaptation table, HR to FR

codec target and HR direct allocation.
HALF RATE DIRECT ALLOCATION
Even if intracell handover from FR to HR and from HR to FR are found to be efficient, it is

important to avoid doing more intracell handovers than necessary. This is why it is important to
set HR direct allocation RxLev target to the correct figure to avoid that a call in very good radio
conditions is allocated in FR since it will be sent to HR immediately after because of radio
conditions.
In order to set these parameters in UL and in DL (amrDirectAllocRxLevUL,
amrDirectAllocRxLevDL), a Call Path Trace analysis could be done based on the distribution
of the amrHRtoFRIntracellCodecMThresh vs. RxLev, bearing in mind also that codec requests
depends also on the table that is being used.
HALF RATE SETTINGS
AMR adaptation tables are the main/critical parameter to define HR penetration.
Adaptation table thresholds define radio condition where adaptation from AMR FR to AMR HR
and AMR HR to AMR FR occurs. Optimistic table defines low C/I (degraded radio conditions)
in order to handover from HR to FR and also a low target to handover from AMR FR to HR.
Thus, HR penetration is favored. When pessimistic tables are set, C/I to handover from HR to
FR are high, so quickly after radio is degraded, FR is requested.
AMR adaptation table and HR to FR intracell handover target are highly related since once
both parameters are defined, a target C/I is established and thus, radio conditions where HR is
used are set, e.g. in DL, it is the same to set a pessimistic table with a HR to FR target to 5k9
than a typical table with a target 6k7.
Two main parameters are related to HR to FR handover: Adaptation table and

amrHRtoFRIntracellCodecMThresh while main parameter for FR to HR is the adaptation table:
• Parameters like n and p from the (n,p) voting algorithm are found to have a limited
impact on intracell HO ratio. In order to maximize overlap, it is recommended to
set nCapacityFRRequestedCodec to 100% of P and nHRRequestedCodec to 50%
of pRequestedCodec
• The intracell codec target for HO from FR to HR is hardcoded and set to 12k2 FR
codec. Therefore, this threshold is fully defined by the choice of adaptation table.
It is important to check that thresholds for intracell HO HR to FR and FR to HR are correctly
set in order to avoid ping-pong handover. It should be check that C/I threshold to adapt from
HR to FR is lower than FR to HR and a good overlapped zone is found in order to avoid ping
pong intracell HO due to wrong parameter settings.
Nortel confidential

The figure below is a typical example of a correct setting to guarantee a good overlap for DL
intracell handover:
HR to FR FR to HR
6k7 HR 12k2 FR
17 dB C/I BS 20,5 dB C/I
As AMR HR penetration is a trade-off between radio conditions and voice quality, it is highly
dependent on environment since if high interference is found, penetration is only obtained if
voice quality is highly jeopardized. Handovering to FR mode too early because parameter are
too constraining would provide benefit of HR capacity. On the other hand, handovering to FR
mode too late jeopardizes user voice quality as lower codecs might be used too long in lower
C/I ranges.
Using pessimistic table threshold and 7,4 HR as amrHRtoFRIntracellCodecMThresh, intracell
HO HR to FR is done as soon as possible when radio conditions starts to be degraded.
Normally this case brings a low HR penetration, around 20 to 25% HR penetration (highly
dependent on radio/environment conditions). Increase of HR penetration is obtained setting a
lower codec for HR to FR intracell handover (30 to 35% HR penetration can be expected). A
more aggressive strategy is to change adaptation set to more optimistic thresholds which
would bring a higher HR penetration (50 to 55% HR penetration can be expected).
Nortel confidential

HALF RATE MAXIMIZATION ANALYSIS
Considering the graph of speech MOS vs C/I, one can see that AMR-HR with link adaptation
is in theory slightly worse than EFR. AMR-HR provides fair quality down to 9dB while EFR can
go down to 7 dB for the same quality. But both, AMR-HR and EFR are quite poor below 7dB
while FACCH and SACCH performance are in a range where the BLER is not very good but
still can be handled. This would show that an AMR-HR and EFR user would have “roughly” the
same behavior at cell edge, either will drop or will attempt to release the calls as the quality
will degrade.
In urban area, where the limiting factor is not necessarily the coverage but the C/I, it has been
tested to maximize the HR penetration in order to analyze the drop performance.
• From a drop performance perspective, AMR FR only has degraded the statistics;
but introducing the link adaptation using the full-set of lower codecs did for sure
bring a improvement in terms of voice quality. As soon as HR has been activated
with a setting maximizing its penetration to a level of 80%, the drop indicator did
go downward to a level similar to what it was before.
• From a voice quality perspective, there has been no real improvement here as the
objective was to lower down the drop rate.
• From a blocking view, HR maximized did improve the blocking rate for call
initiation and handovers.
Maximizing HR in the urban area could definitely reduced the drop performance to the level it
was in EFR only and brought big improvement in terms of resource availability related to traffic
mobility
In order to maximize that HR penetration, one can either:
• Reduce at maximum the level for the direct allocation in HR

• favor FR to HR intra cell handover by setting nFRRequestedCodec to 1
• avoid HR to FR intracell handover by setting amrHRtoFRIntracellCodecMThresh
to 4k75
Of course, these settings are not standard and the maximization of HR could be loosen by
changing these parameters along with the intracell ping-pong protection Concerning the
adaptation table, it is recommended to use the customized one as HR becomes poor very
quickly for low C/I lower.
Nortel confidential

6.32.5 AMR USER BEHAVIOUR EFFECT

AMR has been implemented to give a better voice quality robustness against radio condition
degradation via lower codec usage. Thus, when radio is degraded voice quality is still
acceptable for human perception.
On the other hand, signaling channels have traditionally given better performance than voice
channels since they are transmitted in a more robust channel and because retransmission are
allowed. Erroneous packets are more critical for voice quality degradation than signaling,
which can be retransmitted a certain time until call is released before it is considered lost, i.e.
via RLT counter.
Signaling has been found to be, in some specific cases, more constraining than AMR low
codecs. This means that in some cases, while signaling is not correctly received and thus RLT
counter is decreasing due to radio conditions, AMR low codecs are able to still give a fair voice
quality. This effect impacts critically GSM networks KPI since user behavior becomes key
factor. In the same radio degraded condition where signaling is not correctly received (or even
before for EFR user!), an EFR user would realize its voice quality becoming poor, hangs up,
release the call. This release would be pegged as a normal clearing of call from a counter
perspective. On the other hand, AMR users do not realize of this radio condition degradation
since AMR low codecs allow a fair voice quality at low C/I. AMR user drags the communication
until RLT counter reaches 0 or when it tries to hang up, one of the links is lost. This effect has
been found to increase call drop ratio from GSM networks.
Good Radio Conditions

AMR EFR
AMR EFR
Very Good Very Good

Voice Quality Voice Quality
Very Bad Radio Conditions

EFR
AMR
Signalling Channels Traffic Channels
Good Voice Quality Bad Voice Quality
Signalling channels risks to be lost User Hangs Up

User keeps talking since VQ is good Correct Released call
Call drop is increased No Call Drop
LCAUTION!
Thus, from a counter perspective, this kind of tricky situation is seen as a dropped call in AMR,
while it is being pegged as a normal clearing for a EFR user.
This problem is intrinsic to AMR standards. While waiting for AMR standard to be improved,
one of the work-around is to increase radioLinkTimeout which maximize probability to recover
radio conditions without degradation of AMR user perception or leave enough time to clear
properly the call when it starts to be very poor in terms of voice quality.
Nortel confidential

T200 with RLT drops have found to be related. It can happen that a user which realizes radio
condition has been degraded tries to hang up when one of the links is lost. This will provoke
that network start its procedure to release the call but it is never correctly released since one
of the links messages are never correctly released. Thus, T200 drops are pegged. It has been
found that when RLT is increased, RLT drops are decreased while T200 drops are slightly
increased.
In order to validate somehow this effect, EFR and AMR tests have been performed in
coverage limited zone. Some monitoring findings supported also that phenomena.
Two mobiles were running in parallel in a coverage limited zone. Both mobiles were running in
a car moving at 50km/h connected to a single external antenna. Without user behavior
intervention, both calls end at the same time. RLT (SACCH performance) is independent from
speech codecs, EFR and AMR call ends at the same time.
Nortel confidential

6.32.6 VOICE QUALITY ANALYSIS

AMR improves voice quality. Figures below show FER evolution depending on speech codec.
U p lin k F E R e v o lu tio n
2 .2 5 %
2 .0 0 %
1 .7 5 %
AMR power control benefit: 0.5%

1 .5 0 %
1 .2 5 %
AMR link adaptation benefit: 0.5%

1 .0 0 %
0 .7 5 %
High half rate
F E R U L S ta n d a rd F R
voice quality
FER U L AMR FR
0 .5 0 %
FER U L AMR HR
0 .2 5 %
0 .0 0 %
1 0 -M a r
1 2 -M a r
1 6 -M a r
2 3 -M a r
2 7 -M a r
2 9 -M a r
3 1 -M a r
1 4 -M a r
2 5 -M a r
2 5 -F e b
2 7 -F e b
2 9 -F e b
2 8 -J a n
3 0 -J a n
2 -M a r
8 -M a r
4 -M a r
3 -F e b
6 -M a r
1 -F e b
• AMR FR FER is significantly lower than EFR FER

• EFR FER is also improved due to AMR L1m power control aggressiveness
• AMR HR FER is very low since it uses robust codecs and it is used in very good
radio quality
• When AMR HR is activated, AMR FR FER increases since AMR FR is used in
worst radio conditions than AMR HR
• When AMR HR is activated, less interferences are found since AMR HR uses half
time radio resources and thus, EFR FER slightly improves.
USE OF TEPMOS TO ESTIMATE VOICE QUALITY IN AMR ONLY
The TEPMOS indicator has been successfully validated for AMR traffic with the proposed link
adaptation tables. The indicator provides a very good match versus the pMOS as calculated
through the standardized PESQ algorithm. The chart below shows the validation for AMR-FR
in TU3 with the typical table.
Nortel confidential

Note that the voice degradation caused by frame losses on the terrestrial links or by the
perturbations induced during handovers is not captured by the indicator.
The TEPMOS enables to measure the impact of AMR tuning on the user perceived voice
quality in various configurations and thus to find ore optimal QoS tradeoff: choice of the
adaptation table, AMR-HR allocation triggers, AMR based on traffic, Interference
cancellation...
However with EFR, the indicator is less accurate. One reason is that the TEPMOS relies
mainly on the weighted FER per AMR codec mode. In AMR each codec mode is used in a
limited C/I range. For EFR the same encoding is used over the whole working range limiting
the accuracy. A second reason is that with EFR, class 2 bits are not protected. Thus the frame
erasure rate with EFR does not reflect the voice quality degradation occurring when a speech
frame is correct (class 1 bit OK) and some class 2 bits are erroneous. With AMR-FR however
there are no class 2 bit defined. Thus the FER or the TEPMOS reflect more accurately the
perceived voice quality with AMR.
Nortel recommends thus using the TEPMOS with EFR cautiously. Variations in EFR TEPMOS
are representative of different voice quality perception enabling comparison between cells or
TDMA with EFR traffic. However EFR and AMR TEPMOS shall not be used to compare the
voice quality between the two modes.
Nortel confidential

6.32.7 AMR MONITORING

The purpose of this AMR monitoring section is to provide the reader with observation findings
made during the VO and onwards on different live networks.
From a tuning and optimization perspective, the AMR feature is not as straightforward as
another feature mainly because of the known limitations of the standards, some erratic mobile
issues and the dependency with the terrain and user profile.
Nevertheless, with all the efforts made on the optimization in several challenging clusters, it is
possible today to provide general guidelines for the tuning and optimization of the feature
according to the environment and customer’s objectives.
Most of the results and trends presented hereafter are based on the monitoring made on
different live areas. Each area having specific characteristics in terms of:
• Design and engineering strategy

• Spectrum available
• Current traffic profile (numbers, mobility, offered services…)
• Field morphology
• AMR mobile penetration
For these above reasons, there is no comparison and absolute trends to be considered here
when deploying AMR feature. The purpose of this section is to provide some guidelines in
terms of monitoring observation and what are the contributors of the changes that could be
observed.
The performances of the AMR feature were evaluated regarding newly dedicated counters:
• TCH resource: AMR FR and HR allocation, assignment, resource usage,

connection duration
• Handover: AMR FR and HR HO required, executed, completed and failures
• Drops: AMR FR and HR drops per cause radio, LAPD or Others
• L1M: AMR level, quality, power control, C/I…
• Additional counters related to AMR specific mechanisms such as the codec
distribution, FER, RATSCCH failures etc…
There is also a huge set of already existing counters that are being pegged whether or not the
call is in FR, EFR or AMR. All these counters are mostly related to the allocation and the
handovers procedures. For more details on these counters, please refer to [R29].
OVERALL FINDINGS
After having successfully tested all the procedures and the specific algorithms related to the
AMR feature throughout numerous testing in lab and live, AMR have been deployed
progressively on live areas under different environments:
• rural areas with low density of urbanized areas where coverage was the limiting
factor
• suburban areas with spot of dense traffic and where the interference was definitely
the constraining factor
• urban to dense urban areas where interference and coverage (indoor) limitations
are mainly the constraining factors. Traffic was also a important constraint.
Nortel confidential

With the AMR activation over different clusters, it has been proven that all the usual indicators
like the resource allocation, the call establishment, the blocking were performing within
standard ranges with the exception for the call drop indicator.
Many efforts have then been deployed to address this drop call concern. Nortel has been
through the testing of different timers impact (T200, NY1, RLT, and T3103) and the changing
of some key elements in the AMR algorithm with always the objective to isolate potential
software issues. None of them did bring huge improvements in reducing the drop call
performance though but many findings were interesting and kept for future settings (TDMA
priority, timer T3103 extension, RLT extension). In parallel to these efforts, several papers
were submitted by different providers and customers to the GERAN meeting indicating
potential issues with actual AMR performance vs signaling performance, i.e. the improved
lower codec rates provide voice robustness in areas where signaling channel fails to perform
reliably (SACCH and FACCH). Call are being dropped while voice quality is still acceptable.
Beside this, we have also observed some differences between EFR and AMR mobiles in their
estimation of RxQual under severe interference and DTX situations which may, in some
cases, lead to some delays in the decision of handovers.
Even if the main driver of all the AMR monitoring activities is the drop call performance for
which the variations will depend upon the environment, the mobile penetration and the traffic
mobility, the feature has proven many benefits in terms of coverage, voice quality and
capacity.
Nortel confidential

COVERAGE LIMITED AREAS
OBSERVATION
In this type of environment, RLT drop contribution is usually much higher because calls are
being dragged at cell edges and the overlap between neighboring sites is less important than
in urban areas. The T200 drops can be also higher than usual but in a lesser extent than the
RLT. T3103 drops are less significant than areas where the overlap is more dense since they
are directly related to users mobility.
In such rural area, RLT drops (and T200 with a less extent) represent more than 45% of the
drops while T3103 represents less than 25%. Activating AMR increase the dropped calls with
two main contributors, the RLT and the T3103.
Extend the DL RLT timer and keep the UL to its original value would lead to a reduction of the
drop contribution on RLT cause. The timer extent cannot fully compensate the robustness of
the codecs vs. SACCH performance when C/N becomes critical.
HR activation does not brig any improvement in the drop performance. In an area where the
limiting factor is the coverage and not the traffic, there is no real benefit to have HR activated
unless necessary. The excess of T3107 drops is not necessary here.
RECOMMENDATION
In coverage limited areas with low traffic (rural areas) Nortel recommend to avoid using as
much as possible the low codecs in order not to experience any “user behavior” effect. Usage
of the optimistic table or a customized table avoiding at least the 4k75 codec is necessary.
The DL RLT (radioLinkTimeout) should be increased subsequently to a minimum of 32
SACCH periods. To a certain extent it could be interesting to customize if possible a “10k2
only” table for such environment and keep the RLT to 32 as the 10k2 is bringing a 1-2 dB
coverage gain vs EFR.
Concerning HR, one should look at the real traffic carried on a cell level to decide whether or
not capacity is required. In a general manner, HR should be disabled in such environment as it
does not bring any extra benefit. T3107 drops would then be avoided.
From a handover perspective, it is recommended to change the timer T3103 (t3103) to a value
of 9 seconds in order to offer a wider window of good completion of the procedure at cell edge
where the quality might be poorer.
INTERFERENCE LIMITED AREAS
OBSERVATION
In this kind of environment, T3103 drops are dominant; it represents more than 45% of the
drops, while RLT is around 25%. This ratio remains the same before and after AMR activation
as RLT drops can also be a consequence of T3103 increase: a handover that fails and come
back to its original channel in worst radio conditions than before may drop on RLT.
Nortel confidential

The activation of HR in this environment does not affect the overall drop indicator. The T3107
increase is due to the substantial increase of intra cell handover that occur when HR is
activated. That activation usually show some improvement of the T3103 as some intercell HO
can occur now in better radio conditions. However, the slight improvement of the T3103 drops
is compensated by an increase of T3107 which makes the overall drop not being modified.
RECOMMENDATION
In urbanized environment, potentially facing spots of interference, it is advisable to enable the

legacy HO in order to perform HO on Quality criteria (RxQual) instead of CMR (AMR
algorithm).
For the same reasons, it is also recommended to have a window of decision for the rescue HO
short enough to react for signal degradation. It has been observed in some specific situations
and interfered areas differences in the RxQual estimation between EFR and AMR mobiles.
If the volume of handover is higher after AMR activation:
• Make sure that the allocation priority threshold (allocPriorityThreshold) is well set
on the target cells
• Extend the T3103 timers (t3103). Usually set to 5s, when this timer is set to 9s, it
has been observed some improvement on the HO failures
It is also advisable to make sure that TDMA priorities are well set (frAMRPriority &
hrAMRPriority). As the allocation in AMR does not take directly the level of interference in the
resource classification, a higher priority on hopping TDMA can be set for AMR allocations in
order to favor hopping layers.
In such environment, it has also been observed that increasing the HR usage may decrease
the drop rate to normal values as from a MOS perspective, HR and EFR are similar in low C/I
ranges. The gain in such conditions is not on the coverage but on the capacity.
CODEC 10K2 ONLY
OBSERVATION
With today’s AMR performances and according to customer objectives, there are no real
benefits to activate AMR in rural environments (or coverage limited areas). However,
implementing the 10k2 only is a trade-off between the drop call control and the slight gain in
voice quality at cell edges.
It can be seen from a drop distribution perspective that an area is coverage limited as the RLT
contribution is much higher than T3103. Activating AMR FR would increase the drop rate in a
network where the AMR mobile penetration is very important.
By changing the AMR adaptation table in such a way to limit the codec usage to only 10k2, the
drop rate would clearly decrease. Removing totally HR improve further the drop indicator to a
value very close to the EFR period prior to the AMR activation.
It can be observed that in rural areas, running AMR with 10k2 only adaptation table and no HR
does bring down the drop ratio to a certain extent to standard level. The 10k2 codec gain of
2dB in coverage can still be obtained. The DL RLT extended to 32 SACCH or more may not in
all cases compensate the signaling weakness vs the robusteness of the 10k2 at cell edges
Nortel confidential

RECOMMENDATION
Setting the AMR table to 10k2only usage requires customizing the table at BSC level (class1
change = planned outage).
Another solution would be to set the optimistic table or Nortel customized table that is detailed
above.
On cell basis, HR should be totally avoided unless necessary but with pessimistic settings
(see Nortel customized table)
RLT should be also kept to 32 in such configuration.
ISOLATED AREAS
OBSERVATION
AMR has been deployed in a cluster of sites totally or partially isolated one to each other.
In the particular case where AMR is deployed in a cluster of sites totally or partially isolated
one to each other, whether or not the area is urbanized and the level of traffic significant, the
majority of the drops will be on RLT as calls are being dragged away or indoor without
candidates (or very few).
If the radio constraints are more due to C/N here, RLT has to be extended to 32 in order to
compensate the robusteness.of the codecs at the border of cells, and it is better to activate an
optimistic table.
HR can be reasonably activated if necessary as the RF conditions are clean.
So in this particular case, one can observe:
• The overall drop level do not change before and after AMR activation
• RLT drops represent more than 40% of the drop contribution
• T200 drops represent more than 22% of the drops which is probably a
consequence of the coverage lack with releases of calls made in limited radio
conditions
• HR traffic penetration is close to 55%
• T3107 drops are quite important
• T3103 drops are low as there is no real inter-site HO. The only ones being intercell
intra site HO where overlapping should be OK.
RECOMMENDATION
As in coverage limited or rural areas, Nortel would recommend to avoid using as much as
possible the low codecs in order not to experience any “user behavior” effect with AMR. A
usage of the optimistic table or a customized table avoiding at least the 4.75 codec is
necessary.
The RLT in the downlink (user perception) should be increased subsequently to a minimum of
32 SACCH period.
Concerning HR, one should look at the real traffic carried on a cell level to decide whether or
not capacity is required.
Nortel confidential

If HR is activated, a pessimistic HR table should be implemented in order to limit somehow the

HR penetration in order not to have too much T3107 contribution and keep a fair voice quality
level. If more penetration is required, there are numerous settings that could be done from the
direct allocation, to the ping-pong protection, the change of a table or the triggering of intracell
HO thresholds.
In such environment where inter-site HOs are limited, there are no real recommendations in
terms of the intercell settings. The majority of HOs will occur intra-site where normally the
overlap between cells is reasonable.
Nortel confidential

6.33. IMPACT OF AUTOMATIC HANDOVER ADAPTATION

ACTIVATION
The Automatic Handover Adaptation feature adapts handover parameters to radio
environment of each call; taking into account mobile speed and frequency hopping with
BSCe3 (this BSS feature is available from V14.3). The objective is to minimize call drops and
bad quality transients.
The feature also has a power control adaptation mechanism in addition to the power budget
handover adaptation.
For a good understanding of this feature, please refer to the Automatic handover adaptation
chapter, or to the Functional Note TF1216 : Automatic handover adaptation ([R17])
6.33.1 RELATED PARAMETERS

All the parameters directly related to this feature are described in the Automatic Handover
Adaptation Parameters chapter, but one should also take into account the following
parameters to monitor an impact of the feature on an existing network.
selfAdaptActivation Use for activate the Automatic Handover adaptation
servingfactorOffset This attribute defines the offset linked to the serving cell, used to decrease the HO margin
neighDisfavorOffset This attribute modifies the offset linked to the neighbouring cell, used to increase the HO marging
Number of signal strength measurements performed on a serving cell, used to compute arithmetic
rxLevHreqave
strength averages in handover and power control algorithms
Number of measurement results used in the PBGT algorithm to compute the average neighboring
rxNCellHreqave
signal strength
Number of measurement reports used in short averaging algorithm on current cell for signal strength
rxLevHreqaveBeg
arithmetic average
Number of measurement results used in short averaging algorithm to compute the average
rxLevNCellHreqaveBeg
neighboring signal strength
Number of arithmetic averages taken into account to compute the weighted average bit error rate in
rxQualHreqave handover and power control algorithms. Each is calculated from rxQualHreqave bit error rate (BER)
measurements on a radio link
This attribute defines the number of quality measures used by the power control mechanism, in
rxQualAveBeg
case of hopping TS or fast MS
hoMargin Margin to use for PBGT handovers to avoid subsequent handover, in PBGT formula
Margin to be added to hoMargin until rxLevHreqave for short averaging algorithm in order to
hoMarginBeg
compensate the lack of measurements
Number of Measurement Results messages that must be received before the handover algorithm in
runHandOver
a cell is triggered
Nortel confidential

6.33.2 DEPLOYMENT OPTIMIZATION AND MONITORING

The expected gains when deploying Automatic Handover Adaptation feature are:
• Reduce Overall RF Drops

• Improve HO Drops and HO Failures
• RLT drops and BER improvement due to automatic power control effects
• Reduced time at max power due to better efficiency in power control
Hereunder is an example of activation of AHA that shows those improvements.
FIRST ACTIVATION
Activation parameters setting:
Parameter Value
selfAdaptActivation enabled
servingfactorOffset 2
neighDisfavorOffset 2
rxLevHreqave 8
rxNCellHreqave 8
rxLevHreqaveBeg 2
rxLevNCellHreqaveBeg 2
rxQualHreqave 8
rxQualAveBeg 2
hoMargin 4
hoMarginBeg 4
runHandOver 1
That activation has proven some good results, mainly on RF drops and Minute Of Usage, but
also on HO repartition, as shown below:
RF Drop per Erlang Evolution
Nortel confidential

Handover Distribution
As explained in the feature description the algorithm helps in the Urban areas by making
intelligent decisions for Power Budget handovers and reducing interference by more reactive
adjustment in attenuation.
In coverage limited environment the advantage is highly mitigated. In order to capture the
benefits from the feature in the Suburban and Rural areas through reducing rescue
handovers; appropriate recommendations should be applied (see chapter Final recommended
setting).
Hereunde are the general conclusions about AHA activation:
• RF MoU/Drop improvement follows more closely the reduction in drop due to

handovers. BSCs with good coverage and having interference issues definitely
showed improvement in drops.
• BSCs with good ratio of hopping radios and having reduction in BER showed some
considerable improvement in RLT drops. These were areas where the UL BER
had shown consistent improvement after the feature activation
• BSCs with very low ratio of hopping Sectors OR even with high ratio of hopping
sectors showed NO considerable improvement in drops if they are coverage
limited OR less RF overlap.
Nortel confidential

FINE TUNING
FREQUENCY HOPPING CASE
The power Budget handover adaptation in the frequency hopping case ( > 3 SFH per sector)
uses servingfactorOffset to favor the server as suppose to the neighbor in two of the four
cases. So the setting of “-2” for servingFactorOffset means it will actually favor the server OR
in other words disfavor the neighbor greatly. The neighDisfavorOffset is already applied at “2”
dB such that the two cases where you have enough measurements of your server the
effective HOMargin (eff) will be 8 dB when you have not enough measurements in the
neighbor and 6 dB when you have enough measurements in the server as well as from the
neighbor. In the expectation of making better and more handovers decisions on PBGT in
these two case the HOMargin (eff) should be reduced by 2 dB in both these cases in order not
to disfavor the neighbor by effectively HOMargin of “6” OR “4” by tuning the
servingFactorOffset from “-2” to “0”.
Note: experience results presented in this part are done with 8 SFH per sector.
Handover QoS
NON FREQUENCY HOPPING CASE
The power Budget handover adaptation in the non-frequency hopping case ( < 4 SFH per
sector) does not use servingFactorOffset to favor the server as suppose to the neighbor. This
case uses the neighborDisfavorOffset and so the HOMargin (eff) remains at 6 and 4 dB for
cases with server having enough measurements. However, the other two cases where the
neighbor is disfavored when the server is not having enough measurements seems to be very
high with the intial settings; HOMargin (eff) ( 4 + 4 = 8 dB). It was recommended to change the
HOMargin (eff) by tuning hoMarginBeg from “4” dB to “2” dB to get effective margin of “6” dB.
Nortel confidential

Handover QoS
FINAL RECOMMENDED SETTING
The table below provides the recommended setting to take advantage of AHA activation
depending on the area characteristics:
Parameter Urban area Suburban area Rural area

selfAdaptActivation enabled enabled enabled
servingfactorOffset 0 2 0
neighDisfavorOffset 2 2 2
rxLevHreqave 8 8 8
rxNCellHreqave 8 8 8
rxLevHreqaveBeg 2 2 2
rxLevNCellHreqaveBeg 2 2 2
rxQualHreqave 8 8 8
rxQualAveBeg 2 2 2
hoMargin 4 4 2
hoMarginBeg 2 2 4
runHandOver 1 1 1
Nortel confidential

6.34. HANDOVER FOR TRAFFIC REASONS ACTIVATION

GUIDELINE
The purpose of this guideline is to define a default activation of the feature “Handovers for
traffic reasons” over the whole BSC. This proposal includes also the usage of the feature
“Handover decision according to adjacent cell priorities and load” and the default activation of
directed retry. We remind that HoTraffic must be favoured for traffic reason instead of using
the feature Directed Retry, which is a solution only for occasional cases of congestion.
For a better understanding please refer to the following Functional Notes and chapters:
• [R12] Handover for traffic reasons: TF132

• Handover for traffic reasons (from V12)
• [R13] Handover decision according to adjacent cell priorities and load TF716
• Handover decision according to adjacent cell priorities and load (from V12)
• Directed Retry Handover
The objectives of a BSC deployment of that feature would be:
• to reduce current TCH blocking wherever it happens on normal origination and

during HO phase
• to anticipate unexpected TCH blocking in order to improve traffic carried on
originating and ongoing calls
• to facilitate feature activation process by generalising the settings on the whole
BSC
6.34.1 ALGORITHMS AND PARAMETERS DEFINITION

As the Directed Retry handover is intended to re-direct TCH Allocation on a loaded cell to an
other cell, the traffic handover’s objective is to leverage resources blocking when one cell is
overloaded by redirecting the most appropriate calls in progress to neighbour cells with a
PBGT handover procedure.
OVERLOAD CRITERION
The overload criterion is defined on a cell basis and can take two expressions according to the
operator’s choice :
• If queuing is not activated the number of available TCHs is lower than the defined
threshold,
• If queuing is activated: the number of queued TCH requests is greater than the
defined threshold.
That mechanism is decribed in the chapter Congestion determination.
When overload occurs, the BTS sends, on request from the BSC, HO indications including the
list of candidate neighbors n for which the following expression is fullfilled:
EXP2Traffic(n) = Pbgt(n) - [hoMargin(n) - hoMarginTrafficOffset(n)]
Refer also to the chapter General formulas.
Nortel confidential

RELATED PARAMETERS
hoTraffic (bsc) enable the traffic HO feature at BSC level
hoTraffic (bts) enable the traffic HO feature at BTS level
level strength margin added to compute the neighbor eligibility in case of traffic HO
hoMarginTrafficOffset
(refer to EXP2Traffic)
minimum number of free TCHs which triggers the beginning of the TCH congestion
numberOfTCHFreeBeforeCongestion
phase and the beginning of the traffic overload condition
number of free TCHs which triggers the end of the TCH congestion phase and the end
numberOfTCHFreeToEndCongestion
of the traffic overload condition
list of couples of causes (HOInitialCause and HONonEssentialCause) to prevent
hoPingpongCombination
possible HO ping pong due to traffic HO
hoPingpongTimeRejection timer associated to the anti ping pong feature
level strength offset added to compute the neighbor eligibility depending on its state of
offsetLoad
congestion (refer to EXP4)
Furthermore and as described in the chapter Expected effects and recommended parameters,
queuing and directed retry parameters have to be set properly. As a reminder:
• Queuing activation: please refer to chapters Queuing and TCH Allocation

Management Parameters
• Directed retry: please refer to chapters Directed Retry Handover and Directed
Retry Handover Parameters
FEATURE INTERWORKING
In order to avoid blocking the originating calls on congested cells, directed retry with default
settings should be enabled, and to avoid a return from non congested to congested cell after
HO traffic activation two features should be used:
• prevent « ping-pong » effect by applying a protection timer for all incoming

relations onto the congested cell
• prevent a « snow ball » effect by using the load status conditions through the
usage of the offset load parameter in :
EXP4(n) = EXP2(n) – [offsetLoad(n) * stateLoad(n)]
Nortel confidential

6.34.2 EXPECTED EFFECTS AND RECOMMENDED PARAMETERS

Let’s consider a cell A passing through different states of congestion and the HO interactions
in its neighborhood.
Normal phase Overload phase Normal phase
Cell A Cell A Cell A
Normal HO (PBGT, Qual, Lev, …) Non congested cell

Traffic HO
Congested cell
Prevented HO on load condition
In a normal phase incoming HO toward cell A can be alarm HO, PBGT HO, or traffic HO
coming from congested neighbor cells.
As the congestion state is reached on cell A, depending on the cell load state and the
associated parameter, some procedures are engaged to try to set back the cell to a non
congested state:
• traffic HO are activated from cell A to its non congested neighbor cells, i.e. PBGT
HO with a smaller margin
• traffic HO are disfavored toward congested cell thanks to Handover decision
according to adjacent cell priorities and load feature
• HO toward cell A are also disfavored
When the cell A succeed in balancing the excess of traffic it reaches again a non congested
cell and the normal procedures are applicable again.
PARAMETER TUNING
As described hereabove the expected behaviour takes benefit from the Handover for traffic
reasons feature that allows to balance calls in good radio conditions toward neighbor cells via
a traffic HO, from the directed retry HO that balance TCH assignment to neighbor cells, and
from the Handover decision according to adjacent cell priorities and load feature that prevents
from oading the cell with unnecessary incoming HO.
Directed retry parameters settings are summarized in the following chapter §4.5.5 and
hoMarginTrafficOffset and offsetLoad parameters tuning is explained hereunder.
Nortel confidential

hoMarginTrafficOffset
Cell A congested Cell B non congested
Offset load
One can observe on the above figure that using traffic HO is likely to simulate an increase in
the non congested neighbor cell coverage of hoMarginTrafficOffset dB. In order to prevent
outgoing traffic HO from A to B to come back on A an offsetLoad value equal to
hoMarginTrafficOffset is recommended. In that case any attempt of HO from “traffic extended”
B cell coverage to A would be discarded.
offsetLoad ≥ hoMarginTrafficOffset
Furthermore, the correct setting of the anti ping pong feature sould harden that behaviour for
the PBGT HO from B to A.
LCAUTION!
The following exceptions should be applied:
• Timer protection should not be set from cells like: indoor, microcells, special
coverage, or any relation with HOmarginPBGT < 0
• Offset load should not be set from cells like: indoor, microcells, special coverage,
or any relation with HOmarginPBGT < 0
Nortel confidential

RECOMMENDED PARAMETERS
CONGESTION DETECTION
Parameter Recommended value

numberOfTCHFreeBeforeCongestion 10 % of potential ressources for circuit calls including preemptable PDTCH
numberOfTCHFreeToEndCongestion 20 % of potential ressources for circuit calls including preemptable PDTCH
Note: potential ressources for circuit calls including preemptable PDTCH cans be deduced
from the following metric
(C1700 max value (tchFrAveragedAvailableMax) - AllocPriorityThreshold)
HANDOVER FOR TRAFFIC REASONS ACTIVATION

hoTraffic (bsc) enabled
hoTraffic (bts) enabled
hoMarginTrafficOffset 6 dB
Note: HoMarginTrafficOffset should be tune such as the resulting margin should be equivalent
to the one for rescue HO. This margin can be increase case by case for cell with important
congestion. At on stage it is preferable to add capacity.
Nortel confidential

HANDOVER DECISION ACCORDING TO ADJACENT CELL PRIORITIES

AND LOAD ACTIVATION

offsetLoad ≥ hoMarginTrafficOffset
GENERAL PROTECTION AGAINST HO PINGPONG

hoPingpongCombination (all, PBGT)
hoPingpongTimeRejection at least 20s
DIRECTED RETRY HANDOVER ACTIVATION

directedRetryModeUsed bts
interBscDirectedRetry allowed
intraBscDirectedRetry allowed
interBscDirectedRetryFromCell allowed
intraBscDirectedRetryFromCell allowed
modeModifyMandatory used
directedRetry - 80 dBm
Nortel confidential

6.35. DISABLING AMR BASED ON TRAFFIC IN V15.1.1

Previously to V15.1.1, if hrCellLoadStart > 0, then HR calls can be allocated as long as the
RxLev criterion is matched.
To achieve such a behavior in V15.1.1, since AMR based on traffic is automatically activated,
it is necessary to set the parameters as following:
• filteredTrafficCoefficient = 1
• hrCellLoadStart = 1 (range [0 to 100])
• hrCellLoadEnd = 0 (range [0 to 100])
With this values, the “V15.1 like” behaviour should be reached after nb_of_inService_DRX*10
seconds.
Note: the behaviour with this configuration is based on a theoretical study of the AMR based
on traffic algorithm.
To prevent HR allocation, it is necessary to set the parameters as following :
• hrCellLoadStart = 0 (range [0 to 100])

• amrDirectAllocRxLevUL or amrDirectAllocRxLevDL = more than -48 dBm
Nortel confidential

6.36. NETWORK SYNCHRONIZATION IMPACTS
6.36.1 COLLISION PROBABILITY
PROBABILITY COLLISION
METHOD OF CALCULATION
In an asynchronous network or in a burst synchronized network, the probability collision

between 2 not co-site cells cannot be precisely calculated. In these two cases, a collision
probability average value is usually used when calculating interferences. But in a time
synchronized network the exact calculation of the collision probability between 2 cells is
possible using the hopping GSM algorithm. Generally, this calculation depends on the
following 9 parameters:
• HSN1 and HSN2 - range 1 to 63
• MAIO1 and MAIO2 - range 0 to Nb of frequencies of MA list1(2) - 1
• FNOffset1 and FNOffset2 - range from 0 to 2715647 (the length of a GSM

hyperframe).
• Nb of frequencies of MA list1 and Nb of frequencies of MA list2.
Duration over which to compute the collision probability the GSM hyperframe length: 2715647
GSM frames.
In the case of 1x1 frequency hopping fractional reuse, as the same MA list is used, the
number of parameters goes down to 8.
Cell x1, HSN1= 9

MAIO1= 0 F24 F30 F4 F33 F25 F26 F26 F19
FN1 = 150
MA list = 38 Freq
collision
Cell x2, HSN2= 10
MAIO2= 26
FN2 = 1450 F22 F16 F22 F5 F2 F26 F37 F36
MA list = 38 Freq
Duration : d
Probability of collision calculation
Nortel confidential

The more TDMA, the more the average collision probability will tend to its limit = 1 / Nb. Freq.
It leads also to ad hoc plan’s limitation, for which the Collision probability is constant. No
change in the parameters of the hopping law (HSN, FN) will bring any difference to the
collision probability, for all the MAIO are used by all the TDMA (ad-hoc frequency plan implies
number of TDMA is equal to the number of hopping frequencies).
SPECIAL PROPERTIES OF THE HOPPING LAWS
As it will be detailed below, the hopping GSM laws have some interesting properties which
could be used for decreasing and controlling the collision probability when using time
synchronization.
PERIODICITY
Applying the GSM hopping algorithm, the following periodicity can be found concerning the FN
and FN Offsets:
ARFCN (FN) = ARFCN (FN + 26*51*64).
This property implies that the calculation of the collision probability over a duration of 84864
(where 84864 = 26*51*64) TDMA frames is equivalent to the collision probability calculation
over a duration of 2715648 TDMA frames
Therefore, the computation of the exact value of collision probability requires a shorter
duration - 84864 TDMA frames - than the whole GSM hyperframe. It implies also that using
the Nortel FN Offset range (0 to 84863) allows the calculation of collision probability with 100%
precision.
EQUIVALENT HOPPING COMBINATIONS
A hopping combination between two cells is defined as the following set of hopping
parameters: (HSN1, FNOffset1, MAIO1, HSN2, FNOffset2, MAIO2)
Applying again the GSM hopping algorithm, it can be found that the collision probability
between the hopping combinations:
(HSN1, FN1, MAIO1) and (HSN2, FN2, MAIO2)
is equal to the collision probability between hopping combinations:
(HSN1, FNOffset1, mod (MAIO1+k, Nb Freq.))

And
(HSN2, FNOffset2, mod (MAIO2+k, Nb Freq.))
This property allows that the calculation of the collision probabilities between all hopping
combinations that exist between 2 cells needs computing the collision probabilities only for
some hopping combinations of these 2 cells - therefore, less computing time than in the
general case is needed.
Nortel confidential

“MAGIC” HOPPING COMBINATIONS
In the case of asynchronous hopping networks, the interference between a victim cell and an
interferer cell is calculated by using an average collision probability between two cells. This
probability is calculated with a simple formula which takes into account the number of common
frequencies, the number of TRXs of the interfering cell and the numbers of frequencies of both
MA lists.
Using the GSM hopping algorithm, it can be found that the hopping combinations for 2 cells
have collision probabilities which, depending on the used FN Offsets, HSNs and MAIOs, may
be or not be significantly different from the above mentioned average collision probability.
This property can be exploited only on Network with low fractional reuse where the chosen
hopping combinaisons with very low or low collision probabilities (so called magic Hopping
combinaison) could be used throughout the network for decreasing the collision probability
and thus the network interference.
Time synchronization allows knowing and controlling the FNOffset. Therefore, the existence of
those hopping combinations that have significantly different collision probabilities from the
average collision probability could be exploited only in the case of time synchronized networks
with low fractional reuse.
Unfortunately, there are several difficulties about using these special hopping combinations as
the multiple matching of the 3 parameters (HSN, FN Offsets, MAIOs) at a network level is very
complex. Finding the best global solution through systematic computing is not possible but it is
supposed that a satisfactory feasibility can be achieved by using a certain strategy of
parameter planning (HSN, FN Offsets, and MAIOs.
6.36.2 TSC IMPACTS

The TSC (Training Sequence Code) is used by the GSM equalizer for the characterization of
the radio channel. The 8 TSCs were chosen for better combating the random GMSK
interference, other types of not GSM interferences or noise.
In a synchronized network, if the interferer is a co-channel interference then, the interferer is
another TSC and not random bits of GMSK. In this case, depending on the couple victim TSC
and interferer TSC, the synchronization may cause further C/I degradation (and in very few
cases a slight improvement). As the different synchronized couples of TSCs have not the
same de-correlation level this degradation is variable and it is the highest when the victim and
the co-channel interferer have the same TSC (when the equalizer considers the interferer as a
reflection of the useful signal); this case is called TSC collision.
It has to be underlined that an interferer is considered synchronized with a victim only if the
time bit offset between them is less or equal to 5 time bit periods. Therefore, if the difference
of propagation distance for victim and interferer is greater than 5,5 km then the victim and the
interferer are non synchronized and there is no TSC impact.
Nortel confidential

Also, the TSC impact in a synchronized network depends on the fact if an interference
cancellation feature is deployed or not in a network.
When an interference cancellation feature is not deployed in the synchronized network, the
TSC degradation impact in the case of TSC collision may be up to 3 dB. But this impact is
significantly higher when an interference cancellation feature is deployed: if in this case a TSC
collision exists between the victim and the strongest co-channel interferer, then all gain due to
the interference cancellation is lost and also an extra loss in C/I is produced (the TSC
degradation impact may be up to 12 dB).
Therefore, synchronization may cause significant network C/I degradation when synchronizing
a network without a careful TSC (BCC) planning.
In an asynchronous network, the BCC planning is contained in BSIC (NCC&BCC) planning
which is done in order to avoid usually co-BCCH & co-BSIC neighboring. This kind of planning
is no longer satisfactory for a synchronized network: in this case, a BCC planning has to be
done firstly for avoiding the TSC collisions and then a NCC planning has to be done in order to
avoid usually co-BCCH & co-BSIC neighboring.
BCC planning for avoiding TSC collisions is far from being trivial as only 8 values (0 to 7) are
available and TSC collisions have to be avoided on the BCCH channel as well as on the TCH
channel (which usually is hopping).
Each victim and interferer TSC couple (i, j) has an intrinsic impact value: Ti,j. But the real
impact of an interfering TSC on the final value of interference has to be calculated taking also
into account a factor characterizing the interference situation. This factor, called DITR
(Dominant to Interferer TSC Ratio), reflects how much stronger the co-channel interference
with the same TSC as the dominant interferer is comparing to the rest of interference (which is
the sum of: interferences with other TSCs, adjacent-channel interferences and thermal noise).
6.36.3 FN OFFSET IMPACTS

In a synchronized network without a FN Offset planning, the same types of bursts and
channels (FCH, SCH, BCCH, SDCCH, SACCH, and CCCH) will occur simultaneously on
different BTS.
Using NW synchronization and a FN Offset planning for all neighbors of each optimized cell
could bring an improvement on collision probability, an improvement to handovers reactivity
and a reduction on interference level on SACCH channels by avoiding (or lowering) the
simultaneous SACCH transmissions between interfering cells.
SACCH IMPACT
In a synchronized network without a FN Offset planning, the SACCH transmission will be

simultaneous and, as SACCH channel is always transmitted regardless of the voice activity, it
will not benefit from the discontinuous transmission (DTX) mechanism at all, since it is always
transmitted. The consequence of this fact is a higher interference level on SACCH channels
than on TCH channels.
Nortel confidential

In a synchronized network with an intelligent FN Offset planning, the simultaneous SACCH

transmissions of interfering cells can be avoided (or lowered) and thus the interference level
on SACCH channels can be significantly reduced.
SCH IMPACT
FN Offset has an important role on BSIC decoding reactivity. According to the GSM standard,
a mobile should attempt to demodulate SCH on the BCCH carrier of as many neighbor cells
as possible, and read the BSIC as often as possible for neighboring cell information and at
least once every 10 seconds in dedicated mode or for cell selection or reselection in idle
mode.
In a synchronized network without a FN Offset planning, the SCH transmission of neighbor
cells will be simultaneous and a mobile will need much more time for BSIC reading. Thus, a
mobile will read the BSIC of a smaller number of neighbors if FN Offset is not correctly
planned.
In a synchronized network with an intelligent FN Offset planning, the simultaneous SCH
transmission of neighbor cells can be significantly reduced. In this case, a mobile could read
the BSIC of a greater number of neighbors in the window of 10 seconds. It has to be
underlined that in this case an intelligent scheduling for BSIC refreshing has a very significant
impact.
Finally, it has to be mentioned that the BSIC searching and decoding speed in active mode
depends on the type of TCH channel used by mobiles. During a 26 TDMA frames period, a
mobile has only one idle frame for searching and decoding the BSIC of neighbor cells when
using a FR TCH channel, whereas it has 12 idle frames when using a HR TCH channel.
Consequently, for a synchronized network, the impact of an intelligent FN Offset planning on
the BSIC searching and decoding speed in active mode is more significant for the mobiles
using FR TCH channels than for the mobiles using HR TCH channels.
Neighbor relationships and the Interference Matrix are used as input data for the SCH Color
allocation (see [R34])
Nortel confidential

6.36.4 INTERFERENCE CANCELLATION

Network synchronization should allow to optimizing receiver performances in both Uplink
(maximizing the gain on interference cancellation algorithms) and Downlink (with the
introduction of SAIC mobiles).
UPLINK (INTERFERENCE CANCELLATION)
Since V9-V10, Nortel’s proprietary algorithm of uplink interference cancellation requires BTS
equipped with antenna diversity.
It can work with or without frequency hopping and it can remove any kind of interferer that has
some spatial or temporal coherence (co-channel, adjacent channel, CDMA signal leaking in
the PCS band, TV transmitter, etc...).
The number of simultaneous interferers is a limiting factor to the good working of the feature.
The feature removes the stronger interference signal and proves to be more efficient when the
ratio (Stronger Interferer / Sum of all interferers) is high. Theoretical gain values are
summarized bellow:
1 interferer 5 interferers
Synchronous interferers 8dB 1dB
Asynchronous interferers 4.5dB 0.5dB
Potential gains with interference cancellation feature
The algorithm uses the window of 26 bits of the TSC in the normal bursts.
The table above shows that the gain is higher in case of synchronous interferers. If the
stronger interferer uses the same TSC than the useful signal, then, the useful signal will be
degraded as well (TSC collision).
The TSC collision problem doesn’t happen if, comparing to the victim burst, the interferer burst
has a delay greater than 5 symbols. This is the assumption taken for the non synchronized
case.
Nortel confidential

DOWNLINK (SAIC MOBILES)
In the same way as for the uplink, SAIC (Single Antenna Interference Cancellation) mobiles
may limit the interferences impact in downlink.
SAIC mobiles are the DARP (Downlink Advanced Receiver Performance) phase 1 mobiles.
One antenna downlink algorithm, based on signal processing in the mobiles takes benefit at
the burst level by improving the C/I ratio up to 9 dB gain in first adjacent interferences and up
to 2 dB for co channel interferences. Unlike uplink interference cancellation, the benefit of this
feature at the network level depends on the penetration of these mobiles. At 75% penetration,
1 dB improvement on C/I can be achieved.
Moreover, in non-interfered conditions, these algorithms do not degrade the performances.
The real benefit on the network will actually depend on the mobiles performances and their
penetration on the market.
Since performances are dependent on SAIC mobiles penetration, there is a way to part the
requests associated with a mobile type (SAIC or not) on some of the TDMA rather than others
in case of TCH allocation. Each TDMA is affected with a property (DARPPh1Priority) that
shares the TDMA of a cell in 2 pools:
• TDMA handling preferably SAIC mobiles requests.

• TDMA handling preferably non SAIC mobiles requests.
The BSC radio allocator is modified to include this new type of priority to be combined with all
already existing priorities. The BSC chooses the radio TS using the following order:
• SAIC :
For a SAIC type of request, whatever the type of request (FR, AMR FR,
AMR HR, DATA) BSC allocates the MS on a high priority DARPPh1
resource unless there is no free TCH (that copes with the request) in the
high priority DARPPh1 pool of resources. For AMR HR request, if there is
any hole in the high priority DARPPh1 pool of resources, this one is selected
otherwise BSC looks for an available full TS in the high priority DARPPh1
pool of resources. If there is neither available hole nor available full TS in the
high priority DARPPh1 pool of resources, BSC looks for first an available
hole in the low priority DARPPh1 pool of resources, then an available full TS
in this pool of resources.
For a non SAIC type of request, whatever the type of request (FR, AMR FR,
AMR HR, DATA) BSC allocates the MS on a low priority DARPPh1 resource
unless there is no free TCH in the low priority DARPPh1 pool of resources.
For AMR HR request, if there is any hole in the low priority DARPPh1 pool of
resources, this one is selected otherwise BSC looks for available full TS in
the low priority DARPPh1 pool of resources. If there is neither available hole
nor available full TS in the low priority DARPPh1 pool of resources, BSC
looks for first an available hole in the high priority DARPPh1 pool of
resources, then an available full TS in this pool of resources.
Nortel confidential

• Interference level,
• TDMA priority,
• TDMA number (from the smallest to the biggest: 0 to n),
• TS number (from the biggest to the smallest: TS7 to TS0).
Note: For radio resource allocation only SDCCH requests are not differentiated depending if
the mobile requesting is SAIC capable or not.
Nortel confidential

6.37. NETWORK SYNCHRONIZATION ENGINEERING PLANNING
6.37.1 TSC PLANNING

TSC (BCC) planning uses only 8 values of TSC and therefore avoiding the TSC collisions or
using intelligently the best TSC couples throughout a network is a complicate task. The TSC
planning strategy is to allocate the best TSC couples to the worst interfering cell couples.
Nortel Engineering recommends a relatively simple TSC planning which has as input:
• The Nortel TSC impact matrix Ti,j

• The Interference matrix (IM) of the network
• The quantity of interference between cells due the used frequency plan (given by
the collision probability and the traffic)
Thus, Nortel’s TSC planning strategy is to allocate the best TSC couples, which have the
smallest Ti,j values, to the interfering cell couples which have the highest values of
IM *Collision probability*Traffic.
The TSC planning has then to be used as input for the final BSIC (NCC+BCC) planning.
6.37.2 FN OFFSET PLANNING

The FN Offset planning has simultaneously 3 different and independent requirements:
• Avoiding SACCH collision

• Avoiding SCH collision (for speeding up BSIC reading)
• Contributing with the couple HSN and MAIO planning at obtaining a lower collision
probability between the hopping laws
In order to address independently the 3 requirements of FNOffset planning, Nortel defines
FNOffset as a combination of 4 new parameters:
• SACCH Color ( integer from 0 to 12 for HR traffic network or 0 from 0 to 25 for FR

traffic network)
• SCH Color ( integer from 0 to 50 )
• Hopping Color ( integer from 0 to 123 for HR traffic networkor 0 from 0 to 61 for
FR traffic network)
• Global Color
where:
Global Color = SACCH Color * 51 + SCH Color * 52

FN Offset = Global Color + Hopping Color* 13 * 51 (for synchronized networks without HR
traffic)
or
FN Offset = Global Color + Hopping Color* 26 * 51 (for synchronized networks without HR
traffic)
Nortel confidential

It can be easily verified that:
• The impact of SACCH Color on SACCH collisions is equivalent to the impact of

FN Offset (Global Color) on SACCH collisions
• The impact of SCH Color on SCH collisions is equivalent to the impact of
FN Offset (Global Color) on SCH collisions
• SACCH Color has no impact on SACCH Collisions
• SCH Color has no impact on SACCH collisions
• Hopping Color has no impact on SACCH and SCH collisions
Therefore, for making an easier FN Offset planning, Nortel obtains the FN Offset planning by
making independently:
• SACCH Color planning

• SCH Color planning
• Hopping Color planning
It has to be noted that:
• SACCH Color planning is done taking into account the TN Offset planning
additionnally
• Hopping Color planning is useful only for a fractional reuse frequency plan as it has
no impact fro adhoc frequency plans
For further details concerning the SACCH Color, SCH Color and Hopping color please refer to
[R34])
6.37.3 TN OFFSET PLANNING

In a time synchronized network, a TNOffset planning has to be performed in order to spread
as much as possible the TNOffsets between neighbor sites. This can be easily obtained if
through planning the sites that have the same TNOffset are as far as possible from each
another). This planning does not take into account FNOffset planning but it has to be used
then as input for the SACCH Color planning
Nortel confidential

6.37.4 SYNCHRONIZATION STRATEGIES

The parameter planning in a synchronized network depends strongly on the used frequency
plan: ad-hoc or fractional reuse. For each of two frequency plans, 3 different synchronization
strategies were envisaged by Nortel Engineering:
• 100% Synchronization Solution, when the synchronization is applied to a

significant part of the network (or all network);
• Hot Spot Solution, when synchronization is applied for only some couples of cells
(sites), representing the network hot spots, which are heavily interfering;
• Mixed Synchronized/Not Synchronized Solution, when synchronization is
applied to clusters of sites of limited size;
So far, Nortel has experimented only the 100% Synchronization Solution in a frequency adhoc
plan.
Nortel confidential

6.38. NETWORK SYNCHRONIZATION FIRST TRIAL RESULTS
DEFINITION
ENGINEERING TESTS CHARACTERISTICS
A network engineering study of only the 100% Synchronization Solution in a frequency adhoc
plan was performed during a trial,
The trial synchronized zone consisted of 33 synchronized sites which were divided into 2
different clusters:
• KPI Cluster (10 sites)

• Buffer Cluster (23 sites)
Only the cells of KPI Cluster were taken into account when assessing the performances of
different test scenarios. Also, initially, the KPI Cluster cells were supposed to not be interfered
by any not synchronized cell.
Broadly, the impact of the following parameters was tested:

• Burst synchronization with existing BSIC plan (w/o a TSC plan);
• TSC planning with Burst synchronization;
• ICA algorithm usage (50% or 100%) with Burst synchronization & TSC plan;
• Time synchronization with FNOffset planning (SCH + SACCH color) without TNOffset
planning (same TSC plan and TNOffset plan as Burst Synchronization);
• Time synchronization with FNOffset planning (SCH + SACCH color) and TNOffset
planning (same TSC plan as Burst Synchronization);
Please refer to Network Synchronization handbook [R34] for a complete KPI Results
presentation.
Nortel confidential

ICA 50% VS ICA 100% IN BURST SYNCHRONIZATION
In order to determine the best ICA settings, tests were carried out in Burst Synchronization
with an existing BSIC plan as well as with a planned TSC. The expectation that ICA 100%
performs better than ICA 50% was confirmed. This can be seen in the following charts, where
average UL BER and MOU metrics are presented in Burst Synchronization with an existing
BSIC plan. Following these tests, it was decided that only ICA 100% will be used in the
following tests.
AVE RxQual UL
0,53
0,52
ICA @50% ICA @100%
0,51
0,5
0,49
0,48
0,47
0,46
0,45
0,44
06
06
06
06
06
06
06
06
20
20
20
20
20
20
20
20
8/
8/
8/
8/
8/
8/
8/
8/
/0
/0
/0
/0
/0
/0
/0
/0
07
08
09
10
11
12
13
14
MOU
290
ICA @50% ICA @100%
270
250
230
210
190
170
150
07/08/2006 08/08/2006 09/08/2006 10/08/2006 11/08/2006 12/08/2006 13/08/2006 14/08/2006
Nortel confidential

A gain can be achieved with NW synchronization only when deploying with interference
cancellation features (ICA in UL, SAIC in DL) and performing engineering planning of the
following parameters: TSC, FN Offset, TNOffset, hopping laws.
The interference cancellation features work significantly better in burst or time synchronized
networks than in asynchronous networks provided that co-channel TSC collisions are avoided.
The impact of interference cancellation is expected to be greater in UL due to a more
performing interference cancellation algorithm and 100% penetration.
In DL, the interference cancellation algorithm is less performing and, at present, the
penetration of mobiles with such a feature is still low in life networks (below 30%).
PLANNED TSC VS BSIC PLAN – BURST SYNCHRONIZATION
As mentioned before, in an asynchronous network the BSIC planning is done in order to avoid
BSIC/BCCH conflict between the neighbors. Evidently, this BSIC planning cannot ensure that
there are no harmful TSC when synchronizing the network. Furthermore, this methodology of
BSIC planning cannot take in consideration that the TSC couples have different TSC impacts
when synchronizing the network and therefore it cannot take advantage of this fact by
allocating the best TSC couples to the worst couples of interfering cells.
MOU TRAFFIC CARRIED

310
BSIC Plan TSC Plan
290 8400
270 7200
250 6000
Traffic
MOU
230 4800
High Non RF Drops

210 3600
190 2400
170 1200
150 0
6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
00 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200
8 /2 8 / 8 / 8 / 8 / 8 / 8 / 8 / 8 / 8 / 8 / 8 / 8 / 8 / 8 / 8 / 8 /
/0 /0 /0 /0 /0 /0 /0 /0 /0 /0 /0 /0 /0 /0 /0 /0 /0
07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23
The intent behind this test case was to see how much a planned TSC provides improvements
in performance against an un-planned TSC (BSIC). As it was expected, the MOU evolution
shows an improving trend.
Nortel confidential

7. APPENDIX A: MAIN EXCHANGE PROCEDURES

AT BSC LEVEL
7.1. ESTABLISHMENT PROCEDURE
SABME: frame to set asynchronous balanced mode (initiate a link for numbered information
transfer).
UA: unnumbered aknowledge
Nortel confidential

7.2. CHANNEL MODE PROCEDURE
Nortel confidential

7.3. DEDICATED CHANNEL ASSIGNMENT
Nortel confidential

7.4. INTRACELL HANDOVER PROCEDURE
Nortel confidential

7.5. INTRABSS HANDOVER PROCEDURE
From BTS 1 to BTS 2
Nortel confidential

7.6. INTERBSS HANDOVER PROCEDURE
BTS 1 (from BSC 1) to BTS 2 (from BSC 2)
Nortel confidential

7.7. 2G-3G HANDOVER PROCEDURE
Nortel confidential

7.8. RESOURCE RELEASE PROCEDURE (EXAMPLE)
Nortel confidential

7.9. SACCH DEACTIVATION PROCEDURE
Nortel confidential

7.10. MOBILE TERMINATING CALL
Nortel confidential

7.11. MOBILE ORIGINATING CALL
Nortel confidential

8. APPENDIX B: ERLANG TABLE

The table below presents the number of Erlang that are expected with regards to the number
of TCH channels on a given cell and considering a blocking rate of 0,01 %. The computation
follows the Erlang B law.
Additionally, this table gives the number of Erlang expected depending on the AMR Half Rate
penetration.
LCAUTION!
The expected number of Erlang with regards to the AMR HR penetration has been calculated
based on an estimation of the gain in capactiy provided by AMR HR. It should not be
considered as contractual but as a good approximation of the expected gain.
% Blocking 2% 2% 2% 2% 2%
AMR HR penetration 0% 25 % 50 % 75 % 100 %
Number of TCH
1 0,021 0,021 0,022 0,023 0,027
2 0,223 0,230 0,247 0,284 0,365
3 0,602 0,630 0,698 0,849 1,177
4 1,092 1,158 1,324 1,688 2,482
5 1,657 1,783 2,097 2,787 4,294
6 2,276 2,483 3,000 4,138 6,621
7 2,935 3,208 3,882 5,299 8,377
8 3,627 3,972 4,814 6,502 10,152
9 4,345 4,767 5,786 7,732 11,922
10 5,084 5,589 6,794 8,982 13,669
11 5,842 6,434 7,833 10,245 15,385
12 6,615 7,299 8,899 11,516 17,056
13 7,401 8,182 9,991 12,790 18,677
14 8,200 9,082 11,106 14,065 20,241
15 9,010 9,978 12,114 15,360 22,004
16 9,829 10,885 13,119 16,655 23,747
17 10,656 11,800 14,119 17,946 25,468
18 11,491 12,724 15,112 19,234 27,164
19 12,333 13,656 16,099 20,516 28,834
20 13,181 14,594 17,077 21,791 30,473
21 14,036 15,540 18,046 23,059 32,082
22 14,896 16,525 19,272 24,579 34,075
23 15,761 17,520 20,517 26,118 36,081
24 16,631 18,524 21,783 27,678 38,102
25 17,504 19,536 23,068 29,257 40,135
26 18,383 20,558 24,374 30,857 42,182
27 19,265 21,587 25,698 32,474 44,240
28 20,150 22,624 27,041 34,112 46,310
29 21,040 23,669 28,403 35,767 48,391
30 21,932 24,643 29,596 37,200 50,467
31 22,827 25,617 30,791 38,629 52,551
32 23,725 26,593 31,989 40,058 54,645
Nortel confidential

33 24,626 27,569 33,191 41,485 56,748

34 25,529 28,545 34,394 42,908 58,857
35 26,435 29,521 35,600 44,329 60,975
36 27,343 30,498 36,808 45,748 63,100
37 28,254 31,534 37,988 47,248 65,077
38 29,166 32,574 39,169 48,750 67,051
39 30,081 33,618 40,349 50,255 69,023
40 30,997 34,664 41,528 51,761 70,990
41 31,916 35,714 42,708 53,269 72,954
42 32,836 36,768 43,886 54,779 74,914
43 33,758 37,825 45,065 56,290 76,870
44 34,682 38,886 46,242 57,803 78,822
45 35,607 39,815 47,306 59,197 80,555
46 36,534 40,741 48,364 60,585 82,272
47 37,462 41,662 49,414 61,968 83,973
48 38,392 42,580 50,458 63,346 85,658
49 39,323 43,493 51,494 64,719 87,327
50 40,255 44,402 52,523 66,085 88,979
51 41,189 45,308 53,546 67,447 90,616
52 42,124 46,426 54,862 68,982 92,628
53 43,060 47,549 56,184 70,519 94,640
54 43,997 48,678 57,513 72,059 96,654
55 44,936 49,812 58,847 73,600 98,667
56 45,876 50,951 60,187 75,144 100,682
57 46,816 52,095 61,533 76,690 102,697
58 47,758 53,245 62,886 78,237 104,712
59 48,700 54,399 64,243 79,786 106,726
60 49,644 55,344 65,345 81,124 108,458
61 50,589 56,285 66,443 82,456 110,181
62 51,534 57,224 67,537 83,782 111,893
63 52,480 58,158 68,626 85,101 113,592
64 53,428 59,091 69,711 86,414 115,282
65 54,376 60,019 70,792 87,720 116,961
66 55,325 61,029 71,867 89,092 118,865
67 56,275 62,039 72,937 90,459 120,765
68 57,226 63,048 74,003 91,822 122,664
69 58,177 64,057 75,065 93,181 124,559
70 59,129 65,065 76,122 94,536 126,452
71 60,082 66,073 77,174 95,886 128,341
72 61,035 67,080 78,222 97,232 130,227
73 61,990 68,087 79,266 98,574 132,109
74 62,945 69,258 80,665 100,154 134,307
75 63,901 70,434 82,071 101,738 136,512
76 64,857 71,614 83,482 103,323 138,723
77 65,813 72,798 84,900 104,912 140,939
78 66,771 73,987 86,325 106,504 143,163
79 67,729 75,179 87,755 108,098 145,392
80 68,688 76,377 89,192 109,696 147,628
81 69,647 77,340 90,276 111,137 149,435
82 70,607 78,300 91,358 112,578 151,237
83 71,568 79,258 92,434 114,017 153,032
84 72,529 80,215 93,508 115,455 154,822
Nortel confidential

85 73,490 81,169 94,578 116,890 156,606

86 74,452 82,120 95,644 118,324 158,384
87 75,415 83,069 96,706 119,756 160,156
88 76,378 84,016 97,764 121,187 161,922
89 77,342 85,131 99,178 122,918 164,140
90 78,306 86,247 100,596 124,654 166,362
91 79,270 87,365 102,020 126,396 168,590
92 80,235 88,485 103,448 128,144 170,823
93 81,201 89,607 104,882 129,899 173,062
94 82,167 90,732 106,322 131,659 175,307
95 83,133 91,857 107,765 133,424 177,556
96 84,100 92,944 108,975 134,758 179,493
97 85,067 94,033 110,184 136,088 181,428
98 86,035 95,122 111,393 137,415 183,361
99 87,003 96,212 112,601 138,736 185,291
100 87,972 97,303 113,809 140,053 187,220
101 88,941 98,395 115,017 141,366 189,146
102 89,910 99,487 116,223 142,675 191,070
103 90,880 100,581 117,429 143,979 192,993
104 91,850 101,704 118,717 145,583 195,088
105 92,820 102,828 120,005 147,190 197,185
106 93,791 103,955 121,295 148,800 199,284
107 94,763 105,083 122,587 150,412 201,385
108 95,734 106,212 123,880 152,025 203,487
109 96,706 107,342 125,173 153,640 205,590
110 97,678 108,474 126,467 155,257 207,694
111 98,651 109,568 127,684 156,717 209,642
112 99,624 110,663 128,900 158,177 211,588
113 100,597 111,758 130,115 159,634 213,531
114 101,571 112,854 131,331 161,091 215,473
115 102,545 113,951 132,546 162,547 217,414
116 103,519 115,047 133,760 164,001 219,352
117 104,493 116,145 134,974 165,454 221,289
118 105,468 117,244 136,187 166,906 223,224
Nortel confidential

9. ABBREVIATIONS & DEFINITIONS
9.1. ABBREVIATIONS
For other abbreviations, refer to [R3].
AMNU Advanced Management Unit

AMR Adaptative Multi-Rate
AMR-HR Adaptative Multi-Rate Half Rate
AMR-FR Adaptative Multi-Rate Full Rate
BCC Base station Colour Code
Last three bits of BSIC code. The BCC is used to identify one of the cells
sharing the same BCCH frequency. Neighouring cells may, or may not, have
different BCC.
BCCH Broadcast Control CHannel
Common mobile logical channel used for broadcasting system information
on the radio interface
BCF Base Common Function
BDA BSC application database
This database contains all the information objects describing the BSS.
BDE OMC-R operations database
This database contains all the information objects describing the BSS under
OMCR management control, and the objects required to manage OMC-R
functionalities
BER Bit Error Rate
Method of measuring the quality of radio link transmission
A ratio of the number of digital errors received in a specified period to the
total number of bits received in the same period. Usually expressed as a
negative exponent, i.e:
10-6 means one bit error in 106 bits of transmission, or one in a million
BIFP Base Interface Front-end Processor
Set of BSC functional units managing the interface with BTS
BSC Base Station Controller
BSCB BTS Signalling Concentration Board
Board which concentrates 12 LAPD signalling channels between BSC and
BTS into 3 channels
Nortel confidential

BSIC Base Station Identity Code

Code used to identify a base station which allows mobile stations to
distinguish the cells sharing the same BCCH frequency. A BSIC is defined
by an (NCC, BCC) combination
BSS Base Station Subsystem

Radio Cellular Network radio subsystem made up of Base Station
Controllers, one or more remote TransCoder Units and one or more Base
Transceiver Stations
BTS Base Transceiver Station
CA Cell Allocation
Radio frequency channel allocated to a cell
CBCH Cell Broadcast CHannel
Logical channel used inside a cell to broadcast short messages in
unacknowledged mode
CC Call Control
Sublevel of layer 3 on the radio interface charged with managing call
processing
CCCH Common Control CHannel
Common bidirectional mobile control channel, used for transmitting
signalling information on the radio interface
CCH Control Channel
Common or dedicated control channel
CGI Cell Global Identifier
Global identifier of a mobile network cell. The CGI contains the Location
Area Code (LAC), Mobile Country Code (MCC), Mobile Network Code
(MNC) and the cell identifier in the location area
CMC Codec Mode Command
CPU Central Processing Unit
Slave BSC processing unit
CPU-MPU/BIFP Central BSC processing unit handling MPU and BIFP functions
dB Decibel
Measurement unit of relative power level defined as 10 log10 (P1/P2) where
P1 and P2 are the power levels.
dBm Power in dB relative to 1 mW
Nortel confidential

DCCH Dedicated Control CHannel

Dedicated radio signalling channel with one SDCCH + one SACCH
DITR Dominant to Interferer TSC Ratio
DLNA Duplexer Low Noise Amplifier
Amplifier installed between BTS and the antenna
DRX Driver and Receiver Unit
Signal processing unit for radio transmission and reception.
DTX Discontinuous Transmission
EFR Enhanced Full Rate vocoder
EIRP Equivalent Isotropic Radiated Power
eMLPP enhanced Multi Level Precedence and Preemption
FACCH Fast Associated Control CHannel
Dedicated signalling channel (Um interface)
FCCH Frequency Correction CHannel
Common frequency synchronization channel
FCH Frequency CHannel
Common frequency synchronization channel
FER Frame Erasure Rate
FH Frequency Hopping
FN Frame Number
FP Frame Processor
FR Full Rate TCH
GSM Global System for Mobile Communications
GSM 900 Radio Cellular Network standard adapted for the 900 MHz frequency band.
HO HandOver: automatic call transfer between two radio channels
HR Half Rate TCH
HSN Hopping Sequence Number
ICM Iinitial Codec Mode
L1M Processor functional unit handling BTS radio measurements
LAC Location Area Code
Code used to identify a location area in the GSM network
LAI Location Area Identity
Geographic identity of a group of cells used to locate a mobile station
Nortel confidential

LB Link Budget
LNA Low Noise Amplifier, part of DLNA system
MA Mobile Allocation
MAI Mobile Allocation Index
MAIO Mobile Allocation Index Offset
MCC Mobile Country Code
MTBF Minimum Time Between Failure
MEU Masthead Electronics Unit
Mini-masthead electronics cabinet. Remote amplifier located between BTS
and the antenna
MHz MegaHertz
MMU Mass Memory Unit (BSC)
MPU Main Processor Unit (BSC)
Set of BSC functional units charged mainly with call processing functions
MNC Mobile Network Code
Mp Measurement processing
MRC Maximum Radio Combiner
MS Mobile Station
MSC Mobile Services Switching Center
MCL Minimum Coupling Loss
MTBF Mathematical Time Between Failure
It is a mathematical time expectancy between two successive parts of
equipment or unit failure
NCC Network Colour Code
First three bits of the BSIC code. Each country is assigned a list of NCC.
NMC Network Management Centre
NSS Network and Switching SubSystem
Radio Cellular Network subsystem including an MSC, main HLR, VLR, EIR
and AUC
NS/EP National Security and Emergency Preparedness
OMC Operation and Maintenance Centre for the radio subsystem
OMC-R Operation and Maintenance Centre - Radio
OMC-S Operation and Maintenance Centre - Switching
OMU Central BSC Operation & Maintenance Unit
OSS Operation SubSystem
Nortel confidential

Radio Cellular Network operations subsystem including the OMC-R and

OMC-S
PA Power Amplifier
PBGT Power Budget
PC Power Control
PCH Paging CHannel
Common subscriber radio paging channel
PLMN Public Land Mobile Network
PSTN Public Switched Telephone Network
PURQ-AC Public Use Reservation for Queuing – All Calls
RACH Random Access CHannel
Common mobile logical channel, reserved for random access requests
transmitted by mobile stations on the radio interface.
RF Radio Frequency
RLC Radio Link Counter
RX BTS receiver
RXLEV Received signal Level
RXQUAL Received signal Quality
SACCH Slow Associated Control CHannel
Slow logical control channel associated with a traffic channel during a
communication
SCH Synchronization CHannel
Common time division synchronization channel
SDCCH Standalone Dedicated Control CHannel
Dedicated radio signalling channel temporarily allocated during call set up.
There are 2 types of SDCCH: SDCCH/8 and SDCCH/4, on which the logical
channels are grouped by 8 and by 4 respectively and combined with CCH
SFH Slow Frequency Hopping
SFH mobile mobile using an hopping channel
Non SFH mobile mobile using a non hopping channel
SICD Serial Interface Controller LAPD
BSC board controller for Abis and Ater Interface
SNR Signal to Noise Ratio
SPU Signal Processing Unit
SUP SUPervision unit
Functional BSC monitoring unit
Nortel confidential

SWC SWitching matrix Controller (BSC 6000)

TA Timing Advance
Alignment process designed to compensate propagation time between a
mobile and base station
TCH Traffic CHannel
Radio traffic channel
TCH/F Traffic CHannel/Full rate
TCH/H Traffic CHannel/Half rate
TDMA Time Division Multiple Access
Abbreviation used to designate a transmission frame on the radio interface,
divided into eight time slots (TS) or channels
TMU Traffic Management Unit
TRX Transmission/reception subsystem of the BTS
TS Time Slot
TSC Training Sequence Code
TSCB Transcoder Signalling Concentration Board (BSC)
Board which concentrates LAPD signalling channels between BSC and TCU
into a single channel
TX BTS transmitter
WPS Wireless Priority Service
Nortel confidential

9.2. DEFINITIONS
CODEC MODE
Codec mode is used to designate one of the 8 AMR vocoder and identified using its rate
(12k2, 10k2, 7.95, 7k4, 6k7, 5k9, 5k15, 4k75) give in kbps.
CONCENTRIC CELL
Two concentric geographical zones delimited by distance and level criteria (outer zone and
inner zone).
Outerzone
Innerzone
BCCH and
traffic signalling
channels channels
DUAL BAND CELL
Each group of TRXs is dedicated to a frequency band (900 and 1800 MHz for example) with
different radio propagation condition; the frequency band used for the largest zone (outer) is
the one used by the mono-band MS already existing in the network, since a mono-band MS
must still be able to decode the common channels.
Outerzone
Innerzone / band1 band0
GSM (or DCS)
DCS (or GSM)
BCCH and
traffic channels
signalling
channels
DUAL COUPLING CELL
Each group of TRXs is dedicated to a frequency band and the two groups of TRXs are
combined with coupling systems with different losses, resulting in different coverage areas
with the same TX transmission power.
Nortel confidential

Outerzone
Innerzone
H2D
H4D
traffic BCCH and
channels signalling
channels
ERLANG
Unit of telecommunications traffic intensity.

The number of erlangs represents the average number of resources or circuits occupied
during the peak traffic hour.
FREQUENCY LOAD
Defines the load of a frequency hopping pattern and is evaluated as below:
fl = Nb of hopping TRX in the cell / Nb of frequencies in the hopping law
FREQUENCY HOPPING: AD-HOC
The Ad-Hoc frequency hopping does not reproduce a pattern all over the network. Frequency
planning is done (HSN, MAIO, MA lists) according to the interference matrix. The particularity
is that the number of hopping TRX = the number of hopping frequencies in most of the cases.
FREQUENCY HOPPING PATTERNS: 1X1
This frequency pattern is used in case of frequency hopping. Each hopping TRX of 1*1 cell,
uses all frequencies of the frequency law:
f1,f2,f3,f4
f1,f2,f3,f4 f1,f2,f3,f4
FREQUENCY HOPPING PATTERNS: 1X3
This frequency pattern is used in case of frequency hopping. Each hopping TRX of 1*3 cell,
uses 1/3 frequencies of the frequency law:
Nortel confidential

f1,f2,f3
f7,f8,f9 f4,f5,f6
MULTIZONE CELL
Used in order to refer following kinds of cell:
• concentric cell (see above)

• heterogeneous coupling cell (see above)
• dual-band cell (see above)
RADIO INTERFACE
Interface between the mobile station (MS) and the BTS.
SPEECH FRAME
Corresponds to 20 ms of speech on the radio interface and theTRAU interface.
TIMING ADVANCE
Delay used to compensate propagation time between mobile and base station.
UM-INTERFACE
See “Radio interface”
WPS CALL
Call which has priority level set in the Assignment Request or Handover Request between 2
and 6 (3GPP TS 48.008)
Nortel confidential

10. INDEX
All the parameters listed in the chapter ALGORITHM PARAMETERS are listed and indexed
here below:
accessClassCongestion, 344 btsMSAccessClassBarringFunction, 350

adaptiveReceiver, 448 btsSMSynchroMode, 445
adjacent cell umbrella ref, 359 btsThresholdHopReconf, 388
allocPriorityTable, 344 callClearing, 332
allocPriorityThreshold, 345 callReestablishment, 298
allocPriorityTimers, 346 callReestablishmentPriority, 350
allocWaitThreshold, 347 capacityTimeRejection, 414
allOtherCasesPriority, 347 cellAllocation, 389
amrAdaptationSet, 425, 426, 427 cellBarQualify, 351
amrDirectAllocIntRxLevDL, 435 cellBarred, 351
amrDirectAllocIntRxLevUL, 435 cellDeletionCount, 306
amrDirectAllocRxLevDL, 433 cellDtxDownLink, 402
amrDirectAllocRxLevUL, 433 cellReselectHysteresis, 284
amrFRIntercellCodecMThresh, 435 cellReselectOffset, 285
amrFRIntracellCodecMThresh, 436 cellReselInd, 285
amrHRIntercellCodecMThresh, 436 cellType_adjacentCellHandover, 330
amrHRtoFRIntracellCodecMThresh, 436 cellType_bts, 330
amriRxLevDLH, 437 channelType, 351
amriRxLevULH, 437 cId, 417
amrReserved1, 438 coderPoolConfiguration, 428
amrReserved2, 438 compressedModeUTRAN, 417
answerPagingPriority, 348 concentAlgoExtMsRange, 365
assignRequestPriority, 348 concentAlgoExtRxLev, 366
averagingPeriod, 371 concentAlgoIntMsRange, 365
baseColourCode, 446 concentAlgoIntRxLev, 366
bCCHFrequency_adjacentCellHandover, 397 concentric cell, 367
bCCHFrequency_adjacentCellReselection, 397 cypherModeReject, 448
bCCHFrequency_bts, 399 dARPPh1Priority, 446
biZonePowerOffset_adjacentCellHandover, 363 data mode 14.4 kbit/s, 403
biZonePowerOffset_handoverControl, 364 data non transparent mode_bts, 403
bscHopReconfUse, 387 data non transparent mode_signalingPoint, 403
bscMSAccessClassBarringFunction, 349 data transparent mode_bts, 404
bscQueueingOption, 349 data transparent mode_signalingPoint, 404
bsMsmtProcessingMode, 336 Data14_4OnNoHoppingTs, 403
bsPowerControl, 336 delayBetweenRetrans, 382
bssMapT1, 375 directedRetry, 359
bssMapT12, 375 directedRetryModeUsed, 360
bssMapT13, 375 directedRetryPrio, 354
bssMapT19, 376 distHreqt, 308
bssMapT20, 376 distWtsList, 308
bssMapT4, 376 diversity, 406
bssMapT7, 377 diversityUTRAN, 417
bssMapT8, 377 dtxMode, 402
bssMapTchoke, 377 early classmark sending, 395
bssPagingCoordination, 447 earlyClassmarkSendingUTRAN, 418
bssSccpConnEst, 378 emergencyCallPriority, 352
bsTxPwrMax, 336 enableRepeatedFacchF, 442
bts Time Between HO configuration, 310 encrypAlgoAssComp, 448
btsHopReconfRestart, 387 encrypAlgoCiphModComp, 449
btsIsHopping, 388 encrypAlgoHoPerf, 449
Nortel confidential

encrypAlgoHoReq, 449 intraCell, 323

encryptionAlgorSupported, 450 intraCellHOIntPriority, 353
enhancedTRAUFrameIndication, 408 intraCellQueueing, 354
enhCellTieringConfiguration, 409 intraCellSDCCH, 323
estimatedSiteLoad, 394 layer3MsgCyphModeComp, 450
extended cell, 332 locationAreaCodeUTRAN, 421
facchPowerOffset, 442 lRxLevDLH, 326
fDDARFCN, 418 lRxLevDLP, 337
fDDMultiratReporting, 293 lRxLevULH, 326
fDDreportingThreshold, 293 lRxLevULP, 337
fDDreportingThreshold2, 294 lRxQualDLH, 328
fhsRef, 390 lRxQualDLP, 338
fnOffset, 445 lRxQualULH, 328
forced handover algo, 310 lRxQualULP, 338
frAMRPriority, 430 maio, 391
frPowerControlTargetMode, 431, 432 masterBtsSmId, 446
frPowerControlTargetModeDl, 432 maxNumberRetransmission, 382
gprsNetworkModeOperation, 447 measurementProcAlgorithm, 404
gprsPreemptionForHR, 442 microCellCaptureTimer, 331
gsmToUmtsReselection, 289 microCellStability, 331
gsmToUMTSServiceHo, 418 minNbOfTDMA, 354
handOver from signalling channel, 311 minTimeQualityIntraCellHO, 414
hoMargin, 311 missDistWt, 309
hoMarginAMR, 441 missRxLevWt, 303
hoMarginAMRUTRAN, 419 missRxQualWt, 301
hoMarginBeg, 312 mobileAllocation, 392
hoMarginDist, 312 mobileCountryCodeUTRAN, 422
hoMarginDistUTRAN, 420 mobileNetworkCodeUTRAN, 422
hoMarginRxLev, 313 modeModifyMandatory, 361
hoMarginRxLevUTRAN, 419 msBtsDistanceInterCell, 333
hoMarginRxQual, 313 msRangeMax, 333
hoMarginRxQualUTRAN, 419 msTxPwrCCH, 285
hoMarginTiering, 409 msTxPwrMax, 317
hoMarginTrafficOffset, 314 msTxPwrMax2ndBand, 339
hoMarginTrafficOffsetUTRAN, 420 msTxPwrMaxCell, 318
hoMarginUTRAN, 419 multi band reporting, 395
hoPingpongCombination, 314 nbLargeReuseDataChannels, 410
hoPingpongCombinationUTRAN, 420 nbOfRepeat, 383
hoPingpongTimeRejection, 315 nCapacityFRRequestedCodec, 440
hoPingpongTimeRejectionUTRAN, 421 neighDisfavorOffset, 416
hoppingSequenceNumber, 391 new power control algorithm, 339
hoRejectionTimeOverloadUTRAN, 421 nFRRequestedCodec, 440
hoSecondBestCellConfiguration, 316 nHRRequestedCodec, 440
hoTraffic_bsc, 316 noOfBlocksForAccessGrant, 383
hoTraffic_bts, 316 noOfMultiframesBetweenPaging, 384
hrAMRPriority, 430 notAllowedAccessClasses, 355
hrCellLoadEnd, 427 numberOfPwciSamples, 410
hrCellLoadStart, 427 numberOfSlotsSpreadTrans, 385
hrPowerControlTargetMode, 431, 432 numberOfTCHFreeBeforeCongestion, 355
hrPowerControlTargetModeDl, 432 numberOfTCHFreeToEndCongestion, 356
incomingHandOver, 317 numberOfTCHQueuedBeforeCongestion, 356
interBscDirectedRetry, 360 numberOfTCHQueuedToEndCongestion, 356
interBscDirectedRetryFromCell, 360 offsetLoad, 319
interCellHOExtPriority, 352 offsetPriority, 319
interCellHOIntPriority, 353 offsetPriorityUTRAN, 422
interferenceType, 409 otherServicesPriority, 357
interferer cancel algo usage, 406 pagingOnCell, 386
intraBscDirectedRetry, 361 pcmErrorCorrection, 408
intraBscDirectedRetryFromCell, 361 penaltyTime, 286
Nortel confidential

powerBudgetInterCell, 320 selfAdaptActivation, 415

powerControlIndicator, 292 selfTuningObs, 411
powerIncrStepSizeDL, 340 servingBandReporting, 296
powerIncrStepSizeUL, 340 servingBandReportingOffset, 297
powerRedStepSizeDL, 340 servingfactorOffset, 415
powerRedStepSizeUL, 341 siteGsmFctList, 405
preemptionAuthor, 358 small to large zone HO priority, 368
pRequestedCodec, 441 smartPowerManagementConfig, 451
preSynchroTimingAdvance, 334 smartPowerSwitchOffTimer, 451
priority, 357 smsCB, 413
processorLoadSupConf, 394 speechMode_bts, 412
pwciHreqave, 411 speechMode_signallingPoint, 412
qsearchC, 294 standard indicator AdjC_adjacentCellHandover,
radChanSelIntThreshold, 372 396
radioAllocator, 428 standard indicator
radioLinkTimeout, 298 AdjC_adjacentCellReselection, 397
radResSupBusyTimer, 374 standardIndicator, 399
radResSupervision, 374 synchronized, 322
radResSupFreeTimer, 374 t3101, 378
reportTypeMeasurement, 296 t3103, 379
retransDuration, 386 t3107, 379
rlf1, 299 t3109, 380
rlf2, 300 t3111, 380
rlf3, 300 t3121, 424
rNCId, 422 t3122, 381
rndAccTimAdvThreshold, 334 temporaryOffset, 288
runCallClear, 335 thresholdInterference, 373
runHandOver, 320 timeBetweenHOConfiguration, 322
runPwrControl, 342 timerPeriodicUpdateMS, 381
rxLevAccessMin, 287 tnOffset, 445
rxLevDLIH, 324 trafficPCMAllocationPriority, 393
rxLevDLPBGT, 329 transceiver equipment
rxLevDLPbgtUTRAN, 423 class_transceiverEquipment, 368
rxLevHreqave, 303 transceiver equipment class_transceiverZone,
rxLevHreqaveBeg, 304 369
rxLevHreqt, 304 transceiverZone, 369
rxLevMinCell, 321 uMTSAccessMinLevel, 289
rxLevMinCellUTRAN, 423 uMTSReselectionARFCN, 290
rxLevNCellHreqaveBeg, 307 uMTSReselectionOffset, 290
rxLevULIH, 324 uMTSSearchLevel, 290
rxLevWtsList, 305 uplinkPowerControl, 342
rxNCellHreqave, 307 uRxLevDLP, 342
rxQualAveBeg, 416 uRxLevULP, 343
rxQualDLIH, 325 uRxQualDLP, 343
rxQualHreqave, 301 uRxQualULP, 343
rxQualHreqt, 302 wPSManagement, 444
rxQualULIH, 325 wPSQueueStepRotation, 444
rxQualWtsList, 302 zone Tx power max reduction, 370
sacchPowerOffset, 443 zoneFrequencyHopping, 393
sacchPowerOffsetSelection, 443 zoneFrequencyThreshold, 393
scramblingCode, 423
Z END OF DOCUMENT Y
Nortel confidential

V17.0 BSS (Access) Parameters User Guide - bPUG

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

V17.0 BSS (Access) Parameters User Guide - bPUG

Uploaded by

Copyright:

Available Formats

V17.

0 BSS Parameter User Guide (BPUG)

Copyright© 2008 Nortel Networks, All Rights Reserved

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 2/629

System release: GSM/BSS V16

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 3/629

System release: GSM/BSS V15

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 4/629

System release: GSM/BSS V14

System release: GSM/BSS V13

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 5/629

System release: GSM/BSS V12

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 6/629

1. ABOUT THIS DOCUMENT .........................................................................................................16

1.1. OBJECT ..................................................................................................................................16

2. RELATED DOCUMENTS ............................................................................................................22

2.1. APPLICABLE DOCUMENTS ........................................................................................................22

3. CLASSIFICATION OF BSS PARAMETERS ..............................................................................25

3.1. PARAMETER LIST ....................................................................................................................25

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 7/629

3.4.30 Microcellular algorithm ..................................................................................................39

4.1. INTRODUCTION .......................................................................................................................43

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 8/629

4.5.10 Note on Rxlev Uplink/Downlink difference ....................................................................64

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 9/629

4.11.3 Barring of access class .............................................................................................. 154

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 10/629

4.20.2 Feature benefits ......................................................................................................... 217

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 11/629

4.31.4 Post V17 Behaviour ................................................................................................... 280

5. ALGORITHM PARAMETERS .................................................................................................. 284

5.1. INTRODUCTION .................................................................................................................... 284

6. ENGINEERING ISSUES........................................................................................................... 451

6.1. GSM/GPRS TS SHARING: PRIORITY HANDLING AND QUEUING ............................................. 451

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 12/629

6.2. LAYER 1 MANAGEMENT: CHANGES BETWEEN V1 AND V2 ...................................................... 454

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 13/629

6.20.1 Frequency band favouring ......................................................................................... 512

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 14/629

6.32. AMR FIELD FEEDBACK ........................................................................................................ 555

7. APPENDIX A: MAIN EXCHANGE PROCEDURES AT BSC LEVEL...................................... 604

7.1. ESTABLISHMENT PROCEDURE .............................................................................................. 604

8. APPENDIX B: ERLANG TABLE.............................................................................................. 615

9. ABBREVIATIONS & DEFINITIONS ......................................................................................... 618

9.1. ABBREVIATIONS ................................................................................................................... 618

10. INDEX ....................................................................................................................................... 627

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 15/629

1. ABOUT THIS DOCUMENT

1.3. AUDIENCE FOR THIS DOCUMENT

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 16/629

1.5. DOCUMENT STRUCTURE

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 17/629

1.6. UPDATES TO PREVIOUS RECOMMENDATIONS

1.6.1 BETWEEN V16 AND V17

1.6.2 BETWEEN V15.1.1 AND V16

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 18/629

1.6.3 BETWEEN V15.1 AND V15.1.1

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 19/629

1.6.4 BETWEEN V15.0 AND V15.1.

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 20/629

Serving factor offset

PE/DCL/DD/000036 17.03 / EN Standard 03/03/2008 Page 21/629

2.1. APPLICABLE DOCUMENTS