SYSTEM INFORMATION BSS EQUIPMENT PLANNING

GSM SOFTWARE RELEASE 9

GSR9

68P02900W21-S

SYSTEM INFORMATION BSS EQUIPMENT PLANNING

GSM SOFTWARE RELEASE 9

68P02900W21-S

GSR9

System Information: BSS Equipment Planning

2004 - 2007 Motorola, Inc. All Rights Reserved

68P02900W21-S 01 Feb 2007

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 Motorola and the Motorola logo 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. CE Compliance The CE mark confirms Motorola Ltds statement of compliance with EU directives applicable to this product. Copies of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can be obtained from the local Motorola representative or the CNRC helpdesk, contact details : Email: mailto:csc.emea@motorola.com Tel: +44 (0) 1793 565 444

01 Feb 2007

Table of Contents

Contents
System Information: BSS Equipment Planning Issue status of this manual ............................................................................................................................................ 2 Version information ................................................................................................................................................ 2 Resolution of Service Requests ............................................................................................................................. 2 Incorporation of CDCNs......................................................................................................................................... 3 General information ....................................................................................................................................................... 4 Purpose ................................................................................................................................................................. 4 Feature references................................................................................................................................................. 4 Cross references.................................................................................................................................................... 5 Data encryption...................................................................................................................................................... 5 Text conventions.................................................................................................................................................... 6 Reporting safety issues ................................................................................................................................................. 7 Procedure .............................................................................................................................................................. 7 Warnings and cautions .................................................................................................................................................. 8 Warnings................................................................................................................................................................ 8 Failure to comply with warnings ............................................................................................................................. 8 Cautions................................................................................................................................................................. 8 General warnings .......................................................................................................................................................... 9 Warning labels ....................................................................................................................................................... 9 Specific warnings ................................................................................................................................................... 9 General cautions ......................................................................................................................................................... 12 Caution labels ...................................................................................................................................................... 12 Specific cautions .................................................................................................................................................. 12 Devices sensitive to static ........................................................................................................................................... 13 Special handling techniques ................................................................................................................................ 13 Caring for the environment .......................................................................................................................................... 14 Disposal of Motorola Networks equipment in EU countries ................................................................................. 14 Disposal of Motorola Networks equipment in non-EU countries .......................................................................... 14 Motorola manual set .................................................................................................................................................... 15 Ordering manuals and CD-ROMs ........................................................................................................................ 15 Manual amendment..................................................................................................................................................... 16 GMR availability ................................................................................................................................................... 16

68P02900W21-S 01 Feb 2007 i

Contents

CDCN availability ................................................................................................................................................. 16 CDCN instructions ............................................................................................................................................... 16 CDCN amendment record ........................................................................................................................................... 17

Chapter 1 Introduction to planning.............................................................................................................. 1-1

Manual overview......................................................................................................................................................... 1-2 Introduction ......................................................................................................................................................... 1-2 Contents.............................................................................................................................................................. 1-2 BSS equipment overview ........................................................................................................................................... 1-4 System architecture ............................................................................................................................................ 1-4 System components ........................................................................................................................................... 1-5 BSS features .............................................................................................................................................................. 1-8 Planning impacts................................................................................................................................................. 1-8 Diversity .............................................................................................................................................................. 1-8 Frequency hopping ............................................................................................................................................. 1-9 Short Message Service, Cell Broadcast (SMS CB)............................................................................................. 1-9 Code Storage Facility Processor (CSFP).......................................................................................................... 1-10 PCU for GPRS upgrade .................................................................................................................................... 1-10 Enhanced-GPRS (EGPRS)............................................................................................................................... 1-10 Adaptive Multi-Rate (AMR) ............................................................................................................................... 1-11 GSM half rate.................................................................................................................................................... 1-12 LoCation Services (LCS)................................................................................................................................... 1-13 BSC Reset Management (BRM) ....................................................................................................................... 1-13 Advanced Speech Call Item (ASCI) .................................................................................................................. 1-14 VersaTRAU backhaul for EGPRS..................................................................................................................... 1-14 Quality of Service (QoS) ................................................................................................................................... 1-15 QoS2................................................................................................................................................................. 1-16 Increased Network Capacity (Huge BSC) ......................................................................................................... 1-17 Improved Timeslot Sharing (ITS) ...................................................................................................................... 1-17 Enhanced BSC capacity using DSW2............................................................................................................... 1-18 High Speed MTL ............................................................................................................................................... 1-18 Addition of new BSC/PCU software (PXP) and hardware (PSI2) to increase GPRS capacity (ePCU) ............. 1-18 High bandwidth interconnect between BSC and PCU (PSI2) ........................................................................... 1-18 Dual Transfer Mode .......................................................................................................................................... 1-19 CTU2-D............................................................................................................................................................. 1-19 96 MSIs............................................................................................................................................................. 1-21 BSS planning overview............................................................................................................................................. 1-22 Introduction ....................................................................................................................................................... 1-22 Background information .................................................................................................................................... 1-22 Planning methodology....................................................................................................................................... 1-23

68P02900W21-S ii 01 Feb 2007

Contents

Acronyms ................................................................................................................................................................. 1-25 Acronym list ...................................................................................................................................................... 1-25

Chapter 2 Transmission systems ................................................................................................................ 2-1

BSS interfaces............................................................................................................................................................ 2-2 Introduction ......................................................................................................................................................... 2-2 Interconnecting the BSC and BTSs ............................................................................................................................ 2-4 Introduction ......................................................................................................................................................... 2-4 Interconnection rules........................................................................................................................................... 2-4 Network topology........................................................................................................................................................ 2-6 Introduction ......................................................................................................................................................... 2-6 Star connection ................................................................................................................................................... 2-7 Daisy chain connection ....................................................................................................................................... 2-8 Daisy chain planning........................................................................................................................................... 2-8 Aggregate Abis ................................................................................................................................................. 2-10 RTF path fault containment............................................................................................................................... 2-14 16 kbit/s RSL .................................................................................................................................................... 2-16 16 kbit/s XBL..................................................................................................................................................... 2-19 Dynamic allocation of RXCDR to BSC circuits (DARBC).................................................................................. 2-20 Managed HDSL on micro BTSs ............................................................................................................................... 2-22 Introduction ....................................................................................................................................................... 2-22 Integrated HDSL interface ................................................................................................................................ 2-22 General HDSL guidelines ................................................................................................................................. 2-24 Microcell system planning................................................................................................................................. 2-24

Chapter 3 BSS cell planning......................................................................................................................... 3-1

Planning tools ............................................................................................................................................................. 3-3 Introduction ......................................................................................................................................................... 3-3 GSM frequency spectrum........................................................................................................................................... 3-4 GSM900 frequency spectrum ............................................................................................................................. 3-4 DCS1800 frequency spectrum ............................................................................................................................ 3-5 Absolute radio frequency channel capacity......................................................................................................... 3-5 Modulation techniques and channel spacing ...................................................................................................... 3-6 Traffic capacity ........................................................................................................................................................... 3-8 Dimensioning ...................................................................................................................................................... 3-8 Channel blocking ................................................................................................................................................ 3-8 Traffic flow .......................................................................................................................................................... 3-9 Grade of service.................................................................................................................................................. 3-9 Adaptive multi-rate (AMR) ........................................................................................................................................ 3-10 Introduction ....................................................................................................................................................... 3-10 Capacity and coverage ..................................................................................................................................... 3-10

68P02900W21-S 01 Feb 2007 iii

Contents

Quality of service .............................................................................................................................................. 3-11 Applications....................................................................................................................................................... 3-12 Migration to AMR half rate ................................................................................................................................ 3-13 Interoperability with GSM half rate .................................................................................................................... 3-13 Interoperability with EGPRS.............................................................................................................................. 3-13 GSM half rate ........................................................................................................................................................... 3-14 Introduction ....................................................................................................................................................... 3-14 Capacity and coverage ..................................................................................................................................... 3-14 Quality of service .............................................................................................................................................. 3-14 Applications....................................................................................................................................................... 3-15 Migration to half rate ......................................................................................................................................... 3-16 Interoperability with AMR half rate .................................................................................................................... 3-16 Interoperability with EGPRS.............................................................................................................................. 3-16 Propagation effects on GSM frequencies ................................................................................................................. 3-17 Propagation production ..................................................................................................................................... 3-17 Decibels ............................................................................................................................................................ 3-17 Fresnel zone ..................................................................................................................................................... 3-19 Radio refractive index (RRI).............................................................................................................................. 3-20 Environmental effects on propagation............................................................................................................... 3-23 Attenuation........................................................................................................................................................ 3-23 Multipath propagation........................................................................................................................................ 3-26 GSM900 path loss ............................................................................................................................................ 3-38 Path loss GSM900 against DCS1800 ............................................................................................................... 3-39 Frequency re-use ..................................................................................................................................................... 3-41 Introduction ....................................................................................................................................................... 3-41 Re-use pattern .................................................................................................................................................. 3-42 Carrier/Interference (C/I) ratio ........................................................................................................................... 3-44 Sources of interference ..................................................................................................................................... 3-45 Sectorization of sites ......................................................................................................................................... 3-46 Overcoming adverse propagation effects ................................................................................................................. 3-47 Hardware techniques ........................................................................................................................................ 3-47 Error protection and detection........................................................................................................................... 3-48 GSM speech channel encoding for full rate ...................................................................................................... 3-53 GSM speech channel encoding for enhanced full rate...................................................................................... 3-55 GSM speech channel encoding for half rate ..................................................................................................... 3-56 GSM speech channel encoding for AMR full rate ............................................................................................. 3-57 GSM speech channel encoding for AMR half rate ............................................................................................ 3-58 Link adaptation for AMR channels .................................................................................................................... 3-60 GSM control channel encoding ......................................................................................................................... 3-61

68P02900W21-S iv 01 Feb 2007

Contents

GSM circuit-switched data channel encoding ................................................................................................... 3-62 Mapping logical channels in the TDMA frame structure.................................................................................... 3-64 GPRS channel coding schemes ....................................................................................................................... 3-70 EGPRS channel coding schemes ..................................................................................................................... 3-76 64 kbit/s TRAU for EGPRS ............................................................................................................................... 3-86 Link adaptation (LA) in GPRS/EGPRS ............................................................................................................. 3-87 Voice activity detection (VAD)........................................................................................................................... 3-87 Discontinuous transmission (DTX).................................................................................................................... 3-88 Receive diversity............................................................................................................................................... 3-90 Subscriber environment............................................................................................................................................ 3-93 Subscriber hardware......................................................................................................................................... 3-93 Environment...................................................................................................................................................... 3-93 Distribution ........................................................................................................................................................ 3-94 Hand portable subscribers ................................................................................................................................ 3-95 Future planning ................................................................................................................................................. 3-96 Microcellular solution ................................................................................................................................................ 3-97 Layered architecture ......................................................................................................................................... 3-97 Combined cell architecture ............................................................................................................................... 3-97 Combined cell architecture structure................................................................................................................. 3-98 Expansion solution............................................................................................................................................ 3-99 Frequency planning ................................................................................................................................................ 3-100 Introduction ..................................................................................................................................................... 3-100 Rules for Synthesizer Frequency Hopping (SFH) ........................................................................................... 3-100 Rules for BaseBand Hopping (BBH) ............................................................................................................... 3-103 Inter-radio access technology (2G-3G) cell reselection and handovers ................................................................. 3-105 Introduction ..................................................................................................................................................... 3-105 2G-3G handover description ........................................................................................................................... 3-105 Impact of 2G-3G handovers on GSM system architecture.............................................................................. 3-106 System consideration...................................................................................................................................... 3-106 Dual Transfer Mode................................................................................................................................................ 3-107 DTM Timeslots planning considerations ......................................................................................................... 3-107 System considerations.................................................................................................................................... 3-109 QoS2............................................................................................................................................................... 3-109 Call model parameters for capacity calculations .................................................................................................... 3-111 Introduction ..................................................................................................................................................... 3-111 Typical call parameters ................................................................................................................................... 3-111 Control channel calculations................................................................................................................................... 3-116 Introduction ..................................................................................................................................................... 3-116 Planning considerations.................................................................................................................................. 3-117

68P02900W21-S 01 Feb 2007 v

Contents

Number of CCCHs and PCCCHs per BTS cell ............................................................................................... 3-118 User data capacity on the PCCCH timeslot .................................................................................................... 3-129 Number of SDCCHs per BTS cell ................................................................................................................... 3-130 Control channel configurations........................................................................................................................ 3-133 GPRS/EGPRS traffic planning................................................................................................................................ 3-137 Determination of expected load ...................................................................................................................... 3-137 Network planning flow ..................................................................................................................................... 3-137 GPRS/EGPRS network traffic estimation and key concepts................................................................................... 3-138 Introduction to the GPRS/EGPRS network traffic estimation .......................................................................... 3-138 Dynamic timeslot allocation............................................................................................................................. 3-140 Carrier timeslot allocation examples ............................................................................................................... 3-146 BSS timeslot allocation methods..................................................................................................................... 3-152 Provisioning the network with switchable timeslots......................................................................................... 3-154 Recommendation for switchable timeslot usage ............................................................................................. 3-159 Timeslot allocation process on carriers with GPRS traffic............................................................................... 3-160 GPRS/EGPRS air interface planning process ........................................................................................................ 3-161 Influential factors in GPRS/EGPRS cell planning and deployment ................................................................. 3-161 Estimating the air interface traffic throughput.................................................................................................. 3-171 Select a cell plan............................................................................................................................................. 3-172 Estimating timeslot provisioning requirements ................................................................................................ 3-173 Optimum file size calculation........................................................................................................................... 3-181 File transit times calculations .......................................................................................................................... 3-182 Configurable initial coding scheme ................................................................................................................. 3-185 GPRS/EGPRS data rates ............................................................................................................................... 3-186

Chapter 4 AMR and GSM planning .............................................................................................................. 4-1

Introduction to AMR and GSM planning ...................................................................................................................4-2 AMR basic operation........................................................................................................................................... 4-2 GSM half rate basic operation............................................................................................................................. 4-2 New hardware..................................................................................................................................................... 4-3 Influencing factors ............................................................................................................................................... 4-3 Planning .............................................................................................................................................................. 4-4 Quality and capacity ................................................................................................................................................... 4-5 Benefits of AMR .................................................................................................................................................. 4-5 AMR Full Rate and AMR Half Rate speech quality ............................................................................................. 4-5 AMR voice quality improvement and coverage ................................................................................................. 4-10 Benefits of GSM half rate .................................................................................................................................. 4-11 GSM Half Rate speech quality .......................................................................................................................... 4-11 Capacity increase due to half rate usage .......................................................................................................... 4-11 Timeslot usage.................................................................................................................................................. 4-15

68P02900W21-S vi 01 Feb 2007

Contents

Rate adaptation ........................................................................................................................................................ 4-16 Introduction ....................................................................................................................................................... 4-16 Codec modes.................................................................................................................................................... 4-16 Thresholds and hystereses ............................................................................................................................... 4-17 Downlink adaptation MS monitor ...................................................................................................................... 4-17 Handover and power control .................................................................................................................................... 4-19 Introduction to handover and power control...................................................................................................... 4-19 Handover and power control thresholds ........................................................................................................... 4-19 Miscellaneous information ........................................................................................................................................ 4-22 Emergency call handling................................................................................................................................... 4-22 Circuit pooling ................................................................................................................................................... 4-22 Half rate utilization .................................................................................................................................................... 4-23 Description ........................................................................................................................................................ 4-23 Parameter descriptions ..................................................................................................................................... 4-23 Operational aspects .......................................................................................................................................... 4-27 Hardware.................................................................................................................................................................. 4-29 Equipment descriptions..................................................................................................................................... 4-29 Backhaul ........................................................................................................................................................... 4-31 Summary .................................................................................................................................................................. 4-35

Chapter 5 BTS planning steps and rules .................................................................................................... 5-1

BTS planning overview............................................................................................................................................... 5-2 Introduction ......................................................................................................................................................... 5-2 Outline of planning steps .................................................................................................................................... 5-2 Macrocell cabinets...................................................................................................................................................... 5-4 Horizon II macro.................................................................................................................................................. 5-4 Horizonmacro ..................................................................................................................................................... 5-4 Horizoncompact and Horizoncompact2 .............................................................................................................. 5-5 M-Cell6 ............................................................................................................................................................... 5-5 M-Cell2 ............................................................................................................................................................... 5-5 Microcell enclosures ................................................................................................................................................... 5-6 Horizon II mini ..................................................................................................................................................... 5-6 Horizonmicro and Horizonmicro2 ........................................................................................................................ 5-7 Horizon II micro ................................................................................................................................................... 5-7 Receive configurations ............................................................................................................................................... 5-8 Introduction ......................................................................................................................................................... 5-8 Planning considerations...................................................................................................................................... 5-8 Receiver planning actions................................................................................................................................... 5-9 Transmit configurations ............................................................................................................................................ 5-11 Introduction ....................................................................................................................................................... 5-11

68P02900W21-S 01 Feb 2007 vii

Contents

Planning considerations .................................................................................................................................... 5-11 Transmit planning actions ................................................................................................................................. 5-12 EGPRS enabled CTU2/CTU2D configuration........................................................................................................... 5-13 EGPRS enabled CTU2/CTU2D configuration limitations .................................................................................. 5-13 EGPRS general configuration ........................................................................................................................... 5-13 BaseBand Hopping (BBH) ................................................................................................................................ 5-14 Broadcast Control CHannel (BCCH) RTF configuration.................................................................................... 5-15 Antenna configurations ............................................................................................................................................. 5-16 Planning considerations .................................................................................................................................... 5-16 Antenna planning actions.................................................................................................................................. 5-16 Carrier equipment (transceiver unit) ......................................................................................................................... 5-17 Introduction ....................................................................................................................................................... 5-17 Restrictions in CTU2s usage in Horizonmacro BTSs........................................................................................ 5-17 CTU/CTU2 power supply considerations .......................................................................................................... 5-18 Planning considerations .................................................................................................................................... 5-20 Transceiver planning actions ............................................................................................................................ 5-20 Micro base control unit (microBCU).......................................................................................................................... 5-21 Introduction ....................................................................................................................................................... 5-21 Planning considerations .................................................................................................................................... 5-21 MicroBCU planning actions............................................................................................................................... 5-21 Network interface unit (NIU) and site connection...................................................................................................... 5-22 Introduction ....................................................................................................................................................... 5-22 Planning considerations .................................................................................................................................... 5-22 NIU planning actions ......................................................................................................................................... 5-24 BTS main control unit ............................................................................................................................................... 5-25 Introduction ....................................................................................................................................................... 5-25 Planning considerations .................................................................................................................................... 5-25 Planning considerations Horizon II macro/Horizon II mini as expansion cabinet ........................................... 5-26 Planning actions................................................................................................................................................ 5-27 Cabinet interconnection ............................................................................................................................................ 5-28 Introduction ....................................................................................................................................................... 5-28 Planning considerations .................................................................................................................................... 5-28 Planning considerations - Horizon II macro as master cabinet ......................................................................... 5-31 Planning considerations - Horizon II mini as master cabinet............................................................................. 5-31 XMUX/FMUX/FOX planning actions ................................................................................................................. 5-31 Site expansion board planning actions (Horizon II macro only) ........................................................................ 5-32 Battery back-up provisioning .................................................................................................................................... 5-33 Introduction ....................................................................................................................................................... 5-33 Planning considerations .................................................................................................................................... 5-33

68P02900W21-S viii 01 Feb 2007

Contents

External power requirements.................................................................................................................................... 5-34 Introduction ....................................................................................................................................................... 5-34 Planning considerations.................................................................................................................................... 5-34 Power planning actions..................................................................................................................................... 5-35 Network expansion using macro/microcell BTSs...................................................................................................... 5-36 Introduction ....................................................................................................................................................... 5-36 Expansion considerations ................................................................................................................................. 5-36 Mixed site utilization.......................................................................................................................................... 5-36 Line interface modules (HIM-75, HIM-120)............................................................................................................... 5-37 Introduction ....................................................................................................................................................... 5-37 Planning considerations.................................................................................................................................... 5-37 HIM-75/HIM-120 planning actions..................................................................................................................... 5-37 DRI/Combiner operability components ..................................................................................................................... 5-38 Overview........................................................................................................................................................... 5-38 DRI and combiner relationship.......................................................................................................................... 5-38

Chapter 6 BSC planning steps and rules .................................................................................................... 6-1

BSC planning overview .............................................................................................................................................. 6-2 Introduction ......................................................................................................................................................... 6-2 Mixing of equipment types .................................................................................................................................. 6-2 Outline of planning .............................................................................................................................................. 6-3 Capacity calculations.................................................................................................................................................. 6-4 Introduction ......................................................................................................................................................... 6-4 Remote transcoding............................................................................................................................................ 6-4 BSC system capacity.................................................................................................................................................. 6-5 System capacity summary .................................................................................................................................. 6-5 Scaleable BSC.................................................................................................................................................... 6-6 Enhanced BSC capacity option .......................................................................................................................... 6-7 Huge BSC capacity option .................................................................................................................................. 6-7 LCS option .......................................................................................................................................................... 6-7 Determining the required BSS signaling link capacities.............................................................................................. 6-8 BSC signaling traffic model................................................................................................................................. 6-8 Typical parameter values.................................................................................................................................. 6-10 Assumptions used in capacity calculations ....................................................................................................... 6-15 Link capacities .................................................................................................................................................. 6-17 Determining the number of RSLs required ............................................................................................................... 6-18 Introduction ....................................................................................................................................................... 6-18 Planning considerations.................................................................................................................................... 6-18 Determining the number of RSLs...................................................................................................................... 6-19 One phase access and enhanced one phase................................................................................................... 6-19

68P02900W21-S 01 Feb 2007 ix

Contents

Standard traffic model ....................................................................................................................................... 6-20 Non-standard traffic model................................................................................................................................ 6-22 BSC to BTS E1 interconnect planning actions .................................................................................................. 6-27 Determining the number of LCF GPROCs for RSL and GSL processing BSC to BTS E1 interconnect planning actions............................................................................................................................................................... 6-29 Determining the number of MTLs required ............................................................................................................... 6-32 Introduction ....................................................................................................................................................... 6-32 Planning considerations .................................................................................................................................... 6-32 Standard traffic model ....................................................................................................................................... 6-33 Non-standard traffic model for 64k MTL............................................................................................................ 6-35 Non-standard traffic model for HSP MTL .......................................................................................................... 6-36 Calculate the number of LCFs for MTL processing........................................................................................... 6-38 LCFs for 64k MTL links ..................................................................................................................................... 6-38 LCFs for HSP MTL links.................................................................................................................................... 6-38 MSC to BSC signaling over a satellite link ........................................................................................................ 6-39 Determining the number of LMTLs required ............................................................................................................. 6-40 Introduction ....................................................................................................................................................... 6-40 Planning considerations .................................................................................................................................... 6-40 Determining the number of LMTLs.................................................................................................................... 6-40 BSC to SMLC interconnection planning actions................................................................................................ 6-41 Calculate the number of LCFs for LMTL processing......................................................................................... 6-41 Determining the number of XBLs required................................................................................................................ 6-42 Introduction ....................................................................................................................................................... 6-42 Determining the number of XBLs ...................................................................................................................... 6-42 Standard traffic model ....................................................................................................................................... 6-43 Non standard traffic model ................................................................................................................................ 6-43 Determining the number of GSLs required ............................................................................................................... 6-45 Planning considerations .................................................................................................................................... 6-45 Load balancing.................................................................................................................................................. 6-48 Generic processor (GPROC).................................................................................................................................... 6-49 GPROC nomenclature ...................................................................................................................................... 6-49 Introduction ....................................................................................................................................................... 6-49 GPROC functions and types ............................................................................................................................. 6-49 GPROC3/GPROC3-2 planning assumptions .................................................................................................... 6-51 BSC types ......................................................................................................................................................... 6-51 Planning considerations .................................................................................................................................... 6-52 Cell broadcast link............................................................................................................................................. 6-54 OMF GPROC required...................................................................................................................................... 6-54 Code storage facility processor......................................................................................................................... 6-54 GPROC redundancy ......................................................................................................................................... 6-54

68P02900W21-S x 01 Feb 2007

Contents

GPROC planning actions.................................................................................................................................. 6-56 Transcoding.............................................................................................................................................................. 6-58 Introduction ....................................................................................................................................................... 6-58 GDP/XCDR/EGDP/GDP2 planning considerations........................................................................................... 6-59 EGDP provisioning............................................................................................................................................ 6-60 Planning actions for transcoding at the BSC..................................................................................................... 6-61 Multiple serial interface (MSI) ................................................................................................................................... 6-63 Introduction ....................................................................................................................................................... 6-63 Planning considerations.................................................................................................................................... 6-63 MSI planning actions......................................................................................................................................... 6-63 Packet Subrate Interface (PSI2)............................................................................................................................... 6-65 Introduction ....................................................................................................................................................... 6-65 Planning consideration...................................................................................................................................... 6-65 PSI2 planning actions ....................................................................................................................................... 6-65 Kiloport switch (KSW) and double kiloport switch (DSW2) ....................................................................................... 6-66 Introduction ....................................................................................................................................................... 6-66 Planning considerations.................................................................................................................................... 6-66 KSW/DSW2 planning actions ........................................................................................................................... 6-68 BSU shelves............................................................................................................................................................. 6-69 Introduction ....................................................................................................................................................... 6-69 Planning considerations.................................................................................................................................... 6-69 BSU shelf planning actions ............................................................................................................................... 6-70 Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) ...................................................... 6-72 Introduction ....................................................................................................................................................... 6-72 Planning considerations.................................................................................................................................... 6-72 KSWX/DSWX planning actions......................................................................................................................... 6-73 Generic clock (GCLK)............................................................................................................................................... 6-75 Introduction ....................................................................................................................................................... 6-75 Planning considerations.................................................................................................................................... 6-75 GCLK planning actions ..................................................................................................................................... 6-75 Clock extender (CLKX)............................................................................................................................................. 6-76 Introduction ....................................................................................................................................................... 6-76 Planning considerations.................................................................................................................................... 6-76 CLKX planning actions...................................................................................................................................... 6-76 Local area network extender (LANX) ....................................................................................................................... 6-77 Introduction ....................................................................................................................................................... 6-77 Planning considerations.................................................................................................................................... 6-77 LANX planning actions...................................................................................................................................... 6-77 Parallel interface extender (PIX)............................................................................................................................... 6-78

68P02900W21-S 01 Feb 2007 xi

Contents

Introduction ....................................................................................................................................................... 6-78 Planning considerations .................................................................................................................................... 6-78 PIX planning actions ......................................................................................................................................... 6-78 Line interface boards (BIB/PBIB, T43/PT43) ............................................................................................................ 6-79 Introduction ....................................................................................................................................................... 6-79 Planning considerations .................................................................................................................................... 6-79 (P)BIB/(P)T43 planning actions......................................................................................................................... 6-80 Digital shelf power supply ......................................................................................................................................... 6-81 Introduction ....................................................................................................................................................... 6-81 Planning considerations .................................................................................................................................... 6-81 Power supply planning actions.......................................................................................................................... 6-81 Non Volatile Memory (NVM) board........................................................................................................................... 6-82 Introduction ....................................................................................................................................................... 6-82 Planning considerations .................................................................................................................................... 6-82 NVM planning actions ....................................................................................................................................... 6-82 Verifying the number of BSU shelves and BSSC cabinets ....................................................................................... 6-83 Verification ........................................................................................................................................................ 6-83

Chapter 7 RXCDR planning steps and rules............................................................................................... 7-1

Overview of remote transcoder planning .................................................................................................................... 7-2 Introduction ......................................................................................................................................................... 7-2 Outline of planning steps..................................................................................................................................... 7-2 RXCDR system capacity ............................................................................................................................................ 7-4 System capacity summary .................................................................................................................................. 7-4 RXCDR to BSC connectivity....................................................................................................................................... 7-5 Introduction ......................................................................................................................................................... 7-5 Capacity .............................................................................................................................................................. 7-5 RXCDR to BSC links .................................................................................................................................................. 7-6 Introduction ......................................................................................................................................................... 7-6 E1 interconnect planning actions ........................................................................................................................ 7-7 RXCDR to MSC links.................................................................................................................................................. 7-8 Introduction ......................................................................................................................................................... 7-8 E1 interconnect planning actions ........................................................................................................................ 7-8 Generic processor (GPROC)...................................................................................................................................... 7-9 GPROC nomenclature ........................................................................................................................................ 7-9 Introduction ......................................................................................................................................................... 7-9 Planning considerations ...................................................................................................................................... 7-9 Transcoding.............................................................................................................................................................. 7-10 Introduction ....................................................................................................................................................... 7-10 XCDR/GDP/EGDP/GDP2 planning considerations........................................................................................... 7-12

68P02900W21-S xii 01 Feb 2007

Contents

EGDP provisioning............................................................................................................................................ 7-13 Planning actions for transcoding at the RXCDR ............................................................................................... 7-14 Multiple serial interface (MSI) ................................................................................................................................... 7-16 Introduction ....................................................................................................................................................... 7-16 Planning considerations.................................................................................................................................... 7-16 MSI planning actions......................................................................................................................................... 7-17 Kiloport switch (KSW) and double kiloport switch (DSW2) ....................................................................................... 7-18 Introduction ....................................................................................................................................................... 7-18 Planning considerations.................................................................................................................................... 7-18 KSW/DSW2 planning actions ........................................................................................................................... 7-19 RXU shelves............................................................................................................................................................. 7-21 Introduction ....................................................................................................................................................... 7-21 Planning considerations.................................................................................................................................... 7-21 RXU shelf planning actions ............................................................................................................................... 7-22 Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) ...................................................... 7-24 Introduction ....................................................................................................................................................... 7-24 Planning considerations.................................................................................................................................... 7-24 KSWX/DSWX planning actions......................................................................................................................... 7-25 Generic clock (GCLK)............................................................................................................................................... 7-26 Introduction ....................................................................................................................................................... 7-26 Planning considerations.................................................................................................................................... 7-26 GCLK planning actions ..................................................................................................................................... 7-26 Clock extender (CLKX)............................................................................................................................................. 7-27 Introduction ....................................................................................................................................................... 7-27 Planning considerations.................................................................................................................................... 7-27 CLKX planning actions...................................................................................................................................... 7-27 LAN extender (LANX)............................................................................................................................................... 7-28 Introduction ....................................................................................................................................................... 7-28 Planning considerations.................................................................................................................................... 7-28 LANX planning actions...................................................................................................................................... 7-28 Parallel interface extender (PIX)............................................................................................................................... 7-29 Introduction ....................................................................................................................................................... 7-29 Planning considerations.................................................................................................................................... 7-29 PIX planning actions ......................................................................................................................................... 7-29 Line interfaces (BIB, T43)......................................................................................................................................... 7-30 Introduction ....................................................................................................................................................... 7-30 Planning considerations.................................................................................................................................... 7-30 BIB/T43 planning actions .................................................................................................................................. 7-31 Digital shelf power supply......................................................................................................................................... 7-32

68P02900W21-S 01 Feb 2007 xiii

Contents

Introduction ....................................................................................................................................................... 7-32 Planning considerations .................................................................................................................................... 7-32 Power supply planning actions.......................................................................................................................... 7-32 Non volatile memory (NVM) board ........................................................................................................................... 7-33 Introduction ....................................................................................................................................................... 7-33 Planning considerations .................................................................................................................................... 7-33 NVM planning actions ....................................................................................................................................... 7-33 Verify the number of RXU shelves and BSSC cabinets............................................................................................ 7-34 Verification ........................................................................................................................................................ 7-34

Chapter 8 PCU upgrade for BSS .................................................................................................................. 8-1

BSS planning for GPRS/EGPRS ................................................................................................................................ 8-2 Introduction to BSS planning for GPRS/EGPRS................................................................................................. 8-2 PCU to SGSN interface planning ........................................................................................................................ 8-2 Feature compatibility ........................................................................................................................................... 8-4 BSS upgrade provisioning rules........................................................................................................................ 8-13 Maximum BSS configuration............................................................................................................................. 8-14 PCU hardware layout ............................................................................................................................................... 8-20 PCU shelf (cPCI) ...................................................................................................................................................... 8-22 Planning considerations .................................................................................................................................... 8-22 MPROC board .......................................................................................................................................................... 8-24 Introduction ....................................................................................................................................................... 8-24 PSP planning considerations ............................................................................................................................ 8-24 DPROC board .......................................................................................................................................................... 8-25 Introduction ....................................................................................................................................................... 8-25 PICP or PRP planning considerations .............................................................................................................. 8-25 PXP planning considerations ............................................................................................................................ 8-28 PMC module............................................................................................................................................................. 8-30 Introduction ....................................................................................................................................................... 8-30 Planning considerations .................................................................................................................................... 8-30 (Packet) Rear Transition Module .............................................................................................................................. 8-31 Introduction ....................................................................................................................................................... 8-31 Planning considerations .................................................................................................................................... 8-31 PCU equipment redundancy and provisioning goals ................................................................................................ 8-32 Support for equipment redundancy................................................................................................................... 8-32 PCU equipment redundancy planning .............................................................................................................. 8-32 PRP/PICP configure ......................................................................................................................................... 8-32 PXP configuration ............................................................................................................................................. 8-37 Upgrading the PCU ........................................................................................................................................... 8-40 E1 link/ETH link provisioning for GPRS and EGPRS ............................................................................................... 8-43

68P02900W21-S xiv 01 Feb 2007

Contents

E1 interface provisioning................................................................................................................................... 8-43 E1 Planning considerations .............................................................................................................................. 8-43 Ethernet interface provisioning ......................................................................................................................... 8-44 QoS capacity and QoS2 impact ............................................................................................................................... 8-45 MTBR allocation................................................................................................................................................ 8-47 PRP-PDTCH QoS planning .............................................................................................................................. 8-49 CTU2D impact .................................................................................................................................................. 8-56 PCU-SGSN: traffic and signal planning .................................................................................................................... 8-57 Introduction ....................................................................................................................................................... 8-57 Gb entities......................................................................................................................................................... 8-57 General planning guidelines ............................................................................................................................. 8-58 Specific planning guidelines.............................................................................................................................. 8-58 Gb signaling ...................................................................................................................................................... 8-58 Determining net Gb load ................................................................................................................................... 8-59 Gb link timeslots................................................................................................................................................ 8-60 Frame relay parameter values .......................................................................................................................... 8-60 BSS-PCU hardware planning example for GPRS .................................................................................................... 8-63 Introduction ....................................................................................................................................................... 8-63 BSS - PCU planning example for GPRS........................................................................................................... 8-63 BSS-PCU hardware planning example for EGPRS .................................................................................................. 8-69 Introduction ....................................................................................................................................................... 8-69 BSS - PCU planning example for EGPRS ........................................................................................................ 8-69 BSS - PCU planning example for EGPRS with QoS enabled, QoS2 not enabled ............................................ 8-75 BSS - PCU planning example for EGPRS with QoS and QoS2 enabled .......................................................... 8-82

Chapter 9 Planning exercises ...................................................................................................................... 9-1

Pre-requisites ............................................................................................................................................................. 9-2 Requirements ..................................................................................................................................................... 9-2 Network topology ................................................................................................................................................ 9-3 Exercises.................................................................................................................................................................... 9-4 Introduction ......................................................................................................................................................... 9-4 Determine the hardware requirements for BTS B....................................................................................................... 9-5 Cabinet ............................................................................................................................................................... 9-5 Summary ............................................................................................................................................................ 9-5 Determine the hardware requirements for BTS K....................................................................................................... 9-8 Introduction ......................................................................................................................................................... 9-8 Cabinet ............................................................................................................................................................... 9-8 Receiver requirements........................................................................................................................................ 9-8 Transmitter combining requirements................................................................................................................... 9-8 Summary ............................................................................................................................................................ 9-9

68P02900W21-S 01 Feb 2007 xv

Contents

Determine the hardware requirements for the BSC.................................................................................................. 9-11 Introduction ....................................................................................................................................................... 9-11 Summary........................................................................................................................................................... 9-13 Determine the hardware requirements for the RXCDR ............................................................................................ 9-14 MSI requirements.............................................................................................................................................. 9-14 Transcoder requirement.................................................................................................................................... 9-14 Link interface..................................................................................................................................................... 9-15 GPROC requirement......................................................................................................................................... 9-15 KSW/DSW2 requirement .................................................................................................................................. 9-15 KSWX/DSWX requirement................................................................................................................................ 9-15 GCLK requirement ............................................................................................................................................ 9-15 CLKX requirement ............................................................................................................................................ 9-15 PIX requirement ................................................................................................................................................ 9-15 LANX requirement ............................................................................................................................................ 9-16 Power supply .................................................................................................................................................... 9-16 Summary........................................................................................................................................................... 9-16 Calculations using alternative call models ................................................................................................................ 9-17 Introduction ....................................................................................................................................................... 9-17 Planning example 1 .......................................................................................................................................... 9-17 Planning example 2 .......................................................................................................................................... 9-27 Planning example 3 .......................................................................................................................................... 9-36 Planning example 4 (using AMR)...................................................................................................................... 9-47 Planning example 4 (using AMR)...................................................................................................................... 9-61 Planning example 5 .......................................................................................................................................... 9-75 Planning example of BSS support for LCS provisioning........................................................................................... 9-86 Typical parameter values .................................................................................................................................. 9-86 LCS planning example calculations .................................................................................................................. 9-86 Planning example for DTM Feature.......................................................................................................................... 9-89

Chapter 10 Location area planning............................................................................................................ 10-1

Location area planning considerations ..................................................................................................................... 10-2 Location area planning calculations.......................................................................................................................... 10-3 Example procedure ........................................................................................................................................... 10-3

Chapter 11 Call model parameters ............................................................................................................ 11-1

Deriving call model parameters from network statistics............................................................................................ 11-2 Standard call model parameters ....................................................................................................................... 11-2 Call duration (T) ................................................................................................................................................ 11-6 Ratio of SMSs per call (S)................................................................................................................................. 11-7 Ratio of handovers per call (H) ......................................................................................................................... 11-8 Ratio of intra BSS handovers to all handovers (i) ............................................................................................. 11-9

68P02900W21-S xvi 01 Feb 2007

Contents

Ratio of location updates per call (I).................................................................................................................. 11-9 Ratio of IMSI detaches per call (I)................................................................................................................... 11-10 Location update factor (L) ............................................................................................................................... 11-10 Paging rate (PGSM) .......................................................................................................................................... 11-11 Pages per call (PPC) ........................................................................................................................................ 11-11 Percent link utilization MSC to BSS [U(MSC BSS)] ..................................................................................... 11-12 Percent link utilization BSC to BTS [U(BSC BTS)]....................................................................................... 11-13 Blocking for TCHs (PB TCHs) ........................................................................................................................... 11-13 GPRS CS1 uplink usage (CS1_usage_UL) .................................................................................................... 11-14 GPRS CS1 downlink usage (CS1_usage_DL) ............................................................................................... 11-15 GPRS CS2 uplink usage (CS2_usage_UL) .................................................................................................... 11-16 GPRS CS2 downlink usage (CS2_usage_DL) ............................................................................................... 11-17 GPRS CS3 uplink usage (CS3_usage_UL) .................................................................................................... 11-18 GPRS CS4 uplink usage (CS4_usage_UL) .................................................................................................... 11-19 GPRS CS4 downlink usage (CS4_usage_DL) ............................................................................................... 11-20 EGPRS MCS1 uplink usage (MCS1_usage_UL)............................................................................................ 11-21 EGPRS MCS1 downlink usage (MCS1_usage_DL) ....................................................................................... 11-22 EGPRS MCS2 uplink usage (MCS2_usage_UL)............................................................................................ 11-23 EGPRS MCS2 downlink usage (MCS2_usage_DL) ....................................................................................... 11-24 EGPRS MCS3 uplink usage (MCS3_usage_UL)............................................................................................ 11-25 EGPRS MCS3 downlink usage (MCS3_usage_DL) ....................................................................................... 11-26 EGPRS MCS4 uplink usage (MCS4_usage_UL)............................................................................................ 11-27 EGPRS MCS4 downlink usage (MCS4_usage_DL) ....................................................................................... 11-28 EGPRS MCS5 uplink usage (MCS5_usage_UL)............................................................................................ 11-29 EGPRS MCS5 downlink usage (MCS5_usage_DL) ....................................................................................... 11-30 EGPRS MCS6 uplink usage (MCS6_usage_UL)............................................................................................ 11-31 EGPRS MCS6 downlink usage (MCS6_usage_DL) ....................................................................................... 11-32 EGPRS MCS7 downlink usage (MCS7_usage_DL) ....................................................................................... 11-33 EGPRS MCS8 uplink usage (MCS8_usage_UL)............................................................................................ 11-34 EGPRS MCS8 downlink usage (MCS8_usage_DL) ....................................................................................... 11-35 EGPRS MCS9 uplink usage (MCS9_usage_UL)............................................................................................ 11-36 EGPRS MCS9 downlink usage (MCS9_usage_DL) ....................................................................................... 11-37 Sample statistic calculations ........................................................................................................................... 11-38 Call duration (T) .............................................................................................................................................. 11-38 Number of SMSs per call (S) .......................................................................................................................... 11-39 Ratio of handovers per call (H) ....................................................................................................................... 11-39 Ratio of intra-BSS handovers to all handovers (i) ........................................................................................... 11-39 Number of location updates per call (l) ........................................................................................................... 11-40 IMSI detaches per call (I) ................................................................................................................................ 11-40

68P02900W21-S 01 Feb 2007 xvii

Contents

Location update factor (L) ............................................................................................................................... 11-40 Paging Rate (PGSM) for a BSC......................................................................................................................... 11-40

Chapter 12 Standard BSS and Horizon BTS configurations................................................................... 12-1

Standard configurations............................................................................................................................................ 12-2 Typical BSS configurations....................................................................................................................................... 12-3 BSC with 24 BTSs ............................................................................................................................................ 12-3 BSC with full redundancy .................................................................................................................................. 12-4 Transcoder........................................................................................................................................................ 12-5 Single cabinet BTS configurations............................................................................................................................ 12-6 Single cabinet Horizon II macro BTS ................................................................................................................ 12-6 Single cabinet Horizon II mini BTS.................................................................................................................... 12-7 Single cabinet Horizon II micro BTS ................................................................................................................. 12-8 Single cabinet Horizonmacro BTS .................................................................................................................... 12-9 Two cabinet BTS configurations ............................................................................................................................. 12-10 Two cabinet Horizon II macro BTS ................................................................................................................. 12-10 Two cabinet Horizon II mini BTS..................................................................................................................... 12-11 Two cabinet Horizonmacro BTS .....................................................................................................................12-12 Three cabinet BTS configurations .......................................................................................................................... 12-13 Three cabinet Horizon II macro BTS............................................................................................................... 12-13 Three cabinet Horizon II mini BTS .................................................................................................................. 12-14 Three cabinet Horizon II micro BTS ................................................................................................................ 12-15 Three cabinet Horizonmacro BTS................................................................................................................... 12-16 Four cabinet BTS configurations ............................................................................................................................ 12-17 Four cabinet Horizon II macro BTS................................................................................................................. 12-17 Four cabinet Horizon II mini BTS .................................................................................................................... 12-18 Four cabinet Horizonmacro BTS.....................................................................................................................12-19 Horizon macrocell RF configurations ...................................................................................................................... 12-20 Overview of configuration diagrams ................................................................................................................ 12-20 Horizon II macro cabinets ............................................................................................................................... 12-20 Horizon II macro cabinets with PGSM Duplexer ............................................................................................. 12-30 Horizon II mini cabinets................................................................................................................................... 12-36 Horizon II micro cabinets................................................................................................................................. 12-44 Horizonmacro cabinets ................................................................................................................................... 12-47 Horizoncompact2 ............................................................................................................................................ 12-56 Microcell RF configurations .................................................................................................................................... 12-60 Horizonmicro2 ................................................................................................................................................. 12-60 Connecting Horizon II macro cabinets to Horizonmacro cabinets .......................................................................... 12-63 Connection overview....................................................................................................................................... 12-63 Compatibility issues ........................................................................................................................................ 12-63

68P02900W21-S xviii 01 Feb 2007

Contents

Examples of mixed cabinet configurations...................................................................................................... 12-63 Connecting Horizon II macro cabinets to M-Cell6 cabinets .................................................................................... 12-71 Connection overview....................................................................................................................................... 12-71 Compatibility issues ........................................................................................................................................ 12-71

Chapter 13 M-Cell BTS configurations ...................................................................................................... 13-1

M-Cell BTS configurations........................................................................................................................................ 13-2 Standard M-Cell configurations ................................................................................................................................ 13-3 Single cabinet BTS configurations............................................................................................................................ 13-4 Single cabinet M-Cell6 BTS .............................................................................................................................. 13-4 Single cabinet M-Cell2 BTS .............................................................................................................................. 13-5 Two cabinet BTS configuration................................................................................................................................. 13-6 Two cabinet M-Cell6 BTS ................................................................................................................................. 13-6 Two cabinet M-Cell6 BTS with CTU2 Adapter .................................................................................................. 13-7 Three cabinet BTS configuration .............................................................................................................................. 13-8 Three cabinet M-Cell2 BTS............................................................................................................................... 13-8 Four cabinet BTS configuration ................................................................................................................................ 13-9 Four cabinet M-Cell6 BTS................................................................................................................................. 13-9 M-Cell RF configurations ........................................................................................................................................ 13-10 Overview......................................................................................................................................................... 13-10 M-Cell6 cabinets ............................................................................................................................................. 13-10 M-Cell2 cabinets M-Cell6 cabinets.................................................................................................................. 13-45

Index.....................................................................................................................................................................I

68P02900W21-S 01 Feb 2007 xix

Contents

68P02900W21-S xx 01 Feb 2007

List of Figures

List of Figures
Figure 1-1 BSS block diagram .......................................................................................................................................... 1-4 Figure 1-2 CTU2D PWR.................................................................................................................................................. 1-20 Figure 1-3 CTU2D CAP................................................................................................................................................... 1-20 Figure 1-4 CTU2D ASYM................................................................................................................................................ 1-20 Figure 2-1 BSS interfaces ................................................................................................................................................. 2-2 Figure 2-2 Possible network topology ............................................................................................................................... 2-6 Figure 2-3 Star connection ................................................................................................................................................ 2-7 Figure 2-4 Closed loop and open ended daisy chains ...................................................................................................... 2-8 Figure 2-5 Simple daisy chain ........................................................................................................................................... 2-9 Figure 2-6 Daisy chain with branch ................................................................................................................................. 2-10 Figure 2-7 Typical low capacity BSC/BTS configuration ................................................................................................. 2-11 Figure 2-8 Example using a switching network ............................................................................................................... 2-11 Figure 2-9 Timeslot allocation using new and old algorithms .......................................................................................... 2-12 Figure 2-10 Alternative network configuration with E1 switching network ....................................................................... 2-13 Figure 2-11 A configuration with a BTS equipped with two redundant RTFs .................................................................. 2-15 Figure 2-12 A configuration with a BTS equipped with two non-redundant RTFs ........................................................... 2-15 Figure 2-13 Fully equipped RTF...................................................................................................................................... 2-17 Figure 2-14 Sub-equipped RTF....................................................................................................................................... 2-18 Figure 2-15 XBL utilization .............................................................................................................................................. 2-19 Figure 2-16 Conversion of E1 to HDSL links by modem and microsite........................................................................... 2-24 Figure 2-17 Microcell daisy chain network configuration ................................................................................................. 2-25 Figure 2-18 Microcell star network configuration............................................................................................................. 2-25 Figure 2-19 Microcell configuration using E1/HDSL links................................................................................................ 2-25 Figure 3-1 UK network users............................................................................................................................................. 3-5 Figure 3-2 Eight TDMA timeslots per RF carrier ............................................................................................................... 3-6 Figure 3-3 Modulation techniques and channel spacing ................................................................................................... 3-7 Figure 3-4 AMR half rate capacity increase .................................................................................................................... 3-11 Figure 3-5 AMR full rate call quality improvements ......................................................................................................... 3-12 Figure 3-6 GSM half rate capacity increase .................................................................................................................... 3-14 Figure 3-7 GSM half rate codec comparison................................................................................................................... 3-15 Figure 3-8 First Fresnel zone radius calculation.............................................................................................................. 3-19 Figure 3-9 Refraction ...................................................................................................................................................... 3-20

68P02900W21-S 01 Feb 2007 xxi

List of Figures

Figure 3-10 Measurement of the RRI .............................................................................................................................. 3-21 Figure 3-11 Refraction effects on a microwave system................................................................................................... 3-22 Figure 3-12 Attenuation................................................................................................................................................... 3-23 Figure 3-13 Reflection ..................................................................................................................................................... 3-24 Figure 3-14 Scattering..................................................................................................................................................... 3-24 Figure 3-15 Diffraction..................................................................................................................................................... 3-25 Figure 3-16 Polarization .................................................................................................................................................. 3-25 Figure 3-17 Propagation effect - Rayleigh fading environment ....................................................................................... 3-26 Figure 3-18 Rayleigh distribution..................................................................................................................................... 3-27 Figure 3-19 Propagation effect - Rician environment ...................................................................................................... 3-27 Figure 3-20 Rician distribution......................................................................................................................................... 3-28 Figure 3-21 Plane earth loss ........................................................................................................................................... 3-31 Figure 3-22 Focusing of power........................................................................................................................................ 3-33 Figure 3-23 Measurement of gain ................................................................................................................................... 3-33 Figure 3-24 Building propagation .................................................................................................................................... 3-35 Figure 3-25 Okumura propagation graphs ...................................................................................................................... 3-36 Figure 3-26 BTS antenna height of 50 m, MS height of 1.5 m (GSM900 ........................................................................ 3-39 Figure 3-27 BTS antenna height of 100 m, MS height of 1.5 m (GSM900) ..................................................................... 3-39 Figure 3-28 Path loss against cell radius for small cells .................................................................................................. 3-40 Figure 3-29 Adjacent cell interference............................................................................................................................. 3-42 Figure 3-30 7 cell re-use pattern ..................................................................................................................................... 3-42 Figure 3-31 3 cell re-use pattern ..................................................................................................................................... 3-43 Figure 3-32 2 site - 6 cell re-use pattern.......................................................................................................................... 3-44 Figure 3-33 Carrier interference measurements.............................................................................................................. 3-45 Figure 3-34 coding process ............................................................................................................................................. 3-49 Figure 3-35 Coding process illustration (full rate and enhanced full rate speech) ........................................................... 3-50 Figure 3-36 Coding process illustration (AMR full rate and AMR half rate speech)......................................................... 3-51 Figure 3-37 Coding process illustration (GSM HR speech, control and data) ................................................................. 3-52 Figure 3-38 Speech channel encoding............................................................................................................................ 3-54 Figure 3-39 Preliminary coding for enhanced full rate speech ........................................................................................ 3-55 Figure 3-40 Speech channel encoding for GSM half rate speech ................................................................................... 3-56 Figure 3-41 Speech channel encoding for AMR full rate ................................................................................................. 3-58 Figure 3-42 Speech channel encoding for AMR half rate................................................................................................ 3-60 Figure 3-43 Control channel coding ................................................................................................................................ 3-62 Figure 3-44 Data channel encoding ................................................................................................................................ 3-63 Figure 3-45 Diagonal interleaving - full rate speech ........................................................................................................ 3-65 Figure 3-46 Diagonal interleaving - half rate speech ....................................................................................................... 3-66 Figure 3-47 Rectangular interleaving control................................................................................................................ 3-68 Figure 3-48 Diagonal interleaving - CS data ................................................................................................................... 3-70

68P02900W21-S xxii 01 Feb 2007

List of Figures

Figure 3-49 GPRS channel coding scheme 1 (CS1)....................................................................................................... 3-71 Figure 3-50 GPRS channel coding scheme 2 (CS2)....................................................................................................... 3-72 Figure 3-51 GPRS channel coding scheme 3 (CS3)....................................................................................................... 3-73 Figure 3-52 GPRS channel coding scheme 4 (CS4)....................................................................................................... 3-74 Figure 3-53 EGPRS channel coding scheme 1 (MCS-1) ................................................................................................ 3-77 Figure 3-54 EGPRS channel coding scheme 2 (MCS-2) ................................................................................................ 3-78 Figure 3-55 EGPRS channel coding scheme 3 (MCS-3) ................................................................................................ 3-79 Figure 3-56 EGPRS channel coding scheme 4 (MCS-4) ................................................................................................ 3-80 Figure 3-57 EGPRS channel coding scheme 5 (MCS-5) ................................................................................................ 3-81 Figure 3-58 EGPRS channel coding scheme 6 (MCS-6) ................................................................................................ 3-82 Figure 3-59 EGPRS channel coding scheme 7 (MCS-7) ................................................................................................ 3-83 Figure 3-60 EGPRS channel coding scheme 8 (MCS-8) ................................................................................................ 3-84 Figure 3-61 EGPRS channel coding scheme 9 (MCS-9) ................................................................................................ 3-85 Figure 3-62 SACCH multiframe (480 ms) for DTX and full rate....................................................................................... 3-88 Figure 3-63 SACCH multiframe (480 ms) for DTX and half rate ..................................................................................... 3-89 Figure 3-64 Receive diversity.......................................................................................................................................... 3-91 Figure 3-65 Training sequence code............................................................................................................................... 3-92 Figure 3-66 Subscriber environment ............................................................................................................................... 3-94 Figure 3-67 Subscriber distribution ................................................................................................................................. 3-95 Figure 3-68 Layered architecture .................................................................................................................................... 3-97 Figure 3-69 Combined cell architecture .......................................................................................................................... 3-98 Figure 3-70 Combined cell architecture structure............................................................................................................ 3-99 Figure 3-71 Separating BCCH and TCH bands ............................................................................................................ 3-100 Figure 3-72 Band usage for macrocells with microcells ................................................................................................ 3-100 Figure 3-73 Frequency split for TCH re-use planning example ..................................................................................... 3-102 Figure 3-74 Avoiding co-channel and adjacent channel interference............................................................................ 3-103 Figure 3-75 BBH frequency spectrum allocation ........................................................................................................... 3-103 Figure 3-76 GSM and UMTS system nodes and interfaces .......................................................................................... 3-106 Figure 3-77 DTM MS states .......................................................................................................................................... 3-107 Figure 3-78 CCCH and PCCCH decision tree............................................................................................................... 3-118 Figure 3-79 Location area diagram ............................................................................................................................... 3-131 Figure 3-80 MM state models for MS and SGSN .......................................................................................................... 3-140 Figure 3-81 Carrier with reserved and switchable GPRS/EGPRS timeslots ................................................................. 3-154 Figure 3-82 Carrier with reserved, switchable GPRS/EGPRS timeslots and DTM PDCHs........................................... 3-154 Figure 3-83 Circuit-switched carrier, 1 BCCH/CCCH + 1 SDCCH + 6 TCH timeslots................................................... 3-158 Figure 3-84 1 carrier, all timeslots (8 TCHs) designated as switchable......................................................................... 3-158 Figure 3-85 Generic planning and dimensioning process ............................................................................................. 3-161 Figure 3-86 Multiplexing 4 TBFs on an air timeslot ....................................................................................................... 3-165 Figure 3-87 LLC_PDU frame layout .............................................................................................................................. 3-181

68P02900W21-S 01 Feb 2007 xxiii

List of Figures

Figure 3-88 LLC PDU to TDMA bursts .......................................................................................................................... 3-187 Figure 4-1 AMR FR/clean speech versus EFR versus performance requirements ........................................................... 4-6 Figure 4-2 AMR FR/clean speech codec modes ............................................................................................................... 4-7 Figure 4-3 AMR HR/clean speech versus EFR versus GSM FR versus GSM HR versus performance requirements...... 4-8 Figure 4-4 AMR HR/clean speech codec modes............................................................................................................... 4-9 Figure 4-5 3 carriers, only one hr-capable carrier............................................................................................................ 4-12 Figure 4-6 3 carriers, all hr-capable................................................................................................................................. 4-13 Figure 4-7 5 carriers, only one hr-capable carrier............................................................................................................ 4-13 Figure 4-8 5 carriers, only 3 hr-capable carriers.............................................................................................................. 4-14 Figure 4-9 5 carriers, all hr-capable carriers.................................................................................................................... 4-14 Figure 4-10 Rate adaptations: codec modes, thresholds and hystereses ....................................................................... 4-17 Figure 4-11 Congestion threshold settings for AMR half rate.......................................................................................... 4-28 Figure 4-12 Alternative configurations for the BSSC3 cabinet ........................................................................................ 4-31 Figure 4-13 AMR backhaul paths .................................................................................................................................... 4-33 Figure 4-14 hr backhaul paths - ESS mode enabled....................................................................................................... 4-34 Figure 5-1 DRI and combiner relationship....................................................................................................................... 5-38 Figure 6-1 BSS planning diagram ..................................................................................................................................... 6-9 Figure 6-2 EGDP configuration with the additional E1 termination in use ....................................................................... 6-60 Figure 6-3 EGDP configuration without the additional E1 termination in use .................................................................. 6-61 Figure 7-1 Sub-multiplexing and speech transcoding at the RXCDR .............................................................................. 7-11 Figure 7-2 EGDP configuration with the additional E1 termination in use ....................................................................... 7-13 Figure 7-3 EGDP configuration without the additional E1 termination in use .................................................................. 7-14 Figure 8-1 PCU to SGSN interface planning ..................................................................................................................... 8-3 Figure 8-2 Mixed Deployment ......................................................................................................................................... 8-11 Figure 8-3 PCU shelf layout ............................................................................................................................................ 8-20 Figure 8-4 Provisioning goals (full redundancy) .............................................................................................................. 8-33 Figure 8-5 Provisioning goals (Maximum coverage) ....................................................................................................... 8-34 Figure 8-6 EGPRS maximum throughput and coverage, full redundancy not required ................................................... 8-35 Figure 8-7 Provisioning goals (full redundancy) .............................................................................................................. 8-38 Figure 8-8 Provisioning goals (maximum coverage) ....................................................................................................... 8-39 Figure 8-9 BER versus Number of mobiles ..................................................................................................................... 8-56 Figure 8-10 Frame relay parameters............................................................................................................................... 8-61 Figure 8-11 PCU equipment and link planning for GPRS................................................................................................ 8-63 Figure 8-12 PCU Equipment and link planning for EGPRS............................................................................................. 8-69 Figure 9-1 Network topology ............................................................................................................................................. 9-3 Figure 10-1 Four BSCs in one LAC................................................................................................................................. 10-4 Figure 10-2 Four BSCs divided into two LACs ................................................................................................................ 10-5 Figure 12-1 BSC controlling 24 BTSs.............................................................................................................................. 12-3 Figure 12-2 Fully redundant BSC controlling 34 BTSs .................................................................................................... 12-4

68P02900W21-S xxiv 01 Feb 2007

List of Figures

Figure 12-3 BSSC cabinet equipped to provide transcoding........................................................................................... 12-5 Figure 12-4 Macrocell BTS with one Horizon II macro cabinet........................................................................................ 12-6 Figure 12-5 Macrocell BTS with one Horizon II mini cabinet ........................................................................................... 12-7 Figure 12-6 Macrocell BTS with one Horizon II micro cabinet......................................................................................... 12-8 Figure 12-7 Macrocell BTS with one Horizonmacro cabinet............................................................................................ 12-9 Figure 12-8 Macrocell BTS with two Horizon II macro cabinets .................................................................................... 12-10 Figure 12-9 Macrocell BTS with two Horizon II mini cabinets........................................................................................ 12-11 Figure 12-10 Macrocell BTS with two Horizonmacro cabinets ...................................................................................... 12-12 Figure 12-11 Macrocell BTS with three Horizon II macro cabinets................................................................................ 12-13 Figure 12-12 Macrocell BTS with three Horizon II mini cabinets ................................................................................... 12-14 Figure 12-13 Macrocell BTS with three Horizon II micro cabinets................................................................................. 12-15 Figure 12-14 Macrocell BTS with three Horizonmacro cabinets.................................................................................... 12-16 Figure 12-15 Macrocell BTS with four Horizon II macro cabinets.................................................................................. 12-17 Figure 12-16 Macrocell BTS with four Horizon II mini cabinets ..................................................................................... 12-18 Figure 12-17 Macrocell BTS with four Horizonmacro cabinets...................................................................................... 12-19 Figure 12-18 [DCS1800] 4 or 8 carrier omni with HCUs and air combining .................................................................. 12-21 Figure 12-19 [DCS1800] 6 or 12 carrier omni with DHUs ............................................................................................. 12-22 Figure 12-20 [DCS1800] 2 sector 3/3 or 6/6 with DHUs................................................................................................ 12-23 Figure 12-21 [DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining .................................................. 12-24 Figure 12-22 [DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs.......................................................................................... 12-25 Figure 12-23 [DCS1800] 2 cab, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining.................................................. 12-26 Figure 12-24 [DCS1800] 3 sector 2/2/2 or 4/4/4 with air combining and 4 branch Rx diversity..................................... 12-27 Figure 12-25 [DCS1800/GSM900] 3 sector 2/2/2 and 2/2/2 with air combining ............................................................ 12-28 Figure 12-26 [PGSM900] 4 or 8 carrier omni with HCUs and air combining ................................................................. 12-30 Figure 12-27 [PGSM900] 6 or 12 carrier omni with DHUs ............................................................................................ 12-31 Figure 12-28 [PGSM900] 2 sector 3/3 or 6/6 with HCUs............................................................................................... 12-32 Figure 12-29 [PGSM900] 2 cab, 2 sector 4/4 or 8/8 with HCUs and air combining....................................................... 12-33 Figure 12-30 [PGSM900] 3 sector 2/2/2 or 4/4/4........................................................................................................... 12-34 Figure 12-31 [PGSM900] 2 cab, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining4............................................... 12-35 Figure 12-32 DCS1800/EGSM900 HP Omni-1/SP Omni-2........................................................................................... 12-37 Figure 12-33 DCS1800/EGSM900 HP Omni-2/SP Omni-4........................................................................................... 12-38 Figure 12-34 DCS1800/EGSM900 HP Bowtie-2/SP Bowtie-4 ...................................................................................... 12-39 Figure 12-35 DCS1800/EGSM900 HP 2 sector 1/1/SP 2 sector 2/2............................................................................. 12-40 Figure 12-36 DCS1800/EGSM900 HP 2 sector 2/2/SP 2 sector 4/4............................................................................. 12-41 Figure 12-37 DCS1800/EGSM900 HP 3 sector 1/1/1/SP 3 sector 2/2/2 ....................................................................... 12-42 Figure 12-38 DCS1800/EGSM900 HP 3 sector 2/2/2/SP 3 sector 4/4/4 ....................................................................... 12-43 Figure 12-39 [DCS1800/EGSM900] Horizon II micro one cabinet configuration ........................................................... 12-45 Figure 12-40 [DCS1800/EGSM900] Horizon II micro three cabinet configuration......................................................... 12-46 Figure 12-41 4 carrier omni, duplexed hybrid and air combining................................................................................... 12-48

68P02900W21-S 01 Feb 2007 xxv

List of Figures

Figure 12-42 6 carrier omni, duplexed dual-stage hybrid and air combining ................................................................. 12-49 Figure 12-43 2 sector (3/3), duplexed dual-stage hybrid combining.............................................................................. 12-50 Figure 12-44 2 sector (6/6), duplexed dual-stage hybrid and air combining.................................................................. 12-51 Figure 12-45 3 sector (2/2/2), duplexed hybrid combining ............................................................................................ 12-52 Figure 12-46 3 sector (4/4/4), duplexed hybrid and air combining ................................................................................ 12-53 Figure 12-47 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 1) .................................................. 12-54 Figure 12-48 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 2) .................................................. 12-55 Figure 12-49 Horizoncompact2 single BTS system....................................................................................................... 12-57 Figure 12-50 Horizoncompact2 two BTS system .......................................................................................................... 12-58 Figure 12-51 Horizoncompact2 three BTS system........................................................................................................ 12-59 Figure 12-52 Horizonmicro2 single BTS system ........................................................................................................... 12-61 Figure 12-53 Horizonmicro2 two BTS system ............................................................................................................... 12-61 Figure 12-54 Horizonmicro2 three BTS system............................................................................................................. 12-62 Figure 12-55 Sector 4/4 configuration with Horizon II macro and Horizonmacro cabinets ............................................ 12-64 Figure 12-56 Sector 6/6 configuration with Horizon II macro and Horizonmacro cabinets ............................................ 12-65 Figure 12-57 Sector 2/2/2 configuration (Horizon II macro as master cabinet) ............................................................. 12-66 Figure 12-58 Sector 2/2/2 configuration (Horizonmacro as master cabinet) ................................................................. 12-67 Figure 12-59 Sector 4/4/4 configuration with Horizon II macro and Horizonmacro cabinets ......................................... 12-68 Figure 12-60 Sector 6/6/6 configuration with Horizon II macro and Horizonmacro cabinets ......................................... 12-69 Figure 12-61 Horizonmacro cabinet configuration using CTUs and CTU2s .................................................................. 12-70 Figure 12-62 900 MHz Horizon II macro and 900 MHz M-Cell6 interconnections ......................................................... 12-72 Figure 12-63 1800 MHz Horizon II macro and 1800 MHz M-Cell6 interconnections ..................................................... 12-73 Figure 13-1 Single cabinet M-Cell6 BTS ......................................................................................................................... 13-4 Figure 13-2 Single cabinet M-Cell2 BTS ......................................................................................................................... 13-5 Figure 13-3 Two cabinet M-Cell6 BTS ............................................................................................................................ 13-6 Figure 13-4 Two cabinet M-Cell6 BTS with CTU2 Adapters ........................................................................................... 13-7 Figure 13-5 Three cabinet M-Cell2 BTS.......................................................................................................................... 13-8 Figure 13-6 Four cabinet M-Cell6 BTS............................................................................................................................ 13-9 Figure 13-7 3 carrier omni, hybrid combining ................................................................................................................ 13-11 Figure 13-8 3 carrier omni, hybrid combining, medium power duplexer ........................................................................ 13-12 Figure 13-9 4 carrier omni, hybrid combining ................................................................................................................ 13-13 Figure 13-10 4 carrier omni, hybrid combining, medium power duplexer ...................................................................... 13-14 Figure 13-11 6 carrier omni, cavity combining............................................................................................................... 13-15 Figure 13-12 6 carrier omni, cavity combining, high power duplexer............................................................................. 13-16 Figure 13-13 8 carrier omni, combining......................................................................................................................... 13-17 Figure 13-14 2 sector (3/3), hybrid combining ............................................................................................................... 13-18 Figure 13-15 2 sector (3/3), hybrid combining, medium power duplexers ..................................................................... 13-19 Figure 13-16 3 sector (2/2/2), combining....................................................................................................................... 13-20 Figure 13-17 3 sector (2/2/2), combining, medium power duplexers............................................................................. 13-21

68P02900W21-S xxvi 01 Feb 2007

List of Figures

Figure 13-18 3 sector (4/4/4), air combining, medium power duplexers........................................................................ 13-22 Figure 13-19 3 sector (4/4/4), air combining, medium power duplexers........................................................................ 13-23 Figure 13-20 3 sector (4/4/4), cavity combining ............................................................................................................ 13-24 Figure 13-21 3 sector (4/4/4), 3-input CBF, hybrid combining....................................................................................... 13-25 Figure 13-22 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers................................................... 13-27 Figure 13-23 3 sector (5/5/5), 3-input CBF, air combining, medium power duplexers................................................... 13-29 Figure 13-24 3 sector (5/5/5), 3-input CBF, combining, medium power duplexers........................................................ 13-30 Figure 13-25 3 sector (6/6/6), cavity combining, high power duplexers ........................................................................ 13-31 Figure 13-26 3 sector (6/6/6), 3-input CBF, air combining, medium power duplexers................................................... 13-32 Figure 13-27 3 sector (6/6/6), 3-input CBF, combining, medium power duplexers........................................................ 13-33 Figure 13-28 3 sector (8/8/8), cavity combining, medium power duplexers (Part 1)...................................................... 13-34 Figure 13-29 3 sector (8/8/8), cavity combining, medium power duplexers (Part 2)...................................................... 13-35 Figure 13-30 3 sector (8/8/8), cavity combining, high and medium power duplexers (Part 1) ....................................... 13-36 Figure 13-31 3 sector (8/8/8), cavity combining, high and medium power duplexers (Part 2) ....................................... 13-37 Figure 13-32 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers (Part 1)...................................... 13-39 Figure 13-33 3 sector (8/8/8), 3-input CBF, air combining, medium power duplexers (Part 2)...................................... 13-40 Figure 13-34 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers (Part 1)........................................... 13-41 Figure 13-35 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers (Part 2)........................................... 13-42 Figure 13-36 3 sector (2/2/2), hybrid combining............................................................................................................ 13-43 Figure 13-37 3 sector (2/2/2), hybrid combining, medium power duplexers .................................................................. 13-44 Figure 13-38 2 carrier, single sector, hybrid combining................................................................................................. 13-45 Figure 13-39 2 carrier, single sector, hybrid combining, medium power duplexer......................................................... 13-46 Figure 13-40 2 sectors (1 carrier per sector) ................................................................................................................. 13-47 Figure 13-41 2 carrier, single sector, air combining ...................................................................................................... 13-48 Figure 13-42 2 sectors .................................................................................................................................................. 13-49

68P02900W21-S 01 Feb 2007 xxvii

List of Figures

68P02900W21-S xxviii 01 Feb 2007

List of Tables

List of Tables
Table 1-1 Version information .............................................................................................................................................. 2 Table 1-2 Resolution of Service Requests ........................................................................................................................... 2 Table 1-3 Incorporation of CDCNs ....................................................................................................................................... 3 Table 1-1 Transceiver unit usage...................................................................................................................................... 1-5 Table 1-2 Acronym list .................................................................................................................................................... 1-25 Table 2-1 BSS interface .................................................................................................................................................... 2-3 Table 2-2 RTF types ....................................................................................................................................................... 2-16 Table 3-1 dBm and dBW to power conversion ................................................................................................................ 3-18 Table 3-2 Speech channel coding................................................................................................................................... 3-49 Table 3-3 AMR codecs, convolutional output bits and punctured bits ............................................................................. 3-53 Table 3-4 X, Y and Z bit values for AMR FR speech channel encoding.......................................................................... 3-57 Table 3-5 X, Y, Z and W bit values for AMR HR speech channel encoding .................................................................... 3-59 Table 3-6 Interleaving ..................................................................................................................................................... 3-64 Table 3-7 Distribution of 456 bits from one 20 ms full rate speech sample ..................................................................... 3-67 Table 3-8 Distribution of 228 bits from one 20 ms half rate speech sample .................................................................... 3-67 Table 3-9 Coding parameters for GPRS coding schemes .............................................................................................. 3-75 Table 3-10 Coding parameters for EGPRS coding schemes .......................................................................................... 3-86 Table 3-11 Frequency and parameter setting plan........................................................................................................ 3-102 Table 3-12 Typical parameters for BTS call planning.................................................................................................... 3-111 Table 3-13 Control channel configurations.................................................................................................................... 3-123 Table 3-14 Example Configurations .............................................................................................................................. 3-133 Table 3-15 Control channel configurations for non-border location area....................................................................... 3-133 Table 3-16 Control channel configurations for border location area.............................................................................. 3-135 Table 3-17 MM state model of MS ................................................................................................................................ 3-139 Table 3-18 Capping settings ......................................................................................................................................... 3-142 Table 3-19 CTU2D output power .................................................................................................................................. 3-142 Table 3-20 DRI-RTF Mapping functionality ................................................................................................................... 3-143 Table 3-21 Arrangement of packet data timeslots for example 1 .................................................................................. 3-147 Table 3-22 Arrangement of packet data timeslots for example 2 .................................................................................. 3-147 Table 3-23 Arrangement of packet data timeslots for example 3 .................................................................................. 3-148 Table 3-24 Arrangement of packet data timeslots for example 4 .................................................................................. 3-149 Table 3-25 Arrangement of packet data timeslots for example 5 .................................................................................. 3-150

68P02900W21-S 01 Feb 2007 xxix

List of Tables

Table 3-26 Arrangement of packet data timeslots for example 6 .................................................................................. 3-150 Table 3-27 Arrangement of packet data timeslots for example 7 .................................................................................. 3-151 Table 3-28 Arrangement of packet data timeslots for example 8 .................................................................................. 3-151 Table 3-29 Arrangement of packet data timeslots for example 9 .................................................................................. 3-152 Table 3-30 Switchable timeslot utilization (Part A) ........................................................................................................ 3-156 Table 3-31 Switchable timeslot utilization (Part B) ........................................................................................................ 3-158 Table 3-32 Typical TCP throughput against RLC/MAC throughput at zero block error rate .......................................... 3-166 Table 3-33 for various transfer delays at GBR 15 kbit/s or less ................................................................................. 3-167 Table 3-34 for transfer delay = 500 ms at GBR greater than 15 kbit/s ....................................................................... 3-168 Table 3-35 for transfer delay = 250 ms at GBR greater than 15 kbit/s ....................................................................... 3-169 Table 3-36 ARP mobile selection (ARP Rank) order..................................................................................................... 3-170 Table 3-37 BSS ARP configuration Parameters............................................................................................................ 3-171 Table 3-38 Percentage of code utilization in a 4x3 non-hopping re-use pattern at 20% BLER ..................................... 3-172 Table 3-39 MTBR Mix ................................................................................................................................................... 3-176 Table 3-40 MTBR Constant........................................................................................................................................... 3-176 Table 3-41 THP Weight Mix .......................................................................................................................................... 3-176 Table 3-42 THP Weight Constant.................................................................................................................................. 3-176 Table 3-43 QoS Configuration Examples ...................................................................................................................... 3-177 Table 3-44 QoS Disabled; Capacity: 18 users, DL Throughput per MS: 0.33 (6/18) TS ............................................... 3-178 Table 3-45 QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11) TS ................................................ 3-179 Table 3-46 GPRS downlink data rates (kbit/s) with TCP (CS1)..................................................................................... 3-187 Table 3-47 GPRS downlink data rates (kbit/s) with TCP (CS2)..................................................................................... 3-188 Table 3-48 GPRS downlink data rates (kbit/s) with TCP (CS3)..................................................................................... 3-188 Table 3-49 GPRS downlink data rates (kbit/s) with TCP (CS4)..................................................................................... 3-188 Table 3-50 GPRS downlink data rates (kbit/s) with UDP (CS1) .................................................................................... 3-189 Table 3-51 GPRS downlink data rates (kbit/s) with UDP (CS2) .................................................................................... 3-189 Table 3-52 GPRS downlink data rates (kbit/s) with UDP (CS3) .................................................................................... 3-189 Table 3-53 GPRS downlink data rates (kbit/s) with UDP (CS4) .................................................................................... 3-190 Table 3-54 EGPRS downlink data rates (kbit/s) with TCP (MCS1) ............................................................................... 3-190 Table 3-55 EGPRS downlink data rates (kbit/s) with TCP (MCS2) ............................................................................... 3-190 Table 3-56 EGPRS downlink data rates (kbit/s) with TCP (MCS3) ............................................................................... 3-191 Table 3-57 EGPRS downlink data rates (kbit/s) with TCP (MCS4) ............................................................................... 3-191 Table 3-58 EGPRS downlink data rates (kbit/s) with TCP (MCS5) ............................................................................... 3-191 Table 3-59 EGPRS downlink data rates (kbit/s) with TCP (MCS6) ............................................................................... 3-192 Table 3-60 EGPRS downlink data rates (kbit/s) with TCP (MCS7) ............................................................................... 3-192 Table 3-61 EGPRS downlink data rates (kbit/s) with TCP (MCS8) ............................................................................... 3-192 Table 3-62 EGPRS downlink data rates (kbit/s) with TCP (MCS9) ............................................................................... 3-193 Table 3-63 EGPRS downlink data rates (kbit/s) with UDP (MCS1) ............................................................................... 3-193 Table 3-64 EGPRS downlink data rates (kbit/s) with UDP (MCS2) ............................................................................... 3-193

68P02900W21-S xxx 01 Feb 2007

List of Tables

Table 3-65 EGPRS downlink data rates (kbit/s) with UDP (MCS3)............................................................................... 3-194 Table 3-66 EGPRS downlink data rates (kbit/s) with UDP (MCS4)............................................................................... 3-194 Table 3-67 EGPRS downlink data rates (kbit/s) with UDP (MCS5)............................................................................... 3-194 Table 3-68 EGPRS downlink data rates (kbit/s) with UDP (MCS6)............................................................................... 3-195 Table 3-69 EGPRS downlink data rates (kbit/s) with UDP (MCS7)............................................................................... 3-195 Table 3-70 EGPRS downlink data rates (kbit/s) with UDP (MCS8)............................................................................... 3-195 Table 3-71 EGPRS downlink data rates (kbit/s) with UDP (MCS9)............................................................................... 3-196 Table 4-1 AMR potential coverage gains ........................................................................................................................ 4-10 Table 4-2 Supported AMR codecs .................................................................................................................................. 4-16 Table 4-3 BSS parameters used to determine MS threshold and hysteresis .................................................................. 4-18 Table 4-4 Handover and power control - Full and Half Rate default values .................................................................... 4-20 Table 4-5 Backhaul configuration based on parameter settings...................................................................................... 4-31 Table 4-6 Call placement on terrestrial backhaul ............................................................................................................ 4-32 Table 4-7 Voice call mapping on the backhaul for a 64K RTF ........................................................................................ 4-32 Table 5-1 Transmit configurations................................................................................................................................... 5-11 Table 5-2 BBH capability for Horizon II macro Site Controller......................................................................................... 5-14 Table 5-3 BBH capability for Horizonmacro Site Controller............................................................................................. 5-14 Table 5-4 CTU/CTU2 power requirements...................................................................................................................... 5-18 Table 5-5 CTU/CTU2 power requirements for M-Cell cabinets ....................................................................................... 5-19 Table 5-6 Site connection requirements for M-Cell2 and M-Cell6 ................................................................................... 5-23 Table 5-7 Horizon II macro XMUX expansion requirements ........................................................................................... 5-29 Table 5-8 Horizon II mini only network XMUX expansion requirements.......................................................................... 5-29 Table 5-9 Horizon II macro as master - Horizon II mini as expansion XMUX requirements ............................................ 5-29 Table 5-10 Horizon II macro as master - Horizon II mini as expansion XMUX requirements .......................................... 5-30 Table 5-11 Horizonmacro FMUX expansion requirements.............................................................................................. 5-30 Table 6-1 BSC maximum capacities ................................................................................................................................. 6-5 Table 6-2 Typical call parameters ................................................................................................................................... 6-10 Table 6-3 Other parameters used in determining GPROC and link requirements........................................................... 6-14 Table 6-4 Signaling message procedures ....................................................................................................................... 6-15 Table 6-5 BTS support for 16 kbit/s RSLs ....................................................................................................................... 6-19 Table 6-6 Number of BSC to BTS signaling links (without LCS) ..................................................................................... 6-20 Table 6-7 Backhaul requirements ................................................................................................................................... 6-28 Table 6-8 Number of MSC and BSC signaling links without LCS (20% utilization) ......................................................... 6-34 Table 6-9 Number of MSC and BSC signaling links without LCS (40% utilization) ......................................................... 6-34 Table 6-10 Number of MSC and BSC signaling links without LCS (20% utilization) ....................................................... 6-35 Table 6-11 Number of BSC to RXCDR signaling links .................................................................................................... 6-42 Table 6-12 Typical call parameters relating to XBLs ....................................................................................................... 6-43 Table 6-13 GPROC type/function.................................................................................................................................... 6-50 Table 6-14 BSS configurations and their availability ....................................................................................................... 6-56

68P02900W21-S 01 Feb 2007 xxxi

List of Tables

Table 6-15 KSWX/DSWX (non-redundant) ..................................................................................................................... 6-73 Table 6-16 KSWX/DSWX (redundant) ............................................................................................................................ 6-74 Table 7-1 RXCDR maximum capacities ............................................................................................................................ 7-4 Table 7-2 KSWX/DSWX (non-redundant) ....................................................................................................................... 7-25 Table 7-3 KSWX/DSWX (redundant) .............................................................................................................................. 7-25 Table 8-1 VersaTRAU backhaul recommendations for a given number of PDTCHs......................................................... 8-7 Table 8-2 Expected throughput/TS and coding schemes (conservative) .......................................................................... 8-8 Table 8-3 Expected throughput/TS and coding schemes (aggressive) ............................................................................. 8-9 Table 8-4 Erlang table ..................................................................................................................................................... 8-12 Table 8-5 BSS upgrade in support of GPRS/EGPRS...................................................................................................... 8-13 Table 8-6 Recommended maximum BSS network parameter values (part A) ................................................................ 8-15 Table 8-7 Recommended maximum BSS parameter values (part B).............................................................................. 8-16 Table 8-8 Recommended maximum BSS network parameter (part C) ........................................................................... 8-18 Table 8-9 Maximum number of timeslots that can be processed .................................................................................... 8-22 Table 8-10 Maximum number of timeslots that can be provisioned................................................................................. 8-23 Table 8-11 Provisioning goals (per PCU) ........................................................................................................................ 8-36 Table 8-12 Provisioning goals (per PCU) ........................................................................................................................ 8-40 Table 8-13 Upgrade scenarios for PRP configuration ..................................................................................................... 8-41 Table 8-14 Upgrade scenarios for PXP configuration ..................................................................................................... 8-42 Table 8-15 Local Timeslot Zone Level capacity 4MS/PDTCH......................................................................................... 8-46 Table 8-16 PRP Board Service Level Capacity 4MS/PDTCH ......................................................................................... 8-46 Table 8-17 Maximum MTBR in UL/DL per multislot capability ........................................................................................ 8-48 Table 8-18 for various transfer delays at GBR 15kbit/s or less .................................................................................... 8-51 Table 8-19 for Transfer delay = 500 ms at GBR greater than 15 kbit/s ........................................................................ 8-52 Table 8-20 for Transfer delay = 250 ms at GBR greater than 15 kbit/s ........................................................................ 8-53 Table 8-21 Gb entities and identifiers.............................................................................................................................. 8-57 Table 8-22 GPRS call model ........................................................................................................................................... 8-63 Table 8-23 EGPRS call model......................................................................................................................................... 8-70 Table 8-24 EGPRS with QoS enabled call model ........................................................................................................... 8-76 Table 8-25 EGPRS with QoS and QoS2 enabled call model .......................................................................................... 8-83 Table 9-1 Busy hour demand and number of carriers ....................................................................................................... 9-2 Table 9-2 Customer ordering guide 900 MHz (M-Cell6 indoor) ......................................................................................... 9-6 Table 9-3 Customer ordering guide 900 MHz (M-Cell6 indoor) ......................................................................................... 9-6 Table 9-4 Customer ordering guide 1800 MHz (Horizon II macro indoor) ......................................................................... 9-9 Table 9-5 Customer ordering guide 1800 MHz (Horizon II macro indoor) ....................................................................... 9-10 Table 9-6 GPROCs required at the BSC......................................................................................................................... 9-11 Table 9-7 BSC timeslot requirements.............................................................................................................................. 9-12 Table 9-8 Equipment required for the BSC ..................................................................................................................... 9-13 Table 9-9 Equipment required for the RXCDR ................................................................................................................ 9-16

68P02900W21-S xxxii 01 Feb 2007

List of Tables

Table 9-10 BSU Shelves ................................................................................................................................................. 9-42 Table 9-11 RXU shelves ................................................................................................................................................. 9-46 Table 9-12 Cell planning - control channel calculations (based on Erlang B models) ..................................................... 9-49 Table 9-13 GPROCs and MSI cards ............................................................................................................................... 9-56 Table 9-14 RXU shelves ................................................................................................................................................. 9-59 Table 9-15 Control channel calculation ........................................................................................................................... 9-63 Table 9-16 BSU shelves ................................................................................................................................................. 9-69 Table 9-17 Determining the number of XCDR/GDP/GDP2 cards ................................................................................... 9-72 Table 9-18 RXU3 shelves ............................................................................................................................................... 9-73 Table 9-19 KSW/DSW2 requirements ............................................................................................................................ 9-84 Table 9-20 Typical LCS call model parameter ................................................................................................................ 9-86 Table 9-21 BSU shelves ................................................................................................................................................. 9-98 Table 10-1 Example of values for the parameters for location area planning ................................................................. 10-3 Table 11-1 Typical parameters for BTS call planning...................................................................................................... 11-2 Table 11-2 Sample Statistics......................................................................................................................................... 11-38 Table 12-1 Equipment required for 4 or 8 carrier omni with HCUs and air combining................................................... 12-21 Table 12-2 Equipment required for 6 or 12 carrier omni with DHUs.............................................................................. 12-22 Table 12-3 Equipment required for 2 sector 3/3 or 6/6 with DHUs ................................................................................ 12-23 Table 12-4 Equipment required for 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining .................................. 12-24 Table 12-5 Equipment required for 3 sector 2/2/2 or 4/4/4 with HCUs .......................................................................... 12-25 Table 12-6 Equipment required for 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining ............................ 12-26 Table 12-7 Equipment required for 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity......................................................... 12-27 Table 12-8 Equipment required for 3 sector 2/2/2 and 2/2/2 ......................................................................................... 12-29 Table 12-9 Equipment required for 4 or 8 carrier omni with HCUs and air combining................................................... 12-31 Table 12-10 Equipment required for 6 or 12 carrier omni with DHUs............................................................................ 12-32 Table 12-11 Equipment required for 2 sector 3/3 or 6/6 with HCUs .............................................................................. 12-33 Table 12-12 Equipment required for 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining ................................ 12-34 Table 12-13 Equipment required for 3 sector 2/2/2 or 4/4/4 .......................................................................................... 12-35 Table 12-14 Equipment required for 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining .......................... 12-36 Table 12-15 Equipment required for HP Omni-1/SP Omni-2......................................................................................... 12-37 Table 12-16 Equipment required for HP Omni-1/SP Omni-2......................................................................................... 12-38 Table 12-17 Equipment required for HP Omni-1/SP Omni-2......................................................................................... 12-39 Table 12-18 Equipment required for HP 2 sector 1/1/SP 2 sector 2/2........................................................................... 12-40 Table 12-19 Equipment required for HP 2 sector 2/2/SP 2 sector 4/4........................................................................... 12-41 Table 12-20 Equipment required for HP 3 sector 1/1/1/SP 3 sector 2/2/2..................................................................... 12-42 Table 12-21 Equipment required for HP 3 sector 1/1/1/SP 3 sector 2/2/2..................................................................... 12-44 Table 12-22 Equipment required for Horizon II micro one cabinet configuration........................................................... 12-45 Table 12-23 Equipment required for Horizon II micro three cabinet configuration......................................................... 12-47 Table 12-24 Equipment required for 1 cabinet, 4 CTU configuration, duplexed hybrid and air combining .................... 12-48

68P02900W21-S 01 Feb 2007 xxxiii

List of Tables

Table 12-25 Equipment required for 1 cabinet, 6 CTU configuration, duplex dual-stage hybrid and air combining ...... 12-49 Table 12-26 Equipment required for 1 cabinet, 6 CTU configuration, duplexed dual-stage hybrid combining .............. 12-50 Table 12-27 Equipment required for dual cabinet, 12 CTU configuration, duplexed dual-stage hybrid and air combining 1251 Table 12-28 Equipment required for 1 cabinet, 6 CTU configuration, duplexed hybrid combining ................................ 12-52 Table 12-29 Equipment required for dual cabinet, 12 CTU configuration duplexed hybrid and air combining .............. 12-53 Table 12-30 Equipment required for 4 cabinet, 24 CTU configuration, duplex dual-stage hybrid and air combining .... 12-55 Table 13-1 Equipment required for single cabinet, 4 TCU configuration with hybrid combining and diversity............... 13-11 Table 13-2 Equipment required for single cabinet, 4 TCU configuration with hybrid combining, diversity and medium power duplexer....................................................................................................................................................... 13-12 Table 13-3 Equipment required for single cabinet, 4 TCU configuration with hybrid combining and diversity............... 13-13 Table 13-4 Equipment required for single cabinet, 4 TCU configuration with hybrid combining, diversity and medium power duplexer....................................................................................................................................................... 13-14 Table 13-5 Equipment required for single cabinet, 6 TCU configuration with cavity combining and diversity ............... 13-15 Table 13-6 Equipment required for single cabinet, 6 TCU configuration with cavity combining, diversity and high power duplexer ................................................................................................................................................................. 13-16 Table 13-7 Equipment required for multiple cabinet, 8 TCU configuration with combining and diversity....................... 13-17 Table 13-8 Equipment required for single cabinet, 6 TCU configuration with hybrid combining and diversity............... 13-18 Table 13-9 Equipment required for single cabinet, 6 TCU configuration with combining, diversity and medium power duplexer ................................................................................................................................................................. 13-19 Table 13-10 Equipment required for single cabinet, 6 TCU configuration with combining and diversity........................ 13-20 Table 13-11 Equipment required for single cabinet, 6 TCU configuration with combining, diversity and medium power duplexers................................................................................................................................................................ 13-21 Table 13-12 Equipment required for dual cabinet, 12 TCU configuration with air combining, diversity and medium power duplexers (3 antenna per sector) ........................................................................................................................... 13-22 Table 13-13 Equipment required for multiple cabinet, 12 TCU configuration with air combining, diversity and medium power duplexers (2 antenna per sector)................................................................................................................. 13-23 Table 13-14 Equipment required for multiple cabinet, 12 TCU configuration with hybrid combining and diversity........ 13-24 Table 13-15 Equipment required for dual cabinet, 12 TCU configuration with 3-input CBF, hybrid combining and diversity ............................................................................................................................................................................... 13-26 Table 13-16 Equipment required for multiple cabinet, 12 TCU configuration with 3-input CBF, air combining, diversity and medium power duplexers ....................................................................................................................................... 13-28 Table 13-17 Equipment required for 3 cabinets, 15 TCU configuration with 3-input CBF, air combining, diversity and medium power duplexers (3 antennas/sector) ....................................................................................................... 13-29 Table 13-18 Equipment required for 3 cabinets, 15 TCU configuration with 3-input CBF, combining, diversity and medium power duplexers (2 antennas/sector) ..................................................................................................................... 13-30 Table 13-19 Equipment required for 3 RF cabinets, 18 TCU configuration with cavity combining, diversity and high power duplexers................................................................................................................................................................ 13-31 Table 13-20 Equipment required for 3 cabinets, 18 TCU configuration with 3-input CBF, air combining, diversity and medium power duplexers (3 antennas/sector) ....................................................................................................... 13-32 Table 13-21 Equipment required for 3 cabinets, 18 TCU configuration with 3-input CBF, combining, diversity and medium power duplexers (2 antennas/sector) ..................................................................................................................... 13-33 Table 13-22 Equipment required for 4 RF cabinets, 24 TCU configuration with cavity combining, diversity and medium power duplexers..................................................................................................................................................... 13-35 Table 13-23 Equipment required for 4 RF cabinets, 24 TCU configuration with cavity combining, diversity and both high and medium power duplexers ................................................................................................................................ 13-38

68P02900W21-S xxxiv 01 Feb 2007

List of Tables

Table 13-24 Equipment required for 4 cabinets, 24 TCU configuration with 3-input CBF, air combining, diversity and medium power duplexers (3 antennas/sector) ....................................................................................................... 13-40 Table 13-25 Equipment required for 4 cabinets, 24 TCU configuration with 3-input CBF, combining, diversity and medium power duplexers (2 antennas/sector) ..................................................................................................................... 13-42 Table 13-26 Equipment required for single cabinet, 6 TCU configuration with hybrid combining and diversity............. 13-43 Table 13-27 Equipment required for single cabinet, 6 TCU configuration with hybrid combining, diversity and medium power duplexers..................................................................................................................................................... 13-44 Table 13-28 Equipment required for single cabinet, 2 TCU configuration with hybrid combining and diversity............. 13-45 Table 13-29 Equipment required for single cabinet, 2 TCU configuration with hybrid combining, diversity and medium power duplexer ...................................................................................................................................................... 13-46 Table 13-30 Equipment required for single cabinet, 2 TCU configuration with diversity................................................ 13-47 Table 13-31 Equipment required for single cabinet, 2 TCU configuration with air combining and diversity .................. 13-48 Table 13-32 Equipment required for single cabinet, 2 TCU configuration with diversity................................................ 13-49

68P02900W21-S 01 Feb 2007 xxxv

List of Tables

68P02900W21-S xxxvi 01 Feb 2007

About This Manual

System Information: BSS Equipment Planning

This manual provides an overview of the various BSS elements and BSS planning methodology. It describes the requirements and procedures for planning a BSS cell site, a BTS including Horizon and M-cell range of equipments, a BSC including the scenario when a LCS is used, an RXCDR and location area. It provides an overview of AMR and its usage in the Motorola system. It describes about obtaining the call model parameters from network statistics collected at the OMC-R. This manual also deals with standard BSS, Horizon BTS and M-Cell BTS configurations.

68P02900W21-S 01 Feb 2007 1

Issue status of this manual

Issue status of this manual

The following shows the issue status of this manual since it was first released.

Version information
The following lists the versions of this manual in order of manual issue: Table 1-1 Version information Manual issue O A B C D E F G H J K L M N P Q R S Date of issue 03 Oct 1994 30 Dec 1994 01 Sep 1995 31 May 1995 28 Mar 1997 29 Aug 1997 27 Apr 1998 15 Apr 2000 27 Feb 2001 15 Aug 2001 15 Apr 2002 Not issued 13 Mar 2003 Not issued 11 Sep 2003 15 Mar 2004 11 Jan 2005 01 Feb 2007 Issue P - includes GSM Software Release 7 and EGPRS Issue Q - includes GSM Half Rate Issue R - includes GSM Software Release 8 Issue S - Software release GSR9 Issue M - includes GSM Software Release 6 (Horizon II) Remarks Original issue - Software Release GSR 1.2.2.x Issue A - Software Release 1.2.3.x Issue B - Software Release 1.3.0.x Issue C - Software Release 1.4.0.x Issue D - (also supersedes 68P02900W31-B) Issue E - includes GSM Software Release 3 Issue F - includes GSM Software Release 3 Issue G - includes GSM Software Release 4.1 (1.6.1.3) Issue H - includes GSM Software Release 5 Issue J - includes GSM Software Release 5.1 Issue K - includes GSM Software Release 6

Resolution of Service Requests

The following Service Requests are now resolved in this manual: Table 1-2 Resolution of Service Requests Service Request N/A GMR Number N/A Remarks

68P02900W21-S 2 01 Feb 2007

Issue status of this manual

Incorporation of CDCNs
The following CDCNs are now incorporated in this manual: Table 1-3 Incorporation of CDCNs CDCN N/A GMR Number N/A Remarks

68P02900W21-S 01 Feb 2007 3

General information

General information

Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or any one acting on behalf of the customer, to abide by the instructions, system parameters or recommendations made in this manual. If this manual was obtained when you attended 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) or Customer Documentation Change Notices (CDCNs).

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.

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.

Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features released at Motorola General System Releases (GSRn), GPRS Support Node (GSNn) releases or UMTS System Releases (USRn). In these manuals, new and amended features are tagged to help users to assess the impact on installed networks. The tags are the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and Development Prioritization (RDP) numbers. The tags include index references which are listed in the manual Index. The Index includes the entry feature which is followed by a list of the RDB or RDP numbers for the released features, with page references and hot links in electronic copy. The tags have the format: {nnnn} or {nnnnn}. Where {nnnn} {nnnnn} Is the RDB number The RDP number

68P02900W21-S 4 01 Feb 2007

General information

The tags are positioned in text as follows: New and amended feature information Complete new sections of content as follows: All sections under a main heading All paragraphs under subheadings Tag position in text In the heading immediately after the heading content as follows: Main heading {nnnn} Subheading {nnnn}

Single paragraphs of new or amended text. New or amended complete Figures and Tables Warnings, Cautions and NOTEs. General command syntax, user input or displays (in special fonts). Computer output displays (in special fonts).

Immediately before the affected paragraph. After the Figure or Table number and before the title text. Immediately before the affected text in the Warning, Caution or NOTE. On a separate line immediately the affected item or immediately before the affected item. On a separate line immediately the affected item or immediately before the affected item.

For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this software release, refer to the manual System Information: GSM Overview (68P02901W01), to the manual System Information: GPRS Overview (68P02903W01), or to the manual System Information: UMTS Overview (68P02905W21).

Cross references
Throughout this manual, references are made to external publications, chapter numbers and section names. The references to external publications are shown in italics, chapter and section name cross references are emphasized blue 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.

Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM, GPRS or UMTS network is encrypted. In order to comply with the export and import requirements of particular countries, this encryption occurs at different levels as individually standardized, 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.

68P02900W21-S 01 Feb 2007 5

General information

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: CRTL-c ALT-f | 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.

68P02900W21-S 6 01 Feb 2007

Reporting safety issues

Reporting safety issues

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: Procedure 1 Reporting safety issues
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 88417733 (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.

68P02900W21-S 01 Feb 2007 7

Warnings and cautions

Warnings and cautions

The following describes how warnings and cautions are used in this manual and in all manuals of this Motorola manual set.

Warnings
A definition and example follow:

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

Do not look directly into fiber optic cables or data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fiber 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 customer's failure to comply with these requirements.

Cautions
A definition and example follow:

Definition of Caution
A caution means that there is a possibility of damage to systems, or individual items of equipment within a system. However, this presents no danger to personnel.

Example and format

Do not use test equipment that is beyond its due calibration date; arrange for calibration to be carried out.

68P02900W21-S 8 01 Feb 2007

General warnings

General warnings
Observe the following specific warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola manuals: 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 customer's 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.

Specific warnings
Specific warnings used throughout the manual sets are shown, 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

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.

68P02900W21-S 01 Feb 2007 9

General warnings

High voltages are not utilized in Motorola GSM, GPRS or UMTS equipment.

Electric shock

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

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: ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz. CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10 kHz to 300 GHz).

Laser radiation

Do not look directly into fiber optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fiber optic cables connected to data in/out connectors.

68P02900W21-S 10 01 Feb 2007

General warnings

Lifting equipment

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

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

Do not wear earth straps when working with standby battery supplies.

Lithium batteries

Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithium batteries must not be removed or replaced. Any boards containing defective lithium batteries must be returned to Motorola for repair. Contact your local Motorola office for how to return defective lithium batteries.

68P02900W21-S 01 Feb 2007 11

General cautions

General cautions
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.

Fiber optics

Fiber optic cables must not be bent in a radius of less than 30 mm.

Static discharge

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.

68P02900W21-S 12 01 Feb 2007

Devices sensitive to static

Devices sensitive to static

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 dispatched 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: Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible, work on an earthed metal surface. Wipe insulated plastic work surfaces with an antistatic 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.

68P02900W21-S 01 Feb 2007 13

Caring for the environment

Caring for the environment

The following information is provided to enable regulatory compliance when using Motorola Networks equipment in EU countries with the following directives (and any subsequent amendments thereto): European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE). European Parliament and Council Directive 94/62/EC Packaging and Packaging waste.

Disposal of Motorola Networks equipment in EU countries

Please do not dispose of Motorola Networks equipment or packaging materials in landfill sites. In the EU, Motorola Networks in conjunction with a recycling partner will ensure that equipment and any surplus packaging materials are collected and recycled according to the requirements of EU environmental law. Please contact the Customer Network Resolution Center (CNRC) for assistance. The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com/. Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.

Disposal of Motorola Networks equipment in non-EU countries

In non-EU countries, dispose of Motorola Networks equipment in accordance with national and regional regulations.

68P02900W21-S 14 01 Feb 2007

Motorola manual set

Motorola manual set

The Motorola manual sets provide the information needed to operate, install and maintain the Motorola equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media: Printed hard copy Electronic, as fully navigable PDF files on: o o The Motorola customer support web site at: (https://mynetworksupport.motorola.com/index.asp). CD-ROM produced in support of a major system software release.

Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software release, together with current versions of appropriate hardware manuals, and has additional navigation facilities. A snapshot copy of on-line documentation is also included, though it will not be updated in line with subsequent point releases. The CD-ROM does not include Release NOTEs or documentation supporting specialist products such as MARS or COP.

Ordering manuals and CD-ROMs

Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs. All orders must be placed with your Motorola Local Office or Representative.

68P02900W21-S 01 Feb 2007 15

Manual amendment

Manual amendment
Changes to a manual that occur after the printing date are incorporated into the manual using either Customer Documentation Change Notices (CDCNs) or General Manual Revisions (GMRs): Small changes are published in CDCNs. These describe the changes rather than replacing large sections of the manual. They are sent directly to customers and Motorola Local Offices and are accessible on the Motorola Extranet. CDCNs are numbered in sequence using the format: o o o Shortened manual order number Issue identifier CDCN number

For example: 01W23-M-CDCN01 would be the first CDCN produced for 68P2901W23-M. Major changes are effected by publishing a GMR. GMRs are also produced in order to incorporate CDCNs when the numbers applying to a particular manual become significant. In this case, the CDCNs numbers are listed in the GMR amendment record. GMRs are issued to correct Motorola manuals as and when required. A GMR has the same identity as the target manual. Each GMR is identified by a number in a sequence that starts at 01 for each manual at each issue.

GMR availability
GMRs are published as follows: Printed hard copy - Complete replacement content or loose leaf pages with amendment list. o Remove and replace pages in this manual, as detailed on the GMR instruction sheet. Motorola service web - Updated at the same time as hard copies. CD-ROM - Updated periodically as required.

CDCN availability
CDCNs are published as follows: PDF distributed electronically - Description of changes, occasionally with replacement loose leaf pages. Motorola service web - Updated at the same time as hard copies.

CDCN instructions
When a CDCN is incorporated in this manual, the record is completed to record the amendment. Retain the instruction sheet that accompanies each CDCN and insert it in a suitable place in this manual for future reference.

68P02900W21-S 16 01 Feb 2007

CDCN amendment record

CDCN amendment record

Record the insertion of CDCNs in this manual in the following table: CDCN number Incorporated by (signature) Date

68P02900W21-S 01 Feb 2007 17

CDCN amendment record

68P02900W21-S 18 01 Feb 2007

Chapter 1 Introduction to planning

An overview of this manual and the various elements of a BSS and the BSS planning methodology are provided here. Included is information about BSS system architecture, components, and features that can affect the planning stage together with information required before planning can begin. The following topics are described: Manual overview BSS equipment overview BSS features BSS planning overview

OMC-R planning is beyond the scope of this manual. For information on installing a new OMC-R, refer to 68P02901W47, Installation and Configuration: OMC-R Clean Install. For information on upgrading an existing OMCR for this software release, refer to 68P02901W74, Software Release NOTEs: OMC-R System.

68P02900W21-S 01 Feb 2007 1-1

Manual overview

Chapter 1: Introduction to planning

Manual overview
Introduction
The manual contains information about planning a GSM network, and utilizing a combination of Horizon and M-Cell BTS equipment.

Contents
The manual contains the following chapters: Chapter 1: Introduction to planning Provides an overview of the various elements of a BSS and the BSS planning methodology. Chapter 2: Transmission systems This chapter provides an overview of the transmission systems used in GSM. Chapter 3: BSS cell planning States the requirements and procedures used in producing a BSS cell site plan. Chapter 4: AMR and GSM planning Provides an overview of the AMR and usage in the Motorola system. Chapter 5: BTS planning steps and rules Provides the planning steps and rules for the BTS, including the Horizon and M-Cell range of equipments. Chapter 6: BSC planning steps and rules Provides the planning steps and rules for the BSC, including when LCS is used. Chapter 7: RXCDR planning steps and rules Provides the planning steps and rules for the RXCDR. Chapter 8: PCU upgrade for BSS Provides information for the PCU upgrade to the BSS. Chapter 9: Planning exercises Provides planning exercises designed to illustrate the use of the rules and formulae provided in Chapters 3, 4, 5, 6, 7 and 8. Chapter 10: Location area planning Provides the planning steps and rules for location area planning. Chapter 11: Call model parameters Provides the planning steps and rules for deriving call model parameters from network statistics collected at the OMC-R.

68P02900W21-S 1-2 01 Feb 2007

System Information: BSS Equipment Planning

Manual overview

Chapter 12: Standard BSS and Horizon BTS configurations Provides diagrams of the logical interconnections of the components in various standard BSS and Horizon BTS site configurations.

Chapter 13: M-Cell BTS configurations Provides diagrams of the logical interconnections of the components in various M-Cell BTS site configurations.

68P02900W21-S 01 Feb 2007 1-3

BSS equipment overview

Chapter 1: Introduction to planning

BSS equipment overview

System architecture
The architecture of the Motorola Base Station System (BSS) is versatile, and allows several possible configurations for a given system. The BSS is a combination of digital and RF equipment that communicates with the Mobile Switching Centre (MSC), the Operations and Maintenance Centre Radio (OMC-R), and the Mobile Stations (MS) as shown in Figure 1-1. Figure 1-1 BSS block diagram
MSC LRs A INTERFACE

OMC-R

SGSN

RXCDR O&M

BSS

PCU ABIS INTERFACE

BSC

BSS

BTS 1

BTS 5

BTS 8

...

BTS n

BTS 2

BTS 6

BTS 3

BTS 7

BTS 4

AIR INTERFACE MS MS

...

MS

MS

...

68P02900W21-S 1-4 01 Feb 2007

System Information: BSS Equipment Planning

BSS equipment overview

The OMC-R can be linked through the RXCDR and/or to the BSS/BSC direct. The example of multiple MSs connected to BTS 4 and BTS 7, is assumed to be connected to all the other BTSs as shown in Figure 1-1.

System components
The BSS is divided into a Base Station Controller (BSC), Remote Transcoder (RXCDR), Packet Control Unit (PCU) and one or more Base Transceiver Stations (BTSs). These can be in-built or externally located Horizon II macro, Horizonmacro, or M-Cell BTS cabinets or enclosures. The Transcoder (XCDR) or Generic Digital Processor (GDP, EGDP, or GDP2) provides 4:1 multiplexing of the traffic, and can be located at the BSC or between the BSC and MSC. When half rate is in use, it is possible to achieve a greater reduction (refer to the transcoding sections of Chapter 6 and Chapter 7 for a detailed description). When the XCDR/GDP/EGDP/GDP2 is located at the MSC, it reduces the number of communication links to the BSC. When transcoding is not performed at the BSC, the XCDR is referred to as a remote transcoder (RXCDR). The RXCDR is part of the BSS but can serve more than one BSS. In the Motorola BTS product line, the radio transmit and receive functions are provided as listed in Table 1-1: Table 1-1 Transceiver unit usage Transceiver unit Compact Transceiver Unit 2 D (CTU2-D) Compact Transceiver Unit 2 (CTU2) Where used Horizon II macro, Horizon II micro, Horizon II Mini, and Horizon II Extension off H2 master. Horizon II macro, Horizonmacro (with limitations see CTU2 on page 1-5 on next page), M-Cell6 and MCell2 with CTU2 Adapter. Horizonmacro. Horizonmicro, Horizonmicro2, Horizoncompact and Horizoncompact2. M-Cell6, M-Cell2 and BTS6. M-Cell6 and M-Cell2. M-Cellmicro, M-Cellcity and M-Cellcity+.

Compact Transceiver Unit (CTU) Dual Transceiver Module (DTRX) Transceiver Control Unit (TCU) Transceiver Control Unit (TCU-B) Transceiver Control Unit, micro (TCU-m)

68P02900W21-S 01 Feb 2007 1-5

BSS equipment overview

Chapter 1: Introduction to planning

Except for the TCU, which is backwards compatible by switching from TCU to SCU on the front panel, all other transceiver units are only compatible with the equipment listed.

CTU2D

The CTU2-D is not currently part of GSR9, and will be delivered in a separate software load. In Horizon II family which includes Horizon II macro, Horizon II micro, Horizon II Mini, and Horizon II Extension off H2 master, the transceiver functions are provided by the CTU2D. It can be configured to operate in single or double density mode. CTU2D retains the behavior of CTU2 and extends to support two simultaneous carriers for EGPRS (Carrier B UL GMSK limited). The main reason for CTU2D not supporting unrestricted EDGE on both carriers is MIPS constraints of the host processor. CTU2D radio can support the following working modes: CTU2D single density mode: This mode is identical in operation to the existing CTU2 single density mode. CTU2D double density power mode: This mode is also known as ITS Mode whereby the CTU2 and CTU2D operations are identical. CTU2D double density capacity mode: Of the two carriers, carrier A is fully EDGE-capable, while carrier B supports GPRS/TCH. TS blanking is not required. The maximum output power of carrier A in 8PSK mode is 10 W* and GMSK mode is 20 W*. The maximum output power carrier B (GMSK only) is always 20 W*. CTU2D double density asymmetric mode: Of the two carriers, carrier A is fully EDGEcapable, while carrier B supports EDGE on the DL and GMSK (EDGE) on the UL. The maximum output power of carrier A in 8PSK mode is 10 W* and GMSK mode is 20 W*. The maximum output power of carrier B in GMSK mode is 20 W*.

The output powers listed are for 900 MHz frequency. For all other frequencies, the output power varies. The hybrid of CTU2 and CTU2D can be configured in different operational modes within one cell. Description and planning rules for the CTU2 are provided in Chapter 5 of this manual. Configuration diagrams are shown in Chapter 12. The receivers can support receive diversity.

68P02900W21-S 1-6 01 Feb 2007

System Information: BSS Equipment Planning

BSS equipment overview

CTU2
In Horizon II macro, the transceiver functions are provided by the CTU2, which can be configured to operate in single or double density mode. This CTU2 can also be used by Horizonmacro as a CTU replacement with restrictions (see NOTE on page 1-7). Depending on the number of CTU/CTU2s in the Horizonmacro cabinet, there are output power restrictions that needs a mandatory third power supply installed in the Horizonmacro cabinet. This can affect the battery hold-up module in ac-powered cabinets, as the location for the third power supply means that the battery hold-up module has to be removed, and an external battery backup unit added. There are no available slots for the redundant power supply if three power supplies are required. The CTU2 can also be used by M-Cell6 and M-Cell2 with a CTU2 Adapter. The M-Cell6 cabinet requires up to three power supplies when used with CTU2s. The M-Cell2 cabinet requires up to two power supplies when used with CTU2s. Description and planning rules for the CTU2 are provided in Chapter 5 of this manual. Configuration diagrams are shown in Chapter 12. The receivers can support receive diversity.

CTU2s do not support the use of CCBs. A CTU2 cannot be CCB equipped and does not act as a full replacement or swap for the CTU. The CTU2 only acts as a CTU replacement in the non-controller or standby controller mode. Contact the Motorola Local Office for details. When installed in Horizonmacro, the CTU2 only supports baseband hopping in single density mode.

CTU
In Horizonmacro, the transceiver functions are provided by the CTU. Description and planning rules for the CTU are provided in Chapter 5 of this manual. Configuration diagrams are shown in Chapter 12. The receivers can support receive diversity.

DTRX
In Horizonmicro, Horizonmicro2, Horizoncompact, and Horizoncompact2, the transceiver functions are provided by the dual transceiver module (DTRX). System planning is described in Chapter 2 and configuration diagrams are shown in Chapter 12. The receivers do not support receive diversity.

TCU/TCU-B
In M-Cell6, M-Cell2, and BTS6, the transceiver functions are provided by the TCU or TCU-B (not BTS6). Description and planning rules for the TCU/TCU-B are provided in Chapter 5 of this manual. Configuration diagrams are shown in Chapter 13. The receivers can support receive diversity.

TCU-m
In M-Cellmicro, M-Cellcity and M-Cellcity+ the transceiver functions are provided by a pair of TCU-ms. The receivers do not support receive diversity.

68P02900W21-S 01 Feb 2007 1-7

BSS features

Chapter 1: Introduction to planning

BSS features
Planning impacts
This section provides a description of the software features that might affect the required equipment before planning the actual equipment. Check with the appropriate Motorola sales office regarding software availability with respect to these features. Diversity Frequency hopping Short Message, Cell Broadcast Code Storage Facility Processor Packet Control Unit (PCU) for General Packet Data Service (GPRS) upgrade Enhanced-GPRS (EGPRS) Adaptive Multi-Rate (AMR) GSM half rate Location services (LCS) BSC Reset Management (BRM) Advanced Speech Call Item VersaTRAU backhaul for EGPRS Quality of Service (QoS) {27703} QoS2 {28398} Increased Network Capacity (Huge BSC) Improved Timeslot Sharing (ITS) {22168}Enhanced BSC capacity using DSW2 {28337} High Speed MTL {28351} Add New BSC/PCU Software (PXP)/Hardware (PSI2) to increase GPRS capacity (ePCU) {26740} High Bandwidth interconnect between BSC and PCU (PSI2) {23291}Dual Transfer Mode (DTM) {30828} CTU2-D 96 MSIs

Diversity
Diversity reception (spatial diversity) at the BTS is obtained by supplying two uncorrelated receive signals to the transceiver. Each transceiver unit includes two receivers, which independently process the two received signals and combine the results to produce an output. This results in improved receiver performance when multipath propagation is significant and in improved interference protection.

68P02900W21-S 1-8 01 Feb 2007

System Information: BSS Equipment Planning

BSS features

Two Rx antennas are required for each sector. Equivalent overlapping antenna patterns and sufficient physical separation between the two antennas are required to obtain the necessary de-correlation.

Frequency hopping
There are two methods of providing frequency hopping synthesizer hopping and baseband hopping. Each method has different hardware requirements. The main differences are: Synthesizer hopping needs the use of wideband (hybrid) combiners for transmit combining, while baseband hopping does not. Baseband hopping needs the use of one transceiver for each allocated frequency, while synthesizer hopping does not.

Synthesizer hopping
Synthesizer hopping uses the frequency agility of the transceiver to change frequencies on a timeslot basis for both receive and transmit. The transceiver calculates the next frequency and re-programs its synthesizer to move to the new frequency. There are three important points to NOTE when using this method of providing frequency hopping: Use Hybrid combining. Cavity combining is not allowed when using synthesizer hopping. The output power available with the use of the hybrid combiners must be consistent with coverage requirements. It is only necessary to provide as many transceivers as required by the traffic. One transceiver in each sector must be on a fixed frequency to provide the BCCH carrier.

Baseband hopping
For baseband hopping, each transceiver operates on preset frequencies in the transmit direction. Baseband signals for a particular call are switched to a different transceiver at each TDM frame to achieve frequency hopping. There are three important points to NOTE when using this method of providing frequency hopping: The number of transceivers must be equal to the number of transmit (or receive) frequencies required. Use of either remote tuning combiners or hybrid combiners is acceptable. Calls could be dropped, if a single transceiver fails, due to the inability to inform the MSs.

Short Message Service, Cell Broadcast (SMS CB)

The Short Message Service, Cell Broadcast (SMS CB) feature, is a means of unilaterally transmitting data to MSs on a per cell basis. A Cell Broadcast Channel (CBCH) provides this feature. The data originates from either a Cell Broadcast Centre (CBC) or OMC-R (user-defined messages are entered using the appropriate MMI command). The CBC or OMC-R downloads cell broadcast messages to the BSC, together with indications of the repetition rate, and the number of broadcasts required per message. The BSC transmits these updates to the appropriate BTSs, which ensures that the message is transmitted as requested.

68P02900W21-S 01 Feb 2007 1-9

BSS features

Chapter 1: Introduction to planning

Code Storage Facility Processor (CSFP)

The BSS supports a GPROC acting as the Code Storage Facility Processor (CSFP). The CSFP allows preloading of a new software release while the BSS is operational. When BTSs are connected to the BSC, a CSFP is required at the BSC and a second CSFP is equipped for redundancy as required.

PCU for GPRS upgrade

The PCU hardware provides GPRS functionality and is part of the BSS equipment. GPRS introduced packet data services and GPRS planning are fundamentally different from the planning of circuit-switched networks. One of the reasons for the difference is that a GPRS network allows the queuing of data traffic instead of blocking a call when a circuit is unavailable. Consequently, the use of Erlang B tables for estimating the number of trunks or timeslots required is not a valid planning approach for the GPRS packet data provisioning process.

Enhanced-GPRS (EGPRS)
The Enhanced Data Rates for Global Evolution (EDGE) enhances the data throughput of the GPRS to enable the Enhanced-GPRS (EGPRS) system. The planning guide takes into account the larger data capacity of the system dependent on the expected EGPRS usage. The EGPRS feature is an extension to the software architecture introduced by the General Packet Radio Service (GPRS) feature, and the Coding Scheme 3/Coding Scheme 4 feature. This means that a network supporting EGPRS also provides support for the GSM voice and GPRS data. The following are some of the features included with EGPRS: EGPRS employs a new set of GSM modulation and channel coding techniques that increase a users packet data throughput from a maximum of 21.4 kbit/s per air timeslot with GPRS to a maximum of 59.2 kbit/s per air timeslot with EGPRS. The maximum data throughput for a multi-slot mobile utilizing all eight air timeslots with EGPRS is 473.6 kbit/s compared to 171.2 kbit/s in GPRS. The initial release of EGPRS provides support for a multi-slot mobile using four downlink and two uplink air timeslots. In GSR9, the EDMAC feature allows the support of mobiles classes 11 and 12 to enable 3 or 4 timeslot assignment in the UL. Support for the mobile classes, which dictate the multi-slot capabilities of a mobile and is the same for EGPRS as in GPRS (classes 1-12).

Although a large portion of the EGPRS impact, the BSS software is focused on the air interface. Impacts also exist on the terrestrial interfaces to carry the large volume of data traffic produced by these new data rates.

The data rates used here are theoretical values.

68P02900W21-S 1-10 01 Feb 2007

System Information: BSS Equipment Planning

BSS features

Adaptive Multi-Rate (AMR)

The AMR feature provides enhanced speech quality by adapting the speech and channel coding rates according to the quality of the radio channel. It provides increased capacity by allocating half rate channels to some or all mobiles. AMR selects the optimum channel rate as full rate (fr) or half rate (hr) and codec mode (speech and channel bit rates) to provide the best combination of speech quality and system capacity. The feature is tuned by the network user on a cell-by-cell basis to obtain the best balance between quality and capacity. AMR is introduced using current hardware components, or it can utilize new hardware that further enhances the benefits of AMR. Due to the increased processing requirements of AMR, the existing GDP (which currently supports 30 voice channels and data services) only supports 15 AMR voice channels. However, two GDPs are paired to support a full E1s worth of channels (30). This results in an overall reduction in transcoding shelf (or cage) capacity - 30 channels per GDP pair. The AMR program introduces new transcoder equipment (the GDP2), capable of supporting 60 voice (AMR or non-AMR) channels, thus reducing footprint. The existing RXU shelf has only one E1 connection per transcoder slot, hence the GDP2 only supports 30 channels when used in this configuration. A new RXU shelf (RXU3) and BSSC cabinet (BSSC3) have been introduced to utilize the added capacity.

When using the GDP2 within the new RXU3 shelf in a non-MSI slot, enhanced capacity mode must be enabled to access the second E1. The GDP2 can be used to full capacity in the existing BSU shelf, which has no associated E1 limitation.

The existing hardware supports 16 kbit/s switching on the backhaul between the BSC and BTS. Therefore, when using existing switching hardware, each half rate equipped RTF must have an additional two 64 kbit/s timeslots equipped to fully utilize all 16 half rate channels. The existing hardware also supports 16 kbit/s switching on the backhaul between the BSC and RXCDR, requiring 16 kbit/s per voice channel. The Double Kiloport Switch (DSW2) has been introduced to address the problem. The DSW2 supports double the number of ports (enhanced capacity mode) when used in the RXCDR, as well as subrate switching capability down to 8 kbit/s (extended subrate switching mode). With 8 kbit/s switching between the BSC and BTS, a half rate voice stream can be carried in an 8 kbit/s subchannel, rather than the 16 kbit/s subchannel required with KSWs. This eliminates the need for the two additional 64 kbit/s timeslots required per half rate capable RTF. There is one exception, that is, when the 7.95 kbit/s half rate codec mode is included in the half rate Active Codec Set. This codec mode needs 16 kbit/s backhaul, mandating the extra backhaul resources. The half rate Active Codec Set is provisioned on a per cell basis. Before AMR (and the use of half rate), all channels between the BSC and RXCDR (referred to as the Ater interface) required 16 kbit/s Ater channels, which were assigned during initialization/reconfiguration. With AMR, when a half rate traffic channel is assigned, the voice stream utilizes an 8 kbit/s channel (depending upon the codec modes employed). The DSW2 benefit of 8 kbit/s subrate switching allows this capability to be realized. Dynamic assignment of BSC to RXCDR channels is employed to maximize Ater channel usage. The BSC assigns an 8 or 16 kbit/s channel as required, based upon the backhaul in use across the BSC-BTS interface. This allows the operator to equip fewer channels than previously possible, with the assumption that some calls are utilizing half rate backhaul.

68P02900W21-S 01 Feb 2007 1-11

BSS features

Chapter 1: Introduction to planning

Extended range cells

AMR is only supported on the normal range timeslots and not on extended range timeslots. Intra-cell handovers are supported between the two types of timeslots with the restriction that an AMR call on a normal timeslot has to handover to EFR/FR on the extended range timeslot. Handovers in the opposite direction can handover to AMR.

GSM half rate

GSM half rate 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 and is considered a viable option for high-density areas. GSM half rate is introduced using current hardware components, or utilizing new hardware that further enhances the benefits of this feature. The new hardware is described in detail in Adaptive Multi-Rate (AMR) on page 1-11. The GDP and GDP2 boards are enhanced to support GSM HR, thus providing 30 and 60 channels of transcoding capability, respectively. As the current RXU shelf has only one E1 connection per transcoder slot, the GDP2 supports 30 channels when used in this configuration. The new RXU shelf (RXU3) and BSSC cabinet (BSSC3) are used to utilize the full capacity. The backhaul between the BTS and BSC is 8 kbit/s or 16 kbit/s. 8 kbit/s needs that the subrate (8K) switching is present at the BSC. The existing hardware only supports 16 kbit/s switching on the backhaul between the BSC and BTS. Therefore, when using existing switching hardware, each half rate equipped RTF must have an additional two 64 kbit/s timeslots equipped to fully utilize all 16 half rate channels. The existing hardware also supports only 16 kbit/s switching on the backhaul between the BSC and RXCDR, requiring 16 kbit/s per voice channel (as it does currently). The Double Kiloport Switch (DSW2) supports subrate switching capability down to 8 kbit/s (extended subrate switching mode), as well as double the number of ports (enhanced capacity mode) when used in the RXCDR. With 8 kbit/s switching between the BSC and BTS, a half rate voice stream is carried in an 8 kbit/s subchannel, rather than the 16 kbit/s subchannel required with KSWs. This eliminates the need for the two additional 64 kbit/s timeslots required per half rate capable RTF. As with AMR half rate, a GSM half rate call can fit within an 8 kbit/s timeslot (an Ater channel) on the terrestrial resource from the BSC to the RXCDR, rather than the 16 kbit/s timeslot required for full rate calls. If a percentage of the active calls are assumed to be half rate, then efficiency can be gained by reducing the number of terrestrial resources between the BSC and RXCDR. The DSW2 benefit of 8 kbit/s subrate switching allows this capability to be realized. Dynamic assignment of BSC to RXCDR channels is employed to maximize Ater channel usage. The BSC can assign an 8 kbit/s or 16 kbit/s channel as required, based upon the backhaul in use across the BSCBTS interface. This allows the user to equip fewer channels than previously possible, with the assumption that some calls are utilizing half rate backhaul. This dynamic allocation is an enhancement to the existing Auto Connect mode feature, referred to as Enhanced Auto Connect mode. Enhanced Auto Connect is applicable to both AMR and GSM half rate.

Extended range cells

GSM half rate is only supported on the normal range timeslots and not on extended range timeslots (it is envisaged that the C/I ratio in the extended range portion of an extended range cell does not support a half rate call).

68P02900W21-S 1-12 01 Feb 2007

System Information: BSS Equipment Planning

BSS features

LoCation Services (LCS)

LCS provides a set of capabilities that determine location estimates of mobile stations and makes that information available to location applications. Applications requesting location estimates from LCS can be located in the MS, the network, or external to the PLMN. LCS is not classified as a supplementary service and can be subscribed to without subscribing to a basic telecommunication service. LCS is applicable to any target MS, whether the MS supports LCS. However, there are restrictions on choice of positioning method or notification of a location request to the MS user when the LCS or individual positioning methods respectively are not supported by the MS. LCS utilizes one or more positioning mechanisms to determine the location of a mobile station. Positioning an MS involves two main steps: Signal measurements. Location estimate computation based on the measured signals. Mobile originating location request (MO-LR) Any location request from a client MS to the LCS server made over the GSM air interface. While an MO-LR could be used to request the location of another MS, its primary purpose is to obtain an estimate of the location of the client MS, either for the client MS itself or for another LCS client designated by the MS. Mobile terminating location request (MT-LR) Any location request from an LCS client where the client is treated as external to the PLMN to which the location request is made. Network induced location request (NI-LR) Any location request for a target MS from a client considered to be within any of the PLMN entities currently serving the target MS. In this case, the LCS client is also within the LCS server. Examples of a NI-LR include a location request needed for supplementary services, for emergency call origination and by O&M in a visited PLMN.

Location service requests are divided into three categories:

LCS architecture
The LCS architecture can be one of the following: NSS-based The Serving Mobile Location Centre (SMLC) is connected to an MSC instead of a BSC. The MSC acts as a relay point for LCS signaling between the SMLC and BSC. BSS-based The SMLC is connected to a BSC instead of an MSC. The LCS signaling between the SMLC and BSC goes directly between the two entities.

BSC Reset Management (BRM)

BSC Reset Management (BRM) provides the option for fast failover of the BSC, for certain types of equipment failure. This minimizes the BSS outage, reducing the downtime from 10 minutes to 20 minutes to less than two minutes for most occurrences.

68P02900W21-S 01 Feb 2007 1-13

BSS features

Chapter 1: Introduction to planning

Equip the BSC with a redundant secondary BSP GPROC3/GPROC3-2 to utilize this feature.

Advanced Speech Call Item (ASCI)

The Advanced Speech Call Item (ASCI) feature includes the enhanced Multi-Level Precedence and Preemption (eMLPP) feature.

Enhanced Multi-level Precedence and Pre-emption

With the enhanced Multi-level Precedence and Pre-emption (eMLPP) feature, operators can provide preferential services to special users with higher priority such as police and medical personnel during emergency situations and high priority subscribers. With the eMLPP feature, the following functions are supported: Pre-emption: The Motorola BSS supports resource pre-emption based on a full set of Ainterface priority levels and procedures as defined in 3GPP TS 48.008. Enhancements based on priority are also provided. Resources of lower priority calls can be pre-empted to allow higher priority calls to go through. Pre-emption is supported in the following procedures: o CS point-to-point call: - New call set-up. - External handovers. - Internal imperative handovers. - Call switchover where calls do not necessarily require to be terminated due to a single failure on the linkset between an RXCDRBSC or due to MSC indicated CIC changes. The following types of resource pre-emption are supported: o o o TCH Ater channel Queue block

Priority Protection of switchable PDTCH Resources. eMLPP priority support - BSS supports eMLPP priority between the MSC and MS.

VersaTRAU backhaul for EGPRS

VersaTRAU reduces EGPRS backhaul costs by taking advantage of statistical multiplexing. This is achieved when packing variable size radio blocks to be sent over PDTCHs on a carrier, into one large TRAU frame associated with the carrier. Analysis of the RF conditions of current GPRS networks and predictions for EGPRS indicate that the average maximum throughput per EGPRS TS does not use the entire DS0 (that is, reach MCS9). The following are some of the key features included with VersaTRAU: VersaTRAU allows the backhaul for an EGPRS capable carrier to be dynamically provisioned in terms of 64 kbit/s terrestrial timeslots (DS0s).

68P02900W21-S 1-14 01 Feb 2007

System Information: BSS Equipment Planning

BSS features

Statistics are provided to the operator to measure the backhaul utilization for an EGPRS capable carrier to detect whether the backhaul is under or over provisioned. Traffic from all PDTCHs on a carrier is packed efficiently into a Versachannel of one or more terrestrial timeslots associated with this carrier. Versachannel is defined as the portion of the backhaul associated with an RTF that is used to carry TRAU frames associated with the air timeslots configured as a PDTCH. New TRAU frame formats are introduced to carry the multiplexed data blocks over the Versachannel.

All EGPRS capable carriers use VersaTRAU frame formats on the backhaul after introduction of VersaTRAU. If half rate (GSM/AMR) is enabled on an EGPRS carrier, in order to maximize the backhaul utilization, the 16 kbit/s switching format for the half rate calls is not supported on the backhaul and 8 kbit/s switching (requiring DSWs) has to be used.

Quality of Service (QoS)

With the Quality of Service (QoS) feature, operators are able to enter into varying levels of Service Level agreements with end users that guarantee both different probabilities of access to the network and different throughputs once the network is accessed. Admission and retention control based Allocation/Retention priority (ARP), is provided for Interactive and Background traffic classes. QoS for conversational and streaming traffic classes is not supported, however, conversational and streaming traffic is allowed into the GPRS network and downgraded to Interactive class and is not subject to further downgrade or preemption. The QoS feature allows operators to charge premium rates for the highest quality of service classes and thus to focus the resources of their network to their revenue generating customers. The provision of focused QoS classes ensures that the subscribers receive the best possible service specific to the types of applications used and specific to the type of tariff selected.

QoS dimensioning
The two most significant factors that influence quality of a service are: Delay Throughput

In R99 and beyond, four traffic classes are defined to accommodate the need for different levels of these factors for different applications. These are: Conversational Streaming Interactive Background

The BSS has internally defined additional traffic classes created by grouping similar PFC characteristics. The internally defined traffic classes are: Short-Term Non-Negotiated Traffic (STNNT) Pre-Admission PFC (PAP) QoS disabled

68P02900W21-S 01 Feb 2007 1-15

BSS features

Chapter 1: Introduction to planning

As the specification for conversational and streaming is still evolving, the BSS is implementing differentiation of service among interactive and background traffic classes. Requests to create packet flows for streaming or conversational mode are treated as interactive traffic flows. Support for streaming or conversational traffic class at the BSS is limited in its scope, that is, streaming and conversational traffic classes get QoS of interactive traffic class when admitted. However, the BSS does not make any guarantees regarding sustaining applications using the streaming and conversational traffic classes.

QoS impacts on BSS

The QoS feature influence the following BSS entities: Gb interface PFM procedures over the Gb interface are defined in 48.018 as CREATE_BSS_PFC, MODIFY_BSS_PFC, DOWNLOAD_BSS_PFC, DELETE_BSS_PFC and their corresponding ACKs and NACKs. In addition, the support for optional PFI IE in UL_UNITDATA and DL_UNITDATA PDUs is also dictated by the support for PFM procedures. PDTCH planning The PDTCH formula in Chapter 3, Dual Transfer Mode has been updated to reflect the QoS design to allow QoS to reserve the appropriate amount of throughput per cell. The updated equations provide the cell with appropriate amount of throughput for QoS subscribers based on the input to the formulas. PDTCH assignment to PRP The formula for assigning PDTCHs to a PRP has been updated to allow subscribers with QoS to have the necessary throughput reserved at the PRP. The formulas use the user configurable parameters for MTBR for each Traffic Class and Coding Scheme usage to determine the maximum number of PDTCHs to assign to a PRP.

QoS2
{27703} The QoS2 builds on top of QoS. The key components of QoS2 implementation are as follows: Add support for Streaming Traffic class. Maximum bit-rate enforcement as per the QoS profile. Capacity is based on a less conservative budget to start (using user configurable initial coding scheme).

Support for Streaming Traffic Class allows the operator to specify a service requiring constraints on delay and jitter as well as minimum bit rate. Support for PFCs requesting streaming traffic class can be enabled/disabled using the streaming_enabled BSS parameter. If support for streaming traffic class is disabled, BSS tries to admit the streaming traffic classes as one of the matching interactive traffic classes (determined based on the MTBR settings, details defined in the GSR8 QoS implementation). Guaranteed Bit Rate as per the 3GPP specification is defined as the guaranteed number of bits delivered at an SAP within a period of time (if there is data to deliver), divided by the duration of the period. For the GPRS RAN, the guaranteed bit rate is defined as the bit rate at the LLC layer. QoS introduced the internal BSS concept of an MTBR (Minimum Throughput Budget Requirement) associated with each PFC. The Guaranteed Bit Rate for each PFC is an extension of this concept except that the GBR must be enforced as a true guarantee and not just a commitment. The MTBR is measured as the raw air throughput at the RLC/MAC layer whereas the GBR measurements exclude any RLC retransmissions.

68P02900W21-S 1-16 01 Feb 2007

System Information: BSS Equipment Planning

BSS features

Transfer Delay (definition as per 23.107) indicates maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a bearer service, where delay for an SDU is defined as the time from a request to transfer an SDU at one SAP to its delivery at the other SAP. Transfer delay of an arbitrary SDU is not meaningful for a bursty source (applicable only to real-time traffic classes streaming/conversational). In addition, the transfer delay for Radio Access Bearer can be smaller than the overall requested transfer delay, as transport through the core network uses a part of the acceptable delay. Transfer delay as all other attributes in the Aggregate BSS QoS profile is negotiable. QoS2 is based on the GSR8 implementation of QoS. All the PFCs for a given operator share the same TBF over the air interface to transfer data for the PFCs. GSR9 enhances the LLC scheduling within the TBF. The real-time service is prioritized appropriately over the non real-time services where necessary. However, at the RLC layer, all PFCs for the mobile still share the same pipe. GSR9 streaming support is limited to at most one active real-time PFC per user at any given time. Maximum Bit Rate enforcement allows the BSS to throttle the throughput of the user to the maximum bit rate stated in the QoS parameters (ABQP) even if there is capacity to provide the user a higher throughput. The main purpose of the maximum bit rate enforcement from an users perspective are to limit the delivered bitrate to the applications or external networks and to allow maximum required or permitted bitrate to be defined for applications able to operate with different rates. The maximum bitrate applies to all traffic classes. Streaming_enabled and qos_mbr_enabled parameters affect cell capacity. In addition, some other parameters influence user experience although there is no impact to capacity, which include stream_downgrade_enabled and mtbr_downgrade_enabled. For example, if stream_downgrade_enabled is disabled and the idle resource is not enough, RT service is rejected.

Increased Network Capacity (Huge BSC)

{28398} The optional feature, Increased Network Capacity enhances the network capacity and supports database capacity up to 8 MB. The network capacity is as follows: The Maximum number of carriers that a BSC supports increases from 512 to 750. The Maximum number of sites that a BSC supports increases from 100 to 140. The Maximum number of circuits that a BSC supports increases from 3200 to 4800. The maximum number of BSC-XCDR connectivity that a BSC supports increases from 27 to 42.

This feature has an impact on the collection and dispatch of the additional statistics due to the increased number of managed objects. The upload and collection of statistics to the OMC takes place at 30 minute or 60 minute intervals, and lasts for 20 minutes.

Improved Timeslot Sharing (ITS)

The Improved Timeslot Sharing feature supports EGPRS on DD CTU2 and retains no HW changes of CTU2, BSS SW, and HII FW allow each CTU2 to be able to switch rapidly between Double Density modulation (GMSK) and Single Density modulation (8PSK). The power output is not affected for GMSK and 8PSK. Thus, the EGPRS PDTCH can only be configured on Carrier A of DD CTU2 while the corresponding timeslots on the paired Carrier B have to be blanked out. Although the feature of ITS does not double the voice capacity per CTU2, compared with EGPRS on single Density Mode CTU2, it offers more channels to service voice users with EGPRS service in parallel.

68P02900W21-S 01 Feb 2007 1-17

BSS features

Chapter 1: Introduction to planning

Enhanced BSC capacity using DSW2

{22168} This feature expands (double) the TDM timeslots in the BSC from 1024 TSs to 2048 TSs in one switch cage using bank 0/1 extension mode. When this switch cage has one or more extension cages, the switch cage uses 1024 TSs (BANK0), and the other extension cages share the rest of the 1024 TSs (BANK1). When up to 4 switch cages are configured, the maximum capacity is 8192 x 64 kbit/s TSs. This allows the customer to equip more devices. For example, MSI, PSI, and so on, in multiple cages.

High Speed MTL

{28337} HSP MTL feature offers enhanced capacity and flexibility of MTL to support huge BSC configurations by increasing the capacity of MTL from 64k to 2M. The BSC supports High Speed MTL (HSP MTL) link utilization to a maximum of 20%. This feature utilizes and needs the GPROC3-2 (FR25739) hardware to increase the MTL capacity.

Addition of new BSC/PCU software (PXP) and hardware (PSI2) to increase GPRS capacity (ePCU)
{28351} The evolved PCU feature provides a migration path for operators wanting to expand existing GPRS capabilities. A new DPROC type called PXP is introduced. PXP combines the functionality of PICP and PRP into one board. U-DPROC2 is a new hardware type that takes over all the functions of a legacy DPROC board and has a new mode for high-capacity operations. U-DPROC2 hardware board is configured as a new PXP function that combines the functionality of the PICP and PRP into one board. PXP is connected with the PSI2 board in BSC through Ethernet link.

High bandwidth interconnect between BSC and PCU (PSI2)

{26740} The PSI2 card is introduced in GSR9. It connects the BSC to the PCU with Ethernet connectivity. The physical interface from the card is a 1000BASE-T over four pairs of copper wire. This connection can also be operated in 100BASE-TX mode of operation, utilizing two pairs of copper wire. The standard backplane connections is used, with a PBIB or PT43 board replacing the BIB or T43 board, respectively, at the top of the cabinet. The new interconnect board (PBIB or PT43) at the top of the BSC cabinet allows a single RJ45 Ethernet connection instead of two span lines for one of the supported MSI positions. This link is referred as the Ethernet Link unless it is required to specify 100BASE-TX or 1000BASE-T modes of operation.

68P02900W21-S 1-18 01 Feb 2007

System Information: BSS Equipment Planning

BSS features

Dual Transfer Mode

{23291} This optional feature supports the DTM mobiles (subset of class A) and can access packet and circuit services simultaneously. The DTM MS in a CS connection can add a PS session to it by making a DTM request. The DTM MS that is in a PS session can get a CS page or the operator can choose to make a CS call, in that event, the PS session is aborted by the MS. If the CS connection is established then the MS can add a PS session to the CS session to perform DTM.

DTM impacts on BSS

The DTM feature influences the following BSS entities: Radio resource management The DTM PS timeslots are converted from TCH. When a DTM MS in dedicated mode requests the timeslots for the PS session, some TCHs in the cell are converted into DTM PDCHs. The database parameter Max_DTM_TS defines the maximum of CS timeslots that can be converted to DTM PDCHs. The Max_DTM_TS planning impacts the provisions of circuit switched timeslots and switchable GPRS/EGPS timeslots. PDTCH planning Some timeslots per PRP are reserved for the PS sessions of DTM subscribers, which impact the PDTCH planning in PCU. GSL link planning Due to the impact of paging coordination and DTM signaling messages, the additional load on GSL is taken into consideration.

CTU2-D
{30828}

The CTU2-D is not currently part of GSR9, and will be delivered in a separate software load. With the introduction of CTU2D feature, the new CTU2D radios can support both SD and DD EDGE architectures, in addition to the various modes supported by the legacy CTU2 radios. According to the CTU2, Carrier A/B definitions and nomenclature also apply to CTU2D. The following are the different Edge modes that the CTU2D radio supports: CTU2D SD This mode is identical in operation to the existing CTU2 SD and is only included for reference. CTU2D PWR

68P02900W21-S 01 Feb 2007 1-19

BSS features

Chapter 1: Introduction to planning

This mode is also known as ITS Mode whereby the CTU2 and CTU2D operations are identical. Of the two carriers, if the TS on carrier A is supporting an EDGE TS, then the corresponding TS on carrier B is blanked, that is, not supporting anything. Carrier B TS is capable of supporting only TCH or GPRS PDs while the corresponding TS on carrier A does not have an EDGE TS. The maximum output power of both carriers whether in GMSK or 8PSK mode is 20W* as shown in Figure 1-2. Figure 1-2 CTU2D PWR

A B
CTU2D CAP

E E E E T T T T X X X X
T/G T/G T/G T/G

DD 20W CTU2D PWR / CTU2 ITS

Of the two carriers, carrier A is fully EDGE-capable, while carrier B supports GPRS/TCH. TS blanking is not required. The maximum output power of carrier A in 8PSK mode is 10W* and GMSK mode is 20W*. The maximum output power carrier B (GMSK only) is always 20W* as shown in Figure 1-3. Figure 1-3 CTU2D CAP

A
No E

E E E E E E E E
or T or G
T/G T/G T/G T/G T/G T/G T/G T/G

DD 10W CTU2D CAP

CTU2D ASYM Of the two carriers, carrier A is fully EDGE-capable, while carrier B supports EDGE on the DL and GMSK (EDGE) on the UL. The maximum output power of carrier A in 8PSK mode is 10W* and GMSK mode is 20W*. The maximum output power of carrier B in GMSK mode is 20W* Figure 1-4. Figure 1-4 CTU2D ASYM

The output powers listed are for 900 MHz frequency. For all other frequencies, the output power varies.

68P02900W21-S 1-20 01 Feb 2007

System Information: BSS Equipment Planning

BSS features

96 MSIs

The 96 MSI feature is not currently part of GSR9, and will be delivered in a separate software load. This feature expands the number of MSIs supported from 56 to 96 and allows for additional E1s between the BSC and the BTSs, RXCDR(s), and PCU. The impact on BSS is as follows: If 96 MSIs are equipped at a BSC (12 MSIs in each of 8 cages), only one PCU can be deployed to the BSC to keep the total number of MMS/MSIs in the entire BSS system limit. When the system is operating in single rate mode, some devices can be out of service until the fullenhanced capacity mode is re-enabled. The OML is important for the customer to control the BSC in OMC side. The current algorithm configures the MSI with the OML with priority in the database to ensure the availability of MSI in either single rate or enhanced capacity mode.

68P02900W21-S 01 Feb 2007 1-21

BSS planning overview

Chapter 1: Introduction to planning

BSS planning overview

Introduction
A brief overview of the planning process is provided in this section.

Background information
Before planning, the required information is categorized into three main areas: Traffic model and capacity calculations Category of service Site planning

Traffic model and capacity calculations

The following information is required to calculate the capacity required: Traffic information (Erlangs/BTS) over desired service area Average traffic per site Call duration Number of handovers per call Ratio of location updates to calls Ratio of total pages sent to time in seconds (pages per second) Ratio of intra-BSC handovers to all handovers LCS usage Number of TCHs half rate (AMR or GSM) usage Ratio of SDCCHs to TCHs Link utilization (for C7 MSC to BSS links) SMS utilization (both cell broadcast and point to point) Expected (applied and effective) GPRS load

eMLPP impact on BSS equipment and capacity calculations

With eMLPP feature, preferential service is provided for higher priority calls by pre-empting the resource from lower priority calls when the system is under congestion. When planning radio and terrestrial resources, the adequate resources require to be planned by treating all calls equal without considering preemption. That is, BSS planning focuses on providing planning steps and rules under normal traffic load without congestion, with certain capacity margin planned for traffic surge or congestion, such as link provisioning based on 25% or 35% or 40% signaling link utilization, or processor provisioning based on 70% utilization.

68P02900W21-S 1-22 01 Feb 2007

System Information: BSS Equipment Planning

BSS planning overview

Therefore, BSS equipment planning disregards the eMLPP feature, and capacity or equipment calculation formula is not updated for this feature.

Category of service
Category of service area urban, suburban, or rural: o o o Cell configuration in each category, sector against omni. Frequency re-use scheme to meet traffic and C/I requirements. Number of RF carriers in cell/sector to support traffic.

Grade of service of the trunks between the MSC/BSC, that is, Erlang B at 1%. Grade of service of the traffic channels (TCH) between the MS and BTS, that is, Erlang B at 2%. Cell grid plan, a function of the following: o o o Desired grade of service or acceptable level of blockage. Typical cell radio link budget. Results of field tests.

Site planning
The following information is required to plan each site. Location of the BSC and BTSs. Local restrictions affecting antenna heights, equipment shelters, and so on. Number of sites required (RF planning issues). Re-use plan, (frequency planning) omni or sector: o o o Spectrum availability. Number of RF carrier frequencies available. Antenna type(s) and gain specification.

Diversity requirement. Diversity doubles the number of Rx antennas and associated equipment. Redundancy level requirements (determined for each item). Supply voltage.

Planning methodology
A GSM digital cellular system consists of several BSSs. The planning cycle begins with defining the BSS cell, followed by the BTS(s), BSC(s), and the RXCDR(s). Planning a BSS involves the following: Select the configuration, omni or sectored and the frequency re-use scheme that satisfies traffic, interference and growth requirements. Plan all the BTS sites as follows: o Use an appropriate RF planning tool to determine the geographical location of sites and the RF parameters of the selected terrain.

68P02900W21-S 01 Feb 2007 1-23

BSS planning overview

Chapter 1: Introduction to planning

o o o

Determine which equipment affecting features are required at each site. For example, diversity or frequency hopping. Plan the RF equipment portion and cabinets for each BTS site. Plan the digital equipment portion for each BTS site. Sites for each BSC. Which BTSs are connected to which BSC How the BTSs are connected to the BSCs. Traffic requirements for the BSCs. Digital equipment for each BSC site. Shelf, cabinets, and power requirements for each BSC.

Plan the BSCs after the BTS sites are configured and determine the following: o o o o o o

Plan the remote transcoder (RXCDR) requirements and, if required, the subsequent hardware implementation. Plan the Packet Control Unit (PCU) for the desired packet data capacity for the system.

68P02900W21-S 1-24 01 Feb 2007

System Information: BSS Equipment Planning

Acronyms

Acronyms
Acronym list
Table 1-2 contains a list of acronyms as used in this manual. Table 1-2 Acronym list Acronym AGCH A-GPS ALM AMR ARFCN ARP ARQ ASCI ATB BBH BCCH BCS BCU BE BER BG BHCA BIB BLER BRM BSC BSP BSS BSSC(n) BSU BTC Meaning Access grant channel Assisted GPS Advanced load management Adaptive multi-rate Absolute radio frequency channel number Allocation / retention priority Automatic repeat request Advanced speech call item All trunks busy Baseband hopping Broadcast control channel Block check sequence Base controller unit Best effort Bit error rate Back ground Busy hour call attempts Balanced line interface board Block error rate BSC reset management Base station controller Base station processor Base station system Base station system control (n = 2 or 3) Base station unit Bus termination card Continued

68P02900W21-S 01 Feb 2007 1-25

Acronyms

Chapter 1: Introduction to planning

Table 1-2 Acronym list (Continued) Acronym BTF BTP BTS BVC(I) C/I CBC CBF CBL CCB CCCH CDMA CIC CIR CLKX CN CP cPCI CPU CRC CS(n) CSFP CTU CTU2 CTU2D PWR CTU2D CAP CTU2D ASYM DARBC dB DCF DDF DCS DECT Meaning Base transceiver function Base transceiver processor Base transceiver station BSSGP virtual circuit (identifier) Carrier to interference ratio Cell broadcast centre Combining bandpass filter Cell broadcast centre link Cavity combining block Common control channel Code division multiple access Circuit identity code Committed information rate Clock extender Core network Call processing Compact PCI Central processing unit Cyclic redundancy check Channel coding scheme (number) Code storage facility processor Compact transceiver unit Compact transceiver unit 2 CTU2D double density power mode CTU2D double density capacity mode CTU2D double density asymmetric mode Dynamic allocation of RXCDR to BSC circuits Decibel Duplexed combining bandpass filter Dual stage duplexed combining filter Digital cellular system Digital enhanced cordless telephony Continued

68P02900W21-S 1-26 01 Feb 2007

System Information: BSS Equipment Planning

Acronyms

Table 1-2 Acronym list (Continued) Acronym DD DDM DHU DL DLCI DLNB DPROC (D)RAM DRCU DRI DRIM DRX DSP DSW2 DSWX DTE DTRX DTX DUP DYNET e E1 EAC EDGE EDMAC EFR EGDP EGPRS EGSM ELM E-OTD ePCU Meaning Double Density Dual density mode Dual hybrid combiner unit Downlink Data link connection identifier Dual low noise block Data processor (Dynamic) random access memory Diversity radio control unit Digital radio interface Digital radio interface module Discontinuous reception Digital signal processor Double kiloport switch Double kiloport switch (extender) Data terminal equipment Dual transceiver module Discontinuous transmission Duplexer Dynamic network Erlang 32 channel 2.048 Mbps span line Enhanced auto-connect Enhanced data rates for global evolution Enhanced Dynamic Allocation Medium Access Mode Enhanced full rate Enhanced generic digital processor Enhanced-GPRS Enhanced global system for mobile communication EGSM layer management Enhanced observed time difference Evolved PCU (Enhanced PCU) Continued

68P02900W21-S 01 Feb 2007 1-27

Acronyms

Chapter 1: Introduction to planning

Table 1-2 Acronym list (Continued) Acronym eMLPP FACCH FEC FHI FM FMUX FN FOX fr FR FTD FTP GBL (or GbL) GCLK GDP(2) GDS GGSN GMLC GMM GMSK GOS GPROC(n) GPRS GPS GSM GSM half rate GSN GSR HCOMB HCU HDLC HDSL Meaning Enhanced multi-level precedence and pre-emption Fast access control channel Forward error correction Frequency hopping index Fault management Fiber optic multiplexer (Horizonmacro) Frame number Fiber optic multiplexer (M-Cell) Full rate referring to the channel rate Frame relay, or full rate referring to the speech codec File transit delay File transfer protocol Gb link Generic clock Generic digital processor (2) GPRS data stream Gateway GPRS support node Gateway mobile location centre GPRS mobility management Gaussian minimum shift keying Grade of service Generic processor (n = 1, 2 or 3) General packet radio system Global positioning by satellite Global system for mobile communication GSM half rate (GSM half rate speech version 1) feature GPRS support node GSM software release Hybrid combiner Hybrid combining unit High level data link control High bit rate digital subscriber line Continued

68P02900W21-S 1-28 01 Feb 2007

System Information: BSS Equipment Planning

Acronyms

Table 1-2 Acronym list (Continued) Acronym HIISC HPM hr HR HSC HSNI IADU IMRM IMSI INS IP IPL IR ITS ISDN ISI ISP KSW(X) LA LAC LAN(X) LAPB LAPD LCF LCS LLC LMTL LMU LNA MA(IO) MAC MAP Meaning Horizon II macro site controller High power mode Half rate (AMR or GSM), referring to the channel rate Half rate (AMR or GSM), referring to the speech codec Hot swap controller Hopping sequence number interactive Integrated antenna distribution unit Intelligent multi-layer resource management International mobile subscriber identity In service Internet protocol Initial program load Incremental redundancy Improved Timeslot Sharing Integrated services digital network Inter symbol interference Internet service provider Kiloport switch (extender) Link adaptation Location area code Local area network (extender) Link access protocol balanced Link access protocol data Link control function Location services Logical link control Location service MTL Location measurement unit Low noise amplifier Mobile allocation (index offset) Medium access control Mobile application part Continued

68P02900W21-S 01 Feb 2007 1-29

Acronyms

Chapter 1: Introduction to planning

Table 1-2 Acronym list (Continued) Acronym MBR MCAP MCU MCUF MIB MLC MMI MPROC MS MSC MSI (-2) MTBR MTL MTP NCH NE NIU NPM NSE (I) NSP NSS NSVC (I) NTP NVM O&M OLM OMC-R OMF OML OOS OPL PACCH Meaning Maximum bit rate Motorola cellular advanced processor bus Main control unit Main control unit with dual FMUX Management information base Mobile location centre Man machine interface Master processor Mobile station Mobile switching centre Multiple serial interface (2) Minimum throughput budget requirement MTP transport layer link Message transfer part Notification channel Network element Network interface unit Normal power mode Network service entity (identifier) Network support program Network subsystem Network service layer virtual circuit (identifier) Network time protocol Non volatile memory Operations and maintenance Off line MIB Operations and maintenance centre radio Operations and maintenance function Operations and maintenance link Out of service Optimization link Packet associated control channel Continued

68P02900W21-S 1-30 01 Feb 2007

System Information: BSS Equipment Planning

Acronyms

Table 1-2 Acronym list (Continued) Acronym PAGCH PAP PAR PBCCH PBIB PCCCH PCH PCI PCM PCMCIA PCR PCS PCU PDCCH PDN PDP PDTCH PDU PFC PFM PICP PIX PLMN PMC PNCH PPCH PPP PRACH PSK PSM PSTN PSU Meaning Packet access grant channel Pre-admission PFC Peak to average ratio Packet broadcast control channel Packet BIB Packet common control channel Paging channel Peripheral component interconnect Pulse code modulation Personal computer memory card international association Preventive cyclic retransmission Personal communication system Packet control unit Packet dedicated control channel Packet data network Packet data protocol Packet data traffic channel Protocol data unit Packet flow context Packet flow management Packet interface control processor Parallel interface extender Public land mobile network PCI mezzanine card Packet notification channel Packet paging channel Point to point protocol Packet random access channel Phase shift keying Power supply module Public switched telephone network Power supply unit Continued

68P02900W21-S 01 Feb 2007 1-31

Acronyms

Chapter 1: Introduction to planning

Table 1-2 Acronym list (Continued) Acronym PT43 PTCCH/D PTCCH/U PTP PVC PXP QOS (or QoS) RACH RAM RAN RAT RAU RDB RF RLC ROM RRI RSL RTD RTF RX (or Rx) RXCDR RXU SACCH SB SCC SCCP SCH SCM SCU SD SDCCH Meaning Packet T43 Packet timing advance control channel / downlink Packet timing advance control channel / uplink Point to point Permanent virtual circuit Processor with PRP and PICP function Quality of service Random access channel Random access memory Radio access network Radio access technology Routing area update Requirements database Radio frequency Radio link control Read only memory Radio refractive index Radio signaling link RLC transit delay Radio transceiver function Receive Remote transcoder Remote transcoder unit Slow access control channel Stealing bit Serial channel controller SS7 signaling connection control part Synchronization channel Status control manager Slim channel unit Single Density Stand alone dedicated control channel Continued

68P02900W21-S 1-32 01 Feb 2007

System Information: BSS Equipment Planning

Acronyms

Table 1-2 Acronym list (Continued) Acronym SDM SFH SGSN SID SLS SM SMLC SMS SNDCP SS7 STNNT STP SURF SURF2 TBF TCCH TCH TCP TCU TDM TDMA TMSI TOA TRAU TS TSW TX (or Tx) U-DPROC2 UE UL UMTS USF Meaning Single density mode Synthesizer frequency hopping Serving GPRS support node Silence descriptor Signaling link selection Session management Serving mobile location centre Short message service Sub network dependent convergence protocol CCITT signaling system number 7 Short-term non-negotiated traffic Shielded twisted pair Sectorized universal receiver front end (Horizonmacro) Sectorized universal receiver front end 2 (Horizon II macro) Temporary block flow Timing access control channel Traffic channel Transmission control protocol Transceiver control unit Time division multiplexing Time division multiple access Temporary mobile subscriber identity Time of arrival Transcoder rate adaptation unit Timeslot Timeslot switch Transmit Universal DPROC2 User equipment Uplink Universal mobile telecommunication system Uplink state flag Continued

68P02900W21-S 01 Feb 2007 1-33

Acronyms

Chapter 1: Introduction to planning

Table 1-2 Acronym list (Continued) Acronym UTP UTRAN VersaTRAU VGC VGCS WAN WAP XBL XCDR XMUX Meaning Unshielded twisted pair UMTS radio access network Versatile transcoder rate adaptation unit Voice group call Voice group call service Wide area network Wireless access protocol Transcoder to BSS link Transcoder board Expansion multiplexer (Horizon II macro)

68P02900W21-S 1-34 01 Feb 2007

Chapter 2 Transmission systems

This chapter contains possible logical interconnections and descriptions of BSS interconnections. The following topics are described: BSS interfaces Interconnecting the BSC and BTSs Network topology Managed HDSL on micro BTSs

68P02900W21-S 01 Feb 2007 2-1

BSS interfaces

Chapter 2: Transmission systems

BSS interfaces
Introduction
Figure 2-1 and Table 2-1 indicate the type of interface, rates, and transmission systems used to convey information around the various parts of the BSS system. Figure 2-1 BSS interfaces

OMC-R

OML

X.25 (LAPB)

Gb OPTION B

MSC
Air interface Abis interface

MS

(LAPDm)

BTS
RSL (LAPD)

BSC

A interface MTL (C7), XBL (LAPD) OML (X.25)

RXCDR SGSN

GDS Gb OPTION A Gb OPTION C

PCU
CBL X.25 (LAPB)

CBC

68P02900W21-S 2-2 01 Feb 2007

System Information: BSS Equipment Planning

BSS interfaces

Table 2-1 BSS interface Interface Air From/To MS-BTS Signaling by RACH, SDCCH, SACCH, FACCH E1links Abis (Mobis) A A BTS - BSC BSS - MSC RXCDR BSC MSC - OMCR MSC - CBC Gb GDS PCU - SGSN PCU - BSC RSL MTL (OML, CBL) XBL OML (X.25) CBL (X.25) GBL GSL 16/64 kbit/s 64 kbit/s or 2048 kbit/s* 16/64 kbit/s 64 kbit/s 64 kbit/s E1 64 kbit/s LAPD C7 LAPD LAPB LAPB Frame Relay LAPD Rate Using LAPDm

* In GSR9, Motorola BSS supports 2048 kbit/s high speed signaling link (HSP MTL), that is, a whole span of E1 is one signaling link.

68P02900W21-S 01 Feb 2007 2-3

Interconnecting the BSC and BTSs

Chapter 2: Transmission systems

Interconnecting the BSC and BTSs

Introduction
Network topology is specified in terms of the path(s) between the BSC and the BTS sites. A path is determined by E1 circuits, and possible intervening BTS sites are used to provide the connection. Transcoding is performed at the BSC or RXCDR.

Interconnection rules
The following rules must be observed while interconnecting a BSC and BTSs: The BSC shares MSI boards between BTSs. When there are two or more E1 circuits, at least two MSIs are recommended for redundancy. A minimum of one MSI is required at each BTS. The maximum number of active carrier units is determined by available E1 circuit capacity. Typically, a carrier unit needs two 64 kbit/s timeslots on an E1 circuit. An RTF is configured as half rate capable, which means it can support AMR half rate and/or GSM half rate. Once an RTF is configured as AMR half rate capable, and if AMR half rate is enabled, the 7.95 kbit/s half rate codec mode is included in the Half Rate Active Codec Set or (for either AMR half rate or GSM half rate) 8 kbit/s subrate switching is not available. For example, if 16kbit/s is used for the backhaul, then the carrier unit assigned to that RTF needs four 64 kbit/s timeslots on the E1 circuit (Refer to the NOTE). In a redundant connection, each carrier unit needs two 64 kbit/s timeslots on two different E1 circuits. Four 64 kbit/s timeslots are required if the half rate exception case applies. The AMR half rate exception case is defined as- A carrier which is assigned an RTF configured as (AMR or GSM) half rate capable, and 8 kbit/s subrate switching is not available (for example, 16 kbit/s is used for the backhaul), or (for AMR) the 7.95 kbit/s half rate codec mode is included in the Half Rate Active Codec Set. The Half Rate Active Codec Set is AMR specific and is configured on a per cell basis. At the BSC, one E1 circuit is required to connect to a daisy chain. If the connection is a closed loop daisy chain, two E1 circuits are required. To provide redundancy, the two E1 circuits must be terminated on different MSIs. In a closed loop daisy chain, the primary RSLs for all BTS sites are routed in the same direction with the secondary RSLs routed in the opposite direction. The primary RSL at each BTS site in the daisy chain is always equipped on the multiple serial interface link (MMS) equipped in CAGE 15, slot 16, port A. The secondary RSL at each BTS site is equipped on the MMS equipped in either shelf 15, slot 16, port B, or shelf 15, slot 14, port A, or shelf 14, slot 16, port A.

68P02900W21-S 2-4 01 Feb 2007

System Information: BSS Equipment Planning

Interconnecting the BSC and BTSs

When discussing the BSC or RXCDR, cage is a legacy term used in BSS commands that has been replaced by shelf in this manual. That is, cage and shelf mean the same thing. Additional backhaul bandwidth is required to support GPRS traffic using CS3/CS4 coding schemes. Each timeslot, on a CS3/CS4 capable carrier, needs 32 kbit/s for a total of four 64 kbit/s timeslots on the E1 circuit, irrespective of the speech coding. Additional backhaul bandwidth is required to support EGPRS traffic using MCS1-MCS9 coding schemes. Each non-signaling timeslot, shares the Versachannel backhaul associated with the particular carrier. Backhaul is provisioned based on expected EGPRS usage and recommendation in Table 8-1 of Chapter 8. Versachannel is defined as the portion of the RTF backhaul that is used to carry the data for the air timeslots configured as PDTCHs, at any given time. Reconfigure the InCell BTS to have integral sectors in the cabinet. Install M-Cell cabinets to serve the remaining sectors. Daisy chain the M-Cell E1 links to the BSC.

The following rules must be observed while interconnecting InCell and M-Cell equipment:

68P02900W21-S 01 Feb 2007 2-5

Network topology

Chapter 2: Transmission systems

Network topology
Introduction
The operator can specify the traffic that is to use a specific path. A direct route between any two adjacent sites in a network can consist of one or more E1 circuits. Figure 2-2 shows a possible network topology. Figure 2-2 Possible network topology
BSC

BTS 10

BTS 1

BTS 5

BTS 2

BTS 6

BTS 11

BTS 3

BTS 7

BTS 9

BTS 4

BTS 8

Each BTS site in the network must obey the following maximum restrictions: Six serial interfaces supported at a Horizon II macro BTS. Six serial interfaces supported at a Horizonmacro BTS. Two serial interfaces supported at a Horizonmicro2 / Horizoncompact2 BTS. Six serial interfaces supported at an M-Cell6 BTS. Four serial interfaces supported at an M-Cell2 BTS. Two serial interfaces supported at an M-Cellcity / M-Cellcity+ BTS. Ten BTS(s) in a path, including the terminating BTS for E1 circuit. Six RSL signaling links per Horizon II macro BTS site (maximum of four per path). Six RSL signaling links per Horizonmacro or M-Cell BTS site (maximum of two per path).

An alternative path is reserved for voice/data traffic in the case of path failure. This is known as a redundant path, and is used to provide voice/data redundancy, that is, loop redundancy. The presence of multiple paths does not imply redundancy. Each signaling link has a single path. When redundant paths exist, redundant signal links are required, and the signaling is load shared over these links. In case of a path failure, the traffic can be rerouted, but the signaling links go out of service, and the load is carried on the redundant links.

68P02900W21-S 2-6 01 Feb 2007

System Information: BSS Equipment Planning

Network topology

Star connection
A star connection is defined by installing E1 circuits between each BTS site and the BSC, as shown in Figure 2-3. Figure 2-3 Star connection
BTS 3 BTS 2 BTS 4

BTS 1

BSC

BTS 5

MSC BTS 7 BTS 9 BTS 8

A star connection requires more MSI cards at the BSC than daisy chaining, for the same number of BTS sites. The star connection allows for a greater number of carrier units per BTS site. An E1 circuit provides for one signaling link, along with either: Fifteen GSM voice carriers Fifteen CS1/CS2 GPRS carriers Seven CS3/CS4 carriers Three or more EGPRS carriers (depending on the backhaul configured for each of these carriers if VersaTRAU is enabled) or Some proportionate mix of GSM, GPRS and EGPRS

The number of carriers on an E1 circuit is reduced by 1 for each carrier to which the half rate exception case applies. The half rate exception case is defined in the section Interconnecting the BSC and BTSs.

68P02900W21-S 01 Feb 2007 2-7

Network topology

Chapter 2: Transmission systems

Daisy chain connection

Daisy chaining multiple BTS sites together can better utilize the 64 kbit/s timeslots of one E1 circuit from the BSC. Daisy chaining the sites together provides for the efficient utilization of the E1 circuit and interconnects smaller sites back to the BSC. The daisy chain can be open ended or closed looped back to the BSC as shown in Figure 2-4. Figure 2-4 Closed loop and open ended daisy chains
BTS 3 BTS 2
DAISY CHAIN CLOSED LOOP

BTS 4 BTS 10

BRANCH OF THE DAISY CHAIN

BTS 1

BTS 6

BSC

BTS 5

MSC
DAISY CHAIN CLOSED LOOP

BTS 11 BTS 7
SINGLE MEMBER DAISY CHAIN, A STAR

BTS 9

BTS 8

The closed loop version provides for redundancy while the open ended version does not.

Longer daisy chains (five or more sites) cannot meet the suggested round-trip delay.

Daisy chain planning

The introduction of multiple E1 circuits and branches increases the complexity of the network topology. Since the network can contain multiple E1 circuits, branches, multiple paths over the same E1 circuit, and closed loop interconnections, each E1 circuit is planned individually.

Simple daisy chain

A daisy chain without branches and with a single E1 circuit between each of the BTSs is referred to as a simple daisy chain. The maximum capacity supported in this connection is limited by the capacity of the connection between the BSC and the first BTS in the chain. A simple daisy chain is shown in Figure 2-5.

68P02900W21-S 2-8 01 Feb 2007

System Information: BSS Equipment Planning

Network topology

Figure 2-5 Simple daisy chain

Tx

Rx

Tx

Rx

BSC
Rx Tx

BTS 1
Rx Tx Rx

BTS 2
Tx

Tx

Rx Tx

Rx

Tx

Rx

USED IN CLOSED LOOP CONNECTION ONLY

BTS 3
Rx Tx

BTS 4
Rx Tx

BTS X

The capacity of a closed loop single E1 circuit daisy chain is the same as that of a daisy chain. The closed loop daisy chain has redundant signaling links for each BTS, although they transverse the chain in opposite directions back to the BSC. The following equation determines the number of E1s required for a daisy chain:

N BSC BTS

nE GPRS RTF_DS0_COUNTi + (nC GPRS 4 ) + (nTGPRS 2 ) + TAHRE 4 + b i =0 = 31

Is NBSC - BTS nEGPRS nCGPRS RTF_DS0_ COUNTi nTAHRE b Minimum number of E1 links required (rounded up to an integer). Total number of carriers in the daisy chain with EGPRS enabled. Total number of carriers in the daisy chain with GPRS CS3 and CS4 enabled. Value of rtf_ds0_count for the RTF. Total number of GSM voice only carriers in the daisy chain where the half rate exception applies. Number of BTS sites in the chain.

Where

Example
Consider a daisy chain with 3 BTSs, each with 1 GSM voice carrier, 1 CS3/4 enabled carrier and 1 EGPRS enabled carrier for which the half rate exception case does not apply. The number of E1s required (assuming VersaTRAU is restricted - RTF_DS0_COUNT = 8 for each EGPRS RTF and all EGPRS RTFs are non-BCCH) is shown:

[(3 8) + (3 4) + (3 2) + (0 4) + 3]= 1.45E1s

31
Two E1s are required to support daisy chaining between the BTSs and the BSC.

68P02900W21-S 01 Feb 2007 2-9

Network topology

Chapter 2: Transmission systems

Daisy chain with branch BTS site

The addition of a branch BTS site (BTS Y), as shown in Figure 2-6, affects the capacity of the links between the BSC and the site from which the branch originates, as these are used for the path to the branched site. Figure 2-6 Daisy chain with branch

Tx

Rx

Tx

Rx

BSC
Rx Tx

BTS 1
Rx Tx Rx

BTS 2
Tx

Tx

Rx Tx

Rx

Tx

Rx

BTS 3
Rx Tx

BTS 4
Rx Tx

BTS X

USED IN CLOSED LOOP CONNECTION ONLY

Rx

BTS Y
Tx

A branch can have multiple BTS sites on it. A branch can be closed, in which case there are redundant signaling links on different E1 circuits. In a closed loop, which needs redundant signaling links for each BTS site, with an open branch, the E1 circuit to the branch needs to carry redundant signaling links.

Aggregate Abis
This is an option designed to allow greater flexibility while planning the network. It can also help reduce leasing costs of E1 links by optimizing link usage over the greatest distance between a BSC and a BTS. This is achieved by the introduction of third party multiplexer equipment enabled by Motorola software. This equipment allows timeslots on one E1 link to be multiplexed to more than one BTS. Therefore, if the situation arises where several single carrier BTSs each need their own dedicated E1 link, this greatly under utilizes each link capacity. If the geographical locations of the sites and the distances of the E1 links are advantageous, it is possible to initially send all the traffic channels for every site over one E1 link to the third party multiplexer and then distribute them over much shorter distances to the required sites. If the distance between the BSC and the multiplexer site is sufficiently large, this results in significant leasing cost savings compared to the original configuration. There are two diagrams illustrating the previous (Figure 2-7) and subsequent (Figure 2-8) scenarios.

68P02900W21-S 2-10 01 Feb 2007

System Information: BSS Equipment Planning

Network topology

Figure 2-7 Typical low capacity BSC/BTS configuration

BSC

5x64 kbit/s TIMESLOTS USED 26x64 kbit/s TIMESLOTS UNUSED

5x64 kbit/s TIMESLOTS USED 26x64 kbit/s TIMESLOTS UNUSED

BTS
TWO CARRIER ONE RSL 5x64 kbit/s TIMESLOTS USED 26x64 kbit/s TIMESLOTS UNUSED

BTS
TWO CARRIER ONE RSL

BTS
TWO CARRIER ONE RSL

Figure 2-8 Example using a switching network

BSC

MORE EFFICIENT USE OF LONGEST E1 LINK

20x64 kbit/s TIMESLOTS USED 11x64 kbit/s TIMESLOTS UNUSED

TWO CARRIER ONE RSL 5x64 kbit/s TIMESLOTS USED 26x64 kbit/s TIMESLOTS UNUSED E1 MULTIPLEXER 10x64 kbit/s TIMESLOTS USED 21x64 kbit/s TIMESLOTS UNUSED

BTS
TWO CARRIER ONE RSL

BTS

5x64 kbit/s TIMESLOTS USED 26x64 kbit/s TIMESLOTS UNUSED

5x64 kbit/s TIMESLOTS USED 26x64 kbit/s TIMESLOTS UNUSED

BTS
TWO CARRIER ONE RSL

BTS
TWO CARRIER ONE RSL

Another advantage of introducing the multiplexer is the improvement in the timeslot mapping onto the Abis interface.

68P02900W21-S 01 Feb 2007 2-11

Network topology

Chapter 2: Transmission systems

Currently they are allocated from timeslot 1 upwards for RSLs and timeslot 31 downwards for RTF traffic channels. Most link providers lease timeslots in contiguous blocks (that is, there are no gaps between timeslots). Under the existing timeslot allocation scheme this often means leasing a whole E1 link for a few timeslots. There is a new algorithm for allocating timeslots on the Abis interface. This is only used on the links that are directly connected to the new aggregate service; the existing algorithm for allocating timeslots is used on the other links. The new software allocates timeslots from timeslot 1 upwards. The RSLs are allocated first and the RTF timeslots next, with each site being equipped consecutively, thus allowing contiguous blocks of timeslots to be leased. It is important that the sites are equipped in the order that they are presented. Also, RSLs must be equipped first on a per site basis to coincide with the default timeslots for software downloads to the BTSs. Figure 2-9 is an example of timeslot allocation in a network using an aggregate service, with links to the aggregate service and links bypassing it. Figure 2-9 Timeslot allocation using new and old algorithms
NEW ALGORITHM 1 2 3 4 5 RSL1 RTF1 RTF1 RTF2 RTF2 6 7 8 9 10 11 12 13 14 15 RSL2 RTF3 RTF3 RTF4 RTF4 RSL3 RTF5 RTF5 RTF6 RTF6 16 17 18 19 20 RSL4 RTF7 RTF7 RTF8 RTF8 ORIGINAL ALGORITHM 13 13 02 92 8 RSL3 RTF5 RTF5 RTF6 RTF6

BSC
ALLOCATION UNAFFECTED

ALLOCATION AFFECTED NEW ALGORITHM 1 2 3 4 5 RSL3 RTF5 RTF5 RTF6 RTF6 6 7 8 9 10 RSL4 RTF7 RTF7 RTF8 RTF8

ALLOCATION AFFECTED

BTS 1
TWO CARRIER ONE RSL 1 2 3 4 5 RSL1 RTF1 RTF1 RTF2 RTF2

E1 MULTIPLEXER ALLOCATION AFFECTED

BTS 3
ORIGINAL ALGORITHM

NEW ALGORITHM 1 2 3 4 5 RSL2 RTF3 RTF3 RTF4 RTF4 ALLOCATION AFFECTED

NEW ALGORITHM

13 13 02 92 8

RSL4 RTF7 RTF7 RTF8 RTF8

ALLOCATION UNAFFECTED

BTS 2

BTS 4

Similar problems are encountered while equipping redundant RSL devices onto paths containing aggregate services. The new method of allocating timeslots when connecting to an aggregate service is from timeslot 1 upwards, so there is no way of reserving the default download RSL timeslot. This gives rise to a situation where the default RSL timeslot is already allocated to another device, for example RTF. To avoid this situation, the primary and redundant RSLs can be equipped first (in an order that results in the correct allocation of default RSL timeslots), or reserve the default download RSL timeslot so that it is correctly allocated when the primary or redundant RSL is equipped. If the site needs to be expanded in the future to preserve blocks of contiguous timeslots on the links, it is possible to reserve the timeslots needed for the expansion so that they can be made free in the future.

68P02900W21-S 2-12 01 Feb 2007

System Information: BSS Equipment Planning

Network topology

Alarm reporting
This feature has an impact on the alarm reporting for the E1 links. If the link is connected to a third party switching network and is taken out of service, the BTS reports the local alarm, but the remote alarm only goes to the third party aggregate service supporting the E1 link. A situation may arise where the internal links within the E1 switching network fail, causing the RSL to go out of service with no link alarms generated by GSM network entities (BTS, BSC). In these cases, it is the responsibility of the third party aggregate service provider to inform the users of the link outage. The only indication of failure is the RSL state change to out of service. Figure 2-10 shows a possible network configuration using several switching networks. Figure 2-10 Alternative network configuration with E1 switching network
BSC

E1 MULTIPLEXER

E1 MULTIPLEXER

BTS

BTS

BTS

BTS

BTS

BTS

BTS

BTS

E1 MULTIPLEXER

E1 MULTIPLEXER

BTS

BTS

BTS

BTS

Restrictions/limitations
The ability to nail path timeslots along a link containing an E1 switching network is supported. The operator is able to reserve, nail, and free timeslots. The maximum number of sites within a path is ten for E1 networks. Even though it is a pseudo site, the aggregate service is counted as a site in the path. Hence, the number of BTSs that can be present in a path is reduced from ten to nine. GCLK synchronization functions, but any BTS sites connected downlink from a switching network synchronizes to it and not to the uplink GSM network entity (BTS, BSC).

68P02900W21-S 01 Feb 2007 2-13

Network topology

Chapter 2: Transmission systems

RTF path fault containment

Each transceiver at a BTS needs a receive/transmit function to be enabled which notifies the transceiver about various operating parameters which can be used. These include the ARFCN, type of carrier, and primary/secondary path, among others. The path is of utmost importance. An RTF can be assigned different paths. The path is the route which the two (or four for the half rate exception case) 64 kbit/s timeslots, assigned to the transceiver from the E1 link, take to get to and from the BTS/BSC. Each RTF can be assigned a different path for its two (or four) timeslots, including RTFs that are in the same cell. One path is designated as the primary, the other as the secondary. In the event of primary path failure, the RTF selects the secondary path, and the carrier remains in call processing. If all the paths to one RTF fail, the entire cell is taken out of call processing, regardless of whether there are other transceivers/RTFs with serviceable paths in the same cell. This allows the cell to remain in call processing if all paths to one RTF fail, as described in the previous paragraphs. Any call in progress on the failed path is handed over to the remaining RTFs in the same cell, if there are available timeslots. If timeslots are unavailable, the call is released. In addition, the timeslots on the transceiver of the failed path are barred from traffic until the path is re-established, but any SDCCHs on the carrier remain active. If all paths to all RTFs in an active cell have failed and there is still an active RSL, then the cell is barred from traffic.

Advantages
The customer can save on timeslot usage by using this feature, and removing any redundant paths that are normally equipped to manage path failure. Figure 2-11 shows the conventional redundant set-up, which needs four extra timeslots to provide for redundant paths. Figure 2-12 shows the alternative configuration, where if one RTF path fails, call processing continues through the other path, although with reduced capacity. This configuration only needs four timeslots instead of eight, as required for Figure 2-11.

Double the number of timeslots required for RTFs to which the half rate exception case applies. The customer has to weigh up the cost saving advantages of the alternative configuration against the reduced capacity in the event of failure of an RTF path.

68P02900W21-S 2-14 01 Feb 2007

System Information: BSS Equipment Planning

Network topology

Figure 2-11 A configuration with a BTS equipped with two redundant RTFs
BSC
RTF1 EQUIPPED ON PATH 1 (2 TIMESLOTS) RTF1 EQUIPPED ON PATH 2 (2 TIMESLOTS)

BTS 3

BTS 1

RTF2 EQUIPPED ON PATH 1 (2 TIMESLOTS)

RTF2 EQUIPPED ON PATH 2 (2 TIMESLOTS)

BTS 2

Figure 2-12 A configuration with a BTS equipped with two non-redundant RTFs

BSC

RTF2 EQUIPPED ON PATH 1 (2 TIMESLOTS)

RTF1 EQUIPPED ON PATH 2 (2 TIMESLOTS)

BTS 3

BTS 1

BTS 2

68P02900W21-S 01 Feb 2007 2-15

Network topology

Chapter 2: Transmission systems

16 kbit/s RSL
The 16 kbit/s RSL reduces the transmission costs between the BSC and BTS (Abis interface) for single carrier sites in particular. Before the introduction of the 16 kbit/s RSL, a single carrier BTS required three E1 64 kbit/s timeslots; one for the 64 kbit/s RSL and two for the 16 kbit/s traffic channels. The two 64 kbit/s timeslots dedicated to the traffic channels can normally accommodate eight traffic channels. In the case of a single carrier site, it is not possible to use all eight traffic channels of the two 64 kbit/s timeslots. The reason being that, in the case of a single carrier site, the carrier is the BCCH carrier and the air interface timeslot 0 of the BCCH carrier is reserved for BCCH information. This information is generated at the BTS. The TSW at the BTS routes the traffic channels from the two specified timeslots on the Abis interface to the dedicated transceiver for transmission. The traffic channel on the Abis interface corresponding to the timeslot 0 on the air interface is unused and is available to carry the signaling traffic. Therefore one 16 kbit/s sub-channel remains unused on the Abis interface, which is a waste of resources. With the introduction of the 16 kbit/s RSL, it is possible to place it on this unused sub-channel because the RSL is not transmitting on the air interface. The advantage is that it frees up one 64 kbit/s timeslot on the Abis interface, reducing the requirement to serve a single carrier system to only two 64 kbit/s timeslots. This operates with Horizon BTSs using KSW switching. In a similar manner, when the single carrier is half rate capable and 16 kbit/s backhaul is used (8 kbit/s switching is unavailable or the 7.95 codec rate for AMR is included in the half rate active codec set for that cell), this feature reduces the number of required E1 64 kbit/s timeslots from five to four. (This is not shown in the table and figures.) Figure 2-13 (fully-equipped RTF) and Figure 2-14 (sub-equipped RTF) show the eight types of RTF which are possible using the previously described options. They are listed in Table 2-2. Table 2-2 RTF types Type 1 2 3 4 5 6 7 8 Options A fully equipped BCCH RTF with an associated 16 kbit/s RSL. A fully equipped BCCH RTF with no associated 16 kbit/s RSL. A fully equipped non-BCCH RTF with an associated 16 kbit/s RSL. A fully equipped non-BCCH RTF with no associated 16 kbit/s RSL. A sub-equipped BCCH RTF with an associated 16 kbit/s RSL. A sub-equipped BCCH RTF with no associated 16 kbit/s RSL. A sub-equipped non-BCCH RTF with an associated 16 kbit/s RSL. A sub-equipped non-BCCH RTF with no associated 16 kbit/s RSL.

68P02900W21-S 2-16 01 Feb 2007

System Information: BSS Equipment Planning

Network topology

Fully equipped RTF

Figure 2-13 Fully equipped RTF

FULLY EQUIPPED RTF

BCCH

NON-BCCH

16 kbit/s BTS only ASSOCIATED 16 kbit/s RSL NO ASSOCIATED 16 kbit/s RSL

16 kbit/s BTS only ASSOCIATED 16 kbit/s RSL NO ASSOCIATED 16 kbit/s RSL

Configuration Timeslot X Timeslot Y

KEY

16 kbit/s sub-channel unavailable for use. 16 kbit/s sub-channel used for 16 kbit/s RSL. 16 kbit/s sub-channel available for voice traffic.

68P02900W21-S 01 Feb 2007 2-17

Network topology

Chapter 2: Transmission systems

Sub-equipped RTF
Figure 2-14 Sub-equipped RTF

Planning constraints
The following RSL planning constraints apply: A BTS supports either 16 kbit/s RSLs or 64 kbit/s RSLs, not both. A BSC supports both 16 kbit/s and 64 kbit/s RSLs. A BSU based BTS supports up to six 16 kbit/s RSLs. Up to six 16 kbit/s RSLs are supported by Horizon II macro and Horizonmacro. Up to two 16 kbit/s RSLs are supported by Horizonmicro2 / Horizoncompact2. Up to six 16 kbit/s RSLs are supported by M-Cell6. Up to four 16 kbit/s RSLs are supported by M-Cell2. Up to two 16 kbit/s RSLs are supported by M-Cellmicro and M-Cellcity. The BTS and BSC support a mix of both fully equipped and sub-equipped RTFs. A ROM download is carried out over a 64 kbit/s RSL, even at a site designated as a 16 kbit/s RSL.

68P02900W21-S 2-18 01 Feb 2007

System Information: BSS Equipment Planning

Network topology

A CSFP download utilizes a 16 kbit/s RSL at a 16 kbit/s designated site. The 16 kbit/s RSL can only be configured on CCITT sub-channel 3 of a 64 kbit/s E1 timeslot for BSU based sites. An associated 16 kbit/s RSL is supported on redundant RTF paths where one exists on the primary path.

16 kbit/s XBL
The 16 kbit/s XBL provides a lower cost solution to the customer by reducing the interconnect costs between an RXCDR and BSC. This is achieved by reducing the XBL data rate from the current 64 kbit/s to 16 kbit/s. This frees three 16 kbit/s subchannels on the E1 64 kbit/s timeslot and enables them to be used as TCHs. A BSC can interconnect up to ten RXCDRs and vice-versa. A total of 20 XBL links are deployed in any configuration. An XBL can be configured without restriction in any timeslot. It is possible to select a rate of 16 kbit/s or 64 kbit/s on a XBL basis. Therefore, there can be two different rates at the same BSC to RXCDR, although this is not considered a typical configuration. As a result of the introduction of the 16 kbit/s RSL, there is no reduction in the processing capacity of the BSC or the RXCDR. Figure 2-15 demonstrates XBL utilization. Figure 2-15 XBL utilization

BSC 1

XBL

XBL

BSC 2

XBL

XBL

BSC 3

XBL

XBL

RXCDR

BSC 9

XBL

XBL

BSC 10

XBL

XBL

MAXIMUM OF TWO XBLs BETWEEN THE BSC AND XCDR OF EITHER 64 kbit/s OR 16 kbit/s ON THE E1 LINK. MAXIMUM OF TEN BSCs CONNECTED TO AN RXCDR OR VICE VERSA.

68P02900W21-S 01 Feb 2007 2-19

Network topology

Chapter 2: Transmission systems

Dynamic allocation of RXCDR to BSC circuits (DARBC)

The DARBC feature introduces fault management for call traffic on the BSC to RXCDR interface (referred to as the Ater interface), by managing the individual 16 kbit/s channels (called Ater channels) on this interface. In addition, this feature provides for validation of the CIC and Ater channel provisioning between the BSC and RXCDR to ensure that calls are placed on the correct circuit between the BSC and the MSC. Without this feature in place, fault management of the Ater channels is not possible. All Ater and CIC information must be manually verified by the operator, resulting in a higher O&M cost for the Motorola BSS. An operator has the option to operate either in the auto-connect mode or in the backwards compatibility mode. These modes are managed on a per AXCDR basis.

Auto-connect mode
This is a mode which can be selected by the operator. This mode refers to a BSC in which Ater channels are allocated and released dynamically as resources are provisioned, unprovisioned, or while handling a fault condition. Auto-connect mode provides fault tolerance along with the call processing efficiency of the backwards compatibility mode. This is the recommended mode of operation for the BSC.

Backwards compatibility mode

Backwards compatibility mode cannot be used in conjunction with the AMR or GSM half rate features. Auto-connect or enhanced auto-connect mode must be specified. This is a user selectable mode which refers to a BSC and/or RXCDR in which Ater channels and CICs are statically switch connected. This mode does not provide any fault tolerance and CIC validations. It is intended only to provide an upgrade path. Once both the BSC and RXCDR are upgraded, the use of autoconnect mode is recommended.

While upgrading the network, if the BSC is upgraded before the RXCDR, backwards compatibility mode must be used for the corresponding AXCDR. Before the introduction of this feature, all Ater channels were statically assigned and use of XBL links was not mandatory. Currently, if an operator decides to use the auto-connect, it is necessary to equip XBL links on the RXCDR and BSC. If XBLs are not equipped, and the AXCDR is operating in the auto-connect mode, all CICs at the BSC associated with that AXCDR are blocked and call traffic does not go to that AXCDR.

Enhanced auto-connect (EAC) mode

EAC mode allows for per call allocation of RXCDR to BSC circuits (Ater channels). There are some issues that the operator must consider when planning and provisioning the BSC/RXCDR network. EAC mode is introduced with the AMR feature and also applies to the GSM half rate feature. It takes advantage of the use of half rate traffic channels where only 8 kbit/s backhaul to the RXCDR is required. EAC mode is user enabled across a BSC - RXCDR interface and only provides benefits when the RXCDR is equipped with any number of EGDPs or GDP/GDP2s, and the BSC and RXCDR are populated exclusively with DSW2s (no KSWs).

68P02900W21-S 2-20 01 Feb 2007

System Information: BSS Equipment Planning

Network topology

When in EAC mode, a CIC no longer has a fixed position on the Ater interface. Rather, a CIC can be considered as belonging to a pool of CICs where a separate pool is maintained for each RXCDR connected to the BSC. When a call is assigned to a CIC, the BSC allocates an Ater channel that goes to the same RXCDR as the assigned CIC. One implication of such a pooling is that the number of CICs equipped that go through the RXCDR may not be the same as the number of Ater channels from the BSC to the RXCDR. XBL links are required between the BSC and RXCDR as in the auto-connect mode. Equipping less than 16 kbit/s in Ater capacity per equipped CIC relies upon a percentage of the calls to be utilizing half rate backhaul. If that assumption proves to be false, some capacity is lost as CICs are unusable due to a lack of Ater resources [if CIC - Ater provisioning is equal (16 kbit/s Ater capacity per CIC], EAC mode is not required and the system automatically reverts to auto-connect mode even if EAC is enabled). EAC mode also needs XBL bandwidth. Use of EAC mode (specifically the provisioning of fewer Ater channels than CICs) is best considered when BSC - RXCDR backhaul costs are a concern. If the operator chooses to equip a higher number of CICs than can be handled by the Ater channels, there is a possibility that a call assignment may fail because Ater channels are unavailable. To prevent such assignments from failing, the BSC provides a facility that automatically blocks at the MSC, all idle CICs that go through a particular RXCDR when the number of available Ater channels to RXCDR reaches a configurable threshold. The operator controls such thresholds through the cic_block_thresh and cic_unblock_thresh values. These thresholds are used to maintain Ater resources, to ensure that resources are available when a fault occurs and also to balance the call load.

For AMR, when the 7.95 kbit/s half rate codec mode is included in the Half Rate Active Codec Set, 16 kbit/s backhaul is required. This is provisioned on a per cell basis and should be taken into consideration when provisioning Ater resources.

68P02900W21-S 01 Feb 2007 2-21

Managed HDSL on micro BTSs

Chapter 2: Transmission systems

Managed HDSL on micro BTSs

Introduction
Managed HDSL brings the benefits of full OMC-R management to those products that support integrated HDSL technology. Specifically, it allows remote configuration, status, control, and quality of service information to be handled by the OMC-R. External HDSL modems configured as slave devices can also be managed by the same mechanism as long as they are connected to an integrated master HDSL port. This enables such an HDSL link to be managed entirely from the OMC-R. Following the introduction of this feature, the initial basic version of the product is no longer supported.

Horizonmicro2 microcell BTSs (and Horizoncompact2 macrocell BTSs) shipped after 31st December 2001 are not fitted with an internal HDSL modem. A suitable external HDSL modem must be used if a HDSL link to the BSC is required for these BTSs. The local Motorola office can provide assistance before purchasing a HDSL modem for this purpose.

Integrated HDSL interface

HDSL cable selection
The cabling needs to comply with the following selection guidelines: Correct number of pairs for an application. Each tip and ring pair must be of a twisted construction. The tip and ring must not be mixed between the pairs, that is, tip1 must not be used as a pair with ring 2. Either unshielded twisted pair (UTP) or shielded twisted pair (STP) can be used. The cable gauge should be between 0.4 mm and 0.91 mm (AWG 26 to AWG 19). Attenuation at 260 kHz should be less than 10.5 dB/km. Cable runs should be limited to a length depending on the product.

Certain types of cables are known to perform suitably in HDSL applications, provided they are correctly installed, and the guidelines for selection and installation are observed. Recommendations for the types of cables are as follows: Unshielded twisted pair o o o o BT CW1308 and equivalents Category 3 UTP Category 4 UTP Category 5 UTP

68P02900W21-S 2-22 01 Feb 2007

System Information: BSS Equipment Planning

Managed HDSL on micro BTSs

Shielded twisted pair o o o Category 3 STP Category 4 STP Category 5 STP

The following kinds of cables should be avoided for HDSL applications: Twisted quad cable is unsuitable for use in HDSL applications. A drop wire that consists of two parallel conductors with supporting steel cable works with HDSL but since it is not twisted, it provides little immunity from noise, and is therefore not recommended. An information cable which is typically made of non-twisted, multicore construction, for example, ribbon cable, is not recommended.

HDSL cable installation

If cabling does not exist between two end sites, the guidelines to be followed for the installation of cables are given: The conductor pairs should be connected point-to-point only, not point to multipoint. The use of different gauges of cable in one link should be avoided. Bridge taps in the cable run should be avoided. Loading coils in the cable run must be removed. The isolation between the tip and the ring should be greater than 1 Mohm (at SELV voltage levels). The isolation between the tip and earth should be greater than 1 Mohm (at SELV voltage levels). The isolation between the ring and earth should be greater than 1 Mohm (at SELV voltage levels).

HDSL range
HDSL range is affected by many factors, which should be taken into account when planning the system. Microcell systems can have longer distances, typically 2 km or so, because of their different link error requirements. The following factors reduce the available distances: o o o o Bridge gaps add unwanted loads onto the cables Gauge changes add unwanted signal reflections Small gauge cables increase the signal attenuations Other noise sources

HDSL is specified not to affect other digital subscriber link systems and voice traffic.

However, standard E1 traffic affects (and is affected by) HDSL systems running in the same cable binder, if unshielded from each other.

68P02900W21-S 01 Feb 2007 2-23

Managed HDSL on micro BTSs

Chapter 2: Transmission systems

General HDSL guidelines

Conversion of E1 to HDSL at a site away from the BSC needs either an external modem or a microsite. It is better to utilize the microsite to carry out this conversion (Refer to Figure 2-16). Figure 2-16 Conversion of E1 to HDSL links by modem and microsite
E1 LINK HDSL

SLAVE EXTERNAL MODEM

Horizonmicro2

BSC

E1 LINK

E1 LINK

SLAVE

HDSL

HDSL

E1 LINK

Horizonmicro2 BTS

EXTERNAL MODEM

Horizonmicro2 Horizonmicro2
HDSL

E1 LINK

HDSL

HDSL

Horizonmacro

Horizonmicro2 M = MASTER

Horizonmicro2 S = SLAVE

Horizonmicro2

Microcell BTSs have a maximum of two 2.048 Mbit/s links. If the HDSL equipped version is purchased (not available for Horizonmicro2 after December 2001), the links are automatically configured as either E1 or HDSL through a combination of database settings and auto-detection mechanisms. The setting of master/slave defaults can be changed by database settings for those scenarios, such as a closed loop daisy chain, where the defaults are not appropriate.

Microcell system planning

Network configurations from the BSC can be a combination of daisy chain and star. Links can be either E1 or HDSL, and can be mixed as appropriate within the network.

Daisy chain
Figure 2-17 shows a BSC connected to an external modem which then connects from its slave port to the master port of the Horizonmicro2. The slave port of the Horizonmicro2 connects to the next Horizonmicro2 master port, and so on, until the last Horizonmicro2 port is connected.

68P02900W21-S 2-24 01 Feb 2007

System Information: BSS Equipment Planning

Managed HDSL on micro BTSs

Figure 2-17 Microcell daisy chain network configuration

BSC

E1 LINK

SLAVE

HDSL

HDSL

HDSL

EXTERNAL MODEM

Horizonmicro2

Horizonmicro2

Horizonmicro2

M =

MASTER

S = SLAVE

Star configuration
Figure 2-18 shows a BSC which is connected to an external modem, which then connects from its slave port to the master port of a Horizonmicro2. In this configuration, an external modem is used every time a link to a Horizonmicro2 is used, hence the star formation. Figure 2-18 Microcell star network configuration

E1 LINK

SLAVE EXTERNAL MODEM

HDSL

Horizonmicro2

BSC

E1 LINK

SLAVE EXTERNAL MODEM

HDSL

Horizonmicro2

E1 LINK

SLAVE EXTERNAL MODEM

HDSL

Horizonmicro2

M =

MASTER

E1 link
In Figure 2-19, an E1 link is used from the BSC to the first Horizonmicro2. From there onwards, HDSL links are used, running from master to slave in each Horizonmicro2, or conversion can be at any BTS, in either direction. Figure 2-19 Microcell configuration using E1/HDSL links

E1 LINK S

HDSL

HDSL

Horizonmicro2 BSC M = MASTER

Horizonmicro2

Horizonmicro2

S = SLAVE

68P02900W21-S 01 Feb 2007 2-25

Managed HDSL on micro BTSs

Chapter 2: Transmission systems

68P02900W21-S 2-26 01 Feb 2007

Chapter 3 BSS cell planning

When planning a mobile telephone system, the aim is to create a communications network that fulfils the following requirements: Provides the desired capacity Offers good frequency efficiency Implemented at low cost High grade service

These requirements, when analyzed, actually conflict with one another. Therefore, the operating network is always a solution achieved through compromise. The cost of different network configurations can vary considerably. From an engineering point of view, it would be worthwhile to use efficient solutions despite high costs. However, a mobile telephone network is so huge an investment that the financial factors are always going to limit the possibilities. The effect of limited funds is particularly obvious during the first stage of the network. Consequently, economical planning is a condition for giving the best possible service from the onset. The use of the GSM900, EGSM900, and DCS1800 frequency bands create many propagation-based problems. As the channel characteristics are not fixed, design challenges and impairments arise. These impediments must be dealt with to protect MS telephone users from experiencing excessively varying signal levels and lack of voice quality. It is important to predict the RF path loss between the BTS and the MS within the coverage area in different types of environment. Knowledge of the transmitter and receiver antenna heights, nature of the environment, and terrain variations is essential. When planning a network, there are several major factors to be considered. These are described in the following topics: Planning tools GSM frequency spectrum Traffic capacity Adaptive multi-rate (AMR) GSM half rate Propagation effects on GSM frequencies Frequency re-use Overcoming adverse propagation effects Subscriber environment Microcellular solution Frequency planning Inter-radio access technology (2G-3G) cell reselection and handovers

68P02900W21-S 01 Feb 2007 3-1

Managed HDSL on micro BTSs

Chapter 3: BSS cell planning

Dual Transfer Mode Call model parameters for capacity calculations Control channel calculations GPRS/EGPRS traffic planning GPRS/EGPRS network traffic estimation and key concepts GPRS/EGPRS air interface planning process

68P02900W21-S 3-2 01 Feb 2007

System Information: BSS Equipment Planning

Planning tools

Planning tools
Introduction
It is essential to make many calculations at regular intervals from the BTS to predict the signal strength in a cell area. The smaller the interval, the more accurate is the propagation model. In addition, calculations should be performed at regular distances along each radial arm from the BTS, to map the signal strength as a function of distance from the BTS. The result is the necessity to perform hundreds of calculations for each cell, which is time consuming, but for the intervention of the software-planning tool. The planning tool can be fed with all the details of the cell, such as: Type of terrain Environment Heights of antennas

It can perform the necessary number of calculations required to provide an accurate picture of the propagation paths of the cell. Several planning tools are available in the market, such as Netplan or Planet, and it is up to the operators to select the tool(s) that suit them best. Check the figures by practical measurements after the calculation and implementation of the cell. This is because, with all the variable factors in propagation modeling, an accuracy of 80% is considered excellent.

68P02900W21-S 01 Feb 2007 3-3

GSM frequency spectrum

Chapter 3: BSS cell planning

GSM frequency spectrum

GSM900 frequency spectrum
The original GSM frequency spectrum was allocated in 1979. This consisted of two subbands 25 MHz wide. The frequency range is as follows: Uplink range: 890 MHz to 915 MHz Downlink range: 935 MHz to 960 MHz The uplink frequencies (mobiles transmitting to the BTS) are on the lowest frequency band. This is because there is a lower free space path loss for lower frequencies. This is more advantageous to the mobile as it has a reduced transmit output power capability compared to the BTS. The two bands are divided into channels; a channel from each band is then paired. One of the pair is allocated for uplink and one for the downlink. Each subband is divided into 124 channels; these are then given a number known as the Absolute Radio Frequency Channel Number (ARFCN). So a mobile allocated an ARFCN has one frequency to transmit and one to receive on. The frequency spacing between the pair is always 45 MHz for GSM. The spacing between individual channels is 200 kHz and at the beginning of each range is a guard band. 124 ARFCNs are allocated to the various network users. These ARFCNs are 1-124 inclusive. More frequencies were allocated to the GSM as they became available to provide for future network expansion. An extra 10 MHz was added on to the two GSM bands and this is known as Extended GSM (EGSM). The EGSM frequency range is as follows: Uplink range: 880 MHz to 915 MHz Downlink range: 925 MHz to 960 MHz This allows another 50 ARFCNs to be used, bringing the total to 174. These additional ARFCNs are 975 1023 inclusive.

The original Phase 1 MSs can only work with the original GSM frequency range and it needs a Phase 2 MS to take advantage of the extra ARFCNs. The operator cannot guarantee that the network has a significant number of Phase 2 MSs. Care should be taken when using EGSM frequencies not to make holes in the network for Phase 1 MSs.

68P02900W21-S 3-4 01 Feb 2007

System Information: BSS Equipment Planning

GSM frequency spectrum

DCS1800 frequency spectrum

As GSM evolved, it was decided to apply the technology to the Personal Communications Networks. This required changes to the air interface to modify the frequency range over which it operates. The modified frequency range is as follows: Uplink range Downlink range 1710 MHz to 1785 MHz 1805 MHz to 1880 MHz

This provides 374 ARFCNs with a frequency separation of 95 MHz between the uplink and downlink frequencies. In the UK, these ARFCNs are shared between the four network users (refer to Figure 3-1). Two of these network users, Orange and T-mobile operate exclusively in the DCS1800 range while the other two, Vodafone and O2 have been allocated DCS1800 channels on top of their GSM900 networks. ARFCNs are numbered from 512 to 885 inclusive. Digital Enhanced Cordless Telephony (DECT) uses the part at the top of the band. Figure 3-1 UK network users

Uplink
1785MHz DECT 1781.5MHz 1876.5MHz 1880MHz

Downlink
DECT

Orange

Orange

T-mobile

T-mobile

1721.5MHz

1816.5MHz

Vodafone/O2 1710MHz 1805MHz

Vodafone/O2

Absolute radio frequency channel capacity

Each RF carrier supports 8 time division multiplexed physical channels and each of these is capable of supporting speech or signaling information (refer to Figure 3-2). When AMR half rate or GSM half rate are enabled, each timeslot is divided into 2 subchannels, capable of supporting speech.

68P02900W21-S 01 Feb 2007 3-5

GSM frequency spectrum

Chapter 3: BSS cell planning

The maximum number of RF carriers at any one BTS site is 24 for Horizon II macro, Horizonmacro, and M-Cell6. Therefore, the maximum number of physical channels available at a BTS site is 24 x 8 = 192. When AMR or GSM half rate is used, each half rate enabled carrier supports a maximum of 16 physical channels. Figure 3-2 Eight TDMA timeslots per RF carrier
0 1 2 3 4 5 6 7

BTS

Maximum 24 carriers for Horizonmacro and M-Cell6 Maximum 25 carriers for BTS6

Modulation techniques and channel spacing

The modulation techniques used in GSM are Gaussian minimum shift keying (GMSK) and 8-Phase Shift Keying (PSK). GMSK is used for voice, circuit switched data and GPRS. This works by shaping the data to be modulated with a Gaussian filter. The filter removes some of the harmonics from the data square wave producing a more rounded shape. When this is applied to a phase modulator, the result is a modified envelope shape at the output of the modulator. The bandwidth of this envelope is narrower than that of a comparable one produced from non-filtered data. With each modulating carrier occupying a narrower bandwidth, more efficient use can be made of the available overall bandwidth. The modulations used in EGPRS are GMSK and 8-PSK. 8-PSK is a multi-level modulation in which 3 bits are mapped onto a symbol. The symbols are grey coded for reducing the number of bits in error between adjacent symbols. The 8-PSK signal is then filtered to ensure that GSM spectrum mask is preserved. This filter is a linearized GMSK pulse, that is, the main component in a Laurant decomposition of the GMSK modulation (refer to 3GPP TS 05.04 V8.4.0). The bandwidth allocated to each carrier frequency in GSM is 200 kHz. The actual bandwidth occupied by a transmitted GSM carrier is far greater than 200 kHz, even with Gaussian filtering. The signal therefore overlaps into surrounding frequencies, as illustrated in Figure 3-3.

68P02900W21-S 3-6 01 Feb 2007

System Information: BSS Equipment Planning

GSM frequency spectrum

Figure 3-3 Modulation techniques and channel spacing

-10 dB POINT

CHANNEL 1 dB 0 -10 -20 -30 -40 -50 -60 -70

CHANNEL 2

CHANNEL 3

200 kHz

If two carriers from the same or adjacent cells are allocated adjacent frequencies or channel numbers, they interfere with each other because of the described overlapping. This interference is an unwanted signal noise. All noise is cumulative, so starting with a large amount by using adjacent channels our wanted signal soon deteriorates the required quality standard. For this reason, adjacent frequencies should never be allocated to carriers in the same or adjacent cells. Figure 3-3 illustrates the fact that the actual bandwidth of a GMSK modulated signal (8-PSK possesses approximately the same spectrum mask) is considerably wider than the 200 kHz channel spacing specified by GSM. At the channel overlap point, the signal strength of the adjacent channel is only -10 dB the wanted signal. While this falls within the minimum carrier to interference ratio of 9 dB, it is significant and must be planned around so that allocation of adjacent frequencies in adjacent cells never occurs. One other consideration about channel spacing is when using combiners. If a cavity-combining block is used, the frequencies for combining should be separated by at least three ARFCNs else it could cause intermodulation products and spurious frequency generation. These could interfere with other carriers further away in the radio spectrum, possibly in adjacent cells. The source of interference becomes more difficult to locate as they would not necessarily be a problem to the home cell.

68P02900W21-S 01 Feb 2007 3-7

Traffic capacity

Chapter 3: BSS cell planning

Traffic capacity
Dimensioning
One of the most important steps in cellular planning is system dimensioning. Some idea of the projected usage of the system must be obtained (for example, the number of people wishing to use the system simultaneously) to dimension a system correctly. This means traffic engineering. Consider a cell with N voice channels; the cell is therefore capable of carrying N individual simultaneous calls. The traffic flow is defined as the average number of concurrent calls carried in the cell. The unit of traffic intensity is the Erlang. The traffic defined in this way can be thought of as a measure of the voice load carried by the cell. The maximum carried traffic in a cell is N Erlangs, which occurs when there is a call on each voice channel all the time. If during a time period T (seconds), a channel carrying traffic is busy for t (seconds), then the average carried traffic, in Erlangs, is t/T. The total traffic carried by the cell is the sum of the traffic carried by each channel. The mean call holding time is the average time a channel is serving a call.

Channel blocking
The standard model used to dimension a system is the Erlang B model, which models the number of traffic channels or trunks required or a given grade of service and given offered traffic. There are times when a call request is made and all the 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 is less than the offered traffic. If a call is blocked, the caller can try again within a short interval. If there is an absence of blocking, repeated call attempts increase the offered traffic the level. Because of this effect, the notion of offered traffic is somewhat confusing. However, if the blocking probability is small, ignore the effect of repeated call attempts and assume that the blocked calls are abandoned. The number of calls handled during a 24-hour period varies considerably with time. There are two peaks during weekdays, although the pattern can change from day to day. Across the typical day, the variation is such that a one-hour period shows greater usage than any other does. From the hour with the least traffic to the hour with the greatest traffic, the variation can exceed 100:1. There can also be unpredictable peaks caused by a wide variety of events (for example, the weather, natural disasters, conventions, sports events). In addition to this, system growth should be taken into account. There are a set of common definitions to describe this busy hour traffic loading. Busy Hour: The busy hour is a continuous period during which traffic volume or number of call attempts is the greatest. Peak Busy Hour: The busy hour each day, it is not usually the same over some days. Time Constant Busy Hour: The one-hour period starting at the same time each day for which the average traffic volume or call attempts count is greatest over the days under consideration. Busy Season Busy Hour: The engineering period where the grade of service criteria is applied for the busiest clock hour of the busiest weeks of the year. Average Busy Season Busy Hour: The average busy season busy hour is used for trunk groups and always has a grade of service criteria applied. For example, for the Average Busy Season Busy Hour load, a call requiring a circuit in a trunk group should not encounter All Trunks Busy (ATB) no more than 1% of the time. Peak loads are of more concern than average loads when engineering traffic routes and switching equipment.
68P02900W21-S 3-8 01 Feb 2007

System Information: BSS Equipment Planning

Traffic capacity

Traffic flow
If mobile traffic is defined as the aggregate number of MS calls (C) in a cell with regard to the duration of the calls (T) as well as their number, then traffic flow (A) can be defined as: Traffic Flow (A) = C x T Where C T Is the calling rate per hour. the average holding time per call.

Suppose an average hold time of 1.5 minutes is assumed and the calling rate in the busy hour is 120, then the traffic flow would be 120 x 1.5 = 180 call minutes or 3 call hours. One Erlang of traffic intensity on one traffic channel means a continuous occupancy of that particular traffic channel. Considering a group of traffic channels, the traffic intensity in Erlangs is the number of call-seconds per second or the number of call-hours per hour. For example, if there are a group of 10 traffic channels, which had a call intensity of 5 Erlangs, then half of the circuits would be busy at the time of measurement.

Grade of service
One measure of the quality of service is how many times a subscriber is unsuccessful in setting up a call (blocking). Blocking data states what grade of service is required. It is given as a percentage of the time that the subscriber is unable to make a call. Typical blocking for the MS-BSC link is 2% with 1% being acceptable on the BSC-MSC link. There is a direct relationship between the grade of service required and the number of channels. The customers desired grade of service has a direct effect on the number of channels needed in the network.

68P02900W21-S 01 Feb 2007 3-9

Adaptive multi-rate (AMR)

Chapter 3: BSS cell planning

Adaptive multi-rate (AMR)

Introduction
AMR offers two strong benefits: Expands air interface capacity through AMR half rate. Expands the area of high call quality coverage through AMR full rate.

The ability of the AMR codec to change the allocation of source and channel coding bits provide a high level of speech quality. The overall improvements are dependant upon channel quality (C/I). A codec with a higher level of error protection (and a corresponding decrease in speech quality) is selected as channel quality deteriorates, leading to an increase in the sensitivity of the transceivers, thus providing optimum performance. The half rate (hr) ability of AMR, which allows for two calls per timeslot, provides the largest increase in capacity, but at a cost of a decrease in voice quality. Initially the AMR capable MS penetration rate may be low; suggesting that in circumstances where capacity is paramount and voice quality is secondary then GSM half rate is employed as an alternative. For details about GSM half rate, see GSM half rate on page 3-14. With AMR operating in full rate mode, or in a mix of full rate and half rate where handovers between the modes are permitted, a capacity gain can be realized as a result of being able to operate at a lower C/I threshold. This can result in higher traffic loading. However, the benefits of AMR do not extend to the signaling channels, or to the use of non-AMR codecs and data services. Capacity gains of this type are dependent upon other factors (for example, propagation conditions) and any improvement gained by a replanning of existing systems should be considered with care. The 3GPP document, TR 46.076, Adaptive Multi-Rate (AMR) speech codec; Study Phase Report, is a summary of a report on AMR which contains additional information regarding the technical aspects and benefits.

Capacity and coverage

AMR half rate doubles the number of voice calls that can be supported over the air interface, thus allowing up to double the number of subscribers that are supported by a base station. This is achieved by halving the air interface necessary to support a single voice call using AMR half rate. On the backhaul, it is possible to support 8 voice calls per E1 timeslot instead of 4 when 8 kbit/s backhaul is used (refer to Figure 3-4).

68P02900W21-S 3-10 01 Feb 2007

System Information: BSS Equipment Planning

Adaptive multi-rate (AMR)

Figure 3-4 AMR half rate capacity increase

Quality of service
AMR full rate delivers improved voice quality in poorer radio environments, providing high quality in poorer signaling conditions: AMR full rate offers higher quality voice communications in poor radio environments such as corporate and urban buildings where no dedicated in-building coverage has been provided. AMR full rate improves voice quality across the entire network, by supporting high quality voice codecs in radio environments that cannot support Enhanced Full Rate (EFR).

AMR full rate expands the area of high quality voice coverage within a cell by intelligently selecting the best from a selection of codecs in various radio environments. Figure 3-5 shows the different profiles of these codecs.

68P02900W21-S 01 Feb 2007 3-11

Adaptive multi-rate (AMR)

Chapter 3: BSS cell planning

Figure 3-5 AMR full rate call quality improvements

In comparison to the EFR curve, AMR full rate offers a significantly higher quality codec solution in marginal radio environments (C/I = 13 to 4 dB). This enables operators to offer high voice quality in radio environments that does not support EFR. This improvement is paramount in urban environments, which usually have a C/I between 11dB and 13 dB.

Applications
With the flexibility of the AMR system, it is possible to customize the application of AMR to meet specific network and service needs. Some of the potential application scenarios are identified together with the advantages offered and the types of networks to which they suit.

Full rate only - High quality over full range of channel errors
Due to the robust error correction, ability of AMR, improved resilience to errors compared to GSM EFR is provided. So that when in call, the speech quality varies little with channel errors. It also provides significantly improved quality under marginal coverage conditions (for example, at cell edge, coverage holes, and so on). Some capacity advantage is also derived from the improved resilience under low C/I conditions. It supports tighter frequency re-use. Potential service applications - Suitable for operators who do not require to increase capacity through half rate operation, but wish to offer the best speech quality possible to all users.

Half rate only - Improved quality over current HR codec

The AMR codec can be operated in half rate channel mode to gain maximum capacity advantage. Potential service applications - Suitable for operators who need the greatest capacity enhancement from half rate operation. Some loss of quality at high channel error rates and in background noise can be expected.

68P02900W21-S 3-12 01 Feb 2007

System Information: BSS Equipment Planning

Adaptive multi-rate (AMR)

Full and half rate operation - HR tied to cell congestion

In this case, full rate is used until cell congestion triggers a switch to use of half rate channels. The operator also specifies a handover of half rate capable mobiles from a full rate channel to a half rate channel to help ease the congestion. This provides a tuneable trade-off between call quality and capacity. Potential service applications - Suitable for operators who want to combine speech quality and capacity improvements.

Migration to AMR half rate

When migrating, care should be taken to ensure that the call capacity rating of the various components of the system are not exceeded. Use of AMR HR improves the spectral efficiency over the air interface (and potentially the backhaul), but from a load perspective a half rate call has the same impact as a full rate call.

Interoperability with GSM half rate

AMR half rate and GSM half rate can coexist within a system, down to the RTF level. One subrate operates as AMR half rate, the other as GSM half rate.

Interoperability with EGPRS

When AMR half rate is enabled on an EGPRS capable carrier (pkt_radio_type = 3) in order to maximize the VersaTRAU backhaul utilization, only 8 kbit/s switching on the backhaul is supported.

68P02900W21-S 01 Feb 2007 3-13

GSM half rate

Chapter 3: BSS cell planning

GSM half rate

Introduction
GSM half rate offers enhanced capacity over the air interface, corresponding to the proportion of mobiles within a coverage area that supports GSM half rate. An air timeslot is split into two subchannels, each containing a half rate channel. Although the speech quality is considered inferior to other speech codecs, GSM half rate capable mobiles have a high penetration level due to its early introduction into the standards and hence it is considered a viable option for high-density areas.

Capacity and coverage

GSM half rate doubles the number of voice calls that can be supported over the air interface as with AMR half rate, thus allowing up to double the number of subscribers that are supported by a base station. This is achieved by halving the air interface capacity necessary to support a single voice call using GSM half rate. On the backhaul, it is possible to support 8 voice calls per E1 timeslot instead of 4 when 8 kbit/s backhaul is used (refer to Figure 3-6). Figure 3-6 GSM half rate capacity increase

Quality of service
The GSM half rate codec does not perform as well as the AMR half rate codec. Figure 3-7 shows the Mean Opinion Scores (MOS) for the various coding schemes versus C/I (the 4.75 <-> 7.95 values are for AMR half rate). This provides a relative comparison of voice quality against the other codecs.

68P02900W21-S 3-14 01 Feb 2007

System Information: BSS Equipment Planning

GSM half rate

Figure 3-7 GSM half rate codec comparison

Applications
GSM half rate is best suited for use when spectral efficiency is required. Two useful application scenarios are identified together with the advantages offered and the types of networks to which they are suited.

GSM half rate can be controlled at the cell level and is suitable to deal with high user density clusters.

Half rate
The GSM half rate codec can be operated in half rate channel mode to gain maximum capacity advantage. All qualifying calls are placed on a half rate channel. Potential service applications - Suitable for operators who need the greatest capacity enhancement from half rate operation. A reduction in speech quality is expected.

Full and Half rate operation - HR tied to cell congestion

In this case full rate is used until cell congestion triggers a switch to use GSM half rate channels. The operator also specifies a handover of half rate capable mobiles from a full rate channel to a half rate channel to help ease the congestion. This provides a tuneable trade-off between call quality and capacity. Potential service applications - Suitable for operators who want to combine speech quality and capacity improvements.

68P02900W21-S 01 Feb 2007 3-15

GSM half rate

Chapter 3: BSS cell planning

Migration to half rate

When migrating, care should be taken to ensure that the call capacity rating of the various components of the system are not exceeded. Use of GSM half rate improves the spectral efficiency over the air interface (and potentially the backhaul), but from a load perspective a half rate call has the same impact as a full rate call.

Interoperability with AMR half rate

GSM half rate and AMR half rate can coexist within a system, down to the RTF level. One subrate is operating as GSM half rate, the other as AMR half rate.

Interoperability with EGPRS

When GSM half rate is enabled on an EGPRS capable carrier (pkt_radio_type = 3) in order to maximize the VersaTRAU backhaul utilization, only 8 kbit/s switching on the backhaul is supported.

68P02900W21-S 3-16 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Propagation effects on GSM frequencies

Propagation production
Most of the methods used to predict propagation over irregular terrain are actually terrain based, since they are designed to compute the diffraction loss and free space loss based upon the path profile between the transmitter and the receiver. A widely used technique in the United Kingdom is the prediction method used by the Joint Radio Committee (JRC) of the Nationalized Power Industries. This method utilizes a computerized topographical map in a database, providing some 800,000-height reference points at 0.5 km intervals covering the whole of the UK. The computer predicts the received signal level by constructing the ground path profile between the transmitter and receiver using the database. The computer then tests the path profile for a line of sight path and tests whether the Fresnel zone clearance is obtained over the path. The free space and plane earth propagation losses are calculated, and the higher value is selected. If the line of sight and Fresnel-zone clearance test fails, then the program evaluates the loss caused by any obstructions and grades them into single or multiple diffraction edges. However, this method fails to take buildings into account when performing its calculation. The calculations are based upon the terrain features. Although the use of topographical based calculations are useful when designing mobile communication systems, most mobile systems are centered around urban environments. In the urban environments, the path between the transmitter and receiver can be blocked by some obstacles (buildings for example). Therefore, it is necessary to resort to approximate methods of calculating diffraction losses since exact calculations for each obstacle becomes difficult.

Decibels
The decibel (dB) is used to express power output levels, receiver input levels and path losses, and enables calculations used when planning radio systems to be simplified. Any number is expressed as a decibel. The only requirement is that the original description and unit scale is appended to the dB, indicating a value, which can be used when adding, subtracting, or converting decibels. For example, for a given power of 1 mW that is expressed as 0 dBm, the m refers to the fact that the original scale of measurement was in thousandths of a watt (milliwatts). For a power of 1 W, the equivalent in dB is 0 dBW. The decibel scale is logarithmic and this allows large or small numbers to be more easily expressed and calculated. For example, take a power of 20 watts transmitted from a BTS, which was .000000001 W at the receiver. It is difficult to express accurately the total power loss in a simple way. By converting both figures to decibels referenced to 1 mW, 20 W becomes 43 dBm and .000000001 W is -60 dBm. The path loss can now be expressed as 103 dBm. Multiplication and division also become easier when using decibels. Multiplication simply needs adding the dB figures together, while division needs subtracting one dB figure from the other. Another example is for every doubling of power figures, the increase is 3 dB and for every halving of power the decrease is 3 dB. Table 3-1 gives examples of dB conversions.

68P02900W21-S 01 Feb 2007 3-17

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

The basic equation used to derive power (dB) from power (W) is: N dB = 10 x log10 (PL/RPL) Where N PL RPL Is the required power level in dB. the power level being converted. the reference power level.

Table 3-1 dBm and dBW to power conversion dBm +59 +56 +53 +50 +49 +46 +43 +40 +39 +36 +33 +30 +27 * dBW 29 26 23 20 19 16 13 10 9 6 3 0* -3 Power 800 W 400 W 200 W 100 W 80 W 40 W 20 W 10 W 8W 4W 2W 1W 500 mW dBm + 24 + 21 + 20 +17 +14 +11 +10 +7 +4 +1 0 ** -3 -6 dBW -6 -9 -10 -13 -16 -19 -20 -23 -26 -29 -30 -33 -36 Power 250 mW 125 mW 100 mW 50 mW 25 mW 12.5 mW 10 mW 5 mW 2.5 mW 1.25 mW 1 mW 0.5 mW 0.25 mW dBm -9 -10 -20 -30 -40 -50 -60 -70 -80 -90 -100 -110 -120 dBW -39 -40 -50 -60 -70 -80 -90 -100 -110 -120 -130 -140 -150 Power 0.125 mW 0.1 mW 0.01 mW 1W 0.1 W 0.01 W 1 nW 0.1 nW 0.01 nW 1 pW 0.1 pW 0.01 pW 0.001 pW

1W reference value.

** 1 mW reference value.

The reference value is measured across a 50-ohm non-reactive load.

68P02900W21-S 3-18 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Fresnel zone
The Fresnel zone actually consists of several different zones, each one forming an ellipsoid around the major axis of the direct propagation path. Each zone describes a specific area depending on the wavelength of the signal frequency. If a signal from that zone is reflected on an obstacle, which protrudes into the zone, it means that a reflected signal as well as the direct path signal arrives at the receiver. Radio waves reflected in the first Fresnel zone arrives at the receiver out of phase with those taking the direct path and so combine destructively. This results in low received signal strength. It is important when planning a cell to consider all the radio paths for obstacles, which can produce reflections from the first Fresnel zone. If they exist, it is like planning permanent areas of no coverage in certain parts of the cell. To calculate whether this condition exists, the radius of the first Fresnel zone at the point where the object is suspected of intruding into the zone must be calculated. Figure 3-8 illustrates the formula.

F1 =

d1 * d 2 * d
Is F1 d1 d2 d the first Fresnel zone. distance from Tx antenna to the obstacle. distance from Rx antenna to the obstacle. wavelength of the carrier wave. total path length.

Where

Figure 3-8 First Fresnel zone radius calculation

FREQUENCY = 900 MHz WAVELENGTH = 30 cm

F1 d

d1

d2

Once the cell coverage has been calculated, the radio path can be checked for any objects intruding into the first Fresnel zone. Ideally the link should be planned for no =intrusions but in some cases they are unavoidable. If that is the case then the next best clearance for the first Fresnel zone is 0.6 of the radius. When siting a BTS on top of a building, care must be taken with the positioning and height of the antenna to ensure that the roof edge of the building does not intrude into the first Fresnel zone.

68P02900W21-S 01 Feb 2007 3-19

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

Radio refractive index (RRI)

It is important when planning a cell or microwave radio link to have an understanding of the effects the RRI can have on microwave communications, and also what causes these changes. RRI measurements provide planners with information on how much a radio wave is refracted by the atmosphere at various heights above sea level. Refraction (see Figure 3-9) is the changing of direction of propagation of the radio wave as it passes from a denser layer of the atmosphere to a less dense layer. It also occurs when passing from a less dense layer to a denser layer. This can also occur under certain conditions, even at higher altitudes. Figure 3-9 Refraction
REFRACTION OCCURS AS THE RADIO WAVE PASSES THROUGH LAYERS OF DIFFERENT ATMOSPHERIC DENSITY

EARTH

The main effect to cell planners is that changes in the RRI can increase or decrease the cell radius depending on conditions prevailing at the time. The RRI is referenced to a value n at sea level. The value varies with seasons and location but for the UK, the mean value is 1.00034. This figure is cumbersome to work with, so convention has converted n to N. Where N Is (n-1) x 106

The value of N now becomes 340 units for the UK. The actual seasonal and global variations are only a few tens of units at sea level. The following influence the value of N: The proportion of principal gasses in the atmosphere such as nitrogen, oxygen, carbon dioxide, and rare gasses. These maintain a near constant relationship as height is increased. Although they affect the RRI, the affect does not vary. The quantity of water vapor in the atmosphere. This is a variable and has significant effects on the RRI. The temperature, pressure, and water vapor pressure have major effects on the RRI.

68P02900W21-S 3-20 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

All either increases or decreases the RRI depending on local conditions, resulting in more or less refraction of a radio wave. Although for a well-mixed atmosphere, the RRI falls by 40 N units per 1 km increase in height sea level.

Measurement of RRI
There are two main ways of measuring the RRI at any moment in time. The first method is by use of Radio Sounds. This is an instrument, which is released into the atmosphere, normally attached to a balloon. It measures the temperature, pressure, and humidity as it rises. These are transmitted back to the ground station with a suitable reference value. The measurements of pressure are made every 35 m, humidity every 25 m, and temperature every 10 m. These together provide a relatively crude picture of what the value of the RRI is over a range of heights. The second method is a more sophisticated means of measuring the RRI. It uses fast response devices called refractometers. These are carried by a balloon, aircraft, or spaced apart on a high tower. These instruments are based upon the change in resonant frequency of a cavity with partially open ends caused by the change in RRI of air passing through the cavity. This gives a finer measurement showing variations in the RRI over height differences of a little over one meter. This is illustrated in the graph as shown in Figure 3-10. The aircraft mounted refractometer can give a detailed study over several paths and heights. Figure 3-10 Measurement of the RRI

HEIGHT (km)

0 RRI (N)

340

Effects of deviations
The lapse rate of 40 N per km is based on clear sky readings with good atmosphere mixing. A radio system is calibrated during these conditions and the height alignment in the case of a microwave point-topoint link is determined. It is easier to see the effects on a microwave point-to-point system when examining the effects of uneven variations of the RRI. Figure 3-11A shows an exaggerated curved radio path between two antennas under normal conditions. The atmosphere refracts the signal and the signal arrives at the receiving antenna. Figure 3-11B illustrates the condition known as super refraction, where the RRI increases greater than 40 N per km. This results in the path being refracted too much and not arriving at the receive antenna. While this does not cause any interference (as with sub refraction), it could result in areas of no coverage. Figure 3-11C illustrates the condition known as sub refraction, where the radio waves are not diffracted enough. This occurs when the lapse rate is less than 40 N per km. Under these conditions, the main signal path misses the receive antenna. Similar effects on a cell would increase the cell size, as the radio waves would be propagated, further resulting in co-channel and adjacent channel interference.

68P02900W21-S 01 Feb 2007 3-21

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

Figure 3-11 Refraction effects on a microwave system

EARTH

NORMAL REFRACTION

EARTH

SUPER REFRACTION

EARTH

SUB-REFRACTION

The last effect is known as ducting and occurs when the refraction of the radio wave produces a path, which matches the curvature of the Earth. If this happens radio waves are propagated over far greater distances than normal and can produce interference in places not subjected to any.

Events modifying the clear sky lapse rate

There are four main events that can modify the clear sky lapse rate and they are as follows: Radiation nights This is the result of a sunny day followed by clear skies overnight. The Earth absorbs heat during the day and the air temperature rises. After sunset, the Earth radiates heat into the atmosphere and its surface temperature drops. This heat loss is not replaced resulting in air closer to the surface cooling faster than air higher up. This condition causes a temperature inversion and the RRI profile no longer has a uniform lapse rate. This effect only occurs over land and not water as water temperature variations are over a longer period of time. Advection effects This effect is caused by high-pressure weather fronts moving from land to the sea or other large expanses of water. The result is warm air from the high-pressure front covering the relatively cool air of the water. When this combination is blown back over land, the trapped cool air causes a temperature inversion. It persists until the air mass strikes high ground where the increase in height mixes and dissipates the inversion.

68P02900W21-S 3-22 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Subsidence This occurs again in a high-pressure system. This time over land, when air descending from high altitude is heated by compression as it descends. This heated air then spreads over the cooler air. This type of temperature inversion occurs at an altitude of 1 km but can occasionally drop to 100 m where it causes severe disruption to radio signals.

Frontal systems This happens when a cold front approaching an area forces a wedge of cold air under the warmer air causing a temperature inversion. These disturbances tend to be short lived as the cold front dissipates quickly.

Although those described are the four main causes of RRI deviations, local pressure, humidity and temperature conditions could well give rise to events that affect the RRI.

Environmental effects on propagation

It is important to consider the effects that objects in the path of the radio wave have on it at the frequency range used for GSM. Most objects in the path have some effect on the signal as the wavelength is approximately 30 cm for GSM900 and 15 cm for DCSI1800. Such things as vehicles, buildings, office fittings even people and animals affect the radio wave in one way or another. The main effects can be summarized as follows: Attenuation Reflection Scattering Diffraction Polarization changes

Attenuation
Any object obstructing the wave path causing absorption of the signal (refer to Figure 3-12) causes attenuation. The effects are quite significant at GSM frequencies but still depend on the type of materials and dimensions of the object in relation to the wavelength used. Buildings, trees, and people cause the signal to be attenuated by varying degrees. Figure 3-12 Attenuation
INCOMING WAVE OBJECT ABSORBS THE ENERGY IN THE RADIO WAVE OUTGOING WAVE ATTENUATED BY THE OBJECT

68P02900W21-S 01 Feb 2007 3-23

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

Reflection
This is caused when the radio wave strikes a relatively smooth conducting surface. The wave is reflected at the same angle at which it arrived (see Figure 3-13). The strength of the reflected signal depends on how well the reflector conducts. The greater the conductivity, the stronger is the reflected wave. This explains why seawater is a better reflector than sand. Figure 3-13 Reflection
INCIDENT WAVE REFLECTED WAVE

EQUAL ANGLES SMOOTH SURFACE, SUCH AS WATER, VERY REFLECTIVE

AMOUNT OF REFLECTION DEPENDS ON CONDUCTIVITY OF THE SURFACE

Scattering
This occurs when a wave reflects off a rough surface (see Figure 3-14). The rougher the surface and the relationship between the size of the objects and the wavelength determines the amount of scattering that occurs. Figure 3-14 Scattering
INCIDENT WAVE ENERGY IS SCATTERED ROUGH STONY GROUND

Diffraction
Diffraction occurs when a radio wave is bent off its normal path. This happens when the radio wave passes over an edge, such as the edge of a building roof or at street level (see Figure 3-15). The amount of diffraction that takes place increases as the frequency used is increased. Diffraction can be a good thing as it allows radio signals to reach areas where they would not be propagated.

68P02900W21-S 3-24 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Figure 3-15 Diffraction

SIDE VIEW

EXPECTED PATH

SHADOW AREA

DIFFRACTED WAVE

PLAN VIEW

DIFFRACTED WAVE GIVING COVERAGE AROUND THE CORNER

MICRO BTS AT STREET LEVEL

DIFFRACTED WAVE GIVING COVERAGE AROUND THE CORNER

Polarization changes
This can happen with any of the effects due to atmospheric conditions and geomagnetic effects such as the solar wind striking the atmosphere of the earth. These polarization changes mean that a signal can arrive at the receiver with a different polarization than that which the antenna has been designed to accept. If this occurs, the antenna attenuates the received signal. Figure 3-16 shows the effects of polarization on a transmitted signal. Figure 3-16 Polarization
ELECTRICAL PART OF WAVE VERTICALLY POLARIZED ELECTRICAL STORM ELECTRICAL PART OF WAVE HORIZONTALLY POLARIZED (CHANGED BY ELECTRICAL STORM)

Tx

Rx

68P02900W21-S 01 Feb 2007 3-25

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

Multipath propagation
Rayleigh and Rician fading
The receiver picks up the same signal as a result of the propagation effects on the transmitted signal, which has been reflected from many different objects resulting in what is known as multipath reception. The signals arriving from the different paths have traveled different distances and therefore arrive at the receiver at different times with different signal strengths. Because of the reception time difference, the signals can or cannot be in phase with each other. The result is that some combine constructively resulting in a gain of signal strength while others combine destructively resulting in a loss of signal strength. The receiving antenna is not required to be moved far for the signal strength to vary by many tens of decibels. For GSM900, a move of just 15 cm or half a wavelength can suffice to observe a change in signal strength. This effect is known as multipath fading. It is experienced in urban areas where there are many buildings and the only signals received are from reflections and refractions of the original signal.

Rayleigh environment
Rayleigh has described this type of environment. Rayleigh analyzed the signal strength along a path with a moving receiver and plotted a graph of the typical signal strength measured due to multipath fading. The plot is specifically for non line of sight (refer to Figure 3-17) and is known as Rayleigh distribution (refer to Figure 3-18). Figure 3-17 Propagation effect - Rayleigh fading environment

Rx

Tx

68P02900W21-S 3-26 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Figure 3-18 Rayleigh distribution

SIGNAL STRENGTH

THRESHOLD

DEEP NULLS
1 2

/ WAVELENGTH

DISTANCE

Rician environment
When the signal path is predominantly in line of sight (see Figure 3-19) with insignificant reflections or diffractions arriving at the receiver, this is known as Rician distribution (see Figure 3-20). There are still fades in signal strength but they rarely dip the threshold which the receiver cannot process them. Figure 3-19 Propagation effect - Rician environment

Rx

Tx

68P02900W21-S 01 Feb 2007 3-27

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

Figure 3-20 Rician distribution

SIGNAL STRENGTH

THRESHOLD

DISTANCE

Comparison of DCS1800 and GSM900

From a pure frequency point of view, DCS1800 generally has more fades than GSM900. However, they are usually less pronounced.

Receive signal strength

A moving vehicle in an urban environment seldom has a direct line of sight path to the base station. The propagation path contains many obstacles in the form of buildings, other structures, and even other vehicles. Because there is no unique propagation path between the transmitter and receiver, the instantaneous field strength at the MS and BTS exhibits a highly variable structure. The received signal at the mobile is the net result of many waves that arrive through multiple paths formed by diffraction and scattering. The amplitudes, phase, and angle of arrival of the waves are random and the short-term statistics of the resultant signal envelope a Rayleigh distribution. Rician distribution is exhibited if a microcell is employed where part of a cell coverage area is predominantly the line of sight.

Free space loss

This is the loss of signal strength that occurs as the radio waves are propagated through free space. Free space is defined as the condition where there are no sources of reflection in the signal path. This is impossible to achieve in reality but it does give a good starting point for all propagation loss calculations. Equally important in establishing path losses is the effect that the devices radiating the signal have on the signal itself. The device is assumed as an isotropic radiator as a basis for the calculation. This is a theoretical pinpoint antenna, which radiates equally in every direction. If the device is placed in the middle of a sphere it would illuminate the entire inner surface with an equal field strength. The following formula is used to find out what the power covering the sphere is:

P=

Pt 4 * d 2

68P02900W21-S 3-28 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Where Pt d

Is the input power to the isotropic antenna. the distance from the radiator to the surface of the sphere.

This formula illustrates the inverse square law that the power decreases with the square of the distance. The effective aperture (Ae) of the receiving antenna must be calculated to work out the power received at a normal antenna.

Ae =

2 4

The actual received power can be calculated as follows:

Pr = P * Ae
If P is substituted with the formula for the power received over the inner surface of a sphere and Ae with its formula, then the result is:
2 Pt Pr = * 2 4 * d 4

Free space path loss

This is the ratio of the actual received power to the transmitted power from an isotropic radiator and is calculated by the following formula:

4 * d Free space loss in dB = 20log

Logs are used to make the figures more manageable. The formula is dependent on distance and frequency. The higher the frequency, the shorter is the wavelength, and therefore the greater the path loss. The formula is based on units measured in meters. For convenience, modify the formula to use kilometer and megahertz for the distance and frequency. It becomes:

Free space loss = 32 + 20logd + 20logf dB

Where d f Is the distance in km. the frequency in MHz.

Plane earth loss

The free space loss as stated is based solely on a theoretical model and is of no use by itself when calculating the path loss in a multipath environment. The earth in its role as a reflector of signals must be taken into account to provide a more realistic model. When calculating the plane earth loss, the model assumes that the signal arriving at the receiver consists of a direct path component and a reflective path component. Together these are called the space wave.

68P02900W21-S 01 Feb 2007 3-29

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

The formula for calculating the plane earth loss is:

d2 L = 20 log h1 * h 2 dB
This takes into account the different antenna heights at the transmitter and receiver. Although this is still a simple representation of path loss. When this formula is used it implies the inverse fourth law as opposed to the inverse square law. So, for every doubling of distance there is a 12 dB loss instead of 6 dB, as with the free space loss calculation. The final factors in path loss are the ground characteristics. These increase the path loss even further depending on the type of terrain (refer to Figure 3-21). The earths characteristics can be divided into three groups: Excellent earth: For example seawater; this provides the least attenuation, so a lower path loss. Good earth: For example, rich agricultural land, moist loamy lowland, and forests. Poor earth: For example, industrial or urban areas, and rocky land. These give the highest losses and are found when planning urban cells.

Figure 3-21 illustrates plane earth loss, taking all factors into account.

68P02900W21-S 3-30 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Figure 3-21 Plane earth loss

Tx FREE SPACE LOSS d Rx

PATH LOSS INCREASES 6 dB FOR A DOUBLING OF d.

Tx

Rx h1

2
h2

PLANE EARTH LOSS INCLUDES ONE EARTH REFLECTOR. PATH LOSS INCREASES 12 dB FOR A DOUBLING OF d.

Tx

Rx h1

3
h2

PLANE EARTH + CORRECTION FACTOR FOR TYPE OF TERRAIN. PATH LOSS INCREASES 12 dB FOR A DOUBLING OF d + A FACTOR FOR TYPE OF TERRAIN.

68P02900W21-S 01 Feb 2007 3-31

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

Clutter factor
The nature of the surrounding urban environment influences the propagation of the RF signal in an urban area. An urban area can then be placed into two sub categories- the built up area and the suburban area. The built up area contains tall buildings, office blocks, and high-rise residential tower blocks, whilst a suburban area contains residential houses, playing fields, and parks as the main features. Problems can arise in placing areas into one of these two categories, so two parameters are utilized. A land usage factor describing the percentage of the area covered by buildings and a degree of urbanization factor, describing the percentage of buildings of four storeys in the area.

F B(dB) = 20 + + 0.18L 0.34H + K 40

Where B(dB) F L H K U Is the clutter factor in dB. the frequency of RF signal. the percentage of land within 500 m square occupied by buildings. the difference in height between the squares containing the transmitter and receiver. 0.094U - 5.9 the percentage of L occupied by buildings of four storeys.

A good base station site should be high enough to clear all the surrounding obstacles in the immediate vicinity. Although employing high antennas increases the coverage area of the base station, this can also have adverse effects on channel re-use distances because of the increased possibility of co-channel interference.

Antenna gain
The additional gain provided by an antenna can be used to enhance the distance that the radio wave transmits. Antenna gain is measured against an isotropic radiator. Any antenna has a gain over an isotropic radiator because in practice it is impossible to radiate the power equally in all directions. This means that in some directions the radiated power is concentrated. This concentration, or focusing of power, is what enables the radio waves to travel further and if it was possible to be radiated from an isotropic radiator. Refer to Figure 3-22.

68P02900W21-S 3-32 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Figure 3-22 Focusing of power

ISOTROPIC RADIATOR (A SPHERICAL PATTERN) VERTICAL DIPOLE RADIATION PATTERN (SIDE VIEW)

TRANSMITTER

Measuring antenna gain

The gain of a directional antenna is measured by comparing the signal strength of a carrier emitted from an isotropic antenna and the directional antenna. First the power of the isotropic radiator is increased so that both receive levels are the same. The emitted powers required to achieve that are then compared for both antennas. The difference is a measure of gain experienced by the directional antenna. It always has some gain when compared to an isotropic radiator. See example in Figure 3-23. Figure 3-23 Measurement of gain

10 W

MEASUREMENT POINT

MEASUREMENT POINT 1000 W

TRANSMITTER

In this example, to achieve a balanced receive level the isotropic radiator must have an input power of 1000 W, as opposed to the directional antenna which only needs 10 W. The gain of the directional antenna is 100 dBi or 20 dBi.

68P02900W21-S 01 Feb 2007 3-33

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

Where i

Is isotropic.

The more directional the antenna is made than the more gain it experiences. This is apparent when sectorizing cells. Each sectored cell needs less transmit power than the equivalent range omni cell due to the gain of its directional antenna, 14 dBi to 17 dBi. The gain is also present in the receive path, though in all cases the gain decreases as the frequency increases. This is why the uplink mobile to BTS frequency is usually the lowest part of the frequency range. This gives a slight gain advantage to the lower power mobile transmitter.

Propagation in buildings
With the increased use of hand portable equipment in mobile cellular systems, combined with the increased availability of cordless telephones, it has become essential to study RF propagation into and within buildings. When calculating the propagation loss inside a building (see Figure 3-24), a building loss factor is added to the RF path loss. This building loss factor is included in the model to account for the increase in attenuation of the received signal when the mobile is moved from outside to inside a building. This is fine if all operators stand next to the walls of the building when making calls, but this does not happen, so the internal distance through which the signal passes should be considered. Due to the internal construction of a building, the signal can suffer from spatial variations caused by the design of the interior of the building.

68P02900W21-S 3-34 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Figure 3-24 Building propagation

TRANSMITTER

W dBm X dBm

X dBm = SIGNAL STRENGTH OUTSIDE BUILDING W dBm = SIGNAL STRENGTH INSIDE BUILDING BUILDING INSERTION LOSS (dBm) = X -W = B dBm

GAIN

TRANSMITTER

REFERENCE POINT

The building loss tends to be defined as the difference in the median field intensity at the adjacent area just outside the building and the field intensity at a location on the main floor of the building. This location can be anywhere on the main floor. This produces a building median field intensity figure, which is then used for plotting cell coverage areas and grade of service. When considering coverage in tall buildings, if any floors of that building are the height of the transmitting antenna, a path gain is experienced.

Okumura method
In the early 1960s, a Japanese engineer named Okumura carried out a series of detailed propagation tests for land mobile radio services at various different frequencies. The frequencies were 200 MHz in the VHF band and 453 MHz, 922 MHz, 1310 MHz, 1430 MHz, and 1920 MHz in the UHF band. The results were statistically analyzed and described for distance and frequency dependencies of median field strength, location variabilities, and antenna height gain factors for the base and mobile stations in urban, suburban, and open areas over quasi-smooth terrain. Okumura defined the correction factors corresponding to various terrain parameters for irregular terrain, such as rolling hills, isolated mountain areas, general sloped terrain, and mixed land or sea path. A method for predicting field strength and service area for a given terrain of a land mobile radio system was defined as a result of these tests carried out primarily in the Tokyo area. The Okumura method is valid for the frequency range of 150 MHz to 2000 MHz, for distances between the base station and the mobile stations of 1 km to 100 km, with base station effective antenna heights of 30m to 100m.

68P02900W21-S 01 Feb 2007 3-35

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

The results of the median field strength at the stated frequencies were displayed graphically (see Figure 3-25). Different graphs were drawn for each of the test frequencies in each of the terrain environments (for example; urban, suburban, and hilly terrain). The various antenna heights used at the test transmitter base stations are also shown on these graphs. The graphs show the median field strength in relation to the distance in km from the site. It does not transfer easily into a computer environment as this is a graphical representation of results. However, the results provided by Okumura are the basis on which path loss prediction equations have been formulated. Another Japanese engineer named Hata has carried out the most important work. Hata has taken Okumuras graphical results and derived an equation to calculate the path loss in various environments. These equations have been modified to take into account the differences between the Japanese terrain and the type of terrain experienced in Western Europe. Figure 3-25 Okumura propagation graphs
110

922 MHz
100 h.= 320 m h.= 220 m 90

x x x
Free Space

h.= 140 m h.= 45m h.= 3 m

FIELD STRENGTH (dB rel. 1 uV/m) FOR 1 kW ERP

80

70

60

50

40

x x x x x x x xx x xx x xxx xx x x x x

30

20

10

-10

0.6

5 LOG SCALE

10

20

30

40

50

60

70

80

90

100

LINEAR SCALE DISTANCE (km)

PROPAGATION GRAPH FOR 922 MHz

Hatas propagation formula

Hata used the information contained in Okumuras propagation loss report of the early 1960s, which presented its results graphically, to define a series of empirical formulas to allow propagation prediction to be done on computers. The propagation loss in an urban area can be presented as a simple formula of: A + B log 10R

68P02900W21-S 3-36 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Where A B R

Is the frequency. the antenna height function. the distance from the transmitter.

Using this basic formula, which is applicable to radio systems is the UHF and VHF frequency ranges. Hata added an error factor to the basic formula to produce a series of equations to predict path loss. Hata has set a series of limitations, which must be observed when using this empirical calculation method to facilitate this actionWhere Frequency range (fc) Distance (R) Base station antenna height (hb) Vehicular antenna height (hm) Is 100 to 1500 MHz 1 to 20 km 30 to 200 m 1 to 10 m

Hata defined three basic formulas based upon three defined types of coverage area: urban, suburban, and open. Hatas formula predicts the actual path loss, and not the final signal strength at the receiver. Urban Area: Lp = 69.55 + 26.16 log10fc - 13.82.log10hb - a(hm) # + (44.9 - 6.66. log10hb).log10R dB Where # Is the correction factor for vehicular station antenna height.

Medium - Small City: a(hm) = (1.1 . log10fc - 0.7).hm - (1.56.log10fc - 0.8) Large City: a(hm) = 3.2 (log10 11.75hm)2 - 4.97 Where fc Suburban Area: Lps = Lp [Urban Area] - 2. [log10 (f/28)] 2 - 5.4 dB Rural Area: Lpr = Lp [Urban Area] - 4.78. (log10fc) 2 + 18.33.log10fc - 40.94 dB Is > 400 MHz

68P02900W21-S 01 Feb 2007 3-37

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

Power budget and system balance

In any two-way radio system, the radio path losses and equipment output powers must be taken into account for both directions. This is especially true in a mobile network, where there are different characteristics for the uplink and downlink paths. These include receive path diversity gain in the uplink only, the possibility of mast head amplifiers in the uplink path, the output power capability of the mobile is a lot less than that of the BTS, and the sensitivity of the BTS receiver is usually better than that of the mobile. If these differences are not considered, it is possible that the BTS has a service area far greater than that which the mobile is able to use due to its limited output power. Therefore, the path losses and output powers in the uplink and downlink must be carefully calculated to achieve a system balance. One where the power required of the mobile to achieve a given range is equitable to the range offered by the power transmitted by the BTS. The output powers of the BTS and mobile are unlikely to be the same for any given distances due to the differences in uplink and downlink path losses and gains as described. Once the area of coverage for a site has been decided, the calculations for the power budget can be made. The system balance is then calculated which decides the output powers of the BTS and mobile to provide acceptable quality calls in the area of coverage of the BTS. The BTS power level must never be increased the calculated level for system balance. Although this seems a simple way to increase coverage, the system balance is different and the mobile cannot make a call in the new coverage area. Increase the gain of the antenna, to increase the cell coverage. This affects both the uplink and downlink therefore maintaining system balance. Separate antennas used for transmit and receive must be of similar gain. If the cell size is reduced, the BTS power can be altered as the mobiles output power is adaptive all the time. There is a statistic in the BTS that checks the path balance every 480 ms for each call in progress. The latest uplink and downlink figures reported along with the actual mobile and BTS transmit powers are used in a formula to give an indication of the path balance.

GSM900 path loss

Figure 3-26 and Table 3-27 compare the path losses at different heights for the BTS antenna and different locations of the mobile subscriber between 1 km and 100 km cell radius.

68P02900W21-S 3-38 01 Feb 2007

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies

Figure 3-26 BTS antenna height of 50 m, MS height of 1.5 m (GSM900

220 210 200 190
URBAN INDOOR URBAN SUBURBAN

PATH LOSS (dB)

180 170 160 150 140 130 120 110 100 90 1

RURAL (QUASI OPEN)

RURAL (OPEN)

10 CELL RADIUS (km)

100

Figure 3-27 BTS antenna height of 100 m, MS height of 1.5 m (GSM900)

220 210 200 190
URBAN INDOOR URBAN SUBURBAN

PATH LOSS (dB)

180 170 160 150 140 130 120 110 100 90 1

RURAL (QUASI OPEN)

RURAL (OPEN)

10 CELL RADIUS (km)

100

Path loss GSM900 against DCS1800

Figure 3-28 illustrates the greater path loss experienced by the higher DCS1800 frequency range compared to the GSM900 band. The cell size is typical of that found in urban or suburban locations. The difference in path loss for the GSM900 band at 0.2 km compared with 3 km is 40 dB, a resultant loss factor of 10,000 compared to the measurement at 0.2 km.

68P02900W21-S 01 Feb 2007 3-39

Propagation effects on GSM frequencies

Chapter 3: BSS cell planning

Figure 3-28 Path loss against cell radius for small cells
170

160

DCS1800 (METROPOLITAN CENTRES)

150

PATH LOSS (dB)

140

130

GSM900

120
DCS1800 (MEDIUM SIZED CITIES AND SUBURBAN CENTRES)

110

100 0.1 0.3 CELL RADIUS (km) 1.0 3.0

68P02900W21-S 3-40 01 Feb 2007

System Information: BSS Equipment Planning

Frequency re-use

Frequency re-use
Introduction
The network planner designs the cellular network around the available carriers or frequency channels. The frequency channels are allocated to the network provider from the GSM/EGSM900 and DCS1800 bands as shown Frequency Band GSM900 EGSM900 DCS1800 Tx Range 935 - 960 MHz 925 - 960 MHz 1805 - 1880 MHz Rx Range 890 - 915 MHz 880 - 915 MHz 1710 - 1785 MHz RF Carriers 124 174 374

Within this range of frequencies, only a finite number of channels are allocated to the planner. The number of channels does not necessarily cover the full frequency spectrum and care should be taken when selecting or allocating the channels. Installing a greater number of cells provides greater spectral efficiency with more frequency re-use of available frequencies. However, a balance must be struck between the spectral efficiency and all the costs of the cell. The size of cells also indicates how the frequency spectrum is used. Maximum cell radius is determined in part by the output power of the mobile subscriber (MS) and interference caused by adjacent cells (see Figure 3-29). The output power of the MS is limited in all frequency bands. Therefore to plan a balanced transmit and receive radio path, the planner must make use of the path loss and the link budget. The effective range of a cell varies according to the location, and can be as much as 35 km in rural areas and as little as 1 km in a dense urban environment.

68P02900W21-S 01 Feb 2007 3-41

Frequency re-use

Chapter 3: BSS cell planning

Figure 3-29 Adjacent cell interference

CARRIER F 33 INTERFERING CARRIER F 33

RECEIVE SIGNAL LEVEL

- 75dBm

- 100dBm SERVING BTS DISTANCE

INTERFERING BTS

MOBILE POSITION

Re-use pattern
The total number of radio frequencies allocated is split into some channel groups or sets. These channel groups are assigned on a per cell basis in a regular pattern, which repeats across all the cells. Thus, each channel set can be re-used several times throughout the coverage area, giving rise to a particular re-use pattern (for example, 7-cell re-use pattern shown in Figure 3-30). Figure 3-30 7 cell re-use pattern
EACH USING CHANNEL SETS

3 4 5 3 1 2 1

2 7 6 4 7 5 3 1 6 2

4 7 3 4 5 1 5

1 6 2 7 6

7 CELL RE-USE

The number of available channels per cell reduces and therefore the system capacity falls as the number of channel sets increases. However, as the number of channel sets increases, the distance between co-channel cells also increases, thus the interference reduces. Therefore selecting the optimum number of channel sets is a compromise between quality and capacity.

68P02900W21-S 3-42 01 Feb 2007

System Information: BSS Equipment Planning

Frequency re-use

4 site- 3 cell re-use pattern

Due to the increase in frequency robustness within the GSM, different re-use frequency patterns can be adopted which gives an overall greater frequency efficiency. The most common re-use pattern is 4 site with 3 cells (see Figure 3-31). With the available frequency allocation divided into 12 channels sets numbered a1-3, b1-3, c1-3, and d1-3. The re-use pattern is arranged so that the minimum re-use distance between cells is 2 to 1. Figure 3-31 3 cell re-use pattern

c1 c2 d1 d2 b1 b2 b3 a2 c1 c2 c3 d2 b1 b2 b3 a2 a3 NEW CELL CAN USE d1-3 FREQ ALLOCATION a1 d3 b2 b3 b1 d1 a3 c2 c3 d2 d3 d1 c1 a1 d3 b2 b3 a2 a3 a1 b1 c3 d2 d3 d1

EXAMPLE b1 b2 a1 a2 a3 c2 c3 c1 b3 a2

The other main advantage of this re-use pattern is if a new cell is inserted in the network, then there is always a frequency channel set available which does not cause any adjacent channel interference.

2 site- 6 cell re-use pattern

Another solution to network user capacity problems can be an even higher frequency re-use pattern. The re-use pattern, shown in Figure 3-32, uses a 2 site - 6 cell re-use.

68P02900W21-S 01 Feb 2007 3-43

Frequency re-use

Chapter 3: BSS cell planning

Figure 3-32 2 site - 6 cell re-use pattern

a1 a6 b1 b6 b5 b4 a4 a5 a6 a1 a3 a2 b2 b3 b6 b1 b2 a5 a4 b5 b4 b3 a2 a3

60 SECTORS

2 sites repeated each with 6 cells = 2 x 6 = 12 groups. If the operator has only 24 carriers allocated for their use, they are still in a position to use 2 carriers per cell. However, this can be difficult and cannot be possible to implement. It also cannot be possible due to the current network configuration. However, the subscribers per km ratio can be improved.

Carrier/Interference (C/I) ratio

When a channel is re-used, there is a risk of co-channel interference, where other base stations are transmitting on the same frequency. As the number of channel sets increases, the number of available channels per cell reduces and therefore capacity reduces. However, the interference level also reduces, increasing the quality of service. The capacity of any one cell is limited by the interference that can be tolerated for a given grade of service. Some other factors, apart from the capacity, affect the interference level: Power control (both BTS and MS) Hardware techniques Frequency hopping (if applied) Sectorization Discontinuous transmission (DTX)

Carrier or interference measurements taken at different locations within the coverage of a cell can be compared to a previously defined acceptable criterion. For instance, the criterion for the C/I ratio maybe set at 8 dB, with the expectation that the C/I measurements are better than that figure for 90% of the cases (C/I90). For a given re-use pattern, the predicted C/I ratio related to the D/R ratio can be determined (see Figure 3-33) to give the overall system comparison.

68P02900W21-S 3-44 01 Feb 2007

System Information: BSS Equipment Planning

Frequency re-use

Figure 3-33 Carrier interference measurements

C

(2 CELLS USING THE SAME BCCH FREQUENCY) /I CAN BE RELATED TO D/R

BS R
MS

BS

DISTANCE BETWEEN CELLS

D
ANALOGUE SYSTEM D/R = 4.4 GSM SYSTEM D/R = 2.62

GSM system: 9dB

C = 7.94 I

(D / R ) 4 = 7.94 6
D Therefore = 47.66 R
Thus
4

D 4 = 47.66 = 2.62 R

Sources of interference
Adjacent channel interference: This type of interference is characterized by unwanted signals from other frequency channels spilling over or injecting energy into the channel of interest. With this type of interference influenced by the spacing of RF channels, its effect can be reduced by increasing the frequency spacing of the channels. However, this has the adverse effect of reducing the number of channels available for use within the system. The base station and the mobile stations receiver selectivity can also be designed to reduce the adjacent channel interference. Environmental noise: This type of interference can also provide another source of potential interference. The intensity of this environmental noise is related to local conditions and can vary from insignificant to levels that can completely dominate all other sources of noise and interference.

68P02900W21-S 01 Feb 2007 3-45

Frequency re-use

Chapter 3: BSS cell planning

There are also several other factors which have to be taken into consideration. o o o The interfering co-channel signals in a given cell would normally arise from some surrounding cells, not just one. What effect do the directional antennas have when employed? If receiver diversity is to be used, what type and how is implementation to be achieved?

Sectorization of sites
As cell sizes are reduced, the propagation laws indicate that the levels of carrier interference tend to increase. In an omni cell, co-channel interference is received from six surrounding cells, all using the same channel sets. Therefore, one way of significantly cutting the level of interference is to use several directional antennas at the base stations, with each antenna radiating a sector of the cell, with a separate channel set. Sectorization increases the number of traffic channels available at a cell site, which means more traffic channels available for subscribers to use. In addition, by installing more capacity at the same site, there is a significant reduction in the overall implementation and operating costs experienced by the network user. By using sectorized antennas, sectorization allows the use of geographically smaller cells and a tighter economic re-use of the available frequency spectrum. This results in better network performance to the subscriber and greater spectrum efficiency. The use of sectorized antennas allows better control of any RF interference, which results in a higher call quality and an improved call reliability. More importantly for the network designer, sectorization extends and enhances the cells ability to provide the in-building coverage that is assumed by the hand portable subscriber. Sectorization provides the flexibility to meet uneven subscriber distribution by allowing, if required, an uneven distribution of traffic resources across the cells on a particular site. This allows a more efficient use of both the infrastructure hardware and the available channel resources. Finally, with the addition of diversity techniques, an improved sensitivity and increased interference immunity are experienced in a dense urban environment.

68P02900W21-S 3-46 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Overcoming adverse propagation effects

Hardware techniques
Multipath fading is responsible for more than just deep fades in the signal strength. The multipath signals are all arriving at different times and the demodulator attempts to recover all the time-dispersed signals. This leads to an overlapping situation where each signal path influences the other, making the original data hard to distinguish. This problem is known as inter symbol interference (ISI) and is made worse by the fact that the output from the demodulator is rarely a square wave. The sharp edges are normally rounded off so that when time dispersed signals are combined it makes it difficult to distinguish the original signal state. Another factor that makes things even more difficult is that the modulation technique Gaussian minimum shift keying introduces a certain amount of ISI. Although this is a known distortion and can under normal conditions be filtered out, when it is added to the ISI distortion caused by the time delayed multipath signals, it makes recovery of the original data that much harder.

Frequency hopping
Frequency hopping is a feature that can be implemented on the air interface (for example, the radio path to the MS) to help overcome the effects of multipath fading. GSM recommends only one type of frequency hopping - baseband hopping; but the Motorola BSS supports an additional type of frequency hopping, called synthesizer hopping.

Baseband hopping
Baseband hopping is used when a base station has several transceivers available. The data flow is routed in the baseband to various transceivers, each of which operates on a fixed frequency, in accordance with the assigned hopping sequence. The different transceivers receive a specific individual timeslot in each TDMA frame containing information destined for different MSs. There are important points to NOTE when using this method of providing frequency hopping: There is a requirement to provide as many transceivers as the number of allocated frequencies. Within Horizon II macro equipment applications, the use of any type of Tx block (DUP, HCU, DHU) is acceptable.

CCBs cannot be used with Horizon II macro equipment. If Horizon II macro CTU2s are used in Horizonmacro equipment and are controlled by a MCUF, baseband hopping is only supported when the CTU2s are used in single density mode. Within Horizonmacro equipment applications, the use of any type of Tx block (TDF, DCF, DDF) or cavity combining blocks (CCBs) is acceptable. Within M-Cell equipment applications, the use of either combining bandpass filter or hybrid, or cavity combining blocks is acceptable. The use of remote tuning combiners, cavity combining blocks or hybrid combiners is acceptable in BTS6 equipment applications.

68P02900W21-S 01 Feb 2007 3-47

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Synthesizer hopping
Synthesizer hopping uses the frequency agility of the transceiver to change frequencies on a timeslot basis for both transmit and receive. The transceiver board in the CTU, the digital processing, and control board in the TCU, and the SCB in the DRCU calculates the next frequency and programs one of the pair of Tx and Rx synthesizers to go to the calculated frequency. As the transceiver uses a pair of synthesizers for both transmit and receive, as one pair of synthesizers is used the other pair is retuning. There are important points to NOTE when using synthesizer hopping: Instead of providing as many transceivers as the number of allocated frequencies, there is only a requirement to provide as many transceivers as determined by traffic plus one for the BCCH carrier. The output power available with the use of hybrid combiners must be consistent with coverage requirements. CCBs cannot be used for synthesizer hopping (mechanical tuning is too slow).

Therefore as a general rule, cells with a small number of carriers make good candidates for synthesizer hopping, whilst cells with many carriers are good candidates for baseband hopping. There is also another rule: there can only be one type of hopping at a BTS site, not a combination of the two.

Error protection and detection

Many different coding schemes are used to protect the logical channels from transmission errors introduced by the radio path. The coding and interleaving schemes depend on the type of logical channel to be encoded. All logical channels need some form of convolutional encoding, but since protection needs are different, the code rates may also differ. The coding protection schemes, shown in Figure 3-34, are as follows: Speech channel encoding The speech information for one 20 ms full rate speech block is divided over eight GSM bursts. The speech information for one half-rate speech block is divided over four GSM bursts. This ensures that if bursts are lost due to interference over the air interface the speech can still be reproduced. Common control channel encoding 20 ms of information over the air carries four bursts of control information, for example BCCH. This enables the bursts to be inserted into one TDMA multiframe. Data channel encoding The data information is spread over 22 bursts. This is because every bit of data information is important. Therefore, when the data is reconstructed at the receiver, if a burst is lost, only a small proportion of the 20 ms block of data is lost. The error encoding mechanisms should then enable the missing data to be reconstructed.

68P02900W21-S 3-48 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Figure 3-34 coding process

20 ms INFORMATION BLOCK SPEECH (260 BITS FULL RATE OR ENHANCED FULL RATE, OR A BITS AMR) ENCODING CONTROL (184 BITS) INTERLEAVING CONTROL (4 BURSTS) 0.577 ms INFORMATION BURSTS SPEECH (8 BURSTS FULL RATE OR ENHANCED FULL RATE, OR B BURSTS AMR)

DATA (240 BITS)

DATA (22 BURSTS)

Refer to Table 3-2 for values of A bits and B bursts on a per channel type basis. The shaded areas indicate the channel types that are not supported. Table 3-2 Speech channel coding Channel type Is channel type supported? Yes Yes No Yes Yes No Yes No Yes Yes Yes Yes Yes No Yes Yes Yes Number of speech bits delivered per block (A) 244 204 159 148 134 118 103 95 159 148 134 118 103 95 260 244 112 Number of speech bursts delivered per block (B)r 8 8 8 8 8 8 8 8 4 4 4 4 4 4 8 8 4

TCH/AFS12.2 TCH/AFS10.2 TCH/AFS7.95 TCH/AFS7.4 TCH/AFS6.7 TCH/AFS5.9 TCH/AFS5.15 TCH/AFS4.75 TCH/AHS7.95 TCH/AHS7.4 TCH/AHS6.7 TCH/AHS5.9 TCH/AHS5.15 TCH/AHS4.75 TCH/FS TCH/EFS TCH/HS

68P02900W21-S 01 Feb 2007 3-49

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

AFS = AFR = AMR full rate (speech) AHS = AHR = AMR half rate (speech) HS = HR = GSM half rate (speech)

Figure 3-35 illustrates the coding process for full rate and enhanced full rate speech, control, and data channels; the sequence is complex. Figure 3-35 Coding process illustration (full rate and enhanced full rate speech)
EFR SPEECH FRAME 244 BITS FR SPEECH FRAME 260 BITS BCCH, PCH, AGCH, SDCCH, FACCH, SACCH, CBCH 184 BITS DATA TRAFFIC 9.6/4.8/2.4 k N0 BITS

RACH + SCH P0 BITS

CYCLIC CODE + REPETITION IN: 244 OUT: 260

FIRECODE + TAIL IN: 184 OUT: 228

ADD IN TAIL IN: N0 BITS OUT: N1 BITS

CYCLIC CODE + TAIL IN: P0 BITS OUT: P1 BITS

CLASS 1a CYCLIC CODE + TAIL IN: 260 OUT: 267

CONVOLUTION CODE IN: 267 BITS OUT: 456 BITS

CONVOLUTION CODE IN: 248 BITS OUT: 456 BITS

CONVOLUTION CODE + PUNCTURE IN: N1 BITS OUT: 456 BITS

CONVOLUTION CODE IN: P1 BITS OUT: 2 x P1 BITS

TCH/2.4 RE-ORDERING & PARTITIONING + STEALING FLAG IN: 456 BITS OUT: 8 SUB-BLOCKS

DIAGONAL INTERLEAVING + STEALING FLAG IN: BLOCKS OF 456 BITS OUT: 22 SUB-BLOCKS

BLOCK DIAGONAL INTERLEAVING IN: 8 BLOCKS OUT: PAIRS OF BLOCKS

BLOCK RECTANGULAR INTERLEAVING IN: 8 SUB-BLOCKS OUT: PAIRS OF SUB-BLOCKS

8 x TCH FR (BURSTS) 8 x TCH EFR (BURSTS) 8 x FACCH/TCH (BURSTS) 8 x TCH 2-4 kBIT/S (BURSTS)

4 x BCCH, PCH, AGCH 4 x SDCCH, SACCH 4 x CBCH (BURSTS)

1 x RACH 1 x SCH (BURST)

19 x TCH 9.6 kBIT/S (BURST)

68P02900W21-S 3-50 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Figure 3-36 illustrates the coding process for AMR full rate and AMR half rate speech, control and data channels. Figure 3-36 Coding process illustration (AMR full rate and AMR half rate speech)
AMR SPEECH FRAME "A" BITS (see ) BCCH, PCH, AGCH, SDCCH, FACCH, SACCH, CBCH 184 BITS DATA TRAFFIC 9.6/4.8/2.4 k N0 BITS

RACH + SCH P0 BITS

CLASS 1a CYCLIC CODE (6) + TAIL (4) IN: "A" OUT: "A" + 10 BITS

FIRECODE + TAIL IN: 184 OUT: 228

ADD IN TAIL IN: N0 BITS OUT: N1 BITS

CYCLIC CODE + TAIL IN: P0 BITS OUT: P1 BITS

CONVOLUTION CODE IN: A" + 10 BITS OUT: see

CODE PUNCTURING IN: see OUT (AFR): 448 BITS OUT (AHR): 224 BITS

CONVOLUTION CODE IN: 248 BITS OUT: 456 BITS

CONVOLUTION CODE + PUNCTURE IN: N1 BITS OUT: 456 BITS

CONVOLUTION CODE IN: P1 BITS OUT: 2 x P1 BITS

INBAND SIGNALLING IN (AFR): 448 BITS IN (AHR): 224 BITS OUT (AFR): 456 BITS OUT (AHR): 228 BITS

TCH/2.4

RE-ORDERING & PARTITIONING + STEALING FLAG IN: 456 BITS OUT: 8 SUB-BLOCKS

DIAGONAL INTERLEAVING + STEALING FLAG IN: BLOCKS OF 456 BITS OUT: 22 SUB-BLOCKS

BLOCK DIAGONAL INTERLEAVING IN: 8 BLOCKS OUT: PAIRS OF BLOCKS

BLOCK RECTANGULAR INTERLEAVING IN: 8 SUB-BLOCKS OUT: PAIRS OF SUB-BLOCKS

8 x TCH FR (BURSTS) 8 x TCH EFR (BURSTS) 8 x FACCH/TCH (BURSTS) 8 x TCH 2-4 kBIT/S (BURSTS)

4 x BCCH, PCH, AGCH 4 x SDCCH, SACCH 4 x CBCH (BURSTS)

1 x RACH 1 x SCH (BURST)

19 x TCH 9.6 KBIT/S (BURST) AFR = AMR Full Rate AHR = AMR Half Rate

68P02900W21-S 01 Feb 2007 3-51

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Code puncturing is performed to remove some of the encoded bits. In addition, for AMR half rate codecs, Class 2 bits are added to the Class 1 bits. The inband signaling bits (8 for AFR and 4 for AHR) are block-coded representations of the codec identifier, which indicates the AMR codec used for channel encoding in the forward channel and the AMR codec requested to be used for channel encoding in the reverse channel.

Figure 3-37 illustrates the coding process for GSM half rate speech, control, and data channels. Figure 3-37 Coding process illustration (GSM HR speech, control and data)
HR 112 bits EFR Speech Frame 244 bits FR Speech Frame 260 bits BCCH, PCH, AGCH, SDCCH, FACCH, SACCH, CBCH 184 bits Data Traffic 9.6/4.8/2.4K No Bits RACH + SCH PO Bits

Cyclic code + Tail In: 112 bits Out: 121 bits

Cyclic code + Repetition In: 244 bits Out: 260 bits

Firecode + Tail In: 184 bits Out: 228 bits Class 1A Cyclic Code + Tail In: 160 bits Out: 267 bits

Add In Tail In: No bits Out: N1 bits

Cyclic code + Tail In: P0 bits Out: P1 bits

Convolution Code In: 121 bits Out: 228 bits

Convolution Code In: 267 bits Out: 456 bits

Convolution Code In: 248 bits Out: 456 bits TCH/2.4

Convolution Code + Puncture In: N1 bits Out: 456 bits

Convolution Code In: P1 bits Out: 2 X P1 bits

Re-ordering & Partitioning + Stealing Flag In: 228 bits Out: 4 sub-blocks

Re-ordering & Partitioning + Stealing Flag In: 456 bits Out: 8 sub-blocks

DIAGONAL INTERLEAVING STEALING FLAG In: Blocks of 456 bits Out: 22 Sub-blocks

Block Diagonal Interleaving In: 4 blocks Out: Pairs of blocks

Block Diagonal Interleaving In: 8 blocks Out: Pairs of blocks

Block Rectangular Interleaving In: 8 sub-blocks Out: Pairs of sub-blocks

1 X RACH 1 X SCH (burst)

4 X TCH HR (bursts)

8 X TCH FR (bursts) 8 X TCH EFR (bursts) 8 X FACCH/TCH (bursts) 8 X TCH 2-4 kBits/S (bursts)

4 X BCCH, PCH, AGCH 4 X SDCCH, SACCH 4 X CBCH (bursts) 19 x TCH 9.6 kBIT/S (BURST)

68P02900W21-S 3-52 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Table 3-3 lists the output bits resulting from the convolutional coder and the number of punctured bits for the different AMR codecs (see Figure 3-36). Table 3-3 AMR codecs, convolutional output bits and punctured bits Codec mode TCH/AFS12.2 TCH/AFS10.2 TCH/AFS7.95 TCH/AFS7.4 TCH/AFS6.7 TCH/AFS5.9 TCH/AFS5.15 TCH/AFS4.75 TCH/AHS7.95 TCH/AHS7.4 TCH/AHS6.7 TCH/AHS5.9 TCH/AHS5.15 TCH/AHS4.75 Is codec mode supported? Yes Yes No Yes Yes No Yes No Yes Yes Yes Yes Yes No Rate 1/2 1/3 1/3 1/3 1/4 1/4 1/5 1/5 1/2 1/2 1/2 1/2 1/3 1/3 Number of output bits from convolutional coder 508 642 513 474 576 520 565 535 266 260 240 224 303 285 Number of punctured bits 60 194 65 26 128 72 117 87 78 64 40 16 91 73

AFS = AFR = AMR full rate (speech) AHS = AHR = AMR half rate (speech)

GSM speech channel encoding for full rate

The BTS receives transcoded speech over the Abis interface from the BSC. At this point, the speech is organized into its individual logical channels by the BTS. These logical channels of information are then channel coded before being transmitted over the air interface. The transcoded speech information is received in frames, each containing 260 bits. The speech bits are grouped into three classes of sensitivity to errors, depending on their importance to the intelligibility of speech.

Class 1a
Three parity bits are derived from the 50 Class 1a bits. Transmission errors within these bits are catastrophic to speech intelligibility; therefore, the speech decoder is able to detect uncorrectable errors within the Class 1a bits. If there are Class 1a bit errors, the whole block is ignored.

68P02900W21-S 01 Feb 2007 3-53

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Class 1b
The 132 Class 1b bits are not parity checked, but are fed together with the Class 1a and parity bits to a convolutional encoder. Four tail bits are added which set the registers in the receiver to a known state for decoding purposes.

Class 2
The 78 least sensitive bits are not protected at all. The resulting 456-bit block is then interleaved before being sent over the air interface.

Over the Abis link, when using full rate speech vocoding, 260 bits are transmitted in 20 ms equaling a transmission rate of 13 kbit/s. If enhanced full rate is used then 244 bits are transmitted over the Abis link for each 20 ms sample. The EFR frame is treated to some preliminary coding to build up to 260 bits before being applied to the same channel coding as full rate. The encoded speech now occupies 456 bits, but is still transmitted in 20 ms thus raising the transmission rate to 22.8 kbit/s. Figure 3-38 shows a diagrammatic representation of speech channel encoding. Figure 3-38 Speech channel encoding

260 BITS
CLASS 1a 50 BITS CLASS 1b 132 BITS CLASS 2 78 BITS TAIL BITS 50 3 132 4

PARITY CHECK

CONVOLUTIONAL CODE

378

78

456 BITS

68P02900W21-S 3-54 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

GSM speech channel encoding for enhanced full rate

The transcoding for enhanced full rate produces 20 ms speech frames of 244 bits for channel coding on the air interface. After passing through a preliminary stage, which adds 16 bits to make the frame up to 260 bits, the EFR speech frame is treated to the same channel coding as full rate. The additional 16 bits correspond to an 8-bit CRC, which is generated, from the 50 Class 1a bits plus the 15 most important Class 1b bits and 8 repetition bits corresponding to 4 selected bits in the original EFR frame of 244 bits.

Preliminary channel coding for EFR

EFR speech frame: o 50 Class 1a + 124 Class 1b + 70 Class 2 = 244 bits. Add 8 bits CRC generated from 50 Class 1a + 15 most important Class 1b bits to Class 1b bits. Add 8 repetition bits to Class 2 bits. 50 Class 1a + 132 Class 1b + 78 Class 2 = 260 bits. Preliminary coding: o o

Output from preliminary coding: o

EFR frame of 260 bits passed on for similar channel coding as full rate. Figure 3-39 shows a diagrammatic representation of preliminary coding for enhanced full rate speech. Figure 3-39 Preliminary coding for enhanced full rate speech

244 BITS
CLASS 1a 50 BITS CLASS 1b 124 BITS CLASS 2 70 BITS

8 BIT CRC ADDED TO CLASS 1b BITS

8 REPETITION BITS ADDED TO CLASS 2 BITS

CLASS 1a 50 BITS

CLASS 1b 132 BITS

CLASS 2 78 BITS

260 BITS

68P02900W21-S 01 Feb 2007 3-55

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

GSM speech channel encoding for half rate

The transcoded speech information is received in 20 ms speech frames, each containing 112 bits. The speech bits are grouped depending on their importance to the intelligibility of speech.

Class 1a
The 22 most significant bits of the 95 Class 1 bits are crucial to the speech intelligibility and hence are protected by 3 parity bits used for error detection. If there are errors in the Class 1a bits, the whole block is ignored.

Class 1b
The remaining of the Class 1 bits are not parity checked but are fed together with the Class 1a and parity bits to a convolutional encoder. Six tail bits are added which sets the registers in the receiver to a known state for decoding purposes.

Class 2
The remaining 17 bits (of the 112 total bits) are known as the Class 2 bits and are not protected. These are appended to the encoded Class 1 bits. The resulting 228-bit Block is then interleaved before being sent over the air interface. Figure 3-40 shows a diagrammatic representation of preliminary coding for GSM HR speech. Figure 3-40 Speech channel encoding for GSM half rate speech

CLASS 1a 22 BITS

CLASS 1b 73 BITS

CLASS 2 17 BITS TAI L BITS

PAR ITY CHECK

CLASS 1a 22 BITS 3

CLASS 1b 73 BITS

211 Con voluted Bits

CLASS 2 17 BITS

228 BITS

68P02900W21-S 3-56 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

GSM speech channel encoding for AMR full rate

The transcoded speech information is received in frames, each containing X bits, where X varies over the different AMR full rate codecs (see Table 3-4 for values of X). The speech bits are grouped into two classes of sensitivity to errors, depending on their importance to the intelligibility of speech.

Class 1a
Six parity bits are derived from the Y Class 1a bits, where Y varies over the different AMR full rate codecs (see Table 3-4 for values of Y). Transmission errors within these Class 1a bits are catastrophic to speech intelligibility; therefore, the speech decoder is able to detect uncorrectable errors within the Class 1a bits. If there are Class 1a bit errors, the whole block is ignored.

Class 1b
The Z Class 1b bits are not parity checked, but are fed together with the Class 1a and parity bits to a convolutional encoder. Four tail bits are added which set the registers in the receiver to a known state for decoding purposes. Z varies over the different AMR full rate codecs (see Table 3-4 for values of Z). The convolutionally coded symbols are punctured to reduce the resulting data rate to that supported over the air interface. AMR codecs use a set of Systematic Recursive (SR) convolutional codes instead of the Non-Systematic Non-Recursive (NSNR) convolutional codecs used by full rate and enhanced full rate. The SR codes selected for AMR are more complex and expensive than the NSNR codecs for EFR and FR. However, they provide better error protection.

InBand signaling
InBand signaling bits are used to coordinate the codec usage between the BTS and MS because the utilized channel codec can vary dynamically from speech frame to speech frame (see Link Adaptation section). These bits alternately indicate to the receiver which codec was used to channel encode the speech frame, and which codec the sender would like to receive in the opposite direction. Eight InBand signaling bits are added to the encoded and punctured Class 1a, 1b, and parity bits. The InBand signaling bits are the block-coded representation of the appropriate 2-bit codec identifier. The resulting 456-bit block is then interleaved before being sent over the air interface. The encoded speech now occupies 456 bits, but is still transmitted in 20 ms, thus raising the transmission rate to 22.8 kbit/s. Table 3-4 X, Y and Z bit values for AMR FR speech channel encoding Codec mode TCH/AFS12.2 TCH/AFS10.2 TCH/AFS7.95 TCH/AFS7.4 TCH/AFS6.7 TCH/AFS5.9 TCH/AFS5.15 TCH/AFS4.75 Is codec mode supported? Yes Yes No Yes Yes No Yes No X bits 244 204 159 148 134 118 103 95 Y bits 81 65 75 61 55 55 49 39 Z bits 163 139 84 87 79 63 54 56

68P02900W21-S 01 Feb 2007 3-57

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

AFS = AFR = AMR full rate (speech) AHS = AHR = AMR half rate (speech)

Figure 3-41 shows a diagrammatic representation of speech channel encoding for AMR full rate. Figure 3-41 Speech channel encoding for AMR full rate
CLASS 1a Y BITS CLASS 1b Z BITS TAIL BITS Y 6 Z 4

PARITY CHECK

CONVOLUTIONAL CODE

INBAND SIGNALLING BITS 8

CODE PUNCTURING 448

456 BITS

GSM speech channel encoding for AMR half rate

The BTS receives transcoded speech over the Abis interface from the BSC. The speech is organized into its individual logical channels by the BTS. These logical channels of information are then channel coded before being transmitted over the air interface. The transcoded speech information is received in frames, each containing X bits, where X varies over the different AMR half rate codecs (see Table 3-5 for values of X). The speech bits are grouped into three classes of sensitivity to errors, depending on their importance to the intelligibility of speech.

Class 1a
Six parity bits are derived from the Y Class 1a bits, where Y varies over the different AMR half rate codecs (see Table 3-5 for values of Y). Transmission errors within these Class 1a bits are catastrophic to speech intelligibility; therefore, the speech decoder is able to detect uncorrectable errors within the Class 1a bits. If there are Class 1a bit errors, the whole block is ignored.

Class 1b
The Z Class 1b bits are not parity checked, but are fed together with the Class 1a and parity bits to a convolutional encoder. Four tail bits are added which set the registers in the receiver to a known state for decoding purposes. Z varies over the different AMR half rate codecs (see Table 3-5 for values of Z). The convolutionally coded symbols are punctured to reduce the resulting data rate to that supported over the air interface.

68P02900W21-S 3-58 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

AMR codecs use a set of Systematic Recursive (SR) convolutional codes instead of the Non-Systematic Non-Recursive (NSNR) convolutional codecs used by half rate. The SR codes selected for AMR are more complex and expensive than the NSNR codecs for HR. However, they provide better error protection.

Class 2
Any channel coding does not protect the W Class 2 bits. They are simply appended to the encoded and punctured class 1a, 1b, and parity bits. W varies over the different AMR half rate codecs (see Table 3-5 for values of W).

InBand signaling
InBand signaling bits are used to coordinate the codec usage between the BTS and MS because the utilized channel codec can vary dynamically from speech frame to speech frame (see Link Adaptation section). These bits alternately indicate to the receiver which codec was used to channel encode the speech frame, and which codec the sender would like to receive in the opposite direction. Four InBand signaling bits are added to the encoded and punctured class 1a, 1b, parity, and Class 2 bits. The InBand signaling bits are the block-coded representation of the appropriate 2-bit codec identifier. The resulting 228-bit block is then interleaved before being sent over the air interface. The encoded speech now occupies 228 bits, but is still transmitted in 20 ms, thus raising the transmission rate to 11.4 kbit/s. Two half rate subchannels sharing the same timeslot have a total transmission rate of 22.8 kbit/s. Table 3-5 X, Y, Z and W bit values for AMR HR speech channel encoding Codec mode TCH/AHS7.95 TCH/AHS7.4 TCH/AHS6.7 TCH/AHS5.9 TCH/AHS5.15 TCH/AHS4.75 Is codec mode supported? Yes Yes Yes Yes Yes No X bits 159 148 134 118 103 95 Y bits 67 61 55 55 49 39 Z bits 56 59 55 47 42 44 W bits 36 28 24 16 12 12

AFS = AFR = AMR full rate (speech) AHS = AHR = AMR half rate (speech)

Figure 3-42 shows a diagrammatic representation of speech channel encoding for AMR half rate.

68P02900W21-S 01 Feb 2007 3-59

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Figure 3-42 Speech channel encoding for AMR half rate

CLASS 1a Y BITS

CLASS 1b Z BITS

CLASS 2 W BITS TAIL BITS

PARITY CHECK

CONVOLUTIONAL CODE

INBAND SIGNALLING BITS 4 W

CODE PUNCTURING

228 BITS

Link adaptation for AMR channels

The fundamental performance benefit of the AMR traffic channel is the networks ability to dynamically select the optimal speech and channel codec combination in reaction to the observed channel conditions. Link adaptation is the process by which the optimal codec is selected. A non-AMR traffic channel, such as full rate or Enhanced full rate, is permitted to use one fixed speech and channel codec combination only. In favorable channel conditions, this provides high sound quality. However, as the channel conditions degrade, the Bit Error Rate (BER) and Frame Erasure Rate (FER) increase. These erased frames and bit errors significantly degrade sound quality. Conversely, an AMR traffic channel, based on the observed channel conditions, is permitted to select dynamically the optimal codec combination from a set of up to 4. The AMR codec combination characteristics range from high vocoding rate / low channel coding rate to low vocoding rate / high channel coding rate. The optimal codec combination is the one, which provides the appropriate amount of voice and channel coding to maximize the sound quality with the constraint of maintaining a maximum permitted FER level. Thus, in any channel condition, an AMR traffic channel limits erased frames to a permitted level yet provides the highest sound quality possible for that condition. For example, under good channel conditions, the AMR traffic channel selects the codec combination with the highest vocoding and lowest channel coding rates. Here, the minimal channel coding is sufficient to maintain the permitted FER level. Moreover, the vocoding provides high sound quality rivaling that of EFR operating in a good channel condition. Under poor channel conditions, the AMR channel selects the codec combination with the lowest vocoding and highest channel coding rates. Here, the increased channel coding is sufficient to correct bit errors and thus maintain the permitted FER level. The decreased vocoding provides sound quality, which is noticeably less than EFR, operating in a good channel condition. However, the speech frames are not erased, as they would be for EFR and FR operating under a poor channel condition. Thus, unlike EFR and FR, intelligible voice is still communicated, just with less sound quality. This is better than no voice at all.

68P02900W21-S 3-60 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Measuring channel conditions: C/I

On an AMR traffic channel, both the BTS and mobile observe and measure, their respective receive channel conditions. This measurement is converted to a carrier to interference (C/I) value. The measured C/I value is compared to configurable C/I ranges which define when a particular codec combination (out of the set of 4) should be selected. As C/I increases into the next highest range, the link adaptation process selects the combination with the next highest vocoding / next lowest channel coding rates. As the C/I decreases into the next lowest range, the link adaptation process selects the combination with the next lowest vocoding / next highest channel coding rates.

Coordinating adaptation: InBand signaling

Once a codec combination is selected, it must be conveyed to the sender to instruct it to use the selected combination in future speech transmissions. The BTS selects the optimal codec combination and instructs the mobile to use it for subsequent uplink speech transmissions. Likewise, the mobile selects the optimal combination and instructs the BTS to use it for subsequent downlink speech transmissions. These instructions are conveyed using the InBand signaling bits, which reside within each encoded and transmitted speech frame. Link adaptation, or the selecting of optimal codec combinations, is performed independently and simultaneously for the uplink and downlink channels. To coordinate these processes, two types of InBand signaling are used. Each is sent in alternating encoded and transmitted speech frames. Codec Mode Indication (CMI) Codec Mode Command/Request (CMC/R)

The CMI indicates to the receiver which codec combination was used by the sender to encode the currently and subsequently transmitted speech frame. Thus, the receiver can determine which combination to use in decoding the current and next received speech frames. The CMR indicates to the BTS which codec combination the mobile would prefer be used in downlink speech encoding and transmission. Generally, the BTS grants this request. Similarly, the CMC indicates to the mobile which codec combination the BTS would prefer be used in uplink speech encoding and transmission. This command is always granted.

GSM control channel encoding

Figure 3-43 shows the principle of the error protection for the control channels. This scheme is used for all the logical signaling channels, the synchronization channel (SCH) and the random access burst (RACH). The diagram applies to SCH and RACH, but with different numbers.

68P02900W21-S 01 Feb 2007 3-61

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Figure 3-43 Control channel coding

184 BITS

184

PARITY BITS

FIRE CODE

TAIL BITS

184

40

CONVOLUTIONAL CODE

456

456 BITS
When control information is received by the BTS it is received as a block of 184 bits. These bits are first protected with a cyclic block code of a class known as a Fire Code. This is particularly suitable for the detection and correction of burst errors, as it uses 40 parity bits. Before the convolutional encoding, four tail bits are added which set the registers in the receiver to a known state for decoding purposes. The output from the encoding process for each block of 184 bits of signaling data is 456 bits, exactly the same as for speech. The resulting 456-bit block is then interleaved before being sent over the air interface.

GSM circuit-switched data channel encoding

Figure 3-44 shows the principle of the error protection for the 9.6 kbit/s data channel. The other data channels at rates of 4.8 kbit/s and 2.4 kbit/s are encoded slightly differently, but the principle is the same.

68P02900W21-S 3-62 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Figure 3-44 Data channel encoding

DATA CHANNEL 9.6 kbit/s 240 BITS

240 TAIL BITS

240

CONVOLUTIONAL CODE

488

PUNCTURE

456

456 BITS
Data channels are encoded using a convolutional code only. With the 9.6 kbit/s data, some coded bits require to be removed (punctuated) before interleaving, so that like the speech and control channels, they contain 456 bits every 20 ms. The data traffic channels need a higher net rate than their actual transmission rate (net rate means the bit rate before the coding bits have been added). For example, the 9.6 kbit/s service needs 12 kbit/s, because status signals (such as the RS-232 DTR) have to be transmitted as well. The output from the encoding process for each block of 240 bits of data traffic is 456 bits, exactly the same as for speech and control. The resulting 456-bit block is then interleaved before being sent over the air interface.

Over the PCM link, 240 bits were transmitted in 20 ms, equaling a transmission rate of 12 kbit/s, 9.6 kbit/s raw data, and 2.4 kbit/s signaling information. The encoded control information now occupies 456 bits but is still transmitted in 20 ms thus raising the transmission rate to 22.8 kbit/s.

68P02900W21-S 01 Feb 2007 3-63

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Mapping logical channels in the TDMA frame structure

Interleaving
Having encoded or error protected the logical channel; the next step is to build its bitstream into bursts that can then be transmitted within the TDMA frame structure. It is at this stage that the process of interleaving is carried out. Interleaving spreads the content of one traffic block across several TDMA timeslots. The following interleaving depths are used: Speech (full rate) - 8 blocks Speech (half rate) - 4 blocks Control - 4 blocks Data - 22 blocks

This process is an important one, for it safeguards the data in the harsh air interface radio environment. Because of interference, noise, or physical interruption of the radio path, bursts may be destroyed or corrupted as they travel between the MS and BTS. A figure of 10 to 20% is quite normal. The purpose of interleaving is to ensure that only some of the data from each traffic block is contained within each burst. Thus when a burst is not correctly received, the loss does not affect the overall transmission quality because the error correction techniques are able to interpolate for the missing data. If the system worked by simply having one traffic block per burst, then it would be unable to do this and transmission quality would suffer. It is interleaving (summarized in Table 3-6) that is largely responsible for the robustness of the GSM air interface, enabling it to withstand significant noise and interference, and maintain the quality of service presented to the subscriber. Table 3-6 Interleaving Transcoder Rate Adaptation Unit (TRAU) frame type Speech (full rate) Speech (half rate) Control CS data Number of GSM bursts the traffic block is spread over 8 4 4 22

Diagonal interleaving - full rate speech

Figure 3-45 illustrates, in a simplified form, the principle of the interleaving process applied to a full rate speech channel.

68P02900W21-S 3-64 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Figure 3-45 Diagonal interleaving - full rate speech

20 ms SPEECH SAMPLE 456 BITS 20 ms SPEECH SAMPLE 456 BITS 20 ms SPEECH SAMPLE 456 BITS BITS 0, 8, 16, 24 ..... 448

BITS 4, 12, 20, 28 ..... 452

BITS 0, 8, 16, 24 ..... 448

MAPPED TO ODD BITS OF BURST

MAPPED TO EVEN BITS OF BURST

MAPPED TO EVEN BITS OF BURST

BITS 4, 12, 20, 28 ..... 452 MAPPED TO ODD BITS OF BURST

012345678 .... 113

012345678 .... 113

The diagram shows a sequence of speech blocks after the encoding process. Each block contains 456 bits, these blocks are then divided into eight blocks each containing 57 bits. Each block contains bits from even bit positions or bits from odd bit positions. The GSM burst is produced using these blocks of speech bits. The first four blocks is placed in the even bit positions of the first four bursts. The last four blocks are placed in the odd bit positions of the next four bursts. As each burst contains 114 traffic-carrying bits, it is shared by two speech blocks. Each block shares four bursts with the block preceding it, and four with the block that succeeds it, as shown. In the diagram, block 5 shares the first four bursts with block 4 and the second four bursts with block 6.

Diagonal interleaving - half rate speech

Figure 3-46 illustrates, in a simplified form, the principle of the interleaving process applied to a half rate speech channel.

68P02900W21-S 01 Feb 2007 3-65

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Figure 3-46 Diagonal interleaving - half rate speech

20 ms SPEECH SAMPLE 228 BITS 20 ms SPEECH SAMPLE 228 BITS 20 ms SPEECH SAMPLE 228 BITS BITS 0, 8, 16, 24 ..... 224

BITS 4, 12, 20, 28 ..... 225

BITS 0, 8, 16, 24 ..... 224

MAPPED TO ODD BITS OF BURST

MAPPED TO EVEN BITS OF BURST

MAPPED TO EVEN BITS OF BURST

BITS 4, 12, 20, 28 ..... 225 MAPPED TO ODD BITS OF BURST

012345678 .... 113

012345678 .... 113

The diagram shows a sequence of speech blocks after the encoding process. Each block contains 228 bits, these blocks are then divided into four blocks each containing 57 bits. Each block contains bits from even bit positions or bits from odd bit positions. The GSM burst is produced using these blocks of speech bits. The first two blocks are placed in the even bit positions of the first two bursts. The last two blocks are placed in the odd bit positions of the next two bursts. As each burst contains 114 traffic-carrying bits, it is shared by two speech blocks. Each block shares two bursts with the block preceding it, and two with the block that succeeds it, as shown. In the diagram, block 5 shares the first two bursts with block 4 and the second two bursts with block 6.

Transmission - full rate speech

Each burst is transmitted in the designated timeslot of eight consecutive TDMA frames, providing the interleaving depth of eight. Table 3-7 shows how the 456 bits resulting from a 20 ms full rate speech sample are distributed over eight normal bursts.

68P02900W21-S 3-66 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Table 3-7 Distribution of 456 bits from one 20 ms full rate speech sample Distribution 0 8 16 24 32 40 ...............448 1 9 17 25 33 41 ...............449 2 10 18 26 34 42 ..............450 3 11 19 27 35 43...............451 4 12 20 28 36 44...............452 5 13 21 29 37 45................453 6 14 22 30 38 46................454 7 15 23 31 39 47................455 Burst even bits of burst N even bits of burst N + 1 even bits of burst N + 2 even bits of burst N + 3 odd bits of burst N + 4 odd bits of burst N + 5 odd bits of burst N + 6 odd bits of burst N + 7

It is important to remember that each timeslot on this carrier is occupied by a different channel combination: traffic, broadcast, dedicated or combined.

As FACCH steals speech bursts from a subscriber channel, it experiences the same kind of interleaving as the speech data that it replaces (interleaving depth = 8). The FACCH steals a 456-bit block and is interleaved with the speech. Each burst containing a FACCH block of information has the appropriate stealing flag set.

Transmission - half rate speech

For half rate speech, two independent subchannels share the same air interface timeslot. While each subchannels 20 ms speech sample is encoded and diagonally interleaved into its own 4 bursts separately, both subchannels must share the physical channel at transmission time. To do this, both subchannels alternate transmitting their associated four bursts on the air interface. Sub channel 0 transmits on the shared timeslot during the even numbered TDMA frames, while subchannel 1 transmits during the odd numbered frames. Table 3-8 shows how the 228 bits resulting from a 20 ms half-rate speech sample are distributed over eight normal bursts. Table 3-8 Distribution of 228 bits from one 20 ms half rate speech sample Distribution 0 4 8 12 16 20 .................224 2 6 10 14 18 22 ................226 1 5 9 13 17 21 ...................225 3 7 11 15 19 23 .................227 Burst even bits of burst N even bits of burst N + 1 odd bits of burst N + 2 odd bits of burst N + 3

It is important to remember that each timeslot on this carrier is occupied by a different channel combination: traffic, broadcast, dedicated or combined.

68P02900W21-S 01 Feb 2007 3-67

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

FACCH, because it steals speech bursts from a subscriber channel, experiences the same kind of interleaving as the speech data that it replaces (diagonal interleaving). However, because the FACCH contains twice as many bits as a half rate speech block, the FACCH steals the bursts from two encoded half-rate speech blocks. The FACCH steals a 456-bit block and is interleaved with the speech. Each burst containing a FACCH block of information has the appropriate stealing flag set. Because the FACCH is twice as large as the half rate speech blocks, the FACCH steals the space of two encoded and interleaved 20 ms speech samples. It occupies the even bits of the first two bursts, both the even and odd of the middle two bursts, and the odd bits of the last two bursts.

Rectangular interleaving - control

Figure 3-47 illustrates, in a simplified form, the principle of rectangular interleaving. This is applied to most control channels. Figure 3-47 Rectangular interleaving control

CONTROL BLOCKS

456 BITS

114 BITS EVEN

114 BITS

114 BITS EVEN

114 BITS ODD

ODD

BURSTS

FRAME 1

FRAME 2

FRAME 3

TDMA FRAMES
The diagram shows a sequence of control blocks after the encoding process previously described. Each block contains 456 bits, these blocks are then divided into four blocks each containing 114 bits. Each block contains bits for even or odd bit positions. The GSM burst is produced using these blocks of control.

68P02900W21-S 3-68 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Transmission - control
Each burst is transmitted in the designated timeslot of four consecutive TDMA frames, providing the interleaving depth of four. The control information is not diagonally interleaved, as are speech and data. This is because only a limited amount of control information is sent to every multiframe. If the control information was diagonally interleaved, the receiver would not be capable of decoding a control message until at least two multiframes were received. This would be too long a delay.

Diagonal interleaving - CS data

Figure 3-48 illustrates, in a simplified form, diagonal interleaving applied to a 9.6 kbit/s data channel. The diagram shows a sequence of data blocks after the encoding process previously described, all from the same subscriber. Each block contains 456 bits, these blocks are divided into four blocks each containing 114 bits. These blocks are then interleaved together. The first 6 bits from the first block are placed in the first burst. The first 6 bits from the second block is placed in the second burst and so on. Each 114-bit block is spread across 19 bursts and the total 456 block is spread across 22 bursts. Data channels have an interleaving depth of 22, although this is sometimes also referred to as an interleaving depth of 19.

Transmission - CS data
The data bits are spread over a large number of bursts, to ensure that the data is protected. Therefore, if a burst is lost, only a small amount of data from one data block is actually lost. Due to the error protection mechanisms used, the lost data has a higher chance of being reproduced at the receiver. This wide interleaving depth, although providing a high resilience to error, does introduce a time delay in the transmission of the data. If data transmission is slightly delayed, it does not effect the reception quality, whereas with speech, if a delay was introduced this could be detected by the subscriber. This is why speech uses a shorter interleaving depth. Figure 3-48 shows a diagrammatic representation of diagonal interleaving for CS data.

68P02900W21-S 01 Feb 2007 3-69

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Figure 3-48 Diagonal interleaving - CS data

DATA BLOCKS

456 BITS

114 BITS

114 BITS

114 BITS

114 BITS

114

114

114

114

FIRST 6 BITS

FIRST 6 BITS

FIRST 6 BITS

FIRST 6 BITS

LAST 6 BITS

LAST 6 BITS

LAST 6 BITS

LAST 6 BITS

10

11

12

13

14

15

16

17

18

19

20

21

22

GPRS channel coding schemes

Four different coding schemes have been defined for GPRS: CS1 CS2 CS3 CS4

The mother code used is a half-rate convolutional coder applied to CS1 to CS3 followed by puncturing (CS2 and CS3) leading to various effective code rates. Coding is not applied to CS4.The following applies to all four coding schemes: User data (RLC data block, segmented LLC PDUs) and RLC/MAC header are coded together. Coded bits are block interleaved over four bursts. Eight stealing bits (SB) are used to signal which coding scheme is used for transmission of a block.

These are described in the following sections.

68P02900W21-S 3-70 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Channel coding scheme 1 (CS1)

CS1 is the most robust coding scheme of the four GPRS coding schemes. Figure 3-49 shows the encoding of the user data (160 bits RLC data block, segmented LLC PDUs) and the RLC/MAC header (24 bits) for downlink. In the first stage of coding, these 184 bits are protected according to Fire code using extra 40 bits (BCS) for error detection (used in ARQ). The subsequent 224 bits are then convolutionally coded followed by interleaving over four bursts. CS1 provides a user data rate (excluding RLC/MAC header) of 8 kbits/s. Figure 3-49 GPRS channel coding scheme 1 (CS1)
3 bits USF 21 bits RLC/MAC Header Data Block coded 4 bits 224 bits Rate 1/2 convolutional coding TB 160 bits 40 bits BCS

465 bits Puncturing

465 bits

Block interleaving over 4 bursts

114 bits

114 bits

114 bits

114 bits

Mapped to 4 TDMA bursts; coding scheme signalled through 8 stealing bits (2 per burst) TB 3 bits Header & data 57 bits SB 1 bit TS SB Header & data 57 bits TB 3 bits

26 bits 1 bit

68P02900W21-S 01 Feb 2007 3-71

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Channel coding scheme 2 (CS2)

CS2 is less robust than CS1 at the expense of providing higher user data rate. Figure 3-50 shows the encoding of the user data (240 bits RLC data block, segmented LLC PDUs) and the RLC/MAC header (34 bits) for downlink. The USF bits (3) are pre-coded to provide additional protection. In the first stage of coding, these 274 bits are protected according to Fire code using extra 16 bits (BCS) for error detection (used in ARQ). The subsequent 290 bits are then convolutionally coded, punctured, and interleaved over four bursts. CS2 provides a user data rate (excluding RLC/MAC header) of 12 kbits/s. Figure 3-50 GPRS channel coding scheme 2 (CS2)
6 bits (pre-coded) USF

28 bits Data Block coded

240 bits

16 bits BCS

RLC/MAC Header

4 bits 290 bits Rate 1/2 convolutional coding TB

588 bits Puncturing

546 bits

Block interleaving over 4 bursts

114 bits

114 bits

114 bits

114 bits

Mapped to 4 TDMA bursts; coding scheme signalled through 8 stealing bits (2 per burst) TB 3 bits Header & data 57 bits SB 1 bit TS SB Header & data 57 bits TB 3 bits

26 bits 1 bit

68P02900W21-S 3-72 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Channel coding scheme 3 (CS3)

CS3 is less robust than CS1 and CS2 at the expense of providing higher user data rate. Figure 3-51 shows the encoding of the user data (288 bits RLC data block, segmented LLC PDUs) and the RLC/MAC header (30 bits) for downlink. The USF bits (3) are pre-coded to provide additional protection. In the first stage of coding, these 318 bits are protected according to the Fire code using extra 16 bits for (BCS) for error detection (used in ARQ). The subsequent 334 bits are then convolutionally coded, punctured, and interleaved over four bursts. CS3 provides a user data rate (excluding RLC/MAC header) of 14.4 kbits/s. Figure 3-51 GPRS channel coding scheme 3 (CS3)
6 bits (pre-coded) USF

24 bits Data Block coded

288 bits

16 bits BCS

RLC/MAC Header

4 bits 344 bits Rate 1/2 convolutional coding TB

676 bits Puncturing

456 bits

Block interleaving over 4 bursts

114 bits

114 bits

114 bits

114 bits

Mapped to 4 TDMA bursts; coding scheme signalled through 8 stealing bits (2 per burst) TB 3 bits Header & data 57 bits SB 1 bit TS SB Header & data 57 bits TB 3 bits

26 bits 1 bit

68P02900W21-S 01 Feb 2007 3-73

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Channel coding scheme 4 (CS4)

CS4 is the least robust GPRS coding scheme and it has no FEC capability. Figure 3-52 shows the encoding of the user data (400 bits RLC data block, segmented LLC PDUs) and the RLC/MAC header (40 bits) for downlink. The USF bits (3) are pre-coded to provide additional protection. These 440 bits are protected according to Fire code using extra 16 bits (BCS) for error detection (used in ARQ). The subsequent 456 bits are then interleaved (no convolutionally coding) over four bursts. CS4 provides a user data rate (excluding RLC/MAC header) of 20 kbits/s. Figure 3-52 GPRS channel coding scheme 4 (CS4)
12 bits (pre-coded) USF

28 bits Data Block coded

400 bits

16 bits BCS

RLC/MAC Header

456 bits (0 bits TB) No convolutional coding

456 bits No puncturing

456 bits

Block interleaving over 4 bursts

114 bits

114 bits

114 bits

114 bits

Mapped to 4 TDMA bursts; coding scheme signalled through 8 stealing bits (2 per burst) TB 3 bits Header & data 57 bits SB 1 bit TS SB Header & data 57 bits TB 3 bits

26 bits 1 bit

All control channels except for the PRACH use CS1. Two types of packet random access burst are transmitted on the PRACH: an 8 information bits random access burst, or an 11-information bits random access burst (called the extended packet random access burst). The mobile must support both random access burst types. GPRS traffic channels use scheme CS1, CS2, CS3, or CS4. This allows the coding scheme to be dynamically adapted to the channel conditions and thereby maximizing throughput and optimizing the performance.

68P02900W21-S 3-74 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Coding schemes CS3 and CS4 are not used before GSR5.1. USF is the Uplink State Flag, which is transmitted on the downlink and is an invitation to an MS to transmit. The BCS is Block Check Sequence, which is used for the detection of errors and subsequent Automatic Repeat Request (ARQ). Table 3-9 summarizes the coding parameters for the GPRS coding schemes. Table 3-9 Coding parameters for GPRS coding schemes Coding scheme CS1 Effective Code rate after 1/2 convolutional coding and puncturing USF Pre-coded USF RLC/MAC header/bits User bits (RLC blocks; segmented LLC PDUCs) BCS Tail Coded bits Punctured bits User Data rate at RLC/MAC kbit/s 1/2 CS2 2/3 CS3 3/4 CS4 1

3 3 21 181

3 6 28 268

3 6 24 312

3 12 28 428

40 4 456 0 8

16 4 588 132 12

16 4 676 220 14.4

16 456 0 20

16/32 kbit/s TRAU

In the BSS architecture, the link, which the GPRS data traverses from the channel coders in the BTS to the PCU, is currently implemented using 16 kbit/s TRAU-like links. These links are carried over subrate switched E1 timeslots, which have some signaling included to ensure the link is synchronized between the channel coders and the PCU. However, Table 3-9 shows that there is not enough bandwidth available on a 16 kbit/s link to carry CS3 and CS4, therefore the 32 kbit/s TRAU is required. The method used is to combine two component 16 kbit/s TRAU channels to create a 32 kbit/s TRAU channel. The two 16 kbit/s channels are referred to as the left and right channels. The left channel is the primary channel, which is currently used for all GPRS traffic. The right (or auxiliary) channel is used for the larger CS3 and CS4 GPRS TRAU-like frames.

68P02900W21-S 01 Feb 2007 3-75

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Only one 16 kbit/s timeslot (CIC) is used between the BSC and RXCDR for a CS call, therefore termination is necessary.

EGPRS channel coding schemes

Nine different coding schemes have been defined for EGPRS, MCS-1 to MCS-9. MCS-1 to MCS-4 coding schemes use GMSK and MCS-5 to MCS-9 coding schemes use 8-PSK. The mother code used is a 1/3 rate convolutional coder applied to all the coding schemes followed by various puncturing schemes leading to various effective code rates. The following apply to all nine coding schemes: User data (RLC data block, segmented LLC PDUs), RLC/MAC header and the USF bits are coded independently. The USF bits (3) are block coded, resulting in 12 bits and 36 bits for GMSK and 8-PSK coding schemes respectively. In case of MCS-1 to MCS-4, USF block coding is identical to CS-4. This facilitates multiplexing of GPRS and EGPRS on the same timeslot (GPRS mobiles must be able to detect USF sent by EGPRS GMSK block). The mother code used is 1/3 rate convolutional encoder. There are three different RLC/MAC header types used, which contain information about the coding and puncturing scheme, used for a block. Header type 1 is used for MCS-7 to MCS-9, header type 2 is used for MCS-5 and MCS-6, and header type 3 is used for MCS-1 to MCS-4. Eight stealing bits (SBs) are used to signal which header type should be used to extract various information. Coding schemes MCS-7 to MCS-9 are interleaved over two bursts and coding schemes MCS-1 to MCS-6 are interleaved over four bursts. Two or three puncturing schemes per coding scheme are used enabling Incremental Redundancy (IR); the code combining process of radio blocks in error thus providing additional coding gain, particularly for higher code rates. There are three code families, A, B, and C. The code families facilitate re-segmentation of erroneous radio blocks into more robust coding schemes for re-transmission. Coding schemes MCS-1 and 4 are in family C, MCS-2, 5 and 7 are in family B, and MCS-3, 6, 8 and 9 are in family A.

Hybrid ARQ type I is not supported. These are described in the following sections.

68P02900W21-S 3-76 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Channel coding scheme MCS-1

MCS1 is the most robust coding scheme of the four EGPRS GMSK modulated coding schemes. Figure 3-53 shows the encoding of the user data (176 bits RLC data block, segmented LLC PDUs), the RLC/MAC header (28 bits, header type 3) for downlink. Extra 12 bits (BCS) for error detection (used in ARQ) protect the user data. The subsequent 196 bits (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over four bursts. Extra 8 bits (HCS) for error detection protect the header data. The subsequent 36 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS1 provides a user data rate (excluding RLC/MAC header) of 8.8 kbits/s. Figure 3-53 EGPRS channel coding scheme 1 (MCS-1)
196 bits 3 bits USF Block coded 28 bits 8 bits 2 bits 176 bits 12 bits 6 bits BCS TB

RLC/MAC Header HCS FBI E Data

Rate 1/3 convolutional coding

12 bits

108 bits

588 bits Puncturing P1 P2 372 bits

SB = 12

12 bits

68 bits

372 bits

Burst 1

Burst 2

Burst 3

Burst 4

TB 3 bits

Header & data 57 bits

SB 1 bit

TS 26 bits

SB 1 bit

Header & data 57 bits

TB 3 bits

68P02900W21-S 01 Feb 2007 3-77

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Channel coding scheme MCS-2

MCS-2 coding scheme is less robust than MCS-1. Figure 3-54 shows the encoding of the user data (224 bits), the RLC/MAC header (28 bits, header type 3) for downlink. Extra 12 bits (BCS) for error detection (used in ARQ) protect the user data. The subsequent 244 bits (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over four bursts. Extra 8 bits (HCS) for error detection protect the header data. The subsequent 36 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS2 provides a user data rate (excluding RLC/MAC header) of 11.2 kbits/s. Figure 3-54 EGPRS channel coding scheme 2 (MCS-2)
244 bits 3 bits USF Block coded 28 bits 8 bits 2 bits 224 bits 12 bits 6 bits BCS TB

RLC/MAC Header HCS FBI E Data

Rate 1/3 convolutional coding

12 bits

108 bits

672 bits Puncturing P1 P2 372 bits

SB = 12

12 bits

68 bits

372 bits

Burst 1

Burst 2

Burst 3

Burst 4

TB 3 bits

Header & data 57 bits

SB 1 bit

TS

SB

Header & data 57 bits

TB 3 bits

26 bits 1 bit

68P02900W21-S 3-78 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Channel coding scheme MCS-3

MCS-3 coding scheme is less robust than MCS-1 and MCS-2. Figure 3-55 shows the encoding of the user data (296 bits), the RLC/MAC header (28 bits, header type 3) for downlink. Extra 12 bits (BCS) for error detection (used in ARQ) protect the user data. The subsequent 316 bits (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over four bursts. Extra 8 bits (HCS) for error detection protect the header data. The subsequent 36 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS3 provides a user data rate (excluding RLC/MAC header) of 14.8 kbits/s. Figure 3-55 EGPRS channel coding scheme 3 (MCS-3)
316 bits 3 bits USF Block coded 28 bits 8 bits 2 bits 296 bits 12 bits 6 bits BCS TB

RLC/MAC Header HCS FBI E Data

Rate 1/3 convolutional coding

12 bits

108 bits Puncturing

948 bits Puncturing P1 P2 372 bits P3 372 bits

SB = 12

12 bits

68 bits

372 bits

Burst 1

Burst 2

Burst 3

Burst 4

TB 3 bits

Header & data 57 bits

SB 1 bit

TS

SB

Header & data 57 bits

TB 3 bits

26 bits 1 bit

68P02900W21-S 01 Feb 2007 3-79

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Channel coding scheme MCS-4

MCS-4 coding scheme is the least robust GMSK modulated coding scheme; it has no FEC capability. Figure 3-56 shows the encoding of the user data (352 bits), the RLC/MAC header (28 bits, header type 3) for downlink. Extra 12 bits (BCS) for error detection (used in ARQ) protect the user data. The subsequent 372 bits (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over four bursts. Extra 8 bits (HCS) for error detection protect the header data. The subsequent 36 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS4 provides a user data rate (excluding RLC/MAC header) of 17.6 kbits/s. Figure 3-56 EGPRS channel coding scheme 4 (MCS-4)
372 bits 3 bits USF Block coded 28 bits 8 bits 2 bits 352 bits 12 bits 6 bits BCS TB

RLC/MAC Header HCS FBI E Data

Rate 1/3 convolutional coding

12 bits

108 bits Puncturing

1116 bits Puncturing P1 P2 372 bits P3 372 bits

SB = 12

12 bits

68 bits

372 bits

Burst 1

Burst 2

Burst 3

Burst 4

TB 3 bits

Header & data 57 bits

SB 1 bit

TS

SB

Header & data 57 bits

TB 3 bits

26 bits 1 bit

68P02900W21-S 3-80 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Channel coding scheme MCS-5

MCS-5 is the most robust coding scheme of the five EGPRS 8-PSK modulated coding schemes. Figure 3-57 shows the encoding of the user data (448 bits), the RLC/MAC header (25 bits, header type 2) for downlink. Extra 12 bits (BCS) for error detection (used in ARQ) protect the user data. The subsequent 468 bits (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over four bursts. Extra 8 bits (HCS) for error detection protect the header data. The subsequent 33 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS5 provides a user data rate (excluding RLC/MAC header) of 22.4 kbits/s. Figure 3-57 EGPRS channel coding scheme 5 (MCS-5)
468 bits 3 bits USF Block coded 25 bits 8 bits 2 bits 448 bits 12 bits 6 bits BCS TB

RLC/MAC Header HCS FBI E Data

Rate 1/3 convolutional coding

36 bits

99+1 spare bits No puncturing

1404 bits Puncturing P1 P2 1248 bits

SB = 8

36 bits

100 bits

1248 bits

Burst 1

Burst 2

Burst 3

Burst 4

TB 9 bits

Data 156 bits

U SB

TS 78 bits

SB U

Data 156 bits

TB 9 bits

12 5 1 bits bits bit

1 4 13 bit bitsbits

68P02900W21-S 01 Feb 2007 3-81

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Channel coding scheme MCS-6

MCS-6 coding scheme is less robust than MCS-5. Figure 3-58 shows the encoding of the user data (592 bits), the RLC/MAC header (25 bits, header type 2) for downlink. Extra 12 bits (BCS) for error detection (used in ARQ) protect the user data. The subsequent 612 bits (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over four bursts. Extra 8 bits (HCS) for error detection protect the header data. The subsequent 33 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS-6 provides a user data rate (excluding RLC/MAC header) of 29.6 kbits/s. Figure 3-58 EGPRS channel coding scheme 6 (MCS-6)
612 bits 3 bits USF Block coded 25 bits 8 bits 2 bits 592 bits 12 bits 6 bits BCS TB

RLC/MAC Header HCS FBI E Data

Rate 1/3 convolutional coding

36 bits

99+1 spare bits No puncturing

1836 bits Puncturing P1 P2 1248 bits

SB = 8

36 bits

100 bits

1248 bits

Burst 1

Burst 2

Burst 3

Burst 4

TB 9 bits

Data 156 bits

U SB

TS 78 bits

SB U

Data 156 bits

TB 9 bits

12 5 1 bits bits bit

1 4 13 bit bitsbits

68P02900W21-S 3-82 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Channel coding scheme MCS-7

MCS-7 coding scheme is less robust than MCS-5 and MCS-6. It also carries two radio blocks per 20ms. Figure 3-59 shows the encoding of the user data, which consists of two separate user data blocks, 448 bits each, the RLC/MAC header (37 bits, header type 1) for downlink. Extra 12 bits (BCS) for error detection (used in ARQ) protect each user data block. The subsequent 468 bits per radio block (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over two bursts. Extra 8 bits (HCS) for error detection protect the header data. The subsequent 45 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS-7 provides a user data rate (excluding RLC/MAC header) of 44.8 kbits/s. Figure 3-59 EGPRS channel coding scheme 7 (MCS-7)
468 bits 3 bits USF Block coded 37 bits 8 bits 2 bits 448 bits 12 6 bits bits 2 bits 448 bits 12 6 bits bits BCS TB

RLC/MAC HCS FBI E Data Header

BCS TB FBI E Data

Rate 1/3 convolutional coding

36 bits

135 bits Puncturing

1404 bits Puncturing

1404 bits Puncturing

P1 SB = 8 36 bits 124 bits

P2

P3

P1

P2

P3

612 bits 612 bits 612 bits 612 bits 612 bits 612 bits

Burst 1

Burst 2

Burst 3

Burst 4

TB 9 bits

Data 153 bits

U SB

TS 78 bits

SB U

Data 153 bits

TB 9 bits

15 5 1 bits bits bit

1 4 16 bit bitsbits

68P02900W21-S 01 Feb 2007 3-83

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Channel coding scheme MCS-8

MCS-8 coding scheme carries two user data blocks like MCS-7. Figure 3-60 shows the encoding of the two user data blocks, 544 bits each, the RLC/MAC header (37 bits, header type 1) for downlink. Extra 12 bits (BCS) for error detection (used in ARQ) protect each user data block. The subsequent 564 bits per radio block (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over two bursts. Extra 8 bits (HCS) for error detection protect the header data. The subsequent 45 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS-8 provides a user data rate (excluding RLC/MAC header) of 54.4 kbits/s. Figure 3-60 EGPRS channel coding scheme 8 (MCS-8)
564 bits 3 bits USF Block coded 37 bits 8 bits 2 bits 544 bits 12 6 bits bits 2 bits 544 bits 12 6 bits bits BCS TB

RLC/MAC HCS FBI E Data Header

BCS TB FBI E Data

Rate 1/3 convolutional coding

36 bits

135 bits Puncturing

1692 bits Puncturing

1692 bits Puncturing

P1 SB = 8 36 bits 124 bits

P2

P3

P1

P2

P3

612 bits 612 bits 612 bits 612 bits 612 bits 612 bits

Burst 1

Burst 2

Burst 3

Burst 4

TB 9 bits

Data 153 bits

U SB

TS 78 bits

SB U

Data 153 bits

TB 9 bits

15 5 1 bits bits bit

1 4 16 bit bitsbits

68P02900W21-S 3-84 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Channel coding scheme MCS-9

MCS-9 coding scheme carries two user data blocks like MCS-7 and 8. Figure 3-61 shows the encoding of the MCS-9 two user data blocks, 592 bits each, the RLC/MAC header (37 bits, header type 1) for downlink. Extra 12 bits (BCS) for error detection (used in ARQ) protect each user data block. The subsequent 612 bits per radio block (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over two bursts. The puncturing results in MCS-9 with having no FEC protection. Extra 8 bits (HCS) for error detection protect the header data. The subsequent 45 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS-9 provides a user data rate (excluding RLC/MAC header) of 59.2 kbits/s. Figure 3-61 EGPRS channel coding scheme 9 (MCS-9)
612 bits 3 bits USF Block coded 37 bits 8 bits 2 bits 592 bits 12 6 bits bits 2 bits 592 bits 12 6 bits bits BCS TB

RLC/MAC HCS FBI E Data Header

BCS TB FBI E Data

Rate 1/3 convolutional coding

36 bits

135 bits Puncturing

1836 bits Puncturing

1836 bits Puncturing

P1 SB = 8 36 bits 124 bits

P2

P3

P1

P2

P3 612 bits

612 bits 612 bits 612 bits 612 bits 612 bits

Burst 1

Burst 2

Burst 3

Burst 4

TB 9 bits

Data 153 bits

U SB

TS 78 bits

SB U

Data 153 bits

TB 9 bits

15 5 1 bits bits bit

1 4 16 bit bitsbits

68P02900W21-S 01 Feb 2007 3-85

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

EGPRS traffic channels use coding schemes MCS-1 to MCS-9. This allows the coding scheme to be dynamically adapted to the channel conditions like GPRS through the Link Adaptation (LA) process (see Link Adaptation in GPRS/EGPRS ) and thereby maximizing throughput and optimizing the performance. The IR feature of EGPRS also allows the LA process to be more aggressive in terms of BLER on the first transmissions and thereby increasing the utilization of higher code rates over a larger percentage of a cell. Table 3-10 summarizes the coding parameters for the EGPRS coding schemes. Table 3-10 Coding parameters for EGPRS coding schemes Coding scheme: MCS-n 9 Effective Code rate after 1/2 convolutional coding and puncturing Effective Header Code rate after 1/2 convolutional coding and puncturing Modulation RLC blocks per Radio Block (20ms) Raw Data within one Radio Block Family BCS Tail payload HCS User Data rate at RLC/MAC kb/s 59.2 54.4 44.8 29.6 2 2x592 A 2 2x544 A 2x12 2x6 8 22.4 17.6 14.8 11.2 8.8 1.0 8 0.92 7 0.76 6 0.49 5 0.37 4 1.0 3 0.85 2 0.66 1 0.53

0.36

0.36

0.36

1/3

1/3

0.53

0.53

0.53

0.53

8-PSK 2 2x448 B 1 592 A 1 448 B 1 352 C 12 6 1

GMSK 1 224 B 1 176 C

296 A

64 kbit/s TRAU for EGPRS

In the BSS architecture, the link, which the EGPRS data traverses from the channel coders in the BTS to the PCU, is currently implemented using 16 kbit/s TRAU-like links. These links are carried over subrate switched E1 timeslots, which have some signaling included to ensure the link is synchronized between the channel coders and the PCU. In case of GPRS, 32 kbits/s TRAU is used to carry CS3 and CS4. In case of EGPRS, Table 3-10 shows that there is not enough bandwidth available on a 32 kbit/s link to carry MCS7 to 9, therefore VersaTRAU frame formats are used to statistically multiplex the data for each air timeslot configured as a PDTCH on the RTF backhaul available for use as Versachannel.

68P02900W21-S 3-86 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

For EGPRS, any enabled carrier has a certain amount (ranging from 3 to 8 DS0s) of terrestrial backhaul configured and a portion of this backhaul is used as the Versachannel to carry the data for the air timeslots configured as PDTCHs. The EGPRS feature needs additional backhaul to provision EGPRS carriers. The additional backhaul is either 7 DS0s to implement EGPRS on a BCCH carrier or 8 DS0s to implement EGPRS on a non-BCCH carrier, if VersaTRAU feature is restricted. If VersaTRAU feature is unrestricted, the backhaul for an EGPRS carrier can be configured using the rtf_ds0_count parameter.

Link adaptation (LA) in GPRS/EGPRS

The Link Adaptation (LA) process is used to improve the throughput of users and system by adapting the highest coding scheme to the prevailing radio channel condition. The development of LA algorithm is generally based on maximizing user or system throughput, under the constraint of keeping the systems operating BLER within an acceptable bound. This ensures that the overall throughput performance is not degraded due to the operation of higher layers protocols. The implementation of LA is manufacturer dependant and is also mandatory. The standards provide sufficient information and guidelines to facilitate the development of proprietary algorithms. This is achieved through specific information elements in the various header and control messages communicated between the BTS and MS. In addition, there are various measurement reports produced by the MS that can be used as inputs to the LA process. The actual implementation is generally based on guidelines provided by the standards and the boundaries specified in the standards. The LA impact in improving the system performance is greater in EGPRS compared to GPRS due to: Higher number of codes, that is, better granularity. Richer MS measurement reports. Incremental redundancy (Hybrid ARQ type II).

The LA process uses the measurement reports as inputs to move between various codes per packet downlink Ack/Nack period. In Motorolas implementation, a code change is applied to all the blocks and timeslots. In addition, IR is the only mode used in EGPRS, and appropriate measures are taken to comply with the constraints specified in the standards.

Voice activity detection (VAD)

VAD is a mechanism whereby the source transmitter equipment identifies the presence or absence of speech. VAD implementation is affected in speech mode by encoding the speech pattern silences at a rate of 500 bit/s rather than the full 13 kbit/s. This results in a data transmission rate for background noise, known as comfort noise, which is regenerated in the receiver. Without the comfort noise, the total silence between the speech would be considered to be disturbing by the listener.

68P02900W21-S 01 Feb 2007 3-87

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Discontinuous transmission (DTX)

DTX overview
DTX increases the efficiency of the system through a decrease in the possible radio transmission interference level. It does this by ensuring that the MS and BTS do not transmit unnecessary message data (that is background noise when the user is not speaking). Instead, background noise information is measured and periodically transmitted to the other user, where it is played back to generate an agreeable sounding comfort noise. DTX can be implemented, as necessary, on a call-by-call basis. The effects are most noticeable in communications between two MSs. DTX in its most extreme form, when implemented at the MS can also result in considerable power saving. If the MS does not often transmit during silences there is a reduction in the overall power output requirement. The implementation of DTX is much at the discretion of the network provider and there are different specifications applied for different types of channel usage.

DTX and full rate or enhanced full rate

DTX is implemented over a SACCH multiframe (480 ms), as illustrated in Figure 3-62. During this time, of the possible 104 frames, only the 4 SACCH frames and 8 Silence Descriptor (SID) frames are transmitted. Figure 3-62 SACCH multiframe (480 ms) for DTX and full rate
26 FRAME MULTIFRAME 52-59

S A C C H 0

S A C C H

SID

S A C C H

S A C C H 103 SID

4 x SACCH 26 FRAME MULTIFRAMES (120 ms) 8 x SILENCE DESCRIPTOR (SID)

DTX and GSM half rate

DTX is implemented over a SACCH multiframe (480 ms), as illustrated in Figure 3-63 for each subchannel. During this time, of the possible 104 frames, only the 4 SACCH frames and 8 Silence Descriptor (SID) frames per sub-channel are transmitted.

68P02900W21-S 3-88 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

Figure 3-63 SACCH multiframe (480 ms) for DTX and half rate

DTX and AMR full rate or half rate

Four types of DTX blocks exist for AMR channels. These blocks are transferred between the speech coder and the channel coder. For example, in downlink DTX, these blocks would be sent from the TRAU to the channel coder in the same 320-bit frames as that used for 20 ms speech frames. SID_FIRST: Indicates end of speech period and the start of a silence (no transmission) period. SID_UPDATE: Conveys silence descriptor information periodically during a silence period. The receiver to generate comfort noise for the listener during the silence period uses this. NO_DATA: Non-transmitted block during a silence period. ONSET: Indicates end of silence period and the start of a speech period.

Unlike full rate or Enhanced full rate DTX, AMR DTX is not designed with fixed TDMA frames of transmission during the SACCH multiframe. The four SACCH bursts are always transmitted during the SACCH TDMA frames. However, transmission during a silence period adheres to the following sequence: One SID_FIRST DTX block is transmitted after the last speech block of the speech period. It is interleaved immediately following the last encoded speech block. Two NO_DATA DTX blocks elapse over the next two periods where encoded speech blocks would normally be transmitted. One SID_UPDATE DTX block is transmitted. The SID UPDATE block is encoded and rectangularly interleaved over 4 TDMA frames.

68P02900W21-S 01 Feb 2007 3-89

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

Seven NO_DATA DTX blocks elapse over the next seven periods where encoded speech blocks would normally be transmitted. The one SID_UPDATE and seven NO_DATA sequence repeat for as long as the silence period lasts. One ONSET DTX block is transmitted immediately before the first speech block of the new speech period is sent. This ONSET is interleaved immediately before the first encoded speech block.

An ONSET can occur any time after a SID_FIRST DTX block, depending on how long the silence period lasts. Thus, for example, no SID_UPDATES would be transmitted if the silence period did not last long enough for the two NO_DATA periods to elapse.

For AMR channels, silence descriptor information (SID_UPDATE blocks) are transmitted every 8-speech blocks compared to every 24 for full rate and Enhanced full rate channels. Silence information is more frequently updated for AMR channels, thereby providing a more accurate representation of comfort noise to the user. All four AMR DTX frames contain InBand signaling bits to allow link adaptation to be performed during silence periods (refer to Link adaptation for AMR channels for further details).

Receive diversity
In its simplest case, multipath fading arises from destructive interference between two transmission paths. The deepest instantaneous fade occurring at the frequency for which the effective path length difference is an odd multiple of half wavelengths. If two receive antennas are mounted a defined distance apart, then it follows that the probability of them simultaneously experiencing maximum fade depth at a given frequency is much less than for the single antenna situation. There are three ways of utilizing this concept: The receiver can be switched between the two RF receive paths provided with two antennas. The RF signals from two receive paths can be phase aligned and summed. The phasing can be made so as to minimize the distortion arising from the multipath transmission.

Each of the methods has advantages and disadvantages. In the case of the switched configuration, it simply selects the better of the two RF signals, which is switched through to the receiver circuitry. Phase alignment has the advantage of being a continuously optimized arrangement in terms of signal level, but phase alignment diversity does not minimize distortion. The Motorola transceivers use this diversity concept. The distortion minimizing approach, whilst being an attractive concept, has not yet been implemented in a form that works over the full fading range capabilities of the receivers and therefore has to switch back to phase alignment at low signal levels. This means a rather complex control system is required. It must be emphasized that diversity does not usually have any significant effect on the mean depression component of fading, but the use of phase alignment diversity can help increase the mean signal level received.

68P02900W21-S 3-90 01 Feb 2007

System Information: BSS Equipment Planning

Overcoming adverse propagation effects

In microcellular applications, the M-Cellcity and Horizonmicro or Horizonmicro2 do not support spatial diversity. Figure 3-64 Receive diversity
MOBILE

ANTENNAS (approx 10 wavelengths) SPACE BETWEEN

PATH LENGTH IN WAVELENGTHS

METHODS OF UTILIZATION: a. SWITCHED. b. PHASE ALIGNED AND SUMMED. c. PHASE ALIGNED WITH MINIMUM DISTORTION.

BTS

Equalization
As mentioned in multipath fading, in most urban areas the only signals received are multipath. If nothing was done to try and counter the effects of Inter Symbol Interference (ISI) caused by the time dispersed signals, the Bit Error Rate (BER) of the demodulated signal would be far too high, giving a poor quality signal, unacceptable to the subscriber. To counter this, a digital signal-processing algorithm called an equalizer is built into the receiver. The equalizer uses a known bit pattern inserted into every burst transmitted, called the training sequence code. This allows the equalizer to assess and modify the effects of the multipath component, resulting in a far cleaner, less distorted signal. Without this equalizer, the quality of the received signal would be unacceptable for the majority of the time.

Training sequence code

The training sequence code (see Figure 3-65) is used so that the demodulator can estimate the most probable sequence of modulated data. As the training sequence is a known pattern, this enables the receiver to estimate the distortion ISI on the signal due to propagation effects, especially multipath reception. The receiver must be able to cope with two multipaths of equal power received at an interval of up to 16 microseconds. If the two multipaths are 16 microseconds delayed then this would be approximately equivalent to 5-bit periods. There are 32 combinations possible when two 5-bit binary signals are combined. As the transmitted training sequence is known at the receiver, it is possible to compare the actual multipath signal received with all 32 possible combinations reproduced in the receiver. From this comparison, the most likely combination can be selected and the filters set to remove the multipath element from the received signal.

68P02900W21-S 01 Feb 2007 3-91

Overcoming adverse propagation effects

Chapter 3: BSS cell planning

The multipath element can be of benefit once it has been identified, as it can then be recombined with the wanted signal in a constructive way to give a greater received signal strength. Once the filters have been set, they can be used to filter the random speech data as it is assumed they have suffered from the same multipath interference as the training sequence code. The multipath delay is calculated on a burst-by-burst basis, as it is constantly changing. Figure 3-65 Training sequence code
Signal from shortest path

3 bits

Signal from delayed path

68P02900W21-S 3-92 01 Feb 2007

System Information: BSS Equipment Planning

Subscriber environment

Subscriber environment
Subscriber hardware
System quality (voice quality, for example), system access, and grade of service, as perceived by the customer, are the most significant factors in the success of a cellular network. The everyday subscriber neither knows nor really cares about the high level of technology incorporated into a cellular network. However, they do care about the quality of their calls. What the network designer must remember is that it is the subscriber who selects the type of equipment they wish to use on the network. It is up to the network provider to satisfy the subscriber, whatever they choose. The output power of the mobile subscriber is limited in a GSM system to a maximum of 8 W for a mobile and a minimum of 0.8 W for a hand portable. For a DCS1800 system, the mobile subscriber is restricted to a maximum of 1 W and a minimum of 250 mW hand portable.

Environment
Not only does the network designer have to plan for the subscribers choice of phone, the designer has to plan for the choice of subscribers as to where they wish to use that phone. When only the mobile unit was available, system coverage and hence subscriber use was limited to on street, high-density urban or low capacity rural coverage areas. During the early stages of cellular system implementation, the major concern was trying to provide system coverage inside tunnels. However, with the advances in technology the hand portable subscriber unit is now firmly established. With this introduction came new problems for the network designer. The portable subscriber unit provides the user far more freedom of use but the subscriber still expected exactly the same service. The subscriber now wants quality service from the system at any location. This location can be on a street or any floor of a building whether it is the basement or the penthouse and even in lifts (see Figure 3-66). Thus, greater freedom of use for the subscriber gives the network designer even greater problems when designing and implementing a cellular system.

68P02900W21-S 01 Feb 2007 3-93

Subscriber environment

Chapter 3: BSS cell planning

Figure 3-66 Subscriber environment

URBAN/CITY ENVIRONMENTS

RURAL AREAS

BUILDINGS

LIFTS

TUNNELS

Distribution
Not only do network designers have to identify the types of subscriber that use the cellular network now and in the future, but also at what location these subscribers are attempting to use their phones. Dense urban environments need an entirely different design approach, due to considerations mentioned earlier in this chapter, than the approach used to design coverage for a sparsely populated rural environment. Road and rail networks have subscribers moving at high speed, so this must be accounted for when planning the interaction between network entities whilst the subscriber is using the network. Even in urban areas, the network designer must be aware that traffic is not necessarily evenly distributed. As Figure 3-67 illustrates, an urban area can contain sub-areas of uneven distribution such as a business or industrial district, and has to plan for a seasonal increase of traffic due to, for example, a convention centre. It is vitally important that the traffic distribution is known and understood before network design, to ensure that a successful quality network is implemented.

68P02900W21-S 3-94 01 Feb 2007

System Information: BSS Equipment Planning

Subscriber environment

Figure 3-67 Subscriber distribution

HIGH SPEED MOBILES (RAILWAYS)

RURAL

URBAN

BUSINESS AREAS 40% ROAD/RAIL NETWORK EXHIBITIONS INDUSTRIAL 20% RESIDENTIAL 30% 10%

SUBSCRIBERS DISTRIBUTION CHANGES ON A HOURLY BASIS

Hand portable subscribers

The network designer must ensure that the network is designed to ensure a quality service for the most demanding subscriber. This is the hand portable subscriber. The hand portable now represents the vast majority of all new subscriber units introduced into cellular networks. So clearly the network users, and hence the network designers, must recognize this. Before commencing the network design based around hand portable coverage, the network designer must first understand the limitations of the hand portable unit and secondly, what the hand portable actually needs from the network. The hand portable phone is a small lightweight unit, which is easy to carry and has the ability to be used from any location. The ability of the unit to be used at any location means that the network must be designed with the provision of good in-building coverage as an essential element. The hand portable units have a low output power. For example: 0.8W to 8W (GMSK) and 0.2W to 2W (8-PSK) for GSM900. 0.25W to 1W (GMSK) and 0.107W to 1W (8-PSK) for DCS1800.

Therefore, the distance at which these units can be used from a cell is constrained by RF propagation limitations. For practical purposes, the actual transmit power of the hand portable should be kept as low as possible during operation. This helps from not only an interference point of view, but also helps to extend the available talk time of the subscriber unit, which is limited by battery life.

68P02900W21-S 01 Feb 2007 3-95

Subscriber environment

Chapter 3: BSS cell planning

Future planning
Normal practice in network planning is to select one point of a well-known re-use model as a starting point. Even at this early stage, the model must be improved because any true traffic density does not follow the homogeneous pattern assumed in any theoretical models. Small-sized heavy traffic concentrations are characteristic of the real traffic distributions. Another wellknown traffic characteristic feature is the fast descent in the density of traffic when leaving city areas. It is uneconomical to build the whole network using a standard cell size; it becomes necessary to use cells of varying sizes. Connecting areas with different cell sizes brings about new problems. In principle, it is possible to use cells of different size side-by-side, but without careful consideration, this leads to a wasteful frequency plan. This is because the re-use distance of larger cells is greater than that of smaller cells. The situation is often that the borders are so close to the high-density areas that the longer re-use distances mean decreased capacity. Another solution, offering better frequency efficiency, is to enlarge the cell size gradually from small cells into larger cells. In most cases, the traffic concentrations are so close to each other that the expansion cannot be completed before it is time to start approaching the next concentration, by gradually decreasing the cell size. This is why the practical network is not a regular cluster composition, but a group of directional cells of varying size. Besides this need for cells of different size, the unevenness of the traffic distribution also causes problems in frequency planning. Theoretical frequency division methods applicable to homogenous clusters cannot be used. It is quite rare that two or more neighboring cells need the same amount of channels. It must always be kept in mind that the values calculated for future traffic distribution are only crude estimates and that the real traffic distribution always deviates from these estimates. In consequence, the network plan should be flexible enough to allow for rearrangement of the network to meet the real traffic needs.

Conclusion
In conclusion, there are no fixed rules for radio network planning. It is a case of experimenting and reiterating. By comparing different alternatives, the network designers should find a plan that both fulfils the given requirements and keeps within practical limitations. When making network plans, the designers should always remember that every location in a network has its own conditions, and all local problems must be tackled and solved on an individual basis.

68P02900W21-S 3-96 01 Feb 2007

System Information: BSS Equipment Planning

Microcellular solution

Microcellular solution
Layered architecture
The basic term layered architecture is used in the microcellular context to explain how macrocells overlay microcells. It is worth noting that when talking of the traffic capacity of a microcell it is additional capacity to that of the macrocell in the areas of microcellular coverage. The traditional cell architecture design, Figure 3-68, ensures that, as far as possible, the cell gives almost total coverage for all the MSs within its area. Figure 3-68 Layered architecture

MACROCELL

MICROCELL A

MICROCELL B

TOP VIEW

SIDE VIEW

MACROCELL

MICROCELL A

MICROCELL B

Combined cell architecture

A combined cell architecture system, as illustrated in Figure 3-69, is a multi-layer system of macrocells and microcells. The simplest implementation contains two layers. The bulk of the capacity in a combined cell architecture is provided by the microcells. Combined cell systems can be implemented into other vendor networks.

68P02900W21-S 01 Feb 2007 3-97

Microcellular solution

Chapter 3: BSS cell planning

Figure 3-69 Combined cell architecture

UNDERLAYED MICROCELL (COULD BE A DIFFERENT VENDOR)

CONTIGUOUS COVERAGE OVER AREAS OF HIGH SLOW MOVING TRAFFIC DENSITY OVERLAYED MACROCELLS

Macrocells: Implemented specifically to cater to the fast-moving MSs and to provide a fallback service for coverage of holes and pockets of interference in the microcell layer. Macrocells form an umbrella over the smaller microcells. Microcells: Microcells handle the traffic from slow-moving MSs. The microcells can give contiguous coverage over the required areas of heavy subscriber traffic.

Combined cell architecture structure

A combined cell architecture employs cells of different sizes overlaid to provide contiguous coverage. This structure is shown in Figure 3-70.

68P02900W21-S 3-98 01 Feb 2007

System Information: BSS Equipment Planning

Microcellular solution

Figure 3-70 Combined cell architecture structure

LINK TO IMPLEMENT MICROCELLS AS A SEPARATE SYSTEM ALTERNATIVE SYSTEM (MICROCELLS CONTROLLED BY THE SAME BSC AS MACROCELLS)

MSC BSC A

SYSTEM 2 MICROCELL

BSC B SYSTEM 1 MACROCELL BTS 1 BTS 2 BTS 5

BTS 3

BTS 4 MICROCELL COVERAGE

MACROCELL COVERAGE

SYSTEM 1 = OVERLAY SYSTEM SYSTEM 2 = UNDERLAY SYSTEM

Macrocell and microcell networks are operated as individual systems. The macrocell network is more dominant as it handles the greater amount of traffic. Microcells can be underlayed into existing networks.

Expansion solution
As the GSM network evolves and matures, its traffic loading increases as the number of subscribers grow. Eventually a network reaches a point of traffic saturation. The use of microcells can provide high traffic capacity in localized areas. The expansion of a BTS site past its original designed capacity can be a costly exercise and the frequency re-use implications require to be planned carefully (co-channel and adjacent channel interference). The use of microcells can alleviate the increase in congestion; the microcells could be stand-alone cells to cover traffic hotspots or a contiguous cover of cells in a combined architecture. The increased coverage gives greater customer satisfaction.

68P02900W21-S 01 Feb 2007 3-99

Frequency planning

Chapter 3: BSS cell planning

Frequency planning
Introduction
The ultimate goal of frequency planning in a GSM network is attaining and maintaining the highest possible C/I ratio everywhere within the network coverage area. A general requirement is at least 12 dB C/I, allowing tolerance in signal fading the 9dB specification of GSM. The actual plan of a real network is a function of its operating environment (geography, RF and so on) 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.

Rules for Synthesizer Frequency Hopping (SFH)

As the BCCH carrier is not hopping, it is strongly recommended to separate bands for BCCH and TCH, as shown in Figure 3-71. Figure 3-71 Separating BCCH and TCH bands

n channels BCCH Guard Band

The benefits are as follows: Makes planning simpler. Better control of interference.

m channels TCH

If microcells are included in the frequency plan, the band usage shown in Figure 3-72 is suggested. Figure 3-72 Band usage for macrocells with microcells

Macro BCCH Micro TCH

Micro BCCH

Macro TCH (SFH)

Practical rules for TCH 1x3 re-use pattern

BCCH re-use plan: 4x3 or 5x3, depending on the bandwidth available and operating environment. Divide the dedicated band for TCH into 3 groups with an equal number of frequencies (N). These frequencies are the ARFCN equipped in the MA list of a hopping system (FHI).

68P02900W21-S 3-100 01 Feb 2007

System Information: BSS Equipment Planning

Frequency planning

Use an 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 (see planning example). The number of frequencies (N) in each group is determined by the design loading factor (or carrier-to-frequency ratio). A theoretical maximum of 50% is permitted in 1x3 SFH. Any value higher than 50% would practically result in unacceptable quality. Some commonly used loading factors (sometimes termed as fractional load factors) are 40%, 33%, 25% and so on. As a general guideline,

N=

( highest non BCCH transceivercount in a cell) (loading factor)

No more than 48 frequencies in a cell with multiple carriers with GPRS/EGPRS timeslots. Use the same HSN for sectors within the same site. Use different HSNs for different sites. This helps to randomize the co-channel interference level between the sites. Use different MAIOs to control adjacent channel interference between the sectors within a site

Mobile Allocation (MA) is the set of frequencies that the mobile or BTS is allowed to hop over. Two timeslots on the same transceiver of a cell are configured to operate on different MAs. MA is the subset of the total allocated spectrum for the GSM user and the maximum number of frequencies in a MA list is limited to 64 by GSM recommendations. Mobile Allocation Index Offset (MAIO) is an integer offset that determines which frequency within the MA is the operating frequency. If there are N frequencies in the MA list, then MAIO = {0, 1, 2, N-1}. Hopping Sequence Number (HSN) is an integer parameter that determines how the frequencies within the MA list are arranged. There are 64 HSNs 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 provides a pseudo random hopping sequence. The pseudo random pattern repeats itself after every hyperframe, which is equal to 2,715,648 (26 x 51 x 2048) TDMA frames, or about 3 hours 28 minutes and 54 seconds. Motorola defines a Frequency Hopping Indicator (FHI) that is made up of the three GSM defined parameters. Up to 4 different FHIs can be defined for a cell in a Motorola BSS and every timeslot on a transceiver can be independently assigned one of the defined FHI. MAI is an integer that points to the frequency within a MA list, where MAI = 0 and MAI = N-1 being the lowest and highest frequencies in the MA list of N frequencies. MAI is a function of the TDMA frame number (FN), HSN and MAIO of a frequency hopping system.

TCH re-use planning example

Bandwidth: 10 MHz Site configuration: Mix of 2-2-2, 3-3-3 and 4-4-4 Loading factor: 33% Environment: Multi layer (micro and macro co-exist)

The spectrum is split as shown in Figure 3-73.

68P02900W21-S 01 Feb 2007 3-101

Frequency planning

Chapter 3: BSS cell planning

Figure 3-73 Frequency split for TCH re-use planning example

8 channels

Macro BCCH Micro TCH 12 channels

Micro BCCH

Macro TCH (SFH) 27 channels

A total of 49 channels are available and the first and last one are reserved as guard bands. Thus, there are 47 usable channels. 12 channels are used in the BCCH layer with a 4x3 re-use pattern. Based on 33% loading and a 4-4-4 configuration, N is calculated as N = 3 / 0.33 = 9 hopping frequencies per cell. Thus, a total of 27 channels are required for the hopping TCH layer. The remaining 8 channels are used in the micro layer as BCCH. One of the possible frequency and parameter setting plans are outlined in Table 3-11. Table 3-11 Frequency and parameter setting plan ARFCN Sector A Sector B Sector C 21, 24, 27, 30, 33, 36, 39, 42, 45 22, 25, 28, 31, 34, 37, 40, 43, 46 23, 26, 29, 32, 35, 38, 41, 44, 47 HSN Any from {1, 2, 63} Same as Same as MAIO 0, 2, 4 1, 3, 5 0, 2, 4

The MAIO setting avoids all possible adjacent channel interference among sectors within the same site. The interference (co or adjacent channel) between sites still exists but it is reduced by the randomization effect of the different HSNs.

Practical rules for TCH 1x1 re-use pattern

1x1 is practical in rural area of low traffic density, where the average occupancy of the hopping frequencies is low. With careful planning, it can be used in high traffic areas as well. BCCH re-use 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 different HSNs to reduce interference (co and adjacent channel) between the sites. Use the same HSNs for all carriers within a site and use MAIOs to avoid adjacent and cochannel interference between the carriers. Repeated or adjacent MAIOs are not to be used within the same site to avoid co-channel and adjacent channel interference respectively. A maximum loading factor of 1/6 or 16.7% is inherent in a continuous sequence of frequency allocation. Since adjacent MAIOs are restricted, the maximum number of MAIOs permitted is:

Max MAIOs =

1 * (Total allocated channels) 2

In a 3-cell site configuration, the logical maximum loading factor is 1/6 or 16.7%.

Figure 3-74 illustrates how co-channel and adjacent channel interference can be avoided.

68P02900W21-S 3-102 01 Feb 2007

System Information: BSS Equipment Planning

Frequency planning

Figure 3-74 Avoiding co-channel and adjacent channel interference

Different MAIOs to avoid co-channel interference HSN = 1

HSN = 1

HSN = 1

Non adjacent MAIOs to avoid adjacent channel interference

Rules for BaseBand Hopping (BBH)

All the rules outlined for SFH are generally applicable to BBH. As the BCCH is in the hopping frequency list, a dedicated band separated from TCH is not essential. An example of frequency spectrum allocation is shown in Figure 3-75. Figure 3-75 BBH frequency spectrum allocation

Micro BCCH

BBH channels and micro TCH

If the ITS feature is unrestricted and enabled, the baseband hopping characteristic is restricted on the DD CTU2 DRIs of which Carrier A is EGPRS capable. These DRIs do not join the BBH even if in the database their corresponding ARFCNs are configured in the MA list. For effective utilization of the ITS feature and to maintain stability, it is recommended to use the parameter re_rtf_id to map the DD CTU2 Carrier A to 64k RTF and exclude these ARFCNs from the MA list if BBH must be applied for the cell.

68P02900W21-S 01 Feb 2007 3-103

Frequency planning

Chapter 3: BSS cell planning

{30828} CTU2D defines a new site-level parameter of asym_edge_enabled for the CTU2D asymmetric feature. The element enables or disables support of asymmetric EGPRS for CTU2D on per SITE basis. The use of this functionality needs that the system remap its internal TDM allocations resulting in the removal of BBH support for EDGE (in any mode) for the entire Site. As this only impacts Baseband hopping and does not need wholesale configuration changes, the system simply does not configure hopping systems for SD EDGE and DD EDGE. When CTU2D is configured in CAPacity mode, BTS supports the GMSK carrier Bs Baseband Hopping, that is, for BBH the system supports hopping for GMSK carriers assigned to Carrier B irrespective of the EDGE capabilities and PD support for Carrier A.

68P02900W21-S 3-104 01 Feb 2007

System Information: BSS Equipment Planning

Inter-radio access technology (2G-3G) cell reselection and handovers

Inter-radio access technology (2G-3G) cell reselection and handovers

Introduction
An optional feature is supported for handovers and cell reselection between different Radio Access Technology (RAT) networks in the circuit and packet switched domain. The RAT can be either GSM/GPRS/EDGE (2G/2.5G) or the Universal Mobile Telecommunication System (UMTS) (3G). UMTS is beyond the scope of this manual and only its handover interaction with GSM is described here. For further information on UMTS, refer to System Information: UMTS Equipment Planning, 68P02905W22.

2G-3G handover description

The 2G-3G handover feature supports handovers between different RAT networks. The RAT can be either 2G/2.5G (GSM/GPRS/EDGE) or 3G (UMTS). Current evolving 3G UMTS networks soon allows operators to provide UMTS coverage along with GSM/GPRS/EGPRS coverage in their networks. This feature enables a multi-RAT MS (a mobile station that can function in multiple Radio Access Networks RANs) to either reselect or handover between a GSM RAN(GERAN) and a UMTS Radio Access Network (UTRAN). To accomplish this, support is needed from the MS, core network elements (MSC) and GSM/UMTS network elements. The GSM BSS support for this feature includes: Cell reselection across UTRAN (UMTS FDD neighbors) and GERAN in idle mode. Handovers between 3G (UMTS-FDD) and 2G (GSM) in active mode.

Restriction
There is currently an upper limit of 32 FDD UTRAN neighbors in the GSM/GPRS system.

Implementation
The BSS Inter-RAT handover GSM function is an option that must be unrestricted by Motorola. It also needs unrestricting on site by the operator with the inter_rat_enabled parameter. With the arrival of UMTS systems, there are likely to be small UMTS coverage areas within larger GSM coverage areas. In such an environment the call would drop when a UMTS subscriber goes out of a UMTS coverage area and into a GSM coverage area. Congestion in the smaller UMTS areas could become a problem when the traffic in the UMTS coverage area is high. A GSM subscriber may wish to access a service with specific QoS characteristic (for example, high bit rate data service) that may not be supported in the GSM system. To avoid these problems the operator may wish to configure their network such that handover and cell reselection between UMTS and GSM is possible. The GSM BSS inter-RAT handover function provides a solution to these problems by allowing a multi-RAT MS to perform cell reselection and handover while between an UMTS FDD cell and a GSM cell.

68P02900W21-S 01 Feb 2007 3-105

Inter-radio access technology (2G-3G) cell reselection and handovers

Chapter 3: BSS cell planning

Impact of 2G-3G handovers on GSM system architecture

Figure 3-76 shows the system architecture for the GSM BSS inter-RAT handover feature. Figure 3-76 GSM and UMTS system nodes and interfaces
E-Interface

GSM Core Network (MSC/GSN)

Gn-Interface

UMTS Core Network (3G MSC/SGSN)

A-Interface

Gb-Interface

Iu-Cs-Interface Iu-Ps--Interface

GSM/GPRS PCU BSC Abis BTS BTS

UTRAN RNS RNC Iub Node B Iur RNS RNC Iub Node B

BSS

Um

Uu

Multi-RAT MS

System consideration
Existing 2G CoreNetwork (CN) nodes must be able to interact with the 3G CN nodes through MAP procedures defined on the E-interface between a 2G CN node and 3G CN node. The GSM BSS inter-RAT handover feature does not support: Cell reselection to UTRAN TDD neighbor cells or CDMA2000 neighbor cells. Extended measurement reporting. Enhanced measurement reporting. Blind handovers. The sending of SI2quater on extended BCCH. The BSS restricts the maximum number of UTRAN neighbors per GSM cell to 32.

68P02900W21-S 3-106 01 Feb 2007

System Information: BSS Equipment Planning

Dual Transfer Mode

Dual Transfer Mode

This optional feature enables the network to support DTM capable mobiles (subset of class A). Such mobiles are able to access packet and circuit services simultaneously. A DTM capable MS with a CS connection can make a DTM request to add a PS session. A DTM capable MS that has only a PS session should abort that session in order to establish a CS session. The trigger would be that a CS page is received or the user decides to make a CS call before the PS session has completed. Once the CS connection is established, the MS can add a PS session by making a DTM request. The following figure describes the DTM MS states. Figure 3-77 DTM MS states

DTM Timeslots planning considerations

The timeslots required for a DTM PS session, that is the PDCHs, are converted from TCH. When a DTM MS in dedicated mode requests the timeslots for the PS session, the required TCHs in the cell are converted into DTM PDCHs. This applies only when the MS is entering DTM mode, CS + PS. If a DTM capable MS requests a PS session, they are treated as a regular data user. The Database parameter Max_DTM_TS specifies the maximum number of TCH timeslots in a cell that can be converted to DTM PDTCHs in order to serve requests for DTM mode operation. The DTM mode PS sessions can be multiplexed on the same timeslot, as can DTM half rate CS sessions. DTM mode sessions need a minimum of two timeslots, one each for the CS and PS sessions. The higher class MS can support multiple PDCHs. General rule for Max_DTM_TS configuration is to consider the number of subscribers using DTM in the cell at any instant and the number of timeslots that require to be allocated to each subscriber. The number of timeslots allocated to each subscriber should be based on the capabilities of the mobile classes in the cell since the mobile class limits the number of timeslots the subscriber can use.

68P02900W21-S 01 Feb 2007 3-107

Dual Transfer Mode

Chapter 3: BSS cell planning

The probability a subscriber is in dedicated mode is given by the following equation:

R CS =

(BHCA per sub * Voice call duration )

3600
UL traffic per sub (Kbits/hour) DL traffic per sub (Kbits/hour) + Average UL rate (Kbps) Average DL rate (Kbps) 3600

The probability a subscriber is in packet transfer mode is given by the following equation:

R PS

Where the UL traffic per sub (kbits) is given by the following equation:
Percentage GPRS CS usage in total UL traffic UL traffic per sub (Kbits) = + * GPRS UL traffic per sub (Kbits/hour) Percentage EGPRS MCS usage in total UL traffic * EGPRS UL traffic per sub (Kbits/hour)

the DL traffic per sub (kbits) is given by the following equation:

Percentage GPRS CS usage in total DL traffic DL traffic per sub (Kbits) = * GPRS DL traffic per sub (Kbits/hour) + Percentage EGPRS MCS usage in total DL traffic * EGPRS DL traffic per sub (Kbits/hour)

the Average uplink rate is given by the following equation:

4 PercentageGPRS CS usage in total UL traffic* (CSn_usage_ UL * CSn_rate) * (1 BLERGPRS + n 1 = AverageUL rate_per_s ub = 9 PercentageEGPRS MCS usage in total UL traffic* (MCSn_usage _UL * MCSn_rate) * (1 BLEREGPRS n =1 ULTimeslot _ weighting

and the Average downlink rate is given by the following equation:

4 Percentage GPRS CS usage in total DL traffic* (CSn_usage_DL * CSn_rate) * (1 BLERGPRS ) + n =1 Average DL rate _ per _ sub = 9 Percentage EGPRS MCS usage in total DL traffic* (MCSn_usage_DL * MCSn_rate) * (1 BLEREGPRS ) n =1 * DLTimeslot _ weighting

The probability a DTM capable subscriber is in DTM mode is given by the following equation:
R DTM = (1 + DTM mode scaling factor ) * R

CS

* R PS

The number of subscribers using DTM in a cell at any instant is given by: Number of subscribers using DTM at any instant = RDTM*PDTM*Total_Subs_per_cell Some DTM mobiles have the capability to support multiple DL or UL PDTCH together with voice TCH at the same time to acquire higher peak throughput (for example, DTM Class 9 and Class 11). Therefore, DTM Token per cell should be set with minimum value to ensure that the DTM Mobile is not downgraded to lower DTM Class capability with less throughput. Set max_dtm_ts with roundup value according to the number of subscribers using DTM at any instant and DTM mobile capability in this cell. max_dtm_ts = Roundup (Number of subscribers using DTM at any instant) * The maximum PD number supported by DTM MS capability in DTM mode in this cell.

68P02900W21-S 3-108 01 Feb 2007

System Information: BSS Equipment Planning

Dual Transfer Mode

For example, the maximum PD number supported by DTM Class 5 mobile is 1 and the maximum PD number supported by DTM Class 9/11 mobile is 2. As a result of the requested DTM PDs (max_dtm_ts), SW and RES per cell, the total number of PDs requested per PCU may exceed its capabilities. In such circumstances the PCU allocates resources (up to the maximum) for the RES TS. Then the remaining resources are shared between DTM and SW TS, the partition between the two is updated dynamically based on demand.

System considerations
The system considerations are as follows. The BSS restricts the maximum number of DTM timeslots to 29 and with at least 1 reserved or switchable PD in a cell. The BSS restricts the maximum number of Lapdm frames for GTTP to 12. The default value is set to 5, considering the impact on the voice quality. The performance defined PD placement algorithm (gprs_ts_config_alg = 0) has not been modified as a result of DTM. Therefore the recommendation is to use the user defined algorithm (gprs_ts_config_alg = 1), in which case the network planner should take into account how to set max_gprs_ts_per_carrier so as to free up some resource on carriers with high throughput for the PS portion of DTM mode sessions. If the performance algorithm is used, reserved PDCH takes all the best timeslots then the remainder is shared between DTM and SW. With DTM unrestricted, res_gprs_pdchs + sw_gprs_pdchs + max_dtm_ts <=30 in a cell.

QoS2
For GPRS/EGPRS, Quality of Service (QoS) architecture is aimed at providing a framework for differentiation of services and users. Concepts and architecture for QoS are described in 3GPP technical specification 23.107. It is important that QoS characteristics be provided as consistently as possible in the network. Any network entity not involved in negotiation and provision of QoS parameters might become a bottleneck, decreasing the operators perceived QoS. The GSR8 Quality of Service Feature introduced the support for prioritized retention, admission and throughput (minimum bit rate enforcement) specifically targeted to support the Interactive and Background traffic classes defined in the 3GPP specifications. The GSR9 Quality of Service builds on top of this. The key components of QoS2 implementation are as follows: Add support for Streaming Traffic class Maximum bit-rate enforcement as per the QoS Profile Capacity is based on a less conservative budget to start (using user configurable initial coding scheme)

Support for Streaming Traffic Class allows the operator to specify a service requiring constraints on delay and jitter as well as minimum bit rate. Support for PFCs requesting streaming traffic class can be enabled or disabled using the streaming_enabled BSS parameter. If support for streaming traffic class is disabled, BSS still tries to admit the streaming traffic classes as one of the matching interactive traffic classes (determined based on the MTBR settings, details defined in the GSR8 QoS implementation).

68P02900W21-S 01 Feb 2007 3-109

Dual Transfer Mode

Chapter 3: BSS cell planning

Guaranteed bit rate as per the 3GPP specification is defined as the guaranteed number of bits delivered at a SAP within a period of time (provided that there is data to deliver), divided by the duration of the period. For the GPRS RAN, the guaranteed bit rate is defined as the bit rate at the LLC layer. QoS introduced the internal BSS concept of an Minimum Throughput Budget Requirement (MTBR) associated with each PFC. the Guaranteed bit rate for each PFC is an extension of this concept except that the GBR needs to be enforced as a true guarantee and not just a commitment. The MTBR is measured as the raw air throughput at the RLC/MAC layer whereas the GBR measurements excludes any RLC retransmissions. Transfer Delay indicates maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a bearer service, where delay for an SDU is defined as the time from a request to transfer an SDU at one SAP to its delivery at the other SAP. Transfer delay of an arbitrary SDU is not meaningful for a bursty source (applicable only to real-time traffic classes streaming/conversational). In addition, the transfer delay for Radio Access Bearer is smaller than the overall requested transfer delay, as transport through the core network uses a part of the acceptable delay. Transfer delay as all other attributes in the Aggregate BSS QoS Profile is negotiable. QoS2 is based on the GSR8 implementation and all the PFCs for a given user share the same TBF over the air interface to transfer data for the PFCs. GSR9 enhances the LLC scheduling within the same TBF such that the real-time service is prioritized appropriately over the non real-time services where necessary but at the RLC layer, all PFCs for the mobile still share the same pipe. GSR9 streaming support is limited to at most one active real-time PFC per user at any given time. Maximum bit rate enforcement allows the BSS to throttle the throughput of user to the maximum bit-rate stated in the QoS parameters (ABQP) even if there is capacity to provide the user a higher throughput. The main purpose of maximum bit rate enforcement from an operators perspective is to limit the delivered bit rate to applications or external networks and to allow maximum required or permitted bit rate to be defined for applications able to operate with different rates. The Maximum bit rate applies to all traffic classes. Streaming_enabled and qos_mbr_enabled parameters affect cell capacity. In addition, some other parameters impact user experience although no impact to capacity, which include stream_downgrade_enabled and mtbr_downgrade_enabled. For example, if stream_downgrade_enabled is disabled, RT service are rejected if the idle resource is not enough. There are challenges for streaming traffic when performing cell reselection, when reselecting from one cell to another the connection between the mobile and the network is typically lost for 2 - 5 seconds. If using the NACC feature, the transfer delay can be guaranteed.

68P02900W21-S 3-110 01 Feb 2007

System Information: BSS Equipment Planning

Call model parameters for capacity calculations

Call model parameters for capacity calculations

Introduction
This section provides information on how to determine the number of control channels required at a BTS. This information is required for the sizing of the links to the BSC, and is required when calculating the exact configuration of the BSC required to support a given BSS.

Typical call parameters

The number of control channels required at a BTS depends on a set of call parameters; typical call parameters for BTS planning are given in Table 3-12. Table 3-12 Typical parameters for BTS call planning Busy hour peak signaling traffic model Call duration Ratio of SMSs per call Number of handovers per call Ratio of location updates to calls: non-border location area Ratio of location updates to calls: border location area Ratio of IMSI detaches to calls Location update factor: non-border location area using IMSI type 2 Location update factor: border location area using IMSI type 2 GSM circuit-switched paging rate in pages per second Ratio of intra-BSC handovers to all handovers Ratio of LCSs per call Mobile terminated LCS ratio Mobile originated LCS ratio Percent link utilization (MSC to BSS) for GPROC2/GPROC3 Percent link utilization (BSC to BTS) Percent link utilization (BSC to RXCDR) Percent link utilization (BSC to SMLC) Percent link utilization (BSC to PCU) Parameter reference T = 90 seconds S = 2 H = 1.32 l=2 l=7 I = 0.2 L = l + 0.5I = 2.1 L = l + 0.5I = 7.1 PGSM = 60 i = 0.6 Lcs = 0.1 LRMT = 0.95 LRMO = 0.05 U(MSC - SS) = 0.20 U(BSC - BTS) = 0.25 UBSC-RXCDR = 0.40 UBSC-SMLC = 0.40 UBSC-PCU = 0.25 Continued

68P02900W21-S 01 Feb 2007 3-111

Call model parameters for capacity calculations

Chapter 3: BSS cell planning

Table 3-12 Typical parameters for BTS call planning (Continued) Busy hour peak signaling traffic model Percent link utilization (BSS to SGSN) Percent CCCH utilization Block Rate for TCHs Block Rate for MSC-BSS trunks Number of cells per BTS Average SMS message size (payload only) Number of BSCs per location area Busy Hour Call Attempts per sub/BH XBL (enhanced auto connect) parameters Number of XBL messages per new call Number of XBL messages per hr <-> fr handover Length of an average XBL message, in bytes Number of hr <-> fr handovers per call GPRS parameters GPRS Average packet size (bytes) GPRS Traffic per subscriber /BH (kbytes/hr) - Uplink GPRS Traffic per subscriber /BH (kbytes/hr) - Downlink Average sessions per subscriber (per BH) PS attach/detach rate (per sub/BH) PDP context activation/deactivation (per sub/BH) Routing area update GPRS paging rate in pages per second Coding scheme rates (CS1 to CS4) at the RLC/MAC layer PKSIZE = 336.65 ULRATE = 34.14 DLRATE = 127.81 Avg_Sessions_per_sub = 0.64 PSATT/DETACH = 0.5 PDPACT/DEACT = 0.4 RAU = 1.4 PGPRS = 25.91 CS1 = 9.2 kbit/s CS2 = 13.6 kbit/s CS3 = 15.8 kbit/s CS4 = 21.8 kbit/s Continued MNEWCALL = 1 MHANDOVER = 1 LXBL = 50 Hhr-fr = 1 Parameter reference UGBL = 0.40 UCCCH = 0.33 PB-TCHs = 2% PB-Trunks = 1% CBTS = 3 SMSSIZE = 100 bytes BSCLA = 1 BHCAsub 1.8

68P02900W21-S 3-112 01 Feb 2007

System Information: BSS Equipment Planning

Call model parameters for capacity calculations

Table 3-12 Typical parameters for BTS call planning (Continued) Busy hour peak signaling traffic model Coding scheme usage (CS1 to CS4) at a BLER of 10% Parameter reference CS1_usage_UL = CS1_usage_DL = 20% CS2_usage_UL = CS2_usage_DL = 45% CS3_usage_UL = CS3_usage_DL = 25% CS4_usage_UL = CS4_usage_DL = 10 Percentage GPRS coding scheme usage in total traffic Cell updates (per sub/BH) EGPRS parameters EGPRS Average packet size (bytes) - Uplink EGPRS Average packet size (bytes) - Downlink EGPRS Traffic per sub/BH (kbytes/hr) -Uplink EGPRS Traffic per sub/BH (kbytes/hr) -Downlink EGPRS coding scheme rates (MCS-1 to MCS-9) at the RLC/MAC layer PKULSIZE = 134.39 PKDLSIZE = 562.99 ULRATE = 34.14 DLRATE = 127.81 MCS1 = 10.55 kbit/s MCS2 = 12.95 kbit/s MCS3 = 16.55 kbit/s MCS4 = 19.35 kbit/s MCS5 = 23.90 kbit/s MCS6 = 29.60 kbit/s MCS7 = 31.10 kbit/s MCS8 = 46.90 kbit/s MCS9 = 61.30 kbit/s Continued CSuse_UL_GPRS = CSuse_DL_GPRS = 50% CellUpdate = 0.33

68P02900W21-S 01 Feb 2007 3-113

Call model parameters for capacity calculations

Chapter 3: BSS cell planning

Table 3-12 Typical parameters for BTS call planning (Continued) Busy hour peak signaling traffic model Coding scheme usage (MCS1 to MCS9) at a BLER of 20% Parameter reference MCS1_usage_UL = MCS1_usage_DL = 10% MCS2_usage_UL = MCS2_usage_DL = 8% MCS3_usage_UL = MCS3_usage_DL = 33% MCS4_usage_UL = MCS4_usage_DL = 1% MCS5_usage_UL = MCS5_usage_DL = 21% MCS6_usage_UL = MCS6_usage_DL = 15% MCS7_usage_UL = MCS7_usage_DL = 5% MCS8_usage_UL = MCS8_usage_DL = 3% MCS9_usage_UL = MCS9_usage_DL = 4% Percentage EGPRS coding scheme usage in total traffic Average packet size for GPRS and EGPRS traffic mix (bytes) Uplink Average packet size for GPRS and EGPRS traffic mix (bytes) Downlink DTM parameters Percentage of DTM Mobiles DTM mode scaling factor QoS parameters Average GBR for service mix (kbit/s) - Uplink Average GBR for service mix (kbit/s) - Downlink Peak GBR for service mix (kbit/s) -Uplink Peak GBR for service mix (kbit/s) - Downlink GBRAVG_UL = 3.80 GBRAVG_DL = 5.60 GBRPEAK_UL = 9.65 GBRPEAK_DL = 12.70 MSDTM = 30% DTMfactor = 30% PKDLSIZE = 562.99 CSuse_UL_EGPRS = CSuse_DL_EGPRS = 50% PKULSIZE = 134.39

68P02900W21-S 3-114 01 Feb 2007

System Information: BSS Equipment Planning

Call model parameters for capacity calculations

Number of handovers per call and Ratio of intra-BSC handovers to all handovers include 2G-3G handovers. The percentages represent the split of the traffic between the GPRS and EGPRS traffic mix which is network dependent. The percentages can be used to determine the average traffic per sub/BH for a GPRS and EGPRS traffic mix as follows: Traffic per subscriber/BH for GPRS and EGPRS mix (kbytes/hr) = (Percentage GPRS coding scheme usage in total traffic * GPRS Traffic per sub/BH) + (Percentage EGPRS coding scheme usage in total traffic * EGPRS Traffic per sub/BH). The average packet sizes for a GPRS and EGPRS traffic mix are based on the GPRS and EGPRS percentage splits defined for this model. The DTM scaling factor represents the likelihood that a DTM subscriber overlaps a CS call and a PS session.

Location update factor (L)

The location update factor (L) is a function of the ratio of location updates to calls (I), the ratio of IMSI detaches to calls () and whether the short message sequence (type 1) or long message sequence (type 2) is used for IMSI detach; typically = 0 (that is IMSI detach is disabled) as in the first formula given . When IMSI detach is enabled, the second or third of the formulas given should be used. The type of IMSI detach used is a function of the MSC. If IMSI detach is disabled: L = I If IMSI detach type 1 is enabled: L = I + 0.2 * If IMSI detach type 2 is enabled: L = I + 0.5 *

68P02900W21-S 01 Feb 2007 3-115

Control channel calculations

Chapter 3: BSS cell planning

Control channel calculations

Introduction
There are four types of air interface control channels, they are: Broadcast Control CHannel (BCCH) Common Control CHannel (CCCH) Standalone Dedicated Control CHannel (SDCCH) Cell Broadcast CHannel (CBCH), which uses one SDCCH

GPRS/EGPRS defines several new radio channels and packet data traffic channels.

Packet Common Control CHannels (PCCCHs)

The following channels are mapped onto PCCCH: Packet Access Grant CHannel (PAGCH) Downlink only, mapped on AGCH or PDTCH. Used to allocate one or several PDTCHs. Packet Broadcast Control CHannel (PBCCH) Downlink only, mapped on BCCH or PDTCH. Packet Notification CHannel (PNCH) Downlink only. Used to notify the MS of a PTM-M. This is not used in the first GPRS/EGPRS release. Packet Paging Channel (PPCH) Downlink only, mapped on DTCH or CCCH. This is used to page the MS. Packet Random Access CHannel (PRACH) Uplink only. This is used to allow request allocation of one or several PDTCHs, in either uplink or downlink directions.

Packet Data Traffic CHannel (PDTCH)

A PDTCH corresponds to the resource allocated to a single MS on one physical channel for user data transmission.

Packet Dedicated Control CHannels (PDCCHs)

Packet Associated Control CHannel (PACCH) The PACCH is bi-directional. It is used for MS-PCU control signaling while the MS is performing a packet transfer. Packet Timing advance Control CHannel (PTCCH/U) Uplink channel, used to transmit random access bursts. The transceiver uses these bursts to estimate the timing advance for an MS when it is in transfer state.

68P02900W21-S 3-116 01 Feb 2007

System Information: BSS Equipment Planning

Control channel calculations

Packet Timing advance Control CHannel (PTCCH/D) Downlink channel, used to transmit timing advance updates to several MSs at the same time.

Planning considerations
In planning the GSM/GPRS/EGPRS control channel configuration, the network planner must consider three main variables: Signaling requirements of the CCCH Signaling requirements of the PCCCH (if enabled) Signaling requirements of the SDCCH

SDCCH planning can be done independently, but CCCH planning depends on PCCCH planning. It is assumed that by adequate provisioning of the downlink part of the CCCH or PCCCH, the uplink part is implicitly provisioned with sufficient capacity.

CCCH and PCCCH planning

When PCCCH is disabled (pccch_enabled is set to zero), all control signaling for GSM and GPRS/EGPRS occur on the CCCH. When PCCCH is enabled, control signaling for GPRS/EGPRS occurs on the PCCCH instead of the CCCH. Thus, CCCH signaling decreases when PCCCH is enabled. In other words, the CCCH planning is dependent on PCCCH planning. When PCCCH is enabled (pccch_enabled is set to 1), an additional variable must be considered. The network planner must decide whether or not to use paging coordination in the system. If the planner decides to use paging coordination (also called Network Operation Mode I), then a MS only needs to monitor the paging channel on the PCCCH, and receives circuit-switched pages on the PACCH when it has been assigned a PDTCH. If the planner decides not to use paging coordination (called Network Operation Mode III), the MS that needs to receive pages for both circuit-switched and packet-switched services should monitor paging channels on both PCCCH and CCCH.

Network Operation Mode II is currently not supported in the Motorola BSS.

CCCH and PCCCH decision tree

Figure 3-78 summarizes the decisions used to determine which planning steps should be used to determine the CCCH and PCCCH signaling capacity requirements.

68P02900W21-S 01 Feb 2007 3-117

Control channel calculations

Chapter 3: BSS cell planning

Figure 3-78 CCCH and PCCCH decision tree

(1) Decide whether or not paging coordination will be used in the network. (2) Calculate the number of CCCHs per BTS cell when PCCCH is enabled. (3) Calculate the number of PRACH blocks per BTS cell. (4) Calculate the number of PAGCHblocks per BTS cell. (5) Calculate the number of PPCH blocks per BTS cell. (6) Calculate the number of PBCCH blocks per BTS cell.

pccch_enabled = 1

pccch_enabled = 0

Calculate the number of CCCHs per BTS cell when PCCCH is disabled.

Combined BCCH
This planning guide provides the planning rules that enable the network planner to evaluate whether a combined BCCH can be used, or if a non-combined BCCH is required. The decision to use a noncombined BCCH is a function of the number of CCCH channels required and the number of SDCCH channels required. The use of a combined BCCH is desirable because it permits the use of only one timeslot on a carrier that is used for signaling. A combined BCCH can offer four more SDCCH blocks for use by the GSM circuitswitched signaling traffic. If more than an average of three CCCH blocks, or more than four SDCCH blocks, are required to handle the signaling load, more control channel timeslots are required. The planning approach for GPRS/EGPRS/GSM control channel provisioning is to determine whether a combined BCCH is possible, given the load on the CCCH control channel. When more than three and less than nine CCCH blocks are required to handle the combined load, the use of a combined BCCH is not possible. When more than nine CCCH blocks are needed, one or more timeslots are required to handle the CCCH signaling. In this case, it is advantageous to use a combined BCCH again, depending on the CCCH and SDCCH load. The determination of how many CCCH and SDCCH blocks are required to support the circuit-switched GSM traffic is deferred to the network planning that is performed with the aid of the relevant planning information for GSM. The network planning that is performed using the planning information determines how many CCCH and SDCCH blocks are required, and subsequently how many timeslots in total, are required to support the CCCH and SDCCH signaling load.

Number of CCCHs and PCCCHs per BTS cell

The following factors should be considered when calculating the number of CCCHs per BTS cell are as follows: The CCCH channels comprise the Paging CHannel (PCH) and Access Grant CHannel (AGCH) in the downlink, and the Random Access CHannel (RACH) in the uplink. If PCCCH is enabled (pccch_enabled is set to 1), then the PCCCH relieves all GPRS/EGPRS control signaling from the CCCH. Further, if paging coordination is also enabled, GSM CS paging also occurs on the PCCCH for all GPRS/EGPRS-enabled mobiles. If the CCCH has a low traffic requirement, the CCCH can share its timeslot with SDCCHs (combined BCCH). If the CCCH carries high traffic, a non-combined BCCH must be used. o Combined BCCH (with four SDCCHs) Number of CCCH blocks = 3

68P02900W21-S 3-118 01 Feb 2007

System Information: BSS Equipment Planning

Control channel calculations

Number of CCCH blocks reserved for AGCH bs_ag_blks_res is 0 to 2 Number of CCCH blocks available for PCH is 1 to 3 o Non-combined BCCH Number of CCCH blocks = 9 Number of CCCH blocks reserved for AGCH bs_ag_blks_res is 0 to 7 Number of CCCH blocks available for PCH is 2 to 9 When a non-combined BCCH is used, it is possible to add additional CCCH control channels (in addition to the mandatory BCCH on timeslot 0). These additional CCCH control channels are added, in order, on timeslots 2, 4, and 6 of the BCCH carrier, thus creating cells with 18, 27, and 36 CCCH blocks. These configurations would only be required for high capacity cells or in large location areas with a large number of pages. The number of blocks required for NCH depends upon the number of VGC calls envisaged to be active simultaneously in the cell. The number of NCH blocks affects the AGCH/PCH bandwidth and also the performance of the NCH. Each CCCH block can carry one message. The message capacity of each CCCH block is 4.25 messages/second. This is due to the 51-frame multiframe structure of the channel. Each PCCCH block can carry one message. The message capacity of each PCCCH block is 4.17 messages/second. This is due to the 52-frame multiframe structure of the channel. The AGCH is used to send immediate assignment and immediate assignment reject messages for GSM MSs and, if PCCCH is not enabled, GPRS/EGPRS MSs. Each AGCH immediate assignment message can convey channel assignments for up to two MSs. Each AGCH immediate assignment reject message can reject channel requests from up to four MSs. The PCH is used to send GSM paging messages and, if PCCCH is not enabled, GPRS/EGPRS paging messages. Each PCH paging message can contain pages for up to four MSs using TMSI or two MSs using IMSI. If no paging messages are to be sent in a particular CCCH block, then an immediate assignment or immediate assignment reject message can be sent instead. The current Motorola BSS implementation applies the following priority (highest to lowest) for downlink CCCH messages: o o o Paging message (if not reserved for AGCH) Immediate assignment message Immediate assignment reject message

Thus, for example, if for a particular CCCH sub-channel there are always paging messages (that is high paging load) waiting to be sent, no immediate assignment or immediate assignment reject messages are sent on that CCCH sub-channel. Hence the option to reserve CCCH channels for AGCH. It can normally be assumed that sufficient capacity exists on the uplink CCCH (RACH) once the downlink CCCH is correctly dimensioned. Some other parameters can be used to configure the CCCH channels. Some of these are: o Number of paging groups. Each MS is a member of only one paging group and only needs to listen to the PCH sub-channel corresponding to that group. Paging group size is a trade off between MS idle-mode battery life and speed of access (for example, a lot of paging groups, means the MS need only listen occasionally to the PCH, but as a consequence it takes longer to page that MS, resulting in slower call set-up as perceived by a PSTN calling party).

68P02900W21-S 01 Feb 2007 3-119

Control channel calculations

Chapter 3: BSS cell planning

o o

Number of repetitions for MSs attempting to access the network on the RACH. The time MS must wait between repetitions on the RACH.

{26881} Extended Uplink TBF is the feature that enhances uplink data performance by minimizing the interruptions of uplink data flow in GPRS/EGPRS networks due to a frequent release and establishment of uplink TBF. According to the principle of Extended Uplink TBF, this feature decreases the amount of RACH for uplink applications session like uplink FTP. If the uplink application is rare, total amount of decreased RACH is small. Thus the impact of RACH decrement can be ignored, if the uplink application is booming and total amount of decreased RACH is huge, otherwise the impact of RACH decrement cannot be ignored and RACH decrement is taken into account for CCCHs calculation. Precise determination of the CCCH requirements is difficult. However, some statistics can be collected (for example ACCESS_PER_PCH, ACCESS_PER_AGCH) by the BSS and can be used to determine the CCCH loading and hence perform adjustments.

Calculating the number of CCCHs per BTS cell - PCCCH disabled

When PCCCH is disabled (pccch_enabled is set to zero), the provisioning of the CCCH is estimated by calculating the combined load from the GPRS/EGPRS pages, GSM pages, GPRS/EGPRS access grant messages and GSM access grant messages. The calculation is performed by adding the estimated GPRS/EGPRS and GSM paging blocks for the BTS cell to the estimated number of GPRS/EGPRS and GSM access grant blocks for the BTS cell, and dividing that sum by the CCCH utilization factor. The blocking factor and Erlang B table are then used to provide the number of CCCHs required.

Introducing the GPRS/EGPRS feature into a cell may cause noticeable delays for paging in that cell. Motorola advises operators to re-check the NPAGCH and NPCH equations provided here when adding GPRS/EGPRS to a cell. Enable PCCCH in cells with heavy paging. The following planning actions are required:

In the following paragraphs, GPRS notation represents GPRS/EGPRS. Determine the number of CCCHs per BTS. The average number of blocks required to support AGCH and PCH is given by the following equation:

N PCH + AGCH + NCH = N PCH + N AGCH + N NCH

The average number of blocks required to support AGCH and PCH is given by the following equation:

N PCH + AGCH =

N AGCH + N PCH U CCCH

The average number of blocks required to support AGCH only is given by the following equation:

N AGCH = + N AGCH GSM + N AGCH GPRS

68P02900W21-S 3-120 01 Feb 2007

System Information: BSS Equipment Planning

Control channel calculations

The average number of blocks required to support AGCH for GSM traffic is given by the following equation:

N PCH + AGCH =

AGCH N AGCH / Block * 4.25

The number of access grants per AGCH block is 2.

N AGCH / Block = 2
The average number of blocks required to support AGCH for GPRS/EGPRS traffic is given by the following equation:

N AGCH GPRS =
Where:

RACHA Arrivals / Sec *1.1 4.25 GPRS _ Users * Avg _ Sessions _ per _ user 3600

RACHA _ Arrivals _ per _ sec =

The access grant rate is given by the following equation:

AGCH = CALL + L + S + LCS

The call rate (calls per hour) is given by the following equation:

call =

e T c T c T c T

The location update rate (LU per hour) is given by the following equation:

L = L *

The SMS rate (SMSs per hour) is given by the following equation:

S = S *

The LCS rate (LCSs per hour) is given by the following equation:

LCS = L CS *

The average number of blocks required to support PCH only is given by the following equation:

N PCH = + N PCH GSM + N PCH GPRS

The average number of blocks required to support GSM CS paging only is given by the following equation:

N PCH GSM =

PGSM N Pages / Block *1.25

68P02900W21-S 01 Feb 2007 3-121

Control channel calculations

Chapter 3: BSS cell planning

When DTM feature is enabled, the average number of blocks required to support GSM CS paging is given by the following equation:

P * (1 R PS * PDTM ) N PCH _ GSM = GSM N Pages / Block * 4.25

Where, RPS is the probability of MS in PS mode and PDTM is the DTM penetration rate. The number of pages per paging PCH block depends on whether paging is performed using TMSI or IMSI. For TMSI paging: N pages/Block = 4 For IMSI paging: N pages/Block = 2 The number of paging blocks required at a cell to support GPRS/EGPRS is given by:

P * 1.2 N PCH GPRS = GPRS 4.25

Where Is

UCCCH AGCH GPRS_Users Avg_Sessions_per_user

CCCH utilization access grant rate (per second) number of GPRS and EGPRS users on a cell average number of sessions originated by user per busy hour (this includes the sessions for signaling) call arrival rate per second location update rate per second number of SMSs per second number of Erlangs per cell average call length, in seconds. number of GSM circuitswitched traffic pages transmitted to a BTS cell per second. number of GPRS or EGPRS pages transmitted to a BTS cell per second

call L S e T PGSM

PGPRS

68P02900W21-S 3-122 01 Feb 2007

System Information: BSS Equipment Planning

Control channel calculations

The following table provides the control channel configurations.

Table 3-13 Control channel configurations Timeslot 0 Other timeslots Comments

1 BCCH + 3 CCCH + 4 SDCCH

N x 8 SDCCH

combined BCCH. The other timeslot may or may not be required, depending on the support of circuitswitched traffic where the value of N is >= 0. non-combined BCCH. The value of N is >= 1. non-combined BCCH. This is an example of one extra timeslot of CCCHs added in support of GPRS traffic. The value of N is >= 1.

1 BCCH + 9 CCCH 1 BCCH + 9 CCCH

N x 8 SDCCH N x 8 SDCCH, 9 CCCH

Calculating the number of CCCHs per BTS cell - PCCCH enabled

When PCCCH is enabled (pccch_enabled is set to 1), the Network Operation Mode becomes relevant to the planning rules. If paging coordination is used and Network Operation Mode is I, then circuit-switched pages for Class A and Class B mobiles (mobiles that are capable of both GSM and GPRS) and pages for EGPRS mobiles are sent on the PCCCH instead of the CCCH. Regardless of paging coordination though, all GPRS/EGPRS control signaling occurs on the PCCCH. Hence, the following planning rules should be used. The average number of blocks required to support AGCH, NCH and PCH is given by the following equation:

N PCH_ AGCH_ NCH = N PCH_ AGCH + N NCH

If VGCS is enabled in a cell, NNCH = 1. The average number of blocks required to support AGCH and PCH is given by the following equation:

N PCH + AGCH = ( N AGCH + N PCH )

1 U CCCH

The average number of blocks required to support AGCH only is given by the following equation:

N AGCH_ GSM =

AGCH N AGCH/Block * 4.25

The number of access grants per AGCH block is 2.

N AGCH / Block = 2
The access grant rate is given by the following equation:

AGCH = CALL + L + S + LCS

The call rate (calls per hour) is given by the following equation:

call =

e T

68P02900W21-S 01 Feb 2007 3-123

Control channel calculations

Chapter 3: BSS cell planning

The location update rate (LU per hour) is given by the following equation:

L = L *

c T c T c T

The SMS rate (SMSs per hour) is given by the following equation:

S = S *

The LCS rate (LCSs per hour) is given by the following equation:

LCS = L CS *

The average number of blocks required to support PCH depends on the provisioning of paging coordination in the cell. If paging coordination is not enabled then the average number of blocks required to support GSM CS paging is given by the following equation:

N PCH =

PGSM N Pages / Block * 4.25

If paging coordination is enabled, the average number of blocks required to support GSM CS paging is given by the following equation:

N GSM Only MS * PGSM N GSM Capable MS N PCH = N Pages / Block * 4.25

The number of pages per paging PCH block depends on whether paging is performed using TMSI or IMSI. For TMSI paging: N pages/Block = 4 For IMSI paging: N pages/Block = 2 The number of paging blocks required at a cell to support GPRS/EGPRS is given by the following equation:

P * 1.2 N PCH GPRS = GPRS 4.25

Where Is

UCCCH AGCH P call L S

CCCH utilization access grant rate (per second) paging rate per second call arrival rate per second location update rate per second number of SMSs per second
Continued

68P02900W21-S 3-124 01 Feb 2007

System Information: BSS Equipment Planning

Control channel calculations

Where

Is

e T PGSM

number of Erlangs per cell average call length, in seconds. the number of GSM circuit-switched traffic pages transmitted to a BTS cell per second. number of mobiles in the system that do not support GPRS/EGPRS. number of mobiles in the system that support GSM and, optionally, GPRS/EGPRS. This is also equal to the total number of mobiles in the system minus the number of GPRS/EGPRS-only mobiles in the system.

NGSM_Only_MS NGSM_Capable_MS

The network planner can provision up to 1 PCCCH timeslot per BTS cell. If the PCCCH is enabled, then the PCCCH occupies a reserved PDTCH timeslot on the BCCH carrier. The use_bcch_for_gprs parameter is ignored to allow only the PCCCH timeslot on the BCCH carrier. [FR27539] PCCCH/PBCCH can be enabled if BCCH carrier is part of the hopping system and TS1 of the BCCH carrier is a non-hopping timeslot. In other words, hopping can be enabled on TS2 to TS7 of the BCCH carrier while PCCCH/PBCCH is enabled and TS1 is configured or allocated as PCCCH/PBCCH timeslot. The network planner can reserve 1 to 12 of the radio blocks on the uplink PCCCH as PRACH, For GPRS/EGPRS random access, using the cells bs_prach_blks parameter. Any uplink PCCCH blocks that are not reserved for PRACH can be used as PDTCH for up to 2 mobiles. The network planner allocates the 12 radio blocks on the downlink PCCCH among 4 logical channels: PBCCH, PPCH, PAGCH, and PDTCH. Allocation among these channels is a trade-off between the following factors:

The PPCH and PAGCH capacity required for the cell. The delay required for mobiles to acquire PBCCH system information upon entering the cell. This delay is directly related to the delay before a mobile can start a data session following cell selection. The PDTCH capacity available on the PCCCH timeslot.

PBCCH blocks are reserved using the bs_pbcch_blks parameter. PAGCH blocks can be reserved using the bs_ag_blks_res parameter. All other downlink PCCCH blocks can be used for the PPCH, but there is no parameter to reserve PPCH blocks. Nevertheless, the network planner should calculate the number of PPCH blocks required in a BTS cell to determine how many blocks can be allocated to PBCCH blocks. Any downlink PCCCH blocks that are not reserved for PBCCH, can be used for user data transmission when not being utilized for control signaling. The PCCCH timeslot is used for user data for up to 2 mobiles. For the subsequent calculations, the message capacity for each PCCCH block is 1 message per 0.240 second.

68P02900W21-S 01 Feb 2007 3-125

Control channel calculations

Chapter 3: BSS cell planning

To calculate the number of PRACH blocks per BTS cell

The network planner should use the average number of blocks necessary to support PRACH to set the cells bs_prach_blks parameter.

In the following paragraphs, GPRS notation represents GPRS/EGPRS.

bs_prach_blk = Roundup( N PRACH )

The average number of blocks required to support PRACH is given by the following equation:

N PRACH =

GPRS_RACH/Sec*0.24 U PCCCH GPRS _ Users * Avg _ Sessions _ per _ user 3600

Is

The average number of PRACH arrivals per second is given by the following equation:

GPRS _RACH / Sec =

Where

UCCCH GPRS_RACH/sec GPRS_Users Avg_Sessions_per_user

desired PCCCH utilization GPRS/EGPRS random access rate (per second) number of GPRS and EGPRS users on a cell average number of sessions originated by user per busy hour (this includes the sessions for signaling)

Calculating the number of PAGCH blocks per BTS cell

The network planner should use the average number of blocks necessary to support PAGCH to set the cells bs_pag_blk parameter.

bs_pag_blk = Roundup( N PAGCH )

The average number of blocks required to support PAGCH is given by the following equation:

N PAGCH =

GPRS _ RACH / Sec *1.1 * 0.24 U PCCCH

68P02900W21-S 3-126 01 Feb 2007

System Information: BSS Equipment Planning

Control channel calculations

The average number of PAGCH arrivals per second is given by the following equation:

GPRS_ RACH / Sec =

GPRS _Users * Avg _ Sessions _ per _ user 3600

Is

Where

UCCCH GPRS_RACH/sec GPRS_Users Avg_Sessions_per_user

desired PCCCH utilization GPRS/EGPRS random access rate (per second) number of GPRS and EGPRS users on a cell average number of sessions originated by user per busy hour (this includes the sessions for signaling)

Calculating the number of PPCH blocks per BTS cell

The average number of blocks required to support PPCH is given by:

N PPCH =

N PPCH _ GSM + N PPCH _ GPRS U PCCCH

In the following paragraphs, GPRS notation represents GPRS/EGPRS. If paging coordination is not enabled in the network, then the average number of PPCH blocks required to support GSM CS paging only is zero:

N PPCH _ GSM = 0
If paging coordination is enabled, then the average number of blocks required to support PPCH is given by the following equation:

N PPCH _ GSM =

N GSM _ GPRS MS N ALL _ SMS

* PGSM * 0.24

The average number of PPCH blocks required to support GPRS/EGPRS paging only is given by the following equation:

N PPCH _ GPRS = PGPRS * 1.2 * 0.24

68P02900W21-S 01 Feb 2007 3-127

Control channel calculations

Chapter 3: BSS cell planning

Where

Is

UCCCH NGSM_GPRS_MS NALL_MS PGSM PGPRS

desired PCCCH utilization number of mobiles in the system that are capable of both GSM and GPRS/EGPRS services total number of mobiles in the system number of GSM circuit-switched traffic pages transmitted to a BTS cell per second number of GPRS/EGPRS pages transmitted to a BTS cell per second

When GSM CS paging load becomes heavy and paging coordination is enabled, the PPCH blocks exceed the capacity of PCCCH.

Selecting the number of PBCCH blocks per BTS cell

The network planner must allocate between 1 and 4 PBCCH radio blocks on the downlink PCCCH by setting the cells bs_pbcch_blks parameter. An allocation of 4 PBCCH blocks minimizes the time required for the mobile to acquire the GPRS/EGPRS broadcast system information of the cell. In turn, this minimizes the delay before the mobile can start data transmission upon cell selection or reselection. An allocation of 1 PBCCH block minimizes the radio resources consumed by PBCCH, freeing up more radio resources for PAGCH, PPCH, and user data transmission. Thus choosing the number of PBCCH blocks per BTS cell is a trade-off between the data transmission delay following cell selection or reselection against radio resources available for PPCH, PAGCH, and PDTCH. The number of PCCCH blocks available for PBCCH is given by the following equation:

AvailablePBCCH = 12 Roundup( N PAGCH ) Roundup( N PPCH )

So, the network planner must select the number of PBCCH block (NPBCCH) such that it does not exceed the blocks available (maximum of 4 blocks). The network planner must also consider the trade-off with PDTCH capacity on the PCCCH timeslot. It is recommended that the network planner maximize the PBCCH blocks instead of PDTCH capacity on the PCCCH timeslot. The PCCCH timeslot is only used for PDTCHs during conditions of cell congestion. Therefore, the network planner can improve the user experience more by maximizing the PBCCH blocks and consequently minimizing data transmission delay following cell selection or reselection. The network user chooses to prioritize PDTCH capacity when only a single PDTCH exists in the cell, that is, the PCCCH timeslot is the only GPRS/EGPRS timeslot.

68P02900W21-S 3-128 01 Feb 2007

System Information: BSS Equipment Planning

Control channel calculations

User data capacity on the PCCCH timeslot

The PCCCH timeslot can support user data traffic (PDTCH) for up to two mobiles. The radio blocks on the uplink PCCCH timeslot that are not required for PRACH are available for PDTCH. Similarly, the radio blocks on the downlink PCCCH timeslot that are not required for PBCCH, PAGCH, or PPCH are available for PDTCH as well. If other PDTCHs are available in the cell, PDTCHs are allocated on the PCCCH timeslot when the cell is congested. Accordingly, the network planner can estimate the data capacity on the PCCCH timeslot. The formulas given can be use to estimate the raw data capacity of the PCCCH timeslot. The raw data rate estimates are not adjusted for protocol overhead and possible data compression. They are for informational use only. The raw downlink PDTCH capacity is given by the following equation:

Downlink Capacity =

12 N PBCCH N PAGCH N PPCH * TS Data Rate 12

The raw uplink PDTCH capacity is given by the following equation:

Uplink Capacity =

12 Roundup( N PRACH ) * TS Data Rate 12

Is

Where

TS_Data_Rate

average data rate of the PCCCH timeslot based on the expected radio conditions on the PCCCH carrier.

The radio conditions determine the coding scheme used for the data transmission. For example, suppose the network planner expects good radio conditions on the PCCCH carrier so that CS4 is used 80% of the time and CS3 is used 20% of the time. The network planner also calculates the following when dimensioning the PCCCH: NPAGCH = 2 NPPCH = 3 NPBCCH = 4 In this case, the average data rate is calculated as follows:

TS Data Rate = 0.80 * 20 + 0.2 *14.6 = 18.92 Kbits / s

So the raw data capacity for the downlink PCCCH can be calculated using the following equation:

Downlink Capacity =

12 4 2 3 * 18.92 = 4.73 Kbits / s 12

68P02900W21-S 01 Feb 2007 3-129

Control channel calculations

Chapter 3: BSS cell planning

Number of SDCCHs per BTS cell

Determining the SDCCH requirement is an important part of the planning process. The SDCCH is where a large portion of signaling and data messaging takes place for SMS, location update and call set-up. As the number of calls taking place in a BTS increases, greater demand is placed on the control channel for call set-up and the same is true if the number of SMS increases. The Fast Call Setup feature allows the BSS to allocate an appropriate channel based on the establishment cause. That is, TCH directly to the MS if the MS intends to make a speech call, or SDCCH if the MS intends to send a SMS. The user configurable parameter TCH_usage_threshold keeps track of the percentage of TCH that are busy in the BCCH band. When the busy percentage is equal or higher to TCH_usage_threshold, the BSS turns this feature off. If DTM feature is unrestricted, the GTTP message is sent on SDCCH when the DTM subscriber is in dedicated mode and allocated to the SDCCH. If the following requirements are met, the message is sent on the main DCCH by GTTP message:

The DTM MS is in dedicated mode. The information contained in the message is signaling. The number of LAPDm frames is smaller than Max_Lapdm specified by the network.

By reviewing the collected network statistics GTTP_UL_LLC, GTTP_DL_LLC and DTM_REQ_REC on a continuous basis, the network planner can tune the Max_Lapdm parameter, as well as the SDCCH configuration. Based on the analysis, the GTTP has only minor impact on SDCCH planning.

Considering the impact to voice quality from GTTP signaling, set Max_Lapdm parameter to the default value of 5. The following factors should be considered when calculating the number of SDCCH per BTS cell:

To determine the required number of SDCCHs for a given number of TCHs per cell, the call, location update, and SMS (point to point) rates must be determined. A TCH is directly allocated to the MS for a speech call when the Fast Call Setup feature is turned on. The SDCCH usage drops require to be accounted for. Refer to the equations for information on calculating these rates. Once these rates are determined, the required number of SDCCHs for the given number of TCHs can be determined. Refer to the equations for information on calculating the required number of SDCCHs. The rates for SMS are for the SMSs taking place over an SDCCH. For MSs involved in a call, the SMS takes place over the TCH, and does not need the use of an SDCCH. Further, if the network is configured to send SMS over GPRS, SMS does not need the use of a SDCCH. Calculating the number of SDCCHs required is necessary for each cell at a BTS site. The equation for NSDCCH is used to determine the average number of SDCCHs. There is a limit of 124 or 128 SDCCHs (depending on whether control channels are combined or not) per cell. This limits the number of supportable TCHs within a cell. A change in the call model also affects the number of SDCCHs (and supportable TCHs) required. The formula should then be used to calculate the number of SDCCHs needed. The number of Erlangs in Table 3-15 and Table 3-16is the number of Erlangs supported by a given cell, based on the number of TCHs in that cell. To determine the number of Erlangs supported by a cell, use Erlang B.

68P02900W21-S 3-130 01 Feb 2007

System Information: BSS Equipment Planning

Control channel calculations

The number of TCHs in a cell vary depending upon the number of carriers that are (AMR or GSM) half rate capable. The number of calls that use the half rate capable carriers varies depending upon such factor as cell loading, mobile penetration and so on. In Table 3-15 and Table 3-16, a worst case scenario is assumed, where all half rate capable carriers are used as half rate.

Not all combinations of half rate usage are shown in the tables.

The call arrival rate is derived from the number of Erlangs (Erlangs divided by call duration). Use Erlang B (on the value of NSDCCH) to determine the required number of SDCCHs necessary to support the desired grade of service. The number of location updates is higher for sites located on the borders of location areas, as compared to inner sites of a location area (refer to Figure 3-79).

Figure 3-79 Location area diagram

BORDER BTS =

INNER BTS =

LOCATION AREA

Calculating the number of SDCCHs per BTS cell

Determine the number of SDCCHs per BTS cell. The average number of SDCCHs is given by the following equation:

N SDCCH = Call * Tc * Tu + L * (TL + Tg ) + S * (TS + Tg ) + LCS * (TLCS + Tg )

68P02900W21-S 01 Feb 2007 3-131

Control channel calculations

Chapter 3: BSS cell planning

Where

Is

NSDCCH call Tc Tu

average number of SDCCHs call arrival rate per second time duration for call set-up the Fast Call Setup component. This is set to 1 if Fast Call Setup is disabled or not purchased otherwise this is set to (100 - TCH usage threshold)/100. location update rate time duration of location updates guard time for SDCCH number of SMSs per second. time duration of SMS (Short Message Service set-up) number of LCSs per second. time duration of LCS (Location Service Set-up).

L TL Tg S TS LCS TLCS

The timeslots allocated for SDCCH follows the new algorithm for picking the timeslots based on the parameter setting.

Per carrier db parameter sd_priority: The parameter sd_priority takes a value in the range 0 through 255, and this assigns a priority to the carrier (RTF); the lower the priority the higher the possibility to get a SDCCH in the carrier (RTF). PBCCH: If PBCCH is configured, the NON BCCH carrier has preference over the BCCH carrier. Number of available TCH barred timeslots: Available TCH barred timeslots are TCH barred timeslots which are not configured as SDCCH timeslots yet. TCH or PDTCH cannot be configured on a TCH barred timeslot since it does not have a terrestrial backhaul. It can only be used for SDCCHs since SDCCH timeslots do not need terrestrial backhaul. PGSM/EGSM: The PGSM carrier is preferred over EGSM carriers. Per carrier db parameter pkt_radio_type: The parameter pkt_radio_type determines if the RTF can carry GPRS/EDGE or not. Carriers with lower pkt_radio_type are preferred over carriers with higher pkt_radio_type. Half Rate: Non Half Rate carriers are preferred over Half Rate capable carriers. Sdcch loading (Not the db parameter sd_load, but the actual number of SDCCH timeslots configured). Carriers with fewer sdcch loading are selected over carriers with higher sdcch loading so that SDs get distributed among carriers with identical SD related parameters. The db parameter sd_load determines the number of timeslots in the carrier that can be SDCCH. This can take a value of 0 through 8; that is, up to 8 timeslots can be configured as SDCCH in a single carrier. Carrier id: Carrier id is used as a tie breaker among two carriers. Carrier with lower carrier id is selected over carrier with higher carrier id.

68P02900W21-S 3-132 01 Feb 2007

System Information: BSS Equipment Planning

Control channel calculations

SDCCH configuration recommendations

SDCCH TS should be spread as widely as possible across available carriers. Only one SDCCH TS is allowed on the BCCH Carrier. This can be achieved by setting sd_load parameter for BCCH RTF to 1. A maximum of 3 SDCCH TS on other carriers are recommended, though 2 SDCCH TS is a preferred maximum. This can be achieved by setting sd_load on non BCCH RTF to 2 or 3.
Number_sdcchs_preferred is the number of SDCCH the system configures at the system initialization time.

When channel_reconfiguration_switch is enabled, then based on SDCCH usage, the TCH in the cell can be reconfigured to SDCCH up to max_number_of_sdcchs based on need. When SDCCH blocking is perceived to be high at a cell, set the max_number_of_sdcchs to be greater than number_sdcchs_preferred by a value of 8 or 16. This can help alleviate SDCCH blocking in that cell. The following table provides a set of example configurations.
Table 3-14 Example Configurations Number of SDCCH/ cell SDCCH on BCCH carrier SDCCH on second carrier SDCCH on third carrier SDCCH on fourth carrier SDCCH on fifth carrier SDCCH on sixth carrier

60 64 92

12 8 12

16 16 16

16 16 16

16 16 16

8 16

16

Control channel configurations

Table 3-15 and Table 3-16 give typical control channel configurations based on the typical BTS planning parameters given in Table 3-12. Due to the many combinations of half rate capable RTFs, only a partial listing is depicted.

Control channel configurations for non-border location area

The following table shows the configurations for non-border location area cell, where the ratio of location updates to calls is 2.
Table 3-15 Control channel configurations for non-border location area Number of RTFs Number of TCHs Number of Erlangs Number of SDCCHs Timeslot utilization Timeslot 0 Other timeslots

1 fr

2.94

1 BCCH +3 CCCH +4 SDCCH 1 BCCH + 9 CCCh

N/A

1 hr

12

6.61

8 SDCCH
Continued

68P02900W21-S 01 Feb 2007 3-133

Control channel calculations

Chapter 3: BSS cell planning

Table 3-15 Control channel configurations for non-border location area (Continued) Number of RTFs Number of TCHs Number of Erlangs Number of SDCCHs Timeslot utilization

2 fr

14

8.20

1 BCCH + 3 CCCH+4 SDCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH

8 SDCCH

1 fr 1 hr 2 hr 3 fr 2 fr 1 hr 1 fr 2 hr 3 hr 4 fr 3 fr 1 hr 3 hr 4 fr 3 hr 4 fr 3 fr 1 hr 5 fr 6 fr 5 fr 1 hr

21 26 21 29 36 40 29 36 40 29 40 29 36 36 44 51

14.03 18.38 14.04 21.03 27.3 31.0 21.03 27.3 31.0 21.03 31.0 21.03 27.3 27.3 34.7 41.2

13 15 13 16 21 22 16 20 22 16 22 16 20 20 24 28

2*8 SDCCH 2*8 SDCCH 2*8 SDCCH 2*8 SDCCH 3*8 SDCCH 3*8 SDCCH 2*8 SDCCH 3*8 SDCCH 3*8 SDCCH 2*8 SDCCH 3*8 SDCCH 2*8 SDCCH 3*8 SDCCH 3*8 SDCCH 3*8 SDCCH 4*8 SDCCH
Continued

68P02900W21-S 3-134 01 Feb 2007

System Information: BSS Equipment Planning

Control channel calculations

Table 3-15 Control channel configurations for non-border location area (Continued) Number of RTFs Number of TCHs Number of Erlangs Number of SDCCHs Timeslot utilization Timeslot 0 Other timeslots

3 fr 3 hr 6 hr 7 fr 8 fr 9 fr 10 fr

66 82 51 59 66 74

55.3 70.6 41.2 49.6 55.3 62.9

35 43 28 32 35 39

1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH

5*8 SDCCH 6*8 SDCCH 4*8 SDCCH 4*8 SDCCH 5*8 SDCCH 5*8 SDCCH

The CBCH reduces the number of SDCCHs by one and needs another channel.

Control channel configurations for border location area

The following table shows the configurations for the border location area cell, where the ratio of location updates to calls is 7.
Table 3-16 Control channel configurations for border location area Number of RTFs Number of TCHs Number of Erlangs Number of SDCCHs Timeslot utilization Timeslot 0 Other timeslots

1 fr 1 hr 2 fr 1fr 1hr

6 12 13 21

2.28 6.61 7.4 14.0

7 12 15 20

1 BCCH + 9 CCCH 1 BCCH +3 CCCH + 4SDCCH 1 BCCH + 9 CCCH 1 BCCH + 3 CCCH+ 4 SDCCH

8 SDCCH 8 SDCCH 2*8 SDCCH 2*8 SDCCH

Continued

68P02900W21-S 01 Feb 2007 3-135

Control channel calculations

Chapter 3: BSS cell planning

Table 3-16 Control channel configurations for border location area (Continued) Number of RTFs Number of TCHs Number of Erlangs Number of SDCCHs Timeslot utilization Timeslot 0 Other timeslots

2 hr 3 fr 2 fr 1hr 1 fr 2hr 3 hr 4 fr 3 fr 1 hr 5 fr 6 fr 5 fr 1 hr 3 fr 3 hr 7 fr 8 fr 9 fr 10 fr

24 20 27 34 36 27 34 35 42 49 63 49 56 63 70

16.6 13.2 19.3 25.5 27.3 19.3 25.5 26.4 32.8 39.3 52.5 39.3 45.9 52.5 59.1

24 21 27 34 36 27 34 35 41 48 62 48 55 64 68

1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9CCCH 1 BCCH + 9CCCH 1 BCCH + 9 CCCH 1 BCCH + 9CCCH 1 BCCH + 9CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 9CCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH

3*8 SDCCH 3*8 SDCCH 4 * SDCCH 5*8 SDCCH 5*8 SDCCH 4*8 SDCCH 4*8 SDCCH 5*8 SDCCH 6*8 SDCCH 6*8 SDCCH 8*8 SDCCH 6*8 SDCCH 7x8 SDCCH 8*8 SDCCH 9*8 SDCCH

For the ITS feature, to configure more EGPRS PDs on DD CTU2 Carrier A, set sd_priority to lowest value and set sd_load to 0 for both carrier A and B.

68P02900W21-S 3-136 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS traffic planning

GPRS/EGPRS traffic planning

Determination of expected load
The planning process begins by determining the expected GPRS/EGPRS load (applied load) to the system. The next step is to determine the effective load to the system by weighing the applied load by network operating parameters. These parameters consist of the expected BLock Error Rate (BLER) based on the cell RF plan, the protocol overhead (GPRS/EGPRS protocol stack, that is TCP/IP, LLC, SNDCP, RLC/MAC), the expected advantage from V.42bis compression, SIP signaling compression and TCP/IP header compression, and the multislot operation of the mobiles and infrastructure. The effective load at a cell is used to determine the number of GPRS timeslots required to provision a cell. The provisioning process can be performed for a uniform load distribution across all cells in the network or on an individual cell basis for varying GPRS cell loads. The number of GPRS/EGPRS timeslots is the key piece of information that drives the BSS provisioning process in support of GPRS/EGPRS. The planning process also uses network generated statistics, available after initial deployment, for replanning a network. The statistics fall into two categories: PCU specific statistics, and GSN (SGSN + GGSN) statistics.

Network planning flow

The following sections are presented in support of the GPRS/EGPRS network planning:
GPRS/EGPRS network traffic estimation and key concepts

This section introduces the key concepts involved in planning a network. Because GPRS/EGPRS introduces the concept of a switchable timeslot that can be shared by both the GSM circuit-switched infrastructure and by the GPRS/EGPRS infrastructure, much of the content is dedicated to the discussion of this topic.
GPRS/EGPRS air interface planning process

This provides a table of inputs that can serve as a guide in the planning process. In subsequent planning sections, references are made to parameters in this table of inputs. A key piece of information that is needed for the planning process is the RF cell plan. This subsection discusses the impact of different cell plans on the GPRS/EGPRS provisioning process, and how to use this information in order to determine the number of GPRS/EGPRS timeslots that are required on a per cell basis.

68P02900W21-S 01 Feb 2007 3-137

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

GPRS/EGPRS network traffic estimation and key concepts

Introduction to the GPRS/EGPRS network traffic estimation

Packet data notation is interchangeably used in this section. The GPRS/EGPRS network planning is fundamentally different from the planning of circuit-switched networks. One of the fundamental reasons for the difference is that a GPRS/EGPRS network allows the queuing of data traffic instead of blocking a call when a circuit is unavailable. Consequently, the use of Erlang B tables for estimating the number of trunks or timeslots required is not a valid planning approach for the GPRS/EGPRS packet data provisioning process. The GPRS/EGPRS traffic estimation process starts by looking at the per cell GPRS/EGPRS data traffic profile such as fleet management communications, E-mail communications, web browsing, audio/video playing, PoC service and large file transfers. Once a typical data traffic profile mix is determined, the required network throughput per cell can be calculated as measured in kbit/s. The desired network throughput per cell is used to calculate the number of GPRS/EGPRS timeslots required to support this throughput on a per cell basis. The estimated GPRS/EGPRS network delay is derived based on computer modeling of the delay between the Um interface and the Gi interface. The results are provided in this planning guide. The network delay can be used to determine the mean or average time it takes to transfer a file of arbitrary length. In order to simulate the delay, the following factors are considered:

Traffic load per cell Mean packet size Number of available GPRS/EGPRS timeslots Distribution of CS1 to CS4 and MCS-1 to MCS-9 rate utilization Distribution of Mobile Station (MS) multislot operation (1, 2, 3 or 4) BLER

Use of timeslots
The use of timeslots for GPRS/EGPRS traffic is different from how they are used in the GSM circuitswitched case. In circuit-switched mode, an MS is either in idle mode or dedicated mode. In dedicated mode, a circuit is assigned through the infrastructure, whether or not a subscriber is transporting voice or data. In idle mode, the network knows where the MS is, but there is no circuit assigned. In GPRS/EGPRS mode, a subscriber uses the infrastructure timeslots for carrying data only when there is data to be sent. However, the GPRS/EGPRS subscriber can be attached and not sending data, and this still presents a load to the GSN part of the GPRS/EGPRS system, which must be accounted for when provisioning the GPRS infrastructure in state 2 as explained .

68P02900W21-S 3-138 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

The GPRS/EGPRS mobile states and conditions for transferring between states are provided in Table 3-17 and shown in Figure 3-80 in order to specify when infrastructure resources are being used to transfer data. The comment column specifies what the load is on the infrastructure equipment for that state, and only in state 3 does the infrastructure equipment actually carry user data. The infrastructure equipment is planned such that many more MSs can be attached to the GPRS/EGPRS network that is in state 2, than there is bandwidth available to simultaneously transfer data. One of the more significant input decisions for the network planning process is to determine and specify how many of the attached MSs are actively transmitting data in the Ready state 3. In the Standby state 2, no data is being transferred but the MS is using network resources to notify the network of its location. The infrastructure has equipment limits as to how many MSs can be in state 2. When the MS is in state 1, the only required infrastructure equipment support is the storage of MS records in the HLR. Network provisioning needs planning for traffic channels and for signaling channels, also referred to as control channels. The BSS combines the circuit-switched and GPRS control channels together as BCCH/CCCH. The software provides the option of configuring the PBCCH/PCCCH for GPRS/EGPRS control channels.
Table 3-17 MM state model of MS Present state number Next state Present state Condition for state transfer Comments (present state)

IDLE

READY(3)

GPRS/EGPRS Attach

Subscriber is not monitored by the infrastructure that is not attached to GPRS/EGPRS MM, and therefore does not load the system other than the HLR records. Subscriber is attached to GPRS/EGPRS MM and is being actively monitored by the infrastructure that is MS and SGSN establish MM context for subscriber IMSI, but no data transmission occurs in this state. Data transmission through the infrastructure occurs in the Ready state. The ready timer (T3314) default time is 32 seconds. The timer value can be modified during the signaling process by MS request.2 - 60 s in 2 s increments or 61 - 1800 s in 60 s increments.

STANDBY

READY(3)

PDU Transmission

READY

IDLE(1) S

GPRS/EGPR Detach

READY

STANDBY(2)

Ready timer expiry or force to Standby (network or the MS can send a GMM signaling message to invoke force to Standby.)

The MS and SGSN state models are illustrated in Figure 3-80.

68P02900W21-S 01 Feb 2007 3-139

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

Figure 3-80 MM state models for MS and SGSN

IDLE

IDLE

GPRS Attach

GPRS Detach

GPRS Attach

GPRS Detach or Cancel Location

STANDBY timer expiry

READY

STANDBY timer expiry or Cancel Location PDU transmission

READY

READY timer expiry or Force to STANDBY

READY timer expiry or PDU reception Force to STANDBY or Abnormal RLC condition

STANDBY

STANDBY

MM State Model of MS

MM State Model of SGSN

Dynamic timeslot allocation

This section proposes a network planning approach when utilizing dynamic timeslot mode switching of timeslots on a carrier with GPRS/EGPRS timeslots. The radio interface resources can be shared dynamically between the GSM circuit-switched services and GPRS/EGPRS data services as a function of service load and user preference. The timeslots on any carrier can be reserved for packet data use, for circuit-switched use only, or allocated as switchable. Motorola uses the term switchable to describe a timeslot that can be dynamically allocated for packet data service or for circuit-switched service. The timeslot allocation is performed such that the GPRS/EGPRS reserved timeslots are allocated for GPRS/EGPRS use before switchable timeslots. GSM circuit-switched timeslots are allocated to the circuit-switched calls before switchable timeslots. The switchable timeslots are allocated with priority given to circuit-switched calls. Switchable timeslots are compatible with the AMR and GSM half rate features. Timeslots are further allocated by TRAU type and BCCH carrier. 64 kbit/s TRAU are allocated before 32 kbit/s TRAU, 32 kbit/s TRAU are allocated before 16 kbit/s TRAU. In addition, TRAU types are given priority over the BCCH carrier. For EGPRS, 64 kbit/s terrestrial timeslots are needed on the link between the BTS and BSC to support the backhaul required for EGPRS coding schemes MCS-1 to MCS-9. This is a single 64 kbit/s and not adjacent 16 kbit/s subrate timeslots. For Non-BCCH carriers all timeslots should have 64 kbit/s while for BCCH, the BCCH times slot uses 16 kbit/s sub rate.

68P02900W21-S 3-140 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

It is possible for the circuit-switched part of the network to be assigned all of the switchable terrestrial backing under high load conditions and, in effect, block GPRS access to the switchable timeslots at the BTS. In addition, the reserved GPRS pool of backing resources can be taken by the circuit-switched part of the network when BSC to BTSE1outages occur, and when emergency pre-emption type of calls occur and cannot be served with the pool of non-reserved resources.

Background and discussion

Multiple carriers per cell can be configured with GPRS/EGPRS timeslots by the operator for packet data traffic handling capability. By doing so, it can meet the expanding base of packet data subscribers and enhance performance, that is, increase data throughput. There are two options to configure GPRS/EGPRS timeslots on multiple carriers per cell:

Configure for performance This is the network default option. Configure for performance provides the network with the capability to configure all the reserved and switchable GPRS/EGPRS timeslots in a cell contiguously to maximize performance. The contiguous GPRS/EGPRS timeslots configured on a carrier in a cell provide ease in scheduling packet data and the capability to service multiple timeslot GPRS mobiles. If the DTM feature is unrestricted the number of timeslots that can be allocated for SW of each carrier type (64k, 32k, 16k) is restricted to reserve capacity for DTM. However, reserved and switchable GPRS/EGPRS timeslots are granted the best available timeslots with the remainder left for potential conversion to DTM PDCH.

User specified This provides the customer with the flexibility to configure reserve and switchable GPRS/EGPRS timeslots on a per carrier basis in a cell. If DTM feature is unrestricted this option is recommended, and it is suggested that the network planner limit the maximum number of non DTM PDCHs per carrier (max_gprs_ts_per_carrier) so as to free up some resource (TCH) on the best carriers for the PS sessions of DTM MS.

Depending on hardware configuration at a cell, there maybe some limitations on how timeslots are allocated to EGPRS on a carrier. EGPRS is available on Horizon macro II through software upgrade. It is also available on Horizon macro through CTUII upgrade. Since 8-PSK modulated signals do not posses a constant envelope, linearity requirement on the power amplifier is increased to maintain the out-of-band radiation to a minimum. The Compact transceiver unit (CTUII) can operate in two modes: High Power Mode (HPM) or Normal Power Mode (NPM). Each have two sub-modes of operations as far as number of carriers are concerned: Single Density Mode (SDM) or Dual Density Mode (DDM). With the introduction of ITS, EGPRS can operate in SDM and in DDM under which the output power in GMSK mode (irrespective of whether in EGPRS, GPRS, or voice) can be similar or higher than the output power in 8-PSK mode, depending on whether operating in NPM or HPM respectively. CTUII produces the same average output power in EGPRS 8-PSK mode as that of GSM (GMSK) when GSM is configured in DDM. However, when GSM is in SDM, its output power can be up to 5dB higher than EGPRS. There is a settable capping of the output power to equalize the average output power in GMSK and 8-PSK modes, if required. To support EGPRS on DDM CTU2 and retain no HW changes of CTU2, each CTU2 is able to rapidly switch between Double Density modulation (GMSK) and Single Density modulation (8PSK). The power output is not affected by the ITS feature for GMSK and 8PSK. The capping works in 4 steps by setting a data base parameter to the values as shown in Table 3-18.

68P02900W21-S 01 Feb 2007 3-141

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

Table 3-18 Capping settings Step Data base parameter value

0 1 2 >2

5dB higher 2dB higher 1dB higher 0dB difference

Therefore, depending on the configuration of a cell, it is possible that GMSK signals can be set to have, on average, higher power than 8-PSK signals. The following are the scenarios in which there can be up to 5dB difference between GMSK and 8-PSK modulated signals:

A 2-carrier cell (2/2/2) can have one EGPRS carrier and one GSM full power carrier. Some of the timeslots of a 1-carrier cell (1/1/1) are allocated to EGPRS. Different powers are on timeslot by timeslot basis. On the same timeslot allocated to EGPRS, operators can operate on MCS-1 to MCS-4 and MCS-5 to MCS-9.

However, as a general deployment rule the GMSK and 8-PSK signal power levels should be set equally (data base parameter value > 2). {30828}CTU2D output power is depicted in the following Table.
Table 3-19 CTU2D output power GMSK 8PSK

EGSM900 SD EGSM900 DD

63W -0/+2dB 20W -0/+2dB

20W -0/+2dB 8PSK 20W - 0/+2dB (Timeslot Blanking, that is, ITS Mode) 8PSK 9W - 0/+2dB (no Timeslot Blanking, that is, ITS Mode) 16W -0/+2dB 8PSK 16W - 0/+2dB (Timeslot Blanking, that is, ITS Mode 8PSK 8W - /+2dB (no Timeslot Blanking, that is, ITS Mode)

DCS1800 SD DCS1800 DD

50W -0/+2dB 16W -0/+2dB

When the RTF to DRI mapping is performed, the RTFs equipped for EGPRS (that is, 64 kbit/s TRAU) are mapped to SDM or DDM equipped CTUII radios if possible. If the ITS feature is unrestricted and enabled, it is not recommended to map user preferred 64K RTF to improper DRI because it would invalidate the ITS feature. If no single-density or double-density CTUIIs are available and other DRI hardware is available, the EGPRS RTF falls back to 16K TRAU. When such a mapping occurs, the carrier supports signaling, voice and data. {30828} The existing DRI-RTF Mapping functionality is enhanced to cater to the new radio (CTU2D) and enhanced capabilities (CAP and ASTM mode) which are summarized in the following table:

68P02900W21-S 3-142 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

Table 3-20 DRI-RTF Mapping functionality DRI-RTF Mapping functionality CAP and ASTM mode

SD A DD DD-B PWR-A PWR-B CAP-A CAP-B

CTU2/CTU2D in Single Density (Level0) CTU2/CTU2D GMSK Carrier A (Level1) CTU2/CTU2D GMSK Carrier B with DD-A (Level1) CTU2/CTU2D Edge Carrier A (Level2) CTU2/CTU2d D GMSK Carrier B with PWR-A (Level2) CTU2D Edge Carrier A (Level3/4) CTU2D Edge Carrier B with CAP-A (ASYM supported Level4) or CTU2D GMSK Carrier B with CAP-A (ASYM not supported Level3)
Is

Where

Level 0 Level 1 Level 2

basic SD Edge/GMSK operation (CTU2/CTU2D Equivalent) basic DD GMSK/GMSK Operation (CTU2/CTU2D Equivalent) Level 1 + Basic DD Edge/GMSK Operation with A Edge and B GMSK with Timeslot Blanking (as per GSR8 ITS) (CTU2/CTU2D Equivalent) Level 1 + Enhanced DD Edge/GMSK removes B TS Blanking (CTU2D Only) Level 3 + Edge/Edge with B restricted to UL GMSK Only (CTU2D Only)

Level 3 Level 4

The mapping preferences are given by:

Edge RTF Priority: SD / CAP-A / CAP-B (1) / PWR-A / CAP-B (2,3) / PWR-B (3)
o o o

When ASYM enabled When ASYM disabled Edge downgraded to 16K CAP-B is preferred due to removal of timeslot blanking and the use is unrestricted. It results in PWR-A Edge being either stolen or downgraded to 16K.

Non Edge BCCH RTF Priority: CAP-B (1) / PWR-A / CAP-A / SD / PWR-B (2)
o o

Non Edge non BCCH RTF Priority: As legacy except CAP-B is considered unrestricted.

Due to the importance of the BCCH carrier, the BCCH is remapped onto an available DRI, even if that DRI is unable to support EGPRS. In the event that the BCCH RTF is remapped onto a DRI that cannot support EGPRS, the carrier can only support GSM voice calls.

68P02900W21-S 01 Feb 2007 3-143

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

The BCCH RTF always attempts to migrate to a CTUII if possible. This requirement primarily comes into play post-initialization when the BCCH RTF fails. The BSS software attempts to both maintain EGPRS service and keep the BCCH on a CTUII if at all possible. If the BCCH RTF is configured for EGPRS and there is only one SDM CTUII available, the BCCH RTF is mapped onto that CTUII, since EGPRS service and EGPRS one phase access would still be available. However, if the BCCH RTF is not configured with 64 kbit/s terrestrial backing and there is only one CTUII available, the BCCH is moved to a non-CTUII radio. At initialization the BSS should load up non-CTUII hardware with 16K/32K carriers as much as possible. Thus, the BSS software attempts to assign EGPRS carriers onto EGPRS-capable hardware first, and then assign carriers to the rest of the hardware in its usual fashion. The BSS ignores the pkt_radio_type value of the BCCH carrier if PBCCH/PCCCH is enabled in the cell. The minimum backhaul requirement is determined to be 3 DS0s since a minimum of 2 DS0s are required to support voice traffic if all 8 timeslots on a carrier are configured as TCH and the additional third DS0 provides the bare minimum backhaul required for configurations when 1 to 3 timeslots on the carrier are configured as PDTCHs. The third DS0 also helps in reducing the time required to start servicing the first PDTCH timeslot by keeping this backhaul synchronized between the BTS and the PCU even when there are no PDTCHs active on a carrier (provided there are enough GDS resources available across the cell). The RTF allow_32k_trau and use_bcch_for_gprs attributes were replaced with a new parameter pkt_radio_type. pkt_radio_type also accommodates the 64K backhaul necessary to support EGPRS and makes it possible to configure RTFs on which GPRS data is specifically disallowed. Technical Description: BSS Implementation (68PO2901W36) provides a complete description of these commands. Depending on the restrictions imposed on GPRS (32 kbit/s TRAU) and EGPRS (enabled or disabled), pkt_radio_type can be set between 0 (no packet data) and 3 (64k). Every RTF equipped as pkt_radio_type = 3 (64K) also has a configurable attribute rtf_ds0_count. If the VersaTRAU feature is unrestricted, the operator can configure the RTF backhaul for an EGPRS capable carrier to be between 3 and 8 64 kbit/s terrestrial timeslots. The BSS supports a minimum of zero to a maximum of 30 GPRS/EGPRS timeslots per cell. The sum of reserved and switchable GPRS/EGPRS timeslots should not exceed 30. The GPRS/EGPRS carriers can be provisioned to carry a mix of circuit-switched traffic and GPRS traffic. There are three provisioning choices combined with timeslot configuration options selected :

Reserved GPRS/EGPRS timeslots allocated only for packet data use. Switchable timeslots dynamically allocated for either GSM circuit-switched traffic or GPRS/EGPRS traffic (designated as switchable timeslots by Motorola). Remaining timeslots on the carrier with GPRS/EGPRS timeslots, if any, only for circuitswitched use.

Planning goals - reserved against switchable timeslots

The network planner can consider the following network planning goals when trying to determine when to use reserved timeslots against when to use switchable timeslots:

Use reserved timeslots to guarantee a minimum quality of service (QoS) for packet data users. Use switchable timeslots to provide low circuit mode blocking and high packet data throughput when the voice busy hour and the GPRS busy hour do not coincide. Use switchable timeslots to provide higher packet data throughput without increasing the circuit-switched blocking rate. If all the GPRS/EGPRS timeslots are provisioned as switchable, the last available timeslot is not given to a circuit-switched call until transmission of all the GPRS/EGPRS traffic on that last timeslot is completed. Therefore, there is a circuit-switched blocking on that last timeslot on the cell until the timeslot becomes free.

68P02900W21-S 3-144 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

Use switchable timeslots to provide some GPRS/EGPRS service coverage in low GPRS traffic volume areas. Use switchable timeslots to provide extra circuit-switched capacity in spectrum limited areas. In order to make the decision on how to best allocate reserved and switchable timeslots, the network planner needs to have a good idea of the traffic level for both services. The proposal in this planning guide is to drive the allocation of switchable timeslots and reserved GPRS/EGPRS timeslots from a circuit-switched point of view.

Start by looking at the circuit-switched grade of service objectives and the busy hour traffic level, as measured in Erlangs. Once the circuit-switched information is known, the potential impact on switchable timeslots can be analyzed. The GPRS/EGPRS QoS can be planned by counting the number of available reserved GPRS/EGPRS timeslots, and by evaluating the expected utilization of the switchable timeslots by the circuit-switched part of the network during the GPRS/EGPRS busy hour. If DTM feature is unrestricted, TCHs are converted to DTM PDCHs in order to support DTM mode (CS + PS) sessions. Therefore, when considering the circuit-switched planning information, the network planner should account for the fact that some circuit-switched timeslots can be converted for the PS sessions of DTM subs. This is depends on the DTM MS penetration, DTM MS behavior, Max_DTM_TS configuration and DTM request blocking rate, and so on. The PDCH planning considers only the GPRS PS traffic excluding PS in DTM mode. DTM PS traffic is considered in Max_DTM_TS planning (as described in the section DTM Timeslots planning considerations). The priority of timeslot allocation takes into account the factors in the following list. The highest priority starts with number 1 and the lowest priority is number 5. In the examples that follows, priorities 3 and 4 are not considered. 1. 2. 3. TRAU-Type - in the order 64K, 32K, and 16K. BCCH Carrier. Most INS number of timeslots: At this step, the following are taken into account:
o o o

Continuous timeslots SD load (signaling load) SD priority

4.

The highest local carrier id: This may or may not be corresponding to the RTF index. So, the highest local carrier id may not necessarily be RTF + 3 if there is a 4 carrier cell (RTF + 0 to RTF +3). Hence, the RTF index is irrelevant. TS priority in the following order:
o o o

5.

Reserved Switchable Circuit-switched (T)

When DTM feature is unrestricted, reserved or switchable timeslots allocation should take into account the performance of DTM PDCHs. That means some candidate timeslots on the best performance carriers should be left behind for the DTM PDCHs. The max_gprs_ts_carrier setting should reserve some timeslots in these carriers for DTM PDCHs. If DTM feature is unrestricted, res_gprs_pdchs + sw_gprs_pdchs + max_dtm_ts <=30 and also res_gprs_pdchs + sw_gprs_pdchs >=1 if max_dtm_ts > 0. Otherwise, res_gprs_pdchs + sw_gprs_pdchs <=30 for DTM feature is restricted.

68P02900W21-S 01 Feb 2007 3-145

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

The 64k DDM CTU2 carrier A is less preferred for 64k PDCH placement and its paired 32k carrier B is less preferred for 32k PDCH placement. {30828} With the removal of timeslot blanking for CAP configurations of CTU2D (CAP mode), both Carrier A and Carrier B is considered as independent and non-interacting when placing PDs, that is, an EDGE PD placed on A has no impact on Bs ability and priority for the support of EDGE/GPRS PDs. When CTU2D is configured in ASYM mode, 64K Carrier A is preferred to 64K Carrier B due to asymmetric capability of Carrier B UL restriction to GMSK.

Carrier timeslot allocation examples

The following configuration examples explore different ways to configure timeslots in a cell. Some of these examples also illustrate the usage of the PDTCH/backhaul proportion when configuring the timeslots on an EGPRS capable carrier (pkt_radio_type set to 3) with a configurable RTF backhaul (using the rtf_ds0_count parameter). In the examples, the following annotations are used: B = BCCH/CCCH timeslot for GPRS/GSM signaling. SD = The ith SDCCH timeslot for GSM signaling. The subscript represents the ascending order in which the SDCCH timeslots are allocated across carriers. P = PCCCH timeslot for GPRS/EGPRS signaling. RG = Reserved GPRS timeslot (EGPRS cannot be used, if non-64K RTF). RE = Reserved EGPRS timeslot (GPRS can be used). SG = Switchable GPRS timeslot (EGPRS cannot be used, if non-64K RTF). SE = Switchable EGPRS timeslot (GPRS can be used). T = Circuit-switched use only timeslots. X = Blanked-out timeslots (on DDM CTU2 Carrier B as Carrier A is capable of EGPRS).

Example 1
There are 15 switchable GPRS/EGPRS timeslots and 10 reserved GPRS/EGPRS timeslots in a 5 carrier cell. This example assumes that the VersaTRAU feature is not purchased. In this case, the RTF backhaul for an RTF with pkt_radio_type set to 3 (64K) is defaulted to 7 DS0s if it is the BCCH RTF or 8 DS0s if it is a non-BCCH RTF. The following are assumed:
pkt_radio_type is set to: o o o o

PGSM BCCH RTF: 64K (3) EGSM 2 non-BCCH carriers: 32 k (2) PGSM 1 non-BCCH carrier: 16K (1) PGSM 1 non-BCCH carrier: None (0)

One CTUII and four non-CTUII GPRS 32K and EGPRS unrestricted

68P02900W21-S 3-146 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

{30828} Assuming sd_load of 2, sd_priority is the same for all the carriers, and PBCCH is not enabled, the preferred number of SDCCH is 64, HR is disabled, and the timeslot allocation is shown as illustrated. The GPRS/EGPRS timeslots are configured contiguously for performance. The packet data timeslots are arranged as shown in the table . The BCCH RTF is mapped to CTUII and all the reserved timeslots are EGPRS capable. The non-BCCH 32K carriers are used for GPRS CS1 to CS4. The remaining switchable timeslots are mapped to one of the non-BCCH 16K carrier. {30828}
Table 3-21 Arrangement of packet data timeslots for example 1 Carrier TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7

BCCH 64K (CTUII) Non-BCCH 32K (non-CTUII) Non-BCCH 32K(non-CTUII) Non-BCCH 16K (non-CTUII) Non-BCCH

B SD7 SD8 SD3 SD1

SD5 SG SG SD4 SD2

SD6 SG SG SG T

RE RG SG SG T

RE RG SG SG T

RE RG SG SG T

RE RG SG SG T

RE RG SG SG T

Example 2
There are 15 switchable GPRS/EGPRS timeslots and 10 reserved GPRS/EGPRS timeslots in a 5 carrier cell. This example assumes that the VersaTRAU feature is not purchased. In this case, the RTF backhaul for an RTF with pkt_radio_type set to 3 (64K) is defaulted to 7 DS0s if it is the BCCH RTF or 8 DS0s if it is a non-BCCH RTF. The following are assumed:
pkt_radio_type is set to: o o o o

BCCH RTF: None (0) 1 non-BCCH carrier: 64K (3) 2 non-BCCH carriers: 32K (2) non-BCCH carrier: 16K (1)

One CTUII and four non-CTUII GPRS 32K and EGPRS unrestricted

The GPRS/EGPRS timeslots are configured contiguously for performance. The packet data timeslots are arranged as shown in the table . The BCCH RTF is mapped to non-CTUII DRI and all the circuit-switched timeslots are allocated to it. The EGPRS and GPRS timeslots are allocated to non-BCCH carriers as shown.
Table 3-22 Arrangement of packet data timeslots for example 2 Carrier TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7

BCCH 16K (non-CTUII) Non-BCCH 64K (CTUII) Non-BCCH 32K(non-CTUII) Non-BCCH 32K (non-CTUII) Non-BCCH 16K (non-CTUII)

B RE SG SG T

SD RE SG SG SG

T RE SG SG T

T RE SG SG T

T RE SG SG T

T RE SG SG T

T RE SG SG T

T RE SG SG T

68P02900W21-S 01 Feb 2007 3-147

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

Example 3
There are 8 switchable GPRS/EGPRS timeslots and 4 reserved GPRS/EGPRS timeslots in a 5 carrier cell. This example assumes that the VersaTRAU feature is not purchased. In this case, the RTF backhaul for an RTF with pkt_radio_type set to 3 (64K) is defaulted to 7 DS0s, if it is the BCCH RTF or 8 DS0s if it is a non-BCCH RTF. The following are assumed:
pkt_radio_type is set to: o o o o o o

PGSM BCCH RTF: 64K (3) and PBCCH enabled with sd_priority = 255 PGSM 2 non-BCCH carriers: 32K (2) with sd_priority = 100 EGSM non-BCCH carriers: None (0) with sd_priority = 255 EGSM non-BCCH carrier: None (0) with sd_priority = 200 One CTUII and four non-CTUII GPRS 32K and EGPRS unrestricted

max_gprs_ts_carrier = 4

{30828} Assuming sd_load of 2 for all the carriers, and PBCCH not enabled, preferred number of SDCCH being 64, PBCCH is enabled (BSS level and cell level, and at the carrier level hr_allowed) the timeslot allocation is shown in Table 3-23. This example also demonstrates how resources can be set aside for DTM mode sessions (which need allocation to TCHs). In the example a DTM allocation could be made on TS2 and TS3 for the first three carriers. There are more options on the last two carriers, assuming they are GPRS capable (if not, it is not possible to make a DTM allocation on them).
Table 3-23 Arrangement of packet data timeslots for example 3 Carrier TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7

BCCH 64K (CTUII) Non-BCCH 32K (non-CTUII) Non-BCCH 32K(non-CTUII) Non-BCCH 16K (non-CTUII) Non-BCCH 16K (non-CTUII)

B SD1 SD2 SD7 SD5

P SD3 SD4 SD8 SD6

T T T T T

T T T T T

RE SG SG T T

RE SG SG T T

RE SG SG T T

RE SG SG T T

Example 4
There are 14 switchable GPRS/EGPRS timeslots and 10 reserved GPRS/EGPRS timeslots in a 5 carrier cell. This example assumes that the VersaTRAU feature is not purchased. In this case, the RTF backhaul for an RTF with pkt_radio_type set to 3 (64K) is defaulted to 7 DS0s, if it is the BCCH RTF or 8 DS0s if it is a non-BCCH RTF. The following are assumed:
pkt_radio_type is set to: o o o

BCCH RTF: None (0) 2 non-BCCH carriers: 64k (3) 1 non-BCCH carrier: 32k (2)

68P02900W21-S 3-148 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

1 non-BCCH carrier: None (0)

Two CTUII and three non-CTUII GPRS 32K and EGPRS unrestricted
pccch_enabled = 1

In this example, the BCCH carrier is not configured to be used as the carrier for GPRS/EGPRS. However, since there are two CTUIIs available, BCCH is mapped to CTUII even though is not capable of supporting EGPRS. Additionally, the non-BCCH carrier configured with 64k backhaul is not used for packet data. PCCCH, however, is always allocated on the BCCH carrier. Therefore, on the BCCH carrier, TS2 is allocated to PCCCH and TS3 to TS7 is allocated to circuit-switch TCH only. The following table shows the timeslot allocation.
Table 3-24 Arrangement of packet data timeslots for example 4 Carrier TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7

BCCH 16K (CTUII) Non-BCCH 64K (CTUII) Non-BCCH 64K(non-CTUII) Non-BCCH 32K (non-CTUII) Non-BCCH 32K (non-CTUII)

B
RE

SD
RE

P
RE

T
RE

T
RE

T
RE

T
RE

T
RE

T
SG T

T
SG T

T
SG T

T
SG T

T
SG T

T
SG T

T
SG T

T
SG T

Example 5
There are 12 switchable GPRS/EGPRS timeslots and 10 reserved GPRS/EGPRS timeslots in a 6 carrier cell. This example assumes that the VersaTRAU feature is not purchased. In this case, the RTF backhaul for an RTF with pkt_radio_type set to 3 (64K) is defaulted to 7 DS0s if it is the BCCH RTF or 8 DS0s if it is a non-BCCH RTF. The following are assumed:
pkt_radio_type is set to: o o o o

BCCH RTF: 64K (3) 1 non-BCCH carrier: 64K (3) 1 non-BCCH carrier: 32K (2) 3 non-BCCH carriers: None (0)

Three CTUII and three non-CTUII GPRS 32K and EGPRS unrestricted Two (AMR or GSM) half-rate enabled carriers

68P02900W21-S 01 Feb 2007 3-149

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

The following table shows the timeslot allocation.

Table 3-25 Arrangement of packet data timeslots for example 5 Carrier TS0 TS1 TS2 TS3
RE SE SG T T T

TS4
RE RE SG T T T

TS5
RE RE SG T T T

TS6
RE RE SG T T T

TS7
RE RE SG T T T

BCCH 64K (CTUII) Non-BCCH 64K (CTUII) Non-BCCH 32K(non-CTUII) Non-BCCH 16K (non-CTUII) Non-BCCH 16K (hr enabled) (non-CTUII) Non-BCCH 16K (hr enabled) (non-CTUII)

B
SE SG T T T

SD
SE SG T T T

P
SE SG T T T

Example 6
There are 4 switchable EGPRS timeslots and 4 reserved EGPRS timeslots in a 4 carrier cell. The following are assumed:
pkt_radio_type set to BCCH RTF 64k (3)

3 non-BCCH carrier: 64k (3) 3 CTUIIs EGPRS unrestricted

Table 3-26 shows the timeslot allocation. Table 3-26 Arrangement of packet data timeslots for example 6 Carrier TS0 TS1 TS2
SE SE

TS3
SE SE

TS4
RE RE

TS5
RE RE

TS6
RE RE

TS7
RE RE

BCCH 64K (CTUII) Non-BCCH 64K (CTUII) Non-BCCH 64K(CTUII) Non-BCCH 64K (CTUII)

B
SE

SD
SE

T
T

T
T

T
T

T
T

T
T

T
T

T
SE

T
SE

Example 7
There are 10 switchable GPRS/EGPRS timeslots and 12 reserved GPRS/EGPRS timeslots in a 6 carrier cell. The following are assumed:
pkt_radio_type set to: o o

BCCH RTF: 64k (3), rtf_ds0_count = 4 1 non-BCCH carrier: 64k (3), rtf_ds0_count = 5

68P02900W21-S 3-150 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

o o

1 non-BCCH carrier: 32k (2) 3 non-BCCH carriers None (0)

Three CTUII and three non-CTUII GPRS 32K and VersaTRAU (and therefore EGPRS) unrestricted Two (AMR or GSM) half-rate enabled carriers

The following table shows the timeslot allocation.

Table 3-27 Arrangement of packet data timeslots for example 7 Carrier TS0 TS1 TS2 TS3
RE RE SG T T T

TS4
RE RE SG T T T

TS5
RE RE SG T T T

TS6
RE RE SG T T T

TS7
RE RE SG T T T

BCCH 64K (CTUII) Non-BCCH 64K (CTUII) Non-BCCH 32K(CTUII) Non-BCCH 16K (non-CTUII) Non-BCCH 16K (hr enabled) (non-CTUII) Non-BCCH 16K (hr enabled) (non-CTUII)

B
SE SG T T T

SD
SE SG T T T

RE
RE SG T T T

Example 8
There are 5 switchable GPRS/EGPRS timeslots and 4 reserved GPRS/EGPRS timeslots in a 2 carrier cell. The following are assumed:
pkt_radio_type set to: o o

BCCH RTF: 64K (3), rtf_ds0_count = 6 1 non-BCCH carrier: 64K (3), rtf_ds0_count = 6

CTUII (DDM) EGPRS and VersaTRAU unrestricted

pccch_enabled = 1

The following table shows the timeslot allocation.

Table 3-28 Arrangement of packet data timeslots for example 8 Carrier TS0 TS1 TS2 TS3
T SG

TS4
SE X

TS5
RE X

TS6
RE X

TS7
RE X

BCCH 64K (CTUII DD Carrier A) Non-BCCH 64K (CTUII DD Carrier A)

B
SG

SD
SG

P
X

Non-BCCH 64K are downgraded to 16K. The maximum PDs configuration for two carriers of DD CTU2 is 8 if Carrier A has EGPRS PDs. The requested 9 PDs cannot be all met.

68P02900W21-S 01 Feb 2007 3-151

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

Example 9
{30828} There are 8 switchable GPRS/EGPRS timeslots and 4 reserved GPRS/EGPRS timeslots in a 4 carrier cell. The CTU2D Asymmetric feature is unrestricted and ASYM mode is enabled for the site on which these 4 carriers are configured. PBCCH is enabled and the preferred number of SDCCH is 80. The sd_priority = 2 and sd_load = 3 for all the carriers.

1 CTU2D (CAP) and 1 CTU2 (PWR) PGSM BCCH carrier: 64K 1 PGSM non-BCCH carrier: 64K with rtf_ds0_count = 6, mapped to CTU2D CAP_B 1 PGSM non-BCCH carrier: 64K with rtf_ds0_count = 4, mapped to CTU2D PWR_A 1 PGSM non-BCCH carrier: 32K

Table 3-29 Arrangement of packet data timeslots for example 9 Carrier TS0 TS1 TS2
SD(4) SD(3) SD(9) T

TS3
SD(5) SE T T

TS4
SD(6) SE T T

TS5
RE SE SE T

TS6
RE SE SE T

TS7
RE SE SE T

BCCH 64K (CTU2D CAP A) Non-BCCH 64K (CTU2D CAP B) Non-BCCH 64K (CTU2D PWR A) Non-BCCH 32K (CTU2D PWR B)

B
SD(1) SD(7) SD(10)

PB
SD(2) SD(8) T

BSS timeslot allocation methods

The BSS algorithm that is used in order to determine allocation of switchable timeslots gives priority to circuit-switched calls. Consequently, if a switchable timeslot is being used by a packet data mobile and a circuit-switched call is requested after all other circuit-switched timeslots are used, the BSS takes the timeslot away from the packet data mobile and gives it to the circuit-switched mobile, except when the switchable timeslot to be stolen is the last packet data timeslot in the cell and the protect_last_ts element is enabled. The switchable timeslot is re-allocated back to the packet data mobile when the circuit-switched call ends. The number of reserved packet data timeslots can be changed by the operator to guarantee a minimum number of dedicated packet data timeslots at all times. The operator provisions the packet data timeslots on a carrier by selecting the number of timeslots that are allocated as reserved and switchable, and not by specifically assigning timeslots on the carrier. Motorola has implemented an idle circuit-switched parameter that enables the operator to strongly favor circuit-switched calls from a network provisioning perspective. By setting the idle parameter to 0, this capability is essentially turned off. When a circuit-switched call ends on a switchable packet data timeslot and the number of idle circuitswitched timeslots is greater than an user defined threshold, the BSS re-allocates the borrowed timeslot for packet data service. When the number of idle timeslots is less than or equal to a programmable threshold, the BSS does not allocate the timeslot back for packet data service, even if it is the last available timeslot for packet data traffic.

68P02900W21-S 3-152 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

Stolen timeslots
A switchable timeslot can be stolen at any time for use by a CS call, except when the switchable timeslot to be stolen is the last packet data timeslot in the cell and the protect_last_ts element is enabled. When a switchable timeslot needs to be stolen for use by a CS call, the switchable timeslot to be stolen is the last packet data timeslot in the cell, and the protect_last_ts element is enabled, the timeslot is stolen only if there is no data transfer active or queued for the timeslot. If there are any reserved packet data timeslots in the cell, the switchable timeslots are not protected from being stolen for use by circuit-switched calls. The BSS supports dynamic switching between switchable timeslots and circuit-switched timeslots and vice versa. Switchable packet data timeslots are stolen starting with the lowest numbered GPRS timeslot on a carrier to maintain continuous packet data timeslots. The BSS selects which switchable packet data timeslot is stolen based on an algorithm that takes into account the pkt_radio_type (GPRS/EGPRS capability), the associated RTF backhaul (configured as rtf_ds0_count for EGPRS capable carriers if VersaTRAU is unrestricted or statically computed in other cases depending on the pkt_radio_type) and the number of switcahble or reserved timeslots already on the carrier. A rank order based on the backhaul to PDTCH ratio is established at the time of the initial air timeslot allocation. This rank order is also used at the time of allocating the reserved and switchable timeslots in the cell. The switchable timeslots are the ones that result in the least degradation in the backhaul to PDTCH ratio for the cell when they get stolen for voice traffic. When (AMR or GSM) half rate is enabled on one or more (RTFs assigned to) carriers in a cell and some number of timeslots are reserved for half rate usage (hr_res_ts), then the BSS attempts to ensure that the last timeslots to be allocated within a cell are half rate capable. Therefore switchable timeslots are allocated to full rate calls before the reserved half rate capable timeslots (the only exception to this being when the only available resource able to support the full rate request is the last GPRS/EGPRS timeslot, and the protect last ts functionality is enabled). When the ITS feature is unrestricted and enabled and a voice call steals one EGPRS PD timeslot on a DD CTU2 Carrier A, the corresponding blanked-out timeslot on Carrier B comes back into service. If the stolen EGPRS timeslot on DD CTU2 comes back to PDCH, the corresponding blanked-out timeslot on Carrier B is configured back to OOS. {30828} CTU2D PWR mode is treated the same as the ITS mode whereby the stolen operation is identical.

Contiguous timeslots
Multislot mobile operation needs that contiguous timeslots are available. The BSS takes the lowest numbered switchable timeslot in such a manner as to maintain contiguous GPRS/EGPRS timeslots for multislot GPRS/EGPRS operation and at the same time maintain an optimum ratio of PDTCH/available backhaul per carrier across the cell. The BSS attempts to allocate as many timeslots as requested in multislot mode, and then backoff from that number as timeslots are not available. For example, suppose that timeslots 3 and 4 are switchable, and timeslots 5, 6, and 7 are GPRS/EGPRS reserved (refer to Figure 3-81). When the BSS needs to re-allocate a switchable timeslot from GPRS/EGPRS mode to circuitswitched mode, the BSS assigns timeslot 3 before it assigns timeslot 4 for circuit-switched mode. Figure 3-81 provides timeslot allocation with reserved and switchable timeslots.

68P02900W21-S 01 Feb 2007 3-153

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

Figure 3-81 Carrier with reserved and switchable GPRS/EGPRS timeslots

S S R R R

TS0

TS7

R: Reserved PDTCH. S: Switchable PDTCH. Blank: Circuit-switched use only timeslots.

If the emergency call pre-emption feature is enabled, the BSS selects the air timeslot that carries the emergency call from the following list (most preferable listed first):

Idle circuit-switched Idle or in-service switchable GPRS/EGPRS timeslot (from lowest to highest) In-service circuit-switched Idle or in-service reserved GPRS/EGPRS timeslot (from lowest to highest)

DTM PS timeslot allocation method is done by resource allocation algorithm. The DTM PS timeslots are converted from TCH dynamically per request. When a DTM MS in dedicated mode requests the timeslots for the PS session, some TCHs in the cell are required as, and if necessary converted into, DTM PDCHs. The number of timeslots allocated to the CS connection of a DTM MS is limited to one. For the PS sessions of a DTM MS, the system supports DTM multislot class 5, 9 and also class 11 when EDA is supported. If EDA is not enabled, the system only supports DTM class 5 and 9 configurations, that is, 1 DL: 1 UL and 2 DL: 1 UL respectively. The CS and PS timeslots allocated to a DTM MS are contiguous, and DTM PDCHs are also adjacent with each other. Half-rate PDCH is not supported in DTM mode. For example, suppose that timeslots 0, 1, 2 and 3 are TCH, and timeslots 4 and 5 are switchable, and timeslots 6, and 7 are GPRS/EGPRS reserved. When the BSS allocates 2 PDCHs and 1 TCH for a DTM MS in this carrier, Figure 3-82 provides a timeslot allocation for this mobile.
Figure 3-82 Carrier with reserved, switchable GPRS/EGPRS timeslots and DTM PDCHs

Provisioning the network with switchable timeslots

Provisioning the network with switchable timeslots can offer flexibility in the provisioning process for combining circuit-switched and GPRS/EGPRS service. This flexibility is in the form of additional available network capacity to both the circuit-switched and GPRS/EGPRS subscribers, but not simultaneously. Because the BSS favors circuit-switched use of the switchable timeslots, the network planner should examine the demand for switchable timeslots during the circuit-switched busy hour and during the GPRS/EGPRS busy hour.

68P02900W21-S 3-154 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

Normally, the operator provisions the circuit-switched radio resource for a particular Grade Of Service (GOS), such as 2%. This means that 2 out of 100 circuit-switched calls are blocked during the busy hour. If the operator chooses to use the new switchable timeslot capability, it is now possible to share some GPRS timeslots between the circuit-switched calls and the GPRS/EGPRS calls. When DTM feature is enabled, the number of switchable timeslots for normal GPRS/EGPRS data use should consider the situation for only pure GPRS/EGPRS data use excluding DTM PS traffic. During the cell planning, network planner can get the circuit-timeslots utilization for DTM by analysis of Max_DTM_TS and statistic DTM_TS_Usage. During the circuit-switched busy hour, the circuit-switched use of these switchable timeslots dominate their use. The circuit-switched side of the network has priority use of the switchable timeslots, and attempts to provide a better grade of service as a result of the switchable timeslots being available. The examples in Table 3-29 and Table 3-30 assumes that the planning is being performed for a cell that has two carriers. The first carrier is for circuit-switched used as shown in Figure 3-83. The second carrier is a carrier with GPRS/EGPRS timeslots; all eight timeslots are configured as switchable, as shown in Figure 3-84. The table was created using the Erlang B formula in order to determine how many circuit-switched timeslots are required for a given grade of service. The table covers the range of 2 Erlangs to 9 Erlangs of circuit-switched traffic in order to show the full utilization of two carriers for circuitswitched calls. The purpose of the table is to show how the circuit-switched side of the network allocates switchable timeslots during the circuit-switched busy hour in an attempt to provide the best possible GOS, assumed to be 0.1% for the purposes of this example. The comments column in the table is used to discuss what is happening to the availability of switchable timeslots for GPRS/EGPRS data use as the circuit-switched traffic increases, as measured in Erlangs. This example shows some Erlang traffic levels that cannot be adequately served by two carriers at the stated grade of service listed in the tables. This occurs at the 7 and 8 Erlang levels for 0.1% GOS. In these cases, all of the switchable timeslots are used up on the second carrier in an attempt to reach a 0.1% GOS. For the 9 Erlang traffic level, 2 carriers is not enough to serve the circuit-switched traffic at a 2% GOS. This would indicate a need for a second circuit-switched carrier, in addition to the first circuit-switched carrier and the carrier with GPRS/EGPRS timeslots. AMR or GSM half rate usage should be considered when determining the number of circuit switched timeslots required. Two half rate circuit-switched calls can be carried in a single timeslot (provided of course that the (RTF assigned to) carrier is half rate enabled). The number of actual (circuit-switched) calls that can expect to be using half rate depend upon such factors as user (both BSS and MSC) preference, mobile (AMR capable, GSM half rate) penetration, mobile preference, RF conditions, handoff parameter and threshold setting, cell congestion levels, and so on. Once an estimate of half rate usage is determined, it can be used to determine if the GOS can be met. Table 3-30 and Table 3-31 show two examples using half rate assumptions.

68P02900W21-S 01 Feb 2007 3-155

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

Table 3-30 Switchable timeslot utilization (Part A) GOS Planned circuitswitched Erlangs/cell Total number of circuitswitched timeslots required Number of switchable timeslots necessary to provide GOS Comments

2%

Outside busy hour time periods, the carrier most likely carries only packet data traffic. Therefore, packet data. network planning should be performed, assuming there are 8 timeslots available for GPRS traffic. During circuit- switched busy hour, at least 2 of the switchable timeslots are occasionally used by the circuit-switched side of the network in an attempt to provide the best possible GOS - assumed to be 0.1%. During the circuit-switched busy hour, 2 of the switchable timeslots are occasionally used by the circuit-switched side of the network in an attempt to provide the 2% GOS. During the circuit-switched busy hour, 4 of the switchable timeslots are occasionally used by the circuit-switched side of the network in an attempt to provide the best possible GOS - assumed to be 0.1%. All the switchable timeslots are occasionally used to provide 0.1% GOS. Continued

0.1%

2%

0.1%

10

2% 0.1% 2% 0.1%

4 4 5 5

9 12 10 14

3 6 4 8

2%

12

68P02900W21-S 3-156 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

Table 3-30 Switchable timeslot utilization (Part A) (Continued) GOS Planned circuitswitched Erlangs/cell Total number of circuitswitched timeslots required Number of switchable timeslots necessary to provide GOS Comments

0.1%

15

There are not enough switchable timeslots to provide 0.1% GOS. There are not enough switchable timeslots to provide 0.1% GOS. All the switchable timeslots are occasionally used to provide 2% GOS. There are not enough switchable timeslots to provide 0.1% GOS. There are not enough switchable timeslots to provide the 2% GOS. There are not enough switchable timeslots to provide the 0.1% GOS. Assumption is 100% half rate utilization and all carriers are capable of half rate. All of the switchable timeslots are occasionally used to satisfy the 2% GOS. Assumption is 50% half rate utilization and all carriers are capable of half rate.

2% 0.1%

7 7

13 17

7 11

2%

14

0.1%

18

12

2%

15

0.1%

20

14

2%

10 20 half rate calls at 2 subchannels per timeslot 14 9 full rate calls (9 timeslots) + 9 half rate calls (5 timeslots)

0.1%

68P02900W21-S 01 Feb 2007 3-157

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

Table 3-31 Switchable timeslot utilization (Part B) GOS Planned circuitswitched Erlangs/cell Total number of circuitswitched timeslots required Number of switchable timeslots necessary to provide GOS Comments

2%

15

There are not enough switchable timeslots to provide the 2% GOS. There are not enough switchable timeslots to provide the 0.1% GOS. Assumption is 100% half rate utilization and all carriers are capable of half rate. All of the switchable timeslots are occasionally used to satisfy the 2% GOS. Assumption is 50% half rate utilization and all carriers are capable of half rate.

0.1%

20

14

2%

10 20 half rate calls at 2 subchannels per timeslot 14 9 full rate calls (9 timeslots) + 9 half rate calls (5 timeslots)

0.1%

Timeslot allocation for 2 carrier site (1 circuit-switched + 1 GPRS/EGPRS)

Figure 3-83 shows one circuit-switched carrier with one BCCH/CCCH timeslot, one SDCCH timeslot, and six TCH timeslots. Figure 3-83 Circuit-switched carrier, 1 BCCH/CCCH + 1 SDCCH + 6 TCH timeslots
B SD

TS0

TS7

B: BCCH/CCCH for GPRS/GSM signalling. SD: SDCCH for GSM signalling. Blank: Circuit-switched use only timeslots.
Figure 3-84 shows one carrier for GPRS/EGPRS traffic with all timeslots (eight TCHs) designated as switchable. Figure 3-84 1 carrier, all timeslots (8 TCHs) designated as switchable
S S S S S S S S

TS0

TS7

S: Switchable TCH.
Table 3-30 and Table 3-31 show the switchable timeslot utilization.

68P02900W21-S 3-158 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS network traffic estimation and key concepts

Recommendation for switchable timeslot usage

The following recommendation is offered when using switchable timeslots. It is important to determine the GOS objectives for circuit-switched traffic and QoS objectives for packet data traffic before selecting the number of switchable timeslots to deploy. During the circuit-switched busy hour, potentially all switchable timeslots are occasionally used by the circuit-switched calls. The circuit-switched timeslot allocation mechanism continues to assign switchable timeslots as circuit-switched timeslots as the circuit-switched packet data continues to increase. Therefore, if there is a minimum capacity requirement for GPRS services, the network planner should plan the carrier with enough reserved timeslots in order to handle the expected packet data traffic. This ensures that there is a minimum guaranteed network capacity for the data traffic during the circuit-switched busy hour. During the non-busy hours, the switchable timeslots are considered as available for use by the packet data network. Therefore, in the circuit-switched off busy hours, potentially all switchable timeslots could be available for the packet data network traffic. The BSS call statistics should be inspected to determine the actual use of the switchable timeslots by the circuit-switched services. The circuit-switched busy hour and the packet data busy hour should be monitored to see if they overlap when switchable timeslots are in use. If the busy hours overlap, an adjustment is needed to the number of reserved timeslots allocated to the packet data portion of the network in order to guarantee a minimum packet data quality of service (QoS) as measured by packet data throughput and delay. Furthermore, one or more circuit-switched carriers requires to be added to the cell being planned or replanned so that the switchable timeslots are not required in order to offer the desired circuit-switched grade of service. Assume that switchable timeslots are occasionally unavailable for packet data traffic during the circuit-switched portion of the network busy hour. Provision enough reserved timeslots for packet data traffic during the circuit-switched busy hour to meet the desired minimum packet data QoS objectives, as measured by packet data throughput. When CS and PS busy hour coincide, it is recommended that RES TS are configured to be sufficient to service the mean PS load, particularly if QoS is enabled, since CS traffic automatically pre-empties any PS traffic on SW TS. In these networks, the difference between the mean and peak traffic (as evidenced by the mean_load_factor parameter), can then be serviced by SW TS. Any TS configured as RES TS reduces the CS call capacity. More flexibility is envisaged with QoS disabled and if the operator does not have a strong commitment (for example, due to pricing plans) to maintain a certain level of service for PS data. If the CS and PS busy hour do not coincide, then the number of RES TS configured depends on the degree of overlap of the CS and PS load. In general, the rule is where there is more overlap then more RES TS is required. If there is no overlap whatsoever, that is, most TSs are assumed to be available to PS users during the PS busy hour, then a majority SW TS configuration is acceptable. For example, if 8 PDCHs are needed for mean_load_traffic, and we can assume mean_load_factor is 200%, peak_load_traffic needs 16 PDCHs, if overlap is 100% (CS and PS busy hour coincide), then we need 8 RS and 8 SW PDCHs. If overlap = 100% (CS and PS busy hour coincide), then we need 8 RS and 8 SW PDCHs. If overlap = 0 (CS and PS busy hour totally do not coincide), then we need 4 RS (recommended minimum configuration for a larger GPRS cell) and 12 SW. If overlap = 50% (CS and PS busy hour partly coincide), then we need 4 - 8 RS and 12 - 8 SW, detailed value is decided according to statistics.

68P02900W21-S 01 Feb 2007 3-159

GPRS/EGPRS network traffic estimation and key concepts

Chapter 3: BSS cell planning

Timeslot allocation process on carriers with GPRS traffic

The following procedure helps in determining how to allocate GPRS/EGPRS timeslots.
Procedure 3-1 Determining the allocation of GPRS/EGPRS timeslots 1

Estimate reserved timeslot requirement: Determine the number of reserved GPRS/EGPRS timeslots are needed on a per cell basis in order to satisfy a packet data throughput QoS. The use of PBCCH in a cell needs at least one reserved GPRS/EGPRS timeslot in that cell. The GPRS/EGPRS reserved timeslots should equal the sum of the active and standby timeslots that are allocated to a carrier.

Allocate switchable timeslots: Determine the number of reserved GPRS/EGPRS timeslots are needed on a per cell basis. The use of switchable timeslots can potentially offer increased capacity to both the GPRS/EGPRS and circuitswitched traffic if the traffic is staggered in time.

Add an extra circuit-switched carrier: If there is a require to use some timeslots on the carrier with only GPRS/EGPRS timeslots to satisfy the circuit-switched GOS objectives and the timeslot requirement overlaps with the number of reserved GPRS/EGPRS timeslots, consider adding another circuit-switched carrier to the cell.

Monitor network statistics: After deploying the GPRS/EGPRS timeslots on the cell, review the collected network statistics on a continuous basis in order to determine whether the reserved GPRS/EGPRS timeslots, switchable GPRS/EGPRS timeslots, and circuit-switched timeslots are truly serving the GOS and QoS objectives. As previously discussed, the use of switchable timeslots can offer network capacity advantages to both circuit-switched traffic and packet data traffic as long as the demand for these timeslots is staggered in time.

68P02900W21-S 3-160 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

GPRS/EGPRS air interface planning process

Influential factors in GPRS/EGPRS cell planning and deployment
The planning and dimensioning of a system containing packet data users is not as straightforward as a system populated with only circuit-switched users. Sophisticated tools are required to properly model the behavior of packet data users and dimension the required bandwidth for a given service mix. In GSM, the issues are further complicated when EGPRS is introduced in an existing GSM network which also supports GPRS. A generic planning and dimensioning process is shown in Figure 3-85. The main objectives are to minimize the number of sites and timeslots (spectrum) to support a given packet data users load at an acceptable QoS without compromising the QoS of voice users. Acceptable QoS for the packet data users with best effort type service is qualified by the bitrate or delay experienced. This should be at least like those experienced while using the normal wired line analogue modems. The QoS feature allows the system to differentiate between subscribers on the basis of the QoS level subscribed to or negotiated by the system. QoS2 can support RT streaming. It occupies more PDCHs.
Figure 3-85 Generic planning and dimensioning process
Number of subscribers (GPRS/EGPRS split) Area to cover coverage requirements RF Information Traffic Profile and Service mix QoS requirements Bandwidth available Network configurations RLC/MAC overheads

Traffic characterisation RF cell planning BTS dimensioning TS dimensioning BSS dimensioning Interface dimensioning

Cell sizes Number of cells TS requirements BSS requirements Interface requirements

Input parameters

Planning tools

Output parameters

At a higher level, the cell planning and deployment can be broken down into two activities, which become inter-related depending on the traffic volumes supported and bandwidth available. These are cell coverage and cell dimensioning. In addition, there are some deployment rules that are applied if there is sufficient flexibility in the choice of carrier and segregation of timeslots; this depends on the network configuration. Issues and influential factors that should be consider in carrying out the process shown are qualified.

Network configuration
Network configurations in which packet data (GPRS or EGPRS) can be introduced include:

Existing GSM network with GPRS already deployed. Existing GSM network without GPRS.

68P02900W21-S 01 Feb 2007 3-161

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Rolling out a new GSM network with or without GPRS. A new GSM based packet data system only.

Of these, the first configuration is the most likely deployment and the most challenging one. The second one dictates mass GPRS and/or EGPRS handset deployment to justify its deployment. The last two configurations are less of concern as they can be fine tuned to provide adequate coverage and grade of service. So, only the first configuration is considered.

RF cell planning (cell coverage)

The degree of coverage per GPRS and EGPRS coding scheme varies depending on several factors including:

Spectrum availability. Re-use patterns: hopping or non-hopping. Environment: As the radio conditions change the subsequent C/I (C/N) requirements at a given BLER also change. BTS power amplifier capability and how it is set for GMSK and 8-PSK modes. Cell sizes and cell border design criteria. BSS algorithms (for example, LA).

EGPRS can be introduced in an existing GSM network with full EGPRS coverage. The following factors are to be considered:

When the QoS feature is not enabled, the system employs the best effort packet data services (no high QoS requirements are supported) with RLC acknowledge mode (ARQ). The choice of operating BLER point is flexible within a certain range. In Motorolas implementation, acceptable BLER operating point is embedded in the LA algorithms for GPRS and EGPRS. When the QoS feature is enabled, the BSS is able to assign a MTBR per PFC. This allows the system to reserve throughput at the Local Timeslot Zone (Cell Level) and PRP (board level). When QoS2 feature is enabled, the BSS is able to support real-time service and enforce MBR for a PFC. It introduces more optimistic coding scheme for admission. CS1 and MCS-1 have been designed such that they match the voice coverage footprint. In addition, due to IR in EGPRS, higher operating BLERs can be tolerated. The higher the operating BLER the higher the coverage per GPRS/EGPRS coding scheme. However, the operating BLER cannot be excessive since it has undesirable consequences on system capacity and as such impacts the number of users that can be supported. In Motorolas implementation, the LA algorithm attempts to maximize the throughput while keeping implicitly the BLER operating regions within an acceptable bound in order not to degrade the overall system performance. The PA output power capability does not impact the EGPRS availability at cell borders since power difference in HPM applies only to 8-PSK modulated coding schemes. This, however, leads to less coverage (lower C/I or C/N) for higher code rates and impacts the system capacity. Frequency re-planning is required not so much to guarantee GPRS/EGPRS coverage but more to eliminate possible coverage degradation for voice users. In a conventional GSM voice network, the frequency planning of the traffic carriers are based on assuming certain activity factors (DTX). When GPRS/EGPRS are introduced, the level of interference goes up because of the following factors:

68P02900W21-S 3-162 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Higher activity: This depends on how the timeslot dimensioning is carried out to account for packet data users. If timeslots are driven hard, then the level of activity can be higher than that assumed for the voice only system. Also due to behavior of packet data users being different, data flow control throughout the network, multiplexing of users on the same timeslot, the activity profile are different. Maintaining the same quality of service for the voice users means loading due to packet data users needs scaling. 8-PSK signal peak to average ratio (PAR): due to 8-PSK envelop variation, the GMSK symbols are occasionally hit with higher interference than usual when average power of GMSK and 8-PSK signals are set to be the same. However, the level of degradation should be considered within the context of the likely degradation that may encounter otherwise as a result of having a lower average power in the 8-PSK mode (thus reducing the impact of PAR). It is envisaged that the impact of lower average power prevails the impact of PAR, and the average powers in GMSK and 8-PSK modes should be set equal.

Cell/timeslot dimensioning
The following factors influence cell/TS dimensioning since they impact throughput per TS as well as the apparent throughput seen by a user, that is, pipe size:

Types of services, applications, and volume of data that are to be supported. QoS required (user experience). Number of users multiplexed on the same timeslot. Multiplexing of GPRS and EGPRS users on the same timeslot. Signaling overhead (control channels). RLC/MAC protocol parameters setting. Multi-slot operation. QoS feature enable or disabled. QoS2 feature, Streaming service is enabled or disabled. Enforce MBR is enabled or disabled. Cell selection and re-selection. Hardware limitations, for example, number of timeslots supported per cell. Re-use pattern: BCCH carrier, FH carrier.

Of the influences listed, the last two can be easily dealt with while the remaining ones need detailed investigation, through simulation, to fully quantify their impacts. The following shed light on some of the issues that are encountered:

If QoS is enabled, the number of PDTCHs required to support the MTBR specified is different than when QoS is disabled. The BSS treats all mobiles equally when scheduling the air interface in a QoS disabled environment. If QoS2 feature is enabled, PDCHs required to support real-time service are more than QoS2 disabled. BSS provide more bandwidth and higher priority for real-time service to ensure transfer delay is met. Volume of data has varying impacts on system capacity. Short messages do not benefit from higher code rates for those users in good radio conditions since LA process needs time to converge to higher code rates. Moreover, RLC protocols, such as TBF holding time, degrade the capacity for short messages. As a general rule, the throughput seen in practice is lower than the ideal throughput for short messages and is closer to the ideal throughput for long messages.

68P02900W21-S 01 Feb 2007 3-163

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Up to four users can be multiplexed on a timeslot. Depending on system loading the apparent bit pipe seen by a user is subsequently reduced as in Figure 3-86. In addition, this could impact the throughput per timeslot since the LA process suffers due to variation of radio channel conditions between scheduling opportunities. Thus, even for long messages the ideal throughput is hardly achieved. In Motorolas implementation, there is an intelligent load management algorithm in the PCU that attempts to balance the load across resources allocated to the packet data users. This improves the overall system and operators QoS performance depending on the bandwidth provisioned for the packet data users. The QoS feature extends this general concept to provide per traffic class MTBR. Multiplexing of GPRS and EGPRS users on the same timeslot is possible. The only impact is a slight degradation in maximum achievable throughput for EGPRS users in the DL. This is because the GMSK has to be used in the DL when the GPRS is to be scheduled in the UL. This allows GPRS users to decode their block allocations sent on the DL (decoding the USF). RLC protocols such as TBF holding time, poll period (to receive measurement reports and Ack/Nack status of the transmitted blocks), RLC Ack/Nack window size, impacts the throughput per timeslot and as such number of users that can be supported. If Extended Uplink TBF feature is enabled, the TBF holding time is longer than that when the feature is disabled. If the PFC is in Ack mode, it is possible that the transfer delay for the LLC frame exceeds the TD guarantee, but given that the TD guarantee is performed over a set of packets, the impact is minimal. Alternately, if the PFC is in UnAck mode, there is no impact for TD guarantee. The operating BLER is an important parameter in optimizing the end-to-end throughput. The higher the operating BLER the higher the coverage per GPRS/EGPRS coding scheme. However, the operating BLER cannot be excessive since it has undesirable consequences on system capacity and as such impacts the number of users that can be supported. For example, although IR enables MCS-9 throughput to be like other coding schemes at low C/I values, but the corresponding BLER is quite high. This from system viewpoint could have detrimental effects due to the RLC protocol operation such as those in the last bullet points. In Motorolas implementation, the LA algorithm attempts to maximize the throughput while keeping implicitly the BLER operating regions within an acceptable bound in order not to degrade the system performance. If PCCCH is enabled, timeslot dimensioning for packet data traffic should consider the blocks used for control signaling.

68P02900W21-S 3-164 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Figure 3-86 Multiplexing 4 TBFs on an air timeslot

4 TBFs/TS

User 1 User 2 80ms 20ms block User 3 User 4

Time

QoS dimensioning and QoS2 dimensioning

The two most significant factors that influence quality of a service are:

Delay Throughput

In R99 and beyond, four traffic classes are defined to accommodate the need for different levels of these factors for different applications. These are:

Conversational Streaming Interactive Background

The BSS has internally defined additional traffic classes created by grouping similar PFC characteristics. The internally defined traffic classes are:

Short-Term Non-Negotiated Traffic (STNNT) Pre-admission PFC (PAP) QoS Disabled

Current GSR9 BSS does not support conversational service, it is downgraded to streaming service when QoS2 is unrestricted and streaming_enabled is enabled, Requests to create packet flows for conversational mode are treated as streaming. the BSS does not make any guarantee regarding strict parameter for conversational traffic.

68P02900W21-S 01 Feb 2007 3-165

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Traffic handling priority (THP)

Three priorities are defined in the standards for handling the traffic pertaining to the interactive traffic class only. For the BSS, these priorities determine relative throughput assigned to a particular Packet Flow Context (PFC). This is achieved by applying relative weights for each priority, defined at a BSS level. These weights are user configurable. In addition to the three standardized priorities, a fourth and a fifth THP are defined internally by the BSS for the background and best effort traffic classes respectively. The assigned weights for these internally defined THPs act relative to the three THPs that are defined for the interactive traffic class by the standards. THP provides a mechanism to differentiate services among different PFCs that may or may not belong to the same user.

Minimum Throughput Budget Requirement (MTBR)

A Minimum Throughput Budget Requirement (MTBR) is non-standards based BSS parameter associated with each PFC. The MTBR of a given TBF is the sum of MTBRs of all the PFCs that are multiplexed on that TBF. MTBR allows the BSS to admit each PFC if a minimum budget for resources can be met. The MTBR is subjected to a minimum of 2 kbit/s for each admitted PFC. The operator is allowed to configure the minimum throughput budget requirement in both the uplink and downlink directions separately. MTBR is measured as raw air throughput at the RLC/MAC layer without factoring in the Block Error Rate (BLER) and unsolicited retransmissions. It is not a guaranteed bitrate. MTBR is merely a budgeting guideline for the admission control mechanism. This helps to ensure that no more users are admitted than the system can handle without compromising service. MTBR is not achieved by a TBF with insufficient data to transmit. MTBR is set and regulated in terms of throughput at the RLC/MAC layer. Throughputs at the application layer are lower than the RLC/MAC throughput due to overhead consumed by the headers and retransmissions at the intermediate layers and the application layer. Table 3-32 shows typical TCP throughput for each 10 kbit/s of RLC/MAC throughput at zero block error rate. The TCP throughput depends upon the IP packet size and the LLC PDU size. Several typical values are shown in the following table.
Table 3-32 Typical TCP throughput against RLC/MAC throughput at zero block error rate RLC/MAC throughput (kbit/s) IP packet size (octets) LLC PDU size (octets) Typical TCP throughput (kbit/s)

10.0 10.0 10.0

1500 1500 576

1508 600 604

8.73 8.33 8.28

Guaranteed Bit Rate (GBR)

The Guaranteed Bit Rate is defined in specification 3GPP TS 23.107 Quality of Service (QoS) concept and architecture, Release 6 as a QoS attribute, maintained per streaming and conversational PFC. The GBR is a negotiable parameter. The EGBR is the additional throughput that is allocated to a user that is sufficient to service the GBR and the transfer delay requirements of the streaming service. The TABR of a given TBF is the sum of MTBRs and EGBRs of all the PFCs that are multiplexed on that TBF. The GBR in the uplink and downlink directions have different values. EGBR is defined as GBR/, where is a value between 0 and 1. In order to find the average downlink EGBR the minimum value for must first be found. Average downlink Streaming EGBR is calculated as follows: STR_EGBR = Average_GBR / * (1+BLER)

68P02900W21-S 3-166 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

BLER is typically 10%-15%. The value of is dependent on the transfer delay parameter for the streaming service. The minimum transfer delay that the PCU supports is user configurable. For planning purposes this value of minimum transfer delay is used to determine the value of . For a given GBR, the value of is dependent on the transfer delay parameter for the streaming service. In order to determine the value of to use, first obtain the weighted average GBR per service in the network. This is obtained by multiplying the frequency of the service in the network by the GBR of the service.

N AverageGBR = GBRi * FSi / STRi i =1

Where Is

N GBRi FSi

the number of streaming service types in the network the GBR of streaming service i the percentage of streaming service i in service mix of subscribers in a given PCU the percentage of total streaming service in service mix of subscribers in a given PCU

STRi

Looking up that Average GBR value in the tables , we obtain the value to use. The following table provides the minimum value of given the minimum transfer delay supported in the PCU, in networks where the majority of streaming services have GBR of 15 kbit/s or lower, for example, PoC. If an application does not need so stringent a transfer delay then the will be larger for that application, resulting in less EGBR required for a particular GBR. The default minimum transfer delay value is set to 500ms resulting in = 0.62.
Table 3-33 for various transfer delays at GBR 15 kbit/s or less Minimum Transfer delay (ms) Minimum Transfer delay (ms) Minimum Transfer delay (ms)

250 300 350 400 450 500 550 600

0.42 0.48 0.52 0.56 0.59 0.62 0.64 0.66

1550 1600 1650 1700 1750 1800 1850 1900

0.84 0.84 0.84 0.85 0.85 0.85 0.86 0.86

2850 2900 2950 3000 3050 3100 3150 3200

0.9 0.9 0.9 0.91 0.91 0.91 0.91 0.91

Continued

68P02900W21-S 01 Feb 2007 3-167

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Table 3-33 for various transfer delays at GBR 15 kbit/s or less (Continued) Minimum Transfer delay (ms) Minimum Transfer delay (ms) Minimum Transfer delay (ms)

650 700 750 800 850 900 950 1000 1050 1100 1150 1200 1250 1300 1350 1400 1450 1500

0.68 0.7 0.71 0.73 0.74 0.75 0.76 0.77 0.78 0.78 0.79 0.8 0.8 0.81 0.82 0.82 0.83 0.83

1950 2000 2050 2100 2150 2200 2250 2300 2350 2400 2450 2500 2550 2600 2650 2700 2750 2800

0.86 0.87 0.87 0.87 0.87 0.88 0.88 0.88 0.88 0.89 0.89 0.89 0.89 0.89 0.89 0.9 0.9 0.9

3250 3300 3350 3400 3450 3500 3550 3600 3650 3700 3750 3800 3850 3900 3950 4000

0.91 0.91 0.91 0.91 0.92 0.92 0.92 0.92 0.92 0.92 0.92 0.92 0.92 0.92 0.93 0.93

For networks where the majority of streaming services have GBR greater than 15 kbit/s, the following two tables provide the minimum values of for transfer delays of 500ms and 250ms. In networks where the configured minimum transfer delay parameter is set to be greater than 500ms then the table for the transfer delay of 500 ms should be used. Here, the procedure is to first determine the GBR for which the majority of service in the network operate, for example, video streaming 40 kbit/s, then looking up the GBR at the table , obtain . If the GBR value is not in the table, then the two closest GBR values should be evaluated and the value resulting in the lower value should be selected.
Table 3-34 for transfer delay = 500 ms at GBR greater than 15 kbit/s GBR (bits/s) GBR (bits/s) GBR (bits/s)

15000 16000 17000 18000

0.62 0.63 0.65 0.66

41000 42000 43000 44000

0.8 0.8 0.8 0.81

67000 68000 69000 70000

0.86 0.86 0.86 0.86

Continued

68P02900W21-S 3-168 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Table 3-34 for transfer delay = 500 ms at GBR greater than 15 kbit/s (Continued) GBR (bits/s) GBR (bits/s) GBR (bits/s)

19000 20000 21000 22000 23000 24000 25000 26000 27000 28000 29000 30000 31000 32000 33000 34000 35000 36000 37000 38000 39000 40000

0.67 0.68 0.69 0.69 0.7 0.71 0.72 0.72 0.73 0.74 0.74 0.75 0.75 0.76 0.76 0.77 0.77 0.78 0.78 0.79 0.79 0.79

45000 46000 47000 48000 49000 50000 51000 52000 53000 54000 55000 56000 57000 58000 59000 60000 61000 62000 63000 64000 65000 66000

0.81 0.81 0.82 0.82 0.82 0.82 0.83 0.83 0.83 0.83 0.84 0.84 0.84 0.84 0.85 0.85 0.85 0.85 0.85 0.85 0.86 0.86

71000 72000 73000 74000 75000 76000 77000 78000 79000 80000 81000 82000 83000 84000 85000 86000 87000 88000 89000 90000

0.87 0.87 0.87 0.87 0.87 0.87 0.87 0.88 0.88 0.88 0.88 0.88 0.88 0.88 0.88 0.89 0.89 0.89 0.89 0.89

Table 3-35 for transfer delay = 250 ms at GBR greater than 15 kbit/s GBR (bits/s) GBR (bits/s) GBR (bits/s)

15000 16000 17000 18000 19000 20000 21000

0.42 0.43 0.45 0.46 0.47 0.48 0.49

41000 42000 43000 44000 45000 46000 47000

0.63 0.63 0.64 0.64 0.64 0.65 0.65

67000 68000 69000 70000 71000 72000 73000

0.72 0.72 0.72 0.73 0.73 0.73 0.73

Continued

68P02900W21-S 01 Feb 2007 3-169

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Table 3-35 for transfer delay = 250 ms at GBR greater than 15 kbit/s (Continued) GBR (bits/s) GBR (bits/s) GBR (bits/s)

22000 23000 24000 25000 26000 27000 28000 29000 30000 31000 32000 33000 34000 35000 36000 37000 38000 39000 40000

0.5 0.51 0.52 0.52 0.53 0.54 0.55 0.56 0.56 0.57 0.58 0.58 0.59 0.59 0.6 0.61 0.61 0.62 0.62

48000 49000 50000 51000 52000 53000 54000 55000 56000 57000 58000 59000 60000 61000 62000 63000 64000 65000 66000

0.66 0.66 0.66 0.67 0.67 0.68 0.68 0.68 0.69 0.69 0.69 0.7 0.7 0.7 0.7 0.71 0.71 0.71 0.72

74000 75000 76000 77000 78000 79000 80000 81000 82000 83000 84000 85000 86000 87000 88000 89000 90000

0.74 0.74 0.74 0.74 0.74 0.75 0.75 0.75 0.75 0.76 0.76 0.76 0.76 0.76 0.76 0.77 0.77

Admission control and retention (GSR8 QoS)

Allocation/Retention Priority (ARP) is defined in specification 3GPP TS 23.107 Quality of Service (QoS) concept and architecture, version 4.6.0 Release 4 as a QoS attribute, maintained per PFC, that provides prioritized allocation and retention. It is a subscription parameter, meaning non-negotiable by the network entities. ARP ranges from 1 to 3 with 1 being the highest priority. The BSS maps the ARP parameter and the traffic class into ARP Rank, as shown in Table 3-36. The BSS uses ARP Rank to determine which PFCs have priority access to the system. ARP Rank 6 is higher priority than ARP Rank 1.
Table 3-36 ARP mobile selection (ARP Rank) order ARP value THP 1 THP 2 THP 3 Effort Background

1 2 3

6 5 4

6 5 4

6 5 4

6 5 4

3 2 1

Admission Control determines which PFCs get access to the system and which PFCs get pre-empted from the system to make room for higher ARP Rank PFCs. For a complete description of allocating resources at the cell and PRP level, refer to Chapter 8, PCU upgrade for BSS and QoS capacity and QoS2 impact.

68P02900W21-S 3-170 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

ARP (QoS2)
The priority, pci and pvi attributes of the ARP IE are supported as part of the QoS Phase II Feature. The BSS uses ARP to determine which PFCs have priority access to the system. The BSS provides the user the same level of configurability using the attributes shown in the table for the cases where the BSS does not receive the ARP IE attribute from the SGSN (SGSN may not be R6 compatible or may not include the optional ARP IE in the CREATE-BSS-PFC message).
Table 3-37 BSS ARP configuration Parameters Traffic Class Precedence Class Streaming or Conversational Interactive or Best Effort Background

0 1 2

arp_streaming_1 arp_streaming_2 arp_streaming_3

arp_i_be_1 arp_i_be_2 arp_i_be_3

arp_bg_1 arp_bg_2 arp_bg_3

Admission Control determines which PFCs get access to the system and which PFCs get pre-empted from the system to make room for higher ARP PFCs. For a complete description of allocating resources at the cell and PRP level, refer to Chapter 8, PCU upgrade for BSS and QoS capacity and QoS2 impact.

Estimating the air interface traffic throughput

The GPRS/EGPRS data throughput estimation process given in this chapter is based upon the Poisson process for determining the GPRS/EGPRS mobile packet transfer arrivals to the network and for determining the size of GPRS/EGPRS data packets generated or received by the GPRS/EGPRS mobiles. Some wired LAN/WAN traffic studies have shown that packet interarrival rates are not exponentially distributed. Recent work argues that LAN traffic is much better modeled using statistically self-similar processes instead of Poisson or Markovian processes. Self-similar traffic pattern means the interarrival rates appear the same, regardless of the timescale at which it is viewed (in contrast to Poisson process, which tends to be smoothed around the mean in a larger timescale). The exact nature of wireless GPRS traffic pattern is not known due to lack of field data. In order to minimize the negative impact of under-estimating the nature of the GPRS/EGPRS traffic, it is proposed in this planning guide to adjust the mean GPRS/EGPRS cell loading value, by a factor of 200% to account for the burstiness of GPRS/EGPRS traffic. When mean_load_factor parameter is assumed 200%, it means peak traffic is twice of mean traffic. This parameter impacts the connection between RS PDCH and SW PDCH with different overlap scenarios. Using this cell loading factor has the following advantages:

Cell overloading due to the bursty nature of GPRS/EGPRS traffic is minimized. The variance in file transit delay over the Um to Gi interface is minimized such that the delay can be considered a constant value for the purposes of calculating the time to transfer a file of arbitrary size.

LAN/WAN wireline studies have also shown that even when statistically valid studies are performed, the results come out different in follow-up studies. It turns out that web traffic patterns are difficult to predict accurately and, therefore, it is highly recommended that the network planner makes routine use of the GPRS/EGPRS network statistics.

68P02900W21-S 01 Feb 2007 3-171

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

The following sections describe dimensioning the system:

Select a cell plan Estimating timeslot provisioning requirements Optimum file size calculation File transit times calculations

Sections Optimum file size calculation and File transit times calculations are optional. These should be followed if an over the air file transfer time can be calculated for any size file. The results depend on the choices made in sections Select a cell plan and Estimating timeslot provisioning requirements.

Select a cell plan

Select a cell plan to determine the expected BLER and percentage of time data is transferred at the GPRS/EGPRS data rates. The cell plan that is selected for GPRS/EGPRS can be determined by the plan currently in use for the GSM circuit-switched part of the network. However, it is necessary to change an existing cell plan used for GSM circuit-switched to get better BLER performance for the GPRS/EGPRS part of the network. The PCU dynamically selects the best coding scheme in order to maximize the data throughput on a per mobile basis. The coding scheme rate selection is performed periodically during the temporary block flow (TBF). When planning frequency, it is required that there are no more than 48 frequencies in a cell with multiple carriers supporting GPRS/EGPRS timeslots. To demonstrate the performance of various GPRS and EGPRS coding schemes, Table 3-38 shows the percentage utilization of GPRS and EGPRS coding schemes at a fixed operating BLER of 20% in a 4x3 BCCH (non-hopping) re-use pattern, and under a TU channel condition. If non-regular patterns are used, a specific simulation study is required to match the particular cell characteristics. The simulation process is outside the scope of this planning guide.

When the QoS feature is enabled, the timeslot zone and PRP board level headroom compensate for BLER.
Table 3-38 Percentage of code utilization in a 4x3 non-hopping re-use pattern at 20% BLER Coding scheme % of code utilization

CS1
CS2 CS3 CS4

10.0 22.5 12.5 5.0 5.0 4.0 16.5

Continued

MCS-1
MCS-2 MCS-3

68P02900W21-S 3-172 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Table 3-38 Percentage of code utilization in a 4x3 non-hopping re-use pattern at 20% BLER (Continued) Coding scheme
MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9

% of code utilization

0.5 10.5 7.5 2.5 1.5 2.0

Estimating timeslot provisioning requirements

Here, we determine the number of GPRS/EGPRS timeslots that require to be provisioned on a per cell basis. Timeslot provisioning is based on the expected per cell mean GPRS/EGPRS traffic load, as measured in kbit/s. The packet data traffic load includes all SMS traffic routed through the GSN. The SMS traffic is handled by the GPRS/EGPRS infrastructure in the same manner as all other GPRS traffic originating from the PDN. The cell BLER and CS rate characteristics selected, provide the needed information for evaluating the following equation (totally segregated EGPRS and GPRS timeslots):

No _ PDTCH _ TS = Roundup[(

Mean _ traffic _ load _ GPRS * Mean _ load _ factor + TS _ Data _ Rate _ GPRS Mean _ traffic _ load _ EGPRS * Mean _ load _ factor )] TS _ Data _ Rate _ EGPRS

When DTM is enabled, pure PS without DTM mode is considered. Therefore, DTM capable MS in CS dedicated mode should be excluded. The calculation should use the following equation:

No _ PDTCH _ TS = Roundup[(

Mean _ traffic _ load _ GPRS * Mean _ load _ factor + TS _ Data _ Rate _ GPRS Mean _ traffic _ load _ EGPRS * Mean _ load _ factor ) * (1 R CS * PDTM )] TS _ Data _ Rate _ EGPRS

Where, RCS is the probability of MS in CS mode and PDTM is the DTM penetration rate. No_PDTCH_TS includes the PCCCH timeslot when PCCCH is enabled in the cell.

The equation is based on the DL traffic load and it is assumed that the DL provisioning would be sufficient to handle UL traffic, without additional provisioning.

68P02900W21-S 01 Feb 2007 3-173

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

The Mean_load_factor of 200% has been applied to the traffic load for systems without the QoS feature enabled to account for any surges in the data traffic and to carry packet switched signaling traffic. For example, assuming a traffic load with normal distribution, given a mean traffic load of M, the 99th-percentile peak traffic load, P, could be calculated as P = M + 3*M. The Mean_load_factor for networks with that traffic distribution is then P/M*100%. For systems with the QoS feature enabled the Mean_load_factor can be used to take into account when multiple QoS enabled mobiles are in a cell at the same instance. Traffic class, GBR and MTBR mix, relative THP, mobiles multi-slot capability, local timeslot zone (cell level) and PRP board level headroom are considered in the Mean_load_factor. Higher the Traffic Class, the MTBR needed and the relative THP weight would be higher which has a direct effect on Mean_load_factor. If there are more numbers of higher multi-slot capable mobiles in the traffic the Mean_load_factor is further increased. If more headroom is reserved for local timeslot zone/PRP board level the number of PDCH provisioned should be more to meet the QoS requirements in the cell. With QoS enabled headroom of 16.7% is reserved for local timeslot zone/PRP board level. Allocating more PDTCHs has the effect that QoS mobiles are not downgraded during peak usage at a cell.

For systems without the QoS feature enabled, Mean_traffic_load for each cell can be calculated using the following formulae:

Mean trafficload GPRS =

Avg sessions per sub * Data per sub per session * GPRS sub per cell 3600
Avg sessions per sub * Data per sub per session * EGPRS sub per cell 3600

Mean traffic load E GPRS =

For systems with the QoS feature enabled, Mean_traffic_load for each cell can be calculated using the following formulae:

Mean_traff ic_load_GP RS = (STR_EGBR * %subs_STR + I1_MTBR * %subs_I1 + I2_MTBR * %subs_I2 + I3_MTBR * %subs_I3 + BG_MTBR * %subs_BG + BE_MTBR * %subs_BE) * GPRS_subs_ per_cell/3 600

Mean_traffic_load_EGPRS = (STR_EGBR * %subs_STR + I1_MTBR * %subs_I1 + I2_MTBR * %subs_I2 + I3_MTBR * %subs_I3 + BG_MTBR * %subs_BG + BE_MTBR * %subs_BE) * GPRS_subs_ per_cell/3600

The units for Data_per_sub_per_session is kbyte/hr

68P02900W21-S 3-174 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

For systems without the QoS feature enabled:

TS Data Rate GPRS =

1 4 CSi % Code utilization * CSi UserDatarate * (1 BLER) 100 i =1

1 4 TS Data Rate EGPRS = MCSi % Code utilization * MCSi UserDatarate * (1 BLER) 100 i =1
For systems with the QoS feature enabled:

TS Data Rate GPRS =

1 (SUM from CS1 to egprs_init _cs (CS Code utilizatio n * CS UserData rate ) 100 + SUM from egprs_init _cs to max_egprs_ cs (CS Code utilizatio n * CS UserData rate for gprs_init_ cs)

TS Data Rate EGPRS =

1 (SUM from MCS1 to egprs_init _cs (CS Code utilizatio n * CS UserData rate ) 100 + SUM from egprs_init _cs to max_egprs_ cs (CS Code utilizatio n * CS UserData rate for gprs_init_ cs)

For systems with the QoS2 feature enabled, default coding scheme is CS2 and MCS3 (refer to GPRS/EGPRS data rates).

(M)CS_USAGE is the percentage of usage of (E)GPRS coding schemes.

Number of timeslots
The number of PDTCH timeslots calculated in the section Estimating timeslot provisioning requirements on page 3-173, denotes the number of timeslots that need to be provisioned on the cell to carry the mean traffic load on the cell. It is important to differentiate between the required number of timeslots processed at any instance in time and the total provisioned timeslots because it directly affects the provisioning of the communication links and the PCU hardware. The active timeslots are timeslots that are simultaneously carrying data being processed by the PRP on the PCU at any instance in time. It is possible, however, to transfer packet switched data on each of the 1080 timeslots of a PCU simultaneously (assuming that all 9 PRPs are configured, legacy deployment mode), The PCU rapidly multiplex all the timeslots with a maximum of 270 timeslots at any instance in time. For example, if there are MSs on each of 1080 timeslots provisioned on the air interface, the PCU processes timeslots in 4 sets of 270 timeslots, with switching between sets occurring every block period. The use of timeslots processed at any instance and total provisioned timeslots enables several cells to share the PCU resource. While one cell is experiencing a high load condition, using all eight packet data timeslots for instance, another cell operating its mean load averages out the packet data traffic load at the PCU. The E1s between the BTS and BSC must be provisioned to handle the number of timeslots calculated because all of the timeslots can become active under high load conditions.

Timeslot refinement with QoS enabled

The number of PDTCHs determined for support of QoS should be compared to the examples given. Refer to the examples to determine a refined number of PDTCHs to support QoS with a given set of configuration parameters.

68P02900W21-S 01 Feb 2007 3-175

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Table 3-39 MTBR Mix MTBR Mix Percentage DL UL

I1 I2 I3 BG BE

14 10 4 2 2

2 2 2 2 2

Table 3-40 MTBR Constant MTBR Constant Percentage DL

2 2 2 2 2

UL

I1 I2 I3 BG BE

2 2 2 2 2

Table 3-41 THP Weight Mix THP Weight Mix

I1 I2 I3 BG BE

40 40 20 20 20

Table 3-42 THP Weight Constant THP Weight Constant

I1 I2 I3 BG BE

40 40 20 20 20

68P02900W21-S 3-176 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Table 3-43 shows the QoS Configuration Examples. Table 3-43 QoS Configuration Examples

Comparison: Number of Class 4 Mobiles in a Cell with 6 PDTCHs; TRAU = 16K, all THP weight = 40, MTBR = 2.
Table 3-44 and Table 3-45 show the impact of QoS on the number of PDTCHs required to support a given traffic mix. The colored cells highlight the additional mobile being added for the specified time period.

68P02900W21-S 01 Feb 2007 3-177

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Table 3-44 QoS Disabled; Capacity: 18 users, DL Throughput per MS: 0.33 (6/18) TS Mobiles 2 3 4 5 6 7 Link MS per TS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

0 0 33 0 33 0 33 0 133 100 133 100 133 100 133 100 133 100 133 100 233 200 233 200 233 200 233 200 233 200 233 200

0 0 33 100 33 100 33 100 33 100 133 200 133 200 133 200 133 200 133 200 133 200 233 300 233 300 233 300 233 300 233 300

0 0 33 0 33 0 83 0 83 0 83 0 183 100 183 100 183 100 183 100 183 100 183 100 283 200 283 200 283 200 283 200

33 0 33 0 333 0 83 100 83 100 83 100 83 100 83 100 183 200 183 200 183 200 183 200 183 200 183 200 283 300 283 300

33 100 33 100 83 100 83 100 83 100 83 100 83 100 183 200 183 200 183 200 183 200 183 200 183 200 283 300 283 300 283 300

33 0 33 0 83 100 84 100 83 100 83 100 83 200 83 200 83 200 183 300 183 300 183 300 183 300 183 300 183 300 283 400

DL UL DL UL DL UL DL UL DL UL DL UL Dl UL DL UL DL UL DL UL DL UL DL UL DL UL DL UL DL UL DL UL

0.50 1.00 1.33 1.67 1.83 2.00 2.17 2.33 2.50 2.67 2.83 3.00 3.17 3.33 3.50 3.67

Continued

68P02900W21-S 3-178 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Table 3-44 QoS Disabled; Capacity: 18 users, DL Throughput per MS: 0.33 (6/18) TS (Continued)

333 17 300 18 19 20 21 22 23 333 300 333 300 333 300 333 300 333 300 333 300

233 300 333 400 333 400 333 400 333 400 333 400 333 400

283 200 283 200 283 200 283 200 283 200 283 200 283 200

283 300 283 300 283 300 283 300 283 300 283 300 283 300

283 300 283 300 283 300 283 300 283 300 283 300 283 300

283 400 283 400 283 400 283 400 283 400 283 400 283 400

DL UL DL UL DL UL Dl UL DL UL DL UL DL UL

3.83

Table 3-45 QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11) TS Mobiles 2 3 4 5 6 7 Link MS per TS

1 2 3 4 5 6 7

0 0 33 0 33 0 83 100 83 100 83 100 83 100

0 0 33 100 33 100 83 100 83 100 117 100 117 100

0 0 33 0 67 0 67 0 67 0 100 100 150 100

33 0 33 0 67 100 67 100 67 100 100 100 150 200

33 100 33 100 67 100 67 100 117 100 117 100 117 100

33 0 33 0 33 0 333 0 83 100 83 100 83 200

DL UL DL UL DL UL DL UL DL UL DL UL Dl UL

0.50 1.00 1.50 1.83 2.17 2.67 3.00

Continued

68P02900W21-S 01 Feb 2007 3-179

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Table 3-45 QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11) TS (Continued)

83 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 100 133 100 133 100 233 200 233 200 233 200 233 200 233 200 233 200 233 200 233 200 233 200 233 200 233 200 233 200 233 200

117 100 167 200 167 200 167 200 167 200 167 200 167 200 167 300 167 200 167 200 167 200 167 200 167 200 167 200 167 200 167 200

150 100 150 100 150 100 150 100 150 100 150 100 150 100 150 100 150 100 150 100 150 100 150 100 150 100 150 100 150 100 150 100

150 200 150 200 150 200 150 200 150 200 150 200 150 200 150 200 150 200 150 200 150 100 150 200 150 200 150 200 150 200 150 200

167 100 167 100 167 100 167 100 167 100 167 1200 167 100 167 100 167 100 167 100 167 100 167 100 167 100 167 100 167 100 167 100

133 200 133 200 233 300 233 300 233 300 233 300 233 300 233 300 233 300 233 300 233 300 233 300 233 300 233 300 233 300 233 300

DL UL DL UL DL UL DL UL DL UL DL UL DL UL DL UL DL UL DL UL DL UL DL UL Dl UL DL UL DL UL DL UL

3.33

3.67 3.83 4.00

68P02900W21-S 3-180 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Optimum file size calculation

This section is intended to be used as an aid in determining the size of a file that is to be transferred as an LLC PDU from the mobile to the SGSN. The file size consists of the application file to be transferred, which includes any application-related overhead. In addition to the application file, there is transport and network layer protocol overhead, TCP and IP. Finally, there is GPRS/EGPRS Link Layer Control (LLC) and sub network convergence (SNDCP) protocol overhead. The application file plus all of the protocol overhead summed together makes up the one or more LLC_PDU frames that constitute the file to be transferred. The percentage of protocol overhead depends on the transport layer used, such as TCP or UDP. For example, the TCP/IP protocol overhead is 40 bytes when TCP/IP header compression is not used. When TCP/IP header compression is used, the TCP/IP header can be reduced to 5 bytes from 40 bytes after the first LLC frame is transferred. The use of header compression continues for as long as the IP address remains the same.
Figure 3-87 illustrates a typical LLC_PDU frame with the user application payload and all of the protocol overhead combined for the case of no TCP/IP header compression. Figure 3-87 LLC_PDU frame layout
7 LLC 2 SNDCP 20 IP 20 TCP APPLICATION 4 CRC

64 BYTES < L < 1580 BYTES

If V.42bis application data compression is used, the effective file size for transmission is reduced by the data compression factor which can range from 1 to 4. Typically, V.42bis yields a 2.5 compression advantage on a text file, and close to no compression advantage (factor = 1) on image files and short files:

File size LLC =

App ln App ln + roundup * protocol overhead V.42bis factor V.42bis factor * LLC Payload
Is

Where

File_size_LLC Appln LLC_payload protocol_overhead

file size in bytes to be transferred, measured at the LLC layer. user application data file size, measured in bytes. maximum LLC PDU payload of 1527 bytes. protocol overhead for TCP/IP/SNDCP/LLC/CRC is 53 bytes without header compression and 18 bytes with header compression. application data compression is over the range of 1 to 4, a typical value is equal to 2.5.

V.42bis_factor

68P02900W21-S 01 Feb 2007 3-181

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Examples of calculation
Example 1:

A 3 kbyte/s application file transfer needs the following number of bytes to be transferred at the LLC_PDU layer: Application = 3 kbytes Assume that V.42bis_factor = 2, that is no application data compression. Without Header compression: File_size_LLC = 3000/2 + roundup (3000/2/1527) x 53 = 1553 bytes With header compression: The first LLC_PDU header is not compressed, and all subsequent LLC_PDUs are compressed. For this size file of 3000 bytes, only 2 LLC_PDU transmissions are required so the File_size_LLC is: File_size_LLC = 1500 + 53+18 = 1571 bytes
Example 2:

A PoC service has the following parameters: Application = 20 packets, every packet has a size range from 200 to 400 bytes, assuming total 6000 Bytes, and speak 10s then listen 10s. SIP signaling with RSVP, no SIGcomp, the size of total signaling size is 5249 Bytes (from INVITE to PRACK, 27 messages, whose size varies from 5 to 625 Bytes.). Assume V.42bis_factor = 1, that is no application data compression and No header compression: File size LLC = 6000+ (number of packet)* 53+ 5249+ (number of signaling)*53+18 = 6000+1060+ 5249 + 1431+ 18 = 13758 (bytes) SIP SIGcomp (RFC3322) has 2 regular compression algorithm and there are simulation results as follows:

LZ77 algorithm: compression ratio range is from 0.7 to 0.9(Typical SIP call setup), 0.8 can be used. RoHC algorithm: compression ratio range is from 0.2 to 0.8(Typical SIP call setup), 0.5 can be used.

For the PoC service of example2, if V.42bis_factor =2, using LZ77 algorithm, File size LLC = (6000)/2+ 20*53+ (5249*0.8)/2+ 27*53 + 18 = 7609 (bytes)

File transit times calculations

The network planner can follow this section to determine how long it takes to transfer a file of an arbitrary size over the Um to Gi interface. The application file is segmented into LLC PDU frames as illustrated previously. The File Transit Delay (FTD) is calculated using the following information: total number of RLC blocks of the file, BLER, number of timeslots used during the transfer, and mean RLC Transit Delay (RTD) value:

FTD = RTD +

RLC blocks * 0.02(1 + CS _ BLER ) mslot

68P02900W21-S 3-182 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Where

Is

FTD RTD

file transit delay measured in seconds. transit delay time from the Um interface to the Gi interface for a file size of only one RLC/MAC block of data. RTD is estimated to be 0.9 s when the system running at 50% capacity. This parameter is updated when field test data is available. total number of RLC blocks of the file. This can be calculated by dividing file_size_LLC by the corresponding RLC data size for various GPRS and EGPRS code rates. mobile multislot operating mode; the value can be from 1 to 4. the BLER for the specific coding rate. The value is specified in decimal form. Typical values range form 0.1 to 0.2

RLC_Blocks

mslot

CS_BLER

The equation does not include the effects of acknowledgement messages. The reason is that the largest effect is in the uplink direction, and it is expected that the downlink direction l dominates the cell traffic. The DL sends an acknowledgement message on an as-needed basis, whereas the uplink generates an acknowledgement message based on downlink commands transmitted at a frequency varying between 2 and 12 RLC blocks. It is expected that the downlink acknowledgement messages do not significantly effect the file transit delay in the downlink direction. The RTD parameter is directly correlated to the system utilization and the mean packet size. When the cell approaches its throughput capacity limit, the RTD value increases dramatically, and the infrastructure starts to drop packets. Simulation data indicates that when traffic load is minimal, the RTD value is at a minimum limit of 0.7 seconds. At a cell throughput capacity of 50%, the RTD increases to 0.9 seconds. It is recommended that cell throughput provisioning be performed at the mean cell capacity level of 50%. Provisioning for a mean cell throughput greater than 50% greatly increases the likelihood of dropped packets, and RTD values of over 2.6 seconds can occur. The assumptions used in the simulation to determine the RTD value at a mean cell throughput level of 50% are: 25% of the cell traffic at the CS1 rate and 75% of the cell traffic at the CS2 rate, BLER 10%, mobiles multislot distribution 1:2:3:4 = 20:50:20:10, 8 PDTCH, DL, mean LLC_PDU packet size of 435 bytes.

68P02900W21-S 01 Feb 2007 3-183

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Examples of calculations
Example 1:

A 3 kbyte/s application file transit time at the CS2 rate, using one timeslot, BLER = 10%, and no header or V.42bis compression is: 3 kbyte/s file transit time over Um to Gi interface =0.9 + Roundup (3106/30) * 0.02 * 1.1 / 1 = 3.2 seconds
Where Is equal to

File_size_LLC CS2 payload Air time for one RLC/MAC block (1 + CS_BLER) Multislot operation
Example 2:

3106 bytes (as calculated in the previous example) 30 bytes 0.02 seconds 1.1 1

An Audio Streaming service, has 290 packets, packet size is 400 bytes, BLER = 10%, and no header or V.42bis compression is: Transit time of a packet over Um to Gi interface = 0.9 + Roundup (471/56) * 0.02 * 1.1 / 1 = 1.098 seconds Total time = 1.098*290 = 318 s
Where Is equal to

File_size_LLC MCS5 payload Air time for one RLC/MAC block (1 + CS_BLER) Multislot operation
Example 2:

400+53+18 =471 bytes 56 bytes 0.02 seconds 1.1 1

A PoC service has the following parameters: Application = 20 packets, every packet has a size range from 200 to 400 bytes, assuming total 6000 Bytes, and speak 10s then listen 10s. SIP signaling with RSVP, no SIGcomp, the size of total signaling size is 5249 Bytes (from INVITE to PRACK, 27 messages, whose size varies from 5 to 625 Bytes.). Assume V.42bis_factor = 1, that is no application data compression. No header compression. Then every PoC voice data packet has different TD, for example, the first packet, size = 300 bytes, for other packets, the minimum size = 250 bytes, maximum size = 400 bytes, then

68P02900W21-S 3-184 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

TD1 = 0.9+ Roundup[(300+53+18)/56]*0.02*1.1/1 = 1.054 s TDMin = 0.9 + Roundup[(250+53)/56]*0.02*1.1/1 = 1.032 s TDMax = 0.9 + Roundup[(400+53)/56]*0.02*1.1/1 = 1.098 s Total transfer delay for PoC service is meaningless, since listen and talk has 10s interval. For signaling transfer: The first signaling is INVOKE, size is 625 Bytes, for other packets, minimum size = 5 bytes, maximum size = 625 Bytes, total signaling size is 5324. Assume using LZ77 algorithm (0.8), TD1 = 0.9+ Roundup[(625+53+18)*0.8 /56]*0.02*1.1/1 = 1.12 s TDMin = Roundup[(5+53)*0.8/56]*0.02*1.1/1 = 0.022 s TDMax= Roundup[(625+53)*0.8/56]*0.02*1.1/1 = 0.22 s. Total signaling time is 1.12+ Roundup[(5324-625)*0.8/56]*0.02*1.1/1 = 2.616 s, actual transfer delay for PoC call maybe 3- 5 s since MS Radio access cost some time.
Where Is equal to

MCS5 payload Air time for one RLC/MAC block (1 + CS_BLER) Multislot operation

56 bytes 0.02 seconds 1.1 1

Configurable initial coding scheme

Before GSR7, Coding Scheme 2 (CS2) was used to start for all downlink and uplink TBFs. Now, the operator is able to control the initial downlink coding scheme (using database parameters) to improve throughput of cells in which it is well known that all mobiles are capable of higher coding schemes, such as microcells. CS2 is still used to start when the carrier or PDTCHs assigned for the TBFs are not capable of the initial coding scheme CS3 or CS4 if they are set in the database. The feature also applies to EGPRS, for examples, MCS-2 can be selected as the initial coding scheme. QoS2 has default value of CS-2 and MCS3. If the coding scheme configured is lower, the budgeted throughput per TS is lower. {30828} In CTU2D ASYM mode, Carrier Bs UL TS is always restricted to GMSK (CS 1 to CS 4, or MCS 1 to MCS 4). Therefore when the egprs_init_ul_cs is configured higher than MCS4 it is restricted to MCS3 when admitting a new mobile on Carrier B.

68P02900W21-S 01 Feb 2007 3-185

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

GPRS/EGPRS data rates

The information provided is for reference only. It is also used to calculate timeslot data rates at each layer, if required. These are theoretical calculated values, based on the protocol overheads at each layer. They do not necessarily represent the data rates that the system can support. The final throughput at application layer is less than those quoted in the tables due to various protocol overheads and the behavior of various layers in response to packet data flow.

The following assumptions are made to arrive at the numbers:

Mean IP packet size of approximately 500 bytes. LLC in unacknowledged mode. This implies that it is assumed there is no signaling overhead to acknowledge LLC frames. In practice, the LLC acknowledged mode imposes relatively significant overhead at RLC/MAC level due to additional signaling required over the user data channel. V42.bis data compression is disabled (if V42.bis is enabled, the data rate is highly variable depending on data contents. This parameter is also configured in SGSN). The behavior of TCP, for example, slow start, is not taken into consideration, that is, perfect TCP response is assumed. In practice, this imposes additional overhead since the channel is not fully utilized for certain portion of time. Increased efficiencies gained from lowered overhead, as a result of using higher numbers of timeslots, is not calculated for this analysis. C/I for each coding scheme is sufficient to support error free transport, that is, BLER = 0.
o o

H/C = Header compression. TS = Timeslot.

The rates are calculated bottom to top as follows (refer to Figure 3-87 and Figure 3-88):

Physical layer: GSM data rates. RLC/MAC: Error free data rate including RLC/MAC headers (see earlier description of various coding schemes, user and header encoding procedures. LLC: Error free user data rate excluding RLC/MAC header, that is, LLC broken into RLC blocks (Figure 3-88). SNDCP: Includes header associated with LLC (7 bytes + 4bytes CRC, Figure 3-85). IP user rate: Includes header associated with SNDCP (2 bytes, Figure 3-85). TCP: includes header associated with IP (20 bytes, Figure 3-85). The header compression is not applied to the first LLC IP frame. App. user rate: Includes header associated with TCP (20 bytes, Figure 3-85). For more than 1 timeslot, the overheads are applied only to one of the timeslots.

68P02900W21-S 3-186 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Figure 3-88 LLC PDU to TDMA bursts

LLC frame

LLC layer

RLC block Segment Segment Segment

RLC/MAC layer

Header

RLC data

Tail

Radio link layer Convolutional encoding (dictates code rate), Puncturing and Interleaving

Burst 1

Burst 2

Burst 3

Burst 4

Transmission across the radio link

Table 3-46 through Table 3-71 provide illustrations of the data rates by application at each layer in the GPRS stack. Table 3-46 GPRS downlink data rates (kbit/s) with TCP (CS1) Protocol Stack CS1 and TS = 1 CS1 and TS = 2 CS1 and TS = 3 CS1 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 7.73 7.83 7.93 7.94 8.00 9.20 33.86

H/C 7.91 7.92

No H/C 15.73 15.83 15.93 15.94 16 18.4 67.72

H/C 15.93 15.93

No H/C 23.73 23.83 23.93 23.94 24 27.6 101.58

H/C 23.93 23.93

No H/C 31.73 31.83 31.93 31.94 32 36.8 135.44

H/C 31.93 31.93

68P02900W21-S 01 Feb 2007 3-187

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Table 3-47 GPRS downlink data rates (kbit/s) with TCP (CS2) Protocol Stack CS2 and TS = 1 CS2 and TS = 2 CS2 and TS = 3 CS2 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 11.60 11.75 11.90 11.92 12 13.6 33.86

H/C 11.86 11.89

No H/C 23.60 23.75 23.90 23.92 24 27.1 67.72

H/C 23.89 23.90

No H/C 35.60 35.75 35.90 35.92 36 40.65 101.58

H/C 35.89 35.90

No H/C 47.60 47.75 47.90 47.92 48 54.2 135.44

H/C 47.89 47.90

Table 3-48 GPRS downlink data rates (kbit/s) with TCP (CS3) Protocol Stack CS3 and TS = 1 CS3 and TS = 2 CS3 and TS = 3 CS3 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 13.92 14.10 14.28 14.30 14.4 15.8 33.86

H/C 14.24 14.26

No H/C 28.32 28.50 28.68 28.70 28.8 31.5 67.72

H/C 28.67 28.68

No H/C 42.72 42.90 43.08 43.10 43.2 47.3 101.58

H/C 43.07 43.08

No H/C 57.12 57.30 57.48 57.50 57.6 63.0 135.44

H/C 57.47 57.48

Table 3-49 GPRS downlink data rates (kbit/s) with TCP (CS4) Protocol Stack CS4 and TS = 1 CS4 and TS = 2 CS4 and TS = 3 CS4 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 7.73 7.83 7.93 7.94 8.00 9.20 33.86

H/C 7.91 7.92

No H/C 15.73 15.83 15.93 15.94 16 18.4 67.72

H/C 15.93 15.93

No H/C 23.73 23.83 23.93 23.94 24 27.6 101.58

H/C 23.93 23.93

No H/C 31.73 31.83 31.93 31.94 32 36.8 135.44

H/C 31.93 31.93

68P02900W21-S 3-188 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Table 3-50 GPRS downlink data rates (kbit/s) with UDP (CS1) Protocol Stack CS1 and TS = 1 CS1 and TS = 2 CS1 and TS = 3 CS1 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 7.79 7.83 7.93 7.94 8.00 9.20 33.86

H/C 7.92 7.92

No H/C 15.79 15.83 15.93 15.94 16 18.4 67.72

H/C 15.93 15.93

No H/C 23.79 23.83 23.93 23.94 24 27.6 101.58

H/C 23.93 23.93

No H/C 31.79 31.83 31.93 31.94 32 36.8 135.44

H/C 31.93 31.93

Table 3-51 GPRS downlink data rates (kbit/s) with UDP (CS2) Protocol Stack CS2 and TS = 1 CS2 and TS = 2 CS2 and TS = 3 CS2 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 11.69 11.75 11.90 11.92 12 13.6 33.86

H/C 11.88 11.89

No H/C 23.69 23.75 23.90 23.92 24 27.1 67.72

H/C 23.89 23.90

No H/C 35.69 35.75 35.90 35.92 36 40.65 101.58

H/C 35.89 35.90

No H/C 47.69 47.75 47.90 47.92 48 54.2 135.44

H/C 47.89 47.90

Table 3-52 GPRS downlink data rates (kbit/s) with UDP (CS3) Protocol Stack CS3 and TS = 1 CS3 and TS = 2 CS3 and TS = 3 CS3 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 14.03 14.10 14.28 14.30 14.4 15.8 33.86

H/C 14.25 14.26

No H/C 28.43 28.50 28.68 28.70 28.8 31.5 67.72

H/C 28.67 28.68

No H/C 42.83 42.90 43.08 43.10 43.2 47.3 101.58

H/C 43.07 43.08

No H/C 57.23 57.30 57.48 57.50 57.6 63.0 135.44

H/C 57.47 57.48

68P02900W21-S 01 Feb 2007 3-189

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Table 3-53 GPRS downlink data rates (kbit/s) with UDP (CS4) Protocol Stack CS4 and TS = 1 CS4 and TS = 2 CS4 and TS = 3 CS4 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 19.49 19.58 19.84 19.86 20 21.6 33.86

H/C 19.80 19.81

No H/C 39.48 39.58 39.84 39.86 40 43.1 67.72

H/C 39.82 39.83

No H/C 59.48 59.58 59.84 59.86 60 64.7 101.58

H/C 59.82 59.83

No H/C 79.48 79.58 79.84 79.86 80 86.2 135.44

H/C 79.82 79.83

Table 3-54 EGPRS downlink data rates (kbit/s) with TCP (MCS1) Protocol Stack MCS1 and TS =1 MCS1 and TS = 2 MCS1 and TS = 3 MCS1 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 8.51 8.62 8.73 8.74 8.80 10.55 33.86

H/C 8.70 8.72

No H/C 17.31 17.42 17.53 17.54 17.60 21.10 67.72

H/C 17.52 17.52

No H/C 26.11 26.22 26.33 26.34 26.40 31.65 101.58

H/C 26.32 26.32

No H/C 34.91 35.02 35.13 35.14 35.20 42.20 135.44

H/C 35.12 35.12

Table 3-55 EGPRS downlink data rates (kbit/s) with TCP (MCS2) Protocol Stack MCS2 and TS = 1 MCS2 and TS = 2 MCS2 and TS = 3 MCS2 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 10.83 10.97 11.11 11.12 11.20 12.95 33.86

H/C 11.07 11.09

No H/C 22.03 22.17 22.31 22.32 22.40 25.90 67.72

H/C 22.30 22.30

No H/C 33.23 33.37 33.51 33.52 33.60 38.85 101.58

H/C 33.50 33.50

No H/C 44.43 44.57 44.71 44.72 44.80 51.80 135.44

H/C 44.70 44.70

68P02900W21-S 3-190 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Table 3-56 EGPRS downlink data rates (kbit/s) with TCP (MCS3) Protocol Stack MCS3 and TS = 1 MCS3 and TS = 2 MCS3 and TS = 3 MCS3 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 14.31 14.49 14.68 14.70 14.80 16.55 33.86

H/C 14.63 14.66

No H/C 29.11 29.29 29.48 29.50 29.60 33.10 67.72

H/C 29.46 29.47

No H/C 43.91 44.09 44.28 44.30 44.40 49.65 101.58

H/C 44.26 44.27

No H/C 58.70 58.89 59.08 59.10 59.20 66.20 135.44

H/C 59.06 59.07

Table 3-57 EGPRS downlink data rates (kbit/s) with TCP (MCS4) Protocol Stack MCS4 and TS = 1 MCS4 and TS = 2 MCS4 and TS = 3 MCS4 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 17.02 17.23 17.46 17.48 17.60 19.35 33.86

H/C 17.40 17.43

No H/C 34.61 34.83 35.06 35.08 35.20 38.70 67.72

H/C 35.04 35.05

No H/C 52.21 52.43 52.66 52.68 52.80 58.05 101.58

H/C 52.64 52.65

No H/C 69.81 70.03 70.26 70.28 70.40 77.40 135.44

H/C 70.24 70.25

Table 3-58 EGPRS downlink data rates (kbit/s) with TCP (MCS5) Protocol Stack MCS5 and TS = 1 MCS5 and TS = 2 MCS5 and TS = 3 MCS5 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 21.66 21.93 22.22 22.24 22.40 23.90 101.58

H/C 22.15 22.19

No H/C 44.05 44.33 44.62 44.64 44.80 23.90 203.16

H/C 44.59 44.61

No H/C 66.45 66.73 67.02 67.04 67.20 23.90 304.74

H/C 66.99 67.01

No H/C 88.85 88.13 89.42 89.44 89.60 23.90 406.32

H/C 89.39 89.41

68P02900W21-S 01 Feb 2007 3-191

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Table 3-59 EGPRS downlink data rates (kbit/s) with TCP (MCS6) Protocol Stack MCS6 and TS = 1 MCS6 and TS = 2 MCS6 and TS =3 MCS6 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 28.62 28.99 29.36 29.39 29.60 31.10 101.58

H/C 29.26 29.32

No H/C 58.21 58.58 58.96 58.99 59.20 62.20 203.16

H/C 58.93 58.94

No H/C 87.81 88.18 88.56 88.59 88.80 93.30 304.74

H/C 88.53 88.54

No H/C 117.41 117.78

H/C 118.13 118.14

118.16 118.19 118.40 124.40 406.32

Table 3-60 EGPRS downlink data rates (kbit/s) with TCP (MCS7) Protocol Stack MCS7 and TS =1 MCS7 and TS = 2 MCS7 and TS = 3 MCS7 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 43.31 43.87 44.43 44.49 44.80 46.90 101.58

H/C 44.29 44.38

No H/C 88.11 88.67 89.23 89.29 89.60 93.80 203.16

H/C 89.19 89.21

No H/C 132.90 133.47

H/C 133.99 134.01

No H/C 177.70 178.27

H/C 178.79 178.81

134.03 134.09 134.40 140.70 304.74

178.83 178.89 179.20 187.60 406.32

Table 3-61 EGPRS downlink data rates (kbit/s) with TCP (MCS8) Protocol Stack MCS8 and TS =1 MCS8 and TS = 2 MCS8 and TS = 3 MCS8 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 52.60 53.27

H/C 53.78 53.88

No H/C 106.99 107.67

H/C 108.30 108.33

No H/C 161.38 162.07

H/C 162.70 162.73

No H/C 215.78 216.47

H/C 217.10 217.13

53.95 54.02 54.40 56.50 101.58

108.35 108.42 108.80 113.00 203.16

162.75 162.82 163.20 169.50 304.74

217.15 217.22 217.60 226.00 406.32

68P02900W21-S 3-192 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Table 3-62 EGPRS downlink data rates (kbit/s) with TCP (MCS9) Protocol Stack MCS9 and TS =1 MCS9 and TS = 2 MCS9 and TS = 3 MCS9 and TS = 4

No H/C App. user rate TCP IP user rate SNDCP LLC RLC/MAC Physical layer 57.24 57.97

H/C 58.53 58.64

No H/C 116.43 117.17

H/C 117.85 117.89

No H/C 175.62 176.37

H/C 177.05 177.09

No H/C 234.82 235.57

H/C 236.25 236.29

58.71 58.79 59.20 61.30 101.58

117.91 117.99 118.40 122.60 203.16

177.11 177.19 177.60 183.90 307.74

236.31 236.39 236.80 245.20 406.32

Table 3-63 EGPRS downlink data rates (kbit/s) with UDP (MCS1) Protocol Stack MCS1 and TS =1 MCS1 and TS = 2 MCS1 and TS = 3 MCS1 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 8.57 8.62 8.73 8.74 8.80 10.55 33.86

H/C 8.71 8.72

No H/C 17.37 17.42 17.53 17.54 17.60 21.10 67.72

H/C 17.52 17.52

No H/C 26.17 26.22 26.33 26.34 26.40 31.65 101.58

H/C 26.32 26.32

No H/C 34.97 35.02 35.13 35.14 35.20 42.20 135.44

H/C 35.12 35.12

Table 3-64 EGPRS downlink data rates (kbit/s) with UDP (MCS2) Protocol Stack MCS2 and TS = 1 MCS2 and TS = 2 MCS2 and TS = 3 MCS2 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 10.91 10.97 11.11 11.12 11.20 12.95 33.86

H/C 11.09 11.09

No H/C 22.11 22.17 22.31 22.32 22.40 25.90 67.72

H/C 22.30 22.30

No H/C 33.31 33.37 33.51 33.52 33.60 38.85 101.58

H/C 33.50 33.50

No H/C 44.51 44.57 44.71 44.72 44.80 51.80 135.44

H/C 44.70 44.70

68P02900W21-S 01 Feb 2007 3-193

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Table 3-65 EGPRS downlink data rates (kbit/s) with UDP (MCS3) Protocol Stack MCS3 and TS = 1 MCS3 and TS = 2 MCS3 and TS = 3 MCS3 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 14.42 14.49 14.68 14.70 14.80 16.55 33.86

H/C 14.65 14.66

No H/C 29.22 29.29 29.48 29.50 29.60 33.10 67.72

H/C 29.47 29.47

No H/C 44.02 44.09 44.28 44.30 44.40 49.65 101.58

H/C 44.27 44.27

No H/C 58.82 58.89 59.08 59.10 59.20 66.20 135.44

H/C 59.07 59.07

Table 3-66 EGPRS downlink data rates (kbit/s) with UDP (MCS4) Protocol Stack MCS4 and TS = 1 MCS4 and TS = 2 MCS4 and TS = 3 MCS4 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 17.15 17.23 17.46 17.48 17.60 19.35 33.86

H/C 17.42 17.43

No H/C 34.75 34.83 35.06 35.08 35.20 38.70 67.72

H/C 35.04 35.05

No H/C 52.34 52.43 52.66 52.68 52.80 58.05 101.58

H/C 52.64 52.65

No H/C 69.94 70.03 70.26 70.28 70.40 77.40 135.44

H/C 70.24 70.25

Table 3-67 EGPRS downlink data rates (kbit/s) with UDP (MCS5) Protocol Stack MCS5 and TS = 1 MCS5 and TS = 2 MCS5 and TS = 3 MCS5 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 21.82 21.93 22.22 22.24 22.40 23.90 101.58

H/C 22.17 22.19

No H/C 44.22 44.33 44.62 44.64 44.80 23.90 203.16

H/C 44.60 44.61

No H/C 66.62 66.73 67.02 67.04 67.20 23.90 304.74

H/C 67.00 67.01

No H/C 89.02 88.13 89.42 89.44 89.60 23.90 406.32

H/C 89.40 89.41

68P02900W21-S 3-194 01 Feb 2007

System Information: BSS Equipment Planning

GPRS/EGPRS air interface planning process

Table 3-68 EGPRS downlink data rates (kbit/s) with UDP (MCS6) Protocol Stack MCS6 and TS = 1 MCS6 and TS = 2 MCS6 and TS =3 MCS6 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 28.84 28.99 29.36 29.39 29.60 31.10 101.58

H/C 29.30 29.32

No H/C 58.44 58.58 58.96 58.99 59.20 62.20 203.16

H/C 58.94 58.94

No H/C 88.03 88.18 88.56 88.59 88.80 93.30 304.74

H/C 88.54 88.54

No H/C 117.63 117.78

H/C 118.14 118.14

118.16 118.19 118.40 124.40 406.32

Table 3-69 EGPRS downlink data rates (kbit/s) with UDP (MCS7) Protocol Stack MCS7 and TS =1 MCS7 and TS = 2 MCS7 and TS = 3 MCS7 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 43.65 43.87 44.43 44.49 44.80 46.90 101.58

H/C 44.35 44.38

No H/C 88.44 88.67 89.23 89.29 89.60 93.80 203.16

H/C 89.20 89.21

No H/C 133.24 133.47

H/C 134.00 134.01

No H/C 178.04 178.27

H/C 178.80 178.81

134.03 134.09 134.40 140.70 304.74

178.83 178.89 179.20 187.60 406.32

Table 3-70 EGPRS downlink data rates (kbit/s) with UDP (MCS8) Protocol Stack MCS8 and TS =1 MCS8 and TS = 2 MCS8 and TS = 3 MCS8 and TS = 4

No H/C App. user rate UDP IP user rate SNDCP LLC RLC/MAC Physical layer 53.00 53.27

H/C 53.85 53.88

No H/C 107.39 107.67

H/C 108.32 108.33

No H/C 161.79 162.07

H/C 162.72 162.73

No H/C 216.19 216.47

H/C 217.12 217.13

53.95 54.02 54.40 56.50 101.58

108.35 108.42 108.80 113.00 203.16

162.75 162.82 163.20 169.50 304.74

217.15 217.22 217.60 226.00 406.32

68P02900W21-S 01 Feb 2007 3-195

GPRS/EGPRS air interface planning process

Chapter 3: BSS cell planning

Table 3-71 EGPRS downlink data rates (kbit/s) with UDP (MCS9) Protocol Stack MCS9 and TS =1 MCS9 and TS = 2 MCS9 and TS = 3 MCS9 and TS = 4

No H/C App. user rate UD IP user rate SNDCP LLC RLC/MAC Physical layer 57.68 57.97

H/C 58.60 58.64

No H/C 116.87 117.17

H/C 117.88 117.89

No H/C 176.07 176.37

H/C 177.08 177.09

No H/C 235.27 235.57

H/C 236.28 236.29

58.71 58.79 59.20 61.30 101.58

117.91 117.99 118.40 122.60 203.16

177.11 177.19 177.60 183.90 304.74

236.31 236.39 236.80 245.20 406.32

68P02900W21-S 3-196 01 Feb 2007

Chapter 4 AMR and GSM planning

This chapter provides an overview of the Adaptive Multi-Rate (AMR) and GSM half rate feature and their operation within the Motorola system. The GSM half rate and the half rate portion of AMR are similar. Hence, the information here covers both features. The benefits of the features are outlined, and performance discussed. The manual gives an understanding of how AMR and GSM half rate works and how they are configured. The various parameters controlling AMR operation are discussed. However, not all of the commands and parameters are shown in detail. The topics described are as follows:
Introduction to AMR and GSM planning Quality and capacity Rate adaptation Handover and power control Miscellaneous information Half rate utilization Hardware

68P02900W21-S 01 Feb 2007 4-1

Introduction to AMR and GSM planning

Chapter 4: AMR and GSM planning

Introduction to AMR and GSM planning

AMR basic operation
Existing GSM speech codecs operate at a fixed coding rate. Channel protection is also fixed. AMR adapts the speech and channel coding rates according to the quality of the radio channel. This gives better channel quality and better robustness to errors. Capacity is enhanced by allocating half rate channels to some or all mobiles. In order to obtain the best balance between quality and capacity, the system allocates a half rate (hr) or full rate (fr) channel according to channel quality and the traffic load on the cell. The control system is not fixed but can be tuned to meet particular needs. The three primary levels of adaptation of the control system are:

Handovers between hr and fr channels according to traffic demands. Variable partitioning between speech and channel coding bit rates to adapt to channel conditions for best speech quality. Optimization of channel and codec control algorithms to meet specific user needs and network conditions.
fr only for maximum robustness to channel errors but no capacity advantage. hr only for maximum capacity advantage. Mixed hr/fr operation allowing a trade-off between quality and capacity.

This allows the codec to be applied in many ways, of which three important examples are:

GSM half rate basic operation

GSM half rate was introduced in phase 2 of the standards, and operates at a fixed coding rate. Due to this early introduction into the standards, the penetration rate of half rate capable mobiles is high. However, the speech quality is poor when compared to the half rate mode of AMR (as well as all forms of full rate speech). GSM half rate is used as a means to increase capacity within a cell. As with AMR half rate, capacity is increased by either always preferring half rate (hr), or by allocating a half rate or full rate (fr) channel according to channel quality and the traffic load on the cell. Handovers between hr and fr channels vary according to traffic demands. The best examples of applying the codec are:

hr only for maximum capacity advantage. Mixed hr/fr operation allowing a tradeoff between quality and capacity. AMR and GSM half rate interaction

AMR and GSM half rate can co-exist in a cell. A carrier could have a mix of GSM half rate and AMR (full rate and/or half rate) simultaneously. The parameters that govern half rate operation have been made generic to facilitate that style of operation.

68P02900W21-S 4-2 01 Feb 2007

System Information: BSS Equipment Planning

Introduction to AMR and GSM planning

New hardware
New hardware has been developed to support the AMR and the GSM half rate features. This equipment, in conjunction with the supporting software and firmware, provides the capabilities necessary to exploit the advantages of AMR and/or GSM half rate. This equipment consists of the following:

Double Kiloport Switch (DSW2) Double Kiloport Switch Extender (DSWX) Generic DSP Processing board 2 (GDP2) Remote Transcoder Unit 3 (shelf) (RXU3) Base Station System Cabinet 3 (BSSC3)

AMR and GSM half rate is used without the benefit of any of the new hardware; although not as efficiently (this is discussed later in the chapter).

Without new hardware, AMR needs the use of GDPs configured as EGDP(s).

Influencing factors
There are many factors to be taken into account when configuring/operating a system in which AMR and/or GSM half rate is present. These include:

AMR-capable handset penetration (see the first NOTE ). GSM half ratecapable handset penetration (see the second NOTE ). Transceiver capability. Carrier configuration. Use of reserved channels / cell congestion.

It is assumed that an AMR-capable handset or mobile includes both fr and hr capability. Most handsets or mobiles are GSM half rate capable.

68P02900W21-S 01 Feb 2007 4-3

Introduction to AMR and GSM planning

Chapter 4: AMR and GSM planning

Planning
The system operator must decide how the system should operate with regard to full and half rate, and what combination of new and old equipment is to be utilized. Other decisions, such as codec rates and backhaul, must also be made. Utilization of the half rate capability of AMR and/or GSM half rate. Quality and capacity describes the benefits of the AMR codecs and how AMR Full Rate and AMR Half Rate compare to the existing GSM codecs. The GSM Half Rate codec is compared to the other GSM codecs. Also discussed are the benefits in coverage of AMR Full Rate. The capacity increases made possible with half rate are discussed, with examples showing the potential gains under a variety of configurations and (half rate) capable handset penetration. The information in Quality and capacity can be used to help determine how AMR full rate and AMR/ GSM half rate is utilized. As stated earlier, there are three primary methods of AMR usage, two of which apply to GSM half rate:

AMR full rate only (AMR only): This has the advantage of providing better voice quality under a broad range of channel conditions. This method is robust but provides no capacity advantage per carrier. It is particularly suited to areas where adverse propagation conditions prevail. Forced half rate: This is used when capacity is paramount. Voice quality is sacrificed to carry more calls per carrier. It is used in severely congested areas, or where voice quality is not a concern. A mix of full rate and half rate: Full rate is generally used until the cell becomes congested, at which time half rate is employed. This configuration provides quality voice coverage until congestion is reached. This capacity on demand configuration is well suited for environments with varying traffic patterns. The information contained in Half rate utilization can be used to help configure the system to maximum effectiveness when half rate is used.

Rate adaptation provides information on the rate adaptation characteristics of AMR. Miscellaneous information provides information on emergency call handling and circuit pooling. Hardware contains a description of the new hardware and what advantages it delivers.

68P02900W21-S 4-4 01 Feb 2007

System Information: BSS Equipment Planning

Quality and capacity

Quality and capacity

Benefits of AMR
The ability of the AMR codec to change dynamically the allocation of source and channel coding bits provides a high level of speech quality. The overall improvements are dependant upon channel quality (C/I). As channel quality deteriorates, a codec with a higher level of error protection (and a corresponding decrease in speech quality) is selected, leading to an increase in sensitivity of the transceivers, thus providing optimum performance. The half rate mode of AMR can be utilized to obtain a capacity gain on the air interface. This can be tied to congestion at the cell level to provide capacity gains on an as needed basis. With AMR operating in full rate mode, or in a mix of full rate and half rate where handovers between the modes is permitted, a capacity gain can be realized because of the ability to operate at a lower C/I threshold. This can result in potentially higher traffic loading. However, the benefits of AMR do not extend to the signaling channels, or to the use of non-AMR codecs and data services. Capacity gains of this type are dependent on other factors (for example, propagation conditions) and are beyond the scope of this chapter. Under high channel error conditions, an AMR FR codec mode, which has a low source-coding rate and a high level of error protection, is selected. This allows good speech quality to be maintained under conditions 6 dB worse than the corresponding level for EFR. This translates to an improvement in terminal or BTS sensitivity, but is subject to the limit of robustness of the signaling channels (presumed to be at least 2 dB, and possibly as high as 4 dB or 6 dB). This can be exploited for range extension, or improved coverage in buildings. Range extension is discussed further in AMR voice quality improvement and coverage later in this chapter.

AMR Full Rate and AMR Half Rate speech quality

Introduction
Here, the relative performance of the AMR Full Rate and Half Rate speech codecs is shown for comparative purposes. Mean Opinion Scores (MOS) are subjective. Test conditions affect MOS. However, the relative performance of the codecs to each other is reliable. The conditions used in the tests are no background impairments, static channel conditions, and ideal frequency hopping.

The graphs in Figure 4-1 to Figure 4-3 and the accompanying information are extracted from GSM 06.75 (v. 7.2.0), Performance Characterization of the GSM Adaptive Multi-Rate (AMR) speech codec.

68P02900W21-S 01 Feb 2007 4-5

Quality and capacity

Chapter 4: AMR and GSM planning

AMR Full Rate

In Figure 4-1, AMR FR speech quality (best AMR codec) is compared with EFR and performance requirements under a range of channel conditions.
Figure 4-1 AMR FR/clean speech versus EFR versus performance requirements
MOS 5.0

4.0

3.0

2.0

Sel. Requirements AMR-FR EFR Conditions

1.0 No Errors Sel. Requirements AMR-FR EFR 4.01 4.06 4.01 C/I=16 dB C/I=13 dB 4.01 4.06 4.01 4.13 4.01 4.08 3.65 3.96 3.05 C/I=10 dB C/I= 7 dB C/I= 4 dB 3.65 3.59 1.53 2.66 C/I= 1 dB

Figure 4-2 shows the individual codec modes for AMR FR/clean speech, as illustrated in Figure 4-1.

68P02900W21-S 4-6 01 Feb 2007

System Information: BSS Equipment Planning

Quality and capacity

Figure 4-2 AMR FR/clean speech codec modes

MOS 5.0

4.0

3.0

2.0

EFR 12.2 10.2 7.95 7.4 6.7 5.9 5.15 4.75 No Errors C/I=16 dB C/I=13 dB 4.01 4.06 4.13 3.96 4.01 3.94 C/I=10 dB 3.65 3.93 4.05 4.08 3.98 3.80 C/I= 7 dB 3.05 3.44 3.80 3.96 3.84 3.86 3.69 3.58 3.52 C/I= 4 dB 1.53 1.46 2.04 3.26 3.11 3.29 3.59 3.44 3.43

Conditions C/I= 1 dB

1.0 EFR 12.2 10.2 7.95 7.4 6.7 5.9 5.15 4.75 4.01 4.01 4.06 3.91 3.83 3.77 3.72 3.50 3.50

1.43 1.39 1.87 2.20 2.43 2.66

AMR half rate

Figure 4-3 and Figure 4-4 show performance curves for AMR HR speech quality compared to EFR as well as GSM FR and HR under the same range of channel conditions as the AMR FR comparison shown in Figure 4-1 and Figure 4-2.

68P02900W21-S 01 Feb 2007 4-7

Quality and capacity

Chapter 4: AMR and GSM planning

Figure 4-3 AMR HR/clean speech versus EFR versus GSM FR versus GSM HR versus performance requirements
MOS 5.0

4.0

3.0 Sel. Requirements 2.0 AMR-HR EFR FR HR 1.0 No Errors Sel. Requirements AMR-HR EFR FR HR 3.99 4.11 4.21 3.50 3.35 C/I=19 dB C/I=16 dB C/I=13 dB C/I=10 dB C/I= 7 dB 3.99 4.04 3.99 3.96 3.72 4.21 3.50 3.14 3.38 3.74 3.14 3.24 2.74 3.10 3.34 2.74 2.80 C/I= 4 dB 1.50 2.00 1.58 1.50 1.92

Conditions

68P02900W21-S 4-8 01 Feb 2007

System Information: BSS Equipment Planning

Quality and capacity

Figure 4-4 AMR HR/clean speech codec modes

MOS 5.0

4.0

3.0

2.0

EFR 7.95 7.4 6.7 5.9 5.15 4.75 FR HR Conditions No Errors 4.21 4.11 3.93 3.94 3.68 3.70 3.59 3.50 3.35 4.04 3.93 3.96 3.95 3.90 3.82 3.60 3.46 C/I=19 dB C/I=16 dB C/I=13 dB 4.21 3.37 3.52 3.53 3.72 3.60 3.42 3.50 C/I=10 dB 3.74 2.53 2.74 3.10 3.19 3.38 3.30 3.14 3.24 C/I= 7 dB 3.34 1.60 1.78 2.22 2.57 2.85 3.10 2.74 2.80 1.21 1.33 1.84 2.00 1.50 1.92 C/I= 4 dB 1.58

1.0 EFR 7.95 7.4 6.7 5.9 5.15 4.75 FR HR

Conclusions
The MOS scores for AMR FR are higher than EFR, considerably better at lower C/I levels. AMR HR speech quality is better than GSM FR and HR, but not as good as EFR. If one considers a MOS score of 3.0 to be the accepted communications quality level, then at lower C/I levels (7 dB and 4 dB) the AMR HR speech coder quality is poor. AMR hr provides the capacity benefit of allowing two calls to exist in the space of one timeslot. This behavior suggests that one viable deployment strategy is to use the fr mode until capacity limitations force calls to utilize hr mode, at which time some fr calls can also be moved to hr. A hr call can also be moved to a fr channel through an interference-based handover, depending on the congestion state of the cell and system parameter settings. The Motorola system supports this configuration, as well as many others, including forcing all calls to use hr all the time, equipment permitting. Selection of a particular mode of operation is up to the user. MOS scores are subjective and vary depending upon customer expectations.

68P02900W21-S 01 Feb 2007 4-9

Quality and capacity

Chapter 4: AMR and GSM planning

AMR voice quality improvement and coverage

Analysis has shown that AMR FR under C/I = 13 dB provides the same quality of service (MOS = 4) as GSM FR/EFR under C/I = 15 dB. AMR FR provides better overall voice quality than GSM FR/EFR under comparable radio conditions. This can translate to an increase in coverage area. A study has been done to quantify the potential coverage gains. The following assumptions are used:

System is interference-limited (the impact of thermal noise is negligible compared with the level of interference). System is 100% loaded: all the available physical resources are used (this is the worst-case assumption - coverage gains increase with less loading). Path loss exponent assumed to be 3.76, and the shadowing lognormal standard deviation is 10 dB. Power control and any type of DTX are not used. All terminals are AMR.

The results of the study are shown in Table 4-1. The coverage reliability is expected to increase by 5 to 8 percentage points depending on the frequency reuse patterns. The link budget improvement can potentially lead to an increase in cell areas around 27%. This type of increase in coverage applies to existing networks where site spacing can be modified or new networks where it has to be selected. The majority of terminals are AMR. Non-AMR terminal performance could be degraded under these conditions.
Table 4-1 AMR potential coverage gains Frequency re-use pattern Coverage at 15 dB Coverage at 13 dB Gain in coverage (increase in cell radius) Gain in coverage area

1-3-3 3-1-3 3-3-9 4-1-4 4-3-12 7-1-7 7-3-21

44% 57% 81% 70% 92% 88% 98%

36% 49% 74% 62% 87% 82% 96%

8% 8% 7% 8% 5% 6% 2%

16.6% 16.6% 14.5% 16.6% 10.3% 12.4% 4%

First digit = # cell sites, second digit = # sectors/cell and third digit = # carriers/cell.

68P02900W21-S 4-10 01 Feb 2007

System Information: BSS Equipment Planning

Quality and capacity

Benefits of GSM half rate

GSM Half Rate offers enhanced capacity over the air interface, corresponding to the proportion of mobiles within a coverage area that supports Half Rate. GSM half rate 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. The GSM Half Rate codec uses the VSELP (Vector-Sum Excited Linear Prediction) algorithm. The VSELP algorithm is an analysis-by-synthesis coding technique and belongs to the class of speech coding algorithms known as CELP (Code Excited Linear Prediction). The benefits of GSM half rate are an increase in capacity at a cell without requiring additional transceiver boards or carriers. The use of half rate can be tied to congestion at the cell level to provide capacity gains on a needed basis.

GSM Half Rate speech quality

Figure 4-1 shows how GSM Half Rate compares with the EFR, FR, and AMR HR codecs. Mean Opinion Scores (MOS) are subjective and can vary depending upon customer expectations. Test conditions affect MOS. However, the relative performance of the codecs to each other is reliable. The conditions used in the tests are no background impairments, static channel conditions, and ideal frequency hopping.

In conclusion, the GSM Half Rate codec voice quality performance is inferior to the other codecs. This suggests a deployment strategy of using fr mode until capacity limitations force calls to utilize hr mode, at which time some fr calls can also be moved to hr. A hr call is also moved to a fr channel through an interference-based handover, depending on the congestion state of the cell and system parameter settings, as well as a quality-based handover when no viable candidate neighbor cells exist. The Motorola system supports this configuration, as well as many others, including forcing all calls to use hr all the time, equipment permitting. Selection of a particular mode of operation is the decision of the user.

Capacity increase due to half rate usage

On the air interface up to twice as many calls can be handled in a cell when half rate is used (as previously mentioned, this is a trade-off with quality). The actual increase in call carrying capacity is typically less than 100% due in part to the penetration level of half rate capable handsets. As the penetration level rises, the half rate carriers become more efficient. In Figure 4-4 to Figure 4-8, the carried Erlangs (at 2% blocking) are shown for a variety of carrier configurations. For each configuration, the capacity increase is shown as a function of the handset penetration level.

68P02900W21-S 01 Feb 2007 4-11

Quality and capacity

Chapter 4: AMR and GSM planning

The results shown were obtained through simulation and under the following assumptions:

A hr-capable handset is given a hr timeslot if available, else a fr timeslot on a fr carrier. Preference is to assign a fr-capable only handset to a fr carrier if available; else, it is assigned to a hr-capable carrier. Preference is at call establishment to assign a hr-capable handset an idle subchannel on a timeslot that has the other subchannel occupied with a call.

Graphs
The graphs are intended to illustrate the call carrying effectiveness as a function of hr carriers and hrcapable MS penetration and do not take into account any control channels. The actual carried Erlangs can be slightly less than the Erlangs in the graphs.
Figure 4-5 3 carriers, only one hr-capable carrier

Carried Erlangs (at ~2% blocking) 25.000 20.000 15.000 10.000 5.000 0.000 0.00

0.10

0.20

0.30 0.40 0.50 0.60 0.70 AMR Capable MS Penetration

0.80

0.90

1.00

68P02900W21-S 4-12 01 Feb 2007

System Information: BSS Equipment Planning

Quality and capacity

Figure 4-6 3 carriers, all hr-capable

Carried Erlangs (at ~2% blocking)

40.000 35.000 30.000 25.000 20.000 15.000 10.000 5.000 0.000 0.00 0.20 0.40 0.60 0.80 1.00 AMR Capable MS Penetration

Figure 4-7 5 carriers, only one hr-capable carrier

Carried Erlangs (at ~2% blocking)

40.000 35.000 30.000 25.000 20.000 15.000 10.000 5.000 0.000 0.00 0.20 0.40 0.60 0.80 1.00 AMR Capable MS Penetration

68P02900W21-S 01 Feb 2007 4-13

Quality and capacity

Chapter 4: AMR and GSM planning

Figure 4-8 5 carriers, only 3 hr-capable carriers

Carried Erlangs (at ~2% blocking) 60.000 50.000 40.000 30.000 20.000 10.000 0.000 0.00

0.10

0.20

0.30 0.40 0.50 0.60 0.70 AMR Capable MS Penetration

0.80

0.90

1.00

Figure 4-9 5 carriers, all hr-capable carriers

Carried Erlangs (at ~2% blocking) 80.000 70.000 60.000 50.000 40.000 30.000 20.000 10.000 0.000 0.00 0.10 0.20 0.30 0.40 0.50 0.60 0.70 AMR Capable MS Penetration 0.80 0.90 1.00

Conclusions
Figure 4-4 to Figure 4-8 are useful in illustrating that, for some deployment strategies such as a maximum capacity configuration, more carrier equipment should be configured as hr-capable when hrcapable handset penetration raises. For example, in a 5 carrier cell with a 50% handset penetration rate, there is not much difference in Erlang capacity between a 3 hr-capable carrier configuration and a 5 (all) hr-capable carrier configuration. The 5 hr-capable carrier configuration is better able to utilize the extra capacity that hr offers as the handset penetration rises. GSM hr-capable handset penetration is expected to be high.

68P02900W21-S 4-14 01 Feb 2007

System Information: BSS Equipment Planning

Quality and capacity

When migrating a system to one that includes half rate, ensure that the call capacity rating of the various components of the system have not exceeded. Use of hr improves the spectral efficiency over the air interface (and potentially the backhaul), but from a load perspective, a half rate call has the same impact as a full rate call. Other strategies, such as utilizing hr only during periods of high demand, would need fewer hr-capable carriers. Figure 4-4 to Figure 4-8 demonstrates how even adding one hr-capable carrier can increase Erlang capacity.

Timeslot usage
This section briefly describes timeslot configuration and the algorithm used to optimize usage. A GSM carrier consists of 8 timeslots, some or all of which can be used for voice traffic. In full rate, each voice call occupies one timeslot. In half rate, the timeslot is split into two subchannels, each of which is capable of supporting one hr call. A fr call cannot be carried within two subchannels split across two timeslots. At any instance, depending on configuration, a carrier contains a combination of fr and hr calls. To optimize capacity, it is desirable not to have fragmented hr usage. That is, it is best to use both subchannels of a single timeslot rather than one subchannel on two timeslots. This frees up contiguous subchannels for use in a fr call. The Motorola algorithm attempts first to assign new calls to timeslots that have one subchannel in use before using a timeslot with both subchannels idle. This provides a large degree of concentration. Some degree of fragmenting is unavoidable as calls begin and end and the algorithm attempts to fill in the holes as new calls arrive. This applies to all arriving calls (for example, originations, handovers, and so on). It was also considered whether to further pack hr calls together through intra-cell handover whenever fragmenting reaches a level where a fr call can be blocked. Simulations have been carried out under a variety of configurations and conditions, and it was determined that the negative aspects of performing the otherwise unnecessary handover outweighs the slight capacity gain. Although the results varied according to penetration rate and configuration, in general, additional blocking of 1.5% or less resulted for the fr only handsets (as compared with the hr-capable handsets). Limiting the number of hr capable carriers in a cell can reduce this disparity.

68P02900W21-S 01 Feb 2007 4-15

Rate adaptation

Chapter 4: AMR and GSM planning

Rate adaptation
Introduction
Rate Adaptation (RA) is particular to AMR and refers to the control and selection of the codec mode based upon channel quality. Another name for it is Codec Mode Adaptation. The term Codec Mode refers to one of the various choices of bit partitioning between the speech and error protection bits.

Codec modes
14 codec modes are defined for AMR; 8 for the fr channel mode, and 6 for the hr channel mode. Up to 4 codec modes are utilized for any given voice call. This is called the Active Codec Set (ACS). The uplink and downlink directions can each use a different codec mode; hence, there are 2 sets of associated thresholds and hysteresis, one for uplink and one for downlink. The ACS can be selected from the supported codec modes. An analysis has been performed to determine that common set of codec modes should be supported across all the CCU platforms (not all platforms could support all of the codec modes). The conditions is a 900 MHz, ideal frequency hopped system with a co-channel interferer and a typical urban multipath channel model. The speech is at a nominal input level and is not degraded by background noise. The result is the selection of 5 fr and 5 hr codec modes, as shown in Table 4-2. The shaded areas indicate the codec modes that are not supported.
Table 4-2 Supported AMR codecs Speech codec bit rate (fr) Is codec mode supported? Speech codec bit rate (hr) Supported?

12.2 kbit/s 10.2 kbit/s 7.95 kbit/s 7.4 kbit/s 6.7 kbit/s 5.9 kbit/s 5.15 kbit/s 4.75 kbit/s

Yes Yes No Yes Yes No Yes Yes

N/A N/A 7.95 kbit/s 7.4 kbit/s 6.7 kbit/s 5.9 kbit/s 5.15 kbit/s 4.75 kbit/s

N/A N/A Y Y Y Y Y N

Through simulation and testing, default values were determined for the ACS and initial codec modes. These initial values are subjected to change and are appropriate for all conditions. The analysis provided the following defaults for the ACS:

Full Rate: 12.2 kbit/s, 10.2 kbit/s, 7.4 kbit/s, and 5.15 kbit/s. Half Rate: 7.4 kbit/s, 5.9 kbit/s, and 5.15 kbit/s.

If 16 kbit/s backhaul is used for the BTS-BSC interface (that is 4 x 64 kbit/s timeslots per hr carrier) then the 7.95 kbit/s codec mode is added to the hr ACS.

68P02900W21-S 4-16 01 Feb 2007

System Information: BSS Equipment Planning

Rate adaptation

An initial codec mode is also required. The analysis provided the following default values:

FR initial codec mode: 10.2 kbit/s. HR initial codec mode: 6.7 kbit/s.

The HR initial codec mode remains at 6.7 kbit/s even if the 7.95 codec mode is added to the HR ACS.

Thresholds and hystereses

Associated with the Active Codec Set are the thresholds and hystereses used for the codec mode adaptation in the BSS and the MR for both uplink and downlink directions. The codec mode is changed rapidly in response to the changing radio conditions as illustrated in Figure 4-10.
Figure 4-10 Rate adaptations: codec modes, thresholds and hystereses
C/I CODEC_MODE_4 THR_3 + HYST_3 =THR_MX_ Up (3) THR_3 CODEC_MODE_3 THR_2 + HYST_2 =THR_MX_ Up (2) THR_2 CODEC_MODE_2 THR_1 + HYST_1 =THR_MX_ Up (1) CODEC_MODE_1 THR_1 = THR_MX_ Dn (2) = THR_MX_ Dn (3) = THR_MX_ Dn (4)

Rate adaptation thresholds and hystereses are set on a per cell basis.

Downlink adaptation MS monitor

There is a risk that certain mobiles have an impaired ability to estimate correctly the C/I for a channel in certain conditions. For these mobiles the codec mode adaptation threshold and hysteresis values proves to be inefficient, meaning that the threshold and hysteresis values are out of the range of the C/I measuring ability of the MS, resulting in the MS being unable to adapt its codec mode efficiently. For this reason, the BSS monitors mobiles to detect such scenarios. The BSS uses the Codec Mode Requests and the reported RXQUAL values from the MS to determine if the threshold and hysteresis values used by the MS are inefficient, and increase or decrease the threshold and hysteresis values accordingly. The BSS instructs the MS of the change in threshold and hysteresis values using the Channel Mode Modify procedure. A list of parameters with their ranges and default values (subject to change) is provided in Table 4-3 for completeness.

68P02900W21-S 01 Feb 2007 4-17

Rate adaptation

Chapter 4: AMR and GSM planning

Table 4-3 BSS parameters used to determine MS threshold and hysteresis Parameter amr_ms_monitor _period Minimum Maximum Default Description

10SACCH periods

120SACCH periods

40SACCH periods

Used for detecting MSs continually requesting the highest or lowest modes. If the user specifies a value of zero, then the MS monitor functionality is disabled.

amr_ms_high _cmr amr_ms_low _cmr amr_ms_high _rxqual

50%

100%

99%

Percentages for monitoring AMR MSs continually requesting the highest codec mode. Percentages for monitoring AMR MSs continually requesting the lowest codec mode. Threshold for monitoring AMR MSs continually requesting the highest codec mode. The threshold defaults to 2.5% BER or RXQUAL4

50%

100%

95%

0QBand Units

7QBand Units

4QBand Units

amr_ms_low _rxqual

0QBand Units

7QBand Units

2QBand Units

Threshold for monitoring MSs continually requesting the lowest mode. The threshold defaults to 0.5% BER or RXQUAL 2

amr_dl_thresh _adjust

1 dB

7 dB

3 dB

For applying compensation to the C/I adaptation thresholds. Range is 1 to 7 dB in steps of 1 dB.

68P02900W21-S 4-18 01 Feb 2007

System Information: BSS Equipment Planning

Handover and power control

Handover and power control

Introduction to handover and power control
This section explains the new AMR and GSM half rate specific handover and power control threshold parameters. It does not explain how they are used, as this is according to current operation. The ranges are not indicated either, as they are like the existing values.

Handover and power control thresholds

The upper and lower Rxqual thresholds for handover and power control are affected by the ACS within a cell. As a result, new thresholds are provided for AMR-specific use. The existing parameters and levels are still applicable to non-AMR calls. The half rate Rxqual values are used for both GSM half rate and AMR half rate operation, as behavior at Rxqual decision points is similar. The Rxlev thresholds are applicable to both AMR and non-AMR calls, hence no new Rxlev parameters are introduced. Analysis has been carried out to determine a default set of AMR-specific Rxqual threshold values. These values (see Table 4-4, which are preliminary and subject to change, are applicable to the fr ACS and the hr ACS as described in Rate adaptation. The default database values follow the recommendations of Rxlev Handovers Disabled and Uplink diversity.

68P02900W21-S 01 Feb 2007 4-19

Handover and power control

Chapter 4: AMR and GSM planning

Table 4-4 Handover and power control - Full and Half Rate default values Thresholds (UL/DL) - all figures in QBand Units Threshold name Non Frequency Hopping No UL Diversity RXLEV enabled l_rxqua l_XX_p_ amr_fr l_rxqua l_XX_h_ amr_fr l_rxqua l_XX_p_ hopping _amr_fr l_rxqua l_XX_h_ hopping _amr_fr l_rxqua l_XX_p_ hr l_rxqua l_XX_h_ hr u_rxqua l_XX_p_ hr l_rxqua l_XX_p_ hopping _hr l_rxqua l_XX_h_ hopping _hr RXLEV disabled UL Diversity RXLEV enabled RXLEV disabled RXLEV enabled Frequency Hopping No UL Diversity RXLEV disabled UL Diversity RXLEV enabled RXLEV disabled

3/3

3/3

4/3

4/3

4/4

4/4

5/4

5/4

4/4

4/4

5/4

5/4

5/5

5/5

6/5

6/5

2/2

2/2

2/2

2/2

3/3

3/3

3/3

3/3

0/0

0/0

0/0

0/0

2/2

2/2

2/2

2/2

3/3

3/3

3/3

3/3

XX refers to ul or dl.

68P02900W21-S 4-20 01 Feb 2007

System Information: BSS Equipment Planning

Handover and power control

Regarding intra-cell hr to fr handovers: An intra-cell handover from a hr channel to a fr channel is attempted either if an interference based handover is indicated (the received quality is of a BER greater than l_rxqual_xx_h_hr and the signal level is u_rxlev_xx_ih and both hr_intracell_ho_allowed and force_hr_usage allow for it). or A quality-based handover is indicated and there are no viable neighbor cells, and both hr_intracell_ho_allowed and force_hr_usage allow for it.

68P02900W21-S 01 Feb 2007 4-21

Miscellaneous information

Chapter 4: AMR and GSM planning

Miscellaneous information
Emergency call handling
It is a priority to place an emergency call upon a fr channel, if possible. If necessary to do so, a call of a lower priority is pre-empted. When selecting a call to pre-empt, the software attempts to minimize the disruption by choosing first a fr call of lower priority. Failing that, a lower priority single occupancy hr call (the other subchannel is idle) is searched for, followed by a timeslot carrying two hr calls (both being of lower priority).

Circuit pooling
On the terrestrial route connecting the BSS and the MSC, certain circuits can be used for different combinations of bearer capabilities. This can be realized in practice by grouping the circuits into pools supporting the same channel types. The MSC holds this information as route data. If the MSC allocates an A interface circuit, it should only ask for resources from the BSS that it knows are not incompatible with the nominated circuit. In the case where several circuit pools (groups of circuits supporting the same channel types) are available on the BSS MSC interface, the terrestrial circuit allocated by the MSC is selected taking into account the circuit pool the circuit belongs to and the required channel type. The GDP supports FR, GSM HR and EFR speech only, while the EGDP supports fr, EFR, and AMR. The GDP2 supports FR, GSM HR, EFR, and AMR. The older XCDR card only supports GSM full rate. When a mix of transcoding equipment (GDP, EGDP/GDP2) is used in conjunction with AMR being enabled, the MSC must select a CIC, which is attached to an EGDP or GDP2, if AMR is the only option allowed in the Channel Type element of the Assignment Request or Handover Request messages. If AMR is one of the possible options (FR or EFR being the others) then the MSC should select an EGDP/GDP2 CIC. If the call is not AMR possible, the MSC should select a GDP CIC. If AMR is indicated as the only option and a CIC attached to a GDP is selected, the call is rejected. Similarly, when GSM HR is the only option allowed, the MSC must avoid choosing an EGDP CIC. The ability of the MSC to select a CIC based on the available channel types is called circuit pooling. The BSC does not support the option to do the CIC selection, nor the circuit pool and circuit pool list elements. Therefore, it is incumbent upon the MSC to do the selection. The MSC vendors (Alcatel, Siemens, Nokia, and Nortel) support circuit pooling. (Specifically it was asked about circuit pool 26, which all except Alcatel support - Alcatel supports circuit pool 27.) This topic is expanded upon in Transcoding in Chapter 6, BSC planning steps and rules, and Transcoding in Chapter 7, RXCDR planning steps and rules. For more detailed information on circuit pooling, refer to GSM 08, Mobile-services Switching Centre Base Station System (MSC - BSS) interface; Layer 3 specification.

68P02900W21-S 4-22 01 Feb 2007

System Information: BSS Equipment Planning

Half rate utilization

Half rate utilization

Description
Some parameters associated with the usage of half rate (hr) have been introduced to allow the operator to tailor their system to suit their needs. Brief descriptions of these parameters and their impact to system operation are provided here.

Parameter descriptions
Unconditionally forcing hr usage
Force hr usage (force_hr_usage) This parameter allows the operator to force hr usage when assigning a resource. The MSC channel type preference is overridden whenever possible. The parameter is checked upon arrival of a new call entering the system and all handovers. The parameter can be set to enable or disable and defaults to disable. It is configurable on a BSS basis.

Cell congestion threshold forcing hr usage

Congestion threshold for hr usage (new_calls_hr) This parameter is used to qualify hr usage in a cell with the level of cell congestion (that is, busy traffic channels). When triggered, the MSC channel type preference is overridden whenever possible. The parameter is checked upon arrival of a new call entering the system and for all handovers. For multi-zone cells, the BSS considers only outer zone resources when establishing whether the threshold has been exceeded. Both the fr and hr resources within the outer zone are used for the calculation. See also the Inner zone utilization threshold. This parameter range is 0-101 in steps of 1%. The value of 101 indicates the mechanism is disabled and is the default value. It is configurable on a cell basis.

Congestion relief
Some capabilities of hr utilization are similar to, or make use of the calculations of, some parts of the existing congestion relief feature set; in particular, directed retry and advanced congestion relief. These features must be enabled in order for those particular hr capabilities to operate properly. A brief description of the pertinent congestion relief features is provided for completeness. Advanced congestion relief allows the operator to set thresholds, in units of percentage, on a cell basis that can trigger the handover of some calls to neighboring cells in order to reduce congestion in the triggering cell. There are two sets of thresholds defined within a cell that control the triggering of congestion based intercell handovers:
tch_congest_prevent_thres (1-101) mb_tch_congest_thres (1-101)

68P02900W21-S 01 Feb 2007 4-23

Half rate utilization

Chapter 4: AMR and GSM planning

The tch_congest_prevent_thres parameter specifies the level at which the congestion relief procedure is initiated. The mb_tch_congest_thres parameter specifies the level at which a MultiBand MS is redirected to the preferred band. mb_tch_congest_thres must be less than or equal to tch_congest_prevent_thres. When the congestion relief threshold (tch_congest_prevent_thres) exceeds, the BSS behaves according to the setting of the element ho_exist_congest:

Attempts to handover as many calls as the number of queued requests, Attempts to handover as many call as meet the congestion handover criteria.

Calls within the cell consider RF conditions, so only the MSs near the candidate cell(s) are moved. Directed retry (mb_tch_congest_thres) redirects new traffic when the cell is congested, resulting in the new call being moved to an alternative cell.

Call reconfiguration threshold

Intra-cell fr to hr call reconfiguration threshold (reconfig_fr_to_hr) When the indicated threshold is exceeded, some fr calls within a cell are reconfigured (by handover) to a hr channel within the same cell in order to reduce congestion in that cell. This mechanism works in conjunction with the congestion relief feature, and needs congestion relief to be enabled (within the cell). The threshold is calculated upon arrival of a new call entering the system and all handovers.

The BSS applies qualification criteria to the half rate capable full rate calls before allowing the reconfiguration to a half rate traffic channel. The qualification is based upon the existing congestion relief (directed retry alternatives) criteria for congestion based inter-cell handovers. The criteria identify calls, which are at the extremities of the cell by using a power budget calculation involving the neighbor handover congestion margin. The BSS does not perform reassignment to a half rate traffic channel for a call, which is identified by the existing congestion relief calculations as being at the extremities of the cell. This qualification is performed in an attempt to ensure that the operator is provided with adequate QoS when the call is reassigned to a half rate traffic channel. For multi-zone cells, the BSS considers only outer zone resources when establishing whether the threshold has been exceeded. Both the fr and hr resources within the outer zone are used for the calculation. See also the Inner zone utilization threshold. Once triggered, the BSS reconfigures, as many qualifying existing hr-capable calls (currently using fr) to use hr as there are hr resources available. This parameter range is 0-101 in steps of 1%. The value of 101 indicates the mechanism is disabled and is the default value. It is configurable on a cell basis.

Inner zone utilization threshold

Inner zone utilization threshold (inner_hr_usage_thres) This parameter is necessary because the reconfig_fr_to_hr and new_calls_hr thresholds are triggered by the usage of the outer zone only within a cell.

68P02900W21-S 4-24 01 Feb 2007

System Information: BSS Equipment Planning

Half rate utilization

Both concentric cells and dual band cells are multi-zone cells. The situation can occur where the inner zone has low usage but the outer zone is congested such that the reconfig_fr_to_hr threshold is exceeded. The BSS attempts to trigger full rate to half rate intra-cell handovers for the calls that qualify. If some of the calls that qualify reside within the inner zone, the BSS attempts to reconfigure these half rate capable full rate calls to half rate when the inner zone is not congested. A similar situation can occur when the new_calls_hr threshold is exceeded and new calls are assigned. To prevent these situations from occurring, an additional threshold is applied. The inner zone utilization threshold (inner_hr_usage_thres) is used for this purpose. It protects against reconfigurations within, and new hr calls assigned to the inner zone, when the usage of the inner zone is low. The inner_hr_usage_thres is applied when the utilization of half rate is triggered by reconfig_fr_to_hr being exceeded and when new_calls_hr is exceeded. If the threshold reconfig_fr_to_hr has been exceeded, half rate capable full rate calls residing on the inner zone are eligible as candidates for reconfiguration from full rate to half rate if the inner_hr_usage_thres has also been exceeded. If the threshold new_calls_hr has been exceeded, half rate capable calls are eligible to be assigned directly to half rate channels within the inner zone if the inner_hr_usage_thres has also been exceeded. This parameter range is 0-101 in steps of 1%. The value of 101 indicates no half-rate usage in the inner zone and is the default value. It is configurable on a cell basis.

Reserved timeslots
Half rate resource guard limit (hr_res_ts) When congestion triggered half rate usage either is employed, through call assignments (cell congestion threshold forcing hr usage) or through reconfigurations (call reconfiguration threshold), there must be available hr resources for the mechanism to work properly. This is normally accounted for by setting reconfig_fr_to_hr and new_calls_hr such that when they are triggered, there are sufficient resources available for the half rate calls. However, in multi-zone cells, inner zone resources could be exhausted before any congestion thresholds are reached (the thresholds only consider outer zone resources). To ensure that there are half rate resources available, the operator has the option to allow the BSS to reserve a maximum number of (half rate capable) traffic timeslots within the inner zone. This facility is provided to ensure that when a multi-zone cell enters into congestion, there are half rate capable resources available within the inner zone to allow half rate utilization related procedures to be employed. When reserved timeslots only are left within an inner zone, a full rate resource is sought in the outer zone before the reserved timeslots in the inner zone being considered. The reserved timeslots are applied to the inner zone only, although it is configurable on all cells and not just multi-zone cells. It has no effect when set on a non multi-zone cell. The actual value within the inner zone can be dynamically limited to be less than hr_res_ts by the BSS. The BSS limits the hr_res_ts for the inner zone if the BSS detects that the inner_hr_usage_thres is not able to exceed if the hr_res_ts element is left as the user defined. hr_res_ts is also limited by the number of half rate capable resources available in the cell or zone. This parameter range is 0-255 in steps of one timeslot. The default value is 2 timeslots (each timeslot is capable of supporting two hr calls). It is configurable on a cell basis.

68P02900W21-S 01 Feb 2007 4-25

Half rate utilization

Chapter 4: AMR and GSM planning

Intra-cell hop count

Number of intra-cell interference handovers (hr_fr_hop_count). Intra-zone intra-cell hr interference handovers are governed by the BSS in a similar manner to how fr calls are governed by the existing hop_count and hop_count_timer elements. The current functionality restricts the number (hop_count) of intra-cell interference based handovers within a period (hop_count_timer). If the hop_count is exceeded within the hop_count_timer period, the BSS triggers an inter-cell quality based handover for the call. If so many intra-cell interference based handovers are performed in a short period, it indicates that the cell is experiencing problems with bad interference and the call would be best served by the network by being moved to another cell. A similar mechanism is employed for intra-cell half rate interference handovers. All intra-cell half rate interference handovers contribute to the existing hop_count. The hr_fr_hop_count parameter is provided to limit the number of intra-cell interference based handovers from hr to fr. The BSS does not allow an intra-cell congestion handover to be performed by a call for which the hr_fr_hop_count is met and the hop_count_timer has not expired. This allows a call experiencing repeated high interference levels to remain on a fr channel rather than hr during congestion. An inter-cell handover is not triggered by hr_fr_hop_count, for this functionality the existing hop_count parameter is used. The hop count timer (hop_count_timer) is an existing parameter, used to qualify the new hr (hr_fr_hop_count) element and the existing element (hop_count). This parameter range is 0-255 in steps of 1. The default value is 1 hop. It is configurable on a cell basis. It must be set to a value less than or equal to hop_count.

hr intra-cell handover support

Enable/Disable (support) of hr intra-cell handover (hr_intracell_ho_allowed). The hr_intracell_ho_allowed element contains an option to disable intra-cell quality handovers for half rate channels. The element has 4 possible values, which take effect when a hr intra-cell handover is triggered by the BSS. For interference based handovers it further specifies the possible target channel types - full and/or half rate. Quality based handovers always target a full rate channel when handovers are enabled. The force_hr_usage element overrides any preference specified with the hr_intracell_ho_allowed element. The value of the element causes the following behavior: If hr_intracell_ho_allowed is set to hr intra-cell, handovers are disabled. If handover required is sent to MSC, then the control for this hr intra-cell handover is passed to the MSC by sending a Handover required message, identifying the current cell as the only handover candidate. This functionality mirrors the fr functionality specified by the element: intra_cell_handover_allowed. If hr_intracell_ho_allowed is set such that hr intracell handovers are disabled. Then no Handover Required is sent to MSC, then hr intra-cell handovers are not supported within the cell. The intra-cell handover request is ignored by the BSS. This functionality mirrors the fr functionality specified by the element: intra_cell_handover_allowed. If hr_intracell_ho_allowed is set such that hr intra-cell handovers are enabled and fr is only allowed, the BSS attempts to allocate a fr channel as a target resource for the hr intra-cell interference or quality-based handover. If hr_intracell_ho_allowed is set such that hr intra-cell handovers are enabled and hr is allowed, the BSS attempts to allocate a hr or fr target resource for the hr intra-cell interference based handover, based on the congestion levels within the cell, the MSC preference and the user preference. A qualitybased handover always targets a fr channel.

68P02900W21-S 4-26 01 Feb 2007

System Information: BSS Equipment Planning

Half rate utilization

This parameter range is 0-3 and is configurable on a cell basis. The default value is 3.
Where Is

0 1 2 3

Half-rate intra-cell handovers are not initiated by the BSS. Handover required sent to MSC. Half-rate intra-cell handovers are disabled. Handover required not sent to MSC. Half-rate intra-cell handovers are enabled. Full-rate only allowed. Half-rate Intra-Cell handovers are enabled. Half-rate and full-rate allowed.

It is recommended that hr_intracell_ho_allowed is set to a value of 2 or 3 dependent on the half rate (AMR or GSM) strategy of the network. Where half rate is being used to maximize capacity gains by half rate, with call quality of secondary concern, then a value of 3 should be used. Where half rate is being used to provide capacity gains using half rate but with more emphasis placed on call quality, then a value of 2 should be used.

Operational aspects
Using half rate exclusively
In some situations, the operator can decide to maximize half rate usage in the system by enabling the force AMR hr usage parameter (force_hr_usage). This forces all hr-capable MSs to be placed upon an available hr capable carrier, provided it is possible (that is MSC allows AMR hr and/or GSM hr, the CIC is capable of the transcoding, a hr channel is available, and so on). This setting maximizes Erlang capacity in the system at the expense of call quality (due primarily to the lower MOS of hr) and to a lesser extent the prohibiting of hr to fr intra-cell handovers). As an alternative to using force_hr_usage, new_calls_hr can be set low and hr_intracell_ho_allowed used to control intra-cell handovers. hr_intracell_ho_allowed can then be set to allow hr to fr intra-cell handovers, thus improving call quality in some instances.

Using half rate in conjunction with congestion

The system is configured on a cell basis, to tie hr usage to the congestion level within a cell (new_calls_hr). This allows calls to be handled at the higher voice quality (fr) level until cell congestion reaches a configurable threshold, at which point new hr-capable calls are assigned to hr channels (hrcapable means that the MSC allows AMR and/or GSM hr, the CIC is capable of the transcoding, a hr channel is available, and so on). By using the existing congestion relief feature and the cell reconfiguration threshold, additional capacity can be attained. As described earlier, the congestion relief feature can be used to identify calls most likely to benefit from a switch to another, less congested, cell, and perform a handover to move them. When this mechanism is employed, the operator can then use the cell reconfiguration capability to increase capacity further by reconfiguring qualifying fr calls to hr. Congestion is calculated as a function of busy timeslots (and half timeslots) divided by all timeslots (not counting control channels). The inner zone utilization threshold is used in multi-zone cells and prevents unnecessary inner zone reconfigurations. The configuration of parameters takes place as follows: The congestion threshold for hr usage (new_calls_hr) is selected.

68P02900W21-S 01 Feb 2007 4-27

Half rate utilization

Chapter 4: AMR and GSM planning

If it is desired to attain additional capacity through call reconfigurations, and the congestion relief feature is enabled, then the cell reconfiguration threshold is set at a level at which it wishes to force qualifying MSs (on a fr channel) to be reconfigured to hr (reconfig_fr_to_hr). This can be set above or below the congestion relief threshold, as calls qualifying for congestion relief are not candidates for fr to hr reconfiguration. If voice quality (that is, fr) is the primary concern, then congestion relief handover should be performed first. In addition, the reconfiguration threshold must not be set the congestion threshold for hr usage (new_calls_hr), otherwise calls could be assigned fr and immediately reconfigured to hr. For multi-zone cells, an inner zone utilization threshold is selected. In many cases, the criteria for inner zone hr utilization is the same as the outer zone. In these cases, the inner zone utilization threshold can be set the same as the new call threshold or the reconfiguration threshold. Following the descriptions, the thresholds could be set in the pattern shown in Figure 4-11.
Figure 4-11 Congestion threshold settings for AMR half rate
CONGESTION HIGH
reconfig_fr_to_hr new_calls_hr and inner_hr_usage_thres Congestion relief threshold

LOW

hr intra-cell handover control

The intra-cell hop count (hop_count) is set to the desired value. It must be set equal to or less than the hop_count parameter. The hop count timer (hop_count_timer) is also set to the desired value. The level of support of hr intra-cell handovers (hr_intracell_ho_allowed) is configured. The value of these settings is particular to the system being optimized.

AMR hr and GSM hr operation

AMR hr and GSM hr are compatible with each other. When GSM half rate and AMR are enabled in the BSS and in a cell, half rate-enabled carriers are capable of supporting both AMR and GSM calls. The selection of AMR or GSM is dependent upon the MSC preferences (indicated in the Channel Type element of the Assignment Request or Handover Request messages) and the capabilities of the selected CIC.

68P02900W21-S 4-28 01 Feb 2007

System Information: BSS Equipment Planning

Hardware

Hardware
Equipment descriptions
New hardware (and associated software) has been developed to enhance the operation of AMR and/or GSM half rate. Each new item is described here.

DSW2 and DSWX

The DSW2 provides two improvements over existing capability:

It allows for 8 kbit/s subrate switching in the BSC and RXCDR (called extended subrate switching (ESS) mode). When used in the RXCDR along with DSWXs, it allows for double the timeslot capacity (with one extension shelf, 1024 timeslots per shelf) (called enhanced capacity (EC) mode).

ESS mode is used to decrease backhaul costs when half rate is in use between the BTS and BSC and (if also enabled in the RXCDR) the BSC and RXCDR. As long as the 7.95 codec mode (AMR) is not used, the backhauled TRAU fits in an 8 kbit/s subchannel. On the BTS - BSC interface, this can result in a 50% saving in backhaul costs per 8 kbit/s hr-capable carrier. Without 8 kbit/s switching, each half rate call needs a full 16 kbit/s backhaul bearer, or four 64 kbit/s timeslots per carrier. With 8 kbit/s switching, the same backhaul as is required for full rate (two 64 kbit/s timeslots) is used. A similar saving can be achieved on the BSC - RXCDR interface. When ESS mode is enabled in the BSC, 8 kbit/s backhaul can be used between the BTS and BSC. For every connected RXCDR with ESS enabled, 8 kbit/s backhaul can be used between the BSC and that RXCDR. Use of ESS mode needs all DSW2s to be used (within the BSC or RXCDR). KSWXs and DSWXs are used (exclusively or mixed), with the restriction that a KSWX cannot be connected to a DSWX or viceversa. EC mode is available in the RXCDR and can be used to increase the number of timeslots available. Each device (that is MSIs, GDPs, EGDPs, and GDP2s) needs a specific number of timeslots. By increasing the number of timeslots available across two shelves, more combinations of equipment are possible. This capability is likely to be used in conjunction with the RXU3 shelf, which provides for additional E1 connectivity. (More detailed information is available in the later chapters of this manual.) EC mode needs the use of all DSW2s and DSWXs. DSW2s and DSWXs are backwards compatible with KSWs and KSWXs, and are interchangeable (in nonESS and non-EC modes) with, again, the restriction that a KSWX cannot be connected to a DSWX or vice-versa.

EGDP and GDP2

The current GDP can terminate 30 terrestrial circuits and handle the transcoding for GSM Full Rate (FR), Enhanced Full Rate (EFR) and GSM Half Rate (HR). It takes up one slot and connects to a single E1 span line. Due to the added processor burden required by AMR, the GDP cannot support 30 channels beyond FR/EFR/HR. Two cards however, operating in a tandem configuration through a firmware upgrade, can support a and 30 channels of FR/EFR/AMR. This arrangement of two GDPs is called an EGDP. It occupies two card slots and can terminate one E1 span line.

68P02900W21-S 01 Feb 2007 4-29

Hardware

Chapter 4: AMR and GSM planning

EGDP cannot support GSM HR. A more efficient solution is provided through a new development, the GDP2. With its upgraded DSP and other enhancements, the GDP2 is capable of transcoding 60 channels of FR/EFR/HR/AMR. It takes up one card slot and can terminate two E1 span lines. All card combinations are present in a system simultaneously. When the GDP2 is inserted into a card slot that terminates only one E1 span (a non-RXU3 shelf) 30 terrestrial circuits are supported.

RXU3
The existing RXU shelf provides 19 MSI slots (see NOTE), of which 5 are considered MSI-capable, meaning they have connectivity for two E1 span lines. The other 14 slots can terminate only one E1 span line, as they were designed to hold GDPs (or the older XCDRs). The RXU3 shelf provides for termination of two E1 span lines per card slot. A combination of MSIs and XCDR/GDP/EGDP/GDP2s can share these 19 slots without connectivity restriction (timeslot restrictions still apply). This enables the GDP2s to be used to capacity. Within the RXCDR, enhanced capacity mode must be enabled to access the second E1 when GDP2s are used. Within the current BSC, the BSU shelf contains 12 MSI slots, of which up to 6 slots are used for the transcoder function. All slots support the connectivity for two E1 terminations per card slot, allowing GDP2s to be used to capacity.

These are called MSI slots, but they may contain either a MSI or a transcoder board.

BSSC3
The BSSC2 cabinet has connectivity for up to 48 E1 span lines, which is the capacity of two of the existing shelves. To accommodate the additional shelf capacity, a new BSSC3 cabinet has been developed which can terminate up to 76 E1 span lines. This is accomplished by adding 6 additional T43/BIB boards to the cabinet top. Like the BSSC2, the BSSC3 cabinet can function as a BSC (BSC2) or an RXCDR (RXCDR2), depending on how the cabinet shelves are equipped. Figure 4-12 shows the alternative configurations available for the BSSC3.

Earlier BSUs/RXUs were used in the BSSC3 cabinet instead of or in conjunction with the BSU2/RXU3.

68P02900W21-S 4-30 01 Feb 2007

System Information: BSS Equipment Planning

Hardware

Figure 4-12 Alternative configurations for the BSSC3 cabinet

BSC2 Configuration RXCDR2 Configuration

BSU2

RXU3

RXU3

BSU2

BSU2

BSU2

RXU3

RXU3

Basic BSC2

With expansion shelf, or as 2 separate BSC2s

BSC2 with transcoding

Basic RXCDR2

RXCDR2 with expansion shelf

Backhaul
Table 4-5 and Table 4-6 show how one fr voice call or two hr calls on a single air timeslot are mapped to terrestrial resources at the RTF. Table 4-5 shows how the amount of backhaul configured for each timeslot for a given RTF is based on database parameter settings. The amount of terrestrial backing allocated for an RTF is based on three parameters: hr_enabled (with values 0 = no half rate, 1 = half rate) allow_8k_trau (with values 0 = no 8k TRAU, 1 = 8k TRAU) pkt_radio_type (adds EGPRS support and supersedes allow_32k_trau) Table 4-5 Backhaul configuration based on parameter settings hr_enabled allow_8k_trau 0 = voice only pkt_radio_type 1 = 16k data and voice 2 = 32k data and voice 3 = 64k data and voice

0 1

16k 32k

16k 32k (data uses only 16k) 16k

32k 32k

VersaTRAU Not Supported (allow_ 8k_trau cannot be set to 0 if pkt_radio_ type is 3) VersaTRAU

16k

32k

68P02900W21-S 01 Feb 2007 4-31

Hardware

Chapter 4: AMR and GSM planning

Table 4-6 shows how a fr call or two hr calls are placed onto the terrestrial backhaul. Table 4-6 Call placement on terrestrial backhaul hr_enabled allow_8k_trau 0 = voice only pkt_radio_type 1 = 16k data and voice 2 = 32k data and voice 3 = 64k data and voice

Full rate call on 16k

Full rate call on left most 16k subrate group of the 32k (duplicated on both 16k in the UL)

Full rate call on 16k subrate corresponding to the air timeslot - see Table 4-7.

1 1

0 1

2 half rate calls on separate 16k subrates

Not supported. Half rate with 8K switching assigns the two half rate voice channels to the two bits allocated to an air timeslot. The first half rate voice channel is allocated bit 0. The second half rate voice channel is allocated bit 1. For example, air timeslot B has the first half rate channel assigned to B0 and the second half rate channel assigned to B1 see Table 4-7.

2 half rate calls share one 16K subrate

Table 4-7 Voice call mapping on the backhaul for a 64K RTF VersaTRAU subchannel DS0 Bit 0 DS0 Bit 1 DS0 Bit 2 DS0 Bit 3 DS0 Bit 4 DS0 Bit 5 DS0 Bit 6 DS0 Bit 7

0 1 2

A0 E0

A1 E1

B0 F0

B1 F1

C0 G0

C1 G1

D0 H0

D1 H1

Key: A - H are air timeslots 0 - 7 respectively.

68P02900W21-S 4-32 01 Feb 2007

System Information: BSS Equipment Planning

Hardware

The VersaTRAU Subchannel2 and any higher numbered VersaTRAU Subchannels are always used to carry the multiplexed data for all the PDCHs configured on this carrier. The tables give sample configurations for 16kbit/s, 32kbit/s, and 64kbit/s backhaul. Figure 4-13 and Figure 4-14 apply only to the 16kbit/s backhaul.

When a fr call is connected, the BTS-BSC-RXCDR backhaul path is as shown on the left in Figure 4-13. 16 kbit/s backhaul is required on all the legs. When an AMR hr call is connected which includes the 7.95 kbit/s rate in the Active Codec Set, then a similar backhaul path is needed, as shown on the right in Figure 4-13.
Figure 4-13 AMR backhaul paths
16 kbit/s Ater-CIC connection CIC EGDP / GDP2 16 kbit/s Ater-CIC connection CIC EGDP / GDP2

RXCDR Switch 16 kbit/s Ater allocated BSC Switch

RXCDR Switch 16 kbit/s Ater allocated BSC Switch

16 kbit/s Abis backhaul

16 kbit/s Abis backhaul

BTS Switch CCU CCU

BTS Switch

AMR fr call over air interface

hr call over air interface (w / 7.95 kbit/s)

For a connected AMR hr call not requiring the 7.95 codec rate or a GSM hr call, if ESS mode is enabled in the BSC, but not in the RXCDR, then the backhaul path shown on the left in Figure 4-14 results. For the same call, if ESS mode is enabled in the BSC and the RXCDR then the path showed on the right in Figure 4-14 results.(The idle tone insertion is used internally to fill the 16 kbit/s timeslot.

68P02900W21-S 01 Feb 2007 4-33

Hardware

Chapter 4: AMR and GSM planning

Figure 4-14 hr backhaul paths - ESS mode enabled

16 kbit/s Ater-CIC connection CIC EGDP / GDP2 8 kbit/s Ater-CIC connection CIC EGDP / GDP2 8 kbit/s idle tone RXCDR Switch 16 kbit/s Ater allocated 8 kbit/s idle tone RXCDR Switch 8 kbit/s Ater allocated

BSC Switch 8 kbit/s Abis backhaul

BSC Switch 8 kbit/s Abis backhaul

BTS Switch CCU hr call over air interface CCU

BTS Switch hr call over air interface

68P02900W21-S 4-34 01 Feb 2007

System Information: BSS Equipment Planning

Summary

Summary
AMR transcoding is supported using existing GDPs working in a tandem configuration, the EGDP, or with the GDP2. The former provides a capacity of one half (15 channels of FR/EFR/AMR per card slot) of what is currently supported for the GDP (30 channels FR/EFR/HR per card slot); the latter double the capacity (60 channels of FR/EFR/HR/AMR per card slot). GSM HR transcoding can be supported with the GDP (30 channels) or the GDP2 (60 channels). GDP2s work in the existing RXU shelf, but only at half capacity because there is connectivity of only one E1 per card slot (for most slots). The RXU3 shelf provides 2 x E1 connectivity for all card slots (enhanced capacity mode must be enabled to access the second E1 when GDP2s are used in nonMSI slots). The existing BSU shelf provides two E1 connectors per card slot, for local transcoding configurations. The current BSSC2 cabinet provides for 48 E1 terminations. In order to use the RXU3 shelves to capacity, the BSSC3 cabinet has been developed. This can terminate 76 E1 span lines. The DSW2 can be utilized to reduce backhaul costs between both the BTS and BSC and the BSC and RXCDR, when hr is used. Additionally, within the RXCDR, use of DSW2s/DSWXs can support a greater number of timeslots, which translates to more combinations of card types, particularly MSIs. The proper combination(s) of equipment should be tailored per network.

68P02900W21-S 01 Feb 2007 4-35

Summary

Chapter 4: AMR and GSM planning

68P02900W21-S 4-36 01 Feb 2007

Chapter 5 BTS planning steps and rules

This chapter describes the planning steps and rules for the BTS, including the macrocell and the microcell. The planning steps and rules for the BSC are provided in Chapter 6, BSC planning steps and rules, and that for the remote transcoder (RXCDR) are in Chapter 7, RXCDR planning steps and rules. This chapter details the following sections:
BTS planning overview Macrocell cabinets Microcell enclosures Receive configurations Transmit configurations EGPRS enabled CTU2/CTU2D configuration Antenna configurations Carrier equipment (transceiver unit) Micro base control unit (microBCU) Network interface unit (NIU) and site connection BTS main control unit Cabinet interconnection Battery back-up provisioning External power requirements Network expansion using macro/microcell BTSs Line interface modules (HIM-75, HIM-120) DRI/Combiner operability components

68P02900W21-S 01 Feb 2007 5-1

BTS planning overview

Chapter 5: BTS planning steps and rules

BTS planning overview

Introduction
The following information should be available to plan the equipage of a BTS site:

Number of cells controlled by the site. Number of carriers required. Number of standby carriers per cell. Output power per cell. The required output power must be known to ensure that the selected combining method and antenna configuration provides sufficient output power. Alternatives include changing combiner types or using more than one transmitting antenna. Duplexers can be used to reduce the amount of cabling and the number of antennas.

Antenna configuration for each cell. Cabinet or enclosure types to be used. Future growth potential. The potential future growth of the site must be known to make intelligent trade offs between fewer cabinets/enclosures initially and ease of expansion later.

Existence of equipment shelters at the site. Macro or microcell outdoor equipments should be included in the BTS planning for locations where there are no equipment shelters. Macro/microcell should be included where rooftop mounting or distributed RF coverage is required or where space and access are restricted.

Requirement of battery backup equipment for the outdoor equipment.

Outline of planning steps

Macrocell and microcell BTS sites
The information required for planning a macro/microcell BTS site is as follows:

Determine if the site is indoor or outdoor. Number of macrocell cabinets required, refer to the section Macrocell cabinets. For number of microcell enclosures required, refer to the section Microcell enclosures. For receiver configuration (including planning for Dual Band), refer to the section Receive configurations. For transmit configuration, refer to the section Transmit configurations. For EGPRS enabled CTU2 configuration, refer to the section EGPRS enabled CTU2/CTU2D configuration. For antenna configuration, refer to the section Antenna configurations.

68P02900W21-S 5-2 01 Feb 2007

System Information: BSS Equipment Planning

BTS planning overview

For the amount of carrier equipment required, refer to the section Carrier equipment (transceiver unit). For the number of micro base control units required, refer to the section Micro base control unit (microBCU). For the number of network interface units required, refer to the section Network interface unit (NIU) and site connection. For the number of E1/T1 links required, refer to the section Network interface unit (NIU) and site connection. For the number of main control units required, refer to the section BTS main control unit. For the number of FOX and FMUX boards required, refer to the section Cabinet interconnection. For battery back-up provisioning, refer to the section Battery back-up provisioning. For external power supply requirements, refer to the section External power requirements.

68P02900W21-S 01 Feb 2007 5-3

Macrocell cabinets

Chapter 5: BTS planning steps and rules

Macrocell cabinets
Horizon II macro
Horizon II macro is the next generation replacement for Horizonmacro. Horizon II macro and Horizonmacro are identical in terms of capacity and support the same numbers of carriers, RSLs, and E1s. The Horizon II macro supports equipping of four RSLs per E1, thus reducing the amount of E1 spans needed at a site that needs more than two RSLs. Horizonmacro and M-Cell BTSs currently support two RSLs per E1. A Horizon II macro cabinet (indoor or outdoor) can support 12 carriers when populated fully with six {30828} CTU2s/CTU2Ds, used in double density mode, or can support six carriers when the six {30828} CTU2s/CTU2Ds are used in single density mode. {30828} The mode Capacity can be configured for CTU2D if the CTU2D Capacity feature is unrestricted. Expansion beyond 12 carriers per cabinet needs additional cabinets. The maximum RF carriers supported per Horizon II macro site controller (HIISC) is 24. The Horizon II macro outdoor is a Horizon II macro indoor along with an outdoor enclosure that incorporates heat management. The Horizon II macro outdoor can operate in the temperature range from -40C to 50C.

The Horizon II macro does not support the use of CCBs.

Horizonmacro
A Horizonmacro cabinet (indoor or outdoor) can support six carriers (CTUs). Expansion beyond six carriers needs additional cabinets. The Horizonmacro 12 carrier outdoor is, in effect, an outdoor enclosure which can accommodate either one or two indoor cabinets for 6 or 12 carrier operation.

CCBs cannot be used with the Horizonmacro indoor cabinet if the cabinet is to be installed in the 12 carrier outdoor enclosure. All Horizonmacro cabinets/enclosures incorporate heat management systems. The Horizonmacro outdoor can operate at ambient temperatures up to 50C. The Horizonmacro 12 carrier outdoor can operate at ambient temperatures up to 45C.

68P02900W21-S 5-4 01 Feb 2007

System Information: BSS Equipment Planning

Macrocell cabinets

Horizoncompact and Horizoncompact2

The Horizoncompact and the Horizoncompact2 are an integrated cell site, designed primarily for outdoor operation and consist of:
BTS unit

This is like Horizonmicro / Horizonmicro2 and is a two-carrier cell with combining.

Booster unit

This incorporates two Tx amplifiers, delivering 10 W (nominal) at each antenna. The BTS can be wall-mounted or pole-mounted. The wall can be concrete, brickwork, stonework, dense aggregate block work, or reconstituted stone, with or without rendering. Cooling is by natural convection, and the unit can operate at ambient temperatures up to 50C.

The main difference between the Horizoncompact and the Horizoncompact2 is that the latter can be expanded to support two additional BTSs. In this document, future references to Horizoncompact2 also include Horizoncompact unless specifically stated otherwise.

M-Cell6
The M-Cell6 cabinet can support six carriers (TCUs or CTU2 Adapter in an EGPRS configuration) or 12 carriers (TCUs or CTU2 Adapter in a non-EGPRS configuration). Expansion beyond this needs additional cabinets. Outdoor cell sites are provided with an ancillary cabinet and a side cabinet. The M-Cell6 HMS has the following options:

Fans that circulate ambient air through the cabinet, for both indoor and outdoor units. A heat exchanger for ambient temperatures up to 45C, for outdoor cabinets only. An air conditioning unit for ambient temperatures up to 55C, for outdoor cabinets only.

M-Cell2
The M-Cell2 cabinet can support two carriers (CTU2 Adapter in EGPRS configuration) or four carriers (CTU2 Adapter in non-EGPRS configuration). The M-Cell2 outdoor cabinet accommodates all the elements in an indoor cabinet. It also provides limited accommodation for LTUs and battery backup. A fan within the cabinet provides cooling. Unlike M-Cell6 outdoor cabinets where the antenna terminations are in a side cabinet, M-Cell2 terminations are on the main cabinet. The M-Cell2 HMS has the following options:

Fans that circulate ambient air through the cabinet, for both indoor and outdoor units. A heat exchanger for ambient temperatures up to 45C, for outdoor cabinets only. An air conditioning unit for ambient temperatures up to 55C, for outdoor cabinets only.

68P02900W21-S 01 Feb 2007 5-5

Microcell enclosures

Chapter 5: BTS planning steps and rules

Microcell enclosures
Horizon II mini
Horizon II mini, introduced in GSR7, can satisfy all the current Horizon II macro requirements but also add significant functionality that enables it to be classed as a Mini Macro BTS like the M-Cell2 BTS. The architecture is based on the Horizon II macro architecture and effectively Horizon II mini operates like a Horizon II macro cabinet. The Mini BTS can be expanded from the Horizon II macro, Horizonmacro, and M-Cell6. The Horizon II mini enclosure can house two {30828} CTU2s/CTU2Ds that can be configured in both single density and double density mode. {30828} The mode Capacity can be configured for CTU2D if the CTU2D Capacity feature is unrestricted. As a result, the carrier capacity is 1-4 carriers, for a maximum network configuration of 16 to 24 carriers per site dependent on cabinet capacity. Horizon II mini is available as indoor and outdoor variant, and can be mounted on wall, floor, or rack. The wall may be concrete, brickwork, stonework, dense aggregate block work, or reconstituted stone, with or without rendering. Software parameters are added to distinguish Horizon II mini cabinets to allow easier configuration. The Horizon II mini parameters allow for:

Only one BTP to be equipped to a Horizon II mini master cabinet. A maximum of two physical radios to be equipped to a Horizon II mini cabinet.

Due to the compact and low-cost nature of this product, there is no accommodation for redundancy hardware. Horizon II mini can only be equipped with {30828} CTU2/CTU2D radios and, therefore, supports EGPRS.

The Horizon II mini uses E1 links for both TRAU and RSL and can be expanded from a Horizonmacro family BTS or be used as a network of Horizon II minis.

SDH feature
Horizon II mini also supports an auxiliary power supply or an optional third party SDH module requiring a 48 V dc power supply up to a maximum dissipation of 60W. When the outdoor enclosure is configured with the SDH module, it can be a standalone only BTS.

The outdoor enclosure configuration cannot be expanded in a network, as the communications power card, to supply -48 V dc, should be inserted in the Site I/O slot.

68P02900W21-S 5-6 01 Feb 2007

System Information: BSS Equipment Planning

Microcell enclosures

Horizonmicro and Horizonmicro2

The Horizonmicro and the Horizonmicro2 are an integrated cell site, designed primarily for outdoor operation and consist of a single small two-carrier BTS unit. The Horizonmicro and Horizonmicro2 can be wall or pole-mounted. The wall may be concrete, brickwork, stonework, dense aggregate block work, or reconstituted stone, with or without rendering. Cooling is by natural convection, and the unit can operate at ambient temperatures up to 50C.

The main difference between the Horizonmicro and the Horizonmicro2 is that the latter can be expanded to support two additional BTSs. In this document, future references to Horizonmicro2 also include Horizonmicro unless specifically stated otherwise.

Horizon II micro
The Horizon II micro is an integrated cell site, designed for indoor, and outdoor microcellular applications and consists of a single small two carrier BTS ({30828} CTU2/CTU2D) unit. It can be configured for two carriers in double density mode for GSM/GPRS or one carrier in Single Density mode for EGPRS. If ITS is unrestricted and enabled, double density mode can be used for EGPRS. {30828} The mode Capacity can be configured for CTU2D if the CTU2D Capacity feature is unrestricted. It can be seen as a replacement to the Horizonmicro2 where it deems obsolete (because of an obsolete chip set or where features no longer can be supported) and is to target applications in both 900 MHz and 1800 MHz bands. The Horizon II micro can be wall or pole-mounted. The wall may be concrete, brickwork, stonework, dense aggregate block work, or reconstituted stone, with or without rendering. Cooling is by natural convection or by an internal fan. The unit can operate at ambient temperatures up to 50C.

68P02900W21-S 01 Feb 2007 5-7

Receive configurations

Chapter 5: BTS planning steps and rules

Receive configurations
Introduction
The receiver equipment provides the termination and distribution of the received signals from the Rx antennas. Receiver equipment is required for each Rx signal in every cabinet or enclosure in which it is used. Each Rx antenna must terminate on a single cabinet or enclosure. If the signal is to go to multiple cabinets, it is distributed from the first cabinet.

Horizonmicro2 and Horizon II micro are two-carriers only, combined to a single antenna. Horizoncompact2 is two-carriers only, with two antennas. Two versions of the Horizonmicro2 and Horizoncompact2 BTSs are available. One version can operate on GSM900 frequencies and the other can operate on DCS1800 frequencies.

Planning considerations
The factors affecting planning for GSM900 and DCS1800 BTSs are provided in this section.

GSM900
The following factors should be considered when planning the GSM900 receive equipment:

Horizon II macro and Horizon II mini BTSs need one 900 MHz SURF2 for each cabinet. Currently, for Horizon II macro only, a second (optional) 900 MHz SURF2 can be installed to provide 4-branch diversity.

For Horizon II macro only, an optional SURF2 dual band adaptor allows a 900 MHz SURF2 and an 1800 MHz SURFs to be installed in the same cabinet, thus providing dual band capability. Receive antennas can be extended across Horizon II macro/Horizon II mini cabinets by using the 900 SURF2 expansion ports to feed a SURF2 in another cabinet.

Horizonmacro BTSs need one 900 MHz SURF for each cabinet. This has dual band (900/1800 MHz) capability. Receive antennas can be extended across Horizonmacro cabinets by using the 900 SURF expansion ports to feed a SURF in another cabinet.

M-Cell2 and M-Cell6 BTSs need one DLNB for each sector. Receive antennas can be extended across M-Cell6 cabinets by using the IADU expansion ports to feed an IADU in another cabinet.

68P02900W21-S 5-8 01 Feb 2007

System Information: BSS Equipment Planning

Receive configurations

DCS1800
The following factors should be considered when planning the DCS1800 receive equipment:

Horizon II macro and Horizon II mini BTSs need one 1800 MHz SURF2 for each cabinet. Currently, the SURF2 is not dual band and only supports 900 MHz/1800 MHz capability in separate cabinets. For Horizon II macro only, a second (optional) 1800 MHz SURF2 can be installed to provide 4-branch diversity. Receive antennas can be extended across Horizon II macro/Horizon II mini cabinets by using the 1800 SURF2 expansion ports to feed a SURF2 in another cabinet. Horizonmacro BTSs need one 1800 MHz SURF for each cabinet. Receive antennas can be extended across Horizonmacro cabinets by using the 1800 SURF expansion ports to feed a SURF in another cabinet.

Two types of 1800 SURF are available: One is 1800 MHz single band and the other is 1800 MHz/900 MHz dual band.

M-Cell2 and M-Cell6 BTSs need one LNA for each sector. Receive antennas can be extended across M-Cell6 cabinets by using the LNA expansion ports to feed an LNA in another cabinet.

DCS1800 and GSM900

It should be considered that Horizon II macro Dual Band capable cabinets need one 1800 MHz SURF2, one 900 MHz SURF2 and a Dual Band Adaptor, when planning dual band (that is, support for both DCS1800 and GSM900 within a single cabinet) receive equipment.

The maximum number of transceiver units for a dual band cabinet configuration is 3 {30828} CTU2s/CTU2Ds per band. A third power supply is required. The rear SURF2 controls {30828} CTU2/CTU2D radio slots 3, 4, and 5. The front SURF2 controls {30828} CTU2/CTU2D radio slots 0, 1, and 2. Contact your Motorola Local Office for more information. Refer to Chapter 12, Standard BSS and Horizon BTS configurations, for Dual Band cabinet physical configuration.

Receiver planning actions

The following planning actions are required:

Determine the number of cells. Determine the number of cells which have {30828} CTU2s/CTU2Ds/CTUs/TCUs in more than one cabinet. Determine the number of Rx antennas per cell supported in each cabinet. Determine the type and quantity of receive equipment required.

68P02900W21-S 01 Feb 2007 5-9

Receive configurations

Chapter 5: BTS planning steps and rules

When using CTU2s in double density mode, both carriers should be in the same sector and can be individually reset. Dropping one carrier does not affect the second CTU2 carrier.

68P02900W21-S 5-10 01 Feb 2007

System Information: BSS Equipment Planning

Transmit configurations

Transmit configurations
Introduction
The transmit equipment provides bandpass filtering and signal combining for the BTS cabinets. The {30828} CTU2/CTU2D used in Horizon II macro can be configured to use a single high power carrier (single density mode) or two lower power carriers (double density mode). For M-Cell2 and M-Cell6 cabinets, a TxBPF is required for each antenna.

Horizonmicro2 and Horizon II micro are two-carrier only, combined to a single antenna. Horizoncompact2 is two-carrier only, with two antennas.

Planning considerations
The transmit configurations available for Horizon II macro, Horizon II mini, Horizonmacro, M-Cell2 and M-Cell6 BTSs are listed in Table 5-1.
Table 5-1 Transmit configurations Number of Carriers BTS Types Cabinet Transmit Configurations Wide Band Combining Cabinet Transmit Configurations Cavity Combining

1 1 1 or 2 1 or 2 2 2 3 3 3 or 4 3 or 4

M-Cell2 and M-Cell6 Horizonmacro Horizon II macro Horizon II mini M-Cell2 and M-Cell6 Horizonmacro M-Cell6 Horizonmacro Horizon II macro Horizon II mini

1 TxBPF 1 DCF or 1 TDF 1 DUP 2 DUP (BowtieCombiner) 1 HCOMB + 1 TxBPF 1 DCF 2 HCOMB + 1 TxBPF 2 DCF or 1 DDF DUP + 1 HCU or 2 DUP and Air 2 DUP (BowtieCombiner) and Air

Not available Not available Not available Not available 1 CCB output 1 CCB output 1 CCB output 1 CCB output CCBs not supported CCBs not supported
Continued

68P02900W21-S 01 Feb 2007 5-11

Transmit configurations

Chapter 5: BTS planning steps and rules

Table 5-1 Transmit configurations (Continued) Number of Carriers BTS Types Cabinet Transmit Configurations Wide Band Combining Cabinet Transmit Configurations Cavity Combining

4 4 5 5 6 6 6

M-Cell6 Horizonmacro M-Cell6 Horizonmacro M-Cell6 Horizonmacro Horizon II macro

2 HCOMB + 1 TxBPF 1 DDF + 1 HCU 3 HCOMB + 1 TxBPF 2 DDF and Air 4 HCOMB + 1 TxBPF 2 DDF and Air 1 DUP + 1 DHU or 2 DUP + 1 HCU and Air

1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension CCBs not supported

A CCB output includes a TxBPF, but a CCB extension does not include it. EGPRS supports single density CTU2 configuration only. The Tx configuration options apply only for the Horizonmacro and Horizon II macro cases as 1 carrier per CTU2 Radio.

Transmit planning actions

Determine the transmit equipment required.

68P02900W21-S 5-12 01 Feb 2007

System Information: BSS Equipment Planning

EGPRS enabled CTU2/CTU2D configuration

EGPRS enabled CTU2/CTU2D configuration

{30828}

EGPRS enabled CTU2/CTU2D configuration limitations

{30828} EGPRS is a restricted feature. This configuration is supported only when this feature is unrestricted. If ITS feature is unrestricted and enabled, the EGPRS can be configured on double density CTU2. The CTU2 radio is supported in the Horizon II macro and Horizonmacro BTS cabinet platforms. In addition, the CTU2 radio is supported in the M-Cell6 and M-Cell2 cabinet platforms when the CTU2 Adapter is used. {30828} CTU2D is supported on H2Macro, H2Mini, and H2Micro Sites only. When the master cabinets are H2Macro and H2Mini, the extension H2 cabinets support CTU2D; legacy Mcell and H1 extension cabinets do not support CTU2D and remain OOS.

The CTU2-D is not currently part of GSR9, and will be delivered in a separate software load.

EGPRS general configuration

The EGPRS feature needs additional backhaul to provision EGPRS carriers. The additional backhaul is either seven DS0s to implement EGPRS on a BCCH carrier or eight DS0s to implement EGPRS on a nonBCCH carrier, if VersaTRAU feature is restricted. If VersaTRAU feature is unrestricted, the backhaul for an EGPRS carrier can be configured using the rtf_ds0_count parameter. If VersaTRAU is restricted, the maximum number of EGPRS carriers that can be equipped for a threesector site is 21. The total number of E1s available at a Horizonmacro or Horizon II macro site is 6. Some numbers of these DS0s are needed for RSLs to the BSC (up to 6 with MCUF, and H2 site controller). The rest of the DS0s are available for TRAU. An entire RTF must be configured to the same physical E1. This allows configuration of three non-BCCHs. EGPRS RTFs on each E1 (using 24 DS0s) for a total of 18 EGPRS non-BCCH carriers. The remaining 7 DS0s can be used for BCCH RTFs and RSLs. Therefore, the worst-case configuration when every possible timeslot is configured as an EGPRS carrier in a three-sector site is 21 carriers:

18 (3x6) non-BCCH (with 8 air timeslots on each RTF) carriers at a site. Three BCCH carriers (with 7 air timeslots on each RTF). The remaining DS0s are available for use as RSLs.

If VersaTRAU is unrestricted, the maximum number of EGPRS carriers for the same configuration can be up to 24. If the recommended non-aggressive backhaul of five DS0s per EGPRS carrier is used, six EGPRS carriers (using 30 DS0s) can be configured on each E1. This would need four E1s for the 24 EGPRS carriers leaving the remaining four DS0s available for RSLs.

68P02900W21-S 01 Feb 2007 5-13

EGPRS enabled CTU2/CTU2D configuration

Chapter 5: BTS planning steps and rules

BaseBand Hopping (BBH)

There are several restrictions for an EGPRS enabled {30828} CTU2/CTU2D. Baseband hopping (BBH) is only allowed with other EGPRS enabled CTU2 radios in the same hopping group. Table 5-2 and Table 5-3 show the restrictions for the Horizon II macro Site Controller and the Horizonmacro Site Controller respectively. In ITS mode, EGPRS double density carrier A and its pair are excluded for BBH. {30828} For BBH restriction aspect, CTU2D PWR mode and ITS mode are identical. In CTU2D CAP mode, the BBH restrict ion on carrier A is the same as PWR mode, and GMSK carrier B supports for BBH. In CTU2D ASYM mode, all the EGPRS carriers (in SD/DD/Capacity mode) within the site are removed from BBH system.

Table 5-2 indicates that BBH is not permitted with EDGE enabled CTU2s when Horizonmacro is the Master Site Controller. BBH is only permitted with EDGE enabled CTU2s when they are controlled by the Horizon II macro Site controller as Master. Table 5-2 BBH capability for Horizon II macro Site Controller CTU2 (SD EGPRS) CTU2 (SD EGPRS) CTU2 (DD GSM) CTU2 (SD GSM) CTU (SD GSM) CTU2 (DD GSM) CTU2 (SD GSM) CTU (SD GSM)

4 6 6 6

6 4 4 4

6 4 4 4

6 4 4 4

Table 5-3 BBH capability for Horizonmacro Site Controller CTU2 (SD EGPRS) CTU2 (SD EGPRS) CTU2 (DD GSM) CTU2 (SD GSM) CTU (SD GSM) CTU2 (DD GSM) CTU2 (SD GSM) CTU (SD GSM)

6 6 6 6

6 6 6 6

6 6 4 4

6 6 4 4

68P02900W21-S 5-14 01 Feb 2007

System Information: BSS Equipment Planning

EGPRS enabled CTU2/CTU2D configuration

Broadcast Control CHannel (BCCH) RTF configuration

The Broadcast control channel (BCCH) Radio Transceiver Function (RTF) should be configured as a 64K carrier. For EGPRS, the only radio that supports 64K is the {30828} CTU2/CTU2D. It is not necessary that the {30828} CTU2/CTU2D used for the BCCH RTF is EGPRS enabled.

68P02900W21-S 01 Feb 2007 5-15

Antenna configurations

Chapter 5: BTS planning steps and rules

Antenna configurations
Planning considerations
The following factors should be considered when planning the antenna configuration:

Omni, one sector, two sector, three sector (either 120 or 60), or six sector (two cabinets are needed). Share existing antenna(s) or new/separate antenna(s). Diversity considerations. Antenna type:
o o o o o

Gain Size Bandwidth Appearance Mounting

Antenna planning actions

Determine the antenna configuration.

68P02900W21-S 5-16 01 Feb 2007

System Information: BSS Equipment Planning

Carrier equipment (transceiver unit)

Carrier equipment (transceiver unit)

Introduction
The transceiver unit for Horizon II macro and Horizon II mini is the {30828} CTU2/CTU2D. This can be configured to operate in single density (single carrier) or double density (2 carrier) mode. The CTU2 can also be used as a CTU replacement (subject to restrictions) in a Horizonmacro cabinet, but NOT an outdoor cabinet.

CCBs are not supported by the {30828} CTU2/CTU2D (refer to Chapter 1 for more information of CTU2D configuration). The transceiver unit for Horizonmacro is a CTU. This is eventually phased out and replaced by the CTU2, as used in the Horizon II macro. For rules relating to replacement of a CTU with a CTU2, contact your Motorola Local Office. The transceiver unit for Horizonmicro2 and Horizoncompact2 is a DTRX. The transceiver unit for M-Cell2 and M-Cell6 is either a TCU or a TCU-B. The TCU-B is an enhancement of the original TCU and can be used as a direct replacement for the TCU. However, TCU-B has the following differences:

The TCU-B only supports GSM/EGSM900. The TCU-B cannot be used as a SCU (in pre M-Cell equipment).

References to TCU in the text include TCU-B, except where stated otherwise. AMR and GSM half rate are supported on all transceiver equipment described here, except for the DTRX.

Restrictions in CTU2s usage in Horizonmacro BTSs

The following restrictions apply when CTU2s are used to replace CTUs in Horizonmacro BTSs:

CTU2s cannot be used in Horizonmacro outdoor BTSs. CTU2s cannot be used in Horizonmacro indoor BTSs that are powered from 110 V ac. BBH is only supported in single density mode when CTU2s are used in Horizonmacro indoor BTSs. CCBs are not supported when CTU2s are used in Horizonmacro indoor BTSs. RF power output from the CTU2s is reduced. Fully populated Horizonmacro cabinets that contain two or more CTU2s need three PSUs. PSU redundancy is not available in these configurations.

68P02900W21-S 01 Feb 2007 5-17

Carrier equipment (transceiver unit)

Chapter 5: BTS planning steps and rules

CTU/CTU2 power supply considerations

Under normal circumstances, the Horizonmacro only needs two power supply modules (PSMs) to power six CTUs, and the third PSM slot can be used either for a redundant PSM or for an optional hold-up battery module (in ac-powered systems). These power supply requirements change if CTU2s are used in the Horizonmacro cabinet. Depending on the number of CTU2s used, it can be necessary to install a third PSM, thus losing the internal battery backup facility. In cases where battery backup is required, an external battery backup unit (BBS) needs to be added. In addition, where a third (redundant) PSM is already installed, redundancy is lost. Table 5-4 lists the CTU/CTU2 combinations and power supply requirements in Horizonmacro and Horizon II macro cabinets. This table applied to both GPRS and the EGPRS feature overlay.

Table 5-4 does not include Horizon II mini, as Horizon II mini needs only one power supply as minimum/maximum. Table 5-4 CTU/CTU2 power requirements Horizonmacro Number of CTUs Number of CTU2s Number of power supplies required Horizon II macro Number of CTU2s Number of power supplies required

6 5 4 3 2 1 0 4 3 2 1 0 3 2 1 0

0 1 1 1 1 1 1 2 2 2 2 2 3 3 3 3

2 3 2 2 2 1 1 3 2 2 2 2 3 3 2 2

6 5 4 3 2 1

3 3 3 2 2 1

Continued

68P02900W21-S 5-18 01 Feb 2007

System Information: BSS Equipment Planning

Carrier equipment (transceiver unit)

Table 5-4 CTU/CTU2 power requirements (Continued) Horizonmacro Number of CTUs Number of CTU2s Number of power supplies required Horizon II macro Number of CTU2s Number of power supplies required

2 1 0 1 0 0

4 4 4 5 5 6

3 3 2 3 3 3

The Horizon II macro always has a spare fourth power supply slot available for either a redundant power supply or for a hold-up battery module (in ac-powered cabinets).
Table 5-5 lists the CTU/CTU2 combinations and power supply requirements in M-Cell6 and M-Cell2 cabinets. This table is independent of the CTU2 operating mode or feature overlay. This table assumes that slots that do not use CTU2 adapters are populated with TCUs. Table 5-5 CTU/CTU2 power requirements for M-Cell cabinets Number of CTU2 Adapters Number of power supplies required

M-Cell6 AC Indoor: 16 M-Cell6 AC Outdoor: 14 56 M-Cell6 DC Indoor: 14 56 M-Cell2 AC Indoor and M-Cell2 AC Outdoor: 1 2 1 1 (add one more for redundancy) 2 2 (add one more for redundancy) 3 4 5

68P02900W21-S 01 Feb 2007 5-19

Carrier equipment (transceiver unit)

Chapter 5: BTS planning steps and rules

Planning considerations
The following factors should be considered when planning carrier equipment:

The number of carriers based on traffic considerations. Plan for future growth. Allowance must be made for BCCH and SDCCH control channels. Information about how to determine the number of control channels required is in the Control channel calculations section in Chapter 3. One transceiver unit is required to provide each RF carrier. However, with the introduction of the {30828} CTU2/CTU2D this is no longer true. The {30828} CTU2/CTU2D is capable of single and double density operation for GSM/GPRS; one {30828} CTU2/CTU2D can support one RF carrier or be configured to support two RF carriers. The exception to this is for EGPRS. An EGPRS enabled CTU2 can only be configured in single density mode (that is, one CTU2 per carrier). If ITS feature is unrestricted and enabled, an EGPRS enabled CTU2 can also be configured in double density mode but with timeslot blanking on the paired carrier. {30828} With the introduction of CTU2D more modes, that is, CAP and ASYM, can support EGPRS with double density without timeslot blanking. Include redundancy requirements. Redundancy can be achieved by installing excess capacity in the form of additional transceiver units. Plan the number of power supplies required in accordance with the number of transceivers required.

Transceiver planning actions

Determine the number of transceivers required and the number of power supplies required to power the transceivers.

68P02900W21-S 5-20 01 Feb 2007

System Information: BSS Equipment Planning

Micro base control unit (microBCU)

Micro base control unit (microBCU)

Introduction
The microBCU (or BCU) is the macro/microcell implementation of a BTS site controller.

Planning considerations
The following factors should be considered when planning the BCU complement:

Horizon II macro/Horizon II mini The Horizon II macro/Horizon II mini is like the Horizonmacro in that it has a built-in digital module shelf. However, unlike Horizonmacro, the NIU is integrated on the HIISC (the equivalent of the Horizonmacro MCUF) and external FMUXs and BPSMs are not required. The digital module shelf can be equipped for redundancy and/or additional E1/T1 link capacity with the addition of a redundant HIISC.

Horizonmacro Each Horizonmacro cabinet has a built-in digital module shelf. This provides the Horizonmacro equivalent of M-Cell6 microBCU cage functionality. The digital module shelf can be equipped for redundancy and/or additional E1/T1 link capacity with the addition of a redundant MCUF, NIU, FMUX, and BPSM.

M-Cell6 Each M-Cell6 cabinet needs one microBCU cage. Two microBCU cages can be equipped for redundancy and/or additional E1/T1 link capacity with the addition of a redundant MCU, NIU, and FOX/FMUX.

M-Cell2 The first M-Cell2 cabinet needs one microBCU2 cage. Two microBCU2 cages can be equipped for redundancy and/or additional E1/T1 link capacity. Additional cabinets do not need microBCU2 cages.

MicroBCU planning actions

For M-Cell equipment, determine the number of microBCUs required.

68P02900W21-S 01 Feb 2007 5-21

Network interface unit (NIU) and site connection

Chapter 5: BTS planning steps and rules

Network interface unit (NIU) and site connection

Introduction
The NIU provides the interface for the Horizon II macro, Horizonmacro or M-Cell2/6 BTS to the terrestrial network.

M-Cellcity and M-Cellcity+ are fitted with a single NIU-m only. The equivalent modules in Horizoncompact2 and Horizonmicro2 are RHINO/DINO.

Planning considerations
Depending on the BTS equipment installed, the following factors should be considered when planning the NIU complement:

Horizon II macro/Horizon II mini

Both Horizon II macro and Horizon II mini use the Horizon II site controller (HIISC). NIU functionality is integrated into the HIISC. From the functional point of view, the Integrated NIU functions in the same way as the standalone NIU with the exception that support for four RSL links per E1 and a maximum of six E1s is now supported in Horizon II macro and Horizon II mini. A minimum of one HIISC (with integrated NIU functionality) is required in the master cabinet for each Horizon II macro BTS site. Horizon II mini does not support hardware redundancy. For a Horizon II macro master cabinet, redundancy for the NIU functionality depends on a redundant HIISC. If a redundant HIISC is installed, a redundant site expansion board is also required. Slave Horizon II macro cabinets connected to the master cabinet also need redundant site expansion boards and redundant XMUXs.

For Horizon II macro only: The integrated NIU within the redundant HIISC has connectivity to all the E1 links for that site through the use of relays and switches. The redundant HIISC can be switched automatically to become the main HIISC, taking over all duties of the main HIISC (including controlling all E1 links at that site) through a BTS reset.

68P02900W21-S 5-22 01 Feb 2007

System Information: BSS Equipment Planning

Network interface unit (NIU) and site connection

Horizonmacro and M-Cell

The first NIU in a digital module shelf (Horizonmacro) or microBCU cage (M-Cell6) can interface two E1/T1 links. The second NIU in a digital module shelf or microBCU cage can interface one E1/T1 link. Each E1/T1 link provides 31 (E1) or 24 (T1) usable 64 kbit/s links. A minimum of one NIU is required for each BTS site. One NIU can support two MCUFs (Horizonmacro) or two MCUs (M-Cell6). The NIU feeds the active MCUF/MCU. To calculate the number of 64 kbit/s links required, view the site as consisting of its own equipment, and that of other sites, which are connected to it by the drop and insert (daisy chain) method.
o o

Two 64 kbit/s links are required for each active transceiver. A 64 kbit/s link is required for every RSL (LAPD signaling channel) to the site. In the drop and insert (daisy chain) configuration, every site needs its own 64 kbit/s link for signaling.

Redundancy for the NIU module depends on the number of redundant E1/T1 links to the site. Plan for a maximum of two NIUs per digital module shelf or microBCU cage (three E1or T1 links). Plan for a maximum of one NIU per microBCU2 cage for M-Cell2 cabinets (two E1 or T1 links).

The minimum number of NIUs and microBCU cages required for a given number of E1/T1 links to a single M-Cell cabinet is shown in Table 5-6.
Table 5-6 Site connection requirements for M-Cell2 and M-Cell6 Number of E1/T1 links Minimum number of NIU required Number of BCU cages required NOTEs

1 2 3 3 4 5 6

1 1 2 2 2 3 4

1 1 1 2 2 2 2

M-Cell2 and M-Cell6 M-Cell2 and M-Cell6 M-Cell6 M-Cell2 and M-Cell6 M-Cell2 and M-Cell6 M-Cell6 only M-Cell6 only

Only one digital module shelf is installed in the Horizon II macro and Horizonmacro.

68P02900W21-S 01 Feb 2007 5-23

Network interface unit (NIU) and site connection

Chapter 5: BTS planning steps and rules

E1 link interfaces
For driving a balanced 120 ohm 3 V (peak pulse) line, use a BIB. For driving a single ended 75 ohm 2.37 V (peak pulse) line, use a T43.

T1 link interfaces
For driving a balanced 110 ohm 3 V (peak pulse) line, use a BIB.

NIU planning actions

Determine the number of NIUs required.

68P02900W21-S 5-24 01 Feb 2007

System Information: BSS Equipment Planning

BTS main control unit

BTS main control unit

Introduction
The main control unit provides the main site control functions for a BTS. The main control unit used depends on the BTS equipment:

Both Horizon II macro and Horizon II mini use a Horizon II macro site controller (HIISC) with triple XMUX. Horizonmacro uses a main control unit with dual FMUX (MCUF). M-Cell6 and M-Cell2 use a main control unit (MCU).

The HIISC can only be used in Horizon II macro. The MCUF is backward compatible with the MCU and can be used in M-Cell6 and M-Cell2 BTSs. Horizon II mini is a new small macro BTS and the HIISC used within can support a maximum of 24 RF carriers across the sites. The HIISC used in Horizon II macro can also support 24 RF carriers.

Planning considerations
Horizon II macro
The following factors should be considered when planning the HIISC complement for a Horizon II macro site:

Only the master Horizon II macro cabinet needs a HIISC. For redundancy, add another HIISC in the digital module shelf of the master cabinet. This also provides redundancy for the NIU and XMUX as well, since they are integrated in the HIISC.

This redundancy configuration also needs a redundant site expansion board in all Horizon II macro cabinets at sites where more than one cabinet is installed.

Horizon II mini

Only the master Horizon II mini cabinet needs a HIISC. The HIISC used can support a maximum of 24 RF carriers across the sites. There is no accommodation for redundancy in this BTS.

68P02900W21-S 01 Feb 2007 5-25

BTS main control unit

Chapter 5: BTS planning steps and rules

Horizonmacro
The following factors should be considered when planning the MCUF complement for a Horizonmacro site:

Only the master cabinet needs a MCUF. An optional 20 MB PCMCIA memory card is installed for non-volatile code storage. For redundancy, add another MCUF in the digital module shelf of the master cabinet.

M-Cell6 and M-Cell2

The following factors should be considered when planning the MCU complement for an M-Cell6 or M-Cell2 site:

Only the master cabinet needs a MCU. An optional 20 MB PCMCIA memory card is installed for non-volatile code storage. For redundancy, add another mBCU cage and MCU in the master cabinet.

Planning considerations Horizon II macro/Horizon II mini as expansion cabinet

This information describes the factors that require to be taken into account if Horizon II macro cabinets are used to expand existing Horizonmacro or M-Cell6 sites.

Horizon II macro slave BTS planning considerations

A XMUX is required instead of a HIISC in the slave cabinet. A site expansion board is required. If redundancy is required, a redundant XMUX and redundant site expansion board must be installed.

Horizon II mini slave BTS planning considerations

A XMUX is required instead of a HIISC in the slave cabinet. A site expansion board is required. Horizon II mini does not support hardware redundancy.

Horizonmacro master BTS planning considerations

Only the master cabinet needs an MCUF. A 20 MB PCMCIA memory card running CSFP must be installed in the MCUF to accommodate the use of the CTU2 transceiver from a code storage standpoint. If the site is equipped with a redundant MCUF, the PCMCIA is also mandatory for the redundant MCUF.

68P02900W21-S 5-26 01 Feb 2007

System Information: BSS Equipment Planning

BTS main control unit

M-Cell6 master BTS planning considerations

Due to expansion limitations, M-Cell2 BTSs cannot be used with Horizon II macro (or Horizonmacro) cabinets.

Only the master cabinet needs an MCU. A 20 MB PCMCIA memory card running CSFP must be installed in the MCU to accommodate the use of the CTU2 transceiver from a code storage standpoint. If the site is equipped with a redundant MCU, the PCMCIA is also mandatory for the redundant MCU. The master cabinet must have a FMUX installed to communicate with the Horizon II macro BTS.

Planning actions
Horizon II macro/Horizon II mini
Determine the number of HIISCs required.

Horizonmacro
Determine the number and configuration of MCUFs required.

M-Cell6 and M-Cell2

Determine the number and configuration of MCUs required.

68P02900W21-S 01 Feb 2007 5-27

Cabinet interconnection

Chapter 5: BTS planning steps and rules

Cabinet interconnection
Introduction
Horizon II macro
The XMUX multiplexes and demultiplexes full duplex transceiver links between a site expansion board and up to six {30828} CTU2s/CTU2Ds in a Horizon II macro expansion cabinet.

Horizon II mini
The XMUX multiplexes and demultiplexes full duplex transceiver links between a site expansion board and two {30828} CTU2s/CTU2Ds in a Horizon II mini expansion cabinet.

Horizon II micro
Horizon II micro supports up to three cabinets. It can be connected to either another Horizon II micro or any legacy macro or mini product through an expansion board like the Horizon II macro Site I/O.

Horizonmacro
The FMUX multiplexes and demultiplexes full duplex transceiver links between a MCUF and up to six CTUs.

M-Cell6 and M-Cell2

The FOX provides the bidirectional electrical to optical interface between an MCU and FMUX and up to six TCUs. The FMUX multiplexes and demultiplexes electrical connections for up to six TCUs or CTU2 Adapters onto a single fiber optic connection operating at the rate of 16.384 Mbit/s.

Planning considerations
Horizon II macro
The following factors should be considered when planning the XMUX complement:

A XMUX is required in each Horizon II macro expansion cabinet. The master Horizon II macro cabinet does not need a XMUX as a triple XMUX is integrated on the HIISC. There is no support for hardware redundancy in Horizon II mini. A site expansion board (unique to Horizon II macro) is required for the master and every expansion cabinet in the Horizon II macro BTS site when expansion is required (see Table 5-7). Redundancy needs duplication of the HIISC in the master cabinet and all XMUXs and site expansion boards.

68P02900W21-S 5-28 01 Feb 2007

System Information: BSS Equipment Planning

Cabinet interconnection

Table 5-7 Horizon II macro XMUX expansion requirements Cabinet Master Expansion 1 Expansion 2 Expansion 3

1 (master) 2

None 1 site expansion board only 1 site expansion board only 1 site expansion board only 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board

Horizon II mini
The following factors should be considered when planning the XMUX complement:

A XMUX is required in each Horizon II mini expansion cabinet. The master Horizon II mini cabinet does not need a XMUX, as a triple XMUX is integrated on the HIISC. A site expansion board (unique to Horizon II macro and Horizon II mini) is required for the master and every expansion cabinet in the Horizon II macro BTS site when expansion is required (see Table 5-8 to Table 5-10).

Table 5-8 Horizon II mini only network XMUX expansion requirements Cabinet Master Expansion 1 Expansion 2 Expansion 3

1 (master) 2

None 1 site expansion board only 1 site expansion board only 1 site expansion board only 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board

Table 5-9 Horizon II macro as master - Horizon II mini as expansion XMUX requirements Cabinet Master Expansion 1 Expansion 2 Expansion 3

1 (master) 2

None 1 site expansion board only 1 XMUX + 1 site expansion board

Continued

68P02900W21-S 01 Feb 2007 5-29

Cabinet interconnection

Chapter 5: BTS planning steps and rules

Table 5-9 Horizon II macro as master - Horizon II mini as expansion XMUX requirements (Continued) Cabinet Master Expansion 1 Expansion 2 Expansion 3

1 site expansion board only 1 site expansion board only

1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board

1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board

Table 5-10 Horizon II macro as master - Horizon II mini as expansion XMUX requirements Cabinet Master Expansion 1 Expansion 2 Expansion 3

1 (master) 2

None None 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board 1 XMUX + 1 site expansion board

None

1 FMUX

The Horizon II mini is a micro family BTS and the HIISC used has RF limitations of 24 carriers per site in a Horizon II mini network.

Horizonmacro
The following factors should be considered when planning the FMUX complement:

An FMUX is not required in the master cabinet for two or three cabinet configurations (see Table 5-11). A fourth Horizonmacro cabinet needs one FMUX plus one FMUX in the master cabinet (see Table 5-11). Redundancy needs duplication of an FMUX and associated MCUF.

Table 5-11 Horizonmacro FMUX expansion requirements Cabinet Master Expansion 1 Expansion 2 Expansion 3

1 (master) 2 3 4

None None None 1 1 1 1 1 1 1

68P02900W21-S 5-30 01 Feb 2007

System Information: BSS Equipment Planning

Cabinet interconnection

M-Cell6 and M-Cell2

The following factors should be considered when planning the FOX/FMUX complement:

A FOX board is required for more than two TCUs. Each additional M-Cell6 cabinet needs a minimum of one FOX and FMUX plus one FMUX in the first cabinet. Redundancy needs duplication of all FOX and FMUX boards and associated MCU and microBCU cages.

Planning considerations - Horizon II macro as master cabinet

Due to expansion limitations, M-Cell2 BTSs cannot be used with Horizon II macro cabinets. The following factors should be considered while planning to use a Horizon II macro as a master cabinet with Horizonmacro or M-Cell6 expansion cabinets:

A site expansion board is required in the Horizon II macro master cabinet. A XMUX is not required in the Horizon II macro master cabinet. Each Horizonmacro or M-Cell6 slave cabinet must contain a FMUX (replaces the MCUF/MCU). For redundancy, the master Horizon II macro cabinet needs an additional HIISC and site expansion board. Each Horizonmacro slave cabinet needs an additional FMUX, and each M-Cell6 slave cabinet needs an additional FMUX and FOX.

Planning considerations - Horizon II mini as master cabinet

Horizon II mini as a Master cabinet and Macro family BTS as expansions are considered a non-Motorola approved configuration. Horizon II mini outdoor variant needs a -230 V dc supply.

XMUX/FMUX/FOX planning actions

Horizon II macro
Determine the number of XMUXs required (applies to expansion cabinets only).

68P02900W21-S 01 Feb 2007 5-31

Cabinet interconnection

Chapter 5: BTS planning steps and rules

Horizonmacro
Determine the number of FMUXs required.

M-Cell6 and M-Cell2

Determine the number of FOX/FMUXs required.

M-Cell2 BTSs are not supported as an expansion to Horizon II macro or Horizonmacro cabinets.

Site expansion board planning actions (Horizon II macro only)

If more than one cabinet is to be used at a site, determine the number of site expansion boards required.

68P02900W21-S 5-32 01 Feb 2007

System Information: BSS Equipment Planning

Battery back-up provisioning

Battery back-up provisioning

Introduction
The Horizon II outdoor enclosure can be provisioned to have battery back-up in case of power failure at the site.

Planning considerations
The following factors influence the planning for battery back-up for a Horizon II outdoor enclosure.

Two optional internal batteries to provide a minimum of 5 minutes back-up. An optional external battery cabinet has dimensions 1555x799x760 mm and weight 110 kg when empty, 590 kg with 16 SBS C11 batteries included. This cabinet can house up to 16 Hawker SBS C11 battery cells (8 strings) or equivalent. Two string sets can provide a battery back-up for about one hour; a full cabinet can provide battery back-up for about four hours. The intermediate battery back-up solution consists of a frame fixed to the ground housing the batteries and an oversized shroud fitted over it fixed onto the main cabinet.
o o

Size: 350mm wide x 687mm deep x 1441mm high. Weight: Without batteries including metalwork and interconnect cables, the weight is 40kg. With batteries, the weight is 160kg.

The frame can house a maximum of two strings of SBS C11 batteries (each string consisting of 2 batteries) which provides 1 hour back-up power.

The back-up times for the internal, intermediate, and external battery backup are for a fully loaded system in a worst case scenario. Longer back-up times are achieved under a typical load. There is a visual display of outdoor battery voltages.

68P02900W21-S 01 Feb 2007 5-33

External power requirements

Chapter 5: BTS planning steps and rules

External power requirements

Introduction
Macrocell cabinets and Microcell enclosures can operate from a variety of power supplies.

Planning considerations
The following factors should be considered when planning the power supply requirements:
Horizon II macro

Horizon II macro power requirements are determined by the BTS cabinet type. Indoor: +27 V dc, -48 V dc, 110-230 V ac Outdoor: 200-240 V ac single/3-phase only.
Horizon II mini

Horizon II mini power requirements are determined by the BTS cabinet type. Indoor: +27 V dc, -48 V dc, 110-230 V ac Outdoor: 230 V ac only.
Horizonmacro

Horizonmacro power requirements are determined by the BTS cabinet type. Indoor: +27 V dc, -48 V dc, 230 V ac Outdoor: 110 V ac single phase, 230 V ac single/3-phase. 12 carrier outdoor: 230 V ac single/3-phase.

Only -48 V dc indoor cabinets can be installed in the 12 carrier outdoor.

Horizonmicro2 and Horizoncompact2

The Horizonmicro2 and Horizoncompact2 enclosures operate from 88 to 265 V ac power source.
Horizon II micro

The Horizon II micro enclosure operates from 88 to 300 V ac power source.

M-Cell6

The M-Cell6 BTS cabinet can be configured to operate from either a +27 V dc or -48 V/-60 V dc power source (indoor) or 230 V/110 V ac.

68P02900W21-S 5-34 01 Feb 2007

System Information: BSS Equipment Planning

External power requirements

M-Cell2

The M-Cell2 BTS cabinet can be configured to operate from either a +27 V dc or 230 V/110 V ac power source.
M-Cellcity and M-Cellcity+

The M-Cellcity and M-Cellcity+ BTS enclosures operate from 88 to 265 V ac power source.

Power planning actions

Determine the power supply required.

68P02900W21-S 01 Feb 2007 5-35

Network expansion using macro/microcell BTSs

Chapter 5: BTS planning steps and rules

Network expansion using macro/microcell BTSs

Introduction
An existing network with previous generations of Motorola equipment such as BTS4, BTS5, BTS6, TopCell, or ExCell can be expanded using macro/microcell. The Network topology can be any of those specified in Chapter 2, Transmission systems of this manual. A macro/microcell BTS can occupy any position in a network.

Expansion considerations
The following factors should be considered when expanding an existing network using macro/microcell BTS cabinets:

A macro/microcell BTS cannot share a cell with a BTS4, BTS5, BTS6, TopCell, or ExCell. The rules governing the number of NIUs required at the macro/microcell BTS are given in Table 5-6 of this chapter. The rules governing the number of MSIs required at the BSC are given in the Multiple serial interface (MSI) section of Chapter 6, BSC planning steps and rules.

Mixed site utilization

To upgrade sites utilizing previous generations of Motorola equipment such as BTS5, BTS4, BTS6, TopCell, or ExCell, proceed in the following manner:

Sites with previous generation equipment should be expanded with the appropriate modules, until the cabinets are full. To expand a previous generation site, the equipment in the previous generation cabinet must be re-configured so that it serves a complete set of sectors in the target configuration. A macro site should then be added to the site to serve the remaining sectors. The macro site should then be connected into the network by daisy chaining it to the existing site. Customers who have not purchased the daisy-chaining feature should order the free of charge feature M-Cell - InCell Interworking, SWVN2460, to obtain a suitable license for upgrading.

Example
To upgrade a BTS6 2/2/2 to a 3/3/3, reconfigure the BTS6 to a 3/3, order an M-Cell omni 3 and install it to serve the third sector.

68P02900W21-S 5-36 01 Feb 2007

System Information: BSS Equipment Planning

Line interface modules (HIM-75, HIM-120)

Line interface modules (HIM-75, HIM-120)

Introduction
The line interface modules, HDSL interface module, 75 ohm (HIM-75), and HDSL interface module, 120 ohm (HIM-120), provide impedance matching for E1, T1 and HDSL links.

Planning considerations
The following factors should be considered when planning the line interface complement:

To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544 Mbit/s) 3 V (peak pulse) line, use a HIM-120. To match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peak pulse) line, use a HIM-75. Each HIM-75/HIM-120 can interface four E1/T1 links to specific slots on one shelf.

HIM-75/HIM-120 planning actions

The following planning actions are required:

Determine the number to be deployed. Determine the number of HIM-75s or HIM-120s required.

Minimum number of HIM 75s or HIM 120s =

Number of PCUs 2

68P02900W21-S 01 Feb 2007 5-37

DRI/Combiner operability components

Chapter 5: BTS planning steps and rules

DRI/Combiner operability components

Overview
This enhancement improves the operability of the Digital Radio Interface (DRI) and combiner devices by increasing the flexibility with which these devices can be equipped, unequipped, and re-equipped. This feature is achieved by specifying the DRI role in system combining when equipping the DRI.

DRI and combiner relationship

Figure 5-1 illustrates the DRI and combiner relationship. Figure 5-1 DRI and combiner relationship

COMB 0

First controlling DRI

Second controlling DRI

DRI 0 0

DRI 0 1

68P02900W21-S 5-38 01 Feb 2007

Chapter 6 BSC planning steps and rules

The plans for setting up a BSC and the relevant rules to be followed are described in this chapter. The topics described in this chapter are as follows:
BSC planning overview Capacity calculations BSC system capacity Determining the required BSS signaling link capacities Determining the number of RSLs required Determining the number of MTLs required Determining the number of LMTLs required Determining the number of XBLs required Determining the number of GSLs required Generic processor (GPROC) Transcoding Multiple serial interface (MSI) Packet Subrate Interface (PSI2) Kiloport switch (KSW) and double kiloport switch (DSW2) BSU shelves Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) Generic clock (GCLK) Clock extender (CLKX) Local area network extender (LANX) Parallel interface extender (PIX) Line interface boards (BIB/PBIB, T43/PT43) Digital shelf power supply Non Volatile Memory (NVM) board Verifying the number of BSU shelves and BSSC cabinets

68P02900W21-S 01 Feb 2007 6-1

BSC planning overview

Chapter 6: BSC planning steps and rules

BSC planning overview

Introduction
Information pertaining to the NEs must be known to plan the equipage of a BSC. The NE configuration needs the following information:

Number of BTS sites to be controlled. Number of RF carriers (RTF) at each BTS site. Number of TCHs and PDTCHs at each site. Total number of AMR half rate or GSM half rate capable TCHs at each site. Total number of TCHs and PDTCHs under the BSC. Number of cells controlled from each BTS site should not exceed the maximum number of cells per BSC detailed in Table 6-1. Physical interconnection of the BTS sites to the BSC. Location of the XCDR function. Path for the OML links to the OMC-R. Use of E1 links. Use of Ethernet links. Use of balanced or unbalanced E1. Use of PBIB or PT43. Traffic load to be handled (also take future growth into consideration). Number of MSCs to BSC trunks. LCS architecture.

Mixing of equipment types

The planning rules for each type of shelf should be taken into account, when mixing the BSU and RXU shelves at a BSC. This needs using the information contained in this chapter (for the BSC) and those in Chapter 7, RXCDR planning steps and rules (for the RXCDR), as the RXU shelf is primarily used in the RXCDR. This applies to both the legacy RXU shelf and the new RXU3 shelf. This is also true for the cabinets. The additional connectivity provided by the new BSSC3 is required in the BSC when the RXU3 shelf or shelves are used.

68P02900W21-S 6-2 01 Feb 2007

System Information: BSS Equipment Planning

BSC planning overview

Outline of planning
Planning a BSC involves the following steps:

Plan the number of RSL links between the BSC and BTS site(s). Refer to the section Determining the number of RSLs required. Plan the number of E1 links between the BSC and BTS site(s). Refer to the section BSC to BTS E1 interconnect planning actions. Plan the number of MTL links between the BSC and MSC. Refer to the section Determining the number of MTLs required. Plan the number of XBL links required between the BSC and AXCDR. Refer to the section Determining the number of XBLs required. Plan the number of GSL links required between the BSC and the PCU. Refer to Determining the number of GSLs required. Plan the number of GPROCs required. Refer to the section Generic processor (GPROC). Plan the number of XCDR/GDP/EGDP/GDP2s required. Refer to the section Transcoding. Plan the number of LMTL links required between the BSC and the SMLC, if LCS is enabled in the BSS and if BSS-based LCS architecture is supported. Refer to the section Determining the number of LMTLs required. Ignore this if the BSS supports only the NSS-based LCS architecture. Plan the number of E1 links between the BSC and SMLC if LCS is enabled in the BSS and if BSS-based LCS architecture is supported. Refer to the section Determining the number of LMTLs required. Ignore this if the BSS supports only the NSS-based LCS architecture. Plan the number of MSIs required. Refer to the section Multiple serial interface (MSI). Plan the number of PSI2s required. Refer to the section Packet Subrate Interface (PSI2). Plan the number of KSWs/DSW2s and timeslots required. Refer to the section Kiloport switch (KSW) and double kiloport switch (DSW2). Plan the number of BSU shelves. Refer to the section BSU shelves. Plan the number of KSWXs/DSWXs required. Refer to the section Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX). Plan the number of GCLKs required. Refer to the section Generic clock (GCLK). Plan the number of CLKXs required. Refer to the section Clock extender (CLKX). Plan the number of LANXs required. Refer to the section Local area network extender (LANX). Plan the number of PIXs required. Refer to the section Parallel interface extender (PIX). Plan the number of (P) BIB or (P) T43s required. Refer to the section Line interface boards (BIB/PBIB, T43/PT43). Plan the power requirements. Refer to the section Digital shelf power supply. Decide whether an NVM board is required. Refer to the section Non Volatile Memory (NVM) board. Verify the planning process. Refer to the section Verifying the number of BSU shelves and BSSC cabinets.

68P02900W21-S 01 Feb 2007 6-3

Capacity calculations

Chapter 6: BSC planning steps and rules

Capacity calculations
Introduction
The throughput capacities of the BSC processing elements (for example, GPROC) and the throughput capacities of its data links, determine the number of supported traffic channels (TCHs). These capacities are limited by the ability of the processors, and the links to process the signaling information associated with these TCHs. The following sections, discussed , provide information on how to calculate processor requirements, signaling link capacities and BSC processing capacities:

BSC system capacities BSS signaling link capacities Traffic models BSC GPROC functions and types Number of GPROCs required

Remote transcoding
When the transcoding function resides outside of the BSC cabinet, in the RXCDR, it is possible to have multiple RXCDRs connected to a single BSC, and vice-versa. This is especially useful for two reasons:

In certain configurations, the RXCDR call (CIC) capacity is greater than that of a BSC. A failure of an RXCDR or communication line does not result in a complete failure of the BSC to handle calls.

Each BSC connects to up to nine RXCDRs, and vice-versa. The level of connectivity is constrained by the number of XBLs supported. The connectivity is limited to 20 at each BSC and RXCDR (see Determining the number of XBLs required in this chapter). The operator determines the level of connectivity. Excess RXCDR capacity should not be wasted, nor should larger BSCs be connected only to one RXCDR. One guideline is to have each BSC connect to four RXCDRs. System size, capacity, and cost are the major factors in deciding the configuration.

68P02900W21-S 6-4 01 Feb 2007

System Information: BSS Equipment Planning

BSC system capacity

BSC system capacity

System capacity summary
Table 6-1 provides a summary of BSC maximum capacities. Table 6-1 BSC maximum capacities Item GSR7 GSR8 GSR9

BTS sites BTSs (cells) Active RF carriers DRIs RSLs PCUs GSLs MMS PATHs DHPs LCFs Trunks(see NOTE ) C7 links to MSC C7 links to SMLC E1 links Ethernet links Maximum busy hour call attempts

100 250 384

a,b

100 250 384

a,b

100d 250 384a,b,d 384a,d 250 1 60c 112e 250 232 25 2400a,b,d 16 16 112e 12f 90,000d

384a,b 250 3 180

c

384a,b 250 3 180

c

112 250 232 25 2400 16 16 112 N/A 90,000

a,b

112 250 232 25 2400 16 16 112 N/A 90,000

a,b

- The capacity can be increased to 512 carriers and 3200 trunks if the optional enhanced BSC capacity feature is enabled.

- For GSR9, it is mandatory to deploy GPROC3/GPROC3-2s in active and/or standby BSP slots in the BSC in any potential BSP slots on a site. For example, slot 20 and slot 24 in shelf 0 and slot 20 in shelf 1. - 180 for 3xPCU, 60 per PCU in GSR7 and GSR8. For GSR9, the BSS can support 60 GSLs with the introduction of ePCU (refer to Chapter 8).

68P02900W21-S 01 Feb 2007 6-5

BSC system capacity

Chapter 6: BSC planning steps and rules

- The capacities represent the BSS capacities for GSM circuit-switched traffic. If the GPRS traffic is carried on the BSS, the GSM circuit-switched traffic handling capacity reduces in direct proportion to the timeslots configured for GPRS traffic. - The capacity can be increased to 140 BTS sites, 750 carriers, and 4800 trunks, if the optional huge BSC capacity feature is enabled. The maximum number of DRIs is 750. - With {22169}96 MSI feature introduced, a BSC site can support 192 MMSs.

A PSI2 replaces a MSI to support the Ethernet link between BSC and PCU. The maximum number of PSI2 boards and Ethernet links is 12. The MMS number and E1 links decrease accordingly. Planning is a multi-variant problem. When planning a BSC, any limit given in Table 6-1 should not be exceeded for the GSR version used. The first element to reach its limit sets the capacity of the BSC. For example, when dimensioning a BSC with a specific non-standard call model, there is a possibility that the LCF or C7 limit is reached before the Erlang limit is reached.

Scaleable BSC
With the launch of the scaleable BSC, Motorola moved to a position where the diverse requirements of network users in terms of BSC size are addressed by a single platform that can be efficiently configured in small, medium, or large models. Before GSR7, the move to a scaleable BSC is enabled through the migration of the processing boards within the BSC to use the GPROC2 throughout. Now, GPROC2s can be replaced by the new GPROC3s at board level in any slot, thus preserving the scaleable BSC architecture. BSSs targeted at small, medium, or large networks are efficiently addressed by the scaleable BSC where minimal incremental hardware is required to be added as the networks grow. From GSR8, it is mandatory to deploy GPROC3s in active and/or standby BSP slots in the BSC in any potential BSP slots on a site (that is, slot 20 and slot 24 in shelf 0 and slot 20 in shelf 1). Being able to expand capacity within a BSC is beneficial from an operational viewpoint, because there is less time and effort involved than compared with having to move sites from one BSC to another, or even from one OMC-R to another. Put into context, the BSC capacity before GSR3 supported in the order of 40 sites of three sectors and one carrier per sector; or alternatively, 20 sites of three sectors and two carriers per sector. At GSR3, the capacity was increased to allow the operator to move to support in the order of 40 sites of three sectors and two carriers per sector. At GSR4, the capacity is increased to allow the operator to move to support in the order of 64 sites of three sectors and two carriers per sector. The scaleable BSC also offers a substantial advantage for microcellular deployment where a single BSC is able to support up to 100 microcellular BTSs, each equipped with two carriers per site. The scaleable BSC capacity is enabled because of the increased processing performance and memory of the GPROC. The maximum capacity is increased as shown in Table 6-1. This increased capacity is achieved through the deployment of GPROC2s or GPROC3s/GPROC3-2s for each function at the BSC, including Base Station Processor (BSP) and Link Control Function (LCF).

The GPROC3/GPROC3-2 is a high performance direct replacement for the GPROC2 and the original GPROC (GPROC1).

68P02900W21-S 6-6 01 Feb 2007

System Information: BSS Equipment Planning

BSC system capacity

Enhanced BSC capacity option

This feature is introduced as a restricted option. If the feature is restricted, the BSC supports the normal BSC maximum capacity of 384 RF carriers, and 2400 trunks (see Table 6-1). If the feature is unrestricted, the BSC maximum capacity is increased to 512 RF carriers and 3200 trunks. Hardware upgrades are required by the BSS to support the optional Enhanced BSC capacity. BTP processors at the InCell BTSs must be replaced with GPROC2s.

From GSR8, GPROC3s are required in the BSP slots.

Huge BSC capacity option

This feature is introduced as a restricted option. If the feature is restricted, the BSC supports the BSC maximum capacity of 100 BTS sites, 384 RF carriers, and 2400 trunks (see Table 6-1). If the feature is unrestricted, the BSC maximum capacity is increased to 140 BTS sites, 750 RF carriers, and 4800 trunks. Hardware upgrades are required by the BSS to support the optional Huge BSC capacity. Specifically, HSP MTLLCF processors must be replaced with GPROC3-2 to support the HSP MTL link and DSW2/DSWX is mandatory to increase the number of TDM timeslots from 1024 to 2048.

LCS option
This feature is a restricted option. If the feature is restricted, no location service capability is provided. If the feature is unrestricted, the BSS supports the Network Sub-System (NSS) based Serving Mobile Location Center (SMLC) architecture or the BSS-based SMLC architecture, and the BSS supports new LCS signaling for cell ID +TA positioning method:

New LCS signaling messages on the A-interface or Lb interface. New LCS signaling messages on the Mobis interface and Um interface.

The provisioning rules and steps for BSS equipment only support cell ID and the TA positioning method for LCS is provided for NSS-based and BSS-based LCS architectures respectively in the following sections.

68P02900W21-S 01 Feb 2007 6-7

Determining the required BSS signaling link capacities

Chapter 6: BSC planning steps and rules

Determining the required BSS signaling link capacities

BSC signaling traffic model
For a GSM system, the throughput of network entities, including subcomponents, depends upon the assumed traffic model used in the network design or operation. Traffic models are fundamental to some planning actions. The capacity of the BSC as a whole, or the capacity of a particular GPROC, depends on its ability to process information transported through signaling links connecting it to the other network elements. These elements include MSC, BTSs, and the OMC-R. Depending on its device type and BSC configuration, a GPROC controls signaling links to one or more other network elements. A capacity figure can be stated for each GPROC device type in terms of a static capacity such as the number of physical signaling links supported, and a dynamic capacity such as processing throughput. In general telephony environments, processing and link throughput capacities can be stated in terms of the offered call load. To apply this for the GSM BSC, all signaling information to be processed by the BSC is related to the offered call load (the amount of traffic offered/generated by subscribers). When calls are blocked due to all trunks or all TCHs being busy, most of the signaling associated with call setup and clearing still takes place, even though few or no trunk resources are utilized. Therefore, the offered call load (which includes the blocked calls) should be used in planning the signaling resources (for example; MTLs and RSLs). In the case where the BSC has more than enough trunks to handle the offered traffic, adequate signaling resources should be planned to handle the potential carried traffic. The trunk count can be used as an approximate Erlang value for the potential load carried. As a result, the signaling links and processing requirements should be able to handle the greater of the following:

Offered load Potential load

The number of trunks or the offered call load in Erlangs (whichever is greater) should be used to determine the link and processing requirements of the BSC. BSC capacity planning needs a model that takes into consideration the signaling generated from all the pertinent GSM procedures: call setup and clearing, handover, location updating, and paging, to the offered call load. To establish the relationship between all the procedures, the traffic model expresses processing requirements for these procedures as ratios to the number of call attempts processed. The rate at which call attempts are processed is a function of the offered call load and the average call hold time.

A standard traffic model can be assumed when initially planning a network. However, once the network is running, it is critical to monitor and measure the real call parameters (described in Chapter 11) from the live network to ascertain the true network call model.

68P02900W21-S 6-8 01 Feb 2007

System Information: BSS Equipment Planning

Determining the required BSS signaling link capacities

Future planning should then be based on this actual (non-standard) call model instead of the standard call model. Past studies have shown that the actual call model in some networks differs considerably from the standard call model, and this has a direct impact on dimensioning requirements.

Figure 6-1 graphically depicts various factors that should be taken into account when planning a BSS. Figure 6-1 BSS planning diagram
MSC TRANSCODER
WITH SUBMULTIPLEXING TRANSCODING AT MSC 1 x 64 KBIT/S CIRCUIT/C7 SIGNALLING LINK 1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK * 1 x 64 KBIT/S CIRCUIT/ XBL 1 x 64 KBIT/S CIRCUIT/4 TRUNKS 1 x 64 KBIT/S CIRCUIT/8 TRUNKS (HALF RATE WITH 8 KBIT/S SUBMULTIPLEXING ENABLED) WITH SUBMULTIPLEXING TRANSCODING AT BSC 1 x 64 KBIT/S CIRCUIT/C7 SIGNALLING LINK 1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK* 1 x 64 KBIT/S CIRCUIT/TRUNK

A INTERFACE (TERRESTRIAL LINKS) -C7 SIGNALLING LINKS -X.25 CONTROL LINK * -REQUIRED TRUNKS

GDS INTERFACE ** - GDS TRAU CHANNELS - GSL LINKS

GBL

BSC TO PCU GDS-TRAU CIRCUITS THE # OF GSLs THE # OF GBLs

PCU

1 x 16 KBIT/S CIRCUIT/GPRS TIMESLOT FOR CS1 AND CS2 2 x 16 KBIT/S CIRCUIT/GPRS TIMESLOTS FOR CS3 AND CS4 1 x 64 KBIT/S GSL LINK RTF_DS0_COUNT x 64 KBIT/S FOR EACH EGPRS RTF

THE BSC TO MSC 64 kbit/s CIRCUITS ARE DETERMINED FROM THE # OF TRUNKS REQUIRED TO CARRY THE SUMMATION OF AIR INTERFACE TRAFFIC (IN ERLANGS, TYPICALLY USING 1% BLOCKING) FROM ALL BTSs - PLUS THE # OF GDS TRAU LINKS (DETERMINED FROM THE NUMBER OF GPRS TIMESLOTS UNDER A BSC) - PLUS THE # OF C7 SIGNALLING LINKS - PLUS - (IF APPLICABLE*) THE # OF X.25 LINKS (USUALLY ONE PER BSC) - PLUS THE # OF XBL LINKS - PLUS THE # OF GSL LINKS BSC
1 x 64 KBIT/S OF 1 x 16 KBIT/S RTF CIRCUIT/LAPD SIGNALLING LINK 2 x 64 KBIT/S CIRCUITS/RTF 4 x 64 KBIT/S CIRCUITS/RTF (SEE NOTE)

MOTOROLA BSC/BTS INTERFACE NON-BLOCKING

THE # OF TCHs REQUIRED (USING TYPICALLY 2% BLOCKING) TO CARRY SUBSCRIBER TRAFFIC. THE TCHs PLUS THE REQUIRED SIGNALLING TSs DIVIDED BY EIGHT (OR 16 WITH HALF RATE MANDATED) DETERMINES THE CARRIERS REQUIRED (ON A BTS/SECTOR BASIS) BTS
AIR INTERFACE -TCHs, PDTCHs AND SIGNALLING TSs -TYPICALLY 2% BLOCKING FOR CS TRAFFIC AIR INTERFACE (TRAFFIC IN ERLANGS)

TRANSCODING MUST BE LOCATED AT THE BSC, OR BETWEEN THE BSC AND MSC 8 pt. left aligned text TCH = TRAFFIC CHANNEL TS = TIMESLOT * X.25 MAY BE PASSED TO RXCDR OR MSC SITE ** GDS-TRAU AND GSL ARE CARRIED ON SEPARATE LINKS

USING TRAFFIC, TO DETERMINE E1/T1 LINK INTERCONNECT HARDWARE FOR THE `A' AND `BSC TO BTS' INTERFACE.

68P02900W21-S 01 Feb 2007 6-9

Determining the required BSS signaling link capacities

Chapter 6: BSC planning steps and rules

4 x 64 kbit/s circuits/RTF for a (AMR or GSM) HR RTF and 8 kbit/s switching is not provisioned, or (for AMR only) the 7.95 kbit/s half rate codec mode is included in the Half Rate Active Codec Set. Besides the factors described in Figure 6-1, when LCS is enabled in the BSS, the following factors require to be taken into account when planning a BSS:

MTL link provisioning to support LCS signaling between the MSC and BSC for either NSSbased LCS architecture or BSS-based LCS architecture, but not both. LMTL link provisioning for BSS-based LCS architecture only. RSL link provisioning with LCS supported.

Typical parameter values

The parameters required to calculate BSC processing and signaling link capacities are listed in Table 6-2 with their typical values. Two methods for determining the BSC link capacity are given. The first method is based on the typical call parameters given in Table 6-2 and simplifies planning to look up tables, or the simple formulae indicated in the standard traffic model planning steps. When the call parameters being planned differ significantly from the standard traffic model, more complex formulae must be used as indicated in Nonstandard traffic model planning steps.
Table 6-2 Typical call parameters Busy hour peak signaling traffic parameter Reference parameter

Call duration Ratio of SMSs per call Number of handovers per call Ratio of location updates to calls: non-border location area Ratio of location updates to calls: border location area Ratio of IMSI detaches to calls Location update factor: non-border location area using IMSI type 2 Location update factor: border location area using IMSI type 2 GSM circuit-switched paging rate in pages per second Ratio of intra-BSC handovers to all handovers Ratio of LCSs per call

T = 90 seconds S =2 H = 1.32 l=2 l=7

I = 0.2 L = l + 0.5I = 2.1 L = l + 0.5I = 7.1 PGSM = 60 i = 0.6 Lcs = 0.1

Continued

68P02900W21-S 6-10 01 Feb 2007

System Information: BSS Equipment Planning

Determining the required BSS signaling link capacities

Table 6-2 Typical call parameters (Continued) Busy hour peak signaling traffic parameter Reference parameter

Mobile terminated LCS ratio Mobile originated LCS ratio Percent link utilization (MSC to BSS) Percent link utilization (BSC to BTS) Percent link utilization (BSC to RXCDR) Percent link utilization (BSC to SMLC) Percent link utilization (BSC to PCU) Percent link utilization (BSC to SGSN) Percent CCCH utilization Block Rate for TCHs Block Rate for MSC-BSS trunks Number of cells per BTS Average SMS message size (payload only) Number of BSCs per location area Busy Hour Call Attempts per sub/BH
XBL (enhanced auto connect) parameters

LRMT = 0.95 LRMO = 0.05 U(MSC BSS) = 0.20 U(BSC BTS) = 0.25 UBSC-RXCDR = 0.40 UBSC-SMLC = 0.40 UBSC-PCU = 0.25 UGBL = 0.40 UCCCH = 0.33 PB-TCHs = 2% PB-Trunks = 1% CBTS = 3 SMSSIZE = 100 bytes BSCLA = 1 BHCAsub = 1.8 MNEWCALL = 1 MHANDOVER = 1 LXBL =50 Hhr-fr = 1 PKSIZE = 336.65 ULRATE = 34.14 DLRATE = 127.81 Avg_Sessions_per_sub = 0.64 PSATT/DETACH = 0.5 PDPACT/DEACT = 0.4 RAU = 1.4 PGPRS = 25.91
Continued

Number of XBL messages per new call Number of XBL messages per hr <-> fr handover Length of an average XBL message, in bytes Number of hr <-> fr handovers per call
GPRS parameters

GPRS Average packet size (bytes) GPRS Traffic per sub/BH ( bytes/hr) Uplink GPRS Traffic per sub/BH ( bytes/hr) Downlink Average sessions per subscriber (per BH) PS attach/detach rate (per sub/BH) PDP context activation/deactivation (per sub/BH) Routing area update GPRS paging rate in pages per second

68P02900W21-S 01 Feb 2007 6-11

Determining the required BSS signaling link capacities

Chapter 6: BSC planning steps and rules

Table 6-2 Typical call parameters (Continued) Busy hour peak signaling traffic parameter Reference parameter

Coding scheme rates (CS1 to CS4) at the RLC/MAC layer

CS1 = 9.2 kbit/s CS2 = 13.6 kbit/s CS3 = 15.8 kbit/s CS4 = 21.8 kbit/s

Coding scheme usage (CS1 to CS4) at a BLER of 10%

CS1_usage_UL = CS1_usage_DL = 20% CS2_usage_UL = CS2_usage_DL = 45% CS3_usage_UL = CS3_usage_DL = 25% CS4_usage_UL = CS4_usage_DL = 10%

Percentage GPRS coding scheme usage in total traffic (see ) Cell updates (per sub/BH)
EGPRS parameters

CSuse_UL_GPRS = CSuse_DL_GPRS = 50% CellUpdate = 0.33 PKULSIZE = 134.39 PKDLSIZE = 562.99 ULRATE = 34.14 DLRATE = 127.81 Avg Sessions per sub = 0.64 PSATT/DETACH = 0.5 PDPACT/DEACT = 0.4 RAU = 1.4 PGPRS = 25.91 MCS1 = 10.55 MCS2 = 12.95 MCS3 = 16.55 MCS4 = 19.35 MCS5 = 23.90 MCS6 = 29.60 MCS7 = 31.10 MCS8 = 46.90 MCS9 = 61.30
Continued

EGPRS Average packet size (bytes) - Uplink EGPRS Average packet size (bytes) Downlink EGPRS Traffic per sub/BH (kbytes/hr) Uplink EGPRS Traffic per sub/BH (kbytes/hr) Downlink Average sessions per subscriber (per BH) PS attach/detach rate (per sub/BH) PDP context activation/deactivation (per sub/BH) Routing area update GPRS paging rate in pages per second Coding scheme rates (MSC1-MSC9) at the RLC/MAC layer

68P02900W21-S 6-12 01 Feb 2007

System Information: BSS Equipment Planning

Determining the required BSS signaling link capacities

Table 6-2 Typical call parameters (Continued) Busy hour peak signaling traffic parameter Reference parameter

Coding scheme usage (MCS1 to MCS9) at a BLER of 20%

MCS1_usage_UL = MCS1_usage_DL = 10% MCS2_usage_UL = MCS2_usage_DL = 8% MCS3_usage_UL = MCS3_usage_DL = 33% MCS4_usage_UL = MCS4_usage_DL = 1% MCS5_usage_UL = MCS5_usage_DL = 21% MCS6_usage_UL = MCS6_usage_DL = 15% MCS7_usage_UL = MCS7_usage_DL = 5% MCS8_usage_UL = MCS8_usage_DL = 3% MCS9_usage_UL = MCS9_usage_DL = 4%

Percentage EGPRS coding scheme usage in total traffic Average packet size for GPRS and EGPRS traffic mix (bytes) Uplink (see ) Average packet size for GPRS and EGPRS traffic mix (bytes) Downlink (see )
DTM parameters

CSuse_UL_EGPRS = CSuse_DL_EGPRS = 50% PKULSIZE = 134.39 PKDLSIZE = 562.99

Percentage of DTM mobiles DTM mode scaling factor (see )

QoS parameters

MSDTM = 30% DTMfactor = 30% GBRAVG_UL = 3.80 GBRAVG_DL = 5.60 GBRPEAK_UL = 9.65 GBRPEAK_DL = 12.70

Average GBR for service mix (kbit/s) - Uplink Average GBR for service mix (kbit/s) Downlink Peak GBR for service mix (kbit/s) - Uplink Peak GBR for service mix (kbit/s) - Downlink

68P02900W21-S 01 Feb 2007 6-13

Determining the required BSS signaling link capacities

Chapter 6: BSC planning steps and rules

Number of handovers: These include 2G-3G handovers. Percentage GPRS coding scheme usage: These percentages represent the split of the traffic between for GPRS and EGPRS traffic mix, which is network dependent. The percentages can be used to determine the average traffic per sub/BH for a GPRS and EGPRS traffic mix as follows: Traffic per sub/BH for GPRS and EGPRS mix (kbytes/hr) = (Percentage GPRS coding scheme usage in total traffic * GPRS Traffic per sub/BH) + (Percentage EGPRS coding scheme usage in total traffic * EGPRS Traffic per sub/BH) Average packet size for GPRS and EGPRS traffic mix (bytes): These are the average packet sizes for a GPRS and EGPRS traffic mix based on the GPRS and EGPRS percentage splits defined for this model. DTM mode scaling factor: The DTM scaling factor represents the likelihood that a DTM subscriber can overlap a CS call and a PS session.

Location update factor

The location update factor (L) is a function of the ratio of location updates to calls (l), the ratio of IMSI detaches to calls (I) and whether the short message sequence (type 1) or long message sequence (type 2) is used for IMSI detach; typically I = 0 (that is IMSI detach is disabled) as in the first formula given . When IMSI detach is enabled, the second or third of the formulas given should be used. The type of IMSI detach used is a function of the MSC. If IMSI detach is disabled: L=1 If IMSI detach type 1 is enabled: L = 1+ 0.2 * I If IMSI detach type 2 is enabled: L = 1+ 0.5 * I

Other parameters
Other parameters used to determine GPROC and link requirements are listed in Table 6-3.
Table 6-3 Other parameters used in determining GPROC and link requirements Busy hour peak signaling traffic mode Reference parameter

Number of MSC - BSC trunks Number of BTSs per BSS Number of cells per BSS Pages per call LCS request rate (req/sec/BSC)

N B C PPC = PGSM * (T/N) LCS_BSC_Rate = (N/T) * LCS

68P02900W21-S 6-14 01 Feb 2007

System Information: BSS Equipment Planning

Determining the required BSS signaling link capacities

Assumptions used in capacity calculations

Signaling message sequence and size assumptions
Certain signaling message sequence patterns and message sizes have been assumed to calculate link and processing capacity values for the various procedures included in the signaling traffic model. These assumptions translate into specific formula coefficients and include a margin of safety. As they are dependent on call procedures, they are recalculated for every major software release. Link utilization should be monitored to detect significantly different behavior. The procedures used for the calculations are provided in Table 6-4.
Table 6-4 Signaling message procedures MSC - BSC BSC - BTS SMLC - BSC

Call setup and clearing Handover, incoming and outgoing Location update SMS - P to P IMSI detach (type 1) IMSI detach (type 2) Paging N/A

Call setup and clearing Handover, incoming and outgoing Location update SMS - P to P IMSI detach (type1) IMSI detach (type 2) Paging One phase access and Enhanced one phase access

N/A N/A N/A N/A N/A N/A N/A

Enhanced One Phase is not supported with EGPRS carriers. LCS LCS LCS

The BSS software uses a new small message header (compact header) for delivering messages between the BSC/PCU and the BTS. The new message header contains the minimum information necessary to deliver the messages between the processes. The size of the new message header is 8 bytes, as compared to 28 bytes in pre GSR6 releases. This reduces the signaling link utilization between the BSC-BTS and BSC-PCU. An additional assumption, which is made in determining the formula coefficients, is that the procedures not included in the traffic model are considered to have a negligible effect.

Supplementary Service (SS) messaging has not been taken into account. This could contribute a significant signaling overhead in some networks.

68P02900W21-S 01 Feb 2007 6-15

Determining the required BSS signaling link capacities

Chapter 6: BSC planning steps and rules

Paging assumptions
In calculating the average message size for paging, it is assumed that paging is by LAC (or LAI) only. Paging by LAC only, is the recommended method. Paging by LAC and cell ID is not necessary, and has two major disadvantages:

The paging method is controlled by the MSC and is signaled to the BSC through the setting of the Cell Identification Discriminator in the BSSMAP paging message. The BSC can determine from its Configuration Management database the cells that require to be paged from the location area code only. Therefore, the MSC does not require to send a list of each individual cell identity. Paging by LAC and Cell ID increases the length of the BSSMAP paging considerably and significantly increases the C7 signaling load between the MSC and BSC. Paging by LAC only reduces the possibility of paging channel overload on the air interface caused by any database mismatch between the BSC and MSC. If the BSC receives a cell identity in the paging message from the MSC that does not exist in its Configuration Management database, it defaults to paging all cells in the BSS for safety reasons. This can cause overload of the paging channel on the radio interface.

Half rate assumptions

A (AMR or GSM) half rate enabled carrier is capable of carrying two half rate calls in each timeslot, for 16 (half rate) TCHs. The actual number in use at a given instance depends upon such factors as user (both BSS and MSC) preference, mobile (that is, AMR capable) penetration, RF conditions, handoff parameter, and threshold setting, cell congestion levels, and so on. If it is known to a large degree of certainty what is the mix of half rate and full rate calls, that number can be used when considering equipment planning. Otherwise, it is recommended that a worst case approach be taken. For example, when determining the RSL signaling link capacity required, and half rate usage is expected to be no more than 50%, and there are two (both half rate enabled) carriers, a mix of 9 fr and 10 hr (plus 2 timeslots for signaling) TCHs can be used (for a total of 19). A worst case estimate assumes 16 TCHs per half rate enabled carrier, for 28 TCHs. If only one carrier is half rate enabled, worst case results in (16 hr, 6 fr) 22 TCHs. When 8 kbit/s subrate switching is not available, or an RTF is configured as AMR half rate capable and the 7.95 kbit/s half rate codec mode is included in the Half Rate Active Codec Set, then the carrier unit assigned to that RTF needs four 64 kbit/s timeslots on the E1 circuit (regardless of how they are utilized). For an EGPRS capable RTF (pkt_radio_type set to 3), 16 kbit/s switching on the backhaul is not supported and allow_8k_trau has to be enabled if half rate is supported.

AMR HR Active Codec Set cannot include 7.95 kbit/s, when pkt_radio_type is set to 3.

68P02900W21-S 6-16 01 Feb 2007

System Information: BSS Equipment Planning

Determining the required BSS signaling link capacities

Link capacities
The level of link utilization is largely a matter of choice of the system designer. A design that has more links running at a lower message rate can have the advantage of offering better fault tolerance, since the impact of failure of any one link on the signaling traffic is less. Reconfiguration around the fault could be less disruptive. Such a design could offer reduced queuing delays for signaling messages. A design that utilizes fewer links at a higher message rate, reduces the number of 64 kbit/s circuits required for signaling, and potentially reduces the number of resources (processors, data ports) required in the MSC. It is recommended that the C7 links be designed to operate at no more than 20% link utilization when the MTL is running on a GPROC1 and no more than 40% utilization when the MTL/LMTL is running on a GPROC2 or GPROC3. Before use of the 40% utilization for GPROC2 or GPROC3, it is imperative that the operator verifies that the MSC/SMLC vendor can also support 40% utilization at the MSC/SMLC end; if not, only 20% link utilization should be used for GPROC2 and GPROC3. If higher link utilizations are used, the controlling GPROCs (LCF-MTLs/LCF-LMTLs) become overloaded. If HSP MTL {28337} is enabled, no more than 20% link utilization for the 2M MTL is recommended.

Overloading GPROCs can cause the BSC to become unstable. Links must be monitored closely to ensure that link utilization does not exceed the maximum. If link utilization is regularly approaching the maximum, additional capacity should be added to reduce the possibility of overloading the GPROCs. The protocol C7, used for the MSC to BSC links and SMLC to BSC links, allows for the signaling traffic from the failed link to be redistributed among the remaining functioning links. Both the MSC-BSC and SMLC-BSC C7 link set officially have at least two and at most 16 links. The failure of links, for any reason, causes the signaling to be shared across the remaining members of the link set. Therefore, the design must plan for reserve link and processing capacity to support a certain number of failed signaling links.

68P02900W21-S 01 Feb 2007 6-17

Determining the number of RSLs required

Chapter 6: BSC planning steps and rules

Determining the number of RSLs required

Introduction
Each BTS site that is connected directly to the BSC, including the first site in a daisy chain, must be considered individually. Once individual RSL requirements are calculated, the total number of LCFs can be determined for the BSC.

Planning considerations
The following factors should be considered when planning the provision of RSL (LAPD signaling) links from the BSC to BTS sites:

With the Motorola BSC/BTS interface, there is a need for at least one RSL link to every BTS site. One link can support multiple collocated cells. As the system grows, additional signaling links are required. Refer to the section Determining the required BSS signaling link capacities in this chapter to determine the number of RSL links required. If closed loop daisy chains are used, each site needs a RSL in both directions. The provision of additional RSL links for redundancy. PCCCH signaling traverses the GDS (on a PDTCH) instead of the RSL. Thus, cells with PCCCH enabled do not add to the RSL requirements for the BTS. If paging coordination is enabled with PCCCH, GSM circuit-switched pages are sent on the PCCCH. Thus, some of the GSM paging load is removed from the RSL. If LCS is enabled in the BSS, the signaling load due to LCS needs to be taken into account. The number of 16 kbit/s RSL links is limited, depending on the platform. See 16 kbit/s RSL in Chapter 2 for further details. 64 kbit/s RSLs must be used when allowable numbers are exceeded.

If DTM is unrestricted in the BSS, the signaling load due to DTM Call Establishment/Release and GTTP needs to be taken into consideration. Based on the analysis under current call model parameters, the additional load by DTM is minor and can be ignored. With the incremental penetration of DTM capable subscribers, the DTM signaling load will be increased in the future. {26881} Extended Uplink TBF is the feature enhances uplink data performance by minimizing the interruptions of uplink data flow in GPRS/EGPRS networks due to a frequent release and establishment of uplink TBF. According to the principle of Extended Uplink TBF, this feature decreases the amount of RACH for uplink applications session like uplink FTP, and so on. If the uplink application is rare, the total amount of decreased RACH is small. Thus, the impact of RACH decrement can be ignored. If the uplink applications are booming, total amount of decreased RACH is huge. Therefore the impact of RACH decrement cannot be ignored, and RACH decrement is taken into account for RSL calculation.

68P02900W21-S 6-18 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of RSLs required

Table 6-5 lists the limitations for 16 kbit/s RSLs supported on each BTS platform. Table 6-5 BTS support for 16 kbit/s RSLs BTS Platform Number of 16 kbit/s RSLs Supported

A BSU-based BTS Horizon II macro and Horizonmacro Horizonmicro2 / Horizoncompact2 M-Cell6 M-Cell2 M-Cellmicro and M-Cellcity

8 6 2 6 4 2

Horizon II macro BTSs support 4 x RSLs per E1, whereas Horizonmacro and M-Cell BTSs only support 2 x RSLs per E1. This should be taken into consideration when determining the number of E1s required to support the calculated RSLs per site.

Determining the number of RSLs

The equation for determining the number of RSL links for the combined signaling load is as follows: RSLGPRS + GSM = RSLGPRS + RSLGSM This is evaluated for 16 kbit/s RSLs or for 64 kbit/s RSLs. The interface between the BTS and BSC does not permit mixing the two RSL rates.
Where Is

RSLGPRS + GSM

the combined number of RSL signaling links on a per BTS site basis operating at a 16 kbit/s RSL rate or at a 64 kbit/s RSL rate. the number of RSL signaling links required to serve the GPRS part of the network at 16 kbit/s or at 64 kbit/s. the number of RSL signaling links required to serve the GSM part of the network at 16 kbit/s or at 64 kbit/s.

RSLGPRS

RSLGSM

One phase access and enhanced one phase

In a GPRS network, there are two packet access procedures that a mobile station can use to establish an uplink TBF. The packet access performs in either one phase or in two phases. In GPRS software architecture before GSR6, the BSS supports only the two phase-access procedure. Now, one phase access mode and enhanced one phase access mode are supported.

68P02900W21-S 01 Feb 2007 6-19

Determining the number of RSLs required

Chapter 6: BSC planning steps and rules

One phase access

In a one phase uplink TBF access, the MS initiates an uplink TBF by sending a RACH to the BSS. The RACH is received at the BTS and is then forwarded to the PCU. The PCU responds to the RACH with an Immediate Assignment message containing an uplink assignment. The MS moves to the assigned PDTCH and begins its uplink data transfer. This procedure allows the MS to gain access to the network much quicker than the two-phase establishment procedure.

Enhanced one phase

The enhanced one phase uplink TBF access procedure speeds up the one phase packet access procedure even further. The enhanced one phase access procedure allows the PCU to assign resources for a one phase uplink TBF, allowing the BTS to react quickly to a one phase RACH without forwarding the RACH to the PCU and incurring excessive RSL delay and increasing RSL load. Depending on the RSL load, the RACH to Immediate Assignment delay reduces by approximately 60 ms or more.

Standard traffic model

The number of BSC to BTS signaling links (RSLs) must be determined for each BTS. This number depends on the number of TCHs and PDTCHs at the BTS. Table 6-6 gives the number of RSLs required (rounded up to the nearest integer value) for a BTS to support the given number of TCHs and PDTCHs, based on the typical call parameters given in the standard traffic model column of Table 6-2. If the call parameters differ significantly from the standard traffic model, use the formulae for the non-standard traffic model.

Table 6-6 assumes that there are no cells with PCCCH enabled.

Enhanced One Phase is not supported with EGPRS carriers. For assumptions specific to half rate refer to section Half rate assumptions.

Table 6-6 Number of BSC to BTS signaling links (without LCS) With Enhanced One Phase Access #TCHs/BTS (n) #PDTCHs/ BTS (Ngprs) # 64 kbit/s RSLs # 16 kbit/s RSLs With One Phase Access # 64 kbit/s RSLs # 16 kbit/s RSLs

<= 30

0 15 30 45 60 75 90

2 2 2 2 2 2 2

8 8 8 8 8 8 8

2 2 2 2 2 2 2

8 8 8 8 8 8 8
Continued

68P02900W21-S 6-20 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of RSLs required

Table 6-6 Number of BSC to BTS signaling links (without LCS) (Continued) With Enhanced One Phase Access #TCHs/BTS (n) #PDTCHs/ BTS (Ngprs) # 64 kbit/s RSLs # 16 kbit/s RSLs With One Phase Access # 64 kbit/s RSLs # 16 kbit/s RSLs

31 to 60

0 15 30 45 60 75 90

3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 4

9 9 9 9 9 9 9 10 10 10 10 10 10 10 11 11 11 11 11 11 11 12 12 12 12 12 12 12 14

3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 4

9 9 9 9 9 9 9 10 10 10 10 10 10 10 11 11 11 11 11 11 11 12 12 12 12 12 12 12 14
Continued

61 to 90

0 15 30 45 60 75 90

91 to 120

0 15 30 45 60 75 90

121 to 150

0 15 30 45 60 75 90

151 to 180

68P02900W21-S 01 Feb 2007 6-21

Determining the number of RSLs required

Chapter 6: BSC planning steps and rules

Table 6-6 Number of BSC to BTS signaling links (without LCS) (Continued) With Enhanced One Phase Access # TCHs/BTS (n) #PDTCHs/ BTS (Ngprs) # 64 kbit/s RSLs # 16 kbit/s RSLs With One Phase Access # 64 kbit/s RSLs # 16 kbit/s RSLs

15 30 45 60 75 90 181 to 210 0 15 30 45 60 75 90

4 4 4 4 4 4 4 4 4 4 4 4 4

14 14 14 14 14 14 15 15 15 15 15 15 15

4 4 4 4 4 4 4 4 4 4 4 4 4

14 14 14 14 14 14 15 15 15 15 15 15 15

The RSL calculations assume PGPRS = 0 for cells in which Ngprs = 0. This is not necessarily true. If the BSC has GPRS timeslots, even if the cells do not have traffic channels configured as PDTCHs, it may have paging traffic.
RACH_Arrivals/sec figures have been calculated using Avg_Sessions_per_user as in the call model table. GPRS_Users_BTS has been calculated based on the number of timeslots configured on the cell.

A BTS can support either 64 kbit/s RSLs or 16 kbit/s RSLs, but not both. The number of 16 kbit/s RSLs allowable is dependent on the hardware platform and some 16 kbit/s values in the tables may not be valid. 64 kbit/s RSLs must be used if the allowable number of 16 kbit/s RSLs is exceeded.

Non-standard traffic model

64 kbit/s RSLs
If the call parameters differ significantly from those given in Table 6-2, use the following formula to determine the required number of 64 kbit/s RSLs. If LCS is enabled at the BSS, LCS signaling (+ 24 * LCS) needs to be included (as shown) in the following equations. If LCS is disabled, remove (+ 24 * LCS) from the equations.

68P02900W21-S 6-22 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of RSLs required

If paging coordination (NOM I) is enabled and every cell in the BTS site has PCCCH enabled (pccch_enabled = 1):

RSL GSM@64K =

(n) * (59 + S * (25 + Size * 0.125) + 38 * H + 24 * L + 24 * L CS ) (1000 * U * T) + ((31 + 3 * C BTS ) * PGSM /(8000 * U)) * (N GSM_only_M S /N GSM_Capabl e_ - MS )

Otherwise:

RSL GSM@64K =

(n) * (59 + S * (25 + Size * 0.125) + 38 * H + 24 * L + 24 * L CS ) (1000 * U * T) + ((31 + 3 * C BTS ) * PGSM /(8000 * U))

If DTM feature is enabled,

RSL GSM@64K =

(n) * (59 + S * (25 + Size * 0.125) + 38 * H + 24 * L + 24 * L CS ) (1000 * U * T) + ((31 + 3 * C BTS ) * PGSM * (1 - R PS * PDTM )/(8000 * U)))

Where, RPS is the probability of MS in PS transfer mode; PDTM is the DTM penetration rate. The RSL traffic load for GPRS depends on the following factors:

PCCCH provisioning per cell. The access mechanism used on the air interface. Motorola BSCs allow use of one phase access or a Motorola proprietary enhanced one phase mechanism.

With one phase access

RSL GPRS@64K =

(32 + C BTS ) * PGPRS

8000 * U

* (PCCCH _ BTS) +

5.5 * GPRS _ RACH / sec * (1 R PCCCH _ Cells _ in _ BTS ) 1000 * U

With enhanced one phase access

Enhanced One Phase is not supported with EGPRS carriers.

RSL GPRS@64K =

* (PCCCH _ BTS) + 8000 * U 7.5 * GPRS _ RACH / sec * (1 R PCCCH _ Cells _ in _ BTS ) 1000 * U

(32 + C BTS ) * PGPRS

68P02900W21-S 01 Feb 2007 6-23

Determining the number of RSLs required

Chapter 6: BSC planning steps and rules

Therefore, the total number of 64 kbit/s RSLs required is:

RSL GSM + GPRS @ 64 k = Roundup(RSL GSM @ 64 k + RSL GPRS @ 64 k )

When all cells in the BTS have PCCCH enabled then RSLGPRS@64k = 0.

16 kbit/s RSLs
If the call parameters differ significantly from those given in Table 6-2, use the following formula to determine the required number of 16 kbit/s RSLs. If LCS is enabled at the BSS, LCS signaling (+ 24 * LCS) needs to be included (as shown) in the following equations. If LCS is disabled, remove (+ 24 * LCS) from the equations. If paging coordination (for example NOM I) is enabled and every cell in the BTS site has PCCCH enabled (pccch_enabled = 1): RSLGSM@16K={(n)*(59+S*(25+Size*0.125)+38*H+24*L+24*LCS)/(1000*U*T)+((31+3*C BTS)*PGSM/(8000*U))*(NGSM_only_MS/NGSM_Capable_-MS) }*4 Otherwise: RSLGSM@16K={(n)*(59+S*(25+Size*0.125)+38*H+24*L+24*LCS)/(1000*U*T)+(31+3*CBTS)*PGSM/(8000 *U) }*4 When DTM is enabled, RSLGSM@16K={(n)*(59+S*(25+Size*0.125)+38*H+24*L+24*LCS)/(1000*U*T)+(31+3*CBTS)*PGSM*(1RPS*PDTM)/(8000*U) }*4 Where, RPS is the probability of MS in PS transfer mode; PDTM is the DTM penetration rate.

With one phase access

RSL GPRS@16k = GPRS _ RACH / sec (32 + C BTS ) * PGPRS * (PCCH _ BTS) + * (1 R PCCH _ Cells _ In _ BTS ) * 4 8000 * U 1000 * U

With enhanced one phase access

Enhanced One Phase is not supported with EGPRS carriers.

68P02900W21-S 6-24 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of RSLs required

RSL

GPRS@64K

= / sec

(7 . 5 * GPRS _ RACH (32 + C BTS ) * P GPRS * (PCCCH _ BTS ) + 8000 * U 1000 * U (1 R PCCCH _ Cells _ In _ BTS )
Therefore, the total number of 16 kbit/s RSLs required is: RSLGSM+GPRS@16k = Round up (RSLGSM@16K + RSLGPRS@16k)

) *

*4

When all cells in the BTS have PCCCH enabled then RSLGPRS@16k = 0.

GPRS RACH arrivals

The average number of RACH arrivals per second is given by:

GPRS _ RACH / sec =

GPRS _ Users _ BTS * Avg _ Session _ per _ user 3600

RACH/sec depends on the traffic profile on the network. For the same amount of data transferred per user in a busy hour, if the traffic is predominantly WAP, then the number of RACH arrivals is high compared to what is observed when the data traffic is predominantly FTP transfers. The traffic profile should be calculated based on the applications running on the network. With the introduction of the Interleaving TBF feature, it is expected that the sessions arrival rate in each cell may potentially be higher than in GSRs before GSR6. With interleaving, TBFs it is possible to have multiple MSs on each timeslot. Customers should consider this fact when estimating the sessions for the formula. In the equations:
Where Is

RSLGSM + GPRS n S SMSSIZE H

the number of BSC-BTS signaling links. the number of TCHs at the BTS site. the ratio of SMSs to calls. the average size of the SMS message (payload only). the number of handovers per call.
Continued

68P02900W21-S 01 Feb 2007 6-25

Determining the number of RSLs required

Chapter 6: BSC planning steps and rules

Where

Is

L LCS U T PGSM PGPRS CBTS GPRS_RACH/sec GPRS_Users_BTS Avg_Sessions_per_user

the location update factor. the number of LCSs per call. the percent link utilization (example 0.25). the average call duration. the GSM paging rate in pages/second. the GPRS paging rate in pages/ second. the number of cells at the BTS. the number of RACH arrivals/ second/BTS. the number of GPRS users on the BTS. the average number of sessions per user in a busy hour. This includes the sessions required for signaling (attach, detach, PDP context activation/ deactivation, routing area updates, and so on). the number of mobiles in the system that do not support GPRS. Equals 0, if all cells in the BTS have PCCCH enabled, otherwise, this equals 1. the ratio of PCCCH-enabled cells at the BTS (the number of cells at the BTS with PCCCH enabled divided by the total number of cells at the BTS). Percentage of Capable Mobiles using DTM DTM Mode Scaling Factor probability that a sub is in DTM mode probability that a sub is in dedicated mode probability that a sub is in Packet transfer mode Busy Hour Call Attempts Per Sub number of handovers per call GSM circuit-switched paging rate in pages per second
Continued

NGSM_Only_MS PCCCH_BTS

RPCCCH_Cells_in_BT

PDTM DTM_Mode_Scaling_Factor RDTM RCS RPS BHCA_per_sub H PGSM

68P02900W21-S 6-26 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of RSLs required

Where

Is

RAU PDPACT/DEACT PSATT/DETACH CellUpdate T ULRate DLRate Total_subs_per_BSS T ULRate DLRate Total_subs_per_BSS

routing area update PDP context activation/deactivation (per sub/BH) PS attach/detach rate (per sub/BH) cell updates (per sub/BH) call duration Traffic per sub/BH (kbytes/hr) Uplink Traffic per sub/BH (kbytes/hr) Downlink the total users under a BSS in the busy hour call duration Traffic per sub/BH (kbytes/hr)Uplink Traffic per sub/BH (kbytes/hr) Downlink the total users under a BSS in the busy hour

The Enhanced Scheduling feature introduces a new parameter percent_traf_cs, which secures a portion of the bandwidth on the RSL for Circuit Switched (CS) traffic. The default value of this parameter is 55%, which means that GPRS traffic cannot utilize more than 45% of the total RSL bandwidth, that is, 45% of the total link capacity (16 k or 64 k). Setting percent_traf_cs to zero implies pre-GSR7 conditions, that is, CS and GPRS have equal privileges to occupy the RSL. Normal RSL planning does not recommend exceeding a MEAN of 25% RSL utilization. Hence, the thresholds for this parameter are to be triggered under abnormal conditions, where unexpected sustained surge occurs. Assuming that during a surge of traffic (much higher than the planned 25%) the ratio of CS to GPRS traffic is maintained, the default value (55%) for percent_traf_cs can be adjusted to reflect it. Take an example where total RSL MEAN utilization is 25%, and the ratio of CS to GPRS traffic 4 to 1. In other words, CS contributes 20% to RSL utilization and GPRS contributes 5%. Maintaining the same ratio during a surge suggests to set percent_traf_cs to 80%, meaning that GPRS cannot occupy more than 20% of total RSL bandwidth.

BSC to BTS E1 interconnect planning actions

Determine the number of E1 links required to connect to a BTS. Redundant links are added, if required. To determine the impact of different coding schemes on interconnect planning, use the following equation:

{[( N BSC BTS =

nE GPRS i=0

RTF _ DSO _ COUNTi ) + ( nC

31

GPRS

* 4 ) + ( nG GPRS * 2 ) + L16 / 4 ]} + L 64

68P02900W21-S 01 Feb 2007 6-27

Determining the number of RSLs required

Chapter 6: BSC planning steps and rules

Where

Is

NBSC-BTS nEGPRS nCGPRS

the minimum number of E1 links required (rounded up to an integer). the number of carriers with EGPRS enabled. the number of carriers with GPRS CS3 and CS4 enabled and GSM voice only carriers where the half rate exception case applies. the number of carriers with GPRS CS1 and CS2 enabled and GSM voice only carriers where the half rate exception case does not apply. the number of 16 kbit/s RSLs (LAPD links). the number of 64 kbit/s RSLs (LAPD links). value of rtf_dso_count for the RTF.

nGGPRS

L16 L64 RTF_DSO_COUNTi

This formula includes both L16 and L64 to provide the necessary number of RSLs. As, either L16 or L64 RSL can be used to a single BTS, but not both.
Table 6-7 defines the backhaul required for the different coding schemes and configurations. Table 6-7 Backhaul requirements 16 kbit/s 32 kbit/s VersaTRAU backhaul

GSM Voice only carries where the half rate exception case does not apply. Carriers with only GPRS CS1 and CS2 enabled.

GSM Voice only carriers where the half rate exception case does apply. Carriers with only GPRS CS1, CS2, CS3, and CS4 enabled.

EGPRS capable carriers (MCS1-MCS9).

All EGPRS carriers (pkt_radio_type = 3) use VersaTRAU frame formats on the backhaul between BTS and PCU to carry the data for PDTCHs on this carrier irrespective of whether VersaTRAU is restricted/unrestricted.

BSC to BTS E1 interconnect planning example

Assume a three sector BTS with 8 carriers per sector. Each sector has:

2 carriers of GSM voice with no half rate exception. 1 carrier with GPRS CS1 and CS2. 2 carriers of GSM voice with half rate exception. 2 carriers of GPRS CS1, CS2, CS3, CS4. 1 carrier of EGPRS, VersaTRAU is restricted and all EGPRS RTFs are non-BCCH.

68P02900W21-S 6-28 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of RSLs required

The number of E1s is calculated as follows:

No.E1s =

{[(3 * 8) + (12 * 4) + (9 * 2) + 0] + 1} =3 31

In this example, 3 E1s are required to backhaul this BTS to the BSC. To find out the total number of E1s required for a BSC, all of the BTSs backhaul requirements would require to be calculated and then added together. Refer to the network configuration to determine if backhaul from multiple BTSs could be multiplexed on a single E1. Examples of this type of capability would be if:

The BTSs are daisy chained, The network uses cross connect equipment between BTSs and BSCs.

The same example is presented in a scenario where VersaTRAU is unrestricted. We again have a 3 sector BTS with 8 carriers per sector. Each sector has:

2 carriers of GSM voice with no half rate exception. 1 carrier with GPRS CS1 and CS2. 2 carriers of GSM voice with half rate exception. 2 carriers of GPRS CS1, CS2, CS3, and CS4. 1 carrier of EGPRS, VersaTRAU is unrestricted and RTF backhaul is set to 5.

The number of E1s would be calculated as follows:

No.E1s =

{[(3 * 5) + (12 * 4) + (9 * 2) + 0] + 1} =3 31

In this example, 3 E1s are required to backhaul this BTS to the BSC. To find out the total number of E1s required for a BSC, all of the BTSs backhaul requirements would require to be calculated and then added together.

Determining the number of LCF GPROCs for RSL and GSL processing BSC to BTS E1 interconnect planning actions
Determine the number of GPROCs required to support the layer 3 call processing.

Both GPROC2 and GPROC3 or a combination of the two can perform layer 3 call processing for GSM and GPRS (GPROC3 is a direct board level replacement for GPROC2). See Generic processor (GPROC) later in this chapter. The calculations are performed separately for the number of GPROCs required for GSM traffic and for GPRS traffic. The LCF GPROCs can simultaneously handle signaling traffic from both the GSM and GPRS parts of the network. It is possible to calculate the GPRS/EGPRS part of the signaling load for the LCF GPROCs in fractional increments. The GPRS/EGPRS LCF GPROC requirements can be directly added to the GSM requirements in order to determine the total number of LCF GPROCs to equip at a BSC.

68P02900W21-S 01 Feb 2007 6-29

Determining the number of RSLs required

Chapter 6: BSC planning steps and rules

GSM layer 3
There are two methods for calculating this number. The first is used when the call parameters are like those listed in Table 6-2 (standard traffic model). The second method is used when the call parameters differ significantly from those listed in the tables (that is non-standard traffic model).
Standard traffic model (without LCS)

Use the formula: GL3 = n/693+B/20+C/120

Where Is

GL3 n B C
Non-standard traffic model

the number of LCF GPROCs required to support the layer 3 call processing. the number of TCHs at the BSC (see half rate assumptions earlier in this chapter). the number of BTS sites. the number of cells.

If the call parameters differ significantly from those given in Table 6-2, the alternative formula given should be used to determine the recommended number of LCFs. GL3 = n*(1+0.35*S+0.34*H*(1-0.4*i)+0.32*L+0.35*Lcs)/(19.6*T) + (0.00075*PGSM+0.004)*B+C/120 When DTM is enabled and network-paging coordination is disabled (not in NOM1), GL3 = n*(1+0.35*S+0.34*H*(1-0.4*i)+0.32*L+0.35*Lcs)/(19.6*T) + (0.00075*PGSM*(1RPS*PDTM)+0.004)*B+C/120 Where, RPS is the probability of MS in PS transfer mode; PDTM is the DTM penetration rate. The formula has been calculated using 70% mean utilization of the GPROC.
Where Is

GL3 n S H i L LCS T PGSM B

the number of LCF GPROCs required to support the layer 3 call processing. the number of TCHs under the BSC (see half rate assumptions earlier in this chapter). the ratio of SMSs to calls. the number of handovers per call. the ratio of intra-BSC handovers to all handovers. the location update factor. the number of LCSs per call. the average call duration. the GSM paging rate in pages per second. the number of BTS sites.
Continued

68P02900W21-S 6-30 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of RSLs required

Where

Is

C LCS T PGSM B C

the number of cells. the number of LCSs per call. the average call duration. the GSM paging rate in pages per second. the number of BTS sites. the number of cells.

Having calculated the LCF GPROCs for RSLs, ensure that the traffic is evenly distributed across the LCFs. This can be difficult in cases where large sites are being used, and in such cases additional LCFs are required. Alternatively, use the formula for traffic channels on each LCF. If the calculated value exceeds 1, the sites should be redistributed on the other available LCFs, or additional LCFs should be equipped.

GPRS layer 3
The MSC can send GSM alerting pages to a GPRS/EGPRS mobile that operates in class A or class B modes. The significance of this is that GPRS/EGPRS mobile stations capable of class A and B operation create a larger population of GSM capable mobile stations that should be considered when provisioning the LCF GPROCs. The planning information provided here should be used for this provisioning.
GL3_GPRS = 0.002 * Total_RACH/sec * (1-RPCCCH_Cells) + 0.00075 * B * PGPRS * PCCCH_BSS

Where

Total _ Rach / sec =

GPRS _ subs _ per _ PCU * Avg _ session _ per _ subs 3600

Is

Where

GL3_GPRS Total_RACH/sec RPCCCH_Cells

the sum of all GPRS RACH arrivals at the BSC. the number of TCHs under the BSC (see Half rate assumptions earlier in this chapter). the ratio of PCCCH-enabled cells (the number of cells in the BSS with PCCCH enabled divided by the total number of cells in the BSS. the number of BTS sites. 0 if all cells in the BSS have PCCCH enabled, otherwise = 1. paging rate in pages per second. the total number of GPRS users under a PCU in the busy hour. the average number of sessions per subscriber in a busy hour (includes sessions for signaling).

B PCCCH_BSS PGPRS GPRS_subs_per_PCU Avg_session_per_subs

68P02900W21-S 01 Feb 2007 6-31

Determining the number of MTLs required

Chapter 6: BSC planning steps and rules

Determining the number of MTLs required

Introduction
MTLs carry signaling traffic between the MSC and BSC. BSC supports MTL with 64kbit/s and 2Mbit/s. The number of required MTLs depends upon the BSS configuration size and traffic model. 64kbit/s MTLs are carried on E1 links between the MSC and BSC, which are also used for traffic. HSP MTLs are only supported on E1 links.

HSP MTL (High Speed MTL) is part of Huge BSC feature to provide 2M MTL capacity. When it is deployed, GPROC3-2 is required to host HSP LCF. Only one HSP MTL can be supported on a GPROC3-2 board. Mix configuration of 64kbit/s and HSP MTLs is not supported.

Planning considerations
The following factors should be considered when planning the links from the BSC to MSC:

Determine traffic requirements for the BSC. Traffic is determined using either of the following methods:
o

Multiply the number of subscribers expected to use the BSC by the average traffic per subscriber. Total the traffic potential of each BTS under the BSC, determined by the number of TCHs available, the number of TCHs required or the subscriber potential.

or
o

Determine the number of trunks to support the traffic requirements of the BSC using Erlang B tables at the required blocking rate. Determine the MTL loadshare granularity to be used for the BSC. MTL loadshare granularity determines the number of logical links that is mapped onto the physical links. Setting the mtl_loadshare_granularity database element to 1 results in a more even distribution of traffic across the MTL links. This feature allows a more gradual increase in the number of MTLs required with the increased traffic load on the BSC. Determine if LCS is enabled in the BSS and which LCS architecture is supported by the BSC. The BSC can support either NSS-based LCS architecture or BSS-based LCS architecture, but not both.

68P02900W21-S 6-32 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of MTLs required

For example, with an increase in the number of MSC-BSC trunks from 1550 to 1600, with 20% link utilization, the number of 64k MTLs required for a BSC goes up from 8 to 16, if using a granularity of 0. When using a granularity of 1, only 10 64k MTLs is required. This results from the enhanced load sharing of 64k MTLs and illustrates the difference between setting the load share granularity to 0 and 1 respectively. Table 6-8 and Table 6-9 illustrate the difference between setting the loadshare granularity to 0 and 1 for 64k MTL. Table 6-10 and Table 6-11 illustrate the difference between setting the loadshare granularity to 0 and 1 for HSP MTL. Load share granularity of 0 means 16 logical links mapped to equipped physical MTL links. Load share granularity of 1 means 64 logical links mapped to equipped physical MTL links. These calculations are for the MTLs required from the BSS perspective, using the BSS planning rules. If the MSC vendor supplies their own planning rules for a given configuration, the more conservative MTL provisioning figures should be used. If the MSC vendor does not provide the planning rules for the MTLs required in a downlink direction, then use a load share granularity of 0 to be conservative in MTL provisioning. Load sharing of MTLs in the downlink direction depends on the mechanism used by the MSC to load share the signaling links from the MSC to BSC.

Standard traffic model

The number of MSC to BSC signaling links (MTL) required depends on the desired link utilization, the type, and capacity of the GPROCs controlling the MTLs and the MTL loadshare granularity. The BSS software distributes call-signaling traffic across 16 or 64 logical links, which are then evenly spread across the active MTLs.

From GSR8, GPROC3s are required in the BSP slots. {28337} For GSR9, GPROC3-2 is required at BSC for supporting HSP MTL. There is only one HSP MTL per GPROC3-2 board.

CCITT C7 uses a 4-bit number, the Signaling Link Selection (SLS), generated by the upper layer to load share message traffic among the in-service links of a link set. When the number of in-service links is not a power of 2, some links experience a higher load. The BSS supports distribution of signaling in the uplink direction, over 64 logical links. The BSS evenly distributes the 64 logical links over the active MTLs. The number of MTLs is a function of the number of MSC to BSC trunks or the offered call load and signaling for the call load. Table 6-8 and Table 6-9 give the recommended minimum number of MSC to BSC signaling links based on the typical call parameters, detailed in Table 6-2. The value for N is the greater of the following:

The offered call load (in Erlangs) from all the BTSs controlled by the BSC. The potential carried load (approximately equal to the number of MSC to BSC trunks).

The offered call load for a BSS is the sum of the offered call load from all of the cells of the BSS. The offered call load at a cell is a function of the number of TCHs and blocking. As blocking increases, the offered call load also increases. For example, for a cell with 15 TCHs and 2% blocking, the offered call load is 9.01 Erlangs.

68P02900W21-S 01 Feb 2007 6-33

Determining the number of MTLs required

Chapter 6: BSC planning steps and rules

Before setting the load share granularity to 1, it is recommended that confirmation is gained from the Motorola local contact, or local office, that the switch is compatible with the load share granularity set to 1.
Table 6-8 and Table 6-9 show how to estimate the number of 64k MTLs to be used for the BSC, with 20% and 40% link utilization, respectively. Table 6-8 Number of MSC and BSC signaling links without LCS (20% utilization) N = the greater of number of MSC-BSC trunks or the offered load from the BTSs Number of MTLs with 16 logical links Minimum required With redundancy Number of MTLs with 64 logical links Minimum required With redundancy

N <= 85 85< N <=170 170 < N <= 350 350 < N <= 450 450 < N <= 660 660< N

4 6 8 16 16 16

5 7 9 16 16 16

4 6 8 11 13 16

5 7 9 12 14 16

Table 6-9 Number of MSC and BSC signaling links without LCS (40% utilization) N = the greater of number of MSC-BSC trunks or the offered load from the BTSs Number of MTLs with 16 logical links Minimum required With redundancy Number of MTLs with 64 logical links Minimum required With redundancy

N <= 85 85< N <=170 170 < N <=350 350 < N <= 520 520 < N <= 880 880< N <=1000 1000< N <= 1200 1200< N <= 1500 1500< N

2 3 4 6 8 16 16 16 16

3 4 5 7 9 16 16 16 16

2 3 4 6 8 10 11 13 16

3 4 5 7 9 11 12 14 16

Table 6-10 shows how to estimate the number of 2M HSP MTLs to be used for the BSC, with 20% link utilization.

68P02900W21-S 6-34 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of MTLs required

Table 6-10 Number of MSC and BSC signaling links without LCS (20% utilization) N=the greater of number of MSCBSC trunks or the offered load from the BTSs Number of MTLs with 16 logical links Minimum required With redundancy Number of MTLs with 64 logical links Minimum required With redundanc y

N<=1227 1227<N<=2773 2773<N<=3804 3804<N<=4179 4179< N<=4800

1
2 3 4 4

2 3 43 5 5

1 2 3 3 4

2
3 4 4 5

The capacities shown in Table 6-8, Table 6-9 and Table 6-10 are based on the standard traffic model shown in Table 6-2. It is recommended that the C7 links be designed to operate at no more than 20% link utilization when the 64k MTL is running on a GPROC1 and no more than 40% utilization when the MTL/LMTL is running on a GPROC2 or GPROC3/GPROC3-2. Before use of the 40% utilization for GPROC2 or GPROC3/GPROC3-2, it is imperative that the operator verifies if the MSC vendor can also support 40% utilization at the MSC end. If not, then only 20% link utilization should be used for GPROC2 and GPROC3/GPROC3-2. It is required the HSP MTLs be designed to operate at no more than 20% utilization.

Non-standard traffic model for 64k MTL

If the call parameters differ significantly from those given in Table 6-2, the following procedure is used to determine he required number of 64k DS0 MSC to BSC signaling links:

Use the formula to determine the maximum number of Erlangs supported by a C7 signaling link (nlink).

n link =

1000* U *T 40 + S* (26 + 0.125*SMSSIZE) + 24* H *(1 0.83*i) + 24* L + CICS * LCS + 9* PPC

Use the formula to determine the maximum number of Erlangs supported by a GPROC (LCF-MTL) supporting a C7 signaling link (nlLCF-MTL).

nl LCFMTL =

20* T (1 + 0.16*S + 0.5 * H * (1 0.6 * i) + 0.42* L + 0.45* L CS + PPC * (0.005 * B + 0.05))

The maximum amount of traffic an MTL (a physical link) can handle (nlmin) is the smaller of the two numbers from.

nl min = MIN(n link , nl LCF _ MTL )

68P02900W21-S 01 Feb 2007 6-35

Determining the number of MTLs required

Chapter 6: BSC planning steps and rules

Signaling over the A-interface is uniformly distributed over some logical links. The number of logical links is defined on the BSC by database parameter mtl_loadshare_granularity = 0 or 1, which corresponds to 16 or 64 logical links, respectively, over which the MTL signaling is load shared. Hence, the total amount of traffic that a logical link would hold, is calculated as:

N log ical =

N Ng

Next we require to determine the number of logical links each MTL (physical link) can handle

n log_ per _ mtl = rounddown(

nl min ) N log ical

Finally, the number of required MTLs (mtls) is:

mtls = roundup(

Ng n log_ per _ mtl

) + R 16

mtls should not exceed 16 per BSC.

The formula to determine the maximum number of Erlangs supported by a GPROC (LCF-MTL) has been calculated using 70% mean utilization of GPROC2 (see Calculate the number of LCFs for MTL processing later in this section). Suggest to maintain the mean utilization of GPROCs at or 70%.

Non-standard traffic model for HSP MTL

If the call parameters differ significantly from those given in Table 6-2, the following procedure is used to determine the required number of MSC to BSC HSP signaling links:

Use the formula to determine the maximum number of Erlangs supported by a C7 signaling link (nlink).

n link =

31000 * U*T 40+ S*(26+ 0.125*SMS SIZE) + 24* H * (1 0.83*i) + 24* L + CICS * LCS + 9 * PPC

Signaling over the A-interface is uniformly distributed over some logical links. The number of logical links is defined on the BSC by database parameter mtl_loadshare_granularity = 0 or 1, which corresponds to 16 or 64 logical links, respectively, over which the MTL signaling is load shared. Hence, the total amount of traffic that a logical link would hold, is calculated as:

N log ical =

N Ng

68P02900W21-S 6-36 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of MTLs required

Next we require to determine the number of logical links each MTL (physical link) can handle

n log_ per _ mtl = rounddown (

n link ) N log ical

Finally, the number of required MTLs (mtls) is:

mtls = roundup(

Ng n log_ per _ mtl

Is:

) + R 16

Where:

U T S SMSSIZE H i L Clcs LCS PPC B mtls round up round down MIN Ng R

the percent link utilization (for example 0.20). call hold time. the ratio of SMSs per call. the average size of the SMS message (payload only). the number of handovers per call. the ratio of intra-BSC handovers to all handovers. the location update factor. 26 for NSS-based architecture. 31 for BSSbased architecture. the number of LCSs per call. the number of pages per call. the number of BTSs supported by the BSC. the number of MTLs required round up to the next integer. round down to the next integer. the minimum of two values. the number of logical links (16 or 64). the number of redundant MTLs.

68P02900W21-S 01 Feb 2007 6-37

Determining the number of MTLs required

Chapter 6: BSC planning steps and rules

Calculate the number of LCFs for MTL processing

The purpose of the MTL LCF GPROC is to support the functions of MSC link protocol.

Both GPROC2 and GPROC3 or a combination of the two can perform MTL processing (GPROC3 is a direct board level replacement for GPROC2). See Generic processor (GPROC) later in this chapter. It is not recommended that an LCF supports both MTLs and RSLs. It is not permitted for a LCF to support both MTLs and LMTLs.

LCFs for 64k MTL links

Since one LCF GPROC can support two 64k MTLs, the number of required LCFs is:

N LCF = Roundup(

mtls ) 2

However, if the traffic model does not conform to the standard model: If

2 * n link > nl LCF MTL , then N LCF = mtls mtls ) 2

Otherwise,

N LCF = Roundup(

LCFs for HSP MTL links

Since one GPROC3-2 LCF can support one HSP MTL, the number of required LCFs is the number of HSP MTLs.

N LCF = mtls
Where Is

NLCF ROUND UP mtls nlink nlLCF-MTL

the number of LCF GPROCs required. rounding up to the next integer. calculated in the previous section. calculated in the previous section. calculated in the previous section.

68P02900W21-S 6-38 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of MTLs required

MSC to BSC signaling over a satellite link

The BSC supports Preventive Cyclic Retransmission (PCR) to interface to the MSC over a satellite link. PCR retransmits unacknowledged messages when there are no new messages to be sent. This puts an additional processing load on the GPROC (LCF-MTLs) controlling the C7 signaling links. It is recommended that when PCR is used, that the number of MTLs (and thus the number of LCF-MTLs) be doubled from the number normally required.

68P02900W21-S 01 Feb 2007 6-39

Determining the number of LMTLs required

Chapter 6: BSC planning steps and rules

Determining the number of LMTLs required

Introduction
LMTLs carry the LCS signaling traffic between the BSC and the SMLC. This is only applicable for BSSbased LCS architecture when LCS is enabled in the BSS. The number of required LMTLs depends upon the BSS configuration size and traffic model. LMTLs are carried on E1 between the SMLC and BSC.

Planning considerations
The following factors require to be considered when planning the number of LMTL links from the BSC to the SMLC:

Determine the LCS traffic requirements of the BSC. A BSC can only connect to one SMLC.

Determining the number of LMTLs

Traffic model
The number of required LMTLs depends upon the BSS configuration size and traffic model. See Table 6-1, Table 6-2 and Table 6-4.

LMTL number
Use the following formula to determine the required number of 64 kbit/s LMTLs (rounded up to the next integer):

LCS_ BSC_ Rate *19 L LMTL = Roundup 1000 * U BSC _ SMLC

Where Is

LLMTL LCS_BSC_Rate UBSC_SMLC ROUND UP

the number of BSC to SMLC signaling links. requests number per BSC per second. the percentage of the link utilization. rounding up to the next integer.

68P02900W21-S 6-40 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of LMTLs required

BSC to SMLC interconnection planning actions

Determine the number of E1 links required to connect to a SMLC. Redundant links are added, if required.

L LMTL N BSC-SMLC = Roundup 31

Where Is

NBSC-SMLC ROUND UP

the minimum number of E1 links required (rounded up to an integer). rounding up to the next integer.

The BSC-SMLC signaling link LLMTL can only be terminated on an E1.

Calculate the number of LCFs for LMTL processing

The purpose of the LMTL LCF GPROC is to support the functions of the SMLC link protocol. For the LCF GPROC, one dedicated LCF-LMTL is required for processing LMTLs.

Both GPROC2 and GPROC3 or a combination of the two can perform LMTL processing (GPROC3 is a direct board level replacement for GPROC2). See Generic processor (GPROC) later in this chapter. From GSR8, if the LMTL functionality is assigned to the BSP, a GPROC3 is required. It is not recommended that an LCF supports both LMTLs and RSLs. It is not permitted for a LCF to support both MTLs and LMTLs.

68P02900W21-S 01 Feb 2007 6-41

Determining the number of XBLs required

Chapter 6: BSC planning steps and rules

Determining the number of XBLs required

Introduction
XBLs carry the signaling traffic between the BSC and RXCDR. The number of XBL links required depends upon the number of CICs and/or the number of Ater interface channels. Planning considerations The following factors require to be considered when planning the number of XBL links from the BSC to the RXCDR:

Determine the traffic requirements of the BSC and/or the number of trunks (CICs) used between the BSC and RXCDR. Determine the mode (backward compatibility or auto-connect/ enhanced auto connect) in which the BSC and RXCDR operate. See Chapter 2 for a description of the modes. A maximum of 20 XBLs (64 kbit/s or 16 kbit/s) can be configured for a BSC/RXCDR. A BSC can connect to a maximum of 10 RXCDRs and vice-versa.

Determining the number of XBLs

The calculations should be performed for every connected RXCDR. The number of XBL links depends on the number of trunks on the BSC-RXCDR interface and whether the auto-connect mode or enhanced auto-connect mode is enabled at the RXCDR/BSC. Table 6-11 details the minimum number of XBLs required to support the given number of trunks between the BSC and RXCDR, with auto-connect mode or enhanced auto-connect mode.
Table 6-11 Number of BSC to RXCDR signaling links N = number of MSC to BSC trunks No redundancy Number of 64 kbit/s XBLs Number of 16 kbit/s XBLs With redundancy Number of 64 kbit/s XBLs Number of 16 kbit/s XBLs

N 1200 1200 < N 2400 2400 < N 3200 3200 < N <=4800

1 2 3 4

4 8 11 16

2 4 6 8

8 16 22* 32*

* This exceeds the 20 XBL limit and is therefore not a valid configuration. It is recommended that the XBL link utilization does not exceed 40%. This allows a link to double the capacity (to 80%) under fault conditions (in some configurations). 80% utilization, queuing delays could become substantial. Although both auto-connect mode and enhanced auto-connect mode apply a load, it is the enhanced auto-connect mode load that can vary depending on system configuration. When operating in this mode, the XBL link utilization should be monitored to determine if additional capacity is required. The number of XBL links as shown is a minimum number that are required, regardless of measured utilization. This is due to peak usage requirements during start up and reconfigurations due to faults and maintenance. XBL link utilization is a network statistic, calculated on a per XBL basis.

68P02900W21-S 6-42 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of XBLs required

Standard traffic model

The minimum number of XBL links required as given in Table 6-11 was verified using a standard set of call parameters. These are given in Table 6-12.
Table 6-12 Typical call parameters relating to XBLs Parameter Value

Link utilization Call duration Average XBL message size XBL messages per new call * XBL messages per full rate <-> half rate handover Full rate <-> half rate handovers per call

40% 90 s 50 bytes 1 1 1

* Mobile origination, mobile termination, hand-in from MSC.

Non standard traffic model

If the call parameters differ significantly from those given in Table 6-12, use the following formula to determine if the required number of 64 kbit/s XBLs (rounded up to the next integer) should be adjusted:

XBL = (N / T ) * (M newcell + M handover * H f r hr ) * L XBL * 8 64000 * U BSC-RXCDBC

Use the following formula to determine if the required number of 16 kbit/s XBLs (rounded up to the next integer) should be adjusted:

(N / T ) * (M newcell + M handover * H f r hr ) * L XBL * 8 XBL = *4 64000 * U BSC-RXCDBC

Where Is

XBL N T Mnewcall Mhandover Hfr-hr LXBL U(BSC-RXCDR)

the number of BSC to RXCDR signaling links. the number of MSC-BSC trunks. the average call duration in seconds. the number of XBL messages per new call. the number of XBL messages per hr <-> fr handover. the number hr <-> fr handovers per call. the average length of a XBL message in bytes. the percentage link utilization (0.40, for example).

68P02900W21-S 01 Feb 2007 6-43

Determining the number of XBLs required

Chapter 6: BSC planning steps and rules

Double the number if redundancy is desired. The number of XBLs required is then the larger of the number as determined by the formula and the number given in Table 6-11.

68P02900W21-S 6-44 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of GSLs required

Determining the number of GSLs required

Planning considerations
In GSR9, the connection between PCU and BSC can be E1 and/or Ethernet link. Ethernet links and E1 links can be equipped simultaneously in the system. When only E1 is used, PCU needs one E1 in order to carry GSL signaling, and a second E1 for redundancy. In this configuration, PCU can support up to 30 primary GSL 64 kbit/s timeslots and 30 redundant. Each 64 kbit/s timeslot is one LAPD channel. It is recommended that two GSL E1 links per PCU are provisioned for resilience purposes, even when the GSL is lightly loaded. When Ethernet link is used, maximum of 30 GSL 64kbit/s timeslots can be carried by one Ethernet link. In the following configuration, up to 60 GSL 64kbit/s timeslots can be supported in the system:

Only Ethernet links are used; Ethernet and E1 links are used simultaneously.

GSL provision should be load-balanced over multiple links, as the mechanism for providing resiliency against link failures. The number of GSLs required is calculated as follows:
GSL = MAX (GSLrun_time, GSLinit_time)

The requirement for the number of GSLs during system initialization (GSLinit_time) is 6. Each GSL message consists of three parts: LAPD protocol, BSS executive header protocol, and the application message carrying actual signaling information. The LAPD and BSS protocol parts can be considered messaging overhead. In addition, in a similar manner to RSL, the GSL traffic depends on the access mechanism used on the Air interface. The calculation for the required number of GSL links during runtime (after the system stabilizes) is as shown . GSLrun_time= GSLPaging+GSLRACH When DTM is enabled, GSLrun_time= (GSLPaging+GSLRACH) *DTMGSL_overhead Where, DTMGSL_overhead=103%. With one phase access, there is additional loading on the RSL and GSL due to enhanced one phase messaging and immediate assignment messages for UL TBF setups. When DTM feature is unrestricted, the network planner need consider the additional loading on the GSL due to DTM paging coordination and new introduced signaling messages.
With one phase access

GSL RACH = 1 R PCCH _ Cells * Total _ RACH / sec* 5.5 1000 * U

68P02900W21-S 01 Feb 2007 6-45

Determining the number of GSLs required

Chapter 6: BSC planning steps and rules

With enhanced one phase access

Enhanced One Phase is not supported with EGPRS carriers.

GSL RACH = 1 R PCCH _ Cells * Total _ RACH / sec* 7.5 1000 * U

Where:

Total _ RACH / sec = GPRS _ subs _ per _ PCU * Avg _ session _ per _ subs 3600
GPRS paging is performed per routing area (RA). A GPRS page is sent to all cells within the RA. If PCCCH is enabled at a cell then the GPRS page is sent to that cell on the GDS TRAU link. The GSL requirements for GPRS paging is given by the following:

GSL Paging = 8.5 * PGPRS * No _ LCFs _ for _ RSL * PCCCH _ BSS 1000 * U
Where Is

GSL GSLinit_time GSLrun_time PGPRS Total_RACH/sec U GPRS_subs_per_PCU Avg_session_per_subs

the number of 64 kbit/s LAPD GSL timeslots to provision. the number of GSLs required for system initialization. the number of GSLs required for signaling while the system is stable. the GPRS paging rate in pages per second. the sum of all GPRS RACH arrivals on the BSC. the link utilization, typically 0.25. the total GPRS users under a PCU in the busy hour. the average number of sessions per subscriber in a busy hour (this includes sessions for signaling).
Continued

68P02900W21-S 6-46 01 Feb 2007

System Information: BSS Equipment Planning

Determining the number of GSLs required

Where

Is

RPCCCH_Cells

the ratio of PCCCH-enabled cells (the number of cells with PCCCH enabled divided by the total number of all cells in the BSS). the number of LCF boards in the BSC that terminate RSL links. = 0 if all cells in the BSS have PCCCH enabled, otherwise = 1 Percentage of Capable Mobiles Using DTM. DTM Mode Scaling Factor. probability that a sub is in DTM mode. probability that a sub is in dedicated mode. probability that a sub is in Packet transfer mode. Busy Hour Call Attempts Per Sub. number of handovers per call. GSM circuit-switched paging rate in pages per second. routing area update. PDP context activation/deactivation (per sub/BH). PS attach/detach rate (per sub/BH). cell updates (per sub/BH). call duration. Traffic per sub/BH (kbytes/hr) Uplink. Traffic per sub/BH (kbytes/hr) Downlink. the total users under a BSS in the busy hour.

No_LCFs_for_RSL PCCCH_BSS PDTM DTM_Mode_Scaling_Factor RDTM RCS RPS BHCA_per_sub H PGSM RAU PDPACT/DEACT PSATT/DETACH CellUpdate T ULRate DLRate Total_subs_per_BSS

68P02900W21-S 01 Feb 2007 6-47

Determining the number of GSLs required

Chapter 6: BSC planning steps and rules

Load balancing
When applying even distribution of GSLs terminated on LCFs, the GSL traffic is load balanced over all GSLs. Furthermore, should more than one GSL terminate on a LCF, the load is balanced over these GSLs. The general rule of thumb is to terminate at least one GSL on a SITE LCF in a heavily loaded system to avoid unnecessary LAN traffic. In sysgen, the gsl_lcf_mapping parameter determines if the BSS automatically distributes the GSLs to different LCFs (Auto mode) or if the operator should specify the LCF (Manual mode) that terminates the GSL. In Auto mode, the user is not prompted for the LCF during the equipage of the GSL and the system distributes the GSLs as evenly as possible on the LCFs In Manual mode, the user is prompted for an LCF during the equipage of the GSL. AUTO mode of gsl_lcf_mapping is only valid in sysgen. Outside of sysgen, gsl_lcf_mapping is always set to MANUAL. Should the operator require to specify LCFs outside of sysgen mode or wish to configure the system manually, the GSLs should be evenly distributed among the LCFs that terminate the RSLs. The operator can choose to distribute manually the GSLs, but it is recommended to use a similar approach - evenly distribute among LCFs carrying RSL traffic. Although it is not necessary, the operator can chose to consider the total count of PDTCHs on each LCF and assign more GSLs to those LCFs having more PDTCHs.

68P02900W21-S 6-48 01 Feb 2007

System Information: BSS Equipment Planning

Generic processor (GPROC)

Generic processor (GPROC)

GPROC nomenclature
For the purposes of this manual only and to avoid confusion between different versions of the generic processor (GPROC), the following nomenclature is used:
GPROC1 specifically refers to the original GPROC. GPROC2 specifically refers to the GPROC2. GPROC3 specifically refers to the GPROC3. GPROC3-2 specifically refers to the GPROC3 phase2. GPROC is used in this manual as a non-specific term referring to both GPROC2, GPROC3 and GPROC3-2.

Introduction
Generic processor (GPROC) boards are used throughout the Motorola BSS as a control processor. This section describes the BSC GPROC types and their functions. The BSC configuration type and GPROC device type are essential factors for BSC planning. The GPROC3/GPROC3-2 is a high performance direct replacement for GPROC2s and GPROC1s. This allows for any combination of GPROC types to be installed except in the BSP slots where a GPROC3/GPROC3-2 is required. GPROC3s/GPROC3-2s cannot be used with software versions earlier than GSR7. In GSR9, one GPROC3-2 is required in order to support each HSP MTL.

GPROC functions and types

GPROCs are assigned functions and are then known by their function names. The GPROC is the basic building block of a distributed architecture. The GPROC provides the processing platform for the BSC. By using multiple GPROCs, software tasks can be distributed across GPROCs to provide greater capacity. The set of tasks that a GPROC is assigned, depends upon the configuration and capacity requirements of the BSC. Although every GPROC of the same type (1, 2, or 3) is similar from a hardware standpoint, when a group of tasks are assigned to a GPROC, it is considered to be a unique GPROC device type or function in the BSC configuration management scheme. There are a limited number of defined task groupings in the BSC, which result in the naming of four unique GPROC device types for the BSC. The processing requirement of a particular BSC determines the selection and quantity of each GPROC device type. The possible general task groupings or functions for assignment to GPROCs are:

BSC common control functions. OMC-R communications - OML (X.25) including statistics gathering. MSC link protocol (C7).

68P02900W21-S 01 Feb 2007 6-49

Generic processor (GPROC)

Chapter 6: BSC planning steps and rules

SMLC link protocol (C7). BSS Layer 3 call processing (BSSAP) and BTS link protocol, RSL (LAPD). LAPD-type GDS link protocol, GSL. Cell broadcast centre link (CBL). Base Site Control Processor (BSP). Link Control Function (LCF). Operations and Maintenance Function (OMF). Code Storage Facility Processor (CSFP).

The defined GPROC devices and functions for the BSC are as follows (also see Table 6-13):

At a combined BSC BTS site, the BTF and DHP are additional GPROC function and type in the network element.
Table 6-13 defines the GPROC types/functions for different software releases. Table 6-13 GPROC type/function Software Release BSP MTL-LCF LMTLLCF RSL-LCF OMF CSFP

GSR7 GSR 8 onwards GSR9

GPROC2 or GPROC3 GPROC3 GPROC3 or GPROC3-2

GPROC2 or GPROC3 GPROC2 or GPROC3 GPROC2 or GPROC3 or GPROC3- 2

GPROC2 or GPROC3 GPROC2 or GPROC3 GPROC2 or GPROC3 or GPROC3- 2

GPROC2 or GPROC3 GPROC2 or GPROC3 GPROC2 or GPROC3 or GPROC3- 2

GPROC2 or GPROC3 GPROC2 or GPROC3 GPROC2 or GPROC3 or GPROC3- 2

GPROC2 or GPROC3 GPROC2 or GPROC3 GPROC3 or GPROC3-2

When the enhanced BSC capacity feature and AMR (and/or GSM half rate) are used together, it is mandatory for a GPROC3/GPROC3-2 to be installed in the BSP slot at the BSC. Otherwise, replacing a GPROC2 with a GPROC3/GPROC3-2 in the BSP slot is at the discretion of the user. From GSR8, a GPROC3/GPROC3-2 is mandatory in the BSP capable slots. {28337}For GSR9, GPROC3-2 is required for hosting HSP MTL LCF in BSC.

68P02900W21-S 6-50 01 Feb 2007

System Information: BSS Equipment Planning

Generic processor (GPROC)

GPROC3/GPROC3-2 planning assumptions

The following assumptions are made regarding planning GPROC3 and GPROC3-2 usage:

GPROC3/GPROC3-2 processing performance is improved, when compared with GPROC2. A GPROC3/GPROC3-2 is required in the BSP slots. In GSR9, only GPROC3/GPROC3_2 can be used as CSFP. {28337} A GPROC3-2 is required for supporting each HSP MTL. The GPROC3/GPROC3-2 can be used for other board functions besides BSP in the BSC only as a board level replacement. Replacement is not mandatory for these functions. The GPROC3 does not provide any capacity and performance improvements in terms of number of links or sites supported. The only difference is that an operator sees lower processor utilizations. The GPROC3/GPROC3-2 can be used as board level replacement for GPROC2 and GPROC1 at a BTS. It is not mandatory for any function. The GPROC3/GPROC3-2 can be used as board level replacement for GPROC2 at the RXCDR. It is not mandatory for any function.

BSC types
The BSC is configured as one of two types; the type is determined by the GPROCs present.
BSC type 1 o

Master GPROC Running the base site control processor (BSP) and carrying out operations and maintenance functionalities.

Link control processor (LCF) Running the radio-signaling link (RSL) and layer 3 processing or MTL/LMTL (C7 signaling link) communications links. It also runs the GSLs for GPRS signaling between the BSC and PCU.

BSC type 2 o

Master GPROC Running the BSP LCF OMF Running the O&M, including statistics collection, and OML link (X.25 control links to the OMC-R signaling link) communications links. It also runs the GSLs for GPRS signaling between the BSC and PCU.

o o

68P02900W21-S 01 Feb 2007 6-51

Generic processor (GPROC)

Chapter 6: BSC planning steps and rules

BSC type 2 o

Master GPROC Running the BSP LCF OMF Running the O&M, including statistics collection, and OML link (X.25 control links to the OMC-R).

o o

Planning considerations
The following factors should be considered when planning the GPROC complement:

BSP limitation From GSR8, it is mandatory to deploy GPROC3s/GPROC3-2 in any potential BSP slot in the site, both active and standby (that is, slot 20 and 24 in shelf 0 and slot 20 in shelf 1).

Each BSC needs:

o o o o o o

One master GPROC3/GPROC3-2 (BSP). One OMF (if it is a type 2 BSC). Some LCFs for MTLs, see Link control function . One dedicated LCF for LMTL (if LCS is enabled and the BSS LCS architecture is supported). LCFs to support the RSL and control of the BTSs. LCFs to support the GSLs for GPRS signaling between the BSC and PCU. One redundant master GPROC3/GPROC3-2 (BSP). At least one redundant pool GPROC (covers LCFs). An optional dedicated CSFP. For GSR9, it is mandatory to deploy GPROC3/GPROC32 for CSFP.

Optional GPROCs include:

o o o

A maximum of eight GPROCs can be supported in a BSU shelf. For redundancy, each BSC should be equipped with a redundant BSP controller and an additional GPROC3/GPROC3-2 to provide redundancy for the signaling LCFs. Where multiple shelves exist, each shelf should have a minimum of two GPROCs to provide redundancy within that shelf.

68P02900W21-S 6-52 01 Feb 2007

System Information: BSS Equipment Planning

Generic processor (GPROC)

Link control function

The following factors should be considered when planning the number of LCFs:

MTLs are assigned to dedicate LCFs. LMTLs are handled by one dedicated LCF. HSP MTL can only be supported by GPROC3-2. A single GPROC LCF can process up to 800 active calls if the ssm_critical_overload_ threshold is set to 100. The default value is 80, meaning that the 641st non-emergency call is rejected (80% x 800 = 640 active calls). Refer to Technical Description: BSS Command Reference (68P02901W23) for further details. For optimum performance, GSL handling should be distributed among the LCFs that terminate RSLs. (See Load balancing in the previous section.)

Combining MTL and RSL processing on a single GPROC is not recommended. The planning rules for LCFs using GPROCs are:

A single GPROC supports two MTLs each working at 20% link utilization. However, if the link utilization is higher, the actual number of MTLs supported per LCF depends on the Erlangs supported per LCF and MTL for that particular call model. A single GPROC3-2 supports one HSP MTL working at 20% link utilization. If any LCF does not satisfy the criteria, either rebalancing of sites on the available LCF GPROCs at the BSC is required or additional LCF GPROCs are required to be equipped at the BSC to process the traffic load. The link utilization of a RSL should not exceed 25%. A single GPROC can support up to 12 GSLs. This is set by the GPROC max_gsls parameter. Up to 25 LCFs can be supported. A maximum of 31 BTS sites can be controlled by a single LCF. All RSLs (LAPD links) for the BTSs terminate on the same GPROC, so if return loops are used, then the maximum number of BTS sites is 15 (if GPROC_slots = 32). If GPROC_slots is set to 16 then at the most 15 RSLs may exist which would support up to 7 BTS sites, and if GPROC_slots is set to 24 then at the most 23 RSLs may exist, supporting up to 11 BTS sites.

The number of serial links per GPROC must be determined. The current values are 16, 24 or 32 with 16 being the default value. One link is reserved for each board (for GPROC test purposes) so the number of available serial links is 15, 23 or 31. However, when the links are running at high load, the GPROC experiences some performance problems when terminating 31 links. Hence, the use of more than 23 links per board is not recommended.

Setting GPROC_slots = 24 allows for additional LAPD links up to the recommended maximum without the timeslot under-utilization associated with a GPROC_slots setting of 32.

68P02900W21-S 01 Feb 2007 6-53

Generic processor (GPROC)

Chapter 6: BSC planning steps and rules

Cell broadcast link

The cell broadcast link (CBL) connects the BSC to the cell broadcast centre. For typical applications (less than ten messages per second), this link can exist on the same LCF as that used to control BTSs. The CBL should not be controlled by an LCF MTL (a GPROC controlling an MTL).

OMF GPROC required

The BSC type 2 configuration offloads many of the O&M functions and control of the interface to the OMC-R from the BSP. One of the major functions offloaded from the BSP is the central statistics process. It is recommended to equip an OMF.

Code storage facility processor

The BSS supports a GPROC acting as the code storage facility processor (CSFP). The CSFP allows preloading of a new software release while the BSS is operational. When software is upgraded from GSR8 to GSR9, it is mandatory to deploy GPROC3/GPROC3-2 for CSFP. If a dedicated GPROC is to exist for the CSFP, an additional GPROC is required. When Horizon II macro, Horizonmacro or M-Cell BTSs are connected to the BSC, a dedicated CSFP is required at the BSC and a second dedicated CSFP should be equipped for redundancy. The BSS supports a method whereby a dedicated CSFP GPROC is not required. This method is implemented using the configure_csfp command and works as follows: The system can borrow certain devices and temporarily convert them into a CSFP, and when the CSFP functionality is no longer needed the device can be converted back into its previous device. The devices the system can borrow are a redundant BSP/BTP or a pooled GPROC3-2. This functionality allows an operator who already has either a redundant BSP/BTP or a pooled GPROC3-2 in service to execute a command from the OMC-R to borrow the device and convert it into a CSFP. The operator can then download the new software load or database and execute a CSFP swap. Once the swap has been completed and verified as successful, the operator can return the CSFP back to the previous redundant or pooled device type through a separate command from the OMC-R. See Technical Description: BSS Command Reference (68P02901W23) for more details on the configure_csfp command.

GPROC redundancy
BSP redundancy
A failure of the BSP GPROC3/GPROC3-2 causes a system outage. If the BSC is equipped with a redundant BSP GPROC3/GPROC3-2, the system restarts under the control of the redundant BSP GPROC3s. If the BSC is not equipped with a redundant BSP and the BSP GPROC3/GPROC3-2 was to fail, the BSC would be inoperable. The BSC Reset Management feature is enabled by default. This feature provides fast switchover between master and redundant BSP processors in the event of a BSP failure. This reduces the outage time from 10 to 20 minutes to less than 2 minutes.

68P02900W21-S 6-54 01 Feb 2007

System Information: BSS Equipment Planning

Generic processor (GPROC)

Pooled GPROCs for LCF and OMF redundancy

The BSS supports pooled GPROCs for LCF and OMF redundancy. By equipping additional GPROCs for spares, if an LCF or the OMF GPROC were to fail, the system software automatically activates a spare GPROC from the GPROC pool to replace the failed GPROC.

GPROC pre-emption
The GPROC pre-emption function searches for a Busy-Unlocked (B-U) GPROC running a lower priority function when a GPROC hosting a higher priority function goes out of service and there are no EnabledUnlocked (E-U) GPROCs to host the higher priority function. If such a GPROC is found, the lower priority function is pre-empted by the higher priority function. The BSS uses the function type and function ID to determine the order in which functions are brought into service. The order of function type is OMF first, LCF second and BTF third. The function with the lower ID is of higher priority than that of the function with the higher ID. Functions with lower IDs are brought into service before functions with higher IDs. This priority scheme allows the operator to arrange functions in the order of importance. The operator can configure the pre-emption algorithm using a database element as follows: chg_element pool_gproc_pre_emption <value> 0 Value=0: No pre-emption. Value=1: Function level pre-emption. If a function of lower priority is running on a GPROC, that function is pre-empted. In the case of a pre-empted LCF, the LCF with the highest function ID is pre-empted. OMF can pre-empt LCF. Value=2: Intra function level pre-emption. OMF cannot pre-empt LCF. If a function of lower priority is running on a GPROC, that function is pre-empted. If a GPROC running an LCF goes out of service and there is no lower priority function type (for example BTF) running on a pool GPROC, then the function tables are searched for a lower priority LCF to pre-empt. The default value is 1. From GSR9, with the introduction of HSP MTL, the pre-emption algorithm is altered. GPROC type is considered more important than the LCF ID. The priority order is as given below:

OMF: When OMF needs to pre-empt or camp on other GPROCs, it selects the GPROC based on the following order:
o o

{FR28398}If the Increased Network Capacity Feature is unrestricted, the order is GPROC3 > GPROC2 > GPROC3-2. {FR28398} If the Increased Network Capacity feature is restricted, the order is GPROC3-2 > GPROC3 > GPROC2.

HSP LCF (LCF when configured with max_mtls = 31). This can only be supported on GPROC 3-2. Standard LCF (LCF when configured with max_mtls = 0, 1 or 2). This can be MTL LCF or LCF for SITEs. BTF

When GPROC pre-emption occurs, service on lower priority GPROC should be terminated. In order to minimize service interruption, following are suggested for GPROC planning:

Equip redundant GPROC for pooled GPROC. Assign lowest priority to LCF which serves least traffic. Equip HSP MTL LCF before other Standard LCF.

68P02900W21-S 01 Feb 2007 6-55

Generic processor (GPROC)

Chapter 6: BSC planning steps and rules

Recommendations for High-Availability:

To reach high availability, GPROC redundancy for BSP (1+1), MTL_LCF (N+1), RSL_LCF (N+1) and other functions (OMF, CSFP, LMTL) (N+1) are recommended. To achieve medium availability, GPROC redundancy for BSP(1+1), MTL_LCF, RSL_LCF, CSFP, OMF, LMTL, (N+1) are recommended. The worst cases and lowest availability is only one GPROC spare for BSP redundancy.

The table lists Availability predictions for three distinct redundant alternatives for a huge BSC configuration. Alternative (1) offers the best availability and relies on resource pools with over provisioning for both LCF functionalities, that is, both the MTL-LCF and RSL-LCF pool have their own extra GPROC boards to provide the best resilience to the pool. These extra boards are kept active and load-balance their respective pool load. The CSFP, OML, and LMTL active/standby configurations share a common spare. Hence, four spare GPROC boards are required in this configuration: 1 GPROC3/GPROC3-2 for BSP, 1 GPROC3-2 for MTL-LCF and 2 GPROC2 for the other functions. Alternative (2) represents an intermediate solution were a common spare is provided as backup of the CSFP, OML, LMTL, MTL-LCF pool, and RSL-LCF pool. Because of the MTL-LCF computational requirements, this common spare board should be a GPROC3-2 board. Alternative (3) represents the worst-case scenario were the only redundant component is the BSP.
Table 6-14 BSS configurations and their availability BSC Configurations Availability

Act/Sby BSP, 3+1 MTL-LCF, 19+1 RSL-LCF, Act/Sby CSFP, Act/Sby OML, Act/Sby LMTL (1) Act/Sby BSP, 3:1 MTL-LCF, 19:1 RSL-LCF, Act/Sby CSFP, Act/Sby OML, Act/Sby LMTL (2) Act/Sby BSP, 3+0 MTL-LCF, 19+0 RSL-LCF, Simplex CSFP, Simplex OML, Simplex LMTL (3)

99.9978% 99.9974% 99.9921%

GPROC planning actions

Determine the number of GPROCs required.

Where

Is

NGPROC B L C R

the total number of GPROCs required. the number of BSP GPROC3s/GPROC3-2 the number of LCF GPROCs. the number of CSFP GPROC3s/GPROC3-2. the number of pool GPROCs (for redundancy).

68P02900W21-S 6-56 01 Feb 2007

System Information: BSS Equipment Planning

Generic processor (GPROC)

If dedicated GPROCs are required for either the CSFP or OMF functions then they should be provisioned separately.

68P02900W21-S 01 Feb 2007 6-57

Transcoding

Chapter 6: BSC planning steps and rules

Transcoding
Introduction
Transcoding reduces the number of cellular subscriber voice/data trunks required by a factor of four. When (AMR or GSM) half rate is in use and 8 kbit/s subrate switching is available and (for AMR only) the 7.95 kbit/s half rate codec mode is not included in the Half Rate Active Codec Set, the reduction factor for the half rate calls becomes eight. In most configurations, half rate is used only for part of the time, thus yielding a reduction factor of less than eight. If transcoding takes place at the switch using an RXCDR, the number of links between the RXCDR and the BSC is reduced to approximately one quarter (less when half rate is employed under the conditions described) of the number of links between the RXCDR and the MSC. The GDP2 can process 60 channels of FR, EFR, AMR, GSM HR, and Phase 2 data services and is capable of terminating two E1 links from the MSC. It can also function as a replacement for the GDP. The capacity of one BSU shelf is 12 MSI slots, six of which contain a transcoder (XCDR), generic digital processor (GDP), enhanced digital processor (EGDP), or generic digital processor 2 (GDP2); this limitation is due to power constraints. An RXU shelf can support up to 16 GDP/XCDR/EGDP/GDP2s and typically provides a better solution of the transcoding function for larger commercial systems. The GDP2 is used to 60 channel capacity in the BSU shelf, and when used in the new RXU3 shelf and BSSC3 cabinet (within the RXCDR, enhanced capacity mode must be enabled to access the second E1 when GDP2s are used). The existing RXU shelf has only one E1 per transcoder slot, therefore the GDP2 cannot be used to its full capacity in the existing RXU shelf (the GDP2 supports only 30 channels when used in the RXU shelf). Refer to the section Overview of remote transcoder planning in Chapter 7, RXCDR planning steps and rules. An EGDP is a new development of the GDP board, used to support AMR. Due to the additional transcoding requirements of AMR, each of the 15 DSPs on the GDP board is only capable of supporting the transcoding function for a single channel of GSM speech (AMR, FR, and EFR) and Phase 2 data services. To offer 30 channels of enhanced transcoding using the same E1 span line to the MSC, enhanced GDPs are equipped as pairs, each providing half of the transcoding resources. This results in an overall reduction in capacity equivalent to 30 channels per GDP pair. Use of an EGDP is practical only when used in conjunction with AMR. The EGDP does not support GSM half rate. The EGDP can also terminate one Abis E1 link, thus reducing the number of MSIs boards required (see EGDP provisioning). Due to the ability of the GDP2 to function as a GDP, it can replace one or both of the GDPs in the EGDP configuration. This is not an optimal use of the GDP2 and is most likely to occur in emergency situations (for example, board replacement). As a result, it is not considered in the planning procedures. The MSC recommends a particular codec type or types to be used on a call-by-call basis. It sends the BSC a preference-ordered list, based on such factors as MS capabilities and user configuration. When the MSC is capable of choosing the MSC-RXCDR trunk (CIC) based upon the preferred codec type, a mix of transcoding equipment can be used. If this capability (called circuit pooling) is not present, then some equipment combinations can result in non-optimal behavior. When circuit pooling is available in an AMR enabled system, both AMR capable (EGDP/GDP2) and nonAMR capable (XCDR/GDP) equipment can be used. If circuit pooling is not present, GDP2s or EGDPs should be used exclusively to prevent downgrading or blocking of calls.

68P02900W21-S 6-58 01 Feb 2007

System Information: BSS Equipment Planning

Transcoding

When AMR is employed and both XCDR/GDPs and EGDP/GDP2s are present (and circuit pooling is present at the MSC), there must be sufficient GDP2 and EGDP equipment available to handle the expected AMR traffic. The proportion of AMR capable transcoding circuits versus non-AMR capable transcoding circuits should be no less than the proportion of AMR capable MSs versus non-AMR capable MSs. A safety factor of no less than 20% is recommended (20% allows for some variation in the actual number and allows for a period of growth in AMR capable MS penetration before having to add more AMR transcoding ability). Each AMR half rate call needs one (AMR) transcoder circuit. Lack of an available AMR circuit could cause a call to be downgraded to another codec type or possibly blocked. When GSM half rate is employed and a mix of XCDRs and GDP/GDP2s are present, a similar situation exists. However, due to the early introduction into the standards of GSM half rate, most mobile are expected to be GSM half rate capable. Since a CIC is not tied to any particular voice channel, circuit pooling is rendered ineffective, as there is no way to predict which mobiles require GSM half rate. It becomes necessary to update all transcoding to support GSM HR in order to guarantee GSM half rate can be used when needed. Without this upgrade, calls on non-GSM HR capable CICs remain on a full rate channel. When GSM half rate and AMR are both in use and a combination of AMR transcoding equipment (EGDP, GDP2) and GSM half rate transcoding equipment (GDP, GDP2) exist, circuit pooling is most effective when choosing AMR CICs (EGDP, GDP2) for AMR capable mobiles, and the remaining CICs for nonAMR capable mobiles. Ideally, for AMR capable mobiles the MSC would first select a CIC attached to an EGDP, followed by one attached to a GDP2. For a non-AMR capable mobile the MSC would first select a CIC attached to a GDP, followed by one attached to a GDP2. The selection of the proper CIC (circuit pool) is dependent upon the capability of the connected MSC.

GDP/XCDR/EGDP/GDP2 planning considerations

The following factors should be considered when planning the GDP/XCDR/EGDP/GDP2 complement:

A XCDR can process 30 voice channels (E1), supports GSM Full Rate speech (GSM FR), uplink/downlink volume control and is capable of terminating one E1 link from the MSC. A GDP can process 30 voice channels (E1), supports GSM FR, enhanced Full Rate speech (EFR), GSM half rate speech (GSM HR), uplink/downlink volume control and is capable of terminating one E1 link from the MSC. An EGDP consists of a pair of GDP cards, a primary and a secondary. Each EGDP can process 30 channels of GSM FR, EFR, AMR (FR and HR) speech and Phase 2 data services, and terminates one E1 link from the MSC.

GSM HR is not supported on an EGDP.

The primary GDP of an EGDP terminates the E1 interface to the MSC. The secondary GDP of an EGDP terminates an E1 interface to the BTS. See EGDP provisioning. The GDP2 can process 60 channels of FR, EFR, AMR (FR and HR), GSM HR, and Phase 2 data services and is capable of terminating two E1 links from the MSC. It can also function as a replacement for the GDP. XCDRs, GDPs, EGDPs, and GDP2s can co-exist in a shelf.

68P02900W21-S 01 Feb 2007 6-59

Transcoding

Chapter 6: BSC planning steps and rules

The proportion of AMR-capable circuits (GDP2/EGDP) to non AMR-capable circuits (XCDR/GDP) should be sufficient to handle the expected AMR traffic. The master MSI slot(s) should always be populated to enable communication with the OMC-R. The master MSI slot contains an XCDR/GDP/EGDP (see NOTE) /GDP2, if the OML goes through the MSC. The A-interface must terminate on the XCDR/GDP/EGDP (either the primary or secondary) /GDP2. An XCDR card is incompatible with a GPROC3/GPROC3-2 in the BSP slots. XCDRs must be replaced with GDP/GDP2s.

EGDP provisioning
The secondary GDP of an EGDP can use the E1 connection to terminate an Abis link. This reduces the need for MSIs and makes more efficient use of the available TDM timeslots. The (secondary) GDP has one E1 interface (instead of two for an MSI), which must be taken into account in site (MSI) planning.
Figure 6-2 and Figure 6-3 show the EGDP used in configurations with and without the additional E1 termination in use respectively. Figure 6-2 EGDP configuration with the additional E1 termination in use

68P02900W21-S 6-60 01 Feb 2007

System Information: BSS Equipment Planning

Transcoding

Figure 6-3 EGDP configuration without the additional E1 termination in use

Planning actions for transcoding at the BSC

Planning transcoding at the BSC must always be performed as it determines the number of E1 links for the A interface. This text should be read in conjunction with the BSS planning diagram, Figure 6-1.

Using E1 links
The minimum number of E1 links required for the A-interface is the greater of the two calculations that follow (fractional values should be rounded up to the next integer value). N = C2M+ T/30 N = C2M + (C64k+X+T)/31

68P02900W21-S 01 Feb 2007 6-61

Transcoding

Chapter 6: BSC planning steps and rules

2M MTL and 64kbit/s MTL cannot be supported simultaneously.

Where Is

N C64k C2M X T

the minimum number of E1 links required. the number of 64kbit/s MTL links (C7 signaling links) to the MSC. the number of HSP MTL (if HSP MTL feature is unrestricted) to the MSC the number of OML links (X.25 control links to the OMC-R) through the MSC. the number of trunks between the MSC and the BSC (see Figure 6-1).

Each XCDR/GDP/EGDP can terminate one E1 link. Each GDP2 can terminate two E1 links (when used in a BSU or RXU3 shelf (enhanced capacity mode must be enabled within the RXCDR to access the second E1 when GDP2s are used)). The equipment can be mixed within the following calculation:

N = X GE + 2 * G2
Where Is

N XGE G2

the minimum number of E1 links required. the number of XCDR/GDP/EGDPs. the number of GDP2s.

Verify that the number of AMR circuits is sufficient to handle the expected AMR traffic. If necessary, adjust the number of EGDP/GDP2s. The following formula is used to determine the percentage of AMR capable circuits:

%AMRcircuits =

GDP 2 * 60 + EGDP * 30 * 100 GDP 2 * 60 + EGDP * 30 + XCDR * 30 + GDP * 30

Count primary and secondary EGDPs as one EGDP in the equation.

68P02900W21-S 6-62 01 Feb 2007

System Information: BSS Equipment Planning

Multiple serial interface (MSI)

Multiple serial interface (MSI)

Introduction
A multiple serial interface provides the interface for the links between a BSSC cabinet and other network entities in the BSS, BSC to BTS and BSC to RXCDR. An MSI can interface only E1 links.

Planning considerations
The following factors should be considered when planning the transcoder complement:

Each MSI can interface two E1 links.

A MSI card is compliant with G703 (1998).

Each E1 link provides 31 usable 64 kbit/s channels. Redundancy for the MSI depends on the provisioning of redundant E1 links connected to the site. The master MSI slot(s) should always be populated to enable communication with OMC-R.

If the OML links go directly to the MSC, the master slot should be filled with a XCDR/GDP/EGDP (primary or secondary)/GDP2, else the slot should be filled with an MSI, which terminates the E1 link carrying the OML link to the OMC-R. These E1 links do not require to go directly to the OMC-R, they can go to another network element for concentration. {22169} With the introduction of the 96 MSI feature, the MSI with OML can be configured with priority in the database to make sure that the MSI is available in either single rate or enhanced capacity mode. {28337} When the HSP MTL feature is unrestricted, the E1 links used to carry HSP MTL should be taken into account. There are two connected modes. In the first connection mode, the E1 links go to the MSC through the RXCDR. The impact of this mode of connection on the RXCDR can be found in Chapter 7. In the second connection mode, the E1 links go to the MSC directly. Both the modes impact E1 planning in BSC.

MSI planning actions

If local transcoding is used then the NBSC-RXCDR element in the following equations can be ignored, otherwise refer to Chapter 7, RXCDR planning steps and rules for the determination of the NBSCRXCDR element.

68P02900W21-S 01 Feb 2007 6-63

Multiple serial interface (MSI)

Chapter 6: BSC planning steps and rules

With E1 links
Determine the number of MSIs required.
Without LCS:

N MSI =

( N BSC BTS + N BSC RXCDR + N GDS TRAU + N GSL E1 ) 2

With LCS for BSS-based LCS architecture:

N MSI =

( N BSC BTS + N BSC RXCDR + N BSC SMLC + N GDSTRAU + N GSL E1 ) 2

The BSC-SMLC signaling link LMTL terminates only on an E1.

68P02900W21-S 6-64 01 Feb 2007

System Information: BSS Equipment Planning

Packet Subrate Interface (PSI2)

Packet Subrate Interface (PSI2)

Introduction
The PSI2 card introduced in GSR9 is used to connect BSC to PCU with Ethernet connectivity. The physical interface from the card is a 1000BASE-T over 4 pairs of copper wire. This same connection can be operated in 100BASE-TX mode of operation as well. The standard backplane connections can be used, with a PBIB or PT43 board replacing the BIB or T43 board, respectively, at the top of the cabinet. The new interconnect board (PBIB or PT43) at the top of the BSC cabinet allows a single RJ45 Ethernet connection instead of 2 span lines for one of the supported MSI positions.

Planning consideration
The following factors should be considered when planning the equipage of PSI2 cards:

Each PSI2 connects PXP in PCU with Ethernet link. Every PSI2/PXP pair provides an Ethernet link, which can carry both GSL and GSD TRAU simultaneously. Each BSC cage can be typically equipped with 2 PSI2 cards when KSW and KSWXs are used and 3 PSI2 cads when DSW2 and DSWX are used. They occupy MSI slots 6,7,12 and 13. There are up to 12 PSI2 cards in a BSC site. A PSI2 can support 64 to 320 usable 64kbit/s TDM channels. Redundancy for PSI2 depends on the provisioning of redundant Ethernet links connected with PXP in PCU.

PSI2 planning actions

The number of PSI2 cards required is dependent on planning of the PXP boards in PCU (Refer to Chapter 8).

68P02900W21-S 01 Feb 2007 6-65

Kiloport switch (KSW) and double kiloport switch (DSW2)

Chapter 6: BSC planning steps and rules

Kiloport switch (KSW) and double kiloport switch (DSW2)

Introduction
The kiloport switch (KSW) card provides digital switching for the TDM highway of the BSC. The double kiloport switch (DSW2) is an enhanced version of the KSW, which supports twice the number of ports (enhanced capacity mode), as well as extended subrate switch capability of 8 kbit/s (extended subrate switching capability). Use of 8 kbit/s subrate switching can reduce backhaul costs when used in conjunction with the AMR or GSM half rate feature.

Planning considerations
The following factors should be considered when planning the KSW/DSW2 complement:

A minimum of one KSW/DSW2 is required for each BSC site. The KSW, or DSW2 not in enhanced capacity mode, has a capacity of 1024 x 64 kbit/s ports or 4096 x 16 kbit/s ports, which can be expanded by adding up to three additional KSW/DSW2s,giving a total switching capacity of 4096 x 64 kbit/s ports or 16384 x 16 kbit/s ports. When operating in enhanced capacity mode, the DSW2 has a capacity of 2048 x 64 kbit/s ports or 8192 x 16 kbit/s ports, which can be expanded by adding up to three additional DSW2s,giving a total switching capacity of 8192 x 64 kbit/s ports or 32768 x 16 kbit/s ports. When operating in extended subrate switching mode (but not enhanced capacity mode), the DSW2 can further switch 8192 x 8 kbit/s ports which can be expanded by adding up to three additional DSW2s, giving a total switching capacity of 32768 x 8 kbits/s ports. When operating in extended subrate switching mode and enhanced capacity mode, the DSW2 can further switch 16384 x 8 kbit/s ports which can be expanded by adding up to three additional DSW2s, giving a total switching capacity of 65536 x 8 kbits/s ports. Eight (64 kbit/s) timeslots per KSW/DSW2 are reserved by the system for test purposes and are not available for use. A mix of KSWs and DSW2s needs that the DSW2s are not operated in the enhanced capacity mode. For redundancy, duplicate all KSWs/DSW2s. In mixed configurations (KSWs and DSW2s), KSWs can be redundant to DSW2s and vice-versa. Verify that each KSW or DSW2 that is not in enhanced capacity mode uses no more than 1016 ports, or that each DSW2 in enhanced capacity mode uses no more than 2040 ports (8 ports are used internally). The devices in a BSC that need TDM timeslots are:
o o o

GPROC1 = 16 timeslots. GPROC2 or GPROC3, GPROC3-2= 32, 24 or 16 timeslots. GDP or XCDR (or GDP2 acting as a GDP replacement) = 16 timeslots.

68P02900W21-S 6-66 01 Feb 2007

System Information: BSS Equipment Planning

Kiloport switch (KSW) and double kiloport switch (DSW2)

o o o o

EGDP = 96 timeslots. GDP2 = 24 timeslots. MSI = 64 timeslots. PSI2 = tdm_ts_blocks timeslots *32 (64 ~ 320 timeslots).

The tdm_ts_blocks is a database parameter used to set the number of TDM timeslots blocks. One block contains 32 TDM timeslots. When the PXP (the partner of PSI2) works at prp_fanout_mode 1 (refer to PXP planning considerations in Chapter 8), 5 blocks are recommended for GPRS and 9 blocks for EGPRS. When the PXP works at prp_fanout_mode2, 3 blocks are recommended for GPRS and 5 blocks are recommended for EGPRS.

There is one additional consideration with regard to timeslot usage, which is related to the timeslot allocation policy employed. Timeslots are grouped in 32 blocks of 32 timeslots each. Generally, groups of 16 (the first 16 or last 16) can be allocated within a block. However, the GDP2 is a special case, as it needs 24 timeslots, a group of 16 and another 8 out of an additional block. The remaining 8 timeslots (within the block of 16) can only be used by another GDP2. Hence, if there is an odd number of GDP2s then 8 timeslots are unusable. As each device needs at a minimum 16 timeslots, this does not have any significant effect on timeslot planning. The number of TDM timeslots is given by:
N=(G*n)+(RGDPXCDR*16)+(REGDP *96)+(RGDP2*24)+(M*64)+(RPSI2T * t) Where Is

N G n RGDPXCDR REGDP RGDP2 M RPSI2T

the number of timeslots required. the number of GPROCs. 16, 24 or 32 (depending on the value of the gproc_slots database parameter). the number of GDP/XCDRs. the number of EGDPs. the number of GDP2s. the number of MSI. the number of PSI2s 64 to 320 (depending on the value of the tdm_ts_blocks database parameter. t = tdm_ts_blocks *32).

Any BSC site, which contains a DRIM, has 352 timeslots allocated to DRIMs, irrespective of the number of DRIMs equipped.

68P02900W21-S 01 Feb 2007 6-67

Kiloport switch (KSW) and double kiloport switch (DSW2)

Chapter 6: BSC planning steps and rules

KSW/DSW2 planning actions

Calculate the minimum number of KSWs/DSW2s required per BSC:

Use this formula when enhanced capacity mode is not enabled:

N=(G*n)+(RGDPXCDR *16)+(REGDP *96)+(RGDP2*24)+(M*64)+(RPSI2T * t)/1016

Use this formula when enhanced capacity mode is enabled:

N=(G*n)+(RGDPXCDR *16)+(REGDP *96)+(RGDP2*24)+(M*64)+(RPSI2T *t)/2040 Where Is

N G n

the number of KSWs/DSW2s required. the number of GPROCs. 16, 24 or 32 (depending on the value of the gproc_slots database parameter). the number of GDP/XCDRs. the number of EGDPs. the number of GDP2s. the number of MSI. the number of GDP2s. 64~320 (depending on the value of the tdm_ts_blocks database parameter. t = tdm_ts_blocks *32)

RGDPXCDR REGDP RGDP2 M RPSI2T t

Each KSW/DSW2 has to serve the boards in its shelf and the boards of any extension shelf connected to its shelf by its TDM highway of 1016 available timeslots (or 2040 when operating in enhanced capacity mode). In case of multiple expansion shelves, the TDM highways of each shelf do not merge into a common unique TDM highway across all shelves, that is, a KSW/DSW2 in one shelf cannot serve boards in other expansion shelves. For example, in the case of a BSC consisting of two shelves each having 32 unused timeslots per KSW/DSW2 free, an additional MSI board CANNOT be added even if an MSI slot is free at each shelf, (but one GPROC per shelf can be added if one GPROC slot per shelf is free).

68P02900W21-S 6-68 01 Feb 2007

System Information: BSS Equipment Planning

BSU shelves

BSU shelves
Introduction
The number of BSU shelves is normally a function of the number of GPROCs, MSIs and XCDR/GDP/EGDP/GDP2s required.

Planning considerations
The following factors should be considered when planning the number of BSU shelves:

Each BSU shelf supports up to eight GPROCs. If the number of these exceeds the number of slots available, an additional BSU shelf is required. Each expansion shelf is allocated to a single KSW/DSW2 and extension shelves are differentiated by the presence of the KSW/DSW2. Extension shelves are those, which do not contain a primary KSW/DSW2. Shelves containing a KSW/DSW2 are called expansion shelves. An extension shelf extends the TDM highway. It is limited to the same number of (aggregate) timeslots as the shelf containing the KSW/DSW2. An expansion shelf adds an additional TDM highway. It increases the number of timeslots to that of the additional KSW/DSW2. The following capacities depend on timeslot usage. Refer to Kiloport switch (KSW) and double kiloport switch (DSW2) for information on how to determine timeslot usage.
o o

A BSU shelf can support up to 12 MSI boards. A BSU shelf can support up to six XCDR/GDP/EGDP/GDP2s (reducing the number of MSI boards appropriately).

For EGDPs, both the primary and the secondary must be counted. An XCDR card is incompatible with a GPROC3/GPROC3-2 in the BSP slots. XCDRs must be replaced with GDP/GDP2s.

68P02900W21-S 01 Feb 2007 6-69

BSU shelves

Chapter 6: BSC planning steps and rules

BSU shelf planning actions

Determine the number of BSU shelves required. The number of BSU shelves required is the highest value result of the following three calculations (fractional values should be rounded up to the next integer value):

BS =

G 8 M+R BS = 12 R BS = 6

Or Bs = (M+R+P)/12 when PSI2 cards used in BSC cage

Where Is

Bs G M R P

the minimum number of BSU shelves required. the number of GPROCs. the number of MSIs. the number of XCDR/GDP/EGDP/GDP2s (see NOTE). the number of PSI2 cards.

For EGDPs, both the primary and the secondary EGDPs must be counted. The number of timeslots equipped to each shelf must be verified. This verification procedure is like Planning considerations (the KSW/DSW2 timeslot validation prevents a shelf from exceeding the timeslot limit) and is repeated here for completeness. (G*n)+(RGDPXCDR *16)+(REGDP *96)+(RGDP2*24)+(M*64)+(RPSI2* t) <=1016
Where Is

G n RGDPXCDR REGDP RGDP2 M RPSI2T

the number of GPROCs in the shelf. 16, 24 or 32 (depending on the value of the gproc_slots database parameter). the number of GDP/XCDRs in the shelf. the number of EGDPs in the shelf. the number of GDP2s in the shelf. the number of MSIs in the shelf. the number of PSI2s 64~320 (depending on the value of the tdm_ts_blocks database parameter. t = tdm_ts_blocks *32).

68P02900W21-S 6-70 01 Feb 2007

System Information: BSS Equipment Planning

BSU shelves

When enhanced capacity mode is not enabled (non-extension shelf): (G*n)+(Rgdpxcdr*16)+(Regdp*96)+(Rgdp2*24)+(M*64)+(RPSI2* t)<=1016 When enhanced capacity mode is enabled (extension shelf): (G*n)+(Rgdpxcdr*16)+(Regdp*96)+(Rgdp2*24)+(M*64)+(RPSI2* t)<=1024 If the result of the equation exceeds the value quoted, the configuration of MSIs, GPROCs, and GDPs and PSI2s can be adjusted, or an additional shelf or shelves is required.

The number of shelves should be larger if an attempt to reduce the number of KSWs/DSW2s is made. The maximum number of shelves at a site = 8. The maximum number of cabinets at a site = 8. Horizon and M-Cell sites need only a cabinet to be equipped and not a shelf. Without {FR22169}: Although the BSC can support a maximum of 56 MSIs and each of up to 4 BSU shelves can support 12 MSIs, adding one extension shelf does not provide additional capacity for the extra 8 MSIs. With {FR22169}: The BSC can support 96 MSIs with 12 MSIs in each of the 8 cages.

68P02900W21-S 01 Feb 2007 6-71

Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)

Chapter 6: BSC planning steps and rules

Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)
Introduction
The KSWX extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in multi-shelf configurations. The KSWX is required whenever a network element expands beyond a single shelf. The DSWX performs the same function as the KSWX when used in the BSU. It is necessary when enhanced capacity mode (2048 timeslots capacity) is used. DSWXs are not required to pair with DSW2s when extended subrate switching mode is used (KSWXs can be used).

Planning considerations
The following factors should be considered when planning the KSWX/DSWX complement:

KSWXs/DSWXs are not required in a single shelf configuration (that is, when expansion or extension is not required). For redundancy, duplicate all KSWX/DSWX boards (needs redundant KSW/DSW2). In mixed configurations (KSWXs and DSWXs), KSWXs can be redundant to DSWXs and vice-versa. KSWXs/DSWXs are used in three modes:
o o o

KSWX/DSWXE (Expansion) is required to interconnect the KSWs/DSW2s for sites with multiple KSWs/DSW2s. KSWX/DSWXR (Remote) is required in shelves with KSWs/DSW2s to drive the TDM highway in shelves that do not have KSWs/DSW2s. KSWX/DSWXL (Local) are used in shelves that have KSWs/DSW2s to drive the clock bus in that shelf and in shelves that do not have KSWs/DSW2s to drive both the local TDM highway and the clock bus in that shelf.

Five of the redundant KSWX/DSWX slots are also CLKX slots. The maximum number of KSWX/DSWX slots per shelf is 18, nine per KSW/DSW2. KSWXs and DSWXs can both be used, however they should always be used with like pairs, for example DSWXs with DSWXs and KSWXs with KSWXs. Operation in enhanced capacity mode needs the use of all DSWXs (and DSW2s).

68P02900W21-S 6-72 01 Feb 2007

System Information: BSS Equipment Planning

Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)

The fiber optic cables, which are used to extend/expand the TDM highway from one BSU to another BSU, must be of the same length to limit the risk of TDM highway extension/expansion errors.

KSWX/DSWX planning actions

The number of KSWXs/DSWXs required is the sum of the KSWX/DSWXE, KSWX/DSWXL and KSWX/DSWXR.
NKX = NKXE + NKXR + NKXL NKXE = K * (K-1) NKXR = SE

When SE = 0, NKXL = 0 When SE > 0, NKXL = K + SE

Where Is

NKX NKXE NKXR K SE For example:

the number of KSWXs/DSWXs required. the number of KSWX/DSWXE. the number of KSWX/DSWXR. the number of non-redundant KSWs/DSW2s. the number of extension shelves.

Table 6-15 KSWX/DSWX (non-redundant) Extension shelves KSW/DSW2 (non redundant) 1 2 3 4

0 1 2 3 4

0 3 5 7 9

4 6 8 10 12

9 11 13 15 17

16 18 20 22 24

68P02900W21-S 01 Feb 2007 6-73

Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)

Chapter 6: BSC planning steps and rules

Table 6-16 KSWX/DSWX (redundant) Extension shelves KSW/DSW2 (redundant) 1 2 3 4

0 1 2 3 4

0 6 10 14 18

8 12 16 20 24

18 22 26 30 34

32 36 40 44 48

68P02900W21-S 6-74 01 Feb 2007

System Information: BSS Equipment Planning

Generic clock (GCLK)

Generic clock (GCLK)

Introduction
The generic clock (GCLK) generates all the timing reference signals required by a BSU.

Planning considerations
The following factors should be considered when planning the GCLK complement:

One GCLK is required at each BSC. The maximum number of GCLK slots per shelf is two. For redundancy, add a second GCLK at each BSC in the same shelf as the first GCLK.

GCLK planning actions

Determine the number of GCLKs required.
GCLKs = 1 + 1 redundant

68P02900W21-S 01 Feb 2007 6-75

Clock extender (CLKX)

Chapter 6: BSC planning steps and rules

Clock extender (CLKX)

Introduction
A clock extender (CLKX) board provides expansion of GCLK timing to more than one BSU.

Planning considerations
The following factors should be considered when planning the CLKX complement:

One CLKX is required in the first BSU shelf, which contains the GCLK when expanding beyond the shelf occurs. Each CLKX can supply the GCLK signals to six shelves. There are three CLKX slots for each GCLK, allowing each GCLK to support up to 18 shelves (LAN extension allows only fourteen shelves in a single network element). There are three CLKX slots for each GCLK, allowing each GCLK to support up to 18 shelves (LAN extension allows only fourteen shelves in a single network element). The maximum number of CLKX slots per shelf is six. (The CLKX uses six of the redundant KSWX slots.) With a CLKX, a KSWX/DSWXL is required to distribute the clocks in the master and each of the expansion/extension shelves. For redundancy, duplicate each CLKX (needs a redundant GCLK). Fiber optic cables that extending clock reference signals from the parent shelf to all other shelves and itself at a site must be of the same length to maintain site synchronization integrity.

CLKX planning actions

Determine the number of CLKXs required.

E N CLKX = ROUNDUP * (1 + R F ) 6
Where Is

NCLKX ROUND UP E RF

the number of CLKXs required. rounding up to the next integer. the number of expansion/extension shelves. redundancy factor (1 if redundancy is required (recommended), 0 for no redundancy).

68P02900W21-S 6-76 01 Feb 2007

System Information: BSS Equipment Planning

Local area network extender (LANX)

Local area network extender (LANX)

Introduction
The LANX provides a LAN interconnection for communications between all GPROCs at a site.

Planning considerations
The following factors should be considered when planning the LANX complement:

One LANX is supplied in each shelf. For full redundancy add one LANX for each shelf. The LANX can support a maximum network size of 14 shelves.

LANX planning actions

Determine the number of LANXs required.
NLANX = NBSU * (1+ RF) BSU 14 Where Is

NLANX NBSU RF

the number of LANXs required. the number of BSU shelves. redundancy factor (1 if redundancy is required (recommended), 0 for no redundancy).

68P02900W21-S 01 Feb 2007 6-77

Parallel interface extender (PIX)

Chapter 6: BSC planning steps and rules

Parallel interface extender (PIX)

Introduction
The PIX board provides eight inputs and four outputs for site alarms.

Planning considerations
The following factors should be considered when planning the PIX complement:

The maximum number of PIX board slots per shelf is two. The maximum number of PIX board slots per site is eight.

PIX planning actions

Select the number of PIXs required. PIX 2 * number of BSUs or PIX 8

68P02900W21-S 6-78 01 Feb 2007

System Information: BSS Equipment Planning

Line interface boards (BIB/PBIB, T43/PT43)

Line interface boards (BIB/PBIB, T43/PT43)

Introduction
The line interfaces, balanced-line interface board (BIB) and T43 board (T43), provide impedance matching for E1 links. The PBIB and PT43 provide an Ethernet link in addition to impedance matching for E1links.

Planning considerations
The following factors should be considered when planning the line interface complement:

Use a BIB or PBIB to match a balanced 120-ohm (E1 2.048 Mbit/s) or balanced 110-ohm 3 V (peak pulse) line. Use a T43 Board (T43) or PT43 board to match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peak pulse) line. The PBIB and PT43 are used when PSI2s exist in BSC cage. They are at the top of the BSC cabinet and replace 2 span lines with a single RJ45 connection for Ethernet. Each BIB/T43 can interface six E1links to specific slots on one shelf. Each PBIB/PT43 can interface four E1 links and one Ethernet link to specific slots on one shelf. Up to four (P)BIBs or (P)T43s per shelf can be mounted on a BSSC2 cabinet.
o o o o

A maximum of 24 E1 links can be connected to a BSU shelf. A BSSC2 cabinet with two BSU shelves can interface a maximum of 48 E1 links. A maximum of 4 Ethernet links can be connected to a BSU shelf. A maximum of 8 Ethernet links can be connected to a BSSC cabinet.

The number of E1links is reduced by 2 times the number of Ethernet links provisioned.

A BSSC3 cabinet can have up to seven (P)BIBs or (P)T43s per shelf mounted, but in the BSU configuration this additional connectivity is not needed.

68P02900W21-S 01 Feb 2007 6-79

Line interface boards (BIB/PBIB, T43/PT43)

Chapter 6: BSC planning steps and rules

(P)BIB/(P)T43 planning actions

The following planning actions are required:

Determine the number and type of link (E1) to be driven. Determine the number of Ethernet links to be driven. Determine the number of (P)BIBs or (P)T43s required. Determine the split between BIB/T43 and PBIB/PT43 boards required. Minimum number of MSIs = (Number of E1 /2). Number of PBIB/PT43 = number of PSI2s. Minimum number of BIB/T43= (number of MSIs - 2*number of PSI2s)/3.

68P02900W21-S 6-80 01 Feb 2007

System Information: BSS Equipment Planning

Digital shelf power supply

Digital shelf power supply

Introduction
A BSSC2 or BSSC3 cabinet can be supplied to operate from a +27 V dc or -48 V/-60 V dc power source.

In this manual, BSSC is a generic term that means both BSSC2 and/or BSSC3.

Planning considerations
The following factors should be considered when planning the PSU complement:

Two DPSMs are required for each shelf in the BSSC. Two IPSMs are required for each shelf in the BSSC2 (-48 V/-60 V dc). Two IPSM2s are required for each shelf in the BSSC3 (-48 V/-60 V dc). Two EPSMs are required for each shelf in the BSSC (+27 V dc). For redundancy, add one DPSM, IPSM, or EPSM for each shelf.

Power supply planning actions

Determine the number of PSUs required. PSUs = 2 * Number of BSUs + RF * Number of BSUs Where: RF is the redundancy factor (1 if redundancy is required (recommended), 0 for no redundancy).

68P02900W21-S 01 Feb 2007 6-81

Non Volatile Memory (NVM) board

Chapter 6: BSC planning steps and rules

Non Volatile Memory (NVM) board

Introduction
The optional non volatile memory board provides the BSC with an improved recovery facility following a total power loss. With the NVM board installed, data is retrieved from the NVM board rather than from the OMC-R during recovery from a total power loss.

Planning considerations
The following factors should be considered when planning the NVM complement:

Only one NVM board can be installed at the BSC. The NVM board uses slot 26 in the BSU shelf 0 (master) of the BSC, which is an unused slot. The appropriate software required to support the NVM board must be loaded at the OMC-R and downloaded to the BSC.

NVM planning actions

The NVM board is optional.

68P02900W21-S 6-82 01 Feb 2007

System Information: BSS Equipment Planning

Verifying the number of BSU shelves and BSSC cabinets

Verifying the number of BSU shelves and BSSC cabinets

Verification
After planning is complete, verify that:

The number of shelves is greater than one eighth of the number of GPROC modules. Each non-redundant KSW/DSW2 has its own shelf. Each extension shelf supports extension of a single KSW/DSW2. The number of KSWX/DSWXs, LANXs, CLKXs, and GPROCs is correct. The number of MSI, PSI2s and XCDR/GDP/EGDP/GDP2s 12 * number of shelves. The number of XCDR/GDP/EGDP/GDP2s 6 * number of shelves. The number of PSI2s <= 4 per shelf and 12 per site.

For the two calculations, the EGDP consists of a primary and a secondary board.

The number of BTS sites 100 The number of BTS cells 250 RSLs 250 Carriers 384 LCFs 25 Erlangs 3000

If the Huge BSC feature is enabled, the number of BTS sites 140 and carriers 750. If the Enhanced BSC feature is enabled, carriers 512.

If necessary, add extra BSU shelves. Each BSSC cabinet supports two BSU shelves.

68P02900W21-S 01 Feb 2007 6-83

Verifying the number of BSU shelves and BSSC cabinets

Chapter 6: BSC planning steps and rules

68P02900W21-S 6-84 01 Feb 2007

Chapter 7 RXCDR planning steps and rules

This chapter provides an overview of the manual. It also provides information on various elements of BSS, BSS planning methodology, and BSS system architecture, components and features. This chapter describes the planning steps and rules for the RXCDR in the following sections:
Overview of remote transcoder planning RXCDR to BSC connectivity RXCDR to BSC links RXCDR to MSC links Generic processor (GPROC) Transcoding Multiple serial interface (MSI) Kiloport switch (KSW) and double kiloport switch (DSW2) RXU shelves Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) Generic clock (GCLK) Clock extender (CLKX) LAN extender (LANX) Parallel interface extender (PIX) Line interfaces (BIB, T43) Digital shelf power supply Non volatile memory (NVM) board Verify the number of RXU shelves and BSSC cabinets

68P02900W21-S 01 Feb 2007 7-1

Overview of remote transcoder planning

Chapter 7: RXCDR planning steps and rules

Overview of remote transcoder planning

Introduction
The following information is required to plan the equipage of an RXCDR:

BSC traffic requirements Number of trunks (including redundancy) from the MSC Each RXCDR can support multiple BSCs The sum of the MSIs and the XCDR/GDP/EGDP/GDP2s for each BSC define the number of slots required at the RXCDR

Each EGDP comprises two GDP cards.

The use of E1 links The use of balanced or unbalanced E1

Outline of planning steps

Follow Procedure 7-1 to plan an RXCDR.
Procedure 7-1 Planning an RXCDR 1 2 3 4 5 6 7

Plan the number of links between the XCDR and BSC sites by referring to the section Overview of remote transcoder planning. Plan the number of E1 links between the RXCDR and MSC sites by referring to the section RXCDR to MSC links. Plan the number of GPROCs required by referring to the section Generic processor (GPROC). Plan the number of XCDR/GDP/EGDP/GDP2s required by referring to the section Transcoding. Plan the number of MSIs required by referring to the section Multiple serial interface (MSI). Plan the number of KSWs/DSW2s and timeslots required by referring to the section Kiloport switch (KSW) and double kiloport switch (DSW2). Plan the number of RXU shelves by referring to the section RXU shelves.
Continued

68P02900W21-S 7-2 01 Feb 2007

System Information: BSS Equipment Planning

Overview of remote transcoder planning

Procedure 7-1 Planning an RXCDR (Continued) 8

Plan the number of KSWXs/DSWXs required by referring to the section Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX). Plan the number of GCLKs required by referring to the section Generic clock (GCLK). Plan the number of CLKXs required by referring to the section Clock extender (CLKX). Plan the number of LANXs required by referring to the section LAN extender (LANX). Plan the number of PIXs required by referring to the section Parallel interface extender (PIX). Plan the number of BIB or T43s required by referring to the section Line interfaces (BIB, T43). Plan the power requirements by referring to the section Digital shelf power supply. Decide whether an NVM board is required by referring to the section Non volatile memory (NVM) board. Verify the planning process by referring to the section Verify the number of RXU shelves and BSSC cabinets.

9 10 11 12 13 14 15 16

68P02900W21-S 01 Feb 2007 7-3

RXCDR system capacity

Chapter 7: RXCDR planning steps and rules

RXCDR system capacity

System capacity summary
Table 7-1 provides a summary of RXCDR maximum capacities. Table 7-1 RXCDR maximum capacities Item GSR6 GSR7 GSR8 GSR9

RXCDR per BSC XBLs GPROCs per shelf CIC OMLs

10 20 2 2400 1

10 20 2 2400 1
*

10 20 2 2400 1
*

10 20 2 2400* 1

*: Increased to 4800 CICs when AMR (and/or GSM half rate) are both enabled.

68P02900W21-S 7-4 01 Feb 2007

System Information: BSS Equipment Planning

RXCDR to BSC connectivity

RXCDR to BSC connectivity

Introduction
A single BSC can have multiple RXCDRs connected to it and vice-versa. This is useful for the following reasons:

In some configurations, the RXCDR call (CIC) capacity is greater than that of a BSC. Failure of an RXCDR, or the communication path between BSC and RXCDR results in loss of capacity but not a complete failure of the serving BSC.

Capacity
Each BSC can connect to up to ten RXCDRs and vice-versa. The level of connectivity is constrained by the number of XBLs (limit of 20 at each BSC and RXCDR) that can be supported. Refer to the section Determining the number of XBLs required for further details. The level of connectivity is determined by the operator. Excess RXCDR capacity should not be wasted. Larger BSCs should not be connected to only one RXCDR. Each BSC should connect to four RXCDRs. System size, capacity, and cost are the major influences on the selected configuration. With the introduction of advanced transcoding capabilities (that is, AMR), care should be taken when distributing the functions across multiple RXCDRs. For optimum redundancy, each RXCDR should have an appropriate mix of transcoder capability. For example, in a four BSC, four RXCDR configuration where all are interconnected and there are a limited number of transcoder cards capable of AMR (for example, GDP2s), optimally the cards are distributed equally among the RXCDRs.

68P02900W21-S 01 Feb 2007 7-5

RXCDR to BSC links

Chapter 7: RXCDR planning steps and rules

RXCDR to BSC links

Introduction
Refer to Figure 6-1 for the RXCDR to BSC links. The number of E1 links between the RXCDR and the BSCs is the number required to support the A-interface from the RXCDR to the BSC. The number of links between the RXCDR and the BSC is reduced to approximately one quarter of the number of links between the RXCDR and the MSC when 16 kbit/s backhaul is used. When (AMR or GSM) half rate is in use, 8 kbit/s subrate switching is available and (for AMR only) the 7.95 kbit/s half rate codec mode is not included in the Half Rate Active Codec Set, the reduction factor for the half rate calls becomes eight.

In most configurations, half rate is likely to be used only a part of the time, thus yielding a reduction factor of less than eight. 8 kbit/s backhaul can be used when (AMR or GSM) half rate is in use, the 7.95 kbit/s half rate codec mode is not included in the Half Rate Active Codec Set, and 8 kbit/s subrate switching is in use. If a percentage of the active calls is assumed to be half rate, the efficiency can be increased 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. 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 referred to as Enhanced Auto Connect mode. Whenever the number of CICs exceeds the number of 16 kbit/s trunks between the RXCDR and BSC, there is a possibility that a call assignment may fail because of resource shortage. Therefore, ensure the accuracy of half rate usage estimations. The number depends on a combination of factors, which includes (AMR or GSM) capable mobile penetration, whether forced half rate usage is enabled and/or tied in with congestion, and MSC preferences. It is recommended that a safety factor of at least 20% is factored into any half rate usage estimate (20% allows for some variation in the actual number). When HSP MTL feature {28337} is unrestricted, the E1 links used to carry HSP MTL require to be accounted. There are two connected modes. One is the E1 links go to MSC by RXCDR. Another is the E1 links go to MSC directly. For the first connected mode, MSIs are required to terminate HSP MTL at RXCDR (A HSP MTL from MSC is terminated at one port of an MSI and nailed to BSC from another MSI port) whereas for the second connected mode (E1 links go from BSC to MSC directly), there is no impact on RXCDR planning.

4 x 64 kbit/s circuits/RTF for a (AMR or GSM) HR RTF and 8 kbit/s switching is not provisioned, or, (for AMR only) the 7.95 kbit/s half rate codec mode is included in the Half Rate Active Codec Set.

68P02900W21-S 7-6 01 Feb 2007

System Information: BSS Equipment Planning

RXCDR to BSC links

E1 interconnect planning actions

Determine the number of E1 links required. If HSP MTLs are deployed and they pass through RXCDR: NBSC-RXCDR = C2M+ {C64k + X+B64+[T*(1-PHR)+B16]/4 + (T*PHR)/8} / 3
Where Is

NBSC-RXCDR C64k C2M X B64 T PHR B16

minimum number of E1 links required. number of 64kbit/s C7 signaling links to the MSC. number of HSP MTLs to the BSC. number of OML links (X.25 control links to the OMC-R) through the RXCDR. number of 64 kbit/s XBL links. number of trunks between the MSC and the BSC (Refer to Figure 6-1). percentage in decimal (for example, 0.35) of expected half rate usage(meeting the criteria stated previously). number of 16 kbit/s XBL links.

PHR is zero if Enhanced Auto Connect mode is not in use. Each E1 link carries up to 120 (240 at half rate) trunks with a signaling link or 124 (248 at half rate) trunks without a signaling link.

The half rate numbers are only possible with all calls using half rate. HSP MTL and 64kbit/s MTL can not be supported simultaneously.

Redundant E1 links carrying extra trunks can be added. If HSP MTLs go to MSC directly (not through RXCDR), C2M is 0 in the equation.

68P02900W21-S 01 Feb 2007 7-7

RXCDR to MSC links

Chapter 7: RXCDR planning steps and rules

RXCDR to MSC links

Introduction
The number of E1 links between the RXCDR and the MSC is the number required to support the A-interface from the RXCDR to the MSC.

E1 interconnect planning actions

Determine the number of E1 links required. The minimum number of E1 links required for the A-interface is the greater of the two following calculations (fractional values should be rounded up to the next integer value): NRXCDR-MSC = C2M + T/30 NRXCDR-MSC = C2M + (C64k+ X+ T)/31
Where Is

NRXCDR-MSC C64k C2M X T

minimum number of E1 links required. number of 64kbit/s C7 signaling links to the MSC. number of HSP MTL links. number of OML links (X.25 control links to the OMC-R) through the MSC. number of trunks between the MSC and the BSC (See Figure 6-1).

{28337} When HSP MTL feature is used and the E1 links go to MSC by RXCDR, MSIs are required to terminate HSP MTL at RXCDR. If the HSP MTLs go from the BSC to the MSC directly, there is no impact on RXCDR planning and C2M is 0 in the equation. HSP MTL and 64kbit/s MTL cannot be supported simultaneously.

68P02900W21-S 7-8 01 Feb 2007

System Information: BSS Equipment Planning

Generic processor (GPROC)

Generic processor (GPROC)

GPROC nomenclature
In this manual, the different versions of the Generic Processor are as follows:

GPROC2: Refers to GPROC2 GPROC3: Refers to GPROC3 GPROC3-2: Refers to GPROC3 phase 2 GPROC: Refers to both GPROC2 and GPROC3/GPROC3-2

Introduction
Generic processor (GPROC) boards are used throughout the Motorola BSS as a control processor. The GPROC3/GPROC3-2 is a high performance direct replacement for GPROC2s and GPROC1s. This allows for any combination of GPROC types to be installed. GPROC3s/GPROC3-2s cannot be used with software versions earlier than GSR7.

Planning considerations
The following factors should be considered when planning the GPROC complement at the RXCDR:

Each shelf needs at least one GPROC board, along with one for redundancy. A maximum of two GPROCs per shelf are supported: One BSP GPROC One GPROC that can be configured as a redundant BSP GPROC or as a CSFP GPROC

For RXCDR, both GPROC2 and GPROC3s/GPROC3-2s can be in the BSP slots.

68P02900W21-S 01 Feb 2007 7-9

Transcoding

Chapter 7: RXCDR planning steps and rules

Transcoding
Introduction
Transcoders (XCDR/GDP/EGDP/GDP2s) provide the interface for the E1 links between the MSC and the BSC. The XCDR/GDP/EGDP/GDP2s perform the transcoding/rate adaptation function, which compresses the information on the trunks by a factor of four (16 kbit/s). When (AMR or GSM) half rate is in use and 8 kbit/s subrate switching is available [and the 7.95 kbit/s half rate codec mode is not included in the Half Rate Active Codec Set (AMR)] the reduction factor for the half rate calls becomes eight.

In most configurations, half rate is used only a part of the time, thus yielding a reduction factor of less than eight. The number of links between the RXCDR and the BSC is reduced to approximately one quarter (less when half rate is employed under the conditions described ) of the number of links between the RXCDR and the MSC. The GDP2 can process 60 channels of FR, EFR, AMR, GSM HR and Phase 2 data services and is capable of terminating two E1 links from the MSC. It can also function as a replacement for the GDP. Within the RXCDR, enhanced capacity mode must be enabled to access the second E1 when GDP2s are used. An EGDP is a new configuration of the GDP board, which is used to support AMR. Due to the additional transcoding requirements of AMR, each of the 15 DSPs on the GDP board is only capable of supporting the transcoding function for a single channel of GSM speech (AMR, FR, and EFR) and Phase 2 data services. To offer 30 channels of enhanced transcoding using the same E1 span line to the MSC, EGDPs are equipped as pairs, each providing half of the transcoding resources.

This results in an overall reduction in transcoding shelf capacity, which is equivalent to 30 channels per GDP pair. Use of an EGDP is practical only when used in conjunction with AMR. The EGDP does not support GSM half rate. The EGDP can also terminate one Ater E1 link, thus reducing the number of MSI boards required (See EGDP provisioning). The GDP2 can function as GDP and hence it can replace one or both the GDPs in the EGDP configuration. This is not an optimal use of the GDP2 and occurs in emergency situations (for example, board replacement). As a result, it is not considered in the planning procedures. The MSC recommends a particular codec type or types to be used on a call by call basis. It sends the BSC a preference-ordered list, based on factors such as MS capabilities and user configuration. When the MSC is capable of selecting the MSC-RXCDR trunk (CIC) based upon the preferred codec type, a mix of transcoding equipment can be used. If this circuit pooling capability is not present, some equipment combinations can result in non-optimal behavior. When circuit pooling is available in an AMR enabled system, both AMR-capable (EGDP/GDP2) and non -AMR-capable (XCDR/GDP) equipment are used. If circuit pooling is not present, GDP2s or EGDPs should be used exclusively to prevent downgrading or blocking of calls.

68P02900W21-S 7-10 01 Feb 2007

System Information: BSS Equipment Planning

Transcoding

When AMR is employed and both XCDR/GDPs and EGDP/GDP2s are present (and circuit pooling is present at the MSC), there must be sufficient GDP2 and EGDP equipment available to handle the expected AMR traffic. The proportion of AMR-capable transcoding circuits versus non- AMR-capable transcoding circuits should not be less than the proportion of AMR-capable MSs versus non -AMR-capable MSs. A safety factor of no less than 20% is recommended (20% allows for some variation in the actual number and allows for a period of growth in AMR-capable MS penetration before having to add more AMR transcoding ability). Each AMR half rate call needs one (AMR) transcoder circuit. Lack of an available AMR circuit could cause a call to be downgraded to another codec type or possibly blocked. When GSM half rate is employed and a mix of XCDRs and GDP/GDP2s are present, a similar situation exists. However, due to the early introduction into the standards of GSM half rate, most mobiles are expected to be GSM half rate capable. Since a CIC is not tied to any particular voice channel, circuit pooling is rendered ineffective, as there is no way to predict which mobiles need GSM half rate. It becomes necessary to update all transcoding to support GSM HR in order to guarantee that GSM half rate can be used when required. Without this upgrade, calls on non-GSM HR capable CICs remain on a full rate channel. When GSM half rate and AMR are both in use and a combination of AMR transcoding equipment (EGDP, GDP2) and GSM half rate transcoding equipment (GDP, GDP2) exist, circuit pooling is most effective when selecting AMR CICs (EGDP, GDP2) for AMR capable mobiles, and the remaining CICs for nonAMR capable mobiles. Ideally, for AMR capable mobiles the MSC would first select a CIC attached to an EGDP, followed by one attached to a GDP2. For a non-AMR capable mobile the MSC would first select a CIC attached to a GDP, followed by one attached to a GDP2. The selection of the proper CIC (circuit pool) is dependent upon the capability of the connected MSC.

Each trunk needs a quarter (1/4th) (or an eighth (1/8th) in some cases for AMR half rate as described ) of a 64 kbit/s circuit between the RXCDR and BSC. Each control link (RSL, OML, XBL, C7) needs one 64 kbit/s circuit (RSL and XBL have the option of using 16 kbit/s circuits).

Figure 7-1 shows sub-multiplexing and speech transcoding at the RXCDR. Figure 7-1 Sub-multiplexing and speech transcoding at the RXCDR
RXCDR X C D R/ G D P/ G D P 2 BSC Horizon II macro BTS

M S C

K S W / D S W 2

M S I / M S I 2

M S I / M S I 2

K S W / D S W 2

M S I / M S I 2

N I U

C T U 2

ONE RF CARRIER

HIISC

64 kbit/s A-LAW TRUNKS

4 TO 8 TRUNKS PER 64 kbit/s CIRCUIT

64 kbit/s 4 OR 8 TCHs

THE XCDR/GDP/GDP2 TRANSCODES 64 kbit/s A-LAW PCM TO/ FROM 13 kbit/s MAPPED ONTO 16 kbit/s OR UP TO 8 kbit/s MAPPED ONTO 8 kbit/s, AND SUBMULTIPLEXES 4 to 8 TRUNKS TO/FROM 1 x 64 kbit/s CIRCUIT.

THE KSW (DSW2) SUBRATE SWITCHES 16 kbit/s (8 kbit/s) TIMESLOTS. THE CTU2 ENCODES/DECODES 13 (UP TO 8 FOR HALF RATE) kbit/s TO/FROM 22.8 (11.4) kbit/s FOR 8 (16) TIMESLOTS, AND SUBMULTIPLEXES 4 (13 kbit/s MAPPED ON 16 kbit/s) OR 8 (UP TO 8 kbit/s MAPPED ON 8 kbit/s FOR HALF RATE) TIMESLOTS ONTO 1 x 64 kbit/s CIRCUIT, OR THE OTHER WAY AROUND.

8 x 22.8 kbit/s TIMESLOTS OR 16 x 11.4 kbit/s TIMESLOTS

68P02900W21-S 01 Feb 2007 7-11

Transcoding

Chapter 7: RXCDR planning steps and rules

In Figure 7-1, the CTU2 operates in single density mode (one carrier), although it can also operate in double density mode (two carriers).

XCDR/GDP/EGDP/GDP2 planning considerations

The following factors should be considered when planning the XCDR/GDP/EGDP/GDP2 complement:

A XCDR can process 30 voice channels (E1), support GSM Full Rate speech (GSM FR), uplink/downlink volume control and is capable of terminating one E1 link from the MSC. A GDP can process 30 voice channels (E1), support GSM FR, enhanced Full Rate speech (EFR), GSM half rate speech (GSM HR), uplink/downlink volume control and is capable of terminating one E1 link from the MSC. An EGDP consists of a pair of GDP cards, a primary and a secondary. Each EGDP can process 30 channels of GSM FR, EFR, AMR (FR and HR speech), and Phase 2 data services, and terminates one E1 link from the MSC. The primary GDP of an EGDP terminates the E1 interface to the MSC. The secondary GDP of an EGDP may terminate an E1 interface to the BSC. Refer to EGDP provisioning. The GDP2 can process 60 channels of FR, EFR, AMR (FR and HR), GSM HR, and Phase 2 data services and is capable of terminating two E1 links from the MSC. It can also function as a replacement for the GDP. The GDP2 is used to terminate 2 E1s (that is, 60 voice channels) only in the RXU3 shelf and BSSC3 cabinet (enhanced capacity mode must be enabled to access the second E1 when GDP2s are used). The current RXU shelf has only one E1 per transcoder slot, and the current BSSC2 cabinet does not have space for additional line interface boards. The GDP2 supports only 30 channels when used in the RXU shelf and/or BSSC2 cabinet. XCDRs, GDPs, EGDPs, and GDP2s can co-exist in a shelf. The proportion of AMR-capable circuits (GDP2/EGDP) to non AMR-capable circuits (XCDR/GDP) should be sufficient to handle the expected AMR traffic. The master MSI slot(s) should always be populated to enable communication with the OMCR. The master MSI slot can contain a XCDR/GDP/EGDP (either the primary or the secondary) /GDP2, if the OML goes through the MSC. The A-interface must terminate on the XCDR/GDP/EGDP (either the primary or the secondary) /GDP2. Slot 24 (XCDR 0) in the RXU shelf 0 (master) is lost if an optional NVM board is required.

An XCDR card is incompatible with a GPROC3/GPROC3-2 in the BSP slots. XCDRs must be replaced with GDP/GDP2s.

68P02900W21-S 7-12 01 Feb 2007

System Information: BSS Equipment Planning

Transcoding

EGDP provisioning
The secondary GDP of an EGDP uses the E1 connection to terminate an Ater link. This reduces the need for MSIs and makes more efficient use of the available TDM timeslots.

The secondary GDP has one E1 interface (instead of two for an MSI), which must be taken into account in site (MSI) planning.
Figure 7-2 and Figure 7-3 show the EGDP used in configurations with and without the additional E1 termination in use, respectively. Figure 7-2 EGDP configuration with the additional E1 termination in use

68P02900W21-S 01 Feb 2007 7-13

Transcoding

Chapter 7: RXCDR planning steps and rules

Figure 7-3 EGDP configuration without the additional E1 termination in use

Planning actions for transcoding at the RXCDR

The number of transcoders at the RXCDR is proportional to the number of E1 links between the RXCDR and the MSC.

Using E1 links
Each XCDR/GDP/EGDP can terminate one E1 link. Each GDP2 can terminate two E1 links [when used in a RXU3 shelf with enhanced capacity mode enabled (when GDP2s are used)].

68P02900W21-S 7-14 01 Feb 2007

System Information: BSS Equipment Planning

Transcoding

Plan the equipment according to the following formula: XGE + 2 * G2 = NRXCDR-MSC

Where Is

XGE G2 NRXCDR-MSC

number of XCDRs, GDPs and EGDPs. number of GDP2s. minimum number of E1 links required (as N is calculated in RXCDR to MSC links).

Verify that the number of AMR circuits is sufficient to handle the expected AMR traffic. If necessary, adjust the number of EGDP/GDP2s. Use the following formula to determine the percentage of AMR-capable circuits:

%AMR Circuits =

(GDP2 * 60 + EGDP2 * 30) *100 (GDP2 * 60 + EGDP2 * 30 + XCDR * 30 + GDP * 30)

In the equation, count the primary and secondary EGDPs as one EGDP. If HSP MTL is unrestricted and passes through RXCDR, MSI cards are required to terminate HSP MTLs between RXCDR and MSC (Refer to the section RXCDR to BSC links). XGE+2* G2 = NRXCDR-MSC C2M In the equation, C2M is the number of HSP MTLs.

68P02900W21-S 01 Feb 2007 7-15

Multiple serial interface (MSI)

Chapter 7: RXCDR planning steps and rules

Multiple serial interface (MSI)

Introduction
A multiple serial interface provides the interface for the links between an RXCDR site and other network entities, RXCDR to OMC-R and RXCDR to BSC.

Planning considerations
The following factors should be considered when planning the transcoder complement:

Each MSI can interface two E1 links. Each E1 link provides 31 usable 64 kbit/s channels. Redundancy for the MSI depends on the provisioning of redundant E1 links connected to the site. When one remote transcoder site supports multiple BSCs, each BSC needs its own E1 interface as follows:
o The number of MSIs should be equal to half the number of RXCDR to BSC E1 links. Redundancy needs additional links and MSIs. o If the OMLs (X.25 links) do not go through the MSC, a dedicated E1 link (half an MSI) is required for the X.25 links to the OMC-R. o Additional E1 links are required to concentrate X.25 links from other network entities. o Additional E1 links are required for HSP MTLs if HSP MTL is used and passes through RXCDR. MSI cards are required to terminate HSP MTLs that go to the MSC. o Each BSC uses one to four 64 kbit/s or 16 kbit/s channels for XBL fault management communications. Refer to Service Manual: BSC/RXCDR (68P02901W38) for further details.

The master MSI slots should always be populated to enable communication with the OMC-R. If the OML links go directly to the MSC, the master slot should be filled with a XCDR/GDP/EGDP (primary or secondary)/GDP2, else the slot should be filled with an MSI that terminates the E1 link carrying the OML link to the OMC-R. These E1 links should not require to go directly to the OMC-R, they can go to another network element for concentration.

68P02900W21-S 7-16 01 Feb 2007

System Information: BSS Equipment Planning

Multiple serial interface (MSI)

MSI planning actions

With E1 links
Use the following equation to determine the number of MSIs required: NMSI = NBSC-RXCDR/2
Where Is

NMSI NBSC-RXCDR

number of MSIs required. number of E1 links required (as N calculated in RXCDR to BSC links).

68P02900W21-S 01 Feb 2007 7-17

Kiloport switch (KSW) and double kiloport switch (DSW2)

Chapter 7: RXCDR planning steps and rules

Kiloport switch (KSW) and double kiloport switch (DSW2)

Introduction
The KSW/DSW2 provides digital switching for the TDM highway of the RXU. The double kiloport switch (DSW2) is an enhanced version of the KSW, which supports double the number of ports (enhanced capacity mode), as well as extended subrate switching capability down to 8 kbit/s (extended subrate switching mode). Use of 8 kbit/s subrate switching can reduce backhaul costs when used in conjunction with the AMR or GSM half rate feature.

Planning considerations
The following factors should be considered when planning the KSW/DSW2 complement:

A minimum of one KSW/DSW2 is required for each RXU site. The KSW or DSW2 which is not in enhanced capacity mode, has a capacity of 1024 x 64 kbit/s ports or 4096 x 16 kbit/s ports, which can be expanded by adding up to three additional KSW/DSW2s, giving a total switching capacity of 4096 x 64 kbit/s ports or 16384 x 16 kbit/s ports. When operating in enhanced capacity mode, the DSW2 has a capacity of 2048 x 64 kbit/s ports or 8192 x 16 kbit/s ports, which can be expanded by adding up to three additional DSW2s, giving a total switching capacity of 8192 x 64 kbit/s ports or 32768 x 16 kbit/s ports. When operating in extended subrate switching mode (but not enhanced capacity mode), the DSW2 can further switch 8192 x 8 kbit/s ports which can be expanded by adding up to three additional DSW2s, giving a total switching capacity of 32768 x 8 kbits/s ports. When operating in extended subrate switching mode and enhanced capacity mode, the DSW2 can further switch 16384 x 8 kbit/s ports which can be expanded by adding up to three additional DSW2s, giving a total switching capacity of 65536 x 8 kbits/s ports. Eight (64 kbit/s) timeslots per KSW/DSW2 are reserved by the system for test purposes and are not available for use. A mix of KSWs and DSW2s needs that the DSW2s are not operated in the enhanced capacity mode. For redundancy, duplicate all KSWs/DSW2s. In mixed configurations (KSWs and DSW2s), KSWs can be redundant to DSW2s and vice-versa. Verify that each KSW or DSW2 not in enhanced capacity mode uses no more than 1016 ports, or that each DSW2 in enhanced capacity mode uses no more than 2040 ports (8 ports are used internally). The devices in an RXCDR that need TDM timeslots are:
o GPROC2 or GPROC3 = 32 (or 16) timeslots o GDP or XCDR (or GDP2 acting as a GDP replacement) = 16 timeslots o EGDP = 96 timeslots

68P02900W21-S 7-18 01 Feb 2007

System Information: BSS Equipment Planning

Kiloport switch (KSW) and double kiloport switch (DSW2)

o GDP2 = 24 timeslots o MSI = 64 timeslots

The number of TDM timeslots is given by: N = (G * N) + (RGDPXCDR * 16) + (REGDP * 96) + (REDP2 * 24) + (M * 64)
Where Is

N G n RGDPXCDR REGDP REDP2 M

number of timeslots required. number of GPROCs. 16 or 32 (depending on the value of the gproc_slots database parameter). number of GDPs/XCDRs. number of EGDPs. number of GDP2s. number of MSIs.

KSW/DSW2 planning actions

Use the following formula to determine the number of KSWs or DSW2s required when enhanced capacity mode is not enabled: N = [(G * n) + (RGDPXCDR * 16) + (REGDP * 96) + (REDP2 * 24) + (M * 64)]/1016 Use this formula when enhanced capacity mode is enabled: N = [(G * n) + (RGDPXCDR * 16) + (REGDP * 96) + (REDP2 * 24) + (M * 64)]/2040
Where Is

N G n RGDPXCDR REGDP REDP2 M

number of KSWs/DSW2s required. number of GPROCs. 16 or 32 (depending on the value of the gproc_slots database parameter). number of GDPs/XCDRs. number of EGDPs. number of GDP2s. number of MSIs.

68P02900W21-S 01 Feb 2007 7-19

Kiloport switch (KSW) and double kiloport switch (DSW2)

Chapter 7: RXCDR planning steps and rules

Each KSW/DSW2 has to serve the boards in its shelf along with the boards of any extension shelf connected to its shelf by its TDM highway of 1016 available timeslots (or 2040 when operating in enhanced capacity mode). In case of multiple expansion shelves, the TDM highways of each shelf do not merge into a common unique TDM highway across all shelves, that is, a KSW/DSW2 in one shelf cannot serve boards in other expansion shelves. For example, in the case of an RXCDR consisting of two shelves each having 32 unused timeslots per KSW/DSW2 free, an additional MSI board cannot be added even if a MSI slot is free at each shelf (but one GPROC per shelf can be added if one GPROC slot per shelf is free).

68P02900W21-S 7-20 01 Feb 2007

System Information: BSS Equipment Planning

RXU shelves

RXU shelves
Introduction
The number of RXU shelves is a function of the number of MSIs and XCDR/GDP/EGDP/ GDP2s required.

Planning considerations
The following factors should be considered when planning the number of RXU shelves:

Each expansion shelf is allocated to a single KSW/DSW2 and shelves are differentiated by the presence of the KSW/DSW2. Extension shelves are those, which do not contain a primary KSW/DSW2. Shelves containing a KSW/DSW2 are called expansion shelves. An extension shelf extends the TDM highway. It is constrained to the same number of (aggregate) timeslots as the shelf containing the KSW/DSW2. An expansion shelf adds an additional TDM highway. It increases the number of timeslots to that of the additional KSW/DSW2. The number of devices that can be served by a KSW/DSW2 is governed by the TDM timeslot allocation required for each device. This is discussed previously in the KSW/DSW2 planning considerations. The number and type of shelves can then be determined from the devices required. For example, two shelves, each equipped with three MSIs and 16 GDP/XCDRs, can be served by a single KSW. If each shelf has five MSIs with 14 GDP/XCDRs, the KSW can serve only one shelf, and two KSWs are required. The existing RXU shelf has connectivity for up to five MSIs (2 x E1 connections). The remaining 14 slots have one E1 connection. All slots are used for XCDR/GDP/EGDP (primary or secondary)/GDP2s. The RXU3 shelf has connectivity for two E1s per slot. All slots are used for XCDR/GDP/EGDP/GDP2s and MSIs. The GDP2 can be used to terminate 2 x E1s, (that is, 60 voice channels) only in the RXU3 shelf and BSSC3 cabinet (enhanced capacity mode must be enabled to access the second E1 when GDP2s are used). The current RXU shelf has only one E1 per transcoder slot, and the current BSSC2 cabinet does not have space for additional line interface boards. The GDP2 supports only 30 channels when used in the RXU shelf and/or BSSC2 cabinet. An NVM board cannot be installed if all the XCDR slots in the RXU shelf 0 (master) are required.

An XCDR card is incompatible with a GPROC3 in the BSP slots. XCDRs must be replaced with GDP/GDP2s.

68P02900W21-S 01 Feb 2007 7-21

RXU shelves

Chapter 7: RXCDR planning steps and rules

RXU shelf planning actions

Use the appropriate formula (fractional values should be rounded up to the next integer) to determine the number of RXU shelves required: For the current generation RXU shelf: RX = max((M/5) + (R+NNVM)/16) For the new generation RXU3 shelf: RX3 = (M+R+NNVM)/19
Where Is

RX RX3 M R NNVM

minimum number of RXU shelves required. minimum number of RXU3 shelves required. number of MSIs. number of XCDR/GDP/EGDP/GDP2s. number of optional NVM boards (0 or 1).

For EGDPs, both the primary and the secondary must be counted. The number of timeslots equipped to each shelf must be verified using the appropriate equation given .

Enhanced capacity mode is not enabled

The verification procedure is like the KSW/DSW2 planning consideration. (G*n) + (RGDPXCDR * 16) + (REGDP * 96) + (RGDP2 * 24) + (M * 64) <=1016
Where Is

G n RGDPXCDR REGDP RGDP2 M

number of GPROCs in the shelf. 16 or 32 (depending on the value of the gproc_slots database parameter). number of GDP/XCDRs in the shelf. number of EGDPs in the shelf. number of GDP2s in the shelf. number of MSIs in the shelf.

68P02900W21-S 7-22 01 Feb 2007

System Information: BSS Equipment Planning

RXU shelves

Enhanced capacity mode is enabled (non-extension shelf)

(G*n) + (RGDPXCDR * 16) + (REGDP * 96) + (RGDP2 * 24) + (M * 64) <=1016

Enhanced capacity mode is enabled (extension shelf)

(G*n) + (RGDPXCDR * 16) + (REGDP * 96) + (RGDP2 * 24) + (M * 64) <=1016 If the result of using the appropriate equation exceeds the value quoted, the configuration of MSIs, GPROCs and GDPs can be adjusted, or an additional shelf or shelves are required.

68P02900W21-S 01 Feb 2007 7-23

Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)

Chapter 7: RXCDR planning steps and rules

Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)
Introduction
The KSWX extends the TDM highway of a RXU to other RXUs and supplies clock signals to all shelves in multi-shelf configurations. The KSWX is required whenever a network element grows beyond a single shelf. The DSWX performs the same function as the KSWX. It is necessary when enhanced capacity mode (2048 timeslot capability) is used (but not in extended subrate switching mode).

Planning considerations
The following factors should be considered when planning the KSWX/DSWX complement:

KSWXs/DSWXs are not required in a single shelf configuration (that is, when expansion or extension is not required). For redundancy, duplicate all KSWX/DSWX boards (needs redundant KSW/DSW2). In mixed configurations (KSWXs and DSWXs), KSWXs can be redundant to DSWXs and vice-versa. KSWXs/DSWXs are used in three modes:
o KSWX/DSWXE (Expansion) are required to interconnect the KSWs/DSW2s for sites with multiple KSWs/DSW2s. o KSWX/DSWXR (Remote) are required in shelves with KSWs/DSW2s to drive the TDM highway in shelves that do not have KSWs/DSW2s. o KSWX/DSWXL (Local) are used in shelves that have KSWs/DSW2s to drive the clock bus in that shelf and in shelves that do not have KSWs/DSW2s to drive both the local TDM highway and the clock bus in that shelf.

Five of the redundant KSWX/DSWX slots are also CLKX slots. The maximum number of KSWX/DSWX slots per shelf is 18, nine per KSW/DSW2. KSWXs and DSWXs may both be used. However, KSWXs and DSWXs should always be used with like pairs, that is, DSWXs with DSWXs and KSWXs with KSWXs. Operation in enhanced capacity mode needs the use of all DSWXs (and DSW2s).

The fiber optic cables, which are used to extend/expand the TDM highway from one RXU to another RXU, must be of the same length to limit the risk of TDM highway extension/expansion errors.

68P02900W21-S 7-24 01 Feb 2007

System Information: BSS Equipment Planning

Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)

KSWX/DSWX planning actions

The number of KSWXs/DSWXs required is the sum of KSWX/DSWXE, KSWX/DSWXL, and KSWX/DSWXR. NKX = NKXE + NKXR + NKXL NKXE = K (K-1) NKXR = SE When SE=0, NKXL = 0 When SE > 0 NKXL = K + SE
Where Is

NKX NKXE NKXR NKXL K SE

number of KSWXs/DSWXs required number of KSWX/DSWXE number of KSWX/DSWXR. number of KSWX/DSWXL number of non-redundant KSWs/DSW2s number of extension shelves

For example:
Table 7-2 KSWX/DSWX (non-redundant) Extension shelves 1 KSW/DSW2 (non redundant) 2 3 4

0 1 2 3 4

0 3 5 7 9

4 6 8 10 12

9 11 13 15 17

16 18 20 22 24

Table 7-3 KSWX/DSWX (redundant) Extension shelves 1 KSW/DSW2 (non redundant) 2 3 4

0 1 2 3 4

0 6 10 14 18

8 12 16 20 24

18 22 26 30 34

32 36 40 44 48

68P02900W21-S 01 Feb 2007 7-25

Generic clock (GCLK)

Chapter 7: RXCDR planning steps and rules

Generic clock (GCLK)

Introduction
The generic clock (GCLK) generates all the timing reference signals required by a RXU.

Planning considerations
The following factors should be considered when planning the GCLK complement:

One GCLK is required at each RXCDR. A second GCLK is optionally requested for redundancy. Both GCLKs must reside in the same shelf of the RXCDR.

GCLK planning actions

Use the following formula to determine the number of GCLKs required: GCLKs = 1 + 1 redundant

68P02900W21-S 7-26 01 Feb 2007

System Information: BSS Equipment Planning

Clock extender (CLKX)

Clock extender (CLKX)

Introduction
A clock extender (CLKX) board provides expansion of GCLK timing to more than one RXU.

Planning considerations
The following factors should be considered while planning the CLKX complement:

One CLKX is required in the first RXU shelf, which contains the GCLK, when expansion beyond the shelf occurs. Each CLKX can supply the GCLK signals to six shelves. There are three CLKX slots for each GCLK, allowing each GCLK to support up to 18 shelves (LAN extension only allows fourteen shelves in a single network element). The maximum number of CLKX slots per shelf is six.

The CLKX uses six of the redundant KSWX/DSWX slots.

With a CLKX, a KSWX/DWSXL is required to distribute the clocks in the master and each of the expansion/extension shelves. For redundancy, duplicate each CLKX (needs a redundant GCLK). Fiber optic cables extending clock reference signals, from the parent shelf to all other shelves and itself at a site, must be of the same length to maintain site synchronization integrity.

CLKX planning actions

Use the following formula to determine the number of CLKXs required: NCLKX = Roundup (E/6) * (1 + RF)
Where Is

NCLKX ROUND UP E RF

number of CLKXs required. rounding up to the next integer. number of shelves. redundancy factor (1 if redundancy required (recommended), 0 for no redundancy).

68P02900W21-S 01 Feb 2007 7-27

LAN extender (LANX)

Chapter 7: RXCDR planning steps and rules

LAN extender (LANX)

Introduction
The LANX provides a LAN interconnection for communications among all GPROCs at a site.

Planning considerations
The following factors should be considered when planning the LANX complement:

A LANX is supplied in each shelf. For full redundancy, add one LANX for each shelf. The LANX can support a maximum network size of 14 shelves.

LANX planning actions

Use the following formula to determine the number of LANXs required: NLANX = NRXU * (1 + RF)
Where Is

NLANX NRXU RF

number of LANXs required. number of RXU shelves (RXU <=14). redundancy factor (1 is the recommended value if redundancy is required, 0 for no redundancy).

68P02900W21-S 7-28 01 Feb 2007

System Information: BSS Equipment Planning

Parallel interface extender (PIX)

Parallel interface extender (PIX)

Introduction
The PIX provides eight inputs and four outputs for site alarms.

Planning considerations
The following factors should be considered when planning the PIX complement:

The maximum number of PIX board slots per shelf is two. The maximum number of PIX board slots per site is eight.

PIX planning actions

Determine the number of PIXs required as follows: PIX ? 2 * number of RXUs or PIX ? 8

68P02900W21-S 01 Feb 2007 7-29

Line interfaces (BIB, T43)

Chapter 7: RXCDR planning steps and rules

Line interfaces (BIB, T43)

Introduction
The line interfaces, balanced-line interface board (BIB) and T43 board (T43), provide impedance matching for E1 links.

Planning considerations
The following factors should be considered when planning the line interface complement:

Use a BIB to match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm 3 V (peak pulse) line. Use a T43 Board (T43) to match a single-ended 75 ohm 2.37 V (peak pulse) line. Each BIB/T43 can interface six E1 links to specific slots on one shelf. All E1 links must be terminated, including the links, which are fully contained in the cabinet, for example, between RXU and BSU. Up to four BIBs or T43s per shelf can be mounted on a BSSC2 cabinet.
o A maximum of 24 E1 links can be connected to a RXU shelf. o A BSSC2 cabinet with two RXU shelves can interface 48 E1 links.

Up to seven BIBs or T43s per shelf can be mounted on a BSSC3 cabinet.

o A maximum of 38 E1 links can be connected to a RXU3 shelf. o A BSSC3 cabinet with two RXU3 shelves can interface 76 E1 links.

When fully equipping two RXU3 shelves with 38 E1s each, there are four unused E1 links on two of the BIB/T43s. GDP2s must be used to utilize fully two E1s per slot.

68P02900W21-S 7-30 01 Feb 2007

System Information: BSS Equipment Planning

Line interfaces (BIB, T43)

BIB/T43 planning actions

The following planning actions are required:

Determine the number E1 link to be driven. Calculate the number of E1s to be terminated for each shelf. Determine the number of BIBs or T43s required per shelf. Minimum number of BIBs or T43s required per shelf = Number of E1 links/6. Sum up across all shelves for the total.

68P02900W21-S 01 Feb 2007 7-31

Digital shelf power supply

Chapter 7: RXCDR planning steps and rules

Digital shelf power supply

Introduction
A BSSC cabinet can be supplied to operate from either a +27 V dc or -48/-60 V dc power source.

Planning considerations
The following factors should be considered while planning the PSM complement:

Two DPSMs are required for each shelf in the BSSC/RXCDR. Two IPSMs are required for each shelf in the BSSC2/RXCDR (-48/-60 V dc). Two EPSMs are required for each shelf in the BSSC2/RXCDR (+27 V dc). For redundancy, add one DPSM, IPSM or EPSM for each shelf.

Power supply planning actions

Use the following formula to determine the number of PSMs required: PSMS = 2 * Number of RXUs + RF * Number of RXUs Where RF = is the Redundancy factor (recommended value is 1 if redundancy is required, 0 for no redundancy).

68P02900W21-S 7-32 01 Feb 2007

System Information: BSS Equipment Planning

Non volatile memory (NVM) board

Non volatile memory (NVM) board

Introduction
The non volatile memory board provides the Remote Transcoder with an improved recovery facility following a total power loss. With the NVM board installed, data is retrieved from the NVM board rather than from the OMC-R during recovery from a total power loss.

Planning considerations
The following factors should be considered when planning the NVM complement:

Only one NVM board can be installed at the RXCDR. The NVM board uses slot 24 on the RXU shelf 0 (master) of the RXCDR. In the case that a XCDR board is already occupying that slot, the XCDR board and associated interface cabling can be moved from slot 24 to the spare slot. If there are no spare slots, then the XCDR board occupying slot 24 must be removed to accommodate the NVM board, with a subsequent reduction in capacity of the RXCDR. The appropriate software required to support the NVM board must be loaded at the OMC-R and downloaded to the RXCDR.

NVM planning actions

The NVM board is optional.

68P02900W21-S 01 Feb 2007 7-33

Verify the number of RXU shelves and BSSC cabinets

Chapter 7: RXCDR planning steps and rules

Verify the number of RXU shelves and BSSC cabinets

Verification
After planning is complete, verify that:

Each non-redundant KSW/DSW2 has its own shelf. Each extension shelf supports extension of a single KSW/DSW2. The number of KSWXs/DSWXs, LANXs, CLKXs, and GPROCs is correct.

If necessary, add extra RXU shelves. Each BSSC cabinet supports two RXU shelves.

68P02900W21-S 7-34 01 Feb 2007

Chapter 8 PCU upgrade for BSS

The following information for the PCU upgrade to the BSS to support GPRS and EGPRS is provided:
BSS planning for GPRS/EGPRS PCU hardware layout PCU shelf (cPCI) MPROC board DPROC board PMC module (Packet) Rear Transition Module PCU equipment redundancy and provisioning goals E1 link/ETH link provisioning for GPRS and EGPRS QoS capacity and QoS2 impact PCU-SGSN: traffic and signal planning BSS-PCU hardware planning example for GPRS BSS-PCU hardware planning example for EGPRS

68P02900W21-S 01 Feb 2007 8-1

BSS planning for GPRS/EGPRS

Chapter 8: PCU upgrade for BSS

BSS planning for GPRS/EGPRS

Introduction to BSS planning for GPRS/EGPRS
The BSS planning process for GPRS/EGPRS involves adding additional BSS equipment and software to the BSS, in addition to the PCU hardware and software. The extent of the additional BSS equipment depends on the amount of traffic expected to be carried over the GPRS/EGPRS part of the network and the coding schemes used on the air interface.

This section contains planning for both GPRS and EGPRS and NOTEs differences where appropriate. The section GPRS/EGPRS network traffic estimation and key concepts in Chapter 3, BSS cell planning is intended to provide the network planner with the rules to determine the number of GPRS/EGPRS timeslots that are to be provisioned at the BTS, subsequently provisioned in PCU hardware, and provisioned with communication links. The BSS planning process described here focuses on the provisioning of the PCU hardware within the BSS. Refer to BSS-PCU hardware planning example for GPRS and BSS-PCU hardware planning example for EGPRS. Its purpose is to unite the information presented in the entire document from a planning perspective.

PCU to SGSN interface planning

The PCU to SGSN interface is referred to as the Gb Interface. The Gb interface connects the BSS PCU to the GPRS SGSN. Motorola supports three Gb interface options (options A, B, and C), as shown in Figure 8-1.

68P02900W21-S 8-2 01 Feb 2007

System Information: BSS Equipment Planning

BSS planning for GPRS/EGPRS

Figure 8-1 PCU to SGSN interface planning

The RXCDR can be used as an E1 switching interface between the PCU and SGSN, as shown in option A. Alternatively, the BSC can be used as an E1 switching interface, as shown in option B. Option C is the case where there is no BSS E1 switching element between the PCU and SGSN. The PCU is configured for E1 loop timing recovery on all the PCU E1 interfaces. The PCU is connected directly to the BSC E1 interfaces and the BSC is configured to provide the E1 master clock. If the PCU is connected to a GSN that does not have a master clock source, some interface equipment that has a master clock source (such as DACs) should be used. The Motorola BSC and RXCDR equipment can be used in place of DACs for this purpose. When an RXCDR or BSC is used as an E1 switching element, as shown in option A and option B, respectively, additional equipment provisioning of these network elements are required to support the PCU E1 interfaces. This is in accordance with the provisioning rules for adding E1 interfaces to the RXCDR and BSC network elements.

68P02900W21-S 01 Feb 2007 8-3

BSS planning for GPRS/EGPRS

Chapter 8: PCU upgrade for BSS

Feature compatibility
Alarms consolidation
No additional BSS, GPRS or EGPRS network planning is required. PCU device alarms impact only PCU functional unit severity, and not the cell functional unit severities. Therefore, the impact is to the following PCU devices: DPROC and PCU System Processor (PSP).

BSC-BTS dynamic allocation

No additional BSS or GPRS network planning is required. The dynamic allocation feature specifies how the BSC configures and shares the terrestrial backing between the GPRS data traffic and the Circuit-Switched (CS) traffic. The terrestrial backing between the BTS and BSC should have enough capacity to carry the radio timeslots assigned to both GPRS and circuit switched traffic. If there is not enough capacity, because there are not enough physical channels, the BSC allocates the backing to CS first. The remaining capacity is assigned to GPRS (reserved GPRS timeslots first, and then to switchable GPRS timeslots). If the DTM feature is enabled the resource available for switchable GPRS timeslots is planned excluding DTM traffic; see Chapter 3 for an explanation of this process. Any terrestrial backing resources not used by circuit-switched calls are allocated for switchable use. However, circuit-switched calls can take resources away from the switchable pool when traffic demands need more terrestrial capacity. Switchable resources are used first and then the resources are used for DTM. Terrestrial resources available in the switchable pool are available for GPRS traffic use. The BSC reassigns GPRS switchable, DTM or reserved backing to CS if backing is required for emergency circuit-switched calls. In this case, the switchable and reserved backing is reassigned so that the remaining GPRS radio timeslots within a carrier are contiguous. The CS3/CS4 feature and EGPRS feature that need 32 kbit/s and 64 kbit/s bandwidth (variable bandwidth in terms of a configurable rtf_ds0_count if VersaTRAU is unrestricted), respectively on backhaul, have been designed to work mutually exclusively with the BSC-BTS dynamic allocation feature.

Circuit error rate monitor

No circuit error rate monitor support is provided by the GPRS/EGPRS feature.

Circuit-switched (voice or data) calls

The addition of GPRS/EGPRS to a GSM network impacts the traffic and signaling handling network capability for GSM voice and circuit data traffic. Additional loading on the BSS elements due to the GPRS/EGPRS traffic needs additional BSS equipment and interface circuits. Three classes of mobile devices permit non-simultaneous attachment to the circuit-switched and packet data channels. Hence, the BSS need not be provisioned to simultaneously handle the call processing and signaling for both circuit-switched traffic and GPRS/EGPRS packet data services on a per subscriber basis. The BSS treats class A mobiles like class B mobiles, if DTM feature is not enabled. Therefore, the BSS part of the network supports the simultaneous attachment, activation and monitoring of circuit-switched and packet data services. Simultaneous GPRS/EGPRS and circuit-switched traffic is not supported, if the DTM feature is not enabled. The mobile user can make and/or receive calls on either of the two services sequentially, but not simultaneously. The selection of the appropriate service is performed automatically. When the DTM feature is unrestricted, a DTM MS with a CS connection can make a DTM request to add a PS session. A DTM MS with only a PS session has to abort that session to establish a CS session.

Concentric cells
GPRS/EGPRS timeslots are available in the outer zone carriers.

68P02900W21-S 8-4 01 Feb 2007

System Information: BSS Equipment Planning

BSS planning for GPRS/EGPRS

Congestion relief
No additional BSS or GPRS/EGPRS network planning is required. Congestion relief considers switchable GPRS/EGPRS timeslots as idle TCHs.

Cell resource manager dynamic reconfiguration

No additional BSS or GPRS/EGPRS network planning is required. The Cell Resource Manager (CRM) dynamic reconfiguration feature can use the switchable GPRS/EGPRS timeslots, but it cannot reconfigure the reserved GPRS/EGPRS timeslots under any circumstance.

Directed retry
No additional BSS or GPRS/EGPRS network planning is required. The BSC uses directed retry to relieve cell congestion by redistributing traffic across cells. For the GPRS/EGPRS traffic part of the BSS, the BSC treats switchable GPRS/EGPRS timeslots like idle TCHs.

Emergency call pre-emption

No additional BSS or GPRS/EGPRS network planning is required. The BSS can configure any GPRS and/or EGPRS timeslot to carry out emergency calls. If an emergency call has to be made within a cell with a GPRS or EGPRS carrier, the BSS selects the air timeslot in the following order:

Idle TCH. Switchable GPRS timeslot (from lowest to highest). Switchable EGPRS timeslot (from lowest to highest).

If the emergency call pre-emption feature is enabled, the BSS select the air timeslot from the following list in the following order:

Idle TCH Switchable GPRS timeslot (from lowest to highest) Switchable EGPRS timeslot (from lowest to highest) DTM PDCH In-use TCH Reserved GPRS timeslot (from lowest to highest) Reserved EGPRS timeslot (from lowest to highest) PBCCH/PCCCH timeslot

Emergency TCH channels are pre-empted when eMLPP is enabled and if the MSC has assigned a low priority and pre-emption vulnerability to the emergency call occupying the TCH.

All available GPRS timeslots are assigned to be switchable before any EGPRS timeslot.

Extended range cells

No additional BSS or GPRS or EGPRS network planning is required.

68P02900W21-S 01 Feb 2007 8-5

BSS planning for GPRS/EGPRS

Chapter 8: PCU upgrade for BSS

The extended range cell feature extends the range of a GSM 900 MHz mobile beyond 35 kilometers up to a maximum range of 121 kilometers (depending on limiting factors). This range extension is not supported for GPRS or EGPRS carriers.

Frequency hopping and redefinition

The GSM radio uses slow frequency hopping to improve data reliability and to increase the number of active users. The GPRS/EGPRS timeslots assigned to the uplink and downlink channels must have the same frequency parameters. GPRS/EGPRS timeslots can have a different timeslot activity factor to voice, and hence cause the cell C/I performance to change from a GSM-only system. The frequency redefinition feature extends the GSM 4.08 capabilities to GPRS and EGPRS.

Global reset
No additional BSS or GPRS/EGPRS network planning is required. The global reset procedure initializes the BSS and MSC in the event of a failure. A global reset does not affect any resources assigned to GPRS/EGPRS.

Integrated Horizon HDSL interface

No additional BSS, GPRS, or EGPRS network planning is required other than to plan for the GDS link. The PCU does not support a high bit-rate subscriber line (HDSL) between the PCU and the BSC. However, the BSC can use an MSI board (with HDSL capabilities) to terminate a GDS link to the PCU if an E1 is used for the connection.

Multiband handovers
No additional BSS, GPRS, or EGPRS network planning is required. The BSC treats switchable GPRS/EGPRS timeslots like idle TCHs in the case of multiband handovers.

Over the air flow control for circuit-switched mobiles

No additional BSS, GPRS, or EGPRS network planning is required. The BSC treats switchable GPRS/EGPRS timeslots like idle TCHs in the case of over the air flow control for the circuit-switched mobiles feature.

RTF path fault containment

The BSC uses a switchable GPRS/EGPRS timeslot for a Cell Broadcast CHannel (CBCH) or a Standalone Dedicated Control CHannel (SDCCH). The RTF path fault feature converts TCHs to SDCCH when an RTF path fault occurs. The RTF path feature can also convert TCH barred switchable GPRS/EGPRS timeslots, to SDCCH. The converted GPRS/EGPRS timeslots are returned to GPRS/EGPRS after the original RTF path fault is cleared.

SMS cell broadcast

The CBCH can reside on a switchable GPRS/EGPRS timeslot. Therefore, switchable GPRS/EGPRS timeslots can be reconfigured as SDCCHs. However, GPRS/EGPRS reserved timeslots cannot be reconfigured as SDCCHs.

SD placement prioritization
A GPRS/EGPRS carrier cannot be configured such that the sum of the number of allowed SDCCHs and the number of GPRS/EGPRS timeslots exceed the capacity of the carrier.

68P02900W21-S 8-6 01 Feb 2007

System Information: BSS Equipment Planning

BSS planning for GPRS/EGPRS

GPRS seamless cell reselection

No additional BSS, GPRS, or EGPRS network planning is required. Seamless cell reselection alleviates heavy performance degradation in the GPRS/EGPRSs system due to frequent cell reselections by performing the cell change procedure at the RLC/MAC layer rather than at a higher layer.

VersaTRAU backhaul
VersaTRAU backhaul feature allows the operator to configure the backhaul required for an EGPRS capable RTF using the rtf_ds0_count parameter associated with the RTF. The backhaul per RTF has to be planned based on the number of reserved and switchable timeslots in the cell and expected RF conditions.
Table 8-1 summarizes the recommended VersaTRAU backhaul for a given number of configured PDTCHs per carrier. The recommendations are based on the achievement of average coding scheme of at least MCS6. Table 8-1 VersaTRAU backhaul recommendations for a given number of PDTCHs Number of PDTCH Recommended aggressive VersaTRAU backhaul (average 28 kbit/s) Number of DS0 Average kbit/s (effective MCS) Recommended non-aggressive VersaTRAU backhaul Number of DS0 Average kbit/s (effective MCS)

8 7 6 5 4 3 2 1

4 3 3 3 2 2 1 1

28 kbit/s (MCS5) 24 kbit/s (MCS5) 28 kbit/s (MCS5) 33 kbit/s (MCS6) 28 kbit/s (MCS5) 37 kbit/s (MCS6) 28 kbit/s (MCS5) 59 kbit/s (MCS9)

5 4 4 3 3 2 1 1

34 kbit/s (MCS6) 31 kbit/s (MCS6) 37 kbit/s (MCS6) 33 kbit/s (MCS6) 41 kbit/s (MCS6) 37 kbit/s (MCS6) 28 kbit/s (MCS5) 59 kbit/s (MCS9)

Table 8-2 shows the recommended initial settings (non-aggressive in terms of backhaul savings) for the rtf_ds0_count for an EGPRS RTF when VersaTRAU backhaul feature is unrestricted. The first 2 rows show the different initial configurations ranging from 1 PDTCH per carrier to 8 PDTCHs per carrier (nonBCCH carrier). The next row shows the number of DS0s forming the VersaTRAU frame (Versachannel), the expected throughput and coding scheme with the given VersaTRAU backhaul. The rows further down the table indicate the number of DS0s constructing the VersaTRAU frame and throughputs after 1, 2, 3, 4 and 5 TSs are stolen for voice. In this table, the recommended backhaul for the Versachannel is conservative, and generally results in MCS6 (if all PDTCHs on the given carrier are carrying active data transfers at the same time. Higher coding schemes on individual timeslots can be reached if other timeslots on the carrier are idle due to the benefits of the statistical multiplexing). Table 8-3 is more aggressive and shows the recommended number of DS0s forming the VersaTRAU, which generally results in MCS5.

68P02900W21-S 01 Feb 2007 8-7

BSS planning for GPRS/EGPRS

Chapter 8: PCU upgrade for BSS

Table 8-2 Expected throughput/TS and coding schemes (conservative)

# of PD/carrier # DS0 for VersaTRAU including voice VersaTRAU % saving versus. Today #TRAU # PDs left Average datarate/TS CS used #TRAU # PDs left Average datarate/TS CS used #TRAU # PDs left Average datarate/TS CS used #TRAU # PDs left Average datarate/TS CS used #TRAU # PDs left Average datarate/TS CS used #TRAU 5 4 3 2 1 0

8 5

7 5

6 5

5 4

4 4

3 4

2 3

1 3

38

38

38

50

50

50

63

63

5 8 34 MCS6 4 7 31 MCS6 4 6 37 MCS6 4 5 44 MCS6 4 4 59 MCS9 3

4 7 31 MCS6 4 6 37 MCS6 4 5 44 MCS6 4 4 59 MCS9 3 3 59 MCS9 3

4 6 37 MCS6 4 5 44 MCS6 4 4 59 MCS9 3 3 59 MCS9 3 2 59 MCS9 3

3 5 33 MCS6 3 4 41 MCS6 2 3 37 MCS6 2 2 59 MCS9 2 1 59 MCS9

3 4 41 MCS6 2 3 37 MCS6 2 2 59 MCS9 2 1 59 MCS9

2 3 37 MCS6 2 2 59 MCS9 1 1 59 MCS9

1 2 28 MCS 9 2 1 59 MCS 9

1 1 59 MCS 9

Continued

68P02900W21-S 8-8 01 Feb 2007

System Information: BSS Equipment Planning

BSS planning for GPRS/EGPRS

Table 8-2 Expected throughput/TS and coding schemes (conservative) (Continued)

# PDs left Average datarate/TS CS used

3 59 MCS9

2 59 MCS9

1 59 MCS9

Table 8-3 Expected throughput/TS and coding schemes (aggressive)

# of PD/carrier # DS0 for VersaTRAU including voice VersaTRAU % saving versus. Today #TRAU # PDs left Average datarate/TS CS used #TRAU # PDs left Average datarate/TS CS used #TRAU # PDs left Average datarate/TS CS used #TRAU # PDs left Average datarate/TS 3 2 1 0

8 4

7 4

6 4

5 4

4 4

3 3

2 3

1 3

50

50

50

50

50

63

63

63

4 8 28 MCS5 3 1 24 MCS5 3 6 28 MCS6 3 5 33

3 1 24 MCS5 3 6 28 MCS5 3 5 33 MCS6 3 4 41

3 6 28 MCS5 3 5 33 MCS6 3 4 41 MCS6 3 3 37

3 5 33 MCS6 3 4 41 MCS6 2 3 37 MCS6 2 2 59

2 4 28 MCS5 2 3 37 MCS6 2 2 59 MCS9 2 1 59

2 3 37 MCS6 2 2 59 MCS9 1 1 59 MCS9

1 2 28 MCS 5 2 1 59 MCS 9

1 1 59 MCS9

Continued

68P02900W21-S 01 Feb 2007 8-9

BSS planning for GPRS/EGPRS

Chapter 8: PCU upgrade for BSS

Table 8-3 Expected throughput/TS and coding schemes (aggressive) (Continued)

CS used #TRAU # PDs left Average datarate/TS CS used #TRAU # PDs left Average datarate/TS CS used 5 4

MCS6 3 4 44 MCS6 2 3 37 MCS7

MCS6 2 3 39 MCS6 2 2 59 MCS9

MCS6 2 2 59 MCS9 2 1 59 MCS9

MCS9 2 1 59 MCS9

MCS9

Evolved PCU (ePCU)

The evolved PCU feature provides a migration path for operators wanting to expand existing GPRS capabilities. A new DPROC type called PXP is introduced. PXP combines the functionality of PICP and PRP into one board. U-DPROC2 is a new hardware type which takes over all the functions of legacy DPROC board and has new mode for high-capacity operation. U-DPROC2 hardware board can be configured as new PXP function which combines the functionality of PICP and PRP into one board. PXP are connected with PSI2 board in BSC through Ethernet link. PXP can provide PDCH capacity of 280/70 or 140/140 (Total Fanout/Throughput, refer to NOTE1). A combination of PXP, PICP and PRP can be configured in the PCU. It allows network users to reuse existing DPROC hardware in PCU with GSR9 SW release. Figure 8-2 is an example of mixed configuration in which PRP, PICP and PXP coexist in the PCU.

68P02900W21-S 8-10 01 Feb 2007

System Information: BSS Equipment Planning

BSS planning for GPRS/EGPRS

Figure 8-2 Mixed Deployment

Besides the mixed deployment, customers can also select to configure the PCU in one of the following ways:

Legacy Deployment: U-DPROC2 boards are configured as PICPs and PRPs as in legacy configuration (pre-GSR9). U-DPROC2 functions as board level replacement of DPROC. New Deployment: With new configuration, U-DPROC2 boards are configured as PXPs. The PCU can be fully configured with 12 U-DPROC2 boards functioning as PXP.

The Increase throughput of PRP with the PCU feature {28000}, provides an option to increase PRP/PXP throughput by reducing the PRP/PXP capacity. For prp_fanout_mode1, a maximum of X timeslots per PRP/PXP (X is equal to 30 for PRP, and 70 for PXP) are served at a 20ms block period. For prp_fanout_mode2, all timeslots assigned to a PRP/PXP are served at a 20ms block period. 3xPCU feature is disabled in GSR9.

{22415} Customer can setup more GPRS TSs in database than all PRP/PXPs can support and are not rejected. MMI commands are accepted with a warning message. It can save operator's CAPEX, especially at the initial stage of GPRS deployment and in the location only requiring GPRS coverage. At least one PDCH is assigned to a cell. The coverage has higher priority than capacity. Enough PDCH resources/PRP should still be available when cell capacity is required.

68P02900W21-S 01 Feb 2007 8-11

BSS planning for GPRS/EGPRS

Chapter 8: PCU upgrade for BSS

DTM operation and planning considerations

The DTM feature allows a mobile to access both the CS and PS services simultaneously. The GPRS/EDGE timeslots used for the PS service for DTM are taken from the pool of idle TCH. However, to allow these timeslots to be configured as GPRS timeslots, it is necessary to reserve a pool of PRP and GDS backing resource. Therefore, consideration must be made for the number of DTM timeslots that is required when dimensioning the network to support the desired number of switchable and reserved timeslots in the network. The DTM token (defined by max_dtm_ts planning in Chapter 3, BSS cell planning should be converted to DTM PD from idle TCH to carry DTM PS traffic. While allocating resources for GPRS/EDGE, first assign resources for reserved GPRS timeslots. Share the remaining resource between switchable timeslots and DTM that can be used to provide backing for TCH reconfigured to support DTM GPRS/EDGE timeslots. One of the most likely use cases for DTM is that a CS voice call is established and a PS data session is established to send data associated with that call. This close association between the CS and the PS services allows to apply the Erlang model for the estimation of the DTM PS call behavior. This allows to estimate the resources that should be provided for DTM to meet an acceptable level of blocking and therefore introduce the DTM service with the minimum requirement to increase GPRS/EDGE resources. Following this approach the max_dtm_ts that is specified for each cell is treated as a group of trunks that could possibly carry the PS part of a DTM call. To determine the number of trunks that max_dtm_ts represents, estimate the number of DTM sessions that are to be interleaved onto this resource. Interleaving varies from 4 where 4 half rate CS calls share a single GPRS/EDGE timeslots, to 0.5, where a single CS call uses 2 GPRS/EDGE timeslots. On an average the effective interleaving is assumed to be 1. This is because when a cell is near congestion as single use of 2 timeslots is unlikely and reconfiguration to half rate is difficult in a congested situation. The Table 8-4 shows an extract from an Erlang table that shows the relationship between the number of trunks and the average Erlangs that can be carried at 2% blocking.
Table 8-4 Erlang table Trunks Erlangs

1 2 3 4 5 6 7 8 9 10

0.02 0.2 0.6 1.05 1.65 2.25 2.9 3.6 4.3 5.05

68P02900W21-S 8-12 01 Feb 2007

System Information: BSS Equipment Planning

BSS planning for GPRS/EGPRS

Initially, the PCU tries to allocate resource for the sum of the max_dtm_ts and switchable timeslots for all the cells mapped to each PRP. If a PRP does not have sufficient resource for this, Table 8-4 is used to estimate the pool of resources that needs to be reserved to meet the DTM requirement at 2% blocking rate (this is only an estimate as the number CS congestion leads to use of TCH resources that could be reconfigured for DTM use. Additionally fragmentation of the available CS and PS resources can reduce the possibility of establishing a DTM call). For example, if 20 cells are mapped to a PRP and max_dtm_tch is specified as 4, the PCU initially tries to allocate a pool of 80 PRP/GDS resource. If this is not possible, the Erlang calculation is used to determine that a pool of 30 PRP/GDS should be reserved. If there is still not enough resource available, the PCU estimates the arrival rate for DTM calls and dynamically manages the size of the pool required for DTM such that there is sufficient resource to meet the expected DTM demand at 2% blocking rate in the next cell balancing cycle. If there is still not enough resource available, the PCU shares the resources pro-rata to the ratio of the sum of the max_dtm_ts to the sum of the database value of switchable timeslots for the cells mapped to the PRP. This clearly increases the DTM blocking, so care should be taken especially when over provisioning the number of timeslots in the database. Reserved timeslots are never shared with DTM, if all available timeslots are allocated for reserved GPRS/EDGE DTM will be disabled until resources not required for reserved timeslots become available. The PCU shares out the backing for the switchable and DTM (64K, 32K, 16K) pro-rata to the ratio of the sum of the max_dtm_ts to the sum of the database value of switchable timeslots for the cells mapped to the PRP. In summary, DTM token has to be counted as packet resource in GPRS/EGPRS PRP and GDS resource planning.

BSS upgrade provisioning rules

Table 8-5 identifies the BSS network elements that need upgrading to support GPRS/EGPRS.

Refer to the relevant planning information for the chassis-level planning rules covering the BSC, BTS and RXCDR.
Table 8-5 BSS upgrade in support of GPRS/EGPRS Equipment Additional element BSS upgrade

BSC

Chassis (optional) Software upgrade

Add KSWs/DSW2s, LCF GPROC2s/GPROC3s/GPROC3-2s, BSP GPROC3s/GPROC3-2s, MSIs per BSC as needed in support of the Gb (where Gb is connected through the BSC), RSL, BSC-BTS traffic carrying E1 links. {28351} PSI2 or MSI needed for GDS TRAU, GDS LAPD (GSL). PT43/PBIB-ES when PSI2 cards used EGPRS enabled CTU2 radios are required. CTU2D radios on Horizon II macro also support EGPRS
Continued

BTS (Horizon II macro, Horizonmacro, M-Cell6, MCell2)

CTU2 Transceiver, with EGPRS Firmware upgrade (M-Cell6 and M-Cell2 need the CTU Adapter with the CTU2s)

68P02900W21-S 01 Feb 2007 8-13

BSS planning for GPRS/EGPRS

Chapter 8: PCU upgrade for BSS

Table 8-5 BSS upgrade in support of GPRS/EGPRS (Continued) Equipment Additional element BSS upgrade

PCU

Software upgrade

UDPROC-2s can replace DPROCs. For high capacity PCUs where more than 24 E1s are needed, it is necessary to add a second T43 patch panel to the PCUs. The upgrade kit includes a patch panel (75O or 120Q) and two cable management brackets. Besides E1, ETH is also used for GDS TRAU and GSL link when PXP/U-DPROC2 is used.

OMC-R

Software upgrade for EGPRS support

One per 64 BSS network elements, with any mix of circuit or packet (GPRS) channels supported; software in support of the PCU. Add KSWs/DWS2s, GPROC2s /GPROC3s/GPROC3-2s, MSIs per RXCDR as needed to support the Gb interface shown as option A in Figure 8-1.

RXCDR

Chassis (optional)

OMC-R planning steps and rules are beyond the scope of this manual.

Maximum BSS configuration

Table 8-6, Table 8-7 and Table 8- provide the recommended maximum BSS network parameter values in support of GPRS and EGPRS per BSS network element.

68P02900W21-S 8-14 01 Feb 2007

System Information: BSS Equipment Planning

BSS planning for GPRS/EGPRS

Table 8-6 Recommended maximum BSS network parameter values (part A) Network Element Network Parameter Maximum Value prp_fanout_mode1- 30 at any instance in time; 120 total timeslots.**** prp_fanout_mode2- 48 at any instance in time; 48 total timeslots. ****

PCU (PRP)

Air interface timeslots processing per PRP

PCU (PXP)

Air interface timeslots processing per PXP

prp_fanout_mode1- 70 at any instance in time; 280 total timeslots. **** prp_fanout_mode2- 140 at any instance in time; 140 total timeslots. ****

PCU (PICP)

PCU-SGSN (Gb) interface (GBL)

1 Gb E1 to carry frame relay channelized or nonchannelized GPRS traffic deployed over the BSC to PCU interface. The Gb E1 carries both data and signaling traffic between the PCU and SGSN. 2 (for redundancy) 1 (no redundancy) 4* 9* 12* 250***** 140***** 2

PCU PCU PCU PCU PCU PCU E1 numbers for GSL (PICP)

Maximum PSP MPROCs Maximum PICP DPROCs Maximum PRP DPROCs Maximum PXP DPROCs Number of cells supported Number of BTS sites supported Maximum physical E1s between BSC and PCU (one primary E1 and one redundant) Maximum physical ETH links between BSC and PCU Maximum number per E1 link (E1 corresponds to a quantity of thirty 64 kbit/s LAPD channels) Maximum per ETH link Maximum number of E1s per PCU Maximum number of ETHs per PCU

ETH links for GSL (PXP) LAPD-type GDS links(GSL)

12*** 30

30 36** 12***

TRAU-type GDS links

68P02900W21-S 01 Feb 2007 8-15

BSS planning for GPRS/EGPRS

Chapter 8: PCU upgrade for BSS

* The total numbers of DPROCs cannot exceed 12 in PCU. ** Maximum if all supported carriers on the PCU is EGPRS capable. PRPs can support four E1s when terminating EGPRS timeslots (4x9 PRPs = 36 E1s). ***One ETH per PXP/PSI2 pair. The maximum 12 PXP in PCU. ETH can be 100/1000 Mbit/s. ****If DTM feature is unrestricted, some timeslots per PRP are reserved for the exclusive use by DTM PDCHs. The cells supported by a PRP share a pooled total number of DTM tokens. The number of this kind of timeslots is determined by the algorithm in PCU, considering the max_dtm_ts settings in the cells processed by this PRP. ***** The number can be reached when Huge BSC is unrestricted (Refer to Chapter 6).

Table 8-7 Recommended maximum BSS parameter values (part B) Network Element Network Parameter Maximum Value

BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS)

GPRS/EGPRS carriers per cell Timeslots per carrier (GSM, GPRS and EGPRS) Users per timeslot in each direction Timeslots per active user DL Timeslots per active user UL GPRS/EGPRS timeslots per cell (total of switchable and reserved) PCU per BSC Air interface timeslots processed at any instance in time (with redundancy for PRP/PICP configuration) Air interface timeslots processed at any instance in time (with redundancy for PXP configuration)

12/21* /24** 8 4 4 2 or 4 30

BSS (BSC) BSS (PCU)

1
prp_fanout_mode1 30*8=240 prp_fanout_mode2 48*8=384 See Figure 8-3. prp_fanout_mode1 70*11=770 prp_fanout_mode2 140*11=1540 See Figure 8-6. Continued

BSS (PCU)

68P02900W21-S 8-16 01 Feb 2007

System Information: BSS Equipment Planning

BSS planning for GPRS/EGPRS

Table 8-7 Recommended maximum BSS parameter values (part B) (Continued) Network Element Network Parameter Maximum Value prp_fanout_mode1 120*8=960 prp_fanout_mode2 48*8=384 See Figure 8-3. prp_fanout_mode1 280*11=3080 prp_fanout_mode2 140*11=1540 See Figure 8-6. prp_fanout_mode1 30*9=270 prp_fanout_mode2 48*9=432 See Figure 8-4. prp_fanout_mode1 70*12=840 prp_fanout_mode2 140*12=1680 See Figure 8-7. prp_fanout_mode1 120*9=1080 prp_fanout_mode2-48*9=432 See Figure 8-4.

BSS (PCU)

Total air interface timeslots (with redundancy for PRP/PICP configuration)

BSS (PCU)

Total air interface timeslots (with redundancy for PXP configuration)

BSS (PCU)

Air interface timeslots processed at any instance in time (for PRP/PICP configuration) Air interface timeslots processed at any instance in time (for PXP configuration)

BSS (PCU)

BSS (PCU)

Total air interface timeslots (for PRP/PICP configuration)

BSS (PCU)

Total air interface timeslots (for PXP configuration)

prp_fanout_mode1 280*12=3360 prp_fanout_mode2 140*12=1680 See Figure 8-7.

*Maximum when all carriers at a BTS are EGPRS enabled. ** If VersaTRAU feature is unrestricted then the maximum number of carriers when all carriers at the BTS are EGPRS enabled can be 24.

For the mixed configuration using PXP as well as PRP, the parameter values are the capacity combination of PRP and PXP. In the field environment, there are two key statistics, CPU_Usage and PRP_LOAD, which further help in optimizing the PRP/PXP planning. These statistics are collected for an extended amount of time (representative of peak hour, during holidays and so on) such that the traffic patterns can be studied and the PRP/PXP planning can be optimized.

68P02900W21-S 01 Feb 2007 8-17

BSS planning for GPRS/EGPRS

Chapter 8: PCU upgrade for BSS

CPU_USAGE
Observing the CPU utilization of all PRP/PXPs in the PCU is an important avenue in determining whether the boards are overloaded. In a system with multiple PRP/PXPs, the load is generally balanced across all PRP/PXPs and the CPU utilization is also similar. Add a PRP or PXP in a PCU if the CPU utilization on any of the PRP/PXPs exceeds 80% during peak hours consistently.

PRP_LOAD
This statistic is used to determine the actual load on the PRP and to understand the traffic patterns in the system. This statistic reports a mean value by default, but it is important to configure the individual bins to get a finer resolution on the traffic in order to determine a change in traffic volume over time. For the PRP on the legacy DPROC, it is recommended that PRP_LOAD does not exceed a mean of 100 during the busy hour when QoS is critical. A mean value greater than 100 implies that more than 30 TS are pending service, which generally indicates that the throughput is non-optimal. This is optimal for networks that allow some PDTCH congestion level at the cells (Refer to DL_PDTCH_CONGESTION statistics). However, PRP_LOAD mean figures of 101-160 are acceptable provided that the traffic density per PDTCH on a cell level is moderate. A traffic density per PDTCH is considered moderate when DL_PDTCH_CONGESTION is low (less than 30% of the time). In this scenario, a multi-slot mobile still has good throughputs. For a MEAN PRP_LOAD exceeding 160, it is recommended to consider adding a PRP. Maintaining a MEAN PRP_LOAD over 160 results in poor throughput for the end-users as well as the trigger of rebalancing of cells across PRPs. For the PXP, the field data is required for the analysis of the right value of PRP_LOAD for PXP planning.
Table 8-8 Recommended maximum BSS network parameter (part C) Network Element Network Parameter Maximum Value

GBL links (E1s) T43 boards Cable harnesses Gb frame relay frame octet size

Maximum per PCU Maximum per PCU To connect 4 x T43 sites Maximum

4 (GPRS only),12 (PICP) or 36 (PXP)* 4 8** 2 1600 bytes

* Maximum number when EGPRS supported carriers are being employed. ** For high capacity PCUs, where more than 24 E1s are needed, it is necessary to add a second T43 patch panel to the PCUs. This number is less if VersaTRAU is unrestricted and not all EGPRS carriers are provisioned with a backhaul of 8 DS0s, and PRPs are used.

The total number of air interface timeslots supported by the PCU is affected by the fact that all of the timeslots of a cell are allocated to the same PRP or PXP board. Allocation of a part of the GPRS/EGPRS timeslots for a cell to one PRP/PXP and another part of the GPRS/EGPRS timeslots of the same cell to a different PRP/PXP is not supported. This fragmentation of the cells across PRP and PXP boards result in not all GPRS/EGPRS timeslots for a cell being assigned to a PRP/PXP and may even result in not all cells being assigned to a PRP/PXP. When planning the BSS, if the number of GPRS+EGPRS timeslots in the BSS does not exceed max_GPRS or max_EGPRS TSg, all GPRS/EGPRS timeslots of all cells are assigned to a PRP or PXP.

68P02900W21-S 8-18 01 Feb 2007

System Information: BSS Equipment Planning

BSS planning for GPRS/EGPRS

If prp_fanout_mode = 1: max GPRS/max EGPRS TSg = (nPRP * 120)+(mPXP*280) - max_GPRS_TS_cell If prp_fanout_mode = 2: max GPRS/max EGPRS TSg = (nPRP * 48)+(mPXP*140) - max_GPRS_TS_cell
Where max_GPRS/max_EGPRS TSg nPRP mPXP max_GPRS_TS_cell prp_fanout_mode Is

maximum number of GPRS/EGPRS timeslots per PCU guaranteed to be assigned to a PRP. number of PRP boards in the PCU. number of PXP boards in the PCU. number of GPRS/EGPRS timeslots in the cell in the BSS with the most GPRS timeslots. A database parameter indicating the options of PRP fanout in the PCU. All the PRP/PXPs should have the same PRP fanout mode.

E1 cable requirements for a fully configured PCU

Each PCU needs at least one interconnection panel, located on the PCU cabinet, which contains up to 4 x T43 boards. To support a maximum of 24 E1 s for a fully configured PCU, 4 x T43 boards require to be populated. With EGPRS carriers, a second interconnect panel can be added if the number of E1s is greater than 24. The number of T43 boards in the second interconnect panel is dependent on the number of E1s required. A cable harness is staged with the PCU containing 18 E1 RJ45 to RJ45 cables. A second cable harness has to be caged to hold an extra 6 E1 RJ45 to RJ45 cables.

ETH cable requirements for a fully configured PCU

Every PXP board uses an ETH RJ45 port in the RTM. The port uses a standard Category 5e patch cable.

68P02900W21-S 01 Feb 2007 8-19

PCU hardware layout

Chapter 8: PCU upgrade for BSS

PCU hardware layout

There is one PCU per BSS. Figure 8-3 shows the PCU shelf layout.
Figure 8-3 PCU shelf layout

DEFAULT LAPD LINKS TO BSC

DEFAULT LAPD LINK TO BSC

4 5

10 11 12 13 14 15 16

D P R O C

D P R O C

D P R O C

D P R O C

D P R O C

D P R O C

M P R O C A

M P R O C B

D P R O C

D P R O C

D P R O C

D P R O C

D P R O C

D P R O C

DEFAULT LAPD LINK TO BSC

DEFAULT LAPD LINKS TO BSC

16 15 14 13 12 11 10 9

4 3

D P R O C T M

D P R O C T M

D P R O C T M

D P R O C T M

D P R O C T M

D P R O C T M

H S C A

M P R O C B T M

H S C B

M P R O C A T M

D P R O C T M

D P R O C T M

D P R O C T M

D P R O C T M

D P R O C T M

D P R O C T M

68P02900W21-S 8-20 01 Feb 2007

System Information: BSS Equipment Planning

PCU hardware layout

RTMs are used for DPROCs and P (packet) RTMs for U-DPROC2s. Old and new RTMs are incompatible, and must match the DPROC type installed in the slot on the front of the shelf. the U-DPROC2 transition module has 2 GbE ports (the ETH ports). Any of the two available default LAPD link slots is used.

68P02900W21-S 01 Feb 2007 8-21

PCU shelf (cPCI)

Chapter 8: PCU upgrade for BSS

PCU shelf (cPCI)

Introduction
The PCU cabinet can hold up to three PCU (cPCI) shelves; only two PCU shelves can be fitted when EGPRS is used. Each PCU is connected to only one BSC. Each cabinet is pre-wired with a panel in the rear of the cabinet for the desired E1 termination type, balanced 120 ohm, or unbalanced 75 ohm terminations with 1500 volt lightning protection per E1.

Planning considerations
The following factors should be considered when planning the cPCI complement:

The maximum number of timeslots that can be processed at any instance in time per PCU in the fully redundant configuration (refer to Table 8-6 to Table 8-8). The maximum number of total timeslots that can be provisioned per PCU in the fully redundant configuration (refer to Table 8-6 to Table 8-8). Three fan/power supply units per cPCI shelf provide N+1 hot-swap redundancy. A minimum of two power supply units are required, with a fan-only unit required in the third location if a power supply unit is not fitted. One air filter per fan/power supply unit is required. (Total of 3 per PCU.) Each PCU cPCI shelf needs two MPROC boards for redundancy. MPROC redundancy is not required for normal PCU operation, but is necessary for the PCU to achieve high availability. Each MPROC board needs one bridge board and one transition module for a redundant MPROC configuration, or if the Web MMI feature is enabled. One alarm board per PCU is required. One main circuit breaker panel per PCU is required. There are four bays on the right side of the shelf that can be used for auxiliary equipment such as tape drives, CD-ROM drives and hard disks. The PCU is configured without any auxiliary equipment and this area of the shelf is covered with blank panels.

Table 8-9 Maximum number of timeslots that can be processed Board prp_fanout_mode=1 prp_fanout_mode=2

DPROC/PRPs or U-DPROC2/PRPs U-DPROC2/PXPs

30*8=240 70*11=770

48*8=384 140*11=1540

68P02900W21-S 8-22 01 Feb 2007

System Information: BSS Equipment Planning

PCU shelf (cPCI)

Table 8-10 Maximum number of timeslots that can be provisioned Board prp_fanout_mode=1 prp_fanout_mode=2

DPROC/PRPs or U-DPROC2/PRPs U-DPROC2/PXPs

120*8=960 280*11=3080

48*8=384 140*11=1540

If E1 connectivity is used, additional T43 modules and interconnect cables are required for the PCU cage to support 18 GDS TRAU links for GPRS and 36 GDS TRAU links for EGPRS. If ETH connectivity is used, no additional interconnects are required for GDS but are required if more than 24 Gb E1 links are needed.

68P02900W21-S 01 Feb 2007 8-23

MPROC board

Chapter 8: PCU upgrade for BSS

MPROC board
Introduction
The PCU planning process determines the type and number of MPROC boards to populate in the PCU. The PCU provisioning requirements take the MPROC redundancy solution into consideration.

PSP planning considerations

The MPROC board is used for PSP purposes. The PSP is the PCU system processor, which is a master system processor board. The PSP controls compact PCI bus synchronization and arbitration. It also performs centralized configuration and fault handling for the PCU site. If MPROC redundancy is required, each PCU cPCI shelf needs two MPROC cards (boards). The MPROC redundancy flag specified during the equipping of the PCU should be enabled. The MPROC cards should be inserted in slot 7 and 9 (see Figure 8-2). A MPROC (PSP 0) card is inserted into slot 7 and the other MPROC (PSP 1) is inserted into slot 9. The MPROC (PSP 0) in slot 7 is paired with a hot swap controller/bridge module in slot 10 and MPROC (PSP 1) in slot 9 is paired with a hot swap controller/bridge module (HSC) in slot 8. If no redundancy is required, only one MPROC card should be inserted in either slot 7 or 9 of the PCU cage. The MPROC redundancy flag specified during the equipping of the PCU should be disabled. The MPROC (PSP 0) in slot 7 is paired with a hot swap controller/bridge module in slot 10 or MPROC (PSP 1) in slot 9 is paired with a hot swap controller/bridge module (HSC) in slot 8. If both MPROCs are present but redundancy is not desired or the equip flag is disabled, the MPROC in slot 7 is the primary MPROC and is responsible for powering off the MPROC in slot 9. In this case, the MPROC in slot 9 is considered transparent. The MPROC card is a Motorola MCP820 or MCP750 microprocessor board with a TMCP700 transition module.

68P02900W21-S 8-24 01 Feb 2007

System Information: BSS Equipment Planning

DPROC board

DPROC board
Introduction
The PCU planning process determines the type and number of DPROC boards to populate in the PCU. The PCU provisioning requirements use the number of GPRS timeslots as the planning rule input. The estimation process for determining the number of GPRS timeslots is provided in GPRS/EGPRS network traffic estimation and key concepts in Chapter 3, BSS cell planning.

PICP or PRP planning considerations

DPROC board slots can be used for either PICP or PRP purposes. Each DPROC has an E1 transition module mounted in the rear of the shelf directly behind it. A DPROC can be configured as a PICP with zero, one, or two E1 PMC modules, and with PICP software. The DPROC can be configured as a PRP with either one or two E1 PMC modules, and with PRP software. The cPCI shelf supports a total of 16 cards. The redundancy MPROC boards with bridge capability occupy four slots, leaving 12 slots for PICPs or PRPs. For system availability reasons, PICPs and PRP boards should be evenly distributed between the two backplanes within the PCU shelf. The PICP/PCP provisioned boards should be populated from left to right. The left and right backplanes are connected together through the bridge board located behind the MPROC processor board. Therefore, the first PICP would occupy board slot 1, PICP 2 would occupy board slot 11, PICP 3 would be in slot 2 and PICP 4 in slot 12. PRP provisioning should also be performed in a similar fashion, alternating provisioned boards between the left and right backplanes.

PICP board
The following factors should be considered when planning the complement PICP board:

The PCU can support up to four PICP boards. A PICP board supports a maximum of two PMC modules or MSIs. The PICP boards can terminate the following links: LAPD-Type GDS links (GSL), and Gb links (GBL). But GSL and GBL cannot be resident in the same MSI.

PRP board
The following factors should be considered when planning the complement PRP board:

The PCU can support up to 10 PRP boards with the recommended maximum being 9 PRP boards. When 9 PRP boards are populated, there are three slots available for the PICP boards. PRP boards with PMCs can terminate one GDS TRAU E1 per PMC module for GPRS and two GDS TRAU E1s when configured exclusively with EGPRS carriers but cannot terminate GDS LAPD E1 links (GSL) or Gb E1 links (GBL). Each PRP board must terminate at least one GDS TRAU E1. A PRP board that does not terminate any GDS TRAU E1s has no function (PRP is always OOS when no GDS is equipped, or PRP loses normal function when all associated GDSs are OOS).

68P02900W21-S 01 Feb 2007 8-25

DPROC board

Chapter 8: PCU upgrade for BSS

Up to 120 air timeslots can be terminated on one PRP in prp_fanout_mode1 or up to 48 air timeslots can be terminated on one PRP in prp_fanout_mode2. In prp_fanout_mode1, the maximum number of air timeslots that can be assigned to a PRP is 120. The number of air timeslots that can be served at a given time interval is 30. The timeslot assignment to available PRP is load balanced by software which attempts to equally distribute the timeslots across PRPs. In prp_fanout_mode2, the maximum number of air timeslots that can be assigned to a PRP is 48. All the timeslots provisioned by a PRP can be served at any given time interval. The timeslot assignment to available PRP is load balanced by software which attempts to equally distribute the timeslots across PRPs.

The actual distribution of timeslots can be slightly different from that shown here depending on cell configurations, that is, all timeslots for a single cell must terminate on a single PRP, which can lead to slight imbalances when multiple timeslots are configured per cell. A PRP board supports up to two PMC modules.

PRP planning
The general guidelines dictate the maximum capacity of the PRP at 120 MS and/or 120 TS per board. There are two key statistics, CPU_Usage, and PRP_LOAD, which further help in optimizing the PRP planning. These statistics are collected for an extended amount of time (representative of peak hour, during holidays, and so on) such that the traffic patterns can be studied and the PRP planning can be optimized. When DTM is enabled, DTM token should be considered as packet timeslot resource in PRP planning.

CPU usage
Observing the CPU utilization of all PRPs in the PCU is an important means in determining whether the boards are overloaded. In a system with multiple PRPs, the load is generally balanced across all PRPs and the CPU utilization is similar as well. The general rule is to consider adding a PRP in a PCU if the CPU utilization on any of the PRPs consistently exceeds 80% during peak hours. This statistics reports 3 values for a given time interval - MIN, MAX and MEAN. Although the MAX value can reach 100% (for a fraction of a second at a time) this should never be used as the criteria for the load on the board. In fact, the MEAN value should be the only indicative of the PRP utilization. In addition, several days worth of data (or even weeks) can be considered in order to make a consistent decision. CPU utilization plots versus time can help observe a pattern in increased CPU utilization.

PRP load (modified per service pack 1670.27t1)

When DL_PDTCH_CONGESTION is low (less than 30% of the time), a multi-slot mobile can still use this statistic to determine the actual load on the PRP and help to understand the traffic patterns in the system. For instance, when the majority of the GPRS traffic is signaling (primarily attach/detach, PDP Context Act/Deact, Cell Update and RAUs) the PRP_LOAD is expected to be low. A PRP handling GPRS signaling traffic is expected to produce a PRP_LOAD value in the range of 5-10. However, the PRP_LOAD is higher when the PRP handles actual data transfer (WAPs, FTPs and so on).

68P02900W21-S 8-26 01 Feb 2007

System Information: BSS Equipment Planning

DPROC board

This statistic reports a MEAN value by default, but it is important to configure the individual bins to get a finer resolution on the traffic in order to determine a change of traffic volume over time when QoS is critical. A mean value greater than 100 implies that more than 30 TS are pending service, which generally indicates a non-optimal throughput. This is optimal for networks that allow some PDTCH congestion level at the cells (see DL_PDTCH_CONGESTION statistics). However, PRP_LOAD MEAN values in the range of 101-160 are acceptable if the traffic density per PDTCH on a cell level is moderate. This results in good throughputs. For a MEAN PRP_LOAD exceeding 160, it is recommended to consider adding a PRP. Maintaining a MEAN PRP_LOAD over 160 results in poor throughput for the end-users as well as the trigger of rebalancing of cells across PRPs.

PDTCH planning
The general guidelines for a new network are to configure at least 4 PDTCH/cell on the BCCCH carrier for optimizing the throughput of multi-slot mobiles that are capable of 4 TS on the DL (downlink). Configuring more than 4 TS/cell normally assumes the expectancy of high volumes of actual data traffic and the planning guidelines described in Chapter 3.
Chapter 3 apply. However, if the most of the traffic is signaling (attaches/detaches, PDP Context Act/Deact, Cell Updates, RAUs), several statistics are to be monitored to determine whether the addition of PDTCHs in a cell is required. In networks where GPRS subscriber base is widely enabled but the general data usage per subscriber is low, special consideration is required. The following statistics are useful in determining the PDTCH requirements for a cell.

DL_BUSY_PDTCH
This statistic measures the MEAN, MAX and MIN number of occupied PDTCH carrying downlink packet traffic. Normally, observing the MEAN value should be indicative of how the PDTCHs are utilized in the cell. For a more detailed PDTCH occupancy distribution, this statistics can also be configured to report 10 bins. By default, bin 0 is pegged every block period (20 ms) when no TBFs are allocated on any of the PDTCHs on the cell. Bin 1 is pegged when 1 to 2 PDTCHs are busy; bin 2 is pegged when 3 to 4 PDTCHs are busy, and so on. For example, a cell configured with 10 PDTCHs, with a MEAN value reported as 9.2 implies that all 10 configured PDTCHs are being utilized and needs a further look at the DL_PDTCH_CONGESTION statistic. However, if the MEAN is 5, the configured PDTCHs are probably underutilized and the number of PDTCHs can be reduced. Before reducing the number of PDTCHs, other statistics have to be evaluated first.

AVAILABLE_PDTCH
This statistic enables to optimize the number of switchable versus reserved TSs in a cell. If the busy hour of voice traffic does not interleave with GPRS busy hour, some TS can be configured as switchable, carrying voice traffic during CS busy hour and data traffic during GPRS busy hour.
Example:

8 of 10 TSs are configured as switchable in a cell.

DL_PDTCH_CONGESTION reports high levels of congestion (more than 30%).

The DL_BUSY_PDTCH reports a MEAN of 5.

This example illustrates a condition where TSs is stolen to handle voice traffic and therefore needs the addition of TSs to this cell to handle the GPRS traffic.

MS_CLASS_1_10_REQ
This statistic enables to determine the average number of TSs used by the average mobile on the DL and UL. Hence, it provides an indication what kind of throughput can be expected. For example, a class 10 mobile (capable of 4 DL and 2 UL TS) expects high throughputs.

68P02900W21-S 01 Feb 2007 8-27

DPROC board

Chapter 8: PCU upgrade for BSS

NO_PDTCH_AVAIL
This statistic is pegged in extreme conditions when the last switchable TS are stolen for a voice call. This condition indicates that GPRS service is not available at this time on the cell and needs a reconfiguration of switchable versus reserved TS, or the addition of TS in the cell.

DL_PDTCH_CONGESTION
This statistic is pegged when the average traffic density in a cell exceeds 2 MS/PDTCH. Although each PDTCH can interleave up to 4 MS, it is not the recommended traffic density. The congestion level in a cell is measured every block period (20 ms) but the statistic is pegged every 8 seconds (400 block periods) when the mean is calculated to determine whether the cell was congested. If the mean exceeds 2 MS/TS, it is determined that the cell was congested during the last 8 seconds. The value reported by this statistic represents the accumulated time (in ms) that the cell was congested. It is recommended that the total time a cell is congested does not exceed 30% of the busy hour time interval. Considering a 30 minutes statistics time interval, this translates to 10 minutes (value of 30000). When the majority of the GPRS traffic (higher than 90%) is known to be signaling, a congestion level of up to 50% of the busy hour statistics time interval can be allowed. Under this level of congestion and when the intended PRP_LOAD is already high (<100), t10% of subscribers who attempt to transfer data experience throughput degradation.

GBL_DL_DATA_THRPUT
This statistic is compared with the SGSN statistic to determine the actual data sent across the network that does not result from signaling traffic.

PXP planning considerations

U-DPROC2 boards are inserted in DPROC slots, which can be used for PICP, PRP or PXP purposes. DPROC board can be referred to when U-DPROC2 board is configured as PRP or PICP. The UDPROC2 board has exactly one E1 module (not configurable). It supports up to 4 E1 links providing the same connectivity as the DPROC board with 2 E1 PMC modules. The software automatically maps E1 PMC modules and span identifiers onto the correct spans of the U-DPROC2 board. When a U-DPROC2 board is configured as PXP, it has one ETH connection for GDS (GSL and TRAU Frame), and can be used to connect up to 3 E1 cables for Gb connections. The cPCI shelf supports a total of 16 cards. The redundant MPROC boards with bridge capability occupy 4 slots, leaving 12 slots for PXPs, PRPs and PICPs. To describe the maximum configuration, it is assumed that only PXPs are used. Up to 280 air timeslots can be terminated on one PXP in prp_fanout_mode1. The number of air timeslots that can be served at a given time interval is 70. The assignment of timeslot to available PXP is load balanced by software. Up to 140 air timeslots can be terminated on one PXP in prp_fanout_mode2. All the timeslots provisioned by a PXP can be served at any given time interval. The timeslot assignment to available PXP is load balanced by software. When DTM is enabled, DTM token should be considered as packet timeslot resource in PXP planning.

68P02900W21-S 8-28 01 Feb 2007

System Information: BSS Equipment Planning

DPROC board

The actual distribution of timeslots can be slightly different from that shown here depending on cell configurations, that is, all timeslots for a single cell must terminate on a single PXP, which can lead to slight imbalances when multiple timeslots are configured per cell. The statistics used for PRP planning are also applied for PXP planning.

68P02900W21-S 01 Feb 2007 8-29

PMC module

Chapter 8: PCU upgrade for BSS

PMC module
Introduction
The number of PMC modules installed depends on the number of PICP /PRP configured boards in the PCU. For the PXP (U-DPROC2), one E1 PMC module is always attached and there is no require to further consider the number of E1 PMCs fitted.

Planning considerations
The following factors should be considered when planning the PMC complement for the DPROC board:

Each PRP board needs at least one PMC module. Each PICP board has up to two PMC modules. TRAU-type GDS terminate on a PMC module in a PRP board. LAPD-type GDS (GSL) and Gb E1 (GBL) links terminate on a PMC module in PICP board and cannot share a PMC module. For GPRS, only one TRAU-type GDS per PMC module on a PRP board is allowed. The other E1 termination on the PMC module cannot be used. For EGPRS, the PRP can support two PMC modules when configured with EGPRS air timeslots, each with up to two TRAU-type GDS links. Up to two Gb E1 links (GBL) per PMC module are allowed. Up to two LAPD-type GDS E1 (GSL) links per PMC module are allowed. On the PMC NIB, the PCU can support an arbitrary mixture of 12416kbit/s TRAU, 62-32kbit/s TRAU and 62-64kbit/s (each individual DS0 that is part of a Versachannel is a single 64kbit/s TRAU channel) TRAU such that the following equation is satisfied:
#16kbit/sTS + (2 x #32kbit/sTS) + (2 x 64kbit/sDS0s) < 124

For VersaTRAU carriers (pkt_radio_type = 3), there is no one-to-one correlation between the number of air timeslots and the number of DS0s required on the backhaul so the number of DS0s should be used in the equation. The PMC NIB has sufficient CPU capacity to support a 124-16kbit/s TRAU or one full span. Since 32 kbit/s TRAU is actually composed of two 16 kbit/s TRAU channels, the PMC NIB can support half as many 32 kbit/s TRAU, or one full span. With the channelized subrate insert/extraction removed in the 64 kbit/s (VersaTRAU) TRAU, the PMC NIB can achieve twice as much bandwidth, which is 62 of the 64 kbit/s TRAU channels, or two full spans of 64kbit/s TRAU. The PMC NIB can support an arbitrary combination of 16kbit/s and 64kbit/s (VersaTRAU) TRAU channels, or channels with channelized subrate insertion/extraction and those without, trading off at a ratio of two 16kbit/s timeslots to one 64kbit/s timeslot. When mixed traffic is used, the two spans on the PMC NIB are not fully utilized.

68P02900W21-S 8-30 01 Feb 2007

System Information: BSS Equipment Planning

(Packet) Rear Transition Module

(Packet) Rear Transition Module

Introduction
The number of rear transition modules installed depends on the number of PICP /PRP/PXP boards configured in the PCU.

Planning considerations
The following factors should be considered when planning the number of rear transition modules required:

One rear transition module is required per PRP board. One rear transition module is required per PICP board. One packet rear transition module is required per PXP board.

The rear transition module type must match the board type used in the corresponding card slot in the front of the shelf.

68P02900W21-S 01 Feb 2007 8-31

PCU equipment redundancy and provisioning goals

Chapter 8: PCU upgrade for BSS

PCU equipment redundancy and provisioning goals

Support for equipment redundancy
The PCU supports four types of redundancy:
2N

1MPROC/bridge board pair (non-redundant), 2 MPROC/bridge board pairs (redundant).

N+1

2PS/FAN units (non-redundant), 3 PS/FAN unit (redundant). (always 3 fan units required)
Load shared

The signaling data on the GSL and GBL are load shared across the available links. Provisioning more links than is required in the event of a failure creates seamless redundancy. The GSL and GBL use a routing algorithm to dynamically balance the load across all available links. The individual GSL and GBL links can be distributed across the available PICPs/PXPs. In the event of a PICP/PXP failure, the remaining PICP(s)/PXP(s) if equipped will process the signaling load.
Load balanced

The air timeslots on the GDS links are terminated on a PRP/PXP board. The PCU automatically balances the number of air timeslots across the available PRP/PXPs. In the event of a GDS link failure, the BSC and PCU attempt to move the air timeslots to another available GDS link. In the event of a PRP/PXP failure, all the air timeslots on the failed PRP/PXP are moved to other PRP/PXPs if adequate resources are available.

PCU equipment redundancy planning

Three types configuration are supported in GSR9. The first one includes PRPs/PICPs as legacy configuration. The second is a new configuration with only PXPs. The third is a combination of PICP/PRP and PXP.

PRP/PICP configure
For redundant PCU operation, the PCU should be planned such that there are sufficient boards provisioned as shown in Figure 8-4, that is, only eight PRP boards and two PICP boards are required to handle the expected maximum GPRS traffic load. The ninth PRP board and third PICP board offer the extra capacity to provide redundancy in the event of a PRP or PCIP failure. The third PICP board provides redundancy for the software processes that run on the first two PICP boards. The GDS TRAU E1 (GDS) link redundancy is obtained by calculating the number of PRP boards required and then adding an additional PRP board. The GSL E1 link redundancy is obtained by provisioning a second GSL E1. The PCU load-balances across the LAPD GSL links. If a PRP or PICP board fails, the PCU automatically re-distributes the load to the other boards in service.

68P02900W21-S 8-32 01 Feb 2007

System Information: BSS Equipment Planning

PCU equipment redundancy and provisioning goals

Two Gb E1s (GBL) are required to handle the traffic for a fully configured PCU. Gb E1 link resiliency is obtained by adding an additional two Gb E1s and load balancing across all of the Gb E1s. The number of GBLs is increased to 12 per PCU when EGPRS carriers are equipped. The PRP and PICP (DPROC) boards are hot swappable so that when a board failure is detected, a replacement board may be inserted without disrupting ongoing GPRS traffic on the other boards. The DPROC must be locked before removal and unlocked after board insertion. The PRP and PICP boards have associated transition module boards. There is an associated redundant transition module board with each redundant PRP and PICP board. The PCU shelf hardware allows for N+1 MPROC board redundancy. This N+1 redundancy capability is subject to MPROC redundancy software availability. The MPROC board(s) and the MPROC bridge boards are not shown in Figure 8-4 or Figure 8-5, but the redundant MPROC has an associated redundant bridge board. The PCU shelf comes with N+1 power supply/fan redundancy. The power supplies are hot swappable. The power supply/fan units are not shown in Figure 8-4 and Figure 8-5. The PCU architecture offers a considerable degree of provisioning flexibility. Figure 8-4 and Figure 8-5 demonstrate this flexibility where the provisioning goals range from full redundancy (as shown in Figure 8-4) to maximum coverage (as shown in Figure 8-5 for GPRS and Figure 8-6 for EGPRS).
Table 8-11 summarizes the provisioning goals demonstrated with Figure 8-4, Figure 8-5 and Figure 8-6. Figure 8-4 Provisioning goals (full redundancy)

Refer to Table 8-11 for a matrix of provisioning goals achieved with this instance of PCU provisioning.

68P02900W21-S 01 Feb 2007 8-33

PCU equipment redundancy and provisioning goals

Chapter 8: PCU upgrade for BSS

Figure 8-5 Provisioning goals (Maximum coverage)

Refer to Table 8-11 for a matrix of provisioning goals achieved with this instance of PCU provisioning.

Figure 8-5 shows 18 GDSs, as required for CS3/CS4. Only 9 GDSs are required for CS1/CS2.

68P02900W21-S 8-34 01 Feb 2007

System Information: BSS Equipment Planning

PCU equipment redundancy and provisioning goals

Figure 8-6 EGPRS maximum throughput and coverage, full redundancy not required

The number of GDS links per PRP is decreased to 2 for PRP fanout mode 2. Refer to Table 8-11 for a matrix of provisioning goals achieved with this instance of PCU provisioning.

68P02900W21-S 01 Feb 2007 8-35

PCU equipment redundancy and provisioning goals

Chapter 8: PCU upgrade for BSS

Table 8-11 Provisioning goals (per PCU) Metric Goal

GPRS maximum coverage with redundant configuration (Figure 8-4). Number of timeslots processed at any instance in time Total number of provisioned timeslots at a BSS Number of MPROCs Number of PRPs Number of PICPs Number of TRAU-Type GDS E1s Number of LAPDType GDS (GSL)E1s Number of GbE1s MPROC board redundancy PRP board redundancy PICP board redundancy GDS TRAU E1 redundancy GSL E1 redundancy Gb E1 redundancy 4 Yes Yes Yes Yes Yes Yes Mode 1: 240(30*8) Mode 2: 384(48*8) Mode 1: 960(120*8) Mode 2: 384(48*8) 2 8 2 18

GPRS maximum coverage, redundancy not required (Figure 8-5). Mode 1: 270(30*9) Mode 2: 432(48*9) Mode 1: 1080(120*9) Mode 2: 432(48*9) 1 9 2 18

EGPRS maximum coverage, redundancy not required (Figure 8-6). Mode 1: 270(30*9) Mode 2: 432(48*9) Mode 1: 1080(120*9) Mode 2: 432(48*9) 1 9 3 36**

4 No No No No Yes Yes

8 No No* No* No* Yes Yes

68P02900W21-S 8-36 01 Feb 2007

System Information: BSS Equipment Planning

PCU equipment redundancy and provisioning goals

* Capacity does not meet calculated maximums in the event of a failure. This can or cannot affect customer usage dependant on the current load of the system. ** The maximum number of GDS resources can be less if VersaTRAU is unrestricted and EGPRS carriers are equipped with less than 8 DS0s of backing on the backhaul.

PXP configuration
For redundant PCU operation, the PCU should be planned such that there are sufficient boards provisioned as shown in Figure 8-7, that is, only 11 PXP boards are required to handle the expected maximum GPRS traffic load. The 12th PXP board offers the extra capacity to provide redundancy in the event of a PXP failure. When PXP is configured, Ethernet connectivity is required between BSC (PSI2) and PCU (PXP). Both GDS TRAU and GDS LAPD can be carried by ETH link. GDS (TRAU and LAPD) redundancy is obtained by equip one more PXP board than the number of PXP boards actually required. If a PXP board fails, the PCU automatically re-distributes the load to the other boards in service. Each PXP can support 3 E1 links, used to transfer Gb (GBL) traffic. Gb E1 link resiliency is obtained by adding an additional PXP and load balancing across all of the Gb E1s. PCU can support 36 Gb when used with full PXP configuration. The PXP boards have associated packet rear transition module boards not shown in the figures . There is an associated redundant packet rear transition module board with each redundant PXP board. The redundancy of MPROC, power supply and fan is same as description in PRP/PICP configure. The PCU architecture offers a considerable degree of provisioning flexibility. Figure 8-7 and Figure 8-8 demonstrate this flexibility where the provisioning goals range from full redundancy (as shown in Figure 8-7) to maximum coverage (as shown in Figure 8-8 for GPRS/EGPRS).
Table 8-12 summarizes the provisioning goals demonstrated with Figure 8-7 and Figure 8-8.

68P02900W21-S 01 Feb 2007 8-37

PCU equipment redundancy and provisioning goals

Chapter 8: PCU upgrade for BSS

Figure 8-7 Provisioning goals (full redundancy)

Refer to Table 8-12 for a matrix of provisioning goals achieved with this instance of PCU provisioning.

68P02900W21-S 8-38 01 Feb 2007

System Information: BSS Equipment Planning

PCU equipment redundancy and provisioning goals

Figure 8-8 Provisioning goals (maximum coverage)

Refer to Table 8-12 for a matrix of provisioning goals achieved with this instance of PCU provisioning.

68P02900W21-S 01 Feb 2007 8-39

PCU equipment redundancy and provisioning goals

Chapter 8: PCU upgrade for BSS

Table 8-12 Provisioning goals (per PCU) Metric Goal

GPRS maximum coverage with redundant configuration (Figure 8-6) Number of timeslots processed at any instance in time
prp_fanout_mode1- 770 (70*11) prp_fanout_mode21540 (140*11) prp_fanout_mode13080(280*11) prp_fanout_mode21540(140*11)

GPRS maximum coverage, Redundancy not required (Figure 8-7)

prp_fanout_mode1840(70*12) prp_fanout_mode21680(140*12) prp_fanout_mode13360(280*12) prp_fanout_mode21680(140*12)

Total number of provisioned timeslots at a BSS

Number of MPROCs Number of PXPs Number of TRAU-LAPD GDS ETHs* Number of Gb E1s MPROC board redundancy PXP board redundancy GDS/GSL ETH redundancy Gb E1 redundancy

2 11 11 3*11=33 Yes Yes Yes Yes

1 12 12 3*12=36 No No Yes Yes

* Capacity does not meet calculated maximums in the event of a failure. This can or cannot affect customer usage dependent on the current load of the system.

Upgrading the PCU

The PCU can be incrementally upgraded for additional capacity, by adding one PXP board, PRP board or by one PICP board at a time. Table 8-13 and Table 8-14 show different upgrade scenarios based on the number of timeslots supported by PXP or PRP and redundancy required. The actual number of boards and links required is based upon the formulas in this chapter.

Table 8-13 shows maximum configurations for all DPROC boards configured into PRP. All the PRPs in the PCU should have the same setting of prp_fanout_mode.

68P02900W21-S 8-40 01 Feb 2007

System Information: BSS Equipment Planning

PCU equipment redundancy and provisioning goals

Table 8-13 Upgrade scenarios for PRP configuration Number of air timeslots* No. of PRP No. of PICP No. of GDS No. of GBL No. of GSL Total links Remarks

Mode 1-120 Mode 2-48

Mode 1-4 Mode 2-2

Mode 1-8 Mode 2-6

Minimum. configuration, no redundancy No Gb redundancy With redundant links With redundant links With redundant links No Gb redundancy with redundant links with redundant links with redundant links with redundant links with redundant links

Mode 1-240 Mode 2-96 Mode 1-240 Mode 2-96 Mode 1-360 Mode 2-144 Mode 1-480 Mode 2-192 Mode 1-600 Mode 2-240 Mode 1-600 Mode 2-240 Mode 1-720 Mode 2-288 Mode 1-840 Mode 2-336 Mode 1-960 Mode 2-384 Mode 1-1080 Mode 2-432

2 2

1 2

Mode 1-8 Mode 2-4 Mode 1-8 Mode 2-4 Mode 1-12 Mode 2-6 Mode 1-16 Mode 2-8 Mode 1-20 Mode 2-10 Mode 1-20 Mode 2-10 Mode 1-24 Mode 2-12 Mode 1-28 Mode 2-14 Mode 1-32 Mode 2-16 Mode 1-36 Mode 2-18

2 6

2 2

Mode 1-12 Mode 2-8 Mode 1-16 Mode 2-12 Mode 1-20

Mode 1-24 Mode 2-16 Mode 1-24 Mode 2-14 Mode 1-28 Mode 2-18 Mode 1-36 Mode 2-24 Mode 1-40 Mode 2-26 Mode 1-44 Mode 2-28 Mode 1-48 Mode 2-30

5 5

1 2

2 6

2 2

10

10

10

10

* All air timeslots are assumed to be EGPRS capable and assumed to have a backing on the backhaul of 64kbit/s/air timeslot. If VersaTRAU is unrestricted, the number of GDS resources is between 18 and 36 and depends on the number of DS0s equipped for each EGPRS RTF on the backhaul.

68P02900W21-S 01 Feb 2007 8-41

PCU equipment redundancy and provisioning goals

Chapter 8: PCU upgrade for BSS

Table 8-14 shows maximum configurations for all DPROC boards configured into PXP. All the PXPs in the PCU should have the same setting of prp_fanout_mode. Table 8-14 Upgrade scenarios for PXP configuration Number of air timeslots* Number of PXP Number of GDS(TRAU_LAPD) Number of GBL Remarks

Mode 1-280 Mode 2-140 Mode 1-560 Mode 2-280 Mode 1-840 Mode 2-420 Mode 1-1120 Mode 2-560 Mode 1-1400 Mode 2-700 Mode 1-1680 Mode 2-840 Mode 1-1960 Mode 2-980 Mode 1-2240 Mode 2-1120 Mode 1-2520 Mode 2-1260 Mode 1-2800 Mode 2-1400 Mode 1-3080 Mode 2-1540 Mode 1-3360 Mode 2-1680

Minimum configuration, no redundancy with redundant links with redundant links with redundant links with redundant links with redundant links with redundant links with redundant links with redundant links with redundant links with redundant links with redundant links

2 3 4 5 6 7 8 9 10 11 12

2 3 4 5 6 7 8 9 10 11 12

6 9 12 15 18 21 24 27 30 33 36

*For mixed configuration using PRP as well as PXP, the capacities of PRP and PXP have to be considered when upgrading for the additional capacity.

68P02900W21-S 8-42 01 Feb 2007

System Information: BSS Equipment Planning

E1 link/ETH link provisioning for GPRS and EGPRS

E1 link/ETH link provisioning for GPRS and EGPRS

E1 interface provisioning
The BSC to PCU E1 links should not go through any network elements. The E1 links should meet the ITU-T Recommendation G.703. This recommendation includes E1 length specification. The PCU is configured for E1 loop timing recovery on all of the PCU E1 interfaces. The PCU is connected directly to the BSC E1 interfaces and the BSC is configured to provide the E1 master clock. If the PCU attaches to a GSN that does not have a master clock source, an interface piece of equipment, such as a Digital Cross Connect switch (DACs) that does have a master clock source, should be used. The Motorola BSC and RXCDR equipment can be used in place of DACs for this purpose.

E1 Planning considerations
The following factors should be considered when planning the E1 interfaces and links if all DPROCs are equipped as PRP/PICP:

GDS TRAU E1
On the PMC NIB, the PCU can support an arbitrary mixture of 124 16 kbit/s TRAU, 62 32 kbit/s TRAU and 62 64kbit/s (VersaTRAU DS0s) TRAU such that the following equation is satisfied:
#16kbit/sTS + (2 x #32kbit/sTS) + (2 x 64kbit/sDS0s) < 124

PCU GDS E1
There can be up to 18 TRAU-type GDS E1 links per PCU for GPRS and 36 TRAU-type GDS E1 links per PCU for EGPRS.

When GPRS is configured, each PMC on a PRP supports one E1 link. If EGPRS is configured, each PMC can support two E1 links. However, the second E1 can only be used for EGPRS.

GSL LAPD (GSL) E1

The GSL traffic is load balanced over all GSLs. Each E1 carries up to 30 LAPD links. For LAPD-type GDS resiliency, two E1s are recommended, regardless of the number of LAPD channels required. For example, if only one channel is required to carry the expected signaling load, two E1s with one LAPD channel per E1 should be used. The MPROC load balancing software distributes the load evenly between the two LAPD channels.

PCU Gb E1 (GBL)
There can be up to 4 Gb E1s per PCU for GPRS and 12 Gb E1s per PCU for EGPRS.

68P02900W21-S 01 Feb 2007 8-43

E1 link/ETH link provisioning for GPRS and EGPRS

Chapter 8: PCU upgrade for BSS

Ethernet interface provisioning

{28351}In GSR9, High bandwidth interconnection between BSC and PCU is provided. This capability introduces Ethernet connectivity between BSC (PSI2) and PCU (PXP). One PSI2/PXP pair supports one ETH link. Up to 12 Ethernet links can be supported between BSC and PCU. These links can run either in 1000BASE-TX or 100BASE-T modes.

PCU GDS (TRAU-LAPD)

With ETH link introduced, a new type of GDS (TRAU-LAPD) can be equipped. This kind of GDS can carry both TRAU and LAPD (GSL) simultaneously on ETH link. The traffic load of GDS on one link depends on the capacity of PXP. The number of PDCH for one PXP is 280 for prp_fanout_mode1 and 140 for prp_fanout_mode2. The maximum number of GSL on one link is 30. 60 GSLs can be equipped for the PCU. When multiple ETH links exist, it is recommended to equip GSLs evenly on different links for resiliency. GDS (TRAULAPD) supports N + M redundancy. Signaling and traffic load is shared among in-service ETH links. If one (pair) fails, the load is redistributed among the remaining in-service links.

PCU Gb (E1)
Every PXP can support 3 Gb (E1) links. There can be up to 36 Gb E1s per PCU for GPRS/EGPRS. When multiple PXPs exist, it is recommended to equip Gb E1s evenly on different PXPs for resiliency.

GPROC LCF
The GPROC LCFs available at the BSC terminate up to 12 LAPD channels. Up to 60 LAPD-type links can be provisioned at the PCU. The LAPD links can be distributed on the LCF automatically, based on the capacity available on the LCFs.

Either the GPROC2 or the GPROC3/GPROC3-2 can perform LAPD-type link processing.

68P02900W21-S 8-44 01 Feb 2007

System Information: BSS Equipment Planning

QoS capacity and QoS2 impact

QoS capacity and QoS2 impact

The QoS feature retains the 120 mobile per PRP board limit from previous loads. However, this feature can affect the overall capacity of the PRP and PXP board. Each PRP/PXP board has a capacity in terms of MTBR. When that capacity is reached, no more non-STNNT mobiles or PFCs can be admitted without preempting other PFCs first. There is a trade-off between the number of mobiles being serviced and the MTBR of the PFCs of the mobiles being serviced. If the MTBR of the various traffic classes are set to high values, or there are multiple PFCs per mobile, fewer mobiles can be serviced per PRP/PXP board. A simple example is when there is only one GPRS timeslot equipped and in-service, and a high ARP value PFC is allocated a single timeslot of MTBR (calculated from coding scheme and MTBR) for its use. Additional non-STNNT PFCs of equal or lower ARP value cannot be assigned to that timeslot without compromising the service of the first high ARP value PFC and are subsequently rejected. Four mobiles can be allocated on each PDTCH provided there is sufficient available throughput. When the BSS is managing its pool of MTBR resources, it reserves headroom (16.7%), that is, it does not allocate 100% of its resources in terms of MTBR commitments. The purpose of the headroom is to reserve some throughput in the system so that each PFC has a high probability of meeting its MTBR regardless of coding scheme changes and to allow short term PFCs (such as PAP and STNNT) to enter the system. The headroom is managed on two distinct levels:

The first level of headroom is at local timeslot zone. The BSS reserves headroom within a local zone of timeslots such that coding scheme changes by any mobile within that local zone of timeslots, or addition of a STNNT or PAP mobile to that local zone of timeslots, does not affect the ability of the mobiles within that local zone of timeslot to meet their MTBR requirements. The second level of headroom is at the PRP/PXP board. This is headroom on the PRP/PXP board's ability to service 30/70 timeslots per block period of throughput (assume it is mode1). Some of this throughput is reserved for coding scheme changes, and STNNT and PAP mobiles.

When admitting a new mobile, the BSS verifies that there is sufficient headroom at both of these levels. If there is insufficient headroom to admit the new mobile, other mobiles can be downgraded and/or preempted and the requesting mobile can also be downgraded or rejected. The amount of MTBR throughput that is available on each timeslot to commit to the mobiles is a function of the number of mobiles scheduled on that timeslot. In the maximum case, 8 kbit/s of MTBR can be allocated for GPRS and 14 kbit/s for EGPRS per timeslot. This maximum value is used for all the capacity calculations . GSR9 provides a more optimistic estimation. The bandwidth can be obtained from configurable parameters (egprs_init_dl_cs, egprs_init_ul_cs, init_dl_cs, init_ul_cs). Default value is CS2 (12 kbit/s) and MCS3 (14.8 kbit/s). To determine the overall MTBR capacity of a PRP board, both levels of headroom must be considered. The most constricting of these levels of headroom determines the overall capacity of the PRP board. Table 8-13 shows the summation of the headroom of all of the local timeslot zones on a PRP board for the downlink and the uplink as well as the corresponding summation of the MTBR throughputs (or committable throughput) of all the timeslot zones on the PRP board. It is important to NOTE that for these calculations it is assumed there are multislot class 1 mobiles (each using a single uplink and downlink timeslot) and 4 mobiles scheduled per timeslot (allowing 8 kbit/s committable bandwidth per slot). The local timeslot zone headroom is a function of the coding scheme in use but the MTBR throughput of the PRP board is independent of the coding schemes used.

68P02900W21-S 01 Feb 2007 8-45

QoS capacity and QoS2 impact

Chapter 8: PCU upgrade for BSS

Table 8-15 takes the coding schemes allowed on a timeslot (for all timeslots) and calculates a Local Timeslot Zone Level MTBR throughput summed over all timeslots equipped on the PRP board. By dividing the summation of the local timeslot zones (the available MTBR commitment) by the commitment made to each mobile (2 kbit/s) the theoretical limitation based on this restriction is calculated. It is clear from this example that the Local Timeslot Zone Level Headroom, when there are 120 timeslots equipped on the board and mobiles with only 1 timeslot and 2 kbit/s MTBR requirements, will not be the restricting factor as the 120 mobile per board restriction is more constraining. When PXP board is used, 280 mobiles can be supported. When FR28000 is enabled, mode1 and mode2 are 30/120(70/280) or 48/48(140/140). Table 8-15 Local Timeslot Zone Level capacity 4MS/PDTCH Parameter Coding scheme CS-1/2 CS-3/4 EGPRS

Peak throughput per TS (bit/s) Local timeslot zone MTBR throughput per TS (bit/s) Local timeslot zone total headroom (%) Number of timeslots equipped Summation of local timeslot zone level MTBR throughput over PRP (bit/s) Theoretical limitation based solely on local timeslot zone restriction Max MS at 2 kbit/s/MS Local timeslot zone Maximum MS at 2 kbit/s/MS

12000 8000 33.3 120 960000 480 120

20000 8000 60.0 120 960000 480 120

59200 8000 86.5 120 960000 480 120

Table 8-16 shows the PRP board service headroom and corresponding PRP board service level MTBR throughput. The PRP board service headroom and corresponding PRP board service throughputs are both a function of the actual coding schemes of the mobiles on the board at the moment, (that is, the MTBR or committable throughput of the board is higher when higher coding schemes are in use on the board). It is important to NOTE that for these calculations it is assumed there are multislot class 1 mobiles (each using a single uplink and downlink timeslot) and 4 mobiles scheduled per timeslot (allowing 8kbit/s committable bandwidth per slot). CS-1 is the worst case. Table 8-16 PRP Board Service Level Capacity 4MS/PDTCH Parameter Coding scheme CS-1 CS-1/2 CS-3/4 EGPRS

Peak throughput per TS (bit/s) Number of PDCH every block period (PRP board, 30/120 mode) Local timeslot zone MTBR throughput Local timeslot zone total headroom (%) Summation of local timeslot zone level MTBR throughput over PRP (bit/s) Theoretical limitation based solely on local timeslot zone restriction Maximum MS at 2 kbit/s/MS Local timeslot zone Maximum MS at 2 kbit/s/MS

8000 30 240000 16.7 200000 100

11200 30 336000 16.7 280000 140

15360 30 460800 16.7 384000 192

25120 30 753600 16.7 628000 314

100

120

120

120

68P02900W21-S 8-46 01 Feb 2007

System Information: BSS Equipment Planning

QoS capacity and QoS2 impact

Table 8-16 takes the current throughput per timeslot and calculates a PRP board service level MTBR based on the requisite headroom. By dividing the PRP Board Service level MTBR throughput (the maximum committable bandwidth) by the commitment per mobile (2 kbit/s MTBR), a theoretical maximum limitation is calculated. In all but the worst-case scenario (all mobiles experiencing CS-1), the board level Service Capacity is not the limiting factor in the number of mobiles supported per board. The 120 mobile per board limit is the constraining factor. While considering the overall PRP capacity, the PRP service level headroom usually limits the number of mobiles on the PRP board, that is, as long as there are multiple cells on the PRP board. For example, if the MTBR is set to 6 kbit/s in both uplink and downlink for all traffic classes, interleaving is limited to one mobile per timeslot in the uplink and mobiles with multiple slots in the downlink. At the timeslot zone level, 120 mobiles are allowed onto the PRP board. However, at the PRP board service level, in the worst case (all CS-1), only 30 mobiles can be admitted to the PRP board. With a combination of 20% CS-1 and 80% CS-2, 70 mobiles can be admitted. With 20% CS-1, 40% CS-3 and 40% CS-4, 60 mobiles can be admitted.

MTBR allocation
The BSS attempts to maintain its MTBR commitments to PFCs in the order of priority by ARP Value. In other words, PFCs of a higher ARP Value are more likely to get access to the system and get their requested MTBR. The BSS attempts to ensure the ARP Value ordering of MTBR commitments through downgrading and pre-emption.

Per timeslot commitment

The BSS commits a maximum of 6 kbit/s of MTBR in the downlink and in the uplink per GPRS timeslot on the air interface (and 12 kbit/s per EGPRS timeslot) when there are less than four mobiles allocated on the timeslot. This maximum commitment per timeslot is independent of the type of backhaul or the current coding schemes of the mobiles. The remaining throughput on the timeslot the commitment is headroom and is allocated to the mobiles according to their THP weights. For timeslots that are configured as PCCCH timeslots, the BSS commits 0 kbit/s of MTBR. PCCCH timeslots share both user data and control signaling. Therefore, the BSS does not make any MTBR commitments on the PCCCH timeslot. There could be a large amount of control signaling transmitting (which has higher priority than user data) that would not allow the BSS to maintain MTBR on this timeslot. In order to admit 4 mobiles per timeslot (required to satisfy 120 mobiles per PRP board), some of the headroom on each timeslot can be used to admit a fourth mobile on to a timeslot, effectively increasing the committable bandwidth on that GPRS timeslot to 8 kbit/s (and 14 kbit/s per EGPRS timeslot). This increase only occurs to admit a fourth mobile and is not done for any other number of mobiles on the timeslot, as using this headroom allows individual PFCs to operate further from prescribed MTBR within the tolerance band, as dictated by PDAK polling rates. This timeslot MTBR commitment forms the basis for the MTBR allocation. The headroom allows the MTBR commitments to be maintained regardless of any coding scheme changes made by the mobile. Each traffic class has an associated MTBR that is configurable by the operator, or is fixed at zero. Within the interactive traffic class, each THP has its own associated MTBR that is configurable by the operator. The MTBR of THP 2 must be less than or equal to the MTBR of THP 1, and the MTBR of THP 3 must be less than or equal to the MTBR of THP 2. For all traffic classes except for interactive THP 1 and interactive THP 2, the maximum MTBR can be fit into a single timeslot allocation no matter how the MTBR is set. This guarantees that these classes are not rejected by the system when timeslots are idle in the cell and available throughput exists on the PRP board.

68P02900W21-S 01 Feb 2007 8-47

QoS capacity and QoS2 impact

Chapter 8: PCU upgrade for BSS

Within the interactive traffic class, the THP 3 class has a maximum MTBR that can be fit into a single timeslot allocation no matter how the MTBR is set. This means that a THP 3 is not rejected by the system when timeslots are idle in the cell and available throughput exists on the PRP board. THP 1 and THP 2 both support a maximum MTBR of 24 kbit/s in the downlink and 6 kbit/s in the uplink. THP 1 and THP 2 are downgradable to THP3 so that they can be fit into a single timeslot and thus are not rejected by the system when timeslots are idle in the cell and available throughput exists on the PRP board.

Per mobile commitment

The BSS limits its MTBR commitment to a mobile to a value that the mobile is capable of supporting. In GSR8, the BSS allocates no more than 6 kbit/s per timeslot to the mobile in each direction (UL/DL). If the mobile does not support enough timeslots in the downlink direction to support the MTBR of its requested THP, which can only happen for interactive THP 1 and 2, the mobile is downgraded. In GSR9, the BSS allocates resource according to initial coding scheme (it is configurable) and negotiation number of timeslot. See Table 8-17 for maximum MTBR in downlink and uplink for each multislot class. m stands for bitrate (kbit/s) that one timeslot provides using a coding scheme. For example, in GSR8, m always is set to 6 kbit/s, in GSR9, m = 9.2 for CS1, m = 13.6 for CS2.
Table 8-17 Maximum MTBR in UL/DL per multislot capability Mobile multislot class Multislot class supported Possible configure Maximum MTBR (uplink) Maximum MTBR (downlink)

1 2 4 5 6

1 2 4 5 6

1 uplink timeslot 1 downlink timeslot 1 uplink timeslot 2 downlink timeslots 1 uplink timeslot 3 downlink timeslots 2 uplink timeslots 2 downlink timeslots 2 uplink timeslots 2 downlink timeslots or 1 uplink timeslot 3 downlink timeslots 1 uplink timeslot 4 downlink timeslots 2 uplink timeslots 3 downlink timeslots 1 uplink timeslot 4 downlink timeslots or 2 uplink timeslots 3 downlink timeslots

m m m m m

m 2m 3m 2m 2m

8 9 10

8 9 10

m m m

4m 3m 3m

Continued

68P02900W21-S 8-48 01 Feb 2007

System Information: BSS Equipment Planning

QoS capacity and QoS2 impact

Table 8-17 Maximum MTBR in UL/DL per multislot capability (Continued) Mobile multislot class Multislot class supported Possible configure Maximum MTBR (uplink) Maximum MTBR (downlink)

11

11

Class 10 or 3 uplink timeslots 2 downlink timeslots Class 10 or 4 uplink timeslots 1 downlink timeslot

2m

12

12

Biasable mobile commitment

The BSS limits its MTBR commitment to a biasable mobile (multislot classes 6 and 10, and any that map to these classes) to the maximum MTBR allowed per timeslot multiplied by the number of timeslots that are fixed in each direction. Thus, multislot class 6 is committed at most 12 kbit/s (2 timeslots) in the downlink and 6 kbit/s (1 timeslot) in the uplink, and class 10 is committed at most 18 kbit/s (3 timeslots) in the downlink and 6 kbit/s (1 timeslot) in the uplink

Per timeslot zone commitment

The BSS limits its MTBR commitment to a timeslot zone to 6 kbit/s of MTBR in the downlink and in the uplink per timeslot in that timeslot zone unless a fourth mobile is scheduled on that timeslot. When scheduling the fourth mobile on a timeslot, the BSS allows a commitment to be 8 kbit/s on all timeslots where there are four mobiles assigned.

Per PRP board commitment

The BSS limits its MTBR commitment to a PRP to 25 active timeslots of throughput in either direction. The remaining 5 timeslots are reserved as headroom for STNNT and PAP mobiles and for coding scheme changes. The total committable bandwidth is a function of the coding schemes of the mobiles on the board.

PRP-PDTCH QoS planning

The maximum number of PDTCHs to assign per PRP based on the information provided in QoS capacity and QoS2 impact is calculated using the following steps:

Calculate the PRP board throughput based on coding schemes used while subtracting PRP board headroom. Calculate the average downlink MTBR to determine the amount to reserve for each QoS subscriber. Divide the PRP board throughput by the average downlink MTBR to determine the MAX_QOS_PDTCHS_PER_PRP.

68P02900W21-S 01 Feb 2007 8-49

QoS capacity and QoS2 impact

Chapter 8: PCU upgrade for BSS

Calculating PRP board throughput

PRP board throughput is calculated as follows:

PRP BOARD THROUGHPUT = THRUPUT_TS * {(8000 * %CS1_USAGE) + (12000 * %CS2_USAGE) + (14400 * %CS3_USAGE) + (20000 * %CS4_USAGE) + (8800 * %MCS1_USAGE) + (11200 * %MCS2_USAGE) + (14800 * %MCS3_USAGE) + (17600 * %MCS4_USAGE) + (22400 * %MCS5_USAGE) + (29600 * %MCS6_USAGE) + (44800 * %MCS7_USAGE) + (54400 * %MCS8_USAGE) + (59200 * %MCS9_USAGE) } * (100% 16.7%)
Where Is

THRUPUT_TS

the maximum TS worth of throughput that can be supported per PRP/PXP depending on deployment and mode. the percentage of time the relevant coding scheme is used by subscribers in the cells attached to a given PCU.

%CS1_USAGE %CS2_USAGE %CS3_USAGE %CS4_USAGE %MCS1_USAGE %MCS2_USAGE %MCS3_USAGE %MCS4_USAGE %MCS5_USAGE %MCS6_USAGE %MCS7_USAGE %MCS8_USAGE %MCS9_USAGE

Calculating average downlink EGBR

The EGBR is the additional throughput that is allocated to a operator that is sufficient to service the GBR and the transfer delay requirements of the streaming service. EGBR is defined as GBR/, where is a value between 0 and 1. In order to find the average downlink EGBR the minimum value for must first be found. Average downlink Streaming EGBR is calculated as follows:

STR_EGBR = Average_GBR/ * (1 + BLER)

BLER is typically 10%-15%. The value of is dependent on the transfer delay parameter for the streaming service. The minimum transfer delay that the PCU supports is user configurable. For planning purposes this value of minimum transfer delay is used to determine the value of .

68P02900W21-S 8-50 01 Feb 2007

System Information: BSS Equipment Planning

QoS capacity and QoS2 impact

For a given GBR, the value of is dependent on the transfer delay parameter for the streaming service. The minimum transfer delay that the PCU supports is user configurable. For planning purposes this value of minimum transfer delay is used to determine the value of . In order to determine the value of to use, first obtain the weighted average GBR per service in the network. This is obtained by multiplying the frequency of the service in the network by the GBR of the service.

AverageGBR =

GBRi * FSi/STRi
i =1

Where

Is

N GBRi FSi STRi

the number of streaming services types in the network the GBR of streaming service i. The percentage of streaming service i in service mix of subscribers in a given PCU. the percentage of total streaming service in service mix of subscribers in a given PCU.

Look up at the Average GBR value in the tables to obtain the value. The table provides the minimum value of for a given minimum transfer delay supported in the PCU, in networks where the majority of streaming services have GBR of 15 kbit/s or lower, for example, PoC. In practice, where an application does not need a stringent transfer delay, is larger for that application, resulting in less EGBR required for a particular GBR. The default minimum transfer delay value has been set to 500ms resulting in = 0.62.
Table 8-18 for various transfer delays at GBR 15kbit/s or less Min Transfer delay (ms) Min Transfer delay (ms) Min Transfer delay (ms)

250 300 350 400 450 500 550 600 650 700 750 800

0.42 0.48 0.52 0.56 0.59 0.62 0.64 0.66 0.68 0.7 0.71 0.73

1550 1600 1650 1700 1750 1800 1850 1900 1950 2000 2050 2100

0.84 0.84 0.84 0.85 0.85 0.85 0.86 0.86 0.86 0.87 0.87 0.87

2850 2900 2950 3000 3050 3100 3150 3200 3250 3300 3350 3400

0.9 0.9 0.9 0.91 0.91 0.91 0.91 0.91 0.91 0.91 0.91 0.91
Continued

68P02900W21-S 01 Feb 2007 8-51

QoS capacity and QoS2 impact

Chapter 8: PCU upgrade for BSS

Table 8-18 for various transfer delays at GBR 15kbit/s or less (Continued) Min Transfer delay (ms) Min Transfer delay (ms) Min Transfer delay (ms)

850 900 950 1000 1050 1100 1150 1200 1250 1300 1350 1400 1450 1500

0.74 0.75 0.76 0.77 0.78 0.78 0.79 0.8 0.8 0.81 0.82 0.82 0.83 0.83

2150 2200 2250 2300 2350 2400 2450 2500 2550 2600 2650 2700 2750 2800

0.87 0.88 0.88 0.88 0.88 0.89 0.89 0.89 0.89 0.89 0.89 0.9 0.9 0.9

3450 3500 3550 3600 3650 3700 3750 3800 3850 3900 3950 4000

0.92 0.92 0.92 0.92 0.92 0.92 0.92 0.92 0.92 0.92 0.93 0.93

For networks where the majority of streaming services have GBR greater than 15 kbit/s, Table 8-19 and Table 8-20 provide the minimum values of for transfer delays of 500 ms and 250 ms. In networks where the configured minimum transfer delay parameter has been set to be greater than 500 ms, the table for the transfer delay of 500 ms should be used. First determine the GBR for which the majority of service in the network operate, for example, video streaming 40 kbit/s, then looking up the GBR at the table , obtain . If the GBR value is not in the table, then the two closest GBR values should be evaluated and the value resulting in the lower value is selected.
Table 8-19 for Transfer delay = 500 ms at GBR greater than 15 kbit/s Min Transfer delay (ms) Min Transfer delay (ms) Min Transfer delay (ms)

15000 16000 17000 18000 19000 20000 21000 22000 23000

0.62 0.63 0.65 0.66 0.67 0.68 0.69 0.69 0.7

41000 42000 43000 44000 45000 46000 47000 48000 49000

0.8 0.8 0.8 0.81 0.81 0.81 0.82 0.82 0.82

67000 68000 69000 70000 71000 72000 73000 74000 75000

0.86 0.86 0.86 0.86 0.87 0.87 0.87 0.87 0.87

Continued

68P02900W21-S 8-52 01 Feb 2007

System Information: BSS Equipment Planning

QoS capacity and QoS2 impact

Table 8-19 for Transfer delay = 500 ms at GBR greater than 15 kbit/s (Continued) Min Transfer delay (ms) Min Transfer delay (ms) Min Transfer delay (ms)

24000 25000 26000 27000 28000 29000 30000 31000 32000 33000 34000 35000 36000 37000 38000 39000 40000

0.71 0.72 0.72 0.73 0.74 0.74 0.75 0.75 0.76 0.76 0.77 0.77 0.78 0.78 0.79 0.79 0.79

50000 51000 52000 53000 54000 55000 56000 57000 58000 59000 60000 61000 62000 63000 64000 65000 66000

0.82 0.83 0.83 0.83 0.83 0.84 0.84 0.84 0.84 0.85 0.85 0.85 0.85 0.85 0.85 0.86 0.86

76000 77000 78000 79000 80000 81000 82000 83000 84000 85000 86000 87000 88000 89000 90000

0.87 0.87 0.88 0.88 0.88 0.88 0.88 0.88 0.88 0.88 0.89 0.89 0.89 0.89 0.89

Table 8-20 for Transfer delay = 250 ms at GBR greater than 15 kbit/s Min Transfer delay (ms) Min Transfer delay (ms) Min Transfer delay (ms)

15000 16000 17000 18000 19000 20000 21000 22000 23000 24000

0.42 0.43 0.45 0.46 0.47 0.48 0.49 0.5 0.51 0.52

41000 42000 43000 44000 45000 46000 47000 48000 49000 50000

0.63 0.63 0.64 0.64 0.64 0.65 0.65 0.66 0.66 0.66

67000 68000 69000 70000 71000 72000 73000 74000 75000 76000

0.72 0.72 0.72 0.73 0.73 0.73 0.73 0.74 0.74 0.74
Continued

68P02900W21-S 01 Feb 2007 8-53

QoS capacity and QoS2 impact

Chapter 8: PCU upgrade for BSS

Table 8-20 for Transfer delay = 250 ms at GBR greater than 15 kbit/s (Continued) Min Transfer delay (ms) Min Transfer delay (ms) Min Transfer delay (ms)

25000 26000 27000 28000 29000 30000 31000 32000 33000 34000 35000 36000 37000 38000 39000 40000

0.52 0.53 0.54 0.55 0.56 0.56 0.57 0.58 0.58 0.59 0.59 0.6 0.61 0.61 0.62 0.62

51000 52000 53000 54000 55000 56000 57000 58000 59000 60000 61000 62000 63000 64000 65000 66000

0.67 0.67 0.68 0.68 0.68 0.69 0.69 0.69 0.7 0.7 0.7 0.7 0.71 0.71 0.71 0.72

77000 78000 79000 80000 81000 82000 83000 84000 85000 86000 87000 88000 89000 90000

0.74 0.74 0.75 0.75 0.75 0.75 0.76 0.76 0.76 0.76 0.76 0.76 0.77 0.77

Calculating average downlink MTBR

Average downlink MTBR is calculated as follows: AVERAGEDOWNLINKMTBR = (STR_EGBR * %subs) + (IIMTBR * %subs) + (12 MTBR * %subs) + .... (I3_MTBR* %subs) + (BG_MTBR* %subs) + (BE_MTBR* %subs)
Where Is

STR_EGBR I1_MTBR I2_MTBR I3_MTBR BG_MTBR BE MTBR %subs

the throughput required to guarantee downlink GBR and average transfer delay for the streaming traffic class. the downlink MTBR values set for each of the traffic classes.

the percentage of subs allocated to each of the traffic classes in the system based on subscription or by default based on no QoS subscription or roaming subscribers entering the system and having their QoS attributes negotiated to a traffic class.

68P02900W21-S 8-54 01 Feb 2007

System Information: BSS Equipment Planning

QoS capacity and QoS2 impact

The MTBR values are defined at the cell level. The values to use for this equation are either the average MTBRs for each traffic class across all cells connected to a PCU or the maximum MTBR values set at a cell for each traffic class.

Calculating MAX_QOS_MS_PER_PRP
MAX_QOS_MS_PER_PRP is calculated as follows: MAX_QOS_ MS_PER PRP = PRP BOARD THROUGHPUT/AVERAGE DOWNLINK MTBR

Maximizing MS and throughput per PRP/PXP

When QoS is enabled, particularly where the traffic is predominantly streaming traffic (which needs large EGBR), it is advisable that the PRP/PXP operates in mode 2. This is because mode 2 maximizes throughput rather than coverage, whereas mode 1 increases coverage at the expense of throughput. It is anticipated that in networks where QoS is enabled, data services are no longer in the initial deployment stage and hence the option that maximizes throughput is most appropriate. However, before deciding on the mode, the MS per PRP number that can be supported versus maximizing coverage for mode 1 and mode 2 should be verified. This information enables to decide upon the most suitable mode of operation for the particular mix of data services in the network. Typically in networks where there is no streaming traffic mode 1 operation is acceptable, particularly, if most services are assigned the minimum MTBR of 2 kbit/s. For example, a PRP in mode 1 supports 30 TS throughput/120 TS coverage, while a PRP in mode 2 supports 48 TS throughput/48 TS coverage. Assuming a worst case-coding scheme of CS-1, the PRP throughput is 240 kbit/s in mode 1 operation, and 384 kbit/s in mode 2.

240 kbit/s is determined from 8 kbit/s (CS1) * 30 TS and 384 kbit/s is determined from 8 kbit/s (CS1) * 48 TS. If planning for an average downlink bit rate per mobile (no streaming) of 2 kbit/s, then in mode 1, 120 mobiles (240/2) can be simultaneously supported over 120 TS and for mode 2, 192 mobiles (384/2) can be simultaneously supported. However, in mode 2 this is over the PRP board limit of 72 mobiles. Therefore, the PRP board places the limit on the number of supported mobiles to 72 mobiles over the 48 TS of coverage. In this example, mode 1 can support more mobiles than mode 2 and therefore in this situation mode 1 operation is preferred. If planning for an average downlink bit rate per mobile (with provision for streaming traffic) of 8 kbit/s then in mode 1, only 30 mobiles (240/8) can be simultaneously supported over 120 TS and for mode 2, 48 mobiles can be simultaneously supported. Mode2 support more mobiles than mode1, achieving a PRP board throughput of 384 kbit/s (488), and therefore in this situation mode 2 operation is preferred. This approach can be summarized in the following manner: If the planned average bit rate per mobile is R kbit/s then for mode 1: mobile numbers = Min (240/R, 120); for mode 2: mobile numbers = Min (384/R, 72). This relationship is plotted for the two modes in the graph below. The cross over point between preferring mode 2 of mode 1 is R = 3.3 kbit/s.

68P02900W21-S 01 Feb 2007 8-55

QoS capacity and QoS2 impact

Chapter 8: PCU upgrade for BSS

Figure 8-9 BER versus Number of mobiles

CTU2D impact
{30828}

The CTU2-D is not currently part of GSR9, and will be delivered in a separate software load. When CTU2D is configured in ASYM mode LA algorithms and when admitting a mobile, BSS limits uplink-coding schemes on Carrier B to GMSK modulation, that is, MCS1 to MCS4. Also, in ASYM mode, if egprs_init_ul_cs is higher than MCS4, it is restricted to MCS3 when admitting a new mobile on Carrier B. MCS3 is selected since it offers a reasonable compromise of throughput versus link performance, whereas MCS4 is un-coded (code rate = 1) and therefore it is only appropriate in favorable channel conditions.

68P02900W21-S 8-56 01 Feb 2007

System Information: BSS Equipment Planning

PCU-SGSN: traffic and signal planning

PCU-SGSN: traffic and signal planning

Introduction
The PCU is connected to the SGSN through the Gb interface as a Data Terminal Equipment (DTE). The physical Gb connection can be established in two ways: Point-to-point frame relay connection, with DACs. Through the frame relay network.

E1 links are used in both cases.

Gb entities
This section describes the Gb entities and illustrates the mapping of GPRS cells using either the point-topoint frame relay connection (PTP FR) or frame relay network.
Table 8-21 provides a description of the Gb entities and identifiers. Table 8-21 Gb entities and identifiers Gb Entity and Identifier Description

E1

The physical link contains 32 timeslots. One is reserved for E1 synchronization. Each timeslot uses a rate of 64 kbit/s. The bearer channel allows the frame relay protocol to map its resources to the E1 layer. A frame relay virtual circuit. This allows the packet switched FR network to act as a circuit-switched network by guaranteeing an information rate and time delay for a specific PVC. A unique number assigned to a PVC end point in a frame relay network. An instance of the NS layer. Typically, one NSE is used for each PCU being served by a SGSN. The NSE has significance across the network, and is therefore the same at the SGSN and PCU. Uniquely identifies a NSE. A logical circuit that connects the NSE peers between the SGSN and PCU. The NSVC has significance across the network. Therefore, it is configured identically at the SGSN and PCU.
Continued

Frame relay bearer channel (FR BC) Permanent virtual circuit (PVC)

Data link connection identifier (DLCI) Network service entity (NSE)

Network service entity identifier (NSEI) Network Service Virtual Circuit (NSVC)

68P02900W21-S 01 Feb 2007 8-57

PCU-SGSN: traffic and signal planning

Chapter 8: PCU upgrade for BSS

Table 8-21 Gb entities and identifiers Gb Entity and Identifier Description

Network Service Virtual Circuit Identifier (NSVCI) BSSGP virtual circuit (BVC)

Uniquely identifies a NSVC. There is a one-to-one mapping between the NSVCI and DLCI. A logical circuit that connects the BSSGP peers between the BSS and SGSN. It is only configured in the PCU. The PCU contains one point-to-point BVC per an actively serving cell. Uniquely identifies a BVC.

BSSGP Virtual Circuit Identifier (BVCI)

General planning guidelines

These are the general planning guidelines: There can be more than one BVC per NSE/PCU/BSS. There is one point-to-point BVCI per cell, statically configured at the PCU and dynamically configured at the SGSN. There are multiple NSVCs serving one NSE. There is a one-to-one mapping between NSVCIs and DLCIs. Multiple DLCIs can share the same bearer channel, and therefore the same timeslot grouping. A bearer channel can be mapped between one and 31 DS0s, depending on the throughput needed for that particular link. The DLCI has local significance only while the NSVCI has significance across the network. One E1 can be fractionalized into several bearer channels.

Specific planning guidelines

Motorola deploys one NSEI per PCU. Each NSEI must be unique.

Gb signaling
This section describes the Gb protocol signaling. The signaling and the Gb link capacity limitations must be considered in each Gb link plan.

Gb protocol signaling
The GPRS/EGPRS Mobility Management (GMM/EGMM) signaling procedures that contribute to uplink and downlink overhead on the Gb link are as follows: Attach/Detach with ciphering Cell reselection Inter/Intra RAU PDP activate/deactivate Paging
68P02900W21-S 8-58 01 Feb 2007

System Information: BSS Equipment Planning

PCU-SGSN: traffic and signal planning

Gb link PDU data

Each Gb link PDU carries protocol overhead, which is calculated to be 71 bytes.

Determining net Gb load

Consider the network equipment, traffic model and protocol overheads to determine the net load that must be delivered to each PCU served by the SGSN.

Base formulae
Use the following base formulae to determine the load expected on the Gb interface:

Signaling_Data_Rate (bytes/s) = (21 * Cellupdate + 312 * PSAttach/Detach + 125 * RAU + 172 * Subscribers_per_PCU PDPAct/deact) * + 89 * PGPRS 3600
User_Data_ Rate(bytes /s) = {Subscribe rs_per_PCU* Data_per_S ubscriber*1000)(1+ 3600 71 } PKSIZE

Total _ Date _ Rate(bytes / s) = Signaling _ Data _ Rate + User _ Data _ Rate

Where Is

Total Data Rate

the required bandwidth (bit/s) for GPRS data transmission over a GBL interface between the PCU and SGSN after all of the protocol and signaling overhead is accounted for. the required rate (bytes/s) for GPRS signaling transmission over a GBL interface between the PCU and SGSN after all of the protocol. the required rate (bytes/s) for GPRS user application data over a GBL interface between the PCU and SGSN, including protocol overhead. the attach/detach rate per sub/BH. the periodic, Intra and inter area update rate per sub/BH. the PDP context activation/ deactivation rate per sub/busy hour. the GPRS paging rate (per sec). the average packet size, in bytes. the average number of subscribers supported on a PCU. the data traffic per subscriber in a busy hour (kbytes/busy hour). the cell reselections rate per sub/busy hour.

Signaling_Data_Rate

User Data Rate

PS attach/detach RAU PDP act/deact Pgprs PKsize Subscribers_per PCU Data_per Subscriber CellUpdate

68P02900W21-S 01 Feb 2007 8-59

PCU-SGSN: traffic and signal planning

Chapter 8: PCU upgrade for BSS

To simplify Gb planning, the Signaling_Data_Rate can be ignored since it is insignificant compared to the Total_Data_Rate.

Gb link timeslots
The traffic and signaling is carried over the same E1 on the Gb link (GBL). The number of required 64 kbit/s Gb link timeslots can be calculated using the equation given . Each E1 can carry up to 31 timeslots. When fewer than 31 timeslots are needed on an E1, specifying a fractional E1 is more cost effective. No_GBL_TS = Total_Data_Rate/(8000*UGRI) NPCU_SGSN = No_GBL_TS/31
Where Is

No_GBL_TS

the number of timeslots to provision on the GBL E1 between the PCU and SGSN. This value can be used to specify a fractional E1. defined by the equation in the previous section, and represents the required bandwidth (bps) for GPRS data transmission over a GBL interface between the PCU and SGSN after all of the protocol and signaling overhead is accounted for. the link utilization. the E1 link between the PCU and SGSN.

Total_Data_Rate

UGBL NPCU-SGSN

Frame relay parameter values

The network planner needs to specify the values for the following three frame relay interface parameters: Committed Information Rate (CIR) Committed Burst Rate (Bc) Burst Excess Rate (Be)

These frame relay parameter values are determined as described in the following text and illustrated in Figure 8-10.

68P02900W21-S 8-60 01 Feb 2007

System Information: BSS Equipment Planning

PCU-SGSN: traffic and signal planning

Figure 8-10 Frame relay parameters

Committed Information Rate (CIR)

The recommended cumulative CIR value for NSVC should be greater than, or equal to, 50% of the cumulative information rate of the active timeslots on the PCU. The Motorola PCU distributes the use of all the NSVCs by the subscribers evenly in a round-robin manner. The round-robin algorithm continuously assigns subscribers to the next NSVC in a sequential manner when a subscriber PDP context is established. If an NSVC becomes unavailable, it is skipped over, and the next available NSVC in the round-robin is used. The BSSGP feature inherently provides load sharing over all available NSVCs. The load sharing capability over multiple Gb links is provided by the BSSGP high level protocol layer, which results in link resiliency. The recommended cumulative CIR value for all PVCs should be greater than, or equal to, half the cumulative information rate of the active timeslots routed to the NSVC. This mapping is actually determined as a mean load, evenly distributed over all of the available NSVCs as next described. Over many cells, it is expected that the PCU handles the traffic throughput equal to the number of timeslots planned for the busy hour traffic load. The recommended frame relay network CIR value is calculated as follows:
CIR_Value = F * Total_Data_Rate * 8 Num_NSVC

Where

Is

CIR_Value F Total_Data_Rate

the committed Information rate per NSVC (PVC). the CIR provisioning factor, equal to 0.5. defined in Determining net Gb load, and represents the required bandwidth (bit/s) for GPRS data transmission over a GBL interface between the PCU and SGSN after all of the protocol and signaling overhead is accounted for.

68P02900W21-S 01 Feb 2007 8-61

PCU-SGSN: traffic and signal planning

Chapter 8: PCU upgrade for BSS

By using half the number of timeslots in the CIR calculation, the load of all the timeslots is served by the combination of the CIR and Bc frame relay network rated capacity. It should be noted that this strategy makes use of the overload carrying capacity of the frame relay network when more than half of the planned timeslots are in use. When a cell uses all of its provisioned timeslots as active timeslots (that is, timeslots being processed by the PCU at that instance in time), other cells must use fewer of their timeslots being processed in order for the overall PCU Gb interface bandwidth allocation to be within configured frame relay network interface parameter (CIR, Bc, Be) values. The BSS attempts to utilize as many timeslots as are supported in PCU hardware and in communication links simultaneously.

Committed Burst rate (Bc)

The Bc is the maximum amount of data (in bits) that the network agrees to transfer, under normal conditions, during a time interval Tc. The Bc value should be configured such that if one of the provisioned E1 links fails, the remaining E1 links can carry the load of the failed link, by operating in the Bc region. For example, with three E1 links provisioned, if any one of the three should fail, the other two should have the capacity to carry the load of the failed link on the remaining two links, by operating in the Bc region.

Burst excess rate (Be)

The Be is the maximum amount of uncommitted data (in bits) in excess of Bc that a frame relay network can attempt to deliver, during a time interval Tc. The network treats Be data as discardable.

68P02900W21-S 8-62 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for GPRS

BSS-PCU hardware planning example for GPRS

Introduction
This section provides an example of the PCU hardware provisioning process and the link provisioning process associated with adding a PCU to the BSC as shown in Figure 8-11. For the provisioning of the BSC hardware, the network planner should follow the relevant planning rules for adding additional E1 interface hardware in support of the GDS and GSL links. The provisioning of the SGSN hardware is not covered in this planning guide. The QoS feature is not enabled.
Figure 8-11 PCU equipment and link planning for GPRS

BSS - PCU planning example for GPRS

Use this example to provision a BSS with 10 sites consisting of 20 cells, one GPRS carrier per cell, PCCCH disabled (pccch_enabled = 0) at cells, DTM disabled and with the following GPRS call model:
Table 8-22 GPRS call model Item Value

Average packet size (bytes) Traffic per sub/BH (kbytes/hr) uplink Traffic per sub/BH (kbytes/hr) downlink PS attach/detach rate (per sub/BH) PDP context activation/deactivation (per sub/BH) Routing area update Cell Updates GPRS paging rate in pages per second GPRS users per cell

PKSIZE=310.08 ULRATE=33.46 Data rate_per sub = 90.73 PS attach/detach = 0.5 PDPact/deact = 0.4 RAU= 1.4 CellUpdate =0.33 Pgprs = 18.73 200
Continued

68P02900W21-S 01 Feb 2007 8-63

BSS-PCU hardware planning example for GPRS

Chapter 8: PCU upgrade for BSS

Table 8-22 GPRS call model (Continued) Item Value

Average sessions per user per hour GSM circuit-switched paging rate (pages/second) Ratio of LCSs per call Mobile terminated LCS ratio Ratio of mobiles in the system that are both GSM and GPRS capable Number of PCCCH-enabled cells in the BSS Total number of cells in the BSS TRAU TYPE Mobile Class Type CS utilization CS CS1 CS2 CS3 CS4

0.45 Pgsm = 60 LCS = 0.1 LRMT = 0.95 NgSM GPRS Ms/NaII MS = 0.25 10 20 64 10 Distribution 20% 45% 25% 10% Rate 8 kbit/s 12 kbit/s 14.4 kbit/s 20 kbit/s

Selecting a cell RF plan

Use the 4x3 non-hopping table (Table 3-22) to determine what values to use for CS rate and BLER for the selected cell RF plan.

Determining the number of CCCHs at each BTS cell

Use the following equation:
NPAGCH = (NAGCH + NPCH)/UCCCH

When pccch_enabled = 0 (PCCCH disabled) at the cell, the BTS combines the additional control channel load for the GPRS data traffic with the existing circuit-switched traffic load onto the CCCH. On the other hand, when pccch_enabled = 1 at the cell, GPRS does not add any additional control channel load on the CCCH. In this case, however, PCCCH reduces the GSM circuit-switched signaling load on the CCCH with paging coordination. The network planner needs to consider paging coordination, the expected paging rate and the access grant rate in order to calculate the number of CCCH blocks needed. This calculation should be performed using the guidelines given in the Control channel calculations section of Chapter 3.

Determining the number of GPRS carrier timeslots at each BTS cell

Use the equation to determine the number of GPRS timeslots that are required on a per cell basis. In order to use this equation, the network planner should have the expected cell load in kbit/s.

68P02900W21-S 8-64 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for GPRS

Mean_traff ic_load =

GPRS_Users* Data_rate_per_sub_downlink * 8bits/byte 3600 = 200 * 90.73 * 8 / 3600 = 40.32kbit/s

TS_Data_Rate =

(8 * 20 + 12 * 45 + 14.4 * 25 + 20 * 10) 1 4 CSi_ERate* CSi_Utilization = 100 i =1 100 = 12.6kbit/s Mean_traffic_load * Mean_load_ factor NPBCCH + NPAGCH + NPPCH No_PDCH_TS= Roundup( + ) TS_Data_Rate 12 40.32 * 2 4 + 0.0264 + 38.71 = Roundup( + ) = 11 12.6 12

Calculating the number of GDS E1/ETH links

Compute the number of GDS TRAU E1 channels required for the air interface timeslots required to carry the traffic. Remember: Each CS1/CS2 timeslot needs 16K TRAU channel. CS3/CS4 timeslots needs 32K TRAU on GDS TRAU interface. CS3/CS4 is enabled on a carrier hence all the GPRS timeslots for that carrier need 32K TRAU.

For this case, Total GDS E1s = 20 cells * (11 TS/cell)*(32K/TS) /31*64k = 4 E1s ETH link has no limitation of bandwidth compared with PXP board. Total GDS PDCH is 220. Hence, 4 PXP boards (mode1, 70/280) or 2 PXP boards (mode2,140/140) are needed, thus requiring 3 or 4 ETH links. If the number of GDS E1 links exceeds the limit for one PCU then ETH is required to replace E1 links to extend the capacity of the links. If the capacity still exceeds the limit for one PCU, a new BSC-PCU is needed.

Calculating the number of active timeslots

Assuming that coverage is to be provided to at least half of the timeslots at any instance, the number of mean 11/2= 6 PDTCHs (from Calculating the number of GDS E1/ETH links), the number of active timeslots is: 6 active timeslots per cell * 20 cells per BSC = 120 active timeslots If the number of active timeslots exceeds the limit for one PCU, those cells have to be moved to another BSS.

Calculating the number of PRP boards

Each PRP board can process 30 active timeslots at any given time for a total of 120 timeslots. Using the value calculated in Partitioning the load across another PCU (another BSS), the number of PRPs required to serve 20 cells is: 120 active timeslots/30 active timeslots per PRP = 4 PRPs These 4 PRPs have more than enough capacity to handle the additional 3 standby timeslots per cell. Using the conservative provisioning rule of one GDS TRAU E1 per PRP, 4 GDS TRAU E1s are provisioned. Refer to the appropriate section of this chapter for the PCU provisioning rules.

68P02900W21-S 01 Feb 2007 8-65

BSS-PCU hardware planning example for GPRS

Chapter 8: PCU upgrade for BSS

Calculating the BSC LCF impact to support GPRS traffic

The BSC LCF GPROC processor load is increased by the volume of GPRS signaling traffic. The BSS planning rule for LCF provisioning in the following equation should be used.
GL3_GPRS = 0.002 * Total_RACH/sec * (1 RPCCH_Cells) + 0.00075 * B * PGPRS * PCCCH_BSS = 0.002 * ( 200 * 20 * 5 ) * (1 0.5) + (0.00075 * 10) * 18.73 * 1) = 0.146 5

Where B is the number of BTS sites. In this instance, B=10. The network planner can select to add an additional LCF GPROC or to examine the GSM circuit-switched provisioning to check if an existing LCF GPROC can process this additional load.

Calculating the number of GBL links

Using the standard traffic model and Gb formulae:

Signaling_ Data_Rate =
21 * Cell Update + 312 * PS Attach/Det ach + 125 * RAU + 172 * PDP Act/Deact * Susbcriber s_per_PCU + 89 * P GPRS 3600 (21 * 0.33 + 312 * 0.5 + 125 * 1.4 + 172 * 0.4) * 20 * 200 = + 89 * 18.73 3600 = 2119bytes/ s (GPRS_User s_PCU * Data_rate_ per_sub * 1000) 71 User_Data_ Rate = + (1 + ) 3600 PK size 200 * 20 * 90.73 * 1000 71 =( ) * (1 + ) = 123894byte s/s 3600 310.08

Signaling_ Data_Rate + User_Data_ Rate ) Data_Rate_ Per_GBL * Utilizatio nGBL 2119 + 123894 = Roundup( ) = 63 8000 * 0.25 No_GBL_TS 63 NPCU SGSN = = = 2.03 31 31 No_GBL_TS = Roundup(
Hence, 3 Gb links have to be provisioned.

Calculating the number of GSL links

Use the following equation to calculate how many 64 kbits/s GSL links are required. For this example, the number of users on a PCU is 5000. It assumes that all 20 cells parented to a single LCF card in the BSC, after performing this step. Evaluating this equation and the supporting expressions results in one 64 kbit/s GSL link being required, assuming that enhanced one phase is enabled, after rounding up to the nearest integer value (but not including redundancy). Refer to Determining the number of GSLs required in Chapter 6, BSC planning steps and rules for further details on the following equations.

68P02900W21-S 8-66 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for GPRS

Total_cells * GPRS_users_per_cell* Averagesessions 3600 (20 * 200) * (0.45) = = 0.5/s 3600 number_of_PCCCH enabled_cells RPCCH_Cells = = 10/20 = 0.5 total_number_of_cells_in_BSS (1 0.5) * 0.5 * 7.5 GSLRACH = = 0.075 1000 * 0.25 8.5 *18.73 *1 *1 GSLPaging = = 0.64 1000 * 0.25 Total_RACH/sec =
The number of GSL TSs for run-time is represented by:

GSLrun_time = GSLPaging + GSLRACH = ROUND_UP(0.64 + 0.075) = 1

The number of GSLs required is:
GSL = MAX(GSLrun_time, GSLinit_time) = MAX(1,6) = 6

Balancing the GSL load across the LCFs

This step can be performed optionally and automatically by the system at sysgen. If it is desired to perform the operation manually, suggestions and an example are given in the Load balancing section of Determining the number of GSLs required in Chapter 6, BSC planning steps and rules.

Calculating the PCU hardware to support the PCU traffic

To calculate the PCU hardware for supporting the PCU traffic, the following requirements are to be considered: 4 PRP boards, 1 PRP board per GDS E1 link. 2 PICP board, 1 PICP board to process GDS LAPD and GBL link and the other PICP board for GBL links. 1 MPROC board per PCU shelf (2 for redundancy). 1 PCU shelf with alarm board and 3 power supply / fan assemblies, 1 PCU shelf per 9 PRP boards. 1 PCU cabinet per 3 PCU shelves (cages).

After calculating the number of GDS, GBL and GSL E1 links, ensure that there are sufficient number of PICP boards to cover the GBL and GSL E1 links. The PCU hardware calculation calculates the number of PICP boards based only on the ratio of PICP boards to PRP boards. The following calculation takes into account the number of E1 links terminated on the PICP boards for the GBL and GSL E1 links. A PICP board can terminate both GBL and GSL links on the board, but not on the same PMC module. Each PICP has two PMC modules. Two E1 links are required for the GBL. Each PICP can terminate up to 3 GBL links. Therefore, 2 PICPs are required for the GBL E1 links. One E1 link is required for the GSL (redundant GSL not provided). Each PICP can terminate up to 2 E1 GSL links and up to 12 GSL 64 kbit/s timeslots distributed over two E1s.

68P02900W21-S 01 Feb 2007 8-67

BSS-PCU hardware planning example for GPRS

Chapter 8: PCU upgrade for BSS

There is a limit of 2 GSL E1s per PCU. Therefore, 1/4 of a PICP is required for the GSL E1 link. The GBL and GSL E1 link requirements show that 2 PICPs are sufficient to process the link provisioning requirements.

Calculating the increased data traffic load on the E1s between the BSC and BTSs
It is assumed that the GPRS traffic is in addition to the existing circuit-switched traffic. Six timeslots are required for the GPRS timeslot traffic on a per cell basis. Therefore, an additional 12 x 16 kbits/s timeslots (CS1/CS2) or 32 kbit/s timeslots (CS3/CS4) are required on a per BTS site basis, 2 cells per site, in order to carry the GPRS traffic. The allocation of GPRS carrier timeslots has to be decided, that is, they are reserved or switchable. GSM circuit-switched statistics can be used to decide about the allocation. Refer to Dynamic timeslot allocation in Chapter 3: BSS cell planning.

Calculating the changes in signaling traffic load (RSL load) on the E1s between the BSC and BTSs
For cells without PCCCH (pccch_enabled = 0), the BTS combines the additional signaling load for the GPRS data traffic with the existing circuit-switched traffic load. This results in an additional load on the existing RSL links between each BTS and the BSC. For cells with PCCCH, GPRS does not add significant additional control channel load on the RSL. In this case, however, PCCCH reduces the GSM circuitswitched signaling load on the RSL with paging coordination. The new load on the RSL for GPRS is based on the evaluation of the following equation and other supporting equations. Refer to Determining the number of RSLs required in Chapter 6, BSC planning steps and rules for further details on the following equation.
RSLGPRS + GSM = RSLGPRS + RSLGSM

The GSM RSL calculation should be performed with 64 kbit/s RSL in order to be consistent with the GPRS calculation.

BSC link provisioning impact

The BSC needs additional hardware to support the addition of the GPRS network traffic. For BSC provisioning, refer to the planning rules given in Chapter 6. The BSC needs more E1 terminations in support of the additional E1 links to the PCU and in support of the additional GPRS traffic over the BTS to BSC interface. In this example, 4 E1s were added for the GDS links and 3 E1s added for the GSL link.

BTS provisioning impact

GPRS has no impact on the hardware provisioning of a Horizon II macro, Horizonmacro or M-Cell BTS.

68P02900W21-S 8-68 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

BSS-PCU hardware planning example for EGPRS

Introduction

This section builds upon the previous example shown in BSS-PCU hardware planning example for GPRS by adding EGPRS into the system. The main additions are: New EGPRS carriers. Calculation of the impact of increased data capacity on the system.

The provisioning of the SGSN hardware is not covered in this planning guide.
Figure 8-12 PCU Equipment and link planning for EGPRS

BSS - PCU planning example for EGPRS

The example for EGPRS has new call model parameters for increased data usage.

Refer to BSS - PCU planning example for GPRS to compare the GPRS/EGPRS call model parameters. Use this example to provision a BSS with 10 sites consisting of 20 cells, one GPRS carrier per cell, PCCCH disabled (pccch_enabled = 0) at cells and DTM disabled.

68P02900W21-S 01 Feb 2007 8-69

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

Additional data
The QoS feature is not enabled. Add one EGPRS carrier per cell with the following call model:
Table 8-23 EGPRS call model Item Value

Average packet size for GPRS and EGPRS traffic mix (bytes) Average packet size for GPRS and EGPRS traffic mix (bytes) GPRS and EGPRS Traffic per sub/BH (kbytes/hr) - uplink GPRS and EGPRS Traffic per sub/BH (kbytes/hr) - downlink PS attach/detach rate (per sub/BH) PDP context activation/deactivation (per sub/BH) Routing area update Cell Updates GPRS paging rate in pages per second GPRS/EGPRS users per cell Average sessions per user per hour GSM circuit-switched paging rate (pages/second) Ratio of LCSs per call Mobile terminated LCS ratio Ratio of mobiles in the system that are both GSM and GPRS capable Percentage of mobiles that are EGPRS capable Number of PCCCH-enabled cells in the BSS Total number of cells in the BSS

PKULSIZE = 188.71 PKDLSIZE = 435.97 ULRATE = 35.59 Data rate_per sub = 92.38 PSATT/DETACH =0.5 PDPACT/DEACT = 0.4 RAU= 1.4 CellUpdate = 0.33 PGPRS = 18.73 250 0.45 PGSM = 60 LCS = 0.1 LRMT = 0.95 NGSM GPRS MS/NAU MS = 100% 5% 10 20
Continued

68P02900W21-S 8-70 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

Table 8-23 EGPRS call model (Continued) Item CS Value Distribution Rate

CS1 CS2 CS3 CS4 MCS1 MCS2 CS utilization MCS3 MCS4 MCS5 MCS6 MCS7 MCS8 MCS9 Total

10% 22.5% 12.5% 5% 5% 4% 16.5% 0.5% 10.5% 7.5% 2.5% 1.5% 2% 100%

8 12 14.4 20 8.8 11.2 14.8 17.6 22.4 29.6 44.8 54.4 59.2

Selecting a cell RF plan

Use the 4x3 non-hopping table (Table 3-22 in Chapter 3: BSS cell planning) to determine the values to use for CS rate and BLER for the selected cell RF plan.

Determining the number of CCCHs at each BTS cell

Use the following equation:
NPAGCH = (NAGCH+NPCH) / UCCCH

When pccch_enabled = 0 (PCCCH disabled) at the cell, the BTS combines the additional control channel load for the GPRS data traffic with the existing circuit-switched traffic load onto the CCCH. On the other hand, when pccch_enabled = 1 at the cell, GPRS does not add any additional control channel load on the CCCH. In this case, however, PCCCH reduces the GSM circuit-switched signaling load on the CCCH with paging coordination. The network planner needs to consider paging coordination, the expected paging rate, and the access grant rate in order to calculate the number of CCCH blocks needed. This calculation should be performed using the guidelines given in Control channel calculations in Chapter 3: BSS cell planning.

Determining number of GPRS and EGPRS carrier timeslots at each BTS cell
Use the equation to determine the number of GPRS timeslots that are required on a per cell basis. To use this equation, the expected cell load in kbit/s should be known.

68P02900W21-S 01 Feb 2007 8-71

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

GPRS_Users * Data_rate_ per_sub * 8 bits/byte 3600 250 * 92.38 * 8 = = 51.32kbit/ s 3600 9 1 i=4 TS_Data_Ra te = ( CSi_Rate * CSi_distri bution + MCSi_Rate * MCSi_distr ibution) 100 i =1 i =1 17.41 kbit / s Mean_traff ic_load = No_PDCH_TS = Roundup{ = Roundup{ 51.32 * 2 }= 6 17.41 Mean_traff ic_load * Mean_load_ factor } TS_Data_Ra te

Therefore, provide 6 timeslots on the cell. If the number of users, Mean_traffic_load and TS_Data_Rate has increased with the EGPRS capabilities, the timeslots calculation does not increase as per the GPRS calculation. The new equation provides 6 timeslots but these are divided between GPRS and EGPRS. In this example, l has 8 GPRS timeslots configured as switchable or packet data from the original GPRS carrier and 8 timeslots defined as packet data for the new EGPRS carrier for a total of 16 data capable timeslots per cell. This is a total of 320 data capable timeslots.

Calculating the number of GDS E1/ETH links

Compute the number of GDS TRAU E1 channels required for the air interface timeslots required to carry the traffic. The following requirements have to be considered: Each CS1/CS2 timeslot needs 16K TRAU channel. CS3/CS4 timeslots needs 32K TRAU. MCS1 through MCS9 need a variable VersaTRAU backhaul in units of 64K DS0s on the GDS TRAU interface

The example here assumes that each EGPRS RTF is equipped with a backhaul of 8 DS0s (rtf_ds0_count = 8). This is the worst case. Typical configuration needs less GDS resources. CS3/CS4 is enabled on a carrier hence all the GPRS timeslots for that carrier would need 32K TRAU and the EGPRS carrier would need 64K TRAU.

For this case, it can be calculated that 8 GDS TRAU E1s are required

Total _ GDS _ E1 = = 7.74

(20cells * 8TS / Cell * 32kTS) + (20cells * 8TS / Cell * 64kTS) 31* 64k

If ETH links are used for BSC-PCU connectivity, there are no concerns of ETH links bandwidth. The number of ETH links required only depends on the number of PXPs.

68P02900W21-S 8-72 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

Calculating the number of active timeslots

Two work modes are introduced in GSR9 {28000}. For prp_fanout_mode1, a PRP board can be assigned up to 120 timeslots but only 30 will be serviced (active) at any given time. A PXP board can be assigned up to 280 timeslots but only 70 will be serviced (active) at any given time. For prp_fanout_mode2, 48 timeslots provisioned by a PRP can be served at any given time interval. 140 timeslots provisioned by a PXP can be served at any given time interval. The PRP/PXP algorithms handle the scheduling of timeslots in an efficient manner dependant on resources available. Assuming that PXP is used and prp_fanout_mode1 to provide coverage:
Active Timeslots per PXP = 70 Supported Timeslots per PXP = 280

Since the equation resulted in 6 timeslots and the cell has 16 timeslots between GPRS and EGPRS, the total active timeslots and supported timeslots are:
Total active timeslots = 6*20 = 120 Total supported timeslots = 16*20 = 320

Calculating the number of PXP boards

Each PXP board can process 70 active timeslots at any given time for a total of 280 timeslots. Using the value calculated in Calculating the number of active timeslots and the number to assign to each PXP, the following equation is created: Round Up (120 active timeslots/ 70 active timeslots per PXP) = 2 Round Up (320 supported timeslots/280 supported timeslots per PXP) = 2 The number of PXP = MAX (2,2) =2 The 2 ETH links are required based on 2 PXPs.

Each PXP must terminate one GDS TRAU_LAPD ETH link and the timeslots of an entire cell must terminate on the same PXP.

Calculating the BSC LCF impact to support GPRS traffic

The volume of GPRS and EGPRS signaling traffic increases the BSC LCF GPROC2 processor load. The BSS planning rule for LCF provisioning in the following equation should be used.

0.002 * Total_RACH /sec * (1 R PCCCH_Cell s) + 0.00075 * B * G L3_GPRS = P GPRS * PCCCH_BSS 250 * 20 * 0.45 = 0.002 * ( ) * (1 0 .5) + 0 .00075 * 10 * 18 .73 * 1 = 0 .14 3600
An additional LCF GPROC2 can be added or the GSM circuit-switched provisioning can be examined to check if an existing LCF GPROC2 can process this additional load.

68P02900W21-S 01 Feb 2007 8-73

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

Calculating the number of GBL links

Using the standard traffic model and Gb formulae:

Signaling_ Data_Rate = (21 * Cell Update + 312 * PS Attach/Det 172 * PDP ACT/Deact ) *

ach

+ 125 * RAU +

Subscriber s_per_PCU + 89 * P GPRS 3600 ( 21 * 0 . 33 + 312 * 0 . 5 + 125 * 1 . 4 + 172 * 0 . 4 ) * 20 * 250 = + 89 * 18 . 73 3600 = 2649 bytes/s GPRS_Users _PCU * Data_rate_ per_sub * 1000) 71 User_Data_ Rate = ( * (1 + ) 3600 PK size 250 * 20 * 92.38 * 1000 71 =( ) * (1 + ) = 149200.77b ytes/s 3600 435.97 Total_Data _rate 2649 + 149200 . 77 No_GBL_TS = = = 75 . 92 8000 * U GRI 8000 * 0 . 25 N PCU SGSN = No_GBL_TS/ 31 = 75.92/31 = 2.45
Hence, 3 Gb links are to be provided.

Calculating the number of GSL links

Use the following equation to calculate the number of 64 kbits/s GSL links required. In this example, the number of users on a PCU is 5000. It assumes that all 20 cells are attached to a single LCF card in the BSC. Evaluating this equation and the supporting expressions results in one 64 kbit/s GSL link being required, assuming that preload is enabled, after rounding up to the nearest integer value (but not including redundancy). Refer to Determining the number of GSLs required in Chapter 6, BSC planning steps and rules for further details on the following equations: Total_RACH/sec =20*250*0.45/3600 = 0.625 GSLRACH = (1-0.5)*0.625*5.5/(1000*0.25) = 0.006875 GSLPaging = 8.5*18.73*1*1/(1000*0.25) = 0.64 The number of GSL TS for run time is represented by: GSLrun_time = GSLRACH+GSLPaging = Round Up (0.006875+0.64) = 1 The number of GSL required is GSL=MAX(GSLrun_time, GSLinit_time) = 6

Balancing the GSL load across the LCFs

This step is performed either optionally or automatically by the system at sysgen. If it is desired to perform the operation manually, suggestions are given in Load balancing section of Determining the number of GSLs required in Chapter 6, BSC planning steps and rules.

Calculating the PCU hardware to support the PCU traffic

The following is the required PCU hardware: 2 PXP boards, 2 GDS ETH links (GDS TRAU_LAPD) with the PXPs. 3 GBL balanced across 2 PXPs. 1 MPROC board, 1 MPROC board per PCU shelf (2 for redundancy).

68P02900W21-S 8-74 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

1 PCU shelf with alarm board and 3 power supply / fan assemblies, 1 PCU shelf per 12 PXP boards. 1 PCU cabinet, 1 PCU cabinet per 3 PCU shelves.

After calculating the number of GDS, GBL, and GSL links, ensure that there are a sufficient number of PXP boards to cover the GBL and GSL links. Both GBL and GDS TRAU_LAPD links can terminate on a PXP board. Each PXP has two PMC modules supporting 2 GBL and 1 RJ45 port supporting 1 ETH link.

Calculating the increased data traffic load on the E1s between the BSC and BTSs
It is assumed that the EGPRS traffic is in addition to the existing circuit-switched traffic and GPRS traffic already available in the system. In Determining the number of CCCHs at each BTS cell it was determined that 8 timeslots would be required for the EGPRS required on a per BTS site basis, 2 cells per site, in order to carry the GPRS traffic. A decision can be made at this stage of the provisioning process on how to allocate the EGPRS carrier timeslots. When EGPRS enabled, all reserved and switchable timeslots are backhauled from the BTS through the BSC to the PCU. The physical link calculations must take this into account. The CPU processing equations require to take into account the percentage of backhauled timeslots that are active at a given time interval. If GSM circuit-switched statistics are available, they could be reviewed to aid in this decision. Refer to Dynamic timeslot allocation in Chapter 3: BSS cell planning.

Calculating the changes in signaling traffic load (RSL load) on the E1s between the BSC and BTSs
For cells without PCCCH (pccch_enabled = 0), the BTS combines the additional signaling load for the EGPRS data traffic with the existing circuit-switched traffic load. This results in an additional load on the existing RSL links between each BTS and the BSC. For cells with PCCCH, EGPRS does not add significant additional control channel load on the RSL. In this case, however, PCCCH reduces the GSM circuit-switched signaling load on the RSL with paging coordination. The new load on the RSL for GPRS is based on the evaluation of the following equation and other supporting equations. Refer to Determining the number of GSLs required in Chapter 6, BSC planning steps and rules for further details on the following equation. RSLGPRS+GSM = RSLGPRS+RSLGSM Perform the GSM RSL calculation with 64 kbit/s RSL to be consistent with the EGPRS calculation.

BSC link provisioning impact

The BSC can need additional hardware in order to support the addition of the EGPRS network traffic. For BSC provisioning, refer to the planning rules given in Chapter 6. The BSC needs more E1 terminations in support of the additional EGPRS traffic over the BTS to BSC interface.

BSS - PCU planning example for EGPRS with QoS enabled, QoS2 not enabled
This example uses the same base call model parameters as those used in BSS - PCU planning example for EGPRS except that the QoS feature is enabled. QoS needs new call model parameters to be specified based on QoS usage.

68P02900W21-S 01 Feb 2007 8-75

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

Refer to BSS - PCU planning example for EGPRS to compare the GPRS/EGPRS call model parameters.

Additional data:
The QoS feature is enabled. Add one EGPRS carrier per cell with the following call model:
Table 8-24 EGPRS with QoS enabled call model Item Value

Average packet size for GPRS and EGPRS traffic mix (bytes) Average packet size for GPRS and EGPRS traffic mix (bytes) GPRS and EGPRS Traffic per sub/BH (kbytes/hr) - uplink GPRS and EGPRS Traffic per sub/BH (kbytes/hr) - downlink PS attach/detach rate (per sub/BH) PDP context activation/deactivation (per sub/BH) Routing area update Cell Updates GPRS paging rate in pages per second GPRS/EGPRS users per cell GSM circuit-switched paging rate (pages/second) Ratio of LCSs per call Mobile terminated LCS ratio Ratio of mobiles in the system that are both GSM and GPRS capable Percentage of mobiles that are EGPRS capable Number of PCCCH-enabled cells in the BSS Total number of cells in the BSS

PKULSIZE = 188.71 PKDLSIZE=435.97 ULRATE=35.59 Data rate_per sub = 92.38 PSATT/DETACH =0.5 PDPACT/DEACT = 0.4 RAU= 1.4 CellUpdate = 0.33 PGPRS = 18.73 250 PGSM = 60 LCS = 0.1 LRMT = 0.95 NGSM GPRS MS/NAU MS = 100% 5% 10 20
Continued

68P02900W21-S 8-76 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

Table 8-24 EGPRS with QoS enabled call model (Continued) Item Value

I1_MTBR I2_MTBR I3_MTBR BG_MTBR BE_MTBR I1_MTBR_USAGE I2_MTBR_USAGE I3_MTBR_USAGE BG_MTBR_USAGE BE_MTBR_USAGE TRAU Type Mobile Class Type CS CS1 CS2 CS3 CS4 MCS1 MCS2 CS distribution MCS3 MCS4 MCS4 MCS5 MCS6 MCS7 MCS8 MCS9 Total

14 10 4 2 2 5% 10% 25% 20% 40% 64 10 Distribution 10% 22.5% 12.5% 5% 5% 4% 16.5% 0.5% 0.5% 10.5% 7.5% 2.5% 1.5% 2% 100% Rate 8 12 14.4 20 8.8 11.2 14.8 17.6 17.6 22.4 29.6 44.8 54.4 59.2

Selecting a cell RF plan

BLER is compensated by the PRP board headroom required for QoS. The CS coding schemes are set as pre-defined values determined by the QoS feature. For GPRS, the maximum rate is 8K and for EGPRS the maximum rate is 14K.

68P02900W21-S 01 Feb 2007 8-77

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

Determining the number of CCCHs at each BTS cell

Use the following equation: NPAGCH = (NAGCH+NPCH) / UCCCH When pccch_enabled = 0 (PCCCH disabled) at the cell, the BTS combines the additional control channel load for the GPRS data traffic with the existing circuit-switched traffic load onto the CCCH. On the other hand, when pccch_enabled = 1 at the cell, GPRS does not add any additional control channel load on the CCCH. In this case, however, PCCCH reduces the GSM circuit-switched signaling load on the CCCH with paging coordination. The network planner needs to consider paging coordination, the expected paging rate, and the access grant rate in order to calculate the number of CCCH blocks needed. This calculation should be performed using the guidelines given in Control channel calculations Chapter 3: BSS cell planning.

Determining number of GPRS and EGPRS carrier timeslots at each BTS cell
Use the equation to determine the number of GPRS timeslots that are required on a per cell basis. In order to use this equation, the n expected cell load in kbit/s should be known.

GPRS_Users * Data_rate_ per_sub * 8 bits/byte 3600 250 * 92.38 * 8 = = 51.32kbit/ s 3600 9 1 i=4 TS_Data_Ra te = ( CSi_Rate * CSi_distri bution + MCSi_Rate * MCSi_distr ibution) 100 i =1 i =1 17.41 kbit / s Mean_traff ic_load = No_PDCH_TS = Roundup{ = Roundup{ 51.32 * 2 }= 6 17.41 Mean_traff ic_load * Mean_load_ factor } TS_Data_Ra te

The equation takes into account the amount of local timeslot headroom to allow to the required MTBR. The mean load factor is set to 2 to accommodate peak data scenarios since the mean traffic load is based on averages. The defined timeslot throughput and the PRP board headroom allocated by the QoS feature cover the signaling peak periods.

Calculating the number of GDS E1/ETH links

Compute the number of GDS TRAU E1 channels required for the air interface timeslots required to carry the traffic. Each CS1/CS2 timeslot needs 16K TRAU channel. CS3/CS4 timeslots need 32K TRAU. MCS1 through MCS9 need a variable VersaTRAU backhaul in units of 64K DS0s on the GDS TRAU interface.

The example here assumes that each EGPRS RTF is equipped with a backhaul of 8 DS0s (rtf_ds0_count = 8).

68P02900W21-S 8-78 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

CS3/CS4 is enabled on a carrier hence all the GPRS timeslots for that carrier would need 32K TRAU and the EGPRS carrier would need 64K TRAU.

For this case, it can be calculated that 8 GDS TRAU E1s are required.

Total _ GDS _ E1s = =8

( 20 cells * 8 TS / Cell * 32 kTS ) + ( 20 cells * 8 TS / Cell * 64 kTS ) 31 * 64 k

If the number of active timeslots exceeds the limit for one PCU, those cells have to be moved to another BSS. Since the limit is 3360 active timeslots, only one PCU is required.

Calculating the number of active timeslots

A PRP board can be assigned up to 120 timeslots but only 30 are serviced (active) at any given time. The PRP algorithms handle the scheduling of timeslots in an efficient manner dependent on available resources. The QoS feature provides further guidelines on the number of timeslots to assign to a PRP to achieve the requested MTBR per subscriber. PRP board throughput is calculated as follows: PRP BOARD THROUGHPUT =THRUPUT_TS* {(8000 * %CS1_USAGE) + (12000 * %CS2_USAGE) + (14400 * %CS3_USAGE) + (20000 * %CS4_USAGE) + (8800 * %MCS1_USAGE) + (11200 * %MCS2_USAGE) +(14800 * %MCS3_USAGE) + (17600 * %MCS4_USAGE) + (22400 * %MCS5_USAGE) +(29600 + %MCS6_USAGE) + (44800 * %MCS7_USAGE) + (54400 * %MCS8_USAGE) +(59200 * %MCS9_USAGE) } *(100% 16.7%) = 30*{8000*10%+ (12000 * 22.5%) + (14400 * 12.5%) + (20000 * 5%) + (8800 * 5%) + (11200 * 4%) + (14800 * 16.5%) + (17600 *0.5%) + (22400 * 10.5%) + (29600 *7.5%) + (44800 * 2.5%) + (54400 * 1.5%) + (59200 * 2%) } *(100% 16.7%) =30*17410*83.3% = 435075 bps. AVERAGEDOWNLINKMTBR = (STR_EGBR*%subs) + (IIMTBR * %subs) + (12 MTBR * %subs) + ... ... (I3_MTBR* %subs) + (BG_MTBR* %subs) + (BE_MTBR* %subs) = 3.9 kbit/s

%subs of STR_EGBR is 0. Therefore, MAX_QOS_PDCHS_PER_PRP = 435075/(3.9*1000) = 112.

Calculating the number of PRP boards

The previous example had one GPRS carrier per cell that provided adequate throughput for the calculated 6 timeslots. The new equation also provides 6 timeslots but these are divided between GPRS and EGPRS. The new EGPRS carrier provides 8 timeslots of data capacity that is the required 6. In this example, we have 8 GPRS timeslots configured as switchable or packet data from the original GPRS carrier and 8 timeslots defined as packet data for the new EGPRS carrier for a total of 16 data capable timeslots per cell. This is a total of 320 data capable timeslots. 320 PDTCHs/112 MAX per board = 4 PRP boards. The provisioning of the 8 GDS E1s to 4 PRPs is required in order not to break the 60 timeslots per PRP.

68P02900W21-S 01 Feb 2007 8-79

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

Each PRP must terminate at least one GDS TRAU E1 and the timeslots of an entire cell must terminate on the same PRP.

Calculating the BSC LCF impact to support GPRS traffic

The volume of GPRS and EGPRS signaling traffic increases the BSC LCF GPROC2 processor load. The BSS planning rule for LCF provisioning in the following equation should be used.
G L3_GPRS = 0.002 * Total_RACH /sec * (1 R PCCCH_Cell
s

) + 0.00075 * B *

P GPRS * PCCCH_BSS 250 * 20 * 5 = 0.002 * ( ) * (1 0 . 5 ) + 0 . 00075 * 10 * 1 . 4 * 1 = 0 . 017 3600

An additional LCF GPROC2 can be added or the GSM circuit-switched provisioning can be examined to check whether an existing LCF GPROC2 can process this additional load.

Calculating the number of GBL links

Using the standard traffic model and Gb formulae:
GPRS_Users_PCU * Data_rate_per_sub *1000) 71 * (1 + ) 3600 PKsize 250 * 20 * 92.38 *1000 71 ) * (1 + ) = 149200bytes/s =( 3600 435.97 Total_Data_rate 2649 + 149200 No_GBL_TS = = = 75 8000 * UGRI 8000 * 0.25 NPCU SGSN = No_GBL_TS/31 = 75/31 = 2.42 User_Data_Rate = (

Hence, 3 Gb links are required.

Calculating the number of GSL links

Use the following equation to calculate the number of 64 kbit/s GSL links required. In this example, the number of users on a PCU is 5000. It assumes that all 20 cells are parented to a single LCF card in the BSC. Evaluating this equation and the supporting expressions results in one 64 kbit/s GSL link being required, assuming that preload is enabled, after rounding up to the nearest integer value (but not including redundancy). Refer to Determining the number of GSLs required in Chapter 6, BSC planning steps and rules, for further details on the following equations. Total_RACH/sec =(20*250)*(5+2.86+0.78+1)/3600 = 13.39/s RPCCCH_Cells = (number of PCCCH-enabled cells)/total number of cells in the BSS = 10/20 = 0.5 GSLRACH = ((1-0.5)*13.39*5.5)/(1000*0.25) = 0.147 GSLPaging = 8.5*0.32*1*1/(1000*0.25) = 0.01 The number of GSL TS for run time is represented by: GSLrun_time = GSLRACH+GSLPaging = Round Up (0.147+0.01) = 1

68P02900W21-S 8-80 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

The number of GSL required is GSL= MAX (GSLrun_time, GSLinit_time) = MAX(1,6) = 6

Balancing the GSL load across the LCFs

This step is performed either optionally or automatically by the system at sysgen. If it is desired to perform the operation manually, suggestions and an example are given in Load balancing section of Determining the number of GSLs required in Chapter 6, BSC planning steps and rules.

Calculating the PCU hardware to support the PCU traffic

The following hardware is required: 4 PRP boards, 8 GDS E1 links (GDS) timeslot balanced across the PRPs. 2 PICP boards, 1 PICP board to process GDS LAPD (GSL) and 1 PICP board to process the GBL traffic. 1 MPROC board, 1 MPROC board per PCU shelf (2 for redundancy). 1 PCU shelf with alarm board and 3 power supply / fan assemblies, 1 PCU shelf per 9 PRP boards. 1 PCU cabinet, 1 PCU cabinet per 3 PCU shelves.

After calculating the number of GDS, GBL and GSL E1 links, ensure that there are a sufficient number of PICP boards to cover the GBL and GSL E1 links. The PCU hardware calculation gives the number of PICP boards based only on the ratio of PICP boards to PRP boards. The following calculation takes into account the number of E1 links terminated on the PICP boards for the GBL and GSL E1 links. A PICP board can terminate both GBL and GSL links on the board, but not on the same PMC module. Each PICP has two PMC modules. It was determined that 3 E1 links are required for the GBL. Each PICP can terminate up to 4 GBL links. Therefore, 3/4 of a PICP is required for the GBL E1 links. It was determined that 1 E1 link is required for the GSL (redundant GSL not provided). Each PICP can terminate up to 2 E1 GSL links and up to 60 GSL 64 kbit/s timeslots distributed over two E1s. There is a limit of 2 GSL E1s per PCU. Therefore, 1/4 of a PICP is required for the GSL E1 link. Due to the limitation that a PMC cannot share a GSL and GBL, a second PICP is required. The GBL and GSL E1 link requirements show that one PICP is sufficient to process the link provisioning requirements.

Calculating the increased data traffic load on the E1s between the BSC and BTSs
It is assumed that the EGPRS traffic is in addition to the existing circuit-switched traffic and GPRS traffic already available in the system. 8 timeslots would be required for the EGPRS timeslot traffic on a per cell basis. Therefore, additional 16 x 16 kbits/s timeslots (MCS1 - MCS9) are required on a per BTS site basis, 2 cells per site, in order to carry the GPRS traffic. A decision can be made at this stage on how to allocate the EGPRS carrier timeslots. When EGPRS is enabled, all reserved and switchable timeslots are backhauled from the BTS through the BSC to the PCU. The physical link calculations must take this into account. The CPU processing equations require to take into account the percentage of backhauled timeslots that are active at a given time interval. If GSM circuitswitched statistics are available, they can be used. Refer to Dynamic timeslot allocation in Chapter 3: BSS cell planning.

68P02900W21-S 01 Feb 2007 8-81

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

Calculating the changes in signaling traffic load (RSL load) on the E1s between the BSC and BTSs
For cells without PCCCH (pccch_enabled = 0), the BTS combines the additional signaling load for the EGPRS data traffic with the existing circuit-switched traffic load. This results in an additional load on the existing RSL links between each BTS and the BSC. For cells with PCCCH, EGPRS does not add significant additional control channel load on the RSL. In this case, however, PCCCH reduces the GSM circuit-switched signaling load on the RSL with paging coordination. The new load on the RSL for GPRS is based on the evaluation of the following equation and other supporting equations. Refer to Determining the number of GSLs required in Chapter 6, BSC planning steps and rules for further details on the following equation. RSLGPRS+GSM = RSLGPRS+RSLGSM The GSM RSL calculation should be performed with 64 kbit/s RSL in order to be consistent with the EGPRS calculation.

BSC link provisioning impact

The BSC can need additional hardware in order to support the addition of the EGPRS network traffic. For BSC provisioning, refer to the planning rules in Chapter 6. The BSC needs more E1 terminations in support of the additional E1 links to the PCU and in support of the additional EGPRS traffic over the BTS to BSC interface. In this example, eight E1s were added for the GDS links and one E1 added for the GSL link.

BSS - PCU planning example for EGPRS with QoS and QoS2 enabled
This example uses the same base call model parameters as those used in BSS - PCU planning example for EGPRS except that the QoS feature is enabled. QoS needs new call model parameters to be specified based on QoS usage.

See BSS - PCU planning example for EGPRS to compare the GPRS/EGPRS call model parameters.

Additional data
The QoS feature is enabled. Add two EGPRS carriers per cell with the following call model:

68P02900W21-S 8-82 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

Table 8-25 EGPRS with QoS and QoS2 enabled call model Item Value

Average packet size for GPRS and EGPRS traffic mix (bytes) Average packet size for GPRS and EGPRS traffic mix (bytes) GPRS and EGPRS Traffic per sub/BH (kbytes/hr) - uplink GPRS and EGPRS Traffic per sub/BH (kbytes/hr) - downlink PS attach/detach rate (per sub/BH) PDP context activation/deactivation (per sub/BH) Routing area update Cell Updates GPRS paging rate in pages per second GPRS/EGPRS users per cell Average sessions per user per hour GSM circuit-switched paging rate (pages/second) Ratio of LCSs per call Mobile terminated LCS ratio Ratio of mobiles in the system that are both GSM and GPRS capable Percentage of mobiles that are EGPRS capable Number of PCCCH-enabled cells in the BSS Total number of cells in the BSS STR_GBR1(PoC) STR_GBR2(Audio) STR_GBR2(video) I1_MTBR I2_MTBR I3_MTBR BG_MTBR BE_MTBR

PKULSIZE = 188.71 PKDLSIZE =435.97 ULRATE = 35.59 Data_rate_per_sub = 92.38 PSATT/DETACH = 0.45 PDPACT/DEACT = 0.4 RAU= 1.4 CellUpdate = 0.33 PGPRS = 18.73 250 0.45 PGSM = 60 LCS = 0.1 LRMT = 0.95 NGSM GPRS MS/NAU MS = 100% 5% 10 20 8kbit/s 10kbit/s 18kbit/s 14 10 4 2 2
Continued

68P02900W21-S 01 Feb 2007 8-83

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

Table 8-25 EGPRS with QoS and QoS2 enabled call model (Continued) Item Value

STR_GBR1_USAGE STR_GBR2_USAGE STR_GBR3_USAGE I1_MTBR_USAGE I2_MTBR_USAGE I3_MTBR_USAGE BG_MTBR_USAGE BE_MTBR_USAGE TRAU Type Mobile Class Type CS CS1 CS2 CS3 CS4 MCS1 MCS2 CS Distribution MCS3 MCS4 MCS5 MCS6 MCS7 MCS8 MCS9 Total

15% 3% 4% 3% 10% 25% 15% 25% 64 10 Distribution 10% 22.5% 12.5% 5% 5% 4% 16.5% 0.5% 10.5% 7.5% 2.5% 1.5% 2% 100% Rate 8 12 14.4 20 8.8 11.2 14.8 17.6 22.4 29.6 44.8 54.4 59.2

Selecting a cell RF plan

BLER is compensated by the PRP board headroom required for QoS. The CS coding schemes are set as pre-defined values determined by the QoS feature. For GPRS the maximum rate is 8K and for EGPRS the maximum rate is 14K.

Determining the number of CCCHs at each BTS cell

Use the following equation: NPAGCH = (NAGCH+NPCH) / UCCCH

68P02900W21-S 8-84 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

When pccch_enabled = 0 (PCCCH disabled) at the cell, the BTS combines the additional control channel load for the GPRS data traffic with the existing circuit-switched traffic load onto the CCCH. On the other hand, when pccch_enabled = 1 at the cell, GPRS does not add any additional control channel load on the CCCH. In this case, however, PCCCH reduces the GSM circuit-switched signaling load on the CCCH with paging coordination. Paging coordination, the expected paging rate and the access grant rate have to be taken into account in order to calculate the number of CCCH blocks needed. This calculation should be performed using the guidelines given in Control channel calculations in Chapter 3: BSS cell planning.

Determining number of GPRS and EGPRS carrier timeslots at each BTS cell
Use the equation to determine the number of GPRS timeslots that are required on a per cell basis. In order to use this equation, the expected cell load in kbit/s should be known.
Mean_traffic_load = = GPRS_Users * Data_rate_per_sub * 8bits/byte 3600

250 * 92.38 * 8 = 51.32kbps 3600 1 ( CSi_Rate * CSi_distribution + 100 i =1

TS_Data_Rate = = 17.41kbps

i4

MCSi_Rate * MCSi_Distribution)
i =1

= No_PDCH_TS = Roundup( = Roundup( 51.32 * 2 )=6 17.41

Mean_traffic_load * Mean_load_factor NPBCCH + NPAGCH + NPPCH )+( ) TS_Data_Rate 12

The equation takes into account the amount of local timeslot headroom to allow to the required MTBR. The mean load factor is set to 2 to accommodate peak data scenarios since the mean traffic load is based on averages. The defined timeslot throughput and the PRP board headroom allocated by the QoS feature cover the signaling peak periods.

Calculating the number of GDS E1/ETH links

Compute the number of GDS TRAU E1 channels required for the air interface timeslots required to carry the traffic. Each CS1/CS2 timeslot needs 16K TRAU channel. CS3/CS4 timeslots needs 32K TRAU. MCS1 through MCS9 need a variable VersaTRAU backhaul in units of 64K DS0s on the GDS TRAU interface.

The example here assumes that each EGPRS RTF is equipped with a backhaul of 8 DS0s (rtf_ds0_count = 8). CS3/CS4 is enabled on a carrier. Hence, all the GPRS timeslots for that carrier would need 32K TRAU and the EGPRS carrier would need 64K TRAU.

For this case, it can be calculated that 8 GDS TRAU E1s are required.

68P02900W21-S 01 Feb 2007 8-85

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

Total_GDS_ E1s =

(20cells * 8TS/Cell * 32kTS) + (20cells * 8TS/Cell * 64kTS) 31 * 64k = 7.74

If the number of active timeslots exceeds the limit for one PCU, those cells have to be moved to another BSS. Since the limit is 3360 active timeslots, only one PCU is required.

Calculating the number of active timeslots

A PRP board can be assigned up to 120 timeslots but only 30 are serviced (active) at any given time. The PRP algorithms handle the scheduling of timeslots in an efficient manner dependent on resources available. The QoS feature provides further guidelines on the number of timeslots to assign to a PRP to achieve the requested MTBR per subscriber. PRP board throughput is calculated as follows: Assuming initial coding scheme is CS2 and MCS3: PRP BOARD THROUGHPUT = THRUPUT_TS* {(8000 * %CS1_USAGE) + 12000 * (%CS2_USAGE+CS3_USAGE+CS4_USAGE)} + {(8800 * %MCS1_USAGE) + (11200 * %MCS2_USAGE) + 14800 * (%MCS3_USAGE+ MCS4_USAGE+MCS5_USAGE+ %MCS6_USAGE+%MCS7_USAGE +%MCS8_USAGE+%MCS9_USAGE) } *(100% 16.7%) = 30*{( 8000*10%)+ (12000 * 22.5%) + 14400 * (12.5%+5%) + (8800 * 5%) + (11200 * 4%) + (14800 * 16.5%+0.5%+ 10.5%+7.5%+2.5%+1.5%+2%) } *(100% 16.7%) =30*12976*83.3% = 324270 bit/s. For streaming service, we need convert GBR to EGBR, assuming TD=500ms, BLER =10%, Average_GBR = (8*15%+10*3%+18*4%)/(15%+3%+4%) = 10.09 kbit/s STR_EGBR =(10.09kbit/s,500ms,rho=0.62)/(1+ BLER)= 10.09/0.62*1.1 = 17.9 kbit/s AVERAGEDOWNLINKMTBR = (STR_EGBR*%subs) + (IIMTBR * %subs) + (12 MTBR * %subs) + ... ... (I3_MTBR* %subs) + (BG_MTBR* %subs) + (BE_MTBR* %subs) = (17.9*22%) + (14*3%)+(10*10%)+(4*25%)+(2*15%)+(2*25%) = 7.16 kbit/s Therefore: MAX_QOS_PDCHS_PER_PRP = 324270/(7.16*1000) = 45 If we use one PXP board(70TS), mode 1 then MAX_QOS_PDCHS_PER_PRP = (70/30)* 324270/(7.16*1000) = 105

Calculating the number of PRP boards

The previous example had one GPRS carrier per cell that provided adequate throughput for the calculated 6 timeslots. The new equation also provides 6 timeslots but these are divided between GPRS and EGPRS. The new EGPRS carrier provides 8 timeslots of data capacity that is above the required 6. In this example, we have 8 GPRS timeslots configured as switchable or packet data from the original GPRS carrier and 8 timeslots defined as packet data for the new EGPRS carrier for a total of 16 data capable timeslots per cell. This is a total of 320 data capable timeslots. 320 PDTCHs/45 MAX per board = 8 PRP boards. If PXP board is used, 320 PDTCHs/105 MAX per board = 4 PXP boards. The provisioning of the 8 GDS E1s to 9 PRPs is required in order not to break the 60 timeslots per PRP.

68P02900W21-S 8-86 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

Each PRP must terminate at least one GDS TRAU E1 and the timeslots of an entire cell must terminate on the same PRP.

Calculating the BSC LCF impact to support GPRS traffic

The volume of GPRS and EGPRS signaling traffic increases the BSC LCF GPROC2 processor load. The BSS planning rule for LCF provisioning in the following equation should be used.
GL3_GPRS = 0.002 * Total_RACH/sec * (1 RPCCCH_Cells) + 0.00075 * B * PGPRS * PCCCH_BSS = 0.002 * ( 250 * 20 * 5 ) * (1 0.5) + 0.00075 *10 *1.4 *1 = 0.017 3600

An additional LCF GPROC2 can be added or the GSM circuit-switched provisioning can be examined to check whether an existing LCF GPROC2 could process this additional load.

Calculating the number of GBL links

Using the standard traffic model and Gb formulae:
GPRS_Users_PCU * Data_rate_per_sub *1000) 71 * (1 + ) 3600 PKsize 250 * 20 * 92.38 *1000 71 ) * (1 + ) = 149200bytes/s =( 3600 435.97 Total_Data_rate 2649 + 149200 No_GBL_TS = = = 75 8000 * UGRI 8000 * 0.25 NPCU SGSN = No_GBL_TS/31 = 75/31 = 2.42 User_Data_Rate = (

Hence, 3 Gb links are required.

Calculating the number of GSL links

Use the following equation to calculate the number of 64 kbits/s GSL links required. For this example, the number of users on a PCU is 5000. It assumes that all 20 cells are parented to a single LCF card in the BSC. Evaluating this equation and the supporting expressions results in one 64 kbit/s GSL link being required, assuming that preload is enabled, after rounding up to the nearest integer value (but not including redundancy). Refer to Determining the number of GSLs required in Chapter 6, BSC planning steps and rules for further details on the following equations. Total_RACH/sec =20*250*(5+2.86+0.78+1)/3600 = 13.39/s RPCCCH_Cells = (number of PCCCH-enabled cells)/total number of cells in the BSS = 10/20 = 0.5 GSLRACH = (1-0.5)*13.39*5.5/(1000*0.25) = 0.147 GSLPaging = 8.5*0.32*1*1/(1000*0.25) = 0.01 The number of GSL TS for run time is represented by: GSLrun_time = GSLRACH+GSLPaging = Round Up (0.147+0.01) = 1 The number of GSL required is GSL= MAX (GSLrun_time, GSLinit_time) = MAX(1,6) = 6

68P02900W21-S 01 Feb 2007 8-87

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

Balancing the GSL load across the LCFs

This step can be performed optionally and automatically by the system at sysgen. If it is desired to perform the operation manually, suggestions and an example are given in Load balancing section of Determining the number of GSLs required in Chapter 6, BSC planning steps and rules.

Calculating the PCU hardware to support the PCU traffic

The following hardware is required: 4 PXP boards, 4 ETH links (GDS) timeslot balanced across the PRPs. 3 Gb links. 1 MPROC board, 1 MPROC board per PCU shelf (2 for redundancy). 1 PCU shelf with alarm board and 3 power supply / fan assemblies, 1 PCU shelf per 9 PRP boards. 1 PCU cabinet, 1 PCU cabinet per 3 PCU shelves.

After calculating the number of GDS, GBL, and GSL E1 link, ensure that there are a sufficient number of PICP boards to cover the GBL and GSL E1 links. The PCU hardware calculation calculates the number of PICP boards based only on the ratio of PICP boards to PRP boards. The following calculation takes into account the number of E1 links terminated on the PICP boards for the GBL and GSL E1 links. A PICP board can terminate both GBL and GSL links on the board, but not on the same PMC module. Each PICP has two PMC modules. It was determined that 3 E1 links are required for the GBL. Each PICP can terminate up to 4 GBL links. Therefore, 3/4 of a PICP is required for the GBL E1 links. It was determined that one E1 link is required for the GSL (redundant GSL not provided). Each PICP can terminate up to 2 E1 GSL links and up to 60 GSL 64 kbit/s timeslots distributed over two E1s. There is a limit of 2 GSL E1s per PCU. Therefore, 1/4 of a PICP is required for the GSL E1 link. Due to the limitation that a PMC cannot share a GSL and GBL, a second PICP is required. The GBL and GSL E1 link requirements show that one PICP is sufficient to process the link provisioning requirements.

Calculating the increased data traffic load on the E1s between the BSC and BTSs
It is assumed that the EGPRS traffic is in addition to the existing circuit-switched traffic and GPRS traffic already available in the system. 8 timeslots are required for the EGPRS timeslot traffic on a per cell basis. Therefore, an additional 16 x 16 kbits/s timeslots (MCS1 - MCS9) are required on a per BTS site basis, 2 cells per site, to carry the GPRS traffic. A decision can be made at this stage on how to allocate the EGPRS carrier timeslots. When EGPRS is enabled, all reserved and switchable timeslots are backhauled from the BTS through the BSC to the PCU. The physical link calculations must take this into account. The CPU processing equations require to take into account the percentage of backhauled timeslots that are active at a given time interval. If GSM circuitswitched statistics are available, they could be reviewed to aid in this decision. Refer to Dynamic timeslot allocation in Chapter 3: BSS cell planning.

Calculating the changes in signaling traffic load (RSL load) on the E1s between the BSC and BTSs
For cells without PCCCH (pccch_enabled = 0), the BTS combines the additional signaling load for the EGPRS data traffic with the existing circuit-switched traffic load. This results in an additional load on the existing RSL links between each BTS and the BSC. For cells with PCCCH, EGPRS does not add significant additional control channel load on the RSL. In this case, however, PCCCH reduces the GSM circuit-switched signaling load on the RSL with paging coordination.

68P02900W21-S 8-88 01 Feb 2007

System Information: BSS Equipment Planning

BSS-PCU hardware planning example for EGPRS

The new load on the RSL for GPRS is based on the evaluation of the following equation and other supporting equations. Refer to Determining the number of RSLs required in Chapter 6, BSC planning steps and rules for further details on the following equation. RSLGPRS+GSM = RSLGPRS+RSLGSM The GSM RSL calculation should be performed with 64 kbit/s RSL in order to be consistent with the EGPRS calculation.

BSC link provisioning impact

The BSC can need additional hardware in order to support the addition of the EGPRS network traffic. For BSC provisioning, refer to the planning rules given in Chapter 6. The BSC needs more E1 terminations in support of the additional E1 links to the PCU and in support of the additional EGPRS traffic over the BTS to BSC interface. In this example, eight E1s are added for the GDS links and one E1 added for the GSL link.

68P02900W21-S 01 Feb 2007 8-89

BSS-PCU hardware planning example for EGPRS

Chapter 8: PCU upgrade for BSS

68P02900W21-S 8-90 01 Feb 2007

Chapter 9 Planning exercises

This chapter explains the planning exercises designed to illustrate the use of the rules and formulae. The tables of required equipment lists only the major Motorola supplied items. Equipment such as not cable, external power supplies, and air conditioning equipment are not covered. Refer to the Motorola local office for assistance in ensuring that all necessary items are purchased. This chapter includes the following sections:
Pre-requisites Exercise Determine the hardware requirements for BTS B Determine the hardware requirements for BTS K Determine the hardware requirements for the BSC Determine the hardware requirements for the RXCDR Calculations using alternative call models Planning example of BSS support for LCS provisioning

68P02900W21-S 01 Feb 2007 9-1

Pre-requisites

Chapter 9: Planning exercises

Pre-requisites
Requirements
In the area of interest, a demand analysis has identified the requirement for 11 BTSs with the busy hour Erlang requirement shown in second column of Table 9-1.
Table 3-13 or Table 3-14 (depending on position in location area) in the Call model parameters for capacity calculations section of Chapter 3, BSS cell planning, provides the maximum Erlang capacity for a given number of carriers at 2% blocking. The third column of Table 9-1 provides the number of carriers (RTFs) required.

If hr (AMR) is used, hr usage needs to be taken into account for Erlang calculations. If other blocking factors at the air interface are required, the number of Erlangs quoted in Table 3-14 and Table 3-15 in the Call model parameters for capacity calculations section of Chapter 3, BSS cell planning can be found by reference to standard Erlang B tables for the equivalent number of traffic channels at the required blocking factor.
Table 9-1 Busy hour demand and number of carriers BTS identification Erlangs Antenna configuration

A B C D E F G H J K L Total

6 5 2 5 14 10 5 2 5 20/20/20 5 119

Omni 2 Omni 2 Omni 1 Omni 2 Omni 3 Omni 3 Omni 2 Omni 1 Omni 2 Sector 4/4/4 Omni 2 32 carriers

68P02900W21-S 9-2 01 Feb 2007

System Information: BSS Equipment Planning

Pre-requisites

Network topology
Using a frequency-planning tool, assigns adequate frequencies to support the BTS antenna configurations of Table 9-1. Based on this, initial planning of the network gives the topology shown in Figure 9-1.
Figure 9-1 Network topology
RXCDR MSC

BSC OMC-R BTS K BTS A BTS E

BTS B

BTS F

BTS L

BTS C

BTS G

BTS J

BTS D

BTS H

68P02900W21-S 01 Feb 2007 9-3

Exercises

Chapter 9: Planning exercises

Exercises
Introduction
In order to illustrate the planning steps, the individual hardware requirements for BTS B and BTS K is calculated, followed by the calculation to produce the hardware requirements for the BSC, and RXCDR. The parameters required for the database generation they are noted. The calculations for the hardware capacity use the standard call model given in Chapter 3 and Chapter 6. Half rate usage is not specified for this exercise.

68P02900W21-S 9-4 01 Feb 2007

System Information: BSS Equipment Planning

Determine the hardware requirements for BTS B

Determine the hardware requirements for BTS B

From Figure 9-1 and Table 9-1, it can be seen that BTS B needs two RF carriers in an omni configuration to carry a peak demand of five Erlangs.

Cabinet
From the site requirements and the potential future expansion it can be determined that this site should be built using an M-Cell6 indoor cabinet. For the cabinet and any of the following items, contact the Motorola local office if part numbers are required.

Main site number

Contact the Motorola local office if part numbers are required.

Interface option
Contact the Motorola local office if part numbers are required.

Power redundancy
Contact the Motorola local office if part numbers are required.

Duplexing
Only two antennas are used on this site, so we require to specify duplexing. Contact the Motorola local office if part numbers are required.

Digital redundancy
It is not considered that the purpose of this site justifies the expense of digital redundancy.

Alarm inputs
More that eight alarm inputs are not required, so nothing is needed here.

Memory
Requirement is to have non-volatile code storage and the ability to download code in background mode. Contact the Motorola local office if part numbers are required.

Database option
Contact the Motorola local office if part numbers are required.

Summary
The equipment required and an example of customer order creation for an M-Cell6 indoor (900 MHz) configuration to implement BTS B is listed in Table 9-2 and Table 9-3.

68P02900W21-S 01 Feb 2007 9-5

Determine the hardware requirements for BTS B

Chapter 9: Planning exercises

Table 9-2 Customer ordering guide 900 MHz (M-Cell6 indoor) Question Compulsory

Voltage used

+27 V dc -48 V/60 V dc 110/240 V ac 123 1 2345678

How many cells are required? How many carriers are required per cell? (RF configuration) How many cabinets are required for the RF configuration? What type of combining is required?

1234

CBF (Hybrid) CCB (Cavity) 3 I/P CBF Air T43 (E1) (75 ohm) BIB (E1) (120 ohm) BIB (T1) (120 ohm)

What line interface is required?

Table 9-3 Customer ordering guide 900 MHz (M-Cell6 indoor) Question Options

Is link redundancy required? Is digital redundancy required? Is power redundancy required? Is duplexing required? Is a high power duplexer shelf or external rack required? Are 16-way alarm inputs required? Is a memory card required? Is database required? (Provided by local office) Is ac battery backup required? Select ac battery box options?

Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No
Continued

68P02900W21-S 9-6 01 Feb 2007

System Information: BSS Equipment Planning

Determine the hardware requirements for BTS B

Table 9-3 Customer ordering guide 900 MHz (M-Cell6 indoor) (Continued) Question Options

Is -48 V power supply module (APSM) required? Is Comms Power Supply Module (CPSM) required?

Yes No Yes No

68P02900W21-S 01 Feb 2007 9-7

Determine the hardware requirements for BTS K

Chapter 9: Planning exercises

Determine the hardware requirements for BTS K

Introduction
From Figure 9-1 and Table 9-1, it can be seen that BTS K needs 12 RF carriers in a 4/4/4 sector configuration to carry a peak demand of 20 Erlangs per sector.

Cabinet
From the site requirements and the potential future expansion, it can be determined that this site is included in two or three Horizonmacro cabinets. Alternatively, the site can be included is a better word in a single Horizon II macro indoor cabinet.

Receiver requirements
A single Horizon II macro cabinet solution, a two cabinet Horizonmacro solution and a three cabinet Horizonmacro solution are provided .

Single cabinet Horizon II macro solution

The single cabinet consists of six CTU2 transceivers, operating in pairs and in dual carrier mode to provide the 3 sector 4/4/4 configuration. An optional SURF2 dual band adaptor allows a 900 MHz SURF2 and an 1800 MHz SURFs to be installed in the same cabinet, thus providing dual band capability. A maximum of 3 CTU2s per band can be accommodated for 2/2/2 and 2/2/2 configuration. Refer to Chapter 12, Standard BSS and Horizon BTS configurations for details on configuration.

Two cabinet Horizonmacro solutions

Each cabinet has four carriers of a sector plus two carriers of a shared sector. Two SURF modules support the four carriers in each sector. The shared sector is supported by interconnecting the SURF in the master cabinet to the SURF in the extender cabinet.

Three cabinet Horizonmacro solutions

Each cabinet is dedicated to a sector, to support easy expansion.

Transmitter combining requirements

A one, two, and three cabinet solution is provided .

Single cabinet Horizon II macro solution

Each sector needs two DUPs, one for each CTU2.

68P02900W21-S 9-8 01 Feb 2007

System Information: BSS Equipment Planning

Determine the hardware requirements for BTS K

Two cabinet Horizonmacro solutions

Each sector needs two DCF modules. The shared sector has one DCF module in the master cabinet and the other DCF in the extender cabinet.

Three cabinet Horizonmacro solutions

Each cabinet is dedicated to a sector, which needs one DDF and one HCU modules.

Summary
The equipment required, and an example of customer order creation for a single cabinet Horizon II macro indoor (1800 MHz) configuration, to implement BTS K is listed in Table 9-4 and Table 9-6.
Table 9-4 Customer ordering guide 1800 MHz (Horizon II macro indoor) Question Compulsory 4

Voltage used

+27 V dc 4 -48 V/60 V dc 240 V ac 1 2 3 1 2 3 4 5 6 7 8 1 2 1 2 3 4 DUP and Air 4 DUP and HCU DUP and DHU DUP, HCU and Air DUP, DHU and Air DUP, HCU, DHU and Air T43 (E1) (75 ohm) BIB (E1) (120 ohm)

How many cells are required?

How many carriers are required per cell? (RF configuration)

One carrier (single density) or two carriers (double density) required per CTU2? How many cabinets are required for the RF configuration?

What type of combining is required?

What line interface is required?

68P02900W21-S 01 Feb 2007 9-9

Determine the hardware requirements for BTS K

Chapter 9: Planning exercises

Table 9-5 Customer ordering guide 1800 MHz (Horizon II macro indoor) Questions Options 4

Is digital redundancy required? Is power redundancy required? Is an extra line interface required? Are 16-way alarm inputs required? Is a compact flash (memory) card required? Is a stacking bracket required? Is battery backup required? Is database required? (Provided by local office)

Yes No Yes No Yes No Yes No Yes No Yes No Yes No Yes No

4 4 4 4 4 4 4 4

68P02900W21-S 9-10 01 Feb 2007

System Information: BSS Equipment Planning

Determine the hardware requirements for the BSC

Determine the hardware requirements for the BSC

Introduction
From Figure 9-1 and Table 9-1, it can be seen that this BSC controls 11 BTSs with 32 carriers in 13 cells to carry a peak demand of 119 Erlangs.

BSC to BTS links

Figure 9-1 shows that the number of links connected from the BTSs to the BSC is four.

BSC to MSC links

Reference to standard Erlang B table shows that 119 Erlangs at 1% blocking needs 138 traffic channels. One OML link, one XBL link and one C7 signaling link are required. The number of trunks required is given by: [(1+1)+(1+1)+(1+1)+(138/4)]/31=1.3

Transcoder requirement
None required, remote transcoding.

MSI requirement
Minimum number of MSIs required is given by: (4+2)/2=3

Line interface
Depending on the interface standard used, one BIB or one T43 is sufficient for three MSIs.

GPROC requirement
GPROC function requirements are listed in Table 9-7.
Table 9-6 GPROCs required at the BSC Function Number required

BSP LCFs for MTLs LCFs for RSLs Optional GPROC requirements Redundant BSP (GPROC3), CSFP Redundant LCP Total GPROC3s Total GPROC2s/GPROC3s

1 (GPROC3) 1 1 1 1 1+1 2+1

68P02900W21-S 01 Feb 2007 9-11

Determine the hardware requirements for the BSC

Chapter 9: Planning exercises

The notation n + m means that n is the items required and m the redundancy.

KSW/DSW2 requirement
Device timeslot requirements are listed in Table 9-8.
Table 9-7 BSC timeslot requirements Device Number required

GPROCs XCDR MSI Total timeslots

5*32 = 160 None 3*64 = 192 352

Therefore, the BSC can be accommodated in one BSU shelf and one KSW/DSW2 is required.

KSWX/DSWX requirement
The BSC is included in one shelf so there is no requirement for a KSWX/DSWX.

GCLK requirement
One GCLK per BSC is required plus one for redundancy.

CLKX requirement
The BSC is included in one shelf so there is no requirement for a CLKX.

PIX requirement
The number of PIX boards required depends on the number of external alarms that are required. Use one for this example.

LANX requirement
An adequate number of LANXs are provided for non-redundant operation. A redundant LAN needs one additional LANX per cabinet.

Power supply
Depending on the power supply voltage, two EPSM plus one for redundancy or two IPSM plus one for redundancy is required.

68P02900W21-S 9-12 01 Feb 2007

System Information: BSS Equipment Planning

Determine the hardware requirements for the BSC

Summary
The equipment required to implement the BSC is listed in Table 9-8.
Table 9-8 Equipment required for the BSC Equipment Number required

BSSC2 or BSSC3 cabinet BSU shelf MSI BIB or T43 GPROC3 GPROC2/GPROC3 KSW/DSW2 GCLK PIX (provides up to 8 external alarms) LANX EPSM/IPSM (+27 V) (-48 V)

1 1 3 1 1+1 2+1 1+1 1+1 1 1 2+1

The notation n + m means that n the items required plus m the redundancy.

68P02900W21-S 01 Feb 2007 9-13

Determine the hardware requirements for the RXCDR

Chapter 9: Planning exercises

Determine the hardware requirements for the RXCDR

MSI requirements
It is necessary to provide enough MSIs to communicate on the links to the BSC, for E1 links the traffic connection comes directly from the transcoder card.

Links to the BSC

From the calculation in the previous section BSC to MSC links, it can be seen that there are two links to the BSC.

Links to the OMC-R

From the topology, (see Figure 9-1) it can be seen that a link to the OMC-R from the RXCDR must be provided.

Number of MSIs required

Three E1 links are required. The number of MSI cards is given by:

3 / 2 = 1 .5
This value should be rounded off to 2.

Transcoder requirement
From the calculation in the previous section BSC to MSC links, it can be seen that 138 traffic channels and two C7 links are required. The number of transcoder cards is given by:

138/30 = 5
This applies to either XCDR or GDP card. A GDP2 can transcode 60 channels and if used exclusively is determined by:

138/60 = 3

Enhanced capacity mode must be enabled within the RXCDR to access the second E1 when GDP2s are used in non-MSI slots. XCDR, GDP and GDP2s are mixed within a shelf. The GDP2 needs that the RXU3 shelf be used. The BSSC3 cabinet with two RXU3 shelves can interface up to 76 E1/T1 links. The BSSC2 cabinet can interface only up to 48 E1/T1 link.

68P02900W21-S 9-14 01 Feb 2007

System Information: BSS Equipment Planning

Determine the hardware requirements for the RXCDR

Link interface
From the MSI requirements, it can be seen that, two E1 links to the BSC and one to the OMC-R are required. From the transcoder requirements it can be seen that a further five E1 links are required. A total of eight E1 links are required. The number of BIB/T43s is given by:

8/6 = 1.3
This value should be rounded off to 2.

GPROC requirement
One GPROC2/GPROC3 is required, plus one for redundancy.

KSW/DSW2 requirement
From the number of MSIs, transcoders and E1 links, it can be seen that the total number of timeslots is given by:

2 * 16 + 5 * 16 + 2 * 64 = 240
One KSW/DSW2 is required, plus one for redundancy.

KSWX/DSWX requirement
The RXU is contained in one shelf so there is no requirement for a KSWX/DSWX.

GCLK requirement
One GCLK is required plus one for redundancy.

CLKX requirement
The RXU is contained in one shelf, so there is no requirement for a CLKX.

PIX requirement
The number of PIX boards required depends on the number of external alarms that are required. Use one for this example.

68P02900W21-S 01 Feb 2007 9-15

Determine the hardware requirements for the RXCDR

Chapter 9: Planning exercises

LANX requirement
An adequate number of LANXs are provided for non-redundant operation. A redundant LAN needs one additional LANX per cabinet.

Power supply
Depending on the power supply voltage, two EPSMs plus one for redundancy or two IPSMs plus one for redundancy is required.

Summary
The equipment required to implement the RXCDR is listed in Table 9-9.
Table 9-9 Equipment required for the RXCDR Equipment Number required

BSSC2 or BSSC3 cabinet RXU or RXU3 shelf MSI XCDR/GDP-E1 BIB or T43 GPROC2/GPROC3 KSW or DSW2 GCLK PIX (provides up to 8 external alarms) LANX EPSM/IPSM (+27 V) (-48 V)

1 1 2 5 2 1+1 1+1 1+1 1 1 2+1

The notation n + m means that n the items required plus m the redundancy.

68P02900W21-S 9-16 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Calculations using alternative call models

Introduction
This section is provided to assist the users for whom the planning models given in Chapter 5 BTS planning steps and rules, Chapter 6 BSC planning steps and rules and Chapter 7 RXCDR planning steps and rules are inappropriate. Where this is the case, the various planning tables that are used in the previous example in this chapter is not correct and the actual values require to be derived using the formulae given in Chapter 5 BTS planning steps and rules, Chapter 6 BSC planning steps and rules and Chapter 7 RXCDR planning steps and rules. The necessary calculations are demonstrated in the following examples.

Planning example 1
Dimension a network with following requirements:
GSM software release = GSR6 (Horizon II) Number of sites 4/4/4 sites (BTS: M-Cell6) = 28 Number of omni 2 sites (BTS: M-Cell2) = 2

Call model parameters

Call duration T = 75 s Ratio of SMSs per call S = 0.1 Ratio of location updates per call = 2 Ratio of IMSI detaches per call I = 0.2 (type 2) Location update factor L = 2 + 0.5 * 0.2 = 2.1 Number of handovers per call H = 2 Ratio of intra-BSC handovers to all handovers i = 0.5 MTL link utilization = 35% (0.35) RSL link utilization U = 25% (0.25) CCCH utilization UCCCH = 33% (0.33) Probability of blocking TCH PB-TCH < 2% Probability of blocking SDCCH PB-SDCCH < 1% Probability of blocking on A-interface < 1% Number of BTS sites B = 28 +2 = 30 Number of cells per BSS C = 28 * 3 + 2 = 86 Number of cells per BTS CBTS = 3 GSM paging rate in pages per second PGSM =10 GPRS paging rate in pages per second PGPRS = 0

68P02900W21-S 01 Feb 2007 9-17

Calculations using alternative call models

Chapter 9: Planning exercises

Mean_TBF_Rate = 1 Number of GPRS timeslots NGPRS= 0

Other considerations
Line interface type = E1 Network termination option = T43 Power voltage option = -48/-60 V dc Type of combining used = hybrid (CBF) Dedicated CSFP = YES CSFP redundancy = NO Redundancy for all other modules = YES MTL links redundancy = YES RSL link redundancy = NO Coding schemes CS3 and CS4 used = NO BTS connectivity = star configuration IMSI/TMSI paging = TMSI MTL load balancing granularity = 16

GSR6 (Horizon II) limitations

Maximum BTS sites = 100 Maximum BTS cells = 250 Active RF carriers = 512 Trunks = 3000 C7 links = 16

Cell planning - control channel calculations

From Erlang B tables, the number of Erlangs supported by 32 TCHs with Grade Of Service (GOS) of 2% is 23.72 Erlangs and the number of Erlangs supported by 16 TCHs (2-carrier cell) with GOS of 2%, is 9.83 Erlangs. Total Erlangs offered by a 4/4/4 BTS = 3 * 23.72 = 71.06 Erlangs Total Erlangs offered by an omni 2 BTS = 9.83 Erlang
4-carrier cell - determining the number of CCCHs

Call arrival rate:

ca = e/T = 23.72/75 = 0.316

SMS rate:

s = S * e/T = 0 * 23.72/75 = 0.032

Location update rate:

LU = L * e/T = 2.1 * 23.72/75 = 0.664

68P02900W21-S 9-18 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Access grant rate is given by:

AGCH = ca + S + L = 1.012
From the call model parameters, paging rate PGSM is 10, so the average number of CCCH blocks required to support paging only is:

N PCH = PGSM /(4 * 4.25) = 10/(4 * 4.25) = 0.588

The average number of CCCH blocks required to support AGCH only is given by:

N AGCH = AGCH /(2 * 4.25) = 1.012/(2 * 4.25) = 0.119

Using a CCCH utilization figure, UCCCH of 0.33, the average number of CCCH blocks required to support both PCH and AGCH is given by:

N PAGCH = (N AGCH + N PCH )/U CCCH = (0.119 + 0.588)/0.33 = 2.143

Assuming 1% blocking, the Erlang B tables show that 7 CCCHs are required. This can be supported using a non-combined BCCH with 9 CCCH timeslots. It is recommended to reserve 2 CCCH block for access grant messages.
4 carrier cell - determine the number of SDCCHs per cell

Using the values calculated in the previous section and other call model parameters, the average number of SDCCHs and NSDCCH is given by formulae detailed in Chapter 3 as:

N SDCCH = ca * TC + LU * (TL + Tg ) + s * (Ts + Tg ) = 0.312 * 5 + 0.664 * (4 + 4) + 0.032 * (6 + 4) = 7.211

To support an average number of busy SDCCHs of 7.211 with less than 1% blocking is 14 as determined by use of Erlang B tables. Hence, the number of timeslots required to carry SDCCH signaling traffic is two, with each timeslot offering 8 SDCCHs.
4-carrier cell - determining the number of TCHs

The total number of signaling timeslots required for a 4-carrier configuration with the given call model parameters is three (1 non-combined BCCH timeslot with 9 CCCHs and 2 timeslots with 8 SDCCHs each). Hence, the number of traffic channels per 4 carrier cell = 32 - 3 = 29.
Omni 2 cell - determining the number of CCCHs

Call arrival rate:

ca = e/T = 9.83/75 = 0.131

SMS rate:

s * e/T = 0.1 * 9.83/75 = 0.013

Location update rate:

LU = L * e/T = 2.1 * 9.83/75 = 0.275

Access grant rate is given by:

AGCH = ca + S + L = 0.419

68P02900W21-S 01 Feb 2007 9-19

Calculations using alternative call models

Chapter 9: Planning exercises

From the call model parameters paging rate PGSM is 10, so the average number of CCCH blocks required to support paging only is:

N PCH = PGSM /(4 * 4.25) = 10/(4 * 4.25) = 0.588

The average number of CCCH blocks required to support AGCH only is given by:

N AGCH = AGCH /(2 * 4.25) = 0.419/(2 * 4.25) = 0.049

Using a CCCH utilization figure, UCCCH, of 0.33, the average number of CCCH blocks required to support both PCH and AGCH is given by:

N PAGCH = (N AGCH + N PCH )/U CCCH = (0.049 + 0.588)/0.33 = 1.932

Assuming 1% blocking, the Erlang B tables show that 7 CCCHs are required. This can be supported using a non-combined BCCH timeslot with 9 CCCH blocks. It is recommended to reserve 2 CCCH blocks for access grant messages.
Omni 2 cell - determine the number of SDCCHs per cell

Using the values calculated in the previous section and other call model parameters, the average number of SDCCHs, NSDCCH is given by formula detailed in Chapter 3:

N SDCCH = ca * TC + LU * (TL + Tg ) + s * (Ts + Tg )

= 0.131 * 5 + 0.275 * (4 + 4) + 0.013 * (6 + 4) = 2.988

The number of SDCCHs to support an average number of busy SDCCHs of 2.988 with less than 1% blocking as determined by use of Erlang B tables is approximately 8. The number of timeslots required to carry SDCCH signaling traffic is 1.
Omni 2 cell - determining the number of TCHs

The total number of signaling timeslots required for a 4-carrier configuration with the given call model parameters is three (1 non-combined timeslot BCCH with 9 CCCHs and 2 timeslots with 8 SDCCHs each). Therefore, the number of traffic channels per 2 carrier cell = 16 - 2 = 14 Hence, traffic offered by a 4 carrier cell is the 21.04 Erlangs (29 channels at 2% GOS) and that by a 2 carrier cell is 8.2 Erlangs (14 channels at 2 % GOS). Carried Erlangs for the cells are 20.62 and 8.04, respectively.

BSS planning - determining the number of RSLs

The number of 64 kbit/s RSLs required is given by:
RSLG GSM + GPRS@64K = n * (95 + 67 * S + 35 * H + 25 * L 1000 * U * T

) + (47 + 3 * C) * P

6 * Mean_TBF_R ate * N GPRS GSM + (52 + C) * PGPRS + 8000 * U 1000 * U

Where, n is the number of TCHs under the BTS. Hence, for a 4/4/4 site (no GPRS):
RSL GSM +GPRS@64K = 29 * 3 * 95 + 67 * 0.1 + 35 * 2 + 25 * 2.1 1000 * 0.25 * 75

) + (47 + 3 * 3) *10 + (52 + 3) * 3 +

8000 * 0.25

6*0 = 1.40 1000 * 0.25

The number of RSLs required per 4/4/4 site is 2 and that for an omni 2 site is 1 (calculated in similar way).

68P02900W21-S 9-20 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

BSC to BTS E1 interconnect planning

Number of E1 links required between a BSC and BTS is given by:

{[( N BSCBTS =

nE GPRS i =0

RTF_DSO_COUNTi) + (nC

GPRS

* 4) + (nG GPRS * 2) + L16/4]} + L64

31

(CS3 and CS4 are not used.) Number of E1 links required between each 4/4/4 BTS and BSC:

((0 * 8) + (0 * 4) + (12 * 2) + 0) + 2 ~1 31 ((0 * 8) + (0 * 4) + (2 * 2) + 0) + 1 ~1 31

Number of E1 links required between each omni 2 BTS and BSC is given by:

Hence, only one E1 interconnection is required between each BTS and BSC for the given site configurations (provided they are in star configurations), giving a total of 30 E1 links.
Determining the number of LCF GPROCs for RSL processing

Number of LCF-RSLs required is given by:

n *(1+ 0.35*S = 0.34* H*(1 0.4*i) + 0.32* L) C G L3 = + (0.00075 * PGSM + 0.004) * B + (19.6*T) 120
Where n is the number of TCHs under a BSC:

2464* (1+ 0.35* 0.1 + 0.34* 2 * (1 0.4 * 0.5) + 0.32* 2.1) 86 GL3 = + (0.00075 *10+ 0.004 ) * 30+ (19.6 * 75) 120
The number of LCFs for RSL processing is 5.
Determining the number of MTLs

Total Erlangs offered by the BSC with 28 sites, 4/4/4 configuration and 2 omni 2 site.

= 28 * 3 * 21.04 + 2 * 8.04 = 1784 Erlangs

Total Erlangs carried by the BSC with 28 sites, 4/4/4 configuration and 2 omni 2 site.

= 28 * 3 * 20.62 + 2 * 8.04 = 1748 Erlangs

The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 1812; check that the figure is within limits. Number of pages per call is given by:

PPC = PGSM * T/N = 10 * 75/1812 = 0.42

Using the call model parameters, the number of MTLs can be calculated using formulae detailed in Chapter 6.

68P02900W21-S 01 Feb 2007 9-21

Calculations using alternative call models

Chapter 9: Planning exercises

Maximum number of Erlangs supported by a C7 link is given by:

n link = n link =

(1000 * U * T) (40 + 47 * S + 22 * H * (1 0.8 * i) + 24 * L + 9 * PPC ) (1000 * 0.25 * 75) = 150 Erlangs (40 + 47 * 0.1 + 22 * 2 * (1 0.8 * 0.5) + 24 * 2.1 + 9 * 0.42)

Maximum number of Erlangs supported by a GPROC supporting a C7 signaling link is given by:

nl LCFMTL = nl LCFMTL =

(20 * T) (1 + 0.16 * S + 0.5 * H * (1 0.6 * i) + 0.42 * L + PPC * (0.005 * B + 0.05))

(20 * 75) (1 + 0.16 * 0.1 + 0.5 * 2 * (1 0.6 * 0.5) + 0.42 * 2.1 + 0.42 * (0.005 * 30 + 0.05)) = 560 Erlangs

Hence:

= nlmin = min(n link' nlLCF MTL ) = 150 Erlangs

Amount of traffic (or number of trunks) each logical link holds:

N logical = 1812/16 = 113.25

Using a MTL load-sharing granularity of 16 the number of logical links each MTL can handle:

150 n log_per_mtl = round down ~1 113.25

The number of required MTLs are given by:

16 mtls = round up = 16 1
Check that the figure is within limits.
Determining the number of LCFs for MTL processing

Using the formula detailed in Chapter 6 BSC planning steps and rules, since:

2 * n link < nlLCF MTL

16 N LCF = round up = 8 2
XBL requirements

Refer to Table 6-11 in Chapter 6 BSC planning steps and rules. Number of XBLs required = 2

68P02900W21-S 9-22 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

GPROC requirements

Number of GPROCs required for MTL processing = 8 Number of GPROCs required for RSL processing = 5 Total number of LCF GPROCs required = 13 (check that the figure is within limits) Number of BSP GPROC3s (with redundancy) = 2 Number of CSFP GPROCs = 1 Total number of GPROCs for BSC= 17 (16 +1 for redundancy)
MSI requirements

Each MSI interfaces two E1 links. Number of E1 links required at the BSC for interconnecting with the RXCDR is:

N logical = 1812/16 = 113.25

Hence number of MSIs required for BSC to RXCDR interface = 8. Each BTS site in this example needs one E1 interconnection. Hence, the number of MSIs required for BTSs is 30/2 = 15. Total number of MSIs required at the BSC = 23
KSW/DSW2 requirements

Number of TDM timeslots is given by:

N = (G * n) + (M * 64) = (R *16)
Where G is the number of GPROCs; M is the number of MSIs, and R is the number of XCDR/GDPs at the BSC.

N = 17 * 32 + 23 * 64 = 2016
Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 2 non-redundant KSWs/DSW2s are required for this configuration. For redundancy, an additional 2 KSWs/DSW2s are required. Total KSWs/DSW2s required (with redundancy) = 4
BSU shelves

The number of BSU shelves required is the greater of the two calculations (since we have no local transcoding):

N BSU = G/8 = 17/8 ~ 3 BSU shelves N BSU = (M + R)/12 = 23/12 ~ 2 BSU shelves
Ensure that the following is true for each shelf.

N + (G * n) + (M * 64) + (R *16) 1016

Therefore, 3 BSU shelves are required to accommodate all the hardware needed for this configuration.
KSWX/DSWX requirements

The KSWX/DSWX extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in the multi-shelf configuration. The KSWX/DSWX can be used in expansion, remote and local modes. We need 3 BSU shelves with 2 non-redundant KSWs/DSW2s, which implies that we have 1 expansion shelf and 1 extension shelf.

68P02900W21-S 01 Feb 2007 9-23

Calculations using alternative call models

Chapter 9: Planning exercises

Number of KSWXs/DSWXs required is sum of the KSWXE, KSWXR, and KSWXL

N KX = N KXE + N KXR + N KXL

NKXE = K*(K-1) = 2 *1 = 2 (K is the number of non-redundant KSWs/DSW2s) NKXR = SE = 1 (SE is the number of extension shelves) NKXL = K + SE = 3 NK X = 2 + 1 + 3 = 6 Therefore, the number of KSWXs/DSWXs required (with redundancy) = 12
GCLK requirements

The generic clock generates all the timing reference signals required by a BSU. One GLCK is required at each BSC. Number of GCLKs required (with redundancy) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one BSU. The number of CLKXs required is given by:

N CLKX = Round up (E/6) * (1 + R F )

Where E is the number of expansion/extension shelves and RF is the redundancy factor.

N CLKX = Round up (3/6) * (1 + 1) = 1

The number of CLKXs required (with redundancy) = 2
LANX requirements

N LANX = N BSU * (1 + R F ) = 3 * 2 = 6
Where RF is the redundancy factor. Total number of LANXs required (with redundancy) = 6
PIX requirements

PIX provides eight inputs and four outputs for site alarms.

PIX 2 * Number of BSUs = 6

Line interfaces

Number of T 43s = Number of MSIs/3 = 23/3 ~ 8

The number of T43 boards required is Eight.
Digital power supply requirements

Number of PSUs required is given by:

PSUs = N BSU * (2 + R F )

PSUs = 3 * (2 + 1) = 9
One redundant PSU is required for each BSU shelf, hence, the total number of PSUs required is 12. Non Volatile Memory (NVM) board for BSC (optional).

NVM = 0 or 1

68P02900W21-S 9-24 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

RXCDR planning
Conventionally, multiple BSCs connect to an RXCDR and vice versa, for load sharing and redundancy purposes. Assuming that two same sized BSCs connect to 2 RXCDRs, so that the signaling traffic and voice traffic is equally distributed over 2 RXCDRs. Each RXCDR would be dimensioned using the rules in the following text.
Determining the number of RXCDR to MSC links

Number of RXCDR to MSC links is given by:

N RXCDR - MSC = (C + X + T)/31

Where: C is the number of MTL links required. X is the number of OML links required. T is the number of trunks between MSC and BSC.

N RXCDR - MSC = (16 + 2 + 1812)/31 = 60

Each XCDR card terminates one E1 interconnection; hence, number of non-redundant XCDR cards required is 60.
MSI requirements for RXCDR

As calculated in MSI requirements, the number of BSC-RXCDR links is 16 and each MSI card interfaces 2 E1 links. Hence, 8 MSI cards are required on the RXCDR.
RXU shelves

The number of RXU shelves required is given by (assuming that NVM board is fitted).

N RXU = max[M/5, (R + N NVM )/16] = max(8/5,61/16) ~ 4

Hence, 4 RXU shelves are required to equip 58 XCDR cards and 8 MSI cards.
GPROC requirements for RXCDR

Each shelf should have minimum of one GPROC. Hence, 4 non-redundant GPROCs are required. If the operator chooses to use redundancy, 8 GPROCs is required.
KSW/DSW2 requirements for RXCDR

The number of TDM slots required for GPROCs, MSIs and XCDRs is given by:

TDM timeslots required = G * n + R * 64 + M * 16

TDM timeslots required = 8 * 32 + 8 * 64 + 60 *16 = 1728

Each KSW/DSW2 provides 1016 timeslots on the TDM highway, hence, 2 non-redundant KSWs/DSW2s are required for the RXCDR with this configuration.
KSWX/DSWX requirements for RXCDR

The number of KSWXs/DSWXs required is the sum of KSWXE, KSWXR, and KSWXL. We need 4 RXU shelves with 2 non-redundant KSWs/DSW2s, which implies that there is 1 expansion shelf and 2 extension shelves.

N KX = N KXE + N KXR + N KXL

68P02900W21-S 01 Feb 2007 9-25

Calculations using alternative call models

Chapter 9: Planning exercises

N KXE = K * (K 1) = 2 * 1 = 2
K is the number of non-redundant KSWs/DSW2s.

N KXR = S E = 2
SE is the number of extension shelves.

N KXL = K + SE = 4 N KX = 2 + 2 + 4 = 8
The number of KSWXs/DSWXs (with redundancy) = 16
GCLK requirements

The generic clock generates all the timing reference signals required by a RXU. One GLCK is required at each RXCDR. Number of GCLKs required (with redundancy) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one RXU.

N CLKX = Round up(E/6) * (1 + R F )

Where Is

E RF

the number of expansion/extension shelves. the redundancy factor.

N CLKX = Round up(4/6) = 1

The number of redundant CLKXs required is 2.
LANX requirements

Number of LANXs required is given by:

N LANX = N RXU * (1 + R F ) = 4 * 2 + 8
Where RF it the redundancy factor. Total number of LANXs required with redundancy = 8
PIX requirements

PIX provides eight inputs and four outputs for site alarms.

PIX 2 * Number of RXUs = 8

Hence, 8 PIX cards are required for the RXCDRs.
Line interfaces

Number of T43s = Number of E1s/6 = (60 + 15)/6 ~ 13

The number of T43 boards required is 13.

68P02900W21-S 9-26 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Digital power supply requirements

PSUs = 2 * RXUs = 8
One redundant PSU is required for each RXU shelf, hence, total number of PSUs required of is 12.
Non-volatile memory (NVM) board for RXCDR (optional)

NVM = 1(in this example)

Planning example 2
Dimension a network with the following requirements:
GSM software release = GSR6 (Horizon II) Number of sites 2/2/2 sites (BTS: M-Cell6) = 55 Number of omni 2 sites (BTS: M-Cell2) = 5

Call model parameters

Call duration T = 100 s Ratio of SMSs per call S = 0.12 Ratio of location updates per call = 2.4 Ratio of IMSI detaches per call I = 0.2 (type 2) Location update factor L = 2.4 + 0.5 * 0.2 = 2.5 Number of handovers per call H = 2.6 Ratio of intra-BSC handovers to all handovers i = 0.6 MTL link utilization = 35% (0.35) RSL link utilization U = 25% (0.25) CCCH utilization UCCCH = 33% (0.33) Probability of blocking TCH PB-TCH < 2% Probability of blocking SDCCH PB-SDCCH < 1% Probability of blocking on A-interface < 1% Number of BTS sites B = 55 + 5 = 60 Number of cells per BTS CBTS = 3 GSM paging rate in pages per second PGSM = 10 GPRS paging rate in pages per second PGPRS = 0 Mean_TBF_Rate = 1 Number of GPRS timeslots NGPRS = 0

Other considerations
Line interface type = E1 Network termination option = T43 Power voltage option = -48/-60 V dc

68P02900W21-S 01 Feb 2007 9-27

Calculations using alternative call models

Chapter 9: Planning exercises

Type of combining used = Hybrid (CBF) Dedicated CSFP = YES CSFP redundancy = NO Redundancy for all other modules = YES MTL links redundancy = YES RSL link redundancy = NO Coding schemes CS3 and CS4 used = NO BTS connectivity = Star configuration IMSI/TMSI paging = TMSI MTL load balancing granularity = 64 NVM board fitted at RXCDR

GSR6 (Horizon II) limitations

Maximum BTS sites = 100 Maximum BTS cells = 250 Active RF carriers = 512 Trunks = 3000 C7 links = 16

Cell planning - control channel calculations

From Erlang B tables, the number of Erlangs supported by 16 TCHs (2-carrier cell) with GOS of 2% is 9.83 Erlangs. Total Erlangs offered by a 2/2/2 BTS = 3 * 9.83 = 29.49 Erlangs Total Erlangs offered by an omni 2 BTS = 9.83 Erlangs
2-carrier cell - determining the number of CCCHs

Call arrival rate:

call = e/T = 9.83/100 = 0.0983

SMS rate:

S = S * e/T = 0.12 * 9.83/100 = 0.012

Location update rate:

LU = L * e/T = 2.5 * 9.83/100 = 0.246

Access grant rate is given by:

AGCH = call + S + L = 0.356

From the call model parameters, the paging rate PGSM is 8, so the average number of CCCH blocks required to support paging only is:

N PCH = PGSM /(4 * 4.25) = 8/(4 * 4.25) = 0.471

68P02900W21-S 9-28 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

The average number of CCCH blocks required to support AGCH only is given by:

N AGCH = AGCH /(2 * 4.25) = 0.356/(2 * 4.25) = 0.042

Using a CCCH utilization figure (UCCCH) of 0.33, the average number of CCCH blocks required to support both PCH and AGCH is given by:

N PAGCH = ( N AGCH + N PCH ) / U CCCH = (0.042 + 0.471) /0.33 = 1.553

Assuming 1% blocking, the Erlang B tables show that 6 CCCHs are required. This can be supported using a non-combined BCCH with 9 CCCH timeslots. It is recommended to reserve 3 CCCH blocks for access grant messages.
Determine the number of SDCCHs per cell

Using the values calculated in the previous section and other call model parameters, the average number of SDCCHs, NSDCCH, is given by the formula mentioned in Chapter 3:

NSDCCH = call * TC + LU * (TL + Tg ) + s * (TS + Tg ) = 0.098 * 5 + 0.246 * (4 + 4) + 0.012 * (6 + 4) = 2.575

The number of SDCCHs to support an average number of busy SDCCHs of 2.575 with less that 1% blocking as determined by use of Erlang B tables is 8. Hence, the number of timeslots required to carry SDCCH signaling traffic is 1, with the timeslot offering 8, SDCCHs.
Determining the number of TCHs

Total number of signaling timeslots required for a 2-carrier configuration with the given call model parameters is two (1 non-combined BCCH timeslot with 9 CCCHs and 1 timeslot with 8 SDCCHs each). Therefore, the number of traffic channels per 2 carrier cell = 16 2 = 14. Hence, traffic offered by a 2-carrier cell is 8.2 Erlangs (14 channels at 2 % GOS). Carried Erlangs for the cells is 8.04 Erlangs.

BSS planning - determining the number of RSLs

The number of RSLs (64 kbits/s) required is determined by using the following formula:

RSL GSM + GPRS @ 64K = 14 * 3 * (95 + 67 * 0 .12 + 35 * 2 .6 + 25 * 2.5) ( 47 + 3 * C ) * PGSM + (52 + C ) * PGPRS 3 * 2.6 + 25 * 2 .5 + 1000 * U * T 8000 * U 6 * Mean _ TBF _ Rate * N GPRS + 1000 * U
Where n is the number of TCHs under the BTS. Hence, for a 2/2/2 site (no GPRS):

RSL GSM + GPRS @ 64K = 14 * 3 * (95 + 67 * 0.12 + 35 * 2.6 + 25 * 2.5) ( 47 + 3 * 3) *10 + (52 + C) * 3 6*0 + + = 0.79 1000 * U * T 8000 * 0.25 1000 * U
For both 2/2/2 site and an omni 2 site, the number of RSLs required is one.

68P02900W21-S 01 Feb 2007 9-29

Calculations using alternative call models

Chapter 9: Planning exercises

BSC to BTS E1 interconnect planning

Number of E1 links required between a BSC and BTS is given by:

nE GPRS RTF _ DSO _ Count + ( nC GPRS * 4) + ( nG GPRS * 2) + L16 / 4 + L 64 i = 0 N BSC - BTS = 31

(CS3 and CS4 are not used.) Number of E1 links required between each 2/2/2 BTS and BSC is given by:

((0 * 8) + (0 * 4) + (6 * 2) + 0) ~1 31 ((0 * 8) + (0 * 4) + (2 * 2) + 0) + 1 ~1 31

Number of E1 links required between each omni 2 BTS and BSC is given by:

Hence, only one E1 interconnect is required between each BTS and BSC for the given site configurations (provided they are in star configurations), giving a total of 60 E1 links.
Determining the number of LCF GPROCs for RSL processing

Number of LCF-RSLs required is given by:

G L3

n * (1 + 0.35 * S + 0.34 * H * (1 0.4 * i) + 0.32 * L) + (0.00075* PGSM + 0.004) 19.6 * T = * B + C 120

2380* (1 + 0.35*1.12 + 0.34 * 2.6 * (1 0.4 * 0.6) + 0.32 * 2.5) + (0.00075* 8 + 0.004) 19.6 *100 = * 60 + 170 120

Where n is the number of TCHs under a BSC:

G L3

The number of LCFs for RSL processing is 6.

Determining the number of MTLs

Total Erlangs offered by the BSC with 55 sites, 2/2/2 configuration and 5 omni 2 sites: =55*3*8.2+5*8.2=1394 Erlangs Total Erlangs carried by the BSC with 55 sites, 2/2/2 configuration and 5 omni 2 site: =55*3*8.04+5*8.04=1366.8 Erlangs The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 1423. Check figure is within limits. Number of pages per call is calculated by using the following formula: PPC = PGSM * T/N = 8 * 100 / 1423 = 0.57

68P02900W21-S 9-30 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Using the call model parameters, the number of MTLs can be calculated using the formulae mentioned in Chapter 6 of this manual. Maximum number of Erlangs supported by a C7 link is given by:

n Link =

(1000 * U * T) (40 + 47 * S + 22 * H * (1 0.8 * I) + 24 * L + 9 * PPC ) (1000 * 0.25 *100) = 178Erlangs (40 + 47 * 0.12 + 22 * 2.6 * (1 0.8 * 0.6) + 24 * 2.5 + 9 * 0.57) (20 * T) (1 + 0.16 * S + 0.5 * H * (1 0.6 * i) + 0.42 * L + PPC * (0.005 * B + 0.05))

n Link =

nl LCF MTL =

nlLCFMTL =
Hence:

(20*100) (1 + 0.16* 0.12 + 0.5 * 2.6 * (1 0.6 * 0.6) + 0.42* 2.5 + 0.57* (0.005* 60 + 0.05))

n Link nl min = min n = 178Erlangs LCF MTL

Amount of traffic (or number of trunks) each logical link can hold is given by:

nllog ical =

1423 = 22.23 64

using a MTL load-sharing granularity of 64. The number of logical links each MTL can handle is given by:

nllog per mtl = Round down (178 / 22.23) ~ 8 = 22.23

The number of required MTLs:

mtls = Round up(64 / 8) = 8

Check this figure is within limits.
Determining the number of LCFs for MTL processing

Using the formula mentioned in Chapter 6, since:

2 * n link < nlLCF MTL

8 N LCF = Roundup = 4 2
XBL requirements

Referring to Table 6-11 in Chapter 6 BSC planning steps and rules. Number of XBLs required = 2

68P02900W21-S 01 Feb 2007 9-31

Calculations using alternative call models

Chapter 9: Planning exercises

GPROC requirements

Number of GPROCs required for MTL processing = 4 Number of GPROCs required for RSL processing = 5 Total number of LCF GPROCs required = 9 (Check this figure is within limits) Number of BSP GPROC3s (with redundancy) = 2 Number of CSFP GPROCs = 1 Total number of GPROCs for BSC = 13 (12+1 for redundancy)
MSI requirements

Each MSI interfaces two E1 links. Number of E1 links required at the BSC for interconnecting with the RXCDR and without redundancy is: (8 + 2 + 2 + 1423/4)/31 ~ 12 Hence, the number of MSIs required for BSC to RXCDR interface = 6. Each BTS site in this example needs one E1 interconnect. Hence, the number of MSIs required for BTSs is 60/2 = 30. Total number of MSIs required at the BSC = 36.
KSW/DSW2 requirements

Number of TDM timeslots is given by: N = (G * n) + (M * 64) + (R * 16)

Where Is

G M R N = 13 * 32 + 36 * 64 = 2720

the number of GPROCs. the number of MSIs. the number of GDP/XCDRs in the BSC.

Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 3 non-redundant KSWs/ DSW2s is required for this configuration. For redundancy, 3 additional KSWs/DSW2s are required. Total KSWs/DSW2s required (with redundancy) = 6
BSU shelves

The number of BSU shelves required is the greater of the two calculations (since we have no local transcoding): NBSU G/8 = 13/8 ~ 2 BSU shelves NBSU (M + R)/12 = 36/12 ~ 3 BSU shelves Ensure that the following is true for each shelf: N + (G *n) + (M * 64) + (R * 16) 1016 Therefore, 3 BSU shelves are required to accommodate all the hardware needed for this configuration.

68P02900W21-S 9-32 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

KSWX/DSWX requirements

The KSWX/DSWX extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in the multi-shelf configuration. The KSWX/DSWX is used in expansion, remote and local modes. We need 3 BSU shelves with 3 master/redundant KSWs/DSW2s, which implies 2 expansion shelves. Number of KSWXs/DSWXs required is the sum of KSWXE, KSWXR, and KSWXL: NKX = NKXE + NKXR + NKXL NKXE = K*(K-1) = 3 *2 = 6 (K is the number of non-redundant KSWs/DSW2s) NKXR = SE = 0 (SE is the number of extension shelves) NKXL = K + SE = 3 NKX = 6 + 0 + 3 = 9 The number of KSWXs/DSWXs required (with redundancy) = 18
GCLK requirements

The generic clock generates all the timing reference signals required by a BSU. One GLCK is required at each BSC. Number of GCLKs required (with redundancy) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one BSU. Number of CLKXs required is given by: NCLKX = Roundup(E/6) * (1 + RF) Where E is the number of expansion/extension shelves and RF is the redundancy factor. NCLKX = Roundup(3/6) * (1 + 1) = 2 The number of CLKX required (with redundancy) = 2
LANX requirements

NLANX = NBSU * (1 + RF) = 3 * 2 = 6 Where RF is the redundancy factor. Total number of LANXs required (with redundancy) = 6
PIX requirements

PIX provides eight inputs and four outputs for site alarms: PIX Number of BSUs = 6
Line interfaces

Number of T43s = Number of MSIs/3 = 36/3 ~ 12 The number of T43 boards required is 12.
Digital power supply requirements

The number of PSUs required is given by: PSUs = NBSU * (2 + RF) PSUs = 3 * (2 + 1) = 9 One redundant PSU is required for each BSU shelf, hence total number of PSUs required is 9.
Non-volatile memory (NVM) board for BSC (optional)

NVM = 0 or 1

68P02900W21-S 01 Feb 2007 9-33

Calculations using alternative call models

Chapter 9: Planning exercises

RXCDR planning
Conventionally, multiple BSCs connect to an RXCDR and vice versa, for load sharing and redundancy purposes. Assuming that two same sized BSCs connect to 2 RXCDRs so that the signaling traffic and voice traffic is equally distributed over 2 RXCDRs. Each RXCDR would be dimensioned using the rules in the following text.
Determining the number of RXCDR to MSC links

Number of RXCDR to MSC links is given by: NRXCDR-MSC = (C + X + T)/31

Where Is

C X T

the number of MTL links required. the number of OML links required. the number of trunks between MSC and BSC.

NRXCDR-MSC = (16 + 2 + 1423)/31 = 47 Each XCDR card terminates one E1 interconnect. Hence, the number of non-redundant XCDR cards required is 47.
MSI requirements for RXCDR

As calculated in MSI requirements, the number of BSC-RXCDR links is 12. Each MSI card interfaces 2 E1 Links, hence, 6 MSI cards are required on the RXCDR.
RXU shelves

The number of RXU shelves required is given by (assumes an NVM board is fitted): NRXU = max(M/5, (R + NNVM)/16) = max(6/5, (47 + 1)/16) ~ 3 Ensure the following is true for each shelf: N + (G * n) + (M * 64) + (R * 16) 1016 Hence, 3 RXU shelves are required to equip 47 XCDR cards and 6 MSI cards.
GPROC requirements for RXCDR

Each shelf should have minimum of one GPROC. Hence, 3 non-redundant GPROCs are required. If the operator chooses to use redundancy, 6 GPROCs are required.
KSW/DSW2 requirements for RXCDR

Number of TDM slots required for the GPROCs, MSIs and XCDRs is given by: TDM timeslots required = G * n + M * 64 + R * 16 TDM timeslots required = 6 * 32 + 6 * 64 + 47 * 16 = 1328 Each KSW/DSW2 provides 1016 timeslots on the TDM highway, hence, 2 non-redundant KSWs/DSW2s are required for RXCDR with this configuration.
KSWX/DSWX requirements for RXCDR

The number of KSWXs/DSWXs required is the sum of KSWXE, KSWXR, and KSWXL. The calculations imply that 1 expansion and 1 extension shelf are required.

68P02900W21-S 9-34 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

NKX = NKXE + NKXR + NKXL NKXE = K * (K - 1) = 2 * 1 = 2 K is the number of non-redundant KSWs/DSW2s. NKXR = SE = 1 SE is the number of extension shelves. NKXL = K + SE = 3 NKX = 2 +1 +3 = 6 The number of KSWXs/DSWXs (with redundancy) = 12
GCLK requirements

The generic clock generates all the timing reference signals required by a RXU. One GLCK is required at each RXCDR. Number of GCLKs required (with redundancy) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one RXU: NCLKX = Roundup(E/6) * (1 + RF)
Where Is

E RF NCLKX = Roundup(2/6) * (1 + 1) = 2

the number of expansion/extension shelves. the redundancy factor.

The number of redundant CLKXs required is 2.

LANX requirements

Number of LANXs required is given by: NLANX = NRXU * (1 + RF) = 3 * 2 = 6 Where RF is the redundancy factor. Total number of LANXs required with redundancy = 6
PIX requirements

PIX provides eight inputs and four outputs for site alarms. PIX 2 * Number of RXUs = 6 Hence, 6 PIX cards are required for RXCDR.
Line interfaces

Number of T43s = Number of E1s/6 = (47 + 12)/6 ~ 10 The number of T43 boards required is 10.
Digital power supply requirements

PSUs = 2 * RXUs = 6 One redundant PSU is required for each RXU shelf, hence, the total number of PSUs required is 9.

68P02900W21-S 01 Feb 2007 9-35

Calculations using alternative call models

Chapter 9: Planning exercises

Non-volatile memory (NVM) board for RXCDR (optional)

NVM = 1 (in this example)

Planning example 3
Dimension a network with following requirements:
GSM software release = GSR7 Number of sites 6/6/6 sites (BTS: M-Cell6) = 20 No AMR support No Enhanced capacity mode support

Call model parameters

Call duration T = 120 s Ratio of SMSs per call S = 0.12 Ratio of location updates per call = 2.4 Ratio of IMSI detaches per call I = 0 Location update factor L = 2.4 + 0.5 * 0 = 2.4 Number of handovers per call H = 2.5 Ratio of intra-BSC handovers to all handovers i = 0.6 Paging rate per second PGSM = 8 pages per second Number of cells at the BTS CBTS = 3 MTL link utilization = 35% (0.35) RSL link utilization U = 25% (0.25) CCCH utilization UCCCH = 33% (0.33) Probability of blocking TCH PB-TCH < 2% Probability of blocking SDCCH PB-SDCCH < 1% Probability of blocking on A-interface < 1%

Other considerations
Line interface type = E1 Network termination option = T43 Power voltage option = -48/-60 V dc Type of combining used = Hybrid (CBF) Dedicated CSFP = YES CSFP redundancy = NO Redundancy for all other modules = YES MTL links redundancy = YES RSL link redundancy = NO Coding schemes CS3 and CS4 used = NO

68P02900W21-S 9-36 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

BTS connectivity = Star configuration IMSI/TMSI paging = TMSI MTL load balancing granularity = 16 NVM board fitted at BSC and RXCDR

GSR7 limitations (assuming big BSC system)

Maximum BTS sites = 100 Maximum BTS cells = 250 Active RF carriers = 512 Trunks = 3200 C7 links = 16

Cell planning - control channel calculations

From Erlang B tables, the number of Erlangs supported by 48 TCHs (6-carrier cell) with GOS of 2% is 38.39 Erlangs. Total Erlangs offered by a 6/6/6 BTS = 3 * 38.39 = 115.17 Erlangs
6-carrier cell - determining the number of CCCHs

Call arrival rate:

call = e / T = 38.39 / 120 = 0.32

SMS rate:

call = S * e / T = 0.12 * 38.39 / 120 = 0.038

Location update rate:

LU = L * e / T = 2.4 * 38.39 / 120 = 0.768

Access grant rate is given by:

AGCH = call * S + LU = 0.32 + 0.038 + 0.768 = 1.126

From the call model parameters, the paging rate P is 8, so the average number of CCCH blocks required to support paging only is: NPCH = PGSM/(4*4.25) = 8/(4*4.25) = 0.471 The average number of CCCH blocks required to support AGCH only is given by: NAGCH = AGCH/(2 * 4.25) = 0.132 Using a CCCH utilization figure (UCCCH) of 0.33, the average number of CCCH blocks required to support both PCH and AGCH is given by: NPAGCH = (NAGCH + NPCH)/UCCCH = (0.132 + 0.471)/0.33 = 1.828 Assuming 1% blocking, the Erlang B tables show that 6 CCCHs are required. This can be supported using a non-combined BCCH with 9 CCCH timeslots. It is recommended to reserve 3 CCCH blocks for access grant messages.

68P02900W21-S 01 Feb 2007 9-37

Calculations using alternative call models

Chapter 9: Planning exercises

Determining the number of SDCCHs per cell

Using the values calculated in the previous section and other call model parameters, the average number of SDCCHs and NSDCCH is given by the formula mentioned in Chapter 3. NSDCCH = call * TC + LU * (TL + Tg) + s * (Ts + Tg) = 8.126 To support an average number of busy SDCCHs of 8.126 Erlangs signaling traffic with less that 1% blocking is 14 as determined by use of Erlang B tables. Hence, the number of timeslots required to carry SDCCH signaling traffic is 2, with each timeslot offering maximum 8 SDCCHs.
Determining the number of TCHs

Total number of signaling timeslots required for a 6-carrier configuration, with the given call model parameters is 3 (1 non-combined BCCH timeslot with 9 CCCHs and 2 timeslots with 8 SDCCHs each). Therefore, the number of traffic channels per 6 carrier cell = 48 - 3 = 45. Hence, traffic offered by a 6-carrier cell is 35.61 Erlangs (45 traffic channels at 2% GOS). Carried Erlangs is 34.90 Erlangs. Total channels/carrier = 48 Total traffic channels (voice) = 45 Control/signaling channels = 3

BSS planning
The major steps for planning the BSC system include: The number of RSL links between the BSC and BTSs. The number of E1 links between BSC and BTSs. The number of LCFs for RSL processing. The number of MTL links between BSC and MSC. The number of LCFs for MTL processing. The number of XBL links between BSC and RXCDR. The number of GSL links between BSC and RXCDR. The number of GPROCs. The number of XCDR/GDP/GDP2s. The number of MSI cards. The number of KSWs/DSW2s. The number of BSU shelves. The number of KSWXs/DSWXs. The number of GCLKs. The number of CLKXs. The number of LANXs. The number of PIXs. The number of line interface cards (T43s). The number of digital power supplies. Whether or not an optional NVM board is fitted.

68P02900W21-S 9-38 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

RSL requirements

The number of 64 kbit/s RSLs required is given by:

RSL GSM + GPRS @ 64K = n * (95 + 67 * S + 35 * H + 25 * L ) ( 47 + 3 * C BTS ) * PGSM + (52 + C BTS ) * PGPRS + + 1000 * U * T 8000 * U 6 * Mean _ TBF _ Rate * N GPRS 1000 * U

Where n is the number of TCHs under the BTS. Hence, for a 6/6/6 site (no GPRS):
RSL GSM + GPRS @ 64K = 45 * 3 * (95 + 67 * 0.12 + 35 * 2.5 + 25 * 2.4) (47 + 3 * 3) * 10 + (52 + 3) * 8 6*0 + + = Roundup (1.351) 1000 * 0.25 * 120 8000 * 0.25 1000 * 0.25

The number of RSLs required per 6/6/6 site is 2.

BSC to BTS E1 interconnect planning

Number of E1 links required between a BSC and BTS is given by: {23769}
nE GPRS RTF _ DSO _ Count + (nCGPRS * 4) + (nG GPRS * 2) + L16 / 4 + L64 i = 0 N BSC- BTS = 31

Number of E1 links required between each 6/6/6 BTS and BSC is given by:

((0 * 8) + (0 * 4) + (18 * 2) + (0/4)) + 2 ~ 1.22 31

Hence, 2 E1 interconnections are required between each BTS and BSC for the given site configurations (provided they are in star configurations). There are total of 20 * 2 = 40 E1 links needed. The number of E1s between the BSC and BTS is 40.
Determining the number of LCF GPROCs for RSL processing

Number of LCF-RSLs required is given by:

C n * (1 + 0.35 * S + 0.34 * H * (1 0.4 * i) + 0.32 * L) G L3 = + (0.00075* PGSM + 0.004) * B + 19 . 6 * T 120

Where, n is the number of TCHs under a BSC:

60 2700* (1 + 0.35* 0.12 + 0.34* 2.6 * (1 0.4 * 0.6) + 0.32* 2.5) + (0.00075* 8 + 0.004) * 20 + 19.6 *120 120
Determining the number of MTLs

Total Erlangs offered by the BSC with 20 sites and 6/6/6 configuration is given by: 20 * 3 * 35.61 = 2136.6 Erlangs Total Erlangs carried by the BSC with 20 sites and 6/6/6 configuration is given by: 20 * 3 * 34.40 = 2094 Erlangs

68P02900W21-S 01 Feb 2007 9-39

Calculations using alternative call models

Chapter 9: Planning exercises

The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 2165 (using offered Erlangs to calculate). Verify that this figure is within limits (< 3200 for a big BSC system). Number of pages per call: PPC = PGSM * T/N = (8 * 120)/2165 = 0.443 Using the call model parameters, the number of MTLs can be calculated using formulae mentioned in Chapter 6 of this manual. Maximum number of Erlangs supported by a C7 link is given by:

n Link = n Link =

(1000 * U * T) (40 + 47 * S + 22 * H * (1 0.8 * i) + 24 * L + 9 * PPC ) (1000 * 0.35 *120) = 310Erlangs (40 + 47 * 0.12 + 22 * 2.5 * (1 0.8 * 0.6) + 24 * 2.4 + 9 * 0.44)
(20 * T) (1 + 0.16 * S + 0.5 * H * (1 0.6 * i) + 0.42 * L + PPC * (0.005 * B + 0.05))
(20 *120) (1 + 0.16 * 0.12 + 0.5 * 2.5 * (1 0.6 * 0.6) + 0.42 * 2.4 + 0.44 * (0.005 * 20 + 0.05))

Maximum number of Erlangs supported by GPROC supporting a C7 signaling link is given by:

nl LCF MTL =
nlLCF MTL =

=1410.2 Erlangs Hence:

n Link nlmin = min n = 310Erlangs LCF MTL

Amount of traffic each logical link holds:

nllog ical =

2165 = 135.31Erlangs 16

using a MTL load-sharing granularity of 16. The number of logical links each MTL can handle:

nllog_ per _ mtl = Round down (310 / 135.31) ~ 2

The number of required MTLs: Check this figure is within limits (<16). The number of MTLs required = 9
Determining the number of LCFs for MTL processing

Using the formula mentioned in Chapter 6, since:

2 * n link < nlLCF MTL

9 N LCF = Roundup ~ 5 2

68P02900W21-S 9-40 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

XBL requirements

Referring to Table 6-11 in Chapter 6, BSC planning steps and rules, Number of XBLs required = 2 (using N = 2165)
GSL requirements

N/A (signaling links between BSC and PCU).

GPROC requirements

To determine the number of GPROCs: NGPROC = 2B + L + C + R B = Number of BSP GPROC3s (x 2 for redundancy) = 3

A total of 3 BSU shelves are required and each shelf must have at least one GPROC (x2 for redundancy). L = Total number of LCF GPROCs required = 5 C = Number of CSFP GPROCs (optional) = 0 R = Number of pool GPROCs (for redundancy) = 1 Total number of GPROCs for BSC = (2 * 3 + 5 +0 + 1) = 12
XCDR/GDP/GDP2 requirements

N/A (no local RXCDR).

MSI requirements

Each MSI interfaces two E1 links.

N MSI =

N BSC RXCDR 2

NMSI = Number of MSIs required. NBSC-RXCDR = Number of E1 links required. Number of E1 links required at the BSC for interconnecting with the RXCDR is:

N BSC-RXCDR =
=

C + X + B64 + T * (1 PHR ) + N16 / 4 + (T * PHR ) / 8 31

9 + 2 + 2 + ( 2165 / 4 ) = 17 . 9 ~ 18 31

PHR in the equation is not considered in non-AMR cases. Hence the number of MSIs required for the BSC to RXCDR interface is 18/2 = 9. Each BTS site in this example needs two E1 interconnections. Hence, the number of MSIs required for BTSs is 20 * 2 / 2 = 20. Total number of MSIs required at the BSC = 20 + 9 = 29

68P02900W21-S 01 Feb 2007 9-41

Calculations using alternative call models

Chapter 9: Planning exercises

KSW/DSW2 requirements

Determine the number of KSWs/DSW2s (N) required by using the following formula:

N=

(G * n ) + R GDPXCDR * 16) + R EGDP * 80 + ( R GDP 2 * 24) + ( M * 64) 1016

Where Is

G n RGDP2 M

the number of GPROCs. 16 or 32 (16 in this example). N/A in this example (RXCDR case). the number of MSIs (29).

RGDPXCDR and REGDP are not considered in the equation. Therefore, the total number of timeslots required is: 12 * 16 + 29 * 64 = 2048 Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 3 non-redundant KSWs/ DSW2s are required for this configuration. For redundancy, 3 additional KSWs/ DSW2s are required. Thus total KSWs/DSW2s required (with redundancy) = 3 + 3 = 6
BSU shelves

Each BSU shelf can support up to 12 MSI cards. A total of 29 MSI cards are required based on the previous calculation. The total number of BSU shelves required is: Roundup(29/12) = 3 BSU shelves Total GPROCs = 12 and total MSIs = 29, split between 3 BSU shelves.
Table 9-10 BSU Shelves BSU 1 BSU 2 BSU 3 Check Limit

GPROCs MSI cards

4 12

4 9

4 8

<=8 < = 12

Ensure that the following is true for each shelf. (G * n) + (M * 64) + (R * 16) 1016 That is, (4 * 16) + (12 * 64) + (0 * 16) 1016 Therefore, the number of BSU shelves required to accommodate all the hardware needed for this configuration is NBSU = 3.

68P02900W21-S 9-42 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

KSWX/DSWX requirements

KSWXs/DSWXs should be considered for this example as the configuration needs more than one shelf. The KSWX/DSWX extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in the multi-shelf configuration. The KSWX/DSWX can be used in expansion, remote and local modes. We need 3 BSU shelves with 3 master/redundant KSWs/DSW2s, which implies that 2 expansion shelves are required. The number of KSWXs/DSWXs required (NKX) is the sum of KSWXDSWXE, KSWX/DSWXR, and KSWX/DSWXL: NKX = NKXE + NKXR + NKXL NKXE = K*(K-1) = 3 *2 = 6 (K is the number of non-redundant KSWs) NKXR = SE = 0 (SE is the number of extension shelves) NKXL = K + SE = 3 NK X = 6 + 0 + 3 = 9 The number of KSWXs/DSWXs required (with redundancy) = 18

The maximum number of KSWX/DXWX slots per shelf 18. KSWXs and DSWXs can be used together in a shelf, provided that they are used with like pairs, KSWX is connected to KSWX and DSWX connected to DSWX.

GCLK requirements

The generic clock generates all the timing reference signals required by a BSU. One GLCK is required at each BSC. The number of GCLKs required (with redundancy) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one BSU. Number of CLKXs required is given by: NCLKX = Roundup(E/6) * (1+RF) Where E is the number of expansion/extension shelves and RF is the redundancy factor. NCLKX = Roundup(3/6) * (1+3) = 2 The number of CLKXs required (with redundancy) = 2
LANX requirements

NLANX = NBSU * (1+RF) Where RF is the redundancy factor. NLANX = 3*2 = 6 Total number of LANXs required (with redundancy) = 6
PIX requirements

PIX provides eight inputs and four outputs for site alarms. PIX Number of BSUs = 6

68P02900W21-S 01 Feb 2007 9-43

Calculations using alternative call models

Chapter 9: Planning exercises

Line interfaces

Number of T43s = Roundup(Number of MSIs/3) Number of T43s = 29/3 ~10 The number of T43 boards required is 10.
Digital power supply requirements

PSUs = NBSU * (2 + RF) One redundant PSU is required for each BSU shelf, hence the total number of PSUs required is: PSUs = 3 * (2 + 1) = 9 The total number of PSUs required is 9.
Non-volatile memory (NVM) board for BSC (optional)

NVM = 0 or 1 An NVM board is required in this example, so NVM = 1.

RXCDR planning
The following planning steps are performed for this example: The number of links between the RXCDR and BSC. The number of E1 links between the RXCDR and MSC. The number of XCDR/GDP2/GDP2s. The number of GPROCs. The number of MSIs. The number of KSWs/DSW2s. The number of RXU shelves. The number of KSWXs/DSWXs. The number of GCLKs. The number of CLKXs. The number of LANXs. The number of PIXs. The number of line interface boards (T43s). The number of digital power supply units. Whether or not an optional NVM board is fitted.

Determining the number of E1 links between the RXCDR and BSC

See MSI requirements in the previous section (9 MTLs x 2).

68P02900W21-S 9-44 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Determining the number of E1 links between the RXCDR and MSC

Number of RXCDR to MSC links is given by:

N RXCDR MSC = (C + X + T)/31

Where Is

C X T

the number of MTL links required (9). the number of OML links required (2). the number of trunks between MSC and BSC (2165).

N RXCDR _ MSC =

9 + 2 + 2165 = 70.19 31

The number of E1 links between the RXCDR and MSC = 71

Determining the number of XCDR/GDP/GDP2 cards

Each XCDR/GDP/GDP2 terminates one E1 link (for the RXU shelf). Hence, the number of non-redundant cards required is 47, which, can be a mix of XCDRs, GDPs and GDP2s. The number of non-redundant XCDR/GDP/GDP2 cards = 47
PROC requirements for RXCDR

Each shelf should have minimum of one GPROC. Hence, 5 non-redundant GPROCs are required. If the operator chooses to use redundancy, 10 GPROCs are required. The number of GPROCs required for RXCDR = 5 + 5 (for redundancy) = 10
MSI requirements for RXCDR

As calculated in MSI requirements, the number of BSC-RXCDR links is 18. Each MSI card interfaces 2 E1 links, hence, 9 MSI cards are required on the RXCDR. MSI requirements for RXCDR = 9
KSW/DSW2 requirements for RXCDR

Number of TDM slots required for the GPROCs, MSIs and XCDRs is given by: TDM timeslots required = G * n + M * 64 + R * 16 TDM timeslots required = 12 * 32 + 9 * 64 + 71 * 16 = 2096 Each KSW/DSW2 provides 1016 timeslots on the TDM highway, hence, 3 non-redundant KSWs/DSW2s are required for RXCDR with this configuration. KSWs/DSW2s required for the RXCDR = 3 + 3 (redundant) = 6
RXU shelves

The number of RXU shelves required is given by (assuming that an NVM board is fitted): NRXU = max(M/5,(R + NNVM)/16) = max(9/5, (71 + 1)/16) ~ 5

68P02900W21-S 01 Feb 2007 9-45

Calculations using alternative call models

Chapter 9: Planning exercises

Table 9-11 RXU shelves RXU 1 RXU 2 RXU 3 RXU 4 RXU 5

MSIS XCDRs/GDPs GDP2s GPROCs

1 7 7 2

2 7 7 2

2 7 7 2

2 7 7 2

2 7 8 2

Ensure that the following holds good for each shelf. N + (G * n) + (M * 64) + (R * 16) 1016 Hence, 5 RXU shelves are required to equip 71 XCDR/GDP/GDP2 cards and 9 MSI cards. The number of RXU shelves required = 5
KSWX/DSWX requirements for RXCDR

The number of KSWXs/DSWXs required is the sum of KSWX/DSWXE, KSWX/DSWXR, and KSWX/DSWXL. The calculations imply 2 expansion and 2 extension shelves are required. NKX = NKXE + NKXR + NKXL NKXE = K * (K 1) = 3 * (3 1) = 6 K is the number of non-redundant KSWs/DSW2s. NKXR = SE = 2 SE is the number of extension shelves. NKXL = K + SE = 3 + 2 = 5 NKX = 6 + 2 + 5 = 13 The number of KSWXs/DWSXs required = 13 + 13 (redundant) = 26

KSWXs and DSWXs are used together in a shelf, provided that they are used with like pairs, that is, KSWX connected to KSWX and DSWX connected to DSWX.
GCLK requirements

The generic clock generates all the timing reference signals required by an RXU. One GLCK is required at each RXCDR. Number of GCLKs required = 1 + 1 (redundant) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one RXU: NCLKX = Roundup(E/6) * (1 + RF)
Where Is

E RF

the number of expansion/extension shelves. the redundancy factor.

68P02900W21-S 9-46 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

NCLKX = Roundup(4/6) * (1 + 1) = 2 The number of CLKXs required = 1 + 1 (redundant) = 2

LANX requirements

Number of LANXs required is given by: NNANX = NRXU * (1 + RF) = 5 * 2 = 10 Where RF is the redundancy factor. Total number of LANXs required with redundancy = 10
PIX requirements

PIX provides eight inputs and four outputs for site alarms. PIX 2 * Number of RXUs = 2 * 5 = 10 Hence, 10 PIX cards are required for the RXCDR.
Line interfaces

Number of T43s = Number of E1s/6 = (18 +71)/6 ~ 15 The number of T43 boards required = 15
Digital power supply requirements

PSUs = 2 * RXUs + RF * RXUs = 2 * 5 + 1 * 5 = 15 One redundant PSU is required for each RXU shelf, hence, the total number of PSUs required = 15.
Non-volatile memory (NVM) board for RXCDR (optional)

NVM = 1 (required in this example)

Planning example 4 (using AMR)

Dimension a network with following requirements:
GSM software release = GSR 8 Number of sites 6/6/6 sites (BTS: M-Cell6) = 20 AMR MS penetration rate = 35% (AMR fr/hr-capable MSs) Total AMR hr usage PHR = 50% * PAMR = 18% (among all MSs) BSS provides additional ~35% voice traffic supported AMR hr GPROC3 is mandatory for the BSP GDP2 is considered to support AMR hr New RXCDR shelf is mandatory No local XCDR 8K/16K switching is used, (needs DSW2 support) No enhanced capacity mode support No GPRS in the system

68P02900W21-S 01 Feb 2007 9-47

Calculations using alternative call models

Chapter 9: Planning exercises

Call model parameters

Call duration T = 120 s Ratio of SMSs per call S = 0.12 Ratio of location updates per call = 2.4 Ratio of IMSI detaches per call I = 0 Location update factor L = 2.4 + 0.5 * 0 = 2.4 Number of handovers per call H = 2.5 Ratio of intra-BSC handovers to all handovers i = 0.6 Paging rate per second PGSM = 8 pages per second Number of cells at the BTS CBTS = 3 MTL link utilization = 35% (0.35) RSL link utilization U = 25% (0.25) CCCH utilization UCCCH = 33% (0.33) Probability of blocking TCH PB-TCH < 2% Probability of blocking SDCCH PB-SDCCH < 1% Probability of blocking on A-interface < 1%

Other considerations
Line interface type = E1 Network termination option = T43 Power voltage option = -48/-60 V dc Type of combining used = Hybrid (CBF) Dedicated CSFP = YES CSFP redundancy = NO Redundancy for all other modules = YES MTL links redundancy = YES RSL link redundancy = NO Coding schemes CS3 and CS4 used = NO BTS connectivity = Star configuration IMSI/TMSI paging = TMSI MTL load balancing granularity = 16 NVM board fitted at BSC and RXCDR

GSR 8 limitations (assuming big BSC system)

Maximum BTS sites = 100 Maximum BTS cells = 250 Active RF carriers = 512

68P02900W21-S 9-48 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Trunks = 3200 C7 links = 16

Table 9-12 Cell planning - control channel calculations (based on Erlang B models) All full rate Total Carriers AMR HR/ Carriers Total TCH Signaling / Control TCH Total Voice TCH Total TCH AMR (hr) Carrier Signaling /Control TCH Total Voice TCH AMR HR TCH AMR HR TCH %

6 6 6 6 6 6

1/6 2/6 3/6 4/6 5/6 6/6

48 48 48 48 48 48

3 3 3 3 3 3

45 45 45 45 45 45

56 64 72 80 -88 96

3 4 4 4 -4 4

53 60 68 76 -84 88

16 32 48 64 - 80 88

30.2 53.3 70.6 84.2 95.2 100

For planning purposes, it is assumed that the AMR-capable MSs use AMR FR channels, and hr is used under conditions of congestion. The estimated AMR penetration rate is 35%, of which half of those calls could be in half rate mode due to congestion (as given in the assumptions), yielding about 18% of the calls in half rate mode. From the pre-calculated table , it is seen that, 1 half rate enabled carrier would provide about 30% AMR half rate channels. However, to allow for future growth in the penetration level and to allow for a greater margin of safety, 2 half rate enabled carriers are assumed for the remainder of this exercise.
6-carrier cell - determining the number of CCCHs

Call arrival rate:

CB = e

= 53.43/120 = 0.445

SMS rate:

S = S * e

= 0.12 * 53.43/120 = 0.053

Location update rate:

LU = L * e

= 2.4 * 53.43/120 = 1.069

Access grant rate is given by:

AGCH = CB + S + LU = 0.445 + 0.053 + 1.069 = 1.567

From the call model parameters, the paging rate P is 8, so the average number of CCCH blocks required to support paging only is:

N PCH =

PGSM

(4 * 4.25)

= 8

(4 * 4.25)

= 0.471

68P02900W21-S 01 Feb 2007 9-49

Calculations using alternative call models

Chapter 9: Planning exercises

The average number of CCCH blocks required to support AGCH only is given by

N AGCH = AGCH /(2 * 4.25) = 1.567/8.5 = 0.1.184

Using a CCCH utilization figure (UCCCH) of 0.33, the average number of CCCH blocks required to support both PCH and AGCH is given by:

N PAGCH = (N AGCH + N PCH )/U CCCH = (0.184 + 0.471)/0.33 = 1.985

Assuming 1% blocking, the Erlang B tables show that 7 CCCHs are required. This can be supported using a non-combined BCCH with 9 CCCH timeslots. It is recommended to reserve 2 CCCH blocks for access grant messages.
Determining the number of SDCCHs per cell

Using the values calculated in the previous section and other call model parameters, the average number of SDCCHs and NSDCCH is given by the formula:

N SDCCH = 2 CB * TC + LU * (TL + Tg ) + * (TS + Tg) = 11.31

The number of SDCCHs to support an average number of busy SDCCHs of 11.31 Erlangs signaling traffic with less that 1% blocking as determined by use of Erlang B tables is 18. Hence, the number of timeslots required to carry SDCCH signaling traffic is 3 with each timeslot offering maximum 8 SDCCHs.
Determining the number of TCHs

Total number of signaling timeslots required for a 6-carrier configuration with the given call model parameters is four (1 non-combined BCCH timeslot with 9 CCCHs and 3 timeslots with 8 SDCCHs each). Therefore, the number of traffic channels per 6 carrier cell (4 fr carriers + 2 hr carriers) = 4 * 8 + 16 * 2 - 4 = 60 Hence, traffic offered by a 6-carrier cell is 49.64 Erlangs (60 traffic channels at 2% GOS). Carried Erlangs is 49.64 * 98% = 48.65 Erlangs Total Erlangs offered by the BSC with 20 sites and 6/6/6 configuration is given by: 20*3*49.64=2978.4 Erlangs Total Erlangs carried by the BSC with 20 sites and 6/6/6 configuration is given by: 20*3*48.65=2919 Erlangs The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 3003. Check this is within the limit of <=3200. If the number of trunks (3003) exceeds the limit, by a small number (less than a quarter of a percent or so) it can be considered negligible and planning could continue. However, there is an alternative approach, particularly for the half rate usage, which is discussed here. In fact, we can assume that the trunk limit was 3000 in order to provide a working example. The carried Erlangs were calculated for worst case planning. It was assumed that all AMR half rate enabled carriers would, at the worst case, be handling all AMR half rate calls. However, given that the AMR-capable mobile penetration is 35%, it is unlikely that all the AMR half rate enabled carriers are carrying all half-rate traffic. Certainly, exclusive (forced) AMR half rate usage could have been assumed (in which case the AMR hr TCH % should be used to calculate the number of (total and AMR half rate enabled) carriers required) but that is not the assumption made here. The approach used here is to relax the AMR half rate usage assumption, enough to satisfy the trunking limit, yet provide a large margin of safety as AMR penetration grows. A minimal assumption is made, that one of the AMR HR carriers can carry 14 HR calls and 1 FR call. This yields the following:

68P02900W21-S 9-50 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

1 HR carrier = 16 AMR HR TCH = 14 AMR HR TCH + 1 FR TCH = 15 TCH The total # of AMR voice TCH = 4 * 8 + 1 * 16 + 14 TCH + 1 - 4 = 59 The traffic offered by a 6 carrier/cell is (based on 59 TCH with 2% of GOS) = 48.70 Erlangs Carried Erlangs by such system configuration (per BTS) = 48.70 *98% = 47.73 Erlangs Total Erlangs carried by the BSC with 20 sites and 6/6/6 configuration is given : 20 * 3 * 48.70 = 2922 Erlangs The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 2946. This alternatively calculated number (2946) can be used for the remainder of the calculations in this section. # of sites (BTS) per BSC: # of cells per BTS: # of carriers per cell: # TCHs per carrier: # Control channels per carrier: # of available voice TCH: # of Erlangs offered per BTS: # of Erlangs carried per BTS: # of Erlangs offered by this BCS system: # of trunks to carry such traffic: 20 3 6 63 (AMR HR, AMR FR, GSM FR/EFR, and so on) 4 59 (30 AMR HR + 29 FR) 48.70 47.73 20 * 3 * 48.70 = 2922 (using Erlangs B calculation) 2946

BSS planning
The major steps for planning the BSC system include the following:
68P02900W21-S 01 Feb 2007 9-51

The number of RSL links between the BSC and BTSs. The number of E1 links between BSC and BTSs. The number of LCFs for RSL processing. The number of MTL links between BSC and MSC. The number of LCFs for MTL processing. The number of XBL links between BSC and RXCDR. The number of GSL links between BSC and RXCDR. The number of GPROC3s. The number of XCDR/GDP/GDP2s. The number of MSI cards. The number of DSW2s. The number of BSU shelves. The number of KSWXs/DSWXs.

Calculations using alternative call models

Chapter 9: Planning exercises

The number of GCLKs. The number of CLKXs. The number of LANXs. The number of PIXs. The number of line interface cards (T43s). The number of digital power supplies. Whether or not an optional NVM board is fitted.

RSL requirements

The number of 64 kbit/s RSLs required is given by:

RSL GSM + GPRSG64k =

n(95 + 67 + S + 35 * H + 25 * L) + 1000 * U * T (47 + 3 * C BTS ) * PGSM + (52 + C BTS ) * PGPRS) 6 * Mean_TBF_Rate * N GPRS + 8000 * U 1000 * U

Where n is the number of TCHs under the BTS. Hence, for a 6/6/6 site (with AMR but no GP)

RSL GSM + GPRSG64k =

59 * 3 * (95 + 67 + 0.12 + 35 * 2.5 + 25 * 2.4) (47 + 3 * 3) * 8 + (52 + 3) * 8) + + 1000 * 0.25 * 120 8000 * 0.25

0 = Roundup(1. 70) 1000 * 0.25

The number of RSLs required per 6/6/6 site (with 2 carriers of AMR HR) = 2
BSC to BTS E1 interconnect planning

Number of E1 links required between a BSC and BTS is given by: {23769}

N BSCBTS

nEGPRS RTF_DS0_COUNT + (nC GPRS * 4) + (nG GPRS * 2) + L16/4 + L64 = n =0 31

Number of E1 links required between each 6/6/6 BTS and BSC:

((0 * 8) + (6 * 4) + (12 * 2) + (0/4) + 2)) ~ 1.61 31

Hence, 2 E1 interconnections are required between each BTS and BSC for the given site configurations (provided they are in star configurations). There are total of 20 * 2 = 40 E1 links needed. The number of E1 link between the BSC and BTS is 40

68P02900W21-S 9-52 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Determining the number of LCF GPROCs for RSL processing

Number of LCF-RSLs required, assuming only GPROC3s are used, is given by:

G L3GPROC3 = [ n * (1 + 0.35 * S + 0.34 * H * (1 0.4 * i) + 0.32 * L) + 0.00075 * PGSM + 0.004 * B + (C/120)] (19.6 * T)

Where n is the number of TCHs under a BSC.

2700*(1+ 0.35*0.12+ 0.34* 2.6*(1 0.4*0.6)+ 0.32* 2.5 60 ] + (0.00075 *8 + 0.004* 20+ ) (19.6*120) 120

Determining the number of MTLs

Total Erlangs offered by the BSC with 20 sites, and 6/6/6 configuration is given by:

= 20 * 3 * 35.61 = 2136.6Erlangs
Total Erlangs carried by the BSC with 20 sites, and 6/6/6 configuration is given by:

= 20 * 3 * 34.40 = 2094Erlang s
The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 2165 (using offered Erlangs to calculate). Verify that this figure is within limits (< 3200 for a big BSC system). Number of pages per call is given by:

PPC = PGSM * T/N = (8 * 120)/2165 = 0.443

Using the call model parameters, the number of MTLs can be calculated using formulae mentioned in Chapter 6 of this manual. Maximum number of Erlangs supported by a C7 link is given by:

D LNK = D LNK =

(1000 * U * T) (40 + 47 * S + 22 * H * (1 0.8 * i) + 24 * L + 9 * PPC ) (1000 * 0.35 *120 = 310Erlangs (40 + 47 * 0.12 + 22 * 2.5 * (1 0.8 * 0.6) + 24 * 2.4 + 9 * 0.44) (20 * T) (1 + 0.16 * S + 0.5 * H * (1 0.6 * i) + 0.42 * L + PPC * (0.005 * B + 0.05))

Maximum number of Erlangs supported by GPROC supporting a C7 signaling link is given by:

n1LCF MTL = n1LCFMTL = n1min

(20*120) (1 + 0.16* 0.12 + 0.5* 2.5* (1 0.6 * 0.6) + 0.42* 2.4 + 0.44* (0.005* 20 + 0.05)) = min(n1LNK , n1LCF MTL ) = 310Erlangs

Amount of traffic each logical link holds is given by:

N logical = 2165/16 = 135.31Erlangs

using a MTL load-sharing granularity of 16.

68P02900W21-S 01 Feb 2007 9-53

Calculations using alternative call models

Chapter 9: Planning exercises

The number of logical links each MTL can handle is given by:

n log_per_mtl = round_down(310/135.31) ~ 2
The number of required MTLs: Check this figure is within limits (<16). The number of MTLs required = 9
Determining the number of LCFs for MTL processing

Using the formula mentioned in Chapter 6, since:

2 * n LNK < n1LCF MTL 9 N LCF = ROUNDUP( ) ~ 5 2

XBL requirements

Referring to Table 6-11 in Chapter 6, BSC planning steps and rules. Number of XBLs required = 2 (using N = 2165)
GSL requirements

N/A (signaling links between BSC and PCU).

GPROC requirements

To determine the number of GPROCs:

N GPROC = 2B + L + C + R
B = Number of BSP GPROC3s (x 2 for redundancy) = 3 A total of 3 BSU shelves are required and each shelf must have at least one GPROC (x 2 for redundancy).
Where Is

L C R

total number of LCF GPROCs required = 5. number of CSFP GPROCs (optional) = 0. number of pool GPROCs (for redundancy) = 1.

Total number of GPROCs for BSC = (2 * 3 + 5 +0 + 1) = 12

XCDR/GDP/GDP2 requirements

N/A (no local RXCDR).

MSI requirements

Each MSI interfaces two E1 links.

N MSI =

N BSC RXCDR 2

68P02900W21-S 9-54 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

NMSI = Number of MSIs required. NBSC-RXCDR = Number of E1 links required. Number of E1 links required at the BSC for interconnecting with the RXCDR is:

N BSC RXCDR =

C + X + B64 + T * (1 PHR ) + N16/4 + (T * PHR )/8 31

(9 + 2 + 2 + 2165/4)) = 17.9 ~ 18 31

PHR in the equation is not considered in non-AMR cases. Hence the number of MSIs required for the BSC to RXCDR interface is 18/2 = 9. Each BTS site in this example needs two E1 interconnections. Hence, the number of MSIs required for BTSs is 20 * 2 / 2 = 20. Total number of MSIs required at the BSC = 20 + 9 = 29
KSW/DSW2 requirements

Determine the number of KSWs/DSW2s (N) required:

N=

(G * n) + (R GDPXCDR * 16) + (R EGDP * 80) + (R GDP2 * 24) + (M * 64) 1016

Is

Where

G n RGDP2 M

the number of GPROCs. 16 or 32 (16 in this example). N/A in this example (RXCDR case). the number of MSIs (29).

RGDPXCDR and REGDP are not considered in the equation. Therefore, the total number of timeslots required is:

12 * 16 + 29 * 64 = 2048
Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 3 non-redundant KSWs/ DSW2s are required for this configuration. For redundancy, 3 additional KSWs/ DSW2s are required. Thus total KSWs/DSW2s required (with redundancy) = 3 + 3 = 6.

68P02900W21-S 01 Feb 2007 9-55

Calculations using alternative call models

Chapter 9: Planning exercises

BSU shelves

Each BSU shelf can support up to 12 MSI cards. A total of 29 MSI cards are required based on the previous calculation. The total number of BSU shelves required is given by:

RoundUp(

29 ) = 3BSU shelves 12

Total GPROCs = 12 and total MSIs = 29, split between 3 BSU shelves: Table 9-13 GPROCs and MSI cards BSU 1 BSU 2 BSU 3 Check Limit

GPROCs MSI cards

4 12

4 9

4 8

<=8 < = 12

Ensure that the following is true for each shelf:

(G * n) + (M * 64) + (R *16) 1016

That is,

(4 *16) + (12 * 64) + (0 *16) 1016

Therefore, the number of BSU shelves required to accommodate all the hardware needed for this configuration is NBSU = 3.
KSWX/DSWX requirements

KSWXs/DSWXs should be considered for this example as the configuration needs more than one shelf. The KSWX/DSWX extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in the multi-shelf configuration. The KSWX/DSWX is used in expansion, remote and local modes. We need 3 BSU shelves with 3 master/redundant KSWs/DSW2s, which implies that 2 expansion shelves are required. The number of KSWXs/DSWXs required (NKX) is the sum of KSWXDSWXE, KSWX/DSWXR, and KSWX/DSWXL.

N KX = N KXE + N KXR + N KXL

NKXE = K*(K-1) = 3 *2 = 6 (K is the number of non-redundant KSWs) NKXR = SE = 0 (SE is the number of extension shelves) NKXL = K + SE = 3 NK X = 6 + 0 + 3 = 9 The number of KSWXs/DSWXs required (with redundancy) = 18

The maximum number of KSWX/DXWX slots per shelf <=18. KSWXs and DSWXs is used together in a shelf, provided that they are used with like pairs, that is KSWX connected to KSWX and DSWX connected to DSWX.

68P02900W21-S 9-56 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

GCLK requirements

The generic clock generates all the timing reference signals required by a BSU. One GLCK is required at each BSC. The number of GCLKs required (with redundancy) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one BSU. Number of CLKXs required is given by:

N CLKX = Roundup(E/6) * (1 + R F )
Where Is

E RF

the number of expansion/extension shelves the redundancy factor.

N CLKX = Roundup(3/6) * (1 + 1) = 2
The number of CLKXs required (with redundancy) = 2
LANX requirements

N LANX = NBSU * (1 + R F )
Where RF is the redundancy factor.

N LANK = 3 * 2 = 6
Total number of LANXs required (with redundancy) = 6
PIX requirements

PIX provides eight inputs and four outputs for site alarms. PIX Number of BSUs = 6
Line interfaces

Number of T43s = Roundup (Number of MSIs/3) Number of T43s= 29/3 ~ 10 The number of T43 boards required is 10.
Digital power supply requirements

The number of PSUs required is given by: One redundant PSU is required for each BSU shelf, hence the total number of PSUs required is: PSUs = 3*(2+1)=9 The total number of PSUs required is 9.
Non-volatile memory (NVM) board for BSC (optional)

NVM = 0 or 1 An NVM board is required in this example, so NVM = 1.

68P02900W21-S 01 Feb 2007 9-57

Calculations using alternative call models

Chapter 9: Planning exercises

RXCDR planning

The following planning steps are performed for this example: The number of links between the RXCDR and BSC. The number of E1 links between the RXCDR and MSC. The number of XCDR/GDP2/GDP2s. The number of GPROCs. The number of MSIs. The number of KSWs/DSW2s. The number of RXU shelves. The number of KSWXs/DSWXs. The number of GCLKs. The number of CLKXs. The number of LANXs. The number of PIXs. The number of line interface boards (T43s). The number of digital power supply units. Whether or not an optional NVM board is fitted.

Determining the number of E1 links between the RXCDR and BSC

N BSC RXCDR =

C + X + B64 + [T * (1 PHR ) + B16]/4 + (T * PHR ) 31

= 18

See MSI requirements in the previous section (9 MTLs x 2).

Determining the number of E1 links between the RXCDR and MSC

Number of RXCDR to MSC links is given by:

N RXCDR MSC = (C + X + T)/31

Where Is

C X T

the number of MTL links required (9). the number of OML links required (2). the number of trunks between MSC and BSC (2165).

N RXCDR MSC =

(9 + 2 + 2165) = 70.19 31

The number of E1 links between the RXCDR and MSC = 71

68P02900W21-S 9-58 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Determining the number of XCDR/GDP/GDP2 cards

Each XCDR/GDP/GDP2 terminates one E1 link (for the RXU shelf). Hence, the number of non-redundant cards required is 47, which can be a mix of XCDRs, GDPs and GDP2s. The number of non-redundant XCDR/GDP/GDP2 cards = 47
GPROC requirements for RXCDR

Each shelf should have minimum of one GPROC hence, 5 non-redundant GPROCs are required. If the operator chooses to use redundancy, 10 GPROCs are required.

N RXCDR MSC =

(9 + 2 + 2165) = 70.19 31

The number of GPROCs required for RXCDR = 5 + 5 (for redundancy) = 10.

MSI requirements for RXCDR

As calculated in MSI requirements, the number of BSC-RXCDR links is 18. Each MSI card interfaces 2 E1 links, hence, 9 MSI cards are required on the RXCDR. MSI requirements for RXCDR = 9
KSW/DSW2 requirements for RXCDR

Number of TDM slots required for the GPROCs, MSIs and XCDRs is given by: TDM timeslots required = G*n + M*64 + R*16 TDM timeslots required = 12*32 + 9*64 + 71*16 = 2096 Each KSW/DSW2 provides 1016 timeslots on the TDM highway, hence, 3 non-redundant KSWs/DSW2s are required for RXCDR with this configuration. KSWs/DSW2s required for the RXCDR = 3 + 3 (redundant) = 6
RXU shelves

The number of RXU shelves required is given by (assumes an NVM board is fitted):

N RXU = max(M/5, (R + N NVM )/16) = max(9/5, (71 + 1)/16 ~ 5

Table 9-14 RXU shelves RXU 1 RXU 2 RXU 3 RXU 4 RXU 5

MSIs XCDRs/GDPs GDP2s GPROCs

1 7 7 2

2 7 7 2

2 7 7 2

2 7 7 2

2 7 8 2

Ensure that the following is true for each shelf: N + (G*n) + (M*64) + (R*16) 1016 Hence, 5 RXU shelves are required to equip 71 XCDR/GDP/GDP2 cards and 9 MSI cards. The number of RXU shelves required = 5

68P02900W21-S 01 Feb 2007 9-59

Calculations using alternative call models

Chapter 9: Planning exercises

KSWX/DSWX requirements for RXCDR

The number of KSWXs/DSWXs required is the sum of KSWX/DSWXE, KSWX/DSWXR, and KSWX/DSWXL. The calculations implies that 2 expansion and 2 extension shelves are required.

N KX = N KXE + N KXR + N KXL

N KXE = K * (K 1) = 3 * (3 1) = 6
K is the number of non-redundant KSWs/DSW2s.

N KXR = S E = 2
SE is the number of extension shelves.

N KXL = K + S E = 3 + 2 = 5 N KX = 6 + 2 + 5 = 13
The number of KSWXs/DWSXs required = 13 + 13 (redundant) = 26

KSWXs and DSWXs can be used together in a shelf, provided that they are used with like pairs, that is. KSWX connected to KSWX and DSWX connected to DSWX.
GCLK requirements

The generic clock generates all the timing reference signals required by an RXU. One GLCK is required at each RXCDR. Number of GCLKs required = 1 + 1 (redundant) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one RXU.

N CLKX = Roundup(E/6) * (1 + R F )
Where Is

E RF

the number of expansion/extension shelves. the redundancy factor.

N CLKX = Roundup(4/6) * (1 + 1) = 2
The number of CLKXs required = 1 + 1 (redundant) = 2
LANX requirements

Number of LANXs required is given by: Where RF it the redundancy factor.

N LANX = N RXU * (1 + R F ) = 5 * 2 = 10
Total number of LANXs required with redundancy = 10

68P02900W21-S 9-60 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

PIX requirements

PIX provides eight inputs and four outputs for site alarms. PIX 2*Number of RXUs = 2*5 = 10 Hence, 10 PIX cards are required for the RXCDR.
Line interfaces

Number of T43s= Number of E1s/6=(18+71)/6~15 The number of T43 boards required = 15

Digital power supply requirements PSUs = 2*RXUs + RF * RXUs = 2*5 +1*5 =15

One redundant PSU is required for each RXU shelf, hence total number of PSUs required = 15.
Non-volatile memory (NVM) board for RXCDR (optional)

NVM = 1 ( required in this example)

Planning example 4 (using AMR)

Dimension a network with following requirements:
GSM software release = GSR 8 Number of sites 6/6/6 sites (BTS: M-Cell6) = 20 AMR MS penetration rate = 35% (AMR fr/hr-capable MSs) Total AMR hr usage PHR = 50% * PAMR = 18% (among all MSs) BSS provides additional ~35% voice traffic supported AMR hr GPROC3 is mandatory for the BSP GDP2 is considered to support AMR hr New RXCDR shelf is mandatory No local XCDR 8K/16K switching is used, (needs DSW2 support) No enhanced capacity mode support No GPRS in the system

Call model parameters

Call duration T = 120 s Ratio of SMSs per call S = 0.12 Ratio of location updates per call = 2.4 Ratio of IMSI detaches per call I = 0 Location update factor L = 2.4 + 0.5 * 0 = 2.4 Number of handovers per call H = 2.5

68P02900W21-S 01 Feb 2007 9-61

Calculations using alternative call models

Chapter 9: Planning exercises

Ratio of intra-BSC handovers to all handovers i = 0.6 Paging rate per second PGSM = 8 pages per second Number of cells at the BTS CBTS = 3 MTL link utilization = 35% (0.35) RSL link utilization U = 25% (0.25) CCCH utilization UCCCH = 33% (0.33) Probability of blocking TCH PB-TCH < 2% Probability of blocking SDCCH PB-SDCCH < 1% Probability of blocking on A-interface < 1%

Other considerations
Line interface type = E1 Network termination option = T43 Power voltage option = -48/-60 V dc Type of combining used = Hybrid (CBF) Dedicated CSFP = YES CSFP redundancy = NO Redundancy for all other modules = YES MTL links redundancy = YES RSL link redundancy = NO Coding schemes CS3 and CS4 used = NO BTS connectivity = Star configuration IMSI/TMSI paging = TMSI MTL load balancing granularity = 16 NVM board fitted at BSC and RXCDR

GSR 8 limitations (assuming big BSC system)

Maximum BTS sites = 100 Maximum BTS cells = 250 Active RF carriers = 512 Trunks = 3200 C7 links = 16

68P02900W21-S 9-62 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Cell planning - control channel calculations (based on Erlang B models)

Table 9-15 Control channel calculation All full rate Total Carriers AMR HR/ Carriers Total TCH Signaling / Control TCH Total Voice TCH Total TCH AMR (hr) Carrier Signaling /Control TCH Total Voice TCH AMR HR TCH AMR HR TCH %

6 6 6 6 6 6

1/6 2/6 3/6 4/6 5/6 6/6

48 48 48 48 48 48

3 3 3 3 3 3

45 45 45 45 45 45

56 64 72 80 -88 96

3 4 4 4 -4 4

53 60 68 76 -84 88

16 32 48 64 -80 88

30.2 53.3 70.6 84.2 95.2 100

For planning purposes, it is assumed that the AMR-capable MSs uses AMR FR channels, and that hr is used under conditions of congestion. The estimated AMR penetration rate is 35%, of which half of those calls are in half rate mode due to congestion (as given in the assumptions), yielding about 18% of the calls in half rate mode. From the pre-calculated table, it is seen that 1 half rate enabled carrier would provide about 30% AMR half rate channels. However, to allow for future growth in the penetration level and to allow for a greater margin of safety, 2 half rate enabled carriers can be assumed for the remainder of this exercise.
6-carrier cell - determining the number of CCCHs

Call arrival rate: ca =e/T=53.43/120=0.445 SMS rate: S = S*e/T=0.12*53.43/120=0.053 Location update rate: LU = L*e/T=2.4*53.43/120=1.069 Access grant rate is given by: AGCH = CA + S + LU = 0.445+0.053+1.069 = 1.567 From the call model parameters, the paging rate P is 8, so the average number of CCCH blocks required to support paging only is given : NPCH = PGSM /(4*4.25) = 8/(4*4.25) = 0.471 The average number of CCCH blocks required to support AGCH only is given by: N AGCH = AGCH /(2*4.25) = 1.567/8.5 = 01.184) Using a CCCH utilization figure (UCCCH) of 0.33, the average number of CCCH blocks required to support both PCH and AGCH is given by: NPAGCH= (NAGCH+NPCH)/UCCCH = (0.184+0.471)/0.33=1.985 Assuming 1% blocking, the Erlang B tables show that 7 CCCHs are required. This can be supported using a non-combined BCCH with 9 CCCH timeslots. It is recommended to reserve 2 CCCH blocks for access grant messages.

68P02900W21-S 01 Feb 2007 9-63

Calculations using alternative call models

Chapter 9: Planning exercises

Determining the number of SDCCHs per cell

Using the values calculated in the previous section and other call model parameters, the average number of SDCCHs and NSDCCH is given by the formula mentioned in Chapter 3. NSDCCH = 2CA * TC + LU * (TL + Tg) + S * (TS + Tg) = 11.31 To support an average number of busy SDCCHs of 11.31 Erlangs signaling traffic with less than 1% blocking is 18 as determined by use of Erlang B tables. Hence, the number of timeslots required to carry SDCCH signaling traffic is 3, with each timeslot offering a maximum of 8 SDCCHs.
Determining the number of TCHs

Total number of signaling timeslots required for a 6-carrier configuration, with the given call model parameters is 4 (1 non-combined BCCH timeslot with 9 CCCHs and 3 timeslots with 8 SDCCHs each). Therefore, the number of traffic channels per 6 carrier cell (4 fr carriers + 2 hr carriers) = 4 * 8 + 16 * 2 - 4 = 60 Hence, traffic offered by a 6-carrier cell is 49.64 Erlangs (60 traffic channels at 2% GOS). Carried Erlangs is 49.64 * 98% = 48.65 Erlangs. Total Erlangs offered by the BSC with 20 sites, and 6/6/6 configuration is given by: 20 * 3 * 49.64 = 2978.4 Erlangs Total Erlangs carried by the BSC with 20 sites, and 6/6/6 configuration is given by: 20* 3 * 48.65 = 2919 Erlangs The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 3003. Check this is within the limit of <=3200. If the number of trunks (3003) exceeds the limit by a small number, (less than a quarter of a percent or so) it can be considered negligible and planning can continue. However, there is an alternative approach, particularly for the half rate usage, which is discussed here. In fact, we can assume that the trunk limit was 3000 in order to provide a working example. The carried Erlangs were calculated for worst case planning. It is assumed that all AMR half rate enabled carriers would, at worst case, be handling all AMR half rate calls. However, given that the AMR-capable mobile penetration is 35%, it is unlikely that all the AMR half rate enabled carriers are carrying all halfrate traffic. Certainly, exclusive (forced) AMR half rate usage could have been assumed (in which case the AMR hr TCH % should be used to calculate the number of (total and AMR half rate enabled) carriers required) but that is not the assumption made here. The approach used here is to relax the AMR half rate usage assumption enough to satisfy the trunking limit, yet provide a large margin of safety as AMR penetration grows. A minimal assumption is made, that one of the AMR HR carriers can carry 14 HR calls and 1 FR call. This results the following: 1 HR carrier = 16 AMR HR TCH = 14 AMR HR TCH + 1 FR TCH = 15 TCH The total number of AMR voice TCH = 4 * 8 + 1 * 16 + 14 TCH + 1 - 4 = 59 The traffic offered by a 6 carrier/cell is (based on 59 TCH with 2% of GOS) = 48.70 Erlangs Carried Erlangs by such system configuration (per BTS) = 48.70 *98% = 47.73 Erlangs Total Erlangs carried by the BSC with 20 sites, and 6/6/6 configuration is given : 20 * 3 * 48.70 = 2922 Erlangs

68P02900W21-S 9-64 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 2946. This alternatively calculated number (2946) can be used for the remainder of the calculations in this section. # of sites (BTS) per BSC: # of cells per BTS: # of carriers per cell: # TCHs per carrier: # Control channels per carrier: # of available voice TCH: # of Erlangs offered per BTS: # of Erlangs carried per BTS: # of Erlangs offered by this BCS system: # of trunks to carry such traffic: 20 3 6 63 (AMR HR, AMR FR, GSM FR/EFR, and so on) 4 59 (30 AMR HR + 29 FR) 48.70 47.73 20 * 3 * 48.70 = 2922 (using Erlangs B calculation) 2946

BSS planning
The major steps for planning the BSC system include: The number of RSL links between the BSC and BTSs. The number of E1 links between BSC and BTSs. The number of LCFs for RSL processing. The number of MTL links between BSC and MSC. The number of LCFs for MTL processing. The number of XBL links between BSC and RXCDR. The number of GSL links between BSC and RXCDR. The number of GPROC3s. The number of XCDR/GDP/GDP2s. The number of MSI cards. The number of DSW2s. The number of BSU shelves. The number of KSWXs/DSWXs. The number of GCLKs. The number of CLKXs. The number of LANXs. The number of PIXs. The number of line interface cards (T43s). The number of digital power supplies. Whether or not an optional NVM board is fitted.

68P02900W21-S 01 Feb 2007 9-65

Calculations using alternative call models

Chapter 9: Planning exercises

RSL requirements

The number of 64 kbit/s RSLs required with the given by:

RSL GSM + GPRS@64k =

n * (95 + 67 * S + 35 * H + 25 * L) + 1000 * U * T (47 + 3 * C BTS ) * PGSM + (52 + C BTS ) * PGPRS 6 * Mean_TBF_rate * N GPRS + 8000 * U 1000 * U * T

Where n is the number of TCHs under the BTS. Hence, for a 6/6/6 site (with AMR but no GPRS):

RSL GSM +GPRS@64k =

59 * 3(95 + 67 * 0.12 + 35* 2.5 + 25* 2.4) (47 + 3 * 3) * 8 + (52 + 3) * 8 0 + + 1000* 0.25*120 8000* 0.25 1000* 0.25
= Roundup(1.70)
The number of RSLs required per 6/6/6 site (with 2 carriers of AMR HR) = 2
BSC to BTS E1 interconnect planning

Number of E1 links required between a BSC and BTS is given by: {23769}
nEGPRS n =0

{[( N BSC-BTS =

RTF_DS0_COUNT) + (nC

GPRS

* 4) + nG GPRS * 2) + L16/4]} + L64

31

Number of E1 links required between each 6/6/6 BTS and BSC: = [((0*8)+(6*4)+(12*2)+(0/4))/31] ~ 1.61 Hence, two E1 interconnections are required between each BTS and BSC for the given site configurations (provided they are in star configurations). Thus, a total of 20*2=40 E1 links are required. The number of E1s between the BSC and BTS is 40.
Determining the number of LCF GPROCs for RSL processing

Number of LCF-RSLs required, assuming only GPROC3s are used, is given by:

G L3-GPROC3 = [ n * (1 + 0.35 * S + 0.34 * H * (1 0.4 * i) + 0.32 * L) C + (0.00075 * PGSM + 0.004) * B + ] 19.6 * T 120

Where n is the number of TCHs under a BSC.

3540 * (1 + 0.35 * 0.12 + 0.34 * 2.6 * (1 0.4 * 0.6) + 0.32 * 2.4) + 19.6 * 120 60 (0.00075 * 8 + 0.004) * 20 + ] 120

Determining the number of MTLs

Total Erlangs carried by the BSC with 20 sites, and 6/6/6 configuration is given by: =20*3*48.70=2922 Erlangs

68P02900W21-S 9-66 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 2946. Number of pages per call is given by: PPC = PGSM * T/N = (8*120)/2946 = 0.325 Using the call model parameters, the number of MTLs can be calculated using formulae mentioned in Chapter 6 of this manual. Maximum number of Erlangs supported by a C7 link is given by:

D LINK = D LINK =

(1000 * U * T) (40 + 47 * S + 22 * H * (1 0.8 * i) + 24 * L + 9 * PPC ) (1000 * 0.35 *120) = 311.65Erlangs (40 + 47 * 0.12 + 22 * 2.5 * (1 0.8 * 0.6) + 24 * 2.4 + 9 * 0.325)

Maximum number of Erlangs supported by a GPROC3 supporting a C7 signaling link is given by: NLcf-mtl-gproc=

(20 * T *1.7) (1 + 0.16 * S + 0.5 * H * (1 0.6 * i) + 0.42 * L + PPC * (0.005 * B + 0.05)) (20 * 120 * 1.7) (1 + 0.16 * S + 0.5 * 2.5 * (1 0.6 * 0.6) + 0.42 * 2.4 + 0.325 * (0.005 * 20 + 0.05)) = 1393.1Erlangs =
Hence, for GPROC3 only: n1min=min(nLINK, n1LCF-MTL-GPROC3) = 312 Erlangs Amount of traffic each logical link can hold is given by: Nlogical= 2946/16= 184.1 Erlangs using a MTL load-sharing granularity of 16. The number of logical links each MTL can handle: Nlog_per_mtl = round down (312/184.1) ~ 2 The number of required MTLs: mtls = roundup (16/2)+R = 9 Check this figure is within limits (<12). The number of MTLs required = 9
Determining the number of LCFs for MTL processing

If GPROC3s are used exclusively:

n MTL GPROC3 = RoundDown(

n1LCFMTL_GPROC3 n lmin

1393 n MTL GPROC3 = RoundDown( )=4 12

68P02900W21-S 01 Feb 2007 9-67

Calculations using alternative call models

Chapter 9: Planning exercises

N LCFGPROC3 = Roundup(

MTLs n MTL GPROC3

)=3

The number of LCFs for MTL processing = 3

XBL requirements

The required number of XBLs is given by: XBM = [{(N/T)* (Mnewcall+Mhandovers+Hfr-hr)*LXBL*8}/(64000*UBSC-RXCDR)] Referring to Table 6-11 in Chapter 6, BSC planning steps and rules. Number of 64 kbit/s XBLs required = 3 (6 with redundancy)
GSL requirements

N/A (signaling links between BSC and PCU is not considered in this example).
GPROC3 requirements

To determine the number of GPROC3s: NGPROC3 = 2B+L+C+R B = Number of BSP GPROC3s (x 2 for redundancy) = 3

A total of 3 BSU shelves are required and each shelf must have at least one GPROC3 (x 2 for redundancy).
Where Is

L C R

total number of LCF GPROC3s required = 3. number of CSFP GPROC3s (optional) = 1. number of pool GPROC3s (for redundancy) = 1.

Total number of GPROC3s (exclusively) for BSC = (2 * 3 + 3 +1 + 1) = 11

XCDR/GDP/GDP2 requirements

N/A (no local RXCDR).

MSI requirements

Each MSI interfaces two E1 links. NMSI = NBSC_RXCDR / 2 NMSI = Number of MSIs required. NBSC-RXCDR = Number of E1 links required. Number of E1 links required at the BSC for interconnecting with the RXCDR is:

C + X + B64 + T * (1 PHR ) + B16/4 + (T * PHR )/8 31 (9 + 2 + 3 + (2946 * (1 0.18)/4)) + ((2946 * 0.18)/4) = = 24.2 ~ 25 31 N BSC RXCDR =

68P02900W21-S 9-68 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Hence the number of MSIs required for the BSC to RXCDR interface is 25/2 = 13. Each BTS site in this example needs two E1 interconnections. Hence, the number of MSIs required for BTSs is 20 * 2 / 2 = 20.

The assumptions are that the system starts allocating AMR HR resources (for AMR HRcapable MSs through HO procedures) when certain congestion thresholds are reached. Assuming that 50% of AMR-capable MSs are able to HO to HR (total about 18% MSs among all MSs). Total number of MSIs required at the BSC = 13 + 20 = 33
DSW2 requirements

Extended subrate switching mode (8 kbit/s switching) is required, so DSW2s are used. Determine the number of DSW2s (N) required:

N=

(G * n) + (R GDPRXCDR *16) + (R EGDP * 80) + (R GDP2 * 24) + (M * 64) 1016

Is

Where

G n RGDPXCDR REGDP RGDP2 M 11*16+33*64 = 2288

the number of GPROC3s (11). 16 or 32 (16 in this example). N/A in this example. N/A in this example. N/A in this example. the number of MSIs (33).

Therefore the total number of timeslots required is: Each DSW2 provides 1016 TDM timeslots. Hence, 3 non-redundant DSW2s are required for this configuration. For redundancy, 3 additional DSW2s are required. Thus, total DSW2s required = 3 + 3 (redundant) = 6.
BSU shelves

Each BSU shelf can support up to 12 MSI cards. A total of 33 MSI cards are required, based on the previous calculation. The total number of BSU shelves required is.
33 Roundup( 12 ) = 3BSU shelves.

Total GPROC3s = 11 and total MSIs = 33, split between 3 BSU shelves
Table 9-16 BSU shelves BSU 1 BSU 2 BSU 3 Check Limit

GPROC3s MSI cards

4 11

4 11

3 11

<=8 < = 12

Ensure that the following is true for each shelf:

68P02900W21-S 01 Feb 2007 9-69

Calculations using alternative call models

Chapter 9: Planning exercises

(G*n) + (M*64) + (R*16) 1016 That is, (4*16) + (12*64) + (0*16) 1016 Therefore, the number of BSU shelves required to accommodate all the hardware needed for this configuration is NBSU = 3.
KSWX/DSWX requirements

KSWXs/DSWXs should be considered for this example as the configuration needs more than one shelf. The KSWX/DSWX extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in the multi-shelf configuration. The KSWX/DSWX can be used in expansion, remote and local modes. We need 3 BSU shelves with 3 master/redundant KSWs/DSW2s, which implies that 2 expansion shelves are required. The number of KSWXs/DSWXs required (NKX) is the sum of KSWXDSWXE, KSWX/DSWXR, and KSWX/DSWXL. NKX= NKXE+NKXR+NKXL NKXE = K*(K-1) = 3 *2 = 6 (K is the number of non-redundant KSWs). NKXR = SE = 0 (SE is the number of extension shelves). NKXL = K + SE = 3. NK X = 6 + 0 + 3 = 9. The number of KSWXs/DSWXs required (with redundancy) = 18

The maximum number of KSWX/DXWX slots per shelf <=18. KSWXs and DSWXs can be used together in a shelf, provided that they are used with like pairs, that is, KSWX connected to KSWX and DSWX connected to DSWX.

GCLK requirements

The generic clock generates all the timing reference signals required by a BSU. One GLCK is required at each BSC. The number of GCLKs required (with redundancy) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one BSU. Number of CLKXs required is given by: NCLKX= Roundup (E/6) * (1+R F) Where E is the number of expansion/extension shelves and RF is the redundancy factor. NCLKX= Roundup 3/6) * (1+1) = 2 The number of CLKXs required (with redundancy) = 2
LANX requirements NLANX = NBSU*(1+R F)

Where, RF it the redundancy factor.

NLANX = 3*2 =6

Total number of LANXs required (with redundancy) = 6

68P02900W21-S 9-70 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

PIX requirements

PIX provides eight inputs and four outputs for site alarms. PIX Number of BSUs = 6
Line interfaces

Number of T43s = RoundUp (Number of MSIs)/3) Number of T43s = 33/3 = 11 The number of T43 boards required is 11
Digital power supply requirements

One redundant PSU is required for each BSU shelf, hence the total number of PSUs required is: The total number of PSUs required is 9
Non-volatile memory (NVM) board for BSC (optional)

An NVM board is required in this example, so NVM = 1.

RXCDR planning
The following planning steps are performed (for this example): The number of links between the RXCDR and BSC. The number of E1 links between the RXCDR and MSC. The number of XCDR/GDP/GDP2s. The number of GPROC3s. The number of MSIs. The number of DSW2s. The number of RXU3 shelves. The number of KSWXs/DSWXs. The number of GCLKs. The number of CLKXs. The number of LANXs. The number of PIXs. The number of line interface boards (T43s). The number of digital power supply units. Whether or not an optional NVM board is fitted.

Determining the number of E1 links between the RXCDR and BSC

N BSC RXCDR =

C + X + B64 + T * (1 PHR ) + B16/4 + (T * PHR )/8 = 25 31

Determining the number of E1 links between the RXCDR and MSC

Number of RXCDR to MSC links is given by: NRXCDR-MSC = (C+X+T)/31

68P02900W21-S 01 Feb 2007 9-71

Calculations using alternative call models

Chapter 9: Planning exercises

Where

Is

C X T

the number of MTL links required (9). the number of OML links required (2). the number of trunks between MSC and BSC (2165).

NRXCDR-MSC = { (9 + 2 + 2946)/31 }= 95.38 ~ 96 The number of E1 links between the RXCDR and MSC = 96
Determining the number of XCDR/GDP/GDP2 cards

Each XCDR/GDP/GDP2 card terminates 2 E1 links in the RXU3 shelf. Hence, the number of non-redundant cards required = 96/2 = 48, which can be a mix of XCDRs, GDPs and GDP2s.

The GDP cards can be retained for the existing FR traffic, we only require to allocate enough GDP2 cards for the additional AMR HR traffic. During the system planning exercise, we learnt that 31 AMR HR channels are needed to support AMR HR calls (among 2 carriers/6 carriers/cell). There are a total of 59 TCHs for voice traffic among 6 carriers/cell. Therefore, the number of GDP2 cards needed to support AMR HR traffic is: 30/59 (% AMR HR TCH) * 2946 (total trunks in BSC)/60 (GDP2 carries 60 calls) = GDP2 = 25
Table 9-17 Determining the number of XCDR/GDP/GDP2 cards XCDR/GDP/GDP2 Total number needed Number of E1s supported

GDP2 cards

25 (each GDP2 can offer 60 voice calls in RXU3 shelf (with enhanced capacity mode enabled) for AMR HR or FR voice calls). 46 (each card supports 30 FR voice traffic calls) 71

25 * 2 = 50

XCDR/GDP cards Total number of cards (mix) Total E1s supported

46 * 1 = 46 96

GPROC3 requirements for RXCDR

Each shelf should have minimum of one GPROC3. Hence, 5 non-redundant GPROCs are required. If the operator selects to use redundancy, 10 GPROC3s are required. The number of GPROC3s required for RXCDR = 5 + 5 (for redundancy) = 10
MSI requirements for RXCDR

As calculated in MSI requirements, the number of BSC-RXCDR links is 25. Each MSI card interfaces 2 E1 links, hence, 13 MSI cards are required on the RXCDR. MSI requirements for RXCDR = 13

68P02900W21-S 9-72 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

DSW2 requirements for RXCDR

No enhanced capacity mode is assumed as timeslot usage per shelf is not a limiting factor in this configuration. Number of TDM slots required for the GPROC3s, MSIs and XCDRs is given by: N= (G*n) (RGDPXCDR*16) + (REGDP * 80) + (RGDP2 * 24) + (M * 64)

TDM timeslots required = 8 * 16 + 25 * 24 + 13 * 64 = 2296

Each DSW2 provides 1016 timeslots on the TDM highway, hence, 3 non-redundant DSW2s are required for RXCDR with this configuration. DSW2s required for the RXCDR = 3 + 3 (redundant) = 6
RXU3 shelves

The number of RXU3 shelves required is given by (assuming that an NVM board is fitted):

N RXU3 =

M + R + N NVM 13 + 71 + 1 ~5 = 19 19

Possible configurations Table 9-18 RXU3 shelves RXU 1 RXU 2 RXU 3 RXU 4 RXU 5

MSIs / 2 E1s (M) GDP2s (R) GDPs (R)

3 5 9

3 5 9

2 5 9

2 5 9

3 5 10

Ensure that the following is true for each shelf: N + (G*n) + (M*64) + (R*16) 1016 Hence, 5 RXU3 shelves are required to equip 71 transcoder cards and 13 MSI cards. The number of RXU3 shelves required = 5
KSWX/DSWX requirements for RXCDR

The number of KSWXs/DSWXs required is the sum of KSWX/DSWXE, KSWX/DSWXR, and KSWX/DSWXL. The calculations imply 2 expansion and 2 extension shelves are required.

N KXE = N KX + N KXR + N KXL

NKXE = K * (K-1) = 3 * (3-1) = 6 K is the number of non-redundant DSW2s.

N KXR = S E = 2
SE is the number of extension shelves.

N KXL = K + S E = 3 + 2 = 5

68P02900W21-S 01 Feb 2007 9-73

Calculations using alternative call models

Chapter 9: Planning exercises

N KX = 6 + 2 + 5 = 13
The number of KSWXs/DWSXs required = 13 + 13 (redundant) = 26

KSWXs and DSWXs can be used together in a shelf, provided that they are used with like pairs, that is, KSWX connected to KSWX and DSWX connected to DSWX.
GCLK requirements

The generic clock generates all the timing reference signals required by the RXU3. One GLCK is required at each RXCDR. Number of GCLKs required = 1 + 1 (redundant) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one RXU3:

N CLKX = Roundup(E/ 6) * (1 + R F )
Where Is

E RF

the number of expansion/extension shelves. the redundancy factor.

N CLKX = Roundup(2/6) * (1 + 1) = 2
The number of CLKXs required = 1 + 1 (redundant) = 2
LANX requirements

Number of LANXs required is given by:

N LANX = N RXU 3 * (1 + R F ) = 5 * 2 = 10
Where RF it the redundancy factor. Total number of LANXs required with redundancy = 10
PIX requirements

PIX provides eight inputs and four outputs for site alarms.

PIX 2 * Number of RXU3s = 2 * 5 = 10

Hence, 10 PIX cards are required for the RXCDR.
Line interfaces

Number of T43s = Number of E1s/6 = (25+96)/6 ~ 21 The number of T43 boards required = 15
Digital power supply requirements

PSUs = 2*RXU3s + RF*RXU3s = 2*5 + 1*5 = 15 One redundant PSU is required for each RXU3 shelf, hence total number of PSUs required = 15.

68P02900W21-S 9-74 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Non-volatile memory (NVM) board for RXCDR (optional)

NVM= 1 (required in this example)

Planning example 5
Dimension a network with following requirements:
GSM software release = GSR9 Number of sites 4/4/4 sites (BTS: M-Cell6) = 62 Without AMR No LCS support No fast call setup

Call model parameters

Call duration T = 96 s Ratio of SMSs per call S = 2 Ratio of location updates per call = 2.0 Ratio of IMSI detaches per call I = 0.20 Location update factor L = 2.0 + 0.5 * 0.2 = 2.1 Number of handovers per call H = 1.32 Ratio of intra-BSC handovers to all handovers i = 0.6 Paging rate per second PGSM = 60 pages per second Number of cells at the BTS CBTS = 3 MTL link utilization = 20% (0.20) RSL link utilization U = 25% (0.25) CCCH utilization UCCCH = 33% (0.33) Probability of blocking TCH PB-TCH < 2% Probability of blocking SDCCH PB-SDCCH < 1% Probability of blocking on A-interface < 1%

Other considerations
Line interface type = E1 Network termination option = T43/PT43 Power voltage option = -48/-60 V dc Type of combining used = Hybrid (CBF) Dedicated CSFP = YES CSFP redundancy = NO Redundancy for all other modules = YES MTL links redundancy = YES

68P02900W21-S 01 Feb 2007 9-75

Calculations using alternative call models

Chapter 9: Planning exercises

RSL link redundancy = NO XBL link redundancy = NO BTS connectivity = Star configuration IMSI/TMSI paging = TMSI MTL load balancing granularity = 16 NVM board fitted at BSC and RXCDR

GSR9 limitations (assuming Huge BSC system)

Maximum BTS sites = 140 Maximum BTS cells = 250 Active RF carriers = 750 Trunks = 4800
HSP MTL links is used and they are connected with MSC directly (not pass through RXCDR)

Cell planning - control channel calculations

From Erlang B tables, the number of Erlangs supported by 32 TCHs (4-carrier cell) with GOS of 2% is 23.72 Erlangs and the number of Erlangs supported by 48 TCHs (6-carrier cell) with GOS of 2% is 38.39 Erlangs. Total Erlangs offered by a 4/4/4 BTS = 3 * 23.72 = 71.16 Erlangs
4-carrier cell - determining the number of CCCHs

Call arrival rate is given by: call = e/T = 23.72/96= 0.25 SMS rate is given by: s = S*e/T = 2*23.72/96 = 0.49 Location update rate is given by: LU = L*e/T = 2*23.72/96 = 0.49 Access grant rate is given by: AGCH = call + s + LU = 1.23 From the call model parameters, the paging rate P is 60, so the average number of CCCH blocks required to support paging only is: NPCH = PGSM / (4 * 4.25) = 60/(4*4.25) = 3.53 The average number of CCCH blocks required to support AGCH only is given by: NAGCH = AGCH / (2*4.25) = 1.23/ (2*4.25) = 0.014 Using a CCCH utilization figure (UCCCH) of 0.33, the average number of CCCH blocks required to support both PCH and AGCH is given by: NPAGCH = NAGCH + NPCH / UCCCH = (3.53+0.014)/0.33 = 10.74 Considering a non-combined BCCH with 9 CCCH blocks, 2 timeslots BCCH+CCCH are needed here.

68P02900W21-S 9-76 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Determine the number of SDCCHs per cell

Using the values calculated in the previous section and other call model parameters, the average number of SDCCHs and NSDCCH, is given by the formula mentioned in Chapter 3. NSDCCH = CB * TC + LU * (TL + Tg) + S * (TS + Tg) = 10.07 To support an average number of busy SDCCHs of 10.07 Erlangs signaling traffic with less than 1% blocking is 18 as determined by use of Erlang B tables. Hence, the number of timeslots required to carry SDCCH signaling traffic is 3 with each timeslot offering a maximum of 8 SDCCHs.
Determining the number of TCHs

Total number of signaling timeslots required for a 4-carrier configuration with the given call model parameters is 5 (2 non-combined BCCH timeslot with 9 CCCHs and 3 timeslots with 8 SDCCHs each). Therefore, the number of traffic channels per 4 carrier cell = 32 5 = 27. Hence, traffic offered by a 4-carrier cell is 19.26 Erlangs (27 traffic channels at 2% GOS). Carried Erlangs is 18.87 Erlangs. Total channels/cell = 32 Total traffic channels (voice) = 27 Control/signaling channels = 5

BSS planning
The major steps for planning the BSC system include: The number of RSL links between the BSC and BTSs. The number of E1 links between BSC and BTSs. The number of LCFs for RSL processing. The number of MTL links between BSC and MSC. The number of LCFs for MTL processing. The number of XBL links between BSC and RXCDR. The number of GSL links between BSC and RXCDR. The number of GPROCs. The number of XCDR/GDP/GDP2s. The number of MSI cards. The number of KSWs/DSW2s. The number of BSU shelves. The number of KSWXs/DSWXs. The number of GCLKs. The number of CLKXs. The number of LANXs. The number of PIXs. The number of line interface cards (T43s). The number of digital power supplies. Whether or not an optional NVM board is fitted.

68P02900W21-S 01 Feb 2007 9-77

Calculations using alternative call models

Chapter 9: Planning exercises

RSL requirements

The number of 64 kbit/s RSLs required is given by: RSL GSM+GPRS@64k = RoundUp (RSL GSM + RSL GPRS) RSLGSM = n*(59+S*(25+SMSsize*0.125)+38*H+24*L+24*Lcs)/(1000*U*T) +(31+3*Cbts)*Pgsm/(8000*U) RSLGPRS = (32+Cbts)* PGPRS/ (8000*U) + 5.5 * GPRS_RACH/sec / (1000*U) Where n is the number of TCHs under the BTS. Hence, for a 4/4/4 site (no GPRS): RSLGSM +GPRS = Roundup (RSLGSM+ RSLGPRS) = Roundup (1.98 +0) = 2 The number of RSLs required per 4/4/4 site is 2.
BSC to BTS E1 interconnect planning

Number of E1 links required between a BSC and BTS is given by: {23769}
nEGPRS n =0

{[( N BSC BTS =

RTF_DS0_CO

UNT) + (nC GPRS * 4) + (nG GPRS * 2) + L16/4]}) + L64 31

Number of E1 links required between each 4/4/4 BTS and BSC: = (12*2+2)/31 = 1 Hence, 1 E1 interconnection is required between each BTS and BSC for the given site configurations (provided they are in star configurations). Thus, a total of 62 * 1 = 62 E1 links are required. The number of E1s between the BSC and BTS is 62.
Determining the number of LCF GPROCs for RSL processing

Number of LCF-RSLs required is given by:

G L3 =

n * (1 + 0.35 * S + 0.34 * H * (1 0.4 * i) + 0.32 * L) C + (0.00075 * PGSM + 0.004) * B + (19.6 * T) 120

Where, n is the number of TCHs under a BSC: 62*3*27*(1+0.35*2+0.34*2.5*(1-0.4*0.6)+0.32*2.1)/ (19.6*96) + (0.00075*60+0.004)*62 +62*3/120 = 12.638 ~13
Determining the number of MTLs

Total Erlangs offered by the BSC with 62 sites with 4/4/4 configuration: = 62 *3* 19.26 = 3582.36 Erlang Total Erlangs carried by the BSC with 62 sites with 4/4/4 configuration: = 62*3*18.87 = 3510.71 Erlang The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 3602 (using offered Erlangs to calculate). Using the call model parameters, the number of MTLs can be calculated using formulae mentioned in Chapter 6 or according to the Table 6-11 (Number of HSP MTL at 20% utilization) in 4 HSP MTLs are required (with redundancy).

68P02900W21-S 9-78 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Determining the number of LCFs for MTL processing

Since one GPROC3-2 LCF can support one HSP MTL, the number of LCFs is equal to the number of HSP MTLs.

N mtls LCF = the number of LCFs for 4 HSP MTLs is 4

XBL requirements

Refer to Table 6-11 in Chapter 6, BSC planning steps and rules. Number of XBLs required = 4 (using N = 3602)
GSL requirements

N/A (signaling links between BSC and PCU)

GPROC requirements

To determine the number of GPROCs: NGPROC = B + L + C + R

Where Is

B L C R

number of BSP GPROC3s/GPROC3-2s (include redundancy) = 3. total number of LCF GPROCs required = 17. (Where the number of RSL LCF is 13, MTL LCF is 4) number of CSFP GPROCs (dedicated) = 1. number of pool GPROCs (for redundancy) = 3.

For common pool, one GPROC3-2 is suggested. For MTL-LCF, GPROC3-2 is required. For high reliability and availability, 3 GPROCs are required. One is for RSL LCF redundancy, the second one is for MTL LCF redundancy and the third one for other GPROC function redundancy. Total number of GPROCs for BSC = 3+17+1+3 = 24
XCDR/GDP/GDP2 requirements

N/A (no local RXCDR).

MSI requirements

Each MSI interfaces two E1 links. NMSI = Number of MSIs required NBSC-RXCDR = Number of E1 links required at the BSC for interconnecting with the RXCDR NBSC-RXCDR= {C+X+B64+[T*(1-PHR)+N16]/4+(T*PHR)/8}/31 If HSP MTLs are used (go to MSC directly) and non_AMR supported. NBSC-RXCDR = C + (X+ B64+ T/4))/31 = 0 + (2 + 4+ 3602/4)/31 = 29.24 ~ 30 Where 2 OMLs, and 4 XBLs are required. PHR in the equation is not considered in non-AMR cases.

68P02900W21-S 01 Feb 2007 9-79

Calculations using alternative call models

Chapter 9: Planning exercises

Additional 4 E1s are required for HSP MTL. Hence, the number of MSIs required for the BSC to RXCDR interface is (30+4)/2 = 17. Each BTS site in this example needs 1 E1 interconnections. Hence, the number of MSIs required for BTSs is 62 / 2 = 31. Total number of MSIs required at the BSC = 31 + 17 = 48
KSW/DSW2 requirements

Determine the number of KSWs/DSW2s (N) required (if enhanced capacity mode is not enabled): N=(G*n)+(Rgdpxcdr*16)+(Regdp*96)+(Rgdp2*24)+(M*64)+(Rpsi* t)/1016
Where Is

G n Rgdp M Rpsi

the number of GPROCs. 16 or 32 (32 in this example). N/A in this example (RXCDR case). the number of MSIs the number of PSI (N/A in this example)

RGDPXCDR and REGDP are not considered in the equation. Therefore the total number of timeslots required is: 24x32+48x64 = 3840 Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 4 non-redundant KSWs/ DSW2s are required for this configuration. For redundancy, 4 additional KSWs/ DSW2s are required. Thus, total KSWs/DSW2s required (with redundancy) = 4 + 4 = 8.
BSU shelves

Each BSU shelf can support up to 12 MSI cards or 8 MSI with 4 PSI in GSR9. A total of 48 MSI cards are required, based on the previous calculation. The total number of BSU shelves required is: Roundup (48/12) = 4 BSU shelves Total GPROCs = 24 and total MSIs = 48, split between 4 BSU shelves.
BSU 1 BSU 2 BSU 3 BSU4 CHECK LIMIT

GPROCS MSI CARDS

6 12

6 12

6 12

6 12

<=8 < = 12

Where BSU 1,2, 3, 4 have KSW/DSW2 in shelf.

68P02900W21-S 9-80 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

Ensure that the following is true for each expansion shelf.

(G * n ) + (M * 64) + (R *16) 1016

That is, 6 * 32 + 12 * 64 < 1016 Therefore, the number of BSU shelves required to accommodate all the hardware needed for this configuration is NBSU = 4.
KSWX/DSWX requirements

KSWXs/DSWXs should be considered for this example as the configuration needs more than one shelf. The KSWX/DSWX extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in the multi-shelf configuration. The KSWX/DSWX can be used in expansion, remote and local modes. We need 4 BSU shelves with 4 master/redundant KSWs/DSW2s, which implies that 4 expansion shelves are required. The number of KSWXs/DSWXs required (NKX) is the sum of KSWXDSWXE, KSWX/DSWXR, and KSWX/DSWXL: NKX = NKXE + NKXR + NKXL NKXE = K*(K-1) = 4 *3 = 12 (K is the number of non-redundant KSWs) NKXR = SE = 0 (SE is the number of extension shelves) NKXL = K + SE = 4+0=4 NK X = 12 +4 = 16 The number of KSWXs/DSWXs required (with redundancy) = 32

The maximum number of KSWX/DXWX slots per shelf <=18. KSWXs and DSWXs are used together in a shelf, provided that they are used with like pairs, that is, KSWX connected to KSWX and DSWX connected to DSWX.

GCLK requirements

The generic clock generates all the timing reference signals required by a BSU. One GLCK is required at each BSC. The number of GCLKs required (with redundancy) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one BSU. Number of CLKXs required is given by:
N = Roundup (E/6) * (1 + R F )

Where

Is

E RF

the number of expansion/extension shelves the redundancy factor.

NCLKX = Roundup (4/6) * 2 = 2 The number of CLKXs required (with redundancy) = 2

68P02900W21-S 01 Feb 2007 9-81

Calculations using alternative call models

Chapter 9: Planning exercises

LANX requirements

N LANX = N BSU * (1 + R F )
Where, RF is the redundancy factor. NLANX = 4 * 2 = 8 Total number of LANXs required (with redundancy) = 8
PIX requirements

PIX provides eight inputs and four outputs for site alarms. PIX number of BSUs = 8
Line interfaces

Number of MSIs Number of T43s = Roundup 3

Number of T43s = RoundUp (48/3) = 16 The number of T43 boards required is 16
Digital power supply requirements

The number of PSUs required is given by: PSUs = NBSU * (2 + RF) One redundant PSU is required for each BSU shelf, hence the total number of PSUs required is: PSU = 4 * (2 +1) = 12 The total number of PSUs required is 12.
Non-volatile memory (NVM) board for BSC (optional) NVM = 0 0r 1

An NVM board is required in this example, so NVM = 1.

RXCDR planning
The following planning steps are performed (for this example): The number of links between the RXCDR and BSC. The number of E1 links between the RXCDR and MSC. The number of XCDR/GDP2/GDP2s. The number of MSIs. The number of RXU shelves. The number of GPROCs. The number of KSWs/DSW2s. The number of KSWXs/DSWXs. The number of GCLKs. The number of CLKXs. The number of LANXs. The number of PIXs.

68P02900W21-S 9-82 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

The number of line interface boards (T43s). The number of digital power supply units. Whether or not an optional NVM board is fitted.

Determining the number of E1 links between the RXCDR and MSC

Number of RXCDR to MSC links is given by: NRXCDR-MSC = C + (X+T)/31

Where Is

C X

the number of HSP MTL links required. Assuming HSP MTLs go from BSC to MSC directly, C is 0 in equation. the number of OML links through MSC. If OML links do not pass through MSC, X is equal to 0. Then an additional E1 is needed between RXCDR and OMC-R. the number of trunks between MSC and BSC (3602).

NRXCDR-MSC = 3602/31 = 116.2 ~ 117 The number of E1 links between the RXCDR and MSC = 117
Determining the number of XCDR/GDP/GDP2 cards

Each XCDR/GDP/GDP2 terminates one E1 link (for the RXU shelf). Hence, the number of non-redundant cards required is 3602/31= 117, which can be a mix of XCDRs, GDPs and GDP2s. The number of non-redundant XCDR/GDP/GDP2 cards = 117.
MSI requirements for RXCDR

As calculated in MSI requirements, the number of BSC-RXCDR links is 30 and 1 E1 for BSC- OMC-R. Each MSI card interfaces 2 E1 links, hence, 16 MSI cards are required on the RXCDR. MSI requirements for RXCDR = 16.
RXU shelves

The number of RXU shelves required is given by (assumes an NVM board is fitted): NRXU = Max (M/5, (R+NNVM)/16 = Max (16/5, (117+1)/16) = 8
GPROC requirements for RXCDR

Each shelf should have minimum of one GPROC. Hence, 8 non-redundant GPROCs are required. If the operator selects to use redundancy, 16 GPROCs are required. The number of GPROCs required for RXCDR = 8 + 8 (for redundancy) = 16
KSW/DSW2 requirements for RXCDR

Number of TDM slots required for the GPROCs, MSIs and XCDRs is given by: TDM timeslots required = G*n + M*64 + R*16 16 * !6 + 15 * 64 + 117 * 16 = 3216 Each KSW/DSW2 provides 1016 timeslots on the TDM highway, hence, 4 non-redundant KSWs/DSW2s are required for RXCDR with this configuration. KSWs/DSW2s required for the RXCDR = 4 + 4 (redundant) = 8

68P02900W21-S 01 Feb 2007 9-83

Calculations using alternative call models

Chapter 9: Planning exercises

Table 9-19 KSW/DSW2 requirements RXU 1 RXU 2 RXU 3 RXU 4 RXU 5 RXU6 RXU7 RXU8

MSIS XCDRS/GDP S GPROCS

2 14 2

2 14 2

2 15 2

2 15 2

2 15 2

2 15 2

2 15 2

2 14 2

Ensure that the following is true for each shelf: N + (G*n) + (M*64) + (R*16) 1016 Hence, 8 RXU shelves are required to equip 117 XCDR/GDP/GDP2 cards and 16 MSI cards. The number of RXU shelves required = 8.
KSWX/DSWX requirements for RXCDR

The number of KSWXs/DSWXs required is the sum of KSWX/DSWXE, KSWX/DSWXR, and KSWX/DSWXL. The calculations imply that 2 expansion and 2 extension shelves are required.

N KX = N KXE + N KXR + N KXL N KXE = K * (K 1) = 4 * 3 = 12

K is the number of non-redundant KSWs/DSW2s.

N KXR = S E = 4
SE is the number of extension shelves.

N KXL = K + S E = 4 + 4 = 8
N KX = 12 + 4 + 8 = 24
The number of KSWXs/DWSXs required = 24 + 24 (redundant) = 48 KSWXs and DSWXs can be used together in a shelf, provided that they are used with like pairs, that is, KSWX connected to KSWX and DSWX connected to DSWX.
GCLK requirements

The generic clock generates all the timing reference signals required by an RXU. One GLCK is required at each RXCDR. Number of GCLKs required = 1 + 1 (redundant) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one RXU: NCLKX = Roundup (E/6) * (1+RF)
Where Is

E RF

the number of expansion/extension shelves. the redundancy factor.

NCLKX = Roundup(8/6) * (1+0) =2 NCLKX = Roundup (8/6) * (1+ 0) = 2 The number of CLKXs required = 2 + 2 (redundant) = 4

68P02900W21-S 9-84 01 Feb 2007

System Information: BSS Equipment Planning

Calculations using alternative call models

LANX requirements

Number of LANXs required is given by: NLANX = NRXU *(1+RF) = 8*2 = 16 Where RF is the redundancy factor. Total number of LANXs required with redundancy = 16
PIX requirements

PIX provides eight inputs and four outputs for site alarms. PIX 2* Number of RXUs = 2*8 = 16 Hence, 16 PIX cards are required for the RXCDR.
Line interfaces

Number of T43s = Number of E1s/6 = (117+30+4+1)/6 = 26 The number of T43 boards required = 26
Digital power supply requirements

PSUs = 2*RXUs+RF * RXUs = 2*8 + 1*8 = 24 One redundant PSU is required for each RXU shelf, hence total number of PSUs required = 24.
Non-volatile memory (NVM) board for RXCDR (optional)

NVM= 1 (required in this example)

68P02900W21-S 01 Feb 2007 9-85

Planning example of BSS support for LCS provisioning

Chapter 9: Planning exercises

Planning example of BSS support for LCS provisioning

Typical parameter values
Use this example to plan the equipment of a BSC supporting a traffic model, with the parameters listed in Table 9-20 and their typical values. This example is for 28 sites/BSC with 3 cells/BTS and 4 carriers/cell.
Table 9-20 Typical LCS call model parameter PARAMETER VALUE

MAXIMUM TRUNKS BETWEEN MSC AND BSC NUMBER OF BTSS PER BSS NUMBER OF CELLS PER BSS CALL DURATION CALL RATE [CALL/SUB/BH] LCS PENETRATION RATE [%] LCS REQUEST RATE2: [REQ/SEC/BSC] LINK UTILIZATION FACTOR UMSC_BSC LINK UTILIZATION FACTOR U BSC_BTS

N=3000 28 4*4*4 SITES 28*3 T = 75 S CALL_SUB_RATE = 1 LCS = 5% LCS_BSC_RATE = 2 0.35 0.25

LCS planning example calculations

Determine LCS architecture
BSS-based LCS architecture is supported.

68P02900W21-S 9-86 01 Feb 2007

System Information: BSS Equipment Planning

Planning example of BSS support for LCS provisioning

Calculate MTLs (actually needed trunks number is 1812)

nlink_bss = = (1000 * U * T) (40 + 47 * S + 22 * H(1 0.8 * i) + 24 * L + 31 * L CS ) + 9 + PPC * (1 + L CS )

(1000 * 0.35 * 75) (40 + 47 * 0.1 + 22 * 2.5 * (1 0.8 * 0.6) + 24 * 2 + 31 * 0.05) + 9 * 0.124 * (1 + 0.05)) = 151.486

nlLCFMTL = (20 * T)/(1+ 0.16* S + 0.5 * H * (1 0.6 * i) + 0.42* L + 0.45* LCS ) + PPC * (0.005* B + 0.05)* (1 + LCS )) = (20 * 75) (1 + 0.6 * 0.1 + 0.5 * 2.5 * (1 0.6 * 0.6) + 0.42* 0.05) + 0.124* (0.005* 56 + 0.05)* (1 + 0.05)) = 559.268

n1min=MIN (nllink, n1LCF-MTL )= 151.468 nllogical = N/Ng = (1812/64) = 28.31 nlog_per_mtl = RoundDown (n1min/Nlogical) = 5 Finally, the number of required MTLs with 64 logical links is: mtls = RoundUp (Ng/ Nlog_per_mtl) = 13

Calculate MTL LCFs

NLCF-MTL = 13/2 = 6

Calculate RSLs
According to Chapter 3, TCHs per BTS is 29*3. Then,

RSL GSM @ 64k =

n * (49 + 50 + S + 32 * H + 25 * L + L CS * 24) (27 + 3 * C) * PGSM * (1 + L CS ) + 1000 * U * T 8000 * U 87 * (49 + 50 * 0.1 + 32 * 2.5 + 20 * 2 + 0.05 * 24) ( 27 + 3 * 3) * 3 * (1 + 0.05) = + = 0.87 1000 * 0.25 *120 8000 * 0.25

Calculate RSL LCFs

n * (1 + 0.35 * S + 0.34 * H * (1 0.4 * i) + 0.32 * L + 0.45 * L CS + (19.6 * T) G L3 = C 0.0004 + 0.00075 * P * (1 + L CS )) * B + )] 120 [

68P02900W21-S 01 Feb 2007 9-87

Planning example of BSS support for LCS provisioning

Chapter 9: Planning exercises

3000 * (1 + 0.35 * 0.1 + 0.34 * 2.5 * (1 0.4 * 0.6) + 0.32 * 2 + 0.45 * 0.05 + 19.6 *120 86 (0.004 + 0.00075 *1.05 * 3) * 30 + 120 =
Therefore, the RSL LCFs number is 4.

Calculate LMTLs
LMTL =

Roundup(

LCS_BSC_Rate *19 2 * 19 ) = Roundup( ) =1 1000 * U BSC_SMLC 1000 * 0.2

Calculate LMTL LCFs

N LCF _ LSL = 1

68P02900W21-S 9-88 01 Feb 2007

System Information: BSS Equipment Planning

Planning example for DTM Feature

Planning example for DTM Feature

{23291}

Dimension a network with following requirements:

GSM software release = GSR9 Number of sites 6/6/6 sites (BTS: M-Cell6) = 41, 3EGPRS carrier per cell No QoS support DTM is enabled Without AMR With VersaTRAU No LCS support Core Network Paging coordination is disabled, PCCCH is disabled (NOM2) HSP MTL links is used FCS is disabled

Call model parameters

Call duration T = 90 s Ratio of SMSs per call S = 2 Ratio of location updates per call = 2.0 Ratio of IMSI detaches per call I = 0.20 Location update factor L = = 2.1 Number of handovers per call H = 1.32 Ratio of intra-BSC handovers to all handovers i = 0.6 GSM Paging rate per second PGSM = 60 pages per second Number of cells at the BTS CBTS = 3 MTL link utilization = 20% (0.20) RSL link utilization U = 25% (0.25) CCCH utilization UCCCH = 33% (0.33) GBL utilization = 40% (0.40) Probability of blocking TCH PB-TCH < 2% Probability of blocking SDCCH PB-SDCCH < 1% Probability of blocking on A-interface < 1% Average packet size PKsize=560.17 bytes Traffic per sub/BH (Kbytes/hr)- uplink ULrate = 14.55 Traffic per sub/BH (Kbytes/hr)- downlink DLrate = 54.46 GPRS Paging rate per second PGPRS = 20.94 pages per second Average sessions per user per hour = 0.45

68P02900W21-S 01 Feb 2007 9-89

Planning example for DTM Feature

Chapter 9: Planning exercises

GPRS users per cell = 100000 / (41*3) = 813 RAU message per sub per hour = 1.4 Cell Update message per sub per hour = 0.33 PDP context activation/deactivation per sub per hour = 0.4 PS Attach/Detach per sub per hour = 0.5 DL Timeslot weighting for user = 0.25 UL Timeslot weighting for user = 2 Percentage of Capable Mobiles Using DTM = 30% DTM mode scaling factor = 30%

Other considerations
Line interface type (except BSC-PCU) = E1 Line interface type (BSC-PCU) = Ethernet Link Network termination option = T43/PT43 Power voltage option = -48/-60 V dc Type of combining used = Hybrid (CBF) Dedicated CSFP = YES CSFP redundancy = NO Redundancy for all other modules = YES MTL links redundancy = YES RSL link redundancy = NO EGPRS enabled = YES BTS connectivity = Star configuration IMSI/TMSI paging = TMSI MTL load balancing granularity = 16 NVM board fitted at BSC and RXCDR ePCU enabled = YES
o

DPROC2 works as PXP and Prp_fanout_mode 1 enabled

GSR9 limitations (assuming Huge BSC system)

Maximum BTS sites = 140 Maximum BTS cells = 250 Active RF carriers = 750 Trunks = 4800 MSI = 96 HSP MTL links is used.

From Erlang B tables, the number of Erlangs supported by 48 TCHs (6-carrier cell) with GOS of 2% is 38.39 Erlangs. Total Erlangs offered by a 6/6/6 BTS = 3 * 38.39 = 115.17 Erlangs

68P02900W21-S 9-90 01 Feb 2007

System Information: BSS Equipment Planning

Planning example for DTM Feature

DTM related parameters calculation:

The probability a subscriber is in dedicated mode is given by:

RCS =

( BHCApersub *Voicecallduration) 1.8 * 90 = = 4.5% 3600 3600

UL traffic per sub (Kbits) per hour is 14.55*8= 116.4 kbits/hour DL traffic per sub (Kbits) per hour is 54.46*8= 435.68 kbits/hour The Average uplink rate is given by:
AverageULrate_per_su b = 4 (Percentag eGPRSUsage intotalULt raffic * ( (CSn_usage UL * CSn_reate) * (1 - BLER )+ n =1 4 (MCSn_usag eUL * CSn_reate) * (1 - BLER Percentage EGPRSMCSus ageintotal ULtraffic * ( ( n =1
GPRS

GPRS

* ULTimeslot _ weighting = 30.78 kbps

The Average downlink rate is given by:

AverageULr ate_per_su b = 4 (Percentag eGPRSUsage intotalDLt raffic * ( (CSn_usage DL * CSn_reate) * (1 - BLER ) + n = 1 4 ( Percentage EGPRSMCSus ageintotal DLtraffic * ( (MCSn_usag eDL * CSn_reate) * (1 - BLER n = 1
GPRS

GPRS

* DLTimeslot _ weighting = 3.85 kbps

The probability that a subscriber is in packet transfer mode is given by:

R PS

ULtrafficpersub(Kbit/h) DLtrafficpersub(Kbit/h) + AverageULrate(Kbps) AverageDLrate(Kbps) =

3600

= (116.4/30.78 + 435.68/3.85)/3600 = 3.25%

The probability a DTM capable subscriber is in DTM mode (that is, using DTM) is given by:
RDTM= (1+DTMmodescalingfactor)*(RCS*RPS) = 0.19% 6-carrier cell - determining the number of CCCHs

Call arrival rate is given by: call = e/T = 115.17/90= 1.28 SMS rate is given by:

68P02900W21-S 01 Feb 2007 9-91

Planning example for DTM Feature

Chapter 9: Planning exercises

s=S*e/T = 2*115.17/96 = 2.69 Location update rate is given by: LU=L*e/T = 2*115.17/96 = 2.56 Access grant rate is given by: AGCH= call + s + LU = 6.53 From the call model parameters, the paging rate P is 60, so the average number of CCCH blocks required to support paging only is: NPCH = PGSM*(1-PDTM*RPS)/(4*4.25) = 60*(1-30%*3.25%)/(4*4.25) = 3.49 The average number of CCCH blocks required to support AGCH only is given by: NAGCH = AGCH/(2*4.25) = 6/(2*4.25) = 0.77 Using a CCCH utilization figure (UCCCH) of 0.33, the average number of CCCH blocks required to support both PCH and AGCH is given by: NPAGCH = (NAGCH + NPCH)/UCCCH = (3.49+0.77)/0.33 = 12.91 Considering a non-combined BCCH with 9 CCCH blocks, 2 timeslots BCCH+CCCH are needed here.
Determine the number of SDCCHs per cell

Using the values calculated in the previous section and other call model parameters, the average number of SDCCHs. NSDCCH, is given by the formula mentioned in Chapter 3: NSDCCH = call * TC + LU*(TL+Tg) + s* (Ts+Tg) = 1.28* 5+2.69*8+2.56*10=53.49 To support an average number of busy SDCCHs of 53.49 Erlangs signaling traffic with less than 1% blocking is 68 as determined by use of Erlang B tables is 68. Hence, the number of timeslots required to carry SDCCH signaling traffic is 9, with each timeslot offering a maximum of 9 SDCCHs are needed.
Determine the number of maximum DTM timeslots per cell

General rule for Max_DTM_TS configuration is to consider the number of subscribers using DTM in the cell at any instant and the number of timeslots that require to be allocated to each subscriber. The number of subscribers using DTM in a cell at any instant is given by: Number of subs using DTM at any instant = RDTM*PDTM*Total_Subs=0.19% * 813 * 30% =0.46 Considering there are DTM Class 9 and Class 11 in this cell:
Max_DTM_TS = Roundup (Number of Subs using DTM at any instant) * The maximum PD number supported by DTM MS in DTM mode in this cell = 1* 2 = 2.

Total DTM token needed per cell is 2.

Determining the number of PDCHs

Use the equation to determine the number of GPRS timeslots that are required on a per cell basis. In order to use this equation, the network planner should have the expected cell load in kbit/s.

Mean_traffic_load =

GPRS_Users * (1 R CS * R DTM ) * Data_rate_per_sub 3600

813 * (1 0.19%) * (14.55 + 54.46) * 8 3600

= 122.99kbps

68P02900W21-S 9-92 01 Feb 2007

System Information: BSS Equipment Planning

Planning example for DTM Feature

i = 4CSi_distribution * (1 BLER ) * GPRS_Percentage + i =1 GPRS 1 9 TS_Data_Rate = 100 MCSi_Rate * MCSi_Distribution * (1 BLER ) * EGPRS_percentage EGPRS i = 1
= 15.39kbps
Mean_traffic_load * Mean_load_factor TS_Data_Rate

No_PDCH_TS = Roundup{

= Roundup(

122.99 * 2 15.39

) = 16

There are 16 timeslots configured as packet switch timeslots (include switchable and reserved TS). In this example, we put circuit switch call capacity into first priority and guarantee minimum GPRS coverage at the same time. So, totally 4 timeslots are configured as reserved PDTCH. Total 12 timeslots configured as switchable timeslots.
Determining the number of TCHs

Total number of signaling timeslots required for a 6-carrier configuration with the given call model parameters is 11 (2 non combined BCCH timeslot with 9 CCCHs and 9 timeslots with 8 SDCCHs each). 4 timeslots are used as reserved PDCHs. Therefore, the number of traffic channels per 6 carrier cell = 48 - 11- 4 = 33. Hence, traffic offered by a 6-carrier cell is 24.63 Erlangs (33 traffic channels at 2% GOS). Total Erlangs in the BSS = 24.63*41*3 = 3029.49. Total channels/carrier = 48 Total traffic channels (voice) = 33 Control/signaling channels = 11 Reserved timeslots = 4 DTM token = 2 Switchable timeslots = 12

Determining the number of active PDCHs

Since the equation resulted in 18 timeslots and 4 reserved timeslots are active, the total active timeslots and supported timeslots for BSS are: Total active timeslots = 4*3*41 = 492 Total supported timeslots = 18*3*41 = 2214

BSS planning
The major steps for planning the BSC system include: The number of RSL links between the BSC and BTSs. The number of E1 links between BSC and BTSs. The number of LCFs for RSL processing. The number of MTL links between BSC and MSC.

68P02900W21-S 01 Feb 2007 9-93

Planning example for DTM Feature

Chapter 9: Planning exercises

The number of LCFs for MTL processing. The number of XBL links between BSC and RXCDR. The number of GSL links between BSC and PCU. The number of PXP cards in PCU. The number of PSI cards. The number of GPROCs. The number of XCDR/GDP/GDP2s. The number of MSI cards. The number of PSI requirements. The number of KSWs/DSW2s. The number of BSU shelves. The number of KSWXs/DSWXs. The number of GCLKs. The number of CLKXs. The number of LANXs. The number of PIXs. The number of line interface cards (T43s). The number of digital power supplies. Whether or not an optional NVM board is fitted.

RSL requirements

The number of 64 kbit/s RSLs required is given by: RSLGSM+GPRS@64k =Roundup(RSLGSM+RSLGPRS) RSLGSM = N*(59+S*(25+SMSsize*0.125)+38*H+24*L)/(1000*U*T)+(31+3+CBTS)*PGSM* (1-PDTM*RPS)/(8000*U) RSLGPRS =(32+ CBTS)* PGPRS /(8000*U)+5.5*GPRS_RACHpersec/(1000*U) Where n is the number of TCHs under the BTS. Hence, for a 6/6/6 site: RSLGSM = 33*3(59+2*25+100*0.125)+38*1.32+24*2.1+24*0)/(1000*0.25*0.90)+(31+3+3)*60* (1-30%*3.25%)/(8000*0.25) =2.22 RSLGPRS =(32+3)*20.94/(8000*0.25)+5.5*(813*3*0.45/3600)/(1000*0.25) = 0.37 RSLGSM+GPRS =Roundup (RSLGSM + RSLGPRS) = Roundup (2.22+0.37) = 3 The number of RSLs required per 6/6/6 site is 3.
BSC to BTS E1 interconnect planning

Number of E1 links required between a BSC and BTS is given by: {23769}

68P02900W21-S 9-94 01 Feb 2007

System Information: BSS Equipment Planning

Planning example for DTM Feature

{[( N BSCBTS =

n EGPRS i =0

RTF DS0_Count ) + (nC

i

GPRS

* 4) + nG GPRS * 2) + L16 /4]} + L 64

31

Assuming the number of RTF_DS0_COUNT for 1 EGPRS carry with 8 switchable PDCHs/cell is 5, for 1 EGPRS carry with 4 reserved PDs is 3 and 4 with 4 switchable PDs for the third EGPRS/cell carry. Therefore, Number of E1 links required between each 6/6/6 BTS and BSC: NBSC-BTS= Roundup {[(3*(3+5+4)+3*3*2+3]/31}=2 Assuming the number of RTF_DS0_COUNT for 1 EGPRS carry with 8 switchable PDCHs/cell is 5, for 1 EGPRS carry with 4reserved PDs is 3 and 4 with 4 switchable PDs for the third EGPRS/cell carry. Therefore, Number of E1 links required between each 6/6/6 BTS and BSC: NBSC-BTS= Roundup {[(3*(3+5+4)+3*3*2+3]/31}=2 Hence, 2 E1 interconnections are required between each BTS and BSC for the given site configurations (provided they are in star configurations). Thus a total of 41 * 2 = 82 E1 links are required. The number of E1s between the BSC and BTS is 82.
Determining the number of LCF GPROCs for RSL processing

Number of LCF-RSLs required is given by:

n * (1 + 0.35 * S + 0.34 * H * (1 0.4 * i) + 0.32 * L + 0.35 * L CS (19.6 * T) G L3 = C + 0.00075 * PGSM * (1 - PDTM * R PS + 0.004) * B + )] 120 [
GL3_GPRS= 0.002*Total_RACH/sec+(1-RPCCCH_Cell)+0.00075*B*PGPRS*PCCCH_BSS Where, n is the number of TCHs under a BSC. GL3 = [33 * 3 * 41 * (1 + 0.35 * 2 + 0.34 * 1.32 * (1 - 0.4 * 0.6) + 0.32 * 2.1) / (19.6 * 90)] + [(0.00075 * 60 *(1-30%*3.25%) + 0.004) * 41 + 41 * 3 / 120 ]= 6.24+3.01 = 9.25 GL3_GPRS= 0.002* (100000*0.45/3600)+0.00075*41*20.94 = 0.64 Therefore, the number of LCF-RSLs required is 10.
Determining the number of MTLs

Total Erlangs offered by the BSC with 41 sites with 6/6/6 configuration: 41*3*24.63=3028.88 The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 3052 (using offered Erlangs to calculate). Verify that this figure is within limits (< 4800 for a Huge BSC system). Number of pages per call: PPC = PGSM*T/N = 60*90/3052 = 1.77 The number of 3052 Erlangs supported by HSP P MTL is 4 (with redundancy).
Determining the number of LCFs for MTL processing

One HSP MTL is supported by one GPROC3-2 MTL-LCF. Therefore, the number of LCFs for MTL is 4.
XBL requirements

Referring to Table 6-11 in Chapter 6, BSC planning steps and rules. Number of XBLs required = 4 (using N = 3052)

68P02900W21-S 01 Feb 2007 9-95

Planning example for DTM Feature

Chapter 9: Planning exercises

GSL requirements

Total_RACH/sec =41*3*813*0.45/3600 = 12.50 GSLRACH = 1*12.50*5.5/(1000*0.25) = 0.275 GSLPaging = 8.5*20.96*10*1/(1000*0.25) = 7.12 The number of GSL TS for run time is represented by: GSLrun_time = (GSLRACH+GSLPaging) * GSLDTM_overhead = Roundup ((7.12+0.275)*1.03) = 8 The number of GSL required is GSL= Max (GSLrun_time, GSLinit_time) = 8
Calculate the number of GBL links

Using the standard traffic model and Gb formulae:

Signaling_ Data_Rate= (21* Cell + 312* PS )* update Attach/Det ach Subscriber s_per_PCU + 89 * P GPRS 3600
User_Data_ Rate = GPRS_Users _PCU * Data_rate_ per_sub * 1000 71 * 1+ 3600 PK size

No_GBL_TS = N PCU_SGSN =
Therefore,

Total_Data_Rate 8000 * U GBL

No_GBL_TS 31

Signaling_Data_Rate = (21*0.33+312*0.5+125*1.4+172*0.4)*123*813/3600+89*20.96 = 13161.72bytes/s

User_Data_Rate = (813*123*92.28*1000/3600*(1+71/560.17) = 1704518 bytes/s No_GBL_TS = (13161.72+1704518)/(8000*0.4) = 536.78 NPCU-SGSN = 536.78 / 31 = 17.3 ~ 18 The number of GBLs required is 18.
Number of PXP cards and BSC to PCU Ethernet link Interconnect Planning

There is one ETH link between a PXP/PSI pair. So the number of ETH links required is determined by the number of PXP cards. (refer to Ethernet interface provisioning in Chapter 8) As PXP works at Prp_fanout_mode=1, a PXP board can be assigned up to 280 timeslots but only 70 are serviced (active) at any given time. As calculated , the total active timeslots are 492 and the supported timeslots are 2214. The number of PXPs from PDCH capacity view is: Maximum (492/70, 2214/280) = 8 From the view of 18 GBLs required where one PXP can support 3 GBLs, the PXPs needed are Round up (18/3)=6. Taken all aspect into consideration, 8 PXPs are needed with supporting of 18 GBLs. 8 of them connect with PSIs in BSC by 8 ETH links.

68P02900W21-S 9-96 01 Feb 2007

System Information: BSS Equipment Planning

Planning example for DTM Feature

GPROC requirements

To determine the number of GPROCs: NGPROC = B+L+C B = Number of BSP GPROC3s/GPROC3-2s (with redundancy) = 3 L = Total number of LCF GPROCs required = 14 (4 MTL LCFs and 10 RSL LCFs) C = Number of CSFP GPROCs (optional) = 1 R = Number of pool GPROCs (for redundancy) = 1 Total number of GPROCs for BSC = (3 + 14 +1 + 1) = 19
XCDR/GDP/GDP2 requirements

N/A (no local RXCDR).

MSI requirements

Each MSI interfaces two E1 links.

NMSI =
Where

N BSC RXCDR 2
Is

NMSI NBSC-RXCDR

number of MSIs required. number of E1 links required between BSC and RXCDR.

Number of E1 links required at the BSC for interconnecting with the RXCDR is: NBSC-RXCDR= C+ (X+B64+ (T*(1-PHR)+N16)/4+(T*PHR)/8)/31 = 4 + (2 + 4+ 3052/4)/31 = 28.80 ~29

PHR in the equation is not considered in non-AMR cases. Hence the number of MSIs required for the BSC to RXCDR interface is 29/2 = 15. Each BTS site in this example needs two E1 interconnections. Hence the number of MSIs required for BTSs is 41 * 2 / 2 = 41. Total number of MSIs required at the BSC = 41 +15 = 56
PSI requirements

The required PXP/PSI pairs are 8, as because EGPRS is enabled, the TDM_TS_Blocks for every PSI is set to 9 (Refer to KSW/DSW2 planning actions in Chapter 6). That means 9x32=288 TDM HW timeslots are needed for every PSI.
KSW/DSW2 requirements

Determine the number of KSWs/DSW2s (N) required (enhanced capacity is enabled): N=(G*n)+(Rgdpxcdr*16)+(Regdp*96)+(Rgdp2*24)+(M*64)+(Rpsi*t)/2040

68P02900W21-S 01 Feb 2007 9-97

Planning example for DTM Feature

Chapter 9: Planning exercises

Where

Is

G n RGDP2 Rpsi t N

the number of GPROCs. 16 or 32 (16 in this example). N/A in this example (RXCDR case). M = the number of MSIs. the number of PSIs. the TDM HW timeslots of PSI (TDM_TS_Blocks *32) [19*32 + 56*64+ 8*(9*32)]/2040 = 3.2 ~ 4

Each DSW2 provides 2040 TDM timeslots in enhanced capacity mode. Hence, 4 non-redundant DSW2s are required for this configuration. For redundancy, 4 additional DSW2s are required. Thus, total DSW2s required (with redundancy) = 4 + 4 = 8.
BSU shelves

Each BSU shelf can support up to 12 MSI cards or 4 PSI cards and 8 MSI cards. A total of 56 MSI cards and 8 PSI cards are required, based on the previous calculation. The total number of BSU shelves required is: Maximum (56/8, 8/4, (56+8)/12) = 7. However, as verification , when TDM_Ts_Blocks is 9 for every PSI, there is over capacity for some extension or non-extension shelf. Therefore, the number of BSU shelves required to accommodate all the hardware needed for this configuration is NBSU = 8. Total GPROCs = 19 and total MSIs = 56, PSIs= 8 split between 8 BSU shelves:
Table 9-21 BSU shelves BSU1 BSU2 BSU3 BSU4 BSU5 BSU6 BSU7 BSU8

GPROCs MSI card PSI cards

3 8 1

3 8 1

3 8 1

2 8 1

2 8 1

2 8 1

2 8 1

2 8 1

Ensure that the following is true for each shelf: when enhanced capacity mode is enabled (non-extension shelf) (G*n)+(Rgdpxcdr*16)+(Regdp*96)+(Rgdp2*24)+(M*64)+(Rpsi* t)<=1016 That is, (3*32)+ (8*64) + (9*32) <=1016 when enhanced capacity mode is enabled (extension shelf) (G*n)+(Rgdpxcdr*16)+(Regdp*96)+(Rgdp2*24)+(M*64)+(Rpsi* t)<=1024 That is, (3*32) + (8*64) + 1*9*32 <=1024 or (2*32+8*64+9*32<1024)

68P02900W21-S 9-98 01 Feb 2007

System Information: BSS Equipment Planning

Planning example for DTM Feature

KSWX/DSWX requirements

KSWXs/DSWXs should be considered for this example as the configuration needs more than one shelf. The KSWX/DSWX extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in the multishelf configuration. The KSWX/DSWX can be used in expansion, remote and local modes. We need 8 BSU shelves with 4 master/redundant DSW2s, which implies that 4 expansion shelves are required. The number of KSWXs/DSWXs required (NKX) is the sum of KSWXDSWXE, KSWX/DSWXR, and KSWX/DSWXL. NKX = NKXE + NKXR + NKXL NKXE = K*(K-1) = 4 *3 = 12 (K is the number of non-redundant KSWs). NKXR = SE = 4 (SE is the number of extension shelves). NKXL = K + SE = 8 NK X = 12 + 4 + 8 = 24 The number of KSWXs/DSWXs required = 24
GCLK requirements

The generic clock generates all the timing reference signals required by a BSU. One GLCK is required at each BSC. The number of GCLKs required (with redundancy) = 2
CLKX requirements

Provides expansion of GCLK timing to more than one BSU. Number of CLKXs required is given by: NCLKX = Roundup (E/6) * (1 + RF)
Where Is

E RF NCLKX = Roundup (8/6)* (1+1)

the number of expansion/extension shelves. the redundancy factor.

The number of CLKXs required (with redundancy) = 4.

LANX requirements

NLANX=NBSU * (1 + RF) Where, RF it the redundancy factor. NLANX = 8*(1+1) Total number of LANXs required (with redundancy) = 16
PIX requirements

PIX provides eight inputs and four outputs for site alarms. PIX <= Number of BSUs = 8
Line interfaces

Number of PT43s = Number of PSIs = 8 Minimum number of T43s = Roundup (MSIs/3) = 19

68P02900W21-S 01 Feb 2007 9-99

Planning example for DTM Feature

Chapter 9: Planning exercises

Digital power supply requirements

The number of PSUs required is given by: PSUs = NBSU * (2 + RF) One redundant PSU is required for each BSU shelf, hence the total number of PSUs required is: PSUs = 8 * (2+1) = 24 The total number of PSUs required is 24
Non volatile memory (NVM) board for BSC (optional)

NVM = 0 or 1 An NVM board is required in this example, so NVM = 1.

68P02900W21-S 9-100 01 Feb 2007

Chapter 10 Location area planning

This section provides a description of location area planning with an example. Each operator should undertake this exercise to optimize the network configurations based on the paging load on the BSC. The topics described here are as follows.
Location area planning considerations Location area planning calculations

68P02900W21-S 01 Feb 2007 10-1

Location area planning considerations

Chapter 10: Location area planning

Location area planning considerations

Before the GSR4 BSS software release, the traffic handled by the BSC was limited by the number of BTSs and carriers that could be handled by the BSC. Increasing BSC capacities have an impact on some of the call model parameters, especially the paging load on the BSC. Since an MS is paged in a location area, paging rate depends on the number and size of BSCs in that location area. If there are too many BSCs in a location area, each with large number of BTS sites and high traffic handling capacity, it results in high paging load on each of the BSCs in that location area. This leads to more hardware (LCF GPROCs) having to be equipped on each BSC. Increasing the number of location areas increases the number of location updates on the cells bordering the location area. Provision more SDCCHs for this increased signaling on the border cells. Fewer channels are available for traffic. A well-planned network should have similar paging loads in each location area. A small paging load suggests that the location area is too small and could be combined with neighboring location areas, minimizing location update activity, and reducing use of SDCCH resources. A paging load too close to the theoretical maximum paging load (calculated using the number of PCHs used and if mobile is paged using IMSI or TMSI) would suggest that the location area is too large and should be split into multiple location areas, to avoid paging overload and the need for extra hardware. This exercise should be undertaken by each operator to optimize the network configurations based on the paging load on the BSC. This topic is explained further, with an example, in the following sections.

68P02900W21-S 10-2 01 Feb 2007

System Information: BSS Equipment Planning

Location area planning calculations

Location area planning calculations

Example procedure
Assume a network with four BSCs under a location area (refer to Figure 10-1) each with call model parameters as shown in Table 10-1.
Table 10-1 Example of values for the parameters for location area planning

Parameter

Value

Call duration, T Number of SMSs per call, S Number of location updates per call (nonborder) IMSI detaches per call, Id Location update factor Number of handovers per call, H Number of intra-BSC handovers to all handovers, i MTL link utilization RSL link utilization CCCH utilization Probability of blocking TCH PB-TCH Probability of blocking SDCCH PB-SDCCH Probability of blocking on A-interface Paging repetition Ratio of incoming calls and SMSs to the total calls and SMSs

96 s 2 2 0.2 (type 2) 2 + 0.5*0.2 = 2.1 1.32 0.6 20% 25% 33% < 2% < 1%
< 1%

1.2 0.50

Further assume that each of the BSC handles about 1200 Erlangs (48 sites with 2/2/2 configurations and 2 sites with omni 2 configuration) of traffic.

68P02900W21-S 01 Feb 2007 10-3

Location area planning calculations

Chapter 10: Location area planning

Figure 10-1 Four BSCs in one LAC

MSC

LAC=1

BSC

BSC

BSC

BSC

The paging rate in the location area can be calculated using the following formula:

P = paging repetition % of inco min g calls and SMS total calls and SMS in the LA per sec ond
= 1.2 * 0.50 (4*1200) / 96 * (1+2) = 90 pages per second Now, calculate the number of GPROC LCF-RSLs required with this paging load using the formula detailed in Chapter 6. (2044 * (1 + 0.35*2 + 0.34*1.32 * (1 0.4*0.6) + 0.32*2.1)) / (19.6 * 96) + (0.00075*90 + 0.004) * 50 + 146/120 = 7.74 The number of GPROC2s per BSC required for RSL is 8. Since most of the cells in the BSC are non-border cells, the location updates per cell is around 2. Based on this figure, calculate the number of SDCCHs required for each cell. From Erlang B tables, the number of Erlangs supported by 16 TCHs (2 carrier cell) with GOS of 2% is 9.83 Erlangs.

call e / T
Use the formulae provided in Chapter 3 for control channel calculations as follows: Call arrival rate: call = e/T = 9.83 / 96 = 0.1024 Ratio of SMSs to calls: S = S * e/T = 2 * 9.83 / 96 = 0.2048 Ratio of location updates to calls: LU = L * e/T = 2.1 * 9.83/96 = 0.215 The average number of SDCCHs, NSDCCH is given by: NSDCCH = call * TC + LU * (TL + Tg) + S * (TS + Tg) = 0.1024 * 5 + 0.215 * (4 + 4) + 0.2048 * (6 + 4) = 4.28

68P02900W21-S 10-4 01 Feb 2007

System Information: BSS Equipment Planning

Location area planning calculations

The number of SDCCHs to support an average number of busy SDCCHs of 4.28, with less that 1% blocking as determined by use of Erlang B tables, is 10. Hence, the number of timeslots required to carry SDCCH signaling traffic is 2 with each timeslot offering 8 SDCCHs. The number of PCHs to support GSM CS paging only, is given by (assuming IMSI paging): NPCH_GSM = PGSM / (NPages/Block * 4.25) = 90 / (2*4.25) = 10.59 = 11 This means that it is likely that a maximum of 2 additional CCCH timeslots (or a minimum of 1) are required to support this level of paging. Now, use the same call model parameters and divide the location area so that each location area contains two BSCs (refer to Figure 10-2). Dividing the location area into two location areas increase the location updates on the border cells. Assume that 25% of the cells under a BSC become border cells (a conservative estimate) and the number of location updates per call goes up to 6 on cells on the location area border. The average number of location updates per call for the BSC would approximately be equal to 3 (0.25*6 + 0.75*2).
Figure 10-2 Four BSCs divided into two LACs
MSC

LAC = 1

LAC = 2

BSC

BSC

BSC

BSC

Location update factor: L = 3 + 0.5 * 0.2 = 4 Since the location area now has two BSCs, the paging rate is given by: Paging Rate = 1.2 * 0.5 * (2*1200) / 96 * (1+2) = 45 pages / second The number of GPROC LCFs required for RSL (using the formula) = 4.70 = 5 (2044 * (1 + 0.35*2 + 0.34*1.32 * (1 0.4*0.6) + 0.32*3.1)) / (19.6 * 96) + (0.00075*45 + 0.004) * 50 + 146/120 = 6.399 = 7 GPROC2 RSL LCFs This simple expedient of reducing the number of BSCs in a LA has reduced the required number of GPROC2 RSL-LCFs by 1 per BSC, and therefore 4 GPROC2s for the whole LA of 4 BSCs.

68P02900W21-S 01 Feb 2007 10-5

Location area planning calculations

Chapter 10: Location area planning

Call arrival rate: call = e/T = 9.83 / 96 = 0.1024 Ratio of SMSs to calls: S = S * e/T = 2 * 9.83 / 96 = 0.2048 Ratio of location updates to calls: LU = L * e/T = 3.1 * 9.83/96 = 0.317 The average number of SDCCHs for border cells, NSDCCH is given by: NSDCCH = call * TC + LU * (TL + Tg) + LU * (TS + Tg) = 0.1024 * 5 + 0.317 * (4 + 4) + 0.2048 * (6 + 4) = 5.096 The number of SDCCHs to support an average number of busy SDCCHs of 5.096 with less than 1% blocking as determined by use of Erlang B tables, is 11. Hence, the number of timeslots required to carry SDCCH signaling traffic is 2, with each timeslot offering 8 SDCCHs. The number of PCHs to support GSM CS paging only, is given by (assuming IMSI paging): NPCH_GSM = PGSM / (NPages/Block * 4.25) = 45 / (2*4.25) = 5.29 = 6 This means that a maximum of 1 additional CCCH timeslot (or a minimum of 0) is required to support this level of paging. This result shows that with the same number of timeslots for SDCCHs for this example, in addition to reduced timeslots of CCCH (PCH), savings on equipment could be achieved by the simple expedient of decreasing the number of BSCs per LA. The increase in SDCCHs due to increased LA signaling is compensated by the decrease in PCHs. If the network planner divides the location area such that not too much traffic crosses the border of the location area (resulting in a lower number of location updates), even fewer resources are required of the air interface for location update signaling.

68P02900W21-S 10-6 01 Feb 2007

Chapter 11 Call model parameters

The derivation of call model parameter values from the GSM network statistics collected at the OMC-R are described in this chapter. Most of the calculations used for equipment planning use the standard call model parameters. Each network behaves in a unique way. Hence, the operators must compute their own set of call model parameter values for a network based on the performance statistics collected at the OMCR. This helps to optimize the configurations on a network. All the statistics used for determining the call model parameters must be collected during the busy hours and must be averaged over a reasonable period of time (three months or more). The call model parameters calculated should be averaged over the entire network or at the BSC level for equipment dimensioning purposes. This helps in averaging out the load from the network entities. The topic described here is Deriving call model parameters from network statistics.

68P02900W21-S 01 Feb 2007 11-1

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

Deriving call model parameters from network statistics

Standard call model parameters
Table 11-1 lists the standard call model parameters. Table 11-1 Typical parameters for BTS call planning Busy hour peak signaling traffic model Parameter reference

Call duration Ratio of SMSs per call Number of handovers per call (Refer to NOTE) Ratio of location updates to calls: non-border location area Ratio of location updates to calls: border location area Ratio of IMSI detaches to calls Location update factor: non-border location area (Refer to NOTE) Location update factor: border location area (Refer to NOTE) GSM circuit-switched paging rate in pages per second Ratio of intra-BSC handovers to all handovers (Refer to NOTE) Ratio of LCSs per call Mobile terminated LCS ratio Mobile originated LCS ratio Percent link utilization (MSC to BSS) Percent link utilization (BSC to BTS) Percent link utilization (BSC to RXCDR) Percent link utilization (BSC to SMLC) Percent link utilization (BSC to PCU Percent link utilization (BSS to SGSN Percent CCCH utilization

T = 90 seconds S=2 H = 1.32 l = 2I = 2 l = 2I = 7 I = 0.2 L = 2L = 2.1 L = 2L = 7.1

PGSM = 60 i = 0.6 Lcs = 0.1 LRMT = 0.95 LRMO = 0.05 U(MSC - BSS) = 0.20 U(BSC - BTS) = 0.25 UBSC-RXCDR = 0.40 UBSC-SMLC = 0.40 UBSC-PCU = 0.25 UGBL = 0.40 UCCCH = 0.33
Continued

68P02900W21-S 11-2 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

Table 11-1 Typical parameters for BTS call planning (Continued) Busy hour peak signaling traffic model Parameter reference

Block Rate for TCHs Block Rate for MSC-BSS trunks Number of cells per BTS Average SMS message size (payload only) Number of BSCs per location area Busy Hour Call Attempts per sub/BH XBL (enhanced auto connect) parameters Number of XBL messages per new call Number of XBL messages per hr <-> fr handover Length of an average XBL message, in bytes Number of hr <-> fr handovers per call GPRS parameters GPRS Average packet size (bytes) GPRS Traffic per sub/BH (kbytes/hr) Uplink GPRS Traffic per sub/BH (kbytes/hr) Downlink Average sessions per subscriber (per BH) Average SMS message size (payload only) PS attach/detach rate (per sub/BH) PDP context activation/deactivation (per sub/BH) Routing area update GPRS paging rate in pages per second Coding scheme rates (CS1 to CS4) at the RLC/MAC layer

PB-TCHs = 2% PB-Trunks = 1% CBTS = 3 SMSSIZE = 100 bytes BSCLA = 1 BHCAsub = 1.8 MNEWCALL = 1 MHANDOVER = 1 LXBL = 50 Hhr-fr = 1 PKSIZE = 336.65 ULRATE = 34.14 DLRATE = 127.81 Avg_Sessions_per_sub = 0.64 SMSSIZE = 100 bytes PSATT/DETACH = 0.5 PDPACT/DEACT = 0.4 RAU = 1.4 PGPRS = 25.91 CS1 = 9.2 kbit/s CS2 = 13.6 kbit/s CS3 = 15.8 kbit/s CS4 = 21.8 kbit/s
Continued

68P02900W21-S 01 Feb 2007 11-3

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

Table 11-1 Typical parameters for BTS call planning (Continued) Busy hour peak signaling traffic model Parameter reference

Coding scheme usage (CS1 to CS4) at a BLER of 10%

CS1_usage_UL = CS1_usage_DL = 20% CS2_usage_UL = CS2_usage_DL = 45% CS3_usage_UL = CS3_usage_DL = 25% CS4_usage_UL = CS4_usage_DL = 10% CSuse_GPRS = 50% CellUpdate = 0.33 PKULSIZE = 134.39 PKDLSIZE = 562.99 ULRATE = 34.14 DLRATE = 127.81 Avg_Sessions_per_sub = 0.64 PSATT/DETACH = 0.5 PDPACT/DEACT = 0.4 RAU = 1.4 PGPRS = 25.91 MCS1 = 10.55 kbit/s MCS2 = 12.95 kbit/s MCS3 = 16.55 kbit/s MCS4 = 19.35 kbit/s MCS5 = 23.90 kbit/s MCS6 = 29.60 kbit/s MCS7 = 31.10 kbit/s MCS8 = 46.90 kbit/s MCS9 = 61.30 kbit/s
Continued

Percentage GPRS coding scheme usage in total traffic (Refer to NOTE) Cell updates (per sub/BH)
EGPRS parameters

EGPRS Average packet size (bytes) - Uplink EGPRS Average packet size (bytes) Downlink EGPRS Traffic per sub/BH (kbytes/hr) Uplink EGPRS Traffic per sub/BH (kbytes/hr) Downlink Average sessions per subscriber (per BH) PS attach/detach rate (per sub/BH) PDP context activation/deactivation (per sub/BH) Routing area update GPRS paging rate in pages per second Coding scheme rates (MCS1 to MCS9) at the RLC/MAC layer

68P02900W21-S 11-4 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

Table 11-1 Typical parameters for BTS call planning (Continued) Busy hour peak signaling traffic model Parameter reference

MCS1_usage_UL = MCS1_usage_DL = 10% MCS2_usage_UL = MCS2_usage_DL = 8% MCS3_usage_UL = MCS3_usage_DL = 33% MCS4_usage_UL = MCS4_usage_DL = 1% Coding scheme usage (MCS1 to MCS9) at a BLER of 20% MCS5_usage_UL = MCS5_usage_DL = 21% MCS6_usage_UL = MCS6_usage_DL = 15% MCS7_usage_UL = MCS7_usage_DL = 5% MCS8_usage_UL = MCS8_usage_DL = 3% MCS9_usage_UL = MCS9_usage_DL = 4% Percentage EGPRS coding scheme usage in total traffic (Refer to NOTE) Average packet size for GPRS and EGPRS traffic mix (bytes) Uplink (Refer to NOTE) Average packet size for GPRS and EGPRS traffic mix (bytes) Downlink (Refer to NOTE)
DTM parameters

CSuse_EGPRS = 50% PKULSIZE = 134.39

PKDLSIZE = 562.99

Percentage of DTM mobiles DTM mode scaling factor (Refer to NOTE) QoS parameters Average GBR for service mix (kbit/s) Uplink Average GBR for service mix (kbit/s) Downlink Peak GBR for service mix (kbit/s) - Uplink Peak GBR for service mix (kbit/s) Downlink

MSDTM = 30% DTMfactor =30% GBRAVG_UL = 3.80 GBRAVG_DL = 5.60 GBRPEAK_UL = 9.65 GBRPEAK_UL = 12.70

68P02900W21-S 01 Feb 2007 11-5

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

The handovers include 2G-3G handovers. L is a function of I. It depends on the following message sequences used for IMSI detach: short message sequence (type 1) and long message sequence (type 2) and whether short message sequence (type 1) or long message sequence (type 2) is used for IMSI detach. Typically = 0 (disabled), but when it is enabled:
o o

Type 1: L = I + 0.2 * I Type 2: L = I + 0.5 * I

The percentages represent the split of the traffic for GPRS and EGPRS traffic mix, which is network dependent. The percentages can be used to determine the average traffic per sub/BH for a GPRS and EGPRS traffic mix as follows: Traffic per sub/BH for GPRS and EGPRS mix (kbytes/hr) = (Percentage GPRS coding scheme usage in total traffic * GPRS Traffic per sub/BH) + (Percentage EGPRS coding scheme usage in total traffic * EGPRS Traffic per sub/BH) The average packet sizes for a GPRS and EGPRS traffic mix are based on the GPRS and EGPRS percentage splits defined for this model. The DTM scaling factor represents the likelihood that a DTM subscriber overlaps a CS call and a PS session.

Call duration (T)

Average call duration for a network can be derived from the statistics BUSY_TCH_MEAN and TOTAL_CALLS using the following formula:

T=

i =1 N i =1

BUSY_TCH_MEAN * stat_interval_in_sec

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION )

Where

Is

N BUSY_TCH_MEAN

number of cells under the BSC. average number of busy TCHs in the cell. It is updated each time an allocation or de-allocation of a TCH occurs. It provides a mean value indicating the average number of TCHs in use. The time recorded for a TCH in use includes the guard time (T3111), which is the time allowed between ending a call and starting another call.
Continued

68P02900W21-S 11-6 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

Where

Is

TOTAL_CALLS

number of circuit-oriented calls that originate in the cell. It is pegged only once per connection at the time of the first successful TCH assignment procedure. Subsequent channel changes are not counted. total number of assignments that were redirected to another cell, due to redirected retry handover procedure, multiband band re-assignment procedure, or handover during assignment procedure. interval in which statistics are collected. It is 3600 if the statistic interval is one hour and 1800 if the statistic interval is 30 minutes.

ASSIGNMENT_REDIRECTION

stat_interval_in_sec

Call duration (T) in the formula is calculated for one cell and should be calculated as an average of call durations of all the BSCs in the network.

Ratio of SMSs per call (S)

The number of SMSs per call can be calculated using the SMS related statistics parameters in the following formula:

S=

(SMS_INIT_ON_SDCCH+ SMS_INIT_ON_TCH )
i =1

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION )
i =1

Where

Is

N SMS_INIT_ON_SDCCH SMS_INIT_ON_TCH TOTAL_CALLS

number of cells under the BSC. number of times an SMS transaction occurs on a SDCCH. number of times an SMS transaction occurs on a TCH. number of circuit-oriented calls that originate in the cell. It is pegged only once per connection at the time of the first successful TCH assignment procedure. Subsequent channel changes are not counted. total number of assignments that were redirected to another cell, due to redirected retry handover procedure, multiband band re-assignment procedure, or handover during assignment procedure.

ASSIGNMENT_REDIRECTION

68P02900W21-S 01 Feb 2007 11-7

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

The ratio of SMSs per call must be averaged over all the BSCs in the network.

Ratio of handovers per call (H)

Handovers can be inter-BSS, intra-BSS or intra-cell. Therefore, the number of handovers per call can be calculated using the following formula:

H=

(out_inter_bss_req_to_msc + out_intra_bss_ho_atmp + intra_cell_ho_atmp)

i =1

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION )
i =1

Where

Is

N out_inter_bss_req_to_msc out_intra_bss_ho_atmpt

number of cells under the BSC. number of outgoing inter-BSS handover requests to the MSC. number of times the assignment command is sent to an MS to initiate an outgoing intraBSS handover attempt. number of times an assignment command is sent to an MS, to initiate an intra-cell handover attempt. number of circuit-oriented calls that originate in the cell. It is pegged only once per connection at the time of the first successful TCH assignment procedure. Subsequent channel changes are not counted. total number of assignments that were redirected to another cell, due to redirected retry handover procedure, multiband band re-assignment procedure, or handover during assignment procedure.

intra_cell_ho_atmpt

TOTAL_CALLS

ASSIGNMENT_REDIRECTION

H should be averaged over all the BSCs in the network.

The TOTAL_CALLS parameter is the count of the total circuit-switched calls in a cell. It should be summed for all the cells in the BSC, when used in the formula.

68P02900W21-S 11-8 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

Ratio of intra BSS handovers to all handovers (i)

Using the statistics previously detailed, this ratio can be calculated for a cell as follows:

i=

(out_intra_bss_ho_atmpt + intra_call_ho_atmpt)
i =1

out_inter_bss_req_to_msc + out_intra_bss_ho_atmpt + intra_cell_ho_atmpt

i =1

Where

Is

number of cells under the BSC.

i should be averaged over all the cells in the network.

Ratio of location updates per call (I)

The ratio of location updates per call, for a cell, can be calculated using the following formula:

I=

OK_ACC_PROC[location_update]
i =1

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION )
i =1

Where

Is

N OK_ACC_PROC[location_update] TOTAL_CALLS

number of cells under the BSC. counts the number of MS requests for location updates. number of circuit-oriented calls that originate in the cell. It is pegged only once per connection at the time of the first successful TCH assignment procedure. Subsequent channel changes are not counted. counts the total number of assignments that were redirected to another cell, due to redirected retry handover procedure, multiband band re-assignment procedure, or handover during assignment procedure.

ASSIGNMENT_REDIRECTION

The ratio I should be averaged over all the BSCs in the network.

68P02900W21-S 01 Feb 2007 11-9

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

Ratio of IMSI detaches per call (I)

IMSI detaches is 0 if disabled. If enabled, it is calculated per cell as follows:

I=

(OK_ACC_PROC[imsi_detach]) (TOTAL_CALLS + ASSIGNMENT_REDIRECTION )

i =1 N i =1

Where

Is

N OK_ACC_PROC[imsi_detach] TOTAL_CALLS

the number of cells under the BSC. counts the number of MS requests for IMSI detach. the number of circuit-oriented calls that originate in the cell. It is pegged only once per connection at the time of the first successful TCH assignment procedure. Subsequent channel changes are not counted. counts the total number of assignments that were redirected to another cell, due to redirected retry handover procedure, multiband band re-assignment procedure, or handover during assignment procedure.

ASSIGNMENT_REDIRECTION

The ratio I should be averaged over all the BSCs in the network.

Location update factor (L)

The location update factor is calculated using the ration of location updates per call (l) and the ratio of IMSI detaches per call (I). For networks with IMSI detach disabled, the location update factor equals the ratio of location updates per call (l). If IMSI detach is enabled, L is calculated as follows depending on whether short message sequence (type 1) or long message sequence (type 2) is used: L = l (IMSI detach disabled, that is, I = 0) L = l + 0.2* I (type 1) L = l + 0.5* I (type 2)

IMSI detach types indicate the way the MSC clears the connection with the BSS after receiving the IMSI detach. When using IMSI detach type 1, the MSC clears the SCCP connection, a clearing procedure that involves only one uplink (average size of 42 bytes) and one downlink message (average size of 30 bytes). When using IMSI detach type 2, the MSC sends the CLEAR COMMAND and the BSS sends CLEAR COMPLETE, which involves three uplink (average size of 26 bytes) and three downlink messages (average size of 30 bytes). A location update procedure itself takes five downlink messages (average size of 30 bytes) and six uplink messages (average size of 26 bytes).

68P02900W21-S 11-10 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

Hence, an IMSI detach (type1) takes a total of 2/11 (approximately 0.2) of the total number of messages as a location update and an IMSI detach (type 2) takes 6/11 (approximately 0.5) of the messages of a location update.

Paging rate (PGSM)

PAGE_REQ_FROM_MSC counts the number of paging messages received by the BSS from the MSC during the statistics time interval. The paging message is then sent to the BSS in an attempt to locate a particular MS. Each message refers only to one MS. The BSS in turn transmits a paging message over the PCH, which may include identities for more than one MS (two MSs if paged using IMSI and four if using TMSI).

An MS is paged in a location area, which encompasses multiple BSCs. It is also possible to have multiple location areas within a BSC. The paging rate, therefore, is a summation of the paging messages sent to each location area in a BSC, averaged over the interval period. Since PAGE_REQ_FROM_MSC is kept on a per cell basis, the value of this counter for any cell in that location area, for a given statistics interval, denotes the pages in the location area during that statistics interval.

GSM

(PAGE_REQ_FROM_MSC )
i =1

stat_interval_in_seconds_ith_location_area_in_bsc
Is

Where

PAGE_REQ_FROM_MSC

number of paging messages received from the MSC by the BSS. This statistic is pegged when a paging message is received pertaining to the cell in which the MS is paged.

Pages per call (PPC)

Pages per call for a BSC can be calculated as:

PC

(PAGE_REQ_F
i =1

ROM_MSC

)
ON

(TOTAL_CALL
i =1

S + ASSIGNMENT

_REDIRECTI

Where
N

Is

number of cells under the BSC.

Alternatively, pages per call can be calculated using the formula:

PC

GSM

(T/N

68P02900W21-S 01 Feb 2007 11-11

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

Where
N T

Is

number of MSC-BSC trunks. call duration, in seconds.

Or:

PC

GSM

(T/e

)
Is

Where
e

BSC Erlang.

Percent link utilization MSC to BSS [U(MSC BSS)]

The percent link utilization MSC to BSS on the uplink and downlink can be calculated using the following formulae:

U(MSC BSS) =

(MTP_MSU_TX * 6) + MTP_SIF_SIO_TX + (SIB_TX * 7 )

MTP_LINK_INS * MTL_Rate * 8

U(MSC BSS) =

(MTP_MSU_RX * 6) + MTP_SIF_SIO_RX + (SIB_RX * 7 )

MTP_LINK_INS * MTL_Rate * 8
Is

Where

MTP_MSU_RX MTP_MSU_TX MTP_SIF_SIO_ MTP_SIF_SIO_ SIB_RX SIB_TX MTP_LINK_INS MTL_Rate

number of MSUs received over a link. number of MSUs transmitted on a link. number of SIFs and SIOs received over a link. number of SIFs and SIOs transmitted over a link. number of SIB LSSU messages received over a link. number of SIB LSSU messages transmitted over a link. length of time a signaling link is in service in milliseconds. number of DS0 channels on E1 that are equipped as MTL. For example, MTL_Rate=1 means only one DS0 channel is equipped as MTL, so the bandwidth of MTL is 1*64 kbit/s=6 4kbit/s. If MTL_Rate=31, it means the whole span of E1 is equipped as MTL.

68P02900W21-S 11-12 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

Percent link utilization BSC to BTS [U(BSC BTS)]

The percent link utilization BSC to BTS on the uplink and downlink for 64 kbit/s RSLs can be calculated using the following formulae:

U(BSC BTS) =
U(BSC BTS) =

RSL_TX_OCT ETS * 100% RSL_LINK_INS * RSL_BANDWIDTH_FACTOR * 2

RSL_RX_OCT ETS * 100% RSL_LINK_INS * RSL_BANDWI DTH_FACTOR * 2
Is

Where

N LMTP_MSU_RX LMTP_MSU_TX LMTP_SIF_SIO_RX LMTP_SIF_SIO_TX LMTP_SIB_RX LMTP_SIB_TX LMTP_LINK_INS

number of LMTLs to the BSC. number of MSUs received over a link. number of MSUs transmitted on a link. number of SIFs and SIOs received over a link. number of SIFs and SIOs transmitted over a link. number of SIB LSSU messages received over a link. number of SIB LSSU messages transmitted over a link. length of time a signaling link is in service in milliseconds.

Blocking for TCHs (PB TCHs)

The TCH blocking rate is calculated using the following formula:

P B TCHs =

TCH_Q_REMO
i =1 i =1

ALLOC_TCH_ FAIL TCH_Q_REMO VED[assign ment_resou rce_req] VED[ho_req ] ALLOC_TCH + ALLOC_TCH_ FAIL N

TCH_Q_REMO
Is

VED[assign ment_resou rce_req]

TCH_Q_REMO VED[ho_req ]
number of cells under the BSC. number of times a TCH is unsuccessfully allocated in a cell for originations and hand ins. number of times a queued assignment request is allocated a TCH. number of times a queued handover request is allocated a TCH.
Continued

Where

N ALLOC_TCH_FAIL TCH_Q_REMOVED [assignment_resource_req] TCH_Q_REMOVED[ho_req]

68P02900W21-S 01 Feb 2007 11-13

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

Where

Is

TCH_Q_REMOVED[ho_req] ALLOC_TCH

number of times a queued handover request is allocated a TCH. number of times a TCH is successfully allocated in a call for call originations, hand ins.

GPRS CS1 uplink usage (CS1_usage_UL)

The coding scheme usage on the uplink for GPRS CS1 is calculated using the following formula:
UL_RADIO_B LKS_8PSK_1 _TS_CS_1 + UL_RADIO_B LKS_8PSK_2 _TS_CS_1 + UL_RADIO_B LKS_GMSK_1 _TS_CS_1 + UL_RADIO_B LKS_GMSK_2 _TS_CS_1 CS1_usage_ UL = UL_RADIO_B LKS_8PSK_1 _TS + UL_RADIO_B LKS_8PSK_2 _TS + UL_RADIO_B LKS_GMSK_1 _TS + UL_RADIO_B LKS_GMSK_2 _TS * 100

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_CS_1

number of radio blocks received in the UL for CS1 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for CS1 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for CS1 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of RLC radio blocks received in the UL for CS1 from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL.
Continued

UL_RADIO_BLKS_8PSK_2_TS_CS_1

UL_RADIO_BLKS_GMSK_1_TS_CS_ 1

UL_RADIO_BLKS_GMSK_2_TS_CS_ 1

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

68P02900W21-S 11-14 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

Where

Is

UL_RADIO_BLKS_GMSK_1_TS

number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_GMSK_2_TS

GPRS CS1 downlink usage (CS1_usage_DL)

The coding scheme usage on the downlink for GPRS CS1 is calculated using the following formula:

DL_RADIO_BLKS_1_TS_CS_1 + DL_RADIO_BLKS_2_TS_CS_1 + DL_RADIO_BLKS_3_TS_CS_1 + DL_RADIO_BLKS_4_TS_CS_1 * 100 CS1_usage_DL = DL_RADIO_B LKS_1_TS DL_RADIO_B LKS_2_TS + + DL_RADIO_BLKS_3_TS + DL_RADIO_BLKS_4_TS
Where Is

DL_RADIO_BLKS_1_TS_CS_1

number of radio blocks received in the DL for CS1 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for CS1 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for CS1 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for CS1 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_CS_1

DL_RADIO_BLKS_3_TS_CS_1

DL_RADIO_BLKS_4_TS_CS_1

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 01 Feb 2007 11-15

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

GPRS CS2 uplink usage (CS2_usage_UL)

The coding scheme usage on the uplink for GPRS CS2 can be calculated using the following formula:
UL_RADIO_BLKS_8PSK_1 _TS_CS_2 + UL_RADIO_BLKS_8PSK_2 _TS_CS_2 + UL_RADIO_BLKS_GMSK_1 _TS_CS_2 + UL_RADIO_BLKS_GMSK_2 _TS_CS_2 * 100 CS2_usage_ UL = UL_RADIO_BLKS_8PSK_1 _TS + UL_RADIO_BLKS_8PSK_2 _TS + UL_RADIO_BLKS_GMSK_1 _TS + UL_RADIO_BLKS_GMSK_2 _TS

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_CS_2

number of radio blocks received in the UL for CS2 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for CS2 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for CS2 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of RLC radio blocks received in the UL for CS2 from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_8PSK_2_TS_CS_2

UL_RADIO_BLKS_GMSK_1_TS_CS_2

UL_RADIO_BLKS_GMSK_2_TS_CS_2

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

UL_RADIO_BLKS_GMSK_1_TS

UL_RADIO_BLKS_GMSK_2_TS

68P02900W21-S 11-16 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

GPRS CS2 downlink usage (CS2_usage_DL)

The coding scheme usage on the downlink for GPRS CS2 is calculated using the following formula:

DL_RADIO_BLKS_1_TS_C S_2 + DL_RADIO_BLKS_2_TS_C S_2 + DL_RADIO_BLKS_3_TS_C S_2 + DL_RADIO_BLKS_4_TS_C S_2 * 100 CS2_usage_DL = DL_RADIO_BLKS_1_TS + DL_RADIO_BLKS_2_TS + DL_RADIO_BLKS_3_TS + DL_RADIO_BLKS_4_TS
Where Is

DL_RADIO_BLKS_1_TS_CS_2

number of radio blocks received in the DL for CS2 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for CS2 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for CS2 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for CS2 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_CS_2

DL_RADIO_BLKS_3_TS_CS_2

DL_RADIO_BLKS_4_TS_CS_2

DL_RADIO_BLKS_1_TS DL_RADIO_BLKS_2_TS DL_RADIO_BLKS_3_TS DL_RADIO_BLKS_4_TS

68P02900W21-S 01 Feb 2007 11-17

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

GPRS CS3 uplink usage (CS3_usage_UL)

The coding scheme usage on the uplink for GPRS CS3 is calculated using the following formula:
UL_RADIO_B LKS_8PSK_1 _TS_CS_3 + UL_RADIO_B LKS_8PSK_2 _TS_CS_3 + * 100 UL_RADIO_B LKS_GMSK_1 _TS_CS_3 + UL_RADIO_B LKS_GMSK_2 _TS_CS_3 CS3_usage_ UL = UL_RADIO_B LKS_8PSK_1 _TS + UL_RADIO_B LKS_8PSK_2 _TS + UL_RADIO_B LKS_GMSK_1 _TS + UL_RADIO_B LKS_GMSK_2 _TS

Where

Is

DL_RADIO_BLKS_1_TS_CS_3

number of radio blocks received in the DL for CS3 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for CS3 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for CS3 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for CS3 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_CS_3

DL_RADIO_BLKS_3_TS_CS_3

DL_RADIO_BLKS_4_TS_CS_3

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 11-18 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

GPRS CS4 uplink usage (CS4_usage_UL)

The coding scheme usage on the uplink for GPRS CS4 is calculated using the following formula:
UL_RADIO_BLKS_8PSK_1_TS_CS_4 + UL_RADIO_BLKS_8PSK_2_TS_CS_4 + UL_RADIO_BLKS_GMSK_1_TS_CS_4 + UL_RADIO_BLKS_GMSK_2_TS_CS_4 * 100 CS4_usage_UL = UL_RADIO_BLKS_8PSK_1_TS + UL_RADIO_BLKS_8PSK_2_TS + UL_RADIO_BLKS_GMSK_1_TS + UL_RADIO_BLKS_GMSK_2_TS

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_CS_4

number of radio blocks received in the UL for CS4 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for CS4 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for CS4 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of RLC radio blocks received in the UL for CS4 from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_8PSK_2_TS_CS_4

UL_RADIO_BLKS_GMSK_1_TS_CS_4

UL_RADIO_BLKS_GMSK_2_TS_CS_4

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

UL_RADIO_BLKS_GMSK_1_TS

UL_RADIO_BLKS_GMSK_2_TS

68P02900W21-S 01 Feb 2007 11-19

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

GPRS CS4 downlink usage (CS4_usage_DL)

The coding scheme usage on the downlink for GPRS CS4 is calculated using the following formula:

DL_RADIO_BLKS_1_TS_C S_4 + DL_RADIO_BLKS_2_TS_C S_4 + DL_RADIO_BLKS_3_TS_C S_4 + DL_RADIO_BLKS_4_TS_C S_4 *100 CS4_usage_DL = DL_RADIO_B LKS_1_TS DL_RADIO_B LKS_2_TS + + DL_RADIO_BLKS_3_TS + DL_RADIO_BLKS_4_TS
Where Is

DL_RADIO_BLKS_1_TS_CS_4

number of radio blocks received in the DL for CS4 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for CS4 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for CS4 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for CS4 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL

DL_RADIO_BLKS_2_TS_CS_4

DL_RADIO_BLKS_3_TS_CS_4

DL_RADIO_BLKS_4_TS_CS_4

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 11-20 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

EGPRS MCS1 uplink usage (MCS1_usage_UL)

The coding scheme usage on the uplink for EGPRS MCS1 is calculated using the following formula:
UL_RADIO_B LKS_8PSK_1 _TS_MCS_1 + UL_RADIO_B LKS_8PSK_2 _TS_MCS_1 + UL_RADIO_B LKS_GMSK_1 _TS_MCS_1 + UL_RADIO_B LKS_GMSK_2 _TS_MCS_1 MCS1_usage _UL = UL_RADIO_B LKS_8PSK_1 _TS + UL_RADIO_B LKS_8PSK_2 _TS + UL_RADIO_B LKS_GMSK_1 _TS + UL_RADIO_B LKS_GMSK_2 _TS * 100

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_MCS_1

number of radio blocks received in the UL for MCS1 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS1 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for MCS1 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS1 from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_8PSK_2_TS_MCS_1

UL_RADIO_BLKS_GMSK_1_TS_MCS_1

UL_RADIO_BLKS_GMSK_2_TS_MCS_1

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

UL_RADIO_BLKS_GMSK_1_TS

UL_RADIO_BLKS_GMSK_2_TS

68P02900W21-S 01 Feb 2007 11-21

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

EGPRS MCS1 downlink usage (MCS1_usage_DL)

The coding scheme usage on the downlink for EGPRS MCS1 is calculated using the following formula:
DL_RADIO_BLKS_1_TS_M CS_1 + DL_RADIO_BLKS_2_TS_M CS_1 + DL_RADIO_BLKS_3_TS_M CS_1 + DL_RADIO_BLKS_4_TS_M CS_1 * 100 MCS1_usage _DL = DL_RADIO_BLKS_1_TS + DL_RADIO_BLKS_2_TS + DL_RADIO_BLKS_3_TS + DL_RADIO_BLKS_4_TS

Where

Is

DL_RADIO_BLKS_1_TS_MCS_1

number of radio blocks received in the DL for MCS1 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for MCS1 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for MCS1 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for MCS1 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_MCS_1

DL_RADIO_BLKS_3_TS_MCS_1

DL_RADIO_BLKS_4_TS_MCS_1

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 11-22 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

EGPRS MCS2 uplink usage (MCS2_usage_UL)

The coding scheme usage on the uplink for EGPRS MCS2 is calculated using the following formula:
UL_RADIO_B LKS_8PSK_1 _TS_MCS_2 + UL_RADIO_B LKS_8PSK_2 _TS_MCS_2 + UL_RADIO_B LKS_GMSK_1 _TS_MCS_2 + UL_RADIO_B LKS_GMSK_2 _TS_MCS_2 MCS2_usage _UL = UL_RADIO_B LKS_8PSK_1 _TS + UL_RADIO_B LKS_8PSK_2 _TS + UL_RADIO_B LKS_GMSK_1 _TS + UL_RADIO_B LKS_GMSK_2 _TS * 100

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_MCS_2

number of radio blocks received in the UL for MCS2 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS2 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for MCS2 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS2 from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_8PSK_2_TS_MCS_2

UL_RADIO_BLKS_GMSK_1_TS_MCS_2

UL_RADIO_BLKS_GMSK_2_TS_MCS_2

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

UL_RADIO_BLKS_GMSK_1_TS

UL_RADIO_BLKS_GMSK_2_TS

68P02900W21-S 01 Feb 2007 11-23

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

EGPRS MCS2 downlink usage (MCS2_usage_DL)

The coding scheme usage on the downlink for EGPRS MCS2 is calculated using the following formula:

DL_RADIO_BLKS_1_TS_MCS_2 + DL_RADIO_BLKS_2_TS_MCS_2 + *100 DL_RADIO_BLKS_3_TS_MCS_2 + DL_RADIO_BLKS_4_TS_MCS_2 MCS2_usage_DL = DL_RADIO_BLKS_1_TS + DL_RADIO_BLKS_2_TS + DL_RADIO_BLKS_3_TS + DL_RADIO_BLKS_4_TS
Where Is

DL_RADIO_BLKS_1_TS_MCS_2

number of radio blocks received in the DL for MCS2 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for MCS2 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for MCS2 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for MCS2 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_MCS_2

DL_RADIO_BLKS_3_TS_MCS_2

DL_RADIO_BLKS_4_TS_MCS_2

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 11-24 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

EGPRS MCS3 uplink usage (MCS3_usage_UL)

The coding scheme usage on the uplink for EGPRS MCS3 is calculated using the following formula:
UL_RADIO_B LKS_8PSK_1 _TS_MCS_3 + UL_RADIO_B LKS_8PSK_2 _TS_MCS_3 + UL_RADIO_B LKS_GMSK_1 _TS_MCS_3 + UL_RADIO_B LKS_GMSK_2 _TS_MCS_3 MCS3_usage _UL = UL_RADIO_B LKS_8PSK_1 _TS + UL_RADIO_B LKS_8PSK_2 _TS + UL_RADIO_B LKS_GMSK_1 _TS + UL_RADIO_B LKS_GMSK_2 _TS * 100

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_MCS_3

number of radio blocks received in the UL for MCS3 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS3 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for MCS1 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS3 from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_8PSK_2_TS_MCS_3

UL_RADIO_BLKS_GMSK_1_TS_MCS_3

UL_RADIO_BLKS_GMSK_2_TS_MCS_3

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

UL_RADIO_BLKS_GMSK_1_TS

UL_RADIO_BLKS_GMSK_2_TS

68P02900W21-S 01 Feb 2007 11-25

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

EGPRS MCS3 downlink usage (MCS3_usage_DL)

The coding scheme usage on the downlink for EGPRS MCS3 is calculated using the following formula:

DL_RADIO_BLKS_1_TS_MCS_3 + DL_RADIO_BLKS_2_TS_MCS_3 + DL_RADIO_BLKS_3_TS_MCS_3 + DL_RADIO_BLKS_4_TS_MCS_3 *100 MCS3_usage_DL = DL_RADIO_BLKS_1_TS + DL_RADIO_BLKS_2_TS + DL_RADIO_BLKS_3_TS + DL_RADIO_BLKS_4_TS
Where Is

DL_RADIO_BLKS_1_TS_MCS_3

number of radio blocks received in the DL for MCS3 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for MCS3 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for MCS3 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for MCS3 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_MCS_3

DL_RADIO_BLKS_3_TS_MCS_3

DL_RADIO_BLKS_4_TS_MCS_3

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 11-26 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

EGPRS MCS4 uplink usage (MCS4_usage_UL)

The coding scheme usage on the uplink for EGPRS MCS4 is calculated using the following formula:
UL_RADIO_B LKS_8PSK_1 _TS_MCS_4 + UL_RADIO_B LKS_8PSK_2 _TS_MCS_4 + UL_RADIO_B LKS_GMSK_1 _TS_MCS_4 + UL_RADIO_B LKS_GMSK_2 _TS_MCS_4 MCS4_usage _UL = UL_RADIO_B LKS_8PSK_1 _TS + UL_RADIO_B LKS_8PSK_2 _TS + UL_RADIO_B LKS_GMSK_1 _TS + UL_RADIO_B LKS_GMSK_2 _TS * 100

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_MCS_4

number of radio blocks received in the UL for MCS4 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS4 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for MCS4 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_8PSK_2_TS_MCS_4

UL_RADIO_BLKS_GMSK_1_TS_MCS_4

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

UL_RADIO_BLKS_GMSK_1_TS

UL_RADIO_BLKS_GMSK_2_TS

68P02900W21-S 01 Feb 2007 11-27

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

EGPRS MCS4 downlink usage (MCS4_usage_DL)

The coding scheme usage on the downlink for EGPRS MCS4 is calculated using the following formula:

DL_RADIO_BLKS_1_TS_M CS_4 + DL_RADIO_BLKS_2_TS_M CS_4 + * 100 DL_RADIO_BLKS_3_TS_M CS_4 + DL_RADIO_BLKS_4_TS_M CS_4 MCS4_usage _DL = DL_RADIO_BLKS_1_TS + DL_RADIO_BLKS_2_TS + DL_RADIO_BLKS_3_TS + DL_RADIO_BLKS_4_TS
Where Is

DL_RADIO_BLKS_1_TS_MCS_4

number of radio blocks received in the DL for MCS4 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for MCS4 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for MCS4 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for MCS4 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_MCS_4

DL_RADIO_BLKS_3_TS_MCS_4

DL_RADIO_BLKS_4_TS_MCS_4

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 11-28 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

EGPRS MCS5 uplink usage (MCS5_usage_UL)

The coding scheme usage on the uplink for EGPRS MCS5 is calculated using the following formula:
UL_RADIO_B LKS_8PSK_1 _TS_MCS_5 + UL_RADIO_B LKS_8PSK_2 _TS_MCS_5 + UL_RADIO_B LKS_GMSK_1 _TS_MCS_5 + UL_RADIO_B LKS_GMSK_2 _TS_MCS_5 MCS5_usage _UL = UL_RADIO_B LKS_8PSK_1 _TS + UL_RADIO_B LKS_8PSK_2 _TS + UL_RADIO_B LKS_GMSK_1 _TS + UL_RADIO_B LKS_GMSK_2 _TS * 100

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_MCS_5

number of radio blocks received in the UL for MCS5 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS5 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for MCS5 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS5 from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_8PSK_2_TS_MCS_5

UL_RADIO_BLKS_GMSK_1_TS_MCS_5

UL_RADIO_BLKS_GMSK_2_TS_MCS_5

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

UL_RADIO_BLKS_GMSK_1_TS

UL_RADIO_BLKS_GMSK_2_TS

68P02900W21-S 01 Feb 2007 11-29

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

EGPRS MCS5 downlink usage (MCS5_usage_DL)

The coding scheme usage on the downlink for EGPRS MCS5 is calculated using the following formula:
DL_RADIO_B LKS_1_TS_M CS_5 + DL_RADIO_B LKS_2_TS_M CS_5 + * 100 DL_RADIO_B LKS_3_TS_M CS_5 + DL_RADIO_B LKS_4_TS_M CS_5 MCS5_usage _DL = DL_RADIO_B LKS_1_TS + DL_RADIO_B LKS_2_TS + DL_RADIO_B LKS_3_TS + DL_RADIO_B LKS_4_TS

Where

Is

DL_RADIO_BLKS_1_TS_MCS_5

number of radio blocks received in the DL for MCS5 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for MCS5 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for MCS5 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for MCS5 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_MCS_5

DL_RADIO_BLKS_3_TS_MCS_5

DL_RADIO_BLKS_4_TS_MCS_5

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 11-30 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

EGPRS MCS6 uplink usage (MCS6_usage_UL)

The coding scheme usage on the uplink for EGPRS MCS6 is calculated using the following formula:
UL_RADIO_B LKS_8PSK_1 _TS_MCS_6 + UL_RADIO_B LKS_8PSK_2 _TS_MCS_6 + * 100 UL_RADIO_B LKS_GMSK_1 _TS_MCS_6 + UL_RADIO_B LKS_GMSK_2 _TS_MCS_6 MCS6_usage _UL = UL_RADIO_B LKS_8PSK_1 _TS + UL_RADIO_B LKS_8PSK_2 _TS + UL_RADIO_B LKS_GMSK_1 _TS + UL_RADIO_B LKS_GMSK_2 _TS

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_MCS_6

number of radio blocks received in the UL for MCS6 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS6 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for MCS6 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS6 from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_8PSK_2_TS_MCS_6

UL_RADIO_BLKS_GMSK_1_TS_MCS_6

UL_RADIO_BLKS_GMSK_2_TS_MCS_6

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

UL_RADIO_BLKS_GMSK_1_TS

UL_RADIO_BLKS_GMSK_2_TS

68P02900W21-S 01 Feb 2007 11-31

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

EGPRS MCS6 downlink usage (MCS6_usage_DL)

The coding scheme usage on the downlink for EGPRS MCS6 is calculated using the following formula:

DL_RADIO_BLKS_1_TS_MCS_6 + DL_RADIO_BLKS_2_TS_MCS_6 + *100 DL_RADIO_BLKS_3_TS_MCS_6 + DL_RADIO_BLKS_4_TS_MCS_6 MCS6_usage_DL = DL_RADIO_BLKS_1_TS + DL_RADIO_BLKS_2_TS + DL_RADIO_BLKS_3_TS + DL_RADIO_BLKS_4_TS
Where Is

DL_RADIO_BLKS_1_TS_MCS_6

number of radio blocks received in the DL for MCS6 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for MCS6 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for MCS6 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for MCS6 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_MCS_6

DL_RADIO_BLKS_3_TS_MCS_6

DL_RADIO_BLKS_4_TS_MCS_6

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 11-32 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

EGPRS MCS7 downlink usage (MCS7_usage_DL)

The coding scheme usage on the downlink for EGPRS MCS7 is calculated using the following formula:
DL_RADIO_B LKS_1_TS_M CS_7 + DL_RADIO_B LKS_2_TS_M CS_7 + DL_RADIO_B LKS_3_TS_M CS_7 + DL_RADIO_B LKS_4_TS_M CS_7 * 100 MCS7_usage _DL = DL_RADIO_B LKS_1_TS + DL_RADIO_B LKS_2_TS + DL_RADIO_B LKS_3_TS + DL_RADIO_B LKS_4_TS

Where

Is

DL_RADIO_BLKS_1_TS_MCS_7

number of radio blocks received in the DL for MCS7 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for MCS7 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for MCS7 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for MCS7 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_MCS_7

DL_RADIO_BLKS_3_TS_MCS_7

DL_RADIO_BLKS_4_TS_MCS_7

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 01 Feb 2007 11-33

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

EGPRS MCS8 uplink usage (MCS8_usage_UL)

The coding scheme usage on the uplink for EGPRS MCS8 is calculated using the following formula:
UL_RADIO_B LKS_8PSK_1 _TS_MCS_8 + UL_RADIO_B LKS_8PSK_2 _TS_MCS_8 + * 100 UL_RADIO_B LKS_GMSK_1 _TS_MCS_8 + UL_RADIO_B LKS_GMSK_2 _TS_MCS_8 MCS8_usage _UL = UL_RADIO_B LKS_8PSK_1 _TS + UL_RADIO_B LKS_8PSK_2 _TS + UL_RADIO_B LKS_GMSK_1 _TS + UL_RADIO_B LKS_GMSK_2 _TS

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_MCS_8

number of radio blocks received in the UL for MCS8 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS8 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for MCS8 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS8 from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_8PSK_2_TS_MCS_8

UL_RADIO_BLKS_GMSK_1_TS_MCS_8

UL_RADIO_BLKS_GMSK_2_TS_MCS_8

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

UL_RADIO_BLKS_GMSK_1_TS

UL_RADIO_BLKS_GMSK_2_TS

68P02900W21-S 11-34 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

EGPRS MCS8 downlink usage (MCS8_usage_DL)

The coding scheme usage on the downlink for EGPRS MCS8 is calculated using the following formula:
DL_RADIO_BLKS_1_TS_M CS_8 + DL_RADIO_BLKS_2_TS_M CS_8 + DL_RADIO_BLKS_3_TS_M CS_8 + DL_RADIO_BLKS_4_TS_M CS_8 * 100 MCS8_usage _DL = DL_RADIO_BLKS_1_TS + DL_RADIO_BLKS_2_TS + DL_RADIO_BLKS_3_TS + DL_RADIO_BLKS_4_TS

Where

Is

DL_RADIO_BLKS_1_TS_MCS_8

number of radio blocks received in the DL for MCS8 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for MCS8 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for MCS8 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for MCS8 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_MCS_8

DL_RADIO_BLKS_3_TS_MCS_8

DL_RADIO_BLKS_4_TS_MCS_8

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 01 Feb 2007 11-35

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

EGPRS MCS9 uplink usage (MCS9_usage_UL)

The coding scheme usage on the uplink for EGPRS MCS9 is calculated using the following formula:
UL_RADIO_B LKS_8PSK_1 _TS_MCS_9 + UL_RADIO_B LKS_8PSK_2 _TS_MCS_9 + * 100 UL_RADIO_B LKS_GMSK_1 _TS_MCS_9 + UL_RADIO_B LKS_GMSK_2 _TS_MCS_9 MCS9_usage _UL = UL_RADIO_B LKS_8PSK_1 _TS + UL_RADIO_B LKS_8PSK_2 _TS + UL_RADIO_B LKS_GMSK_1 _TS + UL_RADIO_B LKS_GMSK_2 _TS

Where

Is

UL_RADIO_BLKS_8PSK_1_TS_MCS_9

number of radio blocks received in the UL for MCS9 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS9 from MSs capable of 8PSK that support a maximum of 2 TS in the UL. number of radio blocks received in the UL for MCS9 from MSs capable of 8PSK that support a maximum of 1 TS in the UL. number of radio blocks received in the UL for MCS9 from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of 8PSK supporting a maximum of 2 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 1 TS in the UL. number of radio blocks received in the UL from MSs capable of GMSK supporting a maximum of 2 TS in the UL.

UL_RADIO_BLKS_8PSK_2_TS_MCS_9

UL_RADIO_BLKS_GMSK_1_TS_MCS_9

UL_RADIO_BLKS_GMSK_2_TS_MCS_9

UL_RADIO_BLKS_8PSK_1_TS

UL_RADIO_BLKS_8PSK_2_TS

UL_RADIO_BLKS_GMSK_1_TS

UL_RADIO_BLKS_GMSK_2_TS

68P02900W21-S 11-36 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

EGPRS MCS9 downlink usage (MCS9_usage_DL)

The coding scheme usage on the downlink for EGPRS MCS9 is calculated using the following formula:
DL_RADIO_BLKS_1_TS_M CS_9 + DL_RADIO_BLKS_2_TS_M CS_9 + DL_RADIO_BLKS_3_TS_M CS_9 + DL_RADIO_BLKS_4_TS_M CS_9 * 100 MCS9_usage _DL = DL_RADIO_BLKS_1_TS + DL_RADIO_BLKS_2_TS + DL_RADIO_BLKS_3_TS + DL_RADIO_BLKS_4_TS

Where

Is

DL_RADIO_BLKS_1_TS_MCS_9

number of radio blocks received in the DL for MCS9 from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL for MCS9 from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL for MCS9 from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL for MCS9 from MSs supporting a maximum of 4 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 1 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 2 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 3 TS in the DL. number of radio blocks received in the DL from MSs supporting a maximum of 4 TS in the DL.

DL_RADIO_BLKS_2_TS_MCS_9

DL_RADIO_BLKS_3_TS_MCS_9

DL_RADIO_BLKS_4_TS_MCS_9

DL_RADIO_BLKS_1_TS

DL_RADIO_BLKS_2_TS

DL_RADIO_BLKS_3_TS

DL_RADIO_BLKS_4_TS

68P02900W21-S 01 Feb 2007 11-37

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

Sample statistic calculations

Table 11-2 shows a sample of the statistics collected for one BTS in the BSC for a one hour interval. Table 11-2 Sample Statistics Statistic Parameter Cell 1 Cell 2 Cell 3

BUSY_TCH_MEAN
TOTAL_CALLS

9.25 571 0 0 0 531 512 0 746 28 43696 0

14.94 927 0 15 2 1214 747 0 1056 49 43696 0

24.12 1407 0 5 0 141 1844 0 268 76 43696 0

SMS_NO_BCAST_MSG SMS_INIT_ON_SD- CCH SMS_INIT_ON_TCH out_inter_bss_req_to_msc out_intra_bss_ho_atm intra_cell_ho_atmpt OK_ACC_PROC [location_update] OK_ACC_PROC [imsi_detach] PAGE_REQ_FROM_MSC ASSIGNMENT_REDIRECTION

Using the formulae detailed in the previous sections, call model parameters can be calculated as follows:

Call duration (T)

Call duration is given by:

T=

i =1 N i =1

BUSY_TCH_MEAN * stat_interval_in_sec

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION )

T = (9.25 + 14.94 + 24.12) 3600 / (521 + 927 + 1407) + 0 + 0 + 0

The average call duration for this BSC = 59.86. Likewise, call durations for all the cells in the BSC can be calculated. The call duration value used for dimensioning purposes should be the average of the call durations over all the BSCs in the network.

68P02900W21-S 11-38 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

Number of SMSs per call (S)

The number of SMSs per call is given by:

S=

(SMS_NO_BCAST_MSG + SMS_INIT_ON_SDCCH + SMS_INIT_ON_TCH )

i =1

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION )
i =1

S = [(0 + 0 + 0) + (0 + 15 + 2) + (0 + 5 + 0)] / (571 + 927 + 1407) = 0.075

Ratio of handovers per call (H)

The ratio of handovers per call is given by:

H=

(out_inter_bss_req_to_msc + out_intra_bss_ho_atmpt + intra_cell_ho_atmpt )

i +1

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION )
i =1

H = [(531 + 512 + 0) + (1214 + 747 + 0) + (141 + 1844 + 0)] / (571 + 927 + 1407 + 0 + 0 + 0) = 1.717

Ratio of intra-BSS handovers to all handovers (i)

Using the statistics previously detailed, this ratio can be calculated for a BSS as follows:

i=

(out_intra_bss_ho_atmpt + out_intra_cell_ho_atmp)
i =1

(out_inter_bss_req_to_msc + out_intra_bss_ho_atmpt + intra_cell_ho_atmpt )

i =1

[(512 + 0) + (747 + 0) + (1844 + 0)] / [(531 + 512 + 0) + (1214 + 747 + 0) + (141 + 1844 + 0)] = 0.562

68P02900W21-S 01 Feb 2007 11-39

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

Number of location updates per call (l)

Location updates per call can be calculated as:

I=

(OK_ACC_PROC[location_update])
i =1

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION )
i =1

I = (746 + 1056 + 268) / (571 + 927 + 1407) + 0 + 0 + 0 = 0.712

IMSI detaches per call (I)

The number of IMSI detaches per call is given by:

I=

(OK_ACC_PROC[imsi_det ach]) (TOTAL_CALLS + ASSIGNMENT_REDIRECTION )

i =1 N i =1

I = (28 + 49 + 76) / (571 + 927 + 1407 + 0 + 0 + 0) = 0.052

Location update factor (L)

The location update is given by:

L = l + 0.5 I L = 0.712 + 0.5 0.052 = 0.738

Paging Rate (PGSM) for a BSC

The paging rate for a BSC (with multiple location areas) can be calculated as:

= GSM

(PAGE_REQ_FROM_MSC )
stat_interval_in_seconds_ith_location_area

68P02900W21-S 11-40 01 Feb 2007

System Information: BSS Equipment Planning

Deriving call model parameters from network statistics

Since, in this case the BSC has only one location area, PGSM is given by:

GSM

= 43696/3600

= 12.13 pages

per second

All call model parameters should be calculated by taking an average over all the BSCs in the entire network. This example illustrates the computation of call model parameters from the network statistics obtained from the OMC-R. As previously mentioned, it is recommended that statistics collected at busy hours over a long period of time (a couple of months) are used for all calculation purposes.

68P02900W21-S 01 Feb 2007 11-41

Deriving call model parameters from network statistics

Chapter 11: Call model parameters

68P02900W21-S 11-42 01 Feb 2007

Chapter 12 Standard BSS and Horizon BTS configurations

This chapter provides the diagrams of the logical interconnections of the components in various standard BSS and Horizon BTS site configurations for macrocell and microcell systems. Older generation (M-Cell) BTS site/RF configurations are provided in Chapter 13 M-Cell BTS configurations. This chapter includes the following sections:
Standard configurations Typical BSS configurations Single cabinet BTS configurations Two cabinet BTS configurations Three cabinet BTS configurations Four cabinet BTS configurations Horizon macrocell RF configurations Microcell RF configurations Connecting Horizon II macro cabinets to Horizonmacro cabinets Connecting Horizon II macro cabinets to M-Cell6 cabinets

68P02900W21-S 01 Feb 2007 12-1

Standard configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Standard configurations
The examples shown here are with individual antennas for transmit and receive signals. Duplexers are required if individual antennas are not used. However, duplexers can result in performance degradation. For carrier redundancy, the RF carrier equipment must be duplicated for each BTS. The diagrams that follow are not intended to imply the maximum capacity nor a typical configuration using that specific equipment. Rather, they are meant to highlight the configurations that are within the constraints of the BSS architecture, and are feasible when the macrocell hardware is deployed in a digital equipment shelf controlled BTS. The diagrams also show possible cabinet boundaries. Cabinet designs, however, allow for some different arrangements of the same configuration. Rather than showing redundancy for all Horizon II macro/Horizonmacro BTS configurations, the control redundancy is depicted only for one Horizon II macro/Horizonmacro cabinet diagram (see Figure 12-4 and Figure 12-7).

68P02900W21-S 12-2 01 Feb 2007

System Information: BSS Equipment Planning

Typical BSS configurations

Typical BSS configurations

BSC with 24 BTSs
The digital module configuration for a BSC controlling 24 BTSs is shown in Figure 12-1.
Figure 12-1 BSC controlling 24 BTSs
DUAL IEEE LAN DUAL SERIAL BUS PIX BTC GPROC 0 LANX A GPROC 1 LANX B GPROC 2 GPROC 3 KSW A GCLK

BSU SHELF 1
DUAL MCAP BUS GCLK REDUND ANT A DUAL TDM HIGHWAY BUS B

RMT KSWX A

CLKX

LCL KSWX A

CLKX

LCL KSWX B

BTC

MSI 0

MSI 1

MSI 2

MSI 7

2 Mbit/s LINKS

BTS 1
FIBRE OPTIC LINKS

BTS 2

BTS 3

BTS 12

MSC/RXCDR
2.048 Mbit/s LINK INTERFACES FROM/TO MSC AND TO/FROM BTS SITES BTS 13 BTS 14 BTS15,16 2 Mbit/s LINKS BTS 23, 24

DUAL SERIAL BUS LCL KSWX A LCL KSWX B RMT KSWX B BTC MSI 0 MSI 1 MSI 2 MSI 6 A B DUAL TDM HIGHWAY BUS BTC GPROC 0 GPROC 1 LANX B GPROC 2 KSW B REDUNDANT

DUAL MCAP BUS

LANX A DUAL IEEE LAN

BSU SHELF 2 BSSC CABINET

68P02900W21-S 01 Feb 2007 12-3

Typical BSS configurations

Chapter 12: Standard BSS and Horizon BTS configurations

BSC with full redundancy

The digital module configuration for a fully redundant BSC controlling 34 BTSs is shown in Figure 12-2.
Figure 12-2 Fully redundant BSC controlling 34 BTSs
DUAL IEEE LAN DUAL SERIAL BUS PIX BTC GPROC 0 GPROC 1 GPROC 2 GPROC 3 KSW A B KSW GCLK A LANX A LANX B

BSU SHELF 1
DUAL MCAP BUS GCLK B A B

REDUNDANT DUAL TDM HIGHWAY BUS

EXP KSWX A

EXP KSWX B

CLKX

LCL KSWX A

CLKX

LCL KSWX B

BTC

MSI 0

MSI 1

MSI 2

MSI 9

2 Mbit/s LINKS

BTS 1

BTS 2

BTS 3

BTS 16,17

FIBRE OPTIC LINKS

MSC
2.048 Mbit/s LINK INTERFACES FROM/TO MSC AND TO/FROM BTS SITES BTS 18 BTS 19 BTS 20 BTS 33,34

2 Mbit/s LINKS

EXP KSW A

EXP KSWX B

LCL KSWX A

LCL KSWX B

BTC

MSI 0

MSI 1

MSI 2

MSI 9

DUAL TDM HIGHWAY BUS

A B

BTC

GPROC 0

GPROC 1

GPROC 2

GPROC 3

KSW A

KSW B REDUNDANT

DUAL MCAP BUS

DUAL SERIAL BUS DUAL IEEE LAN

LANX A

LANX B

BSU SHELF 2 BSSC CABINET

68P02900W21-S 12-4 01 Feb 2007

System Information: BSS Equipment Planning

Typical BSS configurations

Transcoder
The digital module configuration for a BSSC cabinet equipped to provide transcoding, is shown in Figure 12-3.
Figure 12-3 BSSC cabinet equipped to provide transcoding
DUAL IEEE 802.5 LAN DUAL SERIAL BUS BTC GPROC 0 GPROC 1 KSW A GCLK LANX A LANX B

RXU SHELF 1
DUAL MCAP BUS GCLK

REDUNDANT DUAL TDM HIGHWAY BUS

A B

RMT KSWX A

CLK X

LCL KSWX A

CLKX

LCL KSWX B

BTC

MSI 0

MSI 1

XCDR 0

XCDR 15

FIBRE OPTIC LINKS

2.048 Mbit/s LINK INTERFACES FROM/TO BSCS

2.048 Mbit/s LINK INTERFACES FROM/TO MSC

LCL KSWX A

LCL KSWX B

RMT KSWX B

BTC

MSI 0

MSI 1

XCDR 0

XCDR 15 A

DUAL TDM HIGHWAY BUS B BTC GPROC 0 GPROC 1 KSW B REDUNDANT LANX A LANX B

DUAL MCAP BUS

DUAL SERIAL BUS DUAL IEEE LAN

RXU SHELF 2 REMOTE TRANSCODER CABINET

68P02900W21-S 01 Feb 2007 12-5

Single cabinet BTS configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Single cabinet BTS configurations

Single cabinet Horizon II macro BTS
The configuration shown in Figure 12-4 is an example of a one-cabinet Horizon II macro. This configuration can support 6 carriers in single density mode or 12 carriers in double density mode.
Figure 12-4 Macrocell BTS with one Horizon II macro cabinet

INTEGRATED NIU HIISC (FOR REDUNDANCY)

INTEGRATED NIU HIISC

12 12

2 C T U 2 2

2 C T U 2 2

2 C T U 2 2

2 C T U 2 2

2 C T U 2 2

2 C T U 2 2

Horizon II macro CABINET

68P02900W21-S 12-6 01 Feb 2007

System Information: BSS Equipment Planning

Single cabinet BTS configurations

Single cabinet Horizon II mini BTS

The configuration shown in Figure 12-5 is an example of a one-cabinet Horizon II mini. This configuration can support a maximum of four carriers.
Figure 12-5 Macrocell BTS with one Horizon II mini cabinet

INTEGRATED NIU HIISC (FOR REDUNDANCY)

INTEGRATED NIU HIISC

4 4

2 C T U 2 2

2 C T U 2 2

Horizon II mini CABINET

68P02900W21-S 01 Feb 2007 12-7

Single cabinet BTS configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Single cabinet Horizon II micro BTS

The configuration shown in Figure 12-6 is an example of a one-cabinet Horizon II micro. This configuration can support a maximum of two carriers.
Figure 12-6 Macrocell BTS with one Horizon II micro cabinet

INTEGRATED NIU HIISC

2 2

2 C T U 2 2

Horizon II micro CABINET

68P02900W21-S 12-8 01 Feb 2007

System Information: BSS Equipment Planning

Single cabinet BTS configurations

Single cabinet Horizonmacro BTS

The configuration shown in Figure 12-7 is an example of a one-cabinet Horizonmacro. This configuration can support a maximum of six carriers.
Figure 12-7 Macrocell BTS with one Horizonmacro cabinet

DIGITAL EQUIPMENT SHELF

N I U N I U

MCUF

MCUF

(FOR REDUNDANCY)

12

12

C T U 2

C T U 2

C T U 2

C T U 2

C T U 2

C T U 2

Horizonmacro CABINET

If CTUs are replaced with CTU2s from the Horizon II macro, the master (and redundant) MCUF must have a 20 Mbyte PCMCIA card running the CSFP to accommodate the added memory requirements of the GSR6 (Horizon II) objects. In addition, the CTU2 can support only baseband hopping in single density mode when installed in Horizonmacro.

68P02900W21-S 01 Feb 2007 12-9

Two cabinet BTS configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Two cabinet BTS configurations

Two cabinet Horizon II macro BTS
The configuration shown in Figure 12-8 is an example of a two cabinet Horizon II macro. This configuration can support a maximum of 12 carriers in single density mode and 24 carriers in double density mode. The HIISC interfaces to the CTU2s in the second (slave) cabinet through site expansion boards in both cabinets (connected through fiber optic cables) and an XMUX replaces the HIISC in the second cabinet. The site expansion board is optional equipment in the master BTS and is required only when site expansion is required.
Figure 12-8 Macrocell BTS with two Horizon II macro cabinets

If a redundant HIISC is installed in the master cabinet, redundant site expansion boards must be installed in the master and slave cabinets and a redundant XMUX must be installed in each slave cabinet.

68P02900W21-S 12-10 01 Feb 2007

System Information: BSS Equipment Planning

Two cabinet BTS configurations

Two cabinet Horizon II mini BTS

The configuration shown in Figure 12-9 is an example of a two cabinet Horizon II mini. This configuration can support a maximum of four carriers in single density mode and eight carriers in double density mode. The HIISC interfaces to the CTU2s in the second (slave) cabinet through site expansion boards in both cabinets (connected through fiber optic cables) and an XMUX replaces the HIISC in the second cabinet. The site expansion board is optional equipment in the master BTS and is required only when site expansion is required.
Figure 12-9 Macrocell BTS with two Horizon II mini cabinets
Horizon II mini MASTER CABINET
INTEGRATED XMUX HIISC CONNECTION VIA BACKPLANE SITE EXPANSION BOARD

2 C T U 2

2 C T U 2

2 C T U 2

2 C T U 2

4 X M U X SITE EXPANSION BOARD

Horizon II mini SLAVE CABINET

68P02900W21-S 01 Feb 2007 12-11

Two cabinet BTS configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Two cabinet Horizonmacro BTS

The configuration shown in Figure 12-10 is an example of a two cabinet Horizonmacro. This configuration can support a maximum of 12 carriers. The MCUF interfaces to the CTUs in the second cabinet through a FMUX in the second cabinet.
Figure 12-10 Macrocell BTS with two Horizonmacro cabinets
N I U

DIGITAL EQUIPMENT SHELF

Horizonmacro CABINET

MCUF

12 2 2 2 2 2 2

C T U

C T U

C T U

C T U

C T U

C T U

12 C T U

DIGITAL EQUIPMENT SHELF

F M U X

C T U

C T U

C T U

C T U

C T U

HorizonmacroCABINET

If CTUs are replaced with CTU2s from the Horizon II macro, the master (and redundant) MCUF must have a 20 Mbyte PCMCIA card running the CSFP to accommodate the added memory requirements of the GSR6 (Horizon II) objects. In addition, the CTU2 can support only baseband hopping in single density mode when installed in Horizonmacro.

68P02900W21-S 12-12 01 Feb 2007

System Information: BSS Equipment Planning

Three cabinet BTS configurations

Three cabinet BTS configurations

Three cabinet Horizon II macro BTS
The configuration shown in Figure 12-11 is an example of a three cabinet Horizon II macro. Like a two cabinet configuration, the HIISC interfaces to the CTU2s in the slave cabinets through site expansion boards in all cabinets (connected through fiber optic cables) and an XMUX replaces the HIISC in each of the slave cabinets.
Figure 12-11 Macrocell BTS with three Horizon II macro cabinets

68P02900W21-S 01 Feb 2007 12-13

Three cabinet BTS configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Three cabinet Horizon II mini BTS

The configuration shown in Figure 12-12 is an example of a three cabinet Horizon II mini. Like a two cabinet configuration, the HIISC interfaces to the CTU2s in the slave cabinets through the site expansion boards in all cabinets (connected through fiber optic cables) and an XMUX replaces the HIISC in each of the slave cabinets.
Figure 12-12 Macrocell BTS with three Horizon II mini cabinets
Horizon II mini MASTER CABINET
INTEGRATED XMUX HIISC CONNECTION VIA BACKPLANE SITE EXPANSION BOARD

4 2 C T U 2 2 C T U 2 2

2 C T U 2

2 C T U 2

4 X M U X SITE EXPANSION BOARD

Horizon II mini SLAVE CABINET

2 C T U 2

2 C T U 2

4 X M U X SITE EXPANSION BOARD

Horizon II mini SLAVE CABINET

If a redundant HIISC is installed in the master cabinet, redundant site expansion boards must be installed in the master and slave cabinets and a redundant XMUX must be installed in each slave cabinet.

68P02900W21-S 12-14 01 Feb 2007

System Information: BSS Equipment Planning

Three cabinet BTS configurations

Three cabinet Horizon II micro BTS

The configuration shown in Figure 12-13 is an example of a three cabinet Horizon II micro. The HIISC interfaces to the CTU2s in the slave cabinets through the site expansion boards in all cabinets (connected using fiber optic cables) and an XMUX replaces the HIISC in each of the slave cabinets.
Figure 12-13 Macrocell BTS with three Horizon II micro cabinets
Horizon II micro MASTER CABINET
INTEGRATED XMUX HIISC CONNECTION VIA BACKPLANE SITE EXPANSION BOARD

2 2 C T U 2 2

2 C T U 2

2 X M U X SITE EXPANSION BOARD

Horizon II micro SLAVE CABINET

2 C T U 2

2 X M U X SITE EXPANSION BOARD

Horizon II micro SLAVE CABINET

If a redundant HIISC is installed in the master cabinet, redundant site expansion boards must be installed in the master and slave cabinets and a redundant XMUX must be installed in each slave cabinet.

68P02900W21-S 01 Feb 2007 12-15

Three cabinet BTS configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Three cabinet Horizonmacro BTS

The configuration shown in Figure 12-14 is an example of a three cabinet Horizonmacro. This configuration can support a maximum of 18 carriers. The MCUF interfaces to the CTUs in the other cabinets through the FMUXs.
Figure 12-14 Macrocell BTS with three Horizonmacro cabinets
N I U

DIGITAL EQUIPMENT SHELF

Horizonmacro CABINET

2 MCUF 2

12 2 2 2 2 2 2

C T U

C T U

C T U

C T U

C T U

C T U

Horizonmacro CABINET

12 C T U

DIGITAL EQUIPMENT SHELF

F M U X

C T U

C T U

C T U

C T U

C T U

Horizonmacro CABINET

12 C T U

DIGITAL EQUIPMENT SHELF

F M U X

C T U

C T U

C T U

C T U

C T U

If CTUs are replaced with CTU2s from the Horizon II macro, the master (and redundant) MCUF must have a 20 Mbyte PCMCIA card running the CSFP to accommodate the added memory requirements of the GSR6 (Horizon II) objects. In addition, the CTU2 can support only baseband hopping in single density mode when installed in Horizonmacro.

68P02900W21-S 12-16 01 Feb 2007

System Information: BSS Equipment Planning

Four cabinet BTS configurations

Four cabinet BTS configurations

Four cabinet Horizon II macro BTS
The configuration shown in Figure 12-15 is an example of a four cabinet Horizon II macro. Like a two cabinet configuration, the HIISC interfaces to the CTU2s in the slave cabinets through the site expansion boards in all cabinets (connected through fiber optic cables) and an XMUX replaces the HIISC in each of the slave cabinets.
Figure 12-15 Macrocell BTS with four Horizon II macro cabinets
Horizon II macro MASTER CABINET
CONNECTION VIA BACKPLANE INTEGRATED XMUX HIISC SITE EXPANSION BOARD

12 2 C T U 2 2 C T U 2 2 C T U 2 2 C T U 2 2 C T U 2 2 C T U 2 2 2

2 C T U 2

2 C T U 2

2 C T U 2

2 C T U 2

2 C T U 2

2 C T U 2

12 X M U X SITE EXPANSION BOARD

Horizon II macro SLAVE CABINET

2 C T U 2 2 C T U 2 2 C T U 2 2 C T U 2 2 C T U 2 2 C T U 2 12 X M U X SITE EXPANSION BOARD

Horizon II macro SLAVE CABINET

2 C T U 2 2 C T U 2 2 C T U 2 2 C T U 2 2 C T U 2 2 C T U 2 12 X M U X SITE EXPANSION BOARD

Horizon II macro SLAVE CABINET

68P02900W21-S 01 Feb 2007 12-17

Four cabinet BTS configurations

Chapter 12: Standard BSS and Horizon BTS configurations

If a redundant HIISC is installed in the master cabinet, redundant site expansion boards must be installed in the master and slave cabinets and a redundant XMUX must be installed in each slave cabinet.

Four cabinet Horizon II mini BTS

The configuration shown in Figure 12-16 is an example of a four cabinet Horizon II mini. Like a two cabinet configuration, the HIISC interfaces to the CTU2s in the slave cabinets through site expansion boards in all cabinets (connected through fiber optic cables) and an XMUX replaces the HIISC in each of the slave cabinets.
Figure 12-16 Macrocell BTS with four Horizon II mini cabinets
Horizon II mini MASTER CABINET
CONNECTION VIA BACKPLANE INTEGRATED XMUX HIISC SITE EXPANSION BOARD

4 2 C T U 2 2 C T U 2 2 2

2 C T U 2

2 C T U 2

4 X M U X SITE EXPANSION BOARD

Horizon II mini SLAVE CABINET

2 C T U 2 2 C T U 2 4 X M U X SITE EXPANSION BOARD

Horizon II mini SLAVE CABINET

2 C T U 2 2 C T U 2 4 X M U X SITE EXPANSION BOARD

Horizon II mini SLAVE CABINET

68P02900W21-S 12-18 01 Feb 2007

System Information: BSS Equipment Planning

Four cabinet BTS configurations

Four cabinet Horizonmacro BTS

The configuration shown in Figure 12-17 is an example of a four cabinet Horizonmacro. This configuration supports 24 carriers. The MCUF interfaces to the CTUs in the other cabinets through the FMUXs. An additional FMUX is required in the main cabinet to support the third extension cabinet.
Figure 12-17 Macrocell BTS with four Horizonmacro cabinets
N I U

DIGITAL EQUIPMENT SHELF

F M U X

Horizonmacro CABINET
2

12 MCUF

2 2

12 2 2 2 2 2 2

C T U

C T U

C T U

C T U

C T U

C T U

Horizonmacro CABINET

12 C T U

DIGITAL EQUIPMENT SHELF

F M U X

C T U

C T U

C T U

C T U

C T U

Horizonmacro CABINET

12 C T U

DIGITAL EQUIPMENT SHELF

F M U X

C T U

C T U

C T U

C T U

C T U

Horizonmacro CABINET

12 C T U

DIGITAL EQUIPMENT SHELF

F M U X

C T U

C T U

C T U

C T U

C T U

If CTUs are replaced with CTU2s from the Horizon II macro, the master (and redundant) MCUF must have a 20 Mbyte PCMCIA card running the CSFP to accommodate the added memory requirements of the GSR6 (Horizon II) objects. In addition, the CTU2 can support only baseband hopping in single density mode when installed in Horizonmacro.

68P02900W21-S 01 Feb 2007 12-19

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Horizon macrocell RF configurations

Overview of configuration diagrams
The Horizon macrocell BTS cabinets/enclosures are explained in the following order: Horizon II macro cabinets Horizon II mini cabinets Horizonmacro cabinets Horizoncompact2 enclosures

Horizon II macro cabinets

The following series of Horizon II macro RF configuration diagrams show the ways of connecting together Horizon II macro SURF2 and Tx blocks to meet different operational requirements. The series of diagrams is by no means exhaustive, and numerous alternative configurations can be adopted to achieve the same aim. Each diagram (except for the PGSM diagrams) is applicable to either EGSM900 or DCS1800 operation, though the SURF2 module illustrated is an 1800 MHz SURF2. For EGSM900 operation, a 900 MHz SURF2 is required. Two SURF2s can be installed in the Horizon II macro cabinet (see Figure 12-24), in which case they can be of the same type (900 and 1800 SURF2s) or can be mixed in the same cabinet when the dual band adaptor is installed.

{30828} The configurations for both CTU2 and CTU2D are identical.

Rules for equipping Horizon II macro cabinets

The following rules apply when equipping any Horizon II macro cabinet for the configurations shown in Figure 12-18 to Figure 12-24. In these figures, the configurations are also applicable to CTU2D where ever CTU2 can be used. {30828}The following conditions are applicable for CTU2D also: A maximum of six CTU2s can be accommodated. All CTU2s in the cabinet must operate at the same frequency (either 900 MHz or 1800 MHz). When operating in double density mode, both CTU2 carriers must be in the same sector. {30828} In addition, the dri_density parameter should be set to two and with CTU2D in ASYM mode, dri_density value should be three to achieve EDGE capability. When operating in Dual band mode within a single cabinet, up to three CTU2s per band can be accommodated. An external equipment cabinet is not required.

68P02900W21-S 12-20 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800] 4 or 8 carrier omni with HCUs and air combining

Figure 12-18 shows a single cabinet, four CTU2 configuration with duplexers, hybrid combiner units and air combining. Table 12-1 provides a summary of the equipment required for this configuration. Figure 12-18 [DCS1800] 4 or 8 carrier omni with HCUs and air combining
Tx/Rx Tx/Rx ANTENNA ANTENNA

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
HCU

4
RX

2
HCU

1
RX

ANT

ANT

BLANK

DUP

BLANK

DUP

EMPTY

CTU2

CTU2

EMPTY

CTU2

CTU2

Horizon II macro CABINET

Table 12-1 Equipment required for 4 or 8 carrier omni with HCUs and air combining Quantity Equipment

2 1 4 1 2 2

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP HCU

68P02900W21-S 01 Feb 2007 12-21

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800] 6 or 12 carrier omni with DHUs

Figure 12-19 shows a single cabinet, six CTU2 configuration with duplexers and dual hybrid combiner units. Table 12-2 provides a summary of the equipment required for this configuration. Figure 12-19 [DCS1800] 6 or 12 carrier omni with DHUs
Tx/Rx Tx/Rx ANTENNA ANTENNA

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
DHU

4
RX

2
DHU

1
RX

ANT

ANT

BLANK

DUP

BLANK

DUP

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

Horizon II macro CABINET

Table 12-2 Equipment required for 6 or 12 carrier omni with DHUs Quantity Equipment

2 1 6 1 2 2

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP DHU

68P02900W21-S 12-22 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800] 2 sector 3/3 or 6/6 with DHUs

Figure 12-20 shows a single cabinet, six CTU2 configuration with duplexers and dual hybrid combiner units. Table 12-3 provides a summary of the equipment required for this configuration. Figure 12-20 [DCS1800] 2 sector 3/3 or 6/6 with DHUs
SECTOR 2
Tx/Rx ANTENNA Rx ANTENNA

SECTOR 1
Rx ANTENNA Tx/Rx ANTENNA

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
DHU

4
RX

2
DHU

1
RX

ANT

ANT

BLANK

DUP

BLANK

DUP

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

Horizon II macro CABINET

Table 12-3 Equipment required for 2 sector 3/3 or 6/6 with DHUs Quantity Equipment

4 1 6 1 2 2

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP DHU

68P02900W21-S 01 Feb 2007 12-23

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining
Figure 12-21 shows a two cabinet configuration, each cabinet containing four CTU2s with duplexers, hybrid combiner units and air combining. Table 12-4 provides a summary of the equipment required for this configuration. Figure 12-21 [DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining
SECTOR 2
Tx/Rx ANTENNAS

SECTOR 1
Tx/Rx ANTENNAS

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
HCU

4
RX

2
HCU

1
RX

5
HCU

4
RX

2
HCU

1
RX

ANT

ANT

ANT

ANT

BLANK

DUP

BLANK

DUP

BLANK

DUP

BLANK

DUP

EMPTY

CTU2

CTU2

EMPTY

CTU2

CTU2

EMPTY

CTU2

CTU2

EMPTY

CTU2

CTU2

3
XMUX

0
HIISC

Horizon II macro SLAVE CABINET

SITE EXPANSION BOARD

Horizon II macro MASTER CABINET Fibre Optic Link (x2)

SITE EXPANSION BOARD

Table 12-4 Equipment required for 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining Quantity Equipment

4 2 8 2 4 4

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP HCU

68P02900W21-S 12-24 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs

Figure 12-22 shows a single cabinet, six CTU2 configuration with duplexers and hybrid combiner units. Table 12-5 provides a summary of the equipment required for this configuration. Figure 12-22 [DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs
SECTOR 3
Tx/Rx Rx ANTENNA ANTENNA

SECTOR 2
Rx Tx/Rx ANTENNA ANTENNA

SECTOR 1
Rx Tx/Rx ANTENNA ANTENNA

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
HCU
RX

4
HCU

3
RX

2
HCU

1
RX

ANT

ANT

ANT

DUP

DUP

DUP

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

Horizon II macro CABINET

Table 12-5 Equipment required for 3 sector 2/2/2 or 4/4/4 with HCUs Quantity Equipment

6 1 6 1 3 3

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP HCU

68P02900W21-S 01 Feb 2007 12-25

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800] 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining
Figure 12-23 shows a two cabinet configuration, each cabinet containing six CTU2s with duplexers, hybrid combiner units and air combining. Table 12-6 provides a summary of the equipment required for this configuration. Figure 12-23 [DCS1800] 2 cab, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining
SECTOR 3
Tx/Rx ANTENNAS

SECTOR 1
Tx/Rx ANTENNAS

SECTOR 2
Tx/Rx ANTENNAS

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
HCU
RX

4
HCU

3
RX

2
HCU

1
RX

0
HCU

5
RX

4
HCU

3
RX

2
HCU

1
RX

ANT

ANT

ANT

ANT

ANT

ANT

DUP

DUP

DUP

DUP

DUP

DUP

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

3
XMUX

0
HIISC

SITE EXPANSION BOARD

Horizon II macro SLAVE CABINET

Horizon II macro MASTER CABINET

Fibre Optic Link (x2)

SITE EXPANSION BOARD

Table 12-6 Equipment required for 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining Quantity Equipment

6 2 12 2 6 6

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP HCU

68P02900W21-S 12-26 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800] 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity

Figure 12-24 shows a single cabinet, six CTU2 configuration for 4 branch Rx diversity with duplexers, hybrid combiner units and air combining. Table 12-7 provides a summary of the equipment required for this configuration. Figure 12-24 [DCS1800] 3 sector 2/2/2 or 4/4/4 with air combining and 4 branch Rx diversity
SECTOR 3 SECTOR 2 SECTOR 1

RX 2C SURF2 RX 2B SURF2

RX 1C

RX 0C

EXP EXP RX C D 0D

RX 1D

RX 2D

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
RX RX

4
RX

3
RX

2
RX

1
RX

ANT

ANT

ANT

ANT

ANT

ANT

DUP

DUP

DUP

DUP

DUP

DUP

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

Horizon II macro CABINET

Table 12-7 Equipment required for 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity Quantity Equipment

12 1 6 2 6

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP

68P02900W21-S 01 Feb 2007 12-27

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800/GSM900] 3 sector 2/2/2 and 2/2/2

Figure 12-25 shows a single cabinet, three CTU2 (1800 MHz) and three CTU2 (900 MHz) configuration with duplexers and air combining. This is a typical Horizon II Macro dual band configuration, which supports both 900 MHz and 1800 MHz within the same cabinet. Table 12-8 provides a summary of the equipment required for this configuration. Refer to the notes on page 12-29 for required equipment units and software load. Figure 12-25 [DCS1800/GSM900] 3 sector 2/2/2 and 2/2/2 with air combining
900 900 900 SECTOR 2 SECTOR 1 SECTOR 0
A B A B A B

1800 1800 1800 SECTOR 2 SECTOR 1 SECTOR 0

A B A B A B

A2

B0

900 SURF2

B2

A0

1800 SURF2

DB Adaptor

900

900

900

1800

1800

1800

DUP

DUP

DUP

DUP

DUP

DUP

CTU2 900

CTU2 900

CTU2 900

CTU2 1800

CTU2 1800

CTU2 1800

A B

A B

A B

A B

A B

A B

Horizon II macro CABINET

68P02900W21-S 12-28 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

Table 12-8 Equipment required for 3 sector 2/2/2 and 2/2/2 Quantity Equipment

12 1 1 3 3 1 1 3 3 3

Antennas Horizon II macro cabinet Dual band adaptor 1800 MHz CTU2 900 MHz CTU2/ SURF2
Receiver

1800 MHz SURF2 900 MHz SURF2

Transmitter/receiver

1800 MHz DUP 900 MHz DUP

Power supply

Power supply

A fourth power supply is recommended - contact your Motorola Local Office for full details.

The HII Dual band adaptor allows a single Horizon II cabinet to be used for both 1800 MHz and 900 MHz frequency bands in a GSM/GPRS network controlled by one BSC. This implementation places an adaptor module at the bottom of the SURF bay. Each of the 900 MHz and 1800 MHz SURF2 modules is plugged into this adaptor module. The adaptor module interconnects the outputs of the SURF2 modules to the appropriate CTU2 slot in a hardwired fashion. Each CTU2 uses its primary receive inputs. A maximum of three CTU2 per frequency band can be configured with the dual band adaptor in a Horizon II cabinet. The rear SURF2 controls CTU2 radio slots from 3 to 5; the front SURF2 controls CTU2 radio slots from 0 to 2.

68P02900W21-S 01 Feb 2007 12-29

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Horizon II macro cabinets with PGSM Duplexer

The following series of Horizon II macro RF configuration diagrams suggests the ways of connecting together Horizon II macro cabinets with PGSM Duplexers. The series of diagrams is by no means exhaustive, and numerous alternative configurations can be adopted to achieve the same aim.

Rules for equipping Horizon II macro cabinets with PGSM Duplexer

The following rules apply when equipping any Horizon II macro cabinet for the configurations shown in Figure 12-26 to Figure 12-31: A maximum of six CTU2s can be accommodated. All CTU2s in the cabinet must operate at the same frequency (PGSM 900 MHz). When operating in double density mode, both CTU2 carriers must be in the same sector. A PGSM duplexer is required for both main and diversity receiver branches.

[PGSM] 4 or 8 carrier omni with HCUs and air combining

Figure 12-26 shows a single cabinet, four CTU2 configuration with duplexers, hybrid combiner units and air combining. Table 12-9 provides a summary of the equipment required for this configuration. Figure 12-26 [PGSM900] 4 or 8 carrier omni with HCUs and air combining
Tx/Rx Tx/Rx ANTENNA ANTENNA

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
HCU

4
RX

2
HCU

1
RX

ANT

ANT

BLANK

DUP

BLANK

DUP

EMPTY

CTU2

CTU2

EMPTY

CTU2

CTU2

Horizon II macro CABINET

68P02900W21-S 12-30 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

Table 12-9 Equipment required for 4 or 8 carrier omni with HCUs and air combining Quantity Equipment

2 1 4 1 2 2

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP HCU

[PGSM900] 6 or 12 carrier omni with DHUs

Figure 12-27 shows a single cabinet, six CTU2 configuration with duplexers and dual hybrid combiner units. Table 12-10 provides a summary of the equipment required for this configuration. Figure 12-27 [PGSM900] 6 or 12 carrier omni with DHUs
Tx/Rx Tx/Rx ANTENNA ANTENNA

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
DHU

4
RX

2
DHU

1
RX

ANT

ANT

BLANK

DUP

BLANK

DUP

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

Horizon II macro CABINET

68P02900W21-S 01 Feb 2007 12-31

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Table 12-10 Equipment required for 6 or 12 carrier omni with DHUs Quantity Equipment

2 1 6 1 2 2

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP DHU

[PGSM900] 2 sector 3/3 or 6/6 with HCUs

Figure 12-28 shows a single cabinet, six CTU2 configuration with duplexers and hybrid combiner units. Table 12-11 provides a summary of the equipment required for this configuration. Figure 12-28 [PGSM900] 2 sector 3/3 or 6/6 with HCUs
SECTOR 2
Tx/Rx ANTENNA Rx ANTENNA

SECTOR 1
Rx ANTENNA Tx/Rx ANTENNA

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
HCU
RX

4
RX

3
RX

2
HCU

1
RX

ANT

ANT

ANT

ANT

DUP

DUP

DUP

DUP

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

0
Image008.eps

Horizon II macro CABINET

68P02900W21-S 12-32 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

Table 12-11 Equipment required for 2 sector 3/3 or 6/6 with HCUs Quantity Equipment

4 1 6 1 4 2

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP HCU

[PGSM900] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining
Figure 12-29 shows a two cabinet configuration, each cabinet containing four CTU2s with duplexers, hybrid combiner units and air combining. Table 12-12 provides a summary of the equipment required for this configuration. Figure 12-29 [PGSM900] 2 cab, 2 sector 4/4 or 8/8 with HCUs and air combining

68P02900W21-S 01 Feb 2007 12-33

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Table 12-12 Equipment required for 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining Quantity Equipment

4 2 8 2 4 4

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP HCU

[PGSM900] 3 sector 2/2/2 or 4/4/4

Figure 12-30 shows a single cabinet, six CTU2 configuration with duplexers. Table 12-13 provides a summary of the equipment required for this configuration. Figure 12-30 [PGSM900] 3 sector 2/2/2 or 4/4/4
SECTOR 3
Tx/Rx ANTENNA Rx ANTENNA

SECTOR 2
Tx/Rx ANTENNA Rx ANTENNA

SECTOR 1
Rx ANTENNA Tx/Rx ANTENNA

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

5
RX RX

4
RX

3
RX

2
RX

1
RX

ANT

ANT

ANT

ANT

ANT

ANT

DUP

DUP

DUP

DUP

DUP

DUP

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

0
Image012.eps

Horizon II macro CABINET

68P02900W21-S 12-34 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

Table 12-13 Equipment required for 3 sector 2/2/2 or 4/4/4 Quantity Equipment

6 1 6 1 6

Antennas Horizon II macro cabinet CTU2

Receiver

SURF2
Transmitter/receiver

DUP

[PGSM900] 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining
Figure 12-31 shows a two cabinet configuration, each cabinet containing six CTU2s with duplexers, hybrid combiner units and air combining. Table 12-14 provides a summary of the equipment required for this configuration. Figure 12-31 [PGSM900] 2 cab, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining4

68P02900W21-S 01 Feb 2007 12-35

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Table 12-14 Equipment required for 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining Quantity Equipment

6 12 2 6 6

Antennas
Horizon II macro cabinet

CTU2
Receiver

SURF2
Transmitter/receiver

DUP HCU

Horizon II mini cabinets

The following series of Horizon II mini RF configuration diagrams suggests the ways of connecting together Horizon II mini MiniSURF2 and Tx blocks to meet different operational requirements. The series of diagrams is by no means exhaustive, and numerous alternative configurations can be adopted to achieve the same aim. Each diagram is applicable to either EGSM900 or DCS1800 operation, though the MiniSURF2 module illustrated is an 1800 MHz SURF2. For EGSM900 operation, a 900 MHz MiniSURF2 is required. For PGSM900 operation, only certain configurations are noted: Omni-2 (with diversity), Omni-4 (with diversity) and Sector 2/2 (no diversity).

Rules for equipping Horizon II mini cabinets

The following rules apply when equipping any Horizon II mini cabinet for the configurations shown in Figure 12-32 to Figure 12-38: A maximum of two CTU2s can be accommodated. Both CTU2s in the cabinet must operate at the same frequency (either 900 MHz or 1800 MHz). When operating in double density mode, both CTU2 carriers must be in the same sector. An external equipment cabinet is not required.

68P02900W21-S 12-36 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800/EGSM900/PGSM900] High power Omni-1, standard power Omni2

Figure 12-32 shows a single cabinet, one CTU2, high power (HP) Omni-1/standard power (SP) Omni-2 configuration. Table 12-15 provides a summary of the equipment required for this configuration. Figure 12-32 DCS1800/EGSM900 HP Omni-1/SP Omni-2
Sector 1: 2 carriers

ALARM

HIISC

1A 1B 0B BATTERY
T43/BIB

0A

FRONT

REAR

Horizon II mini CABINET

Table 12-15 Equipment required for HP Omni-1/SP Omni-2 Quantity Equipment

6 1 1 1

Antenna Horizon II mini cabinet CTU2

Receiver

MiniSURF2

68P02900W21-S 01 Feb 2007 12-37

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800/EGSM900/PGSM900] High power Omni-2, standard power Omni4

Figure 12-33 shows a single cabinet, two CTU2 high power (HP) Omni-2/standard power (SP) Omni-4 configuration. Table 12-16 provides a summary of the equipment required for this configuration. Figure 12-33 DCS1800/EGSM900 HP Omni-2/SP Omni-4
Sector 1: 4 carriers

ALARM

HIISC

1A 1B 0B BATTERY T43/BIB 0A

FRONT

REAR

Horizon II mini CABINET

Table 12-16 Equipment required for HP Omni-1/SP Omni-2 Quantity Equipment

2 1 2 1

Antenna Horizon II mini cabinet CTU2

Receiver

MiniSURF2

68P02900W21-S 12-38 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800/EGSM900] High power Bowtie-2, standard power Bowtie-4

Figure 12-34 shows a single cabinet, two CTU2 High Power (HP) Bowtie-2/Standard Power (SP) Bowtie4 configuration. Table 12-17 provides a summary of the equipment required for this configuration. Figure 12-34 DCS1800/EGSM900 HP Bowtie-2/SP Bowtie-4
Antenna 1: 4 carriers Antenna 2: 4 carriers

Hybrid

ALARM

HIISC

1A 1B 0B BATTERY 0A

T43/BIB

FRONT

REAR

Horizon II mini CABINET

Table 12-17 Equipment required for HP Omni-1/SP Omni-2 Quantity Equipment

2 1 2 1 1

Antenna Horizon II mini cabinet CTU2 Bowtie-4 configuration

Receiver

MiniSURF2
Transmitter/receiver

Hybrid combiner

68P02900W21-S 01 Feb 2007 12-39

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800/EGSM900] High power 2 sector 1/1, standard power 2 sector 2/2

Figure 12-35 shows a single cabinet, two CTU2, HP 2 sector 1/1/SP 2 sector 2/2 configuration. Table 12-18 provides a summary of the equipment required for this configuration. Figure 12-35 DCS1800/EGSM900 HP 2 sector 1/1/SP 2 sector 2/2
Sector 1: 2 carriers Sector 2: 2 carriers

ALARM

HIISC

0A 1A 1B 0B

BATTERY
T43/BIB

FRONT

REAR

Horizon II mini CABINET

Table 12-18 Equipment required for HP 2 sector 1/1/SP 2 sector 2/2 Quantity Equipment

4 1 2 1

Antenna Horizon II mini cabinet CTU2

Receiver

MiniSURF2

68P02900W21-S 12-40 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800/EGSM900/PGSM900] High power 2 sector 2/2, standard power 2 sector 4/4

Figure 12-36 shows a two cabinet (each cabinet containing two CTU2s), high power (HP) 2 sector 2/2/standard power (SP) 2 sector 4/4 configuration. Table 12-19 provides a summary of the equipment required for this configuration. Figure 12-36 DCS1800/EGSM900 HP 2 sector 2/2/SP 2 sector 4/4
Sector 2: 4 carriers 2 Sector 1: 4 carriers

SITE EXP

ALARM HIISC

0A 1A

ALARM HIISC

BATTERY

0A 1A

1B 0B

T43/BIB

1B 0B

T43/BIB

FRONT

REAR Horizon II mini SLAVE CABINET

BATTERY

FRONT

Horizon II mini MASTER CABINET

Table 12-19 Equipment required for HP 2 sector 2/2/SP 2 sector 4/4 Quantity Equipment

4 2 2 4 2

Antenna Horizon II mini cabinet Site I/O board CTU2

Receiver

MiniSURF2

68P02900W21-S 01 Feb 2007 12-41

SITE EXP

REAR

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800/EGSM900] High power 3 sector 1/1/1, standard power 3 sector 2/2/2

Figure 12-37 shows a two cabinet (the master cabinet containing two CTU2s, the slave cabinet containing one CTU2), high power (HP) 3 sector 1/1/1/standard power (SP) 3 sector 2/2/2 configuration. Table 12-20 provides a summary of the equipment required for this configuration. Figure 12-37 DCS1800/EGSM900 HP 3 sector 1/1/1/SP 3 sector 2/2/2
Sector 3: 4 carriers 2 Sector 1: 2 carriers Sector 2: 2 carriers

SITE EXP

ALARM HIISC

0A 1A

ALARM HIISC

BATTERY

0A 1A

1B 0B

T43/BIB

1B 0B

FRONT

REAR FRONT Horizon II mini SLAVE CABINET REAR Horizon II mini MASTER CABINET

Table 12-20 Equipment required for HP 3 sector 1/1/1/SP 3 sector 2/2/2 Quantity Equipment

6 2 2 3 2

Antenna Horizon II mini cabinet Site I/O board CTU2

Receiver

MiniSURF2

BATTERY
T43/BIB

SITE EXP

68P02900W21-S 12-42 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800/EGSM900] High power 3 sector 2/2/2, standard power 3 sector 4/4/4

Figure 12-38 shows a three cabinet (each cabinet containing two CTU2s) high power (HP) 3 sector 2/2/2/standard power 3 sector 4/4/4. Table 12-21 provides a summary of the equipment required for this configuration. Figure 12-38 DCS1800/EGSM900 HP 3 sector 2/2/2/SP 3 sector 4/4/4
Sector 2: 4 carriers 2 2 Sector 1: 4 carriers

SITE EXP

ALARM HIISC

0A 1A

ALARM HIISC

BATTERY

0A 1A

1B 0B

T43/BIB

1B 0B

T43/BIB

FRONT

REAR Horizon II mini SLAVE CABINET Sector 3: 4 carriers

BATTERY
REAR

FRONT

Horizon II mini MASTER CABINET

ALARM HIISC

0A 1A

1B 0B

T43/BIB

BATTERY

FRONT

Horizon II mini SLAVE CABINET

68P02900W21-S 01 Feb 2007 12-43

SITE EXP

REAR

SITE EXP

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Table 12-21 Equipment required for HP 3 sector 1/1/1/SP 3 sector 2/2/2 Quantity Equipment

6 3 2 6 3

Antenna Horizon II mini cabinet Site I/O board CTU2

Receiver

MiniSURF2

Horizon II micro cabinets

The following series of Horizon II micro RF configuration diagrams show the ways of connecting together Horizon II micro, MiniSURF2 and Tx blocks to meet different operational requirements. The series of diagrams is by no means exhaustive, and numerous alternative configurations can be adopted to achieve the same aim. Each diagram is applicable to either EGSM900 or DCS1800 operation, though the MiniSURF2 module illustrated is an 1800 MHz SURF2. For EGSM900 operation, a 900 MHz MiniSURF2 is required.

Rules for equipping Horizon II micro cabinets

The following rules apply when equipping any Horizon II micro cabinet for the configurations shown in Figure 12-39 and Figure 12-40: When operating in double density mode, both CTU2 carriers must be in the same sector. An external equipment cabinet is not required.

68P02900W21-S 12-44 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800/EGSM900] Single cabinet - Horizon II micro

Figure 12-39 shows a single cabinet configuration. Table 12-22 provides a summary of the equipment required for this configuration. Figure 12-39 [DCS1800/EGSM900] Horizon II micro one cabinet configuration
Sector 1: 2 carriers

ALARM

HIISC

1A 1B 0B BATTERY
T43/BIB POWER SUPPLY FRONT REAR Horizon II micro CABINET

Table 12-22 Equipment required for Horizon II micro one cabinet configuration Quantity Equipment

2 1 1 1

Antenna Horizon II micro cabinet CTU2

Receiver

MiniSURF2

68P02900W21-S 01 Feb 2007 12-45

0A

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800/EGSM900] Three cabinet - Horizon II micro

Figure 12-40 shows a three cabinet configuration. Table 12-23 provides a summary of the equipment required for this configuration. Figure 12-40 [DCS1800/EGSM900] Horizon II micro three cabinet configuration
Sector 2: 2 carriers 2 2 Sector 1: 2 carriers

SITE EXP

ALARM XMUX

0A 1A

ALARM HIISC

BATTERY

0A 1A

1B 0B

T43/BIB
POWER SUPPLY POWER SUPPLY

1B 0B

T43/BIB

FRONT

REAR Horizon II micro SLAVE CABINET Sector 3: 2 carriers

BATTERY

FRONT

Horizon II micro MASTER CABINET

ALARM XMUX

0A 1A

1B 0B

T43/BIB
POWER SUPPLY

BATTERY

FRONT

Horizon II micro SLAVE CABINET

SITE EXP

REAR

SITE EXP

REAR

68P02900W21-S 12-46 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

Table 12-23 Equipment required for Horizon II micro three cabinet configuration Quantity Equipment

2 1 1 1 3

Antenna Horizon II micro cabinet CTU2

Receiver

MiniSURF2 Site I/O board (expansion)

Horizonmacro cabinets
The following series of Horizonmacro RF configuration diagrams show the ways of connecting together Horizonmacro SURF and Tx blocks to meet different operational requirements. The series of diagrams is by no means exhaustive, and numerous alternative configurations can be adopted to achieve the same aim. Each diagram is applicable to either EGSM900 or DCS1800 operation, though the SURF module illustrated is a single band 1800 SURF. For EGSM900 operation a 900 SURF (dual band) is required. Connections to the 900 SURF are identified similar to the 1800 SURF, with two additional connectors provided for dual band 1800 use. A dual band 1800 SURF is also available which has two additional connectors provided for dual band 900 use.

Rules for equipping Horizonmacro cabinets

The following rules apply when equipping any Horizonmacro cabinet for the configurations shown in Figure 12-41 to Figure 12-48: A maximum of six CTUs can be accommodated. An external equipment cabinet is not required.

68P02900W21-S 01 Feb 2007 12-47

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800] 4 carrier omni, with duplexed hybrid and air combining

Figure 12-41 shows a single cabinet, four CTU configuration with duplexed hybrid and air combining. Table 12-24 provides a summary of the equipment required for this configuration. Figure 12-41 4 carrier omni, duplexed hybrid and air combining
Tx/Rx ANTENNA Tx/Rx ANTENNA

B2 1 0 A 2 1 0

B A

SURF

DCF

DCF

C T U

C T U

C T U

C T U

A B

A B

A B

A B

Horizonmacro CABINET

Table 12-24 Equipment required for 1 cabinet, 4 CTU configuration, duplexed hybrid and air combining Quantity Equipment

2 1 4 1 2

Antennas Horizonmacro cabinet CTU

Receiver

SURF
Transmitter/receiver

DCF

68P02900W21-S 12-48 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800] 6 carrier omni, with duplexed dual-stage hybrid and air combining
Figure 12-42 shows a single cabinet, six CTU configuration with duplexed dual-stage hybrid and air combining. Table 12-25 provides a summary of the equipment required for this configuration. Figure 12-42 6 carrier omni, duplexed dual-stage hybrid and air combining
Tx/Rx ANTENNA Tx/Rx ANTENNA

B2 1 0 A 2 1 0

B A

SURF FEED THROUGH

DDF

DDF

C T U

C T U

C T U

C T U

C T U

C T U

A B

A B

A B

A B

A B

A B

Horizonmacro CABINET

Table 12-25 Equipment required for 1 cabinet, 6 CTU configuration, duplex dual-stage hybrid and air combining Quantity Equipment

2 1 6 1 2 1

Antennas Horizonmacro cabinet CTU

Receiver

SURF
Transmitter/receiver

DDF Feed through, with two through connectors

68P02900W21-S 01 Feb 2007 12-49

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800] 2 sector (3/3), with duplexed dual-stage hybrid combining

Figure 12-43 shows a single cabinet, six CTU configuration with duplexed dual-stage hybrid combining. Table 12-26 provides a summary of the equipment required for this configuration. Figure 12-43 2 sector (3/3), duplexed dual-stage hybrid combining
Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 2) Rx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 2)

B2 1 0 A 2 1 0

B A

SURF FEED THROUGH

DDF

DDF

C T U

C T U

C T U

C T U

C T U

C T U

A B

A B

A B

A B

A B

A B

Horizonmacro CABINET

Table 12-26 Equipment required for 1 cabinet, 6 CTU configuration, duplexed dual-stage hybrid combining Quantity Equipment

4 1 6 1 2 1

Antennas Horizonmacro cabinet CTU

Receiver

SURF
Transmitter/receiver

DDF Feed through, with two through connectors

68P02900W21-S 12-50 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800] 2 sector (6/6), with duplexed dual-stage hybrid and air combining
Figure 12-44 shows a dual cabinet, 12 CTU configuration with duplexed dual-stage hybrid and air combining. Table 12-27 provides a summary of the equipment required for this configuration. Figure 12-44 2 sector (6/6), duplexed dual-stage hybrid and air combining
Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 2)

B2 1 0 A 2 1 0

B A

B2 1 0 A 2 1 0

B A

SURF

SURF

FEED THROUGH

FEED THROUGH

DDF

DDF

DDF

DDF

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER Horizonmacro CABINET

MASTER Horizonmacro CABINET

Table 12-27 Equipment required for dual cabinet, 12 CTU configuration, duplexed dual-stage hybrid and air combining Quantity Equipment

4 2 12 2 4 2

Antennas Horizonmacro cabinet CTU

Receiver

SURF
Transmitter/receiver

DDF Feed through, with two through connectors

68P02900W21-S 01 Feb 2007 12-51

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800] 3 sector (2/2/2), with duplexed hybrid combining

Figure 12-45 shows a single cabinet, six CTU configuration with duplexed hybrid combining. Table 12-28 provides a summary of the equipment required for this configuration. Figure 12-45 3 sector (2/2/2), duplexed hybrid combining
Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1) Rx Rx Rx ANTENNAS ANTENNAS ANTENNAS (SECTOR 3) (SECTOR 2) (SECTOR 1)

B2 1 0 A 2 1 0

B A

SURF

DCF

DCF

DCF

C T U

C T U

C T U

C T U

C T U

C T U

A B

A B

A B

A B

A B

A B

Horizonmacro CABINET

Table 12-28 Equipment required for 1 cabinet, 6 CTU configuration, duplexed hybrid combining Quantity Equipment

6 1 6 1 3

Antennas Horizonmacro cabinet CTU

Receiver

SURF
Transmitter/receiver

DCF

68P02900W21-S 12-52 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[DCS1800] 3 sector (4/4/4), with duplexed hybrid and air combining

Figure 12-46 shows a dual cabinet, 12 CTU configuration with duplexed hybrid and air combining. Table 12-29 provides a summary of the equipment required for this configuration. Figure 12-46 3 sector (4/4/4), duplexed hybrid and air combining
Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 2)

B2 1 0 A 2 1 0

B A

B2 1 0 A 2 1 0

B A

SURF

SURF

DCF

DCF

DCF

DCF

DCF

DCF

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER Horizonmacro CABINET

MASTER Horizonmacro CABINET

Table 12-29 Equipment required for dual cabinet, 12 CTU configuration duplexed hybrid and air combining Quantity Equipment

6 2 12 2 6

Antennas Horizonmacro cabinet CTU

Transmitter/receiver

SURF DCF

68P02900W21-S 01 Feb 2007 12-53

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[DCS1800] 3 sector (8/8/8), with duplexed dual-stage hybrid and air combining
Figure 12-47 and Figure 12-48 show a four cabinet, 24 CTU configuration with duplexed dual-stage hybrid and air combining. Table 12-30 provides a summary of the equipment required for this configuration. Figure 12-47 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 1)
Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 1) TO SURF EXT A EXTENDER 1 Horizonmacro SURF B0 CABINET

B2 1 0 A 2 1 0

B A

B2 1 0 A 2 1 0

B A

SURF

SURF

HCU DDF DDF

HCU DDF

HCU

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER 3 Horizonmacro CABINET

EXTENDER 2 Horizonmacro CABINET

68P02900W21-S 12-54 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

Figure 12-48 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 2)
SURF A0 TO EXTENDER 2 Horizonmacro CABINET SURF EXT B

Tx/Rx ANTENNA (SECTOR 1)

Tx/Rx ANTENNA (SECTOR 2)

Tx/Rx ANTENNA (SECTOR 2)

B2 1 0 A 2 1 0

B A

B2 1 0 A 2 1 0

B A

SURF

SURF

HCU DDF

HCU DDF

HCU DDF

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

C T U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER 1 Horizonmacro CABINET

MASTER Horizonmacro CABINET

Table 12-30 Equipment required for 4 cabinet, 24 CTU configuration, duplex dual-stage hybrid and air combining Quantity Equipment

6 4 24 6 4 6

Antennas Horizonmacro cabinet CTU

Transmitter

Hybrid combiner unit (HCU)

Receiver

SURF
Transmitter/receiver

DDF

68P02900W21-S 01 Feb 2007 12-55

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Horizoncompact2
The Horizoncompact2 BTS system comprises a BTS enclosure and a booster enclosure. One or two additional Horizoncompact2 BTS systems can be added as slaves to provide a two or three BTS site. The Horizoncompact2 BTS system supports the following site configurations using GSM900 or DCS1800 BTSs:
1 BTS site

Omni site - one or two carriers in a single cell.

2 BTS site

Omni site - up to four carriers in a single cell. Two sector site, and two carriers per cell.
3 BTS site

Omni site - up to six carriers in a single cell. Two sector site, two/four carriers per cell. Three sector site, two carriers per cell. The following dual band cell configurations are supported when GSM900 and DCS1800 Horizoncompact2 BTSs are used:
2 BTS cell

One BTS with two GSM900 carriers and one BTS with two DCS1800 carriers.
3 BTS cell

Two BTSs with four GSM900 carriers and one BTS with two DCS1800 carriers. or Two BTSs with four DCS1800 carriers and one BTS with two GSM900 carriers.

68P02900W21-S 12-56 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[GSM900/DCS1800] Horizoncompact2 single BTS system

Figure 12-49 shows the configuration for a single Horizoncompact2 BTS system. Figure 12-49 Horizoncompact2 single BTS system
Tx2 ANTENNA Tx1/Rx ANTENNA

ANT

ANT

FILTER
Tx

DUPLEXER
Rx Tx

AMP Horizoncompact2 BOOSTER

Rx Tx2

AMP

Tx1

ISOLATOR MODULE

ISOLATOR MODULE

Rx IN

Tx2 OUT

Tx1 OUT

DINO / RHINO

DTRX

Horizoncompact2 BTS

68P02900W21-S 01 Feb 2007 12-57

Horizon macrocell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[GSM900/DCS1800] Horizoncompact2 two BTS system

Figure 12-50 shows the configuration for a two Horizoncompact2 BTS system using fiber optic cables. An HDSL option is available which allows the BTSs to be connected through HDSL links. Refer to Figure 12-49 for internal connections within the BTS and booster.

Figure 12-50 Horizoncompact2 two BTS system

Tx2 ANTENNA Tx1/Rx ANTENNA Tx2 ANTENNA Tx1/Rx ANTENNA

Horizoncompact2 BOOSTER

Horizoncompact2 BOOSTER

DINO / RHINO Horizoncompact2 MASTER BTS

DINO / RHINO Horizoncompact2 SLAVE BTS

FIBRE OPTIC LINK

68P02900W21-S 12-58 01 Feb 2007

System Information: BSS Equipment Planning

Horizon macrocell RF configurations

[GSM900/DCS1800] Horizoncompact2 three BTS system

Figure 12-51 shows the configuration for a three Horizoncompact2 BTS system using fiber optic cables. An HDSL option is available which allows the BTSs to be connected through HDSL links. Refer to Figure 12-49 for internal connections within the BTS and booster. Figure 12-51 Horizoncompact2 three BTS system
Tx2 Tx1/Rx ANTENNA ANTENNA Tx2 Tx1/Rx Tx2 Tx1/Rx ANTENNA ANTENNA ANTENNA ANTENNA

Horizoncompact2 BOOSTER

Horizoncompact2 BOOSTER

DINO / RHINO Horizoncompact2 MASTER BTS

DINO / RHINO Horizoncompact2 SLAVE BTS

FIBRE OPTIC LINK

Horizoncompact2 BOOSTER

FIBRE OPTIC LINK

DINO / RHINO Horizoncompact2 SLAVE BTS

68P02900W21-S 01 Feb 2007 12-59

Microcell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

Microcell RF configurations
Horizonmicro2
The Horizonmicro2 BTS is like the Horizoncompact2, but does not include (or support) a booster enclosure. One or two additional Horizonmicro2 BTSs can be added as slaves to provide a two or three BTS site. The Horizonmicro2 BTS supports the following site configurations using GSM900 or DCS1800 BTSs:
1 BTS site

Omni site - one or two carriers in a single cell.

2 BTS site

Omni site - up to four carriers in a single cell. Two sector site, two carriers per cell.
3 BTS site

Omni site - up to six carriers in a single cell. Two sector site, two/four carriers per cell. Three sector site, two carriers per cell. The following dual band cell configurations are supported when GSM900 and DCS1800 Horizonmicro2 BTSs are used:
2 BTS cell

One BTS with two GSM900 carriers and one BTS with two DCS1800 carriers.
3 BTS cell

Two BTSs with four GSM900 carriers and one BTS with two DCS1800 carriers Or Two BTSs with four DCS1800 carriers and one BTS with two GSM900 carriers.

68P02900W21-S 12-60 01 Feb 2007

System Information: BSS Equipment Planning

Microcell RF configurations

[GSM900/DCS1800] Horizonmicro2 single BTS system

Figure 12-52 shows the configuration for a single Horizonmicro2 BTS system. Figure 12-52 Horizonmicro2 single BTS system
Tx1/Tx2/Rx ANTENNA

ANT

DUPLEXER
Rx Tx

COMBINER/ ISOLATOR MODULE

Tx Tx Tx

Rx IN

Tx2 OUT

Tx1 OUT

DINO / RHINO

DTRX

Horizonmicro2 BTS

[GSM900/DCS1800] Horizonmicro2 two BTS system

Figure 12-53 shows the configuration for a two Horizonmicro2 BTS system using fiber optic cables. An HDSL option is available, which allows the BTSs to be connected through HDSL links. Refer to Figure 12-52 for internal connections within the BTS. Figure 12-53 Horizonmicro2 two BTS system
Tx1/Tx2/Rx ANTENNA Tx1/Tx2/Rx ANTENNA

DINO / RHINO Horizonmicro2 MASTER BTS

DINO / RHINO Horizonmicro2 SLAVE BTS

FIBRE OPTIC LINK

68P02900W21-S 01 Feb 2007 12-61

Microcell RF configurations

Chapter 12: Standard BSS and Horizon BTS configurations

[GSM900/DCS1800] Horizonmicro2 three BTS system

Figure 12-54 shows the configuration for a three Horizonmicro2 BTS system using fiber optic cables. An HDSL option is available, which allows the BTSs to be connected through HDSL links. Refer to Figure 12-52 for internal connections within the BTS. Figure 12-54 Horizonmicro2 three BTS system
Tx1/Tx2/Rx ANTENNA Tx1/Tx2/Rx ANTENNA Tx1/Tx2/Rx ANTENNA

DINO / RHINO Horizonmicro2 MASTER BTS

DINO / RHINO Horizonmicro2 SLAVE BTS

FIBRE OPTIC LINK

FIBRE OPTIC LINK

DINO / RHINO Horizonmicro2 SLAVE BTS

68P02900W21-S 12-62 01 Feb 2007

System Information: BSS Equipment Planning

Connecting Horizon II macro cabinets to Horizonmacro cabinets

Connecting Horizon II macro cabinets to Horizonmacro cabinets

Connection overview
This section provides examples of how previous generation Horizonmacro BTS equipment can be connected to the latest generation Horizon II macro BTS equipment.

Compatibility issues
The following points must be taken into account when connecting Horizon II macro cabinets to Horizonmacro cabinets: Although the Horizon II macro equipment is compatible with Horizonmacro equipment, the CTU2 is the only module that can be used in either cabinet. When CTU2s are used in Horizonmacro, baseband hopping is only supported in single density mode. In cases, where the Horizonmacro BTS is the master cabinet and the MCUF is the master site controller, the MCUF must have a 20 Mbyte PCMCIA card running the CSFP to accommodate the added memory requirements of the GSR6 (Horizon II) objects.

Examples of mixed cabinet configurations

Figure 12-55 to Figure 12-60 are examples of possible configurations for mixed Horizon II macro and Horizonmacro cabinets.

68P02900W21-S 01 Feb 2007 12-63

Connecting Horizon II macro cabinets to Horizonmacro cabinets

Chapter 12: Standard BSS and Horizon BTS configurations

Sector 4/4 configuration using two cabinets

Figure 12-55 shows the configuration for sector 4/4, using one Horizon II macro cabinet with duplexers and one Horizonmacro cabinet. Figure 12-55 Sector 4/4 configuration with Horizon II macro and Horizonmacro cabinets
SECTOR 1 SECTOR 2

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

2B SURF

1B

0B 2A 1A

0A

EXT

4
RX

1
RX

BLANK

DCF

DCF

ANT

ANT

BLANK

BLANK

DUP

BLANK

BLANK

DUP

EMPTY

EMPTY

CTU2

EMPTY

EMPTY

CTU2

SITE EXPANSION BOARD

HIISC

FMUX

Horizon II macro master cabinet

Horizonmacro slave cabinet

Fibre Optic Link (x2)

68P02900W21-S 12-64 01 Feb 2007

System Information: BSS Equipment Planning

Connecting Horizon II macro cabinets to Horizonmacro cabinets

Sector 6/6 configuration using two cabinets

Figure 12-56 shows the configuration for sector 6/6, using one Horizon II macro cabinet with duplexers and hybrid combiner units and one Horizonmacro cabinet. Figure 12-56 Sector 6/6 configuration with Horizon II macro and Horizonmacro cabinets
SECTOR 1 SECTOR 2

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

2B SURF

1B

0B 2A 1A

0A

EXT

5
HCU

4
RX

2
HCU

1
RX

DDF

FTHRU

DDF

ANT

ANT

BLANK
LOAD

DUP

BLANK

DUP

EMPTY

EMPTY

CTU2

EMPTY

CTU2

CTU2

SITE EXPANSION BOARD

HIISC

FMUX

Horizon II macro master cabinet

Horizonmacro slave cabinet

Fibre Optic Link (x2)

68P02900W21-S 01 Feb 2007 12-65

Connecting Horizon II macro cabinets to Horizonmacro cabinets

Chapter 12: Standard BSS and Horizon BTS configurations

Sector 2/2/2 configuration using two cabinets

Figure 12-57 and Figure 12-58 show the configurations for sector 2/2/2, using one Horizon II macro cabinet with duplexer and one Horizonmacro cabinet. In Figure 12-57, the Horizon II macro is the master cabinet, whereas in Figure 12-58 the Horizonmacro is the master cabinet. Figure 12-57 Sector 2/2/2 configuration (Horizon II macro as master cabinet)
SECTOR 1 SECTOR 3 SECTOR 2

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX 0A B A

RX 1A

RX 2A

2B SURF

1B

0B 2A 1A

0A

EXT

1
RX

BLANK

DCF

DCF

ANT

BLANK

BLANK

BLANK

BLANK

BLANK

DUP

EMPTY

EMPTY

EMPTY

EMPTY

EMPTY

CTU2

SITE EXPANSION BOARD

HIISC

FMUX

Horizon II macro master cabinet

Horizonmacro slave cabinet

Fibre Optic Link (x2)

68P02900W21-S 12-66 01 Feb 2007

System Information: BSS Equipment Planning

Connecting Horizon II macro cabinets to Horizonmacro cabinets

Figure 12-58 Sector 2/2/2 configuration (Horizonmacro as master cabinet)

SECTOR 3 SECTOR 2 SECTOR 1

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX 0A B A

RX 1A

RX 2A

2B SURF

1B

0B 2A 1A

0A

EXT

1
RX

BLANK

DCF

DCF

ANT

BLANK

BLANK

BLANK

BLANK

BLANK

DUP

EMPTY

EMPTY

EMPTY

EMPTY

EMPTY

CTU2

SITE EXPANSION BOARD

XMUX

MCUF

Horizon II macro slave cabinet

Horizonmacro master cabinet

Fibre Optic Link (x2)

68P02900W21-S 01 Feb 2007 12-67

Connecting Horizon II macro cabinets to Horizonmacro cabinets

Chapter 12: Standard BSS and Horizon BTS configurations

Sector 4/4/4 configuration using two cabinets

Figure 12-59 shows the configuration for sector 4/4/4, using one Horizon II macro cabinet with duplexers and one Horizonmacro cabinet. Figure 12-59 Sector 4/4/4 configuration with Horizon II macro and Horizonmacro cabinets
SECTOR 2 SECTOR 1 SECTOR 3

RX 2B SURF2

RX 1B

RX 0B

EXP EXP RX 0A B A

RX 1A

RX 2A

2B

1B

0B 2A 1A

0A

SURF

EXT

5
RX

4
RX

2
RX

1
RX

BLANK

DCF

DCF

ANT

ANT

ANT

ANT

BLANK

DUP

DUP

BLANK

DUP

DUP

EMPTY

CTU2

CTU2

EMPTY

CTU2

CTU2

SITE EXPANSION BOARD

HIISC

FMUX

Horizon II macro master cabinet

Horizonmacro slave cabinet

Fibre Optic Link (x2)

68P02900W21-S 12-68 01 Feb 2007

System Information: BSS Equipment Planning

Connecting Horizon II macro cabinets to Horizonmacro cabinets

Sector 6/6/6 configuration using two cabinets

Figure 12-60 shows the configuration for sector 6/6/6, using one Horizon II macro cabinet with duplexers and dual hybrid combiner units and one Horizonmacro cabinet. Figure 12-60 Sector 6/6/6 configuration with Horizon II macro and Horizonmacro cabinets
SECTOR 2 SECTOR 1 SECTOR 3

RX 2B

RX 1B

RX 0B

EXP EXP RX B A 0A

RX 1A

RX 2A

2B SURF

1B

0B 2A 1A

0A

EXT

5
DHU

4
RX

2
DHU

1
RX

DDF

FTHRU

DDF

ANT

ANT

BLANK

DUP

BLANK

DUP

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

SITE EXPANSION BOARD

HIISC

FMUX

Horizon II macro master cabinet

Horizonmacro slave cabinet

Fibre Optic Link (x2)

68P02900W21-S 01 Feb 2007 12-69

Connecting Horizon II macro cabinets to Horizonmacro cabinets

Chapter 12: Standard BSS and Horizon BTS configurations

Using CTU2s in Horizonmacro cabinets

Figure 12-61 shows an example of a configuration with CTU2s (operating in single density mode) installed in a Horizonmacro cabinet. Figure 12-61 Horizonmacro cabinet configuration using CTUs and CTU2s
SECTOR 3 SECTOR 2 SECTOR 1

2B SURF

1B

0B 2A 1A

0A

EXT

DCF

DCF

DCF

CTU2 CTU2

MCUF

Horizonmacro cabinet

68P02900W21-S 12-70 01 Feb 2007

System Information: BSS Equipment Planning

Connecting Horizon II macro cabinets to M-Cell6 cabinets

Connecting Horizon II macro cabinets to M-Cell6 cabinets

Connection overview
This section provides the examples of how older generation M-Cell6 BTS equipment can be connected to the latest generation Horizon II macro BTS equipment.

M-Cell2 BTS cabinets cannot be connected to Horizon II macro BTS cabinets.

Compatibility issues
The following points must be taken into account when connecting Horizon II macro cabinets to M-Cell6 cabinets: Although the Horizon II macro equipment is compatible with M-Cell6 equipment, none of the Horizon II macro components can be used in the M-Cell6. In cases, where the M-Cell6 BTS is the master cabinet and the MCU is the master site controller, the MCU must have a 20 Mbyte PCMCIA card running the CSFP to accommodate the added memory requirements of the GSR6 (Horizon II) objects. In cases, where the M-Cell6 BTS is the site controller and has CTU2 adapters running, the MCU must have a 20 Mbyte PCMCIA card running the CSFP to accommodate the use of the CTU2 transceiver from a code storage standpoint. A CTU2 can be used in an M-Cell6 cabinet when the CTU2 Adapter is used. The M-Cell6 must have a FMUX installed to communicate with the Horizon II macro cabinet. When DCS1800 cabinets are connected, connections between the Horizon II macro SURF2 and the M-Cell6 LNAs must include -13 dB attenuators.

68P02900W21-S 01 Feb 2007 12-71

Connecting Horizon II macro cabinets to M-Cell6 cabinets

Chapter 12: Standard BSS and Horizon BTS configurations

900 MHz BTSs

Figure 12-62 shows how a 900 MHz Horizon II macro BTS cabinet can be connected to a 900 MHz MCell6 BTS cabinet to create a 2 sector (4/4) configuration. Figure 12-62 900 MHz Horizon II macro and 900 MHz M-Cell6 interconnections
SECTOR 1 SECTOR 2

RX RX RX EXP EXP RX RX RX 2B 1B 0B B A 0A 1A 2A SURF2

DUPLEXER

DUPLEXER

DLNB

IADU

4
RX

1
RX

ANT

ANT

BLANK BLANK

DUP

BLANK BLANK

DUP

BLANK

CBF1

CBF0

EMPTY EMPTY CTU2 EMPTY EMPTY

CTU2

0
HIISC

T C U

T C U

T C U

T C U

FMUX

SITE EXPANSION

Horizon II macro BOARD master cabinet

M-Cell6 slave cabinet

Fibre Optic Link (x2)

68P02900W21-S 12-72 01 Feb 2007

System Information: BSS Equipment Planning

Connecting Horizon II macro cabinets to M-Cell6 cabinets

1800 MHz BTSs

Figure 12-63 shows how a 1800 MHz Horizon II macro BTS cabinet can be connected to a 1800 MHz MCell6 BTS cabinet to create a 2 sector (4/4) configuration. Figure 12-63 1800 MHz Horizon II macro and 1800 MHz M-Cell6 interconnections
SECTOR 1 SECTOR 2

RX RX RX EXP EXP RX RX RX 2B 1B 0B B A 0A 1A 2A SURF2

DUPLEXER

DUPLEXER

LNA

4
RX

1
RX

ANT

ANT

BLANK BLANK

DUP

BLANK BLANK

DUP

BLANK

CBF1

CBF0

EMPTY EMPTY CTU2 EMPTY EMPTY

CTU2

0
HIISC

T C U

T C U

T C U

T C U

FMUX

SITE EXPANSION

Horizon II macro BOARD master cabinet

M-Cell6 slave cabinet

Fibre Optic Link (x2)

68P02900W21-S 01 Feb 2007 12-73

Connecting Horizon II macro cabinets to M-Cell6 cabinets

Chapter 12: Standard BSS and Horizon BTS configurations

68P02900W21-S 12-74 01 Feb 2007

Chapter 13 M-Cell BTS configurations

This chapter is included for reference purposes. It provides diagrams of the logical interconnections of the components in older generation M-Cell BTS equipment and typical RF configurations. Examples of how M-Cell equipment is connected to current generation horizon equipment are provided in Chapter 12, Standard BSS and Horizon BTS configurations. The topics described here are as follows:
M-Cell BTS configurations Standard M-Cell configurations Single cabinet BTS configurations Two cabinet BTS configuration Three cabinet BTS configuration Four cabinet BTS configuration M-Cell RF configurations

68P02900W21-S 01 Feb 2007 13-1

M-Cell BTS configurations

Chapter 13: M-Cell BTS configurations

M-Cell BTS configurations

M-Cell BTS configurations are included for reference purposes. It provides diagrams of the logical interconnections of the components in older generation M-Cell BTS equipment and typical RF configurations. Examples of connecting M-Cell equipment to current generation Horizon equipment are described in Chapter 12, Standard BSS and Horizon BTS configurations. This chapter describes the following configurations:
Standard M-Cell configurations Single cabinet BTS configurations Two cabinet BTS configuration Three cabinet BTS configuration Four cabinet BTS configuration M-Cell RF configurations

68P02900W21-S 13-2 01 Feb 2007

System Information: BSS Equipment Planning

Standard M-Cell configurations

Standard M-Cell configurations

The examples in this section are shown with individual antennas for transmit and receive signals. Duplexers are required if individual antennas are not used. However, duplexers can result in performance degradation. For carrier redundancy, the RF carrier equipment must be duplicated for each BTS. The diagrams that follow do not indicate the maximum capacity or a typical configuration using that specific equipment. The diagrams highlight the configurations that are feasible when the macrocell hardware is deployed in an M-Cell BTS, within the constraints of the BSS architecture. The diagrams also show possible cabinet boundaries. Cabinet designs, however, allow for some different arrangements of the same configuration.

For typical BSS configurations, refer to Figure 12-1 and Figure 12-2 in Chapter 12, Standard BSS and Horizon BTS configurations. The control redundancy is depicted only for one M-Cell6, and one M-Cell2 cabinet diagram (Refer to Figure 13-1 and Figure 13-2).

68P02900W21-S 01 Feb 2007 13-3

Single cabinet BTS configurations

Chapter 13: M-Cell BTS configurations

Single cabinet BTS configurations

Single cabinet M-Cell6 BTS
The configuration shown in Figure 13-1 is an example of a single cabinet M-Cell6 BTS. This configuration supports six carriers.
Figure 13-1 Single cabinet M-Cell6 BTS

N I U

mBCU

N I U

mBCU

MCU

MCU

12 F O X

12 F O X

(FOR REDUNDANCY)

12

12

2 T C U

2 T C U

2 T C U

T C U 2

T C U

T C U

M-CELL6 BTS CABINET

68P02900W21-S 13-4 01 Feb 2007

System Information: BSS Equipment Planning

Single cabinet BTS configurations

Single cabinet M-Cell2 BTS

The configuration shown in Figure 13-2 is an example of a single cabinet M-Cell2 BTS. This configuration supports two carriers.
Figure 13-2 Single cabinet M-Cell2 BTS

N I U

mBCU

N I U

mBCU

MCU

MCU

(FOR REDUNDANCY)

2 T C U

T C U

M-CELL2 CABINET

68P02900W21-S 01 Feb 2007 13-5

Two cabinet BTS configuration

Chapter 13: M-Cell BTS configurations

Two cabinet BTS configuration

Two cabinet M-Cell6 BTS
The configuration shown in Figure 13-3 is an example of a two cabinet M-Cell6 BTS. This configuration supports 12 carriers. The MCUs interface to the TCUs through the FOX or the FMUX/FOX.
Figure 13-3 Two cabinet M-Cell6 BTS
N I U mBCU

M-CELL6 BTS CABINET

MCU

12

F M U X

12 F O X 12 2 2 2 2 2 2 T C U

T C U

T C U

T C U

T C U

T C U

M-CELL6 BTS CABINET

12 2 2 2 2 2 2 T C U mBCU F O X F M U X

T C U

T C U

T C U

T C U

T C U

68P02900W21-S 13-6 01 Feb 2007

System Information: BSS Equipment Planning

Two cabinet BTS configuration

Two cabinet M-Cell6 BTS with CTU2 Adapter

The configuration shown in Figure 13-4 is an example of a two cabinet M-Cell6 BTS when CTU2 Adapters are used. This configuration supports 24 carriers. The MCUs interface to the CTU2s through the FOX or the FMUX/FOX.
Figure 13-4 Two cabinet M-Cell6 BTS with CTU2 Adapters
N I U mBCU

M-CELL6 BTS CABINET

MCU

12

F M U X

12 F O X 12 2 2 2 2 2 2 T C U

T C U

T C U

T C U

T C U

T C U

M-CELL6 BTS CABINET

12 2 2 2 2 2 2 T C U mBCU F O X F M U X

T C U

T C U

T C U

T C U

T C U

68P02900W21-S 01 Feb 2007 13-7

Three cabinet BTS configuration

Chapter 13: M-Cell BTS configurations

Three cabinet BTS configuration

Three cabinet M-Cell2 BTS
The configuration shown in Figure 13-5 is an example of a three cabinet M-Cell2 BTS. This configuration supports six carriers.
Figure 13-5 Three cabinet M-Cell2 BTS
N I U mBCU

M-CELL2 CABINET

MCU

12

F O X

12 2 2 T C U

T C U

M-CELL2 CABINET
2 2

T C U

T C U

M-CELL2 CABINET
2 2

T C U

T C U

68P02900W21-S 13-8 01 Feb 2007

System Information: BSS Equipment Planning

Four cabinet BTS configuration

Four cabinet BTS configuration

Four cabinet M-Cell6 BTS
The configuration shown in Figure 13-6 is an example of a four cabinet M-Cell6 BTS. This configuration supports 24 carriers. The MCUs interface to the TCUs through the FOX or the FMUX/FOX.
Figure 13-6 Four cabinet M-Cell6 BTS
N I U mBCU 12 F M U X 2

M-CELL6 BTS CABINET

MCU

12

F M U X

12 F O X 12 2 2 2 2 2 2 T C U 12 F M U X 2

T C U

T C U

T C U

T C U

T C U

M-CELL6 BTS CABINET

12 2 2 2 2 2 2 T C U mBCU F O X F M U X

T C U

T C U

T C U

T C U

T C U

M-CELL6 BTS CABINET

12 2 2 2 2 2 2 T C U mBCU F O X F M U X

T C U

T C U

T C U

T C U

T C U

M-CELL6 BTS CABINET

12 2 2 2 2 2 2 T C U mBCU F O X F M U X

T C U

T C U

T C U

T C U

T C U

68P02900W21-S 01 Feb 2007 13-9

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

M-Cell RF configurations
Overview
The M-Cell BTS cabinets can be configured as follows: M-Cell6 single cabinet M-Cell6 multiple cabinets M-Cell2 single cabinet

Rules for equipping M-Cell cabinets

The following rules apply when equipping an M-Cell cabinet for the configurations shown in Figure 13-7 to Figure 13-42: An M-Cell6 BTS cabinet accommodates a maximum of six TCUs. An M-Cell6 BTS cabinet accommodates a maximum of twelve carriers when CTU2 Adapters are used. An M-Cell2 BTS cabinet accommodates a maximum of two TCUs. An external equipment cabinet is not required, unless specifically stated in the text accompanying the configuration diagram. An M-Cell6 side cabinet accommodates a maximum of three high power duplexers.

M-Cell6 cabinets

Diversity is assumed in all figures, unless stated otherwise.

[GSM900] 3 carrier omni, with hybrid combining and diversity

A single cabinet, four TCU configuration with hybrid combining and diversity, is shown in Figure 13-7. Table 13-1 provides a summary of the equipment required for this configuration.

68P02900W21-S 13-10 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

Figure 13-7 3 carrier omni, hybrid combining

Tx ANTENNA Rx ANTENNAS

DLNB

RF INPUT RF LOAD

IADU

NonHCOMB

3-INPUT CBF
4 4

T C U

T C U

T C U

A B

A B

A B M-Cell6 BTS CABINET

Table 13-1 Equipment required for single cabinet, 4 TCU configuration with hybrid combining and diversity Quantity Equipment

3 1 3 1 1 1

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Non-hybrid combiner (Non-HCOMB)

Receiver

DLNB

68P02900W21-S 01 Feb 2007 13-11

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 3 carrier omni, with hybrid combining, diversity, and medium power duplexer
A single cabinet, four TCU configuration with hybrid combining and diversity, is shown in Figure 13-8. Table 13-2 provides a summary of the equipment required for this configuration.
Figure 13-8 3 carrier omni, hybrid combining, medium power duplexer
Tx/Rx ANTENNA Rx ANTENNA

DUPLEXER DLNB
RF INPUT RF LOAD

IADU

NonHCOMB

3-INPUT CBF
4 4

T C U

T C U

T C U

A B

A B

A B M-Cell6 BTS CABINET

Table 13-2 Equipment required for single cabinet, 4 TCU configuration with hybrid combining, diversity and medium power duplexer Quantity Equipment

2 1 3 1 1 1 1

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Non-hybrid combiner (Non-HCOMB)

Receiver

DLNB
Transmitter/receiver

Medium power duplexer

68P02900W21-S 13-12 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 4 carrier omni, with hybrid combining and diversity

A single cabinet, four TCU configuration with hybrid combining and diversity, is shown in Figure 13-9. Table 13-3 provides a summary of the equipment required for this configuration.
Figure 13-9 4 carrier omni, hybrid combining
Tx ANTENNA Rx ANTENNAS

DLNB
RF INPUT RF LOAD

IADU

HCOMB

3-INPUT CBF
4 4

T C U

T C U

T C U

T C U

A B

A B

A B

A B M-Cell6 BTS CABINET

Table 13-3 Equipment required for single cabinet, 4 TCU configuration with hybrid combining and diversity Quantity Equipment

3 1 4 1 1 1

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Hybrid combining block (HCOMB)

Receiver

DLNB

68P02900W21-S 01 Feb 2007 13-13

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 4 carrier omni, with hybrid combining, diversity, and medium power duplexer
A single cabinet, four TCU configuration with hybrid combining, diversity, and medium power duplexer, is shown in Figure 13-10. Table 13-4 provides a summary of the equipment required for this configuration.
Figure 13-10 4 carrier omni, hybrid combining, medium power duplexer
Tx/Rx ANTENNA Rx ANTENNA

DUPLEXER
RF INPUT RF LOAD

DLNB

HCOMB

3-INPUT CBF

IADU

T C U

T C U

T C U

T C U

A B

A B

A B

A B M-Cell6 BTS CABINET

Table 13-4 Equipment required for single cabinet, 4 TCU configuration with hybrid combining, diversity and medium power duplexer Quantity Equipment

2 1 4 1 1 1 1

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Hybrid combining block (HCOMB)

Receiver

DLNB
Transmitter/Receiver

Medium power duplexer

68P02900W21-S 13-14 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 6 carrier omni, with cavity combining and diversity

A single cabinet, six TCU configuration with cavity combining and diversity, is shown in Figure 13-11. Table 13-5 provides a summary of the equipment required for this configuration.
Figure 13-11 6 carrier omni, cavity combining
Tx ANTENNA Rx ANTENNAS

DLNB CCB CCB

(EXTENSION)

(OUTPUT)

IADU

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

M-Cell6 BTS CABINET

Table 13-5 Equipment required for single cabinet, 6 TCU configuration with cavity combining and diversity Quantity Equipment

3 1 6 1 1 1

Antennas M-Cell6 BTS cabinet TCU

Transmitter

CCB (Output) CCB (Extension)

Receiver

DLNB

68P02900W21-S 01 Feb 2007 13-15

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 6 carrier omni, with cavity combining, diversity, and high power duplexer
A single cabinet, six TCU configuration with cavity combining, diversity, and high power duplexer, is shown in Figure 13-12. Table 13-6 provides a summary of the equipment required for this configuration. An external equipment rack/cabinet is required for a high power duplexer in an indoor installation.
Figure 13-12 6 carrier omni, cavity combining, high power duplexer
Rx ANTENNA Tx/Rx ANTENNA

DLNB
ANT

IADU
CCB (EXTENSION) 6 6 CCB (OUTPUT) Rx

Tx HIGH POWER DUPLEXER

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

M-Cell6 BTS CABINET

M-Cell6 SIDE CABINET

Table 13-6 Equipment required for single cabinet, 6 TCU configuration with cavity combining, diversity and high power duplexer Quantity Equipment

3 1 1 6 1 1 1 1

Antennas M-Cell6 BTS cabinet M-Cell6 side cabinet TCU

Transmitter

CCB (Output) CCB (Extension)

Receiver

DLNB
Transmitter/Receiver High power duplexer

68P02900W21-S 13-16 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 8 carrier omni, with combining and diversity

A dual cabinet, 8 TCU configuration with combining and diversity, is shown in Figure 13-13. Table 13-7 provides a summary of the equipment required for this configuration.
Figure 13-13 8 carrier omni, combining
Tx ANTENNA Tx/Rx ANTENNA Rx ANTENNA

Rx EXT BLOCK

DUPLEXER DLNB

IADU CBF IADU

CCB (EXTENSION) 6 2 2 CCB (OUTPUT)

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

A B

A B MASTER M-Cell6 BTS CABINET

EXTENDER M-Cell6 BTS CABINET

Table 13-7 Equipment required for multiple cabinet, 8 TCU configuration with combining and diversity Quantity Equipment

3 2 8 1 1 1 1 1 1

Antennas M-Cell6 BTS cabinet TCU CBF CCB (Output) CCB (Extension)
Receiver

DLNB Rx extension block

Transmitter/Receiver

Medium power duplexer

68P02900W21-S 01 Feb 2007 13-17

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 2 sector (3/3), with hybrid combining and diversity

A single cabinet, six TCU configuration with hybrid combining and diversity, is shown in Figure 13-14.
Table 13-8 provides a summary of the equipment required for this configuration. Figure 13-14 2 sector (3/3), hybrid combining
Tx ANTENNA (SECTOR 2) Tx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 2) Rx ANTENNA (SECTOR 1)

DLNB
RF INPUT RF LOAD RF INPUT RF LOAD

DLNB

IADU

3-INPUT CBF
NonHCOMB

3-INPUT CBF

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B M-Cell6 BTS CABINET

Table 13-8 Equipment required for single cabinet, 6 TCU configuration with hybrid combining and diversity Quantity Equipment

6 1 6 2 1 2

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Non-hybrid combiner (Non-HCOMB)

Receiver

DLNB

68P02900W21-S 13-18 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 2 sector (3/3), with hybrid combining, diversity, and medium power duplexers
A single cabinet, six TCU configuration with hybrid combining, diversity, and medium power duplexers, is shown in Figure 13-15. Table 13-9 provides a summary of the equipment required for this configuration.
Figure 13-15 2 sector (3/3), hybrid combining, medium power duplexers
Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 2) Rx ANTENNA (SECTOR 1)

DUPLEXER DUPLEXER
RF INPUT RF LOAD RF INPUT RF LOAD

DLNB

DLNB

3-INPUT CBF
NonHCOMB

IADU 3-INPUT CBF

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B M-Cell6 BTS CABINET

Table 13-9 Equipment required for single cabinet, 6 TCU configuration with combining, diversity and medium power duplexer Quantity Equipment

4 1 6 2 1 2 2

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Non-hybrid combiner (Non-HCOMB)

Receiver

DLNB
Transmitter/Receiver

Medium power duplexer

68P02900W21-S 01 Feb 2007 13-19

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 3 sector (2/2/2), with combining and diversity

A single cabinet, six TCU configuration with combining and diversity, is shown in Figure 13-16. Table 13-10 provides a summary of the equipment required for this configuration.
Figure 13-16 3 sector (2/2/2), combining
Tx ANTENNA (SECTOR 1) Tx ANTENNA (SECTOR 2) Tx ANTENNA (SECTOR 3) Rx ANTENNAS (SECTOR 1) Rx ANTENNAS (SECTOR 2) Rx ANTENNAS (SECTOR 3)

DLNB

DLNB

DLNB

IADU

CBF

CBF

CBF

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

M-Cell6 BTS CABINET

Table 13-10 Equipment required for single cabinet, 6 TCU configuration with combining and diversity Quantity Equipment

9 1 6 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

CBF
Receiver

DLNB

68P02900W21-S 13-20 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 3 sector (2/2/2), with cavity combining, diversity, and medium power duplexers
A single cabinet, six TCU configuration with cavity combining, diversity, and medium power duplexers, is shown in Figure 13-17. Table 13-11 provides a summary of the equipment required for this configuration.
Figure 13-17 3 sector (2/2/2), combining, medium power duplexers
Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 3) Rx ANTENNA (SECTOR 2) Rx ANTENNA (SECTOR 1)

DUPLEXER DUPLEXER DUPLEXER DLNB DLNB DLNB

IADU CBF CBF CBF

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B M-Cell6 BTS CABINET

Table 13-11 Equipment required for single cabinet, 6 TCU configuration with combining, diversity and medium power duplexers Quantity Equipment

6 1 6 3 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

CBF
Receiver

DLNB
Transmitter/Receiver

Medium power duplexer

68P02900W21-S 01 Feb 2007 13-21

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 3 sector (4/4/4), with air combining, diversity, and medium power duplexers (3 antenna per sector)
A dual cabinet, 12 TCU configuration with air combining, diversity, and medium power duplexers, is shown in Figure 13-18. Table 13-12 provides a summary of the equipment required for this configuration.
Figure 13-18 3 sector (4/4/4), air combining, medium power duplexers
Rx ANTENNA (SECTOR 2) Tx/Rx Tx Tx/Rx ANTENNA ANTENNA ANTENNA (SECTOR 3) (SECTOR 3) (SECTOR 2) Rx Rx Tx Tx/Rx Tx ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA (SECTOR 2)(SECTOR 1) (SECTOR 1) (SECTOR 2) (SECTOR 1)

DUPLEXER

DUPLEXER

DLNB

Rx EXT BLOCK

DUPLEXER

DLNB

DLNB

IADU

IADU

CBF2
6 6

CBF1

CBF0

CBF2

CBF1

CBF0
6 6

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER M-Cell6 BTS CABINET

MASTER M-Cell6 BTS CABINET

Table 13-12 Equipment required for dual cabinet, 12 TCU configuration with air combining, diversity and medium power duplexers (3 antenna per sector) Quantity Equipment

9 2 12 6 3 1 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

CBF
Receiver

DLNB Rx extension block

Transmitter/Receiver

Medium power duplexer

68P02900W21-S 13-22 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 3 sector (4/4/4), with air combining, diversity, and medium power duplexers (2 antenna per sector)
A multiple cabinet, 12 TCU configuration with air combining, diversity, and medium power duplexers, is shown in Figure 13-19. Table 13-13 provides a summary of the equipment required for this configuration.
Figure 13-19 3 sector (4/4/4), air combining, medium power duplexers
Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1)

DUPLEXER

DUPLEXER

DUPLEXER

DLNB IADU

Rx EXT BLOCK

DUPLEXER

DUPLEXER

DUPLEXER
DLNB

DLNB

IADU

CBF2
6 6

CBF1

CBF0

CBF2

CBF1

CBF0
6 6

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER M-Cell6 BTS CABINET

MASTER M-Cell6 BTS CABINET

Table 13-13 Equipment required for multiple cabinet, 12 TCU configuration with air combining, diversity and medium power duplexers (2 antenna per sector) Quantity Equipment

6 2 12 6 3 1 6

Antennas M-Cell6 BTS cabinet TCU

Transmitter

CBF
Receiver

DLNB Rx extension block

Transmitter/Receiver

Medium power duplexer

68P02900W21-S 01 Feb 2007 13-23

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 3 sector (4/4/4), with cavity combining and diversity

A multiple cabinet, 12 TCU configuration with cavity combining and diversity, is shown in Figure 13-20. Table 13-14 provides a summary of the equipment required for this configuration.
Figure 13-20 3 sector (4/4/4), cavity combining
Tx ANTENNA (SECTOR 1) Rx ANTENNAS (SECTOR 1)

DLNB

IADU
(EXTENSION)

CCB

(OUTPUT)

CCB

T C U

T C U

T C U

T C U

A B

A B

A B

A B MASTER M-Cell6 CABINET

Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master cabinet for sectors 2 and 3.

Table 13-14 Equipment required for multiple cabinet, 12 TCU configuration with hybrid combining and diversity Quantity Equipment

6 3 12 3 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

CCB (output) CCB (extension)

Receiver

DLNB

68P02900W21-S 13-24 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 3 sector (4/4/4), with 3-input CBF, hybrid combining and diversity
A dual cabinet, 12 TCU configuration with 3-input CBF, hybrid combining and diversity, is shown in Figure 13-21. Table 13-15 provides a summary of the equipment required for this configuration.
Figure 13-21 3 sector (4/4/4), 3-input CBF, hybrid combining
Rx ANTENNA (SECTOR 3) Tx ANTENNA (SECTOR 3) Tx Tx Rx ANTENNA ANTENNA ANTENNA (SECTOR 2) (SECTOR 1) (SECTOR 2) Rx ANTENNA (SECTOR 1)

RF INPUT RF LOAD

DLNB

Rx EXT BLOCK IADU

DLNB

DLNB

IADU

RF INPUT RF LOAD 6 6

RF INPUT RF LOAD

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER M-Cell6 BTS CABINET

MASTER M-Cell6 BTS CABINET

68P02900W21-S 01 Feb 2007 13-25

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

Table 13-15 Equipment required for dual cabinet, 12 TCU configuration with 3-input CBF, hybrid combining and diversity Quantity Equipment

9 2 12 3 3 3 1

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Hybrid combiner module (HCOMB)

Receiver

DLNB Rx extension block

68P02900W21-S 13-26 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 3 sector (4/4/4), with 3-input CBF, air combining, diversity, and medium power duplexers
A multiple cabinet, 12 TCU configuration with 3-input CBF, air combining, diversity, and medium power duplexers, is shown in Figure 13-22. Table 13-16 provides a summary of the equipment required for this configuration.
Figure 13-22 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers
Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 3) Tx/Rx & Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 1)

RF INPUT RF LOAD

DUPLEXER

DLNB

Rx EXT BLOCK

DUPLEXER

DUPLEXER

DLNB

DLNB

IADU
RF INPUT 6 6 RF LOAD RF INPUT

IADU
6 RF LOAD 6

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER M-Cell6 BTS CABINET

MASTER M-Cell6 BTS CABINET

68P02900W21-S 01 Feb 2007 13-27

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

Table 13-16 Equipment required for multiple cabinet, 12 TCU configuration with 3-input CBF, air combining, diversity and medium power duplexers Quantity Equipment

6 2 12 3 3 3 1 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Hybrid combiner module (HCOMB)

Receiver

DLNB Rx extension block

Transmitter/Receiver

Medium power duplexer

68P02900W21-S 13-28 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 3 sector (5/5/5), with 3-input CBF, air combining, diversity, and medium power duplexers (3 antenna per sector)
A three cabinet, 15 TCU configuration with 3-input CBF, air combining, diversity, and medium power duplexers, is shown in Figure 13-23. Table 13-17 provides a summary of the equipment required for this configuration.
Figure 13-23 3 sector (5/5/5), 3-input CBF, air combining, medium power duplexers
Tx/Rx ANTENNA (SECTOR 1) Tx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 1)

DUPLEXER
RF INPUT RF LOAD

DLNB

IADU 3-INPUT CBF

NonHCOMB 6 6

3-INPUT CBF

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B MASTER M-Cell6 BTS CABINET

Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master cabinet for sectors 2 and 3.

Table 13-17 Equipment required for 3 cabinets, 15 TCU configuration with 3-input CBF, air combining, diversity and medium power duplexers (3 antennas/sector) Quantity Equipment

9 3 15 6 3 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Non-hybrid combiner (Non-HCOMB)

Receiver

DLNB
Transmitter/Receiver

Medium power duplexer

68P02900W21-S 01 Feb 2007 13-29

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 3 sector (5/5/5), with 3-input CBF, combining, diversity, and medium power duplexers (2 antenna per sector)
A three cabinet, 15 TCU configuration with 3-input CBF, combining, diversity, and medium power duplexers, is shown in Figure 13-24. Table 13-18 provides a summary of the equipment required for this configuration.
Figure 13-24 3 sector (5/5/5), 3-input CBF, combining, medium power duplexers
Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 1)

DUPLEXER DUPLEXER
RF INPUT RF LOAD

DLNB

3-INPUT CBF
NonHCOMB

3-INPUT CBF

IADU

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B MASTER M-Cell6 BTS CABINET

Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master cabinet for sectors 2 and 3.

Table 13-18 Equipment required for 3 cabinets, 15 TCU configuration with 3-input CBF, combining, diversity and medium power duplexers (2 antennas/sector) Quantity Equipment

6 3 15 6 3 3 6

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Non-hybrid combiner (Non-HCOMB)

Receiver

DLNB
Transmitter/Receiver

Medium power duplexer

68P02900W21-S 13-30 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 3 sector (6/6/6), with cavity combining, diversity, and high power duplexers
A multiple cabinet, 18 TCU configuration with cavity combining, diversity, and high power duplexers, is shown in Figure 13-25. Table 13-19 provides a summary of the equipment required for this configuration. An external equipment rack/cabinet is required for a high-power duplexer in an indoor installation.
Figure 13-25 3 sector (6/6/6), cavity combining, high power duplexers
Rx ANTENNA Tx/Rx ANTENNA

DLNB
ANT

IADU
CCB (EXTENSION) 6 6 CCB (OUTPUT) Rx

Tx HIGH POWER DUPLEXER

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B M-Cell6 SIDE CABINET

MASTER M-Cell6 BTS CABINET

Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master cabinet for sectors 2 and 3. Each extender cabinet terminates in a high power duplexer in the side cabinet.

Table 13-19 Equipment required for 3 RF cabinets, 18 TCU configuration with cavity combining, diversity and high power duplexers Quantity Equipment

6 3 1 18 3 3 3 3

Antennas M-Cell6 BTS cabinet M-Cell6 side cabinet TCU

Transmitter

CCB (output) CCB (extension)

Receiver

DLNB
Transmitter/Receiver

High power duplexer

68P02900W21-S 01 Feb 2007 13-31

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 3 sector (6/6/6), with 3-input CBF, air combining, diversity, and medium power duplexers (3 antenna per sector)
A three cabinet, 18 TCU configuration with 3-input CBF, air combining, diversity, and medium power duplexers, is shown in Figure 13-26. Table 13-20 provides a summary of the equipment required for this configuration.
Figure 13-26 3 sector (6/6/6), 3-input CBF, air combining, medium power duplexers
Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 1)

DUPLEXER DUPLEXER
RF INPUT RF LOAD

DLNB

3-INPUT CBF
NonHCOMB

3-INPUT CBF

IADU

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B MASTER M-Cell6 BTS CABINET

Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master cabinet for sectors 2 and 3.

Table 13-20 Equipment required for 3 cabinets, 18 TCU configuration with 3-input CBF, air combining, diversity and medium power duplexers (3 antennas/sector) Quantity Equipment

6 3 18 6 3 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Non-hybrid combiner (Non-HCOMB)

Receiver

DLNB
Transmitter/Receiver

Medium power duplexer

68P02900W21-S 13-32 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 3 sector (6/6/6), with 3-input CBF, combining, diversity, and medium power duplexers (2 antenna per sector)
A three cabinet, 18 TCU configuration with 3-input CBF, combining, diversity, and medium power duplexers, is shown in Figure 13-27. Table 13-21 provides a summary of the equipment required for this configuration.
Figure 13-27 3 sector (6/6/6), 3-input CBF, combining, medium power duplexers
Tx/Rx ANTENNA (SECTOR 1) Tx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 1)

DUPLEXER
RF INPUT RF LOAD RF INPUT RF LOAD

DLNB

IADU 3-INPUT CBF

NonHCOMB

3-INPUT CBF
6 6

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B MASTER M-Cell6 BTS CABINET

Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master cabinet for sectors 2 and 3.

Table 13-21 Equipment required for 3 cabinets, 18 TCU configuration with 3-input CBF, combining, diversity and medium power duplexers (2 antennas/sector) Quantity Equipment

6 3 18 6 3 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Non-hybrid combiner (Non-HCOMB)

Receiver

DLNB
Transmitter/Receiver

Medium power duplexer

68P02900W21-S 01 Feb 2007 13-33

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 3 sector (8/8/8), with cavity combining, diversity and medium power duplexers
A four cabinet, 24 TCU configuration with cavity combining, diversity and medium power duplexers, is shown in Figure 13-28 and Figure 13-29. Table 13-22 provides a summary of the equipment required for this configuration.
Figure 13-28 3 sector (8/8/8), cavity combining, medium power duplexers (Part 1)

68P02900W21-S 13-34 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

Figure 13-29 3 sector (8/8/8), cavity combining, medium power duplexers (Part 2)
Rx ANTENNA (SECTOR 1) DUPLEXER 2 DUPLEXER 1 TO MASTER M-Cell6 DUPLEXER 0 BTS CABINET Rx REV BLOCK 2 Rx REV BLOCK 1 Rx REV BLOCK 0 Tx ANTENNA (SECTOR 1)

DLNB

IADU

CCB (EXTENSION)

CCB (OUTPUT)

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

EXTENDER 1 M-Cell6 BTS CABINET Extender 2 and extender 3 M-Cell6 cabinets configured similar to the extender 1 cabinet for sectors 2 and 3.

Table 13-22 Equipment required for 4 RF cabinets, 24 TCU configuration with cavity combining, diversity and medium power duplexers Quantity Equipment

9 4 24 3 3 3 3 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

CCB (output) CCB (extension) CBF

Receiver

DLNB Rx extender block

Transmitter/Receiver

Medium power duplexer

68P02900W21-S 01 Feb 2007 13-35

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 3 sector (8/8/8), with cavity combining, diversity and both high and medium power duplexers
A multiple cabinet, 24 TCU configuration with cavity combining, diversity and both high and medium power duplexers, is shown in Figure 13-30 and Figure 13-31. Table 13-23 provides a summary of the equipment required for this configuration. An external equipment rack/cabinet is required for a high power duplexer in an indoor installation.
Figure 13-30 3 sector (8/8/8), cavity combining, high and medium power duplexers (Part 1)

68P02900W21-S 13-36 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

Figure 13-31 3 sector (8/8/8), cavity combining, high and medium power duplexers (Part 2)
TO MASTER M-Cell6 BTS CABINET DUPLEXER 2 DUPLEXER 1 DUPLEXER 0 Rx REV BLOCK 2 Rx REV BLOCK 1 Rx REV BLOCK 0 EXTENDER 2 M-Cell6 BTS CABINET EXTENDER 1 M-Cell6 BTS CABINET Tx/Rx Tx/Rx Tx/Rx ANTENNA ANTENNA ANTENNA (SECTOR 3)(SECTOR 2) (SECTOR 1)

EXTENDER 2 M-Cell6 BTS CABINET EXTENDER 1 M-Cell6 BTS CABINET

DLNB
ANT

IADU
CCB (EXTENSION) CCB (OUTPUT) Rx Tx

ANT

T C U

T C U

T C U

T C U

T C U

T C U

Rx Tx

ANT

Tx HIGH POWER DUPLEXERS EXTENDER 1 M-Cell6 BTS CABINET M-Cell6 SIDE CABINET Extender 2 and extender 3 M-Cell6 cabinets configured similar to the extender 1 cabinet for sectors 2 and 3. The master, extender 1 and extender 2 cabinets terminate in a high power duplexer in the side cabinet.

A B

A B

A B

A B

A B

A B

Rx

68P02900W21-S 01 Feb 2007 13-37

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

Table 13-23 Equipment required for 4 RF cabinets, 24 TCU configuration with cavity combining, diversity and both high and medium power duplexers Quantity Equipment

6 4 1 24 3 3 3 3 3 3 3

Antennas M-Cell6 BTS cabinet M-Cell6 side cabinet TCU

Transmitter

CCB (output) CCB (extension) CBF

Receiver

DLNB Rx extender block

Transmitter/Receiver

High power duplexer Medium power duplexer

68P02900W21-S 13-38 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 3 sector (8/8/8), with 3-input CBF, air combining, diversity, and medium power duplexers (3 antenna per sector)
A four cabinet, 24 TCU configuration with 3-input CBF, air combining, diversity, and medium power duplexers, is shown in Figure 13-32 and Figure 13-33. Table 13-24 provides a summary of the equipment required for this configuration.
Figure 13-32 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers (Part 1)
IADU TO EXTENDER 1 M-Cell6 BTS CABINET

Tx ANTENNA (SECTOR 3) RF INPUT RF LOAD

Tx/Rx ANTENNA (SECTOR 3)

Tx ANTENNA (SECTOR 2)

Rx ANTENNA (SECTOR 3)

Rx EXT BLOCK

DUPLEXER

DLNB

Rx EXT BLOCK

IADU IADU

6 RF INPUT RF LOAD RF INPUT RF LOAD

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER 3 M-Cell6 BTS CABINET

EXTENDER 2 M-Cell6 BTS CABINET

68P02900W21-S 01 Feb 2007 13-39

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

Figure 13-33 3 sector (8/8/8), 3-input CBF, air combining, medium power duplexers (Part 2)
TO EXTENDER 2 Rx EXT BLOCK M-Cell6 BTS CABINET Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 2) RF INPUT RF LOAD Tx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 1)

DUPLEXER

DLNB

Rx EXT BLOCK

DUPLEXER

DLNB

IADU
RF INPUT RF LOAD 6 6 RF INPUT RF LOAD

IADU

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER 1 M-Cell6 BTS CABINET

MASTER M-Cell6 BTS CABINET

Table 13-24 Equipment required for 4 cabinets, 24 TCU configuration with 3-input CBF, air combining, diversity and medium power duplexers (3 antennas/sector) Quantity Equipment

9 4 24 6 3 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF
Receiver

DLNB Rx extender block

Transmitter/Receiver

Medium power duplexer

68P02900W21-S 13-40 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 3 sector (8/8/8), with 3-input CBF, combining, diversity, and medium power duplexers (2 antenna per sector)
A four cabinet, 24 TCU configuration with 3-input CBF, combining, diversity, and medium power duplexers, is shown in Figure 13-34 and Figure 13-35. Table 13-25 provides a summary of the equipment required for this configuration.
Figure 13-34 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers (Part 1)
Tx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 3) DUPLEXER IADU TO EXTENDER 1 M-Cell6 BTS CABINET

RF INPUT RF LOAD

DUPLEXER

Rx EXT BLOCK

DUPLEXER

DLNB

Rx EXT BLOCK

IADU IADU

6 RF INPUT RF LOAD RF INPUT RF LOAD

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER 3 M-Cell6 BTS CABINET

EXTENDER 2 M-Cell6 BTS CABINET

68P02900W21-S 01 Feb 2007 13-41

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

Figure 13-35 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers (Part 2)
TO EXTENDER 2 M-Cell6 BTS CABINET Tx/Rx ANTENNA (SECTOR 2) DUPLEXER Rx REV BLOCK 1 Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1) RF INPUT RF LOAD Tx/Rx ANTENNA (SECTOR 1)

DUPLEXER

DUPLEXER

DLNB IADU

Rx EXT BLOCK

DUPLEXER

DUPLEXER

DLNB IADU

RF INPUT 6 6 RF LOAD

RF INPUT RF LOAD 6 6

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

HCOMB

3-INPUT CBF

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

A B

EXTENDER 1 M-Cell6 BTS CABINET

MASTER M-Cell6 BTS CABINET

Table 13-25 Equipment required for 4 cabinets, 24 TCU configuration with 3-input CBF, combining, diversity and medium power duplexers (2 antennas/sector) Quantity Equipment

6 4 24 6 6 3 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

3-input CBF Hybrid combiner module (HCOMB)

Receiver

DLNB Rx extender block

Transmitter/Receiver

Medium power duplexer

68P02900W21-S 13-42 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[DCS1800] 3 sector (2/2/2), with hybrid combining and diversity

A single cabinet, six TCU configuration with hybrid combining and diversity, is shown in Figure 13-36. Table 13-26 provides a summary of the equipment required for this configuration.
Figure 13-36 3 sector (2/2/2), hybrid combining
Tx ANTENNA (SECTOR 1) Tx ANTENNA (SECTOR 2) Tx ANTENNA (SECTOR 3) Rx ANTENNAS (SECTOR 1) Rx ANTENNAS (SECTOR 2) Rx ANTENNAS (SECTOR 3)

LNA

LNA

LNA

TxBPF

TxBPF

TxBPF

HYBRID

HYBRID

HYBRID

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B M-Cell6 BTS CABINET

Table 13-26 Equipment required for single cabinet, 6 TCU configuration with hybrid combining and diversity Quantity Equipment

9 1 6 3 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

TxBPF Hybrid combiner module (HCOMB)

Receiver

LNA

68P02900W21-S 01 Feb 2007 13-43

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[DCS1800] 3 sector (2/2/2), with hybrid combining, diversity, and medium power duplexers
A single cabinet, six TCU configuration with hybrid combining, diversity, and medium power duplexers, is shown in Figure 13-37. Table 13-27 provides a summary of the equipment required for this configuration.
Figure 13-37 3 sector (2/2/2), hybrid combining, medium power duplexers
Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 3) Rx ANTENNAS (SECTOR 1) Rx ANTENNAS (SECTOR 2) Rx ANTENNAS (SECTOR 3)

DUPLEXER

DUPLEXER

DUPLEXER

LNA

LNA

LNA

HYBRID

HYBRID

HYBRID

T C U

T C U

T C U

T C U

T C U

T C U

A B

A B

A B

A B

A B

A B M-Cell6 BTS CABINET

Table 13-27 Equipment required for single cabinet, 6 TCU configuration with hybrid combining, diversity and medium power duplexers Quantity Equipment

6 1 6 3 3 3

Antennas M-Cell6 BTS cabinet TCU

Transmitter

Hybrid combiner module (HCOMB)

Receiver

LNA
Transmitter/Receiver

Medium power duplexer

68P02900W21-S 13-44 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

M-Cell2 cabinets M-Cell6 cabinets

Diversity is assumed in all figures, unless stated otherwise.

[GSM900] 2 carrier, single sector, with hybrid combining and diversity

A single cabinet, two TCU configuration with hybrid combining and diversity, is shown in Figure 13-38. Table 13-28 provides a summary of the equipment required for this configuration.
Figure 13-38 2 carrier, single sector, hybrid combining
Tx ANTENNA Rx ANTENNAS

DLNB

CBF

T C U

T C U

A B

A B

M-Cell2 BTS CABINET

Table 13-28 Equipment required for single cabinet, 2 TCU configuration with hybrid combining and diversity Quantity Equipment

3 1 2 1 1

Antennas M-Cell2 BTS cabinet TCU

Transmitter

CBF
Receiver

DNLB

68P02900W21-S 01 Feb 2007 13-45

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[GSM900] 2 carrier, single sector, with hybrid combining, diversity, and medium power duplexer
A single cabinet, two TCU configuration with hybrid combining, diversity, and medium power duplexer, is shown in Figure 13-39. Table 13-29 provides a summary of the equipment required for this configuration.
Figure 13-39 2 carrier, single sector, hybrid combining, medium power duplexer
Tx/Rx ANTENNA Rx ANTENNA

DUPLEXER

DLNB

CBF

T C U

T C U

A B

A B

M-Cell2 BTS CABINET

Table 13-29 Equipment required for single cabinet, 2 TCU configuration with hybrid combining, diversity and medium power duplexer Quantity Equipment

2 1 2 1 1 1

Antennas M-Cell2 BTS cabinet TCU

Transmitter

CBF
Receiver

DNLB
Transmitter/Receiver

Medium power duplexer

68P02900W21-S 13-46 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[GSM900] 2 sectors (1 carrier per sector), with diversity

A single cabinet, two TCU configuration with diversity, is shown in Figure 13-40. Table 13-30 provides a summary of the equipment required for this configuration.
Figure 13-40 2 sectors (1 carrier per sector)
Tx ANTENNA Tx ANTENNA Rx ANTENNAS Rx ANTENNAS

DLNB

DLNB

CBF

CBF

T C U

T C U

A B

A B

M-Cell2 BTS CABINET

Table 13-30 Equipment required for single cabinet, 2 TCU configuration with diversity Quantity Equipment

6 1 2 2 2

Antennas M-Cell2 BTS cabinet TCU

Transmitter

CBF
Receiver

DNLB

68P02900W21-S 01 Feb 2007 13-47

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

[DCS1800] 2 carrier, single sector, with air combining and diversity

A single cabinet, two TCU configuration with air combining and diversity, is shown in Figure 13-41.
Table 13-31 provides a summary of the equipment required for this configuration. Figure 13-41 2 carrier, single sector, air combining
Tx ANTENNA Tx/Rx ANTENNA Rx ANTENNA

DUPLEXER LNA

TxBPF

T C U

T C U

A B

A B

M-Cell2 BTS CABINET

Table 13-31 Equipment required for single cabinet, 2 TCU configuration with air combining and diversity Quantity Equipment

3 1 2 1 1 1

Antennas M-Cell2 BTS cabinet TCU

Transmitter

TxBPF
Receiver

LNA
Transmitter/Receiver

Medium power duplexer

68P02900W21-S 13-48 01 Feb 2007

System Information: BSS Equipment Planning

M-Cell RF configurations

[DCS1800] 2 sectors, with diversity

A single cabinet, two TCU configuration with diversity, is shown in Figure 13-42. Table 13-32 provides a summary of the equipment required for this configuration.
Figure 13-42 2 sectors
Tx ANTENNA Tx ANTENNA Rx ANTENNAS Rx ANTENNAS

LNA

LNA

TxBPF

TxBPF

T C U

T C U

A B

A B

M-Cell2 BTS CABINET

Table 13-32 Equipment required for single cabinet, 2 TCU configuration with diversity Quantity Equipment

6 1 2 2 2

Antennas M-Cell2 BTS cabinet TCU

Transmitter

TxBPF
Receiver

LNA

68P02900W21-S 01 Feb 2007 13-49

M-Cell RF configurations

Chapter 13: M-Cell BTS configurations

68P02900W21-S 13-50 01 Feb 2007

Index

A planning example of BSS support for LCS provisioning, 986 Acronyms, 1-25 Adaptive multi-rate (AMR) Applications, 3-12 Capacity and coverage, 3-10 Interoperability with EGPRS, 3-13 Interoperability with GSM half rate, 3-13 Introduction, 3-10 Migration to AMR half rate, 3-13 Quality of service, 3-11 Adaptive multi-rate (AMR), 3-10 AMR Full Rate and AMR Half Rate speech quality, 4-5 AMR voice quality improvement and coverage, 4-10 Antenna configurations, 5-16 Antenna planning actions, 5-16 Planning considerations, 5-16
B

Backhaul, 4-31 Battery back-up provisioning, 5-33 Introduction, 5-33 Planning considerations, 5-33 Benefits of AMR, 4-5 Benefits of GSM half rate, 4-11 BSC planning overview, 6-2 Mixing of equipment types, 6-2 Outline of planning, 6-3 BSC system capacity, 6-5 Enhanced BSC capacity option, 6-7 Huge BSC capacity option, 6-7 LCS option, 6-7 Scaleable BSC, 6-6 System capacity summary, 6-5 BSS - PCU planning example for EGPRS, 8-69 BSS - PCU planning example for EGPRS with QoS enabled, QoS2 is not enabled, 8-75 BSS cell planning, 3-107 BSS equipment overview System architecture, 1-4 System components, 1-5 BSS equipment overview, 1-4 BSS features {22168} Enhanced BSC capacity using DSW2, 1-18

{23291}Dual transfer mode, 1-19 {26740} High bandwidth interconnect between BSC and PCU (PSI2), 1-18 {28337} BSC signaling link set capacity and flexibility (High speed MTL), 1-18 {28351} Addition of new BSC/PCU software (PXP) and hardware (PSI2) to increase GPRS capacity (ePCU), 118 {30828} CTU2-D, 1-19 Adaptive Multi-Rate (AMR), 1-11 Advanced Speech Call Item (ASCI), 1-14 BSC Reset Management (BRM), 1-13 Code Storage Facility Processor (CSFP), 1-10 Diversity, 1-8 Enhanced-GPRS (EGPRS), 1-10 Frequency hopping, 1-9 GSM half rate, 1-12 Improved timeslot sharing, 1-17 LoCation Services, 1-13 PCU for GPRS upgrade, 1-10 Planning impacts, 1-8 Quality of Service (QoS), 1-15 Short Message Service, Cell Broadcast (SMS CB), 1-9 VersaTRAU backhaul for EGPRS, 1-14 BSS features, 1-8 BSS interfaces, 2-2 BSS planning for GPRS/EGPRS, 8-2 BSS planning overview Background information, 1-22 Planning methodology, 1-23 BSS planning overview, 1-22 BSS-PCU hardware planning example for EGPRS, 8-69 BSS-PCU hardware planning example for GPRS BSS - PCU planning example for GPRS, 8-63 Introduction, 8-63 BSS-PCU hardware planning example for GPRS, 8-63 BTS main control unit, 5-25 Introduction, 5-25 Planning actions, 5-27 Planning considerations HorizonII macro/HorizonII mini as expansion cabinet, 526 Planning considerations, 5-25 BTS planning overview, 5-2 Outline of planning steps, 5-2

68P02900W21-S 01 Feb 2007 I

Index

Cabinet, 9-5 Cabinet interconnection Introduction, 5-28 Planning considerations, 5-28 Site expansion board planning actions, 5-32 XMUX/FMUX/FOX planning actions, 5-31 Cabinet interconnection, 5-28 Calculations using alternative call models, 9-17 Call model parameters for capacity calculations, 3-111 Typical call parameters, 3-111 Capacity calculations, 6-4 Remote transcoding, 6-4 Capacity increase due to half rate usage, 4-11 Carrier equipment CTU/CTU2 power supply considerations, 5-18 Planning considerations, 5-20 Restrictions when using CTU2s in Horizonmacro BTSs, 517 Transceiver planning actions, 5-20 Circuit pooling, 4-22 CLKX planning actions, 6-76 CLKX requirement, 9-15 Clock extender (CLKX), 6-76, 7-27 CLKX planning actions, 7-27 Planning considerations, 7-27 Codec modes, 4-16 Connecting Horizon II macro cabinets to Horizonmacro cabinets, 12-63 Compatibility issues, 12-63 Connection overview, 12-63 Examples of mixed cabinet configurations, 12-63 Connecting Horizon II macro cabinets to M-Cell6 cabinets, 12-71 Compatibility issues, 12-71 Connection overview, 12-71 Control channel calculations, 3-116 Control channel configurations, 3-133 Number of CCCHs and PCCCHs per BTS cell, 3-118 Number of SDCCHs per BTS cell, 3-130 Planning considerations, 3-117 User data capacity on the PCCCH timeslot, 3-129
D

Deriving call model parameters from network statistics, 11-2 Blocking for TCHs (PB TCHs), 11-13 Call duration (T), 11-6, 11-38 EGPRS MCS1 downlink usage (MCS1_usage_DL), 11-22 EGPRS MCS1 uplink usage (MCS1_usage_UL), 11-21 EGPRS MCS2 downlink usage (MCS2_usage_DL), 11-24 EGPRS MCS2 uplink usage (MCS2_usage_UL), 11-23 EGPRS MCS3 downlink usage (MCS3_usage_DL), 11-26 EGPRS MCS3 uplink usage (MCS3_usage_UL), 11-25 EGPRS MCS4 downlink usage (MCS4_usage_DL), 11-28 EGPRS MCS4 uplink usage (MCS4_usage_UL), 11-27 EGPRS MCS5 downlink usage (MCS5_usage_DL), 11-30 EGPRS MCS5 uplink usage (MCS5_usage_UL), 11-29 EGPRS MCS6 uplink usage (MCS6_usage_UL), 11-31 EGPRS MCS7 downlink usage (MCS7_usage_DL), 11-33 EGPRS MCS8 downlink usage (MCS8_usage_DL), 11-35 EGPRS MCS8 uplink usage (MCS8_usage_UL), 11-34

EGPRS MCS9 downlink usage (MCS9_usage_DL), 11-37 EGPRS MCS9 uplink usage (MCS9_usage_UL), 11-36 GPRS CS1 downlink usage (CS1_usage_DL), 11-15 GPRS CS1 uplink usage (CS1_usage_UL), 11-14 GPRS CS2 downlink usage (CS2_usage_DL), 11-17 GPRS CS2 uplink usage (CS2_usage_UL), 11-16 GPRS CS3 uplink usage (CS3_usage_UL), 11-18 GPRS CS4 downlink usage (CS4_usage_DL), 11-20 GPRS CS4 uplink usage (CS4_usage_UL), 11-19 IMSI detaches per call (I), 11-40 Location update factor (L), 11-10, 11-40 No. of SMSs per call (S), 11-39 Number of location updates per call (l), 11-40 Pages per call (PPC), 11-11 Paging rate (PGSM), 11-11 Paging Rate (PGSM) for a BSC, 11-40 Percent link utilization BSC to BTS [U(BSC BTS)], 1113 Percent link utilization MSC to BSS [U(MSC BSS)], 1112 Ratio of handovers per call (H), 11-8, 11-39 Ratio of IMSI detaches per call (I), 11-10 Ratio of intra BSS handovers to all handovers (i), 11-9 Ratio of intra-BSS handovers to all handovers (i), 11-39 Ratio of location updates per call (I), 11-9 Ratio of SMSs per call (S), 11-7 Sample statistic calculations, 11-38 Standard call model parameters, 11-2 Description, 4-23 Determine the hardware requirements for BTS B, 9-5 Determine the hardware requirements for BTS K, 9-8 Determine the hardware requirements for the BSC, 9-11 Determine the hardware requirements for the RXCDR, 9-14 Determining the number of GSLs required, 6-45 Load balancing, 6-48 Planning considerations, 6-45 Determining the number of LMTLs required, 6-40 BSC to SMLC interconnection planning actions, 6-41 Calculate the number of LCFs for LMTL processing, 6-41 Determining the number of LMTLs, 6-40 Introduction, 6-40 Planning considerations, 6-40 Determining the number of MTLs required, 6-32 Calculate the number of LCFs for MTL processing, 6-38 Introduction, 6-32 LCFs for 64k MTL links, 6-38 LCFs for HSP MTL links, 6-38 MSC to BSC signaling over a satellite link, 6-39 Non-standard traffic model for 64k MTL, 6-35 Non-standard traffic model for HSP MTL, 6-36 Planning considerations, 6-32 Standard traffic model, 6-33 Determining the number of RSLs required, 6-18 BSC to BTS E1 interconnect planning actions, 6-27 Determining the number of RSLs, 6-19 Non-standard traffic model, 6-22 One phase access and enhanced one phase, 6-19 Planning considerations, 6-18 Standard traffic model, 6-20 Determining the number of XBLs required, 6-42 Determining the number of XBLs, 6-42 Introduction, 6-42

68P02900W21-S II 01 Feb 2007

Index

Non-standard traffic model, 6-43 Standard traffic model, 6-43 Determining the required BSS signaling link capacities, 6-8 Assumptions used in capacity calculations, 6-15 BSC signaling traffic model, 6-8 Link capacities, 6-17 Typical parameter values, 6-10 Digital shelf power supply, 6-81, 7-32 Planning considerations Power supply planning actions, 7-32 Planning considerations, 7-32 Downlink adaptation MS monitor, 4-17 DPROC board, 8-25 DRI/Combiner operability components, 5-38 DRI and combiner relationship, 5-38 Overview, 5-38 DTM Transfer Mode DTM Timeslots planning considerations, 3-107 System considerations, 3-109
E

E1 link/ETH link provisioning for GPRS and EGPRS, 8-43 E1 interface provisioning, 8-43 E1 Planning considerations, 8-43 Ethernet interface provisioning, 8-44 EGPRS enabled CTU2/CTU2D configuration, 5-13 Baseband hopping (BBH), 5-14 Broadcast control channel (BCCH) RTF configuration, 515 EGPRS enabled CTU2/CTU2D configuration limitations, 5-13 EGPRS general configuration, 5-13 Emergency call handling, 4-22 Equipment descriptions, 4-29 Evolved PCU (ePCU), 8-10 External power requirements, 5-34 Introduction, 5-34 Planning considerations, 5-34
F

Four cabinet BTS configuration, 13-9 Four cabinet M-Cell6 BTS, 13-9 Four cabinet BTS configurations, 12-17 Four cabinet Horizon II macro BTS, 12-17 Four cabinet Horizon II mini BTS, 12-18 Four cabinet Horizonmacro BTS, 12-19 Frequency planning Introduction, 3-100 Rules for baseband hopping (BBH), 3-103 Rules for synthesizer frequency hopping (SFH), 3-100 Frequency planning, 3-100 Frequency re-use Carrier/Interference (C/I) ratio, 3-44 Introduction, 3-41 Re-use pattern, 3-42 Sectorization of sites, 3-46 Sources of interference, 3-45 Frequency re-use, 3-41

GCLK planning actions, 6-75 GCLK requirement, 9-15 Generic clock (GCLK), 6-75, 7-26 GCLK planning actions, 7-26 Planning considerations, 7-26 Generic Processor BSC types, 6-51 Cell broadcast link, 6-54 Code storage facility processor, 6-54 GPROC functions and types, 6-49 GPROC nomenclature, 6-49 GPROC planning actions, 6-56 GPROC redundancy, 6-54 GPROC3/GPROC3-2 planning assumptions, 6-51 Introduction, 6-49 OMF GPROC required, 6-54 Planning considerations, 6-52 Generic processor (GPROC), 6-49, 7-9 GPROC nomenclature, 7-9 Planning considerations, 7-9 GPROC requirement, 9-15 GPRS/EGPRS air interface planning process, 3-161 Configurable initial coding scheme, 3-185 Estimate timeslot provisioning requirements, 3-173 Estimating the air interface traffic throughput, 3-171 File transit times calculations, 3-182 GPRS/EGPRS data rates, 3-186 Optimum file size calculation, 3-181 Select a cell plan, 3-172 GPRS/EGPRS network traffic estimation and key concepts, 3-138 BSS timeslot allocation methods, 3-152 Carrier timeslot allocation examples, 3-146 Dynamic timeslot allocation, 3-140 Provisioning the network with switchable timeslots, 3-154 Switchable timeslot usage, 3-159 Timeslot allocation process on carriers with GPRS traffic, 3-160 GPRS/EGPRS traffic planning, 3-137 Determination of expected load, 3-137 GSM frequency spectrum, 3-4 Absolute radio frequency channel capacity, 3-5 DCS1800 frequency spectrum, 3-5 GSM900 frequency spectrum, 3-4 Modulation techniques and channel spacing, 3-6 GSM half rate Capacity and coverage, 3-14 Interoperability with AMR half rate, 3-16 Interoperability with EGPRS, 3-16 Introduction, 3-14 Migration to half rate, 3-16 Quality of service, 3-14 GSM half rate, 3-14 GSM half rate Applications, 3-15 GSM half rate basic operation, 4-2 GSM Half Rate speech quality, 4-11 GSR9 QoS2, 3-109

68P02900W21-S 01 Feb 2007 III

Index

Half rate utilization, 4-23 Handover and power control, 4-19 Handover and power control thresholds, 4-19 Hardware, 4-29 Horizon macrocell RF configurations, 12-20 Horizon II macro cabinets, 12-20 Horizon II macro cabinets with PGSM duplexer, 12-30 Horizon II micro cabinets, 12-44 Horizon II mini cabinets, 12-36 Horizoncompact2, 12-56 Horizonmacro cabinets, 12-47 Overview of configuration diagrams, 12-20
I

LCS planning example calculations, 9-86 Line interface boards (BIB/PBIB, T43/PT43), 6-79 Line interface modules HIM-75/HIM-120 planning actions, 5-37 Introduction, 5-37 Planning considerations, 5-37 Line interface modules (HIM-75, HIM-120), 5-37 Line interfaces (BIB, T43), 7-30 BIB/T43 planning actions, 7-31 Planning considerations, 7-30 Link interface, 9-15 Local area network extender (LANX), 6-77 Location area planning calculations, 10-3 Location area planning considerations, 10-2
M

Influencing factors, 4-3 Interconnecting the BSC and BTSs, 2-4 Interconnection rules, 2-4 Inter-radio access technology (2G-3G) cell reselection and handovers Impact of 2G-3G handovers on GSM system architecture, 3-106 Inter-radio access technology (2G-3G) cell reselection and handovers, 3-105 Inter-radio access technology (2G-3G) cell reselection and handovers Introduction, 3-105 Inter-radio access technology (2G-3G) cell reselection and handovers 2G-3G handover description, 3-105 Inter-radio access technology (2G-3G) cell reselection and handovers System considerations, 3-106 Introduction, 4-16 Introduction to AMR and {22064} GSM planning, 4-2 Introduction to BSS planning for GPRS/EGPRS, 8-2 Introduction to BSS-PCU hardware planning, 8-69 Introduction to handover and power control, 4-19 Introduction to transcoding, 6-58
K

Kiloport switch (KSW) and double kiloport switch (DSW2), 7-18 KSW/DSW2 planning actions, 7-19 Planning considerations, 7-18 Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX), 6-72, 7-24 KSWX/DSWX planning actions, 7-25 Planning considerations, 7-24 KSW/DSW2 requirement, 9-15 KSWX/DSWX planning actions, 6-73 KSWX/DSWX requirement, 9-15
L

Macrocell cabinets, 5-4 Horizon II macro, 5-4 Horizoncompact and Horizoncompact2, 5-5 Horizonmacro, 5-4 M-Cell2, 5-5 M-Cell6, 5-5 Managed HDSL on micro BTSs, 2-22 Integrated HDSL interface General HDSL guidelines, 2-24 Microcell system planning, 2-24 Integrated HDSL interface, 2-22 Manual overview, 1-2 Maximum BSS configuration, 8-14 M-Cell BTS configurations, 13-2 M-Cell RF configurations, 13-10 M-Cell2 cabinets, 13-45 M-Cell6 cabinets, 13-10 overview, 13-10 Micro base control unit (microBCU), 5-21 MicroBCU planning actions, 5-21 Planning considerations, 5-21 Microcell enclosures Horizon II micro, 5-7 Horizon II mini, 5-6 Horizonmicro and Horizonmicro2, 5-7 Microcell enclosures, 5-6 Microcell RF configurations, 12-60 Horizonmicro2, 12-60 Microcellular solution Combined cell architecture, 3-97 Combined cell architecture structure, 3-98 Expansion solution, 3-99 Layered architecture, 3-97 Microcellular solution, 3-97 Miscellaneous information, 4-22 MPROC board, 8-24 Multiple serial interface (MSI), 7-16 MSI planning actions, 7-17 Planning considerations, 7-16
N

LAN extender (LANX), 7-28 LANX planning actions, 7-28 Planning considerations, 7-28 LANX planning actions, 6-77 LANX requirement, 9-16

Network expansion using macro/microcell BTSs, 5-36 Expansion considerations, 5-36 Introduction, 5-36

68P02900W21-S IV 01 Feb 2007

Index

Mixed site utilization, 5-36 Network interface unit (NIU) and site connection, 5-22 NIU planning actions, 5-24 Planning considerations, 5-22 Network topology, 2-6, 9-3 16 kbit/s RSL, 2-16 16 kbit/s XBL, 2-19 Aggregate Abis, 2-10 Daisy chain connection, 2-8 Daisy chain planning, 2-8 Dynamic allocation of RXCDR to BSC circuits (DARBC), 2-20 RTF path fault containment, 2-14 Star connection, 2-7 New hardware, 4-3 Non volatile memory (NVM) board, 7-33 NVM planning actions, 7-33 Planning Considerations, 7-33 NVM planning actions, 6-82
O

on volatile memory (NVM) board, 6-82 Operational aspects, 4-27 Overcoming adverse propagation effects {22064} GSM speech channel encoding for half rate, 3-56 64 kbit/s TRAU for EGPRS, 3-86 Discontinuous transmission (DTX), 3-88 EGPRS channel coding schemes, 3-76 Error protection and detection, 3-48 GPRS channel coding schemes, 3-70 GSM circuit-switched data channel encoding, 3-62 GSM control channel encoding, 3-61 GSM speech channel encoding for AMR full rate, 3-57, 358 GSM speech channel encoding for enhanced full rate, 3-55 GSM speech channel encoding for full rate, 3-53 Hardware techniques, 3-47 Link adaptation (LA) in GPRS/EGPRS, 3-87 Link adaptation for AMR channels, 3-60 Mapping logical channels in the TDMA frame structure, 364 Receive diversity, 3-90 Voice activity detection (VAD), 3-87 Overcoming adverse propagation effects, 3-47
P

Gb entities, 8-57 Gb link timeslots, 8-60 Gb signaling, 8-58 General planning guidelines, 8-58 Introduction, 8-57 Specific planning guidelines, 8-58 PICP or PRP planning considerations, 8-25 PIX planning actions, 6-78 PIX requirement, 9-15 Planning, 4-4 Planning considerations, 8-22 Horizon II macro as master cabinet, 5-31 Horizon II mini as master cabinet, 5-31 Planning example 1, 9-17 Planning example 4 (using AMR), 9-61 Planning example for DTM Feature (FR23291), 9-89 Planning tools, 3-3 PMC module, 8-30 Power supply, 9-16 Power supply planning actions, 6-81 Pre-requisites, 9-2 Propagation effects on GSM frequencies Attenuation, 3-23 Decibels, 3-17 Environmental effects on propagation, 3-23 Fresnel zone, 3-19 GSM900 path loss, 3-38 Multipath propagation, 3-26 Path loss GSM900 against DCS1800, 3-39 Propagation production, 3-17 Radio refractive index (RRI), 3-20 Propagation effects on GSM frequencies, 3-17 PRP/PICP configure, 8-32 PXP configuration, 8-37 PXP planning considerations, 8-28
Q

QoS capacity and QoS2 impact CTU2D impact, 8-56 MTBR allocation, 8-47 PRP-PDTCH QoS planning, 8-49 QoS capacity and QoS2 impact, 8-45 Quality and capacity, 4-5
R

Parallel interface extender (PIX), 6-78, 7-29 PIX planning actions, 7-29 Planning considerations, 7-29 Parameter descriptions, 4-23 PCU equipment redundancy and provisioning goals, 8-32 PCU equipment redundancy planning, 8-32 PCU hardware layout, 8-20 PCU shelf (cPCI), 8-22 PCU to SGSN interface planning, 8-2 PCU-SGSN traffic and signal planning, 8-57 traffic and signaling planning Determining net Gb load, 8-59 Frame relay parameter values, 8-60

Rate adaptation, 4-16 Rear Transition Module, 8-31 Receive configurations, 5-8 Planning considerations, 5-8 Receiver planning actions, 5-9 Receiver requirements, 9-8 Remote transcoder planning overview, 7-2 Outline of planning steps, 7-2 RXCDR system capacity, 7-4 RXCDR to BSC connectivity, 7-5 Capacity, 7-5 RXCDR to BSC links, 7-6 E1 interconnect planning actions, 7-7 RXCDR to MSC links, 7-8 E1 interconnect planning actions, 7-8

68P02900W21-S 01 Feb 2007 V

Index

RXU shelves, 7-21 Planning considerations, 7-21 RXU shelf planning actions, 7-22
S

Single cabinet BTS configurations, 12-6, 13-4 Single cabinet Horizon II macro BTS, 12-6 Single cabinet Horizon II micro BTS, 12-8 Single cabinet Horizon II mini BTS, 12-7 Single cabinet Horizonmacro BTS, 12-9 Single cabinet M-Cell2 BTS, 13-5 Single cabinet M-Cell6 BTS, 13-4 Standard configurations, 12-2 Standard M-Cell configurations, 13-3 Subscriber environment Distribution, 3-94 Environment, 3-93 Future planning, 3-96 Hand portable subscribers, 3-95 Subscriber environment, 3-93 Support for equipment redundancy, 8-32
T

The exercise, 9-4 Three cabinet BTS configuration, 13-8 Three cabinet M-Cell2 BTS, 13-8 Three cabinet BTS configurations, 12-13 Three cabinet Horizon II macro BTS, 12-13 Three cabinet Horizon II micro BTS, 12-15 Three cabinet Horizon II mini BTS, 12-14 Three cabinet Horizonmacro BTS, 12-16 Thresholds and hystereses, 4-17 Timeslot usage, 4-15 Traffic capacity Channel blocking, 3-8

Dimensioning, 3-8 Grade of service, 3-9 Traffic flow, 3-9 Traffic capacity, 3-8 Transcoder requirement, 9-14 Transcoding, 6-58, 7-10 EGDP provisioning, 6-60 GDP/XCDR/EGDP/GDP2 planning considerations, 6-59 Planning actions for transcoding at the BSC, 6-61 XCDR/GDP/EGDP/GDP2 planning considerations, 7-12 EGDP provisioning, 7-13 Transmit configurations, 5-11 Planning considerations, 5-11 Transmit planning actions, 5-12 Transmitter combining requirements, 9-8 Two cabinet BTS configuration, 13-6 Two cabinet M-Cell6 BTS, 13-6 Two cabinet M-Cell6 BTS with CTU2 Adapter, 13-7 Two cabinet BTS configurations, 12-10 Two cabinet Horizon II macro BTS, 12-10 Two cabinet Horizon II mini BTS, 12-11 Two cabinet Horizonmacro BTS, 12-12 Typical BSS configurations, 12-3 BSC with 24 BTSs, 12-3 BSC with full redundancy, 12-4 Transcoder, 12-5 Typical parameter values, 9-86
U

Upgrading the PCU, 8-40

V

Verify the number of BSU shelves and BSSC cabinets, 6-83 Verify the number of RXU shelves and BSSC cabinets, 7-34 Verification, 7-34

68P02900W21-S VI 01 Feb 2007

Standard Printing Instructions

Part Number Manual Title Date 68P02900W21-S System Information: BSS Equipment Planning 01-Feb-2007

A4 Ring Bound - GSD (UK) Binder Printing Finishing 4 D-ring binder - A4 size (210mm x 297mm) white PVC. 40mm or 65mm capacity depending on the size of the manual. Clear pockets on front and spine. Cover / spine text overprinted onto Motorola supplied cover stock. Body- printed double sided onto white A4 (210mm x 297mm) 80g 4 hole paper. A4 size (210mm x 297mm) clear PVC sheet front page for protection. Bag wrapped with clear polythene.

If this is to be used by manufacturing as an Inbox document, then refer to appropriate Materials or Methods Specification.