Capacity Enhancing Techniques and Multi Layer Systems

CHAPTER 1
CHAPTER 2
CHAPTER 3
CHAPTER 4
CHAPTER 5
TRAINING MANUAL COURSE TITLE CAPACITY ENHANCING TECHNIQUES AND MULTILAYER SYSTEMS INC HR
VERSION 1 REV 1 GSM SOFTWARE RELEASE 7
FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED
COURSE CODE SYS12
VERSION 1 REV 1 GSM SOFTWARE RELEASE 7
WILL NOT BE UPDATED
TRAINING MANUAL COURSE TITLE CAPACITY ENHANCING TECHNIQUES AND MULTILAYER SYSTEMS INC HR
COURSE FOR TRAINING CODE PURPOSES ONLY SYS12 THIS MANUAL
GSM Software Release GSR7
Course Code SYS12 Course title Capacity Enhancing Techniques and Multilayer Systems inc HR
E Motorola 2002 All Rights Reserved Printed in the UK.
EMOTOROLA LTD. 2004
Course Code SYS12: Course title Capacity Enhancing Techniques and Multilayer Systems inc HR FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED
Version 1 Rev 0
Copyrights, notices and trademarks

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey license under its patent rights of others.
Trademarks
and MOTOROLA are registered trademarks of Motorola Inc. Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc. All other brands and corporate names are trademarks of their respective owners.
. . .
ii
EMOTOROLA LTD. 2004
Version 1 Rev 0
Contents
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 3 4 5 8 9
Chapter 1 Introduction to Capacity Enhancing Techniques and Multilayer Systems

Introduction to Capacity Enhancing Techniques and Multilayer Systems . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reuse Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sectorisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 x 3 Frequency Reuse Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sectorisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 x 6 Frequency Reuse Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saturation point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcellular Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcellular Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola PBGT Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcellular Techniques, cont., . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adaptive Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiband Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adaptive MultiRate (AMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMR Full Rate Channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMR Half Rate Channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Half Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Concentric Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of Concentric Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction of carriers on different frequency bands . . . . . . . . . . . . . . . . . . . . . . . Coincident Multiband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single BCCH for Dual Band Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directed Retry and Congestion Relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directed retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Congestion relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2004
11
13 13 14 14 16 16 16 18 18 110 110 112 112 112 114 116 116 116 118 118 120 122 124 124 124 124 124 126 126 128 128 128 130 130 130
iii
Version 1 Rev 0
Extended Range Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
132
Chapter 2 Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multipath Fading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Hopping Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Band Frequency Hopping (BBH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synthesiser Frequency Hopping (SFH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Hopping Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . chg_hop_params . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Redefinition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Hopping to Enhance Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Reuse Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aggressive Frequency Reuse in SFH System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Guidelines for SFH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aggressive Frequency Reuse in SFH System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Guidelines for SFH using 1x3 Frequency Reuse . . . . . . . . . . . . . . . . . . . . . . . . SFH 1x3 Frequency Reuse Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Guidelines for SFH using 1x1 Frequency Reuse . . . . . . . . . . . . . . . . . . . . . . . . SFH 1x1 Frequency Reuse Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comparisons between 1x3 and 1x1 Frequency Reuse Patterns . . . . . . . . . . . . . . . . . . . Frequency Reuse in Baseband Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Progressive Reuse Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Homogeneous Reuse Pattarn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Rules for BBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity Gains for SFH and BBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimisation after Frequency Hopping Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbour List Optimisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Optimisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommendations for hopping systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXQUAL Hopping parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF Hardware Optimisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21 21 22 22 22 24 26 28 212 212 214 216 218 220 222 222 223 224 224 226 226 229 231 231 231 231 233 233 235 237 237 239 239 239 239 239 241 241 243
Chapter 3 Deployment of Microcellular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deployment of Microcellular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
31
33 33
EMOTOROLA LTD. 2004
Version 1 Rev 0
Introduction to Microcellular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What are microcells? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The street canyon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcell applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MultiLayered System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combined cell handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hotspots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hotspots handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handovers to/from hotspot cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handovers to the hotspot cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling Handovers in Hotspots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fast moving MSs entering a hotspot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSs leaving a hotspot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Idle Mobile Behaviour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Association of mobiles to micro/macro layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods of controlling reselection into a cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell reselection C2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell reselection C2 Continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selective cellbar on microcells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C2 reselection exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Effects of Broadcasting Separate BA Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Broadcasting separate BA lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Method 1: (see table opposite) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Method 2: (see table opposite) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The layered Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BA Lists Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34 34 34 34 34 36 38 310 312 312 312 312 314 314 314 316 316 318 320 322 324 326 328 328 328 328 330 332
Chapter 4 Microcellular Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Microcellular Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcellular Handover Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macro%Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macro%Micro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Micro%Micro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Micro%Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Current Motorola Handover Decision Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . hreqave and hreqt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pointing Averaging Mechanisms to Decision Processes . . . . . . . . . . . . . . . . . . . . . . . . . . use_neighbor_pbgt_hreqave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbour cell : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Seven Motorola Microcellular Handover Procedures . . . . . . . . . . . . . . . . . . . . . . . . . Type 1 Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PBGT algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink RXLEV only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2004
41
43 43 44 44 44 44 44 46 48 410 412 412 416 418 418 420
v
Version 1 Rev 0
Adapted Power Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uplink Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example One Equally Sized Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example Two Large server, Small Neighbour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Type 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power budget exercise part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power budget exercise part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Criteria 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Criteria 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Type 1 Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Type 2 Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Type 3 Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR5 Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Type 4 Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Type 5 Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Algorithm Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimisation of type 5 handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Type 6 Algorithm (Delay PBGT using Dynamic ho_margin) . . . . . . . . . . . . . . . . . . . . . . . Description of variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Algorithm Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Scenario for Adjacent Channels (Both BCCH Carriers) . . . . . . . . . . . . . . . . . . Type 7 Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Algorithm Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interference Avoidance Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting of Candidate List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Margin Per Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Margin Per Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXQUAL and Microcell Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timed Offset upon RXQUAL Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Micro Micro Quality Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handovers Adaptive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adaptive Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adaptive Receive Level handovers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adaptive Receive Quality Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hopping Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adaptive Power Budget Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cumulative Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example Application Scenarios for Handover Procedures . . . . . . . . . . . . . . . . . . . . . . . . Imperative handover from microcell to macrocell . . . . . . . . . . . . . . . . . . . . . . . . . . Handdown from macrocell to microcell (handover to a type 5 neighbour) . . . . . Handover to a type 3 neighbour (round the corner handover) . . . . . . . . . . . . . . . . Handover to a lineofsight neighbour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applying the algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
422 424 424 426 430 430 430 432 434 436 436 438 440 440 442 444 444 446 448 448 448 450 452 452 456 456 458 460 460 460 463 463 465 465 467 467 469 469 471 471 473 473 473 475 475 475 475 475 475
EMOTOROLA LTD. 2004
Version 1 Rev 0
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . add_neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Separate BA Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
477 484 484 484
Chapter 5 Capacity Enhancing Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Capacity Enhancing Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directed Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Congestion relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Congestion Handover Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Directed Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Emergency and EGSM calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcellular purchasable option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directed Retry and External Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Congestion relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Congestion Relief Standard Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Congestion Relief Type 2 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Associated Congestion Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Concentric Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Based Concentric Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover to Inner Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Based Concentric Cells HO to Inner Zone Power Level . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover to Inner Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Concentric Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover to Outer Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interference Based Concentric Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interference Based Concentric Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Budget Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Power Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interference Based Algorithm Handover to Inner Zone . . . . . . . . . . . . . . . . . . . . . . . . . Direct Inner Zone Threshold and Neighbour Report Timer . . . . . . . . . . . . . . . . . . . . . . . . Interference Based Algorithm Handover to Outer Zone . . . . . . . . . . . . . . . . . . . . . . . . . Power Control When Using Interference Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Concentric Cells Channel Allocation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . outer_zone usage_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . intra_cell_handover_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Emergency call preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Immediate Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2004
51
51 51 52 52 54 56 56 56 56 58 510 512 512 512 514 516 518 518 520 520 522 522 522 524 524 526 526 528 528 528 530 532 534 536 538 538 538 538 538 538
vii
Version 1 Rev 0
Multiband Intercell Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiband Intercell Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiband Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced SDCCH to TCH (preferred band) Assignment . . . . . . . . . . . . . . . . . . . . . . . . . Multiband Neighbour Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ALM for EGSM Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EGSM Layer Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbour Reordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ALM for EGSM Carriers Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coincident Multiband Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Coincident Multiband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coincident Multiband External Neighbour Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single BCCH for Dual Band Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single BCCH for Dual Band Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Overview (Continued) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Primary Band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Secondary band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dependancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modification Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . inner_zone_alg <value>cell=<cell_desc> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipping DRI and RTF groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outer zone usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dual band Inner Zone use Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Propagation Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power losses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dual Band Inner Zone Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dual Band Inner Zone Use Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dual Band Inner Zone Use Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Power Control on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Power Control off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS Power Control on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS Power Control off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handovers to n/bours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling the Dual Band Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
540 541 544 546 548 550 552 552 552 552 554 554 554 558 558 558 560 562 562 564 564 566 566 568 568 568 568 570 570 570 570 572 572 572 574 576 576 578 578 578 578 578 578 580 580 582
EMOTOROLA LTD. 2004
Version 1 Rev 0
Handover and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Budget Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Budget Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Power Level Inner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit Power Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dependancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EGSM Layer Management Within a Dualband Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Range Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeslot Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Range Cell parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Range Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intracell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intercell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF Planning Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximizing Output Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximizing Receiver Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
583 584 584 584 584 584 586 588 590 592 594 594 594 596 598 5100
Chapter 6 Adaptive MultiRate and HalfRate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Adaptive MultiRate and Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adaptive MultiRate (AMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMR Full Rate Channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMR Half Rate Channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Half Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Active Codec Set Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMR HalfRate Further Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RTF Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Allocation for AMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Force HalfRate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reconfiguration of Existing FullRate Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reservation of HalfRate Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMR Full Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMR Half Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/Disabling Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMR FR/HR Commands to Specify ACS and Associated Parameters . . . . . . . . . . . . . . AMR FR/HR Commands to Specify ACS and Associated ParametersContd . . . . . . . Downlink Adaptation Change Minimum Time Period . . . . . . . . . . . . . . . . . . . . . . . MS Monitor Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Adaptation MS Monitor Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (AMR) Half Rate Handover and Power Control Parameters . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2004
61
61 61 62 64 64 64 64 64 64 66 68 68 610 610 612 612 614 616 618 620 622 624 626 628 628 630
ix
Version 1 Rev 0
AMR or GSM HalfRate Intracell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMR or GSM Half Rate Intracell Handover Hop Count . . . . . . . . . . . . . . . . . . . . . . . . . .
632 634
Chapter 7 Planning of Microcells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Planning of Microcells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Steps in Planning Microcellular Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identification of requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quality of Service Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic capacity enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Erlang . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Erlang per subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic Capacity Enhancement Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dimensioning of Signalling Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning for Hotspots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detection of Hotspot cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macro Frequency Reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for Calculating Link Budgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum Coupling Loss Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Designing with Close Proximity Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modulation Spectrum dropoff with frequency Offset . . . . . . . . . . . . . . . . . . . . . . . Designing with Close Proximity Mobiles Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uplink Budget Calculation Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link budget with Close Proximity Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Budget without Close proximity Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Budget for Balanced Downlinks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Budget with close Proximity Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Budget without Close Proximity Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The InBuilding Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to picocellular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Picocellular Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inbuilding Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Propagation from outside to inside . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InBuilding RF Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF repeater with cell enhancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation from Tall Buildings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directional antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMNI antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x
71
71 71 72 72 74 76 76 76 76 76 78 710 712 712 714 714 716 718 720 722 722 724 726 726 726 726 728 728 728 730 730 730 732 732 734 735 736 738 738 740
EMOTOROLA LTD. 2004
Version 1 Rev 0
Installation of Microcell Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizonmicro2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCellcity & MCellcity+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna types for Picocellular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directional antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Omni antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Designing with Radiating Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . G-1
742 742 744 744 746 746 746 746 748
EMOTOROLA LTD. 2004
xi
Version 1 Rev 0
xii
EMOTOROLA LTD. 2004
Version 1 Rev 0
List of Figures
EMOTOROLA LTD. 2004
xiii
Version 1 Rev 0
List of Tables
xiv
EMOTOROLA LTD. 2004
Version 1 Rev 0
General information
General information
Important notice
If this manual was obtained when attending a Motorola training course, it will not be updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then corrections will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel in the operation, installation and maintenance of the Motorola cellular infrastructure equipment and ancillary devices. It is recommended that all personnel engaged in such activities be properly trained by Motorola. WARNING Failure to comply with Motorolas operation, installation and maintenance instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by Motorola, although they can be used to supplement and enhance the knowledge gained through such training.
ETSI standards
The standards in the table below able are protected by copyright and are the property of the European Telecommunications Standards Institue (ETSI). ETSI specification number GSM 02.60 GSM 03.60 GSM 03.64 GSM 04.01 GSM 04.02 GSM 04.03 GSM 04.04 GSM 04.05 GSM 04.06 GSM 04.07 GSM 04.08 GSM 04.10 GSM 04.11 GSM 04.12 GSM 04.13 GSM 04.60 GSM 04.64 GSM 04.65 GSM 08.01 GSM 08.02 GSM 08.04 GSM 08.06 GSM 08.08 GSM 08.16 GSM 08.18 GSM 08.51 GSM 08.52 GSM 08.54 GSM 08.56 GSM 08.58 GSM 09.18 GSM 09.60
Figures from the above cited technical specifications standards are used, in this training manual, with the permission of ETSI. Further use, modification, or redistribution is strictly prohibited. ETSI standards are available from http://pda.etsi.org/pda/ and http://etsi.org/eds/
EMOTOROLA LTD. 2004 1
General information
Version 1 Rev 0
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and GPRS network is encrypted. In order to comply with the export and import requirements of particular countries, this encryption occurs at different levels as individually standardised, or may not be present at all in some parts of the network in which it is normally implemented. The manual set, of which this manual is a part, covers encryption as if fully implemented. Because the rules differ in individual countries, limitations on the encryption included in the particular software being delivered, are covered in the Release Notes that accompany the individual software release.
Cross references
Throughout this manual, cross references are made to the chapter numbers and section names. The section name cross references are printed bold in text. This manual is divided into uniquely identified and numbered chapters that, in turn, are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents.
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to represent keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows: CTRLc ALTf | CR or RETURN Press the Control and c keys at the same time. Press the Alt and f keys at the same time. Press the pipe symbol key. Press the Return key.
EMOTOROLA LTD. 2004
Version 1 Rev 0
Reporting safety issues
Reporting safety issues

Introduction
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises: 1. 2. 3. Make the equipment concerned safe, for example by removing power. Make no further attempt to adjust or rectify the equipment. Report the problem directly to the Customer Network Resolution Centre, Swindon +44 (0)1793 565444 or China +86 10 68437733 (telephone) and follow up with a written report by fax, Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax). Collect evidence from the equipment under the guidance of the Customer Network Resolution Centre.
4.
EMOTOROLA LTD. 2004
Warnings and cautions
Version 1 Rev 0
Warnings and cautions

Introduction
The following describes how warnings and cautions are used in this manual and in all manuals of this Motorola manual set.
Warnings
Definition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents, as well as those inherent in the equipment.
Example and format

WARNING Do not look directly into fibre optic cables or data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola manuals. Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals, or on the equipment itself, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Cautions
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of equipment within a system. However, this presents no danger to personnel.
Example and format

CAUTION Do not use test equipment that is beyond its due calibration date; arrange for calibration to be carried out.
EMOTOROLA LTD. 2004
Version 1 Rev 0
General warnings
General warnings
Introduction
Observe the following specific warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola manuals: S S S S S S S S Potentially hazardous voltage Electric shock RF radiation Laser radiation Heavy equipment Parts substitution Battery supplies Lithium batteries
Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning labels must not be removed, painted over or obscured in any way.
EMOTOROLA LTD. 2004
General warnings
Version 1 Rev 0
Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will be incorporated into procedures as applicable. These must be observed by all personnel at all times when working with the equipment, as must any other warnings given in text, in the illustrations and on the equipment.
Potentially hazardous voltage

WARNING This equipment operates from a hazardous voltage of 230 V ac single phase or 415 V ac three phase supply. To achieve isolation of the equipment from the ac supply, the ac input isolator must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989 (UK), or to the relevant electricity at work legislation for the country in which the equipment is used. NOTE Motorola GSM equipment does not utilise high voltages.
Electric shock
WARNING Do not touch the victim with your bare hands until the electric circuit is broken. Switch off. If this is not possible, protect yourself with dry insulating material and pull or push the victim clear of the conductor. ALWAYS send for trained first aid or medical assistance IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries and even death, may result. Direct electrical contact can stun a casualty causing breathing, and even the heart, to stop. It can also cause skin burns at the points of entry and exit of the current. In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS send for trained first aid or medical assistance IMMEDIATELY. If the casualty is also suffering from burns, flood the affected area with cold water to cool, until trained first aid or medical assistance arrives.
RF radiation
WARNING High RF potentials and electromagnetic fields are present in this equipment when in operation. Ensure that all transmitters are switched off when any antenna connections have to be changed. Do not key transmitters connected to unterminated cavities or feeders.
Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are: S S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz. CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10 kHz to 300 GHz).
EMOTOROLA LTD. 2004
Version 1 Rev 0
General warnings
Laser radiation
WARNING Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
Lifting equipment
WARNING When dismantling heavy assemblies, or removing or replacing equipment, a competent responsible person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for these operations.
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for these operations. When equipments have to be manhandled, reference must be made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation for the country in which the equipment is used.
Parts substitution
WARNING Do not install substitute parts or perform any unauthorized modification of equipment, because of the danger of introducing additional hazards. Contact Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
WARNING Do not wear earth straps when working with standby battery supplies.
Lithium batteries
WARNING Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithium batteries must not be removed or replaced. Any boards containing defective lithium batteries must be returned to Motorola for repair.
Contact your local Motorola office for how to return defective lithium batteries.
EMOTOROLA LTD. 2004
General cautions
Version 1 Rev 0
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the equipment described in the Motorola manuals. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
CAUTION Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
CAUTION Motorola equipment contains CMOS devices. These metal oxide semiconductor (MOS) devices are susceptible to damage from electrostatic charge. See the section Devices sensitive to static in the preface of this manual for further information.
EMOTOROLA LTD. 2004
Version 1 Rev 0
Devices sensitive to static
Devices sensitive to static

Introduction
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation that is susceptible to damage from electrostatic charge. Such a charge applied to the leads of the device could cause irreparable damage. These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulation packing material or by use of unearthed soldering irons. MOS devices are normally despatched from the manufacturers with the leads shorted together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Provided the leads are shorted it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced, observe the following precautions when handling the replacement: S S S S S S Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. All metal tools should be used and when not in use they should be placed on an earthed surface. Take care when removing components connected to electrostatic sensitive devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and pins, they should be transferred directly from their packing to the equipment (or the other way around) and never left exposed on the workbench.
EMOTOROLA LTD. 2004
Chapter 1
Introduction to Capacity Enhancing Techniques and Multilayer Systems
EMOTOROLA LTD. 2004
11
Version 1 Rev 0
12
EMOTOROLA LTD. 2004
Version 1 Rev 0

Objectives
On completion of this section the student will have: S S Discussed the reasons why a multilayer solution would be adopted in a network Appreciate the solutions Motorola offers to increase capacity in a network
EMOTOROLA LTD. 2004
13
Introduction
Version 1 Rev 0
Introduction
Motorola has a wide variety of capacity enhancing solutions in RF technology and design approach S S S S S S S S S S S S S S Macrocellular Technology IOS Frequency Hopping Microcellular Technology InBuilding Solutions Microcellular Handover Algorithms Multilayer Technology Dualband Technology Congestion Relief Concentric Cells Coincident Multiband Single BCCH for Dual Band Cells Extended Range Cells Adaptive MultiRate
All these solutions will be discussed in this course in detail, with the exception of microcellular technology that is reviewed, as it is covered in depth on previous prerequisite courses.
Considerations
These capacity enhancing solutions have there own characteristics and requirements in design and implementation. To choose the best solution for customer requirements and network specification, the following should be taken into account. S S S S S Available Frequency Spectrum Capacity Requirements Mobile Handset Availability Network Environment Ease of Future Expansion
Each network has different drivers for both growth and expansion. National constraints of frequency, tariffing, subscriber base and competition will determine the cell card. Every network is different and every network will require different feature deployment. This course aims to provide the tool box of features to effect growth in a given network.
14
EMOTOROLA LTD. 2004
Version 1 Rev 0
Introduction
Introduction
Frequency Spectrum Availability GSM900 Macro Layer IOS Frequency Hopping Concentric Cells Dual band Technology (MS Capable) Coincident mb/Single BCCH Capacity Requirement Microcellular Techniques InBuilding Solutions Microcellular Handover Algorithms DCS1800 Micro Layer Congestion Relief Adaptive MultiRate Network Environment Multilayer Technology Extended range Cells Ease of Future Expansion
sys12_ch01_01a
EMOTOROLA LTD. 2004
15
Frequency Spectrum
Version 1 Rev 0
Frequency Spectrum
Reuse Pattern
Each network will have a total number of radio frequencies available. This allocation is split into a number of channel groups or sets. If the frequency spectrum is contiguous then guard channels are needed. Each channel group is solely for a particular type of usage. For example one channel group could be used for the BCCH of macrocells, another for nonBCCH, another for microcells etc. This is a typical single layer with isolated microcells frequency segmenation. In the case of the multilayer scenario, the segmentation highrise macrocell, streetlevel macrocell, microcell layer and indoor picocell. These channel groups are assigned on a per cell basis in a regular pattern that repeats across all of the cells. Thus each set may be reused many times throughout the coverage area, giving rise to a particular reuse pattern eg, 7 cell reuse pattern.
Frequencies
GSM Tx 935 960 MHz 124 RF carriers Rx 890 915 MHz EGSM Tx 925 960 MHz 174 RF carriers Rx 880 915 MHz DCS1800 Tx 1805 1880 MHz 374 RF carriers Rx 1710 1785 MHz GSM850 Tx 869.2 893.8 MHz 122 RF carriers Rx 824.2 848.8 MHz
16
EMOTOROLA LTD. 2004
Version 1 Rev 0
Frequency Spectrum
Frequency Spectrum
3 4 1 5 6 3 4 1 5 7 2 7 5 6 2 4 1 7 5 6 3 2 4 1 3
S Frequency Reuse Pattern (omnicell) S 7 Cell Reuse
SYS12_Ch01_02
EMOTOROLA LTD. 2004
17
Sectorisation
Version 1 Rev 0
Sectorisation
The capacity of any network is a function of the number of RF channels available and the number of times those frequencies can be reused in a given area and the desired blocking probability. One way to increase the capacity of the network is by frequency reuse. Frequency reuse can be achieved by sectorisation of existing cell sites. To increase the coverage and capacity of a network built up of omnidirectional cells, the conventional approach is to sectorise the existing cells (i.e. restrict the coverage area of each cell to a sector of 120 or 60 of arc thereby allowing increased control of coverage and interference). In this way, it is possible to reuse frequencies over smaller distances, allowing a significant increase in network capacity, whilst maintaining the C/I ratio at an acceptable level.
4 x 3 Frequency Reuse Pattern

The diagram opposite shows a four site reuse pattern with 120 sectorised cells. This is ideal for a new system with moderate subscriber capacity. For the future, if the network becomes increasingly dense additional sectorisation and site splitting could be used as a methodology. If the operator has only 24 carriers allocated for their use, they will be restricted theoretically to 2 carriers per cell. This means only 16 channels, which is not a lot if you consider each cell could contain several office blocks. A solution to this problem could be the introduction of microcells, which can mean a greater frequency reuse pattern.
18
EMOTOROLA LTD. 2004
Version 1 Rev 0
Sectorisation
Four Site Pattern
Reuse
a1 a2 b1 b2 a3
a1 a2 a3
b3
c1 c2
d1 d2 d3
c3
120 Sectors
SYS12_Ch01_03
EMOTOROLA LTD. 2004
19
Sectorisation
Version 1 Rev 0
Sectorisation
2 x 6 Frequency Reuse Pattern
A further solution to network operators capacity problems may be the introduction of six sector operation. This technique permits six cells to be controlled from a single base site controller. Six sector operation can be used to deliver capacity benefits to EGSM900 operators and coverage benefits to DCS1800 operators. It employs narrow band antennas which utilize higher transmitted power and a narrower beam width coverage than standard antennas. The use of narrow beam antennas results in a reduction in cochannel interference, which in turn allows tighter frequency reuse and greater network capacity. Secondly, it allows a DCS1800 operator to achieve a greater range, due to the high transmit power and therefore achieve coverage with fewer cell sites. Moreover, penetration into buildings is improved for both EGSM900 and DCS1800.
110
EMOTOROLA LTD. 2004
Version 1 Rev 0
Sectorisation
TwoSite Pattern
a1 a6 b1 b6 b2 a2
a5 a4 b1 b6
a3
b5 b4 a1 a6
b3
b2
b5 a2 b4
b3
a5 a4
sys12_ch01_04
a3
60 Sectors
EMOTOROLA LTD. 2004
111
Cell splitting
Version 1 Rev 0
Cell splitting
Later, as the subscriber base grows within a confined area, (usually a town or city), it is necessary to provide even more capacity in some areas by subdividing the cells of the network to position more cells within the same area. This, in turn, reduces the coverage area of some of the existing cells by introducing antenna tilt techniques. Finally, after the number of cells has increased, and the area of coverage of each cell decreases to the saturation point, another approach to the provision of increased capacity is necessary.
Saturation point
At saturation point investment in expensive rooftop sites has already become considerable, and any ability to increase capacity further or to cover holes that exist in the network in areas of already heavy subscriber demand by conventional macrocellular means is now exhausted. Subscriber access to the network in these areas is likely to become a great deal more problematic, as new subscribers only increase the network difficulties. Time of access to the network in these saturation areas will increase steadily and to aggravate matters further the quality of service as perceived by the subscriber will fall at least as fast. Worse still, there may be small areas at street level where it is difficult or maybe impossible to provide adequate coverage because interference restricts further cell reduction. Call continuity for subscribers moving through such areas is likely to be poor and complaints from disappointed subscribers are likely to increase.
Cell size
The number of cells in any geographic area is determined by the number of mobile subscribers operating in that area. The maximum cell size is mainly determined by the distance radio waves can travel and the propagation delay this produces.
Large cells
Larger cells are mainly used in remote areas where there are few subscribers, using high transmission power.
Small cells
Smaller cells cover areas of dense subscriber traffic using low transmission power. These are usually used in urban areas. Some networks may have cells as small as two or three hundred meters radius in areas of high traffic.
Trade off large v small

Network operators wish to have their cells as large as possible to keep the cost of equipment down. They must also ensure that all those wishing to use the cell can gain access to it. The smaller the cell radius, the more handovers required and the chances of co and adjacent channel interference increases. It is harder to find physical locations for cells and antennas as you increase the number of traditional BSSs. All this has to be taken in to consideration when planning a network. The use of microcells may alleviate some of these problems.
112 EMOTOROLA LTD. 2004
Version 1 Rev 0
Cell splitting
Network Expansion
sys12_ch_01_05
EMOTOROLA LTD. 2004
113
Frequency Hopping
Version 1 Rev 0
Frequency Hopping
Frequency hopping was introduced as a technique to counter jamming and increase security of military communications. It basically operates by changing the frequency used at regular intervals. It has been adopted in GSM specifications due to being able to counter two specific problems: S Multipath Fading: Fading is more apparent at some frequencies and not so much at others, particularly for slow moving or stationary mobiles. By using different frequencies the probability of being continously affected by fading is reduced, so the transmission link quality is improved. This characteristic is normally referred as Frequency Diversity. Interference: If a neighbouring cell is transmitting at the same or adjacent frequencies then it will cause interference n the source cell. This situation can be avoided by using frequency hopping, because calls will move between different frequencies not equally effected by interfering signals.
The frequency is changed on a per timeslot basis, so all bits in a burst are transmitted in the same frequency.
114
EMOTOROLA LTD. 2004
Version 1 Rev 0
Frequency Hopping
Frequency Hopping
S Multipath Fading
(11)
S Interference
Same Channel Adjacent Channel 4 3
2 77 1 6
3 1 4 5 (11) 2 3 (10) 7 1
(11) 2
SYS12_Ch01_07
EMOTOROLA LTD. 2004
115
Microcellular Techniques
Version 1 Rev 0
Microcellular Systems
As capacity increases, cell size reduces at a rapid rate. The number of cells required increases until saturation point is reached when the available frequency resource and physical location of equipment limits what can be achieved with traditional cell planning techniques. Smaller cells also begin to stretch frequency reuse rules and the ability of locating carriers in close proximity to each other. djacent channel and cochannel criteria are stretched in a small cell environment, the ability to meet GSM specified levels are severely tested and restrict what can be achieved without significant degradation of network performance. These operational limitations restrict the minimum radius of a macrocell to about 500m, which is not enough to meet the capacity and coverage requirements of dense urban networks. Microcells have been developed to solve the problems described above. A microcell is a cell which is mounted below rooftop level. Radio wave propagation is determined by diffraction and scattering around buildings, the main rays propagating within street canyons. They have a radius of 300m or smaller and exhibit transmission behaviour, which differs from conventional large or small cells. Propagation is primarily line of sight and radio path loss increases sharply as the receiver moves out of sight of the transmitter. Microcells offer improved propagation properties, experience less severe fading and require lower transmitter powers than conventional macrocells.
Motorola PBGT Algorithms

At present there are seven PBGT algorithms that offer an intelligent product able to recognise the needs of the system and direct traffic according to resources and conditions of the network. To achieve this intelligent functionality, the PBGT algorithm may be configured on a perneighbour basis, allowing each neighbour to be processed following different criteria. What is configured is not the PBGT formula itself, but its surrounding conditions to trigger a handover. Type 1: Standard Configuration Type 2: Macro Neighbour of a Micro Cell via Imperative Handover Type 3: Around the Corner Type 4: Line of Sight Configuration Type 5: Qualified Neighbour Configuration (Time) Type 6: Dynamic Handover Margin Configuration (Time) Type 7: Adjacent Channel Neighbours
116
EMOTOROLA LTD. 2004
Version 1 Rev 0
Microcellular Handover Algorithms
LOS primarily Less severe fading Less transmit power PBGT Algorithms Type 1 to type 7 Adaptive handovers RXLEV RXQUAL PBGT
Small Radius Typically 100m or less
SYS12_Ch1_08
EMOTOROLA LTD. 2004
117
Microcellular Techniques, cont.,
Version 1 Rev 0

Adaptive Handovers
Normal handovers are triggered by a voting method such that if p from n of the most recent rolling averages meet a certain number, then the need for a handover is recognised. However, this standard method may be too slow to catch a rapidly deteriorating call. The alternative method of adaptive handovers now exists for Quality, Receive Level and Power Budget handovers. The adaptive handover method causes handovers to be recognized based on a cumulative area rather than a vote. The adaptive handover method enables handovers to occur more rapidly when conditions are deteriorating quickly, but less rapidly when conditions are only marginally poor.
118
EMOTOROLA LTD. 2004
Version 1 Rev 0
EMOTOROLA LTD. 2004
119
Multiband Environment
Version 1 Rev 0
Network operators now have the ability to utilize the GSM900,EGSM, DCS1800, PCS1900 and GSM850 frequency spectrum. Not only can this environment be supported by multiband telephones, but also by the ability of the Motorola network to support multiband intracell and intercell handovers. Multiband intercell and intracell handovers will provide the BSS with the ability to support intercell and intracell handovers where cells are operating in different frequency bands. In addition, the network operator will have the ability to deploy cells of differing frequency bands within the same BTS site(s).
120
EMOTOROLA LTD. 2004
Version 1 Rev 0
GSM 900
DCS 1800
GSM 900 DCS 1800 GSM 900
GSM 900 DCS 1800 GSM 900 GSM 900 DCS 1800 GSM 900 DCS 1800
PCS 1900
DCS 1800
DCS 1800
GSM 900
EGSM
DCS 1800 GSM 900 DCS 1800
GSM 900 DCS 1800
GSM 850
sys12_ch01_12
EMOTOROLA LTD. 2004
121
Half Rate
Version 1 Rev 0
Half Rate
The GSM Half Rate feature offers enhanced capacity over the air interface, corresponding to the proportion of mobiles within a coverage area that supports Half Rate. An air timeslot is split into two subchannels, each containing a half rate channel. Speech quality is considered inferior to other speech codecs but has a high penetration level (of GSM HR capable mobiles) due to its early introduction into the standards. Due to these large penetration levels it is considered a viable option for high density areas. A GSM HR call can fit within an 8kbps timeslot (an Ater channel) on the terrestrial resource from the BSC to the RXCDR, rather than the 16kbps timeslot required for FR calls. If a percentage of the active calls can be assumed to be HR, then efficiencies can be gained by reducing the number of terrestrial resources between the BSC and RXCDR. This is possible only if the BSC can dynamically allocate a timeslot to a CIC on an 8kbps/16kbps basis. This dynamic allocation is performed across a trunked interface between the BSC and a remote transcoder (RXCDR). This interface is called the Ater interface. The dynamic allocation is an enhancement to the existing Auto Connect mode feature, referred to as Enhanced Auto Connect mode. Enhanced Auto Connect is part of the AMR feature and is mentioned here only to point out that GSM HR will enjoy the same benefit. The backhaul requirements between the BTS and BSC may also be reduced to 8kbps as long as subrate (8K) switching is present at the BSC. Both GDP and GDP2 boards will be enhanced to support GSM HR. GDP will be introduced first, followed by GDP2 in a future release.
122
EMOTOROLA LTD. 2004
Version 1 Rev 0
Half Rate
Half Rate
5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5
Full Rate Speech
Half rate channel
5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5
Half rate channel
SYS12_ch1_13
EMOTOROLA LTD. 2004
123
Adaptive MultiRate (AMR)
Version 1 Rev 0

Adaptive MultiRate (AMR) is introduced in GSR7 and provides two modes of working AMR fullrate channel mode (AMR FR) and AMR halfrate channel mode (AMR HR).
AMR Full Rate Channel Mode

This mode of working provides higher speech quality in areas of poor RF conditions.
Full Rate Link Adaptation

AMR FR link adaption works in conjuction with the rest of the AMR feature set, namely AMR, Call downgrade on CIC capability mismatch and Enhanced GDP provisioning. It provides improved speech quality in poor RF environments by adapting the speech rates and level of error correction on a call. Speech quality is improved by reducing the speech rate and increasing the level of error correction in poor RF environment.
AMR Half Rate Channel Mode

This mode of working allows two AMR calls to be placed on a single air interface timeslot. This gives an increase in cell capacity with no additional hardware. However extra backhaul is required between BSC and BTS due to there being no 8kbps switching in release GSR7. There is also a lower QoS provided by AMR halfrate calls.
Half Rate Link Adaptation

AMR HR link adaption operates in a similar way to AMR FR link adaption. The differences are the bit rates of the HR codec modes supported, different initial HR codec mode and differnt associated uplink and downlink codec mode adaption thresholds and hystersis values.
124
EMOTOROLA LTD. 2004
Version 1 Rev 0
Dependant on: Enhanced GDP Provisioning Call downgrade on CIC capability mismatch
Up to 16 AMR half rate calls Up to 8 AMR full rate calls
MSC
RXCDR
BSC
BTS
Or a combination of the two.
Up to four codec modes can be included in FR and HR Active Codec Set Which Codec Mode used depends on RF conditions
For half rate rtf two E1 timeslots required
SYS12_amr_01
EMOTOROLA LTD. 2004
125
Concentric Cells
Version 1 Rev 0
Concentric Cells
Purpose of Concentric Cells
Concentric cells are a feature that has been developed to allow a regular frequency reuse pattern, for example 4 x 3. Or to have a super frequency reuse pattern, for example 2 x 3 or 1 x 3 superimposed upon it. These two groups have a single BCCH frequency operating in the same coverage area. The BCCH provides coverage to the entire area of the cell, this area is known as the outer zone (zone 0), this zone could also contain nonBCCH frequencies. The rest of the nonBCCH frequencies are contained in a smaller area with the overall coverage area, this area is known as the inner zone (zone 1). Zone 0 is reserved for carriers that transmit at maximum level. This cell structure provides increased capacity through more efficient reuse of the inner zone frequencies. The operator can select between two different use algorithms when defining zone 1 in a cell: S S Power based Algorithm Interference Based Algorithm
MS assignment to the inner or outer zone is based on the received signal level of the serving cell (powerbased algorithm) or a comparison of signal levels from the serving and neighbour cells (interference based algorithms). Transitions between zones is controlled using intracell procedures. Concentric cells are described in detail in chapter 5.
126
EMOTOROLA LTD. 2004
Version 1 Rev 0
Concentric Cells
Concentric Cells
Power Based Algorithm
Interference Based Algorithm
Zone 1 Inner Zone
Non BCCH Transmitting at lower power than BCCH or Having a tighter reuse pattern that reduces the useful coverage area of the carrier
SYS12_Ch01_14
Zone 0 Outer Zone
BCCH Broadcast at max tx level defined for that cell
Other non_BCCH carriers
EMOTOROLA LTD. 2004
127
Concentric Cells
Version 1 Rev 0
Implementation of Multiband
Introduction of carriers on different frequency bands
New carriers with a different frequency band can be introduced into an existing network. This effectively means that there are two sets of cells, but the equipment is located in the same geographical position. The two options below allow for a more refined solution to the implementation of multiband.
Coincident Multiband
This feature enables operators to install new radios in a different frequency band. This installation will turn an operators network into a multiband network. One obstacle to this type of upgrade is the investment in time and money already made by the operator in optimising the existing network. With the addition of a secondary network, with different propagation characteristics, this optimisation effort would have to be repeated. This can deter some operators, who want the extra capacity, from installing a multiband network. To avoid this problem of optimising two networks, it is logical that the new secondary network should complement the existing infrastructure. To achieve this, the software must be configurable enough to allow the new network to use the same cell boundaries established by the original network. This can be done by using mobilereported measurement reports of the primary network while established on the secondary network. This allows the mobile to be handled as if it were on the primary network, using the primarys boundaries and minimizing propagation characteristics differences, whilst not taking any primary network resources. This feature requires two BCCH carriers, one for each frequency band.
Single BCCH for Dual Band Cells

This is a feature developed in GSR 5 software release. GSM specifications allow the use of a common BCCH for different bands of operation when resources across all bands are colocated and synchronised. With this feature it is possible for carriers within a cell to be configured in different frequency bands.
128
EMOTOROLA LTD. 2004
Version 1 Rev 0
Concentric Cells
Concentric Cells Implementation with Dualband
Two sets of cells with the equipment in the same geographical position
Coincident Multiband
sys12_ch01_15
EMOTOROLA LTD. 2004
129
Directed Retry and Congestion Relief
Version 1 Rev 0

Directed retry and congestion relief are software based techniques which can be used to increase capacity in very dense cellular systems where there is significant coverage overlap from neighbouring cells. Calls in the overlap region can be maintained on more than one cell with sufficiently high quality.
Directed retry
Directed retry allows handover of a mobile station from an SDCCH of one cell directly to a TCH of another cell. A directed retry handover procedure may be initiated when a mobile station, which is assigned to a SDCCH, requires a traffic channel at a time when all TCHs in the same cell are busy. The system queues the traffic channel request and executes a selection process to determine whether any neighbouring cell is a valid candidate for receiving a directed retry handover.
Congestion relief
This procedure is activated when a mobile station assigned to an SDCCH requires a traffic channel and none are available. Two options are offered for deciding how many handover procedures are actually initiated. One option is that the number of handover procedures initiated is at most the number of outstanding requests for a TCH. The second option allows for initiation of a handover procedure for each mobile station that meets the modified criteria to support the feature.
130
EMOTOROLA LTD. 2004
Version 1 Rev 0
Congestion Relief Type 1
S
As many MSs handed out as in queue
Directed Retry
As many MS that qualify for handover, regardless of queue
MS handed over to qualified neighbour

MS established on SDCCH, but no TCHs available
Congestion Relief Type 2

SYS12_Ch01_16
EMOTOROLA LTD. 2004
131
Extended Range Cells
Version 1 Rev 0

This feature allows the range of a cell to extend from 35Km for normal range timeslots to an extended range of 121Km. This is used when the extra range is required, for example islands situated up to 121km from the coastline, with a low subscriber base.
132
EMOTOROLA LTD. 2004
Version 1 Rev 0
35 km
Normal range Cells
121 km
sys12_ch01_17
EMOTOROLA LTD. 2004
133
Version 1 Rev 0
134
EMOTOROLA LTD. 2004
Chapter 2
Frequency Hopping
EMOTOROLA LTD. 2004
21
Version 1 Rev 0
22
EMOTOROLA LTD. 2004
Version 1 Rev 0
Frequency Hopping
Frequency Hopping
Objectives
On completion of this section the student will have: S S S S Reviewed the implementation of baseband and synthesiser frequency hopping Discussed the planning considerations for frequency hopping Discussed the capacity gain that frequency hopping gives Discussed the optimisation issues relating to frequency hopping
EMOTOROLA LTD. 2004
21
Introduction
Version 1 Rev 0
Introduction
Frequency hopping has been around for many years and was first introduced in military communication systems to help secrecy and combat jamming techniques. The most basic explanation is the frequency changes at regular intervals. It has been adopted into GSM to increase capacity and quality in a network as subscriber growth continues. In addition to this frequency hopping can be rolled out very easily as it already utilises existing network infrastructure.
Multipath Fading
It is well known that when considering a cellular urban environment in most cases multipath propagation will be present and, as a consequence of that, important short term variations in the received level are frequent. This is called Rayleigh fading and results in quality degradation because some of the information will be corrupted. For a fast moving mobile, the fading situation can be avoided from one burst to another because it also depends on the position of the mobile so the problem is not so serious, but for a stationary one the reception may be permanently affected resulting in a very bad quality, even a drop call. Once the information is received by the mobile or the base station, the only weapon to cope with the disturbance produced by the fading (errors in the information bits) are the decoding and deinterleaving processes, with an effectiveness limited by the number of errors they have to deal with. Frequency hopping is able to take advantage of the frequency selective nature of the fading to decrease the number of errors, at the same time that they are temporally spread. If a mobile is stationary (or quasi stationary) at a point where a deep fade exists on the frequency in question and the system uses frequency hopping, the call will spend time on frequencies that are not fading at that point. As a result, the decoding and deinterleaving processes can more effectively remove the bit errors caused by bursts received whilst on the faded frequencies (errors will be randomly distributed instead of having long bursts of errors). This increase in effectiveness leads to a transmission quality improvement of the same proportion.
Interference
The second effect of frequency hopping is referred as averaging the interference experienced by the calls. Considering a non hopping system, the set of calls on the interferer cells which can interfere with the wanted call is fixed for the duration of those calls and some calls will be found with very good quality (no interference problems) and some others with very bad quality (permanent interference problems). With hopping, that set of interfering calls will be continually changing and the effect is that calls tend to experience an average quality rather than extreme situations of either good or bad quality (all the calls will suffer from a controlled interference but only for short and distant periods of time, not for all the duration of the call).
22
EMOTOROLA LTD. 2004
Version 1 Rev 0
Introduction
Introduction
Non hopping Error burst
Hopping freq 1 Radio selects burst Radio does not select burst Hopping freq 2
EMOTOROLA LTD. 2004
23
Frequency Hopping Basics
Version 1 Rev 0

Synthesiser Frequency Hopping (SFH) The transceiver unit retunes to a different operating frequency set (Tx & Rx) on each TDMA burst (approx 577s). The retuning will follow the sequence explained in the following section. In theory, there is no restriction on the number of frequencies the transceiver unit can hop on. However, GSM specifications limit the total number to 64 frequencies for a SFH transceiver unit. Base Band Hopping (BBH) In this method, the transceiver unit will always transmit at an assigned frequency. Frequency hopping is done by switching the information frame of one call from one radio, to another within a cell, per TDMA burst (approx 577s). The switching of radios will follow the sequence defined in FHI, as explained below. The resultant transmitted signal on the airinterface is identical to SFH. Please note that the uplink path will not use BBH and the radio on which the call is established will always receive the uplink signal from the MS. All the processing (e.g. coding, interleaving etc) will be carried out by this radio and the processed information will be routed to different radios for transmission. GSM recommendation defines the following parameters for a frequency hopping system and they are sent from the BTS to MS in the assignment messages during call set up. Mobile Allocation (MA): This is the set of frequencies the mobile/BTS are allowed to hop over. Two timeslots on a same radio of a cell may be configured to operate on different MA. MA is the subset of the total allocated spectrum for the GSM operator and the maximum number of frequencies in a MA list is limited by GSM recommendation to 64. Mobile Allocation Index Offset (MAIO): This is an integer offset that determines which frequency within the MA will be the operating frequency. If there are N frequencies in the MA list, then MAIO = {0, 1, 2, N1}. The first channel from which to hop, as set in the MA, is set by equip <site> RTF, it can be changed by chg_rtf_freq. Used to set the MAIO, which defines the channel from which the MS is to hop. Hopping Sequence Number (HSN): This is an integer parameter that determines how the frequencies within the MA list are arranged. There are 64 HSN defined by GSM. HSN = 0 sets a cyclical hopping sequence where the frequencies within the MA list are repeated in a cyclical manner. HSN = 1 to 63 will provide pseudo random hopping sequence. The pseudo random pattern will repeat itself after every hyperframe, which is equal to 2,715,648 (26x51x2048) TDMA frames or about 3 hours 28 minutes and 54 seconds. Motorola defines a Frequency Hopping Indicator (FHI) that is made up of the above three GSM defined parameters. Up to 4 different FHI can be defined for a cell in a Motorola BSS and every timeslot on a radio can be assigned one of the defined FHI, independently.
24
EMOTOROLA LTD. 2004
Version 1 Rev 0
chg_element hopping_support <*><location>cell=<cell_desc> * 0 = No Hopping 1 = Synthesiser hopping 2 = Baseband hopping chg_element hopping_systems_enabled, <index><*><location>cell=<cell_desc> index = 0 3 (FHI) or 255 * = 0 disabled 1 enabled chg_element hopping_systems_hsn, <FHI><*><location>cell=<cell_desc> * 0 (cyclic) 1 to 63 (Pseudo random hopping) chg_hopping<cell_desc><FHI><f1>[<f2>].......[<f64>] equip<site no>rtf used to set ARFCN which defines the MAIO, the frequency from which to begin to hop
sys12_ch02_02
EMOTOROLA LTD. 2004
25
Base Band Frequency Hopping (BBH)
Version 1 Rev 0

Its main characteristic is that the transmitting units (radios) are always transmitting a fixed frequency and frequency hopping is performed by moving the information for every call among the available radios on a per burst basis. A call will start in a particular timeslot of one radio and will move to the same timeslot of the other radios spending the time associated to a burst (about 577 microsec.) in each radio (and hence in each different frequency). Changing the frequency implies changing the radio (the call hops between Radios). It must be noticed that although data are transmitted by different radios, all the processing (coding, interleaving, etc.) is done by the digital part associated to the radio the call was initially assigned to, and only after that, the information is routed to the corresponding transmitting unit. Looking at the uplink, MS to BS direction, the call is always processed by the radio the call was initially assigned to. The table in the diagram will explain the performance: Assuming a cell with 4 radios and 4 frequencies (f1 to f4), doing Base Band Hopping in a cyclic way and a call assigned to radio 3 timeslot 5, the call process will be described. The first consequence is that as many radios as frequencies in the hopping sequence need to be physically equipped in the cell, which means that the restriction in the number of frequencies to hop over will come from the traffic requirements in the cell (number of radios equipped in the cell). At the same time, because the radios do not need to retune each burst, this type of FH can be used in cells where the combination of transmission signals to the antenna is done through Remote Tune Combiners (high capacity cells usually equip that kind of combiners). As required by the GSM system, the BCCH frequency must be always on the air transmitting the maximum power (Power control do not apply for BCCH carriers), and particularly its timeslot 0 cannot hop (if additional Common Control Channels CCCH are allocated in other timeslots 1 to 7, they will not be allowed to hop as well). From the working philosophy described for BBH there is no problem at all for timeslots 1 to 7 of the BCCH carrier to hop (provided that they are not used to allocate CCCHs) since the permanent presence of this frequency on the air is guaranteed, but the bursts using this frequency will be transmitted at maximum power. This is another important point in BBH: The BCCH frequency can be included in the hopping sequence and also the BCCH carrier can carry hopping calls in timeslots 1 through 7. If Downlink Power Control is enabled in the Base Station it will only take effect for the bursts transmitted in the nonBCCH frequency.
26
EMOTOROLA LTD. 2004
Version 1 Rev 0
Base Band Frequency Hopping

BCCH f1 f1 f1 f1 f1 f1
Other control t/s non hopping
Non BCCH f2
Non BCCH f3
Non BCCH f4
f2
f3
f4
f4
f1
Timeslot 0 non hopping
Tx
Rx
Tx
Rx
Tx
Rx
Tx
Rx
Call assigned to radio 3 (f3) timeslot 4 Burst number 1 2 3 4 ............................cyclic

sys12_ch0203
EMOTOROLA LTD. 2004
27
Synthesiser Frequency Hopping (SFH)
Version 1 Rev 0

In this type of hopping the radio changes the transmitting frequency each burst and the call always stays in the same radio where it started. Motorola equipment has had SFH available since 1992 and a high reliability in implementing this kind of hopping has been achieved. The radio is able to retune to a different frequency for transmission every 577 microsecs., and because such fast frequency changes, Remote Tune Combiners (RTC) must not be equipped if synthesiser FH is to be used. So, Synthesiser Frequency Hopping requires the use of wideband combiner devices such as hybrid combiners. The main advantage of SFH is that there is no restriction on the number of carriers equipped in the cell. The number of radios will be determined by the traffic needed to be handled, but they can hop up to over 64 different frequencies (limitation coming from GSM specifications) if they are available according to the planning. Since with SFH the number of frequencies can be greater than the number of carriers, if the BCCH frequency is included in the hopping sequence, its presence on the air would not be guaranteed unless the BCCH carrier transmits it when no other carrier does. This has two implications: S The BCCH frequency can be included in the hopping sequence, (SFH through BCCH) but timeslots 1 to 7 from BCCH carrier cannot be used to carry traffic because they must be reserved to put the BCCH frequency on the air when necessary (dummy Bursts DB). At the same time, for the bursts transmitted in the BCCH frequency the radios will do it at the same power used by the BCCH carrier (BCCH power). The BCCH carrier will never hop. It will either carry traffic in timeslots 1 to 7 on the BCCH frequency (if not included in the hopping sequence) or transmit dummy frames.
Because of this, BCCH frequency is not included in the hopping sequence, so BCCH timeslots do not hop and nonBCCH timeslots do. The example below and opposite shows a more detailed explanation of this. Assuming a cell with 2 radios and 5 frequencies (fb for the BCCH and f1, f2, f3 and f4 for hopping fb being the lowest one), doing Synthesiser Hopping in a cyclic way on radio 2 and a call assigned to radio 2 timeslot 5 the call process is described in the diagram opposite. Transmission and reception are always routed through the same timeslot in the same carrier (it does not happen for transmission in Base Band Hopping). In this case, for timeslot 5, depending on the inclusion of BCCH frequency in the hopping sequence or not, the evolution of the call will be different Motorola equipment allows the system operator to define the hopping system on a per timeslot basis. So, allowing different hopping configurations for different timeslots. This is very useful for the purpose of interference averaging and to randomise the distribution of the errors.
28
EMOTOROLA LTD. 2004
Version 1 Rev 0
Synthesiser Frequency Hopping through BCCH
BCCH fb fb
Non BCCH
fb
BCCH frequency: b f
fb
Hopping frequencies: f1, f2, f3, f4
fb
fb
Timeslot 0 non hopping
Tx
Rx
Tx
Rx
FHI 0 =fb, f1, f2, f3, f4
Call assigned to radio 2 timeslot 5 Burst number 1 2 3 4 5 6 ..........cyclic
sys12_ch0204
EMOTOROLA LTD. 2004
29
Version 1 Rev 0
210
EMOTOROLA LTD. 2004
Version 1 Rev 0
Synthesiser Frequency Hopping not through BCCH

BCCH fb fb fb fb fb
Non BCCH
BCCH Frequency fb Hopping frequencies f1, f2, f3, f4
f1
fb
Timeslot 0 non hopping Tx Rx Tx Rx
FHI = f1, f2, f3, f4 Call assigned to radio 2 timeslot 5 Burst number 1 2 3 4 5 ...............cyclic
sys12_ch02_05
EMOTOROLA LTD. 2004
211
Frequency Hopping Enhancements
Version 1 Rev 0

chg_hop_params
If any of the hopping parameters are changed, by using the database parameters previously discussed in this chapter, the site is reset. By using the chg_hop_params command it allows under most circumstances frequency hopping parameters to be changed without resetting the site. The exception being if a hopping system is enabled, disabled or changed which is synthesiser hopping through the BCCH frequency. Once the system accepts the chg_hop_params command, the system displays a warning message that the site will reset. When this parameter was introduced it also allowed both synthesiser and baseband hopping in different cells at the same site as well as being able to mix nonhopping cells and hopping cells. Multiple hopping parameters can be changed at the site at one time by using the chg_hop_params command but once the system excepts the chg_hop_params command for a particular cell, the system rejects other chg_hop_params command until the system reconfiguration due to the first command is complete. The operator may change hopping support from no hopping to baseband hopping, or from no hopping to synthesizer hopping, or vice versa, provided that all FHIs for the cell are disabled.
212
EMOTOROLA LTD. 2004
Version 1 Rev 0

chg_hop_params<site>[<cell_desc>] hoping systems (FHIs) to be modified: in cell <cell_desc> (return=no change for this cell):<fhi 1>........<fhi n> hopping support: 0 = no hopping 1 = synthesizer 2 = baseband FHI <fhi 1> status: 0=disable 1 = enable Mobile allocation (ARFCNs) for FHI<fhi 1>:<arfcn 1>......<arfcn n> HSN for FHI<fhi 1>: 0=cyclic 1 63= pseudorandom warning: The site will reset if the operator enabled, disabled or changed hopping system which is synthesiser hopping through the BCCH RTF. Are you sure (y = yes, n = no)?
sys12_ch02_06
EMOTOROLA LTD. 2004
213
Frequency Redefinition
Version 1 Rev 0
This conforms to the Frequency Redefinition procedure defined in TS GSM 04.08 version 4.17.0. Before this feature was implemented an MS assigned to a channel that is affected by the hopping reconfiguration would either be handed over to a channel not affected by hopping reconfiguration or dropped if there are no channels available. With this feature the MS is able to dynamically adjust to the new hopping parameters, thus avoiding any handovers or dropped calls. Frequency Redefinition will only occur when certain changes occur. These differ for baseband and synthesiser hopping in as much as enabling or disabling a FHI, changing the HSN of an enabled FHI are common for both. But because the actual frequencies that are being hopped through are determined by the number of radios actually equipped for baseband hopping and for synthesiser hopping by the mobile allocation which can contain up to 64 different frequencies, Frequency Redefinition occurs differently for the two types. For baseband if a carrier with hopping timeslots transitions from INS to OOS or vice versa then Frequency Redefinition occurs, changing the mobile allocation whilst baseband hopping is not allowed. For synthesiser hopping changing the mobile allocation (which is allowed) of an enabled FHI causes Frequency Redefinition to occur. However, if timeslots are taken OOS they continue to transmit so no hopping reconfiguration needs to be done on corresponding timeslots using the same frequency hopping system. The same criteria are imposed when timeslots come back into service. The feature was designed with the following requirements in mind. 1. 2. Any calls on a channel which are undergoing a hopping reconfiguration will not be handed over or have the call released. Channels that are undergoing a hopping reconfiguration will be made available for intracell handovers from another carrier going OOS if there are idle channels available. Any calls trying to establish on a SDCCH or TCH shall not be granted a SDCCH or TCH that is undergoing hopping reconfiguration. Hopping reconfiguration takes between 10 20s for old gen equipment and milliseconds for newgen. All calls on a channel that is undergoing hopping reconfiguration will be notified of the new hopping changes via the Frequency Redefinition message. Basically this message includes the new hopping parameters together with a start time in terms of an absolute frame number. Upon an error condition (MS gets MA containing ARFCNs that are not all in one band) and the start time has NOT elapsed then the MS stays on the current channel and sends the RR STATUS message back to the BSS. The RR STATUS message will contain the cause value, (Frequency Not Implemented). If the start time has elapsed then the MS aborts the radio connection and, if permitted, attempts Call Reestablishment.
3.
4.
5.
214
EMOTOROLA LTD. 2004
Version 1 Rev 0
Hopping reconfiguration occurs Frequency Redefinition message sent to MS containing: MS in dedicated mode
BTS
Start time (TDMA frame no) Mobile allocation HSN MAIO
If there is an error and start time not elapsed MS send RR Status message and no action taken If there is an error and start time has elapsed the MS aborts the connection
EMOTOROLA LTD. 2004
215
Frequency Hopping to Enhance Network Capacity
Version 1 Rev 0

In principle, implementation of frequency hopping system will not add extra capacity to the existing network. Frequency hopping when implemented will enable more aggressive frequency reuse pattern that leads to better spectrum efficiency. This enables the network operator to add more transceivers in existing sites while maintaining the network quality. In a congested network with fixed frequency plan, adding radios would mean compromising the carrier interference ratio (C/I), which may lead to unacceptable quality level that may eventually crash the network if pushed to the limit. Thus, frequency hopping is effectively compressing the available spectrum to make room for extra capacity, without degrading the average C/I as in a fixed frequency system. In a cellular network, there is always a tradeoff between capacity & quality. Maintaining the current capacity, implementing frequency hopping will improve overall quality. On the other hand, extra capacity could be added by implementing frequency hopping while maintaining the current quality. However, realizing maximum gains in both quality and capacity would not be achievable.
216
EMOTOROLA LTD. 2004
Version 1 Rev 0
Quality
Capacity
NonHopping
sys12_ch02_08
EMOTOROLA LTD. 2004
Quality
Capacity
Hopping
Capacity
Hopping
Quality
Quality
Hopping
Capacity
217
Frequency Reuse Patterns
Version 1 Rev 0

The basic principle, cellular systems are based on, is the reuse of the frequencies in order to obtain the highest capacity with the minimum spectrum. The more the frequencies are used inside a certain coverage area, the more amount of traffic (capacity) can be carried. The possibilities of reusing the frequencies are limited by interference problems arising when the same frequency is used in two cells that are too close each other (cochannel interference). It can be considered that a cellular network is made up by a basic unit, in which all the frequencies are used, repeated all along the area which is intended to be covered. This basic unit (set of cells) is usually known as cluster, and it is the pattern used to deploy the network. The size of the cluster is directly related to the capacity that can be achieved. The smaller the size, the more times will be needed to be reused in the coverage area, so the higher the reuse ratio and hence, the capacity. The usual way to refer to a reuse pattern is by giving the number of cells included in the cluster as well as its configuration. In that way, a cluster made up by m sites with n cells per site, giving a total of p = m*n cells, will be referred as mxn reuse pattern. Any frequency will be used once and only once inside the cluster. As an example, a 12 cell cluster made up by 4 threecell sites, known as 4x3 reuse pattern, meaning that one frequency will be reused once each 12 cells or, equivalently, that 12 frequencies (one per carrier) will be needed to configure this cluster (a 4x3 reuse pattern with, for instance, 3 carriers per cell would require up to 36 different frequencies). Considering a conventional fixed frequency system in GSM, it has been agreed that a 4x3 reuse pattern is the best compromise solution taking into account the cochannel interference and the reachable capacity. Higher capacity goals, without allocating more spectrum, lead to different techniques able to control the interference and allow the system operator to use smaller clusters (tighter frequency reuse patterns). Frequency hopping is the most efficient one, considering the very small cluster size that can be achieved. As it will be described later in the document, a 3x3 reuse pattern can be successfully implemented in a system working with Base Band Hopping. More aggressive reuse patterns such as 1x3 (all the sites reuse the same set of frequencies) are possible in a system working with Synthesiser Frequency Hopping, although it must be noticed that with SFH more than one frequency can be assigned to each carrier. This reduction in the size of the cluster, respect to the 4x3 one, can be used to increase capacity. The results achieved in the systems already implemented using that configuration prove its effectiveness to allow a very high capacity increase. It is important to notice that, either for a fixed system or a Base Band Hopping system, the ratio Number of Frequencies/Number of carriers is always 1, whereas for a Synthesiser Frequency Hopping system, it can be higher than one. It is common to refer to a SFH system as having a mxnxt reuse pattern, being t the number of frequencies used to hop over. Sometimes, the ratio is intended to be noticed and they are named as mxn r/t reuse patterns (r carriers hopping over t frequencies). The number of frequencies needed to implement a cluster with that reuse pattern would be m*n*t. As an example, the 1x3 2/4 reuse pattern uses 12 frequencies separated into three groups of four frequencies each, and two carriers hop over these four frequencies. (A 50% reduction in the number of frequencies required, respect to the fixed system that commonly uses a 4x3 reuse pattern).
218
EMOTOROLA LTD. 2004
Version 1 Rev 0

3x3 Frequency Reuse Pattern implemented with BBH
1x3 2/4 Frequency Reuse Pattern implemented with SFH
12 frequencies separated into three groups of four frequencies each, two carriers hop over these four frequencies 50% reduction on 4x3 reuse pattern
EMOTOROLA LTD. 2004
219
Loading Factor
Version 1 Rev 0
Loading Factor
Loading Factor (or sometimes termed as Fractional load factor) is an important parameter in SFH systems. It is calculated as: loading factor = (highest non BCCH transceiver count in a cell) (Number of hopping channels) Since the number of frequency channels is always higher than the radio count in a cell, some channels will be idle at one time. Thus, loading factor is equivalent to the maximum channeloccupancy to totalchannel ratio in a cell at any given instant. The lower the value the lower is the channel loading, which indicates fewer collisions of frequencies and hence better quality. A theoretical maximum of 50% is permitted in 1X3 SFH. Any value higher than 50% practically, results in unacceptable quality. Some commonly used loading factor are 40%, 33%, 25% etc. In 1X1 SFH, a practical tested loading factor is 1/6 or 16.7%. For a rough comparison, this is about equivalent to a 33% loading in 1X3 SFH or a wellplanned 4X3Xn fixed reuse network, as far as average quality is concerned. In terms of spectrum utilization or capacity, 1X1 at 16.7% loading is equivalent to 1X3 at 50% loading.
220
EMOTOROLA LTD. 2004
Version 1 Rev 0
Loading Factor
Loading Factor
Loading Factor = (highest non BCCH radio count in a cell (number of hopping channels)
bcch
non_ bcch
3 = 0.5 = 50% 6
sys12_ch02_09
EMOTOROLA LTD. 2004
221
Aggressive Frequency Reuse in SFH System
Version 1 Rev 0

Reuse plan in a frequency hopping network is different and more aggressive than it is in a fixed frequency network for both BBH and SFH. Most of the SFH networks employ two different reuse plans for the BCCH and TCH layers. Since the BCCH will not be hopping, conventional fixed frequency reuse plans such as 4X3 or 5X3 are normally used. It is always a design goal to have the cleanest frequencies in the BCCH layer. As for the TCH layer, the common methodology would be 1X3 (1 site 3sector) reuse pattern. This is a much more efficient spectrum utilization, which is not possible in a fixed frequency system as the resultant C/I would be degraded badly beyond of the cell radius. An even more aggressive reuse plan 1X1 (1 site 1 sector) is feasible in networks where the operating environment permits it. 1X1 is by far the most efficient and yet practical aggressive reuse plan tested and proposed by Motorola. Nevertheless, careful planning has to be practiced to achieve good results. The guidelines are outlined below.
Planning Guidelines for SFH

The ultimate goal of frequency planning in a GSM network is attaining and maintaining a highest possible C/I ratio everywhere within the network coverage area. A general requirement is at least 12dB C/I, allowing tolerance in signal fading above the 9dB specification of GSM. The actual plan of a real network is a function of its operating environment (geography, RF etc) and there is no universal textbook plan that suits every network. Nevertheless, some practical guidelines gathered from experience can help to reduce the planning cycle time. S Strongly recommended to have separate bands for BCCH and TCH. If micro cells are included in the frequency plan then they also should have a separate band too. S S S This makes planning simpler Allows better control of interference
The use of IOS would be the most efficient way of working out a frequency plan, this means the frequencies would not be in separate bands but would be used in their most efficient permutation.
222
EMOTOROLA LTD. 2004
Version 1 Rev 0
n channels BCCH
m channels TCH
Guard band
Macro BCCH Micro TCH
Micro BCCH
Macro TCH (SFH)
EMOTOROLA LTD. 2004
223
Planning Guidelines for SFH using 1x3 Frequency Reuse
Version 1 Rev 0

This page deals with some general guidelines for SFH using 1x3 frequency reuse plan, followed by an example. S S BCCH reuse plan: 4X3 or 5X3, depending on the bandwidth available and operating environment. Divide the dedicated band for TCH into 3 groups with equal number of frequencies (N). These frequencies will be the ARFCN equipped in the MA list of a Hopping system (FHI). Use equal number of frequencies in all cells within the hopping area. The allocation of frequencies to each sector is recommended to be in a regular or continuous sequence. Number of frequencies (N) in each group is determined by the designloading factor (or carriertofrequency ratio). For example: mixture of 444 and 555 site configurations and loading factor of 33%. Then N = 5 1/(0.33) = 15 frequencies in the MA list. As loading factor has direct effect on the overall network quality and its setting is highly dependent on the RF environment, a smaller scale trial is recommended to obtain the necessary data and experience before larger scale deployment. As a general rule, SFH with 33% loading is equivalent to a wellplanned 4X3 fixed frequency system. Use same HSN for sectors within the same site. Use different HSN for different sites. This will help to randomise the co channel interference level between the sites. Use different MAIO to control adjacent channel interference between the sectors within a site.
S S
SFH 1x3 Frequency Reuse Example

The example on the diagram opposite has a bandwidth of 10 Mhz, giving us 49 channels of which the first and last are used as guard channels, so 47 usable channels. The BCCH has 12 channels allocated to it in a 4x3 reuse pattern. It is a multilayer environment with 8 channels being allocated for the Micro layer. The site configuration consists of a mixture of 222, 333 and 444 sites, with a loading factor chosen of 33%.
224
EMOTOROLA LTD. 2004
Version 1 Rev 0
Planning Guidelines for SFH using 1x3 Frequency reuse

Bandwidth: 10Mhz(49 Channels 2 Guard) Site configuration mixture of 2 2 2, 3 3 3 & 4 4 4. Loading factor 33 % Multi layer environment (micro & macro coexist)
(highest non BCCH radio count in a cell) = No of hopping channels loading factor 4 1 = 9 hopping channels 0.33 8 channels
Macro BCCH Micro TCH
Micro BCCH
Marco TCH (SFH)
12 channels
27 channels
sys12_ch02_12
ARFCN
HSN
MAIO
Sector A 21, 24, 27, 30, 33, 36, 39, 42, 45 Any from(1,263) 0, 2, 4 Sector B 22, 25, 28, 31, 34, 37, 40, 43, 46 Same as above Sector C 23, 26, 29, 32, 35, 38, 41, 44, 47 Same as above 1, 3, 5 0, 2, 4
The MAIO settings ensure that adjacent channel interference is avoided between sectors within the same site. Co and adjacent channel interference between sites will exist, but the effect is reduced by the randomisation effect of the different HSN
Version 1 Rev 0

1x1 frequency reuse is usually practical in rural areas with low traffic density, where the average occupancy of the hopping frequencies is low. With careful planning it can also be used in high traffic areas as well. S S S S BCCH reuse plan: 4x3 or 5x3, depending on the bandwidth available and operating environment The allocation of TCH frequencies to each sector is recommended to be in a regular or continuous sequence Use a different HSN to reduce interference (co and adjacent channel) between the sites Use the same HSN for all carriers within a site and use MAIO to avoid adjacent and cochannel interference between the carriers. Repeated or adjacent MAIO are not to be used within the same site to avoid cochannel and adjacent channel interference respectively Maximum loading factor of 1/6th or 16.7% is inherent in a continuous sequence of frequency allocation. Since adjacent MAIO is restricted, the maximum permitted is: Max MAIO = x (Total allocated channel)
SFH 1x1 Frequency Reuse Example

In this example the configuration is 4/4/4 with a loading factor of 16.7%. Therefore the number of frequencies to hop through is 18. There are no repeated or adjacent MAIO and the HSN is the same within the site. Other sites would have a different HSN to reduce interference.
226
EMOTOROLA LTD. 2004
Version 1 Rev 0

Available Channels : 18 Site configuration : 444. Loading factor : 16.7%
(highest non BCCH radio count in a cell) = No of hopping channels loading factor 4 1 = 18 hopping channels 0.167
sys12_ch02_14
MA = 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38
1 HSN = 1
13 Different MAIO to avoid co channel
15
11
17
HSN = 1
HSN = 1
Non adjacent MAIO to avoid adjacentchannel

sys12_ch02_15
MAIO restricted to 18/2 = 9
EMOTOROLA LTD. 2004
227
Comparisons between 1x3 and 1x1 Frequency Reuse Patterns
Version 1 Rev 0

Both alternatives should be considered when SFH deployment is decided. The following important aspects should be considered for comparison purposes: Quality: The improvement in quality is the consequence of the frequency diversity and the loading factor (ratio Frequencies/Carriers). Under the same conditions, the quality of both systems will be similar, but 1x3 reuse is more affected by irregularities in the network. For an irregular network 1x1 system will perform with better quality. Capacity: Considering the limitation of MAIO planning in a 1x1 system, and the loading factor, two situations can be found: Totally regular network: If the implementation of 1x3 pattern is possible with 50% of loading (good performance must be guaranteed), the capacity increase is the same that can be achieved with 1x1 pattern. Irregular network: If 1x3 reuse pattern requires less than 50% of loading (40%, 33%, or lower), the 1x1 reuse pattern will permit higher capacity increase. Frequency Planning: Frequency Hopping leads to a simplification in planning issue, and a reduction of manpower. In both cases, only BCCH planning requires a significant effort. For TCH planning with SFH the regularity of the network is very important . For regular ones, 1x3 reuse is very simple because the three groups can be easily and systematically assigned to the sectors without problems of interference. When the sectors are not evenly distributed omni or twosector cells are present, etc. 1x3 reuse requires more effort to avoid interference, whereas 1x1 system does not require any planning effort at all. Flexibility: The main advantage of Synthesiser Hopping appears at the time of integrating a new site, because of the simplicity of this task: Only a clean frequency is needed for BCCH purposes, and the same frequencies used in all the sites will be reused in the new one, following the reuse pattern. Provided that the network is regular, there is no difference between a 1x3 and 1x1 environments. For irregular networks it is easier to integrate a new site in a 1x1 environment. Expansion: When a new carrier needs to be added to an existing site, it is an easier task in a 1x1 than in a 1x3 system. For the 1x3 system there will be a higher increase in the loading factor for the cell, so probably it is required a modification in the frequency groups to tolerate the addition of the carrier without impacting the quality. For 1x1 case, provided that the maximum number of carriers in the site was not reached before, it is easy to expand the capacity with an extra carrier.
228
EMOTOROLA LTD. 2004
Version 1 Rev 0
Quality
Regular Irregular
Capacity
Regular Irregular
Frequency Planning Regular Irregular Flexibility Regular Irregular Expansion
sys12_ch02_16
EMOTOROLA LTD. 2004
229
Frequency Reuse in Baseband Hopping
Version 1 Rev 0

For Base Band Hopping, since the number of frequencies to use in the hopping sequence is determined by the number of carriers equipped, in order to be able to achieve the advantages of hopping, a system with high number of carriers per cell is recommended (4 carriers per cell is a good value), and the higher this ratio the better the performance enhancement achieved. Alternative reuse patterns have been suggested to be implemented combined with Base Band frequency hopping operation:
Progressive Reuse Patterns

Each new carrier added to a cell is equipped with the frequency reused in a more tight way: 1st TCH carrier: 4x3 reuse pattern 2nd TCH carrier: 3x3 reuse pattern 3rd TCH carrier: 2x3 reuse pattern
Homogeneous Reuse Pattarn

A more tight reuse pattern than the conventional 4x3 is used for all the TCH carriers, leading to the same gains achieved with the progressive reuse patterns for high loaded systems. It also saves frequencies (available for other purposes, microcellular layer for instance) in systems with few carriers per cell. Homogeneous 3x3 reuse pattern is the option widely chosen to implement in some systems with very good performance results. For comparative issues, considering a highly loaded system (4 or 5 carriers per cell) where BBH is expected to give more benefits, since all the calls spend part of its time in each carrier, no difference should be noticed between both ways of reusing, but homogeneous 3x3 reuse has the advantage that all the frequencies contribute equally to the interference experienced by the calls (for Progressive Reuses the most tightly reused frequencies contribute more to the quality degradation), so, the effect of one carrier going out of service is different for each TCH radio in a Progressive Reuse than in an Homogeneous one.
Planning Rules for BBH

The rules outlined for synthesiser hopping are generally applicable for baseband hopping. However as the BCCH is usually in the hopping frequency list, a dedicated band separated from the TCH band may not be essential. An example of a frequency spectrum is shown on the PPT slide opposite.
230
EMOTOROLA LTD. 2004
Version 1 Rev 0
2nd TCH (2x3) 1st TCH (3x3) BCCH (4x3) Progressive reuse
Micro BCCH
2nd TCH (3x3) 1st TCH (3x3) BCCH (3x3) Homogeneous reuse
BBH channels & micro TCH

sys12_ch02_17
EMOTOROLA LTD. 2004
231
Capacity Gains for SFH and BBH
Version 1 Rev 0

To give the reader a guide has to how frequency hopping can increase gain in a network the following examples to show the theoretical capacity gains for different frequency reuse plans have been included. Of course these maybe different in the actual network and the operating environment may restrict direct implementation of the reuse plan.
Example
In this example the operator has 7.2Mhz (or 36 GSM channels) of spectrum to use. The table on the PPT slide shown opposite shows the capacity per site for a fixed plan, BBH and SFH with different loading and frequency reuse. In all cases the calculations are based on 2% blocking with 2 timeslots used for control channels in each sector. Fixed Frequency: 22 TCH = 14.8959 from Erlang B tables 3 sectors so 14.8959 x 3 = 44.7 Erlangs 4x3 reuse with 9 channels per site so 9x4=36 channels BBH: 30 TCH = 21.9316 from Erlang B tables 3 sectors so 21.9316 x 3 = 65.8 Erlangs 3x3 reuse with 12 channels per site so 12x3=36 channels 30 TCH = 21.9316 from Erlang B tables 3 sectors so 21.9316 x 3 = 65.8 Erlangs 12 channels for BCCH (4x3) Hopping channels = (highest non BCCH radio in a cell) loading factor 8 = 3/0.375 1x3 reuse for SFH so 3x8 = 24 Total channels 12 + 24 = 36 SFH (50%): 38 TCH = 29.1661 from Erlang B tables 3 sectors so 29.9316 x 3 = 87.5 Erlangs 12 channels for BCCH (4x3) Hopping channels = (highest non BCCH radio in a cell) loading factor 8 = 4/0.5 1x3 reuse for SFH so 3x8 = 24 Total channels 12 + 24 = 36 SFH (16.7%): 38 TCH = 29.1661 from Erlang B tables 3 sectors so 29.9316 x 3 = 87.5 Erlangs 12 channels for BCCH(4x3) Hopping channels = (highest non BCCH radio in a cell) loading factor 24 = 4/0.167 1x1 reuse for SFH so 24 channels to hop through Total channels = 12 + 24 = 36
SFH (37.5%):
232
EMOTOROLA LTD. 2004
Version 1 Rev 0
Reuse plan
Configuration Capacity per Capacity gain site ( Erlang ) over fixed plan 3 3 3 4 4 4 44.7 65.8 65.8 4 4 4 5 5 5 5 5 5 87.5 87.5 97% 97% 47% 47%
Fixed frequency BBH
4x3 3x3
SFH 4x3 (BCCH) (37.5% 1x3 (TCH) loading) SFH 4x3 (BCCH) (50% loading) 1x3 (TCH) SFH (16.7% loading) 4x3 (BCCH) 1x1 (TCH)
EMOTOROLA LTD. 2004
233
Optimisation after Frequency Hopping Implementation
Version 1 Rev 0

Any modification to a network is initially accompanied by a performance change. So implementing a frequency hopping plan in a network that is already optimised would certainly shift its overall performance, probably for the worse. Therefore post implementation optimisation is crucial and necessary. There are several methods of measuring network performance and comparing them before and after implementation: S S S S OMCR statistics including key and health statistics CTP analyse of measurement reports using call trace Speech quality assess the received speech quality with subjective scores Drive test drive around the test area and monitor the RF environment with a test phone
Eliminate Non RF related issues
Optimisation
Neighbour List
dBase
RF Hardware
Frequency Plan
234
EMOTOROLA LTD. 2004
Version 1 Rev 0
Frequency Hopping Implementation
Monitor Performance Dont panic!

Not meeting expectations
Take the credit!!

Meets Expectations
Optimisation
EMOTOROLA LTD. 2004
235
Neighbour List Optimisation
Version 1 Rev 0

Neighbour list is a list containing all the information regarding the relationship that the source cell has with its surrounding neighbour cells. It is the backbone of a GSM cellular network and it forms the basis of mobility. Without a correct set of neighbour list, a GSM network would collapse as many handover failures would occur and most calls would be dropped when the RF condition in the serving cell deteriorates beyond the limits. There are 3 types of neighbour lists: S S S Correct neighbour list. Incomplete neighbour list neighbour cells that ought to be in the list are missing. This will eventually lead to high handover failure and droppedcall rate. Over complete neighbour list Extra or weak neighbour cells being added or present in the neighbour list. This usually happens when the neighbour lists are not updated after cells are added/removed or sites configuration (e.g. bore angle) are altered. A call may be handed temporarily to a weak neighbour due to signal fading and handed back to the original cell, seconds later. This creates a pingpong handover and some calls may be lost because the weak neighbour cell cannot maintain them.
How to Detect
New valid neighbours can be added to an incomplete neighbour list by adding dummy neighbours to the cell dBase and analyse the Measurement reports (MR) using CTP or other equivalent tools. The mobiles served by this cell will be instructed to monitor the dummy neighbours frequencies and report the associated Rxlev in the MR. If there is a valid neighbour with BCCH frequency that is among the dummy frequencies, valid Rxlev and BSIC will be reported. The Neighbour Analysis function of the CTP can be configured to generate neighbours information (e.g. total number of MR reporting a particular neighbour, % of MR reporting this neighbour with Rxlev exceeding certain configurable margin etc). If a neighbour is reported in significant % of MR with Rxlev exceeding preset margin, it may be considered a new valid neighbour and added in the neighbour list. Weak neighbours can be detected with the Neighbour Analysis function of the CTP. With sufficient call trace data, the statistical analysis of the Rxlev of all the neighbours can be studied. For example, the Neighbour Summary function generates summary report of all the serving cell/neighbour combinations. This summary gives: The servers LAC, CI and its reported neighbours BCCH frequency and BSIC. The total number of MRs of the server and the number of MRs reporting one particular neighbour. The number of MR reporting each neighbour exceeding 3 preset thresholds and the associated % figures. Based on these statistics, neighbours that are not reported or reported with very weak Rxlev or reported with low occurrence may be considered as extra neighbour and deleted from the dBase.
236
EMOTOROLA LTD. 2004
Version 1 Rev 0
Neighbour List
Correct Incomplete
Over complete
Dummy neighbours
MRs analysed by CTP
sys12_ch02_20
EMOTOROLA LTD. 2004
237
Database Optimisation
Version 1 Rev 0
There are two important operations that are critical in a cellular system. S S Power control for MS and BTS Handovers
Power Control
Power control is the mechanism where the MS/BTS dynamically changes its transmit power in order to maintain the receive level within certain preset limits. A closed loop methodology is used base on: S S Receive level at MS/BTS Quality based, measures BER at MS/BTS
Recommendation s for hopping systems

alt_qual_proc = 0 (uses BER for receive quality processing) decision_alg_type = 1 (Enables power increase based on quality) mspwr_alg = 1 (uses enhanced PC algorithm for oscillation prevention) pwrc = 1 (Do not include BCCH measurement for rxlev calculations) As a result of frequency hopping and specifically interference averaging the overall BER will be higher than nonhopping systems at the same perceived speech quality. Thus, the Rxqual upper thresholds for PC may be set to values higher than they were in a nonhopping system.
Handovers
In a hopping system, handovers due to Rxqual and interference (intracell) behave differently from a nonhopping system. Due to the interference averaging effect, the average interference level in a hopping system is usually higher than before hopping is turned on. Therefore once hopping is turned on the number of handovers due to Rxqual may increase significantly immediately after hopping is turned on and subsequently increase the handover failure rate. So the handover thresholds and hreqave, hreqt have to be modified to suit the new RF environment.
RXQUAL Hopping parameters

The hop_qual_enabled parameter enables or disables the use of specific rxqual thresholds for hopping call handovers. chg_cell_element hop_qual_enabled [<lacation>] [,index] [,index] <value> <cell_desc_opt> System then prompts for l_rxqual_dl_h_hopping l_rxqual_ul_h_hopping l_rxqual_dl_p_hopping l_rxqual_ul_p_hopping Values entered between 0 and 1810
Version 1 Rev 0
Interference averaging has an effect on: Rxqual Power control settings Handover control settings chg_cell_element hop_ qual _enabled [<location>] [,index] <value> <cell_ desc_opt> l_rxqual _dl_h_hopping l_rxqual _ul_h_hopping l_rxqual _dl_p_hopping l_rxqual _ul_p_hopping Values 0 1810
EMOTOROLA LTD. 2004
239
RF Hardware Optimisation
Version 1 Rev 0
Alterations to the physical RF hardware are sometimes the unavoidable actions needed in cellular optimisation. There are in general four types of cell coverage that are undesirable in a cellular network: S Umbrella cell a very high site (e.g. on a hill) that has a very wide coverage area and has line of sight (LOS) to cells that are located far away. It poses serious interference problem, especially in a 1X3 or 1X1 SFH system that has high radio count. Splash or island Spiltover or overshot coverage of one cell to its neighbouring cells and usually not reciprocal. This is similar to umbrella cell but splashover is usually localised within a few spots instead of a continuous large area. Overlap undesirable high level of reciprocal coverage overlap between 2 neighbouring cells. Void coverage holes that exist due to no dominant cell.
S S
In a frequency hopping system, all of the above cell coverage affect RF quality and if exist must be rectified as soon as possible. This is especially critical in SFH system with irregular sector orientation, where the reuse pattern is much tighter and collision probability is higher.
How to detect
To detect an umbrella cell is straight forward as it is always a very high site (e.g. on a small hill) and simple drive test will prove its over stretched coverage into other cells. Splash or island interference is usually localized within small spots. It is also nonreciprocal, meaning the interference effect is one way, i.e. from the interfering cell to its neighbours and not the other way round. CTP or drive test can be used to detect island or splash. The distinctive characteristics are: Sudden emergence of the interfering cell as a strong neighbour and may temporary serve a call. A dualpeak distribution of timing advance may be observed in the interfering cell. The peak at higher end can be attributed to the island of splash spots located distant away from serving area of the cell. Overlapping is reciprocal interference where the effect on the overlapped cells is mutual. CTP or drive testing can be used to detect overlaps with the following distinctive characteristics: The overlapped neighbours will be reported within low margin from the server Rxlev, in a significant high number of measurement reports (MR). High occurrence of HO between the cells within the overlapped area. Drive testing or CTP can easily detect void in coverage. In any case, there will be a considerable number of MR reporting very low Rxlev of the server and its neighbour.
240
EMOTOROLA LTD. 2004
Version 1 Rev 0
Problem Replace site Umbrella cell
Suggestion
Reduce number of carriers Modify frequency plan Down tilt, antenna type, transmit power.
Antenna height Island/splash

Down tilt, antenna type Transmit power
Frequency plan Overlapping

Antenna height Down tilt, antenna type Transmit power
Add site Void

Sector orientation Transmit power, antenna type
sys12_ch02_21
EMOTOROLA LTD. 2004
241
Frequency Plan
Version 1 Rev 0
Frequency Plan
After a frequency plan has been designed there maybe times when for various reasons it will need to be modified. On this page are a three examples of different situations where a change is required. An umbrella cell with high transceiver count. If some spare channels are available, they may be added to or used to replace a few channels in the existing MA. This in effect reduces the channel occupancy of the original frequency plan, and hence lowers the frequency collision rate. Cells at the boundary of hopping and nonhopping systems. There are usually interference problems at the boundary of two different frequency plans. As explained above, some spare channels will be handy in reducing the interference. If no channels available for spare, swapping the frequency between the sectors within a hopping site may be a 2nd alternative. Areas with no dominant server and served by several cells. This is critical especially in a network with irregular sector orientation. Introducing spare channels or swapping channels between cells, as explained above, may be effective in reducing the average interference level.
242
EMOTOROLA LTD. 2004
Version 1 Rev 0
Frequency Plan
Frequency Plan
Non Hopping
Hopping
Spare Channel 18
34 10,14 ,
Interference Swap with 11 or replace with 18
20 1, 4, 7, , 10
24 2, 5, 8, , 11
28 3, 6, 9, 12 ,
EMOTOROLA LTD. 2004
243
Frequency Plan
Version 1 Rev 0
244
EMOTOROLA LTD. 2004
Version 1 Rev 0
Frequency Plan
Frequency Plan
Main Road 20, 1, 4, 7,10 24, 2, 5, 8,11
28, 3, 6, 9, 12
20 1, 4, 7,10 24, 2, 5, 8,11
28, 3, 6, 9, 12
20, 1, 4, 7,10
28, 3, 6, 9, 12
EMOTOROLA LTD. 2004

Interference area 24, 2, 5, 8,11
245
Frequency Plan
Version 1 Rev 0
246
EMOTOROLA LTD. 2004
Chapter 3
Deployment of Microcellular
EMOTOROLA LTD. 2004
31
Version 1 Rev 0
32
EMOTOROLA LTD. 2004
Version 1 Rev 0
Objectives
On completion of this chapter the student will have: S S S S Discussed the deployment of microcells. Discussed idle mobile behaviour in microcells. Discussed the techniques employed in microcells. Discussed the principles employed in providing inbuilding coverage.
EMOTOROLA LTD. 2004
33
Introduction to Microcellular
Version 1 Rev 0
At present, 80% to 90% of the current GSM subscribers fall into one category, that of slow moving and stationary mobile stations. Microcells address this category of subscriber by providing increased quality of service through reduced blocking and greater coverage in built up areas.
What are microcells?

The microcell is a reduced power cell intended for use in dense traffic environments, such as cities or possibly within public buildings. The microcell has its antenna(s) below rooftop level and usually at least 5m above street level. The main region of operation for the microcell is the street canyon. Microcells typically have a radius of 200300 metres and exhibit transmission behaviour, which differs from conventional large or small cells. Propagation is primarily line of sight and radio path loss increases sharply as the receiver moves out of sight of the transmitter. Microcells differ greatly from the conventional macrocell, which provides umbrella coverage over a wide area, by providing focused coverage and capacity over all or part of the macrocell coverage area. Microcells offer improved propagation properties, experience less severe fading.
The street canyon

Radio signals from a microcell to a hand portable unit of street level travel by reflection and diffraction from buildings and other street furniture, but principally by line of sight. Usually the antennas of microcells are so positioned that only negligible amounts of radiation escape over the rooftops. The microcells functions are almost isolated within the street canyon. Propagation loss rises steeply when the hand portable moves out of the line of sight (around the street corner). The street canyon is effectively a sealed enclosure, albeit with somewhat different propagation characteristics.
RF considerations
By using microcells areas that have previously been unreachable by macrocells can now have RF coverage. Microcells also allow a much tighter reuse of the available RF spectrum.
Microcell applications
Microcellular is a system that has applications in: S S S Hotspots Dense urban areas (contiguous coverage) Inbuilding systems.
34
EMOTOROLA LTD. 2004
Version 1 Rev 0
The Street Canyon
Microcells provide RF coverage previously unreachable by Macro Allows tighter reuse of frequencies Antenna(s) situated below rooftop levels Propogation primarily line of sight
RF Signal Street Canyon Effect
sys12_ch02_01
EMOTOROLA LTD. 2004
35
MultiLayered System
Version 1 Rev 0
MultiLayered System
In the Motorola multilayer network approach, a complete microcellular network is deployed under the existing macrocell network. Cells of different sizes are overlaid, and base stations with different transmit power levels coexist in close proximity. The wide coverage area with highpowered macrocells is considered as the Overlay network. The macrocells will provide wide coverage and act as a safety net for mobiles moving between microcellular areas. The low powered microcells that are installed within the high traffic areas of the network can be considered as the Underlay network. Through the right choice of the microcell site locations, an improved and flexible coverage may be provided, increasing the capacity through tighter frequency reuse and smaller cell sizes. This is possible due to the street canyon effect dominating the RF propagation. With a proper location of the antennae (6 metres to 2/3 the height of the building) the coverage provided is constrained by the surrounding buildings and the reuse pattern can be much tighter as the intermicro interference can be controlled. Reuse patterns of 3 x 1 (three frequency sets for the whole two carriers system) have been implemented in some systems over the entire microcellular portion of the network, by making use of the flexibility Motorolas software provides. When planning for our multilayered system we have to plan that micro/picocells will cover the large majority of subscriber density. The mobiles will be slow moving. Therefore we could have a threelayered system. Macro: Micro: Supporting fast moving mobiles. Also support for congestion in micro/pico layers and for bad quality in micro/pico layers. Supports slow moving mobiles down at street level (outdoor environment), therefore reducing congestion where large subscriber density is found. For inbuilding coverage using micro cells can give better coverage using external penetration. Where good coverage and good quality of signal is needed within a building containing a large subscriber density, then pico cells can be set up as a third layer to support this.
Pico:
36
EMOTOROLA LTD. 2004
Version 1 Rev 0
MultiLayered System
MultiLayered System
Macro Layer: Fast moving mobiles and umbrella coverage
Micro Layer: Support of slow moving mobiles at street level
Pico Layer: Support of inbuilding solution
sys12_ch02_03
EMOTOROLA LTD. 2004
37
Deployment Strategies
Version 1 Rev 0
After many systems deployed, it has been easy to identify in which situations we implement microcells and what are the configurations to cope with them. There are typical situations where microcells are deployed: Capacity relief in hotspot locations: Traffic is concentrated and produces blocking in certain cells. In this situation microcells are planned to put the capacity where needed. At the same time, coverage and quality are improved to the high number of subscribers generating the traffic, without introducing interference to the rest of the system, as it would be done by adding new radios to the macrocells (assuming this would be possible). Capacity relief in saturated areas (business areas, commercial centres, etc.) Macrocellular expansions are difficult to plan there as the system has reached its minimum cell size. There are not frequencies available for adding new radios in macro stations and even if that would be possible, they would not provide the erlang density required.
Inbuilding coverage
Increasing the coverage area does not necessarily imply increasing the geographic area of coverage. Improving inbuilding coverage within the existing coverage area is one of the uses of microcells. A picocell could be designed to cover a specific building internally. Easy capacity expansion system wide as the number of subscribers increases The system is mature, and the cell radius is minimum. High capacity solutions must be used. Other solutions are short term, as they do not provide the same capacity and quality. Sometimes they are difficult to implement, more expensive, and do not have extra values added as the quality and coverage improvement, the better in building penetration, the lower interference added, the longer mobile battery life, etc. In a MacroMicro Layered System these are the typical configurations implemented to cope with the situations exposed above:
Isolated microcells
Deployed in hotspot locations coping with specific capacity requirements in a certain area. These microcells would reuse frequencies from the macro layer, and microcellular algorithms are only used to go down from the macro layer.
Sparsely connected microcells

These are loosely interconnected microcells. This is the natural system growth from hotspot configuration. This configuration covers capacity problems in a certain area. In this configuration microcellular algorithms are used not only to go down from the macro layer but also to perform handovers between microcells.
Contiguous microcellular network underlaying the standard macrocellular system.

In this case a dedicated part of spectrum for the microcellular network is desired, even if not entirely necessary. Microcellular algorithms will be needed to maintain the call in the micro layer and to address specific scenarios that appear in the new propagation environment (antennas below roof level and street canyon propagation effect).
Version 1 Rev 0
Deployment Strategy
Cluster
Hotspots
High Subscriber Area Contiguous System
sys12_ch02_04
EMOTOROLA LTD. 2004
39
Combined cell handovers
Version 1 Rev 0

Within a combined cellular network the microcellular layer is biased to be dominant because the majority of calls will take place on the microcells that offer a much higher quality of service. Only under certain conditions when that normally high level of service cannot be maintained does control pass to the macrocellular part of the combined network. The macrocellular network functions separately from, but in conjunction with, the microcellular network. As long as a mobile moves at relatively low speeds within the area served by the microcellular network, communication is via the microcell offering the best quality of service. As long as a faster moving unit continues to move above a certain speed, communication is via the overlaying macrocell, because in this instance only the macrocellular part of the network can offer the higher quality of service under these conditions. However, when a signal level from the mobile subscriber equipment at a microcell indicates that a better quality of service can be offered by an overlaying macrocell (such as when a subscriber moves towards X in the diagram opposite), and this condition persists, handover to the overlying macrocell occurs. This condition would also occur on emergence from microcellular coverage, at microcellular blackspots and with rapid increase of speed, (such as a car starting from traffic lights at Y and accelerating towards Z. In these cases the macrocell acts as a safety net for the overlaid microcells.
310
EMOTOROLA LTD. 2004
Version 1 Rev 0
Combined Cell Handovers
Macrocell
X
Hand up to macro layer
Hand up to macro layer
SYS102_ch04_05
EMOTOROLA LTD. 2004
311
Hotspots
Version 1 Rev 0
Hotspots
Hotspots are easier to implement than contiguous microcell coverage. Hotspots can be implemented in areas of high traffic density where the use of either a microcell or the utilization of existing hardware and software is purely employed to relieve the loading of the macrocell. As the coverage is noncontiguous and the RF hardware employed is effectively a standalone cell, the frequency planning is relatively easy.
Hotspots handovers
As a hotspot is in an area of high traffic density then presumably most of the subscribers would be very slow moving or stationary. It would be unwise to place a microcell as a hotspot if its coverage extends onto a road or railway. Cell location is critical to ensure efficient use of carrier resource.
Handovers to/from hotspot cells

There are a number of possibilities open to the planner when configuring hotspot cells. Two basic considerations are whether handovers into the cell are allowed from the macrocells, or they are disabled.
Handovers to the hotspot cell

If desired, it is possible to disable handins to the hotspot cell in order to tailor the cell for optimal handling of local mobiles. Consider the case, for example, where the hotspot cell provides extra coverage (and hence picks up extra traffic) compared to the macrocell (e.g. with an inbuilding hotspot cell). There is always the danger that the hotspot cell coverage will extend out of the building and maybe onto a busy road. This cell will then pick up traffic from the road that could otherwise have been handled by the macrocell serving that area. This traffic is served at the expense of inbuilding capacity. The traffic carrying capacity of the cell is therefore not being used optimally. Additionally, if fast moving mobiles successfully hand in to the hotspot cell, there is a danger that due to their speed the hand out may fail causing the call to be dropped. If there is no danger, due to spurious coverage, of the hotspot cell picking up mobiles which should have been handled by the macrocells then handins and handouts to the hotspot cell should be enabled. Care should be taken with the use of adjacent channels in the hotspot cell and the overlying macrocell. Potentially, there are situations where this may work, for example, if the area contains only slow moving traffic. Then, handovers may be fast enough to prevent adjacent channel interference from happening (disabling handins would not be allowable in this case).
312
EMOTOROLA LTD. 2004
Version 1 Rev 0
Hotspots
Hotspots
Macro
S
Road Micro or utilisation of existing hardware and software High Traffic Density
Frequency Planning Simple
Used for Slow Moving Traffi
Handovers Allowed for Slow Moving Traffic
Handovers Not Allowed for Fast Moving Traffic
SYS102_ch04_06
EMOTOROLA LTD. 2004
313
Controlling Handovers in Hotspots
Version 1 Rev 0

The microcellular handover procedures developed for use in the combined cell architecture (see microcellular database parameters) can also be used to control handovers to/from hotspot cells. However, there is also scope for using the parameters in the standard algorithms to adjust the handovers as required. Two methods may be: S S Make the hotspot cell difficult to hand into or reselect by fast moving MSs. Ensure that fast handover from MS leaving the hotspot cell is encouraged.
Fast moving MSs entering a hotspot

Fast moving MSs selecting the hotspot cell run the risk of dropped calls should they originate a call. There is also a risk of fast MSs dropping calls should they enter the cell in dedicated mode. To discourage fast moving MSs from handing into the hotspot cell in dedicated mode, there are 2 mechanisms (apart from disabling incoming handovers). These options are to increase the handover margin and/or to increase the averaging time in the macrocell. The handover margin is definable on a per neighbour basis and therefore can be increased for handovers to the hotspot cell, and left as it was for the macrocells other neighbours. The averaging time defined by hreqave is now definable on a per cell and per neighbour basis and therefore increasing it will affect handovers into the hotspot cell.
MSs leaving a hotspot

Given the typical environment of a hotspot microcell, MS leaving the cell will often attempt to hand out of the cell after they have turned a corner. There is often a very rapid drop of signal strength (20dB or more) on turning the corner. The system design should be such that; S S this drop is recognized and a handover command generated. the hotspot signal strength should be sufficient for the MS to receive the handover command correctly.
It is highly likely that, at the point where the hotspot cell signal experiences a rapid drop, the macrocell will be significantly stronger after the drop. Therefore a high value of ho_margin can be used. The averaging period, defined by hreqave, however, should be set to a short value, allowing a fast handover. Another possibility is to trigger the handover on downlink rxlev, again with a short averaging period.
314
EMOTOROLA LTD. 2004
Version 1 Rev 0
Macrocell
Fast moving MS
Fast moving MS
Fast moving MS
Hotspot Cell
Macrocell (per neighbour)
Hotspot cell (per neighbour)
hreqave (high value) ho_margin (high value) rxlev_min_cell (high value)
hreqave (low value)
sys12_ch03_08
EMOTOROLA LTD. 2004
315
Idle Mobile Behaviour
Version 1 Rev 0

Idle mobiles are constantly listening to the BCCHs of its serving and surrounding cells to enable it to setup a call on the most appropriate cell when required. How a mobile unit behaves in idle mode is more loosely specified by the GSM recommendations. This has the consequence that mobiles from different manufacturers may behave differently.
Association of mobiles to micro/macro layer

A basic philosophy may be to keep all idle mobiles camped onto the macrolayer and then to drop them to the microlayer on call setup. The problems which can occur if this is not done, are caused by the fact that the mobiles cell reselection process may be too slow to avoid loss of service. A fast moving mobile camped on a microcell will, if it does not reselect quick enough, experience downlink interference and loss of the downlink CCCH. Slow reselection and interference on the downlink can result in lost pages. There is also the option of doing nothing. Letting the mobiles originate on their best server, micro or macro, will result in most mobiles originating on the microlayer. This will increase system capacity but will cause problems with fast mobiles. The operator must decide which gives the best overall system performance: Maximizing capacity with freely allowed origination OR Best performance for fast mobiles with restricted originations. Of course the problem of fast moving mobiles may not occur.
316
EMOTOROLA LTD. 2004
Version 1 Rev 0
Macrocell
Fast moving MS
Fast Moving MS
Fast moving MS
Hotspot Cell
Fast moving mobiles in idle mode may: Originate or reselect onto hotspot cell, or Excluded unless fulfilling criteria
sys12_ch02_09
EMOTOROLA LTD. 2004
317
Methods of controlling reselection into a cell
Version 1 Rev 0

Before considering the use of separate BA lists to control reselection into a cell we shall look at the effect of changing the database parameters rxlev_access_min and cell_reselect_hysteresis. The example opposite shows the effect of increasing the value of rxlev_access_min in the hotspot cell. The obvious disadvantage of increasing this parameter is that the MS will be discouraged from selecting into the cell until it is quite near the antenna. Another possibility would be to use cell_reselect_hysteresis to discourage reselections. The disadvantage would be having set the hotspot as a separate location area. C1 is calculated by MS P1 and P2 are broadcast on BCCH. C1= (A MAX (B, 0)) A:= Rxlev Average P1 B:= P2 Max RF Power of Ms P1 = rxlev_access_min=<*>
0= 110 dBm 1= 109 dBm . . 63= 47 dB P2= ms_txpwr_max_cch= <*> 0= 43 dBm 1= 41 dBm . . 15= 13 dBm
Note: +A A +B B
Good downlink Poor downlink Poor uplink Good uplink
A brief description of C1 would be:

for selection the MS chooses the best positive C1 value. for reselection the C1 value of the neighbour must be greater than that of the server.
cell_reselect_hysteresis= <*>
* 0= 0dB RXLEV 1= 2dB RXLEV . . 7= 14dB RXLEV
Altering this parameter will make reselection into other macros delayed.
318
EMOTOROLA LTD. 2004
Version 1 Rev 0
Cell Reselection for Fast Moving Mobile Units
70 dBm
Macrocell rxlev_access_min = 6 ( 104 dBm) ms_txpwr_max_cch = 5 (33 dBm) cell_reselec_hysteresis = 4 (8 dB)

60 dBm Loc B
Hotspot Cell rxlev_access_min = 40 ( 70dBm) ms_txpwr_max_cch = 5 (33dBm)
P = 4 (33dBm)
Loc A
C1 calculation for macro cell C1 = (A MAX(B,0) A = 70 (104) = 34 B = 33 33 = 0 C1 = 34 0 = 34dB (if reselection + 8 = 42 dB)
C1 calculation for micro cell C1 = (A MAX(B,0) A = 60 (70) = 10 B = 33 33 = 0 C1 = 10 0 = 10dB
sys12_ch02_10
EMOTOROLA LTD. 2004
319
Cell reselection C2
Version 1 Rev 0
Cell reselection C2
C2 can be used to control mobiles from reselecting into the microcell by setting a time that the mobile must be in receipt of the microcell or macrocell neighbours BCCH before it can camp on, it could also reduce the number of reselections. This parameter is only applicable to phase 2 mobiles, phase 1 mobiles use C1. C2 is an optional GSM feature which can only be used for cell reselection, it can be enabled or disabled on a cell basis. If C2 parameters are not being broadcast the C1 process is used for reselection. The formula below shows that C2 is firmly based on the original C1 calculation. C2= C1 + Cell_reselect_offset Temporary offset * H (for penalty_time <31) C2= C1 Cell_reselect_offset (for penalty_time= 31) H = 0 for (penalty_time T) < 0 H = 1 for (penalty_time T) > 0 Whilst idle the mobile will maintain a list of the strongest 6 neighbours being monitored from the idle ba list. This will be constantly updated and reselection parameters regularly checked. At least every 5 seconds the MS will calculate C2 for the server and C2 for neighbours, if the C2 for the best neighbour exceeds that of the server for a period of 5 seconds then reselection will take place. If the neighbour is in a different location area then cell_reselection_hysteresis is also considered for the same period. The parameters affecting C2 are broadcast on BCCH system information to an idle mobile and are described below:
cell_reselect_param_ind = <*>
This parameter is used by the MS to determine if C2 parameters are being broadcast or not. If set the MS will use the C2 process for reselection, otherwise C1 controls reselection as well as selection. <*> 0 C2 parameters not broadcast 1 C2 parameters broadcast
cell_reselect_offset = <*>
An integer code specifies the cell_reselect_offset in dBs. This offset could be either positive or negative depending on the value of penalty_time. <*> 0 = 0dB 1 = 2dB . 63 = 126dB
320
EMOTOROLA LTD. 2004
Version 1 Rev 0
Cell reselection C2
Cell reselection C2
MS passes through cell in T = 30s
Macrocell C1 = 20dB
Hotspot Cell C1 = 30dB cell_reselect_param_ind = 1 penalty_time = 1 (40s) cell_reselect_offset = 10 (20dB) temporary_offset = 4 (40dB)
C2 = C1 + cell_reselection_offset temporary_offset x H Unless penalty_time = 31 then C2 = C1 cell_reselection_offset H = 1 as penalty_time T > 0 (40 30 = 10) C2 = 30 + 20 40 x 1 = 10dB Will not select as less than macro C1 Will select as more then macro C1 If the mobile is stationary H = 0 as penalty_time T < 0 (40 large = neg) C2 = 30 + 20 40 x 0 = 50dB
sys12_ch02_11
EMOTOROLA LTD. 2004
321
Cell reselection C2 Continued
Version 1 Rev 0

A brief description of C2 would be:
S For reselection to take place within a location area. C2 (server)<C2 (neighbour) for penalty_time S For reselection to take place to another location area. C2 (server)<C2 (neighbour) for penalty_time (note: C1 calculation for the neighbour will still take cell_reselect_hysterisis into account)
temporary_offset = <*>
This negative temporary_offset is imposed only for the duration of the penalty time, then it is disregarded. <*> 0 = 0dB 1 = 10dB . 7 = infinity
penalty_time = <*>
penalty_time is the duration for which the negative temporary_offset is considered, and is compared with Time T in the algorithm. Time T is the length of time the MS has maintained the neighbour in its top six measured cells. If penalty_time is set to 31 the temporary_offset is ignored and the cell_reselect_offset becomes constantly negative. <*> 0 = 20 sec 1 = 40 sec . 30 = 620 sec 31 = temporary_offset ignored, cell_reselect_offset is negative
cell_bar_qualify = <*>
cell_bar_qualify is used only in cell selection to prioritise a cell as being normal or low priority. The MS will always select cells with normal priority providing their C1 calculation is greater than zero. Only if a normal priority cell cannot be found will a low priority cell (providing C1 > 0) be selected. This is a phase 2 mobile function. <*> 0 normal 1 low
Version 1 Rev 0
EMOTOROLA LTD. 2004
323
Selective cellbar on microcells
Version 1 Rev 0

An alternative approach is to selectively cellbar the microcells. This means that mobiles in idle mode may only camp on the macrocells. Origination would occur on the macrocell, followed by handdown to the microcell if appropriate. This approach, however, has the disadvantage that any extra geographical coverage which barred microcells offer over and above that of the macrocells would be lost as far as originations were concerned. This situation could be alleviated to some extent by not barring indoor and pedestrian area microcells or areas of macrocell deep fade. Selective cell bar is set in add_cell and is set by the prompt cell_bar_access_switch. cell_bar_access_switch= 0 cell is not barred
cell_bar_access_switch= 1 cell is barred
Emergency calls (user class 10) are not, and cannot be, barred. An MS decodes the BCCH data to determine if it is allowed access to the system. BCCH data includes information which indicates that the cell transmitting the data is part of the selected PLMN (unbarred) or not (barred).
324
EMOTOROLA LTD. 2004
Version 1 Rev 0
Selective CellBar
Macro
cell_bar_access_switch = 0
MS selects onto macro
Micros
cell_bar_access_switch = 1
sys12_ch02_12
EMOTOROLA LTD. 2004
325
Version 1 Rev 0
C2 reselection exercise
The parameters and levels specified on the facing page are typical values experienced by a mobile in the reselection process. Use these values to determine whether the mobile will reselect to the neighbour cell. The mobile has been in the server well over one hour, and the best neighbour has been in the top six measured cells for exactly 4 minutes.
WORKING AREA
SERVING (working out C1 first)
A= A= B= B= C1= C2= Rxlev Av P1 = P1= rxlev_access_min= dB (P2= ms_txpwr_max_cch= dBm) dB dB dB dBm)
P2 Max RF Power of MS + = = =
NEIGHBOUR
A= A= B= B= C1= C2= + Rxlev Av P1 P2 Max RF Power of MS = = = = (P1= rxlev_access_min= dB (P2= ms_txpwr_max_cch= dB dB dB dBm) dBm)
FOO OCRCIC<SIOL <- rcouco( 2 <- lcheg_nto( ) bciiTocrcicbsTgvrscocrhr
326
EMOTOROLA LTD. 2004
Version 1 Rev 0
C2 Reselection Example
S
SERVING CELL DATABASE PARAMETERS

CELL IDENTITY= rxlev_access_min= ms_txpwr_max_cch= 234 10 255 038 20 (90dBm) 7 (29dBm)
cell_reselect_param_ind=1 cell_reselect_offset= temporary_offset= penalty_time=

S
3 3 5
BEST NEIGHBOUR CELL DATABASE PARAMETERS

CALL IDENTITY = rxlev_access_min= ms_txpwr_max_cch= 234 10 262 042 20 5 (33dBm)
cell_reselect_param_ind=1 cell_reselect_offset= temporary_offset= penalty_time=

S
2 1 12
Rxlev Average
Serving= )70 dBm Best Neighbour= )63 dBm
S S
cell_reselect_hysteresis= 2 Mobile power class= 4 2w 33 dBm(
EMOTOROLA LTD. 2004
327
Effects of Broadcasting Separate BA Lists
Version 1 Rev 0

Broadcasting separate BA lists
The separate BA lists feature allows the operator to select neighbours to be included in the BCCH allocation on the SACCH and the BCCH. S BA BCCH: This list is the BA sent in the System Information Message Type 2 on the BCCH. It is the list of BCCH frequencies in use by a PLMN in a given geographical area. It is used by the MS in cell selection and reselection. BA SACCH: This list is the BA sent in the System Information Message Type 5 on the SACCH. It indicates to the MS which BCCH frequencies are to be monitored for handover purposes.
By maintaining two distinct BA lists, the operator is given the flexibility to vary the frequencies the MS monitors in idle mode independant of the frequencies the MS monitors as potential neighbours in active mode.
Method 1: (see table opposite)

With this arrangement, there is no restriction on handovers, they can occur macromacro, macromicro, micromacro, and micromicro. However, when a mobile which is camped on a microcell moves out of this cell, it can only reselect a macrocell since this is all there is in its BA(BCCH) list.
Method 2: (see table opposite)

Method 2 is similar to method 1 except that the microcells are removed from the macrocell BA(BCCH), resulting in there being no reselection mechanism to return to the microcells once the macro layer is entered. This would place a large amount of idle mode traffic on the macrolayer. This traffic would place call originations on the macrolayer and hand down to the microlayer would then follow where appropriate. This strategy could be used in the case where there are fast moving mobiles and the slow reselection process and downlink interference would cause lost CCCH lost pages.
328
EMOTOROLA LTD. 2004
Version 1 Rev 0
Broadcasting Separate BA Lists
Method 1
Broadcast Microcell BA(BCCH) Microcell BA(SACCH) Macrocell BA(BCCH) Macrocell BA(SACCH)
Broadcast candidates listed Overlying macrocell Overlying macrocells Neighbour microcells Neighbour macrocells Underlying microcells Neighbour macrocells Underlying microcells
Method 2
Broadcast Microcell BA(BCCH) Microcell BA(SACCH) Macrocell BA(BCCH) Macrocell BA(SACCH)
Broadcast candidates listed Overlying macrocell Overlying macrocells Neighbour microcells Neighbour macrocells Neighbour macrocells Underlying microcells
sys12_ch02_14
EMOTOROLA LTD. 2004
329
The layered Approach
Version 1 Rev 0

Let us compare the picocellular environment with that of the microcellular solution. Within the microcellular area of coverage we had a small cell of less than 500m radius, with the antenna mounted below rooftop. This enabled the RF to be contained within street canyons. This provided additional capacity, as well as efficient reuse of the portion of the frequency spectrum allocated to operators. The picocellular area of coverage is a small cell of less than 100m radius with the antenna mounted inside a building. However, the RF environment is now contained within the building, thereby providing additional capacity as well as a high frequency reuse. Picocellular can be considered as the third layer within a multilayer network. The picocellular solution provides this functionality of a seamless service within the existing infrastructure by utilising the same phone, same features, as well as the same method of accessing these features in all environments. There must also be the seamless service between the three layers: Layer 1 macrocell Layer 2 microcell Layer 3 picocell as well as the support of the mobile in both the idle and dedicated mode.
330
EMOTOROLA LTD. 2004
Version 1 Rev 0
The Layered Approach
Macrocell
Microcell
Picocell
EMOTOROLA LTD. 2004
331
BA Lists Exercise
Version 1 Rev 0
BA Lists Exercise
If it was decided that we would like the mobile just to camp on to the macro layer in idle mode, and not on the micro cell layer (handovers to take place between layers) how would we set up the neighbour list in the micro and macro serving cells? For the inbuilding solution we want the mobiles to reselect to the pico cell in the lobby from the macro when entering the building, but once in the building, we do not want to reselect back to the macro. How would we set the neighbour list for the pico cells and micro cells?
332
EMOTOROLA LTD. 2004
Version 1 Rev 0
BA Lists Exercise
BA Lists Exercise
Macro Cell 1
Pico Cell 6
Pico Cell 5 Micro Cell 2
Pico Cell 4
Pico Cell 3
Macrocell 1 BA list BCCH SACCH
Microcell 2 BA list BCCH SACCH
Picocell 3 BA list BCCH SACCH
sys12_ch02_15
EMOTOROLA LTD. 2004
333
BA Lists Exercise
Version 1 Rev 0
334
EMOTOROLA LTD. 2004
Chapter 4
Microcellular Database
EMOTOROLA LTD. 2004
41
Version 1 Rev 0
42
EMOTOROLA LTD. 2004
Version 1 Rev 0
Objectives
On completion of this chapter the student will have: S S S S S Reviewed the principles of handovers in multilayer systems. Discussed the seven Motorola microcellular handover algorithms. Discussed the use of adaptive handovers. Discussed the add_neighbor command. Written an add_neighbor database for a given execise
EMOTOROLA LTD. 2004
43
Microcellular Handover Criteria
Version 1 Rev 0

When planning a microcellular handover strategy, there are some basic criteria that should be employed. These criteria detail a strategy for handovers between:
MacroMacro
This is the standard power budget or imperative type of handover.
MacroMicro
When the environmental conditions are well known, to ensure that the micro cell is going to provide a good service to a particular mobile, its level will be measured and when it exceeds a certain value (rxlev_min) for a given period (delay time), and power budget conditions are met, this mobile will be allowed to be passed between the macro and the micro. This period must be long enough to ensure that this mobile is not a fast mobile.
MicroMicro
Line of sight Algorithm incorporates a delay timer to limit the handover rate (pingpong handovers) and to force fast moving mobiles to hand up to the macro layer before quality of service is degraded. This is because microcells have a small radius and as the mobile travels towards the edge of the cell it will suffer interference, also the number of handovers generated would cause and unacceptable loading on the system processors. Around the corner In this configuration, the signal level is monitored and handovers will be prevented to the neighbour microcell unless the server level goes below a threshold. This is extremely useful when the topology of the streets can create problems such as rapid drop in signal level when turning a corner.
MicroMacro
It is necessary to keep the call as long as possible in the micro layer, this effectively disables the use of power budget considerations to trigger the handover to the macro layers. However power budget is still calculated for candidate ordering purposes for imperative handovers such as Rxqual and Rxlev. System behaviour is dependant on mobile speed. If the speed is low enough the microcellular system will take the call, but if the speed increases the call will be handed up to the macrocellular layer. For example a car may stop at traffic lights and be located in a micro. When the vehicle starts to move faster, the timer of the serving micro cell will prevent handover to further micro and this mobile will be forced to hand up to a macro. Another reason to hand calls up to the macrocell is when the microcell capacity is exceeded and directed retry or congestion relief is being used. The macrocell cell could then be used to take the congested calls. The main design target can thus be stated as: Keep the mobiles on the microcells except when their speed is high enough to degrade their service quality, in which case they are to be served by the macrocells. If their speed reduces such that they can be adequately served by the microcells, then hand them back to the microcells. Motorola defines a number of handover procedures each tailored to a particular scenario, these procedures can be selected on a perneighbour basis.
Version 1 Rev 0
Pbgt or Imperative handovers
Macro
Macro
Fast moving MS
Micro
Micro
Imperative handovers MS speed Combat adj chan int Congestion Relief
Slow moving MS Line of sight (micro or macro) Round the corner
Acceptable rxlev Delay time Pbgt
sys12_ch05_01
EMOTOROLA LTD. 2004
45
Current Motorola Handover Decision Algorithms
Version 1 Rev 0

The HDPC in the RSS software constantly monitors measurement reports from the mobile during a call. The mobile is capable of monitoring up to 64 neighbours, that can be made up of a maximum 32 SACCH and 32 BCCH neighbours. During a full SACCH multiframe a total of 104 or 100 measurements (12 for serving cell measurements if DTX on) can be made. These measurements report on the neighbours receive level and also decode the BSIC of the neighbours. The mobile also reports on the serving cells receive level, receive quality, timing advance, power level, whether DTX is enabled and which BA list is in use. Once the measurement reports reach the HDPC then they are subject to averaging, the level of averaging is set by hreqave and hreqt. The HDPC then makes decisions on handovers, power level changes and timing advance changes. Handover triggers are currently based on the following criteria: 1. 2. 3. 4. 5. Receive Quality (Uplink and downlink) Interference level (Uplink and downlink) Receive Signal Strength (Uplink and downlink) Distance (Timing Advance) Power Budget
A decision has to made by the BSC as to what priority should be given to each of the five criteria. They are in fact placed in order of priority, Receive Quality being the most important and Power Budget being the least. Therefore, if there are more handover bids to a cell than free channels, then the bids with cause Receive Quality shall take highest priority. Cells that the MS is being handed over to, can also be placed in priority levels. These priority levels are considered together with the list of candidates and the interference levels in the choice of new cell. If there are then two cells, which meet the criteria for handover, then the cell with the highest priority shall be used. This enables umbrella cells for instance to be given a lower priority and therefore only handle calls when no other cell is available. Channel congestion in the best cell shall cause the choice of the second cell. If no cell is available and call queuing is employed then the MS will be placed in the queue until the relevant cell becomes available. MS placed in queue for handover purposes take priority over new calls.
46
EMOTOROLA LTD. 2004
Version 1 Rev 0
Current Motorola Handover Decision Algorithm
To BSC (handover_rec)
Cause Value Qualified n/bours (ranked1 up to 6)
Neighbours evaluated by: Criteria 1 Criteria 2 Rxlev BSIC Freq
n1
Rxlev BSIC Freq Rxlev Rxlev (s) Rxqual (s) Timing Adv Power Level DTX used BA used nCell(1 to 6) BSIC Freq
RxQual (ul) RxQual (dl) Interference (ul) Interference (dl) Rxlev (ul) Rxlev (dl) Timing adv Pbgt Power Changes Timing adv changes
SYS12_Ch5_03
n2
n3
EMOTOROLA LTD. 2004
47
hreqave and hreqt
Version 1 Rev 0
hreqave and hreqt

To set the bin values of the parameters hreqave and hreqt the following commands are used. Two types of algorithm are available, those being unweighted and weighted (for rxqual only) algorithms. chg_cell_element hreqave = hreqt = alg_name The algorithm name specifies the averaging mechanism to be enabled. surround_cell rel_tim_adv rxlev_dl_ho rxlev_ul_ho rxlev_dl_pc rxlev_ul_pc rxqual_dl_ho rxqual_ul_ho rxqual_dl_pc rxqual_ul_pc bin_num Is the bin for data storage, range 0 to 1 alg_num Is the number for weighting if used. The range is from 0 to 255 cell_id Is the GSM cell id or cell to be affected by the change The two parameters points to hreqave and hreqt. hreqave (0 to 31) hreqt (0 to 31) Note: The product of hreqt and hreqave can, at maximum equal 32, as only 32 averages can be stored at any moment in time. neighbour Rxlev timing advance downlink handover uplink handover downlink power control uplink power control downlink handover uplink handover downlink power control uplink power control <alg_name>,<bin_num><alg_num> cell <cell_desc>
48
EMOTOROLA LTD. 2004
Version 1 Rev 0
hreqave and hreqt
hreqave and hreqt
chg_cell_element <alg_name>
surround_cell rel_tim_adv rxlev_dl_ho quality_weighting 0 to 255 rxlev_ul_ho rxlev_dl_pc rxlev_ul_pc rxqual_dl_ho rxqual_ul_ho rxqual_dl_pc rxqual_ul_pc
<bin_name>
range 0 to 1
hreqave (0 to 31) hreqt (0 to 31)
<alg_num>
<cell_id>
EMOTOROLA LTD. 2004
49
Pointing Averaging Mechanisms to Decision Processes
Version 1 Rev 0

Each averaging mechanism produces at least one set of averages every SACCH multiframe, these averages are used by decision processes controlling handover and power control. The software bin where each set of averages is stored, has to be directed to the decision process utilising them. This pinpointing is specified in add_cell.
n and p voting
The averages can be further processed, by using a voting mechanism. A number of averages are taken (n value), these averages are compared to a threshold (set in add_cell). The averages are then compared to a threshold (also set in add_cell), if a number of these averages (p value) exceeds the threshold then a decision is made. This decision could be for a handover or power increase or decrease. Averaging Bin Pointer chg_cell_element.... ul_rxlev_av_p n and p numbers n1/p1 Threshold l_rxlev_ul_p u_rxlev_ul_p l_rxlev_dl_p u_rxlev_dl_p l_rxqual_ul_p u_rxqual_ul_p l_rxqual_dl_p u_rxqual_dl_p l_rxlev_ul_h l_rxlev_dl_h Comment Power increase/decrease uplink due to level Power increase/decrease downlink due to level Power increase/decrease uplink due to quality Power increase/decrease downlink due to quality Uplink handover due to rxlev Downlink handover due to rxlev, these averages are also used for the serving part of the Pbgt calculation for criteria 2. Uplink handover due to rxqual Downlink handover due to rxqual Uplink handover due to interference Downlink handover due to interference
dl_rxlev_av_p ul_rxqual_p
n2/p2 n3/p3
dl_rxqual_p ul_rxlev_av_h dl_rxlev_av_h
n4/p4 n5/p5 n5/p5
ul_rxqual_av_h dl_rxqual_av_h ul_rxlev_av_ih dl_rxlev_av_ih tim_adv_av_alg ncell_rxlev_av_h_calc
n6/p6 n6/p6 n7/p7 n7/p7 n8/p8
l_rxqual_ul_h l_rxqual_dl_h l_rxlev_ul_ih
p_bgt_rxlev_av_h
l_rxlev_dl_ih ms_max_range Handover due to distance Used to access per cell averaged neighbour measurements to be used to calculate valid neighbour candidates for handovers (criteria1 and 2) Used to calculate averages for neighbour cell measurements to be used for power budget calculation, when the calculation is done to determine if the cell qualifies for power budget handover.
410
EMOTOROLA LTD. 2004
Version 1 Rev 0
chg_cell_element rxlev_ul_ho, 0 0 <cell id> hreqave = 4 hreqt = 1 decision_1_ul_rxlev_av_h = 0 l_rxlev_ul_h = 30 decision_1_n5 = 4 decision_1_p5 = 2 ho_recognised
Measurement reports/averages every 480ms from radio hreqave = 4 hreqt = 4
Decision Mechanism 47dBm
CV rxlev ul <n1.....n6>
BIN 0 Averaging Mechanism
80dBm
110dBm
SYS12_Ch4_04
EMOTOROLA LTD. 2004
411
use_neighbor_pbgt_hreqave
Version 1 Rev 0
In order that the sites unaffected by the microcellular deployment can use their existing PBGT calculation the chg_element use_neighbor_pbgt_hreqave flag can be used. This can be used in the PBGT calculation for the neighbour rxlev_dl
Neighbour cell :
The hreqave used for pbgt handover decision and depends upon the source cell parameter use_neighbor_pbgt_hreqave. If use_neighbor_pbgt_hreqave is set to 0, hreqave used is the one defined in surround_cell (in chg_cell_element). If use_neighbor_pbgt_hreqave is set to 1, hreqave is retrieved from the per_neighbor_hreqave which is defined per neighbour (in add_neighbor). When the per neighbour hreqave value is used, a value of 1 is always used for hreqt and the averages are stored in the microcell_av area .
For pbgt handovers, the decision is made for the source cell with hreqave defined in rxlev_dl_ho, and for the neighbour cell with hreqave either defined in per cell surround_cell, or the per_neighbor_hreqave if use_neighbor_pbgt_hreqave is set to 1. For pbgt neighbour ordering, the decision is made for the source cell with hreqave defined in rxlev_dl_ho, and for the neighbour cell with hreqave always defined in the per cell surround_cell regardless of use_neighbor_pbgt_hreqave. Note: For pbgt handovers, the parameter decision_1_p_bgt_rxlev_av_h is used to specify which bin is used, for rxlev_dl_ho and surround_cell, for the purpose of making a Better Cell (pbgt) handover decision. For candidate ordering, the parameter decision_1_ncell_rxlev_av_h_calc is used to specify which bin is used for surround_cell for the neighbour cell averages and for the serving cell averages the parameter decision_1_dl_rxlev_av_h specifies the bin.
412
EMOTOROLA LTD. 2004
Version 1 Rev 0
use_neighbor_pbgt_hreqave (example 1)
use_neighbor_pbgt_hreqave = 0
PBGT handover detected
Serving
Neighbour
chg_cell_element rxlev_dl_ho, 0 0 <cell id> (hreqave = 8, hreqt = 1 chg_cell_element surround_cell, 0 0 <cell id> (hreqave = 8, hreqt = 1) decision_1_p_bgt_rxlev_av_h = 0 Candidate ordering uses the same hreqave as for pbgt handover decisions decision_1_ncell_rxlev_av_h_calc = 0
sys12_ch05_06
EMOTOROLA LTD. 2004
413
Version 1 Rev 0
414
EMOTOROLA LTD. 2004
Version 1 Rev 0
use_neighbor_pbgt_hreqave (example 2)
use_neighbour_pbgt_hreqave = 1 PBGT handover detected
Surround cell hreqave (Per neighbour)
Serving
Neighbour
chg_cell_element rxlev_dl_ho, 0 0 <cell id> (hreqave = 8, hreqt = 1) chg_cell_element surround_cell, 0 0 <cell id> (hreave = 8, hreqt = 1) Per neighour hreqave set in add_neighbour by surround cell hreqave Only one bin, hreqt always = 1 (hreqave = 4) For Pbgt handovers uses per neighbour hreqave decision_1_p_bgt_rxlev_av_h = 0 For Pbgt neighbour ordering uses per cell hreqave decision_1_ncell_rxlev_av_h_calc = 0
EMOTOROLA LTD. 2004
415
The Seven Motorola Microcellular Handover Procedures
Version 1 Rev 0

When the microcellular feature is enabled and the need for a power budget handover is detected, the handover process checks the CM database to see if there are any further power budget restrictions, these are set in the neighbour cells description (pbgt_alg_type) and have a valid range from 1 to 7. These algorithms are described briefly on this page, but in greater detail later. Another important point is candidate ordering which is a key component of the algorithms used. Once again these are described later.
Algorithm Title Conventional GSM PBGT Restricted PBGT for macro cells PBGT with RXLEV as qualifier PBGT with time in cell as qualifier PBGT with delay since neighbour level exceeds threshold as qualifier Delayed power budget using dynamic handover margin PBGT algorithm to avoid adjacent channel interference
pbgt_alg_type 1 2
3 4
416
EMOTOROLA LTD. 2004
Version 1 Rev 0
S S
Specified on a per neighbour basis by pbgt_alg_type Each neighbour cell is classified by an algorithm ranging from 1 to 7
EMOTOROLA LTD. 2004
417
Type 1 Algorithm
Version 1 Rev 0
Type 1 Algorithm
PBGT algorithm
Algorithm 1 is simply the standard GSM power budget algorithm. The difference from the previous implementation is that the averaging period (hreqave) can be set on a perneighbour basis, The power budget formula can be considered in two parts, the left handside the serving cell and the right handside the neighbour cell. The power budget calculation is carried out every 480ms (SACCH multiframe). For each reported neighbour of all mobiles engaged in traffic the aim of the formula is to afford the mobile the lowest uplink pathloss (not subject to N & P voting).
PBGT(n)=
(min(ms_txpwr_max,P) rxlev_dl PWR_C_D) SERVER (min(ms_txpwr_max,P) rxlev_dl) NEIGHBOUR
For handover to take place it is usual for: PBGT(n)>ho_margin

SYS12_Ch4_08
418
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 1 Algorithm
Type 1 Power Budget Assessment
All values in dBm
Serving
neighbour
Min(ms_txpwr_max,P) rxlev_dl PWR_C_D
Min(ms_txpwr_max,P) rxlev_dl
PBGT(n) = [Min(ms_txpwr_max,P) rxlev_dl PWR_C_D] [Min(ms_txpwr_max,P) rxlev_dl]
PBGT(n) > ho_margin

SYS12_Ch4_09
EMOTOROLA LTD. 2004
419
Type 1 Algorithm
Version 1 Rev 0
Downlink RXLEV only

Probably the most important factor in any handover decision and selection process should be the mobiles perception of its serving downlink level as compared to neighbours downlink level. This is accounted for in the power budget expression:
SERVER PBGT(n)=
SYS12_Ch4_09a
NEIGHBOUR ( Rxlev_DL)
( Rxlev_DL )
As can be noted, all the other inputs to the formula have been removed and this level comparison can be easily seen. PBGT(n) will become a value greater than 0 if the reported neighbour level becomes greater than the server. The rxlev_dl averages for the neighbour can come from two sources. This is covered later in the course.
420
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 1 Algorithm
Considering RXLEV Only
PBGT(n) > 0
Serving 43dBm
Neighbour 43dBm
<server>
<neighbour>
PBGT(n)
SYS12_Ch4_10
= [ rxlev_dl ] [ rxlev_dl]
EMOTOROLA LTD. 2004
421
Adapted Power Consideration
Version 1 Rev 0

A direct level comparison is not always correct because the mobile is potentially reporting adapted power on the serving cell where as, the neighbour is being measured at its full BCCH power level. A correction factor must therefore be considered:
SERVER PBGT(n)=
SYS12_Ch4_11
NEIGHBOUR
( Rxlev_DL PWR_C_D ) ( Rxlev_DL)
Where PWR_C_D = max_tx_bts Actual BTS output power. PWR_C_D will always equal a positive value, or zero. In the example shown opposite the downlink serving receive level is 80dBm and the downlink neighbour receive level is 72dBm. At first glance it appears that the neighbour cell has the better level. However, this does not take into account the transmit level of the BTSs. The server has a transmit power of 35dBm and the neighbour has a transmit power of 43dBm. But is the server on full power? Well in this case no, as the maximum transmit power that the server can output is 43dBm. So by applying the correction faction the system can take adapted power into consideration and compare like for like. Therefore the power budget calculates to 0, the same case as before. If the mobile moved towards the neighbour, its receive level would increase and the servers receive level would decrease and hence the power budget of the neighbour would become more positive and hence a likely candidate for handover.
422
EMOTOROLA LTD. 2004
Version 1 Rev 0
Adapted Power Correction Factor
PBGT(n) > 0
80 dBm
72 dBm
Serving 35dBm
Neighbour 43dBm
max_ tx _bts = 0 (43dBm)
<server>
PBGT(n) = [ rxlev_dl PWR_C_D]
<neighbour>
[ rxlev_dl]
Where PWR_C_D = max_tx_bts Actual BTS output power
= [80 (43 35)]

=0
sys12_ch05_12
[72]
EMOTOROLA LTD. 2004
423
Uplink Consideration
Version 1 Rev 0
Remember that the aim of this formula is to provide the mobile with the lowest uplink pathloss, so far the uplink path has not been considered. The first part of each side of the formula provides this comparison. min (ms_txpwr_max, P) ms_txpwr_max of the neighbour can be specified in add_neighbor for an external cell and for an internal neighbor the ms_txpwr_max is read from the neighbour cell area of the database (add_cell). The value of P equates to the maximum power of the mobile concerned. The power budget formula is designed for a mobile suited to the PLMN being used, that is that the mobile always has sufficient power to support all cells within the PLMN. In this case the P value is never used and the ms_txpwr_max is always the deciding uplink factor. The following examples illustrate this ideal. Note: ms_txpwr_max of the server equates to the value specified in max_tx_ms in add_cell. In the next three examples we have two equally sized cells, large server small neighbour, and small server large neighbour. For each, example values of relevant database settings have been shown. Please bear in mind that every situation has different needs and these are only examples designed to show the principle and not to be taken as defaults.
Example One Equally Sized Cells

When the cells are of equal size the values of max_tx_ms (server) equals ms_txpwr_max (neighbour). This gives neither cell advantage when calculating power budget. Therefore for the mobile would have to move towards the neighbour for its power budget to increase and hence overcome the handover margin for a handover to take place.
424
EMOTOROLA LTD. 2004
Version 1 Rev 0
Example One Equally Sized Cells
PBGT(n) > 0
80dBm
72dBm
Serving 35dBm
max_tx_bts =0 max_tx_ms = 33
Power Class = 4
Neighbour 43dBm
ms_txpwr_max = 33
<server>
PBGT(n) = [Min(ms_txpwr_max,P) rxlev_dl PWR_C_D]

<neighbour>
[Min(ms_txpwr_max,P) rxlev_dl] =[33+80 (43 35)] [33+72]

=0
SYS12_ch05_13
EMOTOROLA LTD. 2004
425
Example Two Large server, Small Neighbour
Version 1 Rev 0

In this case the value of ms_txpwr_max (neighbour) is a less than max_tx_ms (server) by a margin of 6 dBm. With the same receive levels as before the neighbours power budget has a value of 6 dB, hence making it more attractive for handover. This can take place because the actual size of the neighbour cell is smaller than the server, so the actual distance travelled on the uplink is less so the mobile power required in that cell can be less than the server.
426
EMOTOROLA LTD. 2004
Version 1 Rev 0
PBGT(n) > 0
80dBm 72dBm
Serving
Neighbour 37dBm
35dBm max_tx_bts =0 max_tx_ms =33
ms_txpwr_max =27
Power Class = 4
<server>
PBGT(n) = [Min(ms_txpwr_max,P) rxlev_dl PWR_C_D]

<neighbour>
[Min(ms_txpwr_max,P) rxlev_dl] = [33 + 80 (43 35)] [27 +72] = 6dB
sys12_ch05_14
EMOTOROLA LTD. 2004
427
Version 1 Rev 0
Example Three Small Server, Large Neighbour

In this case the value of max_tx_ms is less than ms_txpwr_max by 6 dBm. If the receive levels are the same as in the previous examples, then the power budget of the neighbour is 0 dBm. This has the effect of the smaller cell retaining the mobile for as long as possible and the receive level of the larger neighbour will have to exceed the server by 0 dBm plus the handover margin.
428
EMOTOROLA LTD. 2004
Version 1 Rev 0
Example Three Small Server, Large Neighbour
PBGT(n) > 0
72dBm 80dBm
Server 35dBm max_tx_bts = 0 max_tx_ms = 27
Neighbour 43dBm ms_txpwr_max = 33
Power Class = 4 <server> PBGT(n) = [Min(ms_txpwr_max,P) rxlev_dl PWR_C_D] <neighbour> [Min(ms_txpwr_max,P) rxlev_dl] = [27 + 80 (37 35)] [33 + 72] = 0dB
sys12_ch05_14a
EMOTOROLA LTD. 2004
429
Type 1
Version 1 Rev 0
Type 1
Power budget exercise part 1
The figures specified on the facing page can be used by the HDPC to calculate the Power budget assessment. Use the working area to calculate PBBT (n).
SERVING (macro) serving= serving= serving= min (ms_txpwr_max,P) rxlev_dl PWR_C_D
NEIGHBOUR (micro) neighbour= neighbour= neighbour= min (ms_txpwr_max(n),P) rxlev_ncell (n)
PBGT (n) = Serving Neighbour PBGT (n) = PBGT (n) =
Power budget exercise part 2

If the measured parameters remain the same and the neighbor was a microcell what would you change if you wished the PBGT(n) figure to equal at least 8. Note: the uplink of the microcell does not require 33 dBm. It would only require 25 dBm.
Parameter ......................... could be altered to equal ......................
430
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 1
Type 1 Power Budget Example

S
SERVING CELL DATABASE PARAMETERS Cell identity= 234 10 255 038 max_tx_ms= 33 dBm max_tx_bts= 0 (43dB) ms_txpwr_max_def = 33dBm add_neighbour external 234 10 256 039 ms_txpwr_max_cell= 33dBm
BEST NEIGHBOURS DATABASE PARAMETERS Cell identity= 234 10 256 039 ms_txpwr_max_def= 33 ms_txpwr_max_cell= 33
RXLEV AVERAGE SERVING (Reported)= 90dBm NEIGHBOUR= 75 dBm
S S
SERVING CELL DL OUTPUT POWER= 31dBm MOBILE= CLASS 4 CLASS

1 2 3 4 5
MAX POWER
20W 8W 5W 2W 0.8W
dBm
43 39 37 33 29
EMOTOROLA LTD. 2004
431
Criteria 1
Version 1 Rev 0
Criteria 1
Criteria 1 ensures that the mobile is perceiving each neighbours Rxlev at a power level good enough for the downlink path to support a good call, criteria 1 is as follows: rxlev_ncell > rxlev_min(n) + Max (0, Pa) rxlev_ncell is the latest averaged average processed for that neighbour. rxlev_min (n) is the database parameter set in the add_neighbor command. For internal cells rxlev_min_cell is optional and if not specified then rxlev_min_def in the add_cell command of the server is used. The last part of this calculation tempers the perceived downlink rxlev average with the potential uplink path. Max (0, Pa) where Pa = ms_txpwr_max(n) P
P = max power of ms If the MS is suited for the PLMN in question Pa will always equal either zero or a negative value and will therefore not be considered. The value of ms_txpwr_max (n), can be set by ms_txpwr_max_def in add_cell for undefined adjacent cells and ms_txpwr_max_cell in add_neighbor. If the MS is not suited to that neighbour, ie its maximum power can not support that required by that cell then the averaged rxlev_ncell would have to become a greater value to overcome this handicap. Criteria 1 would therefore prevent such a handover until the MS was deeper into that neighbour. Any neighbour failing Criteria 1 is not further considered in any handover decision process. The software bin and hence averages used for criteria 1 are created in the averaging mechanism chg_cell_element surround cell for per cell averaging or from add_neighbor per neighbour surround_cell hreqave which in both cases is pointed to by decision_1_ncell_av_h_calc in add_cell. In the example shown opposite the neighbour receive level minimum has been set to 80dBm and the actual receive level is 70dBm. Even after the mobile power has been taken into consideration criteria 1 allows the neighbour to be taken into consideration for further processing by criteria 2.
432
EMOTOROLA LTD. 2004
Version 1 Rev 0
Criteria 1
First Criteria
80dBm 70dBm
Serving
Neighbour
rxlev_min_cell = 30 ms_txpwr_max = 39
MS Power Class 4 (P)
rxlev_ncell > rxlev_min(n) + max (0,Pa) Pa = ms_txpwr_max P 70 > 80 + 6 70 > 74 6 = 39 33
sys12_ch05_17
EMOTOROLA LTD. 2004
433
Criteria 2
Version 1 Rev 0
Criteria 2
Each neighbour, for that mobile, that satisfies criteria 1 is then subjected to criteria 2. criteria 2 specifies that: PBGT(n) ho_margin ho_margin for both external and internal cells can be specified in the add_neighbor command. For internal cells this parameter is optional and if not specified then the ho_margin_def in the add_cell of the neighbour is used. Criteria 2 will produce a result for each neighbour, which has got to be greater than zero for consideration by the specific handover procedure to follow. For microcellular the neighbours are then ranked by algorithm type. The neighbour software bin and hence the averages used in criteria 2 are set in chg_cell_element surround_cell which is pointed to by decision_1_ncell_rxlev_av_h_calc in add_cell. The server averages used in criteria 2 are again set in chg_cell_element rxlev_dl_ho which in this case is pointed to by decision_1_p_bgt_rxlev_av_h in add_cell. In the example shown the power budget calculates to 2dB. The ho_margin is set to 6dB, once criteria 2 is applied, it gives a value of 4dB.
434
EMOTOROLA LTD. 2004
Version 1 Rev 0
Criteria 2
Second Criteria
80dBm
70dBm
Serving 35dBm
rxlev_min_cell = 30 ms_txpwr_max = 33 max_tx_bts = 0 max_tx_ms = 33
Neighbour 43dBm
ms_txpwr_max = 33 ho_margin = 6
<server>
MS Power Class 4 (P)
<neighbour>
PBGT(n) = [Min(ms_txpwr_max,P) rxlev_dl PWR_C_D] [Min(ms_txpwr_max,P) rxlev_dl]
2 = [33 + 80 (43 35)] [33 + 70] Criteria 2 specifies PBGT(n) ho_margin 2 6 = 4dB
sys12_ch05_18
EMOTOROLA LTD. 2004
435
Type 1 Algorithm
Version 1 Rev 0
Type 1 Algorithm
Uses
This is an extension of an existing algorithm to a per neighbour basis. As this is the case, it will still mainly be used in its traditional role, that of macro to macro handovers.
436
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 1 Algorithm
Type 1 Algorithm
Uses Serving cell is a macrocell Preferred handover mechanism for macro to macro handovers Trigger mechanism is PBGT Ordering for microcell algorithm
Macrocell (Type 1)
Macrocell (Type 1)
sys12_ch05_19
EMOTOROLA LTD. 2004
437
Type 2 Algorithm
Version 1 Rev 0
Type 2 Algorithm
If a neighbour is defined as a type 2 in the database, that means that a handover to that cell will only be triggered imperative causes. Normally used to defined macro neighbours in microcells. This algorithm type is used for Macrocells neighbours and any other neighbours to which power budget handovers are not allowed. The element pbgt_ho_needed shall always be set to FALSE for neighbours of this type.
438
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 2 Algorithm
Type 2 Algorithm
To retain traffic in a microcellular layer, the marcocell is made a type 2 neighbour. This algorithm type is used for macrocells neighbours and any other neighbours to which power budget handovers are not allowed. If an imperative handover takes place (rxlev/rxqual), type 2 neighbour gets priority.
Additionally if an type 3 (round the corner neighbour) generates a handover cause and the handover fails then a type 2 neighbour will be next in the candidate list
Macrocell (type 2 neighbour)
HO fails MS hands up to macrocell

Microcell Microcell
sys12_ch05_20
EMOTOROLA LTD. 2004
439
Type 3 Algorithm
Version 1 Rev 0
Type 3 Algorithm
The operator has the option to select a power budget algorithm where once the standard GSM power budget conditions have been met, an additional restriction must be overcome before a power budget handover will be initiated to that neighbour cell. The additional restriction being that of the serving cell uplink and downlink RXLEVs must be below specified thresholds. These thresholds are defined on a per neighbour basis. This algorithm prevents power budget handovers to neighbours located around a corner until the receive levels of the serving cell has dropped below the thresholds, indicating that the MS has moved around the corner. This guards against the case where the threshold is crossed only due to a temporary fade. The probability of this happening both in the uplink and downlink is low due to the 45Mhz frequency separation. Signal losses of as much as 2030 dBs in the space of 1040 metres can be measured when turning a street corner. With this in mind, it is imperative that the handover algorithm reacts quickly enough to maintain the call. In the diagram opposite, a mobile is using Micro 1. When it reaches the area A, the signal level of Micro 2 will be higher but if the mobile does not turn the corner it is not necessary to handover to Micro 2 as this cell would experience a high drop in rxlev around the corner 4. This scenario could lead to drop calls when the speed of the mobiles is high. Using the type3 algorithm with this configuration will avoid the potential problems by maintaining the call on micro 1. Another feature implemented in this configuration is an alternative ordering in the handover candidate list. When a handover is generated for an aroundthecorner type3 neighbour but the microcell is blocked as the corner is turned, all macro neighbours will be considered as candidates, ordered by PBGT. This will avoid problems in the scenario where the mobile turns the corner, as the server signal level is expected to drop abruptly and a handover to the macro layer is triggered. An other application for this algorithm would be where there is a serving microcell and an in building microcell.
GSR5 Enhancements
An optimised type 3 pbgt handover algorithm has been introduced since GSR 5. This makes use of relative thresholds (path loss) instead of absolute level thresholds. This takes into account that the BTS maybe using adaptive power control and prevents handovers occurring at different points for different carriers. For a handover to take place [Pbgt(n) > ho_margin] and [dl path loss > dl threshold] and [ul path loss > ul threshold] Generate handover cause Note: ul path loss = ul transmit pwr ul rxlev dl path loss = dl transmit pwr dl rxlev
440
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 3 Algorithm
Type 3 Algorithm
If microcell is blocked after the corner is turned, all macrocells are considered as neighbours by power budget.
If the mobile follows this direction, Cell 2 would not only have to meet power budget requirements, but the rxlev both on the ul and dl would have to fall below a preset level on the server.
Cell 1
ul_rxlev_serv_l dl_rxlev_serv_l
Cell 2
When mobile passes through A, it would be undesirable to hand over to Cell 2
sys12_ch05_21
900 Cell type 3 neighbour
1800 Cell serving
PBGT (n) criteria met for 900 cell Rxlev on 1800 server has to fall below preset level ul_rxlev_serv_l and dl_rxlev_serv_l (add_neighbour)
sys12_ch05_21
EMOTOROLA LTD. 2004
441
Type 4 Algorithm
Version 1 Rev 0
Type 4 Algorithm
This configuration is typically (but not exclusively) used between micro neighbours that are near LOS related. The algorithm incorporates a delay timer to limit the handover rate and to force fast moving mobiles to hand up to the macro layer before quality of service is degraded. This configuration is identified as type 4 in the database definition. System behaviour is dependent upon mobile speed. If the speed is low enough the microcellular system will take the call, but if the speed increases the call will be handed up to the macrocellular layer. The algorithm contains the additional restriction that the MS must have been on the current channel for at least the number of SACCH periods defined by the per neighbour parameter qualify_time. This value is compared to a counter qualify_count, which is initially set to zero when the MS enters that cell and incremented every time a measurement report is received for that channel until the value reaches a maximum value of 255. If the mobile qualifies for the standard power budget handover, the quality_count is compared to the qualify_time. If the qualify_count is greater than qualify_time, then that neighbour is set to true for a power budget handover. qualify_time 0 to 255 SACCH multiframes
In the example opposite, a mobile located in a car handed into the microcellular system (Microcell 1) when it was stopped at a traffic light: the system considered it was a slow moving mobile. If the vehicle speed subsequently increases such that the mobile is considered fast moving by the system, the timer of the serving microcell will prevent the handover to Microcell 2 and this mobile will be forced to hand up to the macro layer through an imperative handover. Note: The timer can be set to zero and then can be used as the standard power budget handover mechanism between microcells due to candidate ordering.
442
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 4 Algorithm
Type 4 Algorithm
Mobile handed up to Macro layer because it has not been in the cell long enough
Mobile handed over Mobile handed over to to microcell as it meets microcell 2 2 as itmeets
power budget requirements power budget requirements
qualify_time = 100 Approx time 50s
to handover to mircrocell 3
for power budget reasons
and qualifies time and qualifies forfor time

because it it has been because has been stationary atat the traffic lights stationary the traffic lights for more than 50s s for more than 50
Microcell 3
Microcell 2
Microcell
Time spent in microcell 2 = 10s
qualify_time = 0 time = 0s
Microcell 3 = type 4
A Pbgt handover is triggered from microcell 1 by type 4 neighbour

Candidate ordering places type 4 neighbours at the top of list
Time is not a factor for microcell 2 as qualify_time = 0
sys12_ch05_22
EMOTOROLA LTD. 2004
443
Type 5 Algorithm
Version 1 Rev 0
Type 5 Algorithm
In this case the trend of the neighbour signal level is monitored. To allow a handover to a neighbour defined to use this configuration, its level has to exceed a threshold for a defined period of time. This configuration may be used to hand down from the macro to the micro layer when a microcell neighbour is deemed to have a high signal level continuously for a period of time. The period and threshold may be configured to control the handover rate between layers and to identify the mobiles whose speed is over the desired limit and therefore should remain in the macro layer.
Algorithm Description
The rxlev threshold (rxlev_ncell_h) is set in add_neighbor as is the qualify_delay timer which is set in SACCH multiframes. This delay is stored in the element qualify_delay_count and is initialised to the value set in qualify_delay. Once the call qualifies for the standard GSM power budget algorithm and the neighbour exceeds the rxlev threshold, the qualify_delay_count is decremented. If the neighbour goes below the rxlev threshold the qualify_delay_count is reset to the qualify_delay value. The power budget need is only set to true once the qualify_delay_count reaches 0. qualify_delay 0 to 255 SACCH multiframes rxlev_ncell_h 0 to 63 In the example opposite, a fast moving mobile is identified by the serving macrocell and is never handed down to the micro layer. It did not report the microcell signal level as exceeding the required threshold for long enough.
444
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 5 Algorithm
Type 5 Algorithm
Macro
Microcell C MS qualifies for Pbgt handover Rxlev = 70dBm
Time in secs = 10
qualify_delay = 30 (approx 15s) rxlev_ncell_h = 40 (70dBm)

sys12_ch05_24
EMOTOROLA LTD. 2004
445
Optimisation of type 5 handovers
Version 1 Rev 0

Type 5 handovers are intended for handdown calls from macrocells to microcells. A problem occurs though with the indoor environment. This is because good quality might exist with relatively low RXLEV. As handdowns are based on relatively high threshold (based on outdoor situation) a handdown to macrocell to microcell might not take place, even when the microcell is the correct cell for the call to be in. To avoid this problem, optimisation of this procedure causes type 5 handover algorithm to ignore the level threshold when the power budget between the serving cell and the neighbour cell meets a settable handover margin. ho_margin_type5 63 to 63 def = 63 (set in modify_neighbor) If rxlev(n) > rxlev_ncell_h or pbgt(n) > ho_margin_type5(n) Then decrement qualify_delay_count or else reset qualify_delay_count if rxlev(n) < rxlev_ncell_h or pbgt(n) < ho_margin_type5 (n) If qualify_delay_count = 0 and pbgt(n) > ho_margin_type5 (test only) Then handover maybe generated if pbgt(n) ho_margin_cell > 0
446
EMOTOROLA LTD. 2004
Version 1 Rev 0
rxlev_ncell_h = 30 qualify_delay = 10
Serving Cell (Macro)
ho_margin_type5 = 10 ho_margin(n) = 8
75dBm
81dBm
Neighbour Cell (Pico)
Pbgt (n) = 6dB rxlev (n) > rxlev_ncell_h 81> 80 No

or
pbgt (n) > ho_margin_type5 (n) 6 > 10 Yes
Decrement qualify_delay_count (10 SACCH) Genrate handover if pbgt(n) ho_margin(n) > 0 6 (8) = 2 Better Cell handover triggered
EMOTOROLA LTD. 2004
447
Type 6 Algorithm (Delay PBGT using Dynamic ho_margin)
Version 1 Rev 0

This configuration is designed to penalise the handover margin for a defined period of time. When the PBGT calculation exceeds the ho_margin, the penalty will be applied and when a timer expires a different value will be subtracted from the ho_margin. Effectively it attempts to limit the handover rate and may be used to hand down to the microcellular layer as fast mobiles may be identified via this mechanism as well. It may also be used between microcells to force the fast mobiles to hand up to the macro layer. In addition, the algorithm has the flexibility to allow the handovers during the penalty time in the scenario where rxlevs of the cells change very fast and the PBGT calculation exceeds the dynamic ho_margin requirements. The algorithm makes use of a dynamic handover margin. It also makes use of three database parameters set in add_neighbor. ho_static_offset 0 to 127 ho_dynamic_offset 0 to 127 delay_time 0 to 255
Description of variables
ho_margin(n) Per neighbour handover margin. ho_margin _dyn Local variable used within this procedure only qualify_delay_count(n) Value stored per neighbour in the active data block
Algorithm Definition
Initially if the pbgt(n) is greater than ho_margin(n) , then the count of qualify_delay_count is set to delay_time. For each measurement report received, the PBGT(n) is checked and criteria 1 and 2 calculated. If: qualify_delay_count(n) > 0 then qualify_delay_count(n) = qualify_delay_count(n) 1 (SACCH Multiframes) and ho_margin_dyn = ho_margin(n) + ho_static_offset If qualify_delay_count(n) = 0 then ho_margin_dyn = ho_margin(n) + ho_static_offset(n) ho_dynamic_offset(n) If pbgt(n) > 0 and pbgt(n) > ho_margin_dyn Then a power budget handover reason is set to true for this neighbour.
448
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 6 Algorithm
ServCell
N/bourCell
PBGT(n) > ho_margin......Timer starts ho_margin_dyn = ho_margin(n) + ho_static_offset(n) Timer expires ho_margin_dyn = ho_margin(n)+ho_static_offset ho_dynamic_offset If PBGT(n) > 0 and PBGT(n) > ho_margin_dyn PBGT handover need
PBGT(n)(10dBm) > ho_margin_dyn (2 + 4 2 = 4) Yes so the indoor cell set to true for this neighbour PBGT(n)(4dBm)>ho_margin(2dBm) Count = 60 SACCH ho_margin_dyn = 2+4 = 6 Too much for PBGT to indoor cell
ho_static_offset = 4 ho_dynamic_offset = 2 delay_time = 60 (30s)
PBGT(n)(0dB)>ho_margin_dyn (2 + 4 2) = 4 No so the indoor cell is set false as a neighbour
Diagram number
Time taken 30s
EMOTOROLA LTD. 2004
449
Handover Scenario for Adjacent Channels (Both BCCH Carriers)
Version 1 Rev 0

Ideally there should be separation between the micro and macro layer frequency bands. If the frequency spectrum is limited in a particular network it may be necessary to assign adjacent channel frequencies. The GSM recommendations indicate that degradations occur at an adjacent channel interference level of about 9dB in a fading channel (no shadowing). This means that for a mobile moving from one microcell to another, where the channels assigned are adjacent (see diagram), there is a limited window in which handover can occur. Only as the neighbour cells signal gets within 9dB of the serving channel does the neighbour BSIC become decodeable. The MS can then start reporting this neighbour channel and the BSS can start the averaging process. If the handover command is not sent before the target channel exceeds the serving channel by 9dB, the handover may fail because the handover command becomes corrupted. The other constraint on the handover is that the handover process itself will only start when the power budget expression exceeds the ho_margin. The handover success rate is largely dependent on mobile speed and adjacent channel handover parameters. To minimise problems the following recommendations should be adopted; S S Use as large a frequency set as possible in the microcell layer. As far as possible avoid the use of adjacent channels in adjacent cells. Wherever possible, avoid the use of adjacent channels in neighbour cells which are round the corner from each other. The rapid signal changes in a round the corner scenario make the window in the diagram smaller in terms of distance travelled. Avoid the use of adjacent channels in neighbour cells which may encounter fast moving mobiles. Use short averaging periods and low ho_margins for adjacent channel handovers. In cases where micro/macrocell frequencies are separated only by a narrow guard band, (one channel), the microcell frequency which is nearest to the macrocell frequency, should be assigned to the microcells furthest away (in distance) from the macrocell. If none of the above recommendations can be adopted then use of the 7th algorithm type may be utilised.
S S S
450
EMOTOROLA LTD. 2004
Version 1 Rev 0
Power
Serving Neighbour
9dB
9dB
Distance
Adjacent BSIC is decode able here Target PBGT beats ho_margin ho_command becomes unreliable
S S S S S S
Large micro frequency set Avoid adj channel frequencies for round the corner neighbours Avoid the use of adj channels which are likely to encounter fast handovers Use short averaging periods and low ho_margins for adj channel Distance adj channel micros from macro Alternatively use the type 7 handover algorithm
sys12_ch_03_09
EMOTOROLA LTD. 2004
451
Type 7 Algorithm
Version 1 Rev 0
Type 7 Algorithm
In large microcellular deployments where frequency spectrum for micros is limited, there are situations where it is impossible to avoid deploying adjacent microcells with adjacent BCCH frequencies. As a mobile being served by one of these cells approaches the interfering neighbour cell, the quality of the call degrades perhaps to the point of dropping altogether. Assuming that both cells have only a single carrier, neither an intracell handover nor a handover to the interfering neighbour improves the situation. This algorithm allows a third Cell, which is not on an adjacent channel, to be the preferred target for handover even though an interfering neighbour may have the strongest signal. When Power budget adj_chan_ho_margin > 0 a handover will be generated before the neighbour signal strength (and thus interference) becomes too strong to drop the call.
Algorithm Definition
During the handover detection phase the type 7 algorithm computes the power budget equation using rxlev averages from the bin dl_rxlev_av_h_dec for the serving cell and ncell_rxlev_av_h_calc for type 7 neighbour cells and evaluates the equation Power budget adj_chan_ho_margin > 0 If any of the type 7 neighbours pass the above equation, a handover cause of ADJ_CHAN_INTF is detected, this is an imperative handover even through the power budget equation is used to detect the handover. The relative priority of this handover is just above that of the power budget handover. The handover is performed to a cell different from this neighbour. This is managed because we delete the neighbour that activated this condition from the candidate list as it will be explained in the candidate list generation section. Any neighbours that satisfy criteria 1 will be a candidate for handover. If no neighbours satisfy criteria 1 then no handover will be generated. A database parameter is included to detect the risk coming from neighbours in adjacent frequencies, when defined as type 7, this is adj_chan_ho_margin. adj_chan_ho_margin 63 to 63 (set in add_neighbor)
452
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 7 Algorithm
Type 7 Algorithm
Cell A
Cell B
ARFCN 10
ARFCN 11
Type 7
Serving cell
ARFCN 21
Cell C
pbgt adj_chan_ho_margin > 0 (for cell B) Cell B satisfies criteria for PBGT handover but fails additional constraint of adj_chan_ho_margin Cell C passes criteria 1 so handover generated to it
sys12_ch05_26
EMOTOROLA LTD. 2004
453
Type 7 Algorithm
Version 1 Rev 0
454
EMOTOROLA LTD. 2004
Version 1 Rev 0
Type 7 Algorithm
Type 7 Algorithm Example
Handover to Macro
Macro ARFCN = 21
ARFCN = 10 Micro (Serving)
adj_chan_ho_margin = 9 pbgt(n) Micro = 10 ho_margin(n) = 6
pbgt(n) pbgt_adj_chan_ho_margin > 0 10 9 > 0 PBGT handover changed to imperative Use long hreqave so changes take longer time to alter outcome
Handover to Micro when pbgt allows use adj channel int test
ARFCN = 11 Micro
sys12_ch05_27
EMOTOROLA LTD. 2004
455
Interference Avoidance Test
Version 1 Rev 0

Another problematic situation could appear when calls are handed over to a cell that has a neighbour with adjacent (BCCH) frequency. It is possible to enable the BSS to perform an interference avoidance test on the neighbour candidate before handing it over a call. This test can be done regardless of which of the seven types is used for this neighbour. If adj_chan_intf_test enabled in NEIG1and any other valid neighbour NEIG2 (of the current cell) has an adjacent channel frequency with the candidate neighbour (NEIG1) then perform following check: Candidate neighbour rxlev rxlev of neighbour on adj chan < adj_chan_rxlev_diff If check fails then delete neighbour N1 from candidate list. adj_chan_intf_test 0 = no 1 = yes adj_chan_rxlev_diff 63 to 63 (both set in add_neighbor)
Example
A mobile is on a serving cell and detects a neighbour with an adjacent channel frequency, the candidate neighbour rxlev is 70dBm and the adjacent channel neighbour rxlev is 75dBm. adj_chan_rxlev_diff = 9dB So Candidate neighbour rxlev rxlev of neighbour on adj chan < adj_chan_rxlev_diff 70 (75) < 9 5<9 The check has failed as the rxlev difference between the two neighbours is only 5dB which would cause a interference problem to the MS.
456
EMOTOROLA LTD. 2004
Version 1 Rev 0
Adjacent Channel Interference Avoidance Test
Cell A
adj_chan_intf_test = 1
Cell B
For Cell B and Cell C
ARFCN 20
ARFCN 10
Serving cell
ARFCN 11
Cell C
Cell B and Cell C is a valid neighbour of the serving cell A Cell B rxlev Cell C rxlev < adj_chan_rxlev_diff If test fails remove candidate neighbour from candidate list
sys12_ch05_28
EMOTOROLA LTD. 2004
457
Setting of Candidate List
Version 1 Rev 0

Using the microcell implementation, each neighbour is assigned a power budget algorithm to be used for that neighbour. Upon receipt of each measurement report the BSS uses the assigned algorithm for each neighbour reported by the MS to determine if the MS qualifies for a power budget handover to that neighbour. The BSS then evaluates the number of neighbours that qualify for a power budget handover. These neighbours are then prioritised based on the algorithm used to determine the power budget handover qualification and the value of the power budget calculation. The BSS will then manipulate the list of candidate cells based on the flow chart opposite. Further to this process there are a number of alternative functions that are defined in course SYS03 Database Applications. Specifically these are: worse_neighbor_ho Allows handovers to a neighbour with a lower rxlev than the current serving cell. ho_only_max_power For uplink handovers, the MS must be at full power. For downlink handovers, the base must be at full power to take place. neighbor_journal =1 No warm up period for neighbours, all neighbour information padded with zeros. Averaging and power budget calculation will begin immediately.If a previously reported neighbour is missing in the measurement, a zero rxlev is used for the neighbour. Stored neighbour information will be removed when the disuse count is equal to the surrounding cell hreqave (set in add_neighbor) or 8 depending on the setting of disuse_cnt_hreqave. neighbor_journal = 0 There is a warmup period for the surround cell hreqave before power budget calculations begin. The last received rxlev for the unreported neighbour will be used for missing data. Stored neighbour information will be removed when the disuse count is equal to the surrounding cell hreqave (set in add_neighbor) or 8 depending on the setting of disuse_cnt_hreqave. disuse_cnt_hreqave 0 Use max count which equals 8 1 Use surround cell hreqave (set in add_neighbor) In case of a mobile missing reports, attention should be paid to the parameter missing_rpt in the add_cell: If missing_rpt = 0 The last measurement value is repeated and the averaging, voting and handover decisions will still be done. One limiting factor in time to go on repeating measurements is link_fail, when this counter expires then the link will be broken down under control of T3109. If missing_rpt = 1 No averaging or handover will happen and this measurement report will be forgotten. No dl handover or power control decisions will be made. The uplink ones will continue as normal.
458
EMOTOROLA LTD. 2004
Version 1 Rev 0

In
Remove any neighbours that fail the interference avoidance test
Remove any neighbour that does not satisfy additional requirements of its algorithm (NA type 1 and 2) Evaluate Criteria 1, then all that pass evaluate by Criteria 2 so all candidates sorted in order of PBGT with The strongest neighbour first
Handover triggered by type 3 neighbour
yes
Neighbour candidate list: All algorithm 3 neighbours All algorithm 1 and 2 neighbours Any algorithm 4,5 and 6 neighbours
Prefers type 3 neighbours, uses type 2 neighbours as default candidates, then others as last resorts
no
Out
Handover triggered by type 4,5 or 6 neighbour
yes
Neighbour candidate list: Remove algorithm 2 neighbours Any algorithm 4,5 and 6 neighbours Any algorithm 1 neighbours
no
Handover triggered by imperative handovers or adj chan int
yes
Neighbour candidate list: Remove any algorithm 7 neighbours which fail test: All algorithm 1 and 2 neighbours Any other neighbours
no
Out
SYS12_Ch4_29
EMOTOROLA LTD. 2004
459
Handover Margin Per Cause
Version 1 Rev 0

Two handover margins have been configured per neighbour, specific to the cause of the handover being performed. This cause specific handover margin will always be used in determining if the neighbour should be excluded from the candidate list. The value assigned is set by using the modify_neighbor command. ho_margin_rxqual[n](63 to 63): The value to be applied to the PBGT calculation when handover cause is RXQUAL. If PBGT ho_margin_rxqual[n] < 0, the neighbour will be excluded. ho_margin_rxlev[n] (63 to 63): The value to be applied to the PBGT calculation when handover cause is RXLEV. If PBGT ho_margin_rxlev[n] < 0, the neighbour will be excluded A per cell flag is used to determine if the cause specific margin should be used in the candidate ordering procedure. ho_margin_usage_flag = 0 ho_margin[n] value (standard handover margin) will be used for sorting the candidate list for RXLEV and RXQUAL handovers. ho_margin_usage_flag = 1 ho_margin_rxqual[n] or ho_margin_rxlev[n] will be used for sorting the candidate list for RXQUAL or RXLEV handovers. Individual neighbours can be guaranteed to not be the target of a particular type of handover by setting the cause specific margin to the highest value. The margin can be set to control the level at which the neighbour must be at before considering it as a candidate for a specific handover cause.
Application
With this feature, there is more flexibility since it gives the possibility to: Avoid the handover to unwanted neighbours where the call will be at risk. Sort the neighbours in the desired order, for going to the less congested cells or to the less interfered neighbours. Handover the calls only to good neighbours. For some of them this condition will be satisfied, even with negative PBGT to the server and for others, it will be necessary to have positive PBGT.
460
EMOTOROLA LTD. 2004
Version 1 Rev 0

Exclusion procedure:
Remove neighbor from candidate list if: PBGT ho_margin(n)<0 _ (Better Cell Handover)
Remove neighbor from candidate list if: PBGT ho_margin_rxqual(n)<0 _ _ (UL/DL RXQUAL Handover)
Remove neighbor from candidate list if: PBGT ho_margin_rxlev(n)<0 _ _ (UL/DL RXLEV Handover)
Sorting Procedure
yes
ho_margin_flag =0?
no
Sort neighbours based on: Pbgt ho_margin_rxqual(n) (ul/dl RXLEV Handovers) Sort neighbours based on: Pbgt ho_margin(n) (All other handover causes)
Sort neighbours based on: Pbgt ho_margin_rxlev(n) (ul/dl RXQUAL Handovers)
Sort neighbours based on: Pbgt ho_margin(n) (All other handover causes)
SYS12_Ch4_30
EMOTOROLA LTD. 2004
461
RXQUAL and Microcell Enhancements
Version 1 Rev 0

Timed Offset upon RXQUAL Handover
This feature addresses a particular situation that normally happens in the systems: it is possible for the serving cell to have a much better RXLEV than a neighbour when a call is handed over to the neighbour for RXQUAL reasons. This situation would likely result in a power budget handover back to the original serving cell. If the poor RXQUAL condition still exists, the call may experience a continuous bouncing between cells. The pingpong protection mechanism is implemented to help in this situation. When a channel is activated as the target channel of a RXQUAL handover, the bounce_protect_qual_tmr is started. Its value is the number of SACCH periods during which bounce_protect_margin is applied. When a channel is activated as the target channel of a congestion handover, the bounce_protect_cong_tmr is started. Its value is the number of SACCH periods during which bounce_protect_margin is applied. bounce_protect_margin: additional value added to the configured ho_margin of the source cell
An interference handover cause which results in an intercell handover due to lack of resources on the serving cell will be treated in the same way as a RXQUAL handover. bounce_protect_qual_tmr 0 to 127 SACCH periods Default = 0 (disabled) bounce_protect_cong_tmr 0 to 127 SACCH periods Default = 0 (disabled) bounce_protect_margin 0 to 127 (decibels) Default = 0
462
EMOTOROLA LTD. 2004
Version 1 Rev 0
Handover for quality reasons
Handover for quality reasons
Good RXLEV
Serving
Neighbour
bounce_protect_qual_tmr = 20 (10s) bounce_protect_margin = 20 (20dB)

20dB is added to the ho_margin for 10s to prevent the mobile being handed back to the original server for power budget reasons
SYS12_Ch4_31
EMOTOROLA LTD. 2004
463
Micro Micro Quality Handover
Version 1 Rev 0

When a RXQUAL handover condition exists, a layer indication for the serving cell and the type of neighbour within the environment (identified by the PBGT algorithm utilised by that neighbour) will be used to prioritise the microcell neighbours, thereby attempting to handover, as well as maintain, the call within the microcellular layer. The lower the number for the layer indication, the larger the layer. Currently, this means that cell level 0 is the macro layer, cell level 1 is the micro layer and cell level 2 is the pico layer. RXQUAL handovers can effectively be disabled to a specific neighbour by setting the ho_margin_rxqual[n] for that neighbour to 63. Prioritisation and ordering of handover candidates will only be performed if the functionality is enabled via the prioritize_microcell flag, and the bounce_protect_qual_tmr is not active.
Commands:
Element layer_number Min 0 Max 2 Default 0 Value Definition 0 = Macrocell 1 = Microcell 2 = Picocell 0 = Disabled Layer of serving cell will not impact sorting of candidate list. 1 = Enabled Layer of serving cell will impact sorting of candidate list. Comments per cell element
prioritize_microcell 0
per cell element
Ordering
The following ordering will only be performed if the functionality is enabled via the prioritize_microcell flag, and the bounce_protect_qual_tmr (Timed Offset upon RXQUAL Handover) is not active. The dependency on bounce_protect_qual_tmr is to prevent a call from pingpongs between two microcells if bad RXQUAL exists in both. RXQUAL condition with call in microcell layer: All neighbours which exceed rxlev_min[n] + Max (0,Pa) All neighbours remaining after exclusion procedure considering handover margin per cause Neighbour types prioritized : (a) 4,5,6 sorted by PBGT ho_margin followed in the list by (b) 3 sorted by PBGT ho_margin followed in the list by (c) 1,2 sorted by PBGT ho_margin RXQUAL condition with call in macrocell layer: All neighbours which exceed rxlev_min[n] + Max (0,Pa) All neighbours remaining after exclusion procedure considering handover margin per cause Neighbour types prioritised : (a) 1 sorted by PBGT ho_margin followed in the list by (b) 2,3,4,5,6 sorted by PBGT ho_margin
Version 1 Rev 0
Prioritize_microcell = 1
Neighbour types 1 Followed by 2,3,4,5 and 6
layer_number = 0
layer_number = 0
Neighbour type 5
Neighbour types 1 and 2
layer_number = 1
layer_number = 1
Neighbour types 4, 5, 6 followed by 3
sys12_ch05_35
EMOTOROLA LTD. 2004
465
Handovers Adaptive
Version 1 Rev 0
Handovers Adaptive
Overview
Normal handovers are triggered by a voting method such that if p from n of the most recent rolling averages meet a certain number, then the need for a handover is recognised. However, this standard method may be too slow to catch a rapidly deteriorating call. The alternative method of adaptive handovers now exists for Quality, Receive Level and Power Budget handovers. The adaptive handover method causes handovers to be recognized based on a cumulative area rather than a vote. The adaptive handover method enables handovers to occur more rapidly when conditions are deteriorating quickly, but less rapidly when conditions are only marginally poor. To achieve this, a cumulative total of the measurements are maintained. For Quality and Receive level adaptive handovers, this total is only maintained if the latest measurement exceeds the handover trigger threshold specific to that type of handover. The total is reset to zero any time there is no marginal need for a handover. For adaptive Power budget handovers, the total is not reset, but maintained using a leaky bucket criterion. This means the total will be incremented when the latest measurement (Pbgt(n)) exceeds the handover trigger threshold (ho_margin), and decremented by the difference, if it does not exceed the trigger level. A handover need is recognized in all cases when the cumulative total value exceeds the cumulative total trigger level, which is independently set for each type of handover. This enhancement to adaptive handovers allows for a third option to the previous two described. With this enhancement, the operator has the option of setting the cumulative area for adaptive power budget handovers on a per cell or per Neighbour basis. This option is provided by modifying adap_ho_pbgt.
466
EMOTOROLA LTD. 2004
Version 1 Rev 0
Handovers Adaptive
Adaptive Handovers
S S
Quick reaction to fading calls Reacts less rapidly when conditions are only marginally poor Based on accumulated report measurements Types:
S S S
S S
Rxlev Rxqual PBgt: Per cell Per neighbour
EMOTOROLA LTD. 2004
467
Adaptive Handovers
Version 1 Rev 0
Adaptive Handovers
The three types of handover that are controlled by adaptive procedure are rxlev, rxqual and pbgt. For the latter type of handover, pbgt may be recognised on a per cell or per neighbour basis.
Adaptive Receive Level handovers.

Controlled by the parameter adap_ho_rxlev. adap_ho_rxlev specifies whether the system allows adaptive receive level handovers. At each measurement report the cumulative area are updated and compared to a cumulative trigger. If the area is greater than the cumulative power adaptive receive level (rxlev) trigger a need for a handover is recognized. 0 Disables adaptive receive level handovers at the location. 1 Enables adaptive receive level handovers at the location. The level set in the parameters adap_trigger_rxlev_dl and adap_trigger_rxlev_ul triggers the handover. Range of both is 0255, which refers to a cumulative total of sequential measurements from the HDPC process. At each new measurement report average (hreqave period) the rxlev of the server is compared against the lower handover threshold for uplink (or downlink). If the level of the server goes below the threshold (in dBs) then: rxlev_cumulative_area = rxlev_cumulative_area + (l_rxlev_xx_h rxlev_xx) xx = ul or dl If the level of the server goes above the threshold (in dBs) then: rxlev_cumulative_area is reset to zero. If the rxlev_cumulative_area exceeds the adap_trigger_rxlev_xx then a handover cause of rxlev is generated for that call.
468
EMOTOROLA LTD. 2004
Version 1 Rev 0
Adaptive Handovers
Adaptive Receive Level Handovers
1st Av measurement report, acc area = 0 rxlev_xx = 15 (95dBm) Cumulative area = 0 + (20 15) = 5 Server Neighbour 2nd Av measurement report, acc area = 5 rxlev_xx = 25 (85dBm) l_rxlev_xx_h = 20 (90dBm) adap_trigger_rxlev_xx = 24 xx = ul or dl
63 47dBm
Cumulative area resets to 0 as server gone above the threshold 3rd Av measurement report, acc area = 0 rxlev_xx = 5 (105dBm) Cumulative area = 0 + (20 5) = 15 4th Av measurement report, acc area = 15
20
90dBm
rxlev_xx = 10 (100dBm) Cumulative area = 15 + (20 10) = 25
110dBm
Cumulative area exceeds adap trigger hence handover CV rxlev generated
SYS12_Ch4_37
EMOTOROLA LTD. 2004
469
Adaptive Receive Quality Handovers
Version 1 Rev 0

Controlled by the parameter adap_ho_rxqual. adap_ho_rxqual (0 Disables, 1 Enables) specifies whether the system allows adaptive quality handovers. At each measurement report the cumulative area is updated and compared to a cumulative trigger. If the area is greater than the cumulative power adaptive quality (rxqual) trigger a need for a handover is recognized. The adap_trigger_rxqual_xx parameter specifies the cumulative trigger level for adaptive rxqual handovers. When the threshold set by this parameter is exceeded, the system performs a quality handover. The range is 0 65535. (where xx = ul or dl) The adaptive handover technique has an alternative set of parameters for use in hopping cells: adap_trigger_hop_rxqual_xx, which specifies the trigger threshold for downlink rxqual for calls that are frequency hopping. At each new measurement report average (hreqave period) the rxqual of the server is compared against the lower handover threshold for uplink (or downlink). If the rxqual of the server goes below the threshold (either by quality bands or BER) then: rxqual_cumulative_value = rxqual_cumulative_value + (rxqual_xx l_rxqual_xx_h) If the rxqual of the server goes above the threshold (in dBs) then: rxlev_cumulative_area is reset to zero. If the rxlev_cumulative_area exceeds the adap_trigger_rxqual_xx then a handover cause of rxqual is generated for that call.
Hopping Parameters
When the cell is frequency hopping two parameters exist so the rxqual adaptive handovers can be optimised. For non hopping carriers the dasebase parameters adap_trigger_rxqual_xx is used. But for hopping carriers where a lower level of BER can be tolerated two other database parameters exist.
chg_element adap_trigger_hop_rxqual_dl <value> <location> chg_element adap_trigger_hop_rxqual_dl <value> <location> The range is 0 65535
470
EMOTOROLA LTD. 2004
Version 1 Rev 0
1st Av measurement report, acc area = 0 rxqual_xx = 453 Cumulative area 0+(453 400) = 53
Server Neighbour
2nd Av measurement report, acc area = 53 rxqual_xx = 226
adap_trigger_rxqual_xx = 1000 alt_qual_proc = 0
Cumulative area resets to 0 as server gone above threshold 3rd Av measurement report, acc area = 0
0 1 2 3 4 5 6 7
sys12_ch05_38
0.14 0.28
rxqual_xx = 905 Cumulative area = 0 + (905 400) = 505
0.57 1.13 2.26 4.53 9.05 18.1 400

Cumulative area = 505 + (905 400) = 1010 Cumulative area exceeds adap trigger hence handover CV rxlev generated 4th Av measurement report, acc area = 505 rxqual_xx = 905
EMOTOROLA LTD. 2004
471
Adaptive Power Budget Handovers
Version 1 Rev 0

Outline
Controlled by the parameter adap_ho_pbgt. S S S 0 = Standard power budget algorithm enabled 1 = Adaptive handover algorithm enabled using percell cumulative area 2 = Adaptive handover algorithm enabled using perneighbour cumulative area
Adaptive power budget handovers are enabled by the parameter adap_ho_pbgt, which allows a choice between a per cell basis where the same trigger values are set for all neighbour cells (trigger set by adap_trigger_pbgt (0255)), or on a perneighbour basis set by adap_trigger_pbgt_nbr (0 255) which sets the trigger level neighbour by neighbour. When measurement reports exceed the trigger, the total is not reset, but maintained using a leaky bucket criterion. This means the total will be incremented when the latest measurement (Pbgt(n)) exceeds the handover trigger threshold (ho_margin), and decremented by the difference, if it does not exceed the trigger level. A handover need is recognized in all cases when the cumulative total value exceeds the cumulative total trigger level.
Cumulative Area
The Cumulative area is a calculation made by comparing the pbgt(n) with ho_margin(n) for every average. If pbgt(n) > ho_margin(n) then (for both per cell and per neighbour options): The pbgt_cumul_area = pbgt_cumul_area + (pbgt(n) ho_margin) Or else if ho_margin(n) > pbgt(n) The pbgt_cumul_area = pbgt_cumul_area (ho_margin(n) pbgt(n)) Note: pbgt_cumul_area cannot be less than 0.
Per Cell: A handover need is recognised if: pbgt_cumul_area > pbgt_trigger Per Neighbour: A handover need is recognised if: pbgt_cumul_area > adap_trigger_pbgt_nbr
472
EMOTOROLA LTD. 2004
Version 1 Rev 0
Adaptive Power Budget handovers
Example
adap_trigger_pbgt_nbr = 20 ho_margin = 5 adap_trigger_pbgt_nbr = 10 ho_margin = 5
n1
n2
pbgt (n1)
pbgt (n2)
Pbgt (n1) ho_margin
Pbgt (n2) Cumulative ho_margin area n1
Cumulative area n2
2 4 6 8 10 12 14
2 0 2 4 6 8 10
3 1 1 3 5 7 9
7 5 3 1 1 3 5
0 0 1 4 9 16 25
0 0 0 0 1 4 9
Pbgt(n) > ho_margin pbgt_cumulative_area = pbgt_cumulative_area + (pbgt(n) ho_margin) Pbgt_cumulative_area > adap_trigger_pbgt_nbr
SYS12_Ch4_39
Handover
EMOTOROLA LTD. 2004
473
Example Application Scenarios for Handover Procedures
Version 1 Rev 0

Opposite is an application example for handovers between microcells with various relationships. The table gives an example of how the Motorola algorithms might be applied in these cases.
Imperative handover from microcell to macrocell

The macrocell is a type 2 neighbour for each of the microcells. This means that if an imperative handover is generated whilst in one of the microcells, the macrocell will always be given high priority (see handover candidate ordering list).
Handdown from macrocell to microcell (handover to a type 5 neighbour)

The 3 microcells are all specified as type 5 neighbours of the macrocell. This allows the possibility of delaying the handdown from the macrocell until the mobile has seen a consistently high signal level from the microcell for a specified time. In this way, fast mobiles will not stay in a microcell long enough to trigger a handdown.
Handover to a type 3 neighbour (round the corner handover)

Microcell 2 is specified to be a type 3 neighbour of microcell 1. This means that a mobile travelling along route A will satisfy the condition for handover because the serving cell RXLEV threshold is crossed as the mobile turns the corner. A mobile travelling along route B, however, will not satisfy the condition for handover because the serving cell RXLEV will remain above the threshold.
Handover to a lineofsight neighbour

Microcells 1 and 3 are lineofsight neighbours,and in this case algorithm 4 is applied. This is used in preference to algorithm 1 since type1 neighbours would have an equal weighting with type 2 neighbours in the event of an RXQUAL handover.
Applying the algorithms

Care must be exercised in the application of these algorithms since the relations between the microcells (LOS or round the corner) depends upon the path taken between them. Depending upon the RF planning, it may be possible to arrange that, having specified an algorithm tailored to one particular route between the cells, then any other route goes via other cells. For example, this could be done to isolate possible areas of adjacent or cochannel interference in the network.
474
EMOTOROLA LTD. 2004
Version 1 Rev 0
Application Scenarios for Handover Procedures
A 3 B 1 Microcells 1,2 and 3
Macrocell B
Macrocell A
sys12_ch05_46
CELL Macro A
NEIGHBOUR Macro B 1 2 3 Macro
ALGORITHM 1 5 5 5 2 3 4 2 3 3 2 4 3
2 3 Macro
1 3 Macro
1 2
EMOTOROLA LTD. 2004
475
Exercise
Version 1 Rev 0
Exercise
S The aim of this exercise is to complete a database with suitable levels (for add_neighbor) using the microcellular principles considered in the course. The strategy for all mobiles is that when idle, they are to be served by the macrocell layer. Fast moving mobiles are to be discouraged from handing into the microcells. Slow moving mobiles in dedicated mode are to be served by the microcell layer. As well as using add_neighbor you may use add_cell of the neighbour if it is an internal neighbour. The following information is to be considered: All cells are on separate sites Rxlev on street: MACROCELL 60dBm MICROCELL 75dBm In building 80dBm Fast moving mobiles spend no more than ten seconds in the microcells (A SACCH multiframe period is 480 msecs). Slow moving pedestrians move past the building containing cell 5 after 10s. All microcells are under the control of a separate BSC from that of the macrocell. All cells are in the same location area. The system is GSM 900. Consider the inbuilding microcell may radiate through the walls to the street. NCC for your network has number (0,4). You can choose a value of BCC for the BSIC. S S S S S S S Serving Cell 0 frequency 45 Macrocell 1 frequency 20 Microcell 2 frequency 43 Microcell 3 frequency 44 Microcell 4 frequency 42 Inbuilding Cell 5 frequency 42
S S S
S S S S S S S
Complete the information you would enter for the neighbors add_cell (not prompted for external neighbours). hreqave is to be set on a per neighbour basis for rxlev(n) averages. ho_margin to be set on a per neighbour basis. Neither directed retry or congestion relief are enabled Concentric cells are not enabled Extended range cells are not enabled Assume for the purposes of this exercise that PBGT adaptive handovers are not employed.
476
EMOTOROLA LTD. 2004
Version 1 Rev 0
Exercise
Microcellular Exercise
FAST MS
MACROCOVERAGE (CELL 1)
INBUILDING CELL 5
FAST MS
MICROCELL 2
SERVER 0
MICROCELL 3
PEDESTRIAN WALKWAY
MICROCELL 4
= ANTENNA
sys12_ch05_MicEx
EMOTOROLA LTD. 2004
477
Exercise
Version 1 Rev 0
add_neighbour srccell_id xxx xx xxx xx0 neighbor_cell_id xxx xx xxx xx1 Placement _ _ _ _ list type _ _ _ _ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____
add_cell
(frequency)
frequency_type = BSIC = max_tx_ms = rxlev_min_def =

Version 1 Rev 0
Exercise
add_cell
(frequency)

Exercise
Version 1 Rev 0
add_cell
(frequency)

Version 1 Rev 0
Exercise
add_cell
(frequency)

Exercise
Version 1 Rev 0
add_cell
(frequency)
482
EMOTOROLA LTD. 2004
Version 1 Rev 0
Database Parameters
Database Parameters
add_neighbor
The current add_neighbor command includes all parameters on the command line. The microcell feature will change the add_neighbor command to prompt for the necessary information to enable the microcellular types.
Separate BA Lists
The separate BA lists allows the operator to select neighbours to be included in the BCCH Allocation on the SACCH and the BCCH. The BSS maintains two separate lists ba_bcch This list is the BA sent in system information message type 2 on the BCCH. It is the list of frequencies in use by a given PLMN in a given geographical area. It is used by the MS for cell selection and reselection. ba_sacch This list is the BA sent in system information message type 5 on the SACCH. It indicates to the MS which BCCH frequencies are monitored for handover purposes. By maintaining two distinct BA lists, the operator is given the flexibility to vary the frequencies the MS monitors in idle mode independent of the frequencies the MS monitors as potential neighbours in dedicated mode. It is possible to set a combined total of 64 distinct frequencies in the ba_bcch and ba_sacch lists. Each of these frequencies can be included in one or both of these lists. However, the number is restricted to 32 frequencies in the ba_sacch. This limit is consistent with the number of different frequencies the MS can report on in measurement report messages based on the format of the messages. The ba_bcch may contain up to the total of 64 distinct frequencies only if all the frequencies included in the ba_sacch are included in the ba_bcch. Note 1: The neighbor_cell_id may be placed with the string test# where # is a number between 1 and 64. The addition of test neighbours are to add frequencies to the ba_sacch and/or ba_bcch lists. Therefore, for test neighbours the placement will be an optional parameter and ignored if entered and the frequency will be the only prompted parameter. Note 2: If the list_type is ba_bcch and placement is internal, no data will be prompted.
EMOTOROLA LTD. 2004
483
Database Parameters
Version 1 Rev 0
add_neighbor
Command name: Security Level: Function: Parameters:

<src_cell_id> <neighbor_cell_id> <placement>
add_neighbor 2 Used to add one neighbour cell to another a source cell neighbour list
Cell identity of the cell to which a neighbor is being added. Cell identity of the cell specified as a neighbour to the source cell. internal external Specifies that the neighbour cell is inside the BSS. Specifies that the neighbour cell is outside of the BSS.
<list_type>
ba_bcch
Put neighbours frequency on the ba_bcch list. ba_sacch Put neighbours frequency on the ba_sacch list. both Put neighbours frequency on the ba_bcch and ba_sacch lists.
484
EMOTOROLA LTD. 2004
Version 1 Rev 0
Database Parameters
Add Neighbor Prompts Table

Prompt Enable synchronization: Range 1 (Yes) 0 (No) pgsm egsm dcs1800 pcs1900 gsm850 1 to 124 for GSM900 0, 1 to 124, 975 to 1023 for EGSM900 512 to 885 for DCS1800 512 to 810 for PCS1900 0 to 63 0 Default Notes N/A for external neighbours N/A if source cell is at a Horizonoffice BTS N/A for internal neighbours.
Enter the neighbour cell frequency type:
None
Enter the BCCH frequency number:
None N/A for internal neighbours A value MUST be entered at this EGSM BCCH frequencies 0, prompt. 975 to 1023 are not available when the egsm_bcch_sd parameter is disabled. None N/A for internal neighbours A value MUST be entered at this prompt. None N/A for internal neighbours A value MUST be entered at this prompt.
Enter base station identity code (bsic):
Enter MS transmit power maximum:
Enter neighbour receive level minimum: Enter neighbour handover margin:
5 to 39 (odd values only) for PGSM and EGSM 0 to 30 (even values only) for DCS1800 0 to 32 (even values only) and 33, for PCS1900 0 to 63
rxlev_min_def of neighbour cell ho_margin_def of neighbor cell
Required for external neighbours Required for external neighbours Refer to the description of the ho_margin_def parameter. Only prompted if inner_zone_alg for the source cell is set to 2, and the neighbour is being added to the SACCH list N/A if source cell is at a Horizonoffice BTS Only prompted if Does the neighbour have a carrier with an interfering frequency? = 1 (yes).
63 to 63
Does this neighbour have a carrier with an interfering frequency?
0 (No) 1 (Yes)
0 (No)
Enter the threshold for inner zone 0 to 63 handover
EMOTOROLA LTD. 2004
485
Database Parameters
Version 1 Rev 0
Prompt Enter the margin for inner zone handover
Range 0 to 63 0
Default
Notes Only prompted if Does the neighbour have a carrier with an interfering frequency? = 1 (yes).
Enter the power budget surrounding cell hreqave: Enable adjacent channel interference avoidance test?: Enter rxlev difference for adjacent channel interference avoidance test:
1 to 31 0 (No) 1 (Yes) 63 to 63
8 0 (No) 0 NA if microcell is not purchased NA if microcell is not purchased This prompt only applies if the previous answer was 1 N/A if microcell is not purchased This prompt only appears if pbgt_alg_type = 7. N/A if multilayer handovers is not purchased and pbgt_alg_type 3
Enter the power budget algorithm 1 to 7 type: Enter the adjacent channel 63 to 63 interference detection handover margin: Enter the uplink receive level 0 to 255 threshold of the serving cell:
1 ho_margin_cell
Enter the downlink receive level threshold of the serving cell: Enter the qualifying time threshold: Enter the qualifying delay time:
0 to 255
None A value MUST be entered at this prompt. None
0 to 255
0 to 255
Enter the neighbour cell receive level threshold:
0 to 63
Enter the delay time:
0 to 255
Enter the handover static offset:
0 to 127
Enter the handover dynamic offset:
0 to 127
N/A if multilayer handovers is not purchased and pbgt_alg_type 3 0 SACCH N/A if multilayer handovers periods is not purchased and pbgt_alg_type 4 0 SACCH N/A if multilayer handovers periods is not purchased and pbgt_alg_type 5 None N/A if multilayer handovers is not purchased and A value MUST be entered at this pbgt_alg_type 5 prompt. 0 SACCH N/A if multilayer handovers periods is not purchased and pbgt_alg_type 6 0 N/A if multilayer handovers is not purchased and pbgt_alg_type 6 0 N/A if multilayer handovers is not purchased and pbgt_alg_type 6
486
EMOTOROLA LTD. 2004
Version 1 Rev 0
Database Parameters
Prompt Enter neighbour congestion handover margin:
Range 63 to 63 To disable congestion handovers to this neighbour, set the value to 63
Default ho_margin_cell of neighbour cell
Is directed retry allowed at this external neighbour cell?:
1 = Yes 0 = No
Enter the Range of the neighbour normal cell: extended
Normal
Notes Value should be less than or equal to the ho_margin_cell of the neighbour cell. This prompt is only presented if directed retry or congestion relief is purchased. N/A when adding internal neighbours This prompt is only presented if directed retry or congestion relief is purchased. This prompt is only presented if the Extended Range Cells feature is unrestricted. N/A if source cell is at a Horizonoffice BTS
add_neighbour In order that the correct integer values are added in the add_neighbor command prompts, the following is useful: In the prompts for timers in algorithms 4, 5 and 6. Then 0 to 255 equates to: 0 SACCH multiframes= 0 secs 1 SACCH multiframes= 480 msecs 2 SACCH multiframes= 960 msecs
255 SACCH multiframes= 122.4 secs In prompts for thresholds in algorithms 3 and 5. Then 0 to 63 equates to: 0= 110 db 1= 109 db 2= 108 db
63= 47 db In prompts for offsets in algorithms 6. Then 0 to 127 equates to: 0= 0 db 1= 1 db 2= 2 db
127= 127 db
Chapter 5
Capacity Enhancing Database
EMOTOROLA LTD. 2004
51
Version 1 Rev 0
52
EMOTOROLA LTD. 2004
Version 1 Rev 0

Objectives
On completion of this chapter the student will be able to: S S S S S S Discuss the use and implementation of directed retry and congestion relief Discuss the use and implementation of multiband Discuss the use and implementation of concentric cells Discuss the use and implementation of coincident multiband Discuss the use and implementation of single BCCH for dual band cells Discuss the use and implementation of extended range cells
EMOTOROLA LTD. 2004
51
Directed Retry
Version 1 Rev 0
Directed Retry
The GSM implementation of standard directed retry allows the simultaneous handling of call setup assignment and handover procedures, by allowing a handover from an SDCCH to a TFC. Essentially this feature allows a MS to be handed from an SDCCH in one cell that has no TFC channel capacity available at call setup (for that MS) to a TFC channel in another cell. This feature will not be activated unless the Assignment Request (for that MS) is queued awaiting resource (i.e. All TFC resources in the cell are utilized). It is possible to enable this feature such that it will only allow movement of an MS to cells internal to the BSS. This implementation has no impact on the Ainterface signalling and for this reason can be used with an existing MSC configuration. If this feature is implemented to allow the MS to be handed to an external cell, then it requires the Handover Required message to carry a cause of directed retry. To instruct the mobile to move the Handover Command carrying the channel mode element is sent to the mobile. The channel mode element indicates to the mobile that the target channel supports, either speech, signalling or data. Of course a directed retry handover will not be initiated unless the MS has reported a strong enough neighbour that meets a congestion relief criteria. If directed retry is enabled and the BSS receives an Assignment Request and no TFC channels are available then the Assignment Request is queued regardless of queuing being enabled in add_cell. If a TFC becomes available whilst the neighbours are being processed then the queuing procedure is followed and the directed retry procedure is aborted. If queuing is disabled in the BSS, the BSS will perform an internal queuing procedure, to a maximum of 25 calls. If queuing is enabled normal queuing shall be performed. If the BSS is using internal queuing, it will not send a Queuing Indication message. If all attempts at directed retry fail or no valid neighbours are reported then the TFC request will remain queued for the remainder of the relevant queuing timer.
Congestion relief
This feature consists of two congestion relief procedures (they are mutually exclusive) that can be enabled independently or in conjunction with Directed Retry. If the MS requiring a TFC channel has not had the opportunity to report a neighbour that is good enough to hand to, then the BSS may force another MS to handover from the congested cell to free up a TFC channel. Of course this MS that is in an established call is only forced to handover if it has a neighbour that meets the congestion handover criteria. If no calls meet the congestion handover criteria, no handovers shall be initiated. The following options are available: 1. 2. The maximum number of handovers initiated by this method is the number of queued requests in the congested cell. The maximum number of handovers initiated by this method is the number of calls meeting the congestion handover criteria in the congested cell.
52
EMOTOROLA LTD. 2004
Version 1 Rev 0
Directed Retry
Directed Retry
Serving Cell
Neighbour Cell
MS is on SDCCH, but wants TCH non available MS queued regardless of whether queuing enabled or not If there is a qualified neighbour, MS hands over chg_element dr_preference <*> <bsc or 0> 0 = DR disabled 1 = DR enabled
SYS12_Ch05_01
EMOTOROLA LTD. 2004
53
Congestion Handover Criteria
Version 1 Rev 0

The handover criteria is specified on a per cell basis. A handover margin is prompted in add_neigbor, this is called the congest_ho_margin. If the latest rxlev_dl average of any of the neighbours (for any MSs established in a call on the congested cell) meet criteria 1 then they are further processed through a modified criteria 2: pbgt congest_ho_margin > 0 If any neighbours qualify using directed retry they can be used to handover the call to the best neighbour. To make it easier to handover to this neighbour in the case of congestion, this parameter value should be less that the value of the handover margin(s) for handovers for radio reasons. To disable congestion handovers to this neighbour, set the congestion handover margin to the maximum value +63. In addition as the congest_ho_margin is usually set to negative values or 0 to facilitate DR handovers to neighbours with free resources. A positive congest_ho_margin would mean that the chances of finding a suitable neighbour would be minimal and the congestion situation on the serving cell couldnt be resolved effectively. congest_ho_margin is a per neighbour parameter. Valid Range: 63dB to 63dB Default Value: None
54
EMOTOROLA LTD. 2004
Version 1 Rev 0
N1 N2 Server N3 N4 N5
N6
S S S
All neighbours assessed to see if they meet criteria 1 Then ordered by pbgt congest_ho_margin > 0
congest_ho_margin 63 to +63
SYS12_Ch05_03
Default None
EMOTOROLA LTD. 2004
55
Enabling Directed Retry
Version 1 Rev 0

dr_preference
This is a chg_element command and is entered at the BSC, it is used to enable the feature and to determine if the MSC is to be involved in the procedure as necessary. By entering this command it determines if handovers can be forced to either internal neighbours or internal and external neighbours.
dr_standard_congest
This is a chg_element command that can only be entered on a per cell basis if the dr_preference is enabled at the BSC. This element enables or disables the standard directed retry feature on a per cell basis. If this is command is enabled within the BSS then the timer that that awaits an Assignment Complete message may require modification (i.e. increasing) in the MSC
dr_ho_during_assign
The BSS has the ability to enable and disable handovers triggered during an assignment procedure. These handovers would be from SDCCH to TFC in target cell. This feature does not effect the existing SDCCH to SDCCH handovers enabled in add_cell. If an intracell handover is needed during an assignment procedure and the assignment request is queued, the BSS will perform the intracell handover. If an intercell handover is needed during the assignment procedure and the Assignment Command has not been sent to the MS, an intercell handover is initiated. No Handover Performed message shall be sent to the MSC as the Assignment Complete from the new cell contains all the necessary information. If the Assignment Command has been sent to the MS, the BSS shall wait for either the Assignment Complete or Failure message from the MS before initiating the handover.
Emergency and EGSM calls

If the emergency call preemption feature is enabled, emergency calls will not be handed over for congestion reasons unless all the calls in the cell are emergency calls. In the case of all emergency calls in a cell, preemption cannot occur so a handover shall be attempted to service the incoming emergency call. An MS on an EGSM channel shall not be handover from an EGSM frequency due to congestion unless an EGSM capable MS is queued.
Microcellular purchasable option

When directed retry and or congestion relief are allowed, if a neighbour qualifies for a congestion handover prior to satisfying the microcellular algorithm selected for that cell, a handover will be attempted (cause directed retry). A way of avoiding this would be to give the microcell neighbours a high congest_ho_margin.
TCH flow control

It is advisable, if the maximum benefit of directed retry or congestion relief is to be had the tch_flow_control should be disabled.
Version 1 Rev 0
chg_element dr_preference <*> <bsc or 0> 0 = DR Disabled (def) 1 = DR Enabled
BSC
Entered at BSC
Chg_element dr_standard_congest <*><site id><cell id> 0 = Disabled ( 1 = DR enable
BTS
BTS
BTS
Entered per Cell
Handover during assignment for radio reasons chg_element dr_ho_during_assign <*><site id> cell_number = <cell id> 0 = Ignore the need for handover 1 = Handover on queue
SYS12_Ch05_04
EMOTOROLA LTD. 2004
57
Directed Retry and External Handovers
Version 1 Rev 0

msc_preference (Default 0)
This element is used to set the message flow sequence used on the Ainterface for external handovers during the assignment procedure. This element must align with the MSC expectations. The MSC implementation may depend on whether queuing is enabled in the cell. The cause value sent to the MSC can be set according to whether directed retry is supported by the MSC. This parameter requires the directed retry or multiband operation to be enabled.
chg_element dr_chan_mode_modify <value> 0 or bsc (Default 0)

This element is entered at the BSC and determines the need for a channel mode modify procedure after a successful handover in which the channel mode changed ( GSM 04:08 sect 7.3.7 ). The BSS shall read this database parameter only in the case of a successful handover in which the channel mode changed, the MS is phase 1, and the new channel mode is full rate speech. Typically changing the channel mode during a handover occurs only during a directed retry handover that has successfully completed to this BSS during directed retry procedure. This is required as some MSs cannot interpret the channel_mode element of the handover_command. Valid Range 0 = disabled, 1 = Enabled
chg_element handover_required_curr_ch <value> 0 or bsc(Default 0)

This parameter must align with the settings of the MSC regarding the contents of the Handover Required message from the BSS. This parameter is set on a per BSS basis, it determines if the current channel information element is included in the Handover Required message. This element is found in GSM08:08. The target BSS on receipt of a Handover Required message composes the requested channel type with the current_channel_element and if they are different it will include the channel_mode_element in the handover_command. This is done so that the MSs can determine whether that are moving to a speech, data or signalling channel. Valid Range 0 = Not included, 1 = Included modify_neighbor <source cell><neighbor cell> dr_allowed 1 Allows a directed retry to an external neighbour during the assignment procedure. An external handover may only be initiated if either the dr_standard_congest or dr_ho_during_assign parameter is enabled. This attribute is only valid for SACCH neighbours.
58
EMOTOROLA LTD. 2004
Version 1 Rev 0
chg_element msc_preference <*> <site id> cell_number = <cell id> MSC

0 = Directed Retry is supported in the BSS but not across the AInterface 1 = Directed Retry is supported within the BSS. The only A interface impact is the Assignment Complete message, which contains the optional Cell ID if the Cell ID changes during the assignment. 2 = The BSS sends the Handover Required message with the cause directed retry to the MSC. 3 = The BSS sends the Handover Required message with the cause of the handover to the MSC (for example, BetterCell). 4 = The BSS sends an Assignment Failure message with the cause directed retry and then sends a Handover Required message with cause directed retry to the MSC. 5 = The BSS sends an Assignment Failure message with the cause directed retry and then sends a Handover Required message with the cause of the handover to theMSC (for example, Better Cell). 6 = The BSS sends a Handover Required message with cause directed retry and then sends an Assignment Failure message with cause directed retry to the MSC. 7 = The BSS sends a Handover Required message with the cause of the handover (for example, Better Cell) and then sends an Assignment Failure message with cause directed retry to the MSC.
SYS12_Ch05_05
Assignment Complete
BSS
BSS
EMOTOROLA LTD. 2004
59
Congestion relief
Version 1 Rev 0
Congestion relief
Congestion relief is an optional feature which is available as an alternative to Directed retry for the case of a congested cell. This feature differs in that it chooses the best candidate from all existing calls in the cell to be moved to the alternate cell thus freeing TCHs in the congested cell. This can result in better overall system quality compared to Directed retry because the best handover candidate is chosen instead of the candidate requesting a TCH. It consists of two congestion relief procedures (they are mutually exclusive) that can be enabled independently or in conjunction with Directed Retry. If the MS requiring a TFC channel has not had the opportunity to report a neighbour that is good enough to hand to, then the BSS may force another MS to handover from the congested cell to free up a TFC channel. Of course this MS that is in an established call is only forced to handover if it has a neighbour that meets the congestion handover criteria. If no calls meet the congestion handover criteria, no handovers shall be initiated. The following options are available: 1. 2. The maximum number of handovers initiated by this method is the number of queued requests in the congested cell. The maximum number of handovers initiated by this method is the number of calls meeting the congestion handover criteria in the congested cell.
510
EMOTOROLA LTD. 2004
Version 1 Rev 0
Congestion relief
Congestion Relief
Type 1
Serving Cell
Neighbour Cell
MS is on SDCCH, but wants TCH non available MS queued regardless of whether queuing enabled or not Another MS that is best qualified, hands over chg_element ho_exist_congest 1 <site> cell_number = <cell id>
Type 2
Serving Cell
Neighbour Cell
MS is on SDCCH, but wants TCH non available MS queued regardless of whether queuing enabled or not All the MSs that qualify, handover chg_element ho_exist_congest 2 <site> cell_number = <cell id>
SYS12_Ch05_06
EMOTOROLA LTD. 2004
511
Congestion Relief Standard Parameters
Version 1 Rev 0

The main O&M impacts of this feature are to the BSS database with several BSS, Cell and Neighbour parameters, some of which are shared with the Directed Retry feature.
Database Parameters
ho_exist_congest This parameter determines if attempts to handover existing calls on a TCH will be initiated in the case of an MS needing a TCH when there are none available in that cell. This parameter indicates either to attempt to handover as many calls as the number of queued assignment requests (if set to 1) or attempt to handover as many calls as meet the congestion handover criteria (if set to 2). It concerns a cell. Valid Range: 0,1 or 2 Default Value: 0 If set to 0, the functionality is disabled. congest_ho_margin This parameter is used in the case of a congestion handover. To make it easier to handover to this neighbour in the case of congestion in the current cell, this parameter value should be less that the value of the handover margin(s). To disable congestion handovers to this neighbour, set the congestion handover margin to the maximum value. Valid Range: 63dB to 63dB Default Value: None tch_congest_prevent_thres This per cell parameter specifies the level of overall TCH utilisation by any MS in a given Cell, at which the Congestion Relief procedure is initiated. The parameter is expressed as a percentage. Valid Range: 1 to 101 Default Value: 100 If set to 100 it means congestion relief will be triggered when attempting to use the last resource. If set to 101 it means congestion relief can only will be triggered when there is no resources left. mb_tch_congest_thres Used to control the percentage point at which Multiband Mobile Stations will start to be redirected to the preferred band. The BSS does not allow an incoming band preference handover should the servicing of that handover cause this percentage to be exceeded. Valid Range: 1 to 101 Default Value: 100
Timers
valid_candidate_ period The BTS (RRSM) timer valid_candidate_period specifies the duration for which candidate channels for handover due to congestion are kept, before querying again for new ones. Valid Range: 0 to 1000000 Default Value: 4000 milliseconds
Version 1 Rev 0
Mobile attempts to set up call in cell
Serving Cell
congest_ho_margin = 5
Neighbour Cell
Pbgt(n) = 2
ho_exist_congest = 1 tch_congest_prevent_thres = 90 Neighbour cell must pass criteria 1 to be used as target pbgt(n) congest_ho_margin > 0 valid_candidate_period = 4000
SYS12_Ch05_07
EMOTOROLA LTD. 2004
513
Congestion Relief Type 2 Parameters
Version 1 Rev 0

Advanced Congestion Relief defines new handover procedures to select active calls to be handed over to relieve congestion in the cell. These new procedures take the form of expanding the decision process for handover to include the state of congestion at the target cell and incorporate the added dimension of time over which the decision is to be implemented. For example, target cells will not accept a congestion relief handover that puts itself into a congested state, resulting in further congestion procedures being invoked. Excessive handovers are therefore eliminated. A source cell will not attempt a congestion relief handover, for a period of time, to a target cell that had rejected a previous handover attempt. The time period may be specified by the operator or as a default, may be set to the time between the onset and completion of a congestion relief procedure. This protects the system from experiencing excessive handover attempts, as well as resulting in a reduction in signalling. congest_at_source Used to control how a given cell behaves should it be unable to force a given imperative handover Valid Range: 0,1 Default Value: 1 If set to 0: The system takes no actions if a given candidate rejects a handover. If set to 1: if a congestion relief handover is needed, the source Cell retries candidates which were previously unable to serve the handover request. congest_at_target Used to control how a given cell behaves should it reject a handover request (either an imperative or congestion relief attempt). Valid Range: 0,1 Default Value: 1 If set to 0: The system will take no action if the Cell reject a handover request. If set to 1: The system will invoke Congestion Relief procedures if this cell rejects a handover request. If a BSS target cell accepts an incoming handover due to congestion relief and this handover itself triggers the target cell congestion relief procedures, that target cell does not trigger any handover attempts back to the source cell which triggered the congestion relief to begin with.
enhanced_relief
This database parameter was introduced at GSR5 and when enabled removes rejection of non imperative handovers when congest_at_target is set to 1. Valid Range: 0,1Default: 0 ext_rtry_cand_prd timer Used to control the time between successive attempts to handover to a particular interBSS target cell which had previously rejected a handover attempt (either an imperative or congestion relief attempt). Valid Range: 0 to 1000000 Default Value: 4000 milliseconds rtry_cand_prd timer Used to control the time between successive attempts to handover to a particular intraBSS target cell which had previously rejected a handover attempt (either an imperative or congestion relief attempt). Valid Range: 0 to 1000000 Default Value: 4000 milliseconds
Version 1 Rev 0
BSC
BSC
Neighbour Cell
Neighbour Cell
Serving Cell
Neighbour Cell
chg_element ho_exist_congest 2 Neighbour selection criteria is the same as Type 1, with the addition of procedures if a handover attempt is rejected If congest_at_target =1, then initiate congestion relief procedures in that cell, when it rejects a handover attempt congest_at_source = 1....Retries after rtry_cand_period = 4000 (def) For external neighbours ext_rtry_cand_period = 4000 (def)
SYS12_Ch05_08
EMOTOROLA LTD. 2004
515
Associated Congestion Parameters
Version 1 Rev 0

When performing a handover to a new cell, due to congestion problems in the serving cell, it is possible that the serving cells rxlev could be much better than the target cells rxlev. Thus, after arriving in the target cell, the mobile could immediately hand over back to the original server due to PBGT or rxlev, followed very quickly by another congestion handover and so on. This condition is known as pingpong or bouncing. To cure this problem, an extra handover margin bounce_protect_margin can be added to the ho_margin(n) for a defined period of time bounce_protect_cong_tmr in the target cell after a channel is activated in that cell. This makes it more difficult for the mobile to hand over back to the original cell after a congestion handover. The functionality of the bounce_protect_margin is shared with bounce protect margins applied for rxqual reasons (covered in SYS03).
chg_element bounce_protect_margin <*><cell_desc> <*> = 0 to 127 dB (default = 0)
chg_element bounce_protect_cong_tmr <*><cell_desc> <*> = 0 to 255 (default = 0)
516
EMOTOROLA LTD. 2004
Version 1 Rev 0

10dB added to ho_margin(n) for 20 SACCH
Serving Cell
Neighbour Cell
chg_element bounce_protect_margin 10 <cell_desc>

sys12_ch6_08a
chg_element bounce_protect_cong_tmr 20 <cell_desc>
EMOTOROLA LTD. 2004
517
Concentric Cells
Version 1 Rev 0
Concentric Cells
Concentric Cells is an optional feature which provides cell resource partitioning using the concept of the concentric cell structure (outer and inner zones) to allow for tighter reuse patterns and increased frequency economy. This feature describes the use of a single BCCH using interference estimation or measurement to move traffic between the conventional macrocell underlay (Outer zone) and the super reuse layer (Inner zone). Concentric Cell is an elegant and simple technique in which the size of cells on the super reuse layer (inner zone) is selfgoverned by interference or by the power that the carriers on the inner zone transmit. With this feature the operator may configure nonBCCH carriers within a cell to have a smaller coverage area. The carriers equipped within a cell may be grouped into two zones: S S Zone 0: Also referred to as the outer zone, is reserved for carriers that may broadcast at the maximum transmit level defined for the cell. Zone 1: Also referred to as the inner zone, may be defined with nonBCCH carriers transmitting lower power than the BCCH carrier, or having a tighter reuse pattern that reduces the useful coverage area of the carrier.
The Mobile Station connected to Zone 0 must meet specific criteria before it can be assigned a traffic channel configured on a carrier in Zone 1 and vice versa. There are two different use algorithms, specified by the operator on a per cell basis, to trigger the transitions between the two zones of the cell. S S Power Based Concentric Cells: Inner zone carriers transmit less power than outer ones and the transitions between zones are based on absolute level thresholds. Interference Based Concentric Cells: Inner and outer zone carriers transmit all the same power within and the transitions between zones are based on some interference conditions. These interference conditions are protection margins against potential interfering neighbours.
The use of a single BCCH implies that the carriers placed in the outer zone are available in the whole cell coverage area whereas the inner zone carriers are only available in a restricted area close to the site location. The signalling previous to the call setup is established in the outer zone and whenever it is possible to move to the inner, the call is transferred to the inner carriers. The Concentric Cell feature is basically a capacity enhancement feature. The possibility of implementing tighter reuse patterns in the area close to the antenna site permits to increase the capacity at the same time that quality is guaranteed by the use of interference estimation algorithm
Multiband
From software release GSR 5.0 multiband operation of concentric cells is allowed. For example if DCS1800 is being added to an existing GSM900 network, the existing GSM900 BCCH plan can be used, since there is no need to plan DCS1800 BCCHs when 1800MHz carriers are added. For this feature to be efficient the network should have sufficient number of multibandcapable mobiles and equipment should be collocated and synchronized. (InCell cabinets cannot be mixed with MCell/Horizon cabinets in the same logical area). In the example described above, all mobiles must be at least GSM900 capable to access the system. Since the BCCH carriers are defined in the GSM900 band, single band DCS1800 mobiles will be unable to access the system.
Version 1 Rev 0
Concentric Cells
Concentric Cells
Zone 1 Inner Zone
Non BCCH Transmitting at lower power than BCCH or Having a tighter reuse pattern that reduces the useful coverage area of the carrier
SYS12_Ch01_14
Zone 0 Outer Zone
BCCH Broadcast at max tx level defined for that cell
Other non_BCCH carriers
Multiband Operation of Concentric Cells Supported from GSR 5.0
EMOTOROLA LTD. 2004
519
Power Based Concentric Cells
Version 1 Rev 0

To enable concentric cells and the whether a power, interference or dual band operation is being selected, is set by the database parameter: inner_zone_alg = <*> Where 0 = Disabled 1 = Power based use algorithm 2 = Interference based use algorithms 3 = Dual band in use In the power based intracell handover algorithm carriers in the inner zone are given reduced maximum uplink and downlink transmit levels, which define the coverage area of the inner zone. The decision to move traffic between zones is based on the downlink and uplink receive levels with respect to the serving cell, as well as database parameters, which are prompted when inner_zone_alg = 1. S ms_txpwr_max_inner 5 to 39 dBm Default value: max_tx_ms
Valid Range: PGSM, EGSM and GSM 850 S S S
DCS 1800 and PCS 1900 0 to 30 dBm Default value: max_tx_ms zone_ho_hyst Valid range: 0 to 30 Default = 0 rxlev_dl_zone Valid range: 0 to 63 Default = 63 rxlev_ul_zone Valid range: 0 to 63 Default = 63
Handover to Inner Zone

A handover is initiated when both the uplink and the downlink receive level averages are greater than the sum of the respective uplink or downlink thresholds defined for the inner zone plus the per cell hysteresis for interzone handover plus the difference between the current uplink/downlink transmit power and the maximum uplink/downlink transmit power of the inner zone carrier. Initiate handover into the inner zone if the following is true for the inner zone carrier(s): rxlev_dl > rxlev_dl_zone + zone_ho_hyst + (bs_txpwr bs_txpwr_max_inner) and rxlev_ul > rxlev_ul_zone + zone_ho_hyst + (ms_txpwr ms_txpwr_max_inner) where: rxlev_dl/ul_zone = minimum rxlev in inner zone 110dBm(0) to 47dBm(63) bs/ms_txpwr = current tx power in outer zone (max_tx_bts and max_tx_ms). Nonbcch carriers can use adaptive pwr control.
bs_txpwr_max_inner = trx maximum power capability trx_pwr_red (Set in RTF equipage) This is the reduced power downlink due to being an inner cell. Each carrier can have a different trx_pwr_red value, giving multiple subzones inide zone 1.
Version 1 Rev 0
Power Based Concentric Cells Handover to Inner Zone
inner_zone_alg = 1
rxlev_dl_zone = 33 (77 dBm) rxlev_ul_zone = 36 (74 dBm) zone_ho_hyst = 3 dB trx_pwr__red = 3 (6dB) ms_txpwr_max_inner = 31 dBm bs_txpwr_max_inner = trx max power capability trx_pwr_red Zone 0 Zone 1 Mobile Power Class = 4 rxlev_dl = 65 dBm rxlev_ul = 63dBm
rxlev_dl 65
> rxlev_dl_zone > 77 +3
+ zone_ho_hyst + (43 (43 6))
+ (bs_txpwr bs_txpwr_max_inner)
65 > 68 rxlev_ul 63 > rxlev_ul_zone > 74 +3 + zone_ho_hyst + (33 31) + (ms_txpwr ms_txpwr_max_inner)
63 > 69
SYS12_Ch05_10
EMOTOROLA LTD. 2004
521
Power Based Concentric Cells HO to Inner Zone Power Level
Version 1 Rev 0

Overview
Using the power based algorithm, the operator may set each carrier in the inner zone to different maximum downlink transmit power levels. Using this configuration, the BSS shall perform handovers between inner zone carriers based on the same algorithms used to perform handovers between zones. By utilizing this functionality, the operator can effectively have multiple subzones within zone 1. However, all carriers defined to be in zone 1 share the same maximum uplink transmit level. All carries defined to be in zone 0 shall have maximum downlink transmit level defined by the BCCH power level and the maximum uplink transmit level as defined per cell in the database.
Handover to Inner Carrier

The HDPC provides the minimum and maximum power level that satisfies the two handover algorithms. Call processing also utilizes these values to select a channel on a carrier that has the lowest maximum transmit level that is within the given range. The maximum power level for a candidate carrier is one power level weaker than the serving carrier and is calculated by incrementing the serving carriers maximum transmit power level: maximum power level = serv_txpwr_max + 1 Where: serv_txpwr_max = trx_pwr_red defined for the serving carrier The minimum power for the candidate carrier is derived from the downlink transmit power criterion as follows: minimum power > rxlev_dl_zone + zone_ho_hyst + bs_txpwr rxlev_dl All parameters in the above equation are converted into dBm before calculation of the minimum power. The minimum power is then converted from dBm to level units. If the computed value falls between two different levels in the conversion table, the stronger power level shall be used Prior to sending the zone handover recognized message, the handover process must verify that the calculation range is valid, and that the cell has at least one carrier within the calculated range. To facilitate this process a list of carriers is provide in descending order by TRX power level reduction value (trx_pwr_red) Therefore last entries will be outer zone carriers. The call does not qualify for an inner carrier handover if the minimum power level turns out to be stronger than the maximum power level or no carriers in the list has a trx_pwr_red value within the minimum and maximum power level range, inclusively. If the call qualifies for both an inner carrier handover and the standard interference handover, the max power level is adjusted to cell max, max_tx_bts This allows CP to assign the call to an outer carrier when there are no resources available for the inner carrier handover and thereby satisfying the standard interference handover requirement.
522
EMOTOROLA LTD. 2004
Version 1 Rev 0
Power Based Concentric Cells Handover to Inner Zone Power Level
serv_txpwr_max = 2 (39 dBm) rxlev_dl_zone = 30 (80 dBm) rxlev_dl = 60 (50 dBm) bs_txpwr = 3 (37 dBm) zone_ho_hyst = 4 dB
39 dBm 37 dBm 13 dBm rxlev_dl = 50 dBm
Zone 1 Zone 0 min power > rxlev_dl_zone + zone_ho_hyst + bs_txpwr rxlev_dl > 80 + 4 + 37 (50) > 11 dBm (level 16 in between levels so . . . ) min power = 15 (13 dBm) max power level = serv_txpwr_max + 1 =2+1 = 3 (37 dBm)
SYS12_Ch05_11
Handovers into inner carriers with maximum power levels of 15 to 3 are allowed
EMOTOROLA LTD. 2004
523
Concentric Cells
Version 1 Rev 0
Concentric Cells
Handover to Outer Zone
A handover is initiated when either the uplink or the downlink receive level average is below the respective uplink or downlink threshold defined for the inner zone and a further increase of the transmit power is not allowed. Initiate handover into the outer zone if the following is true: rxlev_dl < rxlev_dl_zone AND bs_txpwr = bs_txpwr_max_inner OR rxlev_ul < rxlev_ul_zone AND ms_txpwr = ms_txpwr_max_inner
where: rxlev_ul/dl_zone = minimum rxlev in inner zone 110dBm(0) to 47dBm(63) bs_txpwr_max_inner = TRX maximum power trx_pwr_red This is the reduced power downlink due to being an inner cell. ms_txpwr_max_inner = specifies the max power an MS can use in the inner zone of a concentric cell, see W23 bs/ms_txpwr = current tx power in inner zone
524
EMOTOROLA LTD. 2004
Version 1 Rev 0
Concentric Cells
Concentric Cells Handover to Outer Zone
inner_zone_alg = 1
rxlev_dl_zone = 33 (77 dBm) rxlev_ul_zone = 36 (74 dBm) ms_txpwr_max_inner = 31 dBm rxlev_ul = 76 dBm rxlev_dl = 76 dBm
trx_pwr_red = 3 (6dB)
Zone 1 Mobile Power Class = 4
bs_txpwr_max_inner = trx max power capability trx_pwr_red Zone 0
rxlev_dl 76 OR rxlev_ul 76
SYS12_Ch05_12
< rxlev_dl_zone < 77
AND AND
bs_txpwr = bs_txpwr_max_inner 27 = (33 6) X
< rxlev_ul_zone < 74
AND AND
ms_txpwr = ms_txpwr_max_inner 31 = 31
EMOTOROLA LTD. 2004
525
Interference Based Concentric Cells
Version 1 Rev 0

Overview
The interference algorithm is based on the interference estimation in the inner zone. The handover to the inner zone is triggered if no interference is expected from any neighbour, and as soon as interference is expected from any neighbour the call makes handover to the outer zone. The interference estimation is just a modified power budget calculation with all the interfering neighbours. To be free of interference from a particular neighbour, the power budget with the serving cell must be better that the one with the neighbour in a threshold (inner_zone_threshold) and a margin (inner_zone_margin) to prevent pingpong. So, with this new configuration, the thresholds were defined on a per neighbour basis, and depending on the type of interference expected from the neighbour: Cochannel or adjacentchannel interference, and the influence of the cell: front to front, back to front or front to back interference. The database parameter that indicates that the neighbour uses an interfering frequency (i.e. may be adjacent or cochannel) is: interfering_nbr (set in add_neighbor) Range: 0 to 1 0 = no 1 = yes
526
EMOTOROLA LTD. 2004
Version 1 Rev 0
Thresholds set per neighbour
Neighbour 2
Neighbour 1
Neighbour 3
Serving Cell Power budget calculated for all neighbours To be free of interference from a particular neighbour: pbgt(s) must be better than pbgt (n)s + threshold + margin Handover to the inner zone if no interference from any neighbour As soon as interference expected handover to the outer zone
SYS12_Ch05_13
EMOTOROLA LTD. 2004
527
Version 1 Rev 0

Power Budget Calculation
For concentric cell inter zone handovers, the usual power budget formula is modified to remove consideration of the mobiles transmit power capacity, as follows: Pbgt (n) = (ms_txpwr_max rxlev_dl pwr_c_d) (ms_txpwr_max (n) rxlev_ncell (n))
where: pwr_c_d = maximum downlink Tx power in outer zone actual downlink Tx power ms_txpwr_max = maximum mobile transmit power defined per cell An assumption is made at this stage that the difference between the serving cell maximum BS transmit power level and the neighbour cell maximum BS transmit power level is equal to the difference the serving cell maximum MS transmit power level and the neighbour cell maximum MS transmit power level. (i.e. ms_txpwr_max ms_txpwr_max(n) = bs_txpwr_max bs_txpwr_max(n)). This is because bs_ txpwr_max(n) is not presently available in the database and the MS power levels are used in the equation instead of the BS power levels.
Mobile Power Factor

Since the focus of this algorithm is to prevent the MS from getting into a position where it can experience or cause interference, an additional factor is calculated to account for the mobile reporting poor quality and the decision_alg_num database parameter being set to 1, to allow a power increase due to quality even when the rxlev is above its upper threshold. This factor is defined here and used in the equations below: ms_pwr_factor = rxlev_ul + (ordered_power_level used_power_level) l_rxlev_ul_p This calculation incorporates pending power control changes and, to be conservative, is based on the lower end of the power box and should deter the MS from being served by the inner zone.
528
EMOTOROLA LTD. 2004
Version 1 Rev 0
Neighbour 1
Neighbour 2
ms_txpwr_max = 33
ms_txpwr_max = 33
rxlev(n1) = 90 rxlev(n2) = 80
rxlev (s) = 70
max_tx_ms = 33 pwr_c_d = 0
Pbgt(n) = (ms_txpwr_max rxlev_dl pwr_c_d) (ms_txpwr_max(n) rxlev_ncell(n)) Pbgt(n1) = (33 (70) 0) (33 (90)) = 20dB Pbgt(n2) = (33 (70) 0) (33 (80)) = 10dB
decision_alg_type =1
Neighbour 1 Neighbour 2
rxlev (n2) = 75 rxlev (n2) = 65 used_power_level = 27dBm ordered_power_level = 29dBm rxlev (s) = 70
63
47dBm
0 1 2
0.14 0.28 0.57 1.13 2.26 400 4.53 9.05 18.1
rxlev_ul = 70dBm
35
3 4 5 6
74dBm (l_rxlev_ul_p)
110dBm
sys12_ch06_p29
ms_pwr_factor = rxlev_ul+(ordered_power_level used_power_level) l_rxlev_ul_p 70 + (29 27) (74) = 6dB
EMOTOROLA LTD. 2004
529
Interference Based Algorithm Handover to Inner Zone
Version 1 Rev 0

In deciding whether a call is suitable to be served by an inner zone channel, the BSS (HDPC) must satisfy itself that both of the conditions below are true. However, it should be noted that they must be true in relation to all neighbours that contain a co or adjacentchannel interfering carrier frequency. Uplink Criteria: (Checks if the mobile is going to interfere with neighbour cells) pbgt(n) +ms_pwr_factor + inner_zone_threshold(n) +inner_zone_margin(n) 0 and Downlink Criteria: (Checks if the neighbours are going to interfere with the mobile) rxlev_dl + pwr_c_d (rxlev_ncell(n) + inner_zone_threshold(n) + inner_zone_margin(n)) 0
Where: inner_zone_threshold(n) Range 0 to 63 and inner_zone_margin(n) Range 0 to 63 and are per neighbour database defined values.
530
EMOTOROLA LTD. 2004
Version 1 Rev 0
interfering_nbr = 1
interfering_nbr = 1
rxlev (n2) = 90 pbgt (n2) = 20
rxlev (n1) = 80 pbg (n1) = 10
ms_pwr_factor = 0 inner_zone_threshold(n1) = 15dB inner_zone_threshold(n2) = 15dB inner_zone_margin(n1&2) = 3dB pwr_c_d = 43 43 = 0 rxlev (s) = 70
Uplink Pbgt(n) + ms_pwr_factor + inner_zone_threshold(n) + inner_zone_margin(n) 0 Neighbour 1 10 + 0 + 15 + 3 0 8 0 No Neighbour 2 20 + 0 + 15 + 3 0 2 0 Yes

SYS12_Ch05_14
Downlink Rxlev_dl + pwr_c_d (rxlev_ncell (n) + inner_zone_threshold(n) + inner_zone_margin(n)) 0 Neighbour 1 Neighbour 2 70 + 0 (80 + 15 + 3) 0 8 0 No 70 + 0 (90 +15 +3) 0 2 0 Yes
EMOTOROLA LTD. 2004
531
Direct Inner Zone Threshold and Neighbour Report Timer
Version 1 Rev 0

The handover process uses two database parameters (direct_inner_zone_threshold and neighbor_report_timer) to determine the minimum number of measurement reports that must be received from the MS on the current channel prior to moving the MS to the inner zone. If the call is on an SDCCH, the handover process shall accelerate the process in an effort to reduce the number of channel changes for the MS. Using this method, the call may be assigned directly to a TCH in the inner zone rather than moving first to an outer zone TCH the then to another TCH in the inner zone. This method allows the handover process to initiate the inner zone handover as soon as a downlink rxlev average has been calculated if the calculated average is greater than the direct_inner_zone_threshold . If the MS is on an SDCCH on a nonBCCH carrier, power control shall be considered in the calculation as shown below:
dl_rxlev + ((current_dl_power_level max_tx_bts ) * 2) > direct_inner_zone_threshold Note: The value 2 is used in the algorithm to convert absolute values into dBm.
If the above statement is TRUE, the MS qualifies for an inner zone resource. This method is based on the assumption that if the serving cell receive level is strong enough, neighbor cells will not cause harmful interference. For all other cases, the use of the neighbor_report_timer is required. Since this algorithm is based on neighbour information reported by the MS, the MS must be allowed enough time to report on interfering neighbours before moving the MS to the inner zone. This delay is defined in SACCH periods by the database element neighbor_report_timer. The handover process counts the number of measurement reports received on a channel in the qualify_count element. Prior to receipt of the specified number of measurement reports (i.e., qualify_count < neighbor_report_timer), a handover to the inner zone can only be initiated if for ALL of the defined interfering neighbours the handover process has received hreqave measurements and the handover criteria is met. Once the delay has been met (i.e., qualify_count >= neighbor_report_timer), the handover process shall assume that any neighbours which have not been reported by the MS are not strong enough to prohibit handover into the inner zone. As long as all reported interfering neighbours meet the specified criteria, the handover into the inner zone shall be initiated. When computing averages to determine if the call meets the inner zone use criteria, the handover process shall compute an average using all received measurements (min of 2) for a given neighbour if less than hreqave measurements have been received. direct_inner_zone_threshold Valid Range 0 to 63 Default = 63 neighbor_report_timer Valid Range 0 to 255 SACCH Periods Default = 10
532
EMOTOROLA LTD. 2004
Version 1 Rev 0
max_tx_bts = 43 dBm Mobile on SDCCH and has received its second dl_rxlev from the serving cell dl_rxlev = 70 Current dl power level = 33 dBm direct_inner_zone_threshold = 45 (65dBm) dl_rxlev + ((current_dl_power_level max_tx_bts)*2) > direct_inner_zone_threshold 70 + ((5 0)*2) > 65 60 > 65
SYS12_Ch05_15
For all other cases: Before moving mobile to the inner zone, interfering neighbours must have time to report their level neighbor_report_timer = 10 (sacch) qualify_count < neighbor_report_timer Ho can only take place if all interfering n/bours reported hreqave measurements and HO criteria met qualify_count neighbor_report_timer Any interfering n/bours not reported exclude
EMOTOROLA LTD. 2004
533
Interference Based Algorithm Handover to Outer Zone
Version 1 Rev 0

The handover process shall initiate a handover out of the inner zone if the following algorithm is true for any interfering neighbour: Uplink Criteria: (Is mobile interfering with the neighbour?) pbgt(n) + ms_pwr_factor + inner_zone_threshold(n) > 0 OR Downlink Criteria: (Is the neighbour interfering with the mobile?) rxlev_dl + pwr_c_d rxlev_ncell(n) inner_zone_threshold(n) < 0
534
EMOTOROLA LTD. 2004
Version 1 Rev 0
interfering_nbr = 1
interfering_nbr = 1
rxlev(n2)= 60 pbgt(n2) = 8
rxlev(n1) = 55 pbgt(n1) = 10
inner_zone_threshold(n1) = 15dB inner_zone_threshold(n2) = 15dB rxlev(s)= 65
ms_pwr_factor = 3 (in both cases) pwr_c_d = 43 33 = 10
Uplink
pbgt(n) + ms_pwr_factor + inner_zone_threshold(n) > 0 Neighbour 1 Neighbour 2
SYS12_Ch05_16
Downlink
rxlev_dl + pwr_c_d rxlev_ncell(n) inner_zone_threshold(n) < 0 65 + 10 (55) 15 < 0 Neighbour 1 15 < 0 Yes Neighbour 2 65 + 10 (60) 15 < 0 10 < 0 Yes
10 + 3 + 15 > 0 8 > 0 Yes 8 + 3 + 15 > 0 10 > 0 Yes
EMOTOROLA LTD. 2004
535
Power Control When Using Interference Algorithm
Version 1 Rev 0

If the call is active on a channel in the inner zone, the BSS performs an additional check prior to ordering a power decrement. When the BSS power control algorithm determines that the downlink power should be decremented, a check will be performed to verify that the power decrement will not cause the MS to subsequently require a handover to the outer zone. The power control decrement is only allowed if the following is TRUE for ALL neighbours that have been identified as interferers: rxlev_dl power decrement rxlev_ncell(n) > inner_zone_threshold(n) If the call is active on a channel in the inner zone, and the BTS is not transmitting at the maximum power level the following equation is evaluated for ALL neighbours which have been identified as interferers: rxlev_dl + power increment rxlev_ncell(n) > inner_zone_threshold(n) If a power increment is necessary to satisfy the above equation for ALL interfering neighbours, the power level increment is ordered. The BSS selects the minimum power increment that satisfies the above equation for ALL interfering neighbours. The power increment can only be ordered if the ordered power level remains below the maximum transmit level.
536
EMOTOROLA LTD. 2004
Version 1 Rev 0
interfering_nbr = 1
interfering_nbr = 1
rxlev(n2) = 60
rxlev(n1) = 70
rxlev(s) = 60 inner_zone_threshold(n1) = 15dB inner_zone_threshold(n) = 15dB Power Control Decrement rxlev_dl power decrement rxlev_ncell(n) > inner_zone_threshold(n) Neighbour 1 Neighbour 2 60 2 (70) > 15 8 > 15 No 60 2 (60) > 15 2 > 15 No
SYS12_Ch05_17
1st Example 2 dB power decrement ordered
2nd Example 6 dB power increment ordered
Power Control Increment rxlev_dl + power decrement rxlev_ncell > inner_zone_threshold(n) Neighbour 1 60 + 6 (70) > 16 > 1 60 + 6 (60) > 6>1
Neighbour 2
EMOTOROLA LTD. 2004
537
Concentric Cells Channel Allocation Rules
Version 1 Rev 0

outer_zone usage_level
A database threshold, outer_zone_usage_level, has been introduced which allows the operator to specify the level of traffic channel congestion which must be reached in the outer zone prior to the use of the inner zone resources. Since inner zone frequencies may have a tighter reuse pattern, this allows the operator to only use those frequencies more prone to interference if the cell is congested. If the operator chooses to use inner zone resources whenever a MS is qualified, regardless of outer usage, the database parameter outer_zone_usage_level can be set to 0. The tch resources in the outer zone must be greater than outer_zone_usage_level for this feature to operate. outer_zone_usage_level Valid Range 0 to 100 (Indicating the percentage of outer zone TCH usage) Default = 0
Flow Control
The traffic channel flow control, congestion relief, and dynamic reconfiguration features, use the traffic channels usage in the outer zone ONLY to determine of the cell is congested. Congestion relief procedures only initiate handovers for calls in the outer zone. To avoid barring of access classes prior to using the inner zone resources, the outer_zone_usage_level should be set to a lower value than both the normal_overload_threshold and the critical_overload_threshold used by the CRM flow control feature.
intra_cell_handover_allowed
The BSS does not consider the intra_cell_handover_allowed flag when initiating interzone handovers. Interzone handovers can be enabled or disabled separately using the database parameters included with the implementation of this feature. If a zone handover attempt into the inner zone fails due to congestion (that is, no inner zone resource available) and the call qualifies for an interference handover, the call will not handover due to interference if the intra_cell_handover_allowed flag is disabled.
Emergency call preemption

The BSS selects a call from the outer zone to be preempted for the emergency call preemption procedure.
Immediate Assignments
The BSS always selects an outer zone channel for an Immediate Assignment, even if a traffic channel is allocated. If there are no resources available in the outer zone, the BSS sends an Immediate Assignment Reject.
538
EMOTOROLA LTD. 2004
Version 1 Rev 0
outer_zone_usage_level 0 to 100%
% TCH Congestion in outer zone before handover to inner zone allowed

S
Flow Control, Congestion Relief, Dynamic Channel Reconfiguration all happen in outer zone only Intra_cell_handover_allowed parameter irrelevant for interzone handovers option_emergency_preempt always preempts an outer zone call All Immediate Assignments in outer zone
EMOTOROLA LTD. 2004
539
Multiband Intercell Handover
Version 1 Rev 0

Multiband intercell handover is an optional feature which allows a single Network Operator with licences in multiple frequency bands (GSM 850, GSM 900, DCS 1800, PCS 1900) to support the use of multiband mobiles. By supporting transparent handovers between bands, Multiband intercell handover allows seamless operation of the mobile in a multiband environment. This feature includes the following: S S S Multiband support at site level. (BTS site with GSM 850, GSM 900, DCS1800 and PCS 1900 in homogeneous cabinets). Multiband Intercell handovers. Unique Traffic Management in a multiband network using Advanced Load Management.
A multiband network can be either single or multilayer. So, for example, GSM 900 macro cells can operate alongside DCS 1800 macro cells. Alternatively DCS 1800 micro cells could, for example, underlay GSM 900 macro cells. All handovers between bands are inter cell and with the introduction of Single BCCH intracell handovers are now supported, also the normal intracell handovers between GSM and EGSM channels. Frequency hopping is still supported as before, that is that a mobile can hop within its own band. Hopping between bands is not supported.
540
EMOTOROLA LTD. 2004
Version 1 Rev 0
GSM 850
Sufficient Multiband Mobiles needed

GSM 900 GSM 900 DCS 1800 GSM 900 DCS 1800 GSM 900 DCS 1800
GSM 900
DCS 1800 GSM 900 DCS 1800
GSM 900 DCS 1800
Inter Cell Supported
EGSM
GSM 900 DCS 1800 GSM 900
GSM 900 DCS 1800
DCS 1800
Intra Cell supported with Single BCCH for dual Band Cells Feature
DCS 1800
PCS 1900
Frequency Hopping supported within Bands
SYS12_Ch05_18
EMOTOROLA LTD. 2004
541
Version 1 Rev 0
Multiband Database Parameters

In order to enable the multiband feature and all its functionality, the parameter mb_preference is used. chg_element mb_preference < * > location <*> 0= multiband handovers disabled 1= multiband handovers enabled Once this is done, the BSS will take notice of the add_cell prompt frequency_type, which sets the frequency band for the cell. frequency_type (add_cell prompt) 1 or PGSM 2 or EGSM 4 or DCS 1800 8 or PCS 1900 16 or GSM 850 After a call is set up on a particular cell of course a handover may become necessary. It is possible to specify, for each cell, the frequency band(s) of the target cell for any handover that is made out of that cell. This is done by the interband_ho_allowed parameter. The system then chooses a particular band from within the interband_ho_allowed selection based on the preference set by subsequent parameters. chg_element interband_ho_allowed < * > <cell_desc> <*> PGSM EGSM DCS 1800 PCS 1900 1 y X X X 2 X y X X 3 y y X X 4 X X y X 5 y X y X 6 X y y X 7 y y y X 8 X X X y 9 y X X y 10 X y X y 11 y y X y
Check W23 for GSM 850 values.
542
EMOTOROLA LTD. 2004
Version 1 Rev 0
GSM 900
DCS 1800
mb_preference 1 <location> frequency_type = 1 interband_ho_allowed 5 <cel_desc>
SYS12_Ch05_19
EMOTOROLA LTD. 2004
543
Version 1 Rev 0

Having set the frequency bands to which a call in the cell can handover (interband_ho_allowed) it is possible to specify a preference for a particular one. For example, if interband_ho_allowed= 1 then a call could handover to a PGSM, EGSM or PCS1900 neighbour cell; it may be useful to try to hand most calls over to the PCS 1900 in a multilayer system. A preference for a particular band is set by the band_preference parameter. It is not, however, certain that all handovers out of this cell will always go to the preferred band, this depending upon another parameter, band_preference_mode. This parameter can cause the BSS to ignore the band_preference setting, or to take it into account when ordering target neighbour cells for inclusion in the handover_recognised message. The band_preference parameter displays the frequency bands that the cell prefers to use for handovers and specifies the destination frequency band for intercell handovers. Valid range 1 (PGSM), 2 (EGSM), 4 (DCS1800), 8 (PCS1900) 16 (GSM850) Default value The frequency type of the cell (as set by frequency_type). The band_preference_mode parameter specifies the method the system uses to program a Multiband MS with the preferred frequency band for a given cell in the BSS. 0. 1. The BSS attempts to hand a Multiband MS over to the strongest neighbour that the MS reported when a handover is required for normal radio resource reasons. The BSS attempts to assign a Multiband MS to the strongest preferred band neighbour that the MS reported at the time of SDCCH to TCH assignment. If the BSS cannot assign a preferred band TCH the BSS will not try to direct this MS to the preferred band for the life of the current call connection. The BSS always hands the MS over to the strongest MSreported neighbour when a handover is required for normal radio resource reasons. The BSS attempts to hand a Multiband MS over to the strongest preferred band neighbour that the MS reported when a handover is required for normal radio resource reasons. The BSS places preferred band neighbours ahead of nonpreferred band neighbours in order to attempt to assign a channel from the preferred band for the MS. This value combines the functions of values 1 and 2. The BSS continually attempts to hand a Multiband MS over to a preferred band TCH immediately after initial assignment. The BSS will not attempt to allocate a TCH in the preferred band for this MS at the time of SDCCHtoTCH assignment. The BSS will enter a mode of continually monitoring for qualified preferredband neighbours reported by the MS in order to hand the MS over. The BSS will stay in this mode until it finds a neighbour TCH in the preferred band for the current serving cell. Handovers for normal radio resource reasons may occur during the monitoring mode, and these handovers will be to the strongest preferred band neighbour reported by the MS. This value combines the functions of values 1, 2, and 4. This value functions identically to value 5, except it is only triggered when the cell is congested.
EMOTOROLA LTD. 2004
2.
3. 4.
5. 6.
544
Version 1 Rev 0
band_preference = 4 MS has received SDCCH and is waiting for TCH band_preference_mode = 1 (Chooses strongest preferred band neighbour if possible, does not attempt to direct to preferred band during duration of call) band_preference_mode = 4 Immediately after initial assignment, BSS constantly monitors for a qualified preferred band neighbour) PGSM Strongest Overall PGSM Serving MS needs to handover for normal radio reasons band_preference_mode = 0 (Handover to strongest neighbour) band_preference_mode = 2 (Handover to strongest preferred band neighbour) band_preference_mode = 3 (Combines 1 and 2) band_preference_mode = 5 (Combines 1, 2 and 4) band_preference_mode = 6 (Combines 1, 2 and 4 but triggered for congestion reasons) PGSM DCS1800 Strongest DCS 1800
PGSM
DCS 1800
sys12_ch06_18
EMOTOROLA LTD. 2004
545
Enhanced SDCCH to TCH (preferred band) Assignment
Version 1 Rev 0

In the case of values 1, 3, 5 and 6, it has been found that the MS does not report on neighbour cells from other frequency bands fast enough to allow the TCH assignment to the preferred band neighbour cell. A feature released in GSR 5.0 makes an allowance for this. The parameter works by specifying the number of measurement reports that the RSS waits before responding to the CRM if the MS does not report a preferred band neighbour. sdcch_tch_band_reassign_delay Valid Range 0 to 4 (SACCH multiframes) Use of this parameter may cause a delay of up to two seconds.
546
EMOTOROLA LTD. 2004
Version 1 Rev 0
The parameter works by specifying the number of measurement reports that the RSS waits before responding to the CRM if the MS has not reported a preferred band neighbour This is needed to allow time for the MS to report neighbour cells from other frequency bands sdcch_tch_band_reassign_delay
Valid Range 0 to 4 (SACCH multiframes) Use of this parameter may cause a delay of up to two seconds
EMOTOROLA LTD. 2004
547
Multiband Neighbour Measurement
Version 1 Rev 0

Multiband mobiles of course produce measurement reports relating to the serving cell and the best six neighbours when in dedicated mode, just as single band mobiles do. However, to ensure an equal chance of selecting each bands target cells, it is possible to reserve some of the six positions for neighbours in a measurement report for each available band. This is done via the multiband_reporting database parameter. multiband_reporting<element_value><location><cell_number> Value type Integer Valid range 0 to 3 0. 1. Normal reporting of the six strongest neighbour cells with known and allowed NCC part of the BSIC, irrespective of the band used. Report the strongest neighbour cell, with known and allowed NCC part of BSIC, in each of the frequency bands in the neighbour cell list, excluding the frequency band of the serving cell. The remaining positions in the measurement report shall be used for reporting Cells in the band of the serving Cell. Any still remaining positions will be used to report the next strongest identified neighbours in other bands irrespective of the band used. Report the two strongest cells, with known and allowed NCC part of BSIC, in each of the frequency bands in the neighbour cell list, excluding the frequency band of the serving cell. The remaining positions in the measurement report shall be used for reporting Cells in the band of the serving Cell. Any still remaining positions will be used to report the next strongest identified neighbours in other bands irrespective of the band used. Report the three strongest cells, with known and allowed NCC part of BSIC, in each of the frequency bands in the neighbour cell list, excluding the frequency band of the serving cell. The remaining positions in the measurement report shall be used for reporting Cells in the band of the serving Cell. Any still remaining positions will be used to report the next strongest identified neighbours in other bands irrespective of the band used.
2.
3.
Default value 0
548
EMOTOROLA LTD. 2004
Version 1 Rev 0
Multiband Neighbour Measurements

Example: multiband_reporting 3 <location> <cell_number>
Neighbour List Three strongest neighbours from bands other than the serving cell n1, n3 and n5
PGSM n2
DCS 1800 n1 PGSM n6
PGSM
Then the next three neighbours from the band of the serving cell n2, n4 and n6
DCS 1800 n3
Serving DCS1800 n5
Any remaining positions taken by neighbours from any band regardless of band used
SYS12_Ch05_21
PGSM n4
EMOTOROLA LTD. 2004
549
MSC Requirements
Version 1 Rev 0
MSC Requirements
The MSC can support BSS equipment from different vendor for each frequency band. This provides the operator the ability to distribute the changes required for Multiband operation To have a working dualband capability in the network, some MSC requirements apply. The MSC needs to have the capability to handle Classmark 3 (CM3) information element. CM3 information is sent by multiband mobile to MSC contains info of multiband capabilities and the MS power classes in the different bands. The CM3 info then is stored in the MSC for the duration of the call. In case the mobile is required to perform a multiband handover, the CM3 info must be transmitted to the target BSS, which informs the new BSS about the multiband capabilities of the mobile. If a handover becomes necessary in a multiband environment, the network must of course know the frequency band capabilities of the mobile so that a PGSM mobile is not handed over to a DCS 1800 cell for example. In internal handovers this discrimination is handled by the BSC as part of its normal handover control function, but in external handovers the target BSC must be told the mobiles capabilites. Moreover, the MSC must know the mobiles capabilities in case this affects its choice of BSC; in a multilayer configuration each layer could be controlled by a different BSC. There are 3 GSMdefined messages for informing the network of the mobiles capabilities Classmark 1 Phase of MS Early classmark sending enabled A5/1 support Power Class Classmark 2 Phase of MS Early classmark sending enabled A5/1/2/3 support Power Class Synchronization Supplementary Services SMS support EGSM support Classmark 3 support Classmark 3 is the important message in multiband, but is normally only sent by the mobile when interrogated by the MSC. In order to save time it is possible to send classmark 3 spontaneously using the parameters opposite. This will happen within 40ms if the initial layer 3 message at call setup unless specified otherwise, and is communicated to the target BSC of an external handover in the handover request message. Classmark 3 PGSM/EGSM/DC S 1800 support A4/5/6/7 support Power class
550
EMOTOROLA LTD. 2004
Version 1 Rev 0
MSC Requirements
Classmark of Mobile
chg_element early_classmark_sending <*>0 <*> 0= disabled 1= enabled on Ainterface, disabled on air interface 2= disabled on Ainterface, enabled on air interface 3= enabled on Ainterface and air interface Def = 0
chg_element early_classmark_delay <*>0 <*> 0 to 100,000 ms
Def = 0
EMOTOROLA LTD. 2004
551
ALM for EGSM Carriers
Version 1 Rev 0

EGSM Layer Management
In a predominantly PGSM and DCS1800 multiband network, there are problems with utilization of the EGSM frequencies. This is because of the interaction with the multiband handover feature. The multiband handover feature uses two database parameters band_preference and band_preference_mode. If for example band_preference was set to DCS1800 and band_preference_mode = 4, meaning on trigger of a normal handover try to direct the call to the preferred band. Then if an EGSM capable MS established on a PGSM cell with EGSM capabilities, if there are idle EGSM TCH capacity the MS will be assigned to the EGSM TCH resource. But when a handover is triggered due to RF reasons (better cell etc) the MS will be targeted to the DCS1800 band, because it is the preferred band. Consequently EGSM resources are under used.The reordering of candidate neighbour cells when a handover is triggered depends on the MS being EGSM capable and the MS having established on a EGSM resource. It does not operate with the coincident multiband feature and cannot support external handovers to EGSM neighbours. It does not operate with EGSM BCCH frequencies or support hopping through EGSM frequencies within PGSM/EGSM cell.
Database parameters
chg_element bss_egsm_alm_allowed <*><location> (BSS only) <*> 0 = EGSM ALM feature disabled 1 = EGSM ALM feature enabled
Neighbour Reordering
If we take the case of band_preference_mode = 4, the RSS process orders the neighbours into two distinct groups before reporting them to the CP process. These groups are preferred band neighbours and nonpreferred band neighbours. If the MS is EGSM capable and it is currently established on an EGSM TCH channel. The nonpreferred band neighbours (in this case PGSM) will be checked to see if they have any EGSM resources. If a neighbour does have EGSM resources, it will be placed at the head of the list as the highest priority neighbour.
552
EMOTOROLA LTD. 2004
Version 1 Rev 0
Preferred band neighbour (DCS1800) Preferred Non Preferred neighbour (PGSM)
Non Preferred
Non Preferred neighbour (PGSM/EGSM)
Candidate neighbours reported from RSS chg_element bss_egsm_alm_allowed 1 <location>
Non Preferred band (PGSM/EGSM)
Preferred band (DCS1800)
Non Preferred band (PGSM)
Candidate neighbours sorted by CP
sys12_05_alm1
EMOTOROLA LTD. 2004
553
ALM for EGSM Carriers Examples
Version 1 Rev 0

Example 1
EGSM Capable MS Establishes on a PGSM Resource In this case the database parameters band_preference and band_preference_mode will direct the call to the preferred band. For instance if an EGSM capable MS establishes on a PGSM TCH resource and a handover is triggered. If band_preference = DCS1800 and band_preference_mode = 4, then when the next handover is triggered the MS will be directed to the DCS1800 layer. Once on the DCS1800 layer the MS will continue to be directed to the DCS1800 layer. If at any time the MS is handed into a PGSM/EGSM cell, if EGSM TCH resources are available, will be granted an EGSM resource.
Example 2
EGSM Capable MS Establishes on a EGSM Resource Before this feature the MS would have been directed to a DCS1800 resource on handover. To make better use of the EGSM resources the candidate neighbour cells are manipulated so that any PGSM neighbour with EGSM capabilities is preferred. If the handover to the PGSM/EGSM cell results in the MS being assigned to a PGSM resource. The BSS will revert to directing the MS to the preferred band in this case DCS1800. If the handover fails to the PGSM/EGSM neighbour due to no resources, then the BSS attempts to target the MS to the next neighbour which may be a PGSM/EGSM, DCS1800 or PGSM cell. Once the MS is directed to the DCS1800 layer, it will continue to be directed to the DCS1800 layer as directed by band_preference and band_preference_mode.
554
EMOTOROLA LTD. 2004
Version 1 Rev 0
ALM for EGSM Carriers Example 1
EGSM capable MS establishes on a PGSM TCH resource
DCS1800
DCS1800
PGSM/EGSM EGSM MS on PGSM TCH If on PGSM resource will be directed by band_preference and band _preference_mode
PGSM/EGSM
band_preference = DCS1800
band_preference_mode = 4
If a handover occurs to a PGSM/EGSM neighbour and there are no EGSM resources
On the next handover the MS will be directed to the DCS1800 layer
EMOTOROLA LTD. 2004
555
Version 1 Rev 0
556
EMOTOROLA LTD. 2004
Version 1 Rev 0
ALM for EGSM Carriers Example 2
EGSM capable MS establishes on a EGSM TCH resource
DCS1800 DCS1800
PGSM/EGSM PGSM/EGSM EGSM MS on EGSM TCH
If on EGSM resource will not be directed by band_preference and band_preference_mode if there are EGSM neighbours If there are no PGSM/EGSM resources the BSS attempts to target the MS to the next neighbour which could be (in order) PGSM/EGSM , DCS1800 or PGSM If a handover occurs to a PGSM/EGSM neighbour and there are no EGSM resources and the MS is assigned to a PGSM resource, then the MS will be directed to DCS1800 layer On the next handover the MS will be directed to the DCS1800 layer and once on the DCS1800 layer will directed to DCS1800 neighbours
Diagran Number
EMOTOROLA LTD. 2004
557
Coincident Multiband Handover
Version 1 Rev 0

This feature enables operators to install new radios in a different frequency band. This installation will turn an operators network into a multiband network. One obstacle to this type of upgrade is the investment in time and money already made by the operator in optimising the existing network. With the addition of a secondary network, with different propagation characteristics, this optimisation effort would have to be repeated. This can deter some operators, who want the extra capacity, from installing a multiband network. To avoid this problem of optimising two networks, it is logical that the new secondary network should complement the existing infrastructure. To achieve this, the software must be configurable enough to allow the new network to use the same cell boundaries established by the original network. This can be done by using mobilereported measurement reports of the primary network while established on the secondary network. This allows the mobile to be handled as if it were on the primary network, using the primarys boundaries and minimizing propagation characteristics differences, whilst not taking any primary network resources. This feature is designed to complement the Multiband feature and the functionality described here is only available if that feature is enabled.
Feature objectives
This feature has two main objectives: S To ensure that the specific DCS 1800 cell will only unload the traffic from its coincident GSM cell and not take traffic away from surrounding GSM cells. This is achieved by defining the DCS cell boundaries by the underlying GSM cell boundaries. To maintain the quality in the GSM network and only have one network to optimise. This is achieved by having the same handover boundaries between the GSM and DCS cells.
Cell Definitions
Coincident Cell
A cell that has a colocated neighbour cell whose cell boundary follows that of the said cell, but has a different frequency type to that of the neighbour cell. The coincident cell has only one GSM1800 neighbour, which is collocated.
Primary Cell
A cell (GSM900), that is already optimised in the network and has a colocated neighbour, whose cell boundary follows that boundary of the said cell. The primary cell has a preferred band equal to the frequency type of the coincident cell (GSM1800). If no coincident GSM1800 cell exists, then no GSM1800 neighbours are defined.
Secondary Cell
A cell, which is not optimised and has a colocated neighbour whose cell boundary follows the boundary of the said cell. The secondary cell has a preferred band the same as that of its own frequency type (GSM1800). The colocated GSM1800 cell has all the same GSM900 neighbours, as does the GSM900 cell, in addition to the colocated GSM900 (coincident) cell itself. In addition to the GSM900 cells, the GSM1800 cell may have other GSM1800 neighbours. This feature will not affect normal multiband handovers to a preferred band.
Version 1 Rev 0
Optional two way neighbour
To increase capacity cell A and C is added to cover the same area as cell B and C
One way neighbour
Two way neighbour
Secondary
Secondary
A Coincident neighbour
Primary
Primary
Primary
These cells are optimised and power budget handovers can occur B & D also C & B are neighbours of each other All belong to the same frequency band
sys12_ch06_22
EMOTOROLA LTD. 2004
559
Configuring Coincident Multiband
Version 1 Rev 0

chg_element coincident_mb <value> <location> cell=<cell_desc> Value (valid range): 0. 1. 2. Coincident Multiband is disabled Coincident Multiband utilises better cell detection Coincident Multiband utilises coincident cell redirection
Prompts for : S GSM cell id of the host cell S coincident_offset 63 to 63 S low_signal_thres 0 to 63 The BSS will use an additional offset to the power budget equation when the neighbour being used for downlink measurements (GSM900) is not reported. If the MS is on a TCH on cell A (DCS1800) and downlink measurements for cell B (GSM900) were not being reported, then the serving cells measurements would be used in the power budget equation with addition of the offset. When a handover condition is present to a neighbour with a coincident preferred band cell, the MS supports multiple frequency bands and the MS reported receive level of the target cell is above the threshold defined by this parameter; the BSS will attempt to hand the MS directly to the coincident preferred band cell. This functionality is only used if coincident_mb is set to 2 and is set in both directions (both cells have to be coincident to each other).
Example
In the case shown opposite, Cell A and Cell B are colocated coincident neighbours of each other. Cell B is part of the GSM900 network, while Cell A has been added and is part of the, secondary, GSM1800 network. Assume that a mobile was using a traffic channel on cell A (DCS1800). The MS would be measuring the strength of Cell B and Cell D (GSM900 because they are defined in the neighbour database). When Cell A receives the measurement report from the MS, in a coincident cell, the BSS uses the measurement level of Cell B as the downlink measurement, instead of using the downlink receive level of Cell A to make a decision as to whether a handover is needed. This is done because the propagation characteristics of the two cells can vary. The BSS uses the signal strength reports of Cell D from the mobile to determine whether there are any viable candidates for the needed handover (PBGT calculations). If Cell B was not decoded as a neighbour then coincident_offset is applied to the pbgt calculation to compensate for the lower propagation characteristics of the DCS1800 Cell. If C (DCS1800) was also a neighbour of A, the downlink receive level of cell A will be used in the serving cell power budget calculations as it is in the same frequency band. Coincident Cell Redirection This is the enhanced functionality of handing over to an unreported neighbour. If the BSS decides that Cell E (GSM900) is a viable candidate for handover for a MS occupying a traffic channel on Cell A (DCS1800), the BSS will detect that Cell F (DCS1800) is a coincident cell of Cell E, and will redirect the handovers to Cell F as long as the rxlev of Cell E is detected as being above low_signal_thres. The value of low_signal _thres is set at a level which takes into account the difference in rxlev between the GSM900 cell and its DCS1800 coincident neighbour. The colocated coincident cells (GSM900 and DCS1800) must be synchronised in order to perform a handover to an unreported neighbour; therefore the cells must be located at the same site. They also have to use the same BSIC to have successful communication upon handover (this requirement only applies if coincident_mb is set to 2). The cells must be synchronised because the Handover Command sent to the MS has the cell E (GSM900) cell description (the cell the MS was reporting on in the measurement reports), but the cell F (DCS1800) channel description. If the cells are not synchronised the handover will fail. The Handover Access burst is encoded using the BSIC of the target cell cell E (GSM900) and thus cell F must have the same value in order to successfully decode the message.
Version 1 Rev 0
Cell DCS1800
Cell DCS1800
Cell DCS1800
Cell PGSM
Cell PGSM
Cell PGSM
coincident_mb =2 for both cells E and F BSIC same for E and F Sync handovers enabled between cells F and E band_preference =4 for cell E PBGT handover to cell F when measured rxlev above low_signal_thres
coincident_mb = 1 for cells A,C,B and D Optionally A and C can be neighbours Or they are not and coincident_offset used to compensate for the lower signal strength of the DCS 1800 cell. This offset is added to the ho_margin
EMOTOROLA LTD. 2004
561
Coincident Multiband External Neighbour Enhancements
Version 1 Rev 0

Prior to GSR6 problems were encountered when an external handover occurred between cells with coincident neighbours with coincident_mb = 2. This was because the criteria for a seamless redirected handover to the secondary DCS1800 cell is based upon the rxlev of the primary GSM900 neighbour cell being above low_signal_thres. In the case of an external neighbour the result of this calculation would never be used as it is made in the source BSC. Hence mobiles were being redirected to the secondary DCS1800 cell incorrectly and causing bad quality in the network. The solution is to offer a new coincident multiband option of 3.
Operation
chg_element value = 3 coincident_mb <value> <location> cell=<cell_desc> Internal cells uses coincident_mb = 2 External cells uses coincident_mb = 1
For the example on the opposite page we have a coincident cells on the border of two BSCs A and B. For these cells we have set coincident_mb = 3. If a handover from a secondary DCS1800 cell occurs internally then the redirected handover can occur in the normal way by coincident_mb = 2 and coincident_offset as the calculation of low_signal_thres can be made within the same BSC and the correct decision can be made whether to redirect or not. However if the handover from a secondary DCS1800 cell is external then it uses coincident_mb = 1 so better cell detection is used based upon coincident_offset. If however the actual cell size was the same for the GSM900 and DCS1800 coincident cells then calculation of low_signal_thres is no longer of consequence and the border cells can be set at coincident_mb = 2.
562
EMOTOROLA LTD. 2004
Version 1 Rev 0
BSC A
BSC B
Cell Cell DCS1800 DCS1800
Cell Cell PGSM
Cell Cell PGSM
Cell Cell PGSM
coincident_mb =3 for cells F and E BSIC same for E and F + Sync handovers For external neighbours uses coincident_mb = 1
coincident_mb = 3 for cells A and B BSIC same for A and B + Sync handovers coincident_mb = 2 for cells C and D BSIC same for C and D + Sync handovers For internal handovers uses same as coincident_mb = 2
SYS03_ch05_coinenh
EMOTOROLA LTD. 2004
563
Version 1 Rev 0

This is a feature developed in GSR 5 software release. GSM specifications allow the use of a common BCCH for different bands of operation when resources across all bands are colocated and synchronised. With this feature it is possible for carriers within a cell to be configured in different frequency bands.
Feature Overview
Restricted Features
The following restricted features need to be enabled Dual Band Cells Concentric Cells Multiband Handovers Homogeneous Cabinet (Cabinets at a site can be of different frequency types) Heterogeneous Cabinet (Cabinets are able to support multiple frequency types and is required for combined cabinet configurations only)
Frequency Hopping
Because Frequency Hopping between different bands in not allowed per GSM specifications, the dual band cells feature only supports frequency hopping that are defined to contain frequencies from a single frequency band. In a dual band cell the hopping systems may contain either primary or secondary band frequencies, but not a combination of both.
564
EMOTOROLA LTD. 2004
Version 1 Rev 0
n Restricted Features
S S S S S
Dual Band Cells Concentric Cells Multiband Handovers Homogenous Cabinet Heterogenous Cabinet
n Frequency Hopping
EMOTOROLA LTD. 2004
565
Version 1 Rev 0

Feature Overview (Continued)
The single BCCH for dual band cells provides the capability to configure and manage cells with carriers from different frequency bands by using the concentric cells configuration. S S S Primary band carriers are configured in the outer zone, to provide total cell coverage To be consistent with the concentric cells feature the BCCH and SDCCHs must be in the primary band, along with any other nonBCCH carriers of the same band Secondary band carriers are configured in the inner zone and these contain the remaining nonBCCH carriers. In effect the inner zone coverage could be the same as the outer zone For this feature to operate efficiently the operator would need a subscriber base populated with a sufficient number of multiband capable mobiles The feature benefits operators by providing a convenient way of expanding system capacity by utilizing frequencies from the secondary band provided a sufficient multiband capable subscriber population exists This strategy enables system capacity to be increased without modifying the frequency plan. Or, the neighbour list
S S
S S
566
EMOTOROLA LTD. 2004
Version 1 Rev 0
System Expansion
Primary Band Outer Zone Contains BCCH carrier, SDCCH and any optional non BCCH carriers
No need to modify Secondary Band Inner Zone frequency plan

Remaining non BCCH carriers
Sufficient number of multiband mobiles D
No need to modify associated neighbour lists
SYS12_Ch05_24
EMOTOROLA LTD. 2004
567
Frequency Types
Version 1 Rev 0
Frequency Types
Two different frequency types at cell level can be configured, these can be a combination of PGSM, EGSM, DCS1800 or GSM850. Any of these bands can be assigned as the primary band for the cell.
Primary Band
The primary band is set using frequency_type, to add or change a frequency type, add cell or change cell element is used.
Secondary band
The secondary band is set using secondary_freq_type database parameter. This is prompted after the inner zone algorithm has been set to 3 to enable the dual band cells feature, or can be modified using the change cell element command.
Dependancies
S S S If the primary cell frequency type is DCS1800 the secondary frequency type can either be PGSM, EGSM or GSM850 If the primary cell frequency type is PGSM or EGSM the secondary frequency type must be DCS1800 or GSM850 Cell and cabinet frequency types must be allowed at the BSS as per the frequency_types_allowed command
568
EMOTOROLA LTD. 2004
Version 1 Rev 0
Frequency Types
Frequency Types
Primary band set by frequency_type Secondary band set by:

secondary_freq_type Range 1 PGSM 2 EGSM 4 DCS1800 16 GSM850
Primary Band PGSM
DCS1800
EGSM
frequency_type = DCS1800 secondary_freq_type = PGSM or EGSM
PGSM
DCS1800 DCS1800 Secondary Band EGSM DCS1800
frequency_type = PGSM or EGSM secondary_freq_type = DCS1800
frequency_types_allowed
SYS12_Ch05_25
EMOTOROLA LTD. 2004
569
Modification Overview
Version 1 Rev 0
inner_zone_alg <value>cell=<cell_desc>
The procedure to establish a dual band cell configuration begins with modifying the inner zone algorithm element for the new dual band cell. This is accomplished by using a value of 3. Once this value is entered the following secondary band parameters are prompted: S S S S S S S S S S Frequency Type of the secondary band BTS maximum transmit power level MS maximum transmit power level Handover power level Handover hysteresis Downlink receive level threshold Uplink receive level threshold Dual band offset Power budget mode These parameters are explained fully later.
Equipping DRI and RTF groups

With dual band cells it is necessary to equip DRI and RTF groups per cell since the frequency type of the RTF must match the radio equipment tied to the DRI. There must be different DRI and RTF groups associated with the primary band and the secondary band of a dual band cell. Secondary band carriers must be equipped as inner zone carriers.
Outer zone usage

At this point the operator must indicate the percentage of outer zone traffic channels that need to be in use prior to the assignment of secondary band channels. This is set by outer_zone_usage_level database parameter.
570
EMOTOROLA LTD. 2004
Version 1 Rev 0
inner_zone_alg <value> cell = <cell_desc>

S
Where value 3 = dual band cell in use Frequency type of the secondary band BTS maximum transmit power level MS maximum transmit power level Handover power level Handover hysteresis Downlink receive level threshold Uplink receive level threshold Dual band offset Power budget mode outer_zone_usage_level
DRIs and RTFs for the secondary band must be equipped
EMOTOROLA LTD. 2004
571
Dual band Inner Zone use Algorithms
Version 1 Rev 0

The dual band inner zone use algorithm differs from the power based use algorithm in a number of ways. Rather than defining the maximum transmit power for the inner zone on a per carrier basis the inner zone use algorithm defines the maximum transmit power as one value applied to all secondary band carriers.
Propagation Differences
In order to account for propagation differences between bands and allow secondary band carriers to provide total cell coverage, the inner zone use algorithm allows the maximum transmit power level of secondary band carriers to exceed the maximum transmit power level of the primary band.
Power losses
Unlike the power based algorithm which uses the power level at the radio as a reference point and assumes a consistent degradation of the signal for all carriers in the cell from that point on , the inner zone use algorithm must consider other factors when comparing signal strengths from different frequency bands to accurately determine whether a mobile can be served by a secondary band channel. These factors are: S Due to different level of combining the loss of power between the radio unit and the top of the antenna may not be consistent across all radio units within the cell. The power difference is calculated by subtracting the secondary band power loss from the primary band power loss. Due to the radio frequency propagation being weaker at 1800 MHz than at 900 MHz, propagation loss over the air interface has got to be taken into consideration. These factors are accounted for in the database parameter
S S
dual_band_offset = <*> Range = 63 to 63
572
EMOTOROLA LTD. 2004
Version 1 Rev 0
Max transmit power same for all secondary carriers Max transmit power of secondary can exceed mas trasmit power of primary Radio power level changes Power loss from radio to top of antenna
Power D = primary band power loss secondary band power loss
Primary Band
Max power primary = 37 dBm
Max power secondary = 43 dBm
Loss of power between radio and top of antenna
Secondary Band
RF propagation is weaker at 1800MHz than 900MHz
Propagation loss
dual_band_offset = Power D + Propagation D Range = 63 to 63

SYS12_Ch05_26
EMOTOROLA LTD. 2004
573
Dual Band Inner Zone Algorithms
Version 1 Rev 0

This section concerns the use of dual band inner zone algorithms. S S S Basically inter zone management is provided by the concentric cells feature. It uses the power based use algorithm which manages traffic between zones using algorithms based on uplink and downlink receive levels. Also the operator is able to manually set preferences by using the database element, outer_zone_usage_level. If it is set to 0, channels in the inner zone are used whenever a mobile is qualified to use those resources. If set from 1 to 100 inner zone resources are allocated only when a mobile is qualified and at least the specified percentage of outer zone traffic channels are in use. Traffic between frequency bands of different cells is currently managed by the multiband feature. To achieve a satisfactory algorithm for interzone traffic management, with dual band cells, the concentric cells power based use algorithm is enhanced with multiband features interband traffic management shifted from intercell to intracell level.
574
EMOTOROLA LTD. 2004
Version 1 Rev 0
Dual Band Inner Zone Use Algorithms
Concentric Cells
Primary Band
Uplink and downlink receive levels
Secondary Band
outer_zone_usage_level = 0 to 100
Enhanced multiband feature
SYS12_Ch05_27
EMOTOROLA LTD. 2004
575
Version 1 Rev 0

In comparing the receive levels of the outer zone to the inner zone threshold, the inner zone use algorithm must adjust for values being from two different frequency bands and convert the primary band receive levels to an estimated value for the secondary band. This is done using the dual band offset parameter. RXLEVINNER = RXLEVOUTER + dual_band_offset This offset is applied to both uplink and downlink receive levels
Algorithms
The calculated receive level inner value is then used in the dual band inner zone algorithm for both uplink and downlink RXLEV_DL INNER > rxlev_dl_zone + zone_ho_hyst + (bts_txpwr bts_txpwr_max_inner) RXLEV_UL INNER > rxlev_ul_zone + zone_ho_hyst + (ms_txpwr min(ms_txpwr_max_inner,P) Within this algorithm are database parameters that are set per cell after the inner_zone_alg = 3 (dual band use) rxlev_dl/ul_zone = <*> * = Range 0 to 63
zone_ho_hysteresis = <*> * = Range 63 to 63 bts_txpwr_max_inner = <*> * = Range as defined for max_tx_bts (0 to 21) ms_txpwr_max_inner = <*> * = Range as defined for max_tx_ms (5 to 39 PGSM and EGSM 0 to 36 DCS 1800) P = maximum capability of the mobile in the inner zone frequency band.
576
EMOTOROLA LTD. 2004
Version 1 Rev 0
Dual Band inner Zone Use Algorithms
RXLEVINNER = RXLEVOUTER + dual_band_offset (RXLEV_DLINNER > rxlev_dl_zone + zone_ho_hyst + (bts_txpwr bts_txpwr_max_inner) (RXLEV_ULINNER > rxlev_ul_zone + zone_ho_hyst + (ms_txpwr
min(ms_txpwr_max_inner,P)
rxlev_dl/ul_zone zone_ho_hysteresis bts_txpwr_max_inner ms_txpwr_max_inner
Range 0 to 63 Range 63 to 63 Range as defined for max_tx_bts (0 to 21) Range as defined for max_tx_ms (5 to 39 PGSM and EGSM 0 to 36 DCS1800)
P is the maximum power of MS in inner zone
EMOTOROLA LTD. 2004
577
Version 1 Rev 0

This page deals with the algorithms necessary to handover calls from the secondary band to either the primary band or a qualified neighbour. The algorithms for uplink and downlink depend on whether BTS and mobile power control is switched on or off.
BTS Power Control on

rxlev_dl < rxlev_dl_zone and bts_txpwr = bts_txpwr_max_inner Receive level downlink is less than the receive level threshold and the BTS is at full power
BTS Power Control off

rxlev_dl < rxlev_dl_zone Receive level downlink is less than the receive level threshold
MS Power Control on
rxlev_ul < rxlev_ul_zone and ms_txpwr = min(ms_txpwr_max_inner,P) Receive level uplink is less than the receive level threshold and the mobile is at full power
MS Power Control off

rxlev_ul < rxlev_ul_zone
Handovers to n/bours
The neighbour cells are assessed first to see if they are suitable cells to handover too pbgt(n) > ho_margin If any neighbour qualifies, a handover is initiated otherwise the mobile is moved to the outer zone.
578
EMOTOROLA LTD. 2004
Version 1 Rev 0
rxlev_dl < rxlev_dl_zone and bts_txpwr = bts_txpwr_max_inner
rxlev_dl < rxlev_dl_zone
rxlev_ul < rxlev_ul_zone & ms_txpwr = min(ms_txpwr_max_inner,P)
rxlev_ul < rxlev_ul_zone
S S
pbgt(n) > ho_margin if neighbour qualifies intercell handover If no neighbour qualifies handover MS to outer zone
EMOTOROLA LTD. 2004
579
Enabling the Dual Band Feature
Version 1 Rev 0

A resource from either the secondary or primary band of a dual band cell will be allocated for assignments or handovers provided the necessary criteria is met. These include the previously discussed restricted features that need to be enabled and the need for the inner zone algorithm to be set to 3. There are further criteria for enabling the dual band feature.
Multiband
S The database parameter multiband preference has to be set to 1 to enable the multiband feature. mb_preference <value> <location> Valid Range = 0 multiband feature disabled 1 multiband feature enabled S The database feature coincident multiband must be set to disabled in order to change inner zone algorithm to indicate dual band cells. This is because dual band and coincident multiband cannot be configured simultaneously.
coincident_mb = 0 (disabled) S S S The mobile must support the frequency band of the inner zone. The database parameter band preference mode must be set to either 1,3,5 or 6
band_preference_mode = 1, 3, 5 or 6 The parameter interband_ho_allowed defines the frequency types of the BCCH carrier of target cells that are allowed for intercell handover. If the target cell is a dual band cell the actual channel assigned by the target cell may be of a frequency type not specified by interband_ho_allowed as long as the mobile supports that frequency type.
chg_element interband_ho_allowed <value> <location> cell=<cell_desc> Valid range 1 to 11 (PGSM, EGSM, DCS1800 and PCS1900) 16 to 27 (The above plus GSM850) S The percentage of outer zone traffic channel usage meets or exceeds the outer zone usage level.
580
EMOTOROLA LTD. 2004
Version 1 Rev 0
mb_preference <value> <location> Valid Range = 0 multiband feature disabled 1 multiband feature enabled
Primary Band
coincident_ mb set to 0 or disabled
Inner zone signal strength criteria met
band_preference_mode = 1,3,5 or 6
Secondary Band interband _ho_allowed

Multiband mobile
TCH usage exceeds outer_zone_usage_level

SYS12_Ch05_28
EMOTOROLA LTD. 2004
581
Handover and Power Control
Version 1 Rev 0

With the dual band feature it is necessary to perform intra cell handovers both within the secondary and primary bands as well as between the secondary and primary bands of a dual band cell. The BSS performs power level conversions during intra cell channel changes between channels of different frequency bands. It is also necessary to perform intercell handovers from the secondary and primary bands of a dual band cell as well as to the secondary and primary bands of a dual band cell. The power budget equation determines the need for an intercell handover by essentially comparing the serving cell BCCH signal strength to the neighbour cell BCCH signal strength. This means the signal strength in a dual band cell must come from the primary zone. When the call is in the secondary zone, the signal strength reported by the mobile cannot be used in the power budget equation, because frequencies in the secondary band have a different propagation than frequencies in the primary band.
582
EMOTOROLA LTD. 2004
Version 1 Rev 0
Primary Band
Primary Band
Secondary Band
Serving cell BCCH signal strength
Secondary Band
Neighbour cell BCCH signal strength If call is in the secondary zone, signal strength reported by mobile cannot be used in pbgt equation
Primary Band
Secondary Band
SYS12_Ch05_29
EMOTOROLA LTD. 2004
583
Version 1 Rev 0

Power Budget Mode
There are two ways to obtain the primary zone signal strength, selectable via the pbgt_mode data base element. If pdgt_mode = 1 If the mobile is assigned to a resource on the secondary band, the mobile will use the serving channel measurements and then subtract the dual_band_offset. This estimated value is then inserted into the power budget equation. If the pbgt_mode = 0 The serving cell BCCH is included in the ba_sacch neighbour cell list of the serving cell. The mobile will then report the serving cell signal strength for the primary band, which can be used in the calculation of power budget for neighbours with the same frequency band. The actual number of neighbour frequencies that can be reported on is reduced by one, also the number of true neighbours that the MS can report on is reduced from six to five. If pbgt_mode = 0 then the server is auto equipped as a neighbour.
Handover Power Level Inner

The database parameter ho_pwr_level_inner specifies the handover power level for the inner zone. It is set when the inner_zone_alg is set to dual band cell, the BSS then prompts for the value to be entered. This allows secondary and primary bands to have different handover power levels, rather than having one value for the entire cell.
Transmit Power Capability

Before development of this feature, transmit power capability could only be modified when the frequency type of the cell is set to DCS 1800 or PCS 1900. The tx_pwr_cap is used to indicate that the carrier units are capable of high power. The dual band cells feature has modified this parameter so that it can be set when the primary, outer zone frequency type of the cell is PGSM, EGSM, DCS 1800 or GSM850.
Dependancies
This parameter is valid only if the RCUs, (D)RCUs, SCUs or TCUs at the site are inactive.The system does not accept this parameter if the associated DRIs are unlocked.
584
EMOTOROLA LTD. 2004
Version 1 Rev 0
pbgt_mode = 1
S S
RXLEV_DLEST_BCCH = RXLEVINNER_ZONE dual_band_offset RXLEV_DLEST_BCCH is then used in power budget equation
pbgt_mode = 0
S
BCCH frequency of serving cells is added to the BA SACCH neighbour cell list of serving cell Serving cell BCCH takes the place of an actual neighbour Serving cell is auto equipped as a neighbour
S S
ho_pwr_level_inner Range from 2 to 19,0 to 15 based on the phase and class of the mobile tx_power_cap Used to indicate that the carrier units are capable of high power
EMOTOROLA LTD. 2004
585
EGSM Layer Management Within a Dualband Cell
Version 1 Rev 0

Dualband cells allow DCS1800 secondary band carriers to be considered as a preferred band neighbour. But before the secondary band of he dualband cell can be considered it must first qualify, by passing some entry criteria calculated on the downlink rxlev of the primary band BCCH reported. If the secondary band of the dualband cell does qualify it is sorted as a preferred band neighbour. In the modified candidate list shown opposite the nonpreferred band neighbour BCCH (PGSM/EGSM) cells with DCS1800 secondary band resources appear in the list twice. Once as a preferred band resource and once as a nonpreferred band resource. If the MS is EGSM capable and is currently established on an SDCCH, band_preference_mode is set to 1, 3 or 5 and there are free EGSM resources in the current cell. The band_preference_mode which would normally handover the call to the strongest preferred band neighbour cell will be ignored in this case, and a free EGSM resource will be allocated to the call. To implement the EGSM layer management feature call processing ignores any zone handovers directed to the DCS1800 frequency band when a EGSM capable MS is on an EGSM TCH in the primary band.If an intercell handover is triggered and the EGSM capable MS is on an EGSM TCH resource in a dualband cell. The MS is directed to the next available cell with an EGSM resource, whether it be a single band cell or a primary band resource within a dualband cell. If this handover cannot take place, for example congestion reasons. The MS will be targeted to the next neighbour in the neighbour list, the neighbour maybe a single band DCS1800 cell, a dualband cell with DCS1800 resources or a single band PGSM cell, as directed by band_preference. When an EGSM capable MS establishes on a PGSM TCH resource in a dualband cell and a zone handover is triggered to direct the MS to the secondary band within the cell. The zone handover will be processed and the MS shall be handed into the secondary band (DCS1800).
586
EMOTOROLA LTD. 2004
Version 1 Rev 0
Preferred band neighbour (DCS1800) Preferred band Nonpreferred band neighbour (PGSM) Nonpreferred band neighbour (PGSM/EGSM) Nonpreferred band Nonpreferred band neighbour (PGSM/EGSM) with secondary DCS1800 Nonpreferred band neighbour (PGSM) with secondary DCS1800
Candidate neighbours reported from RSS
Nonpreferred band (PGSM/EGSM) Nonpreferred band neighbour (PGSM/EGSM) with secondary DCS1800
chg_element bss_egsm_alm_allowed 1 <site number> Preferred band (DCS1800)
Nonpreferred band (PGSM) Candidate neighbours sorted by CP
EMOTOROLA LTD. 2004
587
Extended Range Cell
Version 1 Rev 0
Extended Range Cell

Motorola supports a software feature called Extended Range Cell or ERC that allows mobiles to use a cell beyond the GSM specified 35 kilometre limit. At distances greater than 35 Km the propagation delay exceeds the standard GSM timing advance of 63 bit periods or 233us. This timing advance is sufficient for the twoway propagation delay between the BTS and the MS to be overcome. From distances over 35km, the MSs transmitted signal will begin to arrive in the following timeslot, corrupting the data being processed in both timeslots. With the ERC feature enabled, the BTS expands its receive window to cover both the MS allocated timeslot and the following timeslot. This gives an effective 156 extra bit periods for the propagation delay which increases the maximum cell radius to 121km. In simple terms, it is necessary to use two normal timeslots to form a single extended range timeslot. Using two timeslots allows the BTS to handle additional propagation delay from the mobile. The actual value of timing advance given to the MS can still only go up to 63 bit periods, but as the MSs transmit burst can be late by a whole timeslot at the BTS and still be decoded correctly. The extended range cell feature is supported by the SCU, TCU and CTU families of radio.
588
EMOTOROLA LTD. 2004
Version 1 Rev 0
Extended Range Cell
Extended Range Cell
Tx BTS
4
Propagation Delay
Rx MS
3 timeslot offset
Tx MS
Propagation Delay
Rx BTS
S S S
SYS12_Ch05_30
To prevent the burst from moving from its timeslot into a neighbouring timeslot a timing advance is introduced to send the burst earlier therefore overcoming the propogation delay The maximum timing advance for a normal range timeslot is 63 bit or a propogation distance of 35 km radius anymore than this and it runs into the next timeslot. Extended range allows the complete use of the next timeslot, hence a further 156 bits, which together with the 63 bits from the primary timeslot gives a radius of 121 km
EMOTOROLA LTD. 2004
589
Timeslot Allocation
Version 1 Rev 0
Timeslot Allocation
In an extended range cell, all BCCH and SDCCH control channels are allocated dual timeslot channels. This allows the cell signalling to cover mobiles within the 35Km limit and the extended coverage range (up to 121km). When a mobile originates, it is assigned either a single timeslot or dual timeslot channel, based on the timing advance information. Mobiles can also move between normal range areas and extended range areas based on timing advance information reported. It is recommended that combined control channels be configured for two carrier cells. If noncombined control channels are used the 8 SDCCHs placed on the second carrier would also need to be allocated an extended range cell timeslot. This will reduce the capacity of the cell by either one extended range cell timeslot or two normal range timeslots. It can be assumed that with some extended timeslots configured, that the signalling requirements will be reduced from that of a two carrier cell with all normal timeslot configured. However, this is not to say that it cannot be configured for noncombined where conditions dictate.
590
EMOTOROLA LTD. 2004
Version 1 Rev 0
Timeslot Allocation
Timeslot Allocation
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
BCCH CONTROL CONTROL Extended TCH Extended TCH TCH TCH
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7 Non BCCH
Extended TCH
Extended TCH
TCH
TCH
TCH
TCH
S S
SYS12_Ch05_31
All BCCH, CCCH or SDCCH must be extended range timeslots Each carrier can have between 0 and 4 extended range timeslots
EMOTOROLA LTD. 2004
591
Extended Range Cell parameters
Version 1 Rev 0

The extended range cell feature is enabled using the parameter ext_range_cell. The range of the extended range cell is dictated by the timing advance applied to it. The parameter ms_max_range has an increased range, from 63 to 219. Each of these timing advances equates to 550m. If the extended range cell feature is activated, then the number of timeslots per carrier assigned to extended range use is assigned within the equip rtf command. A maximum of 4 extended range timeslots can be assigned per carrier, each consisting of a pair of normal range timeslots. A maximum of 20 SDCCHs are allowed in the extended range cell feature. These must all reside on the BCCH carrier. This configuration will be spaced over 3 timeslots utilizing a combined multiframe. The priority of extended range cell carriers can be altered by use of the add_neighbor command. Carriers are classified as normal or extended range.
592
EMOTOROLA LTD. 2004
Version 1 Rev 0
Extended Range Cell Parameters

chg_cell_element ext range_cell = <*><cell decription> <*> 0 = extended range disabled 1 = extended range enabled chg_element ms_max_range = <*><location>cell =<cell desc> <*> = 0 to 63 Normal range cell
= 0 to 219 Extended range cell equip <site> RTF . . enter the number of extended range timeslots allowed: 0 to 4 chg_element max_number_of_sdcchs = <*><location>cell=<cell desc>
<*>=maximum of 20 for extended range cell add_neighbour <source><target><placement><list_type> . Enter the range of the neighbour cell: normal or extended.
EMOTOROLA LTD. 2004
593
Extended Range Handovers
Version 1 Rev 0

Intracell Handovers
If the mobile is on an extended range timeslot, but its timing advance indicates that it within 35Km of the BTS i.e. < 63 bits. Then an intracell handover occurs to a normal range timeslot to save resources for distant mobiles. The opposite happens when the mobile is on a normal range timeslot and moves beyond 35Km of the BTS i.e. > 63.
Intercell Handovers
When a handover occurs from a normal range cell to an extended range cell, the target cell (which does not know the mobile timing advance) will always assume that the incoming call requires an extended range timeslot, so that no matter where the incoming mobile is located, (within range of the extended range cell) the call will always survive. Therefore the target cell will always allocate an extended range timeslot if possible. When the handover actually takes place, the target cell will examine the mobiles timing advance and if it is in fact below 63 bit periods (I.e. within range for a normal range cell) it will handover to a normal range timeslot. To assist with this procedure, the serving cell prioritises the neighbours. Firstly, the timing advance is compared to a threshold. Prior to GSR 5.0 the threshold was 50. With GSR 5.0 it is now possible to set the threshold with the parameter erc_ta_priority. The value can be set between 0 and 63. If the timing advance is above the threshold, the extended range neighbours are placed at the top of the list of handover candidates. If the timing advance is below the threshold, the extended range neighbours are placed at the end of the list of handover candidates. erc_ta_priority = <*> * = 0 to 63
594
EMOTOROLA LTD. 2004
Version 1 Rev 0
Normal range Cell Extended Range Cell
Serving Cell Prioritises Neighbours Timing Advance compared to a Threshold erc_ta_priority = <*> * = 0 to 63 Timing Advance > Threshold Timing Advance < Threshold ERC neighbours top of neighbour list ERC neighbours at the end of neighbour list
SYS12_Ch05_34
EMOTOROLA LTD. 2004
595
RF Planning Guidelines
Version 1 Rev 0
Most of the GSM900 mobiles in use in networks around the world are Class 4. These give an output power of 2 Watts. However, Class 2 mobiles are still manufactured which give an output of 8 Watts and are able to transmit further. For planning purposes the Class 4 (2W) mobile should be used for consistency The sensitivity of the MS is fixed by the manufacturer and is primarily designed for the GSM specification of a 35km cell. The BTS can, however, be optimised by increasing transmit power. Sensitivity can also be increased through the use of low noise masthead amplifiers.
Another consideration is that the primary propagation method of GSM is Line of Sight (LOS). As such the height of the transmitting / receiving antenna is vital. The simple formula listed in the example shows the minimum height required to reach a specific distance.
596
EMOTOROLA LTD. 2004
Version 1 Rev 0
Example
86.607 km
540M + 46M
1 _
d = (2rh)
Where r = radius of the Earth = 6.4 x 10 m h = height of the antenna including height above sea level 1 _ 2
d = (2 x 6.4 x 106 x 586)
D = 86.607 km
SYS12_Ch05_32
EMOTOROLA LTD. 2004
597
Maximizing Output Power
Version 1 Rev 0

To maximise the output power of the Base Station, single carrier cells can be used. This will avoid the combination losses of multiple carrier cells. This means that the output power at the top of the cabinet could be set to 40 watts (900MHz), giving an increase in signal strength of 3 dB. However, this will limit the capacity handling ability of the cells. For cells where additional carriers are required, air combining can be implemented so that the combination losses are minimised. To maximise transmit and receive powers, high gain directional antennas are should be implemented with a minimum of 16dBi gain, however the exact specifications will depend on the specific application. The antennas should also be mounted as high as is practical. Obviously, the higher the antenna is the larger the propagation distance. Note: Where possible sites should be located on top of hills, etc to gain the height above the average surrounding terrain. This allows for large effective antenna height without the need for high towers. The horizon distance should also be taken into account when deciding the antenna height.
598
EMOTOROLA LTD. 2004
Version 1 Rev 0

Single carrier cells S S S S Avoid the combination losses of multiple carrier cells.
Multiple carrier cells Air combining to minimize combination losses.
Base Station Antennas High gain directional antennas Wherever possible antennas should be positioned on high ground
EMOTOROLA LTD. 2004
599
Maximizing Receiver Sensitivity
Version 1 Rev 0

Nothing can be done to improve the sensitivity of the mobile phone as it is fixed to the specifications of each manufacturer. Therefore the design figure to be used in the link budget calculations is 102dBm ,as per ETSI specifications. Optimizing the receive path will improve the sensitivity. The exact figure will depend on the specifications of the amplifier used. Motorola 900 and 1800 radios are already designed to exceed the ETSI specifications for BTS sensitivity. In addition to this, the implementation of Low Noise Mast Head Amplifiers will add significantly to the effectiveness of the cell. Low noise amplifiers can give gains of up to 12dB in the uplink.
5100
EMOTOROLA LTD. 2004
Version 1 Rev 0
MS Sensitivity fixed S Link budget design specification of 102 dBm
Low Noise Mast Head Amplifiers S Gains of up to 12dB in the uplink
MHA Bias Tee (internal to MHA) RF feeder
DC voltage BTS
SYS12_Ch05_33
EMOTOROLA LTD. 2004
5101
Version 1 Rev 0
5102
EMOTOROLA LTD. 2004
Chapter 6
Adaptive MultiRate and HalfRate
EMOTOROLA LTD. 2004
61
Version 1 Rev 0
62
EMOTOROLA LTD. 2004
Version 1 Rev 0
Adaptive MultiRate and Half Rate
Adaptive MultiRate and Half Rate

Objectives
S S S S S S Discuss Half Rate Discuss Adaptive MultiRate. Consider AMR Half and Full Rate Consider AMR Half and Full Rate Link Adaptation Discuss MS Monitor Functionality Discuss Handover and Power Control Parameters for AMR
EMOTOROLA LTD. 2004
61
Half Rate
Version 1 Rev 0
Half Rate
The GSM Half Rate feature offers enhanced capacity over the air interface, corresponding to the proportion of mobiles within a coverage area that supports Half Rate. An air timeslot is split into two subchannels, each containing a half rate channel. Speech quality is considered inferior to other speech codecs but has a high penetration level (of GSM HR capable mobiles) due to its early introduction into the standards. Due to these large penetration levels it is considered a viable option for high density areas. A GSM HR call can fit within an 8kbps timeslot (an Ater channel) on the terrestrial resource from the BSC to the RXCDR, rather than the 16kbps timeslot required for FR calls. If a percentage of the active calls can be assumed to be HR, then efficiencies can be gained by reducing the number of terrestrial resources between the BSC and RXCDR. This is possible only if the BSC can dynamically allocate a timeslot to a CIC on an 8kbps/16kbps basis. This dynamic allocation is performed across a trunked interface between the BSC and a remote transcoder (RXCDR). This interface is called the Ater interface. The dynamic allocation is an enhancement to the existing Auto Connect mode feature, referred to as Enhanced Auto Connect mode. Enhanced Auto Connect is part of the AMR feature and is mentioned here only to point out that GSM HR will enjoy the same benefit. The backhaul requirements between the BTS and BSC may also be reduced to 8kbps as long as subrate (8K) switching is present at the BSC. Both GDP and GDP2 boards will be enhanced to support GSM HR. GDP will be introduced first, followed by GDP2 in a future release.
62
EMOTOROLA LTD. 2004
Version 1 Rev 0
Half Rate
Half Rate
5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5
Full Rate Speech
Half rate channel
5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5
Half rate channel
SYS12_ch1_13
EMOTOROLA LTD. 2004
63
Version 1 Rev 0

Adaptive MultiRate (AMR) is introduced in GSR7 and provides two modes of working AMR fullrate channel mode (AMR FR) and AMR halfrate channel mode (AMR HR).
AMR Full Rate Channel Mode

This mode of working provides higher speech quality in areas of poor RF conditions.
Full Rate Link Adaptation

AMR FR link adaptation works in conjunction with the rest of the AMR feature set, namely AMR, Call downgrade on CIC capability mismatch and Enhanced GDP provisioning. It provides improved speech quality in poor RF environments by adapting the speech rates and level of error correction on a call. Speech quality is improved by reducing the speech rate and increasing the level of error correction in poor RF environment. The speech rate used is determined by the codec mode used. The Active Codec Set (ACS) refers to the set of up to 4 AMR codec modes that can be utilised for any given voice call in the uplink and downlink direction.
AMR Half Rate Channel Mode

This mode of working allows two AMR calls to be placed on a single air interface timeslot. This gives an increase in cell capacity with no additional hardware. However extra backhaul is required between BSC and BTS due to there being no 8kbps switching in release GSR7. This means that AMR halfrate speech data has to be carried in 16kbps TRAU format between BSC and BTS. Given that potentially 16 AMR halfrate calls can be supported on an AMR halfrate carrier, an AMR halfrate RTF must have four associated E1 timeslots provisioned between BSC and BTS. Due to reduced bandwidth, an AMR halfrate call will in general have a lower QoS than a fullrate call. For this reason the user will be able to specify a congestion level that has to be exceeded in an AMR halfrate cell before new calls will be assigned to a halfrate channel. In addition, when the received bit error rate (Rxqual) indicates that a half rate channel is suffering interference and that the speech quality of the call is therefore impaired, an intracell handover back to fullrate (or to another halfrate channel) is supported to maintain quality of service. There is also a lower QoS provided by AMR halfrate calls.
Half Rate Link Adaptation

AMR HR link adaptation operates in a similar way to AMR FR link adaptation. The differences are the bit rates of the HR codec modes supported, different initial HR codec mode and different associated uplink and downlink codec mode adaptation thresholds and hystersis values.
Active Codec Set Values

In total there are 8 Active Codec Set values. 0 1 2 3 4 5 6 7 12.20 kbps 10.20 kbps 7.95 kbps 7.40 kbps 6.70 kbps 5.90 kbps 5.15 kbps 4.75 kbps
The BSS supports: 12.1, 10.2, 7.4, 6.7 and 5.15 kbps for a full rate channel. 7.95, 7.4, 6.7, 5.9 and 5.15 kbps for a half rate channel.
Version 1 Rev 0
Dependant on: Enhanced GDP Provisioning Call downgrade on CIC capability mismatch
Up to 16 AMR half rate calls Up to 8 AMR full rate calls
MSC
RXCDR
BSC
BTS
Or a combination of the two.
Up to four codec modes can be included in FR and HR Active Codec Set Which Codec Mode used depends on RF conditions
For half rate rtf two E1 timeslots required
SYS12_amr_01
EMOTOROLA LTD. 2004
65
AMR HalfRate Further Considerations
Version 1 Rev 0

The operator may set a database parameter in order to override any MSC channel rate preference (if given) and the cells congestion threshold, causing AMR calls to be assigned directly to HalfRate channels. This allows temporary forcing (from the OMC) of HalfRate usage during busy periods. IntraCell handovers for quality reasons from HalfRate are still permitted when the override flag is set, but the target resource for the intracell handover will be forced to halfrate. In addition to the ability to specify that new halfrate capable calls should be assigned to halfrate traffic channels when cell congestion exceeds the threshold, the operator will have the ability to specify a second (or alternative) congestion threshold. When this congestion threshold is exceeded in an AMR halfrate channel mode cell, the BSS SW will reassign halfrate capable fullrate calls to halfrate traffic channels. Congestion and qualityrelated intracell handovers can occur between AMR FR and AMR HR channel modes, and between GSM FR/EFR and AMR HR. The following conditions apply to determination of a halfrate capable call for either congestion based FRHR intracell handovers or quality based halfrate intracell handovers: S The MSC must identify to the BSC that the call is capable of both channel types and at least one FR and one HR (the AMR HR) speech version in the Channel Type IE in the Assignment Request or Handover Request. S The identified FR and HR speech versions must be enabled at the BSS level (AMR FR/AMR HR/EFR) and Cell level (AMR FR/HR). S The MSC must not specify that rate changes not allowed after initial assignment in the Channel Type IE. Note: If rate changes not allowed after initial assignment is specified by the MSC, the BSS must only allow the call to use the channel type allocated initially. Therefore any procedures, such as congestion based FRHR intracell handovers or quality based halfrate intracell handovers, which will result in a channel rate change are not allowed. S The specified CIC for the call must be AMR capable (uses the transcoding resources of an enhanced transcoding GDP), which means that it will support halfrate and all of the FR speech versions. Note that if the CIC used changes during the call (at the request of the MSC), the call may become routed onto a basic GDP or XCDR, and so it shall no longer be a half rate capable call. The portion of the feature relating to handover of existing FullRate calls to HalfRate is used in conjunction with the Congestion Relief feature, and verifies that this feature is in use. Mobiles which are considered the best candidates for using HalfRate are those closest to the centre of the cell, as indicated by those not included in the power budget criterion for standard Congestion Relief (handing over to the strongest neighbour cell).
66
EMOTOROLA LTD. 2004
Version 1 Rev 0
Assignment or Handover Request Msg At least one FR and one AMR HR speech version in the channel type IE MSC must not specify rate changes not allowed after initial assignment in the channel type IE
MSC
RXCDR
G D P
BSC
BTS
Identified AMR FR and AMR HR must be enabled at cell level
Identified AMR FR and AMR HR must be enabled at BSS level
Specified CIC for the call must be AMR capable (Enhanced GDP)
SYS12_amr_02
EMOTOROLA LTD. 2004
67
Enabling Half Rate
Version 1 Rev 0
Enabling Half Rate

Many of the parameters associated with the AMR feature are generic to both Half Rate and AMR. In the case of enabling Half Rate there are two new parameters unique to half Rate. At BSS level chg_element gsm_bss_half_rate_enabled <*> <location> <*> 0 = Disabled 1 = Enabled In the case of remote transcoding the AXCDR must have CIC validation enabled. Also if the parameter handover_required_sp_ver_used is disabled this parameter will not be allowed to be enabled. At cell level chg_element gsm_half_rate_enabled <*><site no>cell = <cell_id> <*> 0 = Disabled 1 = Enabled The GSM Half Rate feature can only be used at sites comprised of Horizonmacro, Horizonmacro2, MCell2 or MCell6 cabinets. Or a combination of these cabinets.
RTF Change
If the AMR Half Rate or GSM Half Rate feature is enabled then when the RTFs are equipped two further prompts will appear. One to state whether Half Rate is enabled on that RTF and the other to state whether 8kbps of TRAU is allowed on that RTF. Note: If AMR half Rate is enabled and the 7.95kbps Codec Mode exists in the Active Codec Set the 8kbps TRAU option will not be prompted. Example: equip 1 rtf Existing equip outputs unchanged Enter the value for Half Rate enabled = 1 Is 8kbps TRAU allowed (yes/no)?: yes Existing equip outputs unchanged COMMAND ACCEPTED
68
EMOTOROLA LTD. 2004
Version 1 Rev 0
Enabling Half Rate
Enabling Half Rate
MSC Handover request or assignment request required channel is halfrate
BSC
Enabling\Disabling pararmeters per BSS gsm_bss_half_rate_enabled
BTS
Single Zone cell
MultiZone Cell
Equiping RTFs Enabling\Disabling parameters per Cell gsm_half_rate_enabled

SYS12_amr_02a
half_rate_enabled Allow_8k_trau
EMOTOROLA LTD. 2004
69
Channel Allocation for AMR
Version 1 Rev 0

In the Channel Type information element within the Handover Request and Assignment Request messages from the MSC there is a Speech/data indicator octet. This defines whether the request is for speech, data or signalling. the operation of the BSS is different for each option.
Speech
The Channel rate and type octet contained within the Channel Type Information element in the Handover request and Assignment request messages from the MSC contains the following: S Required channel rate i.e. Fullrate, halfrate or either fullrate or halfrate. S In the case of either, the preferred channel rate may be indicated. S In the case of either, whether rate changes are permitted after initial channel allocation may also be indicated. Also the permitted speech version indication octets within the channel type information element list is in order of preference, the speech versions which maybe used for the call. Fullrate Channel Required If the MSC specifies that a call must be allocated a full rate channel by setting the Channel rate and type octet within the Channel type information element in an assignment request or handover request message to a full rate TCH channel Bm. AMR Halfrate Channel Required If an assignment request or handover request message from the MSC specifies the Channel rate and type octet within the channel type information element as half rate TCH channel Lm the BSS will attempt to allocate a half rate channel to the call if GSM speech half rate version 3 is in the permitted speech version indication list. If not the BSS rejects the request. The BSS can only allocate an AMR halfrate channel if the following are true: S The AMR halfrate channel mode is enabled at BSS level S The AMR halfrate channel is enabled for the target cell S There are AMR halfrate channels available in the target cell and the MSC specifies that AMR halfrate If none of these are true and the MSC specifies that an AMR halfrate channel is to be used, then the BSS rejects the assignment/handover request. This is done by sending an assignment failure message to the MSC which can have the cause value requested speech version unavailable for AMR being disabled, or no radio resource available for the case of no AMR halfrate channel resources being available in the target cell.
610
EMOTOROLA LTD. 2004
Version 1 Rev 0

MSC Handover request or assignment request required channel is halfrate
Enabling/Disabling parameters per BSS BSC amr_bss_half_rate_enabled
BTS
Single Zone cell
Multizone cell
Enabling/Disabling parameters per cell amr_half_rate_enabled
ch6_amr_en/dis
chg_element amr_bss_half_rate_enabled <*><location> <*> 0 = Disabled 1 = Enabled chg_element amr_half_rate_enabled <*><site> cell = <cell_id> <*> 0 = Disabled 1 = Enabled Note: CIC Validation must be enabled and in the case of handovers the handover_required_speech_ver_used must also be included in the handover required message.
Force HalfRate
Version 1 Rev 0
Force HalfRate
In the case of the MSC specifying that either a fullrate or a halfrate channel can be allocated to a call, the BSS decides what to allocate. The BSS will attempt to allocate a fullrate channel to the call if any of the following are true: S The AMR or GSM halfrate channel mode is disabled at BSS level S The AMR or GSM halfrate channel mode is disabled for the target cell S The Channel rate and type octet indicates that rate changes after initial channel allocation are not allowed S The CIC selected for the call does not have (AMR) halfrate capability. In addition to this if there is no preferred channel rate , or that a fullrate channel is preferred. The BSS will attempt to allocate a fullrate to the call unless the criteria is met which allows the BSS to ignore the precedence specified by the MSC. The criteria governing this procedure is two fold. S The force_hr_usage per BSS element is set. chg_element force_hr_usage <*> <location> <*> 0 = disabled 1 = enabled S The per cell new_calls_hr congestion level has been exceeded. This congestion threshold indicates at what congestion level the BSS SW should start assigning new halfrate capable calls as AMR or GSM halfrate calls. A limitation exists based on the number of idle halfrate channels and free generic traffic channels in the cell. chg_cell_element new_calls_hr <*> cell = <cell_id> <*> 0 to 101(%) Setting this element to 101 effectively disables the new calls at halfrate congestion mechanism.
Reconfiguration of Existing FullRate Calls

The BSS supports the configuration of the new reconfig_fr_to_hr congestion threshold on a percell basis to indicate at what congestion level the BSS SW should instigate reconfiguration of halfrate capable fullrate calls to AMR or GSM halfrate calls. chg_cell_element reconfig_fr_to_hr <*> cell = <cell_id> <*> 0 to 101(%) Setting this element with a value of 101 effectively disables the reconfigure halfrate full rate calls to halfrate congestion mechanism.
612
EMOTOROLA LTD. 2004
Version 1 Rev 0
Force HalfRate
Force HalfRate
MSC Handover request or assignment request required channel is full rate or halfrate capable
Per BSS parameter to force fullrate calls BSC to AMR or GSM half rate force_hr_usage
BTS
Single Zone cell
MultiZone cell
Congestion parameter for forcing halfrate capable calls to AMR or GSM half rate new_calls_hr reconfig_fr_to_hr
ch_6_amr_force
EMOTOROLA LTD. 2004
613
Reservation of HalfRate Resources
Version 1 Rev 0

The operator will have the ability to reserve a number of halfrate resources (on generic timeslots) for use in congestion. FullRate calls are prevented from using these resources until there are no other timeslots available in the cell/zone. The reserved generic timeslots will be applied to the inner and outer zones within a multizone cell. For example, if the operator specifies to reserve two generic timeslots, this will result in two timeslots being reserved on the inner zone and two timeslots being reserved on the outer zone. It should be noted that the reservation of generic timeslots is applied to each zone within multizone cells (Concentric Cell, Dual Band Cell). Within a cell that does not support multiple zones, all the cell resources are considered to be in the outer zone. The hr_res_ts element specifies the maximum number of halfrate capable timeslots to be reserved within each zone of the cell. Within the inner zone, the actual value can be dynamically limited to be less than hr_res_ts, if the BSS detects that the inner_hr_usage_thres will not be able to be exceeded because of the setting of hr_res_ts. hr_res_ts is also limited by the number of halfrate capable resources available in the cell or zone. There are no specific dedicated HalfRate reserved timeslots. Any timeslot on a HalfRate capable carrier can be considered reserved if FullRate calls have not been assigned to them due to there only being hr_res_ts number of timeslots left in the cell/zone. chg_element hr_res_ts <*><site> cell = <cell_id> <*> 0 to 2558 Default = 2
614
EMOTOROLA LTD. 2004
Version 1 Rev 0
BTS Multi Zone Cell
Single Zone cell
Reservation of timeslots for halfrate usage hr_res_ts
SYS!_amr_10
EMOTOROLA LTD. 2004
615
AMR Full Rate Link Adaptation
Version 1 Rev 0

Full Rate AMR Link Adaptation provides the mechanism by which the BSS adapts between speech codec modes in an AMR codec on the uplink and downlink of an AMR FR call, to provide the most suitable level of error correction for the RF environment. Uplink and downlink codec modes are considered separately and can be adapted separately. The AMR feature provides a set of Full Rate codec modes. With Full Rate Link Adaptation, up to four of these codec modes could be placed in the per cell Full Rate Active Codec Set. It is over this Active Codec Set that the call is adapted according to the quality of the link between the mobile and the BSS. The Full Rate codec modes supported are: AFS 12.2 kbps AFS 10.2 kbps AFS 7.4 kbps AFS 6.7 kbps AFS 5.15 kbps The higher the bit rate of the codec mode indicated the higher the speech rate and the lower the error correction rate. Upto 4 of these codec modes can be included in the FR ACS. For each pair of codec of modes there is an associated threshold and hysteresis value. The associated threshold is used as the lower decision threshold for switching the codec mode to a lower mode with a lower speech rate. The sum of the associated threshold and associated hysteresis is used as the upper decision threshold for switching the codec mode to a less robust mode with a higher speech rate. The threshold and hysteresis are expressed in terms of normalized Carrier to Interference (C/I) values. CODEC_MODE_1 Represents the lowest codec mode (lowest speech bit rate, highest error correction bit rate) of the FR ACS CODEC_MODE_2 Represents the second lowest codec mode, if the ACS contains more than one codec mode. CODEC_MODE_3 Represents the third lowest codec mode, if the ACS contains more than two codec modes. CODEC_MODE_4 Represents the highest codec mode (highest speech bit rate, lowest error correction bit rate) of the ACS if the ACS contains four codec modes. The FR ACS, Full Rate Initial Codec mode and the associated codec mode adaptation threshold and hysteresis values to be used are communicated to the mobile and the channel coder on call initialization and handover. FR AMR codecs provide different levels of error correction and allow different channel bit error rates for acceptable quality of service. As an example, at the lowest codec mode (low speech rate, high error correction) a larger BER may be acceptable as more of the errors will be corrected, where as in a higher codec mode a larger BER would be unacceptable as less errors will be corrected. The differences in AMR channel characteristics prompt the introduction for a new set of HDPC RXQUAL algorithm thresholds. The new HDPC parameters are specific to AMR FR calls and utilize the existing GSM Handover and Power Control algorithms. These new HDPC parameters allow an AMR FR capable cell to be tailored for AMR FR capable mobiles, to increase the range of cells and improve service in poor coverage areas, minimize interference levels to improve speech quality, increase capacity (through tighterreuse of frequencies) and increase service quality by lowering the number of handovers for AMR FR. This release of Full Rate Link Adaptation is tailored towards maximizing speech quality and hence all defaulted values supplied in the software are geared to that goal.
Version 1 Rev 0
AMR FullRate Link Adaptation
C/I
CODEC_MODE_4
THR3 + HYST3 THR3 Available Full Rate Codec Modes AFS 12.2 kbps AFS 10.2 kbps AFS 7.4 kbps Up to 4 can be AFS 6.7 kbps AFS 5.15 kbps THR1 + HYST1 THR1 chosen
CODEC_MODE_2 CODEC_MODE_3
THR2 + HYST2 THR2
CODEC_MODE_1
SYS12_amr_3
EMOTOROLA LTD. 2004
617
AMR Half Rate Link Adaptation
Version 1 Rev 0

Half Rate AMR Link Adaptation provides similar functionality to Full Rate AMR Link Adaptation but for the Half Rate AMR channel. In Half Rate AMR Link Adaptation there is a different Half Rate Active Codec Set. This AHS can contain up to four of the Half Rate AMR codec modes that are supported. The Half Rate codec modes supported are AHS 7.95 kbps, 7.4 kbps, 6.7 kbps, 5.9 kbps and 5.15 kbps. There is also a different Half Rate Initial Codec Mode and different associated uplink and downlink codec mode adaptation thresholds and hysteresis values for Half Rate AMR calls. The existing GSM Handover and Power Control algorithms are still used for the Half Rate AMR channel, but similar to Full Rate Link Adaptation a new set of Handover and Power Control thresholds are introduced. The new Half Rate AMR HDPC RXQUAL thresholds are different to the Full Rate AMR HDPC thresholds because the Half Rate channel will display different characteristics to a Full Rate AMR channel. For these reasons the customer may wish to configure the Handover and Power Control algorithms in a different manner to cater for the Half Rate AMR channel. The MS Monitor introduced in Full Rate AMR Link Adaptation also applies to Half Rate AMR calls. CODEC_MODE_1 Represents the lowest codec mode (lowest speech bit rate, highest error correction bit rate) of the HR ACS CODEC_MODE_2 Represents the second lowest codec mode, if the HR ACS contains more than one codec mode. CODEC_MODE_3 Represents the third lowest codec mode, if the HR ACS contains more than two codec modes. CODEC_MODE_4 Represents the highest codec mode (highest speech bit rate, lowest error correction bit rate) of the HR ACS if the ACS contains four codec modes.
618
EMOTOROLA LTD. 2004
Version 1 Rev 0
AMR HalfRate Link Adaptation
C/I
CODEC_MODE_4
THR3 + HYST3 THR3 Available Half Rate Codec Modes AHS 7.95 kbps AHS 7.4 kbps AHS 6.7 kbps Up to 4 can be AHS 5.9 kbps AHS 5.15 kbps THR1 + HYST1 THR1 chosen
CODEC_MODE_2 CODEC_MODE_3
THR2 + HYST2 THR2
CODEC_MODE_1
SYS12_amr_5
EMOTOROLA LTD. 2004
619
Enabling/Disabling Link Adaptation
Version 1 Rev 0

It is possible in certain situations to disable Link Adaptation for calls in a cell. This is achieved by the use of four parameters. chg_element amr_fr_dl_la_enabled <*><site>cell = <cell_id> <*> 0 disabled 1 enabled Default = 1 chg_element amr_fr_ul_la_enabled <*><site>cell = <cell_id> <*> 0 disabled 1 enabled Default = 1 chg_element amr_hr_dl_la_enabled <*><site>cell = <cell_id> <*> 0 disabled 1 enabled Default = 1 chg_element amr_hr_ul_la_enabled <*><site>cell = <cell_id> <*> 0 disabled 1 enabled Default = 1
620
EMOTOROLA LTD. 2004
Version 1 Rev 0
BSC
BTS Multi Zone Cell
Single Zone cell
Enabling \ Disabling Parameters Per Cell amr_fr_dl_la_enabled amr_fr_ul_la_enabled amr_hr_dl_la_enabled amr_hr_ul_la_enabled

SYS12_amr_11
EMOTOROLA LTD. 2004
621
AMR FR/HR Commands to Specify ACS and Associated Parameters
Version 1 Rev 0

The database parameter chg_acs_params is dealt with here. For this parameter to take effect the BTS type must be AMR capable. Namely these are solely Horizonmacro cabinets, solely MCell2/6 cabinets or a mixture of Horizonmacro and MCell2/6. The AMR firmware is available on CTU, TCUA and TCUB. Also AMR FullRate or HalfRate must be enabled in the cell for the AMR parameters to come into effect. This command allows the parameters to be set before or after AMR is enabled in the cell, thereby allowing the performance to be optimised for calls subsequently initiated in the cell. chg_acs_params <mode> <cell_id> mode = 0 Full rate 1 Half rate 2 Both rates This command is used to specify up to 4 codec modes, to be used in the ACS, associated thresholds and hysteresis values for the cell. Depending on whether Full rate, Half rate or both is entered a number of further prompts are displayed. On this page are the prompted parameters for Full rate. Active Codec Set values 0 1 2 3 4 5 6 7 12.20kbps 10.20kbps 7.95kbps 7.40kbps 6.70kbps 5.90kbps 5.15kbps 4.75
The BSS supports 12.2, 10.2, 7.4, 6.7 and 5.15kbps for a FR channel. Enter AMR Full Rate active codec set : Range 0,1,3,4 and 6 Parameter: amr_fr_acs Description: Up to 4 AMR codec modes that can be used for any given voice call in the uplink or downlink direction. Default (0,1,3 and 6) Enter AMR Full Rate initial codec mode : Range 0,1,3,4 and 6 Parameter: amr_fr_initial_codec_mode Description: Codec mode used at the beginning of a call. If one mode is entered for FR ACS, then the FR Initial Codec Mode will default to this if valid. Default: 1 Enter AMR Full Rate uplink adaptation thresholds : Range 0 to 63 (0.5dB steps) Parameter(s): amr_fr_uplink_threshold3 amr_fr_uplink_threshold2 amr_fr_uplink_threshold1 Description: Lower Fullrate uplink decision threshold for switching from one mode to another. Default: 20, 14 and 9 (10dB, 7dB and 4.5dB).
Version 1 Rev 0
FullRate Example
Note: In this example previously only one mode was configured MMI RAM 0115 > chg_acs_params 0 2 3 4 0 2 678 01 AMR Full Rate active codec set : 1 AMR Full Rate initial codec set : 1 Enter AMR Full Rate active codec set : 1 3 4 6 Enter AMR Full Rate initial codec mode : 1 Enter AMR Full Rate uplink adaptation thresholds : 40 30 20 Enter AMR Full Rate uplink adaptation hysteresis : 1 1 2 Enter AMR Full Rate downlink adaptation thresholds : 45 35 25 Enter AMR Full Rate downlink adaptation hysteresis : 1 1 2 Enter AMR Full Rate uplink adaptation thresholds for frequency hopping : 16 11 4 Enter AMR Full Rate uplink adaptation hysteresis for frequency hopping : 1 1 1 Enter AMR Full Rate downlink adaptation thresholds for frequency hopping : 27 22 14 Enter AMR Full Rate downlink adaptation hysteresis for frequency hopping : 1 1 1 COMMAND ACCEPTED
SYS12_amr_06
EMOTOROLA LTD. 2004
623
AMR FR/HR Commands to Specify ACS and Associated ParametersContd
Version 1 Rev 0

Enter AMR Full Rate uplink adaptation hysteresis : Range 0 to 15 (0.5dB steps) Parameter(s): amr_fr_uplink_hystersis3 amr_fr_uplink_hystersis2 amr_fr_uplink_hystersis1 Description: The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode. Default: 1,1,1 (0.5dB). Enter AMR Full Rate downlink adaptation thresholds : Range 0 to 63 (0.5dB steps) Parameter(s): amr_fr_downlink_threshold3 amr_fr_downlink_threshold2 amr_fr_downlink_threshold1 Description: Lower Fullrate downlink decision threshold for switching from one mode to another. Default: 30, 24 and 19 (15dB, 12dB and 9.5dB). Enter AMR Full Rate downlink adaptation hysteresis : Parameter(s): amr_fr_downlink_hystersis3 amr_fr_downlink_hystersis2 amr_fr_downlink_hystersis1 Description: The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode. Default: 1,1,1 (0.5dB). Enter AMR Full Rate uplink adaptation thresholds for frequency hopping: Range 0 to 63 (0.5dB steps) Parameter(s): amr_fr_uplink_threshold3_hopping amr_fr_uplink_threshold2_hopping amr_fr_uplink_threshold1_hopping Description: Uplink switching thresholds applied to frequency hopping channels. Default: 16, 11 and 4 (8.0dB, 5.5dB and 2.0dB) Enter AMR Full Rate uplink adaptation hysteresis for frequency hopping: Range 0 to 15 (0.5dB steps) Parameter(s): amr_fr_uplink_hystersis3_hopping amr_fr_uplink_hystersis2_hopping amr_fr_uplink_hystersis1_hopping Description: Uplink hysteresis applied to frequency hopping channels Default: 1, 1, 1 (0.5dB) Enter AMR Full Rate downlink adaptation thresholds for frequency hopping: Range 0 to 63 (0.5dB steps) Parameter(s): amr_fr_downlink_threshold3_hopping amr_fr_downlink_threshold2_hopping amr_fr_downlink_threshold1_hopping
Version 1 Rev 0
FullRate Example NonHopping
CODEC_MODE_4 1 10.2kbps THR3 + HYST3 20 + 0.5 = 20.5dB Uplink 22.5 + 0.5 = 23dB Downlink
20dB Uplink CODEC_MODE_3 3 7.4kbps THR2 + HYST2 22.5dB Downlink
THR3
15 + 0.5 = 15.5dB Uplink 17.5 + 0.5 = 18dB Downlink
15dB Uplink CODEC_MODE_2 4 6.7kbps 17.5dB Downlink
THR2
10 + 1 = 11dB Uplink THR1 + HYST1 10dB Uplink Initial Codec Mode CODEC_MODE_1 6 5.15kbps 12.5dB Downlink 12.5 + 1 = 13.5dB Downlink THR1
SYS12_amr_07
EMOTOROLA LTD. 2004
625
Version 1 Rev 0
Description: Downlink switching thresholds applied to frequency hopping channels Default: 26, 21 and 14 (13.0dB, 10.5dB and 7.0dB) Enter AMR Full Rate downlink adaptation hysteresis for frequency hopping: Range 0 to 15 (0.5dB) Parameter(s): amr_fr_downlink_hystersis3_hopping amr_fr_downlink_hystersis2_hopping amr_fr_downlink_hystersis1_hopping Description: Downlink hysteresis applied to frequency hopping channels. Default: 1,1,1 (0.5dB)
Downlink Adaptation Change Minimum Time Period

In the case of downlink adaptation procedure it is possible to specify the minimum time period between initiating changes in the downlink codec mode. When the parameter is set to a value greater than the inherent delay in the adaptation process, a wait period is added to slow down the adaptation. chg_element amr_dl_la_mode_chg_min <*> 0 <*> 0 to 255 (ms) Default = 100ms
626
EMOTOROLA LTD. 2004
Version 1 Rev 0
FullRate Example Hopping
C/I
CODEC_MODE_4 1 10.2kbps THR3 + HYST3 8dB Uplink CODEC_MODE_3 3 7.4kbps THR2 + HYST2 13.5dB Downlink 8 + 0.5 = 9.5dB Uplink 13.5 + 0.5 = 14dB Downlink THR3
5.5 + 0.5 = 6dB Uplink 11 + 0.5 = 11.5dB Downlink
5.5dB Uplink CODEC_MODE_2 4 6.7kbps THR1 + HYST1 11dB Downlink
THR2
2 + 0.5 = 2.5dB Uplink 7 + 0.5 = 7.5dB Downlink
2dB Uplink Initial Codec Mode CODEC_MODE_1 6 5.15kbps 7dB Downlink
THR1
SYS12_amr08
EMOTOROLA LTD. 2004
627
MS Monitor Functionality
Version 1 Rev 0
Full Rate AMR Link Adaptation introduces MS Monitor functionality that monitors and compensates for the inability of some mobiles to accurately estimate the current conditions of the channel that it is using. The threshold and hysteresis values supplied for AMR calls by the network at call initialization may be ineffective for some mobiles in certain RF conditions. The MS Monitor is introduced as a mechanism to adjust the downlink codec mode adaptation thresholds during a call so that the MS is able to correctly adapt across the ACS as needed. The MS Monitor works by monitoring a mobile during a call and detecting conditions that indicate that the downlink codec mode adaptation thresholds need adjusting. The MS Monitor will decrease the thresholds at the MS if they are deemed to be too high and increase the thresholds if they appear to be too low. If a mobiles thresholds are too low, i.e. the range of C/I values that the MS is measuring is below the lowest threshold in the ACS, then the mobile will request the lowest codec mode whilst simultaneously indicating to the network that that call is in very good RF quality conditions. The mobile could operate very well in these conditions in the highest codec mode. The Monitor checks these conditions over a certain period of time and if the quality of the call is high enough then the downlink adaptation thresholds will be modified in the mobile. Similarly, the MS Monitor will increase the thresholds at the mobile if the network sees that the MS is requesting the highest codec mode, whilst indicating that the call is in poor RF quality conditions, as this would indicate that the range of C/I values measured by the mobile were above the highest threshold in the ACS.
Downlink Adaptation MS Monitor Parameters

The BSS MS Monitor, monitors AMR mobiles over a period defined as amr_ms_monitor_period and collects CMR values and RXQUAL values. At the end of this period the data that has been collected is processed and a decision made whether or not to adapt the thresholds used by the mobile. The BTS shall monitor the Codec Mode Request values for individual calls in order to determine mobiles for which the downlink adaptation thresholds should be adjusted. chg_element amr_ms_monitor_period <*> 0 <*> 10 to 120 (SACCH) Default = 40 (SACCH) Description: Used for detecting MSs continually requesting the highest or lowest modes. chg_element amr_ms_high_cmr <*> 0 <*> 50 to 100 (%) Default = 99% Description: Percentages for monitoring AMR MSs continually requesting the highest codec mode. chg_element amr_ms_low_cmr <*> 0 <*> 50 to 100 (%) Default = 95% Description: Percentages for monitoring AMR MSs continually requesting the lowest codec mode. chg_element amr_ms_high_rxqual <*> 0 <*> 0 to 7 (QBand Units) Default = 2.5% BER or QBand Unit 4 Description: Threshold for monitoring AMR MSs continually requesting the highest codec mode. chg_element amr_ms_low_rxqual <*> 0 <*> 0 to 7 (QBand Units) Default = 0.5% BER or QBand Unit 2 Description: Threshold for monitoring AMR MSs continually requesting the lowest codec mode. chg_element amr_dl_thresh_adjust <*> 0 <*> 1 to 7 (dB) Default = 3dB Description: For applying compensation to the C/I adaptation thresholds.
Version 1 Rev 0
Rxqual Thresholds
0 Lower threshold for monitoring AMR MSs requesting the lowest 2 Default codec mode
When an AMR MS has requested the lowest codec mode at least 95% (def) of the monitoring period (40SACCH def)
Apply increase or decrease to dl adaptation thresholds
Default Higher threshold for monitoring AMR MSs requesting the highest codec mode When an AMR MS has requested the highest codec mode at least 99% (def) of the monitoring period (40SACCH def)
SYS12_amr_12
EMOTOROLA LTD. 2004
629
(AMR) Half Rate Handover and Power Control Parameters
Version 1 Rev 0

The ability to set unique thresholds for power control and handovers is allowed. This is because the active codec set used in the cell will affect the thresholds. These additional thresholds are AMR or GSM half rate specific, with existing parameters and levels still applicable for nonAMR calls. The Rxlev thresholds applied for an AMR or GSM half rate traffic channel remain the same as for existing call types (e.g. GSM FR and EFR speech). Full Rate l_rxqual_ul_p_amr_fr (Def 226 BER or 4 QBand) l_rxqual_ul_h_amr_fr (Def 453 BER or 5 QBand) l_rxqual_ul_h_hopping_amr_fr (Def 453 BER or 5 QBand) l_rxqual_ul_p_hopping_amr_fr (Def 113 BER or 3 QBand) l_rxqual_dl_p_amr_fr (Def 113 BER or 3 QBand) l_rxqual_dl_h_amr_fr (Def 226 BER or 4 QBand) l_rxqual_dl_h_hopping_amr_fr (Def 0 BER or 0 QBand) l_rxqual_dl_p_hopping_amr_fr (Def 0 BER or 0 QBand) Half Rate l_rxqual_ul_p_hr (Def 57 BER or 2 QBand) l_rxqual_ul_h_hr (Def 113 BER or 3 QBand) u_rxqual_ul_p_hr (Def 28 BER or 1 QBand) l_rxqual_ul_h_hopping_hr (Def 0 BER or 0 QBand) l_rxqual_ul_p_hopping_hr (Def 0 BER or 0 QBand) l_rxqual_dl_p_hr (Def 57 BER or 2 QBand) l_rxqual_dl_h_hr (Def 113 BER or 3 QBand) u_rxqual_dl_p_hr (Def 14 BER or 0 QBands) l_rxqual_dl_h_hopping_hr (Def 0 BER or 0 QBand) l_rxqual_dl_p_hopping_hr (Def 0 BER or 0 QBand) All range values 0 to 1810 BER if alt_qual_proc = 0 0 to 7 QBand if alt_qual_proc = 1
630
EMOTOROLA LTD. 2004
Version 1 Rev 0
Rxqual Thresholds
BER
QBands
u_rxqual_xx_x_hr The ability to set unique handover and power control thresholds for half rate is supported l_rxqual_xx_x_xx
1810
SYS12_amr_13
EMOTOROLA LTD. 2004
631
AMR or GSM HalfRate Intracell Handovers
Version 1 Rev 0

The support of intracell quality handovers for halfrate channels is provided by the database parameter hr_intracell_ho_allowed. For interference based handovers it further specifies the possible target channel types i.e. full and/or half rate. A Half rate channel will be targeted where the BSS force_half_rate usage flag is set, or in the case where half rate usage is linked to congestion, if either the new_calls_hr or the reconfig_fr_hr thresholds have been reached. A full rate channel will be targeted in all other cases. For quality based intracell handovers, it is possible to either disable (by disabling all intracell handovers) or support targeting of a full rate resource. A half rate resource is not a supported target for quality based intracell handovers. This has four settings listed below: chg_element hr_intracell_ho_allowed <*> <site> cell = <cell_id> <*> 0 Halfrate intracell quality handovers are not initiated by the BSS. Handover required sent to the MSC. 1 Halfrate intracell handovers are disabled. Handover required is not sent to the MSC. 2 Halfrate intracell handovers are enabled. Fullrate only is allowed for interference and quality based handover. 3 Halfrate intracell handovers are enabled. Halfrate and fullrate are allowed for interference based handover. Fullrate only allowed for quality based handover. Related controls force_hr_usage When set will allow targeting of half rate channels for interference based handovers with a hr_intracell_ho_allowed setting of 3. Overriden by a setting of 2 (full rate only) and ignored for settings of 0 or 1 (internal handovers either not supported or disabled). Unless disabled (settings of 0,1), quality based handovers will always target full rate channels. new_calls_hr/reconfig_fr_hr When cell congestion exceeds either threshold, interference based handovers will target half rate channels with hr_intracell_ho_allowed setting of 3, full rate targeted with a setting of 2. Unless disabled (settings of 0, 1), quality based handovers will always target full rate channels.
632
EMOTOROLA LTD. 2004
Version 1 Rev 0
(AMR) HalfRate Intracell Handovers
BTS
hr_intracell_ho_allowed (enabled)
SYS12_amr_14
EMOTOROLA LTD. 2004
633
AMR or GSM Half Rate Intracell Handover Hop Count
Version 1 Rev 0

A unique hop count counter is provided for AMR or GSM half rate intracell quality handovers from halfrate channels is provided for by the database parameter hr_fr_hop_count. chg_element hr_fr_hop_count<*><site> cell = <cell_id> <*> 0 to 255 Default = 1 Used in conjunction with hr_intracell_ho_allowed to restrict the number of intracell handovers between half rate and full rate in any one (hop_count_timer) period (see also hop_count). For a call switching between a half rate channel and a full rate channel, the BSS shall disable intracell handovers and retain on a full rate channel when this threshold (and/or the existing hop_count threshold) is reached. Half rate support shall be reenabled at expiry of the hop_count_timer period. hop_count Used in conjunction with hr_intracell_ho_allowed to restrict the number of intracell handovers. Considers existing full to full and new half to half and/or half to full rate handovers. For half rate intracell handovers with full rate target channel support only (hr_intracell_ho_allowed settings of 2 or 3 based on handover type as above) either this and/or hr_fr_hop_count being reached will disable intracell handovers from the allocated full rate channel for the remainder of the hop_count_timer period. This shall cover congestion based handovers requiring a half rate channel i.e. full rate calls with intracell handovers currently suspended due to reaching the hop_count limit shall not be subject to full to half rate reconfiguration when instigated for a cell. For a call on a half rate channel with intracell handovers currently disabled, qualification for a quality based intracell handover shall be considered as imperative and an intracell handover to full rate performed where possible as intracell handovers are disabled the call shall be retained on the new full rate channel for the remainder of the hop_count_timer period.
634
EMOTOROLA LTD. 2004
Version 1 Rev 0
BTS
hr_fr_hop_count (reached) within hop_count_timer Or for all intracell handovers hop_count (reached) within hop_count_timer
SYS12_amr_15
EMOTOROLA LTD. 2004
635
Version 1 Rev 0
636
EMOTOROLA LTD. 2004
Chapter 7
Planning of Microcells
EMOTOROLA LTD. 2004
71
Version 1 Rev 0
72
EMOTOROLA LTD. 2004
Version 1 Rev 0
Objectives
S S S S S S Discuss the principles of planning microcells. Discuss frequency planning for microcells Calculate a microcell link budget. Discuss the antenna types used in microcellular Appreciate microcellular BTS products Discuss the antenna types for inbuilding cells
EMOTOROLA LTD. 2004
71
Steps in Planning Microcellular Systems
Version 1 Rev 0

Identification of requirements
The first step in planning a microcellular system is to create a clear specification of the requirements for the final system; these requirements include the following points: S S S S S S S S S S S S S Traffic requirements Quality of service (RF coverage, RXQUAL, Blocking) Coverage area Frequency planning Site surveys Specific areas of strategic coverage Hotspots and poor RF coverage Indoor penetration requirements Antennal types and placements Base station products Equipment location E1 links backhaul Coordination with other operators Rate of system growth
72
EMOTOROLA LTD. 2004
Version 1 Rev 0
Identification of Requirements
Traffic requirements Quality of service Coverage area Frequency planning Site surveys Specific areas of strategic coverage Indoor coverage requirements Antenna types and placements Base station products Equipment location E1 links backhaul Coordination with other operators Rate of system growth
sys12_ch04_01
EMOTOROLA LTD. 2004
73
Quality of Service Targets
Version 1 Rev 0

It is of great importance when designing a microcellular system to take into account the way offered traffic is to be handled. With increasing traffic, the behaviour of a multilayer microcell system is complex, therefore it is important from the outset to be clear about the criteria which must be fulfilled in order to constitute a good system design. Some consideration should be given to the following criteria: S S S S S S S blocking probability for originations sdcch blocking E1 link blocking system RF losses (RXQUAL<=4) mean handovers per call location updates per call <= 2% <=1% <=1% <= 2% >= 98% <= 2 <= 1
The first of these criteria is directly experienced by the user. The last criteria must be met so as to avoid overloading the BSS processing capability. The actual behaviour of the system will depend upon user behaviour, variables such as call distribution, speed distribution, repeat attempts etc. make it difficult to produce a model which incorporates all of these aspects. In order to achieve these criteria, very careful use of the handover algorithms and parameters is required. Careful consideration should also be given to the RF coverage as increasing the cell size will increase the traffic handled and vice versa. It has been found that the frequency plan can affect performance. The handovers per call figure do not show a strong dependence on the number of frequencies. The figures for RXQUAL and RF losses however, improve greatly with the increased numbers of frequencies. It is worth considering how existing customers may be affected when implementing the microcells. The aim is to ensure the quality of service is at least as good as the macrocell.
74
EMOTOROLA LTD. 2004
Version 1 Rev 0
Subscriber profiles Blocking probability for originations SDCCH blocking E1 link blocking System RF losses (RXQUAL<=4) Mean handovers per call Location updates per call
sys12_ch04_02
< = 2% < = 1% < = 1% < = 2% > = 98% <=2 <=1
EMOTOROLA LTD. 2004
75
Traffic capacity enhancement
Version 1 Rev 0

Erlang
Traffic capacity is measured in Erlangs. One Erlang equates to one traffic channel permanently utilized for the period of measurement.
Erlang per subscriber

This factor is used to calculate the number of subscribers supported per cell. The factor is chosen from the network profile or actual usage from network statistics. For example if the average holding time for a call is 1 minute 30 seconds, as a fraction of an hour that computes to 1/40th. That expressed that in decimal is 0.025, therefore we have 0.025 Erlangs per subscriber, if that subscriber makes one call in that hour.
Channel Blocking
The standard model used to dimension a system is the Erlang B model. This gives us the number of traffic channels or trunks required or a given grade of service and given ordered traffic. There will be times when a call request is made and all channels or trunks are in use, this call is then blocked. The probability of this happening is the grade of service of the cell. If blocking occurs then the carried traffic will be less than the offered traffic. If a call is blocked, the caller may try again within a short period. Repeated attempts cause the offered traffic to go above the level if there had been an absence of blocking. Because of this factor offered traffic can be incorrect. But if the blocking probability is small then this effect can be ignored.
Example
On the page opposite is an example scenario for a single macrocell with 3 microcells deployed.
Scenario assumptions;
S S S S S Erlangs supported by the 2 carrier macrocell = 8.20E (2 control channels 14TCH). Single carrier microcell support 2.94E. Dual carrier microcells support 9.01E. 0.025 Erlangs per subscriber. 2% blocking (grade of service).
Note:
For call originations it is dependant on what layer (micro or macro) the MS is in idle mode, as to what capacity is available (unless directed retry or congestion relief is used). The capacity of both layers is available for handovers.
76
EMOTOROLA LTD. 2004
Version 1 Rev 0
Traffic Capacity Enhancement
Combined cell scenario Macro (2 carriers) + 3 micro (1 carrier) (1 control channel) +3 micro (2 carrier) (1 control channel)
Capacity increase factor 1 2.08 4.30 * *
Offered Traffic 8.20 17.02 35.23 * *
Subscriber 328 680.80 1409.20 * *
Macrocell Microcells * If subscribers are in micro coverage area
sys12_ch04_03
EMOTOROLA LTD. 2004
77
Traffic Capacity Enhancement Student Exercise
Version 1 Rev 0

Our urban coverage in the example is maintained by a twocarrier macro cell using two common control channels. The subscriber density has risen to 2500 subscribers. To cover all these subscribers with a GOS of 2% blocking, how many onecarrier, two carrier or six carrier microcells would we need? The average subscriber makes two calls per hour with each call lasting two minutes. Assume that all microcells use just one control channel.
78
EMOTOROLA LTD. 2004
Version 1 Rev 0
Capacity Enhancement Student Exercise
First, calculate Erlang/Subscriber No of calls Duration of call(s) Erlang/Subscriber = = = No of calls x call duration(s) 3600 =
Next work out how many Erlangs of traffic need to be supported in the area. Erlangs needed = = = Remember: Therefore: Resultant Erlangs needed layer (on page 47) = Erlangs needed Erlangs supplied from the macro The macro will support traffic as well. Erlang/Subscriber x no. of subscribers
= = Single carrier microcell support at 2% grade of service = Dual carrier microcell support at 2% grade of service = Therefore the number of onecarrier microcells = Erlangs needed Single carrier microcell = Erlangs needed Dual carrier microcell Erlangs needed Six carrier microcell =
Therefore the number of twocarrier microcells
Therefore the number of sixcarrier microcells
EMOTOROLA LTD. 2004
79
Dimensioning of Signalling Channels
Version 1 Rev 0

Consideration should also be given to the required number of signalling channels necessary to handle the signalling generated by a microcellular system. There are three main elements which must be dimensioned. S S S Paging channels Access grant channels SDCCH channels
In order to do this, it is first necessary to have a prediction of the numbers of the various types of transaction that will require resources, these are: S S S S S Call setups SMS setups Supplementary Service invocations Location updates Attach/detach
An analysis of the potential traffic can be done by looking at existing Macrocell usage or the use of planning tools (e.g. Hotspot detection software). Once a Microcell is installed optimisation can take place to help get the signalling channel ratios correct. It is wise to plan for any future expansion at this stage to ensure that the quality of service is not affected by sudden traffic growth in an area.
710
EMOTOROLA LTD. 2004
Version 1 Rev 0
Dimensioning of Signaling Channels
Table 1Signalling Channels (nonLAC)
Number of RTFs
Number of TCHs
Number of Erlangs
Number of SDCCHs
Timeslot utilization Timeslot 0 Other Timeslots
2.94
1 BCCH + 3 CCCH + 4 SDCCH
2 4
14 30
8.20 21.9
8 12
1 BCCH + 9 CCCH 1 BCCH + 3 CCCH + 4 SDCCH
8 SDCCH 8 SDCCH
Table 2 Signalling Channels (LAC)
Number of RTFs
Number of TCHs
Number of Erlangs
Number of SDCCHs
Timeslot utilization Timeslot 0

1 BCCH + 9 CCCH
Other Timeslots 8 SDCCH 8 SDCCH
1 2
6 14
2.28 8.20
8 12
29
21.04
20
2 x 8 SDCCH
sys12_ch04_04
EMOTOROLA LTD. 2004
711
Planning for Hotspots
Version 1 Rev 0

To recap hotsots are located where there is a high subscriber density. Therefore careful liason with the customer should take place to identify where the traffic exists and what type of traffic it is. Further to this an initial inspection of the identified area should take place and potential antenna sites located. It is a good idea to locate 3 or 4 potential sites so there is plenty of choice. Only after this should the hotspot detector be used to select the best site.
Detection of Hotspot cells

The method used to detect hotspots is simply to place a test transmitter in a candidate Hotspot location and transmit a dummy BCCH which is cell barred. The dummy BCCH is transmitted on a clean frequency for which the signal strength in the candidate test area is otherwise below some threshold value. The BSIC/frequency of this dummy BCCH is added to the BA(SACCH) list of the macrocell for which the Hotspot is intended to relieve. The measurement reports of mobiles operating on such a macrocell are analysed to see how strongly they are reporting the dummy BCCH CTP. For a given level reported by the mobile, and given hysteresis values, an assessment can be made of whether the mobile would have handed over to the Hotspot cell, had it been a real cell in the neighbour list of the macrocell. After analysis and assessment, an estimate can be made as to how much of the mobile population in idle mode would have camped on the Hotspot cell, had it not been barred. The attraction of using the Hotspot detector is that separate coverage checks to guarantee traffic are not necessary, the traffic is guaranteed by the very nature of the Hotspot detector technique. Of course coverage checks may still be required to verify that interference does not arise. Appendix B contains a hotspot survey giving detailed information on this subject.
712
EMOTOROLA LTD. 2004
Version 1 Rev 0
Measurement report analysed by CTP
Macrocell providing existing coverage
Measurement reports of hotspot cell sent to serving BTS
Areas identified for antenna location
sys12_ch04_06
EMOTOROLA LTD. 2004
713
Frequency Planning
Version 1 Rev 0
Frequency Planning
There are two possibilities for microcell frequency planning, either reusing frequencies from the macro layer or having a separate band for micros. However, between these two options a mixed strategy could be used. Basically if we have hot spot cells or sparsely connected cells then having a separate frequency spectrum for them would not be efficient. However, if it were a contiguous microcellular layer then it would be better to reserve a separate frequency spectrum as it would be problematic to reuse frequencies in dense traffic areas (more on next page). A mixed solution would be to have a small separate band for the microcellular layer and use this wherever it is not possible to reuse frequencies from the macro layer. For instance if the micro layer had two carriers per cell then a possible solution would be to have the separate band supplying the BCCH frequencies and reuse if necessary the carriers supporting the nonBCCH carriers. A possible way of selecting which frequencies to use for the micro layer would be to scan the available frequency spectrum in the micro area, select any frequencies which fall below 90dBm and use those for the micro layer as macro frequency reuse. When reusing frequencies from the macro layer, if frequency hopping is not being used, we can use frequencies from both the nonBCCH and BCCH frequencies. However, if frequency hopping is being used in the macrolayer then it not advisable to reuse frequencies from the nonBCCH as any interference is hard to identify.
Example
If we take the case of a network with a total of 39 frequencies. In this network there is a combination of a dense city centre environment utilising microcell coverage and a less dense areas also needing the use of micro cells to provide adequate coverage.
Macro Layer
In this network we are using a 5x3 reuse pattern meaning 15 frequencies are used as BCCH channels. The nonBCCH channels are using frequency hopping, the number of frequencies they hop over depends on whether the cells are located in the city centre or outside the city centre. The city centre cells hop over 5 frequencies and the outside city centre are hopping over 6 frequencies. The reason for this is the need to provide more frequencies for the microcell layer in the city, so 1 of the hopping frequencies has been used to provide this.
Micro Layer
There are 9 frequencies being used in the microcells in the city centre. These are made up from: 6 of these frequencies are dedicated frequencies and the other 3 are the ones provided from the frequencies excluded from the macro hopping channels. This number is reduced to 6 (dedicated channels) outside the city centre.
Macro Layer Frequency Reuse

If there are no separate microcell frequencies available, then the macrocell BCCH frequencies can be reused, as long as the macro interference is taken into account, based on its signal strength.
714
EMOTOROLA LTD. 2004
Version 1 Rev 0
Frequency Planning
Frequency Planning
Example Macro Layer

a1 a2 b1 b2 e1 e2 e3 d1 d2 d3 c3 b3 c1 c2 a3
39 Frequencies Available 5x3 reuse pattern for macros = 15 frequencies for BCCH City Centre Additional 15 frequencies used for nonBCCH carriers, hopping with a 3x1x5 reuse pattern Outside City Centre Additional 18 frequencies used for nonBCCH carriers, hopping with a 3x1x6 reuse pattern City Centre
Micro Layer
9 Channels available 6 dedicated, 3 from frequencies excluded for hopping frequencies Outside City Centre 6 dedicated frequencies available only Macrocell BCCH frequencies could be reused
sys12_ch04_07
EMOTOROLA LTD. 2004
715
Macro Frequency Reuse
Version 1 Rev 0

The previous page states that it is theoretically possible to reuse macrocell frequencies. However, it must be emphasised that this is a theoretical analysis using; S S S perfect grid locations identical antenna heights homogenous propagation
These factors all add to the variability in the overall picture, and mitigate against the general reuse of macrocell frequencies in the microcells. There may be some cases where it can be confirmed, by means of the propagation tool or by measurement, that the signal strength from a macrocell is sufficiently low at a microcell location so as not to cause interference. In this case the frequency could be reused in a microcell. However, this is only likely to hold true for isolated microcells. Therefore the following recommendations are adopted; It is preferred that microcell and macrocell layers should use distinct frequency bands. Occasional reuse of a macrocell frequency in the microcell layer may be possible, but this should be confirmed by empirical tests on the system in question. The next possibility to consider is the case where the macrocell frequency allocations are immediately adjacent to each other. For example, if the microcell frequencies are 13 18, then there is an adjacent channel problem. This will occur in the macrocell employing channel 12. A mobile operating on a microcell on channel 13 may not be able to decode the BSIC of the macrocell due to the difference in signal strength exceeding the adjacent channel protection ratio. Thus the macrocell would not appear as a handover candidate and the interlayer handover would not occur. Conversely a mobile on the macrocell would see the microcell as an adjacent channel interferer when it was in the coverage area of this microcell. This could lead to dropped calls. Leaving one guard channel between the micro and macro allocations alleviates this problem considerably, as the adjacent channel protection ratio is now 41dB. This means that the macrocell BSIC can be read over most of the coverage area of the microcell and conversely the area of a microcell over which a mobile on the macrocell will suffer interference is greatly reduced. This motivates the second recommendation; At least one guard channel should be maintained between the frequencies in use in a macrocell and the frequencies in use in the microcells underlying that macrocell. In cases where limited spectrum availability means that a guard channel is not possible, it may be possible to invoke violations of the first recommendation to make the frequency plan work. In the previous example where the microcell frequency groups are 13 18, interference problems were experienced in the macrocell using channel 12. It may be possible to engineer the microcell planning so that microcells that would have used channel 13 use another channel (e.g. channel 10) instead. It is emphasised that that these macro/micro reuse cases should be checked by measurement.
716
EMOTOROLA LTD. 2004
Version 1 Rev 0
Macro Frequencies
Guard Channel Micro Frequencies
It is recommended that macro and micro frequencies use distinct frequency bands for ease of planning Adjacent channel macro and micro frequencies could cause neighbours not to be decoded due to interference (micro source/macro neighbour) and..... If a mobile was on the macro layer, it might see the micro as a adjacent channel interferer, therefore it is recommended that a guard channel is used.
sys12_ch04_08
EMOTOROLA LTD. 2004
717
Requirements for Calculating Link Budgets
Version 1 Rev 0

To ensure the coverage requirements are met for each antenna the link budget should be calculated. The link budget is used to calculate the minimum downlink signal strength received at the mobile as well as the minimum uplink received. The inputs include receive path diversity gain in the uplink, the possible use of mast head amplifiers and the output power of the mobile. Most of the information would come from the manufacturers specifications, or be calculated for each Microcell separately. If these differences are not taken into consideration it is possible that the BTS will have a service area far greater than which the mobile can support due to it operating on a much limited output power. Therefore the path losses and output powers must be very carefully calculated to achieve a system balance. These factors together with the base station height can be used to calculate the coverage area of the cell. Increasing the output power of the BTS will of course increase the cell size, but it will mean that the mobile is maybe not capable of making a call in the new coverage area. A solution would be to increase the gain of the antenna.
BTS/MS Tx Power
The maximum transmit power of the BTS or MS depends upon the type being used for example: Horizonmicro2 Class 4 MS GSM900 1.2W 2.0W 30.8dBm 33.0dBm
The actual transmit power is set by the database parameter max_tx_bts, the value of which for different radios are listed in W23. The values represent the calibrated output power at the top of the cabinet with one stage of combining. Therefore any further combining will effect the actual power output and will require calculating on an individual basis.
Feeder loss
This will depend on the length of cable and its design specification. A figure of 3dBm is fairly typical.
BTS Antenna gain

This information is taken from manufacturers information sheets, typical value 8dBi.
Fading/Interference Margin
Losses due to multipath fading and interference. These figures are usually 3dB each.
MS/BTS Rx Sensitivity
The receiver sensitivity is defined as the minimum allowable receive signal level that will result in a given audio quality. The reference sensitivity for a Horizonmicro2 BTS is 107dBm and the GSM reccomendation for a class 4 mobile is 102dBm. Bearing in mind this is minimum value and system noise could affect call quality an increase in the receive threshold is often chosen as a starting design goal, especially when amplifiers are used in the design.
Antenna/Body loss
This is the loss due to the operator absorbing a portion of the electromagnetic wave. The GSM recommendation is a loss of 3dB.
Diversity Gain
Improves uplink performance by allowing receiver to select strongest signal.
Version 1 Rev 0
Antenna
BTS antenna gain
Antenna gain/diversity gain
Fading/Interference margin
Cable
Total Tx power top of rack
Feeder loss Feeder loss Duplexer or Tx filter loss
Fading/Interference margin
Duplexer Tx Combiner Rx
Combining loss
BTS receiver sensitivity
MS receiver sensitivity MS transmit power
BTS TX Power
MS antenna gain/body loss
T C U
sys12_ch_03_10
T C U
EMOTOROLA LTD. 2004
719
Minimum Coupling Loss Considerations
Version 1 Rev 0

In any RF design where there is the possibility of mobiles operating in close proximity to the base station antenna some consideration must be given to the minimum coupling loss. The minimum coupling loss is the propagation path loss between the base station antenna and the nearest point where a mobile may be expected to be in operation. If the MCL and the system losses are low then there is a potential for interference from foreign mobiles using external base stations while they are located close to the antennas. Lets say a mobile is using the indoor system near the perimeter of the cell and is being received at a low level. If a foreign mobile is in use close to the antenna on a nearby channel, then the interference may drown out the wanted mobiles signal. In most cases, the combined total path loss from the MCL and the system losses are large enough to prevent the foreign mobiles unwanted power from being received within 9dB of the sensitivity of the TRX. If the system losses are low then the cell coverage may be determined by the need for the wanted signal to have an interference margin of greater than 9dB.
720
EMOTOROLA LTD. 2004
Version 1 Rev 0
Minimum Coupling loss Considerations
Mobile from foreign network
Wanted Mobile
S S S S
Minimum Coupling Loss (MCL) is the minimum distance between antenna and nearest realistic point where a mobile can operate The foreign mobile/microcell BTS generates wideband noise/modulation A C/I ratio of 9dB must be maintained for the call to be maintained in the uplink or downlink A margin may be introduced (MCL) to counter this effect however it will restrict the coverage of the microcell
sys12_ch_03_11
EMOTOROLA LTD. 2004
721
Designing with Close Proximity Mobiles
Version 1 Rev 0

Let us take the example of a foreign mobile near the microcell antenna. The question we need to ask is what is the receive level at the radio and is it 9dBs less than the minimum wanted receive level? In order to work out this we need to know some information regarding the mobile: S S S Foreign MS Tx power What is the frequency band of the foreign mobile How far the foreign mobiles frequency offset from the wanted mobiles.
For our example lets say the MS tx power = 33dBm, frequency offset = 400KHz and the mobile is operating in the GSM900 frequency band. Next we need to consider the point in the neighbourhood of this antenna where the path loss is minimum i.e. the nearest point at which a mobile could be expected to be operating. The point at which MCL is experienced will depend on various parameters antenna gain, height, orientation etc. For example, for a directional antenna in a tall building the MCL point may not be on the street at all but in a building opposite the antenna. For our example the MCL = 65dBm
Modulation Spectrum dropoff with frequency Offset

Depending on how much the foreign mobile is offset from the wanted mobiles frequency a value of relative power is given (dBs)for the given offset. So in the diagram on the opposite page our offset is 400KHz so, reading off the graph, that will give us a 60dB drop in relative power.
Note:
Further reading on this topic can be found in GSM 05.05.
722
EMOTOROLA LTD. 2004
Version 1 Rev 0
Relative power (dB)
0 Foreign MS Tx Power 10 Frequency Band Foreign MS 20 30 Frequency Offset 40 MCL 50 60 70 80 Spectrum Characteristics (spectrum due to the modulation) GSM 05.05 GSM 900
200
400
600
1200
1800
3000
6000
Frequency from the carrier
sys12_ch04_12
EMOTOROLA LTD. 2004
723
Designing with Close Proximity Mobiles Calculations
Version 1 Rev 0

The raw values can now be used in a link budget calculation to see what the foreign power at the wanted radio will be. From the previous page, the MS power level 33dBm Taking into consideration the 60dB drop in relative power 33 60 = 27dBm Let us say that the losses at the radio are: Feeder loss = 3dB Duplexor + cable loss = 1 dB Foreign MS Tx power in wanted 200KHz band Minimum coupling loss (MCL) Feeder loss Duplexor + cable loss Foreign power at radio Min wanted rx level for 9dB C/I 27dBm 65 dB 3dB 1 dB 96dBm 87dBm
Therefore the receive level that the wanted mobile must operate on is 87dBm for interference from the foreign mobile to be within GSM defined margins. The graph below shows foreign MS receive levels at the radio against MCL and system losses.
Foreign MS Rx at TRX against MCL & System Losses

(400Khz, MS Tx = 33dBm)
50 60 0 70 80 90 100 110 120 130 140
10 15 20 25 30 35 40 45
MCL =35dB MCL= 45dB MCL = 55dB MCL =65dB MCL = 75dB
System Losses (dB)

sys12_ch_03_12a
724
EMOTOROLA LTD. 2004
Version 1 Rev 0
Foreign MS Tx power = 27dBm MCL = 65dBm
Antenna Duplexer Tx T C U
Foreign MS power at radio = 96 dBm
sys12_ch_03_12
Wanted MS will have to be received at 9 dBs less than foreign MS power 87dBm
EMOTOROLA LTD. 2004
Cable
Feeder loss = 3dB
Duplexer/cable loss = 1dB
Rx
Foreign MS
Wanted MS
725
Uplink Budget Calculation Comparisons
Version 1 Rev 0

Having calculated the minimum receive level for the wanted signal to obtain adequate carrier to interference ratio with respect to the foreign signal, we may now calculate the allowed path loss. The wanted receive level for our example was 87dBm.
Link budget with Close Proximity Mobiles

The MS is transmitting at full power on 33dBm and the receive level taking into consideration is 87dBm, so the difference between the two is 120dB. However, as discussed previously there are other factors to be taken into consideration. Antenna gain/body loss 3dB BTS antenna gain 5dBi BTS feeder loss 3dB Duplexor/Cable loss 1dB This leaves us with an allowed path loss for 87dBm at the radio of 118dB
Link Budget without Close proximity Mobiles

If we say the BTS sensitivity is 104dBm, if we allow a further margin of 7dB to compensate for noise, then we come to a figure of 97dBm, so this time the difference between the MS and receive level is 130dB. Of course the same gains and losses apply so: Antenna gain/body loss 3dB BTS antenna gain 5dBi BTS feeder loss 3dB Duplexor/Cable loss 1dB This leaves us with an allowed path loss for 97dBm at the radio of 128dB
Conclusions
If the link is designed with close proximity mobiles taken into consideration, then the path loss figure has a 10dB difference between it and designing the link budget without close proximity mobiles. In effect this will mean the BTS output power will have a reduced output power, with the implication that the effective cell size is also reduced.
726
EMOTOROLA LTD. 2004
Version 1 Rev 0
Link Budget with Close proximity Mobiles MS transmit power = 33 dBm Calculated receive level = 87 dBm Resultant link budget without losses/gains = 120 dB Antenna gain/body loss = 3dB BTS antenna gain = 5dBi BTS feeder loss = 3dB Duplexor/cable loss = 1dB
Path loss for 87 dBm at the radio is 118dB

S
Link Budget without Close proximity Mobiles BTS sensitivity with 7 dB margin for noise = 97dBm MS transmit power = 33 dBm Resultant link budget without losses/gains = 130 dB Antenna gain/body loss = 3dB BTS antenna gain = 5dBi BTS feeder loss = 1dB
Path loss for 97dBm at the radio is 128 dB
EMOTOROLA LTD. 2004
727
Link Budget for Balanced Downlinks
Version 1 Rev 0

Having calculated the link budget for the uplink we can now calculate the link budget for the downlink.
Link Budget with close Proximity Working

The path loss for the uplink is 118dB. The system losses will be the same as for the uplink: Antenna gain/body loss 3dB BTS antenna gain 5dBi BTS feeder loss 3dB Duplexor \ Cable loss 1dB Combiner loss 3dB Bearing in mind that the MS receiver sensitivity for a class 4 mobile is 102dBm and allowing for a noise margin of 7dB then the design parameter we are looking for is 95dBm. Therefore BTS power output to meet these requirements is 28dBm
Link Budget without Close Proximity Working

In this case the path loss is 128dB. To meet this criteria the BTS output power would have to increase by 10dBs to 38dBm.
728
EMOTOROLA LTD. 2004
Version 1 Rev 0
Transmit power at antenna = 26dBm
Antenna
Antenna gain = 5dB (21dBm)
Path Loss = 118dB Body/antenna loss = 3 dB
Duplexer Tx Combiner T C U
sys12_ch_03_15
EMOTOROLA LTD. 2004
Cable
Feeder loss = 3 dB ( 92 dBm ) (24dBm) Duplexer/cable loss = 1 dB (25dBm)
Rx
Combiner loss = 3 dB (28dBm)
Wanted MS Receiver Sensitivity = 95 dBm
BTS Tx power at the radio = 28dBm
729
The InBuilding Solution
Version 1 Rev 0

Introduction to picocellular
Providing a high level of capacity and coverage inside buildings is a natural progression from the macrocellular wide area coverage, through microcellular coverage of urban environments to the picocellular solution that will provide coverage within buildings. The picocellular infrastructure will provide more cost effective solutions than the traditional BTS infrastructure due to very low output powers, as well as meeting specific environmental conditions. S S S Macrocellular wide area coverage, using your phone in a car. Microcellular coverage of urban environments using a handportable phone. Picocellular enables the concept of cellular everyone everywhere.
Picocellular Benefits
The picocellular environment can offer the operator the following benefits: S S low RF power providing high quality, focused indoor coverage without adversely affecting the surrounding network; picocells maximise efficient use of the available frequency spectrum enabled by the use of low RF output power.
An effective inbuilding system must also provide: S S S S S S coverage at all locations where people might wish to make or receive a call; good call quality; sufficient capacity to support the number of calls to be made; easy capacity expansion when it is required; easy installation; minimal disruption to the external network;
730
EMOTOROLA LTD. 2004
Version 1 Rev 0
Why PicoCellular
Capacity and coverage Macrocells Microcells Picocells
Mobile Picocells Offer
Pedestrian and urban
Offices Undergrounds, Metros Network maturity
Low RF Power Maximise use of available Frequency Spectrum Good indoor coverage Good call capacity Sufficient capacity to ensure all calls
Ease of expansion Ease of installation Min disruption to ext network
sys12_ch02_17
EMOTOROLA LTD. 2004
731
Inbuilding Coverage
Version 1 Rev 0
Inbuilding Coverage
Inbuilding coverage that comes from macrocells and externally mounted microcells is difficult to predict. This is because the main propagation paths into the building from an antenna mounted at some external location depends very much on the particular relationship between the antenna and the building. The diagram opposite demonstrates this. The inbuilding penetration for the case of normal incidence (a) is expected to be significantly better than for the case where the angle of incidence is shallow (b). Improved inbuilding coverage arising from onstreet microcells is likely to be fairly irregular, with most of the improvement in the immediate neighbourhood of the microcell antennas themselves. The situation is complicated by the dependence of inbuilding penetration on the composition and structure of the building.
Propagation from outside to inside

S S S S Cells deployed within streets external to the buildings being covered. Coverage provided both onstreet and, where possible, inbuilding. Cell capacity dependent on expected subscriber usage in cell area and frequency spectrum restrictions. Inbuilding coverage dependent on building penetration requirement (directly affects Tx power and Rx sensitivity requirements).
732
EMOTOROLA LTD. 2004
Version 1 Rev 0
Inbuilding Coverage
Inbuilding Coverage from External Cell
Affected building
Roadway
Antenna position
Affected building
(a) Normal incidence of Rx/Tx
Roadway
Antenna position
(a) Shallow incidence of Rx/Tx
sys12_ch_03_17
EMOTOROLA LTD. 2004
733
InBuilding RF Repeaters
Version 1 Rev 0
Also known as internal illumination. The concept here is to place a BTS either inside or outside the building to be covered, and site a number of RF repeaters inside the building. A single carrier will feed a number of repeaters and if necessary additional carriers can be used. Connection to the repeaters is via coaxial cable or in some cases may be fibre optic. The RF Repeaters (sometimes referred to as RF Heads) normally contain a low noise amplifier, duplexer and sometimes a transmit amplifier. If there is Microcell coverage outside the building with spare traffic capacity, a cell enhancer can be used to pick up the RF from the Micro BTS and distribute it to the in-building repeaters. This method works well with one or two carriers however, if more capacity is required it becomes difficult because of problems at the heads with RF intermodulation and wideband noise.
734
EMOTOROLA LTD. 2004
Version 1 Rev 0
In-building coverage using RF repeaters

Second Floor Antenna -3 dB Splitter First Floor Antenna
Duplexer
Tx TRX Rx
RF repeater with cell enhancer
Cell enhancer Indoor distribution system (antennas & leaky feeder) Microcell pickup antenna
EMOTOROLA LTD. 2004
735
Operation from Tall Buildings
Version 1 Rev 0

A problem sometimes occurs with the uplink operation of microcellular systems when mobiles are operating from the upper floors of tall buildings. Consider the case as shown opposite, where a MS is being served by a nearby street level microcell. The MS is operating in a building that is higher than the typical surrounding buildings. The downlink signal from the nearby microcell antenna is the best server so the MS camps on the cell and makes calls via that cell. The problem is that due to the building height, the uplink signal is now no longer constrained by the street canyons, and the signal will radiate uncontrollably, potentially causing uplink interference. The severity of such a problem depends on the mobiles proximity to windows in the building, and on the required power level. Potential solutions to this problem are; 1. 2. Design the system so that in the upper floors of such typically high buildings the macrocell will be the best server. Set the power control window, so that mobiles camped on a microcell in this situation operate at lower power levels, (provided no other detrimental effects are experienced). Introduce special inbuilding coverage in the upper floors, so that the mobile can operate on a special cell within the building, at lower power.
3.
736
EMOTOROLA LTD. 2004
Version 1 Rev 0
MS operating from tall building
Serving microcell at street level utilising street canyon effect
S Design the system so upper floors are served by macro layer S Set power control lower for microcell lower to prevent excessive
radiation
S Introduce inbuilding coverage

sys12_ch_03_19
EMOTOROLA LTD. 2004
737
Antenna Types
Version 1 Rev 0
Antenna Types
In general there are two types of antennas to choose from: omni_directional (omni) and directional antennas. Omni antennas provide a uniform field pattern in 360 dergrees in the horizontal plane. Directional antennas have increased gain in one or more directions at the expense of reducing gain in other directions. Both directional and omni directional antennas have their uses in microcellular systems. The different antenna types can be used by the proficient cell planner to avoid shadows reduce handover requests, and maximise traffic capture.
Directional antennas
Directional antennas are useful for covering long streets that are of a shape similar to the antenna gain pattern, giving the added advantages of extra gain in the forward direction and suppressed signal in the reverse direction this is a useful characteristic if the cell is a potential interferer to another cell located behind it. It is also worth noting that a directional antenna could be used to improve inbuilding coverage and reduce cochannel interference in the reverse direction.
738
EMOTOROLA LTD. 2004
Version 1 Rev 0
Antenna Types
Antenna Types Directional Antennas
Antenna
Buildings
Coverage Inbuilding coverage improvement
Antenna Reduced cochannel interference in this direction
Buildings
Coverage
sys12_ch_03_20
EMOTOROLA LTD. 2004
739
OMNI antennas
Version 1 Rev 0
OMNI antennas
Omni antennas are useful for covering open areas (e.g. squares, plazas). In these areas, it is desirable to have a clear best server cell to avoid excessive handovers and their attendant problems. Another application is to create a corner crossroads cell. This avoids having transient cells at street crossroads. The problem with transient cells is that a mobile may handover too (or camp on) a cell whilst it is stationary at traffic lights, and then lose the cell as it drives off at high speed before it has a chance to reselect/handover. This situation must be avoided as even slow moving mobiles could experience problems. The solution could be the use of an omni antenna to cover the crossroads. However, by intersecting with more streets the potential for interference with other cells may be increased.
740
EMOTOROLA LTD. 2004
Version 1 Rev 0
OMNI antennas
OMNI Antennas
Antenna
Drop call could result due to transient nature of cells
Antenna
Antenna
sys12_ch_03_21
EMOTOROLA LTD. 2004
741
Installation of Microcell Antennas
Version 1 Rev 0

S The theoretical radiation pattern of an antenna will be distorted by mounting it in close proximity to a wall or other structure. The antenna should ideally be mounted more than one wavelength away. Antennas should be mounted as far away as possible from any electrical equipment (e.g. security cameras, burglar alarms). This is because high values of EIRP could cause triggering of the devices and contravene the standards set for the immunity of equipment to EMC disturbances within Europe on the 1st Jan 1996. Position of antenna and antenna azimuth should be as close as possible to the value used in the prediction tool. An external antenna should ideally be mounted at least one floor lower than the lowest roof in the cells coverage area in order to avoid diffraction over rooftops. Antennas should be mounted at least one floor lower than that of the opposite buildings. Remember not to have antennas too low (at least 5 to 7m up) this avoids obstruction by buses etc. Building features near the antenna (eg buttresses and corners) will have great effects on cell shape, therefore, antenna locality should be carefully chosen.
S S
Diversity
Due to the types of propagation and the low propagation delays in the microcellular environment the benefits of diversity would have to be considered on an individual basis. Not only is space diversity (2 antennae [10 apart) a possible method, but also phase diversity could be used at the BTS. This system again would have to be considered on a per cell basis.
742
EMOTOROLA LTD. 2004
Version 1 Rev 0
Close Proximity of wall or other structures will cause distortion Mount antennas as far away as possible from electrical equipment Directional antenna azimuth should be as close as possible to prediction tool Antenna height should be situated so as not to radiate over rooftops, but not too low so tall vehicles cause interference Building features such as buttresses and corners have a great effect on coverage Diversity (Motorola BTSs do not support this feature)
sys12_ch04_ant
EMOTOROLA LTD. 2004
743
Version 1 Rev 0
Microcellular Base Station Products

Motorola manufactures a range of products specifically designed to be operated in the microcellular environment. A brief description of each of these products is listed on this page, however a much more in depth description of each product is contained in the appendix.
Horizonmicro2
This is a twocarrier base transceiver station (BTSs) that operate in the GSM900 or DCS1800 frequency bands. It can be deployed indoor or out of doors, operated over a wide temperature range, and can be wall or pole mounted. It has an Expansion feature from GSR 5.0 that allows two or three Horizon micro2 BTS units to be connected together to effectively form a two, four or six carrier site. They are interconnected by fibre optic cable. One BTS in the configuration acts as the master and the other units as slaves. If the expanded feature is used a mixture of GSM900 and DCS 1800 frequencies can be equipped.
RF Output Power
The Horizon micro2 GSM900 generates 1.2 W (30.8 dBm) per carrier, while the DCS1800 generates 2.0 W (33.0 dBm) per carrier.
Frequency Hopping
The Horizonmicro2 and Horizonmicro2_ext and support synthesizer frequency hopping (SFH).
Links
Options exist for sites to be interconnected by E1 or HDSL (star and daisy chain) links.
MCellcity & MCellcity+

This is a twocarrier base transceiver station (BTSs) that operate in the GSM900 or DCS1800 frequency bands. It can be deployed indoor or out of doors, operated over a wide temperature range, and can be wall or pole mounted. The MCell city+ adds High bit rate Digital Subscriber Line (HDSL) modems, and air combining providing an improved RF output power.
RF Output Power
The MCellcity GSM900 generates 1.2W (30.8 dBm) per carrier, while the DCS1800 generates 1W (30.0 dBm). The MCellcity+ GSM900 generates 2.5W, whilst the DCS1800 generates 2W.
Frequency Hopping
These products do not support frequency hopping.
Links
Options exist for sites to be interconnected by E1/T1, the MCellcity+ has a HDSL modem providing the technology to connect up the network, enabling E1 or HDSL communication links.
Version 1 Rev 0
Microcellular Base Station Products
Horizonmicro2
ig.057.rh
SYS12_Ch4_22
EMOTOROLA LTD. 2004
745
Antenna types for Picocellular
Version 1 Rev 0

Both directional and omnidirectional antennas have their uses within the inbuilding environment. The different attributes of the various antenna types can be used by the cell planner to: S S S Reduce handover requests Maximise traffic capture Minimise external interference
Directional antenna
Directional antennas are useful for covering long corridors, giving the added advantages of extra gain in the forward direction and suppressed signal in the reverse direction. This can reduce cochannel interference in the reverse direction. The building geometry will modify the directivity of any particular antenna. S S S High gain (forward direction) Control of interference in reverse direction Good for covering long corridors
Omni antenna
Omni antenna are useful for covering open areas. In these areas it is desirable to have a clear best server cell to avoid excessive handovers.
Installation of antennas
S The theoretical radiation pattern of an antenna will be distorted by mounting it in close proximity to a wall or other structure. The antenna should ideally be mounted more than one wavelength away. Antennas should be mounted as far away as possible from any electrical equipment, (e.g. security cameras, burglar alarms). Building features near the antenna will have a great effect on cell shape, therefore antenna locality should be carefully chosen. Cosmetic appearance. Consideration of EMC.
S S S S
746
EMOTOROLA LTD. 2004
Version 1 Rev 0
Antenna Types for Picocellular
Rooms Directional Antenna
Reduced cochannel interference in this direction
Coverage
Rooms
OMNI Antenna
sys12_ch_03_33
EMOTOROLA LTD. 2004
747
Designing with Radiating Cable
Version 1 Rev 0

Radiating cable or flat strip are types of cable which have holes milled in the outer conductor. This allows the RF to leak along the length of the cable and hence offers an alternative to point source antennas. A small portion of the RF energy that is transmitted down the cable leaks out from the holes, hence the term leaky coax.
Some of the expected advantages of radiating cable are that the coverage is more uniform and the radiated power levels are low, which improves signal containment and reduces the risk of overloading the portable unit. Although Radiating cable can be used most anywhere, typical applications have been for covering long tunnels and hallways.
When designing a leaky feeder system it is important to check that the chosen cable type has the correct fire and smoke ratings for the all the areas of installation. It is recommended that the manufacturers mounting fixtures are included in the design to ensure that the coverage pattern and coupling loss meets the specification.
748
EMOTOROLA LTD. 2004
Version 1 Rev 0
Leaky Cable
First Floor
Splitter, tap or directional coupler B T S

sys12_ch_03_34
Ground Floor
EMOTOROLA LTD. 2004
749
Version 1 Rev 0
750
EMOTOROLA LTD. 2004
Version 1 Rev 0
Appendix A (Erlang B Tables)
EMOTOROLA LTD. 2004
A1
Version 1 Rev 0
Erlang B
Offered Erl Carried Erl
No of Traffic Channels 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Grade of Service 0.01% 0.0001 0.0001 0.0142 0.0142 0.0868 0.0868 0.2347 0.2347 0.4520 0.4519 0.7282 0.7282 1.0541 1.0540 1.4219 1.4218 1.8256 1.8254 2.2601 2.2599 2.7216 2.7214 3.2069 3.2066 3.7133 3.7130 4.2387 4.2383 4.7811 4.7806 5.3389 5.3384 5.9109 5.9103 6.4958 6.4952 7.0927 7.0920 7.7005 7.6997 8.3186 8.3177 8.9462 8.9453 9.5826 9.5817 0.1% 0.0010 0.0010 0.0458 0.0457 0.1938 0.1936 0.4393 0.4388 0.7621 0.7614 1.1459 1.1448 1.5786 1.5770 2.0513 2.0493 2.5575 2.5549 3.0920 3.0890 3.8511 3.8474 4.2314 4.2272 4.8305 4.8257 5.4464 5.4409 6.0772 6.0711 6.7215 6.7148 7.3781 7.3707 8.0459 8.0378 8.7239 8.7152 9.4115 9.4020 10.1077 10.0978 10.8121 10.8013 11.5241 11.5126 0.5% 0.0050 0.0050 0.1054 0.1049 0.3490 0.3473 0.7012 0.6977 1.1320 1.1264 1.6218 1.6137 2.1575 2.1467 2.7299 2.7163 3.3326 3.3159 3.9607 3.9409 4.6104 4.5874 5.2789 5.2525 5.9638 5.9340 6.6632 6.6299 7.3755 7.3387 8.0995 8.0590 8.8340 8.7898 9.5780 9.5301 10.3308 10.2791 11.0916 11.0362 11.8598 11.8005 12.6349 12.5718 13.4164 13.3493 1.0% 0.0101 0.0100 0.1526 0.1511 0.4555 0.4509 0.8694 0.8607 1.3608 1.3472 1.9090 1.8899 2.5009 2.4759 3.1276 3.0963 3.7825 3.7447 4.4612 4.4166 5.1599 5.1083 5.8760 5.8172 6.6072 6.5411 7.3517 7.2782 8.1080 8.0270 8.8750 8.7863 9.6516 9.5551 10.4369 10.3325 11.2301 11.1178 12.0306 11.9103 12.8378 12.7095 13.6513 13.5148 14.4705 14.3257 2.0% 0.0204 0.0200 0.2235 0.2190 0.6022 0.5902 1.0923 1.0704 1.6571 1.6240 2.2759 2.2304 2.9354 2.8767 3.6271 3.5545 4.3447 4.2578 5.0840 4.9823 5.8415 5.7247 6.6147 6.4824 7.4015 7.2535 8.2003 8.0363 9.0096 8.8294 9.8284 9.6319 10.6558 10.4427 11.4909 11.2611 12.3330 12.0863 13.1815 12.9179 14.0360 13.7553 14.8959 14.5980 15.7609 15.4457 4.0% 0.0417 0.0400 0.3333 0.3200 0.8120 0.7795 1.3994 1.3435 2.0573 1.9750 2.7649 2.6543 3.5095 3.3691 4.2830 4.1116 5.0796 4.8765 5.8954 5.6596 6.7272 6.4581 7.5727 7.2698 8.4300 8.0928 9.2977 8.9258 10.1745 9.7675 11.0594 10.6170 11.9516 11.4736 12.8504 12.3364 13.7552 13.2050 14.6654 14.0788 15.5807 14.9574 16.5005 15.8405 17.4245 16.7276 5.0% 0.0526 0.0500 0.3813 0.3622 0.8994 0.8544 1.5246 1.4484 2.2185 2.1075 2.9603 2.8123 3.7378 3.5509 4.5430 4.3158 5.3702 5.1017 6.2157 5.9049 7.0764 6.7226 7.9501 7.5526 8.8349 8.3932 9.7295 9.2430 10.6327 10.1011 11.5436 10.9664 12.4613 11.8382 13.3852 12.7159 14.3147 13.5989 15.2493 14.4868 16.1885 15.3791 17.1320 16.2754 18.0795 17.1756
A2
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
No of Traffic Channels 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
Grade of Service 0.01% 10.2274 10.2264 10.8800 10.8789 11.5400 11.5388 12.2069 12.2057 12.8803 12.8791 13.5600 13.5587 14.2456 14.2442 14.9367 14.9352 15.6332 15.6317 16.3348 16.3332 17.0412 17.0395 17.7523 17.7505 18.4678 18.4660 19.1876 19.1857 19.9115 19.9095 20.6392 20.6372 21.3708 21.3686 22.1059 22.1037 22.8446 22.8423 23.5867 23.5843 24.3319 24.3295 25.0804 25.0779 25.8318 25.8293 26.5862 26.5836 0.1% 12.2432 12.2309 12.9689 12.9559 13.7008 13.6871 14.4385 14.4241 15.1818 15.1667 15.9304 15.9144 16.6839 16.6672 17.4420 17.4246 18.2047 18.1865 18.9716 18.9526 19.7426 19.7228 20.5174 20.4969 21.2960 21.2747 22.0781 22.0560 22.8636 22.8407 23.6523 23.6287 24.4442 24.4197 25.2391 25.2138 26.0369 26.0108 26.8374 26.8106 27.6407 27.6131 28.4466 28.4181 29.2549 29.2257 30.0657 30.0357 0.5% 14.2038 14.1328 14.9968 14.9218 15.7949 15.7160 16.5980 16.5150 17.4057 17.3187 18.2177 18.1267 19.0339 18.9387 19.8540 19.7547 20.6777 20.5743 21.5050 21.3975 22.3356 22.2239 23.1694 23.0536 24.0063 23.8863 24.8461 24.7219 25.6887 25.5603 26.5340 26.4013 27.3818 27.2449 28.2321 28.0910 29.0848 28.9394 29.9397 29.7900 30.7969 30.6429 31.6562 31.4979 32.5175 32.3549 33.3807 33.2138 1.0% 15.2950 15.1421 16.1246 15.9633 16.9588 16.7892 17.7974 17.6195 18.6402 18.4538 19.4869 19.2920 20.3373 20.1339 21.1912 20.9792 22.0483 21.8278 22.9087 22.6796 23.7720 23.5342 24.6381 24.3917 25.5070 25.2519 26.3785 26.1147 27.2525 26.9799 28.1288 27.8475 29.0074 28.7174 29.8882 29.5894 30.7712 30.4634 31.6561 31.3395 32.5430 32.2175 33.4317 33.0974 34.3223 33.9791 35.2146 34.8625 2.0% 16.6306 16.2980 17.5046 17.1545 18.3828 18.0151 19.2648 18.8795 20.1504 19.7474 21.0394 20.6186 21.9316 21.4929 22.8268 22.3703 23.7249 23.2504 24.6257 24.1332 25.5291 25.0185 26.4349 25.9062 27.3431 26.7963 28.2536 27.6885 29.1661 28.5828 30.0808 29.4791 30.9973 30.3774 31.9158 31.2775 32.8360 32.1793 33.7580 33.0828 34.6817 33.9880 35.6069 34.8948 36.5337 35.8030 37.4619 36.7127 4.0% 18.3526 17.6185 19.2842 18.5128 20.2193 19.4105 21.1576 20.3113 22.0988 21.2149 23.0429 22.1212 23.9896 23.0300 24.9388 23.9413 25.8904 24.8548 26.8442 25.7705 27.8002 26.6882 28.7581 27.6078 29.7180 28.5292 30.6796 29.4525 31.6431 30.3773 32.6081 31.3038 33.5748 32.2318 34.5430 33.1613 35.5126 34.0921 36.4837 35.0243 37.4560 35.9578 38.4297 36.8925 39.4046 37.8284 40.3807 38.7655 5.0% 19.0307 18.0792 19.9853 18.9860 20.9430 19.8959 21.9037 20.8085 22.8672 21.7238 23.8333 22.6416 24.8018 23.5617 25.7726 24.4840 26.7457 25.4084 27.7207 26.3347 28.6978 27.2629 29.6767 28.1928 30.6573 29.1245 31.6397 30.0577 32.6236 30.9924 33.6090 31.9286 34.5960 32.8662 35.5843 33.8050 36.5739 34.7452 37.5648 35.6866 38.5570 36.6291 39.5503 37.5728 40.5447 38.5175 41.5403 39.4633
A3
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 27.3435 27.3407 28.1035 28.1006 28.8661 28.8632 29.6313 29.6284 30.3991 30.3980 31.1693 31.1661 31.9418 31.9386 32.7166 32.7134 33.4937 33.4904 34.2730 34.2695 35.0543 35.0508 35.8377 35.8342 36.6232 36.6195 37.4105 37.4068 38.1998 38.1960 38.9910 38.9871 39.7839 39.7800 40.5787 40.5746 41.3751 41.3710 42.1733 42.1691 42.9631 42.9888 43.7745 43.7701 44.5775 44.5730 45.3820 45.3775 0.1% 30.8789 30.8480 31.6943 31.6626 32.5119 32.4793 33.3316 33.2982 34.1533 34.1192 34.9771 34.9422 35.8028 35.7670 36.6305 36.5938 37.4599 37.4224 38.2911 38.2528 39.1241 39.0849 39.9587 39.9187 40.7950 40.7542 41.6328 41.5912 42.4723 42.4298 43.3132 43.2699 44.1557 44.1115 44.9995 44.9545 45.8448 45.7990 46.6915 46.6448 47.5395 47.4920 48.3888 48.3404 49.2394 49.1902 50.0913 50.0412 0.5% 34.2459 34.0747 35.1129 34.9374 35.9818 35.8018 36.8523 36.6680 37.7245 37.5359 38.5983 38.4053 39.4737 39.2763 40.3506 40.1489 41.2290 41.0229 42.1089 41.8983 42.9901 42.7752 43.8727 43.6534 44.7566 44.5329 45.6418 45.4136 46.5283 46.2957 47.4160 47.1789 48.3049 48.0633 49.1949 48.9489 50.0861 49.8356 50.9783 50.7234 51.8717 51.6123 52.7661 52.5022 53.6615 53.3932 54.5579 54.2851 1.0% 36.1086 35.7475 37.0042 36.6342 37.9014 37.5224 38.8001 38.4121 39.7003 39.3033 40.6019 40.1959 41.5049 41.0898 42.4092 41.9851 43.3149 42.8817 44.2218 43.7795 45.1299 44.6786 46.0392 45.5788 46.9497 46.4802 47.8613 47.3827 48.7740 48.2863 49.6878 49.1909 50.6026 50.0966 51.5185 51.0033 52.4353 51.9109 53.3531 52.8196 54.2718 53.7291 55.1915 54.6396 56.1120 55.5509 57.0335 56.4631 2.0% 38.3916 37.6238 39.3227 38.5363 40.2551 39.4500 41.1889 40.3651 42.1238 41.2813 43.0600 42.1988 43.9973 43.1174 44.9358 44.0371 45.8754 44.9579 46.8160 45.8797 47.7577 46.8026 48.7004 47.7264 49.6441 48.6512 50.5887 49.5769 51.5342 50.5036 52.4807 51.4311 53.4280 52.3594 54.3762 53.2887 55.3252 54.2187 56.2750 55.1495 57.2256 56.0811 58.1770 57.0134 59.1291 57.9465 60.0820 58.8803 4.0% 41.3580 39.7036 42.3363 40.6428 43.3157 41.5831 44.2962 42.5243 45.2776 43.4665 46.2600 44.4098 47.2434 45.3538 48.2278 46.2985 49.2127 47.2442 50.1987 48.1907 51.1854 49.1380 52.1730 50.0861 53.1613 51.0349 54.1504 51.9844 55.1403 52.9346 56.1308 53.8856 57.1220 54.8371 58.1139 55.7893 59.1064 58.7422 60.0996 57.8956 61.0934 58.6496 62.0878 59.6042 63.0827 60.5594 64.0783 61.5151 5.0% 42.5369 40.4100 43.5345 41.3578 44.5331 42.3064 45.5326 43.2559 46.5330 44.2063 47.5343 45.1576 48.5364 46.1096 49.5394 47.0624 50.5431 48.0160 51.5477 48.9703 52.5529 49.9253 53.5589 50.8810 54.5656 51.8373 55.5730 52.7943 56.5810 53.7519 57.5897 54.7102 58.5989 55.6690 59.6088 56.6284 60.6193 57.5883 61.6304 58.5488 62.6420 59.5099 63.6541 60.4714 64.6668 61.4335 65.6800 62.3960
A4
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 46.1881 46.1835 46.9956 46.9909 47.8046 47.7998 48.6150 48.6101 49.4268 49.4218 50.2399 50.2349 51.0544 51.0493 51.8701 51.8650 52.6872 52.6819 53.5055 53.5002 54.3251 54.3197 55.1458 55.1403 55.9678 55.9622 56.7909 56.7852 57.6152 57.6094 58.4406 58.4347 59.2671 59.2611 60.0946 60.0886 60.9233 60.9172 61.7530 61.7468 62.5837 62.5775 63.4155 63.4091 64.2482 64.2418 65.0819 65.0754 0.1% 50.9444 50.8935 51.7987 51.7469 52.6542 52.6015 53.5108 53.4573 54.3685 54.3142 55.2274 55.1722 56.0873 56.0313 56.9483 56.8914 57.8104 57.7526 58.6734 58.6147 59.5375 59.4779 60.4025 60.3421 61.2685 61.2072 62.1354 62.0733 63.0033 62.9403 63.8721 63.8082 64.7417 64.6770 65.6123 65.5467 66.4837 66.4172 67.3559 67.2886 68.2290 68.1608 69.1029 69.0338 69.9776 69.9076 70.8531 70.7822 0.5% 55.4554 55.1781 56.3537 56.0720 57.2530 56.9668 58.1533 57.8625 59.0544 58.7591 59.9564 59.6566 60.8593 60.5550 61.7630 61.4542 62.6676 62.3542 63.5729 63.2551 64.4791 64.1567 65.3860 65.0591 66.2937 65.9622 67.2021 66.8661 68.1113 67.7708 69.0212 68.6761 69.9318 69.5822 70.8431 70.4889 71.7551 71.3963 72.6677 72.3044 73.5811 73.2132 74.4950 74.1225 75.4096 75.0326 76.3248 75.9432 1.0% 57.9558 57.3762 58.8789 58.2901 59.8028 59.2048 60.7276 60.1203 61.6531 61.0366 62.5794 61.9536 63.5065 62.8714 64.4343 63.7899 65.3628 64.7091 66.2920 65.8290 67.2219 66.5496 68.1524 67.4709 69.0837 68.3928 70.0156 69.3154 70.9481 70.2386 71.8812 71.1624 72.8150 72.0868 73.7494 73.0119 74.6843 73.9375 75.6198 74.8636 76.5560 75.7904 77.4926 76.7177 78.4298 77.6455 79.3676 78.5739 2.0% 61.0355 59.8148 61.9898 60.7500 62.9448 61.6859 63.9004 62.6224 64.8567 63.5596 65.8136 64.4973 66.7712 65.4357 67.7293 66.3747 68.6881 67.3143 69.6474 68.2545 70.6073 69.1952 71.5678 70.1364 72.5288 71.0783 73.4904 72.0206 74.4525 72.9634 75.4151 73.9068 76.3782 74.8506 77.3418 75.7950 78.3059 76.7398 79.2705 77.6851 80.2356 78.6309 81.2011 79.5771 82.1671 80.5237 83.1335 81.4708 4.0% 65.0744 62.4714 66.0710 63.4282 67.0682 64.3855 68.0659 65.3432 69.0641 66.3015 70.0628 67.2603 71.0619 68.2195 72.0616 69.1791 73.0617 70.1392 74.0622 71.0998 75.0632 72.0607 76.0647 73.0221 77.0665 73.9839 78.0688 74.9460 79.0715 75.9086 80.0745 76.8716 81.0780 77.8349 82.0818 78.7986 83.0861 79.7626 84.0906 80.7270 85.0956 81.6917 86.1009 82.6568 87.1065 83.6222 88.1125 84.5880 5.0% 66.6937 63.3590 67.7079 64.3225 68.7225 65.2864 69.7377 66.2508 70.7532 67.2156 71.7693 68.1808 72.7857 69.1464 73.8026 70.1125 74.8199 71.0789 75.8376 72.0457 76.8557 73.0129 77.8742 73.9805 78.8930 74.9484 79.9123 75.9167 80.9319 76.8853 81.9518 77.8542 82.9721 78.8235 83.9927 79.7931 85.0137 80.7630 86.0350 81.7333 87.0566 82.7038 88.0786 83.6746 89.1008 84.6458 90.1233 85.6172
A5
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 65.9166 65.9100 66.7522 66.7456 67.5888 67.5820 68.4263 68.4194 69.2647 69.2578 70.1040 70.0970 70.9441 70.9370 71.7852 71.7780 72.6270 72.6198 73.4698 73.4624 74.3133 74.3059 75.1577 75.1501 76.0028 75.9952 76.8488 76.8411 77.6955 77.6878 78.5430 78.5352 79.3913 79.3834 80.2403 80.2323 81.0901 81.0820 81.9405 81.9324 82.7917 82.7835 83.6437 83.6353 84.4963 84.4878 85.3496 85.3410 0.1% 71.7294 71.6576 72.6064 72.5338 73.4842 73.4107 74.3627 74.2884 75.2420 75.1667 76.1220 76.0458 77.0026 76.9258 77.8840 77.8061 78.7661 78.6873 79.6488 79.5692 80.5322 80.4517 81.4163 81.3349 82.3010 82.2187 83.1863 83.1031 84.0723 83.9882 84.9588 84.8739 85.8460 85.7602 86.7338 86.6471 87.6222 87.5346 88.5112 88.4227 89.4007 89.3113 90.2908 90.2005 91.1815 91.0903 92.0727 91.9806 0.5% 77.2407 76.8545 78.1571 77.7663 79.0741 78.6787 79.9917 79.5918 80.9099 80.5054 81.8287 81.4195 82.7480 82.3342 83.6678 83.2495 84.5882 84.1653 85.5092 85.0816 86.4306 85.9985 87.3526 86.9158 88.2750 87.8337 89.1980 88.7520 90.1215 89.6709 91.0454 90.5902 91.9698 91.5100 92.8947 92.4303 93.8201 93.3510 94.7459 94.2722 95.6722 95.1938 96.5989 96.1159 97.5260 97.0384 98.4536 97.9613 1.0% 80.3059 79.5028 81.2447 80.4322 82.1840 81.3622 83.1238 82.2926 84.0642 83.2235 85.0050 84.1549 85.9463 85.0868 86.8880 86.0191 87.8303 86.9519 88.7729 87.8852 89.7161 88.8189 90.6597 89.7531 91.6037 90.6876 92.5481 91.6226 93.4930 92.5580 94.4383 93.4939 95.3840 94.4301 96.3301 95.3668 97.2766 96.3038 98.2235 97.2412 99.1707 98.1790 100.1184 99.1172 101.0664 100.0558 102.0148 100.9947 2.0% 84.1003 82.4183 85.0676 83.3663 86.0353 84.3146 87.0035 85.2634 87.9720 86.2125 88.9409 87.1621 89.9102 88.1120 90.8800 89.0624 91.8500 90.0130 92.8205 90.9641 93.7914 91.9155 94.7626 92.8673 95.7341 93.8194 96.7060 94.7719 97.6783 95.7247 98.6509 96.6779 99.6238 97.6313 100.5971 98.5851 101.5707 99.5393 102.5446 100.4937 103.5188 101.4484 104.4934 102.4035 105.4682 103.3588 105.4434 104.3145 4.0% 89.1188 85.5540 90.1254 86.5204 91.1324 87.4871 92.1396 88.4540 93.1472 89.4213 94.1551 90.3889 95.1633 91.3567 96.1717 92.3249 97.1805 93.2933 98.1895 94.2619 99.1988 95.2309 100.2084 96.2001 101.2183 97.1696 102.2284 98.1393 103.2388 99.1093 104.2494 100.0795 105.2603 101.0499 106.2715 102.0206 107.2829 102.9915 108.2945 103.9627 109.3063 104.9341 110.3184 105.9057 111.3308 106.8775 112.3433 107.8476 5.0% 91.1462 86.5889 92.1693 87.5608 93.1927 88.5331 94.2164 89.5056 95.2404 90.4784 96.2646 91.4514 97.2891 92.4247 98.3139 93.3982 99.3389 94.3719 100.3642 95.3460 101.3897 96.3202 102.4154 97.2947 103.4414 98.2694 104.4677 99.2443 105.4941 100.2194 106.5208 101.1948 107.5477 102.1703 108.5748 103.1461 109.6022 104.1221 110.6297 105.0983 111.6575 106.0748 112.6855 107.0512 113.7136 108.0280 114.7420 109.0049
A6
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 86.2036 86.1949 87.0582 87.0495 87.9135 87.9047 88.7695 88.7606 89.6261 89.6172 90.4834 90.4743 91.3413 91.3322 92.1998 92.1906 93.0589 93.0496 93.9187 93.9093 94.7790 94.7696 95.6400 95.6304 96.5015 96.4919 97.3636 97.3539 98.2263 98.2165 99.0896 99.0797 99.9534 99.9434 100.8178 100.8077 101.6827 101.6725 102.5481 102.5379 103.4141 103.4038 104.2807 104.2702 105.1477 105.1372 106.0153 106.0047 0.1% 92.9645 92.8715 93.8568 93.7629 94.7496 94.6549 95.6430 95.5473 96.5369 96.4403 97.4312 97.3338 98.3261 98.2278 99.2215 99.1223 100.1174 100.0173 101.0138 100.9128 101.9106 101.8087 102.8080 102.7052 103.7058 103.6021 104.6040 104.4994 105.5028 105.3972 106.4019 106.2955 107.3015 107.1942 108.2016 108.0934 109.1021 108.9930 110.0030 109.8930 110.9044 110.7935 111.8062 111.6944 112.7084 112.5957 113.6110 113.4974 0.5% 99.3816 98.8847 100.3100 99.8085 101.2389 100.7327 102.1681 101.6573 103.0978 102.5823 104.0279 103.5077 104.9583 104.4335 105.8892 105.3597 106.8204 106.2863 107.7520 107.2132 108.6840 108.1405 109.6163 109.0682 110.5490 109.9963 111.4821 110.9247 112.4155 111.8534 113.3493 112.7826 114.2834 113.7120 115.2179 114.6418 116.1527 115.5720 117.0879 116.5024 118.0234 117.4332 118.9592 118.3644 119.8953 119.2958 120.8318 120.2276 1.0% 102.9638 101.9340 103.9128 102.8736 104.8622 103.8136 105.8121 104.7540 106.7623 105.6947 107.7128 106.6357 108.6637 107.5771 109.6149 108.5187 110.5664 109.4608 111.5183 110.4031 112.4705 111.3458 113.4230 112.2887 114.3758 113.2320 115.3289 114.1756 116.2823 115.1195 117.2360 116.0637 118.1900 117.0081 119.1443 117.9529 120.0989 118.8980 121.0538 119.8433 122.0090 120.7889 122.9645 121.7348 123.9202 122.6810 124.8762 123.8274 2.0% 107.4188 105.2704 108.3945 106.2267 109.3706 107.1832 110.3469 108.1400 111.3235 109.0970 112.3004 110.0544 113.2775 111.0120 114.2549 111.9698 115.2326 112.9280 116.2106 113.8864 117.1888 114.8450 118.1673 115.8039 119.1460 116.7631 120.1250 117.7225 121.1042 118.6821 122.0836 119.6420 123.0633 120.6021 124.0433 121.5624 125.0234 122.5230 126.0038 123.4838 126.9845 124.4448 127.9653 125.4060 128.9464 126.3675 129.9277 127.3292 4.0% 113.3561 108.8218 114.3691 109.7943 115.3823 110.7670 116.3957 111.7398 117.4093 112.7129 118.4231 113.6862 119.4372 114.6597 120.4514 115.6333 121.4658 116.6072 122.4805 117.5812 123.4953 118.5555 124.5103 119.5299 125.5255 120.5045 126.5409 121.4792 127.5564 122.4542 128.5722 123.4293 129.5881 124.4045 130.6042 125.3800 131.6204 126.3556 132.6369 127.3314 133.6535 128.3073 134.6702 129.2834 135.6872 130.2597 136.7043 131.2361 5.0% 115.7706 109.9821 116.7993 110.9594 117.8283 111.9369 118.8574 112.9146 119.8868 113.8924 120.9163 114.8704 121.9459 115.8486 122.9758 116.8270 124.0058 117.8055 125.0360 118.7842 126.0664 119.7631 127.0970 120.7421 128.1277 121.7213 129.1585 122.7006 130.1896 123.6801 131.2207 124.6597 132.2521 125.6395 133.2836 126.6194 134.3152 127.5994 135.3470 128.5796 136.3789 129.5600 137.4110 130.5405 138.4432 131.5211 139.4756 132.5018
A7
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 112.9739 112.9626 106.8834 106.8727 107.7520 107.7412 108.6211 108.6102 109.4906 109.4797 110.3607 110.3497 111.2313 111.2202 112.1024 112.0911 113.8459 113.8345 114.7184 114.7069 115.5913 115.5797 116.4647 116.4530 117.3385 117.3268 118.2128 118.2010 119.0875 119.0756 119.9627 119.9507 120.8383 120.8262 121.7144 121.7022 122.5908 122.5788 123.4877 123.4554 124.3450 124.3326 125.2228 125.2102 126.1009 126.0883 126.9795 126.9668 0.1% 120.8482 120.7253 114.5140 114.3995 115.4174 115.3020 116.3212 116.2049 117.2255 117.1082 118.1301 118.0119 119.0351 118.9160 119.9404 119.8205 121.7523 121.6306 122.6588 122.5362 123.5657 123.4421 124.4729 124.3485 125.3805 125.2551 126.2885 126.1622 127.1968 127.0696 128.1054 127.9773 129.0144 128.8854 129.9238 129.7938 130.8335 130.7028 131.7435 131.6117 132.6538 132.5212 133.5645 133.4309 134.4755 134.3410 135.3868 135.2514 0.5% 128.3345 127.6928 121.7685 121.1597 122.7056 122.0921 123.6430 123.0248 124.5807 123.9578 125.5187 124.8911 126.4570 125.8247 127.3956 126.7586 129.2737 128.6273 130.2131 129.5621 131.1529 130.4971 132.0929 131.4325 133.0332 132.3681 133.9738 133.3040 134.9147 134.2401 135.8558 135.1765 136.7972 136.1132 137.7389 137.0502 138.6808 137.9874 139.6230 138.9249 140.5654 139.8628 141.5081 140.8006 142.4510 141.7388 143.3942 142.6773 1.0% 132.5337 131.2083 125.8325 124.5741 126.7890 125.5211 127.7458 126.4683 128.7029 127.4158 129.6602 128.3636 130.6178 129.3116 131.5756 130.2598 133.4920 132.1571 134.4506 133.1061 135.4094 134.0553 136.3684 135.0047 137.3277 135.9544 138.2872 136.9044 139.2470 137.8545 140.2070 138.8049 141.1672 139.7555 142.1276 140.7063 143.0883 141.6574 144.0491 142.6086 145.0102 143.5601 145.9715 144.5118 146.9330 145.4637 147.8948 146.4158 2.0% 137.7858 135.0301 130.9092 128.2911 131.8910 129.2532 132.8729 130.2155 133.8551 131.1780 134.8375 132.1407 135.8200 133.1036 136.8028 134.0667 138.7690 135.9936 139.7523 136.9573 140.7359 137.9212 141.7196 138.8852 142.7036 139.8495 143.6877 140.8140 144.6720 141.7786 145.6565 142.7434 146.6412 143.7084 147.6261 144.6736 148.6111 145.6389 149.5963 146.6044 150.5817 147.5701 151.5673 148.5360 152.5530 149.5020 153.5389 150.4682 4.0% 144.8466 139.0527 137.7215 132.2126 138.7389 133.1894 139.7565 134.1662 140.7742 135.1432 141.7921 136.1204 142.8101 137.0977 143.8282 138.0751 145.8650 140.0304 146.8836 141.0083 147.9024 141.9863 148.9212 142.9644 149.9403 143.9426 150.9594 144.9210 151.9787 145.8995 152.9981 146.8782 154.0177 147.8570 155.0374 148.8359 156.0572 149.8149 157.0771 150.7940 158.0972 151.7733 159.1174 152.7527 160.1377 153.7322 161.1581 154.7118 5.0% 147.7394 140.3525 140.5081 133.4827 141.5408 134.4637 142.5736 135.4449 143.6065 136.4261 144.6395 137.4075 145.6727 138.3891 146.7060 139.3707 148.7730 141.3343 149.8067 142.3164 150.8405 143.2985 151.8744 144.2807 152.9085 145.2631 153.9426 146.2455 154.9769 147.2281 156.0113 148.2108 157.0459 149.1936 158.0805 150.1765 159.1152 151.1595 160.1501 152.1426 161.1850 153.1258 162.2201 154.1091 163.2553 155.0925 164.2906 156.0760
A8
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 127.8584 127.8456 128.7378 128.7249 129.6175 129.6045 130.4976 130.4846 131.3782 131.3650 132.2591 132.2459 133.1404 133.1271 134.0221 134.0087 134.9041 134.8906 135.7865 135.7730 136.6693 136.6557 137.5525 137.5387 138.4360 138.4222 139.3199 139.3060 140.2041 140.1901 141.0887 141.0746 141.9737 141.9595 142.8590 142.8447 143.7446 143.7302 144.6306 144.6161 145.5169 145.5023 146.4035 146.3889 147.2905 147.2758 148.1778 148.1630 0.1% 136.2985 136.1622 137.2104 137.0732 138.1227 137.9846 139.0353 138.8962 139.9482 139.8082 140.8614 140.7205 141.7749 141.6331 142.6887 142.5460 143.6028 143.4592 144.5172 144.3727 145.4319 145.2864 146.3468 146.2005 147.2621 147.1148 148.1776 148.0295 149.0935 148.9444 150.0096 149.8596 150.9260 150.7750 151.8426 151.6908 152.7595 152.6068 153.6768 153.5231 154.5942 154.4396 155.5120 155.3564 156.4299 156.2735 157.3482 157.1909 0.5% 144.3377 143.6160 145.2814 144.5549 146.2253 145.4942 147.1694 146.4336 148.1138 147.3733 149.0585 148.3132 150.0033 149.2533 150.9484 150.1937 151.8938 151.1343 152.8393 152.0751 153.7851 153.0162 154.7311 153.9574 155.6773 154.8989 156.6237 155.8406 157.5704 156.7825 158.5172 157.7247 159.4643 158.6670 160.4116 159.6096 161.3591 160.5523 162.3068 161.4953 163.2547 162.4385 164.2028 163.3818 165.1511 164.3254 166.0997 165.2692 1.0% 148.8567 147.3681 149.8189 148.3207 150.7812 149.2734 151.7438 150.2263 152.7065 151.1795 153.6695 152.1328 154.6326 153.0863 155.5960 154.0400 156.5595 154.9939 157.5232 155.9480 158.4872 156.9023 159.4513 157.8567 160.4156 158.8114 161.3800 159.7662 162.3447 160.7212 163.3095 161.6764 164.2746 162.6318 165.2397 163.5874 166.2051 164.5431 167.1707 165.4990 168.1364 166.4550 169.1023 167.4113 170.0684 168.3677 171.0346 169.3242 2.0% 154.5250 151.4345 155.5112 152.4010 156.4976 153.3677 157.4842 154.3345 158.4709 155.3015 159.4578 156.2686 160.4448 157.2359 161.4320 158.2034 162.4194 159.1710 163.4069 160.1387 164.3945 161.1066 165.3823 162.0747 166.3702 163.0428 167.3583 164.0112 168.3466 164.9796 169.3350 165.9483 170.3235 166.9170 171.3121 167.8859 172.3009 168.8549 173.2899 169.8241 174.2790 170.7934 175.2682 171.7628 176.2575 172.7324 177.2470 173.7021 4.0% 162.1787 155.6915 163.1993 156.6713 164.2201 157.6513 165.2410 158.6314 166.2620 159.6116 167.2832 160.5918 168.3044 161.5722 169.3258 162.5527 170.3472 163.5334 171.3688 164.5141 172.3905 165.4949 173.4123 166.4758 174.4342 167.4568 175.4562 168.4380 176.4783 169.4192 177.5005 170.4005 178.5228 171.3819 179.5452 172.3634 180.5678 173.3450 181.5904 174.3268 182.6131 175.3086 183.6359 176.2904 184.6588 177.2724 185.6818 178.2545 5.0% 165.3260 157.0597 166.3615 158.0434 167.3970 159.0272 168.4327 160.0111 169.4685 160.9951 170.5044 161.9792 171.5404 162.9634 172.5765 163.9477 173.6127 164.9320 174.6490 165.9165 175.6853 166.9011 176.7218 167.8857 177.7583 168.8704 178.7950 169.8552 179.8317 170.8401 180.8686 171.8251 181.9055 172.8102 182.9425 173.7953 183.9795 174.7806 185.0167 175.7659 186.0540 176.7513 187.0913 177.7367 188.1287 178.7223 189.1662 179.7079
A9
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 149.0655 149.0506 149.9535 149.9385 150.8418 150.8267 151.7304 151.7152 152.6193 152.6040 153.5086 153.4932 154.3981 154.3827 155.2880 155.2725 156.1782 156.1625 157.0686 157.0529 157.9594 157.9436 158.8505 158.8346 159.7419 159.7259 160.6336 160.6175 161.5256 161.5094 162.4178 162.4016 163.3104 163.2941 164.2032 164.1868 165.0964 165.0798 165.9898 165.9732 166.8835 166.8668 167.7774 167.7607 168.6717 168.6548 169.5662 169.5493 0.1% 158.2667 158.1085 159.1855 159.0263 160.1045 159.9444 161.0238 160.8628 161.9433 161.7814 162.8631 162.7002 163.7831 163.6194 164.7034 164.5387 165.6239 165.4583 166.5447 166.3781 167.4657 167.2982 168.3869 168.2185 169.3084 169.1390 170.2301 170.0598 171.1520 170.9808 172.0741 171.9021 172.9965 172.8235 173.9191 173.7452 174.8420 174.6671 175.7650 175.5893 176.6883 176.5116 177.6118 177.4342 178.5355 178.3570 179.4595 179.2800 0.5% 167.0484 166.2131 167.9973 167.1573 168.9464 168.1017 169.8957 169.0462 170.8452 169.9909 171.7948 170.9359 172.7447 171.8810 173.6948 172.8263 174.6450 173.7718 175.5954 174.7174 176.5460 175.6833 177.4968 176.6093 178.4478 177.5555 179.3989 178.5019 180.3502 179.4485 181.3017 180.3952 182.2534 181.3421 183.2052 182.2892 184.1572 183.2364 185.1094 184.1839 186.0618 185.1315 187.0143 186.0792 187.9670 187.0271 188.9198 187.9752 1.0% 172.0010 170.2810 172.9675 171.2379 173.9343 172.1949 174.9012 173.1522 175.8682 174.1095 176.8354 175.0671 177.8028 176.0248 178.7703 176.9826 179.7380 177.9406 180.7059 178.8988 181.6739 179.8571 182.6420 180.8158 183.6103 181.7742 184.5787 182.7330 185.5473 183.6919 186.5161 184.6509 187.4850 185.6101 188.4540 186.5695 189.4232 187.5290 190.3925 188.4886 191.3620 189.4483 192.3316 190.4083 193.3013 191.3683 194.2712 192.3285 2.0% 178.2366 174.6719 179.2264 175.6419 180.2153 176.6119 181.2063 177.5821 182.1964 178.5525 183.1867 179.5229 184.1771 180.4935 185.1676 181.4642 186.1582 182.4350 187.1490 183.4060 188.1398 184.3770 189.1308 185.3482 190.1219 186.3195 191.1132 187.2909 192.1045 188.2624 193.0960 189.2341 194.0876 190.2058 195.0793 191.1777 196.0711 192.1497 197.0630 193.1218 198.0551 194.0940 199.0472 195.0663 200.0395 196.0387 201.0318 197.0112 4.0% 186.7049 179.2367 187.7280 180.2189 188.7513 181.2013 189.7747 182.1837 190.7981 183.1662 191.8217 184.1488 192.8453 185.1315 193.8690 186.1143 194.8929 187.0971 195.9168 188.0801 196.9407 189.0631 197.9648 190.0482 198.9890 191.0294 200.0132 192.0127 201.0375 192.9960 202.0619 193.9794 203.0864 194.9829 204.1109 195.9465 205.1356 196.9302 206.1603 197.9139 207.1851 198.8977 208.2100 199.8816 209.2349 200.8655 210.2599 201.8495 5.0% 190.2038 180.6936 191.2415 181.6794 192.2792 182.6653 193.3170 183.6512 194.3549 184.6372 195.3929 185.6233 196.4310 186.6094 197.4691 187.5957 198.5073 188.5820 199.5456 189.5683 200.5839 190.5548 201.6224 191.5413 202.6609 192.5278 203.6994 193.5145 204.7381 194.5012 205.7768 195.4880 206.8156 198.4748 207.8544 197.4617 208.8933 198.4487 209.9323 199.4357 210.9714 200.4228 212.0105 201.4100 213.0497 202.3972 214.0889 203.3845
A10
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 170.4610 170.4440 171.3561 171.3390 172.2514 172.2342 173.1470 173.1297 174.0429 174.0255 174.9391 174.9216 175.8354 175.8179 176.7321 176.7144 177.6290 177.6113 178.5262 178.5083 179.4236 179.4057 180.3213 180.3033 181.2192 181.2011 182.1174 182.0992 183.0158 182.9975 183.9145 183.8961 184.8134 184.7950 185.7126 185.6940 186.6120 186.5933 187.5117 187.4929 188.4115 188.3927 189.3116 189.2927 190.2120 190.1930 191.1126 191.0935 0.1% 180.3836 180.2032 181.3080 181.1267 182.2326 182.0503 183.1573 182.9742 184.0823 183.8983 185.0075 184.8225 185.9329 185.7470 188.8585 186.6717 187.7844 187.5966 188.7104 188.5217 189.6366 189.4469 190.5630 190.3724 191.4896 191.2981 192.4164 192.2240 193.3434 193.1501 194.2706 194.0763 195.1980 195.0028 196.1256 195.9294 197.0533 196.8563 197.9813 197.7833 198.9094 198.7105 199.8377 199.6379 200.7662 200.5655 201.6949 201.4932 0.5% 189.8728 188.9235 190.8260 189.8719 191.7793 190.8204 192.7328 191.7691 193.6865 192.7180 194.6403 193.6671 195.5942 194.6163 196.5484 195.5658 197.5026 196.5151 198.4571 197.4648 199.4116 198.4146 200.3664 199.3645 201.3212 200.3146 202.2763 201.2649 203.2314 202.2153 204.1868 203.1658 205.1422 204.1165 206.0978 205.0673 207.0536 206.0183 208.0095 206.9694 208.9655 207.9207 209.9217 208.8721 210.8780 209.8236 211.8345 210.7753 1.0% 195.2412 193.2888 196.2114 194.2492 194.1816 195.2098 198.1521 196.1705 199.1226 197.1314 200.0933 198.0924 201.0641 199.0535 202.0351 200.0147 203.0061 200.9761 203.9774 201.9376 204.9487 202.8992 205.9201 203.8609 206.8917 204.8228 207.8634 205.7848 208.8353 206.7469 209.8072 207.7091 210.7793 208.6715 211.7515 209.6340 212.7238 210.5966 213.6962 211.5593 214.6688 212.5221 215.6415 213.4850 216.6143 214.4481 217.5872 215.4113 2.0% 202.0243 197.9838 203.0169 198.9585 204.0096 199.9294 205.0023 200.9023 205.9952 201.8753 206.9882 202.8485 207.9813 203.8217 208.9745 204.7950 209.9678 205.7685 210.9612 206.7420 211.9547 207.7157 212.9483 208.6894 213.9421 209.6632 214.9358 210.6371 215.9297 211.6111 216.9237 212.5853 217.9178 213.5595 218.9120 214.5338 219.9063 215.5081 220.9006 216.4826 221.8951 217.4572 222.8897 218.4319 223.8843 219.4066 224.8790 220.3814 4.0% 211.2850 202.8336 212.3102 203.8178 213.3355 204.8021 214.3608 205.7864 215.3862 206.7707 216.4117 207.7552 217.4372 208.7397 218.4628 209.7243 219.4885 210.7090 220.5143 211.6937 221.5401 212.6785 222.5660 213.6633 223.5919 214.6483 224.6180 215.6332 225.6441 216.6183 226.6702 217.6034 227.6965 218.5886 228.7227 219.5738 229.7491 220.5591 230.7755 221.5445 231.8020 222.5299 232.8286 223.5154 233.8552 224.5010 234.8819 225.4866 5.0% 215.1283 204.3718 216.1676 205.3593 217.2071 206.3467 218.2466 207.3343 219.2862 208.3218 220.3258 209.3095 221.3655 210.2972 222.4052 211.2850 223.4450 212.2728 224.4849 213.2607 225.5248 214.2486 226.5648 215.2366 227.6049 216.2246 228.6450 217.2128 229.6852 218.2009 230.7254 219.1981 231.7657 220.1774 232.8060 221.1657 233.8464 222.1541 234.8868 223.1425 235.9273 224.1310 236.9679 225.1195 238.0085 226.1081 239.0492 227.0967
A11
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 192.0134 191.9942 192.9145 192.8952 193.8157 193.7963 194.7172 194.6978 195.6190 195.5994 196.5209 196.5013 197.4231 197.4034 198.3255 198.3057 199.2281 199.2082 200.1310 200.1109 201.0340 201.0139 201.9373 201.9171 202.8408 202.8205 203.7445 203.7241 204.6484 204.6279 205.5525 205.5320 206.4568 206.4362 207.3614 207.3407 208.2661 208.2453 209.1711 209.1502 210.0763 210.0553 210.9816 210.9605 211.8872 211.8660 212.7930 212.7717 0.1% 202.6238 202.4212 203.5528 203.3493 204.4821 204.2776 205.4115 205.2061 206.3411 206.1347 207.2708 207.0636 208.2008 207.9926 209.1309 208.9218 210.0612 209.8511 210.9916 210.7806 211.9222 211.7103 212.8530 212.6402 213.7840 213.5702 214.7151 214.5004 215.6484 215.4308 216.5779 216.3613 217.5095 217.2920 218.4413 218.2228 219.3732 219.1539 220.3053 220.0850 221.2376 221.0164 222.1700 221.9479 223.1026 222.8795 224.0354 223.8113 0.5% 212.7911 211.7271 213.7478 212.6790 214.7046 213.6311 215.6616 214.5833 216.6188 215.5357 217.5760 216.4882 218.5334 217.4408 219.4910 218.3935 220.4486 219.3464 221.4064 220.2994 222.3643 221.2525 223.3224 222.2058 224.2806 223.1591 225.2388 224.1127 226.1973 225.0663 227.1558 226.0200 228.1145 226.9739 229.0733 227.9279 230.0322 228.8820 230.9912 229.8383 231.9504 230.7906 232.9097 231.7451 233.8691 232.6997 234.8286 233.6544 1.0% 218.5602 218.3746 219.5333 217.3380 220.5066 218.3015 221.4799 219.2651 222.4534 220.2288 223.4270 221.1927 224.4007 222.1566 225.3745 223.1207 226.3484 224.0849 227.3224 225.0492 228.2965 226.0135 229.2707 226.9780 230.2451 227.9426 231.2195 228.9073 232.1941 229.8721 233.1687 230.8370 234.1435 231.8020 235.1183 232.7671 236.0933 233.7323 237.0683 234.6977 238.0435 235.6631 239.0188 236.6288 239.9941 237.5942 240.9696 238.5599 2.0% 225.8739 221.3564 226.8688 222.3314 227.8638 223.3065 228.8589 224.2817 229.8540 225.2569 230.8493 226.2323 231.8446 227.2077 232.8401 228.1833 233.8356 229.1589 234.8312 230.1346 235.8269 231.1103 236.8226 232.0862 237.8185 233.0621 238.8144 234.0381 239.8104 235.0142 240.8065 235.9904 241.8027 236.9667 242.7990 237.9430 243.7953 238.9194 244.7917 239.8959 245.7882 240.8724 246.7848 241.8491 247.7814 242.8258 248.7781 243.8026 4.0% 235.9086 226.4723 236.9354 227.4580 237.9623 228.4436 238.9892 229.4296 240.0162 230.4155 241.0432 231.4015 242.0703 232.3875 243.0975 233.3736 244.1247 234.3597 245.1520 235.3459 246.1793 236.3321 247.2067 237.3184 248.2341 238.3048 249.2616 239.2912 250.2892 240.2776 251.3168 241.2641 252.3445 242.2507 253.3722 243.2373 254.4000 244.2240 255.4278 245.2107 256.4557 246.1975 257.4836 247.1843 258.5116 248.1712 259.5397 249.1581 5.0% 240.0899 228.0854 241.1307 229.0741 242.1715 230.0629 243.2123 231.0517 244.2533 232.0406 245.2942 233.0295 246.3353 234.0185 247.3763 235.0075 248.4175 235.9966 249.4586 236.9857 250.4999 237.9749 251.5411 238.9641 252.5824 239.9533 253.6238 240.9426 254.6652 241.9320 255.7067 242.9213 258.7482 243.9103 257.7897 244.9003 258.8313 245.8898 259.8730 246.8793 260.9147 247.8689 261.9564 248.8586 262.9982 249.8483 264.0400 250.8380
A12
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 213.6989 213.6776 214.6051 214.5836 215.5115 215.4899 216.4180 216.3964 217.3248 217.3030 218.2317 218.2099 219.1389 219.1170 220.0462 220.0242 220.9537 220.9316 221.8614 221.8393 222.7694 222.7471 223.6774 223.6551 224.5857 224.5633 225.4942 225.4716 226.4028 226.3802 227.3117 227.2889 228.2207 228.1979 229.1299 229.1070 230.0393 230.0162 230.9488 230.9257 231.8585 231.8354 232.7685 232.7452 233.6785 233.6552 234.5888 234.5653 0.1% 224.9683 224.7433 225.9013 225.6754 226.8345 226.6077 227.7679 227.5401 228.7014 228.4727 229.6351 229.4054 230.5689 230.3383 231.5029 231.2714 232.4370 232.2045 233.3712 233.1379 234.3056 234.0713 235.2402 235.0050 236.1749 235.9387 237.1098 236.8726 238.0447 237.8067 238.9799 238.7409 239.9152 239.6752 240.8506 240.6097 241.7861 241.5444 242.7218 242.4791 243.6577 243.4140 244.5936 244.3491 245.5298 245.2842 246.4680 246.2195 0.5% 235.7882 234.6093 236.7480 235.5642 237.7078 236.5193 238.6678 237.4745 239.6279 238.4298 240.5881 239.3852 341.5485 240.3407 242.5089 241.2963 243.4694 242.2521 244.4301 243.2080 245.3909 244.1639 246.3518 245.1200 247.3127 246.0762 248.2738 247.0325 249.2351 247.9889 250.1964 248.9454 251.1578 249.9020 252.1193 250.8587 253.0809 251.8155 254.0427 252.7725 255.0045 253.7295 255.9665 254.6866 256.9285 255.6439 257.8907 256.6012 1.0% 241.9451 239.5257 242.9208 240.4916 243.8965 241.4576 244.8724 242.4237 245.8483 243.3898 246.8244 244.3581 247.8005 245.3225 248.7767 246.2889 249.7530 247.2555 250.7294 248.2221 251.7059 249.1889 252.6825 250.1557 253.6592 251.1226 254.6360 252.0896 255.6129 253.0567 256.5898 254.0239 257.5669 254.9912 258.5440 255.9585 259.5212 256.9260 260.4985 257.8935 261.4759 258.8611 262.4534 259.8288 263.4309 260.7966 264.4086 261.7645 2.0% 249.7749 244.7794 250.7718 245.7564 251.7687 248.7334 252.7658 247.7105 253.7629 248.6875 254.7600 249.6648 255.7573 250.6421 256.7546 251.6195 257.7520 252.5969 258.7494 253.5744 259.7470 254.5520 260.7445 255.5297 261.7422 256.5074 262.7400 257.4852 263.7378 258.4630 264.7357 259.4409 265.7336 260.4189 266.7316 261.3970 267.7297 262.3751 268.7279 263.3533 269.7261 264.3316 270.7244 265.3099 271.7227 266.2883 272.7211 267.2667 4.0% 260.5678 250.1451 261.5959 251.1321 262.6241 252.1192 263.6524 253.1063 264.6807 254.0934 265.7090 255.0807 266.7374 256.0679 267.7659 257.0552 268.7944 258.0426 269.8229 259.0300 270.8515 260.0175 271.8802 261.0050 272.9089 261.9925 273.9376 262.9801 274.9664 263.9677 275.9952 264.9554 277.0241 265.9431 278.0530 266.9309 279.0820 267.9187 280.1110 268.9066 281.1401 269.8945 282.1692 270.8824 283.1983 271.8704 284.2275 272.8584 5.0% 265.0819 251.8278 266.1238 252.8176 267.1658 253.8075 268.2078 254.7974 269.2498 255.7873 270.2919 258.7773 271.3340 257.7673 272.3762 258.7574 273.4184 259.7475 274.4606 260.7376 275.5029 261.7278 276.5453 262.7180 277.5876 263.7083 278.6301 264.6986 279.6725 265.6889 280.7150 266.6793 281.7575 267.6697 282.8001 268.6601 283.8427 269.6506 284.8854 270.6411 285.9281 271.6316 286.9708 272.6222 288.0135 273.6129 289.0563 274.6035
A13
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 235.4992 235.4757 236.4099 236.3862 237.3206 237.2969 238.2316 238.2078 239.1427 239.1188 240.0540 240.0300 240.9655 240.9414 241.8771 241.8529 242.7889 242.7647 243.7009 243.6765 244.6130 244.5886 245.5253 245.5008 246.4378 246.4132 247.3504 247.3257 248.2632 248.2384 249.1762 249.1512 250.0893 250.0643 251.0025 250.9774 251.9160 251.8908 252.8296 252.8043 253.7433 253.7179 254.6572 254.6317 255.5713 255.5457 258.4855 258.4598 0.1% 247.4024 247.1550 248.3389 248.0906 249.2756 249.0263 250.2124 249.9622 251.1493 250.8981 252.0863 251.8343 253.0235 252.7705 253.9608 253.7069 254.8983 254.6434 255.8359 255.5800 256.7736 256.5168 257.7114 257.4537 258.6494 258.3907 259.5875 259.3279 260.5257 260.2652 261.4640 261.2026 262.4025 262.1401 263.3411 263.0777 264.2798 264.0155 265.2186 264.9534 266.1576 265.8914 267.0967 266.8296 268.0359 267.7678 268.9752 268.7062 0.5% 258.8529 257.5587 259.8153 258.5162 260.7777 259.4739 261.7403 260.4316 262.7030 261.3894 263.6657 262.3474 264.6286 263.3054 265.5915 264.2636 266.5546 265.2218 267.5177 266.1801 268.4810 267.1385 269.4443 268.0971 270.4077 269.0557 271.3713 270.0144 272.3349 270.9732 273.2986 271.9321 274.2624 272.8911 275.2263 273.8502 276.1903 274.8094 277.1544 275.7686 278.1186 276.7280 279.0828 277.6874 280.0472 278.6470 281.0117 279.6066 1.0% 265.3863 262.7325 266.3641 263.7005 267.3420 264.6686 268.3200 265.6368 269.2981 266.6051 270.2762 267.5735 271.2545 268.5419 272.2328 269.5104 273.2112 270.4791 274.1896 271.4477 275.1682 272.4165 276.1468 273.3854 277.1255 274.3543 278.1043 275.3233 279.0832 276.2924 280.0621 277.2615 281.0412 278.2308 282.0203 279.2001 282.9994 280.1694 283.9787 281.1389 284.9580 282.1084 285.9374 283.0780 286.9169 284.0477 287.8985 285.0175 2.0% 273.7196 268.2452 274.7181 269.2238 275.7168 270.2024 276.7154 271.1811 277.7142 272.1599 278.7130 273.1387 279.7118 274.1176 280.7108 275.0965 281.7097 276.0755 282.7088 277.0546 283.7079 278.0337 284.7071 279.0129 285.7063 279.9922 286.7056 280.9715 287.7050 281.9509 288.7044 282.9303 289.7038 283.9098 290.7034 284.8893 291.7030 285.8689 292.7026 286.8486 293.7023 287.8283 294.7021 288.8080 295.7019 289.7879 296.7018 290.7677 4.0% 285.2588 273.8465 286.2861 274.8346 287.3154 275.8228 288.3447 276.8110 289.3742 277.7992 290.4036 278.7875 291.4331 279.7758 292.4627 280.7642 293.4922 281.7526 294.5219 282.7410 295.5515 283.7295 296.5812 284.7180 297.6110 285.7066 298.6408 286.8951 299.6708 287.6838 300.7005 288.6725 301.7304 289.6612 302.7603 290.6499 303.7903 291.6387 304.8203 292.6275 305.8504 293.6164 306.8805 294.6053 307.9107 295.5942 308.9408 296.5832 5.0% 290.0992 275.5942 291.1420 276.5849 292.1850 277.5757 293.2279 278.5665 294.2709 279.5573 295.3139 280.5482 296.3570 281.5391 297.4001 282.5300 298.4432 283.5210 299.4863 284.5120 300.5295 285.5031 301.5728 286.4941 302.6160 287.4852 303.6593 288.4764 304.7027 289.4675 305.7460 290.4587 306.7894 291.4500 307.8329 292.4412 308.8763 293.4325 309.9198 294.4238 310.9633 295.4152 312.0069 296.4066 313.0505 297.3980 314.0941 298.3894
A14
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 257.3998 257.3741 258.3144 258.2885 259.2290 259.2031 260.1439 260.1178 261.0588 261.0327 261.9740 261.9478 262.8892 262.8629 263.8047 263.7783 264.7202 264.6938 265.6359 265.6094 266.5518 266.5252 267.4678 267.4411 268.3840 268.3571 269.3003 269.2734 270.2167 270.1897 271.1333 271.1062 272.0501 272.0228 272.9669 272.9396 273.8839 273.8566 274.8011 274.7736 275.7184 275.6908 276.6358 276.6082 277.5534 277.5257 278.4711 278.4433 0.1% 269.9146 269.6447 270.8542 270.5833 271.7939 271.5221 272.7337 272.4609 273.6738 273.3999 274.6138 274.3390 275.5538 275.2782 276.4940 276.2175 277.4344 277.1570 278.3749 278.0965 279.3155 279.0362 280.2562 279.9760 281.1970 280.9159 282.1380 281.8559 283.0791 282.7960 284.0202 283.7362 284.9615 284.6765 285.9029 285.6170 286.8444 286.5575 287.7860 287.4962 288.7277 288.4390 289.6695 289.3799 290.6115 290.3209 291.5535 291.2619 0.5% 281.9762 280.5663 282.9408 281.5261 283.9055 282.4860 284.8703 283.4480 285.8352 284.4061 286.8002 285.3662 287.7653 286.3265 288.7304 287.2868 289.6957 288.2472 290.6610 289.2077 291.6264 290.1683 292.5919 291.1289 293.5575 292.0897 294.5231 293.0505 295.4889 294.0114 296.4547 294.9724 297.4206 295.9335 298.3866 296.8947 299.3527 297.8559 300.3188 298.8172 301.2851 299.7786 302.2514 300.7401 303.2178 301.7017 304.1843 302.6633 1.0% 288.8761 285.9873 289.8558 286.9572 290.8355 287.9272 291.8154 288.8972 292.7953 289.8674 293.7753 290.8375 294.7554 291.8078 295.7355 292.7781 298.7157 293.7485 297.6960 294.7190 298.6763 295.6895 299.6567 296.6602 300.6372 297.6308 301.6178 298.6016 302.5984 299.5724 303.5791 300.5433 304.5598 301.5142 305.5407 302.4852 306.5215 303.4563 307.5025 304.4275 308.4835 305.3987 309.4646 306.3700 310.4458 307.3413 311.4270 308.3127 2.0% 297.7017 291.7477 298.7017 292.7277 299.7017 293.7077 300.7018 294.6878 301.7020 295.6680 302.7022 296.6482 303.7025 297.6284 304.7028 298.6087 305.7032 299.5891 306.7036 300.5695 307.7041 301.5500 308.7046 302.5305 309.7052 303.5111 310.7059 304.4917 311.7066 305.4724 312.7073 306.4532 313.7081 307.4339 314.7089 308.4148 315.7099 309.3957 316.7108 310.3766 317.7118 311.3576 318.7129 312.3386 319.7140 313.3197 320.7151 314.3008 4.0% 309.9711 297.5722 311.0013 298.5613 312.0316 299.5503 313.0619 300.5395 314.0923 301.5286 315.1227 302.5178 316.1532 303.5070 317.1836 304.4963 318.2141 305.4856 319.2447 306.4749 320.2753 307.4653 321.3059 308.4537 322.3366 309.4431 323.3672 310.4326 324.3980 311.4221 325.4287 312.4116 326.4595 313.4011 327.4904 314.3907 328.5212 315.3804 329.5521 316.3700 330.5830 317.3597 331.6140 318.3494 332.6450 319.3392 333.6760 320.3290 5.0% 315.1378 299.3809 316.1815 300.3724 317.2252 301.3639 318.2690 302.3555 319.3127 303.3471 320.3566 304.3387 321.4004 305.3304 322.4443 306.3221 323.4882 307.3138 324.5321 308.3055 325.5761 309.2973 326.6201 310.2891 327.6641 311.2809 328.7082 312.2728 329.7523 313.2646 330.7964 314.2566 331.8405 315.2485 332.8847 316.2405 333.9289 317.2324 334.9731 318.2245 336.0174 319.2165 337.0617 320.2086 338.1060 321.2007 339.1503 322.1928
A15
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 279.3890 279.3610 280.3070 280.2789 281.2251 281.1970 282.1433 282.1151 283.0617 283.0334 283.9803 283.9519 284.8989 284.8704 285.8177 285.7891 286.7366 286.7080 287.6557 287.6269 288.5749 288.5460 289.4942 289.4653 290.4137 290.3846 291.3332 291.3041 292.2530 292.2237 293.1728 293.1435 294.0928 294.0633 295.0128 294.9833 295.9331 295.9035 296.8534 296.8237 297.7739 297.7441 298.6945 298.6646 299.6152 299.5852 300.5360 300.5060 0.1% 292.4956 292.2032 293.4379 293.1445 294.3803 294.0859 295.3227 295.0274 296.2653 295.9690 297.2079 296.9107 298.1507 297.8526 299.0936 298.7945 300.0366 299.7365 300.9797 300.6787 301.9228 301.6209 302.8661 302.5633 303.8095 303.5057 304.7530 304.4482 305.6966 305.3909 306.6403 306.3336 307.5840 307.2765 308.5279 308.2194 309.4719 309.1624 310.4160 310.1056 311.3602 311.0488 312.3044 311.9921 313.2488 312.9356 314.1933 313.8791 0.5% 305.1508 303.6251 306.1174 304.5869 307.0842 305.5487 308.0510 306.5107 309.0178 307.4727 309.9848 308.4348 310.9518 309.3970 311.9189 310.3593 312.8861 311.3216 313.8533 312.2840 314.8206 313.2465 315.7880 314.2091 316.7555 315.1717 317.7231 316.1344 318.6907 317.0972 319.6584 318.0601 320.6262 319.0230 321.5940 319.9860 322.5619 320.9491 323.5299 321.9123 324.4980 322.8755 325.4661 323.8388 326.4343 324.8021 327.4026 325.7656 1.0% 312.4083 309.2842 313.3896 310.2557 314.3711 311.2273 315.3525 312.1990 316.3341 313.1707 317.3157 314.1425 318.2974 315.1144 319.2791 316.0863 320.2609 317.0583 321.2428 318.0303 322.2247 319.0024 323.2067 319.9746 324.1887 320.9468 325.1708 321.9191 326.1530 322.8915 327.1352 323.8639 328.1175 324.8363 329.0999 325.8089 330.0823 326.7814 331.0647 327.7541 332.0473 328.7268 333.0298 329.6996 334.0125 330.6724 334.9952 331.6452 2.0% 321.7163 315.2820 322.7176 316.2632 323.7189 317.2445 324.7202 318.2258 325.7216 319.2072 326.7231 320.1886 327.7246 321.1701 328.7261 322.1516 329.7277 323.1332 330.7294 324.1148 331.7310 325.0964 332.7328 326.0781 333.7346 327.0599 334.7364 328.0417 335.7383 329.0235 350.1769 336.1698 351.2084 337.1601 352.2400 338.1504 353.2717 339.1408 354.3033 340.1312 355.3350 341.1216 356.3667 342.1121 343.7549 336.8798 344.7572 337.8620 4.0% 334.7071 321.3188 335.7382 322.3087 336.7693 323.2986 337.8007 324.2885 338.8317 325.2784 339.8629 326.2684 340.8942 327.2584 341.9255 328.2484 342.9568 329.2385 343.9881 330.2286 345.0195 331.2187 345.0509 332.2089 347.0824 333.1991 348.1138 334.1893 349.1453 335.1795 350.1769 336.1698 351.2084 337.1601 352.2400 338.1504 353.2717 339.1408 354.3033 340.1312 355.3350 341.1216 356.3667 342.1121 357.3985 343.1025 358.4302 344.0930 5.0% 340.1947 323.1949 341.2391 324.1771 342.2835 325.1693 343.3279 326.1615 344.3724 327.1538 345.4169 328.1461 346.4614 329.1384 347.5060 330.1307 348.5506 331.1230 349.5952 332.1154 350.6398 333.1078 351.6845 334.1003 352.7292 335.0927 353.7739 336.0852 354.8186 337.0777 355.8634 338.0702 356.9082 339.0627 357.9530 340.0553 358.9978 341.0479 360.0427 342.0405 361.0875 343.0332 362.1325 344.0258 363.1774 345.0185 364.2223 346.0112
A16
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
Grade of Service 0.01% 301.4570 301.4269 302.3781 302.3479 303.2993 303.2690 304.2207 304.1902 305.1421 305.1116 306.0637 306.0331 306.9854 306.9547 307.9072 307.8764 308.8291 308.7983 309.7512 309.7202 310.6734 310.6423 311.5957 311.5645 312.5181 312.4868 313.4406 313.4092 314.3632 314.3318 315.2860 315.2545 316.2089 316.1772 317.1319 317.1001 318.0550 318.0231 318.9782 318.9463 319.9015 319.8695 320.8249 320.7929 321.7485 321.7163 322.6722 322.6399 0.1% 315.1378 314.8227 316.0825 315.7664 317.0272 316.7102 317.9721 317.6541 318.9170 318.5981 319.8620 319.5422 320.8072 320.4863 321.7524 321.4306 322.6977 322.3750 323.6431 323.3194 324.5886 324.2640 325.5341 325.2086 326.4798 326.1533 327.4256 327.0982 328.3714 328.0431 329.3174 328.9881 330.2634 329.9331 331.2095 330.8783 332.1557 331.8236 333.1020 332.7689 334.0484 333.7144 334.9949 334.6599 335.9414 335.6055 336.8881 336.5512 0.5% 328.3709 326.7291 329.3393 327.6926 330.3078 328.6563 331.2764 329.6200 332.2450 330.5838 333.2137 331.5476 334.1825 332.5116 335.1513 333.4755 336.1202 334.4396 337.0892 335.4037 338.0582 336.3679 339.0273 337.3322 339.9965 338.2965 340.9657 339.2609 341.9350 340.2253 342.9044 341.1899 343.8738 342.1545 355.8433 343.1191 345.8129 344.0838 346.7825 345.0486 347.7522 346.0135 348.7220 346.9784 349.6918 347.9433 350.6617 348.9084 1.0% 335.9780 332.6182 336.9608 333.5912 337.9437 334.5642 338.9266 335.5373 339.9098 336.5105 340.8926 337.4837 341.8757 338.4570 342.8589 339.4303 343.8421 340.4037 344.8254 341.3771 345.8087 342.3506 346.7921 343.3242 347.7755 344.2978 348.7590 345.2714 349.7426 348.2451 350.7262 347.2189 351.7098 348.1927 352.6935 349.1668 353.6773 350.1405 354.6811 351.1145 355.6450 352.0885 356.6289 353.0626 357.6129 354.0367 358.5969 355.0109 2.0% 345.7595 338.8443 346.7618 339.8266 347.7643 340.8092 348.7667 341.7914 349.7692 342.7738 350.7717 343.7563 351.7743 344.7388 352.7770 345.7214 353.7796 346.7040 354.7823 347.6867 355.7851 348.6694 356.7879 349.6521 357.7907 350.6349 358.7936 351.6177 359.7965 352.6006 360.7995 353.5835 361.8025 354.5664 362.8055 355.5494 363.8086 356.5324 264.8117 357.5155 365.8149 358.4986 366.8181 359.4817 367.8213 360.4649 368.8246 361.4481 4.0% 359.4620 345.0836 360.4939 346.0741 361.5257 347.0647 362.5576 348.0553 363.5895 349.0459 364.6215 350.0366 365.6534 351.0273 366.6854 352.0180 367.7175 353.0088 368.7495 353.9995 369.7813 354.9903 370.8137 355.9812 371.8458 356.9720 372.8780 357.9629 373.9102 358.9538 374.9424 359.9447 375.9747 360.9357 377.0069 361.9267 378.0392 362.9177 379.0715 363.9087 380.1039 364.8997 381.1363 365.8908 382.1687 366.8819 383.2011 367.8730 5.0% 365.2673 347.0040 366.3123 347.9967 367.3574 348.9895 368.4024 349.9823 369.4475 350.9751 370.4926 351.9680 371.5388 352.9608 372.5829 353.9537 373.6280 354.9466 374.6732 355.9396 375.7184 356.9325 376.7637 357.9255 377.8089 358.9185 378.8542 359.9115 379.8995 360.9045 380.9448 361.8976 381.9902 362.8907 383.0356 363.8838 384.0810 364.8769 385.1264 365.8701 386.1718 366.8632 387.2173 367.8564 388.2627 368.8496 389.3082 369.8428
A17
EMOTOROLA LTD. 2004
Version 1 Rev 0
Erlang B
No of Traffic Channels 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400
Grade of Service 0.01% 323.5959 323.5636 324.5198 324.4874 325.4438 325.4113 326.3679 326.3353 327.2922 327.2594 328.2165 328.1837 329.1409 329.1080 330.0655 330.0325 330.9901 330.9570 331.9149 331.8817 332.8398 332.8065 333.7648 333.7314 334.6898 334.6564 335.6150 335.5815 336.5403 336.5067 337.4657 337.4320 338.3912 338.3574 0.1% 337.8348 337.4970 338.7816 338.4429 339.7285 339.3888 340.6755 340.3348 341.6226 341.2810 342.5698 342.2272 343.5170 343.1735 344.4643 344.1198 345.4117 345.0663 346.3592 346.0129 347.3068 346.9595 348.2544 347.9062 349.2022 348.8530 350.1500 349.7998 351.0979 350.7468 352.0459 351.6938 352.9939 352.6409 0.5% 351.6316 349.8735 352.6017 350.8386 353.5717 351.8039 354.5419 352.7692 355.5121 353.7345 356.4823 354.6999 357.4527 355.6654 358.4231 356.6310 359.3935 357.5965 360.3640 258.5622 361.3346 359.5279 362.3052 360.4937 363.2759 361.4596 364.2467 362.4255 365.2175 363.3914 366.1884 364.3574 367.1593 365.3235 1.0% 359.5810 355.9852 360.5651 356.9595 361.5493 357.9338 362.5335 358.9082 363.5178 359.8826 364.5021 360.8571 365.4865 361.8317 366.4710 362.8063 367.4555 363.7809 368.4400 364.7556 369.4246 365.7303 370.4092 366.7051 371.3939 367.6800 372.3786 368.6548 373.3634 369.6298 374.3483 370.6048 375.3331 371.5798 2.0% 369.8279 362.4313 370.8312 363.4146 371.8346 364.3979 372.8381 365.3813 373.8415 366.3647 374.8451 367.3482 375.8486 368.3316 376.8522 369.3152 377.8558 370.2987 378.8595 371.2823 379.8632 372.2659 380.8669 373.2496 381.8707 374.2333 382.8745 375.2170 383.8784 376.2008 384.8822 377.1846 385.8862 378.1684 4.0% 384.2335 368.8642 385.2660 369.8554 386.2985 370.8466 387.3310 371.8378 388.3636 372.8291 389.3962 373.8203 390.4288 374.8116 391.4614 375.8029 392.4940 376.7943 393.5267 377.7857 394.5594 378.7770 395.5921 379.7685 396.6249 380.7599 397.6577 381.7514 398.6905 382.7428 399.7233 383.7343 400.7561 384.7259 5.0% 390.3538 370.8361 391.3993 371.8293 392.4449 372.8226 393.4904 373.8159 394.5360 374.8092 395.5817 375.8026 396.6273 376.7960 397.6730 377.7893 398.7187 378.7827 399.7644 379.7762 400.8101 380.7696 401.8558 381.7631 402.9016 382.7565 403.9474 383.7500 404.9932 384.7435 406.0390 385.7371 407.0849 386.7306
A18
EMOTOROLA LTD. 2004
Version 1 Rev 0
EMOTOROLA LTD. 2004
A19
Version 1 Rev 0
A20
EMOTOROLA LTD. 2004
Version 1 Rev 0
Appendix B (Hotspot Survey)
EMOTOROLA LTD. 2004
B1
Hotspot Survey
Version 1 Rev 0
Hotspot Survey
The objective is to provide a cost-effective method of confirming the location for microcells. Once a search area is defined for a potential microcell site then test transmitters will be set up in the search areas. The points at which the transmitter is sited must: S S S S be practical for installation of BTS equipment be practical in terms of antenna mounting be practical in terms of acquirement, both on cost, environmental and likelihood of lease it should be capable of capturing identified potential traffic
The test cell is then used as a target, by neighbouring cells, for the collection of large volumes of subscriber-generated measurement reports, using the call-trace BSS feature and then analyzed using the Call Trace Product (CTP). The Hotspot/Neighbour Analysis facility produces a series of graphs and reports that analyzes neighbour data. It allows several neighbour reports to be produced summarising neighbour information.
B2
EMOTOROLA LTD. 2004
Version 1 Rev 0
Hotspot Survey
Hotspot Sit Equipment
Typical equipment required for Hotspot transmitter site.
EMOTOROLA LTD. 2004
B3
Hotspot Survey
Version 1 Rev 0
Pre-requisites (local office)

Search areas have been defined based upon: S S S S S S S S S Neighbouring cell traffic/blocking statistics Potential traffic capture areas have been identified (e.g. pedestrian areas, shopping centres and business areas). Maps of appropriate area, are available, to approximate scale of 1:12000. Dummy neighbour definitions, for the test transmitters have been defined in the surrounding cells neighbour lists. Microcell design requirements have been agreed with customer. Suitable vehicles and manpower are available. CTP is installed. Clean frequency available for hotspot sites. Authority is obtained from local authorities/police to conduct hotspot activity.
Equipment loaned by Swindon (less optional items)

The following equipment is required: Equipment 900MHz TEMS Hotspot Generator Bird Wattmeter Portable lightweight, sectioned 5metre mast Pneumatic telescopic 8 metre mast kit (optional) Portable mast tripod 0dBd and 3dBd Katrein omni antennas 5dB directional antennas with 65 and 120 degree beam width (one of each) 10 and 20m feeder cables portable generator (optional) mains inverter charger for TEMS batteries Digital camera Compass Total Cost
B4
Initial Cost() 8000 300 350
2000
100 260 300
150 600 100 50 500 70 12780

EMOTOROLA LTD. 2004
Version 1 Rev 0
Hotspot Survey
Initial deployment
It is proposed that an engineer from Swindon will travel to a certain country, with the required test equipment, for up to a maximum of two weeks. He will be responsible for training the local office in hotspot work for the microcellular trial/rollout. He will work with the local office engineers, in reviewing the pre-planning work, deployment of the hotspot transmitter and analysis of the CTP data so that the local office is capable of providing hotspot work, as cost effective sold service to the customer.
Post initial deployment

The TEMS transmitter and ancillaries necessary for the hotspot work will be rented to the local office for the microcell trial period until the local office can source their own equipment.
Practical deployment of hotspot survey

1. Identify hotspot test transmitter sites from 2. high traffic/blocking macro cells Identifed areas under cells identified above, which, will potentially relieve traffic from macro layer areas likely to generate high mobile microcell usage (e.g. pedestrian areas, office areas) Areas required to maintain contiiguous microcell layer or to link areas of high traffic Buildings of strategic importance
As many test transmitters as possible should be deployed to ensure the best possible comparison, of potential microcell sites, simultaneously thus removing the uncertainty and inaccuracy incurred with different sample periods. The duration of the data collection will depend on the traffic levels on the surrounding cells, The test transmitter will require mains power to maintain continuous RF output , from the TEMS transmitter, over extended periods. This can be supplied by a 12v driven, car mounted, mains inverter or a separate portable mains generator (normal ring mains supply is often unavailable in test locations). For security, the test site should not be unattended and thus a vehicle should be used to transport equipment, provide power for the test transmitter and provide a secure location for the equipment. An alternative to the lightweight mast would be to use a 58metre pneumatic mast attached to the vehicle, (a van would provide a suitable platform). This would speed up the mast erection process but would prevent access to some sites where vehicular access is restricted.
3. 4.
EMOTOROLA LTD. 2004
B5
Hotspot Survey
Version 1 Rev 0
5.
Testneighbour insertion, in all macro cells neighbour lists likely to provide coverage to test transmitter hotspot sites . The basic is not defined in test neighbours. When test transmitters are set up at different locations then the transmitter can be set with a different bsic so that CTP can differentiate between the two sites during post-processing.
Normal neighbour syntax add_neighbor <src_gsm_cell_id or src_cell_name> <neighbor_gsm_cell_id> <placement> [<list_type>] Test neighbour syntax add_neighbor <src_gsm_cell_id or src_cell_name> <test> <num> <placement> [<list_type>] Note : The string test <num> may be entered for this field where <num> is a value from 1 to 64. This permits test neighbours to be added to the BA_SACCH and/or BA_BCCH lists. When a test neighbour is added, the value entered in the placement field will be ignored and the frequency will be the only prompted parameter. 6. Trace-call should be enabled on all cells surrounding the test site(s) but care should be taken to prevent overloading of resources.
GPROC loading can be assessed from the raw stat cpu_usage, over a number of days, real-time monitoring can be achieved via RAM EMON see Note 1 The trace-call data has a relatively low priority, in BSS link terms, to prevent the potential loss of data, the following should be considered: GPROC loading (LCF, BSP, OML) Data collection: Data type No. of MRs No. of simultaneous calls per LCF No. of cells/sites per LCF Trace-call (nth call/IMSI/SCCP) Note1. : to monitor GPROC loading remote login to GPROC, set Executive Monitor mode <set_mmi exec_mon> monitor GPROC loading, every half second, with command <perf> < ENTER> Exit from RAM EMON mode with command <set_mmi cust_mmi> alternatively check loading with ps command within RAM EMON range 1255(1=all MRs) max 4 as config. In database range 1255(1=all calls)
B6
EMOTOROLA LTD. 2004
Version 1 Rev 0
Hotspot Survey
CTP analysis
The data analysis will vary dependant on the type of microcell and the reason for the microcell implementation. << to be continued >> ANNEXE Guidelines for using 1500 Call Trace The user should be aware that care must be taken when using call trace. If an excessive amount of trace data is requested by the user, the BSS and OMC performance will degrade and some trace data will be discarded in order to preserve system integrity. Worst case scenario full data: The heaviest burden is placed on the network when the user specifies all data types, a measurement report interval of 1, and 16 simultaneous calls traced per LCF. We therefore recommend that the following guidelines not be exceeded when requesting full data (that is, all data with measurement report interval=1): Max. # of calls simultaneously traced at the OMC <= 8 Max. # of calls simultaneously traced per BSS* <= 4
Max. # of calls simultaneously traced per MMI TTY <= 2 Note: This limit must be enforced by the user, since the Maximum simultaneous calls traced per LCF limit specified during trace creation is the limit per LCF, and a BSC will typically contain several LCFs. Other factors: The user is advised to avoid sending trace data to the OMC when other significant OML activities, such as uploads and downloads, are occuring. A high call load on the BSS will also adversely affect call trace performance.
EMOTOROLA LTD. 2004
B7
Hotspot Survey
Version 1 Rev 0
Tracing more calls In general, users may trace a larger number of calls simultaneously by limiting the amount of data requested for each call. For example: For a moderately loaded (2500 cph, 10 sec hold time) single LCF system, the following criteria would not normally result in loss of trace data: Measurement Report Interval = 10 Data Types: all Nth call interval = 1 Max. simultaneous calls per LCF = 8 Note, however, if the number of calls traced simultaneously were increased to 16, and the load increased to 4000cph, 12 sec hold time, data would start to be lost at around the 13th call. Tips: 1. Specify only the data types that you need. RSS data produces the most output. Abis data can also produce a lot of data, particularly during call creation, handover, and completion. Use the Total number of calls to be traced field to limit the total amount of data collected. When specifying RSS (measurement report) data, choose a Measurement Report Interval greater than 1 (the default is 10). For Nth call traces, specify a large number for N (e.g. 50). For Nth call traces, specify a small number for the maximum number of traces per LCF (e.g. 2). Trace on a particular mobile, subscriber or call whenever possible. Use the trace_disp MMI command to monitor the number of calls being traced. Trace outside of peak call periods if possible. Stop or reduce tracing when performing code/database uploads and downloads. Delete unwanted trace logs from the OMC. A cron task periodically deletes old logs. However heavy call trace usage may necessitate more frequent attention.
2. 3. 4. 5. 6. 7. 8. 9. 10.
B8
EMOTOROLA LTD. 2004
Version 1 Rev 0
Hotspot Survey
EMOTOROLA LTD. 2004
B9
Hotspot Survey
Version 1 Rev 0
B10
EMOTOROLA LTD. 2004
Version 1 Rev 0
Appendix C (In-Building Requirements Questionnaire)
EMOTOROLA LTD. 2004
C1
In-Building Requirements Questionnaire
Version 1 Rev 0

The following questionnaire should be given to the operator/customer as soon as the location has been selected for an in-building system. The information obtained can then be used as a foundation for discussion of the system requirements. Building plans should be used to indicate the location of any requested information. Operator: Customer:
General Information:
1. Which of the following criteria define the requirements of this system: a) b) c) d) e) f) Equipment trial Improve on poor cellular coverage levels Provide high capacity for in-building users In-building mobile calls originating on this system must be maximized To replace the existing PABX system Other please specify
2.
Are there any deadlines for installation/optimization which have to be met?
3.
Can building plans be supplied in both paper and electronic formats?
Capacity If possible, a sample of PABX and existing macro statistics should be used to determine the estimated traffic loading of the in-building system.
1. How many mobile users are expected to use this system?
2.
What is the expected growth of the system?
C2
EMOTOROLA LTD. 2004
Version 1 Rev 0
3.
Estimate the average busy hour figure in Erlangs per user?
4.
Where the high capacity solution is required: i) estimate peak traffic for each grouping of users
ii)
estimate time of peak busy hour for each group.
5.
Identify areas which are expected to have high capacity requirements.
6.
Identify the type of users (job description) in each area.
7.
What is the required target blocking probability?
Coverage
1. Identify all areas of the building(s) requiring coverage.
2.
Are there any key areas which are particularly important from a coverage point of view?
3.
Identify all entrances and exits , including to and from parking areas.
EMOTOROLA LTD. 2004
C3
Version 1 Rev 0
4.
Is coverage required in any lifts/stairwells? Specify.
5.
Describe the general structure of the building. Indicate: internal/external wall materials; brickwork, glass, partition walls if glass is used, is it metallic/tinted? floor layout - open plan or enclosed rooms? is there an atrium or other building feature which may require special consideration? number of floors in the building are all floors required to have in-building coverage?
Installation
1. Is there a suitable location to install the in-building system BTS (210 by 72 by 41cm)?
2.
Is 48V (27V) available in this location? (Additional space for a power supply may be needed).
3.
Are there existing 2Mbit links to the external network? (Indicate location or proposed location).
4.
Do leased lines exist between PABX and Cellular Operators Switching Platform?
5.
What capacity is available on these links?
C4
EMOTOROLA LTD. 2004
Version 1 Rev 0
6.
Will this system be configured as a co-located BSC or connected to an existing BSC?
7.
Are there are restrictions on mounting silent RF units of 33 x 15 x 11cm and 10kg in weight within the building?
8.
Are there any positions where there would be difficulty in supplying mains power (110V/220V/240V) for the above units?
9.
Are there any restrictions on using coax to feed distributed antenna?
10.
Can any cabling be routed through false ceilings?
11.
Does the building have an existing fibre optic or twisted pair backbone which could be used to connect the RF units to the cluster controller? (Attach cable specification if available). Note: HDSL links require twisted pairs without any electronic switching
12.
Identify the location of patch panels where this system can be connected to. (Indicate the type of connectors used).
13.
Are there limitations on access times for measurements, installation or optimisation?
EMOTOROLA LTD. 2004
C5
Version 1 Rev 0
14.
Are there any common/public areas in the building where instalklation would be prohibited?
15.
Are there any specific equipment types you wish to use or avoid in this site?
Network Operator/RF Environment

1. Which frequency spectrum will be used, and how many frequencies will be available? (Identify specific frequencies if possible).
2.
What is the signal level inside the building perimeter from the existing macro Network?
3.
Identify the location of the surrounding macro sites on a map. Indicate cell name, BCCH/TCH carrier frequencies, BSICs, antenna orientations and output power levels.
4.
How much tolerance is there towards mobiles external to the building originating on the in-building system?
5.
How near are other buildings containing picocell systems?
C6
EMOTOROLA LTD. 2004
Version 1 Rev 0
EMOTOROLA LTD. 2004
C7
Version 1 Rev 0
C8
EMOTOROLA LTD. 2004
Version 1 Rev 0
Planning the InBuilding Solution

Planning the inbuilding solution
When considering the picocellular solution, certain factors have to be taken into account. The flow chart opposite highlights certain functions that will enable the identification of the requirements needed to oversee the picocellular installation. Also contained in the Appendices is: S InBuilding Requirements Questionnaire
This questionnaire, when completed, will enable assessment of the customer requirements and should be sent prior to visiting the customer. The questionnaire forms the basis for initial discussions and will focus the customer to provide the information required. Let us consider each of the functions:
EMOTOROLA LTD. 2004
C9
Version 1 Rev 0
Send Inbuilding requirement questionnaire Talk to Customer Initial Planning Visit Site Modify Plan
Agree Final Plan with Customer Order and Install Equipment Test and Optimise Run and Maintain
C10
EMOTOROLA LTD. 2004
Version 1 Rev 0
Talk to the customer

Determine predicted traffic levels
Each BTS can offer a determined traffic capacity in Erlangs, which is dependent on the grade of service offered. Questions have to be asked to determine the required traffic levels from each of the users and an initial estimate of the position of those users within the building. If the traffic levels are not known, then useful estimates are: S S S S S S S 100mE per Heavy user 30mE per Average user 10mE per Light user
Answers to these questions can also be resolved by use of: Current mobile billing information Number of incoming calls Existing PABX call records Identify geographically located groups by types of employment/mobile usage.
Determine Coverage Requirements

The primary goal for most systems will be excellent coverage. However, the greater the area, and the higher the probability of coverage within that area, the higher the cost of the final system. With this in mind, it will be useful to get rankings of importance of different areas within the building. This will aid decisions later on in the process.
Obtain Building Plans

These are required for planning the system. The more detail, the better, and in both paper and electronic format.
Obtain Contact Name for Building Cable

Installation of the system will need help from the inbuilding cable expert.
EMOTOROLA LTD. 2004
C11
Version 1 Rev 0
Talk to the Customer
Determine Predicted Traffic Levels
Get Building plans
Get Contact Name for Building Cabling
Get Surrounding Cell Information
Ask for Statistics to be Enabled on Surrounding Cells

sys12_ch04_25
C12
EMOTOROLA LTD. 2004
Version 1 Rev 0

The cellular operator should provide the details of the surrounding cells. This would normally be in the form of a map and a .CEL file, indicating: S S S S S S RF unit positions Antenna Orientation BSIC Cell ID Carrier Frequencies O/P Power Levels
Other cellrelated information (e.g. rxlev_access_min would also be useful).
Ask for Statistics to be enabled on Surrounding Cells

Traffic loads and interference levels (dropped calls and poor RXQUAL) are good indicators of a system performance. Knowledge of this before and after installation of the inbuilding system will help in diagnosing any problems that may occur later on. (A three week period may be necessary to give a valid statistical benchmark).
EMOTOROLA LTD. 2004
C13
Version 1 Rev 0
Talk to the Customer
Determine Predicted Traffic Levels
Get Building plans
Get Contact Name for Building Cabling
Ask for Statistics to be Enabled on Surrounding Cells

sys12_ch04_25
C14
EMOTOROLA LTD. 2004
Version 1 Rev 0
Initial planning
Initial planning
Coverage prediction needs two inputs: S S Path loss from the picocell RF units Minimum acceptable level for users
Mark High Traffic Areas

Used to determine the RF distribution in a given area where traffic is a limiting factor. To determine this it is imperative that the peak hour is identified for the specific areas as it may differ. If congestion relief is likely to be employed a check must be undertaken to see that adjacent cells do not incurr the same peak hours/traffic loading.
Use Simple Coverage Rules to estimate Coverage

With application of the simple planning rules, and the knowledge of the minimum required signal levels, estimates of the cell radii can be made.
Mark Potential Head Positions on Plan

With the cell radius and traffic levels, initial estimates on the number of heads and their relative positions can be made. When selecting a potential Picocell RF Unit location, several factors should be considered: S Key Areas and VIP locations
In an ideal implementation, all areas of the building would have excellent coverage. Providing such a system may prove to be costly and inefficient so establishing some sort of weighting could be important. S Interference from the macro/micro network will not be constant around the perimeter of the building. To meet the required C/I levels the Picocell RF Units may need to favour one area of the building. RF Leakage from the inbuilding system should be kept to a minimum. In areas of projected high traffic, coincide overlap of coverage from individual cells so that congestion relief/directed retry can be enabled.
S S
The method for assessing the suitability of these locations is to set up a test transmitter on a clean frequency and record the downlink signal strength throughout that floor.
Check Traffic Coverage is Adequate

Readdress coverage requirements ensuring they meet the criteria defined.
Find Space for the BTS

The PBX room would be an ideal position. This may already contain a power source, air conditioning and provide access to the core MDF.
Suggest Cable Runs

Once the position of the RF distribution and the BTS are known, cable runs have to be planned.
EMOTOROLA LTD. 2004 C15
Initial planning
Version 1 Rev 0
Initial Planning
Analyse outside levels to determi required levels on the internal syst
Mark high traffic areas
Use simple coverage rules to estimate c
Mark potential RF distribution on p
Check traffic coverage is adequa
Find space for BTS
Suggest cable runs

sys12_ch04_26
C16
EMOTOROLA LTD. 2004
Version 1 Rev 0
Visit site
Visit site
Ensure RF Unit Site is Suitable
The planned site should be checked for suitability. Theoretically, it should be a flat surface, large and strong enough to support the Picocell RF Unit. Positions of nearby power, telephony and alarm cabling should be checked to ensure no accidents occur while drilling the mounting holes. Care should be taken to minimise environmental impact.
Check Coverage from Suggested Head Sites

In the initial planning of a system, a test transmitter and measurement receiver can be used to check the RF levels that can be achieved from the proposed sites. The transmitter can be placed at the proposed site, ensuring the antenna is mounted on a stand to get the correct proposed height. The coverage area can then be tested by measuring the signal levels.
Check Cable Runs with Site Expert

Go through plans with the building expert. Check that the proposed cable runs are free from potential interference from other telecommunication or electrical services and do not pass through electronic switching elements.
EMOTOROLA LTD. 2004
C17
Visit site
Version 1 Rev 0
Visit Site
Ensure RF unit site is suitable
Check coverage from suggested R Distribution
Take surveys on surrounding cell site and on suggested frequencies
Check cable runs with site expert

sys12_ch04_27
C18
EMOTOROLA LTD. 2004
Version 1 Rev 0
Modify plan
Modify plan
Analyze Outside Signal Levels
All surveys are processed to help determine the frequency plan and coverage requirements. If a specific set of frequencies have not been allocated to the inbuilding system, or macro/micro signals need identifying, a scan of the surrounding network can identify a list of potential candidates. The TEMS frequency scanning tool can be used to measure the signal strength of all GSM frequencies in a particular location. As the mobile is only guaranteed to see BCCH carriers, the BSIC of each frequency should be requested. A map of the surrounding cells can then be used to identify associated traffic channels. As the received signal strength will not remain constant around the building, the scan should be carried out at each of the extremities of the building. It is normally best to make these measurements on the upper floor, as well as intermediate floors, of a building as these are most open to interference. The scan should also be repeated several times at each location to provide a level of confidence, as well as coincide with peak busy hours. It is important to get close to the windows in perimeter offices as this is where the lowest C/I is expected. If a TCH frequency from a surrounding macro is reused on the inbuilding system the associated BCCH must be scanned to determine worst case interference.
Determine Actual Coverage

Combining the measured path loss data and the analysed external signal levels will produce an excellent coverage prediction. This should be compared with the initial requirement to check that all important areas exceed the expectation.
Move RF Distribution if Necessary

For coverage, traffic or interconnect reasons the RF distribution may need to be replanned. This will result in at least a number of extra tasks and repeating a number of checks.
Draw Up Frequency Plan Generate Neighbour List
EMOTOROLA LTD. 2004
C19
Modify plan
Version 1 Rev 0
Modify Plan
Analyse outside signal levels
Determine actual coverage
Move RF distribution positions if necessary
Draw up frequency plan
Generate neighbour list
sys12_ch04_28
C20
EMOTOROLA LTD. 2004
Version 1 Rev 0
Agree final plan with customer

Revisit Customer Agree Final Plan
It is imperative that the following points are discussed with the customer: S S S S S Network architecture to fulfill the requirements Final hardware requirements Responsibilities Resourcing Acceptance criteria. This should be defined in terms of: Coverage Quality Call drop Call setup (originations) Call setup (failures) Handover failures
EMOTOROLA LTD. 2004
C21
Version 1 Rev 0
Agree Final Plan with Customer
Revisit customer
Agree final plan
sys12_ch04_29
C22
EMOTOROLA LTD. 2004
Version 1 Rev 0
Order and install equipment

The flow diagram opposite shows the functional steps and requirements for ordering and installation of the proposed solution.
EMOTOROLA LTD. 2004
C23
Version 1 Rev 0
Order and Install Equipment
Order Motorola Equipment
Order E1 line installation
Order Aux Equipment
Install BTS
Install RF Distribution
Install DC power supply
Fit antenn and coa
Configure in building cabling
sys12_ch04_30
C24
EMOTOROLA LTD. 2004
Version 1 Rev 0
Test and optimize
Test and optimize

The flow diagram opposite shows the functional steps and possible requirements for the testing and optimisation of the solution. The optimization process can be divided into three phases:
Phase 1
S S S S S Database configuration Neighbour list creation Algorithm selections Idle Mode Handover Strategy
Phase 2
In order to minimise disruption to cellular service quality in the building, as much optimisation as possible will be performed before commercial users are allowed to access the system. This will be achieved by setting the Cell_bar_access_switch, but retaining the ability to handover. Optimization will be performed with TEMS mobiles configured to ignore Cell_bar_access. The picocells, at this stage, should be included in the neighbour lists of the external macrocells, but configured with maximum ho_margins in order to exclude the hand in of commercial mobiles. Tests will include: S coverage testing S individual floors lock onto cell under test and disable HO key offices all stairwells
interference testing frequency reuse within the building (NB. floors 1 & 4) external macro frequencies
handover testing floor to floor HO to macros at perimeter HO to macros at all exits
EMOTOROLA LTD. 2004
C25
Test and optimize
Version 1 Rev 0
Test and Optimize

Power up system
Activate cell_bar
Monitor OMC to ensure all equipment is inservice and no ala
Coverage handover tests
Call testing
Connect to commercial system
Check internal to external handovers and originations
Customer signoff against acceptance criteria
Remove cell_bar
sys12_ch04_31
C26
EMOTOROLA LTD. 2004
Version 1 Rev 0
Test and optimize
Tests will include:

S S idle mode operation testing stairwells and areas of possible interference
enable call trace to examine all cells for path balance
This also gives a breakdown of handover causes, BSSMAP and DTAP message counts which are useful in assessing the system traffic character. S enable per neighbour cell stats for handover cause analysis.
This will readily identify cells performance and effectiveness of the selected handover strategy. S handover testing S HO from macros at perimeter HO from macros at all entrances
Full system testing for coverage acceptance.
As a result of the above tests, frequencies, cells power and handover parameters can be adjusted to meet the acceptance criteria. The system call performance should be established with all the picocells set to the correct handover margins in the neighbour lists of the external macrocells in order to allow full testing of the hand in process.
Phase 3
After this phase is completed successfully, Cell_bar_access may be lifted and full commercial service may begin. Further coverage and interference testing will be required to address any issues, in the commercial environment, not carried out in earlier phases. Additionally, some system monitoring will be required to evaluate the effectiveness of the inbuilding system deployment. A subscriber fault reporting process should be put in place so that any faults may be isolated quickly. Once the picocell system has enough subscribers to generate reliable statistics, then a reduced statistical collection should be used for daily system assessment.
EMOTOROLA LTD. 2004
C27
Test and optimize
Version 1 Rev 0
Test and Optimize

Power up system
Activate cell_bar
Monitor OMC to ensure all equipment is inservice and no alarms
Coverage handover tests
Call testing
Connect to commercial system
Check internal to external handovers and originations
Customer signoff against acceptance criteria
Remove cell_bar
sys12_ch04_31
C28
EMOTOROLA LTD. 2004
Version 1 Rev 0
Run and maintain
Run and maintain

The flow diagram opposite shows the functional steps and requirements for ensuring that the installed solution operates effectively and efficiently, as well as monitoring for potential failings.
EMOTOROLA LTD. 2004
C29
Run and maintain
Version 1 Rev 0
Run and Maintain
Check stats to ensure system is carrying traffic
Monitor OMC
Frequency replan if exterior system is replanned
Expand system if it starts to block

sys12_ch04_32
C30
EMOTOROLA LTD. 2004
Answers
EMOTOROLA LTD. 2004
Version 1 Rev 0
ii
EMOTOROLA LTD. 2004
Version 1 Rev 0
C2 Reselection Exercise
The parameters and levels specified on the facing page are typical values experienced by a mobile in the reselection process. Use these values to determine whether the mobile will reselect to the neighbour cell. The mobile has been in the server well over one hour, and the best neighbour has been in the top six measured cells for exactly 4 minutes.
WORKING AREA
SERVING working out C1 first( A= A= B= B= Rxlev Av (-70) - P1 (-90) (P1= rxlev_access_min= (-90) dBm) = 20 dBm
P2 - Max RF Power of MS(P2=ms_txpwr_max_cch= 29dBm) 29 + 33 0 6 = (-4) dB = = 20 dB 26 dB
C1= 20 C2= 20
NEIGHBOUR A= A= B= B= Rxlev Av (-63) - P1 (-90) (P1= rxlev_access_min= (-90) dBm) = 27 dB (P2=ms_txpwr_max_cch= 33 dBm) 0 dB 27 dB 21 dB
P2 - Max RF Power of MS 33 + 33 0 = = =
C1= 27 C2= 27
4 - 10
FOR RESELECTION C2 server( < C2 neighbour( ) cell_reselect_hysteresis C2 server= 26 C2 Neighbour= 21 C2 Neighbour ) cell_reselect_hysterisis= 9 No reselection
EMOTOROLA LTD. 2004 7i
Version 1 Rev 0
7ii
EMOTOROLA LTD. 2004
Version 1 Rev 0
EMOTOROLA LTD. 2004
7iii
Version 1 Rev 0
Power Budget Exercise part 1

The figures specified on the facing page can be used by the HDPC to calculate the Power budget assessment. Use the working area to calculate PBBT (n).
SERVING macro(
Power Budget Exercise part 2

serving= even greater effect. 111 an
serving=
min ms_txpwr_max,P( -Rxlev_DL -PWR_C_D
serving= ms_twpwr_max_cell in add_neigh of-90( 33 - the server - 12 to 27 dBm then the If was set
outcome of the calculation for PBGT(n) would be 9. It could be lowered to 25 dBm to get This has helped make the microcell neighbor look more attractive.
NEIGHBOUR micro( neighbour= min ms_txpwr_max n(,P( -RXLEV_NCELL n( neighbour= neighbour= 33 108 -75(
PBGT n(= serving - Neighbour PBGT n(= 111 PBGT n(= 3 - 108
7iv
EMOTOROLA LTD. 2004
Version 1 Rev 0
EMOTOROLA LTD. 2004
7v
Version 1 Rev 0
Answers (possible solution)

add_neighbor srccell_id xxx xx xxx xx0 neighbor_cell_id xxx xx xxx xx1 Placement External list type Both pgsm 20 0 to 63 All sites could have a separate BSIC 33 dBm Class 4 2w mobiles 6 (-104dBm) Not restricting (note on street level) criteria 1 6 Set low for easy emergency qualification but prevent ping ponging 4 Reasonably quick and accurate for emergency handup 0 Disable interference avoidance test 2 Macrocell (no PBGT(n)) qualification ____ ____ ____ ____ ____ ____ ____ ____
7vi
EMOTOROLA LTD. 2004
Version 1 Rev 0

add_neighbor srccell_id xxx xx xxx xx0 neighbor_cell_id xxx xx xxx xx2 Placement Internal Same BSC as SRC cell list type BA_SACCH Discourages idle selection or reselection 0 No synchronised handovers (separate BTSs) 30 (80 dBm) On street level plus a margin 6 Low for easy qualification but prevent ping ponging 6 Fast handin encouraged 0 Disable interference avoidance test 4 Alg type for line of sight neighbor
(For type 4) 24 20 SACCH multiframes is approximately 10 seconds

forces fast mobiles upto the macro layer.
add_cell parameters neighbor 2 (frequency used = 43) frequency_type PGSM BSIC = (0 to 63) max_tx_ms = 27 rxlev_min_ def = 30
EMOTOROLA LTD. 2004
7vii
Version 1 Rev 0

add_neighbor srccell_id xxx xx xxx xx0 neighbor_cell_id xxx xx xxx xx3 Placement Internal Same BSC as SRCELL list type BA_SACCH Discourages idle selection or reselection 0 30 (80dBm) On street level plus a margin 6 Low ho_margin used as handin encouraged for slow MS but prevents ping ponging 8 Longer hreqave to ensure cochannel interference neighbour is clear 0 Disable interefence avoidance test 7 Alg type for line of sight neighbor 9 ho_margin 3dB higher than ho_margin(n)
7viii
EMOTOROLA LTD. 2004
Version 1 Rev 0

add_neighbor srccell_id xxx xx xxx xx0 neighbor_cell_id xxx xx xxx xx4 Placement Internal list type BOTH 0 30 (80dbm) On street level plus a margin 6 Low ho_margin as handin encouraged for slow MS and prevents ping ponging 4 Fast handin required 0 Disable interference avoidance test 3 Alg type (round the corner neighbour)
(For type 3) 30 (80db) levels drop by typically 20db (For type 3) 30 (80db) levels drop by typically 20db
____ ____ ____ ____ ____ ____
EMOTOROLA LTD. 2004
7ix
Version 1 Rev 0

add_neighbor srccell_id xxx xx xxx xx0 neighbor_cell_id xxx xx xxx xx5 Placement Internal Same BSC as source cell list type BOTH 0 25 (85dbM) Should stop external handing in (25db) 3 Low ho_margin as handover would have to be quick going into the building also prevents ping ponging 3 Fast handin required 0 Disable int avoidance test 6 Inbuilding neighbour other types also should be considered
(For type 6) 20 delay time approx 10s (For type 6) 4

To discourage on street handin
(For type 6) 2 To encourage handin for those entering building.

____ ____ ____ ____ ____ ____
7x EMOTOROLA LTD. 2004
Version 1 Rev 0
EMOTOROLA LTD. 2004
7xi
Glossary of technical terms and abbreviations
10TH JULY 95
G1
Manual Title Goes Here FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED
G2
10TH JULY 95
Numbers
Numbers
# 2 Mbit/s link Number. As used in this manual set, the term applies to the European 4-wire 2.048 Mbit/s digital line or link which can carry 30 A-law PCM channels or 120 16 kbit/s GSM channels. 4th Generation Language.
4GL
10TH JULY 95
G1
A
A interface A3 A38 A5 A8 AB Abis interface Interface between MSC and BSS. Authentication algorithm that produces SRES, using RAND and Ki. A single algorithm performing the function of A3 and A8. Stream cipher algorithm, residing on an MS, that produces ciphertext out of plaintext, using Kc. Ciphering key generating algorithm that produces Kc using RAND and Ki. Access Burst. Interface between a remote BSC and BTS. Motorola offers a GSM standard and a unique Motorola Abis interface. The Motorola interface reduces the amount of message traffic and thus the number of 2 Mbit/s lines required between BSC and BTS. Answer Bid Ratio. ACDC Power Supply module. Alternating Current. Access Class (C0 to C15). Application Context. Automatic Congestion Control. Associated Control CHannel. ACKnowledgement. Accumulated Call meter. Address Complete Message. AC Power Interface Module. Used in M-Cell6 indor ac BTS equipment. AC Power Supply Module. Used in M-Cell6 BTS equipment. Associated Control Service Element. Antenna Combining Unit. Analogue to Digital (converter). ADministration Centre. Analogue to Digital Converter. ADvanced Communications Control Protocol. ADMinistration processor. ADMINistration. Abbreviated Dialling Number. Adaptive Differential Pulse Code Modulation. Application Entity. Accoustic Echo Control. Additional Elementary Functions.
ABR acdc PSM ac AC AC ACC ACCH ACK, Ack ACM ACM ACPIM AC PSM ACSE ACU A/D ADC ADC ADCCP ADM ADMIN ADN ADPCM AE AEC AEF
G2
10TH JULY 95
AET
Active Events Table. Alarms and events are sent to the Events Log in the GUI. Different operators will have different subscription lists. All alarms and events are sent to the AET before they are re-routed to different subscription lists. Automatic Frequency Control. Absolute Frame Number. Automatic Gain Control. Access Grant CHannel. A GSM common control channel used to assign MS to a SDCCH or a TCH. Action indicator. Artificial Intelligence. Alarm Interface Board. A class of processor. The radio link between the BTS and the MS. Amplitude Modulation. Automatic Message Accounting (processor). Cell broadcast mobile terminated message. A message broadcast to all MSs in a cell. Advice of Change. Advice of Change Charging supplementary service. Advice of Change Information supplementary service. Automatic Output Control. Application Process. Absolute Radio Frequency Channel Number. An integer which defines the absolute RF channel number. Automatic ReQuest for retransmission. Address Resolution Protocol. Association Control Service Element. An ASE which provides an AP with the means to establish and control an association with an AP in a remote NE. Maps directly onto the Presentation layer (OMC). Application Service Element (OMC) Application Specific Entity (TCAP). Abstract Syntax Notation One. Alarm and Status Panel. Answer Seizure Ratio. All Trunks Busy. Antenna Transceiver Interface. ATTach. Automatic Trunk Testing Subsystem. Access Unit. Authentication Centre. A GSM network entity which provides the functionality for verifying the identity of an MS when requested by the system. Often a part of the HLR.
AFC AFN AGC AGCH Ai AI AIB AIO Air interface AM AMA AM/MP AoC AoCC AoCI AOC AP ARFCN ARQ ARP ASCE
ASE ASE ASN.1 ASP ASR ATB ATI ATT (flag) ATTS AU AuC
10TH JULY 95
G3
AUT(H) AUTO
AUThentication. AUTOmatic mode.
G4
10TH JULY 95
B
B Interface BA BAIC BAOC BBBX BBH BCC BCCH Interface between MSC and VLR. BCCH Allocation. The radio frequency channels allocated in a cell for BCCH transmission. Barring of All Incoming Calls supplementary service. Barring of All Outgoing Calls supplementary service. Battery Backup Board. Base Band Hopping. BTS Colour Code. Broadcast Control CHannel. A GSM control channel used to broadcast general information about a BTS site on a per cell or sector basis. Binary Coded Decimal. Base station Control Function. The GSM term for the digital control circuitry which controls the BTS. In Motorola cell sites this is a normally a BCU which includes DRI modules and is located in the BTS cabinet. Bearer Capability Information Element. Base station Control Unit. A functional entity of the BSS which provides the base control function at a BTS site. The term no longer applies to a type of shelf (see BSC and BSU). Base Controller Unit Power. Bit Error Rate. A measure of signal quality in the GSM system. Business Exchange Services. Bad Frame Indication. Busy Hour Call Attempt. all Barring of All Incoming call supplementary service. Balanced-line Interconnect Board. Provides interface to 12 balanced (6-pair) 120 ohm (37-pin D-type connector) lines for 2 Mbit/s circuits (See also T43). Barring of All Incoming Calls when Roaming outside the Home PLMN Country supplementary service. Balanced-line Interconnect Module. An area in a data array used to store information. BootLoad. Also known as download. For example, databases and software can be downloaded to the NEs from the BSS. BiLLiNG. Bits per second (bps). Full rate traffic channel. Bit Number. Number which identifies the position of a particular bit period within a timeslot. Bandpass Filter. mBCU Power Supply Module.
BCD BCF
BCIE BCU
BCUP BER BES BFI BHCA BI BIB
BICRoam BIM Bin BL BLLNG bit/s Bm BN BPF BPSM
10TH JULY 95
G5
BS BS
Basic Service (group). Bearer Service. A type of telecommunication service that provides the capability for the transmission of signals between user-network interfaces. The PLMN connection type used to support a bearer service may be identical to that used to support other types of telecommunication service. Base Station Controller. A network component in the GSM PLMN which has the digital control function of controlling all BTSs. The BSC can be located within a single BTS cabinet (forming a BSS) but is more often located remotely and controls several BTSs (see BCF, BCU, and BSU). Basic Service Group. Base Transceiver Station Identity Code. A block of code, consisting of the GSM PLMN colour code and a base station colour code. One Base Station can have several Base Station Colour Codes. BSIC of an adjacent cell. Base Site control Processor (at BSC). Backward Sequence Number. Base Station System. The system of base station equipment (Transceivers, controllers and so on) which is viewed by the MSC through a single interface as defined by the GSM 08 series of recommendations, as being the entity responsible for communicating with MSs in a certain area. The radio equipment of a BSS may cover one or more cells. A BSS may consist of one or more base stations. If an internal interface is implemented according to the GSM 08.5x series of recommendations, then the BSS consists of one BSC and several BTSs. BSS Application Part (of Signalling System No. 7) (DTAP + BSSMAP). Base Station System Control cabinet. The cabinet which houses one or two BSU shelves at a BSC or one or two RXU shelves at a remote transcoder. Base Station System Management Application Part (6-8). BSS Operation and Maintenance Application Part (of Signalling System No. 7). Base Station Unit shelf. The shelf which houses the digital control modules for the BTS (p/o BTS cabinet) or BSC (p/o BSSC cabinet). British Telecom. Bus Terminator. Bus Terminator Card. Base Transceiver Function. Base Transceiver Processor (at BTS). One of the six basic task groups within the GPROC.
BSC
BSG BSIC
BSIC-NCELL BSP BSN BSS
BSSAP BSSC
BSSMAP BSSOMAP BSU
BT BT BTC BTF BTP
G6
10TH JULY 95
BTS
Base Transceiver Station. A network component in the GSM PLMN which serves one cell, and is controlled by a BSC. The BTS contains one or more Transceivers (TRXs). A period of modulated carrier less than one timeslot. The physical content of a timeslot.
Burst
10TH JULY 95
G7
C
C C Interface C7 CA CA CAB CADM Conditional. Interface between MSC and HLR/AUC. ITU-TSS Signalling System 7 (sometimes referred to as S7 or SS#7). Cell Allocation. The radio frequency channels allocated to a particular cell. Central Authority. Cabinet. Country ADMinistration. The Motorola procedure used within DataGen to create new country and network files in the DataGen database. Charge Advice Information. Cell Analysis Tool. Cell Broadcast. Circuit Breaker. Cell Broadcast Centre. Cell Broadcast CHannel. Combining Bandpass Filter. Cell Broadcast Link. Circuit Breaker Module. Cell Broadcast Message Identifier. Cell Broadcast Short Message Service. Clock Bus. Connection Confirm (Part of SCCP network connectivity). Country Code. Call Control. Cavity Combining Block, a three way RF combiner. There are two types of CCB, CCB (Output) and CCB (Extension). These, with up to two CCB Control cards, may comprise the TATI. The second card may be used for redundancy. Completion of Calls to Busy Subscriber supplementary service. Common Control CHannels. A class of GSM control channels used to control paging and grant access. Includes AGCH, PCH, and RACH. Group of MSs in idle mode. Common Channel Distributor. Channel Coding Digital Signal Processor. Conditional Call Forwarding. Control CHannel. Control channels are channels which carry system management messages. Council for Communications Harmonization (referred to in GSM Recommendations).
CAI CAT CB CB CBC CBCH CBF CBL CBM CBMI CBSMS CBUS CC CC CC CCB
CCBS CCCH
CCCH_GROUP CCD CCDSP CCF CCH CCH
G8
10TH JULY 95
CCIT
Comit Consultatif International Tlgraphique et Tlphonique. This term has been superceded by ITUTSS (International Telecommunications Union Telecommunications Sector). Current Call Meter. Capability/Configuration Parameter. Control Channel Protocol Entity. Hundred call-seconds. The unit in which amounts of telephone traffic are measured. A single call lasting one hundred seconds is one CCS. See also erlang. Circuit. Control Driver Board. Common Desktop Environment. Part of the SUN software (crontab cron job file). Call Detail Records. Chargeable DURation. Control Equalizer Board (BTS). Called station identifier. Central Equipment Identity Register. By GSM definition, a cell is an RF coverage area. At an omni-site, cell is synonymous with site; at a sectored site, cell is synonymous with sector. This differs from analogue systems where cell is taken to mean the same thing as site. (See below).
CCM CCP CCPE CCS
Cct CDB CDE CDR CDUR CEB CED CEIR Cell
1 Cell = 1 Sector
Omni Site 1-Cell Site (1 BTS)
6-Sector Site or 6-Cell Site (6 BTSs)
CEND CEPT CERM CF CF CFB CFC CFNRc CFNRy
End of charge point. Confrence des administrations Europennes des Postes et Telecommunications. Circuit Error Rate Monitor. Conversion Facility. all Call Forwarding services. Call Forwarding on mobile subscriber Busy supplementary service. Conditional Call Forward. Call Forwarding on mobile subscriber Not Reachable supplementary service. Call Forwarding on No Reply supplementary service.
10TH JULY 95
G9
CFU Channel
Call Forwarding Unconditional supplementary service. A means of one-way transmission. A defined sequence of periods (for example, timeslots) in a TDMA system; a defined frequency band in an FDMA system; a defined sequence of periods and frequency bands in a frequency hopped system. Coaxial Interconnect Module. CHarging Point. Card Holder Verification information. Ciphering Key Sequence Number. Cell Identity. A block of code which identifies a cell within a location area. CUG Index. Circuit Identity Code. Carrier to Interference Ratio. Unintelligible data produced through the use of encipherment. Ciphering Key Sequence Number. Calling Line Identity. Calling Line Identification Presentation supplementary service. Calling Line Identification Restriction supplementary service. Clock. Clock Extender half size board. The fibre optic link that distributes GCLK to boards in system (p/o BSS etc). Connectionless Manager. CLeaR. Configuration Management. An OMC application. Connection Management. CoMmanD. Channel Mode Modify. Common Management Information Protocol. Common Management Information Service Element. An ASE which provides a means to transfer management information via CMIP messages with another NE over an association established by ASCE using ROSE (OMC). Cellular Manual Revision. CalliNg tone. COnnected Line Identity. Placed together; two or more items together in the same place. A cell which has a co-located neighbour whose cell boundary follows the boundary of the said cell. The coincident cell has a different frequency type, but the same BSIC, as that of the neighbour cell. COnnected Line Identification Presentation supplementary service.
CIM CHP CHV CKSN CI CI CIC CIR, C/I Ciphertext CKSN CLI CLIP CLIR CLK CLKX CLM CLR CM CM CMD CMM CMIP CMISE
CMR CNG COLI Collocated Coincident Cell
COLP
G10
10TH JULY 95
COLR CODEX COM COM COMB CONNACK COMM, Comms CommsLink CONF CONFIG CP CPU C/R CR CR CRC CRE CREF CRM CRM-LS/HS
COnnected Line Identification Restriction supplementary service. Manufacturers name for a type of multiplexer and packet switch commonly installed at the Motorola OMC-R. Code Object Manager. COMplete. Combiner. CONNect ACKnowledgement. COMMunications. Communications Link. (2Mbit/s) CONFerence circuit. CONFIGuration Control Program. Call Processing. Central Processing Unit. Command/Response field bit. Carriage Return (RETURN). Connection Request (Part of SCCP network connectivity). Cyclic Redundancy Check (3 bit). Call RE-establishment procedure. Connection REFused (Part of SCCP network connectivity). Cell Resource Manager. Cellular Radio Modem-Low Speed/High Speed. Low speed modem used to interwork 300 to 2400 bit/s data services under V.22bis, V.23, or V.21 standards. High speed modem used to interwork 1200 to 9600 bit/s data services under V.22bis, V.32, or V.29/V.27ter/V.21 standards. Cathode Ray Tube (video display terminal). Code Storage Facility Processor (at BSC and BTS). Central Statistics Process. The statistics process in the BSC. Circuit Switched Public Data Network. Call Transfer supplementary service. Channel Tester. Channel Type. Call Trace Product (Tool). Common Technical Regulation. Clear to Send. Method of flow control (RS232 Interface). Compact Transceiver Unit (M-Cellhorizon radio). Closed User Group supplementary service. The total value for an entire statistical interval. Call Waiting supplementary service.
CRT CSFP CSP CSPDN CT CT CT CTP CTR CTS CTU CUG Cumulative value CW
10TH JULY 95
G11
D
D Interface D/A DAB DAC DACS DAN DAS DAT DataGen dB DB DB DBA DBMS dc DCB DCCH Interface between VLR and HLR. Digital to Analogue (converter). Disribution Alarm Board. Digital to Analogue Converter. Digital Access Cross-connect System. Digital ANnouncer (for recorded announcements on MSC). Data Acquisition System. Digital Audio Tape. Sysgen Builder System. A Motorola offline BSS binary object configuration tool. Decibel. A unit of power ratio measurement. DataBase. Dummy Burst (see Dummy burst). DataBase Administration/Database Administrator. DataBase Management System. Direct Current. Diversity Control Board (p/o DRCU). Dedicated Control CHannel. A class of GSM control channels used to set up calls and report measurements. Includes SDCCH, FACCH, and SACCH. Data Carrier Detect signal. Data Circuit terminating Equipment. Data Communications Function. Duplexed Combining bandpass Filter. (Used in Horizonmacro). Data Communications Network. A DCN connects Network Elements with internal mediation functions or mediation devices to the Operations Systems. DC Power Supply Module. Digital Cellular System at 1800 MHz. A cellular phone network using digital techniques similar to those used in GSM 900, but operating on frequencies of 1710 1785 MHz and 1805 1880 MHz. Dual-stage Duplexed combining Filter. (Used in Horizonmacro). DataGen Directory Structure. Data Drive Storage. Direct Digital Synthesis. Diversity Equalizer Board. DETach. Decision Feedback Equalizer. Data Gathering Tool.
DCD DCE DCF DCF DCN
DC PSM DCS1800
DDF DDS DDS DDS DEQB DET DFE DGT
G12
10TH JULY 95
DHP DIA DINO E1/HDSL DINO T1 DISC Discon DIQ DIR DL DLCI DLD DLNB DLSP DLSP Dm DMA DMA DMR DMX DN DNIC Downlink DP DPC
Digital Host Processor. Drum Intercept Announcer. Line termination module. Line termination module. DISConnect. Discontiuous. Diversity In phase and Quadrature phase. Device Interface Routine. Data Link (layer). Data Link Connection Identifier. Data Link Discriminator. Diversity Low Noise Block. Data Link Service Process. Digital Link Signalling Processor. Control channel (ISDN terminology applied to mobile service). Deferred Maintenance Alarm. An alarm report level; an immediate or deferred response is required (see also PMA). Direct Memory Access. Digital Mobile Radio. Distributed Electronic Mobile Exchange (Motorolas networked EMX family). Directory Number. Data network identifier. Physical link from the BTS towards the MS (BTS transmits, MS receives). Dial/Dialled Pulse. Destination Point Code. A part of the label in a signalling message that uniquely identifies, in a signalling network, the (signalling) destination point of the message. Digital Processing and Control board. Digital Private Network Signalling System (BT standard for PABX interface). Dual Path Preselector. Dual Port Random Access Memory. Digital Power Supply Module. Dynamic Random Access Memory. Data Rate Converter board. Provides data and protocol conversion between PLMN and destination network for 8 circuits (p/o IWF). Diversity Radio Channel Unit. Contains transceiver, digital control circuits, and power supply (p/o BSS) (see RCU). Generic term for radio channel unit. May be standard RCU or diversity radio channel unit DRCU.
DPC DPNSS DPP DPR, DPRAM DPSM DRAM DRC
DRCU (D)RCU
10TH JULY 95
G13
DRI DRIM DRIX DRX, DRx
Digital Radio Interface. Provides encoding/decoding and encryption/decryption for radio channel (p/o BSS). Digital Radio Interface extended Memory. A DRI with extra memory. DRI Extender half size board. Fibre optic link from DRI to BCU (p/o BSS). Discontinuous reception (mechanism). A means of saving battery power (for example in hand-portable units) by periodically and automatically switching the MS receiver on and off. German term for 2 Mbit/s line (PCM interface). Data Switching Exchange. Digital Speech Interpolation. Digital Signal Processor. Digital Subscriber Signalling No 1. Diversity Signal Strength Indication. Direct Transfer Application Part (6-8). Data Terminal Equipment. Digital Trunk Frame. DaTa form 1 (Part of SCCP network connectivity). Digital Trunk Interface. Dual Tone Multi-Frequency (tone signalling type). Data Terminal Ready signal. Method of flow control (RS232 Interface). Dual Transceiver Module. (Radio used in M-Cellarena and M-Cellarena macro). Discontinuous Transmission (mechanism). A means of saving battery power (for example in hand-portable units) and reducing interference by automatically switching the transmitter off when no speech or data are to be sent. A period of carrier less than one timeslot whose modulation is a defined sequence that carries no useful information. A dummy burst fills a timeslot with an RF signal when no information is to be delivered to a channel. DYnamic NETwork. Used to specify BTSs sharing dynamic resources.
DS-2 DSE DSI DSP DSS1 DSSI DTAP DTE DTF DT1 DTI DTMF DTR DTRX DTX, DTx
Dummy burst
DYNET
G14
10TH JULY 95
E
E E Interface EA EAS Eb/No EBCG EC ECB ECID ECM Ec/No ECT ECT EEL EEPROM EGSM900 EI EIR EIRP EIRP EL EM EMC EMF EMI eMLPP EMMI EMU EMX en bloc See Erlang. Interface between MSC and MSC. External Alarms. External Alarm System. Energy per Bit/Noise floor. Elementary Basic Service Group. Echo Canceller. Performs echo suppression for all voice circuits. Provides echo cancelling for telephone trunks for 30 channels (EC). The Motorola European Cellular Infrastructure Division. Error Correction Mode (facsimile). Ratio of energy per modulating bit to the noise spectral density. Event Counting Tool. Explicit Call Transfer supplementary service. Electric Echo Loss. Electrically Erasable Programmable Read Only Memory. Extended GSM900. Events Interface. Part of the OMC-R GUI. Equipment Identity Register. Effective Isotropic Radiated Power. Equipment Identity Register Procedure. Echo Loss. Event Management. An OMC application. ElectroMagnetic Compatibility. Electro Motive Force. Electro Magnetic Interference. enhanced Multi-Level Precedence and Pre-emption service. Electrical Man Machine Interface. Exchange office Management Unit (p/o Horizonoffice) Electronic Mobile Exchange (Motorolas MSC family). Fr. all at once (a CCITT #7 Digital Transmission scheme); En bloc sending means that digits are sent from one system to another ~ (that is, all the digits for a given call are sent at the same time as a group). ~ sending is the opposite of overlap sending. A system using ~ sending will wait until it has collected all the digits for a given call before it attempts to send digits to the next system. All the digits are then sent as a group. End of Tape. Erasable Programmable Read Only Memory.
EOT EPROM
10TH JULY 95
G15
EPSM EQB EQCP EQ DSP Erlang
Enhanced Power Supply Module (+27 V). Equalizer Board. Control circuit for equalization for 8 time slots each with equalizing circuitry and a DSP (p/o RCU). Equalizer Control Processor. Equalizer Digitizer Signal Processor. International (dimensionless) unit of traffic intensity defined as the ratio of time a facility is occupied to the time it is available for occupancy. One erlang is equal to 36 CCS. In the US this is also known as a traffic unit (TU). Ear Reference Point. Effective Radiated Power. ERRor. Electro-static Point. Embedded SQL (Structured Query Language). An RDBMS programming interface language. Extended TACS (analogue cellular system, extended). Type of Local Area Network. ETSI Technical Report. European Telecommunication Standard. European Telecommunications Standards Institute. End of Transmission. Executive Process.
ERP ERP ERR ESP ESQL E-TACS Ethernet ETR ETS ETSI ETX EXEC
G16
10TH JULY 95
F
F Interface FA FA FA FAC FACCH Interface between MSC and EIR. Fax Adaptor. Full Allocation. Functional Area. Final Assembly Code. Fast Associated Control Channel. A GSM dedicated control channel which is associated with a TCH and carries control information after a call is set up (see SDCCH). Fast Associated Control Channel/Full rate. Fast Associated Control Channel/Half rate. Frequency correction Burst (see Frequency correction burst). Fibre Channel Arbitration Loop. (Type of hard disc). Frequency Correction CHannel. A GSM broadcast control channel which carries information for frequency correction of the mobile (MS). Fault Collection Process (in BTS). Frame Check Sequence. Frequency Division Multiplex. Frequency Division Multiple Access. Fixed Dialling Number. Fault Diagnostic Procedure. Forward Error Correction. Front End Processor. Frame Erasure Ratio. For Further Study. Frequency Hopping. Forward Indicator Bit. Finite Impulse Response (filter type). Foreign Key. A database column attribute; the foreign key indicates an index into another table. Fault Management (at OMC). Frequency Modulation. Fault Management Initiated Clear. Fibre optic MUltipleXer. Frame Number. Identifies the position of a particular TDMA frame within a hyperframe. First Office Application. Fibre Optic eXtender. Full Rate. Refers to the current capacity of a data channel on the GSM air interface, that is, 8 simultaneous calls per carrier (see also HR Half Rate).
FACCH/F FACCH/H FB FC-AL FCCH
FCP FCS FDM FDMA FDN FDP FEC FEP FER FFS, FS FH FIB FIR FK FM FM FMIC FMUX FN FOA FOX FR
10TH JULY 95
G17
FRU Frequency correction
Field Replaceable Unit. Period of RF carrier less than one timeslot whose modulation bit stream allows frequency correction to be performed easily within an MS burst. Frequency Synchronization. Free Space Loss. The decrease in the strength of a radio signal as it travels between a transmitter and receiver. The FSL is a function of the frequency of the radio signal and the distance the radio signal has travelled from the point source. Forward Sequence Number. File Transfer, Access, and Management. An ASE which provides a means to transfer information from file to file (OMC). forwarded-to number. Fault Translation Process (in BTS). File Transfer Protocol.
FS FSL
FSN FTAM
ftn FTP FTP
G18
10TH JULY 95
G
G Interface Gateway MSC Interface between VLR and VLR. An MSC that provides an entry point into the GSM PLMN from another network or service. A gateway MSC is also an interrogating node for incoming PLMN calls. Gigabyte. Gigabit Interface Converter. Generic Clock board. System clock source, one per site (p/o BSS, BTS, BSC, IWF, RXCDR). Group Call Register. Generic DSP Processor board. Interchangeable with the XCDR board. GDP board configured for E1 link usage. GDP board configured for T1 link usage. Giga-Hertz (109). Group ID. A unique number used by the system to identify a users primary group. GSM Multiplexer Board (p/o BSC). GSM Manual Revision. Gateway Mobile-services Switching Centre (see Gateway MSC). Gaussian Minimum Shift Keying. The modulation technique used in GSM. GrouND. Grade of Service. GSM PLMN Area. General Protocol Converter. Generic Processor board. GSM generic processor board: a 68030 with 4 to 16 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR). Generic Processor board. GSM generic processor board: a 68040 with 32 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR). General Packet Radio Service. Global Positioning by Satellite. GSM Service Area. The area in which an MS can be reached by a fixed subscriber, without the subscribers knowledge of the location of the MS. A GSA may include the areas served by several GSM PLMNs. GSM System Area. The group of GSM PLMN areas accessible by GSM MSs. Groupe Spcial Mobile (the committee). Global System for Mobile communications (the system). GSM Mobile Station. GSM Public Land Mobile Network.
GB, Gbyte GBIC GCLK GCR GDP GDP E1 GDP T1 GHz GID GMB GMR GMSC GMSK GND GOS GPA GPC GPROC
GPROC2 GPRS GPS GSA
GSA GSM GSM GSM MS GSM PLMN
10TH JULY 95
G19
GSR GT GTE Guard period GUI GUI client GUI server
GSM Software Release. Global Title. Generic Table Editor. The Motorola procedure which allows users to display and edit MCDF input files. Period at the beginning and end of timeslot during which MS transmission is attenuated. Graphical User Interface. A computer used to display a GUI from an OMC-R GUI application which is beingbrun on a GUI server. A computer used to serve the OMC-R GUI application process running locally (on its processor) to other computers (Gui clients or other MMI processors). GateWaY (MSC/LR) interface to PSTN.
GWY
G20
10TH JULY 95
H
H Interface H-M HAD, HAP HANDO, Handover Interface between HLR and AUC. Human-Machine Terminals. HLR Authentication Distributor. HANDOver. The action of switching a call in progress from one radio channel to another radio channel. Handover allows established calls to continue by switching them to another radio resource, as when an MS moves from one BTS area to another. Handovers may take place between the following GSM entities: timeslot, RF carrier, cell, BTS, BSS and MSC. Hybrid Combining Unit. (Used in Horizonmacro). High level Data Link Control. High bit-rate Digital Subscriber Line. High Layer Compatibility. The HLC can carry information defining the higher layer characteristics of a teleservice active on the terminal. Home Location Register. The LR where the current location and all subscriber parameters of an MS are permanently stored. Heat Management System. The system that provides environmental control of the components inside the ExCell, TopCell and M-Cell cabinets. HandOver. (see HANDO above). Hand Portable Unit. Call hold supplementary service. Home PLMN. Half Rate. Refers to a type of data channel that will double the current GSM air interface capacity to 16 simultaneous calls per carrier (see also FR Full Rate). HandSet. High Speed Interface card. HLR Subscriber Management. Hopping Sequence Number. Home Units. Hardware. 2048 superframes. The longest recurrent time period of the frame structure.
HCU HDLC HDSL HLC
HLR
HMS
HO HPU HOLD HPLMN HR
HS HSI/S HSM HSN HU HW Hyperframe
10TH JULY 95
G21
I
I IA IA5 IADU IAM IAS IC IC IC(pref) ICB ICC ICM ICMP ID, Id IDN IDS IE IEC IEEE IEI I-ETS IF IFAM IM IMACS IMEI Information frames (RLP). Incomming Access (closed user group (CUG) SS (supplementary service)). International Alphanumeric 5. Integrated Antenna Distribution Unit. (The IADU is the equivalent of the Receive Matrix used on pre-M-Cell BTSs). Initial Address Message. Internal Alarm System. Integrated Circuit. Interlock Code (CUG SS). Interlock Code op the preferential CUG. Incoming Calls Barred. Integrated Circuit(s) Card. In-Call Modification. Internet Control Message Protocol. IDentification/IDentity/IDentifier. Integrated Digital Network. INFOMIX Database Server. (OMC-R relational database management system). Information Element (signalling). International Electrotechnical Commission. Institute of Electrical and Electronic Engineers. Information Element Identifier. Interim European Telecommunication Standard. Intermediate Frequency. Initial and Final Address Message. InterModulation. Intelligent Monitor And Control System. International Mobile station Equipment Identity. Electronic serial number that uniquely identifies the MS as a piece or assembly of equipment. The IMEI is sent by the MS along with request for service. IMMediate assignment message. International Mobile Subscriber Identity. Published mobile number (prior to ISDN) (see also MSISDN) that uniquely identifies the subscription. It can serve as a key to derive subscriber information such as directory number(s) from the HLR. Intelligent Network. Interrogating Node. A switching node that interrogates an HLR, to route a call for an MS to the visited MSC. IN Service.
IMM IMSI
IN IN INS
G22
10TH JULY 95
INS InterAlg Interworking
Intelligent Network Service. Interference Algorithm. A single interference algorithm in a cell. The general term used to describe the inter-operation of networks, services, supplementary services and so on. See also IWF. A recording period of time in which a statistic is pegged. The end of an interval. Input/Output. Intelligent Optimization Platform. Initialisation Process. Internet Protocol. Inter-Process Communication. INtermodulation Products. Intellectual PRoperty. Integrated Power Supply Module (48 V). (A hardware component). Indexed Sequential Access Method. International Switching Centre. Integrated Services Digital Network. An integrated services network that provides digital connections between user-network interfaces. Motorola Information Systems group (formally CODEX). International Organisation for Standardization. Informix Structured Query Language. ISDN User Part (of signalling system No. 7). Inactivity Test (Part of SCCP network connectivity). Information Transfer Capability. International Telecommunication Union. International Telecommunication Union Telecommunications Sector. InterWorking Function. A network functional entity which provides network interworking, service interworking, supplementary service interworking or signalling interworking. It may be a part of one or more logical or physical entities in a GSM PLMN. InterWorking MSC. InterWorking Unit.
Interval Interval expiry I/O IOS IP IP IPC IP, INP IPR IPSM IPX ISAM ISC ISDN
ISG ISO ISQL ISUP IT ITC ITU ITUTSS IWF
IWMSC IWU
10TH JULY 95
G23
K
k k K KAIO kb, kbit kbit/s, kbps kbyte Kc kHz Ki KIO KSW KSWX kW kilo (103). Windows size. Constraint length of the convolutional code. Kernal Asynchronous Input/Output. kilo-bit. kilo-bits per second. kilobyte. Ciphering key. A sequence of symbols that controls the operation of encipherment and decipherment. kilo-Hertz (103). Individual subscriber authentication Key (p/o authentication process of AUC). A class of processor. Kiloport SWitch board. TDM timeslot interchanger to connect calls (p/o BSS). KSW Expander half size board. Fibre optic distribution of TDM bus (p/o BSS). kilo-Watt.
G24
10TH JULY 95
L
L1 L2ML L2R Layer 1. Layer 2 Management Link. Layer 2 Relay function. A function of an MS and IWF that adapts a users known layer2 protocol LAPB onto RLP for transmission between the MT and IWF. L2R Bit Orientated Protocol. L2R Character Orientated Protocol. Layer 3. Location Area. An area in which an MS may move freely without updating the location register. An LA may comprise one or several base station areas. Location Area Code. Location Area Identity. The information indicating the location area in which a cell is located. Local Area Network. LAN Extender half size board. Fibre optic distribution of LAN to/from other cabinets (p/o BSS etc). Link Access Protocol Balanced (of ITUTSS Rec. x.25). Link Access Protocol Data. Link Access Protocol on the Dm channel. Inductor Capacitor (type of filter). Link Control Function. Local Communications Network. Link Control Processor. Local Exchange. Light Emitting Diode. Line Feed. Length Indicator. Line Identity. Lower Layer Compatibility. The LLC can carry information defining the lower layer characteristics of the terminal. Traffic channel with capacity lower than a Bm. LAN Monitor Process. Least Mean Square. Local Mobile Station Identity. A unique identity temporarily allocated to visiting mobile subscribers in order to speed up the search for subscriber data in the VLR, when the MSRN allocation is done on a per cell basis. Local Maintenance Terminal. Low Noise Amplifier. Last Number Dialled.
L2R BOP L2R COP L3 LA
LAC LAI LAN LANX LAPB LAPD LAPDm LC LCF LCN LCP LE LED LF LI LI LLC Lm LMP LMS LMSI
LMT LNA LND
10TH JULY 95
G25
Location area
An area in which a mobile station may move freely without updating the location register. A location area may comprise one or several base station areas. Linear Predictive Code. Local PLMN. Location Register. The GSM functional unit where MS location information is stored. The HLR and VLR are location registers. Link Stations Signalling Unit (Part of MTP transport system). Listener Side Tone Rating. Long Term Average. The value required in a BTSs GCLK frequency register to produce a 16.384 MHz clock. Local Terminal Emulator. Long Term Predictive. Line Terminating Unit. Local Units. Location Update. Length and Value.
LPC LPLMN LR
LSSU LSTR LTA LTE LTP LTU LU LU LV
G26
10TH JULY 95
M
M M M-Cell M&TS Mandatory. Mega (106). Motorola Cell. Maintenance and Troubleshooting. Functional area of Network Management software which (1) collects and displays alarms, (2) collects and displays Software/Hardware errors, and (3) activates test diagnostics at the NEs (OMC). Mobile Allocation. The radio frequency channels allocated to an MS for use in its frequency hopping sequence. Medium Access Control. Mobile Allocation Channel Number. A cell in which the base station antenna is generally mounted away from buildings or above rooftop level. Mobile Additional Function. Mobile Access Hunting supplementary service. Mobile Allocation Index. Mean Accumulated Intrinsic Down Time. MAINTenance. Mobile Allocation Index Offset. Mobile Application Part (of signalling system No. 7). The inter-networking signalling between MSCs and LRs and EIRs. Mobile Application Part Processor. Megabyte. Megabits per second. Motorola Cellular Advanced Processor. Mobile Country Code. Motorola Customer Data Format used by DataGen for simple data entry and retrieval. Malicious Call Identification supplementary service. Motorola Customer Support Centre. Main Control Unit for M-Cell2/6. Also referred to as the Micro Control Unit in software. Main Control Unit, with dual FMUX. (Used in M-Cellhorizon). Main Control Unit for M-Cell Micro sites (M-Cellm). Also referred to as the Micro Control Unit in software. The software subtype representation of the Field Replaceable Unit (FRU) for the MCU-m. Mediation Device. (mobile) Management (entity) - Data Link (layer). Maintenance Entity (GSM Rec. 12.00).
MA MAC MACN Macrocell MAF MAH MAI MAIDT MAINT MAIO MAP MAPP MB, Mbyte Mbit/s MCAP MCC MCDF MCI MCSC MCU MCUF MCU-m MCUm MD MDL ME
10TH JULY 95
G27
ME
Mobile Equipment. Equipment intended to access a set of GSM PLMN and/or DCS telecommunication services, but which does not contain subscriber related information. Services may be accessed while the equipment, capable of surface movement within the GSM system area, is in motion or during halts at unspecified points. Maintenance Entity Function (GSM Rec. 12.00). MultiFrame. Multi-Frequency (tone signalling type). MultiFunction block. Management. Manager. Message Handling System. Mobile Handling Service. Mega-Hertz (106). Maintenance Information. Management Information Base. A Motorola OMC-R database. There is a CM MIB and an EM MIB. Mobile Interface Controller. A cell in which the base station antenna is generally mounted below rooftop level. Radio wave propagation is by diffraction and scattering around buildings, the main propagation is within street canyons. minute(s). micro-second (106). Micro Base Control Unit. Management Information Tree. Name of a file on the Motorola OMC-R. Man Machine. Mobility Management. Mobile Management Entity. Middle Man Funnel process. Man Machine Interface. The method in which the user interfaces with the software to request a function or change parameters. A machine configured to use the OMC-R software from an MMI server. MMI client/MMI server. A computer which has its own local copy of the OMC-R software. It can run the OMC-R software for MMI clients to mount. Man Machine Language. The tool of MMI. Multiple Serial Interface Link. (see also 2Mbit/s link) Mobile Network Code. MaiNTenance.
MEF MF MF MF MGMT, mgmt MGR MHS MHS MHz MI MIB MIC Microcell
min ms mBCU MIT MM MM MME MMF MMI
MMI client MMI processor MMI server
MML MMS MNC MNT
G28
10TH JULY 95
MO MO/PP MOMAP MoU MPC MPH MPTY MPX MRC MRN MRP MS MSC MSCM MSCU msec MSI MSIN MSISDN
Mobile Originated. Mobile Originated Point-to-Point messages. Motorola OMAP. Memorandum of Understanding. Multi Personal Computer (was p/o OMC). (mobile) Management (entity) - PHysical (layer) [primitive]. MultiParTY (Multi ParTY) supplementary service. MultiPleXed. Micro Radio Control Unit. Mobile Roaming Number. Mouth Reference Point. Mobile Station. The GSM subscriber unit. Mobile-services Switching Centre, Mobile Switching Centre. Mobile Station Class Mark. Mobile Station Control Unit. millisecond (.001 second). Multiple Serial Interface board. Intelligent interface to two 2 Mbit/s digital links (see 2 Mbit/s link and DS-2) (p/o BSS). Mobile Station Identification Number. Mobile Station International ISDN Number. Published mobile number (see also IMSI). Uniquely defines the mobile station as an ISDN terminal. It consists of three parts: the Country Code (CC), the National Destination Code (NDC) and the Subscriber Number (SN). Mobile Station Roaming Number. A number assigned by the MSC to service and track a visiting subscriber. Message Signal Unit (Part of MTP transport system). A signal unit containing a service information octet and a signalling information field which is retransmitted by the signalling link control, if it is received in error. Mobile Terminated. Describes a call or short message destined for an MS. Mobile Termination. The part of the MS which terminates the radio transmission to and from the network and adapts terminal equipment (TE) capabilities to those of the radio transmission. MT0 is mobile termination with no support for terminal, MT1 is mobile termination with support for an S-type interface and MT2 is mobile termination with support for an R-type interface. Mobile-To-Mobile (call). Message Transfer Part. Mobile Terminated Point-to-Point messages. Mean Time Between Failures. Message Transfer LinK. MTP Transport Layer Link (A interface).
MSRN MSU
MT MT (0, 1, 2)
MTM MTP MT/PP MTBF MTK MTL
10TH JULY 95
G29
MTP MTTR Multiframe
Message Transfer Part. Mean Time To Repair. Two types of multiframe are defined in the system: a 26-frame multiframe with a period of 120 ms and a 51-frame multiframe with a period of 3060/13 ms. Mark Up. Multi User Mobile Station. Multiplexer.
MU MUMS MUX
G30
10TH JULY 95
N
N/W NB NBIN NCC NCELL NCH ND Network. Normal Burst (see Normal burst). A parameter in the hoping sequence. Network (PLMN) Colour Code. Neighbouring (of current serving) Cell. Notification CHannel. No Duplicates. A database column attribute meaning the column contains unique values (used only with indexed columns). National Destination Code. Network Determined User Busy. Network Element (Network Entity). Network Element Function block. Norme Europennes de Telecommunications. Frequency planning tool. Network Function. Network File System. Network Health Analyst. Optional OMC-R processor feature. Network Interface Card. Network Independent Clocking. Network Information Service. It allows centralised control of network information for example hostnames, IP addresses and passwords. Network Interface Unit. Network Interface Unit, micro. Network LinK processor(s). Newton metres. Network Management (manager). NM is all activities which control, monitor and record the use and the performance of resources of a telecommunications network in order to provide telecommunication services to customers/users at a certain level of quality. Network Management Application Service Element. Network Management Centre. The NMC node of the GSM TMN provides global and centralised GSM PLMN monitoring and control, by being at the top of the TMN hierarchy and linked to subordinate OMC nodes. National Mobile Station Identification number. Nordic Mobile Telephone system. No Nulls. A database column attribute meaning the column must contain a value in all rows. A period of modulated carrier less than a timeslot. Number Plan Identifier.
NDC NDUB NE NEF NET NETPlan NF NFS NHA NIC NIC NIS
NIU NIU-m NLK Nm NM
NMASE NMC
NMSI NMT NN Normal burst NPI
10TH JULY 95
G31
NRZ NSAP NSP NSS NT NT NTAAB NUA NUI NUP NV NVRAM nW
Non Return to Zero. Network Service Access Point. Network Service Provider. Network Status Summary. Network Termination. Non Transparent. New Type Approval Advisory Board. Network User Access. Network User Identification. National User Part (of signalling system No. 7). NonVolatile. Non-Volatile Random Access Memory. Nano-Watt (109).
G32
10TH JULY 95
O
O OA O&M OASCU Optional. Outgoing Access (CUG SS). Operations and Maintenance. Off-Air-Call-Set-Up. The procedure in which a telecommunication connection is being established whilst the RF link between the MS and the BTS is not occupied. Outgoing Calls Barred within the CUG. Oversized Voltage Controlled Crystal Oscillator. Optional for operators to implement for their aim. % OverFlow. IDS shutdown state. IDS normal operatng state. Operator Initiated Clear. Off_Line MIB. A Motorola DataGen database, used to modify and carry out Radio Frequency planning on multiple BSS binary files. Overall Loudness Rating. Operations and Maintenance Application Part (of signalling system No. 7) (was OAMP). Operations and Maintenance Centre. The OMC node of the GSM TMN provides dynamic O&M monitoring and control of the PLMN nodes operating in the geographical area controlled by the specific OMC. Operations and Maintenance Centre Gateway Part. (Iridium) Operations and Maintenance Centre GPRS Part. Operations and Maintenance Centre Radio Part. Operations and Maintenance Centre Switch Part. Operations and Maintenance Function (at BSC). Operations and Maintenance Link. Operation and Maintenance Processor. Operation and Maintenance System (BSCOMC). Operation and Maintenance SubSystem. Out Of Service. Originating Point Code. A part of the label in a signalling message that uniquely identifies, in a signalling network, the (signalling) origination point of the message. Olympus Radio Architecture Chipset. Operating System. Open Systems Interconnection. OSI Reference Model. Operation Systems Function block.
OCB OCXO OD OFL offline online OIC OLM
OLR OMAP OMC
OMC-G OMC-G OMC-R OMC-S OMF OML OMP OMS OMSS OOS OPC
ORAC OS OSI OSI RM OSF
10TH JULY 95
G33
OSF/MOTIF OSS Overlap
Open Software Foundation Motif. The basis of the GUI used for the Motorola OMC-R MMI. Operator Services System. Overlap sending means that digits are sent from one system to another as soon as they are received by the sending system. A system using ~ will not wait until it has received all digits of a call before it starts to send the digits to the next system. This is the opposite of en bloc sending where all digits for a given call are sent at one time.
G34
10TH JULY 95
P
PA PAB PABX PAD Paging Power Amplifier. Power Alarm Board. Private Automatic Branch eXchange. Packet Assembler/Disassembler facility. The procedure by which a GSM PLMN fixed infrastructure attempts to reach an MS within its location area, before any other network-initiated procedure can take place. CEPT 2 Mbit/s route through the BSS network. Processor Bus. Private Branch eXchange. Personal Computer. Paging CHannel. A GSM common control channel used to send paging messages to the MSs. Paging Channel Network. Physical Channel. Pulse Code Modulation (see also 2 Mbit/s link which is the physical bearer of PCM). Personal Communications Network. Preventative Cyclic Retransmission. A form of error correction suitable for use on links with long transmission delays, such as satellite links. Packet Control Unit (p/o GPRS). Picocell Control unit (p/o M-Cellaccess). Potential difference. Protocol Discriminator. Public Data. Power Distribution Board. Power Distribution Frame (MSC/LR). Public Data Networks. Power Distribution Unit. Protected Data Unit. Pan European Digital Cellular. A single incremental action modifying the value of a statistic. Modifying a statistical value. Packet Handler. PHysical (layer). Packet Handler Interface. Presentation Indicator. A cell site where the base station antenna is mounted within a building. Protocol Implementation Conformance Statement.
PATH PBUS PBX PC PCH PCHN PCHN PCM PCN PCR
PCU PCU pd PD PD PDB PDF PDN PDU PDU PEDC Peg Pegging PH PH PHI PI Picocell PICS
10TH JULY 95
G35
PID PIM PIN PIN PIX PIXT PK Plaintext PlaNET PLL PLMN PM PM-UI PMA PMS PMUX PN PNE POI POTS p/o pp, p-p PP ppb PPE ppm Pref CUG Primary Cell
Process IDentifier/Process ID. PCM Interface Module (MSC). Personal Identification Number. Problem Identification Number. Parallel Interface Extender half size board. Customer alarm interface (p/o BSS). Protocol Implementation eXtra information for Testing. Primary Key. A database column attribute, the primary key is a not-null, non-duplicate index. Unciphered data. Frequency planning tool. Phase Lock Loop (refers to phase locking the GCLK in the BTS). Public Land Mobile Network. The mobile communications network. Performance Management. An OMC application. Performance Management User Interface. Prompt Maintenance Alarm. An alarm report level; immediate action is necessary (see also DMA). Pseudo MMS. PCM MUltipleXer. Permanent Nucleus (of GSM). Prsentation des Normes Europennes. Point of Interconnection (with PSTN). Plain Old Telephone Service (basic telephone services). Part of. Peak-to-peak. Point-to-Point. Parts per billion. Primative Procedure Entity. Parts per million (x 106). Preferential CUG. A cell which is already optimized in the network and has a co-located neighbour whose cell boundary follows the boundary of the said cell. The primary cell has a preferred band equal to the frequency type of the coincident cell. Programmable Read Only Memory. Location probability. Periodic Supervision of Accessability. Presentation Services Access Point. Power Supply Module.
PROM Ps PSA PSAP PSM
G36
10TH JULY 95
PSPDN
Packet Switched Public Data Network. Public data communications network. x.25 links required for NE to OMC communications will probably be carried by PSPDN. Public Switched Telephone Network. The UK land line telephone network. Power Supply Unit. Pure Sine Wave. Public Telecommunications Operator. Price per Unit Currency Table. Permanent Virtual Circuit. Pass Word. Power. Private eXchange Public Data Network.
PSTN PSU PSW PTO PUCT PVC PW PWR PXPDN
10TH JULY 95
G37
Q
QA Q3 Q-adapter QAF QEI QIC QOS Quiescent mode Q (Interface) Adapter. Interface between NMC and GSM network. Used to connect MEs and SEs to TMN (GSM Rec. 12.00). Q-Adapter Function. Quad European Interface. Interfaces four 2 Mbit/s circuits to TDM switch highway (see MSI). Quarter Inch Cartridge (Data storage format). Quality Of Service. IDS intermediate state before shutdown.
G38
10TH JULY 95
R
R Value of reduction of the MS transmitted RF power relative to the maximum allowed output power of the highest power class of MS (A). RAndom mode request information field. Random Access Burst. Random Access Control CHannel. A GSM common control channel used to originate a call or respond to a page. Random Access CHannel. Random Access Memory. RANDom number (used for authentication). Receive Antenna Transceiver Interface. Rate Adaptation. Remote BSS Diagnostic System (a discontinued Motorola diagnostic facility). Residual Bit Error Ratio. Remote Base Transceiver Station. Radio Control Board (p/o DRCU). Radio Channel Identifier. Radio Control Processor. Radio Channel Unit. Contains transceiver, digital control circuits, and power supply (p/o BSS) (see DRCU). Receiver. Relational DataBase Management System (INFORMIX). Radio Digital Interface System. Restricted Digital Information. Reference Distribution Module. Relative Distinguished Name. A series of RDN form a unique identifier, the distinguished name, for a particular network element. RECommendation. REJect(ion). RELease. Residual Excited Linear Predictive. RELP Long Term Prediction. A name for GSM full rate (see full rate). Resynchronize/resynchronization. REQuest. A Motorola DataGen utility for producing an MMI script from a binary object database. Radio Frequency.
RA RAB RACCH RACH RAM RAND RATI RAx RBDS RBER RBTS RCB RCI RCP RCU RCVR RDBMS RDI RDIS RDM RDN
REC, Rec REJ REL RELP RELP-LTP resync REQ Revgen RF
10TH JULY 95
G39
RFC, RFCH
Radio Frequency Channel. A partition of the system RF spectrum allocation with a defined bandwidth and centre frequency. Receiver Front End (shelf). Receiver Front End Board (p/o DRCU II). Radio Frequency Interference. Radio Frequency Module. Reduced TDMA Frame Number. Reserved for Future Use. Network cable/Connector type. Reduced Instruction Set Computer. Remote login. Release Complete. Radio Link Protocol. An ARQ protocol used to transfer user data between an MT and IWF. See GSM 04.22. Receiver Loudness Rating. ReLeaSeD. Root Mean Square (value). Remote Mobile Switching Unit. Table of 128 integers in the hopping sequence. Read Only Memory. Remote Operations Service Element. An ASE which carries a message between devices over an association established by ASCE (a CCITT specification for O & M) (OMC). Time period between transmit and receive instant of a timeslot in the BTS, propagation determined by the response behaviour of the MS and the MS to BTS delay distance. Regular Pulse Excited. Regular Pulse Excitation - Long Term Prediction. The GSM digital speech coding scheme. Recognised Private Operating Agency. Read Privilege Required. Access to the column is allowed only for privileged accounts. Radio Resource management. Receive Ready (frame). Radio Resource State Machine. Standard serial interface. Radio System Entity. Radio Signalling Link. Radio System Link Function. Radio System Link Processor. Radio SubSystem (replaced by BSS). Received Signal Strength Indicator.
RFE RFEB RFI RFM RFN RFU RJ45 RISC RL RLC RLP RLR RLSD RMS RMSU RNTABLE ROM ROSE
Roundtrip
RPE RPE-LTP RPOA RPR RR RR RRSM RS232 RSE RSL RSLF RSLP RSS RSSI
G40
10TH JULY 95
RSZI RTC RTE RTF RTF RTS RU Run level Rx RXCDR RXF RXLEV-D RXLEV-U RXQUAL-D RXQUAL-U RXU
Regional Subscription Zone Identity. Remotely Tuneable Channel Combiner. Remote Terminal Emulator. Radio Transceiver Function. Receive Transmit Functions. Request to Send. Method of flow control (RS232 Interface). Rack Unit. System processor operating mode. Receive(r). Remote Transcoder. Receive Function (of the RTF). Received signal level downlink. Received signal level uplink. Received signal quality downlink. Received signal quality uplink. Remote Transcoder Unit. The shelf which houses the remote transcoder modules in a BSSC cabinet at a remote transcoder site.
10TH JULY 95
G41
S
S/W SABM SABME SACCH SoftWare. Set Asynchronous Balanced Mode. A message which establishes the signalling link over the air interface. SABM Extended. Slow Associated Control CHannel. A GSM control channel used by the MS for reporting RSSI and signal quality measurements. Slow Associated Control CHannel/SDCCH/4. Slow Associated Control CHannel/SDCCH/8. Slow Associated Control CHannel/Traffic channel. Slow Associated Control CHannel/Traffic channel Full rate. Slow Associated Control CHannel/Traffic channel Half rate. A brand of trunk test equipment. Service Access Point. In the reference model for OSI, SAPs of a layer are defined as gates through which services are offered to an adjacent higher layer. System Audits Process. Service Access Point Indicator (identifier). Surface Acoustic Wave. Synchronization Burst (see Synchronization burst). Serial Bus. Service Centre (used for Short Message Service). Service Code. System Change Control Administration. Software module which allows full or partial software download to the NE (OMC). Signalling Connection Control Part (6-8). Speech Coding Experts Group (of GSM). Synchronization CHannel. A GSM broadcast control channel used to carry information for frame synchronization of MSs and identification of base stations. Status Control Interface. Serial Communication Interface Processor. Status Control Manager. Sub-Channel Number. One of the parameters defining a particular physical channel in a BS. Service Control Point (an intelligent network entity). Small Computer Systems Interface. Slim Channel Unit. Slim Channel Unit for GSM900. Stand-alone Dedicated Control CHannel. A GSM control channel where the majority of call setup occurs. Used for MS to BTS communications before MS assigned to TCH.
SACCH/C4 SACCH/C8 SACCH/T SACCH/TF SACCH/TH SAGE SAP
SAP SAPI SAW SB SBUS SC SC SCCA
SCCP SCEG SCH
SCI SCIP SCM SCN SCP SCSI SCU SCU900 SDCCH
G42
10TH JULY 95
SDL SDT SDU SDR SE Secondary Cell
Specification Description Language. SDL Developement Tool. Service Data Unit. Special Drawing Rights (an international basket currency for billing). Support Entity (GSM Rec. 12.00). A cell which is not optimized in the network and has a co-located neighbour whose cell boundary follows the boundary of the said cell. The secondary cell has a preferred band the same as that of its own frequency type. Support Entity Function (GSM Rec.12.00). Slow Frequency Hopping. Screening Indicator. Service Interworking. Supplementary Information. Supplementary Information A. Silence Descriptor. Signal Information Field. The bits of a message signal unit that carry information for a certain user transaction; the SIF always contains a label. Subscriber Identity Module. Removable module which is inserted into a mobile equipment; it is considered as part of the MS. It contains security related information (IMSI, Ki, PIN), other subscriber related information and the algorithms A3 and A8. Single Inline Memory module. System Integrated Memory Module. Service Information Octet. Eight bits contained in a message signal unit, comprising the service indicator and sub-service field. BSC, BTS or collocated BSC-BTS site. Serial Interface eXtender. Converts interface levels to TTL levels. Used to extend 2 serial ports from GPROC to external devices (RS232, RS422, and fibre optics). Secondary Key. A database column attribute, the secondary key indicates an additional index and/or usage as a composite key. Signalling Link. Serial Link. Send Loudness Rating. Signalling Link Test Message. Switch Manager. Summing Manager. System Management Application Entity (CCITT Q795, ISO 9596). Short Message Cell Broadcast.
SEF SFH SI SI SI SIA SID SIF
SIM
SIMM SIMM SIO
SITE SIX
SK
SL SLNK SLR SLTM SM SM SMAE SMCB
10TH JULY 95
G43
SME SMG SMP SMS SMSCB SMS-SC SMS/PP Smt SN SND SNDR SNR SOA SP
Short Message Entity. Special Mobile Group. Motorola Software Maintenance Program. Short Message Service. Short Message Service Cell Broadcast. Short Message Service - Service Centre. Short Message Service/Point-to-Point. Short message terminal. Subscriber Number. SeND. SeNDeR. Serial NumbeR. Suppress Outgoing Access (CUG SS). Service Provider. The organisation through which the subscriber obtains GSM telecommunications services. This may be a network operator or possibly a separate body. Signalling Point. Special Product. SPare. Signalling Point Code. Suppress Preferential CUG. Signalling Point Inaccessible. Single Path Preselector. Signal Quality Error. Structured Query Language. Service Request Distributor. Signed RESponse (authentication). Supplementary Service. A modification of, or a supplement to, a basic telecommunication service. System Simulator. SCCP messages, Subsystem-allowed (see CCITT Q.712 para 1.15). Site System Audits Processor. Supplementary Service Control string. Subservice Field. The level 3 field containing the network indicator and two spare bits. Signalling State Machine. SubSystem Number. Service Switching Point (an intelligent network element). SCCP messages, Subsystem-prohibited (see CCITT Q.712 para 1.18). SubSystem Prohibited message.
SP SP SP SPC SPC SPI SPP SQE SQL SRD SRES SS SS SSA SSAP SSC SSF SSM SSN SSP SSP SSP
G44
10TH JULY 95
SSS SS7 STAN STAT stats STC STMR SUERM STP Superframe Super user SURF SVC SVM SVN SW SWFM sync Synchronization burst
Switching SubSystem (comprising the MSC and the LRs). ANSI Signalling System No. 7 (alias C7). Statistical ANalysis (processor). STATistics. Statistics. System Timing Controller. Side Tone Masking rating. Signal Unit Error Rate Monitor. Signalling Transfer Point. 51 traffic/associated control multiframes or 26 broadcast/common control multiframes (period 6.12s). User account that can access all files, regardless of protection settings, and control all user accounts. Sectorized Universal Receiver Front-end (Used in Horizonmacro). Switch Virtual Circuit. SerVice Manager. Software Version Number. Software. SoftWare Fault Management. synchronize/synchronization. Period of RF carrier less than one timeslot whose modulation bit stream carries information for the MS to synchronize its frame to that of the received signal. SYStem. SYStem GENeration. The Motorola procedure for loading a configuration database into a BTS.
SYS SYSGEN
10TH JULY 95
G45
T
T T T T43 Timer. Transparent. Type only. Type 43 Interconnect Board. Provides interface to 12 unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for 2 Mbit/s circuits (See BIB). Terminal Adaptor. A physical entity in the MS providing terminal adaptation functions (see GSM 04.02). Timing Advance. Type Approval Code. Total Access Communications System (European analogue cellular system). Terminal Adaptation Function. Transmit Antenna Transceiver Interface. The TATI consists of RF combining equipments, either Hybrid or Cavity Combining. (See CCB). Transparent Asynchronous Transmitter/Receiver Interface (physical layer). To Be Determined. Technical Basis for Regulation. TDM Bus. Transaction Capabilities. Transaction Capabilities Application Part (of Signalling System No. 7). TATI Control Board. Traffic CHannel. GSM logical channels which carry either encoded speech or user data. A full rate TCH. A full rate TCH at 2.4 kbit/s. A full rate TCH at 4.8 kbit/s. A full rate TCH at 9.6 kbit/s. A full rate Speech TCH. A half rate TCH. A half rate TCH at 2.4 kbit/s. A half rate TCH at 4.8 kbit/s. A half rate Speech TCH). Transceiver Control Interface. Transmission Control Protocol/Internet Protocol. Technical Commitee Technical Report. Transceiver Control Unit. Twin Duplexed Filter. (Used in M-Cellhorizon). Time Division Multiplexing.
TA TA TAC TACS TAF TATI
TAXI TBD TBR TBUS TC TCAP TCB TCH TCH/F TCH/F2.4 TCH/F4.8 TCH/F9.6 TCH/FS TCH/H TCH/H2.4 TCH/H4.8 TCH/HS TCI TCP/IP TC-TR TCU TDF TDM
G46
10TH JULY 95
TDMA TDU TE
Time Division Multiple Access. TopCell Digital Unit. Terminal Equipment. Equipment that provides the functions necessary for the operation of the access protocols by the user. Terminal endpoint identifier. Terminal Equipment Identity. TEMPorary. TEST control processor. TransFer Allowed. TransFer Prohibited. Trivial File Transfer Protocol. Transaction Identifier. The multiplex subdivision in which voice and signalling bits are sent over the air. Each RF carrier is divided into 8 timeslots. A signal sent by the BTS to the MS. It enables the MS to advance the timing of its transmission to the BTS so as to compensate for propagation delay. Type, Length and Value. Traffic Manager. TDM Modem Interface board. Provides analogue interface from IWF to modems for 16 circuits (p/o IWF). Traffic Metering and Measuring. Telecommunications Management Network. The implementation of the Network Management functionality required for the PLMN is in terms of physical entities which together constitute the TMN. Temporary Mobile Subscriber Identity. A unique identity temporarily allocated by the MSC to a visiting mobile subscriber to process a call. May be changed between calls and even during a call, to preserve subscriber confidentiality. Timeslot Number. Type Of Number. Channels which carry users speech or data (see also TCH). Equivalent to an erlang. Sequence of modulating bits employed to facilitate timing recovery and channel equalization in the receiver. Transcoder Rate Adaption Unit. TopCell Radio unit. Transceiver(s). A network component which can serve full duplex communication on 8 full-rate traffic channels according to specification GSM 05.02. If Slow Frequency Hopping (SFH) is not used, then the TRX serves the communication on one RF carrier. Technical Specification.
Tei TEI TEMP TEST TFA TFP TFTP TI Timeslot
Timing advance
TLV TM TMI TMM TMN
TMSI
TN TON Traffic channels Traffic unit Training sequence TRAU TRU TRX
TS
10TH JULY 95
G47
TS TS TSA TSA TSDA TSC TSI TSDI TSM TSW TTCN TTL TTY TU TUP TV Tx TXF TXPWR
TeleService. TimeSlot (see Timeslot). TimeSlot Acquisition. TimeSlot Assignment. Transceiver Speech & Data Interface. Training Sequence Code. TimeSlot Interchange. Transceiver Speech and Data Interface. Transceiver Station Manager. Timeslot SWitch. Tree and Tabular Combined Notation. Transistor to Transistor Logic. TeleTYpe (refers to any terminal). Traffic Unit. Telephone User Part (SS7). Type and Value. Transmit(ter). Transmit Function (of the RTF). Transmit PoWeR. Tx power level in the MS_TXPWR_REQUEST and MS_TXPWR_CONF parameters. Transmit Bandpass Filter.
TxBPF
G48
10TH JULY 95
U
UA Unnumbered Acknowledgment. A message sent from the MS to the BSS to acknowledge release of radio resources when a call is being cleared. Unrestricted Digital Information. User Datagram Protocol. User Determined User Busy. Ultra High Frequency. Unnumbered Information (Frame). Union International des Chemins de Fer. User ID. Unique number used by the system to identify the user. Upload (of software or database from an NE to a BSS). Air interface. Universal Mobile Telecommunication System. Uniform PCM Interface (13 bit). Up to Date. Physical link from the MS towards the BTS (MS transmits, BTS receives). Uninterruptable Power Supply. User Part Unavailable. That part of the burst used by the demodulator; differs from the full burst because of the bit shift of the I and Q parts of the GMSK signal. Unstructured Supplementary Service Data. User-to-User Signalling supplementary service.
UDI UDP UDUB UHF UI UIC UID UL Um UMTS UPCMI UPD Uplink UPS UPU Useful part of burst
USSD UUS
10TH JULY 95
G49
V
V VA VAD VAP VBS VC VCO VCXO VDU VGCS VLR Value only. Viterbi Algorithm (used in channel equalizers). Voice Activity Detection. A process used to identify presence or absence of speech data bits. VAD is used with DTX. Videotex Access Point. Voice Broadcast Service. Virtual Circuit. Voltage Controlled Oscillator. Voltage Controlled Crystal Oscillator. Visual Display Unit. Voice Group Call Service. Visitor Location Register. A GSM network element which provides a temporary register for subscriber information for a visiting subscriber. Often a part of the MSC. Very Large Scale Integration (in ICs). Visited MSC. (Recommendation not to be used). Voice Operated Transmission. Visited PLMN. Videotex Service Centre. Send state variable. Vehicular Speaker Phone. Voltage Standing Wave Ratio. The components dedecated to Videotex service.
VLSI VMSC VOX VPLMN VSC V(SD) VSP VSWR VTX host
G50
10TH JULY 95
W
WAN WPA WS Wide Area Network. Wrong Password Attempts (counter). Work Station. The remote device via which O&M personnel execute input and output transactions for network management purposes. Work Station Function block. World Wide Web.
WSF WWW
10TH JULY 95
G51
X
X.25 X.25 link XBL XCB XCDR XCDR board CCITT specification and protocols for public packet-switched networks (see PSPDN). A communications link which conforms to X.25 specifications and uses X.25 protocol (NE to OMC links). Transcoder to BSS Link. The carrier communications link between the Transcoder (XCDR) and the BSS. Transceiver Control Board (p/o Transceiver). Full-rate Transcoder. Provides speech transcoding and 4:1 submultiplexing (p/o BSS, BSC or XCDR). The circuit board required to perform speech transcoding at the BSS or (R)XCDR). Also known as the MSI (XCDR) board. Interchangeable with the GDP board. Transfer. eXchange IDentifier. X terminal window.
XFER XID X-Term
G52
10TH JULY 95
Z
ZC Zone Code
10TH JULY 95
G53
G54
10TH JULY 95

Capacity Enhancing Techniques and Multi Layer Systems

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Capacity Enhancing Techniques and Multi Layer Systems

Încărcat de

Drepturi de autor:

Formate disponibile

CHAPTER 1

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

COURSE CODE SYS12

VERSION 1 REV 1 GSM SOFTWARE RELEASE 7

WILL NOT BE UPDATED

COURSE FOR TRAINING CODE PURPOSES ONLY SYS12 THIS MANUAL

GSM Software Release GSR7

E Motorola 2002 All Rights Reserved Printed in the UK.

EMOTOROLA LTD. 2004

Copyrights, notices and trademarks

EMOTOROLA LTD. 2004

Chapter 1 Introduction to Capacity Enhancing Techniques and Multilayer Systems

Extended Range Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3 Deployment of Microcellular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EMOTOROLA LTD. 2004

Chapter 4 Microcellular Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EMOTOROLA LTD. 2004

477 484 484 484

Chapter 5 Capacity Enhancing Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EMOTOROLA LTD. 2004

Chapter 6 Adaptive MultiRate and HalfRate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7 Planning of Microcells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EMOTOROLA LTD. 2004

742 742 744 744 746 746 746 746 748

EMOTOROLA LTD. 2004

EMOTOROLA LTD. 2004

EMOTOROLA LTD. 2004

EMOTOROLA LTD. 2004

Special key sequences

EMOTOROLA LTD. 2004

Reporting safety issues

Reporting safety issues

EMOTOROLA LTD. 2004

Warnings and cautions

Warnings and cautions

Example and format

Failure to comply with warnings

Example and format

EMOTOROLA LTD. 2004

EMOTOROLA LTD. 2004

Potentially hazardous voltage

EMOTOROLA LTD. 2004

EMOTOROLA LTD. 2004

Devices sensitive to static

Devices sensitive to static

Special handling techniques

EMOTOROLA LTD. 2004

Introduction to Capacity Enhancing Techniques and Multilayer Systems

EMOTOROLA LTD. 2004

EMOTOROLA LTD. 2004

Introduction to Capacity Enhancing Techniques and Multilayer Systems

Introduction to Capacity Enhancing Techniques and Multilayer Systems

EMOTOROLA LTD. 2004

EMOTOROLA LTD. 2004

EMOTOROLA LTD. 2004

EMOTOROLA LTD. 2004

S Frequency Reuse Pattern (omnicell) S 7 Cell Reuse

EMOTOROLA LTD. 2004

4 x 3 Frequency Reuse Pattern

EMOTOROLA LTD. 2004

Four Site Pattern

EMOTOROLA LTD. 2004